Source Detail: we should stop preserving linebreaks in Description field

with #1087, we made a change in the Source Detail template to preserve line breaks in the description field, as well as several other fields.
Some source descriptions include formatting via HTML tags, so this was causing more spacing than necessary. We asked Debra, and she said we should go with styling via HTML tags and not via line breaks.
When a fix for this issue goes to production, we need to let Debra know, so someone can go through and make sure all necessary
s and
s are included in source descriptions.

Summarizing discussion from this morning's meeting:
It would be good to figure out why the line breaks are not always retained; possibly this has something to do with copy-pasting from Word (or other word processor hijinks.)
Having a solution where html tags have to be put into all entries in the future, and retroactively into a bunch of existing ones, is workable, but not ideal.

I haven't been able to figure out how to download Word, but I just tried a couple of experiments in Google Docs and Apple Pages to test whether pasting into textareas introduces html tags:
In both OldCantus and New, copying and pasting from these applications does not lead to the introduction of html tags. Where bullet points exist in the copied text, they are converted into single lines without bullet points.
Unless Word behaves differently than Google Docs and Apple Pages, or unless different operating systems or browsers handle pasting differently, it seems likely that indexers have manually added these html tags to the descriptions of certain sources over the years.
(for what it's worth, I've used a bunch of different browsers and different operating systems over the years, and I've never seen html tags added when I pasted into a text field. I highly doubt this could account for the html tags we're observing in source descriptions)

I don't think the html tags get added with the paste, but something is a little weird about copy pasting. e.g. these two look fairly similar in the editor:

but the one copied from Word has a second line break in it (after "the project") when rendered:

actually, rephrase: I see some related problems about getting html tags inserted when pasting from Word or Outlook from some time back (around 2011). So maybe some sources got tags inserted (automatically) at the last big Cantus update, and since then it's been tag-less?

I don't think it's very likely that somebody writing out their own html would have decided to use a special font for just a few random characters in this description https://cantus.uwaterloo.ca/source/123648, whereas it seems all sorts of likely that they are the result of some sort of weird word-to-html conversion.

Indeed, this does not seem to be the work of some musicologist. Maybe this occurred when some data was automatically added to OldCantus (not exactly sure what "the last big Cantus update" means, but since the copyright dates at the bottom of the pages on OldCantus start with 2012, this could align with your "around 2011").
So, what do we want to do going forward? We already have a WYSIWYG editor set up for articles that we could potentially put onto Source pages, so that musicologists can use bullet points without having to fiddle with HTML tags. Though this doesn't actually solve the problem of someone needing to go through and manually check the formatting of all the source descriptions.

Some source descriptions on OldCantus include tables
https://cantus.uwaterloo.ca/source/123610
I've also seen block quotes and maybe a few other interesting formatting cases.
Some places on OldCantus (e.g. the home page) have an "Enable rich text" option. It doesn't seem to be present for source descriptions, but maybe it was at one time?

Some summary of the discussion @annamorphism and I just had:

We can't just turn off the rendering of html tags, since there currently exist tables, bulleted lists, perhaps block quotes, etc. We don't want these to turn into thickets of <s and >s.
As mentioned above, some parts of OldCantus have the option to switch between wysiwyg, rich-text and plain-text modes. Currently, this is not an option on Source Edit pages, but perhaps this was the case at one point.
It might be that some source descriptions were composed in plain-text mode, others in rich-text, and others in wysiwyg, and that Drupal keeps track of which mode was being used. This could explain why OldCantus was able to neatly display a wide range of types of formatting - it was using multiple different ways of rendering, while we're trying to use just one.

One possible solution to this situation is to add a wysiwyg editor (like we currently use on Article pages) to Source pages. We need to ask Debra about this, though - this feature may initially have been present but was later removed.

another thing I discovered while poking around just now: clicking on "More information about text formats" on the OldCantus edit-the-mainpage editor brings you to https://cantus.uwaterloo.ca/filter/tips. It shows me different information depending on whether or not I'm logged in.

another thing I discovered while poking around just now: clicking on "More information about text formats" on the OldCantus edit-the-mainpage editor brings you to https://cantus.uwaterloo.ca/filter/tips. It shows me different information depending on whether or not I'm logged in.

Interesting, because non-logged in users shouldn't be composing anything anyway!
The "not logged in" information is just the plain-text paragraph of the logged-in information, so presumably it changed to only recommend plain text at some point and not bother informing people about wysiwg.

noting that this issue is similar to #1219, and that we can apply a similar approach (checking for html tags before applying the linebreaks decorator) here as we do there.

After further discussion, we will do what the title of this issue says, and just not preserve linebreaks when the Description is displayed. We will move towards all Source Description formatting being with html tags.

Also, moving this to High Priority so that then Debra, et al can begin harmonizing the actual content of the Description field with this standard approach.

Can I make a potentially left-field suggestion?
I find it frustrating with Django apps when I just want to write some prose with no special formatting, and the $%@# text input fields then mush all my text together when it gets saved.
On the other hand, I also know it creates problems when some descriptions allow line breaks, and this gets mixed up with HTML formatting.
On DIAMM, we use Markdown for fields where we might want to use formatting, but we might also just want to write a plain paragraph or two. The advantage is that this gets converted to HTML when being displayed, including the line breaks, so it's a bit of the best of both worlds.
A bonus is that there is a minimal text editor that comes along with it. See the screenshot.

If this sounds interesting, I can supply more details.

I would love it soooo much if we used markdown. Please, detail away!!!!

I too am intrigued by this suggestion!

@ahankinson Curious about what you use for this? The django-markdown extension (https://github.com/klen/django_markdown)?

@annamorphism
I've put together a little widget that allows for editing larger text fields with markdown a la github. Screenshots with a few features...
A look at the source edit page for Gottschalk:

You can see that rather than having html in those two fields, there is markdown (lists in the bibliography begin with asterisk, italics are made with underscores, tables are made with pipes, etc.). Compare, for example, to what's in those fields on production CantusDB:

Similar to this editor, there's a little tab at the top of this field that goes to "Preview" and displays a preview of the field:

We don't have any of the various text editor features that you have here on GitHub, although we could add a selection if we wanted to.
We can also style this however we want for the actual display, although the downside/upside of markdown is that this would no longer be something that the editor could add through html. For example, I've added some indentation and table styling in the actual display:

What do you think of this?  The downside is that any descriptions where we currently have html we would need to convert to markdown, I think. Although we could probably intially do something where we test whether there are html tags and only attempt markdown conversion if no tags exist...a stopgap while we edit the actual text fields.
As you're thinking, this is also relevant to #1219 and #1221.

Hmmm! Certainly seems like it would be worth playing with and seeing how we feel about it. I don't currently have a sense of how big a task the html-to-markdown conversion would be, but it might well be worth the end result.


[SMALLFIX] Make read buffer size in cp configurable.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/1924/
Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/1929/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/1941/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/1943/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/1946/
Test PASSed.


#571: Add support for Redis TYPE command

Feature Added : #571 Add support for Redis TYPE command
Description
This PR include the addition of new TYPE command.
Implementation for TYPE command. (internal/eval/eval.go) (internal/eval/commands.go)
Added unit tests (internal/eval/eval_test.go)
Added Integration tests (integration_tests/commands/type_test.go)
Added Benchmark (internal/eval/eval_test.go)
Testing
Unit tests

Integration tests

Benchmark

Feel free to suggest any changes @rishirishhh
Please review the PR and let me know any changes. @JyotinderSingh 😇
Thank you
Meet Ghodasara

Excited to contribute to Dice DB!
Thanks a lot for your review and suggestions. 😇
@apoorvyadav1111 @lucifercr07


Update grid_layout.py

Added the ability to change the divider line color

@GingerIndustries thanks for adding this functionality. This is currently failing pylint due to too-many-instance-attributes. apparently we were previous right at the limit, and adding the new one pushed it over.
Some of the attributes could be collapsed into a dictionary or other object that can hold multiple things. But it seems to me that this would make the code more complex for the purpose of pleasing pylint.
Personally I think it would be okay to disable the too-many-instance-attributes check for this class. But I'm open to input from others. If that does turn out to be the route we want to go with, do you know how to do that @GingerIndustries?

It probably doesn't matter, as this will be compiled to an .mpy regardless. I could make the changes, but that is ultimately up to you.

@GingerIndustries we will have to getting passing the CI checks one way or another before it can be merged. Even though the resulting library will get compiled to mpy we still run pylint and a few other checks on the .py version of the code using github actions.
Go ahead and add the pylint disable comment for that specific check. Let me know if you have any trouble, or need help with that.

Okay, it's done.

Nice! Thanks,


How to remove a volume on a node in Eru

Background
Sometimes, we added wrong volume to a node. But we only can change the capacity or resource declaration using eru-cli node set but cannot remove it completely. So things could become:
  init_volume:
    /data:<PHONE_NUMBER>44
    /data1:<PHONE_NUMBER>44
    /data2:<PHONE_NUMBER>44
    /data3:<PHONE_NUMBER>44
    /data4:<PHONE_NUMBER>44
    /data5:<PHONE_NUMBER>44
    /data6:<PHONE_NUMBER>44
    /data7:<PHONE_NUMBER>44
    /data8: 0
  memory:<PHONE_NUMBER>80
  memory_used:<PHONE_NUMBER>96
  name: -------
  podname: --------
  storage:<PHONE_NUMBER>456
  storage_used:<PHONE_NUMBER>096
  volume:
    /data:<PHONE_NUMBER>44
    /data1:<PHONE_NUMBER>16
    /data2:<PHONE_NUMBER>16
    /data3:<PHONE_NUMBER>16
    /data4:<PHONE_NUMBER>16
    /data5:<PHONE_NUMBER>16
    /data6:<PHONE_NUMBER>16
    /data7:<PHONE_NUMBER>16
    /data8: 0
  volume_used:<PHONE_NUMBER>096

Expectation
Able to remove it completely. So is there a way to do so?

The short answer is: set it again, for your case, eru-cli node set --volume /data8:0 $nodename

Due to current implementation, to discard an unused volume, you must follow these steps:

make sure no container is using this volume
set the available bytes of the volume to zero: cli node set --volume /vol:0 will do
delete the volume from meta, using the exactly same command as above: cli node set --volume /vol:0

The short answer is: set it again, for your case, eru-cli node set --volume /data8:0 $nodename
Due to current implementation, to discard an unused volume, you must follow these steps:

make sure no container is using this volume
set the available bytes of the volume to zero: cli node set --volume /vol:0 will do
delete the volume from meta, using the exactly same command as above: cli node set --volume /vol:0

Yeah I have tried both set to zero nor set it using negative size to zero by delta. But the result didn't change.
So you mean I should execute the set to zero twice and it will work as what I expect?


How to use realsense 435i on DOPE (about ros2 topic node)

On the quickrun page, I was able to run ros2 bag but don't know how to replace it with realsense 435i.
isaac_ros_dope lauch code:
ros2 launch isaac_ros_dope isaac_ros_dope_tensor_rt.launch.py model_file_path:=/tmp/models/redbull_60.onnx engine_file_path:=/tmp/models/redbull_60.plan
realsense lauch code:
ros2 run realsense2_camera realsense2_camera_node
realsense topic:

/color/camera_info
/color/image_raw

rosbag info:

Files:             dope_rosbag_0.db3
Bag size:          6.0 MiB
Storage id:        sqlite3
Duration:          0.5s
Start:             Oct 10 2023 03:46:35.884<PHONE_NUMBER>.884)
End:               Oct 10 2023 03:46:35.889<PHONE_NUMBER>.889)
Messages:          2
Topic information: Topic: /camera_info | Type: sensor_msgs/msg/CameraInfo | Count: 1 | Serialization Format: cdr
Topic: /image | Type: sensor_msgs/msg/Image | Count: 1 | Serialization Format: cdr

