Extended support, documentation, and functionalities

Documented scholarly.py
Separated Scholarly, Publication and Author into different files
Added search_single_pub to Scholarly
Fixed bibtex collection and handled exceptions
Expanded support to Chrome and Firefox Webdrivers
Randomized Selenium features for both drivers.
Implemented a no-wait policy when using ToR, for faster study collection.
Implemented expanded error handling for traffic, automation and captchas,
Moved hardcoding to a json file for improved code maintenance

Thanks for your contribution. I will have a look as soon as I find the time;)

What do you mean by?

removed the bib, since it was not working

What do you mean by?

removed the bib, since it was not working

So when I was writing my code I realized that the bib part wasn't working (when you clicked on any bib it would return a 404). While it could be a bug from google server, now it works. In my latest version I did it differently.

Ah yes, I see. I was wondering since I checked your commits and couldn't figure out what you meant by 'removed the bib'.


Can't access certain wasm-c-api memory related methods

So I was messing around with the wasm-c-api, trying to understand how wamr handles linear memory and I tried calling some methods but I always get an "undefined reference" error when trying to compile. The error occurs for the following methods:
wasm_memory_size
wasm_memory_data_size
wasm_memory_data
I know these methods work with wasmtime, and they seem to also be available in wasm_c_api.h, but not in wasm_c_api.c. Have they not been fully implemented yet, or am I missing something?
In case they're not available yet, is there any time estimate to when they will be?

No, you are not missing anything, we haven't implemented memory related APIs  yet.The fully support plan is still under discussion, you will find them as soon as they are finished.


Android demo app should allow easily loading custom scenes from GUI

This could be as simple as a text field to enter a url for an arbitrary scene file. A person with an Android phone should be able to download this demo from android.mapzen.com and put in their own scene file to quickly evaluate it.
@nvkelso @sensescape The goal of this is to make it easier for you to test scene files with tangram-es. Do you have other ideas of how we could facilitate this? We could probably do something similar with iOS, or distribute an OS X tangram.app that you could just drag-and-drop scene files onto.

I like both options (text field and on OS X drag-and-drop in addition to
text field).
On Fri, Mar 10, 2017 at 2:14 PM, Matt Blair<EMAIL_ADDRESS>wrote:

This could be as simple as a text field to enter a url for an arbitrary
scene file. A person with an Android phone should be able to download this
demo from android.mapzen.com and put in their own scene file to quickly
evaluate it.
@nvkelso https://github.com/nvkelso @sensescape
https://github.com/sensescape The goal of this is to make it easier for
you to test scene files with tangram-es. Do you have other ideas of how we
could facilitate this? We could probably do something similar with iOS, or
distribute an OS X tangram.app that you could just drag-and-drop scene
files onto.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tangrams/tangram-es/issues/1362, or mute the thread
https://github.com/notifications/unsubscribe-auth/AA0EO0nDIgUzC-N6t0a5zs-d1Izc-X96ks5rkctXgaJpZM4MZ7Qg
.


Argument for specifying dump location

An argument for specifying where to dump the Brewfile. Maybe the existing --file flag.

Oh, I got a little confused. Turns out it doesn't work if you only give it the folder path, you have to include the file name. It also doesn't autocomplete paths after typing the --file argument.

Yep, you need to pass the full file path you wish to use.


Website Request: https://rainofsnow.com

Can I request this site?
https://rainofsnow.com/mr-dior/#chapter
:3

Certainly. Unfortunately though, I am currently in the process of re-writing the application #35, so you might have to wait a bit. Most of the existing functionality are implemented, so shouldn't be long now.
P.S. Sources have been moved to a new repository novelsave_sources.

Its ok I can wait. Take your time and Thank you ☺

If you dont mind a bug here and there and some missing features, feel free to use the alpha version (The README is yet to be updated 😅).
pip install novelsave==0.7.0a2

the commands are as follows:
novelsave update <url>
novelsave compile <url>
novelsave refresh <url>

refresh runs update and then compile consecutively
So in this case the following command should suffice.
novelsave refresh https://rainofsnow.com/mr-dior/

You'll find the epubs in ~/novels under a folder named after the source (may change before full release).
P.S. I would appreciate you sharing any bugs you may find greatly.

Its ok. And sure ill notify you if i do find some bugs. Thank you so much 😘


add formatting rules for inputs/1 and inputs/2

examples show no parens for inputs -- but formatter doesn't include these!

🤔 interesting, this should happen automatically.

Ah, okay right. So maybe we're missing that extension in our ash formatter rules.

It's not, though. For some reason.

@jamilabreu thank you for your PR! We will need to figure out, however, why this isn't being done automatically in ash.

@jimsynz We're probably doing something wrong picking up dsl patches:
  use Spark.Dsl.Extension,
    sections: [@ash],
    transformers: [Ash.Reactor.Dsl.ActionTransformer, Ash.Reactor.Dsl.MiddlewareTransformer],
    dsl_patches:
      [
        Ash.Reactor.Dsl.Action,
        Ash.Reactor.Dsl.AshStep,
        Ash.Reactor.Dsl.BulkCreate,
        Ash.Reactor.Dsl.BulkUpdate,
        Ash.Reactor.Dsl.Change,
        Ash.Reactor.Dsl.Create,
        Ash.Reactor.Dsl.Destroy,
        Ash.Reactor.Dsl.Load,
        Ash.Reactor.Dsl.ReadOne,
        Ash.Reactor.Dsl.Read,
        Ash.Reactor.Dsl.Transaction,
        Ash.Reactor.Dsl.Update
      ]
      |> Enum.map(&%Spark.Dsl.Patch.AddEntity{section_path: [:reactor], entity: &1.__entity__()})


Adding KBC Game in Python

I want to add simple  KBC game  made using  PYthon in this repo.
Maintainers can you please assign this issue to me

@joshiadarshx  Sure, I'd be happy to have you contribute to this project for Hacktoberfest! 🎉 Feel free to fork the repository and work on implementing the voice assistant features using the OpenAI API. Once you're ready, submit a pull request with your changes, and we'll review and merge it. If you have any questions or need assistance, don't hesitate to ask. Looking forward to your contributions! 🚀

@joshiadarshx Sure, I'd be happy to have you contribute to this project for Hacktoberfest! 🎉 Feel free to fork the repository and work on implementing the voice assistant features using the OpenAI API. Once you're ready, submit a pull request with your changes, and we'll review and merge it. If you have any questions or need assistance, don't hesitate to ask. Looking forward to your contributions! 🚀
I am really new to python and this opensource I don't think that I will be able to add a voice assistant features in this small mini project . Will it not be accepted?sir @Techiral


How does the updateable know that himself was removed from obserable, or make others konw that

Thanks firstly, agera is amzing, but I think there is a flaw：
when we do something like network, we always cancel the behavior under some circumstances, we need a callback like onCancel, I know that the onDeactivation method may tell us all the updateable was removed, but if I use RepositoryCompiler to get a Repository, I can not know that because the onDeactivation is protected, is there anyway to achieve this?

I see multiple angles and am not sure which one suits your underlying requirements, so here they are in the same reply.
I need to dispose of resourceful objects (like Closeables) in the middle of the data processing flow in a CompiledRepository that could go nowhere because the flow is cancelled.
We've just commit a new feature that allows you to configure a "disposer" (of type Receiver<Object>) that will be called with the unused intermediate values from the compiled Repository. Give it a try!
I need to take care of something else when an Observable is deactivated, and I can't go into that Observable to override the observableDeactivated method.
If you have other responsibilities to take care of, chances are you might want to wrap the target Observable and these responsibilities into the same entity, such as a custom Observable that looks like this:
public final class WrappedRepository
    extends BaseObservable implements Repository<Blah> {
  private final Repository<Blah> targetRepository;
  private final Updatable targetRepositoryUpdatable;

  public WrappedRepository(... /* params needed to build targetRepository */) {
    targetRepository = Repositories.repositoryWithInitialValue(...)
        ... // prefer building the target repository here, because you can then
            // totally "own" it, rather than giving the external world a chance
            // to sneak in their updatables.
    targetRepositoryUpdatable = () -> dispatchUpdate();
  }

  protected void observableActivated() {
    targetRepository.addUpdatable(targetRepositoryUpdatable);
    // any additional activation handling?
  }

  protected void observableDeactivated() {
    targetRepository.removeUpdatable(targetRepositoryUpdatable);
    // any additional deactivation handling?
  }

  public Blah get() {
    return targetRepository.get();
  }
}

[Just so you're aware, onDeactivation is not a callback; it is a configuration method for the CompiledRepository.]
I just want to have an onCancel callback inside the updatable; you know, like a traditional callback interface with 3 methods: onResult, onError and onCancel.
Let's discuss "responsibility".
In a typical asynchronous call pattern, the callback is owned by the consumer code of the async method. The consumer code is also the entity that cancels the request -- the async method itself should not actively cancel its requests, or the design feels wrong. This means, at the time the consumer code cancels a request, it can simply handle the cancellation actively rather than using an onCancel method in the callback. (Please do compare this to the case where the async method could not complete the request due to other entities cancelling: the most proper outcome is an error along the line of a CancellationException, which the callback will receive via onError instead.)
In the Agera world, your code owns the updatable; or at least, the process to add the updatable to the observable and remove it from the observable. "Cancellation" is an internal concept only in the CompiledRepository; they only happen if the CANCEL_FLOW configuration is used in onDeactivation, and when all updatables are removed from the Repository. This typically means that, at the time of removing the updatable, your code will know that a network request is potentially cancelled, and can actively perform any cleanup work that the Repository's data processing flow might leave behind.
So please try rethinking the design and explore other ways to achieve the same result more directly.

To add to the comment by @maxtroy
If the API used for your request is asynchronous, the cancel method used can only work in a few way. Cancel could either mean

Don't return the value when you're done, or
Stop the execution mid way

And (3.) In both cases it's common that it also means "don't start if you haven't already started"
Using Agera the first and last will be handled for you anyway, when adding/removing updatables. The second case is handled too; For sync APIs moved to a separate thread using the goTo operator, a compiled repository can be configured to send an interrupt signal to the thread. This is done using SEND_INTERRUPT. Many standard (sync) Java IO APIs supports this mechanism already, and the operation will be interrupted.
As a last note:
If your API doesn't support sync calls (and I'd def. recommend using sync APIs with Agera!), it means that you're currently forcing the thread used in goTo to wait for an async response coming back to return the value. Whatever "wait mechanism" used it most likely will throw a checked exception saying the operation has been interrupted. This is where possible cancel methods could be called. Note however that if they themselves aren't interrupting the execution (the second case of the three above) it will have very little value.


Indents using path rules

I implemented the fixes for all issues raised, but then realized that there were still some use cases that wouldn't work correctly. For example, if two rules share a common ancestor, but it isn't the parent of both rules.  E.g.,
* address.country = "JP"
* address.period.start = "2021-01-01"

