Expose run_jit to allow for custom behaviour in JIT flow

Hi, I'm making this PR primarily to let you know I'm working on a project that uses the JIT in a slightly weird way, I'm making a language that is JITted with Rust as an intermediate language, or at least for its parts that are linked to Rust crate dependencies.
To understand the JIT better, and to give myself a point to start thinking on what else I need I started by splitting out the JIT driver into smaller functions. I'm not sure if this is desirable, it just helped me understand it better.
My next step I've described in this thoughts:
I need some way to make the lazy jit state publicly accessible. It should only be accessible from the rustc thread. This is achieved by using the message channel to send requests to the rustc thread for the regular JIT flow. I need it to be publicly accessible so I can add new functions to the jit_module, and it has to be in the rustc_thread because I assume it
is thread_local for good reason.
I want to enable arbitrary code to invoke the JIT runtime to compile new functions, so I need to expose a way to send messages to the rustc thread.
So I should add a new message type that requests a function to be JIT to the UnsafeMessage enum. And then I should add a new message handler argument to the run_jit function that will be called when a new message is received.
I would love your thoughts on if I'm going in a right direction, and if you think this has a chance of getting merged or if I should just continue in my fork without worrying about upstreaming.
Thanks!

Hi, I'm making this PR primarily to let you know I'm working on a project that uses the JIT in a slightly weird way, I'm making a language that is JITted with Rust as an intermediate language, or at least for its parts that are linked to Rust crate dependencies.

Sounds cool! It may be hard to implement though as rustc isn't really designed for this.

I want to enable arbitrary code to invoke the JIT runtime to compile new functions, so I need to expose a way to send messages to the rustc thread.

If you want to define entirely new functions, you will have to create a new compiler session every time you add a new function. You could still reuse the same JitModule however to avoid having to codegen all functions again every time. https://github.com/rust-lang/rustc_codegen_cranelift/tree/wip_hot_code_swapping is an old branch with some experiments regarding hot code swapping, which is almost exactly what you need to compile new functions as opposed to lazily codegening on the first call as implemented in the lazy-jit mode.

To understand the JIT better, and to give myself a point to start thinking on what else I need I started by splitting out the JIT driver into smaller functions.

I would prefer if the entire JIT driver stays in src/driver/jit.rs (or if necessary submodules thereof) rather than scattering it around. That said, moving predefine_mono_items to src/base.rs makes sense to me, though please move it above CodegenedFunction. Feel free to make a separate PR for that change.
As for making more things public, I'm a bit split. While I do like the idea of your project, I fear that it will make refactorings to cg_clif that are beneficial to the core objective of cg_clif harder.

I want to enable arbitrary code to invoke the JIT runtime to compile new functions, so I need to expose a way to send messages to the rustc thread.

If you want to define entirely new functions, you will have to create a new compiler session every time you add a new function. You could still reuse the same JitModule however to avoid having to codegen all functions again every time. https://github.com/rust-lang/rustc_codegen_cranelift/tree/wip_hot_code_swapping is an old branch with some experiments regarding hot code swapping, which is almost exactly what you need to compile new functions as opposed to lazily codegening on the first call as implemented in the lazy-jit mode.

Thanks a lot, I didn't know this and would've spent a bunch of time figuring it out without this advice. I think it might mean I have to rethink the strategy a bit too, recreating the compiler session means running the full analysis pass again right? That sounds kind of expensive for something that's supposed to happen as a JIT/optimizing behavior. If it's really going to be expensive then I might take a more traditional approach and rely more on cranelift itself and less on rustc, at least for the parts that don't directly interact with Rust crates.

As for making more things public, I'm a bit split. While I do like the idea of your project, I fear that it will make refactorings to cg_clif that are beneficial to the core objective of cg_clif harder.

Totally understandable. My main objective would be to expose the JitModule and use it to define new functions. But if doing that isn't compatible with the way the rustc backend works, then probably I'm better off keeping my own module next to it. Maybe I could even rely more on some other dynamic language implementation built on cranelift.

recreating the compiler session means running the full analysis pass again right?

