Dict manager

Passing:

dict_read
dict_write
dict_update

Codecov Report

Merging #118 (6128817) into main (207bbbf) will increase coverage by 1.55%.
The diff coverage is 84.37%.

@@            Coverage Diff             @@
##             main     #118      +/-   ##
==========================================
+ Coverage   71.40%   72.96%   +1.55%
==========================================
  Files          12       13       +1
  Lines         647      736      +89
==========================================
+ Hits          462      537      +75
- Misses        185      199      +14

Impacted Files
Coverage Δ

src/lib.rs
0.00% <ø> (ø)

src/memory_segments.rs
96.96% <ø> (ø)

src/relocatable.rs
94.28% <0.00%> (-5.72%)
:arrow_down:

src/dict_manager.rs
88.88% <88.88%> (ø)

src/cairo_runner.rs
69.49% <100.00%> (-3.07%)
:arrow_down:

src/ids.rs
43.75% <100.00%> (+9.13%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[WFLY-8841] Update of Elytron security transport guarantee tests to work with Ely…

…tron

removed *.properties files as this info is now created directly via WebTestsSecurityDomainSetup
removed localhost.keystore as it is actually not required for the tests to work
code formatting and import optimizations too

Modify 'integration/web/security/tg' tests to be able to run with Elytron. This is a followup for #10111
https://issues.jboss.org/browse/WFLY-8841

Deprecated by https://github.com/wildfly/wildfly/pull/10111


Error when pulling docker image

Expected Behavior
Docker image pull successful
Actual Behavior
error pulling image configuration: download failed after attempts=1: unknown blob
Steps to Reproduce the Problem

Try pulling the docker image

Specifications

Version:
Platform:
Subsystem:

ghcr links got broken when I tweaked the account name (Arriven -> arriven, case sensitivity doesn't and shouldn't affect URLs at all, every other related functionality like working with the repo via ssh/https works fine which is weird since docker image was the only part of repo that used lowercase variant from the beginning). I triggered a new version and that seems to have fixed it


Updating Windows Service Test Harness

Additions to the Windows Service Test Harness Include:

Renaming of the files from DriverInstaller.ps1 &  DriverInstaller.Tests.ps1 to ServiceInstaller.ps1 & ServiceInstaller.Tests.ps1.
Update to New-ATHDriverService & Remove-ATHDriverService to New-ATHService & Remove-ATHService.
Added support to Win32OwnProcess/Win32ShareProcess service installs, not just drivers
Added variant support to include Win32 API, WMI, sc.exe, and Registry.
Updated Remove-ATHService to support removal of a service via registry deletion.

Hi @mgraeber-rc,
I updated the script to fix all of those issues. Here is a brief overview:

Script now compiles a service binary on the fly. This binary doesn't have the "service" related functionality so starting the service will fail.
I consolidated the outputs for Win32 Service and Driver Services
Added more Pester Tests for New-ATHService and Remove-ATHService


Crash on opening console

I found the conflicting mod. It's Autonomous ReShade. You have to choose one of them until a fix comes.

Did you test latest release here? Don't know now if this was posted before or after it now...
Seems to work just fine for me with latest release here, that is why I'm surprised a bit.


[serval] Add a RAM board?

As found in https://github.com/130s/hut_10sqft/issues/479#issuecomment-714631287, there might be a room for adding 1 more RAM board on serval.
Since serval is still very much in use (despite I was trying to sell a few months ago), it's worth seeking to add more RAM.
Question is whether RAM of these days work with this 9 years old laptop. Not even sure what to look.

Tech support shared with me a recommendation.

Your system can have a maximum of 16 GB (4x4 GB DDR3 SDRAM at 1333MHz) as your system came with 12GB that empty slot would bump you to the max with a 1 x 4GB stick. A quick search on google gave me the following which should work:
https://www.amazon.com/Samsung-M471B5273DH0-CH9-DDR3-1333MHZ-SO-DIMM/dp/B0051SQYBU

Thanks for RAM recommendation! I'll give a shot with that one (and I understand it's my liability).

Added a RAM.
$ free -m
              total        used        free      shared  buff/cache   available
Mem:          15990        8947         263         181        6779        6538
Swap:         12263           0       12263


NPM TypeScript type definitions

This change adds a README and package.json.
The plan is to publish everything committed under types/public
Resolves #27

@ColbyTresness - good feedback, thank you!! mind taking another look?

Looks great to me!

Is there any ETA for publishing this package to npm? It would be great to have an official types package for Node.js Azure Functions.


Basic OTel support

Adding basic OpenTelementry (OTel) support to the Sentry SDK:

Adding a OTel SpanProcessor that can receive spans form OTel and then convert them into Sentry Spans and send them to Sentry.
Adding a OTel Propagator that can receive and propagate trace headers (Baggage) to keep distributed tracing intact.

we need a line in setup.py in extras_require


[Status] Declaration-site variance implementation

