add boolean sync argument to get_path()

Allows for get_path() to be called multiple times in serial without affecting performance.
Whenever get_path() is called, the Files table must be synced with the local filesystem beforehand via sync_all(). This scans over the entire file tree at the server root and essentially ensures each path is mapped to the correct file ID. This can be an expensive operation, and thus we want to minimize calls to sync_all().
This PR allows users to provide sync=False and simply call sync_all() manually beforehand. This is useful for scenarios where developers are calling get_path() multiple times in serial, and sync_all() does not need to be called between invocations. For example:
file_id_manager.sync_all()
for id in ids:
  file_id_manager.get_path(id, sync=False)

Given that sync_all() represents almost all of the performance cost of get_path(), this method is N times faster than calling file_id_manager.get_path(id) in serial, where N is the length of ids.

Codecov Report
Base: 78.59% // Head: 78.49% // Decreases project coverage by -0.09% :warning:

Coverage data is based on head (a254942) compared to base (0dd8ca0).
Patch coverage: 83.33% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #20      +/-   ##
==========================================
- Coverage   78.59%   78.49%   -0.10%
==========================================
  Files           5        5
  Lines         369      372       +3
  Branches       51       52       +1
==========================================
+ Hits          290      292       +2
  Misses         65       65
- Partials       14       15       +1

Impacted Files
Coverage Δ

