Relationship between Boxes and Users

Note: Boxes still need implementation.
Considering doing a has_many :through (Relationship join table). Then Relationship can hold the user's role in the box.

See #7.


Python project version (in the file) is updated to git tag verison

Making it a JSON didn't help.

:tada: This issue has been resolved in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

Git committing in update_version.sh didn't help as well.


Counter says no vaccination available even if the availability is there

provide me authorization to solve this

Hey @Exploringtechnologies, this issue has been resolved in PR#11
https://github.com/ayushi7rawat/CoWin-Vaccine-Notifier/pull/11

it still says it same kindly check

my PR in not merged yet :/

Okay then sorry for that bro


Check corner case handling for r-m-w patterns in merge on read

This has been done as far as i can see. If there are any missing cases - please open this back up.


Ability to keep dragging with mouse outside the window

If you compare https://codesandbox.io/s/react-resizable-panels-zf7hwd and https://react-grid-layout.github.io/react-grid-layout/ you'll notice that react-grid-layout lets you keep dragging even if your mouse leaves the window, but with react-resizable-panels the drag event seems to stop as soon as the mouse leaves the window.
This is probably not a dealbreaker, but it would arguably be nicer UX if the drag event didn't just stop if you accidentally dragged too much.
Sorry, I'm currently on my phone so I can't record a video to make it crystal clear what I'm talking about but I hope the description suffices!

The behavior of react-resizable-panels was intentional. I wanted to avoid the case of being stuck in a resize when you mouse up while outside of the window. I'm not sure if "mouseup" is guaranteed to always fire if the mouse has moved to another window.
Based on some quick testing though, it looks like Chrome, Firefox, and Safari all do a good job of handling this case (dispatching "mouseup" on the window) so maybe I can change this.

Resolved in #44

Released in v0.0.23


opt clean count usage in ColumnStatistic during stats deriving

Proposed changes
Stats deriving refinement step 1: clean up count usage in ColumnStatistic during stats deriving(mainly for stats-available), to avoid serious stats deriving problem.
a. use Statistics rowCount instead of count in ColumnStatistic in stats deriving, since these two infos may be inconsistent and lead to stats deriving problem.
b. remove setCount interface to avoid using this count field during deriving unexpectedly in the future.
c. refine 2 tpcds case plan by fixing a wrong row count info due to the usage in original ColumnStatistic count.

run buildall

run buildall

run buildall

run buildall

run feut

run buildall

run buildall


Spend time with Gary W deciding on Functional Test Tech

Describe the issue
Gary W, DevOps Guild lead, is looking for an improved functional testing component that is free to use, capable and doesn't require the constant updating that the current BDD (Behaviour Driven Development) stack requires.
Additional context

Gary is targeting our accelerator apps because these imprint people as they go through our onboarding
He wants a very simple low barrier of entry to automated testing

Definition of done

Follow up with Gary on June 27th to prompt for this meeting (if it's too early, then we leave this ticket for next sprint)
One or two meeting with Gary and his team
Include Jon in the sessions
Create well defined tickets for any changes we need to make to our accelerator apps

Gary won't have time for this until start of August

This is an old ticket and Gary W seems to have other priorities. So it can be closed. If necessary can be recreated or reopened


docs: badge fix link

Codecov Report

Merging #27 (3c9b844) into master (09517f2) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #27   +/-   ##
=======================================
  Coverage   58.67%   58.67%
=======================================
  Files          13       13
  Lines         242      242
  Branches       35       35
=======================================
  Hits          142      142
  Misses        100      100

Flag
Coverage Δ

unittests
58.67% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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


Transactions

Coverage decreased (-0.4%) to 40.526% when pulling 2cbddcbca41e3e5b1d053be31b4b8d7ef396baa2 on transactions into cc9f64c4f5ab77fde286913e9aa347dd2c4c5db1 on master.


LexRequirement as a struct, instead of a type

Which issue does this PR close?

Closes #12255.
Rationale for this change

What changes are included in this PR?

Converted LexRequirement type into a struct, with the Vec<PhysicalSortRequirement> as the field labeled inner.
Added two functions for convenience, an iter and push function relating to the struct field.
Added implementations for Deref, FromIterator and IntoIterator.
Are these changes tested?

Adjusted the existing tests
Are there any user-facing changes?

The Vec<PhysicalSortRequirement> needs to be wrapped to initialize the struct insance, and some of the usage needs to be adjusted to get the field from the struct.

Made some adjustments, since there was a merge conflict :)


Charts addon: examples

added screens:
- Bar Chart Screen:

Bar Chart
Clustered Bar Chart

- Pie Chart Screen

Pie Chart
Donut Chart

- Line Chart Screen

Line Chart
Smoothed Line Chart
Stacked Line Chart

- Funnel Chart Screen

Funnel Chart

- RadialBar Chart Screen

RadialBar Chart

- Radar Chart Screen

Radar Chart

- Scatter Chart Screen

Scatter Chart

- Waffle Chart Screen

Horizontal Waffle Chart
Vertical Waffle Chart

- Chord Chart Screen

Chord chart

- Choropleth Chart Screen

Choropleth chart

- Pivot Table Screen

Pivot chart


Update website

Setup site with https://www.docz.site/docs/getting-started, with GitHub actions.
Include donation button that leverages PayButton.
Include 'generate basic PayButton' form.
Include docs.
Include link to github.

We're going to do the framework setup for this and then the design will be outsourced.

TODO:

Fix proptypes component not working.
Fix nav links.
Fix viewable-JS not working.
Setup proper landing page.

We're going to try switching from docz to docsify instead.

Page offsets occasionally (not reproducible)
Broken nav/fragment links
Get Started should have 'What is PayButton?' and 'Basic Usage' under it
versions


Better home for "self-service"

@asteed's namespace sweep (#179) has produced a couple of interesting findings:
https://ns.adobe.com/xdm/selfservice

This should not go into XDM root, but find a more appropriate URL.

@ktukker-adobe kstreeter any suggestions on where this type of schema should reside or be renamed to?
In schemas/common/selfservice.schema.json:

A Customer Managed Environment is an environment that allows a system integration or deployer to manage applications. This is also known as selfservice.

@asteed, I feel like we have several schemas that are really descriptions of have Adobe Cloud Platform, as a system, is defined.  This may be better to move to an extension for ACP, but if we do believe this is could be used to describe a general framework for cloud systems we might want to have a "cloud" folder.
I don't think I would make that change for just this schema though.  It's already in common, and the description makes it clear it is WIP.  I would just mark it experimental and make the namespace match where it resides (common).  We can figure out how to organize it later as it progresses.


Feature/pdct 1514 replace passed/approved from backend

Description
Removed Passed/Approved hardcoded logic to replace with checking for equality with new datetime_event_name
Proposed version
Please select the option below that is most relevant from the list below. This
will be used to generate the next tag version name during auto-tagging.

[ ] Skip auto-tagging
[x] Patch
[ ] Minor version
[ ] Major version

Visit the Semver website to understand the
difference between MAJOR, MINOR, and PATCH versions.
Notes:

If none of these options are selected, auto-tagging will fail
Where multiple options are selected, the most senior option ticked will be
used -- e.g. Major > Minor > Patch
If you are selecting the version in the list above using the textbox, make
sure your selected option is marked [x] with no spaces in between the
brackets and the x

Type of change
Please select the option(s) below that are most relevant:

[ ] Bug fix
[ ] New feature
[ ] Breaking change
[ ] GitHub workflow update
[ ] Documentation update
[ ] Refactor legacy code
[ ] Dependency update

How Has This Been Tested?
Please describe the tests that you added to verify your changes.
Reviewer Checklist

[ ] DB_CLIENT DEPENDENCY IS ON THE LATEST VERSION
[ ] The PR represents a single feature (small driveby fixes are also ok)
[ ] The PR includes tests that are sufficient for the level of risk
[ ] The code is sufficiently commented, particularly in hard-to-understand areas
[ ] Any required documentation updates have been made
[ ] Any TODOs added are captured in future tickets
[ ] No FIXMEs remain

lgtm ... noticed this has bumped db-client too

Needed to because the DFCE helpers wouldn't have added the event metadata otherwise


Support chd parent/clone loading

Fixes #17
I tried to not touch the chd_file, so there are some ugly workarounds and a small calculation every read.
Block offset recorded in CHD is in units instead of hunks, so if it's not aligned to units_in_hunk, the parent hunk to be read will be split between two hunks. Since there is no cache for chd_file, parent read might potentially read twice when all parent hunks are not aligned (one for first/second half, one for second/third half, and so on).
This implementation actually works with children of a child, that is:
Original -> Child -> Grandchild
or even:
Disc 1 -> Mod of Disc 1
\-> Disc 2  -> Mod of Disc 2
For grandchildren, a small modification is needed for chdman. It currently only loads one child via command line argument. mamedev/mame#7594
This was tested with PPSSPP and PCSX2, even with grandchildren, though with PPSSPP, using CDLZ actually makes stutters slightly longer compared to CDZL/ciso.
Sorry, this was done in July, but I hadn't had time to clean this for a pull request. Hope it's a good Christmas gift to all.
Edit: Credits to r5 (rz5?) for the 2 commits in the commit description.
Edit 2: If someone knows how to remove the first 3 commits from this PR from Github which the wrong user was used, I'd appreciate it. Even force pushing it didn't remove it.

Well damn, that's a Christmas present.

This is very good work.
I will be happy to merge this if MAME team merges the corresponding PR.

Is it necessary for the MAME team to merge that PR? That is only for grandchildren creation, not playing.
To prevent the double read, we could change the chd_file to include a cache, much like many emulators implement it already, to prevent reading a hunk multiple times for each unit in a hunk. This would simplify the way we use libchdr, so it might be a good idea to implement (in another PR). If you think this is worthy, we can open an issue after this PR is merged to discuss techniques/etc.

This is a good question whether or not to diverge from MAME.
I don't want to run into the situation where we handle an "incompatible" CHD format.
I am following the PR status on MAME side, they are on code freeze for 0.227 release so no rush.
Yes, the cache is another discussion, I've been thinking of this and threaded read-ahead for a while.

Grandchildren support is great. It makes the idea of a 'disc 2 child of disc 1' and 'translation of disc 1 and 2' at the same time possible.

While I agree grandchildren would be fantastic, as rtissera said, it's squarely in mame's court whether that's something to support.

Then lets hope they don't turn this into a purity test of a format with only this one external implementation.

Sorry, should have been clearer about the grandchildren issue. The CHD format does NOT change whether we're implementing grandchildren or not. The only change in chdman is to load the input's parent when creating, so it takes into account the input's parent's data when deduplicating. You can still create grandchildren CHD with current chdman, it just won't deduplicate correctly.
Imagine we have a 100MB file (file A), apply a 10MB patch to it (now file B), and then another 10MB patch (finally, file C).
So the file layout would be something like
File A
AAAAA
AAAAA

File B
AAAAB
AAAAA

File C
AAAAB
AAAAC

Currently, chdman will deduplicate like this:
File A
AAAAA
AAAAA

File B (only stores the difference between A and B)
____B
_____

