Please add the InsertMedia function

Can you please add bindings for the InsertMedia function, it would be very useful :)
My use case is, I'm experimenting with midi livecoding in Rust and I want to integrate it into Reaper as a VST.
The only way to edit the arrangement via the API seems to be via InsertMedia:
Every time the composition changes, writing the midi from memory into a file on disk and then calling InsertMedia.
(Or can you see another way?)
There are 2 related functions:
https://www.reaper.fm/sdk/reascript/reascripthelp.html#InsertMedia
https://www.reaper.fm/sdk/reascript/reascripthelp.html#InsertMediaSection
But for my use case I only need InsertMedia, because every call will overwrite the full composition.

CC @PrismaPhonic https://github.com/helgoboss/reaper-rs/issues/18

There are ways to do this more directly and I think it would involve functions like AddMediaItemToTrack, AddTakeToMediaItem, CreateNewMIDIItemInProj etc. However, it's not super straightforward and it would probably need more time to turn this into good idiomatic Rust. InsertMedia on the other hand should be very easy to add to the medium-level API. If that's enough for you, I could give it a go.

There are ways to do this more directly and I think it would involve functions like AddMediaItemToTrack, AddTakeToMediaItem, CreateNewMIDIItemInProj etc. However, it's not super straightforward and it would probably need more time to turn this into good idiomatic Rust. InsertMedia on the other hand should be very easy to add to the medium-level API. If that's enough for you, I could give it a go.

Yes, I think having InsertMedia would be sufficient for now. Thanks :)

It seems the other way (CreateNewMIDIItemInProj etc.) requires bindings to many more functions, to be able to populate/modify the newly created media item.

Yes, I think having InsertMedia would be sufficient for now. Thanks :)

It seems the other way (CreateNewMIDIItemInProj etc.) requires bindings to many more functions, to be able to populate/modify the newly created media item.

I just realized that the VST also needs to clear the track before adding the new media item, so I'd also need these functions (to iterate over all items and delete each):
https://www.reaper.fm/sdk/reascript/reascripthelp.html#GetTrackNumMediaItems
https://www.reaper.fm/sdk/reascript/reascripthelp.html#GetTrackMediaItem
https://www.reaper.fm/sdk/reascript/reascripthelp.html#DeleteTrackMediaItem
(I could add it on a new track but that would not be idempotent behavior. Also the midi track's FX and routings should survive the "midi file reload".)

Btw, can non-VST Reaper plugin DLLs run in the background, or are they only ran on demand like scripts (and need to be compiled as a VST if they should stay running in the background)?
I only used the Reaper extension API from inside a VST or from a LUA script until now, so I'm wondering if I should compile this one as a VST or as a normal DLL (that exposes ReaperPluginEntry).

I just realized that the VST also needs to clear the track before adding the new media item, so I'd also need these functions (to iterate over all items and delete each):
https://www.reaper.fm/sdk/reascript/reascripthelp.html#GetTrackNumMediaItems
https://www.reaper.fm/sdk/reascript/reascripthelp.html#GetTrackMediaItem
https://www.reaper.fm/sdk/reascript/reascripthelp.html#DeleteTrackMediaItem
(I could add it on a new track but that would not be idempotent behavior. Also the midi track's FX and routings should survive the "midi file reload".)

Btw, can non-VST Reaper plugin DLLs run in the background, or are they only ran on demand like scripts (and need to be compiled as a VST if they should stay running in the background)?
I only used the Reaper extension API from inside a VST or from a LUA script until now, so I'm wondering if I should compile this one as a VST or as a normal DLL (that exposes ReaperPluginEntry).

@Boscop Please see the draft pull request. There are some things that still need to be figured out concerning insert_media().
BTW, if it's urgent, you can always fall back to the low-level API (which brings us down to C level but maybe better than nothing).

@Boscop Please see the draft pull request. There are some things that still need to be figured out concerning insert_media().
BTW, if it's urgent, you can always fall back to the low-level API (which brings us down to C level but maybe better than nothing).

Btw, can non-VST Reaper plugin DLLs run in the background, or are they only ran on demand like scripts (and need to be compiled as a VST if they should stay running in the background)?
I only used the Reaper extension API from inside a VST or from a LUA script until now, so I'm wondering if I should compile this one as a VST or as a normal DLL (that exposes ReaperPluginEntry).

REAPER extension plug-ins are loaded directly at REAPER startup and are unloaded when it quits. So if you want something that's allround all the time and doesn't benefit from having multiple instances around, an extension plug-in is an even better choice than a VST plug-in. reaper-rs has support for both. No need to write the ReaperPluginEntry stuff yourself, there's a macro for that, see the README.

Btw, can non-VST Reaper plugin DLLs run in the background, or are they only ran on demand like scripts (and need to be compiled as a VST if they should stay running in the background)?
I only used the Reaper extension API from inside a VST or from a LUA script until now, so I'm wondering if I should compile this one as a VST or as a normal DLL (that exposes ReaperPluginEntry).

REAPER extension plug-ins are loaded directly at REAPER startup and are unloaded when it quits. So if you want something that's allround all the time and doesn't benefit from having multiple instances around, an extension plug-in is an even better choice than a VST plug-in. reaper-rs has support for both. No need to write the ReaperPluginEntry stuff yourself, there's a macro for that, see the README.

Thanks for the quick implementation, I'll try it out asap.
Yes, I saw that section in the Readme, which caused me to even consider compiling it as non-VST plugin.
But if I wanted to have a text input field (for entering the path to the (Rust) DLL that will be watched and auto-reloaded, which produces the composition), how can I expose an Editor from a non-VST extension plugin? (And then how to open it inside Reaper?)

Thanks for the quick implementation, I'll try it out asap.
Yes, I saw that section in the Readme, which caused me to even consider compiling it as non-VST plugin.
But if I wanted to have a text input field (for entering the path to the (Rust) DLL that will be watched and auto-reloaded, which produces the composition), how can I expose an Editor from a non-VST extension plugin? (And then how to open it inside Reaper?)

If it's just simple text fields, you could use get_user_inputs(). If you have a child window handle that doesn't need to be a parent, you could dock it by using DockWindowAdd and related functions (not yet in reaper-medium but easy to add). Or how about opening a top-level Boscop webview window 😃, triggered by a REAPER action (which can be assigned to a toolbar button) or a custom entry in the "Extensions" menu?

If it's just simple text fields, you could use get_user_inputs(). If you have a child window handle that doesn't need to be a parent, you could dock it by using DockWindowAdd and related functions (not yet in reaper-medium but easy to add). Or how about opening a top-level Boscop webview window 😃, triggered by a REAPER action (which can be assigned to a toolbar button) or a custom entry in the "Extensions" menu?

Btw, I'm considering using imgui-baseview (or iced_baseview) for the GUI, which GUI lib are you using for your Rust-rewrite of ReaLearn? :)

I'm using SWELL (which is a part of WDL and exposed via low-level API), but it's not something I would generally recommend because it's raw Win32 UI programming which feels very clunky, more so in a language like Rust. Also, I didn't find a way to avoid having RefCells all over the place because I'm not in control of the event loop (could probably have just ignored reentrancy issues by using UnsafeCell instead, but then it felt like giving up on some of Rust's safety measures). I just did it because SWELL comes as part of REAPER and standard OS UI components are pretty well suited for a tool like ReaLearn.
I'm interested how things work with imgui-baseview and stuff!

Btw, I'm considering using imgui-baseview (or iced_baseview) for the GUI, which GUI lib are you using for your Rust-rewrite of ReaLearn? :)

I'm using SWELL (which is a part of WDL and exposed via low-level API), but it's not something I would generally recommend because it's raw Win32 UI programming which feels very clunky, more so in a language like Rust. Also, I didn't find a way to avoid having RefCells all over the place because I'm not in control of the event loop (could probably have just ignored reentrancy issues by using UnsafeCell instead, but then it felt like giving up on some of Rust's safety measures). I just did it because SWELL comes as part of REAPER and standard OS UI components are pretty well suited for a tool like ReaLearn.
I'm interested how things work with imgui-baseview and stuff!

Having a bit of a nightmare with this at the moment.
I also want to use the InserMedia so I'm down in the low API at the moment.
        unsafe {
            let c_str = CString::new(msg.data).unwrap();
            let c_world: *const c_char = c_str.as_ptr() as *const c_char;
            Reaper::get().medium_reaper().low().InsertMedia(c_world, 1);
        }

I found this solution, which claims to work:
    let c_str = CString::new(to).unwrap();
    let c_world: *const c_char = c_str.as_ptr() as *const c_char;

I was also sure you would have written utility method somewhere for this but I'm just not good enough at reading rust to spot it.
It saying "use of a moved value" on the msg.data in this line let c_str = CString::new(msg.data.).unwrap();
But adding Copy and Clone traits falls foul of the fact it's got two "String" fields ... this is making my OO brain hurt.
I guess firstly, did you create a wrapper / utility method?
If not, how on earth do I get this working? LOL. NURSE!!


extract 11ty customisations into NHSBSA 'theme'

What
11ty doesn't support themes, but it should be possible to extract all the customisations we've done in the playbook, into a library.
Why
Some groups in the BSA want to maintain their own open source, NHSBSA branded documentation.
Extracting the work done for the playbook will make this easier to maintain a common approach to sites like this one.

Discussed in https://github.com/nhsbsa/nhsbsa-digital-playbook/discussions/209

Originally posted by WORTI3 August 30, 2023
What
Extract common code to the nhsbsa-docs library.
Why
The playbook acts as a handbook that others can easily contribute to and fork for other information-based playbooks. All boilerplate and components that aren't playbook-specific should be moved to the nhsbsa-docs repo, as this is technical and won't be touched by those adding pages.
In short: this will improve the ability to add new content to the playbook and simplify the code involved.
We should be able to install the NHSBSA-docs package into the playbook to gain access to specific functionality as needed.
Anything else
Example code available on WIP branches.


[FEATURE] Introduce builtin Longhorn monitoring stack

          Hello. I copy these rules to my helm chart

https://github.com/SomeBlackMagic/helm-charts/tree/master/charts/longhorn-monitoring
In this chart, i can disable some rules or change the severity level.
Also in future a want add grafana dashboards automaticly
Originally posted by @wirwolf in https://github.com/longhorn/longhorn/issues/3580#issuecomment-1144571098

related: https://github.com/longhorn/longhorn/pull/6157


Missing App Engine facet functionality

App Engine Facet is missing the following features:

installing the facet should configure the project to have the GAE runtime as the primary runtime (if a GAE runtime does not exist, a new one should be created)
uninstalling the facet should remove the GAE runtime as the primary runtime
the facet should limit runtime support of only App Engine Standard runtime
wiki page should be updated with facet functionality

Agree with 1 and 4. I'm not sure why uninstalling the facet should necessarily remove the runtime; and I'm not sure I follow what "facet should limit runtime support of only App Engine Standard runtime" means for the functionality.

In regards to point 2 (uninstalling the facet should remove the GAE runtime as the primary runtime):
Adding an App Engine facet to a project means that the project wants App Engine support which means they want to be able to run/debug their project with the dev app server and deploy to App Engine. If the App Engine facet is removed from a project, that means that the project no longer needs to be run on the dev app server which means that the project has no need for the App Engine runtime.
Removing the GAE runtime as the primary runtime means that GAE is not the default runtime for that project, which when the facet is uninstalled is correct.
After more thought, I think the GAE runtime should not only be removed as the primary runtime, but the GAE runtime should only be compartable with projects that have the GAE facet.
In regards to point 3 (the facet should limit runtime support of only App Engine Standard runtime):
After more thought, I think that should be removed because one of the big things for the App Engine 'reboot' was flexibility. In other words, the user should be able to use GAE runtime if they want (by installing the App Engine facet) but should be able to use other runtimes too.

Is this a superset of #254 ?

The last point is kind of opposite of #254, meaning that a project with the GAE facet can use the GAE runtime and any other runtimes they choose. I am leaning more towards this because it is more flexible and also, I can't see it causing any problems.
I also should mention, that installing a GAE facet could also lead  to the creating of an appengine-web.xml file if it doesn't already exist

For your last point of generating appengine-web.xml, perhaps we need to identify if a project is standard or flexible. For flex, we generate app.yaml then?

My current thinking is that there should be different facets for GAE Standard and Flex mainly because they have different requirements e.g java 7 vs 8, so one project cannot support both standard and flex

Just wanted to note that uninstalling the facet would not delete the appengine-web.xml.


[doc][zh]Fixed the formatting of the text Using_HLL, missing a small parenthesis

…parenthesis
Why I'm doing:

What I'm doing:
Fixes #issue
Fixed the formatting of the text Using_HLL, missing a small parenthesis
What type of PR is this:

[ ] Doc

Does this PR entail a change in behavior?

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

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[ ] This is a backport pr

Bugfix cherry-pick branch check:

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

[ ] 3.3
[ ] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@ZmmBigdata can you sign-off this contribution by git commit -s

thanks for your contribution, really appreciate it


add print button and its print colour and black & white both.

I add print button.

@gunjansaha55 update your repository and add a screenshot of where the print button is located and what happens on click.
Your code seems like you have pasted the code as it is from stack overflow.

I modify my codes and again added the print button and its works. I added some screenshots.
<img width="1440" alt="Screenshot 2022-10-15 at 3

29 26 PM" src="https://user-images.githubusercontent.com/97596347/195980825-d148a1b0-65a6-4832-8672-d21cb3df3f92.png">

Please update the branch and then make a PR

@kaal-coder I update the branch and then make a PR.


Add MIT license

I added MIT license to the project (more information). Let me know if you want another license like GPL or Apache.

Thanks, I hadn't even thought about licensing.


Pathlib2 switched to new syntax in setup.py without bumping major or minor version

The switch to new syntax for conditional dependencies in pathlib2-2.3.2 causes issues to automated build tooling that uses pex. This line: https://github.com/mcmtroffaes/pathlib2/blob/develop/setup.py#L47 used to be done in extras_require instead of install_requires.
Recent versions of setuptools and wheel are able to parse this new syntax, but older versions enforced by pex are not: https://github.com/pantsbuild/pex/blob/v1.4.5/pex/version.py#L9
Until recently, wheel was also forced to version that is not able to parse new syntax: https://github.com/pantsbuild/pex/blob/v1.4.4/pex/version.py#L11
This would be less of an issue if pathlib2 bumped a version in major or minor instead of just patch part of the version number. This is a breaking change for build systems that worked just fine with pathlib2-2.3.0.
I'm asking if we can do one or both of the following to fix this issue.

Revert to extras_require in version 2.3.x of pathlib, preferably 2.x and perhaps use it only for the next major version?
Perhaps avoid using the new syntax entirely? This is a backport package and those who need a backport package most probably do not have up-to-date environment anyway to parse the new features.

Thanks for reporting and sorry for the delay in the response here. I've just pushed a release that uses the old deprecated syntax.


Backtraces upon faults

This would be pretty helpful for debugging

@cstanfill is working on this---eh_frame is a rather interesting format, it turns out

I think this can be closed.


Code School Scholarships title CSS Misalignment

Bug Report
What is the current behavior?
I noticed at my screen resolution, 1366 x 768, the title of this section is displayed incorrectly.

What is the expected behavior?
Header shouldn't overlap with text below it
Additional Info
Issue was originally posted on main repo: https://github.com/OperationCode/operationcode/issues/762
Operating System
Windows 10
Browser
Chrome

Quick fix that wouldn't require any changes to CSS - change the text content of the h6 element to from 'Code School Scholarships' to just 'Scholarships'

Actually - looks like the :after rule on the h6 element in preview.css is causing this:
h6::after {
  flex-grow: 1;
  height: 3px;
  content: '\a0';
  background-color: rgba(0, 0, 0, 0.25);
  align-self: center;
  margin: 0 10px 5px 10px;
}

Very strange ... somehow styles applied to HTML tags in preview.css are leaking out into the global CSS scope. Thought CSS modules was supposed to prevent this?

Modules
General module
Encompasses links, buttons, etc.

a:link,
a:hover,
#left_navigation_box a:last-child,
a#blog_keywords:focus,
a:visited {
  color: #2d2d2d;
}

a:focus {
  border-bottom: 1px dotted #ccc !important;
}

I wonder if this was caused by the recent version bump. Hmmm :thinking:

Upping to high because the issue is highly visible and potentially deflecting new users.

Oh snap that's my css

@jmayergit we shouldn't have let element styles through on our PR review cycle. That's my bad for not outlining that clearly to all devs.
We're going to make an issue to add this check as a Git hook.

You can't think of everything, fairly obscure.
Like @jjhampton I thought the CSS styles would only apply to preview.js. Lesson learned

I'm gonna tackle this.

Assigned as a placeholder for @ctruelson

https://github.com/OperationCode/operationcode_frontend/pull/557 actually fixes this so I recommend closing this issue @kylemh

It should, shouldn't it... It hasn't, but I suspect that's a different problem...


TextEdit: scrolling broken with Wrap Enabled unless empty line at end

Godot version:
v3.2.alpha.calinou.dc114fa2e
OS/device including version:
OS: Ubuntu 19.04 x86_64
Kernel: 5.0.0-13-generic
WM: i3
CPU: Intel Celeron N3450 (4) @ 2.200GHz
GPU: Intel Device 5a85
Memory: 2634MiB / 5351MiB
Issue description:
TextEdit scrolling only works if you have a blank line at the end. This is most prominent with a single paragraph. When scrolled to the bottom of the text, attempting to scroll up does not show earlier text, only the last line. This issue is solved by adding a blank line at the end, though this is not ideal.
Steps to reproduce:

Create new TextEdit node
Turn on text wrap
Insert large amount of text ( like Lorem Ipsum )
Ensure there is no blank line at the end
Scroll to bottom of TextEdit node
Attempt to scroll back up
Observe only the last line displays on the screen

Workaround:

Add blank line at end of document
Scroll to bottom of TextEdit
Attempt to scroll back up
Observe scrolling now works as intended

Minimal reproduction project:
TextEditBug.zip
Thanks Godot team and contributors for everything you do! :beers:

Sounds like an issue which was fixed already, can you try a more recent build?

I can confirm the bug is still present as of last nights daily build:
v3.2.beta.calinou.28294b1f1

Closing because #32229 appears to be the same issue and #33492 did indeed fix it. After compiling from master the issue is no longer present. It appears that the merge did not make it in time to be incorporated in Calinous' daily build.
Thanks team!


Update product scope in Developer Guide

The product scope details information about AddressBook.
WedLog has a significantly different target audience and value proposition.
Let's change the product scope to reflect WedLog's target audience and value proposition.
This will make the developer's guide more relevant for WedLog.

LGTM!!


Correct documentation for expect. Fixes #327, #236

Simply don't mention that a truthy value could be returned from expect

This is a dup of PR #262 I just merged that in.


docker-compose config should be secure by default

Currently, the docker compose configuration doesn't set APP_DEBUG=false, or APP_ENV=production. This means a user accessing even something as simple as a page that doesn't exist (404) will see all environment variables, including database credentials, and other sensitive information, due to the Symfony exception page.

@lrstanley I totally agree. Would you like to submit a PR to update those to more secure defaults?


QR Code Link (HoloLens App) not correct

Thank you for the guide and instructions for creating a collection of links to Dynamics 365 Guides.
I think have found an error in the guide.
The PC app link works fine, but the HoloLens App link does not work.
The PC app link is in this format:
ms-guides://MY-ORG.crm4.dynamics.com/g/8921ce53-ee6b-4006-b173-1deba90c9101
and the HoloLens App link should be in this format:
ms-guides://MY-ORG.crm4.dynamics.com/g/nl-tt6A_vUy1cGeU3HlhEQ
However using your guide the HoloLens App link is
https://api.qrserver.com/v1/create-qr-code/?qzone=4&size=1000x1000&bgcolor=666666&&data=ms-guides://MY-ORG.crm4.dynamics.com/g/8921ce53-ee6b-4006-b173-1deba90c9101
It works and creates a pretty QR code but it obviously reads as
ms-guides://MY-ORG.crm4.dynamics.com/g/8921ce53-ee6b-4006-b173-1deba90c9101 in a QR scanner
This is not in the format ms-guides://MY-ORG.crm4.dynamics.com/g/nl-tt6A_vUy1cGeU3HlhEQ (letters and numbers but NOT a GUID) which would be the correct QR code link for the HoloLens.
I can se that the link to the HoloLens QR code/link is not saved in the Guides table in Dataverse. How do I get the value of the HoloLens link? I would like to know how to access the RANDOMSTRING which is the last bit of the Link to the guide.
Is there a way to generate it based on the GUID of the Guide? Or is it just a random string? Any way to access the link besides manually right clicking on the guide and Copy Link?
Hope you can expand the guide on how to create the correct QR Code Link for the HoloLens App.
Kind regard
Marianne Lilholt
Donkey Power

