[QUESTION] Update record without overwriting unspecified fields

Let's say I have a Person object:
{
    "name": "John",
    "age": 13
}

This object is stored in a LiteDB collection. If I call Update on this object with the following:
{
    "age": 15
}

"name" will be overridden back to null.
Is there any way to bypass this, or will I have to do it manually?

@TheAb03 If you class has an id (as it should, because the resulting document will have an id anyway) and you're willing to use SQL syntax, you could do something like db.Execute($"update collection set age = 15 where _id = {myid}").


pin conda during Python-switch step

even with auto-update-conda disabled, switching Python version (which reinstalls conda) can end up upgrading to the latest conda
Avoid this by adding the conda pinning to that install stage
This should fix the recent failures on CI, which appear to be due to a bug in the recent conda 4.6

Is there repo we build in the CI where we can add a quick check that "conda is indeed the version we expect it to be'? It would have to be a test that has an environment.yml which asks for a different Python version correct?

Good call. Added a check to the Python 3.5 test

Will open a separate issue to track updating to conda 4.6, which is likely waiting for bugfix releases of 4.6

We could use the quant stack repo to test this I think by editing https://github.com/jupyter/repo2docker/blob/8597520e7ad197236006b4246e4ed53516aa3c6d/tests/external/reproductions.repos.yaml#L32 to be verify: jupyter kernelspec list && conda --version | grep 4.5.12

A few of the builds are failing on:
/tmp/install-miniconda.bash: line 66: /srv/conda/envs/kernel/conda-meta/history: No such file or directory

I think. :-/

I made an edit to the path used on L66 of the install script. My guess is that the old path is the correct one and the new one (with extra envs/kernel in it) was a copy pasta from above. If not it seems like we should not have the same line in the if statement above and here but instead have it once.


Can it convert handwritten into text?

No, we have not implemented OCR in this app.

No, we have not implemented OCR in this app.


Network traffic classfication support

This adds simple traffic classification support in TX and RX. This means that when packet is sent or received, it can be placed to different TX or RX queue depending on priority of the packet. This PR tries to keep things simple at this stage so no fancy queueing discipline implementation.

Taking a look "net: core: Add array support to stack info helpers" commit. The description is:

Allow caller to create stack of arrays using NET_STACK_ARRAY_DEFINE() macro.

Nice. But why would one want to create "stack of arrays" using NET_STACK_ARRAY_DEFINE() macro? What usecase does it address? Especially that it's defined as:
+#define NET_STACK_ARRAY_DEFINE(pretty_name, name, orig, size, nmemb)	\
 +	K_THREAD_STACK_ARRAY_DEFINE(name, nmemb, size)

I.e. just renames existing functionality, duplicating macros.
The whole terminology is rather ambiguous too. Reading "stack of arrays", I can imagine anything from an abstract stack (i.e. LIFO) data structure which allows to push similarly abstract array objects on it, to a specialized IP stack which deals with networking arrays (no idea what the latter would be, but if we have storage arrays, we've got to have networking arrays too, right?). I could even imagine there's a typo and it's "array of stacks", but given the overall confusion, I wouldn't be sure.

Can this be marked with explicit "Milestone" setting please, to allow for better resource allocation for the 1.11 release preparation as happening now? Thanks.

Can this be marked with explicit "Milestone" setting please, to allow for better resource allocation for the 1.11 release preparation as happening now? Thanks.

This is definitely not for 1.11 but I do not think you really need to care about what release this PR is targeted at. Anas will assign it a milestone according to release plan.

I.e. just renames existing functionality, duplicating macros.
No exactly. If you look more carefully the code, the macro is adding some extra stuff if net-shell is enabled. Then "net stacks" command will print more information about the created work queue stacks.

Right, and my suggestion was to add that information to the commit message. Even "it's done similarly to other functionality wrapped by net subsystem (e.g. <example1>, <example2>)" would give good insight that at least it's consistent with existing state of affairs, and "Then "net stacks" command will print more information" is even more useful.
(Otherwise yeah, I love these Monday's morning reviews (like when I posted that), it allows to emulate newcomer's perceptions more or less faithfully ;-) ).

This is definitely not for 1.11 but I do not think you really need to care about what release this PR is targeted at. Anas will assign it a milestone according to release plan.

Well, I don't know, https://github.com/zephyrproject-rtos/zephyr/pull/5721 wasn't marked as 1.11, contained quite big refactors and new features, and was merged after the feature freeze date, according to https://github.com/zephyrproject-rtos/zephyr/wiki/Program-Management (there was no announcement on the mailing list, but apparently that would mean that the dates in the doc prevail). So, one may wonder about the plans re: this PR. I'm sure that Anas does the right thing, but as we have technical features to improve the visibility, would be nice to use them.

Updated according to comments.

Codecov Report

Merging #6076 into master will decrease coverage by 0.47%.
The diff coverage is 44.44%.

@@            Coverage Diff             @@
##           master    #6076      +/-   ##
==========================================
- Coverage   52.84%   52.37%   -0.48%
==========================================
  Files         412      410       -2
  Lines       40300    39662     -638
  Branches     7804     7708      -96
==========================================
- Hits        21298    20773     -525
+ Misses      15784    15764      -20
+ Partials     3218     3125      -93

Impacted Files
Coverage Δ

include/net/net_context.h
95.23% <ø> (+2.21%)
:arrow_up:

include/net/net_ip.h
59.85% <ø> (-2.65%)
:arrow_down:

subsys/net/ip/net_stats.h
100% <ø> (ø)
:arrow_up:

subsys/net/ip/net_private.h
61.53% <ø> (+25.82%)
:arrow_up:

include/net/ethernet.h
0% <ø> (-26.67%)
:arrow_down:

subsys/net/ip/net_context.c
58.92% <0%> (-1.38%)
:arrow_down:

subsys/net/lib/app/server.c
25.25% <0%> (ø)
:arrow_up:

subsys/net/ip/icmpv4.c
42.95% <0%> (-0.89%)
:arrow_down:

subsys/net/ip/l2/ieee802154/ieee802154.c
48.14% <0%> (ø)
:arrow_up:

subsys/net/ip/tcp.c
43.04% <0%> (ø)
:arrow_up:

... and 36 more

Continue to review full report at Codecov.

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

Rebased because of changes in master.

Fixing merge conflicts and sanitycheck errors.

Fixing again sanity issues.

VLAN patches updated.

New version. I moved this set to be applied before VLAN PR because of weird errors with tx_queue handling.

Fixing rebase error.

Added unit test.

Added more test cases.

Documentation fixes

Added RX classification support.
Added unit tests for RX.

Rebase against master. Fixed issued reported by sanitycheck.

Rebase against master.

Rebase against master. Reshuffled the patch ordering. now this one depends on checksum offloading PR #6601

sanity fixes

more sanity fixes

rebase against master

Rebase against master. Fixed various sanity issues and couple of patches removed from this PR as they were no longer needed.

New version according to comments. Also moved traffic class functionality to net_tc.c although there is not much stuff there but it is probably more easier to review now.

@nashif could you force-apply this one as sanity is complaining non-issue and I cannot merge this?


Vertical Slider & Icon position

This is really cool thanks, very similar to the iPhone volume & brightness UI as well
Can you have a vertical option? I've tried putting it in a Transform.rotate but it's not behaving properly. Also, then would need to rotate all widgets within and figure out how to place things above and below the bar. And then it looks like you ahve a horizontalDrag which would need to be verticalDrag.
Also, possible to have option to place the icons/text INSIDE of the slider? This would help with a clean minimalist UI

Thank you for the interest 👍 I'm currently working on fixing the fact that the size transition moves adjacent UI elements which is not desired behavior. After that I'll probably first implement alternate locations for the icons and then look into a vertical slider.

very nice :) i look forward to seeing this mature into a solid slider

@jtkeyva I just upload version 0.1.0 that adds the ability to choose the icon location (inline and below for now. I'm working on figuring out how I would wanna do inside). Also fixes the size changing problem. I'll be working on the vertical slider next probably

@jtkeyva Added inside icon option! v0.1.1

very nice! will give it a try and provide feedback soon :)

Looks soooo nice, I am so looking forward for a the vertical orientation of the slider. Any ETA?


Cannot reply on my kata

I have a kata named "subtract the sum". Some people made issues. I want to resolve the issue and reply them but my comment never get published. I tried different browsers and devices. It should be a server side problem. The page wants to be loaded again but my comment never show up there.
Here is a link to the my kata

Actually I cannot reply to ThomasJazz there. He made two issues there.

I think I've encountered a similar problem here: https://github.com/Codewars/codewars.com/issues/409

Thanks @Nivrad00 for the report. That will be very helpful in tracking down the issue. I have been working on some issues related to this. I think a recent forced database upgrade caused both this and a few other issues to start happening. I'm working on a fix.
@DonaldKellett I do believe this issues are related. In some rare cases a few comments may have been lost because of it (or at least not saved when they seemed to be)

Comment issues should be resolved now. There is a very low level ORM issue that was causing issues when updating data that I pushed a workaround for. Some content may be lost if it was created over the last week. The majority of comments should work, just a small percentage of edited comments caused the data issues after the fact.
Leaving open for the time being in-case issues remain.

I take that back, removing comments still causes issues - I will wait to close this bug until the official (non-workaround) fix is found.

Official fix has been deployed


Let plugins modify the body HTML

Addresses https://github.com/denoland/fresh/issues/1701.

superseeded by #2022


Question regarding multipliers

Guys, if I open a 2nd position 2 weeks after my first one with the same token is it going to keep my first multiplier or it is going to start from x1?
Thanks in advance

please ask such questions in the dedicated channels:
https://t.me/bancor
https://discord.com/invite/EHK8wHbgau
https://t.me/BancorDevelopers


The *reduce extension methods don't return the inner function

@armantorkzaban Is the description somewhat understandable?

I solved it while doing https://github.com/dartclub/turf_dart/issues/78.
It can be closed.


SPARKC-161: RDD coalesce() pushdown to cassandra

The first commit is a sketch of the possible implementation. Custom partitioner is not supported yet.
I use to for my performance tests

Why b1.2? It is a new feature.

Commit description has a typo: "scatch"


(fix) FileInput max upload size for all files

Summary | Résumé
1-3 sentence description of the changed you're proposing.
Please include the GitHub issue number or relevant acceptance criteria.
To specify that this PR closes a particular issue you can use the following format
to reference and issue closes #[issue number]. You can use any number of keywords to link
an issue to a PR. Please see the following section
of GitHub's documentation.
For any UI changes please include screenshots at different breakpoints. It would also be helpful to include a
before and after comparison for each change i.e.