File C (stores the difference between B and C, ignoring B's data stored in A)
AAAAC
AAAA_

With my patch, chdman will deduplicate like this:
File A
AAAAA
AAAAA

File B (only stores the difference between A and B)
____B
_____

File C (only stores the difference between B and C, while taking into account B's data in its parent)
_____
____C

This PR will read both CHD files, as the CHD format is not changed. So we will NOT diverge from upstream MAME.

I'm still considering this PR but what is the status of CHD integration in various projects ?
Thinking of PCSX2, DosBox-X, DosBox-Staging, possibly others.

PPSSPP has approved inclusion, but no one has yet done the legwork to make that happen. It has an unofficial bounty (aka a couple of us promised to paypal money to whoever does it) because bountysource screwed up that issue badly.
PCSX2 similarly said they'd be happy to merge it if someone gets the code side supported. Some code was posted along those lines, but there was some issue with dependencies. PCSX2's codebase seems to be a bit of a spiderweb from hell, so that's unsurprising.
No idea about Dosbox stuff.

Well thanks to @irixxxx we switched from libflac to dr flac and I wiped up
most of useless lzma stuff with the option to use system zlib.
So it’s really easier to integrate now I think.
Le sam. 13 mars 2021 à 01:33, Sanaki @.***> a écrit :

PPSSPP has approved inclusion, but no one has yet done the legwork to make
that happen. It has an unofficial bounty (aka a couple of us promised to
paypal money to whoever does it) because bountysource screwed up that issue
badly.
PCSX2 similarly said they'd be happy to merge it if someone gets the code
side supported. Some code was posted along those lines, but there was some
issue with dependencies. PCSX2's codebase seems to be a bit of a spiderweb
from hell, so that's unsurprising.
No idea about Dosbox stuff.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/rtissera/libchdr/pull/42#issuecomment-797831363, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAW4WBNBQ3J7TAC32P2IF33TDKXFNANCNFSM4VJAE7IA
.

SleepyMan chose to base his PR to PCSX2 on this PR so it's just waiting now. There where also other issues to be solved there though and he appears to have disappeared for now.

Just merged it.

With https://github.com/mamedev/mame/pull/7594 being rejected, is it even possible to create "good" grandchildren CHDs at the moment? While chdman technically supports them, specifying multiple parents appears to be impossible so output grandchildren CHDs are bigger than they could have been.


Azure CDN automatically caches file without easy option to disable

Expected Behaviour
User should be able to select whether they'd like the file to be cached.
Actual Behaviour
Currently, it seems that Azure CDN caches the files by default.

We are investigating with the Azure support about the best way to disable it or to automate a regular purge (ongoing with our DevOps team)

Done. @sarahxxu: proposal for a future enhancement (to address in a different issue): enhance the SDK API to let developers programmatically manage caching rules for their own  container.
However, it will need a feasibility study upfront.


Beautifying any js file throws error "command 'HookyQR.beautify' not found"

Versions

beautify - 0.1.9
vscode -  1.5.1
os - ubuntu 16.04.1

Steps to reproduce

f1
beautify

Result
`command 'HookyQR.beautify' not found
Screenshot

Same error here: `command 'HookyQR.beautify' not found
beautify - 0.1.9
vscode - 1.5.1
os - osx 10.11.6

Sorry. I had an outdated version of the VS Code packager and it wasn't including dependancies correctly. Pushed out a new version. Do a search for beautify in the extensions side bar and it should recognise version 0.1.10.

Thanks for the quick fix. Confirmed working on my end.

@HookyQR - Just pulled v0.1.10, it works.
That was quick. Thanks a lot!


Module for SpectralLibrary to FeatureList and RawDataFile

creates a RawDataFile with wrapped scans
adds feature list with all entries as rows
adds feature list with entries collapsed to compounds where all (name, formula, smiles,inchi, inchikey, adduct) are the same


Can't get it to work!

Hi I am a bit of a newbie at web development and I would love to use rangeslider.js in my Masters thesis project. I have downloaded the latest version, installed with Bower via the terminal and linked everything up, I have also changed the setting for the polyfill to false, as shown in previous issues.  Here is my code, if at all useful:
HTML:

    <link href="rangeslider/rangeslider.css" rel="stylesheet">

      <input type="range" id="ranger" min="0" max="99"/>

jQuery:
$(document).ready(function(){       $('input[type="range"]').rangeslider({         polyfill: false,       });     });
Thank you for your help,
Brian

I can't find anyone on Stack Overflow

Have you asked a question? If so, linking to it here would be helpful. At a minimum: the code you've shown here won't work because you're loading jQuery after rangeslider.

@tiesont I tried switching the  around before posting this issue, no difference. here are the StackOverflow questions I posted after browsing existing ones:
https://stackoverflow.com/questions/45170660/rangeslider-js-polyfill-not-working-despite-polyfill-being-set-to-false
https://stackoverflow.com/questions/44854597/rangeslider-js-does-not-install

The example code you get when downloaded from GitHub doesn't even work. Anyone figure this out??

@BeauKelsey Can you be more specific about what "doesn't even work" means? Are there specific errors you are seeing?

dont work for me too :( im using webpack

For me it worked only on document ready
 $(document).ready(function() {         $('[role="range"]').rangeslider({             polyfill : false,             onInit : function() {                 this.output = $( '[role="input-range"]' ).html( this.$element.val() );             },             onSlide : function( position, value ) {                 this.output.html( value );             }         });     });

+1 on this. Can't get it to work.


Nne metadata collector

Sure will fix the other comments later once we get a bit of time :) for that.


Be able to resize font at query editor

Default font-size it's too small, it would be good to be able to resize the font (at least use ctrl + scroll, to increase the font-size)

Closed with 33548c93aa445639bb010f362c58396257554d67


At the conclusion of the final round, the game presents a final scoring and ranking display, highlighting the winner and the final standings of all participants.

commit: 939d7f8

commit: 7387f6a


is There any update

@badafans
Nice work mate
is there any update for this ??

No updates required


Feature Request: parity with latest operator-sdk

I realize this might not be high priority, but it'd be great to be able to use the latest operator-sdk to test changes "locally" using operator-sdk up local but it's not currently possible due to how the project is structured:
❯ operator-sdk up local --namespace=default --kubeconfig=XXX
INFO[0000] Running the operator locally.
FATA[0000] failed to determine operator type

osdk is looking for <project_root>/cmd/manager/main.go to determine the project type

We've been sloppy with this as recently we switched to kubebuilder on other operators we work on. Nevertheless, we will be upgrading this next week, thanks for reporting.

thanks @matyix we've been using the prometheus-operator and absolutely love the pattern. Also want to move to fluent-bit & fluentd so i'd love to help out.

Hello @chiefy - just opened the PR fixing this issue. We are testing it internally (might take 1-2 days) but feel free to check out as well - feedbacks are appreciated. Thanks.


Add tagging preferences

A special section:

Whether contact: prefix is preferred.
Default payment types (visa and mastercard as of now).

Done in 0.1.5.


Issue running the server.

Hi Jan,
I got the maven run and the jar file is created successfully. I run the jar and get the exception that com/passbook/core/HstoreUserType.class is not getting instantiated, however I see that present in the jar file. Is there anyother thing I need to check on why it is not showing up in classpath?.
Error Trace :
mani@mani-laptop:~/passbookserver/jersey-passbook-master$ java -jar target/jersey-passbook-1.0.jar server service-configuration.yml
INFO  [2015-05-12 07:50:13,468] org.hibernate.annotations.common.Version: HCANN000001: Hibernate Commons Annotations {4.0.1.Final}
INFO  [2015-05-12 07:50:13,476] org.hibernate.Version: HHH000412: Hibernate Core {4.1.9.Final}
INFO  [2015-05-12 07:50:13,477] org.hibernate.cfg.Environment: HHH000206: hibernate.properties not found
INFO  [2015-05-12 07:50:13,479] org.hibernate.cfg.Environment: HHH000021: Bytecode provider name : javassist
INFO  [2015-05-12 07:50:13,504] com.yammer.dropwizard.hibernate.SessionFactoryFactory: Entity classes: [com.passbook.core.Device, com.passbook.core.Registration]
Exception in thread "main" org.hibernate.MappingException: Unable to instantiate custom type: com.passbook.core.HstoreUserType
at org.hibernate.type.TypeFactory.custom(TypeFactory.java:218)
at org.hibernate.type.TypeFactory.custom(TypeFactory.java:204)
at org.hibernate.type.TypeFactory.byClass(TypeFactory.java:103)
at org.hibernate.type.TypeResolver.heuristicType(TypeResolver.java:130)
at org.hibernate.mapping.SimpleValue.getType(SimpleValue.java:305)
at org.hibernate.mapping.SimpleValue.isValid(SimpleValue.java:292)
at org.hibernate.mapping.Property.isValid(Property.java:239)
at org.hibernate.mapping.PersistentClass.validate(PersistentClass.java:469)
at org.hibernate.mapping.RootClass.validate(RootClass.java:270)
at org.hibernate.cfg.Configuration.validate(Configuration.java:1294)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1742)
at com.yammer.dropwizard.hibernate.SessionFactoryFactory.buildSessionFactory(SessionFactoryFactory.java:77)
at com.yammer.dropwizard.hibernate.SessionFactoryFactory.build(SessionFactoryFactory.java:35)
at com.yammer.dropwizard.hibernate.HibernateBundle.run(HibernateBundle.java:38)
at com.yammer.dropwizard.hibernate.HibernateBundle.run(HibernateBundle.java:13)
at com.yammer.dropwizard.config.Bootstrap.runWithBundles(Bootstrap.java:64)
at com.yammer.dropwizard.cli.EnvironmentCommand.run(EnvironmentCommand.java:37)
at com.yammer.dropwizard.cli.ConfiguredCommand.run(ConfiguredCommand.java:58)
at com.yammer.dropwizard.cli.Cli.run(Cli.java:53)
at com.yammer.dropwizard.Service.run(Service.java:61)
at com.passbook.PassbookService.main(PassbookService.java:28)
Caused by: java.lang.IllegalAccessException: Class org.hibernate.type.TypeFactory can not access a member of class com.passbook.core.HstoreUserType with modifiers ""
at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:101)
at java.lang.Class.newInstance(Class.java:432)
at org.hibernate.type.TypeFactory.custom(TypeFactory.java:213)
... 20 more

Happens for both Java 7 and 8, the class file is present in the com/passbook/core and is compiled properly, looks like the Device and Registration classes have been loaded properly, only this extension type is having issue to load, other two I see are proper tables.

@maniappan Interesting that… Just back from vacation today, I'll have a look tomorrow

