Error window on start: Unable to load NFS_XtendedInput.asi. Error: 126

So this was working initially but few days later just stopped working on all NFS version. I have other .asi file loaded parallel with this and those ones still loading fine (like HD patch). Game start up after this error message however without xinput support.

Error 126 means that a module is missing (DLL missing).
You need to install the VCRedist: https://aka.ms/vs/17/release/vc_redist.x86.exe
And if you're running Win7 install this (whichever is applicable to your game, UG or UG2):
https://github.com/xan1242/NFSU-XtendedInput/releases/download/2.7/Release-UG-Win7-Pack.zip
https://github.com/xan1242/NFSU-XtendedInput/releases/download/2.7/Release-UG2-Win7-Pack.zip

Yes looks like something corrupted my VCRedist installation. Thanks for the link. You can close this issue now. Thanks again.

thanks finally nfshp2 is running 2560 1440 60fps


TypeError: unsupported operand type(s) for |: 'torch._C._TensorMeta' and 'type'

Hello Lorna
I am getting an error message in image_quality_assessment.py, line 584,
kernel: torch.Tensor | tuple,
TypeError: unsupported operand type(s) for |: 'torch._C._TensorMeta' and 'type'
Kindly Help.

I can't judge exactly how this problem arises, guess it may be a return type problem, try to remove the return type?

Are you able to run the code without any error?
After removing the unsupported operand many other errors are arising
Kindly help by telling your environment cuda cudnn pytorch
On Wed, Apr 19, 2023, 01:52 Lorna @.***> wrote:

I can't judge exactly how this problem arises, guess it may be a return
type problem, try to remove the return type?
—
Reply to this email directly, view it on GitHub
https://github.com/Lornatang/SRGAN-PyTorch/issues/74#issuecomment-1513749777,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASPDQNOE3HENBXMSUJBT673XB3ZXHANCNFSM6AAAAAAW7HEQAI
.
You are receiving this because you authored the thread.Message ID:
@.***>

I run in Ubuntu22.04, no error.

请问您解决这个问题了吗？我遇到了同样的问题

TypeError: unsupported operand type(s) for |: 'torch._C._TensorMeta' and 'type'

Use Python >=3.10 This would solve this problem


idea: improve block menu

There are still some UX issues after inserting commands/structures from the block menu like cursor placement etc.

superseeded by #142


Update README

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

Project coverage is 100.00%. Comparing base (f969c57) to head (e292640).

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #50   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           33        33
  Lines          692       692
  Branches        54        54
=========================================
  Hits           692       692

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


fix(app): sort current offsets by date to ensure order

closes RAUT-722 and RQA-1608
Overview
The data fetched from the runQuery hook does guarantee that the current offsets return in the same order. To fix this, I added sorting via createdAt from the offsets key
Test Plan
see the ticket attached, basically run LPC on desktop with offsets already in the table. Make sure they don't reorder during LPC. The reordering starts after the initial page of the LPC flow and ends when you complete LPC
Changelog
added sorting of the current offsets
Review requests
see test plan
Risk assessment
low

Maybe create a sort function for this?
Not recommend to overwrite the data.


[OA-676] Add back second part of job tutorial

Add back programmatic submission now that CLI is updated

OK to merge, but offline flow won't work until https://github.com/anyscale/product/pull/27459/files is live.

This is ready for review again.


Dem volume solid objects

Description
Solid objects are currently only using simplex. This can be problematic since double contacts can occur at the junction of two triangles.  This PR aims at introducing solid objects built from volume elements, which could solve this problem. The contact between particle and volume 3D object is not implemented yet. Only in the creation and the displacement.
Testing
A new test has been implemented. (volume_solid_object_displacement.cc)
Documentation
Old simulation parameters have been renamed. The center of rotation was being defined by 3 parameters.
Subsection center of rotation and its three parameters (x, y and z) have been replaced by one parameter named center of rotation using a list of doubles.
A new subsection solid surfaces need to be used when defining solid object in the parameter file.
Miscellaneous (will be removed when merged)
Checklist (will be removed when merged)
See this page for more information about the pull request process.
Code related list:

[x] All in-code documentation related to this PR is up to date (Doxygen format)
[x] Lethe documentation is up to date
[x] New feature has unit test(s) (preferred) or application test(s)
[x] The branch is rebased onto master
[x] Changelog (CHANGELOG.md) is up to date
[x] Code is indented with indent-all and .prm files (examples and tests) with prm-indent

Pull request related list:

[x] Labels are applied
[x] There are at least 2 reviewers (or 1 if small feature) excluding the responsible for the merge
[x] If this PR closes an issue or is related to a project, it is linked in the "Projects" or "Development" section
[x] If the fix is temporary, an issue is opened
[x] The PR description is cleaned and ready for merge

Just saw that there is a test called floating_mesh.prm if you want to change it

The content of the Miscellaneous section is actually matters of the Documentation in the PR description. Also, is there a reason you don't resolve the comments in the PR once the topic is discussed or modification has been applied? When I review I think that it's not done when it's still there, and this is why I do not rereview or approve. So I just want to know if there is a specific reason and next time I should just change the way I understand it :) Otherwise, all good for me!

I don't get what you mean about the Miscellaneous section . I did add the changed parameter, do I need to do something else?
About the resolve thing, the comments remaining were not modification requests, but more like questions. I like to keep those open because sometime I'm not the one answering those question (like the one Bruno gave about the SerialSolid thing), or someone else would like to comment over my anwser.

This is not reviewed and ready to merge until @oguevremont  has approved the PR.... then I'll review/merge

1-2 last things, seems good to go. I presume the virtual wall (instead of floating wall) will be made in a follow-up PR?

Yes, that what I had in mind regarding the virtual walls.


Docker UI error

Viktor, thank you for writing the book. It is very informative. Under Implementation of the Deployment section, I ran vagrant up cd but I am getting an error on the Docker UI installation.
Error message is as follows:
==> cd: TASK [docker : DockerUI is running] ********************************************
==> cd: fatal: [localhost]: FAILED! => {"changed": false, "error": "APIError(HTTPError(u'500 Server Error: Internal Server Error for url: http+docker://localunixsocket/v1.21/images/create?tag=latest&fromImage=uifd%2Fui-for-docker',),)", "failed": true, "msg": "Failed to pull the specified image: uifd/ui-for-docker"}
==> cd:         to retry, use: --limit @/vagrant/ansible/cd.retry
==> cd:
==> cd: PLAY RECAP *********************************************************************
==> cd: localhost                  : ok=11   changed=10   unreachable=0    failed=1
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
###########################################################################
I checked Docker Hub for the image, it looks like Docker-UI is already deprecated to Portainer.

I will try to replace the Docker-UI with portainer to see if it will work or not.

I tried portainer/portainer image but I got a similar error message. It looks like the issue is the docker syntax in Ansible playbook.
http://docs.ansible.com/ansible/docker_module.html

Can you tell me which chapter you're reading so that I reproduce the problem on my laptop?

Chapter: Implementation of the Deployment Pipeline: Initial Stages
I am using Windows 7 at work with VirtualBox 5.1.22 and Vagrant 1.8

@pitcha I just did a fresh install on my spare Windows laptop and it worked. Can you confirm that your laptop/network is not behind a firewall/VPB/proxy? If it isn't, can you enter the VM and re-run Ansible with verbose flag?
vagrant ssh cd

ansible-playbook /vagrant/ansible/cd.yml -c local -v

Yes, I am behind a firewall/proxy. I already set the proxy code on Vagrantfile.
 if Vagrant.has_plugin?("vagrant-proxyconf")     config.proxy.http     = "http://myproxy"     config.proxy.https    = "http://myproxy"     config.proxy.no_proxy =  ""   end
Output of ansible-playbook with verbose commad can be found here.

You'll need to setup proxy in Docker config, apt, and change npm inside test container to use the proxy as well. It's tends to be tedious. Do you have an option to not use firewall/proxy?

Thank you for your feedback/response. I've  configured the proxy for the components mentioned above but without success. I am exploring another option to use without proxy/firewall.


Scale edits don't work

When I open customize plus now and press the edit profile button the bone window won't open and it will only open when I close the customize plus window. But anything I edit there wont apply to my character or save it. I can't edit or adjust my current scales. I have uninstalled it, cleared the cache and any files off my PC and reinstall but it still gives me the same problem.
Can anyone help?

if this happens open an unrelated profile of a character who's not loaded, close it and click on the one you're having issues opening it should open right up.
if bone's aren't saving, just check you haven't got Anamnesis open, it sometimes invalidates the skeleton check.


usage in node red?

I am interested in using this to store sensor data. I'm new to Mongodb - is it possible to share a sample flow to show how it is used?. I have a mongodb server running and tested.

I second this request


imports should not have inline value

yeah just hit this too

To verify this, set showPythonInlineValues to true.


Unauthorized when making POST request with ajax