Before
After

Insert Image showing before the change was made
Insert Image showing after a change was made

Test instructions | Instructions pour tester la modification
Sequential steps (1., 2., 3., ...) that describe how to test this change. You should include
anything outside the README that will help the developer access your changes and be able to test
them such as any environmental setup steps and/or any time-based elements that this requires.
This will help a developer test things out without too much detective work.
Unresolved questions / Out of scope | Questions non résolues ou hors sujet
Are there any related issues or tangent features you consider out of scope for
this issue that could be addressed in the future? If so please create issues and provide
links in this section
Pull Request Checklist
Please complete the following items in the checklist before you request a review:

[ ] Have you completely tested the functionality of change introduced in this PR? Is the PR solving the problem it's meant to solve within the scope of the related issue?
[ ] The PR does not introduce any new issues such as failed tests, console warnings or new bugs.
[ ] If this PR adds a package have you ensured its licensed correctly and does not add additional security issues?
[ ] Is the code clean, readable and maintainable? Is it easy to understand and comprehend.
[ ] Does your code have adequate comprehensible comments? Do new functions have docstrings?
[ ] Have you modified the change log and updated any relevant documentation?
[ ] Is there adequate test coverage? Both unit tests and end-to-end tests where applicable?
[ ] If your PR is touching any UI is it accessible? Have you tested it with a screen reader? Have you tested it with automated testing tools such as axe?

Proposed default hint text for file upload:

EN: Files must not exceed 6 MB in total.
FR: Les fichiers ne doivent pas dépasser 6 Mo au total.

Proposed default error message text for file upload:

EN: Files added to the form exceed the total size limit. Upload smaller files for a maximum of 6 MB.
FR: Les fichiers ajoutés au formulaire dépassent la limite de taille totale. Téléversez des fichiers plus petit pour un maximum de 6 Mo.

Proposed link for error message:

Go to first file uploaded, assuming we're solving for a one-page context first.
Revisit later when we make file uploads an available feature for all clients.


feat(orchestrator): verify if auto-generated openapi files are up-to-date

The command yarn --cwd plugins/orchestrator-common openapi:generate generates
./src/auto-generated/api/models/schema.ts and ./src/auto-generated/api/definition.ts from openapi.yaml.
These files can't be edit manually.
Add a mechanism to detect unwanted changes.

Add plugins/orchestrator-common/src/auto-generated/.METADATA.sha1
This metadada file contains the SHA1 of openapi.yaml and genered files
Before the build, check if current SHA1 differs from  SHA1 stored in .METADATA.sha1. If they are different, the build fails.

i suggest this command will not be used by local build in the developer environment.

@jkilzi please review this PR when you have a chance.

LGTM
On Mon, 11 Mar 2024, 10:32 Gloria Ciavarrini, @.***>
wrote:

@.**** commented on this pull request.
In plugins/orchestrator-common/scripts/openapi.sh
https://github.com/janus-idp/backstage-plugins/pull/1323#discussion_r1519313810
:

\ No newline at end of file
+openapi_generate() {

npx openapi-typescript ${OPENAPI_SPEC_FILE} -o ${SCHEMA_FILE}
npx openapi-generator-cli generate -g asciidoc -i ./src/openapi/openapi.yaml -o ./src/auto-generated/docs/index.adoc
npx yaml2json -f ${OPENAPI_SPEC_FILE}

echo '// GENERATED FILE. DO NOT EDIT.' > ${DEFINITION_FILE}
echo 'const OPENAPI = `' >> ${DEFINITION_FILE}
cat ./src/openapi/openapi.json >> ${DEFINITION_FILE}
echo '`' >> ${DEFINITION_FILE}
echo "export const openApiDocument = JSON.parse(OPENAPI);" >> ${DEFINITION_FILE}

rm ./src/openapi/openapi.json
yarn openapi:prettier:fix

They will be formatted during the commit anyway but explicitly invoking
the formatting right after the generation, ensures that they meet the
formatting requirements. Otherwise, we'll see local changes after each
re-generation.
In addition, the calculated hash will be consistent too.
IMO the benefits are greater than the disadvantages.
WDYT?
—
Reply to this email directly, view it on GitHub
https://github.com/janus-idp/backstage-plugins/pull/1323#discussion_r1519313810,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASLQ3VIPO3IWOUR5AL6YAOTYXVTZXAVCNFSM6AAAAABENCJUZWVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTSMRXGE4DMMZZHA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Friendly hovertext for TimeAgo

Closes #1331.

I'm guessing the date parsing is happening clientside, which is good for timezones (it's 10:30 in the UK as i write this):


delete_message is not working, issue with JSON

Cannot delete messages, neither as staff, nor as non-staff, results in exception. Issue can be because duplicate key.

Added to the bug list, will be fixed on the next patch branch, will mention the issue

issue should be fixed with #37 and is available on the latest dev build


Schedule Columns

The Schedule can be simplified as it's currently formatted for a 2 day event but this is only an 8 hour one. But there will be 3 things happening at the same time. Event 1, Event 2 and a Sponsor Event. These all need to be reflected in the table.

Fixed with my PR / Schedule branch.


Jest-circus leaks memory when allocating a buffer in a test

🐛 Bug Report
When allocating a buffer in a test, jest leaks memory when using the jest-circus runner, but does not when using the default runner.
To Reproduce

clone https://github.com/n-e/jest-circus-leak
run node ./node_modules/.bin/jest --logHeapUsage --runInBand --verbose
the heap size increases and node eventually crashes with an OOM error

If testRunner is commented in jest.config.js, the heap size doesn't increase.
Expected behavior
The heap size should stay small
Link to repl or repo (highly encouraged)
https://github.com/n-e/jest-circus-leak
envinfo

npx: installed 1 in 1.236s

  System:
    OS: macOS 10.15.1
    CPU: (8) x64 Intel(R) Core(TM) i5-8259U CPU @ 2.30GHz
  Binaries:
    Node: 12.13.0 - ~/.nvm/versions/node/v12.13.0/bin/node
    Yarn: 1.17.3 - /opt/local/bin/yarn
    npm: 6.12.0 - ~/.nvm/versions/node/v12.13.0/bin/npm
  npmPackages:
    jest: ^24.9.0 => 24.9.0

I think it duplicated with https://github.com/facebook/jest/issues/8816 and possible cause for managing the state of jest-circus.

Duplicate of #8816. Thanks @lamhieu-vk


Flutter web support for firebase_storage plugin

Hi,
firebase_storage plugin doesn't seem to work on Flutter Web. Am I missing something or this plugin is not yet supported for web ? If so, could you point me to workaround to make it work on web ?
Thanks,
Priyanka

as far as I know flutter for web does not have a plugins management system yet, so generally you cannot use plugins with flutter for web yet.
in general,  flutter for web is still at tech view so you shouldn't use it for production.
but if you really will, it's possible to use js libraries temporarily until they'll add plugins. so you can use the firebase js sdk storage package.
Good luck and happy coding!

Plugins are not supported yet in flutter web, you should use a wrapper for the js library instead.
in general, flutter web haven't reached alpha yet, and is currently for tech view, it is not recommended to use it for production.

Hi @ptyagicodecamp
@NoamDev  is right,
There's a dart web version you might want to consider,
you can also take a look to this solution.
A better solution is currently work  in progress.
Closing, as this isn't an issue with Flutter itself,
if you disagree please write in the comments and I will reopen it
Thank you

@iapicca suggestion helped me enable storage on the web for the time being.
Here is a gist of what I did to enable uploading from the web https://gist.github.com/ialhashim/d0c867daa2dc02cf4e178374abd0ca49
Its a hack for now, I am sure the flutter community will develop an official package soon.


OTel: Document disabling reactor plugin and verify that manual context propagation works with agent

We need to document (and may be even recommend) disabling reactor context propagation due to perf overhead and polluted stack traces.
We also need to check if explicit context propagation works with agent - I believe it does not due to shading in the agent.

Related: https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/11042


Update oci-java-sdk-objectstorage to 2.4.0

Updates com.oracle.oci.sdk:oci-java-sdk-objectstorage from 2.3.2 to 2.4.0.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.oracle.oci.sdk", artifactId = "oci-java-sdk-objectstorage" } ]

labels: library-update, semver-minor

Superseded by #484.