OS: Ubuntu 14.04, DB: Postgresql 9.3 on localhost.
Date: Tue, 12 May 2015 09:15:14 -0700
From<EMAIL_ADDRESS>To<EMAIL_ADDRESS>CC<EMAIL_ADDRESS>Subject: Re: [jersey-passbook] Issue running the server. (#1)
@maniappan Interesting that… Just back from vacation today, I'll have a look tomorrow
—
Reply to this email directly or view it on GitHub.

Thanks, works good.
Date: Wed, 13 May 2015 10:27:49 -0700
From<EMAIL_ADDRESS>To<EMAIL_ADDRESS>CC<EMAIL_ADDRESS>Subject: Re: [jersey-passbook] Issue running the server. (#1)
Closed #1 via effb5b7.
—
Reply to this email directly or view it on GitHub.


Compatibility with segment replication

Summary
With 2.9.0 release, there are lot of enhancements going in for segment replication[1][2] feature (went GA in 2.7.0), we need to ensure different plugins are compatible with current state of this feature. Previously, we ran tests on plugin repos to verify this compatibility but want plugin owners to be aware of these changes so that required updates (if any) can be made
What changed
1. Refresh policy behavior

RefreshPolicy.IMMEDIATE will only refresh primary shards but not replica shards immediately. Instead post refresh, primary will start  a round of segment replication to update the replica shard copies leading to eventual consistency.
RefreshPolicy.WAIT_UNTIL ensures the indexing operation is searchable in your cluster i.e. RAW (Read after write guarantee). With segment replication, this guarantee is not promised due to delay in replica shared updates from asynchronous background refreshes.

2. Refresh lag on replicas
With segment replication, there is inherent delay in documents to be searchable on replica shard copies. This is due to the fact that replica shard copies over data (segment) files from primary. Thus, compared to document replication, there will be on average increase in amount of time the replica shards are consistent with primaries.
3. System/hidden indices support
With https://github.com/opensearch-project/OpenSearch/pull/8200, system and hidden indices are now supported with SEGMENT replication strategy. We need to ensure there are no bottlenecks which prevents system/hidden indices with segment replication.
Next steps
With segment replication strong reads are not guaranteed. Thus, if the plugin needs strong reads guarantees specially as alternative to change in behavior of refresh policy and lag on replicas (point 1 and 2 above), we need to update search requests to target primary shard only. With https://github.com/opensearch-project/OpenSearch/pull/7375, core now supports primary shards only based search. Please follow documentation for examples and details
Open questions
In case of any questions or issues, please post it in core issue
Reference
[1] Design
[2] Documentation

Request plugin onwers to add v2.9.0 label.

Hi Plugin Owners,
Gentle reminder to look into this issue as code freeze date for 2.9.0 release is near i.e. July 11th.

For async search we need to do 'primary-first' preference routing to maintain consistency of 'Get asynchronous search results' API - but we need to do this change post we open up preference routing for segrep + carbon.
So we'll need to defer the fix to 2.10.0

@bharath-techie : With support of realtime reads on core for segment replication enabled indices and assuming queries needing RAW (Read after write) guarantees already using realtime reads, do we still need change in this repo ?

Thanks @dreamer-89 . Closing this as this change is no longer required.

Thanks @dreamer-89 . Closing this as this change is no longer required.

Thanks @bharath-techie for looking into this.
Caution: Please do verify that for strong reads, your plugin relies only on get/mget APIs. I am asking as it is still possible to have strong reads guarantees via write paths by using IMMEDIATE/ WAIT_UNTIL refresh policy which ensures replica shard copies are refreshed with the indexing request, ensuring any follow up data retrieval request receives latest data. With SEGMENT both IMMEDIATE/WAIT_UNTIL does not guarantee replica shard refreshes, so for strong reads, any follow up data retrieval query (other than get/mget APIs), client would need to provide either _primary - hits primary shard only but provides strong consistency or _primary_first - hits primary first (as name suggest), if primary not available request is routed to replica copies resulting in better availability (though data when hitting replica could be stale).


Updated the resolution spec for Samsung Odyssey.

Since the article describes the resolution per eye, it should be 1440 x 1600 instead of 2880 x 1600.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/immersive-headset-hardware-details.md
:white_check_mark:Succeeded
View

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.


Move hpcc command from project-aws to haas

@oxhead is this finished?

We have completed this one.  Now the dependency is totally removed.  I will close this issue.


Work in progress in readding pukless friendos

preliminary commit for CI run
cc @mlsteele can you take a look at chain.go and service_helper.go changes? these seem final, unless there are some issues that I missed, I've just finished this patch.
needs more test coverage, TestImplicitResetMatrix was going to be a parametrised test that would take normal | pukless | web-user-0-eldest user, and them after creating impteam with them, try to readd after they reset and stay pukless | get puk | remain in 0-eldest reset state.

@mlsteele do you think you can take another look today? I'd love to have it merged soon.

On Thu, Feb 22, 2018 at 4:16 PM Miles Steele<EMAIL_ADDRESS>wrote:

@mlsteele approved this pull request.
Looks good. Except for question tagged with (XX)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/keybase/client/pull/10586#pullrequestreview-98730936,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA05_-ZAHiTrfC33Nk6sG7EkWbXPvGYtks5tXdlIgaJpZM4SIVnK
.

:D ok. We should block it on the server then. Because having chain.go freak at this case will hose the team and it won't get repaired.

Oh @mlsteele I take it back, that case does matter. There's definitely server-side support for it
The case I was thinking of is when alice,bob,bob@rooter is proven to be the same as alice,bob, but bob doesn't have a PUK.
The case you bring up is legit, and we should worry about it

hmm ok oops this case is so busted it even crashes the client. thanks for bringing this up, @mlsteele ! The serverside seems fine: https://github.com/keybase/keybase/pull/2151 but client has trouble with that in lookupImplicitTeamAndConflicts with error StatusCode_SCTeamProvisionalCanKey which I'm not sure of meaning yet.

Ok. As I understand it this has a non-crasher bug for a rare case. But is otherwise an improvement. So if you'd like to merge this and follow up on that bug separately that's fine with me.
As for merging this change right before a release, it seems a bit risky so I'm not sure you want to skip the phase of having it bake in an admin build for a day or so.

yup lets skip it for now, we can merge it after emergency release

Provisional status is when the server knows about the resolution of
bob@rooter -> bob, but Alice hasn’t signed bob into the team yet.
The provisional state is needed to stop races.
On Fri, Feb 23, 2018 at 12:12 PM Michał Zochniak<EMAIL_ADDRESS>wrote:

yup lets skip it for now, we can merge it after emergency release
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/keybase/client/pull/10586#issuecomment-368074190, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA05_4-8i0PeOHAnj9MzidH-OibUNfm0ks5tXvFvgaJpZM4SIVnK
.

OK So I think I know what's up with that. When there's a team alice,bob@rooter and bob proves rooter, then client will always resolve that assertion when trying to get alice,bob@rooter and will try to get alice,bob instead, which fails. But alice will never bring bob to the impteam, because she will never get SBS notification if bob is pukless.
I think the behavior of not sending SBS for PUKless users is good, because then the road of pukless sbs assertion to the team is:
bob@rooter -> bob@keybase -> bob
instead of just (if they get PUK beforehand)
bob@rooter -> bob

BTW You need the provisional status to properly label conflicts.  This came
up in getting the kbfs docker tests to pass.
On Fri, Feb 23, 2018 at 2:15 PM Michał Zochniak<EMAIL_ADDRESS>wrote:

OK So I think I know what's up with that. When there's a team
alice,bob@rooter and bob proves rooter, then client will always resolve
that assertion when trying to get alice,bob@rooter and will try to get
alice,bob instead, which fails. But alice will never bring bob to the
impteam, because she will never get SBS notification if bob is pukless.
I think the behavior of not sending SBS for PUKless users is good, because
then the road of pukless sbs assertion to the team is:
bob@rooter -> bob@keybase -> bob
instead of just (if they get PUK beforehand)
bob@rooter -> bob
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/keybase/client/pull/10586#issuecomment-368110572, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA05__g9ztOxhfj58E8G7rq8UCWrZijZks5tXw40gaJpZM4SIVnK
.

I think I'm seeing the full picture now, thank you! Sorry to interrupt your vacation. I'll think about how to fix it without breaking anything else.


[Question] How to make model training reproducible

When we train a model for molecule property prediction it gives different results every time when we train the model. It varies a lot in terms of performance. That makes it difficult for comparing results for different models.
i followed this document randomness but i didn't work

Hi! I think all the random functions used in TorchDrug relies on the random number generation of PyTorch, and they are controllable through torch.manual_seed.
One uncontrollable randomness is from the atomic operations in torch_scatter.scatter_add, which will causes a little bit deviation in floating point results even for the same input. But I don't think it will have large effects on the final performance.


Expose default database collation through 'sql-database-projects' extension API

For the purpose of schema conversion we would need to know whether target database is configured as CI or CS. This will be used to produce a warning, if we detect a case-sensitive identifier, but database is configured as CI. In order to support this scenario we need to access <DefaultCollation/> property of the project.
This change adds new method to the ISqlProject interface that allows to read the value of the project property. There already was similar method for the SQL version/platform (<DSP/> property) and while working on the change, I took an opportunity to refactor the way project properties are extracted from the XML. Original code was hardcoded in the getProjectTargetVersion and I extracted it into separate evaluateProjectPropertyValue helper, that can be used in the future by any getter or access method that is supposed to return a value of the single property. This also allows us to improve the way properties are retrieved from the XML. Today the logic is very rudimentary - we read the first matching XML element with the required name. This is not correct as it does not verify the parent to be <PropertyGroup/>, neither it evaluates the Condition attributes nor property value itself. I did not invest in this, but added a TODO there explaining that the method may not perform as expected.
After the helper method was added, I updated the existing getProjectTargetVersion method to leverage it. The only complication here was the error throwing logic, as it was using custom error message. I preserved that, as there were tests verifying it already. For the new accessor method I did not introduce a special error message and rely on generic one I defined for use within the helper method. Additionally, for the collation we return default value of SQL_Latin1_General_CP1_CI_AS, if project does not have the property defined. This is what SSDT for Visual Studio shows in the UI when property is missing and I decided to align with that.
Finally, I added tests for both - original getProjectTargetVersion and new collation extraction method to make sure they work as expected. While working on the tests, I've noticed complaints that some rehected promises were not awaited. I added missing awaits and explained the scenario there in the comment.

Pull Request Test Coverage Report for Build 861802714

16 of 16 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 43.359%

Totals

Change from base Build 861632751:
0.01%

Covered Lines:
26557

Relevant Lines:
55684

💛  - Coveralls


Reduce Python package size

Description of changes
extend file exclusion list to reduce package size

Issue #,
https://github.com/aws-amplify/amplify-cli/issues/5566
https://github.com/aws-amplify/amplify-cli/issues/9919
https://github.com/aws-amplify/amplify-cli/issues/10942 (partially)

Description of how you validated changes
Checklist

[X] PR description included
[X] yarn test passes
[X] Tests are changed or added
[X] Relevant documentation is changed or added (and PR referenced)
[X] New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies

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

@tb102122 thanks for the contribution! Running our test suite it on it now.

@danielleadams anything I have to do? It does not look like that this is related to my change. https://app.circleci.com/pipelines/github/aws-amplify/amplify-cli/10473/workflows/4f4cee01-0b70-400e-b7a3-b97a87590d24/jobs/343823/tests

@tb102122 I am starting it one more time, but it's unrelated, so no need to update anything.

Great do you have any expected release date?

Interesting, the change is merged but I sill see the pip folder with 2.1MB (compressed) in a lambda with no dependencies

The build was done with the amplify CI/CD upgraded to amplify 12.


Add mutation observer to update styles on DOM changes

Fixes #46

This change is

Thanks for the great review. I updated the PR based on your feedback.


Add M1 support for contract builder

Add support for Mac M1 hardware to use with contract builder. Requires to use docker buildx

I believe this was handled by #751, but feel free to reopen if we missed something


Storing sessions

EDIT:
I have resolved this already by storing the vars properly.
Hi,
I have been using this library for a while and it works perfectly fine.
However, I am interested in optimizing my search speeds.
I am using an API which is located on a server which uses CloudFlare. The CloudFlare clearance takes relatively long for every short search query on the webserver.
I would like to store a session which I have created, so I could access the endpoint during the current session (which lasts about 30 minutes), without having to await the clearance for each lookup.
I have tried the following:
var cookieContainer = new CookieContainer();
using (var handler = new ClearanceHandler())
using (var client = new HttpClient(handler, false))
{
var result = await client.GetStringAsync("http://myapiwebsite.com/apiendpoint");
}

However, by using this, I still have to await the clearance with every search I run. Is there a way to store the current session and use it while it lasts?

Hi , can you share your solution with code snippet.
Thanks


Barcode API scanning Barcode with ISO-8859-1/Latin-1 encoded data

Hello Android-Vision Team,
I'm currently having a big problem with using the Barcode API. I need to scan Barcodes where the payload is an XML with ISO-8859-1 (Latin-1) encoded data. I used the Barcode Sample to verify that's not just an issue with the integration in our App but a general problem with the Library. Here are two examples of a Barcode. One is working and the other is not. It's due to the special characters (äöüß) within the payload.
Working:

Not working:

It seems that the parser per default uses UTF-8 when creating the String from the parsed data. As long as there are no special charaters in it everything works fine. If the payload contains special characters (äöüß) they will be displayed not correct due to the wrong encoding.
That is tested on a Nexus 4 with Android 4.2.2
On a Nexus 6p with Android 7, the application crashes when there are special characters in the payload because the native method call throws an Exception in "NewStringUTF".
Is there a way to define the encoding of the payload or to just get the byte array instead of the Barcode object with the already encoded String?

Thanks for reporting this issue. We expect a fix in a future release will properly convert text to UTF-8.

Hi everybody,
I have the same issue here. As mentioned, I think that the native C-implementation expects UTF-8 encoded text, but the payload of the barcodes is encoded in Latin1. I have tested on a LG G4 wih Android 6 and the application crashes also on this device.
Is there any workaround? For example specifying the encoding of the payload?
In the case of the above shown barcodes we haven't influence on the encoding, because the encoding is defined by a kind of law.
Is the fix already scheduled? In this moment I have to decide using the Google Play Library or an other thridpart library for scanning the barcodes... I'd rather use the Google Play Library, but I know that at least one other library which can handle Latin1 encoded payload.
Regards
Thomas Vogel


switchNetwork is undefined when connected through walletConnect.

Hi. I am facing an issue regarding network switching. When connected through useWalletConnect, the switch network is always undefined. If I connect the wallet using useMetamask, it works just fine.
I am using thirdweb version 3.10.3, react version 18.1.0, Next v13.2.3.
Here is how I configured thirdweb.
`
import "../styles/globals.css";
import { appWithTranslation } from "next-i18next";
import { MusicProvider } from "../context/music-context";
import { ModalsProvider } from "../context/Modals-context";
import { AppContextProvider } from "../context/app-context";
import { ThirdwebProvider } from "@thirdweb-dev/react";
import {Goerli,Ethereum} from "@thirdweb-dev/chains"
export const desiredChainId =
process.env.PRODUCTION === "true" ? Ethereum: Goerli;
function MyApp({ Component, pageProps }) {
return (
<ThirdwebProvider activeChain={desiredChainId}>
  <MusicProvider>
    <AppContextProvider>
      <ModalsProvider>
        <Component {...pageProps} />
      </ModalsProvider>
    </AppContextProvider>
  </MusicProvider>
</ThirdwebProvider>

);
}
export default appWithTranslation(MyApp);
Here is how I am trying to use it.
import React, { useContext, useEffect, useState } from "react";
import {
useMetamask,
useWalletConnect,
useNetwork,
useAddress,
useDisconnect,
ChainId,
} from "@thirdweb-dev/react";
import { shortenAddress } from "../src/utils/shortenAddress";
import { addTokenFunction } from "../src/utils/web3utils";
import { useTranslation } from "next-i18next";
import { useRouter } from "next/router";
import { AppContext } from "../context/app-context";
const ModalWallet = ({ SFTDemo }) => {
const connectWithMetamask = useMetamask();
const connectWithWalletConnect = useWalletConnect();
const disconnectWallet = useDisconnect();
const address = useAddress();
const network = useNetwork();
const isGoerli = network[0]?.data?.chain?.name == "Goerli";
const [, switchNetwork] = useNetwork();
console.log("switchNetwork", switchNetwork);
`

Hey @abubakarafzal444  switchNetwork from useNetwork will be undefined if the wallet is not connected or wallet does not support programatic switching ( wallet connect v1, v2 or any other wallet connected through QR code scan )
in the latest version of react sdk, we have a new hook called useSwitchChain which always returns a function for switching network - you can try it out
https://portal.thirdweb.com/react/react.useSwitchChain


[Feature request]: More flexibility for code-bubble-controls

I can foresee it being useful for users to add custom controls to manipulate the preview area. I imagine this would be configurable via the CodeBubbleConfig['component'] object, so its set at a global level rather than a per-code-bubble level?
One example we're hoping to leverage this feature for is a theme toggler. In our case, this would be a dropdown with some theme options. On selecting an option, our app would handle updating whatever theming / classnames updates are needed to provide the right styles to the component being previewed.

I don't think we will be adding custom controls into the component at this time, but you should be able to get the external controls to work with the controls through either the hooks or updateConfig method.


DID manager is not work on https://manager.movedid.build/

connect wallet testnet, click "INIT ADDRAGGR IN DID CONTRACT",

Launch wallet, got below error

Hello, does this error still exist?

tried again， it's ok now


Exception in VS while editing a Bicep file

Bicep version
Bicep CLI version 0.17.1 (d423d61882)
Microsoft Visual Studio Enterprise 2022 (64-bit) - Current
Version 17.5.5
Bicep for Visual Studio
<IP_ADDRESS>307
Describe the bug
Editing a Bicep file caused an exception and a yellow banner in in Visual Studio. The exception stack trace was:
  <entry>
    <record>731</record>
    <time>2023/05/17 01:05:35.548</time>
    <type>Error</type>
    <source>vs/teamfoundation/git/fileandforget/gitchangesource/fault</source>
    <description>
System.IO.IOException: The process cannot access the file 'c:\Temp\TFSTemp\vctmp16020_847633.main.00000000.bicep' because it is being used by another process.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
   at Microsoft.VisualStudio.Text.Implementation.TextDocumentFactoryService.OpenFileGuts(String filePath, DateTime& lastModifiedTimeUtc, Int64& fileSize)
   at Microsoft.VisualStudio.Text.Implementation.TextDocument.Reload(EditOptions options)
   at Microsoft.TeamFoundation.Git.Provider.ChangeIndication.GitChangeSource.<ReloadActiveGitFileStateAsync>d__42.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.TeamFoundation.Git.CoreServices.AsyncQueuedActionLimiter.<ExecuteActionImmediate>d__10.MoveNext()
</description>
  </entry>

Rather a one-time, I'll reopen the issue if happens to me again.


Come up with a documentation on review process by also making use of Owners file

Describe the feature you'd like to have
Considering we have approvers and reviewers in the repo, we should come up with a process and auto handling of much tasks via OWNERS file. We also need to define the process around this
What new functionality do you want?
What is the value to the end user? (why is it a priority?)
The documented process will help many community users to get proper attention over the PRs , Designs..etc .

The first step is taken here https://github.com/ceph/ceph-csi/pull/1150

@humblec is working on this one. removing stalebot label


Wrong commit number in image "Divergent history" of page "3.1 Git Branching - Branches in a Nutshell"

"testing" branch points to c2b9e and "master" to 87ab2. It should be the opposite.
The URL of the page is:
http://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell

Please close this issue as dulicate #472.


Upgrade engines.vscode to 1.66.0

thank you, but I've done it on another branch already.
Your request will be merged soon.


Support custom status of todos

I use a lot of custom status of checkbox as I am using custom themes (mininal, things, …), maybe there could be a better way to show them in DNO.
For example, to show the character in the checkbox 😊

You can display the text inside the checkboxes by turning on "Appearance" > "Tasks" > "Add checkbox text to prefix" in the settings screen. It might be better to hide the icons.
By the way, is there some official or de facto standard set of custom statuses? If you know of one, I would appreciate a link.

Thank you for your guidance. I have found the corresponding options, but I am thinking that if I could make the letters appear in the check box, it might be better to identify them.
I am not familiar with code, but I know some plugins would show some information, hope that would be useful:
obsidian://show-plugin?id=journal-review

obsidian://show-plugin?id=tasks-calendar-wrapper

obsidian://show-plugin?id=time-ruler
There maybe were something wrong and it does not show tasks now. It simply showed the letter in the checkbox.
Theme:
https://github.com/kepano/obsidian-minimal
https://github.com/colineckert/obsidian-things
https://github.com/PKM-er/Blue-Topaz_Obsidian-css
I think the most basically used will be:
- [ ] to-do
- [/] incomplete
- [x] done
- [-] canceled
- [>] forwarded
- [<] scheduling
- [?] question
- [!] important
- [*] star
- ["] quote
- [l] location
- [b] bookmark
- [i] information
- [S] savings
- [I] idea
- [p] pros
- [c] cons
- [f] fire
- [k] key
- [w] win
- [u] up
- [d] down

Thanks for the useful information.
I think Journal Review plugin may be rendering markdown.
DNO is simple icon + text; Obsidian uses the https://lucide.dev/ icon and DNO uses that too.
It's difficult to display the same as the editor, but it doesn't seem difficult to display some similar icons from the built-in icons.
Minimal theme's custom status might be a good reference. I will consider implementing it in a future update.

Got it! Thank you very much for your excellent development technique. Looking forward to this! :D

Now task icons for custom statuses are displayed in v1.3.0.
Please edit data.json directly if you want to change/add icons for custom statuses.


cc1plus: some warnings being treated as errors after adding new vehicle

Ubuntu 20.04
Apollo 5.0
I added a new vehicle and used the adaptation tool. I try to rebuild after configuring the other files and I get this error. I changed the werror file but it gives me the same issue.

Honda is the new vehicle I added. Just need to get past warning so it can build

The error message is clear. You should check if you forgot the return type.

This warning is similar to the warning described in Return with no value. If control reaches the end of a function and no return is encountered, GCC assumes a return with no return value. However, for this, the function requires a return value. At the end of the function, add a return statement that returns a suitable return value, even if control never reaches there.

The error message is clear. You should check if you forgot the return type.

This warning is similar to the warning described in Return with no value. If control reaches the end of a function and no return is encountered, GCC assumes a return with no return value. However, for this, the function requires a return value. At the end of the function, add a return statement that returns a suitable return value, even if control never reaches there.

Yes, I already fixed this issue. It wasn't the return function. I had to uncomment some tings. Can you please tell me what channel_id for canbus is? I'm using a usb can adapter. Does that show where the device port is on? What does channel_id mean? I know this is off topic but help on this would be greatly appreciated. Thank you. My device is on /dev/bus/usb/002.

As you say this is off topic, We need to keep the issue tidy and focused.
I check the code, for now apollo does not support USB card, you need the driver of usb canbus. currently only supports pci card, socket card.
Because I have never used a usb card, I suggest you debug the relevant driver in modules\drivers\canbus

As you say this is off topic, We need to keep the issue tidy and focused.
I check the code, for now apollo does not support USB card, you need the driver of usb canbus. currently only supports pci card, socket card.
Because I have never used a usb card, I suggest you debug the relevant driver in modules\drivers\canbus

It seems that usb connection can be used. #4935. I just need to know what channel_id is. How can apollo tell which port the device is on? My device is on /dev/bus/usb/002. Is that channel_id? What is channel_id? Thank you

This type is not useful, at least it is not used in the code, if you think it is possible, you can try it

This type is not useful, at least it is not used in the code, if you think it is possible, you can try it

@daohu527 https://github.com/ApolloAuto/apollo/blob/master/modules/drivers/canbus/proto/can_card_parameter.proto (In line 15). Does this mean it can use usb card? Where do I change the drivers to my usb adapter driver? Which file? I get this error in dreamview:

Are you in the apollo wechat?


Update Qiskit to 0.37

Changes

Update notebooks to work with Qiskit 0.37.0

qiskit.test.mock is now deprecated
Optimizer.optimize also deprecated
Removed references to Aqua in VQE page

Also noticed a bug in the VQE page while changing to minimize; the old get_probability_distribution function assumed counts dicts were ordered by key when converting to array, which is often not true. I updated it to just stick with dicts throughout.
Pinned the rest of the requirements to the versions on my system. I couldn't find any references to pycodestyle or mypy so I've removed these.

Hey, I just saw this PR. I made PR #1274 removing ignis from the import list in the vqe molecules notebook. Seems like this change could also be included here. Qiskit 0.37 ended support for ignis.

@MarcoBarroca thanks, your change to the imports on the VQE page is now in the main branch. I can't remove the Ignis requirement from the requirements-text.txt yet as it's still used in some of the error-correction pages.

This is because pyscf needs to be installed. In the current qiskit-nature implementation you need a computational chemistry library to run classical calculations that will serve as inputs for the VQE.
Not sure if this should be added to the requirements.txt or not. pyscf was the library used in the original tutorial.

I think easiest is to update the requirements, I'll do it now.

I still see the same issue on https://learn.qiskit.org/course/ch-applications/simulating-molecules-using-vqe/ on the same code cell. 🙁

That is weird, even when installing pyscf from the notebook it doesn't seem to find it.

Requirement already satisfied: pyscf in /srv/conda/envs/notebook/lib/python3.8/site-packages (2.0.1)
Requirement already satisfied: h5py>=2.7 in /srv/conda/envs/notebook/lib/python3.8/site-packages (from pyscf) (3.7.0)
Requirement already satisfied: numpy!=1.16,!=1.17,>=1.13 in /srv/conda/envs/notebook/lib/python3.8/site-packages (from pyscf) (1.22.4)
Requirement already satisfied: scipy!=1.5.0,!=1.5.1 in /srv/conda/envs/notebook/lib/python3.8/site-packages (from pyscf) (1.8.1)
---------------------------------------------------------------------------
MissingOptionalLibraryError               Traceback (most recent call last)
Input In [15], in <cell line: 13>()
     12 optimizer = SLSQP(maxiter=5)
     13 for dist in distances:
     14     (qubit_op, num_particles, num_spin_orbitals,
---> 15                              problem, converter) = get_qubit_op(dist)
     16     result = exact_solver(problem,converter)
     17     exact_energies.append(result.total_energies[0].real)

Input In [10], in get_qubit_op(dist)
     13 driver = ElectronicStructureMoleculeDriver(
     14     molecule=molecule,
     15     basis="sto3g",
     16     driver_type=ElectronicStructureDriverType.PYSCF)
     18 # Get properties
---> 19 properties = driver.run()
     20 num_particles = (properties
     21                     .get_property("ParticleNumber")
     22                     .num_particles)
     23 num_spin_orbitals = int(properties
     24                         .get_property("ParticleNumber")
     25                         .num_spin_orbitals)

File /srv/conda/envs/notebook/lib/python3.8/site-packages/qiskit_nature/drivers/second_quantization/electronic_structure_molecule_driver.py:174, in ElectronicStructureMoleculeDriver.run(self)
    173 def run(self) -> ElectronicStructureDriverResult:
--> 174     driver_class = ElectronicStructureDriverType.driver_class_from_type(
    175         self.driver_type, self.method
    176     )
    177     driver = driver_class.from_molecule(  # type: ignore
    178         self.molecule, self.basis, self.method, self.driver_kwargs
    179     )
    180     return driver.run()

File /srv/conda/envs/notebook/lib/python3.8/site-packages/qiskit_nature/drivers/second_quantization/electronic_structure_molecule_driver.py:85, in ElectronicStructureDriverType.driver_class_from_type(driver_type, method)
     81     raise MissingOptionalLibraryError(
     82         libname=driver_type, name="ElectronicStructureDriverType"
     83     )
     84 # instantiating the object will check if the driver is installed
---> 85 _ = class_obj()
     86 class_obj.check_method_supported(method)
     87 driver_class = class_obj

File /srv/conda/envs/notebook/lib/python3.8/site-packages/qiskit/utils/classtools.py:116, in _WrappedMethod.__get__.<locals>.out(*args, **kwargs)
    113 @functools.wraps(method)
    114 def out(*args, **kwargs):
    115     for callback in self._before:
--> 116         callback.__get__(obj, objtype)(*args, **kwargs)
    117     retval = method(*args, **kwargs)
    118     for callback in self._after:

File /srv/conda/envs/notebook/lib/python3.8/site-packages/qiskit/utils/lazy_tester.py:39, in _RequireNow.__call__(self, *_args, **_kwargs)
     38 def __call__(self, *_args, **_kwargs):
---> 39     self._tester.require_now(self._feature)

File /srv/conda/envs/notebook/lib/python3.8/site-packages/qiskit/utils/lazy_tester.py:223, in LazyDependencyManager.require_now(self, feature)
    221 if self:
    222     return
--> 223 raise MissingOptionalLibraryError(
    224     libname=self._name, name=feature, pip_install=self._install, msg=self._msg
    225 )

MissingOptionalLibraryError: "The 'pyscf' library is required to use 'PySCFDriver'.  See https://pyscf.org/install.html."


Update Blog “stivo”

Automatically generated by Netlify CMS

👷 Deploy Preview for endearing-sfogliatella-6c7dea processing.

Name
Link

🔨 Latest commit
4b1d1c81155ca80193403843430c858238c99396

🔍 Latest deploy log
https://app.netlify.com/sites/endearing-sfogliatella-6c7dea/deploys/645728602c7b2f00081739ef


Can you update the README with the MIT License?

Would appreciate it.

Sure thing, all done.

Thank you!


BUG-Config attributes are not detected by Linter

Description
taipy.Config attributes such as scenarios or configure_generic_data_nodes are not being detected by my Pylint linter after loading a Config

How to reproduce
Using the VSCode Pylint v2023.4.0 extension. Write the following code:
from taipy import Config
Config.load("config.toml")
scenario_object = Config.scenarios["scenario"]

The linter should highlight that Config has no attribute scenarios
Expected behavior
The linter should detect every attribute of Config. This is really useful because the Linter can show me the docstrings of python functions, the type of the attributes and the code defining these attributes. These linter errors are probably linked to how Taipy defines its Config class
Runtime environment

Taipy version: 2.2.0
OS: Windows

Hi @AlexandreSajus, the Config.scenarios, Config.data_nodes, ... were reported in https://github.com/Avaiga/taipy-core/issues/550. We are working on a fix for this issue.
How about the red underline at Config.configure_generic_data_node(..? Is it the same problem?

Ah my bad, yes same issue with configure_generic_data_nodes

Hi @AlexandreSajus, for the issue with the linter, it will be fixed in the release of Taipy 2.3. You can install the develop version and give it a try.
And regarding the problem of GenericDataNode, indeed it is a documentation problem. We will fix this asap. Thank you


Docker Build Error on Step 7 of Production Dockerfile "/bin/sh: 1: npm: not found"

I was working on containerizing this using the provided dockerfiles and I get an error on Step 7 that npm not found. This looks to be a known issue of the program not being named correctly in certain versions. I've added RUN sudo ln -s /usr/bin/nodejs /usr/bin/node as a last command of the Install nodejs block and I'm still having issues creating the container.

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

ID: a44ec5fe-f5e6-7391-0b03-9e5a8d67c492
Version Independent ID: 45fa95fb-3c76-b451-e087-4b7650a738b3
Content: Build Node.js app with MongoDB on Linux - Azure App Service
Content Source: articles/app-service/containers/tutorial-nodejs-mongodb-app.md
Service: app-service-web
GitHub Login: @cephalin
Microsoft Alias: cephalin

Ok I got this to build. First I changed the install node version to 11
RUN curl -sL https://deb.nodesource.com/setup_11.x | sudo -E bash -
and second I had to add the --force param for each npm cache clean command
Install MEAN.JS Prerequisites
RUN npm install --quiet -g gulp bower yo mocha karma-cli pm2 && npm cache clean --force
RUN NODE_ENV=development npm install --quiet && npm cache clean --force

@phillipgibson really appreciate you bringing this to our attention. We will review and make necessary revisions. Will provide an update soon.


Tweak the page content style

issue #19757

after fix
https://deploy-preview-19771--kubernetes-io-master-staging.netlify.com/docs/reference/generated/kubernetes-api/v1.17/

@Arhell Please consider propose your patch to kubernetes-sigs/reference-docs repo. Target file is: https://github.com/kubernetes-sigs/reference-docs/blob/master/gen-apidocs/static/css/stylesheet.css
API reference is generated from the mentioned tool.

Since the fix is merged upstream. Closing this one.
We need an update to the 1.17 API reference docs.
/close


Model > Secondary Parameters sometimes crashes the React app

This is tricky to reproduce reliably, but the new Secondary Parameters form can crash the whole React app. It seems to happen when adding/removing variables under the Model > Map Variables view. Checking and unchecking the Secondary Parameters can trigger a crash that renders the whole page as an empty white screen.

we should probably have error boundaries so that errors at least show an error message of some sort.
the crash itself seems to be this line attempting to map an undefined value. https://github.com/pkpdapp-team/pkpdapp/blob/3faa1ec73299a4f29b5f1f33105167ed91f9c084/frontend-v2/src/features/results/utils.ts#L36

No data is lost, so refreshing the page will work as a workaround.


Panic: 2.8.0+ When prometheus is asked for a reload we almost every time get  panic: released unknown string

Bug Report
Since 2.8.x when we trigger a prometheus daemon reload the prometheus instance crashes.
the instance sustains a stable 150k datapoints/s stream
We are running on linux stretch amd64.

System information:
Linux 4.18.0-0.bpo.1-amd64 x86_64

Prometheus version:
prometheus, version 2.9.1 (branch: HEAD, revision: ad71f2785fc321092948e33706b04f3150eee44f)
build user:       root@09f919068df4
build date:       20190416-17:50:04
go version:       go1.12.4

Prometheus configuration file:

global:
  scrape_interval:     15s # Set the scrape interval to every 15 seconds. Default is every 1 minute.
  evaluation_interval: 15s # Evaluate rules every 15 seconds. The default is every 1 minute.
  external_labels:
      monitor: 'prometheus'

rule_files:
  - "rules/*.yml"
  - "rules/app/*.yml"

scrape_configs:

[..]

remote_write:
  - url: "http://<redacted>:8000/write"
    queue_config:
      capacity: 1000000
      max_shards: 2000

Logs:

Apr 18 10:39:59 srv01 systemd[1]: Reloading Monitoring system and time series database.
Apr 18 10:39:59 srv01 prometheus[8124]: level=info ts=2019-04-18T10:39:59.297Z caller=main.go:724 msg="Loading configuration file" filename=/etc/prometheus/prometheus.yml
Apr 18 10:39:59 srv01 systemd[1]: Reloaded Monitoring system and time series database.
Apr 18 10:39:59 srv01 prometheus[8124]: ts=2019-04-18T10:39:59.302Z caller=dedupe.go:111 component=remote level=info queue=0:http://lts01/url msg="Stopping remote storage..."
Apr 18 10:39:59 srv01 prometheus[8124]: ts=2019-04-18T10:39:59.459Z caller=dedupe.go:111 component=remote level=info queue=0:http://lts01/url msg="WAL watcher stopped" queue=0:http://lts01/url
Apr 18 10:40:00 srv01 prometheus[8124]: ts=2019-04-18T10:40:00.444Z caller=dedupe.go:111 component=remote level=info queue=0:http://lts01/url msg="Remote storage stopped."
Apr 18 10:40:00 srv01 prometheus[8124]: panic: released unknown string
Apr 18 10:40:00 srv01 systemd[1]: prometheus.service: Main process exited, code=exited, status=2/INVALIDARGUMENT

Just to clarify I believe the string interning was merged to master when 2.8 was out. So it didn't get into a release until 2.9.
@beorn- any chance you have the whole goroutine dump from when the panic happened?

We're also seeing this panic on 2.9.1, but it is after a WAL checkpoint competes

Just to clarify I believe the string interning was merged to master when 2.8 was out. So it didn't get into a release until 2.9.
@beorn- any chance you have the whole goroutine dump from when the panic happened?

nope. but i can make that kind of thing happen with delve.

 0  0x000000000042da70 in runtime.fatalpanic
    at /usr/lib/go/src/runtime/panic.go:690
 1  0x000000000042d4c5 in runtime.gopanic
    at /usr/lib/go/src/runtime/panic.go:565
 2  0x0000000001a16f04 in github.com/prometheus/prometheus/storage/remote.(*pool).release
    at /home/rbaugue/development/prometheus/storage/remote/intern.go:80
 3  0x0000000001a19304 in github.com/prometheus/prometheus/storage/remote.release
    at /home/rbaugue/development/prometheus/storage/remote/queue_manager.go:389
 4  0x0000000001a18a98 in github.com/prometheus/prometheus/storage/remote.(*QueueManager).Stop
    at /home/rbaugue/development/prometheus/storage/remote/queue_manager.go:336
 5  0x0000000001a1ee54 in github.com/prometheus/prometheus/storage/remote.(*Storage).ApplyConfig
    at /home/rbaugue/development/prometheus/storage/remote/storage.go:106
 6  0x0000000001aa2274 in github.com/prometheus/prometheus/storage/remote.(*Storage).ApplyConfig-fm
    at /home/rbaugue/development/prometheus/storage/remote/storage.go:76
 7  0x0000000001a9d725 in main.reloadConfig
    at /home/rbaugue/development/prometheus/cmd/prometheus/main.go:742
 8  0x0000000001aa002d in main.main.func13
    at /home/rbaugue/development/prometheus/cmd/prometheus/main.go:565
 9  0x000000000082d8b7 in github.com/oklog/oklog/pkg/group.(*Group).Run.func1
    at /home/rbaugue/development/prometheus/vendor/github.com/oklog/oklog/pkg/group/group.go:38
10  0x000000000045ca91 in runtime.goexit
    at /usr/lib/go/src/runtime/asm_amd64.s:1337

We are seeing the same thing in v2.9 when asking for a reload

level=info ts=2019-04-19T18:37:05.720Z caller=main.go:724 msg="Loading configuration file" filename=/etc/prometheus/prometheus.yml
ts=2019-04-19T18:37:05.721Z caller=dedupe.go:111 component=remote level=info queue="0:https://<redacted>:8086/api/v1/prom/write?db=foo" msg="Stopping remote storage..."
ts=2019-04-19T18:37:05.905Z caller=dedupe.go:111 component=remote level=info queue="0:https://<redacted>:8086/api/v1/prom/write?db=foo" msg="WAL watcher stopped" queue="0:https://<redacted>:8086/api/v1/prom/write?db=foo"
ts=2019-04-19T18:37:06.013Z caller=dedupe.go:111 component=remote level=info queue="0:https://<redacted>:8086/api/v1/prom/write?db=foo" msg="Remote storage stopped."
panic: released unknown string

goroutine 243 [running]:
github.com/prometheus/prometheus/storage/remote.(*pool).release(0xc00041e9c0, 0x0, 0x0)
	/app/storage/remote/intern.go:76 +0x1a6
github.com/prometheus/prometheus/storage/remote.release(0xc144239680, 0x11, 0x11)
	/app/storage/remote/queue_manager.go:386 +0x104
github.com/prometheus/prometheus/storage/remote.(*QueueManager).Stop(0xc149894680)
	/app/storage/remote/queue_manager.go:333 +0x328
github.com/prometheus/prometheus/storage/remote.(*Storage).ApplyConfig(0xc00018a690, 0xc2a4d36680, 0x0, 0x0)
	/app/storage/remote/storage.go:106 +0x3f4
main.reloadConfig(0x7fff3f37ee23, 0x1e, 0x257bba0, 0xc00093a6f0, 0xc0002e79c0, 0x7, 0x7, 0x0, 0x0)
	/app/cmd/prometheus/main.go:742 +0x285
main.main.func13(0x0, 0x0)
	/app/cmd/prometheus/main.go:565 +0x4ed
github.com/oklog/oklog/pkg/group.(*Group).Run.func1(0xc0000d05a0, 0xc0000d0480, 0xc000284000)
	/app/vendor/github.com/oklog/oklog/pkg/group/group.go:38 +0x27
created by github.com/oklog/oklog/pkg/group.(*Group).Run
	/app/vendor/github.com/oklog/oklog/pkg/group/group.go:37 +0xbe
level=info ts=2019-04-19T18:37:14.492Z caller=main.go:321 msg="Starting Prometheus" version="(version=2.9.0, branch=HEAD, revision=1a9cdbd024fea05a1888c3164058087476cfdc3b)"
level=info ts=2019-04-19T18:37:14.492Z caller=main.go:322 build_context="(go=go1.12.3, user=root@4d7ed54ba6d9, date=20190415-09:06:49)"
level=info ts=2019-04-19T18:37:14.492Z caller=main.go:323 host_details="(Linux 3.10.0-957.5.1.el7.x86_64 #1 SMP Fri Feb 1 14:54:57 UTC 2019 x86_64 <redacted>(none))"
level=info ts=2019-04-19T18:37:14.492Z caller=main.go:324 fd_limits="(soft=1048576, hard=1048576)"
level=info ts=2019-04-19T18:37:14.492Z caller=main.go:325 vm_limits="(soft=unlimited, hard=unlimited)"
level=info ts=2019-04-19T18:37:14.494Z caller=main.go:640 msg="Starting TSDB ..."

IIUC this is closed by https://github.com/prometheus/prometheus/pull/5487, feel free to re-open if I'm wrong.


[certs] rename extensions field to private_extensions for better alignment with spec

@pamaury : just a thought for better clarity / consistency with the X.509 spec, perhaps in a follow up PR we should name the extensions field here private_extensions since the spec states "The X.509 v3 certificate format also allows communities to define private extensions to carry information unique to those communities."  Thoughts?
Originally posted by @timothytrippel in https://github.com/lowRISC/opentitan/pull/22573#discussion_r1569105674

Yes I think it makes sense. My only objection would be that private_extension is a bit long but if you think it's clearer then I am happy to change it.

I think it helps differentiate from other types of extensions that would not be placed in the extensions list.


Deduplicate contract data bumps

Currently we just accumulate all the contract data bumps in a vec and apply them one-by-one in Core. This may cause fees to be double-charged and bumps to be overridden. Instead, we should deduplicate bumps by key and only keep the max value.
This could be done either in the host or in core. Host is preferable as it ensures consistent behavior between core and preflight.

There are some inconsistencies with how bump duration is computed in core and in host; I'll experiment with moving this logic completely to the host side to avoid such inconsistencies.


L.CRS.Simple different circle radius depending on longitude (rounding bug)

How to reproduce

Leaflet version I'm using: 1.3.1
Browser (with version) I'm using: Google Chrome, Firefox
OS/Platform (with version) I'm using: Ubuntu 16.04
Initialize a crs: L.CRS.Simple map
Draw some "Circle"s with the same radius horizontally
Zoom out to make circles small (not happening with big circles/close zoom)

What behaviour I'm expecting and which behaviour I'm seeing
I expect all the circles to have the same size, but they change depending on X position.
This is due to latLngToLayerPoint function rounding, specifically: https://github.com/Leaflet/Leaflet/blob/00cc6ff11972dcc011a2374f175727f03b0f9aa4/src/map/Map.js#L967
With _round(), I randomly get radius values of 3 or 4 depending on longitude position. If I remove the _round(), I get radius of 3.5 for all circles. What I did is to remove the _round() and change the _project function of the Circle class and make the rounding into the final this._radius. That fixed the problem for me:
this._radius = Math.round(this._point.x - map.latLngToLayerPoint(latlng2).x);

Demo
https://plnkr.co/edit/BaUIaVJdEcpuRwM69qRl?p=preview

Can't reproduce. Everything looks fine to me. See https://plnkr.co/edit/ZDVAyxo6axzbv5nUYB49?p=preview

Is there anything I'm missing here?

It is actually happening in your plunker. It does not happen when the circles are large / zoom is close. Please zoom out to make them smaller and you'll notice.

OK, that clears it up. I've also made https://plnkr.co/edit/Buc4ZjhxWyTH3tMoesec?p=preview :

It seems that removing the ._round() would fix the issue, but I'm somewhat worried that doing so would break some old browser, or introduce some flickering. Old browsers (I'm thinking IE9 / IE10) might not play nice with non-round CSS offsets and things like that.

Bumping this issue: Rounding the layer points to their nearest integer causes small layers to massively distort at small zoom levels.
https://github.com/Leaflet/Leaflet/blob/d404fc50b073ba57bf44b0d10873d85871f040a8/src/map/Map.js#L1003-L1006
What is the purpose of rounding the layer point to an integer, performance?
In some use cases, the accuracy is more important than the performance. Can we make this configurable, e.g., similar to smoothFactor if one favors accuracy over performance?
I am happy to send a PR your way when there is a consensus how to approach this issue.

Maybe we can really remove this. Was added with: https://github.com/mohsen1/Leaflet/commit/c739bbff22b604f2c50259ff265416ae1d3ae0ae


chore: require modules instead of import [S3C-332]

@ironman-machine

Hello @electrachong
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "DEFAULT_BRANCH": "master", "SCALITY_S3_BRANCH": "rf/module-imports"}
Please follow http://ci.ironmann.io/gh/scality/Integration/13068 for CI status.

@ironman-machine
SCALITY_UTAPI_BRANCH=chore/S3C-415-removeBabel

Hello @electrachong
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "SCALITY_UTAPI_BRANCH": "chore/S3C-415-removeBabel", "DEFAULT_BRANCH": "master", "SCALITY_S3_BRANCH": "rf/module-imports"}
Please follow http://ci.ironmann.io/gh/scality/Integration/13072 for CI status.

@ironman-machine
SCALITY_UTAPI_BRANCH=chore/S3C-415-removeBabel

Hello @electrachong
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "SCALITY_UTAPI_BRANCH": "chore/S3C-415-removeBabel", "DEFAULT_BRANCH": "master", "SCALITY_S3_BRANCH": "rf/module-imports"}
Please follow http://ci.ironmann.io/gh/scality/Integration/13083 for CI status.

