chore: bdd-spring-1587812090 to 0.0.1

chore: Promote bdd-spring-1587812090 to version 0.0.1

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

Needs approval from an approver in each of these files:

OWNERS

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


Fix VeriStand and LabVIEW version check for versions later than 2019

Add PXI Linux RT ipk version check support

[x] This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?
Fix #42 to add VeriStand 2019 support to the version check
Add PXI Linux RT ipk version check support
Why should this Pull Request be merged?
VeriStand 2019 does not report versions in the same way as 2018 SP1 and previous. Additionally, installing VeriStand 2019 changes the way that 2018 SP1 and previous report their versions. Because of this, errors reported during a test run always cause the version checking to fail.
This change also allows checking the VeriStand engine version on RT targets with IPK support.
What testing has been done?

Checked to make sure source is in LV 2015
Checked VeriStand regexes against 2018 SP1, 2019, and 2016 with 2019 installed
Checked VeriStand engine regexes against Pharlap RT and Linux IPK versions

[ ] Fix random wire bends

[ ] It's customary to include your RegEx101 URI in your comment. This allows others to play with the regular expression and test variations.


examples

could you explain how wf-rec uses ffmpeg, what the defaults are (ffmpeg or it's own?),
what options are usable, for ex. can it record a lossless x264 video with opus audio?
or basically how to "translate" ffmpeg options I'd use to wf-rec, if applicable at all

wf-recorder uses libav. You can specify video codec at runtime, default_codec at build time and parameter options but audio is currently hard coded to aac here. An option to change audio codec could be added, patches welcome. See the manpage for more information.

The manpage and/or the output of --help is the best place to see what the available options are. I think we leave most of the things for ffmpeg to autodetect, the only thing that we set by default is the codec to use(libx264).


Add a dev tool for viewing and manipulating extension storage.

We keep a significant amount of data in the extension's local "storage".  Much of this data has an impact on the behavior of the extension (i.e. which branch is executed).  During development of the extension, testing, and demos it is sometimes useful to be able to see this data and even change/remove it.
This could be solved with a command-line tool that supports:

dump storage (to stdout or file) (to a specified format, e.g. csv, json)
load storage (from stdin or file)
show storage in tabular format
show one or more entries (specify by key)
modify an entry (specify by key)
remove one or more entries (specify by key)
reset storage

Storage isn't something that users should mess with, so we would make this a dev-only tool.  It would only live in the repo and would not be distributed.

This could be solved with a command-line tool that supports:

Unfortunately This is only available through the VSCode API.
It'll have to be a command in the extension or the like, i.e. not a clip.
You can clear the data by deleting a couple of folders.
Viewing everything isn't possible either, as VSCode doesn't give access to all the data, we can only access the data via the key (i.e
one at a time).
Also this would introduce a maintenance cost, such code would have to be regularly updated when adding new data storage keys...
My suggesting (for debugging purposes) just debug and manipulate the keys. For demo, blow away the folder that stores such data. (Again it's an internal VSCode format).

I agree with the suggestion. @ericsnowcurrently I think we can just add the necessary flags for code-health related items (items just for development purposes).

FYI - VS Code provides a way to view this, use the command Developer: Log Storage Database Contents

For UI tests and demos it may be enough to support overriding storage with a text file (json?) on disk (e.g. in workspace root or extension data dir).

@luabud


:up: Upgrade some dependencies

Upgraded minor versions by re-creating yarn.lock.
Locked typescript to a version that satisfies @typescript-eslint/typescript-estree.
Upgraded to latest version of concurrently.
Added @types/react as dep in aksel-icons to fix this error when trying to build aksel-icons without installing packages for all workspaces: src/ZoomPlusFill.tsx(17,10): error TS7026: JSX element implicitly has type 'any' because no interface 'JSX.IntrinsicElements' exists.

(To replicate this, delete all node_modules, run yarn workspaces focus @navikt/aksel-icons @navikt/ds-tokens @navikt/ds-css @navikt/ds-react @navikt/ds-tailwind @navikt/aksel @navikt/aksel-stylelint and then yarn boot. Fixing this takes us one step further in making it easier to contribute without access to the navikt npm scope in github.)

Upgrade your node version if you get this error when running playwright: The "parentURL" argument must be of type string or an instance of URL

Works on my machine 🚀 Since we are slowly upgrading to only work with the latest node version, should we specify engine in root package.json? https://docs.npmjs.com/cli/v10/configuring-npm/package-json#engines

Does that do anything though, or is it just for info? I'm afraid we're going to forget that it's there 😅


Server rendering with Material-UI v1.x

I recently upgraded Material-UI from 0.18.7 to 1.4.1. This broke the server rendering.
Previously, styles where inlined in the server-side generated HTML, providing a smooth user experience. Now, the styles are gone. Ouch. Materiaul-UI doc provides insights on how server rendering should be done. In particular, server side rendering should use sheetsRegistry and JssProvider.
With old version of Material-UI, react_on_rails made server rendering activation super-easy. As simple as setting a boolean to true! Now with latest version of Material-UI, it seems quite complex and I find myself browsing react_on_rails code, wondering if I'm not doing it wrong: use railsContext to activate JssProvider? Something else?
As react_on_rails + Material-UI look like a classic duo, is there a simple way of handling this?

Awesome! Will give it a try and probably publish a sample Rails app to illustrate the react_on_rails and Material-UI combo. Thank you!

So you want to use Material-UI with react_on_rails and Google led you here?

With server rendering
Simply setting prerender to true doesn't work because you don't get the CSS. So the rendered HTML is pretty ugly.
As suggested by @justin808 above, the solution is to use react_component_hash, so you can produce the HTML and CSS in a unique place and use them later.
In your view:
<= app = react_component_hash("RenderableApp", prerender: true) %>
<style>
  <%= app['componentCss'] %>
</style>
<%= app['componentHtml'] %>

RenderableApp is a container for the original App component. It takes the context (server vs client) into account:
const RenderableApp = (props, _railsContext) => {
  if (_railsContext.serverSide) {
    // SheetsRegistry? JssProvider?
    // See https://material-ui.com/guides/server-rendering/#handling-the-request

    const sheetsRegistry = new SheetsRegistry();
    const sheetsManager = new Map();
    const generateClassName = createGenerateClassName();

    const componentHtml = renderToString(
      <JssProvider registry={sheetsRegistry} generateClassName={generateClassName}>
        <App/>
      </JssProvider>
    );

    const renderedHtml = {
      componentHtml,
      componentCss: sheetsRegistry.toString(),
    };
    return { renderedHtml };
  }
  else {
    // See https://material-ui.com/guides/server-rendering/#the-client-side
    return (
      <App/>
    )
  }
}

@phbernard Please feel free to submit a doc pr to add this info to some file in the /docs directory.
Thank you for your help!


Add realization for updating version of derived segments in Materiali…

Some function has not been realized in MaterializedViewSupervisor.checkSegments. Check the comment: 2) version of derived segments isn't the max(created_date) of all base segments
So add realization for it：
update version of derived segments if isn't the max (created_date) of all base segments.And prevent exception of  "user supplied segments list did not match with segments list obtained from db"
This function has been checked for 3 months in our druid cluster of 105 nodes.

This PR has:

[x ] been self-reviewed.
[x ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[x ] added integration tests.
[x ] been tested in a test Druid cluster.

Hi @sekingme, apologies for the delay on getting your PR reviewed, but thanks for the contribution :+1:
I'm not personally familiar with this extension at all, but I will try to have a look at it and how your PR fits into it. I agree with @Dylan1312 that it would be very nice to have a test for this behavior you are adding, it appears that maybe MaterializedViewSupervisorTest would be a good place?

Hey @sekingme,
Could you add/update unit tests covering the behaviour this patch fixes please?

Done, already add unit test covering the behaviour.


add an example for intersection plane

a visual helper relevant to #248

Screencast from 08-05-2024 06:05:14 PM.webm

Interesting CI failure. Hopefully now that xargo is gone, it'll work once you update past that. :)


Generating a packing with few particles

Hi, I have been using your code to generate a random packing with very few particles (50~100). I have tried this generation.conf
Particles count: 100
Packing size: 10. 10. 10.
generation start: 1
boundaries mode: 1
contraction rate: 1e-4
The particles are overlapped with each other. Could please tell how to fix it? Or, is it possible to use your code to generate a random packing with very few particles?

Hi,
one possible reason is that due to historical reasons the final particle diameters saved in the packing.xyzd file are equal to the initial particle diameters (specified in the user-provided packing.xyzd or diameters.txt files) and you have to rescale the diameters linearly to get the "real" final particle diameters. Please see this section for more details and sample code. Hope rescaled particles will have no intersections then.
Best,
Vasili

Hi,
Thanks for your quick reply. I did forget to rescale it, however when I use this generation.conf
Particles count: 80
Packing size: 5. 5. 5.
Generation start: 1
Seed: 341
Steps to write: 1000
Boundaries mode: 1
Contraction rate: 1.5e-004

boundaries mode: 1 - bulk; 2 - ellipse (inscribed in XYZ box, Z is length of an ellipse); 3 - rectangle
generationMode = 1 (Poisson, R) or 2 (Poisson in cells, S)
The results still overlap with each other. And it comes wit this results in the terminal:
Checking...
Calc. porosity is 0.313706
Theoretical porosity is 0.664897
Checking min particle distance in a naive way...
Finish:
Calc. porosity is 0.313705899228934
Theoretical porosity is 0.664897
Inner diameter ratio is  1.26992251534201
Time: 46.8032 s, iterations are 8284
Since the calculated porosity is not equal to the theoretical one, I suppose something is wrong. The visualized result is in the attachment. This I do remember to scale it. Many thanks for your time.

Hi，
Somehow, I suspect that my post processing drawing script is wrong, I used matlab function ellipsoid to visualize to the result. Could you please tell me how you visualize it?

Hi,

Since the calculated porosity is not equal to the theoretical one, I suppose something is wrong.

Actually, this is not a problem. The theoretical porosity is the expected porosity, the one calculated from original diameters (which are unity by default). The FBA algorithm uses this expected porosity as a parameter. But it will not always be able to reach it. The LS algorithm doesn't use it at all. So the calculated porosity can have any value.
As i tried to explain in the Readme (section referenced before), you have to multiply particle diameters by (finalDensity / theoreticalDensity)^(1/3) = ((1 - finalPorosity) / (1 - theoreticalPorosity))^(1/3). I think it shall be enough. The only other thing that comes to mind is you can make sure that if your visualization function accepts radii, you pass radii there, not diameters.
I was using some Visual Molecular Dynamics software for visualization actually, but it's probably an overkill. But you can check this reply.
Best,
Vasili

Dear Vasili
Thanks for your quick reply. I have confused the diameter with radii. Sorry for all this trouble.
Cheers
Chen


update hover and remove scroll

this pr updates the lightbox component and removes the scroll function. currently, i'm seeing the hover even when scrolling and when stopping my scroll state, leading to a weird ux and the hovered images getting in the way of reading.
this pr removes the scroll function and tries to simplify the component. it als adjusts the scale.

Thanks @matthewshaver ! @JKarlavige happy to merge it but pls feel free to check if the code is ok 🙏

Sorry I wasn't able to get to this one! All looks good from checking out the code here!


Global Variable on Page to set StyleExpr gives error

I'm trying to add a Global Variable to control the styleexpr of a column on my list page, but I get the following error on the page:
"The identifier 'ScheduleStatusStyle' could not be found."
On my page I have the following field:
field("Schedule Status";"Schedule Status")
{
StyleExpr=ScheduleStatusStyle;
ApplicationArea=All;
}
At the end of the page I have this:
trigger OnAfterGetRecord();
begin
ScheduleStatusStyle := GetScheduleStatusStyle("Schedule Status");
end;
var
ScheduleStatusStyle : Text;
}
The page compiles ok.
This was converted from a working application, so I know the functionality works..

It looks like we're missing automatic inclusion of that variable in the dataset.  For now you could try adding [InDataSet] attribute to ShceduleStatusStyle and we will look into the issue on our side.

Duplicate of #538


chore(master): release 1.52.0

:robot: I have created a release beep boop
1.52.0 (2024-11-06)
Features

update EM and fix package (f186eda)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/indykite/indykite-sdk-python/releases/tag/v1.52.0 :sunflower:


New Release

If you have the time, could you make a new release that includes all the latest changes?
(v3.2 is currently 14 commits behind, which is quite a lot of changes.)

Thanks for the info. Done.

Thanks Boti.
Unfortunately, the version number in library.properties and library.json wasn't incremented either, so I've made a PR for that (#19).


1337 refactor about you component - About you section [WIP]

Context

Changes proposed in this pull request

Guidance to review

Link to Trello card

Checklist

[ ] Attach to Trello card
[ ] Rebased main
[ ] Cleaned commit history
[ ] Tested by running locally

A very similar PR was created: https://github.com/DFE-Digital/refer-serious-misconduct/pull/623


New RadWave SME requests

[x] Splashscreen - text that is currently red should be blue like the clusters.
[x] Modal start button - make button black with a white border
[ ] Modal image - make 2 versions to show depending on screensize.
- current version is good for mobile
- large screens need an image with much smaller text and possibly higher resolution if we don't think that will cause load-time problems.
[x] Add 2 additional background options in 2d mode:
- h-alpha
- Planck gas & dust

#330 would address and close the remaining bullet item


[JBEAP-6348] Not evaluated HTML tags in help text when adding new Paths

JBEAP: https://issues.jboss.org/browse/JBEAP-6348
JIRA: https://issues.jboss.org/browse/WFCORE-1967

Can one of the admins verify this patch?


Update MagicApiaryInventory.java

Changed sidedness to match forestry apiary and fixed canExtractItem to return true for the product slots

These lines caused the slots for Princess, Queen and Drone to only be accessible from two sides, the top and bottom I believe. In original Forestry, those slots can be inserted to from the sides as well.


Add visualizations of surface coregistration (to fsaverage)

https://twitter.com/michaelwaskom/status/963497405726580736

Seems like the tweet that originated this is down. However, I found this other visualization

here

+1 to adding some surface visualization to the reports, especially after poldracklab/fmriprep#2145

Should consider whether to use flattened surfaces or multiple angles for surface-based visualization.
For BOLD, I would think showing the boldref resampled to the surface right after the BOLD-T1w registration (with surface contours) might make it easier to see whether the alignment makes sense. e.g., if I see a lot of dark around the temporal pole, I can look up and see drop out in the volume.


3d: is_on_floor always returns false

Godot version
4.0.dev.calinou [5a61822d7]
System information
Fedora 35 Vulkan
Issue description
is_on_floor never return true when the player collides with the floor, using the template player script.
Steps to reproduce

Run the scene
Because is_on_floor never returns true, motion_velocity.y will grow and the motion in other directions won't work

Minimal reproduction project
is_on_floor_bug.zip

You have set the motion mode to "Free" meaning, it's a game without ground (like a top-down in 2D) all the collisions will be reported as a wall.

Just keep the default value "grounded".

Should the "Free" motion mode be renamed to "Floating" perhaps?

@Calinou "floating" sounds better indeed as it describes well the effects (collision are always walls, no acceleration on the slopes. At first, I thought to something like "no gravity" but I wasn't sure it would be clear to users, I'm not very good at finding names :).
Is the label clear to you (I'm biased as I'm used to it)?

Is the label clear to you (I'm biased as I'm used to it)?

The current label is OK to me, but it may not be very explicit to a newcome.


Defer package installation

It would be nice if Python packages were not installed until opening a py file, C++ packages were not installed until opening a cpp file, and so on.

I opened an issue here.

Blocked by #224.

Fixed in f6496b51b43651a4a7521ad31012f9ad41800449 on develop.


[Bug]example/kine and example/podexec cannot be successfully constructed

Only example/basic works.
example/kine failed
╭─xx@xx ~/go/src/sigs.k8s.io/apiserver-builder-alpha/example/kine ‹master*›
╰─$ apiserver-boot build executables
I1119 15:46:44.620346   22143 build_executables.go:179] CGO_ENABLED=0
I1119 15:46:44.620486   22143 build_executables.go:189] go build -o bin/apiserver cmd/apiserver/main.go
# sigs.k8s.io/apiserver-builder-alpha/example/kine/pkg/apis/mysql/v1
pkg/apis/mysql/v1/tiger_types.go:60:5: cannot use &Tiger literal (type *Tiger) as type runtime.Object in assignment:
        *Tiger does not implement runtime.Object (missing DeepCopyObject method)