rqt grapth of rosbag and image resize node

Still confuse why subscribe of image resize subscribers dose not change,
I did replace "image" with  "/color/image_raw" then colcon build --merge-install but not thing has change.
Please tell me if I miss some step.
resize_node.cpp
using nvidia::gxf::optimizer::GraphIOGroupSupportedDataTypesInfoList;

constexpr char INPUT_CAM_COMPONENT_KEY[] = "input_compositor/cam_info_in";
constexpr char INPUT_DEFAULT_CAM_INFO_FORMAT[] = "nitros_camera_info";
constexpr char INPUT_CAM_TOPIC_NAME[] = "/color/camera_info";
// constexpr char INPUT_CAM_TOPIC_NAME[] = "camera_info";

constexpr char INPUT_COMPONENT_KEY[] = "input_compositor/image_in";
constexpr char INPUT_DEFAULT_TENSOR_FORMAT[] = "nitros_image_bgr8";
constexpr char INPUT_TOPIC_NAME[] = "/color/image_raw";
// constexpr char INPUT_TOPIC_NAME[] = "image";

Terminal
admin@anpc:/workspaces/isaac_ros-dev$ ros2 node info /image_resize
/image_resize
  Subscribers:
    /camera_info: sensor_msgs/msg/CameraInfo
    /camera_info/nitros: negotiated_interfaces/msg/NegotiatedTopicsInfo
    /image: sensor_msgs/msg/Image
    /image/nitros: negotiated_interfaces/msg/NegotiatedTopicsInfo
    /parameter_events: rcl_interfaces/msg/ParameterEvent
  Publishers:
    /parameter_events: rcl_interfaces/msg/ParameterEvent
    /resize/camera_info: sensor_msgs/msg/CameraInfo
    /resize/camera_info/nitros: negotiated_interfaces/msg/NegotiatedTopicsInfo
    /resize/image: sensor_msgs/msg/Image
    /resize/image/nitros: negotiated_interfaces/msg/NegotiatedTopicsInfo
    /resize/image/nitros/nitros_image_rgb8: sensor_msgs/msg/Image
    /rosout: rcl_interfaces/msg/Log
  Service Servers:
    /image_resize/describe_parameters: rcl_interfaces/srv/DescribeParameters
    /image_resize/get_parameter_types: rcl_interfaces/srv/GetParameterTypes
    /image_resize/get_parameters: rcl_interfaces/srv/GetParameters
    /image_resize/list_parameters: rcl_interfaces/srv/ListParameters
    /image_resize/set_parameters: rcl_interfaces/srv/SetParameters
    /image_resize/set_parameters_atomically: rcl_interfaces/srv/SetParametersAtomically
  Service Clients:

  Action Servers:

  Action Clients:


ocamlPackages.qcheck: 0.18 → 0.19.1

Description of changes
Fixes & improvements: https://github.com/c-cube/qcheck/blob/v0.19.1/CHANGELOG.md#0191
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 181837 run on aarch64-darwin 1

1 package marked as broken and skipped:

liquidsoap

11 packages failed to build:

haxe (haxe_4_2)
haxePackages.format
haxePackages.heaps
haxePackages.hlopenal
haxePackages.hlsdl
hxcpp (haxePackages.hxcpp)
haxePackages.hxcs
haxePackages.hxjava
haxePackages.hxnodejs_4
haxe_4_0
haxe_4_1

10 packages built:

beluga
comby
flow
fstar
jackline
libbap
python310Packages.bap
python39Packages.bap
soupault
stog

@GrahamcOfBorg build beluga comby dune-release easycrypt flow fstar jackline jasmin-compiler ligo liquidsoap satysfi soupault stog


Meta data inheritance in nested folders - Mixup metadata types

Description
I created a folder and attach a meta data label with type "date". Next I created an additional folder inside the first folder, it inherits the meta data label, but the type is reset to "Freedom text" and can't be changed.
For files inside the first folder the meta data type is correctly inherited.
For files inside the second folder the bug consists and the type can't be changed.
Expected
The subordinate folders and files inherit the meta data field types correctly.
Actual
Folder 1 is created and a meta data field of type "date" is created.

The meta data type attached to files inside this first folder are correctly set. (Btw: here you see a variation of  #223 on folders, I created "Folder 1.1" and "Folder 1.2", it's not a typo, will try to reproduce it.)

The one (or more) step inside folder 1.1 is created and inherits the meta data field, but the type is mixed up. And can't be changed.

Files inside this 1.1 folder are also with the wrong meta data field.

Info:

OS: [e.g. Linux Debian 10, docker-compose]
Browser [Firefox 78.10.0]
Database [PostgreSQL 12.3, docker-compose]
Papermerge Version [2.0.1, docker-compose]

PS: outstanding project! I appreciate your work!
I found this project after weeks of searching for a substitution of so called "open-source" ECM programms (who are actually attached to a company and in CE there is literally no functionality.)

Indeed, both folders Folder 1.1 and Folder 1.2 should have had inherited metadata of type "date" with format "dd.mm.yy" as specified by parent folder.
@cnbhl, thanks for opening this issue with detailed description!


ARROW-13187: [Python] Avoid creating reference cycle when reading CSV file

Some Python versions have a bug where signal.getsignal creates a reference cycle holding execution frames alive (https://bugs.python.org/issue42248).
This would cause excessive lifetimes of the PyArrow table returned by read_csv.

cc @westonpace


New statusPage pull request

Rebased, changed onhover to onclick

This isn't quite right :). It looks like you created a PR backwards (to merge master into your branch).
Also, I suggest having a single commit with the html, css, json, and readme in a new directory, gem5art/status_page/.
To get around the rebase woes, you can just checkout master, create a new branch (git checkout -b <new branch>) and then copy the four files into that new branch. It may help to just clone a fresh copy of gem5art.

Closing this PR since it is no longer needed.


Fix mistral abandoned tasks

I have the context from Slack, but in the future please try to add some description, context and background so other people without the context about the change also know what is going on :)

LGTM, good catch :+1:

:+1:


Asynchronous plug-in steps and workflows

We discovered recently that asynchronous plug-in steps and workflows are not runnning anymore when bypass custom plugins is enabled for requests. We did test it back and forth and could verify this behavior consistently.

Learn Build status updates of commit fe99fb8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

powerapps-docs/developer/data-platform/bypass-custom-business-logic.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@n0rthface
Thanks for the feedback.
The documentation describes the correct behavior of this parameter. I am aware that there is a bug that causes what you see.
I recommend that you contact technical support to report that this is impacting you.


Error "insertRule` accepts only strings" when using with styled-components

What is the current behavior?

Get with-styled-components example (https://github.com/zeit/next.js/tree/canary/examples/with-styled-components)
Add

)

Error appears:

StyleSheet: `insertRule` accepts only strings.

When i remove the  "styled-components" plugin from .babelrc, everything works fine.

What is the expected behavior?
Styled-jsx tags should work with styled-components + babel-plugin-styled-components in stack.
Environment (include versions)

OS: OSX 10.13.4
Browser: Chrome 70.0.3538.102
styled-jsx (version): 3.1.0

Did this work in previous versions?
IIRC this was working in my older project with Next.js 6.1.1.

Not sure if the problem is with styled-jsx, babel-plugin-styled-components or where, but installing babel-plugin-styled-components version 1.8.0 seems to fix this problem. 1.9.0 doesn't work or the current 1.9.2.

I've been trying to figure this out for 3 days now. If you remove the jsx tag from your

I'm having the same issu as the @jdolinski1
In desperation I have tried the following (with next.js 7.0.2):

<EMAIL_ADDRESS>+<EMAIL_ADDRESS><EMAIL_ADDRESS>+<EMAIL_ADDRESS><EMAIL_ADDRESS>+<EMAIL_ADDRESS><EMAIL_ADDRESS>+<EMAIL_ADDRESS><EMAIL_ADDRESS>+<EMAIL_ADDRESS>
if i remove babel-plugin-styled-components from my babelrc, the error goes away. Same thing if i replace 'style jsx' with 'style' as @tomanagle suggested, but not sure how that affect the rest of my code. Is jsx not needed?

@jsve Are you sure the versions were correctly installed and no caches or something was left behind? I ask because I had this problem, but when I installed<EMAIL_ADDRESS>it disappeared, I had<EMAIL_ADDRESS>and the currently latest nextjs, 7.2 or is it 7.0.2.
I’m not sure but I think removing the jsx attribute will stop the prefixing of classes so it becomes global instead of contained in the component.

pretty sure. tried again now and ran npm cache clean --force and then npm install but with same error message. Is there something other i can try?

That's related to changes introduced in https://github.com/styled-components/babel-plugin-styled-components/pull/172 to support this "new" css prop API: https://www.styled-components.com/docs/api#css-prop
What happens is that component generated from


Fully Implement All Tuplet Variations

The Tuplet implementation right now does not take into consideration all variations possible.
You can see all variations here: http://www2.siba.fi/muste1/index.php?id=100&la=en
You can learn more about the variation types here: https://en.wikipedia.org/wiki/Tuplet
What's missing:

the ability to have a tuple of more than 7
the ability to specifically set how many of the specified duration the tuplet will equal

#29, #30 is dependent on this being completed.

Seems like in order to be able to do everything, the initializer has to take in the following information:

What note duration you want to use for the tuplet
How many of that note in the tuplet
What note duration you want to use for the spacing the tuplet should fit into
How many of that note should the tuplet fit into

We basically need to replicate the information at this link: https://usermanuals.finalemusic.com/Finale2014Mac/Content/Finale/TPDLG.htm

@robtimp would love to get your input on this to see if I'm missing anything and what you think about naming.

Fixed by #33


Add ShuffleNet v2

Added 4 configurations: x0.5, x1, x1.5, x2
Added 2 pretrained models: x0.5, x1
Tested with Imagenet 1k.
Partially addresses: #645
TODO: re-upload the models from my branch, and update the URLs

Codecov Report

Merging #849 into master will increase coverage by 0.9%.
The diff coverage is 82.65%.

@@           Coverage Diff            @@
##           master    #849     +/-   ##
========================================
+ Coverage      54%   54.9%   +0.9%
========================================
  Files          36      37      +1
  Lines        3346    3444     +98
  Branches      549     559     +10
========================================
+ Hits         1807    1891     +84
- Misses       1406    1418     +12
- Partials      133     135      +2

Impacted Files
Coverage Δ

torchvision/models/__init__.py
100% <100%> (ø)
:arrow_up:

torchvision/models/shufflenetv2.py
82.47% <82.47%> (ø)

torchvision/transforms/transforms.py
83.37% <0%> (+0.68%)
:arrow_up:

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 8759f30...de95f2b. Read the comment docs.

I didn't train the pretrained models. The weights were published here: https://github.com/ericsun99/Shufflenet-v2-Pytorch

@fmassa is there any other change request, or can we go on to merge this addition?


add dns  lookup

Please answer these questions before submitting your issue.

Why do you submit this issue?
[ ] Question or discussion
In some cases,BACKEND_SERVICE is config as dns:port;
some dns production is not support Load balancing,for example core dns in cncf.

so i want to add a dns lookup to support the case

Just confirm, you want to do DNS lookup manually by codes, then select the backend from candidates?

yes，maybe can support more ways，for example

dns
Kubernetes service
Maybe kubernetes service load balancer mode is a better way,but the way depends on cloud (aws,Ali),it would be not work in a privite kubernetes cluster
So.i want to add the feature, like kubernetes dubbo
1.Use kubernetes service self support
1.if have time,also supports dns nslookup

Do you have more material about DNS level load balancer can't work automatically? From your asking, it seems, we need codes to do a DNS lookup to get the candidate list. Am I right?

If you want to add new dependency on the agent core, that wouldn't be recommended, especially for this case. The way would be adding a plugin for feature extension. If there is no extension point currently, we could create one.
Anymore, I need more details about what you are trying to do. Because I don't know what dubbo-k8s did, actually, that is not have to be our reference. Agent is very different from a dev framework.

yes，i should change a new title
build the connection between  agent client and oap server with service discover
for example :
Kubernetes
dns
etcd
zk
.....
create a new extension point like oap

OK, that will not be an easy job. NOTICE, receiver role OAP role is never registered through the coordinator, but your service discovery is for looking up receiver role nodes.

And service discovery of OAP node is not recommended in many companies, because the OAP nodes are deployed in the system/operation platform zone, rather than the business zone. Service discovery wouldn't work in this case.

OK，thx

i found the purpose of boot service  int erface for single purpose.
if we want to support  the  polymorphism in service discovery.
2 ways:

modify the boot service to support polymorphism
add a new interface.

Do you have any Suggestions


Make cool dashboard

This is mainly an issue for coaches, as they can't see newly joined users.

remove it completely & when a new user joins show a notification icon on the settings link in the navbar


Spanish translation.

issue #8

This is fantastic. Thanks @manuelitox, for improving the Google Translate versions as well. :smile:


TypeError: Cannot read property 'readdir' of undefined when running test:integration

When I cloned this project and ran npm run test:integration after running npm install, I got the following error:
$ npm run test:integration

><EMAIL_ADDRESS>test:integration /home/wenhao/openzeppelin-test-environment
> node scripts/run-integration-test.js

(node:97482) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'readdir' of undefined
    at run (/home/wenhao/openzeppelin-test-environment/scripts/run-integration-test.js:24:22)
    at Object.<anonymous> (/home/wenhao/openzeppelin-test-environment/scripts/run-integration-test.js:19:3)
    at Module._compile (module.js:652:30)
    at Object.Module._extensions..js (module.js:663:10)
    at Module.load (module.js:565:32)
    at tryModuleLoad (module.js:505:12)
    at Function.Module._load (module.js:497:3)
    at Function.Module.runMain (module.js:693:10)
    at startup (bootstrap_node.js:188:16)
    at bootstrap_node.js:609:3
(node:97482) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:97482) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Seems it is having trouble executing the following command and could not find that directory:
tests = await fs.readdir('test-integration');

