First example in Getting-Started Guide does not work properly

Issue Type

Bug report

Molecule and Ansible details
$ ansible --version && molecule --version
ansible [core 2.11.5]
  config file = None
  configured module search path = ['/home/vagrant/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /home/vagrant/.local/lib/python3.8/site-packages/ansible
  ansible collection location = /home/vagrant/.ansible/collections:/usr/share/ansible/collections
  executable location = /home/vagrant/.local/bin/ansible
  python version = 3.8.10 (default, Sep 28 2021, 16:10:42) [GCC 9.3.0]
  jinja version = 3.0.2
  libyaml = True
INFO     Found config file /home/vagrant/molecule/.config/molecule/config.yml
molecule 3.5.2 using python 3.8
    ansible:2.11.5
    delegated:3.5.2 from molecule
    docker:1.0.2 from molecule_docker requiring collections: community.docker>=1.8.0

Additional Information:

The test environment used is a clean and up-to-date Vagrantbox 'ubuntu/focal64' (v20211007.0.0).

Molecule installation method (one of):

pip (also tried installing it from source but that didn't change anything)

Ansible installation method (one of):

pip

Desired Behavior
The steps shown in the Getting-Started Guide should work without errors:
molecule init role my-new-role --driver-name docker
cd my-new-role/
molecule create

Actual Behaviour
Error: Computed fully qualified role name of my-new-role does not follow current galaxy requirements
The following error output will be seen when executing molecule create according to the documentation:
$ molecule --debug create
DEBUG    Validating schema /home/vagrant/my-new-role/molecule/default/molecule.yml.
INFO     default scenario test matrix: dependency, create, prepare
INFO     Performing prerun...
INFO     Added ANSIBLE_LIBRARY=/home/vagrant/.cache/ansible-compat/068eef/modules:/home/vagrant/.ansible/plugins/modules:/usr/share/ansible/plugins/modules
INFO     Added ANSIBLE_COLLECTIONS_PATH=/home/vagrant/.cache/ansible-compat/068eef/collections:/home/vagrant/.ansible/collections:/usr/share/ansible/collections
INFO     Added ANSIBLE_ROLES_PATH=/home/vagrant/.cache/ansible-compat/068eef/roles:/home/vagrant/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles
ERROR    Computed fully qualified role name of my-new-role does not follow current galaxy requirements.
Please edit meta/main.yml and assure we can correctly determine full role name:

galaxy_info:
role_name: my_name  # if absent directory name hosting role is used instead
namespace: my_galaxy_namespace  # if absent, author is used instead

Namespace: https://galaxy.ansible.com/docs/contributing/namespaces.html#galaxy-namespace-limitations
Role: https://galaxy.ansible.com/docs/contributing/creating_role.html#role-names

As an alternative, you can add 'role-name' to either skip_list or warn_list.

Traceback (most recent call last):
  File "/home/vagrant/molecule/.venv/bin/molecule", line 8, in <module>
    sys.exit(main())
  File "/home/vagrant/molecule/.venv/lib/python3.8/site-packages/click/core.py", line 1128, in __call__
    return self.main(*args, **kwargs)
  File "/home/vagrant/molecule/.venv/lib/python3.8/site-packages/click/core.py", line 1053, in main
    rv = self.invoke(ctx)
  File "/home/vagrant/molecule/.venv/lib/python3.8/site-packages/click/core.py", line 1659, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/vagrant/molecule/.venv/lib/python3.8/site-packages/click/core.py", line 1395, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/vagrant/molecule/.venv/lib/python3.8/site-packages/click/core.py", line 754, in invoke
    return __callback(*args, **kwargs)
  File "/home/vagrant/molecule/.venv/lib/python3.8/site-packages/click/decorators.py", line 26, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/home/vagrant/molecule/.venv/lib/python3.8/site-packages/molecule/command/create.py", line 121, in create
    base.execute_cmdline_scenarios(scenario_name, args, command_args)
  File "/home/vagrant/molecule/.venv/lib/python3.8/site-packages/molecule/command/base.py", line 111, in execute_cmdline_scenarios
    scenario.config.runtime.prepare_environment()
  File "/home/vagrant/molecule/.venv/lib/python3.8/site-packages/ansible_compat/runtime.py", line 255, in prepare_environment
    self._install_galaxy_role(self.project_dir, ignore_errors=True)
  File "/home/vagrant/molecule/.venv/lib/python3.8/site-packages/ansible_compat/runtime.py", line 396, in _install_galaxy_role
    raise InvalidPrerequisiteError(msg)
ansible_compat.errors.InvalidPrerequisiteError: Computed fully qualified role name of my-new-role does not follow current galaxy requirements.
Please edit meta/main.yml and assure we can correctly determine full role name:

galaxy_info:
role_name: my_name  # if absent directory name hosting role is used instead
namespace: my_galaxy_namespace  # if absent, author is used instead

Namespace: https://galaxy.ansible.com/docs/contributing/namespaces.html#galaxy-namespace-limitations
Role: https://galaxy.ansible.com/docs/contributing/creating_role.html#role-names

As an alternative, you can add 'role-name' to either skip_list or warn_list.

While I do understand that my-new-role is not compliant to "current galaxy requirements" the same error is also shown for the role name: my_new_role.
The issue seems to be that both the default role_name and namespace don't follow these galaxy requirements:

role_name for the example in the documentation would be the directory name which is my-new-role
namespace for the example in the documentation would be the author and therefore your name

Even though, after carefully reading the complete error message and the linked documentation in it, these errors should become clear I think that the first example of the Getting-Started Guide should work out-of-the-box. A user that has never used molecule before (like myself) might be very confused by this fact. Not sure if others agree but in my opinion either the documentation (to at least include a warning and explanation) or the implementation (of say the default values replacing " " and "-" with "_") should be adjusted.

Closing this again seeing as it's probably not a bug but a documentation issue


YouTube said: Invalid parameters. (instead of specific error message)

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2018.01.14. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2018.01.14

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue
For a few days now, videos that have been removed, blocked, unavailable in current country etc. yield the generic error "Invalid parameters" instead of the actual message you'd see in a browser, like before.
My workflow depends on knowing why accessing a video failed. I used "youtube-dl --skip-download ..." for this.

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
$ youtube-dl -v NbhXmSBlS_U
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'-v', u'NbhXmSBlS_U']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2018.01.14
[debug] Python version 2.7.14 (CPython) - Linux-4.15.0-rc7-devtest+-x86_64-with-debian-buster-sid
[debug] exe versions: avprobe present, ffmpeg N-81364-gf85842b-static, ffprobe N-81364-gf85842b-static
[debug] Proxy map: {}
[youtube] NbhXmSBlS_U: Downloading webpage
[youtube] NbhXmSBlS_U: Downloading video info webpage
ERROR: NbhXmSBlS_U: YouTube said: Invalid parameters.
Traceback (most recent call last):
  File "/home/zahl/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 784, in extract_info
    ie_result = ie.extract(url)
  File "/home/zahl/bin/youtube-dl/youtube_dl/extractor/common.py", line 438, in extract
    ie_result = self._real_extract(url)
  File "/home/zahl/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1609, in _real_extract
    expected=True, video_id=video_id)
ExtractorError: NbhXmSBlS_U: YouTube said: Invalid parameters.

Description of your issue, suggested solution and other information
This seems to happen since around Jan 4 according to logs.
Examples:
XR4YH1N04pc (This video contains content from UMG, who has blocked it in your country on copyright grounds.)
NbhXmSBlS_U (This video contains content from Formula One Management, who has blocked it on copyright grounds.)
7HpZjCe9LQY (This video is unavailable.)
xPFZl59_OZ4 (This video is no longer available because the YouTube account associated with this video has been terminated.)
n_7t_vO3vlU ("Gamma Ray - Beyo..." The YouTube account associated with this video has been terminated due to multiple third-party notifications of copyright infringement.)
The all just yield "Invalid parameters".
The website itself also behaves slightly different from before, I cannot get it to tell me that a video does not exist by passing random or invalid video ids, I only get the "unavailable" message, so that would at least explain why youtube-dl doesn't report non-existent videos anymore, but the rest should still be possible to detect.

Could be, i didn't try to confirm, but that youtube limits the IPs from data centers. For a quite some time, google, netflix, and other big services added that as the decision making info for providing services. That's why you can't get cheap VPS and make your proxy for netflix any more.

I'm getting this right now for a video that is geoblocked, but not in my country, where my request is coming from.

Im getting this error anytime i try no matter wich link or id um using. Please help

@yan12125 , I also have the same issue with any link and id. Could you please help with that?
My youtube-dl --version is 2018.03.14

Update your youtube-dl...

I picked a random video (EXaLvBGqQww) and downloading works fine with version 2020.07.28. Most likely recent issues (if any) are different from those in 2018. Please make sure you are using the latest version and create a new issue if needed.
Locked this one as the original issue from 2018 have been solved for a long time.


Export as a Cypress Test script doesn't work when using only aria-labels as selectors