This issue is intended to hold information about the current implementation status of the declaration-site variance feature in Dart (dart-lang/language#524).
This issue might be morphed into an implementation issue in the future, if we decide that we wish to proceed and implement this feature fully (and when we know exactly how to do it). But at this point is has no connection to any request for implementation, it just describes the current status in order to help clarifying the way ahead. No label fits really well, but it is 'language-discussion' for now.
Declaration-site variance is tested in this directory. It contains 39 test libraries. In the current situation (df2927553782defdf6046e0389ba12a5b193d0c6) we have the following failures:

Configuration dart2wasm-hostasserts-linux-x64-d8 fails in every test, so that configuration will be ignored in the following.
Test variance_in_inference_error_test expects compile-time errors, and hence it is not executed. The analyzer passes the test, and all CFE configurations fail (and they are the ones with no backend, because it is not executed).
Tests variance_downwards_inference_test, variance_in_inference_test, variance_inout_inference_test pass on the analyzer, and all CFE configurations fail.
Tests variance_in_subtyping_test, variance_inout_subtyping_test pass on the analyzer, on CFE configurations with no backend, and on CFE configurations dart2js and dartdevk, but it fails on all other CFE configurations (dartk, dartkp).

In summary:

There are test failures with the CFE for in_inference_error (compile-time only).
There are test failures with the CFE for {downward,in,inout}_inference.
There are test failures with the CFE with a backend for {in,inout}_subtyping.

So we seem to have the following implementation shortcomings:
There are missing+spurious compile-time errors associated with inference and contravariance, in_inference_error, log. Apparently, contravariant type parameters are treated as covariant type parameters during inference. During type check, the correct check is performed, so the inferred type argument causes an argument passing error.
There are spurious compile-time errors associated with inference and contravariance, downwards_inference, log. Again, it looks like inference ignores contravariance.
There are faulty compile-time errors associated with inference and invariance, inout_inference, log. Again, it looks like inference ignores invariance.
There are unexpected run-time errors associated with contravariance and subtyping with non-JS backends, in_subtyping, log. Apparently, the run-time subtype test ignores contravariance (so C<num> is C<int> yields false even though it should yield true when C's type parameter is contravariant).
Finally, there are unexpected run-time errors associated with invariance and subtyping with non-JS backends, inout_subtyping, log. Again, the run-time subtype test seems to ignore invariance (as usual, by treating it as if it were covariance).
In summary, there is work to do on inference and variance, and on run-time type tests and variance, when the specified variance is contravariance or invariance. These results are relative to the given tests, so if we change the specification of variance then we will need to update the tests and the tool behavior accordingly.
Here is an example which currently shows that the behavior of non-JS backends is consistent with the assumption that type tests involving invariance or contravariance are treated as if the variance were covariance.
class Upper {}
class Middle extends Upper {}
class Lower extends Middle {}

class Exactly<inout X> {}
class Contravariantly<in X> {}

void main() {
  dynamic dynInMiddle = Exactly<Middle>();

  print('Before 1');
  Exactly<Upper> inUpper = dynInMiddle; // Should throw, (1). Doesn't.
  print('After 1');
  Exactly<Middle> inMiddle = dynInMiddle; // Should succeed, (2). OK.
  print('After 2');
  Exactly<Lower> inLower = dynInMiddle; // Should throw, (3). OK.
  print('After 3');

  dynamic dynCtMiddle = Contravariantly<Middle>();
  Contravariantly<Upper> ctUpper = dynCtMiddle; // Should throw, (4). Doesn't.
  print('After 4');
  Contravariantly<Middle> ctMiddle = dynCtMiddle; // Should succeed, (5). OK.
  print('After 5');
  Contravariantly<Lower> ctLower = dynCtMiddle; // Should succeed, (6). Throws.
  print('After 6');
}

Checked status files: dartdevc skips all variance tests (and says that DDC will be gone before variance is released), but dartdevk doesn't skip them, and there are no other skip directives for these tests.


[IA-2920] [IA-2914] [IA-2917] PPW fixes for Galaxy and runtime environment variables

JIRAs:
https://broadworkbench.atlassian.net/browse/IA-2914
https://broadworkbench.atlassian.net/browse/IA-2920
https://broadworkbench.atlassian.net/browse/IA-2917
This PR fixes Galaxy creation under PPW, and correctly sets environment variables for all runtime types under PPW.
This PR does not depend on the PPW feature branch; it can merge to dev anytime.
Tested manually using a fiab.
<!--
Hello, friend!
Remember to mention what sort of testing/verification you performed in the course of building this PR, i.e. checking functionality in the browser locally.
Thanks!
--!>

I tested backwards compatibility against dev too, looks good. 👍


How can i get radar resolution in Carla?

Is the radar resolution available in Carla? I can't find it anywhere.
Please tell me how can i get it, thanks very much!

@kannidekan that concept does not apply to our "radar" because the data generated by the radar is not given in a "per-object" way. In other words, the radar is not attempting to differentiate between multiple targets. Instead, it is providing information about multiple locations that could correspond to the same target (object).

@germanros1987 Ok, i got it. Thanks very much!


feat: Compile-time "Animation" creation

Current Behavior
Currently, the Animation structures are constructed at runtime, which works well for dynamic and interactive applications.
Desired Feature
I propose adding the capability to build Animation structures at compile time. This feature would allow developers to define animations that are static and unchanging throughout the application's life, ensuring these animations are constructed and optimized during compilation, reducing runtime overhead and potentially improving the application's overall performance. (The main reason is for design purposes)
Possible Implementation
I believe this feature could be implemented by providing a macro or a set of const functions that allow for the construction of Animation structures with fixed parameters. This way, developers can opt-in to compile time construction where it makes sense for their application.

Thanks for the suggestion, and sorry for the delayed response.
It's an interesting Idea. However, it is unclear to me if the value would be worth the added complexity. Even animations that never need to change can be created at startup without noticeable performance cost.
If someone proposes a concrete implementation (via a pull request), I may consider merging it. But even in that case, I may reject the PR if I feel it's adding too much complexity.
If you would like to try creating a PR, make sure to:

gate that functionality behind a new feature flag named unstable-comptime
write automated tests

That being said, if it can be done without much more complexity than a handful of simple const functions, then I am up for it :smiley:


4082 Fix retrying of failed CertificateRequests

What this PR does / why we need it:
This PR fixes a bug where failed certificate issuance is not retried by deleting the failed CertificateRequest in the next issuance cycle so that a new one gets created for the same revision.
Which issue this PR fixes:
fixes #4082
Special notes for your reviewer:
Alternative approches:

Change the revision mechanism so that the revision of a Certificate is bumped after the issuance has failed similarly to how it's done now after it has succeeded
Delete the failed CertificateRequest at the point where we exit the back off period

I have tested the fix manually- see https://github.com/jetstack/cert-manager/issues/4082#issuecomment-865292890 for how to reproduce the bug.
Release note:

Fix a bug where failed Certificate Requests were not retried

/kind bug

/assign

Looks good to me, and this implementation makes sense.
At first, increasing the revision number seemed like the right thing to do, however this breaks the semantics of the revision number being an actual issued revision.
I added a comment about the static backoff leading to downtime which we should look at tackling.
/lgtm
/cc @MattiasGees


volumio : fails to set media - requires extra metadatas

dlna.py run against Volumio returns "ERROR:root:Action Failed".
adding:
<DIDL-Lite xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:upnp="urn:schemas-upnp-org:metadata-1-0/upnp/" xmlns:dlna="urn:schemas-dlna-org:metadata-1-0/" xmlns:arib="urn:schemas-arib-or-jp:elements-1-0/" xmlns:dtcp="urn:schemas-dtcp-com:metadata-1-0/" xmlns:pv="http://www.pv.com/pvns/" xmlns="urn:schemas-upnp-org:metadata-1-0/DIDL-Lite/"><item id="0$1$12$16583R2268170" refID="0$1$8I2268170" parentID="0$1$12$16583" restricted="1"><res protocolInfo="http-get:*:audio/wav:DLNA.ORG_PN=WAV;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01700000000000000000000000000000" >http://example.com/test.wav</res></item></DIDL-Lite> to  fixes this.
this I extracted from a test run of gupnp-av-cp  (strace of an mp3) and adapted to the wav test file.
volumio runs upmpdcli. I sorted this out by adding logelevel = 6 and logfilename = /var/log/upmpdcli.log and running systemctl restart upmpdcli. With vanilla dlna I get:
:2:src/upmpd.cxx:132::checkContentFormat: didl parse failed
:2:src/avtransport.cxx:393::set(Next)AVTransportURI: unsupported format: uri http://example.com/test.wav metadata :2:libupnpp/device/device.cxx:354::UpnpDevice: Action failed: SetAVTransportURI code -101

this is volumio 2.238 running on an Odroid C2.
PS: playback and stop work fine.

as of now I stressed upmpdcli a bit by removing items of the metadata. The res element URI as content and the protocolInfo attribute are required per upmpdcli log. Other fields are not yet tested (or already removed from previous comment).


No Hunger - hide hunger bar

Hiya. I noticed that receiving the Hunger effect when the No Hunger tweak is enabled causes the bar to completely empty, which is probably by design to cause starvation damage. However, it feels a little odd for the entire bar to just get obliterated upon eating Rotten Flesh or the like, so I wanted to suggest hiding the hunger bar completely if the tweak is enabled.
The hunger effect is conveyed clearly enough by the potion effect icon imo so it's not an issue of clarity - having the bar despite the mechanic being pretty much disabled seems like clutter. Hearty Meals seems to solve this nicely by moving around bars.  Just wanted to mention also that upon clearing the Hunger effect, the hunger bar doesn't go back to full, which seems to go against what the tweak name implies.

the hunger bar in only full if you have full health.

Just for anyone else reading, Better Hunger works great with this to hide the food bar and move the bubble bar down to replace it.


CASSANDRA-18428: Adding equals/hashCode override for the ServerEncryptionOptions

Thanks for sending a pull request! Here are some tips if you're new here:

Ensure you have added or run the appropriate tests for your PR.
Be sure to keep the PR description updated to reflect all changes.
Write your PR title to summarize what this PR proposes.
If possible, provide a concise example to reproduce the issue for a faster review.
Read our contributor guidelines
If you're making a documentation change, see our guide to documentation contribution

Commit messages should follow the following format:
<One sentence description, usually Jira title or CHANGES.txt summary>

<Optional lengthier description (context on patch)>

patch by <Authors>; reviewed by <Reviewers> for CASSANDRA-#####

Co-authored-by: Name1 <email1>
Co-authored-by: Name2 <email2>

The Cassandra Jira

The code-style is here, just for reference:
https://cassandra.apache.org/_/development/code_style.html

Thanks @Mmuzaf for the review. I'll take a look at those soon.

@Mmuzaf I have opened a new PR#2507 hence will close this. Can you please review that new PR? Thanks


Can this project deal with datasets with over 2 classes?

Hello, I wanna ask about if this project can dealt with datasets with over 2 classes, Like cifar10?

Yes.
Just set the nb_classes variable to the number of classes you want. I'm not sure if AlexNet can accept inputs as small as in the CIFAR 10 dataset. You can possibly remove some pooling layers to accommodate small sized image.
Best,
Rahul

@duggalrahul Hello, I also wanna ask about if the values in mean_subtraction (like 123.68 in img = T.set_subtensor(img[:,0,:,:],img[:,0,:,:] - 123.68)) need to be changed and how to make sure these values for the different image data sets, like cifar 10? Moreover, should I resize the images in (227, 227, 3) or (224, 224, 3)?

Hello, why did you use nb_classes to be 2??

@G33kyKitty  Because he has used Pre-trained weights for Binary Classification. (Cat/Dog)

Ok thank you @Gokkulnath ..


Clear Editor Selection When Find Widget Is Closed

(I Submited a PR for this. Resubmiting now with tests)
This causes the editor selection to be cleared, when the Find
widget is closed.  The cursor will be placed at the beginning of
where the selection was before it was cleared.
The purpose of this change is to mitigate the inconvenient assumption
that all searches will result in a need to type over the searched text,
which seems to rarely be the case.  Currently, if a person wishes to exit
the Find widget after performing a search, they will need to type the
escape keystroke once to close the Find widget.  Then, they will
need to type the escape keystroke again to clear the highlighted
selection from the search.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: brendoncrawford sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Is the build checks going to re-run at some point?

Anything I should do to make checks pass?

This requires UX exploration so I'll suggest we discuss in details in issues first before making changes. thanks anyways for your help!


Change DB icon and obs source value

Hi there! I'm wondering if there is a way to change a MD button value and input that value to an obs text source so I could create a scoreboard directly into obs without the need of an external app once it's kinda hard to manage external sources value.
What's my idea: a way to increase/decrease a number in a MD button and input this number to an obs text source. I'd have 4 buttons for this: one to increase home team score, another one to decrease this score and the other two to do the same for visitor team score.
Change the button value is not mandatory. Change the obs source value is the point here.
I could overcoming this issue by adding multiple buttons with static numbers let's say 10 buttons for each team but it'd take a huge amount of buttons or maybe I could add a variable to a button that changes the text source target so I'd have one button to control the text source target and unique buttons for the numbers. It would still take unacessary extra buttons.
I've tried to find a way on myself with no success up till now.
If there is not this possibility yet, I strong suggest its adding 🤠
Cheers and congrats for your great work!
EDIT: I've just figured out how do it. I created an integer variable for count up/down and set it to change the obs source value to its own value.

Wrong repository


cannot build module with cloudflare

go version go1.15 linux/amd64
# github.com/smallstep/certificates/authority/provisioner
/root/go/pkg/mod/github.com/smallstep/certificates@v0.15.0-rc.1.0.20200506212953-e855707dc274/authority/provisioner/jwk.go:155:24: assignment mismatch: 3 variables but x509util.SplitSANs returns 4 values
/root/go/pkg/mod/github.com/smallstep/certificates@v0.15.0-rc.1.0.20200506212953-e855707dc274/authority/provisioner/x5c.go:197:24: assignment mismatch: 3 variables but x509util.SplitSANs returns 4 values
2020/08/16 09:18:03 [INFO] Cleaning up temporary folder: /tmp/buildenv_2020-08-16-0917.888096838
2020/08/16 09:18:03 [FATAL] exit status 2

Hi @Mon-ius,
I'm having the same issue, but fortunately, I have a backup of the Caddy 2.1.1 binary + CloudFlare module, which I'll attach in the meantime: caddy.zip
Cheers.

I have already compiled with go 1.4 version. There is a bug for go-quic with 1.5. Thx, man.


how to use with Promise or callback

I am struggling to use this library in my use case. I have an array of symbols that I map through and for each symbol I want to use the SMA function. The problem is that I have no way to wait for the calculation to finish on each symbol before calculating the next one.
Am I missing something? I have looked everywhere for examples of a callback function that I can promisify with bluebird.

The API is synchronous. You dont need a promise or callback.


V2.1 tests (validating upload protocol version and encryption key protocol)

API change check
APIView has identified API level changes in this PR and created following API reviews.
com.azure:azure-storage-blob-cryptography


Support for HLSL Shader Model 6 in DX12

Hi,
Are there plans to support the newest features such as HLSL 6 wave intrinsics? I understand this would imply switching to the newest shader compiler toolchain (DXC).
Thanks for your great work!

Hi!
Yes I am planning to switch to DXC in D3D12 backend.


Allow stage/revertSelectedRanges keybinding not just in diffEditor

#93706 introduced default keybindings for stageSelectedRanges, unstageSelectedRanges and revertSelectedRanges as per issue #93564, but they don't work in the regular editor, while running the command from the command palette gives the intended result.
Therefore, I propose to extend the when clauses of  stageSelectedRanges and revertSelectedRanges.  unstageSelectedRanges remains unchanged, since it seems to have no effect in a regular editor.
Note: I tried to be as conservative and left isInDiffEditor intact, but that's probably not needed.

I just noticed one should also be able to invoke stageSelectedRanges / revertSelectedRanges on the current line without selecting the line. Fixed in 324a6a2ab7f814050595346a4bfb3089f9677ffd.

Thank you very much for filing this pull request. I believe that the right thing to do here is for the keybindings to match the when clause of the commands from the command palette hence I have created https://github.com/microsoft/vscode/pull/235713/files. Closing this pull request in favour of that.


Edit form field names are not localized

Start local server with script/server
Click on a tweak from the index list
Click the edit button

Expected: Form field names to be localized
Actual: Form field names are not localized

As stated in the README, this project is no longer maintained and has been retired. Because of this, I am archiving this repository and closing all issues and pull requests. Thanks very much for your support and contributions!


[WEB Improvement] : The github stars section is disappearing in mobile view

Quick Description 🛠
https://github.com/user-attachments/assets/5272f23e-c00c-4917-86b1-6ab81091aacf
I am eager to start working on it , could you please assign it to me?
Select the open-source program you're contributing to
Other
Adherence to Code of Conduct

[X] I adhere to the CONTRIBUTING GUIDELINES of this project.

Hey @ShivanshPlays👋! Thanks for raising this issue and demonstrating your interest in contributing to our project!🚀
We value your engagement and eagerly anticipate your contributions. Should you wish to get involved, please use the /assignme command to self-assign the issue.
This issue provides an excellent opportunity for us to enhance our project, and we're excited to have you join us! Please take a moment to review our CONTRIBUTING GUIDELINES before getting started.
If you have any questions or need assistance, feel free to reach out to us on LinkedIn.❤

can you assign this to me I will work on it

Hey @uzefaqureshi06 I think @ShivanshPlays working on this issue, can please create a new issue and work on it.


DS-4311 Workflow Actions refresh entire MyDSpace page instead of just WorkflowItem

This is a duplicate of DS-4311
Clicking "Claim Task" reloads the entire MyDSpace page. This loses your context, so you need to locate the item you just claimed (and it may suddenly jump to the second page of results, like it did when I tested). This can be fixed by ensuring the MyDSpace page does NOT reload all results, but just reloads the claimed Item (as needed).
In DSpace 6 XMLUI, you can claim a task and immediately see the actions for that item hereafter without having to search for the item in your list again.
After editing the item metadata, the user should also immediately be able to perform the applicable actions (e.g. approve it after editing the metadata) without having to find the item again.
Related to DS-4489 (now #771) and DS-4490 (now #772)
There is no estimate for this task in the release plan.

As discussed in today's meeting, this ticket is not only about the "Claim Task" button (though that button's behavior is the worst).
The page refresh also occurs when clicking "Accept" or "Reject" or "Return to Pool".  So, a user looking to click "Accept" on several claimed tasks in a row would need to:  (a) click Accept (page reloads), (b) search/page for the next item, (c) click Accept again (page reloads), (d) search/page for the next item.    Ideal behavior would allow the user to click "Accept", staying where they are & then click "Accept" on the next item, etc.

@tdonohue
I've take a look on this issue and  to avoid to reload the entire page we need changes on both angular end rest side.
Indeed the main issue is that to reload the single element of the search we need to know which is the new object type created after the execution of a workflow action.
For example when making a request to claim a task the endpoint should return the new claimedtask created while now return only a 204. The same should be when returning a task to the pool.
The problem would still be there without changes on rest side even if we'd use the approach suggested for #772 .
So we'd need:

(REST side) change the way we use now to claim task in such a way that endpoint return the new claimedtask created
(REST side) add new search method by item for pooltasks endpoint and claimedtasks endpoint to allow to retrieve the new task created after performing a "Accept", "Reject" or "Return to Pool" action
(Angular) make changes to reload the single element instead the entire page

in order to try to preview an Item during the Workflow approval process, we could add a View detail button that allow to switch to the existing detail mode, mantaining the focus on that specific Workflow task

Estimantion is about 16hours for REST and about 24hours for angular

In today's meeting, we discussed the proposal above and agreed to the approach.  A few notes from that discussion:

The main issue is the REST API not returning the updated object when a claim/unclaim occurs.  The 204 No Content returned was a mistake & we need to correct it.
The new REST API search methods (to be used after clicking approve/reject) are necessary because the Angular UI doesn't know what the workflow configuration is.  Based on backend configuration, clicking "Approve" or "Reject" may result in different behaviors -- e.g. Item might be archived / sent back to submitter, or it might remain in workflow if multiple approvals are required to place into archive.
The new behavior in the UI will be as follows:

After clicking Approve/Reject buttons, the frontend will query the backend for the next state.
This might result in new buttons appearing (e.g. A reviewer might approve and put the Item into the next workflow step where they can now "Claim" it again).
This could also result in no further actions being available to the reviewer. In this scenario, the buttons may disappear altogether & a simple message like "You approved this item" or "You rejected this item" would appear in their place.
It's important to realize that the Item will NOT disappear from the current list of results.  This would be too complex to implement, and this behavior was modeled based on sites like GitHub (e.g. when you delete branches from GitHub, they just get grayed out but are not removed from your branch list until you refresh the page).
This means that the item won't disappear from a users list until the results list is refreshed (e.g. page reloaded, click on a new facet or new page).  It was noted in our meeting that this behavior may be confusing to users if they click on a new page and find the results list changed (but this also can occur if new items are submitted prior to their clicking on a new page, as new items will suddenly appear in their results list).  We feel this is a good enough approach.

Summary: The approach described above is accepted. This has been split into two tickets:

This #721 ticket itself, which is now scoped to Angular work only.
The necessary REST API backend work to support this implementation: (COMING SOON)


[QUERY] How does the MaxConcurrentCallsPerSession setting in ServiceBusSessionProcessor actually works?

Library name and version
Azure.Messaging.ServiceBus 7.13.1
Query/Question
So currently we have a web app application that is creating a non-session subscription to a topic setting the MaxConcurrentCalls setting to 1. AFAIK that means that if we have 4 instances then we will have at most 4 message locks being acquired for the subscription (one for each instance). So far so good. Now we have a business requirement that will imply that we need to process the messages in order depending on some value. Fortunately we found that ASB has the perfect feature for that and that is sessions:
https://learn.microsoft.com/en-us/azure/service-bus-messaging/message-sessions
Now reading the docs it seems that it is perfect for our use case: if we have the same 4 instances then it means that each one of them will acquire a session lock. That will guarantee that messages with the same session ID will be processed in order. "Long live sessions" we thought. We wanted to start writing the code to setup our ServiceBusSessionProcessor but that's when we started to have some doubts:
https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/servicebus/Azure.Messaging.ServiceBus/samples/Sample05_SessionProcessor.md
More specifically I saw the MaxConcurrentCallsPerSession setting and that's when everything I read in the docs stopped making sense in my head. I thought you could only process one message per session given that the processor was gonna acquire a session lock but it seems that's not true. I guess that setting MaxConcurrentCallsPerSession greater than 1 means that the processor will acquire a session lock, read multiple messages from that session and then it will start processing concurrently (and that would mean that messages from the same session could be processed in an out-of-order way)? If that's the case I believe the message sessions documentation should be updated to mention that is something that can be done if you want to because all that page is talking about ordered handling. But more importantly let's say that we still have the same 4 web app instances, would setting MaxConcurrentCallsPerSession equal to 1 guarantee to us that we will never see multiple messages from the same session being processed at the same time if we use the ServiceBusSessionProcessor?
Environment

Hosting platform: .NET 7
Visual Studio 2022

I thought you could only process one message per session given that the processor was gonna acquire a session lock but it seems that's not true.

This is not true.  Only one consumer can hold the message lock which gives that consumer exclusive access to the session.  No other consumer can read from the session while the lock is held.   The consumer holding the lock can read as many messages concurrently from the session as it would like.    That is controlled in the processor by MaxConcurrentCallsPerSession.

would setting MaxConcurrentCallsPerSession equal to 1 guarantee to us that we will never see multiple messages from the same session being processed at the same time if we use the ServiceBusSessionProcessor

Yes, this is correct.   If you want only a single message at a time, you want to set the concurrent calls to 1.


Update tokenizers version

Is it possible to update the tokenizers' version? We're using the latest transformers python package and it requires tokenizers' version to be >=0.19,<0.20

Hey, bumped it to ^0.19 in 5.3.3, thanks for reporting!

Hi, This issue got resolved with 5.3.3 but again pops up with the latest 5.5.6


brief documentation in Arabic about the translation process of the pr…

Brief documentation in Arabic about the translation process of the project in Crowdin

Hello @BatoolMM, I completed my PR. Could you please give me your feedback?


Policy-based governance, risk, and compliance paper

Fixes https://github.com/kubernetes/sig-security/issues/93

Preview at: https://github.com/kubernetes/sig-security/blob/21c33081ff5118ab5afefb65c15af29a34c10356/sig-security-docs/papers/policy_grc/kubernetes-grc.md.

LGTM

LGTM 🚀

/lgtm


Make sure we cannot create recursive node trees

Right now it is possible to create a node with a child that points to itself. This causes an endless loop.
We have to make sure we cannot add nodes that result in such a loop.

Would it just be enough to make sure that the children ids are never equal to the parent id?

But then i guess it doesn't work if it goes more than one level deep

I would implement a arena using a Vec like this:
pub struct Arena<T> {
    nodes: Vec<Node<T>>
}

pub struct Node<T> {
    pub id: usize,
    pub parent: Option<usize>,
    pub children: Vec<usize>,
    pub data: T
}

impl<T> Arena<T> {
    pub fn new() -> Self {
        Self { nodes: Vec::new() }
    }

    pub fn get(&self, id: usize) -> Option<&Node<T>> {
        self.nodes.get(id)
    }

    pub fn get_mut(&mut self, id: usize) -> Option<&mut Node<T>> {
        self.nodes.get_mut(id)
    }

    pub fn add(&mut self, data: T) -> usize {
        let id = self.nodes.len();

        self.nodes.push(Node { id, parent: None, children: Vec::new(), data });

        id
    }

    pub fn attach(&mut self, parent_id: usize, child_id: usize) {
        if let Some(parent) = self.nodes.get_mut(parent_id) {
            parent.children.push(child_id);
        }

        if let Some(child) = self.nodes.get_mut(child_id) {
            child.parent = Some(parent_id);
        }
    }
}

Then we could create a DomNode struct:
pub struct DomNode {
    /// name of the node, or empty when it's not a tag
    pub name: String,
    /// namespace of the node
    pub namespace: Option<String>,
    /// actual data of the node
    pub data: NodeData,
}

/// Different type of node data
#[derive(Debug, PartialEq, Clone)]
pub enum NodeData {
    Document,
    Text {
        value: String,
    },
    Comment {
        value: String,
    },
    Element {
        name: String,
        attributes: HashMap<String, String>,
    },
}

This can then be used like this:
let mut arena = Arena::<DomNode>::new();

let node_id = arena.add(DomNode {
    name: "".into(),
    namespace: None,
    data: NodeData::Document
});

This has the advantage that the arena can be used for different node types (could be reused for the css parser)
One drawback would be that we cannot remove nodes because the node ids would then change (if that is necessary then an inplementation with a HashMap would make sense again.

There is an arena like system for the current nodes, so maybe we can expand this a bit to make it more flexible. The nodes are added to a document, which is merely an arena of nodes, plus the root node of the tree.  We could check during attachment of nodes if any cyclic references are present or not.

Sounds like a good idea to check that. I think in my implementation cyclic are possible too without that check.
I tried replacing the current arena in my fork and got all tests to pass but I'm not quite happy with the implementation. Maybe you want to take a look (don't want to make a pull request for this)
https://github.com/lucalewin/gosub-browser/blob/arena/src/html5_parser/arena.rs

If this was merged, can this issue be closed now?


Expand is_logger_candidate to check Expr::Name expressions

Summary
Expands the is_logger_candidate func to also check for Expr::Name values. As it would previously not consider:
from logging import error

error("foo")

a candidate but would consider
import logging

logging.error("foo")

a candidate leading to inconsistent behaviour.
This also fixes a bug in the LOG007 rule.
Test Plan
LOG007 test fixed and other tests untouched. If general idea is approved I can add additional test cases to rules which use is_logger_candidate()
Issue Link
See also discussion in: https://github.com/astral-sh/ruff/issues/7502

So I think there's a little more to do here, but it's not clear from this PR because there's actually a bug in LOG007. Lemme push a fix, then I'll come back and explain.

Take a look at https://github.com/astral-sh/ruff/pull/7524. The issue is that we assume all calls are done on attributes, so that we can resolve the attribute to, e.g., .exception or .info or whatever. The same pattern is used in logging_call, in crates/ruff/src/rules/flake8_logging_format/rules/logging_call.rs.
We may want to change logging_call (and the LOG007 method) to match on either name or attribute, and use separate paths to determine whether it's a logger and, if so, what the log level is. Or we could try changing this method to return the logging attribute too.

Interesting, thanks for the taking the time to explain and clarifying my previous misinterpretation of is_logger_candidate in LOG007. I'll have a look tomorrow if I can implement what you're suggesting. Will mark as draft until then.

@qdegraaf - Nice! I think we need to extend this to a few more call sites. Are you able to look into the other usages of is_logger_candidate and apply similar logic? E.g., in blind_except, in the callers of LoggerCandidateVisitor, and so on. If not, we can merge and fix those up later, but I believe they do also need refinement.

Happy to add those to the PR! Will have a look tomorrow

Thank you!


Refresh expiration of cookie

TEST CASE:

Login to https://maia.x.x.x/[domain_name]/graph?domain_id=y with basic authentication
Wait at least 8 hours
repeat step 1

EXPECTED BEHAVIOUR:
User is logged in.
OBSERVED BEHAVIOUR:
Login fails.
Error log message: Request with wrong credentials from XYZ: Authentication failed
Maia is using existing cookie for authentication even when the cookie has already expired.
Workaround is to delete the cookie manually. But Maia should re-authenticate and refresh the cookie.

Okay, I'm trying to replicate, it looks like it's handling it properly but perhaps after 8 hours it will make sense.

Cookie details:

Tested with Chrome Version 96.0.4664.93. I would expect, the browser deletes expired cookies, but apparently it doesn't.
Mitigation: Either browser setting Clear cookies and site data when you close all windows or manually delete the Maia cookie.

Replicated and confirmed.
2021/12/10 12:20:13 ERROR: Authorization header missing (no username/password or token) 2021/12/10 12:45:47 ERROR: Authorization header missing (no username/password or token) 2021/12/10 19:54:42 INFO: Request with wrong credentials from : Resource not found

I'm not sure what we can do otherwise, your mitigation is correct. Should we close the ticket?

Closing ticket due to acceptable mitigation based around browser.


Error Installing on php 8+

I am getting the following error when I am trying to install with php 8.0.14
$ composer require slim/console

  [InvalidArgumentException]
  Package slim/console has requirements incompatible with your PHP version, PHP extensions and Composer version:
    - slim/console 0.1 requires php ^7.2 which does not match your installed version 8.0.14.

require [--dev] [--dry-run] [--prefer-source] [--prefer-dist] [--prefer-install PREFER-INSTALL] [--fixed] [--no-suggest] [--no-progress] [--no-update] [--no-install] [--update-no-dev] [-w|--update-with-dependencies] [-W|--update-with-all-dependencies] [--with-dependencies] [--with-all-dependencies] [--ignore-platform-req IGNORE-PLATFORM-REQ] [--ignore-platform-reqs] [--prefer-stable] [--prefer-lowest] [--sort-packages] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--apcu-autoloader-prefix APCU-AUTOLOADER-PREFIX] [--] [<packages>]...

I have same issue, any updates?


docs: fix path for state_of_the_union sample file

I wonder whether we should provide some standard fixtures in a separate package langchain_sample_data or something like that


Add most missing core docs

This is the biggest step towards getting the documentation website
"core-complete".  By this I mean that we might be missing tutorials or
how-to guides that I'd like to write, someday, but we shouldn't have
any stubs or outright missing pages for the core parts of the library.
After this PR, the main "core" doc still remaining will be the
QuantityPoint reference page.
I started by adapting a treasure trove of Aurora-internal Au docs, which
I didn't know what to do with back when we open-sourced Au.  These
include the "concepts" discussion pages arithmetic.md,
common_unit.md, and dimensionless.md.  I rounded this section out
with new discussion docs on quantity_point and zero.
I also added a new "Au idioms" discussion section, which gave me a home
to migrate the explanation of "unit expression APIs".  This is very
useful and many pages link to it.
The reference docs have been greatly fleshed out.  I finally finished
the stubs for prefix, quantity, and unit.  I also added new
reference docs for corresponding_quantity, math, and zero.
Some of the deeply-nested reference pages --- most especially math ---
became hard to read: the
 sections blended together.  I therefore
added a script which would add a
 at the end of any

section.  I found this improves readability significantly where it's
used.  We need to explicitly opt into using this on a per-page basis,
which is also fine with me.  (The code is executed directly when the
script loads, rather than being encapsulated in a function, because I
couldn't find a simple way to reliably get the script to finish loading
before I called the function.  This bothers me only very slightly.)
Some of the "main section pages" --- namely, how-to, and reference ---
looked a little sparse.  I decided to add descriptions of the most
significant pages in that section (or, for some, all of the pages).
Finally, there are a couple of code updates.

Reworded the phrasing in some comments.
Added a couple test cases to reflect some of the new doc content.
Finally explicitly deleted the Zero constructor for QuantityPoint

Note to reviewers: I tested this by running au-docs-serve, and clicking on every. Single. Link.  I checked that the ones that linked to a sub-section indeed went to the desired sub-section.


Bug in the grouped nav

Looks like there is a bug in the grouped nav, because on mobile, the title doesn't reduce its left spacing like the list does.

cc: @rachael-phillips @mcoker

:tada: This issue has been resolved in version 2.59.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Hide Editor Groups Panel

How to hide the editor groups bar and is there an API for it..?

the answer is the same

Not working for me..!
I commented on other changes and tried them. Any ideas?

Figured 🙌
it's just the old configuration I had 👇
"workbench.editor.showTabs": true, // Need to enable this in order make it hide again

Thanks for the help and patience mate 😅


Installing package on version 1.1.4 is not exposing css and redux files at the root folder. Version 1.1.3 works fine.

Current behavior
Installing the package at version 1.1.4 is not exposing the redux and css files on the root folder. Consequently, importing react-block-ui/redux', react-block-ui/reduxMiddleware and react-block-ui/style.css fails.
Installing the package at version 1.1.3 exposes the files at the root folder as expected.
Expected behavior
Files should be exposed so I can import them as shown in the docs.
Steps to recreate the problem

Create a new node project (npm init -y)
Install package: npm install react-block-ui
Check package files in the node_modules folder

Environment

Windows 10 Professional
NodeJS 6.13.1 (legacy system)
npm 5.6.0

The files are missing from the published package.
<EMAIL_ADDRESS><EMAIL_ADDRESS>

I solved by putting the lib/ folder.
Example:
import ReduxBlockUi from 'react-block-ui/lib/redux';

From what I am seeing, it looks like those files are not being copied over in the build/release script. Going to open a PR to get those added over.

fixed in v1.3.1
/redux works again. or /lib/redux.


Refactor media services

Fixes

Fixes #866 by @obulat
Description

This PR joins three separate modules for media-services into one generic MediaService that can be created with a mediaType parameter. All of the methods for both audio and image are the same. This change will allow us to simplify media fetching, and make the store conversion to Pinia and addition of other media types easier.
Testing Instructions

Run the app as usual, and check that you can search for all media types.
Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the default branch of the repository (main) or a parent feature branch.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

This is great Olga! I haven't tested the code locally yet but I did take it for a spin to do some fun TypeScript hoop-jumping to make the MediaStore a generic class based on the mediaType in the constructor. Take it or leave it, up to you :slightly_smiling_face:

This is great Olga! I haven't tested the code locally yet but I did take it for a spin to do some fun TypeScript hoop-jumping to make the MediaStore a generic class based on the mediaType in the constructor. Take it or leave it, up to you 🙂

Thank you, Sara, your PR is amazing! I've left my notes there, and added some changes from it here.

@WordPress/openverse-frontend can we get a second review on this? :slightly_smiling_face:

How will we handle if a media type has a one-off endpoint, like the /waveform endpoint for audio or future endpoints that, say, 3D models might need?

Subclass the MediaService:
class Model3DService extends MediaService<'3d models'> {
  constructor() {
    super('3d models')
  }

  getCustomData() {
    // impl
  }
}


How do I turn off http.ListenAndServer?

I don't see any Close method in ProxyHttpServer, nor do I find relevant information in the Document. What should I do?

It's an HTTP handler, why should it be different than any other handler?

I got you


Update

One-to-many caching
README is updated
dependencies are updated

Coverage decreased (-1.4%) to 92.511% when pulling 203fddd4288c62ac77ba2945bf9a2ef3ddc45fd5 on TrigenSoftware:update into d9df16c3d20274845051a29d2e24143c95f2d9c8 on jgable:master.

Coverage decreased (-1.4%) to 92.511% when pulling 63f47f50753972dbdc48dafd2bff87157d56a437 on TrigenSoftware:update into d9df16c3d20274845051a29d2e24143c95f2d9c8 on jgable:master.


Work around cython parameter passing bug.

In the words of Mae West, "goodness had nothing to do with it".
In this case, she was wrong though, __goodness tickled a cython code generation bug if __goodness was compiled as a cdef function.
Made __goodness work as a cdef function by removing its default parameter values.
Boiling this down to a human comprehensible example suitable for a cython bug report is a work in progress.
It appears that cython has a bug in passing parameters with defaults to some recursive functions.  __goodness is one of them.  In this case if any of the parameters had defaults parts was passed a 0 (False).  Removing the defaults fixes this.
Also added the showgood submodule to the list of submodules to doctest.

Nice.
Does this make showgood faster at all?


CommentsPart setting for reverse display order

CommentsPartSettings should have an additional option for displaying comments in Ascending (currently wired-in) or Descending order using radio buttons.
Question is: with threaded comments enabled, descending order should be applied to the first level only, or all of them?

1st level only
Otherwise, it's hard to follow the flow of the thread.
Or make it an option?
Desc [y] [n]
1st Level only [y] [n]

Don't we want to implement system Projector queries as discussed a long time ago, make CommentsPart use such a query in the background, and let you do any fancy listing by modifying this query?


fix scheduler to take input from setting page

Description
Please provide a summary of the pull request and the issue it fixes. Please add necessary details, context, dependencies, explanation of when review is needed (see next section), etc.
Fixes #(add issue number here and remove parentheses)
Review Time Estimate
Please give your idea of how soon this pull request needs to be reviewed by selecting one of the options below. This can be based on the criticality of the issue at hand and/or other relevant factors.

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

Type of changes
Please select a relevant option:

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

Checklist:
Please select all applicable options:

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

Hi, @bingzhang, Thanks. I have feedback on a few items:

Please update the pull request description to fill in the checklist entries. This information will be helpful for all reviewers (current or new). Thanks.
Please update the settings page text about download scheduling to include details about the timezone. Here is a suggestion: Events from these calendars will be crawled, parsed, and published daily at the scheduled time displayed below. The default scheduled time is 11:00 PM (Central Time). You can set a different time below.
When I tried changing the time using the develop branch, it's working locally. With the change in this PR, a PytzUsageWarning warning about the timezone goes away. So, it's definitely an improvement, but to test if this would fix the actual problem, this will need to be deployed to the DEV instance.
After I set the time using the Settings page and restarting Events Manager (consider the example of container restarting due to some reason), Events Manager picks up the value in the environment and not the user input that's in the database. I think the core issue is that the Events Manager needs to prefer the user setting over the environment variable setting. Please fix this. Thanks.

Hi, @bingzhang, Thanks. I have feedback on a few items:

Please update the pull request description to fill in the checklist entries. This information will be helpful for all reviewers (current or new). Thanks.
Please update the settings page text about download scheduling to include details about the timezone. Here is a suggestion: Events from these calendars will be crawled, parsed, and published daily at the scheduled time displayed below. The default scheduled time is 11:00 PM (Central Time). You can set a different time below.
When I tried changing the time using the develop branch, it's working locally. With the change in this PR, a PytzUsageWarning warning about the timezone goes away. So, it's definitely an improvement, but to test if this would fix the actual problem, this will need to be deployed to the DEV instance.
After I set the time using the Settings page and restarting Events Manager (consider the example of container restarting due to some reason), Events Manager picks up the value in the environment and not the user input that's in the database. I think the core issue is that the Events Manager needs to prefer the user setting over the environment variable setting. Please fix this. Thanks.

@sandeep-ps I updated the pr. I created a new issue related to your comments. https://github.com/rokwire/events-manager/issues/1035


why windows7 don't support D3D11VideoDecoder

why windows7 don't support D3D11VideoDecoder?

See: https://github.com/StaZhu/enable-chromium-hevc-hardware-decoding#windows-1

This is hardcode limit in chromium, and i think win7 doesn’t support d3d11 as well. Since Chrome 109, Chrome only support Windows >= 10, d3d9 hw decoding code will be removed in the near future as well.

ok, thank you～


Swift: Cannot set expiry date for a container

echo "data" > object1.txt
swift upload container1 object1.txt
swift post container1 -r .r:*,.rlinstings

Date now:
date

Sat Jan 21 14:07:45 UTC 2017

date in 3 min

date -d "Sat Jan 21 14:10:00 UTC 2017" +%s
1485007800

Container inf.
swift stat -v container1

         URL: http://<IP_ADDRESS>:8080/v1/AUTH_94d6b69b25f74041a5c413513612c8bd/container1
  Auth Token: 540238bc72284c74a051df53089583b6
     Account: AUTH_94d6b69b25f74041a5c413513612c8bd
   Container: container1
     Objects: 1
       Bytes: 5
    Read ACL: .r:*,.rlistings
   Write ACL:
     Sync To:
    Sync Key:

Accept-Ranges: bytes
X-Trans-Id: tx04287daafd6045d8a7ba7-0058836b67
X-Storage-Policy: Policy-0
Last-Modified: Sat, 21 Jan 2017 13:54:34 GMT
X-Timestamp:<PHONE_NUMBER>.89799
Content-Type: text/plain; charset=utf-8

Set expiry date:
curl -X PUT -H "X-Auth-Token:540238bc72284c74a051df53089583b6" -H "X-Delete-At:1485007800" http://<IP_ADDRESS>:8080/v1/AUTH_94d6b69b25f74041a5c413513612c8bd/container1

Accepted

The request is accepted for processing.

The time already passed and the container is still accessible publically:

Tried using swift command :
#now
date

Sat Jan 21 14:13:49 UTC 2017

#in 5 min
date -d "Sat Jan 21 14:19:00 UTC 2017" +%s

1485008340

swift post container1 object1.txt -H X-Delete-At:1485008340
But the container is still accessible

With curl REST API query, I should have used POST request not PUT
curl -X PUT
not
curl -X POST


Pussy

What version are you using?

What did you do?

What did you expect to see?
What did you see instead?

What version are you using?
What did you do?
What did you expect to see?
What did you see instead?

What version are you using?
What did you do?
What did you expect to see?
What did you see instead?


Dreamview show "page not found"

Build susses
1.bash scripts/bootstrap.sh
Module monitor is already running - skipping.
Launched module dreamview.
Dreamview is running at http://localhost:8888

2gdb --args /apollo/bazel-bin/modules/dreamview/dreamview --flagfile=/apollo/modules/dreamview/conf/dreamview.conf
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /apollo/bazel-bin/modules/dreamview/dreamview...done.
(gdb) r
Starting program: /home/chr/.cache/bazel/_bazel_chr/540135163923dd7d5820f3ee4b306b32/execroot/apollo/bazel-out/local-dbg/bin/modules/dreamview/dreamview --flagfile=/apollo/modules/dreamview/conf/dreamview.conf
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffc8163700 (LWP 7976)]
/apollo/apollo-platform/ros/ros_comm/roscpp/src/libros/init.cpp:660 configParse() [ WARN] [1544337317.676978932]: transport file: /home/tmp/ros/etc/ros/transport_mode.yaml is not map
/apollo/apollo-platform/ros/ros_comm/roscpp/src/libros/init.cpp:349 start() [ WARN] [1544337317.677074698]: Parse transport_mode file failed
[New Thread 0x7fffc7757700 (LWP 7978)]
[New Thread 0x7fffc6f56700 (LWP 7979)]
[New Thread 0x7fffc6755700 (LWP 7980)]
[New Thread 0x7fffc5f54700 (LWP 7981)]
[New Thread 0x7fffc5753700 (LWP 7982)]
[New Thread 0x7fffc4f52700 (LWP 7983)]
[New Thread 0x7fffb7fff700 (LWP 7984)]
[New Thread 0x7fffb77fe700 (LWP 7985)]
[New Thread 0x7fffb6ffd700 (LWP 7986)]
[New Thread 0x7fffb67fc700 (LWP 7987)]
[New Thread 0x7fffb5ffb700 (LWP 7989)]
terminate called after throwing an instance of 'CivetException'
  what():  null context when constructing CivetServer. Possible problem binding to port.