The previous approach missed this because it was only looking for common direct parents on both rules. I added 4765374 to demonstrate the broken use cases. Then I updated the code in cc1246c to walk paths backwards looking for any common ancestor.
Ready for re-review, @jafeltra!

@jafeltra asked:

If we have FSH rules that look like this:
Instance: ChainsawPatient
InstanceOf: Patient
Usage: #example
* address.city = "Tokyo"
* address.country = "JP"
* name.given = "Joe"
* address.postalCode = "01730"
* address.district = "13"

we would currently create a path rule for address that gets inserted before the first rule. Should it also create another path rule for address before address.postalCode for postalCode and district?

I thought about that, but then realized it's a very hypothetical scenario.    Since it is processing the JSON and spitting out the rules as it does so, the rules will naturally come out in fairly predictable orders.  Sure, we might not know if name comes after or before address, but we know that the address rules (or rules for any complex object) will always be grouped together. So I don't think we even need to worry about it!

@jafeltra and @mint-thompson -- ready for re-review!

I'm going to do an interactive rebase on this branch so that we can more cleanly separate out Guhan's work and he gets some Git cred for it.  Otherwise it will all get squashed together and might give me the credit as the most recent committer on this.

@mint-thompson and @jafeltra -- my rebase has dismissed your stale reviews. Please re-approve.  Thanks!


Add provider for Test-Path -Filter

Summary of the new feature/enhancement

Add FileSystem provider to list of supported filters for Test-Path. It must behave like Get-ChildItem -Filter
Set-Content -Path 'C:\Users\username\Documents\test.txt' -Value 'Hello, World!'
Test-Path -Path 'C:\Users\username\Documents\test.txt' -Filter '*.json'

Expected behavior
False

Actual behavior
True

Proposed technical implementation details (optional)

Do any currently implemented providers provide a -Filter for Test-Path? 🤔 I'm not aware of there being any.

@vexx32 don't think so but to be fair, no other built-in provider has support for Filter in any capacity (at least of those I've tested).
This wouldn't be super easy to add though I don't think. Currently it's just a property on CmdletProvider called Filter. The provider registers that it supports filters by declaring it as part of their ProviderCapabilities.  It's sort of all or nothing, so if this were added to Test-Path you'd need a new ProviderCapabilities value like FilterItemExists.  And/or maybe a new method to test ItemExists with a filter, plus new interface and/or base class to implement/inherit from.

Yeah, that's my thought tbh, the file system provider is the only one I've ever seen a filter on, so I was curious if something else had tried to put filters on Test-Path.
It's an unusual use case too; Test-Path is usually used for testing complete paths, whereas -Filter is generally used to qualify searches (Get-ChildItem/Get-Item) and to filter out certain results. I kind of get the intent here, but I'm not really sure what providing -Filter would add here; you already have the path itself, so you can test if the string ends with a specific extension with more direct methods, or use Split-Path to retrieve just the filename if you have more complex patterns to test against. 😕

Do any currently implemented providers provide a -Filter for Test-Path? 🤔 I'm not aware of there being any.

@vexx32, no. Not yet. It's not mentioned in docs at least

Yeah, that's my thought tbh, the file system provider is the only one I've ever seen a filter on, so I was curious if something else had tried to put filters on Test-Path.
It's an unusual use case too; Test-Path is usually used for testing complete paths, whereas -Filter is generally used to qualify searches (Get-ChildItem/Get-Item) and to filter out certain results. I kind of get the intent here, but I'm not really sure what providing -Filter would add here; you already have the path itself, so you can test if the string ends with a specific extension with more direct methods, or use Split-Path to retrieve just the filename if you have more complex patterns to test against. 😕

@vexx32, Get-ChildItem support two way for filtering:
-Filter
-Include/-Exclude

It must behave like Get-ChildItem -Filter

I wonder if it works:
dir C:\tmp\test1.txt -Filter "*.json"

    Directory: C:\tmp

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a---          28.04.2020    21:26             14 test1.txt

It must behave like Get-ChildItem -Filter

I wonder if it works:
dir C:\tmp\test1.txt -Filter "*.json"

    Directory: C:\tmp

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a---          28.04.2020    21:26             14 test1.txt

@iSazonov, It's another one bug definitely. Try:
 dir C:\tmp\ -Filter "*.json"

It will return only .json files. I had tested it.

Yeah I think fundamentally the way the Filter functionality is designed, it tends not to apply when you supply a completely unambiguous single file path; there's nothing for it to filter in the first place, there's only one thing it can be.
Whether that should change now is an open question, I guess.

I opened #14624 for https://github.com/PowerShell/PowerShell/issues/13764#issuecomment-706584149 bug.

I opened #14624 for https://github.com/PowerShell/PowerShell/issues/13764#issuecomment-706584149 bug.


.pullapprove.yml: Switch to v2 and other updates

This lazily copies image-spec's configuration as updated via
https://github.com/opencontainers/project-template/pull/29 and
https://github.com/opencontainers/image-spec/pull/616
Signed-off-by: Jonathan Boulle<EMAIL_ADDRESS>

LGTM

LGTM


Potential improvements for user registration

Text wrapping in affiliation field of user database page "ClinGen Curation Users"
Find way to share with coordinators and/or affiliation who is in affiliations
Create form/process for coordinators to submit affiliation changes for their EP in a structured format
Teach Clarissa how to manually change emails in the user base

@cgpreston Bullet points 2 and 3 above will be dealt with as part of federation with the GPM.

Bullet point 1 to be addressed in new issue #162

@kilodalton suggested developing an admin tool for bullet point 4.


Horizontal scrollbar is coming when pdf is zoomed to 400%. The content need to reflow to accomodate in the viewport instead of horizontal scrollbar

Attach (recommended) or Link to PDF file here:
Configuration:

Web browser and its version: chrome
Operating system and its version: MAC OS
PDF.js version: latest
Is a browser extension: No

Steps to reproduce the problem:

Open https://mozilla.github.io/pdf.js/web/viewer.html. It opens with a default pdf.
2.Go to browser(chrome) menu and increase the zoom to 400%. Horizontal scroll is coming instead of content adapting/reflowing to the viewport.

What is the expected behavior? (add screenshot)
The content should reflow such that there is no horizontal scroll bar. There should be only vertical scroll bar. Similar to liquid mode in adobe acrobat reader.

What went wrong? (add screenshot)
On zooming to 400% there are two scroll bars horizontal and vertical. There should be only vertical scroll bar instead and content in the pdf should reflow to accomodate in viewport.

Link to a viewer : https://mozilla.github.io/pdf.js/web/viewer.html

If you explicitly choose a percentage zoom value that's large enough that the document doesn't fit horizontally, then showing a scrollbar is the correct/expected behaviour since we can't very well just ignore the users choice here.
Most likely you want the "page-width" zoom-mode instead, which will always fit the document width to the available window width; closing as answered (or possibly even INVALID).

As far as I can tell, the first screenshot above comes from the Acrobat Reader app which is using the liquid mode to render the pdf. As far as I understand this liquid mode, the text and its structure (i.e. lines, paragraphs, columns, ...) is extracted from the pdf and then rendered in using usual layout (images are extracted either and inserted in the text flow).

As far as I can tell, the first screenshot above comes from the Acrobat Reader app which is using the liquid mode to render the pdf. As far as I understand this liquid mode, the text and its structure (i.e. lines, paragraphs, columns, ...) is extracted from the pdf and then rendered in using usual layout (images are extracted either and inserted in the text flow).

Given that essentially everything in PDF documents, including text, is absolutely positioned such a thing almost sounds like it's "violating" the PDF specification itself by no longer respecting the actual document layout. (Since the whole point of the format is that documents should always look the same, regardless of e.g. the OS and viewer used.)
Hence that really sounds like WONTFIX, as far as I'm concerned.

Is there any mode in pdf js which reflow the content atleast if pdf contains only paragraphs when zoom in to 400% instead of giving a horizontal scroll. So that it is easy for the reader to read in the perspective of accessibility.

Is there any mode in pdf js which reflow the content [...]

No, since that's not really how PDF documents work internally; see https://github.com/mozilla/pdf.js/issues/16015#issuecomment-1419043116

It could be something similar to the reader view mode in Firefox:

In that case, we could just call this a duplicate of https://bugzilla.mozilla.org/show_bug.cgi?id=1703168

Hi,
Just for confirmation as this information is not available anywhere in the internet.
How extent does PDF JS support PDF/UA standard regarding accessibility ? As of now the pdf js has support for tagged PDFs to support screen readers but there is no text reflow support even if the pdf is tagged( or PDF/UA supported) right ?
Currently text reflow is supported by Abode Acrobat Reader Pro even in desktop. Open a file in Adobe reader -> zoom to any percentage like 400% then click "view" -> zoom -> reflow. Text reflows in the document.


Test userflow

https://dewebhome.massahub.network/

this the message we sent internally
if you have time, we'd love to hear some feedback on the deweb landing page
https://dewebhome.massahub.network/
let us know on this form: https://forms.gle/W4cELsrc8FsaNTN6A


"window" is not available during server side rendering

Hi there, i'm using latest version react-slideshow in my  gatsby js powerd website. everything is working fine on develop mode but it throws me an error on build process. "window" is not available during server side rendering
this is my component
import React from 'react'
import { useStaticQuery, graphql } from 'gatsby'
import Img from 'gatsby-image'
import { Fade } from 'react-slideshow-image'

const fadeProperties = {
    duration: 5000,
    transitionDuration: 1000,
    infinite: true,
    indicators: false,
    onChange: (oldIndex, newIndex) => {
        console.log(`fade transition from ${oldIndex} to ${newIndex}`);
    }
}

const Slider = () => {
    const data = useStaticQuery(graphql `
        query {
            allFile(
                sort: { fields: name, order: DESC }
                filter: { relativeDirectory: { eq: "slider" } }
            ) {
                edges {
                    node {
                        id
                        name
                        childImageSharp {
                            fluid(maxWidth: 1200, maxHeight: 585, quality: 100) {
                                ...GatsbyImageSharpFluid_withWebp
                                ...GatsbyImageSharpFluidLimitPresentationSize

                            }
                        }
                    }
                }
            }
        }
    `)

    return(

            <Fade {...fadeProperties}>
                {data.allFile.edges.map(image => (

                ))}
            </Fade>

    )
}

export default Slider

I wonder how to make it works on build?

Hi @yudyananda can you check this out https://www.gatsbyjs.org/docs/debugging-html-builds/#fixing-third-party-modules and this. The package uses window to check when you resize the browser but window is a browser object and it's not available on the server.  Let me know if you're able to fix it with the instruction in the links

Hi @femioladeji many thanks for quick answer
try with creating util
util.js

export const isBrowser = () => typeof window !== 'undefined'

somepage.js

import React from 'react'

import Container from '../container'

import { isBrowser } from '../window'

import FrontSlider from '../slider/frontSlider'

const FrontHero = () => {

    return (
        <Container helper="container px-5 pt-0 pb-10 mx-auto">

                {isBrowser() && <FrontSlider />}

                    ...

        </Container>
    )
}

export default FrontHero