I want to use only aria-label as selectors for my tests. After recording I edit each step and I remove the CSS selectors. When trying to export it as a cypress test the extension won't work anymore (it does nothing when I click the download icon).
I've also tried doing the same using the CLI to transform a json file with aria-label as selectors and I get this error:
TypeError: Cannot read properties of undefined (reading '0')
    at handleSelectors (file:///usr/local/lib/node_modules/@cypress/chrome-recorder/dist/CypressStringifyExtension.js:136:63)

Could you please help me?
Thank you.

Removing the aria-label is a decision and not an issue.
// Remove Aria selectors in favor of DOM selectors
https://github.com/cypress-io/cypress-chrome-recorder/blob/41cf2792177c6e8d806afea2333f571687d9de14/src/CypressStringifyExtension.ts#L192


New exporter does not have client and filesystem level metrics

I have set up the new exporter for one of the pure arrays. I noticed that all these client and filesystem level metrics are not available in the new exporter. Not available as part of any other new metrics either.
These are important filesystem and client level metrics. Can you please provide more information on why these are deprecated from the new exporter and if there is any plan to add these back?
purefb_client_performance_iops
purefb_client_performance_latency_usec
purefb_client_performance_opns_bytes
purefb_client_performance_throughput_bytes
purefb_filesystem_user_usage_bytes
purefb_filesystem_group_usage_bytes
purefb_filesystem_performance_iops
purefb_filesystem_performance_latency_usec
purefb_filesystem_performance_opns_bytes
purefb_filesystem_performance_throughput_bytes

Those metrics you are looking for are deemed the most expensive ones in terms of slow response time. For that reason I have defined two specific endpoints that can be used to grab the related info:
http://:/metrics/clients
and
http://:/metrics/usage
The exporter also reports those when invoked without any specific endpoint, like this
http://:/metrics
In both cases you should consider that the response time may very considerably, from something in between 15 and 120 sec, depending on the cardinality of clients and filesystems, therefore you may have to increse the scraping interval timeout for Prometheus and also for the exporter, otherwise the whole array will be marked as down by Prometheus.

Hi @jmg011,
The metrics have been renamed from the previous version of the exporter in order to reflect the name of the corresponding API endpoints. Also I was wrong with my previous answer. The file systems metrics are included in those reported by the /metrics/array and by the /metrics endpoints and their names are these:
purefb_file_systems_space_data_reduction_ratio
purefb_file_systems_space_bytes
purefb_file_systems_performance_latency_usec
purefb_file_systems_performance_throughput_iops
purefb_file_systems_performance_bandwidth_bytes
purefb_file_systems_performance_average_bytes
purefb_file_system_links_lag_msec
The file system usage metrics are instead reported by the /metrics/usage endpoint and are the following
purefb_file_system_usage_users_bytes
purefb_file_system_usage_groups_bytes
Also we have noticed that the current 0.8.1 image published on quay.io has some issues when run on docker engine so it is suggested to use the 0.8.2 which now defaults to the base docker-alpine image

@genegr - I used 0.8.2 image and I still do not see those file system level metrics which are renamed. Can you please confirm that this is the correct image? quay.io/purestorage/pure-fb-ome:0.8.2

Hi @genegr - Any update on this?

Hi @jmg011 - There is a new image quay.io/purestorage/pure-fb-ome:0.8.2, that corresponds to the current release 0.8.3 and that  is based on Sanic instead than Flask+Gunicorn. Anyhow I can confirm the file system metrics are retrived in this and all the previous version of the exporter, at least for the arrays that are on Purity versions 3.2.x. It might instead be the case the file system specific metrics are not retrieved for other less recent Purity releases because they are not available to the REST APIs.

@genegr Thank you. Let me try this new image and see if I can get those metrics. We have 3.2.x so I should be able to get it. I will get back if I still see an issue.

@genegr I tested with this quay.io/purestorage/pure-fb-ome:0.8.2 image
Configuration:
purity/FB version="3.2.6"
scrape interval: 2m
scrape timeout: 2m
No timeouts with 2m interval
scrapped end points: (successful scraping, no failures)
(tested without /metrics as well)
/metrics
/metrics/clients
/metrics/usage
/metrics/array
I see only below 4 filesystem metrics. Can we have a working session to debug this? I can request the account manager to set up a meeting.

@jmg011 Sure thing. We can certainly arrange a session for troubleshooting your current setup. One thing that we have noticed is that there are some differencies between 3.3.x and 3.2.x (and even between 3.3.1 and 3.3.0). In addition to those, there is also a weird issue with the py-pure-client that generates a leak of file descriptors and I am trying to fix  that by swithcing to the 'request' python module until our API client library gets fixed.

@genegr - Can you point me to the exporter for Pure Block Storage?

@jmg011 you can find it here: https://github.com/PureStorage-OpenConnect/pure-fa-openmetrics-exporter
Note that this is in beta and that @genegr is currently on sick leave for a few weeks, so bug fixes may take longer to be addressed

@sdodsley Thank you. Can you verify this syntax? The docker fails to run with this error:
unrecognized arguments: pure_fa_ome:create_app(disable_ssl_warn=True)
docker run -d -p 9491:9491 --name pure-exporter-fa-ver1 quay.io/purestorage/pure-fa-ome 'pure_fa_exporter:create_app(disable_ssl_warn=True)'

@sdodsley Thank you. I ran the exporter on docker. Disabled SSL check.
The logs say:
[2022-03-30 00:38:32 +0000] [1] [INFO] packages: sanic-routing==0.7.2
[2022-03-30 00:38:32 +0000] [1] [INFO] Starting worker [1]
But when I try to access the end-point /metrics, it does not return anything. It says site cannot be reached. I double checked on the port numbers and everything.
http://:9491/metrics
What could be the possible issue?

@sdodsley @genegr - Hi Any update on this?

@jmg011 there will be a delay to responding as @genegr has had a medical emergency and will be offline for a number of weeks.
I will try and get someone else to look at this in the meantime.


[15.9.0] Crash on iOS with SVG containing feComposite called by SvgXml

Description
Hello,
Since 15.9.0, I have a crash on IOS with a SVG called with SvgXml.
I tried some manipulation like remove feComposite tags and the app doesn't crash.
No problem on Android (debug and release)
Thank you
Steps to reproduce

Clone
expo run:ios

Snack or a link to a repository
https://github.com/TomCorvus/RNSVG
SVG version
15.9.0
React Native version
0.76.3
Platforms
iOS
JavaScript runtime
Hermes
Workflow
React Native
Architecture
None
Build type
Debug app & production bundle
Device
iOS simulator
Device model
No response
Acknowledgements
Yes

Hey @TomCorvus,
Thank you for reporting this, can confirm that there is an issue with FeComposite when not all arguments (k1, k2, k3, k4) are provided. I will release the fix as soon as possible. In the meantime, as a workaround, you can add k1="0" k4="0" to each FeComposite to ensure all values are passed (0 is the default).

Thank you @jakex7!

@jakex7 LMK if you prefer that I open a new issue, but I thought it could be related to this

Hey @fbp93, there's no need to create a new issue since it's related to the same crash and requires the same fix.


Add BLAS C bindings

Add BLAS API C FFI bindings so that (eventually) faer can be used as a drop-in replacement to BLAS libraries in software like NumPy

hi! thanks for the pr.
i like the idea of having a blas api, although i'm not sure if i have all of it implemented in faer so far.
how much of the api do you want to cover in this PR? it's fine if you don't do all of it since we can incrementally build it up until it's finished

Hi, I agree that I shouldn't try to get 100% BLAS coverage in this PR. I'll do the basic abstractions and get a couple functions working with LD_PRELOAD before I mark the PR ready. There are some annoying bits like different function names for the 64-bit version and Fortran ABI (AFAIK for the purpose of BLAS this is compatible with C ABI, but I need to look into this more)
I saw you said on reddit that you're not planning to add LAPACK APIs, though I don't think a full coverage is necessary. We only need to add the ones faer performs really well in and users can benefit from it with LD_PRELOAD


Publish a new version to use lodash 4.15.0

Hi,
I noticed a commit (https://github.com/jedrichards/rsyncwrapper/commit/8e0662966ae403d9e712449e612c6fe3ee7b1e72) which updated the lodash version to 4.15.0.
Do you mind publishing a new version based on this commit? I'm using lodash 4.15.0 everywhere in my project. It will save me a lot time if you could do kindly do this.
Thanks!
Matthew

Ah yeah, of course 👍


Turning EZSwipeController into a UINavigationController

I ran into a problem with pushing and popping VC's in the EZSwipe hierarchy.
I've seen some suggestions on here with embedding the EZSwipe in a UINavigationController. I've tried that and it seems to not play nicely with the EZSwipe nav bar. What I think would be really nice is if we actually made the EZSwipe itself a nav controller, and make it smart enough to know which VC in the stack had a VC pushed to it, and we could ideally use the EZSwipe nav bar as the same nav bar used when pushing/popping to the navigation stack.
Lets take a 2 VC example where you have a profile (left) and a messages (right) VC. In your messages VC, you want to be able to click on a conversation with someone and simply push that conversation VC to the stack.
I've seen how the standard EZSwipe is:
app->ezswipe
ezswipe->profileVC
ezswipe->messagesVC
Also I've seen suggested if you want to push/pop VC's:
app->ezswipe
ezswipe->profileVC
ezswipe->navigation controller->messagesVC
The problem with this in my experience so far is that when you push/pop in the messages VC it doesnt play nicely with the EZswipe. For example, if you click on a message and push a conversation VC to your nav stack, the user will still be able to swipe right and navigate to the profile VC. In my opinion, if you swipe right you should dismiss the conversationVC and be back at the messagesVC (then swipe right again to get to your profileVC.
I'm playing around with it now, but what would the implications be if we actually made the EZSwipeController inherit from the UINavigationController class as opposed to a UIViewController class?
If we could make it so you can push/pop anywhere in the EZSwipe and the VC would know how to handle it.

https://github.com/goktugyil/EZSwipeController/issues/13
this might help out

I saw that, but couldn't end up getting:
app->ezswipe
ezswipe->profileVC
ezswipe->navigation controller->messagesVC
to work nicely.
How I've got it going now, is I've put my EZSwipe VC in a nav controller. Then, in the standard swipe mode I use the EZswipe nav bar, and HIDE the navigation controller nav bar. Then when a user selects a message, I unhide the navigation controller nav bar and push my VC. This gives it the same feel of a nav, and since the EZswipe is contained in the nav, I end up getting the swipe right gesture to navigate back when I push/pop VC's which is nice.
It works alright, but still not as slick as I think it could be.
I tried making the EZswipe itself a nav controller and was seeing some wonky behaviour when pushing/popping and unfortunately need to ship tomorrow. I'll update this issue if I end up getting it working correctly.


[Task] Implement all controller features from the DID Spec

Description
Add all controller features to the framework as they are mentioned in the DID specification. This includes the DID Document controller field and the controller fields inside of verification methods / relationships.
Motivation
Allows the creation of identities that are managed by other identities.
Resources
Link to any resources relevant for the task such as Issues, PRs, reference implementations, or specifications.

DID Controller field
DID Controller inside verification methods
DID Controller discussions

To-do list
Create a task-specific to-do list . Please link PRs that match the To-do list item behind the item after it has been submitted.

[ ] Allow controllers to sign DID Messages (During validation).
[ ] Research how to deal with circular DID Controllers (a controls b, b control a).
[ ] Provide an API for signing a DID Message that you control.
[ ] Provide an API for adding / removing controllers to DID Documents and verification methods / relationships.
[ ] Add tests.
[ ] Add example.
[ ] WASM Bindings.

Change checklist
Add an x to the boxes that are relevant to your changes, and delete any items that are not.

[ ] The feature or fix is implemented in Rust and across all bindings whereas possible.
[ ] The feature or fix has sufficient testing coverage
[ ] All tests and examples build and run locally as expected
[ ] Every piece of code has been document according to the documentation guidelines.
[ ] If conceptual documentation (mdbook) and examples highlighting the feature exist, they are properly updated.
[ ] If the feature is not currently documented, a documentation task Issue has been opened to address this.

There are several obstacles to implementing controllers right now due to having to resolve the entire history of a DID. Verifying signatures on both integration chain and diff chain updates from controllers require resolving the controller DID document (for every controller in its history); if the referenced verification method was changed or removed, the signature verification will fail. To solve this we would need to pin signatures to a specific version/hash of a DID document.
This was partially addressed in #458 by allowing embedding verification methods from controllers directly, and allowing the verification method controller property to be set, referencing the controlling DID without needing to resolve it.

This issue is still on hold due to technical limitations with the current DID method.
The planned UTXO DID Method atop Stardust will see controllers handled at the protocol level rather than the client, since nodes will validate whether or not an address is allowed to update an Alias Output.


schema: Completely drop our JSON Schema 'id' properties

We're using JSON Schema draft-04, as declared by our $schema properties.  In draft-04, the id keyword alters the resolution scope.  But our current $ref values use JSON Pointers with relative references like defs-linux.json#/definitions/Device that ignore the ids.
By draft-07, id has become $id, and the docs say:

The root schema of a JSON Schema document SHOULD contain an "$id" keyword with a URI (containing a scheme).

But since xeipuuv/gojsonschema@83a7f6369d5, including any URI that cannot be retrieved generates an error:
$ ./validate config-schema.json test/config/good/minimal.json
Could not read schema from HTTP, response status is 404 Not Found

While a root id entry would be nice, we don't currently host these anywhere with a useful URI.  We could use GitHub links like this, but then testing pull requests would be difficult.
By draft-07, the purpose of internal $id entries is clearly explained:

Providing a plain name fragment enables a subschema to be relocated within a schema without requiring that JSON Pointer references are updated.

We don't need that, because we control all the references.  In the infrequent event of a subschema move, we can update the consuming references in the same commit.
The draft-07 $ref docs also explain that $ref targets may be URNs:

The URI is not a network locator, only an identifier.  A schema need not be downloadable from the address if it is a network-addressable URL, and implementations SHOULD NOT assume they should perform a network operation when they encounter a network-addressable URI.

I haven't found analogous wording for $id, but it's possible that gojsonschema is being overly agressive with its attempted retrievals.
This commit removes all of our id entries.  The resulting JSON Schema is valid (regardless of where you host it) and does not generate the 404s.
If/when we merge/release this it should address opencontainers/runc#1680.

LGTM

LGTM


"Vâlcea" county is listed in the drop-down menu

Description:
"Vâlcea" county appears in the drop-down menu list alongside the rest of the counties in Romania according to law
Precondition:
The website is up an running.

Step 1
Click on the search bar.

Expected results
The counties list appears in the drop-down menu.

Step 2
Scroll down the list

Expected results
The county appears in the drop-down menu as "Vâlcea".


Pagination in editor very annoying

We have a large site with a lots of folders and files. As soon as there are more then 16 files in the CKEditor, a 'pagingcontrol' is active and a page 2, 3  4 etc. is displayed. Browsing through this pages takes a lot of time (7 sec each time) After you have uploaded a file you don't know exactly on which page the file is located.
Very frustrating to find the right file partly because the uploaded file is not automatically selected. You can't search either. Is it possible to turn off the pagination or raise the number for a page?

Look in the editor config settings.  I believe there is an area to set the pagination to 0 which removes it.

Thanks, i have found the setting and it works!


Resource explorer multi property drop

(Ideally dispatch to Redux PR should take care of this; if there's additional work required, this ticket with cover it)

Above comment is true, closing in favor of that ticket


Cloud Tier - backend storage type rclone not found with v3.61

Describe the bug
I am running seaweedfs with a Cloud Tier using rclone as a storage backend according to the wiki entry Cloud Tier.
Since I´ve upgraded from v3.59 to v3.61, seaweed fails to start. This are the logs:
I0110 00:53:56.944076 master.go:269 current: <IP_ADDRESS>:9333 peers:
I0110 00:53:56.945462 file_util.go:27 Folder /var/folders/q2/4fhm8st91rg0sh4qn4vcjz900000gn/T/ Permission: -rwx------
I0110 00:53:56.946203 file_util.go:27 Folder /var/folders/q2/4fhm8st91rg0sh4qn4vcjz900000gn/T/ Permission: -rwx------
F0110 00:53:56.946956 backend.go:55 backend storage type rclone not found
goroutine 73 [running]:
github.com/seaweedfs/seaweedfs/weed/glog.stacks(0x0)
	/github/workspace/weed/glog/glog.go:768 +0x8c
github.com/seaweedfs/seaweedfs/weed/glog.(*loggingT).output(0x103885d00, 0x3, 0x140004fa620, {0x102c27cd6?, 0x1400076faa8?}, 0x1?, 0x0)
	/github/workspace/weed/glog/glog.go:719 +0x3a4
github.com/seaweedfs/seaweedfs/weed/glog.(*loggingT).printf(0x14000736d28?, 0x6?, {0x10199319f, 0x21}, {0x1400076faa8, 0x1, 0x1})
	/github/workspace/weed/glog/glog.go:657 +0xe8
github.com/seaweedfs/seaweedfs/weed/glog.Fatalf(...)
	/github/workspace/weed/glog/glog.go:1154
github.com/seaweedfs/seaweedfs/weed/storage/backend.LoadConfiguration(0x10387f160)
	/github/workspace/weed/storage/backend/backend.go:55 +0xfc
github.com/seaweedfs/seaweedfs/weed/command.startMaster({0x1400071c150, 0x1400071c168, 0x14000127a60, 0x14000127a60, 0x14000598360, 0x140006a7150, 0x1400071c170, 0x1400071c185, 0x14000598380, 0x1400071c190, ...}, ...)
	/github/workspace/weed/command/master.go:131 +0x34
created by github.com/seaweedfs/seaweedfs/weed/command.runServer in goroutine 1
	/github/workspace/weed/command/server.go:311 +0xb10

System Setup
Start command: ./weed server -s3
Running on: Mac OSx (M1)
Seaweedfs Version: version 30GB 3.61 8ae00e47a6e3adf340cbf00269cebec2dad5ba5e darwin arm64
filer.toml
[leveldb2]
enabled = true
dir = "/data/filerldb2"

backend settings in master.toml
[storage.backend]
[storage.backend.rclone.default]
enabled = true
remote_name = "sbox"
key_template = "SeaweedFS/{{ slice . 0 2 }}/{{ slice . 2 4 }}/{{ slice . 4 }}" # optional

rclone.conf
[sbox]
type = sftp
host = u1234.your-storagebox.de
user = u1234
port = 23
pass = abc123xz
shell_type = unix
md5sum_command = md5 -r
sha1sum_command = sha1 -r

https://github.com/seaweedfs/seaweedfs/commit/7a50762b9ed05f1410a24f52571b49a25cd561eb
Use full version binary without reduce size

Thanks for the fast response.
Unfortunately, the full image is not available for arm64.

Is there a specific reason, why the full version is only available for amd64?

need to set it up.

Hey, I'm facing the same issue, although I'm running on WSL 2. Running dpkg --print-architecture, I get amd64, so hence I've tried installing and running with the following versions (all version 3.6.2):

linux_amd64
linux_amd64_full
linux_amd64_full_large_disk
linux_amd64_large_disk

All of these were run with the same configuration and commands that @legout posted at the start of this thread. Each gives me the same error message of backend storage type rclone not found.
Any suggestions?

As a side note, it doesn't seem to be made clear anywhere what all of the various binary versions are. What's the difference between the base binary, and the full/large disk/full large disk variants?

This should fix the build process bf0899cbf4ccb42e02f5984802d41c5e9b5e90bf


missing images

Updating from Reverie 2 to 3 the Folder "images/devices" in reverie is missing. the one that contains the loading pictures for iPad and iPhone. They are called in "header.php". I also did not found "mobile-load.png" to "Enable Startup Image for iOS Home Screen Web App".

you still haven't uploaded mobile-load.png


More information

Hello guys,
Can we get a bit more documentation on this application?
After downloading, I run it I get the expected "Server running on ..." message.
But then when I run the smarttv app I just get a black screen.
There are any folder requirementes? Should I put the server with something else? Maybe change some configuration? Any infomartion would help.
Thanks

did u get this running somehow? got exact the same problem..


xarray based ParticleFile to support netcdf and zarr output

This PR implements exporting of ParticleFile objects based on creating a xarray.DataSet object, rather than core netcdf routines we used before. The big advantage is that this will make it much easier to also support other file formats such as zarr, because if we first create a DataSet, then it can be trivially exported either with ds.to_netcdf() to ds._tozarr().
As suggested by @JamiePringle in #1164, zarr format may have much better performance in disk space and increased speed. This PR will make it easier to test that for real-world applications
To-do

[X] Implement xarray-based DataSet creation for SOA
[x] Implement xarray-based DataSet creation for AOS
[ ] Also implement on Nodes branch (do you think this is a good idea, @CKehl?)
[x] Add unit tests for zarr to test_particle_file.py
[ ] Clean up code
[ ] Expand tutorials to explain use of zarr

Beyond scope of this PR (but interesting to explore)

[ ] Instead of dumping numpy pickled files to disk during the simulation, @daanreijnders suggested that we could create a zarr directory/file immediately during the pset.execution. That would mean no need for conversion upon completion of execute, and hence would directly fix issues like #1091. To be explored!

Thanks for the response, @CKehl. Note that the implementation now is completely backward-compatible; the code can still output netcdf (this is the default for now) and these netcdf files are exactly the same as is now on the  master branch. To use the new zarr-formatted output, the only thing a user has to do is provide a filename ending on .zarr for the ParticleFile object
And yes, I agree that we have to testdrive Zarr-format in real-world simulations and release version 3.0 before we could ever make this default behavior. But in the meantime, this PR does not break any backward compatibility.

@CKehl and @erikvansebille, a couple of comments on zarr.  Christian is right that zarr writes out compressed files, but the output scheme is more complex than presented above. Each variable has its own directory. How the files within the directory are broken up depends on how the data set is chunked. Chunking is similar in concept to the chunking in netCDF, and how performant reading and writing to zarr is depends on the choice, often significantly. The chunking on the dataset can be changed after it is written, but this can be time consuming.
As I commented, I would default to 10000 trajectories and all observations as the default chunk size, but I am sure this could be optimized (and different choices are optimal for different access patterns -- again, this should be familiar from netCDF).
I would spend a little time reading about why zarr was designed as it was. Essentially, data formats like hdf5 (the core of netCDF4) have re-implemented a filesystem. In zarr, you let the heavily optimized file system of your computer act as a file system. This makes it much easier to share data over the network from cloud services, and allows much more graceful parallel writing of data and out-of-order output, especially for compressed data.  For my large problem sizes, both of these are very, very useful.
Also, your file system is often better optimized for the actual physical layout of the storage than something like netCDF4/hdf5 could ever be. (but note that netCDF is starting to implement a zarr backend, and people are working on using zarr and netCDF together... Rich Signell is a good person to follow on this).
One way to look at why Zarr was designed the way it was is to look at these hints for optimal creation of netCDF: https://www.unidata.ucar.edu/software/netcdf/workshops/2011/performance/Time.html . Much of the design of Zarr was to avoid having to worry about this (except for the choice of chunking).
I am happy to talk more about the tradeoffs of Zarr versus netCDF4, but I think Zarr is a carefully designed data store that has many advantages (and some disadvantages) relative to netCDF, and there is a reason many of us who work with very large data sets are attracted to it.

Thanks for this extensive write-up, @JamiePringle. What you say makes a lot of sense, I'm glad that we now implemented native zarr output through xarray in this PR; can you give a go and see how it behaves?
Note that this PR does not include your optimized writing in #1091, we may think of including that too?
And in the future, we might even swap the *.npy temporary output for native .zarr output during execution, so that users who prefer netcdf output can still convert at the end but don't have to anymore. All with full backward compatibility. Exciting!

I will try the patch request sometime this week.
I think it would be non-trivial to move my #1091 code into parcels. The main issue is that a single *.npy contain drifter output from different  times. I am not sure how it happens, but it does. But much of my code in #1091 deals with that.  Also my code saves memory by analyzing each MPI rank by itself... that is harder to do when they are all running in real time.
I agree that writing straight to zarr or netCDF from parcels would be great. Every time I have done parallel IO I have found that 1) you can make it work and 2) it takes significantly longer than expected.
I might start by having each rank write to their own Zarr files, and then merging them afterwards.
I will try to say something more intelligent after I look at the code that writes out the *.npy files -- there are some odd things in how time ends up in them that I need to understand before being able to talk sensibly about this...
Jamie

Thanks @JamiePringle! I understand that MPI support for on-the-fly zarr dumping may be tricky, but going for one zarr directory per node would be a good start

The main issue is that a single *.npy contain drifter output from different times. I am not sure how it happens, but it does.

This is probably because particles are being deleted between time-outputdt/2 and time+outputdt/2.
See the collectionsoa._to_write_particles() function:
https://github.com/OceanParcels/parcels/blob/523a37227364fb2a3b6dfcf1904e3a487ce3c03b/parcels/collection/collectionsoa.py#L29-L37
which controls which particles are dumped to dict at
https://github.com/OceanParcels/parcels/blob/523a37227364fb2a3b6dfcf1904e3a487ce3c03b/parcels/collection/collectionsoa.py#L849
Does this help? If you don't delete particles, are all the times in a single *.npy file the same?

@erikvansebille -- I am buried with reviews and end of term stuff now. I will check if keeping particles from deleting eliminates this problem, but won't be able to do until later this week or Monday. I also wonder if the issue might be the precise equality of your tests and the rounding errors... All of the time to die, release time intervals and write time intervals are multiples of each other...
Anyway, I will let you know what I find in half a week or so.
One last thought -- when writing to Zarr, it may make sense to arrange chunking to optimize writing many trajectories at a single observation, and then re-chunk on conversion.  The current output scheme is a little tricky, because your current scheme has each trajectory start at obs=0 at the first time it is written.  I think that is a fine scheme, but it means at each output step you can write to many different observations. Given that observations that contain no data do not take up much space in zarr (because a uniform set of nan's or any other constant value will compress very well), perhaps in the temporary output having output by (trajectory,output_time_step) might make things much faster, because you can then write to many_trajectories, one_output_timestep in a single operation... This is essentially what you almost do in the npy files...
Jamie

@erikvansebille Indeed, the issue goes away if the particles do not die but live forever. I strongly suspect the issue has to do with the exact equality check... but it is still odd, because the issue pops up in the middle of a string of outputs... for example, the time since release of one of the outputs (converted to days by dividing by 86400), looks like this
       28.75      , 29.        , 29.25      , 29.5       , 29.75      ,
       30.        , 30.25      , 30.5       ,         nan, 30.75      ,
       31.        , 31.04166667]

Where the sequence of numbers is from the a sequence of *.npy files (your current output code handles this perfectly, and the gap is not in the netCDF file). I start particles every half day, and write out every quarter day. It is still unclear to me why the output for some particles skips a step. However, all particles that start at the same time skip the same *.npy
I will investigate later, but it is not a big deal because all of our codes handle it properly.
Jamie

Hi @JamiePringle. I don't use pip myself but guess you 'only' have to go to the directory where parcels is installed and then use git checkout xarray_based_output (see also https://git-scm.com/docs/git-checkout)

That gave me the hint I needed. The pip command is
pip install git+https://github.com/OceanParcels/parcels.git@xarray_based_output

Another way to easily install a package from repo, is to clone the repo, switch to the branch that you're working from, and by using pip install -e .. This will install the package in 'editable' mode: any changes you make will immediately be available in Python, while at the same time, all scripts (e.g. the one to convert .npy to .nc) are installed correctly.

@erikvansebille I tested your code on my runs, and it did what it was supposed to and produced a zarr output. The default chunking it picked was fine for most access patterns.   Like all of these schemes (including netCDF) if you know exactly how you will most often access the data, you can do better by altering the chunking scheme (which is easy enough to do with the rechunker package).

Thanks @JamiePringle, great to hear that the code works for you. Since it's completely backward-compatible, I then suggest we merge it into master. I've just also added information on Barr in the tutorial_output.ipynb tutorial.


Font size on the bottom pane is incorrect

font size on the bottom pane is incorrect,this problem is NOT happening with official themes including "One dark"and"Atom Dark" under the same situation,adjust the UI font size in theme config does work to the whole UI but the part i mentioned.
Expected behavior:
it should be like the screenshot in the README
Observed behavior:
just..that small,the font of directory/CRLF/filetype/encoing on the bottom is so small and nearly unreadable,but for the panes it goes alright.
the following is mine

this is the official one,it is obviously bigger and clear

Atom version: 1.7.3
OS and version: fedora23，gnome 3 with infinality installed
Installed packages:
Community Packages (6) /home/link/.atom/packages
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>Additional information:

Problem can be reproduced in safe mode: [Yes/No]Yes
Problem started happening recently, didn't happen in an older version of Atom: [Yes/No] No
Problem can be reliably reproduced, doesn't happen randomly: [Yes/No] Yes
Problem happens with all files and projects, not only some files or projects: [Yes/No]Yes

Not exactly a bug, but the screenshot in the README is outdated. If you want to increase the font-size use this snippet in your user stylesheet:
.theme-atom-material-ui status-bar {
    font-size: 0.75rem;
}

Cheers!


[release-1.8] Add ECC_SIGNATURE_ALGORITHM env integration test (#28894)

Fixes https://github.com/istio/istio/pull/28894
Cherry-pick of https://github.com/istio/istio/pull/28894 via sha 5a5c0ebf40d232d0886389d4b6a74976dba87a14

Add integration test for ECC_SIGNATURE_ALGORITHM

There was a previous regression when specifying ECC_SIGNATURE_ALGORITHM,
see https://github.com/istio/istio/pull/25203.
Setup:

A test namespace is created
A client and server Echo deployment is created in this namespace
The appropriate PeerAuthentication and DestinationRule resources are
set so that mTLS is strict and used
The root CA is not altered and it will use a generated certificate
using RSA. Due to https://github.com/istio/istio/pull/27239, the
root CA no longer has to ECC to enable ECC_SIGNATURE_ALGORITHM. This has
the benefit of additional testing as well.

Test:

The client sends a request to the server deployment to make sure
communication works inside of the mesh when using ECC certificates.
Using kubectl/openssl, the client then gets the certificate from the
server deployment. It then verifies that the certificate is using ECC,
notably ECDSA, algorithms.

Add license to top of file; lint errors

Run make gen

Fix linting issue

Add proper feature label

Fix name of feature

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[X] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[X] Does not have any changes that may affect Istio users.

@jacob-delgado: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

analyze-tests_istio_release-1.8
797d095bd42e3bd7e5f57820c40dcc7b91d122bf
link
/test analyze-tests_istio_release-1.8

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

analyze-tests_istio_release-1.8
797d095bd42e3bd7e5f57820c40dcc7b91d122bf
link
/test analyze-tests_istio_release-1.8

integ-security-k8s-tests_istio_release-1.8
797d095bd42e3bd7e5f57820c40dcc7b91d122bf
link
/test integ-security-k8s-tests_istio_release-1.8

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

analyze-tests_istio_release-1.8
797d095bd42e3bd7e5f57820c40dcc7b91d122bf
link
/test analyze-tests_istio_release-1.8

integ-security-k8s-tests_istio_release-1.8
797d095bd42e3bd7e5f57820c40dcc7b91d122bf
link
/test integ-security-k8s-tests_istio_release-1.8

integ-security-multicluster-tests_istio_release-1.8
797d095bd42e3bd7e5f57820c40dcc7b91d122bf
link
/test integ-security-multicluster-tests_istio_release-1.8

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio_release-1.8
797d095bd42e3bd7e5f57820c40dcc7b91d122bf
link
/test integ-security-k8s-tests_istio_release-1.8

integ-security-multicluster-tests_istio_release-1.8
797d095bd42e3bd7e5f57820c40dcc7b91d122bf
link
/test integ-security-multicluster-tests_istio_release-1.8

integ-pilot-multicluster-tests_istio_release-1.8
fb3d6c6878385965ddf7b4a8aca6e99a68f60ad9
link
/test integ-pilot-multicluster-tests_istio_release-1.8

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-pilot-multicluster-tests_istio_release-1.8


Compiler issues invalid error: non constant expression in initialization

[Shaders, screenshots, error log, reproduction steps, etc.] [ZIP]
This code:
#version 440

void main(void)
{
  vec4 A[2] = vec4[2](vec4(1.0), vec4((vec2(1.0) * mat2(1.0)).x));
  int x = 1;
  vec4 y = vec4(A[x].z);
}

is accepted by glslangValidator (and also a recent Intel driver).
The NVIDIA compiler erroneously gives an error:
LINK_ERROR
Vertex info
-----------
0(2) : warning C7555: 'attribute' is deprecated, use 'in/out' instead

Fragment info
-------------
0(7) : error C1059: non constant expression in initialization

Filed bug report to NVIDIA:
https://devtalk.nvidia.com/default/topic/978833/opengl/-bug-compile-error-quot-non-constant-expression-in-initialization-quot-/

Shader now compiles successfully in driver version 378.66.


Matt

Line 149 to 157, there is a for loop to find all account documents and show a list of it. The i was incremented too early and it was causing the first value to not be shown (Found out about it testing it alone, so of course only 1 account). Basically the first account is never shown.

I guess you're right, thank you very much.


fix(chips): Final Design QA

https://flo-scss-finish-chips-r7hl20np.herokuapp.com/docs/components/chips/

On the hover state, we need to keep the text color and background color the same. No border color. Only the circle around the "x" has a color change. Light color (non-hover) is grey-500, and hover is grey-600.
Can remove linear-gradient on hover

And we can remove Watch "Live" and Event "Flosports" examples from the docs because it could be confusing.

For all of the chips under examples, we need to remove the gradients on those. Just keep the first color and keep it flat.
(Primary, Secondary, Success) etc.

chips
Need to add combined components that make up our brand chip
chip grey-300
with close icon
!

Need to add combined components to display the flobrand chip

TODO

Update chips radius from 17px to 16px

Update chip text color to $gray-600

Fix sizing issues height should be 32px
** Chrome renders 30.07px
** Firefox renders 31.2px
** Safari renders 30px

Update documentation separating what is part of the FloSports brand from what System Extras are inherited from forking Bootstrap 4

Here is the updated markdown with TODO notes.
chips.md.zip

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


WebSocket patch on Android causes infinite recursion

It looks like when canPatchViaPropertyDescriptor() is false, WebSocket's addEventListener is patched again: property-descriptor.ts#L29, websocket.ts#L6 after already being patched as part of browser.ts#L27.
Setting any of the WebSocket event handlers then causes infinite recursion as the "original" handler that gets called by the second patch is the already patched one from when the EventTarget handlers were patched: utils.ts#L86
You can reproduce minimally on desktop Chrome by breaking on property-descriptor.ts#L14 and having it return false: http://plnkr.co/edit/XF2mZMA6XBHuApVz6BJ4?p=preview (line 736 for me).
We had reports of this happening on Android 4.4 and 5.1, but I've only been able to reproduce on device with 4.4, though in theory it would happen for any devices where patching via property descriptors is unavailable.
Happy to submit a PR, but there is a lot going on between various different browsers and I'm not entirely sure what the best solution that wouldn't break other things is.

thanks @tlancina for this patch :+1:


Consolidate multiple runtimes into a single builder

When using the pack CLI you can ask for suggested builders from within a project directory. The CLI will respond accordingly. Note how the builders are able to handle multiple runtimes.
~/demo/quarkus
❯ pack suggest-builders
Suggested builders:
	Google:                gcr.io/buildpacks/builder:v1      Ubuntu 18 base image with buildpacks for .NET, Go, Java, Node.js, and Python
	Heroku:                heroku/buildpacks:18              heroku-18 base image with buildpacks for Ruby, Java, Node.js, Python, Golang, & PHP
	Paketo Buildpacks:     paketobuildpacks/builder:base     Ubuntu bionic base image with buildpacks for Java, NodeJS and Golang
	Paketo Buildpacks:     paketobuildpacks/builder:full     Ubuntu bionic base image with buildpacks for Java, .NET, NodeJS, Golang, PHP, HTTPD and NGINX
	Paketo Buildpacks:     paketobuildpacks/builder:tiny     Tiny base image (bionic build image, distroless run image) with buildpacks for Golang

Tip: Learn more about a specific builder with:
	pack inspect-builder <builder-image>

Based on in person conversations, we have decided not to pursue this route. Closing.


Better emulate read_default_file DB config parsing

Fixes #773

Arguably all of the database config setting parsing code (not just that for mysql, and not just these two commands) should be unified into a single place, but that's a much more extensive change with greater risk of breaking other things so I went with the simpler option.

Could you please move the management/commands/_private.py file to management/mysql.py ?
That way we don't have none-command files in the commands/ directory.

Thanks !


feat: Safari Web Extension

Description
I don't have enough experience in contributing and pull-requests, so I would be thankful for help.
It adds possibility to build Safari Web Extension that works similar to Chrome extension #1139
Tested with Safari Technology Preview (Safari 16.0) on Mac OS 12.4.
Builded with Xcode 14 beta 3
Safari 16 and Xcode 14 allow us to write extension with a Web Inspector tab feature.
Added shell-safari folder based on shell-chrome folder, just replaced chrome.* with browser.* in some code lines.
Added shell-safari/app folder with Xcode Safari Web Extension Folder.
Added some scripts to package.json for building the extension app
How to build extension

yarn build
cd packages/shell-safari
yarn safari
Builded extension app: packages/shell-safari/app/extension/VueDevTools.app

P.S. To see extension from Safari preferences you should activate Develop/Allow Unsigned Extensions. To avoid this, the extension must be signed with Apple Developer Account.

Additional context
I guess, it should use same code base for Chrome and Safari (with chrome.* and browser.* difference), but I think it should be done by main developers of this repository.

What is the purpose of this pull request?

[ ] Bug fix
[X] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[X] Read the Contributing Guidelines.
[X] Read the Pull Request Guidelines and follow the Commit Convention.
[X] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[X] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).

We should try to reuse the chrome folder instead of duplicating code I guess

Are there any news?


added pkgin to BSD case

Description
Added a pkgin to Package manager programs under BSD

On NetBSD neofetch only showed pkg_* packages with pkg_info. Now it also shows pkgin packages.


Merging various changes/fixes into method-alra

Note that these changes encompass most of the changes needed to get ALRA working, but run-benchmarks is still not working correctly. Merging the current version will allow a subsequent working/fixed merge to happen frictionlessly in the near term.

This PR looks quite challenging to review with most of the 84 files probably edited due to merging from main. Would you be able to rebase this PR to the current tip of the main branch?

@wes-lewis I changed the PR to point at main and merged latest changes. Tests are still failing due to some problem with non-conformable arguments to SVD.

@wes-lewis looks like the error is here: https://github.com/wes-lewis/SingleCellOpenProblems/runs/5994099756?check_suite_focus=true#step:14:925
NotImplementedError: Failed to write value for obsm/denoised, since a writer for type <class 'scipy.sparse._coo.coo_matrix'> has not been implemented yet.

So all you need to do is call .tocsr() on the matrix you put into obsm['denoised'].

I fixed this error in my own branch and now have another error, this time regarding size mismatch.
https://github.com/wes-lewis/SingleCellOpenProblems/runs/6083855173?check_suite_focus=true

Codecov Report

Merging #353 (3104532) into main (0e17517) will increase coverage by 3.01%.
The diff coverage is 50.00%.

:exclamation: Current head 3104532 differs from pull request most recent head 0a6bd4e. Consider uploading reports for the commit 0a6bd4e to get more accurate results

@@            Coverage Diff             @@
##             main     #353      +/-   ##
==========================================
+ Coverage   88.42%   91.43%   +3.01%
==========================================
  Files          77       76       -1
  Lines        1685     1647      -38
  Branches       94       95       +1
==========================================
+ Hits         1490     1506      +16
+ Misses        167      112      -55
- Partials       28       29       +1

Flag
Coverage Δ

unittests
91.43% <50.00%> (+3.01%)
:arrow_up:

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

Impacted Files
Coverage Δ

openproblems/tasks/denoising/methods/alra.py
87.50% <50.00%> (+87.50%)
:arrow_up:

...nproblems/tasks/multimodal_data_integration/api.py
100.00% <0.00%> (ø)

.../tasks/multimodal_data_integration/methods/scot.py

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 0e17517...0a6bd4e. Read the comment docs.

@wes-lewis can you rerun the latest actions run on your repo? I think that tower error was my fault, I've updated your permissions.


encode error when open file

When starting with 'streamlit run demo_page.py', you may encounter the following error: "UnicodeDecodeError: 'gbk' codec can't decode byte 0xae in position 2: illegal multibyte sequence".
To resolve this issue, it is recommended to change the encoding when opening the file. You can do this by modifying your code as follows:
the file path: EmotiVoice/config/joint/config.py
#### Speaker ####
with open(speaker2id_path, encoding='utf-8') as f:
    speakers = [t.strip() for t in f.readlines()]
speaker_n_labels = len(speakers)

我也遇到这个问题了，改了不起作用呢

好像可以了

I think you can find solution here:

The bug has already been fixed. Please update and give it a try.


BE AS CLEAR AND CONCISE AS POSSIBLE.
problem
must scroll down to see the current date unless its early in the month
solution
is it possible to make the first raw of days - the current week?
alternatives (optional)
have you tried to do this yourself? have you seen it done somewhere else?
would a different feature remove the need for this?

it's possible to automatically scroll down, but that means if you wanted to see the filter/sort/new buttons you have to scroll back up, which can be just as annoying.
what i will do is add a button to scroll down for you (assuming today is loaded on the calendar).


pkg: get Maintainers data

Created a struct to store maintainers' data (email, name, type...) and
modified functions on pkg/vcs and pkg/report to parse this data and
store in the RecipientInfo struct

Before sending a pull request, please review Contribution Guidelines:
https://github.com/google/syzkaller/blob/master/docs/contributing.md

Please rebase this on top of latest HEAD. Your branch is almost 200 commits behind. In particular CI does not run all checks we have now and also fails on coverage, which it should not do on HEAD.

I fixed the parsing problems and added some new functions. Can you please take another look?

Please rebase this on top of latest HEAD. Your branch is almost 200 commits behind. In particular CI does not run all checks we have now and also fails on coverage, which it should not do on HEAD.

The branch still seems to be lagging behind.

Add Update #1534 to the commit description, it's a special syntax understood by github to create cross-links.

We are getting close. @ebiggers please take a look as well, I will leave the exact criteria for to/cc selection to you.

I looked at all files except for dashboard/app/*, and they look good to me.

@ebiggers FYI: we discussed that it will be better to do a minimal change to dashboard/app: take recipients in new format and immediately convert them to the old format in the dashboard/app/api.go.
Then we can merge this change and start deploying (dashboard, then syz-manager and syz-ci) and it should not affect any tests.

I changed the dashboard/app commit so it would only make a minimal change. Can you take another look?

@ebiggers I will wait for your stamp to start deploying this.

I will proceed with deployment. If there are any follow ups, let's handle them in separate commits.

This change is deployed to the syzbot dashboard app.
syz-ci instances will start picking it up with 1-24 hours on their own pace, the current syz-ci instance commits can be checked at:
https://syzkaller.appspot.com/upstream
Once all instances pick it up, we may proceed to deploying subsequent dashboard changes and dashapi cleanup.


Support MySQL Prefix Index ("Partial Index", string index with length)

Bug description
Hello,
I have noticed that unique constraints don't get introspected, and if manually added, they vanish at consecutive re-introspections.
How to reproduce
Have a MySQL table that looks like this:

CREATE TABLE Item {
  `categoryId` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
   UNIQUE KEY `categoryId_UNIQUE` (`categoryId`(191)),
}

run introspection.
Expected behavior
It should introspect the unique constraints normally. It should not remove them once introspection is run again.
Prisma information
model Item {
 categoryId    String?    @db.VarChar(255);
}

Environment & setup

OS: Ubuntu v18.04
Database: MySQL 5.7
Node.js version: v14.15.1

Prisma Version
prisma               : 2.19.0
@prisma/client       : Not found
Current platform     : debian-openssl-1.1.x
Query Engine         : query-engine c1455d0b443d66b0d9db9bcb1bb9ee0d5bbc511d (at<EMAIL_ADDRESS>Migration Engine     : migration-engine-cli c1455d0b443d66b0d9db9bcb1bb9ee0d5bbc511d (at<EMAIL_ADDRESS>Introspection Engine : introspection-core c1455d0b443d66b0d9db9bcb1bb9ee0d5bbc511d (at<EMAIL_ADDRESS>Format Binary        : prisma-fmt c1455d0b443d66b0d9db9bcb1bb9ee0d5bbc511d (at<EMAIL_ADDRESS>Studio               : 0.358.0

Looks like we don't support unique keys right now with introspect and only unique indexes. I am going to mark this as a bug for now for team to decide if this was a miss or this is a bug.

This is a "prefix index" (string field with length) in MySQL (Documentation at https://dev.mysql.com/doc/refman/8.0/en/create-index.html, headline "Column Prefix Key Parts
" or https://www.mysqltutorial.org/mysql-index/mysql-prefix-index/) that we unfortunately do not support in Introspection and Migration yet.
From the documentation it seems that you could in theory update your database to not have that length on the unique index any more, then Prisma should just pick that up. Can you try that maybe?
Otherwise unfortunately the only workaround is to add the @unique to the field manually right now and make sure it stays after each future Introspection.

We've just released a proposal to add support for this in the PSL. Please chime in here: https://github.com/prisma/prisma/issues/9577

Since 3.5 we now offer the ability to introspect and migrate length limited indexes using the extendedIndexes preview flag. Can you please try it out?

(If you are looking for partial or filtered or conditional unique indexes or constraints, this is the right issue: https://github.com/prisma/prisma/issues/6974)


Get underlying dataSource via unwrap method

Before this commit, there is no way to get underlying ds.
Is this or adding extra getter method better? WDYT @malafeev ?

Pull Request Test Coverage Report for Build 276

4 of 4 (100.0%)  changed or added relevant lines in 1 file are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.2%) to 47.919%

Files with Coverage Reduction
New Missed Lines
%

src/main/java/io/opentracing/contrib/jdbc/TracingDataSource.java
2
52.27%

Totals

Change from base Build 275:
0.2%

Covered Lines:
472

Relevant Lines:
985

💛  - Coveralls

I think getter is better

I think getter is better

done


Feature - Ignore list for elements to be omitted from renderer

A feature that can omit certain HTML elements from being rendered
for example
html2canvas(element, { ..., ignore: [".some-class", "#some-id"], ... });
will remove elements matching the ignore array but leave the DOM unaffected.
I have added this feature here
https://github.com/nchinan/html2canvas/commit/62c665c4acf20b1d8924da7bbb4c21335217c0ed
I would like to hear your feedback and suggestions
Regards
Neville

I'm noticing that with data-html2canvas-ignore, the element is hidden but not actually removed. The result being that there's an empty white space that's left behind where the element used to show. Is there a good way to actually remove that element form the canvas so that there isn't that ugly white space left behind?

See above comment--the way to do this would be to use the onclone option to modify the cloned document (e.g. set a class or style on the element that does display: none, or just remove said element) before rendering happens. The data-html2canvas-ignore doesn't do that by default as it would cause a reflow (expensive) and possibly also significantly change page rendering in unexpected ways.

Great, thanks. Still having some margin issues on the rendered image but this seems to work as intended. Example:
html2canvas($("body"), {
onclone: function(document) {
if (options.elementsToIgnore.length) {
for (var i = 0; i < options.elementsToIgnore.length; i++) {
$(document).find(options.elementsToIgnore[i]).remove();
}
}
}}).then(function(canvas) {
var imgData = canvas.toDataURL('image/png');
var doc = new jsPDF('p', 'pt', 'a4');
doc.addImage(imgData, 'PNG', 0, 0);
doc.save('sample-file.pdf'); //creates a pdf
}).catch(function(error) {
done(error);
});

For me its still showing that whitespace. When I add element which I have to show as image then its fine but when I add it with another element then whitespace is being added for ignored element. I tried to remove it from DOM also but no luck


Suggestion: integrate language support within lunr.js

Just a suggestion, but multiple language support within lunr.js would be pretty neat.
There is a good repo out there, https://github.com/MihaiValentin/lunr-languages, but unfortunately it's not maintained and there are many good pull requests going unanswered:
https://github.com/MihaiValentin/lunr-languages/pull/11
https://github.com/MihaiValentin/lunr-languages/pull/14
https://github.com/MihaiValentin/lunr-languages/pull/15
Perhaps it would be possible to assimilate the repo. This would provide a central, maintained place for people to submit PRs and improvements.

Update: The lunr-languages repo maintainer has merged most pull request after I nudged him. I still think a merge would be worthwhile but I understand that the effort involved is not non significant.

First, thanks to @MihaiValentin for giving his time in creating and maintaining the lunr-languages project, its really helped increase the usage of lunr.
I'd rather not have the language extensions in the main repository, I think they should be stored, built and released separately from the main project. That said, I would like to have the lunr-languages project (or something derived from it) be a more official part of lunr.
I'm currently working on some fairly large changes to lunr, and as part of this I think I want to look at moving ownership from my own account to some lunr organisation. My hope is to make it as easy as possible to bring other contributors on board. As part of that I'd like to have a language extensions project part of that organisation, and be able to grant commit access to a group of people more able than me to maintain the languages project, I hope that @MihaiValentin would consider helping with that effort.

I think that's a fantastic idea. I'd be following and contributing what I can! Hopefully @MihaiValentin would be on board with that as well.


Saving Flow and Pose models separately during training

@Yuliang-Zou Currently the training saves the complete session (depth, flow and pose) in the checkpoint. Is there any option to save the learned flow model and pose model separately?

Oh I did not make that option. But it should be able to do so if you create separate savers here, and modify the save function accordingly here.


update admin docs to include inventory plugin

update admin docs to include the ansible collection. ref: nofusscomputing/projects/ansible/collections/centurion_erp_collection!2

mentioned in commit a4b37b34a91e0fb7416d889d508d1851c3bf108d

work to be done in !45

mentioned in commit 3993cc96a5cc61b0ed455f2d2b0c21af100fe8c4

mentioned in merge request nofusscomputing/projects/ansible/collections/centurion_erp_collection!2


Don't fill Eclipse project with a ton of empty directories when adding managed directories to classpath

Thanks to @oleastre for tracking down this problem in https://github.com/playframework/playframework/pull/4074#issuecomment-78450169
Also fixes the issue reported in https://github.com/typesafehub/sbteclipse/issues/99

LGTM

My only concern is what happens if it's an all-fresh Sbt project. Then none of src/main or src/test will exist, right? So Eclipse won't have any configured source directories...

If you create the project using activator or from another template then you will have src/main and src/test which is probably the best way to handle and what we recommend most often. I'm not sure sbteclipse's job is to create a template project. It's probably better if it just does one thing and reflects what you have already.

Well, in that case one other answer is that sbteclipse should just do what it does: reflect exactly what Sbt knows about source directories. If you don't need some source directory, remove that from your build definition. :)
I don't feel like arguing too much, I'm fine with this change as is

Thanks!!


Wrong characters with converted font

Hello!
I have a font in .ttf format and used the font converter to get the font .js file. I added it into the HTML after jspdf.js and before my main.js, like this:
<script type="text/javascript" src="js/jspdf.js"></script>
<script type="text/javascript" src="js/Helvetica-Neue-normal.js"></script>
<script type="text/javascript" src="js/main.js"></script>

This is the content of my main.js
var doc = new jsPDF({
	orientation: "portrait",
	unit: "mm",
	format: "a4",
	putOnlyUsedFonts: true
})
doc.setFont("Helvetica-Neue");
doc.setFontStyle("normal");
doc.text("Test", 10, 10);
doc.save("test.pdf");

But this is the result in the test.pdf

In the console log of the HTML I get this:
jsPDF PubSub Error Cannot use 'in' operator to search for '0' in undefined TypeError: Cannot use 'in' operator to search for '0' in undefined
    at GlyfTable.glyphFor (jspdf.js:24131)
    at Subset.glyphsFor (jspdf.js:24525)
    at Subset.encode (jspdf.js:24562)
    at identityHFunction (jspdf.js:15308)
    at Object.<anonymous> (jspdf.js:15375)
    at PubSub.publish (jspdf.js:441)
    at putFont (jspdf.js:1308)
    at putFonts (jspdf.js:1337)
    at putResources (jspdf.js:1362)
    at API.__private__.buildDocument (jspdf.js:1912)

I don't know what could be wrong.
Thanks!
Edit: I tested with PT_Sans font like in your example and it works fine. What I don't understand is why the fonts I'm trying to use doesn't work. The fonts are "Helvetica Neue" and "ITC Charter". Both produces the same result.

Have to have a look into it. Where could I download the Helvetica Neue?

I uploaded it for you.
Helvetica Neue
ITC Charter
Thanks!

I'm also seeing a similar problem with a non standard font. Happy to provide working example or the offending font if that's helpful.

I am having this issue as well with a google font I manually imported ( imported with base64 method into vfs and all ) and this is happening to me also. I have placeholder english text added to the doc and the text output within the PDF file is all gibberish; e.g. DAD124 DJFIA JDOKAOI KALSKO SOIDSF JONAOWUM ASU AOSUW VXBCO UMWOQW etc etc...
I reimported the font and now it's not even appearing; no warnings or errors.


archive repo

This has been moved to https://github.com/wasmCloud/wasmcloud and should be archived. Please transfer issues as well

Archival pending https://github.com/wasmCloud/control-interface-client/pull/67


Configurable channels for multi channel types (like rgb or color_temp)

Right now (v0.1.17) there is always a distance of 1 between each channel for a multi channel type.
Let's take the example from the readme:
- channel: 3
name: my_rgb_lamp
type: rgb
transition: 1
channel_size: 16bit
output_correction: quadratic
channel_setup: rbgw           # Auto-calculated white channel
Although the channel_size is 16bit, channels 3, 4 and 5 will be used for red, green and blue. It would be correct to use 3, 5 and 7. (At least with my DMX controllers. But I guess this is always like this.) So I can just use single channels or need to use 8bit size.
In my oppinion it would be even better to let me configure those channels. I have some rare cases where the channels are not in a row (e.g. red=1, blue = 5, green = 11).

I have just realised that this might be an explanation for issue #46 Transition is flickering.

On further testing I noticed that this works fine although it gets displayd wrong. I have an rgb light using the 16 bit channels 409/411/413 and it works as expected. But in the guy it looks like this:


Tags for versions

Hi,
it seems like you haven't created tags for the versions 3.0.2 and 3.0.3. I find these versions on NPM. Could you create these missing tags please?
Thanks

Pushed these tags :)

The master branch has moved since 3.0.3, functionally still the same, but documentation and test cases have been refactored heavily. This will get released as 3.1.0.
If you want to make changes, I will suggest you pick this version as base, you are likely to find it easier.

Planning for next version of stompjs is on the way. Your participation will be really appreciated, please join at https://github.com/stomp-js/stompjs/issues/1


Add Timeout to constructor for ElasticConnection

…default value

Thanks for merging this in so quickly! It would be appreciated if you could publish a new version of the library soon since I'd rather depend on your published version than our own local copy.

Done

On Oct 15, 2015, at 6:01 PM, Ben Franklin<EMAIL_ADDRESS>wrote:
Thanks for merging this in so quickly! It would be appreciated if you could publish a new version of the library soon since I'd rather depend on your published version than our own local copy.
—
Reply to this email directly or view it on GitHub.


Feature/managed customer

Added description how to create managed customer as a partner and how to add users to this account.

closed via https://github.com/Meshcloud/meshcloud-docs/commit/de28e5181dd2d2997b33ccf6857b5361ec8a39b6


Add control vpc_with_no_eni

Checklist

[ ] Issue(s) linked

It does not have any cost implication.


Backport spec.users.passwd should be optional/omitempty

Relevant v1alpha3 commit: https://github.com/kubernetes-sigs/cluster-api/commit/4c5edd4a9298b2897173bfa1b3904b4cc11f051e
/kind bug
/priority critical-urgent
/help

We should also make sure that other fields marked optional have the omitempty tag properly set

/assign


Cherrypick #1072 release 1.0

Cherrypick #1072 release 1.0
Signed-off-by: Lantao Liu<EMAIL_ADDRESS>

/test pull-cri-containerd-build
/test pull-cri-containerd-node-e2e


Migrating from PyQt5 to PyQt6:

whippersnappy/config_app.py:

Changed imports from PyQt5 to PyQt6
Changed enums to PyQt6 syntax

whippersnappy/cli/whippersnap.py:

Changed imports from PyQt5 to PyQt6
Changed enums to PyQt6 syntax

pyproject.toml:

changed dependencies from PyQt5==5.15.6 to PyQt6

Note: libxcb-cursor needs to be installed using apt in order for PyQt6 to work

Thanks. A few Todos:

[ ] rebase this on the current main with the mac runner fix #34
[ ] fix formatting errors (e.g. black) https://github.com/Deep-MI/WhipperSnapPy/actions/runs/9099665527/job/25024360909
[ ] still we need to figure out what is wrong with sphinx https://github.com/Deep-MI/WhipperSnapPy/actions/runs/9099665526/job/25024360892
[ ] check if we can also bump pyOpenGL to latests which was pinned together with pyQT5 version in #22
[ ] update and test docker
[ ] update readme with required system dependencies
[ ] test in the context of fastsurfer's evaluation pipeline where this is used


The date and time of the file is missing

Copyed file No time information

Thanks for reporting

https://ibb.co/ekNL8U
https://ibb.co/i4wDTU
Its a big misstake why the function say its 1 Jan 1970...

I will more debuggin for this Problem...

i think a lib or what ever is missing... when i get the timestamp in c with the stat function then i get the right times... on the switch 1970... i seach now on libs...

test-timestamp is the test branch


Publish finder for programmes

This PR follows the same flow as https://github.com/alphagov/policy-publisher/pull/11 for publishing a Programme to the PublishingAPI and entails:

refactoring the PublishingAPI interactions (along with the validations and callbacks required) to a concern and using that in the PolicyArea
rename the PolicyAreaPresenter to ContentItemPresenter and change the reference to policy_area to object
add the content_id to Programme
change PublishingAPI test helpers to be more generic
add the Publishable concern to Programme along with updating the test

Ticket.

:+1: top stuff


Secondary routes not getting mapped

Hi,
I have noticed that if you have multiple routes mapped to your app that only the primary route gets re-mapped. This could lead to downtime for anyone accessing the app on any routes other than the primary route. This is a particular issue if you have a secondary route to your app mapped as "www".
There is also an orphaned route left after running cf zero-downtime-push.
Regards,
S

Is it possible to put multiple routes in the manifest?

This should be possible with this: https://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html#routes
Please re-open if this is not the case.


Allow changing automountServiceAccountToken in PodSpec via values.yaml

What does this PR do?
This PR adds serviceAccount.automountServiceAccountToken to values.yaml and thus allows changing automountServiceAccountToken in the PodSpec, which is true by default. This PR does not change the default behavior.
Motivation
automountServiceAccountToken is set to false in the actual service account definition, but in environments that have policies that require automountServiceAccountToken to be false in the actual Podspec this isn't good enough. Ideally the same value would change automountServiceAccountToken in both the service account definition and in the podspec, but since they are respectively true and false by default this would effectively change the default behaviour if both were set by this one value so I opted to only have this value control the attribute in the podspec.
This is the issue described in https://github.com/traefik/traefik-helm-chart/issues/1254
More

[X ] Yes, I updated the tests accordingly
[X] Yes, I updated the schema accordingly
[X] Yes, I ran make test and all the tests passed

The need comes from environments that don't allow automounting the serviceaccount due to policies (OPA, Kyverno or similar).
The solution in such an environment is to disable automounting of the serviceaccount and instead use service account token projection, like described here - https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#launch-a-pod-using-service-account-token-projection
This helm chart already has support for volumes and volumemounts, so this should be a good alternative to automounting the serviceaccount for those who are unable to do so.

Thanks @vidarno for the detailed explanation.
Then, could you just add a test and I'll be happy to review and merge it ?


[2.0.2-wip] footerbar & topbar's inner container width issue.

As I'm mentioned here https://github.com/twitter/bootstrap/commit/f3b6cf1d6d65ccc640152aa4edb88cbea05a8b45
scroll down to my comments. After adding: https://github.com/twitter/bootstrap/commit/f3b6cf1d6d65ccc640152aa4edb88cbea05a8b45#L1R2560
I was wrong this issue still here. To look at this issue just use latest demo from 2.0.2-wip branch.
To solve this I'm just removed ".navbar .container { width: auto; }"

What's the issue?

Just downloaded latest 2.0.2-wip again and opened index.html in gedit, removed responsive.css and opened index.html in browser and everythin fine but width of containers inside navbars become 100% of window width.

+1.  Without responsive.css, it causes the top fixed bar to 100% . With responsive.css included, the "width:auto;" is overriden with correct width except ie7/8. It causes inconsistent behavior.

Resolved in 2.0.2-wip now. Thanks!


Add Helm overrides for env vars, volumes and volume mounts

Issue #, if available: https://github.com/aws-controllers-k8s/community/issues/919
Description of changes:
Adds additional Helm chart value overrides for deployment environment variables, volumes and volume mounts.
When deploying the s3-controller with the following values.yaml overrides:
deployment:
  extraVolumes:
    - name: test-volume
      secret:
        secretName: test-secret
  extraVolumeMounts:
    - name: test-volume-mount
      mountPath: /root/
  extraEnvVars:
    - name: SOMEVAR
      value: somevalue
    - name: PASSWORD
      valueFrom:
        secretKeyRef:
          name: mysecret
          key: password
          optional: false

helm template produces the following output:
# Source: s3-chart/templates/deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: release-name-s3-chart
  namespace: default
  labels:
    app.kubernetes.io/name: s3-chart
    app.kubernetes.io/instance: release-name
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/version: "1.0.4"
    k8s-app: s3-chart
    helm.sh/chart: s3-chart-1.0.4
spec:
  replicas: 1
  selector:
    matchLabels:
      app.kubernetes.io/name: s3-chart
      app.kubernetes.io/instance: release-name
  template:
    metadata:
      labels:
        app.kubernetes.io/name: s3-chart
        app.kubernetes.io/instance: release-name
        app.kubernetes.io/managed-by: Helm
        k8s-app: s3-chart
    spec:
      serviceAccountName: ack-s3-controller
      containers:
      - command:
        - ./bin/controller
        args:
        - --aws-region
        - "$(AWS_REGION)"
        - --aws-endpoint-url
        - "$(AWS_ENDPOINT_URL)"
        - --enable-development-logging
        - "$(ACK_ENABLE_DEVELOPMENT_LOGGING)"
        - --log-level
        - "$(ACK_LOG_LEVEL)"
        - --resource-tags
        - "$(ACK_RESOURCE_TAGS)"
        - --watch-namespace
        - "$(ACK_WATCH_NAMESPACE)"
        - --deletion-policy
        - "$(DELETION_POLICY)"
        image: public.ecr.aws/aws-controllers-k8s/s3-controller:1.0.4
        imagePullPolicy: IfNotPresent
        name: controller
        ports:
          - name: http
            containerPort: 8080
        resources:
          limits:
            cpu: 100m
            memory: 128Mi
          requests:
            cpu: 50m
            memory: 64Mi
        env:
        - name: ACK_SYSTEM_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
        - name: AWS_REGION
          value:
        - name: AWS_ENDPOINT_URL
          value: ""
        - name: ACK_WATCH_NAMESPACE
          value:
        - name: DELETION_POLICY
          value: delete
        - name: ACK_ENABLE_DEVELOPMENT_LOGGING
          value: "false"
        - name: ACK_LOG_LEVEL
          value: "info"
        - name: ACK_RESOURCE_TAGS
          value: "services.k8s.aws/controller-version=%CONTROLLER_SERVICE%-%CONTROLLER_VERSION%,services.k8s.aws/namespace=%K8S_NAMESPACE%"
        - name: SOMEVAR
          value: somevalue
        - name: PASSWORD
          valueFrom:
            secretKeyRef:
              key: password
              name: mysecret
              optional: false
        volumeMounts:
            - mountPath: /root/
              name: test-volume-mount
        securityContext:
          allowPrivilegeEscalation: false
          privileged: false
          runAsNonRoot: true
          capabilities:
            drop:
              - ALL
      securityContext:
        seccompProfile:
          type: RuntimeDefault
      terminationGracePeriodSeconds: 10
      nodeSelector:
        kubernetes.io/os: linux
      hostIPC: false
      hostNetwork: false
      hostPID: false
      volumes:
        - name: test-volume
          secret:
            secretName: test-secret

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

instead of extraXXX can we call these variables additionalXXX?

Modeled these from the prometheus operators Helm chart, which is one of the most extensive charts I've seen before. https://github.com/prometheus-community/helm-charts/tree/main/charts/prometheus


Initial support for the discussions endpoint

References #1109
I don't want to do more than this as there is also a V4 API, but I'd need some help on how they work 😇

What's the end goal for this? How are we gonna add discussion support?

I guess there's no endgoal yet, I just wanted to chip away at some of the work that'd be required to add support for this, and make the GitHubAPI a bit more complete.

I need to read up on how to even use discussions, never have.
Sent with GitHawk

OK so organizations can have teams (GitHawkApp has 0 atm) and teams can have discussions. It's just a place for a team within an organization to have a forum-like thread to discuss stuff.

Closing as its stale


Skin 10 (A skin that doesn't exist and is unused)

So somebody just said there is a unused skin that makes you invisible. That skin doesn't exist. Can you please fix that or make another skin that takes that slot?

I think that was a hack.  I will work on measures to prevent this


[Bug?] Searching searches for files outside of folder

Yo.
I've always noticed a weird bug with ARCExplorer with its search function.

(Image is from 1.4.1, but it's the same in 1.4.2)
I search for mario in the fighter_voice folder, but it pulls up everything with that name outside of the folder.

This is intentional. The search functionality searches the entire ARC rather than the current folder. I think the confusion is that the search bar is on the same line as the current folder path. I'll look into reworking the layout in the future.


fixing build error

I had made a small error while resolving conflicts in the Github UI. After pulling master, it wouldn't build due to a non-implemented interface member. The project should build and run smoothly now. Also renamed carControllerTest.cs to CarControllerTest.cs

That's interesting. Is it because you didn't wait for the CI to finish or did the CI not cover it?

That's interesting. Is it because you didn't wait for the CI to finish or did the CI not cover it?

That's interesting. Is it because you didn't wait for the CI to finish or did the CI not cover it?

I'm not sure how much time the CI should usually take, but I did resolve the conflicts a little before the PR's became approved and merged (all happened within 20 min)

@pietersap What PR was this?


ask a question about the 'net.mat'

Dear researcher, I am sorry to disturb you, when debugging your code, there is a missing'net.mat', I don't know, what is the role of this net? Where can I get the file? Hope to get your reply!

Hi,
You should download the trained model from here to use the testing code:
https://drive.google.com/open?id=0B6CktEG1p54WVVpyMlhOMjBjZk0

I have the same problem about missing "net.mat".
In addition, I have no access to the address, "https://drive.google.com/open?id=0B6CktEG1p54WVVpyMlhOMjBjZk0" that you mentioned in your reply.
how can I have the trained model 'net.mat'?
I hope to hear from you soon
thank you fro your attention in advance

Please try this link:
https://drive.google.com/file/d/0B6CktEG1p54WVVpyMlhOMjBjZk0/view?usp=sharing&resourcekey=0-F3-dFS8yWTq8G0chYu2Lvg

Please try this link: https://drive.google.com/file/d/0B6CktEG1p54WVVpyMlhOMjBjZk0/view?usp=sharing&resourcekey=0-F3-dFS8yWTq8G0chYu2Lvg

Thank you


Configure to run scripts with Xcode 5.0 tools

Thanks for sorting this out - I haven't been working on any ios development for the last year, so haven't upgraded my tools.

My pleasure. I think you can close #18 now.


[VL] fix bug of string buffer size calculation in shuffle

Flatten buffer doesn't update vector, so we can't use the vector to calculate the string buffer size. Instead to get the strlength from stringview and nullbit.

It's a full stringview scan for each binary column. But it's sequential access. Need to check the penalty in future.


os.getConfig does not produce a valid configuration

Expected Behavior
The configuration produced should contain the nested
"deviceApiKeys" = {
  "api.balena-cloud.com":
}

as without this some bootstrapping fails.
Actual Behavior
This is not included.
Steps to Reproduce the Problem

Generate a config
Check for the lack of deviceApiKey field

References

[camerondiver] This issue has attached support thread https://jel.ly.fish/#/support-thread~2732807a-5f30-474a-b8e5-09d3615fb561

@camerondiver This doesn't look like an SDK issue, since the SDK just gets the result from the API's /download-config endpoint
See: https://github.com/balena-io/balena-sdk/blob/master/lib/models/os.coffee#L453-L457
Specifically this endpoint is implemented in the open-balena-api.
See: https://github.com/balena-io/open-balena-api/blob/8639082f9d93c35040112489d8c565c192bff372/src/routes/index.ts#L96
Is this field new?

The deviceApiKeys object is only used internally by os-config. What has happened on the attached support issue is that probably deviceApiKey was missing from the configuration, and when deviceApiKeys was added it was a hackish workaround to extract a deviceApiKey from it. Closing this as invalid.

@majorz FYI, I'm the one who had the original support ticket and deviceApiKey was always present in the singular form. The reason I reported this in the first place was because it seemed very strange that the device was bricked without the plural form in addition to the singular form.

Hi @mhodgson,
Can you provide some extra information about you ended up bricking the device and what you were trying to achieve?
The SDK currently reaches to the API to retrieve a device configuration that's appropriate for that specific API instance, so the API only populates the singular deviceApiKey property.
On the other hand the plural deviceApiKeys as you saw is a dictionary that names the appropriate api keys for all different API instances/domains that the device might be roaming (joining & leaving).

the device was bricked without the plural form in addition to the singular form

When you did run the device w/o the plural form, did it have any issues communicating with the API instance that generated the configuration?
Can you also clarify the OS version that you were using as well as the open balena vesrions (if applicable)?

@thgreasi sure! I'm doing something fairly simple (I think). I have a provisioning script that places a config.json file and a splash image into the default balena img downloaded from the UI. I need to have my devices registered with both Balena and AWS, so I create the device using the Balena API and put the uui, device ID, and API key into the config. For the rest of the config, I rely on the config generated by the API. In the initial versions of the script, I only put the API key in the top level deviceApiKey field. When doing this, the device would boot, and show up on the dashboard, but never get past the "Initializing Supervisor" message. I was not able to find any logs or error messages. Simply adding the plural 'deviceApiKeys' field made everything work as expected. I discovered the difference by downloading a stock image from the dashboard and pulling out the config.json. Sure enough (at least for the TX2) it has the plural and singular versions.

BalenaOS version was v2.38.3+rev3 for the TX2.

So, just to clarify some bits,
This happens for the Nvidia Jetson TX2 v2.38.3+rev3 prod.
You are not using the balena-cli in your provisioning process but instead your code uses the balena-sdk directly to fetch the configuration?
Can you clarify how & in which path of the image you inject the downloaded config.json?

Balena and AWS

This was a bit unclear. Can you clarify whether the device only runs against  balenaCloud?
Can you provide a sample if how the problematic & the fixed config.json looks like (but make sure to not include the actual api key strings in there).

Re: AWS/Balena:
My point is just that I need to set the device name/info at provisioning time, instead of just letting Balena Cloud make one up and provision when the device connects. This is so I can provision a one-to-one mapping of balena devices to AWS things, create and AWS certificate for the device, and attach it as a device env variable in Balena Cloud. This way when the device first boots, it already has a working connection to AWS and no additional configuration is needed.
Re: Balena SDK
Yes, I use the balena-sdk. Here is basically what I am doing:
const balena = require("balena-sdk")();

const appName = "My-Balena-App";
const deviceName = "My-Balena-Device";
const imageVersion = "v2.38.3+rev3";

const uuid = balena.models.device.generateUniqueKey();
device = await balena.models.device.register(appName, uuid);
await balena.models.device.rename(device.uuid, deviceName);

const config = await balena.models.os.getConfig(appName, {
    version: imageVersion
});
config.deviceId = device.id;
config.uuid = device.uuid;
config.deviceApiKey = device.api_key;
// DOESN'T WORK WITHOUT THIS:
config.deviceApiKeys = {
  "api.balena-cloud.com": device.api_key
};

// write config json to img, flash, etc.

I don't have examples handy for you unfortunately. It takes some time to go through all the steps necessary and I'm not in front of a device at the moment.

@mhodgson we are still investigating this internally and will get back to you.
In the mean time it would be very helpful if you could answer the following:

Is this happening only on specific device types (eg does it also happen on RPis)?
Have you tried using the balena-cli to inject the config to your image and does it work when the deviceApiKeys is added manually? It would be very concerning if this didn't work, since this at the moment the way that we support for pre-provisioning devices.

@thgreasi I only have TX2 dev board to test, so I can't test on other devices.
Can you give me an example of how to use the CLI to create a device in balena and then get the config for it? I have not been able to locate a suitable function in the CLI. Also, I prefer the SDK since it is much easier to integrate into our provisioning script (in javascript/node).

Hi again @mhodgson ,
Here is the suggested workflow for pre-provisioning a device using the balena-cli:
$ balena device register MyApp --uuid 16851436b13a4023b39c88dffc79db7d
$ balena device rename 16851436b13a4023b39c88dffc79db7d MyPi
$ balena config generate --device 16851436b13a4023b39c88dffc79db7d --version 2.46.1 --output MyConfig.json
$ balena os configure ../path/to/os.img --device 16851436b13a4023b39c88dffc79db7d --config MyConfig.json

If you also face issues with the above steps, that that would certainly mean that there is something wrong on our side. I think that trying this would be a faster approach to investigate this issue, than passing code back and forth.

Let me also point you to our balena-cli masterclass on preregistering and preloading devices:
https://github.com/balena-io/balena-cli-advanced-masterclass#5-preloading-and-preregistering

And let me also point you on the balena-cli code for the os configure action:
https://github.com/balena-io/balena-cli/blob/0bc1e7057fd307b6a19dfe33b7281b85799c0689/lib/actions-oclif/os/configure.ts#L159-L223


environment

Hello,
I was following the example here: https://github.com/enisimsar/latentswap3d#example-for-mvcgan and  wondering how to run editing under eg3d's setting. I was trying to run the code python predict.py hparams.batch_size=50 load_path=$OUTPUT_PATH generator=eg3d generator.class_name=ffhq but the classifier requires tensorflow back to 1.xxx versions whereas in env.yml the tensorflow is 2.xxx version?
error msg:
  File "/xxx/latentswap3d/src/classifiers/stylegan2/dnnlib/tflib/tfutil.py", line 16, in <module>
    import tensorflow.contrib   # requires TensorFlow 1.x!
ModuleNotFoundError: No module named 'tensorflow.contrib'

Hello,
Thank you for your interest in our work.
To run the StyleGAN2 classifiers, you need to install version 1.15.4-gpu
https://github.com/enisimsar/latentswap3d/blob/0bd30cde15d36fe7381cb65adc448729859cc2b4/env.yml#L274
Please let me know if you have any questions.