Program received signal SIGABRT, Aborted.
0x00007fffeab34c37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
56      ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.

3bt
#0  0x00007fffeab34c37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1  0x00007fffeab38028 in __GI_abort () at abort.c:89
#2  0x00007fffeb143e63 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#3  0x00007fffeb148fa6 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#4  0x00007fffeb148fe1 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#5  0x00007fffeb149213 in __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#6  0x0000000000f14f77 in CivetServer::CivetServer (this=0x1ea0f20, options=std::vector of length -17592182028738, capacity -44 = {...}, _callbacks=0x0, UserContextIn=0x0) at external/civetweb/src/CivetServer.cpp:319
#7  0x000000000047a9a3 in apollo::dreamview::Dreamview::Init (this=0x7fffffffde90) at modules/dreamview/backend/dreamview.cc:111
#8  0x0000000000486d33 in apollo::common::ApolloApp::Spin (this=0x7fffffffde90) at modules/common/apollo_app.cc:57
#9  0x00000000004762de in main (argc=1, argv=0x7fffffffe000) at modules/dreamview/backend/main.cc:19

What should I do ?

If you are running in docker, this is strange. Since all docker share the same docker image.
When you execute the dev_start.sh, do you use git to checkout the r3.0.0 version?
the master branch may contains some incompatible commits.