Add rate and framerate properties to VideoStream (fixes: #1005)

Fixes the regression introduced by #910
This PR fixes the issue by adding properties that point directly to the underlying AVStream's avg_frame_rate. It doesn't set the rate on the new codec_context, but that doesn't appear to be necessary.

I'm having another look at this, and I'm really confused. We already have Stream.average_rate, which does the exact same thing but with a more explicit name. Why do we need two additional accessors?

I see your point and that makes sense. We should just probably remove these accessors, but we should be explicit that it is a breaking change.

I guess a follow on question is what to do with AudioStream.
The actual rate field for an audio stream is stored in sample_rate of the AVCodecParameters. We should probably get rid of the rate passthrough and enforce sample_rate since it is a more explicit name as well.

Closing in favour of #1036


Fix read softgz

While testing my changes to dataset code, I saw that sc.datasets.burczynski06() raised the error:
ValueError: `X` needs to be of one of ndarray, MaskedArray, spmatrix, ZarrArray, ZappyArray, not <class 'dict'>.

But it had a pretty easy fix.

Thanks! 🙂


Cart Menu

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes:  #747

Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

Checklist:

[x] I have made this from my own
[ ] I have taken help from some online resourses
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK

@DragonUncaged make it responsive

@DragonUncaged make it responsive

Done!!

@DragonUncaged correct the link in style_links.json file.

@DragonUncaged correct the link in style_links.json file.

Done!!


Feature request: vite_picture_tag

Is your feature request related to a problem? Please describe.
Rails introduced a picture_tag helper earlier this year. It is on the main branch (not yet released) and presumably will be part of Rails 7.1.
Describe the solution you'd like
I'd like to see a vite_picture_tag wrapper, perhaps with an implementation like this:
def vite_picture_tag(*sources, &block)
  sources.flatten!
  options = sources.extract_options!
  vite_sources = sources.map { |src| vite_asset_path(src) }

  # Delegate to ActionView::Helpers::AssetTagHelper#picture_tag
  picture_tag(*vite_sources, options, &block)
end

Describe alternatives you've considered
The tag helper is syntax sugar; <picture> tags can of course still be created manually without too much effort:
tag.picture do
  tag.source srcset: vite_asset_path("images/one.png")
  tag.source srcset: vite_asset_path("images/two.png")
  vite_image_tag("images/two.png", alt: "example")
end

Versus:
vite_picture_tag("images/one.png", "images/two.png", image: {alt: "example"})

Additional context
I'd be happy to contribute a PR, but I am wondering: should I wait until Rails 7.1 is released?

Hi Matt!
Sounds reasonable to add vite_picture_tag once picture_tag is released.
To avoid users from attempting to use it in older versions of Rails it might be preferable to do something like:
if defined?(Rails) && Rails.gem_version > Gem::Version.new("7.1")
  def vite_picture_tag(*sources, &block)


Custom 3D Tileset no shadows / incorrect lighting

Hey! I am having issues with a custom 3D tileset.
My tileset seems to be unaffected by the engine's lighting/shading/shadowing.

In the background, you can see the default Cesium terrain which is shaded correctly and in theforeground the custom tileset which is far too bright. I am using CesiumSunSky and the time is set to evening.
I tested the Boston & Denver tilesets from Cesium Ion with the same settings and world setup. Those get shaded correctly and cast proper shadows.
Are there any known issues with shadows/lighting in Cesium UE or is there anything I could have missed while creating the tileset?

Does your tileset's glTF material perhaps have an emissive component?  It's hard to say without seeing the tileset. Please followup on the community forum because this is not a bug report or feature request for Cesium for Unreal.


1.19.2 Backport

Took a quick look at CurseForge, didn't see any mods potentially using the removed / renamed experience methods
(And neither did Gateways or NeuralNetwork (at least not on the default branch))
Commits

72e5bc48
96fe830d
052ea2e7

This probably needs to also include the changes to RandomAttributeModifier in 8.5.6 and 8.5.8, and may need to include the constant codecs introduced in 8.5.4

Should ChancedEffectInstance stay in Apotheosis?

Probably.  Can't tell if people are using it or not.


Add conversion script from PLY to NDT

Proposed changes
Closes #348.
Type of change

[ ] 🐛 Bugfix (change which fixes an issue)
[x] 🚀 Feature (change which adds functionality)
[ ] 📚 Documentation (change which fixes or extends documentation)

Checklist

[x] Lint and unit tests (if any) pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (if appropriate)
[x] All commits have been signed for DCO

Additional comments
Planning to add tests before merging. But this already seems to be working well.

Looks great!
Meta question:
Did you consider using a third party python module for loading in the plys?
I feel like even though this looks sane, we won't cover all the combinations in the tests and might aswell rely on a trusted module.
Something like https://github.com/dranjan/python-plyfile comes to mind.
Not blocking at all

Did you consider using a third party python module for loading in the plys?

+1000 to this.

Did you consider using a third party python module for loading in the plys?

Where is the fun in that? :disappointed:
Haha, comments addressed, I think.


juju: 3.3.5 -> 3.5.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/juju/juju/releases.
meta.description for juju is: Open source modelling tool for operating software in the cloud
meta.homepage for juju is: https://juju.is
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.5.0 with grep in /nix/store/2zncsmmdffmsq23xri0vff5n88xv7f6a-juju-3.5.0
found 3.5.0 in filename of file in /nix/store/2zncsmmdffmsq23xri0vff5n88xv7f6a-juju-3.5.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

juju

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/2zncsmmdffmsq23xri0vff5n88xv7f6a-juju-3.5.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A juju https://github.com/r-ryantm/nixpkgs/archive/10a7ecf1943d076296484499ac02bef5759277a7.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/10a7ecf1943d076296484499ac02bef5759277a7#juju

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/2zncsmmdffmsq23xri0vff5n88xv7f6a-juju-3.5.0
ls -la /nix/store/2zncsmmdffmsq23xri0vff5n88xv7f6a-juju-3.5.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

juju

Maintainer pings
cc @VertexA115 for testing.

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

1 package built:

juju


[BUG] Login button not working

Description
i am using WHISPER but i can't login.
Screenshots

Additional information
No response
🥦 Browser
Google Chrome
👀 Have you checked if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

[X] I have read and understood the rules in the Contributing Guidelines

Are you willing to work on this issue ?
Yes I am willing to submit a PR!

right the login button doesn't work atm, we plan to convert it to use a typical login form

Hi @Dun-sin Please assign this issue to me . will solve it in a day

login button working


TS.Net.Engine: Multidevice commandline arguments

This PR enables commandline arguments, specifically -i to select one of mulitple ThunderScopes on a host (Windows only atm, due to XDMA device detection not being implemented under Linux yet), -cport and -dport to set custom listener ports for the control and data plane servers, and -rev to select the PLL configuration dynamically instead of using build time preprocessor directives to switch between them.

Thanks for the contribution!


Fix dropdown to avoid flash

Actually, I reviewed on a server and it's only local that this happens


Validate custom emoji name

[Documentation] says:

Emoji names can only contain a-z, 0-9, dashes (-), and spaces.

However, it is possible to upload custom emoji with "illegal" character (e.g. .) in the name both via UI and via API. It will even show up in autocomplete when editing messages:

But it will not be rendered:

UI and API should validate emoji names and reject invalid ones.

@zulipbot claim

@zulipbot claim

It seems like the validator written to check the emoji name indeed allows "periods (.)" in the emoji name, here it is https://github.com/zulip/zulip/blob/main/zerver/lib/emoji.py#L112,
Either it is a mistake in the validator code or maybe we want to improve the rendering of emoji's such that it allows period!

@zulipbot add "area: emoji" "bug" "help wanted"

@zulipbot claim


Make ./gradlew executable

Useful for building on Unix/Unix-based systems like Linux and macOS.

What exactly did you do? git is not showing any actual changes on the file..

I just changed the file permissions to set ./gradlew as an executable on systems that support it, but the contents of the file itself are unmodified. This will have no effect on Windows since it does not support Unix file permissions. There's some more info here: https://en.wikipedia.org/wiki/File-system_permissions
Also, the changes can be seen in GitHub as

or in CLI git as
$ git diff f0b1531 5bf14c3
diff --git a/gradlew b/gradlew
old mode 100644
new mode 100755

Ah, TIL! I'll merge when I get to my pc


Refactor integration code with 0-stor

Currently the code is so messy and not generic enough, and really hard to maintain. Lots of code parts are done in multiple places.
We need to use the current experience we have atm to re implement the integration cleanly.
https://docs.google.com/document/d/1WAs1MOlaZ8Ed32FrtQZ_ViEsps9V8RnIGqzFADSxFAw/

Object Layer:

[ ] GetBucketInfo
[ ] DeleteBucket
[ ] ListBuckets
[ ] MakeBucketWithLocation
[ ] GetBucketPolicy
[ ] SetBucketPolicy
[ ] DeleteBucketPolicy
[ ] DeleteObject
[ ] CopyObject
[ ] GetObject
[ ] ListObjects
[ ] ListObjectsV2
[ ] PutObject
[ ] NewMultipartUpload
[ ] PutObjectPart
[ ] CopyObjectPart
[ ] CompleteMultipartUpload
[ ] AbortMultipartUpload
[ ] ListMultipartUploads
[ ] ListObjectParts
[ ] Shutdown
[ ] StorageInfo

@muhamadazmy @serboctor I just read the document regarding this refactor work. Looks good, but I have one question regarding migration to this new implementation. Cause it seems the metadata organization is not going to be compatible with the current one.
Can we make sure to open an issue about migration tool that will need to be created in order to be able to update existing archive to this new version?

Currently working on the PR comments.
I will resume writing tests afterwards.

I am still verifying minio mint tests against my branch and fixing Azmy's newly communicated PR comments.

Mint tests all pass now and all PR comments are done. I resumed writing tests.

Finished object gateway tests and zerostor client tests.

Rebased the master from minio's master and rebased my branch from master. They removed vendoring and all the dependencies are messed up. I fixed most things and I am trying to reach a green build again.

I fixed some tests which had race conditions. The build is still not green because of coverage. I'll pause working on it and resume writing tests when I am done with other more critical tasks.

I fixed the make coverage and now the build is green. I still need to write more tests but I'll pause that for now until I am done with more critical tasks.


load() not working

GestureLibraries is not being loaded the line gLibrary.load() is throwing error that index is 0 and size is 0. in HomePage.kt file.

Okay now I got the issue, the file gesture.txt had some issue in encoding and thus was not getting detected. So I made new one and now it works like a charm.


Sticky position with horizontal true

Is your feature request related to a problem? Please describe.
I would like to have a horizontal list with first item sticky.
Describe the solution you'd like
I would like an example how to implement it because when I tried edit this example with prop horizontal=true it does not work.

Hi, I'm not sure this is your intended markup, but you can make horizontal version of the example like this:
https://github.com/inokawa/virtua/assets/48897392/d76a06a5-8c56-40bd-9894-62048fa5ea73
<VList style={{ width: "100vw", height: 160 }} horizontal>
  {Array.from({ length: 100 }).map((_, i) => {
    return (
      <div
        key={i}
        style={{
          display: "flex",
          flexDirection: "row",
          borderBottom: "solid 1px #ccc",
        }}
      >
        {Array.from({ length: 10 }).map((_, j) => {
          const isGroupTop = j === 0;
          return (
            <div
              key={j}
              style={{
                width: 120,
                background: "#fff",
                ...(isGroupTop && {
                  left: 0,
                  width: 60,
                  position: "sticky",
                  borderRight: "solid 1px #ccc",
                }),
              }}
            >
              {isGroupTop ? i : `${i} - ${j}`}
            </div>
          );
        })}
      </div>
    );
  })}
</VList>;


Set Overseerr as default search option in search bar

Description
I love being able to request a movie/tv show and see it show up in the torrents module. However typing !os everytime is not user friendly for my family. Can I have the search bar automatically search Overseerr?
Priority
Medium (Would be very useful)

Hello @mitchando96 ,
@ajnart is already working on an updated version of the search box which is easier to use.
However, we're not quite sure when it will be ready to be released.

Hey @mitchando96 yeah I'm reworking the search feature.
Would you say your issue is more related to speed or memory.
Is the issue that it takes time to write !os or that it is hard to memorize for other people ?
The UI I'm making allows for a clicking selection of the search engine or using the old shortcuts
(It shows name / description and an icon explaining what every option does)
Would that satisfy your needs?
In the meantime if people are not going to access your server for anything else than request media you could set your default search engine to directly use your overseerr instance (overseerr.website.com/search or something similar )

The new update is great! I like the new search bar, but would really love the simple option to choose one of the search modes as a default one (for example overseer). It would make things so much easier for my family (they sometimes get confused while using the ! commands or the new dropdown menu).

Hi @ajnart, I would say it’s both a speed and memory issue, having to type !os and ask my family to memorise it means it goes unused. I haven’t tried the new search yet, but I agree with HoreaM that a default search option would be fantastic. I could set it up to be a mini Overseeer with current download view, no logins required 🥳

The new update is great! I like the new search bar, but would really love the simple option to choose one of the search modes as a default one (for example overseer). It would make things so much easier for my family (they sometimes get confused while using the ! commands or the new dropdown menu).

Okay thank you for the feedback ! I'll open a new issue


dpc treatment

When performing a vectored interrupt its first fetch will be a fetch of a pointer value from some address A. I think it should be possible to set a breakpoint on that address A. Let's here assume that the pointer fetch itself is treated as an instruction fetch (whether it is an instruction or data fetch is another ongoing discussion). In that case an instruction breakpoint with before timing should lead to dpc containing address A in my opinion. A dret instruction can not just perform pc = dpc (as there is no instruction at address A, but a pointer value). I would therefore think that the CLIC spec  needs to add a description of required dret behavior similar to the change in behavior for xret instructions as copied here from section 5.4 (where 'x' refers to privilege, not debug):
if (xcause.inhv) //xcause here refers to the cause CSR of the previous privilege
mode
pc := M[xepc] //xepc here refers to the current privilege mode
else
pc := xepc

I think we should then also add a section similar to section '5.6. Changes to xepc CSRs' to describe the 'Changes to dpc CSR' specifically also noting that the location pointed to by dpc might contain a pointer as opposed to an instruction.
Alternatively it could be forbidden to put breakpoints in the vector table, but that would be a quite awkward restriction.

I agree with the suggestion that it should be permissible to set a trigger on a table load. The CLIC spec states that the table load is treated as a load, not an instruction fetch. This is important, as it affects interpretation of the memory access for PMA and PMP checks, caching, etc. So a trigger on the table load would need to be a data trigger (eg, select = 1). In that case, dpc can be set to the table load address, analogously to xepc being set on a trap during table load. In fact, this applies to any entry to debug mode during table load (eg, haltreq). The behaviour of dret also needs to be updated analogously to xret, to check dcsr.prv to determine the privilege level being returned to, and if xinhv for that level is 1, use dpc as the address for resuming the table load instead of the pc to transfer to.

Hi @pashenden , just want to point out that the CLIC spec was recently updated to align with the Zc JT/JALT and the table load is no longer treated as a load.
here is the revision history entry: 04/26/2022  issue #191 - hw vector fetch permission changed to implicit read with execute permission required.
For permissions-checking purposes, the memory access to retrieve the function pointer for vectoring is an implicit read at the interrupt level of the interrupt handler, and requires execute permission; read permission is irrelevant. If there is an access exception on the table fetch, xepc is written with the faulting address. xtval is either set to zero or written with the faulting address.
Does this affect your recent comment?

Thanks @dansmathers. So that means a trigger would have to be an execute trigger (mcontrol.execute = 1).

From TG meeting 2022/5/10:  Agreed that it would be useful to set a breakpoint entry on table address, but might not be practical to implement in all systems depending on fetch microarchitecture (do breakpoints check PC values or memory addresses on instruction port?).  However, dret should be defined to do the right thing if inhv is set regardless.
If we wanted to avoid optionality then either all systems must allow breakpoints to take effect on table entries, or all systems must ignore them.   Either fixed choice involves additional hardware complexity for some set of plausible hardware microarchitectures, so probably best to make an option.
If this is an option, then debug software would determine via discovery mechanism.  Option would need to be named for ISA infrastructure.
This decision should align with code-size group decision for table-jump instructions, as feature is very similar.
We have decided to make table fetch require instruction-fetch permissions, and consider implicit vector table reads as instruction fetches, so watchpoints are not active for table-fetch operations.  However, watchpoints can be used to detect explicit loads and stores to the table.

TG meeting 2022/7/19: To condense the previous comment:
For implicit hardware table reads, whether breakpoints trap on the table read is left as an implementation option.   For explicit loads used in software vectoring, watchpoints operate as normal for any load.

closed by pull #261


fix Message._update

Edited field on MessageUpdate events is a string in iso8601 format not a timestamp.
Also when using the /global command a MessageUpdate event without a edited field is received
Please make sure to check the following tasks before opening and submitting a PR

[X] I understand and have followed the contribution guide
[X] I have tested my changes locally and they are working as intended
[X] These changes do not have any notable side effects on other Revolt projects

You need to handle it being both an integer and a string, revolt can send either of them, im still trying to get to the bottom of why this is but for now both cases should be handled.

When msgpack is installed it will be a int otherwise a str.
https://github.com/lantern-chat/iso8601-timestamp
When serializing to non-human-readable formats, such as binary formats, the Timestamp will be written as an i64 representing milliseconds since the Unix Epoch. This way it only uses 8 bytes instead of 24.


Examples of bypassing Login Auth URLS

Are there any examples (hopefully none that I missed) that show how to bypass auth via the Curl command?
I was redirected here as an option to download/automate Jamf Connect but I cant find anything on the forums on this GH that shows how its possible since theres a login token (or something of that nature) that is appended to the download URL

If you mean in a server that will append this key in order to authorize the download, then it's not possible. Only the server can create that key.
If you want to post a login before downloading, then that can be done, but I don't think we have any examples.

thanks reasonable and i figured as much - someone on jamfnation has it working somehow but hasnt shared how so I figured id post here.
thank you!


download all delegated roles when doing downloadTargets

Early preview for @cyli. Working on tests right now.
Signed-off-by: David Lawrence<EMAIL_ADDRESS>(github: endophage)

Would be lovely to have some tests for ListTargets to make sure that targets in the higher priority roles displayed instead of the ones in the lower priority roles with the same name.

@cyli yep, working on those now.

LGTM pending CI!

LGTM after CI!


Combining mark not showing correctly

First of all, I would like to thank you for the useful software.  I have a bug namely Combining mark not showing correctly.

Glad you like the software. Thanks for pointing out the bug. I'll look into it.

Is there a new update?


Implement codefix SA1100 DoNotPrefixCallsWithBaseUnlessLocalImplementationExists

Fixes #334.

Allright, thank you for your input. I will fix this :)