Hey, didnt find anything on this so Im asking.
The documentation says that in order to save data (or to get filtered data) you should use this:
fetch('/api/collections/save/posts?token=xxtokenxx', {...
However I am getting {error: 'Unauthorized'} even though the supplied token is valid. I tried with the general token you find in the settings and admin api account token as well.
Im using the master branch.
Any insight on this is welcome. Thanks

OK it works now when I created new user and used its token. I feel like this is a "bug"? I will keep the issue open in case it is in fact a bug.
Cheers.

Also just for the record there is a typo in the docs it says when retrieving filtered data the url is /api/collections/save/posts?token=xxtokenxx when in fact there should be GET instead of SAVE so: /api/collections/get/posts?token=xxtokenxx is correct.

 Why on earth is the docs get us the wrong API endpoint 😂

@adithwip Because the DOCS is for the old Cockpit - you're probably using the Next branch :)

Ok after wasting my time with checking keys i luckily  find your post and that with a new user make no sense.

Also just for the record there is a typo in the docs it says when retrieving filtered data the url is /api/collections/save/posts?token=xxtokenxx when in fact there should be GET instead of SAVE so: /api/collections/get/posts?token=xxtokenxx is correct.

This solved it for me..Thanks. Doc should be updated


Skupper console not accessible with kubectl port-forward

Hi guys,
I run Skupper to connect 2 GKE clusters.
I initialised Skupper using command skupper init --router-cpu-limit "1" --router-memory-limit "1Gi" --controller-cpu-limit "1" --controller-memory-limit "1Gi" on all clusters, then connected clusters and exposed some services.
Everything works like charm except the console. It is exposed via ingress by mistake, but anyway GCP blocks incoming connections so not an issue at the moment.
I tried accessing the console using kubectl port-forward svc/skupper 8080, the browser tries to load the page for while and then nothing.
Here a screenshot:

Here the skupper-service-controller logs:
2023/03/24 10:46:12 http: TLS handshake error from <IP_ADDRESS>:51754: remote error: tls: unknown certificate

I haven't configured any TLS or else, everything is deafult.
I found no documentation about console but it would be really helpful!
I have no idea on how to proceed.
If I have to change configuration, I have no idea how.
Can someone help me please?
Thanks a lot in advance!

Hi @bygui86 ,
If you are running the console from skupper, I think you are missing this step:
$ skupper init --enable-console --enable-flow-collector from the doc https://github.com/skupperproject/skupper-docs/blob/main/modules/console/pages/flow-console.adoc.
Let me know if that solve the problem.

hi @bartoval, thanks for the answer
currently I'm running version 1.2.1
right now I'm running some jobs and I can't have a Skupper restart or outage, but as soon as I can, I try what you suggested!
keep you posted

Hi @bartoval  I upgraded from 1.2.1 to 1.3.0 because the flag --enable-flow-collector was introduced only recently.
Then I tried the command you suggested on Minikube and everything works as described in the link you provided :)
As soon as I can, I try on GKE (upgrade + enable flow) to verify everything is fine there as well.
But I have a question: in case Skupper was already initialised and is currently running in the cluster, how can I enable flow-collector? simply running skupper init --enable-console --enable-flow-collector? does this command perform any restart of any component?
Thanks for the suggestion, keep you posted

At present, the flow-collector placement requires reinstallation of the entire cluster, but it's expected to become more streamlined in the future.


fix skipped tests

Fix tests that fail in windows in CI with error:
fatal: C:\Users\RUNNER~1\AppData\Local\Temp\git-root-20191017-68-73pwp3.sechl\test1.txt:
'C:\Users\RUNNER~1\AppData\Local\Temp\git-root-20191017-68-73pwp3.sechl\test1.txt' is
outside repository

https://github.com/UziTech/git-menu/blob/c447c2f4573c32090c5ac94d2cb3934c97435d78/spec/git/add-spec.js#L41
https://github.com/UziTech/git-menu/blob/c447c2f4573c32090c5ac94d2cb3934c97435d78/spec/git/status-spec.js#L19

:tada: This issue has been resolved in version 3.1.0 :tada:
The release is available on:

GitHub release
Atom package

Your semantic-release bot :package::rocket:


0.3 release

Tasks

[ ] manually test dev.permaplant.net according to protocols #700
[ ] run external link check (book.toml: follow-web-links)
[ ] npm audit, fix security problems
[ ] check if all milestone issues are fixed
[ ] build https://build.libelektra.org/job/PermaPlanT-Folder/job/PermaplanT-Release/
[ ] git tag -s vX.X.X
[ ] git push --tags
[ ] create release PR to pump versions and new section in Changelog
[ ] write announcement

Use case
No response
Related Pull request
No response

I also added this as future documentation in #667, please feel free to comment there if you have ideas on how to improve the release procedure

www.permaplant.net is successfully deployed but I did not tag the commit yet. We could still include some further small fixes (@badnames @ThorbenStaufer @Bushuo), as long as no user participated. (Once someone participated, we better pump to 3.1).
Most important to fix is #713 but please also look at others in https://github.com/ElektraInitiative/PermaplanT/milestone/4
Larger changes should not be done (and won't be merged), so that we don't introduce any new bugs.

@markus2330 I will work on it today in the evening.

I will work on it today in the evening.

Great, thank you! It is rather unlikely that we already work with a participant today, so a fixes this evening would be perfect.
@badnames thx for the urgent fix! fd6585c6b50db63f06715a68c3da6e17a46632a6 is deployed on www.permaplant.net
Looking forward to further small fixes.

Btw. you are also very welcomed to feedback the tour.

I now deployed 5c41142cdf1fce946a14fa99306ab0640a5fef89, it again contains several improvements of the tour texts and fixes (nearly?) everything we found with manual testing.

Btw. you are also very welcomed to feedback the tour.

@Bushuo thx for the feedback and a even bigger thx for the fix!
I would like to get this done today, tomorrow I am not available for most of the day.
@ThorbenStaufer What is the status of #711?
@temmey What is the status of import of sizes #479? Would be great to get this in, especially if it is already done?
Please do these fixes first to get this done.

I'll hopefully do the release tomorrow in the early morning. Our first participant is tomorrow 16:00.

Our first participant is tomorrow 16:00.

Isn't our first one at 10:00? He at least registered for the 10 am. slot.

dbd1dde54ae295e16cc8d321b09bcea401ccc646 now got tagged with v0.3.0
We also improved mergedDatasets.csv with many manual fixes, to be automated later. This is now also in a repository (you should have got access) and also tagged with v0.3.0
A big thanks to everyone involved in this release. Really great work with many important last-minute fixes!

Isn't our first one at 10:00?

Yeah, looks like it someone else registered on the 10am slot. But that shouldn't be a problem, as everything is released&ready! :rocket:

#733 is also merged, so it is now a good time to rebase PRs, CHANGELOG.md should now target 0.3.1
:rocket:


Support for multivariate distributions

_ Is refactor
\X Is new feature
_ Concerns documentation

Description of suggestion or shortcoming:
From perusing the documentation and trying out various things, Squiggle seems to be missing support for multivariate distributions, which makes a lot of things awkward or impossible :)

Yep, we've been thinking about this. It definitely gets tricky, as JS doesn't seem to have good libraries with multivariate support, but we could probably add some simpler options.
Can you be more specific about the functionality you'd want?
I know that often multivariate normals or other simple multivariates are used, maybe we could get far with just a few multivariate structures. I'm not an expert here.

Given that this is just for forward estimation/prediction (new FR forthcoming!), multivariate normals would indeed be sufficient. One can get a multivariate normal from a vector of independent normal scalar RVs by matrix multiplication, but this is also missing ;)

Yea, matrix operations are something I'd like to provide basic support for, but it's definitely more work.
 There's definitely a lot of improvements we'd like to make!


Support for Python Rules that are Code Generators

Checklist

[ ] I have filed an issue about this change and discussed potential changes with the maintainers.
[ ] I have received the approval from the maintainers to make this change.
[x] This is not a stylistic, refactoring, or cleanup change.

Please note that the maintainers will not be reviewing this change until all checkboxes are ticked. See
the Contributions section in the README for more
details.
Discussion thread for this change
Issue number: #6725
Description of this change
Discovery and handling of code-generator Rules
The change introduces the ability for a code-generator Rule being able to carry a Tag intellij-py-code-generator. The presence of this tags signals...

to the aspect logic that it should treat the outputs of the Rule as sources and also to consider the output imports provided on the PyInfo Provider as the imports for the Rule. These output imports need to be mapped so that they look like input imports such as would be configured with the likes of the py_library Rule.
to the base Plugin logic signalling that the Rule should be further processed for sources.
to the base Plugin logic signalling that the Rule is of py_library Kind as it will feign being a py_library.

In this way, the Plugin will deal with the output of the Rule as sources + imports rather than the input Rule attributes of srcs and imports.
After the logic in SyncProjectTargetsHelper issues a bazel query ... to find Targets, it will issue a second bazel query ... to search for the Tag intellij-py-code-generator. The mechanism has been implemented in such a way that other languages could potentially use this Tag-based mechanism in the future so the review should consider the generality of the solution. It would be possible to issue a single cquery (with Starlark code) to perform both queries in one go, but such a cquery would be in consideration of build options which is probably not what is required in this case.
I have also considered the option of querying for the PyInfo provider as a signal that a Rule were a code-generator for a Python project. I rejected this approach so far because...

there may be Rules which don't want to be recognized as a code-generator even though they emit a PyInfo.
the Tag approach with intellij-py-code-generator is opt-in so is less risky.
for other languages, a Tag approach will be an option whereas there may not be a specific Provider to work from.

A second change, this time in AbstractPyImportResolverStrategy, will alter the logic of collecting Python sources such that it is able to cope with processing a directory because this scenario is likely to come up with code generators. The source directory is walked looking for .py files. If it encounters a "boundry file" such as WORKSPACE or BUILD.bazel then it will stop traversing the directories. In reality this won't happen with code-generators but it is implemented to ensure that the directory processing will work more generally.
The pull request also carries some light documentation and a working example to demonstrate the feature.

Please hold off on review as I am investigating a change in the way the logic will detect the code-generator scenario.

I have done some investigation to try to avoid the use of the intellij-py-code-generator tag. I have experimented with adding an OutputGroupInfo Provider to the code-generator Rules which carries a py_generated_srcs depset. For example;
OutputGroupInfo(
    py_generated_srcs = depset([output_directory]),
),

It is possible to adjust the Python-related Aspect logic in the Plugin to derive the generated Python source from target[OutputGroupInfo].py_generated_srcs instead of from target[DefaultInfo].default_runfiles.
The problem is filtering the code-gen Targets to run with the Plugin's Aspect. The Plugin primarily does this filtering by running a Bazel query to find the Targets and Kinds and then filters on the Kind; py_binary, py_library, java_library, go_binary etc.... It has no means of knowing that some bespoke Rule with a Kind such as some_simple_py_generator provides the OutputGroupInfo with attribute py_generated_srcs.
Whilst it is possible to run a second Bazel query to be able to identify Targets that carry the intellij-py-code-generator tag, a similar query (rather than cquery or aquery) seems to be not possible for finding the OutputGroupInfo with attribute py_generated_srcs so that those Targets can be included. I assume a cquery or aquery would be unwanted in the Plugin because they would be governed by build settings.
The same problem applies for adding an additional attribute to PyInfo.
From this investigation, given the constraints of the technology, it seems that the solution of identifying the Python code-generators using an intellij-py-code-generator tag remains the best path forward.
Aside from Python... whilst I can see that the JavaInfo Provider has java_outputs to presumably convey generated sources, should a code-generator Rule exist for producing Java sources that were not one of the ones in JavaBlazeRules.java then I am guessing that the Plugin is going to ignore the Rule and that a mechanism such as this with a simiar tag intellij-java-code-generator might be likewise useful in the future and that this implies the code added to LanguageClass also makes sense in this PR.

@ilanKeshet would it be useful in your case?

Summary of outcomes on discussion around this;

The use of the "tag and query" approach is undesirable because of the additional query operation
A better approach would be to configure a list of Rule Kinds that are known to be code-generator
Suggested this could be configured in the .bazelproject files
@andponlin-canva to investigate this and attempt to shift the PR over to use this approach instead

I woud prefer to develop PEP273-based solution, but PyCharm seems not to support it yet, so let's go


Words in text are interpreted as a reference

Thanks for this :)
When trying to get references from text strings sometimes a word matching a bible book returns a full book reference. For example, the word "mark" in here is giving me an extra ref. Is there a way we can add a flag on the get_references function to say if a chapter number is required in the match?
text = """This one thing I do, forgetting those things which are behind.... I press toward the mark
    for the prize of the high calling of God in Christ Jesus. Phil 3:13, 14"""
references = bible.get_references(text)