[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 9716b57d-8fe1-3e11-8789-2b248a598c15
Version Independent ID: 9f6c723c-0bbc-3e5f-b601-1ecb340abc22
Content: Workflow example 1--Automatically generate deeplinks for the Dynamics 365 Guides PC and HoloLens apps - Dynamics 365 Mixed Reality
Content Source: mr-docs/guides/workflow-example-1.md
Service: dynamics-365-guides
GitHub Login: @Mamaylya
Microsoft Alias: mamaylya

Hi there.
Two months since you assigned this to the doc author. How is the answer coming along? We really could use an instruction on how the "random string" part of the link to the guide is created.
Is there a way to generate it based on the GUID of the Guide? Or is it just a random string? Any way to access the link besides manually right clicking on the guide and Copy Link?

Hi there
Five months since you assigned to the doc author. Have you had time to think of an answer?
We have created a workaround where we manually cut and paste the link to the guide and then have a Power Automate Flow which turns it into an environment aware link. But it would be easier if the link was just the GUID in stead of a random string - or the random string was saved in Dataverse.

@Mamaylya Can you take a look at this request? If you could answer the questions, then I can update the documentation.

@v-wendysmith @Mamaylya hope you have had a pleasant Christmas and New Year. How is the documentation on the link to a Dynamics Guide coming along?

@MezMarianne hope your new year has started off well. There are two different QR code link formats and both are equivalent. Both links contain the unique ID of the Guide record (a GUID). The compressed format contains the binary data of the GUID encoded in a way to minimize the total length. The second format contains the string version of the GUID (which results in a longer string).  I've discussed with the PM for Guides and we will be working on updating the documentation to explain the encoding process.
In the meantime, they have asked for you to open a support ticket so they can determine why the QR code isn't working in your HoloLens. Thank you for following up!

@MezMarianne this took a while to resolve but we managed to release an update to the article based on your feedback. Thanks again for raising it and thanks to @v-wendysmith for completing the update. The refreshed article is going live later today.
Thanks,
Michael


Add possibility to render an overlay component on video

This change adds a new renderOverlayComponent prop that allows to render something on top of the video, but under controls / play button.
Example:
        <VideoPlayer
          video={{uri}}
          style={styles.video}
          videoWidth={320}
          videoHeight={240}
          renderOverlayComponent={() => (
            <Text
              style={{
                color: 'white',
                position: 'absolute',
                right: 20,
                bottom: 20,
              }}>
              Testing
            </Text>
          )}
        />

Hey, we completely rebuilt this component. If you could resolve the conflicts and add it to the latest codebase, that would be great! Anyway, thanks for your work!

@moskalakamil Thank you, I'll take a look when I have time.


About hyper-parameter

Hi,
Nice paper and thanks for sharing the code.
I noticed that the command given in this repo is different from Appendix A in the paper.
In the paper, hyper-parameters between experiments are shared and set to same in table 3 and 4.

Is there much performance difference between different hyper-parameters?
What should I do if I want to run your algorithm in a new dataset?

Thanks so much!

Ah, thanks for reminding me to fix this. At one point, I updated the HPs (and results) in the paper to be simpler, because I found that they didn't make much of a difference. I never changed them in this repo.

Thanks for the reply.
Very insightful paper for saving GPU memory and computation cost.
Hope to see more results on large network structures such as ResNet!

@csyanbin I wonder it would work in larger network because it brings more weights as it could increase the risk of overfitting. That why the former work MAML reduced the number of convolutional filters .

So -- just to make sure I'm translating parameters from the paper to code correct, the parameters for the omniglot experiments would look like this?
# 1-shot
python -u run_omniglot.py \
    --train-shots 10 \
    --inner-batch 10 \
    --inner-iters 5 \
    --shots 1 \
    --eval-batch 5 \
    --eval-iters 50 \
    --meta-batch 5 \
    --meta-iters 100000 \
    --learning-rate 0.001 \
    --meta-step 1 \
    --meta-step-final 0

# 5-shot
python -u run_omniglot.py \
    --train-shots 10 \
    --inner-batch 20 \
    --inner-iters 10 \
    --shots 1 \
    --eval-batch 10 \
    --eval-iters 50 \
    --meta-batch 5 \
    --meta-iters 200000 \
    --learning-rate 0.0005 \
    --meta-step 1 \
    --meta-step-final 0

Hi @jaegerstar, thanks for the discussion.
In a paper named "Deep Meta-Learning: Learning to Learn in the Concept Space", they used maml-style update and applied ResNet as the CNN structure. And they gained improvements compared with original MAML paper.
The difference is that they only meta-update the last few layers for ResNet.

@csyanbin  thanks, I will take a look.

@bkj I see one problem--your 5-shot arguments should have --shots 5. Also, you may want to pass --transduction depending on which experiment you want to reproduce.


Grammar mistake in example

{GENDER:He|She|They} will see it when {GENDER:logs|logs|log} in.

should be
{GENDER:He|She|They} will see it when {GENDER:he|she|they} {GENDER:logs|logs|log} in.

right?

Yes. Your variant is more correct. Thanks for spotting!


Update scope selector for Node.js

Per the javascript-node bundle, the source scope is source.js.node.
Ref: https://github.com/drnic/javascript-node.tmbundle/blob/master/Syntaxes/JavaScript Node.tmLanguage#L29

That's the Dash-used list of keywords as far as I know and not the scope selector. You can include "node" if you want, but it won't change anything.

Indeed, you are correct, the PR was too hasty.  Not sure how my "test" appeared to "pass" with that change.
The actual problem is that many language scopes are of the form source.language.dialect and the language function picks the last element, when the first element after source is usually what you want.  Or better yet, you want the base language plus the dialect.  So js would have the bulk of the JavaScript related doc sets, and js.node would specify the node.js specific docsets, and the resulting docset selector list would be the concatenation of js.node and js.


Uncaught Error: Cannot find module '$ATOM_HOME/packages/proto-repl/lib/lein-runner.coffee'

Hey there.
When trying to start a REPL in atom, I receive this error. Are there any dependencies that I'm missing? On OS X El Capitan
-Thanks
[Enter steps to reproduce below:]

Open core.clj
Repl-toggle (ctrl-alt-, shift-L)
Error is produced

Atom Version: 1.7.4
System: Mac OS X 10.11.5
Thrown From: proto-repl package, v1.1.10
Stack Trace
Uncaught Error: Cannot find module '/Users/Alcatraz/.atom/packages/proto-repl/lib/lein-runner.coffee'
At module.js:340

Error: Cannot find module '/Users/Alcatraz/.atom/packages/proto-repl/lib/lein-runner.coffee'
    at Module._resolveFilename (module.js:338:15)
    at Function.Module._resolveFilename (/Applications/Atom.app/Contents/Resources/app.asar/src/module-cache.js:383:52)
    at Function.require.resolve (/Applications/Atom.app/Contents/Resources/app.asar/src/native-compile-cache.js:53:23)
    at new Task (/Applications/Atom.app/Contents/Resources/app.asar/src/task.js:35:26)
    at Function.module.exports.Task.once (/Applications/Atom.app/Contents/Resources/app.asar/src/task.js:17:14)
    at LocalReplProcess.module.exports.LocalReplProcess.start (/Users/Alcatraz/.atom/packages/proto-repl/lib/local-repl-process.coffee:63:27)
    at Repl.module.exports.Repl.startProcessIfNotRunning (/Users/Alcatraz/.atom/packages/proto-repl/lib/repl.coffee:94:3)
    at Object.module.exports.ProtoRepl.toggle (/Users/Alcatraz/.atom/packages/proto-repl/lib/proto-repl.coffee:170:13)
    at Object.module.exports.ProtoRepl.toggleCurrentEditorDir (/Users/Alcatraz/.atom/packages/proto-repl/lib/proto-repl.coffee:188:6)
    at atom-workspace.subscriptions.add.atom.commands.add.proto-repl:toggle-current-project-clj (/Users/Alcatraz/.atom/packages/proto-repl/lib/proto-repl.coffee:19:5)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:260:29)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:61
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:580:16)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:388:22)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeyEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:98:36)
    at HTMLDocument.<anonymous> (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:3:61)

Commands
     -8:21.9.0 proto-repl:pretty-print (atom-text-editor.editor.is-focused)
  2x -6:39.5.0 window:toggle-dev-tools (atom-text-editor.editor.is-focused)
 10x -5:53.4.0 core:backspace (atom-text-editor.editor.is-focused.autocomplete-active)
     -4:08.6.0 proto-repl:toggle-current-project-clj (atom-text-editor.editor.is-focused)
     -1:31.8.0 core:copy (atom-notification.fatal.icon.icon-bug.native-key-bindings.has-detail.has-close.has-stack)
     -0:00.7.0 proto-repl:toggle-current-project-clj (atom-text-editor.editor.is-focused)

Config
{
  "core": {
    "packagesWithKeymapsDisabled": [],
    "themes": [
      "one-dark-ui",
      "base16-tomorrow-dark-theme"
    ]
  },
  "proto-repl": {
    "leinPath": "/usr/local/bin/lein",
    "refreshOnReplStart": true
  }
}

Installed Packages
# User
proto-repl, v1.1.10

# Dev
No dev packages

Try restarting Atom. It looks like some code has not loaded correctly.

I installed JDK and restarted Atom. Works like a charm now. Thank you and thanks for the REPL!


Investigate Postgres flexible server

Currently the max number of connections supported by our Postgres instance is ~950, and we top out now around 350. So this isn't an urgent need, but as we scale up ReportStream to new senders as well as potentially to new diseases we'll want to be ready for future scale.
Additionally our current install (Postgres single server) has no upgrade path beyond the current one (v11).
Some useful resources:

Flexible Server overview
Comparing single vs flexible
One method of migrating
Pricing of flexible server

A few initial notes:

It seems like Flexible Server doesn't support cross-region replication, so disaster recovery is more work. (We can likely ship daily/incremental backups to another region, but setting up the server in another region would be on us.)
Flexible Server comes with built-in PgBouncer support, which is another project we were investigating

Also, follow up with SimpleReport team on their migration process.


Is there a case in which I don't need body parsers?

I spent the last couple of hours trying to figure out where did my body parameters disappeared.
Eventually, after digging into the code, I saw that what I was missing was urlencoded: { extended: true } (I had just the json part).
So my question is, why do I need to set it explicitly?

Because in microservices I think the JSON request/response is the default and not the urlencoded POST requests.

Isn't the JSON parser set by default? Then why not both?
Could it cause issues when both parsers are set?

It doesn't cause issues, just I thought it can be enough.


KAFKA-8213 DOCS - Fix typo in Streams Dev Guide

