VSCode Incorrectly Showing bal Files Having Errors

Description:
In the VSCode side pane where the files are shown, it sometimes shows some files are having errors (highlighting those files in red, and showing the error count as well). But when the file is opened, it does not contain any error. Once we close the file, the error appears back in the side pane.
Check the following screencast. This uses the Ballerina GraphQL module.
https://user-images.githubusercontent.com/40016057/132165745-81d743b9-48e4-4286-b3f2-5ce2fe0302d7.mov
Affected Versions:
SwanLake-Beta.3-RC1
OS, DB, other environment details and versions:
VSCode Version: 1.60.0
Ballerina VSCode Plugin Version: 2.1.0
OS: macOS Big Sur

Created https://github.com/wso2/ballerina-plugin-vscode/issues/135 to track this.


Mutating admission controller doesn't handle annotations that contain '/'

When adding a patch for an annotation with a path like /metadata/annotations/kubernetes.io/role the annotation isn't added, and any existing annotations are removed.
This happens whether or not there are any existing annotations in that path.

This has to do with how JSON Pointer (RFC 6901) handles escaping of / characters. JSON Patch uses JSON Pointer to model the path field in the patch operation.
The / in kubernetes.io/role needs to be escaped. The path in the patch ought to be: /metadata/annotations/kubernetes.io~1role.


[Docs] Bounding Box documentation update for GA

Overview
Bounding Box documentation update for GA

Screenshots updated
Added details about the handle asset configuration

Page
https://github.com/cre8ivepark/MixedRealityToolkit-Unity/blob/prerelease/2.0.0_stabilization_BBDocsGA/Documentation/README_BoundingBox.md

/azp run mrtk_docs


Added alternative release-manifest with kube-rbac-proxy for exposing the metrics port.

Also added supporting clusterroles, clusterrolebinding, service and make target to build this alternate release-manifest.
Issue #, if available:
Description of changes:
Additions to config/ directory tree, in new default-with-metrics-port directory.
New make target release-manifests-metrics-port
Testing performed:
Successfully queried metrics port through the proxy from a pod in capc-system with default service account token and ca.crt, supported by clusterrolebinding of capc-system default service account to capc-system-metrics-reader clusterrole.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Converted back to draft.  This may need a mechanism to allow EKS-A to override the repo containing the kube-rbac-proxy image...

I've confirmed that we do not need to provide any kube-rbac-proxy image-override mechanics here to support EKS-A.  It uses a clusterctl feature to perform those overrides.

Codecov Report

Merging #138 (ae65501) into main (13ed8d7) will increase coverage by 0.85%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #138      +/-   ##
==========================================
+ Coverage   28.01%   28.87%   +0.85%
==========================================
  Files          27       27
  Lines        2195     2248      +53
==========================================
+ Hits          615      649      +34
- Misses       1502     1521      +19
  Partials       78       78

Impacted Files
Coverage Δ

pkg/cloud/isolated_network.go
30.89% <0.00%> (-1.44%)
:arrow_down:

pkg/cloud/client.go
16.66% <0.00%> (-0.99%)
:arrow_down:

pkg/cloud/tags.go
38.27% <0.00%> (-0.69%)
:arrow_down:

pkg/cloud/instance.go
79.01% <0.00%> (-0.47%)
:arrow_down:

pkg/cloud/affinity_groups.go
16.80% <0.00%> (-0.32%)
:arrow_down:

pkg/cloud/user_credentials.go
0.00% <0.00%> (ø)

pkg/cloud/network.go
44.44% <0.00%> (+0.25%)
:arrow_up:

pkg/cloud/zone.go
21.27% <0.00%> (+2.67%)
:arrow_up:

controllers/cloudstackcluster_controller.go
47.47% <0.00%> (+18.18%)
:arrow_up:

Continue to review full report at Codecov.

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

/lgtm


Costs

What does it costs?

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

ID: fe4f2bf5-0156-dc04-bd89-8f4e61f342b1
Version Independent ID: 1dc5a1e7-c818-f5d9-46ae-639f5b664578
Content: What is Azure Security Center?
Content Source: articles/security-center/security-center-intro.md
Service: security-center
GitHub Login: @TerryLanfear
Microsoft Alias: terrylan

@Floriszz Thanks for your feedback! We will investigate and update as appropriate.

@Floriszz Please refer to Security Center pricing for security center pricing information.

@Floriszz We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Collection operation not supported.

 $" new List<string>().Any()"

ParseException: Type 'List' not found

This is not supported.


build(github-actions): switch checkout to explicit version

Coverage remained the same at 100.0% when pulling 22014a9d0aafe3ee3a57d14d9fa68dc81bfff7ff on build-github-actions-checkout-explicit-version into 64d5b05bd269d499e59482d69899dee0d240ea37 on main.

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


USER-245: Add API to use a specific Custom Tabs implementation

https://doxodev.atlassian.net/browse/USER-245
What I did
On the Android platform through the useCustomTabsImplementation(packageName) API I made it possible to select any of the available Custom Tabs implementations for the in-app-browser, in case the default one is not preferable.
I also added an API (getViewHandlerPackages()) to retrieve the package names of the default view handler and of the view handlers that are also Custom Tabs implementations.
This effort is driven by fatal authentication issues in the doxo mobile app. We observed that users on certain devices - e.g. where Firefox is the default browser and the Custom Tabs implementation in the in-app-browser - are unable to log in because in the end of the oauth flow, although Firefox passes the doxo specific custom scheme callback URL to the OS, somehow the doxo app does not receive it as it does when other browsers back the in-app-browser (e.g. Chrome).
Another issue this change helps address is that on certain devices (at least on LG Aristo, Android 7.0 API level 24) where Opera is installed beside other browsers, the Android APIs return Opera as the only possible view handler. This makes authentication impossible since Opera is not a Custom Tabs implementation.
How I did it
Changed the plugin's JS interface and a few java classes.
How to verify it
Wait for related changes in the doxo mobile app (I haven't made those yet) then have Firefox as the default browser on an Android device. You should be presented with Chrome - instead of Firefox - as the in-app-browser when trying to sign in.

@deepakinseattle
I added you as a reviewer since I know you're a java guy and regarding that I'm not sure about @tylerritchie and @mikewisian.

@uifox, is this in progress or done? You have a WIP label assigned to it right now.


Client Allocation Request for: InK ent.

Client Allocation Questions
Core Information

Name: InK ent.
Website / Social Media: http://inkent.co.kr/
Region: North America
DataCap Requested: 1 TiB
Addresses to be Notarized: f1u2hqlk32xsub5st4bwowvvkup7qjwqpyhqr5ddi
Notary Requested: dannyob

Hi, it looks like you're working from Korea. Could you re-submit with one of the notaries in your region -- perhaps 12ships foundation or MathWallet? (If you have problems there, you can come back to the Filecoin Foundation; it's just easier for them to check your credentials).
안녕하세요, 한국에서 일하시는 것 같습니다. 해당 지역의 공증인 중 한 명에게 다시 제출 -- 아마도 12ships 재단이나 MathWallet? (문제가 있는 경우 Filecoin Foundation으로 돌아가서 자격 증명을 확인하는 것이 더 쉽습니다).


Display Manager

Description of the new feature / enhancement
The idea of Display Manager is to manage display/screen related settings from the keyboard using hotkeys or popup a tool which can be used to adjust windows display settings easily. The tool can also allow the users to customize certain hotkeys to perform predetermined display settings e.g. changing the scale resolution to 100% etc.
Scenario when this would be used?
Users working with different screen or even single displays need to switch between different scales and resolution. The tool can be used to provide users and easy way to adjust these settings and create macros/hotkeys based upon their certain predefined criteria.
Supporting information
No response

/dup #1052


Relations support

Support for relations has been long asked for but I've been reluctant to implement it because the code is not my best and am reluctant to go back into the heavy logic. However, I just worked on getting the parsing function to handle gracefully all types and it looks like relations can be implemented in a way that is self-contained and probably quite straightforward. So I'll lay out what I want to do here and ask for feedback.

Relations are effectively triples of two arguments and a relation type. Assuming that the possible arguments are predetermined, e.g. arguments can only be tokens, or chunks or some other pre-annotated spans, evaluating the agreement is really quite easy -- F1-score where each triple is treated as a unique annotation. I can probably copy lost of the code straight from bioeval.
I haven't thought about this for too long but using F1-score seems to be a bit of a copout here. The probability of a random assignment of a relation is not infinitely small. So maybe kappa can be implemented here instead.
Additionally, in many cases the arguments are not necessarily predetermined, so that would be quite hard to evaluate at the same time and honestly I have no idea how to do it ATM.
So I'm looking for some input here. Would be nice to hear what you think.
cc @jeanphilippegoldman @soluna1

Hi Savkov,
thanks for addressing this issue. I'm not an expert coder at all, so personally I can't help very much. However, I colleague of mine is working also with Brat, so I'll comment with him the issue, he may have some ideas. Let you know asap.

Hi Sasho,
Thanks for sharing your thoughts.
I agree that thinking of agreement evaluation can be quickly tentacular.
I am not sure I can be helpful for developping the evaluation of relations.
But let me add my input.
First, you say "evaluating the agreement is really quite easy -- F1-score
where each triple is treated as a unique annotation"
Let's go like this for a start. but quickly, we may want to distinguish
exact-same relations
from relations pointing on the same chuncks but with a different type.
Then relations with one common argument instead of two.
Another point : you say " in many cases the arguments are not necessarily
predetermined",
defining arguments as "chunks or some other pre-annotated spans".
How a relation can point to stg else ? please clarify
Sorry for my naive remarks and questions.
Thanks for your work
Jean-Philippe Goldman
j:-P
On Thu, Jun 27, 2019 at 9:07 PM Sasho Savkov<EMAIL_ADDRESS>wrote:

Support for relations has been long asked for but I've been reluctant to
implement it because the code is not my best and am reluctant to go back
into the heavy logic. However, I just worked on getting the parsing
function to handle gracefully all types and it looks like relations can be
implemented in a way that is self-contained and probably quite
straightforward. So I'll lay out what I want to do here and ask for
feedback.
Relations are effectively triples of two arguments and a relation type.
Assuming that the possible arguments are predetermined, e.g. arguments can
only be tokens, or chunks or some other pre-annotated spans, evaluating the
agreement is really quite easy -- F1-score where each triple is treated as
a unique annotation. I can probably copy lost of the code straight from
bioeval https://github.com/savkov/bioeval/.
I haven't thought about this for too long but using F1-score seems to be a
bit of a copout here. The probability of a random assignment of a relation
is not infinitely small. So maybe kappa can be implemented here instead.
Additionally, in many cases the arguments are not necessarily
predetermined, so that would be quite hard to evaluate at the same time and
honestly I have no idea how to do it ATM.
So I'm looking for some input here. Would be nice to hear what you think.
cc @jeanphilippegoldman https://github.com/jeanphilippegoldman @soluna1
https://github.com/soluna1
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/savkov/bratutils/issues/17?email_source=notifications&email_token=ADQ5ZKYYZ4D7YZMAF3DAD5DP4UFX5A5CNFSM4H37KESKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G4FABHA,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADQ5ZKY3BOLTRP5NMKYSBULP4UFX5ANCNFSM4H37KESA
.