pkg/apis/mysql/v1/tiger_types.go:61:5: cannot use &Tiger literal (type *Tiger) as type "sigs.k8s.io/apiserver-runtime/pkg/builder/resource".Object in assignment:
        *Tiger does not implement "sigs.k8s.io/apiserver-runtime/pkg/builder/resource".Object (missing DeepCopyObject method)
pkg/apis/mysql/v1/tiger_types.go:62:5: cannot use &TigerList literal (type *TigerList) as type "sigs.k8s.io/apiserver-runtime/pkg/builder/resource".ObjectList in assignment:
        *TigerList does not implement "sigs.k8s.io/apiserver-runtime/pkg/builder/resource".ObjectList (missing DeepCopyObject method)
pkg/apis/mysql/v1/tiger_types.go:73:9: cannot use &Tiger literal (type *Tiger) as type runtime.Object in return argument:
        *Tiger does not implement runtime.Object (missing DeepCopyObject method)
pkg/apis/mysql/v1/tiger_types.go:77:9: cannot use &TigerList literal (type *TigerList) as type runtime.Object in return argument:
        *TigerList does not implement runtime.Object (missing DeepCopyObject method)
pkg/apis/mysql/v1/tiger_types.go:92:5: cannot use &Tiger literal (type *Tiger) as type "sigs.k8s.io/apiserver-runtime/pkg/builder/resource".ObjectWithStatusSubResource in assignment:
        *Tiger does not implement "sigs.k8s.io/apiserver-runtime/pkg/builder/resource".ObjectWithStatusSubResource (missing DeepCopyObject method)
pkg/apis/mysql/v1/tiger_types.go:100:8: impossible type assertion:
        *Tiger does not implement "sigs.k8s.io/apiserver-runtime/pkg/builder/resource".ObjectWithStatusSubResource (missing DeepCopyObject method)
F1119 15:46:48.040681   22143 build_executables.go:194] exit status 2

example/podexec failed
╭─xx@xx ~/go/src/sigs.k8s.io/apiserver-builder-alpha/example/podexec ‹master*›
╰─$ apiserver-boot build executables
I1119 15:53:06.932434   23800 build_executables.go:179] CGO_ENABLED=0
I1119 15:53:06.932612   23800 build_executables.go:189] go build -o bin/apiserver cmd/apiserver/main.go
go: finding module for package sigs.k8s.io/apiserver-builder-alpha/pkg/cmd/server
cmd/apiserver/main.go:27:2: module sigs.k8s.io/apiserver-builder-alpha@latest found (v1.18.0, replaced by ../../../apiserver-builder-alpha), but does not contain package sigs.k8s.io/apiserver-builder-alpha/pkg/cmd/server
F1119 15:53:08.174624   23800 build_executables.go:194] exit status 1

Env
Version v2.0.0-alpha.0
apiserver-builder-alpha commit: c1e3ccc445efb29dd9f7efff107c2bd059b3efd3
go version: go1.15.5 linux/amd64
uname: Linux xx 4.15.0-124-generic #127-Ubuntu SMP Fri Nov 6 10:54:43 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
apiserver-boot version:  Version: version.Version{ApiserverBuilderVersion:"v2.0.0-alpha.0", KubernetesVendor:"kubernetes-1.19.2", GitCommit:"v2.0.0-alpha.0", BuildDate:"2020-11-04-21:20:28", GoOs:"linux", GoArch:"amd64"}
Version 1.18.0 failed to build too.
apiserver-builder-alpha commit: 95dca1d34e91d6e76c50fa4f272a77f573fd7558
apiserver-boot version: Version: version.Version{ApiserverBuilderVersion:"v1.18.0", KubernetesVendor:"kubernetes-1.18.4", GitCommit:"d5fdf8c1b65a7c6068806b540998889ec5114c36", BuildDate:"2020-06-24-19:17:37", GoOs:"darwin", GoArch:"amd64"}

example/kine failed

we removed code-generators from this project. you need to run controller-gen object:headerFile="hack/boilerplate.go.txt" paths="./..." to do a minimal code-generation.

example/podexec

extending arbitrary subresource is not yet supported in the new framework, but we will be getting it very soon

example/kine failed

we removed code-generators from this project. you need to run controller-gen object:headerFile="hack/boilerplate.go.txt" paths="./..." to do a minimal code-generation.

example/podexec

