Update install.md

Installation instruction update. Use latest libsodium  from https://github.com/input-output-hk/iohk-nix/commit/ceb181d109a427e22184928221b85f313d1594ab

I spent some time today trying to figure this out, only for somebody to link me this PR. I guess I was correct that the new sodium fork should be used from the new "audited" branch. By the way there is another commit on there after this one, that says "for backwards compatibility" but I'm guessing that's not needed?
However, my question is around this:
https://github.com/input-output-hk/cardano-node/commit/797289144ad87d494603f19b301e6dbf93310f81
The official documentation, states that it's "okay" to use the ported cbits with the " package cardano-crypto-praos   flags: -external-libsodium-vrf " option with the release version of libsodium ( libsodium/stable v1.0.18 ).
Is this still correct information, to be used in production? Or should this be removed as a recommendation as part of this install.md update?

@CarlosLopezDeLara I'm not sure. It was updated in https://github.com/input-output-hk/iohk-nix/pull/522. We now have the situation where the cardano-node 8 release notes reference what was merged in https://github.com/input-output-hk/iohk-nix/pull/520, yet, iohk-nix we use in our nix builds, has https://github.com/input-output-hk/iohk-nix/pull/522.
The difference is effectively only https://github.com/input-output-hk/libsodium/commit/dbb48cce5429cb6585c9034f002568964f1ce567 commit. Are we certain we don't need the backwards compatibility anymore?

@iquerejeta maybe you got some input here :-)

As mentioned in Discord We're updating the docs to remove mentioning the external VRF hack. Here's the official position regarding using it in production:
In summary, it's not known to be wrong, rather it's not known to be ok, and since this is critical to security, the cautionary principle says don't use it in production.
The libsodium library has certain supported and documented ways to build and use the library. In particular it involves building the whole library using libsodiums own build system. Turning off the external-libsodium-vrf flag (and thus using the bundled C code instead) does neither of these things: it only builds little bits of libsodium and does not use the libsodium build system. So from the perspective of the libsodium developers it is not a supported configuration. For that reason it's not something we can currently recommend to use in production

What about secp ? Is recommendation to still use unreleased version?  https://github.com/bitcoin-core/secp256k1/releases/tag/v0.3.1  release versions now include schnorrsig by default it seems. In fact I built 8.0.0 with v0.3.1 minting blocks on preview right now with it.  Also seen on github devs are using it also?

closing in favor of https://github.com/input-output-hk/cardano-node/pull/5181

What about secp ? Is recommendation to still use unreleased version? https://github.com/bitcoin-core/secp256k1/releases/tag/v0.3.1 release versions now include schnorrsig by default it seems. In fact I built 8.0.0 with v0.3.1 minting blocks on preview right now with it. Also seen on github devs are using it also?

does cardano support secp256k1 transaction?

Hi @zhp1254 . Yes, secp256k1 transactions are supported. Here you can find an example https://github.com/input-output-hk/antaeus/blob/main/e2e-tests/test/Spec/Builtins/SECP256k1.hs


[Feature Request] Provide a way to export current color styles as tailwind.config.js

Once #80 is done it would be nice to be able to export the current color styles to a tailwind.config.js.
This would allow to easily modify the colors in the js file and then use the import feature to update the colors on Figma.
It would also allow to update the tailwind.config.js if, for example, some color changes are made directly in Figma.
If there are forbidden characters in the color name (e.g. spaces), those can simply be removed while exporting.

@impulse I think there was an error in what the PR from @KA95DEV was actually closing: there is no export feature in #87
Could this issue be reopen? I still think would be a really nice addition to be able to export the styles to a file, for example for people that is not using TailwindCSS but that want to simply batch edit their colors on a text editors instead of doing it in Figma, where it takes forever since you have to do it one by one.

Yeah, 👍

@leinardi @impulse  here you go. this works for my needs https://www.figma.com/community/plugin/809138746390300395/%40nju33%2Ftailwindcss

@daugaard47 thanks! Will still look to add this in the feature to eliminate the need for installing multiple plugins.


[BUG] <Using the Divide plugin to proxy WMS service status code 400>

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Using the Divide plugin to proxy WMS service status code 400, the original address is in normal use
originalUrl：http://<IP_ADDRESS>:26160/igs/rest/ogc/doc/金华幅/WMSServer
Expected Behavior
No response
Steps To Reproduce
No response
Environment
ShenYu version(s):

Debug logs
No response
Anything else?
No response

whats version?  can you show log?

whats version? can you show log?

2.5.1  No logs


Update aws-java-sdk-bundle to 1.12.284

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

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.amazonaws", artifactId = "aws-java-sdk-bundle" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "com.amazonaws", artifactId = "aws-java-sdk-bundle" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #2291.


W.check_simulation_ongoing() fails to detect simulation end under certain conditions

By using this kind of code, uxsim can be run incrementally in order to make intervention like reactive traffic control
while W.check_simulation_ongoing():
    # Execute the simulation in increments of 10 seconds
    W.exec_simulation(duration_t=10)

However, W.check_simulation_ongoing() fails to detect simulation end sometimes. This is due to mistakes in handling the edge of the list index. I almost identified the mistake, but I dont have time to fix now, so I share this information.
Workaround: for most cases, it is okey to ignore the error by using try-except. Otherwise, please set sufficiently large duration_t value at the end of simulation duration

Hopefully this is fixed by https://github.com/toruseo/UXsim/pull/126


I can pack build simple (MRI) Ruby HTTP apps using packit library

Context
We should re-write the MRI CNB using packit so that we have improved logging output functionality.
Acceptance Criteria
GIVEN I have a Ruby app that requires no Gems
WHEN I pack build it
THEN I can see that packit style logging appears during Ruby detection
AND when I docker run the app it works

Implemented as a part of https://github.com/cloudfoundry/mri-cnb/pull/4

Acceptance:
Grab latest MRI CNB release
wget -O /tmp/mri-cnb.tgz https://github.com/cloudfoundry/mri-cnb/releases/download/v0.0.97/ruby-cnb-0.0.97.tgz
--2020-04-23 11:59:06--  https://github.com/cloudfoundry/mri-cnb/releases/download/v0.0.97/ruby-cnb-0.0.97.tgz
..............
2020-04-23 11:59:11 (1.56 MB/s) - ‘/tmp/mri-cnb.tgz’ saved [6235074/6235074]