sof-firmware: 2024.09 -> 2024.09.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/sof-firmware/versions.
meta.description for sof-firmware is: Sound Open Firmware
meta.homepage for sof-firmware is: https://www.sofproject.org/
meta.changelog for sof-firmware is: https://github.com/thesofproject/sof-bin/releases/tag/v2024.09.2
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2024.09.2 in filename of file in /nix/store/4vxpg4l65ym4anp074dzz9af5f967hj0-sof-firmware-2024.09.2

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

sof-firmware

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/4vxpg4l65ym4anp074dzz9af5f967hj0-sof-firmware-2024.09.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/dc46520f19239e5f2f50c18aa0aea018437b63c1#sof-firmware

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/4vxpg4l65ym4anp074dzz9af5f967hj0-sof-firmware-2024.09.2
ls -la /nix/store/4vxpg4l65ym4anp074dzz9af5f967hj0-sof-firmware-2024.09.2/bin

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

x86_64-linux

:white_check_mark: 1 package built:

sof-firmware

Maintainer pings
cc @lblasc @evenbrenden @hmenke for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

@NixOS/nixpkgs-merge-bot merge


Make GDE Python 2.7 compatible again

IntelliJ thinks that all the code under graph_def_editor is Python 2.7-compatible, but Python 2.7 does not. We'll need to take the some steps to rectify this issue:

Replace the Python 3.x type hints syntax with the backwards compatible syntax described in PEP 484. That is:def _validate_output_shapes_attr(value):
  # type: (Any) -> List[tf.TensorShape]

instead of:def _validate_output_shapes_attr(value: Any) -> List[tf.TensorShape]:

Replace the calls to urllib.request in the three example scripts with something that works in both Python 2.7 and 3.x.
Add an option to the "env.sh" script to create a Python 2.7 environment if requested.
Run all the tests and examples with Python 2.7 to verify that they work.

Replace the calls to urllib.request in the three example scripts with something that works in both Python 2.7 and 3.x.

I could take this one Fred

Thanks, @BryanCutler

Type hints PR is in. Other items in this issue still yet to be done.

I think Python 2 is no longer relevant. Closing this PR.


Fix serialized egraph in egglog

See this PR: https://github.com/egraphs-good/egglog/pull/368

This is no longer necessary for now- I fixed this using subsume instead of deletion


May I suggest a Readme.md file? Thanks

Awesome! Thank you! We would be including this in our catalog over at nostr.info

Sorry, follow up question - I understand that this is cross-platform, but which platform specifically? Desktop Windows, Linux, MacOS - Mobile Android, iOS.
I asked what Scala is for (first time I've heard of it to be honest) and this is what ChatGPT told me:
Can Scala be used to develop for:

Desktop windows
Desktop linux
MacOS
Mobile Android
Mobile iOS

Yes, Scala can be used to develop applications for all of the platforms you have listed:
Desktop Windows: Scala can be used to develop desktop applications for Windows using various GUI frameworks such as JavaFX, Swing, and ScalaFX.
Desktop Linux: Scala can be used to develop desktop applications for Linux using various GUI frameworks such as JavaFX, Swing, and ScalaFX.
MacOS: Scala can be used to develop desktop applications for MacOS using various GUI frameworks such as JavaFX, Swing, and ScalaFX.
Mobile Android: Scala can be used to develop Android applications using various development frameworks such as the Android Native Development Kit (NDK), Scala on Android (ScalaFX), and the Android SDK.
Mobile iOS: While it is technically possible to use Scala for iOS development using third-party frameworks such as Scala Native and Scala.js, it is not a widely adopted practice in the iOS development community, and Swift or Objective-C are more commonly used for iOS development.


[Removal]: Request Removal from Denylist

Hotspot Name
Fit Lace Puma
Hotspot b58 Address
112wgzDeyybt65kXyNECYixokSBCaKCeXWpsEJQgYzuirMiKpi47
Discord Handle
No response
Hotspot Manufacturer
Bobcat
Removal Reason
Hotspot location has been corrected. Can you please reconsider to remove from denylist?
Modifications
No
Extra forwarders
No
Extra antennas
No
Additional Information

Never found such a bad project. When you bought the equipment, the seller and the project party did not supervise whether the sales were legal or not, and did not inform you of the existing risks, just as the police acquiesced in allowing qualified arms dealers to sell arms, but did not inform you that they must sell and use arms legally.  I believe that Helium will definitely declare bankruptcy. As it is said on the Internet, he is a fraud. Because now everyone is reporting. Even though the new 5G hot spot equipment is excellent, it is impossible for new miners to be deceived again.

Never found such a bad project. When you bought the equipment, the seller and the project party did not supervise whether the sales were legal or not, and did not inform you of the existing risks, just as the police acquiesced in allowing qualified arms dealers to sell arms, but did not inform you that they must sell and use arms legally.  I believe that Helium will definitely declare bankruptcy. As it is said on the Internet, he is a fraud. Because now everyone is reporting. Even though the new 5G hot spot equipment is excellent, it is impossible for new miners to be deceived again.

Guys what is the reason that you are spamming my ticket?

@6CornerDefender confirmed re-asserted

Hi, is there any additional proof required to be provided by me?


Disallow creating Responses with no body.

via https://github.com/square/retrofit/issues/2362
Is there a valid use case for making synthetic cache responses, though?

We need these for the responses in cacheResponse() and networkResponse().
For that particular problem we could confirm the responses returned from interceptors are complete.

Yes that's the check I was trying to allude to. Responses from user
interceptors should have non-null bodies (we can probably safely assume
ours are correct).
On Tue, Jun 13, 2017 at 7:22 PM Jesse Wilson<EMAIL_ADDRESS>wrote:

We need these for the responses in cacheResponse() and networkResponse().
For that particular problem we could confirm the responses returned from
interceptors are complete.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/square/okhttp/pull/3405#issuecomment-308276322, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAEEEaqq10oqEY5ZTdFOMP4YLlIUuMyoks5sDxnRgaJpZM4N5H2g
.

oops, duh. i'll take some stabs at that tomorrow morning.


Installing 'Authors' app gives 'Something went wrong' msg box

I followed the excellent install instructions to the 't' and successfully uploaded both apps to Teams:

The 'Company Communicator' app appears to have installed OK:

But when I try and install the 'Authors' app I get this msg:

I am not a dev so am amazed I got this far, is there a trick to installing the Authors app that I am unaware of?
TIA, Nigel

Solved.  I had copied the wrong GUID for %botId%


feat: breadcrumb: add breadcrumb component

SUMMARY:
Adds Breadcrumb component to Octuple, along with its UTs and story samples.
https://github.com/EightfoldAI/octuple/assets/99700808/f1f71e6f-d305-4015-a2ba-788a8a5fa5c7
JIRA TASK (Eightfold Employees Only):
ENG-41623
CHANGE TYPE:

[ ] Bugfix Pull Request
[x] Feature Pull Request

TEST COVERAGE:

[ ] Tests for this change already exist
[x] I have added unittests for this change

TEST PLAN:
Pull the PR branch and run yarn and yarn storybook. Verify the Breadcrumb stories behave as expected.

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@a07fb0d). Click here to learn what that means.
Patch has no changes to coverable lines.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #629   +/-   ##
=======================================
  Coverage        ?   84.74%
=======================================
  Files           ?      845
  Lines           ?    17710
  Branches        ?     6304
=======================================
  Hits            ?    15008
  Misses          ?     2634
  Partials        ?       68

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


fix: enhance publish action and authors in pyproject.toml

What kind of change does this PR introduce?
Update publishing github action with --skip-existing flag that will not throw an exit status of zero if the version already exists on pypi. Additionally update author list in pyproject.toml.
Summary
Once a pull request is successfully merged into the main branch, it initiates the release and publication processes. Subsequently, the Python Semantic Release action prompts an additional commit for versioning, even after the latest version has already been published. However, this modified version of the release-and-publish.yml will not redundantly republish the recently released version. PyPi also doesn't support multiple authors, hence why I changed name to OpenAdapt.AI Team
Checklist

[x] My code follows the style guidelines of OpenAdapt
[x] I have performed a self-review of my code
[x] If applicable, I have added tests to prove my fix is functional/effective
[x] I have linted my code locally prior to submission
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation (e.g. README.md, requirements.txt)
[x] New and existing unit tests pass locally with my changes

How can your code be run and tested?

Other information

@abrichr Ready for Review! :)


[Bug - Edge Addons API] Uploading a lesser version is possible

Describe the bug
The version of my extension that's published to the store is 1.5.1.
I discovered that, unlike the web-based dashboard, the Upload API doesn't check the versions.
In my case, I was able to upload version 1.3.15 and did not get any issues.
To Reproduce
Steps to reproduce the behavior: upload a ZIP of a version less than the currently-published version.
Expected behavior
Return an error object stating that the version is lesser.
Screenshots

Desktop (please complete the following information):

OS: [e.g. iOS] Windows 10 x64  21H1

Additional context
If this behavior is intended, then there should at least be an API that allows for checking the extension's version.

@avi12  This behavior is in line with UI. In the UI we are validating during publish step after upload. In case of api, the publish step is handled by the 'publish' operation. Please try publishing this extension and the version would be validated during publish operation

I see
Why is the validation step not occurring in the upload step?

Even in the UI the behavior same, we check only when the publish operation is attempted. To be in sync with UI, validation is not done in the upload step for the version

I understood. I was asking why is this behavior like so out of curiosity

it is primarily a design choice made with performance considerations during upload from UI

Thanks @yvsubhash for the details!


Generator may generate ambiguous extensions.

If 2 components of the same name but in different namespaces are included in a query, the generator will generate ambiguous extensions.

ex: Group<All<Components.Boba.A, Components.Fett.A>>; item.A();

Requires to add namespace segments to the extensions until they are no longer ambiguous: item.BobaA(); item.FettA();

Currently fixed like ambiguous extensions that would occur from a redundant query, i.e. by not generating an ambiguous extension.


Refactor VariationModel

See #2207

Separate computing delta weights
Split off box-splitting/support code to separate function

After chatting with Behdad I need to fix some terminology issues with the variable naming.

Sure let's merge this. I'll try to reshuffle things around into more useful structure.

Ah, thanks for fixing the terminology.


skipUpdateTransform for specific DisplayObject?