print(bible.format_scripture_references(references))

#Mark;Philippians 3:13-14

Hi Christopher,
Good catch! I'll work on getting a unit test that reproduces this and then implementing a solution for it.
Thanks,
Nathan

Hey Nathan, as opposed to creating a new issue, I felt adding to this one made sense. As Christopher mentioned, it would be great to have a flag which requires a chapter number. Additionally, it would also be great to require a verse number. One of the issues I'm having is that if the text includes something like Genesis 30, it returns the entire chapter 30. It makes sense, but due to my use case this is a problem. I can detect if a reference is an entire chapter but checking the verses to see if they are the start and end of the chapter, but then I can't tell the difference between a reference like Malachi 4 and Malachi 4:1-6. This means I can't myself remove references that didn't include verse numbers because I have no way of telling the difference in the reference object.
Also like Christopher mentioned, thanks for this. What an awesome tool so far!

Still getting caught up on everything here on the open-source side of life after a busy season...
This sounds like a good suggestion. Let me think about it for a little bit and then play around with implementing it to see what, if any, unintended consequences pop up. But, I think this is something that is doable and useful.


Revamping Kafka Streams docs for functional style

Resolves #703

@sabbyanandan Thanks for the review.


How to share

How do we want to share task that belong to a battery?
This issue involves tasks such as CamCAN (EmoMem, EmoReco, Catell, ...), Aomic (Harriri, WM, Stroop, ...), Preferences, and so on. These are groups of tasks that come all from a battery but in the documentation and in the files, they are reported as individual tasks, and then in the text we make the clarification that they belong to a battery.
The issue is that here in public_protocols we are so far grouping them in batteries, i.e. Aomic folder and inside we go into the separation. I would like to change this and have separated folders, as we treat them as individual tasks, which would result into, for example, 4 folders: HarririAomic, StroopAomic, etc... insted.
@bthirion

Thank you for the discussion !
Well, if you consider downstream tasks (e.g. re-using the output of IBC for cognitive mapping), the battery aspect is not meaningful.
Second, it is not meaningful either if you think in terms of BIDS organization (the "battery" level does not exist --- and it is probably not needed).
To me, public_protocols is there for another reason: make it possible to reproduce / re-run IBC analyses on more people; but I guess that the battery structure is a bit more useful here, because when it comes to undertaking new acquisitions/experiments each battery has its own logic and it has to be understood.
Overall, I'm happy with the current organization and I don't think it could create confusion --- but this is open to discussion.

For me, the issue comes when a user is looking at the documentation or for example, a poster where we present some maps for a task that it's part of a battery, so they come to public_protocols and they don't see the task at a first glance. On the other hand, I've been working on having a small github icon on the implementation tab where we can put a link to each task dir on the repo, so maybe with that it will be bullet proof.


Update ESLint configuration and make it run during development

I realized that because we have an .eslintrc file, Gatsby defers to us to run ESLint, so ESLint is not running by default. This change generally follows the docs for setting up custom ESLint rules with Gatsby: https://www.gatsbyjs.org/docs/eslint/
In order to re-enable running ESLint automatically on build during development, we need to either use gatsby-plugin-eslint or set up eslint-loader and the default rules manually. I chose to use the plugin.
This PR also fixes all but three ESLint errors/warnings.

Outstanding ESLint warnings that I wanted to defer to @adamschwartz on are:
warn ESLintError:
/Users/ispivey/cf-repos/workers-docs-engine/src/components/mdx/custom-syntax-highlighting.js
  29:27  warning  Unnecessary escape character: \#  no-useless-escape

✖ 1 problem (0 errors, 1 warning)

warn ESLintError:
/Users/ispivey/cf-repos/workers-docs-engine/src/components/mdx/demo.js
  17:7  warning  <iframe> elements must have a unique title property  jsx-a11y/iframe-has-title

✖ 1 problem (0 errors, 1 warning)

warn ESLintError:
/Users/ispivey/cf-repos/workers-docs-engine/src/components/mdx/youtube.js
  13:9  warning  <iframe> elements must have a unique title property  jsx-a11y/iframe-has-title

✖ 1 problem (0 errors, 1 warning)

This is awesome. Thank you so much!


Possible bug in interaction between Ecto empty_values, LiveView and dead view

Elixir version
Elixir 1.14.1 (compiled with Erlang/OTP 25
Database and Version
PostgreSQL 15.3
Ecto Versions
3.10.1
Database Adapter and Versions (postgrex, myxql, etc)
Postgrex
Current behavior
After upgrading to 3.10.2 from 3.7 (yes, significant upgrade). I am getting:
ArgumentError: cannot deserialize &Ecto.Type.empty_trimmed_string?/1, the term is not safe for deserialization
  File "lib/plug/crypto.ex", line 80, in Plug.Crypto.non_executable_terms/1
  File "lib/plug/crypto.ex", line 87, in Plug.Crypto.non_executable_list/1
  File "lib/plug/crypto.ex", line 66, in anonymous fn/3 in Plug.Crypto.non_executable_terms/1
  File "maps.erl", line 233, in :maps.fold_1/3
  File "lib/plug/crypto.ex", line 66, in anonymous fn/3 in Plug.Crypto.non_executable_terms/1
  File "maps.erl", line 233, in :maps.fold_1/3
  File "lib/plug/crypto.ex", line 66, in anonymous fn/3 in Plug.Crypto.non_executable_terms/1
  File "maps.erl", line 233, in :maps.fold_1/3

Expected behavior
The application continues to work without throwing exceptions.
Preliminary research
The problem is that I have a dead view; inside it, there is a LiveView rendered with live_render function.
There was a similar issue reported here:
https://github.com/phoenixframework/phoenix_live_view/issues/180#issuecomment-482976498
so I understand I should not put the changeset in the LiveView session.
However, I am not trying to do that. My problem is that the changeset is in the session because of the parent dead view, so it is "by accident".
According to the docs https://hexdocs.pm/phoenix_live_view/Phoenix.Component.html#live_render/3
the session option can only add to the session, so the error persists even if I put an empty map there.
I thought putting a changeset in the dead view session was an OK practice. If that is the case, there is this interplay between:

Ecto putting the function in the changeset
dead view with changeset in the session
live_view session deserializer tripping on functions in deserialized data (since it is unsafe)

I am putting the issue here since I am still determining where the problem is and upgrading Ecto surface it.
Feel free to close the issue if I am not supposed to put changesets even in a dead view session.
Otherwise, I am not sure if the problem lies in Ecto or Phoenix/LiveView

This is expected. There is no guarantee changesets are serializable and my recommendation is to not store changesets in sessions. Instead, store the data that allows you to build them.
Another reason to not store changesets in session is because we can add new fields, then when you update Ecto, it is broken. Generally, you should only store data that you on (and even then, with care).

Thank you for your quick answer! Much appreciated.
I have a followup question.
Would it make sense to fail a little bit earlier and disallow serializing unsafe data in the first place?
I like symmetry :)

We could at the cost of also making serialization more expensive, which I am not sure if worth it?