the result is not as i expected, the slider goes inside another div, in this case <div className="overlay block ...
another approach is using loadable-component, works fine, but it have delay on initial page loading (other element below will overlap slider position before it fully load)

@yudyananda it's weird that it's going into the <div className="overlay block ... so what happens if you comment that div?

use ternary {isBrowser() && <FrontSlider />}
modify the webpack config test: /react-slideshow-image/
comment the
 <div className="absolute .... Another weird parts <div className="absolute ... is duplicated, one with the slider inside it and the other one is the original content

sorry for bothering you, i'll get back to you with example repo

@yudyananda it's fine. Let me know when you have an example repo. I'm always here to help

I had the same issue on my gatsby Website and I solved this using loadable-components. However it is not as good as expected since, as @yudyananda  mentioned, it causes delay on page load. I am not sure what the best solution is.

@mluce194 yes you're correct. The window event is used to handle browser resizing. I'm considering using resize-observer-polyfill but I don't know if it will completely solve the SSR issue. I'll continue to make research and hopefully, I'll come up with a solution that works perfectly.

Hi @femioladeji, sorry for the late reply. You can check the repo here
not sure whats going on here but

somehow gatsby doesnt include react-slideshow component on build output
the react slideshow cause delay on initial page load
about the duplicate, i guess it has connection with relative and absolute position (from the parent and chilldren)

I really hope you can change on how react-slideshow work to make it more suitable (ssr ready) for other framework like gatsby

@yudyananda thanks for reproducing the issue. I've taken a look at it and I've fixed the issue with this PR #81 . I've released a new version (v2.0.1). You don't need any workaround to use it anymore. I've fixed it all in the package so you can remove the isBrowser check and remove the content in gatsy-node file also. There's a little tweak though. Now you have to import the css in your js file so the slider.js file will now look like this
import React from 'react'

import { useStaticQuery, graphql } from 'gatsby'

import Img from 'gatsby-image'

import { Fade } from 'react-slideshow-image'
import 'react-slideshow-image/dist/styles.css'

const fadeProperties = {
    duration: 5000,
    transitionDuration: 1000,
    infinite: true,
    indicators: false,
    onChange: (oldIndex, newIndex) => {
        console.log(`fade transition from ${oldIndex} to ${newIndex}`);
    }
}

const Slider = () => {

    const data = useStaticQuery(graphql `
        query {
            allFile(
                sort: { fields: name, order: DESC }
                filter: { relativeDirectory: { eq: "slider" } }
            ) {
                edges {
                    node {
                        id
                        name
                        childImageSharp {
                            fluid(maxWidth: 1200, maxHeight: 585, quality: 100) {
                                ...GatsbyImageSharpFluid_withWebp
                                ...GatsbyImageSharpFluidLimitPresentationSize

                            }
                        }
                    }
                }
            }
        }
    `)

    return (

            <Fade {...fadeProperties}>
                {data.allFile.edges.map(image => (

                ))}
            </Fade>

    )
}

export default Slider

As regards the positioning, I think it has to do with the div wrapping the just an overlay text.


Need to downgrade the eslint-plugin-react version to 7.14.3

Issue Description
Will have to downgrade the version of eslint-plugin-react to 7.14.3 temporarily as eslint script scan is giving the following error with the new 7.15.0 version of eslint-plugin-react.

so there is already an issue logged https://github.com/yannickcr/eslint-plugin-react/issues/2423 to eslint-config-terra to fix this.
@ Mentions
@bjankord , @ryanthemanuel

Talked in scrum, planning to pin the dep to 7.14.3 until a fix is landed upstream. We'll cut a release once we pin the version down.


Move z3_solver to be first dependency

Current PRs are failing to install z3_solver, addressing problem in this PR

Locally installing from wheel's is fine for me, however it appears there are some remote issues with it.
Making it an issue to investigate further, for now this will resolve the issues


Icons are missing

Prerequisites

[X] I have read the Contributing Guidelines.
[X] I have not leaked any internal/restricted information like screenshots, videos, code snippets, links etc.

What happened?
Hi,
We develop a product with React. We use webpack as a module bundler. However, we are having issues displaying ix icons. Sometimes they are completely missing on the whole UI. We do not have any specific case or scenario to reproduce this issue. Please see the screenshots below:

The icons that are on the screenshots above (and all the icons on our UI) are all IxIcon components. They are gone
sporadically on all the UI. Here is our package.json:
"devDependencies": {
     .....
    "copy-webpack-plugin": "^11.0.0",
    "css-loader": "^6.7.1",
    "css-minimizer-webpack-plugin": "^4.2.2",
    "echarts-for-react": "^3.0.2",
    "html-webpack-plugin": "^5.5.0",
    "mini-css-extract-plugin": "^2.6.1",
    "postcss": "^8.4.18",
    "postcss-loader": "^7.0.1",
    "prettier": "2.7.1",
    "react-chartjs-2": "^5.2.0",
    "react-refresh": "^0.14.0",
    "react-transition-group": "^4.4.5",
    "style-loader": "^3.3.1",
    "tailwindcss": "^3.4.1",
    "terser-webpack-plugin": "^5.3.6",
    "webpack": "^5.74.0",
    "webpack-bundle-analyzer": "^4.6.1",
    "webpack-cli": "^4.10.0",
    "webpack-dev-server": "^4.11.1",
    "webpack-merge": "^5.8.0"
     .....
 },
  "dependencies":
    .....
    "@siemens/ix-echarts": "^2.1.1",
    "@siemens/ix-icons": "^2.2.0",
    "@siemens/ix-react": "^2.4.0",
    "react": "^18.2.0",
    "react-dom": "^18.2.0",
     .....
  },

What type of frontend framework are you seeing the problem on?
React
Which version of iX do you use?
v2.4.0
Code to produce this issue.
This issue happens on our private repository. Here is the smallest codesandbox that I can create:

https://codesandbox.io/p/devbox/pl3yt6

Hello @cerenbattal, thanks for your insights -  I’ve attempted to recreate the issue across different browsers and frameworks, but so far, I haven’t been able to replicate it. Also your code sandbox seems to work just fine on my site, can you verify that the icon in your code sandbox is not working? Otherwise i would recommend trying to upgrade  to the newest iX version an see if this resolves your problem.

Hi @matthiashader, unfortunately, we do not have any reproducing steps for this bug. I've just installed all the required npm packages on the code sandbox with the exact versions that we use on our project.

Hi @matthiashader, unfortunately, we do not have any reproducing steps for this bug. It just happens sporadically. I've just installed all the required npm packages on the code sandbox with the exact versions that we use on our project. I assume that this bug might not be related to the device's OS version. But I want to ask anyway, is there any possibility?

Do you still recommend upgrading iX to 2.5.0?

Hello @cerenbattal - yes, I would at least try. Alternatively, I can offer you to write to our team email to organize a call so we can check it together. Without any possibility of reproducing the issue, it’s really hard to say where the problem is<EMAIL_ADDRESS>

Hello @cerenbattal - yes, I would at least try. Alternatively, I can offer you to write to our team email to organize a call so we can check it together. Without any possibility of reproducing the issue, it’s really hard to say where the problem is<EMAIL_ADDRESS>
Hi @matthiashader,
I got the same error today. We use ix-react 2.5.0.

This is the error line in the chunk file:

As I said, we use webpack.

Hello @cerenbattal - i have looked into your code example, i would adapt the main.jsx to:
`
import { StrictMode } from "react";
import { createRoot } from "react-dom/client";
import App from "./App.jsx";
import "./index.css";
import<EMAIL_ADDRESS>import {
defineCustomElements as themeDefineCustomElements,
} from "@siemens/ix-brand-theme/loader";
import { defineCustomElements } from "@siemens/ix-icons/loader";
defineCustomElements();
themeDefineCustomElements();
createRoot(document.getElementById("root")).render(

);
`
I have also prepared the simplest example i can:
https://github.com/matthiashader/react-webpack-from-scratch
If this error still occur, just let me know.


Add python warning if install a pack that only supports python 2

packs.download action will log a warning if attempt to install a pack that only supports python 2
packs.install workflow will include an extra step to check if the metadata indicates warnings (and will return a warning_list of any of the packs that had a warning - whereby warnings will only be raised if the pack supports python 2). The warning_list will also be an output of the workflow (similar to conflict_list)
st2 client, when running "pack install" will output to screen any warnings reported in the warning_list from the workflow execution.
Part of #4938

I wanted to get some feedback before I started adding UT and integration tests.
I did consider changing the download_pack so the warning was returned rather than just Success, but was concerned that might  cause integration problems if the result of that action were checked. So therefore decided to just log a warning and keep the warning as an extra result to the workflow (similar to conflicts)
Here is some output from runs. In this scenario test1 pack is python 2 &3, test2 pack is python2, test 3 pack is dependant on pack 2 & 3.
Output when use CLI to install test3 pack:
st2 pack install file:///home/centos/test3 --force

	[ succeeded ] init_task
	[ succeeded ] download_pack
	[ succeeded ] make_a_prerun
	[ succeeded ] get_pack_dependencies
	[ succeeded ] check_dependency_and_conflict_list
	[ succeeded ] download_pack
	[ succeeded ] make_a_prerun
	[ succeeded ] get_pack_dependencies
	[ succeeded ] check_dependency_and_conflict_list
	[ succeeded ] install_pack_requirements
	[ succeeded ] get_pack_warnings
	[ succeeded ] register_pack

+-------+-------+------------------+---------+------------------+
| ref   | name  | description      | version | author           |
+-------+-------+------------------+---------+------------------+
| test1 | Test1 | Pack for both    | 0.0.1   | Ammeon Solutions |
|       |       | pythons          |         |                  |
| test2 | Test2 | Pack for both    | 0.0.1   | Ammeon Solutions |
|       |       | pythons          |         |                  |
| test3 | Test3 | Pack for both    | 0.0.1   | Ammeon Solutions |
|       |       | pythons          |         |                  |
+-------+-------+------------------+---------+------------------+
DEPRECATION WARNING: Pack Test2 only supports Python 2.x. ST2 will remove support for Python 2.x in a future release.

Output from execution get on the above workflow:
st2 execution get 5f57622006b2c171a620addb
id: 5f57622006b2c171a620addb
action.ref: packs.install
parameters:
  force: true
  packs:
  - file:///home/centos/test3
  python3: false
status: succeeded (60s elapsed)
start_timestamp: Tue, 08 Sep 2020 10:51:12 UTC
end_timestamp: Tue, 08 Sep 2020 10:52:12 UTC
result:
  output:
    conflict_list: []
    message: Successfully installed packs
    packs_list:
    - test3
    - test1
    - test2
    warning_list:
    - 'DEPRECATION WARNING: Pack Test2 only supports Python 2.x. ST2 will remove support for Python 2.x in a future release.'