I corrected the codefix. Additionally I did a small cleanup of tests's code.

I enabled SA1100 by default as well in 9ddbae3676e71b85d67032cf68c814af305372b3.

Cool :)


add option to create relative links to module

As discussed in #13, implementation for relative module linking in workspace.
Tests are passing.
To test it: npm-workspace install -l

Hello :) Could you please give me some feedback about this PR?
Thanks

Hi, sorry, I don't know why but I was sure I already replied to this one :P, my fault.
Could you please add a test case for the PR? The code looks good, just want to be sure to have a small test at least for regression.


Upgrade Project Reactor 2022.0.9 -> 2022.0.10

This PR contains the following updates:

Package
Type
Update
Change

Project Reactor (source)
import
patch
2022.0.9 -> 2022.0.10

Release Notes

reactor/reactor (Project Reactor)
v2022.0.10
Compare Source
2022.0.10 release train is made of:
reactor-core 3.5.9
reactor-netty 1.1.10
reactor-kafka 1.3.20
These artifacts didn't have any changes:
reactor-pool 1.0.1
reactor-addons 3.5.1
reactor-kotlin-extensions 1.2.2

[ ] If you want to rebase/retry this PR, check this box

Suggested commit message:
Upgrade Project Reactor 2022.0.9 -> 2022.0.10

See:
- https://github.com/reactor/reactor/releases/tag/2022.0.10
- https://github.com/reactor/reactor/compare/2022.0.9...2022.0.10


Last.fm integration not working on El Capitan

When trying to authorize my Last.fm account I just get a message: Unable to login to Last.fm.
I use version v1.4.1.

It seems that this is a issue only on the newest version. With v.1.4.0 it works.

Same here

(Y) Same
@ameraljovic Which 1.4.0 version are you using?  The official binary has the issue with the white box in the bottom left and all the songs skipping.

@chrismou Yes, the official binary v1.4.0.

+1 for broken on 1.4.1, El Capitan.

Still broken on 1.4.1 and the 1.4.0 patched

Yeah, I can't get it working on any version. 1.4.0 official I get the white box of death, 1.4.0 temp and 1.4.1 the music plays but it won't scrobble. I've reverted back to the web player for now.
I may have a go at getting it running in Xcode and see if I can see the problem, but Mac development isn't really my speciality so I'm not holding out too much hope. I did wonder if it had something to do with the last.fm redesign/borked API, but it seems strange it would work right up until upgrading to El Capitan.

Right, I seem to have fixed it locally. It seems to be something to do with El Capitan forcing connections that are using HTTPS to be TLS 1.2. I'm not sure why that affects scrobbling, but disabling App Transport Security seems to have fixed it for me. Not sure if that's a dirty workaround or not, but I'll put in a pull request to @kbhomes and see what he thinks.
In the meantime, I've released my fixed version here: https://github.com/chrismou/radiant-player-mac/releases/tag/v1.4.1
Would appreciate any testing/feedback on whether it works for you. @ameraljovic @nivong @patrickhpan

Only thing I couldn't work out was how to change the version number, so it's trying to get me to "upgrade" to 1.4.1. Small price to pay I guess.

Thanks for the fix @chrismou it works!

Thanks a lot @chrismou.

Cheers guys. I've put in a pull request here: https://github.com/kbhomes/radiant-player-mac/pull/378

@chrismou, works like a charms! :beers:

Is the hotkeys not working on @chrismou's version? Or just here?

No, apparently not.  Doesn't seem to be working on @kbhomes's master branch either.

The media keys are likely something with the 10.11.1 update, issue #381 is tracking that.

Fixed in https://github.com/kbhomes/radiant-player-mac/pull/378 - should be available in the next release (or by building your own binary from master, if you're feeling impatient) :-)

Hmm, still not working on master. Looks unrelated to the original issue. Reopening the ticket while I look into wtf has happened

Now fixed in https://github.com/radiant-player/radiant-player-mac/pull/400


RESTful Api update

Frontend PR: https://github.com/PoiPoi-Dev/PoiPoi-frontend/pull/183
Backend PR: https://github.com/PoiPoi-Dev/poipoi-backend/pull/112


Split coins.json to small files