More context on the issue (I'm working on this alongside @tomekowal):
So far I found that problem surfaces iff:

Changset include nil values
Ecto being at 3.10
(based on the code read-through, I wasn't able to downgrade to lower version)

I won't argue with the rationale - because I agree - yet we are where we are 😉
I find it a ninja issue - not very visible (no indication what is causing it) with the same code working before. It's failure during channel join/token verification (it creates working channel fine) the visible manifestation is a form reloading every 30s.
I hadn't found even single &Ecto.Type.empty_trimmed_string?/1 reference anywhere during data inspections on multiple levels, and I believe Phoenix's token seems to be the only element affected.
Just to note - I have exact same issue with different app than mentioned above (we have dependency sync). See slightly longer stack trace (see below). Same root cause - nil within Changeset passed as a parameter to live_render.
** (ArgumentError) cannot deserialize &Ecto.Type.empty_trimmed_string?/1, the term is not safe for deserialization
    (plug_crypto 1.2.3) lib/plug/crypto.ex:80: Plug.Crypto.non_executable_terms/1
    (plug_crypto 1.2.3) lib/plug/crypto.ex:87: Plug.Crypto.non_executable_list/1
    (plug_crypto 1.2.3) lib/plug/crypto.ex:66: anonymous fn/3 in Plug.Crypto.non_executable_terms/1
    (stdlib <IP_ADDRESS>) maps.erl:411: :maps.fold_1/3
    (plug_crypto 1.2.3) lib/plug/crypto.ex:66: anonymous fn/3 in Plug.Crypto.non_executable_terms/1
    (stdlib <IP_ADDRESS>) maps.erl:411: :maps.fold_1/3
    (plug_crypto 1.2.3) lib/plug/crypto.ex:66: anonymous fn/3 in Plug.Crypto.non_executable_terms/1
    (stdlib <IP_ADDRESS>) maps.erl:411: :maps.fold_1/3
    (plug_crypto 1.2.3) lib/plug/crypto.ex:66: anonymous fn/3 in Plug.Crypto.non_executable_terms/1
    (stdlib <IP_ADDRESS>) maps.erl:411: :maps.fold_1/3
    (plug_crypto 1.2.3) lib/plug/crypto.ex:99: Plug.Crypto.non_executable_tuple/2
    (plug_crypto 1.2.3) lib/plug/crypto.ex:51: Plug.Crypto.non_executable_binary_to_term/2
    (plug_crypto 1.2.3) lib/plug/crypto.ex:330: Plug.Crypto.decode/2
    (phoenix_live_view 0.17.7) lib/phoenix_live_view/static.ex:29: Phoenix.LiveView.Static.verify_token/2
    (phoenix_live_view 0.17.7) lib/phoenix_live_view/session.ex:60: Phoenix.LiveView.Session.verify_session/4
    (phoenix_live_view 0.17.7) lib/phoenix_live_view/channel.ex:805: Phoenix.LiveView.Channel.mount/3
    (phoenix_live_view 0.17.7) lib/phoenix_live_view/channel.ex:58: Phoenix.LiveView.Channel.handle_info/2```

We could at the cost of also making serialization more expensive, which I am not sure if worth it?

Probably not worth it.
It could be worth it if we could make the check on serialization but then skip it on deserialization. However, AFAIU, that is impossible because somebody could tamper with it.


HIVE-26400: Provide docker images for Hive

What changes were proposed in this pull request?

Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

Is there any scope to run it with local version of Hive/Hadoop/Tez or do we need a released version always for this?

The quick answer is yes, but there are some places to modify in order to run specified version:

change version in docker-compose.yml
https://github.com/apache/hive/blob/213208570d1efa0f7a41d5a742edd0439b99163b/dev-support/docker/docker-compose.yml#L51-L52
change the download url in Dockerfile
https://github.com/apache/hive/blob/213208570d1efa0f7a41d5a742edd0439b99163b/dev-support/docker/Dockerfile#L37-L43

I'm wondering if we can build hive from source directly, but need some feedback and investigation.

The new changes add support for running with local version of Hive:
sh deploy.sh --hadoop <hadoop version> --tez <tez version>

this command will build the image with given Hadoop and Tez version, and the local packaging/target/apache-hive-${project.version}-bin.tar.gz that built from source, a cluster with HiveServer2, Metastore and MySQL would be started.
We can also build the image with a specified Hive version, just append --hive <hive version> to the above command.
By default, the command will read the version info from project pom.xml:  project.version, hadoop.version, tez.version, these properties are read as hive version, hadoop.version, tez.version and used for deploy.sh to build the image.
Besides, we can start a standalone HiveServer2 only with embedded Metastore,
sh deploy.sh --hiveserver2

or just start a standalone Metastore with derby,
sh deploy.sh --metastore

@kgyrtkirk @abstractdog @pvary any ideas or suggestions? Thank you!

Very nice work @dengzhhu653!
Could we add BeeLine to the examples, so the user could start to run queries immediately?
Will we officially provide an already built image for the Apache Hive versions? It would be good to update https://cwiki.apache.org/confluence/plugins/servlet/mobile?contentId=27362090#content/view/27362090 for using these images.
Thanks, Peter

is there a chance that we can build this docker image + run simple queries in precommit time? otherwise, I'm afraid we cannot guarantee the stability of this feature

Very nice work @dengzhhu653!
Could we add BeeLine to the examples, so the user could start to run queries immediately?
Will we officially provide an already built image for the Apache Hive versions? It would be good to update https://cwiki.apache.org/confluence/plugins/servlet/mobile?contentId=27362090#content/view/27362090 for using these images.
Thanks, Peter

Seems we should create the remote offical repository first, any suggestions on the repository name?
such as apache/hive-hiveserver2, apache/hive-metastore, or just apache/hive? also cc @nrg4878, @abstractdog, @ayushtkn
Thanks,
Zhihua

is there a chance that we can build this docker image + run simple queries in precommit time? otherwise, I'm afraid we cannot guarantee the stability of this feature

I've just realized that the docker image isn't built from the latest master, but instead from an already released hive version, so after thinking this over again, I guess we don't need a docker image build + test in precommit time (my original idea was to automatically check for every single hive commit if it breaks the image...like a smoke test)

why is this closed? I cannot see the patch on master
I would be sad to see this forgotten, how can we proceed with this?

@abstractdog Agreed. when the PR has no activity, it automatically gets closed. I am re-opening the PR.

@zabetak @abstractdog what is to be done for this here. This seems like very useful and easier way to run hive services out of the box than dev-box setup though less powerful.
the dev-box setup is not part of hive codebase as I understand it. What is it we want to complete before this can be merged? Tahnk you

@zabetak @abstractdog what is to be done for this here. This seems like very useful and easier way to run hive services out of the box than dev-box setup though less powerful. the dev-box setup is not part of hive codebase as I understand it. What is it we want to complete before this can be merged? Tahnk you

I haven't picked up the context here yet
need to check what we have at the moment, I'll try out what was implemented here
my expectation is that I can run different hive components very conveniently on my local machine according to a readme (also included in the repo), and if so, this PR is good to be merged in, let me check next week

@deniskuzZ any thoughts about the PR? Thank you in advance!

I had some comments earlier, if you can confirm you addressed those @dengzhhu653 , I'll take a second look and approve, it's time to merge this I believe
please create an umbrella ticket for hive docker improvements and add this one as the first sub-jira, let's track further improvements there

I had some comments earlier, if you can confirm you addressed those @dengzhhu653 , I'll take a second look and approve, it's time to merge this I believe please create an umbrella ticket for hive docker improvements and add this one as the first sub-jira, let's track further improvements there

I've merged the two images into only one(apache/hive), and create a parent jira to track the improvements, please take a look if have time, thank you!

I love this initiative. Can we get more eyes on it?
I have 2 comments about it:

HMS can work together with MySQL but to many times we found bugs with MySQL which gave us a lot of headache. Is it possible to change for Postgre?
I think we should ask a docker account to push the image to the repository as we have a new build or new release.

What is the remaining part of this task to make it happens?

Thank you @TuroczyX for the comments.

Have changed the back db to Postgres or embedded Derby;
This is the remaining part, want to track it in the future after this task has finished.

Excellent! We have started a conversation today how we can regularly publish the hive into the docker hub. It would be cool if the daily build or the release version could be playable easily.
Can't wait to play with it :)
-Attila

Should be included in this initiative also create an docker image for the hive metastore standalone?
Something like this: https://techjogging.com/standalone-hive-metastore-presto-docker.html
https://github.com/arempter/hive-metastore-docker/blob/master/Dockerfile
https://github.com/aws-samples/hive-emr-on-eks/blob/main/docker/Dockerfile
Thanks

Should be included in this initiative also create an docker image for the hive metastore standalone?
Something like this: https://techjogging.com/standalone-hive-metastore-presto-docker.html
https://github.com/arempter/hive-metastore-docker/blob/master/Dockerfile
https://github.com/aws-samples/hive-emr-on-eks/blob/main/docker/Dockerfile
Thanks

It is a good point. @dengzhhu653 @deniskuzZ @ayushtkn  @abstractdog What do you think about it?

Should be included in this initiative also create an docker image for the hive metastore standalone?
Something like this: https://techjogging.com/standalone-hive-metastore-presto-docker.html
https://github.com/arempter/hive-metastore-docker/blob/master/Dockerfile
https://github.com/aws-samples/hive-emr-on-eks/blob/main/docker/Dockerfile
Thanks

It is a good point. @dengzhhu653 @deniskuzZ @ayushtkn @abstractdog What do you think about it?

The image can serve both HS2 and Metastore, as you can see in the README: https://github.com/apache/hive/pull/3448/files#diff-75345b4702a737ff955983bea3daeac9243e26ef1d2dc0398a31ef28380da9cb. Separating them needs another build, makes it a bit hard to maintain in the public repo.

Should be included in this initiative also create an docker image for the hive metastore standalone?
Something like this: https://techjogging.com/standalone-hive-metastore-presto-docker.html
https://github.com/arempter/hive-metastore-docker/blob/master/Dockerfile
https://github.com/aws-samples/hive-emr-on-eks/blob/main/docker/Dockerfile
Thanks

It is a good point. @dengzhhu653 @deniskuzZ @ayushtkn @abstractdog What do you think about it?

The image can serve both HS2 and Metastore, as you can see in the README: https://github.com/apache/hive/pull/3448/files#diff-75345b4702a737ff955983bea3daeac9243e26ef1d2dc0398a31ef28380da9cb. Separating them needs another build, makes it a bit hard to maintain in the public repo.

Understandable.

Seems like the build is broken. @deniskuzZ Could you please re-start?

Seems like the build is broken. @deniskuzZ Could you please re-start?

A fork of this gets a green run: https://github.com/apache/hive/pull/4133. I think the broken build is may due to run some time consuming tests in the same split.

Seems like the build is broken. @deniskuzZ Could you please re-start?

A fork of this gets a green run: #4133. I think the broken build is may due to some time consuming tests running in the same split.

Do you need any help?

Seems like the build is broken. @deniskuzZ Could you please re-start?

A fork of this gets a green run: #4133. I think the broken build is may due to some time consuming tests running in the same split.

Do you need any help?

Thank you @TuroczyX.
The build would get a green run if I open another jira, I think the fix doesn't change any codes, nor build, so it's safe to go into master if the change itself looks fine, we can ignore the build failure in such case.

Yes, it should be unrelated. But it would be also great if we have a green build to follow the industrial standard. (Even logically does not have relation)
Btw we need to think about as a community to push hive images into docker hub. That would be super cool.

Any update on this? :)

I think it would be a good idea to add ports for development / debugging like this ones:
-p9866:9866 -p10000:10000 -p10001:10001 -p9000:9000 -p8000:8000 -p3306:3306 -p50070:50070 -p50030:50030

I think it would be a good idea to add ports for development / debugging like this ones: -p9866:9866 -p10000:10000 -p10001:10001 -p9000:9000 -p8000:8000 -p3306:3306 -p50070:50070 -p50030:50030

For debug purpose, you can launch the container with:
docker run -d -p 9083:9083 -p 8009:8009 --env SERVICE_OPTS="-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=8009" --env SERVICE_NAME=metastore --name metastore-standalone apache/hive:4.0.0-SNAPSHOT

SERVICE_OPTS will finally propagate to the JVM args of the service.
I opened a new PR for testing it out, https://github.com/apache/hive/pull/4240 cc @TuroczyX @deniskuzZ.

Excellent! Thank you all of your effort @dengzhhu653!


"Unknown frame descriptor" for ZSTD data.

Describe the bug
When reading a partition of big NDJSON files compressed with ZSTD there is an error appears.
Error: Custom { kind: Other, error: External(ArrowError(ExternalError(IoError(Custom { kind: Other, error: "Unknown frame descriptor" })), None)) }
Meanwhile all files could be easily decompressed with ZSTD terminal utility.
To Reproduce
Try to access big ZSTD files with multiple frames.
Expected behavior
Would be good if it could read it.
Additional context
Same was fixed in Hadoop

Thanks for the report -- can you possiblly share an example of such a file (or instructions for how to create one)?

Here is an example file data.zst.json
And the code, which shows that the file could be perfectly decoded with async_compression which is used in DataFusion. Meanwhile it could not be used to read as DataFrame.
use arrow::datatypes::{Field, Schema};
use datafusion::common::arrow::datatypes::{DataType, TimeUnit};
use datafusion::datasource::file_format::options::NdJsonReadOptions;
use datafusion::datasource::file_format::file_compression_type::FileCompressionType;
use datafusion::prelude::*;
use std::io::Error;
use datafusion::error::Result;
use async_compression::tokio::bufread::ZstdDecoder;
use tokio::io::AsyncReadExt;

const FILE_PATH: &str = "data.zst";

#[tokio::main]
async fn main() -> Result<(), Error>  {

    // read file with tokio and create a StreamReader
    let file = tokio::fs::File::open(FILE_PATH).await?;
    let mut reader = ZstdDecoder::new(tokio::io::BufReader::new(file));

    let mut buf = vec![];
    reader.read_to_end(&mut buf).await?;

    println!("📦 Read {} bytes", buf.len());

    let schema = Schema::new(vec![
        Field::new("OriginalRequest", DataType::Utf8, false),
        Field::new(
            "RequestStarted",
            DataType::Timestamp(TimeUnit::Millisecond, None),
            false,
        ),
    ]);

    // Create context
    let ctx = SessionContext::new();

    // Read data
    let json_options = NdJsonReadOptions::default()
        .file_extension("zst")
        .file_compression_type(FileCompressionType::ZSTD)
        .schema(&schema);
    let df = ctx.read_json(FILE_PATH, json_options).await?;

    println!("🤨 Hello, ZStd issue!");
    df.show_limit(10).await?;

    Ok(())
}

Thank you @Smotrov 🙏

Given we now have a good reproducer on this issue I think it is ready for someone to take a look if they have time

Nice find!
It seems like the current code disables repartitioning for gzip:
https://github.com/apache/datafusion/blob/9f0e0164c73c834260f842f0ee942593707730bd/datafusion/core/src/datasource/physical_plan/json.rs#L157-L159
Maybe we have to do something similar for zstd and other compression types 🤔


Source code for chapter 14: Material Design.

We make one more set of amendments to the BitsAndPizzas app.
This time we convert the interface to use RecyclerViews and
CardViews.

Hello,
Could you send me a quick summary of what your pull request covers?
Thanks.
DG

Thank you bzhar93 !
my problem is to open pasta with recyclerview, cardview  as pizza.


Maintaining Desired Audio Features Post-Anonymization

Issue Description:
As part of our ongoing efforts to ensure user privacy and data protection, we are in the process of implementing and comparing state-of-the-art audio anonymization techniques. While doing so, we want to make sure that certain key audio features are preserved even after anonymization. This will help us maintain the functionality of our audio data while still upholding privacy standards.
This issue is intended to track the discussion of maintaining some desired audio features post-anonymization. Please use this issue to list your desiderata and why.

First of all, congratulations on the excellent work you are doing on the topic of voice anonymization.
My first contribution is the following, if you consider the scenario where the speakers present dysphonia, then their anonymized voice would need to preserve this characteristic. One way to measure this preservation would be with the study of statistics derived from Fundamental Frequency, Jitter, and Shimmer (to mention a few) before and after anonymization.


Provide button to delete merged pull request branch

I think it is tricky to clean-up branch of pull-request, for someone who implements new feature on new branch. Currently, you have to go back to your local machine and run a command to remove that branch which is very inconvenience.
This pull request add a button to every merged pull request that head branch still exist that allow user to push that button and delete head branch (see screenshot).

PS. Please merge this pull-request first, this feature depends on a change of git-module. https://github.com/gogits/git-module/pull/15

please merge this pull-request first https://github.com/gogits/git-module/pull/15

Please sign the CLA.

ping @tanapoln

It's sad to see that this was closed as that feature would really add benefit when you're working with  a PR based workflow. From the history of the PR I guess it was because of inactivity of the author?

From the history of the PR I guess it was because of inactivity of the author?

Yes.

Sorry for that, I didn't check github for severals day due to many works.
@Unknwon Do you still consider to accept this request? If yes, I'll continue working on this.

@tanapoln yes, glad see you again :smiley:

@Unknwon please review this

@Unknwon please check

ping @Unknwon


Using the module in a stand alone.

I wanted to use these module in my SBT stand alone module to save data and manipulate it.

Can you please be a bit more specific on what you want to achieve and what's the actual issue?

i have an SBT project that is Not play framework, but it has the play
framework architecture. of resent  i managed to add ebean for mysql to it.
I found that Mongodb would solve the database reads and write that i am
facing. I want to replace the Mysql Ebean with Mongodb. Looking at
play-jongo, just like play-ebean, i can add it to the Stand alone SBT
project and use it.
The problem is that i don't know how to add it and if it can work without
play framework plugin. My application is a Java jar.
*Regards, *
CTO and Dev, creativeDNA  (U) LTD. http://www.creativedna.co.ug/
@Google Plus https://plus.google.com/+ChrispinusOnyancha
@LinkedIn http://ug.linkedin.com/in/ChrispinusOnyancha
@Tweeter https://twitter.com/Chrisp_onyanx
https://play.google.com/store/apps/details?id=com.creativeDNA.ntvuganda&rdid=com.creativeDNA.ntvuganda&rdot=1&feature=md
On Wed, Sep 7, 2016 at 10:13 AM, Martin Grotzke<EMAIL_ADDRESS>wrote:

Can you please be a bit more specific on what you want to achieve and
what's the actual issue?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/alexanderjarvis/play-jongo/issues/54#issuecomment-245195086,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFLy-f6XRNJOhCdIQFeUD4d0Eqvp-2gxks5qnmQDgaJpZM4J2ikW
.

This plugin is built for / tied to play, so you cannot use it without play. For you it would be easier to use a Mongo client or jongo directly. Cheers

Thanks for the feed back


Add support for solc 0.8.19

solc 0.8.19 just got released https://github.com/ethereum/solidity/releases/tag/v0.8.19

For anyone interested, I added solc 0.8.19 support to dapptools https://github.com/dapphub/dapptools/pull/974.

cc @roynalnaruto

Already have a PR here: https://github.com/roynalnaruto/svm-rs/pull/75
@nikitastupin could you build for 0.8.19 in the solc repo? Thanks!

Hey @roynalnaruto! https://github.com/nikitastupin/solc/commit/af2fce8988e41753ab4f726e0273ea8244de5dba - thanks for reminding!


setTimeout can cause process hangs when run in node:child_process

Describe the bug
When birpc is run inside node:child_process, it will leave unhandled NodeJS.Timeout handles hanging. These should be .unref()'ed.
https://github.com/antfu/birpc/blob/7b1fe90f0719eccd673e8100b1538da466a49adc/src/index.ts#L182-L185
But what's even more critical here is that these timeouts are not cleared with clearTimeout even when rpc call succees. This means that for every single RPC call, an Error object is created after 60 second timeout.
Reproduction script to be run in birpc repository - or if running as standalone, change the import path of birpc. You'll need to install why-is-node-running to see setTimeout pointed out.
$ pnpm i -D why-is-node-running

$ touch birpc-repro.mjs # Add code here
$ node birpc-repro.mjs

import { fork } from "node:child_process";
import { fileURLToPath } from "node:url";
import { createRequire } from "node:module";
import { createBirpc } from "./dist/index.mjs";

const require = createRequire(import.meta.url);
const whyIsNodeRunning = require("why-is-node-running");

const isMain = !Boolean(process.env.CHILD_PROCESS);
const filename = fileURLToPath(import.meta.url);

if (isMain) {
  console.log("[main-process]: Running", process.pid);

  const subprocess = fork(filename, { env: { CHILD_PROCESS: "true" } });
  subprocess.on("exit", () => console.log("[main-process] Subprocess exited"));

  console.log("[main-process]: Exiting", process.pid);
} else {
  console.log("[sub-process] Started", process.pid);

  let callback;
  const rpc = createBirpc(undefined, {
    post: (data) => callback({ t: "s", r: "Hello from RPC", i: data.i }),
    on: (cb) => (callback = cb),
  });

  // This will resolve quickly
  const response = await rpc.hello();
  console.log("[sub-process] Received", response);

  console.log("[sub-process] Exiting", process.pid);

  // If sub-process is stuck and wont gracefully exit, this will printout root causes
  setTimeout(() => whyIsNodeRunning(), 5_000).unref();

Output:
$ time node main.mjs
[main-process]: Running 79086
[main-process]: Exiting 79086
[sub-process] Started 79087
[sub-process] Received Hello from RPC
[sub-process] Exiting 79087
There are 3 handle(s) keeping the process running

...

# Timeout
node:internal/async_hooks:202
node:internal/async_hooks:504
node:internal/timers:164
node:internal/timers:198
file:///x/y/z/birpc/dist/index.mjs:38
file:///x/y/z/birpc/dist/index.mjs:33
file:///x/y/z/birpc/main.mjs:36
[main-process] Subprocess exited

real    1m0.113s            <-- This matches with birpc's timeout
user    0m0.142s
sys     0m0.029s

After unref()'ing the setTimeout:
$ time node main.mjs
[main-process]: Running 81181
[main-process]: Exiting 81181
[sub-process] Started 81182
[sub-process] Received Hello from RPC
[sub-process] Exiting 81182
[main-process] Subprocess exited

real    0m0.104s
user    0m0.078s
sys     0m0.025s

Reproduction
Reproduction script above.
System Info
System:
    OS: macOS 13.4.1
    CPU: (8) arm64 Apple M2
    Memory: 836.11 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.17.0 - ~/.nvm/versions/node/v18.17.0/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 9.6.7 - ~/.nvm/versions/node/v18.17.0/bin/npm
    pnpm: 8.6.2 - ~/Library/pnpm/pnpm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 116.0.5845.96
    Safari: 16.5.2

Used Package Manager
pnpm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

But what's even more critical here is that these timeouts are not cleared with clearTimeout even when rpc call succees. This means that for every single RPC call, an Error object is created after 60 second timeout.

Using the minimal reproduction above and adding console.error inside setTimeout calls reveals that these errors are created for every RPC call.
setTimeout(() => {
+  console.error(`Creating error for ${method} even though it succeeded`);
  reject(new Error(`[birpc] timeout on calling "${method}"`))
  rpcPromiseMap.delete(id)
}, timeout)

$ time node main.mjs
[main-process]: Running 81542
[main-process]: Exiting 81542
[sub-process] Started 81543
[sub-process] Received Hello from RPC
[sub-process] Exiting 81543
Creating error for hello even though it succeeded
[main-process] Subprocess exited


nan loss

System Info / 系統信息
CUDA:  12.4
python: 3.10
diffusers: 0.33.0.dev0
Information / 问题信息

[ ] The official example scripts / 官方的示例脚本
[X] My own modified scripts / 我自己修改的脚本和任务

Reproduction / 复现过程

I randomly selected a few videos to fine-tune hunyuanvideo
But I ended up with nan loss at the first step.
the log is
Training steps:   2%|██                                                                                | 1/50 [00:56<46:19, 56.73s/it, loss=nan, lr=2e-7]

Expected behavior / 期待表现
Get the correct loss value.

@tanshuai0219 I believe we interacted in the Diffusers issue too. Upgrading pytorch to 2.5.1 has been confirmed to fix the nan training loss problem by atleast 3 other people now. Could you give it a try?

@tanshuai0219 I believe we interacted in the Diffusers issue too. Upgrading pytorch to 2.5.1 has been confirmed to fix the nan training loss problem by atleast 3 other people now. Could you give it a try?

Yes,it works for me~ The loss value is normal now. Thanks!


update goreleaser, remove unused step

Description
update goreleaser docker image url ghcr.io/troian/golang-cross to ghcr.io/goreleaser/goreleaser-cross
update goreleaser to v1.17.9
remove unused step Set up Go
Changes include

[ ] Bugfix (non-breaking change that solves an issue)
[ ] Hotfix (change that solves an urgent issue, and requires immediate attention)
[x] New feature (non-breaking change that adds functionality)
[ ] Breaking change (change that is not backwards-compatible and/or changes current functionality)

Breaking changes
Please complete this section if any breaking changes have been made, otherwise delete it
Checklist

[x] I have assigned this PR to myself
[x] I have added at least 1 reviewer
[ ] I have added the relevant labels
[ ] I have updated the official documentation
[ ] I have added sufficient documentation in code

Testing

[ ] I have tested this code with the official test suite
[ ] I have tested this code manually

Codecov Report

Merging #173 (8127848) into dev (cf53f77) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##              dev     #173      +/-   ##
==========================================
- Coverage   51.39%   51.38%   -0.01%
==========================================
  Files         113      113
  Lines       16839    16839
==========================================
- Hits         8654     8653       -1
- Misses       7446     7447       +1
  Partials      739      739

Impacted Files
Coverage Δ

protocol/sync_peer.go
69.00% <0.00%> (-1.00%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Feature/windows support

Adds support for running on Windows.  Some path-related operations were assuming a posix OS.  Now paths are always normalized to Posix-style forward-slash delimiters.  Windows will accept both slashes as a delimiter and does not allow forward slashes in file or directory names, so this should be safe and predictable to users.

Coverage decreased (-0.03%) to 85.208% when pulling 882a14821cc5f3282d4f4cc763e387deddef94f3 on cspotcode:feature/windows-support into 43ecda45f9e22b45f042f4e6625804ac82045933 on buehler:develop.

The decrease in code coverage is because there's an if-else block that runs one statement on Windows, the other on Linux and Mac.

@cspotcode
THANK YOU!
I wanted to do this for so long. But never got time for it. 🎉

This should actually fix some other issues in typescript hero! :-)


Update set-up-mobile-policies-for-your-organization.md

Added Notes
Replaced SkypeOnlineConnector with MicrosoftTeams

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@tonysmit PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


Weird address bar behavior when hostname is not a full url but internal servername

Hi,
We are using your router for a project that uses a server hostname vs a "domain name" and when doing so the address bar starts adding the servername to the url. http://bgowebvrs01/

The first is not loaded, but when hitting enter it immediately ads the hostname, and then after every navigation it ads a new one. The routing works btw I see the expected content.
When I use a full qualified name like http://bgowebvrs01.verit.kgjs.com/ none of this is happening. Also not when developing locally using http://localhost;3000/
-Mark

Btw this is in Chrome and IE and I am using 3.0.1 of the route-url library

@MarkNijhof This isn't to do with this library, but instead sporto/erl which is a dependency of this.
The parsing of earlier versions of the library (10 in this case) is absolutely nonsensical, and has been patched in future versions to be (still absolutely nonsensical) slightly more correct.
The version of sporto/erl in elm-route-url needs updating, I gave it a crack this morning with @philipstears but because the Builder uses a Dict String String and newer versions of sporto/erl use a List String String it involves a breaking change across the library and is a PITA to implement as a casual outsider.
@rgrempel Something to be done here?

Sorry not to get to this sooner. I'm now working on #31 to update the sporto/erl dependency ... hopefully that will take care of it.

I've now published version 4, which will use more recent versions of sporto/erl. Let me know if that helps with this issue!


Hey, great job! I want to know what happened to this mistake during my training. Thank you!

{'batch_size': 128, 'calibration': False, 'dataset': 'cifar10', 'decay': 0.0005, 'droprate': 0.3, 'epochs': 10, 'layers': 40, 'learning_rate': 0.001, 'load': './snapshots/pretrained', 'm_in': -25.0, 'm_out': -7.0, 'model': 'wrn', 'momentum': 0.9, 'ngpu': 1, 'oe_batch_size': 256, 'prefetch': 4, 'save': './snapshots/oe_tune', 'score': 'OE', 'seed': 1, 'test': False, 'test_bs': 200, 'widen_factor': 2}
Files already downloaded and verified
Model restored! Epoch: 99
Beginning Training
Traceback (most recent call last):
File "/home/xxx/code/energy_ood-master/CIFAR/train.py", line 257, in
train()
File "/home/xxx/code/energy_ood-master/CIFAR/train.py", line 180, in train
for in_set, out_set in zip(train_loader_in, train_loader_out):
File "/home/xxx/anaconda3/envs/detectron2/lib/python3.7/site-packages/torch/utils/data/dataloader.py", line 517, in next
data = self._next_data()
File "/home/xxx/anaconda3/envs/detectron2/lib/python3.7/site-packages/torch/utils/data/dataloader.py", line 1199, in _next_data
return self._process_data(data)
File "/home/xxx/anaconda3/envs/detectron2/lib/python3.7/site-packages/torch/utils/data/dataloader.py", line 1225, in _process_data
data.reraise()
File "/home/xxx/anaconda3/envs/detectron2/lib/python3.7/site-packages/torch/_utils.py", line 429, in reraise
raise self.exc_type(msg)
ValueError: Caught ValueError in DataLoader worker process 0.
Original Traceback (most recent call last):
File "/home/xxx/anaconda3/envs/detectron2/lib/python3.7/site-packages/torch/utils/data/_utils/worker.py", line 202, in _worker_loop
data = fetcher.fetch(index)
File "/home/xxx/anaconda3/envs/detectron2/lib/python3.7/site-packages/torch/utils/data/_utils/fetch.py", line 44, in fetch
data = [self.dataset[idx] for idx in possibly_batched_index]
File "/home/xxx/anaconda3/envs/detectron2/lib/python3.7/site-packages/torch/utils/data/_utils/fetch.py", line 44, in
data = [self.dataset[idx] for idx in possibly_batched_index]
File "/home/xxx/code/energy_ood-master/utils/tinyimages_80mn_loader.py", line 51, in getitem
img = self.load_image(index)
File "/home/xxx/code/energy_ood-master/utils/tinyimages_80mn_loader.py", line 16, in load_image
return np.fromstring(data, dtype='uint8').reshape(32, 32, 3, order="F")
ValueError: cannot reshape array of size 0 into shape (32,32,3)
Process finished with exit code 1

It seems your tinyimages file has some problem. You might want to check if you download it correctly.

The tinyimages dataset can't be downloaded. How can I use another dataset to train instead of it

There is a replacement for tinyimages available in the outlier exposure codebase. We recommend checking that out.


[MM-214] Add user's theme support in link tooltip component

Summary

Add user's theme support in link tooltip component

Screenshot

What to test?

Link tooltip component is working properly according to the different themes.

Ticket Link:
Fixes: https://community.mattermost.com/core/pl/97pq3s9u6bnd7ghxx8qpu1x7oc

@matthewbirtch Fixed the review comments added by you


Module documentation tracking issue

I’m working on new documentation for modules in TypeScript. I’ll use this issue to track progress. Related:

#51876
#52412

Proposed, very ambitious outline, subject to change:

Introduction

Who is this for?

Theory

Scripts and modules in JavaScript
What is TypeScript’s job concerning modules?
Module emit

Input syntax is (somewhat) decoupled from output
Note: verbatimModuleSyntax
Note: top-level await
Module format interop
Module specifiers are not transformed

Module resolution

Module resolution is host-defined
Who is the host?
TypeScript “mirrors” the host resolver

Module specifiers reference the host’s source files
Declaration files are substituted for JS files
Note: non-JS files supported with allowArbitraryExtensions

Common resolution features

Omittable extensions and directory index files
node_modules and package.json

@types
package.json "exports"

Node’s dual-algorithm system

CJS/ESM detection

File extensions
package.json "type"

ESM algorithm restrictions
package.json "exports" conditions
Importing ESM from CJS requires dynamic import

Bundlers and other Node-like non-Node hosts

noEmit and allowImportingTsExtensions
Customization options

Caveats / limitations?

Why module specifiers are not transformed
Why dual-emit is not supported and sometimes impossible
Future work? Browser, import maps, URLs?

Guides

Choosing compiler options
Troubleshooting dependency issues
Publishing a library

Reference

Module syntax

ESM (link elsewhere?)
CJS in JavaScript
CJS in TypeScript
Type-only imports and exports
Ambient module declarations & augmentations?

Module emit and checking

module

commonjs
es2015+
node16/nodenext

CJS/ESM interop details
The default problem
__esModule marker
allowSyntheticDefaultExports
esModuleInterop
verbatimModuleSyntax

Module resolution

moduleResolution

node16/nodenext
bundler

allowJs and maxNodeModuleJsDepth
package.json

"main", "types"
"typesVersions"
"exports"
"type"
"imports"

Customization compiler options

paths
baseUrl
resolvePackageJsonImports
resolvePackageJsonExports
customConditions
allowImportingTsExtensions
resolveJsonModule
rootDirs
typeRoots
moduleSuffixes

Who is this for?

Approximately everybody 😄

Another section we'll need is effectively "What is the right thing to put on DefinitelyTyped?"

What module settings should my new project use?

@DanielRosenwasser please refer to section 3.i

All of them

@andrewbranch Two more fields worth covering in 4.iii.c:
module and browser

I'm not sure which section this would go in, but there is a semi-obscure question/choice I'd like to get an authoritative answer on, so I'm kinda hijacking this issue as a place to resolve it.
Question

Is it legitimate for a project to store hand-written utility types in a local *.d.ts source file instead of using a *.ts source file?

It's common to have local files in which you might store utility types.  Maybe you put them in a directory called util-types/.  So which file extension type should you put in this directory?

A full-fat *.ts file would work, but at best will result in an empty *.js file being emitted, and at worst might deviate from programmer intent over time if someone accidentally inserts value-land code.
Whereas a *.d.ts enforces this intent and guarantees to have zero JS emit - it only is needed during checking.

Here's some example usage in a multi-file playground.
// @filename: index.ts
import type { Point } from "./util-types/only-types"
export const location: Point = {
    x: 0,
    y: 0,
}

// @filename: util-types/only-types.d.ts
export interface Point {
    x: number,
    y: number,
}

Potential Answers
I'm looking for a steer on whether the use of *.d.ts files for storing hand-written utility types is:

Encouraged:  because this style has active benefits
Supported:  but there's no value judgement on which style you should pick
Discouraged:  this style is supported and not going away, but may confuse people
Harmful:  it may seem to work but will hurt you later or might be deprecated

The answer will help inform whether we should internally force the use of *.ts files for this purpose by banning hand-written *.d.ts files.

The answer to this question is unsatisfying to me. I would say it’s discouraged or even harmful (though it won’t be “deprecated”). At best, it’s a technique with serious pitfalls that can be leveraged by people who understand them enough to set up additional tooling and safeguards to make it viable. Because .d.ts files only occur “naturally” as a pair with a .js file, together as outputs of a .ts file, a .d.ts file always implies the existence of a .js file. So the potential harm is readily apparent: if you hand-author only-types.d.ts and then write import {} from "./only-types.js", this resolves and is legal in all settings, but in verbatimModuleSyntax, the import will be preserved and crash at runtime. While TypeScript has type-only imports and exports, it lacks the analogous concept of a type-only module, one which exists for type information purposes but is known to not exist at runtime, though I’ve casually suggested multiple times that such a concept could be useful.
But the main reason I personally avoid this is just because it doesn’t copy into outDir. For my purposes, I’d rather just eat the cost of the empty JS file (which also protects you from crashes should you accidentally import it at runtime).

Never been so hyped for documentation

How to make dual-mode packages? #53045

I'm not sure if this is too much, but guidance on how to navigating incompatible packages when migrating a TS project from CJS to ESM would be helpful. I can file tickets on projects to fix their package.json and build processes all day, but ultimately it can be very hard to know precisely what is broken, what to tell library authors, and what patch I need to apply to the package to hold me over in nodenext + CJS mode to prepare to go to nodenext + ESM mode.

There’s enough done now to start sharing some in-progress content for those interested. I’ll keep this gist up to date as I finish significant chunks. Feel free to leave feedback in the gist comments.

Quick update: this is getting fairly close to being done and anticipate getting a PR up to put this on the website in the coming weeks. I just pushed a fairly large update to the gist.

I’m getting ready to merge this. There’s still more to do, but it’s complete enough to publish and iterate on.
Feedback is welcome, so I’ll mention the things I already have on my immediate to-do that I won’t get to before merging

Better introduction?
Glossary
Add moduleDetection, allowSyntheticDefaultImports, esModuleInterop, and verbatimModuleSyntax to the reference section. (These are discussed in other places, but they deserve detailed reference-style sections along with module and moduleResolution values.)
Emphasize declaration file extensions’ impact on module format in theory section
Cross-link to this content from other places in the website (there are redirects from deleted sections, so some will work already, but more can be added—website PRs welcome to help with this!)

I wonder if an appendice about baseUrl and paths belongs in there somewhere? Really made me think about it when reading

Just a couple of feedback points:

https://www.typescriptlang.org/docs/handbook/modules/guides/choosing-compiler-options.html#im-writing-es-modules-for-the-browser-with-no-bundler-or-module-compiler likely could also mention package.json#imports since it also can map to work with a large variety of tooling often more than paths including import maps: https://codepen.io/bradleymeck/pen/YzdmQRN

https://www.typescriptlang.org/docs/handbook/modules/theory.html#scripts-and-modules-in-javascript likely should include type=module in the script tags or disambiguate Script vs Module. I think just putting type=module makes less complexity but could cause confusion when thinking there is only ESM and CJS and it not working.

As far as typescript concerned package.json#imports has no relation to paths, because the latter operates on source files, while the former - on the output files. Bundlers muddy the ground there again, since they obviously bundle the output into whatever so they are free to interpret imports whatever they want. This is not the case if you want to output nodejs ESM modules, however.
The section shows how the the browsers scripts were written in ye olde times, specifically how they all shared the same global scope. And there was no type=module back then.

@GabenGar

The intent of these sections seems to be explanatory and not solely limited to TS hence remarks about import maps. I don't think adding more ways for understanding nuance like the fact that paths differs from package.json#imports is harmful; in fact, your comment could be a great addition to the documentation since it is something coming up here under some tension.
Fair enough for the script tags, but it doesn't explain how this differs from the modern day by showing the modern example.


ccl: pull upstream fix for -fno-common

Without the change build fails on upstream gcc-10 as:
ld: x86_print.o:/build/ccl/lisp-kernel/linuxx8664/../area.h:111: multiple definition of
  `tcr_area_lock'; pmcl-kernel.o:/build/ccl/lisp-kernel/linuxx8664/../area.h:111: first defined here

Description of changes

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

[ ] 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.05 Release Notes (or backporting 21.11 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 173633 run on x86_64-linux 1

1 package built:

ccl


pandas.io.gbq verify_schema seems to be too strict.

This line seems for me to be too strict for repeated insertion, because apparently GBQ is not consistent in the order of fields in the schema (or my application screws the order of fields up, anyway, I would say the verification is too strict).
So for example:
dict1 = {'fields': [{'name': 'coordinates_0', 'type': 'FLOAT'}, {'name': 'created_at', 'type': 'STRING'}]}
dict2 = {'fields': [{'name': 'created_at', 'type': 'STRING'}, {'name': 'coordinates_0', 'type': 'FLOAT'}]}
dict1 == dict2  # gives False

would make verification fail, though insertion would work, as the insert as JSON makes the order of fields irrelevant.
Solved that for myself for the moment with:
    def verify_schema(self, dataset_id, table_id, schema):
        from apiclient.errors import HttpError

        try:
            bq_schema = (self.service.tables().get(
                projectId=self.project_id,
                datasetId=dataset_id,
                tableId=table_id
                ).execute()['schema'])
            return set(
                       [json.dumps(x) for x in bq_schema['fields']]  # dump necessary to make dicts hashable
                      ) == set(
                               [json.dumps(x) for x in schema['fields']]
            )  # this still fails if key order is different. But GBQ seems to keep key order.

        except HttpError as ex:
            self.process_http_error(ex)

cc @parthea

The strict ordering of fields is by design (also in 0.16.2). From the docs:
The dataframe must match the destination table in column order, structure, and data types.

because apparently GBQ is not consistent in the order of fields in the schema (or my application screws the order of fields up
Can you confirm whether it is your application that is changing the order of fields? If we can understand how the ordering of fields is changing, we may be better off fixing that problem instead.

My personal preference would be to fail if the column order of the DataFrame being inserted is different. It is trivial to alter the column order of a DataFrame prior to inserting.
Certainly, the proposed changed would be more flexible, but I think that the user should be aware of the column order, in case the schema has actually changed.

Thanks for your answer. Wasn't reading the docs closely enough apparently. It's very likely that it is my application as I am transforming raw JSON from the Twitter API to a dataframe and the order there is arbitrary. I can try to verify that though. But order of columns seemed (before formatting anything for readable output) pretty unnecessary to me and only costing additional programming time as well as introducing more possibilities for errors to sneak in.
On the other hand, but now we are talking about particular project requirements and personal preferences, this use case it not that unlikely. And I don't know how the order of fields in BigQuery would matter for most applications of BigQuery in the end, as you query for fields by name anyway. For my project it's just another step processing the data (which will come in large volume) before inserting, and I need to minimise those. But yes, that's a design decision. I would plead for a less strict option (maybe with an optional argument in to_gbq?) though.

The number of optional arguments in to_gbq is growing, so it may be better to decide whether to incorporate the change by default or not. The proposed change would certainly make inserting data into BigQuery easier, as long as we are ok with not maintaining column order.
I'd like @jacobschaer to comment. The note in the docs to maintain column order was added in #6937.

just to note that HDF5 requires the orderings to be exactly the same as does SQL. I don't think this should be relaxes. Ok to have a 'better' error message though.

Yes, a more detailed error message would be an improvement. Because neither Python dicts, nor pandas DataFrames nor GBQ really cares about column order, so I did not expect it to matter, it took me quite a while to find out what is wrong with my schema.

Note that for the SQL functions the ordering does not need to be the same (as we use named parameters and a dict with the data to insert)

@jreback Can this be closed, or do you expect a PR for this? I improved the error message in #11401 (already merged)

does thi example work?
eg maybe just need a test to validate this

No, the verify schema function is still strict (column order matters). Should I change this?
def verify_schema(self, dataset_id, table_id, schema):
        try:
            from googleapiclient.errors import HttpError
        except:
            from apiclient.errors import HttpError

        try:
            return (self.service.tables().get(
                projectId=self.project_id,
                datasetId=dataset_id,
                tableId=table_id
            ).execute()['schema']) == schema

        except HttpError as ex:
            self.process_http_error(ex)

is schema ordered?

The verify_schema function is currently very strict. Column order matters. The example solution works. I'll submit a PR to make the verify_schema function less strict and add tests to validate this. I'll also update the docs.


embedded Sim gets cut off at bottom

On New Edge
Example: https://sites.google.com/veaziecs.org/vcscodeclub/student-work/vincent-c/race-2p

Still repros


git_fetch_with_cli does not fetch submodules with cli

Problem

I’m having an issue fetching private ssh submodules with git. I dug around and found this commit which adds the option to fetch urls with the system git. However, it appears to only handle parents and any submodules are handled by this line which effectively still uses libgit2.
~/projects/proj1 (feature) $ cargo build -v
    Updating git repository `https://github.com/name/proj2.git`
     Running `git fetch --tags --force --update-head-ok 'https://github.com/name/proj2.git' 'refs/heads/*:refs/heads/*'`
error: failed to load source for a dependency on `proj2`

Caused by:
  Unable to update https://github.com/name/proj2.git

Caused by:
  failed to update submodule `proj3`

Caused by:
  invalid url `git@github.com:name/proj3.git`: relative URL without a base

Steps

Create a rust project with an ssh submodule
Add that rust project as a dependency to a new rust project via proj = { git = https://path }
Attempt to run cargo build

Possible Solution(s)

My options to fix this appear to be:

Make proj2 a submodule in proj1. This will work for this particular library but not some of the others my team is working on due to workspaces.
Switch every project over to HTTPS submodules. This is doable, but is currently the most disruptive option for the team as a whole.
Make the fix and push it upstream.

I’m willing to work on this if no one has time, but I need some guidance as to how to best approach it.
Notes
Output of cargo version: cargo 1.36.0 (c4fcfb725 2019-05-15)

I'm not quite sure if that's the bug here, it looks like we're attempting to parse submodule urls as a Url, which isn't working here. It may be the case that we shouldn't be using a Url intermediate data structure at some point. All git fetches I believe should run through the CLI, even submodule ones, if that option is enabled.

That's a good point, its not necessarily the fetch command failing but the flag that enables it should also cause update_submodules to utilize fetch_with_cli. However, update_submodule fails when parsing the Url structure at this line so the fetch function never actually gets called.

Yeah I think we probably just need to pass a str there instead of Url and that should do the trick?


What Webdav are you using?

Hi, I tried to set up your script with cloudme.com Webdav service but got an error RemoteResourceNotFound, after many trials with the webdavclient3 library I came to the conclusion that CloudMe isn't supported by the library. What Webdav service are you using?

I have used and tested Nextcloud's webdav implementation and the one provided by Hetzner's StorageBox product, which both worked as expected. From what I could gather with a quick look, CloudMe seems to offer a standard webdav implementation and should also work.
Could you please check if you have set the correct URL in the config file? This seems to be https://webdav.cloudme.com/your_username. Also, at least with Nextcloud, using 2FA "breaks" webdav login with password (as 2FA can't be used), so an access token is needed.
Also, since it seems unable to actually find the resource, please double check any firewall/DNS/other network configs that might block the script from connecting to the remote.
Other then that, I need to make an account with cloudMe myself and see if I can get more info on the issue, but I won't have much time for that before the weekend, unfortunately.


Policy 'lstm' doesn't work

Hello.
I firstly change the policy in <run_atari_sil.py> by:
parser.add_argument('--policy', help='Policy architecture', choices=['cnn', 'lstm', 'lnlstm'], default='lstm')
Then I run A2C+SIL on Atari games :
python baselines/a2c/run_atari_sil.py --env BreakoutNoFrameskip-v4
I got error:
Logging to /tmp/a2c
2018-12-25 14:46:34.107377: I tensorflow/core/platform/cpu_feature_guard.cc:141] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2
WARNING:tensorflow:From e:\output\python_output\hardrlwithyoutube\self-imitation-learning-master\baselines\common\distributions.py:148: softmax_cross_entropy_with_logits (from tensorflow.python.ops.nn_ops) is deprecated and will be re
moved in a future version.
Instructions for updating:

Future major versions of TensorFlow will allow gradients to flow
into the labels input on backprop by default.

See `tf.nn.softmax_cross_entropy_with_logits_v2`.

Traceback (most recent call last):
  File "E:\Output\Python_output\HardRLWithYoutube\venv_self-imitation-learning-master\lib\site-packages\tensorflow\python\framework\ops.py", line 1628, in _create_c_op
    c_op = c_api.TF_FinishOperation(op_desc)
tensorflow.python.framework.errors_impl.InvalidArgumentError: Dimension size must be evenly divisible by 15 but is 8192 for 'model_2/Reshape_1' (op: 'Reshape') with input shapes: [16,512], [3] and with input tensors computed as partia
l shapes: input[1] = [3,5,?].

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "baselines/a2c/run_atari_sil.py", line 38, in <module>
    main()
  File "baselines/a2c/run_atari_sil.py", line 35, in main
    num_env=16)
  File "baselines/a2c/run_atari_sil.py", line 20, in train
    sil_update=sil_update, sil_beta=sil_beta)
  File "e:\output\python_output\hardrlwithyoutube\self-imitation-learning-master\baselines\a2c\a2c_sil.py", line 161, in learn
    max_grad_norm=max_grad_norm, lr=lr, alpha=alpha, epsilon=epsilon, total_timesteps=total_timesteps, lrschedule=lrschedule, sil_update=sil_update, sil_beta=sil_beta)
  File "e:\output\python_output\hardrlwithyoutube\self-imitation-learning-master\baselines\a2c\a2c_sil.py", line 35, in __init__
    sil_model = policy(sess, ob_space, ac_space, nenvs, nsteps, reuse=True)
  File "e:\output\python_output\hardrlwithyoutube\self-imitation-learning-master\baselines\a2c\policies.py", line 66, in __init__
    xs = batch_to_seq(h, nenv, nsteps)
  File "e:\output\python_output\hardrlwithyoutube\self-imitation-learning-master\baselines\a2c\utils.py", line 74, in batch_to_seq
    h = tf.reshape(h, [nbatch, nsteps, -1])
  File "E:\Output\Python_output\HardRLWithYoutube\venv_self-imitation-learning-master\lib\site-packages\tensorflow\python\ops\gen_array_ops.py", line 7759, in reshape
    "Reshape", tensor=tensor, shape=shape, name=name)
  File "E:\Output\Python_output\HardRLWithYoutube\venv_self-imitation-learning-master\lib\site-packages\tensorflow\python\framework\op_def_library.py", line 787, in _apply_op_helper
    op_def=op_def)
  File "E:\Output\Python_output\HardRLWithYoutube\venv_self-imitation-learning-master\lib\site-packages\tensorflow\python\util\deprecation.py", line 488, in new_func
    return func(*args, **kwargs)
  File "E:\Output\Python_output\HardRLWithYoutube\venv_self-imitation-learning-master\lib\site-packages\tensorflow\python\framework\ops.py", line 3274, in create_op
    op_def=op_def)
  File "E:\Output\Python_output\HardRLWithYoutube\venv_self-imitation-learning-master\lib\site-packages\tensorflow\python\framework\ops.py", line 1792, in __init__
    control_input_ops)
  File "E:\Output\Python_output\HardRLWithYoutube\venv_self-imitation-learning-master\lib\site-packages\tensorflow\python\framework\ops.py", line 1631, in _create_c_op
    raise ValueError(str(e))