@hahanigehaha233 have you been able to resolve your issue?

Closing this issue since there has been no communication in a while. Feel free to reopen if you have additional questions. Thanks!


How to authenticate routes using Passport?

Hi
With React Router, the routing is handled on the client side. May I know how do we authenticate the route the user is trying to access and redirect to a login page if he has not been authenticated?

There's an example here:
https://github.com/rackt/react-router/blob/master/docs/api/components/RouteHandler.md#willtransitionfromtransition-component-callback
Also,
https://github.com/rackt/react-router/tree/master/examples/auth-flow

At the moment I try to find a solution for the same problem. But the auth-flow example seems to scale badly.
In my app some pages should be visible to everyone, other pages should be visible only for logged in users or administrators. My current idea is to replace the routes every time the login status changes. I have not tried that yet, because @gaearon's #658 has not landed on npm. Also with #712 it should be possible to make the routes conditional.
I am new to the router, so probably I have missed something.

Thanks for the links and discussion. It's been very informative.
For something like https://github.com/rackt/react-router/blob/master/examples/auth-flow/app.js#L8 it's assuming a global auth variable. How could I get a passport instance exposed in this way?

https://github.com/rackt/react-router/blob/master/examples/auth-flow/app.js#L129-164
Not only assumed, but implemented. From what I can tell the global auth object is meant to simulate an authentication API. In auth-flow's case it's using localstorage. However, even though Passport.js is running server-side you can create a similar solution with a few tweaks. On your server, create a few endpoints for authentication, such as /login, /logout, and even /verify if you wish. Client-side, for login, re-code auth.login to make an AJAX call to the /login endpoint and share the result with your React app.