coins.json is 1000+ lines

it would looks like this ?
coins/ethereum.json
coins/bitcoin.json
Having one file is ok too

The advantage would be reduced risk of merge conflict on the coins.json file. On a second thought, I don't think it is worth the effort -- we don't have new coins that often, and long-living pending pull request should be avoided anyways.

Make sense!


Scratch buffer inherits the major mode of the underlying buffer, making it non-editable in many situations

If the scratch buffer is opened while, for example, in the DOOM dashboard, the scratch buffer will inherit all the keymaps of the dashboard. This makes the scratch buffer non-editable. One has to manually switch to another mode.
I would like to start a discussion on this topic. Would it not be better to start the scratch buffer in fundamental-mode and let the user manually change the mode? The mode would then stick to whichever selection the user made when the scratch is closed and opened some other time.

That certainly is an oversight on my part.
Though I'm not totally opposed to removing this functionality, how about if I simply made it a little smarter: don't let it inherit major modes that aren't editing modes (or whose buffers are read-only).
Despite this, users can still override the major mode in persistent scratch buffers with a local variable:
# -*- mode: python-mode -*-

Or something like that, still, users can change the major mode after the fact.
Do you think that's an acceptable compromise?

I have the feeling that the scratch buffer's mode should be independent of
any other buffer. The purpose of this buffer is mostly to scribble things
in it, take temporary notes or quickly execute some lisp code. I have the
feeling that if the scratch buffer changes modes depending on what I'm
looking at, things will only get confusing/annoying for the user.
I'd be interested to know how others feel about it though.
On Thu, 29 Mar 2018, 00:04 Henrik Lissner<EMAIL_ADDRESS>wrote:

That certainly is an oversight on my part.
Though I'm not totally opposed to removing this functionality, how about
if I simply made it a little smarter: don't let it inherit major modes that
aren't editing modes (or whose buffers are read-only).
Despite this, users can still override the major mode in persistent
scratch buffers with a local variable:
-- mode: python-mode --
Or something like that, still, users can change the major mode after the
fact.
Do you think that's an acceptable compromise?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/hlissner/doom-emacs/issues/490#issuecomment-377052781,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF4SDqYViIuhBYupFY1sv8rs8MTQ5fs2ks5tjAjOgaJpZM4S-65h
.

I've added the doom-scratch-buffer-major-mode variable, which is now set to nil by default. This means scratch buffers default to fundamental-mode. It also accepts t (the old behavior of inheriting the major mode of the buffer you were looking at), and any major-mode symbol.
If anything more complex is needed, I suggest keeping this set to nil and adding a hook to doom-scratch-buffer-hook.

I was able to change Doom's default scratch buffer mode with this line in my config.el:
(setq-default doom-scratch-initial-major-mode 'text-mode)

I was able to change Doom's default scratch buffer mode with this line in my config.el:
(setq-default doom-scratch-initial-major-mode 'text-mode)


automatically collects outputs from submodel

First draft to show some ideas:

focusing on user experience at the moment, demonstrated in
test_base_model.py
now the user needs to modify an existing outputs call and add a call
to combine and flatten submodel outputs

testing on vehicle model, there seems to be an increase in jitting time (from 45 -> 80 sec) for jax. Jax execution time also increases
Reducing the outputs form submodes (Eg, cutting down on tire outputs numbers) helps alleviate this issue. This seems to show that even though we only use the con_outputs in the NLP functions, creating a large outputs and then extracting con_outputs from it seems to suffer from performance drop when the number of outputs increases! (maybe in the ops, the large outputs is still created, and it is then 'indexed/gather' to collect the con_outputs)

directly indexing con_outputs from outputs also didn't help with jit time
    def _extract_con_outputs(self, outputs: lnp.ndarray) -> lnp.ndarray:
        idx = np.array(
            [
                self.get_var_index("outputs", c)
                for c in self.get_group_names("con_outputs")
            ],
            dtype=np.int32,
        )
        return outputs[idx]

when we add additional dummy outputs to the tire model, even just 10 outputs, it significantly increases the jit time, and also slows down the execution (to a lesser extent)
Suspect this is because as we pass submodel outputs to top level, it goes through a train of ops to:

concat scalars to an array (make_vector(...))
turned from an array to a dictionary (combine_submodel_outputs, array_to_dict)
concat scalars to an array (in the parent model)
and so on...

So maybe the PR  #49 to use only array I/O for the autograd level is the best approach? (and inside we just use dictionaries, which then hopefully would never see scatter/gather except for the top level)


add query string parameters for setting panel width

Currently writing a course and embedding codepan iframes for experimenting with JS, yet having large console is a design problem for integration. I was thinking about something like what Glitch does: https://glitch-embed.glitch.me/#preview

IssueHunt Summary

Backers (Total: $100.00)

 issuehunt ($100.00)

Submitted pull Requests

#70 iframe width and tabs

Become a backer now!
Or submit a pull request to get the deposits!
Tips

Checkout the Issuehunt explorer to discover more funded issues.
Need some help from other developers? Add your repositories on IssueHunt to raise funds.

IssueHunt has been backed by the following sponsors. Become a sponsor

@issuehunt has funded $100.00 to this issue.

Submit pull request via IssueHunt to receive this reward.
Want to contribute? Chip in to this issue via IssueHunt.
Checkout the IssueHunt Issue Explorer to see more funded issues.
Need help from developers? Add your repository on IssueHunt to raise funds.

This https://github.com/egoist/codepan/pull/75 Pull request includes tabs as GET parameters

cc @makerslabemlyon


nixos/tests: fix succeed() with multiple commands

we previously immediately returned the first commands output, and didn't
execute any of the other commands.
Now, return the last commands output.
This should be documented in the method docstring.
cc @Mic92 #73033
Motivation for this change
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

Notify maintainers
cc @tfc @marijanp

How would that look in python? yield output from inside the loop?

How would that look in python? yield output from inside the loop?

i would not go more complex than
(status, out) = self.execute(...)
output += out

Updated to handle output as suggested.


Swagger Validation for File Downloads

Swagger Validation failed for ZIP File Download,
I am trying to write a file download API. It is a stream type for response but it is failing as "Response Validation failed"
My Yaml FIles is like this:
produces:
  - application/zip

/library/getacitemspackage:
  # This is the controller for getting the acitem and all its internal references as a deep package for the seamless delivery
    x-swagger-router-controller: library_get_acitems_package
    # this is a post method verb of the api service call
    post:
      summary: The API does the zip of all the given acitems and brings all the deep copy references packages from the cloud library
      description: The API does the zip of all the given acitems and brings all the deep copy references packages from the cloud library
      operationId: libraryGetAcitemsPackage
      parameters:
        - name: acitemsList
          in: body
          description: The list of all the acitems for which the package needs to be delivered as a zip
          schema:
            type: object
      responses:
        "200":
          description: Success
          schema:
            type: object
        default:
          description: Error
          schema:
            $ref: "#/definitions/ErrorResponse"

My API code is like this :
			var archive = archiver('zip');
			var totalAcitemListArray = totalAcitemList.toArray();
			for (var index = 0; index < totalAcitemListArray.length; index++) {
				archive.append(fs.createReadStream(path.join(root_directory, totalAcitemListArray[index])), { name:totalAcitemListArray[index] });
			}
			archive.finalize();
			archive.on('error', function(err) {
				response.status(500).send({error: err.message});
			});
			response.send('acitemsPackage.zip');
			archive.pipe(response);

Since you've already closed this issue, I'm guessing you already found the solution.  Just in case though... try changing your response type from "object" to "file".  I believe that will do the trick.

Hi Bigstick Carpet, I tried that too, but the problem is with the swagger-tools, sorry i was using swagger-node and it uses a older version of the swagger-tools package(0.9.0) but the team have updated the latest type:file in the 0.9.1. So that was the issue. I have reported the issue to the swagger team. Thank you for your help


Draw repeat barline dots on all staves

Currently Lomse draws dots of repeat barlines only on the first staff of the instrument, for example:

However repeat dots are commonly placed on each staff in multi-staff scores. This PR makes repeat dots appear on all staves, so the example shown above now looks like the following:

As repeat dots drawing is handled by a barline shape, this shape needs to know coordinates of all staves in its range, so most of the changes in this PR are about forwarding this information to barline shapes. The first commit here reverts b3c2f2b4c2d32040fad74b8f3efaa91a2175ad62 and instead ensures that vertical staff position shifts are reset when a new system's layout begins. This is needed to ensure that InstrumentEngraver::get_top_line_of_staff() (which definition is changed to take these shifts into account, consistently with the other relevant methods of InstrumentEngraver) always gives correct positions for staff coordinates in the current system.

Thank you for this PR. I will check it as soon as possible.

I have reviewed the PR and all the changes make sense to me. All unit tests and regression test passed, so I'll merge it.
I had doubts about whether the static method in BarlineEngraver should be defined in other place. It contains general knowledge about barlines and should perhaps be placed in a new BarlineUtilities class defined in lomse_score_utilities.h, but my second thought was that this method will probably never be used, other than this specific case in BarlineEngraver. Thus, it is simpler to keep it as is and, if convenient, it could be moved in future.
Thanks again for this PR!


proposal: refactor to be used as a library

I've been working over my own local development processes (which is itself written in go) and have taken to using gobin (because it's awesome) as part of that solution. Currently I'm calling that from os.exec - but it would be far more versatile as a library.

My immediate response would be "no" simply because we've all managed to live with the go command not being a library! It just feels like we'd be creating another API surface we'd have to maintain, which given gobin largely calls out to the go command doesn't seem worth the effort.
Can you give a few more details?
cc @rogpeppe @mvdan

In my scenario I have a mix of local code to go run/go build + exec and with non-local code being run with gobin -run. I would be extending the work of gobin but a good deal of the logic is buried in the main function and a smattering of it in unexported functions. I'm not arguing in any degree that it works - I am using it and I'm glad I'm not having to write everything. Unfortunately this means instead of using a slightly less opaque API of functions, I'm having to write another similar layer, which is not very maintainable and difficult to maintain.
Another aspect of it is going from what binary it's using to where the source files are, which unfortunately for some projects I need access to.
I've also had to use the go APIs for parsing go.mod data which at least exists talks are going that they may be putting that in the standard lib.


No OTA on the Espressif boards?

Currently it is stated that the Espressif boards do not support OTA.
Is that temporary or is there a technical limitation?
What does this mean for the meaning of "Supported Hardware"? Is there a minimal subset that needs to work?

Thanks for the quick reply. Does Amazon have any minimal requirements for a product to count as "Supported Hardware"?

There are no additional requirements if a board has already passed under Amazon FreeRTOS qualification program (AFQP). You can read more about AFQP here.  Using a qualified board and Amazon FreeRTOS kernel, you can write applications that can securely connect to AWS IoT.

I am working on a AWS IoT application for a custom ESP32 device and will definitely need OTA support as well as BLE capability. If these features are not available in the near future for AWS freeRTOS, is the default to use AWS IoT Embedded C SDK and then use the Espressif OTA functionality?

Amazon FreeRTOS now supports OTA on ESP32. Please refer to https://amzn.to/2MEciPK for more details. Regarding BLE- while we don't yet have a standardized BLE interface for Amazon FreeRTOS, our partners such as Espressif have solutions for BLE, and our software will work with these solutions. If you want to discuss your use case further, please feel free to reach out to us at freertos-qual AT amazon DOT com.


fix(query): adjusted severity rating and added searchLine in rbac_wildcard_in_rule k8s rule

Proposed Changes

Add searchLine to point to specific rule attributes
Combine the CxPolicy rules into one
Extend description
Adjust rating from LOW to MEDIUM (or HIGH?) for the following reasons:

The rule rbac_roles_with_read_secrets_permissions checks for a specific "permission subset" of this rule and  is rated MEDIUM. This rule here implicitly also covers the same case as the other rule by checking for wildcards, which allow even wider access rights
Wildcard permissions on resources (pods, depoyments, secrets, ...) also include create, update, patch, delete, bind, escalate, impersonate verbs.  Overall, this can put the availability of deployments at risk, in addition to violating confidentiality and integrity
The worst-case setting would be * on all apiGroups, resources, and verbs, essentially meaning cluster admin rights and this would even justify a HIGH severity rating. Depending on what is set to *, the potential blast radius varies. If you think it would be reasonable to assume the worst-case scenario here, HIGH would be appropriate - otherwise at least MEDIUM, I'd say 😊

I submit this contribution under the Apache-2.0 license.

Hello, @Churro! Can you update the severity to HIGH, please?

Hi @rafaela-soares, done :smiley:


Error while running the tutorial

Executing cell 5 in tutorial results in core dump. Tried to execute the same lines in a script and got Illegal instruction (core dumped).
Any help is appreciated!
The machine has 90GB of RAM.
 Are you on an M1 mac by chance?

Thanks for the quick response!
I tried first on M1 Mac but as I noted there I realized that there are dependency issues on Python >=3.8.
Here I report issues on Linux kernel #1 SMP Wed Nov 9 20:13:27 UTC 2022. Installation works, but the execution of MultiMAP.Integration([rna, atac_genes], ['X_pca', 'X_lsi']) consistently fails with core dump.

Could I get you to try a thing for me? I'm pretty sure the various weird crashes people are encountering ultimately lead back to annoy, a package that lives up to its name. Could you pop open MultiMAP/matrix.py in your clone of the repo and replace the definitions of create_tree() and query_tree() with the following:
def create_tree(data, metric):
    if metric == 'euclidean':
        ckd = cKDTree(data)
    else:
        ckd = KDTree(data, metric=metric)
    return ckd

def query_tree(data, ckd, k, metric):
    if metric == 'euclidean':
        ckdout = ckd.query(x=data, k=k, n_jobs=-1)
    else:
        ckdout = ckd.query(data, k=k)
    return ckdout

Then go back to the main directory of the clone and call pip3 install . again, and try to run the thing again.

indeed, that fixes the issue, thank you! :)