ValueError: Dimension size must be evenly divisible by 15 but is 8192 for 'model_2/Reshape_1' (op: 'Reshape') with input shapes: [16,512], [3] and with input tensors computed as partial shapes: input[1] = [3,5,?].

What can I do to fix this? Thank you very much!

I change the num_env in <run_atari_sil.py> from 16 to 15:
train(args.env, num_timesteps=args.num_timesteps, seed=args.seed, policy=args.policy, lrschedule=args.lrschedule, sil_update=args.sil_update, sil_beta=args.sil_beta, num_env=15)
But got another error:
Logging to /tmp/a2c
2018-12-25 14:55:20.343377: I tensorflow/core/platform/cpu_feature_guard.cc:141] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2
WARNING:tensorflow:From e:\output\python_output\hardrlwithyoutube\self-imitation-learning-master\baselines\common\distributions.py:148: softmax_cross_entropy_with_logits (from tensorflow.python.ops.nn_ops) is deprecated and will be re
moved in a future version.
Instructions for updating:

Future major versions of TensorFlow will allow gradients to flow
into the labels input on backprop by default.

See `tf.nn.softmax_cross_entropy_with_logits_v2`.

WARNING:tensorflow:From e:\output\python_output\hardrlwithyoutube\self-imitation-learning-master\baselines\a2c\utils.py:13: calling reduce_max (from tensorflow.python.ops.math_ops) with keep_dims is deprecated and will be removed in a
 future version.