Assuming that you finished the previous compilation session cleanly (which the current jit mode doesn't do as it exits with the exit code of the jitted program before reaching that point), you will get a fair bit of reused work from incr comp, but it is still likely not cheap enough for your purposes.

If it's really going to be expensive then I might take a more traditional approach and rely more on cranelift itself and less on rustc, at least for the parts that don't directly interact with Rust crates.

That is what I would recommend doing.


LGTM.com - false positive - integer comparison - C++

The warning is as follow (for the three issues):
"Comparison between i of type quint16 and S_ARRAY_SIZE of wider type int."
The code clearly uses static_cast() to convert the int to an quint16, moreover the casted value is a constant equal to 256, which is clearly within range for a quint16.
https://lgtm.com/projects/g/metrodango/pip3line/snapshot/e046f7a81f8be6b4517eec1662feb1e17d8c3027/files/defaultplugins/baseplugins/substitution.cpp?sort=name&dir=ASC&mode=heatmap#xa2f279487e9ddbf4:1
https://lgtm.com/projects/g/metrodango/pip3line/snapshot/e046f7a81f8be6b4517eec1662feb1e17d8c3027/files/defaultplugins/baseplugins/substitution.cpp?sort=name&dir=ASC&mode=heatmap#x3bbe3a65dcd32d7c:1
https://lgtm.com/projects/g/metrodango/pip3line/snapshot/e046f7a81f8be6b4517eec1662feb1e17d8c3027/files/defaultplugins/baseplugins/substitution.cpp?sort=name&dir=ASC&mode=heatmap#x890936e77a698943:1

Thanks for the report. I'm quite surprised by this result! We'll look into this as soon as possible.

The fix has now been merged, and it should get deployed to lgtm.com in about three weeks from now.


Add test cases for default method of metric-api

Make sure that:

[ ] You have read the contribution guidelines.
[ ] You submit test cases (unit or integration tests) that back your changes.
[ ] Your local test passed mvn clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #726 (645dcd7) into master (cb193d9) will increase coverage by 0.21%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #726      +/-   ##
============================================
+ Coverage     59.14%   59.36%   +0.21%
- Complexity     1092     1104      +12
============================================
  Files           237      237
  Lines          5461     5461
  Branches        604      604
============================================
+ Hits           3230     3242      +12
+ Misses         1955     1943      -12
  Partials        276      276

Impacted Files
Coverage Δ
Complexity Δ

.../dromara/soul/metrics/api/GaugeMetricsTracker.java
100.00% <0.00%> (+100.00%)
1.00% <0.00%> (+1.00%)

...romara/soul/metrics/api/CounterMetricsTracker.java
100.00% <0.00%> (+100.00%)
1.00% <0.00%> (+1.00%)

...romara/soul/metrics/api/SummaryMetricsTracker.java
100.00% <0.00%> (+100.00%)
3.00% <0.00%> (+3.00%)

...mara/soul/metrics/api/HistogramMetricsTracker.java
100.00% <0.00%> (+100.00%)
3.00% <0.00%> (+3.00%)

...oul/metrics/api/SummaryMetricsTrackerDelegate.java
100.00% <0.00%> (+100.00%)
1.00% <0.00%> (+1.00%)

...l/metrics/api/HistogramMetricsTrackerDelegate.java
100.00% <0.00%> (+100.00%)
1.00% <0.00%> (+1.00%)

...metrics/api/NoneSummaryMetricsTrackerDelegate.java
100.00% <0.00%> (+100.00%)
1.00% <0.00%> (+1.00%)

...trics/api/NoneHistogramMetricsTrackerDelegate.java
100.00% <0.00%> (+100.00%)
1.00% <0.00%> (+1.00%)

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 cb193d9...645dcd7. Read the comment docs.


Birth certificate OCR Logic

Fixes #27
Added the logic for Birth Certificate OCR.

add the missing imports cv2 and numpy, rest is all good

Thanks for the review @garimayy23, I have addressed your comment.


feat: Automate using GitHub Actions

From what I understand, to update the repo, we still require to periodically run harwest codeforces or harwest atcoder. Instead, we could also offer the option of automatically setting up a GitHub Action that runs harwest and updates the repo daily. (using the cron directive in the .yml file)
A few ideas I have in mind:

During initialization, we detect if the repository url is a GitHub repo. If yes, we prompt whether they are okay with automatic updates by a GitHub Action.
If yes, we also add a .github/workflows/harwest.yml to the initial repo.
Currently, the configuration data is stored in lib/resources. This will have to be changed to the repo itself (maybe a .config folder).
If the user runs harwest codeforces or the like locally, we will pull first to receive the latest updated repo.

P.S. Great work with the project - really slick!

I think, first, we should implement as a secondary option of GitHub Action, later on we will add a feature which you discussed in 3rd Point.
Btw, what's your progress on it as of now, how can we start?

I was also curious about the progress of a Github Action.


About the VBR dataset

Hi, thanks for your impressive work. I see there is a run_vbr.yaml in config folder. But after I download the VBR dataset, there is no /ply folder, so I just want to ask, if you do some convert processing on vbr dataset, using like scripts/rosbag2ply.py? Additionally in each scene in vbr, there are several .bag, how do you combine them?
Thanks for your early reply.

Thanks for your interest in our work.
Indeed, one solution would be using scripts/rosbag2ply.py and a shell script to convert all the rosbags.
However, as you can imagine, this is a bit cumbersome.
Now the walkaround is to use the kiss-icp dataloader. The current version of PIN-SLAM supports to use the kiss-icp data loader. You may add (edit) the following contents to the config file:
setting:
  .....
  use_kiss_icp_dataloader: True
  pc_path: "./data/vbr/vbr_slam/spagna/spagna_test0" # or other sequences
  .....

For using the kiss-icp data loader, install kiss-icp by:
pip install kiss-icp

Then simply run:
python pin_slam.py ./config/lidar_slam/run_vbr.yaml rosbag /ouster/points

Currently, this rosbag dataloader does not support the loading of ground truth poses.
Therefore, you need to evaluate the results after the SLAM.
Here are some sample results that you can achieve with PIN-SLAM on the cool Rome dataset:


using TickInterpolator to interpolate rotation results in a stutter during the transition between -3.14 and 3.14

As the title says. Recording provided (note the rotation printed to the output)
https://github.com/user-attachments/assets/14d0de0f-d875-4a45-ad98-92d676351215

workaround possibly found: interpolate the whole transform, not the rotation and position

Hi @ruguysgoingtrickortreating,
This stems from the way rotation works - it's the amount of rotation per axis, in Euler angles. Using Euler angles to interpolate rotations doesn't work well, as can be seen on the video. The same thing happens in animation software as well, when you try to interpolate with Euler angles.
Interpolating the whole transform works well, or alternatively, you can interpolate quaternion, which will only affect the rotation. The quaternion field also represents the node's rotation, just like rotation, but as a Quaternion, which is much better suited to interpolation.

This is good info, would this fit in the docs?

Done.


Cannot login in MS Edge Browser

Trying to login in MS Edge, gives "login failed"

seems fixed atm.

Couldn't confirm, let's revisit this the next time it happens. We'll need details of MS Edge version etc.


Multi team setup

Before issuing a pull request, please see the contributing page.
Added projects/folders for the 3 Swerve FTC teams and TeamMentor.

Hi Malavika, I forked the FIRST repo yesterday.  They just updated the SDK today, so I updated the fork.  For testing, I copied the Tensorflow example program to each team folder, and test built for each team and TeamMentor onto an Android phone.  The program worked.  Afterwards, I deleted the program for each team's folder, but left it in TeamMentor in case anyone wants to build it.


Visual bugs

[ ] Fix line-height 26 px on other in nav bar.

Think this can be closed.  Was fixed in 67d53fe38f444b2d5deb1e98a4fb02b6b9e70f17 :+1:

nope it was not :-1:
See last item in list above.
Ive already created PR for it: https://github.com/Hellowlol/HTPC-Manager/pull/173


python37Packages.kaggle: 1.5.9 -> 1.5.10

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python37Packages.kaggle is: "Official API for https://www.kaggle.com, accessible using a command line tool implemented in Python 3"
meta.homepage for python37Packages.kaggle is: "https://github.com/Kaggle/kaggle-api"
meta.changelog for python37Packages.kaggle is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 1.5.10 with grep in /nix/store/v92y1br18jlxmyacdzypyrh3cqwywx1s-python3.7-kaggle-1.5.10

directory tree listing: https://gist.github.com/9160121202d042a893570d13a4c00aa4

du listing: https://gist.github.com/f623325ae7d1d50a1875ef879cc94d62

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

16 total rebuild path(s)

4 package rebuild(s)

4 x86_64-linux rebuild(s)
4 i686-linux rebuild(s)
4 x86_64-darwin rebuild(s)
4 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
kaggle
python37Packages.kaggle
python38Packages.kaggle
python39Packages.kaggle

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/v92y1br18jlxmyacdzypyrh3cqwywx1s-python3.7-kaggle-1.5.10 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/v92y1br18jlxmyacdzypyrh3cqwywx1s-python3.7-kaggle-1.5.10
ls -la /nix/store/v92y1br18jlxmyacdzypyrh3cqwywx1s-python3.7-kaggle-1.5.10/bin

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

3 packages built:

kaggle (python38Packages.kaggle)
python37Packages.kaggle
python39Packages.kaggle

Maintainer pings
cc @cdepillabout for testing.

Result of nixpkgs-review pr 106122 run on x86_64-darwin 1

3 packages built:

kaggle (python38Packages.kaggle)
python37Packages.kaggle
python39Packages.kaggle


Support exporting metrics to Stackdriver Logging

Today we split events from the Loggregator into Stackdriver Logging/Monitoring. It is desirable to have the metric data available in Stackdriver Logging so users can use exports for further analysis. An example would be exporting to BigQuery to perform custom calculations on metrics not available in Stackdriver Monitoring.
Design Considerations:

Should it be a 'All or Nothing' to log to both Stackdriver Logging and Monitoring or should each endpoint have it's own list of events?
Should we need to perform the same culling for metrics destined for Stackdriver Logging?

Should it be a 'All or Nothing' to log to both Stackdriver Logging and Monitoring or should each endpoint have it's own list of events?

We were certainly surprised that when adding CounterEvent,ValueMetric,ContainerMetric events to firehose.events: sent them to a different place ( Stackdriver Monitoring rather than Stackdriver Logging ).
We'd like to propose having 2 separate config settings ( in both the BOSH release and the Tile )
  firehose.events_to_stackdriver_logging:
    description: Whitelisted event types to send to Stackdriver Logging (comma separated). Valid values include LogMessage,Error,HttpStartStop,CounterEvent,ValueMetric,ContainerMetric
    default: LogMessage,Error
  firehose.events_to_stackdriver_monitoring:
    description: Whitelisted event types to send to Stackdriver Monitoring (comma separated). Valid values include CounterEvent,ValueMetric,ContainerMetric
    default: CounterEvent,ValueMetric,ContainerMetric

For the Pivotal Tracker on GCP use case; we'd probably send everything to Stackdriver Logging -> because we want the ability to send some of the data into BigQuery, and CounterEvent,ValueMetric to Stackdriver Monitoring

@johnsonj Thanks for acting on this issue so quickly.
Will this change make its way into v1.0.6 of the GCP Stackdriver Nozzle for PCF tile ?

Yes! I just need to do some manual validation before releasing. I think it
will be v1.1.0.
On Wed, Aug 23, 2017, 11:35 PM David Laing<EMAIL_ADDRESS>wrote:

@johnsonj https://github.com/johnsonj Thanks for acting on this issue
so quickly.
Will this change make its way into v1.0.6 of the GCP Stackdriver Nozzle
for PCF tile https://network.pivotal.io/products/gcp-stackdriver-nozzle
?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cloudfoundry-community/stackdriver-tools/issues/99#issuecomment-324354705,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAZo5c825cDGPerTO3qb0v5W8MnlFHxbks5sbDjHgaJpZM4O6m9_
.

Released as v1.0.6. Pivnet update pending approval.

Re-opening since v1.0.6 was rolled back due to performance issues

Released as v2.0.1.


ADBDEV-4318: Fix deadlock in case of the BottleNeck HashJoin with shared scan below

Disabling the prefetch mechanism for HashJoin, when the Join was at the
BottleNeck, could lead to a deadlock if there was a SharedScan in both
parts of the join. The deadlock occured because SharedScan producer was in the
inner part of the join, and consumer was in the outer. Thus consumer couldn't
perform the shared scan without prefetching the inner part.
The SharedScan producer for HashJoin is always created under the inner part,
because shareinput_walker function always processes HashJoin node from the Hash
part. For CTEs the prefetching was enabled for all cases, except
the BottleNeck join, because CTE path is marked as motionHazard. Therefore, if
prefetch is disabled, the executor can start performing join from the outer
part while the SharedScan producer will be inside the inner part and this will
probably lead to the deadlock if the SharedScan is cross-slice.
This patch fixes this by not disabling prefetch_dinner for Hash join if
gp_cte_sharing is enabled and we may have a Hash Join on BottleNeck with
Shared Scans below. Without this GUC Hash Join with Shared Scan can appear only
with three-phase aggregation, which is not applied if aggregation occurs on the
coordinator.

Allure report https://allure-ee.adsw.io/launch/54818

Allure report https://allure-ee.adsw.io/launch/54979

Allure report https://allure-ee.adsw.io/launch/55095

I'm ready to approve this.
But extend the patch description explaining the nuances of

Shared Scan that required prefetch_inner to be enabled (see shareinput_walker)

Disabling the prefetch mechanism for HashJoin, when the Join was at the
BottleNeck, could have led to a deadlock if there was a SharedScan in both
parts of the join. The deadlock occured because SharedScan producer was in the
inner part of the join, and consumer was in the outer. Thus consumer couldn't
perform the shared scan without prefetching the inner part.
The SharedScan producer for HashJoin is always created under the inner part,
because shareinput_walker function always processes HashJoin node from the Hash
part. Therefore, if prefetch is disabled, the executor will start performing
join from the outer part while the SharedScan producer will be inside the inner
part and this will probably lead to the deadlock if the SharedScan is
cross-slice.
This patch excludes such deadlocks by preserving the prefetch_inner flag for
the HashJoin when join is held at BottleNeck.
What do you think of such style?  And about CTE path, does it always lead to prefetch_inner = true ? If so, you may write about it as well

yes HashJoin enable prefetch_inner if inner or outer paths are marked as motionHazard and CTE is always marked.
https://github.com/arenadata/gpdb/blob/3756bbba81d9e01ee5a8b4d2238734c47fa0c43e/src/backend/optimizer/util/pathnode.c#L2931
https://github.com/arenadata/gpdb/blob/3756bbba81d9e01ee5a8b4d2238734c47fa0c43e/src/backend/optimizer/plan/createplan.c#L3771-L3776

the Hash part and if join has CTE below then prefetch_inner will be enable because CTE
path marked as motion Hazard. Therefore. if prefetch

--->
the Hash part. For shared CTEs the prefetching was enabled for all cases, except
the BottleNeck join, because CTE path is marked as motionHazard. Therefore,
Will it be correct statement?

for CTE motion Hazard turn on regardless of whether it is shared or not.

Allure report https://allure-ee.adsw.io/launch/55236

Failed job Behave tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/659210

Allure report https://allure-ee.adsw.io/launch/55312

Now you edit two places, but the test only checks one?

should I test including nested loop and merge join?

should I test including nested loop and merge join?

I think, yes, and you may use explain analyze to show plan and execution simultaneously.

Allure report https://allure-ee.adsw.io/launch/55395

Allure report https://allure-ee.adsw.io/launch/55403

Allure report https://allure-ee.adsw.io/launch/55411

Failed job Regression tests with Postgres on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/663586

Failed job Regression tests with ORCA on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/663587

Allure report https://allure-ee.adsw.io/launch/55499

Allure report https://allure-ee.adsw.io/launch/55504

Allure report https://allure-ee.adsw.io/launch/55534

Allure report https://allure-ee.adsw.io/launch/55544

Allure report https://allure-ee.adsw.io/launch/55840

This patch cause to performance degradation. It will be better if prefetch will be executed in the case of shared scans only. If hash join is executed on bottleneck without shared scans, then prefetch is not required.

Failed job Build for x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/682697

Failed job Build for ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/682698

Allure report https://allure-ee.adsw.io/launch/56022

Failed job Regression tests with Postgres on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/682872

Failed job Orca unittests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/682876

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/682880

Failed job Behave tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/682877

Failed job Regression tests with ORCA on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/682873

Allure report https://allure-ee.adsw.io/launch/56105

Allure report https://allure-ee.adsw.io/launch/56116

Failed job Regression tests with Postgres on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/686843

Failed job Behave tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/686849

we call shareinput_mutator_dag_to_tree twice for nodes (on way down and way up) and on way up we already know about the existence of at least producer.

Allure report https://allure-ee.adsw.io/launch/56211

Failed job Build for x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/692569

Failed job Build for x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/692599

Allure report https://allure-ee.adsw.io/launch/56258

Failed job Regression tests with ORCA on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/692670

Allure report https://allure-ee.adsw.io/launch/56309

Allure report https://allure-ee.adsw.io/launch/56323

Allure report https://allure-ee.adsw.io/launch/56454

Allure report https://allure-ee.adsw.io/launch/56572

Allure report https://allure-ee.adsw.io/launch/56581

Allure report https://allure-ee.adsw.io/launch/56625

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/706790


Add support for uint under the Number primitive.

The Number primitive needs support for uint:

[x] Implement IEquatable<uint>.
[ ] Implement IComparable<uint>.
[ ] Implement ISpanParsable<uint>.
[ ] Unit test coverage for the implementations.

Note: The unit test coverage for the IEquatable implementation will be contributed by the repo owner.

This issue needs information on which interfaces are implemented by the BCL types to ensure consistency with .NET runtime.

Currently being discussed in #43 .


Add Prerelease Github Action

Description
We will pre-release on merge with main allowing to test, before major release. On npm registry the tag next will be sync with the latest changes on main
Checklist

[x] For UI or styling changes, I have added a screenshot or gif showing before & after
[x] I have added a changeset

As discussed: how do we increment the versions under the next tag?


Update QT client messages and corresponding translations

This is a rough first attempt to update QT client messages and translations to Doge
equivalents. Haven't managed to update in Japanese or Chinese translations, and need
to merge in corrections made to the existing translation files as well.

Haven't solved the copyright issue (just reverted it to "Bitcoin Core"), as we'll need to add a new translation and modify the UI. Otherwise it's in a lot better state. Could you check the merged translations and tell me if any more need culling? I've cleared the worst messes out, at least.

Still feels like a lot of unneeded changes there. I looked at master and collected actually contributed file updates. There would be zh_CN, zh_TW, it, nl and ko_KR.
For Japanese a find&replace from ビット to ドージ should work as far as I see from the Android Wallet, where a reddit user gave me the hint a while ago.

Okay, try that?

That looks a lot better to me. Ignore my comment about Japanese for now as it turns up with weird results on Google, although the one that's bitcoin at least resembles the meaning a lot better :D
I still want to compile this once and look over it, but so far ACK.


appengine/gophers: add step 5, Firebase authentication

CC @angelafunk.

This fixes https://github.com/GoogleCloudPlatform/golang-samples/issues/418.

The Go 1.6 build is broken - blocked by https://github.com/firebase/firebase-admin-go/issues/110.

Note: this is still blocked by Firebase support for Go 1.6. See https://github.com/firebase/firebase-admin-go/pull/120 and https://github.com/firebase/firebase-admin-go/pull/119.

Closing and reopening to trigger a Travis build.

The Firebase updates are in and the 1.6 build now passes. Please take another look.


Rye中文文档

虽然目前Rye还处于试验阶段，但是无法阻止我的热情。
现在已经开始把文档翻译成中文，希望能在中文互联网推动Rye的发展。
如果作者允许的话 我们将欢迎更多小伙伴加入并完善文档。
预览可以看 https://www.pyrye.cn

I suggest to consider translating the existing README and docs (https://github.com/mitsuhiko/rye/tree/main/docs) as a pull request, to keep translation in-repository. Perhaps later on an official documentation website could be generated with the multiple translations.


display issues with transformed symbols (with links to illustrate)

Hello,
I use a MovieClip symbol which contains several Sprite symbols. I apply a cocktail of scale + rotation + skew on them, and try to understand when problems occure.
It seems that rotation + skew only works on symbols which have homogen scale (same scale.x and scale.y). You can also apply skew and non homogen scale on symbols which have a rotation of 0° or 180°.
Other cases seems to fail.
Demo project (built with Haxe, pixi v3, updated libraries included into project folder haxe/lib/) :
https://github.com/NicolasVereenoghe/git.vega.pixi3.testFlump
Running demo :
http://a-lyrae.com/demo/flump/
Screenshot of the original Flash scene :
https://github.com/NicolasVereenoghe/git.vega.pixi3.testFlump/blob/master/tmp/shot.jpg
The original Flash source :
https://github.com/NicolasVereenoghe/git.vega.pixi3.testFlump/blob/master/assets/assetsGame.fla
A friend tested the same Flump exported files, with Flambe, and the display is accurate.

It might not be easy to see the issues through my "quickly deploy mini game" framework, so I've just tested the same thing directly drawing on stage, and same problems :
var lMovie : Movie = cast stage.addChild( new Movie( "template"));
lMovie.x = lMovie.width / 2;
lMovie.y = lMovie.height / 2;

There might be a kind of patch to correct this transformation issue.

Apply scale to the layer child, not the layer itself :
Into pixi.flump.Movie::renderFrame, at line 317 and 318 :
layer.scale.x = scaleX;
layer.scale.y = scaleY;
Instead :
if ( layer.children.length > 0){
layer.getChildAt( 0).scale.x = scaleX;
layer.getChildAt( 0).scale.y = scaleY;
}else trace( "WARNING : Movie::renderFrame : " + symbol.name + " : " + layer.name + " : empty");

Apply the renderFrame on a Movie after its children are added
Into flump.MoviePlayer::render, from line 317 to 327 :
movie.renderFrame(
keyframe,
(keyframe.location.x + (next.location.x - keyframe.location.x) * interped),
(keyframe.location.y + (next.location.y - keyframe.location.y) * interped),
(keyframe.scale.x + (next.scale.x - keyframe.scale.x) * interped),
(keyframe.scale.y + (next.scale.y - keyframe.scale.y) * interped),
keyframe.skew.x + (next.skew.x - keyframe.skew.x) * interped,
keyframe.skew.y + (next.skew.y - keyframe.skew.y) * interped,
keyframe.alpha + (next.alpha - keyframe.alpha) * interped,
lColor
);
Move this right after line 346, so that the content of the movie instance would be scaled.

I call this a patch because I'm not sure if I break something.
A big problem is that you can no longer modify the scale property of a layer's child into your code because it is refreshed at render time to its orginal.
As far as I understand, when you use the skew property of a pixi Container, if you also modify the scale, the scale transformation is applied on a not skewed landmark. On the contrary, when you use the rotation property, if you also modify the scale, the scale is applied on a rotated landmark.
myContainer.skew( myRotation, myRotation)
is not equivalent to
myContainer.rotation = myRotation
as stated in pixi.flump.Movie::renderFrame
I hope it makes sense, I'll try to use this patch ...

Nico , maybe you can submit a PR ;)

Hey :)
It implies that you can no longer modify scale property of a layer's child, which is very annoying :)
on the other hand, the display is accurate :)
Maybe, there is a better solution ? I would access a transform matrix but it doesn't seem to be available on local landmark ... though, there's a worldTransform property, but it doesn't seem to help ?