Great, in that case I'll roll this out properly (need to decide whether to allow annoy at all). I also figured out how to get rid of the numba requirement, allowing the package to move into newer python releases - as it turns out, it was a single problematic function borrowed from an archival UMAP release.


Performance

The performance as of 0.1.6 is worse than expected.
Between two virtual machines on the same virtualized network (capable of about 30 Gbps of throughput), Quincy only manages:

~ 1.1 Gbps during Server -> Client data transfer
~ 1.3 Gbps during Client -> Server data transfer

with an MTU of 1400 bytes.
Server -> Client
Initial profiling did not yield anything suspicious, other than the fact that QuincyTunnel::process_inbound_traffic takes more time (had more samples) than QuincyTunnel::process_outbound_traffic during the Server -> Client data transfer, which is odd, as most of the data transfered should be going through QuincyTunnel::process_inbound_traffic.
The CPU usage on the Server virtual machine is also only 60 % balanced across all cores, which could mean either either too much IO, or that the Client is the bottleneck.
The CPU usage on the Client is much higher, in the 90s.
Server flamechart:

Client flamechart:

Client -> Server
Pretty much the same behaviour as above - QuincyClient::process_inbound_traffic takes more time than QuincyClient::process_outbound_traffic, which is, again, suspicious.
The CPU usage on the Server side is above 90 %, on the Client side only ~ 70 %.
Server flamechart:

Client flamechart:

Initial conclusions
It seems that the CPU usage on the receiving side is quite high, and that the receiving side spends more time in their respective process_inbound_traffic methods, which is highly suspicious (most of the data transfered should be handled by the respective process_outbound_traffic methods, at least that is my initial assumption).
Further investigation will be needed as to where Quincy client and server spend too much time.
TODO

[x] Test the same scenario with lower and higher MTU
[x] Find the culprit behind suspicious ratio of CPU time spent between process_inbound_traffic and process_outbound_traffic

https://tailscale.com/blog/throughput-improvements/
and
https://tailscale.com/blog/more-throughput/
might be useful in regards to optimizing TUN performance, which seems to be problem at the moment (a lot of time spent in poll_write for the TUN interface).

Different MTUs
With an MTU of 6000, the throughput nearly triples, to about ~ 3 Gbps on regardless of data transfer direction.
From the flamecharts, it is clear that more CPU time is spent encrypting the packets, but most of the time is still spent in poll_write for the TUN interfaces.
Server -> Client
Server flamechart:

Client flamechart:

Client -> Server
Server flamechart:

Client flamechart:

GSO/GRO support is work-in-progress: https://github.com/ssrlive/rust-tun/pull/45

related?
https://users.rust-lang.org/t/zero-copy-async-io-in-rust/106996/3

I can try if io_uring would improve the performance on Linux, it might require some nontrivial changes in the TUN library, but could we worth a shot.


[CT-1557] [Feature] dbt run flag to continue after compilation errors

Is this your first time submitting a feature request?

[X] I have read the expectations for open source contributors
[X] I have searched the existing issues, and I could not find an existing issue for this feature
[X] I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature
Sometimes when developing projects we can leave a model unfinished while working on others. These unfinished models create compilation errors due to dbt needing the fully developed DAG to execute.
A flag like --force should be added to dbt run --select <model> to warn about these compilation errors but ultimately continue with the execution of the selected models. This offers flexibility to developers when they know an unrelated model (not in the same DAG) is broken.
A discussion of this feature: https://discourse.getdbt.com/t/compiling-models-will-break-runs-for-different-models/684
Describe alternatives you've considered
The alternative is to fix the models with compilation errors or delete the broken code. It is much easier, and at times the only option, to delete and come back to the model later. This is less than ideal.
Who will this benefit?
DBT users who quickly develop models or those who have many independent DAGs.
Are you interested in contributing this feature?
Yes. Guidance on what scripts to start with.
Anything else?
https://discourse.getdbt.com/t/compiling-models-will-break-runs-for-different-models/684

Thanks for this idea @kyle-kent !
To make sure I'm following along with your scenario:

are these unfinished models just in your local environment and in use by a single developer?
or are the unfinished models being committed to your project's repository and/or being shared by multiple developers?

@dbeatty10 thanks for the response! The first scenario is what I'm thinking. The second is possible but sounds like bad practice.
This actually came up today during work. I moved a table from mart to intermediate and this raised a compilation error in tables and tests that I did not care about in that moment.

@kentkr wow, very timely that it came up even today!
Drew did give a nice high-level description of such a feature in that discussion you referenced:

I can definitely imagine adding a flag to dbt that would surface compilation errors as warnings. If a model with a compilation error is referenced by a model included in the dbt run, then this would result in a proper error. If the model is instead unrelated, then the compilation error could just be surfaced as a warning.

I don’t think this is something we’re going to prioritize in the near future, but wanted to give you a few different ideas for how to deal with this situation that we've all found ourselves in before:

Quick n' dirty trick 👈
git stash
Commit in progress work, rebase or squash later

I'm going to assume that the instigating situation is that you were originally developing on one section of the code, but then needed to switch focus on some other section of the code before being able to finish the in-progress work.
Quick n' dirty trick
There's two categories a node can be in:

leaf node (with no dependent nodes)
internal node (having at least one dependent node)

For the first category, here's a trick that I've used personally:

rename the non-compiling model to be my_model.sql.x instead of my_model.sql

Since dbt only worries about certain file names (like .yml, .sql, and .py), it will ignore any files ending in .x like they don't even exist.
For the second category, you can do this variation:

rename the non-compiling model to be my_model.sql.x instead of my_model.sql
restore the original definition of my_model.sql that was compiling previously or just give it a dummy definition like select 1

git stash
Assuming that your dbt project is stored in git and you have local uncommitted changes that are raising compile issues, git stash saves your local modifications away and reverts back to a clean working directory.
@jtemporal has a nice write up of how to use git stash here.
Commit in progress work, rebase or squash later
Of course we can always commit the in-progress work in a separate branch, then open a fresh branch for the divergent work.
The problem is that we might not love the resulting commit messages and that there were individual commits within the in-progress branch where the code didn't actually work. Let's assume that were able to come back later to the in-progress branch and finish it off and you want to clean things up before sharing this branch with others.
One way to do this would be to perform an interactive rebase to combine commits.
If you are using GitHub and your repository is configured to allow it, a separate option would be to squash the commits when merging the final pull request.

@dbeatty10 thanks for the tips and I understand the lack of priority. I'd still like to contribute if you're willing to take a look at the PR.
I took a look at the code and am struggling to find where DBT creates a DAG and decides whether a dependency exists or not. Can you point me to where that occurs? Thanks!

