Example and tests for otel collector exporter is not updated still uses serviceName

The opentelemetry collector exporter is not updated. In examples and tests, It still uses serviceName for config and looking at the codebase it does not expose that anymore.
I wonder how these got in if we use typescript
https://github.com/open-telemetry/opentelemetry-js/blob/a3b77387012a5f53c193efdefcbf5f6272876e4d/packages/opentelemetry-exporter-collector/test/node/CollectorTraceExporter.test.ts#L61
https://github.com/open-telemetry/opentelemetry-js/blob/a3b77387012a5f53c193efdefcbf5f6272876e4d/examples/collector-exporter-node/tracing.js#L15
I am also unsure what should be the practice now? Should this be how we configure serviceName now?
https://github.com/open-telemetry/opentelemetry-js/issues/2271

In the updated example just a heads up
import { ResourceAttributes } from '@opentelemetry/semantic-conventions'
import { Resource } from '@opentelemetry/resources'

both libraries also are still on 0.20.0

Thanks @delaneyj 🙏

The opentelemetry collector exporter is not updated. In examples and tests, It still uses serviceName for config and looking at the codebase it does not expose that anymore.
I wonder how these got in if we use typescript
https://github.com/open-telemetry/opentelemetry-js/blob/a3b77387012a5f53c193efdefcbf5f6272876e4d/packages/opentelemetry-exporter-collector/test/node/CollectorTraceExporter.test.ts#L61
https://github.com/open-telemetry/opentelemetry-js/blob/a3b77387012a5f53c193efdefcbf5f6272876e4d/examples/collector-exporter-node/tracing.js#L15
I am also unsure what should be the practice now? Should this be how we configure serviceName now?
#2271

The first one was allowed because of the as any on line 64.
The second one was allowed because examples aren't type checked.

Can we remove the any then?
Ohhh I see how can we enable type checking in the examples do we add some github actions

The examples aren't written in typescript. in order to enable type checking, they would need to be modified for it. This is something we've talked about in the past but just haven't gotten to

Can we remove the any then?

Sure do you want to make a PR?

@dyladan - please assign me this issue. I am working in @alolita team. Thank you

@dyladan Can you please assign this to me
CC: @alolita


Need to remove old unused code

I noticed that gene is still making requests to ws://null/. This is an artifact of the old backend API which used websockets. We need to remove that code, as well as a bunch of other things involved in the old local file support (bgzf, compression, etc).

Thank you @anderspitman related to the old backend expiration issues @yiq mentioned at lab meeting, correct?

This particular request ws://null/ can be another reason why gene.iobio is shown as not secure??
Console message:

The other reason that you have mentioned is http://iobio for image source.
Related to issue: #471

@mvelinder it's not completely related. I would say that is a higher priority so we can turn off the old backend. This is essentially cleanup.

Is this pressing?

I would say no (but it needs to be kept open), unless it's causing https://github.com/iobio/gene.iobio.vue/issues/755, then yes.

The amount of code that needs to be removed to fix the particular error @adityaekawade mentions should be quite easy to take care of.

Removing iobio.js, iobio.min.js, and binary.js from here may be it: https://github.com/iobio/gene.iobio.vue/tree/master/client/app/third-party
But there are a bunch of other unused files in there that we need to clean up at some point.

@anderspitman @tonydisera Do we still need to address this?

Yep

Yep.


Generate Automatic-Module-Name attribute

As it stands, Java 9 Platform Module System cannot infer module name from shapeless' jars due to cross compilation (underscores in _2.xx).
This simple change adds an Automatic-Module-Name attribute to MANIFEST, making it possible to require shapeless modules, rather than going through various repackaaging hacks.
A proper modularization would include definition of module-info.java but that's outside the scope.

Any problem with this PR? This should unblock anyone who wants to use shapeless as a Java module, with a minimal effort.


Test: Update Docs Site Readme

Testing to confirm .env related updates are all still working exactly as expected.

ok - our Github Actions API integration (which is how the now.sh deployment URLs show up on this PR) now seems to be working correctly w/ the new Github Access Token that was added to our Travis Environment Variables config. Closing out.
CC @colbytcook @danielamorse


Display grid - configure from launch file

Desired behavior
I saw there is the GridConfig plugin, which is nice, but I haven't found a way to configure a grid at startup time, automatically. Ideally, even have the option to override <world><scene><grid>false is specified in the world SDF.

Note that the GridConfig plugin lives in ign-gazebo. Here's where the SDF would be parsed.
The Grid3D plugin on the other hand lives in ign-gui and accepts SDF parameters.
We should unify these 2 plugins into one.

Thanks for the clarification. However, Grid3d doesn't work for me with ogre2. I get a flickering in the 3D window, and the Qt widget shows nothing but the titlebar. Is that a known issue?

Grid3d doesn't work for me with ogre2 on Dome.

It's been fixed for Citadel on #172 and is being ported forward in #180

I've now tried adding Grid3D into gui.config, but Ign Gazebo 4 GUI crashes right on startup.
It's sufficient to add
<plugin filename="Grid3D" name="Grid">
    <engine>ogre2</engine>
    <scene>scene</scene>
</plugin>

to e.g. gazebo_plugins.ign from ign-launch examples. It doesn't even have to contain any <insert> section.
Is that still expected and waiting for a fix to be merged, or should I report it as a new issue?
Adding the grid at runtime now works.

We should unify these 2 plugins into one.

#324 consolidates Grid3D with GridConfig and should work from startup or when added at runtime.


Using "Reopen Editor With..." on a notebook doesn't fully close the notebook editor.

VS Code Version: Stable
OS Version: Windows

Steps to Reproduce:

Install the .NET Interactive extension ms-dotnettools.dotnet-interactive-vscode
Install the Jupyter extension ms-toolsai.jupyter.
Open an existing .ipynb file with the Jupyter (preview) editor.
Right-click the editor tab and "Reopen Editor With..." and select ".NET Interactive Jupyter".
Repeat step 4 but select Jupyter (preview) again.

Result:
Depending on how fast things happen, at some point VS Code will fail to reopen the notebook and say that it can't open view type X because view type Y already exists.

Does this issue occur when all extensions are disabled?: N/A

that it can't open view type X because view type Y already exists.

Yes - we don't support to open the same file multiple times for different view types. That is a limitation in how we have implemented things - everything gets identified by uri, nut by the [uri,type]-tuple. With this limitation there are two options

don't allow to create another notebook with different viewType (as today)
dispose/close the conflicting notebook when another notebook comes along

Both aren't ideal, option (1) was the easiest to implement because option (2) means all editors etc need to react too. This means the reference-counting contract is violated (the model is disposed despite them holding a reference) and funny scenarios would happen: split an editor, in one editor do reopen-with, the second editor must now close...
We are aware of this limitation but I our thinking is that content providers are shared across extensions, e.g there would be a "base extension" that only implements read/writing of ipynb-files

@brettfo out of curiosity, why would one want to open an ipynb file with the .Net version?
Why not use the Jupyter ipynb provider?

This is no longer an issue for .NET Interactive as we've completely removed our custom .ipynb handling, but the underlying bug is still interesting.

why would one want to...

They almost certainly wouldn't, but VS Code doesn't know the difference between .NET and Python .ipynb files and it seems to open any given file with the last-used editor, so if a user last had a .ipynb open in .NET doing .NET things then tried to open a Python .ipynb, the .NET editor would have been auto-selected, and that's obviously not correct so they would want to "Reopen With...".  The inverse is also true; if they last were editing Python notebooks then opened a .NET one, the Jupyter (Python) editor would be selected and they'd likely want to "Reopen With...".

Closing this as we don't support to open a notebook (same URI) with different serializers


Bug: openapi spec. generation does not respect Response status_code

Description
When changing the status_code in a Response object for a handler the status_code used in generation stays the default one.
Looks like the Response object status_code field is not used in generation of the openapi.json
See screenshot:

URL to code causing the issue
No response
MCVE
from litestar import Litestar, post, Response
from litestar.status_codes import HTTP_200_OK

@post("/test")
async def test() -> Response[dict[str, str]]:
    return Response(
        {"detail": "Test succesfull"},
        status_code=HTTP_200_OK,
    )

app = Litestar(route_handlers=[test])

Steps to reproduce
1. Start the app
2. Use your favorite openapi renderer
3. Execute the endpoint, returned status is 200, status in rendered openapi is 201.

Screenshots
"![SCREENSHOT_DESCRIPTION](SCREENSHOT_LINK.png)"

Logs
No response
Litestar Version
2.9.0
Platform

[X] Linux
[ ] Mac
[ ] Windows
[ ] Other (Please specify in the description above)

[!NOTE]
While we are open for sponsoring on GitHub Sponsors and
OpenCollective, we also utilize Polar.sh to engage in pledge-based sponsorship.
Check out all issues funded or available for funding on our Polar.sh dashboard

If you would like to see an issue prioritized, make a pledge towards it!
We receive the pledge once the issue is completed & verified
This, along with engagement in the community, helps us know which features are a priority to our users.

@TheZwieback as @Alc-Alc, this is not really a bug. Litestar does not know what you're doing inside your functions, so you'll have to tell it.
You can set the status code on the handler like so

@post("/test", status_code=HTTP_200_OK)
async def test() -> Response[dict[str, str]]:
    return Response(
        {"detail": "Test succesfull"},
        status_code=HTTP_200_OK,
    )

which should do what you're looking for.


Custom properties for bounding boxes in GeoJSON