Description

Jira ticket:  https://issues.apache.org/jira/browse/KAFKA-8213

Fixed typo in Streams Developer Guide interactive queries section

Related
PR on kafka-site: https://github.com/apache/kafka-site/pull/201
cc: @mjsax , @guozhangwang , @joel-hamill , @JimGalasyn
Signed-off-by: Victoria Bialas<EMAIL_ADDRESS>

Merged to trunk and cherry-picked to 2.2, 2.1, 2.0, 1.1 and 1.0 branches.
Thanks for the fix @londoncalling!


Fix bugs and add cn-proxy

Hi, maybe limited to my network environment, sometimes the POST request you intercept, especially playlists with more than 100 songs, might be cut into multiple function calls, so that gzip can't decode easily, which causes error.
I added function to cache the previous buffer that can't be decoded.
Also I wrote a function to get the first proxy on cn-proxy.

Thank you for being the first contributor (and probably the last = =||)
Multi POST request bug is a good point. I noticed before that sometimes gzip decompress fails but didn't think of the true reason. Your solution seems right.
For cn-proxy, I added a auto-proxy selector based on your simple solution. Because sometimes a  cn-proxy server can get 404 or None from Netease music server, so a auto proxy change is very necessary.
And I guess we both are familiar David Tang......

Sorry I'm not familiar with the guy you mentioned, but I happen to find this repo when I searched on Github. This is really interesting because this repo is created recently.
Btw, do you mind me sharing this with others? Since you are the main contributor, I think it's necessary to ask for your permission first.

Oh, a coincidence then. I mentioned that guy because he reposted this on SNS and he is also a Yale Phd student..
And you are welcomed to share this tool with anyone! without any restriction. After all helping others is my first intention.


GH-40431: [C++] Move key_hash/key_map/light_array related files to internal for prevent using by users

Rationale for this change
These files expose implementation details and APIs that are not meant for third-party use. This PR explicitly marks them internal, which also avoids having them installed.
Are these changes tested?
By existing builds and tests.
Are there any user-facing changes?
No, except hiding some header files that were not supposed to be included externally.

GitHub Issue: #40431

cc @kou , it's a temporary fix. And i haven't add ut for now. PTAL?

@kou how about this refactor?

cc @zanmato1984 if you're interested in this

@zanmato1984 Thank you very much for your suggestion, the code looks clearer!

My one last suggestion :)

Thanks!

Thanks @zanmato1984
cc @felipecrv @pitrou do we have some reviewers for ASOF join?

@pitrou PTAL!
The new commit include two things:

Move these codes(key_hash/key_map/light_array) to internal! Besides, seems it's unnecessary to use internal namespace for them. The purpose we want is just prevent user's calling/
Simple refactor to simplify some codes in TempVectorStack.

@github-actions crossbow submit -g cpp

@github-actions crossbow submit -g cpp

@github-actions crossbow submit -g cpp

CI failures are unrelated, I'll merge.


Update zig build to latest master

Version: approximately usable at zig 0.11.0-dev.1571+c1f71963a.
Also, adds package manager support (early MVP).
We need to add root build zig file to support Zig Package Manager. Once package manager gets support for overidding build root directory - we can move this logic in src/build.zig and remove root build.zig.
Also, now every build artifacts must accept target and optimize arguments, so it is also adjusted.
For now, there is not much info about how to use package manager in Zig, so I will leave it here:
Create build.zig.zon:
.{
    .name = "raylib_usage",
    .version = "0.0.0",

    .dependencies = .{
        .raylib = .{
            .url = "https://github.com/raysan5/raylib/archive/543333cae47c397f9bce93fe654aeba7cbe7e33d.tar.gz",
            .hash = "1220a2bf5e5a53060256428b107b7a86077581861e9cb7b42c5083f443575646d59f",
        },
    },
}

Hashes and commits may need adjusting (once merged).
Then in build.zig of your project:
...
const raylib_dep = b.dependency("raylib", .{
    .target = target,
    .optimize = optimize,
});
...
exe.linkLibrary(raylib_dep.artifact("raylib"));
...

@star-tek-mb thank you very much for the review! Maybe thos information could be added somewhere in the Wiki for future users?

Yeah, it should be added to Wiki, but after proper tooling for zig package manager (cli). Like adding dependencies (like npm install).

I feel like this PR was premature given that Zig 0.11 hasn't been released to this day. The average user (me :)) now can't use raylib's build.zig because it uses std.Build which isn't available in 0.10.1 (the latest release). In the future I would recommend waiting for official releases before updating build.zig given the possibility for sudden unannounced API changes breaking the script.
#2913 related

@Not-Nik Thanks for noticing it, I expected Zig 0.11 to be released by next raylib release but it's not...

I feel like this PR was premature given that Zig 0.11 hasn't been released to this day. The average user (me :)) now can't use raylib's build.zig because it uses std.Build which isn't available in 0.10.1 (the latest release). In the future I would recommend waiting for official releases before updating build.zig given the possibility for sudden unannounced API changes breaking the script.
#2913 related

You are right to some extent. But zig 0.11 have many C ABI fixes on windows and linux. (https://github.com/ziglang/zig/pull/14333). So, i recommend to upgrade anyways, but if you want to use raylib for 0.10.1 you can use older raylib version I think.


[Test] reallocate person

Coverage remained the same at 100.0% when pulling 847750ea94f7cfd06a07543596ee90c77541c1ca on tests into 18fc4358a73d40c38e4f3c0e4f65e222e3ce17eb on master.

Your tests dont cover the dojo file which is observably where your functionality is. You might want to include it in your testing otherwise your coverage isnt a true reflection of the implemented functionality

How do I add it here >> 'nosetests --with-coverage --cover-package=src'

I think it makes more sense to move the file into the src package

cool, will do that


help, how to work with ramda?

I have configed the antd sucessfully
but ramda does not work
         tsImportPluginFactory({                 libraryName: 'ramda',                 libraryDirectory: 'es',               }),
any one help me?

I think you should throw an error if the path is wrong


Enable discard_unpacked_layers by default

Issue #, if available:
Fixes #1359.
Description of changes:
Sets discard_unpacked_layers = true in the containerd config file. This is a disk space optimization.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Testing
Verified the config key:
> containerd --version
containerd github.com/containerd/containerd 1.6.19 1e1ea6e986c6c86565bc33d52e34b81b3e2bc71f

> containerd config default | grep -A3 -B3 discard_unpacked_layers
    [plugins."io.containerd.grpc.v1.cri".containerd]
      default_runtime_name = "runc"
      disable_snapshot_annotations = true
      discard_unpacked_layers = false
      ignore_rdt_not_enabled_errors = false
      no_pivot = false
      snapshotter = "overlayfs"

@cartermckinnon After this change we are having issue with image export in containerd:
https://github.com/containerd/containerd/issues/9277
https://github.com/containerd/nerdctl/issues/2588
when we disable this flag manually, image export is successful.
Would you have any thoughts on this?

Why do you need to export images from the node’s container runtime?

@cartermckinnon we need to create an image tar and do some processing in that tar.
basically, the image export functionality should work.

@cartermckinnon got your point. Thanks for the crane tool suggestion.

👋 @cartermckinnon
I wonder if you know a workaround for a challenge we get with this setting being the new default.
In our case we need to export an image from the k8s worker node to the pod. The reason we need to it via the node is that we want k8s users to leverage Pull Secrets and get the image on the nodes using their credentials that our pod has no idea about.
Once the image is pulled, we wanted to export it from the node's image store to the POD by bind mounting the containerd.sock, but it seems that it is not possible anymore, because of the missing layer.
Would appreciate if anyone found a workaround for this.

In general, I would recommend a tool like crane for working with container images inside a pod. Mounting the node's container runtime socket into a pod is risky because 1) it gives the pod the ability to control any other pod on the node and 2) lets the pod circumvent its resource limits by consuming CPU/memory/disk that it has not been allocated (which can interfere with kubelet).
That being said, you know your workload better than I do. 😄 We're working on #1630, which will allow you to disable this setting in the containerd config.

Thanks for your comments, @cartermckinnon
We looked at crane and skopeo, but we couldn't still export the image that was pulled by a kubelet and extensive googling failed me as well.
We are not concerned about the security limitations or resource shunting as, indeed, the clusters we created are ephemeral, not multi-tenanted and specifically are made for CI.
The only reason we need the export capability is to export the image pulled by the k8s and import it in the docker-in-docker pod we are running. This works great when discard_unpacked_layers is not set.
Would be amazing to have this setting exposed tot he EKS users, but also I would be super super curious to know why a simple layer packing can't be done when layers are missing, since the image is run-worthy, why can't one pack it up?

You can disable it via setting it to false using below strategy.
I updated the config.toml using below command as eks bootstrap script is using this file as the base file.
sed -i 's/discard_unpacked_layers = true/discard_unpacked_layers = false/g'  /etc/eks/containerd/containerd-config.toml
Once you update this, you can verify this using below command from your worker node.
containerd config dump

Hi @zaidmnsr
would you mind sharing more details about this approach? At what step you change the config.toml?

Hi @hellt
You can use this command in userdata script. You can modify userdata script in launch template by creating a new version of launch template.


Yongchao/pp pca update

Followup of https://github.com/TuringLang/TuringTutorials/pull/348

@YongchaoHuang can you resolve the git merge conflict, and remove the edits to BayesianDiffEqs, please?

@yebai just hold this until Sunday? I am planning to have a quick review over the weekend?

@storopoli Thanks a lot Jose for the nice review and helpful suggestions - I will have a look and respond ASAP.

@storopoli Thanks very much for the guidance - this is really good practice, I am looking at it.

@storopoli @yebai I just fixed one bug which leads to long sampling time (I forgot to transpose mat_exp when instantiating 'pPCA_ARD(mat_exp)'). Then I run all Julia blocks and it works now - for the two blocks involving NUTS sampling, each takes less than 10 mins to run.
I have not weaved the whole .jmd on my local machine - I just successfully tested the Julia blocks. I think it is improved a lot with Jose's corrections on math symbols.
Would it be possible for you guys to have a quick (hopefully final) review, then we can merge it into master? Thanks ahead.

@yebai it is up to you. I have not checked the code thoroughly, just the model syntax and the text (math, punctuation and typos).

Let's see whether @devmotion is also happy. He worked on this tutorial sometime ago.

@storopoli @devmotion @yebai Thanks a lot for your comments, suggestions and help for improving this PR, I guess most, if not all, of the concerns have been addressed and problems solved. The weaved html looks good - ready to merge?

Many thanks, @YongchaoHuang, for the nice improvements! I am merging this now as the version on the docs website is broken and will benefit from this PR.

@yebai Great. We can always improve it in the future if necessary.

@YongchaoHuang congratulations! Good work!

@storopoli Many thanks  for your help along the journey!


[IDE] Preview downloads files

Describe the bug
Preview tab causes the browser to download the file that is being edited/published.
To Reproduce
Steps to reproduce the behavior:

Create a .websocket file
Open it in the editor
Click save
See that it's downloaded

Expected behavior
Files are not downloaded
File types affected

.websocket
.calculationview

Desktop (please complete the following information):

OS: MacOS 11.6
Browser: Both Safari and Chrome experience this issue

Progress to be tracked in:

https://github.com/eclipse/dirigible/issues/1224

PR merged in Eclipse Dirigible. The functionality will be available with the next release of Eclipse Dirigible.


Blueprints are arranged in random order

Specially during reconfiguring, the blueprints are arranged in some random order. This creates visual discrepancies in user experience.

fixed by #445


docs(*): fix typos

Overview
fix typos
I hope it helps.

PR Checklist

[x] I did below actions if need

I read the Contributing Guide
I added documents and tests.

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


favicon takes 267 kB

https://100r.co/media/services/icon.png takes 267 kB and is often the biggest element on your website. You may want to consider using an SVG format to efficiently compress the image (or reuse https://100r.co/media/interface/logo.svg).

We had no idea we could use a svg as favicon! Will look into it :) Thanks


