Unclear warning about deprecated services in 3.0.0 Beta 3

@msp1974:
Following services are considered as deprecated from v3.0.0, with following warning message in logs: %s service has been deprecated.  Please update to use the new service for this function
DEPRECATED_SERVICES = [
    "update_health_status",
    "lock_vehicle",
    "unlock_vehicle",
    "reset_alarm",
    "honk_blink",
    "start_charging",
    "stop_charging",
]

It's not clear from the warning message what we mean with "please update" and which new service should be used instead. Can we provide more user friendly message to guide the user in right direction for migration?
I guess we want the user to use the new buttons services in stead of direct service call? That works for manual service invocation, but what about automation? Do we want to force the users to use the "Press button" service to invoke the new button services? Im not completely sure we can completely remove these services, since they are required for the button services and useful in the automations.

Yes, think we can make that message better.  Idea is that yes, you use the switch.turn_on/off and button.press service instead of the custom service as this is now redundant.  Will look at that.
Thanks for all great testing and feedback.

I'm also getting problems trying some of the new switches.
Charging (I'm not quite sure what this is supposed to do, but...), when switching on:
Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/commands.py:238
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 14:13:05 (1 occurrences)
Last logged: 14:13:05

[140581630699328] 'NoneType' object is not iterable
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 238, in handle_call_service
    response = await hass.services.async_call(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2149, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2186, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 272, in handle_service
    return await service.entity_service_call(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 882, in entity_service_call
    single_response = await _handle_entity_call(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 952, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/config/custom_components/jlrincontrol/switch.py", line 81, in async_turn_on
    params = self.get_service_params(True)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/jlrincontrol/switch.py", line 125, in get_service_params
    params = list(service.get("params"))
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: 'NoneType' object is not iterable

Climate : in the JLR app, I have the option of using either "Engine Climate" (which only works when the charge cable isn't plugged in) or "Electric Climate". If I try to use the new switch it doesn't appear to do anything (the car is currently plugged in, although I don't see any errors)

This is not related to this issue, can you raise as a new issue and provide a diagnostics file and i will have a lok at it. Thx

Yes, think we can make that message better. Idea is that yes, you use the switch.turn_on/off and button.press service instead of the custom service as this is now redundant. Will look at that.

I have an idea on this one, will create PR

@msp1974 I have suggested an adjustment to the warn message in #128.
btw: since we want the user to use the switch, button and lock services from v3.0.0 in stead of the old custom services, shouldn't we remove the new services in 3.0.0 from the services.yaml, so we can hide them in the HA UI? I guess that services can still be called directly from our code, even if they are not present in the services.yaml?
Im thinking of these new services added in v3.0.0:

enable_journey_recording
disable_journey_recording
enable_guardian_mode
disable_guardian_mode
enable_service_mode
disable_service_mode
enable_transport_mode
disable_transport_mode

These new services serve a specific case of being able to provide a datetime until which is then different from just the switch_turn on service which uses a default 24h (or whatever is set in options).  I need to update docs to explain all this better.
The deprecated ones have no aditional options over the new entities.

These new services serve a specific case of being able to provide a datetime until which is then different from just the switch_turn on service which uses a default 24h (or whatever is set in options).

Aha, I did not catch this. Agree with you that they are useful when they are different from the switches. Although the new service enable_journey_recording has no datetime fields so it could maybe be removed?

Edit: except journey recording which yes i agree and maybe disabling services also have no merit, but is that then more confusing if enable services exist?

Agreed - I think that we should expose disabling services for corresponding enabling services to make the "API" more complete and less confusing.

ok, this is all now in dev.


Docker Hub repository name
dockerpulse/dockerpulse
Terms of services

[X] I accept the term of services

Hi @leejun07.
The extension has been removed from the marketplace after we received confirmation about the extension name violating our trademark.

Hey @lucbpz,
Sorry about that! We did not intend to violate your trademark. We are currently brainstorming new names. Would a name like DockPulse still be in violation or is that a bit on the nose?

Hi @patrickv77. No worries! Can you address the question to my colleagues from<EMAIL_ADDRESS>They can help you with any naming questions.

Sorry about that again @lucbpz! We will be sending them an email shortly. Thanks for the quick reply!


Set of small fixes

Coverage increased (+7.07%) to 46.945% when pulling 4aa3180e7e40825c88f08873d9c953e8f2a5a54e on set-of-small-fixes into ed48a1c495c55f6fda0a7cb9053f13d04ec8f02e on master.

Coverage increased (+7.07%) to 46.945% when pulling 407a6d9267e3af7de3408e3ca5d54ee09d5bdf51 on set-of-small-fixes into ed48a1c495c55f6fda0a7cb9053f13d04ec8f02e on master.

@maretskiy I merged another patch seems like we can close this one

Coverage remained the same at 97.241% when pulling 58419dd8dca88ae52f6c3446904289301c8c2efd on set-of-small-fixes into c2bf9ac1544726ce64962d0781a943e7fe191545 on master.

Coverage remained the same at 97.241% when pulling 58419dd8dca88ae52f6c3446904289301c8c2efd on set-of-small-fixes into c2bf9ac1544726ce64962d0781a943e7fe191545 on master.


sane required npm version

Proposal description
required npm version is quite high. I can't setup the framework with npm i as instructed here: https://embark.status.im/docs/contributing.html

When I run npm i

Okay, my mistake, I thought it was an error in stating the required npm version. Happy to use Yarn. I recommend the contributing guide (https://embark.status.im/docs/contributing.html) is updated as it instructs using npm.

I'll await alpha 2 and see how I get on with yarn. At present I can't build or run tests as per the package file, it looks like there is a lot of dependence on npm there (within the package scripts).

@samthomson you should be able to install embark from latest master using yarn and building it accordingly.

Happy to use Yarn. I recommend the contributing guide (https://embark.status.im/docs/contributing.html) is updated as it instructs using npm.

Absolutely! We're aiming to get all docs straight before 4.0.0 stable hits the road!

@samthomson npm is still used, definitely in the "scripts" of embark's package.json. The requirement applies to doing yarn install instead of npm install, after cloning the repository.


Mark linux_large_image_changer_perf_android unflaky

Last 50 runs flaky and failed number is 0.  15 day flake ratio is under 2%.
Marked flaky in https://github.com/flutter/flutter/pull/82754.  Likely fixed by https://github.com/flutter/flutter/pull/82739.  See https://github.com/flutter/flutter/issues/82747.

@CaseyHillers or @christopherfujino did I do this right with the new .ci.yaml?


feat: overhaul setup of LUMIGO_TRACER_TOKEN

On AWS Lambda, user SecretValue.unsafeUnwrap instead of SecretValue.toString to avoid errors when the user has set the CHECK_SECRET_USAGE flag.
On ECS, try to construct an ECS Secret object from the SecretValue by reverse-parsing the CfnDynamicReference. SecretManager Secrets and SSM Secure Parameters are supported, with and without version.

@hoegertn WDYT? I think the functionality is cool (I positively hate to make a secret in ECS less secret by unwrapping it), but the implementation is... adventurous.


Add option to create exp.ini without running autonom script

Can I have more detail about this work.
My understanding is that we need a button that create the exp.ini file (usually needed by runautonNOM) but the algo should stop there... and that's it. Is that correct ?

Exactly. Create the file but do not run the autoNOM script.
The reason is that in some cases, we want to use the FastGR as an exp.ini text editor. We take the created exp.ini file to either 1) check that it looks right or 2) use it outside of FastGR.


Stuck at NEEDRESTART-KSTA: 1

Hello there,
The latest version get stuck at NEEDRESTART-KSTA: 1 .
I'm using ubuntu-latest runner and all setting are correct except for DNS which is the PR [()is](Add dns input parameter) not yet approved .
Please help with a resolution/explanation
Thanks

Stuck here too, did you find a work around :(

Also have this issue, tried using ubuntu-22.04 instead of ubuntu-latest but it didn't help


control plot_x key

A scan (e.g. ascan) using energy pseudo axis at SRX now uses undulator gap as the default x for live plot.
It needs to be energy.
A more general question, how to set up x axis for plotting when using ascan, dscan, etc.
Namely, I do not want to define my own plan, in which can can use this?

my_plotter = LivePlot('det', 'motor', legend_keys=['sample'])
RE(my_scan, my_plotter)

And shall I be concerned with the message
"Failed to stop Energy(prefix='', name='energy', read_attrs=['uv', 'bragg', 'c_gap', 'move_uv', 'move_cgap'], configuration_attrs=['uv', 'move_uv', 'move_cgap'], monitor_attrs=[])"?
I've tried using both ascan and just run the AbsScanPlan in RE. Same error message.

@tacaswell Are either of these still relevant after your work today? The second issue ("failed to stop...") probably means you did not define a stop method on the Energy pseudo-positioner.

Before I forget - @imrealkaren wants PLOT_X for spec-like scans that functions similarly to PLOT_Y

It is a Device so it should get a stop from that.

And once people start wanting two plots (as CSX just indicated that they do) they'll want PLOT_X1 and PLOT_X2.... I think we need to see if a collection of plans in the beamline config can do the job. A proliferation of gs.* is going to get really confusing.

X1, X2, etc seems excessive, but given how easy and useful it is to configure PLOT_Y, PLOT_X really seems like a feature that should be there.

:+1: on adding just the PLOT_X.
On Fri, Feb 12, 2016 at 6:03 PM K Lauer<EMAIL_ADDRESS>wrote:

X1, X2, etc seems excessive, but given how easy and useful it is to
configure PLOT_Y, PLOT_X really seems like a feature that should be there.
—
Reply to this email directly or view it on GitHub
https://github.com/NSLS-II/bluesky/issues/331#issuecomment-183519550.

K. Just pushing back for the sake of being conservative. I'm convinced.

We probably need to start scoping the gs namespace.  I think with multilple panel plots we need to move away from ascan + special state to named scans/plans the close over a specific set of motors, detectors, and subscriptions.

Given the progress we are making pushing some groups toward OO, I hate to see the SPEC-style API bloat before we even have the chance to teach the good API.

Let me phrase my last comment differently....
Providing lots of nobs for customizing ascan seems more difficult for users than supporting a couple different scans -- ascan_slits, ascan_diff_eta, etc. Bluesky can't ship all thoes varieties, but I think we can build them in beamline configs, plugging in the appropriate subscriptions in each case. Once we address the ~10 scans that beamlines perform, will there be much demand to mutating their settings through gs?

The PLOT_Y key is gone now and, with it, the needs for this. This is now addressed by the 'hints' feature.


chore(publisher): bump refresh interval to 20 seconds

closes #3203

Code LGTM.

Is this necessary now? See #3203. The etcd timeout itself was already at 20 seconds, which is parallel with other components, and this makes it 40 seconds. Maybe I'm misunderstanding the two timeout values here, but it's unclear to me what this fixes. (But if it does, it closes #3203.)

Yes, I think I was mixing up the differences between the two. We have already bumped this value before. Closing.


coverage: Add codecov support to .travis.yml

Add codecov support (copied mostly from Spack) to .travis.yml.
If this works we should see coverage at http://codecov.io/gh/llnl/hatchet.

This is passing, but the report doesn't appear to show up on codecov.io. I see a token to use when uploading reports, but I'm not sure where to apply this.

We weren't actually running the coverage reports 😄.  But after adding a coverage run to the script, we're in business.  Now, unfortunately, we're only 54% covered -- we'll have to work on that!


feat: add load default layout button to dev panel

added a button to load the default layout file.
i moved the default layout file into the plugin to ensure artists don't delete it/move it.
also, i can also set it to load the default layout on default but i'm not sure if artists would want that cos personally, it'll be annoying. we can move the placement of the button though.

this change means we'd have to remove the layout from the template btw.

Ah. I looked at this yesterday and then got distracted
Rather than a button - I was thinking it should be in the dropdown right above "logout" -- basically anything that is VERY rarely used and is more about setting up your entire "Filta State" should probably go in the Filta dropdown menu

-- basically anything that is VERY rarely used and is more about setting up your entire "Filta State" should probably go in the Filta dropdown menu

hm hm makes sense.


Skip links to do not move focus

[x] I’ve read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I’ve read and agree to the Code of Conduct.
[x] I’ve searched for any related issues and avoided creating a duplicate issue.

What happened
Skip links do not move focus in Chrome. Tabbing onto a skip link and then pressing enter moves the viewport to the correct location, but subsequent tabs show the focus does not actually move.
For example, tabbing onto 'Skip to main content' and then pressing 'Enter' will move the viewport to the top of the main content, but then a second tab will cause the 'Skip to navigation' link to receive focus.
Destination anchors need a tabindex of -1 for the focus to move properly.
I suggest the documentation be updated to include this information.
What I expected to happen
When using a skip link, the keyboard focus should move along with the visual focus.

This is a funny one which runs into old school web. It definitely behaves differently in various browsers.
The destination needs to be an anchor to capture focus: . This means the UITK may need to pick a different ID so it won't clash.

Thanks @imperator99 there should now be more detailed documentation around this.


html2canvas display resolution

When i set my display resolution to 800x600 i have corrupted results, actualy results change according to resolution is there a way to stabilaze results with f.e scale option, and like %10 of attempts i have corrupted results with same inputs
Results with 1920x1080(which is desired);

Result with 800x600;

You can reproduce by changeing your screen resolution.
Best.

Following

Without a jsfiddle repro, it's hard to say what the issue is (it could be that your css/dom doesn't for example with into 800x600)


Feature Request: Web

Hey,
It would be great if I could access subscription status from the web, off a user ID. I am using plugin across all platforms (web, app store, google play) and currently need to do my own server-side/web hooks to get this info to be used on the web.
If everything could be wrapped up in this one app, would make life a lot easier.
Thanks,
Rob

Hey Rob,
We have our /subscribers API endpoint which should help with this for you. Hitting this endpoint gets the latest Customer Info for the customer with the given App User ID, or creates a new customer if it doesn't exist.
Let me know if that helps!


Replace the akka with pekko in the doc page

Replace the akka with pekko in the doc page
not includes the part about aws cloud

I want to go to this PR.
I spent about 2 hours today replacing akka/alpakka in the document with pekko/pekko connector


This is to make GitHub provide me access to the GRPC repo

Verify me!

Verification done. Closing Pull request


Fix broken link stylings on CmsViewer

Description
Fix link stylings on CmsViewer

Screenshots

Related Issue
N/A

Pull Request Type
Please check the type of change your PR introduces:

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation changes

Checklist

[x] My code follows the code style of this project.
[ ] I have updated the documentation.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Does this introduce a breaking change?

[ ] Yes
[x] No

@aarontitus @tabiodun Can someone please merge this and push to production?


report session in log

I need to fix a lot of these , so the session ID will make it quicker
https://curation.pombase.org/dumps/latest_build/logs/log.2022-01-19-21-32-38.chado_checks.exists_during_extensions_not_in_cell_cycle_phase

and here
https://curation.pombase.org/dumps/latest_build/logs/log.2022-01-19-21-32-38.chado_checks.happens_during_extensions_not_in_cell_cycle_phase

I've added a session ID column which should be there in the morning.


Require zend-math

This module requires zend-math to work (e.g. for Validate\Csrf) so there should be a dependency in package.json.

However when you are not using Csrf you don't need that dependecy.
We are aware of this kind of issues related with optional dependencies. We have choice to require as less dependencies as we can and delegate to the developer the task of require the optional dependencies he/she need.

I think that is the wrong decision because it defeats the purpose of a dependency manager like composer. If you want people to manage dependencies manually you should probably not have a package.json at all.

Regardless of whether or not you feel the decision is "correct", it is the decision we've made. Since all validators are opt -in, installing the dependencies required for all validators is a disservice to those using a subset of them. If you're already using Doctrine, you'd likely be upset if this component also installed zend-db!
The other option we have is to move any validators with additional dependencies into their own components, which is something we may do in the future. For now, we are declaring the bare minimum dependencies required to use the component, and marking anything else as a suggestion.

I understand it's the decision you've made, but I still think it's the wrong one. It's not just that I wouldn't mind if you installed dependencies I didn't need, it's that I would actually prefer it to the alternative (which is manual dependency management).
However, I also think the better option is to move the validators into components of their own.
On 27 maj 2016 18:47 +0200<EMAIL_ADDRESS>wrote:

Regardless of whether or not you feel the decision is "correct", it is the decision we've made. Since all validators are opt -in, installing the dependencies required for all validators is a disservice to those using a subset of them. If you're already using Doctrine, you'd likely be upset if this component also installed zend-db!
The other option we have is to move any validators with additional dependencies into their own components, which is something we may do in the future. For now, we are declaring the bare minimum dependencies required to use the component, and marking anything else as a suggestion.
—
You are receiving this because you authored the thread.
Reply to this email directly,view it on GitHub(https://github.com/zendframework/zend-validator/issues/83#issuecomment-222196438), ormute the thread(https://github.com/notifications/unsubscribe/AA9DskBctllybcKqAuhVG4OTe6Z9qOR9ks5qFyAigaJpZM4Ioo_a).

Maybe in suggest section (in composer.json) should be said that zend-math component is required by the Csrf validator (as it for other suggestions)


Support for iOS ProximityReader

With iOS 16, Apple released the ProximityReader API. This could be used for a variety of uses such as iPhone to iPhone NFC data transfer.
Under the secure layer of Apple Pay, this could be a major feature to enable developers to create secure data transfers using NFC.
More info:
https://developer.apple.com/tap-to-pay/
https://developer.apple.com/documentation/ProximityReader

@tylercallison thanks for the infomation! I'll definitely take a look!

@whitedogg13 Do you think this would be something we might see implemented within this library?


Crash when trying to go one directory up while being in disk root directory

Description
While in a disk root directory (e.g. C:\), where I've got from "Home" tab, I tried to click "Up" button and application crashed.
Steps To Reproduce

While in Files application, go to "Home" panel (left side panel).
Select any hard drive and move into it (for example, into C:\ directory).
Press "Up" button (or hit Alt-Up as well).

Requirements
While being in the root directory of any disk, this button should be either unavailable to press or should pass you to the "Home" panel.
Files Version
<IP_ADDRESS>
Windows Version
10.0.19045.3693
Log File
debug.log

Thanks for the report, can you see if this is an issue in the preview version. https://files.community/download

No, this is resolved in Preview version.
Thanks for such a quick reaction.


[stable/kafka] affinity rules are not reading the {{ .Release.Name }}

Describe the bug
added affinity rules for kafka metrics pod but it is not reading {{ .Release.Name }} from the values file
        podAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            - labelSelector:
                matchExpressions:
                  - key: app.kubernetes.io/name
                    operator: In
                    values:
                      - kafka
                  - key: app.kubernetes.io/instance
                    operator: In
                    values:
                      - "{{ .Release.Name }}"
              topologyKey: `"kubernetes.io/hostname"

Version of Helm and Kubernetes:
Helm version: version.BuildInfo{Version:"v3.5.0", GitCommit:"32c22239423b3b4ba6706d450bd044baffdcf9e6", GitTreeState:"clean", GoVersion:"go1.15.6"}
Kubernetes version: Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.5+vmware.1", GitCommit:"f4553304874c3b89584280a5ac1b005d57c725a8", GitTreeState:"clean", BuildDate:"2021-03-22T17:07:14Z", GoVersion:"go1.15.8", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.11+vmware.1", GitCommit:"581335ed759cada5037cc08960ce95d73170087f", GitTreeState:"clean", BuildDate:"2021-09-17T00:48:38Z", GoVersion:"go1.15.15", Compiler:"gc", Platform:"linux/amd64"}
What you expected to happen:
it should read the release.name
How to reproduce it (as minimally and precisely as possible):
add affinity rules to the kafka metrics pod like below and install the chart
        podAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            - labelSelector:
                matchExpressions:
                  - key: app.kubernetes.io/name
                    operator: In
                    values:
                      - kafka
                  - key: app.kubernetes.io/instance
                    operator: In
                    values:
                      - "{{ .Release.Name }}"
              topologyKey: "kubernetes.io/hostname"

Any help would be appreciated

I checked the kafka exporter deployment.yaml file, the affinity template is not reading the common.tplvalues.

Hi, @banicr - If your question applies to the Bitnami helm chart for Kafka, please see https://github.com/bitnami/charts/tree/master/bitnami/kafka and open an issue there if desired. This issue queue will not receive an answer. Thanks.


Fix [#98674838] (iframe edit bug)

moved PeerAccess module into services, added '#ssl_if_we_are' method & tests.
iframe edit bug → https://www.pivotaltracker.com/story/show/98674838

This pull request is mostly a test for a trivial method.  :)  But I had fun.

:+1:

One problem: somehow this caused failing tests in travis.  I just started trying to hunt it down.

The failed tests were these:
   1) Portal::TeacherClazz preserving leagacy one to many mapping for teachers <= clazzes clazz.teacher reader should return the first teacher if there is one
   Failure/Error: clazz.teacher.should == teacher

  2) User disallows illegitimate logins: 'plus+'
       Failure/Error: lambda do
     count should not have changed, but did change from 3 to 4
     # ./spec/models/user_spec.rb:86:in `block (4 levels) in <top (required)>'

Are these known to be volatile?

#1 is known to volatile. #2 just started showing up. #1 has been there for
a few weeks.
#1 seems to be caused by the ordering of elements in the database. My guess
is that our current approach is not good enough when two teachers are added
so close together in time.
#2 might be the same thing, however it started showing up just after I
merged the large Zeus commit yesterday. So it might be a real failure. They
did change the User code.
On Fri, Jul 10, 2015 at 9:38 AM, Noah Paessel<EMAIL_ADDRESS>wrote:

The failed tests were these:

Portal::TeacherClazz preserving leagacy one to many mapping for teachers <= clazzes clazz.teacher reader should return the first teacher if there is one
Failure/Error: clazz.teacher.should == teacher

User disallows illegitimate logins: 'plus+'
Failure/Error: lambda do
count should not have changed, but did change from 3 to 4
./spec/models/user_spec.rb:86:in `block (4 levels) in <top (required)>'

Are these known to be volatile?
—
Reply to this email directly or view it on GitHub
https://github.com/concord-consortium/rigse/pull/99#issuecomment-120413852
.

--
Scott Cytacki
The Concord Consortium
http://concord.org


Sync mio TCP and libstd TCP APIs

Rename take_socket_error to take_error, tweak return type.
Add property accessors in addition to set_property
Rename set_keepalive to set_keepalive_ms to make room for Duration later
on.

Closes #458

Thanks. Merged into dev: e436792cb842cc0f3b7d37ff344cfd0565eba3af


Release commit for v2.9.0

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Excellent! Super looking forward to having this release due to improved cold starts


Mariadb container can't start with volume

Configured volume for mariadb service, to save the data, but faced the problem, when I try
docker-compose up -d
Mariadb container starts, I see it "done", but after it instantly exites with the error in logs
Initializing database,
2019-08-25 18:45:52 0 [ERROR] InnoDB: The Auto-extending innodb_system data file './ibdata1' is of a different size 0 pages than specified in the .cnf file: initial 640 pages, max 655360 (relevant if non-zero) pages!,
2019-08-25 18:45:52 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error,
2019-08-25 18:45:52 0 [ERROR] Plugin 'InnoDB' init function returned error.,
2019-08-25 18:45:52 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.,
2019-08-25 18:45:52 0 [ERROR] Unknown/unsupported storage engine: InnoDB,
2019-08-25 18:45:52 0 [ERROR] Aborting,
,
,
Installation of system tables failed!  Examine the logs in,
/var/lib/mysql/ for more information.,
,
The problem could be conflicting information in an external,
my.cnf files. You can ignore these by doing:,
,
    shell> /usr/bin/mysql_install_db --defaults-file=~/.my.cnf,
,
You can also try to start the mysqld daemon with:,
,
    shell> /usr/bin/mysqld --skip-grant-tables --general-log &,
,
and use the command line tool /usr/bin/mysql,
to connect to the mysql database and look at the grant tables:,
,
    shell> /usr/bin/mysql -u root mysql,
    mysql> show tables;,
,
Try 'mysqld --help' if you have problems with paths.  Using,
--general-log gives you a log in /var/lib/mysql/ that may be helpful.,
,
The latest information about mysql_install_db is available at,
https://mariadb.com/kb/en/installing-system-tables-mysql_install_db,
You can find the latest source at https://downloads.mariadb.org and,
the maria-discuss email list at https://launchpad.net/~maria-discuss,
,
Please check all of the above before submitting a bug report,
at http://mariadb.org/jira,
,

My docker-compose.yml
mariadb:
    image: wodby/mariadb:$MARIADB_TAG
    container_name: "${PROJECT_NAME}_mariadb"
    stop_grace_period: 30s
    environment:
      MYSQL_ROOT_PASSWORD: $DB_ROOT_PASSWORD
      MYSQL_DATABASE: $DB_NAME
      MYSQL_USER: $DB_USER
      MYSQL_PASSWORD: $DB_PASSWORD
    volumes:
      - ./local/mysql:/var/lib/mysql # Use bind mount

Using windows 10 and Hyper-V virtualization

Replied in https://github.com/wodby/mariadb/issues/21

I have the same problem
any idea?


in convert_pose.py, how does the initial orientation come?

I'm planning on export more keypoints to generate vmd. And I meet difficult when trying to add more skeleton. I dont know why in "initial = QQuaternion.fromDirection(QVector3D(0,1,0), QVector3D(0,0,1))" it's from (0,1,0) to (0,0,1). How to set initial orientations?

@ddddwee1


  Eg, you have push loaded as both a network module and a user module, and ZNC isn't making that obvious.  I'd suggest using the controlpanel module to verify your list of network and user modules, and make sure that ZNC is only loaded as either a user or network module, and not both.

Not possible as I was using the Python module. Currently I am running without modpython and I don't have access to any supported service so I don't have the module loaded.

Perhaps this was related to #139 ?

I don't think so as my ZNC only has one user, me.

Title updated as I am currently using Pushbullet and just got this message again.
2016-01-19 18:00:22+0200 < *push> HTTPSConnectionPool(host='www.notifymyandroid.com', port=443): Read timed out. (read timeout=1)

I am still the only user.

Between that and the lack of any bumps indicating other users have encountered this issue, yeah. Let's close it. Reopening is only a click away, after all.


Multi dof action extension

Alternate approach for #16
Adds trajectory_msgs/MultiDOFJointTrajectory to FollowJointTrajectory.action goal, as well as some related fields.
Since this changes a core message, we should probably create a galactic-devel fork and merge there instead. However, adding the field shouldn't break too much since robots without a MultiDOF joint can just ignore the component.

This is a fairly major change and I'd like to see some current motivation for this.
Is it to add some cartesian constraints? Planning for a mobile manipulator including the base?

First thought is that the name is misleading. MultiDOF sounds like a normal 7-DOF arm with revolute joints. The name is also confusing because MoveIt supports a single joint having more than one degree of freedom, like a shoulder joint (but it's rarely used).
Maybe call it MixedDOFJointTrajectory? Or MixedTypeJointTrajectory?

This PR adds support for single joints that have more than one degree of freedom, i.e. planar/floating. It adds a Trajectory for MultiDOFJoints, not a JointTrajectory with MultiDOF, if that makes sense.
Either way, the naming reflects the existing names from trajectory_msgs.

Also, I've slightly modified the MultiDOFJointTolerance message to specify how to actually calculate the differences, based on the component field.

What do you think @bmagyar ?

Is the rationale for extending the existing message the fact a multi-dof joint is still a "joint", as in contrast to Cartesian waypoints, trajectories (& associated goals) which do not really fit in at the joint level any more?
I'm asking because it doesn't necessarily seem proper to me to make FollowJointTrajectory.action a union capable of supporting all these different use-cases. Or perhaps in other words: does this semantically make sense? Are there any other future extensions expected?

It definitely extends the scope of this message and opens a lot of possibilities for new use-cases.
The whole-body motion planning aspect is what was really convincing to me.
I have one ask though:
multi_dof_path_tolerance et al is a hazy name IMO. Can we come up with anything better than this to better describe it? We can't change the message type name but the local member name should be improved.

floating_joint_path_tolerance?
transform_path_tolerance?

Is the rationale for extending the existing message the fact a multi-dof joint is still a "joint", as in contrast to Cartesian (fi) waypoints, trajectories (& associated goals) which do not conceptually really fit in at the joint level any more?

The concept of "joint" is rather wide, but yes, the rationale is that planar and floating are the two multi-dof joints defined in the URDF spec, and are thus still "joints". Furthermore, MoveIt treats them as joints and can plan for them.

I'm asking because it doesn't necessarily seem proper to me to make FollowJointTrajectory.action a union capable of supporting all these different use-cases.

Here's my thinking: Let's say we have two robots, R1 and R2, where R1 has MultiDOF joints and R2 does not. Both of them offer the FollowJointTrajectory action.
Right now, R1 has no way to follow a trajectory that includes its MultiDOF joints. Extending the action definition like in this PR enables that capability. R2 does not need to change their implementation at all, because they can safely ignore the multi_dof field. Both robots can still use all nodes that employ the FollowJointTrajectory action.
In the other case where we create a new action that includes the union (both MultiDOF and Regular Trajectory) (call it FollowAllJointTrajectory.action), R1 needs to implement an additional action server, which looks a lot like the existing FollowJointTrajectory action server. But then all the other nodes that use FollowJointTrajectory may also need to be expanded to call either FollowJointTrajectory or FollowAllJointTrajectory in order to work with all the joints of R1. Furthermore, if a tool comes along that only uses FollowAllJointTrajectory then R2 will have to write an additional action server as well in order to use that functionality.

Or perhaps in other words: does this semantically make sense? Are there any other future extensions expected?

trajectory_msgs has been functionally unchanged since 2013 and its description states that they function as the building blocks for most of control_msgs. As indicated by #16, this sort of functionality has been desired since at least 2015.

Should there be a separate .action for this, similar to how FZI created one for Cartesian use-cases?
I'm not sure what you're referring to here with FZI.

The FZI reference is to this, I think:
https://discourse.ros.org/t/developing-a-cartesian-manipulator-interface/13872
The takeaway is, they made a new action server for Cartesian motions instead of modifying the existing one.

multi_dof_path_tolerance et al is a hazy name IMO. Can we come up with anything better than this to better describe it? We can't change the message type name but the local member name should be improved.

I made the message type name, so I went ahead and renamed it. Since the only difference between it and JointTolerance.msg is the component field, I renamed it JointComponentTolerance.msg

@AndyZe thanks for that reference.
The way I see it is that this would allow us to extend the FollowJointTrajectory action with non-revolute/prismatic/linear joints. The goal is not to make a shapeshifter follow trajectory action but to extend the current setup to support whole body trajectories where even in the case of bipeds where a pure joint trajectory could exist (however unrealistic), but the lower body is abstracted as a floating joint for practical reasons, similarly to mobile bases. This would play nicely with controller chaining once we have it in ros2_control.

Thanks!

(and thanks for the Galactic release)


Create posts from meetup events

See: #109
Creates a new markdown file in _posts/ for each meetup.com event. Templates have been updated to support it.
ToDo:

[x] Check for updates since last build (24hr)

/cc @spikeheap @benfoxall

I like this approach

Thanks @benfoxall I'll take a stab at the changes later today. I'm planning to pull it out into its own Grunt plugin to make it more manageable.

Hi @AverageMarcus, looks like a merge conflict with your last PR. Like it though. Once it's mergeable let's do it.

@spikeheap hold off on this. I'm gonna soon open a PR that'll cover this and more.

This is now covered by #131


ci: add core Apache Cloudberry (incubating) build and test workflow

Introduces foundational GitHub Actions workflow for Apache Cloudberry (incubating) CI:

Multi-stage build pipeline with skip detection
Rocky Linux 9 containerized build environment
RPM packaging and source tarball generation
Installation verification
Test matrix for core regression tests (subset starting point)
Detailed test result parsing and reporting
Comprehensive artifact management

The workflow provides:

Clean build environment for each run
Consistent test execution framework
Automated installation testing
Test result aggregation
Clear job dependencies and progression
Flexible CI skip mechanisms

Due to inconsistent test runs, disable the following from greenplum_schedule:

cbdb_parallel
instr_in_shmem_verify

This commit establishes the initial CI pipeline for Apache Cloudberry (incubating) with future test matrix expansion planned.

To merge this PR, we'd better email<EMAIL_ADDRESS>to request the Infra team bypass the old checks.

Amazing work...learned something, thanks

Really efficient work here! You’ve solved the problem with the least amount of code needed.


feat: docker improvements

Features:

Includes CUDA 12.1 and cuDNN 8.9.7 & CUDA/cuDNN installation process. Solved: #215 and #225
Optimized Docker layer caching for faster builds
Added ability to download only necessary checkpoints. Solved: time and space
Switched base image to python:3.10-slim

This setup has been thoroughly tested to ensure stability and performance.
Preconditions:
Join the NVIDIA Developer Program:

Go to the NVIDIA Developer Program.
Sign up for an account if you don't already have one.
Once you have an account, log in to the NVIDIA Developer website.

Download cuDNN:

Navigate to the cuDNN Archive.
Select the version you need (cuDNN 8.9.7 for CUDA 12.1).
Download the appropriate file for Linux (should look like cudnn-linux-x86_64-<IP_ADDRESS>_cuda12-archive.tar.xz)
Place file in the root of the directory.

Run:
docker build -t openvoice .
then
docker run --gpus all -p 8888:8888 openvoice v2
tl;dr
Hey everyone,
I've been working on improving the Docker setup for OpenVoice, and I think these changes will make it much easier to run in a containerized environment.
The main issue I've seen is with CUDA and cuDNN versions not matching up, causing errors. In this Dockerfile, I've included CUDA 12.1 and cuDNN 8.9.7, which work well with the latest PyTorch that supports CUDA 12. This should help eliminate those errors.
Another improvement is the entrypoint shell script. Additionally, you can now download only the checkpoints you need: it will only download the checkpoints for the specified version, saving time and bandwidth.
I've also optimized the Docker layer cache. I rearranged some commands so that if only the local files change, Docker can reuse the base layers that have all the lengthy installations. This should speed up your builds when you're making changes to your local setup.
In summary, smoother, faster, and less prone to errors. It's now easier to spin up different versions and notebooks without CUDA issues or long installations.
This setup has been thoroughly tested to ensure stability and performance.
Give it a try and let me know how it goes! I'm always happy to hear feedback and suggestions. I think this will be a big improvement for the OpenVoice experience.
Happy Dockerizing! 🐳
Vlad
Screenshots:
Running:

Results:

If you want to implement a similar setup on windows, follow:

https://github.com/myshell-ai/OpenVoice/issues/215#issuecomment-2153388034
https://github.com/myshell-ai/OpenVoice/issues/215#issuecomment-2153417117

@wl-zhao, @yuxumin, @Zengyi-Qin, may you take a look, please. I wasn't able to assign a reviewer, this option seems to be disabled in this repo. Thank you!

@oldmanjk Thank you for reviewing the pull and bringing this up, but kernel died can have various causes, this error message can be displayed in everything from lack of memory to missing libs etc.
First issue you are having
The folders should not exist or be populated prior to the checkpoint extraction, this is a docker container. Based on your logs, it seems the first issue you are facing is related to moving the extracted checkpoint files: the directories /workspace/checkpoints_v2/base_speakers and /workspace/checkpoints_v2/converter are not empty, preventing the extracted files from being moved.
In my testing environment, I've built the image from scratch, and it works without any issues. The folders should not exist or be populated prior to the extraction process.
Idk what your build context is, but these are some things that I can think of:

Are you using any persistent volumes or bind mounts when running the container? If so, could you try running the container without those mounts to see if the issue persists? If you have previously run the container with persistent volumes or bind mounts attached to those specific directories, the folders might persist even after the container is removed, causing conflicts when building the image again; or if you didn't clean up the previous container instances or the volumes, files might still be still left there. Could you please ensure that any previous container instances and associated volumes are properly cleaned up before building the image again?
Are there any additional files or directories in your build context that might be causing the folders to be populated?

Second issue
For the second one. Looks like LSP tries to autodetect and start lang servers and it looks for the nodejs executable path. I have the container running right now, here:

It looks like the only mention of jupyterlab-lsp, that requires node is your comment in this pull, so I assume that this is related to your particular setup.

@oldmanjk, could you please check if you have any user-specific jupyter configurations, additional jupyter extensions, or dev environment settings that might be enabling or interacting with the LSP extension? If so, try disabling or removing them and rebuilding the container to see if the errors persist
If the issue still persists after considering these, I'd be happy to work with you to investigate further and find a solution. We can explore additional steps.

@vladlearns I have been working in parallels on a fix for the Dockerfile that will suit the CPU setup, particularly for Mac series M and similar systems. I have finally chanced upon a solution. Considering your work on this matter, perhaps we can combine our efforts. We could develop specialized Dockerfiles; one for CUDA and another for CPU. Correspondingly, we could generate docker-compose files (docker-compose.cuda.yml and docker-compose.cpu.yml). What do you think?
My work : https://github.com/npjonath/OpenVoice/pull/1
note: this PR also include the fix from @Afnanksalal, as this is a requirement to run this project on CPU based architecture. (https://github.com/myshell-ai/OpenVoice/pull/262)
The Openvoice V1 work correctly on my setup. The V2 is still not working because of this issue from MeloTTS
Issue: https://github.com/myshell-ai/MeloTTS/issues/167
And a possible solution for this by running a specific version of MeloTTS : https://github.com/Meiye-lj/Dockerfiles/blob/76c88309a4bb7b7070441bed3b4b72231f5349b8/MeloTTS/Dockerfile

@oldgithubman You added yourself by approving the PR and then dismissing the review because of your environment. Later, you decided to leave without providing any details. Now, when I ask for a review, you are automatically added, and there is no way to remove you.

@vladlearns No it was just for talking about this with you. You can leave the naming as it. I guess GPU usage is the default one.  I will add docker-compose file and Dockerfile.cpu separately to extends your implementation.

@npjonath Sure. So far, I've tested my setup on multiple environments. It works for multiple people as well, but it seems they don't merge pull requests into the main branch. Instead, they ask contributors to fork the repository and point to the fork in the documentation

@npjonath if you can help me out, how does your fork installation actually install openvoice?  Looking at the docker file I don't see where it downloads the git repository?  Maybe I'm missing a step in how to get this working on mac?


Extract common utils for assembling key value pairs with config option prefix in processbuilder

:mag: Description
Issue References 🔗

As described.
Describe Your Solution 🔧

Avoid using magic string value "--conf" in each processbuilder
Extract common utils for assembling key value pairs with config option prefix in processbuilder
NO changes in expected string value for processbuilder command assertions in test suites

Types of changes :bookmark:

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Test Plan 🧪
Behavior Without This Pull Request :coffin:
No behavior changes.
Behavior With This Pull Request :tada:
No behavior changes.
Related Unit Tests
Added CommandUtilsSuite.

Checklists
📝 Author Self Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[x] This patch was not authored or co-authored using Generative Tooling

📝 Committer Pre-Merge Checklist

[ ] Pull request title is okay.
[ ] No license issues.
[ ] Milestone correctly set?
[ ] Test coverage is ok
[ ] Assignees are selected.
[ ] Minimum number of approvals
[ ] No changes are requested

Be nice. Be informative.

Codecov Report
Attention: 5 lines in your changes are missing coverage. Please review.

Comparison is base (ba5cb24) 61.35% compared to head (299baa7) 61.33%.
Report is 4 commits behind head on master.

Files
Patch %
Lines

...ommon/src/main/scala/org/apache/kyuubi/Utils.scala
33.33%
0 Missing and 2 partials :warning:

...apache/kyuubi/engine/chat/ChatProcessBuilder.scala
0.00%
2 Missing :warning:

.../org/apache/kyuubi/util/command/CommandUtils.scala
85.71%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #5767      +/-   ##
============================================
- Coverage     61.35%   61.33%   -0.03%
  Complexity       23       23
============================================
  Files           607      608       +1
  Lines         35914    35912       -2
  Branches       4926     4931       +5
============================================
- Hits          22036    22026      -10
- Misses        11490    11497       +7
- Partials       2388     2389       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Would you like to double-check this PR? Some changes after your last review. @pan3793

overall LGTM, feel free to merge after addressing minor comments and passing CI.
Have good weekend~

Thanks, merged to master and branch-1.8 (1.8.1)


when i have the orb for zapdos it says i need 100 more kayos that i kill another pokemon it says i need 101 kayo isnt it suppose to go down?

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Username:
Server name (all applicable):
Logs:
Where needed, please find your logs with the method down below. Make sure to include the file, or better yet, use a site like https://pastebin.com/ to add it to the ticket without copy pasting all the contents of the file.
For the Minecraft Launcher : C:\Users\USER\AppData\Roaming.minecraft\logs
For the Technic Launcher: C:\Users\USER\AppData\Roaming.technic\modpacks\pixelmon-reforged\logs
For the ATLauncher: C:\Users\USER\AppData\Roaming\ATLauncher\Instances\PixelmonCraft\logs
For the Twitch Launcher: C:\Users\USER\Documents\Curse\Minecraft\Instances\PACK\logs
Additional context
Add any other context about the problem here.

Hello! Sorry for not getting to this sooner but there is now a ticket for it https://pixelmonmod.com/tracker.php?p=2&t=19186 and will be fixed in the future.


option to provide custom serviceAccount

Useful on Openshift if you need securityContextConstraint set on serviceAccount (Openshift does not allow containers running as root, so all required capabilities need to be set in securityContextConstraint).

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


webframe: api to register scheme as privileged

Fixes #2831

Although this fixes the security error for registering service workers, with current version chromium there are hard coded checks for scheme is http/https to handle service worker  requests, hence they wont work. But this has been fixed in this CL which gives embedders's a chance to register schemes that can handle service workers, we need to wait for that.

Thanks!

Thank you. Do we know when the missing Chrome issue will be available to be included in Electron?

@rogeru that particular CLs' parent issue is set for M46 release, not sure when. You could open an issue for tracking, will be implemented once the api becomes available.

Thanks @deepak1556.
I am using registerUrlSchemeAsPrivileged which gets me passed the previous error about file:// not being allowed. The next error is "SecurityError: Failed to register a ServiceWorker: No URL is associated with the caller's document."
It seems we also need to wait for https://code.google.com/p/chromium/issues/detail?id=522900.

Yes thats because of the checks i was talking about which only does SchemeIsHTTPorHTTPS everywhere now. Once the upgrade its replaced by generic OriginCanAccessServiceWorkers check everywhere. This maintains a map of schemes allowed which is obtained from ContentClient::AddServiceWorkerSchemes

@deepak1556 is this fix already in the release? Can I already use it?

@havenchyk nope need to wait for chromium upgrade, can be tracked here https://github.com/atom/electron/issues/3312#issuecomment-153632338

@deepak1556 how about now? I guess there was an update to Chrome 47?

@havenchyk yup need to wait on the PR.


Header component/issue #21

Reviewers
Changes

adding props to Header component

Definition of Done (from ticket)
Unstyled component hierarchy added to support the necessary configurability.
UI components (with different states) added to Storybook.
QA steps (optional)
Known Issues

Trying a new approach to avoid conflicts. I've forced push every change into a single commit.


Missing error event (unknown location)

Running the app for a while and connection is lost to server, it crashes:
events.js:160
      throw er; // Unhandled 'error' event
      ^

Error: socket hang up
    at TLSSocket.onHangUp (_tls_wrap.js:1087:19)
    at TLSSocket.g (events.js:286:16)
    at emitNone (events.js:91:20)
    at TLSSocket.emit (events.js:185:7)
    at endReadableNT (_stream_readable.js:926:12)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickDomainCallback (internal/process/next_tick.js:122:9)

It prob is a lib used outside this lib. But checked Google Auth and it does seem to handle the error. So it would be the request lib.. huh..
Anyone running into this/more info would be highly appreciated.

Not ran into this for a while. Closing it for now.


AttributeError: module 'albumentations.augmentations.functional' has no attribute 'resize'

I've met this problem when trying to train the model.
AttributeError: module 'albumentations.augmentations.functional' has no attribute 'resize'
my albumentations's version is 1.2.1

I‘ve actually check the functional.py in albumentations, there is no resize function....T.T
what can I do to solce this ?
QAQ

just import albumentations as F


The interface disorder

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

VS Code Version:1.69.0
OS Version:MacOS M1

Steps to Reproduce:

I found that in vscode's navigation bar, if the content is outside the scope of the presentation and arrow keys are used, the following image appears.

@donald-ning can you please describe what you would expect to see.

I think the navigation at the bottom is out of place, isn't that a bad design? I want to be able to scroll, not clutter

Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from: https://code.visualstudio.com/insiders/

For the preview version, I use the same method and it will still look like this.

I am curious what contents are there for you in the status bar, because I will probably have a hard time to reproduce. Can you follow these steps in the video and paste the contents here?

I'm sorry, I'm just a beginner, I don't know the specific code content. I can only give you my specific operation in this case.
https://user-images.githubusercontent.com/54016368/179222858-b9cddbe5-bb67-4fba-8967-4de2e62f93e4.mov

Yeah I can reproduce but I do not have a good idea how to solve this. https://github.com/microsoft/vscode/issues/84258 is related to use a different strategy and clip the entry instead of hiding it.
In general we miss a good overflow strategy for the status bar (related https://github.com/Microsoft/vscode/issues/6651).
Is there someone with energy to investigate a solution? Maybe in CSS?

Hi, what if the status bar becomes scrollable when it overflows, but no scrollbar is displayed? We can then scroll horizontally using the mouse wheel or using the left/right arrow keys.
Will this be a good enough solution? I can try to implement this with minimal changes.
https://user-images.githubusercontent.com/17908447/179563348-0d315dee-59d0-45cc-bce2-7d2ae252091a.mp4

Yeah if we can somehow do this only when keyboard focus is in I am willing to take any solution that does not result in the multi line layout shift 👍
Thanks!


Where is the rangenet?

Hello,
Thanks for sharing the code of DarkNet and SqueeezeNet, but I could not fount the architecture of RangeNet. Will you consider publishing it?

well... it seems that the published darknet is the rangenet? seems a little confusing..


userdata column conflict generates a weird empty column

with usedata setting:
            "userData": {
                "tag": "development",
                "price": "$10"
            },

and response
{
	"items": [
		{
			"order_id": 98765432,
			"price": "$42"
		},
		{
			"order_id": 23456765,
			"price": "$24"
		}
	]
}

the following CSV is produced
"order_id","price","tag","78a5eb43deef9a7b5b9ce157b9d52ac4"
"98765432","$10","development",""
"23456765","$10","development",""

runnable in 076-user-data

fixed in df242bed508095332cfe3a6680cc2ee4b316d86d


(GH-2400) Add bundled-ruby option for local transport

This introduces the bundled-ruby config option for the local
transport. The option enables merging default config values currently
used just for a target with name localhost. Those default config
values are:
config:
  local:
    interpreters:
      '.rb' => RbConfig.ruby # This is Bolt's bundled Ruby
features:
  - puppet-agent

The default config values are merged at the target config level, meaning
they are overridden by target-level config but not group-level config.
The 'features' array is appended, not overridden, and is a set so the
value will not be added twice.  The localhost target additionally
defaults to using the local transport as part of the "magic config",
however the bundled-ruby option will only apply to targets that are
already configured to use the local transport.
bundled-ruby currently defaults to false, but will default to true
in Bolt 3.0. A warning is issued for users who don't set the
conifguration and use the local transport that the default config will
be updated.
Closes #2400
!feature

bundled-ruby local transport config option enables local defaults ((#2400)[https://github.com/puppetlabs/bolt/issues/2400)
Set bundled-ruby in the local transport config to enable or disable
the default config currently used for the 'localhost' target.

One fun edge case with this is that localhost default config cannot be unset by the bundled-ruby config option - it still needs to be overridden at the target config level. That should change in Bolt 3.0, but until then it's the exception to the bundled-ruby option.


ASA-4980

Critical issue count could be visible in build summary

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Closing this PR, as some internal discussion is going on whether we want these changes for ASE or not.


Contextual Assistance

Many users want better contextual support, similar to what’s offered by tools like Claude. Adding this would significantly improve workflow efficiency.

Can you please share some examples of what you mean by contextual support


No parser support for Python 2.7, need to figure out if the user file is Py2 or Py3

Fixed by removing parsing features, so should work with all languages now.

Fixed by removing parsing features, so should work with all languages now.


Fix "" escaping

Coverage increased (+0.08%) to 82.895% when pulling 9a080980c530fef5d3c5aa756f0feb2b9b3c97dd on josh-reproduce-escape-error into 93b443550b8663c9c5dbb072ddb0a331dfc2ccca on master.

Coverage increased (+0.08%) to 82.895% when pulling adc3063f8065f53d1efe9430234d2a4c0a6f1a7f on josh-reproduce-escape-error into 93b443550b8663c9c5dbb072ddb0a331dfc2ccca on master.

:+1: :sparkles: :sparkles: :sparkles: :sparkles:

Coverage increased (+0.08%) to 82.895% when pulling 5ca24a8cbc2be259efb50d76933a1d13f414a36b on josh-reproduce-escape-error into 93b443550b8663c9c5dbb072ddb0a331dfc2ccca on master.

Coverage increased (+0.08%) to 82.895% when pulling c0d8fe3c51e90e584fd9dafe0a4c87879d4a758f on josh-reproduce-escape-error into 16baad931107cc913e8aae932053e26d2d4266c0 on master.


Add mechanism to process modules non concurrently

This PR adds a mechanism to mark rules that cannot be processed in parallel. In the configuration we can define single threaded rules like so:
[loading]
single_threaded_rules = ["testing_test.wasm"]

When one of these rules is seen in the execution loop, we check a list of "in flight" rules to see if it's already being processed. If it is, the message is sent back into the log queue for processing. If it's not, we add the rule name to the list of in flight rules and continue with execution. When execution is finished, we remove the rule from the in flight list.

PR description is outdated


Add long_running test flag and feature to exclude tests.

There are certain tests which necessarily take a very long time
as they tax CPU resources. It is not appropriate for these tests
to run on public CI as it they contribute significantly to testing
times and sometimes cause timeouts on CI infrastructure. This
patch adds the test tag @tag('long_test') and the option
--exclude-tags to the test suite runner. Using these in
combination along with marking known long tests should speed up
test times in CI.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@57d4ba0). Click here to learn what that means.
The diff coverage is 61.53%.

@@            Coverage Diff            @@
##             master    #3544   +/-   ##
=========================================
  Coverage          ?   51.54%
=========================================
  Files             ?      393
  Lines             ?    80228
  Branches          ?     9135
=========================================
  Hits              ?    41354
  Misses            ?    37503
  Partials          ?     1371

Looks good!


TGP-641 add Request Accreditation endpoint

New Request Accreditation endpoint
Added operationId to Remove TGP record endpoint
Included regex patterns for eori, actorId and countryOfOrigin fields
Added enums to category and declarable fields
Updated descriptions

Yes, just waiting on some content
From: Ben Healy @.>
Date: Friday, 3 May 2024 at 14:58
To: hmrc/trader-goods-profiles @.>
Cc: Jagtar Singh @.>, Author @.>
Subject: Re: [hmrc/trader-goods-profiles] TGP-641 add Request Accreditation endpoint (PR #35)
@taylors-version commented on this pull request.
I see there's a couple of TODOs, are you going to implement them before merging?
—
Reply to this email directly, view it on GitHubhttps://github.com/hmrc/trader-goods-profiles/pull/35#pullrequestreview-2038211028, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BHEPDK5MO6BQHNEI2J6GRDTZAOJZ3AVCNFSM6AAAAABHFR4V3GVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDAMZYGIYTCMBSHA.
You are receiving this because you authored the thread.Message ID: @.***>
[Opencast Software]https://Opencastsoftware.com/
[twitter]https://twitter.com/TeamOpencast             [instagram] https://www.instagram.com/teamopencast/           [linkedin] https://www.linkedin.com/company/opencastsoftware/
Jagtar Singh
Software Development - Consultant
<EMAIL_ADDRESS>London|Newcastle|Edinburgh|Glasgow|Leeds
Join our team.
See live roles here.https://opencastsoftware.com/careers/vacancies/all-vacancies/?utm_source=E-sig&utm_medium=email&utm_campaign=Recruitment_acquisition_organic_web_link&utm_term=&utm_content=
We build trust. We enable people. We work together. We do the right thing. We make a difference.
This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.E-mails are not encrypted and cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses.The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission.If verification is required please request a hard-copy version.


Update aws-core, http-client-spi, ... to 2.17.159

Updates

software.amazon.awssdk:aws-core
software.amazon.awssdk:http-client-spi
software.amazon.awssdk:netty-nio-client

from 2.17.158 to 2.17.159.
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 = "software.amazon.awssdk" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #772.


Add phosphor icons script to head

Description
Added the Phosphor Icons script to the html head by using preview-head.html
Usage
// class name is the name of the icon

// style can be adjusted in the same way as a font

// styling shortcuts can be used by assigning other classes

Screenshots

LGTM


Difference between Direktiv and Argo Workflows/Events

Hi
How do these two differ? Is there any significant benefit that Diretkiv offers than its 'Argo Workflow.Events' counterpart?
PS: I do not know where to post this question. So I am asking here, this is not an ideal place probably.

We have a slack channel to ask questions but git issues is fine too. Tbh I haven't had a look at Argo events to tell you the difference between our event handling and Argos. The Direktiv design is bound to Knative eventing and Direktiv acts as source and sink for Knative eventing which means it can publish events back to Knative and consume events from Knative as well. Within the engine we are using events as well so a flow can publish messages internally and subflows can consume them.
When it comes to workflows there are differences but at the end every workflow engine has the same concept of states/tasks and it walks through them, loops, foreach, parallels etc. I think the main difference is the use of Kubernetes. Direktiv is trying to "hide" Kubernetes. Users don't have to know and understand Kubernetes. We don't have CRDs and kubectl is not necessary. That is probably the main difference between the two if you compare Argo with our open source version. In theory we could run on Hashicorp Nomad if we write a new interface for functions which are using Knative at the moment.
If there are any specific questions please let me know.

Hi @jensg-st
I have understood you, thanks.
There is another question which is not specific to Direktiv, it is about using serverless in Kubernetes. Given the fact that Kubernetes supports HPA scaling, what is the major benefit of introducing Knative Serverless scaling in Kubernetes, I googled but didn't get a  satisfactory answer.
Taken from Knative Serving It provides automatic scaling for applications to match incoming demand... This is provided by default, by using the Knative Pod Autoscaler (KPA). For example, if an application is receiving no traffic and scale to zero is enabled, Knative Serving scales the application down to zero replicas.
OpenShift and Alibaba say that you can reduce application deployment costs by using Knative but how? But the most popular publich cloud is AWS. The serverless application code is finally run in an EC2 instance.
Does EC2's auto scaling feature has anything to do with K8S's HPA (and/or Knative Serving)? When we configure an EC2 instance, we buy a fixed amount of Memory and CPU for which we have to pay no matter how often we use.
Now if our K8S application (with Knative Serving enabled) is using the EC2 instances under the hood, and assume we do not access the application even once in a month. So we won't be charged anything Or do we need to pay a minimum fee which corresponds to the amount of cpu/memory configured for the EC2 instances with autoscaling enabled Or some other amount?
Also, serverless has cold start issues too.
If you can throw some light on this, it'd be great. Thank you.

Hi @jensg-st
I have understood you, thanks.
There is another question which is not specific to Direktiv, it is about adding the serverless support in Kubernetes. Given the fact that Kubernetes supports HPA scaling, what is the major benefit of introducing Knative Serverless scaling in Kubernetes, I googled but didn't get a  satisfactory answer.
Taken from Knative Serving It provides automatic scaling for applications to match incoming demand... This is provided by default, by using the Knative Pod Autoscaler (KPA). For example, if an application is receiving no traffic and scale to zero is enabled, Knative Serving scales the application down to zero replicas.
When we configure an EC2 instance, we buy a fixed amount of Memory and CPU for which we have to pay no matter how often we use.
Now if our K8S application (with Knative Serving enabled) is executing the serverless code inside the EC2 instances under the hood, and assume we do not access the application even once in a month for the worker nodes. So we won't be charged anything Or do we need to pay a minimum fee which corresponds to the amount of cpu/memory configured for the EC2 instances with autoscaling enabled Or some other amount?
OpenShift and Alibaba say that you can reduce application deployment costs by using Knative. But I have not come across any such claim made by AWS.
Also, serverless has cold start issues but Kubernetes containers are always warm (always running). While Kubernetes containers have no runtime-based time constraints, serverless functions are set to run for a short duration. Kubernetes favour stateful apps, on the hand serverless functions are stateless. So what made the community to add Knative to Kubernetes, I wonder.
If you can throw some light on this, it'd be great. Thank you.

Hi @jensg-st
I have understood you, thanks. There is another question which is not specific to Direktiv, it is about adding the serverless support in Kubernetes.
Taken from Knative Serving It provides automatic scaling for applications to match incoming demand... This is provided by default, by using the Knative Pod Autoscaler (KPA). For example, if an application is receiving no traffic and scale to zero is enabled, Knative Serving scales the application down to zero replicas.
Given the fact that Kubernetes supports HPA scaling, what is the major benefit of introducing Knative Serverless scaling in Kubernetes. They could have added this functionality to plain HPA itself, instead of adding more complexity to the already-complex Kubernetes.
I have little knowledge about Kubernetes, so this question of mine may sound dull. When we configure an EC2 instance, we buy a fixed amount of memory and cpu for which we have to pay no matter how often we use.
Now if our K8S application (with Knative Serving enabled) is executing the serverless code inside the EC2 instances under the hood, and assume we do not access the application even once in a month. So we won't be charged anything for the worker nodes Or do we need to pay a minimum fee which corresponds to the amount of cpu/memory configured for the EC2 instances with autoscaling enabled Or some other amount?
OpenShift and Alibaba say that you can reduce application deployment costs by using Knative on their cloud. But I have not come across any such claim made by AWS.
Also, serverless has cold start issues but Kubernetes (in theory at least) containers should always be warm (running). While Kubernetes containers have no runtime-based time constraints, serverless functions are intended to run for a short duration. Kubernetes favour stateful apps, on the other hand serverless functions are stateless.
So what made the community to add Knative to Kubernetes, I wonder.
If you can throw some light on this, it'd be great. Thank you.

Hi @jensg-st
I have understood you, thanks. There is another question which is not specific to Direktiv, it is about adding the serverless support to Kubernetes.
OpenShift and Alibaba say that you can reduce application deployment costs by using Knative (Knative Serving scales the application down to zero replicas) on their cloud. How can we reduce such costs on AWS and/or Azure?

Hi,
Is this a general question if there is money saving with Knative / Serverless or the Alibaba specific reserved instance approach with Knative?

There are multiple reasons why Knative is a good idea in my opinion. For me one of the main points using Knative is the ease of use if you are in a Kubernetes environment. It is just a almost perfect deployment solution. If you have HTTP based backends it just makes a lot of sense. Instead of having multiple yaml files with deployment, services etc. Knative does it in one simple deployment file. And it comes with additional stuff like revisions, traffic management. If you are unsure, give it a test run and I think Kubernetes deployments getting much easier. You can even avoid cold-starts and start with one pod up all the time.
Looking at the article which is very shallow I'm assuming it is about the Kubernetes CPU and memory request values. In particular memory. Let's say you have 10 pods with Memory requests of 100MB which means you "block" a GB all the time whereas it is lower in average if you use Knative. That depends on the traffic pattern of course but if you have constant traffic then scaling-to-zero does not add much value anyways. The idea is here (at least I think that is what they mean) that you can heavily oversubscribe CPU and in particular memory. For example we are using Knative services for our functions. You can have hundreds of functions which would eat up a lot of memory / CPU (in terms of Kubernetes request) but usually they are not needed at the same time. Therefore you can have 100s of Knative services on a three node cluster. If you add node auto-scaling to the mix I can see cost savings (although the cold-start times are probably insane then). For us it is extremely useful and because our stuff has mostly a workflow character not service orchestration. The cold-start times don't matter too much. It doesn't matter if you flow runs for one minute or one minute and 10 seconds. And for your apps the response times might not matter, e.g. 1 second vs 5 seconds.
The question was if you save money and resources? I personally think deployments with Knative are easier to manage which is potential time and money saving. This is for me a big win already. The cost savings in terms of resources really depends on your usage/request patterns I reckon. If you are ok with cold-starts for e.g internal apps and have these "spread-out" requests you can oversubscribe the cluster by a lot.

Hi
I knew that if we use Knative all we we need to specify is the container name in the function's manifest. The second paragraph really makes sense (something new I have learned) and  the usage patterns (for example amount of traffic we are receiving) can help us choose somewhat-precise amount of resources.
Yes, cold starts is a major issue, end users and stakeholders don't like them. To write serverless functions, I think we should use a language like Rust whose spin up time is a few milliseconds. Java developers should consider using GraalVM (instead of JVM). Its boot time, performance, memory consumption is awesome. Quarkus framework is based on it.
You might be aware of this Kubernetes auto-scaling component, it could add some value to Directkiv..
https://keda.sh/docs/2.9/scalers/
I think cloud native concept is really picking up, my guess is that we'd see deployments on bare metals.
Regards

Hi
we have had a look at keda because we thought we might use it for a more event driven approach for the functions but it was too error prone so we decided against it for now. We build a custom scaler but managing in the backend seemed painful for now and using the HTTP one doesn't add much value because Knative does the same.
Anyways, I hope this little discussion was helpful for you. It was for me. I'm closing it now and feel free to open a new one or use Slack. Up to you.


TW-1256: App crushes on 'Buy with crypto' screen

https://madfish.atlassian.net/jira/software/projects/TW/boards/4?selectedIssue=TW-1256
App was crushing with error: "Selected asset not found", cause of filteredCurrenciesList = []

App was crushing with error: "Selected asset not found", cause of filteredCurrenciesList = []

App was crushing with error: "Selected asset not found", cause of filteredCurrenciesList = []

Can you also, please, leave an explanation of the reason the app crashes. Is it over thrown errors?

App was crushing with error: "Selected asset not found", cause of filteredCurrenciesList = []


Update min-utxo-ada calculation for Babbage, Update Haskell server pparams parser

Pre-review checklist

[x] All code has been formatted using our config (make format for Purescript, nixpkgs-fmt for Nix)
[x] All Purescript imports are explicit, including constructors
[x] All existing examples have been run locally against a fully-synced testnet node
[ ] The integration and unit tests have been run (npm run test) locally
[ ] The changelog has been updated under the ## Unreleased header, using the appropriate sub-headings (### Added, ### Removed, ### Fixed)

I ran the integration tests against the vasil-dev network, and they passed except for the time ones. That should be fixed by #676


add rust

Hello,
Thank you very much for sharing this on YouTube. I really enjoyed both doing the exercise and writing weird hard to read rust code.
Please let me know if anything has to be fixed or could be improved.
Thanks

Thank you this is welcomed. I have some questions.

should the lock file be committed? In practice environments usually everybody has his/her own versions etc.
can the main file be called yatzi instead of category?
You use a lot of map/filter/iter constructs. This is already an improvement of the code. Is it possible to do plain loops with imperative code instead like most other code like the C or Java one?

Thanks for the review.

That's correct the package has no dependencies to be locked anyway.
Actually the main file would be lib.rs which includes category so the imports would look something like use yatzy::category::ones that reads nicely. But it is possible to have both.
That's fair. I don't want to only have bad imperative code, but I'll make them worse.

Thank you. Sorry that I am picky here: Usually the code of ports is as similar as possible, so all participants have the same experience regardless of which language they use and/or to support a workshop/coding dojo in a group which uses different languages at the same time. For example your chance is
    let mut t = 0;
    t = t+ r[0];
    t= t + r[1];
    t +=r[2]+r[3];

    return t + r[4]

but the Java or JavaScript is
   var total = 0;
    total += d1;
    total += d2;
    total += d3;
    total += d4;
    total += d5;
    return total;

While these are equivalent, the second one uses named parameters instead of an array and increments total once in each line. Also the total is total and not t. While some things are not possible in some languages, could you follow the code as much as possible in names, structures and so on. E.g. there is no use of iter/foreach/map in the original code, that was the reason I mentioned it in the previous comment. I was not clear. It is not as much as to make the code worse, but to make it consistent with other languages.
When I do this I compare the source of my port - usually my strongest language - and compare it line by line with my port. This helps me flush out the last inconsistencies. Even comments and (rarely) bad formatting could be ported and preserved. Please have a try

I just didn't know they had to be similar. I'll fix it.

I copied the Java code and tried to make as little changes as possible only to get it compile on rust

Thank you, excellent work. Sorry for the confusion and thank you for your patience. This can be merged,
@emilybache please merge.

Thankyou both for your work on this. I appreciate it.

I'm learning a lot so I'd be glad if I could give something back 🙏🏻🙏🏻


Ensure IAPP and InvasivesBC records are showing on the public facing map again

Bring back the iapp and invasivesBC records on the public facing map before you log in.
Bring back the iapp and invasivesBC records on the public facing map before you log in.
Techy todos:
-[ ]
How activities page/activity page + map works

user logs in / stays logged out
auth request complete
app fetches geojson for both activities and points of interest / iapp stuff --- works up to here logged out
map init action
grabs all the filters for each record set from local storage
puts filters into state (usersettings.recordsets)
loop over each recordset, and fetch the IDS ONLY for that recordset
activities endpoint (id only flag)
points of interest endpoint (site_id only flag)

recordsetlayersrenderers - just filter the 2 big feauturecollections by recordset IDLists - no new server fetches

user clicks on recordset - iapp tablerows get || activity tablerows get - these will get full rows for display
these actions call the same endpoint,
but without the id only flag, and use the same filters, but pass paging variables, ans sorting keys

what needs to change for public:

[ ] check role / logged in before calling admin shape endpoint
[ ] hide the boundary thing for now - nice to have when other stuff done - put it back, but dont upload or pull from server
[ ] activities and points of interest endpoints:
need to work while logged out BUT:
- [ ] can't return person name && can't filter by any name
- [ ] dont worry about hiding columns - just dont pull them from server
[ ] activiy page - can disable the activity page saga while logged out
[ ] other misc ui stuff:

[ ] hide the new record button
[ ] double check tabs make sense for public

This issue is more of an 'epic' - The team shifted to working on getting the new layer format to work before doing this to avoid extra rework.  Doing smaller increments/tickets to get there, will keep this ticket around for info but not drag through sprint point tracking as its too broad.


v1.14 Backports 2024-08-19

[x] #33698 (@youngnick) :warning: resolved conflicts
[ ] #34137 (@youngnick) :warning: resolved conflicts
[ ] #34372 (@Artyop)
[x] #34400 (@mhofstetter)

Once this PR is merged, a GitHub action will update the labels of these PRs:
 33698 34137 34372 34400

/test-backport-1.14

I approved because #33698 is all good, but #34137 has had some content lost along the way.

/test-backport-1.14

I approved because #33698 is all good, but #34137 has had some content lost along the way.

@youngnick I've pushed the fix. Could you please take a look one more time? Thank you!


Icons for Rich Text Editor

Icon Request
Icon name:

Number list
Bullet list
Indent less
Indel more
Strikethrough
Remove formatting

Use case
Develop custom rich text editor
Screenshots of similar icons
Gmail compose box
http://prntscr.com/nie8qg

In fact, we've already got some editor icons that you needed except Strikethrough.
You can just find them in the Editor category on https://remixicon.com.
You did not find them before maybe because of our search keywords is not very strong.
Such as you want number list, but the keywords of our icon are list and list ordered.
That's why we opened the tags.json file so that people can help us to improve the search feature and that's why we hope user can offer keywords rather than icon names only when the requesting icons.
I'll add the keywords you offered above to the existed icons.
You may not find the Remove formatting icon in the Editor category, but you can find the eraser icons in the design category and they are what you can use for your scenario.
At last, thank you for your requests. We'll add Strikethrough icons and maybe other editor icons in the next version.

Now you can find Strikethrough icons from our website remixicon.com


System.NotSupportedException

I'm struggling to get scripts to work on macOS.
I'm on macOS Monterey, version 12.0.1. Following the tutorial I add:
#r "nuget: TorchSharp-cpu"
at the top of my script, but when I try:
let t = torch.ones(3,4)
I get the following error:
This application uses TorchSharp but doesn't contain reference to either libtorch-cuda-11.3-osx-x64 or libtorch-cpu, <IP_ADDRESS>.
The native dlls and dylibs are located where the error message says it's is looking for them, but they won't load. I wonder if this is some funny macOS permissions error??? Can you help me understand where I've gone wrong?
I've tried NativeLibraryLoad using my PyTorch instance of libtorch and to point it to the .nuget package libtorch, but to no avail. The full error is as follows (not sure where Step 2 is):
This application uses TorchSharp but doesn't contain reference to either libtorch-cuda-11.3-osx-x64 or libtorch-cpu, <IP_ADDRESS>. Consider either referencing one of these packages or call System.Runtime.InteropServices.NativeLibrary.Load(path-to-libLibTorchSharp.dylib) explicitly for a Python install or a download of libtorch.so/torch.dll. See https://github.com/dotnet/TorchSharp/issues/169.". Trace from LoadNativeBackend:
TorchSharp: LoadNativeBackend: Initialising native backend, useCudaBackend = False
Step 1 - First try regular load of native libtorch binaries.
Trying to load native component torch_cpu relative to /Users/axolotl/.nuget/packages/torchsharp/0.95.4/lib/netcoreapp3.1/TorchSharp.dll
Trying to load native component LibTorchSharp relative to /Users/axolotl/.nuget/packages/torchsharp/0.95.4/lib/netcoreapp3.1/TorchSharp.dll
Failed to load native component LibTorchSharp relative to /Users/axolotl/.nuget/packages/torchsharp/0.95.4/lib/netcoreapp3.1/TorchSharp.dll
Result from regular native load of LibTorchSharp is False

Step 3 - Alternative load from consolidated directory of native binaries from nuget packages
torchsharpLoc = /Users/axolotl/.nuget/packages/torchsharp/0.95.4/lib/netcoreapp3.1
packagesDir = /Users/axolotl/.nuget/packages
torchsharpHome = /Users/axolotl/.nuget/packages/torchsharp/0.95.4
Trying dynamic load for .NET/F# Interactive by consolidating native libtorch-cpu-* binaries to /Users/axolotl/.nuget/packages/torchsharp/0.95.4/lib/netcoreapp3.1/cpu...
Consolidating native binaries, packagesDir=/Users/axolotl/.nuget/packages, packagePattern=libtorch-cpu, packageVersion=<IP_ADDRESS> to target=/Users/axolotl/.nuget/packages/torchsharp/0.95.4/lib/netcoreapp3.1/cpu...
CopyNativeComponentsIntoSingleDirectory: natives=/Users/axolotl/.nuget/packages/libtorch-cpu/<IP_ADDRESS>/runtimes/osx-x64/native
Consolidating native binaries, packagesDir=/Users/axolotl/.nuget/packages, packagePattern=torchsharp, packageVersion=0.95.4 to target=/Users/axolotl/.nuget/packages/torchsharp/0.95.4/lib/netcoreapp3.1/cpu...
CopyNativeComponentsIntoSingleDirectory: natives=/Users/axolotl/.nuget/packages/torchsharp/0.95.4/runtimes/osx-x64/native
Trying to load native component /Users/axolotl/.nuget/packages/torchsharp/0.95.4/lib/netcoreapp3.1/cpu/libLibTorchSharp.dylib
Failed to load native component /Users/axolotl/.nuget/packages/torchsharp/0.95.4/lib/netcoreapp3.1/cpu/libLibTorchSharp.dylib

at TorchSharp.torch.LoadNativeBackend(Boolean useCudaBackend, StringBuilder& trace)
at TorchSharp.torch.InitializeDeviceType(DeviceType deviceType)
at TorchSharp.torch.InitializeDevice(Device device)
at TorchSharp.torch.ones(Int64[] size, Nullable1 dtype, Device device, Boolean requiresGrad)    at TorchSharp.torch.ones(Int32 rows, Int32 columns, Nullable1 dtype, Device device, Boolean requiresGrad)
at <StartupCode$FSI_0002>.$FSI_0002.main@()
Stopped due to error

now setting the following at the top of the script it fails silently
System.Runtime.InteropServices.NativeLibrary.Load("/Users/axolotl/miniconda3/envs/pt/lib/python3.8/site-packages/torch/lib/libtorch.dylib")

OK - I managed to get a workaround by updating libtorch to 1.10.1 via homebrew ... so there is some issue with the nuget package for TorchSharp-cpu on osx that isn't loading the torch libraries properly, I'll close this for anybody else that might come up against the same issue.


Exception occured: object TypeError:  is not a function

Hello :)
When I was dealing with one of the JScript malwares, I got the following error:
- Exception occured: object TypeError: AB$D[((("e" + "nvironmen") + (intermediate value)(intermediate value)(intermediate value)) + "")] is not a function     at eval (eval at <anonymous> (C:\Users\Sandbox\Desktop\original.js:3:29), <anonymous>:2:802)     at Object.eval [as toString] (eval at <anonymous> (C:\Users\Sandbox\Desktop\original.js:3:29), <anonymous>:2:63571)     at C:\Users\Sandbox\Desktop\original.js:4:25     at ContextifyScript.Script.runInContext (vm.js:35:29)     at Object.exports.runInContext (vm.js:67:17)     at run_in_ctx (C:\tools\malware-jail\jailme.js:145:16)     at Object.<anonymous> (C:\tools\malware-jail\jailme.js:168:1)     at Module._compile (module.js:570:32)     at Object.Module._extensions..js (module.js:579:10)     at Module.load (module.js:487:32)
I runned malware-jail with config_wscript_only config. (download sample: https://ufile.io/31a14)
Thank a lot, awesome tool.

Hi,
the sample has been deleted from the above url. Can you please zip it with password "infected" and upload again?

here: https://dropfile.to/2vadDvO, pwd: "infected".
Thanks a lot !

Hi,
thanks for the sample. Quite advanced piece.
I have committed today a couple of new functions, that avoid the above error.
However in the sample there is a lot of silencing catch(es){}. Need to work a bit more on it in upcoming days.

Cool !  I just fetched the last commits and I get more output. Thanks ! Your tool is very promising.

I have added a bit more functions.
Try to run:
node jailme.js --down=y -c ./config_wscript_only.json malware/20161031/sample_nocatch.js
Still missing something as the payload does not get downloaded. Note the script is calling itself with various arguments.

Thanks a lot. I found a similar sample which you may test as well in the next release of malware-jail:
https://gist.githubusercontent.com/anonymous/4673e1d5f610a21c86038c35bb7c268e/raw/3617557d0653b3892e5e65cf4a0e04a4850cb51c/malware.js

Hi, I've added the missing methods and made a few additional changes.
Please review the outputs in this commit: b587d8f4a75d7cfd2ecda57408ba24ce72d5def8
Appreciate if you can test the latest version.


Build errors

hello, i met the issue with follow:

Errors     << voxblox_rrt_planner:make /home/jinghao/workspace/mav_voxblox_planning/catkin_ws/logs/voxblox_rrt_planner/build.make.002.log
make[2]: *** No rule to make target '/opt/ros/melodic/lib/libompl.so', needed by '/home/jinghao/workspace/mav_voxblox_planning/catkin_ws/devel/lib/libvoxblox_rrt_planner.so'.  Stop.
make[1]: *** [CMakeFiles/voxblox_rrt_planner.dir/all] Error 2
make: *** [all] Error 2

Any ideas?
Thank you

hi,
first,make sure mav_voxblox_planning latest
second,try: sudo apt-get install libompl-dev and remove ros-melodic-ompl
Duplicate of #22


Keep a changelog

Trans should keep a changelog stating its changes accross time. This site explains it perfectly:

What’s the point of a change log?
To make it easier for users and contributors to see precisely what notable changes have been made between each release (or version) of the project.
Why should I care?
Because software tools are for people. If you don’t care, why are you contributing to open source?

The changelog is in place and ready for release 1.0.1


"literal" modifier on custom directive causes v-if to be ignored

Vue.js version
1.0.21
Reproduction Link
http://jsfiddle.net/5sH6A/317/

Quick fix: <div v-test.literal="" v-if="false" >1. This should not be visible</div>
Placing the literal before v-if resolves this bug for a quick fix. This is indeed a bug.
@yyx990803 Assigning to myself to look at.

@vuejs/collaborators FYI
This is due to the modifiers of directives being parsed to directives. so .literal is being fed to the previous directive even though it's not applied to that directive.

Wowsie.
Does not happen with every directive/modifier though, e.g. @click="doSomething" @mouseover.prevent does not prevent the click default.

@simplesmiler Happens with terminable directives
Found the issue and creating PR now


Pull in upstream updates from cisagov/skeleton-tf-module

🗣 Description
This pull request pulls in upstream updates from cisagov/skeleton-tf-module.
💭 Motivation and Context
This repo wasn't even taking advantage of lineage.  Also, @mcdonnnj pointed out that it was wasting APB task slots, since it wasn't able to take advantage of the APB dispatches.
🧪 Testing
All pre-commit hooks and molecule tests pass.
🚥 Types of Changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (causes existing functionality to change)

✅ Checklist

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Makes sense to me  As an aside, the problem with apb is that it just looks for a build.yml workflow and sends a dispatch if it's >week since the last build. If the project hasn't been updated to do anything with those dispatches and there's nothing manually triggering Actions runs, then apb will just keep sending them into the abyss.

Updated the description to state the correct APB issue.


Update build.gradle Fix for issue #45

@zaguiini please review and merge this PR, the community needs it asap:)

I went with https://github.com/zaguiini/react-native-pure-jwt/pull/40. Thanks.


Simple file upload doesn't respect apiEndpoint

File uploading does not respect apiEndpoint or the environment variable STORAGE_EMULATOR_HOST. Instead it uses a hardcoded constant STORAGE_UPLOAD_BASE_URL
Environment details

OS: Mac 10.14.6
Node.js version: 12.12.0
npm version: 6.11.3
@google-cloud/storage version: 4.0.0

Thanks for digging into that, and sharing the solution you found! Is STORAGE_EMULATOR_HOST an official env var? That follows the format from Datastore, although unlike Datastore, I haven't found an official Storage API emulator.
@frankyn what is the extent of support we want to provide for this use case?

I'm currently using fake-gcs-server as my emulator. The environment variable was dug up in source code: https://github.com/googleapis/nodejs-storage/blob/f2d567f279fee0f48c2d6a607f4066c9da372549/src/storage.ts#L375-L379

Would it work if it followed the same creation method as Buckets? ie the bucket.create() method calls the Service.createBucket method. If a File called Bucket.createFile(aka startSimpleUpload_) then when the uri is built inside Bucket.request({ uri: '/o' }) it would end up building the correct url.

@stephenplusplus, STORAGE_EMULATOR_HOST env var was introduced for benchmarking by @jadekler. We don't have an official GCS emulator at the moment.
IIUC, STORAGE_EMULATOR_HOST should have the same effect as setting apiEndpoint.

Ah, nice, I didn't know that slipped in there. I think we can figure this out. I'll assign to myself and update everyone accordingly for reviews!

@frankyn In our other APIs, options.apiEndpoint and the corresponding emulator environment variable are expected to have the same side effects when set-- everything is appended to that "base" URL.
Currently in Storage, however, the emulator environment variable replaces https://storage.googleapis.com/storage/v1, while options.apiEndpoint only replaces storage.googleapis.com.
Since options.apiEndpoint was designed for the same purpose as the environment variable and STORAGE_EMULATOR_HOST isn't an official environment variable, can we rethink this to have both behave equally?
In any case, what would be the correct URL to send the upload request to:

https://${userProvidedOverride}/upload/storage/v1/b/${this.bucket.name}/o
https://${userProvidedOverride}/b/${this.bucket.name}/o (the /upload/ prefix removed, otherwise /storage/v1/ is duplicated)

Hope this made sense!

@frankyn let me know if you think otherwise:
I think we should keep upload requests at the /upload endpoint, as-per GCS documentation. For the particular use case of fake-gcs-server by @chrisrecalis, this endpoint is supported.
+1 to STORAGE_EMULATOR_HOST mapping to options.apiEndpoint, question is which one should take precedence?

If this can help anyone, the workaround provided will not work with:
File.createWriteStream() as it uses startResumableUpload_ instead of startSimpleUpload_.
You can use File.createWriteStream({resumable: false}) in the meantime.


ExecEngine error messages don't show up as expected

In default ExecEngine functions such as InsPair, DelPair, etc., there are explicit statemetns that count the number of arguments and raise an exception of which the text mentions the function that raised the error, as follows:
ExecEngine::registerFunction('InsPair', function ($relationName, $srcConceptName, $srcAtom, $tgtConceptName, $tgtAtom) {
    /** @var \Ampersand\Rule\ExecEngine $this */
    if (func_num_args() != 5) {
        throw new Exception("InsPair() expects 5 arguments, but you have provided ".func_num_args(), 500);
    }

However, in practice, this is NOT what is presented:

This issue calls for the reinstatement of errors as they are geenrated from the PHP, so that the error stuff that is show to the developer makes sense and prevents him/her from tedious searching for what went wrong.

I'm now working on a fix for this issue. See below how it will be.
The error message contains:

The place in the ADL code where a fix is needed
Explanation of what went wrong

Support for multiple tgt atoms in DelPair was already included in: fdb5849bfb34e605632f8dae2c08c09b152c6395


[BUG] 2.11.1 Adding DSL filter to geomap is not possible with Brave browser

Describe the bug
Using Brave  v 1.61.116:
https://github.com/opensearch-project/OpenSearch-Dashboards/assets/2643715/9d0b2257-e3e4-4dd6-97dd-46809699ab97
In Firefox it works as expected.
Expected behavior
Save button is clickable.
OpenSearch Version
2.11.1
Dashboards Version
2.11.1
Plugins
N/A
Screenshots
See vid
Host/Environment (please complete the following information):
Default docker containers

Catch All Triage - 1 2 3 4 5