hi Nicolas,
the cause of this seems deeply rooted in pixi's way to handle transforms, as explained here:
https://github.com/pixijs/pixi.js/issues/3163
Meanwhile, probably your idea to put the scale in a child is the simplest fix.

Hello :) I've just sent a pull request to propose the fix. I'll test this, thanks :)

Thanks for looking into this issue. Happy to incorporate the pull request.
For now I will leave this issue open just incase there are some unforeseen side effects.

@gludion toLocal() and toGlobal() seem to still work correctly

Hey, i've just built another fix.
In order to solve the transform issues, due to the difference between flash or flump on one hand, and pixi on the other hand. They interpret the scale and the skew transformations not in the same order :s
With 0.2 pixi-flump :
http://a-lyrae.com/demo/flump0.2/
With my fix, flash and html look the same :
http://a-lyrae.com/demo/flump0.2fix/
Like previously, the scale is shift from the layer to the children, but this time I also apply the x & y offsets to the child ;)

the code for my test :
https://github.com/NicolasVereenoghe/git.vega.pixi3.flump
the flash source animation :
https://github.com/NicolasVereenoghe/git.vega.pixi3.flump/blob/master/assets/assetsTest.fla

PR sent

Hello :)
Finally, I think I have something good !
before : http://a-lyrae.com/demo/flump0.2/
aflter : http://a-lyrae.com/demo/flump0.2fix/
A part of the Movie::renderFrame had to be rewritten. It now manages much more things !
I had to understand that parameters received by the renderFrame function had to be interpreted differently if we treat a flipbook (weird), a Movie or a Sprite.
As previously, the scale needs to be applied to the layer's child to conform to flash/flump model. It manage offset between transform point and origin that you can use in flash.
Updated flash source animation :
https://github.com/NicolasVereenoghe/git.vega.pixi3.flump/blob/master/assets/assetsTest.fla
I did a lot of testing, I hope it doesn't break anything because this fix brings new oportunities ;)


Move CatalogKey, ColumnMetadata, ColumnMap, CatalogTable to dbt-common

Problem
Part 2 of https://github.com/dbt-labs/dbt-common/pull/147, we want to move CatalogTable to dbt-common, so adapters can depend on them
Solution
Keep import stubs via __init__.py, but depend on versions from dbt-common.
Will require a dbt-common minor version bump.
Checklist

[x] I have read the contributing guide and understand what's expected of me
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX
[ ] This PR includes type annotations for new and modified functions

Keep import stubs via init.py, but depend on versions from dbt-common.
👍


New Var For Filename Pattern: ObjectTypePascalCase

We have ObjectTypeShortPascalCase but not ObjectTypePascalCase.
Maybe I am just missing how one of the other options would apply.

We have ObjectTypeShortPascalCase but not ObjectTypePascalCase.
Maybe I am just missing how one of the other options would apply.

Same scenario here, looking for ObjectTypePascalCase.
These are the current options, no < ObjectTypePascalCase >.


[enhancement] refactor test_run_to_run_stability_tests

Description
This refactors test_run_to_run_stability_tests into test_run_to_run_stability by using the centralized PATCHED_MODELS and other functions within the sklearnex/tests/_utils.py in order to centralize and automate discovery for testing coverage. This duplicates the current functionality such that GPU support can be easily added in a follow-on PR. This reduces the overall maintenance, and aligns with other sklearnex centralized testing.
Changes:

Add proper calls for dispatching LogisiticRegression predict_proba and predict_log_proba
Add cpu checks which properly log fallbacks to sklearn
Add allow_sklearn_fallback to n_jobs testing
Change name of test_run_to_run_stability_tests to test_run_to_run_stability
Create four tests, 1) estimators from patch map with defaults, 2) special instances with specifically set hyper parameters, 3) sparse testing, 4) specific instances that were previously tested in test_run_to_run_stability_tests
Use get_dataframes_and_queues with pytest parametrize for eventual GPU and array_api testing
Rewrite sklearnex/tests/_utils.py gen_dataset to be more generalized for use in test_run_to_run_stability
Rework test_patching to work with the new gen_dataset
shorten integer check in test_patching

Tasks

[x] Compile
[x] Correct issues discovered in public CI
[x] Pass public CI
[ ] Correct issues discovered in private CI
[ ] Pass private CI

/intelci: run

/intelci: run

/intelci: run

/intelci: run

/intelci: run

/intelci: run

/intelci: run

/intelci: run


AlamofireObjectMapper 6 + Alamofire 4 (latest final versions) not compatible