@kentkr There's at least one more option which I didn't think to mention earlier (because I hadn't yet used it myself):

Adding the file(s) to .dbtignore

Using .dbtignore
Suppose I have a model named my_model that isn't working right now. Adding its path to the .dbtignore file will cause it to be ignored before it is even compiled when running dbt run --select <some other model>:
.dbtignore
models/my_model.sql

Review of options when there are compilation errors
We have quite the list of options to solve this problem when it arises:

add the file(s) to .dbtignore
quick n' dirty trick (i.e., adding an .x to the end of the relevant file name)
commit in progress work, rebase or squash later
git stash
re-clone your project into a separate directory from the one with the broken models then run your project in the new directory
fix the compilation error(s)

All of these are possible today without any additional code. Among all of them, .dbtignore would probably be not much more cumbersome than adding a --force flag (especially if it's just one or two models that are causing issues). Once you know about it, it's pretty easy to do and also easy to undo.
Upon further reflection
We want to be thoughtful of the time investment for the contributor (you!) as well as the code reviewers and make sure the "juice is worth the squeeze". In the particular case of a --force option, my gut says the implementation would be relatively complicated, take a fair amount of effort, and wouldn't yield a huge impact over pre-existing options. Even if we could magically snap our fingers and have this implemented already, it's possible the additional code would make maintenance in the future more burdensome.
For those reasons, I'm going to close this issue.
I hope you know that we are always open to hearing your ideas and suggestions for how to improve our product! And we'd definitely welcome your contributions on other issues. For dbt-core specifically, we've got a nice little list of good_first_issues. But you don't need to restrict yourself to just those -- we've got lots of other repos to contribute to also! I'm looking forward to collaborating with you in the future.

@dbeatty10 it did seem complicated lol. Thanks for the list of first issues to contribute to!


Fix wrong name of the GamepadSettings in root_preferences.xml

Hi, Thanks for the great application!
I found that the app will crash trying to tap the "Gamepad Mapping" on settings. After quick investigation I found that the fragment had a wrong class name, so it crash with "class name not found".
This will fix the issue and enable setting gamepad mapping again.

Thanks!


Include hash parameters in login redirection URL

When logging in, the return URL does not include the hash parameters, so the users map setup is lost

With old DE I got around this by storing the full URL in a database but I don't like the solution. I was hoping that using the full .NET core standard would be better but I guess not. This however reminds me that I was going to mention we need to add a retention policy for permalinks as well. I don't think we want to keep them indefinitely so do you have a default length? I'd say a couple of weeks or a month should be the maximum if not logged in and then we can provide options for logged in users.


[SPARK-13091][SQL] Rewrite/Propagate constraints for Aliases

This PR adds support for rewriting constraints if there are aliases in the query plan. For e.g., if there is a query of form SELECT a, a AS b, any constraints on a now also apply to b.
JIRA: https://issues.apache.org/jira/browse/SPARK-13091
cc @marmbrus

Test build #51002 has started for PR 11144 at commit ac830a4.

Test build #51002 has finished for PR 11144 at commit ac830a4.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/51002/
Test PASSed.

Merged build finished. Test PASSed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/51014/
Test FAILed.

Merged build finished. Test FAILed.

test this please

Test build #51016 has started for PR 11144 at commit 5316e85.

Test build #51016 has finished for PR 11144 at commit 5316e85.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/51016/
Test PASSed.

Merging to master.


New version: InMemoryDatasets v0.3.0

Registering package: InMemoryDatasets
Repository: https://github.com/sl-solution/InMemoryDatasets.jl
Created by: @sl-solution
Version: v0.3.0
Commit: 0c145cf911f15300ac130c7ac48afb9a460d2862
Reviewed by: @sl-solution
Reference: https://github.com/sl-solution/InMemoryDatasets.jl/issues/21
Description: Multithreaded package for working with tabular data in Julia

Please merge this manually, since, it meets sequential version number guideline, however, version 0.2.0 was published but not registered.


docs building error

Description

Test for python 3.9 fails

To Reproduce
pytest -v tests

Resolved by working on #9


Running on CPU

Hello,
I have installed tensorflow 1.0.1, CUDA-8.0 and CUDNN 6.0.
After building and compiling the folder this is the error I am facing.
How can I solve this?
techm@techm-XPS-8500:~/Faster-RCNN_TF/tools$ python demo.py --model /home/techm/Faster-RCNN_TF/VGGnet_fast_rcnn_iter_70000.ckpt
W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use SSE3 instructions, but these are available on your machine and could speed up CPU computations.
W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use SSE4.1 instructions, but these are available on your machine and could speed up CPU computations.
W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use SSE4.2 instructions, but these are available on your machine and could speed up CPU computations.
W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use AVX instructions, but these are available on your machine and could speed up CPU computations.
Tensor("Placeholder:0", shape=(?, ?, ?, 3), dtype=float32)
Tensor("conv5_3/conv5_3:0", shape=(?, ?, ?, 512), dtype=float32)
Tensor("rpn_conv/3x3/rpn_conv/3x3:0", shape=(?, ?, ?, 512), dtype=float32)
Tensor("rpn_cls_score/rpn_cls_score:0", shape=(?, ?, ?, 18), dtype=float32)
Tensor("rpn_cls_prob:0", shape=(?, ?, ?, ?), dtype=float32)
Tensor("rpn_cls_prob_reshape:0", shape=(?, ?, ?, 18), dtype=float32)
Tensor("rpn_bbox_pred/rpn_bbox_pred:0", shape=(?, ?, ?, 36), dtype=float32)
Tensor("Placeholder_1:0", shape=(?, 3), dtype=float32)
Tensor("conv5_3/conv5_3:0", shape=(?, ?, ?, 512), dtype=float32)
Tensor("rois:0", shape=(?, 5), dtype=float32)
[<tf.Tensor 'conv5_3/conv5_3:0' shape=(?, ?, ?, 512) dtype=float32>, <tf.Tensor 'rois:0' shape=(?, 5) dtype=float32>]
Tensor("fc7/fc7:0", shape=(?, 4096), dtype=float32)
Loaded network /home/techm/Faster-RCNN_TF/VGGnet_fast_rcnn_iter_70000.ckpt
CUDA driver version is insufficient for CUDA runtime version
CUDA driver version is insufficient for CUDA runtime version
CUDA driver version is insufficient for CUDA runtime version
CUDA driver version is insufficient for CUDA runtime version
CUDA driver version is insufficient for CUDA runtime version
CUDA driver version is insufficient for CUDA runtime version
CUDA driver version is insufficient for CUDA runtime version
CUDA driver version is insufficient for CUDA runtime version
Segmentation fault (core dumped)
Kindly help
Thanks.

hi~i get the same problem,have you already solved it? is it tue to memory or stack too small ?


static_cast<npy_intp>( )
    feather/interop.h:556:31: warning: implicit conversion loses integer precision: 'const int64_t' (aka 'const long long') to 'npy_intp' (aka 'long') [-Wshorten-64-to-32]
        npy_intp dims[1] = {arr_->length};
                           ~~~~~~~^~~~~~
    feather/interop.h:570:61: warning: implicit conversion loses integer precision: 'long long' to 'size_t' (aka 'unsigned long') [-Wshorten-64-to-32]
          memcpy(PyArray_DATA(out_), arr_->values, arr_->length * ByteSize(arr_->type));
          ~~~~~~                                   ~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~
    feather/interop.h:556:25: error: non-constant-expression cannot be narrowed from type 'int64_t' (aka 'long long') to 'npy_intp' (aka 'long') in initializer list [-Wc++11-narrowing]
        npy_intp dims[1] = {arr_->length};
                            ^~~~~~~~~~~~
    feather/interop.h:521:5: note: in instantiation of function template specialization 'feather::py::FeatherDeserializer<5>::ConvertValues<5>' requested here
        ConvertValues<TYPE>();
        ^
    feather/interop.h:659:5: note: in instantiation of member function 'feather::py::FeatherDeserializer<5>::Convert' requested here
        FROM_FEATHER_CASE(UINT8);
        ^
    feather/interop.h:648:24: note: expanded from macro 'FROM_FEATHER_CASE'
          return converter.Convert();                               \
                           ^
    feather/interop.h:556:25: note: insert an explicit cast to silence this issue
        npy_intp dims[1] = {arr_->length};
                            ^~~~~~~~~~~~
                            static_cast<npy_intp>( )
    feather/interop.h:556:31: warning: implicit conversion loses integer precision: 'const int64_t' (aka 'const long long') to 'npy_intp' (aka 'long') [-Wshorten-64-to-32]
        npy_intp dims[1] = {arr_->length};
                           ~~~~~~~^~~~~~
    feather/interop.h:570:61: warning: implicit conversion loses integer precision: 'long long' to 'size_t' (aka 'unsigned long') [-Wshorten-64-to-32]
          memcpy(PyArray_DATA(out_), arr_->values, arr_->length * ByteSize(arr_->type));
          ~~~~~~                                   ~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~
    feather/interop.h:556:25: error: non-constant-expression cannot be narrowed from type 'int64_t' (aka 'long long') to 'npy_intp' (aka 'long') in initializer list [-Wc++11-narrowing]
        npy_intp dims[1] = {arr_->length};
                            ^~~~~~~~~~~~
    feather/interop.h:521:5: note: in instantiation of function template specialization 'feather::py::FeatherDeserializer<6>::ConvertValues<6>' requested here
        ConvertValues<TYPE>();
        ^
    feather/interop.h:660:5: note: in instantiation of member function 'feather::py::FeatherDeserializer<6>::Convert' requested here
        FROM_FEATHER_CASE(UINT16);
        ^
    feather/interop.h:648:24: note: expanded from macro 'FROM_FEATHER_CASE'
          return converter.Convert();                               \
                           ^
    feather/interop.h:556:25: note: insert an explicit cast to silence this issue
        npy_intp dims[1] = {arr_->length};
                            ^~~~~~~~~~~~
                            static_cast<npy_intp>( )
    feather/interop.h:556:31: warning: implicit conversion loses integer precision: 'const int64_t' (aka 'const long long') to 'npy_intp' (aka 'long') [-Wshorten-64-to-32]
        npy_intp dims[1] = {arr_->length};
                           ~~~~~~~^~~~~~
    feather/interop.h:570:61: warning: implicit conversion loses integer precision: 'long long' to 'size_t' (aka 'unsigned long') [-Wshorten-64-to-32]
          memcpy(PyArray_DATA(out_), arr_->values, arr_->length * ByteSize(arr_->type));
          ~~~~~~                                   ~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~
    feather/interop.h:556:25: error: non-constant-expression cannot be narrowed from type 'int64_t' (aka 'long long') to 'npy_intp' (aka 'long') in initializer list [-Wc++11-narrowing]
        npy_intp dims[1] = {arr_->length};
                            ^~~~~~~~~~~~
    feather/interop.h:521:5: note: in instantiation of function template specialization 'feather::py::FeatherDeserializer<7>::ConvertValues<7>' requested here
        ConvertValues<TYPE>();
        ^
    feather/interop.h:661:5: note: in instantiation of member function 'feather::py::FeatherDeserializer<7>::Convert' requested here
        FROM_FEATHER_CASE(UINT32);
        ^
    feather/interop.h:648:24: note: expanded from macro 'FROM_FEATHER_CASE'
          return converter.Convert();                               \
                           ^
    feather/interop.h:556:25: note: insert an explicit cast to silence this issue
        npy_intp dims[1] = {arr_->length};
                            ^~~~~~~~~~~~
                            static_cast<npy_intp>( )
    feather/interop.h:556:31: warning: implicit conversion loses integer precision: 'const int64_t' (aka 'const long long') to 'npy_intp' (aka 'long') [-Wshorten-64-to-32]
        npy_intp dims[1] = {arr_->length};
                           ~~~~~~~^~~~~~
    feather/interop.h:570:61: warning: implicit conversion loses integer precision: 'long long' to 'size_t' (aka 'unsigned long') [-Wshorten-64-to-32]
          memcpy(PyArray_DATA(out_), arr_->values, arr_->length * ByteSize(arr_->type));
          ~~~~~~                                   ~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~
    feather/interop.h:556:25: error: non-constant-expression cannot be narrowed from type 'int64_t' (aka 'long long') to 'npy_intp' (aka 'long') in initializer list [-Wc++11-narrowing]
        npy_intp dims[1] = {arr_->length};
                            ^~~~~~~~~~~~
    feather/interop.h:521:5: note: in instantiation of function template specialization 'feather::py::FeatherDeserializer<8>::ConvertValues<8>' requested here
        ConvertValues<TYPE>();
        ^
    feather/interop.h:662:5: note: in instantiation of member function 'feather::py::FeatherDeserializer<8>::Convert' requested here
        FROM_FEATHER_CASE(UINT64);
        ^
    feather/interop.h:648:24: note: expanded from macro 'FROM_FEATHER_CASE'
          return converter.Convert();                               \
                           ^
    feather/interop.h:556:25: note: insert an explicit cast to silence this issue
        npy_intp dims[1] = {arr_->length};
                            ^~~~~~~~~~~~
                            static_cast<npy_intp>( )
    feather/interop.h:556:31: warning: implicit conversion loses integer precision: 'const int64_t' (aka 'const long long') to 'npy_intp' (aka 'long') [-Wshorten-64-to-32]
        npy_intp dims[1] = {arr_->length};
                           ~~~~~~~^~~~~~
    feather/interop.h:570:61: warning: implicit conversion loses integer precision: 'long long' to 'size_t' (aka 'unsigned long') [-Wshorten-64-to-32]
          memcpy(PyArray_DATA(out_), arr_->values, arr_->length * ByteSize(arr_->type));
          ~~~~~~                                   ~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~
    feather/interop.h:530:25: error: non-constant-expression cannot be narrowed from type 'int64_t' (aka 'long long') to 'npy_intp' (aka 'long') in initializer list [-Wc++11-narrowing]
        npy_intp dims[1] = {arr_->length};
                            ^~~~~~~~~~~~
    feather/interop.h:521:5: note: in instantiation of function template specialization 'feather::py::FeatherDeserializer<9>::ConvertValues<9>' requested here
        ConvertValues<TYPE>();
        ^
    feather/interop.h:663:5: note: in instantiation of member function 'feather::py::FeatherDeserializer<9>::Convert' requested here
        FROM_FEATHER_CASE(FLOAT);
        ^
    feather/interop.h:648:24: note: expanded from macro 'FROM_FEATHER_CASE'
          return converter.Convert();                               \
                           ^
    feather/interop.h:530:25: note: insert an explicit cast to silence this issue
        npy_intp dims[1] = {arr_->length};
                            ^~~~~~~~~~~~
                            static_cast<npy_intp>( )
    feather/interop.h:530:31: warning: implicit conversion loses integer precision: 'const int64_t' (aka 'const long long') to 'npy_intp' (aka 'long') [-Wshorten-64-to-32]
        npy_intp dims[1] = {arr_->length};
                           ~~~~~~~^~~~~~
    feather/interop.h:542:56: warning: implicit conversion loses integer precision: 'int64_t' (aka 'long long') to 'int' [-Wshorten-64-to-32]
            out_values[i] = util::bit_not_set(arr_->nulls, i) ? NAN : in_values[i];
                            ~~~~                           ^
    feather/interop.h:546:24: warning: implicit conversion loses integer precision: 'long long' to 'size_t' (aka 'unsigned long') [-Wshorten-64-to-32]
              arr_->length * ByteSize(arr_->type));
              ~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~
    feather/interop.h:530:25: error: non-constant-expression cannot be narrowed from type 'int64_t' (aka 'long long') to 'npy_intp' (aka 'long') in initializer list [-Wc++11-narrowing]
        npy_intp dims[1] = {arr_->length};
                            ^~~~~~~~~~~~
    feather/interop.h:521:5: note: in instantiation of function template specialization 'feather::py::FeatherDeserializer<10>::ConvertValues<10>' requested here
        ConvertValues<TYPE>();
        ^
    feather/interop.h:664:5: note: in instantiation of member function 'feather::py::FeatherDeserializer<10>::Convert' requested here
        FROM_FEATHER_CASE(DOUBLE);
        ^
    feather/interop.h:648:24: note: expanded from macro 'FROM_FEATHER_CASE'
          return converter.Convert();                               \
                           ^
    feather/interop.h:530:25: note: insert an explicit cast to silence this issue
        npy_intp dims[1] = {arr_->length};
                            ^~~~~~~~~~~~
                            static_cast<npy_intp>( )
    feather/interop.h:530:31: warning: implicit conversion loses integer precision: 'const int64_t' (aka 'const long long') to 'npy_intp' (aka 'long') [-Wshorten-64-to-32]
        npy_intp dims[1] = {arr_->length};
                           ~~~~~~~^~~~~~
    feather/interop.h:542:56: warning: implicit conversion loses integer precision: 'int64_t' (aka 'long long') to 'int' [-Wshorten-64-to-32]
            out_values[i] = util::bit_not_set(arr_->nulls, i) ? NAN : in_values[i];
                            ~~~~                           ^
    feather/interop.h:546:24: warning: implicit conversion loses integer precision: 'long long' to 'size_t' (aka 'unsigned long') [-Wshorten-64-to-32]
              arr_->length * ByteSize(arr_->type));
              ~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~
    feather/interop.h:612:25: error: non-constant-expression cannot be narrowed from type 'int64_t' (aka 'long long') to 'npy_intp' (aka 'long') in initializer list [-Wc++11-narrowing]
        npy_intp dims[1] = {arr_->length};
                            ^~~~~~~~~~~~
    feather/interop.h:521:5: note: in instantiation of function template specialization 'feather::py::FeatherDeserializer<11>::ConvertValues<11>' requested here
        ConvertValues<TYPE>();
        ^
    feather/interop.h:665:5: note: in instantiation of member function 'feather::py::FeatherDeserializer<11>::Convert' requested here
        FROM_FEATHER_CASE(UTF8);
        ^
    feather/interop.h:648:24: note: expanded from macro 'FROM_FEATHER_CASE'
          return converter.Convert();                               \
                           ^
    feather/interop.h:612:25: note: insert an explicit cast to silence this issue
        npy_intp dims[1] = {arr_->length};
                            ^~~~~~~~~~~~
                            static_cast<npy_intp>( )
    feather/interop.h:612:31: warning: implicit conversion loses integer precision: 'const int64_t' (aka 'const long long') to 'npy_intp' (aka 'long') [-Wshorten-64-to-32]
        npy_intp dims[1] = {arr_->length};
                           ~~~~~~~^~~~~~
    feather/interop.h:620:44: warning: implicit conversion loses integer precision: 'int64_t' (aka 'long long') to 'int' [-Wshorten-64-to-32]
            if (util::bit_not_set(arr_->nulls, i)) {
                ~~~~                           ^
    48 warnings and 12 errors generated.
    error: command 'cc' failed with exit status 1

    ----------------------------------------
Command "/Users/johnmcdonnell/venv/bin/python -u -c "import setuptools, tokenize;__file__='/private/var/folders/cv/mqh6bv697bn1fkm8qvm6yz0m0000gn/T/pip-build-P5mz3T/feather-format/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /var/folders/cv/mqh6bv697bn1fkm8qvm6yz0m0000gn/T/pip-TbCtSk-record/install-record.txt --single-version-externally-managed --compile --install-headers /Users/johnmcdonnell/venv/include/site/python2.7/feather-format" failed with error code 1 in /private/var/folders/cv/mqh6bv697bn1fkm8qvm6yz0m0000gn/T/pip-build-P5mz3T/feather-format/
```

Thanks. This problem occurs on Apple's built-in Python 2.7 and I'm able to reproduce it. Working on a patch

@johnmcdonnell i'm going to cut a v0.1.1 release on pypi, let me know if it still does not work for you

Thanks, works perfectly now! Excited to leave my CSV troubles behind.


Update machine-learning-r-csharp-lexicon-based-sentiment-analysis.md

Update for refresh

Hi @jaymathe, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (jaymathe). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;


Poltergeist screen size

I've just switched to using poltergeist as my driver, and am having an issue with my screenshots.  They will save fine, but the images are only about 10px tall.  I have my current window size in capy/poltergeist set to 1680x1050.  The strange thing is, the issue only occurs on our pages that use Ember... other page images are appropriately sized.  A similar thing occurred when I first started using capybara-webkit, until I was told I had to set the webkit_options.  Is there a similar setting for poltergeist that I'm not seeing?
Also, if I do a save_screenshot, the image on the very same page looks fine.  It's screenshot_and_save_page and screenshots on failures that have this issue.

Hi @zacharyjt, I am sorry but I can't allocate time to working out why this effects you only for Ember :(  Did you manage to ever figure it out?


Battle cleric Decisive Strike

The dmg type of the added die was bludgeoning when the weapon dmg die was piercing. This was with a light crossbow at lvl 4.

Screenshots and save always help.

Decisive strike is vanilla and there isn’t anything in desc that suggests it must use weapon damage. Not a bug.

I'll keep everything in mind next time. Thanks!


Make clippy happy

Made clippy happy

I'll merge it myself since this is a trivial change and fix the CI failure in the master branch.