x/mint: refactor, document and unit test keeper's DistributeMintedCoin

Background
This is a follow-up to #1839
DistributeMintedCoin does too many things and violates the separation of concerns. It should be refactored to focus on one thing and potentially call other methods.
Suggested Design

Distributing developer rewards has its own method that is unit tested
Distributing staking incentives, pool incentives and community pool incentives can be refactored into a single reusable method and unit tested

Acceptance Criteria

the suggested refactor is complete to extract 2 functions:

For developer rewards distribution
Reusable function for distributing staking, pool incentives and community pool rewards.

the newly extracted methods are fully covered by unit tests
other tests continue to pass

Marking this as blocked by #1915.
This is better be done after the existing tests are understood and refactored


Misspelling & Gist (?)

You've got a misspelling in the github project description.
Also, this would be a good start for gists. cl-gist has been abandoned. Any plans for gists?

@snunez1 Just fix the misspelling in the description. Nice catch.
Also, I even don't use gist a lot. But it sounds like a good start to a new project. Let me check what cl-gist was doing.

I give the keyword :content to the github-api-call method to send the body through API. It can use to gist.


Channel closed after some file change

Issue description
I have an express server setup, every time that I made a change to some file and some endpoint is called it throws the following error:
Error [ERR_IPC_CHANNEL_CLOSED]: Channel closed
    at new NodeError (node:internal/errors:329:5)
    at process.target.send (node:internal/child_process:724:16)
    at Object.exports.send (/Users/willianferreira/Projects/CargOn/microservices/extratta-api/node_modules/ts-node-dev/lib/ipc.js:17:14)
    at /Users/willianferreira/Projects/CargOn/microservices/extratta-api/node_modules/ts-node-dev/lib/wrap.js:88:9
    at Object.nodeDevHook [as .js] (/Users/willianferreira/Projects/CargOn/microservices/extratta-api/node_modules/ts-node-dev/lib/hook.js:61:17)
    at Module.load (node:internal/modules/cjs/loader:972:32)
    at Function.Module._load (node:internal/modules/cjs/loader:813:14)
    at Module.require (node:internal/modules/cjs/loader:996:19)
    at require (node:internal/modules/cjs/helpers:92:18)
    at Object.getCodec (/Users/willianferreira/Projects/CargOn/microservices/extratta-api/node_modules/iconv-lite/lib/index.js:65:27)

Context
Running the server with ts-node-dev --transpile-only src/index.ts
OS version (is it docker or host?), ts-node-dev version
macOS Big Sur 11.2.3
ts-node-dev ^1.1.6
Did you try to run with ts-node?
Yes.
Did you try to run with --files option enabled?
Yes.
Did you try to run with --debug option enabled?
Yes, the output with it:
[INFO] 08:16:01 Restarting: /Users/willianferreira/Projects/CargOn/microservices/extratta-api/src/services/SendExtratta.ts has been modified
[DEBUG] 08:16:01 /Users/willianferreira/Projects/CargOn/microservices/extratta-api/src/services/SendExtratta.ts compiled in 20 ms
[DEBUG] 08:16:01 Removing all watchers from files
[DEBUG] 08:16:01 Child is still running, restart upon exit
[DEBUG] 08:16:01 Disconnecting from child
[DEBUG] 08:16:01 Sending SIGTERM kill to child pid 9162

Do you have a repro example (git repo) with simple steps to reproduce your problem?
No.

I find out that prisma was the problem and solved the issue adding the following, into my entry file.
process.on('SIGTERM', () => {
  process.exit();
});

Thanks @willianhf! I've had exactly the same problem and your solution definitely improved my workflow 🙂 🙌


Support AutoML

It seems that AutoML is currently not supported. Any roadmap on this? :)
Reference: https://cloud.google.com/bigquery/docs/reference/standard-sql/bigqueryml-syntax-create-automl

Hello,
We haven't have a plan to support AutoML yet. Could you share some context of your use case? We are happy to add those in to bigframes.


Remove top timestamp

⚠ This repo is Continuously Deployed: make sure you follow the guidance ⚠
What
Removal of timestamp at the top of each guidance page: Taking out the ‘Last updated’ information below the guidance title –while the timestamp information remains at the bottom of each guidance page.
Why
User research has shown that users of the Service Manual are irritated and trusting guidance less if it has an old timestamp. It distracts from useful and potentially recently reviewed but unchanged guidance. The timestamp information remains available to users at the bottom of each page. Further details can be found in this user research findings document.
Visual Changes
Removal of ‘last updated’ information on top of the page – no other visual changes.

Thanks for your valuable suggestion! I’ve now added a link to the user research findings document.


issue with CosmeticBullet freezing in place after firing (FastCast)

this happens most of the time I'm firing.

fixed with latest commit bf47ee9


(interpreter) Fix integer expansions to bigint

While working on #225, I discovered that some semantics here was essentially broken. The exponential operator only worked properly with int + int or bigint + int operands. When one of the operands was a float, it was impossible to assign the result to a variable.
$ perlang
Perlang Interactive REPL Console (0.1.0-dev.181, built from git commit 9480f21)
> var v = 2 ** 3.5
[line unknown] Unsupported target type System.Numerics.BigInteger

For reference, the semantics after this MR got merged was insane:
Perlang Interactive REPL Console (0.1.0-dev.186, built from git commit 94fe2ca)
> var v1 = 2 ** 3.5
> var v2 = 2 ** 3.1
> v1.get_type()
System.Numerics.BigInteger
> v2.get_type()
System.Numerics.BigInteger
> 2 ** 3.5
11.313708498984761
> 2 ** 3.1
8.574187700290345

(Using a BigInteger type but containing a double value?!?)
This was corrected in #237:
Perlang Interactive REPL Console (0.1.0-dev.190, built from git commit 3dda89d)
> var v1 = 2 ** 3.5
> var v2 = 2 ** 3.1
> v1.get_type()
System.Double
> v2.get_type()
System.Double


Documentation search bug

Go to http://www.yiiframework.com/doc-2.0/index.html and search for "sort" or "Sort". There will be no results.
"sor" and "sorti" works.

Another example: typing "mult" lists a lot of pages including for example:

Abstract Class yii\web\MultiFieldSession
Getting Data for Multiple Models
Database Access Objects (probably because of this paragraph: "Tip: You can configure multiple DB application components if your application needs to access multiple databases.")

Typing "multi" (just adding the "i") produces only one result:

Class yii\sphinx\ColumnSchema

Reproduced, This is because the search does not do auto extension of terms when an exact term is matched.


Improve usability

We should make life easy from people coming from pandas, spark, R, etc. the usage of the framework.
I'm not saying lets copy the name, but I think some or them are too large o maybe confusing.

from @argenisleon
Right now to print a hist the user must:
priceDf = analyzer.get_data_frame.select("price") #or df.select("price")
hist_dictPri = analyzer.get_numerical_hist(df_one_col=priceDf, num_bars=10)
analyzer.plot_hist(df_one_col=priceDf, hist_dict= hist_dictPri, type_hist='categorical')

I think that we must simplify the function to:
analyzer.plot_hist(df, column, bins, type_hist='categorical')


Documentation: What is an Int?

I've been unable to determine what is representable in a value of type Int in Elm.
This page seems to suggest that Int is a 32bit two's complement integer http://learnyouanelm.github.io/pages/03-types.html
Playing around in the REPL suggests that Int is actually represented as a double precision float. 2^53 is the largest value such that every positive integer below it is representable.

Also, the usual weird JavaScript hacks exist if you are concerned about precision. I'm making use of this in intdict, requiring the user to make sure they are actually passing valid integers (yuck!).
Perhaps something like this is worthwhile to have in core?

Because Elm targets JavaScript, there are certain problems with integers that we cannot fix without very severe performance costs. An Elm Int should be a 32-bit integer, but there is no such thing in JavaScript. So you can think of this as the compiler being non-compliant. The problem is that compliance is basically impossible until we are targeting WebAssembly directly, or some other platform.
Does that answer your question? Also, I don't know where this should be documented. If someone can find a nice place, maybe it makes sense to do.

Would it be possible to keep this issue open until this information finds a place in the documentation?

This sounds like a good addition to faq.elm-community.org


Make flush interval in telemetry configurable via sidecar