extending arbitrary subresource is not yet supported in the new framework, but we will be getting it very soon

Thank you for your reply.

The examples do not work even with code generation. server.StartApiServerWithOptions was removed
Are the examples built as part of a PR build?

/close


Problem with Notes

There seems to be a problem with the 2.10.0 package, diagrams with notes aren't displayed correctly. Could this be related to the viz.js 1.7.1 upgrade? In my workspace, using 1.3.0, everything works fine.

I tried the ready-made examples. Could you please post the difference?

As an example, here are the first lines from the class diagram (that works)
// {type:class}
// {direction:topDown}
[note: You can stick notes on diagrams too!{bg:cornsilk}]
[Customer]<>1-orders 0..*>[Order]

Unfortunately, adding one more line with a note does not:
// {type:class}
// {direction:topDown}
[note: You can stick notes on diagrams too!{bg:cornsilk}]
[Customer]<>1-orders 0..*>[Order]
[Order]-[note:asdf]

For comparison (to be sure about the syntax): http://yuml.me/edit/184be5b8
This is running on VSC 1.9.1 with vscode-yuml 2.10.0. To be sure, I tried the same workspace with 1.3.0 and 1.7.1. Runs perfectly with 1.3.0, but not with 1.7.1.

Any update on this? Were you able to reproduce the problem? The easiest option might be to revert to 1.3.0 for now...

I've just experienced problems with notes in class diagrams for VSC 1.18.1. Extension yUML version 2.10.0.
The note field works just fine alone, but causes an error when attached to a class, as seen with the example from the vscode-yuml wiki:
[Address]-[note: Value Object] results in Error composing the diagram

This issue has been isolated and determined that is caused by newer versions of viz.js
I will use an old version of viz-lite.js


TopK Fuzz Tests 🐝

Is your feature request related to a problem or challenge?
After https://github.com/apache/arrow-datafusion/pull/7721 a SortExec with a limit will use a special TopK . We have basic unit tests, but I think the coverage could be improved, specifically with Fuzz testing
Describe the solution you'd like
What I would like is a new fuzz test to be added to the the existing fuzz cases: https://github.com/apache/arrow-datafusion/tree/main/datafusion/core/tests/fuzz_cases
The structure of SortTest in https://github.com/apache/arrow-datafusion/blob/e95a24b5a260e0e2f603d52682d36cce192676f8/datafusion/core/tests/fuzz_cases/sort_fuzz.rs#L111 might be a good one to follow
The basic outline would be:

Create an input with several columns (integers, strings, floats)
Reorder the input randomly
Divide the input up multiple batches using make_staggered_batches
Run a query like SELECT * FROM t ORDER BY <col(s)> LIMIT <N> and collect the output
Compute the expected result programmatically (e.g. by sort the data, prior to creating RecordBatches)
Ensure the output matches the expected result

Input size: 1000 rows
Parameters to vary

sort cols: (int), (string), (float), (int, string), (string, int), etc.
N: 1, 10, 100, 300 (aka how many are kept)

Bonus points
make it easy to add new columns / types (e.g. like string dictionary)
Describe alternatives you've considered
No response
Additional context
No response

I think this would be a nice beginner project for someone who was familiar with Rust, but not familiar with DataFusion / working with RecordBatches / arrays. There are reasonable existing examples to follow as well
BTW you can run the fuzz tests with:
cargo test --test fuzz

/assign me

@alamb

I have looked this, it seems that make_staggered_batches can only get i64 cols, but the tests seems request cols with (integers, strings, floats). Maybe I need to wirte a fn make_staggered_batches myself?

Thanks @Tangruilin

I have looked this, it seems that make_staggered_batches can only get i64 cols, but the tests seems request cols with (integers, strings, floats). Maybe I need to wirte a fn make_staggered_batches myself?

Sorry, I think I meant use stagger_batches: https://github.com/apache/arrow-datafusion/blob/85046001da91d535f7ea417911cd51944f9820f4/test-utils/src/lib.rs#L72-L76

when i get the result with (string), (float).etc cols. I found that batches_to_vec can only work for i32.  May be I need a another way to convert record batches to vec, are there any suggestions?

@alamb maybe i can add a enum to support other type? If it is ok, i will do it.

when i get the result with (string), (float).etc cols. I found that batches_to_vec can only work for i32. May be I need a another way to convert record batches to vec, are there any suggestions?

I would actually recommend doing it the otherway around:

Create the data with a Vec
Figure out what the expected answer is
Convert the Vec to RecordBatch

Does that make sense?

when i get the result with (string), (float).etc cols. I found that batches_to_vec can only work for i32. May be I need a another way to convert record batches to vec, are there any suggestions?

I would actually recommend doing it the otherway around:

Create the data with a Vec
Figure out what the expected answer is
Convert the Vec to RecordBatch

Does that make sense?

For 2 >  The expected answer will be three types. I consider to use Generics to solve it, but different type need to use different arrow Array, so it seems can not solve.

when i get the result with (string), (float).etc cols. I found that batches_to_vec can only work for i32. May be I need a another way to convert record batches to vec, are there any suggestions?

I would actually recommend doing it the otherway around:

Create the data with a Vec
Figure out what the expected answer is
Convert the Vec to RecordBatch

Does that make sense?

For 2 > The expected answer will be three types. I consider to use Generics to solve it, but different type need to use different arrow Array, so it seems can not solve.

I have a idea. I will try it


WiP: Handle debugger pins

At startup, pins used by the debugger are in Debugger state, prohibiting their
use. disable_jtag allow to get PA15, PB3 and PB4 usable as GPIO or alternate
functions at the cost of disabling JTAG.
Discussed in #77
cc @MauroMombelli

I've tested nojtag on a bluepill with success.

It doesn't work :-( This complies:
#![deny(unsafe_code)]
#![no_main]
#![no_std]

use panic_halt as _;

use stm32f1xx_hal::{
    prelude::*,
    pac,
};
use cortex_m_rt::entry;

#[entry]
fn main() -> ! {
    let p = pac::Peripherals::take().unwrap();

    let mut rcc = p.RCC.constrain();
    let mut gpioa = p.GPIOA.split(&mut rcc.apb2);
    let mut gpiob = p.GPIOB.split(&mut rcc.apb2);
    let mut afio = p.AFIO.constrain(&mut rcc.apb2);

    //let (pa15, pb3, pb4) = afio.mapr.disable_jtag(gpioa.pa15, gpiob.pb3, gpiob.pb4);

    let mut pa15 = gpioa.pa15.into_push_pull_output(&mut gpioa.crh);
    let mut pb3 = gpiob.pb3.into_push_pull_output(&mut gpiob.crl);
    let mut pb4 = gpiob.pb4.into_push_pull_output(&mut gpiob.crl);

    loop {
        pa15.toggle();
        pb3.toggle();
        pb4.toggle();
        cortex_m::asm::delay(8_000_000);
    }
}

Maybe if you create a marker (empty) trait and implement it for Input<MODE>, Output<MODE>,  Analog and Alternate<MODE> (maybe I'm missing another) but not for Debugger`. And then you can add a bound to MODE on line 189.
Sorry for some lacking explanation, I'm on mobile right now.

I see the idea, thanks, will try.

@thalesfragoso Thanks it's working.

yay! Suggestion: those are not the only tricky pin, we could also completely disable debugging to get other 2 pin (PA13 and PA14), also the same could be applied to the external clock pin.. let me dig in the docs a moment

I've blocked PA13 and PA14, freeing them would only be adding a disable_jtag_sw taking the 5 pins.

also i am wandering if this should be proposed to the other implementations too.

I don't understand this sentence. Which other implementations?

I don't understand this sentence. Which other implementations?

other chip implementation like stm32f3xx-hal etc..

Hm, using MaybeUninit will bump the MSRV to 1.36, i.e. the latest and greatest. I personally don't have a problem with that but I can imagine people frowning upon that...

@therealprof si you want I dont use it? I can, that's just using uninitialized instead.

Or i thinks i can remove this uninitialized trick.

@therealprof no more MaybeUninit


ScrollableState.setCanDrag should not contradict with scroll physics

Currently, because ScrollableState.setCanDrag doesn't check whether it complies with ScrollPhysics.shouldAcceptUserOffset, it's possible that user of ScrollableState doesn't check whether it can be set to true or false and thus ignores scroll physics by mistake - which is what happens to NestedScrollView, which forgets to do exactly this https://github.com/flutter/flutter/issues/45619
https://github.com/flutter/flutter/blob/ff15d04f214ae7cc4ffbacde2faefa1772e112e4/packages/flutter/lib/src/widgets/nested_scroll_view.dart#L1619-L1621
I propose that we force users of the ScrollableState to check the physics before they apply their own conditions with such assert (or something similar)
assert(
  _physics == null || newCanDrag == _physics!.shouldAcceptUserOffset(position),
  'When scrollable has physics, canDrag should be equal to shouldAcceptUserOffset result',
);

cc @Hixie

/cc @Piinks

Came across this while working on https://github.com/flutter/flutter/pull/127718
I realized working on that we cannot add this assertion since it would break the nested scroll view. If the outer position is not draggable, but the inner position is, this assertion would trip when the NestedScrollView set drag. Adding more docs in the linked PR. :)


Add maxNumberOfJobs + fix HMAC error

Description
Add maxNumberOfJobs to worker request
Ensure that HMAC auth header is calculated before unencoding the query params
Deepclone distribution modes for update tests
Add unassign job to samples
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-communication-jobrouter


what is drone agent?

I am new to drone. I follow docs to install drone on my local server, everything works fine. I also use vault share secrets between reps, and install the related extension https://github.com/drone/drone-vault .  the extension docs say I need put some config to drone agent
Update your Drone agent configuration to include the plugin address and the shared secret.

DRONE_SECRET_ENDPOINT=http://<IP_ADDRESS>:3000
DRONE_SECRET_SECRET=bea26a2221fd8090ea38720fc445eca6

The problem is I can't find docker agent in docs.drone.io. please help me.
Is drone runner is replacement to drone agent ? But I can't find similar config in drone runner reference https://docker-runner.docs.drone.io/installation/reference/

:wave: hey there, per our issue template, for end-user support please use one of our support channels, such as our chatroom or our mailing list.


[Feature Request] add a doc for adding a custom component in sidebar

What is your enhancement?
add a doc for adding a custom component in sidebar

Hi @Nightmaregodss,
Thank you for working with our products and sorry for our late response.
Can you please give us more details? How do you see it working?
Thank you,
Rares