I have a container in which I constantly add sprites, I know that their position won't change so I don't want theit transform to be calculated each frame. Can I somehow pass skipUpdateTransform to the container so the updateTransform() call won't be called each frame? Something like container.skipUpdateTransform = true. The issue is that it looks like the updateTransform function uses the most CPU (7%) of all the functions in the app.

pixi.js version: 4.7.1
Browser: Chrome 67
Device: Desktop

make your own container and override updateTransform method. Like, how ParticleContainer does it.


Have a "remove"/"cleanup" event?

Hello. I'm trying to write a small extension to LayoutManger for my project and want to keep things as clean as possible. My extension has to do something once the layout has been rendered and once the layout has been removed. It looks like I can listen to the "afterRender" event for my first one, but I don't seem to have anything for remove. Would it possible to have LayoutManager trigger a remove event when the layout has been removed? Or am I missing something?
At the moment, I'm doing the following... Which means I'm having to duplicate LayoutManager code:
Backbone.Layout.prototype.remove = function() {

  // MY CODE GOES HERE

  // Force remove itself from its parent.
  Backbone.Layout._removeView(this, true);
  // Call the original remove function.
  return this._remove.apply(this, arguments);
};

Is there already a better way? Or could you simply add a "remove"/"cleanup" event that gets triggered?

Cleanup event has been added into master, it will exist in the next release: 0.9.7.


Cleanup the PGD branch

This PR is just meant to clean up the PGD branch.
I have simplified the fitting script, and remove unnecessary code. For now I propose to stick to the offline PGD,  we can always add online PGD later.
@modichirag @dlanzieri let me know what you think, this is a suggestion, this why I made a PR instead of directly modifying the pgd branch.
If you want to save some online pgd code, I'm ok with adding things to the experimental folder.

The fitting script works a little bit differently than before. It starts by fitting the power spectrum at z=0, then it uses that fit as a starting point for higher redshfits, so that it only needs to do a few iterations to update the parameters.
At the end it produces a pickle file that we could directly load in the lensing script.

No comments @dlanzieri :-) ?

@EiffL I looked at your changes, overall the codes are very cleaned and I think we can marge this branch to the pgd one! But I'm still trying to understand your changes to fit_pgd.py :)


Update label in NetworkPolicy example explanation

This change intends to fix the label name in the range of ports NetworkPolicy example to improve the explanation.

Thanks.
/lgtm
/approve


Adapter default basePath is taken instead of definition basePath

If basePath is defined on an adapter's defaults, then it is used for resolving all paths before a resource's basePath is referenced.
Basically this is the same issue as js-data/js-data#232 (and should have the same fix), but it pervades into js-data-angular, and occurs over a much larger set of instances.

@ScottTrenda v2.2.3 published ☝ thx again. We're not going to be doing any more work on v2 so I recommend you upgrade to v3 asap 👍

Awesome, thank you. Could I please request a patch release of js-data-angular that uses js-data-http v2.2.3? Much appreciated!!

Can you PR the patch needed
On Fri, Aug 17, 2018, 08:06 Scott Trenda<EMAIL_ADDRESS>wrote:

Awesome, thank you. Could I please request a patch release of
js-data-angular that uses js-data-http v2.2.3? Much appreciated!!
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/js-data/js-data-http/issues/70#issuecomment-413895294,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFsmSxMtFNhP8nUE7y8aOijF2kPzAgOcks5uRtvdgaJpZM4UqKhS
.

I can try. It looks like v3.2.0 to v3.2.1 is just a simple upgrade of js-data-http to v2.2.2, so I'll take a look at what went into that and do the same.


Schema-based default datetime value with sysdate() throws ClassCastException, if attribute is not specified explicitly

OrientDB Version, operating system, or hardware.

v2.2.13

Operating System

Linux

Hi,
Seems like there's a problem with setting a default date through the schema. Consider the following:
create class Test2 extends V

create property Test2.myUuid string
alter property Test2.myUuid default uuid()

create property Test2.myDate datetime
alter property Test2.myDate default sysdate()

Running insert into Test2 content { } will throw a ClassCastException (no idea why). However, insert into Test2 content { "myDate": "2016-01-01" } works very well.
This one might somehow also be related to issue #6978

hi @andreyvk,
I fixed this problem, be aware anyway that for generate the date on record creation you should alter the property in this way : alter property Test2.myDate default "sysdate()" otherwise the function is evaluated at the moment of the alter.
bye

@tglman, hi
I have a couple of questions, because it seems that I will need to redo a bunch of defaults on my schema now, and the schema is quite large.

While sysdate() requires double quotes to get executed properly, why doesnt uuid() require it?
Also, should I get a habit of using double quotes for these function calls in schema at all times now?
Is this double quote thing only 2.2.x specific or can I also apply it on 2.1.x? At the moment I am heavily testing Orient 2.2 so we can update our production (currently 2.1). If I do schema change now with double quotes everywhere, will it affect stuff on 2.1?

hi @andreyvk,

yes sorry any function if inserted without quote is run on alter time, so also uuid()
yes
with quote is portable betheen 2.2.x and 2.1.x

Bye


Dark mode support

Per request at https://meta.wikimedia.org/wiki/MediaWiki_talk:Gadget-MoreMenu.js

@pppery the correction should also apply to users using the vector-2022 version of the tool's CSS, so the change should also be applied in line 428 here.

Thanks. Done.

@MusikAnimal do you have a moment to merge this and transclude it its meta page?

Sorry for taking so long to get to this! I'll get this deployed today. Thanks @pppery for the PR :)


remove tests when installing moment through bower

This file is 3.5 Mb and it's not needed in production.

Thanks!

Merged in fceb92c0e39de35b666eaed665dabb80d6d43f7c


samples/yeoman generator onTurnError pattern is confusing

Describe the bug
The onTurnError handling logic in many of the samples and the Yeoman templates includes logic that perform steps around loading, clearing and then saving bot state that don't appear to have any real effect on the state. It is unclear what the sample code is even intending to do when just considering the high level API calls, but even more confusing when you actually know what the effect of making those calls is (essentially a no-op) under the covers.
Additional context
This is a result of a bug discovered when we were days away from shipping v4.  The fix would have caused a breaking change and the risk to take the fix was too high given the timeline.  The pattern in the onTurnError is required to clear state when the global error handler is fired, and to also to it in a manner that works around the bug.
The error handling logic in onTurnError that loads, clears and saves state appears to be a complete, functional no-op. It's unclear exactly what the person who came up with that pattern was even trying to do. Perhaps their expectation was that this would somehow reset state, but it wouldn't.
This should likely be removed from the samples/templates.
[bug]

In 4.2 this lands in one of two ways.  The above pattern remains as it's what's required to work around the caching bug.  In this case, then all the samples that have an onTurnError() must be cleaned up to have the above pattern.
or this issue makes it in for 4.2
https://github.com/Microsoft/BotBuilder/issues/5175
in which case the onTurnError() will consist of:
// Catch-all for errors.
adapter.onTurnError = async (context, error) => {
    // This check writes out errors to console log .vs. app insights.
    console.error(`\n [onTurnError]: ${error}`);
    // Send a message to the user
    context.sendActivity(`Oops. Something went wrong!`);
    // Delete current conversation state
    await conversationState.delete(context);  // or wherever we land based on the above DCR
};

Yeoman generated templates are fix in botbuilder generator build 4.0.14 or higher.  The implementations are consistent across the templates.  they will get simplified when https://github.com/Microsoft/BotBuilder/issues/5175 gets fixed.  until then, the load/clear/save pattern is required to work around a known bug.

PR #967 makes all the node and typescript samples that have an onTurnError and use state be consistent with the current 4.1.x behavior.  If Microsoft/BotBuilder#5175 makes it in, then another PR will need to issued to update all the onTurnError handles to the new API


Northstar field authmap

What's this PR do?
This updates the dosomething_northstar_save_id_field function to also save the Northstar ID to the authmap table so it's available to the OpenID Connect module. It also adds a primary key to the dosomething_northstar_request_log table because that's a reasonable thing to do.
How should this be reviewed?
👀
Any background context you want to provide?
🍃
Relevant tickets
References DoSomething/northstar#426.
Checklist

[ ] Documentation added for new features/changed endpoints.
[ ] Tested on staging.
[ ] Pinged a PM if this is a larger PR that would benefit from some additional testing love.

🚢
the other thing was I know that @sergii-tkachenko just wrote some special function for getting NS ids... using that NONE logic. but this shouldn't break that. just speaking out into the void here.

Yep, it should handle both cases safely in the accessor function that he added! I did just do a grep and found a theme function that relied on the NONE string though, so pushed up a fix for that in 3d19fc5.

¡OLÉ! :sheep: it!

@angaither @DFurnes Regarding my handling of 'NONE' value: it's introduced here.

@angaither @DFurnes Regarding my handler of 'NONE' value: it's introduced here.

Yep, I linked to that same line in my comment above. 😉


Add [Vishal Saroj] to Rookie list

Description
Welcome! We are excited to have you on board. This is your first formal step in making it official that you are a part of the Polkadot Heroes program as either a hero or a rookie. Please fill out your profile details in this pull request. Remember to place your profile in alphabetical order in the list, add your profile image to the ./images subfolder of either the Heroes/ or Rookies/ folder, and fill out all the informational fields in your card. You can copy and paste someone else's card and replace their information with your own.
Make sure to preview your additions in the Heroes/README.md or the Rookies/README.md file to confirm it looks as expected.
Checklist:

[x] My name is alphabetically ordered by first name in the README
[x] My profile picture is added to the /images folder of either the Heroes/ or the Rookies/ directory
[x] All the fields are filled out for my profile (see the other profiles for examples)

Just become a Rookie...

@vishal-sys all looks good, do you maybe want to change the profile pic (crop the upper and lower areas so it's only your photo)? If you think it's not needed, let me know and I can merge.

good stuff, happy to see you here @vishal-sys :)

Tysm Zsofi ma'am good to be here (:


Add a new configuration file and save username into it after a successful login

Resolves #40

Merged in ddd48f2371dd69623f0542c09ffe1b5d755a1262 with small name change for consistency. Thanks @thii!


Was something like a smart option added?

https://github.com/timmywil/panzoom/pull/583
Just before this PR was closed because it was incomplete, it was indicated that the feature idea would be coming to pan zoom?
The idea from the PR was:

Adds 'smart' to contain option, to add intelligent sensing to use 'outside' or 'inside' per x and y.

Has it made it in yet or is it still in progress? Is there a ticket tracking the progress?

Yes, the issue was closed in favor of https://github.com/timmywil/panzoom/issues/598, which should cover more use cases.


prisma error

