Ember 2.x

Any plans to update this to Ember 2.x and Ember-Data 2.x?

Unfortunately I don't have any plans to do it myself, although I don't believe it would be too hard to update.

@jimmay5469 I saw your note about no longer maintaining this addon; I'd be happy to transfer ownership and take a crack at it at some point, if you want.

Yeah, that would be great! Are you on the ember community slack? I am jimmay5469 on there, we could use that to communicate the details for getting things transferred. I think the addon is a cool idea and it would be awesome to see it developed further. I ended up losing interest in the side project I was using the addon for so I stopped actively working on the addon.


Token is not being returned causing server to not respond

Rancher versions: v1.6.6-rc4
Steps to Reproduce:

Auth into LDAP
Deactivate LDAP
Auth into AD

Results:  AD login page stays up and I have to refresh or sometime re-login again to get it show up.  Then if I log out for any reason, I can get my server into a state where it stops responding completely.

Available in v1.6.8-rc1

Rancher Server: v1.6.8-rc4
Steps:

Turn on/off LDAP 100 times
Turn on/off AD 100 times
Turn on and login with AD

I didn't see the problem.

@galal-hussein - this problem was actually cause by trying to log into AD unsuccessfully.  So trying to log in with the wrong credentials.  Rajashree was still seeing it after the initial fix.

@tfiduccia Yes I tried logging into AD unsuccessfully multiple times. But I couldn't repro after the handleResponse fix suggested by @cjellick @ibuildthecloud . I'm not sure which fix you're referring to?

Oh I think I know, so I first had a cattle PR with the handleResponse fix, but in that PR I added the fix to only 5 out of 6 functions, I missed the 6th one. Then during PR review it was pointed out and on adding the fix to that last function that I missed, I couldn't repro

@tfiduccia @mrajashree I tried login with invalid credentials for over than 20 times, and i can't reproduce the problem.


[SPARK-28931][CORE][TESTS] Fix couple of bugs in FsHistoryProviderSuite

What changes were proposed in this pull request?
This patch fixes the bugs in test code itself, FsHistoryProviderSuite.

When creating log file via newLogFile, codec is ignored, leading to wrong file name. (No one tends to create test for test code, as well as the bug doesn't affect existing tests indeed, so not easy to catch.)
When writing events to log file via writeFile, metadata (in case of new format) gets written to file regardless of its codec, and the content is overwritten by another stream, hence no information for Spark version is available. It affects existing test, hence we have wrong expected value to workaround the bug.

This patch also removes redundant parameter isNewFormat in writeFile, as according to review comment, Spark no longer supports old format.
Why are the changes needed?
Explained in above section why they're bugs, though they only reside in test-code. (Please note that the bug didn't come from non-test side of code.)
Does this PR introduce any user-facing change?
No
How was this patch tested?
Modified existing UTs, as well as read event log file in console to see metadata is not overwritten by other contents.

Can one of the admins verify this patch?

I've found the bug while working on SPARK-28869. While it doesn't make test failures in master branch, it triggers failures on my work so just propose the fix earlier.

Test build #109939 has started for PR 25629 at commit 6de02ca.

Can one of the admins verify this patch?

Test build #109939 has finished for PR 25629 at commit 6de02ca.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/109939/
Test PASSed.

Nice, @HeartSaVioR . This bug fix is worthy to have a JIRA issue.
Could you file a JIRA?

I'll review after that.

Also, cc @vanzin

Thanks @dongjoon-hyun , I just filed the JIRA issue and modified the title.

Test build #109965 has started for PR 25629 at commit c11b50d.

Test build #109965 has finished for PR 25629 at commit c11b50d.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/109965/
Test FAILed.

Ur, it's relevant failure. Although I'll trigger this once more, could you take a look?

org.apache.spark.scheduler.ReplayListenerSuite.End-to-end replay with compression

Retest this please.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/14997/
Test PASSed.

Test build #109977 has started for PR 25629 at commit c11b50d.

It seems to be known flaky - https://issues.apache.org/jira/browse/SPARK-28770 - and not related to this patch, though it occurs frequently.

Test build #109977 has finished for PR 25629 at commit c11b50d.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/109977/
Test FAILed.

Test failure for 109977 is org.apache.spark.sql.hive.client.HiveClientSuites.(It is not a test it is a sbt.testing.SuiteSelector)

retest this, please

Test build #109981 has started for PR 25629 at commit c11b50d.

Test build #109981 has finished for PR 25629 at commit c11b50d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/109981/
Test PASSed.

cc. @felixcheung as this patch is a part of work in SPARK-28869 (found this during working)

Merging to master.

Thanks all for reviewing and merging!


Do not display in print preview

CSS @media print should be used to avoid displaying a red shape in the bottom right corner of every page of the PDF/printout

I've tried to use this code, but it doesn't works.
Anyway, you can just hide icon by clicking

What code did you try?
On Apr 6, 2019, 6:41 AM -0500, Sergey<EMAIL_ADDRESS>wrote:

Closed #86.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

if (window.matchMedia) {
        var mediaQueryList = window.matchMedia('print');
        mediaQueryList.addListener(function(mql) {
            if (mql.matches) {
                beforePrint();
            } else {
                afterPrint();
            }
        });
    }

I've tried to hide notification icon and popup in beforePrint(), but it doesn't works.

Did the Stack Overflow's console.log() before/after print work in your testing?
Couldn't you just modify your styles.css file to have a media query in it?
https://developer.mozilla.org/en-US/docs/Web/CSS/Media_Queries/Using_media_queries#Targeting_media_types


Hiding widgets based on role?

Is it possible to hide certain widgets based or if they have authorization. I have tried using the canSee() function but it hides the entire view not just the widget. Any help would be appreciated.

Hi @mlordi , I have added support for it on this PR: https://github.com/dcasia/nova-dashboard/pull/75


Consider to remove lang suffix from namespace files

While we use folders as lang-containers, lets remove redundant extensions of files. It will allow for easier adding new languages by copy-paste.

@Pucek9 : is this one still needed, if so is it for 1.0 launch, or after?

@Pucek9 : is this one still needed, if so is it for 1.0 launch, or after?
@Xymmer
That is only light proposal, it can be done later for sure.

I am going to do this along with #1775


Added dirty-chai

Coverage remained the same at 93.939% when pulling 998c6afd8b09327baf826357581dea7c712e8501 on dirty-chai into 4942b40fd5cbe0d0c8ad4a4628183b8a8c11b887 on master.


sbt: how to lookup the credential when a repo redirects?

