Helm deployed my chart resources, but fails to record the release so it cannot be managed

When I helm install my chart all of the resources are created successfully but helm spits out
NAME:   myapp-prod
Error: getting deployed release "myapp-prod": release: "myapp-prod" not found

All of the resources are created correctly and the app is running just fine. After this I cannot manage the release with helm anymore as helm just says "release my app-prod not found".
I believe this started after I upgraded to helm 2.10.0
GKE version
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.7", GitCommit:"dd5e1a2978fd0b97d9b78e1564398aeea7e7fe92", GitTreeState:"clean", BuildDate:"2018-04-19T00:05:56Z", GoVersion:"go1.9.3", Compiler:"gc", Platfo
rm:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10+", GitVersion:"v1.10.6-gke.2", GitCommit:"384b4eaa132ca9a295fcb3e5dfc74062b257e7df", GitTreeState:"clean", BuildDate:"2018-08-15T00:10:14Z", GoVersion:"go1.9.3b4", Compiler:"
gc", Platform:"linux/amd64"}

Helm version
Client: &version.Version{SemVer:"v2.10.0", GitCommit:"9ad53aac42165a5fadc6c87be0dea6b115f93090", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.10.0", GitCommit:"9ad53aac42165a5fadc6c87be0dea6b115f93090", GitTreeState:"clean"}

This makes it so the only way I can upgrade my release is to manually delete all the resources then run the broken helm install again. Helm upgrade --install has the same behavior.

This makes it so the only way I can upgrade my release is to manually delete all the resources then run the broken helm install again.

Is this intermittent (meaning this happens seemingly random) or consistent (happens every deploy)? Can you check tiller's logs and see what's the output there?

Happens every time. Seems that my configmap is too long?
create: failed to create: ConfigMap "taskhero-prod.v1" is invalid: []: Too long: must have at most 1048576 characters
That doesn't make sense because I haven't changed my chart since upgrading helm. This worked fine in whatever version I was using previously. Maybe a 1 or 2 line change, but thats it.
Tiller logs
[main] 2018/09/01 17:25:42 Starting Tiller v2.10.0 (tls=false)
[main] 2018/09/01 17:25:42 GRPC listening on :44134
[main] 2018/09/01 17:25:42 Probes listening on :44135
[main] 2018/09/01 17:25:42 Storage driver is ConfigMap
[main] 2018/09/01 17:25:42 Max history per release is 0
[tiller] 2018/09/01 17:26:52 preparing install for taskhero-prod
[storage] 2018/09/01 17:26:52 getting release history for "taskhero-prod"
[tiller] 2018/09/01 17:26:52 rendering taskhero chart using values
2018/09/01 17:26:52 info: manifest "taskhero/charts/nginx-ingress/templates/controller-hpa.yaml" is empty. Skipping.
2018/09/01 17:26:52 info: manifest "taskhero/charts/nginx-ingress/templates/udp-configmap.yaml" is empty. Skipping.
2018/09/01 17:26:52 info: manifest "taskhero/charts/nginx-ingress/templates/controller-stats-service.yaml" is empty. Skipping.
2018/09/01 17:26:52 info: manifest "taskhero/charts/redis/templates/secrets.yaml" is empty. Skipping.
2018/09/01 17:26:52 info: manifest "taskhero/charts/nginx-ingress/templates/controller-daemonset.yaml" is empty. Skipping.
2018/09/01 17:26:52 info: manifest "taskhero/charts/redis/templates/pvc.yaml" is empty. Skipping.
2018/09/01 17:26:52 info: manifest "taskhero/charts/nginx-ingress/templates/tcp-configmap.yaml" is empty. Skipping.
2018/09/01 17:26:52 info: manifest "taskhero/charts/nginx-ingress/templates/headers-configmap.yaml" is empty. Skipping.
2018/09/01 17:26:52 info: manifest "taskhero/charts/nginx-ingress/templates/controller-metrics-service.yaml" is empty. Skipping.
2018/09/01 17:26:52 info: manifest "taskhero/charts/redis/templates/networkpolicy.yaml" is empty. Skipping.
[tiller] 2018/09/01 17:26:52 performing install for taskhero-prod
[tiller] 2018/09/01 17:26:52 executing 0 crd-install hooks for taskhero-prod
[tiller] 2018/09/01 17:26:52 hooks complete for crd-install taskhero-prod
[tiller] 2018/09/01 17:26:52 executing 0 pre-install hooks for taskhero-prod
[tiller] 2018/09/01 17:26:52 hooks complete for pre-install taskhero-prod
[storage] 2018/09/01 17:26:52 getting release history for "taskhero-prod"
[storage] 2018/09/01 17:26:52 creating release "taskhero-prod.v1"
[storage/driver] 2018/09/01 17:26:56 create: failed to create: ConfigMap "taskhero-prod.v1" is invalid: []: Too long: must have at most 1048576 characters
[tiller] 2018/09/01 17:26:56 warning: Failed to record release taskhero-prod: ConfigMap "taskhero-prod.v1" is invalid: []: Too long: must have at most 1048576 characters
[kube] 2018/09/01 17:26:56 building resources from manifest
[kube] 2018/09/01 17:26:56 creating 19 resource(s)
[tiller] 2018/09/01 17:26:56 executing 0 post-install hooks for taskhero-prod
[tiller] 2018/09/01 17:26:56 hooks complete for post-install taskhero-prod
[storage] 2018/09/01 17:26:56 updating release "taskhero-prod.v1"
[storage/driver] 2018/09/01 17:27:00 update: failed to update: configmaps "taskhero-prod.v1" not found
[tiller] 2018/09/01 17:27:00 warning: Failed to update release taskhero-prod: configmaps "taskhero-prod.v1" not found
[storage] 2018/09/01 17:27:01 getting last revision of "taskhero-prod"
[storage] 2018/09/01 17:27:01 getting release history for "taskhero-prod"

That is also a pretty cryptic error message. Why wouldn't helm fail and do nothing rather than actually creating my resources and then leaving the release in a broken state?

Too long: must have at most 1048576 characters

That error means that the configmap release data went over the 1MB limit. Usually that means the chart packaged some extra files that doesn't need to be packaged up. Try adding a .helmignore file that removes any files that should not be part of the chart (you can inspect via helm package, then inspecting the tarball for what was included in the package). Let me know if that works for you.
I agree that the error's fairly cryptic. Feel like taking a crack at bubbling that error up to the client? :)

Looks related to #1413 and #1996
My experience level with helm and Kubernetes is "newbie" so I doubt I would be able to fix this issue properly. From what I understand from the other issues the 1mb limit is an upstream Kubernetes thing. Is that restriction going to be lifted in a future Kubernetes release? It seems a little arbitrary and restrictive

I got rid of some stuff I didn't need, brining the chart down to 87kb unzipped and the issue still persists.

I ran my install command with --dry-run --debug > debug.txt
The txt file is 2kb. Not sure what is going wrong here.

🤦♂ I had accidentally downloaded the fly binary from my concourse installation to my char directly. The fly binary was 15mb. Sorry for the inconvenience! Dumb mistake!

Wanted to thank Andrew for the clue that tipped me into solving this on my system.
Just like him, everything worked fine until it didn't...   Just wanted to add to this and explain what solved the problem for me.  I was making a bunch of timestamped backups of a values.yaml file each time I did a helm upgrade to the component I was modifying.  After awhile I had dozens of these timestamped backup yaml files that were about 80k each.  They added up to push over the 1 Meg limit, so I no longer keep my backups in that release folder and I deleted a bunch of them - so definitely check the total size of your component chart release folder and see if it is over the limit mentioned in this thread.

This was a huge help! I have a project structure with an overarching helm chart and all of my microservices under an images directory with their own helm installs.  Adding images to my .helmignore seemed to solve it.

adding .git into my .helmignore fixed this for me. My git history was 3.4MB :grimacing:


Releases missing in changelog on pocoo.org

http://werkzeug.pocoo.org/docs/0.11/changes/ is missing all releases since 0.11

Per-release docs are currently per-tag. I hope this situation will improve when we switch to RTD. Unfortunately a few organizational things have to happen before that.


Closes: #1 Updated validations.py python script with a new check.

Added a new check if first symbol is a letter with .isalpha()
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

@googlebot I signed it!


Does this compile and run on Android?

I'm very familiar with writing Android app, but not much with Java app. So I'd like to ask if this code can be compiled and run in an Android project?

Android compatibility was not a goal. I believe the use of lambdas and other jdk8 features preclude its use on Android, but I'm no expert on that matter.

@torinnguyen @beowulfe
Android 7 support java8.
I have tried to use this lib with Android, compile passed, but iOS device can not find the bridge.
Maybe due to network permission or other..
@torinnguyen
Do you have any other method make HAP compatible with Android?
Thanks.
06-22 16:46:58.548 31853-31872/? I/System.out: The PIN for pairing is 031-45-151
06-22 16:46:58.564 31853-31872/? W/System.err: [Thread-2] INFO com.beowulfe.hap.HomekitRoot - Added accessory Test Bridge
06-22 16:46:58.564 31853-31872/? W/System.err: [Thread-2] INFO com.beowulfe.hap.HomekitRoot - Added accessory Test Lightbulb
06-22 16:46:58.622 31853-31872/? I/MainActivity: run:
06-22 16:46:58.623 31853-31882/? W/System.err: [nioEventLoopGroup-2-1] INFO io.netty.handler.logging.LoggingHandler - [id: 0xcadc7fa8] REGISTERED
06-22 16:46:58.623 31853-31882/? W/System.err: [nioEventLoopGroup-2-1] INFO io.netty.handler.logging.LoggingHandler - [id: 0xcadc7fa8] BIND(::/:::9123)
06-22 16:46:58.624 31853-31882/? W/System.err: [nioEventLoopGroup-2-1] INFO com.beowulfe.hap.impl.http.impl.NettyHomekitHttpService - Bound homekit listener to /:::9123
06-22 16:46:58.624 31853-31882/? W/System.err: [nioEventLoopGroup-2-1] INFO com.beowulfe.hap.impl.jmdns.JmdnsHomekitAdvertiser - Advertising accessory Test Bridge
06-22 16:46:58.624 31853-31882/? W/System.err: [nioEventLoopGroup-2-1] INFO com.beowulfe.hap.impl.jmdns.JmdnsHomekitAdvertiser - Registering _hap._tcp.local. on port 9123


net: l2: ieee802154: standardize RSSI value

The RSSI value in net_pkt (net_pkt_cb_ieee802154.rssi) was used inconsistently across drivers. Some drivers did cast a signed dBm value directly to net_pkt's unsigned byte value. Others were assigning the negative value of the signed dBm value and again others were offsetting and stretching the signed dBm value linearly onto the full unsigned byte range.
This change standardizes net_pkt's rssi attribute to represent RSSI on the RX path as an unsigned integer ranging from 0 (–174 dBm) to 254 (80 dBm) and lets 255 represent an "unknown RSSI" (IEEE 802.15.4-2020, section <IP_ADDRESS>). On the TX path the rssi attribute will always be zero. Out-of-range values will be truncated to max/min values.
The change also introduces conversion functions to and from signed dBm values and introduces these consistently to all existing call sites. The "unknown RSSI" value is represented as INT16_MIN in this case.
In some cases drivers had to be changed to calculate dBm values from internal hardware specific representations.
The conversion functions are fully covered by unit tests.
Fixes: #58494

A suggestion as well, can you please add your GitHub UserID (and mine as well for that matter) under collaborators for Drivers: IEEE 802.15.4? As long as there are no objections.

Added a (tentative) commit as suggested by @cfriedt . Maintainer/reviewers - pls object and I'l remove the commit again.

Just adding a DNM for now until v3.4.0 is tagged

@cfriedt Inspired by your comments also fixed some magic RSSI values in CCxxxx drivers.


fix: AppBar does not fit theme

What

Fixes the elevation of AppBar in the history tab.

Impacted files

product_list_page.dart

Screenshot

Before

After

Fixes bug

#1172

I believe the best practice is to modify the theme data as the theme of AppBar is the same for the remaining tabs. Since this issue involves only with history tab, I have made the changes specifically.

Yes sure @GowthamGoush we should definitely do that later, but for now this is good enough


Refactor Spark accessor and add type annotations.

Separates SparkIndexOpsMethods into SparkSeriesMethods and SparkIndexMethods and adds type annotations.

Codecov Report

Merging #1859 into master will decrease coverage by 2.76%.
The diff coverage is 95.55%.

@@            Coverage Diff             @@
##           master    #1859      +/-   ##
==========================================
- Coverage   94.15%   91.38%   -2.77%
==========================================
  Files          40       40
  Lines        9772     9683      -89
==========================================
- Hits         9201     8849     -352
- Misses        571      834     +263

Impacted Files
Coverage Δ

databricks/koalas/base.py
97.32% <80.00%> (-0.61%)
:arrow_down:

databricks/koalas/indexes.py
97.22% <100.00%> (-0.05%)
:arrow_down:

databricks/koalas/series.py
95.53% <100.00%> (-1.33%)
:arrow_down:

databricks/koalas/spark/accessors.py
92.24% <100.00%> (-0.38%)
:arrow_down:

databricks/koalas/usage_logging/__init__.py
25.66% <0.00%> (-66.65%)
:arrow_down:

databricks/koalas/usage_logging/usage_logger.py
47.82% <0.00%> (-52.18%)
:arrow_down:

databricks/koalas/__init__.py
71.66% <0.00%> (-18.34%)
:arrow_down:

databricks/conftest.py
89.83% <0.00%> (-10.17%)
:arrow_down:

databricks/koalas/spark/functions.py
88.88% <0.00%> (-7.41%)
:arrow_down:

databricks/koalas/accessors.py
86.13% <0.00%> (-6.94%)
:arrow_down:

... and 16 more

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 0036768...7ce0598. Read the comment docs.


feat: Use LambdaWorks' FieldElement in stark-felt crate

This PR implements the current api in the stark-felt crate using the LambdaWorks library

Can you make sure that it's no std compatible (i see some std imports).
More generally this crate aims to be used by everyone so can you please guide the devs to use the most performant functions plz (if they are all as performant as each other can you state it also).

Hello! Thanks for the review!
Regarding no-std: I found some imports were missing for no-std so I added them in (41d8e81), and made sure I could compile a no-std project importing stark-felt. I couldn't find any explicit std-imports not gated behind the "std" feature, could you expand on this?
Regarding the comments on the arbitrary module: I added some small comments indicating that they are used to generate values for proptests. Is this clear enough or should I add examples / a link to the proptest documentation? This is also a private module, so end users shouldn't have to worry about it.
Regarding performance of certain methods: I ran some micro-benchmarks and wasn't able to find any substancial difference between them. I think it's a good idea to add benchmarks to the crate, so end users can gauge the performance themselves instead of relying on the documentation

Regarding performance of certain methods: I ran some micro-benchmarks and wasn't able to find any substancial difference between them. I think it's a good idea to add benchmarks to the crate, so end users can gauge the performance themselves instead of relying on the documentation

I think the comment was more referring to which of those representations is actually the same as the inner type. i.e. does the field element store big endian or little endian? Or is it some other representation internally. While this does "leak" the inner workings a bit, it might be meaningful for those chasing to save instructions.
For example, in pathfinder we store felts as big endian in the database only because our field element uses big endian under the hood so its a no-op to convert.
Whether or not this actually matters is of course debatable :)