Bug description
Error: @prisma/client did not initialize yet. Please run "prisma generate" and try to import it again.
In case this error is unexpected for you, please report it in https://github.com/prisma/prisma/issues
at new PrismaClient (/home/wisecjgb/nodevenv/backend.wise1ne.com/14/lib/node_modules/.prisma/client/index.js:5:11)
at Object. (/home/wisecjgb/backend.wise1ne.com/utils/prisma.js:2:16)
at Module._compile (internal/modules/cjs/loader.js:1085:14)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
at Module.load (internal/modules/cjs/loader.js:950:32)
at Function.Module._load (internal/modules/cjs/loader.js:790:12)
at Module.require (internal/modules/cjs/loader.js:974:19)
at require (internal/modules/cjs/helpers.js:101:18)
at Object. (/home/wisecjgb/backend.wise1ne.com/routes/hr/rolePermission/rolePermission.controllers.js:2:16)
at Module._compile (internal/modules/cjs/loader.js:1085:14)
How to reproduce

Expected behavior
No response
Prisma information

// Add your schema.prisma

// Add your code using Prisma Client

Environment & setup

OS:
Database:
Node.js version:

Prisma Version

Hey @waheed7866,
Have you tried running prisma generate? If you have, do you perhaps have any more information that could help us reproduce your issue, such as your datamodel?
Thank you!


not work in win7

last source not work in win7..

what do you mean not work? can you give me any more details?

i Compile it, and it can run in win10, but can;t run in win7
missing dll api-ms-win-shcore-scaling-l1-1-1.dll
after i add dll to system.
it show this.
http://puu.sh/qomfr/921b3625db.png

sounds like your windows 7 doesnt have the universal CRT update (https://support.microsoft.com/en-au/kb/2999226). Try seeing if that (or the vs2015 redistributable) works for you. this isn't a project related problem and is user specific.

i had install vs2015, and it should be include universal CRT update

my win7 have  the universal CRT update!!!
i install vs2015 in win7 too....

That DLL might be part of the Windows 10 SDK. Ill take a look at what exports are used from that DLL and see if I can come up with a work around.


unable to select origins on first world join

cannot determine the source of the issue, posting here in case the source is a bug with the mod itself, or an incompatibility with any number of it's add-ons, or a separate mod entirely. please help me resolve this issue.
latest.log

It seems that the origin layer might be experiencing some issue with Requiem. You could try disabling it and see if it causes the issue.

the requiem version has not changed, the previous version of the modpack works just fine, and it has requiem. it was only after updating that the issue reared it's ugly head.

[08:21:48] [main/ERROR]: There was a problem reading Origin layer file requiem:soul_type (skipping): JsonSyntaxException: EntityCondition json type "requiem:start_remnant_gamerule" is not defined.
...
[08:21:48] [main/ERROR]: There was a problem reading Origin layer file origins:origin (skipping): JsonSyntaxException: JsonSyntaxException: EntityCondition json type "requiem:start_remnant_gamerule" is not defined.

Interesting. Try reinstalling Requiem?

Yes, this seems to have been an issue with one of the add-ons (namely Requiem) which probably was incompatible due to an update I made and it wasn't updated yet. I hope that is resolved by now if you have updated to the newest versions. Sorry for taking so long for answering.
I'm closing the issue now, however if the problem still persists please feel free to leave another comment and I'll reopen it.


Weird exception in active_support/cache/dalli_store.rb

Hi and happy new year to  you all :)
I've got a weird problem, where I'm unable to cache a particular item... I'm getting the following error:
NoMethodError: undefined method `>' for false:FalseClass
from /home/app/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/dalli-2.7.6/lib/active_support/cache/dalli_store.rb:105:in `=='

Here's the code:
def average_duration(vspot, venue, from, to)
  cache.fetch(caching_key, expires_in: expire_time) do
    cache_missed_message

    get_average_duration(vspot, venue, from, to)
  end
end