@ironman-machine
SCALITY_UTAPI_BRANCH=chore/S3C-415-removeBabel

Hello @electrachong
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "SCALITY_UTAPI_BRANCH": "chore/S3C-415-removeBabel", "DEFAULT_BRANCH": "master", "SCALITY_S3_BRANCH": "rf/module-imports"}
Please follow http://ci.ironmann.io/gh/scality/Integration/13091 for CI status.

end-to-end passed running with utapi branch:
http://ci.ironmann.io/gh/scality/Integration/13091

@ironman-machine

Hello @electrachong
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "DEFAULT_BRANCH": "master", "SCALITY_S3_BRANCH": "rf/module-imports"}
Please follow http://ci.ironmann.io/gh/scality/Integration/13129 for CI status.

end-to-end passed


Make markdown editing toolbar visible at all times

This PR fixes #11847 - makes the markdown editing toolbar sticky with a longer text cell.
Before - toolbar is only visible at the very top of the cell:

After - toolbar is visible after scroll:

Coverage remained the same at 40.18% when pulling 256e60ca79c885aa7b864b9bff4b2332af4408ec on t-lajian/pinMdToolBar into adfdd569075e7a83c8a8c2c71a1b897648634cd0 on main.


requestAnimationFrame cycle runs forever

Currently, the requestAnimationFrame cycle will never be broken. We should break the cycle (i.e. "cancel" the callback) in willDestroyElement.
See here: https://github.com/emberjs/ember-collection/blob/8bd9cc34304f26a7c2352e5e85db0731907555f5/addon/components/ember-collection.js#L125-L126.

