Weird display issue in IE9, duplicated on Win7 and WinVista

So, I'm using Select2 with the well-known Inspinia theme (https://wrapbootstrap.com/theme/inspinia-responsive-admin-theme-WB0R5L90S), and I'm running into a weird issue in IE9:

As you can see, the dropdown is basically all but missing, and it doesn't seem as if much of the usual styling has been applied.
The weird thing is that Select2 is working fine on the Select2 demo site, as well as in the Inspinia demos, so it's obviously in my particular setup.  There are no errors loading and CSS or JS files, no console errors.  I'm having a bear of a time figuring out what could possibly be causing this.  Has anyone here run into anything similar?

Possibly a duplicate of #4780.  Have you tried setting dropdownParent?  See https://select2.org/dropdown#dropdown-placement

Please feel free to comment if you have any more insight, and we can reopen the issue.


Script installed Fusion 360 doesn't open up a browser to log in.

Describe the bug
Even with the latest version of the installation available at the time of writing, I can't get to log into fusion 360.
To Reproduce
Install Fusion 360 through the wine script and attempt to log in.
Expected behaviour
After clicking into the login button, the program opens up a browser window where I can log in.
Screenshots
Desktop (please complete the following information):

Latest at the time of writing
Nvidia MX250 + nvidia driver 535
LMDE 6
Cinnamon
DXVK

Additional context
Any help on how to resolve this issue would be greatly appreciated.

I was also having this issue with Ubuntu 24.04 but resolved it by making sure I had the deb version of Firefox installed. Not a expert but what browser are you using? And while it may not help me, attaching log files will be sure to help someone else help you.

I also have this issue on fedora 40, and intsalling the rpm version of firefox didn't fix it. Where are log files found?

I was also having this issue with Ubuntu 24.04 but resolved it by making sure I had the deb version of Firefox installed. Not a expert but what browser are you using? And while it may not help me, attaching log files will be sure to help someone else help you.

This is the answer!

I was also having this issue with Ubuntu 24.04 but resolved it by making sure I had the deb version of Firefox installed. Not a expert but what browser are you using? And while it may not help me, attaching log files will be sure to help someone else help you.

Thanks you a lot man!
that did work!

How to Install Firefox as DEB on Ubuntu (Not Snap): https://www.omgubuntu.co.uk/2022/04/how-to-install-firefox-deb-apt-ubuntu-22-04


Create a terse navigator mode

Current navigator mode is full.
Create a terse variant that assigns two functions to most buttons
For example, on page 2 of a bank, preset C would be "previous page" and preset F would be "next page".

Needs to be designed.

Basic idea: page only uses one button instead of two:
The button has a short press (release), or a long press
The menu bank, page 1, the navigator takes you to page 2
On other banks, page 1, the navigator takes you home (long), or to page 2
On other pages, short takes you up, long takes you down

Completed in 0.1.2


juypter notebook keybindings hell!!! disappearing cells!

Does this issue occur when all extensions are disabled?: Yes

VS Code Version:
all
OS Version:
all