Instructions for updating:
keep_dims is deprecated, use keepdims instead
WARNING:tensorflow:From e:\output\python_output\hardrlwithyoutube\self-imitation-learning-master\baselines\a2c\utils.py:15: calling reduce_sum (from tensorflow.python.ops.math_ops) with keep_dims is deprecated and will be removed in a
 future version.
Instructions for updating:
keep_dims is deprecated, use keepdims instead
Traceback (most recent call last):
  File "baselines/a2c/run_atari_sil.py", line 38, in <module>
    main()
  File "baselines/a2c/run_atari_sil.py", line 35, in main
    num_env=15)
  File "baselines/a2c/run_atari_sil.py", line 20, in train
    sil_update=sil_update, sil_beta=sil_beta)
  File "e:\output\python_output\hardrlwithyoutube\self-imitation-learning-master\baselines\a2c\a2c_sil.py", line 161, in learn
    max_grad_norm=max_grad_norm, lr=lr, alpha=alpha, epsilon=epsilon, total_timesteps=total_timesteps, lrschedule=lrschedule, sil_update=sil_update, sil_beta=sil_beta)
  File "e:\output\python_output\hardrlwithyoutube\self-imitation-learning-master\baselines\a2c\a2c_sil.py", line 69, in __init__
    sil_model.entropy, sil_model.value, sil_model.neg_log_prob,