working on this now.


Create issue template

As a contributor to this repository,
I want a template from which I can create new issues
So that when looking at issues, they all follow a consistent standard and aren't missing any information.

This repo has some great example issue templates: https://github.com/stevemao/github-issue-templates

This repo has some great example issue templates: https://github.com/stevemao/github-issue-templates


Add to official "Termux packages" for Android users

https://github.com/termux/termux-packages
reference: https://github.com/termux/termux-packages/blob/master/CONTRIBUTING.md

Nice idea, I just checked it out, do you want me to assign it to you ?

Sorry I'm not a developer. Besides that reading their packaging policy I've a feeling that most likely they'll accept the package if the PR comes from you as the original developer.

Sorry I'm not a developer. Besides that reading their packaging policy I've a feeling that most likely they'll accept the package if the PR comes from you as the original developer.

Sure np assigning it to myself !

I hope they'll accept in official package, alternatively we've https://github.com/termux-user-repository/tur


Module 1 exercises [Kofi Kekeli Amedzro]

KOFI KEKELI _GHANAPOP ASSIGNMENT 1 .pdf
KOFI KEKELI ASSIGNMENT two pop density.pdf

Please "drag & drop" exercise 1 pdf file below.

Please "drag & drop" exercise 2 pdf file below.

Please UPDATE THE TITLE of this "Issue" in the title bar above with your name.