+--------------------------+-------------------------+------------+------------+-----------------+
| id                       | status                  | task       | action     | start_timestamp |
+--------------------------+-------------------------+------------+------------+-----------------+
| 5f576221ef7e4b4ff9e813f8 | succeeded (1s elapsed)  | init_task  | core.noop  | Tue, 08 Sep     |
|                          |                         |            |            | 2020 10:51:13   |
|                          |                         |            |            | UTC             |
| 5f576222ef7e4b4ff9e81408 | succeeded (3s elapsed)  | download_p | packs.down | Tue, 08 Sep     |
|                          |                         | ack        | load       | 2020 10:51:14   |
|                          |                         |            |            | UTC             |
| 5f576225ef7e4b4ff9e81418 | succeeded (1s elapsed)  | make_a_pre | packs.virt | Tue, 08 Sep     |
|                          |                         | run        | ualenv_pre | 2020 10:51:17   |
|                          |                         |            | run        | UTC             |
| 5f576227ef7e4b4ff9e81428 | succeeded (2s elapsed)  | get_pack_d | packs.get_ | Tue, 08 Sep     |
|                          |                         | ependencie | pack_depen | 2020 10:51:19   |
|                          |                         | s          | dencies    | UTC             |
| 5f576229ef7e4b4ff9e81438 | succeeded (1s elapsed)  | check_depe | core.noop  | Tue, 08 Sep     |
|                          |                         | ndency_and |            | 2020 10:51:21   |
|                          |                         | _conflict_ |            | UTC             |
|                          |                         | list       |            |                 |
| 5f57622aef7e4b4ff9e81448 | succeeded (2s elapsed)  | download_p | packs.down | Tue, 08 Sep     |
|                          |                         | ack        | load       | 2020 10:51:22   |
|                          |                         |            |            | UTC             |
| 5f57622def7e4b4ff9e81458 | succeeded (1s elapsed)  | make_a_pre | packs.virt | Tue, 08 Sep     |
|                          |                         | run        | ualenv_pre | 2020 10:51:25   |
|                          |                         |            | run        | UTC             |
| 5f57622fef7e4b4ff9e81468 | succeeded (1s elapsed)  | get_pack_d | packs.get_ | Tue, 08 Sep     |
|                          |                         | ependencie | pack_depen | 2020 10:51:27   |
|                          |                         | s          | dencies    | UTC             |
| 5f576231ef7e4b4ff9e81478 | succeeded (0s elapsed)  | check_depe | core.noop  | Tue, 08 Sep     |
|                          |                         | ndency_and |            | 2020 10:51:29   |
|                          |                         | _conflict_ |            | UTC             |
|                          |                         | list       |            |                 |
| 5f576232ef7e4b4ff9e81488 | succeeded (35s elapsed) | install_pa | packs.setu | Tue, 08 Sep     |
|                          |                         | ck_require | p_virtuale | 2020 10:51:30   |
|                          |                         | ments      | nv         | UTC             |
| 5f576256ef7e4b4ff9e81498 | succeeded (2s elapsed)  | get_pack_w | packs.get_ | Tue, 08 Sep     |
|                          |                         | arnings    | pack_warni | 2020 10:52:06   |
|                          |                         |            | ngs        | UTC             |
| 5f576259ef7e4b4ff9e814a8 | succeeded (2s elapsed)  | register_p | packs.load | Tue, 08 Sep     |
|                          |                         | ack        |            | 2020 10:52:09   |
|                          |                         |            |            | UTC             |
+--------------------------+-------------------------+------------+------------+-----------------+

Output from execution get on the packs.download action:
st2 execution get 5f57622aef7e4b4ff9e81448
id: 5f57622aef7e4b4ff9e81448
action.ref: packs.download
context.user: st2admin
parameters:
  dependency_list:
  - file:///home/centos/test1
  - file:///home/centos/test2
  force: true
  packs:
  - file:///home/centos/test3
  python3: false
status: succeeded (2s elapsed)
start_timestamp: Tue, 08 Sep 2020 10:51:22 UTC
end_timestamp: Tue, 08 Sep 2020 10:51:24 UTC
result:
  exit_code: 0
  result:
    test1: Success.
    test2: Success.
  stderr: 'st2.actions.python.DownloadGitRepoAction: DEBUG    Force mode is enabled, deleting lock file...
    st2.actions.python.DownloadGitRepoAction: DEBUG    Detected local pack directory which is not a git repository, just copying files over...
    st2.actions.python.DownloadGitRepoAction: DEBUG    Moving pack from /root/597177fe4c61b2c9eabc3b2c23217374 to /opt/stackstorm/packs/.
    st2.actions.python.DownloadGitRepoAction: DEBUG    Force mode is enabled, deleting lock file...
    st2.actions.python.DownloadGitRepoAction: DEBUG    Detected local pack directory which is not a git repository, just copying files over...
    st2.actions.python.DownloadGitRepoAction: DEBUG    Moving pack from /root/e1475b30771849db813af564d67d4e47 to /opt/stackstorm/packs/.
    st2.actions.python.DownloadGitRepoAction: WARNING  DEPRECATION WARNING: Pack test2 only supports Python 2.x. ST2 will remove support for Python 2.x in a future release.
    '
  stdout: ''

Screenshot from UI showing how it looks on the pack.install run:

Screenshot from UI showing the download pack warning from above run:

Example of output from CLI when install 2 packs that are only python 2:
st2 pack install file:///home/centos/packs/test2 file:///home/centos/packs/test4

	[ succeeded ] init_task
	[ succeeded ] download_pack
	[ succeeded ] make_a_prerun
	[ succeeded ] get_pack_dependencies
	[ succeeded ] check_dependency_and_conflict_list
	[ succeeded ] install_pack_requirements
	[ succeeded ] get_pack_warnings
	[ succeeded ] register_pack

+-------+-------+------------------+---------+------------------+
| ref   | name  | description      | version | author           |
+-------+-------+------------------+---------+------------------+
| test2 | Test2 | Pack for both    | 0.0.1   | Ammeon Solutions |
|       |       | pythons          |         |                  |
| test4 | Test4 | Pack for both    | 0.0.1   | Ammeon Solutions |
|       |       | pythons          |         |                  |
+-------+-------+------------------+---------+------------------+
DEPRECATION WARNING: Pack Test2 only supports Python 2.x. ST2 will remove support for Python 2.x in a future release.
DEPRECATION WARNING: Pack Test4 only supports Python 2.x. ST2 will remove support for Python 2.x in a future release.

And the execution result:
st2 execution get 5f57a999551860ca3cbac6fc
id: 5f57a999551860ca3cbac6fc
action.ref: packs.install
parameters:
  packs:
  - file:///home/centos/packs/test2
  - file:///home/centos/packs/test4
  python3: false
status: succeeded (23s elapsed)
start_timestamp: Tue, 08 Sep 2020 15:56:09 UTC
end_timestamp: Tue, 08 Sep 2020 15:56:32 UTC
result:
  output:
    conflict_list: []
    message: Successfully installed packs
    packs_list:
    - test2
    - test4
    warning_list:
    - 'DEPRECATION WARNING: Pack Test2 only supports Python 2.x. ST2 will remove support for Python 2.x in a future release.'
    - 'DEPRECATION WARNING: Pack Test4 only supports Python 2.x. ST2 will remove support for Python 2.x in a future release.'
+--------------------------+------------------------+------------+------------+-----------------+
| id                       | status                 | task       | action     | start_timestamp |
+--------------------------+------------------------+------------+------------+-----------------+
| 5f57a99a4a206e0f9ede5f9f | succeeded (1s elapsed) | init_task  | core.noop  | Tue, 08 Sep     |
|                          |                        |            |            | 2020 15:56:10   |
|                          |                        |            |            | UTC             |
| 5f57a99b4a206e0f9ede5faf | succeeded (2s elapsed) | download_p | packs.down | Tue, 08 Sep     |
|                          |                        | ack        | load       | 2020 15:56:11   |
|                          |                        |            |            | UTC             |
| 5f57a99e4a206e0f9ede5fbf | succeeded (1s elapsed) | make_a_pre | packs.virt | Tue, 08 Sep     |
|                          |                        | run        | ualenv_pre | 2020 15:56:14   |
|                          |                        |            | run        | UTC             |
| 5f57a99f4a206e0f9ede5fcf | succeeded (2s elapsed) | get_pack_d | packs.get_ | Tue, 08 Sep     |
|                          |                        | ependencie | pack_depen | 2020 15:56:15   |
|                          |                        | s          | dencies    | UTC             |
| 5f57a9a24a206e0f9ede5fdf | succeeded (0s elapsed) | check_depe | core.noop  | Tue, 08 Sep     |
|                          |                        | ndency_and |            | 2020 15:56:18   |
|                          |                        | _conflict_ |            | UTC             |
|                          |                        | list       |            |                 |
| 5f57a9a34a206e0f9ede5fef | succeeded (6s elapsed) | install_pa | packs.setu | Tue, 08 Sep     |
|                          |                        | ck_require | p_virtuale | 2020 15:56:19   |
|                          |                        | ments      | nv         | UTC             |
| 5f57a9aa4a206e0f9ede5fff | succeeded (1s elapsed) | get_pack_w | packs.get_ | Tue, 08 Sep     |
|                          |                        | arnings    | pack_warni | 2020 15:56:26   |
|                          |                        |            | ngs        | UTC             |
| 5f57a9ac4a206e0f9ede600f | succeeded (3s elapsed) | register_p | packs.load | Tue, 08 Sep     |
|                          |                        | ack        |            | 2020 15:56:28   |
|                          |                        |            |            | UTC             |
+--------------------------+------------------------+------------+------------+-----------------+

Thanks for providing the CLI examples! Everything feels right :+1:

@StackStorm/maintainers @StackStorm/contributors Anyone wants to try this new deprecation warning experience and provide the feedback? Help wanted to try this feature out.

@armab I will give this a try and post the experience/feedback here.

Hi, I spend some time testing this now but I must be doing something wrong. First I patched one of my dev environments with your changes and then I tried it on a plain new CentOS8 VM by running curl -sSL https://stackstorm.com/packages/install.sh | bash -s -- --user=st2admin --password='xxx' --dev=st2/11676 to use the artifacts build by circleci.
st2 --version
st2 3.3dev (3f3326ef7), on Python 3.6.8

For some reason the warning_list after running pack.install is always empty. I tried it with nagios, telegram and https://github.com/StackStorm-Exchange/stackstorm-test2 which is used by the unit tests as well. I also verified that all your changes are part of the installed packages.
Any idea what I'm doing wrong or any better way to test this?

Are those packs python 2 only? The test2 one you referred to isn't. The pack.yaml doesn't specify python versions - so it assumes it's both.
It only reports the warning if the pack's pack.yank states python 2 only.

Nagios as well isn't a python 2 only pack according to it's pack.yaml
I did notice discrepancies between what is shown on the exchange main page and what is in it's pack.yaml in some cases.
Eg some say python 2 only but their supported versions list both.

Thanks @amanda11, that was exactly the issue. I just trusted the info shown on the stackstorm exchange. Everything works as expected with my own packs and forks of a pack with a modified pack.yaml.
I'll run some more tests via the UI and CLI and will let you know if I find anything. So far everything matches exactly what you described above and I like the user experience.