It seems to me that the latest final release AlamofireObjectMapper 6 is not (downward) compatible with the latest final version of Alamofire (4; 5 is still beta).
So this combination using Carthage has stopped working since:
github "Alamofire/Alamofire"
github "tristanhimmelman/AlamofireObjectMapper"

This, however, works:
github "Alamofire/Alamofire"
github "tristanhimmelman/AlamofireObjectMapper" ~> 5.2

Is this known and accepted? Shouldn't a new final version of AlamofireObjectMapper be compatible with the latest final version of Alamofire (it will soon presumably, but not yet)? As a consequence, this could mean that AlamofireObjectMapper 6 would remain beta for at least as long as Alamofire 5.
By the way, thank you for providing this and other great libraries!

@niccey, I've created a fork that is compatible with Xcode 10.2. It upgrades the Swift version from 3.0 to 4.0.
Try putting this in your Cartfile:
github "rzulkoski/AlamofireObjectMapper" "migrate-to-swift-4"

@tristanhimmelman, is it possible to merge my changes in a hotfix release? Say 5.3.0? Here's my branch.

@niccey, I've created a fork that is compatible with Xcode 10.2. It upgrades the Swift version from 3.0 to 4.0.
Try putting this in your Cartfile:
github "rzulkoski/AlamofireObjectMapper" "migrate-to-swift-4"

@tristanhimmelman, is it possible to merge my changes in a hotfix release? Say 5.3.0? Here's my branch.

Thank you, that was the only way I could get around dyld: Symbol not found error. I hope the repo gets maintained soon.

@kublaios That's right, with Xcode 10.2 that is. I ran into the same problem now. My above Cartfile definition worked until Xcode 10.1.
Thanks, @rzulkoski. Your solution is not directly related to my OP but it solves this new Xcode 10.2 problem. With Xcode 10.2 and without your branch, I couldn't even get it to work with AlamofireObjectMapper 6 + Alamofire 5 Beta, I think I got the error mentioned by @kublaios. I guess this issue affects many users of this library.

Yeah, #266 references the same issue and has a similar fix. Whenever Alamofire 5 is officially released we should all be able to go back to master, but I'll be using this fork in the meantime. Glad you guys were able to get back up and running. /cheers

Hello @niccey
I think you should try AlamofireObjectMapper v.5.2.1. It uses Alamofire 4.8.2.


publishes with same URI each 20 minutes.

SELECT COUNT(`uri`), uri
FROM `publish`
GROUP BY 2
ORDER BY 1 desc
LIMIT 5

SELECT *
FROM `publish`
WHERE `uri` = '@ClashOfBeards#2/elite-dangerous-beautiful-vistas-and#4'
LIMIT 50
OFFSET 48950


Preventing from CompletionController triggering in interactive/FSI

When triggering completion (Ctrl-Space) in the F# Interactive window, this would cause an error with out of range index.
Changing to Document role to prevent it.
This shows again that FSI should have its own content type.

I can't repro, I'm on 2015U1. Does it still repro? Maybe it would be better to fix the exception than disabling emojis in the F# Interactive WIndow.

Can't say I tried it recently... but what use would it be in the F# (or any) interactive window anyway?

I agree it doesn't make a lot of sense, it just seems that it's hiding the real issue.


Syncing won't download files from container

What happened?
Syncing upload files from local computer, but won't download files from container.
What did you expect to happen instead?
devspace download files from container as well.
How can we reproduce the bug? (as minimally and precisely as possible)
I tried syncing with phpfpm container
Local Environment:

Operating System: windows
Deployment method: helm

Kubernetes Cluster:

Cloud Provider: none
Kubernetes Version: Client: v1.14.3, Server: v1.15.2

Anything else we need to know?
minikube v1.3.0
devspace 3.5.12
I couldn't try 3.5.14 because both syncing and build is broken:
[info]   Loaded config from devspace.yaml
ERRO[0007] Can't add file *FILE_PATH* to tar: io: read/write on closed pipe
ERRO[0007] Can't close tar writer: io: read/write on closed pipe
ERRO[0016] Can't add file *FILE_PATH* to tar: io: read/write on closed pipe
ERRO[0016] Can't close tar writer: io: read/write on closed pipe
[fatal]  Error building image: Error building image my-app/elasticsearch:latest: Info: Building image 'my-app/elasticsearch' with engine 'docker'
 Error during image build: Error response from daemon: client version 1.40 is too new. Maximum supported API version is 1.39

/kind bug

@vroad thanks for reporting this issue!
Regarding the fatal error in the newest version, I already fixed this and will rollout a new version pretty soon, thanks for finding and reporting this.
Regarding the sync issue, it works for me with the php:7.1.31-fpm image. Could you share your devspace.yaml and send me the log of the command devspace sync -n yournamespace --pod yourpod after you created a file remotely? In which folder are you creating the file in the container?

Actually the command I used was devspace dev.
With devspace sync, sync worked as I expected. The image was php:7.2-fpm, but I doubt if the version has to do with the problem.
[info]   Start syncing
[done] √ Sync started on C:\path\to\my-app <-> /var/www/html (Pod: default/my-app-855b76f994-rvmhh)
[info]   Downstream - Download 9110 files (size: 34379038)
[info]   Upstream - Upload 975 create changes (size 6222188)
[info]   Upstream - Successfully processed 975 change(s)
[info]   Downstream - Untared 500 files...
[info]   Downstream - Untared 1000 files...
[info]   Downstream - Untared 1500 files...
[info]   Downstream - Untared 2000 files...
[info]   Downstream - Untared 2500 files...
[info]   Downstream - Untared 3000 files...
[info]   Downstream - Untared 3500 files...
[info]   Downstream - Untared 4000 files...
[info]   Downstream - Untared 4500 files...
[info]   Downstream - Untared 5000 files...
[info]   Downstream - Untared 5500 files...
[info]   Downstream - Untared 6000 files...
[info]   Downstream - Untared 6500 files...
[info]   Downstream - Untared 7000 files...
[info]   Downstream - Untared 7500 files...
[info]   Downstream - Untared 8000 files...
[info]   Downstream - Untared 8500 files...
[info]   Downstream - Untared 9000 files...
[info]   Downstream - Successfully processed 9110 change(s)
[info]   Initial sync completed
[info]   Downstream - Download file /foo, size: 0
[info]   Downstream - Successfully processed 1 change(s)

@vroad thanks for the output! The advantage of devspace sync is that you can see directly what the sync is doing (with devspace dev the sync log will be in .devspace/logs/sync.log but the command is essentially doing the exact same as the devspace sync command in the background). Can you provide me the sync config in your devspace.yaml?

@vroad: Does the issue still exists when using the latest version of DevSpace? If yes, please provide further details on the sync configuration within your devspace.yaml.

dev:
  terminal:
    labelSelector: &phpfpm-pod-selector
      app: my-app
      service: web-server
    containerName: &container-name my-app-phpfpm
  sync:
    - labelSelector: *phpfpm-pod-selector
      containerName: *container-name
      localSubPath: ./
      excludePaths:
        - .git/
        - .devspace/
        - var/

I've tried devspace version 3.5.16 and the issue still exists.

@vroad Thanks! Could you also provide us the .devspace/logs/sync.log after a faulty devspace dev run?

@vroad I found the problem. The php-fpm container default working directory is /var/www/html and we have a bug on the server side with the exclude paths that they are not applied relative to the working directory. Hence the exclude path var/ will exclude all files from the folder /var/www/html and you don't see any files downloading.
I will fix this and add this to the next release

Should be fixed in v3.5.17


New release?

I reached out to @arvidkahl to offer some help on release management for this library that we use.
A couple of fixes (Elixir warnings) have been integrated, it would be a good moment to create a tag / issue a release.
Happy to help if possible!

@arvidkahl has added me as a contributor, I'll work on a few fixes, CI setup, overall clean-up & gear toward a release.


Bump default pagination size to 1000

Description
Bump default pagination size to 1000
/cc @dogemos @Thunnini
Is this fine to do from a backend node performance perspective?

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

[ ] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards.
[ ] Wrote unit and integration tests
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added relevant godoc comments.
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer
[ ] Review Codecov Report in the comment section below once CI passes

Not needed


Micro:bit 2021 Release Blog Post

Hi Galen,
Can you get this blog post prepped for release?
Hoping to release tomorrow (Friday 6/25)
All files here - https://1drv.ms/u/s!AmMIW5Hxi0RtgZ8Sz5hMvcR4ND8kdg?e=0wcNBP
Thanks!
Jacqueline

Sure, I'll to it this afternoon.


get method dataTaskWithRequest

I had already init a AFHTTPRequestSerializer, then
request =  [serializer requestWithMethod:[self requestMethodName]
                                                       URLString:[self.baseURL stringByAppendingString:self.requestURL]
                                                      parameters:[self generateRequestParameters]
                                                           error:&sError];

And then I use this request to send a get request using AFHTTPSessionManager with method dataTaskWithRequest:, but it return code"201" and I found out that the final url I send did not split joint with the encoded-parameter.
I can not do the GET request by this method because I didn't make it? But I wanna use dataTaskWithHTTPMethod:but it did not Open interface.
It make me sad


Look into Sphinx extension to add OOP design to documentation.

Maybe can use https://pylint.pycqa.org/en/latest/pyreverse.html

Some find it useful. Equally, code should be self-documenting. OOP design diagram will also need updating - perhaps automatically generate.


ensure order numbers can be hand-written

ie do not use the characters lI1oO0 and possibly others depending on how serious we want to be. see http://www.ismp.org/newsletters/acutecare/articles/20090702.asp and http://psqh.com/july-august-2014/misidentification-of-alphanumeric-symbols (quick search results) for more examples of confusion

@nmorduch: I think you can take this one. You'll want to look into the get_random_string function in django.utils.crypto. We use it in brambling/views/orders.py to generate new codes for orders - it takes a second argument which is the alphabet to choose from.
I'd recommend setting the alphabet as a constant at the top of the orders.py file, right after ORDER_CODE_SESSION_KEY.

Did not remove characters such as cCsS2ZvV because that started to feel excessive. Limited it to removing the ones listed above, which can be hard to distinguish on a screen.


Make virtualenv use pythonFull, not python

See https://github.com/AndersonTorres/nixpkgs/commit/d6feeeaab18cdc9d9942aec8c890f9c8799fa382

(triage) @domenkozar is that solved yet?

Nope.

I never really use virtualenv so I got curious what the issues really are about.
nix-shell -p python35Packages.virtuallenv python35Packages.toolz

[nix-shell:] virtualenv testenv
Using base prefix '/nix/store/ln2cn6g6rf116vaq1fgngaqzpzfq495x-python3-3.5.1'
New python executable in testenv/bin/python3.5m
Also creating executable in testenv/bin/python
Installing setuptools, pip, wheel...done.

[nix-shell:] source test/bin/activate