If you haven't done so, please go back to Module 1 and make sure to take
the post-training survey. Participating in surveys is required for receiving
the "GALUP Certificate" by the University of Florida.

Well done, Kofi. You clearly grasped the material outlined in Module 1 and successfully applied it to these exercises. There was a minor issue the coloring on exercise 1, but this can be fixed by ensuring that the correct "reds" color ramp is chosen so that the resulting map resembles the example in the module. Thank you for your participation! Please be sure to fill out the post-Module survey before you begin the next Module.


GRPC Health Checks

Currently agent connectivity to server can be terminated under certain conditions (e.g. no jobs for a while and/or firewall/LB terminating idle connections).  This results in jobs being triggered and sitting in pending until the agent is restarted and "reconnected" to the server.
GRPC health checks could help prevent/correct this issue and make the Drone platform more stable in general.
Discussion regarding this in Discourse: https://discourse.drone.io/t/0-8-1-agent-loses-connection-overnight/864/7
GRPC Health Checks docs: https://github.com/grpc/grpc/blob/master/doc/health-checking.md

The same issue in kubernetes.

I am also seeing this while running in Docker Swarm.

Until we have a patch, it is not recommended to route agent communication through a load balancer or reverse proxy. When I start working on this I will update the issue status, but in the meantime, please feel free to send a patch if you want to expedite a resolution to this issue.