jupyter_server_fileid/manager.py
88.33% <83.33%> (-0.28%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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

Shouldn't a complete system synchronization operation be performed in the background and not on each "get" call?  I don't think surfacing this in the API is correct - nor is requiring users to call sync_all() to ensure the service is up to date.
(I also see that get_id() does perform a transaction - per the PUT vs. GET discussion.)
For now, would it make sense to expose a "list-based" API (e.g., get_paths(ids: List[str]) -> List[Tuple[str, str]]) that takes a list of Ids and returns a list of tuples (Id, path)?   This way you're not exposing a sync flag that would become obsolete once synchronization is moved into the background as an internal optimization.
A mirrored get_ids() would be a bit more clunky and probably less popular, but should probably exist for consistency.
If this approach was adopted, it might make more sense to return a Dict[str, str] since that can be more naturally represented in JSON (in the REST response).

Shouldn't a complete system synchronization operation be performed in the background and not on each "get" call?

Well, if you're willing to sacrifice consistency between the filesystem and the Files DB table, then sure. We could call sync_all() on a time interval, say every 10 seconds, in the background. However, if get_path() doesn't call sync_all() every time, then if the file was moved after the last sync interval, then get_path() would return you the wrong path.
Essentially this is a tradeoff between consistency and performance. My objection to adding this feature as a configurable trait is that I don't see a demonstrable usecase where you want a file path given a file ID and are somehow OK with it being out-of-date. If there is a usecase for that, I still believe that it should not be the default. We should prioritize our methods being as correct as possible out-of-the-box, while allowing users to opt-in to any features that would sacrifice correctness.

(I also see that get_id() does perform a transaction

Yes. Basically we will delete a record if we find a record with the same inode number but different timestamps, since we are assuming that the file at the current path is a completely different file from the one recorded. Otherwise if both the inode number and timestamps match, we update the record with the current path.
I believe this is an implementation detail that just helps maintain consistency between the filesystem and files table. Don't think this should change the HTTP verb we use.

The proposal that I had was to add a get_paths() API and have both get_path() and get_paths() accept a time delta argument. The implementation would then look at how long it has been since sync_all() has been called and call it again if that time is longer than the time delta argument. That would let the caller determine the time interval over which it wants to make sure that filesystem changes are detected, while allowing multiple clients to call these APIs without worrying about calling sync_all() needlessly. Alternatively, we could make that time delta a configurable trait on the local file system file id manager.
The big picture though is that the file id APIs will likely need to update state on a regular interval and we need to make sure we do that in a manner that allows multiple clients to call these APIs without calling sync_all() too many times. We should also probably localize calls to get_paths made from JupyterLab to once place to allow us to update the paths for all open files in a single network call.

I should note that the sync flag wouldn't be able to optimize the case of multiple clients calling these APIs in a manner that doesn't lead to calling sync_all() too many times.

Essentially this is a tradeoff between consistency and performance

Yes, and I believe you're optimizing for the wrong thing. You've decided to penalize the most common API calls (get_xxx()) to address use cases that, frankly, aren't going to be that common- especially when syncing at startup.  (Heck, out-of-band updates don't really exist in Cloud storage or DB-based CMs.)  I'm not saying you need to discard synchronization, just saying it should be moved into the background since users should not care or have to worry about their files being synchronized or specify a time delta!
(I apologize.  I will no longer comment on implementation details.  I will, however, continue to comment on API decisions since that is the contract by which other FileID Services implementations must adhere and they should be able to hide these kinds of decisions from their users.)

Thinking a bit more overnight. If there are N RTC clients, those clients would need to poll get_paths() on a regular interval, which causes a lot of issues. I think a better approach is as follows:

The file id manager should call sync_all in a subprocess on a regular interval.
Each time there is a path change, it should public an event on the event bus.

This way, each client won't have to poll the server to get all these updates. I think this aligns with how @kevin-bates is thinking in his last comment as well.

I'm not saying you need to discard synchronization, just saying it should be moved into the background since users should not care or have to worry about their files being synchronized or specify a time delta!

Hm, even since this project was started, our north star was as follows:

file ID should be as correct as possible out-of-the-box
file ID should be optimized for the most common use-case, which I had believed to be local instances accessing local filesystems

If we do add a sync interval and set it to be the default (i.e. get_path() no longer calls sync_all() by default), we're essentially changing point 1) to read "file ID should balance performance and correctness". Which I think is fine (as there are pros and cons to both), but I believe it requires agreement from others who may want to use file ID. I'll chat with our team members working on the notebook scheduling extensions, and get back to you on what we think.

(I apologize. I will no longer comment on implementation details. I will, however, continue to comment on API decisions since that is the contract by which other FileID Services implementations must adhere and they should be able to hide these kinds of decisions from their users.)

No, I think your comments are super valuable! To be honest, you've been one of the only other contributors critiquing our design. We value your feedback a lot.

The file id manager should call sync_all in a subprocess on a regular interval.

Yes, this would offload the server quite a bit, since the current implementation is not async (see my concerns about performances in #13).


Using Indicator when the RecyclerView content is empty leads to crash

Similar to this Issue. Exception being thrown is IndexOutOfBoundsException, not ArrayIndexOutOfBoundsException. So the solution would be to catch parent exception.

Made PR

Any updates?


Restructure modules for cleaner code.

Split runtime into a separate "Type" module.
Minor cleanup: use newtypes.
Split out an "Error" module.

Thanks! I've rebased your branch on top of steps, which is now the PR's target branch. I should merge all the waiting branches soon.
I'm wondering why some functions are in Curiosity.Runtime.IO and others in Curiosity.Runtime.AppM, e.g. checkCredentials, or why Runtime is in Type.hs, but AppM is in AppM.hs (or RunM is still in Runtime.hs). Is there some rule of thumb you tried to follow ?
For checkCredentials, I think this is because you need it in the S.DBStorage instance, but I fear that it would mean that if that instance was growing, almost everything that is in Runtime.hs should meve there ?
About your comment for AppM:

the reason why I've put this under IO since it provides functionality over IO.

Indeed, that was what we agreed on: Data/ is for pure code, Core/ is for STM on top of the pure code, and Runtime/ is for IO on top of STM (mainly to provide logging and calls to atomically).


Restructured the project to allow for extension modules

This change moves almost all files. If this interferes with your changes, finish those and push them first. I will resolve any conflicts and create a new PR if needed.

Sorry for the conflicts as a result of merging the other PR.  Could you resolve the conflicts?


Fake cmi

I wanted to run only the fake control mode interface, this makes that possible

I added some comments in https://github.com/UM-ARM-Lab/kuka_iiwa_interface/pull/133 that are relevant to this PR

I added some comments in https://github.com/UM-ARM-Lab/kuka_iiwa_interface/pull/133 that are relevant to this PR

@LemonPi I updated it to have the argument thing you suggested, does that look good?

@LemonPi I updated it to have the argument thing you suggested, does that look good?

Yup

Yup


CUDA Graph open fail

System information

OS Platform and Distribution (e.g., Linux Ubuntu 20.04): Linux
DeepRec version or commit id: be62ec312595b51b74260f96a6c0872ce5f1540c
Python version: 3.8
Bazel version (if compiling from source): 0.26.1
GCC/Compiler version (if compiling from source): gcc 9.4.0
CUDA/cuDNN version: cuda11.6/cuDNN8

Describe the current behavior
My usage is:
SessionOptions options;
options.config.mutable_gpu_options()->set_cuda_graph_enable_jit(true);
auto status = tensorflow::LoadSavedModel(options, tensorflow::RunOptions(), model_path, {"serve"}, &bundle);
for (int i = 0; i < loops; ++i) {
   status = bundle.session->Run(inputs, out_names, {}, &outputs);
}

But I can't observe cudaGraph used in nsight system.

Describe the expected behavior
Some sub graph can run by cuda Graph.
Are there any examples of using cuda Graph?

I found that because I didn't compile DeepRec with XLA.
After I fix it, there will be cudaGraphLaunch in the graph when running.
But some times the results is random error, why?

session run error or random results?

session run error or random results?

Random results.


[e2e]: maven workflow_dispatch main default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/11421751221
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.maven.workflow_dispatch.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.maven.workflow_dispatch.main.default.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Sun Oct 20 00:11:13 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/11430754907
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.maven.workflow_dispatch.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.maven.workflow_dispatch.main.default.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Mon Oct 21 00:11:03 UTC 2024
Tests are passing now. Closing this issue.


Pastevents Section added.

Related Issue

#14

Proposed Changes

index.html for past events section added.
styles.css for past events section added.
-images  for past events section added.

Checklist

[x] Documentation of the code
[x] Add your name to the CONTRIBUTORS file
[x] Testing your code in the local machine

Screenshots

LGTM! Thanks for making a PR.

@Debdeep1  is my work fine? kindly comment about this as I am a fresher  your review means a lot to me. Also this is my first contribution in open source.


Add commands for slashing down validators using DowntimeSlasherv2

Description

Adds validator:set-bitmaps command
Adds validator:downtime-slash command
Modify validator:signed-blocks command to work well with downtime slasher

Other changes

Adds intArray flag parser

Tested
Tested on private test net
Slashed successfully on baklava
downtime-slash-history.txt
Related issues

Fixes https://github.com/celo-org/celo-monorepo/issues/5508

Backwards compatibility
Brief explanation of why these changes are/are not backwards compatible.

I guess I don't understand the bitmap stuff, anywhere you can point me to some docs? At first glance I don't understand how slashing start and end periods are a range, but that's unrelated to this PR.

I guess I don't understand the bitmap stuff, anywhere you can point me to some docs? At first glance I don't understand how slashing start and end periods are a range, but that's unrelated to this PR.

The canonical validator set for a given epoch is stored in an ordered list. The signature bitmap tracks whether a validator has signed all blocks in the current epoch by OR-ing all of the block header signatures. The signature bitmaps can't span epoch boundaries because the signer indices in the list can and will change. As a result, we need to slice the intervals on epoch boundaries. The bitmap set is also very gas heavy as it is doing a storage write for each block in the range, so we need to segment the intervals such that the gas limit isn't exceeded.
I refactored this code a bunch to work with an interval type which is hopefully clearer for consumers.


handle comment inside parseFieldDefinitionList

Hi, Thanks to develop great project!
I tried to use federation gateway to my toy project.
but it isn't works well... 😿
I investigated codes & found issue.
My code include commented out field in object type definitions.
likes below.
"""
テスト用のデータです。
"""
type FooBar @goModel(model: "github.com/vvakame/test/foobar.FooBar") {
    name: String
    # logoURL: String
}

@jensneuse Hi! thanks to merge master/HEAD to my branch.
I didn't know why CI is not running. but I guess I am a first time contributor to this repo.
https://docs.github.com/en/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks 🤔 ?


[IS] Secure the secrets in Action Management component

Describe the Issue:
With the introduction of the new Action Management component, we are storing the secrets of the external endpoints in our system.
Since we have a Saas offering it's a must to ensure that the secrets are properly encrypted before adding them to the database which is also comes as a requirement in the SOC compliance.
So we need to improve the action-mgt component to store the secrets using the secret-mgt component.

Sub Task Issue for: https://github.com/wso2/product-is/issues/20747

Related PRs:

https://github.com/wso2/carbon-identity-framework/pull/5795
https://github.com/wso2/identity-api-server/pull/630
https://github.com/wso2/product-is/pull/20706

Change PATCH endpoint to update the full action including minor bug fixes:

https://github.com/wso2/carbon-identity-framework/pull/5808
https://github.com/wso2/identity-api-server/pull/635
https://github.com/wso2/product-is/pull/20736

Closing this issue and track the progress through https://github.com/wso2/product-is/issues/20748


Update our System Team internal Guidelines

Description
Our current https://catenax-ng.github.io/docs/how-to-onboard-teams-to-any-environment page is not up-to-date and not in sync with our documentation in the repository https://github.com/catenax-ng/product-onboarding
The discussion is happening in the Team, there are two options:

Move everything from the page to the repository README.md (keeping the documentation close) and then referencing the product-onboarding repo in our catenax-ng.github.... docs page
Move everything out of the repository README.md's and update our catenax-ng.github.... docs page.

AC

[ ] docs are correct

Visualisation
https://catenax-ng.github.io/docs/how-to-onboard-teams-to-any-environment

will be removed or moved anyway on catena-x side.


overwrite - handle overwrite of non-empty objects with plain values

linked to #646
Result before:
/Path/to/repro/node_modules/dot-object/index.js:118
        throw new Error("Trying to redefine non-empty obj['" + k + "']")
              ^

Error: Trying to redefine non-empty obj['startDateTime']
    at DotObject._fill (/Path/to/repro/node_modules/dot-object/index.js:118:15)
    at DotObject._fill (/Path/to/repro/node_modules/dot-object/index.js:114:10)
    at DotObject.str (/Path/to/repro/node_modules/dot-object/index.js:179:10)

Result after:

@nicklloyd Do you see any risk or side-effect of this?

it's getting 'set' later in the flow yea? You're just removing it beforehand if it's an object?

it's getting 'set' later in the flow yea? You're just removing it beforehand if it's an object?

Yes, we are removing the "object" to replace it with a "string" value,
// Update property from object
return dot.str(path, newValue, objectOrArray)

since the "dotObject" library cannot handle overwriting an object, so it throws an error.

seems fine... can't recall if it was just bloat that kept us from using lodash... they've fixed all that with more recent version

Sidetrack: Do you suggest that we can/should replace DotObject with Lodash?


readthedocs: Provide links for high level sections

Updated the layout to provide links for high level sections. See screenshot for details.

Codecov Report

Merging #3939 into master will decrease coverage by 0.13%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #3939      +/-   ##
============================================
- Coverage     67.27%   67.13%   -0.14%
  Complexity        4        4
============================================
  Files          1032     1032
  Lines         50946    50946
  Branches       7119     7119
============================================
- Hits          34275    34205      -70
- Misses        14331    14401      +70
  Partials       2340     2340

Impacted Files
Coverage Δ
Complexity Δ

...apache/pinot/common/metrics/ValidationMetrics.java
20.28% <0%> (-59.43%)
0% <0%> (ø)

...ller/validation/OfflineSegmentIntervalChecker.java
26.74% <0%> (-38.38%)
0% <0%> (ø)

...egation/function/customobject/MinMaxRangePair.java
75.86% <0%> (-24.14%)
0% <0%> (ø)

...mpl/dictionary/DoubleOffHeapMutableDictionary.java
69.09% <0%> (-9.1%)
0% <0%> (ø)

...e/impl/dictionary/LongOnHeapMutableDictionary.java
88.88% <0%> (-6.67%)
0% <0%> (ø)

.../impl/dictionary/FloatOnHeapMutableDictionary.java
86.66% <0%> (-6.67%)
0% <0%> (ø)

...e/operator/dociditerators/SortedDocIdIterator.java
58.33% <0%> (-5.56%)
0% <0%> (ø)

...impl/dictionary/FloatOffHeapMutableDictionary.java
81.81% <0%> (-5.46%)
0% <0%> (ø)

...e/operator/dociditerators/BitmapDocIdIterator.java
60.71% <0%> (-3.58%)
0% <0%> (ø)

...org/apache/pinot/common/metrics/MetricsHelper.java
72.5% <0%> (-2.5%)
0% <0%> (ø)

... and 17 more

Continue to review full report at Codecov.

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

LGTM 👍


Bug in 2015 MiniZinc challenge

Hi,
I thought I would log this here just as an additional test for the upcoming 2017 challenge.
I noticed the following in the results for the "mapping" "ring_2" instance: Cplex, jaCoP, Chuffed and Choco all managed to prove they had the optimal solution at 1940. Or-tools beat them all at 1640. Assuming the group consensus is correct, this suggests there was an error in the flatzinc layer that year.
Looking at the commits recently, I think Laurent has completely re-written this layer and probably fixed this but it may be worth confirming before the next challenge (we like or-tools and enjoy watching it do well in this event).
Thanks
Rob

Hi,
Thank you for noticing ! I don't know if it has been fixed since..

This is fixed.


Fix config table name

The index field uses registries so we should match that here.
r? @alexcrichton

r? @withoutboats
I'd be a little worried if this doesn't break any tests...

I believe this PR is correct. My understanding is we have a registry.token field for the default registry, but all fields corresponding to other registries should be under registries.{}, as this PR makes so. I think this was just a discrepency between the PR to make publish work (which uses the token) and the PR to make fetch work (which doesn't).
And the publish tests failed, which shows that the tests were using this behavior. But we should rewrite the tests and fix things to be correct.

Ok, so things are currently pretty messy. In .cargo/config, we have
[registry]
index = ".."
token = "..."

[registries.my-registry]
index = ".."
token = "..."

while in .cargo/credentials we have
token = "..."

[my-registry]
token = "..."

IIRC registries was used for .cargo/config so that there'd be no conflict with arbitrary registry names - you could have a registry called index or token for example. This problem still exists for .cargo/credentials though. A registry named token will break things. On the implementation side of things, cargo just merges the contents of .cargo/credentials into .cargo/config's [registry] block, which causes this issue with custom registry tokens.
What's the right thing to do here? It seems like the format of .cargo/credentials needs to change to avoid the naming conflict. We also currently load anything from .cargo/credentials, not just tokens which we may want to tighten up?

Probably both files should use the same format, so registries in the credentials.

We also currently load anything from .cargo/credentials, not just tokens which we may want to tighten up?

Maybe. It seems confusing but useful to allow anything in credentials - anything you don't want to be backed up can go there (which is probably your credentials, but maybe not).

Cool, so .cargo/credentials would have the same layout as .cargo/config except that it only contains token fields, right? i.e.
[registry]
token = "..."

[registries.my-registry]
token = "..."

Do you think we need to worry about back compat for existing credentials files?

Do you think we need to worry about back compat for existing credentials files?

If all you're doing is changing the token for alt registries, no because that's an unstable feature.

Oh, I see. credentials has token at the top level right now!
I think we need to be backwards compatible with that, so we should accept the default registry token at token or registry.token, but all alt registries under the registries table, not registry.

Updated!


Fix: release label

Description:

Add - release - label for release PRs
Also add badge to README for latest Github Release

Visual:
N/A
TODO:

[x] Complete PR Body
~[ ] Updated Architecture/README documents~

!merge


Alpha and Beta for Cd assumptions?

I noticed that your Cd is purely from (I assume Rasaero) Power on and Power off cd data. With Missile Datcom readers and other simulations, either Alpha or both Alpha and Beta values are plotted along with Mach in order to yield a Cd at a certain moment in time. Do you make any adjustments to your Cd in order to account for this difference (like some kind of offset)? Or does your code make the assumption of small angle of attack and symmetric about an axis to avoid using this information? It's a good assumption tbh, if that's what you're doing, but how do your results compare to something like Rasaero or Open Rocket?

@Gui-FernandesBR

I'm sorry @giovaniceotto, but you are probably the best person to answer that question. But I will try...
@nbrophy3 , in fact, Rocketpy considers the drag force (R1) as always parallel to the rocket's axis. We know that the most common literature assumes that the drag acts in a direction opposite to the movement of the aircraft, but there is also a reason for our approach.
I think it is more common to consider the drag force towards the "aircraft" axis (as RocketPy does) when we are working with rockets, but this is not a very certain answer. I'm sure @giovaniceotto can give us a good reason for that assumption.

The complete resolution for this question can be read on RocketPy Article, See Flight and Rocket Model for better compreend it.
"Aerodynamic forces acting on rockets are usually decomposed into the axial force A and the normal force N"


Add NewRelic.

@Osmose r?

This has been on my todo list for like a year straight, neato!
r+, looks good to me!

Good! I'm merging this. Let me know if you have troubles deploying this.


Quality selector does not load on small screens

On small screen the quality selector dropdown does not loads.
This is mainly because there is no header in small screen. Even if I manage to somehow add the button the UI does not match

@jineshpatel30 the bugs you mentioned are fixed in v0.7 release

@jineshpatel30 the bugs you mentioned are fixed in v0.7 release

Great, thanks for fixing them quickly :)


Fixes #1328 - Added getExtension() helper function

Added a helper function for retrieving a nested FHIR Extension based on a collection of nested string URLs (based on the existing getExtensionValue() function) and a supporting unit test.

This looks great. Thanks for the contribution!

Thanks, happy to help!

Coverage: 93.702% (+0.002%) from 93.699% when pulling 1d6ba99e1b53053dbcc8e94a1b5cec8f96e71163 on espresso:main into 585a56ca1c0dbbe60cc9ff8c344d13357dc71166 on medplum:main.


Broken Breadcrumbs

@mmcky are these good now?

Footer is still broken.
https://github.com/QuantEcon/lecture-source-py/issues/131

I am not sure this is fixed until we can test it.  Lets leave open until after the smoke test.

I have tested and am closing.


Add smart pointers to all screens

[x] All screen instances are replaced with std::unique_ptr<> and their getInstance() method is updated to instance.reset(new typename)
[x] The remaining member variables are changed to smart pointers

Done


Add files via upload

@ahmedjaabiri I am sorry for a delay with processing your request.
Pull request merged. Thank you!


This extension violates the Chrome Web Store policy.

any idea why?

Just noticed this as well, also curious about it.


Add GD32E103(arm cotex-m4) device support

This PR adds support for GigaDevice GD32E103VBT6 SoC and GD32E103V-EVAL board that is use the SoC.
Currently, the west module dependency points to https://github.com/feilongfl/hal_gd32.
I'm not sure where can I put these code,I found another issues #34971 have gigadevice RISKV device,but I think it's not good to put code there.
At this time, Only samples/basic/blinky is work.And lots of code is copy from stm32, So some code is not necessary.

Sorry, I found that I changed the file of the stm32 platform by mistake, and the correction is in progress.


[Docker] Laravel Sail Support

As #323 and #316 suggested, we are going to introducing docker support since Laravel 8 uses Laravel Sail to handle docker deployment and development.
We upgrade NOJ to Laravel 8.x and docker version would be available soon later.

Looking forward to this ❤
Any help that you might need?

Looking forward to this ❤
Any help that you might need?

Actually I've tried with https://github.com/ZsgsDesign/NOJ/issues/316#issuecomment-635858260 and been working fine I guess

Actually I've tried with https://github.com/ZsgsDesign/NOJ/issues/316#issuecomment-635858260 and been working fine I guess

Actually I've tried with https://github.com/ZsgsDesign/NOJ/issues/316#issuecomment-635858260 and been working fine I guess

So glad to hear about that. As for official support, I am going to make that a reality by this weekend based on the template mentioned in #316.
If you encountered any bug while using the docker solution, Please left a comment.


Fix typos and whitespace

@lowensk can you please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
git commit --amend -s --no-edit && git push -f

@lowensk thanks

@vieux np :)


QPC: All platforms are unstable

Ref: https://ci.adoptopenjdk.net/job/QEMUPlaybookCheck/229/
With the latest QPC run, all platforms have failed to some degree. 4 have failed due calling buildJDK.sh in an incorrect way (incorrect as of #1962 ).
The risc-v platform is still blocked by #1483
And the arm32 platform seems to be running out of space during the playbook execution.

Changes made to qemuPlaybookCheck.sh have been made to use the correct arguments (willsparker/2123_1). Testing on QPC at: https://ci.adoptopenjdk.net/job/QEMUPlaybookCheck/230/

The above PR should fix the buildJDK.sh issues. Once this has been merged, I'll look at running the arm32 box, to determine if there's still issues with the space.

The PR to fix the arguments has been merged, and it appears to be working on all platforms. For the S390x and ppc64le architectures, the linux.sh script fails for JDK8, as it is unable to find JDK7 on the machines (as Zulu-7 is not installed). I thought that they were meant to default then to using JDK8, but apparently not. This is not the case for JDK11, where I have had the build start on both machines (though currently, I've only managed a QPC run that had ppc64le fail (maybe due to the wrong version of gcc..?), and s390x that core dumped (maybe due to a bad jdk-10 install..?))
I'm going to look into that platform-specific-configuration script, to see if it's meant to set the boot jdk to the build jdk in cases wehre the boot jdk can't be found. If it isn't, I'll look into install zulu-7 on those platforms.

It can always be overriden with JDK7_BOOT_DIR if needed, but I know we've tried to let the autodetection work.
My preference is for it not to fall back if possible, since you then run the risk of being unsure whether from one build to the next it's used a JDK7 or JDK8 as the boot JDK. Our "real" CentOS/RHEL7 ppc64le and s390x build machines all use a true JDK7.

Okay! Thanks for the guidance. Looks like I'll have to adapt the Zulu-7 install to include those platforms :-)

QEMU qcow2 images can be resized easily enough with
qemu-img resize $IMG +10G (if you wanted to add 10GB to it).
However, the partitions still need to be extended, which will be specific to the platform, and is likely to be a massive pain. Helpfully, I think all of the platforms that fail due to disk issues will fail in the build. Therefore, we could mount it as a new partition and just build on that one if it's that difficult.

List of what I did to extend each of the images. After extending partitions, I'll re-compress the image with xz -z, and move the images into /home/jenkins/qemu_base_images/resized_images/, that way we still have backups of the old images

[x] Debian10.aarch64.dsk :

Image is qcow2, so extend by running qemu img resize $IMAGE +10G

When logging into the machine, it automatically extended the root partition, which was lovely to see. So that has 25GB on it now.

[x] Debian11.riscv.dsk:

qcow2 image, so same command as above.

This one has 10GB mounted on the root partition, and 5GB on /home/linux. So, I'll delete the /home/linux partition and create a new one in the same place, of size 15GB:

root@debian:~# lsblk
NAME   MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda    254:0    0  25G  0 disk
|-vda1 254:1    0  10G  0 part /
`-vda2 254:2    0   5G  0 part /home/linux
root@debian:~# fdisk /dev/vda
Command (m for help): d
Partition number (1,2, default 2): 2

Partition 2 has been deleted.

Command (m for help): n
Partition number (2-128, default 2): 2
First sector (20971393-52428766, default 20971520):
Last sector, +/-sectors or +/-size{K,M,G,T,P} (20971520-52428766, default 52428766):

Created a new partition 2 of type 'Linux filesystem' and of size 15 GiB.
Partition #2 contains a ext4 signature.

Do you want to remove the signature? [Y]es/[N]o: Y

The signature will be removed by a write command.
Command (m for help): w
The partition table has been altered.
Syncing disks.

root@debian:~# lsblk
NAME   MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda    254:0    0  25G  0 disk
|-vda1 254:1    0  10G  0 part /
`-vda2 254:2    0  15G  0 part /home/linux

[ ] Debian8.Arm32.dsk:

Still a qcow2 image, so, as above

This ones a bit different, there's a lot more partitions:
$ lsblk
NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
vda    254:0    0   30G  0 disk
├─vda1 254:1    0  243M  0 part /boot
├─vda2 254:2    0  5.3G  0 part /
├─vda3 254:3    0    1K  0 part
├─vda5 254:5    0  502M  0 part [SWAP]
└─vda6 254:6    0   14G  0 part /home

Unfortunately, I can't seem to find a way of extending the root partition, without the following error / issue on startup
[  155.371104] FS-Cache: Netfs 'nfs' registered for caching
Welcome to emergency mode! After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" to try again
to boot into default mode.
[  155.698568] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Give root password for maintenance
(or type Control-D to continue):

I tried removing partitions 2-6, and recreating the / and /home partition, but the same issue occurs. I tried just removing the second and third partition, and it caused the rest of them to disappear as well. I'm going to skip this one for now, in the hopes that somebody else knows how to do this ( @sxa ...? :eyes: )

[x] Ubuntu1804.arm64.dsk:

The disk format is raw. I was able to extend it with qemu-img resize <> +10G though, and it is showing up in lsblk:
NAME                             MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
vda                              252:0    0   30G  0 disk
├─vda1                           252:1    0  512M  0 part /boot/efi
└─vda2                           252:2    0 19.5G  0 part
  ├─ubuntu--18--arm64--vg-root   253:0    0 18.6G  0 lvm  /
  └─ubuntu--18--arm64--vg-swap_1 253:1    0  976M  0 lvm  [SWAP]

However, whenever I run any fdisk commands, I get
GPT PMBR size mismatch (41943039 != 62914559) will be corrected by w(rite)., which fails when I exit, with fdisk: failed to write disklabel: Invalid argument. For some reason, fdisk can't fix this, but parted can. Running parted -l will prompt a fix/ignore check. AFter this, I followed the instructions from this link - created a new partition with fdisk (called /dev/vda3) with the remaining space, created the physical volume pvcreate /dev/vda3, extended the volume group with vgextend /dev/ubuntu-18-arm64-vg /dev/vda3. From there, I extended the LV that was needed lvextend +2568 /dev/ubuntu-18-arm64-vg/root and resized it to the file system : resize2fs /dev/ubuntu-18-arm64-vg/root.
The result is:
root@ubuntu-18-arm64:~# lsblk
NAME                             MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
vda                              252:0    0   30G  0 disk
├─vda1                           252:1    0  512M  0 part /boot/efi
├─vda2                           252:2    0 19.5G  0 part
│ ├─ubuntu--18--arm64--vg-root   253:0    0 28.6G  0 lvm  /
│ └─ubuntu--18--arm64--vg-swap_1 253:1    0  976M  0 lvm  [SWAP]
└─vda3                           252:3    0   10G  0 part
  └─ubuntu--18--arm64--vg-root   253:0    0 28.6G  0 lvm  /

Which looks alright to me :+1:

[ ] Ubuntu18.ppc64le.dsk:

Also uses LVM, and a raw disk image, so I'll do the same process as before, hopefully.

With all but the Debian.ARM32 image extended, I'll swap the original images with the resized images to test on the vagrant server. I'm aware that now QPC can run on build-equinix-ubuntu2004-armv8-1, so I'll quickly reconfigure the job to just use the infra-ibmcloud-vagrant* machines for the time being. If all goes well, I'll move the images over :-)

Latest failures/instabilities
ppc64le ubuntu18 - fails in the test stage. Looks like the test script needs to be updated to support the new name of the tests repo
00:17:27 TESTDIR: /home/linux/testLocation/openjdk-tests is invalid. Please use --testdir|-t to set valid TESTDIR under aqa-tests. Default value current dir (pwd) is used if not provided.
00:17:32 /home/linux/openjdk-infrastructure/ansible/pbTestScripts/testJDK.sh: line 15: cd: /home/linux/testLocation/openjdk-tests/TKG: No such file or directory
00:17:32 + grep -q 'FAILED: 0' /home/vagrant1/workspace/QEMUPlaybookCheck/ARCHITECTURE/ppc64le/OS/ubuntu18/label/vagrant/ansible/pbTestScripts/qemu_pbCheck/logFiles/UBUNTU18.PPC64LE.test_log
00:17:32 + echo TEST FAILED

s390x ubuntu18 - fails when ansible tries running apt-get upgrade, https://ci.adoptopenjdk.net/job/QEMUPlaybookCheck/272/ARCHITECTURE=s390x,OS=ubuntu18,label=vagrant/consoleFull
12:07:41 TASK [Common : Run apt-get upgrade] ********************************************
12:43:05 fatal: [localhost]: FAILED! => {"changed": false, "msg": "'/usr/bin/apt-get upgrade --with-new-pkgs ' failed: E: Sub-process /usr/bin/dpkg returned an error code (1)\n", "rc": 100, "stdout": "Reading package lists...\nBuilding dependency tree...\nReading state information...\nCalculating upgrade...\nThe following NEW packages will be installed:\n  distro-info gcc-11-base libgcc-s1 libnetplan0 linux-headers-4.15.0-144\n  linux-headers-4.15.0-144-generic linux-image-4.15.0-144-generic\n  linux-modules-4.15.0-144-generic linux-modules-extra-4.15.0-144-generic\nThe following packages will be upgraded:\n  accountsservice apt apt-utils base-files bind9 bind9-doc bind9-host\n  bind9utils bsdutils busybox-initramfs busybox-static ca-certificates dbus\n  distro-info-data dmeventd dmsetup dnsutils e2fsprogs fdisk file\n  friendly-recovery gcc-8-base initramfs-tools initramfs-tools-...

aarch64 ubuntu18 - disconnected during build stage, playbook passes without error
01:01:35 Connection to localhost closed by remote host.
aarch64 debian10 - Connection reset by peer
12:01:00 TASK [Gathering Facts] *********************************************************
12:01:00 fatal: [localhost]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: kex_exchange_identification: read: Connection reset by peer\r\nConnection reset by <IP_ADDRESS> port 10020", "unreachable": true}

arm32 debian8 - Fails to download GCC 7.5 binary. URL is invalid
14:15:17 TASK [gcc_7 : Download AdoptOpenJDK gcc-7.5.0 binary] **************************
14:15:35 fatal: [localhost]: FAILED! => {"changed": false, "dest": "/tmp/ansible-adoptopenjdk-gcc-7.tar.xz", "elapsed": 6, "msg": "Request failed", "response": "HTTP Error 404: Not Found", "status_code": 404, "url": "https://ci.adoptopenjdk.net/userContent/gcc/gcc750+ccache.armv7l.tar.xz"}
14:15:35

riscv seems to be successful in its playbook run

Looks like the test script needs to be updated to support the new name of the tests repo

Hmmm all requests to the old repo should redirect so there may be another underlying issue there ...

Hmmm all requests to the old repo should redirect so there may be another underlying issue there ...
I received this error in my own time when I was running some tests using the tests repo. This error would pop up when using the ./get.sh script. I found that changing the folder name to aqa-tests solved it. Ive put in the pr https://github.com/adoptium/infrastructure/pull/2230, ill be testing it to see if it solves it

arm32 debian8 - Fails to download GCC 7.5 binary. URL is invalid

That looks from the log as though the job was tested using a fork of the repository that doesn't have this change in it: https://github.com/adoptium/infrastructure/pull/2201/files

That looks from the log as though the job was tested using a fork of the repository that doesn't have this change in it: https://github.com/adoptium/infrastructure/pull/2201/files

Possibly. I was testing this pr, https://github.com/adoptium/infrastructure/pull/2203 (I shouldve just tested the playbook run in hindsight since the changes only affect mac), at the time. Ill run a new job on master

I received this error in my own time when I was running some tests using the tests repo. This error would pop up when using the ./get.sh script.

Ah right ... So get.sh has been modified to explicitly check that it has been extracted to a directory with the new name, which isn't the case when going via the redirect so https://github.com/adoptium/aqa-tests/pull/2612/files is what broke it. In that case it should be an easy fix :-)

Possibly. I was testing this pr, #2203 (I shouldve just tested the playbook run in hindsight since the changes only affect mac), at the time. Ill run a new job on master

Looks like its able to download it fine, but seems to have run out of space on the disk. Odd
14:27:07 TASK [gcc_7 : Extract AdoptOpenJDK gcc-7 binary to /usr/local/gcc] *************
14:31:01 fatal: [localhost]: FAILED! => {"changed": false, "dest": "/usr/local/", "extract_results": {"cmd": ["/bin/tar", "--extract", "-C", "/usr/local/", "-z", "-f", "/tmp/ansible-adoptopenjdk-gcc-7.tar.gz"], "err": "/bin/tar: gcc/libexec/gcc/armv7l-unknown-linux-gnueabihf/7.5.0/cc1obj: Wrote only 9728 of 10240 bytes\n/bin/tar: gcc/libexec/gcc/armv7l-unknown-linux-gnueabihf/7.5.0/lto-wrapper: Cannot write: No space left on device\n/bin/tar: gcc/libexec/gcc/armv7l-unknown-linux-gnueabihf/7.5.0/lto1: Cannot write: No space left on device\n/bin/tar: gcc/libexec/gcc/armv7l-unknown-linux-gnueabihf/7.5.0/f951: Cannot write: No space left on device\n/bin/tar: gcc/libexec/gcc/armv7l-unknown-linux-gnueabihf/7.5.0/install-tools: Cannot mkdir: No space left on device\n/bin/tar: gcc/libexec/gcc/armv7l-unknown-linux-gnueabihf/7.5.0/install-tools: Cannot mkdir: No space left on device\n/bin/tar: gcc/libexec/gcc/armv7l-unknown-linux-gnueabihf/7.5.0/install-tools/fixincl: Cannot open: No such file or directory\n/bin/tar: gcc/libexec/gcc/armv7l-unknown-linux-gnueabihf/7.5.0/install-tools: Cannot mkdir: No space left on device\n/bin/tar: gcc/libexec/gcc/armv7l-unknown-linux-gnueabihf/7.5.0/install-tools/fixinc.sh: Cannot open: No such file or directory\n/bin/tar: gcc/libexec/gcc/armv7l-unknown-linux-gnueabihf/7.5.0/install-tools: Cannot mkdir: No space left on device\n/bin/tar: gcc/libexec/gcc/armv7l-unknown-linux-gnueabihf/7.5.0/install-tools/mkheaders: Cannot open: No such file or directory\n/bin/tar: gcc/libexec/gcc/armv7l-unknown-linux-gnueabihf/7.5.0/install-tools: Cannot mkdir: No space left on device\n/bin/tar: gcc/libexec/gcc/armv7l-unknown-linux-gnueabihf/7.5.0/install-tools/mkinstalldirs: Cannot open: No such file or directory\n/bin/tar: gcc/libexec/gcc/armv7l-unknown-linux-gnueabihf/7.5.0/liblto_plugin.la: Cannot write: No space left on device\n/bin/tar: Exiting with failure status due to previous errors\n", "out": "", "rc": 2}, "gid": 50, "group": "staff", "handler": "TgzArchive", "mode": "02775", "msg": "failed to unpack /tmp/ansible-adoptopenjdk-gcc-7.tar.gz to /usr/local/", "owner": "root", "size": 4096, "src": "/tmp/ansible-adoptopenjdk-gcc-7.tar.gz", "state": "directory", "uid": 0}

Running new job at https://ci.adoptopenjdk.net/view/Tooling/job/QEMUPlaybookCheck/ to evaluate current status.

This might be tricky to fully work through in a short period, but I'm adding good first issue since it should be possible for someone with good interest in cross-platform virtualisation to try and work on using their own machines.

As of 19/12/22 the failing builds are
aarch64 deb10
23:03:53 TASK [Common : Allow https apt sources] ****************************************
23:04:36 [WARNING]: Updating cache and auto-installing missing dependency: python-apt
23:04:36 fatal: [localhost]: FAILED! => {"changed": false, "cmd": "apt-get update", "msg": "E: Repository 'http://deb.debian.org/debian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable'\nE: Repository 'http://deb.debian.org/debian buster-updates InRelease' changed its 'Suite' value from 'stable-updates' to 'oldstable-updates'", "rc": 100, "stderr": "E: Repository 'http://deb.debian.org/debian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable'\nE: Repository 'http://deb.debian.org/debian buster-updates InRelease' changed its 'Suite' value from 'stable-updates' to 'oldstable-updates'\n", "stderr_lines": ["E: Repository 'http://deb.debian.org/debian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable'", "E: Repository 'http://deb.debian.org/debian buster-updates InRelease' changed its 'Suite' value from 'stable-updates' to 'oldstable-updates'"], "stdout": "Get:1 http://deb.debian.org/debian buster InRelease [122 kB]\nGet:2 http://deb.debian.org/debian buster-updates InRelease [56.6 kB]\nGet:3 http://deb.debian.org/debian buster-backports InRelease [51.4 kB]\nGet:4 http://security.debian.org/ buster/updates InRelease [34.8 kB]\nGet:5 http://deb.debian.org/debian buster-backports/main Sources [456 kB]\nGet:6 http://deb.debian.org/debian buster-backports/main arm64 Packages [482 kB]\nGet:7 http://deb.debian.org/debian buster-backports/main Translation-en [411 kB]\nGet:8 http://security.debian.org/ buster/updates/main Sources [285 kB]\nGet:9 http://security.debian.org/ buster/updates/main arm64 Packages [403 kB]\nGet:10 http://security.debian.org/ buster/updates/main Translation-en [223 kB]\nReading package lists...\n", "stdout_lines": ["Get:1 http://deb.debian.org/debian buster InRelease [122 kB]", "Get:2 http://deb.debian.org/debian buster-updates InRelease [56.6 kB]", "Get:3 http://deb.debian.org/debian buster-backports InRelease [51.4 kB]", "Get:4 http://security.debian.org/ buster/updates InRelease [34.8 kB]", "Get:5 http://deb.debian.org/debian buster-backports/main Sources [456 kB]", "Get:6 http://deb.debian.org/debian buster-backports/main arm64 Packages [482 kB]", "Get:7 http://deb.debian.org/debian buster-backports/main Translation-en [411 kB]", "Get:8 http://security.debian.org/ buster/updates/main Sources [285 kB]", "Get:9 http://security.debian.org/ buster/updates/main arm64 Packages [403 kB]", "Get:10 http://security.debian.org/ buster/updates/main Translation-en [223 kB]", "Reading package lists..."]}

s390x ubuntu18
23:06:25 TASK [Common : Run apt-get upgrade] ********************************************
...
 "Error: Unsupported setup: Directory '/boot' is located on a multi-target device-mapper device",

riscv deb11
23:08:13 TASK [Common : Allow https apt sources] ****************************************
23:08:34 fatal: [localhost]: FAILED! => {"cache_update_time":<PHONE_NUMBER>, "cache_updated": false, "changed": false, "msg": "'/usr/bin/apt-get -y -o \"Dpkg::Options::=--force-confdef\" -o \"Dpkg::Options::=--force-confold\"      install 'apt-transport-https'' failed: E: Failed to fetch http://deb.debian.org/debian-ports/pool/main/a/apt/apt-transport-https_2.1.10_all.deb  404  Not Found [IP: <IP_ADDRESS> 80]\nE: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?\n

arm32 deb8
Failed to install the following package for what looked to be a dependency reason:
failed: [localhost] (item=flex)
failed: [localhost] (item=g++)
failed: [localhost] (item=gcc)
failed: [localhost] (item=gettext)
failed: [localhost] (item=libexpat1-dev)
failed: [localhost] (item=libcups2-dev)
failed: [localhost] (item=libfreetype6-dev)
failed: [localhost] (item=libfontconfig1-dev)
failed: [localhost] (item=libgmp3-dev)
failed: [localhost] (item=libmpfr-dev)
failed: [localhost] (item=systemtap-sdt-dev)

Using QEMU playbook check in github workflows. It can do all but riscv

As of 19/12/22 the failing builds are
aarch64 deb10

23:03:53 TASK [Common : Allow https apt sources] ****************************************
23:04:36 [WARNING]: Updating cache and auto-installing missing dependency: python-apt
23:04:36 fatal: [localhost]: FAILED! => {"changed": false, "cmd": "apt-get update", "msg": "E: Repository http://deb.debian.org/debian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable'

That one will be from Debian 10 going out of support, so we should either have something in the playbooks to update the apt repo reference. See https://wiki.debian.org/DebianOldStable for background.

s390x ubuntu18

23:06:25 TASK [Common : Run apt-get upgrade] ********************************************
...
 "Error: Unsupported setup: Directory '/boot' is located on a multi-target device-mapper device",

@Willsparker Have you hit this one before?

riscv deb11

23:08:13 TASK [Common : Allow https apt sources] ****************************************
23:08:34 fatal: [localhost]: FAILED! => {"cache_update_time":<PHONE_NUMBER>, "cache_updated": false, "changed": false, "msg": "'/usr/bin/apt-get -y -o \"Dpkg::Options::=--force-confdef\" -o \"Dpkg::Options::=--force-confold\"      install 'apt-transport-https'' failed: E: Failed to fetch http://deb.debian.org/debian-ports/pool/main/a/apt/apt-transport-https_2.1.10_all.deb  404  Not Found [IP: <IP_ADDRESS> 80]

That's slightly odd and suggests that apt-get update has not been able to complete successfully since the directory mentioned there does have version 2.5.5 of the package in place.

arm32 deb8 Failed to install the following package for what looked to be a dependency reason:
failed: [localhost] (item=flex)
failed: [localhost] (item=g++)

May just be because Debian8 is ancient (although it might be interesting to see if we can point directly at the correct repo from archive.debian.org). However we should probably check what the latest Raspbian image is and go with that (and possibly add a recent Ubuntu since that is become more common on the platform)


Looking for a maintainer?

@olahol I'm using this package in a project I'm working and would gladly help to maintain it. I have experience maintaining a number of small packages and have also worked on larger OSS projects like webpack (I lead the rebuild of their latest docs site for a while). Anyway, lmk if you're interested and I can get started on the open issues and pull requests.

@olahol, please transfer this package to someone. Looks great and helpful. At least merge pull requests to update dataset. 🙏

@olahol I'd be willing to take ownership of this as well. Would also update it to be used with import, TypeScript, and support node.


Intermittent failure in Twitter OAuth

Reported here, occasional HTTP 503 errors on proporti.onl during Twitter auth flow:
https://twitter.com/AidanBudd/status/969217821174583299
The application logs:
2018-03-01 14:28:47,504: [2018-03-01 14:28:47,495] ERROR in app: Exception on /authorized [GET]
2018-03-01 14:28:47,504: Traceback (most recent call last):
2018-03-01 14:28:47,505:   File "/home/emptysquare/my-venv/local/lib/python2.7/site-packages/flask/app.py", line 1988, in wsgi_app
2018-03-01 14:28:47,505:     response = self.full_dispatch_request()
2018-03-01 14:28:47,505:   File "/home/emptysquare/my-venv/local/lib/python2.7/site-packages/flask/app.py", line 1641, in full_dispatch_request
2018-03-01 14:28:47,505:     rv = self.handle_user_exception(e)
2018-03-01 14:28:47,505:   File "/home/emptysquare/my-venv/local/lib/python2.7/site-packages/flask/app.py", line 1544, in handle_user_exception
2018-03-01 14:28:47,506:     reraise(exc_type, exc_value, tb)
2018-03-01 14:28:47,506:   File "/home/emptysquare/my-venv/local/lib/python2.7/site-packages/flask/app.py", line 1639, in full_dispatch_request
2018-03-01 14:28:47,506:     rv = self.dispatch_request()
2018-03-01 14:28:47,506:   File "/home/emptysquare/my-venv/local/lib/python2.7/site-packages/flask/app.py", line 1625, in dispatch_request
2018-03-01 14:28:47,506:     return self.view_functions[rule.endpoint](**req.view_args)
2018-03-01 14:28:47,506:   File "/home/emptysquare/my-venv/local/lib/python2.7/site-packages/flask_oauth.py", line 427, in decorated
2018-03-01 14:28:47,506:     data = self.handle_oauth1_response()
2018-03-01 14:28:47,507:   File "/home/emptysquare/my-venv/local/lib/python2.7/site-packages/flask_oauth.py", line 379, in handle_oauth1_response
2018-03-01 14:28:47,507:     type='invalid_response', data=data)
2018-03-01 14:28:47,507: OAuthException: Invalid response from twitter

The original reporter is the only Twitter user who seems to trigger this bug. It must be related to this log message I just noticed:

/home/emptysquare/my-venv/local/lib/python2.7/site-packages/werkzeug/wrappers.py:1116: UserWarning: The "session" cookie is too large: the value was 5010 bytes but the header required 26 extra bytes. The final size was 5036 bytes but the limit is 4093 bytes. Browsers may silently ignore cookies larger than this.

Running the server locally doesn't trigger the bug, but in the context of PythonAnywhere's stack it must result in a corrupt cookie, or perhaps a request that's denied before it even reaches my application.
Only the a Twitter user's "lists" can cause unbounded data to be stored in the cookie. Try to store less info about each list to keep the cookie shorter.


[Feat]: Want to add contributor page

Description
"I would like the Contributor page to showcase individual profiles with specific sections for their contributions, bio, and social links. It could also include filters to categorize by role or type of contribution."
Plz assign this task to me @mdazfar2
Screenshots
No response
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I'm a GSSoC'24-Extd contributor
[X] I'm a Hacktoberfest'24 contributor
[X] I am willing to work on this issue (optional)

Hello @sanikamandale17, this is a very good feature, but according to our website, it will not look good. Try to find any other bugs or features, which I am happy to assign to you. Thank you!

Sanika, I need to reach a total of 128 stars to get the Starstruck x2 badge achievement on my GitHub. Can you please help by Star our repository? ⭐


Fail CI on test failure GH Actions

Issue is with our configuration on error, as with other reporter the Github Actions CI throws an Exit Code 1.

This was fixed with last PR merged, where we added also jest configuration for unit tests. The issue was we were not throwing any error on the onError function inside the custom reporter, therefore the CI was successful even when tests failed.


Simple pip

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@7fcd9f3). Click here to learn what that means.
The diff coverage is n/a.

@@          Coverage Diff           @@
##             main      #2   +/-   ##
======================================
  Coverage        ?   0.00%
======================================
  Files           ?       4
  Lines           ?      18
  Branches        ?       0
======================================
  Hits            ?       0
  Misses          ?      18
  Partials        ?       0

Continue to review full report at Codecov.

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


[opbot] check screener on refund

Have opbot check screener on refund.
Requires:

Add sender to GetQuoteRequestByTxHash return, do this in seperate PR
use screener-client to check address and return an error in slack if address is blacklisted

#3045 for step 1

#3076


Change in the command

File: get-started/05_persisting_data.md
Should be: docker run -d ubuntu bash -c "shuf -i 1-10000 -n 1 -o data.txt && tail -f /dev/null" instead of
docker run -d ubuntu bash -c "shuf -i 1-10000 -n 1 -o /data.txt && tail -f /dev/null"
Change "/data.txt" to "data.txt"

Hi @bwadjass, thanks for sharing the issue. Can you help provide more details about why it is an issue?

@craig-osterhout he has mentioned to update the command. I believe that's what the issue is.

Thank you. I was trying to understand why it must be updated.
Both commands appear to work and it looks like it's just a case of relative path vs absolute. Without knowing why one is more preferred, there appears to be no reason to change.
Closing as stale. If there's still and issue, please help provide details on why it is necessary to change.


Fix clippy issues.

It looks like some new checks/improvements are made of this variety:

Use y.clone_into(x) instead of x = y.to_owned()
Don't borrow unless you need to.
Use character literals instead of string literals of size 1

Another quick note: I disabled some clone vs. to_owned checks in the comment filter, as we would need a mutable-borrow version of trim for no great reason.  We COULD create such a function, but I think the current performance hint is minimal for codegen and we can address that in the future.


GPS Items

What if there are GPS5 and GPS9 coordinates in the GPMF? Do you add them all together ?

No, the code uses the GPS9 items if they exist, or the GPS5 items if there are no GPS9 items. It's always one or the other. In the testing I did, if both existed, it looked like the GPS5 items were duplicates of the GPS9 items, and the GPS9 items are supposed to be more accurate.
On a related note, there was a bug in 1.0.1 that prevented the GPS5 items from being used at all. That's fixed in 1.0.2.


Feat: Transformative flavour

Changes made, needs review.
If merged, plugin version will go to 2.0.0, as it also changes the name of the flavoring interface.
Fix #8

This does not fix #8. This PR would need to extract the return type of ctx.reply and use it in ctx.replyWithEmoji.

Major version change will not be required anymore.

Note that you're admin in the repo, there's no need to open pull requests from the fork. You can just open them from other branches in the same repo :)

This still does not solve the issue.
The aim is to make the following code compile:
import { Bot } from "https://deno.land/x/grammy/mod.ts";
import {
    hydrate,
    HydrateFlavor,
} from "https://deno.land/x/grammy_hydrate/mod.ts";

type MyContext = EmojiFlavor<HydrateFlavor<Context>>;

const bot = new Bot<MyContext>("");

bot.use(hydrate(), emojiParser(), async (ctx) => {
    const first = await ctx.reply("Ehh");
    await first.delete();
    const second = await ctx.replyWithEmoji`Hi! ${"robot"}`;
    await second.delete();
});

However, I cannot get it to work myself. It seems like ReturnType somehow swallows the changes that the inner transformative context flavour is performing to ctx.reply. Hence, the emoji flavour does not pick this up so it cannot provide the same type signature as ctx.reply has.
I do not see how this can be fixed. Feel free to investigate. Perhaps the hydrate plugin needs to be adjusted, too, who knows.

It doesn't appear to be just ReturnType, but rather a behavior of Typescript, itself. It seems like function type intersections are essentially treated as overloads, and Typescript will simply pick one of them for the return value type (without much consistency).
Typescript Playground

Note that you're admin in the repo, there's no need to open pull requests from the fork. You can just open them from other branches in the same repo :)

I do it on impulse, I'm still learning to use git 😅

It seems like function type intersections are essentially treated as overloads

This is correct, it makes a lot of sense that this is the root cause of the issue.
I'm still unsure how to proceed from here.

@andrrms @KnorpelSenf Please take a look at https://github.com/grammyjs/hydrate/pull/1/files if it may be a potential workaround.

@andrrms can you please check out https://github.com/grammyjs/hydrate/pull/1 and confirm that everything works for you?


Update MERCHANT_INTEGRATION.md

There was a diff in the original SPL code that may be confusing for people who just want to copy the snippet and test out the SPL token transfer. I cleaned it up so it reads properly in JS.

@cogoo would you review this?

Thanks everyone! 👍🏿


Use interface instead of class to declare service arguments

This allows us to overwrite the class if necessary.

Failing Scrutinizer appears to be unrelated.


Easter eggs

The website needs some funny easter eggs 🥚

This sounds like fun!! Do you have anything in mind?

@JavaScriptErika anything goes :) some have a image spin after 10 clicks some have ascii in the html. Maybe console.log something :)