Add an option to reverse the magnetic z direction

In a small number of phones like some OnePlusOnes the phone manufacturer has implemented the compass API incorrectly.  Provide an option for these users to reverse the direction.

https://github.com/sky-map-team/stardroid/issues/75


adding a download gif to help

Hey Nicole! I noticed that the readme link to download just pointed to the main sparc org so tried to make a pull request to fix it - but I ended up just accidentally merging it (not totally sure how). Then, I realised even the link I gave was wrong (as downloads don't work from the actual files on Github, they work at a repo level) so I added a link purely back to this repo.
So, once I was done derping I thought a gif might be helpful to show people how to get the file. This time I actually did manage to make a pull request as originally planned for you to review!

Thanks @JosephMcArthur for your entertaining comment. :) This is a helpful and welcome addition, I'll merge it right in.

I'd forgotten about this! I actually now have a better way (found yesterday). You can create a release https://github.com/sparcopen/open-education-state-policy-tracking/releases that will give you a direct download link.


Add outside click support

@konsti a class is needed here because react-click-outside needs a ref and stateless functions do not support those

@konsti I moved the propTypes outside. can I merge this one?


Will the training data be released？

This version only uses the open-sourced dataset.

This version only uses the open-sourced dataset.

Hi! Do I have to download all the data or only download the data inside train dataset/subfolder. I can see from datasets.yaml that not all the data were used to train or eval. Is it okay to obtain only the necessary data to fit the path format in datasets.yaml and train the model?
For example, for YoutubeVOS dataset, I think you used the 2018 version. Is the train.zip in this Google Drive (https://drive.google.com/drive/folders/1bI5J1H3mxsIGo7Kp-pPZU8i6rnykOw7f) enough to train the model?
Thanks in advance for your reply.

To get comparable performance, you need to match all the datasets appearing in "run_train_anydoor.py".

Hi!
When I try to train AnyDoor, it always takes a long time to load the dataset.
I type in htop and find that the dataset loading process only uses ONE cpu. I gauss that your serial sampling of two frames in the video results in inefficient CPU utilization, ultimately leading to prolonged data loading. If you need to train multiple times, you will have to go through a long process of data loading each time.
Can you perform one-time, parallel preprocessing on the dataset and only load the preprocessed dataset during training?
thanks.


Can't install via composer

Then I run the command for installation project:
composer create-project symfony/symfony-demo my_project
I am getting the error:
Could not find package symfony/symfony-demo with stability stable in a version installable using your PHP version, PHP extensions and Composer version.
PHP 8.1.8.
Composer 2.3.10

I've just run the command and it worked for me as expected:

Let's see if we can find why it failed for you 🤔

Hmm...

Also I used the ubuntu 21.10

Do you have a global composer config file disabling the packagist.org repository ?

No I don't have any config files for composer :)

Same issue.
Composer 2.3.8
PHP 8.1.8
Ubuntu 21.10

It works for me on Ubuntu 18.04.6, PHP 8.1.8, Composer 2.3.7.
I have loads of PHP extensions installed. If I remove php8.1-sqlite, then it also fails for me:
$ composer create-project symfony/symfony-demo my_project
Creating a "symfony/symfony-demo" project at "./my_project"

In CreateProjectCommand.php line 435:

  Could not find package symfony/symfony-demo with stability stable in a version installable using your PHP version, PHP extensions and Composer version.

@7ochem the upcoming composer 2.4 version will provide a better error message when there is no version compatible with your platform, by giving more details.

@stof that's exactly what I was going to add to my comment: Seems like a Composer issue that the message doesn't clearly state what is missing. Something like the output of composer why-not symfony/symfony-demo, except that you can't run composer why-not when you don't have composer initialised in your current working dir.

I have the same problem, i'm using Ubuntu 20.04 with PHP 8.1.8
I can confirm that the issue is fixed after installing php8.1-sqlite3 as @nasgir suggest.

@7ochem indeed. The extra info is displayed in composer require but not in composer create-project. I opened https://github.com/composer/composer/issues/10959 about it.

When I add the sqlite php extension:
sudo apt install php8.0-sqlite3
The issue is fixed :)
For composer create-project need more details

I've removed the php8.1-sqlite3 also I upgraded the composer version 2.4 and try to itnstall the symfony demo application, however, I saw the error:

Although the issue is for php sqlite extension :(

Well, here, it shows that the latest version is not compatible with your platform due to the PHP version itself.
It indeed does not show warnings for all candidate versions

On my laptop was php version 8.0. I upgraded version and the compmoser showed more detail:

Composer should be 2.4 version

On Manjaro. Had to manually enable pdo-sqlite in php.ini for this to work:
> symfony new ./symfony_demo --demo
* Creating a new Symfony Demo project with Composer
  (running /home/chriego/.local/bin/composer create-project symfony/symfony-demo /home/chriego/Projects/personal/symfony_demo  --no-interaction)

Creating a "symfony/symfony-demo" project at "./symfony_demo"
Cannot use symfony/symfony-demo's latest version v2.4.0 as it requires ext-pdo_sqlite * which is missing from your platform.

Notice the last line
vim /etc/php/php.ini

Find line ;extension=pdo_sqlite and remove the ;


Netutil cleanup

moved network related utilities to extensions.
moved iterators to iterator subfolder
introduced LaneUtil.
I have marked some methods as obsolete instead of removing them to avoid big changes.

@aubergine10 note that I have merely moved the code. I have not written any new code. So I prefer not to change things too much. Maybe just IsFlagSet and LHT ?

@aubergine10 note that I have merely moved the code. I have not written any new code. So I prefer not to change things too much. Maybe just IsFlagSet and LHT ?

Yup, the other stuff can come later.  Want me to create issues to track that, or...?

maybe when you opened an issue I can reference it in the TODO over there.

@aubergine10 I fixed a few things but please mark everything inside GetSortedLanes().

@aubergine10 I made a few changes but please mark everything inside GetSortedLanes() as resolved

I hope you didn't forget about this


fix: update scrollbar for code blocks

Describe this PR
Horizontal scrollbar for code blocks is not currently uniformed in behaviour or appearance.
Changes
Update code component to have a generalised scrollbar look and behaviour, one which is already in place at @prisma/blog as well.
Added wrap prop on codeblock components for cases where we have code blocks that have only one line or we want to wrap the text depending on the context.
⚠ This should be defined by the docs writers.
i.e. in cases such as this code block, it wouldn't make sense to have the full line scrollable, since it'd just make it harder to read or copy.
For #1015:

prod
fixed

For #1023 We changed the behaviour to always display a scrollbar in case it contains large code inside. As it is now, the user needs to scroll inside to make the scrollbar visible, but it is not 100% obvious it is a codeblock with large content.

prod - no inside scroll
prod - inside scroll
fixed

https://github.com/prisma/docs/assets/14851246/19c46b0c-b197-4c49-a443-4c6e7b27369e

What issue does this fix?
Fixes #1023 #1015
Any other relevant information
N/a

@ruheni Could you please review this PR and make sure the comment using wrap property makes sense for doc writers?

I believe this would also fix this issue https://github.com/prisma/docs/issues/1446 ie it looks like the wrap option was a request already.

The wrap property makes sense to have for code snippets. Sharing the update in the #docs and #team-dev-advocacy(reposting) channels would help create visibility. I would also happily mention it in our team sync once this is merged.


New Check: com.google.fonts/check/colorfont_tables

"Fonts must have neither or both the tables COLR and SVG."
Added to the Google Fonts Profile.
(issue #3886)

This is currently marked as a "draft" PR, waiting feedback from @rsheeter on what to use as rationale text for this newly proposed check.

Thanks Felipe!


Windows support

Currently windows does not work. However Winsock is very much like Berkeley Sockets, there are just a few differences.

Currently making bindings for Winsock2, it's a lot more than the Berkeley sockets stuff
I'll PR the bindings to core:win32 at some point
Then it would be easy to take these Berkeley sockets bindings, the Winsock stuff, and make some sort of core:net/sockets

Sounds great.
I've updated this library to work with the newest released version of Odin.
By the way, I don't know if this library is even nearly complete (it might be, or it might not be, I don't have time to check).


Bootstrap process fails to download binary from s3 using aws-cli

What happened: Bootsrap process fails in file install-worker.sh on line 125
What you expected to happen: It should have downloaded binary files
How to reproduce it (as minimally and precisely as possible): just git clone and execute make
Anything else we need to know?: Part from output with echo placed to verify the execute part
amazon-ebs: Downloading binaries from: s3://amazon-eks
amazon-ebs: AWS cli present - using it to copy binaries from s3.
amazon-ebs: aws s3 cp --region us-west-2 s3://amazon-eks/1.11.5/2018-12-06/bin/linux/amd64/kubelet .
amazon-ebs: aws s3 cp --region us-west-2 s3://amazon-eks/1.11.5/2018-12-06/bin/linux/amd64/kubelet.sha256 .
amazon-ebs: fatal error: An error occurred (400) when calling the HeadObject operation: Bad Request

Environment:

AWS Region: default (taken from git no edits), eu-west-1
Instance Type(s): default (taken from git no edits)
AMI Version: region default
Kernel (e.g. uname -a): ami default

Binary downloads are now failing with 403 Forbidden.

This is almost certainly due to #175. It changed the packer builder definition to include environment variables for AWS_ACCESS_KEY_ID & AWS_SECRET_ACCESS_KEY. The problem is, that if you don't specify the packer variables for these, they'll be blank; and, even so, the mere fact that they exist means that the aws CLI will only consider them, and not try other credentials in the chain. One solution might be to detect if those env vars are blank in install-worker.sh, and unset them.

I'm not sure if this is related, but even with #212, I'm still failing to download the binaries. When I run wget manually, I get the following:
 wget 'https://amazon-eks.s3.amazonaws.com/amazon-eks/1.11.5/2018-12-06/bin/linux/amd64/aws-iam-authenticator' --2019-03-07 20:48:19--  https://amazon-eks.s3.amazonaws.com/amazon-eks/1.11.5/2018-12-06/bin/linux/amd64/aws-iam-authenticator
Resolving amazon-eks.s3.amazonaws.com (amazon-eks.s3.amazonaws.com)... <IP_ADDRESS>
Connecting to amazon-eks.s3.amazonaws.com (amazon-eks.s3.amazonaws.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2019-03-07 20:48:19 ERROR 404: Not Found.

Note: I also had to prepend amazon-eks to $S3_URL_BASE to fix a problem where it was returning a 301 error code with no destination:
wget 'https://s3.amazonaws.com/amazon-eks/1.11.5/2018-12-06/bin/linux/amd64/aws-iam-authenticator'
--2019-03-07 20:51:07--  https://s3.amazonaws.com/amazon-eks/1.11.5/2018-12-06/bin/linux/amd64/aws-iam-authenticator
Resolving s3.amazonaws.com (s3.amazonaws.com)... <IP_ADDRESS>
Connecting to s3.amazonaws.com (s3.amazonaws.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: unspecified
ERROR: Redirection (301) without location.

If it matters, I'm using us-east-1, which has some special logic in install-worker.sh

This should be fixed by #212. Can you try again with that change?

Sorry, was unrelated. I made a change to the json config file that didn't work out the way I'd hoped :-) We're all good, thanks.


Add Wordle Clone

Project title
Wordle Clone
Project Description
A Wordle clone which you can play not just once a day, but anytime. Built using HTML, CSS and JS with a tad bit of animate.css and toastr for non-blocking notifications.
Stack:
And in order to tick the check box just but x inside them for example - [x] like this. Please delete options that are not relevant.

[X] Html
[X] CSS
[X] JavaScript

/assign


float 16 & 32 encoding, allowRemainingBytes option, new buffer allocation strategy

switched from runtime allocation strategy to exact accounting allocation strategy
this removes some growth penalties, slicing, and buffer copies at the expense of iterating over the object being encoded twice (not sure if performance impact is beneficial, need to make benchmarks)
some methods have been renamed to reflect their intention
I plan to change (and rename) appendUtf16Data to append chars to string instead of using String.fromCharCode.apply ; this strategy has improved performance in many other scenarios, but not sure of impact here
I plan to add a small benchmark suite to the tests
code coverage needs to be improved, some methods need to be removed, some branches need to be refined
forked from another fork to pull a string-to-integer key change
messed with the tests, added one, changed the forEach to a for loop (to access loop counter, but then did not use yet...) and lots of commented out console.log and console.error statements
*allowRemainingBytes option not yet tested, default false

Coverage decreased (-2.8%) to 96.867% when pulling 5af2c41233d41574f3cc26cb2cc2f92587b0497d on TYoung86:master into f0b5728594ba60034047a39319a63f4311a46211 on paroga:master.

Coverage decreased (-2.8%) to 96.867% when pulling 5af2c41233d41574f3cc26cb2cc2f92587b0497d on TYoung86:master into f0b5728594ba60034047a39319a63f4311a46211 on paroga:master.

allowRemainingBytes has tests ... the test for saucelabs needs to be fixed for pulls.

Coverage increased (+0.4%) to 100.0% when pulling 5a45b213d961a135f141c01acfee1ec0c10d2a12 on TYoung86:master into f0b5728594ba60034047a39319a63f4311a46211 on paroga:master.

cbor-js's cbor.js vs cbor-js-unofficial ... significant performance decrease
despite performance reduction, has shown significant reduction in memory usage, and smaller output when encoding floating point data and integer object keys
I believe I can improve general performance with a fair bit of tweaking

created a performance branch for testing, so far have met par for performance and then some (10% - 15% gain over official)
think I can get performance up a bit higher still.

ah great, gitcdn.xyz is down... tests fail, will update to use rawgit.com if it doesn't come back up...

I merged already some of your changes into master. Could you rebase your work on it and try to avoid changing nearly the whole file? That makes an review nearly impossible.

Yeah, I'll rebase and make the options change separate first. 2nd, float 16
and 32 encoding.
The buffer allocation strategy changes the whole file. I'll keep it out
until I have good code documentation on everything for a formal review.
You can close the pull request for this one.
On Sep 14, 2016 3:22 PM, "Patrick Gansterer"<EMAIL_ADDRESS>wrote:

I merged already some of your changes into master. Could you rebase your
work on it and try to avoid changing nearly the whole file? That makes an
review nearly impossible.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/paroga/cbor-js/pull/14#issuecomment-247125238, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGp96Sb8eTP1xd_siti67x-jHtEZyCsxks5qqEmJgaJpZM4J6OCo
.

Coverage increased (+0.7%) to 100.0% when pulling 7980b1584719638f97f10364b32f0d044fb30a22 on TYoung86:master into 66ccfe3c9cdb508ff15ec9aebd546c3078c504d2 on paroga:master.


Allow skipping to the end of a message without reading all the groups and var data

Add a method something like Decoder.skipToEnd().

I agree.  I've had to roll my own for scanning to a specific group as quickly as possible, and it's not easy due to the stateful nature of the parser and the private state variables, such as index.

Oh nice this is the impetus for --> https://github.com/FIXTradingCommunity/fix-simple-binary-encoding/issues/53

Fixed with https://github.com/real-logic/simple-binary-encoding/pull/865


Suggestion: Allow type annotations for const assertions

Suggestion

🔍 Search Terms

const assertions with type annotations, const assertions, type annotations, typed variables with also using as const
✅ Viability Checklist

My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion

I really love the power of using const assertions for creating deeply immutable and narrowly typed constants, although I feel they have a relatively major flaw in the fragility they introduce when you have a specific shape of data you want a variable to adhere to, as you ultimately have to go and perform the type-checking manually if you make any human mistakes.
This proposal is to allow us to get the best of both worlds, by introducing a new additional syntax to optionally allow for adding a type annotation to a const assertion, in the same manner you would add a type annotation at the start of a variable normally using a colon. e.g.
const ANIMALS = {...} as const: Record<Animal, AnimalInfo>;

The type checking would then effectively perform be performed on the value as it normally would to ensure that the value adheres to the type in the type annotation, and return any errors to be resolved if not.
Importantly however, the actual type of the variable would still remain the deep readonly/immutable type that is generated from using a const assertion.
📃 Motivating Example

Take the following example that the suggestion above references from, where we are trying to get the ANIMALS constant to follow the shape of Record<Animal, AnimalInfo>
enum Animal {
	CAT = 'cat',
	DOG = 'dog',
	MOUSE = 'mouse';
}

interface AnimalInfo {
	sound: string;
	lifeExpectancy: number;
}

const ANIMALS = {
	[Animal.CAT]: {
		sound: 'meow',
		lifeExpectancy: 15,
	},
	[Animal.DOG]: {
		sound: 'woof',
		lifeExpectancy: '10', // NOTE: the type here has accidentally been declared as a string instead of a number
		favoriteFood: 'bone' // NOTE: The AnimalInfo interface does not include a favoriteFood property
	}, // Note: the constant is missing an entry for Animal.MOUSE
} as const;

As you can notice from the embelished example above, it can be quite easy to make mistakes when using const assertions that would ordinarily get picked up as errors just by using a normal type annotation (e.g. const ANIMALS: Record<Animal, AnimaInfo>).
Even if you were to try and use both a normal type annotation and a const assertion like this for example:
const ANIMALS: Record<Animal, AnimalInfo> = {...} as const;

unfortunately (though I think it makes some amount of sense), only the type from the type annotation (Record<Animal, AnimalInfo>) is what will get cast for the type of the ANIMALS constant, effectively making the const assertion redundant.
By allowing the type annotation to happen after the const assertion, we can get the desired benefits without introducing any breaking changes.
💻 Use Cases

The general use cases for this have been for the most part covered by the motivating example above. Essentially you would want to use this anywhere where you want to have the benefit of both performing normal type checking for a variable's value against a type annotation to ensure a consistent shape for the value's data, while still having the type of that variable be cast to the narrower, deeply read-only type that is generated from a const assertion.
There aren't really any existing workarounds for this that I am aware of. The best alternative I've been doing personally is just manually adding the type annotation to a variable and removing it again whenever I want to make changes to it while ensuring I'm not breaking the shape of the data.
Any thoughts, feedbacks, suggestions, or criticisms on this propsal would be greatly appreciated🙏

Looks like the so-called satisfies operator as discussed in #7481 and now #47920.

const ANIMALS: Readonly<Record<Animal, AnimalInfo>> = {...};

?

const ANIMALS: Readonly<Record<Animal, AnimalInfo>> = {...};

?

That is still not the equivalent to the stricter type of what ANIMALS is actually being cast to by using a const assertion.

Looks like the so-called satisfies operator as discussed in #7481 and now #47920.

@jcalz Yep you're right, good find. Will close this suggestion.


Style/MixinGrouping fails for “include” in other contexts

After upgrading to 0.48.0 I get this offense:
spec/lib/pricing_model_consistency_spec.rb:54:42: C: Style/MixinGrouping: Put include mixins in separate statements.
      expect(pricing_model.constants).to include(:KNOWN_PRICE_SET_NAMES, :CUSTOM_PRICING_MODEL_FIELDS, :PRODUCTS, :PLATFORM_PRODUCT_KEYS)
                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

/cc @Drenmi

@brandonweiss: Indeed. There's a PR waiting to be merged for that. 🙂

❤❤❤

Merged.


User Story:  Record alertness level for certain time of day

As a Participant (student),
I want to record my alertness level for a certain time of day,
so that I can further capture metrics around my health behavior.
+Scenario: Select time of day+
Given that it's Wednesday evening
When I want to record my alertness level from earlier today
Then I'm able to indicate how alert I was this morning
Or how alert I was in the afternoon
Or how alert I was in the evening
+Scenario: Defaulting time of day+
Given I haven't recorded any data for today
When I want to record my alertness level
Then the time of day is defaulted to the morning

This may need to be discussed further, based on feedback from today's session.

Michael and the group have aligned on recording one alertness level per day.


Can't compile with SDL2 2.0.14 from LMDE5

front/sdl/mu_renderer.c: In function ‘flush’:
front/sdl/mu_renderer.c:90:2: error: implicit declaration of function ‘SDL_RenderGeometryRaw’; did you mean ‘SDL_RenderGetMetalLayer’? [-Werror=implicit-function-declaration]
   90 |  SDL_RenderGeometryRaw(r->renderer, r->texture,
      |  ^~~~~~~~~~~~~~~~~~~~~
      |  SDL_RenderGetMetalLayer
cc1: all warnings being treated as errors
make[1]: *** [sdl2-frontend.make:182: obj/native/release/sdl2-frontend/mu_renderer.o] Error 1
make: *** [Makefile:286: sdl2-frontend] Error 2

I get this error when following the instructions from README, what should I do to get a newer version of SDL that has this instruction? Is there a fallback or will I have to compile the web frontend?

Hi
Yes. you need SDL 2.0.20 or newer. (Released in Jan 2022)
What OS are you running? You either need to build SDL from source or download a prebuilt update for your system.
Unfortunately there is no fallback to other APIs.
But you could try the Web or Libretro version.
Web:
premake5 --modules=ctrl --static gmake
make config=release_web clean web-frontend

Libretro:
premake5 gmake
make clean libretro-frontend

If you just want to test run the emulator. Perhaps the Flatpak version is an option? It has just been updated to the latest version. https://flathub.org/apps/org.virtualxt.VirtualXT

I compiled a newer version of SDL2 and the emulator now compiles and runs. However, when I decided to run 8088MPH (For fun, I'm sure your emulator would never be accurate enough and there seems to be no composite option anyway.), it says that the CPU runs between 1000% and 3000% faster than a real 8088, even when I set it to run in 8088 mode rather than V20 mode. Trying to run the demo shows nothing, not even a black and white picture like DOSBOX would.

Well.. you wont be running either 8088MPH or Area5150 on VirtualXT unfortunately. It requires very precise timing and near perfect CGA emulation and they target the original IBM 5150 explicitly. That is currently not the goal for this emulator. If you want to try out these demos on an emulator I recommend @dbalsom (GloriousCow) MartyPC whose main focus is accuracy.
As for the reported speed. That is a bit strange. I have to look in to that. I would not expect it to be 100% but I don't see why it should be that far off.
Composite output is being worked on and might be part of next release.


Unprecise documentation on extended function semantics

I stumbled mentions on extended function semantics and went to this section of the doc: https://funcy.readthedocs.io/en/stable/extended_fns.html#extended-fns
IMHO, this section could use some examples. For example it states that providing a mapping instead of a callable would result in lambda x: f[x] being used. It took me some time to figure out how to use this just by reading this dry description.
Would you be interested that I complete this page a bit with usage examples?

Examples will help for sure. I have them in some function docs but not here. Will be grateful if you'll full this in. Maybe something akin to the overview.


wav2vec-u GAN training not converging on Korean dataset

❓ Questions and Help
Before asking:

search the issues.
search the docs.

What is your question?
we are trying to train wav2vec-u on Korean data but our GAN model does not converge well. Are the parameters used to train the model presented in the paper the same as those included in the repo? Also, are the parameters for the multilingual GAN the same as the English model?
Code

What have you tried?
We successfully replicated the Librispeech experiment with English data. We prepared a Korean wav2vec 2.0 model with the public AI hub Korean dataset, but the GAN model does not converge when trained on this same data.
( it is not decreasing until 150K)

We also tried training the GAN using the XLRS model as an encoder using English Librispeech 100 dataset, and it also does not converge well (with hyper parameter range in paper and recipe). The valididation weighted PPL does not fall below ~60.
( it is not decreasing until 150K)

What's your environment?

fairseq Version (e.g., 1.0 or main): 1.0.0a0+741fd13
PyTorch Version (e.g., 1.0): 1.8.0+cu111
OS (e.g., Linux): ubuntu 20.04
How you installed fairseq (pip, source): git clone https://github.com/pytorch/fairseq.git && cd fairseq && git reset --hard 741fd138c69eebc1fac09b590047da85cdeafe2
Build command you used (if compiling from source): python3 -m pip install --editable ./
Python version: 3.8.10
CUDA/cuDNN version: cuda_11.1
GPU models and configuration: A100 x 8
Any other relevant information:

@KimJeongSun  Hello, I have the same problem with wav2vec-u experiment on the Mandarin data set. I guess it may be related to GAN's training hyperparameter settings, but I have adjusted the hyperparameters many times and have not achieved reasonable results. If you have new progress, please share it.

Thanks for your work. What's the current status? I'm not getting good results; my UER is stuck around 90.
I've cloned this repo (it might have environment problems new): https://github.com/oneapi-src/ai-transcribe
Others cloned it with a virtual environment: https://github.com/voidful/wav2vec-u-exp
I'm having trouble with this: https://github.com/facebookresearch/fairseq/issues/5572

Thanks for your work. What's the current status? I'm not getting good results; my UER is stuck around 90.
I've cloned this repo (it might have environment problems new): https://github.com/oneapi-src/ai-transcribe
Others cloned it with a virtual environment: https://github.com/voidful/wav2vec-u-exp
I'm having trouble with this: https://github.com/facebookresearch/fairseq/issues/5572
@KimJeongSun


Update DOCS

There are a few more docs in docs repo that are outdated.
Change them or delete if needed.

@atalyaalon  - can you please list the APIs that are not documented properly?

@idosavion actually all of them.
Any suggestion for a relevant tool?
BTW we thought of using Flask-RESTFPlus, that also has swagger but haven't started yet


[as2_behaviors_motion] Tf timeout not configurable

Feature Description
Right now as it states, there are three behaviors: Follow_path, land and take_off that takes a non-configurable default timeout of 50ms to look for a transformation in the required frame. When using transformation publishers that publish at a low rate (eg: 10hz) because their data source rate is limited (eg: gps+azimuth), this can be a problem, as these behaviors will discard these transformations most of the times.
There should be a way to parametrize this TF timeout.
Implementation Considerations
Include the parameter value of tf timeout in every function that uses tf_handler and supports it, such as 'try_convert' function and 'get_state' function.

@javilinos Has this issue been resolved already?


Update gamma-pendulum.ipynb

fix repo name in jupyter notebook
github.com/jannerm/gamma --> /gamma-models
The colab example doesn't run without this change.

Thanks for catching this!

Thanks for catching this!


Pass through logger from config.

It appears 2fc89bc438ab907d22fb63f595ebc6ccf50bd02a added a new Logger to StateControllerConfig, however it was not passed through to the underlying stateControllerImpl. It is always nil as a result and NewState/UseState will always panic when called because of this.

thanks for the fix!


Modify patient card UI in reference app

Is your feature request related to a problem? Please describe.
Better visibility of patient info cards.
Without a horizontal border separating each card, the look gets very confusing.
Describe the solution you'd like
Card border around patient info cards.
Describe alternatives you've considered
Additional context

Would you like to work on the issue?
Yes

I want to work on this issue.

I have mad e some changes in the UI as per the issue...
https://github.com/google/android-fhir/pull/399

Thanks for creating this issue. This is low-priority. The UI of the reference app isn't something we want to spend a lot of time on.


Cmake fixes (windows port)

Changed several linux commands to their windows counterparts to enable unit tests under Windows.

Awesome, I wouldn't have been known how to implement this! Thanks!

Travis and CircleCI are complaining. I'll fix that later.


How to test promises?

I was looking for expect(Promise.resolve()).toBeFulfilled() or expect(Promise.reject()).toBeRejected(). Is there something like this?

There's no way to synchronously check the state of a Promise, so you'd have to do it asynchronously - and depending on your test framework, that can't really be done transparently in this framework.
In other words, you want promise.then(succeed).catch(fail) where success and fail depend on your test framework.

@ljharb If I understand you correctly, this should work (using Mocha's async handling with the done() callback):
describe('getThing()', () => {
    it('retrieves a thing by an id', (done) => {

      const spy = expect.spyOn(thingService, 'query')
        .andReturn(Promise.resolve({ name: 'My Thang', id: 'xxx' }));

      getThings('xxx')
        .then(thing => {
          expect(spy.calls.length).toEqual(1);
          expect(spy.calls[0].arguments).toEqual('xxx');
          expect(thing).toEqual({ name: 'My Thang', id: 'xxx' });
          done();
        });
    });
  });

getThings() is a function that runs thingService.query() behind the scenes and returns a promise with the result.
However, the .then call of getThings() is never being entered. Mocha keeps throwing me the standard timeout message that the done() doesn't get called at all.
Now, I tried putting the spy in a beforeEach first, but the result is the same.
I don't know if that's an issue with expect, which just doesn't handle promises or something?

Instead of the done callback, simply return the promise. mocha will wait on it, and will fail the test if the promise rejects.

Ah, thanks. Just read about this in Mocha's documentation and tried it, but I'm still getting the exact same error:
    it('retrieves a thing by id', () => {
      return getThing('xxx')
        .then(thing => {
          expect(spy.calls.length).toEqual(1);
          expect(spy.calls[0].arguments).toEqual('xxx');
          expect(thing).toEqual({ name: 'My Thang', id: 'xxx' });
        });
    });

So the error still seems to expect a done() callback?
Error: timeout of 2000ms exceeded. Ensure the done() callback is being called in this test.
Are we sure this has nothing to do with expect then, and is rather a Mocha issue here?

Found the problem, and it was to do with the way the dependent service was imported in the module being tested (see #169).


D2 doesn't start.

When I try to launch D2 it says "Error 25: A critical error has occurred while initializing Direct3D"
cnc-ddraw.log

Blizzard removed ddraw support in the newer versions (1.14*) so you'll have to use a older version such as 1.13c if you want to use cnc-ddraw.

oh, I see. Thanks for answering.


Atomic locks do not provide reliable mutual exclusion when using the file cache driver

Laravel Version: 9.23.0
PHP Version: 8.0.15
Database Driver & Version: none

Description:
The locks returned by FileStore are instances of the class CacheLock. CacheLock's implementation of the acquire method is not atomic when the lock timeout is 0 (the default):
https://github.com/laravel/framework/blob/053840f579cf01d353d81333802afced79b1c0af/src/Illuminate/Cache/CacheLock.php#L30-L50
When the lock timeout is 0, first a get and then a put is performed. When combined, these operations are not atomic and thus multiple actors can enter the critical section protected by the lock. The possibility for race conditions was already discussed in the PR https://github.com/laravel/framework/pull/35139 that introduced the change.
Proposed quick fix
A quick fix would be to always call $this->store->add even if  $this->seconds <= 0 because the store can handle 0 timeouts just fine:
public function acquire()
{
    return $this->store->add($this->name, $this->owner, $this->seconds);
}

There is no need to even check that the add method exists because it is the stores responsibility to return a compatible lock instance.
Proposed proper fix
The proper fix would be to write a custom lock implementation for each store. There already exists DatabaseLock, RedisLock, DynamoDbLock etc. which can guarantee mutual exclusion because their implementation is tailored to the specific store. There is no good way to write an abstract lock implementation that CacheLock attempts to be because the Store contract does not provide the necessary atomic primitives. Calling an undocumented add method on the store, which may or may not be atomic, seems like the wrong thing to do.
Steps To Reproduce:

I created a a repo that can pretty reliably reproduce the race condition:
https://github.com/hbgl/laravel-test-locks
Instructions:
git clone https://github.com/hbgl/laravel-test-locks
cd laravel-test-locks
composer install
php artisan app:test-locks --workers=2 --iterations=1000 --cache-driver=file

Thanks @hbgl, this was a well written issue. We'd very much appreciate a PR for one of the solutions you propose 👍


version:2.9.3  ， porMonitor for proxy doesn't get metric data, the prometheus report "server returned HTTP status 401 Unauthorized"

version:2.9.3  when I open the jwt feature for cluster, the porMonitor for proxy doesn't get metric data, the prometheus report "	server returned HTTP status 401 Unauthorized", but the podmonitor for bookie,broker,zookeeper is  noraml,  I know the http request need certify, but i don't know how to add the admin'token. How should I solve this problem?

hello @aa1215018028 , how about try adding this env to proxy configData:
proxy:
  configData:
    authenticateMetricsEndpoint: "false"

Version 2.9.3 isn't supported. Please check the release policy of Apache Pulsar here: https://pulsar.apache.org/contribute/release-policy/#supported-versions . Please upgrade to the latest version of the Apache Pulsar Helm chart and use the Pulsar LTS version 3.0.x  (3.0.2 currently).


Fixed docker image format

The action is down, try it outside the repo if posible (example here).

Thanks for the hotfix :+1:


#33-as a creater we need to be able to add an image-JustinasBrazauskasadd column for image url

Naming Rules
Name your PR like this: ISSUENUMBER-TITLE-YOURNAME
Description
column for image url
Related to
Make sure you include the issue number with a hash sign # so Github can link this PR to the right issue, like this:
Fixes #33
Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have carefully reviewed my own code
[ ] I have commented my code
[ ] I have updated any documentation

Is this PR only intended to add the one column? It seems it would break the frontend since I don't think the url_address is being submitted with the POST?

Is this PR only intended to add the one column? It seems it would break the frontend since I don't think the url_address is being submitted with the POST?
Bertil as we discussed earlier we need two columns one for image one for video address , this is what he needs help with now ,to make new push to this open PR


Create a Team page for the Website

I've create a simple Team Page. The end goal is to create a location where people can meet who contributes to IPFS, the IPFS Working Groups and on to join the conversation. It is very raw now and I wanted to make sure I collected everyone's ideas in advance.

When you're ready, @daviddias please post a screenshot of what you see locally so we can also assess the display, and make sure what you see is what we see when we run it.

Do we still want to add a Forum link to the nav or will we add the Forum link in the Community page? https://github.com/ipfs/website/pull/276

A simplified version of this is ready to go. I have a PR to blog ready to get the header navs to match up https://github.com/ipfs/blog/pull/225
I'll fix up the docs site header next, and merge it all tomorrow morning. 🚀

Thank you so much, @olizilla ❤


[Bugfix] Add init_cached_hf_modules to RayWorkerWrapper

FILL IN THE PR DESCRIPTION HERE
FIX https://github.com/vllm-project/vllm/issues/4285
RayWorkerWrapper miss init_cached_hf_modules for trust_remote_code
BEFORE SUBMITTING, PLEASE READ THE CHECKLIST BELOW AND FILL IN THE DESCRIPTION ABOVE

 PR Checklist (Click to Expand)
Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.
PR Title and Classification
Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

[Bugfix] for bug fixes.
[CI/Build] for build or continuous integration improvements.
[Doc] for documentation fixes and improvements.
[Model] for adding a new model or improving an existing model. Model name should appear in the title.
[Frontend] For changes on the vLLM frontend (e.g., OpenAI API server, LLM class, etc.)
[Kernel] for changes affecting CUDA kernels or other compute kernels.
[Core] for changes in the core vLLM logic (e.g., LLMEngine, AsyncLLMEngine, Scheduler, etc.)
[Hardware][Vendor] for hardware-specific changes. Vendor name should appear in the prefix (e.g., [Hardware][AMD]).
[Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.
Code Quality
The PR need to meet the following code quality standards:

We adhere to Google Python style guide and Google C++ style guide.
Pass all linter checks. Please use format.sh to format your code.
The code need to be well-documented to ensure future contributors can easily understand the code.
Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.
Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.

Notes for Large Changes
Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.
What to Expect for the Reviews
The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:

 After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.
 After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the vLLM team.
 After the review, the reviewer will put an  action-required label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.
 Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

Thank You
 Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!

@youkaichao

That's very strange. It is already there:
https://github.com/vllm-project/vllm/blob/0ae11f78ab89556d5d867abb98f8a132f7507269/vllm/worker/worker.py#L63-L67

@youkaichao RayWorkerWrapper is not derived from Worker class but WorkerWrapperBase. WorkerWrapperBase miss init_cached_hf_modules.

WorkerWrapperBase.init_worker will call Worker.__init__ , which will call the code i quote above, i.e. init_cached_hf_modules.

@youkaichao
https://github.com/vllm-project/vllm/blob/0ae11f78ab89556d5d867abb98f8a132f7507269/vllm/worker/worker_base.py#L100-L110

WorkerWrapperBase.init_worker will call Worker.__init__ , which will call the code i quote above, i.e. init_cached_hf_modules.

it seems not work now

@youkaichao WorkerWrapperBase is not derived from Worker class.

Worker class object is created here.
https://github.com/vllm-project/vllm/blob/0ae11f78ab89556d5d867abb98f8a132f7507269/vllm/worker/worker_base.py#L135-L138

vllm/vllm/worker/worker_base.py

may missing call init_worker in init method ? It seems only the init method is used in ray executor.
https://github.com/vllm-project/vllm/blob/0ae11f78ab89556d5d867abb98f8a132f7507269/vllm/executor/ray_gpu_executor.py#L94-L120

init_worker_all_kwargs

oh, thanks to point out that. but why not work for ray executor if tp >= 2?

I don't know. Need to ask a ray expert. Maybe @rkooo567

@youkaichao it seems the driver_woker did not add into self.workers, thus not call by _run_workers("init_worker", ...)
https://github.com/vllm-project/vllm/blob/0ae11f78ab89556d5d867abb98f8a132f7507269/vllm/executor/ray_gpu_executor.py#L104-L114

@youkaichao thanks for you reply. but unfortunately, without this fix, I cannot deploy the service using TP>=2 with trust_remote_code=True. I will use this PR as a hotfix first until vllm fixes this issue.

You can use it for your case. I will talk to ray experts to confirm if this is necessary.

by the way, this error has not been found at 0.4.0.post1

@simon-mo please add qwen in ci to avoid this happening again.

Can you guys tell me how to repro the issue? Just removing this code and use tp > 1 & enable trust_remote_code?

@rkooo567 python -m vllm.entrypoints.openai.api_server --model Qwen/Qwen-1_8B-Chat --tensor-parallel-size 2 --trust-remote-code.
But there also have problem when using --engine-use-ray.

I am going to take a look at this issue later today

Okay, I think the issue is some of inputs to init_workers contain refs to huggingface_modules. And when the object is serialized / deseiralized, Python reimports the module (I don't know which API is used to import the module here). I think since the module import is not trivial (we need to use this weird hf module loading API), it cannot find the module and fails.
I think the proposed solution here seems correct (in the __init__, we import the relevant module). Maybe we can move it to Ray specific worker class (though I think it can happen in other distributed tools that require serialization)

@rkooo567 the code used to have deepcopy for these args. I don't know if it is related. I removed deepcopy because I think ray should copy them anyway.
https://github.com/vllm-project/vllm/pull/4024/files#diff-4fc454dabd93d2c8a43a962360afe9753d139415326bc3097c99815bf0311736L147-L154

I actually tried deepcopy, but it didn't seem to work. My guess is as long as the input requires the huggingface_modules ,which cannot be imported through normal import (it looks like it is magically imported when init_cached_hf is called), the issue persists?

@rkooo567 @youkaichao there are some difference with Baichuan-13B-Chat and Yi-34B-Chat:

Baichuan-13B-Chat

cat Baichuan-13B-Chat/config.json
{
  "_from_model_config": true,
  "_name_or_path": "baichuan-inc/Baichuan-13B-Chat",
  "architectures": [
    "BaichuanForCausalLM"
  ],
  "auto_map": {
    "AutoConfig": "configuration_baichuan.BaichuanConfig",
    "AutoModelForCausalLM": "modeling_baichuan.BaichuanForCausalLM"
  },

Yi-34B-Chat

 cat Yi-34B-Chat/config.json
{
  "architectures": [
    "LlamaForCausalLM"
  ],

Baichuan-13B-Chat use auto_map with AutoConfig and AutoModelForCausalLM will hit this init error but Yi-34B-Chat not.

Guess this is exactly the case the config contains modules that require huggingface-modules?


add o-techdocs-container for o-techdocs 5 migration

Looks good :+1: feel free to merge once CI has done it's thing


feat: add test build type for android_build

Add test_build_type to build_android job and command.

@cortinico

Could you make an example on why this is needed @matinzd ?

In some react native projects there are different types of flavors are configured for the project based on the needs, but test flavors are not configured.

@matinzd now that the CI/CD pipeline has been fixed, this needs a rebase.
@cortinico if this is still useful feel free to merge. 🚀

@cortinico if this is still useful feel free to merge. 🚀

I don't have a strong opinion here. We're not using this orb internally and I'll leave the decision to merge to you folks


Possible problematic example in the guide "Automatic Differentiation"

URL(s) with the issue:
https://www.tensorflow.org/guide/autodiff
Description of issue (what needs changing):
In the calculation of gradient by passing a dictionary of variables,
my_vars = {
    'w': tf.Variable(tf.random.normal((3, 2)), name='w'),
    'b': tf.Variable(tf.zeros(2, dtype=tf.float32), name='b')
}

grad = tape.gradient(loss, my_vars)
grad['b']

It seems inappropriate since my_vars creates two new variables, but the pre-defined loss is not calculated from these two variables, and it turns out that no output from grab['b'].
I think there might be two possible modifications,

use the pre-define w and b in the dictionary

my_vars = {
    'w': w,
    'b': b
}
grad = tape.gradient(loss, my_vars)
grad['b']

define a new loss using my_vars

with tf.GradientTape(persistent=True) as tape:
    y = x @ my_vars['w'] + my_vars['b']
    loss = tf.reduce_mean(y**2)
grad = tape.gradient(loss, my_vars)
grad['b']

Note that persistent=True is particularly specified, so I guess the first choice might more agree with the author's initial purpose.

@szcf-weiya,
Can we close this issue as the linked PR is merged? Thanks!

@amahendrakar OK, thanks!


add osm file as fixtures

Related to https://github.com/osmlab/osmlint/pull/113#issuecomment-222711207  I created an OSM file for all the existing linters we have.

The idea is to replace existing mbtiles used for test fixtures.  OSM geometries related to a linter were labeled in the name key. For example, <tag k='name' v='unconnectedHighways' /> except for the untaggedways linter for obvious reasons.
We can use this file to generate individual mbtiles for each test fixture.  Data is in Null island:
--bbox="[-0.089,-0.089, 0,0]"
@arunasank @geohacker @Rub21

Rebased against https://github.com/osmlab/osmlint/pull/113. Closing.


Update osfa.py

added speak title and hello as well as os checking and macos support
(note does not include the batch processing if possible do not merge the entire file

closing because the tests failed


[core-util] Run Prepare Release Script

Packages impacted by this PR
core-util
Issues associated with this PR
Prepare an out-of-band release with a feature added & a bug fixed
Describe the problem that is addressed by this PR
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[ ] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

API change check
API changes are not detected in this pull request.


Missing image tag puts Flux in a weird state

Given:

A Helmrelease currently consumes image 123456789.dkr.ecr.eu-west-1.amazonaws.com/foo:1.0.1 which no longer exists in the repository
A new image  123456789.dkr.ecr.eu-west-1.amazonaws.com/foo:1.2.0  is published
Flux detects this new image, but does not upgrade as it cannot compare timestamps

ts=2019-05-28T07:26:46.716127145Z caller=images.go:107 component=sync-loop workload=test-fe:helmrelease/foo container=chart-image repo=123456789.dkr.ecr.eu-west-1.amazonaws.com/foo pattern=semver:^1.0 current=123456789.dkr.ecr.eu-west-1.amazonaws.com/foo:1.0.1 warning="image with zero created timestamp" current="123456789.dkr.ecr.eu-west-1.amazonaws.com/foo:1.0.1 (0001-01-01 00:00:00 +0000 UTC)" latest="123456789.dkr.ecr.eu-west-1.amazonaws.com/foo:1.2.0 (2019-05-28 07:15:57.401797549 +0000 UTC)" action="skip container"

A common use case which exposes this limitation is when Helmrelease is created before the actual image is published, and a random tag is used.
Flux should preferably just override the image tag when the previous one does not exist.

@michaelgeorgeattard how can know Flux whether it should actually replace the image if it cannot find the timestamp of the image?
I guess that we could obtain information from local images to fill the gap.

A common use case which exposes this limitation is when Helmrelease is created before the actual image is published, and a random tag is used.

The image cache is refreshed periodically, so things will work once the image is published

Linking in #1831 as the strictness it was introduced there.

I guess that we could try to obtain information from local images to fill the gap.

Uhm, that's not going to be easy, since flux and the image may live in different nodes

Flux should preferably just override the image tag when the previous one does not exist.

The problem is that we do not know why a tag does not exists;
:heavy_check_mark: it got removed
:red_circle: the registry has a temporary problems with listing tags
:red_circle: our cache is not up to date
...etc

I actually encountered this limitation by copy pasting another HelmRelease configuration, while leaving the old tag, which never existed for the new repository and will never exist. My hope was that Flux would detect a new tag being published and override the old (invalid, in-existing) tag.

In this case, I think you will have to edit the manifest to have the correct tag, and commit that to git. We introduced a check on the timestamps to avoid situations in which fluxd made an update without knowing for sure that it was safe, and erroneously downgraded images. Side-stepping the check would reintroduce that risk.


Any interest in exposing or extracting utilities?

Thank you for this project!  It's been very helpful and works great!
While this project works for the core React Native components, it doesn't help with other native components (such as react-native-camera).  However, the utilities and approach taken here work just fine with other components.
Is there any interest in exposing some utilities from this library, or extracting them to a different library and then using them from here?
I'm thinking particularly of createMockComponent and the code in mock.js, but there may be other reusable helpers as well.
In my project, I extracted a function out of mock.js that looks like this:
function registerNativeMock(pkg, component) {
  const key = require.resolve(pkg);

  require.cache[key] = {
    id: key,
    filename: key,
    loaded: true,
    exports: component
  };
}

Using this function, mock.js would end up looking like this:
const ReactNativeMock = require('./build/react-native');

registerNativeMock('react-native', ReactNativeMock);

If this idea is of interest, let me know which direction you'd like to go (expose or extract), and I'll be happy to put together a PR.
Also, if you can identify any additional utilities that might be useful when mocking other libraries, point them out and I'll include them.

Something like this isnt really in the scope of this project. as the components youre looking to mock arent actually a part of react-native. However, instead of rolling your own mocking function, I recommend using https://github.com/mfncooper/mockery, it works great for exactly what youre doing!


ENH: Support of parent references in XPath

What Happens?
When you have an XPath expression with references to the parent node, it does not generate data. The problem is in the use of findall function in this line as it only allows access to the children in the tree, see the documentation
To Reproduce
Data and Mapping are attached, together with the desirable output generated using the RMLMapper v6.1.2
data_mapping_output_xpath.zip
Environment (please complete the following information):

OS: macOS Ventura 13.0.1
Python version: 3.9.6
Morph-KGC version: 2.2.0

This is a feature of the RMLMapper (as @jatoledo and @ocorcho know well) that is not enforced by the RML specification.

I close this issue since it is part of #294.


Limitation of the current gluonnlp.data.dataset.transform()

Description
Consider adding a flatten arguement to the nlp.data.dataset.transform()?
The current nlp.data.dataset.transform() applies a transform function fn on each example in the dataset.
    def __getitem__(self, idx):
        item = self._data[idx]
        if isinstance(item, tuple):
            return self._fn(*item)
        return self._fn(item)

So that it assumes each item only be converted to one fn(item). But in some cases, for example, squad dataset, we would use the sliding window to get several doc spans. So for each example in dataset, we would have a number of transformed examples, e.g., fn(item) can be a list. Thus we may need to flatten it manually after we call call transform().
So I think maybe it could be better to have a flatten argument in transform() directly? For example:
    def transform(self, fn, lazy=True, flatten=False):
        trans = _LazyTransformDataset(self, fn)
        if lazy:
            return trans
        if flatten:
            return SimpleDataset(list(itertools.chain.from_iterable([i for i in trans])))
        return SimpleDataset([i for i in trans])

References

list reference and related literature
list known implementations

While I agree that the stated problem should be solved, adding a flag may not be the best approach because:

it complicates the interface by introducing diverging behavior to the same function.
it relies on the return type of the transform function and thus makes it error-prone.

flatten flag would not report error for regular tuple items, which would make it hard for catching the error.

One alternative could be that we have an explicit flatten member function in dataset that is not mixed with transform, which avoids the above two problems. It can handle the one-to-many case similar to the squad sliding window case described in the issue.
The dataset base class is in Gluon, so the change proposal should eventually be moved there.

Great advice! Sorry I didn't check carefully and just assumed the dataset class is under gluonnlp. I will follow your suggestion.


Support to Add,Update,Delete, and List OpenShifts

Checklist

[ ] Affected Issues have been mentioned in the Closing issues section
[x] Documentation has been written/updated.
[x] Changelog entry has been written

Add support for adding, updating, deleting, and listing openshifts in a lagoon
Changelog Entry

Feature - New commands to interact with openshift objects in the lagoon api

closing in favour of #224


SUTime functionality

According to Stanford's website, SUTime is provided automatically in corenlp. Is it included in this wrapper as well? If so, is there any documentation or can anyone provide an example as to how to use it (specifically to go from tagged entities to storing/printing a TIMEX3 object)?

This is not currently supported in the wrapper, but I could add it. Will keep you updated on this thread.

Hey,
Install pynlp==0.4.2
pip3 install pynlp --upgrade
To get all the timex objects:
doc = nlp(text)
timexs = {entity.timex for entity in doc.entities if entity.timex}

For representations
print(timexs)

For text and other attributes tid, value, type, text
for timex in timex:
    print(timex, timex.tid) # for example

Note that i used python set() to get all the timexs. This is because CoreNLP works in such a way
"Saturday" and "afternoon" in "Saturday afternoon"  both give the same timex.
Any questions or bugs, please let me know.
Will update the docs soon.

What annotations did you use here?

Thanks for adding this!
Sorry this has taken so long; I've been messing around with timex but all the timex values I'm getting are blank. Following your code above exactly and with the text "In 1985, Reagan was in office.", "1985" has a non-null timex. However, when I print the entity.timex on "1985", I get:
{<Timex: [tid: , value: , type: ]>}
I'm thinking it has to do with the fact I set ner.useSUTime to False, but I can't run my code without getting a pynlp.exceptions.CoreNLPServerError error without it set to True. Is there an alternative to this, or is it another issue?

Could you show me the same excerpt but with repr(timex) instead of timex.text?
 When I print timex._timex, it shows up:
altValue: "PREV_IMMEDIATE 2500"
text: "the last 2500"
type: "DATE"
tid: "t23"

compared to:
value: "1300"
text: "1300"
type: "DATE"
tid: "t4"

However, running print(timex.altValue) in the try/except block returns nothing like it's not there.
Furthermore, running print(entity.normalized_ner) returns the altValue when it exists and value when that exists. I've tried passing a time for ner to use using ner.providedDocDate and also setting ner.usePresentDateForDocDate to true but neither converted the altValues to an absolute date. Should coreNLP convert the offsets to an absolute date, or should I be doing that myself?


fix UnicodeDecodeError

fix UnicodeDecodeError for MDX dictionaries that use utf-8 instead of utf-16 for metadata

json.detect_encoding   ? Is it a function?
Which dictionary used utf-8 encoding? Which APP compiled the dictionary?


Extend hash to biblio mappers

This is part of the Relaton YAML refactor. https://github.com/metanorma/relaton-bib/issues/7

Currently this gem and relaton-nist breaks because you have not updated the encoding of roles from metanorma/relaton-bib#6.
This is why it is important to do releases not immediately, but only when the entire stack is synchronised. @CAMOBAP795 is creating scripts for both of us to manage releases in our stacks.

@opoudjis I don't finish release yet. I updated roles but didn't push it. The sack is synchronized on my local machine.
I don't like to push a lot of commits fixing small issues. Maybe I had to use branches in this case. Merging branches allows squeezing all commits into one.