Master

fix cosmic and missing _sample_name in MuTect2

this Build is falling the check for some unrelated issues in snpEffect:
/usr/local/bin/snpEff: line 6: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8): No such file or directory
java.lang.RuntimeException: Database file '/home/travis/build/chapmanb/bcbio-nextgen/tests/data/genomes/hg19/snpeff/hg19/snpEffectPredictor.bin' is not compatible with this program version:
Database version : '4.2'
Program version  : '4.1'
Try installing the appropriate database.

Alessandro;
Thanks for the fix and apologies about the build check confusion. I'd broken the build in the process of upgrading snpEff to the 4.2 version -- it required an update to both snpEff and the databases and the snpEff update into the Docker container got slowed by Travis CI issues yesterday. All should work going forward, fingers crossed. Thanks again for this.

I have to sorry I still so sonnig know How the build check in Travis work. And I was just trying to put a flags that the build fail was from a unrelated error!
I still have to figure how to handle MuTect2 vcf for the Germline call since the standard Vcf do not have the SS or Somatic field anymore.
Thanks !
Sent from my iPhone

On Feb 4, 2016, at 6:31 AM, Brad Chapman<EMAIL_ADDRESS>wrote:
Alessandro;
Thanks for the fix and apologies about the build check confusion. I'd broken the build in the process of upgrading snpEff to the 4.2 version -- it required an update to both snpEff and the databases and the snpEff update into the Docker container got slowed by Travis CI issues yesterday. All should work going forward, fingers crossed. Thanks again for this.
—
Reply to this email directly or view it on GitHub.


commands execution occurance

edit: first awesome fix for the datetime thing!
This one is harder to describe. I will try to break it down as best as I observed it.
disclaimer: it has been a long time since i have seen a cron scheduler or worked with it or understood it.
it seems like commands are cached and all executed at the time a player logs in. resulting in redundant executions of the commands.
I believe this is because when zero player are logged in, no zones are active.  resulting in the server pausing. but scheduled commands are seeming to queue up.
what happens: if I log in my test character after a scheduled command is supposed to happen, very shortly after log in, the command executes every command entry I have in zone jobs (two) immediately. my jobs are set to fire off at two specific times of the day.
since I was logging in at 4:13 PM central time, I expected cronjob to do nothing. however ... I will let the screen shots do more talking.

Your jobs have inactive: 60 which should make them run if the zone hasn't been visited for an hour. Could this cause that?

so, on my test server nobody is visiting anything so it should run,  however, they are scheduled and the jobs were running not at the scheduled time.

Zone jobs execute the next time someone is near the zone.


polymer-bundler silently ignores imports/scripts it can't find

This is different than Vulcanize's behavior, and it seems that it can cause problems that are not immediately detected.
Repro steps: Put the following contents in a file called silent_ignore.html
<link rel="import" href="does_not_exist.html">

hello world

Executing vulcanize returns an error (as expected).
> node node_modules/vulcanize/bin/vulcanize silent_ignore.html