When a repository is specified as repo.foo.com, but repo.foo.com redirects to dl.bintray.com, ivy looks for the credential for host = dl.bintray.com while e.g. coursier works with the credential for host = repo.foo.com.
It looks like this was a safety choice at the ivy/httpclient side, to avoid accidentally leaking credentials to the wrong server: it is the standard behavior of the HttpClient APIs (https://github.com/sbt/ivy/blob/2.3.x-sbt/src/java/org/apache/ivy/util/url/HttpClientHandler.java#L303, also when used via setCredentials with an AuthScope).
Unfortunately, it looks like the connection returned by url.openConnection does follow redirects, but doesn't provide access to the redirected hostname.
How could we make this consistent?

Sbt/ivy mirror issue at https://github.com/sbt/ivy/issues/30

Note that coursier looks up credentials by a resolver name: https://github.com/coursier/coursier/issues/358#issuecomment-259095880

Ah, indeed I was referring to picking up the SBT credentials via coursierUseSbtCredentials (which seems enabled by default and appeared to work fine for me, except that it expected the other domain name compared to ivy)

I am getting this issue when using coursier combined with sbt-cinnammon and there doesn't seem to be a workaround for it apart from  temporarily disabling coursier to just let ivy fetch the credentials first.


Fixed typo

Changes Unknown when pulling 9bf2e5e27fc85cd92f0f2190af51a08ac35845a0 on mpscholten:patch-1 into ** on request:master**.

Haha, these copy and paste mistakes... Thanks @mpscholten !


Zowe seems "closed" with meetings and recordings

Feedback on the Zowe Explorer squad kick off was that Zowe seems a bit closed with meetings and recordings. @phaumer are you able to share specifics on which artifacts are difficult to access? We would like to use your feedback to make accessibility better/more open.

Just a theory regarding the impression of closed meetings - due to recent Zoom hacking incidents the OMP tighten access to use of Zoom - I think everyone requires a Zoom account at a minimum - this may give an impression the meetings are not as open as they once were. I think those of use who attend meetings forget our userids are embedded in browsers or Zoom client and don't realize new participants may be presented with userid and password prompts.

Yes, I was hoping that recordings could be provided to the public without the need to sign up with Zoom, which seems an inhibitor, because of their reputation.
Also finding the recording is not easy. When you enter the https://github.com/zowe/community repo you see the Playbacks/Meeting Minutes and Recordings right at the top, but that folder is not used anymore. A clean-up would be good so that it is intuitive to find things.
Teams were also using Google docs or sometime Word docs in Box to share notes in the past that required access.
Perhaps a portal page on zowe.org that provides navigation to each squad's collateral would be good. There should a canonical way to find all wikis, docs, and recordings for CLI vs Web UI vs ML etc. that would increase transparency for the occasional observer of the project.

@phaumer we would like to close this issue if you agree - we think we have improved publishing meeting calendars (yes a Zoom account may be needed for security reasons) .....we do understand that logging of recordings is not consistent across squads and improvement is needed. We will ask the squads to improve - especially when requested by community members (due to time zone issues).

@phaumer we would like to close this issue if you agree - we think we have improved publishing meeting calendars (yes a Zoom account may be needed for security reasons) .....we do understand that logging of recordings is not consistent across squads and improvement is needed. We will ask the squads to improve - especially when requested by community members (due to time zone issues).


You are the GOAT!

Appreciate this repo so much

Thank you so much!
This should've been posted either in DMs or as a discussion instead of an issue


twig.extendFunction aware of other calls

I'm trying to re-create the functionality that Symfony's webpack-encore-bundle adds to twig by creating functions encore_entry_script_tags and encore_entry_link_tags. Here is what I have so far:
fs.readFile(`${__dirname}/public/build/entrypoints.json`, (error, entrypointsFile) => {
    const assets = JSON.parse(entrypointsFile);

    twig.extendFunction('encore_entry_script_tags', (value) => {
        const files = assets.entrypoints[value].js;
        return files.map(file => `<script src="${file}"></script>`).join('\n');
    });
});

Then, in my twig, I have something like the following:
<!-- ... -->
{{ encore_entry_script_tags('entry1') }}
{{ encore_entry_script_tags('entry2') }}
<!-- ... -->

This works to load the correct javascript files into my script, however, in my case, entry1 and entry2 both have common dependency files. Here is what my entrypoints.json file looks like:
{
  "entrypoints": {
    "entry1": {
      "js": [
        "/build/runtime.8e832a5a.js",
        "/build/entry1.66edecb2.js"
      ]
    },
    "entry2": {
      "js": [
        "/build/runtime.8e832a5a.js",
        "/build/entry2.e229d2a9.js"
      ]
    }
  }
}

As you can see, /build/runtime.8e832a5a.js is shared by both entry1 and entry2, and thus gets included twice in the rendered template:
<script src="/build/runtime.8e832a5a.js"></script>
<script src="/build/entry1.e229d2a9.js"></script>
<script src="/build/runtime.8e832a5a.js"></script>
<script src="/build/entry2.66edecb2.js"></script>

If each time the function was executed I could store which entrypoint tags were rendered, I could check the values in subsequent calls to prevent duplication. Is there a way to achieve this? Let me know if I need to explain further.

Try this. But it will work only if both tags are in one template.
const assetsCollection = {};

fs.readFile(`${__dirname}/public/build/entrypoints.json`, (error, entrypointsFile) => {
    const assets = JSON.parse(entrypointsFile);

    twig.extendFunction('encore_entry_script_tags', function (value) {
        // Use template id (path to template)
        const templateId = this.id;
        const files = assets.entrypoints[value].js;
        assetsCollection[templateId] = assetsCollection[templateId] || {};

        return files.filter(file => {
            // if file is unique for template add it to collection and return true
            // else return false to skip it
            let isUnique = false;
            if (assetsCollection[templateId][file] === undefined) {
                assetsCollection[templateId][file] = file;
                isUnique = true;
            }
            return isUnique;
        }).map(file => `<script src="${file}"></script>`).join('\n');
    });
});


Record a Patient Contact Person

The last things to do for this ticket are:

[ ] Adding a feature toggle to the Contact Person section.
[ ] Adding the Person Attributes for the other Contact Person fields (see Given Name implementation for details).

This ticket is currently blocked because there is currently no Person Attributes for Contact Person. These can be created manually here however, there would be a new UUID generated each time in each instance of OpenMRS. This would mean that the source code would also need to be manually changed to ensure that the correct UUIDs are associated with the Contact Person attributes. Therefore, until a way of dynamically creating Person Attributes (see MF-282) is achieved. This feature will remain as a branch on develop. It's ticket on JIRA will be edited to reflect this.


[NLP] Parser fails on deleted Tweets

Parser fails on deleted Tweets, for example:
post = scrape_post('https://twitter.com/AravSrinivas/status/1770128084999758130')
results = multi_chain_parser.process_ref_post(post=post,active_list=["hashtags"])

@ShaRefOh  now the code
post = scrape_post('https://twitter.com/AravSrinivas/status/1770128084999758130')

will throw an exception, so you can use a try catch block and handle the exception appropriately.

(this is on nlp-dev branch currently)


Custom Code unable to be used if user clicks save without entering any text

If a user drags the custom code block onto the canvas, and then clicks save without entering any text - the component can no longer be edited - The only choice is to delete and start again (assuming the user understands the layers).
Would it be possible in the onceclose() function to not exit if the content is currently empty?

I fixed it on this way
const editor = grapesjs.init({
`plugins: [
    'grapesjs-custom-code'
],
pluginsOpts: {
    'grapesjs-custom-code': {
            propsCustomCode: {
                components: {},
            },
            commandCustomCode: {
                handleSave() {
                    const keyCustomCode = 'custom-code-plugin__code';
                    const { target, em } = this;
                    const code = this.getCodeViewer().getContent();
                    target?.set(keyCustomCode, code);
                    // eslint-disable-next-line
                    editor.Modal.close();
                    em.getSelected().view.render(); // this is important part
                },
            }
    }
}

});
And created the new type with the same id to rewrite logic
editor.Components.addType('custom-code', {
    `view: {
        onRender({ el }) {
            setTimeout(() => {
                if (el.offsetHeight === 0) { // no content or without height. It should be clickable
                    const defaultEl = document.createElement('p');
                    defaultEl.classList.add('p-4', 'border', 'border-dark');
                    defaultEl.textContent = 'Default embed code placeholder';
                    el.appendChild(defaultEl);
                }
            }, 500); // If we have some script with src, then we should wait for load
        },
    },
});`


Change text overlay on infobox to current rumour

Currently it just has the word Rumour hovering over it. I think it would be better if it was a short form of what your current rumour is:
SM Sunlight Moth
MM Moonlight Moth
BW Black Warlock
SK Snowy Knight
SG Sapphire Glacialis
SA Sunlight Antelope
MA Moonlight Antelope
DK Dashing Kebbit
DK Dark Kebbit
SK Spotted Kebbit
WK Wild Kebbit
BK Barb-tailed Kebbit
SK Sabre-toothed Kebbit
RK Razor-backed Kebbit
PK Prickly Kebbit
RS Red Salamander
OS Orange Salamander
TS Tecu Salamander
SL Swamp Lizard
GC Grey Chinchompa
RC Red Chinchompa
PF Pyre Fox
EJ Embertailed Jerboa
H Herbiboar
TW Tropical Wagtail
SL Spined Larupia
HG Horned Graahk
SK Sabre-toothed Kyatt

We changed this to display the kc left until you hit the pity rate, thanks for the suggestion though.

The pity rate update has come out so I'm closing this issue.


Metadata has Experiment as top level, but MTH5 has Survey as top level

mt_metadata has Experiment as the top level, whereas MTH5 has the top level as survey.  This was a design flaw that failed to account for multiple surveys.  To make the two symbiotic need to add an Experiment level to MTH5.  This will take some work but shouldn't be too bad.

Ok, wasn't too bad.  This was updated in PR #67.
All the tests passed. but if someone else finds a bug this can be reopened.


WIP master <- develop

Merge the develop branch into the master branch and deploy

Build log
Preview build with this PR (commit): https://output.circle-artifacts.com/output/job/5d1d6d28-d04a-4277-bae9-a7bc400326e2/artifacts/0/index.html


Add method chaining

Looking at this, I'm now not sure if we should do it. The point is to make it shorter to write programs, but we could do just make all functions free functions, like this:
x();
render();

This is both shorter, and more legible. We talked about reasons not to do this, but now I'm not so sure.

Looking at this, I'm now not sure if we should do it. The point is to make it shorter to write programs, but we could do just make all functions free functions, like this:
x();
render();

This is both shorter, and more legible. We talked about reasons not to do this, but now I'm not so sure.

I think the reasoning behind not making them free was so it wouldn't interfere with anything the user would like to define in their program. e.g. if they define some function called circle for whatever reason, well now they can't use the circle mask. Not sure if this would actually be a problem with good docs/example programs though.
If we stick with the class route, this def makes it shorter to write most programs via omission of the class name each method call in a sequence.


convert the project into typescript

I converted the project into typescript based, so anyone who using typescript on their project could use this library. I also had run the test and it works perfectly.

Thanks, @azharalifauzi  for adding typescript support and typings. I looked through the changes and did not find any issues so far.
I will merge it once I have make necessary release related updates. Thanks for taking time to contribute to it and making it more awesome . :heart:

Hi @pavittarx  I am still unable to use this package @ 3.4.2 inside a typescript Nextjs project, is there any additional config I'm missing?


remove usage of absolute paths

Hello Carlos,
Using relative imports make this lib easier to use.
Feel free to merge this PR.
Cheers
Geoffrey

Thanks! I always forgot to correct that! :D Also, I need to implement eslint and prettier!


[CI] use dawidd6/action-download-artifact@v3

Overview

JaCoCo Code Coverage 76.92% :white_check_mark:

Class
Covered
Meta
Status

  Generated by :no_entry_sign: Danger


New Liquid tag for listing files (useful for image galleries, download lists, and index pages).

Here's a basic usage:
 {% gallery name:your_gallery_name %}

 {% endgallery %}

If you want to arrange the images into a grid, you can do this:

 {% gallery name:your_gallery_name %}

Taken on {{ file.date | date: "%F" }}

 {% cycle '', '', '', '

' %}
 {% endgallery %}

It provides this data to the templates:
file.url        # absolute path to file
file.path       # relative path to file
file.htmlurl    # absolute path to html file
file.htmlpath   # relative path to html file
file.name       # File.basename(filename)
file.date       # date extracted from beginning of filename, if present (optional)
file.slug       # basename with the date and file extension stripped off
file.title      # file.slug with hyphens converted to spaces, and put into Title Case

As well as the familiar forloop variable.
Also, none of my code is actually specific to image files. This plugin could easily be used to glob anything out of the filesystem, including a list of available downloads:

 {% gallery name:downloads_page dir:downloads format:tar.gz reverse:no %}

{{ file.title }}

 {% endgallery %}

The above example assumes that it's located inside /downloads_page/index.html and that your .tar.gz files are in /downloads_page/downloads/*.tar.gz. Input is sanitized to prevent the user being able to glob outside of the jekyll source directory.
gallery also reads YAML Front Matter from globbed files, if present. So if you're trying to make an index page for other pages on your site (such as a site map), you can access the yaml in those files directly from the file attribute. In fact, the YAML is interpreted after the filename is parsed, meaning that you can override calculated title and other attributes from your YAML. For example:

{% gallery dir:. format:textile reverse:no %}

{{ file.title }} {{ file.description }}

{% endgallery %}

This example provides a list of links to all the .textile files in your sourcedir, linking correctly to the .html version of those files, and displays the description keyword defined in each file's YAML.

any news on this?

Ehhh... no. I wasn't able to make any progress with regards to
eliminating the 'name' option because I still don't know how to
programmatically determine the location of the template file being
processed (in other words, i can't figure out how to specify a
relative path for the 'dir' option, which is why the 'name' option
exists at all).
So basically this has gone a bit above my head and I'm going to need
somebody who knows more about liquid to help me out with this.


Fix EXE_BAD_ACCESS caused by optional argument

This argument is now non optional, but this never hits the same bad access.
I voted to simplify the code here since the argument is never used optionally in our codebase.
The optional pointer would cause an exception on macos compiled with clang.

I guess simplifying it is OK, but it's strange it was causing an issue. Seems like a compiler bug, which version of Xcode / clang was used.

I have a feeling it is just a false positive in the error detection. But the new code is much more readable anyway.

Thanks!


Azure AD Module requirement under Libraries section

Under the "Libraries" section above, you mention that the Azure AD Module will be installed by the configuration script.  However, this script assumes the user is on a Windows 2016 (or higher) server that has PowerShell v5 or higher.  If you are using a Windows 2012 R2 (or older) server then the command that the configuration script runs (Install-Module) will not work as that is not support in PowerShell v4 and older (the default version on Win2k12R2)  You may want to make a note in this Libraries section that for these older operating systems and/or versions of PowerShell, the user may want to install the module ahead of time.  You may want to also update the script to check for the version of PowerShell and display a message to the user.

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

ID: a61a7e9a-44bf-7bdc-f810-87e2fd6792e1
Version Independent ID: 71d11105-b83e-952e-d107-1ff9a7c8d107
Content: Use existing NPS servers to provide Azure MFA capabilities - Azure Active Directory
Content Source: articles/active-directory/authentication/howto-mfa-nps-extension.md
Service: active-directory
Sub-service: authentication
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@igorvt77 Thank you for your feedback! We will review and provide an update as appropriate.

@igorvt77 We are engaging the content team for the document enhancement request.
@MicrosoftGuyJFlo Could you please help get this document updated ?

Adding to my backlog to review and add to doc.

#please-close


Trajectory Planning Paper

Hello Apollo Team! I just found two following papers from your team and read them.

https://ieeexplore.ieee.org/document/8916917
https://ieeexplore.ieee.org/document/9304787

They are so helpful to understand the details of the trajectory planning algorithm used in Apollo. However, I couldn't find the corresponding code in the Apollo. If it is possible could you tell me where I can find the code?

It is in modules/planning/tasks deciders and optimizers

@qwetqwe Thank you for your help and reply. If you don't mind, can I ask you where I can find the velocity optimization document or paper? Do you use the same algorithm as described in the above papers?


Cannot set local address as destination url

I choose Sub directory on current server and set set as destination url an address of my local network e.g. http://myraspberry/wordpress-static
While starting static site export an error is shown for the destination url because it doesn't contain .com.
Could you allow local addresses?

Issue is located here
https://github.com/WP2Static/wp2static/blob/4b29b3dff1302ad3637298fca4a6422cebf95367/js/wp2static-admin.ts#L376
Only localhost is allowed without domain, but in my case it is an address in my local network which isn't localhost.

This deployment option no longer supported in latest build, but you can programmatically achieve it, using actions/hooks. Please let me know if still needing help with it (and yes, I know this is 2 years in the future now, sorry!)


AYON: Vendorize ayon api

Changelog Description
Vendorize ayon api into openpype vendor directory. The reason is that ayon-python-api is in live development and will fix/add features often in next few weeks/months, and because update of dependency requires new release -> new build, we want to avoid the need of doing that as it would affect OpenPype development.
Additional info
Ayon api was added into separated vendor folder which is added to sys path and PYTHONPATH when ayon_start.py is used.
Testing notes:

AYON mode should still work

Admittedly this PR made me laugh a little. 😄
I feel like this is just a tiny look into the future once everything is split into add-ons for each DCC in a separated codebase, each of which will likely have frequent contributions and changes with also the core still growing and changing over time. I wonder if this just already shows that managing it separately is actually too big of a hurdle to keep the ship moving fast enough (at the current rate that core + apps are changing in conjunction still). Just look at the amount of PRs involving multiple hosts.
So I had a little laugh that we're now trying to avoid a test-run of actually developing these things in separation and start merging the into one big thing - which I'm fine with by the way. Just a fun little mind game.


JSON downloaded files are not nested with WRITE_NESTED download option in config file

Describe the bug
When downloading JSON files for translation (any path, any format), the keys are not nested with WRITE_NESTED download option in config file. The nesting works when using the script directly in the terminal.
This works in the terminal:
simplelocalize download \
 --apiKey MY_API_KEY \
 --downloadPath ./translations.json \
 --downloadFormat multi-language-json \
 --downloadOptions WRITE_NESTED,INCLUDE_DESCRIPTIONS

This does not work using the simplelocalize.yml config
simplelocalize download

###################################
# 'simplelocalize download' command
###################################

# Download path is a path to a file(s) with translations. Use {lang} placeholder to specify language or locale and {ns} placeholder to specify namespace.
# For example, if you have translations in 2 languages and 2 namespaces, you can use the following path: ./src/translations/{lang}/{ns}.json
downloadPath: ./public/locales/{lang}/{ns}.json

# Download format is a format of the file(s) with translations.
# Supported formats: https://simplelocalize.io/docs/general/file-formats/
downloadFormat: single-language-json

# Download options are options that are passed to the download command.
# Supported options: https://simplelocalize.io/docs/general/options/
downloadOptions:
  - WRITE_NESTED # write nested JSON

FYI, the quotes around WRITE_NESTED does not change the outcome.
Thank you.
CLI Version
Operating system (please complete the following information):

OS: Mac OS
OS Version: 13.4.1 (c)
CPU Architecture: Silicon M1

Screenshots
If applicable, add screenshots to help explain your problem.

Hey @adanane
Thanks for reporting this. The issue has been resolved, and it will be available in the next update.

Hey @adanane
The fix has been implemented in version 2.4.1: https://github.com/simplelocalize/simplelocalize-cli/releases/tag/2.4.1


Add Backup/Restore test suite

This needs to be reviewed. Just the current state of the test suite that was worked on together. I've ran this 20+ times without flaking after much trial and error so feel pretty good about that, I just have a couple things I want to update.

Moving off WIP so that testing @hhpatel14 's PR actually runs e2e tests we are confident will pass

/override ci/prow/operator-e2e

/override ci/prow/ci-index


Duplicate occupations in soc-list response

Many occupations occur twice under two different SOC codes. Generally, one of the codes produces results and one does not. We should filter out the invalid occupations.
Example: 11-1010 and 11-1011 are both Chief Executives but only 11-1011 produces results

Should be fixed as part of https://github.com/codeforboston/jobhopper/pull/257

Should be fixed as part of https://github.com/codeforboston/jobhopper/pull/257

Closing this per Lillian

Closing this per Lillian


Added support for async ConfigurationProviders

Added basic support for async configuration providers for libraries/core.javascript (#1328 ). Actual configuration providers (for exampke SharePointListConfigurationProvider) will be implemented separately.
Features included (update):

Async configuration provider support
A caching configuration provider which can wrap other providers

Hi @artokai, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

I added a caching configuration provider which can wrap other providers to this PR.

I has to manually merge this request due to conflicts - will ensure you get listed for credit. Thanks for your great work on this!


Tracking equipment data

It would be great to track equipment / gear data (current vs max distance)

@Crimby88 the inderlaying library is able to do this (at least get gear data) I'm planning to rewrite stuff and add features to get it into the official Home Assistant code, wish me luck ;)

@Crimby88 the inderlaying library is able to do this (at least get gear data) I'm planning to rewrite stuff and add features to get it into the official Home Assistant code, wish me luck ;)

Thank you! And I wish you good luck! Much appreciated

Gear data is included for some time, closing


Upload to PyPi for hosting and distribution

Probably would be good to add to conda too even if on a custom channel.

Got it uploaded and hosted on RTD:
http://jupyter-alabaster-theme.readthedocs.io/en/latest/index.html
https://pypi.python.org/pypi/jupyter-alabaster-theme/0.3.0


fix: remove peeringdb library and peeringdb_sync command

Implementataion here does the following:

Remove fullctl_peeringdb_sync command from fullctl
Remove peeringdb  library and django-peeringdb from fullctl

Task:
https://app.clickup.com/t/14289126/FC-3048

Note that this shouldn't be merged until the required changes are merged in pdbctl (e.g., the implementation of the sync command moved to there)

@Genza999 i think this also had merge conflicts (plus the commit history seems off) - might be good to rebase?

@Genza999 i think this also had merge conflicts (plus the commit history seems off) - might be good to rebase?

Conflicts with base branch have been resolved


[BUG] Add Relevant info on the genre pages

Description
The different genre/category pages display information related to Biography and Memoir rather than what they are
Screenshots
https://github.com/rohansx/informatician/assets/79076050/149de419-034e-4c34-80d2-ffa13b868786
Any additional information?
No response
What browser are you seeing the problem on?
No response
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I have read the discussion tab thoroughly and got the project idea
[X] I am willing to work on this issue (optional)
[X] I am a GSSoC'23 contributor

Hey @rohansx and @AbhishekPSingh07 I want to work on this issue ......please assign me this


fix: image preload

:tada: This PR is included in version 1.13.6 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[bazel] Clean up ROM e2e targets

This PR eliminates two unnecessary bitstream splices and makes use of get_lc_items() to simplify iterating over lifecycle values.

Same comment as in @milesdai's PR: can we park the splicing changes until the meeting. First and the last commits look good though. If you want you can split these changes into two PRs and we can check macro changes in.

Same comment as in @milesdai's PR: can we park the splicing changes until the meeting? First and the last commits look good though. If you want you can split these changes into two PRs and we can check macro changes in.

Sounds good. WDYT about the rom_e2e_watchdog_reconfig changes?

@alphan I've filtered out the other commits and parked the remaining commits (bitstream_splice and watchdog_reconfig) in a branch for now.


worker: Include context error when the retry context is up.

Including the context error makes it easier to e.g. filter out log lines which contain "context canceled". This way, it's simpler to find the original error and ignore the error of the other threads which were canceled as a consequence.

LGTM


Koios: Transaction UTxOs is deprecated

The following endpoint has been deprecated.
https://api.koios.rest/api/v0/tx_utxos

@edridudi

From Koios Devs:

I think we jumped the gun on mainnet one to mention deprecated....part of upcoming changes on v1.1.0:
there will be new utxo_info endpoint, which will show utxo details against bulk tx requested and will be consistent in schema across address_utxos,account_utxos, asset_utxos


New Techniques

Dear all,
Could following techniques be registered in KG?

temporal mean
dhollander response function estimation
fibre orientation distribution (FOD) estimation
streamlines tractography
spherical-deconvolution informed filtering of tractograms (SIFT): (paper ref: https://www.sciencedirect.com/science/article/pii/S1053811912011615)

@tgbugs @UlrikeS91  can we pick this up again and try to make action points?


Xcode 7 archive

When I try to archive in xcode7
make: *** No rule to make target `install'.  Stop.
Command /usr/bin/make failed with exit code 2

please accept pull request
https://github.com/graphhopper/graphhopper-ios/pull/9 this fix bug


Some options returned max values

I edit a friend's save data for him and he told me some values he got in-game were not what I set (not that it breaks the game or gets the account ban). Decided to report this since the wrong values were found after the save was loaded back into the game, not the editor (see below)
Battle Cats ver: EN server - 11.10.0
OS I use editor on: Windows 10, 11
What I edited:
XP:

1st time (on my main laptop - Windows 11):

Value before: 1923257
Value set: 6923257 (adding extra 5 mil)
Value after (in editor): (didn't record)
Value after (in game): 99999999

2nd time (spent some of previous amount):

Value before: 31457999
Value set: 36457999 (also adding extra 5 mil)
Value after (in editor): 36457999
Value after (in game): 99999999

3rd time (on old laptop - Windows 10):

Value before: 99999999
Value set: 69
Value after (in editor): 69
Value after (in game): 99999999

Normal Ticket:

1st time (on my main laptop - Windows 11):

Value before: 173
Value set: 373 (adding extra 200)
Value after (in editor): (didn't record)
Value after (in game): 999

2nd time (spent some of previous amount):

Value before: 849
Value set: 2849 (also adding extra 2000)
Value after (in editor): 2849
Value after (in game): 2999

3rd time (on old laptop - Windows 10):

Value before: 2999
Value set: 299
Value after (in editor): 299
Value after (in game): 999

I also edit catfruits, cateyes and catamins, but those were what I set them at, so nothing wrong.
Also I was using the save option that return transfer code, so the possible fault could be because of that too.
Edit: after using an old save of my alt, neither catfood, platinum shards, NP, battle items, leadership and talent orbs have this issue, but gold tickets does

Used Emulators methods instead. Problem not reproducible with that anymore.

 You are wasting other people's time.


Update leafs/leaves in images

Partially addresses #135.

@jachiang would you mind adding this commit to https://github.com/bitcoinops/taproot-workshop/pull/149 ?
I think it would be useful to have it all in one PR for review.

@bitschmidty I have added your commits from #149 to this branch. I don't know how to push to a PR branch you opened.

Fine by me. Closing https://github.com/bitcoinops/taproot-workshop/pull/149


go-native client preparations (1 of 6)

These two small commits are a precursor to a series of PRs I'll be opening to bring a go-native k8s client to the curated packages CLI commands.

/approve

/test eks-anywhere-presubmit

Presubmit failure appears to be unrelated (perhaps flaky?) will re-run.


Updates for Div Table

Replaced icon images by using font-awesome
Fixed a layout issue when view port is between 720px and 1200px
Added a README file
Moved svg icons to the right file

@kubbafox thanks


x/tools/gopls: design UX around version skew resulting from the forward compatibility proposal

This issue follows up on discussion in https://go.dev/cl/507975, where go/types is being updated to fail type-checking if the required Go version (as configured by types.Config.GoVersion) is greater than the Go version of the standard library (e.g. the version used to compile gopls).
This is the right change for go/types, because an older version of the type checker cannot type check code that was written for a newer version of Go.
However, we aim for an invariant in gopls that "if the Go command works, gopls works" (see also #57979).  Previously, we didn't have to worry about the impact of version skew on this invariant, because the version of go in the users environment is usually the same as the version of go used to compile gopls. So if gopls was producing confusing errors, the go command would also produce confusing errors.
But with forward compatibility (#57001), I think it will frequently be the case that the go command will work correctly, because it was automatically upgraded, yet gopls will fail.
We need to design and test an appropriate UX when users encounter this skew. Some questions to consider:

Should we endeavor to release a new version of gopls with go 1.N in its go.mod file, whenever version 1.N of go is released, so that go install golang.org/x/tools/gopls@latest will always have a version of gopls compatible with all published versions of Go?
Should we pop-up a message prompting the user to reinstall gopls, whenever a new Go version is published?
Should we pop-up a message prompting the user to reinstall gopls, whenever they work on code that is intended for a newer go version?
Should we allow gopls to still partially functoin, by artificially decreasing the version we pass as types.Config.GoVersion?

CC @golang/tools-team

In case of VS Code Go, the extension reads the build info of gopls and if the go version used to build the gopls is too old to handle the go version used in the project (i.e. minor version comparison), it shows a popup message and asks users to rebuild gopls. This is based on the assumption that gopls built with go1.N can work with go1.N and a few older versions of go. We didn't hear much about version skew issues since we implemented this feature. If gopls implements a similar logic (and vscode go should remove this check to avoid double popups), I think that would mostly work.

@hyangah does VS Code actually read the go.mod file to get its go version?

I don't see in the list above the option of gopls rebuilding and reinvoking itself as needed. It could do something like
GOBIN=/some/gopls/cache/go1.N GOTOOLCHAIN=go1.N go install gopls@latest

and then reinvoke /some/gopls/cache/go1.N/gopls.

@rsc I considered that, but there's a chicken and egg problem which would require careful treatment: we can't know the required Go version until we've resolved the users workspace and environment, which happens during the LSP handshake. It's doable, but would require a fair bit of work to splice in a different gopls version during a session.
However, we could just say that "gopls is always built with the latest toolchain", and upgrade whenever there is a newer toolchain available. Added that as an option.
I'm a bit concerned about having gopls download and install new binaries (even if those binaries are go/gopls itself). At least with the forward compatibility proposal there is an explicit act of running the Go command on a module that requires a newer toolchain. In this case, the upgrade would be triggered by the presence of a newer version, which feels different.  Of course, some IDEs auto-upgrade binaries, but that is thus far not a bridge we have crossed with gopls, which should generally be more conservative than any individual IDE. It may have to be opt-in.

@findleyr

does VS Code actually read the go.mod file to get its go version?

Extension runs go version from the workspace root. My understanding is that with the extended forward compatibility work, go version should do the right thing (download/find the right tool chains depending on the GOTOOLCHAIN setup) and report the actually used version.
Complicated cases include, however, multi-module workspaces, nested module, multi-root (vscode's) workspaces, zero-config gopls handling multiple modules, etc. And, in case, users update go.mod file (either the 'go' line, or by updating the dependencies) in the middle of a session. In that case, gopls will be in a better position to detect that and notify editors/users.

Re: gopls self-updating. Another aspect we need to keep in mind is the compatibility between the editor and the gopls. LSP sometimes makes incompatible changes and we also sometimes have custom gopls commands. Editors and users (can) have all the information about the compatibility. I am afraid go and even gopls may not want to know about editors' versions.

@hyangah to be clear I think gopls should only rebuild itself, not upgrade itself. For example, right now I am working with a user who is stuck on v0.11.0, because they are running into performance edge cases of v0.12.x. It's already frustrating enough when we break users, and we would never want to re-break them when they intentionally downgrade!

Note that in many editors, the editor (or its plugin) manages the lifetime of the language server and expects the connection with the language server (over stdio) to be stable after the initial hand-shake. And the initial hand-shake needs to be done within a certain deadline.
We observed a similar pattern with aqua (https://github.com/golang/vscode-go/issues/2229) and it turned out to require pretty delicate handling of processes. (https://github.com/aquaproj/aqua/issues/710)

I think I’m hitting this very issue.
I have go1.21.5 installed, but decided to try a Go 1.22 feature (the servemux change) for a specific project.
This is my transcript:
% git clone https://github.com/robustirc/robustirc
% cd robustirc
% gopls version
golang.org/x/tools/gopls v0.14.2
<EMAIL_ADDRESS>h1:sIw6vjZiuQ9S7s0auUUkHlWgsCkKZFWDHmrge8LYsnc=
% emacs robustirc.go # jump-to-definition for api.NewHTTP(…) works

% echo 'toolchain go1.22rc1' >> go.mod
% grep '^go ' go.mod
go 1.20
% emacs robustirc.go # jump-to-definition still works

% sed -i 's,go 1.20,go 1.21,g' go.mod
% grep '^go ' go.mod
go 1.21
% emacs robustirc.go # jump-to-definition still works

% sed -i 's,go 1.21,go 1.22,g' go.mod
% grep '^go ' go.mod
go 1.22
% emacs robustirc.go # jump-to-definition for api.NewHTTP(…) now broken

So the triggering condition seems to be that the language version and toolchain directive both are on Go 1.22, while gopls was built with Go 1.21.5.
Re-installing gopls with Go 1.22 fixes the problem, but it was not obvious that version skew was what broke gopls (there was some time between switching to Go 1.22 and the next time I needed a gopls feature).
Is there anything we can do to at least produce a good error message?
(PS: If this is a separate issue after all, feel free to split it into a new one or let me know and I can file a separate one.)


As a Pigeon user, i want to be able to import keys from bep39 mnemonic from Palomad Keys

Background
As a Pigeon user, i want to be able to import keys from bep39 mnemonic like we do in paloma keys add --recover so that I am able to import my palomad bep39 mnemonic got generate my ethereum private key so that I can use the same bep39 mnemonic for any EVM and Cosmos chain. Referenced from https://t.me/palomachain/21528
Done when
Acceptance Criteria

[ ]  Allow paloma keys add --recover to be use bep39 mnemonic to import paloma cosmos keys into EVM chains and generate EVM public keys using the palomad private key.

@taariq ok to close for now?

yessss. okay to close.


FPS limit

Hello how does the FPS limit option work? below is what i tried on the .ini but it is still not working
[options]
launch Steam Big Picture using gamestream_launchpad
launcher_exe = gamestream_launchpad.exe 2560 1440 gamestream_steam_bp.ini
wait_on_process = 1
toggle_hdr = 1
refresh_rate = 60

It only works if you have multiple refresh rates to select for your
monitor. It's only for setting the display mode. If it's not in display
settings, it won't work.
wt., 30 sie 2022, 02:40 użytkownik arieldm47 @.***>
napisał:

Hello how does the FPS limit option work? below is what i tried on the
.ini but it is still not working
[options]
launch Steam Big Picture using gamestream_launchpad
launcher_exe = gamestream_launchpad.exe 2560 1440 gamestream_steam_bp.ini
wait_on_process = 1
toggle_hdr = 1
refresh_rate = 60
—
Reply to this email directly, view it on GitHub
https://github.com/lyckantropen/moonlight_hdr_launcher/issues/19, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AASJWLV6Z6YZ5QYG3XOAAH3V3VKBXANCNFSM577V6LTA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


nth:1.0.1

I am submitting

[ ] a new package
[x] an update for a package

Description: add category and keywords for integration with Typst Universe, and add other authors to license file. Otherwise, this is a minor update, no important changes.

Thank you :)


Change the default local directory location for FTP source

As a developer, I'd like to update the default local directory location from /home/vcap/tmp/xd/ftp to /home/vcap/tmp/scdf/ftp.
Acceptance:

Default local directory location points to /home/vcap/tmp/scdf/ftp
README/Docs updated to reflect this change

But do we, really? This couples SCS apps to dataflow, in a way. cc @markfisher

Good point. We could name it more generic then. Perhaps "stream" instead of "scdf"?

We have a similar concern with the File sink: https://github.com/spring-cloud/spring-cloud-stream-app-starters/blob/master/file/spring-cloud-starter-stream-sink-file/src/main/java/org/springframework/cloud/stream/app/file/sink/FileSinkProperties.java#L35
We should avoid "dataflow" in both cases. Perhaps /tmp/ftp-sink (and /tmp/file-sink) are sufficient for defaults?

/tmp/sink/ftp, /tmp/sink/file, /tmp/sink/s3 ?

This issue was moved to spring-cloud-stream-app-starters/ftp#3


[WIP]org settings: Change settings to dropdown.

This coverts the "checkbox" for realm_allow_message_editing  and
"input" for realm_message_content_edit_limit_seconds into a
dropdown with the option for custom time limit option.

This is only one checkbox conversion to the drop-down, next I will do this for "Restrict email domains of new users" if this looks good.
@rishig @timabbott FYI.

Awesome, this looks great! Two text changes, now that I see this live

Let's remove the (default)
Let's change "Custom limit in minutes" -> "Time limit in minutes"

Otherwise ready from my end.

The PR is updated. @timabbott FYI.

Suggestions: @shubhamdhama @rishig @timabbott
Minutes editable after posting: [TextBox]
Editable time in minutes after posting: [TextBox]

For the time limit thing (which is I think what's left here), this could be good enough:
diff --git a/static/js/settings_org.js b/static/js/settings_org.js
index d0700d2..a4a7f8b 100644
--- a/static/js/settings_org.js
+++ b/static/js/settings_org.js
@@ -160,7 +160,8 @@ exports.setup_msg_edit_limit_dropdown_values = function () {
             text: i18n.t("Never"),
         },
         upto_two_min: {
-            text: i18n.t("Up to 2 minutes after posting"),
+            text: i18n.t("Up to __time_limit__ after posting",
+                         i18n.t("2 minutes")),
             seconds: 2*60,
         },
         upto_ten_min: {

Ohh, forgot to comment.
@timabbott PR is updated with the feedback about the translation string, but still the label is Time limit in minutes after posting


⚠ Bofrost.de has degraded performance

In 608792f, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 999 ms

Resolved: Bofrost.de performance has improved in 15e5245.


Evaluate this Crowdsourced Ventilator Covid-19

They have a nice video.
crowdsourced-ventilator-covid-19
https://github.com/Crowdsourced-Ventilator-Covid-19/crowdsourced-ventilator-covid-19

He said use<EMAIL_ADDRESS>as a contact email.

Processed!


Update dependencies and gitignore Pods directory

This PR updates dependencies and gitignores the Pods directory.  This is a somewhat subjective change, so here's my main thoughts:

Tracking the updates of third-party code in our repo contains a lot of junk commits and bogus noise on the diffs - we really only need to specify what our dependencies are, not track their changes
Many of us wanting to contribute to Radiant will inadvertently cause a lot of merge conflicts after runs of pod install if we keep Pods under source control
Downside: hacking on Radiant is not as simple as git clone - you now have to deal with cocoapods.  IMO this is an acceptable barrier to entry and isn't too complex (as the updated README indicates).

So, this is a subjective change, so feel free to weigh in with your opinions as well.
@radiant-player/radiant-player-mac

The only downside I can see to this is that it makes the whole "the fix is in the master branch, compile your own version until the next version is out" a bit more difficult for people.  That said, if we're moving to more regular releases then it's not such an issue.
Personally, I'm just using the pods included in the repo so this is a bit of a change for me. But if it's as simple as just running pod install every so often then I don't see it being a major issue.

@chrismou From what I know about CocoaPods, it's not always that simple.
This is an interesting issue. I'm all for less clutter in the repo, but I think we should make it as easy as possible for developers to fork and PR their changes. If we can find a good, reliable balance I'm down with moving forward with this change.

@jadengore @chrismou It's not always that simple, but oftentimes it's simpler – a pod install is really only ever needed when the dependencies change, so only if you see changes to Podfile or Podfile.lock coming down from master. Most people will not have to run pod install often, probably only they're just pulling down the source for builds once in a while. After doing just that, I came immediately here to see if anyone had proposed ignoring them.
If you want to lock your dependencies in (perhaps to force compatibility with an old version of a library), pulling them down from CocoaPods and committing them is the way to go. Generally those problems can be solved with Podfile.lock and the Pods/ directory can be safely ignored.

I'll close this for now - we can revisit later if we'd like, but for now, it works as-is.

@radiant-player/radiant-player-mac - do we have any updated opinions on this?  Should we version-lock our dependencies in the Podfile and remove them from the repo?


Manager

This pull request finish the logic of project creation, update, delete on disk level
The delete part may needs further discussion. Currently all data on disk will be deleted permanently, we can discuss if this is acceptable on Wednesday's meeting


Multiple data sources

Can you ingest multiple data sources into this program? Particularly CSV files that are scatter plots and not connected.

I also try to get the csv but get an error when importing the library
googleearthplot/googleearthplot.py", line 26
   print "[PlotLineChartFromCSV] plotting a line chart from csv file:"+filepath
SyntaxError: Missing parentheses in call to 'print'. Did you mean print("[PlotLineChartFromCSV]  plotting a line chart from csv file:"+filepath)?

I actually figured that issue out; however having issues with creating a string for vmax below..... within my code.
for i in range(len(namelist)):
stn=namelist[i]
storm = hurdat_atl.get_storm((stn,yrr))
print(stn)
print(max(storm.vmax))
print('')

lat = list(storm.lat)
lon = list(storm.lon)
vmax = list(storm.vmax)
HCAT = list(storm.type)

#Plot line chart
gep2=googleearthplot()

fname=stn+'_'+str(yrr)+'.kml'
#lat=[-77.6192,-77.6192,-77.6195,-77.6198,-77.6208,-77.6216,-77.6216,-77.6216]
#lon=[43.1725,43.1725,43.1728,43.173,43.1725,43.1719,43.1719,43.1719,43.1719]
gep2.PlotLineChart(lat, lon, name=stn, color="pink")
gep2.GenerateKMLFile(filepath=fname)

@VolutionLabs  This is python2 vs Python3 issue.
If you are using python3, it won't work out of the box because this is not compatible with the same (Python3 needs () for print)
As a temporary solution you can download the googleearthplot.py into your project and add paranthesis for all print statements. and use
from googleearthplot import googleearthplot


Add a "Middle-Level" API based on Cypher

Resolves #363
This PR adds a new API "level" to the Hatchet Query Langauge. This API uses a slightly modified subset of the Cypher query language.
As with a normal Cypher query, you can think of a middle-level API query as consisting of two parts:

Path Specification
Condition Specification

Path Specification
In the path specification, the user specifies the wildcards and order of abstract nodes. This part of the query must start with the "MATCH" keyword. The rest of the specification consists of a series of abstract nodes and edges in the following general form:
MATCH (...)-[...]->(...)-[...]->(...)

In the above example, every instance of "..." represents a possible abstract node. However, only the "..." between parentheses must be replaced with actual content. The "..." between square braces can be left empty if desired.
The path specification must contain at least one "node" (content in parentheses) and zero or more "edges" (the -[]-> syntax). The path specification must also end with a "node".
Each placeholder above (i.e., "...") must contain one of the following:

Only a wildcard (same syntax for wildcards as in the high- and low-level APIs) (e.g., ".", "*", "+", 1, 4, etc)
A "variable name" (to be used in the condition section) (e.g., p)
Both a wildcard and a variable name, separated by a comma (e.g., "*", p)

Condition Specification
The condition specification section is used to specify all the conditions that define what real nodes can be matched to abstract nodes in the Path Specification section. This is similar to the filters of the high- and low-level APIs, but, in the middle-level API, all the conditions are specified in a single statement using boolean operators (e.g., and, or, etc.). Internally, the CypherQuery class will convert all these conditions into the individual filters used in the high- and low-level APIs.
The condition specification section starts with the "WHERE" keyword followed by the conditions. Each individual condition has the following form:
<VAR NAME>."<ATTRIBUTE NAME>" <OPERATOR> [VAL]

In the above specification, content in angle braces (<>) represents required user-provided content, and content in square braces represents optional content. This notation is consistent with Cypher with one major exception: the ATTRIBUTE NAME field must be in quotes. This is due to the fact that node attributes in Hatchet (e.g., "time", "time (inc)", etc.) are not guaranteed to follow variable naming requirements, which is guaranteed in Cypher.
There are two sets of "operators" in the middle-level API: string operators and number operators. The tables below describes the available operators for each type.
String Operators:

Operator
Example
Description

Equivalence
p."name" = "main"
Checks if attribute value matches right-hand side

Starts With
p."name" STARTS WITH "MPI"
Checks if attribute value starts with right-hand side

Ends With
p."name" ENDS WITH "impl"
Checks if attribute value ends with right-hand side

Contains
p."name" CONTAINS "RAJA"
Checks if attribute value contains right-hand side as a substring

Regex Match
p."name" =~ "<([\w]+).*>(.*?)<\/\1>"
Checks if attribute value satisfies the regex expression

Number Operators:

Operator
Example
Description

Equivalence
p."time" = 5
Checks if attribute value is equal to right-hand side

Less-Than
p."time (inc)" < 20
Checks if attribute value is less than right-hand side

Greater-Than
p."time (inc)" > 60
Checks if attribute value is greater than right-hand side

Less-Than or Equal
p."time (inc)" <= 20
Checks if attribute value is less than or equal to right-hand side

Greater-Than or Equal
p."time (inc)" >= 60
Checks if attribute value is greater than or equal to right-hand side

Is NaN
p."time" IS NULL
Checks if attribute value is NaN

Is Not NaN
p."time" IS NOT NULL
Checks if attribute value is not NaN

To combine individual conditions, use the three provided binary and unary operators:

AND
OR
NOT

NOTE: currently, all syntax is case sensitive! In the future, I'll probably be modifying it so the keywords (e.g., "MATCH", "WHERE", "ENDS WITH", etc.) are not case sensitive, but for now, make sure keywords are in all caps!
Putting Everything Together
Both parts of the middle-level API query should be combined into a string (I recommend a multi-line string). Once this string is created, the user can use it just like a high-level query. So, to filter a GraphFrame using a middle-level API query, simply pass this string to the GraphFrame.filter function. For example:
path = """MATCH (p)-[]->(2, q)-["*", r]->(s)
WHERE p."time (inc)" >= 30.0 AND NOT q."name" STARTS WITH "b"
AND r."name" =~ "[^b][a-z]+" AND s."name" STARTS WITH "gr"
"""
filtered_gf = gf.filter(path)

Internally, the GraphFrame.filter function will pass the middle-level API query to the new CypherQuery class, which uses the textX library to parse the input and construct a Hatchet query from it.

To keep things consistent going forward, this PR is dependent on #333. So, #333 needs to be merged before this one.
Also, I just noticed that I have to update the NaryQuery class from #333 to support the middle-level API queries.

Travis for Python 3.5+ is failing because of an issue while building Timemory. This is also being encountered in #272, even though, unlike #272, this PR makes no changes to the .travis.yml file."

I just discovered that, if you're using Python 2.7, all middle-level queries must be unicode strings. This requirement is introduced by textX. Additionally, we can't use from __future__ import unicode_literals because that causes issues with the object oriented design of the compound queries feature. This can be relaxed once Python 2.7 support is dropped, but until then, all middle-level queries must be written as u"..." or u"""...""".

Besides the Timemory issue, this PR should be good with respect to Travis. I'll rebase it after #333 is merged.

@cscully-allison I've removed the commented-out code you pointed out. For the testing, there actually already was a test for NOT, but I've added one for OR.


Cherry-pick #28312 to release

As requested by @blindpirate

@bot-gradle merge

Sorry, we can't process your request because of the following error:
Pull request is already in the queue


Fungible Tokens & Direct Tipping

the rebased version of #810 with applied #832
I have squshed the overlapping changes, reducing the commit amount that have simplified rebasing. The diff is almost the same as in the base branch, except that I have extracted #836, you can compare branches by git diff feature/Fungible-Tokens-Direct-Tipping-3 feature/fungible-token-featureflagged. I'm going to test this and check the iframe wallet state.

I'm closing this one because of the branch name the deployment is broken


Flow with multiple devices will sometimes report "Cannot call write after a stream was destroyed" after re-deploy

Hi,
first of all thank you for that awesome extension of node-red. Works quite well so far!
Sometimes I get an error Error from socket: Cannot call write after a stream was destroyed after I re-deploy my flow for some nodes that use the tuya-smart-device node. Mostly it is the same node. The only solution to fix the problem is restarting node-red. Otherwise the error will continue to be thrown.
Does anyone has an idea why that happens?
I've configured all nodes to use Device Virtual ID and Device Key.
Best,
Jakob

Can you please share the logs for further investigation ?

Hi, I have the log of Node-RED, does this help in any way? Or is there an option to get a more detailed log?
16 May 20:02:42 - [info] Started flows
16 May 20:02:42 - [info] [server:Home Assistant] Connecting to http://hass:8123
16 May 20:02:42 - [info] [zigbee2mqtt-server:zigbee2mqtt] MQTT Close
16 May 20:02:42 - [info] [zigbee2mqtt-server:zigbee2mqtt] MQTT End
16 May 20:02:42 - [info] [zigbee2mqtt-server:zigbee2mqtt] MQTT Connected
16 May 20:02:42 - [info] [zigbee2mqtt-server:zigbee2mqtt] Refreshing devices
16 May 20:02:42 - [info] [server:Home Assistant] Connected to http://hass:8123
16 May 20:02:42 - [info] [zigbee2mqtt-server:zigbee2mqtt] MQTT Subscribed to: "zigbee2mqtt/#
16 May 20:02:42 - [info] [zigbee2mqtt-server:zigbee2mqtt] Refreshing devices
16 May 20:02:43 - [info] [tuya-smart-device:power-plug-2] initiating the find command
16 May 20:02:43 - [info] [tuya-smart-device:power-plug-1] initiating the find command
16 May 20:02:44 - [info] [tuya-smart-device:power-plug-2] Connected to device! bf29d8d6d5becdd503m0ta
16 May 20:02:44 - [info] [tuya-smart-device:power-plug-2] Connected to device! bf29d8d6d5becdd503m0ta
16 May 20:02:44 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:02:44 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:02:45 - [info] [tuya-smart-device:power-plug-1] Connected to device! bf8780a47556c35c8a8lg2
16 May 20:02:45 - [info] [tuya-smart-device:power-plug-1] Connected to device! bf8780a47556c35c8a8lg2
16 May 20:02:52 - [info] [tuya-smart-device:power-plug-2] Data from device  [event:data]: {"dps":{"1":true,"9":0,"17":16,"18":0,"19":0,"20":2311,"21":1,"22":621,"23":30545,"24":17787,"25":1172,"26":0}}
16 May 20:02:52 - [info] [tuya-smart-device:power-plug-1] Data from device  [event:data]: {"dps":{"1":true,"9":0,"17":65,"18":0,"19":0,"20":2226,"21":1,"22":595,"23":29200,"24":16636,"25":1252,"26":0}}
16 May 20:02:54 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:02:54 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:03:04 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:03:04 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:03:14 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:03:14 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:03:22 - [info] [tuya-smart-device:power-plug-2] Data from device  [event:data]: {"dps":{"1":true,"9":0,"17":16,"18":0,"19":0,"20":2311,"21":1,"22":621,"23":30545,"24":17787,"25":1172,"26":0}}
16 May 20:03:22 - [info] [tuya-smart-device:power-plug-1] Data from device  [event:data]: {"dps":{"1":true,"9":0,"17":65,"18":0,"19":0,"20":2226,"21":1,"22":595,"23":29200,"24":16636,"25":1252,"26":0}}
16 May 20:03:24 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:03:24 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:03:34 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:03:34 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed

Are the two plugs same brand?
On Sun, 16 May 2021 at 11:35 PM, Jakob Nohe @.***>
wrote:

Hi, I have the log of Node-RED, does this help in any way? Or is there an
option to get a more detailed log?
16 May 20:02:42 - [info] Started flows
16 May 20:02:42 - [info] [server:Home Assistant] Connecting to http://hass:8123
16 May 20:02:42 - [info] [zigbee2mqtt-server:zigbee2mqtt] MQTT Close
16 May 20:02:42 - [info] [zigbee2mqtt-server:zigbee2mqtt] MQTT End
16 May 20:02:42 - [info] [zigbee2mqtt-server:zigbee2mqtt] MQTT Connected
16 May 20:02:42 - [info] [zigbee2mqtt-server:zigbee2mqtt] Refreshing devices
16 May 20:02:42 - [info] [server:Home Assistant] Connected to http://hass:8123
16 May 20:02:42 - [info] [zigbee2mqtt-server:zigbee2mqtt] MQTT Subscribed to: "zigbee2mqtt/#
16 May 20:02:42 - [info] [zigbee2mqtt-server:zigbee2mqtt] Refreshing devices
16 May 20:02:43 - [info] [tuya-smart-device:power-plug-2] initiating the find command
16 May 20:02:43 - [info] [tuya-smart-device:power-plug-1] initiating the find command
16 May 20:02:44 - [info] [tuya-smart-device:power-plug-2] Connected to device! bf29d8d6d5becdd503m0ta
16 May 20:02:44 - [info] [tuya-smart-device:power-plug-2] Connected to device! bf29d8d6d5becdd503m0ta
16 May 20:02:44 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:02:44 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:02:45 - [info] [tuya-smart-device:power-plug-1] Connected to device! bf8780a47556c35c8a8lg2
16 May 20:02:45 - [info] [tuya-smart-device:power-plug-1] Connected to device! bf8780a47556c35c8a8lg2
16 May 20:02:52 - [info] [tuya-smart-device:power-plug-2] Data from device  [event:data]: {"dps":{"1":true,"9":0,"17":16,"18":0,"19":0,"20":2311,"21":1,"22":621,"23":30545,"24":17787,"25":1172,"26":0}}
16 May 20:02:52 - [info] [tuya-smart-device:power-plug-1] Data from device  [event:data]: {"dps":{"1":true,"9":0,"17":65,"18":0,"19":0,"20":2226,"21":1,"22":595,"23":29200,"24":16636,"25":1252,"26":0}}
16 May 20:02:54 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:02:54 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:03:04 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:03:04 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:03:14 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:03:14 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:03:22 - [info] [tuya-smart-device:power-plug-2] Data from device  [event:data]: {"dps":{"1":true,"9":0,"17":16,"18":0,"19":0,"20":2311,"21":1,"22":621,"23":30545,"24":17787,"25":1172,"26":0}}
16 May 20:03:22 - [info] [tuya-smart-device:power-plug-1] Data from device  [event:data]: {"dps":{"1":true,"9":0,"17":65,"18":0,"19":0,"20":2226,"21":1,"22":595,"23":29200,"24":16636,"25":1252,"26":0}}
16 May 20:03:24 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:03:24 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:03:34 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:03:34 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/vinodsr/node-red-contrib-tuya-smart-device/issues/60#issuecomment-841853538,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADQ6OARI25ICDXEBBJQRNDTOACOPANCNFSM44BUNB4Q
.

--
Vinod Surendran R
tenthsone.com
tenthsone.com/adspot (new)
tenthsone.com/junk
talk.tenthstone.com [beta]

All power plugs are from the same brand (and the same model): Teckin SP22

Maybe this can help, I found some more log that is produced before the flow is started:
24 May 14:04:45 - [info] Flows werden gestartet
24 May 14:04:46 - [info] [tuya-smart-device:power-plug-2] Recieved the config {"id":"eaa4fd2.896ec","type":"tuya-smart-device","z":"d20aa8b8.d7f6b8","deviceName":"power-plug-2","deviceId":"bf29d8d6d5becd******","deviceKey":"a6c759da92******","deviceIp":"","retryTimeout":1000,"findTimeout":1000,"tuyaVersion":"3.1","eventMode":"event-both","x":830,"y":320,"wires":[["3c74be4e.913f32"]]}
24 May 14:04:46 - [info] [tuya-smart-device:power-plug-2] Event subscription : shouldSubscribeData=>true , shouldSubscribeRefreshData=>true
24 May 14:04:46 - [info] [tuya-smart-device:power-plug-2] Connecting to Tuya with params {"id":"bf29d8d6d5becdd503m0ta","key":"a6c759da928751c2","ip":"","issueGetOnConnect":false,"nullPayloadOnJSONError":false,"version":"3.1"} , findTimeout :  1000 , retryTimeout:  1000

24 May 14:04:46 - [info] [tuya-smart-device:power-plug-1] Recieved the config {"id":"73bd27e1.eb9168","type":"tuya-smart-device","z":"d20aa8b8.d7f6b8","deviceName":"power-plug-1","deviceId":"bf8780a47556c3******","deviceKey":"7affab4704******","deviceIp":"","retryTimeout":1000,"findTimeout":1000,"tuyaVersion":"3.1","eventMode":"event-both","x":830,"y":120,"wires":[["8ffa77b.f1a6288"]]}
24 May 14:04:46 - [info] [tuya-smart-device:power-plug-1] Event subscription : shouldSubscribeData=>true , shouldSubscribeRefreshData=>true
24 May 14:04:46 - [info] [tuya-smart-device:power-plug-1] Connecting to Tuya with params {"id":"bf8780a47556c35c8a8lg2","key":"7affab4704b16fb7","ip":"","issueGetOnConnect":false,"nullPayloadOnJSONError":false,"version":"3.1"} , findTimeout :  1000 , retryTimeout:  1000

Maybe this can help, I found some more log that is produced before the flow is started:
24 May 14:04:45 - [info] Flows werden gestartet
24 May 14:04:46 - [info] [tuya-smart-device:power-plug-2] Recieved the config {"id":"eaa4fd2.896ec","type":"tuya-smart-device","z":"d20aa8b8.d7f6b8","deviceName":"power-plug-2","deviceId":"bf29d8d6d5becd******","deviceKey":"a6c759da92******","deviceIp":"","retryTimeout":1000,"findTimeout":1000,"tuyaVersion":"3.1","eventMode":"event-both","x":830,"y":320,"wires":[["3c74be4e.913f32"]]}
24 May 14:04:46 - [info] [tuya-smart-device:power-plug-2] Event subscription : shouldSubscribeData=>true , shouldSubscribeRefreshData=>true
24 May 14:04:46 - [info] [tuya-smart-device:power-plug-2] Connecting to Tuya with params {"id":"bf29d8d6d5becdd*******","key":"a6c759da9******","ip":"","issueGetOnConnect":false,"nullPayloadOnJSONError":false,"version":"3.1"} , findTimeout :  1000 , retryTimeout:  1000

24 May 14:04:46 - [info] [tuya-smart-device:power-plug-1] Recieved the config {"id":"73bd27e1.eb9168","type":"tuya-smart-device","z":"d20aa8b8.d7f6b8","deviceName":"power-plug-1","deviceId":"bf8780a47556c3******","deviceKey":"7affab4704******","deviceIp":"","retryTimeout":1000,"findTimeout":1000,"tuyaVersion":"3.1","eventMode":"event-both","x":830,"y":120,"wires":[["8ffa77b.f1a6288"]]}
24 May 14:04:46 - [info] [tuya-smart-device:power-plug-1] Event subscription : shouldSubscribeData=>true , shouldSubscribeRefreshData=>true
24 May 14:04:46 - [info] [tuya-smart-device:power-plug-1] Connecting to Tuya with params {"id":"bf8780a47556c******","key":"7affab4704******","ip":"","issueGetOnConnect":false,"nullPayloadOnJSONError":false,"version":"3.1"} , findTimeout :  1000 , retryTimeout:  1000

I just got similar issue. The issue was because I had a duplicate node for the same device. Once I removed the duplicate the issue was resolved,

Also released a new version which enables reconnect command, please check that as well


BeagleBone Blue doesn't save config

I am not sure whether I am allowed to ask this question here, but any help is pretty much appreciated. I tried to change the wifi config.
connmanctl> tether wifi disable ...
But no effect . What can I do?

currently running/booting  Debian 9.2 2017-10-10 4GB SD IoT  from sd card
already pluged in 12Vdc adapter to improve power-same result
tried to shutdown -r now
and replaced the image on sd card with this one: Debian 9.1 2017-09-21 4GB SD IoT image

Hope someone can help. :(

@BluePackStack all the out of box control of wl18xx for the default image is located in:
/etc/default/bb-wl18xx

Regards,

After restarting. Changes in /etc/default/bb-wl18xx are finally done. Very nice!
Is it true that connman is very buggy on beaglebone? Is there an alternative you can recommend?

It's not buggy, just highly intergrated for the out of box experience... I've setup /etc/default/bb-wl18xx so you can disable parts of it..

It's not buggy, just highly intergrated for the out of box experience... I've setup /etc/default/bb-wl18xx so you can disable parts of it..<

I cleared my early response and went to bed then, since I recognized, that the board wouldn't response to ssh anymore after editing the settings. It seems I can sometimes manipulate softAp SSID and password through different ways, but at the cost of losing control over the board every time. Always have to rewrite SD/Memory to get into system again.
Using: bone-debian-9.2-iot-armhf-2017-10-10-4
Anyway I am very happy that you help me! I will add further information about what exactly crashes my board.


Some page apperance change

Changes in this Pull Request:

Change div width for Radio Bottoms [ shop/customizeLandingpage ]
Change for Bottoms align text to center

Mandatory checks:

[x] latest changes were fetched from the upstream branch before creating this PR (branch is up to date)
[ ] changes were tested manually
[ ] unit tests were properly implemented
[x] communication about interdependent changes has been sent to the team (if applicable)
[x] respective Jenkins jobs were referenced in additional context section of this PR

OSCM Build References:

OSCM Pull And Start job

This change is

Before change:

After change

oscm-portal/WebContent/shop/customFeaturedServices.xhtml, line 57 at r1 (raw file):

    </rich:pickList>

We should in general avoid inline styles as it makes harder the css stylesheet maintainance and the clear separation of view and model. Instead, you can define a class in portal. css and then define the div as such: <div class="fillinDiv fitContentDiv" or so.

oscm-portal/WebContent/shop/customFeaturedServices.xhtml, line 57 at r1 (raw file):

    </rich:pickList>

We should in general avoid inline styles as it makes harder the css stylesheet maintainance and the clear separation of view and model. Instead, you can define a class in portal. css and then define the div as such: <div class="fillinDiv fitContentDiv" or so.

oscm-portal/WebContent/shop/customFeaturedServices.xhtml, line 57 at r1 (raw file):

    </rich:pickList>

We should in general avoid inline styles as it makes harder the css stylesheet maintainance and the clear separation of view and model. Instead, you can define a class in portal. css and then define the div as such: <div class="fillinDiv fitContentDiv" or so.

Done


Added query test and readme example

Looks good. My only comment would be something to the readme about using non-aws sources and credentials. 👍

Looks good. My only comment would be something to the readme about using non-aws sources and credentials. 👍

yes sure will do.  still have to fix the test i added too.

@seddonm1 with that line of thinking - do you think we should generalize and remove references to "Amazon" from AmazonS3FileSystem and AmazonS3FileReader and the module could be s3 instead of aws?

@matthewmturner I think Amazon probably 'owns' the standard and majority of people will use Amazon S3.
I hope the readme can just clarify to users they can use with alternatives (minio, ceph, etc)

@seddonm1 ok sure sounds good.

I think this is good to merge. I might make some changes to README once merged just to clarify how the credentials work.

just want to fix my test, wanted to use assert_batches_eq macro like we do in datafusion. will have that done soon then will merge


Incorrect display of current room temperature

it works good but just Incorrect display of current room temperature.
        "name": "Gree",
        "speedSteps": 5,
        "statusUpdateInterval": 10,
        "sensorOffset": 40,
        "minimumTargetTemperature": 16,
        "maximumTargetTemperature": 30,
        "xFanEnabled": true,
        "temperatureSensor": "disabled",
        "overrideDefaultVerticalSwing": 0,
        "defaultVerticalSwing": 0,
        "encryptionVersion": 0

As described in plugin's documentation current room temperature display depends on the AC unit's capabilities and also the firmware version used. Some units does not have a built in sensor. Some others do have it but the firmware does not report the measured room temperature on the network. In both cases the plugin displays the actual target temperature in Home App instead of the measured one. Firmware problem can be solved by upgrading or downgrading the firmware to a version which does not miss room temperature measurement. (It depends on available firmware releases.) Finally the built in temperature sensor is not precise enough to display the real temperature. It can measure different values of the same room temperature in different modes of the unit (heating / cooling reports different values, although the room temperature is the same).
So in most cases incorrect display of room temperature depends on the AC unit, it's not a plugin problem.
Is this answer acceptable for you or you have a different problem? If not, please describe the problem in more details.

It was working before but now it is not working. I know there is a sensor in the air conditioner because it shows it on itself. The model is Gree Pulsar. There is a Xiaomi Air Cleaner air temperature and humidity sensor in the Apple Home Kit. Can't it take the value there as a basis for Gree?

Unfortunately Apple Home Kit accessories can't communicate with each other. I think it's a security feature.
What does it mean exactly that temperature measurement is not working any more? Does anything changed in your environment? (E.g. updates installed) What is the problem? What do you see?

Could you please set homebridge into debug mode (you can do it on settings page) and collect some logs about GREE plugin? I'd like to check the data received from your GREE unit.

now debug mode is opened i restarted homebridge. how can i collect logs? but i dont use gree now. i have gas boiller. When I increased the room temperature from 22 degrees to 24 degrees via the combi boiler, the instant temperature display on the Gree increased from 19 degrees to 21 degrees.

If you use the UI of homebridge then you can see the logs on the status page but this contains only a few entries. Also there is a logs page accessible from the menu. On the logs page there is a download function also. If UI is not used then logs are available in file somewhere in your homebridge folder structure.

I would be glad if you could inform me when you work on this issue or if there is any update.

I would be glad if you could inform me when you work on this issue or if there is any update.

No problem, I can inform you, but without the logs I can't decide what should be fixed if any. Status updates are continuously reported in debug log also when the AC unit is turned off. So it can help me also in off mode.

okay just tell me what i should do for you .

Just attach the collected debug logs to this issue

Is there any danger in sharing the logs with you? In terms of security and my personal information?

GREE plugin logs do not contain any personal information. You can safely share them with me as others did before you in other issues. The logs contain information only about the AC unit and plugin working state.

I couldn't find exactly where it is. If you write in detail, I can do it. Is it the log title under the accessories?

yes, you are on the right way

Uploading homebridge-gree-ac.log.txt…

homebridge-gree-ac.log.txt

Thank You!
I have analyzed your logs. The GREE plugin works well. Your AC unit reports the 20 °C temperature value. The plugin doesn't need a fix.
If you think that the 20 °C value is not correct, because it should display 22 °C, then you can change the "sensorOffset" configuration parameter from 40 to 38. In this case the Home App will show +2 °C higher temperature than measured by the AC unit.
Unfortunately the GREE AC units do not have a good temperature sensor. The measured value is not precise and depends on many things. The unit can report different values about the same temperature if it is cooling or heating or turned off. A few degrees difference from the correct temperature is normal behavior. This is the reason why I have added the "sensorOffset" configuration parameter to the plugin. It helps to adjust the measured temperature value. I think that this poor quality built-in temperature sensor is one of the reasons why the official GREE+ mobile app does not support displaying the measured temperature at all.

thanks i chance value its works true now !

Sorry but the app started giving wrong information again. It shows 18 degrees when it is 22 degrees inside.

Sorry but I can't fix it. It seems that the AC unit's built-in temperature sensor is malfunctioning and reports an invalid temperature on the network. Maybe a restart (removing power from the AC unit by unplugging it or using a hardware switch, and after a minute restoring power) can help, but I am not sure. The Home App displays exactly that temperature what is reported by the AC unit.

now i chance value ''29'' its works normal now. I'll try it for a few days. If it continues to work stably, I'll let you know.


Maintenance: add Idempotency utility to unit tests

Summary
Given that #1110 is now merged it's now a good time to add the new utility to the unit testing ran at different points of the dev lifecycle.
Additionally, there were some inconsistencies in the package.lock dependencies that prevented some other CI processes from completing successfully (example of failed run).
Why is this needed?
To increase confidence in the code to be merged and to prevent regressions.
Which area does this relate to?
Tests, Idempotency
Solution
See linked PR
Acknowledgment

[X] This request meets Lambda Powertools Tenets
[ ] Should this be considered in other Lambda Powertools languages? i.e. Python, Java

Closing this in favor of #1100


Honor --cc diffs as well

as mentioned in #20,
Any merge conflict will end up with diff --cc instead of diff --git.

I was thinking of using a shortformat style to pick up the filenames, like so…
/chromium/src/third_party/WebKit/Source/devtools on heads/master ⁂
$ git diff --stat
 Source/devtools/front_end/timeline/TimelinePanel.js | Unmerged
 Source/devtools/front_end/timeline/TimelinePanel.js |  5 +++++
 Source/devtools/front_end/ui/Dialog.js              | Unmerged
 Source/devtools/front_end/ui/Dialog.js              | 20 ++++++++++++++++++++
 2 files changed, 25 insertions(+)

~/chromium/src/third_party/WebKit/Source/devtools on heads/master ⁂
$ git diff --numstat
0       0       Source/devtools/front_end/timeline/TimelinePanel.js
5       0       Source/devtools/front_end/timeline/TimelinePanel.js
0       0       Source/devtools/front_end/ui/Dialog.js
20      0       Source/devtools/front_end/ui/Dialog.js

... but that doesn't really work with the text splitting thing you got going.

anyway this works!
fixes #20

regex updated.

This is now available in v0.4.0.
Thanks!


Add assessment-related endpoints to binding with basic API test

### Tasks
- [x] questionnaire https://github.com/konveyor/tackle2-hub/pull/492
- [x] assessment https://github.com/konveyor/tackle2-hub/pull/562
- [x] archetype https://github.com/konveyor/tackle2-hub/pull/563

Done by end of 2023.


agglomerateByVariable should have na.rm parameter?

agglomerateByRank has na.rm parameter, but agglomerateByVariable does not. Is there a reason for this?
library(mia)
data("GlobalPatterns", package = "mia")
tse <- GlobalPatterns

tse_sub <- agglomerateByVariable(tse, by = "cols", group = "SampleType",
                                 na.rm = TRUE) # Won't work
tse_sub

Error in .local(x, ...) : unused argument (na.rm = TRUE)

What if there are some NA values in microbial abundances?
I'm using mia_1.13.45.

I agree it would be logical to have similar behavior for both. The na.rm should be dealth with argument passing.
That being said, should be investigated more closely.

agglomerateByVariable uses scuttle::summarizeAssayByGroup internally. It does not have na.rm parameter. As the function just sums the values, this can be fixed easily.
Add both .merge_cols and .merge_rows na.rm. If na.rm=TRUE, all NA values will be converted to 0.

Thing to note is that na.rm in agglomerateByRank is controlling whether we remove those rows that do not have taxonomy information in specified taxonomy level. Summing NAs still lead to NA:

> agglomerateByRank(tse, rank = "Kingdom", na.rm = TRUE) |> assay()
            CL3     CC1    SV1 M31Fcsw M11Fcsw M31Plmr M11Plmr F21Plmr M31Tong M11Tong LMEpi24M SLEpi20M  AQC1cm  AQC4cm  AQC7cm    NP2     NP3     NP5 TRRsed1 TRRsed2
Archaea      NA    1248  28811      33      57      42     112     140     303      30      131      145    4459   24692   28051   1826   43197   33996     843    8418
Bacteria<PHONE_NUMBER>209<PHONE_NUMBER>418 2076419  718901  433782<PHONE_NUMBER>099  100157  2117461  1217167 1163289 2332489 1671242<PHONE_NUMBER>768 1618758   57845  484708
         TRRsed3   TS28    TS29   Even1  Even2   Even3
Archaea    14250   1598    1690     150     23      91
Bacteria<PHONE_NUMBER>68 1209381 1215987<PHONE_NUMBER>150

na.rm was not working in agglomerateByVariable by column, but by row it was working. The behavior is similar to agglomerateByRank; whether to remove rows that have NA value in group ID.
> agglomerateByVariable(tse, by = 1, group = "Kingdom", na.rm = TRUE) |> assay()
            CL3     CC1    SV1 M31Fcsw M11Fcsw M31Plmr M11Plmr F21Plmr M31Tong M11Tong LMEpi24M SLEpi20M  AQC1cm  AQC4cm  AQC7cm    NP2     NP3     NP5 TRRsed1 TRRsed2
Archaea      NA    1248  28811      33      57      42     112     140     303      30      131      145    4459   24692   28051   1826   43197   33996     843    8418
Bacteria<PHONE_NUMBER>209<PHONE_NUMBER>418 2076419  718901  433782<PHONE_NUMBER>099  100157  2117461  1217167 1163289 2332489 1671242<PHONE_NUMBER>768 1618758   57845  484708
         TRRsed3   TS28    TS29   Even1  Even2   Even3
Archaea    14250   1598    1690     150     23      91
Bacteria<PHONE_NUMBER>68 1209381 1215987<PHONE_NUMBER>150

The question is that whether the behavior of na.rm is intuitive? Most of the functions use na.rm to control whether NA values are excluded in calculation, e.g. sum(c(NA, 1, 3), na.rm = TRUE). For instance, agglomerateByRank could be
agglomerateByRank(tse, rank = "Kingdom", empty.rm = TRUE, na.rm = TRUE)
where empty.rm behaves similarly to current na.rm, and na.rm works like sum(na.rm=TRUE). However, the function is already rather established

na.rm is also present in many functions in other packages. My naive expectation was that if I want to sum up abundances by a column from colData, I should be able to do that even if there are some NAs for a species/metabolite.
For example, I can have a column "organ" with two values "liver" and "heart". I should be able to aggregate all abundances by the "organ" even if some metabolite/microbe is not present in just one sample.

I tend to agree with @artur-sannikov and I would support the default assumption that na.rm ignores NAs in the calculation, and I think that this should behave similarly for all functions (except possibly in some rather special cases).
Even if agglomerateByRank is in use already, I think it could be acceptable change. We could even add an automatic warning that can stay for some releases. It is easier to change now than later in any case, and it is also problematic if users have misleading expectations about the behavior or can't do the standard things easily.
We can also (try to) suggest PRs to scuttle if that helps.


make BSD-3 default, add LGPL, change repo license

This will close #1 by

making BSD-3 the default license for people using the cookiecutter
changing the license of this repo itself from MIT to BSD-3
adding LGPL as an option to the list, which now looks like this:

Select license:
1 - BSD-3
2 - MIT
3 - Mozilla Public License 2.0
4 - Apache Software License 2.0
5 - GNU LGPL v3.0
6 - GNU GPL v3.0
Choose from 1, 2, 3, 4, 5, 6 (1, 2, 3, 4, 5, 6) [1]:

(note: Mozilla and Apache were already in there, but the readme that @sofroniewn was presumably looking at in his original comment was not correct)
@jni, @sofroniewn, @AhmetCanSolak ... lemme know if you have any additional thoughts/ requests.

wait... doesn't "GNU GPL" mean "GNU General Public License?"  making the "GNU" perhaps optional, but at least not repetitive?  https://en.wikipedia.org/wiki/GNU_General_Public_License

wait... doesn't "GNU GPL" mean "GNU General Public License?" making the "GNU" perhaps optional, but at least not repetitive? https://en.wikipedia.org/wiki/GNU_General_Public_License

ah ok - maybe fine to leave as is then

OOOPS! I thought it was GNU Public License. I stand extremely corrected! =) Definitely fine to leave it as is. =)


Add NewIEDriverService

Clone of https://github.com/tebeka/selenium/pull/242

@MarJoSong , since https://github.com/tebeka/selenium is dead, please consider using https://github.com/go-auxiliaries/selenium instead


Custom search function

Hi, ElFinder repositrory can add custom search function such as searching from content metadata https://github.com/Studio-42/elFinder/wiki/Custom-search-function
Is it also possible to add custom search function in this project?

Not yet. It looks great. I will take a look when I have time.

Hi @benny-adiwijaya , please see the latest version 1.5.0 and the Advanced demo for how to use this new function.

Closed due to inactivity. Please feel free to reopen it if the problem persists.


podman 1.9 no longer works with hidepid=2 of /proc

While podman 1.8 worked fine with hidepid=2 for /proc. podman 1.9 always prints:
# podman info
WARN[0000] The cgroupv2 manager is set to systemd but there is no systemd user session available
WARN[0000] For using systemd, you may need to login using an user session
WARN[0000] Alternatively, you can enable lingering with: `loginctl enable-linger 1000` (possibly as root)
WARN[0000] Falling back to --cgroup-manager=cgroupfs
WARN[0000] The cgroupv2 manager is set to systemd but there is no systemd user session available
WARN[0000] For using systemd, you may need to login using an user session
WARN[0000] Alternatively, you can enable lingering with: `loginctl enable-linger 1000` (possibly as root)
WARN[0000] Falling back to --cgroup-manager=cgroupfs
...

@giuseppe PTAL.
I wonder if there is an easy way to add a test for this?

it seems to work here.
Do you have any conf file under ~/.config/containers?
Please share the full output for podman --log-level debug info

@giuseppe :
My fault it is a problem with systemd if i boot with hidepid=2. If i remount with hidepid=2 everything works fine.
When booting with hidepid=2 systemd logs:
Apr 20 09:52:10 host systemd[974]: Failed to determine supported controllers: No such process
Apr 20 09:52:10 host systemd[974]: Failed to allocate manager object: No such process
Apr 20 09:52:10 host systemd[1]<EMAIL_ADDRESS>Failed with result 'protocol'.
Apr 20 09:52:10 host systemd[1]: Failed to start User Manager for UID 1000.

So this is rather a problem with systemd sorry about that.


Merge branch 'ads-main-vscode-2020-08-06T07-08-45' into main

This PR fixes #

Coverage remained the same at 40.276% when pulling 5fc6644c13c7179b85f52b5aef418b1b1800ba47 on vscodemergerelease into 04f25bb29a7863959168c261558f5d9086424736 on release/1.21.


fix: definePageMeta name overriding localized route name

🔗 Linked issue

#2581

❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
While trying to figure out bundler plugins I figured there was an alternative way to tackle #2581. Maybe this is easier to break by Nuxt updates, but I feel this solution makes more sense than https://github.com/nuxt-modules/i18n/pull/2599. I still need to test this with disabled routes, and I may be missing other edge cases, please let me know.
What this PR does is transform the generated routes.mjs file, instead letting name defined in definePageMeta override the localized name (see source code), we capture the locale route name suffix and combine it with the name if it exists, this makes named routes work as expected.
So in routes.mjs the generation would be changed like this example
-name: historyeTgp8UZZfFMeta?.name ?? "history___ja",
+name: (historyeTgp8UZZfFMeta?.name ? historyeTgp8UZZfFMeta?.name + "___ja" : undefined) ?? "history___ja",

What do you think @kazupon?

📝 Checklist

[x] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

I think we might consider reworking Nuxt implementation so we actually expose some page metadata at build-time (via pages:extend).... That will solve some edge cases like this (and with typed pages as well, where a custom name matters).

Closing this as it would break if changes are made upstream, will keep an eye on https://github.com/nuxt/nuxt/issues/24770 and if I have time later (maybe next year 😅) I'll see if I can work on resolving that.