Ktor: type safe routing

[resolves #170]
Boo! 🎃

moved top-level routing { } block to app() - Application.userRoutes becomes Routes.userRoutes
code comments were erroneously prefixed with /api, though the API specification points to /api - but fixing this is for another PR
(out-of-scope) it probably makes sense to extract models out of users.kt at some point, a bigger route handler might become claustrophobic

All in all, Ktor type-safe routing feels good, albeit a bit cumbersome with the annotations and especially having to declare the parent of a sub-route. I'd also love to optionally map the body in the resource definition somehow, before it hits the route handler and receive it in the lambda, like with query parameters - but that might get too complicated/specific. And then to tie that in with the validation plugin and so on.
Happy Hacktoberfest!

Yeah, you can make a ticket about that and assign it to me 👍


Ireland - Beta iOS display issue

Beta tester on iOS in Ireland reports an issue with species name display in count mode - see attachment.

iPhone 7 Software Version 13.5.1


[DEP0047] DeprecationWarning Fix

Fix [DEP0047] DeprecationWarning: The util.isDate API is deprecated.  Please use arg instanceof Date instead.

Hope this can get added soon. Thanks.

Sorry, saw #20 before this one, but this is fixed now!
Released as 🚢 0.2.12 / 2024-11-20

Thanks for the update.


Rule that Identifies Chrome Profile?

Is there a way to identify what profile a Chrome window is using?
This seems to identify chrome windows:
yabai -m rule --add app="^Google Chrome$" space=2
But now I want to have different Chrome profile windows to go to different spaces.
Eg.
yabai -m rule --add app="^Google Chrome$" <work profile window> space=2
yabai -m rule --add app="^Google Chrome$" <personal profile window> space=3

On macOS, applications are "bundles" of all information required to run it, which you can freely modify. Additionally, you can use AppleScript to do all kinds of things and save the script as an application. Together or separate, these can be used to create two different applications with unique names that you can identify in Yabai. There are several gotchas and "wrong" ways of implementing this, but this post should provide you with enough of a starting point and multiple solutions: https://apple.stackexchange.com/questions/389529/use-apple-script-to-open-chrome-with-specific-profile
Good luck! If you get it working report back for others to use too.

not sure if you fixed this already but i just made this work by using "Window --> Name Window" from the Chrome menu.

not sure if you fixed this already but i just made this work by using "Window --> Name Window" from the Chrome menu.

Can elaborate more how you use it? Thanks

When you open chrome, there is some menu in top bar, and that includes Window --> Name Window like he said

I get that, but the name is not persistent, after you close window. Or do i miss something? :)