(testenv)[nix-shell:] python3 -c "import toolz; print(toolz.__version__)"
0.7.4

Clearly, the testenv is not entirely separated from the nix-shell and it's easy to understand why: we've added the package to $PYTHONPATH.
The question is now whether this is an issue. To me it seems more like a feature; nix-shell can already be used to obtain isolation. This gives us instead the possibility to add already packaged packages to an environment, although, of course, this won't work with a requirements.txt or so.
To get back to the issue here. We can use pythonFull, e.g. by just adding all the modules as propagatedBuildInputs to pythonPackages.virtualenv. It seems like an easy fix to me. What do you say?

The issue is mostly about UX. python doesn't have readline or sqlite3, which is very annoying in virtualenv. I've been thinking we'd just include both by default since they're light and convenient.

I’d love that!

Since #19309 we don't have separate modules anymore except tkinter, which is like a 'normal' Python package: pythonPackages.tkinter.
I will soon write some docs on how virtualenv can be used with Nix and what to be wary of.


Update resilience to disclose that sttp does retry

Users shouldn't have to debug to discover that sttp does in fact do more than a 1:1 connection.
If your server happens to have an idle timeout (e.g. play at 75 seconds),
and thus the server side's connection closes prematurely,
sttp will merrily retry the connection, and if that fails, it'll merrily try again, and again, ....
Before submitting pull request:

[ ] Check if the project compiles by running sbt compile
[ ] Verify docs compilation by running sbt compileDocs
[ ] Check if tests pass by running sbt test
[ ] Format code by running sbt scalafmt

Hm it is possible that some backends have some additional behavior. Here you are using async-http-client, is that correct?

Correct - I worked with @jsoref on the problem.

Thanks - I'll reword a bit though, and move the changes to the proper docs, as you've modified the generated version.
To configure AHC, you can provide the org.asynchttpclient.maxRequestRetry option (default 5), or provide custom configuration when creating the backend.


Get access to the getupdates chan

Hello everyone! How i can get access to the getupdates chan.
I want to handle sequence of actions by bot user, after certain action by user. Can you give me advise about it

Hi. You can use default handler for get all bot updates.

Thanks a lot!


seed-time=0 is not appropriate

The auto generated aria2.conf will set seed-time to 0, which will stop seeding as soon as download finished, which is some kind of evil to bit torrent ecosystem.
自动生成的aria2.conf中会设置seed-time为0，这样下载一完成就不做种了，某种程度上败坏aria2的在bt社区的名声，建议改下。

+1 not so good


Unable to build binary on node.js 20

To run harness test, need to run yarn build.binary first. But the pkg used in build binary script had been deprecated and no support to nodejs 20. Got error Error! No available node version satisfies 'node20'.
See: https://github.com/vercel/pkg/issues/2014

@aleung we have not upgraded Prism to support node 20 yet, although it's on our radar for the future.

till now there is no changing thepkg doesn't support node 20


Add Transaction metric collection

Add per-agent transaction count metric collection support for all 4 types of transactions:

Sampled New
Unsampled New
Sampled Continuation
Unsampled Continuation

Currently tps is calculated by factoring in 2 situations - when a new trace is created, and when a new disabled trace is created.
Need to consider 2 more situations where the trace is a continuation:

When a trace is continued, and sampling is true
When a trace is continued, and sampling is false

Should continue after #1103

Changing spec to collect the number of transaction over a certain period of time.
Tps calculation will be done when querying using this data.

Reopening to remove version field.

Reopening for UI


Pod File issue

[!] CocoaPods could not find compatible versions for pod "nanopb":
In Podfile:
ar_flutter_plugin (from .symlinks/plugins/ar_flutter_plugin/ios) was resolved to 0.6.2, which depends on
ARCore/CloudAnchors (~> 1.32.0) was resolved to 1.32.0, which depends on
nanopb (< 2.30910.0, >= 2.30908.0)
firebase_messaging (from `.symlinks/plugins/firebase_messaging/ios`) was resolved to 15.1.0, which depends on
  Firebase/Messaging (= 11.0.0) was resolved to 11.0.0, which depends on
    FirebaseMessaging (~> 11.0.0) was resolved to 11.0.0, which depends on
      nanopb (~> 3.30910.0)

Several other issues about this. It seems to be fixed now. This solution worked for me.

I did the same as mentioned in the solution but it is not working.


LibJS: Cache the shape for normal ECMAScriptFunctionObject prototypes

Instead of creating a unique new prototype shape every time a function object is instantiated, we now keep one cached with the intrinsics.
This avoids a whole lot of shape allocations, reducing GC pressure.
Did this in an effort to make https://blt.se/ load faster. Still lots of work to do. Lots of GC pressure.