Pack build a simple ruby app (https://github.com/cloudfoundry/mri-cnb/tree/master/integration/testdata/simple_app) using downloaded buildpack and Paketo full builder
pack build mri-ruby-app --buildpack /tmp/mri-cnb.tgz --builder gcr.io/paketo-buildpacks/builder:full-cf
full-cf: Pulling from paketo-buildpacks/builder
..........................
Status: Downloaded newer image for gcr.io/paketo-buildpacks/builder:full-cf
full-cnb-cf: Pulling from paketo-buildpacks/run
Digest: sha256:c3f90713f0f6b5cdce3fcb3ee3e1e46ec0f7e1209741b5144a0883f17ae51532
Status: Image is up to date for gcr.io/paketo-buildpacks/run:full-cnb-cf
===> DETECTING
[detector] org.cloudfoundry.ruby-mri 0.0.97
===> ANALYZING
[analyzer] Restoring metadata for "org.cloudfoundry.ruby-mri:ruby" from app image
===> RESTORING
===> BUILDING
[builder] Ruby MRI Buildpack 0.0.97
[builder]   Resolving Ruby MRI version
[builder]     Candidate version sources (in priority order):
[builder]       buildpack.yml -> "2.7.x"
[builder]
[builder]     Selected Ruby MRI version (using buildpack.yml): 2.7.1
[builder]
[builder]   Reusing cached layer /layers/org.cloudfoundry.ruby-mri/ruby
[builder]
===> EXPORTING
[exporter] Adding layer 'launcher'
[exporter] Reusing layer 'org.cloudfoundry.ruby-mri:ruby'
[exporter] Reusing 1/1 app layer(s)
[exporter] Adding layer 'config'
[exporter] *** Images (0e4058111ed1):
[exporter]       index.docker.io/library/mri-ruby-app:latest
Successfully built image mri-ruby-app

Verified that packit style log output shows up.
Run the app image
docker run -p 8080:8080 -e PORT=8080 mri-ruby-app "ruby run.rb"

looks great!


Unified strategy for providing localized title and aria label for icons within components

🧹 Tech Debt
There are several places where components display icons. Each of these might benefit from:

setting title so that sighted users can hover over them to see the icon explained in a tooltip
setting aria-label or other attributes so that screen reader users can understand their purpose
Those strings should be localized. Since we've decided that localization is an application concern and not a Nimble concern, we need to provide (hopefully consistent) APIs for clients to supply these strings.

We may also decide not to set title and to exclude the icon from the accessibility tree if its meaning is provided in other ways. We should consult with Leslie and with web best practice docs to come up with guidance for this.
The icons we've identified so far:

increment/decrement buttons on numeric text input #617
action menu button in table cells #859
sort icon in table header (and soon other icons from #885 like grouping, collapse all, column menu)
banner and tooltip severity

This will also inform related work like the following, though the solution might be different:

#1013
icons as the primary content of a table column header

Goals

Document policy about when providing this content is necessary
Decide on an approach that's consistent across components
Document that approach
Ensure the work to adopt the approach for existing and known future use cases is tracked

Possible Implementations
@rajsite had some ideas around supplying content via attributes vs slotting but I'll let him summarize them.

We need to make sure that the solution is scalable because some components, such as the table will have many strings that need to be localized. For example:

label & tooltip for Collapse All button
label & tooltip for Collapse Group/Row button
label & tooltip for Toggle selection of all rows checkbox for whole table & group rows
label & tooltip for Toggle selection checkbox
Menu item text for items in the column menus -- Sort ascending, Sort descending, Group by column, Size to fit, etc

Options brainstorming:
Slots
Create slots per localized string on the element.
<nimble-table>
   Hello World
</nimble-table>

Pros:

Useful for mixed content (if that is even needed, maybe not?)
Can maybe make shareable slotted content within a framework

Angular: Create a shared component that emits elements with those slots
Blazor: I expect a blazor component written that way would work too

Slots can have default content easily

Cons:

DOM gets littered with many additional elements for providing localized strings
Lots of duplicated slotted content / elements. Have to emit into every table element as children.

Attributes
Create attribute per localized string on the element.
<nimble-table
    collapse-all-button-label="Hello World"
></nimble-table>

Pros:
- Easy discovery of available properties? Type checked in Angular at least

Cons:
- Maybe not as easy to share / reuse attribute configuration?
    - Angular: Might need to write a custom directive that will emit the attributes onto the host. I think that works
    - Blazor: ?
- Lots of duplicated attributes. Have to emit into every table element as children.
- Only text content (maybe that's okay)

## Design Tokens

Conceptually the localized strings are very similar to the sharing pattern of Design Tokens. Vast majority of the time you want to use the same value (increment button text or collapse button text is not control instance specific) but want to adjust to a global config, i.e. theme or language. But also want to be able to override for specific controls as needed.

Create non-css property design tokens, similar to the theme and direction design tokens.
Use the theme-provider to define the value.

Pros:
- Easy discovery of localized string configuration. They are all on the theme-provider.
- Can configure once for the whole page in one spot, does not need to be per control. Much fewer duplicated attributes / slotted elements in the page.
- Can override for specific elements as needed by wrapping in a theme-provider.
- Can configure to be attribute or slotted on the theme provider. But if don't need mixed content then attribute makes sense.

Cons:
- Abuse of the tokens system / not intended use-case?

The theme provider is a cool idea. Another pro is that we could likely single-source the strings in a way that each SLE app doesn't need their own list that would need to be updated every time Nimble adds a new string. For example, we could create sl-theme-provider in systemlink-lib-angular with a child nimble-theme-provider that has all the strings tagged for i18n.
half formed brainstorming👇
That made me realize that it would be cool to have a way for apps to get a list of English Nimble strings that need to be translated. Ideally that list could be imported into the app's localization infrastructure so that they'd automatically get the English version, automatically trigger translation to other languages, and automatically pick up new strings that we add.
How do Angular apps extract strings from their dependent libraries? Could we mark up nimble-angular in the same way we do systemlink-lib-angular and have apps translate the strings inside it? Then it'd be nimble-angular's responsibility to consume the translated strings to configure each component, possibly using one of the approaches above. (I'm not sure when this code would run)
For Blazor, is there a way we could publish a resx file of English strings for apps to translate and then have NimbleBlazor use the translated resx files?


Error: Objects are not valid as a React child

I have a Plone 6.0 site with Volto 18, volto-light-theme, and collective.volto.formsupport (tried 2.7.0 and 3.0.2).  volto-form-block 3.7.3 works fine.  But when using latest volto-form-block 3.8.2 (or 3.7.4 or 3.7.5) I get this error when submitting a form:
    Objects are not valid as a React child (found: object with keys {message}). If you meant to render a collection of children, use an array instead.

    p
    div
    Message@http://localhost:3001/static/js/client.js:317567:29
    FormResult@http://localhost:3001/static/js/VoltoFormBlockView.chunk.js:700:20
    InnerLoadable@http://localhost:3001/static/js/client.js:2179:34
    div
    Segment@http://localhost:3001/static/js/client.js:321861:18
    div
    div
    FormView@http://localhost:3001/static/js/VoltoFormBlockView.chunk.js:825:18
    ValidateConfigForm@http://localhost:3001/static/js/VoltoFormBlockView.chunk.js:1172:28
    View@http://localhost:3001/static/js/VoltoFormBlockView.chunk.js:1358:14
    InnerLoadable@http://localhost:3001/static/js/client.js:2179:34
    StyleWrapper@http://localhost:3001/static/js/client.js:90646:7
    MaybeWrap@http://localhost:3001/static/js/client.js:130418:9
    div
    MaybeWrap@http://localhost:3001/static/js/client.js:130418:9
    RenderBlocks@http://localhost:3001/static/js/client.js:67113:7
    div
    $2e5fe81f2b094176$export$42a852a2b6b56249@http://localhost:3001/static/js/client.js:364550:122
    DefaultView@http://localhost:3001/static/js/client.js:156415:7
    injectIntl(DefaultView)
    div
    View@http://localhost:3001/static/js/client.js:157707:5
    ConnectFunction@http://localhost:3001/static/js/client.js:242834:103
    injectIntl(Connect(View))
    Route@http://localhost:3001/static/js/client.js:247979:29
    Switch@http://localhost:3001/static/js/client.js:248185:29
    main
    div
    Segment@http://localhost:3001/static/js/client.js:321861:18
    MultilingualRedirector@http://localhost:3001/static/js/client.js:152642:7
    PluggablesProvider@http://localhost:3001/static/js/client.js:131757:28
    App@http://localhost:3001/static/js/client.js:149041:5
    ConnectFunction@http://localhost:3001/static/js/client.js:242834:103
    injectIntl(Connect(App))
    ConnectFunction@http://localhost:3001/static/js/client.js:242834:103
    Route@http://localhost:3001/static/js/client.js:247979:29
    Switch@http://localhost:3001/static/js/client.js:248185:29
    Route@http://localhost:3001/static/js/client.js:247979:29
    AsyncConnect@http://localhost:3001/static/js/client.js:162047:5
    AsyncConnectWithContext@http://localhost:3001/static/js/client.js:162166:9
    C@http://localhost:3001/static/js/client.js:248240:31
    ConnectFunction@http://localhost:3001/static/js/client.js:242834:103
    ScrollToTop@http://localhost:3001/static/js/client.js:167133:1
    ConnectFunction@http://localhost:3001/static/js/client.js:242834:103
    Router@http://localhost:3001/static/js/client.js:247608:30
    ConnectedRouter@http://localhost:3001/static/js/client.js:16501:22
    ConnectedRouterWithContext@http://localhost:3001/static/js/client.js:16607:19
    ConnectFunction@http://localhost:3001/static/js/client.js:242834:103
    IntlProvider@http://localhost:3001/static/js/client.js:239501:9
    ConnectFunction@http://localhost:3001/static/js/client.js:242834:103
    Provider@http://localhost:3001/static/js/client.js:242542:18
    CookiesProvider@http://localhost:3001/static/js/client.js:191616:28

Since this error first appears for me in 3.7.4, it should be related to PR #94 by @giuliaghisini .  Any idea?

i think it's not relateed to that pr.
We are using latest versions of volto-form-block and collective.volto.formSupport with some customizations but not on that specific part where error comes up.
Could you make some debug end eventually make a pr ?

I have a PR with a fix.
Just for the record: I had the problem on Volto 18 with volto-light-theme, but I tried in a fresh Volto 17 project and this had the same problem that the form could not be submitted.

@mauritsvanrees that PR doesn't fixes the problem and introduces another error.
i've revrted your pr.
formState.result is a state var that is created with received backend response that should be like this.
{   "data": [     {       "field_id": "1715689298710",        "label": "Testo lungo",        "value": "klkl"     }   ] }
if you don't obtain that response from server, maybe you have to check your Plone addons installed and their versions, or if you have something in the middle that changes the response format.

@giuliaghisini Thanks you! Yes, the response looks exactly as you describe. But still at this line formState.result is an object like that:
{
   "data": [...],
   "message": "Form successfully submitted",
}

which can not be rendered without error like that:
{formState.result}
.
In my opinion the fix should be:
{formState.result.message}

@mbarde your're right! colud you make a pr for this please?

@giuliaghisini PR: https://github.com/collective/volto-form-block/pull/103

I see the same, an Object with a message and data.  Copied from console:
Object { message: "Form successfully submitted", data: (1) […] }

data: Array [ {…} ]

0: Object { field_id: "1718372796037", label: "Who?", value: "dsfdgdfs" }

length: 1

<prototype>: Array []

message: "Form successfully submitted"
```

Sorry for the mess.  Somehow my PR fixed it for me, and I was surprised that it worked for you without it.  I fixed it as best I could, but my frontend dev and debug skills need work. :-)


Cargo publish

Motivation
crate publish effect to push Rust packages to crates.io.
Tested on https://github.com/mlabs-haskell/plutus-ledger-api-rust/pull/38
Maintainer checklist

[x] Documentation (function reference docs, setup guide, option reference docs)
[x] Has tests (VM test, free account, and/or test instructions)
[x] Is the corresponding module up to date?

I've set up CI with staging.crates.io. (log)
Could you confirm that it still meets your needs after my changes?

Tested it, and pushed a new release: https://github.com/mlabs-haskell/plutus-ledger-api-rust/tree/v0


Http request testing (mock server in separate binary)

Alternative approach to https://github.com/newsboat/newsboat/pull/2736.
Http test server is now contained in a separate binary to avoid increasing the size of the regular newsboat/podboat binaries.
The C++ test code communicates with the http test server using (piped) stdin/stdout.
Marking as draft for now as I still plan to review the changes myself (but created a PR already to get some early CI feedback).

coverage: 60.388% (+0.6%) from 59.767%
when pulling dd7818ab58dca358f6b13bce7f1b8e384ce6ad6e on dennisschagt:http-request-testing-separate-server-binary
into ffc9e3d14da753f4889930517892e64ab1c89ade on newsboat:master.

This is an excellent piece of engineering!

Thanks!

why did you go with separate binary and communicating via stdin/stdout? Was there problems with putting http_mock into a Rust library and providing an interface to it via cxx?

Indeed, there were some problems with providing an interface via cxx.
I could not provide those via our already existing libnewsboat-ffi crate because that would negatively influence the binary size of the newsboat/podboat executables (as discussed in https://github.com/newsboat/newsboat/pull/2736#issuecomment-2061912827 + https://github.com/newsboat/newsboat/pull/2736#issuecomment-2067638989))
However, using cxx again in a separate crate didn't work either. When linking the tests to both libnewsboat-ffi and the testing-only crate, I ran into a lot of duplicate symbol definitions. This seems to be a known issue (see for example https://github.com/dtolnay/cxx/issues/883 or https://github.com/dtolnay/cxx/issues/252). It might be possible to work around that but I did not get that to work and I prefer an easier to understand solution.

Conflicting files
Cargo.lock

Just seeing this conflict now.
I will rebase this PR in a moment.

I believe I've handled all comments.
I don't expect any issues, but just to be safe, it might be nice to wait with merging this PR until just after the upcoming release.

I had to rebase due to a merge conflict in the Cargo.lock file.
Enabling auto-merge as this was previously approved.
Thank you for the review!


Change count value in field array to 1 for X,Y,Z.

I was trying to use ZeroSim to test an algorithm that filters point clouds using the PCL, although the output of the LIDAR 3D sensor can be properly displayed in RViz, my algorithm was not working. I believe the issue is that the count field in the point field array is currently being set to the total number of points. Based on https://answers.ros.org/question/234455/pointcloud2-and-pointfield/
I believe the correct value for this field is 1. Setting the value of count for the fields X, Y, and Z when I receive the message in my node allows my algorithm to run correctly.
I have made that change in the proposed PR.

@pedro1713  Fantastic!  This is why we do open source!  :-)


Value index not properly removing value

https://atomicdata.dev/agents/publicAgent appears in https://atomicdata.dev/properties
What could have caused this?

The property existed before, but has been removed. The value cache is not properly updated.
Something else?

I tried running with --rebuild-index, and it fixed the issue. I think the value cache does not update properly in some cases

[ ] Add value index test for changing a property-value (unless one already exists)
[ ] Add value index test for removing a resource

I was able to reproduce this by chaning the parent of the default /setup resource, which seems to be a simple thing to add to tests.


Extract Embedding Model after training

So we have a (shared) embedding network that receives 1 input and outputs 1 embedding. We then build a triplet loss network around it that takes 3 inputs and outputs the loss which we train to minimize the loss. After we've trained our triplet loss network I'd like to use the embedding network without the triplet network. How would we access the "inner" embedding network? My goal is to be able to generate 1 embedding for 1 input.

@manuelhuber i met the same problem, have you solved it?


From Results, link each Candidate to a page about them

As a Voter I would like to read more information about my matched candidates.
For each Candidate, insert a hyperlink to a web page about them.
It could be a campaign homepage, a Facebook page. If  The Virginia-Pilot publishes a Q&A online we can link to that.

Fixed in #262 and #263


[Feature Request]: Document perms and auth tokens

Implementation ideas
Need an equivalent of this in our (node) docs (godoc + markdown/running node):

https://docs.filecoin.io/developers/reference/json-rpc/introduction/#permissions
https://docs.filecoin.io/developers/reference/json-rpc/introduction/#authentication

Useful info from @renaynay:

You have you init + start a node, then from command line, do

celestia <node_type> auth [public|read|write|admin]

That is actually sufficiently covered by the help on CLI:
celestia light auth --help                                                                                15:29:27
Signs and outputs a hex-encoded JWT token with the given permissions. NOTE: only use this command when the node has already been initialized and started.

Usage:
  celestia light auth [permission-level (e.g. read || write || admin)] [flags]

https://node-rpc-docs.celestia.org/


Chnage sodium-native to sodium-javascript

Need to change sodium-native to sodium-javascript for working in webpack

v5 uses universal :)


IOS Info.plist not reading the variables

Dependency versions:
React Native: 0.64.2
React Native Config: 1.4.5
I'm using RNC to help with changing the deployment keys for CodePush. I've followed the instructions in the Read.me and after checking my tmp.xcconfig I can see the environment variables are correct.
I've also added the following to the "Pre-actions" for "Build" and "Run":
cp "${PROJECT_DIR}/../.env.development" "${PROJECT_DIR}/../.env"
"${SRCROOT}/../node_modules/react-native-config/ios/ReactNativeConfig/BuildXCConfig.rb" "${SRCROOT}/.." "${SRCROOT}/tmp.xcconfig"

The "Provide build settings from" drop down menu has the Target as the selection and is not empty.
When I run the project I'm getting an error saying the deployment key is invalid. This error goes away and the update from Codepush is downloaded without issue when i paste the key as is in the Info.plist instead of using $(PUSH_KEY) as the value.
What am I doing wrong? Has anyone else encountered this issue?

@MosefAsad Are you running the app from the command line using react-native run-ios? If so, you'll need to set the envfile in the rn script when running locally like so:
ENVFILE=.env.development npx react-native run-ios

@ryanliszewski I have and it works when I do but I should be able to run the IOS version of the app from Xcode and still have it expose variables to Info.plist as per the instructions outlined in the Read.me. There was a different project I worked on where we had the option of running through either the command line OR through Xcode. In either case, the Info.plist got updated correctly.

@ryanliszewski u saved my life

@luancurti I'm still facing this issue. I confirmed that my package has the fix you made above. Here is my react-native info output. Using the react-native-config 1.5.1 and followed all instructions.  I would really appreciate your input.

System:
OS: macOS 12.6.3
CPU: (4) x64 Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz
Memory: 35.75 MB / 8.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 18.15.0 - /usr/local/bin/node
Yarn: 1.22.19 - /usr/local/bin/yarn
npm: 9.5.0 - /usr/local/bin/npm
Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
Managers:
CocoaPods: 1.12.0 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.1, iOS 16.1, macOS 13.0, tvOS 16.1, watchOS 9.1
Android SDK: Not Found
IDEs:
Android Studio: 2021.3 AI-213.7172.25.2113.9123335
Xcode: 14.1/14B47b - /usr/bin/xcodebuild
Languages:
Java: 17.0.5 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 18.2.0 => 18.2.0
react-native: 0.71.4 => 0.71.4
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
info React Native v0.72.3 is now available (your project is running on v0.71.4).
info Changelog: https://github.com/facebook/react-native/releases/tag/v0.72.3
info Diff: https://react-native-community.github.io/upgrade-helper/?from=0.71.4
info For more info, check out "https://reactnative.dev/docs/upgrading".


Update CodeBuild CI detection to use CODEBUILD_CI env var

Purpose
What is the context of this pull request? Why is it being done?
Update CodeBuild CI detection to use CodeBuild's environment variable for CI: CODEBUILD_CI
Notable Changes
Are there any changes that need to be called out as particularly tricky or significant?
N/A
Tests and Risks?
Is this covered by existing tests? New ones? If no, why not?
Yes
Update the SHA1SUM file
Also make sure that you update the sha1 hash by running sha1sum codecov and updating the SHA1SUM file with the output
Updated the SHA1SUM file

@ibrahim0814
Hi Ibrahim, Could you please take a look at this pull request? Thanks!

Thank you @rasarora Can I ask you to update the SHA1SUM file again, please?

@drazisil
I synced the branch with the existing codebase and updated the SHA1SUM file

Requested deployment.


 Makes using ShapeRenderer not possible.
Which actually worries me a bit, I was debating on using LibGDX for something, but I'm unsure if there are other hidden issues at the moment with other portions of the library which fails on newer hardware or something.

Please search for similar closed/open issues before creating a new one: https://github.com/libgdx/libgdx/issues/3790

Sorry missed it, glad it's resolved.


[Python environment]

Expected Behavior

It supposed to run successfully after I changed some variables of config.json to
"environment": "backtesting", // "live-paper", "backtesting", "live-interactive", "live-interactive-iqfeed"
// algorithm class selector
"algorithm-type-name": "BasicTemplateFrameworkAlgorithm",
// Algorithm language selector - options CSharp, Python
"algorithm-language": "Python",
//Physical DLL location
"algorithm-location": "../../../Algorithm.Python/BasicTemplateFrameworkAlgorithm.py",
//"algorithm-location": "QuantConnect.Algorithm.CSharp.dll",
//"algorithm-location": "../../../Algorithm.Python/BasicTemplateFrameworkAlgorithm.py",
Actual Behavior

It reported some bugs .
20230809 23:36:51.038 ERROR:: Loader.TryCreatePythonAlgorithm():  Python.Runtime.BadPythonDllException: Runtime.PythonDLL was not set or does not point to a supported Python runtime DLL. See https://github.com/pythonnet/pythonnet#embedding-python-in-net
---> System.MissingMethodException: Failed to load symbol Py_IncRef: dlsym(RTLD_DEFAULT, Py_IncRef): symbol not found
at Python.Runtime.Platform.PosixLoader.GetFunction(IntPtr dllHandle, String name)
at Python.Runtime.Runtime.Delegates.GetFunctionByName(String functionName, IntPtr libraryHandle
Potential Solution

Reproducing the Problem

download the project and change the config.json.
System Information

Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues

[x] I have provided detailed steps to reproduce the issue

I have installed the conda and modified PYTHONNET_PYDLL . It seems the path is empty when it tried to load Python DLL

Hey @countif!
Sorry we can't give support for direct local installations of Lean project (too many variables, making it very complex). Suggest instead using our lean cli tool which makes it much easier, please take a look at our documentation for detailed information.


Unexpectedly slow benchmark run

I noticed huge variances on the runtime of https://github.com/mirage/irmin/pull/1441
wall/cpu time of some runs of the tree.exe benchmark (these timings are recorded from within tree.exe (the benchmark program)):

25min13s/2min10s: http://autumn.ocamllabs.io:8081/job/2021-06-03/225705-docker-pread-718e47
1min18s/1min18s: http://<IP_ADDRESS>:8081/job/2021-06-03/171324-docker-pread-03e054
1min45s/1min45s: http://autumn.ocamllabs.io:8081/job/2021-06-07/092436-docker-pread-fc045d
3min13s/1min53s: http://autumn.ocamllabs.io:8081/job/2021-06-07/094240-docker-pread-cb153b

About that last one I noticed that https://github.com/ocaml/dune/pull/4678 ran at the same time. It would explain that wall/cpu time difference.
Timeline of events:

2021-06-07 09:29.36: 1441-build started first
2021-06-07 09:38.46: 4678-build arrived and got stuck on Waiting for resource in pool docker
2021-06-07 09:42.40: 1441-build finished and both 1441-run and 4678-build started at the same time
2021-06-07 09:44.03: 4678-build finished and 4678-run started while 1441-run was still running

URLs:

1441-build: http://autumn.ocamllabs.io:8081/job/2021-06-07/092936-docker-build-6f0b9b
1441-run: http://autumn.ocamllabs.io:8081/job/2021-06-07/094240-docker-pread-cb153b
4678-build: http://autumn.ocamllabs.io:8081/job/2021-06-07/093846-docker-build-09c515
4678-run: http://autumn.ocamllabs.io:8081/job/2021-06-07/094403-docker-pread-4a4bda

Thanks for the detailed log @Ngoguey42! Will look into this!

With pool fixed and cached opam installs, this is faster now. :) Please re-open if you see this issue again! Thanks!


Add a std/item support function to do relocation more generally

When relocating a block of memory, the helper function should only ever move one item at a time, so as to preserve any inter-item linkages. This means that the relocation helper should also manage the memcpy/memmove. Additionally, moves from lower addresses to higher addresses should be done one at a time in reverse order

Done.


Bump gems to 1.0.0

Gems expects JSON back from Rubygems now, not YAML.

Updated to be compatible with https://github.com/gocardless/bump/pull/170.


Source binding issue

There is no problem with the demo running, why am I changing to directly bind resources and cannot use them.
Where did I go wrong?

Fixed by https://github.com/AvaloniaUI/Avalonia.GIF/pull/27


Implement determinate circular progressbar

This is an implementation of the determinate circular progress bar as shown here: https://storage.googleapis.com/material-design/publish/material_v_10/assets/0B14F_FSUCc01N2kzc1hlaFR5WlU/061101_Circular_Sheet_xhdpi_005.webm
Closes #24
Screenshots of this implementation:
1 2 3 4 5 6 7 8

Thanks, I'll look into the code later.
Another question remains that whether the circular progress should move its starting point along the circumference. Although the spec presented so, it might be confusing to user (If the progress stalls it looks kind of weird) and hard to estimate the progress, plus that the spec has no text specification on this except for that video.
A quick research on this:

Library
Status

Angular Materal
Fixed starting point at top

Polymer Elements
N/A

Materialize
N/A

Material Components for the web
Unknown

Material Design Lite
N/A

Material UI
Fixed starting point at 45 deg

I personally like the effect of the moving starting point, which is an innovative way to visually fill the square element and provide visual symmetry even for early progress values.
I don't think a circular progress indicator alone can give the user a precise estimate about the progress value. If that is needed, other UI elements must be used anyway. So I think it is good enough if the user can get a rough idea how far the progress is.
Additionally you can see that the length of the coloured arch is linear to the progress, starting from 0° to 360°, even if the arch is moving. So if you observed the element a couple of times, you get a good feeling of how far the progress is.
Given that, I'd love to keep the effect as it is shown in the video provided by Google.

I think a circular progress indicator alone can give the user an easy impression of the progress, e.g. if the progress starts at the top, then users can read a quarter, half, three quarters, it's pretty natural, the same as we read clocks.
However if the starting point is moving around, the same experience can not apply any more. Users will need extra efforts to read it, or get accustomed to a new way of interaction that is not seen elsewhere.
So although I'm somewhat a spec follower and lover, I have my reservation about this particular design, which is also never stated literally but only showcased in a video.

Other unresolved issues include:

Whether we should provide the starting point as an option.
Whether it should be able to show/hide a track.
Whether it should be able to show/hide a secondary progress.
If we are moving to VectorDrawableCompat (#53) how should the implementation be done.

I prefer making a decision upon these design/implementation issues before we merge it into this library.

Whether we should provide the starting point as an option.

Sure, that can be done easily

Whether it should be able to show/hide a track.

You mean a background of the circle? Might be possible but I did not see it in a Material example. So I'd rather skip it until there is a good reason to implement it.

Whether it should be able to show/hide a secondary progress.

I almost finished implementing that but then it was a bit buggy so I discarded it because I did not see it in the Materials documentation and I personally do not need it. But yes, that can be done for consistency.

If we are moving to VectorDrawableCompat (#53) how should the implementation be done.

I have no experience with VectorDrawableCompat and I looked how the current implementations work. Moving to VectorDrawableCompat is going to be an entire rewrite of the core library so I'd leave this as a second step. Having a stable set of features is a good base for evaluating if VectorDrawableCompat can replace Canvas throughout the library.

Is there anything I can do for the progress of this ticket?

Still think that the progress should start at top (at least by default), per the two Angular Material versions by Google (see above), and (my own) UX considerations.
If this can be an attribute, I'm wondering what its name should be, app:mpb_???circularIndeterminate???? Really can't think of a good name.
And about the secondary progress -- I think it should better be implemented, but it would be weird if the starting point is moving according to progress -- where should it start if it has a different progress value compared to the primary one?
And I think a track should also be implemented, like the horizontal counterpart.

Great, thanks. I'll take care of that.
What about app:mpb_circularIndeterminateStyle = "fixedStartTop" (default), "movingStart"? Is it snake_case or camleCase in the values?

Okay, done implementing the requred features

Thanks for your work! I'll review the code later, due to some personal matters.

Okay cool, thanks :)

So you think it is possible to review and release this within this week? I need the determinate circular progress for an upcoming app release. Otherwise I need to somehow build a fork locally but if that could be avoided would be great.

OK, I'll do the code review ASAP.
BTW, I rebased the fork (Needed a commit upstream), so you might need some extra steps if you want to add commits.

Alright, thanks. Interesting, I did not know that you get the access rights to push to my fork's branch. Otherwise I am familiar with rebasing et cetera, no problem.

Finished reviewing the library module except the 15 degree.

What is the "15 degree problem"?

@webmaster128 https://github.com/DreaminginCodeZH/MaterialProgressBar/pull/51/files/7b6d3d41ae131315032990f49e0975fef23bd0b9#r110824773

@DreaminginCodeZH The link does not point me to any specific line or comment

Strange, perhaps you need to wait till the page load is finished. Anyway you can C-F the string:

How did you get this 15? By estimating from the video, or by stepping to find the first frame and measuring in Photoshop etc? Is it precise, or can it be from the fact the at the beginning the progress is thin but quick in motion? Have you done comparison between 0 and 15, and if so is it that 15 wins?

I measured the angle from the first frame that I could capture in the video. I am pretty sure it does not start at 0. Thus I took 15 and was happy with the result. 0 was not tested.

Strange, perhaps you need to wait till the page load is finished. Anyway you can C-F the string:

It is not there. Did you write it as a pending review comment?

I found a suspicous frame on the second start of the progress:

I have experimented with 0 instead of 15 and they looked the same, and because I see no sensible reason for the animation to start at 15, I'm making it 0 now.

Merged, thanks! Will be released later.

Released on Maven Central just now, should be available within hours.

Cool, thanks!


Refactor sctp_stop_timer to match sctp_start_timer

Hi, this is a straightforward refactor of some lines of code into a stop function, to match the already present start function. This is useful in cases where a user might want to wrap/replace the start and stop functions (which must correspond). Let me know if you need more explanation, thanks!

Committed as part of  https://github.com/sctplab/usrsctp/commit/2d8b09dd5cc9bb7671615be17ea3fe3d5f72f46e.


check embed.zip for Python 3.11, 3.12

PythonEmbed4Win.ps1 makes assumptions about the embed.zip based on Python 3.7 to 3.10.  Test these assumptions against 3.11, 3.12.
Do they still package the embed.zip in an odd manner?  Do they still need a sitecustomize.py?  Is their sitecustomize.py getting overwritten by PythonEmbed4Win.ps1 ?

Checked 3.5, 3.6, 3.7, 3.8, 3.9, 3.10, 3.11, 3.12
3.5 and prior does not run from embed.zip.
3.6 can not run get-pip.py.
The script has been updated to reflect that.


Allow to use more than 10 MDI Commands.

Additional commands can be added with "Add MDI Command" button.

Thanks


New home for "Learning Extended Events in 60 Days"

It seems that the course "Learning Extended Events in 60 Days" has a new landing page (see here). The new link is sqlxevents.com.
That bothers me is the sentence: "... The old methods (bitly and subdomain) will still be valid to point to the old landing page – for a time. ... ". Maybe it is good to add also the new link to the repository.

Hi @bogdandb , I will update resource with new link on Sunday, thanks for your suggestion.

Added via<PHONE_NUMBER>a8301e87b480fc71b7fe0327513af6. Thanks for your contribution.


module 'cirq' has no attribute 'work' or 'version'

Description of the issue
module 'cirq' has no attribute 'work' or 'version'
How to reproduce the issue
pip install cirq==0.11.0
python -c 'import cirq; print(cirq.__version__)'

AttributeError: module 'cirq' has no attribute 'version'

tensorflow_quantum v0.5.0 depends on cirq v0.11.0 I am also unable to import tensorflow_quantum as I get the error

AttributeError: module 'cirq' has no attribute 'work'

Cirq version
You can get the cirq version by printing cirq.__version__. From the command line:
AttributeError: module 'cirq' has no attribute '__version__'

All earlier versions work very fine. I need this version(0.11.0) as the latest release of tfq depends on this.
Can you please clarify if this is the issue only with me? If true can you please help in rectifying this issue. Thank you in advance

It is working in a fresh environment

xref https://github.com/quantumlib/OpenFermion-FQE/issues/90#issuecomment-840983121. I think in any environment that already has an earlier Cirq version, pip install cirq==0.11.0 leads to a broken installation.

It is working in a fresh environment

Alternatively, pip uninstall cirq before installing 0.11.0 should work.


Fix tflint issues

I just realised that .tflint must be in each directory that has Terraform code.
In this case, need to copy .tflint to examples/ directory.
Another adjustment is to upgrade aws plugin in .tflint.hcl file.

AWS Plugin was already on the latest version.
I will enable the terraform_comment_syntax to avoid // comments.
Copied the .tflint.hcl to examples


syslog plugin disabled by default

I used Syslog plugin to record logs, but it did not work as expected. I can not find log file in the path '/var/log/'.

I try to start it manually
syslogd
every thing is ok now

#https://github.com/Kong/kong/issues/3178

version:
kong:latest
kong:0.13-alpine

Hi,
I am facing same issue. syslogd does not start automatically as part of kong docker image. it works manually. Did you manage to get it working?

syslogd is not bundled with or started automatically as part of Kong.
You will need to install / configure / run syslog separately after which the Kong syslog plugin is able to send logs to it. I did a quick test of Kong 2.0.2 on Xenial and everything works as expected.


Test latest version of the rucio-jupyter extension package

dev tag image was deployed in the vre. Closing this PR soon.


Fix the id field in the migration scripts

See https://github.com/huggingface/datasets-server/pull/825#discussion_r1115923999

to do


dependence on NullableArrays

not reflected in REQUIRE.
https://github.com/JuliaDB/DataStreams.jl/blob/master/REQUIRE

fixed


Update MD file on new branch 2017-11-17_13-27-02

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/content1.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Add note about validator memory usage

Since (at least for me) the validator exceeds PHP's default memory limit of 128MB when running the validator locally (seems to require about 150MB).
This note might have saved me a couple mins while I thought I somehow caused the validator to break :)

Yeah, validating that the package exists in the composer repository requires loading some packagist metadata, and 128MB is clearly low for that.

Not sure this needs a specific call-out though?


Popup with autocomplete un-selectable behind another element

Current Behavior
I have an issue with the popup autocomplete component where the popup box appears behind another interactive graph element (an echart in this case). This makes the individual choices unselectable/unclickable. I can provide a clip if it is not clear what I mean.
Expected Behavior
The popup should overlap any other element to maintain clickability.
Steps To Reproduce
A code example:

			<input
				class="input autocomplete"
				type="search"
				name="autocomplete-search"
				bind:value={inputPopupDemo}
				placeholder="Search..."
				use:popup={popupSettings}
			/>

				<Autocomplete
					bind:input={inputPopupDemo}
					options={flavorOptions}
					on:selection={onPopupDemoSelect}
				/>

		<Chart {options} renderer={'svg'} />

Link to Reproduction / Stackblitz
No response
More Information

Hey @endigo9740 ,
thanks for the quick response. That indeed fixed it. Already if I set it to z-[1] !


When Installing Using Pip -- UnicodeDecodeError: 'charmap' codec can't decode byte

When installing selene on python 3.8.2 64bit (Windows), this error occurs:
    ERROR: Command errored out with exit status 1:
     command: 'c:\python\python38\python.exe' -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'C:\\Python\\src\\selene\\setup.py'"'"'; __file__='"'"'C:\\Python\\src\\selene\\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info
         cwd: C:\Python\src\selene\
    Complete output (7 lines):
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "C:\Python\src\selene\setup.py", line 6, in <module>
        long_description = open(join(abspath(dirname(__file__)), "README.md")).read()
      File "c:\python\python38\lib\encodings\cp1252.py", line 23, in decode
        return codecs.charmap_decode(input,self.errors,decoding_table)[0]
    UnicodeDecodeError: 'charmap' codec can't decode byte 0x81 in position 632: character maps to <undefined>
    ----------------------------------------
ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.

If I change line 6 as follows, the error goes away:
long_description = open(join(abspath(dirname(__file__)), "README.md" ), encoding="utf8").read()

@joshglenn, thank you so much for the findings!
I have fixed it in 2.0.0a24, already released
Join our newly created telegram chat: https://t.me/selene_py
Let's grow the selene community there too;)


May I ask whether these three button ICONS can be set to hide and start? Sometimes I accidentally hit the horn icon. Thank you

Hello. https://github.com/AlekPet/ComfyUI_Custom_Nodes_AlekPet/tree/master/ExtrasNode#additional-extensions

Hello. https://github.com/AlekPet/ComfyUI_Custom_Nodes_AlekPet/tree/master/ExtrasNode#additional-extensions

Thank you


1.1.0 (ADAS) - BUG -  Date in rule web display indicates 1969 .. date display incorrect.

In the SSM dashboard, the time always lists as 1969-31-12 .
The date/time is wrong, please fix this

@zhiqiangx Please fix the issue of displaying a time that equals 0.


[Snyk] Security upgrade PyYAML from 3.12 to 5.4

Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

requirements.txt

Vulnerabilities that will be fixed
By pinning:

Severity
Priority Score (*)
Issue
Upgrade
Breaking Change
Exploit Maturity

876/1000  Why? Mature exploit, Has a fix available, CVSS 9.8
Arbitrary Code Execution SNYK-PYTHON-PYYAML-590151
PyYAML:  3.12 -> 5.4
No
Mature

(*) Note that the real score may have changed since the PR was raised.
Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the effected dependencies could be upgraded.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Coverage remained the same at 98.795% when pulling 9a22af25e17ae5a63c495e8a83c09f8e4de04117 on snyk-fix-ccee47f9cde563cb3734d8c0ed5cc695 into 87dbc69b45a58f2e6caa6ba476cf662947ed0a33 on master.

Coverage remained the same at 98.795% when pulling 9a22af25e17ae5a63c495e8a83c09f8e4de04117 on snyk-fix-ccee47f9cde563cb3734d8c0ed5cc695 into 87dbc69b45a58f2e6caa6ba476cf662947ed0a33 on master.


MacOS compatibility, removed cpu freq log message

I've added a check for plattform.machine() before logging


clone下来显示Your app isn't using AndroidX.

FAILURE: Build failed with an exception.

What went wrong:
Could not resolve all files for configuration ':app:debugCompileClasspath'.

Could not resolve io.flutter:arm64_v8a_debug:1.0.0-9a28c3bcf40ce64fee61e807ee3e1395fd6bd954.
Required by:
project :app
Could not resolve io.flutter:arm64_v8a_debug:1.0.0-9a28c3bcf40ce64fee61e807ee3e1395fd6bd954.
Could not get resource 'https://jcenter.bintray.com/io/flutter/arm64_v8a_debug/1.0.0-9a28c3bcf40ce64fee61e807ee3e1395fd6bd954/arm64_v8a_debug-1.0.0-9a28c3bcf40ce64fee61e807ee3e1395fd6bd954.pom'.
Could not HEAD 'https://jcenter.bintray.com/io/flutter/arm64_v8a_debug/1.0.0-9a28c3bcf40ce64fee61e807ee3e1395fd6bd954/arm64_v8a_debug-1.0.0-9a28c3bcf40ce64fee61e807ee3e1395fd6bd954.pom'.
Read timed out
Could not resolve io.flutter:x86_64_debug:1.0.0-9a28c3bcf40ce64fee61e807ee3e1395fd6bd954.
Required by:
project :app
Could not resolve io.flutter:x86_64_debug:1.0.0-9a28c3bcf40ce64fee61e807ee3e1395fd6bd954.
Could not get resource 'https://jcenter.bintray.com/io/flutter/x86_64_debug/1.0.0-9a28c3bcf40ce64fee61e807ee3e1395fd6bd954/x86_64_debug-1.0.0-9a28c3bcf40ce64fee61e807ee3e1395fd6bd954.pom'.
Could not HEAD 'https://jcenter.bintray.com/io/flutter/x86_64_debug/1.0.0-9a28c3bcf40ce64fee61e807ee3e1395fd6bd954/x86_64_debug-1.0.0-9a28c3bcf40ce64fee61e807ee3e1395fd6bd954.pom'.
Read timed out

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 2m 1s
Exception: Gradle task assembleDebug failed with exit code 1
Exited (sigterm)

请问这个问题解决了吗？

由于长时间没有反馈，我将关闭这个Issue。若还有问题，请重新打开此Issue！


Fix success condition in SendPushFinishedEvent call

SendPushFinishedEvent was being called with success: false when batchStatus equaled to PushStatus.Complete.
However, I think it should be success: true when batchStatus equals to PushStatus.Complete
Fixes #924
Fixes #923

@adrianhall can you please review this?

Cleaning up for the pending archival of this repository.


Indexable metadata

Related to #26.
Edited by @KirstieJane: Closes #26 (I think! Correct me if I'm wrong!)

@KirstieJane thank you for the review and the green button offer 😍


[BEAM-11358] Remove unused endOfStreamMonitor from nexmark and remove redundant distributions from monitor

The endOfStreamMonitor in the NexmarkQuery class is not used. The monitor class also had start and end distributions, which used the same values. This PR removes the unused monitor and merges the start and end distributions.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[X] Choose reviewer(s) and mention them in a comment (R: @username).
[X] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[X] Update CHANGES.md with noteworthy changes.
[X] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @echauchot
R: @aromanenko-dev

The spotless check failed with a file I have not edited :confused: I can apply the spotless fix and upload that here if you want?

Run Java PreCommit

Seems I've been a bit quick in the trigger here and changed the logic after merging the two distributions. I'll push a fix later this evening, sorry for the slip!

I've fixed the error, but the error now is not in a part of the code that I haven't touched.

Run Java PreCommit

@rHermes Thanks! Could you create a Jira for this and squash all your commits into one?

@rHermes Thanks! Could you create a Jira for this and squash all your commits into one?

Will do it after work today :)

OK, squashed and created a JIRA issue.

@aromanenko-dev does it look good now?

@rHermes Thanks! Could you elaborate changes regarding this part This PR ... merges the start and end distributions. ?

@echauchot Could you take a look on this PR since you worked on Nexmark too?

@rHermes Thanks! Could you elaborate the changes regarding this part This PR ... merges the start and end distributions. ? Why it was done?

Because they are updated with exactly the same values, they will always be exactly the same, so they could be merged. If you look at the removed lines in Monitor you will see that they where set with exactly the same values

@rHermes thanks for your work ! taking a look

@rHermes thanks for your work ! taking a look

Any update on this?

@rHermes sorry I'm late on that I started the review and then I was dragged on other priorities. I think I could finish by the end of the week.

Thanks for your work @rHermes !
Only some minor fixes and an important comment.
Nexmark execution times are similar to CI. So LGTM
On piece of advice, it is your second cleaning PR on nexmark. Next time, could you please consider submitting cleaning PRs all in a single PR with separate commits with explicit messages? thanks

I thought it was better practice to create separate PRs, but it's easier for me to just combine them, so I'll do that next time :)

@rHermes yes general good practice is to separate PRs that deal with different subjects. But for cleaning PRs, it is the same subject. There a lot of leftovers in nexmark what I would like to avoid is tens of PRs that remove only a couple of fields.

@rHermes yes general good practice is to separate PRs that deal with different subjects. But for cleaning PRs, it is the same subject. There a lot of leftovers in nexmark what I would like to avoid is tens of PRs that remove only a couple of fields.

Got it :+1:
I've addressed your comments from the review, and rebased on top of master.

@rHermes sorry for the delay. I took a llok at your changes. you just forgot a rename and I can merge.

Ahh, my bad. Fixed now :)

@rHermes sorry for the delay. I took a llok at your changes. you just forgot a rename and I can merge.

Ahh, my bad. Fixed now :)

Run Direct Runner Nexmark Tests

Run Direct Runner Nexmark Tests

Run Direct Runner Nexmark Tests

Run Direct Runner Nexmark Tests

my bad, I merged but I forgot to tell you to rename the commit with ticket number and to squash them. It is not that serious, just not very clear in history. you'll know for next time.

my bad, I merged but I forgot to tell you to rename the commit with ticket number and to squash them. It is not that serious, just not very clear in history. you'll know for next time.


Rethink repository organization and process

I originally designed this repository so that the CI would run and build any wheels missing from PyPI, and maybe even eventually auto-upload them. The autowheel package will basically chekc for any version more recent than what's in autowheel.yml so that we don't need to update the repository when new releases are made. The flip side is that if this was run as a daily cron job, one would have to wait 24 hours to get wheels, or trigger builds manually.
However, this might be a bit too magic, and I'm now wondering whether it would make more sense to have a model similar to conda forge, where we have a mini yml recipe (which would really just look like a single section of the autowheel.yml file) for each package, and then either have one package per repo, or (to keep things easier to manage) maybe one package per branch in the repository. Then building a new version would require a PR to update the version number but could be done easily. Having one package per branch also means that we really only ever build what's needed.
@bsipocz @cdeil @larrybradley - any thoughts about this? No strong opinion is a valid thought :)

I like the one package per repo setup of conda-forge a lot. But here it seems a bit of an over-reaction.
I don't necessarily like the one package per branch option, don't see how it would work efficiently without the logic of having one canonical main branch, but I suppose I can be convinced that it would work.
Also, having a daily cron sounds good, I don't think any of the releases has to be rushed out quicker, if they need to then a manual update is always an option.

What I would like to see, but haven't yet opened an issue for it, is that wheel-forge be able to pick up releases from github tags. e.g. being able to check on the wheel building before pushing a release. I think it's a blocker for the core wheels production being moved over here.

I am closing this as we now build wheels in the CI for each package, and am archiving this repo.


Cumulative pay request

implement cumulative status key to Behpardakht global setting. by setting cumulativeDynamicPayStatus to true. method bpCumulativeDynamicPayRequest will be called.
Description
This pull request adds a new class called CumulativePayRequest. This class represents a request for cumulative pay, which is a type of pay that is calculated based on the total amount of pay that an employee has received over a period of time.
you can refer to Behpardakht documentation for more details.
Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

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

[x] New feature (non-breaking change which adds functionality)

[ ] Breaking change (fix or feature that would cause existing functionality to change)

[x] I have read the CONTRIBUTING document.

[x] My pull request addresses exactly one patch/feature.

[x] I have created a branch for this patch/feature.

[x] If my change requires a change to the documentation, I have updated it accordingly.

@khanzadimahdi if you want more info about this PR. you can simply refer to this document.
https://github.com/TookanTech/iranian-services-documents/blob/main/Payment Gateways/Behpardakht/implementation-ipg-fa.pdf | cumulativeDynamicRequest section


Get-module can't see it

Why i "Import-Module AzureRM" but can't see in "Get-Module" ? but command Connect-AzureRmAccount exists.

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

ID: ac940e68-c41e-485b-c89c-057dd407fed1
Version Independent ID: a1f76299-1832-cd86-b4f5-f7635ed62492
Content: Install Azure PowerShell on Windows with PowerShellGet
Content Source: docs-conceptual/azurermps-6.6.0/install-azurerm-ps.md
Product: powershell
GitHub Login: @sptramer
Microsoft Alias: sttramer

You have installed with a method other than Install-Module, and may have auto-import enabled for available commands.


Passcode modal

Need a modal for passcode

"Please remember your passcode and backup your wallet by writing down the seed words. You would be locked out of the app if you forget your passcode and will have to recover it."
@Deveshshankar

https://xd.adobe.com/view/f1543c84-c25a-4ad6-81ca-1e0c540e956e-a407/screen/95c31d30-81fc-42ed-8e8f-c34b57f4f923/
check copy for title @Deveshshankar

Top : Remember your Keeper app passcode and securely write down your Backup Phrase.
Bottom: If you forget your passcode or lose the Backup Phrase, you risk being locked out of your wallet permanently.


[Bug]: Is vllm support function call mode?

Your current environment
Device: Nvidia GeForce 4090
software: vllm 0.5.2 + openai 1.30.5 + transformes 4.42.4
🐛 Describe the bug
I use OpenAI api and vllm to deploy local Qwen2 llm, But vllm function call mode does not work. The OpenAI interface correctly passed the tools info parameters to vllm, but vllm did not use it.  If I enable ' tool_choice="auto" 'parameter, I will encounter with 400 error code.
---------------------------------------------------------------------server script-------------------------------------------------------------
python entrypoints/openai/api_server.py --model="xxx/Qwen2-1.5B-Instruct" --trust-remote-code --host "localhost" --port 8000 --dtype auto
-------------------------------------------------------------client code ------------------------------------------------------------------
from openai import OpenAI
tools = [
{
"type": "function",
"function": {
"name": "get_current_weather",
"description": "Get the current weather in a given location",
"parameters": {
"type": "object",
"properties": {
"location": {
"type": "string",
"description": "The city and state, e.g. San Francisco, CA",
},
"unit": {"type": "string", "enum": ["celsius", "fahrenheit"]},
},
"required": ["location"],
},
},
}
]
openai_api_key = "xxx"
openai_api_base = "http://localhost:8000/v1/"
client = OpenAI(
api_key=openai_api_key,
base_url=openai_api_base,
)
models = client.models.list()
model = models.data[0].id
chat_completion = client.chat.completions.create(
messages=[
{"role": "system", "content": "You are a helpful assistant."},
{"role": "user", "content": "help me query currnet weather in BeiJing."},
],
model=model,
tools=tools,
# tool_choice="auto"
)
print("response: ", chat_completion.choices[0].message)
--------------------------------------------extra info &&  response ----------------------------------------------

response:  ChatCompletionMessage(content='xxx', role='assistant', function_call=None, tool_calls=[])
---------------------------------- enable  tool_choice="auto" parameter ----------------------------------------
openai.BadRequestError: Error code: 400 - {'object': 'error', 'message': "[{'type': 'value_error', 'loc': ('body',), 'msg': 'Value error, Currently only named tools are supported.', 'input': {'messages': [{'role': 'system', 'content': 'You are a helpful assistant.'}, {'role': 'user', 'content': 'help me query currnet weather in San Francisco.'}], 'model': '/home/zhangfan/deep_learning/Qwen2/examples/sft/Qwen2-1.5B-Instruct', 'tool_choice': 'auto', 'tools': [{'type': 'function', 'function': {'name': 'get_current_weather', 'description': 'Get the current weather in a given location', 'parameters': {'type': 'object', 'properties': {'location': {'type': 'string', 'description': 'The city and state, e.g. San Francisco, CA'}, 'unit': {'type': 'string', 'enum': ['celsius', 'fahrenheit']}}, 'required': ['location']}}}]}, 'ctx': {'error': ValueError('Currently only named tools are supported.')}}]", 'type': 'BadRequestError', 'param': None, 'code': 400}

MARK! need fix +1

+1

+1

+1

function call api, plz

class grade(BaseModel):
"""返回json格式"""
result: str = Field(description="Structured Output JSON mode")
op = convert_to_openai_tool(grade)
print(op)
def llm(content_data):
from openai import OpenAI
# Modify OpenAI's API key and API base to use vLLM's API server.
openai_api_key = "EMPTY"
openai_api_base = "http://<IP_ADDRESS>:3004/v1"

client = OpenAI(
    # defaults to os.environ.get("OPENAI_API_KEY")
    api_key=openai_api_key,
    base_url=openai_api_base,
)

models = client.models.list()
model = models.data[0].id

chat_completion = client.chat.completions.create(
    messages=[{
        "role": "system",
        "content": "You are a helpful  AI assistant."
    },
        {
            "role": "user",
            "content":content_data
        },
    ],
    model=model,
    temperature=0.1,
    top_p=0.9,
    tools=grade,
    tool_choice='grade',
)

a = chat_completion.choices[0].message.content
return a

主要就是你需要在 tool_choice 那里写上你函数的名字，你的代码就是“get_current_weather”

the same problem,

+1

mark +1

the same problem,

Trying Llama 3.1, the same behavior occurs with "tool_choice": "required" . If tool_choice is omitted altogether, the output is in text form, e.g., ```
Based on the given prompt, I will call the "search_movies" function with the required parameters. Here's the JSON for the function call:
{
"name": "search_movies",
"parameters": {
"genre": "comedy",
"query_string": "2015 comedy movies",
"year": 2015
}
}```
Happy to try to debug this further.

qwen2, same error
openai.BadRequestError: Error code: 400 - {'object': 'error', 'message': "[{'type': 'extra_forbidden', 'loc': ('body', 'tool_choice'), 'msg': 'Extra inputs are not permitted', 'input': 'auto'}, {'type': 'extra_forbidden', 'loc': ('body', 'tools'), 'msg': 'Extra inputs are not permitted', 'input': [{'type': 'function', 'function': {'name': 'get_weather', 'description': '获取某个地点的天气，用户应首先提供一个地点', 'parameters': {'type': 'object', 'properties': {'location': {'type': 'string', 'description': '城市，例如：北京'}}, 'required': ['location']}}}, {'type': 'function', 'function': {'name': 'get_time', 'description': '获取当前时间，给一个地方点', 'parameters': {'type': 'object', 'properties': {'location': {'type': 'string', 'description': '城市，例如：上海'}}, 'required': ['location']}}}]}]", 'type': 'BadRequestError', 'param': None, 'code': 400}

hello, any update from here, i have same problem ,'type': 'value_error', 'loc': ('body',), 'msg': 'Value error, Currently only named tools are supported.'

+1

same problem here.

Hi guys, I tried writing the following code snippet, which should help resolve the error mentioned above.
"tools": [
    {
        "function": {
            "name": "query_weather",
            "description": "Provides weather information for a specified location.",
            "parameters": {
                    "type": "object",
                    "properties": {
                        "location": {
                            "type": "string",
                            "description": "The location for which to retrieve weather information."
                        },
                    },
                "required": ["location"]
            }
        }
    }
],

"tool_choice": {
    "function": {
        "name": "query_weather"
    },
    "type": "function"
},

Hi guys, I tried writing the following code snippet, which should help resolve the error mentioned above.
"tools": [
    {
        "function": {
            "name": "query_weather",
            "description": "Provides weather information for a specified location.",
            "parameters": {
                    "type": "object",
                    "properties": {
                        "location": {
                            "type": "string",
                            "description": "The location for which to retrieve weather information."
                        },
                    },
                "required": ["location"]
            }
        }
    }
],

"tool_choice": {
    "function": {
        "name": "query_weather"
    },
    "type": "function"
},

Is there a complete code example? what is tool_choice？

Trying Llama 3.1, the same behavior occurs with "tool_choice": "required" . If tool_choice is omitted altogether, the output is in text form, e.g.,
Based on the given prompt, I will call the "search_movies" function with the required parameters. Here's the JSON for the function call:

{
"name": "search_movies",
"parameters": {
    "genre": "comedy",
    "query_string": "2015 comedy movies",
    "year": 2015
}
}

Happy to try to debug this further.

Hello, which llama 3.1 model are you using? How did you start the vllm server and enable function calling?
I'm unable to do so as the tool-call-parser only supports hermes and mistral as of now.

这是来自QQ邮箱的假期自动回复邮件。

来信我已收到，我会尽快给你回复，谢谢！！！

+1

+1

Hi guys,
vLLM does support tool calling, but it must be explicitly enabled and configured for the model that you're using.
Only some models are supported, since each model needs a tool-compatible chat template, and a custom tool parser to extract the model's tool call format into OpenAI's format.
You can read more about it in the docs here
At this time, the OpenAI-compatible API supports tool choice of auto or none, but does not support choosing the tool with a string - you must pass the following to the tool_choice argument: {"type": "function", "function": {"name": "my_function"}}
If you have read the docs linked above, have configured your instance accordingly, and are still having issues, please make sure that you are using the latest version of vLLM!

Hello guys,
To give you a complete example, here is my working code
`from openai import OpenAI
import json
Set up API client with the vLLM server settings
openai_api_key =
openai_api_base = "http://localhost:8000/v1/"
client = OpenAI(api_key=openai_api_key, base_url=openai_api_base)
def query_historical_event(date):
# Dictionary of historical events keyed by date
historical_events = {
"1969-07-20": "On July 20, 1969, Neil Armstrong and Buzz Aldrin became the first humans to land on the Moon during NASA's Apollo 11 mission.",
"1989-11-09": "On November 9, 1989, the Berlin Wall fell, marking the symbolic end of the Cold War and leading to the reunification of East and West Germany.",
"2001-09-11": "On September 11, 2001, terrorist attacks in the United States resulted in the destruction of the World Trade Center in New York City and significant loss of life.",
# Add more dates and events as needed
}
# Return the event if the date exists in the dictionary, otherwise a default message
return historical_events.get(date, f"No historical event information available for {date}.")

Define the tool for historical events
tools = [
{
"function": {
"name": "query_historical_event",
"description": "Provides information about a historical event that occurred on a specified date.",
"parameters": {
"type": "object",
"properties": {
"date": {
"type": "string",
"description": "The date of the event in YYYY-MM-DD format."
},
},
"required": ["date"]
}
}
}
]
Define tool_choice with the function details
tool_choice = {
"type": "function",
"function": {
"name": "query_historical_event"
}
}
Define the conversation with function calling capabilities
messages = [
{"role": "system", "content": "You are a knowledgeable assistant that can retrieve information about historical events."},
{"role": "user", "content": "Can you tell me what happened on November 9, 1989?"},
]
Generate a response using the messages and function tool
chat_response = client.chat.completions.create(
model="meta-llama/Llama-3.1-8B-Instruct",
messages=messages,
temperature=0.7,
max_tokens=1024,
top_p=0.9,
frequency_penalty=0.5,
presence_penalty=0.6,
tools=tools,
tool_choice={"type": "function", "function": {"name": "query_historical_event"}}
)
Check for the function call and handle it
if chat_response.choices[0].message.tool_calls:
# Extract and parse the date argument from the function call
date_argument = chat_response.choices[0].message.tool_calls[0].function.arguments
date_argument_dict = json.loads(date_argument)  # Parse the JSON string to a dictionary
date = date_argument_dict.get("date", None)
# Call the query_historical_event function with the date
response = query_historical_event(date)
print("Assistant response:", response)

else:
# If there's no function call, display the assistant's regular response
print("Assistant response:", chat_response.choices[0].message.content)
`
output: Assistant response: On November 9, 1989, the Berlin Wall fell, marking the symbolic end of the Cold War and leading to the reunification of East and West Germany.
Hope this helps.

Here is my working code. Hope this helps (I am using llama 3.1 deployed on kubernetes)
from openai import OpenAI
import json

# Set up API client with the vLLM server settings
openai_api_key = <your-secret-token>
openai_api_base = "http://localhost:8000/v1/"
client = OpenAI(api_key=openai_api_key, base_url=openai_api_base)

def query_historical_event(date):
    # Dictionary of historical events keyed by date
    historical_events = {
        "1969-07-20": "On July 20, 1969, Neil Armstrong and Buzz Aldrin became the first humans to land on the Moon during NASA's Apollo 11 mission.",
        "1989-11-09": "On November 9, 1989, the Berlin Wall fell, marking the symbolic end of the Cold War and leading to the reunification of East and West Germany.",
        "2001-09-11": "On September 11, 2001, terrorist attacks in the United States resulted in the destruction of the World Trade Center in New York City and significant loss of life.",
        # Add more dates and events as needed
    }

    # Return the event if the date exists in the dictionary, otherwise a default message
    return historical_events.get(date, f"No historical event information available for {date}.")

# Define the tool for historical events
tools = [
    {
        "function": {
            "name": "query_historical_event",
            "description": "Provides information about a historical event that occurred on a specified date.",
            "parameters": {
                "type": "object",
                "properties": {
                    "date": {
                        "type": "string",
                        "description": "The date of the event in YYYY-MM-DD format."
                    },
                },
                "required": ["date"]
            }
        }
    }
]

# Define tool_choice with the function details
tool_choice = {
    "type": "function",
    "function": {
        "name": "query_historical_event"
    }
}

# Define the conversation with function calling capabilities
messages = [
    {"role": "system", "content": "You are a knowledgeable assistant that can retrieve information about historical events."},
    {"role": "user", "content": "Can you tell me what happened on November 9, 1989?"},
]

# Generate a response using the messages and function tool
chat_response = client.chat.completions.create(
    model="meta-llama/Llama-3.1-8B-Instruct",
    messages=messages,
    temperature=0.7,
    max_tokens=1024,
    top_p=0.9,
    frequency_penalty=0.5,
    presence_penalty=0.6,
    tools=tools,
    tool_choice={"type": "function", "function": {"name": "query_historical_event"}}
)

# Check for the function call and handle it
if chat_response.choices[0].message.tool_calls:
    # Extract and parse the date argument from the function call
    date_argument = chat_response.choices[0].message.tool_calls[0].function.arguments
    date_argument_dict = json.loads(date_argument)  # Parse the JSON string to a dictionary
    date = date_argument_dict.get("date", None)

    # Call the query_historical_event function with the date
    response = query_historical_event(date)
    print("Assistant response:", response)
else:
    # If there's no function call, display the assistant's regular response
    print("Assistant response:", chat_response.choices[0].message.content)

output:
Assistant response: On November 9, 1989, the Berlin Wall fell, marking the symbolic end of the Cold War and leading to the reunification of East and West Germany.

Here is my working code. Hope this helps (I am using llama 3.1 deployed on kubernetes)
from openai import OpenAI
import json

# Set up API client with the vLLM server settings
openai_api_key = <your-secret-token>
openai_api_base = "http://localhost:8000/v1/"
client = OpenAI(api_key=openai_api_key, base_url=openai_api_base)

def query_historical_event(date):
    # Dictionary of historical events keyed by date
    historical_events = {
        "1969-07-20": "On July 20, 1969, Neil Armstrong and Buzz Aldrin became the first humans to land on the Moon during NASA's Apollo 11 mission.",
        "1989-11-09": "On November 9, 1989, the Berlin Wall fell, marking the symbolic end of the Cold War and leading to the reunification of East and West Germany.",
        "2001-09-11": "On September 11, 2001, terrorist attacks in the United States resulted in the destruction of the World Trade Center in New York City and significant loss of life.",
        # Add more dates and events as needed
    }

    # Return the event if the date exists in the dictionary, otherwise a default message
    return historical_events.get(date, f"No historical event information available for {date}.")

# Define the tool for historical events
tools = [
    {
        "function": {
            "name": "query_historical_event",
            "description": "Provides information about a historical event that occurred on a specified date.",
            "parameters": {
                "type": "object",
                "properties": {
                    "date": {
                        "type": "string",
                        "description": "The date of the event in YYYY-MM-DD format."
                    },
                },
                "required": ["date"]
            }
        }
    }
]

# Define tool_choice with the function details
tool_choice = {
    "type": "function",
    "function": {
        "name": "query_historical_event"
    }
}

# Define the conversation with function calling capabilities
messages = [
    {"role": "system", "content": "You are a knowledgeable assistant that can retrieve information about historical events."},
    {"role": "user", "content": "Can you tell me what happened on November 9, 1989?"},
]

# Generate a response using the messages and function tool
chat_response = client.chat.completions.create(
    model="meta-llama/Llama-3.1-8B-Instruct",
    messages=messages,
    temperature=0.7,
    max_tokens=1024,
    top_p=0.9,
    frequency_penalty=0.5,
    presence_penalty=0.6,
    tools=tools,
    tool_choice={"type": "function", "function": {"name": "query_historical_event"}}
)

# Check for the function call and handle it
if chat_response.choices[0].message.tool_calls:
    # Extract and parse the date argument from the function call
    date_argument = chat_response.choices[0].message.tool_calls[0].function.arguments
    date_argument_dict = json.loads(date_argument)  # Parse the JSON string to a dictionary
    date = date_argument_dict.get("date", None)

    # Call the query_historical_event function with the date
    response = query_historical_event(date)
    print("Assistant response:", response)
else:
    # If there's no function call, display the assistant's regular response
    print("Assistant response:", chat_response.choices[0].message.content)

output: Assistant response: On November 9, 1989, the Berlin Wall fell, marking the symbolic end of the Cold War and leading to the reunification of East and West Germany.

If i want to apply multiple tools simultaneously, how shouldi do it?


Allow CAS and database authentication to live side-by-side

I was re-reading the README and felt like the whole "if you try to switch it will break things" aspect of our current authentication setup was a little off-putting. I think we can allow users to store both optional CAS logins as well as optional passwords and only utilize them when necessary. Here's what I have in mind:

[ ] Add a field to the Users table for cas_login - this can be blank or null
[ ] Add a method that copies one parameter into the username field; this will either be email or cas_login. We can therefore have the app copy the appropriate username into the relevant field depending on the presence of the CAS_AUTH variable. I'm not sure when this happens, maybe when you start the Rails server? It would also have to double check and make sure that all users have a CAS username before trying to switch; if you try to use CAS w/o having a login for every user, the app returns an error message.
[ ] In terms of switching to password authentication, we already allow for password resets using e-mail so that would be the simplest way to go

I don't know when this should happen, but making it possible would be really nice.

:+1: This is a tough call because we have limited person-hours, but this seems like Pre-Export material to me.

Yea I know, it would be really nice. I'll stick it on the top of our backlog and we'll see if we can get into v5.1.0. Also, depending on how the semester goes we may try for a second sprint as well, so it would definitely go in then.


[core]IcebergConversions addType for Timestamp and Time

Purpose
Linked issue: close #3788
IcebergConversions addType for Timestamp and Time
Tests
IcebergDataTypeCompatibilityTest
API and Format
Documentation

@tsreaper please Review code again,thanks

@tsreaper  Could you please help me take a look when you have time? Thank you

@tsreaper  Could you please review the code again

@tsreaper   i resolving the conflicts, But found a problem

I imitated it according to the new test logic，But the second round commit ,  no data query

why  commit  Invalid？
I will also look at the underlying logic first，This is my first time learning paimon, and there are many things I don’t understand, but I will study and understand them

i found data commited, but query not found

i found data  inseart,  but  data query  not found .  only  one

there is a read table  bug??

I found the difference is kind is append

! [image] (https://github.com/user-attachments/assets/dbbaffb4-ceaa-4da7-ad1c-351d19b74c7b)
why mytest  not compact ?   when not compact,  why the  data not query ?

@tsreaper  I am reading the source code now and solved this problem. Please review it for me.

I found that a lot of the core code was written by you. I will learn from you. I think the source code should make me familiar with paimon quickly. I hope this PR will be submitted as soon as possible. I will continue to contribute to the next one.

Hi @dbac , sorry for keeping you waiting. I've just introduced statistics to IcebergDataFileMeta, so now Iceberg will filter files according to the statistics we converted from IcebergConversions, and we can test the conversion reliably.
Please resolve the conflicts and add tests about timestamp and time to IcebergCompatibilityTest#testAllTypeStatistics. More specifically, do not add new test method. Just add a few columns with timestamp and time type to that test.

@tsreaper

time  only support 3 pecesion (so,  ms ),  and  use int writer.
so  IcebergConversions   time value   should    int  not long.

! [image] (https://github.com/user-attachments/assets/b4a42eba-b1b0-4bb7-a3c3-706f377707dc)
@tsreaper   there is a bug?
but i  use iceberg instert  , can query  result

@tsreaper

Is it a bug? Lessthan invalid, greaterthan ok ?
Is there a problem with writing iceberg data?

https://github.com/apache/iceberg/issues/9431

@tsreaper ？ Could you help me review it again?

Thanks @dbac for the contribution. @tsreaper has created another version #4318 to solve this issue.
Close this PR now.


Split override 中时

中時
中时
https://juejin.cn/post/6844903809206976520#:~:text=出现在非数组对象的属性值中时

Thanks.  This page appears to be a translation of the MDN docs on stringify (but an older version: the parts about BigInt are missing from the translation), we can probably put entries for 原始值 <comp.> primitive value, 属性值 <comp.> property value (well done that translator for interpreting “found in an object” correctly) and maybe even 任意函数 <comp.> arbitrary function.  Agreed 中时 makes an awkward entry (I haven't looked but I'm guessing it's from CEDICT and short for the Taiwan newspaper 中国时报 but it can easily "false positive" as in this example), let's put it in word-overrides

Probably because in Javascript an array is a kind of object.  The translation is more technically precise than the original...


some sounds not woking

Mod Version:
<IP_ADDRESS>
Forge Version:
1.12.2
Link to crash log (if applicable):
Description:
the sounds that arent working are:
equip items
crafting sounds

Post your config.


equidistant (fisheye) distortion model

Nice package, thanks for making this open source!
Question: does Kimera-VIO also support equidistant distortion models? Last time I checked GTSAM was not supporting it, but I have implemented it outside of GTSAM:
https://github.com/berndpfrommer/tagslam/tree/master/include/gtsam_distortion
Before I try hacking an equidistant model into Kimera, I wanted to check that nobody has done this already.

finished the implementation (at least in Kimera-VIO-ROS and Kimera-VIO). How do I run the tests in Kimera-VIO/tests?

Oh thanks @berndpfrommer ! Kimera-VIO uses gtests, but Kimera-VIO-ROS does not have a test suite (yet).
There are two ways to run the tests:

Easiest, server: just push your branch to this repo and the Jenkins server will run the tests for you: see here.
Locally non-ROS: in the build folder:
i) Using the classical make test will run all the tests.
ii) there should be a ./testKimeraVIO  executable that will run all the tests.
Locally ROS: that is the trickiest, since I haven't configured the catkin test to use gtest, and if you run the testKimeraVIO in the build folder of catkin workspace the paths won't be correct, perhaps you can override the gflag inside the main testKimeraVIO executable.

But the easiest is definitely just to push your changes to a  branch in this repo and all the unit tests and performance tests should run fine.

We actually tried to handle the equidistant model in the frontend side of things but it was never extensively tested...

For future visitors, equi model is now supported, but does not perform very well. We are working on better spherical camera representations!


Upgrade ReactQuery to v5

Update dependency @tanstack/react-query from v4 -> v5.
Note: The @trpc/react-query still uses v4 of ReactQuery. Must wait until tRPC will support v5.

@trpc/react-query v11 currently in beta
https://github.com/trpc/trpc/releases/tag/v11.0.0-next-beta.0


refactor/log4rs: upgrade to log4rs 0.4

This change is

r? @ustulation
(maidsafe_highfive has picked a reviewer for you, use r? to override)

Reviewed 3 of 5 files at r1, 2 of 2 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


reqwest = { version = "0.10.1", features = ["json", "blocking"] }

reqwest = { version = "0.10.1", features = ["json", "blocking"] }

Sorry for the slow response here; this PR is merged & a new version 0.10.0 is published. Thx very much!


New react native eventEmitter error

I get the following error.
error message: new NativeEventEmitter() was called with a non-null argument without the required removeListeners method.
prob, related to >
https://stackoverflow.com/questions/69538962/new-nativeeventemitter-was-called-with-a-non-null-argument-without-the-requir

@grinono: Will check and get back to you on this ASAP

@grinono This must be a warning, can you confirm ?

I'm not able to check it, we moved away from this lib. because of this issue, so i guess it was an error but i can not confirm.

Is it possible to confirm ?

This looks similar to #3

Closing due to inactivity


VelocityTransitionGroup throws Strict Mode warnings

The current dependency version of react-transition-group causes React strict mode to issue the following warnings:
Warning: Legacy context API has been detected within a strict-mode tree.

The old API will be supported in all 16.x releases, but applications using it should migrate to the new version.

Please update the following components: Transition

Warning: findDOMNode is deprecated in StrictMode. findDOMNode was passed an instance of Transition which is inside StrictMode. Instead, add a ref directly to the element you want to reference. Learn more about using refs safely here: https://fb.me/react-strict-mode-find-node
    in ul (created by Context.Consumer)
    in Styled(ul) (created by TreeNode)
    in Transition (created by VelocityTransitionGroupChild)
    in VelocityTransitionGroupChild (created by VelocityTransitionGroup)
    in div (created by TransitionGroup)
    in TransitionGroup (created by VelocityTransitionGroup)```

I’m not sure this is just an issue of react-transition-group. VelocityTransitionGroup also uses findDOMNode to get the DOM node of its child. That could probably be fixed by cloning this.props.children to attach a ref to it.
I haven’t looked at anything react-transition-group is doing, however.

Maybe I'm mixing things up, I had a similar warning with a react-transition-group dependency but it might be unrelated !

I wouldn’t be surprised if it were both.


Fix Runtime column in Job

Some tasks were failed due to timeout and now they are re-running

failed task info:

state: FAILED
createdAt: 2024-04-08T07:58:19.86482Z
scheduledAt: 2024-04-08T07:58:24.975338Z
startedAt: 2024-04-24T05:21:51.202746Z
failedAt: 2024-05-02T12:21:51.59164Z

new recreated task:
state: RUNNING
createdAt: 2024-05-02T12:21:51.598543Z
scheduledAt: 2024-05-02T12:21:51.605447Z
startedAt: 2024-05-03T06:19:18.683253Z
failedAt: 2024-05-02T12:21:51.59164Z

task config
retry:
  limit: 10
timeout: 199h

When task is finished I can see correct value

So the value is incorrect only during Running state and only if this task is a re-running task of previos failed task


Request - Allow increase in Subscription Ceiling Values

Are there configuration.yaml settings (or another method) to adjust the NODE_SUBSCRIPTION_CEILING_* parameters used by the matter server, and in particular, the thread ceiling:
https://github.com/home-assistant-libs/python-matter-server/blob/5b0a173c7c49c7e6e638c60c9a7fe1e0208e3f65/matter_server/server/device_controller.py#L81
If not,  can a method to configure this be added in the future (or the existing interval increased, with a suggested number of about 300 or so)?  Ideally, the existing  parameter would remain the floor, but the user could increase the timing.
Reason:
As I'm adding additional thread devices, I'm noticing some random delays in performing commands. Assuming the matter integration uses wildcard subscriptions, my theory is that refreshing all the attributes every 60 seconds is using up a substantial amount of the thread bandwidth contributing to delays, so I'd like to try to use a longer refresh ceiling. Even without wildcard subscriptions, there could be many attribute reports for some device types.
Some rough math behind why I think the ceiling may be too low:  Thread has a maximum raw bps of 250,000. If I assume 2 fabrics per device, 60 devices, an average of 2 hops, and about 75 bytes / packet (I read a silicon labs paper showing headers can take about 60 bytes or so, and I"m assuming another 15 for payload), that means each device can send just under 2 packets second on average under error free ideal conditions. Granted, that's a very rough calculation, but if the device has to report all its attributes each minute, it could use up a lot of the available bandwidth, so I'd like to be able to check whether increasing the reporting ceiling is helpful.

You are misunderstanding how this ceiling works. It is a wildcard subscription (and so does EVERY controller) but that does not mean that a full read of all attributes is sent at each ceiling interval. That will be just a simple ACK at the ceiling interval if there was no attribute change callback within the timespan,
And HA is actually very very very careful on this topic. Most other controllers use ceiling of only seconds or minutes.
We are actually planning on decreasing the ceiling because now it takes way to much time to detect a restarted node.

Thank you for the explanation.  That was helpful (and helped "fix" my understanding of Section 8.5  and 8.6 of the Core Standard). I'll close this now as it seems there's no need for further action here.
Thanks again.


Kestrel Server producing unfriendly outputs

I originally posted this issue in dotnet/cli but was referred here instead.
Steps to reproduce
Make a ASP net core project with ssl, kestrel and individual user accounts
Expected  behavior
Prints decimal number for line number
Actual behavior
Printing hexadecimal? line numbers.
info: Microsoft.AspNetCore.Server.Kestrel[17]
      Connection id "0HL24847RN8VG" bad request data: "Invalid request line: <0x16><0x03><0x01><0x00><0xC6><0x01><0x00><0x00><0xC2><0x03><0x03><0xCE>#<0xC6><0x1E>+<0x9A>@<0x81><0xC9><0xEF><0x00>q<0xCC>%:<0x19>5m*<0xBB>[..."
Microsoft.AspNetCore.Server.Kestrel.BadHttpRequestException: Invalid request line: <0x16><0x03><0x01><0x00><0xC6><0x01><0x00><0x00><0xC2><0x03><0x03><0xCE>#<0xC6><0x1E>+<0x9A>@<0x81><0xC9><0xEF><0x00>q<0xCC>%:<0x19>5m*<0xBB>[...

Environment data
dotnet --info output:
.NET Command Line Tools (1.0.0-preview4-004233)

Product Information:
 Version:            1.0.0-preview4-004233
 Commit SHA-1 hash:  8cec61c6f7

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.14393
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\1.0.0-preview4-004233

It looks like your hitting an HTTP endpoint over HTTPS.

Its outputting the input data (bytes) that are part of the request line as hexadecimal; not the line number of the code

By design.


Split tests into smaller pieces

Currently, many tests look something like:
TEST(a, b) {
  for (i : cases_i) {
    for (j : cases_j) {
      ...
    }
  }
}

It would be better if these were expressed as parameterized tests, so it is easier to execute a specific case. However, I don't like the boilerplate associated with this, at least per my understanding of how to do this in gtest. Perhaps there is a way to do it with a reasonable amount of boilerplate overhead.

I don't like the boilerplate associated with this,

Can you expand a bit more on what you don't like and/or what acceptable boilerplate would be?

Building a test "fixture" like shown in the examples here: https://github.com/google/googletest/blob/main/docs/advanced.md#how-to-write-value-parameterized-tests
The thing I'd do if I were to work on this issue right now is something more like this:
void test(int param1, bool param2);

TEST(test, test_1_true) { test(1, true); }
TEST(test, test_2_true) { test(2, true); }
TEST(test, test_1_false) { test(1, false); }
TEST(test, test_2_false) { test(2, false); }

That said: I think maybe we actually have a few tests that actually should share state between tests, and so could make good use of the test fixture class. For example: https://github.com/dsharlet/slinky/blob/main/builder/copy_test.cc#L41-L42

Yeah, text fixtures aren't the most elegant thing, but it's arguably the only reasonable way to model a shared-state in C++ (or at least the least-bad way). GTest shows its age in many ways but it's still a heck of a lot better than no test framework at all. We could of course consider some of the many other test frameworks for C++ but for Google integration this is probably least bad.

The thing is when there isn't any shared state, you still need a test fixture to implement parameterized tests. That's what I don't like. But it's not worth changing test frameworks over this. We can either do like I showed (just manually call a function implementing the test body in multiple tests) or just eat the boilerplate cost.


added search bar

b36792612e8501fdaf389cd987b817d60142c17e

chat he forgor 💀

b367926

chat he forgor 💀

blame vscode for not detecting it as html


Plotting issue

Hii everyone,
I want to know how to add colours in the contour plots and how to find out the value of minimized chi square of the best fit model parameters.
Thankyou

Are there any plotting routines in emcee? I think you are asking this question at the wrong place, since this has nothing to do with emcee itself.


Update websocket dependency to 1.0.33

Hi lads,
This PR updates the websocket optional dependency from 1.0.31 to 1.0.33 in protoo-client and protoo-server.
The following changes are included by default and nothing standout to me as a breaking change.
https://github.com/theturtle32/WebSocket-Node/compare/v1.0.31...v1.0.33
Main changes:

Refactoring to use ws napi modules
Expose parse options flags to readHandshake phase

protoo libraries 4.0.5 released. Thanks.