LBRY Debian / Apt / Ubuntu Install Cleanup (or switch to snap?)

There are several issues with the LBRY experience in the Ubuntu Software Center:

[ ] An extraneous version appears from the "SnapStore", v0.14
[ ] No screenshot appears for the app
[ ] The license shows as proprietary, when it is actually MIT

I'm guessing the bottom two are fixed by setting correct metadata... somewhere.
Acceptance Criteria

Definition of Done

[ ]  Tested against acceptance criteria
[ ] Tested against the assumptions of the user story
[ ] The project builds without errors
[ ] Unit tests are written and passing
[ ] Tests on devices/browsers listed in the issue have passed
[ ] QA performed & issues resolved
[ ] Refactoring completed
[ ] Any configuration or build changes documented
[ ] Documentation updated
[ ] Peer Code Review performed

This is still true. In particular I'd like at least the extremely old, broken version to not show up when I search "LBRY" (it's the first result).
I'm guessing the other 2 are just properly setting some metadata in one of the build artifacts.

Actually, the "correct" entry is also wrong. It's showing 0.21.5, not 0.23.

Re license:
https://github.com/electron-userland/electron-builder/issues/3914
Could be an existing bug: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/435183 / https://github.com/betaflight/betaflight-configurator/issues/989#issuecomment-375954366
https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/

The proprietary license issue was brought up yesterday by a friend who was trying out lbry. Probably very low priority but wanted to flag that it was noticed.

https://github.com/electron-userland/electron-builder/issues/4270

I've found like a dozen people/projects that have this issue and no one seems to know how to get it to say anything other than proprietary.

it looks like we were building for uappexplorer which is shutdown now. I do not see lbry on the ubuntu snap store. This is something different to build to.
looking here https://github.com/lbryio/lbry-desktop/blob/master/electron-builder.json#L66
We only specify deb for the top level linux key. See docs below, but I think we should add snap as well.
https://www.electron.build/configuration/linux
And the details for snap are

@tiger5226 yeah, it may be better to just pull the trigger and switch to snaps.

or appimages or flatpak or...
open-source is both fun and terrible :grin:

Here: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/435183

I got something from Lubuntu:
"I couldn’t found those packages in ubuntu repositories, so maybe there are some issues with the way the .deb was created. I downloaded FreeTube to look at it ( https://github.com/FreeTubeApp/FreeTube/releases/download/v0.7.1-beta/FreeTube_0.7.1_amd64.deb ) and couldn’t found a /debian folder in which, among others, the license in a machine readable format (copyright) should be placed. Maybe that’s why the system assume it is propietary. More info of copyright file: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/"
Source: https://discourse.lubuntu.me/t/deb-packages-license-issue/470/4

Great find @danrobi11!

Got new comment from Lubuntu:
Source: https://discourse.lubuntu.me/t/deb-packages-license-issue/470/16

I don’t see that any of these packages have an appstream.xml or metainfo.xml as specified by the AppStream specification and their desktop entries are not readily found (another place metadata could come from). That also may be where the problem lies.

Or it could be a combination of these things. Either way, this illustrates a good point: software in the Ubuntu archives is carefully checked to ensure it meets a variety of different specifications to ensure it works properly with the whole ecosystem of applications available in the archives. When you’re using software from outside the archives, you’re bound to run into trouble. This sort of software is entirely unsupported by Ubuntu.
If you want this to work correctly, you will need to talk to the upstream developers and perhaps have them speak with the gnome-software developers to figure out the appropriate solution. Additionally, you should urge them to get their packages included into Debian. Those packages should get automatically synced to Ubuntu.

Like wxl at Lubuntu suggested, i've opened a deb packages license issue at gnome-software gitlab
https://gitlab.gnome.org/GNOME/gnome-software/issues/833

Andre Klapper at the Gnome-software needs more information. Please have a look: https://gitlab.gnome.org/GNOME/gnome-software/issues/833#note_628721

The license shows as proprietary, when it is actually MIT

.deb package for lbry is not very good, it lacks some informations.
To check what is wrong I recommend lintian.
Current output:
lintian ./LBRY_0.47.1.deb
E: lbry: debian-changelog-file-missing-or-wrong-name
E: lbry: description-synopsis-is-empty
E: lbry: dir-or-file-in-opt opt/LBRY/
E: lbry: dir-or-file-in-opt opt/LBRY/LICENSE.electron.txt
E: lbry: dir-or-file-in-opt opt/LBRY/LICENSES.chromium.html
E: lbry: dir-or-file-in-opt ... use --no-tag-display-limit to see all (or pipe to a file/program)
E: lbry: embedded-library opt/LBRY/lbry: freetype
E: lbry: embedded-library opt/LBRY/lbry: lcms2
E: lbry: embedded-library opt/LBRY/lbry: libjpeg
E: lbry: embedded-library ... use --no-tag-display-limit to see all (or pipe to a file/program)
E: lbry: missing-dependency-on-libc needed by opt/LBRY/lbry and 7 others
E: lbry: no-copyright-file
E: lbry: shlib-with-executable-bit opt/LBRY/libEGL.so 0755
E: lbry: shlib-with-executable-bit opt/LBRY/libGLESv2.so 0755
E: lbry: shlib-with-executable-bit opt/LBRY/libVkICD_mock_icd.so 0755
E: lbry: shlib-with-executable-bit ... use --no-tag-display-limit to see all (or pipe to a file/program)
E: lbry: statically-linked-binary opt/LBRY/resources/static/lbry-first/lbry-first
E: lbry: unstripped-binary-or-object opt/LBRY/libVkICD_mock_icd.so
E: lbry: unstripped-binary-or-object opt/LBRY/resources/static/lbry-first/lbry-first
E: lbry: unstripped-binary-or-object opt/LBRY/swiftshader/libEGL.so
E: lbry: unstripped-binary-or-object ... use --no-tag-display-limit to see all (or pipe to a file/program)
W: lbry: description-starts-with-leading-spaces
...

Flatpak is better than Snap because:

Server side code for Snap is closed
Snap doesn't allow users to connect to more than one server. This is similar to Apple's monopoly on the iOS App Store, which means that nobody else can host a server for users to download apps from.


Add words from artsy/hokusai

👍

I'm going to go ahead and merge this, since I did find a typo in artsy/hokusai.

👍


Multiple Down Pickers

When I set up multiple down pickers in the same pages, If I choose an option for one, it disables all the others.
EDIT: Same if I have another classic UITextField and I type in a value.

Added an Example project to the repository who shows how to implement multiple downpickers in a single View. Let me know if it solves your issue.

I solved it like below.
in .h file
@property (nonatomic) DownPicker *picker1;
@property (nonatomic) DownPicker *picker2;
in .m file
NSArray *array1 = @[@"data 1", @"data 2", @"data 3"];
self.picker1 = [[DownPicker alloc] initWithTextField:self.priceTierTF withData:array1];
NSArray *array2 = @[@"data 1", @"data 2", @"data 3"];
self.picker2 = [[DownPicker alloc] initWithTextField:self.priceTierTF withData:array2];


Resolving links and urls

We are integrating with Stoplight Elements (https://meta.stoplight.io/docs/elements/ZG9jOjMyNjU4OTY0-elements) and we are having some issues with the links/anchors inside the page. The layout we are using is “sidebar”, the router is “hash”.
Current Behavior
The problem is that when I click on a link heading I get redirected on the correct place, but the URL goes to the default one.
The link I’m clicking on - http://<IP_ADDRESS>:8887/#gatewayresponse
The link I end up on - http://<IP_ADDRESS>:8887/#/
Would you be able to help us resolve this, since with this functionality it’ll be hard for the users to share the specific part of the documentation that is linked to?
Steps to Reproduce
6035Bug.zip
SF 6035

We are having the same problem and it annoys our end users. A solution to overcome this problem is highly appreciated.

Hey, any update on this one?

I can reproduce to it in https://elements-demo.stoplight.io/
Verify it works here once the fix is made.


NIFI-8161 NiFi EL: migration from SimpleDateFormat to DateTimeFormatter

Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Optimization improvement: Migrates NiFi Expression Language from SimpleDateFormat to DateTimeFormatter
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically main)?