Style Bug When Overlaps is False and Outline is Used

When I set "overlaps" to false on a vector source where the features should have different styles, the correct styles are not used. It only seems to happen when "overlaps" is false and my polygons have a stroke style.
Example: https://jsfiddle.net/x9xjdzz9/g7avmh15/

To add more documentation to the bug, it happens when the strokes are the same color.

Thanks for the bug report. I can confirm the issue.

Pull request: #6359


Fix indent issue

Addresses #1546
Describe the solution you have implemented
Moved indent method to console helpers instead on String patch.

Nice quick work!
Can I suggest we just stop extending String at all and make this a stand-alone helper function somewhere? i.e. delete that whole core_ext directory

i.e.
def indent(string, padding)
  ...
end

Yeah, this is my plan :) just wanted to open a draft before 🛌

Fabulous!

Sorry for giving you feedback before you asked for it 😊

Sorry for giving you feedback before you asked for it 😊

no worries :) I think the basic implementation is done, now it is about fixing many tests, because indentation was off there 🙈

I'm not sure I like the indentation of tags that I had to fix, but I do not have a hard opinion on it either.

The current rpsec already covers the changes with tests.

but I still added a couple of basic tests :)

Great PR 🤩
Is it ready for review? Or do you still have some improvements to do?

it is done from my point of view