ERROR finding /tmp/temp/does_not_exist.js
{ Error: ENOENT: no such file or directory, open '/tmp/temp/does_not_exist.js'
    at Error (native)
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/tmp/temp/does_not_exist.js' }

On the other hand, executing polymer-bundler silently ignores the missing files and succeeds.
> node node_modules/polymer-bundler/lib/bin/polymer-bundler.js silent_ignore.html

<link rel="import" href="does_not_exist.html">

hello world

cc @usergenic

Bundler doesn't really have any error-output regimen.  We can do two things possibly:

Emit missing import warnings to stderr
Possibly provide an option to fail / exit early with code > 0 on missing import

Maybe a 3rd option be to list all the missing references in some section of the output manifest. Either way, I think the 2nd approach you are mentioning would be preferable over throwing warnings in stderr while returning a success error code.

Thanks, I am about to try this shortly.

Since we are able to identify the missing imports now by reviewing the bundle manifest, I'm going to mark this issue as closed.


Removed invalid images

These images seem to have been deleted from the postimg.org server, removing them

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

I think it'd be better to replace them instead.

There are three earlier PRs for this article.

PR #20681 replaces all but one example.
PR#26127 and #30445 do not replace the images, but do attempt to improve the verbiage.

I think we close this PR and merge PR #20681 and then @thecodingaviator can add another replacement image for the missing one on PR #20681.  As far as the other two PRs, we need to discuss further.

I merged #20681, so you can correct the broken image link.


External provision of branch name

Consider adding ability for external provising of branch name. This might be usefull in case, when this plugin is used inside docker container, where there is no git available

Resolved in https://github.com/k4k7us23/Gradle-Branched-Cache/pull/9


[483] Add Somali translation

Closes #483

What about lower and upper casing?

It this how this language works? :laughing:

I really have no idea. Most of this translation was handed over, so I just assumed that it is correct.
I'm assuming that we will get some feedback from the users so we can fix the errors afterwards.


New backend references resources from deleted backend with same name

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

App Id
d1dsr14iqx52pk
AWS Region
us-east-2
Amplify Hosting feature
Backend builds, Backend environments
Frontend framework
Vue
Next.js version
N/A
Next.js router
N/A
Describe the bug
The backend environment of a new environment references resources from a deleted backend with the same name.
Expected behavior
A new environment should not reference resources from a different environment, even an environment with the same name (that was deleted).
Reproduction steps

Create a new environment called main
Import an auth resource on this new environment (e.g auth1234abcd) and deploy it to the backend
Delete the environment entirely
Create another new environment with the same name (i.e main)
Import the same auth resource on this new environment but with a different name (e.g. auth1234efgh) and deploy it to the backend (this will succeed)
Make a change to the backend (e.g. add another resource) and let the automated builds deploy the change via the amplify-console.

See the logs for the failure details, I.e:
2023-07-21T18:34:30.250Z [INFO]: Amplify AppID found: xxx amplify App name is: xxx
2023-07-21T18:34:30.289Z [INFO]: Backend environment main found in Amplify Console app: xxx
2023-07-21T18:34:40.970Z [WARNING]: - Fetching updates to backend environment: main from the cloud.
2023-07-21T18:35:00.649Z [WARNING]: - Building resource api/xxx
2023-07-21T18:35:00.651Z [WARNING]: - Building resource auth/auth1234abcd
2023-07-21T18:35:00.698Z [WARNING]: ✔ Successfully pulled backend environment main from the cloud.
2023-07-21T18:35:01.419Z [WARNING]: ✖ There was an error initializing your environment.
2023-07-21T18:35:01.769Z [INFO]: 🛑 Could not initialize categories for 'main': The "path" argument must be of type string. Received undefined

^ note the auth resource being referenced is from the now non-existent environment.
Build Settings
backend:
  phases:
    build:
      commands:
        - envCache --set stackInfo ""
        - amplifyPush --simple

Log output

```
2023-07-21T18:34:30.250Z [INFO]: Amplify AppID found: xxx amplify App name is: xxx
2023-07-21T18:34:30.289Z [INFO]: Backend environment main found in Amplify Console app: xxx
2023-07-21T18:34:40.970Z [WARNING]: - Fetching updates to backend environment: main from the cloud.
2023-07-21T18:35:00.649Z [WARNING]: - Building resource api/xxx
2023-07-21T18:35:00.651Z [WARNING]: - Building resource auth/auth1234abcd
2023-07-21T18:35:00.698Z [WARNING]: ✔ Successfully pulled backend environment main from the cloud.
2023-07-21T18:35:01.419Z [WARNING]: ✖ There was an error initializing your environment.
2023-07-21T18:35:01.769Z [INFO]: 🛑 Could not initialize categories for 'main': The "path" argument must be of type string. Received undefined
```

Additional information
I've tried instantiating the environment from local (i.e amplify add env && amplify push) and from amplify-console (setting up the branch and backend connection and then letting automated builds deploy the backend).
Initial deploys via the console work but subsequent deploys do not.
Local deploys always work (but don't meet our needs).
I've also verified that the envCache does not have references to the resources by accessing the pre-signed s3 object exposed in the builds env.

Hey, wanted to get some additional information. how was the environment removed was this on the Amplify console or via amplify env remove main?

@adam-nygate thank you for the information. If the backend environment was deleted on console, we will need to remove the env references in the local Amplify cli by amplify env remove main.
But curious could you try adding the AMPLIFY_ENABLE_DEBUG_OUTPUT environment variable to Amplify console and re-attempt the build. Could you provide us the stack trace that gets printed.

Closing the issue due to inactivity. Do reach out to us if you require any assistance.


Consider GPU and maybe some analytics

GPU stats can be included too
Also temperature of CPU and other internal components and the relation between usage and temperature can be interesting stats to look at...
Besides, if you give interesting stats and analytics to your users and work on this area, it can be amazing and it brings a great advantage to your program. It may worth to inspect machine state monitor desktop programs to discover features that would match your project.

@FarshadAmiri
Thank you for your suggestion, we will consider your needs in detail.

@FarshadAmiri
Thank you for your suggestion, we will consider your needs in detail.


Update Pandas Links

Update the reshaping by pivoting and visualising DataFrames links to current stable version.
Resolves #126

Great thanks!


Automotive/AutomotiveResources: (extended description)

Reviews:
| 2025 Chevy Corvette Prices, Reviews, and Pictures / Edmunds | 1/22/2024 |
Restorations:

Year
Make
Model
Article
Owner
Date

1964½–1966
Ford
Mustang
1964½-1966 Ford Mustang - Hemmings

09/22/2018

#3864 closed #3849


Adding sample html file, that could help developers to work on this project.

I think that adding an HTML file including all of the available components could really help to make small improvements in this project. I would gladly do it :)

Good idea!


Semantics of findLinked?

I'm adding support for include to findLinked but I'm not sure how it's supposed to behave. I believe that it's supposed to resolve the ids in a link and then resolve the records from those i.e the result should be a list of records or an empty array. The implementation does a lot more than this though. I'm not sure if it's just vestigial code or whether it's intended to support more complex behaviour.
@dgeb what I'm wondering is, does the following code cover the expected semantics?
_findLinked: function(type, id, link, options){
  var linkType = this.schema.models[type].links[link].model;
  var linkValue = this.retrieveLink(type, id, link);

  return this._find(linkType, linkValue, options);
},

Current implementation, https://github.com/orbitjs/orbit.js/blob/master/lib/orbit-common/source.js#L71

The current implementation in Source is intended as a default that should be suitable for all sources. I think it should actually avoid calling retrieveLink as it does now, and always just call findLink, then find.
It should be overridden for sources that can implement a more direct method to find related resources. For instance, JSON API now has the concept of a related resource URL which should return just what findLinked needs.
I need to revisit the JSONAPISource very soon to bring it into compliance with the latest version of the spec.

@dgeb what confused me about the current implementation is that it appears to sometimes return records and sometimes record ids, e.g. https://github.com/orbitjs/orbit.js/blob/master/lib/orbit-common/source.js#L93.
Based on your comment about using findLink, perhaps the default implementation should be:
_findLinked: function(type, id, link, options){
  var linkType = this.schema.models[type].links[link].model;

  return this.findLink(type, id, link).then(function(linkValue){
    return this._find(linkType, linkValue, options);
  })
},

Regarding JSONAPISource, I was aware that you needed to do some work to bring it in line with the json-api spec so I'm not intending to add support for the include option. As jsonapi-resources supports the include option out of the box I imagine the implementation in JSONAPISource will be pretty straightforward anyway.

@dgeb closing in favour of https://github.com/orbitjs/orbit.js/pull/123


Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter minuvis for common errors and appropiate suggestions to keep this adapter up to date.
This check is based the current head revisions (master / main  branch) of the adapter repository
Please see the result of the check below.
ioBroker.minuvis
   -
ERRORS:

[X] :heavy_exclamation_mark: [E114] Admin support not specified. Please add "common.adminUI.config = json|materialize<|html|none"
[ ] :heavy_exclamation_mark: [E162] js-controller 2.0.0 listed as dependency but 4.0.24 is required as minimum, 5.0.19 is recommended. Please update dependency at io-package.json.
[ ] :heavy_exclamation_mark: [E204] Version "2.3.4" listed at common.news at io-package.json does not exist at NPM. Please remove from news section.
[ ] :heavy_exclamation_mark: [E701] No actual year found in LICENSE. Please add "Copyright (c) 2024 svallant<EMAIL_ADDRESS>at the start of LICENSE
[ ] :heavy_exclamation_mark: [E114] Admin support not specified. Please add "common.adminUI.config = json|materialize|html|none"

WARNINGS:

[ ] :eyes: [W040] "keywords" within package.json should contain "ioBroker"
[ ] :eyes: [W105] Missing suggested translation into uk of "common.titleLang" in io-package.json.
[ ] :eyes: [W109] Missing suggested translation into uk of "common.desc" in io-package.json.
[ ] :eyes: [W130] Many "common.news" found in io-package.json. Repositorybuilder will truncate at 7 news. Please remove old news.
[ ] :eyes: [W145] Missing suggested translation into uk of some "common.news" in io-package.json.
[ ] :eyes: [W172] "common.localLink" in io-package.json is deprecated. Please define object "common.localLinks": { "_default": "..." }
[ ] :eyes: [W181] "common.license" in io-package.json is deprecated. Please define object "common.licenseInformation"
[ ] :eyes: [W184] "common.main" is deprecated and ignored. Please remove from io-package.json. Use "main" at package.json instead.
[ ] :eyes: [W184] "common.noConfig" is deprecated for admin >= 5 at io-package.json. Please use property "adminUI.config":"none".
[ ] :eyes: [W184] "common.title" is deprecated and replaced by "common.titleLang". Please remove from io-package.json.
[ ] :eyes: [W202] Version of package.json (2.3.4) doesn't match latest version on NPM (2.3.3)
[ ] :eyes: [W513] "gulpfile.js" found in repo! Think about migrating to @iobroker/adapter-dev package
[ ] :eyes: [W853] .npmignore found - consider using package.json object "files" instead.

:thumbsup: No suggestions found
Please review issues reported and consider fixing them as soon as appropiate.
Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.
Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
You may start a new check at any time by adding the following comment to this issue:
@iobroker-bot recheck
Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
@mcm1957 for evidence
Last update at Fri, 06 Sep 2024 09:15:14 GMT

This issue has been updated by ioBroker Check and Service Bot
The following isses have been fixed
[E114] Admin support not specified. Please add "common.adminUI.config = json|materialize<|html|none"
:thumbsup:Thanks for fixing the issues.
The following issues are new and have been added
[E114] Admin support not specified. Please add "common.adminUI.config = json|materialize|html|none"

Issue outdated due to RECREATE request. Follow up issue #89 has been created.
This issue will be closed.
your
ioBroker Check and Service Bot


Version 1.0.3 no longer installs due to highline dependency

As of yesterday (02/25/2015) attempts to install librarian puppet version 1.0.3 fail with a message indicating that the highline dependency requires Ruby version 1.9.3 or greater. I am using the default Ruby version on Ubuntu 12.04.5, which is version 1.8.7.
It appears that highline generated a new release (version 1.7.1) on Feb 24, 2015 at 7:58pm ET (https://github.com/JEG2/highline/releases) which now requires Ruby version 1.9.3. Version 1.0.3 of librarian-puppet appears to be picking up this latest version of highline, and thus generating the noted error.
I am able to resolve the issue by installing version 1.6.1 of the highline gem prior to installing librarian-puppet. Would it be possible to require version 1.6.1 of highline specifically in the 1.0.x line of librarian-puppet? This would allow those of us still stuck on the 1.8.x version of Ruby to continue to use librarian-puppet without needing to first install a seemingly unrelated gem.
Thanks!

Just install a previous version of highline as you did. It is actually not needed and is removed in the next version (already committed in master) when using the new librarianp gem


a spelling mistake

there is a spelling mistake at step1_03 line 114&111,which is document  not docment.

i raised a PR for that https://github.com/Microsoft/frontend-bootcamp/pull/70


probably not necessary inserting of the auto_mix_prep library to the requirements.txt by pipreqs

Hello together,
thank you for your nice little tool. It worked pretty well.
After the usage, I just fund the auto_mix_prep library in the requirements.txt which I did not even have installed while my repository was working correctly in my environment.
Then I had a look in your code and found the following two lines in the "mapping" - file and found the following rows 1046 and 1047:
    src:atlas
    src:auto_mix_prep

After a look at the pipreqs.py it seems to me like some import from the source folder inside of my repository is causing to add auto_mix_prep to the requirements.txt py pipreqs.
The deletion of the row "src:auto_mix_prep" will probably cause to add the atlas-library.
Is any of these rows necessary? Especially since src is a common name for code inside a repository. These rows will cause the auto_mix_prep to be installed uselessly in really a lot of virtual environments if I understood it correctly.
I would propose to delete these rows if there is no real reason for them.

This is still relevant as of 2024 btw


Handle realm emojis.

fix: #607
on web

on mobile

message link

Nice. This is one of the high-value tasks.

@borisyankov updated 👍
Ready to go :runner:

Nice!


testing native call function

Thanks, I'm having a ton of fun and learning a lot! I started noting general questions on the trello board so I don't forget. https://trello.com/c/iaeDfy9G


Support for start/end_keyword in listener version 3

I would like to see support for start_keyword and end_keyword in listener version 3.

The problem implementing this is that on the execution side there currently isn't any place where we could call start/end_keywords so that they would get data and result objects similarly as other listener v3 methods get. Changing that would require quite big changes to the code and doing them just to get this feature implemented hasn't been considered worth the effort.
In RF 4.0 the plan is to add new features like IF/ELSE (#3074) that require big changes to the execution side. When doing them, this issue definitely needs to be taken into account. Thus assigned this one to the v4.0 scope.

i really like this feature.
including line numbers for start and end keyword!
This would be a huge enabler for debuggers!

Hi @bergstenarn and @Snooz82 ,
I'm not sure what those problems mentioned by @pekkaklarck are. Maybe there are some potential issues, but I patched the keyword runners to get something similar, and it worked fine for me:
from functools import wraps

import robot
from robot.running.librarykeywordrunner import LibraryKeywordRunner
from robot.running.userkeywordrunner import UserKeywordRunner

ROBOT_LISTENER_API_VERSION = 3

def start_keyword(kw, context):
    print(kw.lineno)
    print(kw.source)

def end_keyword(kw, context):
    print(kw)

def patch_kwrunner(runner):
    old_run = runner.run

    @wraps(runner)
    def wrapper(self, kw, context):
        start_keyword(kw, context)
        try:
            if False:
                # bypassing this keyword
                return self.dry_run(kw, context)
            return old_run(self, kw, context)
        finally:
            end_keyword(kw, context)

    runner.run = wrapper

def start_suite(suite, result):
    patch_kwrunner(LibraryKeywordRunner)
    patch_kwrunner(UserKeywordRunner)

if __name__ == "__main__":
    robot.run("main_suite.robot", listener=__file__)

Related draft pull request #3672

Hi,
rfswarm agent uses the following version 2 api methods:

start_suite
log_message
end_keyword

So not having "end_keyword" in the version 3 listener API is preventing me upgrading rfswarm from the version 2 API, fortunately the version 2 API works in Robot Framework V3 and hopefully won't be depreciated be in Robot Framework V4?
https://github.com/damies13/rfswarm/issues/67
For my project I would be happy to skip V3 and jump to V4 if end_keyword never gets implemented in V3 but does get implemented in V4 api methods.

@damies13
Afaik there are no plans to deprecate Listener v2!
However at the moment it looks like adding start/end_keyword in listener v3 has to be postponed to RF 5 or later RF 4 minor Release.
With RF4 there will definitely not be a Listener V4! The listener Version is not attached to the Robot Version number.

@Snooz82
Thanks, that's good news 👍🏼

I would be willing to work on adding start/end keyword for listener v3.
Is there already some work done? Or maybe someone could provide a guidance to start?

@pekkaklarck
I have made some progress on this topic and created draft pull request (#4344 ). I would like to get your feedback/guidance before proceeding.

There has been a huge amount of work, as expected, but this this feature is finally getting ready! Some of the things that have been done:

Internal logging has been enhanced to make data and result objects available at the same time without using kludges like the old ModelCombiner.
Listener code has been refactored to make it easier to add the new listener methods.
start/end_xxx methods added for all control structures. They get data and result the same way as earlier methods like start_test.
start/end_keyword methods that are called with all keywords, by default, have been added. Also they get data and result. Notice that the data object basically contains just the name and arguments that were used in the data.
Separate start/end_user_keyword, start/end_library_keyword and start/end_invalid_keyword were added to give listeners possibility to get access to the keyword implementation. As the names imply, the first two are called with user and library keywords, respectively. The third one is called if a keyword isn't found or the keyword itself is invalid. If these keywords are defined, matching start/end_keyword is not called.
Model objects related to test libraries. library keywords and invalid keywords have been totally rewritten. These keyword objects are passed to listeners and they have references to libraries. Old code was horrible spaghetti and passing those model objects to listeners wouldn't have been a good idea. Related to this, also resource file and user keyword code has been enhanced. All this was a rather big task, but the code is now considerably better also otherwise and these APIs now ought to be stable.
Test related results are preserved in memory until tests end to keep them available for listeners. All result objects created during execution also have correct parent relations.

There's still some work to do as well:

[ ] New ForIteraion and WhileIteration data objects for representing individual executed loop iterations. We already have matching result objects, but data objects haven't been needed earlier.
[ ] New start/end_body_item listener methods to call as a fallback with all keywords and control structures. This would allow having one method (ore pair of methods) to listen for all body items.
[ ] Added methods need to be added also to the optional robot.api.ListenerV3 base class.
[ ] Tests. Lot of them.

I hope that interested users can test the new functionality and report possible problems and enhancement ideas. Right now you need to use the code directly from the version control, but the plan is to create a beta release soon as well.
Here's an example listener you can try:
def start_test(data, result):
    print()

def start_user_keyword(data, implementation, result):
    # We get a new `implementation` instance every time. Modifying it does not change
    # the original keyword. It could be done via `implementation.owner` if needed, though.
    implementation.body.create_keyword('Log to console', ['It wroks!'])

def start_library_keyword(data, implementation, result):
    print(f"Starting library keyword '{implementation.name}'.")
    print(f"Keyword exists in library '{implementation.owner.name}' "
          f"on line {implementation.lineno}.")
    print(f'Library instance: {implementation.owner.instance}')
    print(f"Keyword's parent: {implementation.parent}")

def start_invalid_keyword(data, implementation, result):
    print('Something bad happened:', implementation.error)

def start_keyword(data, result):
    raise TypeError('Not called because all `start_xxx_keyword` methods exist.')

def end_keyword(data, result):
    print(f"Keyword '{result.full_name}' on line {data.lineno} {result.status}ED.")

You can use it, for example, with this data:
*** Test Cases ***
Library keyword
    Log    Hello!

User keyword
    User keyword
    User keyword

Non-existing keyword
    Non-existing keyword

*** Keywords ***
User keyword
    Log    Hillo!

Tests have been added. There are only two tests in the body_items_v3.robot file under atest/robot, but they are pretty thorough. The first test validates that all listener methods are called and the latter validates modifying data. You can see tests. listeners and a library these tests use in the body_items_v3 directory under atest/testdata. If you are interested in all interesting (and to some extend crazy) ways the data can be manipulated, see the the DataModifier listener.


black formatter, add tox, flake8, ruff dependencies

[x] add dependencies black, tox, flake8, ruff, django-pytest, pytest-cov
[x] black formatter
[x] add tox file
[x] fix flake8 issues
[x] fix ruff issues
[ ] set up dummy pytest test
[ ] playwright dependencies
[ ] set up dummy playwright
[ ] precommit ?

tests for existing apps in the project will go into a different PR

Closing as this is a bit out of date now. We can reopen again later.


Any example to how to set this up in view.py?

hi @ziqiaojin ,
a testapp is included in the repo with an impending release:
https://github.com/garyburgmann/drf-firebase-auth/tree/1.0.0


Setting language attribute when using custom style

Hi,
Question - should the language attribute work when applying a custom style to mapbox?
It seems to work when there is no style applied, but as soon as I apply my custom style with the gl-style directive the language reverts back to English.
Thanks.

Hi @ExaltedJim!
I think you have to define your languages by style, but I don't know exactly. Sorry!


Enable requesting account storage map information

To enable FPI, GetAccountProofs was introduced. This endpoint returns a proof of the account's existence, alongside state headers: AccountHeader, StorageHeader and AccountCode. There is an implicit limitation to this workflow: StorageHeader only contains the top-level storage slot items (eg, for storage maps, only the root is returned, without any actual map information), so any transaction that attempts to get data related to a foreign account's storage map is would fail.
A mechanism should be provided to allow querying for a specific item/key, in a way that enables FPI with procedures that look into any item, not just top-level values. I'm not sure if we would prefer to retrieve individual storage slots, or if it could be made more granular in order to request specific values of storage maps.
As a side note, if a workaround is needed with more urgency, maybe we could (in the client) get the full account object with the GetAccountDetails endpoint for now to work around this limitation.

@Mirko-von-Leipzig @bobbinth can you prioritize this? Its a user request, and we like our users!

imo we should implement the quick-fix @igamigo suggested in the client. Given that our current user-base is small the impact should be minor, and this gets the users something useable asap.
We still need to flesh out a proper design for handling arbitrarily large request ranges which would form part of the solution for this iiuc.

I forgot to mention here that I did implement the quick fix on the client to unblock the pioneers.
Additionally I've added the parameters for querying account maps and map keys for each account on GetAccountProofs on https://github.com/0xPolygonMiden/miden-node/pull/598. FPI integration tests on the client are passing (https://github.com/0xPolygonMiden/miden-client/pull/645 implements these changes).


KayakFirst doesn't record workout when Instant Measurement Start is on (which is the default)

The console starts the workout but the metrics stay blank on the app screen.
When the Instant Measurement Start is off and the workout measurement is started manually then the app works.

Video: https://youtu.be/vxtDmzuLKSM

Ref #397 #430

I'll close this in favor of #430 because they are very related


docs: navbar style & remove light mode

Description
Use docusaurus config to remove dark/light mode. Fix navbar style

:tada: This PR is included in version 0.24.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


New version: AMSSoftware.PassportPhotoMaker version 9.41

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

The URL for download is the same; however the same installer (given on previous version) now installs version 9.41; hence, the PR

Hi @mbilal234,

This PR's version number 9.41 has 2 parameters (sets of numbers between dots - major, minor, etc), which is less than the current manifest's version 9.2.5, which has 3 parameters.

Does this PR's version number exactly match the version reported in the Apps & features Settings page? (Feel free to attach a screenshot.)
(Automated response - build 706)

The URL for download is the same; however the same installer (given on previous version) now installs version 9.41; hence, the PR

Hi @mbilal234,
We call this a "vanity URL" and this is common. Thanks for submitting a new manifest for the new version. Could you remove the old manifest also?

Hi @mbilal234,

This PR's version number 9.41 has 2 parameters (sets of numbers between dots - major, minor, etc), which is less than the current manifest's version 9.2.5, which has 3 parameters.

Does this PR's version number exactly match the version reported in the Apps & features Settings page? (Feel free to attach a screenshot.)
(Automated response - build 706)

Here's an attached screenshot from the latest version downloaded:

The URL for download is the same; however the same installer (given on previous version) now installs version 9.41; hence, the PR

Hi @mbilal234,
We call this a "vanity URL" and this is common. Thanks for submitting a new manifest for the new version. Could you remove the old manifest also?

Sure, i'll do that


other: update sbt-scalafmt from 2.4.4 to 2.4.5

Updates org.scalameta:sbt-scalafmt from 2.4.4 to 2.4.5.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "sbt-scalafmt" } ]

labels: sbt-plugin-update, early-semver-patch, semver-spec-patch

Codecov Report

Merging #56 (3395390) into master (23253c6) will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff             @@
##              master       #56   +/-   ##
===========================================
  Coverage     100.00%   100.00%
  Complexity        29        29
===========================================
  Files              1         1
  Lines            114       114
  Branches           8         8
===========================================
  Hits             114       114

Continue to review full report at Codecov.

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

Superseded by #57.


docs(demos): padding on action content

Short description of what this resolves:
Added padding on the action sheet as described in issue #453
Changes proposed in this pull request:

padding attribute on

Ionic Version: 1.x / 2.x
2.x
Fixes: #453 partially
this is for issue #453

this is for issue #453 on the ionic-site repo

thanks


would you be interested in a code review/refactoring?

Hi John,
Cool to see this CLI - as a fellow gopher + R aficionado thats a bit further along in the go journey, and would also love to see more of the combo of the two (I think go complements R extremely well), this seemed like a great repo in the public sphere to potentially refactor to be a bit more idiomatic for others to reference. That said, I can't fault "if it ain't broke don't mess", so not sure if that would be of interest to you. No harm either way, but didn't want to start messing with anything if you didn't have the time/interest/inclination.
Cheers

The joy that courses through me when I read "gopher + R aficionado."
I think there is enormous potential for both languages to work together, Go is easier to write, and safe than C or C++. I'm exploring the idea of a proper integration à la rcpp but my lack of knowledge of C makes it impossibly difficult.
With regard to making it more idiomatic, I think it could be done but I'm not sure how, happy to hear of any pointers you might have.

fantastic - I'm traveling tomorrow but will get into this soon. I'll throw over some commits/PRs that can incrementally track some changes.
Off the top of my head we'd want to:

shift all the logic meant for the cli under internal
set up goreleaser: https://goreleaser.com/
minor tweaks to error handling missing in some places (like json unmarshaling)

example - great here: https://github.com/devOpifex/cranlogs/blob/master/data/top.go#L43 , missing here: https://github.com/devOpifex/cranlogs/blob/master/data/trending.go#L35

fix where if it hits a non-nil error could panic (at least from me scanning the code I think)

for example: https://github.com/devOpifex/cranlogs/blob/master/data/daily.go#L38 pretty sure you'd actually just get

panic: runtime error: index out of range [0] with length 0

instead could just return Daily{} in those situations

maybe add some slightly richer types so can better handle data validation for the periods etc

got this going here: https://github.com/devOpifex/cranlogs/pull/2

Thanks Devin, this much improved the code!

cool deal - I'll hit up the next round of updates now


move cursor to cursor channel

Applied, thanks.
On Fri, Jul 17, 2015 at 11:58 PM, Reza Jelveh<EMAIL_ADDRESS>wrote:

Closed #5 https://github.com/vrozenfe/qxl-dod/pull/5.
—
Reply to this email directly or view it on GitHub
https://github.com/vrozenfe/qxl-dod/pull/5#event-358518471.


Fix exception handling info in R2R images

ReadyToRunObjectWriter support for "nested ObjectData" where a given node
can produce an enumeration of subordinate ObjectData items. This is used
to produce the EH info that comes from CorInfoImpl in form of ObjectData
blobs.

One other change in ReadyToRunObjectWriter is the newly added support
for modifying the PE header directories - this is needed to publish
the RUNTIME_FUNCTIONS R2R header table in the Exception Directory,
otherwise RtlLookupFunctionEntry doesn't work.

Fix the EH info itself in CorInfoImpl as CoreCLR runtime that we're
targeting with the R2R images uses a different encoding than CoreRT.

MethodGCInfoNode is created for each funclet and holds the index
of the corresponding FrameInfo which is used to emit the proper unwind
and GC info for each funclet.

RuntimeFunctionsTableNode - emit a separate RUNTIME_FUNCTION entry
for each funclet and emit the appropriate final sentinel entry.

ReadyToRunCodegenNodeFactory - new helpers, support for personality
routines, rooting exception lookup table.

Thanks
Tomas

@MichalStrehovsky, @nattress  - sadly it looks like the Wasm leg has failed even though I have a hard time to understand how can the failure be related to my changes. I see several warnings like the following in the log:

08:49:42      1>EXEC : warning : unexpected return type i1 in call to 'RhSetThreadExitCallback', should be void [D:\j\workspace\debug_windows---17cc7869\tests\src\Simple\HelloWasm\HelloWasm.csproj]
08:49:44      1>EXEC : warning : unexpected number of arguments 2 in call to 'ConstrainedCallSupport_GetStubs', should be 0 [D:\j\workspace\debug_windows---17cc7869\tests\src\Simple\HelloWasm\HelloWasm.csproj]
08:49:48      1>EXEC : warning : unresolved symbol: FormatMessageW [D:\j\workspace\debug_windows---17cc7869\tests\src\Simple\HelloWasm\HelloWasm.csproj]
08:49:48      1>EXEC : warning : unresolved symbol: GetCPInfoExW [D:\j\workspace\debug_windows---17cc7869\tests\src\Simple\HelloWasm\HelloWasm.csproj]
08:49:48      1>EXEC : warning : unresolved symbol: GetConsoleCP [D:\j\workspace\debug_windows---17cc7869\tests\src\Simple\HelloWasm\HelloWasm.csproj]
08:49:48      1>EXEC : warning : unresolved symbol: GetConsoleMode [D:\j\workspace\debug_windows---17cc7869\tests\src\Simple\HelloWasm\HelloWasm.csproj]
08:49:48      1>EXEC : warning : unresolved symbol: GetConsoleOutputCP [D:\j\workspace\debug_windows---17cc7869\tests\src\Simple\HelloWasm\HelloWasm.csproj]

And a little bit later,

08:50:24 C:\Users\runner\AppData\Local\Temp\temp_emrun_firefox_profile_pko4bo\prefs.js:56: prefs parse error: integer literal overflowed
08:50:24 C:\Users\runner\AppData\Local\Temp\temp_emrun_firefox_profile_pko4bo\prefs.js:57: prefs parse error: integer literal overflowed
08:50:24 C:\Users\runner\AppData\Local\Temp\temp_emrun_firefox_profile_pko4bo\prefs.js:58: prefs parse error: integer literal overflowed
08:50:24 C:\Users\runner\AppData\Local\Temp\temp_emrun_firefox_profile_pko4bo\prefs.js:59: prefs parse error: integer literal overflowed

Could you please advise me how to proceed in investigating this?
Thanks a lot
TOmas

sadly it looks like the Wasm leg has failed

I would say don't worry about it - it's failing on all pull requests. I don't think it's related to your changes. Cc @morganbr

@dotnet-bot test this please


Make checkpoint saving fully atomic

Bug description
Checkpoint is no longer atomic. I was implemented here to create checkpoints with ".part" and the rename them, but it is no longer implemented that way looking at code here.
Could we implemented it again in that way? If you kill a job that is training during checkpoint it will corrupted the file
What version are you seeing the problem on?
master
How to reproduce the bug
No response
Error messages and logs
# Error messages and logs here please

Environment

Current environment
#- Lightning Component (e.g. Trainer, LightningModule, LightningApp, LightningWork, LightningFlow):
#- PyTorch Lightning Version (e.g., 1.5.0):
#- Lightning App Version (e.g., 0.5.2):
#- PyTorch Version (e.g., 2.0):
#- Python version (e.g., 3.9):
#- OS (e.g., Linux):
#- CUDA/cuDNN version:
#- GPU models and configuration:
#- How you installed Lightning(`conda`, `pip`, source):
#- Running environment of LightningApp (e.g. local, cloud):

More info
No response
cc @borda @awaelchli

@radomirgr Feel free to implement this if you'd like. The contribution is welcome.

This looks straightforward. I will go ahead and create a PR to restore this behavior.

I have created a PR to address this which uses a fsspec transaction context. This should make saves atomic again.
https://github.com/Lightning-AI/pytorch-lightning/pull/20011


GSM features how to develop?

Don't think you'll get it. Gsm stack usually comes in the vendor firmware
blob which is far outside Fernly IMHO
сб, 16 февр. 2019 г., 15:40 Miracle<EMAIL_ADDRESS>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/xobs/fernly/issues/35, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAfmeLpwWbQydojj-SOjshc1_ITShnEdks5vN9IkgaJpZM4a-5Z9
.

--
Ildar Mulyukov,
(ΙΧΘΥΣ) child of God
email<EMAIL_ADDRESS>matrix: @ildar:matrix.org
GoogleTalk<EMAIL_ADDRESS>blog: http://johan-notes.blogspot.com/

I want to make self phone like iPhone :). Is it possible from fernvale board?

I found mt6260_tdma.h file from nuttx. Is it possible make 2G call and send SMS with fernvale board or this board fake and for advertisement? :(

I found "MTK60D-11B1308-V2" source code than described by "bunnie" is it possible use this source code for building new phone? I have not idea which steps I need to do?

Hi @ildar
Can you help me? Only you asnwered my questions.
Thanks!


Copy-DbaSsisCatalog  - error when running from TFS build/release

Hi,
I'm running Copy-DbaSsisCatalog cmdlet from TFS (version 15.117.27024.0) release definition -  powershell task (Powershell version 5.1).
I get the following error:
 WARNING: [10:14:50][Copy-DbaSsisCatalog] There was an error connecting to the   source integration services. | Exception calling ".ctor" with "1" argument(s):   "Could not load file or assembly 'Microsoft.SqlServer.Diagnostics.STrace,   Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of   its dependencies. The system cannot find the file specified."
But only when running from TFS. If I run from Powershell ISE works fine - same code, same machine, same user account.
Also, explicitly loading Microsoft.SqlServer.Diagnostics.STrace assembly (from TFS) raises no error.
And other DbaTools cmdlets I use  (eg.  Start-DbaMigration, Set-DbaAgentJobStep, Set-DbaAgentSchedule)  also work fine.

is the tfs shell importing some other sql "pieces", like SQLPS ?!

Yes,  but  I can also reproduce the error by running only this script (in TFS release definition - Powershell task):
$secPass = ConvertTo-SecureString $SsisDbEncryptionPass -AsPlainText -Force Copy-DbaSsisCatalog -Source $SourceInstance -Destination $DestinationInstance -CreateCatalogPassword $secPass -Force -Verbose
(variable declarations are omitted here)
And of course it works fine if I run it from Powershell ISE :)

dbatools can't work in a session where SQLPS is already loaded so .... that's pretty much it.

I don't think this is the case.
It only fails when run from TFS and as I explained in may previous post, I get the same error even when Copy-DbaSsisCatalog is the only cmdlet in script.

if SQLPS is inherently and silently loaded by the TFS shell you wouldn't notice. Try an Encode-SqlName, if it goes through, something funny is going under the hood

Encode-SqlName : The term 'Encode-SqlName' is not recognized as the name of a c mdlet...  - in the case when this is the only cmdlet in the script.
But I'll have to deal with this issue. Now my own PowerShell function, which connects SSIS using SMO, fails the same way as  Copy-DbaSsisCatalog   - on creating SSIS server object.
When I try the same in a separate script (creating SSIS server object) it succeeds.

You will need to look at the task you are using in TFS to address the use of sqlps. I have not used it in a while but do maintain Azure DevOps releases. The PS task generally is only going to execute what you tell it to, not aware it pre-loads other modules, but I have not worked with TFS itself in a long time.
Our module does not utilize sqlps/sqlserver module and does not get along with either one of them. If you are calling a command like Encode-SqlName this will implicitly import the module found on your TFS agent that contains that command...the error that it is not recognized means the module with it was not found.


Document product limits

We need a recommendation against letting a single row get close to 64MB (the default size at which we split a range). In addition to the current row data, all historical versions of the row that have not been garbage collected count toward the overall size.
Normally, a range contains many rows, in which case when the range gets to the limit, we split into 2 ranges. If a single row takes up all of a range, however, we won't split the range but rather let it get larger than the max limit.

As the row size increases further, memory usage may get spikier (eventually reaching a point where servers will start running out of memory and dying).
At some point, we’ll stop rebalancing the range as well because it is too large.

@robert-s-lee, how important do you think this is at our phase?

See https://github.com/cockroachdb/docs/issues/380 for answers from 2016.

If a single row takes up all of a range, however, we won't split the range but rather let it get larger than the max limit.

Note that this is no longer true. We now block writes to the offending range when it gets too large. It's still important to stay out of this situation, but it will no longer destabilize the rest of the cluster.

Another issue asking or physical maximum limits for column names, table names, row width: https://github.com/cockroachdb/docs/issues/7280

Another suggestion that we need this, from @a-entin:

Question re "System Limits" doc page. I don't think we have one (pls point if missed) and wonder what are the thoughts on that, maybe there is already a plan for it?
The idea is 2 have 1 place to check all kinds of limits a user can bump into. Most databases have that, supper helpful. 3 diff database examples:
https://docs.oracle.com/cd/B28359_01/server.111/b28320/limits.htm
https://docs.oracle.com/cd/E18283_01/timesten.112/e17114/limit.htm
https://docs.memsql.com/v7.1/reference/configuration-reference/system-limits/

Also, there's this very old PR started by @knz that could help.
@johnrk, @taroface, I think it's time for us to prioritize this. Although there are still no actual, hard limits, we should be able to provide guideposts based on our own internal testing and what we know from customer usage. Perhaps telemetry would help here. I think part of the work is defining what dimension to even document limits for. I imagine @a-entin can help.

More from @a-entin:

I would change "production limits" to more directly "product" or "system" limits... production alludes to capacity planning aspect and we need product characteristics documented as first order, imho.
I'm pretty sure we have some hard limits, but even if "no limit", it's really helpful to say this explicitly on essential parameters where limits are expected by users. It will eliminate a lot of support chatter.
We can build the list of parameters to list. The 3 examples are pretty good / common sense and you'll see a lot of correlation

@chudro let me know what topics we should add here! Thanks.

The SE's are in the midst of capturing the topics that should be listed in a product limits page. Here is a link to a google spreadsheet providing that list as it is being captured. There is a separate tab providing a list of example db websites and how they provide similar lists:
https://docs.google.com/spreadsheets/d/1JWqggZ1tZ_wDI_lrvWdEBtge4hQFvXEZYczQtMhkRjI/edit?usp=sharing

@taroface this Cockroach Cloud user requires this type of information:
https://cockroachdb.zendesk.com/agent/tickets/6546

I am looking answers for below questions:

How much maximum columns are supported by a CRDB table?
How much maximum size of individual data can be stored in CRDB cell?
How much maximum size a table can store?
Maximum number of tables in one database?
Maximum number of databases per CRDB cluster?
Your answer will help me to architect my applications.

https://forum.cockroachlabs.com/t/cockroachdb-limits/592/7

Hi @florence-crl , any update on above questions?

Also to cover:

Number of tables, columns, and indexes we support
Row size limits (especially JSON sizes), range size limits
Cluster storage limits in cluster
Number of connections support per host

Verbiage from @jhatcher9999: https://cockroachlabs.slack.com/archives/CHVV403F0/p1610553560090500?thread_ts=1610550065.087100&cid=CHVV403F0

Verbiage from @jhatcher9999: https://cockroachlabs.slack.com/archives/CHVV403F0/p1610553560090500?thread_ts=1610550065.087100&cid=CHVV403F0

I believe the 64MB range limit is changing for 21.1 (or has changed already) - needs to be verified.

The default range size limit changed from 64MB to 512MB in 20.1.

@mikeCRL, thanks for taking this on! This is an old issue, so it's helpful to articulate next steps:

Identify the most important dimensions to document. This SE spreadsheet is a good starting point. In my opinion, we don't have to cover everything. I'd want to focus on all things data-related (as opposed to number of cores per node, etc.), as the data limits are going to be useful for all customers, both self-hosted and CC. @piyush-singh, can you support Mike in this step?
For each dimension, identify the practical "limits". Channeling @bdarnell, we may not want to talk about these as limits, per se, but rather numbers that are known to work. For this, I would poll the SE and CS teams about the biggest environments we know of in the field. Eventually, Engineering may be able to do lots of testing to establish actual limits, but that is a big effort that's not in scope right now.

Notes from my visit to bdarnell's Chief Architect Office Hours.

Regarding documenting hard limits, vs best practices, vs conditional/considerations, vs max known to work:

Question will be 'how firm are the limits.' Hard limit of 63 chars in user. But # tables; you can have 10K if you're not doing much else with them. So hundreds or a few thousands of tables would be a best practice.
Not many hard limits exist. But we don't often have clear answers on what the best practices are. But we do expect max tables may be in the 3-4 digits; going above that may work or it may not. Many caveats.
Therefore likely to be worth starting with a bulleted list over table.

OSS vs CCL vs CC

OSS and CCL should be same; subsets on CC and CC Serverless should exist, and there will be some difference there. (Serverless currently free tier and will expand into new paid tier.)
# of nodes and store size will differ for CC vs CRDB.
In CC, there's always the 'call us for special needs' to note, while you can create 24-node cluster via self service.
The rest should be the same in CC vs CRDB. e.g. # tables.

Other considerations

Some of the limits will be down to a per node number and some not.

E.g. adding more nodes wont help support more tables. Adding more RAM might.

We can define reference node type (for hardware to base limits off of).

E.g. 3 node cluster on CC on standard node types; you can create 10k tables and not touch; but to be useful may not work.

Re. who might be tasked with researching higher priority items if we don't have data; similar point in today's IO call re. who's responsible for benchmarking? (Eng vs rev?) No single owner.

Convince Product or Eng leadership, or Sales Eng will have to do it. (Mike may start by raising with Piyush.)

a-entin has one or two recorded pres. where he talks about sizing; topology matters; how vcpu's matter.
Ben agrees with premise that we can document what we know; anything we add will point readers in the right direction.

I made a few comments and also added a tab "JDBC Metadata Dump". JDBC allows the client to query database defaults and limits. I think we should at least be aware, perhaps true to what we report about ourselves. For example, we report
getMaxConnections | 8192
getMaxColumnsInTable | 1600
getMaxRowSize |<PHONE_NUMBER>

It's become apparent that there is interest in documenting two separate types of things: hard limits (a well-defined list of system-specified limits, including clarity on what we do not limit) and best practices/considerations related to size and scale.
I clarified the split in our spreadsheet - which should remain SSOT for the foreseeable future - and am splitting this work into multiple issues:

CockroachDB
CockroachCloud

Hard limits
#1830
#10032

Size/scale BPs
#10031
#10037

I have raised an initial draft PR for CRDB https://github.com/cockroachdb/docs/pull/10035. In this case, it touches on both of the above - limits and BPs - because there was a lot of info relevant to both gathered in this issue and the sheet. I found that there was a reasonable place for a lot of this existing info on the schema design page, given the focus on various DB object types.
Future efforts to gather information can occur via the more specific issues.

We have closed this issue because it is more than 3 years
old. If this issue is still relevant, please add a comment and reopen
the issue. Thank you for your contribution to CockroachDB docs!


bitbake: Prevent including diff of diff in superflore-change-summary.txt

but there isn't much we can do about this from superflore,

Yes, now that there are two commits for every new ROS distro release, it no longer makes sense for superflore to generate this file => convert this PR to stop doing so, and I'll create an issue for it.

I'll create an issue for it.

https://github.com/ros-infrastructure/superflore/issues/274

Rebased and commit message updated.


Update to latest PS Worker

cc @pragnagopa @ahmelsayed @daxian-dbw should be good to go. NuGet package is already pushed 🙂

I think this is all set to merge @ahmelsayed 👍


ReferenceError: require is not defined (line 1, col 9)

Hi, I am getting ReferenceError: require is not defined (line 1, col 9)
My code in a function node is var _ = require('lodash');
I installed lodash with npm i --save lodash
My directory that I have Node Red running locally shows

Node red version 0.19.5

no response. closing


Work around onDidCloseTextDocument firing on a wrong document.

Sometimes onDidCloseTextDocument seems to get called with a different
document (something involving git?). This works around the problem by
also watching the list of visible editors, and closing the session.
Works around issue #26, related to upstream issue
https://github.com/Microsoft/vscode/issues/30820.

Unfortunately this only works for case one tab has been opened and then closed.
visibleTextEditors[] are not all opened tabs, but only visible (usually just current one)
https://github.com/Microsoft/vscode/issues/15178
So, any actions with tabs closes Session for first opened file.
For example try:

rmate -w file
Doubleclick tab-bar to open new blank tab
See that Session is already stopped, while first file is still open


refactor: split log emission to encrypt and a log, remove address input

Please read contributing guidelines and remove this line.

#6987  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @LHerskind and the rest of your teammates on  Graphite

Benchmark results
Metrics with a significant change:

avm_simulation_time_ms (Token:transfer_public): 57.6 (+32%)
protocol_circuit_witness_generation_time_in_ms (root-parity): 66.2 (+30%)
protocol_circuit_witness_generation_time_in_ms (root-rollup): 90.5 (+43%)
protocol_circuit_proving_time_in_ms (private-kernel-tail): 45,093 (+16%)
protocol_circuit_proving_time_in_ms (base-rollup): 81,230 (+18%)
protocol_circuit_proving_time_in_ms (root-parity): 40,188 (+18%)
protocol_circuit_proving_time_in_ms (root-rollup): 22,697 (+17%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Proof generation
Each column represents the number of threads used in proof generation.

Metric
1 threads
4 threads
16 threads
32 threads
64 threads

proof_construction_time_sha256_ms
5,712
1,556
701
753 (-1%)
774 (-1%)

proof_construction_time_sha256_30_ms
11,434 (-1%)
3,079 (+1%)
1,531 (+12%)
1,430 (+1%)
1,464 (+1%)

proof_construction_time_sha256_100_ms
44,795
12,067
5,703 (+1%)
5,585
5,476

proof_construction_time_poseidon_hash_ms
78.0
34.0
34.0
60.0 (+3%)
87.0 (-1%)

proof_construction_time_poseidon_hash_30_ms
1,520
419
202
226 (+2%)
267 (+1%)

proof_construction_time_poseidon_hash_100_ms
5,759
1,562
721
772 (+1%)
797

L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
4 txs
8 txs
16 txs

l1_rollup_calldata_size_in_bytes
1,412
1,412
1,412

l1_rollup_calldata_gas
9,452
9,456
9,452

l1_rollup_execution_gas
610,273
610,277
610,273

l2_block_processing_time_in_ms
709 (+2%)
1,286
2,473 (+1%)

l2_block_building_time_in_ms
22,389
45,988
87,996

l2_block_rollup_simulation_time_in_ms
22,274
45,607
87,598

l2_block_public_tx_process_time_in_ms
19,151
42,173
84,295

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 8 txs.

Metric
3 blocks
5 blocks

node_history_sync_time_in_ms
5,905
8,489

node_database_size_in_bytes
9,441,360
12,722,256

pxe_database_size_in_bytes
9,242
15,127

Circuits stats
Stats on running time and I/O sizes collected for every kernel circuit run across all benchmarks.

Function
time_ms

GasToken:_increase_public_balance
69.3 (+1%)

GasToken:set_portal
16.9 (-9%)

Token:constructor
95.0 (-4%)

FPC:constructor
62.1

GasToken:mint_public
51.9 (-6%)

Token:mint_public
515 (-5%)

Token:assert_minter_and_mint
61.3 (-6%)

SchnorrAccount:approve_public_authwit
33.1 (-6%)

FPC:prepare_fee
78.9 (-5%)

Token:transfer_public
:warning: 57.6 (+32%)

FPC:pay_refund
68.7 (+9%)

Benchmarking:increment_balance
2,417 (-1%)

Token:_increase_public_balance
56.3 (-1%)

FPC:pay_refund_with_shielded_rebate
56.0

Public DB Access
Time to access various public DBs.

Function
time_ms

get-nullifier-index
0.177 (+2%)

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
256 leaves
512 leaves
1024 leaves
32 leaves

batch_insert_into_append_only_tree_16_depth_ms
10.4 (-1%)
17.0
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.7
31.8
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.604 (-1%)
0.519
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
48.5 (-1%)
76.4 (+1%)
135 (+2%)
247
477 (+1%)
N/A

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
95.9
159
288
543
1,055
N/A

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.495 (-1%)
0.470 (+1%)
0.462 (+1%)
0.448
0.445 (+1%)
N/A

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
59.7 (-1%)
113
188 (+2%)
356
703 (+1%)
N/A

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
109
208
355
691
1,363
N/A

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.505 (-1%)
0.505
0.496 (+2%)
0.482
0.482
N/A

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
60.4

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
N/A
N/A
N/A
N/A
N/A
103

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
0.551

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
79,300
673,633

Transaction size based on fee payment method
| Metric |  |
| - |  |


ImportError: libffi.so.7: cannot open shared object file: No such file or directory

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az keyvault set-policy
Errors:
The command failed with an unexpected error. Here is the traceback:
libffi.so.7: cannot open shared object file: No such file or directory
Traceback (most recent call last):
  File "/home/linuxbrew/.linuxbrew/Cellar/azure-cli/2.29.0/libexec/lib/python3.9/site-packages/knack/cli.py", line 231, in invoke
    cmd_result = self.invocation.execute(args)
  File "/home/linuxbrew/.linuxbrew/Cellar/azure-cli/2.29.0/libexec/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 556, in execute
    self.commands_loader.load_arguments(command)
  File "/home/linuxbrew/.linuxbrew/Cellar/azure-cli/2.29.0/libexec/lib/python3.9/site-packages/azure/cli/core/__init__.py", line 517, in load_arguments
    self.command_table[command].load_arguments()  # this loads the arguments via reflection
  File "/home/linuxbrew/.linuxbrew/Cellar/azure-cli/2.29.0/libexec/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 313, in load_arguments
    super(AzCliCommand, self).load_arguments()
  File "/home/linuxbrew/.linuxbrew/Cellar/azure-cli/2.29.0/libexec/lib/python3.9/site-packages/knack/commands.py", line 104, in load_arguments
    cmd_args = self.arguments_loader()
  File "/home/linuxbrew/.linuxbrew/Cellar/azure-cli/2.29.0/libexec/lib/python3.9/site-packages/azure/cli/core/commands/command_operation.py", line 125, in arguments_loader
    op = self.get_op_handler(self.op_path)
  File "/home/linuxbrew/.linuxbrew/Cellar/azure-cli/2.29.0/libexec/lib/python3.9/site-packages/azure/cli/core/commands/command_operation.py", line 59, in get_op_handler
    handler = import_module(mod_to_import)
  File<EMAIL_ADDRESS>line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
  File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 850, in exec_module
  File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
  File "/home/linuxbrew/.linuxbrew/Cellar/azure-cli/2.29.0/libexec/lib/python3.9/site-packages/azure/cli/command_modules/keyvault/custom.py", line 21, in <module>
    from azure.cli.command_modules.keyvault.security_domain.jwe import JWE
  File "/home/linuxbrew/.linuxbrew/Cellar/azure-cli/2.29.0/libexec/lib/python3.9/site-packages/azure/cli/command_modules/keyvault/security_domain/jwe.py", line 13, in <module>
    from cryptography.hazmat.primitives import hashes, padding
  File "/home/linuxbrew/.linuxbrew/Cellar/azure-cli/2.29.0/libexec/lib/python3.9/site-packages/cryptography/hazmat/primitives/padding.py", line 13, in <module>
    from cryptography.hazmat.bindings._padding import lib
ImportError: libffi.so.7: cannot open shared object file: No such file or directory

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az keyvault set-policy

Expected Behavior
Environment Summary
Linux-5.4.0-1059-azure-x86_64-with-glibc2.27, Ubuntu 18.04.6 LTS
Python 3.9.7
Installer: HOMEBREW

azure-cli 2.29.0 *

Extensions:
aks-preview 0.5.10
k8s-extension 0.1PP.12
azure-devops 0.17.0

Additional Context

keyvault


The usual #114488 background isn't used, dark blue background used by default

Hi, I just tried this out since I've been trying to create a very similar colour scheme for my terminals. This, however, gives me a darker blue background. In the screenshot below, you can see the contrast between the blue of the neovim background and the rest of the terminal and status bar. Any suggestions on what I can do to change the background to the usual #114488?

Is your vim setup to use 24-bit color? Otherwise, as stated in the README it will look bad.

This is what I do:
set termguicolors
set t_8f=^[[38;2;%lu;%lu;%lum       " 24 bit colors
set t_8b=^[[48;2;%lu;%lu;%lum

The `^[^ is the escape character.

Oh don't know how I missed that. I'm using 256 colours. Will change it appropriately. Thanks!
Closing this now.


Cloud Provider choice does not install cloud provider onto cluster

Problem
Working with Harvester templates specifically I noticed that despite choosing harvester in the cloudprovider field, that the cloud provider itself was not provisioned in the cluster.
Expected Behavior
When choosing 'harvester' as the cloudprovider, the corresponding cloud provider configuration is dropped into the resulting Cluster manifest.
What Happens
The cluster is provisioned with Harvester as a node driver but does not include the needed inline kubeconfig file entry under `spec.rkeConfig.machineSelectorConfig[]'.
Desired Fix
I suspect this is difficult to fix as it sits in that acquiring the kubeconfig requires a reference to an existing secret before injecting the contents into a yaml file. Since I can't use kubectl explain to trapse the internal Cluster object docs (they are empty), I am uncertain if there is a secretRef option as opposed to an inline definition.
The other option is keeping the kubeconfig in the values.yaml file, but that presents problems with unencrypted secrets and could not be stored in a code repo without aid of something like SOPs or external secrets, etc.
However, instructions on how to manually inject this would be useful or at least highlighting it as a need.

Did you find a solve for this? I'm having a similar issue with the Harvester CSI driver. Works via the UI, but not through the Helm template...

I have found a workaround for that bug. I also opened an issue for in the harvester repo, but one developer said my workaround was already pretty good and they are not planning on fixing this and that not using the GUI with Cluster-Templates is an advanced use case that is not officially supported e.g. you are on your own trying to make it work.
You can see my workaround in the issue is mentioned here https://github.com/harvester/harvester/issues/4568

I feel this repo is pretty dead. We've pulled it in over at RGS and have been curating it here: https://github.com/rancherfederal/rancher-cluster-templates
Most of it has been rewritten but substantial fixes have already been implemented, Harvester CSI driver works great (although you have to include/generate a kubeconfig for it to work).


[INFINITY-1592] Automated TLS provisioning

WIP: https://jira.mesosphere.com/browse/INFINITY-1592

Hey ho hey; I have left a few comments in the documentation commit. This was not yet a thorough review, but what I saw look generally very good! Awesome stuff. :rocket:

@nickbp @benclarkwood I've removed kafka changes, squashed all commits and we now have only 1 integration tests failure:
https://teamcity.mesosphere.io/viewLog.html?buildId=731824&buildTypeId=DcosIo_DcosCommons_Hdfs_BuildAndTestPr&guest=1
The test_shakedown.test_modify_app_config is reported in the UI as flaky.
I believe this is ready to be merged.

Yes, HDFS is very flaky. I will attempt to get a non-flake today.
@mhrabovcin, please create a ticket to update the logic of the TLSEvaluationStage creation to not log an error when no TLS is requested. It will confuse users and lead to unnecessary support traffic :).

Ticket created - https://jira.mesosphere.com/browse/DCOS-17685

Closing to see if this retriggers the tests.


[EPIC] Improve traceability in the API

What is the expected enhancement?
When we have an error or we want to analyze a succession of events we don't have enough information from traces or the traces that we have are not the best ones. My proposal is to add traces in:

Views: for requests and responses with not sensitive information like id of a Job or a Program
Serializers: add traces with interesting information in the different overrided methods
Scheduler / Ray: review traces that we have here

Ref: #1263


Prices not being fetched correctly

Bug description
The pricefeed module is not fetching prices correctly, for any chain.
Steps to reproduce

Start the parsing of any chain that has a token listed on CoinGecko
Watch the price not being updated

Expected behavior
The price should be updated constantly

Should be fixed with 0a476e1af23e0f7f1455fa4afb59e1de7d2456ad


Table and navigation tweaks

Not sure why it was thought sub and primary nav styles could/should be merged – these have slightly different designs and more notably, different responsive behaviour
Use simpler markup for table captions
Consistently use table component for tables
Ensure tables have the correct scope attributes set
Review other markup in tables that differs from that in prototype

Looks great in general. Mind adding some screenshots since it's mostly visual changes?

@baarkerlounger Added screenshots. Also split sub and primary navigation components apart again in latest commit. Just want to cast an over that before I merge?


Revert "Revert "Revert "Revert "Balder/no more fs4 dispatching from fastsearcher""""

Reverts vespa-engine/vespa#10693
To be continued

@bratseth PR
It should now be ready for another run through system tests.

I assume that when you say prelude.ClusterController, you mean prelude.ClusterMonitor.
prelude.ClusterMonitor went away as it used ping over fs4.
search.ClusterMonitor is used by both search.ClusterSearcher (for external http based clusters), and search.dispatch.SearchCluster which is the rpc based dispatch.
Currently both prelude.ClusterMonitor and dispatch.ClusterMonitor has been monitoring the backends. When I removed monitoring of fs4 the hierarchic_distribution test started failing.
dispatch.SearchCluster which is the NodeManager for dispatch.ClusterMonitor would only control the vipstatus if it was a direct dispatch group/node. And would return 404 when 200 was expected.
After I got it to atleast put it into rotation, then I also had to make get it to take it out of rotation when all nodes in all groups where down.


LogProxyConsumer does not support dash-separated container names.

It is my understanding that the container_name in [container_name]-pebble-ready are a dash-to-underscore mapped version of the 'actual' container name.
LogProxyConsumer fails to implement this same logic and therefore gives:
  File "./src/charm.py", line 29, in __init__
    self.log_proxy_consumer = LogProxyConsumer(
  File "/var/lib/juju/agents/unit-loki-tester-0/charm/lib/charms/loki_k8s/v0/loki_push_api.py", line 1624, in __init__
    getattr(self._charm.on, "{}_pebble_ready".format(self._container_name)),
AttributeError: 'CharmEvents' object has no attribute 'loki-tester_pebble_ready'

When the container name is 'loki-tester'. Note that that is not a valid python identifier.
Solve by, in __init__:
        self.framework.observe(
            getattr(self._charm.on, "{}_pebble_ready".format(self._container_name.replace("-", "_"))),
            self._on_pebble_ready,
        )

Thanks for the report Pietro, I'll take a look at the PR.


[dv/otp_ctrl] dont compare direct_access_rdata_* on on non-integrity partitions

For non-integrity partitions (s.a. VENDOR_TEST), the OTP scoreboard backdoor reads the OTP in raw form (doesn't apply ECC corrections) and compares with actual data returned on the DAI interface. However, in case MacroEccUncorrErr is injected, the IP might try and correct the errors, and the result on the DAI won't match the actual raw data in that particular address.
This issue causes two failures:

Memory comparison. This has been mitigated in CS.

Register comparison for OTP_CTRL.DIRECT_ACCESS_RDATA_*. This is a bit trickier to override in CS, hence this PR is created to address the issue. Just skip the register comparison in case a MacroEccCorrErr or MacroEccUncorrErr happens when we access one of the non-integrity partitions.

@matutem: Could you review this please?

Great, thanks for the review @vogelpi.
@dkabely-ot if you could address this failing CI check, we should then be able to merge this afterwards:

Auto-generated OTP memory map not up-to-date. Regenerate with 'make -k -C hw otp-mmap'.

Hi @andreaskurth
Thanks!
It seems that this CI failure isn't related to the PR itself, however I rebased and re-pushed.

Thanks! It seems that this CI failure isn't related to the PR itself, however I rebased and re-pushed to check if it helps.

Ah, you also need to update hw/ip/otp_ctrl/data/otp_ctrl_scoreboard.sv.tpl, otherwise the file that you changed will get overwritten during the generation of autogenerated files
I took the liberty to do that

Hi @andreaskurth,

Thanks! It seems that this CI failure isn't related to the PR itself, however I rebased and re-pushed to check if it helps.

Ah, you also need to update hw/ip/otp_ctrl/data/otp_ctrl_scoreboard.sv.tpl, otherwise the file that you changed will get overwritten during the generation of autogenerated files
I took the liberty to do that

Thanks!

I don't see how this DV-only change could cause FPGA tests to fail.. merging

Thanks!


Container creation on Win10 required -isolation = hyperv

Freddy that's the issue we are told about in Twitter.
New-NavContainer crushes if I not set -isolation = hyperv parameter.
My Win10 build is 1809.
Docker desktop version <IP_ADDRESS>
Scripts used to create container and cause the issue
$artifactUrl = Get-NavArtifactUrl -nav 2017 -country 'ru' -select latest
$credential = New-Object pscredential 'admin', (ConvertTo-SecureString -String 'P@ssword1' -AsPlainText -Force)

new-navcontainer -accept_eula `
	            -containername nav2017 `
                -auth UserPassword `
                -credential $credential `
	            -artifactUrl $artifactUrl `
	            -includecside `
                -licensefile "c:\temp\lic.flf" `
                -updatehosts `
                -donotexportobjectstotext `
                -alwayspull

**Full output of scripts**

NavContainerHelper is version <IP_ADDRESS>
NavContainerHelper is running as administrator
Host is Майкрософт Windows 10 Корпоративная - ltsc2019
Docker Client Version is 19.03.3
Docker Server Version is 19.03.8
Removing container nav2017
Removing nav2017 from host hosts file
Removing C:\ProgramData\NavContainerHelper\Extensions\nav2017
Pulling image mcr.microsoft.com/dynamicsnav:10.0.17763.1282-generic
10.0.17763.1282-generic: Pulling from dynamicsnav
Digest: sha256:e27e27b7f105252fc38316209078d8f6111a5cf6e55a8e273672945e6549eca7
Status: Image is up to date for mcr.microsoft.com/dynamicsnav:10.0.17763.1282-generic
Using image mcr.microsoft.com/dynamicsnav:10.0.17763.1282-generic
Creating Container nav2017
Version: 10.0.30284.0-ru
Style: onprem
Generic Tag: <IP_ADDRESS>
Container OS Version: 10.0.17763.1282 (ltsc2019)
Host OS Version: 10.0.17763.1282 (ltsc2019)
Using locale ru-RU
Using process isolation
Disabling the standard eventlog dump to container log every 2 seconds (use -dumpEventLog to enable)
Files in C:\ProgramData\NavContainerHelper\Extensions\nav2017\my:

AdditionalOutput.ps1
AdditionalSetup.ps1
MainLoop.ps1
SetupVariables.ps1
updatehosts.ps1
Creating container nav2017 from image mcr.microsoft.com/dynamicsnav:10.0.17763.1282-generic
3a29e17da95edd803b89e01dc7765b9bcf0275a40638819ebfbe9f48c5db2bb8
Waiting for container nav2017 to be ready
Using artifactUrl https://bcartifacts.azureedge.net/onprem/10.0.30284.0/ru
Copying Platform Artifacts
Copying Application Artifacts
Copying Database
Copy Licensefile
Copying Installers
Copying TestToolKit
Copying UpgradeToolKit
Copying Extensions
Installing NAV
Starting Local SQL Server
Installing Url Rewrite
Installing SQL Clr Types
Installing Report Viewer
Installing OpenXML
Starting Internet Information Server
Copying Service Tier Files
Copying Web Client Files
Copying Windows Client Files
Copying PowerShell Scripts
Copying ConfigurationPackages
Copying Test Assemblies
Copying TestToolKit
Copying UpgradeToolKit
Copying Extensions
Copying ClientUserSettings
Copying ReportBuilder
Restoring CRONUS Demo Database
Determining Database Collation
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - The remote computer refused the network connection.)
at , C:\Run\navinstall.ps1: line 110
at , C:\Run\start.ps1: line 209
at , : line 1Error
Using artifactUrl https://bcartifacts.azureedge.net/onprem/10.0.30284.0/ru
Copying Platform Artifacts
Copying Application Artifacts
Copying Database
Copy Licensefile
Copying Installers
Copying TestToolKit
Copying UpgradeToolKit
Copying Extensions
Installing NAV
Starting Local SQL Server
Installing Url Rewrite
Installing SQL Clr Types
Installing Report Viewer
Installing OpenXML
Starting Internet Information Server
Copying Service Tier Files
Copying Web Client Files
Copying Windows Client Files
Copying PowerShell Scripts
Copying ConfigurationPackages
Copying Test Assemblies
Copying TestToolKit
Copying UpgradeToolKit
Copying Extensions
Copying ClientUserSettings
Copying ReportBuilder
Restoring CRONUS Demo Database
Determining Database Collation
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - The remote computer refused the network connection.)
at , C:\Run\navinstall.ps1: line 110
at , C:\Run\start.ps1: line 209
at , : line 1
Initialization of container nav2017 failed
C:\Program Files\WindowsPowerShell\Modules\navcontainerhelper\<IP_ADDRESS>\ContainerHandling\Wait-NavContainerReady.ps1:44 знак:17

...             throw "Initialization of container $containerName failed" ...

            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : OperationStopped: (Initialization ... nav2017 failed:String) [], RuntimeException
FullyQualifiedErrorId : Initialization of container nav2017 failed
...

Also error occurred with old-way container creation using -image parameter:

new-navcontainer -accept_eula `
	            -containername sb `
                -auth UserPassword `
                -credential $credential `
                -imageName mcr.microsoft.com/dynamicsnav:2017 `
	            -includecside `
	            -updatehosts `
                -donotexportobjectstotext `
                -alwayspull

Script output:
NavContainerHelper is version <IP_ADDRESS>
NavContainerHelper is running as administrator
Host is Майкрософт Windows 10 Корпоративная - ltsc2019
Docker Client Version is 19.03.3
Docker Server Version is 19.03.8
Removing container sb
Removing sb from host hosts file
Removing C:\ProgramData\NavContainerHelper\Extensions\sb
Pulling image mcr.microsoft.com/dynamicsnav:2017-ltsc2019
2017-ltsc2019: Pulling from dynamicsnav
Digest: sha256:2988688b51113d927c90f5924aa9525c43f3b7b9c05536c6fe05b8dac1cc207b
Status: Image is up to date for mcr.microsoft.com/dynamicsnav:2017-ltsc2019
mcr.microsoft.com/dynamicsnav:2017-ltsc2019
Using image mcr.microsoft.com/dynamicsnav:2017-ltsc2019
Creating Container sb
Version: 10.0.30284.0-W1
Style: onprem
Generic Tag: <IP_ADDRESS>
Container OS Version: 10.0.17763.973 (ltsc2019)
Host OS Version: 10.0.17763.1282 (ltsc2019)
WARNING: The container operating system matches the host operating system, but the revision is different.
If you encounter issues, you might want to specify -isolation hyperv
Using locale en-US
Using process isolation
Disabling the standard eventlog dump to container log every 2 seconds (use -dumpEventLog to enable)
Files in C:\ProgramData\NavContainerHelper\Extensions\sb\my:
- AdditionalOutput.ps1
- AdditionalSetup.ps1
- MainLoop.ps1
- SetupVariables.ps1
- updatehosts.ps1
Creating container sb from image mcr.microsoft.com/dynamicsnav:2017-ltsc2019
99b509112fdd04f23e06471430b633a8e192bbeefb44d7edd79ddcc7e9bffe9d
Waiting for container sb to be ready
Initializing...
Setting host.docker.internal to <IP_ADDRESS> in container hosts file (copy from host hosts file)
Setting gateway.docker.internal to <IP_ADDRESS> in container hosts file (copy from host hosts file)
Setting kubernetes.docker.internal to <IP_ADDRESS> in container hosts file (copy from host hosts file)
Setting host.containerhelper.internal to <IP_ADDRESS> in container hosts file
Starting Container
Hostname is sb
PublicDnsName is sb
WARNING: DNS resolution not working from within the container.
Using NavUserPassword Authentication
Starting Local SQL Server
Starting Internet Information Server
Creating Self Signed Certificate
Self Signed Certificate Thumbprint FE17E13AE3DE7F9B18971A9F674BB6467EBECDDB
Modifying Service Tier Config File with Instance Specific Settings
Starting Service Tier
Creating Web Site
Creating Web Server Instance
Creating ManagementServicesPort and setting it to 7045
Creating http download site
Setting SA Password and enabling SA
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
at <ScriptBlock>, C:\Run\SetupSqlUsers.ps1: line 13
at <ScriptBlock>, C:\Run\navstart.ps1: line 183
at <ScriptBlock>, C:\Run\start.ps1: line 121
at <ScriptBlock>, <No file>: line 1Error
Initializing...
Setting host.docker.internal to <IP_ADDRESS> in container hosts file (copy from host hosts file)
Setting gateway.docker.internal to <IP_ADDRESS> in container hosts file (copy from host hosts file)
Setting kubernetes.docker.internal to <IP_ADDRESS> in container hosts file (copy from host hosts file)
Setting host.containerhelper.internal to <IP_ADDRESS> in container hosts file
Starting Container
Hostname is sb
PublicDnsName is sb
WARNING: DNS resolution not working from within the container.
Using NavUserPassword Authentication
Starting Local SQL Server
Starting Internet Information Server
Creating Self Signed Certificate
Self Signed Certificate Thumbprint FE17E13AE3DE7F9B18971A9F674BB6467EBECDDB
Modifying Service Tier Config File with Instance Specific Settings
Starting Service Tier
Creating Web Site
Creating Web Server Instance
Creating ManagementServicesPort and setting it to 7045
Creating http download site
Setting SA Password and enabling SA
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
at <ScriptBlock>, C:\Run\SetupSqlUsers.ps1: line 13
at <ScriptBlock>, C:\Run\navstart.ps1: line 183
at <ScriptBlock>, C:\Run\start.ps1: line 121
at <ScriptBlock>, <No file>: line 1
Initialization of container sb failed
C:\Program Files\WindowsPowerShell\Modules\navcontainerhelper\<IP_ADDRESS>\ContainerHandling\Wait-NavContainerReady.ps1:44 знак:17
+ ...             throw "Initialization of container $containerName failed" ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (Initialization of container sb failed:String) [], RuntimeException
    + FullyQualifiedErrorId : Initialization of container sb failed

**Additional context**
If I add -isolation hyperv parameter - everything runs smoothly in both cases.

This is likely due to compatibility problems between host and container.
You should try to do the same using artifacts, where it is possible to get the same build/release of the generic image to base the container on.
I will close this one.
Please open a new one if the problem persists using artifacts.


base link and base footprint should be updated w.r.t the REPs

https://www.ros.org/reps/rep-0120.html
ROX and the real robot packages for the MP platforms follows the conventions.

The current setup with base_link as the child of base_footprint follows the REP convention.  However, the srdf files for both mpo_500 and mpo_700 in neo_mpo_moveit2 had to be updated with the relevanth <disable_collision> tags which fixed the issue.


Add python markdown div example

Edited in the external/imgui_md/imgui_md_wrapper/imgui_md_wrapper.h file,
updated with py external\imgui_md\bindings\generate_imgui_md.py

Thanks a lot, this is perfect, with the addition of having run the generator which is even more perfect. Thanks!

Thanks a lot, this is perfect, with the addition of having run the generator which is even more perfect. Thanks!

Thanks!
I had to apply a small patch on the generator for it to work on Windows (without destroying the line endings),
there is a PR for that as well.

Your contributions are first class! Do not hesitate to post more, if you so wish. I'm very opened to contributions like yours.

Your contributions are first class! Do not hesitate to post more, if you so wish. I'm very opened to contributions like yours.

Thank you!
I am in the process of experimenting with this bundle from c++ and python,
and considering how active you are, I will send in new patches when I encounter issues.


When is a description a prediction and when is it an observation?

The documentation states in several places that RNA descriptions should be surrounded by parentheses if "RNA has not been analysed". However, it is not specified how RNA should be analyzed or in what context. This leaves room for interpretation. Within the LOVD team and between submitters, this rule is interpreted in several ways. For example, a mini gene assay would be sufficient to provide evidence for an in vitro database record, but not everybody agrees whether this assay provides evidence for the RNA change in an actual patient.
After discussion in the HVNC meeting on February 12th, 2024, it was decided that it was not the place for the HVNC to define when an experiment provided sufficient evidence for the parentheses to be removed. As such, it will be left to the implementor of the variant description to make this consideration. We should add this to the documentation to highlight this problem so that people are aware of it.
Suggested implementation:

[ ] Find a good place to explain this situation (suggestion: recommendations/general.md).
[ ] Add text, e.g., "NOTE: the HVNC does not provide rules or regulations when an experiment provided sufficient evidence for a description to be considered not a prediction, but an observed change. This is left to the implementor of the variant description."
[ ] Add a  tag so we can link to this text.
[ ] Make sure all relevant pages mention the rule about predictions requiring parentheses (not al pages contain this info).

[ ] Add this to the DNA pages as well?

[ ] Add a link to the detailed explanation, e.g., "(see notes in the general recommendations)".
[ ] This may also solve the discussion of whether observing a change on RNA level is sufficient to consider a description on protein level an observation and not a prediction. We may choose to add this to the general recommendations page as well.

I do not agree with item 2 "NOTE: the HVNC does not provide rules or regulations ..". In my opinion, an in vitro mini-gene assay to study the consequences of a variant on RNA level is not enough to remove the parentheses in an r. description.  Parentheses can only be removed when RNA isolated from the sample of the individual which has the variant is analysed, i.e. RNA is directly sequenced or cDNA (a DNA copy of the RNA) is sequenced.
NOTE: LOVD has specific "in vitro analysis" records, in such a record the parenthesis may be removed).

I do not agree with item 2 "NOTE: the HVNC does not provide rules or regulations ..". In my opinion, (...)

As no definitions are currently stated on the website, the actual contents of the HGVS nomenclature website doesn't state any requirements for what "RNA analysed" means. We once discussed this in February, and then the decision was that we wouldn't state any specific rules. We would otherwise have to define this for every molecule. I do not remember whether we voted on this subject or just agreed on that call, which means that if you disagree, we may need to repeat the discussion to get an official decision.


Enhanced remote funktion and SX1276 option.

Describe you new feature you'd like
First: thank you for a really good and well-worked project.
I have implemented it with HA for 3 awnings and 2 slat curtains. For the latter, I have a Remote model Situo 5, which in addition to "Up", "Down" and "My" buttons also has a wheel around the "My" button. This ring is especially useful for blinds. It sends the code 0x0B, which has not normally been used for Somfy Remotes as far as I know. I don't know if it might be a consideration to implement it in your outstanding project.
With my old man's eyes, I'm better at software than hardware, and I had a lot of trouble connecting a Wemos ESP32 Mini D to the CC1101 module.
I have previously done a similar project where I have used a Lilly Lora T1 433Mhz module. It has everything gathered in one module including an oled display, and there are 3D files for built-in boxes available on the web. A good overall solution. It use SX1276 instead of CC1101. Could it be a consideration to make this a possible alternative?..

I have looked at the SX1276 and do have plans to remove the Elechouse libraries.  It is on the list.   However, ESPSomfy RTS already supports all of the 80-bit command set including Step Up/Down with the ability to send the step size.  This is only available when the motor is defined as an 80-bit RTS.

Thanks for quick reply.
I was not aware of the 80-bit option - looks great.
I would look forward to the SX1276 solution.
Best regards
Erik

Fra: rstrouse @.>
Sendt: 12. september 2024 18:35
Til: rstrouse/ESPSomfy-RTS @.>
Cc: Erik Palsbo @.>; Author @.>
Emne: Re: [rstrouse/ESPSomfy-RTS] Enhanced remote funktion and SX1276 option. (Issue #470)
I have looked at the SX1276 and do have plans to remove the Elechouse libraries. It is on the list. However, ESPSomfy RTS already supports all of the 80-bit command set including Step Up/Down with the ability to send the step size. This is only available when the motor is defined as an 80-bit RTS.
image.png (view on web)https://github.com/user-attachments/assets/0c4873ad-3f27-4045-8949-b9a7570c340a
—
Reply to this email directly, view it on GitHubhttps://github.com/rstrouse/ESPSomfy-RTS/issues/470#issuecomment-2346763573, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAYJU44DVLM5PUKNHOCHMRDZWG7GDAVCNFSM6AAAAABODNWJAGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBWG43DGNJXGM.
You are receiving this because you authored the thread.Message ID: @.***>


License Clarification Flipped Chamfer

@demseyk nice work on the Flipped Chamfer design, could you please advise on which specific Open Source license (e.g. MIT/CC by SA/etc.) you're releasing your work under?
https://github.com/sqfmi/watchy-cases/tree/main/Flipped Chamfer

@darigovresearch The Flipped Chamfer Design and Flipped Fillet Design are both released under the MIT license.

Thanks @demseyk, pull request https://github.com/sqfmi/watchy-cases/pull/38 should resolve this issue if you're happy with it


Can't map to Redactor field type

Despite the claim that the plugin supports mapping GC fields to "Rich Text" fields in Craft, Redactor fields are not selectable as targets in the map. I'm guessing this has something to do with "Rich Text" no longer being a built-in field type as of 3.0.0-RC1.

Indeed, the plugin source code still only refers to craft\fields\RichText and not to craft\redactor\Field.

Also note that CKEditor is the other recommended rich-text replacement plugin.

Thanks for your feedback! CKEditor and Redactor support is added in latest release.


fix: Microsoft.OpenAPI package reference conflict

Add upper bound to Miicrosoft.OpenAPI package reference to Swashbuckle.AspNetCore.Swagger project to be less than 1.2.0 as it breaks contains breaking changes for  Swashbuckle.AspNetCore.Swagger project
fixes #1717

Better to put some pressure on them to fix it properly so everybody can move to 1.2.x (or 1.3.0 if they want to name it that)
https://github.com/microsoft/OpenAPI.NET/issues/487#issuecomment-648976686

Wait to merge this, fixing it at the source: https://github.com/microsoft/OpenAPI.NET/pull/492


Xpipe Linux - Change default shell ?

Hi, 👋🏻
I've been using XPipe for a few days and was wondering if it was possible to change the default shell for the local connection.
It's set to bash and I'd like to use zsh.
When I open my terminal emulator directly, zsh opens, but when I launch it from XPipe, bash opens (bash -l).
Thanks for any help you can give me :)

It's not possible to change the default shell but hopefully soon you can change the shell to login with for every system, see https://github.com/xpipe-io/xpipe/issues/288

Effectively that is probably what you're looking for. It's just that even if you would switch to zsh that way, bash would still be used as a default for any background operations.

Good to know, thanks for your reply :)

Meanwhile you can create a zsh shell environment manually and use that one

I'll try this, I haven't explored all the configuration options yet :)

You can either search for connections automatically and enable the available shells option to get a zsh environment or create one manually at New ... -> Shell environment


Add Hawkie singing "Super Sonic Racers"

Thazon: @Kuoxsr Is there any instance of Hawk singing the Sonic Riders theme in the pack? If so, where?
Note to self: should this go in a music disc, or should it be a raid celebration sound?  Or some other event?

This one is for @Thaz0n.
With this issue complete, my milestone has been reached.  I just need to do some final testing, write the change log and create the packages for the version 3.0 release.  It should be within the next couple of days (certainly not longer than the end of the weekend.)


Forms System

[x] Forms Database

formId
formType
formData
creationTimestamp

[x] Backend

Submit post

formType
formData

Was completed and published in the inoft_vocal_engine. I made the mistake of creating the issue in the inoft_vocal_framework.


Resolve the 'todo' failure case handling.

Adds handling of the 'bad API key' and 'location unavailable' failure cases.
Also removes redundant success/failure callbacks (JS running implies watch connectivity) and removes extra key.h file.

:+1:


Retries option for rt docker-push/pull

Is there a plan for adding --retries option for rt docker-push/pull commands?

@faraonc,
Can you please share the reasons for adding this functionality?

@faraonc,
Can you please share the reasons for adding this functionality?

There are times docker login during docker-push to Artifactory fails due to some issue with the network causing the CI/CD pipeline to fail. My current work around is to wrap the jfrog rt command with retry function in bash.

Thanks @faraonc.
So we should add the retries to the login part of the command.

@eyalbe4  @faraonc retries option is available only for login right.
In our case docker login succeeded however during push its says preparing and then retry stage and fails after few seconds.
retry argument is not available for docker push right, how do we overcome retry issue during push?