[x] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[x] Have you written or updated unit tests to verify your changes?
[x] Have you verified that the full build is successful on JDK 8?
[x] Have you verified that the full build is successful on JDK 11?
[x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[x] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[x] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[x] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

Thanks for the contribution @arkadius. Moving in the direction of DateTimeFormatter is a good thing, and it sounds like the performance improvements are also notable. There are some particular nuances when it comes to time zone handling, so it is important to have a good number of unit tests to ensure expected behavior regardless of the system default time zone.
I noted several concerns and questions that would be helpful to address. Both @adenes and @turcsanyip have recent experience dealing date parsing issues, so it would be helpful to get additional feedback.

Thanks for review @exceptionfactory . I hope that I've fixed most places that you've pointed out.
Regards to time zone I was trying to make as few changes in current expressions logic as it is possible and nifi expression language currently uses system time zone in some cases. By my comment "some slight differences in interpreting time zone format" I meant that e.g. if someone used X format, he/she may need to change it to XXX for input text like +01:00 - it is because of changes of handling formats between SimpleDateTime and DateTimeFormatterBuilder. Using .parseLenient().parseCaseInsensitive() minimize number of those differences but not to zero.

@turcsanyip thank you for review. Your comments looks reasonable. I'm currently a little bit out of schedule but in a few days I'll prepare suggested changes.

@arkadius Thanks for the review changes.
The code looks good to me now and I also tested it with some flows (formatting and parsing dates back and forth with different formats).
I'm a bit concerned about the migration guide you mentioned on the Jira ticket.
If this change is backward compatible (and as far as I understand it should be that with the lenient formatter), then no migration guide needed.
If migration steps really needed, then it is questionable to add this change in a minor release.
Could you please give us some examples of formats that can be problematic?
I could not find any with my tests, though I did not use really advanced formats.

@arkadius I've been watching this because I've had the same worry as @turcsanyip but didn't have anything useful to say yet. After some digging, it looks like Spark went through this and there are some examples in https://issues.apache.org/jira/browse/SPARK-30668 and tests in related PRs. That could be a good starting point.

Thanks for the helpful reference @jfrazee!  After reviewing the API documentation for SimpleDateFormat and DateTimeFormatter again in light of the Spark issue, it looks like another key difference is that SimpleDateFormat supports lowercase z as a General time zone reference, whereas DateTimeFormatter does not support it.  Implementing a unit test using the lowercase z as part of the parsing pattern should present the differences between the implementations.
Thanks for highlighting the issues you have uncovered @arkadius.  It would be great to find a way forward, unfortunately I'm not sure about the timeline for a new major release, or the best approach for now.  One option is providing a way to use this DateTimeFormatter approach as an optional feature.  This would require reworking the PR to implement new Evaluators, as opposed to changing the existing ones.  As far as how this could work, one approach might be a new toDateTime() function, which would avoid conflicting with the existing toDate() function.  This would allow users to migrate to the new implementation without breaking existing flows.  What do you think @jfrazee and @turcsanyip?

Minor notice, that I should mention is that I personally don't need to have this feature in some release in the near feature. In my deployment we have our own fork with a few modifications. I just want to share this with community, because in our deployment it gave us significant performance improvement.
I don't think that introducing new function(s) would be a good way to go. It would complicate API for end users. Also I have other concerns:

What about other places like format() function? What about implicit string/number to date conversion?
What would be plan to fully migrate to DateTimeFormatter?
Maybe better option would be putting a feature flag in config? But personally IMO good migration guide for some major release would be enough.

I agree with @arkadius that maintaining 2 versions would be a bit overkill, both from code maintenance and end user perspective.
So the best option is to put it aside until NiFi 2.0. Though I'm not aware of any process how to do this (eg. git branch, tagging eg. jira ticket / PR).

Hmm by major release I was meant to 1.14.0 (instead of 1.13.3). I see now that you are pointing to semver concept. Is 1.13.x is last 1.x release? I saw a lot of breaking compatibility changes between semver "minor" versions of NiFi - https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance is full of them + some not documented there.

I see that we can't move forward with decision how to roll out this changes. You don't mind if I move discussion about both options to our dev mailing list? Summarizing I see that we have two options:

To modify implementation of current format / toDate functions - won't mess up api, but will need some date format modifications on users side (which will be described in tests and migration guide). Additional question is in which version should be introduced?
To add new formatDateTime, toDateTime functions (using DateTimeFormatter) next to existing format, toDate (using  SimpleDateFormat, will be deprecated) - won't break flows using current functions, but will add some complexity in api which will vanish after removal of deprecated functions.

Am I right? @turcsanyip can you take off 'requested changes' from this PR? Or there are some other changes in code left that I should made?

I heard that you are planning to release 2.0 version. Are you interested in merge'ing this performance improvement into the new version. I could rebase this branch if you want. What do you think @turcsanyip ?

Thanks for revisiting this pull request @arkadius! Yes, with the main branch version now set to 2.0.0-SNAPSHOT, this is a good time to rebase the pull request and move forward with these changes.

I rebased it. Can you reopen this PR?

It looks like it is not possible to reopen this PR following the rebase. If you can open a new PR, you can reference this one for background.


Added jobs_placed and jobs_done counters

This counters will help track the progress of the jobs placed on the
pool. After placing some jobs, one can easily check the progress of the
total work by
double progress = (thpool_num_jobs_done(thpool)/thpool_num_jobs_placed(thpool))*100;

These counters can also be used to control the job flow, i.e. one can
get total number of waiting jobs at any time by doing
long waiting_jobs = (thpool_num_jobs_placed(thpool) - thpool_num_jobs_done(thpool);
and then using some conditions, the programmer can restrict addition of
new jobs if it crosses a certain limit, can wait for termination of all jobs, etc.
One can also track the rate of execution of jobs in the pool by,
long waiting_jobs1 = ...;
sleep(1);
long waiting_jobs2 = ...;
long jobs_per_sec = waiting_jobs1 - waiting_jobs2;

These counters can be used in various other places also.

Thanks for this. However I close this since I assume this can easily be implemented outside the threadpool (before and after adding jobs), so don't see a good justification to have it built-in.


Install from hex

Installing OTP and Elixir from Hex has a few benefits:

Every released OTP version back to 17.0 supported
Every released Elixir version back to 1.0.5 supported, including branches such as "master"
Elixir is prebuilt for the specific OTP version which means you get OTP version specific features from Elixir
Does not require manually maintaining a list of supported OTP and Elixir versions

I had no idea this was a thing! This is a huge help. I'll review and merge ASAP. Thanks a ton @ericmj.

Going to merge this, and then make a few changes so that we're not downloading the runtimes directly into the working directory.


Small typos and such in README

We didn't have a chance to do a final pass on someone doing a fresh setup from the README before Eric's fellowship ended so this should be done. I noticed a typo on a folder name just now so thought I'd make an issue and start fixing these bits and pieces as I come across them.

Merged a branch that has some work on this. There's more to be done here but wanted to incorporate the updates made so far so will do next bunch on a new issue/branch.


Bicepparams not reading environment variable from Visual Studio Code

Bicep version
Bicep CLI version 0.16.1
Describe the bug
When attempting to call an environment variable from a Bicepparams file, the linter throws error BCP338
Environment variable does not exist, and no default value set bicep(BCP338)
When running dir env: from the same terminal, the variable is present.
Attempting to build the parameters file generates the aforementioned error as well.
To Reproduce
Generate a Bicepparams file:

Error is raised on check:

Run dir env: in console, see environment variable does exist

Additional context
Above example is for demo purposes, I'm not actually using LB_TIER as my env variable, it will be called from a GH workflow with values designated per environment.  Adding the default value a la param env = readEnvironmentVariable('LB_TIER', 'Incorrect') does work, but builds to the default, I left this out to demonstrate the error.
Bicep VS Code Extension version v0.19.5
VS Code Versions:

Hi @jordanrbaker
The latest bicep version is 0.19.5, however you are showing Bicep CLI version 0.16.1 ?
bicep --version
TRACE: Bicep version: 0.19.5+87ca110fc0, CLI arguments: "--version"
Bicep CLI version 0.19.5 (87ca110fc0)
code --list-extensions --show-versions --category Azure
<EMAIL_ADDRESS>Can you confirm that you can update the bicep cli on your deployment agents?
Or else share the yaml with the specific info on which version you are using. e.g. azure powershell or azure cli version ?

Since it appears that you are also testing locally and running into an issue.
Can you test with readEnvironmentVariable('APPDATA') <-- or some other default ENV var ?
Also how did you set the env var value? What operating system are you on?
if you are on windows:
setx TEST TEST

Then totally restart the console and ide, then test again after that.
pwsh> ls env:test

Name                           Value
----                           -----
TEST                           TEST

Local: Win11, Confirming APPDATA does work.
Using setx works as expected.
Using the .NET call from powershell does not work as expected:
System.Environment]::SetEnvironmentVariable('LB_TIER','Regional')
Overwriting the variable set with the powershell call with setx and then resetting the value with the powershell call also works.
I can use setx for my purposes as a workaround -> interested as to how the variables differ and why it cannot read it even though it displays when called

After a bit more poking, it looks like setting the variable at the machine scope works as expected (mirroring setx)
[System.Environment]::SetEnvironmentVariable('LB_TEST2','Regional', "Machine")
Is it expected that readEnvironmentVariable() can only read variables at the machine scope?

I believe user or machine will work, however you have to be sure to restart vs code or the terminal/console fresh after it has been set.

@brwilkinson I stumbled into this issue while looking whether it is possible to use some .env file to provide default values for readEnvironmentVariable when running in VS Code specifically, especially for local development purpose. With your last response, I think I can assume this is not supported 😅

@ggirard07 environment variables can be tricky locally, however most pipelines have an easy way to set them.
The environment file is something that is common in other languages and I think could be useful Bicep.
I think raising this on the latest bicepparam issue would be a good idea.
Would you mind asking on this issue?

https://github.com/Azure/bicep/issues/10777

@brwilkinson
Confirming I'm on Bicep 0.16.1 on my runners where I experience this issue as well.
Setting the variable at the user scope also appears to work: - which I can leverage for my purposes.
[System.Environment]::SetEnvironmentVariable('LB_TEST3','Regional', "User") or [System.Environment]::SetEnvironmentVariable('LB_TEST3','Regional', 1)
I'm going to go ahead and close this and comment on the open param issue that the documentation be updated to reflect that it does not work at the process scope - which is unexpected but reasonable.
Thanks for the help @brwilkinson !


added usage of subtests for hexadecimal

One of #2098

@eklatzer Isn't this exercise deprecated? This should be visible in the root level config.json. Please don't create PRs for deprecated exercises as it causes unnecessary work.

Sorry, have not seen that it is deprecated


WIP support for GCP external-account

This seems related to #49 a bit. Unfortunately there seems to be no way to implement this properly right now since it requires two HTTP calls: once to get a JWT token from the "local" provider and once to trade that token to the remote provider.

I think we should resurrect this draft PR and see if we can get it further (or find a similar solution).
We're getting more use-cases where impersonating service accounts will be real handy.


Update for latest Gleam

Gleam releases now use LLVM triplets for platforms so the download
URLs have been updated accordingly.
Gleam's rebar3 support has been removed.

This change means that future versions of this action cannot download
older versions of Gleam. I can make it backwards compatible, but I will
need help from someone who can convert the shell script into PowerShell
for Windows.

Hi, @lpil.
I'd usually not worry about backward compatibility before 1.0.0 (following Semantic Versioning principles) - which is Gleam's case.
At the same time, if rebar3's no longer support, would it be better to remove rebar3-version from the Gleam combos, everywhere?
Cheers.

This change means that future versions of this action cannot download
older versions of Gleam. I can make it backwards compatible, but I will
need help from someone who can convert the shell script into PowerShell
for Windows.

This is an interesting one... does a backward incompatible change for a supported language mean that we break compatibility for users and thus need to bump the major version? It may be the a big note in the README.md is good enough.
I'm not 100% sure on this on tbh. I tend to think that since our API has not changed, then we do not need to bump the major. To  boot, gleam is not 1.0 yet, thus it should be somewhat expected, no?
Thoughts?

I already have the code for backwards compatibility using shell, so I could add that and we leave windows support as a future addition?

I already have the code for backwards compatibility using shell, so I could add that and we leave windows support as a future addition?

That sounds quite amenable to me :)

@lpil, sure thing. Would you create an issue for what would need to be done, so somebody can take a look at it later? Cheers.

Fab! I've updated this PR and created the issue.
The build is failing but isn't printing any debug information. Is there a way to get more out of it? It passes for other installations so I'm not sure what might be happening.

Fab! I've updated this PR and created the issue.
The build is failing but isn't printing any debug information. Is there a way to get more out of it? It passes for other installations so I'm not sure what might be happening.

There's no gleam-0.23.0-rc1-linux-amd64.tar.gz for v0.23.0-rc1

Ah there it is! I found a typo in the script.

@paulo-ferraz-oliveira LGTM.

Oh yes! I forgot to remove the rebar bits. I have done that now

Merging... Many thanks, @lpil.

Wonderful, thank you! Would it be possible to get this released soon? I would like to start using new Gleam versions 😅

Oh yes! I forgot to remove the rebar bits. I have done that now

Yup, we certainly can 👍

I'll release and tag this today, and by then it'll also contain a pull request of mine 😄.

@starbelly, I'll move your tag, if that's Ok, since it was never released in any case...

v1.13.0 released, v1.13 tagged, v1 moved (to v1.13)


React Player rendering empty div

Current Behavior
My video component looks like this:
// https://github.com/cookpete/react-player/issues/1428
import dynamic from 'next/dynamic'
const ReactPlayer = dynamic(() => import('react-player/lazy'), { ssr: false })

export default function Video({src}) {
  return <ReactPlayer src={src} />
}