Ok.
Could you please update the changelog?

Done, there is some infra issue with the tests

Great, thank you :D
We'll wait for CircleCI to be fixed before approving and merging it 👍

LGTM.
I'll merge this later this week to wait for other potential reviews

for arguments sake, it would be good to fix the method arg in this / the one below from indent to say indent_amount

@luke-hill do you suggest the following?
def indent(string, indent_amount)

Myself I have no issue with the argument being named "padding".

Sorry the method "invocation". It's a bit odd to see indent(indent)

hey, can it be merged, the indent(indent) thing is what was there before as well and not in the scope of the fix. But if it is really necessary I could take a look in a couple of weeks again 🌴

If you're busy @JoeSSS I'm happy to make the change as I'm working in here now.

sure, added you to my fork. I will be on vacation and the plan is not to take the laptop with me :D

thanks for the support!

Hi @JoeSSS,
Thanks for your making your first contribution to Cucumber, and welcome to the Cucumber committers team! You can now push directly to this repo and all other repos under the cucumber organization! 🍾
In return for this generous offer we hope you will:

✅ Continue to use branches and pull requests. When someone on the core team approves a pull request (yours or someone else's), you're welcome to merge it yourself.
💚 Commit to setting a good example by following and upholding our code of conduct in your interactions with other collaborators and users.
💬 Join the community Slack channel to meet the rest of the team and make yourself at home.
ℹ Don't feel obliged to help, just do what you can if you have the time and the energy.
🙋 Ask if you need anything. We're looking for feedback about how to make the project more welcoming, so please tell us!

On behalf of the Cucumber core team,
Aslak Hellesøy
Creator of Cucumber

Awesome, thanks @JoeSSS!
If you're interested in helping us maintain Cucumber, you can find us in the #committers channel in the https://cucumber.io/community#slack

@JoeSSS Hep! Nice to clean up the String class!


make the @sourcegraph/cody-cli package publishable

Also set up a GitHub Action to publish this for the tag cli-v*.
Test plan
n/a; CLI is experimental

Fine to stamp since the CLI package is experimental.


Screen frozen

Hi, there:
I am doing a chat App, I use a ListView as a container ,
 ListView.builder(
              //  controller: _scrollController,
                shrinkWrap: true,
               // physics: ClampingScrollPhysics(),
                itemBuilder: (context, index) {
return chat_widget(index);
}

inside the listview, it will be text message, picture, emoji, avatar. between chat, some time if scrolling the listview (moving up and down to check the message), the screen will frozen
is that a way to capture something ? nothing show at Android Studio's Logcat window .
$ flutter doctor -v
[✓] Flutter (Channel stable, v1.2.1, on Mac OS X 10.14.4 18E226, locale en-CA)
    • Flutter version 1.2.1 at /Users/xxxxx/Desktop/development/flutter
    • Framework revision 8661d8aecd (10 weeks ago), 2019-02-14 19:19:53 -0800
    • Engine revision 3757390fa4
    • Dart version 2.1.2 (build 2.1.2-dev.0.0 0a7dcf17eb)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/xxxx/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)
    • All Android licenses accepted.

[!] iOS toolchain - develop for iOS devices (Xcode 10.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.2.1, Build version 10E1001
    ✗ Verify that all connected devices have been paired with this computer in Xcode.
      If all devices have been paired, libimobiledevice and ideviceinstaller may require updating.
      To update with Brew, run:
        brew update
        brew uninstall --ignore-dependencies libimobiledevice
        brew uninstall --ignore-dependencies usbmuxd
        brew install --HEAD usbmuxd
        brew unlink usbmuxd
        brew link usbmuxd
        brew install --HEAD libimobiledevice
        brew install ideviceinstaller
    • ios-deploy 1.9.4
    • CocoaPods version 1.6.1

[✓] Android Studio (version 3.4)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 34.0.2
    • Dart plugin version 183.5901
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)

[✓] Connected device (2 available)
    • Moto E 4 • ZY224VD7WW                           • android-arm • Android 7.1.1 (API 25)
    • iPhone 6 • 24045FE1-7019-452C-8633-D7C0F098C2DF • ios         • com.apple.CoreSimulator.SimRuntime.iOS-12-2 (simulator)

@dragon2934 do you still experience the issue?

are there specific actions to reproduce it? does that happen often enough to be able to catch it while running it with --verbose flag and paste the output here?

you can create a chat UI (ListView,) , then keep insert all kinds of
widgets (such as Text, Container, Image.network, Icons, ..), then if you
have more than 100 records, then scrolling up or down, it will frozen
On Thu, Oct 17, 2019 at 5:34 AM Stanislav Bondarenko <
<EMAIL_ADDRESS>wrote:

are there specific actions to reproduce it? does that happen often enough
to be able to catch it while running it with --verbose flag and paste the
output here?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/31426?email_source=notifications&email_token=AE2CZ5KLKWVAXXFTHK34AA3QPAWSZA5CNFSM4HHRHBTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBPOP5Y#issuecomment-543090679,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE2CZ5PYJHNIAX2WZRU3VR3QPAWSZANCNFSM4HHRHBTA
.

I created a chat app UI and added a literally infinite number of items (using ListView.builder, returning a widget for every index) and it didn't freeze.
Please provide the code that shows the problem. Thanks.

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact descriptions what happens, logs and the output of 'flutter doctor -v'  please.
All system setups can be slightly different so it's always better to open new issues and reference related issues.


Support draft-21

This just changes the version number and adds support for ticket nonces, which should be enough.
However, draft-20 support never really got interop tested, so let's do some testing with other stacks before merging.

Merging based on bidirectional interop with the -21 implementation in OpenSSL master.


Datetime localization for Azerbaijani language

Added translation for absent language names and datetime strings (moved to Transifex),
Added datetime format for Azerbaijani locale

Hi, thanks for submitting this.  Translations are handled at Transifex. See https://docs.djangoproject.com/en/dev/internals/contributing/localizing/#translations. This PR should only contain the Python files. Do you have a colleague who can +1 your work in formats.py?

@jafarovr, @seferov, @samadli - Can you guys check formats.py file? Used same settings as in ubuntu and windows os locale settings for Azerbaijani.

@timgraham @EmiXLabs +1

@timgraham @EmiXLabs +1

merged in dda2a3cf4cc29d01de180f66d19441f300732e52, thanks!


How do I use it in c#?

Can anyone please provide some examples in c# .net?

I've added a section on usage on the bottom of main README


Weird event nesting

There is some strange nesting happening for one of of the Meetup events
It only happens in production (when deployed to Netlify) but not locally.
I've opened an issue with the Gatsby theme maker https://github.com/matthieuauger/gatsby-theme-meetup/issues/6

Hey there! Thanks for reaching out :)
It seems be caused by the slice on the meetup description here https://github.com/M0nica/React-Ladies/blob/master/src/%40matthieuauger/gatsby-theme-meetup/components/Meetup/Meetup.component.js#L54
Which cuts the link of the meetup and results in weird HTML markup