@armab @nmaludy on the stackstorm exchange overview page where does the supported python versions come from? It doesn't seem to match the pack.yaml of files in exchange

@amanda11 from what I know that info is served from https://github.com/StackStorm-Exchange/index/tree/master/v1/packs which is updated whenever a pr is merged to master in https://github.com/StackStorm-Exchange. If there are discrepancies then it could be that in some instances(just thinking loud here) the ci for index wouldn't have run or had issues.

BTW, besides of pack install CLI warning, there might be also a good idea to log similar message for st2actionrunner or st2api during the pack install execution.

@armab Warnings that we get at moment in the actionrunner.log are:

WARNING when the pack install does a download
st2.actions.python.DownloadGitRepoAction: WARNING  DEPRECATION WARNING: Pack Test2 only supports Python 2.x. Python 2 support will be dropped in future releases. Please consider updating your packs to work with Python 3.x
The warning_list comes out in the audit:
2020-09-15 22:19:13,791<PHONE_NUMBER>38800 AUDIT base [-] Liveaction completed (liveaction_db={'status': 'succeeded', 'runner_info': {u'hostname': u'centos-7-devsource', u'pid': 12107}, 'workflow_execution': u'5f613dd12235164e0be18521', 'parameters': {u'packs_status': {u'test2': u'Success.'}}, 'action_is_workflow': False, 'start_timestamp': '2020-09-15 22:19:12.149032+00:00', 'delay': None, 'callback': {}, 'task_execution': u'5f613de0a287f1ad7e3ffe31', 'notify': None, 'result': {'stdout': u'', 'exit_code': 0, 'stderr': '', 'result': {u'warning_list': [u'DEPRECATION WARNING: Pack Test2 only supports Python 2.x. Python 2 support will be dropped in future releases. Please consider updating your packs to work with Python 3.x']}}, 'context': {u'orquesta': {u'workflow_execution_id': u'5f613dd12235164e0be18521', u'task_id': u'get_pack_warnings', u'task_execution_id': u'5f613de0a287f1ad7e3ffe31', u'task_name': u'get_pack_warnings', u'task_route': 1}, u'user': u'stanley', u'parent': {u'user': u'stanley', u'execution_id': u'5f613dd022bf8267a2bebe1b', u'pack': u'packs'}, u'pack': u'packs'}, 'action': u'packs.get_pack_warnings', 'id': '5f613de0a287f1ad7e3ffe33', 'end_timestamp': '2020-09-15 22:19:13.626455+00:00'})

@amanda11 That's awesome! Yes, that logging is more than enough :+1:
Thanks for checking.

No worries - I thought I had a log in there somewhere, but forgot to put in the examples.
I will merge.


How to assign a user to existing group using REST API?

I am not been able to find a way of assigning an existing group or team to user

am not been able to find a way of assigning an existing group or team to user while creating a user using API.


typo: Copyer -> Copier

I'm sorry for my grammatical mistakes. Now I've revised them again. Thank you for your feedback.


wf.watchApiGateway('Some API', api) errors with Cannot read property 'stageName' of undefined

I have a RestAPI  which is defined with a deploy: false flag.   I then add various methods to the api, and finally create 2 deployment stages DEV, and QA with API keys.   That all works fine.
When I added the code:
    const wf = new Watchful(this, 'monitoring', {
      alarmEmail: 'myemail@address',
    });
    wf.watchLambdaFunction('Lambda watcher', lambdaHandler);
    wf.watchApiGateway('My API', api);

I get a message at deploy time:
Cannot read property 'stageName' of undefined
Subprocess exited with error 1

If I comment out the watchApigateway it proceeds as expected, but only builds dashboard for Lambda.
Are there restrictions on API Gateway?
I also tried defining the api as  const existingAPI = apigateway.RestApi.fromRestApiId(this, 'existingAPI', api.restApiId);
but the watchApiGateway doesn't support the IRestApi, only RestAPI.
Am I missing something?   Thanks
Ken

For configuring the monitoring/dashboards for api gateway, we use the stageName from deploymentStage of the provided api. If you do not set the deploy flag as true, the default deployment stage is not created. Since you have manually created  deployment stage for your api, you probably need to assign it like so
api.deploymentStage = myStage;

Doing that would make the deploymentStage property available and hence stageName too. Let me know if doing that fixes the issue.

Thank you!  That worked great!


Voltage spikes at 5Hz in GPIO36 causing interrupts in release v3.3, v3.2.2 works fine (IDFGH-1917)

Environment

Module used:  [ESP32-WROVER-B in custom pcb]
IDF version: v3.3-51-g5e321badd-dirty
Build System:         [Make]
Compiler version: (crosstool-NG crosstool-ng-1.22.0-80-g6c4433a5) 5.2.0
Operating System:     [Windows]
Power Supply:         [USB+Battery]

Problem Description
ISR attached to interrupt of GPIO36 is being launched repeatedly at 5 Hz aprox.
Pin has external pullup to 3.3V, interrupt is configured to negative edge.
After checking with oscilloscope I see there are some spikes in GPIO36 at 5Hz aprox. These spikes go from 3.3V to 1.5V aprox, but my oscilloscope is not high-end.
My code is just connected to wifi network and doing some http request every 10 seconds or so.
In IDF v3.2.2 this does not happen. There are no spikes in GPIO36 with same code.
If I turn off wifi and go to sleep with this interrupt as wakeup, it works fine = no wakeup until real interrupt happens.
Seems related to bug 3.11 of "ECO and workarounds for bugs in ESP32" document.
Seems related to Issue #1953
I also have this option set up esp_wifi_set_ps(WIFI_PS_MIN_MODEM), but it is also setup in v3.2.2 and does not happen.
Expected Behavior
No spikes on GPIO36 as in IDFv3.2.2.
Thank you very much for your support and please let me know if you need any extra detail about this.

@lrodenasSistel Thanks for reporting, we will look into this issue. Thanks.

https://github.com/espressif/esp-idf/issues/3714#issuecomment-512141448

I have a related issue when using 36/39 as digital input for push buttons. When 2 push buttons (push to ground with 33k pull-ups) are connected to these GPI, every time one button is pushed, I see a spurious interrupt on the other input, as if they were connected.
Indeed, the wiring I have creates a small crosstalk  between the inputs (say a few x0mV drop on one GPI when the other is pressed), but that should not matter at all in the digital domain.
It feels to me that 36/39 still behaves as analogue inputs converted to digital by software and what is being caught is a sort of spurious differential. Could it be the case? To support that idea, if I filter the push button with a 470 nF, the issue does not happen, but that's a hardware modification that is difficult to do atm.
The exact same setup works fine on any other GPIO. I'm using an old IDF (3.1.5)


T update versions 51x

Preparing for a 5.1.2 release (this should be in branch 5.1.x only)

Taking this

Merged, thanks


fix(storage-resize-images): fix bug where resized image did not keep orientation of original image (Issue #290)

fixes #290
Shows the image being displayed correctly using the image's EXIF orientation property in the Mac's image viewer:

Shows the same image displayed in VScode which does not use the EXIF data orientation property:

This shows how the resized image is displayed in the firebase console (The resized image loses EXIF data) without this PR change:

This shows the resized image being displayed correctly. It doesn't have the EXIF data, but it was rotated at the time of resizing using the EXIF data orientation property:

Thank you :)


FLUID-5665: Update documentation with the change that preferences data is moved to a specific model path

This pull request is the doc change for https://github.com/fluid-project/infusion/pull/617 that needs to be merged in first.

@cindyli apparently this pull needs updating to the new framework style.

@amb26, this pull request has been updated to comply with the new framework doc style. Can you have a look? Thanks.


TypeScript config check crashes, need restart

Does this issue occur when all extensions are disabled?: Yes/No ( not sure )

VS Code Version:
OS Version:

Version: 1.87.2 (user setup)
Commit: 863d2581ecda6849923a2118d93a088b0745d9d6
Date: 2024-03-08T15:20:17.278Z
Electron: 27.3.2
ElectronBuildId: 26836302
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22000
Steps to Reproduce:
When working on large TypeScript projects the tsconfig check (at compile time) fails and returns false-positive red-squiggly-line when after the error was corrected, it is only after restarting VS Code does the false-positive resolve and no squiggly line is displayed.
Technical Specs:

11th Gen Intel(R) Core(TM) i5-1145G7 @ 2.60GHz (8 x 1498)
--
GPU Status | 2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled
Load (avg) |
Memory (System) | 15.74GB (5.27GB free)
Process Argv | --crash-reporter-id a1910042-b5bd-4fce-8c5a-3ccd149c50bf
Screen Reader | no
VM | 0%

Extensions

Extension | Author (truncated) | Version
-- | -- | --
npm-intellisense | chr | 1.4.5
vscode-eslint | dba | 2.4.4
vscode-firefox-debug | fir | 2.9.10
copilot | Git | 1.176.0
copilot-chat | Git | 0.13.1
playwright | ms- | 1.0.22
remote-wsl | ms- | 0.86.0
azurecli | ms- | 0.6.0

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


[Improvement] Improve greedy regular expressions

What would you like to be improved?
In DorisExceptionConverter.java we have a greedy regular expression that could potentially cause issues.
  private static final String DATABASE_ALREADY_EXISTS_PATTERN_STRING =
      ".*detailMessage = Can't create database '.*'; database exists";

How should we improve?
Change the regular expression to not be greedy or don't use a regular expression.

What about change it to
private static final String DATABASE_ALREADY_EXISTS_PATTERN_STRING =
".?detailMessage = Can't create database '.?'; database exists";

How about change it to
private static final String DATABASE_ALREADY_EXISTS_PATTERN_STRING =       ".*?detailMessage = Can't create database '.*?'; database exists";

I think that sounds like a better approach. If you have time, try it out and see what needs to change.

Hi @justinmclean
#3399
This PR is ready for review.


Fix up issues related to CHANGELOG.md and Versions

Packages impacted by this PR
@azure/communication-sms
Fix for CHANGELOG.md / Version issues

API change check for @azure/communication-sms
API changes are not detected in this pull request for @azure/communication-sms


Check if pass is valid before committing to disable AP and rebooting

Add captive portal thing for iOS and Android
Allow connecting to open APs

@schollz I'm using Python 2.7 so this is not tested with Python 3 :(

Hi @ilirb these look like great changes, thanks! I'll try them out over the weekend and then merge!

Sounds good 👍
I think we can make it so that if the psk is OK, connect immediately to wifi and disable hostapd without rebooting. Next PR maybe (unless you or someone beats me to it 🏎 )

One more note, RPI can do both hostapd and use wlan as a client. I tried it and was very excited as I was thinking you can serve the connect page while connecting to a client but the excitement went away pretty fast when I learned that both the client and hostapd needs to be on the same channel :doh: anyways...