@kilometers amazingly informative. Thank you.

Is there a React router 4 example out there? I came across this one https://github.com/bodiddlie/headache-diary, which is helpful and uses concepts from the docs, but it'd be great to see an example project of how to use passport for oauth server side and rr client side.  I have an approach that sets a cookie server side and I can read that from React but trying to figure out how to turn that into a state that I can share in my components is my current dilemma. Thanks!

I would also be interested in seeing such approach using react-router v4 featuring for basic auth-flow example

@aroach hey! random v4 user here. here you go: https://reacttraining.com/react-router/web/example/auth-workflow and https://stackoverflow.com/questions/43164554/how-to-implement-authenticated-routes-in-react-router-4

@gaearon both links are dead :/

@gaearon These links are dead, can you please update it?


Automate reports two chef-client runs when reboot resource is used

Describe the bug
Chef Automate will simultaneously report a passed & failed chef-client run when the reboot resource is used. I've attached two screen shots showing the issue. If you look at the first screen shot you'll see both a passed & failed run reporting at 22:57:16
To Reproduce
Steps to reproduce the behavior:

enable chef-client reporting to Automate
use the reboot resource in a chef-client run

Expected behavior
I would expect if the reboot resource & the rest of the chef-client run was succesful I would expect a single succesful run in Automate.
If the reboot resource or the chef-client run failed I'd expect a failed chef-client run in Automate.
Screenshots
Screenshot with two reports:

Drill down showing reboot resource used:

Versions (please complete the following information):
chef-client 13.8.5
Current Automate for August 2019
Additional context
Exact chef-client version from core/chef-dk
https://bldr.habitat.sh/#/pkgs/core/chef-dk

@jonong1972 not sure if you have any ux opinions on this...?

To be clear in my example above the chef-client run was succesful. My guess is since the system is rebooting it interrupts the initial chef-client run & it continues after the reboot. It reports the same time so I think it's still reporting in a single run but that interrupt makes it both a failure & success.

let's pull in lamont and figure out why this is happening on the chef client side of things. doing special magic during ingestion seems risky


Prevent reentrant synchronous callback execution.

I have split this off of #836 to focus on the re-entrancy problem. Even without trying to optimize event loop access of the stream message, we should be handling it correctly for the non-executor stream case.
https://github.com/reactive-streams/reactive-streams-jvm#2-subscriber-code - 2.7
The test fails without the logic change and passes after it. Unfortunately, I'm trying to wrap my head around failures with the testNg. Let me know if you have any ideas what could be up.
PublisherBasedStreamMessageVerification.required_spec317_mustNotSignalOnErrorWhenPendingAboveLongMaxValue: FAILURE

Gradle suite > Gradle test > com.linecorp.armeria.common.stream.PublisherBasedStreamMessageVerification.required_spec317_mustNotSignalOnErrorWhenPendingAboveLongMaxValue FAILED
    java.lang.OutOfMemoryError: GC overhead limit exceeded
DefaultStreamMessageVerification.required_spec317_mustNotSignalOnErrorWhenPendingAboveLongMaxValue: FAILURE

Gradle suite > Gradle test > com.linecorp.armeria.common.stream.DefaultStreamMessageVerification.required_spec317_mustNotSignalOnErrorWhenPendingAboveLongMaxValue FAILED
    java.lang.OutOfMemoryError: GC overhead limit exceeded
DeferredStreamMessageVerification.required_abortMustNotifySubscriber: FAILURE

Gradle suite > Gradle test > com.linecorp.armeria.common.stream.DeferredStreamMessageVerification.required_abortMustNotifySubscriber FAILED
    java.lang.AssertionError: Expected onError(com.linecorp.armeria.common.stream.AbortedStreamException) within 100 ms

        Caused by:
        java.lang.AssertionError: Expected onError(com.linecorp.armeria.common.stream.AbortedStreamException) within 100 ms
DeferredStreamMessageVerification.required_spec317_mustNotSignalOnErrorWhenPendingAboveLongMaxValue: FAILURE

Gradle suite > Gradle test > com.linecorp.armeria.common.stream.DeferredStreamMessageVerification.required_spec317_mustNotSignalOnErrorWhenPendingAboveLongMaxValue FAILED
    java.lang.OutOfMemoryError: GC overhead limit exceeded

172 tests completed, 4 failed, 49 skipped

Made the following change and problem seems gone:
diff --git a/core/src/main/java/com/linecorp/armeria/common/stream/DefaultStreamMessage.java b/core/src/main/java/com/linecorp/armeria/common/stream/DefaultStreamMessage.java
index ffa09cee..82da570c 100644
--- a/core/src/main/java/com/linecorp/armeria/common/stream/DefaultStreamMessage.java
+++ b/core/src/main/java/com/linecorp/armeria/common/stream/DefaultStreamMessage.java
@@ -132,7 +132,7 @@ public class DefaultStreamMessage<T> implements StreamMessage<T>, StreamWriter<T

     private volatile boolean wroteAny;