Sign in

The app is installed and then when I attempt to launch, it asked me to "log in" but will to log in.  I get the following error:
Request Id: 73cb1fe2-42ae-49cc-8bed-62623501cf00
Correlation Id: a48e6314-e347-46ab-b73a-5fa996496547
Timestamp: 2023-06-14T18:47:39Z
Message: AADSTS700016: Application with identifier '50f9fe1f-b469-446f-8132-5df6416db0e9' was not found in the directory 'Contoso'. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You may have sent your authentication request to the wrong tenant.

Hi @jhuard12,
Thanks for reaching out to us. I believe there might be some issue with the client id/tenant id configuration in the resource group. Can you please go through all the steps from the deployment guide once and make sure all the values from the app registration are correctly configured in the resource group (Configuration in the app service and simpleAuth app service)?


Issue with bash not showing the commit details in Fork

Just recently, I noticed that Fork was not showing the 'Commit/Changes/File Tree' pane, with an error message:
/bin/bash: !--RevisionMessageEnd--; No such file or directory
At first, I thought that the issue is with Fork, so I tried reinstall Fork, but the issue still persist.
The message disappeared only when I changed the Git Instance under preference to the default git that was include with the app.
So it's suggesting to me that the issue is with the wslgit symlink.

I'm using Fork Version 1.80
Hope you can help me,
Thanks

Just updated to Fork 1.80 and got the same problem :/

The problem is that Fork changed one argument to --pretty=format:%H±.%aN±.%aE±.%at±.%cN±.%cE±.%ct±.%P±.%B<!--RevisionMessageEnd-->, and bash don't like unescaped <, ! and >. I have implemented a fix that I'm testing now.

Same problem, did same steps, so I'm also assuming the issue is with wslgit

@carlolars seems like a promising fix. I tried to test it, but there's no release in your fork repo (yet), so I tried to build the package but it seems I'm missing a build script for the wslgit.exe file.
I guess I'll wait for your PR, unless there's something I can help with?

Hi! I'm sorry for making problems for you.

The problem is that Fork changed one argument to --pretty=format:%H±.%aN±.%aE±.%at±.%cN±.%cE±.%ct±.%P±.%B<!--RevisionMessageEnd-->, and bash don't like unescaped <, ! and >. I have implemented a fix that I'm testing now.

Yes, I confirm that. I didn't know that particular message could cause an issue.

I'm having the same issue here...

@DanPristupov Is there a way to get the old release for Fork (< 1.80) somewhere temporarily? I didn't find a page for them on https://git-fork.com.

@sneakyvv
You can download Fork 1.79 here (https://cdn.fork.dev/prerelease/ForkInstaller-1.79.exe), but you must disable the update. You must be very quick , otherwise Fork will check and install 1.80 already.

There is now a test build of wslgit with the fix by @carlolars available for download.

You guys are both stars! 🤘
Can confirm it works on Fork 1.80 now 🎉

Confirming that the test build works for Fork 1.80, 1.71 and 1.78 :)
You guys are awesome!
Thanks so much!

@sneakyvv You can download Fork 1.79 here (https://cdn.fork.dev/prerelease/ForkInstaller-1.79.exe), but you must disable automatic updates. You must be very quick , otherwise Fork will check and install 1.80 already.

This is the same thing I did. After downloading the installer, I disabled my WiFi, then proceed to setting it up (and most importantly disable automatic updates). :)

@carlolars @andy-5 will that be better if we change the separator to --RevisionMessageEnd-- in the next update?

There is now a test build of wslgit with the fix by @carlolars available for download.

New wslgit (1.2.0-alpha3) doesn't work for me. Now I am getting fatal: unrecognized argument: --diff-merges=1

@MichalGow Yes, the --diff-merges=1 flag seems to be a quite recent addition to git. I think you need at least version 2.31. There is nothing wslgit can do about that.
@DanPristupov I think there is no need to change the separator, now that wslgit can properly escape the special characters.

I also ran into this issue and the steps described here fixed it:

Downloaded the test version of wslgit mentioned by @andy-5
Upgraded WSL git instance to latest

The changes to fix this are now released as wslgit v1.2.0.


CSS grid doesn't support word-wrap, overflow-wrap and hyphens properties

Long words don't break to the next line where template column widths are defined with fr units
Codepen #1: (word-wrap / overflow-wrap)
Codepen #2: (hyphens)
Workarounds:

use minmax() function instead of fr units. eg:

grid-template-columns: minmax(0, 1fr); instead of
grid-template-columns: 1fr;

use the word-break property
For chrome: word-break: break-word is sufficient, but firefox requires word-break: break-all - which has the unwanted effect of breaking words in the middle.

For reference, see: https://stackoverflow.com/questions/51253050/css-grid-grows-over-100-width-with-fr-but-not-with-minmax

+1
Thanks for the workaround Daniel!


docker sync stop working

Hi
Mam problem z synchronizacją wagi poprzez docker, the last measurements sent to gramin are from September 25, 2023, now when I try to start synchronization I have the following message:
2023-10-02 09:33:51,335 - withings - INFO - Refresh Access Token
2023-10-02 09:33:51,655 - root - INFO - Fetching measurements from 2023-10-02 05:00 to 2023-10-02 23:59
2023-10-02 09:33:51,993 - withings - INFO - Get Measurements
2023-10-02 09:33:52,329 - root - ERROR - No measurements to upload for date or period specified
but I have a weight measurement today at 5:53. Everything was fine until September 25.
--
Is it possible to synchronize a day other than today?

Same for me, working until Sept 25th. No change to my garmin username or password.
2023-10-02 11:04:57,955 - urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): connect.garmin.com:80
2023-10-02 11:04:57,993 - urllib3.connectionpool - DEBUG - http://connect.garmin.com:80 "GET /modern HTTP/1.1" 301 None
2023-10-02 11:04:58,143 - urllib3.connectionpool - DEBUG - https://connect.garmin.com:443 "GET /modern HTTP/1.1" 302 0
2023-10-02 11:04:58,300 - urllib3.connectionpool - DEBUG - https://connect.garmin.com:443 "GET /signin/?service=https%3A%2F%2Fconnect.garmin.com%2Fmodern%2F HTTP/1.1" 200 None
2023-10-02 11:04:58,302 - garmin - ERROR - 'NoneType' object is not subscriptable
2023-10-02 11:04:58,302 - garmin - ERROR - Unable to retrieve Garmin username! Most likely: incorrect Garmin login or password!

Upgrade to v4.0.0

I pulled latest docker image and no change :(. How to check version of docker image?

@longstone the Garmin connect outage yesterday caused some interesting issue.   During some of my tests I noticed that the Garmin connection received a timeout, but the "last_sync" value in /root/.withings_user.json was set anyways.   I guess the logic should receive an update to avoid that.
Today all is well again, both weight and blood pressure values are synced.

@hawkeye583 try docker inspect withings-sync | grep "org.opencontainers.image.version"
This should return "v4.0.0" for now.  If this is the case make sure the container with that version is actually running.

@stynoo i have this: "org.opencontainers.image.version": "nightly"

Do we even push nightly builds?

I've tried running it manually (not on Docker) and also not working.
withings-sync -v -f 2023-09-26 --gu XXXXXX --gp YYYYYYY

@stynoo sorry for the stupid question, but how to do it from docker?

You open a shell with docker exec and start the process manually.

I've tried running it manually (not on Docker) and also not working.
withings-sync -v -f 2023-09-26 --gu XXXXXX --gp YYYYYYY

Can you at least share the part of the log where it goes wrong?

Sorry it's in the second comment earlier but here is more of the log file.
2023-10-02 12:42:52,497 - root - DEBUG - Generating fit data...
2023-10-02 12:42:52,498 - root - INFO - No blood pressure data to sync for FIT file
2023-10-02 12:42:52,498 - root - DEBUG - Fit data generated...
2023-10-02 12:42:52,498 - root - DEBUG - Generating json data...
2023-10-02 12:42:52,499 - root - DEBUG - Json data generated...
2023-10-02 12:42:52,499 - root - INFO - No TrainerRoad username or a new measurement - skipping sync
2023-10-02 12:42:52,499 - root - DEBUG - attempting to upload fit file...
2023-10-02 12:42:52,536 - urllib3.connectionpool - DEBUG - Starting new HTTPS connection (1): sso.garmin.com:443
2023-10-02 12:42:52,878 - urllib3.connectionpool - DEBUG - https://sso.garmin.com:443 "GET /sso/signin?service=https%3A%2F%2Fconnect.garmin.com%2Fmodern&clientId=GarminConnect&gauthHost=https%3A%2F%2Fsso.garmin.com%2Fsso&consumeServiceTicket=false HTTP/1.1" 200 None
2023-10-02 12:42:53,795 - urllib3.connectionpool - DEBUG - https://sso.garmin.com:443 "POST /sso/login?service=https%3A%2F%2Fconnect.garmin.com%2Fmodern&clientId=GarminConnect&gauthHost=https%3A%2F%2Fsso.garmin.com%2Fsso&consumeServiceTicket=false HTTP/1.1" 200 None
2023-10-02 12:42:53,805 - urllib3.connectionpool - DEBUG - Starting new HTTPS connection (1): connect.garmin.com:443
2023-10-02 12:42:54,130 - urllib3.connectionpool - DEBUG - https://connect.garmin.com:443 "GET /modern HTTP/1.1" 302 0
2023-10-02 12:42:54,339 - urllib3.connectionpool - DEBUG - https://sso.garmin.com:443 "GET /sso/login?service=https%3A%2F%2Fconnect.garmin.com%2Fmodern%2F&webhost=https%3A%2F%2Fconnect.garmin.com&gateway=true&generateExtraServiceTicket=true&generateTwoExtraServiceTickets=true&clientId=GarminConnect HTTP/1.1" 302 0
2023-10-02 12:42:54,500 - urllib3.connectionpool - DEBUG - https://connect.garmin.com:443 "GET /modern/ HTTP/1.1" 302 0
2023-10-02 12:42:54,651 - urllib3.connectionpool - DEBUG - https://connect.garmin.com:443 "GET /signin/?service=https%3A%2F%2Fconnect.garmin.com%2Fmodern%2F HTTP/1.1" 200 None
2023-10-02 12:42:54,656 - urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): connect.garmin.com:80
2023-10-02 12:42:54,694 - urllib3.connectionpool - DEBUG - http://connect.garmin.com:80 "GET /modern HTTP/1.1" 301 None
2023-10-02 12:42:54,843 - urllib3.connectionpool - DEBUG - https://connect.garmin.com:443 "GET /modern HTTP/1.1" 302 0
2023-10-02 12:42:54,996 - urllib3.connectionpool - DEBUG - https://connect.garmin.com:443 "GET /signin/?service=https%3A%2F%2Fconnect.garmin.com%2Fmodern%2F HTTP/1.1" 200 None
2023-10-02 12:42:54,998 - garmin - ERROR - 'NoneType' object is not subscriptable
2023-10-02 12:42:54,999 - garmin - ERROR - Unable to retrieve Garmin username! Most likely: incorrect Garmin login or password!
2023-10-02 12:42:54,999 - garmin - DEBUG - To sign in to your Garmin account, please enable JavaScript in your web browser.

2023-10-02 12:42:55,193 - urllib3.connectionpool - DEBUG - https://connect.garmin.com:443 "POST /modern/proxy/upload-service/upload/.fit HTTP/1.1" 403 None
2023-10-02 12:42:55,196 - garmin - ERROR - Bad response during GC upload: 403

Upgrade to v4.0.0

@kissanej you are still running an older version.

ok when i run --fromdate 2023-09-25 it synced all data :) , so i have one more question why sync period for today is from 05:00 to 23:59? It looks like my data from 5:55 is not included in this period.

Upgrade to v4.0.0

@kissanej you are still running an older version.

Thank you, that has sorted it out.


[TF2.0] Bug when export BatchNormalization layer

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Linux Ubuntu 18.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary):
binary
TensorFlow version (use command below):
2.0.0-beta0
Python version:
python 3.6.8
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
cuda 10,
GPU model and memory:
GTX 1080ti

Describe the current behavior
W0708 11:01:14.168962<PHONE_NUMBER>57472 saved_model.py:721] Skipping full serialization of
object <tensorflow.python.keras.layers.normalization_v2.BatchNormalization object at
0x7f61c004a978>, because an error occurred while tracing layer functions. Error message:
Expected Operation, Variable, or Tensor, got None

Describe the expected behavior
There should be no error message.
Code to reproduce the issue
import tensorflow as tf
from tensorflow.keras.layers import BatchNormalization

class BNModel(tf.Module):

    def __init__(self):
        super(BNModel, self).__init__()
        self.bn = BatchNormalization()

    @tf.function(input_signature=[tf.TensorSpec([None, 2], tf.float32)])
    def __call__(self, x):
        return self.bn(x)

if __name__ == '__main__':
    module = BNModel()
    import numpy as np
    arr = np.random.randn(2,2)
    module(arr)
    signatures = {"serving_default": module.__call__}
    tf.saved_model.save(module, "saved_models", signatures=signatures)

Other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

Was able to reproduce the reported issue with Tensorflow 2.0.0.beta0 and It works as expected with Tenosrflow 2.0.0.beta1. Thanks!

My problem is solved. Thank you very much.  @gadagashwini


Symfony3 compatibility

Hi,
Is the compatibility for Symfony 3 planned ?
Thanks,
Julien

Hi @pesseyjulien,
yes, I just need some spare time,
anyway if you want to send a PR it would be great!

Thanks for your answer.
I could try to help but there is actually no deprecated calls logged in the profiler.
Composer just throws an error when trying to update to SF3. It seems like the requirements for the bundle are not met by SF3. Anyway, not sure where to look :)

@pesseyjulien updated the dependencies allowing PHP7 too.
I'm closing this issue, reopen it if there's something wrong,
thanks :)

Great, thanks Emanuele ! :)