However this directory is exactly inside the path where I executed the npm run test:integration command. Am I missing some kind of configuration here?
BTW the npm run test:unit command can be executed normally and gives the correct result.

I believe this error was due to using an old version of Node. At least Node.js 10 is required.


NodeJs Version

What version of nodejs should i use? i used 10 and it didnt work

I used the latest version, 14 and it ran smoothly in agar.io


RC2 - @addTagHelper error

There is an assembly containing an ViewComponent, and it's Razor files (embedded as resources)
I load the assembly from disk:
var assy = Assembly.Load(somePath);

I register it with MVC using ApplicationParts

 var mvcBuilder = services.AddMvc();
 mvcBuilder.AddApplicationPart(assy);

Then I configure Razor, with an EmbeddedFileProvider so it can discover the Razor view, and it's CompilationContext so that it compile the Razor view with a reference added for the assembly itself (as that where it's model is):
            mvcBuilder = mvcBuilder.AddRazorOptions((options) =>
            {

                var previous = options.CompilationCallback;
                options.CompilationCallback = (compilationContext) =>
                {
                    if (previous != null)
                    {
                        previous(compilationContext);
                    }

                  compilationContext.Compilation.AddReferences(
                        MetadataReference.CreateFromFile(assy.Location));
                };

                var  fileProvider = new EmbeddedFileProvider(assy, "Gluon.Module.ThemeSwitcher"));
                options.FileProviders.Add(fileProvider);
            });

In my application, I search for, and invoke the ViewComponent dynamically - as the application doesn't have a dependency on it:

 public class ViewComponentHelper : IExtendedViewComponentHelper
    {
        private readonly IViewComponentDescriptorCollectionProvider _descriptorProvider;
        private readonly IViewComponentSelector _selector;

        public ViewComponentHelper(
          IViewComponentDescriptorCollectionProvider descriptorProvider,
          IViewComponentSelector selector)
        {
            _descriptorProvider = descriptorProvider;
            _selector = selector;
        }

        public Task<IHtmlContent> InvokeIfExistsAsync(IViewComponentHelper componentHelper, string name, object arguments = null)
        {
            if (!Exists(name))
            {
                return Task.FromResult<IHtmlContent>(new HtmlString(string.Empty));
            }

            if (arguments == null)
            {
                return componentHelper.InvokeAsync(name, null);
            }

            return componentHelper.InvokeAsync(name, arguments);

        }

        private bool Exists(string name)
        {
            var comp = _selector.SelectComponent(name);
            bool exists = comp != null;
            return exists;
        }
    }

The ViewComponent get's invoked, but there is this error during Razor compilation:

Any ideas what the problem might be?
Here is the contents of the Razor file:
@addTagHelper "*, Microsoft.AspNetCore.Mvc.TagHelpers"
@model Gluon.Module.ThemeSwitcher.ViewModels.ThemeSwitcherViewModel

@{
    ViewData["Title"] = "Gluon";
}

<li class="dropdown themeswitcher" data-bind="visible: $root.visible">

</li>

If I remove that addTagHelper line in the razor file, it then complains about it again in _Layout.cshtml

If I remove it from there too, it seems to work. Can you not have duplicate addTagHelper calls or something in the View heirarchy?

Looks like it's an issue with the quotes. Duplicate of https://github.com/aspnet/Razor/issues/744

@NTaylorMullen - Nice spot - yep this is indeed the issue. Was pulling my hair out.

If I remove the quotes I get this:

Ah sorry my bad! Wrong namespace that time haha


Integration Test - Release - 2019/05/20 21:08:27

Auto create for integration test. AnotherAuthorUpdatedArticleFlow

@PRMergerTest2 : Thanks for your contribution! The author(s) have been notified to review your proposed change.


About the .core and .ops

Hello！
In the new version of mmdetection, function packages such as .core .ops have been removed, and this object detection code contains many operations that call the above function packages. I would appreciate if you could tell me how to fix the above problem!

Code for the object detection task using stable diffusion

@hsouri

The issue has been resolved, thanks for your outstanding work!

How did you resolve this?

@mingyueqingfeng2022 @hsouri
I encountered the same issue but haven't been able to resolve it. Could you please share how you managed to fix it?

Choose the new version of mmdet (the tool versions in my environment package are mmcv 2.1.0, mmdet 3.3.0, mmengine 0.10.3)

Use the new version of mm related packages to replace the old version packages (for example:
from mmdet.models.builder import BACKBONES as det_BACKBONES
from mmdet.utils import get_root_logger
from mmcv.runner import _load_checkpoint
Change to:
from mmengine.model import BaseModule
from mmdet.registry import MODELS

from mmdet.utils import get_root_logger
from mmengine.runner.checkpoint import _load_checkpoint
) @DogukanBG  @dibyaghosh

Choose the new version of mmdet (the tool versions in my environment package are mmcv 2.1.0, mmdet 3.3.0, mmengine 0.10.3)

Use the new version of mm related packages to replace the old version packages (for example:
from mmdet.models.builder import BACKBONES as det_BACKBONES
from mmdet.utils import get_root_logger
from mmcv.runner import _load_checkpoint
Change to:
from mmengine.model import BaseModule
from mmdet.registry import MODELS
(comment, because there is no get_root_logger in the new version of mmdet.utils) from mmdet.utils import get_root_logger
from mmengine.runner.checkpoint import _load_checkpoint
) @dibyaghosh @DogukanBG

Choose the new version of mmdet (the tool versions in my environment package are mmcv 2.1.0, mmdet 3.3.0, mmengine 0.10.3)