Steps to Reproduce:
I was hitting CTRL+Z outside of the cell when I thought I was inside the cell (usually because running current cell makes you lose cell focus). Sometime it just "undid" the last created cell somewhere else in my notebook, and I actually lost some cells because I didn't realized right away what happened and just continued working.
https://stackoverflow.com/questions/61603833/how-to-recover-accidentally-deleted-cells-in-jupyter-notebook
the workaround...
https://stackoverflow.com/a/69421121
or..
Redefining the Keyboard Shortcuts worked for me. I removed the CTRL+Z shortcut when I'm not inside a cell (you can still access it with the menu Edit > Undo). I did the same for CTRL+SHIFT+Z, and so on.
To do this, I added theses rules to my keybindings.json:
{ "key": "ctrl+z", "command": "-undo" },
{ "key": "ctrl+z", "command": "undo", "when": "!notebookEditorFocused || inputFocus" },
{ "key": "ctrl+shift+z", "command": "-redo" },
{ "key": "ctrl+shift+z", "command": "redo", "when": "!notebookEditorFocused || inputFocus" },
{ "key": "ctrl+y", "command": "-redo" },
{ "key": "ctrl+y", "command": "redo", "when": "!notebookEditorFocused || inputFocus" },
I also removed the Z shortcut from Jupyter extension because I don't like it.
{ "key": "z", "command": "-undo", "when": "notebookEditorFocused && !inputFocus" },
and you guys closed this issue...
the closed issue :(  https://github.com/microsoft/vscode-jupyter/issues/1998#issuecomment-614763069
any chance of this being fixed?

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


Define uninitialised array element access

Problem
During ACIR gen the current implementation of memory (once merged) will throw an error when encountering a load instruction for an array element that hasn't been initialised.
Happy Case
The current behaviour is probably the safest approach, but its nonetheless worth revisiting further down the road once we better understand the requirements of dynamic arrays.
Alternatives Considered
No response
Additional Context
No response
Would you like to submit a PR for this Issue?
No
Support Needs
No response

Backlink: https://github.com/noir-lang/noir/pull/1455/files#r1210854107

@guipublic since dynamic arrays have been implemented, can you revisit this?

All arrays are initialised in noir, when they are declared. So loading an initialised part of an array is only possible for out-of-bounds indices, which cannot be avoided when we have witness indices.
However, in that case the prover will not be able to generate the proof and we will report an error.
We could add a range-check before any array access to prevent out-of-bound errors on the prover and then report better errors to the user.

Closing this issue since I think we have a good answer for it. Arrays themselves can never be uninitialized but out of bounds accesses are still possible. For these cases we issue a compiler error.


[Bug]: Half-cell, particle distribution DFN fails during charge experiments

PyBaMM Version
23.5
Python Version
3.9.18
Describe the bug
Hello,
When i create a half-cell DFN model and I try to include the particle distribution for the positive electrode, it wouldn't take any charge procedure. It only discharges, but the charge always fails.
When i do exactly the same but without including the particle distribution everything works fine.
Steps to Reproduce
import pybamm
Create the model using the particle size distribution option as well as the half cell configuration.
options = {"particle size": "distribution","working electrode": "positive" }
MPDFN_model = pybamm.lithium_ion.DFN(options=options)
Import half cell NMC parameters
param_nmc = pybamm.ParameterValues("Xu2019")
Create size distribution for the positive particles
param_nmc_MP=pybamm.get_size_distribution_parameters(param_nmc, electrode="positive")
Load a simple experiment
experiment = pybamm.Experiment(["Discharge at C/25 until 3.5 V", "Charge at C/25 until 4.2 V"])
Load everything (regardless of the solver used the result and error is the same)
MP_sim_pOCV = pybamm.Simulation(MPDFN_model, parameter_values=param_nmc_MP, solver=pybamm.CasadiSolver(atol=1e-3, rtol=1e-3, mode="safe"), experiment=experiment)
Simulate. The error always arise in the next step.
MP_sol_pOCV = MP_sim_pOCV.solve()
The error always gives a problem when charging, when i just discharge is ok.
Relevant log output
---------------------------------------------------------------------------
NotImplementedError                       Traceback (most recent call last)
Cell In[7], line 3
      1 # MP-DFN
      2 MP_sim_pOCV = pybamm.Simulation(MPDFN_model, parameter_values=param_nmc_MP, solver=pybamm.CasadiSolver(atol=1e-3, rtol=1e-3, mode="safe"), experiment=experiment)
----> 3 MP_sol_pOCV = MP_sim_pOCV.solve()

File ~\.conda\envs\PyBaMM_env\lib\site-packages\pybamm\simulation.py:725, in Simulation.solve(self, t_eval, solver, check_model, save_at_cycles, calc_esoh, starting_solution, initial_soc, callbacks, showprogress, **kwargs)
    723 npts = max(int(round(dt / op_conds.period)) + 1, 2)
    724 try:
--> 725     step_solution = solver.step(
    726         current_solution,
    727         model,
    728         dt,
    729         npts=npts,
    730         save=False,
    731         **kwargs,
    732     )
    733 except pybamm.SolverError as error:
    734     if (
    735         "non-positive at initial conditions" in error.message
    736         and "[experiment]" in error.message
    737     ):

File ~\.conda\envs\PyBaMM_env\lib\site-packages\pybamm\solvers\base_solver.py:1165, in BaseSolver.step(self, old_solution, model, dt, npts, inputs, save)
   1163         model.y0 = old_solution.all_ys[-1][:, -1]
   1164     else:
-> 1165         _, concatenated_initial_conditions = model.set_initial_conditions_from(
   1166             old_solution, return_type="ics"
   1167         )
   1168         model.y0 = concatenated_initial_conditions.evaluate(
   1169             0, inputs=model_inputs
   1170         )
   1172 set_up_time = timer.time()

File ~\.conda\envs\PyBaMM_env\lib\site-packages\pybamm\models\base_model.py:576, in BaseModel.set_initial_conditions_from(self, solution, inplace, return_type)
    574 if isinstance(var, pybamm.Variable):
    575     try:
--> 576         final_state = solution[var.name]
    577     except KeyError as e:
    578         raise pybamm.ModelError(
    579             "To update a model from a solution, each variable in "
    580             "model.initial_conditions must appear in the solution with "
    581             "the same key as the variable name. In the solution provided, "
    582             f"'{e.args[0]}' was not found."
    583         )

File ~\.conda\envs\PyBaMM_env\lib\site-packages\pybamm\solvers\solution.py:510, in Solution.__getitem__(self, key)
    507     return self._variables[key]
    508 else:
    509     # otherwise create it, save it and then return it
--> 510     self.update(key)
    511     return self._variables[key]

File ~\.conda\envs\PyBaMM_env\lib\site-packages\pybamm\solvers\solution.py:470, in Solution.update(self, variables)
    468         model._variables_casadi[key] = var_casadi
    469     vars_casadi.append(var_casadi)
--> 470 var = pybamm.ProcessedVariable(
    471     vars_pybamm, vars_casadi, self, cumtrapz_ic=cumtrapz_ic
    472 )
    474 # Save variable and data
    475 self._variables[key] = var

File ~\.conda\envs\PyBaMM_env\lib\site-packages\pybamm\solvers\processed_variable.py:105, in ProcessedVariable.__init__(self, base_variables, base_variables_casadi, solution, warn, cumtrapz_ic)
    102     self.initialise_2D()
    103 else:
    104     # Raise error for 3D variable
--> 105     raise NotImplementedError(
    106         "Shape not recognized for {} ".format(base_variables[0])
    107         + "(note processing of 3D variables is not yet implemented)"
    108     )

NotImplementedError: Shape not recognized for 48230.0 * y[0:12000] (note processing of 3D variables is not yet implemented)

Ok, i have seen that the error is general for all the particle distribution implementations. No DFN + particle distribution works when it has to do a charge process. I imagine that is a well-known issue and there are probably people working on that.

Thanks for raising. The issue is with post-processing of 3D variables. Duplicate of https://github.com/pybamm-team/PyBaMM/issues/1549


WIP: QE v7.1 with Elpa support

Checklist

[x] Used a personal fork of the feedstock to propose changes
[] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

The QE release source has been changed to Gitlab.
Elpa support has been added to the build.

Can we add LibXC support too for the Linux case? It appears they build Fortran bindings in Linux now.
The unchecked checkboxes up top have been left alone since I can't intelligently decide on what is the correct choice.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@jan-janssen All but one test seems to be passing, so maybe this can get a review?

Hi @Chronum94 , thanks for the contribution!
It seems to me that the linux build fails because it does not find average.x anymore (not entirely sure?).
Could you check whether that binary does no longer exist in 7.1?
If not, then the corresponding check can be removed.
That the build on osx is timing out seems a bit more worrying, I guess this has to do with the introduction of ELPA.
Also, the test suite on Linux seems to take significantly longer now (2800s vs 1800s before - this can also depend on the runner but it would warrant some benchmark).

Would this be a good opportunity to enable a few more add-ons? I had pw2qmcpack in mind. https://github.com/QMCPACK/pw2qmcpack Suggests that it's just a change to the CMake build line.

I suggest you open a separate PR for this once we've merged this one


Add maintainer list

@yankay @hanxiaop @nicole-lihui @dddddai @bartsmykla  @windsonsea
Please add your email addresses in the comments.

<EMAIL_ADDRESS>Thanks!

Codecov Report

Merging #255 (1dc927b) into main (6f171ac) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #255   +/-   ##
=======================================
  Coverage   40.33%   40.33%
=======================================
  Files           7        7
  Lines         419      419
=======================================
  Hits          169      169
  Misses        236      236
  Partials       14       14

Flag
Coverage Δ

unittests
40.33% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

<EMAIL_ADDRESS>   Thanks


Please support Apache Arrow Frame compatibility

Adding support for Apache Arrow would greatly increase the interoperability between application developers and data scientists. https://arrow.apache.org/
It would be much more efficient to share data structures between dataframe-ec and many of the other dataframe like frameworks. It would also allow python users to move their work to Java for the more memory intensive operations.
There is already a Java library for Arrow.
https://arrow.apache.org/docs/java/
https://central.sonatype.com/search?q=g:org.apache.arrow  v:17.0.0&smo=true
Thanks for the great work!

Thank you for opening the issue. Will look into this. Note that it will be a separate project.

Support for Apache Arrow is available in this repo. Note that the initial implementation is just a basic data frame converter to/from VectorSchemaRoot.


Track linkage between data package properties and established standards

@pschumm "linkage between these metadata properties and other established standards such as Dublin Core" is true for all properties in Data Package and are maybe better defined at the common dictionary level, so they apply to all Data Package elements that use them. In Camtrap DP, I have added those as skos:exactMatch (or alike) properties, see here. Maybe we should open an issue to do discuss this further?

Originally posted by @peterdesmet in https://github.com/frictionlessdata/datapackage/issues/63#issuecomment-2109525613

Specifically, the proposal here is to:

Determine whether additional metadata properties should be defined at the common dictionary level for consistency and maintainability, so that they apply to all data package elements that use them (as suggested by @peterdesmet above)
Add to those definitions linkage to established standards such as the Dublin Core or others (cf. what @peterdesmet has done in Camtrap DP)

Note that (2) would really help when pushing greater use of Frictionless within NIH-funded (and related) initiatives and projects.
I don't have time to work on this right now, but will do so later on. This issue is intended to serve as a tickler for that, but also for anyone who may wish to contribute to this in the meantime (which would be terrific).

Note that (2) would really help when pushing greater use of Frictionless within NIH-funded (and related) initiatives and projects.

Agreed! I don't have bandwidth for this either atm, but would be happy to help out later on as well.
As you say, I think the ability to link to Dublin core especially would be a great selling point in our eventual publications to the NIH et al. audience.


Add test Infinispan server SSL/TLS secure connection

Test secure connection with Infinispan server.
Client and server use the same keystore/truststore file for authentication.
Native mode is working correctly. Secure communication was checked.
The first idea was to update the existing module 008-infinispan-getting-started but through Testcontainers there was an issue with the TLS connection (server refused to send TLS Server Hello message).
Moreover, the new module does not require client authentication on the server side through "username" and "password" parameters (i.e. the primary case in the 008-infinispan-getting-started module), therefore I stick to the new module creation

Surpassed by https://github.com/quarkus-qe/beefy-scenarios/pull/49


Feature/zpool basics

Codecov Report

Merging #2 into master will increase coverage by 4.26%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master       #2      +/-   ##
==========================================
+ Coverage   83.93%   88.19%   +4.26%
==========================================
  Files           4        2       -2
  Lines         193      161      -32
==========================================
- Hits          162      142      -20
+ Misses         31       19      -12

Impacted Files
Coverage Δ

src/zpool/topology.rs
0% <0%> (ø)
:arrow_up:

libzfs_core-sys/src/lib.rs

src/zpool/mod.rs

src/zpool/vdev.rs
96.59% <0%> (+2.44%)
:arrow_up:

Continue to review full report at Codecov.

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


Keystone (V2): Get Role by ID

Internal support added; no endpoint support though

Model: openstackinabox.models.keystone.model.db.roles


v0.7.0_04: Chart is disturbed by changing the orientation

SEVERITY: Major
MODULE: Bubble Chart
PLATFORM: Windows 7 / Chrome 45.0
RELEASE: v0.7.0
STEPS TO REPRODUCE:

Navigate URL: http://static.gapminderdev.org/vizabi/release/v0.7.0/preview/bubblechart.html
Bubble chart page will be loaded
Click on the full screen button under RESPONSIVENESS
Click play button
Click Portrait view before stopping the movement of the slider ball
Chart view is changed to Portrait view
Slider ball is stopped
Note that chart is disturbed after changing the orientation

ACTUAL RESULTS:
Chart is disturbed by changing the orientation from full screen to portrait view
EXPECTED RESULTS:
Chart should not be disturbed by changing the orientation
SCREENSHOT:

WHERE:
the problem is within BubbleChart component, see bubblechart-component.js
The events are produced here:
L81      'change:time:value': function () {
L375     this.on("resize", function () {

As you can see, the events are correct, but the effect is wrong.
Each of the events ('change:time:value' and "resize") is working correctly when on it's own, also the zoom feature works when on it's own
SOLUTIONS:
you'll need to discover the interplay between the two events AND ZOOM FEATURE, and resolve it in such a way that nothing else breaks. Most likely, the zoom function is called with wrong parameters or old parameters...
EXTRA:
you may also test the interplay of other events, like trying all the crazy stuff while time is playing

the above fixed the issue

@k6Labz please check the develop if the issue still persists
http://static.gapminderdev.org/vizabi/develop/preview/bubblechart.html

Retest Result: Passed
Environment: Develop branch - http://static.gapminderdev.org/vizabi/develop/preview/bubblechart.html


[bug]/tapdb: proof storage clobber error for postgres backend

Background
This failure has started to pop up on itests for the postgres backend:
2024-06-12 16:42:33.793 [INF] GRDN: Received new proof file for asset ID 9bc313ea555c28227c86fa4a2b90f54dff46b14db4bbc56bd5d5e2e4dc3af34f, version=0,num_proofs=3
2024-06-12 16:42:33.807 [INF] FRTR: Marking parcel (txid=80bf98b4af11c552c95557806afa79468edec7b0a947f2c7b58306b0d4df4211) as confirmed!
2024-06-12 16:42:33.814 [ERR] FRTR: unable to transfer receiver proof: unable to log parcel delivery confirmation: failed to confirm transfer: unknown postgres error: ERROR: more than one row returned by a subquery used as an expression (SQLSTATE 21000)

It can be seen as a test failure in this itest run: https://github.com/lightninglabs/taproot-assets/actions/runs/9486428727/job/26140728303
    --- FAIL: TestTaprootAssetsDaemon/multi_address (13.48s)

The issue appears to be with this query: https://github.com/lightninglabs/taproot-assets/blob/51e3512464e1efbed2abb6b3ea50f26fa41802f5/tapdb/sqlc/queries/assets.sql#L671-L691
If the CTE for target_asset returns more than one asset_id, then this issue will be triggered. AFAICT, sqlite will just take the very first asset ID.
If we look at the table, we see that asset_id here is intended to be unique: https://github.com/lightninglabs/taproot-assets/blob/51e3512464e1efbed2abb6b3ea50f26fa41802f5/tapdb/sqlc/migrations/000002_assets.up.sql#L245-L256
This appears to be the root of the issue, as if you insert proofs for two diff script keys, but the same asset ID, then behavior is undefined across the two DB backends. However, this is only an issue for the db based proof file storage. The file based storage uses a full path of the outpoint+assetID+scriptKey (prev ID 3-tuple). The Universe based storage uses something similar.
Most sub-systems end up using a MultiArchive that's based on some or all the proof storage backends, which my answer why this issue has been hidden for some time.
Suggested Fix
First we need to get a better feel of the impact. When we send out using the ChainPorter, the file based proofs are updated first, then later the DB proofs once proofs are delivered.
Ultimately, I think we need a DB migration here to add the outpoint+script key as a composite 3-tuple primary key, similar to what we've done elsewhere.
Steps to reproduce
Run make itest icase=multi_address on postgres.
Expected behavior
Should pass.
Actual behavior
Fails.

It doesn't fail consistently for me. About 50% of the time the test passes.

It doesn't fail consistently for me. About 50% of the time the test passes.

Weird...

Current suspicion is that the CTE (WITH clause) somehow behaves differently when it comes to transaction serialization.


Change in kube-batch name to volcano

Kube-Batch has been renamed to Volcano, so Doc changes has been made in this PR
https://github.com/kubernetes-sigs/volcano/issues/761
Preview: https://github.com/thandayuthapani/website/blob/master/content/docs/other-guides/job-scheduling.md

This change is

/cc @k82cn

/hold
Let's hold this PR until we have a release.

@k82cn Just checking on the status of this PR - is the related code released yet?

Replaced by https://github.com/kubeflow/website/pull/741 :)


Serial devices should not propagate an exception for communications errors during normal operation.

Even if our program and hardware were perfect, we'd see occasional communications just from electrical noise.
During connection or configuration, communications errors should be fatal, but during normal operation, we should just report exceptions and not terminate the program.

Typically, if there's a comm error the device needs to be reset. Not
always, but often. So this may not be possible. But I'd be happy to be
proven wrong.
On Tue, Aug 29, 2017 at 4:51 AM, Tom Swirly<EMAIL_ADDRESS>wrote:

Even if our program and hardware were perfect, we'd see occasional
communications just from electrical noise.
During connection or configuration, communications errors should be fatal,
but during normal operation, we should just report exceptions and not
terminate the program.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/issues/413, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AA6a6q967rMRDJN56Pk86eaoWl3Xif34ks5sc9EvgaJpZM4PFk2h
.

Is there a way to programmatically reset an AllPixel?
We can't cause any harm by relentlessly retrying in software when a reset is needed, though... right?

It happens automatically when configuring the AllPixel but only if the
configuration changes. There's no simple "RESET" command that can be sent.
And you wouldn't want to. The EEPROM has a limited life and doing that all
the time would decrease that.
Also, the problem isn't the AllPixel ;) Is the linux serial stack and/or
power issues.
On Sat, Feb 17, 2018 at 5:03 AM, Tom Swirly<EMAIL_ADDRESS>wrote:

Is there a way to programmatically reset an AllPixel?
We can't cause any harm by relentlessly retrying in software when a reset
is needed, though... right?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/issues/413#issuecomment-366430771,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6a6i8l-efeUXLerFzgs5HTtelFHPBzks5tVqQCgaJpZM4PFk2h
.


SPIN Algorithm

What does this PR do ?
Implements the SPIN algorithm into Nemo Aligner
Changelog

Please update the CHANGELOG.md under next version with high level changes in this PR. (done)

Usage

You can potentially add a usage example below

# Add a code snippet demonstrating how to use this

Before your PR is "Ready for review"
Pre checks:

[X] Make sure you read and followed Contributor guidelines
[ ] Did you write any new necessary tests?
[ ] Did you add or update any necessary documentation? Make sure to also update the NeMo Framework User Guide which contains the tutorials

Checklist when contributing a new algorithm

[X] Does the trainer resume and restore model state all states?
[X] Does the trainer support all parallelism techniques(PP, TP, DP)?
[X] Does the trainer support max_steps=-1 and validation?
[X] Does the trainer only call APIs defined in alignable_interface.py?
[X] Does the trainer have proper logging?

Additional Information

Related to # (issue)

Oh, also just a note that we'll need CI as well as documentation for this new algorithm. I don't remember exactly how to do these so please synch with @gshennvm for this.

Oh, also just a note that we'll need CI as well as documentation for this new algorithm. I don't remember exactly how to do these so please synch with @gshennvm for this.

The CI will come after the PR is merged because it needs to get merged for testing the new CI components. I will work on the documentation this week.

Documentation has been added


E-Mail Adress not working

The E-Mail-Address<EMAIL_ADDRESS>is not working:

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

ID: 0aea4662-a077-ac83-07bc-137033c20f06
Version Independent ID: 6891063a-9946-5572-99ff-3cc1c0193045
Content: Support for the Azure Education Hub
Content Source: articles/education-hub/educator-service-desk.md
Service: azure-education
GitHub Login: @v-dihans
Microsoft Alias: rymend

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

@rymend the DL for the Educator Services Desk is no longer active. Would you be able to update this article with the correct link?


Consider creating an FAQ page in the User Guide

Is your feature request related to a problem? Please describe.
As with any software package with sufficiently large number of users, some usage questions get asked again and again.  Giving the askers the benefit of the doubt that they did some searching before posting their question, I will vouch that search engines are not always very useful if you don't know the magic terms of art to search for.
Describe the solution you'd like
An FAQ page for things that get asked frequently but might not be found easily anywhere else in our docs.
Off the top of my head, here are some ideas for things it could cover:

What is pvlib?
How does pvlib compare to other tools (PVsyst, SAM, et al)
All I have is GHI, how do I get to POA?
Can I use PVsyst files (PAN/OND) files with pvlib?
Why don't my simulation results make sense? (answer: check timezone localization)
I got a warning like RuntimeWarning: invalid value encountered in arccos, what does it mean?
[your suggestions here]

I'm sure trawling github issues/discussions, stackoverflow, and google group threads would turn up more good things to include.
It might also be a good idea to explicitly try to speak "plain english" in FAQ entries, at least for the title of each entry.  For example an entry might be better titled "All I have is GHI, how do I get POA?" than something mentioning diffuse components and decomposition models.
Describe alternatives you've considered
N/A
Additional context
N/A

This is a good idea. It would be nice to place the link prominently on the top half of the README page.

Great! A question concerning when to use pvlib and when not to use pvlib (e.g., financial calculations) would be a great addition.


error: 2FA request expired, please try again

Problem
Some users faced the error and cannot enable 2fa

Expected Behavior
Users can enable 2fa
Steps to reproduce

input an email address as 2fa
input the code sent to their email
face this error and cannot enable 2fa

2FA codes expire after 30 minutes. How long after receiving the code are they trying to use it?
The workaround here would be to use the Resend your code option in the screenshot and use it immediately.

This account doesn't actually have an email address set as a recovery method or 2FA, so I don't know how they're seeing the email in the screenshot. They do have 2FA set up, but with a phone number. Any security code they're getting in an email is not going to work.
This user should reach out to support, we can reset their 2FA if they escalate through private channels.

Never mind I see the issue now, we'll get a fix out ASAP


API Remove ViewableData::ThemeDir, update changelog to reflect suggested replacement

Remove ThemeDir from ViewableData
Add note to changelog regarding removal, and suggest using ThemeResourceLoader::findThemedResource in conjunction with SSViewer::get_themes instead.

Resolves #6578

Since it can't be done in a single call from templates without a controller method to wrap, should we add a similar method to requireCSS somewhere?

Do you mean adding a themedImage function? Probably just best to hard-code it for that theme, to be honest.

True- it's probably a unique file to that theme

@tractorcow both points updated


Modals are broken in IE8 and IE9

Getting a javascript error in jQuery's camelCase function (Object doesn't support this property or method) when calling .modal("show") on IE8 and IE9.
Seems fine on other browsers, and on IE10

I am having the same issue with modals in IE8 and IE 9. Works well with other browsers.
The JQuery version is 1.11.1.
Semantic UI version: 2.1.14
I get the following error:
Message: 'console' is undefined
Line: 12
Char: 8424
Code: 0
URI: {...}/modal.min.js


Vim/gvim loses focus after job_start

Vim always loses focus after starting a job with a channel using job_start. I verified that this behavior is the same for both vim and gvim. I use Windows but I suspect that the behavior is the same for other OS. Is there an option to keep the focus in vim or at least in gvim?
The usage scenario is this: I am using job_start to open an Electron app to preview html/markdown files.  Most user interactions remain with vim. So it would be nice to not lose the focus when the app is launched.
On Windows focus can be controlled using SetForegroundWindow. I see this function used in gvim source code although I don't pretend to understand the context. I think it is indeed possible at least for gvim.
I am using gvim/vim 8.0 from the official 32bit release for Windows on Windows 10.

I found foreground function and will study that first.

I can confirm that :call foreground() right after job_start does not do anything. :help foreground produces the following:
foreground()	Move the Vim window to the foreground.  Useful when sent from
		a client to a Vim server. |remote_send()|
		On Win32 systems this might not work, the OS does not always
		allow a window to bring itself to the foreground.  Use
		|remote_foreground()| instead.

So maybe this is not possible on Windows or :call foreground() is not the right command. I am not trying to raise a window from the bottom of a pile. I am just trying to retain focus after starting an async job. I am still hoping this is possible.

I got it to work after putting the :call foreground() into the job_start callback function. Hopefully this does not disturb too many people and someone in the future finds this tip useful. It would be good to have this in the channel.txt reference manual as this could be a recurring issue when more people start using the async interface.


Baseline adoption

when trying to change functional parameters in GUI, error message indicating wrong amount of parameters is shown

Solved with 544904417aba4e41815c37a092156f8f5a818697


ADD HACKTOBERFEST AND GSSOC BANNER ON THE README

Description
added banners to the website
Related Issues
Fixes #609
Changes
List the detailed changes made in this PR.

Added banners

Testing Instructions
Detailed instructions on how to test the changes. Include any setup needed and specific test cases.

Pull this branch.
Run npm install to install dependencies.
Run npm test to execute the test suite.
Verify that ...

Screenshots (if applicable)
Add any screenshots that help explain or visualize the changes.

Additional Context
Any additional context or information that reviewers should be aware of.

This PR is based on the following...

Checklist
Make sure to check off all the items before submitting. Mark with [x] if done.

[x ] I have performed a self-review of my code
[ x] I have commented my code, particularly in hard-to-understand areas
[ x] My changes generate no new warnings
[ x] I am working on this issue under GSSOC

@amiya-cyber good work


Updated installation notes for smac on MacOS 10.15 Catalina

Thank you, Daniel! Looks good to me. Please go ahead and merge your PR.


Upgrade cookbook  chef-vault dependency

+1 I am just having the same problem. ;)

+1 Same thing here. I just hacked the metadata.rb to allow 1.3.0 and it worked great.

:+1:

Tracking this work in https://github.com/onbeep-cookbooks/ssl-vault/pull/7

Merged in, this should be fix issues. Let me know!

It works, thanks @mjuarez!


Could not found tag: 0.6.4.dev0 WTForms (0.6.4.dev0)

In my production machine, WTForms Version (0.6.4.dev0) is installed and could not find the tag 0.6.4.dev0 in this repository for pre-production environment setup. Since I have to maintain the exact replica of production server in pre-production setup this version 0.6.4.dev0 is my requirement. Help me with this :)
Thanks

You appear to have installed a very old version and modified the version number. This is not a valid tag. We cannot support that.

@davidism Is there any way to install the pip packages of this version from installed local files in site-packages.

0.6.4 is not a valid version, and if it was it would be ancient. I cannot offer support for it. You'll need to figure out why your project is configured in such a way. I would suggest upgrading instead.


Next build raises no error on OOM failure

If next build fails on a deployment server which memory limits (think Heroku, Doku, or Flynn), it fails without reporting anything.   This makes debugging SUPER hard.
As a note, at least the now deployment process reports this, as your runner (@zeit/ace) does watch for child-process crashes:
> ▲ npm run build
> <--- JS stacktrace --->
> ==== JS stack trace =========================================
>     2: arguments adaptor frame: 2->1
> Security context: 0x3d224adcfb51 <JS Object>
>     3: _visit [0x3d224ad04381 <undefined>:1257] [pc=0x37955b4af2d2] (this=0x133d7d7a391 <a TreeWalker with map 0x288abbcb9379>,node=0x32cb149cda11 <an AST_Binary with map 0x1ede8fc31389>,descend=0x133d7d6ca61 <JS Function (SharedFunctionInfo 0x37931f345b61)>)
>     4: _walk [0x3d224ad04381 <undefined>:1022] [pc=0x37955c7fd55a] (this=0x32cb149cda11 <an AST_Bina...
> FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
> <--- Last few GCs --->
>   293670 ms: Mark-sweep 397.6 (407.1) -> 397.6 (412.1) MB, 424.7 / 0.0 ms [allocation failure] [GC in old space requested].
>   294202 ms: Mark-sweep 397.6 (412.1) -> 397.6 (412.1) MB, 532.3 / 0.0 ms [allocation failure] [GC in old space requested].
>   294770 ms: Mark-sweep 397.6 (412.1) -> 407.7 (407.1) MB, 568.0 / 0.0 ms [last resort gc].
>   295494 ms: Mark-sweep 407.7 (407.1) -> 417.7 (407.1) MB, 724.0 / 0.0 ms [last resort gc].
> Aborted (core dumped)
> Error Error: Command next build ended with code 134
>     at ChildProcess.<anonymous> (/usr/lib/node_modules/@zeit/ace/build/lib/run.js:1:599)
>     at emitTwo (events.js:106:13)
>     at ChildProcess.emit (events.js:191:7)
>     at maybeClose (internal/child_process.js:877:16)
>     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
> (node:136) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Command next build ended with code 134
> ▲ npm start
> Killed
> Error Error: Command next build ended with code 137
>     at ChildProcess.<anonymous> (/usr/lib/node_modules/@zeit/ace/build/lib/run.js:1:599)
>     at emitTwo (events.js:106:13)
>     at ChildProcess.emit (events.js:191:7)
>     at maybeClose (internal/child_process.js:877:16)
>     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
> (node:306) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Command next build ended with code 137

I have the same problem. Is there any temporary way to solve this?

Currently the process needs to have enough memory to build. May be around 1GB. (Or enable swap).

I built my next app on my EC2, which has only 1GB memory. Sometimes it succeed but sometimes doesn't, so I would like to build it on local and push the .next/ to the server side. Is it a good way to solve it?

@Larry850806 yes. That's a pretty good way to do it.

I'm going to close this as next build should now give proper error messages for most errors. There was a bug where process.exit was called before console.error/console.log could be executed.


Overhaul intersection consolidation

Today is a pretty damn good day.
#654 describes how we merge short roads and produce the intersection polygons today. This PR implements "wild alternative number 1," which isn't so crazy after all. The idea is to first run the normal intersection geometry algorithm before removing any of the short roads. That tells us how much to trim back all of the connected roads. We calculate that trimmed endpoint, then remove the short road. To produce the polygon for a consolidated intersection, we simply take the pre-trimmed road center lines, project the left and right, and use those endpoints as corners of the polygon.
Development workflow
A huge amount of trial-and-error and fiddling around went into this. A few things were absolutely necessary to iterate effectively:

a fast compile+import map process. My laptop dying a few months ago really threw off the last attempt at this!
../target/release/game --dev ../data/system/us/seattle/maps/phinney.bin --diff=../phinney.bin. That --diff flag just loads an older copy of a map, and the Ctrl+Tab keybinding toggles between the two. This makes it very easy to compare before/after with the full power of A/B Street -- checking signal timing, debugging intersection geometry, etc.
Marking short roads to merge in debug mode (hotkey m on a road). This let me quickly mark a bunch of short roads in Tempe and try the new algorithm on them, to verify it makes enough progress on the harder cases there.

Editing the map
On the last attempt of this change, I hit a bunch of problems thickening/shrinking roads near consolidated intersections. The approach here moves around when roads get pre-trimmed and simplifies things. But still, this PR has pretty much no special code to handle edits. I tried a few examples and couldn't break anything. There might still be bugs I've missed; I need to make a fuzz tester that automatically modifies roads near consolidated intersections. But for now, I'm willing to deal with problems as they're found.
Validation
I'm regenerating everything now. But I manually inspected differences in a bunch of maps, and the new algorithm pretty much always wins. Some examples... the blue bottom bar is the old version of the map.
Weird angled roads are still funny, but slightly slimmer now:

Weird gaps in the polygon are usually filled, now that the polygon endpoints are always just the left and right sides of each incoming road:

Dramatic problems become totally reasonable:

And in addition, there are a BUNCH of intersections in the Tempe map that I can now consolidate. I'll do that in OSM upstream (junction=intersection) separately as a followup. I didn't tag them before now because they outright break the old algorithm (either producing something very bad or even crashing).
Remaining problems
The new algorithm of course isn't perfect. Two more things I want to improve...

The weird "bowtie" on the right is because we fail to sort all of the incoming roads in the correct clockwise order. We calculate this order by the angle between the road center lines and the geometric center of all of those endpoints, but something is going wrong here.

Why isn't 80th street trimmed back? The problem is a bit easier to see in the map editor:

The blue road actually intersects the grey road above the pink one (the short segment to merge). In other words, two roads physically overlap, but in OSM, they don't share a node. This class of problem happens a fair bit, and I'm not sure what to do about it yet.

I admit, some of the code around the map processing flow, without being already familiar, is pretty in the weeds... but it looks plausible!

Real Soon Now, I'm going to write up some proper articles describing some of the hard problems in A/B Street and assuming no background:

turning road center-lines and widths into these lovely polygons
how pathfinding is set up (all the nuance around left turns out of driveways, modelling private neighborhoods)
how the discrete event simulation works (once the over-taking is a bit more realistic)


[Icon] - Comments icon showing twice

Not a real bug, just the comments icon is showing twice on icons page.

It isn't appearing on the icon.html page anymore.


chore(Topology/Instances/Discrete): merge 2 instances

Prove DiscreteTopology.secondCountableTopology_of_countable directly,
deprecate DiscreteTopology.secondCountableTopology_of_encodable.

Thanks!
maintainer merge


requests[security] breaks on Python 2.6 after pyOpenSSL 18.0.0 (2018-05-16) drops support

WIth the 18.0.0 release, pyOpenSSL dropped support for Python 2.6.
As requests[security] pins pyOpenSSL with only a minimum version, fresh installations of requests pick up the latest and incompatible dependency.
Expected Result
Requests[security] functions to work.
Actual Result
NameError: global name 'memoryview' is not defined

Reproduction Steps
>>> import requests
/Users/dwight/.local/share/virtualenvs/stream-python-z8k7CN8K/lib/python2.6/site-packages/cryptography/__init__.py:26: DeprecationWarning: Python 2.6 is no longer supported by the Python core team, please upgrade your Python. The next version of cryptography will drop support for Python 2.6
  DeprecationWarning
>>> requests.get('https://www.dwightgunning.com')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/dwight/.local/share/virtualenvs/stream-python-z8k7CN8K/lib/python2.6/site-packages/requests/api.py", line 72, in get
    return request('get', url, params=params, **kwargs)
  File "/Users/dwight/.local/share/virtualenvs/stream-python-z8k7CN8K/lib/python2.6/site-packages/requests/api.py", line 58, in request
    return session.request(method=method, url=url, **kwargs)
  File "/Users/dwight/.local/share/virtualenvs/stream-python-z8k7CN8K/lib/python2.6/site-packages/requests/sessions.py", line 508, in request
    resp = self.send(prep, **send_kwargs)
  File "/Users/dwight/.local/share/virtualenvs/stream-python-z8k7CN8K/lib/python2.6/site-packages/requests/sessions.py", line 618, in send
    r = adapter.send(request, **kwargs)
  File "/Users/dwight/.local/share/virtualenvs/stream-python-z8k7CN8K/lib/python2.6/site-packages/requests/adapters.py", line 440, in send
    timeout=timeout
  File "/Users/dwight/.local/share/virtualenvs/stream-python-z8k7CN8K/lib/python2.6/site-packages/urllib3/connectionpool.py", line 601, in urlopen
    chunked=chunked)
  File "/Users/dwight/.local/share/virtualenvs/stream-python-z8k7CN8K/lib/python2.6/site-packages/urllib3/connectionpool.py", line 357, in _make_request
    conn.request(method, url, **httplib_request_kw)
  File "/Users/dwight/.pyenv/versions/2.6.6/lib/python2.6/httplib.py", line 914, in request
    self._send_request(method, url, body, headers)
  File "/Users/dwight/.pyenv/versions/2.6.6/lib/python2.6/httplib.py", line 951, in _send_request
    self.endheaders()
  File "/Users/dwight/.pyenv/versions/2.6.6/lib/python2.6/httplib.py", line 908, in endheaders
    self._send_output()
  File "/Users/dwight/.pyenv/versions/2.6.6/lib/python2.6/httplib.py", line 780, in _send_output
    self.send(msg)
  File "/Users/dwight/.pyenv/versions/2.6.6/lib/python2.6/httplib.py", line 759, in send
    self.sock.sendall(str)
  File "/Users/dwight/.local/share/virtualenvs/stream-python-z8k7CN8K/lib/python2.6/site-packages/urllib3/contrib/pyopenssl.py", line 316, in sendall
    sent = self._send_until_done(data[total_sent:total_sent + SSL_WRITE_BLOCKSIZE])
  File "/Users/dwight/.local/share/virtualenvs/stream-python-z8k7CN8K/lib/python2.6/site-packages/urllib3/contrib/pyopenssl.py", line 304, in _send_until_done
    return self.connection.send(data)
  File "build/bdist.macosx-10.13-x86_64/egg/OpenSSL/SSL.py", line 1719, in send

NameError: global name 'memoryview' is not defined

System Information
$ python --version
Python 2.6.6
$ python -m requests.help
/Users/dwight/.local/share/virtualenvs/stream-python-z8k7CN8K/lib/python2.6/site-packages/cryptography/__init__.py:26: DeprecationWarning: Python 2.6 is no longer supported by the Python core team, please upgrade your Python. The next version of cryptography will drop support for Python 2.6
  DeprecationWarning
{
  "chardet": {
    "version": "3.0.4"
  },
  "cryptography": {
    "version": "2.1.4"
  },
  "idna": {
    "version": "2.6"
  },
  "implementation": {
    "name": "CPython",
    "version": "2.6.6"
  },
  "platform": {
    "release": "17.5.0",
    "system": "Darwin"
  },
  "pyOpenSSL": {
    "openssl_version": "100020ff",
    "version": "18.0.0"
  },
  "requests": {
    "version": "2.18.4"
  },
  "system_ssl": {
    "version": ""
  },
  "urllib3": {
    "version": "1.22"
  },
  "using_pyopenssl": true
}

Hey @dwightgunning, thanks for bringing this to our attention! I think the easiest option is to pin a max version for Python 2.6 specifically in our security section of setup.py. Similar to how we handle win_inet_pton.
One thing we may want to consider is the implications of further supporting 2.6 as a “secure” option though. Given that it’s no longer (to my knowledge) receiving security updates and we’re pinning security packages at a possibly flawed point in time, do we want to reconsider dropping 2.6 prior to Requests 3.0.0?
/cc @Sigmavirus24

We haven't tested against Python 2.6 in a long time, @nateprewitt. In my mind, we dropped support for it a long time ago. Between pip dropping support for it, most packaging libraries dropping support for it, and our inability to test on Python 2.6, I think calling it unsupported in the next release is only reasonable.

Fair.
I setup a fork to test the fix proposed by @nateprewitt and works with my test application.
https://github.com/dwightgunning/requests/commits/v2.18.4-patched-for-py2.6
It's probably not really worthy of a PR but happy to raise one if you'd like to see it.
An alternative for anybody defining a package with setuptools is to use the install_requires property. For instance:
install_requires = []
if sys.version_info < (2, 7, 0):
    install_requires.append('pyOpenSSL<18.0.0')

setup(
    # snip
    install_requires=install_requires
)

Also worth noting that urllib3 does still test against Python 2.6 and is using https://github.com/urllib3/urllib3/pull/1389 to fix this. I wonder if our "security" extra should just depend on the "secure" urllib3 extra and let that do that all the heavy lifting.
As for the alternative fix you've proposed @dwightgunning that only works if people are installing from an sdist. If anyone were to package a wheel for this, then they would not receive the right package version unless they capped it another way.

Python 2.6 was dropped by requests 3 in May 2017 (https://github.com/requests/requests/pull/4118).
Python 2.6 has been unsupported/EOL, and no longer receiving security updates (or any updates), from the core Python team since October 2013.

https://en.wikipedia.org/wiki/CPython#Version_history
And there's relatively few pip installs on 2.6 for requests from PyPI (April 2018):

python_version
percent
download_count

2.7
64.02%
4,941,921

3.6
21.76%
1,679,455

3.5
8.29%
639,898

3.4
5.38%
415,136

2.6
0.28%
21,280

3.7
0.16%
12,724

3.3
0.11%
8,204

3.2
0.01%
808

3.8
0.00%
52

None
0.00%
46

Total

7,719,524

Source: pypinfo --start-date 2018-04-01 --end-date 2018-04-30 --percent --markdown requests pyversion

@hugovk 2.6 and 2.7 are planned to be unsupported with requests3. @nateprewitt already explained that.
Thank you for providing the download stats. I didn't know pypinfo did that.

Hi again @hugovk, the plan is still to remove 2.6 (and in general python2) support in Requests3. The next release will simply be removing documentation that we support Python 2.6. I don't think there's a need to break existing implementations just because we don't support it anymore.

The statement of support for 2.6 in the current stable release was the reason I opened the issue. I understand it's annoying the problem is introducing via an upstream change but I figured it'd be worth noting.
If there's a reasonable way to restore a "workable" py2.6 + Requests2 (even if the python version and some upstream deps aren't maintained) it'll probably be helpful to people.

Hi @dwightgunning, this is resolved in 2.19.0 which is now up on PyPI. We've also removed 2.6 references from the documentation, so going forward we'll be focusing on 2.7 for our Python 2 support target. Ideally Python 2.6 will continue working for the foreseeable future, but we won't be putting resources towards fixing future 2.6-specific issues.
Thanks again for letting us know about this!


Pull to refresh is not working with Tab layout

Hi,
I am using refreshControl from react-native with native-base Tab layout, refreshControl often hangs while pulling to refresh, Please Suggest me some fix for this, Here is the code snippet,
Here is my Tab code where I am applying the pull to refresh functionality
<Tabs tabBarUnderlineStyle={{borderBottomWidth:1}} >           <Tab heading={ <TabHeading >             <Icon style={styles.TabIcon} name="random" type="FontAwesome" />             <Text style={styles.TabText}>Random</Text>             </TabHeading>}> <Content         refreshControl={           <RefreshControl             refreshing={this.state.refreshing}             onRefresh={this._onRefresh}             title="Loading..."           />         }         onScroll={({ nativeEvent }) => {           if (isCloseToBottom(nativeEvent)) {             this.appendQuotes();           }         }}         scrollEventThrottle={400}       >         {quoteList}         {spinner}       </Content>  </Tab>

Cant find Tab code

I made a little change in your provided code, to demonstrate basic example of Tabs with pull to refresh. worked fine

That looks fine and same as what I am working with. But When I am placing tab having refresh Control as the first tab then I encountered this problem. So using your code will changing the Tab position will work?


fix: test fixes

Fixes for #15.

Should we move tests that is not required both manual sync mode to different files ?

Should we move tests that is not required both manual sync mode to different files ?

Seems like addressed in #19


Unable to call performUpkeep(), receiving error "cannot estimate gas"

Would very much appreciate assistance here. I first attempted debugging the chainlink side but then went to try to execute perform upkeep through hh console and noticed that I am not able to execute it successfully.
Went through these steps:
hh deploy --network goerli
hh console --network goerli
const { ethers, deployments } = require('hardhat');
await deployments.fixture('all');

const deployer = (await ethers.getSigners())[0];

const Raffle = await ethers.getContract('Raffle', deployer);

await Raffle.enterRaffle({ value: ethers.utils.parseEther("0.01") })

// This line must return true
await Raffle.checkUpkeep([]);

// Then try to perform by yourself
await Raffle.performUpkeep([]);

checkUpkeep() at this point returns [ true, '0x', upkeepNeeded: true ]
executing performUpkeep() returns:
Error: cannot estimate gas; transaction may fail or may require manual gas limit [ See: https://links.ethers.org/v5-errors-UNPREDICTABLE_GAS_LIMIT ] (reason="execution reverted", method="estimateGas", transaction={"from":"0x97A08B37AbD78275fD84A803fBfAF87fBe6c64AF","to":"0x0b2145adf128F63902ea6F84d29e41BE8154f569","data":"0x4585e33b00000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000000000000000000000","accessList":null}, error={"name":"ProviderError","_stack":"ProviderError: HttpProviderError\n    at HttpProvider.request (/Users/sam/Documents/hh-fcc/hardhat-smartcontract-lottery-fcc/node_modules/hardhat/src/internal/core/providers/http.ts:78:19)\n    at LocalAccountsProvider.request (/Users/sam/Documents/hh-fcc/hardhat-smartcontract-lottery-fcc/node_modules/hardhat/src/internal/core/providers/accounts.ts:187:34)\n    at processTicksAndRejections (node:internal/process/task_queues:96:5)\n    at EthersProviderWrapper.send (/Users/sam/Documents/hh-fcc/hardhat-smartcontract-lottery-fcc/node_modules/@nomiclabs/hardhat-ethers/src/internal/ethers-provider-wrapper.ts:13:20)","code":3,"_isProviderError":true,"data":"0xf0019fe600000000000000000000000000000000000000000000000000000000000017100000000000000000000000000b2145adf128f63902ea6f84d29e41be8154f569"}, code=UNPREDICTABLE_GAS_LIMIT, version=providers/5.7.2)
    at step (/Users/sam/Documents/hh-fcc/hardhat-smartcontract-lottery-fcc/node_modules/@ethersproject/providers/lib/json-rpc-provider.js:48:23)
    at EthersProviderWrapper.<anonymous> (/Users/sam/Documents/hh-fcc/hardhat-smartcontract-lottery-fcc/node_modules/@ethersproject/providers/src.ts/json-rpc-provider.ts:642:20)
    at checkError (/Users/sam/Documents/hh-fcc/hardhat-smartcontract-lottery-fcc/node_modules/@ethersproject/providers/src.ts/json-rpc-provider.ts:78:20)
    at Logger.throwError (/Users/sam/Documents/hh-fcc/hardhat-smartcontract-lottery-fcc/node_modules/@ethersproject/logger/src.ts/index.ts:281:20)
    at Logger.makeError (/Users/sam/Documents/hh-fcc/hardhat-smartcontract-lottery-fcc/node_modules/@ethersproject/logger/src.ts/index.ts:269:28) {
  reason: 'execution reverted',
  code: 'UNPREDICTABLE_GAS_LIMIT',
  method: 'estimateGas',
  transaction: {
    from: '0x97A08B37AbD78275fD84A803fBfAF87fBe6c64AF',
    to: '0x0b2145adf128F63902ea6F84d29e41BE8154f569',
    data: '0x4585e33b00000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000000000000000000000',
    accessList: null
  },
  error: ProviderError: HttpProviderError
      at HttpProvider.request (/Users/sam/Documents/hh-fcc/hardhat-smartcontract-lottery-fcc/node_modules/hardhat/src/internal/core/providers/http.ts:78:19)
      at LocalAccountsProvider.request (/Users/sam/Documents/hh-fcc/hardhat-smartcontract-lottery-fcc/node_modules/hardhat/src/internal/core/providers/accounts.ts:187:34)
      at processTicksAndRejections (node:internal/process/task_queues:96:5)
      at EthersProviderWrapper.send (/Users/sam/Documents/hh-fcc/hardhat-smartcontract-lottery-fcc/node_modules/@nomiclabs/hardhat-ethers/src/internal/ethers-provider-wrapper.ts:13:20)
}

I tried upping the gas limit in network config but it did not seem to do anything:
const networkConfig = {
    5: {
        name: "goerli",
        vrfCoordinatorV2: "0x2Ca8E0C643bDe4C2E08ab1fA0da3401AdAD7734D",
        entranceFee: ethers.utils.parseEther("0.01"),
        gasLane: "0x79d3d8832d904592c0bf9818b621522c988bb8b0c05cdc3b15aea1b6e8db0c15",
        subscriptionId: "5904",
        callbackGasLimit: "1000000", // 500,000
        interval: "30",
    },

I am calling performUpkeep() with the deployer address. In case the issue was with the deployer address, I tried calling again from deployer address after changing performUpkeep to public instead of external and it didn't change the outcome
Here's a link to my repo https://github.com/samwise00/hardhat-smartcontract-lottery-fcc
Thanks all

Can you:

Make this a discusson on the full repo? https://github.com/smartcontractkit/full-blockchain-solidity-course-js/
Thanks!


CORGI-536 - change sources, provides and upstreams to do exact match

?sources={}, ?provides={} and ?upstreams={} should perform an exact match .. this has the benefit of avoiding a LIKE in generated SQL (which is seriously slow and expensive query).
in addition we added re_ variants to enable regex matching if that is so desired.
IMPORTANT - when doing this I added some more tests but confused by the result of explicitly testing node creation ... needs discussion

going to close this for now


bug: 4.7.7 is missing in the nexus

Not sure why this happens (kind of unusually often), but 4.7.7 is not released to the nexus yet : https://mvnrepository.com/artifact/com.netflix.graphql.dgs/graphql-dgs-platform-dependencies.

There is no 4.7.7 I think? The releases page doesn't show it: https://github.com/Netflix/dgs-framework/releases
We went from 4.7.6 to 4.8.

Odd - i have a release notification (gihub) for 4.7.7 - has it been deleted? Anyway, if this is just me confused or it has been deleted, same outcome. I went to 4.8.3 already too, so great you closed that issue. Sorry for the fuz, kind of confusing start into thee week!


appleseed: migrate to boost168

Motivation for this change
boost < 168 fails to build with python >= 3.7
Refer https://github.com/boostorg/python/commit/660487c43fde76f3e64f1cb2e644500da92fe582
Still fails as appleseed-studio requires python2
Refer https://github.com/NixOS/nixpkgs/pull/131719#issuecomment-979740898
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Can you try to get it to compile? Only this patch is not that useful

Can you try to get it to compile?

Still fails as appleseed was migrated to python3 as part of https://github.com/NixOS/nixpkgs/pull/131719.
The only better way to fix it is to follow freebsd ports and patch everything. More details: https://github.com/NixOS/nixpkgs/pull/131719#issuecomment-979740898
I don't think switching back to python2 is an option as py2 reached EOL. let me know if you think otherwise

Can you maybe give upgrading to 2.1.0-beta a try?

Appleseed has been removed from nixpkgs, so closing this PR...


Request: Add path for VLC Flatpak

Can peerflix add support for VLC flatpak? Or can someone tell me how I can alter existing code to make peerflix check for VLC flatpak when using the --vlc flag?

workaround:
mkdir -p ~/.local/bin
echo "flatpak run org.videolan.VLC $@" > ~/.local/bin/vlc
peerflix "torrent" --vlc


Style Guide

This needs a copyedit if/when it becomes easier to find. Feel free to assign this bug to me then (or to open a new one).


Add an appcast generator

We should create an appcast generator program that, at the very least, scans an EXE and outputs the applicable appcast info to an XML file or format. Preferably, it'd scan a folder of EXEs like the Sparkle generate_appcast tool and create a file that is updated over time and can just be plopped on the server.

Fixed by #53


Assert Required Claims Flexibility

Some context of my issue over here. The short of it, is that it seems I cannot SignIn() a user if the principal does not contain the name claim even if the principal has been specified to use a different claim type as the name claim.
In my case I would like to use the "preferred_username" as the principals name. I am pretty sure that the claims principal has the claim type of where the name came from as well, so this wouldn't be too much of  a fuss to do. Could something like checking for the name claim type rather than just doing a blanket check on the claim type "name" like it is now? The LOC in question is here
Thanks.

We simply use a claim called name for the UI. Simply create a name claim with whatever content you want.

OK. I guess all is good then. Thanks a lot.


Improve IDE support by providing CMakePresets.json

This is an upcomming change to the currently used CMakeSettings.json approach, which is specific to Visual Studio.
The new CMakePresets.json file will be used by IDEs to pickup and provide the configuration presets to the users.
VS
Visual Studio will switch to this new config file format, see VS Roadmap.
It will replace CMakeSettings.json which had some issues.
VS Code
Visual Studio Code is switching.
Presets are available in CMake v3.19+.

https://cmake.org/cmake/help/latest/guide/ide-integration/index.html#presets
https://cmake.org/cmake/help/latest/manual/cmake-presets.7.html#id1

Todo

[ ] remove the VS specific CMakeSettings.json
[ ] setup CMakePresets.json

The file should provide reasonable defaults to configure the build environment for ttauri for multiple IDEs.

The newest Visual Studio 2022 is by default configured to read CMakePresets.json if available.

I worked on this issue quite a bit, but CMakePresets.json is insanely broken for Visual Studio Code.
Last time i checked, it didn't even set the CMake -A (arch) and -G (generator) correctly.
But, of course, we can try it with VS2022. Maybe we get it working.


Add elastic-job-cloud-console module.

Coverage decreased (-0.3%) to 89.721% when pulling 2d9d709d38f7c50ca0c45ffb4f8cb1c0d531894a on Zhangxinguo:master into a09731acd2f505988ff598498d95298202a62d92 on dangdangdotcom:master.


shm by name 'timer_shm' not found

Got the error message*56 lua coroutine: runtime error: /usr/local/share/lua/5.1/resty/timer.lua:244: shm by name 'timer_shm' not foundwith the below options or configurations
local options = {
            interval = 2,           -- expiry interval in seconds
            recurring = true,         -- recurring or single timer
            immediate = false,         -- initial interval will be 0
            detached = false,         -- run detached, or be garbagecollectible
            expire = object.handler,  -- callback on timer expiry
            cancel = function(reason, self, param1)
                -- will be called when the timer gets cancelled
				print("Cancelling "..reason.." ".." self"..param1)
            end,
             shm_name = "timer_shm",   -- shm to use for node-wide timers
             key_name = "my_key",      -- key-name to use for node-wide timers
            -- sub_interval = 0.1,       -- max cross worker extra delay
        }

How to solve this issue? I need to run only 1 timer at a time and this can be achieved through shm_name.

In your nginx configuration you need the lua_shared_dict directive, as shown here: https://github.com/Kong/lua-resty-timer#synopsis

In your nginx configuration you need the lua_shared_dict directive, as shown here: https://github.com/Kong/lua-resty-timer#synopsis

@Tieske very helpful. I missed it somehow. Thanks and cheers


enh(Python): nth_fibonacci_number

PR Checklist:

[x] My submission is formatted according to the guidelines in the contributing guide
[x] My addition is on refer on the language README.md file
[x] My addition does not have a spelling problem
[x] My submission has a proper and user-friendly description of the algorithm
[x] My submission has the time complexity of the algorithm
[x] My submission has sample input-output of the program (NOT FOR PYTHON)

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[x] New algorithm
[ ] Optimization in previous algorithms
[ ] Code style update
[ ] Refactor
[ ] Documentation
[ ] Other, please describe:

Briefly describe the changes in this PR

Other information:

Hey @bishtanuj ! This code is just plain recursion and will work in exponential time complexity. A code using dynamic programming(memoization) already exists that is far better and shall work in O(n) time and O(n) space. However, there exists and algorithm to improve space complexity of the code, where you will need O(1) auxiliary space by just maintaining three variables (you can research rest). But unfortunately it doesn't fall under the category "RECURSION"! Hence, no point in this PR i suppose.

The existing code is for the nth Fibonacci number but this program is for Fibonacci series

This PR is about Fibonacci Series, kindly do not confuse it with nth_fibonacci_number, as it is different from it

This PR is about Fibonacci Series, kindly do not confuse it with nth_fibonacci_number, as it is different from it

@ming-tsai sir has changed the name of the PR, but the PR is about Fibonacci Series not nth number

This PR is about Fibonacci Series, kindly do not confuse it with nth_fibonacci_number, as it is different from it

I know full well what your code is meant to do. However, that isn't quite the issue here.
Your current code won't even generate the series of 100 numbers. Just try running it.
You need to optimize your code using dp if at all you want to put it under the category of recursion!


add roxygen2 to R deps?

https://github.com/twosigma/beaker-notebook/issues/3422
unclear why a new R needs a new package but it's possible
we'll need to add this to dockerfile and linux dependencies.

this is what's needed
https://github.com/twosigma/beaker-notebook-www/commit/ebdb4667ac323502defed616bab45a2bff4f5061

https://github.com/twosigma/beaker-notebook/commit/0e0d3382791b7fe9166374f6040af0159788d4f9


State change problem with nextButtonText

The problem occurs when the props of the Stepzilla component change due to a state change of the parent component. In this case, the navigation buttons are re-rendered, with the exception of the Next button. Its text is determined by the state of the Stepzilla component.

Sorry @tomtoxx I need more info on this?
How can I repo this? what impact does it have for the end-user that the buttons are re-rendered? is there an actual error?

If you use i18n, you give the translation function into the step components as props.
If the user now changes the language, the description of the Back button changes but not the description of the Next button, because it gets its description from the state and not from props.
 <button
            style={this.state.showNextBtn ? {} : this.hidden}
            className={props.nextButtonCls}
            onClick={() => {this.next()}}
            id="next-button"
          >
            {this.state.nextStepText}
          </button>

The problem is this: {this.state.nextStepText}

I see what you mean now - let me look into it. I'll use your PR as a guide.

@tomtoxx thanks for raising this issue - working on a fix for it made me see that I initially coded a very bad prop->state pattern, where prop changes had to be synced with state which drove the render. This is a very bad design pattern in react.
I have fixed this issue (i have tested it by changing the next / back button text half way through a step process). The fix is in a branch issue-116:
https://github.com/newbreedofgeek/react-stepzilla/blob/issue-116/src/main.js#L289
Note: I cleaned up old legacy code as well - the above is just the way I now work with props directly
... Before I raise a PR and bring it into master, can you please check out this branch. Launch in dev-mode:
https://github.com/newbreedofgeek/react-stepzilla/blob/master/README.md#dev
... Update the example implementation
https://github.com/newbreedofgeek/react-stepzilla/blob/master/src/examples/Example.js
... With your i18n requirement and verify it all works.
There is another way to test:
If you are using StepZilla via node_modules (i.e. via npm install). just grab the src directly from here https://github.com/newbreedofgeek/react-stepzilla/blob/master/src/main.js as a local copy into your project and import StepZilla from there.
As this is a beaking change and we have many users using this in production I want to make sure its 100% good before merging to master and pushing to NPM.
Again, thanks for your contribution.

Your changes work great! :smile:
I integrated our i18n workflow into the examples and translated them into German.
The buttons now change the language without any problems!


[TimePicker] Min/max is not respected if it doesn't have a default value

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
the time range min/max isn't respected for a  Time component that has the value = null;
it's only after first selected a time that the time range is respected.
https://stackblitz.com/edit/react-ix5es1?file=demo.tsx
Expected behavior 🤔
should always respect the min/max
Steps to reproduce 🕹
Steps:

https://stackblitz.com/edit/react-ix5es1?file=demo.tsx
click to add time
you will see you it displays all the time options and not limited to the min/max

Context 🔦
No response
Your environment 🌎

`npx @mui/envinfo`
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

I am having the same problem, datepicker is still working well


Fix wrong -spec().

This is basically #133 adapted to the most jsx recent code (two releases were done, in the meantime, though, and this issue resurfaced).
Cheers to the original implementation 🎉.
[Fix #133]

I ended up replacing this one with a "deeper" #146. The adventure continues on that one.


New docs layout and a few minor tweaks

Basically completely rewritten the entire structure for the docs, it now looks less ... simple.

Amazing work, thank you for your contribution.


added coding style for both upstream mutt and for our future

@neomutt/reviewers What do you think? I just tried to sum up our opinions regarding coding style.

I don't think we should give examples of "what will be".
Not until it's really close to happening.

@flatcap That means you think we should completely remove the future section?

Yes.
We should have lots of good examples for what the code should look like now,
but I think the future stuff is distracting.

@flatcap fixed.

In general, no coding style is better than another.  It's a matter of taste, and my opinion is that it's not worth spending a single minute debating the pros and cons of a particular style. Discussions like "four spaces are better than two" make no sense.
The goal is having consistency across the code base, not to fit a particular individual's preferences.
Thus, if you really want to devise a specification for how to code within NeoMutt, my suggestion is to look at the whole of the code base and and adopt that style that retroactively fits the most of it.
Any other approach has no fundamental defensible justification.

My .2$

I think this PR is made completely obsolete by Flatcap's much better coding style commit


Identity README additions for 1.1.0 release

resolves #12372

@jianghaolu, keyvault is failing its From Source runs because spring-cloud-azure-appconfiguration-config, has a dependency on azure-security-keyvault-secrets. I've got a PR  open to fix this. You'll have to rebase when I get it merged.

Thanks! I wasn't able to figure that out. Glad you took a look at my pr


jscad CLI fails to load some STL files

When running a project through the Jscad CLI some imported STL files may file.
This may also be related to issue #1333.
It seems like registerDeserializer in registerExtensions.js registers a wrapper that loads the file using fs.readFileSync, passing utf-8 as the encoding. However if the file is binary, this may cause codepage translation to corrupt it.
Patching locally to use 'binary' as the encoding works for these STL files but obviously may cause other problems if there are importers that assume utf8....
Example project failing:
example_project.zip
CLI command invocation:
node<EMAIL_ADDRESS>"/Users/eldan/Desktop/jscadproject" -o "/var/folders/d4/2ffmpbdn51ld1mb7_k7gj4240000gn/T/vscode-jscad-GbnSqf/output.stl"
Output:
bad triangle vertice coords/normal:  1
bad triangle vertice coords/normal:  1
bad triangle vertice coords/normal:  1
bad triangle vertice coords/normal:  1
bad triangle vertice coords/normal:  1
bad triangle vertice coords/normal:  1
bad triangle vertice coords/normal:  1
WARNING: import errors: 7 (some triangles might be misaligned or missing)
Error: point 1503 must be an array of X, Y, Z values
at /Users/eldan/dev/priv/vscode-jscad/node_modules/@jscad/modeling/src/primitives/polyhedron.js:50:41
at Array.forEach ()
at Object.polyhedron (/Users/eldan/dev/priv/vscode-jscad/node_modules/@jscad/modeling/src/primitives/polyhedron.js:49:10)
at toPolyhedron (/Users/eldan/dev/priv/vscode-jscad/node_modules/@jscad/stl-deserializer/index.js:372:21)
at elementFormatterObject (/Users/eldan/dev/priv/vscode-jscad/node_modules/@jscad/stl-deserializer/index.js:54:80)
at deserializeBinarySTL (/Users/eldan/dev/priv/vscode-jscad/node_modules/@jscad/stl-deserializer/index.js:273:11)
at deserialize (/Users/eldan/dev/priv/vscode-jscad/node_modules/@jscad/stl-deserializer/index.js:62:34)
at _require.extensions. [as .stl] (/Users/eldan/dev/priv/vscode-jscad/node_modules/@jscad/core/src/io/registerExtensions.js:20:20)
at Module.load (node:internal/modules/cjs/loader:1282:32)
at Module._load (node:internal/modules/cjs/loader:1098:12)

Perhaps best to load files as binary and allow the actual serializers to decode as utf-8 if they require text?

Perhaps best to load files as binary and allow the actual serializers to decode as utf-8 if they require text?

@eldanb thanks for the nice details.
in core/web/walkfiletree.js, STL files are treated as binary, and the deserializer actually checks for text versus binary format. So, I think that your analysis is correct.
So, if you have time then please create a PR with your change. A reference to the STL file would be nice as well.

Opened https://github.com/jscad/OpenJSCAD.org/pull/1366

@eldanb please try the new release. If satisfied then close this issue as well.
thanks for the fixes!

Looks great. Thanks so much.


TreeView ineffeciencies causing huge trees to take forever

I am working on a reverse engineering project with an archive filesystem which has been be translated so I can make use of it with the TreeView control. I have discovered that doing node.Children.Add() causes a graphical update or something else at least which is taking a long time and ends up hanging the application. There arent many children getting added, a 131 child job takes about 30 seconds which is very slow.
I have confirmed this is not my code, it hangs when node.Children.Add() is called.
I have tried setting the Children ObservableCollection directly since it has a setter but, that does not seem to update the control at all.
Is there any chance this could get looked at? Perhaps add an update to the Children setter or, let us call an update ourselves after adding all the Children?
I am still relatively new to MAUI so I cannot contribute to this myself. I am using .NET 8 MAUI on the latest release UraniumUI.

Iv discovered that it takes exponentially longer, the more elements are in the tree.

TreeView uses BindableLayout. Probably bottleneck is BindableLayout itself.
https://github.com/enisn/UraniumUI/blob/92fdfd90157e6f065cde26a06a310ad37700b997/src/UraniumUI.Material/Controls/TreeView.cs#L92
But, my first approach while building TreeView was using CollectionView, but using multiple-level CollectionView made the application unusable, its performance was much worse than the current state, and it was crashing randomly while scrolling. I'm not sure how to increase performance but I can build a custom item-recycling logic for BindableLayout

Is there something specific about Android?
I can quickly load a huge amount on windows, but Android constantly shows me Performing a full GC


Can we start publishing released builds under "Releases"

Can we use the GitHub releases feature to publish new releases? I just discovered we now have a 1.3.7 version.

This is good idea, currently we release everything on npm, but I think we could get some automation going that allows us to publish to both github and npm.  Will keep you posted


Remove 'open file' feature option

Hi,
First, thank you for this wonderful plugin and your work on it ;
Is it possible to have an option to remove/disable the "open file" feature please ?
I just don't see any use for it, and it makes heavier the UI, also I'm hoping it can't be a feature that leads to some sort of exploit possible

Thank you very much :)

It's on the list of things to do.

This has been completed.

Tahnk you very much @TwisterMc :)


[feature] #2502: Store GIT hash of build

Signed-off-by: Shanin Roman<EMAIL_ADDRESS>

Description of the Change
Add build.rs to extract git hash of build.

Issue
Closes #2502.

Benefits
Easier to debug.

Possible Drawbacks
None.

Usage Examples or Tests
cargo run --bin iroha_client_cli  -- --version
cargo run --bin iroha -- --version

I suppose you forget to add "build" = "build.rs" to Cargo.toml files, no?

hmm, everything works fine without it, but i can add it, no problem

I suppose you forget to add "build" = "build.rs" to Cargo.toml files, no?

hmm, everything works fine without it, but i can add it, no problem

Okay, I've just checked doc, it seems build = "build.rs" now by default starting from some version.


My game won't start

My game won't get past the loading screen. I put in both mods I needed and tried to start the game and it wouldn't start
I'm using Minecraft 1.19 Minekea 1.19 3.3.3 and arrp 0.6.4

Do you have Patchouli installed? I've been meaning to add a check that conditionally loads the configs for that, but at present, I believe Patchouli is a required dependency as well.
If you do have Patchouli, can you post a crash log? It's possible there is a conflict with some other mod (or simply a different bug that I haven't run into and need to address).


OAuth continued - Open the JSON API via OAuth

Clients
In order to make the Ghost API accessible publicly we need to extend our support for OAuth and add different endpoints to the API for adding clients and dealing with authorization requests.
Ghost is going to support two different kinds of clients, Web and Installed Applications and JavaScript-centric applications that run on the Client Side. There is no full public access for everyone as we need to make sure that the operator of a blog is still able to deny access to clients that are not approved.
Web and Installed Applications
The Ghost API supports web, desktop and mobile application.
Public access to API endpoints:
Web and installed applications are allowed to access all API endpoints that don't require authentication by using the client authentication as described in RFC 6749 - 2.3. Client credentials (client_id and client_secret) have to be transmitted with each request to one of the public endpoints to get access.  Desktop and mobile applications are distributed to individual machines, and it is assumed that these clients cannot keep secrets. Therefore no special access rights are granted when using client credentials to access the API for now.
Authenticated access to API endpoints:
If an application wants to access endpoints that requires authentication it has to use the Authorization Code Grant method described in RFC 6749 - 4.1. This grant type requires the user to be redirected to your Ghost blog, where the user authenticates the application. After successful authentication a short lived, single-use code is returned which allows the application to acquire access and refresh token on behalf of the user.
Client Side
The Ghost API supports JavaScript-centric applications. These applications are allowed to access the Ghost API but are treated differently since they typically can't keep a secret.
Public access to API endpoints:
Requests to public endpoints must send a valid client id of a registered client. This is similar to what Google does for Google Maps.
Client side applications are allowed to a access endpoints that don't require authentication if the request comes from a known domain via ajax request (localhost is allowed during development) and contains the client id of a registered application. Checking header values does not guarantee that the client is genuine, but it should prevent random attempts to access the API and allow to revoke access from unwanted clients.
Authenticated access to API endpoints:
If a client side application wants to access an endpoint that requires authentication it has to use the Implicit Grant method described in RFC 6749 - 4.2. This grant type take into account that the application can't keep a secret and therefore provides no code to acquire access and refresh tokens but returns an access token immediately. Refresh tokens are not available and a user has to authorize the app again whenever the access token expires.
To get an access token the application has to redirect the user to a Ghost server where the user authorizes the application. After successful authorization an access token is returned which grants access to the API for a limited time.
Scopes
OAuth allows to optionally specify the scope of a client. Ghost provides the concept of app permissions and I would suggest to use the same permission model for clients as well. Permissions have to be specified when the app is registered and should be presented to the user when an user authorizes an app to access the API.
Authorize endpoint
The Authorization Code Grant and Implicit Grant flows require the user to be redirected to an authorization page that runs on the Ghost server. We have to determine where we could add this page to our ember admin and how to redirect the user back to the inquiring client.
Register a client
Adding a client is done by an authorized user that manually sets up the allowed application and then copies the client credentials to the appropriate places in the client. Examples for such registration pages can be found on the developer pages of Twitter, Facebook or GitHub.
Adding the client manually is easily doable for services that only run on one domain. In our case a client application would have to be registered for every single installation of Ghost. This would require a user to add the application to Ghost before s/he could use a 3rd party client. A draft for registering clients automatically (https://tools.ietf.org/html/draft-ietf-oauth-dyn-reg-20) has been published but isn't a specification yet.
Based on the draft for registering clients automatically I would propose to allow the registration of new clients during the authorization process. That means that a 3rd party client can send registration information along with the authorization information if the client is used with a service for the first time. The user is then asked to add the new client, if he approves the authorization process continues.
Default clients
As Ghost admin and Ghost frontend also need to access the API and authenticate using oAuth there will be two default clients that are available on every Ghost blog. client_id and client_secret are generated randomly for every blog.

Ghost admin (exists but needs update)
Ghost frontend (new)

This is an overview issue for implementing further OAuth features. Issues for implementation are:

[x] Add columns to client table (#4174)
[ ] API endpoints for clients (#4175)
[ ] Client API permissions (#4176)
[ ] Client management screen  ember ghost-ui (#4177)
[ ] Authorize screen  ember ghost-ui (#4178)
[ ] Add access control for public endpoints (Web and Installed Application) (#4179)
[x] Add access control for public endpoints (Public Clients) (#4180)
[x] Remove authentication for public endpoints (#4181)
[x] Make Ember admin work with new access control (#4182)
[ ] Implement authenticated access for Public Clients (Implicit Code Grant) (#4183)
[ ] Implement authenticated access for Web and Installed Apps (Authorization Code Grant) (#4388)
[ ] Client permissions (Scope) (tbd)

Bonus:

[x] Ghost frontend client (#4184)
[ ] Add dynamic client registration to auth screen (tbd)
[ ] Development mode for Clients (tbd)

What is the status of this? Are there instructions for logging in to your blog via OAuth in order to fetch posts?

Defo looking forward to this one!

Hi, I'm working on a sweet little native Android app for Ghost. I love the design of the web client and am planning to bring the very same design focus to the Android app. Just wanted to chime in here to support this issue.
Right now I'm hacking around the problem by using the same token-based authentication mechanism used by the web client. I know that's not secure and requires the user to essentially trust me, but with the transparency of open-source and secure client-side credential storage I should be able to make it relatively safe. As soon as the OAuth API is released I'll switch to that, of course.

Hey!!! cool @vickychijwani

Can't wait for this update

Is there a timelapse for this release ? At least is it going to be released in the near future ?
Thanks to all the devs that are putting this together! :+1:

We don't have planned release dates because we're dependent on volunteer contributions. All the information we have about the status of a project is published on the roadmap: https://trello.com/b/EceUgtCL/ghost-roadmap
We could really use a few more hands on deck to get projects like this moved forward, so if you're interested in helping out let us know.

Hi @ErisDS, what is the status of this ? How i can help you ?

@vickychijwani if you work on android app it's so cool ! And If you want we can work together , I was thinking of doing a iOS app.

什么时候能支持发布文章接口啊，我等的心好累。

Hi,
Is there a time line for the release of the web and installed application registration? I would love to be able to programmatically access the API as I'm building out a Ruby gem to backup your ghost blog to a local postgres database.

@SophieDeBenedetto
Oh, I suggest you to try Github Pages + Jekylly

Thanks @Huang-Libo. Are you suggesting that b/c GH pages + Jekyll allows for version control and lots of backups? I'm not necessarily looking to switch away from Ghost--I really enjoy using the blogging platform. I'm just looking to build a quick and easy way to backup my Ghost blog. Currently when you export your blog you get a super long string of JSON so I was going to parse that and store database records.

@SophieDeBenedetto just set up a cronjob to export the MySQL DB and the contents of your images directory. Maybe include the theme if you're not already tracking the theme through Git or Mercurial.

thanks @nuclearpengy. I should have been more clear--i'm using Ghost(Pro) so I don't think the db/file structure is accessible to me outside the Admin interface.

@SophieDeBenedetto if you're using Ghost(Pro) then backups are provided as part of the managed service.

@nuclearpengy it's my understanding that the backup offered is a JSON download? I'm planning to parse and save to a pg database. was hoping to programmatically access my blogs posts, without having to visit admin panel and click "export".

I'm closing all OAuth and most API issues temporarily with the later label.
RE: OAuth, for the next 2-3 months we'll be implementing an official Ghost OAuth login system, providing global access to all Ghost blogs with a single login. We'll be opening issues around this system soon, and I don't want to cause confusion with OAuth for the API.
JSON API Overhaul & OAuth access are currently scheduled next on the roadmap

@ErisDS  So I can't POST to /posts to publish a new blog post using the API yet?


GCE: t1.micro not supported: Server refuses SSH key

RancherOS Version: (ros os version)
1.0.0
Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.)
GCE
I'm following the instructions on https://docs.rancher.com/os/running-rancheros/cloud/gce/ to deploy RancherOS to GCE but I can't get SSH working to access the instance. I've tried using the cloud config file, project level SSH keys, instance level SSH keys, using the web console, using gcloud, using the rancher username, and using my Google username. No matter what, I just get "server refused our key" and a password prompt.

mm, that's pretty weird. we use the project level keys (yes, the user is rancher) I'll have to test later.

@tboyce021 I've just done quite a bit of testing on GCE with my project level keys, and they're working for me in 1.0.0, 0.9 and 1.0.1-rc3.
I can't reproduce the issue, so the best I can do is point you at http://docs.rancher.com/os/running-rancheros/cloud/gce/#launching-rancheros-using-the-google-console and hope there's something we're doing differently
Please re-open this issue if you have further information.

I just created an entirely new project and an instance with 1.0.0. After it started, I ran
gcloud compute ssh rancher@rancher-os --project rancher-os-tboyce021 --zone us-central1-f
which auto-generated some project-level keys for the 'rancher' user. I then reset the instance as stated in the instructions (supposedly to copy the keys to the 'rancher' user), ran the above command again, and it still just asks for a password.

It seems to just be an issue on f1-micro instances. I tried again using n1-standard-1 and it worked fine. I was hoping to see how well this runs on the free tier, but apparently the answer is "not at all".

mmm, that's very useful to know - when I tested with t2.micro last night it "worked for me" - but you know how reliable that is. (ah, yup, that's a 1GB free tier box, and you're looking at an even smaller one.
I'm working on reducing the memory use again, now that DockerCon is over :)

@tboyce021 - I have tried on micro machines and have had problems.  But I used the "small" and it worked fine.  So for now you can go smaller then the n1-standard-1 and rancheros will work.

@SvenDowideit Is it worth re-opening this ticket and changing the title to include "f1.micro"? I'm having the same problems.
Another thing is 0.9.1 set itself up but the SSH keys didn't work. 1.0.1 has been at 100% CPU for 8 hours or so and still doesn't accept SSH connections. Serial port doesn't give any useful info (last line is Booting hard disk 1...)

its probable that the t1.micro's are too small to get past the docker load of the system images. I'm working on it in the background, but :/

might be handy to add a note to the GCE docs about this limitation with micro instances (since that's what the majority of people testing rancher on GCE are going to try first).

We have title editing technology...


Create test.md

this is a test
Description
What did you change and why?
Include any supporting resources, e.g. link to a Jira ticket, GH issue, FTI, Slack, Aha, etc.
Testing instructions
Netlify link:
Checklist

[ ] Review label added
[ ] PR pointed to correct branch (main for immediate publishing, or a release branch: e.g. release/gateway-3.2, release/deck-1.17)

closing test


[skill idea] awesome to open curated random picked site

ETH2
http://beaconcha.in/
ETH1
http://etherscan.io/
https://ethstats.net/
https://www.gasnow.org/
https://studio.glassnode.com/metrics?a=ETH&m=addresses.ActiveCount
DAPP
https://www.stateofthedapps.com/
https://debank.com/
https://medium.com/quiknode/awesome-ethereum-resource-lists-dd28a9c17fc1
maybe provide sub command as awesome eth2, awesome dapp etc

dde1c9cd6c86b7f2abf767f0ef3c7ac13d5a7824


add docker-compose.yml to .gitignore

Hey @dmitrizagidulin @kayaelle
I think this does what you suggested on our call earlier this morning Dmitri (to make it easier to deploy sign-and-verify from GitHub to the DCC jff AWS instance):

adds docker-compose.yml to .gitignore
renames docker-compose.yml to docker-compose.example.yml
updates the docker section of the README

How does this apply to CU deploy of the container?
On Thu, Oct 20, 2022 at 11:16 AM Dmitri Zagidulin @.***>
wrote:

Merged #70 https://github.com/digitalcredentials/sign-and-verify/pull/70
into main.
—
Reply to this email directly, view it on GitHub
https://github.com/digitalcredentials/sign-and-verify/pull/70#event-7633357008,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFXVRRVSQKYN53IB64L3YLWEF44PANCNFSM6AAAAAARKJNX6I
.
You are receiving this because you are subscribed to this thread.Message
ID: <digitalcredentials/sign-and-verify/pull/70/issue_event/7633357008@
github.com>


Re run the stack after some changes

I am using the stack and have deployed it.
now I made some changes, like deploying ingress, but now they say that the entire stack will be replaced starting with the vcn.
how can I make my cluster stack less destructible?

its force recreate the vcn and destroy all others resources
my tfvar:

# App name suffix
app_name="Homolog"

##################################################################################################
tag_values={
	"freeformTags" = {
	    "Environment" = "Homolog-QA",
	    "DeploymentType" = "App-Cluster-Terraform"
	},
	"definedTags" = {}
}

vcn_cidr_blocks="<IP_ADDRESS>/16"
#create_new_vcn=false #tested false or true but allways recreate it
#existent_vcn_ocid="ocid1.vcn.oc1.xxxxxx" #same here

# Cluster config
cluster_workers_visibility="Private"
cluster_endpoint_visibility="Public"

# BASIC_CLUSTER or ENHANCED_CLUSTER."
cluster_type="ENHANCED_CLUSTER"

# Pool of nodes
node_pool_autoscaler_enabled_1=false
node_pool_initial_num_worker_nodes_1=3
node_pool_max_num_worker_nodes_1=5

# Cluster Tools
cert_manager_enabled=false
metrics_server_enabled=false
prometheus_enabled=false
grafana_enabled=false

# Ingress confs
ingress_nginx_enabled=false
ingress_tls=true
ingress_cluster_issuer="letsencrypt-prod"
<EMAIL_ADDRESS>

# Extra configs
#extra_route_tables
#extra_security_lists

Something similar happened to me due to the image ids of the worker node not matching the data sources after few months (filter was "last').
You can use lifecycle block under your vcn . see my fork example :
resource "oci_containerengine_node_pool" "oke_node_pool" {
  cluster_id         = var.oke_cluster_ocid
  compartment_id     = var.oke_cluster_compartment_ocid
  ...
  --- snipet
    lifecycle {
    ignore_changes = [
      node_config_details.0.size,
      node_source_details.0.image_id  # Add this line to ignore changes to image_id
    ]
  }

HTH
Clouddude


feat/FAT-13 Sync Onboarding logic

📝 Description
3 features in live-common:

Function to extract the device onboarding state from byte flags
Polling mechanism to retrieve the device onboarding state
Make the polling mechanism available as a react hook for LLM and LLD

❓ Context

Impacted projects: live-common
Linked resource(s): FAT-13

✅ Checklist

[x] Test coverage : unit tested + QA tested the logic through this POC
[x] Atomic delivery
[x] No breaking changes : only new features, not updating former features

📸 Demo
Videos have been posted on Slack from this POC
🚀 Expectations to reach
Please make sure you follow these Important Steps.
Pull Requests must pass the CI and be internally validated in order to be merged.

lgtm, the only thing I would change is starting from hex strings instead of byte arrays for the tests, like the actual apdu returned from a device in that case. But I guess it's the same thing

I think to do this, we should unit test getVersion <- it's this function that handles the raw hex string
Otherwise, it would become an integration or end-to-end test 🤓 (which could be interesting to implement, i still haven't look on our we set up the e2e tests with the bots)