Le 12 mars 2016 à 15:17, Emanuele Minotto<EMAIL_ADDRESS>a écrit :
@pesseyjulien https://github.com/pesseyjulien updated the dependencies allowing PHP7 too.
I'm closing this issue, reopen it if there's something wrong,
thanks :)
—
Reply to this email directly or view it on GitHub https://github.com/nibsirahsieu/SalvaJshrinkBundle/issues/19#issuecomment-195749470.


fix(@embark/test-runner): don't try to deploy and register ENS domains after JS tests have run

When running unit tests inside a project that configures ENS subdomains using Smart Contract directives, the tests will output an error because of that particular Smart Contract's deployedAddress being undefined.
This happens only when running tests, not when deploying the Smart Contracts including the custom ENS setup.
It turns out that Embark attempts to compile and deploy the Smart Contracts of the project twice - once before tests are executed, and another time after tests are done executing.
Both compilations/deployments are triggered through our custom config() function within test context, which ensures all Smart Contracts are deployed before tests are executed.
This explains a few things:

There's no such issue when running embark run, in fact the custom ENS subdomains work perfectly fine
That's also why the tests are passing fine as well as the first compilation/deployment doesn't have any issues. The errors only appear after the tests have been executed.

Still, this raises a few more questions, mainly

Why is the Smart Contract's deployedAddress property undefined when config() is executed a second time?
Why is config() executed a second time in the first place?

Let's look into both of these.
Assuming that there's a valid reason that config() is called twice, it's remains unclear why that property of a Smart Contract object is undefined in the second run. The reason for that is that Embark determines whether or not a particular Smart Contract should be deployed. One of the routines ensures that only the Smart Contracts configured for deployment are actually attempted to be deployed (as opposed to just deploying all Smart Contracts found in the file system).
It turns out that the second config() call is done without any Smart Contract configuration, resulting basically in no deployment for any Smart Contract of the application. The address and deployedAddress of a Smart Contract object are however only set after deployment, resulting in them being undefined.
All this makes sense.
config() is simply not designed for being used with an empty contracts: {} config. This raises another question:
Why is config() called with an empty configuration? This leads us to the second point.
It does seem a bit weird that Embark tries to configure compile and deploy a DApp's Smart Contracts again right after the tests have been executed. So why is that?
A quick git blame (no blame intended here) shows us that this routine has been introduced in https://github.com/embark-framework/embark/commit/12cbb7bdd.
Notice the second list point of the commit:

Contracts that had been compiled in the JS tests were being deleted at the end of the JS test run, which caused errors with the files not being found. The fix was to reset the contracts config to no longer require the non-test contracts to be compiled/deployed.

The above is a little tricky to understand without a little bit of context: Embark runs two types of tests, JavaScript tests and Solidity tests. It does that as part of a single process, keeping state in memory in-between those two test runs.
With that in mind, the commit mentioned above says the following:

Artifacts that Embark generates as part of its compilation process are erased after JS tests are done executing. This makes a lot of sense as we don't want to leave any side effects undone when tests are finished.

The commit ensures that not only the artifacts are removed from disc, but also updates Embark's state in memory for contractFiles. The reason for that is that otherwise, in the second test run for Solidity tests, Embark will throw errors as it tries to look up the path for the artifacts in memory for all the Smart Contracts that had been compiled before.

Last but not least, there's another state that needs a reset and that's the Smart Contract configuration. If Embark doesn't reset the memory it'll assume in the second run that all of those Smart Contracts left in memory "have no code associated to it", while in reality, they shouldn't be in memory in the first place.

So it seems that config() is called a second time with an empty Smart Contracts configuration just to ensure that memory is reset and no error messages are shown.
As discussed earlier, this unfortunately also introduced a lot of side effects along the way as Embark tries to reregister ENS subdomains from Smart Contracts that are marked as undeployed and therefore don't have an address to interpolate.
While there's probably different ways to go about it, the most straight forward fix is to simply not call config() a second time when it's really not needed. If the goal is to just reset the memory, we can take advantage of Embark's internal config:contractsConfig:set event, which is what this commit is doing.

Excellent write-up! Thanks @PascalPrecht!


add Netbeans 11.3

Microsoft Reviewers: Open in CodeFlow

I am blocked on this at the moment https://github.com/microsoft/winget-cli/issues/247


response middleware override issue

Hi,
Adding the response middleware the way you did stops others from modifying headers in their own code via the response middleware.
Perhaps you could make use of PyDispatcher or Blinker or similar to allow a producer consumer relationship and allow joint use of the response middleware?

@subyraman
Since I can't push my branch up to this repo, I will just show my changes in __init__.py
Original:
@app.middleware('response')
async def compress_response(request, response):
    return (await self._compress_response(request, response))

Updated:
async def compress_response(request, response):
    return (await self._compress_response(request, response))

# Append the compress response to the end of
# the list of response middlewares
app.response_middleware.append( compress_response )

The updated one pass all the tests, and works as expected on my application.
Would you kindly update it? Else I will just fork it, and update on my own repo


Move some recipes over from the book, and add empty files for those yet to be moved

@bluebandedgobi

:+1:


Switch from Travis CI to GitHub Actions

Other than updating the tutorial TOC, the dev website already looks good!
A few notes:

We could review the roadmap to see if there is anything we want to update for 2021.
I was tempted to remove the talk but have opted not to because 1) it looks like it all still works 2) it mostly covers .hvplot which is still a suitable entry point. @jbednar if you want to change anything about the talk (perhaps just the very end that still uses interact?) then we can easily rebuild the site.

Seems to be working well! Merging.


Add reference to central entities table in new rule eval history tables

Summary
This starts populating the relevant data so we can migrate to using the
central table in a further increment. Note that this is merely adding data
and not changing any logic as of yet. The idea is to start populating
and get us to a point where we can remove the NULL constraint.
Fixes https://github.com/stacklok/minder/issues/4170
Change Type
Mark the type of change your PR introduces:

[ ] Bug fix (resolves an issue without affecting existing features)
[x] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[ ] Refactoring or test improvements (no bug fixes or new functionality)

Testing
Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.
Review Checklist:

[x] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[ ] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

coverage: 53.84% (+0.006%) from 53.834%
when pulling ac7be0a15c441e6628674d9818938c7ad39181ed on evals-central-entities
into 7b9db0dddedf6c45934b904d95faabe23648a548 on main.


added rng_guide

Added RNG guide. View preview here.
Follow-up questions:

should we add a section to show how to split RNG's using pmap?
should we add an additional example using nn.scan for sequential models and modifying the variable_broadcast arg?
should the rng guide be placed under the "Flax fundamentals" section, or somewhere else like "Developer notes"?

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (70214f4) 52.98% compared to head (6d1f4dd) 52.98%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3497   +/-   ##
=======================================
  Coverage   52.98%   52.98%
=======================================
  Files          94       94
  Lines       11206    11206
=======================================
  Hits         5937     5937
  Misses       5269     5269

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

should we add a section to show how to split RNG's using pmap?

I think the vmap example is close enough.

should we add an additional example using nn.scan for sequential models and modifying the variable_broadcast arg?

I don't think its necessary, shouldn't change the rng-related behavior.

should the rng guide be placed under the "Flax fundamentals" section, or somewhere else like "Developer notes"?

I'd vote for "Flax fundamentals".

cc: @froystig


More projects

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