I use it like this:
<Video src="https://www.youtube.com/watch?v=grHP-de1p-U" />

Instead of seeing the video rendered on my page, I'm getting a blank div, in my dev tools I see:

Expected Behavior
See the video rendered on my page.
Environment

URL attempting to play: https://www.youtube.com/watch?v=grHP-de1p-U
Browser: Any.
Operating system: OSX

Can anyone provide an example repo? This behaviour implies a problem with the URL matching logic, but I can load https://www.youtube.com/watch?v=grHP-de1p-U in the demo page without a problem.

I am trying to use this with Remix.run and running into the same issue. I have a barebones repro here: https://github.com/TotalLag/reactplayer-remix-repro
if you run pnpm dev or yarn dev that should get things running.

I could be wrong but the supplied example uses src, not url when defined in React Player
Does the following work?
// https://github.com/cookpete/react-player/issues/1428
import dynamic from 'next/dynamic'
const ReactPlayer = dynamic(() => import('react-player/lazy'), { ssr: false })

export default function Video({src}) {
  return <ReactPlayer url={src} />
}

I am experiencing an empty src in my video tag similar to @daniele-sarnari-blinkoo when trying to use a local file but all remote URLs appear to be working correctly (I'm using 2.11.0)

I could be wrong but the supplied example uses src, not url when defined in React Player
Does the following work?
// https://github.com/cookpete/react-player/issues/1428
import dynamic from 'next/dynamic'
const ReactPlayer = dynamic(() => import('react-player/lazy'), { ssr: false })

export default function Video({src}) {
  return <ReactPlayer url={src} />
}

I am experiencing an empty src in my video tag similar to @daniele-sarnari-blinkoo when trying to use a local file but all remote URLs appear to be working correctly (I'm using 2.11.0)

I always used url property.
In my case the problem was React Strict Mode https://reactjs.org/docs/strict-mode.html.

This package is a trash if you are using this with NextJS. not working at all.

This is what renders in the page.

I had a similar issue in 2.13.0, I was using it with a file and the lazy option, when I clicked the play button the window simply vanished, it showed 0 for height in dev tools.
I resolved it by simply removing height form the ReactPlayer options, I originally had it set to 100% to make it responsive, but apparently having only width at 100% makes it responsive without a problem.
<ReactPlayer
    // ...
    light={image}
    width='100%'
    // height='100%' <-- removed this line
    // ...
  />


CDI-495 What happens if an illegal bean type is found in the set of bean types

illegal bean types in type set are ignored

LGTM

Looks good.


Material variants support

Addressing https://github.com/CesiumGS/cesium-native/issues/676
Maybe it is possible to split the conceptual questions from some lower-level questions. I'll add a comment with some conceptual questions in the issue.
The lower-level questions:
I tried to find the right place for extracting the (metadata) information from the tileset JSON, and pass it on to the Tileset class. The right place for parsing it may be a bit arbitrary. Since this is currently solely operating on the rapidjson document for the tileset, the magic
MaterialVariants parseMaterialVariants(const rapidjson::Document& tileset)
function can basically be inserted anywhere (currently in an anonymous namespace of the TilesetContentManager). But... this has to be changed for the case that the metadata schema is not contained in the tileset JSON, but referred to via a schemaUri. This is related the the question about the "proper way" for passing this information from the place where it is loaded (or where it has to be loaded in the future) to the Tileset object. Having short descriptions about what a TilesetContentManager actually is (beyond /* A class that manages tileset content */), or the role that a TilesetContentLoaderResult plays (beyond that it is /* The result of loading tileset content */) could be really, really, really helpful.

Even though this is only an early draft, it could be good if someone (@kring !?) could have a quick look whether the overall approach is not entirely wrong:

There is a plain struct
struct MaterialVariants {
  std::vector<std::string> tilesetMaterialVariantNames;
  std::vector<std::vector<std::string>> groupsMaterialVariantNames;
};

Some details TBD here. The main point for now is: It is supposed to be a simple structure that offers a bunch of strings and string arrays that are extracted from metadata

An instance of this is offered by the Cesium3DTilesSelection::Tileset class

The data is read, directly from the tileset.json, by the TilesetContentManager class - here (in the part that is 'hidden' by GitHub

It is stored in the TilesetContentLoaderResult, which appears to be the only way to 'transport' this information back to the caller (which has to happen on the main thread, via propagateTilesetContentLoaderResult)

One open question is:
The schema is currently assumed to be in the tileset.json. But the tileset.json might also contain a schemaUri, in which case the schema has to be resolved from an external file. I assume that this will involve some juggling with TilesetJsonLoader and the surrounding infrastructure (createLoader, addChildLoader etc...), and I'm not sure whether this conflicts with the current approach of using the TilesetContentManager to "transport" the data that is loaded back to the Tileset instance.

Longer-term points that are related to this PR:

The TilesetJsonLoader could eventually be replaced by the Cesium3DTilesLoader. But for now, it is pretty specific and deeply entangled in the loader infrastructure, and can probably not easily be replaced
This PR only adds easy, top-level access to the MaterialVariants data. This data is extracted from the metadata. Thus, it should be considered only as a "convenience functionality" that is offered on top of whatever metadata handling classes will exist in the future. Longer term, there might be a Cesium3DTilesMetadata library that contains the auto-generated classes that currently exist only for glTF, but which will also have to exist for 3D Tiles at some point. But regardless of what happens there, "under the hood", the MaterialVariants could still be exposed in the form that is drafted here, with no changes for the clients that consume it.

Thanks again for your contribution @javagl!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.


Relax python version to 3.9

JAX supports 3.8 so I think oryx will work with python 3.8

@sharadmv maybe 3.9 is fine?


Variable '_default' implicitly has an 'any' type

Following error occurs after updating to the current 2.0.0 version during tsc --noEmit. The project uses the current create-react-app package:
node_modules/react-router-last-location/dist/LastLocationProvider.d.ts:10:15 - error TS7005: Variable '_default' implicitly has an 'any' type.
  declare const _default;

Hey @valentinpalkovic ,
Could you create an example repository?
I cannot reproduce it using the newest CRA and 2.0.0.

I created repository with CRA and react-router-last-location and it works correctly:
https://github.com/hinok/create-react-app-react-router-last-location
Could you check if you have that problem in the linked repo above?

@valentinpalkovic  Try 2.0.1, the problem should be solved.

Because #29 and this issue are related, and I can easily see that typings for _default are provided in 2.0.1, I close this issue.


qnwnorm not type stable

When I compare the output of the two following lines:
x,w = QE.qnwnorm([3], [0.0], eye(3))
x,w = QE.qnwnorm([3 3], [0.0, 0.0], eye(2))

I find that x is a vector in the first case and a one line matrix in the second case. I would suggest to adopt a consistent behaviour (the second), or alternatively to have another function qnwmvnorm or smthg like that.
I think the behaviour changed in the last release of QuantEcon.

I have a fix locally -- I take type-instability personally ;)
Will patch up and submit a PR sometime today

Done

Cool, I feel much more stable now...
On Tue, 8 Nov 2016, 13:45 Spencer Lyon<EMAIL_ADDRESS>wrote:

Done
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/QuantEcon/QuantEcon.jl/issues/148#issuecomment-259139685,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAQ5KXA6zMxj_zCYh5uYQ4Go7m0gYmXrks5q8HzlgaJpZM4KrROx
.


Datastore mutation returns error: Field name not defined for input object type

Describe the bug
I followed the steps mentioned in the sample repo to create an Auth and API plugin. Then I tried to save a Post by:
    func saveData() async {

        do {

            let user1 = try await Amplify.Auth.getCurrentUser()
            let users = try await Amplify.DataStore.query(User.self, where: User.keys.username == user1.username)
            print(users)
            if users.count > 0 {
                let user = users[0]
                let data = Post(postBody: "HERE IS \(UUID().uuidString)", pictureKey: "EMPTY", createdAt: .now(), postedBy: user)
                let savedata = try await Amplify.DataStore.save(data)
                print(savedata)
            }
        } catch {
            print(error)
        }
    }

I am getting the following error:
2023-02-03 17:39:06.136883-0800 DatastoreAPISample[27713:15771145] [FetchAuthSessionOperationHelper] Fetching current state
2023-02-03 17:39:06.136928-0800 DatastoreAPISample[27713:15771145] [FetchAuthSessionOperationHelper] Session exists, checking validity
2023-02-03 17:39:06.137410-0800 DatastoreAPISample[27713:15771145] [API] Starting network task for mutation C92C6A68-AB1D-4ABA-B4C1-464D14F59573
2023-02-03 17:39:06.489721-0800 DatastoreAPISample[27713:15771147] [SyncMutationToCloudOperation] GraphQL mutation operation received result: success(Swift.Result<AWSPluginsCore.MutationSync<AWSPluginsCore.AnyModel>, Amplify.GraphQLResponseError<AWSPluginsCore.MutationSync<AWSPluginsCore.AnyModel>>>.failure(GraphQLResponseError<MutationSync<AnyModel>>: GraphQL service returned a successful response containing errors: [Amplify.GraphQLError(message: "The variables input contains a field name \'userPostsId\' that is not defined for input object type \'CreatePostInput\' ", locations: nil, path: nil, extensions: nil)]
Recovery suggestion: The list of `GraphQLError` contains service-specific messages))

The schema used:
type Post
    @model
    @auth(rules: [{ allow: owner, operations: [create, delete] }]) {
    id: ID!
    postBody: String!
    pictureKey: String!
    createdAt: AWSDateTime!
    postedBy: User! @belongsTo
}

type User
    @model
    @auth(rules: [{ allow: owner, operations: [create, delete] }]) {
    id: ID!
    username: String!
    profilePic: String!
    posts: [Post] @hasMany(fields: ["id"])
}

Steps To Reproduce
Steps to reproduce the behavior:
1. Create amplify resources with default values for Auth
1. Create api with User Pool as authentication mechanism and schema as mentioned above
1. SignIn to the app using SRP signIn
1. Save the user to the datastore and verify that it is saved in DDB
1. Try to save a post and see the error

Expected behavior
Post should save without any error
Amplify Framework Version
2.3.2
Amplify Categories
DataStore
Dependency manager
Swift PM
Swift version
Latest
CLI version
10.6.2
Xcode version
14.2
Relevant log output
<details>
<summary>Log Messages</summary>

2023-02-03 17:39:06.126986-0800 DatastoreAPISample[27713:15771147] [OutgoingMutationQueue] receive(_:)
2023-02-03 17:39:06.127068-0800 DatastoreAPISample[27713:15771147] [OutgoingMutationQueue] enqueue(_:)
2023-02-03 17:39:06.129144-0800 DatastoreAPISample[27713:15771965] [StateMachine<State, Action>] Notifying: enqueuedEvent
2023-02-03 17:39:06.129255-0800 DatastoreAPISample[27713:15771965] [StateMachine<State, Action>] resolve(requestingEvent, enqueuedEvent) -> waitingForEventToProcess
2023-02-03 17:39:06.129316-0800 DatastoreAPISample[27713:15771965] [OutgoingMutationQueue] New state: waitingForEventToProcess
2023-02-03 17:39:06.129932-0800 DatastoreAPISample[27713:15771145] [SyncMutationToCloudOperation] main()
2023-02-03 17:39:06.130004-0800 DatastoreAPISample[27713:15771145] [SyncMutationToCloudOperation] sendMutationToCloud(withAuthType:)
2023-02-03 17:39:06.134862-0800 DatastoreAPISample[27713:15771145] [SyncMutationToCloudOperation] sendMutation(describedBy:) sending mutation with sync data: GraphQLRequest<MutationSync<AnyModel>>(apiName: nil, document: "mutation CreatePost($input: CreatePostInput!) {\n  createPost(input: $input) {\n    id\n    createdAt\n    pictureKey\n    postBody\n    updatedAt\n    postedBy {\n      id\n      createdAt\n      profilePic\n      updatedAt\n      username\n      __typename\n      _version\n      _deleted\n      _lastChangedAt\n    }\n    __typename\n    _version\n    _deleted\n    _lastChangedAt\n    owner\n  }\n}", variables: Optional(["input": ["userPostsId": Optional("8776873F-06D2-4E10-85AE-478D099C2CEF"), "createdAt": Optional("2023-02-04T01:38:51.053Z"), "postBody": Optional("HERE IS 7C1D9247-E161-4031-A239-B870A95DF7FD"), "id": Optional("E8AC9071-93A7-48CE-9911-944FFD092EC7"), "pictureKey": Optional("EMPTY")]]), responseType: AWSPluginsCore.MutationSync<AWSPluginsCore.AnyModel>, decodePath: Optional("createPost"), options: Optional(Amplify.GraphQLRequest<AWSPluginsCore.MutationSync<AWSPluginsCore.AnyModel>>.Options(pluginOptions: Optional(AWSPluginsCore.AWSPluginOptions(authType: nil)))))
2023-02-03 17:39:06.135941-0800 DatastoreAPISample[27713:15771145] [OutgoingMutationQueue] respond(to:): waitingForEventToProcess
2023-02-03 17:39:06.135980-0800 DatastoreAPISample[27713:15771965] [API] Starting mutation C92C6A68-AB1D-4ABA-B4C1-464D14F59573
2023-02-03 17:39:06.136124-0800 DatastoreAPISample[27713:15771965] [API] {
  "query" : "mutation CreatePost($input: CreatePostInput!) {\n  createPost(input: $input) {\n    id\n    createdAt\n    pictureKey\n    postBody\n    updatedAt\n    postedBy {\n      id\n      createdAt\n      profilePic\n      updatedAt\n      username\n      __typename\n      _version\n      _deleted\n      _lastChangedAt\n    }\n    __typename\n    _version\n    _deleted\n    _lastChangedAt\n    owner\n  }\n}",
  "variables" : {
    "input" : {
      "userPostsId" : "8776873F-06D2-4E10-85AE-478D099C2CEF",
      "createdAt" : "2023-02-04T01:38:51.053Z",
      "postBody" : "HERE IS 7C1D9247-E161-4031-A239-B870A95DF7FD",
      "id" : "E8AC9071-93A7-48CE-9911-944FFD092EC7",
      "pictureKey" : "EMPTY"
    }
  }
}
2023-02-03 17:39:06.136661-0800 DatastoreAPISample[27713:15771145] [AWSAuthFetchSessionTask] Starting execution
2023-02-03 17:39:06.136718-0800 DatastoreAPISample[27713:15771145] [AWSAuthTaskHelper] Check if authstate configured
2023-02-03 17:39:06.136814-0800 DatastoreAPISample[27713:15771145] [AWSAuthTaskHelper] Auth state configured
2023-02-03 17:39:06.136883-0800 DatastoreAPISample[27713:15771145] [FetchAuthSessionOperationHelper] Fetching current state
2023-02-03 17:39:06.136928-0800 DatastoreAPISample[27713:15771145] [FetchAuthSessionOperationHelper] Session exists, checking validity
2023-02-03 17:39:06.137410-0800 DatastoreAPISample[27713:15771145] [API] Starting network task for mutation C92C6A68-AB1D-4ABA-B4C1-464D14F59573
2023-02-03 17:39:06.489721-0800 DatastoreAPISample[27713:15771147] [SyncMutationToCloudOperation] GraphQL mutation operation received result: success(Swift.Result<AWSPluginsCore.MutationSync<AWSPluginsCore.AnyModel>, Amplify.GraphQLResponseError<AWSPluginsCore.MutationSync<AWSPluginsCore.AnyModel>>>.failure(GraphQLResponseError<MutationSync<AnyModel>>: GraphQL service returned a successful response containing errors: [Amplify.GraphQLError(message: "The variables input contains a field name \'userPostsId\' that is not defined for input object type \'CreatePostInput\' ", locations: nil, path: nil, extensions: nil)]
Recovery suggestion: The list of `GraphQLError` contains service-specific messages))

```
Is this a regression?
No
Regression additional context
No response
Device
Simulator
iOS Version
16
Specific to simulators
No response
Additional context
No response

Looking at the schema, I suspect there are a couple things wrong here. This schema was used as-is from V1 transformer for V2 transformer without running a migration on it. (https://docs.amplify.aws/cli/migration/transformer-migration/).
The operations set on the auth rule indicates that only the owner can create and delete their data, and cannot update or read the data.
@auth(rules: [{ allow: owner, operations: [create, delete] }])

In Transformer V2, with the new deny-by-default paradigm, the operations only specifies what the owners can do. By not having read access, data cannot be synced via syncQuery API or subscriptions. We should simply allow all owners of their data to read, update, delete their data:
@auth(rules: [{ allow: owner }])

Second issue, according to the documentation in https://docs.amplify.aws/cli/graphql/data-modeling/#belongs-to-relationship, @hasMany directive takes in two arguments, indexName and fields. In this schema, @hasMany uses fields but missing the name of the index.
posts: [Post] @hasMany(fields: ["id"])

Then on the child model, there should be an @index with the same index name.
I tried this out with in User2/Post2 which removes the use of fields and User3/Post3 which specifies the indexName and index.
type Post
    @model
    @auth(rules: [{ allow: owner }]) {
    id: ID!
    postBody: String!
    pictureKey: String!
    createdAt: AWSDateTime!
    postedBy: User @belongsTo
}

type User
    @model
    @auth(rules: [{ allow: owner }]) {
    id: ID!
    username: String!
    profilePic: String!
    posts: [Post] @hasMany(fields: ["id"])
}

type Post2
    @model
    @auth(rules: [{ allow: owner }]) {
    id: ID!
    postBody: String!
    pictureKey: String!
    createdAt: AWSDateTime!
    postedBy: User2! @belongsTo
}

type User2
    @model
    @auth(rules: [{ allow: owner }]) {
    id: ID!
    username: String!
    profilePic: String!
    posts: [Post2] @hasMany
}

type Post3
    @model
    @auth(rules: [{ allow: owner }]) {
    id: ID!
    postBody: String!
    pictureKey: String!
    createdAt: AWSDateTime!
    postedBy: User3 @belongsTo(fields: ["userId"])
    userId: ID @index(name: "byUser")
}

type User3
    @model
    @auth(rules: [{ allow: owner }]) {
    id: ID!
    username: String!
    profilePic: String!
    posts: [Post3] @hasMany(indexName: "byUser", fields: ["id"])
}

I can see they are both exposing the foreign key field in the CreatePostInput

The updated schema then should be this: https://github.com/aws-amplify/amplify-ios-samples/pull/21

Updating to the v2 transformer schema fixed the issue.


Links in pip page are broken

Links in the body of the description page for the project are broken:
https://pypi.org/project/google-api-python-client/
The following links are broken:

"docs folder" - under section Google API Client
"Migration Guide" - under section Version 2.0 Release
"docs folder" - under section Documentation
"Contribution Guide" - under section Contributing

Hi @dcamdupe,
Thanks for reporting this! This will be fixed in #1251


feat/zep vectorstore

Description
Zep Vector Store implementation, notebook example, and docs.
Fixes # (issue)
Type of Change
Please delete options that are not relevant.

[X] New feature (non-breaking change which adds functionality)
[X] This change requires a documentation update

How Has This Been Tested?
Notebook pretty much tests end-to-end. Tested against Zep 0.9. Note that I need to push a patch-level bugfix to Zep in order to make the metadata filtering work. Will happen tonight.

[ ] Added new unit/integration tests
[X] Added new notebook (that tests end-to-end)
[X] I stared at the code and made sure it makes sense

Suggested Checklist:

[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

This looks great! Thanks for the contribution.
Small ask: could you add an entry to the table in docs/core_modules/data_modules/storage/vector_stores.md as well? Mostly to document which subset of features are supported.

@Disiok Done!

/-: My IDE reformatted the markdown table. Sorry for the large diff...


Make delay incurred from additional syringe contents modifiable + tiny syringe buff/fix

Why / Balance
My next PR requires my new syringes to have both short doafter and a high transfer amount.
With this change, the new prototype can be told not to do any delay scaling according to the transfer amount.
Also this PR contains a small fix/buff for syringes.
According to #12173, the intent was to have each additional 5u cause a delay increase of 1 second.
However, due to some bad math in #14441, and the fix for that calculation in #25890, the equation got left in a state where each 5u of the transfer amount was affected by the doafter delay increase, instead of only the additional doses being affected.
Here's an illustration of the delays over those PRs:

dose
12173
14441
25890
this pr

5u
0s
0.5s
0.5s
0s

10u
1s
1.5s
1.0s
0.5s

15u
2s
2.5s
1.5s
1.0s

Technical details

Added DelayPerVolume datafield to the injectorComponent, which tells how the injection doAfter increases with the transfer amount.
Also moved the minimum delay check so negative DelayPerVolume can't get the delay under 1 second.
Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

tweak: Syringes are now 0.5 seconds faster.

kind of strange to make an exception in the math for units under 5, feels like it'd be more simple to just adjust the do-after time to line up with the goal

Yeah, kinda forgot about the possibility of transfer amount being < 5u... I guess I'll go and try to fix it then

Yeah, kinda forgot about the possibility of transfer amount being < 5u... I guess I'll go and try to fix it then

the only reason I think about the non-standard values is because I'm a freak of a janitor that uses a syringe and a dead mouse body to clean up puddle spills, so I end up with weird units and decimals all the time, that's why I PR'd so many fixes the syringes lol

Actually I don't really think it needs to be changed for amounts < 5u, since 5u is/was supposed to be the point for minimum amount of chems injected/drawn, and with this exception 5u matches exactly Delay.

syringes my beloved


R-T5.3-4: The tool should be able to support configuring automatic scaling of Docker services based on TOSCA auto scaling policies.

ID:
R-T5.3-4

Type:
PORTABILITY

User   story:
As an Operations Engineer, I want to   configure automatic scaling in a Docker based enviorement

Requirement:
The tool should be able to support   configuring automatic scaling of Docker services based on TOSCA auto scaling   policies.

Extended   Description:
The goal is to set up auto scaling for   components that have been deployed as a service in a Docker swarm or Kubernetes.   Depending on the target platform, it may be required to deploy a separate   component for enacting the auto scaling descisions.

Priority:
Should have

Affected   Tools:
ORCHESTRATOR

Means   of Verification:
Use simple load tests to verify that the   data pipeline tasks deployed to docker enviorenment are scaled up and down   according to the policy setting when autoscaling trigger tresholds are   reached.

As of now auto scaling is not explicitly supported within xOpera, related to this: #25.

We have released new version - 0.6.5 of opera orchestrator, which introduces the new opera notify CLI command that enables invoking TOSCA triggers from policies and will therefore enable scaling.


[test] enable build with JDK17+

Motivation
Since JDK17 the illegal accesses to the JDK classes are forbidden. Mockito needs to access those classes.
Modifications

Changed test runtime options with a minimal configuration to let Mockito work

Documentation

[x] no-need-doc

JDK8 won't compile with --add-opens flag. we need to remove jdk8 compatibility first.

JDK8 won't compile with --add-opens flag. we need to remove jdk8 compile compatibility first.

@nicoloboschi I don't think so. You should add the --add-opens java.base/java.lang=ALL-UNNAMED in a different location. there is test.additional.args property for this purpose.
It should be fine to add --add-opens java.base/java.lang=ALL-UNNAMED to the existing jdk11 profile (we should avoid adding a jdk17 if we can):
https://github.com/apache/pulsar/blob/3c29c7e9c31b1f44ce86ba91f34a5127b3409dfa/pom.xml#L1881-L1882

you're right @lhotari. I updated the PR as you suggested. thanks


Upgrade Litle SDK from 9.10.0 to 9.12.2 throwing NullPointerException

Exception in thread "main" java.lang.NullPointerException
at com.litle.sdk.Communication.requestToServer(Communication.java:130)
at com.litle.sdk.LitleOnline.sendToLitle(LitleOnline.java:706)
at com.litle.sdk.LitleOnline.authorize(LitleOnline.java:165)
at com.litle.sdk.LitleOnline.authorize(LitleOnline.java:157)
at com.jtv.vantiv.AuthExample.main(AuthExample.java:91)

Hi,
Are you having this problem with all the samples or just the AuthExample?

My payment code works fine with 9.10.0. I tried my code and AuthExample in version both are having same issue

I tried AuthExample only in 9.12.2 version.

I am trying to reproduce this error, which version of Java are you using on which OS?

Java 1.8 and line os

There is a difference between Java 7 and 8 in terms of HTTP protocols that was allowing out test environment (Java 7) to work correctly but fail in Java 8. I have update the relevant code and am running tests in both Java environments. After successful testing I will update the releases to have the corrected code.

updated release after testing for Java 7 & 8, can you try the new jar to see if it works for your environment?

Issue fixed.
Thank you.


New Tractus-X project contributor

Before requesting the project contributor role, please make sure, that you:

Make yourself familiar with the Eclipse Foundation project roles: https://eclipse-tractusx.github.io/docs/oss/contributor-committer
Make ourselves familiar with prerequisites, like a signed ECA: https://eclipse-tractusx.github.io/docs/oss/getting-started
Check the committer list of our project and highlight at least one of them on this issue, since every committer
can add project contributors: https://projects.eclipse.org/projects/automotive.tractusx/who

Necessary Information
Email address to add<EMAIL_ADDRESS>Committers, that could take over: @evegufy @oyo
Please make sure, that you accept the invitation you receive from GitHub, after you have been added as project contributor.

I added you as a contributor: https://accounts.eclipse.org/users/jordancx pls verify

I added you as a contributor: https://accounts.eclipse.org/users/jordancx pls verify

Hi @Siegfriedk, I think Jordan is still missing membership in github organization https://github.com/orgs/eclipse-tractusx/teams/automotive-tractusx-contributors
CC: @JordanGerada3


How can i custom worker for python intellisense?

Hello, i have integrated monaco-editor into our projects. it's a wondeful tools, repectively. But my projects member mainly want to support python code. how can i custom a worker for this task?

You can use this :

https://github.com/palantir/python-language-server
Together with :
https://github.com/TypeFox/monaco-languageclient
https://github.com/TypeFox/vscode-ws-jsonrpc
https://github.com/TypeFox/vscode-languageserver-node

@jacobyf or @alexandrudima  did you end up setting this up? We're about to start building this out ourselves.

@pkpp1233 Look at the example in monaco-languageclient. It shows how to connect the Monaco editor with the JSON language server, you can do the same for python. Also this blog post exlpains it.

I had try to use Python-language-server.And pyls  may use TCP connect.
So, if I use the code like JSON-server ,it can not  work..
Area there anybody workout?

@Jandou6 The example in monaco-languageclient shows how to connect the external JSON server process:
https://github.com/TypeFox/monaco-languageclient/blob/b901301fe10c7a51e3b6faa35863bb69c93fcd11/example/src/json-server-launcher.ts#L17-L28
You should be able to spawn pyls process and connect to it in the same way.

I am trying to do the same as @Jandou6 and as suggested by you, but I am getting this error:
Launching PYTHON Server failed: Error: spawn pyls --tcp --host <IP_ADDRESS> --port 5000 ENOENT

Hi
I am able to run all these language server(through monaco language client + monaco editor):
https://github.com/palantir/python-language-server
https://github.com/sourcegraph/javascript-typescript-langserver
https://github.com/felixfbecker/php-language-server
https://github.com/sourcegraph/go-langserver
but somehow not able to run this:
https://reviews.llvm.org/diffusion/L/browse/clang-tools-extra/trunk/clangd/
do I need to do something different?


Updated Binary Neural Classification with Tabular Data Example

Updated the old binary neural classification with tabular data example. Runs end-to-end with code-supplied scikit-Learn toy breast cancer tables. Updated narrative and results.  Good to go.

Looks good to me.


bug: Calendar view not updating

https://github.com/user-attachments/assets/3642fe1b-03a1-4d79-ac89-aea660bfd0e5

    <Popover modal={true}> // in event-form.tsx

This will fix this issue , @hkirat

    <Popover modal={true}> // in event-form.tsx will fix this issue

setting modal={true} will fix this issue @hkirat

@Ashutoshpadhi629, you wish to rise a PR?

just raised one , with another issue


Add Apex FP to showcase

Motivation
Hi, I'd like to add Apex FP to the showcase.
Have you read the Contributing Guidelines on pull requests?
Yes.
Test Plan
Check if Apex FP is added to the showcase.
Related PRs
None.

Thanks 👍


HTTP Task Failure upon error status code

Describe the bug
As a user of the flow HTTP task, I would expect that a task would fail if the service returns  a 5xx status code.
To Reproduce
Run a task and make an http request that will return in a 5xx response code. The task will still succeed
Expected behavior
Expected the task to have failed.
Additional context
Raised by Luis - situation where they want to apply different logic if for example, "a tenant already exists"

Hey @morarucostel could you investigate this one to see what would need to change? For now, this is an investigation only to see the detailed technical design of what would need to change.

I think the design of the HTTP Task should follow these lines:

It should NOT fail the task based on the http status code. Doing that it encapsulates logic into the Task, logic that will limit the user's ability to model the workflow.
The HTTP task should set as output parameter the http response code. Then the flow logic can be desinged based on a switch with a regex of a response code, allowing fallbacks, retries with sleep or anther path to the flow.
Also the response Headers should be available as output parameters, to increase the ussage of the flow
The HTTP Task should allow for the non JSON response to get received and returned (currently it is doing a response = JSON.parse(output) and thus forces the output to be a JSON, even a valid HTML will fail the task),
The Task should allow both HTTP and HTTPS calls (currently it allows just https - fails when provided an http address),

Hey @tlawrie , what do you think?
Should I take a stab at it and try to implement the points from above?

Hi @morarucostel so we have the concept of a link state i.e. the always, on success, on failure that can be attributed to whats next. That was built for this exact purpose around what is a 'failure'.
So could we not follow the logic that 4xx and 5xx are failures?

4xx client error – the request contains bad syntax or cannot be fulfilled
5xx server error – the server failed to fulfil an apparently valid request

Regarding the points you make above, they are also valid

On error, IF we don't agree that errors should result in error path (which i think a strong argument could be made for) then we could have a drop down in the task itself for specifying code range of success? i.e. do I expect a 200 or a 400 or what now.
Agree. Response code should be an output parameter
Im not sure what you mean by response headers but again, more output parameters the better in this case
Should the task ask what the response is?
Agreed. HTTP and HTTPS should be supported. again it can programmatically figure it out or we can ask the user on the task.

hey @morarucostel is this now closed via #45 as well?

hey @tlawrie , not sure about the #45 , actually this one is closed by
this one is now closed via https://github.com/boomerang-io/worker.flow/pull/45

Thanks for confirming. Closing issue.


Provide async space reserver to reserve space background.

Is your feature request related to a problem? Please describe.

The worker cpu usage is 100%, the stack shown that we worker is freeing space all the time.
Describe the solution you'd like
Use high-low watermark async space reserver to free space.
Describe alternatives you've considered
Bring the removed code back.
Urgency
Normal
Additional context
NO

@apc999 Please take a look, Any thoughs?

Could you clarify what does "all the time" mean? Are you trying to say there are many threads with call-stacks like this one you shared, or is this the only one?
Also, what kind of workload were you running to get to this state? Did you observe throughput decrease on any particular scenario? If yes, what it is and how do you measure the throughput?

For your reference, async space reserver is gone so that each write can find and evict the ideal spot in-line with the operation. The old way was for writes to get blocked until space reserver is finished, which was creating many limitations in workers to perform under peak load.
If you think you need async space reserver, you can then try setting alluxio.worker.tieredstore.free.ahead.bytes to something greater than 0. This would cause the first evicting-write to free ahead specified amount of bytes on the worker, so that next writers can just land on already freed space.

"all the time" mean that we capture the stack many time, and we can see the freeSpace callstack each time. as the freeSpace is synchronized so other writer will step into until currect freespace finished by current writer.

Also, what kind of workload were you running to get to this state? Did you observe throughput decrease on any particular scenario? If yes, what it is and how do you measure the throughput?

Three worker with fifty million files, during load files I guess. @shenghuihe Could give more detail?

you can then try setting alluxio.worker.tieredstore.free.ahead.bytes to something greater than 0. This would cause the first evicting-write to free ahead specified amount of bytes on the worker, so that next writers can just land on already freed space.

This will help for the following writers, but is still affect the performance for current writer if setting alluxio.worker.tieredstore.free.ahead.bytes to a bigger value.  So I think alluxio.worker.tieredstore.free.ahead.bytes is a batch approach, but not async approach, leverage the async high-low watermark space reserver, writer will not stuck.

"all the time" mean that we capture the stack many time, and we can see the freeSpace callstack each time.
That does not mean freeing space is consuming your CPU. It just means you're out of worker space and probably trying to push more data.

as the freeSpace is synchronized so other writer will step into until currect freespace finished by current writer.

Compared to old async reserver, there's much less overhead in freeSpace. Because all blocks are already stored in eviction order, freeSpace is just a delete on local file system.

leverage the async high-low watermark space reserver, writer will not stuck.

Just imagine as if the writer that's evicting the space ahead is blocked on async reserver task to finish. So writer will get stuck either way, why do you care which thread is doing the work?

@calvinjia I wonder what's your take on this?

@maobaolong   @ggezer  about 10 threads  write the same worker at the same time,  and  all blocked at freespace。。


[stable/traefik] Specify Annotations for Service Account

Signed-off-by: Yong Wen Chua<EMAIL_ADDRESS>
Is this a new chart

NOTE: We're experiencing a high volume of PRs to this repo and reviews will be delayed. Please host your own chart repository and submit your repository to the Helm Hub instead of this repo to make them discoverable to the community. Here is how to submit new chart repositories to the Helm Hub.

What this PR does / why we need it:
Support use cases like:

GKE workload identity: https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity
EKS IAM roles for service accounts: https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/assign @timoreimann

/ok-to-test

@dtomcej any review? I know this is deprecated but the previous PR that introduced a separate service for Prometheus broke Prometheus scraping.

Not stale

Not stale

@dtomcej can I get this approved please?

Bump.

Closing. Waste of time keeping this alive.


Escape characters in blocks are missing (maybe gene or block)

When synchronization occurs, if there is a block replicated with "\/" it will become "\", which is wrong.

related to d947ca0d8b77070ebd1a9db0a9b27cbabd4c4c07
iterate to gene 0.1.4

6c961661bc60f17550efae1db5400cf460ca5888

Dot char "." must be escaped . on replacements


Enable user to specify empty peers in config

Finishes https://www.pivotaltracker.com/story/show/156540279
Please refer to commit message for details.
Background: Mainly started for reviewing system tests PR on 0.10.1.

I will add line in release notes after new release notes document is planted https://www.pivotaltracker.com/story/show/156411747

Merged as PR 912 depending on this. I will shortly open PR with release notes line.


Reported Vulnerability for package trim-newlines/1.0.0 with node-sass/4.14.1 version

Hi Node-Sass Team,
I am using node-sass/4.14.1, and this package using internally trim-newlines/1.0.0 addon with path
( node-sass/4.14.1/meow/3.7.0/trim-newlines/1.0.0 ) ,
During  scan check this addon reported vulnerable and expecting latest version of this. So could you please work on this by update the package.json for node-sass/4.14.1 to get the latest of trim-newlines.
Please do needful.
Thank you

We don't support old versions of the packge, just the latest release


Update interested-technical-writers.md for GSoD

@emckean
As per your instructions earlier I have sent the PR again.

Closing this pull request as the 2021 program is over. The 2022 program will begin soon; you can add your information in the 2022 interested technical writers file.


Optimization for opportunistic charging

Is your feature request related to a problem? Please describe.
No.
Describe the solution you'd like
Have option to trigger opportunistic charging when tomorrows price is lower than this night, even if price for this night is under price limit. Picture attached for this night. Something that would trigger opportunistic charging when price for last hour of tomorrow is cheaper than it would be tonight (maybe even another slider so that if tomorrows price is 0-200% from the price it would cost tonight to charge after minium SOC has been reached).
Describe alternatives you've considered
N/A
Additional context
Thanks for integration, it has been working great!
Here is charging schedule for tonight. Price tonight is under price limit and opportunistic level limit. It clearly still would be chaper to charge to minium SOC (in picture current EV SOC>minium EV SOC), and charge to full next night. Prices vary so much from night to night, that it is hard to have fixed monetary limit. It would be easy to set percent limit that controls opportunistic charging (for example 110% from tonights price).

Thanks for the feedback and the question.
I would guess that you have set select.ev_smart_charging_charge_completion_time to some certain time. If so, then what you see is the expected charging schedule. In order to achieve what you ask for, you would need to set select.ev_smart_charging_charge_completion_time to None.

Thanks for the feedback and the question.
What is the SOC of the car? If it's below 60% (below the Minium EV SOC), then that could explain what you see.

It is 69% now.

If you check the attributes of the main sensor entity, what is Charging is planned set to?

Charging is planned: true

Hmm. Weird. Can you paste all the attributes here?
And what Target SOC and number.ev_smart_charging_charging_speed do you have?

Thanks. I will look into this more.
By the way, did this happen directly after restarting Home Assistant?
If you click on "Smart charging activated" twice (to turn it off and then on again), the charging schedule should be recalculated, and maybe that will give you a correct charging schedule.

Maybe i explained this badly.
it recalculates it ok. It changes when i change price limit etc.
If i understand opportunistic mode right, this is how it should work now? It is scheduled 1 hour at 0.00, That is cheapest hour before 7.00 (completion.time).
Also at 0.00 price is 6,72cent < 12cent*0,6 (Price limit * Opportunistic level).
What i am suggesting that there is new/alternative mechanism for opportunistic charging that works something like this

When price at A is higher than at B * settable percent, only charge to minimum SOC and do not care at all what price limit is set at. Here A is first cheapest hour AFTER minimum SOC has been reached.

I understand what you mean. What you ask for is how it should work. If opportunistic charging is enabled, there shouldn't be any chargingen at A. And since you have set the completion time to 07:00m then there should not be any charging at B either now. The charging at B shoulfd appear after noon tomorrow, after the prices for the day after tomorrow is available.
So if you have had opportunistic charging enabled and the integration has scheduled charging at A, then there is something wrong.

Ok. i did not understand opportunistic charging right then. Now it just seems to lower price limit to Electricity price limit * Opportunistic level / 100 when I have opportunistic charging on.
I understand that there should not be any scheduled charging at B, Price at B should still used as Electricity price limit?

Sorry. Now I looked again. I did missunderstood you.
There is no bug in the code. It is working as intended.
My intention was that if the last hour tomorrow has a price less than Electricity price limit * Opportunistic level / 100 then the price limit will be lowered to Electricity price limit * Opportunistic level / 100.
I think what you ask for could be expressed as in addition to lower the price limit, the select.ev_smart_charging_charge_completion_time should be ignored.

So then it will become like this instead:

Kinda yes. but also no.
If select.ev_smart_charging_charge_completion_time is set, it must always be scheduled to meet minium ev soc limit to be charged before that.
If price for last hours next day (black bar in your drawing) is lower than lowest price before select.ev_smart_charging_charge_completion_time (after reaching minimum soc level), then stop charging for this session. No need to calculate any electricity price limit/opportunistic level, becouse it is 100% sure that next night is cheaper in any case (atleast for first hour or so).

Yes, agree. And then it becomes much more complicated than I first thought. The integration is now started to reach the limit on how complicated rules the current design can handle. I need to think if this can be achieve with a reasonable effort.
Note that another way to look at this is that you could have set number.ev_smart_charging_opportunistic_level to a lower value if you wanted to be more agressive in the opportunistic savings. If it had been set to 50%, you wouldn't had get any scheduled charging this night.

What if last hour of tomorrow * opportunistic level (50%-150%) is used as Electricity price limit?
I would like to have some kind of set and forget, that is why this automation is so good.
But when electricity price range from 0,5cent to 50cent/kwh in one month, it is impossible to set any limits to price that would work.
We all know that if last hour of tomorrow is lower than tonight, it is less than likely cheaper to postpone charging. That is not fixed as electricity price limit is.

Thanks for that suggestion. That would be easy to implement. Let me think about that.
It is my intention to make it "set and forget".

The intention of the current switch.ev_smart_charging_apply_price_limit is to avoid charging at home if the electrity price is high compared to other ways of charging, such as public charging or charging at you work place.
And then switch.ev_smart_charging_opportunistic_charging was added to make it possible to optimize the cost a little more.
Now, with the suggestion "last hour of tomorrow * opportunistic level (50%-150%) is used as Electricity price limit", the orignal fixed price set by switch.ev_smart_charging_apply_price_limit is not used at all, right?
So my observation is that this suggestion is not an improvement of the current switch.ev_smart_charging_apply_price_limit and switch.ev_smart_charging_opportunistic_charging, but a suggestion to have a different strategy to limit charging. And this strategy does not have an upper limit on the electricity price, meaning that charging will happen even if the price might be very high.
Would you agree on that? And is that what you really want? I don't think that was in your original request.

That would be ok for me. Charging to min soc for whatever price should be done anyways.
Is it possible to leave price limit as it is, and have option to turn this new limit on? When using price limit, we have allready ok with the possibility that charging stops on minium soc level.
Then i ihink that logick could be somethinh like rhis.
If (price to charge over minimum soc) > (price limit OR last price next day) --> only charge to minimum soc.

Sorry for interfering but was trying out the opportunistic charging feature and didn't really understand how this was calculated, was first looking into the code/PR, which lead me to this issue.
I just want to quickly describe my take on this challenge. Every day I compute a custom price limit as an average of the price at 23:00 today and the price at 23:00 tomorrow, i.e., if today's price at 23:00 is DKK 1.50 and tomorrows price at 23:00 is DKK 1.10 then I will set a custom price limit of DKK 1.30. This has been working out quite well for a month and will keep postpone charging "until tomorrow" if the price is continuously dropping. Of cause minimum SoC is still obeyed as long as the original price limit is the max.
An opportunistic level could of cause balance how strict towards highest vs lowest "23:00" price one wants to set the custom limit, though for me an average price has worked out quite well.
Just my 2 cents..

That is about same as i am doing (except we got prices always to 1;00 morning).
So if instead just using fixed price limit, could we use last price (1:00 here) as limit if it is lower than fixed price limit? And maybe settable percent on top of last price.
So when price limit is 10cent, and last price tomorrow is 11 cent, limit would be 10 as it is now. If last price tomorrow is 9 cent, use that as price limit instead of 10 cent. I have used tomorrows last price-10%, but i thik average could also work as well if not even better.

@janneho Yes this does indeed sound quite like the same approach, defining a variable max price limit to either prioritize charging this night, if price seems lower, or postpone until tomorrow if we estimate prices will drop lower then.
I started out using lowest price of tonight 23 vs tomorrow at 23 (last avaliable hour in DK) but sometimes prices doesn't drop any further during the night and only few hours were able to charge due to limit. I guess the usual price variations may vary between countries?

It really is somewhat guessing for tomorrows price but it works quite well and do not charge if tomorrows price is lower.
I have made quick dumb hacky automation, that somewhat works... It just calculates limits at 15:00 (we get new prices at 14:00) Everything is hard coded, 10 cent is max price limit.
description: Calculate limit from nordpool
trigger:
  - platform: time
    at: "15:00:00"
condition: []
action:
  - if:
      - condition: template
        value_template: >-
          {{ (((state_attr('sensor.nordpool_kwh_fi_eur_3_10_01', 'today')[23]) +
          (state_attr('sensor.nordpool_kwh_fi_eur_3_10_01', 'tomorrow')[23])) /
          2) < 10}}
    then:
      - service: number.set_value
        data:
          value: >-
            {{ ((state_attr('sensor.nordpool_kwh_fi_eur_3_10_01', 'today')[23])
            + (state_attr('sensor.nordpool_kwh_fi_eur_3_10_01',
            'tomorrow')[23])) /2}}
        target:
          entity_id: number.ev_smart_charging_electricity_price_limit
    else:
      - service: number.set_value
        data:
          value: "10"
        target:
          entity_id: number.ev_smart_charging_electricity_price_limit
mode: single

Lol, almost a 1:1 copy of my automation, except I use energi data service 😁

Though some times this rule of thumb just does not apply :)

It is true that it does not always work. But still a lot better than fixed limit.
I have used this for a month for price limit, and it does work really well. So no averaging, just last price.
{{ ((state_attr('sensor.nordpool_kwh_fi_eur_3_10_01',
            'tomorrow')[23]) )}}


Error: The number of bands references in the ir. rep. groups is more than # modes = 24.

Hi,
I tried to follow the alpha-SiO2 steps for MgO (one of the examples of phonopy). The input files fc2.hdf5 and fc3.hdf5 were generated using phono3py with dimension for fc2 "2 2 2" and fc3 "1 1 1".
While using the following command.  I got the error.
phonopy-ir --ir_reps --linewidth_hdf5="kappa-m484848-g0.hdf5" --linewidth_temperature=300
The error looks like:
Frequencies and eigenvectors read from "mesh.hdf5"
Structure read from "phonopy.yaml"
Atomic masses read from "phonopy.yaml"
Linewidths read from "kappa-m484848-g0.hdf5" (T = 300.00 K)
Irreducible representations read from "irreps.yaml"
Traceback (most recent call last):
File "/global/homes/a/adhikari/Phonopy-Spectroscopy/Scripts/phonopy-ir", line 72, in
frequencies, 'thz', eigendisplacements, becTensors, args, linewidths = linewidths, irRepData = irRepData
File "/global/homes/a/adhikari/Phonopy-Spectroscopy/SpectroscoPy/CLI/Runtime.py", line 93, in RunMode_IR
'ir', frequencies, frequencyUnits, irIntensities, _IR_IntensityUnits, args, linewidths = linewidths, irRepData = irRepData
File "/global/homes/a/adhikari/Phonopy-Spectroscopy/SpectroscoPy/CLI/Runtime.py", line 465, in RunMode_Output
ptFrequencies, ptIntensities, ptIrRepSymbols, ptLinewidths = GroupForPeakTable(frequencies, intensities, irRepData, linewidths = linewidths);
File "/global/homes/a/adhikari/Phonopy-Spectroscopy/SpectroscoPy/TextExport.py", line 174, in GroupForPeakTable
raise Exception("Error: The number of bands references in the ir. rep. groups is more than # modes = {0}.".format(numModes));
Exception: Error: The number of bands references in the ir. rep. groups is more than # modes = 24.
Please help me in this matter.
Thank you,
Puja

Hi Puja,
Can you post the command lines you used to prepare the eigenvectors and ir. reps. using Phonopy?
The problem is most likely using the conventional cell rather than the primitive cell; Phonopy requires the primitive to calculate the ir. reps., and you should also use that for the Phonopy-Spectroscopy calculations.
Best wishes,
Jonathan

I also note that the error message is misleading -- it is triggered if the number of bands referenced by the ir. reps. is not equal to the number of modes; this will be fixed in the next update.

Hi Jonathon,
I used following commands:
phonopy --dim="2 2 2" --readfc --hdf5 --fc_symmetry=1 --mesh="1 1 1" --eigenvectors
phonopy --dim="2 2 2" --readfc --hdf5 --fc_symmetry=1 --irreps="0 0 0" setting.conf
setting.conf consists:
PRIMITIVE_AXIS = 0.0 0.5 0.5  0.5 0.0 0.5  0.5 0.5 0.0
Puja

Hi Jonathon,
Thank you for pointing it out. Now I tried:
phonopy --dim="2 2 2" --readfc --hdf5 --fc_symmetry=1 --mesh="1 1 1" --eigenvectors setting.conf
phonopy --dim="2 2 2" --readfc --hdf5 --fc_symmetry=1 --irreps="0 0 0" setting.conf
phono3py --dim="1 1 1" --dim_fc2="2 2 2" --fc2 --fc3 -v --br --thm --mesh="48 48 48" --write_gamma --gp=0
phonopy-ir --ir_reps --linewidth_hdf5="kappa-m484848-g0.hdf5" --linewidth_temperature=300
But now I get another error:
Frequencies and eigenvectors read from "mesh.hdf5"
Structure read from "phonopy.yaml"
Atomic masses read from "phonopy.yaml"
Traceback (most recent call last):
File "/global/homes/a/adhikari/Phonopy-Spectroscopy/Scripts/phonopy-ir", line 58, in
eigenvectors, atomicMasses
File "/global/homes/a/adhikari/Phonopy-Spectroscopy/SpectroscoPy/Utilities.py", line 148, in EigenvectorsToEigendisplacements
raise Exception("Error: The number of supplied atomic masses is inconsistent with the number of displacements in the eigenvectors.");
Exception: Error: The number of supplied atomic masses is inconsistent with the number of displacements in the eigenvectors.
Puja

OK :- getting there. I'll have to think about how best to work around this problem in the code.
For now, try the following:

Run phonopy --symmetry to obtain a PPOSCAR file with the primitive cell.
Open the file in a text editor and add the atom types below the fifth line (i.e. convert it to the VASP 5 format).
Remove (or rename) phonopy.yaml.
Run again with phonopy-ir --cell="PPOSCAR" --ir_reps --linewidth_hdf5="kappa-m484848-g0.hdf5" --linewidth_temperature=300.

[Basically, what's happening is that the structure read in by phonopy-ir is the conventional cell, which has a number of atoms that is now inconsistent with the number of eigenvectors and ir. reps. The current Phonopy interface doesn't consider the possibility of people projecting a conventional to primitive cell when doing the calculations.]
Jonathan

Hi Jonathan,
I tried  above steps and now I have another error:
Frequencies and eigenvectors read from "mesh.hdf5"
Structure read from "PPOSCAR"
Atomic masses taken from Phonopy database
Linewidths read from "kappa-m484848-g0.hdf5" (T = 300.00 K)
Irreducible representations read from "irreps.yaml"
Traceback (most recent call last):
File "/global/homes/a/adhikari/Phonopy-Spectroscopy/Scripts/phonopy-ir", line 72, in
frequencies, 'thz', eigendisplacements, becTensors, args, linewidths = linewidths, irRepData = irRepData
File "/global/homes/a/adhikari/Phonopy-Spectroscopy/SpectroscoPy/CLI/Runtime.py", line 93, in RunMode_IR
'ir', frequencies, frequencyUnits, irIntensities, _IR_IntensityUnits, args, linewidths = linewidths, irRepData = irRepData
File "/global/homes/a/adhikari/Phonopy-Spectroscopy/SpectroscoPy/CLI/Runtime.py", line 465, in RunMode_Output
ptFrequencies, ptIntensities, ptIrRepSymbols, ptLinewidths = GroupForPeakTable(frequencies, intensities, irRepData, linewidths = linewidths);
File "/global/homes/a/adhikari/Phonopy-Spectroscopy/SpectroscoPy/TextExport.py", line 157, in GroupForPeakTable
raise Exception("Error: If supplied, linewidths must have the same number of elements as frequencies and intensities.");
Exception: Error: If supplied, linewidths must have the same number of elements as frequencies and intensities.
Puja

OK :-
You will nees to recalculate your linewidths with the --pa command-line option (equivalent to the PRIMITIVE_AXIS settings tag).
I think Phono3py has this option.
Jonathan

Yes, it works. Thank you Jonathan.
Puja


Table 2 Question

Hi,
thanks for this cool work! I am a bit confused about table 2 , how do you evaluate exactly the "Accuracy of other
classes"? Do you generate 1 image per class of the 1000 classes of ImageNet or only of the classes in the table and then classify with ResNet?
Thanks!

Hi! We work on Imagenette (which is a subset of imagenet). The classes are shown in table2. As we described in the paper, we generate 500 images per class and then classify using resnet.

Hi,
What did you use as a guidance concept for each class in imagenette? Could you provide the list?


Add simple version test

See #133 .
Could be as simple as running select sqlite_version(); and ensuring it is above a certain value :)

Yes this is something we definitely should do

It also may be worth adding the sqlite version in a public method on the mix file and building a quick download script to update the amalgamation file.


Upstream proxy example

Go 1.9.1
go-mitmproxy 1.3.1
I was trying to set up an upstream proxy but did not succeed.
https://docs.mitmproxy.org/stable/concepts-modes/#upstream-proxy
I have a proxy with authentication, and after I've to set HTTP_PROXY and HTTPS_PROXY variables, it started giving Proxy Authentication Required error.
I've tried to fork your repo and set the proxy manually, but it didn't work and I haven't dived deep to figure out why.
Was curious if it can be done without any changes or does it require some changed to the current version?

Closed by https://github.com/lqqyt2423/go-mitmproxy/pull/30


Fix docsearch version metatag

The search doesn't work because the scraper can't
find the url with latest anymore.
This PR changes the meta tag, after merging I will update the crawler

Ah. Many thanks for fixing it.


MatchingEngineRouter only support one symbol now?

MatchingEngineRouter only support one symbol now?

Related logic was recently improved, please checkout current master branch.
Different symbol orderbooks are stored in the hashtable:
IntObjectHashMap<IOrderBook> orderBooks
and populated with series of BINARY_DATA messages. This makes symbol to be activated atomically.


Change NavRail position to center on large screen

Issue

On devices with large screens, the NavRail was positioned in the upper left corner.
On foldable devices, the size of the NavRail seemed small.

Overview (Required)

NavRail height changed to 420 dp.
NavRail centered vertically on the left side of the screen.

Links

Screenshot (Optional if screenshot test is present or unrelated to UI)

Before
After

Movie (Optional)

Before
After

Looks great! Thank you!


Problem starting the plugin

Build
https://dev.azure.com/dnceng/internal/_build/results?buildId=2503010
     3>Restore:
         Determining projects to restore...
         Evaluated 1 project(s) in 582ms (1 builds, 0 failures).
         X.509 certificate chain validation will use the default trust store selected by .NET for code signing.
         X.509 certificate chain validation will use the default trust store selected by .NET for timestamping.
         Restoring packages for D:\a\_work\1\s\eng\common\internal\Tools.csproj...
     3>D:\a\_work\1\s\.dotnet\sdk\9.0.100-preview.6.24328.19\NuGet.RestoreEx.targets(19,5): error : Problem starting the plugin 'C:\Users\cloudtest\.nuget\plugins\netcore\CredentialProvider.Microsoft\CredentialProvider.Microsoft.dll'. A task was canceled. [D:\a\_work\1\s\eng\common\internal\Tools.csproj]
##[error].dotnet\sdk\9.0.100-preview.6.24328.19\NuGet.RestoreEx.targets(19,5): error : (NETCORE_ENGINEERING_TELEMETRY=Restore) Problem starting the plugin 'C:\Users\cloudtest\.nuget\plugins\netcore\CredentialProvider.Microsoft\CredentialProvider.Microsoft.dll'. A task was canceled.
     3>D:\a\_work\1\s\eng\common\internal\Tools.csproj : error NU1301: Unable to load the service index for source https://pkgs.dev.azure.com/devdiv/_packaging/dotnet-core-internal-tooling/nuget/v3/index.json.
##[error]eng\common\internal\Tools.csproj(0,0): error NU1301: (NETCORE_ENGINEERING_TELEMETRY=Restore) Unable to load the service index for source https://pkgs.dev.azure.com/devdiv/_packaging/dotnet-core-internal-tooling/nuget/v3/index.json.
         Generating MSBuild file D:\a\_work\1\s\artifacts\obj\Tools\Tools.csproj.nuget.g.props.
         Generating MSBuild file D:\a\_work\1\s\artifacts\obj\Tools\Tools.csproj.nuget.g.targets.
         Writing assets file to disk. Path: D:\a\_work\1\s\artifacts\obj\Tools\project.assets.json
         Failed to restore D:\a\_work\1\s\eng\common\internal\Tools.csproj (in 26.68 sec).

Build leg reported
No response
Pull Request
No response
Known issue core information
Fill out the known issue JSON section by following the step by step documentation on how to create a known issue
 {
    "ErrorMessage" : "Problem starting the plugin",
    "BuildRetry": false,
    "ErrorPattern": "",
    "ExcludeConsoleLog": false
 }

@dotnet/dnceng

Release Note Category

[ ] Feature changes/additions
[ ] Bug fixes
[ ] Internal Infrastructure Improvements

Release Note Description
Additional information about the issue reported
No response

Known issue validation
Build: :mag_right: https://dev.azure.com/dnceng/internal/_build/results?buildId=2503010
Error message validated: [Problem starting the plugin]
Result validation: :white_check_mark: Known issue matched with the provided build.


Removed IFS + Added vmailbox config

Here is a fix for issue #121 and I went a bit further and added support for custom vmailbox settings (usefull for issue #57).
Now, you can define a /tmp/postfix/vmailbox (from within the container) that specifies extra virtual mail boxes. It is describe here: http://www.postfix.org/VIRTUAL_README.html#virtual_mailbox
Custom vmailbox settings are appended to the end of /etc/postfix/vmailbox, so after the generated content from accounts.cf.
What it allows is the support of routing all the other mail from a domain to a mail box.
For example:
accounts.cf:
<EMAIL_ADDRESS><EMAIL_ADDRESS>
vmailbox:
@domain.tld domain.tld/contact/
In this example, all the mails other than<EMAIL_ADDRESS>and<EMAIL_ADDRESS>will be placed in<EMAIL_ADDRESS>mailbox. Be aware that the trailing "/" is required !

Thank you @auguster


Safety of resume and suspend

As it currently stand, the methods Libinput::suspend() and Libinput::resume() are marked as safe, however given a quick glance in the source of libinput, it is pretty clear that calling libinput_suspend or libinput_resume twice in a row is going to corrupt the internal state.
So either these methods should be made unsafe with a warning, or they should be changed to be idempotent (with a boolean flag for example).

No wait, nevermind, I have read too quickly. The libinput functions are actually already idempotent.


New release upcoming?

Firstly, thanks very much for this project.  Has been invaluable.
When can we expect a new release?  Thanks!

Hey, the project is currently unmantained as @jevakallio is unavailable. We at https://github.com/redux-offline/redux-offline are currently working on it. You might want to check on its progress!

What it means: "@jevakallio is unavailable"? Is he active on other projects? Why he abandoned this one?

Please see: https://github.com/redux-offline-team/redux-offline/issues/117#issuecomment-333851443

Thanks @elf-pavlik. Can we close this now?

Thanks @johnunclesam


Fixes clashes with Scalaz implicits.

When importing scalaz syntax implicits at the same time as the resultant
monad implicits there would be clashes.
This fixes the clashes by:

Turning ResultantOps into a class that the companion object inherits
from.
Changing ResultantMonadSyntax so that the companion object mixes in
the implicit conversion trait.
Renaming ensuring to ensure in ResultantMonadSyntax to avoid
clashing with the inbuilt scala ensuring.  This closes #17.
Removing the ||| in ResultantMonadSyntax to avoid clashing with the
||| operator in Scalaz ChoiceOps.

:+1:


Issue with the JSON

Hi mcmilk,
I receive the following error on the unifi page can you help me to fix it? I have redownload your files and setup the config file but still the same. I run the script on ubuntu with xampp. When I create a voucher it will show in the unifi controler but not on the page vouchers then it will give this error:
DataTables warning: table id=myTable - Invalid JSON response. For more information about this error, please see http://datatables.net/tn/1

Will be fixed within some weeks ... sorry for the very long delay ;)


Closes #1

Updated validations.py to only allow Alphabet at the beginning of the username. Added test scenarios.
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

@googlebot I signed it!


Support debug build options

Currently, it is not straightforward to build and deploy packages with debug options. For the build, the CONAN_OPTIONS variable could be used like so:
make CONAN_OPTIONS="-s build_type=Debug" export  package
However, depending on which make targets are being used, all dependencies might be rebuilt with debug options as well. Some documentation or a dedicated make target would be desirable.
For the package deployment with the cli, the build type would need to be passed to cloe-launch (e.g. via the CONAN_OPTIONS variable).

The current best practice to achieve this is to use Conan profiles.
For an example, see the files in dist/conan, where debug build type is applied to all packages matching cloe/develop user-channel:
include(default)

[settings]
build_type=RelWithDebInfo
*/*@cloe/develop:build_type=Debug


[question] Confusion over null comparisons

I have a user-defined struct type X mapped into Koto. A free constructor method returns either Ok(X) or Ok(Value::Null) to indicate an empty result. Now if I assign that result to a variable in Koto x = generate_x() I can do this for example:
if x
  print "valid"

But I cannot do this:
assert_ne(x, null)

This will give me an error about @!= not being implemented for X. So my questions are as follows:

Is it bad design to return null to indicate an empty result?
What would be better? Return an Err or give X a method to check for an empty result? (I guess that's pretty much the same question that lead to Option<T> in Rust)
Why does if x work but not the assertion?

I think returning null from a constructor is fine, it communicates the equivalent of returning an Option<T> in Rust, which seems reasonable enough to me.
You've exposed a bit of a gotcha with the current Object system though...

if x works because of the truthiness rules; anything that isn't false or null is evaluated as true in a boolean context.
assert_ne(null, x) works because the operator system prioritises the value on the LHS: the assertion will pass for any RHS value except for null.
assert_ne(x, null) doesn't work because when an Object is on the LHS it unconditionally defers to the object's KotoObject::not_equal implementation.

I suspect that null on the RHS of equality comparisons is worth treating as a special case, I can't think of a good reason to want to customize the behaviour, and it seems like forcing implementations of equal/not_equal to avoid this kind of surprise would irritating for implementors..

Thanks, that makes sense. It looks as if special treatment is indeed necessary here.


Backport "Add formatters for Option, Map, Period, and Atoms" to LTS

Backports #19658 to the LTS branch.
PR submitted by the release tooling.
[skip ci]

No regressions detected in the community build up to lts-19080.
Reference


Setup linting and prettier

Currently, the app has ESLint installed but it isn't correctly configured. It throws a considerable amount of errors all around the codebase.
The idea would be to setup the linting tools and also prettier so it doesn't throw any errors.

closed by lbryio/lbry-app#911


Packagist package

Hi,
I would like to use this library in my composer project. Would you consider making this available on packagist?

Thanks for pinging me. This was the first standalone PHP library I published, so I'm still getting the hang of it.
Packagist requires a vendor prefix, so I changed the composer.json - the name is now wyz/practicalafas .


Generate TypeScript return types for async functions

Threads through an asyncness bool and an "inner" return value type descriptor for functions, then generates Promise<...> return types for async functions.
Fixes #2394

These tests are now failing, where before they were being covered up by the return type elision for async functions:
#[wasm_bindgen]
pub async fn async_return_7() -> Result<AsyncCustomReturn, u32> {
    Ok(AsyncCustomReturn { val: 7 })
}

#[wasm_bindgen]
pub async fn async_return_8() -> Result<AsyncCustomReturn, AsyncCustomReturn> {
    Ok(AsyncCustomReturn { val: 8 })
}

#[wasm_bindgen]
pub async fn async_throw() -> Result<(), js_sys::Error> {
    Err(js_sys::Error::new("async message"))
}

| the trait `wasm_bindgen::describe::WasmDescribe` is not implemented for `Result<AsyncCustomReturn, u32>`
|
= help: the following implementations were found:
<Result<T, wasm_bindgen::JsValue> as wasm_bindgen::describe::WasmDescribe>

Per the docs, they never should have been supported, and indeed, they don't work when removing the async:
The `Result` type can be returned from functions exported to JS as well as
closures in Rust. Only `Result<T, JsValue>` is supported where `T` can be
converted to JS. Whenever `Ok(val)` is encountered it's converted to JS and
handed off, and whenever `Err(error)` is encountered an exception is thrown in
JS with `error`.

Shall I just remove these tests?

Thanks for the PR! The implementation here looks pretty reasonable to me. I think it's fine to update those tests as well, yeah.
Can you add some specific tests for this new feature though? Ideally there'd be reference tests to see the output, tests in the main tests suite to exercise that things work, and tests in the typescript area to ensure that everything typechecks as expected.

@alexcrichton
I added a test in the typescript-tests area.
I don't see any existing reference tests at all for .d.ts output; am I missing something, or shall I add reference tests for .d.ts to the cli/tests/reference section? (Right now they just test the .js and .wat output)
Also, the only intended output change is to the .d.ts files, so there shouldn't be any new behavior outside of TypeScript, and existing async fn tests should still apply. Not sure if there was something specific you wanted me to add in the main tests suite?


Stable Release?

Is this functionality ever going to be released within a stable version? This has been in preview for over a year now, at least.

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

ID: 711d54ad-842b-2141-95b3-fc71d053dbac
Version Independent ID: be8e8253-7014-1065-ee9b-27a41d35b1ec
Content: Xamarin.Forms Themes - Xamarin
Content Source: docs/xamarin-forms/user-interface/themes/index.md
Product: xamarin
GitHub Login: @davidbritch
Microsoft Alias: dabritch

@ckrempp91, thanks for your feedback.
You can communicate directly with the engineering team via the Issues list on the open source Xamarin.Forms repo, as well as monitor work on the code.
For now, as far as the documentation is concerned, it remains a Preview feature.


Expose Camera APIs in iOS SDK

@blair1618 update with changes.

Tweaked some naming; I'm ready to merge this now as soon as builds pass.