And here's what some of the values are:
[1] pry(#<Widgets::SpotAverageVisitDurationV1>)> caching_key
=> "spot_average_visit_duration_v1_70_7-days"
[2] pry(#<Widgets::SpotAverageVisitDurationV1>)> expire_time
=> 259200 seconds

I've searched all over the issues list, and can't find anything similar... also, when I inspect the code that is apparently breaking, i.e. line 105 in dalli_store.rb it's happening within the #fetch method and not a #== method.
Any help would be greatly appreciated, and I'm happy to share as much as needed in order to fix this possible bug.
Thanks guys, really appreciate this gem and the hard work you've put into it, it's been amazing working with it over the years.

Huh... that's weird...
When I change the caching_key value to spot_average_visit_duration_v1_70_7-day (chop off the trailing 's') or spot_average_visit_duration_v1_70_7-daysx (add a trailing 'x'), it works fine.
It's clear there's something Dalli doesn't like about that key...

OK, I've dug a little deeper, and I can confirm that if it's a brand new key, it will happily cache away. It's only when it attempts to fetch a previously cached key that it will trigger this exception.

@gee-forr What's the class of the key?  Is it a string, a SpotAverageVisitDurationV1, or something else?
My suspicion is that you may be using a complex class for the caching key that doesn't support '=='.  ('!=' on line 105 is probably implemented under the covers using '==', which is why it's reporting a problem with '==')

hey @petergoldstein...
Unfortunately, it's a standard string, here's my implementation:
    def caching_key
      "#{class_key_name}_#{context.product_instance_id}_#{report_interval_identifier}"
    end

@gee-forr What's the class of the value?  If you instantiate such a value in console, does it behave as expected under equality comparisons?

Hi @petergoldstein,
caching_key is simply a string... see below:
[2] pry(#<Widgets::SpotAverageVisitDurationV1>)> caching_key
=> "spot_average_visit_duration_v1_6_about-6-hours"
[3] pry(#<Widgets::SpotAverageVisitDurationV1>)> caching_key.class
=> String
[4] pry(#<Widgets::SpotAverageVisitDurationV1>)> dup_key = caching_key.dup
=> "spot_average_visit_duration_v1_6_about-6-hours"
[5] pry(#<Widgets::SpotAverageVisitDurationV1>)> dup_key.object_id
=><PHONE_NUMBER>2440
[6] pry(#<Widgets::SpotAverageVisitDurationV1>)> caching_key.object_id
=><PHONE_NUMBER>3800
[7] pry(#<Widgets::SpotAverageVisitDurationV1>)> dup_key == caching_key
=> true
[8] pry(#<Widgets::SpotAverageVisitDurationV1>)> dup_key != caching_key
=> false

Hope this helps... if there's anything else I can do to shed some light, let me know :) In the meantime, I've disabled caching for this particular piece of code...

@gee-forr I wasn't asking about the caching key - I was asking about the corresponding cached value.

Hi @petergoldstein, apologies, misunderstood you there :)
It's a Duration object: #<Duration:0x007fefd4e33318 @seconds=0, @negative=false, @total=3300, @weeks=(11/2016), @days=(11/288), @hours=(11/12), @minutes=55> from https://github.com/peleteiro/ruby-duration
That's probably the issue. I'm going to patch that method, and see if I can cache it as something a little more primitive, like a Hash instead.
Thanks for your time and attention, I really appreciate it.


Update downloading images part of kubernetes doc

Coverage remained the same at 51.147% when pulling 8e9c14e698f4de10ea89e00813bffae0e5275267 on ywk253100:170120_kubernetes into 4e84fabd418daa6c405f42c6a8e0884134b5861a on vmware:master.


Problem with bootstrap-treeview folder

Hello!
You've changed repository in commit https://github.com/execut/yii2-widget-bootstraptreeview/commit/c3c2045f552f8a492cd5f103a2cf28cf32343d12
But, you didn't change source path here https://github.com/execut/yii2-widget-bootstraptreeview/blob/master/TreeViewBowerAsset.php#L13
Without change, we have an error "The file or directory to be published does not exist: \vendor\bower/bootstrap-treeview/dist".

Thanks for report! My bower folder was not cleaned, so everything worked fine. I fix it in new version.


enabling serde for Powers; PartialEq for params and keys

Description

adding serdes for Powers
allow the callers to derive PartialEq for UniversalParams and VerifierKey

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[x] Targeted PR against correct branch (master)
[x] Re-reviewed Files changed in the Github PR explorer

not relevant

[x] Linked to Github issue with discussion and accepted design OR have an explanation in the PR that describes this work.
[x] Wrote unit tests
[x] Updated relevant documentation in the code
[x] Added a relevant changelog entry to the Pending section in CHANGELOG.md

just one quick question related to the PR:
so the PartialEq is added for serialization?

No, PartialEq is for accompanying auto-derived Hash trait, motivated by cases where consistent hashing of the verifying key is needed.
For example, the predicate identifier in zexe: pid = H(vk)

Thanks, and fixed.

btw, for the hashing, you should note that the Hash trait in std is not for cryptographic hashing.


refactor diagnostics

motivation: refactor the diagnostics frameworks to seperate between emitting diagnostics and collecting/handling them, this helps creating an API to allow emitting diagnostics from any point at the code without having to pass in a DiagnosticsEngine everywhere
changes:

add newe ObservabilitySystem API to abstract features like diagnostics, metrics and tracing
add new DiagnosticsEmitter API design to [only] emit diagnostics
adjust callsites to always create DiagnosticsEngine using the ObservabilitySystem so that the system are bridged
convert GraphLoading subsystem to use DiagnosticsEmitter instead of DiagnosticsEngine
move the Diagnostic printing code closer the Diganostic handling code in SwiftTool and clean it up
adjust all tests and test utilities to use ObservabilitySystem

note: the code includes several API to allow bridging between the DiagnosticsEngine using the ObservabilitySystem APIs so that we can transition in steps and control the scope of the cahnges. The APIs are marked as deprecated to help trasnition, but are fairly noisy until we make more progress.

@neonichu @abertelrud @elsh this is the first PR towards refactoring the diagnostics subsystem. I worked to create a minimal change-set, but due to the key role of the diagnostics subsystem and how common it is in our API it is still a large amount of files that had to be "touched".
This PR is focused on the core infrastructure. New code is almost exclusively in Observability.swift, rest of change-set is mostly API adaptation. I also migrated one module to the new API to demonstrate how things will look without DiagnosticsEngine. After this is merged, we can start migrating the rest of the modules (starting with Workspace) to the new API and remove the adapters.

@swift-ci please smoke test

@swift-ci please smoke test

swift-ci please smoke test

swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

As far as I am concerned this could be merged at this point.


Lib_Keccak256.sol doesn't work

kafka@largee:~/build/cannon$ npx hardhat test

  MIPSMemory contract
deployed at 0x5FbDB2315678afecb367f032d93F642f64180aa3 by 0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266
preimage initted
preimage updated
comp hash is 0x4a3d5976edd24a1a22f7fae2985b3bd41798eb1176802b50e5612f3e739d3c97
real hash is 0xc5d2460186f7233c927e7db2dcc703c0e500b653ca82273b7bfad8045d85a470

    1) Keccak should work

Not returning the correct empty hash. Easy to reproduce, who wants to fix it? 🥇
It's ported from https://github.com/firefly/wallet/blob/master/source/libs/ethers/src/keccak256.c, I would go about debugging this by diffing the two implementations and disabling rounds/transforms until you find the one that doesn't match.

Found a different implementation, will play with that tomorrow.
https://github.com/brainhub/SHA3IUF
(edit the Makefile)
-CC = c99
-CFLAGS = -std=c99 -Wall -Wextra -Wpedantic -O2 -g
+CC = gcc
+CFLAGS = -Wall -Wextra -Wpedantic -O2 -g

update. have added a function call after this loop :
https://github.com/geohot/cannon/blob/master/contracts/lib/Lib_Keccak256.sol#L94-L101
And after that call i can now print the right ascii values correctly belonging to the hash.
BUT i have 32 chars and need to squeeze that down to 24 :)


Example app links to a 404 on Github

As title...
The link in the README opens a 404 on Github...
https://github.com/quickbirdstudios/XCoordinator#-example

Thanks for pointing out - https://github.com/quickbirdstudios/XCoordinator/pull/51 should fix this.


Drop join on lookup-join

Summary of the changes / Why this improves CrateDB
POC of dropping the join where all outputs are from one side. The performance improvement with this optimization is litte.
Q: select count(t1.a) from doc.t1 join doc.t2 on t1.id = t2.id
C: 1
| Version |         Mean ±    Stdev |        Min |     Median |         Q3 |        Max |
|   V1    |        5.899 ±   22.905 |      2.163 |      3.076 |      3.814 |    232.029 |
|   V2    |        4.836 ±   20.321 |      1.676 |      2.335 |      2.957 |    205.549 |
├---------┴-------------------------┴------------┴------------┴------------┴------------┘
|               -  19.81%                           -  27.36%
There is a 27.12% probability that the observed difference is not random, and the best estimate of that difference is 19.81%
The test has no statistical significance

Checklist

[x] Added an entry in the latest docs/appendices/release-notes/<x.y.0>.rst for user facing changes
[x] Updated documentation & sql_features table for user facing changes
[x] Touched code is covered by tests
[x] CLA is signed
[x] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in the latest docs/appendices/release-notes/<x.y.0>.rst
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

@mfussenegger Could you give me some early feedback ? It works but the performance boost is nothing special. Shall we get this in ?

I'd say 20-30% looks promising enough, so I'd continue.
How does this behave on queries with more data? 5ms is already fairly fast, would be interested seeing the impact on queries that are in the 100ms+ range without it.

I'd say 20-30% looks promising enough, so I'd continue.
How does this behave on queries with more data? 5ms is already fairly fast, would be interested seeing the impact on queries that are in the 100ms+ range without it.

100 times more data lead to the following benchmark:
Q: select count(t1.a) from doc.t1 join doc.t2 on t1.id = t2.id
C: 1
| Version |         Mean ±    Stdev |        Min |     Median |         Q3 |        Max |
|   V1    |       45.073 ±   27.470 |     40.679 |     41.745 |     42.544 |    315.736 |
|   V2    |       31.856 ±   26.484 |     27.489 |     28.419 |     29.175 |    292.208 |
├---------┴-------------------------┴------------┴------------┴------------┴------------┘
|               -  34.36%                           -  37.99%
There is a 99.93% probability that the observed difference is not random, and the best estimate of that difference is 34.36%
The test has statistical significance


NetworkACL Protocl Constants

Added some basic constants for adding NetworkACL Protocols from here https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml

Thanks!


test inheritFDs

Tests that the code changed in https://github.com/dlang/phobos/pull/4934 actually does what it says it does
This isn't perfect, it turns out that testing whether a fd is open in a way that is both posix-portable and doesn't require compiling C is basically impossible. Currently I print a warning if I can't find a way of testing, but that could be a failure instead, I can't decide.
I'd love to know if there's an easier way.

Are you kidding me? I add 60 lines of unittests only and the code coverage says 52% patch coverage and that the project coverage went down?

ping @schveiguy, seeing as you merged the code this is testing.
I think I understand the coverage problem now: I presume the coverage is calculated on linux and therefore only the first attempt in the unittest will be executed.

Are you kidding me? I add 60 lines of unittests only and the code coverage says 52% patch coverage and that the project coverage went down?

CodeCov does nothing more than taking DMD's coverage output (-cov) and building some nice UI around it. To be concrete, the following command is run:
make -f posix.mak std/process.test

which in this case creates std_process.lst in the phobos root directory.
(There is another bug in the DMD coverage generation that requires us to run the coverage statistics per file).
The exact magic can be found here.
You might also be interested in this discussion. In short: DMD purposely doesn't ignore unittest blocks.

I think I understand the coverage problem now: I didn't realise that unittests were counted in the coverage. I presume the coverage is calculated on linux and therefore only the first attempt in the unittest will be executed there

Yes CodeCov shows exactly the coverage output from DMD.

Thanks for the explanation @wilzbach. I do remember that forum discussion now.
By its very nature this unit test will exit as early as possible, so I think the coverage failure should be ignored for this PR.

I'm wondering if it wouldn't be better to actually write a separate D program that can do what we want on any posix platform, and just exec that.

no need for executeShell, TestScript creates a script, we execute that script using the .path to it.

A D (or even just C) program would be better, but I didn't think it was worth the build complications

no need for executeShell, TestScript creates a script, we execute that script using the .path to it.

Oh, wasn't aware of that! For some reason I thought it was just a string.
We still should be testing to see that the output contains some expected file descriptors, to make sure the script is actually doing what we think it should be.

I didn't think it was worth the build complications

Yeah, we would need test directory like in dmd and druntime, along with more Makefiles (shudder).
I wonder if TestScript could be extended to use rdmd instead of a shell!

I wonder if TestScript could be extended to use rdmd instead of a shell!
I think dmd -run would be better, because otherwise you can't run the test-suite for phobos without having built rdmd, which depends on phobos, but if a bug in phobos causes a bug in rdmd...

I found a much easier and more portable way of testing.

Current coverage is 89.38% (diff: 51.85%)

Merging #4948 into master will decrease coverage by 0.02%

@@             master      #4948   diff @@
==========================================
  Files           124        124
  Lines         77033      76984    -49
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits          68872      68812    -60
- Misses         8161       8172    +11
  Partials          0          0

Powered by Codecov. Last update f3a8401...eddc930

Very odd. I can't reproduce the failure locally on FreeBSD 11.0. Everything passes.

I see that the auto-tester is running pretty old FreeBSD (8.4) and things are different there.

Seems like this approach is flawed, can't refer to multi-digit file descriptors in the shell.

You can dup2 to put fds at specific numbers

I've gone back to the old version and added checks for the default fds. I just couldn't any other way working solidly.

LGTM

ping @schveiguy

Auto-merge toggled on


seg fault when running nose tests

Installed according to the guide on the contribution page.
Im running:

Ubuntu 14.04
tensorflow 1.0.0
Python 3.5.1 (default, Mar 14 2017, 15:32:51)

Can you post the complete log?
Are other Tensorflow models running correctly? In my experience segfaults typically happen with GPU issues and/or not enough memory.

This could also be a Tensorflow bug: https://github.com/tensorflow/tensorflow/issues/6968#issuecomment-279060156

hey denny thanks, Iam strongly inclined to believe that its a memory error.
tensorflow: INFO: Creating AttentionLayerBahdanau in mode=eval
tensorflow: INFO:
AttentionLayerBahdanau: {num_units: 10}

tensorflow: INFO: Creating AttentionDecoder in mode=eval
tensorflow: INFO:
AttentionDecoder:
  max_decode_length: 100
  rnn_cell:
    cell_class: GRUCell
    cell_params: {num_units: 8}
    dropout_input_keep_prob: 1.0
    dropout_output_keep_prob: 1.0
    num_layers: 1
    residual_combiner: add
    residual_connections: false
    residual_dense: false

tensorflow: INFO: Creating ZeroBridge in mode=eval
tensorflow: INFO:
ZeroBridge: {}

--------------------- >> end captured logging << ---------------------

----------------------------------------------------------------------
Ran 135 tests in 109.019s

FAILED (SKIP=6, errors=17)
Segmentation fault (core dumped)

This may be a Tensorflow bug and not related to this code, can you try the suggestion here: https://github.com/tensorflow/tensorflow/issues/6968#issuecomment-279060156

Thanks! I'm not sure I needed that, now I don't get the seq fault, but some of the tests are failing. Im going to close this if I should expect failing tests.
--------------------- >> end captured logging << ---------------------

----------------------------------------------------------------------
Ran 135 tests in 62.252s

FAILED (SKIP=6, errors=17)

You should not expect failing test since they are all passing on the CI server. Can you post an error message?

Dropped in on the tests with  nosetests -v -pdb
First error:
/seq2seq/seq2seq/test/models_test.py(154)test_infer()
pred_len = predictions_["predicted_ids"].shape[1]

(pdb) print(predictions.keys())
>>dict_keys(['features.source_ids', 'features.source_len',
 'labels.target_ids', 'features.source_tokens', 'labels.target_len', 'labels.target_tokens'])

So "predicted_ids" isn't a key is the predictions_ dict
The next error is similar to the first and the third error is below:
/seq2seq/seq2seq/test/models_test.py(141)test_train()
-> np.testing.assert_array_equal(predictions_["logits"].shape, [
(Pdb) print(predictions_["logits"])
>>keyError: 'logits'

Hm, interesting. The tests are passing for me locally as well as on the CI server and on my Linux machine. Can you upload/paste the full log somewhere?

Here is a link to the the logs on dropbox

Are you using anaconda by any chance?

It seems like multiple people are having this same issue, but I still haven't been able to reproduce this on any of my machines. I tried Python 3.5, 2.7, CPU and GPU. It must be related to the code here:
https://github.com/google/seq2seq/blob/master/seq2seq/models/seq2seq_model.py#L47

Okay, I think I found it. It seems to actually be a python bug: http://bugs.python.org/issue24931

This should fix it, I hope: https://github.com/google/seq2seq/pull/61
Please open this issue again if it doesn't fix it.

This helped!


[resolves #40] Move fluxible to peer dependencies

CLA is valid!

:+1:

Coverage remained the same at 99.44% when pulling 8261ea07836a62652d267d501f3bc18e0df41197 on fluxiblePeerDep into e29b78550a14c82f8bf0973dd7b0efcf42379e7c on master.


iOS 14.2 - new date/time input pushes web view up after keyboard input

selecting a date input while the keyboard is up, such as during a form with text and date inputs, closes the keyboard but keeps the web view pushed up. Closing the date/time fields then doesn't push the web view back down.
Cordova CLI: 10
Cordova-is 6.1.1
iOS 14.2

Also experiencing this issue in my Ionic app
Cordova CLI: 10
Cordova-is 6.1.1
iOS 14.3

Also experiencing this issue in my Ionic app
Cordova CLI: 10
Cordova-is 6.1.1
iOS 14.3

Facing similar issue but in select with filter input. The keyboard automatically shows up but the view does not come back down after minimizing keyboard. [iOS / iPadOS]

Similar issue. When I tap on a date input, the date picker appears but the content is pushed up to make room for a keyboard that doesn't show.


Implement chess game service

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

0.1.0
GitHub release
0.1.0

Your semantic-release bot :package::rocket:

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

0.1.0
GitHub release
0.1.0

Your semantic-release bot :package::rocket:


Fixing Imbalanced Data

The NER corpus include many more 'O' label than any entities.
How can we fix this using keras?
I tried sample_weight to ajust the loss function during training, but it does not appear to fix the problem fully. What would you suggest?
Thx

In case of Hindi data, there are surely many 'O' entries. Fixing this is not entirely possible, as we would have to go through entire dataset, or create a new one(that is extreme task). We can only make some assumptions, like using only those sentences which have some certain specific number of named entities, using sentences with max_len <= threshold, etc.
I dont understand fixing this by keras. Can you explain more?

That image suggests that you are surely doing something wrong.
How was the output when you were training the model using keras. Was valid. acc increasing steadily(at a optimum rate) and loss decreasing at a good rate?
For handling class imbalances, you can do something like I told in previous comment.

I tried to run the script with default settings, as it can be found in english_NER.ipnb.
The accuracy (and logloss) is stuck at 97.3 from the first epoch.
I'm trying to figure out what is going wrong.

Sorry for late replying.
Were you also getting very low loss (in negative powers of 10) and NaN values during training?

Hello Divesh,
I have a very low loss from the first epoch, I joined a capture of training logs:

The only thing I changed was adding a few parenthis to print functions since I'm running your scripts with python 3, maybe I'm also using a different version of Keras tensorflow, I have keras 2.0.0 and tensorflow 1.0.1 installed on windows 64, which versions did you use initially?
Thanks for helping

The problem is version numbers. I should have made requirements.txt.
I used Keras==1.2.1 and tensorflow-gpu==0.12.1. Though I had tensorflow with GPU support, you can avoid that by installing just tensorflow==0.12.1. Try this in a new env and let me know.
About using python 3, some problems can occur while handling unicodes, but in our case, chances are less.

I got a similar issue that all are predicted to be 'O' for the English dataset, but my issue is even worse as the losses are all nan since the beginning. I will try to match the versions of Keras and tensorflow. Do you have any other advice on this issue? Thanks.

A follow-up with that, it does not seem that the versions of tesorflow and Keras can solve my loss: nan issues. I am wondering if this is due to the gpu vs cpu?

It turns out that I get the same answer with @ArmandGiraud right now. @pandeydivesh15 what was the accuracy?

I trained one model just now. Output in my case:

Stll having this


Live Quiz: Result does not load automatically

Describe the bug

During a live quiz, if the time runs out and the quiz ends, the solution is submitted automatically, the editing is disabled and a message with "The Quiz has ended. Please wait. The results will be loaded automatically." is displayed. The results however are not loaded automatically and you have to refresh the page to see the results.
To Reproduce

Go to 'Course Management'
Create a simple Quiz Exercise (with a short duration), set it to visible and start it
Participate in the Quiz and let the time run out
See the message "The Quiz has ended. Please wait. The results will be loaded automatically."
Results are not loaded automatically, but are visible after refreshing the page

Expected behavior

The results should be loaded automatically after the time has run out.
Screenshots

The screen on which you are stuck after the time has run out.

Thanks for the bug report. I fixed it.


@conda-forge-admin, please rerender

Additional comment:
@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I rerendered the recipe in conda-forge/bipedal-locomotion-framework-feedstock#12.

Done in https://github.com/conda-forge/bipedal-locomotion-framework-feedstock/pull/12 .


fix(install): consume install step/args via action

Currently (without these changes), attempted use of this mixin results in:
installing porter-azure-wordpress...
executing porter install configuration from /cnab/app/porter.yaml
Create Azure MySQL
Error: stat /templates/.template: no such file or directory
err: stat /templates/.template: no such file or directory
Usage:
  azure install [flags]

Flags:
  -h, --help   help for install

Global Flags:
      --debug   Enable debug logging

Error: mixin execution failed: exit status 1
Error: failed to install the bundle: container exit code: 1

(Attempting installation of the azure-mysql-wordpress example bundle)
It seems this mixin needed updating with changes in porter and how/what it communicates to each mixin.
If I understand correctly, porter now sends step data wrapped in the corresponding action to each mixin, like so:
install:
  - azure:
      type: mysql
...

Therefore, I've made amendments to marshal the data into an action, thereby getting all of the data this mixin needs.  I've referenced similar updates in the porter-helm mixin to do so.
Assuming my understanding and approach is correct, let me know if the added test is desirable, or if I/we should just amend the existing unmarshal test.

This was a pretty big oops on my part. So I've cut a new release with your PR and this is available in v0.4.0-ralpha.2+dubonnet.


RESTEASY-1774 - Upgrade HTTP client to 4.5.4

Issue: https://issues.jboss.org/browse/RESTEASY-1774
Upstream Issue: https://issues.jboss.org/browse/WFCORE-3473
EAP Issue: https://issues.jboss.org/browse/JBEAP-13801

@asoldano FYI, I've track down the commit in httpclient causing this test to fails - is this enough to refers to in the release note ? Do you think we should tweak more the test or simply modify our test ?
I've updated this PR to include the modify test, but please let me know if you prefer do take care of this differently!

Hum, weird... not sure what it is failing here. I did not run into that locally...

@asoldano Alessio, just to be sure, i've double check locally on building 4 times the failing test, but still no error:
$ for i in {1..4} ; do mvn clean install ; done | grep -e 'Tests run: ' -e 'BUILD '
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.644 s - in org.jboss.resteasy.test.HeadContentLengthTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.088 s - in org.jboss.resteasy.test.HttpContextTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.019 s - in org.jboss.resteasy.test.PortAssigningTest
[INFO] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.331 s - in org.jboss.resteasy.test.security.BasicAuthTest
[INFO] Tests run: 9, Failures: 0, Errors: 0, Skipped: 0
[INFO] BUILD SUCCESS
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.599 s - in org.jboss.resteasy.test.HeadContentLengthTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.131 s - in org.jboss.resteasy.test.HttpContextTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 s - in org.jboss.resteasy.test.PortAssigningTest
[INFO] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.329 s - in org.jboss.resteasy.test.security.BasicAuthTest
[INFO] Tests run: 9, Failures: 0, Errors: 0, Skipped: 0
[INFO] BUILD SUCCESS
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.688 s - in org.jboss.resteasy.test.HeadContentLengthTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.16 s - in org.jboss.resteasy.test.HttpContextTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 s - in org.jboss.resteasy.test.PortAssigningTest
[INFO] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.334 s - in org.jboss.resteasy.test.security.BasicAuthTest
[INFO] Tests run: 9, Failures: 0, Errors: 0, Skipped: 0
[INFO] BUILD SUCCESS
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.704 s - in org.jboss.resteasy.test.HeadContentLengthTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.158 s - in org.jboss.resteasy.test.HttpContextTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 s - in org.jboss.resteasy.test.PortAssigningTest
[INFO] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.321 s - in org.jboss.resteasy.test.security.BasicAuthTest
[INFO] Tests run: 9, Failures: 0, Errors: 0, Skipped: 0
[INFO] BUILD SUCCESS

Do you have any idea on how I could investigate this more ?

@rpelisse , I'm leaning towards fixing the test affected by the upgrade in a different way; can you check https://github.com/resteasy/Resteasy/pull/1415 and tell me what you think? Basically, in there we're trying calling a resource methods that lasts 10s and want to timeout after 5s of wait. However, the socket timeout is now being effectively set to 2s, so we get a read time out instead of the future timeout. You change would make the test faster, but I think we might have problems from time to time on slow environments, like the Travis CI here. So keeping the longer timeout is probably safer.
If you agree I would close this PR and merge the new one. Please let me know.

@asoldano I think your way is way better! I've +1 your PR and I'm closing this one :)


feature support s3 resource

Proposed changes
issue：#8807

Support create s3 resource
Support create OLAP table with s3 resource
Add storage_cold_medium and remote_storage_resource in DataProperty.
Support for modifying a single data property

Problem Summary:
Describe the overview of changes.
Checklist(Required)

Does it affect the original behavior: (Yes/No/I Don't know)
Has unit tests been added: (Yes/No/No Need)
Has document been added or modified: (Yes/No/No Need)
Does it need to update dependencies: (Yes/No)
Are there any changes that cannot be rolled back: (Yes/No)

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

Could you please provide the sql references? For example how to define S3 resource and how to use it to create table

Could you please provide the sql references? For example how to define S3 resource and how to use it to create table

You can find the syntax in issue #8807


Not Supported 10.0.22000.527

New Windows 11 update has no support for old ini file. Please update.
Thanks in advance!

Duplicate of https://github.com/stascorp/rdpwrap/issues/1698

Duplicate of #1698

No, it is not, that is version .469, I'm asking for .527

Duplicate of #1698

No, it is not, that is version .469, I'm asking for .527

So... Double check termstv.dll version

version .469 is suitable for .527

Duplicate of #1698

No, it is not, that is version .469, I'm asking for .527

version .469 is suitable for .527


[FR] Adding an option to use media link without !

Hello! Could you consider adding an option to set the image property's value as [[image.png]] rather than ![[image.png]]?

Pure text: image.png
Media Link: [[image.png]]
Embedded Media Link: ![[image.png]]

In this way, the property value can become more versatile, as some plugins can access the Media Link format but are not compatible with the third embedded Media format.

Sure, I'll add it!

It's added now to version 1.1.11. Try it our and see how it works for you. Thanks for the suggestion!

It's added now to version 1.1.11. Try it our and see how it works for you. Thanks for the suggestion!

That's great, thank you!  : )


pkgdev mask: offer to send email to gentoo-dev ML

We need to send emails to the gentoo-dev-announce and gentoo-dev mailing lists when last-riting packages. Providing a copy/pastable template (or setting the email for us, ala git send-mail) would make tree cleaning a lot easier.

@thesamesam Could you outline the steps you perform today to last-rite a package with pkgdev mask?

@thesamesam Could you outline the steps you perform today to last-rite a package with pkgdev mask?

The process ("last rites") is described in the devmanual, but let me give my specific steps as I appreciate that's useful too:

Run pkgdev mask
Forget the format it expects because there's no template for name/email/date (I forget if it adds it for me, etc!)
Eventually figure it out by trial-and-error. Write a message like:

# Sam James<EMAIL_ADDRESS>(2022-03-25)
# Abandoned upstream, many bugs.
# bug #123456, bug #....
# Removal on 2022-04-25.
app-misc/foo

Commit it, tagging those bugs with pkgdev commit -b.
Add PMASKED to the KEYWORDS field on each of those bugs.
Copy/paste the package.mask entry I wrote into my mail client and send it to<EMAIL_ADDRESS>and<EMAIL_ADDRESS>with a reply-to of gentoo-dev.
Push.

Thanks for the steps! Never having done a "last-rites" it helps to have your steps laid out like this:
Seems like there are a multiple things that could be addressed here:

Would it be helpful if pkgdev mask accepted multiple -b arguments? (Those would be the same as passed to pkgdev commit)
Some template for the package.mask entry (could then be pre-filled with bug references)
Some interaction with bugzilla to set PMASKED (not sure if that's already implemented?)
Ability to send email (initially I thought the email sending could be handled with git send-email, but this isn't sending patches...).

Would you want for pkgdev mask to be able to do the commit and push all at once?

Thanks for the steps! Never having done a "last-rites" it helps to have your steps laid out like this:
Seems like there are a multiple things that could be addressed here:
[...]

All of these sound great although I wonder if the PMASKED thing could be done on the git hook side on git.gentoo.org -- we could have a new tag like Closes-LastRites or something. I dunno, that sounds a bit ugly, but you get the point.
It should be easy to call pybugz or use python-bugzilla to do that part. But I'd say it's probably less important than the rest.

Would you want for pkgdev mask to be able to do the commit and push all at once?

I'd say no, keep push separate.

* Ability to send email (initially I thought the email sending could be handled with `git send-email`, but this isn't sending patches...).

I'm not quite sure I follow this logic... doesn't git send-email take tree-ish args?
For example, git send-email HEAD^ uses the latest commit as the patch to send. In other words, one process would be: pkgdev mask -> pkgdev commit -> git send-email HEAD^. The commit and sending email parts could probably be added to pkgdev mask using an option or similar so only one command needs to be run.

As I understood it, what @thesamesam is asking for is the ability to send emails like this one to the right lists. Ie, not patches, but just the package.mask comment.

As I understood it, what @thesamesam is asking for is the ability to send emails like this one to the right lists. Ie, not patches, but just the package.mask comment.

Ah, that's fair. It just seems that if email support is added, it would be best to use something else that already has support for it set up (especially assuming many devs already use git send-email for stuff like eclasses) instead of having to inject auth params into yet another config or manually handle auth input.

FWIW I think it'd be worth accepting the minor jank of it looking like a patch given we get the niceties of git send-email.

A first iteration of pkgdev mask --send-email could be just that? Using git send-email under the hood?

Another suggestion is to use something like lr-* scripts from mgorny-dev-scripts. Meaning to use xdg-open with crafted mailto: URL - like here.
How does that sound to you?


pdblp does not handle responseError in ReferenceDataResponse

Code Sample
fun = blpcon.ref(securities, fundamental_fields, [('EQY_FUND_RELATIVE_PERIOD', relativePeriod)])

Problem description
When daily limit has reached, I get TypeError: string indices must be integers
~\.conda\envs\myconda36\lib\site-packages\pdblp\pdblp.py in ref(self, tickers, flds, ovrds)
    362         logger.info('Sending Request:\n{}'.format(request))
    363         self._session.sendRequest(request, identity=self._identity)
--> 364         data = self._parse_ref(flds)
    365         data = pd.DataFrame(data)
    366         data.columns = ['ticker', 'field', 'value']

~\.conda\envs\myconda36\lib\site-packages\pdblp\pdblp.py in _parse_ref(self, flds, keep_corrId, sent_events)
    377             d = msg['element']['ReferenceDataResponse']
    378             for security_data_dict in d:
--> 379                 secData = security_data_dict['securityData']
    380                 ticker = secData['security']
    381                 if 'securityError' in secData:

TypeError: string indices must be integers

When enabling debug, this is trace:
pdblp.pdblp:INFO:Event Type: 'PARTIAL_RESPONSE'
pdblp.pdblp:INFO:Message Received:
ReferenceDataResponse = {
    responseError = {
        source = "bbdbd2"
        code = -4001
        category = "LIMIT"
        message = "uuid: xxxxxxx, SN: xxxxx, sid: xxxxx Daily capacity reached. [nid:xxxx] "
        subcategory = "DAILY_CAPACITY_REACHED"
    }
}

Expected Output
It would be great if _parse_ref() function can understand the PARTIAL_RESPONSE event type and report actual error rather than TypeError which is hiding underlying error.
Version Information
[paste the output of pdblp.__version__ here below this line]
'0.1.8'
Thank you
Thank you for awesome library.

I agree this would be a nice feature to have but will likely not have the time to implement this in the foreseable future. Currently the parsing of the responses happens throughout the library instead of in a centralized place, so implementing this check would be a bit involved. To test would also involve adding mocking since these responses can only be replicated when your limits are hit.

Thanks. At least I have some fixes that I have currently sprinkled the error checking and it worked fine for my use. I will send a pull request on your way soon.

Just sent a new pull request. I am trying to figure out how to link the pull request with this issue. I am completely new to Github workflow.


VSWhere.exe Hard-Coded Path Fails on 32-Bit Windows

There is a bug in the hard-code path specification for the vswhere.exe utility on 32-bit platforms.
Configuration:

Scons: 3.0.4
Python: 2.7.14 on win32
OS: Windows 7 (32-bit)

The vswhere.exe path is hard-coded in vc.py (SCons\Tool\MsCommon\vc.py: line 291 in Scons 3.0.4 and line 289 in Master) as follows:
vswhere_path = os.path.join(
    'C:\\',
    'Program Files (x86)',
    'Microsoft Visual Studio',
    'Installer',
    'vswhere.exe'
)

This causes VS 2017 (14.1) queries to fail on 32-bit platforms with the following cryptic error message:
            scons: warning: VC version 14.1 not installed.  C/C++ compilers are most likely not set correctly.

The appropriate hard-coded path for 32-bit platforms would be:
vswhere_path = os.path.join(
    'C:\\',
    'Program Files',
    'Microsoft Visual Studio',
    'Installer',
    'vswhere.exe'
)

Program files Folder:

'Program Files' [32-bit windows]
'Program Files (x86)' [64-bit windows]

SCons Users Reference: https://pairlist4.pair.net/pipermail/scons-users/2019-March/007645.html

Fixed in #3334

If you get a chance try this out via:
virtualenv venv
. venv/bin/activate
pip install --index-url https://test.pypi.org/simple/ scons==3.0.5a5
scons --version

Good news: this successfully resolved the path problem on 32-bit windows.
Bad news:  a production build using an extremely customized build script fails with 3.0.5a5 that runs successfully with 3.0.4.
Sheepish admission:  I've been using VS 2017 for a long time under Python 2.7 and 32-bit Windows.  I must have manually fixed the path in an earlier release and forgot to report the bug.  For that, I apologize.
Long-winded description:  The custom build script compiles DLLs using mingw-w64 and various MS compilers targeting: release and debug builds, 32-bit and 64-bit architectures, and MSVC runtime compatibility with msvcrt, msvcr80, msvcr90, msvcr100, msvcr120, and ucrt.  For each compiled DLL, import libraries are generated for both the GNU and MSVC compilers using gendef, dlltool, and lib.
Failure in 3.0.5a5:
gendef - lib-random/__build/64vc140d\stk-random-64-crt140-d.dll > lib-random/__build/64vc140d\stk-random-d.def
 * [lib-random/__build/64vc140d\stk-random-64-crt140-d.dll] Found PE+ image
dlltool --as-flags=--64 -m i386:x86-64 --dllname stk-random-64-crt140-d.dll --def lib-random/__build/64vc140d\stk-random-d.def --output-lib lib-random/__build/64vc140d\libstk-random-d.a
dlltool: Can't create .lib file: lib-random/__build/64vc140d\libstk-random-d.a: Invalid bfd target
scons: *** [lib-random\__build\64vc140d\stk-random-64-crt140-d.dll] Error 1

Success in 3.0.4:
gendef - lib-random/__build/64vc140d\stk-random-64-crt140-d.dll > lib-random/__build/64vc140d\stk-random-d.def
 * [lib-random/__build/64vc140d\stk-random-64-crt140-d.dll] Found PE+ image
dlltool --as-flags=--64 -m i386:x86-64 --dllname stk-random-64-crt140-d.dll --def lib-random/__build/64vc140d\stk-random-d.def --output-lib lib-random/__build/64vc140d\libstk-random-d.a
Mkdir("lib-random/_usr/lib/64-140")
ClearReadOnly("lib-random/_usr/lib/64-140\libstk-random-d.a")
Copy("lib-random/_usr/lib/64-140\libstk-random-d.a", "lib-random/__build/64vc140d\libstk-random-d.a")

The first difference in the combined stdout+stderr for both builds is the dlltool error.  This is an error that I have not seen before.

I just pushed out 3.0.5 release.
Please bring this issue the scons-users mailing list.
Can you make a simple reproducer?
Do you think the issue is due to some difference in PATH ?
On Tue, Mar 26, 2019 at 4:31 PM jcbrill<EMAIL_ADDRESS>wrote:

Good news: this successfully resolved the path problem on 32-bit windows.
Bad news: a production build using an extremely customized build script
fails with 3.0.5a5 that runs successfully with 3.0.4.
Sheepish admission: I've been using VS 2017 for a long time under Python
2.7 and 32-bit Windows. I must have manually fixed the path in an earlier
release and forgot to report the bug. For that, I apologize.
Long-winded description: The custom build script compiles DLLs using
mingw-w64 and various MS compilers targeting: release and debug builds,
32-bit and 64-bit architectures, and MSVC runtime compatibility with
msvcrt, msvcr80, msvcr90, msvcr100, msvcr120, and ucrt. For each compiled
DLL, import libraries are generated for both the GNU and MSVC compilers
using gendef, dlltool, and lib.
Failure in 3.0.5a5:
gendef - lib-random/__build/64vc140d\stk-random-64-crt140-d.dll > lib-random/__build/64vc140d\stk-random-d.def

[lib-random/__build/64vc140d\stk-random-64-crt140-d.dll] Found PE+ image
dlltool --as-flags=--64 -m i386:x86-64 --dllname stk-random-64-crt140-d.dll --def lib-random/__build/64vc140d\stk-random-d.def --output-lib lib-random/__build/64vc140d\libstk-random-d.a
dlltool: Can't create .lib file: lib-random/__build/64vc140d\libstk-random-d.a: Invalid bfd target
scons: *** [lib-random__build\64vc140d\stk-random-64-crt140-d.dll] Error 1

Success in 3.0.4:
gendef - lib-random/__build/64vc140d\stk-random-64-crt140-d.dll > lib-random/__build/64vc140d\stk-random-d.def

[lib-random/__build/64vc140d\stk-random-64-crt140-d.dll] Found PE+ image
dlltool --as-flags=--64 -m i386:x86-64 --dllname stk-random-64-crt140-d.dll --def lib-random/__build/64vc140d\stk-random-d.def --output-lib lib-random/__build/64vc140d\libstk-random-d.a
Mkdir("lib-random/_usr/lib/64-140")
ClearReadOnly("lib-random/_usr/lib/64-140\libstk-random-d.a")
Copy("lib-random/_usr/lib/64-140\libstk-random-d.a", "lib-random/__build/64vc140d\libstk-random-d.a")

The first difference in the combined stdout+stderr for both builds is the
dlltool error. This is an error that I have not seen before.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/SCons/scons/issues/3333#issuecomment-476894521, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAFBNHKvytRxk_aLDp6uTvBC9muSXy76ks5vaq3GgaJpZM4cKI3T
.

I have installed 3.0.5 and get the same behavior.  This time the path was the bare minimum for python, scons, and windows.
Time permitting, I will see if I can isolate the problem tomorrow.
I believe the first failure is when running dlltool on the msvc cross-compiled 32-bit to 64-bit binary.  I am not ruling out a path problem.  For the mingw-w64 tools to generate the import library I am manually adding the mingw-w64 path (i.e., env.AppendENVPath('PATH', cls.MINGW_BIN)) to the environment.
It may be easier to isolate the problem in the source rather than conjure a simple reproducer.

o.k. one of the notes for the release is:
- Change the default for AppendENVPath to delete_existing=0, so path
order will not be changed, unless explicitly set (Issue #3276)
So AppendENVPath's default behavior is changed slightly.
If you want the same behavior as before add delete_existing=1 to all your
AppendEnvPath, or at least your mingw related ones?
-Bill
On Tue, Mar 26, 2019 at 5:56 PM jcbrill<EMAIL_ADDRESS>wrote:

I have installed 3.0.5 and get the same behavior. This time the path was
the bare minimum for python, scons, and windows.
Time permitting, I will see if I can isolate the problem tomorrow.
I believe the first failure is when running dlltool on the msvc
cross-compiled 32-bit to 64-bit binary. I am not ruling out a path problem.
For the mingw-w64 tools to generate the import library I am manually adding
the mingw-w64 path (i.e., env.AppendENVPath('PATH', cls.MINGW_BIN)) to the
environment.
It may be easier to isolate the problem in the source rather than conjure
a simple reproducer.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/SCons/scons/issues/3333#issuecomment-476916949, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAFBNGvmomc-NBEf4kVflNbRL34tc3oUks5vasHZgaJpZM4cKI3T
.

Adding delete_existing=1 to the AppendENVPath did not change the erroneous behavior.
However, changing AppendENVPath to PrependENVPath for mingw-w64 resulted in successful builds.
I need to try to narrow down the problem case(s).  It appears to be for an MSVC 64-bit build when the Mingw-w64 tools (gendef and dlltool) are added to the end of the path.  It seems like a conflicting change to the environment perhaps. I am surprised moving the Mingw-w64 tools to the front of the path works.  There is an unintended consequence that I do not fully understand yet.

More information.
When comparing the environment dumps between 3.0.4 and 3.0.5, the following folders are at the end of the 'ENV': { 'PATH': '...'} in 3.0.5 but not in 3.0.4:

C:\ProgramData\chocolatey\bin
C:\msys64
C:\msys
C:\cygwin64\bin
C:\cygwin\bin
C:/Program Files\Java\jdk1.8.0_172\bin

Only the C:\cygwin\bin and java folders actually exist locally.
AppendENVPath for the Mingw-w64 tools after the cygwin tools is the root cause of the problem.  The cygwin version was never intended to be used.  This explains why adding delete_files=1 to AppendENVPath did nothing while PrependENVPath was successful (i.e., the mingw folder is before the cygwin folder).
I don't know where or when these folders are added yet.  None of them were on the system path when SCons was launched.

Hmm.
I thought the changes that were looking new locations only added paths they
found tools to PATH.
Can you make a simple SConstruct and dump PATH for 3.0.4 and 3.0.5?
On Tue, Mar 26, 2019 at 8:16 PM jcbrill<EMAIL_ADDRESS>wrote:

More information.
When comparing the environment dumps between 3.0.4 and 3.0.5, the
following folders are at the end of the 'ENV': { 'PATH': '...'} in 3.0.5 but
not in 3.0.4:

C:\ProgramData\chocolatey\bin
C:\msys64
C:\msys
C:\cygwin64\bin
C:\cygwin\bin
C:/Program Files\Java\jdk1.8.0_172\bin

Only the C:\cygwin\bin and java folders actually exist locally.
AppendENVPath for the Mingw-w64 tools after the cygwin tools is the root
cause of the problem. The cygwin version was never intended to be used.
This explains why adding delete_files=1 to AppendENVPath did nothing while
PrependENVPath was successful (i.e., the mingw folder is before the cygwin
folder).
I don't know where or when these folders are added yet. None of them
were on the system path when SCons was launched.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/SCons/scons/issues/3333#issuecomment-476952830, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAFBNHEZt3p8SpReWS8-a_g4OwHzJ2cVks5vauKEgaJpZM4cKI3T
.

I opened a new issue with more information: https://github.com/SCons/scons/issues/3336
This contains annotated selections from the environment dump.
There is another difference that I am trying to document at the moment:
There are also 4 additional builders in the MSVC environment for 3.0.5 that did not exist in 3.0.4:
Ignore the null addressed.  I  replaced the actual adresses with 0x00000000 for diff purposes.

Environments sequence:
Names: target bits [32|64]
       compiler [mgw|vc]
       msvcr [60|80|90|100|110|120|140]
       mode [d|r]

Environment sequence:
    32mgw60d
    32mgw60r
    32vc80d
    32vc80r
    32vc90d
    32vc90r
    32vc100d
    32vc100r
    32vc110d
    32vc110r
    32vc120d
    32vc120r
    32vc140d
    32vc140r
    64mgw60d
    64mgw60r
    64vc90d
    64vc90r
    64vc100d
    64vc100r
    64vc110d
    64vc110r
    64vc120d
    64vc120r
    64vc140d
    64vc140r

note: 64-bit msvc 2005 was not run

scons_jcb_304_zero.txt
scons_jcb_305_zero.txt

fwiw, substfile/textfile were intentionally added to defaults, should not affect anything you're doing.

The attached files are the env dumps for 3.0.4 and 3.0.5 with the addresses changed to zero.
Environments sequence:
Names: target bits [32|64]
       compiler [mgw|vc]
       msvcr [60|80|90|100|110|120|140]
       mode [d|r]

Environment sequence:
    32mgw60d
    32mgw60r
    32vc80d
    32vc80r
    32vc90d
    32vc90r
    32vc100d
    32vc100r
    32vc110d
    32vc110r
    32vc120d
    32vc120r
    32vc140d
    32vc140r
    64mgw60d
    64mgw60r
    64vc90d
    64vc90r
    64vc100d
    64vc100r
    64vc110d
    64vc110r
    64vc120d
    64vc120r
    64vc140d
    64vc140r

note: 64-bit msvc 2005 was not run

scons_jcb_304_zero.txt
scons_jcb_305_zero.txt

Please put this info in the new bug. This bug is closed.


feat: add cli releases

There's currently no way to consume the Kratix CLI other than cloning and compiling the binary yourself.
Let's improve this by automatically creating releases of the CLI, so the users can download the compiled binary for their OS directly from Github.
We can use release-please with go-releaser to make the entire process very simple.

Go Releaser investigation
Looking at go-releaser it acts upon the creation of a git tag, it doesn't create the tag for you. It will:

create the binaries (multi arch)
create a github release at the tag
upload the binaries to the release
add auto-generated release notes from commit history (can be customised) to the github release
set an go ldflag for the version when building the binary so we can support kratix-cli --version without having to edit the code

We can use github actions workflow that already exists, or write it by hand in circleci (former is probably easier).
Release-please investigation
Looking at release-please it autogenerates a PR that is the placeholder of the next release. The PR contains release notes, and the PR is continually updated as new commits get pushed, example. The PR is created via github workflow. the release note generation is a bit more clever than go-releaser, it uses convention commit to filter out whats a feature by commits prefixed with feat:, and bug fixes from fix:. When you merge the PR (which just updates the CHANGELOG file) it:

Creates a tag
Create a github release from the tag, adds the release notes

image stolen from https://danwakeem.medium.com/improve-your-github-releases-10x-with-this-one-simple-action-56e59e46dd85

Release-please does not doing anything related to building code. They recommend you have other tooling that gets triggered on Github releases being created be responsible for uploading artifacts to the release. Rip grep is an example of a CI using Release-please that has a github action to trigger on a release being created, and then manually uploads the binaries.
Questions

Does goreleaser and release-please play well together?

it seems yes! Not much documentation, but a big project as an example to copy is k8sgpt cli. They use release-please to handle release notes and manual releases, and then delegate to goreleaser to upload the artifacts.

are auto-generated release notes good enough?

we could do a manual release process with manual release notes if we wanted.

do we want automatic or manual releases?

if automatic, we can use the Kratix approach and do a release on every green run of main by pushing a new tag at the end of CI (if using goreleaser). Unclear how to do automatic releases with release-please, and tbh it seems against the point of it
if manual, we can manually push tags (if using goreleaser) or manually merge release-please PR (if using release-please)

Proposal
We use go release to release, and follow the Kratix convention of pushing a new tag on every green run of main.

after chatting with @catmo-syntasso @kirederik we're going to try out the 2nd approach of using release-please combined with gorelaser. Two reasons:

its different release process to Kratix, we might learn we love/hate it/something in-between
since its an early product we might be doing lots of small commits to kratix cli for bug fixes, non-code changes etc, which made make the releases quite noisy. Doing manual releases lets us batch up

draft PR open, next steps in development documented in the PR


Cannot Verify With Public RSA key

I followed the steps here this file: https://github.com/dgrijalva/jwt-go/blob/master/http_example_test.go
I generated the keys using the following:
openssl genrsa -out key256.rsa 4096
openssl rsa -in key256.rsa -pubout > key256.rsa.pub
When I try to parse the key like this:
verifyKey, err = jwt.ParseRSAPublicKeyFromPEM(verifyBytes)

I get the error:
Key must be a PEM encoded PKCS1 or PKCS8 key
I am able to check verify the token using the exact same public key on jwt.io.  The key is a text file in the format:
-----BEGIN PUBLIC KEY-----
All The Key stuff
---END PUBLIC KEY-----

I can verify locally, but not when running from a aws lambda function where I pull the public key from an environment variable.  I think it's stripping out the line breaks, which causes the parsing of the public key to fail, nothing to do with jwt-go.