Merging [#313][cc-pull] into [master][cc-base-branch] will decrease coverage by 0.10%

[][cc-pull]

Powered by Codecov. Last updated by [ab0ff4b...3c5a5d8][cc-compare]
[cc-base-branch]: https://codecov.io/gh/travisbrown/circe/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/travisbrown/circe/compare/ab0ff4b597ab87f3eccb886646a368e09a1a008a...3c5a5d8d6fc6862f63d25a4da185dff934d18fed
[cc-pull]: https://codecov.io/gh/travisbrown/circe/pull/313?src=pr


[Question]:

Please check the following before submitting a new issue.

[X] I have searched the existing issues.
[X] I have carefully read the documentation.

Please select for which platform(s) you need help

[X] Android
[ ] iOS
[ ] Linux
[ ] macOS
[ ] Web
[ ] Windows

Your question
I ran some Android phones and found few error:
unable to connect to service: com.google.android.location.internal.GoogleLocationManagerService.START on com.google.android.gms.
The service for com.google.android.gms.common.internal.service.zap is not available: ConnectionResult{statusCode=SERVICE_VERSION_UPDATE_REQUIRED, resolution=null, message=null}
Version
10.1.0

Can you provide more details please? Questions I have are:

On which phones (brand, model, OS version) does this problem occur?
What is the output of the flutter doctor -v command?
Does this error happen at runtime or compile time?

I set the properties "forceAndroidLocationManager: true", but I found that some Android phones do not return the latitude and longitude.

This is possible depending on the desiredAccuracy level you have set. Some points you might want to look into:

If the desiredAccuracy is set to LocationAccuracy.lowest, the location services will only return location updates if other apps actively requesting location updates. This is a special setting which reduces the battery usage (more details can be found in the Location accuracy section of the README).
If the desiredAccuracy is set to LocationAccuracy.high or better, the location services will only use the GPS provider to get location fixes. For this to work the device needs to have clear sight to the sky and means this usually doesn't work while inside of a building.

If you want us to help more detailed please provide the earlier requested information. On top of that example code is always very helpful as well.

I've solved this problem！static Future<Position?> getCurrentLocation(       {LocationAccuracy? accuracy}) async {     try {       var pos = await Geolocator.getCurrentPosition(           forceAndroidLocationManager: true,           timeLimit: const Duration(milliseconds: 500),           desiredAccuracy: accuracy ?? LocationAccuracy.high);       console.log("posotion:${pos.toJson()}");       return pos;     } catch (e) {       return Geolocator.getLastKnownPosition(forceAndroidLocationManager: true);     }   }


Fix false negative 'function used in fuzz targets'

Our current code automatically fails an LLM-generated fuzz target if it does not contain the function under test.
However, the current pattern-matching is native and has false negatives (i.e., function used correctly but not recognized by us), and rejects valid fuzz targets.
This relates to our function name parsing regex:
https://github.com/google/oss-fuzz-gen/blob/4e3a5ab4cc11df7dd4d99d57612c3c62c034975b/experiment/benchmark.py#L40-L43
A quick temporary solution is checking the function names without special chars.
Later we can make better use of data from FI

Could be related:
#89

Some tricky cases that are still not handled:

destructor: ~String()
overloaded operator: operator+()
Use of these functions can look completely different from their signature.

Also this example with ShallowClone():
https://llm-exp.oss-fuzz.com/Result-reports/ofg-pr/2024-02-13-97-dg-comparison/sample/output-tinyxml2-_znk8tinyxml210xmlelement12shallowcloneepns_11xmldocumente/01

I reckon you have already fixed this? @cjx10

I reckon you have already fixed this? @cjx10

Don't think we have a fix for this kind of functions

overloaded operator: operator+()

What kind of mismatch do we have?
E.g., 'fuzz target uses the correct function, but we think they did not', or 'fuzz target may used the incorrect function, but we cannot tell'.
The former is more problematic, but the latter is tolerable.

What kind of mismatch do we have?

The former.
Correct usage of operator functions does not have the keyword operator.
For example, to use a overloaded operator+(), it would be just class_obj1 + class_obj2

Ah I see, that is difficult to capture.
Is there any other cases like this in general?

Is there any other cases like this in general?

The two cases listed above are all that I've observed

That should be good for now, thanks!


Styling improvement

Great job! 👍
Your project is working fine, here I have some optional suggestions for you :

Styling improvement to make the project more visible.

Kindly personalise your README.md  file, this makes it easier yo find your profiles on LinkedIn, twitter and github.
I would suggest that you refrain from using keywords in your js file the 'filter' keyword to create a finction. This might cause unforeseen circumstances.

Great job , thank you and i will amend all

@Abdullah2213565 Thank you i will work on that


Install fails if database not-yet-created

Running bin/rails generate clearance:install when a database has not yet been created results in the following error:
rescue in connect': FATAL:  database "example_development" does not exist (ActiveRecord::NoDatabaseError)

Which traces back to this line in Clearance:
lib/generators/clearance/install/install_generator.rb:105:in users_table_exists?'`
This is sort of expected, but it would be nice if it were handled more elegantly. I can patch the users_table_exists? method to handle this case if someone can point me to an example of how Clearance prefers to write information back to the prompt.

How were you thinking of handling it?

I think the error as it's displayed is actually pretty good. It could be changed by rescuing NoDatabaseError and raising an exception with a better message (run rails db:create first or something) but even this has complications because versions of Rails < 5 would run rake db:create (which will also work on 5+ but may be confusing to people who find the original error confusing).


No supported way to build static binaries

Summary:
I am accessing my stan program from inside a docker container and would like the ability to compile it as a standalone binary, rather than having to include the associated libraries wherever it goes.
Description:
I am currently using cmdstan inside a docker container in a production environment. One of the problems I have is that when I build my cmdstan binaries and move them, I also have to make
move the entire cmdstan repo, rather than placing my stan binary in an alpine docker container
and being done with it. This means I'm also lugging around a git repository of the cmdstan and
stan code, and unnecessarily increase the size of my docker container. While some of my burden
not entirely necessary (I could just figure out what libraries it is loading and copy only those), it
would be nice if there were an option for cmdstan to produce a binary I could just plop in and forget about.
Current Version:
v2.21.0

Not quite understanding what you mean by a "standalone binary".
E.g. - you can compile file examples/bernoulli/bernoulli.stan via command:
> make examples/bernoulli/bernoulli

the resutling binary is a standalone program that you can copy or move as you wish.

Currently you have to link dynamically the Intel tbb to get a Stan program to work. As I understand you want to move a compiled Stan model into docker. The tbb is linked by default using rpath which hardcodes the tbb link path. You should be able to link the tbb yourself which can the place where you like. Does that make sense? It would be helpful if you provide a git repo with the Dockerfiles and its auxiliary files to run it.

For the purpose of this issue...we can close it, i think. There is no supported way to end up with a static binary. The only action one could take is to review the doc for having a running stan exectuable model with the minimal set of binaries which means to install the tbb.
@mitzimorris thoughts?

is it possible to use the math lib v 2.20 which doesn't include the Intel TBB?

I think that @hugbubby has a valid use case here and I think that we need to find a way to address this, so no, I don't think we should close this issue.

@hugbubby were you asking to deploy a single compiled model inside the
docker container? Or the entirety of cmdstan with its ability to compile
new models?
On Tue, Dec 10, 2019 at 08:20 Mitzi Morris<EMAIL_ADDRESS>wrote:

I think that @hugbubby https://github.com/hugbubby has a valid use case
here and I think that we need to find a way to address this, so no, I don't
think we should close this issue.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/stan-dev/cmdstan/issues/779?email_source=notifications&email_token=AAGET3DPHK5MNKAOEAH536DQX6JSNA5CNFSM4JYBTTBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGPGLLI#issuecomment-564028845,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGET3HZD5QKIUYI4AAA743QX6JSNANCNFSM4JYBTTBA
.

@wds15 Yes ,there is no supported way, which is why I am asking for a way.
@seantalts A single compiled model. I personally have no need to compile more models in my docker container, though I see why you might want to do that; I'm using the one I've created to do inference in a production environment, and don't want to have to lug around the whole git repo.

@hugbubby Well, you can use 2.20 if you want all static model binaries. With 2.21 and going forward there is no supported way for a fully static model binary. You will always have to link dynamically with the Intel TBB.
So what you can do is:

configure a TBB build by yourself (or you could just take the Intel binaries if these work for you)
setup cmdstan to use your provided TBB
then compile the model
place the model binary and the Intel TBB in the docker image

Would that work for you?

@hugbubby Well, you can use 2.20 if you want all static model binaries. With 2.21 and going forward there is no supported way for a fully static model binary. You will always have to link dynamically with the Intel TBB.
So what you can do is:
* configure a TBB build by yourself (or you could just take the Intel binaries if these work for you)

* setup cmdstan to use your provided TBB

* then compile the model

* place the model binary and the Intel TBB in the docker image

Would that work for you?

It works for a certain definition of work; why is there an insistence on demanding the binary be dynamically compiled? I can actually build a statically compiled binary by modifying the internal makefiles; I just created this issue because I'd like to see a configuration option in the local makefile to do this automatically.

The Intel TBB strongly discourages to be used as static library. They don’t even document how one can link statically against it. This is why we do not support it. I think we can close the issue. I am absolutely against going with static linking against the tbb given that is so much discouraged. That’s not my call.
I also don’t ses any issue with what I suggest. You endup getting a docker container with minimal binaries.

would it be possible to use an Intel docker container that supports TBB?
https://docs.nersc.gov/programming/shifter/intel/

would it be possible to use an Intel docker container that supports TBB?
https://docs.nersc.gov/programming/shifter/intel/

I made the decision to use Clear Linux docker containers for their speed and explicit support of TBB. This situation is not without difficulty; I now have to wait for heroku to build the stan binary from scratch every time a new version of the service is pushed, but doing a clean from-ground-zero build also retains its upsides from a consistency perspective.

Thanks for reporting back on your resolution of this and for closing the issue.  This issue will probably come up for others who want to fully encapsulate the Stan environment.

On Dec 23, 2019, at 6:50 PM, hugbubby<EMAIL_ADDRESS>wrote:
would it be possible to use an Intel docker container that supports TBB?
https://docs.nersc.gov/programming/shifter/intel/
I made the decision to use Clear Linux docker containers for their speed and explicit support of TBB. This situation is not without difficulty; I now have to wait for heroku to build the stan binary from scratch every time a new version of the service is pushed, but doing a clean from-ground-zero build also retains its upsides from a consistency perspective.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

I don’t see a resolution here (did I miss something?), and I don’t think the reasoning about dynamically linking TBB (link) applies here, since we’re talking about standalone executables.
In the discussion of reproducibility on discourse (link) it would be helpful to have a static binary to eliminate sources of variability (at least for CmdStan not brms), since the lack static binaries leads to use of variable container runtime systems (among other things).

I don’t see a resolution here (did I miss something?)

the resolution was this:

I made the decision to use Clear Linux docker containers for their speed and explicit support of TBB. This situation is not without difficulty; I now have to wait for heroku to build the stan binary from scratch every time a new version of the service is pushed, but doing a clean from-ground-zero build also retains its upsides from a consistency perspective.


docs: remove mention of the Angular CLI depending on Node 8

The official Angular documentation states that Angular requires Node.js version 10.9.0 or later. The README should align with that

Closing this PR in favour of #14635


Iron Mines issues

On a Valar turn, after selecting YES to save a character, iron mines is discarded and used to save but you are prompted if you want to use it for every other character as well. Once you click YES and use it, it should stop asking.
Or perhaps when there is more than one option, turn it into a chooser prompt and click the character you want to save so it only has to ask 1 question.

We currently have no way to stop events from propagating to other event handlers.  Until I rewrite this to be a possibility, this is going to be an annoyance during Valar.

Also if you have 2x Iron mines, and they prompt for the same character. When you press no for the second Iron Mines prompt the character dies. Also characters with Dupes are not in the list for saves you may want to save them with mines and not dupes in mass resets.

Same issue :)


StreetView hangs/freeze (black space)

Have an issue while use on Android
I should say, it doesn't occur every time I use street view in app.
I can definitely say - issue occurs after the route changed (so maybe it related with a component instantiation)
When street view stuck - I have next state (there is always a black line on top - it's absent when everything ok)

every time I change route (logout/login) and use streetView - the black space grows
but if app start from a route where streetView component situated - everything ok - it works
I use "react-native-router-flux": "3.39.2" for navigation

any comments, please... :)

For those who stack with this issue.
I moved to react-native-navigation, and this bug disappeared

Workaround available #12