If you want a really quick way to remove the display bug, you could change the slice number.
Now we could figure a way to fix it right directly in the theme. The use-case of limiting the description is necessary and I tried some CSS options to hide the overflow but sometimes the cut is not in the right place.

I'll try it again tomorrow, if you have some ideas on the topic I can try them as well 💡

Oo interesting. Thanks for looking into this for me. Yeah, I found displaying the full descriptions to be a bit overwhelming for the site
This Shave package for truncating text looks interesting but I’m not sure if it handles markup well. https://github.com/dollarshaveclub/shave although, I think the most complicated markup I’ll have in a Meetup event description is a url. I’ll try to think of some more flexible solutions.

This is related to the old site and therefore is no longer relevant.


U/cnsetzer/paris hack update notebooks

This pull request is to merge the changes made during and shortly after the Paris Hack Day to update some of the DC2 tutorial notebooks with new catalogs from Run2.1i. There are the majority of notebooks which cannot yet be updated as they need the truth catalogs or someone with DC2/NERSC expertise much greater than myself. This is all documented in issue #110 .
It was also be very much appreciated if someone could also verify that the notebooks I have changed run, and do what they are intended. To my knowledge they do, but of course for tutorial purposes it would be very good to have a confirmation from someone more familiar with DC2.

Thanks for the update, @cnsetzer. This looks great. I'll ping @EiffL and @fjaviersanchez since they are the original authors of these three notebooks to see if they can help with updating some the old text.