@ilirb Yep there are Python3 errors.
I'm getting:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/flask/app.py", line 1982, in wsgi_app
    response = self.full_dispatch_request()
  File "/usr/lib/python3/dist-packages/flask/app.py", line 1614, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File "/usr/lib/python3/dist-packages/flask/app.py", line 1517, in handle_user_exception
    reraise(exc_type, exc_value, tb)
  File "/usr/lib/python3/dist-packages/flask/_compat.py", line 33, in reraise
    raise value
  File "/usr/lib/python3/dist-packages/flask/app.py", line 1612, in full_dispatch_request
    rv = self.dispatch_request()
  File "/usr/lib/python3/dist-packages/flask/app.py", line 1598, in dispatch_request
    return self.view_functions[rule.endpoint](**req.view_args)
  File "startup.py", line 149, in signin
    valid_psk = check_cred(ssid, password)
  File "startup.py", line 87, in check_cred
    f.write(result)

This is "bytes" problem with Python2->3.
And also you need () around the print statements.
You've already done a lot so I don't want you to go through making everything Python3 compatible. If you do want to make it Python3 compatible, I will wait for that. If not I can just merge your stuff into a new branch so I can work on it.

Looks like only the print statements needed change (which I've fixed), I think it should be good now.

Okay, awesome! Very very nice work, thanks


Simple adversarial tests for cw721 staking.

This adds some adversarial tests to the cw721 stake voting module which focus on making sure it correctly updates voting power in the face of strange query and staking events.

Codecov Report
Base: 93.06% // Head: 93.14% // Increases project coverage by +0.08% :tada:

Coverage data is based on head (612fd31) compared to base (2fc4715).
Patch has no changes to coverable lines.

Additional details and impacted files
@@                    Coverage Diff                     @@
##           zeke/cw721-stake-tests     #530      +/-   ##
==========================================================
+ Coverage                   93.06%   93.14%   +0.08%
==========================================================
  Files                          39       39
  Lines                        3603     3603
==========================================================
+ Hits                         3353     3356       +3
+ Misses                        250      247       -3

Impacted Files
Coverage Δ

...cts/voting/cwd-voting-cw721-staked/src/contract.rs
98.13% <0.00%> (+1.86%)
:arrow_up:

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

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

Great!


Add EMG as Modality

should MotorObservatory be a Platform? @dyf

@saskiad current format is name + abbreviation for all modality. confirming:
class name: Electromyography
name: electromyography
abbreviation: emg
enum name: EMG

yes that's correct! I'd make the abbreviation EMG (all capitals) too.


Point-of-interest Cards

Hi. I'd love to see a way to design "point-of-interest" cards just like the one found on https://www.inchoatethoughts.com/dungeon-masters-guide-to-neverwinter (a card sample is https://www.inchoatethoughts.com/wp-content/uploads/2021/12/BeachedLeviathan-scaled.jpg ).

You can definitely do this using the package as a start, but it will likely never have the functionality out of the box. You will need to research the steps, but the easiest way would be to:

Set the page size to a half page with small margins.
Create a new pagestyle with cleared headers and footers (re-add the page background if you want it).
Set three columns.
Place a picture in the first column (its width can be bigger than \textwidth to cheat into the column separator
Place text in second column
Place a sidebar in the third column
Use Adobe Reader to print. It has a print method that lets you print multiple small pages onto a normal-sized page.

Great thanks! I'll try it!


enhancement: INTERNALS.md

This will help people understand the internal architecture.

https://github.com/marc2332/freya/blob/main/CONTRIBUTING.md


adding platform_version method with satisfies? helper method

See #125 as well as https://github.com/chef/omnibus-software/pull/531#issuecomment-164175616. Added a new platform_version method that returns the platform version but also provides a satisfies? helper method for checking version constraints.
I'm totally open to a different way of implementing this, but this felt like the simplest way to approach.
Thanks for taking a look, @sethvargo :)

@sethvargo I followed your advice, and I agree this is a simpler approach. Care to have another look? :smile:

Thanks @sethvargo  :)


2.x Merging multiple updates into reactive_registry refactoring branch

NetflixOSS » eureka » eureka-pull-requests #309 FAILURE
Looks like there's a problem with this pull request

NetflixOSS » eureka » eureka-pull-requests #311 FAILURE
Looks like there's a problem with this pull request

NetflixOSS » eureka » eureka-pull-requests #312 SUCCESS
This pull request looks good


ARROW-17717: [R] Lintr error on CI

The new release of lintr has a new feature - giving a warning when code is commented out - which is causing the lintr-containing CI job to fail.  We could have pinned to a previous version of lintr, but that seem like a useful feature & the lines of code which trigger it seem like reasonable exceptions, so I've just added a #nolint flag on each of them.

DuckDB failure will be unrelated to these changes. Wouldn't usually merge with a pending review but given this is such a trivial change and already has one approval, I'll merge this now so that people working on other PRs can rebase and not have failing CI.


proposal: Reduce default export from each of codes.

Motivation

vscode (tsserver)'s "Find All Reference" does not list up references of the symbol properly (https://github.com/Microsoft/TypeScript/issues/9081). Therefore, we cannot use it factually for types almin provides. I think this decrease the productivity which we got by transition to TypeScript.

Today's programming with static typed language including TypeScript stands on corporating with IDE. I feel it's better to advance it.

Our codes has both of named export and default export. This is a chance to sort the style.

Detailed Design
Change all default export to named export.
Drawback

This is a breaking change.

We have already caused some breaking changes by transition to TypeScript & some refactoring to clean up codes. I think it is not a serious problem to add more breaking changes.

Incompleteness of IDE enforces our coding style.

I also feel this is enforcement by IDE incompleteness. JetBrains' IDE including WebStorm does not have this problem.
But today's programming with static typed language stands on IDE. It's an obvious fact even if we don't like it.
If there is only WebStorm or other JetBrains' IDE in JavaScript/TypeScript world, we don't have to change our coding style. But there is also visual stuidio family which is empowered by tsserver. We cannot avoid it, I think.

@azu how about do you think?