just testing

Bug Report
Which version of the demo you are using? (please provide either a specific
commit
hash
or a specific
release).
Symptom
A clear and concise description of what the bug is.
What is the expected behavior?
What do you expect to see?
What is the actual behavior?
What did you see instead?
Reproduce
Provide the minimum required steps to result in the issue you're observing.
We will close this issue if:

The steps you provided are complex.
If we can not reproduce the behavior you're reporting.

Additional Context
Add any other context about the problem here.

some test comment


JSHint 2.6.0

Update JSHint 2.6.0. Not sure if I am doing the right thing here but I have tried to update to JSHint 2.6.0 as they have es6 fat arrow support amongst other improvements.

Looks good - thank you. Next time feel free to add credit for your PR in the readme :)


Talib and Tulip MFI produce very inaccurate results

Note: for support questions, please join our Discord server

I'm submitting a ...
[x ] bug report
[ ] feature request
[ ] question about the decisions made in the repository

Action taken (what you did)
I made a strategy using the tulip MFI (money flow index) indictor, on debugging the strategy in gekko backtesting I realized the MFI results are very far off from the expected results. To investigate further I tried the talilb MFI. Talib and tulib MFI's are both far off expected results and sometimes output the same and sometimes completely different values.

Expected result (what you hoped would happen)
Have MFI indicator output reliable results, as displayed by the indicators on the exchange where I got my backtesting data from. Bitfinex uses trading-view.com charts, so I assume they are mostly reliable (don't hesitate to correct me if that's known not to be the case)

Actual result (unexpected outcome)
I compared the values with the values given by the mfi indicator on bitfinex with the same parameters for the very same time frames (candles). I realize the candle-data iself (OHCL) from the exchange do not 100% match the candles available in gekko but pretty much. The mfi results however are far off, sometimes not even remotely related to the expected result.

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc)

Backtesting data from bitfinex, EUR-IOT

I made a simple "strategy" to make it easier to reproduce:
var log = require('../core/log');
var strat = {};
strat.init = function() {
	var mfiSettings = {
		optInTimePeriod: 14
	}
	/*TULIP*/this.addTulipIndicator('tulip', 'mfi', mfiSettings );
	/*TALIB*/this.addTalibIndicator('talib', 'mfi', mfiSettings );
}
strat.update = function() {}
strat.log = function() {}
strat.check = function(candle) {

	console.log('candle moment______:',candle.start);
	console.log('candle.close_______:',candle.close);
	console.log('TULIP MFIresult____:',this.tulipIndicators.tulip.result['result']);
	console.log('TALIB MFIresult____:',this.talibIndicators.talib.result['outReal']);
	console.log(candle);
}
module.exports = strat;