hi @timeifler and @fjaviersanchez, any thoughts on this PR?


Nothing shows under the PostgreSQL server after entering server credentials for it on another machine

OS: Win10
Build Version: 20231006.1
Regression: Previous Release
Repro Steps:

Create one PostgreSQL server in VS Code.
Expand the above PostgreSQL server on another machine -> Enter server credentials with the right username and password.
Check whether the "Configure firewall to connect to..." shows under the PostgreSQL server or not.

Expect:
The "Configure firewall to connect to..." shows under the PostgreSQL server.

Actual:
Nothing shows under the PostgreSQL server and a notification pops up.

More Info:
This issue does not reproduce on the current released extension v0.19.4.

This might be an intentional change. I noticed that it is possible to get the wrong IP address when the extension code attempts to add the firewall rule. Could you try going to Azure Portal and configure the firewall rule there and then try accessing the database. If that works, then we don't need to worry about this issue.


Use cross-compilation instead

This will significantly increase the build speed for aarch64/ppc64le. I've made a few attempts to understand how it works

https://github.com/conda-forge/nccl-feedstock/pull/88 (pure C++ & CUDA)
https://github.com/conda-forge/cupy-feedstock/pull/197 (python with C++ & CUDA extension modules)

I suspect we might have to revive cuquantum-python-feedstock. Cross-compiling requires that the build-platform packages
exist (ex: to build cuquantum-python for aarch64 we need custatevec/cutensornet for linux-64), but in the current infra this is not possible ( custatevec/cutensornet for linux-64 are built in a separate pipeline).

@conda-forge-admin, please rerender


GA release of @google-cloud/channel

Package name: @google-cloud/channel
Current release: ga
Proposed release: GA
Instructions
Check the lists below, adding tests / documentation as required. Once all the "required" boxes are ticked, please create a release and close this issue.
Required

[ ] 28 days elapsed since last beta release with new API surface
[ ] Server API is GA
[ ] Package API is stable, and we can commit to backward compatibility
[ ] All dependencies are GA

Optional

[ ] Most common / important scenarios have descriptive samples
[ ] Public manual methods have at least one usage sample each (excluding overloads)
[ ] Per-API README includes a full description of the API
[ ] Per-API README contains at least one “getting started” sample using the most common API scenario
[ ] Manual code has been reviewed by API producer
[ ] Manual code has been reviewed by a DPE responsible for samples
[ ] 'Client Libraries' page is added to the product documentation in 'APIs & Reference' section of the product's documentation on Cloud Site

This issue will fall OoSLO soon.

This was initially released as GA due to a bug in the script that generates these libraries, so there is nothing to be done, and the bug has been addressed.


Output of standalone build script fails to run

the output of  scripts/standalone ./package.sh works if extracted to within the dashboard folder structure, but not if outsideError: Cannot find module 'http-proxy-middleware'
Require stack:
- /home/richard/dev/deleteme/index.js

Obvious issue, not obvious solution. I've tried

manually updating the require to use a file path to the local node_modules (this unravels quickly - there are similar issues for some of the dependencies)
building with different versions of node
using NODE_PATH pointing to the local node_modules
using a symlink from local node_modules to point to a default node_modules location like $HOME/.node_modules
clicking my heels together three times and saying there's no place like node_modules

Couple of useful links

https://nodejs.org/docs/v16.14.0/api/modules.html#loading-from-the-global-folders
https://nodejs.org/docs/v16.14.0/api/modules.html#all-together

@richard-cox Think this is fixed now?

Fixed via https://github.com/rancher/dashboard/pull/6634


Uncaught Exception: EBUSY: resource busy or locked, open 'C:\Users\Jamie\AppData\Roaming\Google Play Music Desktop Playe

An uncaught exception was reported.
Info:
OS: win32
Arch: ia32
GPMDP Version: 3.3.0
Time: Wed Jul 06 2016 18:30:06 GMT-0700 (Pacific Daylight Time)
Error:
EBUSY: resource busy or locked, open 'C:\Users\Jamie\AppData\Roaming\Google Play Music Desktop Playe
Error: EBUSY: resource busy or locked, open 'C:\Users\Jamie\AppData\Roaming\Google Play Music Desktop Player\json_store\playback.json'
    at Error (native)
    at Object.fs.openSync (fs.js:634:18)
    at Object.module.(anonymous function) [as openSync] (ELECTRON_ASAR.js:158:20)
    at Object.fs.writeFileSync (fs.js:1337:33)
    at t.value (C:\Users\Jamie\AppData\Local\GPMDP_3\app-3.3.0\resources\app\build\main\utils\PlaybackAPI.js:9:2417)
    at t.value (C:\Users\Jamie\AppData\Local\GPMDP_3\app-3.3.0\resources\app\build\main\utils\PlaybackAPI.js:9:4016)
    at EventEmitter.<anonymous> (C:\Users\Jamie\AppData\Local\GPMDP_3\app-3.3.0\resources\app\build\main\utils\PlaybackAPI.js:9:1362)
    at emitTwo (events.js:106:13)
    at EventEmitter.emit (events.js:191:7)
    at EventEmitter.<anonymous> (C:\Users\Jamie\AppData\Local\GPMDP_3\app-3.3.0\resources\electron.asar\browser\api\web-contents.js:156:13)

This issue was created automatically inside the uncaughtException handler

Closing this automatically reported issue as a duplicate of #1260


Recommanded modules not installed

MBO module is installed
Go on Shipping > carriers
Install a recommanded module like mondial relay
You are redirected to installed modules tab instead of the configuration of the module & the module isn't installed
Now, click on "recommanded modules" in the header of the carriers' page
Install a recommanded module like mondial relay
You are redirected to installed modules tab instead of the configuration of the module & the module isn't installed

I thought it was a core issue ?

Yes, right !


Use cuda9 1 in c api packaging

Please use '--cuda_version' in build.py to choose between multiple installed CUDA installations.  I'm sure it works. I tested. And this is only needed for Windows.
On Linux, we have docker, in the docker image, it should only have one cuda.

Please use '--cuda_version' in build.py to choose between multiple installed CUDA installations.  I'm sure it works. I tested. And this is only needed for Windows.
On Linux, we have docker, in the docker image, it should only have one cuda.

did u mean I don't have to set up cuda_path and cudnn_path?
Either way the build is failing, and I have been trying different things... without success so far.
you may check the build log --
https://dev.azure.com/onnxruntime/onnxruntime/_build/results?buildId=9606


Its not scanning code 39 barcode types

The barcode scanner is not scanning code 39 barcode types. It is treating them as a different type and giving the result

Under the covers this library just uses http://zbar.sourceforge.net. Any incorrect barcode reading would be an issue with that library.


data is right ?

I tried to see if the code you created works.
but, could not untar jawiki link here
jawiki-20200601-pages-articles-multistream.xml.bz2
i did it
$ tar -jxvf ./jawiki-20200601-pages-articles-multistream.xml.bz2
error ocuer
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Archive contains ‘.afpbb.com/a’ where numeric off_t value expected
tar: Archive contains ‘9年7月10\346\227’ where numeric off_t value expected
tar: Archive contains ‘ー級\n|IMO\347’ where numeric off_t value expected
tar: Exiting with failure status due to previous errors

my env is colab notebook.
data is right? or broken?
really same procedure ?

Waiting for an answer. Thank you.

@syu-tan sorry for late response. You need to extract by using wikiextractor. Pls extract dataset following:  python extract_wiki_data.py

Sorry, late.
I see. Thank you, for your time.


Share /mnt/koji

In order to build packages, we need to create /mnt/koji with the right
structure and share it between the koji hub and builder.
(Building packages is needed for Flatpak testing, since the application packages get rebuilt with prefix=/app)

Thanks for all the PRs!


In this library, what is the "best" default encoding for Fulfillment.getEncodedPreimage and other byte-array data?

@adrianhopebailie @earizon @michielbdejong
This issue arises from thediscussion in #89.
Currently, Fulfillment.getEncodedPreimage produces output in Base64Url encoding. However, in ILP-over-HTTP, the encoding is specified as being Base64.
If we leave things alone, then anyone using the ILP-Testnet's ILP-over-HTTP functionality will have to re-encode from Base64Url to Base64 in order to pass fulfillment data.
Thus, we have (at least) three choices here:

Do nothing. Have any code that needs to interface with both ilp-over-http and this crypto-conditions library just do the double-conversion. This may not be a bad choice because 1.) ilp-over-http is deprecated in favor of ILPv4-over-http, and 2) There's a case to be made that this encoding should be Base64Url, so that anyone putting this data into a URL won't have to double-encode it.
Change the TestNet code to use Base64Url. I will defer to @michielbdejong on this, but I think this is a non-starter because the testnet has certain deprecation guarantees that would make this impractical.
Change this library to use Base64 encoding in all places. Overall, this is not a bad choice, but would force anyone putting crypto-condition primitives into URLs to possibly have to re-encode them. This is probably more likely than any of the use-cases from 1 or 2 above.