AttributeError: 'LstmPolicy' object has no attribute 'entropy'

It seems that the policy 'lstm' can not work because the lack of entropy and so on.
What can I do to fix this? Thank you very much!


Develop

Codecov Report

Merging #2 into master will increase coverage by 0.41%.
The diff coverage is 22.58%.

@@            Coverage Diff             @@
##           master       #2      +/-   ##
==========================================
+ Coverage   12.08%   12.50%   +0.41%
==========================================
  Files           5        5
  Lines         389      408      +19
==========================================
+ Hits           47       51       +4
- Misses        342      357      +15

Impacted Files
Coverage Δ

...bViewController/BTabGroup/BTabViewController.swift
1.86% <0.00%> (-0.08%)
:arrow_down:

BTabViewController/BTabGroup/BTabCell.swift
48.33% <87.50%> (+2.03%)
:arrow_up:


ReplaceOrAdd does not declare 'provides :replace_or_add'.

WARN: Class Chef::Provider::ReplaceOrAdd does not declare 'provides :replace_or_add'.
This will no longer work in Chef 13: you must use 'provides' to use the resource's DSL.

If I get a chance I will try and do some work to remove this one.

@damacus did you get a chance to fix it?

...that would be a nope :( been busy rewriting some other stuff. @someara is it worth converting this to a custom resource?

Shit I started going exactly that but forgot about it. I have a branch
somewhere that's like %75 done.
looks
-s
On Tue, May 9, 2017 at 1:14 PM, Dan Webb<EMAIL_ADDRESS>wrote:

...that would be a nope :( been busy rewriting some other stuff. @someara
https://github.com/someara is it worth converting this to a custom
resource?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/someara/line-cookbook/issues/41#issuecomment-300236759,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAENzFasIPoJ6pok2uuo5lvqYRki82qLks5r4J7vgaJpZM4JwjMa
.

Alright dude feel free to kick it over.
BTW if you haven't got time for this anymore I will shamelessly plug sous chefs :P

Ok, how can I help?
Cause right now this cookbook fails with chef v13.
Perhaps @someara can push that branch and I can see if I understand enough to help out.

Right this is now resolved as part of the rewrite @someara can you make a release purty please?


Update label's character count to include space count

Label now counts spaces in get_total_character_count().

Label and RichTextLabel have consistent character count when spaces are included in the text.
Fixes #27896.

@elizaho Is this still desired? If so, this needs to be rebased on the latest master branch. I can see that this PR contains a merge commit, which is not correct, please see this article for more information.

@elizaho Is this still desired? If so, this needs to be rebased on the latest master branch. I can see that this PR contains a merge commit, which is not correct, please see this article for more information.

Superseded by #52712.


Fix bug w/ intro texts AMDPAR; make API safer

This looks like a lot of code, but it's almost exclusively composed of converting position args to keyword args.
The implementation of AMDPARsing for phrases like "the introductory text for
paragraphs (a) and (b)" had a bug stemming from the interface for creating
Paragraph tokens. Until now, these tokens were constructed with a list
parameter, describing the "label" to associate with the token (note that this
label is slightly different than the labels used with trees). The position of
elements within this list gave them special meaning, which leads to the type
of error introduced. This modifies the API to accept keyword arguments as
well, so that authors can express their intent a bit better. It also fixes
some test cases which were using the interface incorrectly (again, no doubt
due to its error-prone interface)
Also standardizes spacing in regparser.grammar.amdpar a bit further.
For 18f/atf-eregs#103

Please ignore the QuantifiedCode warning; I misconfigured it


React native upgrade to 0.41 doesn't build Android release builds_hangs at bundleReleaseJsAndAssets

Please read the following carefully before opening a new issue.
--- Please use this template, and delete everything above this line before submitting your issue ---
Description
Upgraded to react native 0.41 and tried running the Android builds using gradle
Reproduction
Go to Android folder and run ./gradlew assembleRelease
Solution
I don't have any solution for this.

I get the same issue with 0.43.1

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!
If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.

Just having it and I have no idea what can be the issue. Yesterday was working...