I open the proof of concept of this proposal (https://github.com/almin/almin/pull/94).

It seems that VSCode find all rereference on default exports symbol.

Open UseCase.ts
Put Cursor to import |UseCaseContext| from "./UseCaseContext";
Call "Find All Reference"
Compare results with search "UseCaseContext"

Is It not happen in raw .ts source code?

Could it be happen when we use import xx from "almin"?
Is it happen in use .js and .d.ts source code?

Our codes has both of named export and default export. This is a chance to sort the style.

I half agree with that.
I want to avoid mixing default and named exports in a single file.

vscode (tsserver)'s "Find All Reference" does not list up references of the symbol properly (Microsoft/TypeScript#9081).

Sorry. I retry on vscode 1.9.1 (tsserver 2.1.6), then I did not reproduce this problem.

Sorry. I retry on vscode 1.9.1 (tsserver 2.1.6), then I did not reproduce this problem.

In some case, we reproduce this problem.

In the case of export default class XXX {}, then "Find All Reference"  works fine.
But in the case of class XXX {} export default XXX, then "Find All Reference" does not works well.

But in the case of class XXX {} export default XXX, then "Find All Reference" does not works well.

This pattern is bad on defatult export.
I have no motivation of this change, but I don't reject this change.
Ok. We could start working on the PR #94


tinymce with codesample & Text.pre2htmlentities

I try to use tinymce plugin with codesample, but I am having a issue on rendering post content: it render without highlight. I found that in class Text in function pre2htmlentities section with
-tag's attributes is missing.
I think it must be like that:

return preg_replace_callback('/
(.*?)
/imsu',
create_function('$input', 'return "
".htmlentities($input[2])."";'),
$string);

I made mistake. There is right code:

return preg_replace_callback('/
(.?)
/imsu',
create_function('$input', 'return "
".htmlentities($input[3])."";'),
$string);

Because the problem is related to TinyMCE you can open an issue at
https://github.com/tinymce/tinymce

I don't think so because in post-file data saved correctly with necessary attributes.

<?php
    // Plugins Site Head
    Theme::title();
    Theme::plugins('siteHead');
?>

But on reading and rendering the attributes are lost.

You cannot use code with TinyMCE. It's converted to HTML entities.

No no no. I try to explain to you:
TinyMCE + codesample plugin generates code section with highlight.

It save html entities without highlight because prism.js makes highlight on client-side and not modifies source of post.

But on rendering post Text.pre2htmlentities function is loosing ONLY pre-tag attributes, and all remaining code is rendering correctly.

There was some problem with ParsedownExtra, I fix it on the version 2.0.


chore: bdd-spring-1576838750 to 0.0.1

chore: Promote bdd-spring-1576838750 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


[GHSA-x9vc-6hfv-hg8c] Npgsql vulnerable to SQL Injection via Protocol Message Size Overflow

Updates

Affected products
Description
References

Comments
I'm a maintainer for Npgsql. It was unclear to us the security vulnerability author provided the template for the advisory, and that we had to edit it. The suggested changes trim down the summary, remove the POCs links and provide the correct affected and patched versions.

Hi there @paul-gerste-sonarsource and @NinoFloris! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository.
This change will be reviewed by our Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory

@advisory-database could you please take a look? Users are opening quite some issues and PRs (7 so far over here) related to this. Our apologies for the mistake, we were unfamiliar with the GitHub process.

any idea how long the change needs to be in place before it'll stop being flagged as a NU1903?  I would have thought it'd get checked "each time" but maybe there's some level of caching involved. (I realize the answer is probably not known from this repo's maintainers but...)


Exception while invoking method 'jitsi:updateTimeout' (Black screen in Jitsi Meet View.)

Describe the bug

Black screen in Jitsi Meet View.
To Reproduce

Go to Video Chat
Start a video chat with a user or in a channel or try to join a video call

Server Log

Checking: executePostMessageSent
I20190512-14:38:52.009(0) Exception while invoking method 'jitsi:updateTimeout' TypeError: Cannot set property 'msg' of undefined     at MethodInvocation.jitsi:updateTimeout (app/videobridge/server/methods/jitsiSetTimeout.js:36:4)     at MethodInvocation.methodsMap.(anonymous function) (app/lib/server/lib/debug.js:73:34)     at MethodInvocation.methodMap.(anonymous function) (packages/rocketchat_monitoring.js:2731:30)     at maybeAuditArgumentChecks (packages/ddp-server/livedata_server.js:1767:12)     at DDP._CurrentMethodInvocation.withValue (packages/ddp-server/livedata_server.js:719:19)     at Meteor.EnvironmentVariable.EVp.withValue (packages/meteor.js:1304:12)     at DDPServer._CurrentWriteFence.withValue (packages/ddp-server/livedata_server.js:717:46)     at Meteor.EnvironmentVariable.EVp.withValue (packages/meteor.js:1304:12)     at Promise (packages/ddp-server/livedata_server.js:715:46)     at new Promise ()     at Session.method (packages/ddp-server/livedata_server.js:689:23)     at packages/ddp-server/livedata_server.js:559:43
Screenshots

Devices and Versions

Android 6.0 / 7.0 / 9.0
Version 1.0.2 behind Nginx Proxy.
App Engine 1.4.2
Database Migration143
PID 1
Runnung Instance1
OPlog Enabled

Mobile device model and OS version: (e.g. "Nexus 7 - Android 6.0.1")
Additional context

The bug with the black screen is already fixed on app version 3.5.0


WIP: Page Component

Checklist:

[ ] Documentation
[ ] Tests
[ ] Ready to be merged

Deploy preview for affectionate-nobel-f3a8ec processing.
Built with commit fdde922ab4b14dd5daecdb62736b5091c7bc428b
https://app.netlify.com/sites/affectionate-nobel-f3a8ec/deploys/5be05b5982d3f1196f3d0c38

Codecov Report

Merging #451 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #451      +/-   ##
==========================================
+ Coverage   99.72%   99.73%   +<.01%
==========================================
  Files          77       80       +3
  Lines         370      380      +10
  Branches       15       15
==========================================
+ Hits          369      379      +10
  Misses          1        1

Impacted Files
Coverage Δ

components/panel/src/index.js
100% <ø> (ø)
:arrow_up:

components/main/src/index.js
100% <ø> (ø)
:arrow_up:

components/top-nav/src/index.js
88.88% <ø> (ø)
:arrow_up:

components/page/src/atoms/width-container.js
100% <100%> (ø)

packages/constants/src/index.js
100% <100%> (ø)
:arrow_up:

components/page/src/index.js
100% <100%> (ø)

components/page/src/atoms/main.js
100% <100%> (ø)

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 3ac7d2a...ad278df. Read the comment docs.

This is a purely visual component and has 100% coverage through snapshots so marking the tests as done.

Not sure why Chromatic is not displaying the full component, but it's appearing fine in storybook so have approved


Dashboard fix enhancement

Check the changes and push the commits. I'm attaching a screenshot for reference
Thank you

Okay i will change that
On Wed, 22 Apr 2020, 2:05 pm Pavan Kumar<EMAIL_ADDRESS>wrote:

@Impeekay commented on this pull request.
In src/components/dashboard.js
https://github.com/Impeekay/pi-sniffer-frontend/pull/1#discussion_r412784668
:

Segment,
SegmentGroup,
Header,

Checkbox,
Label,
Table,
Dimmer,
Loader,
Message
} from "semantic-ui-react";

if we're using bootstrap, no need of semantic UI, use either of the two.
Not both
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Impeekay/pi-sniffer-frontend/pull/1#pullrequestreview-397965319,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKJE63QQXTOTDZRLTAM4PCTRN2T4RANCNFSM4MNTXQMA
.

Yeah fine i will do the necessary changes and push the commits
On Wed, 22 Apr 2020, 2:11 pm Pavan Kumar<EMAIL_ADDRESS>wrote:

@Impeekay commented on this pull request.
In src/containers/dashboard.js
https://github.com/Impeekay/pi-sniffer-frontend/pull/1#discussion_r412789105
:

@@ -2,6 +2,15 @@ import React from "react";
import { fetchPiData } from "../api/piData";
import DashboardComponent from "../components/dashboard";
import moment from "moment";
+import 'bootstrap/dist/css/bootstrap.min.css';

same remove this import
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Impeekay/pi-sniffer-frontend/pull/1#pullrequestreview-397970344,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKJE63QAN3XHDTQ47GH6FSTRN2UT5ANCNFSM4MNTXQMA
.

Made the necessary changes check once


release: release 1.1.0

:robot: I have created a release beep boop
1.1.0 (2024-12-17)
Features

about: add george herber's prayer (0f2d4f7)
ci: adding linter (#9) (d01fecf)
config: add analytics (#8) (6f06022)
config: custom domain and icon (6d29580)
config: fix logo and tags (#3) (0fa8179)
layout: rework blog layout to prayer book (11ad1b6)
prayer: add prayer for husband (#7) (92c0a25)
prayer: add prayer for kid and wife (a01a449)
prayer: adding luke's prayer (#6) (3d63c4f)
prayer: adding prayer for family (#10) (67a6dbc)
prayer: complete prayer for wife and child (#5) (eaa3f6a)

Bug Fixes

next 15 async api (5f717a6)
prettier, yarn, next config (dac66b1)
tags: fix project links (#4) (b3d51e6)

Build Related

adding dependabot (a33a209)
deps-dev: bump @types/node from 22.10.1 to 22.10.2 (#30) (2b87bee)
deps-dev: bump @typescript-eslint/eslint-plugin (#27) (fb656ce)
deps-dev: bump @typescript-eslint/parser from 8.16.0 to 8.17.0 (#16) (54f2c46)
deps-dev: bump @typescript-eslint/parser from 8.17.0 to 8.18.0 (#21) (277a892)
deps-dev: bump eslint from 9.16.0 to 9.17.0 (#33) (6d1306c)
deps-dev: bump eslint-config-next from 15.0.3 to 15.0.4 (#25) (5da84b3)
deps-dev: bump eslint-config-next from 15.0.4 to 15.1.0 (#34) (d712f3c)
deps-dev: bump lint-staged from 15.2.10 to 15.2.11 (#31) (6119e1b)
deps-dev: bump prettier from 3.4.1 to 3.4.2 (#32) (72d625e)
deps: bump @grpc/grpc-js from 1.12.3 to 1.12.4 (#24) (2bb2ae4)
deps: bump @next/bundle-analyzer from 15.0.3 to 15.0.4 (#22) (8d34d02)
deps: bump @next/bundle-analyzer from 15.0.4 to 15.1.0 (#35) (e5ece30)
deps: bump nanoid from 3.3.7 to 3.3.8 in the npm_and_yarn group (#28) (e158b9a)
deps: bump next from 15.0.3 to 15.1.0 (#29) (3a02382)
deps: bump next-themes from 0.4.3 to 0.4.4 (#20) (8f62093)
deps: bump tailwindcss from 3.4.15 to 3.4.16 (#18) (46e1a70)
deps: version updates (fafef59)
update release process (ab0b1ba)

Chores

remove newsletter api (cb054e3)

Documentation

adding contributor guide (82179c1)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v1.1.0
:sunflower:


feat: Add ros2_control doxygen documentation support

Add GitHub workflow step to checkout ros2_control
Add breathe settings to conf.py

This is in reference to ros2_control #332

Yes guys please fix it in whatever way we can :D I personally prefer the deployment script as that allows (or at least used to) local testing and keeps all the deployment logic in one place. However I had no time for fixing it and not likely I will have in the near future.

@destogl and @bmagyar, my recent commits show the fully converted workflows to GitHub actions. I added documentation on how you can locally test the workflows to the README.md to address @bmagyar's concern. I still think this way is easier as it requires less code maintenance from us for any future changes (though that does require using an external package to make it really easy). Let me know what you think.

Thanks very much for the effort, especially for the readme ;)


fix ip_filter issue when a TF manifest has IP filters sorted in a dif…

…ferent way than on Aiven side

Unrelated Test failure; merging anyway, we should address the mysql flakiness though


The OpenAI API key from other services isn't working.

First, I tried the OpenAI API. I simply inserted the key, and everything works.
I wanted to try the new o1-mini model, but this model isn't available on my OpenAI account.
I bought an API key for o1-mini from the openrouter.ai website. But now the problem is that it doesn't work at all. I changed the URL as described on the website, but I just get errors like "Another non-200-range status code was received: 404 <Response [404 Not Found]>". How can I fix this?

The issue was resolved. I just needed to set the base URL up to /v1. not full URL


hasNext() doesn't work correctly if a filter is applied.

It seems that the hasNext() check doesn't work correctly when a filter is applied:
                    filter: function(image) {
                        return image.tags.indexOf("MY-TAG") >= 0;
                    },

Let's say that the get property  is set to user and we receive 100 images. Applying the tag filter, the images used to calculate the hasNext check probably are still 100 and the has_next function returns true even when I've already shown the last filtered image.

You could limit the number of image per request by using limit key.
limit:10,
after:function(){
  if(!this.hasNext()){
   loadButton.setAttribute('disabled','disabled');
  }
  }

This works with me.


Remove prime level from TagSet

This removes the prime level from the TagSet and moves it into the Index.
There is also some code cleanup. Some notation is added to various functions to use keyword args to find/filter for indices with specified tags and prime levels, for example:
julia> i = Index(2; tags="Site", plev=2)
(dim=2|id=725|"Site")''

julia> j = Index(2; tags="Site", plev=1)
(dim=2|id=349|"Site")'

julia> is = IndexSet(i,j)
(dim=2|id=725|"Site")'' (dim=2|id=349|"Site")'

julia> isp = prime(is; tags="Site", plev=2)
(dim=2|id=725|"Site")''' (dim=2|id=349|"Site")'

julia> findindex(isp; plev=3)
(dim=2|id=725|"Site")'''

The only breaking change here (should be) removing the notation ("Site",1) that used to mean a TagSet with tag "Site" and prime level 1, but I don't think that was used very much anyway.

I think this is a good improvement in terms of better structuring of the code, and also makes user inputs to be a bit nicer (e.g. not having to think about the interplay of tags and primes). Good use of keyword arguments for the priming functions too. Thanks for the hard work on this!


[pulsar-io] Elasticsearch sink support for Elastic 8

Motivation
OpenSearch high-level rest api client does not support Elastic 8 servers.
There are some hardcoded request fields that are no longer supported in ES 8 and the server throws an error. (Full guide). For the ES Sink usage the first problem I found was about createIndex request for the field "type" (include_type_name in request, type in responses).
Elastic has a guide to softly migrate to newer installation using custom http headers.
We are using OpenSearch client which doesn't support "application/vnd.elasticsearch+json;compatible-with=7" content-type.
The best solution is to migrate from high-level rest client to the official Elastic java client which is Apache 2 licensed.
See the License page

Update: The Java HLRC has been deprecated in 7.15.0 in favor of the Java API Client. The Java API Client is licensed under Apache 2.0.

Elastic java-client is not compatible with OpenSearch.
The solution is to keep both the client (opensearch high-level and elastic java-client) and use the proper one based on the target server.
Modifications

Added a new configuration property: compatibilityMode that accepts:

AUTO (default): it will discover the server version and choose the right client implementation
ELASTICSEARCH: Force to use the ES java client
ELASTICSEARCH_7: Force to use OpenSearch client. It's better to use the OpenSearch implementation for ES7 since it is more "tested" in production and it is the current implementation. (that's a conservative choice to avoid regression while upgrading Pulsar)
OPENSEARCH: Force to use OpenSearch client

Created a new interface RestClient with the two different implementations.
Created a new BulkProcessor API (very similar to the HighLevel rest API client one) to handle bulk requests with the following features:

Multi-thread async requests
Threshold based on number of operations
Threshold based on byte sizes of operations
Periodic auto flush

Moved all the tests (both unit and integration) that are using the container to run with both ES 7,ES 8 and OpenSearch docker containers.

Verifying this change

[x] Make sure that the change passes the CI checks.

This change is already covered by existing tests, such as (please describe tests).

tests under pulsar-io/elastic-search
Pulsar Sink integration tests

Documentation

[x] doc

/pulsarbot rerun-failure-checks

/pulsarbot rerun-failure-checks

/pulsarbot rerun-failure-checks

@lhotari could you please explain to me how to rerun the failed job? I can't find the button

@lhotari could you please explain to me how to rerun the failed job? I can't find the button

The workflow needs to finish before it's possible to rerun failed jobs. That seems to be a limitation compared to the previous solution. The button to rerun failed jobs is only visible to Pulsar committers. For others, it's possible to use /pulsarbot rerun-failure-checks after the workflow has completed.
Yesterday GitHub Actions build queue was very long so that caused delays. When there aren't queues, the workflow finishes in about 1h 20minutes.


useFetch doesn't set isLoading: true in Reloading State

Description
According to the useFetch documentation the Reloading State should have isLoading: true. However, this does not seem to be the case. When I run the typeahead API example and add a console.log() you can see that loading is never true after the initial phase:
https://user-images.githubusercontent.com/5128166/181120258-39e4ee73-f3b8-4db1-bbfe-f1daa1cfc96b.mp4
Raycast version: 1.38.2
Steps To Reproduce

Build and run the typeahead search example
Use the typeahead example and notice that the loading state is not shown after the first time it's been shown

The current behavior
isLoading is not true in the Reloading State.
The expected behavior
isLoading should be true in the Reloading State.

Ah good catch! Not sure how I missed that...
Should be fixed in 1.0.7


feat: opt node selectors for registry and sync

Optional node selectors for k8s deployment.
This is useful for me as I need to specify which node groups my Apicurio Registry can be assigned to. Could be useful to others as well.

closing in favor of #14

Thanks for contribution, will be available in 2.2.0.


Git Alias Commands

Oh-my-zsh currently ignores aliases in ~/.bash_profile. Is there any way to add aliases to my zshrc?
Trying to add this:
function acp() {
    git add .
    git commit -a -m "$1"
    git push
}

You can add this exact same thing to ~/.zshrc, at the end of it to prevent
it from being overridden by oh-my-zsh.
The same with any other aliases you need to add.
—
Marc

I get a zsh: command not found: acp adding the above alias to the end of .zshrc.

Ok, have you restarted the terminal? You need to restart each time you make
a change to zshrc. Also check you didn't misspell the function name or
something.
I'm just trying to rule out basic problems, as you see 😁

Thanks @mcornella , restarting the terminal did it. :+1:

I figured 😊. A shortcut I use all the time is just running "exec zsh".
This will run zsh and put it as the main process, therefore zshrc will be
re-read.
Cheers
—
Marc


[WIP] Add json parse and stringify function to jerryscript c api

Sorry, I just realized that this is a WIP PR.


Add last Node LTS version image to the cache

Given https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2004-README.md#cached-docker-images the Node v14 image is not cached yet. As Node v14 is the active LTS it could justify to have it cached to speed up a lot of GitHub action run.
Tool information

Tool name: Node
Add or update? Update
Desired version: 14
Approximate size:

Area for Triage:

JavaScript and Node.js
Question, Bug, or Feature?:
Feature
Virtual environments affected

[x] alpine
[ ] Ubuntu 16.04
[ ] Ubuntu 18.04
[x] Ubuntu 20.04
[ ] macOS 10.15
[ ] macOS 11.0
[ ] Windows Server 2016 R2
[ ] Windows Server 2019

Are you willing to submit a PR?
Yes if you point me out where is the script to generated docker cached images.

Hello @armandabric @shouze,
Thank you for contacting us.
As soon as we make a decision regarding your request, we'll let you know.

Hi @armandabric,
thanks for the suggestion, I added this issue to our backlog, we will let you know once changes are merged and available.

@armandabric we've added node14 & node14-alpine to all Ubuntu images. The new image rollout will start on Monday and take 3-4 days.

That's a freat news! This will avoid a lot of computation on a lot of GitHub action run :horse_racing: :dash:

@armandabric the images have been deployed!
I'm going to close the issue. Please feel free to contact us if you have any concerns.
Thank you!


Consumption Unit?

The problem
I wonder if the unit used for consumption should be W instead of Wh?

What version of Home Assistant Core are you running?
2024.3.3
What type of installation are you running?
Home Assistant OS
What version of the integration are you running?
0.7.2
Device description
panasonic 9 kw monoblock
Is the integration loading?
Yes
Is the adapter able to connect to the Aquarea Smart Cloud with a stable internet connection?
Yes
Are you able to perform the action you're trying to with the Aquarea Smart Cloud Site/App?
Yes
Area of the issue
No response
Anything in the logs?
No response
Additional information
No response

Hi @MorVes,
The integration doesn't expose any power consumption sensor. Aquarea API only provides us with the energy consumption (kWh) and those are the units the entities use.

I believe you, but then I don't understand this:

Think of this like your can give you the average fuel consumption of your last trip. Nobody can tell what was the exact value of the injected fuel into the engine at any moment during the trip.
(I'm just guessing from the previous answers -> ) The API provies with averages (kWh) what you see in HA is most probably an interpolated graph.


Zoom the view / font_size?

Does Fastmate.app offer a means to Zoom (in and out) the view / font_size?
Thanks for making the app!

Hi! It does not at the moment, sorry. I'm looking into if I can easily enable it!

Fixed in v1.8.0, thanks for the request!

Fantastic, thank you @joelekstrom !
Unfortunately, I can't get v1.8.0 to open on my system, and I'm running macOS 10.14.6, so I can't try v1.8.1 either.  :-/
Thanks in any case for driving this project, I do hope to be able to run the app someday.

@johnnyutahh Sorry to here that! Could you try the steps here to disable Gatekeeper for Fastmate? That should fix issues with launching the app: https://disable-gatekeeper.github.io/

Actually - I notarised a 1.8.0 build, please try that instead:
Fastmate-1.8.0-notarised.zip

Much appreciated. I downloaded and ran the v1.8.0 per below, and it seems to have the same behavior as what I tried a few hours earlier: the app seems to "flash open" (or form what little I can see; some frame pops up for what seems like less than a tenth of a second) and then disappears.
I see no "Allow apps..." Fastmate stuff listed at the Security & Privacy settings pref, like I might otherwise expect.
@joelekstrom - I'm happy to try other things, too. I did not yet execute any method/steps/procedure from https://disable-gatekeeper.github.io.

Actually - I notarised a 1.8.0 build, please try that instead: Fastmate-1.8.0-notarised.zip

@johnnyutahh follow the instructions in the guide mentioned first if you could...this will rule out any gatekeeper issues firstly.
Disabling Gatekeeper for one application only
Using Finder
1. Open Finder and navigate to the Fastmate application you just downloaded.
2. Right-click the application and choose Open.
3. Click Cancel in the confirmation dialog that appears.
4. Right-click the application a second time and choose Open again.
5. Click Open in the confirmation dialog that appears.
You only have to do this for the first application start. You can start the application as usual afterwards.

I performed the following, a couple times (with the latest .zip download). Same problems.
I can try generally-disabling Gatekeeper later (pls remind me if you can?). For now, I have a growing doubt this is a Gatekeeper-related problem.
On 2022-01-31 11:45 AM, Josh wrote:

Disabling Gatekeeper for one application only
Using Finder

Open Finder and navigate to the Fastmate application you just downloaded.
Right-click the application and choose Open.
Click Cancel in the confirmation dialog that appears.
Right-click the application a second time and choose Open again.
Click Open in the confirmation dialog that appears.

I would agree with your suspicions that this may be another issue.  Where you running the Fastmail.app from?  Downloads?  Applications?
Here are the instructions for globally disabling gatekeeper - please remember to re-enable it after testing.
Disabling Gatekeeper permanently
Open a terminal by pressing Cmd + Space, enter “Terminal” and open the application.
Run the following command: sudo spctl --master-disable. Enter your administrator password when requested.
Gatekeeper is now disabled permanently.

Solved!  Details below. Thanks @jcsteele for your diligent effort, much appreciated.
All the open cmds in the following session succeeded. Fastmate.app now runs on my macOS... and supports zooming!  It's a beautiful thing.
Question: is running (Fastmate.app) withGatekeeper=globally_disabled, then running again Gatekeeper=globally_enabled expected to succeed like this? If not, I'd like to invesigate further to see if there possibly something else happening here.
$ sudo spctl --master-disable
$ sudo spctl --status
assessments disabled
$
$ open /Applications/Fastmate.app
$
$ cd /Applications
$ sudo mv Fastmate.app/ Fastmate-1.8.0.app
$ cd
$
$ open /Applications/Fastmate-1.8.0.app
$
$ sudo spctl --master-enable
$ sudo spctl --status
assessments enabled
$
$ open /Applications/Fastmate-1.8.0.app
$
$ ls -d /Applications/Fastmate-1.*
/Applications/Fastmate-1.7.0.app  /Applications/Fastmate-1.8.0.app
$
$ sw_vers
ProductName:	Mac OS X
ProductVersion:	10.14.6
BuildVersion:	18G9323
$
$ date
Mon Jan 31 13:18:10 CST 2022
$

Well this is interesting, thanks for trying all this stuff. Yes, Gatekeeper enabled should work with the new notarised build so I was very surprised you saw the issue again with that. Was it the same exit code 9 thingy?


Cannot use flutter from other directory

Steps to Reproduce
I follow the instruction of https://flutter.dev/docs/get-started/install/macos, and everything goes well in user's home directory. But in other directory flutter don't work.
System information
MacOS Catalina
Version 10.15.1
Logs

In user's home directory:
(base) ➜  ~ which flutter
workspace/flutter/bin/flutter

In other directory:
(base) ➜  my_app  flutter run
zsh: command not found: flutter

(base) ➜  ~ flutter doctor -v
[✓] Flutter (Channel stable, v1.9.1+hotfix.6, on Mac OS X 10.15.1 19B88, locale
en-CN)
• Flutter version 1.9.1+hotfix.6 at /Users/felix/workspace/flutter
• Framework revision 68587a0916 (7 weeks ago), 2019-09-13 19:46:58 -0700
• Engine revision b863200c37
• Dart version 2.5.0
[✗] Android toolchain - develop for Android devices
✗ Unable to locate Android SDK.
Install Android Studio from:
https://developer.android.com/studio/index.html
On first launch it will assist you in installing the Android SDK
components.
(or visit https://flutter.dev/setup/#android-setup for detailed
instructions).
If the Android SDK has been installed to a custom location, set
ANDROID_HOME to that location.
You may also want to add it to your PATH environment variable.
[✓] Xcode - develop for iOS and macOS (Xcode 11.2)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 11.2, Build version 11B52
• CocoaPods version 1.8.4
[!] Android Studio (not installed)
• Android Studio not found; download from
https://developer.android.com/studio/index.html
(or visit https://flutter.dev/setup/#android-setup for detailed
instructions).
[✓] VS Code (version 1.39.2)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.6.0
[!] Connected device
! No devices available
! Doctor found issues in 3 categories.

I should use a full path instead of "workspace/flutter/bin/flutter".