I would be curious to hear pros/cons for picking either Base64 vs. Base64Url as a general choice. Thoughts anyone?

Maybe that can be selected in a Fulfillment builder parameter. By now default to Base64, and change to Base64Url once the testnet is updated. If Base64 is finally deprecated in favor of Base64Url then just drop/deprecate/ignore the builder setting.

Closing this since CryptoConditions have moved to https://github.com/ripple/crypto-conditions, and for ILP-over-HTTP the suggested crypto-condition should be the hashlock packaged in Quilt.


chore(main): release frontend 0.0.3

:robot: I have created a release beep boop
0.0.3 (2024-06-23)
Bug Fixes

docker (9d49010)
docker (219c6fc)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

frontend-v0.0.3
:sunflower:


Then ran bin/composer.phar install --no-dev and bin/grav clear --all
I'm getting the following error:
Whoops \ Exception \ ErrorException (E_ERROR)
Class Grav\Common\Twig\TwigExtension contains 1 abstract method and must therefore be declared abstract or implement the remaining methods (Twig_ExtensionInterface::getName)

Hmmm.. Do you have the Twig PHP extension installed? What version of PHP are you running?

Got it working, just had to delete the composer.lock before I ran bin/composer.phar install --no-dev. This was probably screwed up from way back. Thanks for the help!


Sam361 update urdb api

Update to URDB Version 7
Some utilities like SCE have more than 500 rates, so API limit on number of returned rates prevents all rates. Implement Jay Huggins suggestion:

You can include the “offset” param in your calls, starting with 0, and increment it by the limit value and repeat the calls until you get < 500 results (wouldn’t hurt to explicitly include the limit of 500 for clarity), and page through all results, no matter how many there are.

Improve layout and messagingn in URDB Download window
Get metering / billing option if available
Correctly handle minimum charges: minmonthlycharge and annualmincharge replaced my mincharge and minchargeunits per https://openei.org/services/doc/rest/util_rates/?version=7.
Calculate fixed charge from fixedchargefirstmeter, fixedchargeeaaddl, and fixedchargeunits
For items SAM does not model, get as "unused" item:

fueladjustmentsmonthly $/kWh

demandwindow

coincidentrateschedule, coincidentratestructure, coincidentrateunit

demandratchetpercentage

demandreactivepowercharge

energyattrs

fixedattrs

is_default

servicetype

Add rate notes input for fixed and minimum charges in units that SAM does not handle.
The following items available from the URDB that SAM does not use are now better documented. We could add some of these in the future:

minchargeunits = $/day

fixedchargeunits = {$/day, $/year} (could convert these to $/month)

dgRules Net Billing Hourly vs Net Billing Instantaneous, for now assign either to Net Billing.

fueladjustmentsmonthly (monthly array of $/kWh rates)

coincident demand charges

demand ratchets

demand reactive power charge

demand units (applicability)

I merged Develop into this branch and then ran the test script just before making the pull request. I agree this will be a tricky merge given the UI and defaults changes -- I will test and be prepared for possible manual updates in Develop after the merge.
Note that invoke.cpp and webapis.conf will need to be updated in sam-private as well.

I'm having some trouble getting this working in the open source version. Is that because this now relies on private.h within SAM-private for the API key?

@brtietz Yes. To test any web service features, you have to temporarily copy the API keys from private.h in sam-private to sam and be careful not to commit private.h. Those keys should never have been committed to the open source version of private.h.

For future reference/testing, I used the "conditions" box and some JSON on this page to find those rates:

Thoughts on where to document this for future reference? This doc, perhaps? https://github.com/NREL/SAM-documentation/blob/master/Developer Tools and Instructions/URDB_Upload_Instructions.md

Thanks @brtietz. Review items addressed in e41dccd76.

Documentation for URDB downloads and uploads:
Added https://github.com/NREL/SAM-documentation/blob/master/Developer Tools and Instructions/urdb-download-urls-and-ui-notes-.md
Renamed https://github.com/NREL/SAM-documentation/blob/master/Developer Tools and Instructions/urdb-add-rate-instructions.md

Close #361


Fix state sync

Description
Fix state sync

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[ ] included the correct type prefix in the PR title
[ ] added ! to the type prefix if API or client breaking change
[ ] added appropriate labels to the PR
[ ] targeted the correct branch (see PR Targeting)
[ ] provided a link to the relevant issue or specification
[ ] added a changelog entry to CHANGELOG.md
[ ] included comments for documenting Go code
[ ] updated the relevant documentation or specification
[ ] reviewed "Files changed" and left comments if necessary
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed all author checklist items have been addressed
[ ] reviewed state machine logic
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

Codecov Report

Merging #1454 (1e12fd8) into main (421da96) will decrease coverage by 0.01%.
The diff coverage is 75.00%.

@@            Coverage Diff             @@
##             main    #1454      +/-   ##
==========================================
- Coverage   52.77%   52.75%   -0.02%
==========================================
  Files          71       71
  Lines        6759     6750       -9
==========================================
- Hits         3567     3561       -6
+ Misses       2922     2920       -2
+ Partials      270      269       -1

Impacted Files
Coverage Δ

app/upgradev3/migrations.go
78.26% <0.00%> (ø)

x/leverage/keeper/token.go
76.00% <ø> (+1.80%)
:arrow_up:

ante/ante.go
60.00% <100.00%> (+1.37%)
:arrow_up:

x/leverage/keeper/keeper.go
66.15% <100.00%> (+0.36%)
:arrow_up:


ci: Disable doc tests on Windows.

This is still confusing me. The first commit did not run properly. Then I added debug logging and it has completed. Very odd.


"SearchResult": should say "SearchResults":

A small issue in the documentation, instead of "SearchResult":, the schema actually contains ""SearchResults":.

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

ID: b1390bec-bae0-2fe7-a29c-a242584fd7b3
Version Independent ID: 27892ee4-2ec3-ea70-f747-80a9bc914fd7
Content: Webhook actions for log alerts in Azure alerts
Content Source: articles/azure-monitor/platform/alerts-log-webhook.md
Service: azure-monitor
Sub-service: alerts
GitHub Login: @msvijayn
Microsoft Alias: vinagara

@DuffLV Thank you for your comment . It would be great if you could provide us the link for the exact document which needs to be changed ?

@shashishailaj hi, terribly sorry, thought that clicking the issue on the page will add the link. It is this page: https://docs.microsoft.com/en-us/azure/azure-monitor/platform/alerts-log-webhook

@DuffLV Thank you for pointing this out and provindg the document link . We have initiated a change internally and it should be updated in the next release cycle within 24-48 hours. We will close this issue now.
Thank you.

@shashishailaj - have you verified if indeed webhook have payload as "searchResults"? If so, its a bug - it is should be "searchResult". Please don't arbitrarily update docs without informing authors or SMEs first.
Kindly rollback your doc changes done via #82059

@shashishailaj @DuffLV  - By the way, just tested the webhook from my test Log Analytics workspace - payload contains:

"SearchResult": {
"tables": [
{
"name": "PrimaryResult",
"columns": [ ...],
"rows": [ ... ],
]
},

@msvijayn @shashishailaj Hello, I am consuming the log alerts that have been configured with custom JSON payload:
{
"alertname":"#alertrulename",
"IncludeSearchResults":true
}
from a function app that parses the input and based on it, performs various manipulations. This function logs the output and it is as follows (this is the last run, logged at 2019-07-15 03:46:04.778 UTC):
The payload that was passed in: {
"alertname": "we-t-alert",
"IncludeSearchResults": true,
"SearchResults": {
"tables": [
{
"name": "PrimaryResult",
"columns": [
{
"name": "resource_runId_s",
"type": "string"
},
{
"name": "resource_workflowName_s",
"type": "string"
}
],
"rows": [
[
"08586384462126579839530072226CU13",
"we-t-la-xxxxxxxxxxxxxxxxxxxxxxxx"
]
]
}
],
"dataSources": [
{
"resourceId": "/subscriptions/7c7dd4cf-7f15-415c-xxxx-2a6cyyyyye762/resourcegroups/we-s-rsg-monitoring/providers/microsoft.operationalinsights/workspaces/somename",
"tables": [
"AzureDiagnostics"
]
}
]
}
}
The reason I raised this issue was because the code I wrote for the Function App did not work with "SearchResult"...

@msvijayn @shashishailaj Hello, I am consuming the log alerts that have been configured with custom JSON payload:
{
"alertname":"#alertrulename",
"IncludeSearchResults":true
}
from a function app that parses the input and based on it, performs various manipulations. This function logs the output and it is as follows (this is the last run, logged at 2019-07-15 03:46:04.778 UTC):
The payload that was passed in: {
"alertname": "we-t-alert",
"IncludeSearchResults": true,
"SearchResults": {
"tables": [
{
"name": "PrimaryResult",
"columns": [
{
"name": "resource_runId_s",
"type": "string"
},
{
"name": "resource_workflowName_s",
"type": "string"
}
],
"rows": [
[
"08586384462126579839530072226CU13",
"we-t-la-xxxxxxxxxxxxxxxxxxxxxxxx"
]
]
}
],
"dataSources": [
{
"resourceId": "/subscriptions/7c7dd4cf-7f15-415c-xxxx-2a6cyyyyye762/resourcegroups/we-s-rsg-monitoring/providers/microsoft.operationalinsights/workspaces/somename",
"tables": [
"AzureDiagnostics"
]
}
]
}
}
The reason I raised this issue was because the code I wrote for the Function App did not work with "SearchResult"...

@DuffLV - thanks for the clarification. Yes, for custom webhook the payload will be "SearchResults" - as indicated in the property enabled. This was an err on my part as doc author. But for the rest of the cases - the payload will be "SearchResult" only

@msvijayn, makes sense, thanks.

I want to poke at this. It appears it still doesn't isn't fixed after over a year of being closed.
Documentation needs to be clear since visibility into the WebHookData isn't always easy to interactively work with. So with improperly documented data the user experience becomes less than ideal.


Suggestion: invisible hitbox for mobile.

On mobile devices moving the sliders is difficult. An improvement would be to have an invisible ‘hitbox’ around the handles to improve the mobile user experience.

+1 :)

+1

Have you tried using invisible borders? That's how I usually increase the 'hitbox' of an element...
/* you can't just copy and paste this, its just an example */
.handle {
    border: 10px solid transparent;
}

Normally you'd need to fiddle with the markup a bit so it might not be possible with the default rangeslider template


Extract common reusable component for AppBar functionality in admin

Extract common reusable component for AppBar functionality in admin
Pass the needed title/actions/url params to that component

Screenshots:

Before
After