-    private boolean notifyingSynchronously;
+    private boolean inOnNext;

     /**
      * Creates a new instance with a new {@link ConcurrentLinkedQueue}.
@@ -299,20 +299,29 @@ public class DefaultStreamMessage<T> implements StreamMessage<T>, StreamWriter<T
         if (executor != null) {
             executor.execute(() -> notifySubscriber(subscription, queue));
         } else {
-            if (notifyingSynchronously) {
-                // We don't notify again if we're already notifying, as it may cause incorrect order of handling
-                // objects in the Subscriber - the current notifier will loop through queue correctly and we
-                // don't do anything here. Because subscriber methods must be on the same thread, or
-                // synchronized, we do not have to worry about synchronizing this field access.
-                return;
-            }
-            notifyingSynchronously = true;
             notifySubscriber(subscription, queue);
-            notifyingSynchronously = false;
         }
     }

     private void notifySubscriber(SubscriptionImpl subscription, Queue<Object> queue) {
+        if (inOnNext) {
+            // Do not let Subscriber.onNext() reenter, because it can lead to weird-looking event ordering
+            // issue for a Subscriber implemented like the following:
+            //
+            //   public void onNext(Object e) {
+            //       subscription.request(1);
+            //       ... Handle 'e' ...
+            //   }
+            //
+            // Note that we do not call this method again, because we are already in the notification loop
+            // and it will consume the element we've just added in pushObject() from the queue as expected.
+            //
+            // We do not need to worry about synchronizing the access to the 'inOnNext' because the subscriber
+            // methods must be on the same thread, or synchronized, according to Reactive Streams spec.
+            return;
+        }
+
+
         for (;;) {
             if (state == State.CLEANUP) {
                 cleanup();
@@ -367,7 +376,9 @@ public class DefaultStreamMessage<T> implements StreamMessage<T>, StreamWriter<T
                     }
                 }

+                inOnNext = true;
                 subscriber.onNext(o);
+                inOnNext = false;
                 return true;
             }
         }

I think we don't need to protect reentrance for onComplete() and onError() because it's terminal condition, so I used the flag only for onNext().
I prevented the reentrance even when an executor is specified because we will optimize this later in #836.
The reason why the TestNG tests failed was it gave no chance to the Subscriber to consume anything, because your patch set notifyingSynchronously too soon, even before invoking Subscriber.

Oh! This might also be related to the TCK tests being implemented using onDemand - as I found, this was the reason that the implementation passed required_spec303_mustNotAllowUnboundedRecursion despite the code being wrong. Do you think we need to rethink the TCK test harness? And in that case, I think it won't matter too much which location the booleans are set.

the implementation passed required_spec303_mustNotAllowUnboundedRecursion despite the code being wrong. Do you think we need to rethink the TCK test harness?

That's a good question. I think we can't do much about DefaultStreamMessageVerification because onDemand() is just how a user is expected to use to stream a large number of streams. We could improve PublishedBasedStreamMessageVerification to source the stream from a simpler Publisher implementation which does not extend DefaultStreamMessage, and use PublisherBasedStreamMessage for DeferredStreamMessageVerification.

And in that case, I think it won't matter too much which location the booleans are set.

I'm not sure. Looking from the debugger, the flag was set even before onNext() was called first time, so I'd say it has to be set only when it is apparent that onNext() will be called.

Yeah it was set by awaitdemandfuture - to be honest I wasn't sure what its semantics are supposed to be, but I agree that just wrapping onNext is probably the right call. Will incorporate the suggestion and add comments to the test case!

@anuraaga Yes, please! Thanks again :-)

Updated - please also take a good look at AbstractStreamMessageDuplicator, I found with this change it was logging a NPE that didn't affect test results.
I think it's because while I was debugging TCK code for this, I noticed we weren't following 1.08 - If a Subscription is cancelled its Subscriber MUST eventually stop being signaled. Without checking for CLEANUP state in the loop, we ended up signaling all objects to the subscriber even if they cancelled. Note, 1.08 is not verified by the TCK.
After fixing this, it seems the duplicator would try to push a CloseEvent onto the queue after already having been cleared. Not too sure why this would happen so please check my fix makes any sense at all.

Will check the duplicator soon. Thank you~!!

@minwoox Is #843 also related with the NPE we observed here?

@trustin I could not take a look at this carefully because I had to make weaning foods -_-;. I will look into it.

@anuraaga Thank you for the fix~!! I think it's reasonable fix. 👍  But I think it's a little bit better to check if the signals is cleared before signals.addAndRemoveIfRequested(obj) is called.
I will dig into more about why CloseEvent is pushed after it is cleared. By the way, at which test case did you find this situation?

Thanks @minwoox - I tried applying the fix from #843 and removing mine and indeed the NPE still happens, so they seem to be two separate issues.
Most of the tests in RetryingHttpClientTest, for example respectRetryAfter, reproduce the NPE.

By the way @minwook I have tried to follow your suggestion by checking state == CLOSED before pushing objects in the duplicator. I believe the double-close happens when downstream is closed, for example by HttpRequestSubscriber.setDone and upstream is also closed before getting the cancellation from the duplicator. I guess this is pretty standard - WDYT?

@anuraaga yeah, they are two different issues.

I guess this is pretty standard - WDYT?

You're right. I should've prepared for that situation.
Thank you for fix that~! 💯

Thanks!


Move to Dataflow

Local testing on the hub was successful. Now testing this on Dataflow.

This is like pulling teeth. I am getting a lot of errored cache downloads and keep rerunning the job (each time adding a few files to the cache). I suspect that the server is rate limiting our requests here...

Example Dataflow Job
Typical error looks like this:

Error message from worker: Traceback (most recent call last):
  File "apache_beam/runners/common.py", line 1435, in apache_beam.runners.common.DoFnRunner.process
  File "apache_beam/runners/common.py", line 637, in apache_beam.runners.common.SimpleInvoker.invoke_process
  File "/tmp/8e73d6aa58f363e42749878f06c828302a08fbf313c6a5381289d6df08db87e73fc_iljf/lib/python3.10/site-packages/apache_beam/transforms/core.py", line 2040, in
  File "/tmp/8e73d6aa58f363e42749878f06c828302a08fbf313c6a5381289d6df08db87e73fc_iljf/lib/python3.10/site-packages/pangeo_forge_recipes/transforms.py", line 121, in
  File "/opt/apache/beam-venv/beam-venv-worker-sdk-0-0/lib/python3.10/site-packages/pangeo_forge_recipes/openers.py", line 32, in open_url
    cache.cache_file(url, secrets, **kw)
  File "/opt/apache/beam-venv/beam-venv-worker-sdk-0-0/lib/python3.10/site-packages/pangeo_forge_recipes/storage.py", line 209, in cache_file
    _copy_btw_filesystems(input_opener, target_opener)
  File "/opt/apache/beam-venv/beam-venv-worker-sdk-0-0/lib/python3.10/site-packages/pangeo_forge_recipes/storage.py", line 38, in _copy_btw_filesystems
    data = source.read(BLOCK_SIZE)
  File "/opt/apache/beam-venv/beam-venv-worker-sdk-0-0/lib/python3.10/site-packages/fsspec/implementations/http.py", line 598, in read
    return super().read(length)
  File "/opt/apache/beam-venv/beam-venv-worker-sdk-0-0/lib/python3.10/site-packages/fsspec/spec.py", line 1846, in read
    out = self.cache._fetch(self.loc, self.loc + length)
  File "/opt/apache/beam-venv/beam-venv-worker-sdk-0-0/lib/python3.10/site-packages/fsspec/caching.py", line 421, in _fetch
    self.cache = self.fetcher(start, bend)
  File "/opt/apache/beam-venv/beam-venv-worker-sdk-0-0/lib/python3.10/site-packages/fsspec/asyn.py", line 118, in wrapper
    return sync(self.loop, func, *args, **kwargs)
  File "/opt/apache/beam-venv/beam-venv-worker-sdk-0-0/lib/python3.10/site-packages/fsspec/asyn.py", line 103, in sync
    raise return_result
  File "/opt/apache/beam-venv/beam-venv-worker-sdk-0-0/lib/python3.10/site-packages/fsspec/asyn.py", line 56, in _runner
    result[0] = await coro
  File "/opt/apache/beam-venv/beam-venv-worker-sdk-0-0/lib/python3.10/site-packages/fsspec/implementations/http.py", line 653, in async_fetch_range
    r.raise_for_status()
  File "/opt/apache/beam-venv/beam-venv-worker-sdk-0-0/lib/python3.10/site-packages/aiohttp/client_reqrep.py", line 1070, in raise_for_status
    raise ClientResponseError(
aiohttp.client_exceptions.ClientResponseError: 502, message='Proxy Error', url=URL('https://data-dataref.ifremer.fr/ww3/GLOBMULTI_ERA5_GLOBCUR_01/GLOB-30M/2016/FIELD_NC/LOPS_WW3-GLOB-30M_201608.nc')
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/apache_beam/runners/worker/sdk_worker.py", line 311, in _execute
response = task()
File "/usr/local/lib/python3.10/site-packages/apache_beam/runners/worker/sdk_worker.py", line 386, in
lambda: self.create_worker().do_instruction(request), request)
File "/usr/local/lib/python3.10/site-packages/apache_beam/runners/worker/sdk_worker.py", line 650, in do_instruction
return getattr(self, request_type)(
File "/usr/local/lib/python3.10/site-packages/apache_beam/runners/worker/sdk_worker.py", line 688, in process_bundle
bundle_processor.process_bundle(instruction_id))
File "/usr/local/lib/python3.10/site-packages/apache_beam/runners/worker/bundle_processor.py", line 1113, in process_bundle
input_op_by_transform_id[element.transform_id].process_encoded(
File "/usr/local/lib/python3.10/site-packages/apache_beam/runners/worker/bundle_processor.py", line 237, in process_encoded
self.output(decoded_value)
File "apache_beam/runners/worker/operations.py", line 570, in apache_beam.runners.worker.operations.Operation.output
File "apache_beam/runners/worker/operations.py", line 572, in apache_beam.runners.worker.operations.Operation.output
File "apache_beam/runners/worker/operations.py", line 263, in apache_beam.runners.worker.operations.SingletonElementConsumerSet.receive
File "apache_beam/runners/worker/operations.py", line 266, in apache_beam.runners.worker.operations.SingletonElementConsumerSet.receive
File "apache_beam/runners/worker/operations.py", line 953, in apache_beam.runners.worker.operations.DoOperation.process
File "apache_beam/runners/worker/operations.py", line 954, in apache_beam.runners.worker.operations.DoOperation.process
File "apache_beam/runners/common.py", line 1437, in apache_beam.runners.common.DoFnRunner.process
File "apache_beam/runners/common.py", line 1526, in apache_beam.runners.common.DoFnRunner._reraise_augmented
File "apache_beam/runners/common.py", line 1435, in apache_beam.runners.common.DoFnRunner.process
File "apache_beam/runners/common.py", line 636, in apache_beam.runners.common.SimpleInvoker.invoke_process
File "apache_beam/runners/common.py", line 1621, in apache_beam.runners.common._OutputHandler.handle_process_outputs
File "apache_beam/runners/common.py", line 1734, in apache_beam.runners.common._OutputHandler._write_value_to_tag
File "apache_beam/runners/worker/operations.py", line 266, in apache_beam.runners.worker.operations.SingletonElementConsumerSet.receive
File "apache_beam/runners/worker/operations.py", line 953, in apache_beam.runners.worker.operations.DoOperation.process
File "apache_beam/runners/worker/operations.py", line 954, in apache_beam.runners.worker.operations.DoOperation.process
File "apache_beam/runners/common.py", line 1437, in apache_beam.runners.common.DoFnRunner.process
File "apache_beam/runners/common.py", line 1526, in apache_beam.runners.common.DoFnRunner._reraise_augmented
File "apache_beam/runners/common.py", line 1435, in apache_beam.runners.common.DoFnRunner.process
File "apache_beam/runners/common.py", line 636, in apache_beam.runners.common.SimpleInvoker.invoke_process
File "apache_beam/runners/common.py", line 1621, in apache_beam.runners.common._OutputHandler.handle_process_outputs
File "apache_beam/runners/common.py", line 1734, in apache_beam.runners.common._OutputHandler._write_value_to_tag
File "apache_beam/runners/worker/operations.py", line 266, in apache_beam.runners.worker.operations.SingletonElementConsumerSet.receive
File "apache_beam/runners/worker/operations.py", line 953, in apache_beam.runners.worker.operations.DoOperation.process
File "apache_beam/runners/worker/operations.py", line 954, in apache_beam.runners.worker.operations.DoOperation.process
File "apache_beam/runners/common.py", line 1437, in apache_beam.runners.common.DoFnRunner.process
File "apache_beam/runners/common.py", line 1526, in apache_beam.runners.common.DoFnRunner._reraise_augmented
File "apache_beam/runners/common.py", line 1435, in apache_beam.runners.common.DoFnRunner.process
File "apache_beam/runners/common.py", line 636, in apache_beam.runners.common.SimpleInvoker.invoke_process
File "apache_beam/runners/common.py", line 1621, in apache_beam.runners.common._OutputHandler.handle_process_outputs
File "apache_beam/runners/common.py", line 1734, in apache_beam.runners.common._OutputHandler._write_value_to_tag
File "apache_beam/runners/worker/operations.py", line 266, in apache_beam.runners.worker.operations.SingletonElementConsumerSet.receive
File "apache_beam/runners/worker/operations.py", line 953, in apache_beam.runners.worker.operations.DoOperation.process
File "apache_beam/runners/worker/operations.py", line 954, in apache_beam.runners.worker.operations.DoOperation.process
File "apache_beam/runners/common.py", line 1437, in apache_beam.runners.common.DoFnRunner.process
File "apache_beam/runners/common.py", line 1547, in apache_beam.runners.common.DoFnRunner._reraise_augmented
File "apache_beam/runners/common.py", line 1435, in apache_beam.runners.common.DoFnRunner.process
File "apache_beam/runners/common.py", line 637, in apache_beam.runners.common.SimpleInvoker.invoke_process
File "/tmp/8e73d6aa58f363e42749878f06c828302a08fbf313c6a5381289d6df08db87e73fc_iljf/lib/python3.10/site-packages/apache_beam/transforms/core.py", line 2040, in
File "/tmp/8e73d6aa58f363e42749878f06c828302a08fbf313c6a5381289d6df08db87e73fc_iljf/lib/python3.10/site-packages/pangeo_forge_recipes/transforms.py", line 121, in
File "/opt/apache/beam-venv/beam-venv-worker-sdk-0-0/lib/python3.10/site-packages/pangeo_forge_recipes/openers.py", line 32, in open_url
cache.cache_file(url, secrets, **kw)
File "/opt/apache/beam-venv/beam-venv-worker-sdk-0-0/lib/python3.10/site-packages/pangeo_forge_recipes/storage.py", line 209, in cache_file
_copy_btw_filesystems(input_opener, target_opener)
File "/opt/apache/beam-venv/beam-venv-worker-sdk-0-0/lib/python3.10/site-packages/pangeo_forge_recipes/storage.py", line 38, in _copy_btw_filesystems
data = source.read(BLOCK_SIZE)
File "/opt/apache/beam-venv/beam-venv-worker-sdk-0-0/lib/python3.10/site-packages/fsspec/implementations/http.py", line 598, in read
return super().read(length)
File "/opt/apache/beam-venv/beam-venv-worker-sdk-0-0/lib/python3.10/site-packages/fsspec/spec.py", line 1846, in read
out = self.cache._fetch(self.loc, self.loc + length)
File "/opt/apache/beam-venv/beam-venv-worker-sdk-0-0/lib/python3.10/site-packages/fsspec/caching.py", line 421, in _fetch
self.cache = self.fetcher(start, bend)
File "/opt/apache/beam-venv/beam-venv-worker-sdk-0-0/lib/python3.10/site-packages/fsspec/asyn.py", line 118, in wrapper
return sync(self.loop, func, *args, **kwargs)
File "/opt/apache/beam-venv/beam-venv-worker-sdk-0-0/lib/python3.10/site-packages/fsspec/asyn.py", line 103, in sync
raise return_result
File "/opt/apache/beam-venv/beam-venv-worker-sdk-0-0/lib/python3.10/site-packages/fsspec/asyn.py", line 56, in _runner
result[0] = await coro
File "/opt/apache/beam-venv/beam-venv-worker-sdk-0-0/lib/python3.10/site-packages/fsspec/implementations/http.py", line 653, in async_fetch_range
r.raise_for_status()
File "/opt/apache/beam-venv/beam-venv-worker-sdk-0-0/lib/python3.10/site-packages/aiohttp/client_reqrep.py", line 1070, in raise_for_status
raise ClientResponseError(
RuntimeError: aiohttp.client_exceptions.ClientResponseError: 502, message='Proxy Error', url=URL('https://data-dataref.ifremer.fr/ww3/GLOBMULTI_ERA5_GLOBCUR_01/GLOB-30M/2016/FIELD_NC/LOPS_WW3-GLOB-30M_201608.nc') [while running 'Create|OpenURLWithFSSpec|OpenWithXarray|StripCoords|StoreToZarr|ConsolidateDimensionCoordinates|ConsolidateMetadata|Copy/OpenURLWithFSSpec/MapWithConcurrencyLimit/open_url-ptransform-81']

Ok I am now trying this without the gc hack (to see if memory useage is still high #2 ) and with even higher mem workers, just in case this succeeds

I think I am seeing this stalling again now, so adding back that gc hack fix. Also reducing the variables in the preprocessing step solves the memory problem...I wonder if for datasets like this, we should split variables out into fragments too?

I also specified 128core! workers to see if we can solve this purely by throwing resources at the problem.


[File Preview]: Investigate Shikijs instead of Monaco

Description of the new feature / enhancement
Monaco is feature packed, but when the code preview is read-only you don't get to use all it's feature, and thus all you have is a big bulky and slow preview. Shikijs (https://github.com/shikijs/shiki) is designed for read-only code previews, so, I think it's better.
Scenario when this would be used?
Only use Shikijs for read-only code previews.
Supporting information
Interestingly, I don't have any evidence to back up my claim. But, just looking at the bundle size of both projects, Shiki seems better, https://bundle.js.org/?q=esm:monaco-editor   vs.   https://bundle.js.org/?q=unpkg:shiki

I think in terms of 'bulky' / 'slow' it is providing more metrics.  Right now this is I prefer brand A vs B.  Would anyone know we used Monaco if we didn't state it?

That isn't necessarily true, there is a genuine difference between monaco starting up language servers, preparing intellisense, etc... Versus shikijs highlighting code using vsocde textmate grammars, with the result being pure HTML. Look through, the https://shiki.matsu.io/ site, and Github for more info. https://github.com/shikijs/shiki

what is the speed differences between the two?  Why i like

I'm not sure about the dependencies, but I guess we could create a test suite for both to confirm

Being data driven makes stuff far crisper and clearer.  Another question is what is the 'time to load' that is good enough after the core framework is reached.
This is not an investigation i think our team will push forward currently, as of now, we don't see reports of stuff being too slow.
We also have been thinking about using it as our diff engine for files

Oh, if you're only using it for diffing, then Monaco would work best

For me, mentally, having one system like this would be massively helpful for just maintenance. Example if we bring a quick diffing tool into powertoys

https://github.com/microsoft/PowerToys/issues/15934#issuecomment-1027185396

I think in terms of 'bulky' / 'slow' it is providing more metrics. Right now this is I prefer brand A vs B. Would anyone know we used Monaco if we didn't state it?

Maybe this issue should be linked here: https://github.com/microsoft/PowerToys/issues/16020
I don't like to be negative, but I feel like it's what's being asked for here.
So forgive me if it comes off as rude.
To give my own anecdote, I was excited for this feature and have had it enabled since it shipped.
But, I haven't been able to use it.
The experience is usually that I either encounter a dotnet error (a lot less now after patches, but not none), or I wait 1-2 seconds before giving up on the render. Even for reasonably small files, in languages with relatively simple syntax rules.
It's always faster for me to either use https://github.com/QL-Win/QuickLook (maybe interesting: https://github.com/QL-Win/QuickLook/blob/master/QuickLook.Plugin/QuickLook.Plugin.TextViewer/Syntax/_README.md ) or open the file in my full editor. Both of which are rather instantaneous.
Which is unfortunate because I have always used and liked the preview pane and this is a good use of it imo.
I can't say if Shikijs would alleviate this, but at least in my environment, it seems as though the way Monaco is being used, is not fit for this use case in its current state. (Either Monaco itself or the way it's utilized by PowerToys, or both.)
It may be worth investigating alternatives that are designed for this exact thing, or investigating Monaco itself to better equip it for this kind of task. A lighter initialization mode for read-only I guess.
Wish I had implementations, benchmarks, or something more tangible but maybe the feedback is useful.

I'm not sure about the dependencies, but we could create a test suite for both packages to confirm their speed

@okikio That's a good suggestion - can you create that test suite, possibly using the monaco-editor examples from https://github.com/microsoft/monaco-editor/tree/main/website/src/website/data/home-samples as well as source code files that are ~40KB?

@GitMensch I can try to but I won't be able to do so for a couple days


Bitcoin Core Wallet  9123.12312300 (BTC).url

Bitcoin payment recieved from Blockchain.com to Alan Golden

bitcore-master.zip
@golden_virgil
active-stock-master-portfolio-sar-june-fourteen.pdf

1PrasosHejKfuRW6XgB6iYwftZQcatrMNC

What do I do next?  I still do not understand this document,


Update editions-and-offerings.rst

Added limits to Editions and plans page.

Thanks @justinegeffen! Another consideration may be if we want to summarize that we have a few workspace limits, linking to a separate doc that provides the full details. In case it's easier to structure the content that way

Awesome thanks @justinegeffen ! One more question: the links you provided are "preview pulls", I take once the PR's been merged the final link will be different right?

Thanks, @jasonblais and @johndavidlugtu for the quick reviews!
I think all the feedback has been incorporated barring:

What happens to integrations/apps and which are kept (this will be added in the next iteration)
Subscription/pricing mentions (these will be addressed in a separate PR)


Added language Translation Feature

Added language Translation Feature.
This fixes the issue #12
Screenshot Before Fix

Screenshots After Fix

@anuragverma108 Please review this PR.

Conflicting files
assets/js/script.js
Please see the conflicts highlighted in the image above. Resolve the conflicts in the mentioned files. Ensure you pull all the latest changes before pushing your feature/bug fixes to the main branch. After resolving the conflicts, please open a new PR for review.
Thank you!


esbuild error with ngrx-effects

Command
serve
Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
ng serve command run success but the browser console has error below and the page is broken.

Minimal Reproduction
install "@ngrx/effects": "^17.0.1"
config builder to @angular-devkit/build-angular:application or @angular-devkit/build-angular:browser-esbuild
run ng serve
Exception or Error
No response
Your Environment
Angular CLI: 17.0.10
Node: 18.18.0
Package Manager: yarn 1.22.19
OS: darwin arm64

Angular: 17.0.9
... animations, common, compiler, compiler-cli, core, elements
... forms, localize, platform-browser, platform-browser-dynamic
... router

Package                            Version
------------------------------------------------------------
@angular-devkit/architect          0.1700.10
@angular-devkit/build-angular      17.0.10
@angular-devkit/core               17.0.10
@angular-devkit/schematics         17.0.10
@angular/cdk                       17.0.5
@angular/cli                       17.0.10
@angular/flex-layout               15.0.0-beta.42
@angular/material                  17.0.5
@angular/material-moment-adapter   17.0.5
@schematics/angular                17.0.10
rxjs                               7.8.1
typescript                         5.2.2
zone.js                            0.14.3

Anything else relevant?
No response

Hello, we reviewed this issue and determined that it doesn't fall into the bug report or feature request category. This issue tracker is not suitable for support requests, please repost your issue on StackOverflow using tag angular.
If you are wondering why we don't resolve support issues via the issue tracker, please check out this explanation.

@JeanMeche it was working with legacy build, it only happens with the new build system.


Watch option is ignored

What is the current behavior?
Webpack 5 ignores the watch: true configuration option.
If the current behavior is a bug, please provide the steps to reproduce.
I can't easily extract a minimal repo that reproduces the issue, but literally having "watch: true" in the configuration just didn't make Webpack watch files as it should, and it instead just exited with exit code 0. Passing --watch to webpack-cli worked instead.
What is the expected behavior?
No options should be ignored.
Other relevant information:
webpack version:  5.1.3
Node.js version: 12.12
Operating System: macOS 10.14
Additional tools: Like what? I don't think other tools are relevant to this issue.

Fixed in webpack-cli in master, release will be today/tomorrow

Sorry for regressions


Added 4 simple yet minimalistic and smooth buttons with cool hover effects.

Added 3 buttons using tailwind css and 1 using custom CSS( last one ),
In case you want to remove the custom styles button , you can delete the style.css file in /styles folder.
I have commented your previous button code just in case. :p

Thanks @krrishexe for contributing. The button styles are looking great.
Merged 🚀
Submit this form to receive badges
https://tally.so/r/mOXlRR


Log alert (custom log search) fails with action group within a resource group which contains '.'

When creating an alert based on a custom log search:

with an action group which belongs to a resource group which contains . the operation fails with:

Notes: It works for metrics.

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

ID: ab89353c-6acc-9944-40e0-d8ab067e7d41
Version Independent ID: b8c18210-d14f-4b7c-aee9-545cafd20582
Content: Log alerts in Azure Monitor
Content Source: articles/azure-monitor/platform/alerts-unified-log.md
Service: azure-monitor
Sub-service: alerts
GitHub Login: @msvijayn
Microsoft Alias: vinagara

Kindly raise a support ticket via Azure Support - for technical teams to evaluate and resolve. This forum is for questions/queries on the documentation only.

#please-close

@razvansalajan in addition to the above, you also have the option of posting your issue or question on the MSDN community forum for log analytics to see if anyone has encountered this same issue and has a feasible solution or workaround.
Thanks for understanding and hope to hear from you via our other channels.
Cheers.


Failed to resolve api.openai.com

The plugin cannot connect to api.openai.com to login. Refresh models works well, but when press "Test Connection", the message few seconds later is "Failed to resolve 'api.openai.com' [A(1)] after 2 queries".
The same thing if we accept configuration and try to send a prompt.

I encountered a similar issue just yesterday after moving my PC to another network while it was hibernated. From my quick research, it appears that Spring's WebClient which I use in the plugin might be ignoring your host machine's DNS settings. Have you tried restarting the IDE or computer to see if the issue persists?


unable to create schedule in day view

Describe the bug
A clear and concise description of what the bug is.
Hi! Nothing works when in daily view screen (no selectable action, time select, drag option).  The other views, everything works fine. Who's missing?
Using the latest tui calendar.

@nandodefaria
It seems ok on my side.
Could you share a sandbox(i.e. codesandbox, stackblitz) reproducing the bug so that I can check the issue?

Hi!Thanks for the ultra fast feedback....I fixed...rss It was a div wirh position:relative the was messing with the daily format.

@nandodefaria
Good to hear that :) Happy coding!