I wrote my own MFI indicator for gekko which I'd like to share.
MFI.zip
I'm having it running along with the tulip MFI indicator atm and so far results match 100%. both are still off from the exchange results but it's hard to really know why, because gekko calculates its own "uneven" candle times like 7:18, 7:23, 7:28 etc.
Is there any way to synchronize the start of gekko with the exchange? (I know it's doable in backtesting, but then again, in backtesting the indicator results seem to be off because of the speed that gekko handles candle data - I read some issues on that, have to read more to be sure)

@s5m4  Can friend give you some example to use your indicator?

@s5m4 I've noticed the same issue with the MACD indicator, if you make a strategy with a Talib MACD, a Tulip MACD and a Gekko MACD you'll notice that each results are different.

Any updates? MFI is horribly off

I have tried with multiple exchanges and various MFI algorithms, various history sizes and tried on multiple candle start times. Unfortunately, I am still unable to narrow this down. I am up to date on the development branch
My most recent test was on the 1 min candle. However, I usually test on 5min and 1 hr.
Coin: BTC
Market: USDT
Candle Size: 1min
Exchange: Binance

Note that candles are generated differently (for 5min and up) since Gekko doesn't clamp down the 5 minute intervals on the clock (like 12:00 and 12:05, if the first candle is from 12:01 the next one will be 12:06).
Besides from that, a good starting point would be comparing the candle props (OHCL) from Gekko with those from other platforms. Would you be able to let me know if you spot major differences?
Note that small discrepancies for bitfinex are expected, see #https://github.com/askmike/gekko/pull/2354#issuecomment-407047864 (not related to you, but OP's).

@askmike So what I have figured out, is that the async set up of the 3rd party indicators (so far only MFI) seem to mess things up. If I use my internal MFI (by itself) everything seems to work smoothy. However, if I use a tulip Indicator with my internal MFI both mess up or if I just use the tulipIndicator

Im using tulip ema and still haven't found a way around to match with tradingview, as i believe its buying and on places it really shouldn't. any solutions?


Replace rust-i18n with i18n-embed

As discussed in #1416. From there:

I'm also tempted to just do something akin to your patch, as doing this translation is simple enough that pulling in dependencies may be overkill.

Probably, if strings are to be fairly simple and keep that way. Optimize with phf, even.
Anyway, the new code is here for comparison.
This is a very crude draft with quite some points up for debate: code style and placement, workaround for locale override with config value (there's a comment about this), structure of i18n resources, and MSRV (enabling std::sync::LazyLock, but actually not very relevant to i18n).
Good news is this does not significantly affect compiled size (even down a few kilos actually).

Thanks, I'll review this properly later today.
Once thing worth doing is re-introducing the locale::t! "wrapper" macro such that no changes are needed at the call site (i.e. everything in frontend::render).
I tested this locally and it seemed to work ok:
#[macro_export]
macro_rules! t {
    ($($all:tt)*) => {
        i18n_embed_fl::fl!($crate::locale::LANGUAGE_LOADER, $($all)*)
    }
}

Indeed, that'll remove quite some noise. Though fl! returns String, so some invocations still need to be adjusted.

@nc7s I've pushed some WIP commits to this PR (we can refine these and squash later).

wip: remove unused sys-locale crate

No longer used so I removed it.  I haven't reviewed the replacement logic yet.

wip: remove Cow from several methods

See my comment above re: removing Cow and what that reveals about the way the i18n_embed crate works.

wip: use OnceLock instead of LazyLock

We can use OnceLock (stable on 1.70, Jun 2023) instead of LazyLock (1.80, Jul 2024) to avoid the MSRV bump, as the latter is a little bit too recent (thinking about package maintainers here!).

wip: move i18n into crates/trippy-tui and delete old locales

As the translations are strictly a TUI concern I'd prefer this to live in the trippy-tui crate.  It was quite fiddly to move, but it seems to work.  It seems rust-embed handles differently between debug and release builds but has a "debug-embed" to align them, which I briefly tried but didn't use.
I'm find it confusing to have a i18n.toml config file which defines the assets_dir and having to specify it in #[folder = "i18n"].  I did look briefly if there was a way to avoid this but didn't see anything.
I also removed the old locale directory in this commit.

@nc7s on the fluent ftl files, do you know if it is possible to combine them into a single multi-language file?  This has pros and cons but is handy for generating placeholder translations for new terms for all languages quickly as it plays well with AI tools.
If not, can we name all file as ${lang}_ftl and place them in a single directory? (aside: is there any significance to the name trippy-tui.ftl or is it arbitrary?)

Thanks for the detailed review and code.

wip: move i18n into crates/trippy-tui and delete old locales
As the translations are strictly a TUI concern I'd prefer this to live in the trippy-tui crate. It was quite fiddly to move, but it seems to work. It seems rust-embed handles differently between debug and release builds but has a "debug-embed" to align them, which I briefly tried but didn't use.

I regret to admit it's because I simply followed its docs, which told me to put it in the root. :>

I'm find it confusing to have a i18n.toml config file which defines the assets_dir and having to specify it in #[folder = "i18n"]. I did look briefly if there was a way to avoid this but didn't see anything.

The former is for the i18n-embed crate, the latter for rust-embed. The former does not actually embed files itself, even with that word in the name.

@nc7s on the fluent ftl files, do you know if it is possible to combine them into a single multi-language file? This has pros and cons but is handy for generating placeholder translations for new terms for all languages quickly as it plays well with AI tools.

As shown in rust-i18n docs:
# Use the fluent localization system.
[fluent]
# (Required) The path to the assets directory.
# The paths inside the assets directory should be structured like so:
# `assets_dir/{language}/{domain}.ftl`
assets_dir = "i18n"

I'm afraid we have to manually reimplement some of the set code to support an alternative layout, e.g. building FluentBundles ourselves.

If not, can we name all file as ${lang}_ftl and place them in a single directory? (aside: is there any significance to the name trippy-tui.ftl or is it arbitrary?)

As shown above, trippy-tui.ftl is just {domain}.ftl, which we do have control by manually building a FluentLanguageLoader (not using the fluent_language_loader! macro).

Maybe this is a good use case to implement a few bench marks?

I used its thread safe version, std::sync::LazyLock, but it requires bumping MSRV to 1.80, @fujiapple852 worried it's too new and changed "back" to std::sync::OnceLock, which was introduced in 1.70, lower than current MSRV 1.76. It has the cost of lock, but it seems we need it for Sync:
error[E0277]: `OnceCell<FluentLanguageLoader>` cannot be shared between threads safely
  --> crates/trippy-tui/src/locale.rs:12:29
   |
12 | pub static LANGUAGE_LOADER: OnceCell<FluentLanguageLoader> = OnceCell::new();
   |                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `OnceCell<FluentLanguageLoader>` cannot be shared between threads safely
   |
   = help: the trait `Sync` is not implemented for `OnceCell<FluentLanguageLoader>`
   = note: if you want to do aliasing and mutation between multiple threads, use `std::sync::OnceLock` instead
   = note: shared static variables must have a type that implements `Sync`

For more information about this error, try `rustc --explain E0277`.
error: could not compile `trippy-tui` (lib) due to 1 previous error

Oh sorry I guess I should have remember it needed to go across threads. Yes I think the lock cost is less than creating the string each time but we'd probably need to benchmark it to really know. And yes using OnceLock would also be fine.

Arguably we could .leak() a String into it, since the locale is almost always set only once per run, but we still need to figure out how to write into a static without OnceLock or the like.

I think I missed something, why can't we use OnceLock?

Uh that was intended as an idea for further optimization, OnceLock is fine per se.

@nc7s I pushed another wip commit, this is mostly about making the i18n impl hidden (to the extent possible) inside the locale module.  I also added some tests.

Closed in favour of https://github.com/fujiapple852/trippy/pull/1428


Remove para generation on dt items

Fixes #914
Note the change to the reference test files (now a little shorter). Esp. how line-wrapping for multi-line text is preserved, and paragraphs are still used when subsequent empty-line separated text is found. Also not, paragraph insertion will still be done if a bullet, numbered item, or dt/dd has only a newline as content:
  *
     wrap this in a paragraph

Update to be scoped to <dt> only.

So I really don't like the code approach here, but I am happy for the feature. I'll rewrite tomorrow and close this when I do it.

And done. This is now performed as a cleanup step at the end - if a markdown-generated <dt> ends up with a single <p> child and nothing else, I remove the <p> wrapper and push the children up into the <dt>.


Correct description of OAuth2 preferred username claims config

Since 3.10/rabbitmq/rabbitmq-server#7458, preferred_username_claims has accepted a list of claim names rather than a comma-separated string.

@iinuwa Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@pivotal-cla This is an Obvious Fix

@iinuwa This Pull Request contains an obvious fix. Signing the Contributor License Agreement is not necessary.


Remove CSCC Alpha Support

We still have code that maintains backward compatibility for the alpha API. These should be removed when the alpha API support is discontinued from the platform.  Should also work with the platform team that all Forseti customers are migrated.

#2619


Inconsistent red triangles while when I click on Suggest Annotation

Steps to replicate:

Create a new project
Upload the attached file
Click on Suggest Annotation
No red triangles in column H, I

Change Region as shown

Notice the red triangles
Change region back to start from H2, the red triangles are still there
They should have been there from the beginning as there is no property associated
cdis_usa_japan.csv

yes, suggesting annotation doesn't actually submit the annotation (and get error checks) until the user's next action (in this case, changing the region).  I can change it to submit the annotation from the get-go.


Impossible to load image

coreos01 core # docker load -i /tmp/oraclelinux-7.1.tar.xz
FATA[0005] Error response from daemon: open /var/lib/docker/tmp/docker-import-913281699/repo/boot/json: no such file or directory
i am on CoreOS 695.2.0

You can't load the oraclelinux-7.1.tar.gz, it's not an export, it's a root filesystem. You need to use the associated Dockerfile and build FROM it.


[QUESTION] 'SkiaSharp.SKImageInfo' threw an exception

Hi..
I have read this kind of error but I havent the solution..
First of all I m using .net 5.0.408 + Angular 13 (node 14.17.1)
My project worked fine in windows and CentOS 7 (x86-64 Kernel Linux 3.10.0) mounted in VSP contabo.
Suddenly, the project doesnt work in CentOS 7 (create PDF), even, I havent touch this part of the program, appear the following error.
"
2022-08-20 00:58:10.2711 |             ConfluxApiOperator |  WARN | Exception | StandarViewForWearEquipmentMaintenanceView() | Message:[The type initializer for 'SkiaSharp.SKImageInfo' threw an exception.],Stack:[   at SkiaSharp.SKImageInfo..ctor(Int32 width, Int32 height)
"
always the declaration was:
PackageReference Include="EPPlus" Version="<IP_ADDRESS>"
PackageReference Include="Magick.NET-Q8-AnyCPU" Version="7.23.2"
PackageReference Include="MailKit" Version="3.0.0"
PackageReference Include="PdfSharp" Version="1.50.5147"
PackageReference Include="PDFsharp-MigraDoc" Version="1.50.5147"
PackageReference Include="SixLabors.ImageSharp" Version="1.0.4"
PackageReference Include="SkiaSharp" Version="2.80.3"
PackageReference Include="SkiaSharp.NativeAssets.Linux" Version="2.80.3"

I tested change the following:
PackageReference Include="SkiaSharp" Version="2.80.3"
PackageReference Include="SkiaSharp.NativeAssets.Linux" Version="2.80.3"

to
PackageReference Include="SkiaSharp" Version="2.88.1"
PackageReference Include="SkiaSharp.NativeAssets.Linux" Version="2.88.1"

or to
PackageReference Include="SkiaSharp.NativeAssets.Linux.NoDependencies" Version="2.88.1"

but nothing works, I have to say I dont manage programing, but I try to find a solution.
Thanks for any hint
Ricardo

I have the same issue trying to run samples

No, I didnt. I skipped it for a while


UUID doesn't work with SimpleObject?

@sunli829 I'm adopting new-datasource into my project and I just noticed that Uuid doesn't work with the SimpleObject macro. Did this happen recently?
This is the compiler error I am seeing.
the trait `async_graphql::base::OutputValueType` is not implemented for `uuid::Uuid`

I've solved this problem on the main branch, and now I'm going to merge the new-datasource.

I have merged, uuid dependency was once an option, now it is a required option, but some #[cfg(feature = "uuid")] is not removed.

I thought that might be the problem. My project is compiling now.

@sunli829 @phated should uuid be required?

@sunli829 @phated should uuid be required?

I used uuid in Logger. 😁

Greetings!
I'm bringing it back, because can't use uuid::Uuid with SimpleObject:
[dependencies]
uuid = { version = "1.0.0-alpha.1", features = ["v4", "serde"] }
async-graphql = { version = "3.0.18", features = ["uuid"] }

#[derive(async_graphql::SimpleObject)]
struct Foo {
    uuid: uuid::Uuid,
}

fn main() {
    //
}

error[E0277]: the trait bound `Uuid: OutputType` is not satisfied
  --> src/main.rs:1:10
   |
1  | #[derive(async_graphql::SimpleObject)]
   |          ^^^^^^^^^^^^^^^^^^^^^^^^^^^ the trait `OutputType` is not implemented for `Uuid`
   |
   = note: required because of the requirements on the impl of `OutputType` for `&Uuid`
note: required by a bound in `async_graphql::OutputType::resolve`
  --> /Users/asinotov/.cargo/registry/src/github.com-1ecc6299db9ec823/async-graphql-3.0.18/src/base.rs:81:35

Ok, my mistake, falling back to uuid = "0.8.2" did all fine.