(reverted in https://github.com/LadybirdBrowser/ladybird/commit/061ad33705765792ae935bc8d77e329c20ce55d0)


Add .flake8 as INI file

This adds .flake8 as a filename for the INI language.
Description
.flake8 files use the INI format

we expect you to use INI to configure Flake8 (since each of these files already uses INI as a format).

flake8 is a fairly popular tool for checking Python code, and the .flake8 file seems to exist in a lot of repositories as a config file.
Checklist:

[x] I am associating a language with a new file extension. (technically filename, not extension, but this is the most applicable checklist :shrug:)

[x] The new extension is used in hundreds of repositories on GitHub.com

Search results for each extension:

https://github.com/search?q=filename%3A.flake8&type=Code

[x] I have included a real-world usage sample for all extensions added in this PR:

Sample source(s):

poetry's flake8 config

[ ] I have included a change to the heuristics to distinguish my language from others using the same extension (is this necessary for filename additions, too? Using #3817 as an example.).

I noticed that many INI-format files, like .editorconfig, are classified as their own language. I wasn't sure if that's necessary for .flake8 files.

:frowning: Workflow failed. The push I just did should fix it.

I noticed that many INI-format files, like .editorconfig, are classified as their own language.

Generally, this is to take advantage of a dedicated grammar for syntax highlighting; i.e., sindresorhus/atom-editorconfig. Such languages are grouped under a parent language, and are considered to be such for the purposes of language usage stats.

I wasn't sure if that's necessary for .flake8 files.

If a bespoke .flake8 grammar exists that offers noticeably improved highlighting, then a separate entry for Flake8 configs would make sense. INI's grammar seems to do a good enough job of highlighting .flake8 files, though.


ArgumentException: The 'ClientId' option must be provided

Followed the steps, but when starting, I get "ArgumentException: The 'ClientId' option must be provided"
You need to also do this:
services.AddAuthentication().AddGoogle(googleOptions =>
{
googleOptions.ClientId = Configuration["Authentication:Google:ClientId"];
googleOptions.ClientSecret = Configuration["Authentication:Google:ClientSecret"];
});
Even with this update, after selecting the Google account on the login page, you get the following result after being redirected to https://localhost:44381/signin-google?.....
HttpRequestException: An error occurred when retrieving Google user information (Forbidden). Please check if the authentication information is correct and the corresponding Google+ API is enabled.
Microsoft.AspNetCore.Authentication.Google.GoogleHandler.CreateTicketAsync(ClaimsIdentity identity, AuthenticationProperties properties, OAuthTokenResponse tokens)
Exception: An error was encountered while handling the remote login.
Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler.HandleRequestAsync()

There's nothing to address in the docs here. The advice above about configuring user secrets and should help anyone with this particular issue.


Issue card improvements

Fixes https://github.com/go-gitea/gitea/issues/30682 and does a few improvements:

Use gap instead of margin/padding
Don't render empty image div
Remove right floated class that did nothing

The only "trick" here is tw-gap-[5px], but I felt the need to have such a specific value there.


Proof harness for aws_byte_cursor_read_be* functions

Description of changes:

Updates implementation of aws_byte_cursor_read_be* functions with pre- and post-conditions;
Adds proof harnesses for aws_byte_cursor_read_be* functions;
Adds a preprocessor check to hton64 function to avoid assembly instruction when using CBMC.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@feliperodri @tautschnig @karkhaz @angelhof @danielsn @markrtuttle could you review the proof harnesses?

Looks like you need a clang-format run tho

The new implementation looks great, thank you! Please rebase and run the formatter, then ping us for a merge.

This PR is being blocked by CBMC issue causing verification to fail.

Approved with small comments.

@lucasmt With the updates to CBMC now all proofs succeed. There still is a CodeBuild failure and comments by @danielsn need addressing.

@ColdenCullen @danielsn @tautschnig @karkhaz could you merge it?


Single-spa types not exported with plugin

I am seeing the following issue when I integrate the plugin to my root app. I am not certain however I think this github issue on single-spa could be related to the problem I am seeing.

Vue: Could not find a declaration file for module single-spa. ./node_modules/single-spa/lib/es2015/esm/single-spa.min.js implicitly has an any type. There are types at ./node_modules/single-spa/typings/single-spa.d.ts , but this result could not be resolved when respecting package.json exports. The single-spa library may need to update its package.json or typings.
Project type: [x ] Root Config [ ] Micro-frontend/parcel
Project Framework:  [ ] React [ ] Svelte [ x] Vue [ ] Preact [ ] Other:
My vite config:
import { fileURLToPath, URL } from 'node:url'
import { defineConfig } from 'vite'
import vue from '@vitejs/plugin-vue'
import vitePluginSingleSpa from 'vite-plugin-single-spa';

export default defineConfig({
  plugins: [vue(), vitePluginSingleSpa({
    type: 'root',
    imo: '3.1.1'
  })],
  resolve: {
    alias: {
      '@': fileURLToPath(new URL('./src', import.meta.url))
    }
  }
})

Hello, @amalvivek.  Those are functions that are provided within the single-spa NPM package, not this package.  This package doesn't ship single-spa and merely has it as a peer dependency.

Ah apologies!

No problem.  FYI, single-spa v7 will be out with better typing.  For now, you'll have to deal with the current types single-spa provides.  If you get in trouble like this, you could use TS tricks like the @ts-expect-error comment.


fix(ssr): no external symlink package

Description
Fix https://github.com/sveltejs/kit/issues/5542
If a package is symlinked, we should not externalize it by default as we usually treat them as source code instead, in this case, we no externalize it. This PR handles this.
Additional context

Also refactored the logic flow
The ssr external function only returns boolean without undefined as we're not using the undefined value anywhere

What is the purpose of this pull request?

[x] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the Commit Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[x] Ideally, include relevant tests that fail without this PR but pass with it.

We should still respect ssr.external, right? E.g. vite-plugin-ssr should never be externalized, even if it's linked.

should never be externalized

never always


Thumbnails in preview

Is it possible to have thumbnails in the preview as well ?

Hi @stefan-krajnik, unfortunately no.

@lukasz-galka is it possible to implement it ?

of course, I can think about it, but I can't promise you any date

I also need this feature,  do you have any plans on implementing it?

Hi @oplitnik I will think today how I can implement this and let you know

+1

@lukasz-galka can we implement this?


Can't locate object method "new" via package "HASH"

Following the README I run into an error:
job@snel:~/source/rpki-aspa-demo$ docker run -it apnic/rpki-aspa /bin/bash
root@ffd9b4ae398a:/# /sbin/service rsync start
 * Starting rsync daemon rsync                                                                                [ OK ]
root@ffd9b4ae398a:/# setup-ca --name ta --resources 1-65000
writing RSA key
root@ffd9b4ae398a:/# setup-ca --name ca --parent-name ta --resources 1234
writing RSA key
root@ffd9b4ae398a:/# sign-aspa --ca-name ca --customer-asn 1234 --provider-asn 1235 --out my.asa
Can't locate object method "new" via package "HASH" (perhaps you forgot to load "HASH"?) at /usr/share/perl5/Convert/ASN1.pm line 377.
root@ffd9b4ae398a:/# verify-aspa --ca-name ta --in my.asa
read_file '//my.asa' - open: No such file or directory at /usr/local/bin/verify-aspa line 75.
root@ffd9b4ae398a:/#
```

(running b69c07e70ac19ecdaa8f3fe911a0afc309a3a215)

Ugh, thanks, forgot to update the sign-aspa script to account for the previous set of changes.  This has been fixed now.


pull request for e2e test at 01/20/2017 10:26:17

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Opening File Explorer using the browse button in settings sometimes gets stuck

Windows Terminal version
1.11.3471.0
Windows build number
10.0.19044.1469
Other Software
No response
Steps to reproduce

Press Ctrl + ` to open the settings interface
Click "Add a new profile" to create a new profile
Click the "Browse..." button
The interface freezes. Neither the File Explorer window nor the "Windows Terminal" can be closed via the taskbar

Expected Behavior
Open a file explorer window that works normally, but also can be closed normally
Actual Behavior
The interface is frozen, and the Explorer window for selecting files cannot be manipulated, nor can this window be closed

#13167 has a video attached to it that demonstrates, and also only repros on Windows 10.
This might honestly be something outside our control if it was fixed somehow in Windows 11.


gpkit models needs a setup script

Need a simple setup.py so that users can install the package and use it in other applications.
First, we need to decide what the package name is:
gpkitmodels?
gpkm?
gpkmodels?
We'll move all the models into a folder of that name.

I favor gpkitmodels

It seems this issue should have been closed by #61


Fixing a few typos

This commit just fixes a few typos / inconsistencies in log message strings and should have no other impact. The only exception is the fix inpkg/mocks/ingress.go (probably didn't work before ?)

This is quite embarrassing spelling :see_no_evil:
Thanks for your contribution! @renaudguerin


wrong error report 'incompatible type of initializer'

struct S {
    int a;
    int b;
};

int i;
struct S s = {1, (struct S){i}.a};

wgtcc: error: incompatible type of initializer

But there are no type errors, the error is that the initializer is not a compile-time constant.

I used to be trying to eliminate the generation of anonymous objects in initializer list, but, as we see, it failed.
I have commented(https://github.com/wgtdkp/wgtcc/commit/f42f6e5083ca88702868099781abc1c9522b65e2) that optimization to make things right.
thx :)


A Potential bug in the code

Hi, thank you very much for your open source work.  I've been going through your code recently and spotted something that's got me a bit puzzled. In anchor_projection, it looks like the index positions of returned yaw might be flipped – the first dimension is actually cos(\theta), which is inconsistent with the definition in bbox3d. I also saw that you made some changes in below  that you commented out, and you've tweaked the Sparse4D in SparseDrive  too. Just wondering why you didn't make similar adjustments in this repo. Is it because it won't affect the accuracy or something else? I'd love to hear your thoughts on this. It's really helpful for me to understand the reasoning behind your choices. Thanks a bunch!

It won't affect accuracy, but if we fix this bug, the currently released model checkpoints will all need to be updated, which is quite troublesome. Therefore, we haven't fixed it for now.


Donut chart, show bordered hollow/transparent donut even when data is 0's

When series contains 0, give us an option to show a donut that has a border but is hollowed/transparent.
Imagine a row with several donuts in it, each representing a type of data. If one donut have series of 0's, it would show nothing, making the design inconsistent.

If you have 0 data, you can show a data-point with value 100 which will draw a round circle to keep the design consistent.
Here is the configuration you can use to achieve that.
            series: [100],
            fill: {
                opacity: 0
            },
            stroke: {
                colors: ['#3C99BA']
            },
            dataLabels: {
                formatter: function(val) {
                    return ''
                }
            },
            tooltip: {
                enabled: false
            },


One of our unit tests seems to start a transaction concurrently with closing the database, this sometimes causes a panic here: https://github.com/golang/go/blob/a4cb37d4afd4b6b386ed7b51466c8c57c6045f9c/src/database/sql/sql.go#L3644
I haven't been able to reproduce this with db.Conn db.Close calls yet, but I do have a unit test in https://github.com/golang/go/pull/68953 using database/sql.(*connRequestSet).CloseAndRemoveAll and database/sql.(*connRequestSet).Delete that reliably reproduces the panic.
Update: reproduced with exported methods on database/sql.DB here: https://go.dev/play/p/fHZFq6zgAV4
What did you see happen?
This looks like a race condition in database/sql.(*DB).conn:

In (*DB).conn here delHandle is set to the result of db.connRequests.Add(req), and then db.mu is unlocked
A concurrent call to db.Close will call db.connRequests.CloseAndRemoveAll here
(*DB).conn re-locks db.mu here and calls db.connRequests.Delete(delHandle)
delHandle.idx is positive and no bounds checking is done before trying to index into the slice which was set to nil by (*connRequestSet).CloseAndRemoveAll, resulting in the panic.

Here's a full stack trace (from https://github.com/gravitational/teleport/actions/runs/10427126860/job/28881284822):
panic: runtime error: index out of range [0] with length 0

goroutine 5494 [running]:
database/sql.(*connRequestSet).deleteIndex(...)
	/opt/go/src/database/sql/sql.go:3644
database/sql.(*connRequestSet).Delete(...)
	/opt/go/src/database/sql/sql.go:3638
database/sql.(*DB).conn(0xc001569380, {0x15fa19c0, 0xc0031d4000}, 0x1)
	/opt/go/src/database/sql/sql.go:1366 +0x1625
database/sql.(*DB).begin(0xc001569380, {0x15fa19c0, 0xc0031d4000}, 0x0, 0x1)
	/opt/go/src/database/sql/sql.go:1883 +0x57
database/sql.(*DB).BeginTx.func1(0x1)
	/opt/go/src/database/sql/sql.go:1866 +0x7a
database/sql.(*DB).retry(0x7fa4fef225c8?, 0xc002c0b2c8)
	/opt/go/src/database/sql/sql.go:1568 +0x4b
database/sql.(*DB).BeginTx(0xc001569380, {0x15fa19c0, 0xc0031d4000}, 0x0)
	/opt/go/src/database/sql/sql.go:1865 +0x108
github.com/gravitational/teleport/lib/backend/lite.(*Backend).inTransaction(0xc0033cde40, {0x15fa19c0, 0xc0031d4000}, 0xc002c0b498)
	/__w/teleport/teleport/lib/backend/lite/lite.go:949 +0x155
github.com/gravitational/teleport/lib/backend/lite.(*Backend).Get(0xc0033cde40, {0x15fa19c0, 0xc0031d4000}, {0xc003a9d440, 0x13, 0x18})
	/__w/teleport/teleport/lib/backend/lite/lite.go:598 +0x1e9
github.com/gravitational/teleport/lib/auth/storage.(*ProcessStorage).GetState(0xc0000575c0, {0x15fa19c0, 0xc0031d4000}, {0x14ac87f5, 0x5})
	/__w/teleport/teleport/lib/auth/storage/storage.go:91 +0x264
github.com/gravitational/teleport/lib/service.(*TeleportProcess).initAuthService.func5()
	/__w/teleport/teleport/lib/service/service.go:2486 +0x2db
github.com/gravitational/teleport/lib/srv.(*Heartbeat).fetch(0xc002010ea0)
	/__w/teleport/teleport/lib/srv/heartbeat.go:339 +0x56
github.com/gravitational/teleport/lib/srv.(*Heartbeat).fetchAndAnnounce(0xc002010ea0)
	/__w/teleport/teleport/lib/srv/heartbeat.go:624 +0x2f
github.com/gravitational/teleport/lib/srv.(*Heartbeat).Run(0xc002010ea0)
	/__w/teleport/teleport/lib/srv/heartbeat.go:282 +0xe8
github.com/gravitational/teleport/lib/service.(*LocalService).Serve(0xc0022c37c0)
	/__w/teleport/teleport/lib/service/supervisor.go:588 +0x36
github.com/gravitational/teleport/lib/service.(*LocalSupervisor).serve.func1()
	/__w/teleport/teleport/lib/service/supervisor.go:313 +0x489
created by github.com/gravitational/teleport/lib/service.(*LocalSupervisor).serve in goroutine 4831
	/__w/teleport/teleport/lib/service/supervisor.go:302 +0x105

What did you expect to see?
I expected no panic. sql.DB is advertised as "safe for concurrent use by multiple goroutines"

Related Issues and Documentation

iOS  fatal error: bulkBarrierPreWrite: unaligned arguments #63255 (closed)
database/sql: panic: double close #18429 (closed)
database/sql: panic in DB.QueryRow #61646 (closed)
database/sql: concurrent (*Tx).Stmt calls may crash when Tx is canceled #23208 (closed)
database/sql: rows.Next panic from concurrent map writes #27448 (closed)
database/sql: data race #9715 (closed)
database/sql: possible deadlock on Rows.awaitDone()/Rows.Err()/Rows.Close() after RawBytes change #64498
database/sql: segfault in connection pool when the driver frequently fails to connect #24445 (closed)
database/sql: race detector is not happy on darwin/amd64 #6928 (closed)
database/sql: deadlock on transaction stmt context cancel #40985 (closed)

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

Looks like this code was introduced in https://github.com/golang/go/commit/190d0d3e69b113bea0b6b604ba2f0beb62c08741 by @bradfitz

cc @bradfitz @kardianos @kevinburke

Update: I managed to reproduce the panic very reliably in the go playground using only exported methods https://go.dev/play/p/fHZFq6zgAV4

@cherrymui, this probably warrants a backport to the 1.23 branch.

@gopherbot please backport this to Go 1.23. This is a regression in 1.23. Thanks.


[GH-436] - Making chef client logs readable by all

Fixes issue #436

In general users consider these logs to be sensitive and we've chosen to default the config to 640 due to that. The permissions are and attribute if you wise to make them 644.


Update function lib and remove MobileTable

Update function lib to 1.2.0 and remove mobile  table for it is not supported now.

Codecov Report

Merging #490 into develop will decrease coverage by 0.31%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop     #490      +/-   ##
===========================================
- Coverage    45.56%   45.25%   -0.32%
===========================================
  Files           69       68       -1
  Lines         2401     2380      -21
  Branches       269      269
===========================================
- Hits          1094     1077      -17
+ Misses        1241     1237       -4
  Partials        66       66

Impacted Files
Coverage Δ

.../azure/maven/function/bindings/BindingFactory.java
90.9% <ø> (-0.52%)
:arrow_down:

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 a9836cd...863ca0c. Read the comment docs.


feat(its): process deploy interchain token message

AXE-6952
Uncertain if conversion method for minter is correct. Please see my comments.

Codecov Report
Attention: Patch coverage is 98.71795% with 1 line in your changes missing coverage. Please review.

Project coverage is 94.56%. Comparing base (6ec2622) to head (e94168f).

Files with missing lines
Patch %
Lines

contracts/interchain-token-service/src/contract.rs
98.71%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #122      +/-   ##
==========================================
+ Coverage   94.46%   94.56%   +0.09%
==========================================
  Files          52       52
  Lines        3019     3074      +55
==========================================
+ Hits         2852     2907      +55
  Misses        167      167

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[Tracking] Security Updates

🚀 Feature
This issue will track all of the pending and completed security related PRs.

[ ] Sparse polynomial sorting - #660
[ ] Zip safety - #661
[x] Coefficient to biginteger out of bounds - #655

https://github.com/AleoHQ/snarkVM/pull/655/files#diff-65c324b0c9a766e87a9021bb7110133f9c423fa069bf34c2ac2fbff03167940fR561-R571

[ ] Groth16 prover panics when r equals zero - #678

Closed in favor of PR #679


Add identifier escaping

On a number of occasions, it is useful to have identifiers that do not follow the usual lexical conventions or collide with keywords:

to match foreign message names (e.g., from Candid),
to work around names being reserved (e.g., and, or),
to generally have identifiers that are not limited to alphanumeric.

Here is one possible suggestion:

We use single quotes for quoting identifiers.
For char literals, we use double quotes and rely on the existing overloading mechanism.

I believe that char literals are rare enough that this shouldn't be a significant problem, and it frees up the use of a precious ASCII character. Thoughts?

Just ran into this again; I used the empty string as a method name in Candid (to have shorter hand-written Candid data) in the test suite, but that didn’t work.

BTW, does the candid spec specify the ordering use to sort method names. Is there actually a standard ordering on utf8 we can appeal to?

I think adding method name escaping to Motoko makes a lot of sense and don't see much difficulty doing it. C# has a similar feature and I'm sure many other industrial languages do too.

... and then we could be tempted to use zero width spaces to encode type identifier stamping (tempting but I'm not actually serious.)

BTW, does the candid spec specify the ordering use to sort method names. Is there actually a standard ordering on utf8 we can appeal to?

I assume it's lexicographic ordering of the utf8 encoding, but being explicit is helpful of course.


There is a problem with the chart timestamp conversion time

Lightweight Charts Version:1.1.0
Steps/code to reproduce:

Actual behavior:
I am ready for the data, the timestamp is set to<PHONE_NUMBER> when setData in the chart, but there is a problem in rendering time.
The timestamp seems to be a problem when converting
Expected behavior:

Screenshots

CodeSandbox/JSFiddle/etc link:

So, what the problem is?

So, what the problem is?

https://github.com/tradingview/lightweight-charts/issues/232#issuecomment-542685473

So, what the problem is?

I want to ask Is there an compatibility problem with Apple phones?

So, what the problem is?

I do not know

So, what the problem is?

Will it be a problem in the time zone?The time displayed in the picture differs from the current time by eight hours.

I do not know

I mean that you've said "There is a problem with the chart timestamp conversion time", but didn't say which one 🙂

Will it be a problem in the time zone?The time displayed in the picture differs from the current time by eight hours.

I'm not sure that understand you correctly. On your screenshot on the timescale the latest time is 07:18, the latest date you provided is 07:14 (I'm not sure, maybe there was a bit of realtime updates).
> new Date(1571210040000).toISOString()
'2019-10-16T07:14:00.000Z'

I used some demos on the official website, and I tried to change the time inside the data. https://jsfiddle.net/8efskn4y/
For example,<PHONE_NUMBER> is converted to time

There are eight time zones in the middle. I am Beijing time.
So, is it a time zone issue when the timestamp is converted?

By default we convert dates as they are in UTC timezone, but you can override time formatter via localizationOptions (it'll affect crosshair mark only, not timescale marks thought).

By default we convert dates as they are in UTC timezone, but you can override time formatter via localizationOptions (it'll affect crosshair mark only, not timescale marks thought).

Then will it be added later? When the timestamp is converted, the current time zone is automatically determined according to localization.

Then will it be added later?

What? Converting to specific timezone? Without supporting from the browser I don't think that we'll add it.

I'm going to close the issue. If you'll have any question or updates - feel free to re-open it.

@timocov
please check this one:-
https://jsfiddle.net/saurab_93/ghc74Ldu/2/

data i feed to chart is of dec 2 2019 as you can see in console but at chart it is ploting from dec 1 2019.
do you have any idea how to ressolve this....
thankyou.

@timocov
please check this one:-
https://jsfiddle.net/saurab_93/ghc74Ldu/2/

data i feed to chart is of dec 2 2019 as you can see in console but at chart it is ploting from dec 1 2019.
do you have any idea how to ressolve this....
thankyou.

i solve this issue... !!!
https://jsfiddle.net/saurab_93/ghc74Ldu/15/

@saurabBajgain Actually it isn't data of 2nd December

We use UTC value of the date:
>>> new Date(1575216000000).toISOString()
<<< 19:26:49.816 "2019-12-01T16:00:00.000Z"

If you want to see it as 2nd Dec, you need to add an alignment of the timezone for every bar you have.

@saurabBajgain Actually it isn't data of 2nd December

We use UTC value of the date:
>>> new Date(1575216000000).toISOString()
<<< 19:26:49.816 "2019-12-01T16:00:00.000Z"

If you want to see it as 2nd Dec, you need to add an alignment of the timezone for every bar you have.

yeah this method dateToChartTimeMinute() helps me  :-
function dateToChartTimeMinute(date) {
return Date.UTC(date.getFullYear(), date.getMonth(), date.getDate(), date.getHours(), date.getMinutes(), 0, 0) / 1000;
};
https://jsfiddle.net/saurab_93/ghc74Ldu/15/
Thankyou for your response


Update custom header examples

Custom header example will now work.
Aligns with changes made as a result of this issue https://github.com/tobli/browsertime/issues/97

Thanks!

Sure thing. Is it normal for this build to fail though? https://ci.appveyor.com/project/tobli/browsertime/build/1.0.104

I'd been experimenting with AppVeyor for CI tests on IE. Hadn't gotten it to a working setup. But apparently it was still active for PRs. It was just adding noise, so it's removed now. Might try to get it working in a dedicated branch, but not a high priority.

@tobli Understood. Just wanted to make sure my README change didn't somehow break the build. That would have been a first, to the best of my knowledge.


Up the e2e-nightly timeout to 15m

Up the e2e-nightly timeout to 15m. Though, at the end of the day, I'm bothered that the variance is so high (and not even convinced that upping the timeout is the right thing to do). Consider this a placeholder for digging deeper.

 what's interesting it's k8s-1.23.15 that fails.
https://kubernetes.io/releases/

1.23
Latest Release:1.23.16 (released: 2023-01-18)
End of Life:2023-02-28

One way is bumping the patch version 1.23.15 -> 1.23.16, maybe it'll fix something. Another way is removing 1.23 from the build matrix as it's becoming EoL this month.

Good thoughts and observations, heres's the PR.


Upload captions to YouTube on preview/publish

When a site is previewed or published, all video resources with YouTube ID's and caption files should have those captions uploaded to YouTube.

@abeglova can this be closed?


Change Wallet PIN/Key

Description of feature / user story
As a holder
I want to change my wallet PIN
so that I can keep my wallet secure with stronger PIN
Acceptance Criteria
Wireframes or relevant image assets / links
Notes

Add item to the settings menu
Refactor PIN create screen to work for PIN update
Export wallet, import with new PIN/salt (new wallet key).  (Is there an easier way to do it?).

Maybe Askar supports re-keying wallet

Update keychain items
If biometrics enabled, update secure storage

Based on July 20 Planning , not a priority , so just add feature flag/PIN for now

Resolved by: https://github.com/hyperledger/aries-mobile-agent-react-native/pull/921

Tested in build 1113 on both Android and iOS.
Can someone close this? I cannot in this repo.


Add BigDipper role

TODO (taken over by @makeworld-the-better-one)

[x] Import postgres schemas
[x] Add scripts for copying genesis file
[x] Get fully working
[x] Inventory file
[x] Get theta working
[x] Go through TODOs in files
[x] Set up letsencrypt TLS reverse-proxy optionally
[x] Check for security issues: exposed endpoints, public passwords etc
[x] Get transactions working in Theta
[x] Basic docs

Current issue is with parsing the genesis file.
Command:
export PATH=$PATH:/opt/go/1.18.4/bin:/root/go/bin
bdjuno parse genesis-file --home /home/bigdipper/.bdjuno --genesis-file-path /home/bigdipper/.bdjuno/genesis.json

Output:
4:25PM DBG parsing genesis module=auth
4:28PM DBG parsing genesis module=consensus
4:28PM DBG parsing genesis module=gov
ERROR: error while storing genesis governance proposals: error while storing deposits: pq: insert or update on table "proposal_deposit" violates foreign key constraint "proposal_deposit_height_fkey"

Opened some issues/PRs:

https://github.com/forbole/bdjuno/issues/449
https://github.com/forbole/big-dipper-2.0-cosmos/pull/959

These aren't blockers. The issue they address is ports being open to the public when they shouldn't be, but I don't think it's a security issue.

I've left the server running as a live demo for review purposes. URL is in chat.

@makeworld-the-better-one
What's the reason for requiring the ansible-galaxy install -r requirements.yml command now?

@dasanchez the bigdipper makes use of some third-party Ansible deps/modules that need to be installed. In earlier iterations of this PR, these deps were used by the gaia role as well (for Go installation). Now that only the bigdipper roles needs them, I think the command could be left out of documentation unless bigdipper was being run. I've left it in because it'll be useful in the future. As I understand it, the plan is to use hypha.common to replace other roles, so deps will need to be installed anyway.

@makeworld-the-better-one it looks like the proposals are being pulled from the wrong source in the test server, these are the ones that we expect to see:
https://explorer.theta-testnet.polypore.xyz/proposals
It is probably related to the validator names display too

Ok I will open an issue for that too. All the issues/PRs I've opened are being tracked in #124. Let me know if the proposal issues are a blocker for merging.

[ ] Get this step working consistently (sometimes stalls): Apply metadata to hasura

@dasanchez tried to address your review

The play stopped here:
TASK [bigdipper : Run docker image for Hasura] *********************************************************************************************************************************************************************************************************************
fatal: [{{ target }}]: FAILED! => {"changed": false, "msg": "Error pulling image hasura/graphql-engine:v2.9.0 - 500 Server Error for http+docker://localhost/v1.41/images/create?tag=v2.9.0&fromImage=hasura%2Fgraphql-engine: Internal Server Error (\"Get \"https://registry-1.docker.io/v2/hasura/graphql-engine/manifests/sha256:63d7e9ee630fe537338b1eda6e90407e12dc5dced9784c64fcf7e197cea9b379\": EOF\")"}

Seems like fluke on Docker Hub's end. I'm able to pull the image fine just with a docker pull command. Let me know if get the error again.

Indeed, I ran the play once more and it didn't fail this time.


Add Truffleruby head to CI

Hi, thanks for your PR. It seems that it errors for rails 3.1 - 4.1. Don't think it's really worth it to fix these issues, so I think it's fine to exclude these from the build matrix.
https://travis-ci.org/github/moiristo/deep_cloneable/builds/736342760

@moiristo updated the exclude section

Thanks!


Add opus format support

Rust already has binding for libopus https://docs.rs/opus/0.2.1/opus/
I don't know if this would help anyhow, but opus support for polaris would be very nice :)

Not as trivial as I was hoping, while the vorbis comments format is the same as ogg, that doesn't mean we can just throw an opus file at lewton and get vorbis comments back.
This will require writing a new crate just for this purpose I'm afraid. @RustAudio in case someone over there has suggestions.

Thanks for reply!
Since there is no urgent need for opus support, and I don't know rust :) this issue can be suspended until someone interested in it will be found :)

idk whether this would be helpful, but here one project that seems can read opus format:
https://github.com/izderadicka/audioserve

Unfortunately, it looks like they get their metadata through ffmpeg (https://github.com/izderadicka/audioserve/tree/master/crates/media_info). I would prefer avoiding this, as it's very heavyweight and would complicate the build process for Polaris.

Ok, I see 🙂

Do you only need the comments/metadata to support opus?
Based on this issue, I have written a small parser (as a rust exercise for myself), which just takes something that implements the Read trait (like a BufferedReader) and spits out the opus headers (if it found any). The comment header then contains a map with all the comments.
I would upload it to github, if this is what you need.
Here is an example of the returned headers (I just entered some garbage as comments when creating the file):
OpusHeaders {
    id: IdentificationHeader {
        version: 1,
        channel_count: 1,
        pre_skip: 312,
        input_sample_rate: 48000,
        output_gain: 0,
        channel_mapping_family: 0,
        channel_mapping_table: None,
    },
    comments: CommentHeader {
        vendor: "Lavf58.29.100",
        user_comments: {
            "album": "alb",
            "encoder": "Lavc58.54.100 libopus",
            "TRACKNUMBER": "num",
            "DESCRIPTION": "co",
            "artist": "a",
            "title": "t",
            "date": "ye",
            "genre": "ge",
        },
    },
}

So it seems like reading metadata actually is the only thing missing for opus support in polaris.
I uploaded my parser here.
I hope I didn't mess it up. It is the first time I created a repository on github.

You didn't mess up but if you don't mind, I'd have a couple of nits about the implementation:

read_bytes allocates a Vec on every call, but it could take a buffer as an argument
partial reads are possible in some cases (e.g. network streams or if the process got a signal), you should use read_exact if you want a full buffer
an enum Error would probably be more idiomatic
the to_u32 functions are a bit redundant, and they also incur a lot of bounds checks

a trick here is to read the values in the reverse order: (buf[1], buf[0]); the difference is that a single bounds check is needed -- note how the index shows up in the panic message, so (buf[0], buf[1]) throws a different panic message
a second one is to do a let buf = &buf[0..2] before accessing it

but I'd still get rid of them

Thank you for that feedback :D All of that is correct. I will look into it.

Yes, that vector in read_bytes is not great. Initially I wanted to use const generics, but it seems like they are still feature gated and thus require nightly rust, which I wanted to avoid. When I tried to use an array, rustc complained that its size is not known at compile time, which makes sense. To get around this issue I used a Vec, but that has the downside you mentioned. I could add a second parameter and let the caller pass a mut buffer which will be filled. In that case, the caller would have to always create a buffer before calling the read_bytes function, which is something I wanted to avoid. I will try to find a different solution.
read_exact sounds like a great idea, since I also throw an error if the amount of bytes read does not equal the amount of expected bytes.
In that case, I probably have to use map_err() to map the potential errors of the reader or string conversion to my own error types. Sounds good and would also get rid of the Box.
The bounds checks could probably be mitigated by adding something like an assert!(slice.len() >= 4) before the conversion call, but I agree that removing those functions would be a good idea. I added them because I return a Vec from the read_bytes function and wanted to pass the result directly into the conversion function, but they expect arrays.

It seems like most of these issues are arising from how the read_bytes function is implemented.
I just looked at the polaris readme again and noticed that it already requires nightly rust. In that case, I assume I can just do the same and make use of const generics. This allows me to return arrays from the read_bytes function, which could be directly passed into the u16::from_le_bytes(...) functions. No more vec allocations and no more conversion wrappers.

I removed the read_bytes and inlined any call to read_exact, as you suggested.
I also use reusable buffers in each method and call the from_le_bytes functions directly.
I use multiple buffers, since this allows to read different amounts of bytes.
Finally, I added an ParseError enum, which encapsulates the UnexpectedEOF, the Utf8Error and my own DidNotFindHeaders error.

I'm also not sure how const generics help there.

You are right, I was misunderstanding what const generics are.

Thank you @zaethan for jumping in and @lnicola for the thoughtful review. Reading this thread warms my heart ❤.
A couple suggestions:

When you're satisfied with the code, publish your library on crates.io so polaris (or other projects) can use it easily. How to guide
Add some unit tests, this will make it easier to maintain the library in the long run. I maintain a similar crate for parsing duration of MP3 files, so you can look at this for reference.
Add two more public functions which accepts a &File and a AsRef<Path> (but keep the reader version too). This would be convenient for the most frequent use cases, and also would help users who might not realize that they should use a BufferedReader. You can also find examples of this in the mp3-duration library above.

Thank you for your feedback :)
I added some tests to test the basic functionality and the rejection of obviously damaged files.
I also added the two extra parse functions you suggested (based on your mp3 crate).
I went ahead and published the current state of the library on crates.io. Once again, this is the first time I'm doing this, so I hope I didn't mess it up ^^ (it does not look like it though)
To add opus support to polaris eventually, it looks like we need to add another entry to the AudioFormat enum in utils.rs.
After that, a new function in the index/metadata.rs would need to be added to actually retrieve the metadata. This would essentially be the same as the existing read_vorbis function.

Awesome!
You are correct about the changes to make in Polaris. If you want to give it a go but you're not sure how to contribute to someone else's project on Github, you can follow this guide as a starting point.
Let me know if you need any help!

Hey, I created a Pull Request adding opus support.
I contributed to other projects earlier (never had one of my own before), but that guide was a welcome refresher (I initially messed up the branches though :) )
That said, I tested my changes with a set of opus and mp3 files and it seems to be working just fine. The opus files were generated from other mp3's with ffmpeg.

Implemented by https://github.com/agersant/polaris/pull/88


Native Build Support for Windows

This issue will document the changes needed for Native Build Support in editor using C++.
Further documentation to be placed here... for now, this is the placeholder. ;-)

I'm going to move this to a Summer 2024 deadline / milestone. There are some features that need to be completed in engine before worrying about the build and play aspect of make files and such.


Git Branch Issue

When I pulled from Github, I found I was on master branch not main, which makes Git does not work well. To fix it, I had to switch to main branch by 'checkout', then I was able to work correctly on Git.

Fixed !
Thank you !


Is it possible to pass arbitrary .NET types including delegates?

With Edge.js it's possible to pass arbitrary .NET types, including delegates, and then have the JavaScript code invoke the delegates. Then, from the .NET delegates, you return back to JavaScript, and so on.
Would it be possible to do something similar with this tool?

That's not something currently supported natively in NodeServices. At some point, we might be able to enable Edge.js as an alternative transport layer that you can use with NodeServices (similar to how you can currently choose between HTTP and Socket transports), but that wasn't possible last time I checked because Edge.js didn't support hosting Node within a .NET Core process.
So right now, all types you pass have to be serializable  by Json.NET.

Is there some fundamental difference between desktop and CoreCLR that prevents hosting Node within a .NET Core process?

Nothing fundamental that I know of. AFAIK, it's just not implemented in Edge.js.


Run a Flutter desktop app on Windows 32 bits

Use case
I am developing an application for Android, web and Windows devices for a client of mine. Everything was going well until this client came to me with a 32 bit Windows machine and, for my surprise, the desktop build of my app won't run on 32 bits environments. I know I can use the Flutter Web build, which is already stable, as a PWA, but it is of my interest also run it as a desktop windows application.
Proposal
Is there any way of running this app in a 32 bits enviroment? If not, do you people plan to add this feature to the future versions of flutter?

Duplicate of https://github.com/flutter/flutter/issues/37777


Add sass and scss test files.

Add sass and scss test files from https://github.com/P233/Syntax-highlighting-for-Sass requested in #11 .

This is fantastic, thanks very much 👍


stripH=off option still removes hydrogens

Issue summary
Hi,
I am wondering what is the proper way of preventing Hydrogen removals from input sdf files in the outputs.
It seems that the 'stripH=off' option still removes hydrogen atoms provided within the sdf files, whereas I still want to keep these hydrogens in the outputs,
It does not matter providing the keywords in the command line or the configuration file.
Any suggestions ?
Thanks
Steps to reproduce
Your system configuration
Operating system:
Compiler:
CUDA version (if applicable):
CUDNN version (if applicable):
Python version:

Be sure to use boolean arguments in this option, according to the source code implementation.

Be sure to use boolean arguments in this option, according to the source code implementation.

Correct, but if the invocation is bad, gnina won't run, so I believe @mmagithub ran it correctly. In the context of boost::program_options, many values count as true/false:

When a boolean does take a parameter, there are several options. Those that evaluate to true in C++ are: "true", "yes", "on", "1". Those that evaluate to false in C++ are: "false", "no", "off", "0".

At any rate, I can confirm the issue: stripH has no effect on whether or not hydrogens are present in the output file.
It would be a useful feature to retain or re-add hydrogens to outputs, even respecting the initial atom ordering in the ligand file.

Nonpolar hydrogens are not kept around. stripH does have an effect, but only for polar hydrogens.