Environment variables read via environ when sidecar is spawned are not necessarily available (see https://gist.github.com/cataphract/78ca7cabdded79360d790a8bc249e93d ). Add telemetry flush interval as a session config entry instead.

Codecov Report
Attention: Patch coverage is 0% with 3 lines in your changes missing coverage. Please review.

Project coverage is 70.24%. Comparing base (54708da) to head (b350c8a).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #527      +/-   ##
==========================================
- Coverage   70.25%   70.24%   -0.01%
==========================================
  Files         206      206
  Lines       27823    27826       +3
==========================================
  Hits        19546    19546
- Misses       8277     8280       +3

Components
Coverage Δ

crashtracker
16.86% <ø> (ø)

datadog-alloc
98.73% <ø> (ø)

data-pipeline
51.15% <ø> (ø)

data-pipeline-ffi
0.00% <ø> (ø)

ddcommon
86.68% <ø> (ø)

ddcommon-ffi
75.31% <ø> (ø)

ddtelemetry
59.02% <ø> (ø)

ipc
84.13% <ø> (ø)

profiling
78.68% <ø> (ø)

profiling-ffi
58.26% <ø> (ø)

serverless
0.00% <ø> (ø)

sidecar
35.66% <0.00%> (-0.03%)
:arrow_down:

sidecar-ffi
0.00% <0.00%> (ø)

spawn-worker
54.98% <ø> (ø)

trace-mini-agent
70.93% <ø> (ø)

trace-normalization
98.24% <ø> (ø)

trace-obfuscation
95.73% <ø> (ø)

trace-protobuf
77.16% <ø> (ø)

trace-utils
89.91% <ø> (ø)


Fix Division By Zero Warning for Focal Length

If a file has invalid EXIF data, it can cause an division by zero warning to occur.

Hi Jay,
Thanks for your PR. Can you please provide a unit test for this?

I've added a unit test, but whenever I try to run any tests, I get a notice No tests executed!, so I'm unsure how to fully test my test.

You should specify the configuration file to be used. In travis, it works like this:
php vendor/bin/phpunit -c phpunit.xml.dist

Thanks, Tom. I was able to run the unit tests, and can confirm that it works properly.

Thanks Jay, will merge & release!


Manually merge main into next

This reverts https://github.com/apple/swift/pull/39780 and then re-merges so that history is easier to see in a git blame.

Late LGTM 👍


Dev Containers Fail to Start with Podman in VS Code 1.95.0 (Works in 1.94.0)

Does this issue occur when all extensions are disabled?: No
This issue is related to an extension that cannot be disabled.

VS Code Version: 1.95.0
OS Version: Windows 11 22H2

Steps to Reproduce:

Open VS Code.
Attempt to start a Dev Container for the workspace located at c:\Users\night\code\evm\reth.
Observe the output logs, which indicate that the Dev Container fails to start and remains stuck at a specific step.

Expected Behavior:
Dev Containers should successfully start and connect to the container environment using Podman.
Actual Behavior:
Dev Containers consistently attempt to start using Podman within WSL, but the process does not progress beyond the initial steps. The output logs show that the startup process is stuck.
Devcontainer Configuration:
// devcontainer settings
"dev.containers.dockerPath": "podman",
"dev.containers.dockerComposePath": "podman-compose",
"dev.containers.forwardWSLServices": false,
"dev.containers.defaultFeatures": {

},
"dev.containers.dockerSocketPath": "npipe://\\\\.\\pipe\\podman-machine-1",
"dev.containers.experimentalLockfile": true,
"dev.containers.logLevel": "trace",

Logs:
[31 ms] Dev Containers 0.388.0 in VS Code 1.95.0 (912bb683695358a54ae0c670461738984cbb5b95).
[31 ms] Start: Resolving Remote
[41 ms] Setting up container for folder or workspace: c:\Users\night\code\evm\reth
[43 ms] Start: Run: wsl -l -v
[91 ms] Start: Run: wsl -d Ubuntu-20.04 -e /bin/sh -c echo ~
[1792 ms] Start: Run: wsl -d Ubuntu-20.04 -e /bin/sh -c cd '/root' && /bin/sh
[1807 ms] Start: Run in host: id -un
[1856 ms] root
[1856 ms]
[1857 ms] Start: Run in host:  (command -v getent >/dev/null 2>&1 && getent passwd 'root' || grep -E '^root|^[^:]*:[^:]*:root:' /etc/passwd || true)
[1859 ms] Start: Run in host: echo ~
[1859 ms] /root
[1859 ms]
[1860 ms] Start: Run in host: test -f '/root/.vscode-server/cli/servers/Stable-912bb683695358a54ae0c670461738984cbb5b95/server/node'
[1861 ms]
[1861 ms]
[1861 ms] Exit code 1
[1861 ms] Start: Run in host: test -f '/root/.vscode/cli/servers/Stable-912bb683695358a54ae0c670461738984cbb5b95/server/node'
[1862 ms]
[1862 ms]
[1862 ms] Exit code 1
[1862 ms] Start: Run in host: test -f '/root/.vscode-server/bin/912bb683695358a54ae0c670461738984cbb5b95/node'
[1863 ms]
[1863 ms]
[1863 ms] Exit code 1
[1863 ms] Start: Run in host: test -f '/root/.vscode-remote-containers/bin/912bb683695358a54ae0c670461738984cbb5b95/node'
[1865 ms]
[1865 ms]
[1865 ms] Start: Run in host: test -f '/root/.vscode-remote-containers/bin/912bb683695358a54ae0c670461738984cbb5b95/node_modules/node-pty/package.json'
[1866 ms]
[1866 ms]
[1866 ms] Start: Run in host: test -f '/root/.vscode-remote-containers/dist/vscode-remote-containers-server-0.388.0.js'
[1867 ms]
[1867 ms]
[1869 ms] userEnvProbe: loginInteractiveShell (default)
[1869 ms] userEnvProbe: not found in cache
[1869 ms] userEnvProbe shell: /usr/bin/zsh
[2071 ms] userEnvProbe PATHs:
Probe:     '/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/lib/wsl/lib'
Container: None
[2076 ms] Start: Run in Host: wslpath -w /run/user/0/wayland-0
[2078 ms] Start: Check Docker is running
[2078 ms] Start: Run: docker version

Additional Information:

WSL Version: Ubuntu 20.04
VS Code Version 1.94: The same configuration worked correctly in VS Code version 1.94.

The log shows docker version being run last. I would expect this to be podman version. Could you double-check if podman is indeed in your user settings?
The log also doesn't show trace output, something seems off with the settings.


[BUG] Get Raw File With dot  return  file not found

here should use  pathEscape to parse . to %2E
not so some filename(most of normally) with . will return file not found
gitlab doc
#1074

No need to create an issue if you already created a PR 👍🏻


Updating the server1 cert so that it can be used with Go.

The encoding of the issuer field in this cert is now a PRINTABLESTRING
as opposed to UTF8STRING in the previous server1.pem which was causing
the Go issue.
Fixes #4086.

@carl-mastrangelo The go interop tests are failing. Is that expected?

The change itself looks alright, but we need to resolve the interop test failure before merging this.

@jboeuf You probably also need to update the grpc-go certs to before this will pass.  (though, I don't have anything against submitting it).
They should be https://github.com/grpc/grpc-go/tree/master/interop/server/testdata and https://github.com/grpc/grpc-go/tree/master/interop/client/testdata

I am definitely against committing anything that will introduce new breakages. If you update the go cert first, will we prevent breaking the interop tests by this PR? If so, we should do that.
Please note that it is possible to change both changes (to this repo and to the go repo) at the same time by running the interop tests locally.

@jtattermusch the two certs between repos are mutually incompatible (this is why grpc-go uses its own root CA).  Making the change in both repos and running the test seems fine.  That said, it still seems like there will be a brief window O(~seconds) where the test would fail if rerun from a new PR.

that sounds alright. Just wanted to point out we need to coordinate both
pull requests appropriately to make the transition as short as possible
On Nov 10, 2015 6:59 PM, "Carl Mastrangelo"<EMAIL_ADDRESS>wrote:

@jtattermusch https://github.com/jtattermusch the two certs between
repos are mutually incompatible (this is why grpc-go uses its own root CA).
Making the change in both repos and running the test seems fine. That said,
it still seems like there will be a brief window O(~seconds) where the test
would fail if rerun from a new PR.
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/4096#issuecomment-155531707.


JSON path for current selection

Could we add the current JSON selector for the current caret/cursor/selection position? Meaning
some_item: [
    {
        id: 1,
        something: something,
        url: https://www.some/url/here.com
    },
    {
        id: 2,
        something: something,
        url: https://www.some/url/here.com
    },
    {
        id: 3,
        something: something,
        url: https://www.some/url/here.com
    },
    {
        id: 4,
        something: something,
        url: https://www.some/url/here.com
    }
]

if my caret/selection was over the url property in the object with id # 2 then some indicator (maybe at the top or bottom of the screen) shows the current json selector for that element (some_item[1].url)

That's a good idea

Yes please, can we get this?

Main thing I miss from old JSONView is the ability to see the path in the status bar, and easily copy the path or value via right-click.
I now switch between using JSON Formatter and JSON Viewer, but far as I can tell neither offer that old beloved feature. Would love to see it in JSON Viewer!

Hi @alahosky, I like this feature as well, bear with me :)
Right now I'm trying to fix all bugs and corner cases but I keep improving the extension and adding new features from time to time.

This would be great, indeed!
Currently my workaround for this is to paste the JSON in VS Code and get the path via JSONPath plugin, but that is unnecessarily tedious. :(

Beside show and copy the path, I really want to copy the value (useful in long json document).


Limit the number of transactions for submit_all

atm, user can submit a huge list of transactions and potentially use up all the memory on the peer bringing the peer down. We should add a hard-coded limit (no need to make it a configuration parameter, yet) for this

There should be a limit over transactions.

the limit should be placed on server side on the endpoint that receives transactions

somewhat related is #4944


Chat - Hidden is not shown when starting new chat with a user without previous conversation

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.21-1
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:

Search for a public domain user that you have never chatted before
Observe the name when the conversation is opened

Expected Result:
Hidden should be shown as the name and on LHN
Actual Result:
Hidden is not shown but email is shown
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[x] Android: mWeb Chrome
[ ] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/93399543/3c1c0232-dce4-48cb-ae37-f2901cc9f5b7
View all open jobs on GitHub

Not reproduced on Production
https://github.com/Expensify/App/assets/93399543/b13ca058-b752-414e-9bdd-f817adcac13a

I'm unable to reproduce this on staging v1.4.21-1 in MacOS Chrome. @kbecciv can you confirm this is reproducible on staging?
https://github.com/Expensify/App/assets/16747822/41108fae-019a-4d5e-b440-a64e4878aed4

I can reproduce on staging v1.4.21-1
https://github.com/Expensify/App/assets/93399543/2f6bb29b-bce3-4cce-950c-3962a43d1c47

Weird, ok! I'll continue to dig into it

Couldn't reproduce in dev & staging either 🤔

Seems like this might be tied to https://github.com/Expensify/App/issues/32613? @puneetlath do you know of anything that went to staging recently that might be causing this?

I think you're likely able to see that user's personal details because you were the one that invited them @kbecciv.

We did make some back-end changes, but I don't think this is a bug.

Sounds good, removing the blocker label then. Thanks @puneetlath!

@kbecciv was this bug a result of a regression test? I think we might need to update the test as the scenario here, the user should actually "know" the other user and thus not see "hidden".

@puneetlath  Hello
https://expensify.testrail.io/index.php?/tests/view/4151387

@puneetlath Correct, the bug a result of a regression test -, please attach TR https://expensify.testrail.io/index.php?/tests/view/4151387

@lanitochka17 @kbecciv can we just remove that test? It's no longer relevant with the changes we're making.

Bumped Maria bout removing the test here: https://expensify.slack.com/archives/C9YU7BX5M/p1707322780645939

Deleted the TC (https://expensify.testrail.io/index.php?/cases/view/2778068) that covered this flow.

Thanks @isagoico!


On Unix, only explicitly terminate the native process if not in background

PR Summary
A change was introduced in 7.2-preview.6 to explicitly terminate unix processes so they weren't orphaned, however, it killed all processes including ones that should be running in the background.  The fix is to check to make sure the process isn't in the background before performing the cleanup.
PR Context
Fix https://github.com/PowerShell/PowerShell/issues/18181
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:

[ ] Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
(which runs in a different PS Host).

[ ] Issue filed:

[ ] Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.

[ ] Issue filed:

[ ] Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).

[ ] Issue filed:

[ ] Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

[ ] Issue filed:

/backport to release/v7.2.7

/backport to release/v7.3.0-rc.1


Grommet.io Anchor page bug

The grommet.io anchor page is currently displaying a render blocking error. Cannot read property 'map' of undefined. I pulled the latest master branch and don't see the issue locally and I'm not able to infer much from the heroku branch as when I run this locally it forwards me to the grommet.io url.

The anchor doc code hasn't been changed for quite some time so I'm assuming this is a react-desc bug.

I will check this later today. Thanks for reporting it

On Jul 29, 2017, at 9:54 AM, Alex Mejias<EMAIL_ADDRESS>wrote:
The grommet.io anchor page is currently displaying a render blocking error. Cannot read property 'map' of undefined. I pulled the latest master branch and don't see the issue locally.
The anchor doc code hasn't been changed for quite some time so I'm assuming this is a react-desc bug.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I've fixed it. it was indeed a problem with react-desc


[Bug] because of a simple dateparse error, the provider does not work with serverless Elastic flavor

Error: parsing time "2023-10-31" as "2006-01-02T15:04:05Z07:00": cannot parse "" as "T"
Cause: Obviously, when connecting, the provider first does an API call on the root /, and then want to parse the responded field version.build_date. E.g. this response:
{
  "name" : "serverless",
  "cluster_name" : "foo",
  "cluster_uuid" : "bar",
  "version" : {
    "number" : "8.11.0",
    "build_flavor" : "serverless",
    "build_type" : "docker",
    "build_hash" : "00000000",
    "build_date" : "2023-10-31",
    "build_snapshot" : false,
    "lucene_version" : "9.7.0",
    "minimum_wire_compatibility_version" : "8.11.0",
    "minimum_index_compatibility_version" : "8.11.0"
  },
  "tagline" : "You Know, for Search"
}

But 2023-10-31 does not look like the expected format. A real Elasticsearch responds for example this:
"build_date": "2022-12-05T18:22:22.226119656Z",
Just because of this simple error, the whole (?) provider doesn't not work. Tried with component template and index template resource, and used the example code from documentation.

Thanks for reporting this @ck-ntt. This will be fixed in 0.11.3 which will be released shortly


Compatibility with Gensim 4.0.0?

Gensim has been updated to a new major version (4.0.0), but DaNLP is tied to an older version of Gensim (3.8); is it possible to update to a later version or do you expect it to be incompatible in some manner?
Tried updating with pip and running load_wv_with_gensim (using the test code) and this seemed to work with 4.0.0. Any reason to suspect 4.0.0 isn't properly supported?

Thanks for notifying us about the new version.
Currently, we cannot upgrade Gensim to 4.0.0 because it is a dependency for flair which only allows versions up to 3.8.3.


Create CLI

Create a command line interface with click

I just realized the CLI does not make sense. This is an asynchronous library.
Changing issue to Nuke CLI.


[mesheryctl] Context parameter to control service type deployed

Current Behavior
Currently meshery when deployed in kubernetes, is deployed as service type NodePort by default.
Desired Behavior
Moving forward, the service type needs to be dynamically configured based on the user's preference, adding a context paramter called serviceType would suffice this need.

Host OS: Mac Linux Windows
Meshery Version: all
Platform: Kubernetes

Implementation

Add a context parameter to support different service types.
Change the service type in the manifest, based on the context parameter value.

Contributor Resources

mesheryctl Contributing Guide
Beginner's guide to contributing to Meshery and mesheryctl
mesheryctl Command Tracker
Meshery CLI Commands and Documentation
Layer5 Community Slack

@abhishekkumkar A few clarifications regarding the issue

What should be the command for this?
By manifest, do you mean ~/.meshery/manifests/meshery-service.yaml?

@navendu-pottekkat Will you help @vineethvanga18  with the docs explaining what context is?

@vineethvanga18 The config.yaml will be modified to accommodate this. i.e Viper should properly read this config and get the serviceType parameter.
Then, as you mentioned, we should rewrite the manifest file to reflect this change.
system context create should have a flag which allows users to set this value. The default value should be decided if the user does not specify a value.
@abhishekkumkar one question I have here is that this parameter is redundant for docker platform right? How should we handle that? It might be confusing for the user.
// @leecalcote

@hexxdump @piyushsingariya @panyuenlau do you consider that this is needed?

@hexxdump @piyushsingariya @panyuenlau do you consider that this is needed?

We always need a NodePort to access meshery out-of-cluster in k8s. Not sure why this issue was created?

@piyushsingariya Not necessarily, it could be a LoadBalancer which is the current default service type. We could definitely add a configuration here in the meshconfig. We should plan which command would handle modifying this. Should it be a system command or should it be a sub-command for context? We should give it some thought on how to proceed if we decide we are proceeding with this.

@piyushsingariya @hexxdump Did we reach a consensus on whether or not to add this feature?

Did we reach a consensus on whether or not to add this feature?

The discussion was still on-going, maybe we should discuss this in the next dev meeting to grab attention from more people and we might get more views on this.


Affichage des bornes prises en compte

Il serait intéressant de pouvoir voir les bornes prises en compte dans le calcul pour l'utilisateur. L'idée serait de pouvoir afficher simplement un point, avec une couleur par groupe de puissance (Low / Standard / Fast / Very Fast).
Pour des raisons de performance, il sera certainement obligatoire d'afficher ces points qu'à partir d'un certain zoom.

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
ccmlm, @ColdDevil, @dingguijin, @krgko, @byjpr, @Keiko-Home, @denisse-dev, @cloutprotocol, @cypersii, @Dsummers91, @Doko-Demo-Doa, @mikedemarais, @5pecia1, @scottpaul99, @MSA-brother, @esp10mm, @henriquepagoto, @jakerockland, @8times4, @mirgj


[SPARK-38412][SS] Fix the swapped sequence of from and to in StateSchemaCompatibilityChecker

What changes were proposed in this pull request?
This PR fixes the StateSchemaCompatibilityChecker which mistakenly swapped from (should be provided schema) and to (should be existing schema).
Why are the changes needed?
The bug mistakenly allows the case where it should not be allowed, and disallows the case where it should be allowed.
That allows nullable column to be stored into non-nullable column, which should be prohibited. This is less likely making runtime problem since state schema is conceptual one and row can be stored even not respecting the state schema.
The opposite case is worse, that disallows non-nullable column to be stored into nullable column, which should be allowed. Spark fails the query for this case.
Does this PR introduce any user-facing change?
Yes, after the fix, storing non-nullable column into nullable column for state will be allowed, which should have been allowed.
How was this patch tested?
Modified UTs.

cc. @cloud-fan @viirya @tdas @zsxwing @xuanyuanking

Test passed. Merging to master.

Merged into master/3.2/3.1.


Support InputStream and OutputStream

It would be nice if .setInput(...) and .addOutput(...) were able to take an InputStream and OutputStream. For applications that need to do conversions on the fly dealing with actual files is a pain.

Yup, would be nice. Dup of #16


Scenarios don't work

 Issue by maforget
Friday Dec 23, 2016 at 00:18 GMT
Originally opened as https://github.com/CQUI-Org/cqui/issues/186

Pretty much self explanatory, there are no way to select production when playing one of the 2 new scenarios (Viking & Poland) with the mod.
The other multi player scenarios seems to work fine.

 Comment by chaorace
Monday Feb 27, 2017 at 05:45 GMT

See also: CTD using "Enhanced" keymap option in Australia scenario (maybe this affects the other scenarios too?)

 Comment by bestekov
Monday Feb 27, 2017 at 18:19 GMT

My off the cuff suspicion on this one is that the production cleanup mod that reorganizing the production list probably breaks when the collection of production items diverges from vanilla civ. Simple kludgy solution might be to wrap that whole functionality in an if block that checks for whether the game is in a scenario (if that is accessible information) and just turns off the prod panel reorganization in scenarios.

 Comment by chaorace
Wednesday Mar 01, 2017 at 00:41 GMT

@bestekov Boy, uh, that's not how any of the production panel code works. It was already spaghetti before some 6-7 different modders had a chance to really scramble things up back there. To be honest here: ProductionPanel.lua is going to need a full rewrite if we want to even begin debugging what's going on in this issue

 Comment by bolbass
Saturday Jun 24, 2017 at 06:33 GMT

Possible spy check in scenarios problem on civfanatics.

So... any advance on a resolution for this?


JavaScript size improvements

In order to minify a bit the js size of each js plugin , does it seems valid to use a global subtractive approach on the following?
 static _jQueryInterface(config) { ....

if (typeof $ !== 'undefined') {
  const JQUERY_NO_CONFLICT = $.fn[NAME]
  $.fn[NAME] = Popover._jQueryInterface
  $.fn[NAME].Constructor = Popover
  $.fn[NAME].noConflict = () => {
    $.fn[NAME] = JQUERY_NO_CONFLICT
    return Popover._jQueryInterface
  }
}

[data-dismiss="{class}"]

And final show , hide and toggle functions maybe can be used in a generic way, handling by default the appropriate events, aria-hidden, 'show' class and give access to specific functionality , with the use of callbacks

Hi @GeoSot,
Not sure if I understand totally what you mean, but feel free to create a PR to demonstrate what you mean

Closing as stale. Good news is we did shave ~5-6 off our JS in v4.5.0!


Client appears to forget or lose track of it's job status polling.

After submitting a job when on the "job running" page the client starts polling mblast every x seconds for status updates.  However, when the client leaves that page, the polling continues in the background until a full page refresh.
Additionally, if the client navigates back to that waiting page, an additional repeating poll is started, causing multiple requests to be fired every x seconds for the status.

To fix, the "job polling promise" should be canceled if the component which initialized it is unmounted.


Upload files to PyPi show 'SignatureDoesNotMatch' errors

This GH action worked fine in the past (last file published April 5), but current uploads show the 'SignatureDoesNotMatch' for the uploaded files. My PyPi Secrets hasn't changed since the last time I published a release.
Didn't notice any discernable errors in the gh action logs, but here's the tail of the build & publish log.
Installing the current project: metron-tagger (1.2.6)
Building metron-tagger (1.2.6)
  - Building sdist
  - Built metron-tagger-1.2.6.tar.gz
  - Building wheel
  - Built metron_tagger-1.2.6-py3-none-any.whl
No suitable keyring backends were found
Using a plaintext file to store and retrieve credentials

No suitable keyring backends were found
Publishing metron-tagger (1.2.6) to PyPI
Using a plaintext file to store and retrieve credentials
 - Uploading metron-tagger-1.2.6.tar.gz 0%
 - Uploading metron-tagger-1.2.6.tar.gz 21%
 - Uploading metron-tagger-1.2.6.tar.gz 100%

 - Uploading metron-tagger-1.2.6.tar.gz 100% - Uploading metron_tagger-1.2.6-py3-none-any.whl 0%
 - Uploading metron_tagger-1.2.6-py3-none-any.whl 100%

 - Uploading metron_tagger-1.2.6-py3-none-any.whl 100%

Can you please try to specify the action version to v1.10 if you are using latest, so I can be sure that the previous version was working for you and the problem is in the current one?

First time I tried to publish was with v1.9 (which is what I used in April) & then I tried again with v1.11, both had the same result.

This may be a PyPi issue: https://github.com/pypa/warehouse/issues/11500

Most likely yes, since the version v1.9 of the action definitely wasn't changed since you last time used it.  Closing this issue, since it is no relevant for this repo. Hope it will be solved soon! :)


Failed to parse config

Attempting to set this linter up for my project but running into the following error
$ ./node_modules/.bin/svglint  --debug src/assets/icons/*.svg
-------------------------------------------------------- Log --------------------------------------------------------
(x) (node:33848) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension.
(Use `node --trace-warnings ...` to show where the warning was created)
(x) Failed to parse config: /Users/<redacted>/.svglintrc.js:1
export default {
^^^^^^

SyntaxError: Unexpected token 'export'
    at wrapSafe (internal/modules/cjs/loader.js:1001:16)
    at Module._compile (internal/modules/cjs/loader.js:1049:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
    at Module.load (internal/modules/cjs/loader.js:950:32)
    at Function.Module._load (internal/modules/cjs/loader.js:790:12)
    at ModuleWrap.<anonymous> (internal/modules/esm/translators.js:199:29)
    at ModuleJob.run (internal/modules/esm/module_job.js:183:25)
    at async Loader.import (internal/modules/esm/loader.js:178:24)
    at async file:///Users/<redacted>/node_modules/svglint/bin/cli.js:65:28

I've got a .svglintrc.js file with the following:
export default {
  rules: {
    attr: {
      width: true,
      height: true,
    }
  }
}

Using node 14.18.1 on MacOS 12.1
Am I using it wrong?

Interestingly, if i try it with the following config
module.exports = {
  rules: {
    attr: {
      width: true,
      height: true
    }
  }
};

it just crashes without any output
$ ./node_modules/.bin/svglint  --debug src/assets/icons/*.svg
$ echo $?
1

It looks like the "silent failure" issue doesn't have to do with a single file, but rather with a large number of files (ie, lots of output, with failures) and not using --ci. So, i guess, something stemming from the GUI#update method.
I'm using MacOS 12.1 on iTerm2 + zsh
Note, when i run the testing files you posted above, i get truncated output:

Maybe related to detecting terminal width.. if i stretch my terminal open wider i get:

(ignore the <aws:org-sso> piece that's RPROMPT stuff)

In the meantime, how should I structure my config such that it checks for width and height on <svg> tags only? I'm seeing something about a "rule::selector" rule, but it's not clear how that should be used.

The "rule::selector" rule is indeed what you want. You need to set it to a query selector of the elements for which the rule should hold, so in your case the following should work:
// testing/.svglintrc.js// testing/.svglintrc.js

module.exports = {
  rules: {
    attr: {
      width: true,
      height: true,
      "rule::selector": "svg"
    }
  }
};

It looks like the "silent failure" [(with exit code 1)] issue doesn't have to do with a single file, but rather with a large number of files (ie, lots of output, with failures) and not using --ci. So, i guess, something stemming from the GUI#update method.
I'm using MacOS 12.1 on iTerm2 + zsh
Note, when i run the testing files you posted above, i get truncated output - probably related to the same issue:

At this point I'm going to assume the "truncated output" and "silent failure" are related problems for simplicity, we'll find out if that's the case down the line :slightly_smiling_face:
I have now tested this on

Ubuntu 20.04 with Zsh in default terminal application - no issue
Windows 10 in Powershell in the new Windows terminal - no issue
MacOS 12.1 with Zsh in the default terminal application - same issue!!

Maybe related to detecting terminal width.. if i stretch my terminal open wider i get:

I tested this as well, the terminal width doesn't influence whether or not the output is truncated for me, instead it looks something like:
-------------- Files --------------
x a.svg
  x attr 0:0 Expected attribute 'w
             idth', didn't find it
               At node <svg> (0:0)
  x attr 0:0 Expected attribute 'h
             eight', didn't find i
             t
               At node <svg> (0:0)

------------- Summary -------------
x 1 invalid files.

On the other hand the terminal height does seem to have an effect. With the above setup, if I make the terminal window tall enough there's no truncation. As I make the window shorter the output gets truncated from the top (which matches your findings so far).
Unfortunately, I only have limited access to a Mac so it might be hard for me to work on this. I'd encourage you to look into this yourself if you have time. In the meantime I guess you'd have to default to using the --ci option

For what it's worth, the CLI rendering engine has given problems earlier and is likely due for a proper rewrite. I believe that the update logic I implemented back in the day (which is responsible for repeatedly rendering the GUI when --ci is not set) is poorly done - the --ci flag was added as a cheap workaround for an earlier issue with it.
While I can't comment on the issue reported here, it might be worthwhile to just the GUI implementation entirely.

The "rule::selector" rule is indeed what you want. You need to set it to a query selector of the elements for which the rule should hold, so in your case the following should work:

Thanks - this worked. I swear I had tried this, but I suspect it had gotten mixed up with the truncated output issue and I didn't see the results one would expect. Cheers!
Running with --ci is not an issue for me at all 👍


Params for Mailer (Rails 5.2 ~)

Environment

Ruby 2.6.2
Rails <IP_ADDRESS>
Devise 4.6.1

Current behavior
Since rails 5.2, ActionMailer::Base can use params method to be commonize normal controller. https://edgeguides.rubyonrails.org/action_mailer_basics.html#mailers-are-similar-to-controllers
It is also good for mailer preview to switch locale so I think it would be used in Devise gem as well.
Do we have a plan to implement this ??

Thank you for the issue. The devise mailer will not take advantage of the parameterized mailer because it has many different methods on the mailer that don't share the same parameters. Thank you for the suggestion.

@rafaelfranca why it's not a good idea to make all the mailers in devise to work as parametrized (using with method for the passing parameters into the mailer actions)?

@rafaelfranca I'm needing to access device mailer params in ApplicationMailer on before_action. It sounds like using the new params would be the way to go.

Use case:
class ApplicationMailer < ActionMailer::Base
  before_action :configure_default_url_options

  layout 'mailer'

  private

  def configure_default_url_options
    default_url_options[:host] = params[:user].organization.host
  end

after_action is too late as the template will be rendered with the wrong url options.

@rafaelfranca @carlosantoniodasilva   I'm needing to access devise mailer params in ApplicationMailer on before_action. It sounds like using the new params would be the way to go. The after_action is too late as the template will be rendered with the wrong url options.
Use case:
class ApplicationMailer < ActionMailer::Base
  before_action :configure_default_url_options

  layout 'mailer'

  private

  def configure_default_url_options
    default_url_options[:host] = params[:user].organization.host
  end
end

Is this something we could consider at this point?

@rafaelsales would you be able to specialize the devise_mail method and call super?
e.g. something like this in your mailer:
def devise_mail(record, *args, &block)
  default_url_options[:host] = record.organization.host
  super
end

I haven't looked into mailer params in a while, but iirc they'd require a rework on how all Devise mailers work, so it'd likely be a breaking change and/or one that's difficult to maintain backwards compatibility. But if the above works for you, I think we can call it a day there. :)


Update email template

Description
Updates vpn manager email template as recommended.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

Screenshots
Checklist:

[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

Your reviews @VinneyJ / @kelvinkipruto


Rework build branches

We currently use three branches named master, qa, and live. We want to move to two branches named develop and master. The master branch will become develop, the live branch will become master, and the qa branch will go away entirely.
We will then start building Docker images from both the develop and live branches. The develop images will be tagged with a name like 2.0.115-alpha.1, or perhaps a date and Git SHA like the Language Forge images use (develop-$(date +%Y%m%d)-${{ github.sha }}), and also a moving tag develop so that it's easy to set up a docker-compose entry to automatically use the latest lfmerge:develop tag.
The fieldworks8-{master,qa,live} branches will also be renamed at the same time.

Closing as completed as in #289 and #288


Wide shields showing up for 1 & 2 digit shields at DPR 1

When device pixel ratio (DPR) is > 1, standard width shields are used for 1 and 2 digit route numbers and the wide shield is used for 3 digit route numbers.  Here is DPR 2 for example:

The same area at DPR 1 shows wide shields used for 1 and 2 digit route numbers which should be using the regular width shield:

Safari appears to still be consistently choosing the wrong shield (both 1x and 2x):


[Feature] Adding "Contact us" page

Description
"Contact us" page will add more value to your website, as the clients who are surfing your website will be able to contact you directly.
The "Contact us" page will contain your linkedin, twitter and a text message box using which clients can send you the message directly.
For the text box, I will be using formspree. You can generate your own formspree link and I will add it to the backend, after this you will directly receive all the messages of your clients.
Rest I assure that you will get a good user interface.
Screenshots
No response
Additional Information
No response

Hey @anirudhsalaria if someone wants to get in touch they can join our discord or social handle I don't feel there is need of specific contact us page