Is your feature request related to a problem? Please describe.
Bounding boxes are supported by DLUP and are internally represented as Polygons. There is no easy way of reading bounding boxes from GeoJSONs because the shape function never returns a AnnotationType.BOX.
Describe the solution you'd like
Exporting and reading of annotations with AnnotationType.BOX should be possible. Adding a custom property for Feature object in the GeoJSON would be a good solution. I believe this is also suggested in the Feature Object documentation.
Describe alternatives you've considered
On this branch I have experimented with including a custom property CastToAnnotationTypeBox for bounding boxes.
Additional context
GeoJSON objects may have a property bbox. This should be kept in mind to avoid confusion.
properties can also include other features, such as colors (Issue #154) or annotation ontology.

In the definition of the Feature object it states:

A Feature object has a member with the name "properties".  The value of the properties member is an object (any JSON object or a JSON null value).

An example of this is given in the GeoJSON FeatureCollection example.
It seems that QuPath checks some properties when importing annotations to convert to their Rectangle annotation (i.e. a Polgyons with a length of 5 and and square corners). It will ignore any properties for the object that it does not recognize. This means that the suggested implementation does not interfere with importing annotations into QuPath.
AnnotationType.BOX is only used in specific cases and it is not always wanted to cast a rectangular Polgyon to this datatype. Simply converting every Polygon of length 5 with squared corners will lead to unintended behavior. Having a custom property, such as DLUP_CastToAnnotationTypeBox, will avoid these errors.

That’s a great solution, but I would still additionally add this to the constructor, as we might want to load QuPath GeoJSON objects.


Set BOM in UnicodeCSVWriter in PY2 for better csv reader compatibility

The unicode standard says "Use of a BOM is neither required nor recommended for UTF-8" - i.e., it explicitly discourages use of the BOM. There some interesting discussion here.
I get that MS Excel etc are broken in this regard and there may be a case for supporting them, but we need to make sure we don't break compatibility for other more standards-compliant CSV readers.
Also why is it only being done in Python 2? Does Python 3 add a BOM by default?

I get that MS Excel etc are broken in this regard and there may be a case for supporting them, but we need to make sure we don't break compatibility for other more standards-compliant CSV readers.
How would we achieve this? Shall we improve current test or etc?

Also why is it only being done in Python 2? Does Python 3 add a BOM by default?
Not sure, this is the question to original PR author - @SteinRobert.

Well, it's been some time since I wrote that PR.  I recall that the tests für Python 3 failed and I ended up excluding Python 3 for the BOM fix. Anyways I can't tell you why it's only Python 2. It seems like the test results of the old PR are gone, at least I can't find them.
Maybe we include an optional flag for setting the BOM. In that case everyone could decide what is the better way to write the CSV files, depending on what CSV reader the users of that Oscar installation use.
What do you think about that?

How would we achieve this? Shall we improve current test or etc?

@sasha0 the problem is it depends on client. MS Excel on Windows behaves differently from MS Excel on Mac. As far as I can tell, it is only Excel that is the problem here. To make things worse, this fix apparently will not work on Excel on Mac anyway - you have to use UTF-16 for it to work there.

Maybe we include an optional flag for setting the BOM. In that case everyone could decide what is the better way to write the CSV files, depending on what CSV reader the users of that Oscar installation use.

The issue is that this is not a site-level thing, but a user-level thing. This fix might work for someone using Excel on Windows, but won't work for someone with Excel on Mac.
Personally I think we should just stick to the unicode standard, and perhaps put a note in the documentation saying that if you have trouble with Excel, then you need to manually choose the encoding using the import wizard rather than asking it to auto-detect.

Yeah, agreed. I inclined to add note to the documentation and leave test.

To make things worse, this fix apparently will not work on Excel on Mac anyway - you have to use UTF-16 for it to work there.
We have tried that, but that didn't work for us. Only the BOM setting seemed to work.
@solarissmoke I agree its completely Excel-related and it seems that there is some weird implementation on how CSV files are read. However, one should ignore the spread and impact of Excel for business people and end-users.

Alright, after discussion with @solarissmoke we agreed that we'll initially try to re-create issue and test fix on Python2 and Python3 as well.

Closing in favor of #2306


[Analytics] [GQL Subscriptions] Mismatch request counts in API resource usage summary in Choreo Analytics

There is a mismatch between the publish and subscribe messages for the

Ideally following are the possible scenarios for events for single GQL subscription over single websocket connection with a single response along with connection_init, connection_ack and complete messages.
1 - handshake initialization
1 - connection_init (publish)
1 - conneciton_ack (subscribe)
1 - gql subscription {"id":"1", "type":"subscribe", "payload":{"query":"subscription {\n  employee{\n    employee_name\n     employee_salary\n  }\n}"}} (publish)
1 - gql subscription response {"type":"next","id":"9602a75c-5403-43b6-8529-9c4293cd7d87","payload":{"data":{"employee" : [{"employee_id":1,"employee_name":"Tom","employee_salary":"150000"}] (subscribe)
1- gql sub complete {"id":"9602a75c-5403-43b6-8529-9c4293cd7d87","type":"complete"} (publish)

Fixed with https://github.com/wso2/carbon-apimgt/pull/11880
GQL sub wesocket successful messages with no resource attached are published with wild card resource /*. Eg: (connection_init, ping, pong)
The event published for handshake and frame error messages are published without a resource.


SHODAN_API_KEY_2 is used as a key

Took me some time to figure out why shodan module wasn't working... So I added API key 1 because I only have one key, but I did not delete - SHODAN_API_KEY_2 from provider-config.yaml
For some reason, uncover decided not to use the real key and just kept trying to use SHODAN_API_KEY_2 as a key. Once I removed
- SHODAN_API_KEY_2 everything started working fine.

See https://github.com/projectdiscovery/uncover#provider-configuration, you need to ensure you are not adding invalid keys to config file as they not validated and used as it is.

When multiple keys/credentials are specified for same provider in the config file, random key will be used for each execution.


Repo description should be "Protocol buffer rules for Bazel"

See https://docs.bazel.build/versions/master/skylark/deploying.html#hosting-and-naming-rules

Done :)


Bug in async version of Zookeeper.exists()

In the async versions of the Zookeeper API, exists() erroneously throws a NoNodeException if the node does not exist. This violates the API contract which states that None should be returned.

Released version 1.7.2
https://github.com/davidledwards/zookeeper-client/tree/v1.7.2


Support for Authorization code with PKCE

According the newest spec of OAuth2 implicit flow is NOT recommended any more ("Must NOT be used")
https://tools.ietf.org/html/draft-ietf-oauth-security-topics-09#section-2.1.2
https://tools.ietf.org/html/draft-parecki-oauth-browser-based-apps-00#section-7.8
Instead "Authorization code with PKCE" is the recommended one for public clients.
Please also support this Authorization Code Flow with PKCE. Implicit flow is NOT considered as best practice any more.

Currently, it's just an early proposal and the foundation for a disussion.
The good message is: This lib follows best practices to use it in a safe way and when you combine it with OIDC you get further protections.
So the current strategy is to wait for the final version of this doucment and than decide what's next.

It would be nice to see this be implemented sooner rather than later.
This isn't a standard we're waiting on, its a BCP. The actual standards for Authorization Code Flow[1] and PKCE[2] are already well established, proposed standards.  The BCP is more relevant for determining the default grant types used by libraries, such as this.
[1] https://tools.ietf.org/html/rfc6749, https://tools.ietf.org/html/rfc8252
[2] https://tools.ietf.org/html/rfc7636

@seglberg I did an Authorization Code Flow implementation without PKCE, but unfortunately the PR was rejected.
You can have a look at https://github.com/bechhansen/angular-oauth2-oidc
I'm currently not using it so it is currently not maintained.

Yes! I'm aware of that. :+1:
Of course for maintenance reasons it would be beneficial to have it upstream. If its a matter of sponsoring some form of work (or an official fork), we at @ArroyoNetworks can look into that as well.

https://brockallen.com/2019/01/03/the-state-of-the-implicit-flow-in-oauth2/
I just wanted to add this here. I consider Brock and Dominick opinion important on this topic.

The first one is a draft; the second one experimental. Nethertheless, I'll begin to implement it soon.
@bechhansen should we merge our efforts? Back then, I decided against it b/c I wanted to keep this lib as small as possible but things are changing now with those proposals.

@manfredsteyer sure. It ought to be fairly easy to merge my stuff to the upstream.
I have still no PKCE implementation though.

@bechhansen I've noticed that you are implementing the refresh tokens as part of the Authorization Code Public Client Flow work.
During my time working with OAuth and OIDC I was always taught to keep refresh tokens away from public clients.
I'd imagine that the majority of users (hopefully everyone) would be using Authorization Code Public Client without refresh tokens and instead renewing their tokens using the silent refresh hack that we currently use with implicit flow.
I'm not sure this library should include the handling of refresh tokens as this might encourage users to implement bad practice.
What are your thoughts on this?

any updates on this?
https://www.identityserver.com/articles/change-in-recommendations-for-browser-based-applications

Any updates?


Interpolation function

A function will need to be written to interpolate the ${user.id} placeholders with actual values when the rule conditions are added to the users Session Object.  See https://casl.js.org/v6/en/cookbook/roles-with-persisted-permissions#services for example.
This function will be used to interpolate permission rules that have conditions that leverage information placeholders.
const permissions = [
  {action:”view”,subject:”Form”, condition:”user: ${objectX.id}”},
  {action:”update”,subject:”Form”, condition:”group: ${objectY.department.id}”},
]

const objectX = {
  id:  “x234assdk”
}

const objectY = {
  department: {
    id: “0823honasdf”
  }
}

fn(permissions, { objectX, objectY} => [
  {action:”view”,subject:”Form”, condition:”user: x234assdk”},
  {action:”update”,subject:”Form”, condition:”group: 0823honasdf”},
]

Here is a Gist of what I have been working on. It is working but I still need to handle possible errors. https://gist.github.com/craigzour/107cd109e13f9763c7df0b0a8a8ede58

Closing now that it was merged (https://github.com/cds-snc/platform-forms-client/pull/1135) to our https://github.com/cds-snc/platform-forms-client/tree/feature/permissions


Wheels for 15.0.4 depend on HomeBrew

Noticed this when updating the pre-commit hook for clang-format to the latest version:
clang-format.............................................................Failed
- hook id: clang-format
- exit code: 250

dyld[45432]: Library not loaded: /usr/local/opt/zstd/lib/libzstd.1.dylib
  Referenced from: <4E913C59-89FC-3A87-A878-6F1FAD905D38> /Users/ronald/.cache/pre-commit/repofwxj8esu/py_env-python3.9/lib/python3.9/site-packages/clang_format/data/bin/clang-format
  Reason: tried: '/usr/local/opt/zstd/lib/libzstd.1.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/usr/local/opt/zstd/lib/libzstd.1.dylib' (no such file), '/usr/local/opt/zstd/lib/libzstd.1.dylib' (no such file), '/usr/local/lib/libzstd.1.dylib' (no such file), '/usr/lib/libzstd.1.dylib' (no such file, not in dyld cache)

This is on a machine that does not have homebrew on it. The pre-commit hook installs the clang-format wheel from PyPI.

This is a duplicate of #56 The issue should be fixed for the newly releases v15.0.6. If the problem persist, please feel free to reopen.


Consider opened window to not block the shell

I started using ShowPSAst more often recently to help me with writing more 'intelligent' PSScriptAnalyzer rules (and mainly because I cannot think in ASTs yet).
A common scenario is to show and compare multiple scriptblocks side by side where I play around and modify the scriptblock but still want to compare the results to previous ones.
Therefore it would be useful to not block the shell when opening the external window.

That's a good idea, probably not hard to implement with a background runspace or (slower but even easier to implement) Start-Job.

I've started looking into this. Initially I'm trying to use Start-Job. I've gotten it working, I even have the job automatically remove itself when Show-Ast closes. However, a passed in scriptblock is converted to a string. So I lose the Ast.Extent which contains: File, StartLineNumber, EndLineNumber, StartOffset and EndOffset. This means I can't display the originating file details. I believe this is due to serialization of the ArgumentList parameter.
Any suggestions on a way around this?

This has been implemented.

This has been implemented.

Closed via https://github.com/lzybkr/ShowPSAst/pull/7

Closed via https://github.com/lzybkr/ShowPSAst/pull/7

Awesome. Can we get a new version published or do you want to let it go through some more manual testing first?

Awesome. Can we get a new version published or do you want to let it go through some more manual testing first?


Security alert for axios 0.19.0 (npm dependency)

🐛 Bug description
There is a security alert for axios 0.19.0, which is in npm/package-lock.json.
🤔 Expected Behavior
It should be upgraded to 0.21.1.  (Upgrading binary-install to 0.1.0 and then running npm update should fix it.)
👟 Steps to reproduce
Any package that uses wasm-pack has this warning:

🌍 Your environment
Include the relevant details of your environment.
wasm-pack version: 0.9.1

Update:  binary-install  0.0.1  →  0.1.1
"binary-install": {
  "version": "0.1.1",
  "resolved": "https://registry.npmjs.org/binary-install/-/binary-install-0.1.1.tgz",
  "integrity": "sha512-DqED0D/6LrS+BHDkKn34vhRqOGjy5gTMgvYZsGK2TpNbdPuz4h+MRlNgGv5QBRd7pWq/jylM4eKNCizgAq3kNQ==",
  "requires": {
    "axios": "^0.21.1",
    "rimraf": "^3.0.2",
    "tar": "^6.1.0"
  }
},

Update:  binary-install  0.0.1  →  0.1.1
"binary-install": {
  "version": "0.1.1",
  "resolved": "https://registry.npmjs.org/binary-install/-/binary-install-0.1.1.tgz",
  "integrity": "sha512-DqED0D/6LrS+BHDkKn34vhRqOGjy5gTMgvYZsGK2TpNbdPuz4h+MRlNgGv5QBRd7pWq/jylM4eKNCizgAq3kNQ==",
  "requires": {
    "axios": "^0.21.1",
    "rimraf": "^3.0.2",
    "tar": "^6.1.0"
  }
},

This still (somewhat urgently) needs fixing.

Yes, definitely.

Since @ashleygwilliams and @drager are listed in the project readme as maintainers, could I ask either of you if the community can have a statement on the plan for resolving this high-severity security vulnerability? Thank you very much.

Since @ashleygwilliams and @drager are listed in the project readme as maintainers, could I ask either of you if the community can have a statement on the plan for resolving this high-severity security vulnerability? Thank you very much.

I would happily merge PRs and publish new releases but unfortunately I don't have permission to publish wasm-pack nor binary-install at https://crates.io
I asked for permissions a long time ago but without success, same with the future plans for wasm-pack...

@drager does the same apply for publishing new versions to NPM?

@Keavon As far as I know, yes unfortunately...

Perhaps the first step in the right direction would be to find somebody who's willing to submit a PR. Then we can try to get them published afterwards. I will see if anybody in the Graphite community, or the broader Rust Gamedev community, is willing to help.

Wasn't there some API compatibility issue mentioned by @magcius?https://github.com/rustwasm/wasm-pack/pull/973#issuecomment-787530883

The PR is trivial and a non-issue, not least because one was submitted four months ago. The problem here is that apparently wasm-pack no longer has active developers with sufficient privileges to release further updates to this library - even for changes as simple as running npm update.

As @btzy mentioned, I don't think it is trivial because this codebase uses an old version of Axios and the security issue was not backported. The API has changed in a major version release, so this project will need to be updated to use the new API. I haven't looked closely at how hard that would be (perhaps it is actually quite simple to change a few function calls). But if we do get a PR that fixes it, then it would be a lot easier to move forward if we can get a few minutes of @ashleygwilliams's time to reassign permissions to @drager.

The axios alert is only the first problem: the root Rust crate currently has multiple audit warnings and errors, and though most of them can be solved by an update, others do not have clear and obvious fixes. For example, one of them is a dependence on failure, which was marked as unmaintained months ago. Another is relying on an outdated version of reqwest which has since moved some features into Rust's async/await framework that were previously synchronous.

Axios is the only one causing Dependabot alerts, so it is the first place to begin. Once we solve the issue of merging code and publishing new versions, it'll be easier to investigate other problems.

I don't suppose anyone has a way of contacting @ashleygwilliams IRL so we can get ownerships transferred to someone else?

She has GitHub activity as recent as one month ago. Maybe she just has notifications disabled? There's an email and Twitter handle listed on her GitHub profile, those might be good places to reach out after we have a PR. I'll add a line to the Rust Gamedev newsletter's "Requests for Contribution" section in the next publication coming in the next week.

wasm-pack appears to be unmaintained. See these issues:
https://github.com/rustwasm/wasm-pack/issues/951
https://github.com/rustwasm/team/issues/294
Ashley appears to have moved on from wasm work to Rust Foundation work, leaving this place in a bit of limbo.

As @btzy mentioned, I don't think it is trivial because this codebase uses an old version of Axios and the security issue was not backported. The API has changed in a major version release, so this project will need to be updated to use the new API. I haven't looked closely at how hard that would be (perhaps it is actually quite simple to change a few function calls). But if we do get a PR that fixes it, then it would be a lot easier to move forward if we can get a few minutes of @ashleygwilliams's time to reassign permissions to @drager.

Fortunately wasm-pack does not depend on axios. It depends on binary-install, which in turn depends on axios. And the most recent version of binary-install (a) does not use a vulnerable version of axios and (b) appears to still be compatible with how wasm-pack uses it.
Check the PR.

The axios alert is only the first problem: the root Rust crate currently has multiple audit warnings and errors, and though most of them can be solved by an update, others do not have clear and obvious fixes. For example, one of them is a dependence on failure, which was marked as unmaintained months ago. Another is relying on an outdated version of reqwest which has since moved some features into Rust's async/await framework that were previously synchronous.

Axios is the only one causing Dependabot alerts, so it is the first place to begin. Once we solve the issue of merging code and publishing new versions, it'll be easier to investigate other problems.

True, the axios issue is probably the highest priority issue to resolve, but there are other issues that will need to be dealt with, and even though they're on the Rust side, it's possible those issues could bleed over into the wasm-pack distributable - or worst case, into the WASM bundles it generates.
They will have to be confronted at some point, and the current state of wasm-pack is that a simple change of upgrading one dependency to address a public vulnerability is nearly 5 months behind, does not bode well. The good news is that there is only one hurdle to clear and that's the ownership and/or publishing permissions for crates.io and npmjs.org - or alternatively, and arguably better, is allowing the community and @drager to continue development and finding enough free time for Ashley to perform the occasional publish.

Thank you @simlay for the PR to fix this.
I went ahead and emailed @ashleygwilliams and I'll report back in a few days if I don't hear back. Everyone with Twitter accounts, please go tweet her since we'd like to get control transferred over to @drager or at the very least, get this merged and a new minor release published to the package repositories.

@Keavon Did you get a response?

@drager Not yet. I also followed up a week later (five days ago, today). I'll try and remember in a couple days to follow up again, and continue doing so every week until I get a reply. Do you have any other suggestions about ways of taking over ownership that doesn't revolve around @ashleygwilliams as the single point of failure?

@drager Not yet. I also followed up a week later (five days ago, today). I'll try and remember in a couple days to follow up again, and continue doing so every week until I get a reply. Do you have any other suggestions about ways of taking over ownership that doesn't revolve around @ashleygwilliams as the single point of failure?

I don't think there's any way to get ownership without Ashley. I wrote a thought in #1014 though, that's worth considering if do not get any answer.

@drager I see 16 people listed in https://github.com/orgs/rustwasm/people and I'm wondering if anyone else might have admin-level privileges over the org, but isn't listed under this particular repo's user list. Maybe could someone with org-level admin privileges intervene?

@drager I see 16 people listed in https://github.com/orgs/rustwasm/people and I'm wondering if anyone else might have admin-level privileges over the org, but isn't listed under this particular repo's user list. Maybe could someone with org-level admin privileges intervene?

IIRC @ashleygwilliams is the only owner of the crates.io package. See Owners here: https://crates.io/crates/wasm-pack

Let's try and tackle one step at a time. If we can get back control of the GitHub repo, we might be able to see if the crates.io folks have a way to petition for control of publishing due to an owner who has disappeared off the face of the earth.

Let's try and tackle one step at a time. If we can get back control of the GitHub repo, we might be able to see if the crates.io folks have a way to petition for control of publishing due to an owner who has disappeared off the face of the earth.

@drager has already stated that he has the ability to accept pull requests. It's not necessary to transfer ownership of this repository for the time being.
drager said it and I'll repeat it: the problem is crates.io and publishing new versions there. Not this repository here on GitHub.
To the issue, crates.io does have a policy for transferring ownership:

If someone wants to take over a package, and the previous owner agrees, the existing maintainer can add them as an owner, and the new maintainer can remove them. If necessary, the team may reach out to inactive maintainers and help mediate the process of ownership transfer.

They may have better luck at contacting Ashley. If not, they may be willing to transfer ownership to drager given that he is a maintainer here.
npmjs.com would also be nice, since wasm-pack is published there too, but they do not handle abandonment.

We are not currently accepting dispute requests to "adopt an abandoned package" or "Report Squatting" as we re-evaluate and update the overall dispute process.

Transferring ownership is a large step to take and one that should not be taken lightly, however the only other option I see is to republish this repo under a new name - or perhaps drager's fork, if crates.io doesn't allow a second package under the same source repo.

@drager has already stated that he has the ability to accept pull requests. It's not necessary to transfer ownership of this repository for the time being.

drager said it and I'll repeat it: the problem is crates.io and publishing new versions there. Not this repository here on GitHub.

Oh I see, thank you for clarifying that, I think I misunderstood the situation. If so, can @drager go ahead and merge #1012 right now?
It is possible that npm may be willing to transfer from one GitHub maintainer to another when the one maintainer listed on npm has disappeared. I don't think it's necessarily accurate to call that abandonment, and due to the security vulnerability they may be willing to work with it. Alternatively, we just publish a second package under this official repo (not a fork).

@drager has already stated that he has the ability to accept pull requests. It's not necessary to transfer ownership of this repository for the time being.

drager said it and I'll repeat it: the problem is crates.io and publishing new versions there. Not this repository here on GitHub.

Oh I see, thank you for clarifying that, I think I misunderstood the situation. If so, can @drager go ahead and merge #1012 right now?
It is possible that npm may be willing to transfer from one GitHub maintainer to another when the one maintainer listed on npm has disappeared. I don't think it's necessarily accurate to call that abandonment, and due to the security vulnerability they may be willing to work with it. Alternatively, we just publish a second package under this official repo (not a fork).

Sorry for being unclear. Yes, I can go ahead and merge PRs in this repo right now. Also yes, no need for any fork.

Update: I now got publishing rights for wasm-pack at crates.io! Thank you @ashleygwilliams!

@drager Were you able able to get publishing rights for npm? Now that the patch is merged, are you able to submit a release to crates.io and npm? Thanks so much for making this all happen!

@drager Were you able able to get publishing rights for npm? Now that the patch is merged, are you able to submit a release to crates.io and npm? Thanks so much for making this all happen!

I was not given rights for npm nor binary-install on crates.io...

@drager Hmm. That's unfortunate about npm, although I guess a fork is possible— were you ever in touch with @ashleygwilliams (and could therefore reply) or did your publishing privileges change without any words of communication?
As for binary-install, hasn't that package already been patched and the whole purpose of merging the PR was to upgrade to the new version of it? Excuse me if my memory has these details tangled.

@drager Hmm. That's unfortunate about npm, although I guess a fork is possible— were you ever in touch with @ashleygwilliams (and could therefore reply) or did your publishing privileges change without any words of communication?
As for binary-install, hasn't that package already been patched and the whole purpose of merging the PR was to upgrade to the new version of it? Excuse me if my memory has these details tangled.

Agree... I was not in touch with her. My privileges changed without any communication.
Yes, that's right about binary-install. I'm just thinking ahead, if we want to make changes to it and publish a new version, that's not possible right now...

@drager I had assumed you had gotten in touch, thanks for clarifying. I will follow up my emails with a thank you and a request to go one step further to complete the job by adding you on npm. I realize the accounts may be different from GitHub and maybe that wasn't a quick thing to do without replying to request additional information. Do you have an npm account yet and could you give me the exact name so I can clearly pass that along?
Regarding binary-install, I believe that's a totally separate project and I have no reason to believe it's abandoned (repo link). I might be misunderstanding you so please set me straight.

@drager I had assumed you had gotten in touch, thanks for clarifying. I will follow up my emails with a thank you and a request to go one step further to complete the job by adding you on npm. I realize the accounts may be different from GitHub and maybe that wasn't a quick thing to do without replying to request additional information. Do you have an npm account yet and could you give me the exact name so I can clearly pass that along?
Regarding binary-install, I believe that's a totally separate project and I have no reason to believe it's abandoned (repo link). I might be misunderstanding you so please set me straight.

Sorry for being unclear 😅 Yes, here it is: https://www.npmjs.com/~drager
I was referring to this binary-install actually: https://github.com/rustwasm/binary-install

Is rights on binary-install necessary? There are two parts to wasm-pack and both are located in this repo: the Rust crate which does all the work (./src), and the NPM package which essentially bootstraps it (./npm).

Is having rights on binary-install necessary? There are two parts to wasm-pack and both are located in this repo: the Rust crate which does all the work (./src), and the NPM package which essentially bootstraps it (./npm).

Not the npm package binary-install, no. But in the long run we want to be able to update and publish this package: https://github.com/rustwasm/wasm-pack/blob/master/Cargo.toml#L36 which is this: https://github.com/rustwasm/binary-install

I didn't realize there are two unrelated binary-install libraries! To be clear, this axios security alert came through a binary-install dependency which PR #1012 upgraded, but which binary-install? I assumed it was the one I linked to, since I didn't know about the one related to this project. I also don't see any links to that one on npm, is it on npm or only crates.io or nothing? I'm now confused how it fits into the equation.

I didn't realize there are two unrelated binary-install libraries! To be clear, this axios security alert came through a binary-install dependency which PR #1012 upgraded, but which binary-install? I assumed it was the one I linked to, since I didn't know about the one related to this project. I also don't see any links to that one on npm, is it on npm or only crates.io or nothing? I'm now confused how it fits into the equation.

Hehe yes, it's quite confusing. But the rust one that I linked was not updated, nor is published to npm. The rust one does not depend on axios, and does not have that security issue.

Maybe I am confused too, but the issue it not closed right? There is still no way to update to a released version, which fixes this issue.

Maybe I am confused too, but the issue it not closed right? There is still no way to update to a released version, which fixes this issue.

This issue actually got auto closed when I merged #1012

Maybe I am confused too, but the issue it not closed right? There is still no way to update to a released version, which fixes this issue.

This issue actually got auto closed when I merged #1012

So it should be re-opened, right?

New versions published:
https://crates.io/crates/wasm-pack/0.10.0
https://www.npmjs.com/package/wasm-pack/v/0.10.0

Thank you @drager and @ashleygwilliams! So glad this is finally resolved 🥳.


added the std.exception.Descendant template

mixin(std.exception.Descendant!("SampleException")) creates a subclass of Exception, producing this code:
class SampleException : Exception {
    this(string m = "", string f = __FILE__, size_t l = __LINE__, Throwable t = null) {
        super(m, f, l, t);
    }
}

I've thought about adding something like this but came to the conclusion that it wasn't worth it for two reasons:

You can't have ddoc on the exception type, so it doesn't end up in your ddoc documentation.
Ideally, exceptions would have more information than this. While it's better to have a derived exception structurally identical to Exception rather than just using Exception, because the type gives you additional information, it's far better for the derived type to have additional information. And you can't do that with a mixin like this. So, arguably, it's promoting bad code.

Also, if you have a mixin like this, you really should have Exception's other constructor as well (which admitedly, a number of Phobos exception types are missing):
 this(string msg, Throwable next, string file = __FILE__, size_t line = __LINE__)
{
    super(msg, file, line, next);
}

And I really don't think that Descendant is a particularly good name either. It doesn't indicate in any way shape or form that it's generating an exception. Something like genStdException would make more sense, but again, I don't really think that this is ultimately a good idea.

I agree and think a better solution is a template mixin that generates the two standard constructors, which is where the real boilerplate is at. However, I don't think that's possible due to bugs or limitations with template mixins at the moment. Still, even a string mixin like this one which only adds the constructors would probably be more appropriate.

As JakobOvrum suggests, if we're going to do this, we should probably create a function which generates a string to mixin in the 2 standard constructors rather than have one to generate the whole exception type. That way, we provide a way to reduce boilerplate code but avoid encouraging people to simply create new exception classes with no new data. Those exceptions have their place, but the mixin would probably be more useful with just the constructors, since it could be also be used at least some of the time in exception types which do include other member variables. It also has the advantage of making it possible to have ddoc comments on the exception itself, since it'll just be the constructors which are being mixed in rather than the whole type.


f"Something went wrong while pulling {image}, see the logs above for more information")

Hi All
im getting the following error. Seems to be somthing with Docker and read write permissions
PS D:\LeanCLI> lean backtest 'Crypto DonChan' --verbose --> GET https://raw.githubusercontent.com/QuantConnect/lean-cli/master/announcements.json Error response from daemon: error creating temporary lease: write /var/lib/desktop-containerd/daemon/io.containerd.metadata.v1.bolt/meta.db: read-only file system: unknown Traceback (most recent call last):   File "d:\python3.6.8\lib\site-packages\lean\main.py", line 96, in main     lean.main(standalone_mode=False)   File "d:\python3.6.8\lib\site-packages\click\core.py", line 782, in main     rv = self.invoke(ctx)     return _process_result(sub_ctx.command.invoke(sub_ctx))   File "d:\python3.6.8\lib\site-packages\lean\click.py", line 114, in invoke     result = super().invoke(ctx)   File "d:\python3.6.8\lib\site-packages\click\core.py", line 1066, in invoke     return ctx.invoke(self.callback, **ctx.params)   File "d:\python3.6.8\lib\site-packages\click\core.py", line 610, in invoke     return callback(*args, **kwargs)   File "d:\python3.6.8\lib\site-packages\lean\commands\backtest.py", line 342, in backtest     docker_manager.pull_image(engine_image)   File "d:\python3.6.8\lib\site-packages\lean\components\docker\docker_manager.py", line 70, in pull_image     f"Something went wrong while pulling {image}, see the logs above for more information") RuntimeError: Something went wrong while pulling quantconnect/lean:latest, see the logs above for more information Error: Something went wrong while pulling quantconnect/lean:latest, see the logs above for more information

Hmm, I've never seen that error before, but going off of Google it seems like this is a disk space issue. Can you check whether you have ~20GB of free space to download the LEAN Docker images to?


[Function Request] Record::"Transfer Header" - Function GetHideValidationDialog

As HideValidationDialog is protected but is useful and in our case needed, we would like to have a function in table "Transfer Header" to call the state of HideValidationDialog.
procedure GetHideValidationDialog(): Boolean
begin
  exit(HideValidationDialog);
end;

Already added


Task/721 make contribution admin to see all items

Description
Added detail pages in catalog to show items separately based on user privilege.
Fixes #(add issue number here and remove parentheses)
Review Time Estimate
Please give your idea of how soon this pull request needs to be reviewed by selecting one of the options below. This can be based on the criticality of the issue at hand and/or other relevant factors.

[ ] Immediately
[x] Within a week
[ ] When possible

Type of changes
Please select a relevant option:

[ ] Bug fix (non-breaking change which fixes an issue).
[x] New feature (non-breaking change which adds functionality).
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected).
[ ] Other (any another change that does not fall in one of the above categories.)

Checklist:
Please select all applicable options:

[x] I have signed the Rokwire Contributor License Agreement (CLA). (Any contributor who is not an employee of the University of Illinois whose official duties include contributing to the Rokwire software, or who is not paid by the Rokwire project, needs to sign the CLA before their contribution can be accepted.)
[x] I have updated the CHANGELOG.
[x] I have read the Contributor Guidelines.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[ ] My change requires updating the documentation.
[ ] I have made necessary changes to the documentation.
[ ] I have added tests related to my changes.
[ ] My changes generate no new warnings.
[ ] New and existing unit tests pass locally with my changes.
[ ] Any dependent changes have been merged and published in downstream modules.

Please resolve the merge conflicts here. Thanks.

Please resolve the merge conflicts here. Thanks.

resolved

Please resolve the merge conflicts when you get a chance. Please put the most recent change at the end of the section. Thank you.

Please resolve the merge conflicts here. Thanks.

resolved


Add some documentation on the multi cluster setup

Signed-off-by: Florian Froese<EMAIL_ADDRESS>

It feels like with some minor work on the Helm chart we can reduce the text here significantly. Would you like to discuss and help with that?

I completely agree! This should be part of the helm chart! I'm happy to contribute that part. I'll work on that once the other PRs for the helm chart are merged.


Marker clusterer Uncaught ReferenceError: MarkerClusterer is not defined

Hi,
Thank you for your great job on the module.
I'm testing the marker clusterer but i got the exception when instantiating the MarkerClusterer Object.
I have installed the module via bower. and included   ```

Is MarkerClusterer not shipped ?

Thanks in advance,

No, MarkerClusterer is not officially supported by Google and not by this module either.

Thanks for your prompt answer your module is :+1:


.NET 5 Preview 8

Release Notes
Please report any issues you find with .NET 5, either responding to this issue, creating a new issue or creating a new issue in one of the following repos:

dotnet/aspnetcore - for ASP.NET Core questions
dotnet/efcore - for Entity Framework Core questions
dotnet/sdk - for CLI tools and questions
dotnet/runtime - for runtime, API, or installer issues and questions
dotnet/winforms - for WinForms issues
dotnet/wpf - for WPF issues
nuget/home - for NuGet questions and issues

Known Issues
If there are any issues with the August 2020 release we will track them here and check issues off as they're resolved. See the linked issues for details on progress and resolution details.

[x] 5.0.0-preview.8 in releases.json lists dotnet-runtime-win-arm64.exe RID as win-x86 rather than win-arm64 https://github.com/dotnet/core/issues/5118

[x] Release Pages and dot.net missing Arm64 entries for binaries and installer https://github.com/dotnet/runtime/issues/36699#issuecomment-680906091 - Added missing Arm64 binary link to release page https://github.com/dotnet/core/pull/5121 and fixed on dot.net

[x] WCF packages were not pushed to nuget.org - This was resolved and the packages were updated

After the preview 6, if you build an standalone executable for Linux ARM, and use the produce single file option, it will give segmentation fault at the point on your code you instantiate a new TcpListener class.
If you use the TRIM within the produce single file, it misses some assemblies that are used for webclient (given the same settings from before).

Installation failing on Ubuntu 20.04 when using install-dotnet-preview.sh, with error message: E: Packages were downgraded and -y was used without --allow-downgrades..
I have tried removing all previous versions, including stable 3.1. Also tried installing using Snap and the binary. These fail too.

@bldevuid798 I was able to install and run on Ubuntu 20.04 with SDK Version: 5.0.100-preview.8.20417.9

@rbhanda Okay, thanks for that info. I'll investigate some more.

Installation failing on Ubuntu 20.04 when using install-dotnet-preview.sh, with error message: E: Packages were downgraded and -y was used without --allow-downgrades..

This has been a problem with this install method for multiple 5.0 preview releases. I posted a repro command at https://github.com/dotnet/core/issues/4542#issuecomment-664475585.

On a subsequent install, I first purged netstandard-targeting-pack-2.1. The install completed without any error, but the app is not running.

@bldevuid798 please feel free to give some details about what's going wrong in a new issue, or here. I only linked that issue because it matches the error message you posted.

@dagood Thanks. You were right, the error message that I posted wasn't necessarily the culprit and can be ignored (or in my case I simply purged the netstandard-targeting-pack-2.1 .deb and then performed the install without any errors). I have a reverse proxy setup and it turns out that Apache was up but Kestrel down. My logs showed Unhandled exception. System.PlatformNotSupportedException: EventLog access is not supported on this platform. I've now removed the EventLog Logging provider and I'm officially on .Net 5 Preview 8 and everything is working fine once again.

Unable to publish .net 5 preview 8 Blazor Webassembly App (Asp.Net Core Hosted) . Nuget cannot resolve dependencies.
Error Message while publishing self contained app:
Failed to download package 'Microsoft.NETCore.App.Runtime.win-x<IP_ADDRESS>-preview.8.20407.11' from 'https://api.nuget.org/v3-flatcontainer/microsoft.netcore.app.runtime.win-x86/5.0.0-preview.8.20407.11/microsoft.netcore.app.runtime.win-x<IP_ADDRESS>-preview.8.20407.11.nupkg'.
The download of 'https://api.nuget.org/v3-flatcontainer/microsoft.netcore.app.runtime.win-x86/5.0.0-preview.8.20407.11/microsoft.netcore.app.runtime.win-x<IP_ADDRESS>-preview.8.20407.11.nupkg' timed out because no data was received for 60000ms.
Exception of type 'System.TimeoutException' was thrown.

@UserIsAmitHasan any way to contact you?


citra: nightly 1963 -> 2020, canary 2573 -> 2668

Description of changes
Vulkan's here!
One problem, though: the SDL frontend segfaults.
If that can't be solved, it will have to be disabled.
Another thing: upstream switched to Clang for performance reasons. However, if I try that here, LTO doesn't work.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

I found out that the SDL backend crash isn't a regression, and it's also a problem upstream: https://github.com/citra-emu/citra/issues/7113
I'll undraft this when that's solved.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2972


Add support for null Activity

Allow null Activity when the Compiler has multiple Activities.
This is mainly for use by puppets and animations in order to suspend the face animation.
Closes #4

If there is such an Activity present, then it prevents an optimization that checks whether a state can be accessed by all activities. Is this desired?


Force download via AJAX

Hi,
I am wondering why the file won't download during an ajax call, in my component ;
public function onExportPDF(){
  return PDF::loadTemplate('renatio::invoice')->download();
}

The response is always returned as a string - Response headers ;
Cache-Control:no-cache
Connection:Keep-Alive
Content-Disposition:attachment; filename="document.pdf"
Content-Type:application/pdf
Date:Mon, 17 Jul 2017 02:54:26 GMT
Keep-Alive:timeout=5, max=100
Server:Apache/2.4.25 (Win32) OpenSSL/1.0.2j PHP/7.1.4
Transfer-Encoding:chunked
X-Powered-By:PHP/7.1.4

Hi,
check this topic: https://github.com/mplodowski/DynamicPDF/issues/29

I end up create an export page and component to make it work then in onRun method  added;
if( $this->export ){
   return PDF::loadTemplate('renatio::invoice')->download();
}


Postcode search ignores space

Enabling users to search regardless of space characters in strings

As before - remote running of integration tests is borked on heroku:


update 4.3.1

☆ Ydata-profiling Update 4.3.1 (PKG-2133)☆
Jira Ticket
Upstream
Dependencies
Changes

Updated version number and sha256
Updated pinnings and dependencies

@Arishamays1 can you fix the links in the PR description please? They point to python-pyproject-metadata instead of ydata-profiling.

@Arishamays1 can you fix the links in the PR description please? They point to python-pyproject-metadata instead of ydata-profiling.

Fixed


#11341: Replace tt_lib in bert_tiny, distilbert

Ticket
Link to Github Issue #11341
Master Issue #11240
Problem description
Replace tt_lib with ttnn in models/experimental/bert_tiny, models/experimental/distilbert
Checklist

[x] Post commit CI passes
[ ] Model regression CI testing passes (if applicable)
[x] New/Existing tests provide coverage for changes

run nightly fd pipeline


[Bug] Added AWS Account stuck in "Pending"

Describe the bug
The status of the new hosting AWS Account is stuck in the "Pending" state, with the spinning wheel on the UI. The CloudFormation stack shows "CREATE_COMPLETE"
Expected behavior
Expecting to be able to Add an AWS account to host workspaces.
Versions (please complete the following information):

Version 6.0.0

Additional context
Adding an AWS account (hosting account the same as the main account in this implementation) and the stack was created successfully. On the UI, the status of the new hosting AWS Account is stuck in the "Pending" state, with the spinning wheel. I tried once again with the same result. I cannot terminate the attempted additions of the AWS account, so they are left there on the UI in the pending state. I deleted the stack from first attempt, and the status remains the same. Click the button 'Refresh Account Status" did not change the status.

Corrected the "External ID" and this resolved the issue.


Cake Build Unable to Restore 'Microsoft.CodeAnalysis.Scripting' version '1.0.0-rc2'

What You Are Seeing?
When Cake attempts to restore packages it fails stating it is unable to find 'Microsoft.CodeAnalysis.Scripting' version '1.0.0-rc2'
What is Expected?
Cake to restore packages successfully
What version of Cake are you using?
0.17.0 but also seen using 0.19.4
Are you running on a 32 or 64 bit system?
64bit
What environment are you running on?  Windows? Linux? Mac?
Windows
How Did You Get This To Happen? (Steps to Reproduce)
Run this following command
.\build.ps1 -Experimental -dryrun -Verbosity Diagnostic
Attempted Fixes
Updated cake to 0.19.4 in tools\packages.config
Add reference to Microsoft.CodeAnalysis.Scripting 1.1.0 in tools\packages.config
  <package id="Microsoft.CodeAnalysis.Scripting" version="1.1.0" />

Output Log
C:\Work Files\Development\Product\Build> .\build.ps1 -Experimental -dryrun -Verbosity Diagnostic
Preparing to run build script...
& "C:\Work Files\Development\Product\Build\tools\Cake\Cake.exe" "build.cake" -target="Default" -configuration="Release" -verbosity="Diagnostic"  -dryrun -experimental
Running build script...
Module directory does not exist.
Analyzing build script...
Analyzing C:/Work Files/Development/Product/Build/build.cake...
Analyzing C:/Work Files/Development/Product/Build/project.cake...
Analyzing C:/Work Files/Development/Product/Build/mobilelocations.cake...
Processing build script...
Installing addins...
Creating directory C:/Work Files/Development/Product/Build/tools/Addins
Installing NuGet package Cake.MSBuildTask...
Executing: "C:/Work Files/Development/Product/Build/tools/nuget.exe" install "Cake.MSBuildTask" -OutputDirectory "C:/Work Files/Development/Product/Build/tools/Addins" -ExcludeVersion -NonInteractive -NoCache
The addin Cake.MSBuildTask will reference Cake.MSBuildTask.dll.
The addin Cake.MSBuildTask will reference Microsoft.Build.Framework.dll.
The addin Cake.MSBuildTask will reference Microsoft.Build.Utilities.v4.0.dll.
Installing NuGet package Cake.FileHelpers...
Executing: "C:/Work Files/Development/Product/Build/tools/nuget.exe" install "Cake.FileHelpers" -OutputDirectory "C:/Work Files/Development/Product/Build/tools/Addins" -ExcludeVersion -NonInteractive -NoCache
The addin Cake.FileHelpers will reference Cake.FileHelpers.dll.
Creating script session...
Using prerelease build of Roslyn.
Downloading and installing Roslyn (experimental)...
Installing packages (using https://packages.nuget.org/api/v2)...
Downloading package Microsoft.CodeAnalysis.Scripting (1.0.0-rc2)...
Error: System.InvalidOperationException: An error has occurred. ---> System.Data.Services.Client.DataServiceQueryException: An error occurred while processing this request. ---> System.Data.Services.Client.DataServiceClientException: <?xml version="1.0" encoding="utf-8"?><m:error xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"><m:code /><m:message xml:lang="en-US">An error has occurred.</m:message></m:error>
   at System.Data.Services.Client.QueryResult.Execute()
   at System.Data.Services.Client.DataServiceRequest.Execute[TElement](DataServiceContext context, QueryComponents queryComponents)
   --- End of inner exception stack trace ---
   at System.Data.Services.Client.DataServiceRequest.Execute[TElement](DataServiceContext context, QueryComponents queryComponents)
   at NuGet.DataServiceQueryWrapper`1.Execute[TResult](Func`1 action)
   --- End of inner exception stack trace ---
   at NuGet.DataServiceQueryWrapper`1.Execute[TResult](Func`1 action)
   at NuGet.DataServiceQueryWrapper`1.<GetAll>d__7.MoveNext()
   at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
   at NuGet.PackageRepositoryExtensions.ResolveDependencyCore(IPackageRepository repository, PackageDependency dependency, IPackageConstraintProvider constraintProvider, Boolean allowPrereleaseVersions, Boolean preferListedPackages, DependencyVersion dependencyVersion)
   at NuGet.InstallWalker.ResolveDependency(PackageDependency dependency)
   at NuGet.PackageWalker.Walk(IPackage package)
   at NuGet.PackageWalker.Walk(IPackage package)
   at NuGet.PackageWalker.Walk(IPackage package)
   at NuGet.InstallWalker.ResolveOperations(IPackage package)
   at NuGet.PackageManager.Execute(IPackage package, IPackageOperationResolver resolver)
   at NuGet.PackageManager.InstallPackage(IPackage package, Boolean ignoreDependencies, Boolean allowPrereleaseVersions)
   at Cake.Scripting.Roslyn.Nightly.RoslynNightlyScriptSessionFactory.Install(SemanticVersion version)
   at Cake.Scripting.Roslyn.Nightly.RoslynNightlyScriptSessionFactory.CreateSession(IScriptHost host)
   at Cake.Scripting.Roslyn.RoslynScriptEngine.CreateSession(IScriptHost host, IDictionary`2 arguments)
   at Cake.Core.Scripting.ScriptRunner.Run(IScriptHost host, FilePath scriptPath, IDictionary`2 arguments)
   at Cake.Commands.DryRunCommand.Execute(CakeOptions options)
   at Cake.CakeApplication.Run(CakeOptions options)
   at Cake.Program.Main()

Duplicate of:
https://github.com/cake-build/cake/issues/1583
https://github.com/cake-build/cake/issues/1582
This is an issue with NuGet.org

@martpendle seems like NuGet is having lots of issues today.  I suspect what you are seeing is a symptom of that.

@gep13 Thanks, didn't even think of that being an issue, the unlisted package threw me off on a different path


Partial Dimension.rs

// assert!(self.height.Zero::is_zero())
doesnt work now :(

You have to put #[test] on all unit tests, otherwise they aren't run automatically (and end up as unused functions)

Documentation should start uppercase. So this:
/// This is green
fn green() {}

rather than
/// this is green
fn green() {}


Handle when texts array has an empty array

Right now we crash with an empty texts array with the combo. This fixes this.

Thanks!


WIP: Use globby gitignore handling

closes #236
failing test cases indicate regression in globby gitignore handling Just faulty usage of globby

ToDo

[x] expose getGitIgnoreFilter from globby: globby#56
[x] investigate failing test cases
[x] remove all remnants of lib/gitignore

Generally looks good, but some of the tests seems to be failing.

Will pick this up again in the course of the next two weeks


Cant get the horizontalCalendar.getSelectedDate()

It shows always error while calling horizontalCalendar.getSelectedDate();

Hello @ibrahim-appgodz ,
I need to know the kind of error you are receiving before I can help you!
Also please post some code snippets, or the steps you made to reproduce this error.
Thanks.

no respone!

Sorry, I deleted the stack traces of the error. But it was still there. Please fix it. So that we can use it.
Thanks and Regards,
Mohamed Ibrahim N
From: Mulham Raee<EMAIL_ADDRESS>Sent: Tuesday, March 21, 2017 4:14 AM
To: Mulham-Raee/Horizontal-Calendar<EMAIL_ADDRESS>Cc: Mohamed Ibrahim<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Mulham-Raee/Horizontal-Calendar] Cant get the horizontalCalendar.getSelectedDate() (#5)
no respone!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/Mulham-Raee/Horizontal-Calendar/issues/5#issuecomment-287921316 , or mute the thread https://github.com/notifications/unsubscribe-auth/AS3CJg5JDQt3QHplcT4RL2_wQCrmNDF6ks5rnwE1gaJpZM4L0NZQ .

Dear Ibrahim,
I can't really help you of fix anything until you provide me with the code you are using at least., so I can trace the origin of the problem.
Regards

Ok I will try to get back to you when I get the Stack Trace.
Kind Regards,
Mohamed Ibrahim N
From: Mulham Raee<EMAIL_ADDRESS>Sent: Wednesday, March 22, 2017 1:32 AM
To: Mulham-Raee/Horizontal-Calendar<EMAIL_ADDRESS>Cc: Mohamed Ibrahim<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Mulham-Raee/Horizontal-Calendar] Cant get the horizontalCalendar.getSelectedDate() (#5)
Dear Ibrahim,
I can't really help you of fix anything until you provide me with the code you are using at least., so I can trace the origin of the problem.
Regards
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/Mulham-Raee/Horizontal-Calendar/issues/5#issuecomment-288200749 , or mute the thread https://github.com/notifications/unsubscribe-auth/AS3CJtVcU-r2LUjpIF4qe2yqVdxe8j1Sks5roCyygaJpZM4L0NZQ .


Help

I don't find (line 76 in index.html of the demo: "images : photos,") where is declared variable "photos" ?

photos are the array of images which you'd like to show. For help, you can just view the source of http://nitinhayaran.github.io/Justified.js/demo/index.html


stripe integration

hey guys!
Any ideas on which stripe bundle can we use with cocorico? Something with really great features.

Hi,
For now cocorico have no bundle for Stripe. We hope it will coming soon.


Swift 4 Conversion

Pod install using latest CocoaPods version
Conform to Apple style guide to move from (Void) to ()
Annotate Obj-C dynamic methods
New associated type Element added to Collection type
Integer protocol has been removed
IntMax type alias has been removed
Some types conformances have been built into the types
Other misc changes

Some protocols and code seem to become obsolete.. For example, Mathable. We might want to reconsider the use cases for those code.

https://github.com/apple/swift-evolution/blob/master/proposals/0104-improved-integers.md

Need to find a way to build this PR using Xcode 9.


DAWN-469 ⁃ Standardizing Currencies

Standard Currencies
In order to facilitate a wealth of contracts, interfaces, wallets, and tools it makes sense for us to have a standardized framework for implementing a currency.  The base EOS.IO tokens should implement this standard.
Goals

Standard identification of a currency

which allows for a single contract to operate multiple currencies
which optionally allows guarantee of globally unique "ticker"

Standardized way of constructing a transfer from an account to another account

This may enforce serialization formats

Standardized notifications of to/from when transfer s happen
Standardized access of balances for an account

This may enforce serialization formats

Standardized access to meta-information about a currency (perhaps in global registry)

This may enforce serialization formats

Implementation Details
There is a reference implementation of a currency which can be used to define the spec here.
Sub Tasks

[ ] Derive standard document
[ ] apply standard to the base chain tokens

It should be noted that ERC20 token standard has a critical issue. This led to the loss of millions of dollars for the Ethereum ecosystem. You can read more about the problem here: https://gist.github.com/Dexaran/ddb3e89fe64bf2e06ed15fbd5679bd20
I strongly recommend to avoid using the ERC20 standard as a prototype model when developing the standard for EOS digital assets.

Implemented as eosio.token.


⚠ Samsung has degraded performance

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

HTTP code: 200
Response time: 3014 ms

Resolved: Samsung performance has improved in df90d9e.


No file for error Composable function in Native Compose (Darwin Compose)

JetBrains Compose : 1.2.1
Kotlin : 1.7.20
I tried to use JetBrains Compose in iOS.
I export Compose UI like this
fun createExampleViewController(
    rootComponent: RootComponent
): UIViewController = Application("Example") {
    ExampleApp(rootComponent)
}

@Composable
@OptIn(ExperimentalDecomposeApi::class)
fun ExampleApp(rootComponent: RootComponent) {
    Scaffold(
        bottomBar = {
            BottomBar(rootComponent)
        }
    ) {
        Children(rootComponent.childStack) {
            when (val child = it.instance) {
                is RootComponent.Child.Item -> ItemScreen(child.component)
                is RootComponent.Child.Gallery -> GalleryScreen(child.component)
                is RootComponent.Child.Empty -> Spacer(Modifier.fillMaxSize())
            }
        }
    }
}

However, if I execute assembleExampleXCFramework, an error occurs in the linkDebugFrameworkIosArm64 task.
java.lang.IllegalStateException: No file for com.example.presentation.root/ExampleApp|-5619709659753561405[0]
I don't know what I missed to implement.
My Gradle file is like this
import org.jetbrains.kotlin.gradle.plugin.mpp.apple.XCFramework

@Suppress("DSL_SCOPE_VIOLATION")
plugins {
	alias(libs.plugins.android.library)
	alias(libs.plugins.jetbrains.compose)
	alias(libs.plugins.kotlin.multiplatform)
	id("kotlin-parcelize")
}

kotlin {
	val xcFramework = XCFramework("Example")
	ios {
		binaries.framework {
			isStatic = true
			baseName = "Example"
			xcFramework.add(this)
		}
	}
	android()

	sourceSets.commonMain {
		dependencies {
			implementation(projects.domain)
			implementation(projects.features.item)
			implementation(projects.features.gallery)

			implementation(compose.foundation)
			implementation(compose.material)

			implementation(libs.koin)
			implementation(libs.kotlin.coroutines)
			implementation(libs.bundles.decompose)
		}
	}
}

It works well in android. If anyone knows the cause, I'd appreciate it if you could help me.

I found the same issue #2346

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


training 'Num examples' is not equal to the size of the dataset

Hi,
I’m trying to understand the reported 'Num examples' during the training process.
I am fine-tuning an LLM on my custom dataset, which contains 348,979 chunks of text. However, during training (executing llamafactory-cli train model_pt.yaml), the log shows the following:
09/04/2024 15:03:43 - INFO - llamafactory.data.loader - Loading dataset /DATA/train/raw/data_raw.json...
Converting format of dataset (num_proc=16): 100%|███████████████████████████████████████████████████████████████████████████████████████████████████████| 348979/348979 [00:01<00:00, 188087.31 examples/s]
09/04/2024 15:03:46 - INFO - llamafactory.data.loader - Loading dataset /DATA/train/raw/data_raw.json...
09/04/2024 15:03:46 - INFO - llamafactory.data.loader - Loading dataset /DATA/train/raw/data_raw.json...
09/04/2024 15:03:46 - INFO - llamafactory.data.loader - Loading dataset /DATA/train/raw/data_raw.json...
Running tokenizer on dataset (num_proc=16): 100%|████████████████████████████████████████████████████████████████████████████████████████████████████████| 348979/348979 [00:08<00:00, 39427.21 examples/s]
...
...
[INFO|trainer.py:2134] 2024-09-04 15:04:18,470 >> ***** Running training *****
[INFO|trainer.py:2135] 2024-09-04 15:04:18,470 >>   Num examples = 137,591
[INFO|trainer.py:2136] 2024-09-04 15:04:18,470 >>   Num Epochs = 3
[INFO|trainer.py:2137] 2024-09-04 15:04:18,470 >>   Instantaneous batch size per device = 4
[INFO|trainer.py:2140] 2024-09-04 15:04:18,470 >>   Total train batch size (w. parallel, distributed & accumulation) = 64
[INFO|trainer.py:2141] 2024-09-04 15:04:18,470 >>   Gradient Accumulation steps = 4
[INFO|trainer.py:2142] 2024-09-04 15:04:18,470 >>   Total optimization steps = 6,450
[INFO|trainer.py:2143] 2024-09-04 15:04:18,476 >>   Number of trainable parameters = 167,772,160
I expected to see 348,979 examples reported during training, but only 137,591 are indicated. Could you help me understand why this discrepancy occurs?
Additionally, since my dataset is relatively small, I want to reduce the number of examples used for evaluation. However, changing the 'val_size' in the configuration doesn't seem to have a significant effect.
Here is the configuration file I’m using:
model_name_or_path: meta-llama/Meta-Llama-3-8B
quantization_method: bitsandbytes
quantization_bit: 4

### method
stage: pt
do_train: true
finetuning_type: lora
lora_target: all
lora_rank: 64
lora_alpha: 16
lora_dropout: 0.1
use_adam_mini: true
#flash_attn: fa2
enable_liger_kernel: true

### dataset
dataset_dir: /CODE/FT/LLaMA-Factory/data
dataset: my_data
cutoff_len: 512
#max_samples: 1000
overwrite_cache: true
preprocessing_num_workers: 16

### output
output_dir: /MODELS/base_models/local_models/FT/PT
logging_steps: 10
save_steps: 500
plot_loss: true
overwrite_output_dir: true

### train
per_device_train_batch_size: 4
gradient_accumulation_steps: 4
learning_rate: 2.0e-5
num_train_epochs: 3.0
lr_scheduler_type: cosine
warmup_ratio: 0.1
#bf16: true
fp16: true
ddp_timeout: 180000000

### eval
#val_size: 0.0001
#per_device_eval_batch_size: 1
#eval_strategy: steps
#eval_steps: 500

try this
https://gofile.io/d/yMHabA
select the desired compiler in the installer

we adopted sequence packing at pretraining. multiple sequences will be packed together

Hi, I have another question regarding using sequence packing in sft stage； when i specify packing:True in the config (even if I specify stage: sft), it seems like it will adopt the sequence packing without any warnings. I am wondering whether it is a practical usage to use sequence packing in sft stage? During evaluation, I find some of the benchmark score is normal while the other is not, maybe we should not use packing in sft stage?

@chanchimin Packed training should use different hyperparams from the non-packed ones. You can refer to this thread for further discussions: https://github.com/hiyouga/LLaMA-Factory/issues/5426


add UFPI to domains list

Official website: https://www.ufpi.br/

@karolinefarias Pull request merged. Thank you!


please include LICENSE.txt in the sources uploaded to crates.io

There exist more than 20 variants of the "MIT" license.
Side note: Unless I did my comparison wrong, you seem to have chosen the "Modern Style with sublicense", as it is classified by the Fedora project: https://fedoraproject.org/wiki/Licensing:MIT?rd=Licensing/MIT#Modern_Style_with_sublicense
Your LICENSE.txt text states:

The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.

So, to clarify which "MIT" license actually applies, and to adhere to the text of the chosen license, please include the LICENSE.txt file with the crate published to crates.io. Adding a "LICENSE.txt" entry to the "include" array in Cargo.toml should do that.

Closed in 4f259e0, will be present in the next publish. Thanks!


Periodically crashing app with given stacktrace

 AndroidRuntime  E  FATAL EXCEPTION: AsyncTask #6
                         E  Process: com.speanluy.speanloan.uat, PID: 9985
                         E  java.lang.RuntimeException: An error occurred while executing doInBackground()
                         E      at android.os.AsyncTask$3.done(AsyncTask.java:354)
                         E      at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
                         E      at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
                         E      at java.util.concurrent.FutureTask.run(FutureTask.java:271)
                         E      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
                         E      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
                         E      at java.lang.Thread.run(Thread.java:764)
                         E  Caused by: java.lang.IllegalArgumentException: Given work is not active: JobWorkItem{id=1 intent=Intent { flg=0x10 cmp=com.speanluy.speanloan.uat/reka
                            b.app.background_locator.LocatorBroadcastReceiver (has extras) } dcount=1}
                         E      at android.app.job.JobParameters.completeWork(JobParameters.java:268)
                         E      at androidx.core.app.JobIntentService$JobServiceEngineImpl$WrapperWorkItem.complete(JobIntentService.java:268)
                         E      at androidx.core.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:394)
                         E      at androidx.core.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:383)
                         E      at android.os.AsyncTask$2.call(AsyncTask.java:333)
                         E      at java.util.concurrent.FutureTask.run(FutureTask.java:266)
                         E      ... 3 more

Can you share some code?

@mehdok I have exactly the same crash:
Fatal Exception: java.lang.RuntimeException: An error occurred while executing doInBackground()
       at android.os.AsyncTask$4.done(AsyncTask.java:399)
       at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
       at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
       at java.util.concurrent.FutureTask.run(FutureTask.java:271)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
       at java.lang.Thread.run(Thread.java:919)

Caused by java.lang.IllegalArgumentException: Given work is not active: JobWorkItem{id=1 intent=Intent { flg=0x10 cmp=com.snapmart.ridersdev/rekab.app.background_locator.LocatorBroadcastReceiver (has extras) } dcount=1}
       at android.app.job.JobParameters.completeWork(JobParameters.java:273)
       at androidx.core.app.JobIntentService$JobServiceEngineImpl$WrapperWorkItem.complete(JobIntentService.java:17)
       at androidx.core.app.JobIntentService$CommandProcessor.a(JobIntentService.java:17)
       at androidx.core.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:2)
       at android.os.AsyncTask$3.call(AsyncTask.java:378)
       at java.util.concurrent.FutureTask.run(FutureTask.java:266)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
       at java.lang.Thread.run(Thread.java:919)

I found the stackoverflow issue with this crash:
https://stackoverflow.com/questions/52519946/java-lang-illegalargumentexception-given-work-is-not-active-exception-in-oreo-w

Thank you @nambv, I'll look into it;

thanks @mehdok , hope it will be fixed soon 😄

Well I'm not exactly sure how the JobIntentService works, but is there a reason the JOB_ID is random?
I changed it to constant value and it's not crashing anymore.
       private val JOB_ID = 99

@mehdok can you take a look at @adolfdsilva's  comment and update the lib version if it is solved? 😄

@adolfdsilva @nambv
I'm not really sure why I did that at that time. But if it fixes the problem please create a PR and I would be more than happy to merge it;

@mehdok in official docs with the example code job id is static, may be @adolfdsilva's solution will fix this issue:
https://developer.android.com/reference/androidx/core/app/JobIntentService

@nambv Can you test that and confirm it is working?

@mehdok I have forked your repo to modify and test. Will give you the result soon :-?

@mehdok @nambv I had forked the lib earlier and tested it only on my device, it works fine.
I'm waiting for the update to go live on play store and if I don't see any crashes in firebase, I'll do a PR.


Build tests and samples

Turns out we're not building tests and samples anymore
cc @pranavkm @Tratcher

:shipit:

Would this cause a normal build.cmd run to compile the tests twice? Once for build-test and once for test?

In theory, once we have incremental builds in CLI, it should no-op the second build.

But in the meantime this makes everything even slower locally? That might be a problem.

They have incremental builds working in the latest drop. We're waiting on https://github.com/dotnet/cli/pull/1067#discussion_r51060978 to go through before we switch to it. That should be soon. We could hold off on this check in until that happens.

@JunTaoLuo this might impact your configurable folder change

Here's the deal. I want to push this because the CI doesn't build samples, so I've added a switch that allows you to build "the old way" as a workaround for building locally in case you feel the build is too slow.


added checking of return values in X509_STORE_set_default_paths

I found that X509_STORE_set_default_paths always returns 1 so i added error checking. without this the function us unusable.

Yes some tests fail now. this may be the result of checking directories before adding them as certificate path.

While it might be appropriate to check for some of error conditions, suggested code is essentially wrong on several accounts. For starters, dirent.h is not as portable. OpenSSL uses own abstraction layer for enumerating directories. Secondly, even if one uses that, enumerating files with "pem" [anywhere] in filename is not the way to establish if directory is usable. Because when it comes to actual action it's not the kind of file names that are looked for. Basically the only sensible thing one can do is to check if it's in fact a directory. But it's checked implicitly when files are looked up later, so current code can be viewed as "not incorrect" as it as. With all this in mind suggestion is to close this request.
[On side note I found relevant code paths hard to unravel.]


⚠ ClamAV has degraded performance

In 66d9a4c, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 288 ms

Resolved: ClamAV performance has improved in e3fe96e after 6 minutes.


Add CSP headers

Add CSP (content security policy) headers
TODO:

Check from which domains

Should only be the origin

Check to which domains AJAX requests are made?

White list those domains
For example testnet.gny.io, mainnet.gny.io, testnet-app
Which domains do the Swapgates need?

Related: #55
Related PR: https://github.com/GNYIO/gny-wallet/pull/80


[Bug] Footer mailing input is mismatched on /showcase

Reference
https://togithub.com/storybookjs/frontpage/issues/481

The issue has been reported to maintainer and external contributor can not run the frontpage without backend data, so it should be closed


"You do not have permission to perform this action" error on production server

Hi,
I recently deployed my application on a live server, and for some weird reason all my requests to mutations that are wrapped in the @login_required decorator keep returning the error "You do not have permission to perform this action".
My settings are a replica of what's on the documentation.
For more context: I use a custom login mutation where I use the  token = get_token(user) shortcut to generate the JWT token.
All of this works on my localhost, however it's not working in production.
I did a little digging and it seems the code is not respecting the JWT passed in the header Authorization. I know this because, if I use the graphql_jwt.ObtainJSONWebToken.Field() mutation to login, it seems to set a cookie that then logs the user and returns the correct responses for all those endpoints wrapped in  @login_required
Anybody experienced this before? I'm fine with it setting a cookie if that's the only way, I'd just like to know how to authenticate users with a custom function and also have the token returned in my custom sign up and login mutation.
Any help would be really appreciated.
Thank you.

Figured it out. My server is AWS Elastic Beanstack, and for some reason WSGIPassAuthorization is turned off, so I had to enable "WSGIPassAuthorization On" to get it to work.
https://stackoverflow.com/a/25862505

I am experiencing this in development mode. How did you solve it in ur dev env. @Kendysond

@YasinYA Did you find a solution for that problem ?


[Question] Does it work for directed, weighted graph?

Hi there,
Original Infomap algorithm works on directed, weighted graph. Does Infoflow supports directed weighted graphs as well?
Did you try your algorithm on large graphs (like a few hundred million nodes and a billion edges)? What are the performance results?

Hi,
Yes InfoFlow, both the algorithm and this implementation, supports directed weighted graphs.
We have not yet performed computation on large graphs.


Rework it

https://github.com/cyberalexander/person-registry/blob/654a0ced3719974b3a69199cd4402df7727fe95b/src/main/java/by/academy/it/service/PersonServiceImpl.java#L88

Fixed in one of the earlier commit(s)


[Microsoft Azure Attestation] Control Plane 2021-06-01

ARM API Information (Control Plane)
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? The feature has been deployed in 2022.

When do you expect to publish the swagger? ASAP. This PR is a replacement of the old one: https://github.com/Azure/azure-rest-api-specs/pull/20997

By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version

[x] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki. Note that this doesn't apply if you are trying to merge a PR that was previously in the private repository.

[x] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[x] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

Previous PR https://github.com/Azure/azure-rest-api-specs/pull/20997

/azp run

@msyyc please help take a look at Python SDK breaking change


Add a pass to canonicalize ops used as loop carried values by scf.for

This is an ad hoc pass to clean up some unnecessary operations added
during progressing lowering. MLIR canonicalization currently cannot
clean it up, this is a temporary solution to allow those to be removed
on IREE side.

Note that I'm trying to get a solution upstreamed (https://llvm.discourse.group/t/canonicalization-cross-region/2072) but it seems like coming up with a clean solution might take some time. In the meantime this is the last pattern missing for some of the mobile GPU codegen. Feel free to suggest a better solution.


[BUG] Redeeming cashu tokens to alby lightning address fails

Describe the bug
When attempting to redeem a cashu token to my LUD-16 getalby.com lightning address I get a "Token melt failure: timeout".
To Reproduce
Steps to reproduce the behavior:

Go to cashu.me, create a lightning invoice, redeem it for ecash tokens, click "send ecash" and copy the cashu token string to your clipboard. Or get a valid cashu ecash token via other means.
In amethyst, DM the ecash token to yourself to ensure no one else can claim it.
In the DM view you should see a "redeem" button in place of the ecash token text. Click it.
If you have a getalby LN address set on your profile you should see a "Token melt failure: timeout" error.

Expected behavior
No errors. Expect a lightning payment to my LN address.
Device (please complete the following information):

Phone Brand/Model [e.g. Pixel 7 Pro]: moto g power 2021
Android Version [e.g. 33]: 11
App Version [e.g. v0.20.3]: v0.64.4

Confirming I had the same issue with getalby.   I was using a legends mint for these tests.  What were you using vnprc?   If you were using legends also, I can try later with my own lnbits instance or the 8333 mint.

Hey there,
The reason might've been that the LN node simply failed to find a route.
Client-side, the POST /melt call should have a very long (or infinite) timeout, as this call will block until the payment either succeeds or fails.
That should hopefully resolve the issue. Following further updates!

@findingsov I was also using legend.lnbits.com

I believe this was resolved lately in our Cashu redesign. Let me know if it still happens otherwise.


[FLOC-1647] Flocker CA documentation

Fixes FLOC-1647
Provides three documentation pieces; a new page in the advanced/api section with instructions for generating API user certificates, instructions in indepth/installation for generating and copying over the control service and agent certificates and a new advanced/security section with prose describing an overview of how Flocker's authentication layer works.

This is going to need to be automated / simplified if Flocker is to ever make it in the real world.  But that's not for this issue.

Having addressed review comments in repsect of tech content, I will now hand this over to David Oliver to address any further UX content and IA.

If you're moving the YAML examples you also need to change conf.py to point to new location. Please address, merge forward, and resubmit for final review.

Overall looks pretty good and detailed, though, so hopefully next review will be brief (I want to actually see the output though, and buildbot didn't build latest version).

Merge forward, address, merge. Thanks!

Oh, one last thing: this doesn't update the usage.rst documentation for flocker-deploy, which still talks about SSH. So that needs documenting too.


Mention vCenter v6.7 support

The about document mentions 6.7 as a supported version of vCenter Server, adding that version number here for consistency.

@davidroberts63 : Thanks for your contribution! The author, @rayne-wiselman, has been notified to review your proposed change.

#sign-off

Thanks!


Consider $init_done in handle_define()

ATM where Buienradar is defined and the FHEM init is not yet done, the attributes are not yet set ($init_done is 0). So instead of starting a timer, the notify handler should be listen to global and start the timer after the initialization is done.
See also DevelopmentModuleIntro - Verfügbarkeit von Attributen


Added a configurable CPU alert threshold.

In some situations, CPU usage thresholds other than 90% warrant (or don't warrant) concern. For example:

If this is a production web server with a heavy focus on real time performance, a threshold lower than 90% may be desirable.
If this is a non-time-critical background job server with a single core, sustained loads over 90% may not be of any concern.

Since alerts are not configurable by server component in the library (currently), I'm adding a configuration for the threshold so the user can choose when to be notified.

@f-hj Could I get a review on this please? My team and I would love to see this on the main branch!


Throwing SyntaxError: Unexpected token { on postgraphql execution

npm install -g postgraphql
pg running on 5432
postgraphql --help (fwiw - any command) throws syntax error because of an empty string in showErrorStack

/usr/local/lib/node_modules/postgraphql/build/postgraphql/cli.js:46
const { demo: isDemo = false, connection: pgConnectionString, watch: watchPg, host: hostname = 'localhost', port = 5000, maxPoolSize, defaultRole: pgDefaultRole, graphql: graphqlRoute = '/graphql', graphiql: graphiqlRoute = '/graphiql', disableGraphiql = false, secret: jwtSecret, token: jwtPgTypeIdentifier, cors: enableCors = false, classicIds = false, dynamicJson = false, disableDefaultMutations = false, showErrorStack, } = program;

actually the problem is that const is not a well-formed JSON object - since these are not key-value pairs
cors: enableCors = false, classicIds = false, dynamicJson = false, disableDefaultMutations = false

What version of Node.js are you running? PostGraphQL runs on Node.js 6+. It looks to me like your version of Node.js may not support destructuring. If you need to support an older version of Node.js let me know :+1:

was running node 5.9.x - upgraded to node 6.9.1 on os/x - works now.


chore: internal qa feedback enhancements

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
This PR fixes:

[x] Disable Coming soon buttons in homepage (show disabled state)
[x] Move “My drops” to be a full nav item (similar to doc and get in touch) (make sure to check if the nav is responsive in mobile, if its breaks, it should remain in the menu)
[x] Change “All Drops” to “My Drops”
[ ] Redirect to “My Drops” after user has connected with the wallet
[x] use outline variant for secondary cta button (e.g. Master key modal cancel button)
[x] replace the existing Master key icon in the menu dropdown with a key icon

Fixes #156
How to test
Show steps to replicate and test the feature/fixes in this PR
disable coming soon buttons in homepage

check the drop section for ticket and nft
coming soon should be disabled

my drops should be in nav item

Go to the preview link
Connect your wallet
My Drops should appear as one of the Nav Item

all drops should be called my drops

Go to My Drops
It should be called My Drops now

outline variant for secondary button

try to set master key.
cancel button should be outlined.

Screenshots/Screen Recording of Implementation
see slack

I'm confused about the disabling of coming soon buttons - they are already disabled?
Current main:

This PR:

I don't actually like the auto redirect to the all drops page.. I'd rather than see the beautiful frontend that they were "promised" before they signed in

I'm confused about the disabling of coming soon buttons - they are already disabled? Current main:
This PR:

yeah, I thought since it was part of the enhancement, I ought to make it clear that it was already done 👍


Update context.md

The original sentence didn't make sense so I added Provider as the sentence subject.

Hello @Charlesworth, thank you for taking the time to contribute!
I couldn't find that sentence in the latest version of docs, so I don't think this PR is any longer needed.
Let me close it as outdated, but feel invited to create new PRs for other open issues!