Use the new version of mm related packages to replace the old version packages (for example:
from mmdet.models.builder import BACKBONES as det_BACKBONES
from mmdet.utils import get_root_logger
from mmcv.runner import _load_checkpoint
Change to:
from mmdet.registry import MODELS
(comment, because there is no get_root_logger in the new version of mmdet.utils) from mmdet.utils import get_root_logger
from mmengine.runner.checkpoint import _load_checkpoint
) @dibyaghosh @DogukanBG


 Bikeshed allows (and in fact prefers) the <pre> tags to be on their own line, with the content between them, and will correct the markup for you to make HTML happy.  It will also anti-correct the markup if you're catering to HTML. ^_^
Closing because I'm not that interested in fixing this bug; adjust the markup to make Bikeshed happy also makes it more readable.


Update xarray and mache to conda env dependencies

Closes #583

Hi @chengzhuzhang, I added xarray and mache to the related conda envs.
These dependencies will be added later to the conda-forge feedstock recipe when we start doing the release candidates. Xylar has a process for handling this, where he checks this repo's conda-env/ci.yml and updates the conda-forge feedstock recipe accordingly.


[For Reference] Example of adding a new API and Controller

Description

This is an example PR to show rougly the changes necessary to add the skeleton for a new API and Controller.
NOTE

This example adds a namespaced resource. If you want to use a global resource (like most of our operator APIs), specify --namespaced=false on step 1.

The commits are broken down and show precisely which commands were run.
Specifically:

Generate the new Resource and controller skeleton
operator-sdk create api --group=operator.tigera.io --version=v1 --kind=DemoResource --resource --controller

Generate manifests
make manifests

Add a new Reconciler to pkg/controller, and point the internal/controller implementation at it.

The next steps here would be to fill out the Add and Reconcile functions in pkg/controller/demoresource/demoresource_controller.go with the specific logic of the new feature.
For PR author

[ ] Tests for change.
[ ] If changing pkg/apis/, run make gen-files
[ ] If changing versions, run make gen-versions

For PR reviewers
A note for code reviewers - all pull requests must have the following:

[ ] Milestone set according to targeted release.
[ ] Appropriate labels:

kind/bug if this is a bugfix.
kind/enhancement if this is a a new feature.
enterprise if this PR applies to Calico Enterprise only.

Love it.. what version of operator-sdk should I use for this? If we have a specific version that works with our PROJECT file maybe we could consider a dockerized version as a makefile target perhaps?


TypeError when training with Train_NER_German.py

In BilSTM.py after nnInput sent into the train_on_batch function, it caused TypeError :
unsupported operand type(s) for *: 'IndexedSlices' and 'int'
in line 107
when calling self.model.train_on_batch()
with the dataset GermEval, our Env :
Keras==1.2.2
nltk==3.2.2
numpy=1.14.1
scipy=1.0.0
theano==0.9.0
h5py==2.6.0
tensorflow==0.12.1
In Epho 1 it shows that :
--------- Epoch 1 -----------