@vitto-moz I’m using react-native-navigation and all I get is a black screen. Did you face this issue at all?

@chrise86, I've ended up with my own routing and I'm totally happy with it. But my suggestion for you is -
react-navigation
I think it's the best, comparing all available

@vitto-moz I've fixed the issue and have put a pull request in, if you ever need it.

@vitto-moz I’m using react-native-navigation and all I get is a black screen. Did you face this issue at all?

same issue for me any one got solved??


Make max redirects configurable

It would be nice if maxRedirects was configurable.

released as 1.1.13, thanks!


Feature drag and drop columns

Simple drag and drop ability is finished.
Placeholder poses can be dragged from one column to another, and can be dragged into a new order within a single column.
Columns have also been separated into components.

approved!  Nice work!


Separate plot from solve

Separate plotting features from solve so manipulation of the plots can happen without solving the model every time.

Yep gonna make a separate plot file. I'm working on printing the circuit right now


Code coverage

In our TypeScript code, we should add code coverage reporting.
It should be fairly straightforward to set up, as we're already using jest everywhere.

Fixed!


Added XLSX file support in export

Issue Reference
Added XLSX file support in export

@shivendra-webkul
Checked and Found that the PR is working fine, please make the changes which are mentioned.
Video
https://github.com/bagisto/bagisto/assets/92721837/f1ecc69d-79b5-4944-aafd-481355c8cac2


New Feature : Adding option for downloading multiple animated icons

Importing issues from old repo on Gitlab.
Created by: @Sanyam_Pandey

Currently, a user can only download one animated icons at a time . This feature will allow a user to select and download multiple animated icons at once.
video:
https://gitlab.com/SUSE-UIUX/eos-icons-landing/uploads/bdef2a8fe8fb05c188c63d20004e0c1b/screen-capture__3_.webm

I would like to work on this issue if it's available.

@chinmaym07 I've assigned you to the issue

@cyntss sir I would like to work on this issue if it's available.


Would you release the pretrained model?

Wonderful job!
Would you release the pretrained models?
Thank you!

seems like there are still no news?

Is this different from #21 ?

A new pre-trained model was just released yesterday: https://huggingface.co/stabilityai/stable-audio-open-1.0


Tests fail when installing h5netcdf without netcdf4

What happened:
Created a new conda env for xarray as described in the contribution guide.
Then I installed the h5netcdf and run all the tests (without making any changed in the xarray repo).
Tests failed due to missing dependencies apparently.
What you expected to happen:
Tests should not fail if a package is not a requirement and the backends can operate independently.
Minimal Complete Verifiable Example:
cd xarray
pip install -e .
pip install h5netcdf pytest-xdist
py.test -n 2 .

======================================================================== FAILURES =========================================================================
__________________________________________________________ TestH5NetCDFAlreadyOpen.test_deepcopy __________________________________________________________
[gw0] darwin -- Python 3.8.8 /usr/local/anaconda3/envs/xarray/bin/python3.8

self = <xarray.tests.test_backends.TestH5NetCDFAlreadyOpen object at 0x11ce5d5e0>

    def test_deepcopy(self):
        import h5netcdf

        with create_tmp_file() as tmp_file:
>           with nc4.Dataset(tmp_file, mode="w") as nc:
E           NameError: name 'nc4' is not defined

/Users/Victor/Documents/ProjectsDev/Qblox/xarray/xarray/tests/test_backends.py:2717: NameError
_____________________________________________________ TestH5NetCDFAlreadyOpen.test_open_dataset_group _____________________________________________________
[gw1] darwin -- Python 3.8.8 /usr/local/anaconda3/envs/xarray/bin/python3.8

self = <xarray.tests.test_backends.TestH5NetCDFAlreadyOpen object at 0x11cfe6bb0>

    def test_open_dataset_group(self):
        import h5netcdf

        with create_tmp_file() as tmp_file:
>           with nc4.Dataset(tmp_file, mode="w") as nc:
E           NameError: name 'nc4' is not defined

/Users/Victor/Documents/ProjectsDev/Qblox/xarray/xarray/tests/test_backends.py:2690: NameError
_____________________________________________________________ test_load_single_value_h5netcdf _____________________________________________________________
[gw0] darwin -- Python 3.8.8 /usr/local/anaconda3/envs/xarray/bin/python3.8

    def _get_default_engine_netcdf():
        try:
>           import netCDF4  # noqa: F401
E           ModuleNotFoundError: No module named 'netCDF4'

/Users/Victor/Documents/ProjectsDev/Qblox/xarray/xarray/backends/api.py:105: ModuleNotFoundError

During handling of the above exception, another exception occurred:

    def _get_default_engine_netcdf():
        try:
            import netCDF4  # noqa: F401

            engine = "netcdf4"
        except ImportError:  # pragma: no cover
            try:
>               import scipy.io.netcdf  # noqa: F401
E               ModuleNotFoundError: No module named 'scipy'

/Users/Victor/Documents/ProjectsDev/Qblox/xarray/xarray/backends/api.py:110: ModuleNotFoundError

During handling of the above exception, another exception occurred:

tmp_path = PosixPath('/private/var/folders/9k/k5388g_s44b_97319sslv9c40000gn/T/pytest-of-Victor/pytest-3/popen-gw0/test_load_single_value_h5netcd0')

    @requires_h5netcdf
    def test_load_single_value_h5netcdf(tmp_path):
        """Test that numeric single-element vector attributes are handled fine.

        At present (h5netcdf v0.8.1), the h5netcdf exposes single-valued numeric variable
        attributes as arrays of length 1, as oppesed to scalars for the NetCDF4
        backend.  This was leading to a ValueError upon loading a single value from
        a file, see #4471.
Tests still fail when installing scipy only.
They only pass after installing both netcdf4 and scipy.
 These tests should be marked as also requiring netCDF4.

@caenrigen thanks for the issue. Would you be up for fixing this with a PR?

@caenrigen thanks for the issue. Would you be up for fixing this with a PR?

Unfortunately out of bandwidth currently, this came out when addressing #4981 so I reported it as suggested.
For anyone facing the issue, installing netcdf4 solves the issue as a temporary fix

take


Client Allocation Request for: Notary OH Testing - DO NOT APPROVE, DELETE THIS

Client Allocation Questions
Core Information

Name: Notary OH Testing - DO NOT APPROVE, DELETE THIS
Website / Social Media: www.xnmatrix.com
Region: North America
DataCap Requested: 10TiB
Addresses to be Notarized: f1sa3wnoji3ppaiwy4aw76rwrdqhdxkt4azvttrvy
Notary Requested: XnMatrixSV

@dkkapur Please subscribe to notifications for this Issue to be aware of updates. Notaries may request additional information on the Issue.

Can you give more information...
....


[Slack] support optionally including culprit/project fields

Support optionally including culprit/project in notifications.

ugh.


mutlple bundles examples failed

Bellow is the official example showing how to split bundles, and it failed.
https://github.com/substack/node-browserify/tree/master/example/multiple_bundles
Here is the steps I take

install browserify of version 11.0.1
run the build.sh in the example/multiple_bundles folder
then open static/beep.html in the browser

Then I see some error message in the chrome console
Uncaught Error: Cannot find module '/robot.js'

I also tried version 6.1.2, which was mention here #933 , but it also failed .
Anyone else who has the same problem?

I have run the example successfully. What's content of your built common.js and beep.js?

I believe this is also causing issues for me, huge example files though, looks like the dedupe code inspects the current "t" via "arguments[4]", which fails because the previously defined modules need to be require()'d by index.
 This is caused by the dedupe feature, it only happens when a duplicate is in a later bundle, and then cannot reference back to the original module using the current methodology. I will fix up any broken tests and submit a pr :)

Actually, this is not so simple as it seems, my fix will seemingly work for projects not using fullPaths, but will cause _empty.js to end up outside of the common file created with factor-bundle.


Submit BioNetGen 2.5.2

id: bionetgen
version: 2.5.2
specificationsUrl: https://raw.githubusercontent.com/biosimulators/Biosimulators_BioNetGen/82e86226f99d62a7bd3caefc0f19910b274f9c6a/biosimulators.json
specificationsPatch:
version: 2.5.2
image:
url: ghcr.io/biosimulators/biosimulators_bionetgen/bionetgen:2.5.2
validateImage: true
commitSimulator: true

The previous run failed due to this workflow not having permissions to write simulators. I believe this is now fixed.
Trying again.

Thank you @biosimulators-daemon for your submission to the BioSimulators simulator validation/submission system!
The BioSimulators validator bot is validating the specifications of your simulator, validating your Docker image and committing your simulator to the BioSimulators registry.
We will discuss any concerns with your submission in this issue.
A complete log of your simulator submission job is available here.

The specifications of your simulator is valid!

Summary of tests

Executed 56 test cases

Passed 39 test cases:

cli.CliDescribesSupportedEnvironmentVariablesInline
cli.CliDisplaysHelpInline
cli.CliDisplaysVersionInformationInline
combine_archive.CombineArchiveHasSedDocumentsInNestedDirectories
combine_archive.CombineArchiveHasSedDocumentsWithSameNamesInDifferentInNestedDirectories
combine_archive.CombineArchiveTestCase
combine_archive.WhenACombineArchiveHasAMasterFileSimulatorOnlyExecutesThisFile
combine_archive.WhenACombineArchiveHasNoMasterFileSimulatorExecutesAllSedDocuments
docker_image.DeclaresSupportedEnvironmentVariables
docker_image.DefaultUserIsRoot
docker_image.HasBioContainersLabels
docker_image.HasOciLabels
log.SimulatorReportsTheStatusOfTheExecutionOfCombineArchives
log.SimulatorReportsTheStatusOfTheExecutionOfSedDocuments
log.SimulatorReportsTheStatusOfTheExecutionOfSedOutputs
log.SimulatorReportsTheStatusOfTheExecutionOfSedTasks
published_project.SimulatorCanExecutePublishedProject:bngl/Dolan-PLoS-Comput-Biol-2015-NHEJ
published_project.SimulatorCanExecutePublishedProject:bngl/test-bngl
results_report.SimulatorGeneratesReportsOfSimulationResults
sedml.SimulatorCanResolveModelSourcesDefinedByUriFragments
sedml.SimulatorCanResolveModelSourcesDefinedByUriFragmentsAndInheritChanges
sedml.SimulatorProducesLinear2DPlots
sedml.SimulatorProducesLogarithmic2DPlots
sedml.SimulatorProducesMultiplePlots
sedml.SimulatorProducesReportsWithCuratedNumberOfDimensions
sedml.SimulatorSupportsAlgorithmParameters
sedml.SimulatorSupportsDataGeneratorsWithDifferentShapes
sedml.SimulatorSupportsDataSetsWithDifferentShapes
sedml.SimulatorSupportsModelsSimulationsTasksDataGeneratorsAndReports
sedml.SimulatorSupportsMultipleReportsPerSedDocument
sedml.SimulatorSupportsMultipleTasksPerSedDocument
sedml.SimulatorSupportsRepeatedTasksWithFunctionalRanges
sedml.SimulatorSupportsRepeatedTasksWithMultipleSubTasks
sedml.SimulatorSupportsRepeatedTasksWithNestedFunctionalRanges
sedml.SimulatorSupportsRepeatedTasksWithNestedRepeatedTasks
sedml.SimulatorSupportsRepeatedTasksWithSubTasksOfMixedTypes
sedml.SimulatorSupportsRepeatedTasksWithVectorRanges
sedml.SimulatorSupportsUniformTimeCoursesWithNonZeroInitialTimes
sedml.SimulatorSupportsUniformTimeCoursesWithNonZeroOutputStartTimes

Failed 0 test cases

Skipped 17 test cases:

published_project.SimulatorCanExecutePublishedProject:sbml-core/Caravagna-J-Theor-Biol-2010-tumor-suppressive-oscillations
published_project.SimulatorCanExecutePublishedProject:sbml-core/Ciliberto-J-Cell-Biol-2003-morphogenesis-checkpoint
published_project.SimulatorCanExecutePublishedProject:sbml-core/Edelstein-Biol-Cybern-1996-Nicotinic-excitation
published_project.SimulatorCanExecutePublishedProject:sbml-core/Parmar-BMC-Syst-Biol-2017-iron-distribution
published_project.SimulatorCanExecutePublishedProject:sbml-core/Szymanska-J-Theor-Biol-2009-HSP-synthesis
published_project.SimulatorCanExecutePublishedProject:sbml-core/Tomida-EMBO-J-2003-NFAT-translocation
published_project.SimulatorCanExecutePublishedProject:sbml-core/Varusai-Sci-Rep-2018-mTOR-signaling-LSODA-LSODAR-SBML
published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock
published_project.SimulatorCanExecutePublishedProject:sbml-fbc/Escherichia-coli-core-metabolism
published_project.SimulatorCanExecutePublishedProject:sbml-qual/Chaouiya-BMC-Syst-Biol-2013-EGF-TNFa-signaling
sedml.SimulatorProducesLinear3DPlots
sedml.SimulatorProducesLogarithmic3DPlots
sedml.SimulatorSupportsAddReplaceRemoveModelElementChanges
sedml.SimulatorSupportsComputeModelChanges
sedml.SimulatorSupportsModelAttributeChanges
sedml.SimulatorSupportsRepeatedTasksWithChanges
sedml.SimulatorSupportsRepeatedTasksWithFunctionalRangeVariables

Warnings
cli.CliDescribesSupportedEnvironmentVariablesInline (10.9 s)
Test that the inline help for a command-line interface describes the environment variables that the simulator supports.
Warnings:
The inline help for a command-line interface for a simulation tool should describe the environment variables that the simulation tool supports.

The command-line interface does not describe the following standard environment variables recognized by BioSimulators:
  - 'ALGORITHM_SUBSTITUTION_POLICY'

If the simulation tool implements these variables, they should be described in the inline help for its command-line interface.

Note, support for these environment variables is optional. Simulation tools are not required to support these variables.

Log:

docker_image.DeclaresSupportedEnvironmentVariables (0.4 s)
Test if a Docker image declares the environment variables that is supports
Warnings:
Docker images for simulation tools should declare the environment variables that they support.

The Docker image does not declare the following standard environment variables recognized by BioSimulators:
  - 'ALGORITHM_SUBSTITUTION_POLICY'

If the simulation tool implements these variables, they should be declared in the Dockerfile for the Docker image for the simulator.

Note, support for these environment variables is optional. Simulation tools are not required to support these variables.

Log:

The image for your simulator is valid!

The validation/submission of your simulator failed.
- 401 Client Error: Unauthorized for url: https://auth.biosimulations.org/oauth/token

The complete log of your validation/submission job, including further information about the failure, is available here.
Once you have fixed the problem, edit the first block of this issue to re-initiate this validation.
The BioSimulators Team is happy to help. Questions and feedback can be directed to the BioSimulators Team by posting comments to this issues that reference the GitHub team @biosimulators/biosimulators (without the backticks).

Thank you @biosimulators-daemon for your submission to the BioSimulators simulator validation/submission system!
The BioSimulators validator bot is validating the specifications of your simulator, validating your Docker image and committing your simulator to the BioSimulators registry.
We will discuss any concerns with your submission in this issue.
A complete log of your simulator submission job is available here.

The specifications of your simulator is valid!

Summary of tests

Executed 55 test cases

Passed 38 test cases:

cli.CliDescribesSupportedEnvironmentVariablesInline
cli.CliDisplaysHelpInline
cli.CliDisplaysVersionInformationInline
combine_archive.CombineArchiveHasSedDocumentsInNestedDirectories
combine_archive.CombineArchiveHasSedDocumentsWithSameNamesInDifferentInNestedDirectories
combine_archive.WhenACombineArchiveHasAMasterFileSimulatorOnlyExecutesThisFile
combine_archive.WhenACombineArchiveHasNoMasterFileSimulatorExecutesAllSedDocuments
docker_image.DeclaresSupportedEnvironmentVariables
docker_image.DefaultUserIsRoot
docker_image.HasBioContainersLabels
docker_image.HasOciLabels
log.SimulatorReportsTheStatusOfTheExecutionOfCombineArchives
log.SimulatorReportsTheStatusOfTheExecutionOfSedDocuments
log.SimulatorReportsTheStatusOfTheExecutionOfSedOutputs
log.SimulatorReportsTheStatusOfTheExecutionOfSedTasks
published_project.SimulatorCanExecutePublishedProject:bngl/Dolan-PLoS-Comput-Biol-2015-NHEJ
published_project.SimulatorCanExecutePublishedProject:bngl/test-bngl
results_report.SimulatorGeneratesReportsOfSimulationResults
sedml.SimulatorCanResolveModelSourcesDefinedByUriFragments
sedml.SimulatorCanResolveModelSourcesDefinedByUriFragmentsAndInheritChanges
sedml.SimulatorProducesLinear2DPlots
sedml.SimulatorProducesLogarithmic2DPlots
sedml.SimulatorProducesMultiplePlots
sedml.SimulatorProducesReportsWithCuratedNumberOfDimensions
sedml.SimulatorSupportsAlgorithmParameters
sedml.SimulatorSupportsDataGeneratorsWithDifferentShapes
sedml.SimulatorSupportsDataSetsWithDifferentShapes
sedml.SimulatorSupportsModelsSimulationsTasksDataGeneratorsAndReports
sedml.SimulatorSupportsMultipleReportsPerSedDocument
sedml.SimulatorSupportsMultipleTasksPerSedDocument
sedml.SimulatorSupportsRepeatedTasksWithFunctionalRanges
sedml.SimulatorSupportsRepeatedTasksWithMultipleSubTasks
sedml.SimulatorSupportsRepeatedTasksWithNestedFunctionalRanges
sedml.SimulatorSupportsRepeatedTasksWithNestedRepeatedTasks
sedml.SimulatorSupportsRepeatedTasksWithSubTasksOfMixedTypes
sedml.SimulatorSupportsRepeatedTasksWithVectorRanges
sedml.SimulatorSupportsUniformTimeCoursesWithNonZeroInitialTimes
sedml.SimulatorSupportsUniformTimeCoursesWithNonZeroOutputStartTimes

Failed 0 test cases

Skipped 17 test cases:

published_project.SimulatorCanExecutePublishedProject:sbml-core/Caravagna-J-Theor-Biol-2010-tumor-suppressive-oscillations
published_project.SimulatorCanExecutePublishedProject:sbml-core/Ciliberto-J-Cell-Biol-2003-morphogenesis-checkpoint
published_project.SimulatorCanExecutePublishedProject:sbml-core/Edelstein-Biol-Cybern-1996-Nicotinic-excitation
published_project.SimulatorCanExecutePublishedProject:sbml-core/Parmar-BMC-Syst-Biol-2017-iron-distribution
published_project.SimulatorCanExecutePublishedProject:sbml-core/Szymanska-J-Theor-Biol-2009-HSP-synthesis
published_project.SimulatorCanExecutePublishedProject:sbml-core/Tomida-EMBO-J-2003-NFAT-translocation
published_project.SimulatorCanExecutePublishedProject:sbml-core/Varusai-Sci-Rep-2018-mTOR-signaling-LSODA-LSODAR-SBML
published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock
published_project.SimulatorCanExecutePublishedProject:sbml-fbc/Escherichia-coli-core-metabolism
published_project.SimulatorCanExecutePublishedProject:sbml-qual/Chaouiya-BMC-Syst-Biol-2013-EGF-TNFa-signaling
sedml.SimulatorProducesLinear3DPlots
sedml.SimulatorProducesLogarithmic3DPlots
sedml.SimulatorSupportsAddReplaceRemoveModelElementChanges
sedml.SimulatorSupportsComputeModelChanges
sedml.SimulatorSupportsModelAttributeChanges
sedml.SimulatorSupportsRepeatedTasksWithChanges
sedml.SimulatorSupportsRepeatedTasksWithFunctionalRangeVariables

Warnings
cli.CliDescribesSupportedEnvironmentVariablesInline (10.3 s)
Test that the inline help for a command-line interface describes the environment variables that the simulator supports.
Warnings:
The inline help for a command-line interface for a simulation tool should describe the environment variables that the simulation tool supports.

The command-line interface does not describe the following standard environment variables recognized by BioSimulators:
  - 'ALGORITHM_SUBSTITUTION_POLICY'

If the simulation tool implements these variables, they should be described in the inline help for its command-line interface.

Note, support for these environment variables is optional. Simulation tools are not required to support these variables.

Log:

docker_image.DeclaresSupportedEnvironmentVariables (0.3 s)
Test if a Docker image declares the environment variables that is supports
Warnings:
Docker images for simulation tools should declare the environment variables that they support.

The Docker image does not declare the following standard environment variables recognized by BioSimulators:
  - 'ALGORITHM_SUBSTITUTION_POLICY'

If the simulation tool implements these variables, they should be declared in the Dockerfile for the Docker image for the simulator.

Note, support for these environment variables is optional. Simulation tools are not required to support these variables.

Log:

The image for your simulator is valid!

The validation/submission of your simulator failed.
- 401 Client Error: Unauthorized for url: https://auth.biosimulations.org/oauth/token

The complete log of your validation/submission job, including further information about the failure, is available here.
Once you have fixed the problem, edit the first block of this issue to re-initiate this validation.
The BioSimulators Team is happy to help. Questions and feedback can be directed to the BioSimulators Team by posting comments to this issues that reference the GitHub team @biosimulators/biosimulators (without the backticks).

Thank you @biosimulators-daemon for your submission to the BioSimulators simulator validation/submission system!
The BioSimulators validator bot is validating the specifications of your simulator, validating your Docker image and committing your simulator to the BioSimulators registry.
We will discuss any concerns with your submission in this issue.
A complete log of your simulator submission job is available here.

The specifications of your simulator is valid!

Summary of tests

Executed 55 test cases

Passed 38 test cases:

cli.CliDescribesSupportedEnvironmentVariablesInline
cli.CliDisplaysHelpInline
cli.CliDisplaysVersionInformationInline
combine_archive.CombineArchiveHasSedDocumentsInNestedDirectories
combine_archive.CombineArchiveHasSedDocumentsWithSameNamesInDifferentInNestedDirectories
combine_archive.WhenACombineArchiveHasAMasterFileSimulatorOnlyExecutesThisFile
combine_archive.WhenACombineArchiveHasNoMasterFileSimulatorExecutesAllSedDocuments
docker_image.DeclaresSupportedEnvironmentVariables
docker_image.DefaultUserIsRoot
docker_image.HasBioContainersLabels
docker_image.HasOciLabels
log.SimulatorReportsTheStatusOfTheExecutionOfCombineArchives
log.SimulatorReportsTheStatusOfTheExecutionOfSedDocuments
log.SimulatorReportsTheStatusOfTheExecutionOfSedOutputs
log.SimulatorReportsTheStatusOfTheExecutionOfSedTasks
published_project.SimulatorCanExecutePublishedProject:bngl/Dolan-PLoS-Comput-Biol-2015-NHEJ
published_project.SimulatorCanExecutePublishedProject:bngl/test-bngl
results_report.SimulatorGeneratesReportsOfSimulationResults
sedml.SimulatorCanResolveModelSourcesDefinedByUriFragments
sedml.SimulatorCanResolveModelSourcesDefinedByUriFragmentsAndInheritChanges
sedml.SimulatorProducesLinear2DPlots
sedml.SimulatorProducesLogarithmic2DPlots
sedml.SimulatorProducesMultiplePlots
sedml.SimulatorProducesReportsWithCuratedNumberOfDimensions
sedml.SimulatorSupportsAlgorithmParameters
sedml.SimulatorSupportsDataGeneratorsWithDifferentShapes
sedml.SimulatorSupportsDataSetsWithDifferentShapes
sedml.SimulatorSupportsModelsSimulationsTasksDataGeneratorsAndReports
sedml.SimulatorSupportsMultipleReportsPerSedDocument
sedml.SimulatorSupportsMultipleTasksPerSedDocument
sedml.SimulatorSupportsRepeatedTasksWithFunctionalRanges
sedml.SimulatorSupportsRepeatedTasksWithMultipleSubTasks
sedml.SimulatorSupportsRepeatedTasksWithNestedFunctionalRanges
sedml.SimulatorSupportsRepeatedTasksWithNestedRepeatedTasks
sedml.SimulatorSupportsRepeatedTasksWithSubTasksOfMixedTypes
sedml.SimulatorSupportsRepeatedTasksWithVectorRanges
sedml.SimulatorSupportsUniformTimeCoursesWithNonZeroInitialTimes
sedml.SimulatorSupportsUniformTimeCoursesWithNonZeroOutputStartTimes

Failed 0 test cases

Skipped 17 test cases:

published_project.SimulatorCanExecutePublishedProject:sbml-core/Caravagna-J-Theor-Biol-2010-tumor-suppressive-oscillations
published_project.SimulatorCanExecutePublishedProject:sbml-core/Ciliberto-J-Cell-Biol-2003-morphogenesis-checkpoint
published_project.SimulatorCanExecutePublishedProject:sbml-core/Edelstein-Biol-Cybern-1996-Nicotinic-excitation
published_project.SimulatorCanExecutePublishedProject:sbml-core/Parmar-BMC-Syst-Biol-2017-iron-distribution
published_project.SimulatorCanExecutePublishedProject:sbml-core/Szymanska-J-Theor-Biol-2009-HSP-synthesis
published_project.SimulatorCanExecutePublishedProject:sbml-core/Tomida-EMBO-J-2003-NFAT-translocation
published_project.SimulatorCanExecutePublishedProject:sbml-core/Varusai-Sci-Rep-2018-mTOR-signaling-LSODA-LSODAR-SBML
published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock
published_project.SimulatorCanExecutePublishedProject:sbml-fbc/Escherichia-coli-core-metabolism
published_project.SimulatorCanExecutePublishedProject:sbml-qual/Chaouiya-BMC-Syst-Biol-2013-EGF-TNFa-signaling
sedml.SimulatorProducesLinear3DPlots
sedml.SimulatorProducesLogarithmic3DPlots
sedml.SimulatorSupportsAddReplaceRemoveModelElementChanges
sedml.SimulatorSupportsComputeModelChanges
sedml.SimulatorSupportsModelAttributeChanges
sedml.SimulatorSupportsRepeatedTasksWithChanges
sedml.SimulatorSupportsRepeatedTasksWithFunctionalRangeVariables

Warnings
cli.CliDescribesSupportedEnvironmentVariablesInline (10.1 s)
Test that the inline help for a command-line interface describes the environment variables that the simulator supports.
Warnings:
The inline help for a command-line interface for a simulation tool should describe the environment variables that the simulation tool supports.

The command-line interface does not describe the following standard environment variables recognized by BioSimulators:
  - 'ALGORITHM_SUBSTITUTION_POLICY'

If the simulation tool implements these variables, they should be described in the inline help for its command-line interface.

Note, support for these environment variables is optional. Simulation tools are not required to support these variables.

Log:

docker_image.DeclaresSupportedEnvironmentVariables (0.3 s)
Test if a Docker image declares the environment variables that is supports
Warnings:
Docker images for simulation tools should declare the environment variables that they support.

The Docker image does not declare the following standard environment variables recognized by BioSimulators:
  - 'ALGORITHM_SUBSTITUTION_POLICY'

If the simulation tool implements these variables, they should be declared in the Dockerfile for the Docker image for the simulator.

Note, support for these environment variables is optional. Simulation tools are not required to support these variables.

Log:

The image for your simulator is valid!

Your submission was committed to the BioSimulators registry. Thank you!
Future submissions of subsequent versions of bionetgen to the BioSimulators registry will be automatically validated. These submissions will not require manual review by the BioSimulators Team.


fix($compile): validate directive name for whitespaces

Throw an exception if directive name contains leading or trailing whitespaces
Closes #11397

I think you would also need a new baddirwspc.ngdoc file under docs/content/error/$compile/.
E.g. take a look at docs/content/error/$compile/baddir.ngdoc.

LGTM, provided that an existing error page is used and its content is updated accordingly

@pkozlowski-opensource Is the updated error page good enough for you, or probably you would like to structure conditions in a list?

Should be fine as a starting point. Could you please squash all the 3 commits into one so it is easier to merge?

@pkozlowski-opensource Done

@pkozlowski-opensource Sorry for interrupting you again. I can't understand why CI build failed. Don't see any errors related to my changes. Could you advice on that? :)

It's all well now :)

@pkozlowski-opensource  and @gkalpak can you assign this to a milestone and/or deal with it?
Thanks

It LGTM as is, but if we wanted to go the extra mile, we could verify there is no whitespace in the name whatsoever.

Is this a breaking change or did the compiler just fail to match directives with leading/trailing whitespace before?
Should we just be more compliant and simply trim directive names?

Previously, the compiler just failed to match the directives, so this is not a breaking change.
I am not sure what is the best approach: throwing an error or trimming names (I'd be happy with either).
If we decide to also check for internal whitespace, then I guess throwing makes more sense.

If we decide to also check for internal whitespace, then I guess throwing makes more sense

Personally I would only add additional checks if users keep complaining about common mistakes. Each check cost us frw size and CPU cycles, so checks should be used with moderation, IMO.

Ah, and I'm for throwing - I really don't like systems that try to work-around common mistakes, Fail fast is the way to go IMO.

OK, let's merge this then.