[Backport to main] change exception type; get function name from cache (#790)

Description
Backport PR #790 to main branch
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #793 (8694fc2) into main (a6c5061) will decrease coverage by 0.03%.
The diff coverage is 68.42%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff              @@
##               main     #793      +/-   ##
============================================
- Coverage     84.31%   84.29%   -0.03%
- Complexity     1593     1595       +2
============================================
  Files           135      135
  Lines          5937     5946       +9
  Branches        560      562       +2
============================================
+ Hits           5006     5012       +6
- Misses          693      695       +2
- Partials        238      239       +1

Flag
Coverage Δ

ml-commons
84.29% <68.42%> (-0.03%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...va/org/opensearch/ml/task/MLPredictTaskRunner.java
82.14% <0.00%> (ø)

...org/opensearch/ml/rest/RestMLPredictionAction.java
48.71% <57.14%> (+1.65%)
:arrow_up:

...n/java/org/opensearch/ml/model/MLModelManager.java
78.40% <66.66%> (-0.21%)
:arrow_down:

...a/org/opensearch/ml/engine/algorithms/DLModel.java
85.52% <100.00%> (ø)

...earch/ml/action/load/TransportLoadModelAction.java
84.07% <100.00%> (ø)

...va/org/opensearch/ml/model/MLModelCacheHelper.java
92.24% <100.00%> (+0.18%)
:arrow_up:

...rg/opensearch/ml/plugin/MachineLearningPlugin.java
98.82% <100.00%> (ø)

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


Docker 1.10 and Amazon Elastic Container Registry

So I have been using Docker 1.10 to make sure it works well with existing 3rd party products. I am having a serious problem in regards to pushing images to an ECR. The push times out every one min and tries 3 or 5 times, can't remember. I downgrade to 1.9 and the push works just fine. This is a significant blocker for anyone using Amazon ECS as their deployment cluster and hoping to upgrade to Docker 1.10

If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
For more information about reporting issues, see CONTRIBUTING.md.
You don't have to include this information if this is a feature request
(This is an automated, informational response)

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

Please try with RC4, which just came out yesterday.
There is a fix for push timeouts.

@cpuguy83 I can't find the RC4 file. Can you please point me in its direction?
Thanks

https://releases.dockerproject.org/

@cpuguy83 thanks, Im getting an auth issue with aws
./docker-1.10.0-rc4 login -u AWS -p super_long_token -e none https://314410645069.dkr.ecr.us-east-1.amazonaws.com
Just hangs

ERRO[0886] Handler for POST /v1.22/auth returned error: invalid registry endpoint https://314410645069.dkr.ecr.us-east-1.amazonaws.com/v0/: unable to ping registry endpoint https://314410645069.dkr.ecr.us-east-1.amazonaws.com/v0/
v2 ping attempt failed with error: Get https://314410645069.dkr.ecr.us-east-1.amazonaws.com/v2/: dial tcp <IP_ADDRESS>:443: i/o timeout
v1 ping attempt failed with error: Get https://314410645069.dkr.ecr.us-east-1.amazonaws.com/v1/_ping: dial tcp <IP_ADDRESS>:443: i/o timeout. If this private registry supports only HTTP or HTTPS with an unknown CA certificate, please add --insecure-registry<PHONE_NUMBER>69.dkr.ecr.us-east-1.amazonaws.com to the daemon's arguments. In the case of HTTPS, if you have access to the registry's CA certificate, no need for the flag; simply place the CA certificate at /etc/docker/certs.d/314410645069.dkr.ecr.us-east-1.amazonaws.com/ca.crt

@kitsushadow Do you have the RC4 daemon running?

@kitsushadow Should the https:// be there?

@cpuguy83 yes the daemon is running but its running as sudo b/c if i dont use sudo i get this error
[mminaie@localhost Downloads]$ ./docker-1.10.0-rc4 daemon
unable to configure the Docker daemon with file /etc/docker/daemon.json: open /etc/docker/daemon.json: permission denied

@kitsushadow Yes, the daemon must run as root.

@cpuguy83 thanks for the help! working now


Teradata StdJDBCDelegate error

Because of Teradata do not support != in SQL (I have no idea how this is possible in 2021).
Still, the problem exists.
The solution is to use <> instead of !=. Appears <> is more standard to SQL rather then !=.
The place in quartz is in:
StdJDBCConstants.SELECT_NEXT_TRIGGER_TO_ACQUIRE
Sorry.

Related reading:
https://knowledge.informatica.com/s/article/631826?language=en_US

Just googled and it appears that there might be more affected databases: https://stackoverflow.com/a/723426/449553


fix layout-top-nav drop down menu in small screen.

Please add the following css to fix the BUG.
.layout-top-nav .main-header {
    max-height: inherit;
}

Before:

After:

You know how git works, right?
You can always change the code in your own fork yourself and then send a pull request.
The maintainers then only have to accept the change or deny it. Simple as that.

@dojo1017 yes, but I don't know how to use less..

I wouldn't change it, a additional class is better.


Address Langchain vulnerabilities

Grype scans of the current version of Janus show 3 critical and 2 high severity vulnerabilities. Any high or critical vulnerabilities prevent Janus from being  cross-domained to secure secret spaces. Therefore, Janus cannot currently be used in the AI Code Refactor project. Good news is that all vulnerabilities are due to a singular package, Langchain, with fixes available in newer versions. Updating to at least v0.0.329 should provide all the fixes. Below is a Grype scan screenshot of the current vulnerability CVEs with the corresponding package and fixed versions.

In the newer, closed source versions of Janus (at some point will be open-source), LangChain is at 0.2.3. For the sake of the project you're referencing, you won't need to worry.
I'll keep this opened and marked as planned though, since this will be fixed in the open-source version at some point.

@doyled-it is it possible to get access to the closed source version of Janus?


Portfolio

Coverage remained the same at 82.567% when pulling f5699527dd4658881041724c022ccaddfa4028a2 on hj2304:portfolio into 841ddc392ab9224c914ab756cf0671e952ad3682 on CS2103AUG2017-F10-B2:master.


embed message and photo delete after sending ?

embed message and photo delete after sending ?

i know it's been a while, but i just added the auto removal of files in 1bd406d not sure if i'll ever add the support for embeds though


fix: tolerate explicit JSON null values in UnmarshalXXX() methods

Fixes: https://github.ibm.com/arf/planning-sdk-squad/issues/1517
Fixes: https://github.ibm.com/ibmcloud/platform-services-go-sdk/issues/14
This PR adds an explicit nil check when retrieving properties from a map inside the various UnmarshalXXX() methods.   Previously, we were checking for the existence of the property in the map, but did not consider the possibility that the value of the property is the JSON null value.

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


test ci

Converted to draft PR to avoid accidential merging. I think you can still commit to trigger CI in draft PRs if you need further tests.

I apologize, I didn't mean to open a PR on dask/dask-jobqueue:master.  Closing now.


Feature Request: Support for ROI

Hi,
First of all, thanks for all your all's work on this project, this is an amazingly useful tool!
I have been exploring the features available in both igv.js and igv-jupyter.  I am particularly interested in the ROI feature described here: https://github.com/igvteam/igv.js/wiki/Regions-of-Interest
I tried calling the browser.loadROI() method on a Browser object within igv-jupyter, but ran into an error since that method doesn't exist in the igv-jupyter version.  It would be extremely useful for our use case to have the ability to highlight ROIs in all tracks and/or a specific track.  We would appreciate if this feature could be supported in igv-jupyter too!
On a slightly related note: Is it possible to color the ROIs based on some sort of score?  Our ROIs each have a score associated with them, with higher scores indicating regions that are of greater interest.  Could we vary the transparency of the ROIs such that regions with higher scores are less transparent and those with lower scores are more transparent?
For example, the example method call in the Wiki looks like this:
browser.loadROI([
                        {
                            name: 'ROI set 1',
                            url: 'https://s3.amazonaws.com/igv.org.test/data/roi/roi_bed_1.bed',
                            indexed: false,
                            color: "rgba(68, 134, 247, 0.25)"
                        }
                  ]);

Could the "color" argument take some sort of function to vary the transparency based on a score in the input ROI file?

Support has been added with the latest checkin. This has not yet been pushed to a release.
Example Use
b.roi({
    "name": 'ROI set 1',
    "url": 'https://s3.amazonaws.com/igv.org.test/data/roi/roi_bed_1.bed',
    "indexed": False,
    "color": "rgba(255, 134, 65, 0.25)"
})

If you're interested, you're welcome to check out the code, build the extension and verify that the new functionality works. Otherwise, it will probably take a couple weeks to be properly tested and released.

Fantastic, thanks for such a quick response!  In the meantime, since I opened this issue, I have been experimenting with using browser.load_track() with the Annotation track type as a temporary stand-in to display ROIs as a single track, using a call something like this:
b.load_track({
    "name": "ROI: Annotations",
    "type": "annotation",
    "url": "path/to/my/bed/file.bed"
})

I added in a BED track line to the file to accomplish the second part of my above question regarding coloring the ROIs based on score.  It looks like with the option itemRgb="On" I can specify RGB colors for each row in the file and with useScore=1, the scores in the score column (i.e. column 5) are used to render the track in greyscale, with higher scores showing as darker.  If both are used together, like in the below example file, the color and greyscale functionalities are combined.  So in this file, the first row is displayed as a very transparent red and the second row is displayed as a very dark blue.  (Interestingly, a score of 0 also displays a very dark color, just like a score of 1000 does, so that may be a potential bug to look into.)
Example file content (I tried to upload it, but .bed files aren't a supported file type here in a GitHub comment):
track name="ItemRGBDemo" description="Item RGB demonstration" itemRgb="On" useScore=1
chr1  100218  117218  ROI1  1  +  105218  115218  255,0,0
chr1  206218  222218  ROI2  1000  -  209218  220218  0,0,255

Am I correct in assuming these track line options would also be supported in the b.roi() method you just implemented?

As long as they are supported in the underlying igv.js library, they should be supported in the b.roi() method, as that method just passes the options along to Javascript.

This update has been released to pip.


Add check for dead modules.

When a module defined by a ml-mli pair of files is dead, it would be nice to report that concisely rather than to report that each item in the module is dead.

Indeed dead module is not something checked for currently, and it would be nice to have in future. In particular when a module becomes dead by having all its elements dead, perhaps, transitively, so it's not immediately obvious before running the analysis.

@jberdine we're getting there: https://github.com/cristianoc/reanalyze/pull/61.

Done. Under -experimental.


Add slather/Coveralls test coverage reports

Modify project file to generate code coverage metrics
Add step to .travis.yml to install slather and send metrics to Coveralls
Add .slather.yml to configure how we send metrics to Coveralls.
Add Coveralls Badge to README.md

You will need to enable Coveralls for AlexDenisov/FrameAccessor. I ran slather locally and reported test coverage is 100% :star2:

Very nice feature, thank you @dasmer.
I didn't manage to find why coveralls needs commit access, maybe you can give me a point?
I'm pretty sure there is something obvious, but I can't blindly give an access to a third-party tool, 'cause I'm member of a few organizations with a bunch of private repos.

@AlexDenisov I would refer to https://github.com/lemurheavy/coveralls-public/issues/450. I believe Coveralls needs commit:status to generate coverage stats. I would defer to @nickmerwin for more info.

It looks like test coverage isn't being reported correctly on Travis. Closing until I figure out why.

Got it, let me know if I can help you.

Re-opening to test a fix

@AlexDenisov: We're getting coverage reports again :dancer:

Also, to give you some more insight on why coveralls.io asks for commit read access, the service gives you line-by-line data on how often a tested line is called on in your unit tests:
ie:

Great job, @dasmer!
Waiting for a travis build to see the new and shiny coveralls badge :+1:

Very good job)


[AIRFLOW-520] Fix Version Info in Flask UI

Make sure you have checked all steps below.
Jira

[x] My PR addresses the following Airflow Jira issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-520

Description

[x] Here are some details about my PR, including screenshots of any UI changes:

That is because of the following issue:
>>> import pkg_resources
>>> airflow_version = pkg_resources.require("apache-airflow")[0].version
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/kaxil/.virtualenvs/airflow_stable_pip/lib/python2.7/site-packages/pkg_resources/__init__.py", line 892, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/Users/kaxil/.virtualenvs/airflow_stable_pip/lib/python2.7/site-packages/pkg_resources/__init__.py", line 783, in resolve
    raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (Flask-Login 0.2.11 (/Users/kaxil/.virtualenvs/airflow_stable_pip/lib/python2.7/site-packages), Requirement.parse('Flask-Login<0.5,>=0.3'), set(['flask-appbuilder']))

This also brings it in line with RBAC FAB UI.
Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[x] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters (not including Jira issue reference)
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[x] In case of new functionality, my PR adds documentation that describes how to use it.

When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.

Code Quality

[x] Passes flake8

@ashb Can we include this in 1.10, please ??? 😉

Codecov Report

Merging #4072 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #4072      +/-   ##
==========================================
- Coverage   77.69%   77.68%   -0.01%
==========================================
  Files         199      199
  Lines       15957    15956       -1
==========================================
- Hits        12397    12396       -1
  Misses       3560     3560

Impacted Files
Coverage Δ

airflow/www/views.py
68.89% <0%> (-0.02%)
:arrow_down:

Continue to review full report at Codecov.

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


Update apktool to 2.3.0

There is an exception when decompiling my apk, I didn't dig into it. But it works fine if I replace the apktool with its latest version which is 2.3.0. You can close this PR if you think it's not necessary.

@gejiaheng thanks for your PR. Please, change the version of the library at the bat script as well and I'll merge it.

@gejiaheng nevermind, I've already done this. Thanks for you PL.

Sorry for my carelessness, I forgot bat.


Feature to print resolved version without invoking bazel

It would be great to get the resolved version of bazel without invoking bazel.
Running bazelisk --version takes ~0.5s, which is noticeable by users.
My use case involves caching items that solely depend on the version of bazel, and I would like to avoid invoking bazel altogether whenever it can be avoided.

Closing this as duplicate of https://github.com/bazelbuild/bazelisk/issues/440


feature/delete-checkpoint

Added new dropdown menu option in policies view.
Added delete checkpoint method into the policy service.
Added literals.

Changes Unknown when pulling 08fd53094c76fb840e28c08e015a50d736f51e5b on fjsc:feature/delete-checkpoint into ** on Stratio:master**.


Change Twitter icon to new X Logo

Preview environment created!
The preview environment has been deployed to the cluster.
Client URL: https://pr-1779--epp.elifesciences.org
Storybook URL: https://pr-1779--epp-storybook.elifesciences.org
Note: If this is a new environment, it can take a few minutes for DNS to update.

Preview environment images deployed!
The preview environment has been updated:
client image tag: preview-1779-8b113c02094ae4fc3b2170d5bb1d305bd08d0a0d-20240319.1213
storybook image tag: preview-1779-8b113c02094ae4fc3b2170d5bb1d305bd08d0a0d-20240319.1213
Client URL: https://pr-1779--epp.elifesciences.org
Storybook URL: https://pr-1779--epp-storybook.elifesciences.org
Note: Updated images can take a few minutes to roll out.

@chris-huggins Can you please look at the new logo's and say if you are happy with this?
https://pr-1779--epp.elifesciences.org/

Looks good to me, thanks @discodavey


Bumping pytest version to fix unresolvable pluggy dependency

Fixes #150

Coverage remained the same at 95.185% when pulling 2f7d7e079a5eaca087ee33eeaf5c873827e80f06 on bump-pytest-version into 7dcddb04370a68832a248fa17f230ca011878960 on master.

Coverage remained the same at 95.185% when pulling 2f7d7e079a5eaca087ee33eeaf5c873827e80f06 on bump-pytest-version into 7dcddb04370a68832a248fa17f230ca011878960 on master.

Coverage remained the same at 95.185% when pulling 2f7d7e079a5eaca087ee33eeaf5c873827e80f06 on bump-pytest-version into 7dcddb04370a68832a248fa17f230ca011878960 on master.

Coverage remained the same at 95.185% when pulling 2f7d7e079a5eaca087ee33eeaf5c873827e80f06 on bump-pytest-version into 7dcddb04370a68832a248fa17f230ca011878960 on master.

Thanks!


feat(automod): add mention limit enum

Summary
closes #810
This pull request adds the MENTION_LIMIT enum.
Checklist

[ ] If code changes were made then they have been tested.

[x] I have updated the documentation to reflect the changes.
[ ] I have run task pyright and fixed the relevant issues.

[x] This PR fixes an issue.
[x] This PR adds something new (e.g. new method or parameters).
[ ] This PR is a breaking change (e.g. methods or parameters removed/renamed)
[ ] This PR is not a code change (e.g. documentation, README, ...)

It seems like the AutoModerationTriggerType enum in enums.py was not changed

It seems like the AutoModerationTriggerType enum in enums.py was not changed

Correct, I was told that I didn't do the other half of what the issue was requesting 😅

:+1: It seems like both parts were half done and still 1 part to go.

[x] mention_spam in enum
[x] mention_spam in enum docs
[x] mention_total_limit added to types
[ ] mention_total_limit implementation in the trigger metadata class (auto_moderation.py)

In other words mention_total_limit should appear anywhere allow_list currently appears


OpenBAFANG resets "Speed Meter Signals" to 1

First: the OpenBAFANG tool does not show th parameter "Speed Meter Signals" like the windows tools do.
Seond: using OpenBAFANG on my controller resets the parameter "Speed Meter Signals" to 1 which is needed to be set to 5 for correct speed recognition. Could you possibly add that parameter to your program? I would be verry Happy ;)

Is this problem exists on uart or can system?

Please send me log files

Is this problem exists on uart or can system?

The problem is on uart. I will generate the logs asap but it may take some days. I will come back to you.

Is this problem exists on uart or can system?

The problem is on uart. I will generate the logs asap but it may take some days. I will come back to you.

Just collect log file from it's directory:
on Linux: ~/. config/open-bafang-tool/logs

on macOS: ~/Library/Logs/open-bafang-tool/logs

on Windows: %USERPROFILE%\AppData\Roaming\open-bafang-tool/logs

sorry for the new issue. came from a handheld. (#13) here comes the log again.
log.log

sorry for the new issue. came from a handheld. (#13) here comes the log again.
log.log

Thank you. Please also send other log files from same directory (old.log or similar name, I don't remember)

It is the only file in ~/. config/open-bafang-tool/logs

What is your version of software?

2.1.1-rc

I already found reason why magnet number always sets to 1 (I forgot to remove from code temporary constant, that was added for test purposes). I will fix it in next release and add config to UI

Hello. I just published new release 2.2.2 with parameter for number of magnets


Can't enable RS485

I have a Jakiper 48V100 battery with Pace BMS. When I connect to it with pbmstools I can see all the data, but the CANBus and RS485 protocol selection drop-downs are empty. Clicking Read shows a "successful" message, but still does not populate the list, and there is a a red "interruption" message in the status bar lower right.
Any ideas? Is there more than one variation of the pbmstools software?
I have the password, and I have tried th Jakiper tool, but it has no selection for the RS485 protocol.

Could you try to talk to your manufacturer and ask about another firmware with RS485 support for your battery bank? This is just an idea. I don't know how to make sure RS485 is supported or not.

Hi, we successfully connected and read data from a battery to the serial monitor. But there is an issue with mqtt not connecting. Does it have something to do with home assistant? Can we use a mqtt broker to connect to node red?

The mqtt component of ESPHome is able talk to any MQTT broker and can be used with any Home Automation software / it's not limited to Home Assistant. Could you attach a USB cable to your ESP board and provide a ESPHome log? It will supply all needed details whats going on.

This is the error we get ehrn connecting to mqtt. the logger level is set to very verbose. The mqtt component is asking for a IP but we are not much sure about this ip

Could you provide your YAML configuration too? It looks like the configuration of the mqtt section is wrong.

this is the yaml file we use to test the mqtt alone now

Please pass the FQDN or IP address here:
mqtt:
  broker: <IP_ADDRESS>
  port: 1883
  username: !secret mqtt_username
  password: !secret mqtt_password

MQTT-URLs aren't supported here.


docs/developing: Explicitly install test requirements

Using pip 8.1.2, test requirements specified using "tests_require"
are not automatically installed.

Look like the corresponding pip issue is still open. See https://github.com/pypa/pip/issues/1197

[Current coverage][cc-pull] is 72.78%

Merging [#33][cc-pull] into [master][cc-base-branch] will not change coverage

@@             master        #33   diff @@
==========================================
  Files             9          9
  Lines           654        654
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            476        476
  Misses          178        178
  Partials          0          0

Powered by Codecov. Last updated by [b44cf3c...bb02559][cc-compare]
[cc-base-branch]: https://codecov.io/gh/tony/vcspull/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/tony/vcspull/compare/b44cf3c33dcf1ccd6ac1a52715d8a838bbd0902a...bb0255993c4f84bb24076226d35fcf6dad4230c1
[cc-pull]: https://codecov.io/gh/tony/vcspull/pull/33?src=pr


Syntax error in line 1

/usr/local/bin/resume-bandit: line 1: syntax error near unexpected token `('
'usr/local/bin/resume-bandit: line 1: `var fs   = require("fs");

Note: I'm not very well versed with Node and related things, but a friend told me to try this:
npm install -g fs
which is supposed to install fs module system wide.
It didn't solve the problem.

Could you please explain how can i reproduce this ?

fs is native to nodejs you shouldn't have to install fs
more likely you decided to edit the code and made a change to the text...your error message is incomplete. Please repast the entire thing.

FWIW, I'm able to duplicate @noodlebreak's error. This was off of a freshly brewed (im on a mac) copy of node and a clean npm install -g resume-bandit
My-Mac:Work$ npm install -g resume-bandit
/usr/local/bin/resume-bandit -> /usr/local/lib/node_modules/resume-bandit/src/bandit.js
<EMAIL_ADDRESS>/usr/local/lib/node_modules/resume-bandit
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
My-Mac:Work$ resume-bandit
/usr/local/bin/resume-bandit: line 1: syntax error near unexpected token `('
'usr/local/bin/resume-bandit: line 1: `var fs   = require("fs");
My-Mac:Work$ node -v
v0.12.4

I was just trying to run it, tried running with help option, and I got that error.

Seconded.
Output:
Alexs-MacBook-Air:resume alex$ resume-bandit -d resume.yaml
/usr/local/bin/resume-bandit: line 1: syntax error near unexpected token `('
'usr/local/bin/resume-bandit: line 1: `var fs   = require("fs");

:+1:

i'll try to get around a mac to test this issue , could not reproduce it on my win8 and ubuntu boxes.

@Alexander-0x80, have you hosted this anyhwere? It would be great to try out for demo.

i guess it would be nice to have, i will get on it

Any updates yet, @Alexander-0x80 ?

I guess it should work on mac's now ..  can anyone check this out ?


Create MIT License

Codecov Report

Merging #16 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #16   +/-   ##
=======================================
  Coverage   89.13%   89.13%
=======================================
  Files           4        4
  Lines          46       46
=======================================
  Hits           41       41
  Misses          5        5

Continue to review full report at Codecov.

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


Question: Output to file works - Output to stream doesn't

Hi there,
this isn't an issue (I believe & hope), more a question or a behaviour I can't explain.
I´m trying to convert a mjpeg stream (from a http resource) to a mp4 stream.
If I´m using the native ffmpeg output to file method, everything works as expected:
Here is the code:
var ffmpeg = require('fluent-ffmpeg');

ffmpeg()
    .input('http://<IP_ADDRESS>/image.jpg')
    .inputOptions('-loop 1')
    .outputOptions('-c:v libx264')
    .outputOptions('-t 3')
    .outputOptions('-pix_fmt yuv420p')
    .outputOptions('-f mp4')
    .output('foo.mp4')
    .on('start', function(commandLine) {
        console.log('Spawned Ffmpeg with command: ' + commandLine);
     })
    .on('error', function(err) {
           console.log('An error occurred: ' + err.message);
    })
    .on('end', function() {
          console.log('Processing finished !');
    })
    .run();

If I´m trying to use a stream as an output, I´m getting the following error:
Spawned Ffmpeg with command: ffmpeg -loop 1 -i http://<IP_ADDRESS>/image.jpg -c:v libx264 -t 50 -pix_fmt yuv420p -f mp4 pipe:1
An error occurred: ffmpeg exited with code 1: Could not write header for output file #0 (incorrect codec parameters ?): Invalid argument

Here is the code that produces the error:
var fs = require('fs');
var ffmpeg = require('fluent-ffmpeg');

var wms = fs.createWriteStream('1_newtest.mp4');

ffmpeg()
    .input('http://<IP_ADDRESS>/image.jpg')
    .inputOptions('-loop 1')
    .outputOptions('-c:v libx264')
    .outputOptions('-t 3')
    .outputOptions('-pix_fmt yuv420p')
    .outputOptions('-f mp4')
    .output(wms, {end: true })
    .on('start', function(commandLine) {
        console.log('Spawned Ffmpeg with command: ' + commandLine);
     })
    .on('error', function(err) {
          console.log('An error occurred: ' + err.message);
    })
    .on('end', function() {
          console.log('Processing finished !');
    })
    .run();

My ffmpeg version & compile flags:
ffmpeg version 2.4.3 Copyright (c) 2000-2014 the FFmpeg developers
  built on Dec 13 2014 16:48:42 with Apple LLVM version 6.0 (clang-600.0.56) (based on LLVM 3.5svn)
  configuration: --prefix=/usr/local/Cellar/ffmpeg/2.4.3 --enable-shared --enable-pthreads --enable-gpl --enable-version3 --enable-nonfree --enable-hardcoded-tables --enable-avresample --cc=clang --host-cflags= --host-ldflags= --enable-libx264 --enable-libfaac --enable-libmp3lame --enable-libxvid --enable-libtheora --enable-libvorbis --enable-vda
  libavutil      54.  7.100 / 54.  7.100
  libavcodec     56.  1.100 / 56.  1.100
  libavformat    56.  4.101 / 56.  4.101
  libavdevice    56.  0.100 / 56.  0.100
  libavfilter     5.  1.100 /  5.  1.100
  libavresample   2.  1.  0 /  2.  1.  0
  libswscale      3.  0.100 /  3.  0.100
  libswresample   1.  1.100 /  1.  1.100
  libpostproc    53.  0.100 / 53.  0.100

I´m running this on Mac OSX Yosemite.
If you could give me a hint on what I´m doing wrong, that would be awesome. Thank you.
Cheers
Sebastian

Thanks Asciidisco and Njoyard for your questions and answers, I got the same issues and they are very helpful

Thank you @asciidisco for your solution! It fixed it for me.

:+1:

Guys, is there any other alternative than -movflags frag_keyframe+empty_moov ? I can't use those flags because Twitter media upload rejects video created with it...

@alekbarszczewski you only need those when you intend to stream the media. Just don't use the option when the goal is to read the file as a whole.

@njoyard yes but I don't want to save mp4 to a file - I need to get stream and it does not work for mp4 without this flags

If twitter does not support initial moov you won't be able to stream the same file you send them.

@asciidisco me too face the same problem using to merge audio and video with this https://github.com/WritingMinds/ffmpeg-android-java library for android after merging video is not viewed in default video player in device but it plays in vlc player, think so video codec issue,can you please help me to solve this issue.

.format("h264") √
.format("mp4") ×
or add
.outputOptions(['-movflags isml+frag_keyframe'])
.format("mp4")

Hey @a1003584293 I followed your comment and the process finished without errors But it's still in 3gpp format (in my case) and I want to pipe the mp4 stream and upload it to AWS s3. DO you have any solution for that?
`let readstream = s3.getObject(params).createReadStream();
ffmpeg.setFfmpegPath(ffmpegPath);
ffmpeg(readstream)
.outputOptions(['-movflags isml+frag_keyframe'])
// .outputOptions(['-c:v libx264'])
// .outputOptions(['-f mp4'])
// .outputOptions(['-pix_fmt yuv420p'])
.toFormat('avi')
.on('error', (err, stdout, stderr) => {
// Handle errors here
console.log(err);
console.log(err.message);
})
.on('end', () => {
// Processing is complete
console.log('Processing finished !');
})
.pipe(uploadToS3(response.Key, response.Bucket), { end: true })
// .save(${response.Key}.mp4);
}
const uploadToS3 = (key: string, bucket: string) => {
// Create a new stream
let pt = new stream.PassThrough();
console.log(pt);
// Reuse the same params object and set the Body to the stream
let params = {
Bucket: bucket,
Key: key,
Body: pt,
};
// Upload and wait for the result
s3.upload(params, (err: Error, data: any) => {
if (err) return console.error(err);
console.log('done');
console.log(data.Location);

})
return pt;
};`

Followed up with the forum but the solution doesn't work for me. Here's my error.
Error: Error: Output format mp4 is not available
    at eval (webpack-internal:///(rsc)/./node_modules/fluent-ffmpeg/lib/capabilities.js:589:21)
    at nextTask (webpack-internal:///(rsc)/./node_modules/async/dist/async.mjs:5892:9)
    at next (webpack-internal:///(rsc)/./node_modules/async/dist/async.mjs:5900:9)
    at eval (webpack-internal:///(rsc)/./node_modules/async/dist/async.mjs:430:16)
    at eval (webpack-internal:///(rsc)/./node_modules/fluent-ffmpeg/lib/capabilities.js:549:7)
    at handleExit (webpack-internal:///(rsc)/./node_modules/fluent-ffmpeg/lib/processor.js:170:11)
    at ChildProcess.eval (webpack-internal:///(rsc)/./node_modules/fluent-ffmpeg/lib/processor.js:184:11)
    at ChildProcess.emit (node:events:518:28)
    at ChildProcess._handle.onexit (node:internal/child_process:294:12)
    at Process.callbackTrampoline (node:internal/async_hooks:130:17)
Error: Error processing video
    at FfmpegCommand.eval (webpack-internal:///(rsc)/./src/trpc/index.ts:228:19)
    at FfmpegCommand.emit (node:events:518:28)
    at emitEnd (webpack-internal:///(rsc)/./node_modules/fluent-ffmpeg/lib/processor.js:424:16)
    at eval (webpack-internal:///(rsc)/./node_modules/fluent-ffmpeg/lib/processor.js:433:16)
    at wrapper (webpack-internal:///(rsc)/./node_modules/async/dist/async.mjs:374:16)
    at next (webpack-internal:///(rsc)/./node_modules/async/dist/async.mjs:5898:20)
    at eval (webpack-internal:///(rsc)/./node_modules/async/dist/async.mjs:430:16)
    at wrapper (webpack-internal:///(rsc)/./node_modules/async/dist/async.mjs:374:16)
    at next (webpack-internal:///(rsc)/./node_modules/async/dist/async.mjs:5898:20)
    at eval (webpack-internal:///(rsc)/./node_modules/async/dist/async.mjs:430:16)
    at eval (webpack-internal:///(rsc)/./node_modules/fluent-ffmpeg/lib/capabilities.js:589:18)
    at nextTask (webpack-internal:///(rsc)/./node_modules/async/dist/async.mjs:5892:9)
    at next (webpack-internal:///(rsc)/./node_modules/async/dist/async.mjs:5900:9)
    at eval (webpack-internal:///(rsc)/./node_modules/async/dist/async.mjs:430:16)
    at eval (webpack-internal:///(rsc)/./node_modules/fluent-ffmpeg/lib/capabilities.js:549:7)
    at handleExit (webpack-internal:///(rsc)/./node_modules/fluent-ffmpeg/lib/processor.js:170:11)
    at ChildProcess.eval (webpack-internal:///(rsc)/./node_modules/fluent-ffmpeg/lib/processor.js:184:11)
    at ChildProcess.emit (node:events:518:28)
    at ChildProcess._handle.onexit (node:internal/child_process:294:12)
    at Process.callbackTrampoline (node:internal/async_hooks:130:17)
 ⨯ src\trpc\index.ts (249:16) @ FfmpegCommand.eval
 ⨯ uncaughtException: Error: Error processing video
    at FfmpegCommand.eval (webpack-internal:///(rsc)/./src/trpc/index.ts:228:19)
    at FfmpegCommand.emit (node:events:518:28)
    at emitEnd (webpack-internal:///(rsc)/./node_modules/fluent-ffmpeg/lib/processor.js:424:16)
    at eval (webpack-internal:///(rsc)/./node_modules/fluent-ffmpeg/lib/processor.js:433:16)
    at wrapper (webpack-internal:///(rsc)/./node_modules/async/dist/async.mjs:374:16)
    at next (webpack-internal:///(rsc)/./node_modules/async/dist/async.mjs:5898:20)
    at eval (webpack-internal:///(rsc)/./node_modules/async/dist/async.mjs:430:16)
    at wrapper (webpack-internal:///(rsc)/./node_modules/async/dist/async.mjs:374:16)
    at next (webpack-internal:///(rsc)/./node_modules/async/dist/async.mjs:5898:20)
    at eval (webpack-internal:///(rsc)/./node_modules/async/dist/async.mjs:430:16)
    at eval (webpack-internal:///(rsc)/./node_modules/fluent-ffmpeg/lib/capabilities.js:589:18)
    at nextTask (webpack-internal:///(rsc)/./node_modules/async/dist/async.mjs:5892:9)
    at next (webpack-internal:///(rsc)/./node_modules/async/dist/async.mjs:5900:9)
    at eval (webpack-internal:///(rsc)/./node_modules/async/dist/async.mjs:430:16)
    at eval (webpack-internal:///(rsc)/./node_modules/fluent-ffmpeg/lib/capabilities.js:549:7)
    at handleExit (webpack-internal:///(rsc)/./node_modules/fluent-ffmpeg/lib/processor.js:170:11)
    at ChildProcess.eval (webpack-internal:///(rsc)/./node_modules/fluent-ffmpeg/lib/processor.js:184:11)
    at ChildProcess.emit (node:events:518:28)
    at ChildProcess._handle.onexit (node:internal/child_process:294:12)
    at Process.callbackTrampoline (node:internal/async_hooks:130:17)
  247 |         .on("error", (error: string, stdout: string, stderr: string) => {
  248 |           console.error("Error:", error);
> 249 |           throw new Error("Error processing video");
      |                ^
  250 |         })
  251 |         .videoFilter({
  252 |           filter: "drawtext",


[Automation] Generate Fluent Lite from Swagger fluidrelay#package-2022-06-01

[Automation] Generate Fluent Lite from Swagger fluidrelay#package-2022-06-01

/azp run java - fluidrelay - mgmt - tests

API change check
APIView has identified API level changes in this PR and created following API reviews.
com.azure.resourcemanager:azure-resourcemanager-fluidrelay


SocialNetWork: docker-swarm-DESRIBE|DESC will not work in cqlsh '6.0.0' connected to Cassandra '3.9', the version that you are connected to.

WARN: DESCRIBE|DESC was moved to server side in Cassandra 4.0. As a consequence DESRIBE|DESC will not work in cqlsh '6.0.0' connected to Cassandra '3.9', the version that you are connected to. DESCRIBE does not exist server side prior Cassandra 4.0.

Hi, I met the same WARN, too. Did you find any solution yet? Thanks!


Yii::app->modules on Centos6

On first line it crashes
    if (\Yii::$app->modules) {
        foreach (\Yii::$app->modules as $name => $namespace) {
            $module = \Yii::$app->getModule($name);

            if (!isset($module->menuList) || empty($module->menuList->getList())) {
                continue;
            }

            $menu = array_merge($module->menuList->getList(), $menu);
        }
    }

But on Ubuntu (local) it works. Why this can happen?
Routes and params are valid, I recheck it several times. Code executed in view (main layout).

How exactly it crashes?

http://awesomescreenshot.com/0745z7hdc3
The connection was reset
The connection to the server was reset while the page was loading.
The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer's network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.

What's in the logs?

[Sun Jun 26 15:23:31 2016] [error] [client <IP_ADDRESS>] PHP Fatal error:  Can't use method return value in write context in /var/www/xxx/backend/views/layouts/_sidebar.php on line 39, referer: http://xxx/panel/articles/article/list
latest one

What's in the _sidebar.php around line 39?

Is a view, that $this->render('_sidebar') in main /backend/layouts/main.php. Look code in first post. I erase everything from there for clear tests.

<?php

namespace backend\components;

use backend\components\sidebar\MenuList;
use yii\base\InvalidConfigException;
use yii\base\Module;

/**
 * Class ModuleExtended
 *
 * @package backend\components
 *
 * @property MenuList   $menuList
 * @property array|null $requiredModules
 */
class ModuleExtended extends Module
{
    public $menuList;
    public $requiredModules;

    /**
     * @throws InvalidConfigException
     */
    public function init()
    {
        $this->menuList = new MenuList();
        parent::init();
        $this->checkRequiredModules();
    }

    /**
     * @param string $moduleName
     *
     * @return $this
     */
    public function addRequiredModule($moduleName)
    {
        $this->requiredModules[] = $moduleName;

        return $this;
    }

    /**
     * @return array
     */
    public function getRequiredModules()
    {
        return $this->requiredModules;
    }

    /**
     * @throws InvalidConfigException
     */
    public function checkRequiredModules()
    {
        if ($this->requiredModules) {
            foreach ($this->requiredModules as $moduleName) {
                if (!\Yii::$app->hasModule($moduleName)) {
                    throw new InvalidConfigException('Module requires another module. ' . $moduleName . ' not enabled.');
                }
            }
        }
    }
}

empty($module->menuList->getList())

Prior to PHP 5.5 you can not pass expression (method) to empty(), you need use variable. Try $module->menuList->list or use helper variable.

@rob006 YES! THANK YOU!
Localy I have Ubuntu php 5.5, on Centos php  5.4 That's was a problem. Thank you again. Can be closed.


8.5.3 No such file or directory error

I am using bitbucket to update my concrete5 website. Up pushing an update branch to the orgin. Then pushing the orgin to the live webserver.
The error I get when updating concrete5 to 8.5.3
include(/home/staging/public_html/concrete/vendor/composer/../natxet/cssmin/src/CssMin.php): failed to open stream: No such file or directory
The issue is the actual folder structure in the core is /natx et/CssMin/src/CssMin.php.
To fix the error I made a change the folder structure to /natxet/cssmin/src/CssMin.php.

This is a screenshot of the 8.5.3 directory listing. I don't see this space:

I think you need to revisit your deployment processes. Maybe they're adding these spaces.


Fix typo

Noticed a small typo in the name of the method to get the starting pose from an auto file. This change will make it so the naming of the method reflects the naming in the docs.

nvm didn't realize someone already opened a pr


Bugfix and overrides

In some cases users will need to override the account and group LDAP query patterns, and we previously did not enable this. This PR adds this feature, and it inadvertently fixes a DRY bug regarding the default value of the id_attr configuration option.
I had to refactor the _get_groups_for_user method a bit, but it converts from using filter_format, which just called escape_filter_chars:
def filter_format(filter_template, assertion_values):
  return filter_template % tuple(escape_filter_chars(v) for v in assertion_values)

to using escape_filter_chars directly:
filter_values = {
    'user_dn': ldap.filter.escape_filter_chars(user_dn),
    'username': ldap.filter.escape_filter_chars(username),
}
query = self._group_pattern % filter_values

I will need to update the enterprise docs. I'll work on a PR for that on Monday.

Can you give an example, maybe in the README, of how one might use this?

Added an overview of what this plugin actually does regarding LDAP, and added descriptions to the table of options for the new account_pattern and group_pattern options, as well as two more examples: one for simply specifying id_attr, and another for overriding both account_pattern and group_pattern (including a note that you don't have to override both at the same time). :+1:
Also fixed a few Markdown syntax typos that GitHub was rendering properly, but should still be fixed regardless.

I should also add some tests for these new options... I'll do that tomorrow.


update opentargets-py author information

Andrea is still listed as a contact and author for the opentargets-py client documentation. This should be updated to general "open targets core team" and support email

Well spotted. Perhaps we should have Open Targets Platform team instead of Open Targets Core team as there is Genetics core team as well...
I think we should still acknowledge Andrea though.

Andrea is still listed as the commit author in the git repository, so anyone can see exactly who did what if they are interested.
This has been merged as opentargets/opentargets-py#33 - we can do another PR if there are further changes needed.


Add large tab for "Trace" & improve trace page

Add a large tab for Trace to map and mosaic.
clicking the tab will load the existing trace page
Add breadcrumbs back to map / mosaic
Add a "return to warper link"
Make trace page look similar in format to other maps
(ideally, in the future, the id editor could load up within the tab itself)

So I managed to put it in the tabs themselves now.


extra collisions beside collidable tiles

I am encountering a bug where if you have a tile map with collisions, when I generate a map using that tile map there are extra collisions beside collidable tiles. This happens to every 2d generator and I have tried to fix it with no success. Is this a bug or is there something I am doing wrong?

If this helps my tiles are 32 by 32 pixels

Sorry for being so late, but could you explain further with screenshots?

https://github.com/BenjaTK/Gaea/assets/166310634/586fc12f-7a47-47d2-8565-fb06b0e10f1a
This is what I mean. I'm only supposed to collide with the white tiles, but I am also colliding with surrounding black tiles as well. I'm not sure if I am doing something wrong or if it is a bug.

Seems to me like a project problem. I think you're not colliding with black tiles but the collision shape of your player isn't aligning with the player's sprite or the tile's collision shape isn't a square. Maybe turn on "Visible Collision Shapes"?

This is an earlier prototype but the generation works basically the same. As you can see, some white tiles are given black tile collisions. All of the unintentionally collidable white tiles are neighbors of black tiles. Do you have any idea on how to fix this?


feat(styles-migrations): add migration secondary-classes

Preview environments are getting posted here, as soon as they are ready!


NgModel in a @deferred component doesn't work properly

It can be built without error, but the model won't update.
repro
// app_component.dart
import 'package:angular/angular.dart';
import 'src/my_input/my_input_component.dart';

@Component(
  selector: 'my-app',
  directives: const [InputComponent],
  template: r'<my-input @deferred></my-input>',
)
class AppComponent {}

// src/my_input/my_input_component.dart
import 'package:angular/angular.dart';

@Component(
  selector: 'my-input',
  directives: const [formDirectives],
  template: r'<input [(ngModel)]="model"> {{ model }}',
)
class InputComponent {
  String model;
}

Thanks for filing and for the reproduction case!

Thank you for repro case. We have a fix. It is in review.


Fix infinite recursion error

Looks like I wanted a property to return itself. This PR is a fix to #34

Re-running travis.
Should we move run_example.py to a nosetest?

Merging, since travis won't work from your fork PR.

(I've been using forks in the main repo.)


Typeahead highlight for custom filters

This is a feature request for Typeahead control...
To be able to customize the highlight logic to match a custom filter.
At the moment the control highlights matches only using the default match filter: filter:$viewValue.
We use two custom filters, a custom OR filter and a custom AND filter where we take $viewValue, do .split(' ') on it and then try to match individual words against the list using OR or AND logic accordingly.
It would be great if we could somehow match the highlight logic to be able to see where in a long text item we have the matching words.

Couldn't one override the template to use a custom filter? This is probably the best approach without introducing bloat into the library.


If new msg text is None, fallback to empty str

Equivalent change to b6ba473eabb6f622d24cca3be19efb013dde8481, but happening in a different place. See description from #138.

This seems to have come up a couple of times - if possible, can we add a unit or functional test for it? Let me know if you're comfortable doing that.

Hi @jtatum ,
re: .get() and or '' being redundant - Yea, I thought that too when I looked at the code. As described more verbosely in #138, the value under the key text is None so .get() returns None, not the fallback of empty-string. Subsequently, passing None into the regexp matcher raises an exception.
Here's an illustrative example:
>>> d = {'text': None}
>>> repr(d.get('text', ''))
'None'
>>> repr(d.get('text', '') or '')
"''"

re: Adding tests - Sure, will do.

Hi @jtatum,
Updated PR:

Added unit test for #138, already merged.
Moved logic of change for #144 to deeper-level, defending against bad input of text==None.

Added unit test for #144.

Testing Done:
================================================= 40 passed, 1 skipped in 97.21 seconds ==================================================


Deno: Imports without the extensions aren't valid in Deno.

export * from './memoryStorage'; export * from './types';
need to be:
export * from './memoryStorage.ts'; export * from './types.ts';

@ranseur92 thank you for mentioning this! The imports/exports for deno are fixed now.


Get this error for mailgun

Loading "mailgun.js" tasks...ERROR

SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
Warning: Task "mailgun" not found. Use --force to continue.
Aborted due to warnings.

I sent @markhuge a pull request to his node-mailgun-send that fixes this issue.

Looks like your PR is still lingering.
I was able to send mailgun emails just fine with the grunt send --template=[THE_TEMPLATE_NAME] command.
@rwillwerth - What is your node version? That could be an issue if you're on an older version. I'm on v7.x
node --version

This is going to sound really pedantic, but I've had to stop accepting PRs  (however trivial) for issues that are not effecting current LTS.
This doesn't seem to be an issue in 6.x which is the current LTS.

Nothing wrong with that, Mark. Thanks.
We can call this closed.


check kernel version and issue warning if necessary

Fixes #178
for real this time

The problem is the NOTICE.md mechanism is a general purpose scheme for warning about any change that may cause issues - not just for the 4.0 kernel.
The correct solution is for WARNING.md to include a git hash for the first update that requires the warning. E.g. a line like ``HASH: abcdef0123456789abcdef```
Call this hash W.
The last rpi-update hash in in /boot/.firmware. Call this U.
The latest hash you are updating to is L.
Then, if U < W && L >= W you display the warning.

How to achieve this when hashes are not incremental?

This repo is committed to linearly (without rebases/merges) so the date of the hashes should be in order.
If you run with JUST_CHECK=1 it prints a list of commits since you last updated. Grepping that for the HASH listed in NOTICE.md should say if you are including the WARNING commit.

I have updated the script so it can compare commit hashes. Also added HASH to NOTICE.md in rpi-firmware repo.

Looks promising.
Can you handle the case where HASH is not present in NOTICE.md (I think you should get the warning unconditionally)
Can you handle the case where /boot/.firmware_revision is not present (treat LOCAL_HASH date as very old).

@shrx any chance you would update this to @popcornmix spec so it an be merged?

@shrx it would be cool if you had the time to make the small changes so this PR could be merged.

Sorry, I completely forgot about this.
Will have a look at what needs to be done.

@Ruffio @popcornmix I think everything is in order now, it should handle the case where HASH is not present in NOTICE.md and where /boot/.firmware_revision is not present.

Currently we have a dependency on curl but not wget, and this PR adds a dependency on wget.
Is is possible to switch to using curl for get_hash_date?

@popcornmix can you check now? I removed the offending spaces (hopefully all) and switched to curl.

Should the curl include -L?
I think we needed to add that to all other uses as github sometimes redirects responses.

It can't hurt, I guess.

@popcornmix is this good to go?
I guess that the "add -L to curl in all other places" should be performed in another PR?

With the current NOTICE.md file, we discard the first line of the message.
I suspect we want to use NOTICE when NOTICE_HASH_EXISTS=true and FULL_NOTICE when NOTICE_HASH_EXISTS=false.

@popcornmix merge?

@shrx any chance you would do the last changes so we can get this PR merged? It would be awsome to get it in place. Think about it

@lurch @popcornmix ready to merge?

@popcornmix ready to merge?

@popcornmix ready to merge?

@shrx any chance you would update this PR?

@Ruffio what needs updating?

@shrx Have you read @lurch comments and observations? It also looks like there is a conflict to be resolved.

@shrx is this still relevant?


dsp/window: use half offset to exclude flanking zeros

Please take a look.
Closes #1240.

cc @goofinator

PTAL


Expose SETDEX in '@smogon/calc' npm package

It would be useful for me to be able to access the SETDEXs for each generation so I could put the sets into the optional parameter when instantiating a Pokemon object. I saw that such a data structure exists in shared_controls.js. Would exposing that item in the @smogon/calc npm package be something people would be alright with?

I do believe that @pkmn/smogon provides APIs for looking at sets on the Smogon Dex, so that's probably also a good place to look.

Ok, thanks!


Need to upgrade golang.org/x/net for CVE-2023-39325

Output of helm version: 3.13.0
Output of kubectl version: 1.27.1
Cloud Provider/Platform (AKS, GKE, Minikube etc.):  AKS
New CVE 2023-39325 was published 2 days ago.
https://github.com/advisories/GHSA-4374-p667-p6c8
We need helm team to upgrade package and found a dependabot PR below.
But it is still in open status.
https://github.com/helm/helm/pull/12481

Helm binary is flagged vulnerable in our CVE scanning. We need helm to be compliant in our product.

What I don't understand is how helm/helm@2745909d:go.mod#145 (the current trunk) already references 0.17 (which, according to the adivsory, contains a fix), and has been since at least Oct 12th, but still v3.13.1 which was released after that change occured still contains 0.13.
Was there an accident in release preparation or is this "as expected"?

Can't reproduce with 3.14.0


kak-prelude: init at 2020-03-15

Motivation for this change
This is a dependency for some other plugins (like newer versions of auto-pairs.kak).
Things done2019-07-27

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files [the plugin] (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg eval

@GrahamcOfBorg build kakounePlugins.kak-prelude

@buffet in future, please use the full attribute path in the commit message, so OfBorg knows what to build.


New package: OpenSCAD.OpenSCAD.Nightly version 2024.10.31

Pull request has been created with komac v2.3.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

Verify:


Forecasted GHI is greater than clear sky GHI

Using GFS as the forecast model, I am seeing GHI values as much as 13% higher than what ModelChain calculates when no irradiance data is provided (default ineichen clearsky model).

I’ve seen the same thing from NAM, compared to Ineichen’s clear sky model.
From: willhobbs<EMAIL_ADDRESS>Sent: Thursday, June 30, 2016 1:04 PM
To: pvlib/pvlib-python<EMAIL_ADDRESS>Subject: [EXTERNAL] [pvlib/pvlib-python] Forecasted GHI is greater than clear sky GHI (#206)
Using GFS as the forecast model, I am seeing GHI values as much as 13% higher than what ModelChain calculates when no irradiance data is provided (default ineichen clearsky model).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/pvlib/pvlib-python/issues/206, or mute the threadhttps://github.com/notifications/unsubscribe/AFJNLwPAgBAbxjamoQ6IIuztJhjzHdtzks5qRBMUgaJpZM4JCfbA.

There are two reasons why the forecast module's irradiance data will be different from the ineichen model's:

The forecast module uses the Liu Jordan model to convert a cloud cover forecast to an irradiance forecast. It's going to give different results even in clear sky conditions.
The forecast module fails to supply the Liu Jordan model with a time-varying top-of-atmosphere irradiance. I'll fix this later today.

@cwhanse are you referring to the raw NAM data or the forecast module's processed version of it?

I’m referring to the GHI values in the NAM forecast downloaded from NOAA.
From: Will Holmgren<EMAIL_ADDRESS>Sent: Thursday, June 30, 2016 2:09 PM
To: pvlib/pvlib-python<EMAIL_ADDRESS>Cc: Hansen, Clifford W<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: [EXTERNAL] Re: [pvlib/pvlib-python] Forecasted GHI is greater than clear sky GHI (#206)
There are two reasons why the forecast module's irradiance data will be different from the ineichen model's:

The forecast module uses the Liu Jordan model to convert a cloud cover forecast to an irradiance forecast. It's going to give different results even in clear sky conditions.
The forecast module fails to supply the Liu Jordan model with a time-varying top-of-atmosphere irradiance. I'll fix this later today.

@cwhansehttps://github.com/cwhanse are you referring to the raw NAM data or the forecast module's processed version of it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/pvlib/pvlib-python/issues/206#issuecomment-229773434, or mute the threadhttps://github.com/notifications/unsubscribe/AFJNL_tgdTrqYuvq6Ya2f107GtabUESmks5qRCJDgaJpZM4JCfbA.

@willhobbs I wrote a new cloud cover to irradiance algorithm that's based on the ineichen function and the turbidity file. It's basically this...
solpos = location.get_solarposition(cloud_cover.index)
cs = location.get_clearsky(cloud_cover.index, model='ineichen')
# offset and cloud cover in decimal units here
ghi = (offset + (1 - offset) * (1 - cloud_cover)) * ghi_clear
dni = disc(ghi, solpos['zenith'], cloud_cover.index)['dni']
dhi = ghi - dni * np.cos(np.radians(solpos['zenith']))

See the updated documentation for more.
Lot's of room for experimentation and likely improvements. I have no idea how the accuracy of the two methods ('clearsky_scaling' and 'liujordan') compares.

Closed by #180.


Add documentation for overriding ssh_wrapper in shell app

With this PR we can now specify an ssh wrapper to the shell app. This should be documented somewhere here.
It should include

verbage on why you may need to do it.
how to do it
an simple example

This was documented in master during the 1.7 release notes updates.


Duplicate key in en.json

FleetingLuckSpendTitle key is used for two different strings and it cause some issues when importing into translation software.

Fixed in #348

I just spotted this, and it seems that the linked change made alterations to Elf Immunities only. The duplicate Fleeting Luck key is still present.

hopefully fixed in #349


How to integrate this within semantic-ui prior to build?

So my concern is how do I include js/css and relevant files of this component into semantic-ui prior to build so that all the css and js get build into semantic.min.js/semantic.min.css.

Oh my bad! I had to include calendar in  tasks/config/default.js


Write page "about.html" containing more detailed information than in about dropdown

about.html is mostly written in dev branch, but remains there for now because the "Technical Overview" section remains unwritten because I'm insufficiently familiar with the subject matter to write it.

"Technical Overview" section now written (by @G33kDude), so I'm closing this issue.


package.json is missing main field

Describe the bug
Not all tooling supports the package.json exports field, including TypeScript when running with moduleResolution: node (which is the case for most apps using a bundler).  Is there a reason not to include a main field to improve compatibility with existing tooling?
In my particular case, I'm having trouble with eslint's import/no-extraneous rule.  It does not think the plugin is installed, but it is.
Reproduction URL
https://stackblitz.com/edit/vitejs-vite-yb9bgt?file=src%2Fexample.js&terminal=lint
Reproduction
Check the example, eslint throws an error.  If you add a main to the package.json, the error disappears.
Logs
No response
System Info
N/A

This should be raised at eslint. exports map has a higher priority than main, in fact it means that main must be ignored.
Typescript has it's own types condition and we set that, so that should not be a problem if it is, again, raise it with them.
Sorry if this sounds harsh but the whole "main vs module vs browser vs whatever" top level resolve hint field debacle is only going to get worse if people start adding exports maps to the mix instead of replacing the older fields.
We kept main until we were dropping our commonjs output for backwards compatibility. For all node versions we support, exports maps is supported, so use that.

That's disappointing.  It feels like you're intentionally causing pain to developers like me for purely philosophical reasons.

There is no pain, you can easily change your eslint config to ignore this rule for vite-plugin-svelte, or add a comment to ignore it above the import or contribute a fix to the eslint rule. Rools to resolve exports map exist: https://github.com/lukeed/resolve.exports so having this issue open for 118 months is the cause of this, not us removing main because it is no longer needed.


Add an inferface to Python API for a set of files and jobspecs

Description
Closes #78.

[x] Introduces BatchJobSpec for generating Jobs from a set of files and JobSpecs.
[x] Enables creation of file list via path globbing or dataset specification.
[x] Configurable in-flight batch size
[x] Ensures we have builtin fetch attempt / retry logic and the ability for an end user to specify fetch timeouts
[x] Add in the ability to check and handle failed jobs 'metadata.status' == failed
[ ] Adding native async calls in addition to Futures based async functionality is left for future work.

In the following example from README, BatchJobSpec is interchangeable with JobSpec in the main API.
from nv_ingest_client.client import NvIngestClient
from nv_ingest_client.primitives import BatchJobSpec
from nv_ingest_client.primitives.tasks import ExtractTask

batch_job_spec = BatchJobSpec(
    [
        "data/bo_20/*.pdf",
    ]
)

extract_task = ExtractTask(document_type="pdf", extract_text=True, extract_images=False, extract_tables=False)

batch_job_spec.add_task(extract_task)

client = NvIngestClient(
    message_client_hostname="nv-ingest-ms-runtime",  # Host where nv-ingest-ms-runtime is running
    message_client_port=7670,  # REST port, defaults to 7670
)
job_ids = client.add_job(batch_job_spec)

client.submit_job(job_ids, "morpheus_task_queue", batch_size=10)
result = client.fetch_job_result(job_ids, timeout=60, verbose=True)
print(f"Got {len(result)} results")

(nv_ingest) root@06dc675b3b16:/work/git/nv-ingest# python3 test_python_client.py
Job 14 is not ready. Retrying 1/∞ after 1 seconds.
Job 14 is not ready. Retrying 2/∞ after 1 seconds.
Got 20 results

Checklist

[x] I am familiar with the Contributing Guidelines.
[x] New or existing tests cover these changes.
[x] The documentation is up to date with these changes.

Thanks for doing this work, @edknv
I was attempting to try it out, but:
>>> from nv_ingest_client.primitives import BatchJobSpec
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: cannot import name 'BatchJobSpec' from 'nv_ingest_client.primitives' (/home/nfs/rgelhausen/projects/nv-ingest/venv/lib/python3.11/site-packages/nv_ingest_client/primitives/__init__.py)

Does our init logic need an update to make BatchJobSpec importable?

I believe I'm installing the client library from your commit:
rgelhausen@a4u8g-0132:~/projects/nv-ingest$ git fetch origin pull/158/head:batch_api
rgelhausen@a4u8g-0132:~/projects/nv-ingest$ git checkout batch_api
M       docker-compose.yaml
Switched to branch 'batch_api'
rgelhausen@a4u8g-0132:~/projects/nv-ingest$ git rev-parse HEAD
22899fd7d145f71130aa8fcdfaeb7a0b3d5d6cb6

Creating the env and installing:
rgelhausen@a4u8g-0132:~/projects/nv-ingest$ uv venv --python 3.11 venv
Using CPython 3.11.10
Creating virtual environment at: venv
Activate with: source venv/bin/activate
rgelhausen@a4u8g-0132:~/projects/nv-ingest$ source venv/bin/activate
(venv) rgelhausen@a4u8g-0132:~/projects/nv-ingest$ cd client
(venv) rgelhausen@a4u8g-0132:~/projects/nv-ingest/client$ uv pip install -r requirements.txt
Resolved 25 packages in 31ms
Installed 25 packages in 1.18s
 + annotated-types==0.7.0
 + anyio==4.6.2.post1
 + certifi==2024.8.30
 + charset-normalizer==3.4.0
 + click==8.1.7
 + h11==0.14.0
 + httpcore==1.0.6
 + httpx==0.27.2
 + idna==3.10
 + lxml==5.3.0
 + pillow==11.0.0
 + pydantic==2.9.2
 + pydantic-core==2.23.4
 + pypdfium2==4.30.0
 + python-docx==1.1.2
 + python-magic==0.4.27
 + python-pptx==0.6.23
 + redis==5.0.8
 + requests==2.32.3
 + setuptools==75.2.0
 + sniffio==1.3.1
 + tqdm==4.66.5
 + typing-extensions==4.12.2
 + urllib3==2.2.3
 + xlsxwriter==3.2.0
(venv) rgelhausen@a4u8g-0132:~/projects/nv-ingest/client$ uv pip install .
Resolved 26 packages in 95ms
Installed 1 package in 136ms
 + nv-ingest-client==2024.10.4.dev0 (from file:///home/nfs/rgelhausen/projects/nv-ingest/client)
(venv) rgelhausen@a4u8g-0132:~/projects/nv-ingest/client$ python
Python 3.11.10 (main, Sep  9 2024, 22:11:19) [Clang 18.1.8 ] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from nv_ingest_client.primitives import BatchJobSpec
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: cannot import name 'BatchJobSpec' from 'nv_ingest_client.primitives' (/home/nfs/rgelhausen/projects/nv-ingest/venv/lib/python3.11/site-packages/nv_ingest_client/primitives/__init__.py)

Hmm, I'm trying to repro but I can't seem to, even with using all the commands verbatim starting from git fetch origin pull/158/head:batch_api all the way down to uv pip install ..

ok, you can ignore my feedback. I must have messed up my git index, it's working for me now :)


TypeError: (0 , _styledSystem.removeProps) is not a function

Hi! I just upgraded the styled-system package today from 1.1.1 to 2.2.1, and now I am getting the following TypeError:
TypeError: (0 , _styledSystem.removeProps) is not a function

new BaseComponent
src/components/typography.js:7

   4 | import { Box } from 'grid-styled';
   5 |
   6 | const BaseComponent = props => {
>  7 |   const next = removeProps(props);
   8 |   return <Box {...next} />;
   9 | };
  10 |

Here's my Wrapper:
const BaseComponent = props => {
  const next = removeProps(props);
  return <Box {...next} />;
};

Has anything changed with removeProps?

The removeProps method was removed in v2 (see https://github.com/jxnblk/styled-system/releases/tag/v2.0.0) – instead you can use one of these packages:

https://github.com/jxnblk/styled-system/tree/master/clean-tag
https://github.com/jxnblk/styled-system/tree/master/clean-element

Ah, great! Thanks @jxnblk 😁


[BEAM-10260] Fix continuation token support with statecache

The continuation mode was always-on by mistake. Also, continuation mode would
arbitrarily nest appended state via iterators which would lead to the following
error:
RecursionError: maximum recursion depth exceeded while calling a Python object

In case of continuations tokens, we do not cache anything anymore after the
continuation. Caching after the continuation token would defeat the purpose of
using continuation tokens for large state. A test was added for continuation
tokens.
The extend operation was removed from the statecache in favor of using only
put/get/clear which avoids any race conditions with the cache eviction.

Run Python2_PVR_Flink PreCommit


Implementation of JupyterSetUp class that creates a part of a report

Class is to implement in en.py module that is a reporting component of  process of setting up a Jupyter Notebook.

Done


Use select to determine what executable definition to use

When running on my OSX laptop, for some reason it was always selecting
the Linux binary.  I was looking at trying to fix this by adjusting
the logic, but I have seen other patterns using select and a
condition around the target OS/Arch and this feels cleaner to me.
The upstream conditions being depended on are defined here.
https://github.com/bazelbuild/bazel/blob/1c29dff364fd34d7e6158c812cfd6d96f66be747/src/conditions/BUILD#L87-L94

Let me know if #8 fits your usecase. Thank you very much for this PR, however, it was a little bit easier to create a new one rather than continue with this one.


Fix missing namespace in sys crate build script

The build script of sys crate is throwing an error due to undeclared types. Let's fix it by adding namespaces.

File is imported on line 177. https://github.com/ulagbulag/dlib-face-recognition/blob/079158d821f0e85e4e0cc0c37a8f69b56f44db42/sys/build.rs#L177
Path is imported on line 4. https://github.com/ulagbulag/dlib-face-recognition/blob/079158d821f0e85e4e0cc0c37a8f69b56f44db42/sys/build.rs#L4
So I think there is no problem building on windows. Could you check and comment on?

@HoKim98 the build was failing, until I went to .cargo\registry\src to edit the source code with these changes. I can see the imports and it's weird I saw namespace errors, but this is what fixed my failures. 🤔

That's strange. Let me check on a windows VM and comment again.

for me it was giving the same error but when i used this pr on the cargo file it worked


Decreased Top1 accuracy under Multi GPUs in CIFAR10

Hi, Thank you for providing this ssl library and rapid response.
Now I'm confused with a new question, and I don't know if it can be solved.
I've compared the results of ssl methods (SimCLR, BYOL) of CIFAR10 under single GPU and multi GPUs.
Both of the multi GPUs results are lower then the single GPU under 1000 epoches.
The multi GPUs results were caculated with --sync_batchnorm and --strategy ddp.
Are there any suggestions to solve this problem?
BYOL results are shown as below (the 64 batch size results are still being calculated).

SimCLR results are shown as below.

I also calculated the multi GPU results with sgd optimizer.

There seems to be some problems in the lr optimizer.
Should the warmup_cosine scheduler multi GPU version be changed?
@vturrisi @DonkeyShot21
if self.scheduler == "warmup_cosine"
Here is the multi GPUs results of lr optimizer:

Here is the single GPU results of lr optimizer:

Yes, that doesn't look correct, I'll get back to you soon. Make sure you are using the latest commit.

@nanhuayu I just ran simsiam for 20 epochs with 1 GPU and batch size 256 and 2 GPUs and batch size 128 (per GPU). My results are pretty much the same (the scheduler is exactly the same, and the losses are a tiny bit different because of random initialization or stuff like this).

I ran the same script and under both 1.0.4 version and solo-learn-main vesion, but the results were different.
I haven't installed the solo module in the pip yet.
Is it possible that the version of pl library or torch library has an impact?
@vturrisi

python3 main_pretrain.py \     --dataset $1 \     --backbone resnet18 \     --data_dir ./datasets \     --max_epochs 20 \     --devices 0,1 \     --accelerator gpu \     --strategy ddp \     --precision 16 \     --optimizer sgd \     --scheduler warmup_cosine \     --lr 0.5 \     --classifier_lr 0.1 \     --weight_decay 1e-5 \     --batch_size 128 \     --num_workers 4 \     --crop_size 32 \     --brightness 0.4 \     --contrast 0.4 \     --saturation 0.4 \     --hue 0.1 \     --gaussian_prob 0.0 0.0 \     --crop_size 32 \     --num_crops_per_aug 1 1 \     --zero_init_residual \     --name simsiam-$1-ddp2-2 \     --project solo \     --entity nanhuayu \     --wandb \     --save_checkpoint \     --method simsiam \     --proj_hidden_dim 2048 \     --pred_hidden_dim 512 \     --proj_output_dim 2048

I'm not really sure what I'm supposed to look at. Also, the main and 1.0.4 are the same version. Can you reclone the repo and try from scratch?

I' tried several times, from different machine, and different pytorch version, and both the 1.0.4 and main version, which makes no difference. @vturrisi

I've confirmed the bug in vesion 1.0.4 by print the num_training_steps @vturrisi @DonkeyShot21

Which pytorch lightning version are you using? @nanhuayu

pytorch-lightning 1.6.4
liggtning-bolts 0.5.0
@vturrisi

@nanhuayu Pretty strange that you are getting this behaviour since I couldn't reproduce it. For sure it's related to how pytorch-lightning is parsing stuff, so it might have changed and made our code incompatible. I'm going to fix this as soon as I have time, but for now, you can manually scale the learning rate.

Thanks for your reply.
I've changed the the code related to num_devices in , which works fine in CIFAR and ImageNet100 datasets.
However, another problem happened when I used the DALI in ImageNet100 datasets.
There should be 130000/(4*128bs)*400ep=101562 steps, there are only a half of the steps (50600 steps).
Is it related to num_crops_per_aug?
main_pretrain.py --dataset imagenet100 --backbone resnet18 --data_dir datasets --train_dir imagenet-100/train --val_dir imagenet-100/val --max_epochs 400 --devices 0,1,2,3 --accelerator gpu --strategy ddp --sync_batchnorm --precision 16 --optimizer lars --grad_clip_lars --eta_lars 0.02 --exclude_bias_n_norm --scheduler warmup_cosine --lr 0.3 --weight_decay 1e-4 --batch_size 256 --num_workers 4 --brightness 0.8 --contrast 0.8 --saturation 0.8 --hue 0.2 --num_crops_per_aug 2 --name simclr-400ep-imagenet100-resnet18-256 --project solo --entity nanhuayu --wandb --save_checkpoint --method simclr --temperature 0.2 --proj_hidden_dim 2048

The bugs related to num_devices in solo/methods/base.py need to be fixed, or change the version of pytorch-lightning back to 1.5.10. @DonkeyShot21

@nanhuayu I'll check this soon and migrate to the new parameters that pytorch lightning uses.


Cannot initialize Waterline. The installed version of adapter sails-mongo is too new! Please try installing a version < 1.0.

Hello, I'm in Trouble here with the Lift the App.
I'm wundering, how connection it to the MongoDB. Do i have install the mongo DB npm in the package json file?..
When i want include in the connections.js file the MongoDB adapter like this :
 mongodb: {
    adapter: 'sails-mongo',
    host: 'localhost',
    port: 27017,
    // user: 'username',
    // password: 'password',
    database: 'name'
  },

and in the model.js want connection to the database :
module.exports.models = {

  /***************************************************************************
  *                                                                          *
  * Your app's default connection. i.e. the name of one of your app's        *
  * connections (see `config/connections.js`)                                *
  *                                                                          *
  ***************************************************************************/

   //connection: 'mongodb',

  migrate: 'alter'
};

my package.json file

{
  "name": "sails.js-login-app",
  "private": true,
  "version": "0.0.0",
  "description": "a Sails application",
  "keywords": [],
  "dependencies": {
    "ejs": "~0.8.4",
    "grunt": "0.4.2",
    "grunt-contrib-clean": "~0.5.0",
    "grunt-contrib-coffee": "~0.10.1",
    "grunt-contrib-concat": "~0.3.0",
    "grunt-contrib-copy": "~0.5.0",
    "grunt-contrib-cssmin": "~0.9.0",
    "grunt-contrib-jst": "~0.6.0",
    "grunt-contrib-less": "0.11.1",
    "grunt-contrib-uglify": "~0.4.0",
    "grunt-contrib-watch": "~0.5.3",
    "grunt-sails-linker": "~0.9.5",
    "grunt-sync": "~0.0.4",
    "include-all": "~0.1.3",
    "rc": "~0.5.0",
    "sails": "^0.12.14",
    "sails-disk": "~0.10.0",
    "sails-mongo": "^1.0.0"
  },
  "scripts": {
    "start": "node app.js",
    "debug": "node debug app.js"
  },
  "main": "app.js",
  "repository": {
    "type": "git",
    "url": ""
  },
  "author": "spaceg",
  "license": ""
}

after when i lift the app, i get this back :
error: A hook (`orm`) failed to load!
error: Failed to teardown ORM hook.  Details: Error: Consistency violation: Internal error in Waterline: Adapter received unexpected falsey datastore name (`null`)!  Can't look up a DS entry from this adapter with that...  (Please report this error at http://sailsjs.com/bugs.)
    at Object.teardown (/Users/spaceg/Downloads/basic-login-master/node_modules/sails-mongo/lib/index.js:387:19)
    at runTeardownInEachAdapter (/Users/spaceg/Downloads/basic-login-master/node_modules/sails-hook-orm/lib/teardown.js:45:15)
    at /Users/spaceg/Downloads/basic-login-master/node_modules/sails-hook-orm/node_modules/async/lib/async.js:181:20
    at Object.async.forEachOf.async.eachOf (/Users/spaceg/Downloads/basic-login-master/node_modules/sails-hook-orm/node_modules/async/lib/async.js:233:13)
    at Object.async.forEach.async.each (/Users/spaceg/Downloads/basic-login-master/node_modules/sails-hook-orm/node_modules/async/lib/async.js:209:22)
    at teardown (/Users/spaceg/Downloads/basic-login-master/node_modules/sails-hook-orm/lib/teardown.js:37:11)
    at Hook.teardown (/Users/spaceg/Downloads/basic-login-master/node_modules/sails-hook-orm/index.js:157:14)
    at Sails.wrapper (/Users/spaceg/Downloads/basic-login-master/node_modules/@sailshq/lodash/lib/index.js:3275:19)
    at Object.onceWrapper (events.js:313:30)
    at emitNone (events.js:106:13)
    at Sails.emit (events.js:208:7)
    at Sails.emitter.emit (/Users/spaceg/Downloads/basic-login-master/node_modules/sails/lib/app/private/after.js:50:11)
    at /Users/spaceg/Downloads/basic-login-master/node_modules/sails/lib/app/lower.js:67:11
    at beforeShutdown (/Users/spaceg/Downloads/basic-login-master/node_modules/sails/lib/app/lower.js:45:12)
    at Sails.lower (/Users/spaceg/Downloads/basic-login-master/node_modules/sails/lib/app/lower.js:49:3)
    at Sails.wrapper [as lower] (/Users/spaceg/Downloads/basic-login-master/node_modules/@sailshq/lodash/lib/index.js:3275:19)
    at sailsReady (/Users/spaceg/Downloads/basic-login-master/node_modules/sails/lib/app/lift.js:41:20)
    at /Users/spaceg/Downloads/basic-login-master/node_modules/sails/node_modules/async/lib/async.js:721:13
    at /Users/spaceg/Downloads/basic-login-master/node_modules/sails/node_modules/async/lib/async.js:52:16
    at /Users/spaceg/Downloads/basic-login-master/node_modules/sails/node_modules/async/lib/async.js:264:21
    at /Users/spaceg/Downloads/basic-login-master/node_modules/sails/node_modules/async/lib/async.js:44:16
    at /Users/spaceg/Downloads/basic-login-master/node_modules/sails/node_modules/async/lib/async.js:718:17
    at /Users/spaceg/Downloads/basic-login-master/node_modules/sails/node_modules/async/lib/async.js:167:37
    at /Users/spaceg/Downloads/basic-login-master/node_modules/sails/lib/app/load.js:173:22
    at /Users/spaceg/Downloads/basic-login-master/node_modules/sails/node_modules/async/lib/async.js:52:16
    at /Users/spaceg/Downloads/basic-login-master/node_modules/sails/node_modules/async/lib/async.js:565:21
    at /Users/spaceg/Downloads/basic-login-master/node_modules/sails/node_modules/async/lib/async.js:167:37
    at /Users/spaceg/Downloads/basic-login-master/node_modules/sails/lib/app/load.js:120:23
error:

error: Error:
-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
Cannot initialize Waterline.
The installed version of adapter `sails-mongo` is too new!
Please try installing a version < 1.0.
-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-

    at /Users/spaceg/Downloads/basic-login-master/node_modules/waterline/lib/waterline.js:90:15
    at /Users/spaceg/Downloads/basic-login-master/node_modules/waterline/node_modules/lodash/index.js:3073:15
    at baseForOwn (/Users/spaceg/Downloads/basic-login-master/node_modules/waterline/node_modules/lodash/index.js:2046:14)
    at /Users/spaceg/Downloads/basic-login-master/node_modules/waterline/node_modules/lodash/index.js:3043:18
    at Function.<anonymous> (/Users/spaceg/Downloads/basic-login-master/node_modules/waterline/node_modules/lodash/index.js:3346:13)
    at module.exports.Waterline.initialize (/Users/spaceg/Downloads/basic-login-master/node_modules/waterline/lib/waterline.js:86:7)
    at buildWaterlineOntology (/Users/spaceg/Downloads/basic-login-master/node_modules/sails-hook-orm/lib/build-waterline-ontology.js:45:19)
    at Array.async.auto._buildOntology (/Users/spaceg/Downloads/basic-login-master/node_modules/sails-hook-orm/lib/initialize.js:388:7)
    at listener (/Users/spaceg/Downloads/basic-login-master/node_modules/sails-hook-orm/node_modules/async/lib/async.js:605:42)
    at /Users/spacedigger/Downloads/basic-login-master/node_modules/sails-hook-orm/node_modules/async/lib/async.js:544:17
    at _arrayEach (/Users/spaceg/Downloads/basic-login-master/node_modules/sails-hook-orm/node_modules/async/lib/async.js:85:13)
    at Immediate.taskComplete [as _onImmediate] (/Users/spaceg/Downloads/basic-login-master/node_modules/sails-hook-orm/node_modules/async/lib/async.js:543:13)
    at runCallback (timers.js:794:20)
    at tryOnImmediate (timers.js:752:5)
    at processImmediate [as _immediateCallback] (timers.js:729:5)

error: Could not load Sails app.
error:
error: Tips:
error:  • First, take a look at the error message above.
error:  • Make sure you've installed dependencies with `npm install`.
error:  • Check that this app was built for a compatible version of Sails.
error:  • Have a question or need help?  (http://sailsjs.com/support)

Sails version^0.12.14:
**Node versionv8.10.0:
**NPM version5.6.0:
*DB adapter name adapter: 'sails-mongo',: N/A
DB adapter version: N/A
**Operating systemMacOS 10.13.4 *:

fixed!

Hello @SpaceG  .. Please let me know how you have fixed this issue. Please let me know the steps.
I have hot the same issue.
"sails": "~0.12.0",
"sails-mongo": "^1.0.1"

@Amimona85 could you fix the issue?


Add onSearch prop to the Combobox

This PR adds an onSearch prop to the Combobox to read the users input value.
Note:
I would have preferred to use the onChange prop for this and change it's current use to onSelect but this would break the API on the component I realise.
Use case:
If a user wants to query an endpoint for Combobox options which will be queried and narrowed down as the user starts typing. Think locations for example.

Thank you for this PR @tjcafferkey
I will need to test and probably adjust your suggestion a bit. I am also thinking that I will probably have to add a loading indicator so that the user knows that the combobox is loading the data.
I will also need to adjust the docs.
I will get back to you once I am done!

Yes absolutely. Thank you!
I'll keep an eye on this PR, so I can make sure my future PRs tick all the boxes for you.
I'll also create a couple of issues in the repo for things I think might be useful for contributors too! 😄

@tjcafferkey I pushed an update so that when onChange prop is added the component won't filter the options leaving it up to the developer.
I also updated the docs adding an example: https://rewind-ui.dev/components/combobox#on-search
Further suggestions always accepted!


About the box

While adding a new to do, we should be able to close the box by clicking on the parts outside the box.

This is intentional, and designed to prevent the user from accidentally closing the popup while they are adding a todo. The popup can be closed by pressing the Escape key instead.


Callback Error

Hi Hayden!
I've got an error in my configuration an I'd like to share it with you. Maybe you have a solution?
The generator works but I keep getting the following error message:

/Users/user/Projects/project/node_modules/favicons/index.js:152
                return callback(metadata);
                       ^
TypeError: undefined is not a function
    at Object.rfg.callback (/Users/user/Projects/project/node_modules/favicons/index.js:152:24)
    at /Users/user/Projects/project/node_modules/favicons/node_modules/real-favicon/index.js:121:57
    at /Users/user/Projects/project/node_modules/favicons/node_modules/real-favicon/index.js:116:28
    at done (/Users/user/Projects/project/node_modules/favicons/node_modules/real-favicon/node_modules/async/lib/async.js:135:19)
    at /Users/user/Projects/project/node_modules/favicons/node_modules/real-favicon/node_modules/async/lib/async.js:32:16
    at /Users/user/Projects/project/node_modules/favicons/node_modules/real-favicon/index.js:113:25
    at /Users/user/Projects/project/node_modules/favicons/node_modules/real-favicon/index.js:32:25
    at /Users/user/Projects/project/node_modules/gulp-replace/node_modules/istextorbinary/node_modules/safefs/node_modules/graceful-fs/graceful-fs.js:104:5
    at Object.oncomplete (fs.js:107:15)

That's my configuration:
gulp.task('favicons', function () {
	favicons({
		files: {
			src:  'src/assets/images/favicon-src.png',
			dest: 'dist/assets/images/favicons',
			html: 'dist/favicons.html'
		},
		icons: {
			android:      true,
			appleIcon:    true,
			appleStartup: true,
			coast:        true,
			favicons:     true,
			firefox:      true,
			opengraph:    true,
			windows:      true,
			yandex:       true
		},
		settings: {
			appName:        'test.com',
			appDescription: 'Personal Website of Name',
			developer:      'Name',
			developerURL:   'http://test.com/',
			version:        0.1,
			background:     '#ffffff',
			index:          'dist/index.html',
			url:            'http://test.com/',
			silhouette:     true,
			logging:        false
		}
	});
});

What am I doing wrong? What can I do?

This is actually my fault for not checking if a callback exists - I just fixed it then for favicons-2.1.1.
Anyway, you could fix this issue by specifying a callback function OR (much easier) use gulp-favicons.

Thanks! Yes, fixed in 2.1.1. :)


Update some more dependencies

Do we need pylint, autopep8, pydantic as dependencies? They don't appear necessary for people who just want to run the program or am I missing something?

No they are not necessary, it's probably taken from my VS Code set-up but even there they can be installed afterwards and do not affect CNApy.

I would keep these in the environment.yml because it is used to  set up a development environment. But in the meta.yml they should be removed.


build from git clone don't work

When i try to build this from scratch then i run in an error while build it via docker build.
Step 45 : COPY ./target/check-for-changes.sh ./target/start-mailserver.sh ./target/fail2ban-wrapper.sh ./target/postfix-wrapper.sh ./target/docker-configomat/configomat.sh /usr/local/bin/
lstat target/docker-configomat/configomat.sh: no such file or directory

The folder target/docker-configomat/ is empty when i pull this via git clone https://github.com/tomav/docker-mailserver
Seams not correct, or i make a misstake?

You need to load the submodules as well: git pull --recurse-submodules

Ok thx. May im the only one who build this from scratch. 👍

https://stackoverflow.com/questions/1030169/easy-way-to-pull-latest-of-all-git-submodules


[camera]skip app delegate during unit test

I noticed that during unit tests there are some code in app delegate that eventually setup the FLTCam in background thread, which runs concurrently with normal unit tests in main thread, making breakpoint a bit confusing when debugging.
This PR skips unnecessary didFinishLaunching setups for unit tests.
No version change: only affect Runner app's unit tests.
No unit tests: I don't think OCMock supports stubbing global functions. Just manually tested.
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the relevant style guides and ran the auto-formatter. (Unlike the flutter/flutter repo, the flutter/plugins repo does use dart format.)
[x] I signed the CLA.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[ ] I listed at least one issue that this PR fixes in the description above.
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy, or this PR is exempt from version changes.
[x] I updated CHANGELOG.md to add a description of the change, following repository CHANGELOG style.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

test-exempt: untestable (changes logic specifically for tests)


Implement checkpoint/restore commands

What type of PR is this?
/kind feature
/kind api-change
What this PR does / why we need it:
This enables the checkpoint/restore commands. Right now it can be used like this:
# crictl checkpoint CTR-ID
# crictl restore CTR-ID

To checkpoint and restore a container. It also offers the possibility to restore a container in another pod:
# crictl checkpoint CTR-ID
# crictl restore -p POD-ID CTR-ID # POD-ID being the destination pod

This PR is just to make sure the changes in https://github.com/cri-o/cri-o/pull/4199 can be tested.

/remove-lifecycle stale

/reopen


v0.3.0 release

we should work https://github.com/nerves-project/nerves_init_gadget/pull/18 into this and the 🚢 🇮🇹

Done


Please verify list of exercises

@samumantha @eglerean can you please check that the list here for your session is correct?
https://coderefinery.github.io/2023-09-19-workshop/exercises/

I would remove the dependencies exercise and give 5 more min to workflows exercise. But let's wait for @eglerean opinion.

I will adjust the page based on detailed schedule so don't worry about it now.

[ ] mark exercises not planned to be done in workshop as "optional"


Stack layout component

Implemented the stack layout component (version 1, no animation yet) and applied for the current editor3 layout.
Fixes #6548.
CR: @javierarce @viddo (men in pair programming, men in double code reviewing).

Extract the state logic from the the stack layout view to a view model.
StackLayoutView to listen to change:position events on the view model, and clean/render view(s) accordingly (i.e. the gotoPrev/NextStep logic of removing/creating views can stay in the view)
…with these changes, we can pass the viewModel when creating a stack item instead of individual closures, which now have the semantic methods on the view model i.e.

// …
{
  createStackItemView: function(stackViewModel) {
    // since first only can go fwd:
     stackViewModel.gotoNext();
  },
  createStackItemView: function(stackViewModel) {
   // since in the middle can go both back and fwd
    stackViewModel.gotoPrev();
    stackViewModel.gotoNext();
  },
  createStackItemView: function(stackViewModel) {
    // Last step, can only do:
    stackViewModel.gotoNext()
  }}

The template should not be necessary, going prev/next could/should be translated into this.$el.append(stackItemView.el) or this.$el.append(stackItemView.el) depending on direction. The markup/style will depend on the context and as such should be implementing by the individual stack item views.

What do you think now?

a part from the minor comments :shipit:

I hope this is the final change :fingers_crossed:.

Frontend tests passed, looks ok now @javierarce @viddo?

:ok_hand: fine for me

Waiting for tests, but I feel this is a good one, @javierarce @viddo?

:shipit:

There was conflicts with master, waiting for frontend tests and I'll merge it.


Error when using with --exiftool option

Thank you for creating this wonderful tool. I am using this tool to export my photo library on Big Sur and getting the following error when using exiftool option.
Error exporting photo (BE6A10E6-7569-4E1E-B954-4D647AA99555: IMG_4380.JPG) as IMG_4380.JPG: '<' not supported between instances of 'str' and 'NoneType'
Let me know if you need any additional information about the error. I think the error does not occur if I don't use exiftool option

Please post the entire command line you're using for osxphotos export.

osxphotos export --exiftool --export-by-date

I've searched through the code and can't find an obvious culprit.  Please run the following command and post the content here (or email to me at rturnbull+git@gmail.com).  Note: this will produce a debug dump of data that might contain private information such as location. So if that's important to you, look at it and sanitize the information first (all the fields are labeled should be self-explanatory).
osxphotos debug-dump --dump photos --uuid BE6A10E6-7569-4E1E-B954-4D647AA99555 > debug.txt

debug.txt
Please find attached the output. Thanks again for you support.

Thanks for the additional debug info. One more command to run.  Still trying to sort this out as it's not obvious so far what's causing the data. The error is almost certainly from a sorted call which only occurs a few places in the code but it's not clear from the example you sent what could be causing it.
osxphotos debug-dump --dump keywords --dump persons > debug.txt

debug.txt

Thanks -- that did it! I see the problem.  Now I need to figure out how to fix it as it's a condition I've never seen before and not sure if the issue is in Photos database or in my code.

The error almost certainly occurs in this section of code:
https://github.com/RhetTbull/osxphotos/blob/bd6656107b18d0bcec67540411b85180f6bec372/osxphotos/photoinfo/_photoinfo_export.py#L1596-L1598
The expected behavior when osxphotos encounters a face with no person name attached, is that osxphotos uses a sentinel value of "UNKNOWN" as the person name then filters these out when exporting persons with --exiftool.  In this database there are some persons that show a name of None instead of the sentinel value which is causing the error.  See below where person 14 has name of None but person 3265 has name of _UNKNONW_ as expected.
 14: {'displayname': None,
      'facecount': 166,
      'fullname': None,
      'keyface': 136,
      'keyface_uuid': '56F9638A-EBE3-4628-BD58-41513AB8E90F',
      'photo_uuid': 'C272EE75-FD6C-4819-9788-F60E8AA17DA3',
      'pk': 14,
      'uuid': '16AD2D0E-57DC-4E38-9E2B-E92D126A40FB'},
 3265: {'displayname': None,
        'facecount': 2,
        'fullname': '_UNKNOWN_',
        'keyface': 14760,
        'keyface_uuid': 'CEE75C95-9509-4945-8D7E-3EA60D4F0766',
        'photo_uuid': '42A43625-D9FD-41AC-8FFC-C639395384F2',
        'pk': 3265,
        'uuid': '2CB1B77C-7CF6-4BDB-8736-D7BFE599EBE1'},

Thanks. Like I said its a great tool you have built and I am glad I was able to help you remove a defect from it :). This is a regular Apple PhotoLibrary. I have not really played with it at all. I will still look at the pictures with None and see if I can recollect anything which may useful.
Also I did scroll down the file but failed to notice that there are actual names in there. Will appreciate if you can remove the file . Thanks

I deleted the debug data I'd downloaded.  I'm testing a fix now.

This should be fixed in v0.42.24.  Please give it a try and let me know if you still get an error.

@all-contributors add @kaduskj for bug

Thanks. Updated the version and error no longer occurs.