Layer (type)                     Output Shape          Param #     Connected to
token_emd (Embedding)            (None, None,<PHONE_NUMBER>0

casing_emd (Embedding)           (None, None, 8)       64

char_emd (TimeDistributed)       (None, None, 51, 30)  2850

char_cnn (TimeDistributed)       (None, None, 51, 30)  2730

char_pooling (TimeDistributed)   (None, None, 30)      0

varLSTM_1 (Bidirectional)        (None, None, 200)     191200      merge_1[0][0]

varLSTM_2 (Bidirectional)        (None, None, 150)     165600      varLSTM_1[0][0]

hidden_layer (TimeDistributed)   (None, None, 26)      3926        varLSTM_2[0][0]

chaincrf_1 (ChainCRF)            (None, None, 26)      728         hidden_layer[0][0]
Total params: 65,221,598
Trainable params: 367,034
Non-trainable params: 64,854,564
Could you please tell me how to correct it and how this error occured ?

Hi @3chrisprosise
See the readme.md:
Note: The CNN for character based representations doesn't work with Tensorflow. You will get the error message:
TypeError: unsupported operand type(s) for *: 'IndexedSlices' and 'int'

Solution: Use Theano as backend or don't use character based representations using CNN (parameter: charEmbeddings).
It would be highly appreciated if someone could port the code (the CRF-layer) to Keras 2.x and Tensorflow 1.x.

Sadly character based embeddings does not work with Tensorflow 0.12.x for whatever reason. So I recommend to use Theano as Backend when using this code.

This issue is solved in the latest version (2.1.5), which runs with Keras 2.1.5 and Tensorflow 1.7.0


EnForce Storage Location

Hi, is there a way to enforce the location to store the database?.
Assuming I have a 1TB external micro sd card in the Android Device and I want the database and tables to be in  the 1TB external sd card, how do I enforce this?
Thanks alot.

You can do something like this:
https://medium.com/@mostasim/read-external-database-with-sqliteopenhelper-on-android-e87d66891f4e
You need to provide a context wrapper.
Then when initializing DBFlow, the specific database config should be specified:
FlowManager.init(appContext) {
  database<AppDatabase> (openHelperCreator =  AndroidSQLiteOpenHelper.createHelperCreator(wrappedContext))
}

(using 5.0.0-alpha2 syntax). For old syntax its just specifying a different Context for the AndroidSQLiteOpenHelper classs.


Auto detect

use pbn.autoConvert() to automatically the file type based on the stream data

Coverage increased (+0.1%) to 99.06% when pulling e0ef137c22c21a0a5fa98fee59849d155a11aa70 on auto-detect into 398941374ce9e288532fa26d3f5b46718b5d401b on master.


Fixing the protractor typescript error for e2e tests.

Coverage remained the same at 100.0% when pulling ef4a96b09e0faba04eed3ccb55749690aea57992 on danyhoron:master into b17874ce3be91bda552f9d429e3813d3e4ecd2b8 on antonybudianto:master.

@danyhoron , Thanks for your contribution! :+1:

Thank you for a great starter project.


Basic relationship support - Take 2

Reopen #25

This PR has been superseded by further work (yet to be submitted)


Heroku aws support

Add aws build pack to heroku servers
ACs:

We can make our S3 storage private.
Engineer needs to enter AWS username and password from Heroku shell when retrieving the data*.json file from S3 as part of server deployment to Heroku.

From Rasmus:

rasmus [1:16 PM]
Regarding #689: I can make you an AWS login. Our current process: On my local machine: Build DB image. Upload DB image to S3. On Heroku, download DB image from S3, load it into the DB. Hmmmm, I just realized that we may be able to upload the DB image directly from local machine to heroku by setting the DB URL .... in which case we don't need S3 at all...

The problem we're looking to solve here is the way we use S3 without authentication. Either figure out a way to not use S3 at all, or find a way to lock down S3. The former would involve passing the Heroku DB URL to ./manage.py when running on our local machine. The latter would involve installing the necessary software on Heroku to allow it to access an authenticated S3 endpoint, I believe that would be a Heroku AWS buildback.

Updated release process document with suggestion for how this can be fixed, leaving the issue open until the fix has been verified.

So in other words, what changes do we need to make to a "local" environment for this to work from our own machines:
./manage.py loaddata ../data-2019-07-18.json --database postgres://...ec2-107-21-126-193.compute-1.amazonaws.com:...

The proposed solution worked as intended for Server release: 1.3.8


Rename library to golly

go-commons is a very boring name. Let's Rename the library to golly .
Its an acronym that loosely means Go Open Source Library

Update the project name
Update Go Mod  name
Update Main Documentation Read Me

use golly.nandlabs.io

Given other dependants of this library, we have decided not to rename and merge this with https://github.com/nandlabs/golly


Demo/notebook for common use case

Hello @nicole1q ,  I have a small molecule with known structure that unfortunately was not tested in the original LINCS1000 dataset.  I want to predict the expression profile of this small molecule in the same cell lines used in LINCS1000.  Can you possibly create a demo in the README or an attached notebook highlighting how one would do this with your program.  Many thanks in advance!

To prepare your dataset for a new small molecule, please refer to the instructions in custom_data_preprocessing.ipynb. Once your dataset is ready, you can predict the perturbed expression profile by running test_demo.py, adjusting the split_key argument as needed for your analysis.
If you’re interested in other applications or discussing potential collaborations, please feel free to reach out at<EMAIL_ADDRESS>

Ok, i will take a look at the notebook.  Do you have any documentation for the arguments to your programs?  In particular "split_key"?  What are the values it can take and what do they mean?

Same question~


Update placeholder text

Part of https://github.com/mapzen/documentation/issues/310
Also a few writing style changes for capitalization and abbreviations. I removed the links to example search queries because they require API keys and didn't seem to add much.

This is ready for review and merge now. Testing looks OK for this section.
If you want to preview, you can go to https://dev.mapzen.com/documentation/mapzen-js/api-reference/
When signed in, the placeholder text swaps to the first of your API keys. If you are not signed in or have no API keys, you still see your-mapzen-api-key.


Updating the Pico_and_LED library

Pico_and_LED

Enhancement: adding class-constructor
Enhancement: adding function to check the LED status (on/off)
Improvement:  GPIO_Pin parameter only have to be included at the class constructer.

Features and a example have been added. "Feature/#6" #7 has been merged.
The Pico_and_LED library is now finished


nvidia-texture-tools: 2.1.0 -> unstable-2019-10-27

Motivation for this change
Updating to latest unstable that fixes build on darwin, but sadly is still failing on aarch64. Reported to upsteam as noted in the previous pull request.
Closes #41109.
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

@GrahamcOfBorg build 0ad


Release Checklist for V1.1.1 patch release

[x] Close or defer all tickets in the epics (scope closure)
[x]  Create release candidate branch (branching, tagging)
[x]  Identify destination & distribution targets (communications, announcements)
[x]  Ensure SRE pipelines are in place, including testing (testing evidence)
[x]  Create readme in git repo (scope closure)
[x] ensure changelog has been created
[x]  Documentation updates are in place (docs team)

Release can be closed @RitaMAllenCA

@cspramit
Closed final issue for SDK v1.1.0
Karan created release branch from dev
Karan created version bump (v1.1.1 for code; v1.1.0 for package) PR and included changelog and merged on new RC branch
Communicate to Bandy new release is out once posted as well as IPwe (let Mo know)


shift github repo from "master" branch to "main" branch as the default branch

As @bcpswope pointed out, there is an ongoing effort of moving away from the word master and adapting the branch main.
All new GitHub repos are default to using main but some of our older repos are still using master.
This is an issue to keep track of that work.

Another related request from @berenss
"Would like to see allowlist rather than whitelist. I know Observability is guilty"

all the repos on https://github.com/open-cluster-management-io does not contain master branch as the default branch. They are all using main


When i run the "Copilot auth" commend and choose Copilot setting and throw this error

When i run the "Copilot auth" commend and choose Copilot setting and throw this error,is it a bug or something wrong in my configuration? I have no idea.

Did you find the solution?


xkb-switch-i3: init at 1.8.1

Motivation for this change
Adding xkb-switch with i3 support
Things done

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

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

Result of nixpkgs-review pr 107579 run on x86_64-linux 1

1 package built:

xkb-switch-i3

Result of nixpkgs-review pr 107579 run on x86_64-linux 1

1 package built:

xkb-switch-i3


missing license

@peterkhayes The repo is missing License and as a result not able to use rolling-rate-limiter at work. Can I go ahead and create a pull request to add MIT license ?

Sure!


Cannot change tcp liveness probes with pod overrides

Affected version
0.0.0-dev
Current and expected behavior

When using an integer as as port property:

....
      automatic-log-config:
        podOverrides:
          spec:
            containers:
              - name: airflow
                livenessProbe:
                  tcpSocket:
                    port: 8080
                  initialDelaySeconds: 30
                  periodSeconds: 5
                  failureThreshold: 6

An error is raised complaining that the property must be a string:
    case.go:366: AirflowCluster.airflow.stackable.tech "airflow" is invalid: [spec.webservers.roleGroups.automatic-log-config.podOverrides.spec.containers[0].livenessProbe.tcpSocket.port: Invalid value: "integer": spec.webservers.roleGroups.automatic-log-config.podOverrides.spec.containers[0].livenessProbe.tcpSocket.port in body must be of type string: "integer", spec.webservers.roleGroups.custom-log-config.podOverrides.spec.containers[0].livenessProbe.tcpSocket.port: Invalid value: "integer": spec.webservers.roleGroups.custom-log-config.podOverrides.spec.containers[0].livenessProbe.tcpSocket.port in body must be of type string: "integer"]

When using a string as the tcpSocket.port property, the value must contain the name of the port and not the port number. So "http" and not "8080"

Possible solution
Maybe use  k8s-openapi 0.21.1 to pull in https://github.com/Arnavion/k8s-openapi/pull/153
Additional context
It is apparently a known bug: https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#intorstring
Environment
No response
Would you like to work on fixing this bug?
maybe

Now works like a charm (tested using 0.0.0-dev) and
kind: HbaseCluster
spec:
  restServers:
    roleGroups:
      default:
        replicas: 1
        podOverrides:
          spec:
            containers:
              - name: hbase
                livenessProbe:
                  tcpSocket:
                    port: 1234
                  initialDelaySeconds: 5
                  periodSeconds: 10
                  failureThreshold: 5


[Enhancement] jdbc connector support adb

What I'm doing:
Fix NPE exception caused by null PARTITION_EXPRESSION field of information_schema.partitions when using jdbc connector to connect adb.
What type of PR is this:

[x] Enhancement

Does this PR entail a change in behavior?

[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[x] Parameter changes: default values, similar parameters but with different default values

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.2

@banmoy Hello, I wanted to inform you that we've resolved a Null Pointer Exception (NPE) that occurred when reading ADB data via the JDBC connector. The issue was due to NULL value in the PARTITION_EXPRESSION field of the information_schema.partitions. The fix has been implemented. Please take a look at your earliest convenience.


Cannot change project icon on expo.dev

Build/Submit details page URL
https://expo.dev/accounts/oliver.larcher/projects
Summary
I cannot find any option for changing the icon for a particular project on expo.dev. In the project settings menu, there is an option to change the display name under "Project display info", but not the icon. It appears that the icon is initially set when uploading a build with icon for the first time, but it is not updated then the app icon changes.
Managed or bare?
Managed
Environment
  expo-env-info 1.0.5 environment info:
    System:
      OS: macOS 14.1.1
      Shell: 5.9 - /bin/zsh
    Binaries:
      Node: 20.9.0 - /opt/homebrew/bin/node
      Yarn: 1.22.19 - /opt/homebrew/bin/yarn
      npm: 10.2.3 - /opt/homebrew/bin/npm
    SDKs:
      iOS SDK:
        Platforms: DriverKit 23.0, iOS 17.0, macOS 14.0, tvOS 17.0, watchOS 10.0
    IDEs:
      Android Studio: 2022.2 AI-222.4459.24.2221.9862592
      Xcode: 15.0.1/15A507 - /usr/bin/xcodebuild
    npmPackages:
      expo: ^49.0.0 => 49.0.6
      react: 18.2.0 => 18.2.0
      react-dom: 18.2.0 => 18.2.0
      react-native: 0.72.3 => 0.72.3
      react-native-web: ~0.19.6 => 0.19.7
    npmGlobalPackages:
      eas-cli: 5.9.1
    Expo Workflow: managed

✔ Check Expo config for common issues
✔ Check package.json for common issues
✔ Check dependencies for packages that should not be installed directly
✔ Check for common project setup issues
✔ Check npm/ yarn versions
✔ Check Expo config (app.json/ app.config.js) schema
✔ Check for legacy global CLI installed locally
✔ Check that native modules do not use incompatible support packages
✔ Check that native modules use compatible support package versions for installed Expo SDK
✖ Check that packages match versions required by installed Expo SDK

Detailed check results:

Some dependencies are incompatible with the installed expo version:
<EMAIL_ADDRESS>- expected version: ~2.4.12
<EMAIL_ADDRESS>- expected version: ~0.18.17
<EMAIL_ADDRESS>- expected version: 0.72.6
Your project may not work correctly until you install the correct versions of the packages.
Fix with: npx expo install --fix
Found outdated dependencies

Error output
No response
Reproducible demo or steps to reproduce from a blank project
Go to https://expo.dev/accounts/<ACCOUNT>/projects and try to change a project's icon.

Any chance you figured this out? It's been driving me nuts for some time.

No, unfortunately. I'm starting to wonder if changing the icon used to be an option that was later removed, as the icons I still see in my project list are the ones for projects I created over two years ago. It seems new projects don't get the app logo defined at first build time by default anymore.

+1 I can't find anywhere how to change the actual project icon on expo.dev. The actual app's icon is fine, but I just want to change the project icon on expo.dev and I can't find out how?

+1

+1

The same with me

+1

+1

Nothing yet?

+1

+1

@olarcher, you marked this as needs review last November. Based on the history here, this is a real problem with expo.dev that needs to be resolved, not just reviewed. It's very frustrating to see outdated and missing icons in the management UI despite multiple builds/deploys with updated app icons, and yet have no way to resolve it.

Hi,
Thanks for highlighting this issue. We are aware that we are missing this capacity on our website, we are thinking of adding it in the future, but we currently don't have the engineering capacity to do that. Generally, we understand that it might be problematic and want to solve it, but I can't promise any ETA at the moment.

Thanks for the update - just knowing that it's not in indefinite limbo is helpful!

Still relevant.

+1

+1
The icon for my App changed in stores. I would like to be able to change it in expo too.

Not stale, still awaiting fix
On Sat, 23 Nov 2024, 11:07 github-actions[bot], @.***>
wrote:

This issue is stale because it has been open for 30 days with no activity.
If there is no activity in the next 7 days, the issue will be closed.
—
Reply to this email directly, view it on GitHub
https://github.com/expo/eas-cli/issues/2135#issuecomment-2495123824, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIQI2GY6FU6MYNJ7IFJHP32B7BKHAVCNFSM6AAAAAA734PR5CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJVGEZDGOBSGQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Any news about this?

Just adding one more voice to the problem. We've been updating our projects and 2 out of 3 projects have new app icons that have nothing to do with actual.


Clearing queue sometimes scrobbles when it should not.

OS:
Gentoo (Linux 4.12.5-gentoo #1 SMP Tue Aug 15 20:38:48 CDT 2017)
Windows 10
GPMDP 4.4.0
Issue Description:
Clearing the queue scrobbles the currently "playing" (but paused and <50% played) song. Happens often enough to be easily noticed but not every time the queue is cleared. May be related to  #1614.
Steps to Reproduce:

Connect to Last.fm.
Start playing an album with two or more tracks.
Just after the first song ends/second song starts, pause the player.
Clear the queue from the queue interface in the bottom right.
The second song has been scrobbled despite only playing for a few seconds at most. If not, repeat the process until the issue is duplicated.

Awesome, thanks much!

Fixed in #2614


[BUG] Katana README Documentation link is broken

Describe the bug
In crates/katana/README.md, Documentation is broken.  Return 404: NOT_FOUND
Expected behavior
Link to the correct file.

Good catch, closed by #1523.


Version management, maybe JSON-for-VHDL and/or pyVersioning

While reviewing the latest changes, I found that the version is manually bumped in several places.
On the one hand, there is project JSON-for-VHDL, which allows writing (meta)data in a JSON file and then accessing it from VHDL. In fact, the JSON content can be passed as an string top-level generic, or as a file. It is synthesisable, so it can be used for setting parameters/generics in the design. However, it does not take any area. That is, it is not a JSON core. It's a library that is executed at compilation/synthesis time.
On the other hand, @Paebbels has pyVersioning for handling version management across multiple languages (VHDL, C, Python...). It is meant, precisely, for bumping the version in the HDL source, the C drivers, the docs, etc. all consistently.
In the mid term, it might be interesting to consider these or other similar alternatives.

I found that the version is manually bumped in several places.

Right. I know it is bad practice.
This whole "versioning concept" emerged in a very early stage of the project. Basically, it is just a counter that is incrementing with each new modification...

On the one hand, there is project JSON-for-VHDL, which allows writing (meta)data in a JSON file and then accessing it from VHDL. In fact, the JSON content can be passed as an string top-level generic, or as a file. It is synthesisable, so it can be used for setting parameters/generics in the design. However, it does not take any area. That is, it is not a JSON core. It's a library that is executed at compilation/synthesis time.
...

Look interesting - especially the JSON-for-VHDL concept.
But I am not quite sure there. I have experimented with a simple bash script that extracts the version number from the VHDL package file and inserts it into the documentation. A very hacky and unpretty workaround - indeed. We should discuss this in #37 as the project lacks a real concept of straight versioning (shame on me!)... 😉

Honestly, I don't think there is any direct solution. Even in the Python ecosystem, multiple different approaches are used. Hence, I'm good with any solution you pick. I believe the important issue is having the version defined in a single place, and/or generating it consistenly. #41 is an small step towards that. I agree that we should discuss #37 before implementing a solution across the repo.

VHDL-2019 gives a mechanism to put a date code that you can use as a revision indication.    Long term - and perhaps longer for synthesis tools - the language will have a solution.

While reviewing the latest changes, I found that the version is manually bumped in several places.

SemVer seems to be the way to go! -> #37

On the one hand, there is project JSON-for-VHDL, which allows writing (meta)data in a JSON file and then accessing it from VHDL. In fact, the JSON content can be passed as an string top-level generic, or as a file. It is synthesisable, so it can be used for setting parameters/generics in the design. However, it does not take any area. That is, it is not a JSON core. It's a library that is executed at compilation/synthesis time.

I have some issues with including files from the RTL files.... (related to #35 )
Let's say the version is defined in some global text (or whatever) file. This could be read using plain textio. But the problem here is the configuration of the path where to find the file. A global/static path is not flexible at all. Specifying no path leaves the default path to the mercy of the simulator or synthesis tool...
I don't know if this is primitive workaround or a good platform-independent solution, but how about using an additional VHDL package that contains the version? 🤔 This package file could be created by some simple script, but of course this is not really dynamic... 🤔 🤔

The language (VHDL) provides features for solving those problems (both initialising mems from files or defining a version in some file/package). The point is whether the tools you want to use do support those language features. Generics and/or generic packages can be used for passing the path. It's just an string. For instance, VUnit defines the top-level generic tb_path, which allows reading/writing files relative to the location of the testbench (see https://github.com/VUnit/vunit/blob/master/examples/vhdl/array_axis_vcs/src/test/tb_axis_loop.vhd#L53). So, passing the revnumber through CLI (as done with asciidoc) might work.

Sound reasonable. But I see the problem, that a path defined by a generic might be lost when someone creates a setup from scratch (adding all VHDL files by hand / not using a provided script for project setup).

Moreover, generating a VHDL package from another language/script, which contains the version as a constant, is an absolutely feasible solution. I'd say that's exactly what pyVersioning is about.

I think this is more "stable" solution. From my point of view, the question is not really how to generate this package, but when to generate it. It should be auto-generated by some kind of script that is triggered by an abstract action. But what kind of "action"?? And who triggers that? I'm a little bit lost there. :thinking: :wink:

Hi. I created pyVersioning to be called e.g. in Vivado (synthesis) and Vivado SDK as pre-build steps.
In Vivado (synthesis), it's called as a pre-tcl hook for the main synthesis step.
In Vivado SDK, it's called as a pre-build step, so SDK writes a rule into the auto generated makefiles.
I suspect Intel, Lattice, ... are also providing such hooks.
So on every build, a file is generated including Git Hash, Git date, Git Time, Branch/Tag, repository URL (to identify forks), build date, build time, tool version, compile options.
In case of Vivado synthesis, we generate a text file, that is read via VHDL file I/O to describe the initial content of an AXI4-Lite register. We could also generate a constant, but if a modified file is part of the list of source files, Vivado would invalidate all generated bitstreams after each run. (It will see a modified source and out-date all outputs :(.
While a AXI4-Lite register at address 0x8000_0000 is good for an SoC (e.g. Xilinx MPSoC) a processor might need special CPU capability / CPU info registers to expose these information.

The idea for pyVersioning is to have one information collector (Git, yaml file, CI service) to write any source file as needed. E.g. on a CI server, you don't have a branch name or tag name, because on CI, the repository is checked out via hash. But, CI services are offering these information via environment variables (name depends on the used service). Anyhow, it would be a bummer to implement the rules for each language and service from scratch to collect all information you want to embed into a version register/string.

Hi. I created pyVersioning to be called e.g. in Vivado (synthesis) and Vivado SDK as pre-build steps.

I will have a closer look.

In Vivado (synthesis), it's called as a pre-tcl hook for the main synthesis step.
In Vivado SDK, it's called as a pre-build step, so SDK writes a rule into the auto generated makefiles.

So it is based on tcl only (toolchain agnostic)?

In case of Vivado synthesis, we generate a text file, that is read via VHDL file I/O to describe the initial content of an AXI4-Lite register.

As far as I understand, you are proposing to generate something like a "memory initialization file" (i.e. not a HDL source file!) that keeps the version information, correct?
For the rtl part of the project, the actual version number (32-bit) seems to be sufficient - so an extra memory/hardware(!) module seems to be an overkill. However, it would be interesting to include the "full version" data into the software framework - somehow. 🤔

We could also generate a constant, but if a modified file is part of the list of source files, Vivado would invalidate all generated bitstreams after each run. (It will see a modified source and out-date all outputs :(.

I understand that this is not a good implementation practice, but to honest I would not mind. 😄
Furthermore, Vivado (and maybe other toolchains as well) provides incremental synthesis so only the parts that actually changed will get re-synthesized.

So it is based on tcl only (toolchain agnostic)?

The tool is written in Python an meant for any platform (not tested everywhere) and any language being called from any environment. As Vivado understands only TCL, we have a one-liner to call the Python script :).

As far as I understand, you are proposing to generate something like a "memory initialization file" (i.e. not a HDL source file!) that keeps the version information, correct?

In a first approach we generated the content of a VHDL constant in a package. Because the package is observed by Vivado for changes, Every build run, triggered the package generation and latest version information was integrated into the synthesis (e.g. build time). While Vivado used the latest content due to the pre-tcl hook, the GUI rechecked for modified files after finishing the implementation. Now it saw a modified file and it then invalidates the generated *.bit file. This is a tool bug of Vivado ...
Anyhow, it created an endless loop of builds and outdated output files.
By using a mem-init file, Vivado doesn't know it has changed, but the init-file is read on every build. So we tricked Vivado :).

For the rtl part of the project, the actual version number (32-bit) seems to be sufficient - so an extra memory/hardware(!) module seems to be an overkill.

Yes it might be enough to have a single register for a CPU.
But for an SoC I would encourage a complete register.

Furthermore, Vivado (and maybe other toolchains as well) provides incremental synthesis so only the parts that actually changed will get re-synthesized.

Incremental synthesis was and is a mess with Vivado...

I believe that the register space at address 0x8000_0000 that @Paebbels mentioned is exactly the same as the SYSINFO in NEORV32.

Hmmm, @stnolting, I'm not sure it is good to have issues automatically marked as stale/wontfix and then closed. There is no rush for having issues solved, nor a problem of high traffic which needs aggressive filtering. Moreover, since this is an open source project with no funded developers, it is understandable that some features get fixed quick and others take longer. Therefore, I would recommend to avoid enabling an stale bot yet. Issues can be ordered by latest update (https://github.com/stnolting/neorv32/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc) so it's easy to see whether some is "too old".

:smile: I completely forget that stale is watching this repository...

Hmmm, @stnolting, I'm not sure it is good to have issues automatically marked as stale/wontfix and then closed. There is no rush for having issues solved, nor a problem of high traffic which needs aggressive filtering. Moreover, since this is an open source project with no funded developers, it is understandable that some features get fixed quick and others take longer. Therefore, I would recommend to avoid enabling an stale bot yet. Issues can be ordered by latest update (https://github.com/stnolting/neorv32/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc) so it's easy to see whether some is "too old".

I totally agree :+1:


joined gene names, a possible pitfall to cause incorrect result?

Is chanjo aware of this problematic gene names, which may causes various problems for queries that base on gene names?
➤ gawk '{print $NF}' ccds.15.grch37p13.extended.bed|grep ','|head
NOX1,NOX1,NOX1
NOX1,NOX1,NOX1
NOX1,NOX1
NOX1,NOX1,NOX1
NOX1,NOX1,NOX1
NOX1,NOX1,NOX1
NOX1,NOX1,NOX1
NOX1,NOX1,NOX1
NOX1,NOX1,NOX1
NOX1,NOX1,NOX1
➤ gawk '{print $NF}' ccds.15.grch37p13.extended.bed|grep ','|wc -l
66188

➤ gawk '{print $NF}' ccds.15.grch37p13.extended.bed|grep ','|sort|uniq|wc -l
9290
➤ gawk '{print $NF}' ccds.15.grch37p13.extended.bed|grep ','|sort|uniq >problematic.gene.names.txt

An test query on NOX1 returned a result. So I guess chanjo does indeed take care of the problem. Could you @robinandeer explain how it does that?

I'm not quiet sure what you mean :/
The only problematic gene names I know on are the ones that exist on both the X and Y chromosomes and have to be given prefixes.
It looks like you are picking out exons that belong to multiple transcripts which all map to the same gene but the input looks correct :)
Remember that it's only in the loading step these colums matter - for annotations, only the chrom, start, end columns matter


Unpin antlr4 python runtime version and bump openpulse version.

Pinning antlr4 is causing some grief downstream packages, so we unpin the requirement.

We can unpin the patch version (so make it >4.9,<4.10), but unless we change the version of ANTLR we're actually building the files with, we can't fully unpin it. That said, I've written a little extension for the OQ3 implementation that you can port to here that lets us package multiple versions of the ANTLR files into one package, and choose at import time based on the version of the runtime we have available. I've been totally swamped on Qiskit lately, but I'll tidy it up and get it finished with its new CI today

. I've been totally swamped on Qiskit lately, but I'll tidy it up and get it finished with its new CI today

Perfect, thanks @jakelishman. I'll keep an eye out for an update.

Closing in favor of #8.


Cocoapods Update 4.0.0 to 3.8.2?

New Issue Checklist

[ ] I have read and understood the CONTRIBUTING guide
[ ] I have read the Documentation
[ ] I have searched for a similar issue in the project and found none

Issue Info

Info
Value

Platform Name
e.g. ios / tvos

Platform Version
e.g. 8.0

SDWebImage Version
e.g. 3.7.6

Integration Method
e.g. carthage / cocoapods / manually

Xcode Version
e.g. Xcode 7.3

Repro rate
e.g. all the time (100%) / sometimes x% / only once

Repro with our demo prj
e.g. does it happen with our demo project?

Demo project link
e.g. link to a demo project that highlights the issue

Issue Description and Steps
Please fill in the detailed description of the issue (full output of any stack trace, compiler error, ...) and the steps to reproduce the issue.

@iOSCountry  What is the question/issue here?

closing this. please reopen with more info


Create 0000-01-02-Daria-Timofeeva.md

This is the most frustrating tutorial I have ever experienced!

This tutorial could not have been more confusing.


ypeError: init() got an unexpected keyword argument 'use_ssl

I am run it with the following command:
elasticsearch_loader  --es-host http://localhost:9203 --http-auth elastic:changeme --index raw_bill --type incident csv input.csv

I got :
Traceback (most recent call last):
  File "/Users/redayxu/devCloud/bill/.env/bin/elasticsearch_loader", line 11, in <module>
    load_entry_point('elasticsearch-loader==0.6.0', 'console_scripts', 'elasticsearch_loader')()
  File "/Users/redayxu/devCloud/bill/.env/lib/python3.8/site-packages/click/core.py", line 764, in __call__
    return self.main(*args, **kwargs)
  File "/Users/redayxu/devCloud/bill/.env/lib/python3.8/site-packages/click/core.py", line 717, in main
    rv = self.invoke(ctx)
  File "/Users/redayxu/devCloud/bill/.env/lib/python3.8/site-packages/click/core.py", line 1134, in invoke
    Command.invoke(self, ctx)
  File "/Users/redayxu/devCloud/bill/.env/lib/python3.8/site-packages/click/core.py", line 956, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/Users/redayxu/devCloud/bill/.env/lib/python3.8/site-packages/click/core.py", line 555, in invoke
    return callback(*args, **kwargs)
  File "/Users/redayxu/devCloud/bill/.env/lib/python3.8/site-packages/click/decorators.py", line 17, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/Users/redayxu/devCloud/bill/.env/lib/python3.8/site-packages/elasticsearch_loader/__init__.py", line 95, in cli
    ctx.obj['es_conn'] = Elasticsearch(opts['es_host'], **es_opts)

I ran into this issue as well. A temporary workaround that worked for me was to use the Python 2 version of elasticsearch_loader

How does one use the "Python 2" version?

How does one use the "Python 2" version?

I encountered this issue too, but decided to go a different route, which works well for me.  Rather than loading files with this project, I have setup https://vector.dev/ to listen on a TCP socket, and write to Elasticsearch.  So basically loading to ES is cat file.ldjson | nc localhost 9000.
The vector config was roughly:
api.enabled = true

[sources.in]
type = "socket"
address = "<IP_ADDRESS>:9000"
max_length = 102_400
mode = "tcp"

[transforms.proc]
inputs = ["in"]
type = "remap"
source = '''
  structured = parse_json!(.message)
  . = merge!(., structured)
  del(.message)
'''

[sinks.elasticsearch]
inputs = [ "proc" ]
type = "elasticsearch"
auth.user = "admin"
auth.password = "password"
auth.strategy = "basic"
mode = "bulk"
endpoints = [
    "https://localhost:9200"
]
compression = "none"
tls.verify_certificate = false

How does one use the "Python 2" version?

python2 -m virtualenv p2env
source p2env/bin/activate
pip install elasticsearch_loader
elasticsearch_loader --es-host http://<IP_ADDRESS>:9200 --index mactimes csv /tmp/pas2.dd.mactimes.csv

I get the same issue. Does anyone understand why it is happening in the first place?

use_ssl is getting passed as an argument to the ElasticSearch class constructor here, but the constructor doesn't take use_ssl.

while installing it on python 2 facing below error
ERROR: Exception:
Traceback (most recent call last):
File "/p2env/lib/python2.7/site-packages/pip/_internal/cli/base_command.py", line 223, in _main
status = self.run(options, args)
File "/p2env/lib/python2.7/site-packages/pip/_internal/cli/req_command.py", line 180, in wrapper
return func(self, options, args)
File "/p2env/lib/python2.7/site-packages/pip/_internal/commands/install.py", line 321, in run
reqs, check_supported_wheels=not options.target_dir
File "/p2env/lib/python2.7/site-packages/pip/_internal/resolution/legacy/resolver.py", line 180, in resolve
discovered_reqs.extend(self._resolve_one(requirement_set, req))
File "/p2env/lib/python2.7/site-packages/pip/_internal/resolution/legacy/resolver.py", line 419, in _resolve_one
assert req_to_install.user_supplied
AssertionError

One workaround to get rid of this error is to remove 'use_ssl' from init.py file.
https://github.com/moshe/elasticsearch_loader/blob/master/elasticsearch_loader/__init__.py#L96


chore: minor release :rocket:

do we not want this? https://github.com/TrueLayer/retry-policies/pull/21/files

I did not release release-plz was already set up. Awesome. I'll edit that PR

Closing in favor of https://github.com/TrueLayer/retry-policies/pull/21


Plugin shows that files are uploaded even if they fail NetSuite validation

SuiteScript 2.0 files have some sort of validation performed on them by NetSuite when they are uploaded to the file cabinet.  If they fail this validation, NetSuite returns and error and prevents the upload.  NTFW will still display the "Files Uploaded" informational alert even if the uploaded file fails validation.
There are two scenarios in which I have seen this behavior;

Trying to upload a v2.0 script file over the top of a v1.0 script file results in "Failed to validate script file:  This file is used by a SuiteScript 1.0 script; you cannot change the API version of the file."
Trying to upload a v2.0 script file that doesn't have at least one correct entry point defined for the specified script type results in "SuiteScript 2.0 entry point scripts must implement one script type function".

I've attached the SOAP responses that provide examples of each.  Let me know if I can help in any way.
Entry Points.txt
Failed to validate script file.txt

Thanks for the info. I haven't really tested this much with any 2.0 stuff yet. I see in your examples that we do get an failure for isSuccess and a message with the details. I can add something like a red prompt that will say it failed to upload and popup a message with the details I believe. Is that something like you are expecting? I definitely do not check for isSuccess now which I should be doing.

That's exactly what I was thinking.  I'd certainly appreciate it!

I just pushed version 1.0.8 that should fix your issue. Thanks.

Just tested it with 1.0.8.  Works like a champ!
Thanks for such a quick turn-around...and thanks for putting together this plugin.  I use it all day every day.

Awesome!
No problem! I used it all day too. Thanks for the kind words.


[CSM-423] Component testing for middleware endpoints using Pure DB and Data.Acid.Memory.Pure.

This PR brings batch of refactorings:

Abstraction of MonadWallerWebMode instead using of concrete monad
Base logic of lib tests was moved to lib in module Test.Pos.* (now it also can be used in explorer).
Also part of Test.Util was moved to lib.
Implemented skeleton for wallet tests and test for newPayment and for importing of wallet-keys have been written.

@Martoon-00 @flyingleafe I've addressed all your changes, plz check


docs: Motivations behind this package and limitations

📚 Is your documentation request related to a problem?
I personally would like to know what are the motivations behind this package, and what are the known limitations or limitations you have been thinking about. It seems quite obvious to me that the goal behind nuxt with ionic allows cross platform development with one codebase and still get the advantages of nuxt. To my understanding, just like with next.js in react world, people are mainly using nuxt for the developer experience and SSR/SSG for SEO performance. Correct me if I'm wrong, but SSR shines for unpredictable data (e.g. user generated data) and SSG shines for stable data. One of my main concern is: do SSR and SSG work in this package? There is this package in next world, but they say SSR doesn't work out of the box.
Lastly, are there any other undocumented known limitations?
Knowing and documenting those two points could help other developers have a sense of a kind of roadmap and contribute more easily perhaps.
🔍 Where should you find it?
Seems like one of the first things to tell. It's always good to start with WHY (see Simon Sinek) in my opinion.
ℹ Additional context
No response

I have found this issue to be a limitation
https://github.com/danielroe/nuxt-ionic/issues/19

A big limitation!

The reason is pretty obvious in my view: providing a plug and play solution for deploying a nuxt project on mobile.
This, of course, could prove to be quite challenging considering the large set of features nuxt provides (e.g. does talking about SSR make any sense in this context?)

(e.g. does talking about SSR make any sense in this context?)

I created some example of what I think this module can do for us in terms of SSR with Nuxt and Ionic
https://github.com/saviorsoul/nuxt-ionic
I added one missing piece of nuxt router which was not included in this module:
nuxtApp.hooks.hookOnce('app:created', async () => {
    try {
      await router.replace({
        ...router.resolve(initialURL),
        name: void 0,
        force: true,
      })
    } catch (error2) {
      callWithNuxt(nuxtApp, showError, [error2])
    }
  })

the result is that now app is trying to generate HTML from components but without ionic web-components context, so it basically creates a DOM structure which contains all needed data but is always rendered without possibility to hydrate. Adding ionic web-components context on client-side hydration always changes the DOM structure. So for now my understanding is like this:

it's hard for me to create ionic web-components DOM structure on node.js server. What if I couldn't do it at all - does SSR gives me other benefits?

If I forget about First Contentful Paint which is delivered by server side, I can just use client side rendering which is happening during hydration. If I do display: none (or maybe better visibility: hidden) on 'non-hydratable' DOM from server I still have all needed data for crawlers. I will remove 'non-hydratable' DOM just before client hydration and update the DOM with fully interactive ionic app.

https://github.com/saviorsoul/nuxt-ionic/blob/9121b9afe1822f12911feea45ff544a6e4e51afd/src/runtime/app.vue

I'm able to use data fetched from server side, which is available for me in window.__NUXT__ - I can still speed up client side rendering if I only cache some requests on server side and it will increase my Time To Interactive.

SEO or media preview crawlers might be able to get all the needed data from meta tags and web components that are just plain DOM elements. Maybe it will be even beneficial for crawlers like the one from Bing which doesn't use Javascript?

In mobile context I don't need SSR and SEO, my understanding here is that setting ssr: false in nuxt.config.ts for build should be enough.

https://medium.com/patternfly-elements/web-components-and-seo-58227413e072
So I think to summarise this whole concept, maybe SSR integration with Ionic doesn't gives us easy way of pre-rendering DOM structure on server-side but can gives us all other benefits from both Nuxt and Ionic frameworks?


Use OpenAlex instead of individual sources

This is a great resource! https://openalex.org/ Has an API, connects many many sources (interestingly, not ones like Scopus, bioRxiv, or medRxiv, the same ones we were struggling with). Might be easier to switch to those? Or another time maybe :stuck_out_tongue:

This tool is fantastic. Rearranged code to only use this. Removed a lot of code because of it! See #64


[BUG] ab_channel query is broke the queue.play

Bug Description
If you add "ab_channel" query to the end of the URL, the result will be wrong.
Reproduction Steps
Steps to reproduce the behavior:

Try queue.play() with not query used in end of url
Find and play true song.
Try queue.play() with query used in end of url
Find wrong song.

Expected Result
Result does not change.
Attachments
True video:

Wrong video:

Wrong video on Win:

Versioning:

OS: Ubuntu or Windows 10.
Node Version: v18.13.0 - Hydrogen
Module Version: 9.1.1

Additional Comments
Unrelated, but ytsr is useless.

Having this same error here

Seems like a node-ytsr bug  https://github.com/TimeForANinja/node-ytsr/pull/189

Fix in bump.


Allow use of non-system compiler to build mlir_generated tests

Allow setting of LD_LIBRARY_PATH to reach execution environment of tf_to_kernel so it can load correct version of libstdc++ and so avoid build failure when built with non-system gcc
Fixes #50873

@elfringham  Can you please resolve conflicts? Thanks!

This appears to have been made moot by the merge of #44549


Error in gloss blocks many functions

There is a problem opening a test gloss (we can't find back which, wessel_test3 comes closest to our memory), and now 'search gloss containing we' for instance leads to an error.
We have been deleting many handshape values that were no longer in use, perhaps that is related.
Wasn't able to delete the gloss in the admin either.

Ha, interesting bug. After some investigation, I discovered that wesseltest3 was still using a fieldchoice (of type 'handshape') that was deleted. Once I changed some phonology settings, everything seems normal again. You can safely search for 'wes' again :)
Maybe we want to create an issue that somehow checks whether a fieldchoice is in use before it's deleted in the admin?

thanks Wessel; I'll add that issue, good idea


document NavMeshQuery random seed functionality

I recently created a new project with an updated version of recast-navigation, and noticed the deterministic nature of NavMeshQuery.findRandomSeed, which is amazing.
Even though the implementation makes perfect sense, I was still a bit surprised to see that I got the same series of reproducable randomness as I ran my project over and over, so I was wondering

is this how it used to be before, but implicit, or is this a breaking change from before you introduced setRandomSeed?
does the documentation mention this anywhere?

For the second question, I could not find any documentation on it, and wanted to add it to the README, but could not find a good place to put it. I think it would make sense to mention this functionality, the default seed of 1337, and the expected behavior.

Hey @GGAlanSmithee!
Thanks for creating the issue. There isn't any documentation for this outside of the auto generated docs yet. I'll add some documentation for randomness & setting the random seed shortly and share it here to get your thoughts.
This isn't a breaking change - previously the same seeded random number generator was already being used, but now the seed can be set.

@isaac-mason
cool!

This isn't a breaking change - previously the same seeded random number generator was already being used, but now the seed can be set.

Yeah, I figured. This is really nice though!


[WIP] Batch jobs

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

Comparison is base (ddb890b) 74.0% compared to head (2f39e7a) 73.5%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files

Files
Coverage Δ

src/proto/mod.rs
69.1% <ø> (ø)

src/proto/single/mod.rs
98.0% <100.0%> (ø)

src/producer/mod.rs
47.5% <0.0%> (-18.1%)
:arrow_down:

src/proto/batch/cmd.rs
0.0% <0.0%> (ø)

src/proto/batch/mod.rs
81.6% <81.6%> (ø)


Scan all drives doesn't list excluded paths

When using the --all-drives option the excluded paths aren't listed in the program output, but they are if you use  C:\ as the path to scan.
I'd expect them to be listed whatever scan options are present.

@philrandal Would you test v2.3.4?

Perfect!  Many thanks.


Prototype components with closed style API

Idea: use ui-box, the underlying engine behind evergreen.


Python target version for Black formatter is not up-to-date

This commit d4a17c2 fixes this.

This commit d4a17c2 fixes this.

We should use py39 as this is the version that we use in Lambdalizator as a default one 😉
Let's adjust it within #84.

Solved in updates target version for black to py39

Solved in updates target version for black to py39


svd_compressed() fails at calculating svd for complex matrix

What happened:
svd_compressed() fails at calculating svd for complex matrix. I reconstructed the matrix using M'=UΣV^† . The real matrix input yields reasonable answer, and it fails for complex matrix input.
I calculated the trace and norm of M-M' (M:original matrix; M':M'~UΣV^†) which should be small. On the complex case, difference between M and M' is large.
trace:(768972.9893344672+7563949.776901031j)
norm:54801713.60352144

But on the real case, it yields a reasonable answer.
trace:-2.470109161656353e-08
norm:1.8832952585877038e-07

What you expected to happen:
On the case of complex matrix input, the trace and norm of M-M' should be small.
Minimal Complete Verifiable Example:

code:
import os
import sys
import time
import numpy as np
from opt_einsum import contract

from dask.distributed import Client
from dask_cuda import LocalCUDACluster
from dask_cuda.initialize import initialize
from dask.utils import parse_bytes
from dask.distributed import performance_report
from dask.distributed import wait
from dask.distributed import get_task_stream

import cupy
import rmm
import cudf
import dask.array as da

def setup_rmm_pool(client):
    client.run(
        cudf.set_allocator,
        pool=False,
        #initial_pool_size= parse_bytes("1GB"),
        allocator="default"
    )
    client.run(
        cupy.cuda.set_allocator,
        #rmm.rmm_cupy_allocator,
        rmm.mr.set_current_device_resource(rmm.mr.ManagedMemoryResource())
    )

if __name__ == "__main__":

    initialize(create_cuda_context=True)

    cluster = LocalCUDACluster(local_directory="./tmp/",
                                memory_limit=None)

    client = Client(cluster)
    setup_rmm_pool(client)

    nprs = np.random.RandomState(seed=1234)
    rs = da.random.RandomState(seed=1234,RandomState=cupy.random.RandomState)

    SIZE = 15000
    k = 32

    b = nprs.rand(SIZE) + 1j * nprs.rand(SIZE)
    b = da.from_array(b, chunks=(5000))
    b = b.map_blocks(cupy.asarray)
    #a = contract("i,j->ij",b,b) * 10
    a = da.einsum("i,j->ij",b,b) * 10
    #a = a.persist()

    a = da.exp(1.2*a)

    t0=time.time()
    u,s,vh=da.linalg.svd_compressed(a,k=k, seed=rs)
    u,s,vh=da.compute(u,s,vh)
    t1=time.time()
    u=da.from_array(u,chunks=(5000,k))
    vh=da.from_array(vh,chunks=(k,5000))

    #b = contract("ij,j,jk->ik",u,s,vh)
    b = da.einsum("ij,j,jk->ik",u,s,vh)
    a = a - b #<-a:M, b:M'
    tr = da.sum(da.diagonal(a)).compute()
    print("trace:{:}".format(tr))
    norm=da.linalg.norm(a).compute()
    print("norm:{:}".format(norm))

    sys.exit(0)

Anything else we need to know?:
Warning occurs while calculating svd:
rapids-22.06/lib/python3.9/site-packages/dask/array/utils.py:101: ComplexWarning: Casting complex values to real discards the imaginary part
  meta = meta.astype(dtype)

And I tried to add
print("meta_from_array:dtype",dtype)

in the "meta_from_array" funtion, and got several "float64", maybe there are some bugs while passing dtype?
Environment:

Dask version: 22.06
Python version: 3.9
Operating System: Linux(HPC)
Install method (conda, pip, source): miniconda

Thanks for the report @LUOXIAO92. I see you've also commented on #7639, mind if we close this and continue the discussion over there? If you feel this a different issue, let us know and we can re-open

That's ok. I thought nobody sight my reply, therefore I created a new issue.


Lion's Head

Added New Lion's Head Trail, Western Cape

Thank you please go ahead with the pull request.

@all-contributors please add @Fruitymo for adding a trail

@all-contributors please add @Fruitymo for adding data

@all-contributors please add @Fruitymo for content


Getting actual Type of an Enumerable

Hi there,
There is an issue when handling a Enumerable property, for example:
public List<SomeType> SomeProperty { get; set; } = new List<SomeType>();
You cannot get BaseClass for the Type of SomeProperty as it is null.
The problem it that the Type for an Enumerable property is SomeType[] and not SomeType.
I assume that nobody needs the SomeType[] and uses a string replace to remove the brackets to get the typename. And in case you want to check if something is an Enumerabe it is better to use the IsEnumerable property is anyway.
It would be great if the value of the Type property can be changed to the actual SomeType Type or another property is added to get this value (to avoid braking changes, though option 1 would be better long term).
This is probably the source issue for #256
Sc0tTy

Sorry for the very late response, but this is the fix/code I needed!
Issue can be closed.


feat(haystack): add instrumentation support

[giant PR]
a first pass at a Haystack instrumentor; the README file will be properly written shortly, just copied from guardrails rn

Hey @21ShisodeParth, can you sign the CLA and rename your PR in keeping with conventional commits? "feat: " is the correct prefix.

Let me know if you need help to pass CI.

I have read the CLA Document and I hereby sign the CLA

recheck

recheck

I have read the CLA Document and I hereby sign the CLA

I have read the CLA Document and I hereby sign the CLA

recheck

Fix your bot, it's tagging the wrong people
why do you even feel the need to even have a CLA, probably just a waste of everyone's time

Closing in favor of #644 @21ShisodeParth


controlPlaneMtls renamed to controlPlaneSecurityEnabled

change comments in various values.yaml files

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: elevran
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: linsun
If they are not already assigned, you can assign the PR to them by writing /assign @linsun in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@elevran: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
b5019e41f1b85b7245e20d166b87f6f648b57133
link
/test istio-pilot-multicluster-e2e

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.

@elevran: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
b5019e41f1b85b7245e20d166b87f6f648b57133
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
b5019e41f1b85b7245e20d166b87f6f648b57133
link
/test istio-integ-k8s-tests

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.

/lgtm
/approve

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: elevran, ostromart
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS [ostromart]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Add support for relaying websockets

What kind of change does this PR introduce?
Adds support for relaying WebSockets with Edge Functions by allowing upgrade requests and then relaying messages between the two sockets.
What is the current behavior?
Cannot establish WebSocket requests as GET requests return an unsupported error.
What is the new behavior?
WebSockets are supported, while denying still denying normal GET requests.
Additional context
This is a supported feature with Deno Deploy so unless there's some conflict with the implementation between Supabase <-> Deno Deploy this should work.
If you want me to add tests let me know, there wasn't any existing ones to use as a base.
https://deno.com/blog/deploy-streams#websockets
As a use-case, I'm using WebSockets for tunneling TCP connections, i.e. SSH/Telnet sessions, which doesn't quite fit within the new Multiplayer features as the other end of the channel is not a client/subscriber but a TCP socket which I don't have control over.

@jabinb Thanks a lot for taking the time to create this PR. Currently, Deno Deploy has an execution limit of 50ms, which would be a blocker for supporting web sockets. We've reached out to Deno team to get it clarified.
We'll contact you and re-open this PR if Deno Deploy changes its execution time limits to support web sockets.