refactor: search v1 endpoint and local-database

Current search endpoint is strictly linked with the local storage and the uplinks search. The search v1 #2256  runs in series using async #1225  for each uplink defined in the configuration, once has ended, fetch all dependencies in the local storage (it does not match any, just fetch all of them) then mix all results and on the endpoint filters and remove duplicates. This is not does not help on performance on huge storage with tons of packages.
This refactor will remove the old search endpoint and all the legacy code. The new search endpoint which does not fetch a huge JSON (like the old one) uses query parameters to limit results: eg 'GET /-/v1/search?text=react&size=20&from=0&quality=0.65&popularity=0.98&maintenance=0.5' thus, we know exactly what the user is looking for. We can pass this information to the local storage to filter efficiently (or plugin storage) and remove async in order to empower using streams and native JavaScript to improve the performance and remove all those abstractions.
The uplinks search is also using old library JSONStream which it owns objective was lead with the old search endpoint intended to stream a huge JSON file, we don't need that anymore since the payload get from the search v1 is smaller and not need to stream it right away.
⚠ this PR might take a while, a lot of test requires changes
Breaking changes

plugin storage API changes
remove old search endpoint (this might affect Unity integration) cc: @favoyang @hybridherbst  (if this is an issue we can find a workaround, early feedback is very welcome)

Key goals

remove async dependency by using native code
remove legacy code for streams endpoint
improve local-database methods by using Promises instead callbacks
improve types
update plugins documentation (breaking changes)
find a way to have a fallback to callback support (for easy migration)
improve logging

Ref: https://github.com/verdaccio/verdaccio/issues/2220
Task

[x] remove old endpoint search, (returns 404)
[ ]  ~get rid of async #1225~ not possible yet, uplinks sync metadata still uses it

[x] search refactor (cc: #2248 )
[x] local-storage refactor

[x]  promise instead callback
[x] refactor types (storage), remove duplications
[x]  improve streams usage
[ ]  remove legacy code
[x] polish search on uplinks (currently we are streaming expecting a huge JSON, this is not the case anymore for search v1)

remove old search endpoint (this might affect Unity integration) cc: @favoyang @hybridherbst  (if this is an issue we can find a workaround, early feedback is very welcome)

Thank you for the notification. I don't have a problem with removing the old /-/all endpoint. It gonna be an unscalable service at some point. Though at a smaller scale, it‘s still useful and the only way to get all packages information available on a registry.

Thanks for tagging me here –
From our testing against a dev server we know that Unity Package Manager currently uses only the /-/v1/search? endpoint.
So this definitely needs to stay, otherwise Verdaccio becomes incompatible with Unity Package Manager.
The /-/all endpoint is never called, at least right now, so this can disappear.
Requests to registry: https://packages.domain.com
When adding a scoped registry to Unity (with scope filter com.needle):
/-/v1/search?text=com.needle&from=0&size=250
This returns all packages matching the search.
For each found package, there's a call to
https://packages.domain.com/com.needle.some-package-1
https://packages.domain.com/com.needle.some-package-2
and then of course for downloading,
https://packages.domain.com/com.needle.some-package-1/-/com.needle.some-package-1-1.2.0.tgz
I don't think there are any other requests needed to support Unity, but happy to verify once you did these changes.

thanks for the feedback, I'll find a way to keep both,  maybe the /-/all enabled as a flag or something. Btw, since you are involved in that community, are they planning to upgrade? or are not aware the endpoint was deprecated?

Re.: Removing support for the /-/all endpoint. We are fully aware this is deprecated. Funny enough, we kept support for this endpoint because some registries, most notably Verdaccio, only supported this route! :)
Our search algorithm will always try /-/v1/search first. If the server returns a 404 on that route, we try /-/all next (evidently we fail if both don't work). So as @hybridherbst mentioned, to keep Verdaccio working with Unity's Package Manager if it only supports /-/v1/search route, you need to support searching on package name by a chunk of 250 items. In other words, when implementing the V1 spec  make sure to match the text query parameter against the package name and it should be fine with Unity Package Manager.

Re.: Removing support for the /-/all endpoint. We are fully aware this is deprecated. Funny enough, we kept support for this endpoint because some registries, most notably Verdaccio, only supported this route! :)

Fair enough, 👍🏼 🙃 . That's what I am changing.

Our search algorithm will always try /-/v1/search first. If the server returns a 404 on that route, we try /-/all next (evidently we fail if both don't work). So as @hybridherbst mentioned, to keep Verdaccio working with Unity's Package Manager if it only supports /-/v1/search route, you need to support searching on package name by a chunk of 250 items. In other words, when implementing the V1 spec  make sure to match the text query parameter against the package name, support page size of at least 250 and it should be fine with Unity Package Manager.

@hybridherbst then the version 5 should works already with Unity since the search v1 is enabled by default. Anyway, this PR will improve the performance of what is already implemented.
@okcompute thanks for your input and feedback is really valuable that I can implement this changes confidently 👍🏼 very appreciated.

I was wondering, this PR actually does provide query within the storage API event allowing add possible keywords or more advance filtering directly to the plugin or leave it to the core.
I had some ideas like could be extender in the future:

Disable uplinks search (opt-in)
Filters:

authors
keywords

The current state of this PR is:

Will look up in every uplink defined in the configuration and merge all results
Will lookup to the local storage (private and cached)  and filter by the text query parameter
Will remove duplicates
Apply from it is a bit tricky since there are two different sources of data
Apply size could be done to the whole result (but not at plugin level)

By running pnpm build && pnpm debug on this PR could be tested.
(Still work in progress, test are broken)

I still have to fix some test and finish the refactoring, but is good enough to move this on, I'll continue in other PR, this is getting big and old 😞 , but functional.

In case someone wants to try out
npm i -g<EMAIL_ADDRESS>
or docker nightly-master

@juanpicado,
Congratulations on finishing the big PR.
So this will be a part of verdaccio@6?

Yes, still not pretty stable, but we will get there.


Error: Cannot find module '../build/Release/kerberos'

Getting this error while accessing kerberos. And there is no folder with name build inside lib folder. What can be the issue?
Error: Cannot find module '../build/Release/kerberos'
at Function.Module._resolveFilename (module.js:469:15)
at Function.Module._load (module.js:417:25)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object. (/dev/my_proj/node_modules/kerberos/lib/kerberos.js:1:78)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)

I ran into the same error for tests running in travis . The root cause for failure was Error: Cannot find module 'minimatch', if you have the same cause or something similar, checkout this issue https://github.com/nodejs/node/issues/3922

For me its more of postinstall not running properly. I deleted node_modules/kerberos folder and installed it again to work properly. Please note that just reinstalling didn't solve the issue. You need to delete the kerberos folder as well.


[Backport v2.2] net: coap: Fix possible overflow

Fix possible integer overflow when parsing a CoAP packet.

@ceolin can you add backport PRs to the Backports GitHub project please?

@carlescufi where is it documented ? I've never done it before.

@carlescufi where is it documented ? I've never done it before.


Update BA Role Randomizer to v2.2.0

Rename the in-game add to random to something more meaningful
"Add to BA Role Randomizer"

Do I need to squash this?

No, as long as it doesn't have merge conflicts or changes you don't want, it doesn't matter what your commit history looks like in a PR, we squash merge all hub PRs anyway


Make UI available as View / Card instead of Dashboard

What is happening?
When adding this custom integration, a new Dashboard is created on the sidebar. However, as "light-related" views might be defined in previously-configured dashboards, for the purpose of having related settings close to each other it would be great to have the option to show the UI of this integration within an existing dashboard.
What should be happening?
Ideally there could be the option to not automatically create a dashboard for the scene presets, while at the same time providing a "companion frontend card", meant to be added as single-card view.
Reflection 1
Subjective Opinion
Is this issue tracker the right place for this topic?
Yes, as it pertains to this integration only. The label "Enhancement" might be apt, as it is not describing a bug.
Please enter the scene_preset version you're using
1.2.3
Please enter the Home Assistant version you're using
2024.2.5
Details about your setup
Doesn't really matter, but exclusively hue lights integrated in HA over the Hue integration.
Reflection 2
No
Time and Effort

[X] Yes, I did my homework.
[X] I understand that my issue will be deleted with no further comment if I did not do my homework.

I don't think that that's possible. Both from a technical standpoint and from a design standpoint.
The UI/UX isn't designed to be both standalone and also part of something else. It's also immensely complicated and full of trade-offs to try to build something in a way that achives that and works on desktop and mobile.
I don't think that you really need the whole thing though. You probably just have a few presets that you always use and for those you can use existing lovelace cards that call the relevant services.
iirc you can also have a button card that navigates somewhere so it could navigate you to the view provided by this component


PointsLayers.js in a browser without webGL

There has been added a new test for compile errors:
if (this.getShaderCompileErrors()) {
  throw new Error(this.getShaderCompileErrors());
}

Won't I am gone get an error if the browser doesn't support webgl? I am asking this because in the new version 6.1.1 PointsLayer.js throw an error on Firefox but not in Chrome.

In browsers without webgl support an error should thrown much sooner than this. This test is simply intended to prevent letting the layer render while the shaders failed to compile.

I got the following error:
Error: Fragment shader compilation failed:
0:2(12): warning: extension GL_ARB_gpu_shader5' unsupported in fragment shader Vertex shader compilation failed: 0:2(12): warning: extension GL_ARB_gpu_shader5' unsupported in vertex shader

I have the same error with the heatmap example:
https://openlayers.org/en/latest/examples/heatmap-earthquakes.html
with Firefox 70.0 (Ubuntu).
But when I reload the page the page 3-4 time the error disappear and the heatmap works as expected

See also https://bugzilla.mozilla.org/show_bug.cgi?id=1399501

It might be the case. Thanks.

This is absolutely not acceptable. I've seen this warning before, it should not be preventing the render IIRC. Thanks for reporting, will try to fix this.


No such file or directory: '/Users/$USER/go/bin/puppy': '/Users/$USER/go/bin/puppy'

https://github.com/roglew/guppy-proxy/blob/3b20c16b0859261ed9c659380ec418e8259f32b6/install.sh#L117
I reckon this should be
 require "$GO" build -o "$GOPATH"/bin/puppy $BUILDFLAGS "puppy/cmd/main";

Hey! Thanks for the info. I'll be getting this fixed this weekend.

Done! This was fixed with https://github.com/roglew/guppy-proxy/commit/eead1e908f0855a1716dfe3618e45c137295dd2b

Thanks 👍

But why not install the binary into the $GOPATH like everything else?


Use shared examples

This is an alternate implementation of the spec examples in #195 using RSpec shared examples. This DRYs up the code a bit and makes it a bit easier to read. Here's some example test output:
StackMaster::SparkleFormation::CompileTime::StringValidator
  #validate
    string validation
      with parameter {}
        is not valid
        has an error
      with parameter a
        is valid

and an error:
  2) StackMaster::SparkleFormation::CompileTime::StringValidator#validate string validation {} has an error
     Failure/Error: expect(invalid_parameter_validator.error).to eql error_message.call(errored_parameters, validator_definition)

       expected: "name:[{}] are not Numbers"
            got: "name:[{}] are not Strings"

       (compared using eql?)
     Shared Example Group: "validate invalid parameter" called from ./spec/stack_master/sparkle_formation/compile_time/string_validator_spec.rb:12
     # ./spec/support/validator_spec.rb:21:in `block (3 levels) in <top (required)>'

(note it points to the right spec file and test line string_validator_spec.rb:12)

Merge it to the other branch if your happy with it


VM and SQL Server Backup

In this question, The "copy-only full backup on the VM",
Does it mean: when doing the Azure VM backup, it does copy-only backup, but when doing the SQL DB backup, it does regular backup(truncate the logs)?

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

ID: a079cf10-0e77-8a07-fdea-615b693d6769
Version Independent ID: 6822bc4e-76f5-f57d-c9af-c4e01ea035cd
Content: FAQ - Backing up SQL Server databases on Azure VMs - Azure Backup
Content Source: articles/backup/faq-backup-sql-server.yml
Service: backup
GitHub Login: @v-amallick
Microsoft Alias: v-amallick

@VigilanteWang Thank you for your post.

@VigilanteWang Copy-only backup doesn't become a base for the next differential backup. So the SQL side backups will run in sequence. You can refer to this link - https://charbelnemnom.com/running-sql-server-in-azure-vm-what-backup-solution-should-i-use-azurebackup/ makes it clear.
Feel free to reply if you have questions!

@SadiqhAhmed-MSFT Thank you for you reply. So the Iaas VM backup doesn't truncate the logs, but SQL DB backup does, right?

@VigilanteWang : The Azure Backup for SQL is a solution that includes log backups. So, didn't understand the query about truncating logs.

@VigilanteWang Have you had a chance to see previous response from pvrk?
Please clarify your ask.

@pvrk Thank you. Usually for sql server db backup, after a backup of log, by default it will truncate the log. In this question, it says it will only do a copy-only backup so not to truncate the log.
So, Does it mean when doing sql backup, it still truncates the log?

@VigilanteWang : Thanks for the clarity. There is a slight nuance on how do we interpret the word 'truncate'. For us, 'truncate' means there was an unexpected action leading to the log segment losing data and becoming non-recoverable. It has a negative connotation. When log backups are taken, the log segments are cleared so that upcoming logs are filled. So, yes, in that sense, SQL backup solution takes the log backup and clears log area.
Also, when log backups are taken, they need to be 'parented' to a full so that the right recovery chain is established (Full + logs on that full for point-in-time recovery). Any solution which takes care of log backups should also manage these fulls. On the other hand, a copy-only-full can exist independently and can be taken by any backup solution. Hence, when Azure VM backup is taken, we need the backup to be 'copy-only-full' (via setting the registry key) so that the recovery chain management by the log backup solution is intact.
Hope this clears all queries.

@VigilanteWang Hope the previous post clarified your question. Feel free to ping with questions if any. If not, we can close this thread.

@VigilanteWang We haven't heard back from you, so we will now close this issue. If this remains an issue, please reply and we will gladly continue the discussion.


Bump fullybrowser to 3.0.6

RE-CHECK!

3.0.6 created 11.11.2023

Please fix io-package.json
see issue reported by adapter checker and https://github.com/arteck/ioBroker.fullybrowser/pull/175

RE-CHECK!

3.0.6 created 11.11.2023
380 user
OK


some question about 𝐗_𝑡−𝜌𝐗_(𝑡−1) in the code

Hello!
as the paper said，the input and output should be：

but the code in forecasting_runner:
  if args.inp_adj:              x = torch.cat([avg[None].repeat(bs, 1, 1), x], dim=1)              x = x[:, 1:] - rho * x[:, :-1]     prd_y = self.model(x)     if args.out_adj:             prd_y += rho * x[:, -1]
the x[:, -1] under has changed which mean that x[:, -1]=x[:, 1:] - rho * x[:, :-1] instead of x_{t-1}.
Do I misunderstand?

Hi,
Yes, you are right.
Originally, this part is written in one line; but when I wanted to run the ablation study, I separated the input and output parts and thus caused the bug.
So, fortunately, the main experiments are run without the error, only the ablation study is affected by this bug.
Thanks for pointing the error out!
I will fix it.


JavaScript Code Style lacks examples

There're many options for JavaScript code style. But provided code sample is too short to show all the options.

Hello. I added bigger example. Without classes - i think need split this config to EcmaScript options (idk for now)


navigate() persists the scroll position of the previous page as opposed to bringing to the top like

I have a sign up form with a sign up button at the bottom of that page that navigates a user to a different page upon submittion. The scroll position persists when navigate() happens, where as I was hoping it would reset at the top of the page like <Link/> does.
https://codesandbox.io/s/o4v0pzwp0z

I think that this is not an issue with the router, it has to do with the way SPAs work, maybe you can use something like window.scrollTo(x, y).

I experience the same problem with Links. The page jumps to the container associated with the route. This really should not be the default behavior.
Example: https://codesandbox.io/s/y0jmjj2o8j

Same issue.
It only happens if you are using nested <Router>, the page gets scrolled to the <Router> element on the page (or it's children like simoroshka supposed)

For all who are the same stupid as I am - there is a documented prop for router called primary that controls this behavior
https://stackoverflow.com/questions/53058110/stop-reach-router-scrolling-down-the-page-after-navigating-to-new-page
The issue may be closed

We would never consider you or others "stupid" but your research and help in pointing out the primary prop is much appreciated 🏅


System vm's volumes should be expunged when a primary storage is set in Maintenance Mode

ISSUE TYPE
Enhancement/Improvement Request
COMPONENT NAME
Component:
CLOUDSTACK VERSION
Cloudstack version 4.18,
SUMMARY
System vm's volumes should be expunged when a primary storage is set in Maintenance Mode
Currently, the system vm volumes are set in destroyed state  and have to wait till the storage cleanup thread  runs which is 24hrs by default
Unless the systemvm's volumes are removed the primary storage can't be removed
Steps to reproduce the behavior
Example

Create a cloudstack enviroment with 2 Primary storages (cluster wide and zone wide)

Launch a vm with root disk and data disk ( Both disks are allocated in the cluster wide primary storage)

Put the cluster wide storage in Maintainence Mode

On putting the Cluster wide storage in Maintainence Mode.

The vm goes into stopped state

The system vm volumes  are recreated in the Zone wide storage

The system vm volumes associated with the cluster wide storage are marked in the destroyed state

Screenshots

Admin user who wants to remove the Cluster wide storage cannot do so unless the system vm volumes are expunged and marked as removed and it depends on the global settings paramters

storage.cleanup.interval
storage.cleanup.delay
storage.cleanup.enabled

This doesn't affect the vm disk as they are recreated in another active primary storage

Expected behaviour
Cloudstack should expunge the systemvm volumes instead of marking them destroyed.
As systemvm volumes genrally doesn't contain important  data.
Or we could have pop up  option asking the user if they want to expunge the systemvm volumes immediately when they put a primary storage in Maintenance mode ( some sort of configurable value)

@kiranchavala can I interpret this as a bug actually? volumes on a storage in maintenance are marked as destroyed. I would expect them to be either migrated or expunged indeed. This might even be an operator decision.
Enhancement or bug, I think it can go into 4.18.2, can it (cc @rajujith ) ? or is it too much of a paradigm shift for a minor version?

@DaanHoogland @kiranchavala  This can be considered an improvement. On enabling maintenance on the primary storage allow optional expunge of systemVM volumes?. I am assuming it is not common to delete the primary storage in maintenance before the storage cleanup thread has run subsequently which is by default in 24 hours.

So what is the functionality we want here @kiranchavala @rajujith ?
I would not want an automatic expunge of all volumes on going into maintenance as the reason for the maintenance might not be removing the store from the system.

@kiranchavala can I interpret this as a bug actually? volumes on a storage in maintenance are marked as destroyed. I would expect them to be either migrated or expunged indeed. This might even be an operator decision.
Enhancement or bug, I think it can go into 4.18.2, can it (cc @rajujith ) ? or is it too much of a paradigm shift for a minor version?

I think that this could go into 4.18.2, it seems like a bug to me. I cannot see a case where keeping system VMs' volumes on destroyed state would be beneficial in this situation.

@DaanHoogland
I would also prefer the automatic expunge of only the system VM volumes when primary storage is kept in maintenance mode.

fixed by #9197


Remove all non-mainline U-Boots

Motivation for this change
Keeping untested, and untestable packages around is not great.
As maintainer of U-Boot-related things, I want to remove the last non-mainline U-Boot from Nixpkgs.
All mainline-based U-Boots are basically free, assuming that mainline keeps them in working order.
From this point forward, it would be ideal to not add non-mainline U-Boot to Nixpkgs. Let's see if we can do it.
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

cc @viric who introduced and maintained the package.

Given it's been almost two full weeks, I don't think there is any objection.


TIMX-18-marc-transform-yet-more-fields

How can a reviewer manually see the effects of these changes?
Run the transform locally using the alma-2022-10-11-full-extracted-records-to-index.xml file in the dev S3 bucket, e.g.:
pipenv run transform -i <S3 URL for the above file> -o alma-transformed-records.json -s alma

What are the relevant tickets?

https://mitlibraries.atlassian.net/browse/TIMX-18

Developer

[x] All new ENV is documented in README
[x] Stakeholder approval has been confirmed (or is not needed)

Code Reviewer

[ ] The commit message is clear and follows our guidelines
(not just this pull request message)
[ ] There are appropriate tests covering any new functionality
[ ] The documentation has been updated or is unnecessary
[ ] The changes have been verified
[ ] New dependencies are appropriate or there were no changes

Includes new or updated dependencies?
NO

Pushed new commit


separate file for toy processes, compartments

There are several Toy processes and compartments in the codebase for testing purposes. Some of these are in composition.py, some in the processes directory (exchange_a.py), some for tests within other files (ToyAgent in meta_division process file). Maybe these can all be pulled into a separate file so that they can be more easily accessed and reused?

done in #49

done in #49


Stash proxies

I don't know why it does not apply the tonel v1 format and try to go to v3

To much file changes, do not merge

The modified classes are:

PyramidTreePlugin
PyramidExternalRessourceProxy
PyramidExternalRessourceSource
PyramidSerializerLoader


add support for logging with limit for messages per minutes

this can assist in preventing log spamming with many similar messages.

This is not responsibility of our library or even logger facade. I think messages throttling is responsibility of concrete appender. But this is logging, so you should log every message, because you don't want lost important stacktraces and errors.

I tend to agree. on the other hand it seems like a valuable feature. I will close it now and reconsider in case it will pop-up again.


Non-FOSS in F-Droid build

ref: https://github.com/BlazeCodeDev/TSViewer/blob/V1.4/app/build.gradle#L67
ref: https://github.com/BlazeCodeDev/TSViewer/blob/V1.4/app/build.gradle#L104
ref: https://gitlab.com/fdroid/fdroiddata/-/jobs/3386086237#L290
/LE: fyi https://gitlab.com/fdroid/fdroiddata/-/blob/master/metadata/com.blazecode.tsviewer.yml

Thanks for the heads up! That's got to do with the new added wear os support. Unfortunately there is no other way of communicating between watch and phone.

Yup, maybe add a libre flavor that does not need that?

I'll think about how to fix that, thanks!

Introduced new foss flavor with release V2.0


HTTP Status Code Chart with Time information

Hi, is it possible to enhance the HTTP STATUS CODE chart by adding the time,
Looks like combination of HTTP STATUS CODE Chart and TIME DISTRIBUTION Chart,
To inform that 502 status code happen in what time, to identify the behavior of application.
and inform also the success rate, between status code 200 and non 200,
Thanks

I think #117 will address this in the sense that you will be able to filter by time and therefore displaying only the status codes for that particular time range.

You mean this features already available?

It's not available yet. I'll close this as it's a duplicate of #117.


Unable to install Pennylane-Qulacs GPU: follow-up

This is related to my previous post on this topic : https://github.com/PennyLaneAI/pennylane-qulacs/issues/62#issue-2197685954
I forgot to mention before that I had succeeded in installing Qulacs-GPU on its own, so I am wondering, when I am installing pennylane-qulacs-gpu, is there a way to get the installation process to recognize the existing installation of Qulacs-GPU so that it doen't try to install it over again?

Hey @JustinS6626, are you installing pennylane-qulacs into the same Python environment as the run that already had Qulacs GPU installed?

Hey @JustinS6626, are you installing pennylane-qulacs into the same Python environment as the run that already had Qulacs GPU installed?

Thanks for getting back to me again! Yes, that's what I did. Should I do something else instead?

Just posting this for the paper trail: https://discuss.pennylane.ai/t/unable-to-install-pennylane-qulacs-gpu-verson/4319/2

It looks like it could be an issue in the installation script. Is there anything you can do about that?

Indeed, I tried installing this on Collab and got this:
!pip install pennylane qulacs pennylane-qulacs["gpu"]

Building wheels for collected packages: qulacs-gpu
  error: subprocess-exited-with-error

  × python setup.py bdist_wheel did not run successfully.
  │ exit code: 1
  ╰─> See above for output.

  note: This error originates from a subprocess, and is likely not a problem with pip.
  Building wheel for qulacs-gpu (setup.py) ... error
  ERROR: Failed building wheel for qulacs-gpu
  Running setup.py clean for qulacs-gpu
Failed to build qulacs-gpu
ERROR: Could not build wheels for qulacs-gpu, which is required to install pyproject.toml-based projects

However, as the traceback suggests, this doesn't seem to be a pennylane-qulacs plugin issue; there's an issue with qulacs-gpu. I see this issue here: https://github.com/qulacs/qulacs/issues/623. I think it's best to follow that (we will, as well). If there's a fix, we'll make sure to upgrade the dependency, make sure everything works with the plugin, etc.

Thanks again for getting back to me! Using the workaround mentioned on the qulacs github, I managed to install qulacs-gpu on its own from source, but now when I try to install pennylane-qulacs-gpu, pip doesn't recognize the existing qulacs-gpu installation and tries to install qulacs-gpu again. When I run the pip install command, is there an argument that I can use to stop it from trying to install qulacs-gpu again as well?

Hey @JustinS6626, I recommend cloning the pennylane-qulacs repo and modifying the requirements to something like this (see here for more details about installing from github: https://stackoverflow.com/questions/16584552/how-to-state-in-requirements-txt-a-direct-github-source):
pennylane>=0.32
Qulacs @ git+https://github.com/qulacs/qulacs@<branch name with the fix you mentioned>
numpy~=1.16

Then you can pip install your local clone like this (make sure you're in the root directory of your pennylane-qulacs clone, and have a dedicated virtual environment!):
pip install -e .

Let me know if this works :)

The workaround was actually not a fix to one of the branches itself, but rather a manual installation command mentioned in the related issue https://github.com/qulacs/qulacs/issues/623. The solution given is to run USE_GPU=Yes pip install --no-build-isolation ., which works for me since I have sudo access. Based on that, is there a way to tell pip to skip the qulacs-gpu installation, or to tell it where the existing installation is on my machine so that it doesn't try to install qulacs-gpu again?

On a related note, I was wondering, is qulacs the fastest simulator supported by Pennylane for use with machine learning, or would I be better off using pennylane-lightning?

Based on that, is there a way to tell pip to skip the qulacs-gpu installation, or to tell it where the existing installation is on my machine so that it doesn't try to install qulacs-gpu again?

When you pip install pennylane-qulacs, you can use the --no-dependencies flag to ignore the dependencies (see here: https://stackoverflow.com/questions/12759761/pip-force-install-ignoring-dependencies). Does that work for you?

On a related note, I was wondering, is qulacs the fastest simulator supported by Pennylane for use with machine learning, or would I be better off using pennylane-lightning?

Between the qulacs plugin and lightning, we definitely put more points into supporting lightning ⚡. I would expect it to be faster, but let us know otherwise! You can also try out Catalyst (our quantum-flavoured JIT compiler): https://docs.pennylane.ai/projects/catalyst/en/stable/index.html

Thank you very much for getting back to me!
I tried running

and got
Requirement already satisfied: pennylane-qulacs[gpu] in /usr/local/lib/python3.11/dist-packages (0.33.0.dev0)

However, when I tried
import pennylane as qml
dev = qml.device('qulacs.gpu', wires=2)

I got
Traceback (most recent call last):
  File "/usr/lib/python3.11/idlelib/run.py", line 578, in runcode
    exec(code, self.locals)
  File "<pyshell#1>", line 1, in <module>
  File "/usr/local/lib/python3.11/dist-packages/pennylane/__init__.py", line 398, in device
    raise DeviceError(f"Device {name} does not exist. Make sure the required plugin is installed.")
pennylane._device.DeviceError: Device qulacs.gpu does not exist. Make sure the required plugin is installed.

What else do I need to do to make sure the plugin is recognized?
I will look into Catalyst as well. Does it provide noticeable improvements in speed?


front path in sandbox example

Sorry: commit message should be: "wrong path in sandbox example" ;)


HIVE-23725: ValidTxnManager snapshot outdating causing partial reads

HIVE-23725: ValidTxnManager snapshot outdating causing partial reads in merge insert

@jcamachor could you take a look at this PR, it should solve the partial read problem we were talking about


gittyup frequently asks for https access data

GittyUp 1.3.0 on current Windows 10 Pro
My repository is local with a remote http (not https) origin. I am frequently asked for https access data. The dialog box does not mention the URL the http access data are for. I need to click the cancel button several times to make it disappear. Though, the dialog box reappears after some minutes.
Dialog box should show the URL.
Dialog box should not reappear after the cancel button was clicked.

related to #524 and #529?

Yes, this is a duplicate of #524, but I'm not sure how this relates to #529?


[AutoPR compute/resource-manager] Add hyperVGeneration enum property to ImageProperties

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/5740

(message created by the CI based on PR content)

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/4911


feat: Starboard

Allow users to "star" a message, messages with X amount of stars can then appear in a starboard
How

User stars a message, once X stars have been reached
If no starboard thread has been created, create new starboard thread and pin it
Add message to the starboard.

We have this feature available through Dyno (Webster), is it worth it to duplicate this feature?

Is it on a per channel basis?


Is pure needed?

Question / comment
Here's the space saving achieved by turning on pure bit in babel macro config for styled components:
  144.14 KB         build/static/js/2.0127f623.chunk.js
  51.69 KB (-18 B)  build/static/js/main.1da2e05f.chunk.js
  771 B             build/static/js/runtime-main.70182e92.js

Whole 18 bytes saved!
I wonder... does it mean that I'm using almost every feature of styled-components?
Or is something else wrong in my setup / build / config?
Or is this setting not very useful?

Diffing the beautified output showed me the culprit - I had 1 unused component...
(eslint thought it was used because .propTypes was set)
Maybe pure is primarily useful if same codebase can be built into different targets? Like a multi-paged app or translated app where each language is its own build bundle?

Yeah it's more for component libraries. Where only some parts are used


Fixed 404 routing issue

:+1: I was sketched out by adding 404 to the router but when I walked through your section I think it's an elegant solution to ensure the that req Object end's up being defined the same way.
Would it be possible to squash your commits and then I'll merge? This helps with reverting back if need be. EG. There are multiple commits with the comment Fixed duplicate property not functioning issue.


Loading in Elasticsearch 1.4.4

I have elasticsearch 1.4.4 installed on my system and it does not seem to load reindexing-1.4.1 plugin. Can you tell me how I get my Elasticsearch setup to recognize the plugin ?

Please check Elasticsearch's log file and plugins directory.

It seems there is no 1.4.4.zip anymore
/usr/share/elasticsearch/bin/plugin install org.codelibs/elasticsearch-reindexing/1.4.4 --verbose
-> Installing org.codelibs/elasticsearch-reindexing/1.4.4...
Trying http://download.elasticsearch.org/org.codelibs/elasticsearch-reindexing/elasticsearch-reindexing-1.4.4.zip...
Failed: IOException[Can't get http://download.elasticsearch.org/org.codelibs/elasticsearch-reindexing/elasticsearch-reindexing-1.4.4.zip to /usr/share/elasticsearch/plugins/reindexing.zip]; nested: FileNotFoundException[http://download.elasticsearch.org/org.codelibs/elasticsearch-reindexing/elasticsearch-reindexing-1.4.4.zip]; nested: FileNotFoundException[http://download.elasticsearch.org/org.codelibs/elasticsearch-reindexing/elasticsearch-reindexing-1.4.4.zip];
Trying http://search.maven.org/remotecontent?filepath=org/codelibs/elasticsearch-reindexing/1.4.4/elasticsearch-reindexing-1.4.4.zip...
Failed: IOException[Can't get http://search.maven.org/remotecontent?filepath=org/codelibs/elasticsearch-reindexing/1.4.4/elasticsearch-reindexing-1.4.4.zip to /usr/share/elasticsearch/plugins/reindexing.zip]; nested: FileNotFoundException[https://repo1.maven.org/maven2/org/codelibs/elasticsearch-reindexing/1.4.4/elasticsearch-reindexing-1.4.4.zip]; nested: FileNotFoundException[https://repo1.maven.org/maven2/org/codelibs/elasticsearch-reindexing/1.4.4/elasticsearch-reindexing-1.4.4.zip];
Trying https://oss.sonatype.org/service/local/repositories/releases/content/org/codelibs/elasticsearch-reindexing/1.4.4/elasticsearch-reindexing-1.4.4.zip...
Failed: IOException[Can't get https://oss.sonatype.org/service/local/repositories/releases/content/org/codelibs/elasticsearch-reindexing/1.4.4/elasticsearch-reindexing-1.4.4.zip to /usr/share/elasticsearch/plugins/reindexing.zip]; nested: FileNotFoundException[https://oss.sonatype.org/service/local/repositories/releases/content/org/codelibs/elasticsearch-reindexing/1.4.4/elasticsearch-reindexing-1.4.4.zip]; nested: FileNotFoundException[https://oss.sonatype.org/service/local/repositories/releases/content/org/codelibs/elasticsearch-reindexing/1.4.4/elasticsearch-reindexing-1.4.4.zip];
Trying https://github.com/org.codelibs/elasticsearch-reindexing/archive/1.4.4.zip...
Failed: IOException[Can't get https://github.com/org.codelibs/elasticsearch-reindexing/archive/1.4.4.zip to /usr/share/elasticsearch/plugins/reindexing.zip]; nested: FileNotFoundException[https://github.com/org.codelibs/elasticsearch-reindexing/archive/1.4.4.zip]; nested: FileNotFoundException[https://github.com/org.codelibs/elasticsearch-reindexing/archive/1.4.4.zip];
Trying https://github.com/org.codelibs/elasticsearch-reindexing/archive/master.zip...
Failed: IOException[Can't get https://github.com/org.codelibs/elasticsearch-reindexing/archive/master.zip to /usr/share/elasticsearch/plugins/reindexing.zip]; nested: FileNotFoundException[https://github.com/org.codelibs/elasticsearch-reindexing/archive/master.zip]; nested: FileNotFoundException[https://github.com/org.codelibs/elasticsearch-reindexing/archive/master.zip];
Failed to install org.codelibs/elasticsearch-reindexing/1.4.4, reason: failed to download out of all possible locations..., use --verbose to get detailed information

It installs but maybe it doesn't work. However I'm very new to elasticsearch and I could misunderstand what I see.
I changed a field in a logstash template from analyzed to not_analyzed and I must reindex.
Restarted logstash which pushed the new template to elasticsearch (I verified it), installed the elasticsearch plugin, restarted elasticsearch.
index=my_index
curl -XPOST localhost:9200/${index}/_reindex/${index}_new/?wait_for_completion=true
curl -s -XGET http://localhost:9200/_cat/indices?v|grep -e my_index -e docs.count
health status index                pri rep docs.count docs.deleted store.size pri.store.size
green  open   my_index             5   0          1            0     10.5kb         10.5kb
green  open   my_index_new         5   0          0            0       575b           575b

There are no docs in the new index.

Reindexing plugin 1.4.2 support elasticserach 1.4.4.
Plugin version is different from elasticsearch version.

One final word: it works.
Eventually the documents appear in the new index. After about one minute I get
curl -s -XGET http://localhost:9200/_cat/indices?v|grep -e my_index -e docs.count
health status index                pri rep docs.count docs.deleted store.size pri.store.size
green  open   my_index             5   0          1            0     10.5kb         10.5kb
green  open   my_index_new         5   0          1            0     10.5kb         10.5kb

It seems that ?wait_for_completion=true has no effect. I tried without variables and with '' around the URL to escape the ?
$ curl -XPOST 'localhost:9200/my_index/_reindex/my_index_new/?wait_for_completion=true'
{"acknowledged":true}

and no documents in the new index for a while. Maybe this is because it's elasticsearch 1.4.4.
Anyway, the plugin is mostly OK and I can work around this. Thanks.


update packages

:white_check_mark: Build TheIdServer 2.2.1-fix-dependencies1-0057 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/9203637aa7 by @)


Add AWS DynamoDB API types and controllers

What problem are you facing?
Would like a alpha support for DynamoDB
How could Crossplane help solve your problem?
Add CRD for API types and controller that follows best practices in https://github.com/crossplaneio/crossplane/blob/7420e6/design/one-pager-managed-resource-api-design.md.

@negz looks like this was wrapped up in https://github.com/crossplane/provider-aws/issues/161, so closing this out.


improve subscription reliability

When replying asynchronously from a hello server, the server context disappears (due to network failure).
For subscriptions to work reliable this mechanism has to become more robust.
currently on the server side this error message is observed when trying to push a message to a client where the server context was removed by hello:
Mar 09 17:53:02 vlx129-tpb pcs[186]: ** (MatchError) no match of right hand side value: :invalid_identity
Mar 09 17:53:02 vlx129-tpb pcs[186]: 17:53:02.749 [error] GenServer #PID<0.1693.0> terminating
Mar 09 17:53:02 vlx129-tpb pcs[186]: Supervisor hello_listener_supervisor had child {hello_zmq_listener,{ex_uri,"zmq-tcp",
                                                                 {ex_uri_authority,undefined,"<IP_ADDRESS>",27001},
                                                                 [],undefined,undefined}} started with hello_zmq_listener:start_link({ex_uri,"zmq-tcp",{ex_uri_authority,undefined,"<IP_ADDRESS>",27001},[],undefined,undefined}) at <0.1693.0> exit with reason no match
Mar 09 17:53:02 vlx129-tpb pcs[186]: CRASH REPORT Process <0.1693.0> with 0 neighbours exited with reason: no match of right hand value invalid_identity in hello_zmq_listener:handle_info/2 line 99 in gen_server:terminate/7 line 804
Mar 09 17:53:02 vlx129-tpb pcs[186]: gen_server <0.1693.0> terminated with reason: no match of right hand value invalid_identity in hello_zmq_listener:handle_info/2 line 99

in case of network failure it would be ideal if hello could cash the messages to be send and only discard the context after the connection is long dead (to be determined by heartbeats?).
the client must also identify the dead connection after a similar timeout, then crash the hello client (which is to be restarted by a supervisor).

Here is a fix for this crash: https://github.com/travelping/hello/commit/bb7943cd4f14e4254fb8200adb5d4e063424c096. Please update hello.
I will look more into reconnecting client after context disappeared.

but that is just changing crash->errorlog, while not touching the reason

@thz yes, I just noticed that here isn't the last hello.

hhm. was such a robust behavior not one of the reasons to have something like hello. The underlaying tools like zeroMQ or Erlang distribution or lately http2 give you already the building blocks. I.e. ZeroMQ would reconnect sockets after TCP failure and Erlang Node Communication kann also be configured with more aggressive connectivity checks. And as far i know someone has implemented hello echos above the transport for exactly this reasons.

Hello doesn't have any subscription mechanism. Here is just a notify method which allows to send message from server to client. In this case subscription mechanism is a part of application layer.
As improvements for implementing good pubsub over hello with reused socket I may suggest add feedback for notify method. If happened something wrong you will know about that and be able to remove subscription in your application.


Fixing view highlighting on Android P

Fixes https://github.com/facebook/stetho/issues/648
clipOutRect wasn't the proper API to use in this case, so changed to use save and restore.
Based on this SO answer: https://stackoverflow.com/questions/50231950/what-is-the-best-alternative-to-canvas-cliprect-with-region-op-replace/50247323#50247323

@jasta is this library still being maintained? Would appreciate this PR getting merged so we can stop using a locally-built stetho version.

Can this be merged please?


Adding some basic documents to help improve compliance with FAIR

I have added a code of conduct and a template for the Citation.
I left the citation for you to fill out with your details as you are the software owner. If you have any question don't hesitate to contact me.
Relevant motivation and context.:
Part of my task I was appointed in my masters.

Hi, thank you for your interest in contributing to neural-lam!
It would be great if you could update the PR with the provided PR template, as that allows us to easier understand and track the change.
Regarding the changes themselves:

I think the formulation of a code of conduct is something that should be discussed with the community, and not directly added. It would be a good idea to join our slack channel and start a discussion about this there, to make sure anyone interested could have some input on the formulations in it.
For citation, I would personally prefer if the associated scientific publications were cited (as described in the readme) instead of the software itself. But would be open to adding a citation file if others think it's a good idea.

Hi, I appreciate your feedback. How can I get the PR template again? Or do I need to create a new PR to automatically generate the template.

You can copy it from here: https://github.com/mllam/neural-lam/blob/main/.github/pull_request_template.md?plain=1

I think I will close this for now, and then you can start a discussion with the community about what should be in the code of conduct and re-open this or a new PR with a first proposal based on that.


Refactor chaincode install

Remove dependency on:

github.com/hyperledger/fabric
io/ioutil
github.com/pkg/errors
Also removed use of github.com/gogo/protobuf.

Query installed chaincode implementation and unit tests.
Moved public API code into "pkg" package to separate from test and internal code, and to make running unit tests easier.
Contributes to #49
Contributes to #25

I am going to merge this PR. @channingduan , FYI.

@bestbeforetoday I merged this PR. please open another pr if needed.
usually I hope a pr with status in open is ready for review, for any WIP status, please make the PR status as draft.


After pushing to talk and hitting enter, i get the error: Exception iterating requests!

I get this with anything I say.
C:\Users\Felix>googlesamples-assistant-pushtotalk
INFO:root:Connecting to embeddedassistant.googleapis.com
INFO:root:Using device model rock-micron-212522-pi-hscshi and device id 3439f614-99d5-11e8-89c9-5800e3e95be6
Press Enter to send a new request...
INFO:root:Recording audio request.
INFO:root:Transcript of user request: "hey Google".
INFO:root:Transcript of user request: "hey Google".
INFO:root:End of audio request detected.
INFO:root:Stopping recording.
ERROR:grpc._channel:Exception iterating requests!
Traceback (most recent call last):
File "c:\users\felix\appdata\local\programs\python\python37-32\lib\site-packages\googlesamples\assistant\grpc\audio_helpers.py", line 338, in iter
raise StopIteration
StopIteration
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "c:\users\felix\appdata\local\programs\python\python37-32\lib\site-packages\grpc_channel.py", line 180, in consume_request_iterator
request = next(request_iterator)
File "c:\users\felix\appdata\local\programs\python\python37-32\lib\site-packages\googlesamples\assistant\grpc\pushtotalk.py", line 131, in iter_log_assist_requests
for c in self.gen_assist_requests():
File "c:\users\felix\appdata\local\programs\python\python37-32\lib\site-packages\googlesamples\assistant\grpc\pushtotalk.py", line 217, in gen_assist_requests
for data in self.conversation_stream:
RuntimeError: generator raised StopIteration
Traceback (most recent call last):
File "c:\users\felix\appdata\local\programs\python\python37-32\lib\runpy.py", line 193, in run_module_as_main
"main", mod_spec)
File "c:\users\felix\appdata\local\programs\python\python37-32\lib\runpy.py", line 85, in run_code
exec(code, run_globals)
File "C:\Users\Felix\AppData\Local\Programs\Python\Python37-32\Scripts\googlesamples-assistant-pushtotalk.exe_main.py", line 9, in
File "c:\users\felix\appdata\local\programs\python\python37-32\lib\site-packages\click\core.py", line 722, in call
return self.main(*args, **kwargs)
File "c:\users\felix\appdata\local\programs\python\python37-32\lib\site-packages\click\core.py", line 697, in main
rv = self.invoke(ctx)
File "c:\users\felix\appdata\local\programs\python\python37-32\lib\site-packages\click\core.py", line 895, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "c:\users\felix\appdata\local\programs\python\python37-32\lib\site-packages\click\core.py", line 535, in invoke
return callback(*args, **kwargs)
File "c:\users\felix\appdata\local\programs\python\python37-32\lib\site-packages\googlesamples\assistant\grpc\pushtotalk.py", line 458, in main
continue_conversation = assistant.assist()
File "c:\users\felix\appdata\local\programs\python\python37-32\lib\site-packages\tenacity_init.py", line 241, in wrapped_f
return self.call(f, *args, **kw)
File "c:\users\felix\appdata\local\programs\python\python37-32\lib\site-packages\tenacity_init_.py", line 330, in call
start_time=start_time)
File "c:\users\felix\appdata\local\programs\python\python37-32\lib\site-packages\tenacity_init_.py", line 279, in iter
return fut.result()
File "c:\users\felix\appdata\local\programs\python\python37-32\lib\concurrent\futures_base.py", line 425, in result
return self.__get_result()
File "c:\users\felix\appdata\local\programs\python\python37-32\lib\concurrent\futures_base.py", line 384, in __get_result
raise self.exception
File "c:\users\felix\appdata\local\programs\python\python37-32\lib\site-packages\tenacity_init.py", line 333, in call
result = fn(*args, **kwargs)
File "c:\users\felix\appdata\local\programs\python\python37-32\lib\site-packages\googlesamples\assistant\grpc\pushtotalk.py", line 139, in assist
self.deadline):
File "c:\users\felix\appdata\local\programs\python\python37-32\lib\site-packages\grpc_channel.py", line 345, in next
return self._next()
File "c:\users\felix\appdata\local\programs\python\python37-32\lib\site-packages\grpc_channel.py", line 328, in _next
raise self
grpc._channel._Rendezvous: <_Rendezvous of RPC that terminated with:
status = StatusCode.UNKNOWN
details = "Exception iterating requests!"
debug_error_string = "None"

This looks like an ongoing issue with Windows, as per #246.

I have the exact same problem, have found zero fixes.

same problem here , no solution found ?


PO report template doesn't work

Please verify that this bug has NOT been raised before.

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

Describe the bug*
Hello,
I'm running docker on Windows 10
After adding all reports BO, BOM, PO, SO
Everything works fine except of PO report
I get an error when using PO report template (inventree_po_report.html):
{"error":"TemplateSyntaxError","error_class":"<class 'django.template.exceptions.TemplateSyntaxError'>","detail":"Error details can be found in the admin panel","path":"/api/report/po/6/print/","status_code":500}
Steps to Reproduce
Just add inventree_po_report.html as PO report template in admin panel
Expected behavior
Should print a report
Deployment Method

[X] Docker
[ ] Bare metal

Version Information
Version Information:
InvenTree-Version: 0.8.2
Django Version: 3.2.15
Commit Hash: 62f44d0
Commit Date: 2022-08-25
Database: postgresql
Debug-Mode: False
Deployed using Docker: True
Relevant log output
No response

Fixed in #3677
still not in stable :(
current stable 0.82

@AlexeyHaritonov 0.8.3 should be out pretty soon


How to use fasttext (subwords) vectors in tensorflow embedding layer?

Hey,
I just struggle to find out how can I use Fasttext wordvectors for OOV word (in general) in a keras/tensorflow embedding layer. There is nothing out there. Maybe someone has thought of that too and has some hints for me?
The way via word embedding look up works via indices like
tf.nn.embedding_lookup(word_embeddings, x1)
And you could have an index for one OOV. But how can I assign a specific vector (from a different and custom source like fasttext) at runtime?
I am not so experience with the inner working of tensorflow embedding_lookup.
Up to know I handle OOV words by splitting the OOV in known subwords! So I make more words out of a OOV.

I have 0 experience with fasttest, maybe others can help.

@bwanglzu It has nothing to do with Fasttext! It is about manipulating/customisising word vectors by conditions! If you encounter an OOV word during prediction, how can you assign a specific vector to this this specific word (ie. you check the word for knwon subwords by your own method or using just fasttext...)

@datistiquo take a look at Vocabulary class here.
btw, we're volunteers to maintain the open source project, you're not my customer.  Please ask your questioon in a modest way.

I hope things are working well for you now. I’ll go ahead and close this issue, but I’m happy to continue further discussion whenever needed.


Log MockRandomMergePolicy reverse in verbose.

Description
#12622 introduced surprising reversing merge in tests. Let's help to notice it in verbose test mode.

I think it doesn't need to be mentioned in CHANGES


First test/coverage run is quite slow in 15.x

26 suites and 291 tests total took almost a minute to run in coverage mode, compared to about 10 seconds for 14.x.
Using basically all defaults.

This is gonna be really hard to troubleshoot without a repro :( . Coverage was completely rewritten and simply does more work now. Do you have a custom preprocessor or are you using babel-jest? Are you using collectCoverageFrom? Is there a performance difference when not using coverage in Jest 15 vs 14?
Is this the first test run or the second? The first one will have to compile every single file and the second would use cached transformed and instrumented files.

Not using anything special other than:
"coverageReporters": [
      "text",
      "cobertura",
      "lcov"
]

Can confirm that subsequent runs are a lot faster... not great for CI though :/

This probably means that the previous coverage feature was a huge mess and didn't work correctly.

This probably means that the previous coverage feature was a huge mess and didn't work correctly.

😂
Well I'm glad it's at least only a first-run issue. Feel free to close if you don't want to keep the issue open for tracking.

I'm sorry for the slowdown. Coverage is inherently slow. Can you provide some sort of repro for us that shows this problem, maybe even with the Jest repo itself?
cc @dmitriiabramov in case he added some sleep calls.

Coverage is inherently slow.

Truth! I'll see what I can do... the project I'm testing with is super proprietary.

it might be generating coverage for unstested files that is taking so long. It has to run through all files in the project (probably including node_modules) and match them against a regex to understand if report is needed for the file or not

but if subsequent runs are much faster then it's probably preprocessing + writing cache :)

Istanbul released a much faster implementation of their coverage collector which should hopefully help with this. Otherwise there isn't anyone working on this so closing the issue.


[NEMO-399] Include the official WordCount example from the Beam website

JIRA: NEMO-399:  Include the official WordCount example from the Beam website
Major changes:

Adds the WordCount example from the Beam website
Fixes the README accordingly

Minor changes to note:

None

Tests for the changes:

None

Other comments:

None

Closes #225

@DifferentSC can you briefly take a look at this PR before we release 0.2? I think it would be a good direction for Beam users to use Nemo with an example that they are already familiar with. It simply adds some lines in the README with the example. You can test with the commands specified in the README.

@sanha Also this requires <2min effort to review. It could be also nice to include in the upcoming release.


ERR: no one is publishing to path (regression for v0.15.1 - v0.15.3)

Which version are you using?
v0.15.1 - v0.15.3
Which operating system are you using?

[x] Linux
[ ] Windows
[ ] macOS

Architecture

[x] amd64
[ ] arm64
[ ] arm7
[ ] arm6

Describe the issue
In RTSP proxy mode, some camera streams stopped working for no obvious reason. Server configuration stayed exactly the same, I had to roll back the version to v0.15.0 to restore functionality. The only error is ERR: no one is publishing to path 'abc123'
This is different than https://github.com/aler9/rtsp-simple-server/issues/250
Unfortunately I cannot enable debug output because the system cannot deal with the huge log thoroughput. And if I enabled debug output locally it wouldn't help, because locally the same problematic streams work fine. So this is not reproducible as it happens only in production with many streams and clients involved.
Here are the production logs. It seems as if the first client might be able to read (A.B.C.D), but the second and subsequent ones cannot (W.X.Y.Z).
2021-04-03T07:37:50.910773665Z [I] [4/0/0] [path abc123] [rtsp source] started
2021-04-03T07:37:50.912440932Z [I] [4/0/0] [path abc123] [rtsp source] connecting
2021-04-03T07:37:52.032790618Z [I] [4/0/3] [path abc123] [rtsp source] ready
2021-04-03T07:37:52.103725075Z [I] [4/0/4] [client A.B.C.D:28643] is reading from path 'abc123', 1 track with tcp
2021-04-03T07:38:30.223700286Z [I] [5/0/4] [client W.X.Y.Z:63262] ERR: no one is publishing to path 'abc123'

It might be related to the fact that connecting with VLC to these streams takes a bit longer than usual (more than 10s), but I am not sure.

Hello, is sourceOnDemand enabled?

Yes
abc123:
    readIps:
    - A.B.C.D
    - W.X.Y.Z
    readPass: skHAJM67UKe7wmiz
    readUser: user_YpNX
    source: rtsp://user:pass@address:port/path
    sourceOnDemand: true
    sourceProtocol: tcp

I think I figured how to replicate:
authMethods:
- basic
- digest
encryption: false
logDestinations:
- stdout
logFile: rtsp-simple-server.log
logLevel: info
metrics: false
paths:
  test:
    source: rtsp://SOME_VALID_STREAM
    sourceOnDemand: true
    sourceProtocol: tcp
pprof: false
protocols:
- tcp
readTimeout: 10s
rtmpDisable: true
rtcpPort: 8001
rtpPort: 8000
rtspPort: 8554
rtspsPort: 555
runOnConnectRestart: false
serverCert: server.crt
serverKey: server.key
writeTimeout: 10s

In one terminal run vlc rtsp://localhost:8554/test, and wait for video. Then in another terminal run the same thing.
Logs:
2021/04/03 08:37:34 [I] [0/0/0] rtsp-simple-server v0.15.3
2021/04/03 08:37:34 [I] [0/0/0] [RTSP/TCP listener] opened on :8554
2021/04/03 08:38:22 [I] [1/0/0] [client <IP_ADDRESS>:60826] connected (RTSP/TCP)
2021/04/03 08:38:22 [I] [1/0/0] [path test] [rtsp source] started
2021/04/03 08:38:22 [I] [1/0/0] [path test] [rtsp source] connecting
2021/04/03 08:38:24 [I] [1/0/0] [path test] [rtsp source] ready
2021/04/03 08:38:24 [I] [1/0/1] [client <IP_ADDRESS>:60826] is reading from path 'test', 1 track with tcp
2021/04/03 08:38:37 [I] [2/0/1] [client <IP_ADDRESS>:60832] connected (RTSP/TCP)
2021/04/03 08:38:37 [I] [2/0/1] [client <IP_ADDRESS>:60832] ERR: no one is publishing to path 'test'
2021/04/03 08:38:37 [I] [1/0/1] [client <IP_ADDRESS>:60832] disconnected

If vlc is started at the same time in both terminals, then it seems to work as expected.

Thank you very much for reporting this issue, it is fixed in main and i'll publish a new release as soon as it's possible

added in v0.15.4


Travis build goes green even if casks fail to install

https://travis-ci.org/pivotal-sprout/sprout-wrap/builds/80109369#L764-L769
We should get a failing build to let us know when casks aren't available.

By switching to the chef-cookbooks/homebrew cookbook, this has been solved.


Swap j and k in the native editor

Just a quick fix to reverse these to the correct directions.

Validated


Add production org header

Is your feature request related to a problem? Please describe.
I'm often frustrated when I need to locate critical Salesforce Org details like the Org ID, instance, or API version. Currently, this requires multiple steps in the Salesforce UI, making it inefficient for debugging or troubleshooting. The outdated "Org Header for Salesforce" Chrome extension solved this problem but is no longer maintained.
Describe the solution you'd like
Add a feature to Salesforce Inspector Reloaded that displays essential Salesforce Org details (e.g., Org ID, instance, API version) directly in the extension. This information should be easily visible and customizable, allowing users to modify which fields are displayed based on their needs.
Describe alternatives you've considered

Using the old "Org Header for Salesforce" Chrome extension, but it is unreliable due to lack of updates.
Accessing the details manually through Salesforce UI, which is time-consuming.
Developing a custom solution to extract and display Org information, but this requires significant effort and maintenance.

Additional context
The "Org Header for Salesforce" extension provided a simple, effective interface for accessing Org details. Incorporating this functionality into Salesforce Inspector Reloaded would streamline workflows and enhance user productivity. Screenshots or examples of how the old extension worked can be provided if needed.

Hi @TimPaulaskasDS,
Have you checked the Org tab from the popup ?

HI @tprouvot - I'm looking for something that will display a prominent banner (like the sandbox colors you just introduced) but for production to warn the user that they are in production. We often have developers "accidentally" make changes in production. Since almost everyone I know uses Salesforce Inspector Reloaded (SIR), it would be a good addition.

@TimPaulaskasDS so the need is not org information but more a warning that this env is a production right ?
We already have an option which displays a 2px top border on productions but I agree this is not really visible, I could add a customization for the border height

This is an option that can be enabled :
https://tprouvot.github.io/Salesforce-Inspector-reloaded/how-to/?h=prod#highlight-prod-with-a-top-border

Perhaps that isn't available in v1.24?

Also, didn't want you to think there is a bug or anything. But we use a JIT Access to elevate up to Admin. I can see the org information as an admin, but not the production option/bar. Our default permissions are a Platform User.

Perhaps that isn't available in v1.24?

Yes this is correct, this is coming with the 1.25 👍

Hi @TimPaulaskasDS,
I recently had to work on a prod env quite often and found out that the top border is not enough visible. I'll work on this feature to improve it 👍


🐛 Bug Report: RAM usage leads to memory heap in k8s

📜 Description
Since the upgrade of node 18 we started noticed some unusual memory usage, we 1st started increasing the memory limit in the deployment but didn't solve the issue.
We then upgraded to Node 20 and added this configuration:
# This fixes the Node.js heap memory issues.
ENV NODE_OPTIONS=--max-old-space-size=524
ENV NODE_OPTIONS=--max-semi-space-size=8
# This disables node snapshot for Node 20 to work with the Scaffolder
ENV NODE_OPTIONS="--no-node-snapshot"

but after some days still crashes.
We based the values out of the script mentioned in this guide
👍 Expected behavior
The RAM usage should be constant and not leading to memory heap issue.
👎 Actual Behavior with Screenshots
As you can see from the Grafana dashboard, looks like there is a memory leak and the memory usage keeps increasing over time, till it reaches the container limit and then crashes

👟 Reproduction steps
Add this configuration to the Dockerfile:
# This switches many Node.js dependencies to production mode.
ENV NODE_ENV production
# This fixes the Node.js heap memory issues.
ENV NODE_OPTIONS=--max-old-space-size=524
ENV NODE_OPTIONS=--max-semi-space-size=8
# This disables node snapshot for Node 20 to work with the Scaffolder
ENV NODE_OPTIONS="--no-node-snapshot"

CMD ["node", "packages/backend", "--config", "app-config.yaml"]

and this in the deployment helm chart:
    spec:
      containers:
        - name: backstage
          imagePullPolicy: Always
          image: {{ .Values.deployment.image }}
          ports:
            - name: http
              containerPort: 7007
          envFrom:
            - secretRef:
                name: {{ .Release.Name }}-secrets
          startupProbe:
            tcpSocket:
              port: 7007
            failureThreshold: 30
            periodSeconds: 10
          livenessProbe:
            httpGet:
              port: 7007
              path: /.backstage/health/v1/liveness
          readinessProbe:
            httpGet:
              port: 7007
              path: /.backstage/health/v1/readiness
          resources:
            requests:
              memory: "1Gi"
              cpu: "100m"
            limits:
              memory: "1Gi"

Backstage uses an AWS PG RDS for DB.
📃 Provide the context for the Bug.

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

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
None

I just have to double check.
Do you really do
ENV NODE_OPTIONS=--max-old-space-size=524
ENV NODE_OPTIONS=--max-semi-space-size=8

or do you do
ENV NODE_OPTIONS="--max-old-space-size=524 --max-semi-space-size=8"

or even
ENV NODE_OPTIONS=--max-old-space-size=524
ENV NODE_OPTIONS="--max-semi-space-size=8 $NODE_OPTIONS"

what I wrote above is how we do it :)
ENV NODE_OPTIONS=--max-old-space-size=524
ENV NODE_OPTIONS=--max-semi-space-size=8
``

However, now that I read it carefully, I noticed the one I copied from your Dockerfile (from the documentation) uses double quotes

ENV NODE_OPTIONS="--no-node-snapshot"

Alright. But ENV doesn't stack.
FROM bash
ENV A=1
ENV A=2
ENTRYPOINT ["bash", "-c", "echo ${A}"]

will print just 2.

Alright so the correct way is this?
ENV NODE_OPTIONS="--max-old-space-size=524 --max-semi-space-size=8 --no-node-snapshot"

besides that, the RAM usage isn't quite normal, in 4 days it doubled the amount

In a garbage collected language - even in Java - you can see services being "greedy" and gobbling up RAM up to what you have told it that it's ok to consume.
Of course it shouldn't crash, so yes, you probably have something that does leak or makes huge allocations that do punch through the ceiling. But even if you didn't, you might see it go up to a higher level and then staying there as garbage collection starts working away at it (and then dropping down to a lower baseline and start over, after a restart).

OK, so should I update the Dockerfile as mentioned above, monitor it, and see if it still crashes?

Yes, and consider a higher level than just half a gig - we run with 4 or 8 gigs depending on circumstances, but granted, we load them pretty hard. Remember to update your actual minimum claims in kubernetes accordingly


Question: how to detect if vim.ui.input is been patched by this plugin via lua?

Hi, is there a way to detect if vim.ui.input is been patched by this plugin, or I'm using the builtin neovim's vim.ui.input?

There's not a great way to do so. What are you trying to accomplish?

emmm, I should close this issue for now, maybe after I come up with a minimal init lua that can re-produce the issue that I want to show.


HBASE-24285 Move to hbase-thirdparty-3.3.0

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 20s
Docker mode activated.

_ Other Tests _

+1 :green_heart:
asflicense
0m 16s
The patch does not generate ASF License warnings.

21m 49s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1611/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1611

Optional Tests
dupname asflicense hadoopcheck xml

uname
Linux 716547490cd6 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / a499f3748d

Max. process+thread count
63 (vs. ulimit of 12500)

modules
C: . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1611/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 34s
Docker mode activated.

-0 :warning:
yetus
0m  7s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 35s
branch-2 passed

+1 :green_heart:
compile
2m  6s
branch-2 passed

+1 :green_heart:
shadedjars
4m 28s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
2m  7s
branch-2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m  8s
the patch passed

+1 :green_heart:
compile
2m  4s
the patch passed

+1 :green_heart:
javac
2m  4s
the patch passed

+1 :green_heart:
shadedjars
4m 26s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
2m  2s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
267m 58s
root in the patch passed.

295m  4s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1611/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1611

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 90758d23c989 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / a499f3748d

Default Java
1.8.0_232

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1611/1/testReport/

Max. process+thread count
5057 (vs. ulimit of 12500)

modules
C: . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1611/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

Closing in favor of #1605 .

Thanks @petersomogyi
Looks like branch-2.3 is happy w/ new thirdparty.


ENH: Add RDFa, JSON-LD to HTML templates

[ ] ENH: Add RDFa, JSON-LD to HTML templates

How to schema.org :

https://schema.org/url

https://schema.org/url#examples > RDFa, JSON-LD

JSON-LD

FileExt: .jsonld, .json, .jsonld.json
JSON-LD in HTML:

JSON-LD default context: https://www.w3.org/2013/json-ld-context/rdfa11

<script type="application/ld+json" id="jsonld">
{"@context": {"schema": "http://schema.org/"},
 "@id": "http://example.org/ns/1#thing1",
 "@type": ["schema:Thing",],
 "schema:name": "...",
 "schema:url": "http://example.org/ns/1#thing1",
}
</script>

How to schema.org, opengraph, twitter cards:

https://github.com/CodeForAntarctica/codeforantarctica.github.io/pull/3

] ] DOC: add links to structured data validation tools
] ] ENH,BUG,SCH,TST: add structured data validation tests

See: https://github.com/blockchain-certificates/cert-schema/issues/25#issuecomment-282571524 > canonicalizationAlgorithm

Excellent suggestion. We should do this for cert-web-component as well

Excellent suggestion. We should do this for cert-web-component as well

https://github.com/blockchain-certificates/cert-web-component/issues/4


feat(ci): support debugging on CI server through ssh

Description
As a contributor I want to be able to debug the failing tests on the CI server directly so that I can figure out what is going wrong even if my tests are only failing on the CI server and not on my local machine (which is a very common scenario at present...)
Use this (?) => https://github.com/marketplace/actions/debugging-with-ssh
Acceptance Criteria

Works out of the box with VSCode debugger (preferably, but other is acceptable too)
GIF tutorial in CONTRIBUTING.md showing exactly how it's done in 30 seconds or less.

cc: @takeutak @sfuji822 @hartm @jonathan-m-hamilton @AzaharaC @jordigiam @kikoncuo @jagpreetsinghsasan

Hello! May I take up this issue? I'd like to give this a try ⭐ !

@Leeyoungone All yours! :-)
Disclaimer: I tested out a few months back and the linked GH workflow does indeed work for the purpose of providing SSH access to the CI, but I haven't had a chance to try out if I could debug tests as well so that's the interesting bit and if you  can make it work great, if not, then it's okay to  break this into two parts one is about documenting how to use the SSH connection itself and then a second issue (to be completed at a later time) about the specific VSCode debugging.


Update README.md

What's changed, or what was fixed?
Added type to the apigee_environments table in README so users know PAYG 2024 updated attributes are now supported.
Fixes: #issue

[X ] I have run all the tests locally and they all pass.
[ X] I have followed the relevant style guide for my changes.

thanks @Teodelas
looks like the GH action that was supposed to catch this in the first PR failed us. I'll take a look later.
The action should assert that the docs generaetd with tools//update-docs.sh are current.
Anyway thanks for spotting it!


MNI Atlases

Make atlas folder within m2g for all MNI registered atlases

(And those that exist there are compressed)


Assets which were locked in a pool can't be accessed

Hello, some time a go o locked lunr and zil in a mega pool, with the time, the mega lunr-zil pool became basic pool and I gathered different rewards. Now I'm trying to reclaim them, but now matter how long im waiting. The rewards and my contributions are not showing.

Doest it work?


Fix mixed key constants breaking sorted_constants for hashing ASTSource

Fixes bug introduced in: https://github.com/openai/triton/commit/1ecbc27a8169cd47ef81e061789f05b913a740b1
Reproed via dynamo with a manually updated pin
test_functions.py running test test_triton_kernel_various_args creates constants of  {'RANDOM_SIZE': 0, 5: 128} which breaks this hashing.
A simple step to first string the keys, and then sort works.
cc: @bertmaher @jlebar @ptillet

Thank you for the patch.
Would you be willing to add a comment in the code indicating why we have to stringify the key, so that it's less of a Chesterton's Fence?

Thank you for the patch.
Would you be willing to add a comment in the code indicating why we have to stringify the key, so that it's less of a Chesterton's Fence?

yeah ofc

Thank you for the patch.
Would you be willing to add a comment in the code indicating why we have to stringify the key, so that it's less of a Chesterton's Fence?

yeah ofc

done

Aah, now I understand.  Thanks, approved.

Whats up with CI? seems to be hard failing after formatting?

Yeah, you need to run pre-commit.  (pre-commit install and it will happen automatically.)

Wow, sorry I missed that.  I... didn't think constants ever used named keys (even when using kernels with kwargs).  Is dynamo doing something unusual to pass those as names?  In any case I guess it works (or would have if not for my sorting patch 😅)

pre-commit install

My apologies - I am working out of google3, not 100% sure how to do that. Give me a day or two to get this setup on a personal machine or aws or something lol.
In the menatime, if any of you wanna commandeer it, be my guest :P

My apologies - I am working out of google3

There are a bunch of other Googlers working on this project, maybe connect with @gflegar?
Also FYI we request that Googlers need to get a review from another Googler (e.g. Goran) before sending the patch to OAI.

You might also want to update your github profile, which still says Facebook!  :)

Yea, this is all new :) will do.
On Thu, Mar 21, 2024 at 6:53 PM Justin Lebar @.***>
wrote:

You might also want to update your github profile, which still says
Facebook! :)
—
Reply to this email directly, view it on GitHub
https://github.com/openai/triton/pull/3434#issuecomment-2014171833, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABEI6NEQIYXQ3OTTJXAPSM3YZOFJBAVCNFSM6AAAAABFCI4YSWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJUGE3TCOBTGM
.
You are receiving this because you authored the thread.Message ID:
@.***>


Add file picker

Add basic file/location picker

@kulmann @PVince81 Ready for review. Sorry, it's all just in two commits. I was originally writing the code in Phoenix repo and when I moved it here I lost commit history.


better error handling

I keep running into the same issues:
I've been trying to figure out the issues for several hours but don't see what's wrong.
The error message does not help in any way.
This is less about the issue than the fact that errors could deliver better information.
terminal
TypeError: Cannot read property 'examples/lib/areas/demo.js' of undefined
    at getComponent (/Users/greada/Workspace/Github/react-spring/node_modules/@patternplate/api/lib/demo.js:405:10)
    at /Users/greada/Workspace/Github/react-spring/node_modules/@patternplate/api/lib/demo.js:353:29
    at /Users/greada/Workspace/Github/react-spring/node_modules/@patternplate/client/lib/app/render-page/index.js:99458:27
    at <anonymous>

Chrome
GET http://localhost:1337/api/demo/areas.html 500 (Internal Server Error) areas?components-enabled=true:403

versions
"@patternplate/cli": "^2.5.4",
"@patternplate/render-react": "^2.5.2",

config
module.exports = {
  docs: ['./API*.md'],
  entry: ['./examples/lib/**/demo.js'],
  render: '@patternplate/render-react/render',
  mount: '@patternplate/render-react/mount'
}

jsx
import React from 'react'

export default  () =>
Hello World

js
"use strict";

Object.defineProperty(exports, "__esModule", {
  value: true
});
exports.default = void 0;

var _react = _interopRequireDefault(require("react"));

function _interopRequireDefault(obj) { return obj && obj.__esModule ? obj : { default: obj }; }

var _default = function _default() {
  return _react.default.createElement("div", null, "Hello World");
};

exports.default = _default;

Please provide a link to the relevant repo / commit hash so I can reproduce.

Without a repro this is not actionable. Please feel free to reopen when you can provide one.


#793 - Explorer: "View Owners Strategies"

#793

[ ] search input field keeps the wallet address on browser "back"
flow:

visit explorer
select pair
search for dai/eth
click the menu of any strategy and visit owner
click the back on the browser to go back to the last page
expected: see the pair in the search input field
actual: see the wallet address


How to do the maintenance and migration

Hi all, so finally we made the necessary step to create yet another fork of flakehell xD. The name is awesome by the way.
Do you have any idea of how you want to do the migration and maintenance?

we're on it, see https://github.com/flakeheaven/flakeheaven/discussions/1


#25 event image uploads

This includes file exports and a little bugfix to filenaming to keep it consistent with aux_data_inserters

Confirmed works on the vessel, exports folder as intended


Provide a way to express cookbook multiple constraints

This was initially reported in https://tickets.opscode.com/browse/CHEF-4727 and I couldn't tell if it was migrated or Triaged for Later.
Some cookbooks may have a very long span of compatibility across multiple versions and then a major version breaks backward compatibility as anticipated with semantic versioning.  In a scenario where a cookbook utilizes the database cookbook I have a recipe that requires 1.3.0 for the mysql recipe.  This is removed in 4.0.  Pessimistic versioning doesn't cover constraints spanning multiple versions.
I tried to declare the dependency twice depends 'database', '>= 1.3.0' and depends 'database', '< 4.0', that appears to disregard the second declaration.  There should be some way to express these constraints.

this may be useful. https://github.com/npm/node-semver

This is super obnoxious that we can't do dependencies with more than one constraint (like is commonly done in ruby gems). It means that when we have a cookbook that is referenced by many other cookbooks we either have to

use optimistic version constraints and have things break when we go to a new version. (For example: >= 9.0.1)
use pessimistic version constraints and have to update them in every related cookbook each time we bump the major version. (For example: ~> 9.0 and then change it to ~> 10.0 when 10.0.0 comes out)

Both of these have problems. With optimistic versioning the risk is obviously that some new breaking change will come out and ... break things. With the pessimistic versioning, we basically are saying that the second cookbook cannot use version 9.x anymore when it maybe can just fine, depending on what the breaking change was. Often we'd be happy with '>= 9.0.0', '< 11'. Also, a problem with pessimistic versioning and semver is that if you want to be okay with all 9.x, because you don't mind getting new features, you do ~> 9.0 but if there is some crippling bug that wasn't fixed until 9.0.5, there's no way to say all 9.x and also at least 9.0.5 (at least not with a single constraint. The rubygems docs talk about how to do this with multiple constrains in their section on pessimistic versioning).
So we've gone with pessimistic versioning but it makes it a huge pain when there's a major version change because it spreads like some sort of virus across all the cookbooks that are in the dependency graph.
 Chef is still responsible for resolving dependencies, not rubygems.

You can use Bundler to solve the gems, convert them all to cookbooks, and feed them to chef-solo or chef-client local mode. The actual solver issue is with Erchef, not Chef itself (though Chef does enforce the validation).

This is so painful to work around for all the reasons @b-dean mentions

I think this is a dup of some other issue which has better details.
Yep closing in favor of #2457 and #3924


[ArPow] Add distro matrix to tarball ci

This builds upon the work done in https://github.com/dotnet/source-build/issues/2290.
Add the various distro type/versions and source-build configurations (e.g. offline/online) to the tarball ci.

A couple of options to consider, mostly based on current/existing as well as potential next users of source-build.

Latest released version of Fedora (34/35)
RHEL
CentOS Stream 9, which is basically the in-development/in-testing version of RHEL 9
Other RHEL rebuilds? CentOS? Rocky?
Arch? (We have reports from ArchLinux maintainers that indicate they use source-build and the build often breaks for them)
Ubuntu
Debian


Improve names, indicate when truncated

This PR improves some names, and adds an indicator when the output table is truncated.
I think this closes #8. Technically we could filter all of the allocations to report a fully accurate number, but I think users will typically want to truncate the table

https://github.com/CliMA/ReportMetrics.jl/runs/4889253186?check_suite_focus=true#step:6:104
LGTM

bors r+


Support for PDF receipts

Not sure if this use case is shared among others: I use Scanbot to scan my receipts as multi-page PDFs. Would be great if this tool could work on these pdfs.
Scanbot does a sort of OCR itself, but it doesn't seem to be that good, in the sense that it adds too much noise: a receipt contains so much text, and I'm only interested in the articles, price per article, to see price evolution across multiple weeks.

Your use-case makes a lot of sense to me.
We could use pdf2image as a preprocessor before recognizing the text. I think that would be the easiest thing to try.
Alternatively you could try OCRmyPDF to see if it works with your inputs out of the box.


[DSEC-685] add leoapps to xml uploads

LeoApps now can be scanned like UI scans, and need to have their scan XML uploaded in order to be eligible for the full ConMon experience.

Looks good.


playback keep reading the same frames while writing frames to disk by stbi_write_png

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
D435

Firmware Version
5.9.14

Operating System & Version
Win10

Platform
PC

SDK Version
2.14.1

Issue Description
Hi, I'm currently using playback to read from two rosbag files and synchronize those frames. As far as I don't write those frames to disk by stb, pipe.wait_for_frames() return each frames in .bag file correctly. However, when I try to call stbi_write_png, the next call of playback.resume() and pipe.wait_for_frames() return exactly the same frameset as the previous one.
  auto device = pipe.get_active_profile().get_device();
  rs2::playback playback = device.as<rs2::playback>();

  playback.resume();
  frameset = pipe.wait_for_frames();
  playback.pause();

void saveImages(video_frame & f, std::stringstream & filename, std::string & dir, std::string & subdir)
{
  std::stringstream path;
  path << dir << "\\" << subdir << "\\" << filename.str();

  stbi_write_png(path.str().c_str(), f.get_width(), f.get_height(),
            f.get_bytes_per_pixel(), f.get_data(), f.get_stride_in_bytes());

  std::cout << "Saved " << path.str() << std::endl;
}

Thanks for the help

Hi @dorodnic
Thank you for the quick reply. I noticed playback.set_real_time() has similar functions as calling pause and resume, but it doesn't work for me as well. I'll try decreasing playback speed.

Hi @hflsdupont
Sorry for long delay. We believe this should be now resolved (since 2.16.1 release).
Do you need additional support on this issue?


⚠ Turnos 24x7 has degraded performance

In 4589c43, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 1107 ms

Resolved: Turnos 24x7 performance has improved in 2319b2b.


Fix key type for tnt and add tokenType

📝 Description

Fixed issue with TNT transactions sending the wrong key type.
Added ability to support other token types.

❓ Context

Impacted projects: Helium HNT Wallet
Linked resource(s): ``

✅ Checklist

[x] Test coverage
[x] Atomic delivery
[x] No breaking changes

🚀 Expectations to reach
Please make sure you follow these Important Steps.
Pull Requests must pass the CI and be internally validated in order to be merged.

Hi @Perronef5,
Thank you for your contribution.
Could you please:

Fix the conflicts

Fix the Helium tests (check the CI if needed)

Thank you very much.

Hi @aelmilligy-ledger
I will make those changes by today 👍🏻

the pnpm lock file appear broken. I would recommend to retake the pnpm-lock file from develop branch and pnpm i over it.

let us know if you need help on this 🙏

@gre I could really use your help here... The CI keep failing even when I didn't even touch those packages. I am doing:
git checkout develop pnpm-lock.yaml
pnpm install

something weird has happened with the compressjs package. Here is your change

and here is what it looks like in develop
github.com/LedgerHQ/compressjs/d9e8e4d994923e0ea76a32b97289bcccfe71b82e:
    resolution: {tarball: https://codeload.github.com/LedgerHQ/compressjs/tar.gz/d9e8e4d994923e0ea76a32b97289bcccfe71b82e}
    name: '@ledgerhq/compressjs'
    version: 1.3.1
    hasBin: true
    dependencies:
      commander: 2.20.3
    dev: false

Not sure if it's one of the new dependencies you've added

But definitely you're not supposed to have a git+ssh link inside the pnpm-lock

something weird has happened with the compressjs package. Here is your change  and here is what it looks like in develop
github.com/LedgerHQ/compressjs/d9e8e4d994923e0ea76a32b97289bcccfe71b82e:
    resolution: {tarball: https://codeload.github.com/LedgerHQ/compressjs/tar.gz/d9e8e4d994923e0ea76a32b97289bcccfe71b82e}
    name: '@ledgerhq/compressjs'
    version: 1.3.1
    hasBin: true
    dependencies:
      commander: 2.20.3
    dev: false

Not sure if it's one of the new dependencies you've added  But definitely you're not supposed to have a git+ssh link inside the pnpm-lock
EDIT: Tried locally, copy the resolution from the develop branch instead of yours and try again (i tried to fix but i don't have the rights to push to your PR)

@valpinkman Thankyou for the help. I think I got it this time. May you please trigger the builds again 😀


SAK-30142: Importing material during new site creation sometimes leads to tool duplication

This looks good to me. We've been doing internal QA and this has stopped tool duplication at least 4 times during testing.


Responsive config

Hello @cevou,
This pull request contains a few ideas and code style improvements.
Can you let me know where I can improve?
Regards,

Hi @haringsrob. Thanks for the PR. I will go over it after work.

@cevou Thanks for the quick reply, I see that one travis test is failing, I will check this tomorrow

Can you please give a short description of what all the changes are doing?

It would also be great if you could split code style improvements and features in different PRs. It's much easier to review then.


Remove Endpoints - invite

User Story - Business Need

In the effort to clean up our code we need to investigate and remove unused endpoints. This ticket is to take a look at the endpoints under /invite/ and remove the ones marked for removal. You can view the table of endpoints here.
User Story(ies)
As an engineer
I want to clean up and reduce our codebase
So that it is easier to maintain and upgrade in the future.
Additional Info and Resources

Endpoint Table
Endpoint Spreadsheet

Engineering Checklist

[ ] Investigate the endpoints starting with /invite/ to make sure they aren't being used
[ ] Remove tests associate with those endpoints
[ ] Remove the code associated with those endpoints (if possible). Make sure not to remove any code used by other parts of the application.

Acceptance Criteria

When the designated code and tests have been removed, the application retains full functionality.

QA Considerations

[ ] The QA Regression Suite passes
[ ] The Cypress regression passes

Potential Dependencies

Make sure the removal of these endpoints doesn't affect the work Strike is doing.

Closing/no longer relevant.


Add blog post

Please add this post: Safe Way to access private fields in Rust
Post URL: https://blog.knoldus.com/safe-way-to-access-private-fields-in-rust/
Blog Homepage: https://blog.knoldus.com
Author Name: Amita Yadav, Knoldus Inc
Categories: Getting Started, Language, Performance

Published in c976b72


refactor(providers): merge JsonPubSubClient into JsonRpcClient

Description

Solution

#116  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @ArtificialPB and the rest of your teammates on  Graphite


Elasticsearch: auto-TLS via cert-manager

It should be possible to easily enable TLS on an Elasticsearch cluster.
Initially, an implementation that relies upon cert-manager for signing certificates in its simplest form (e.g. a Certificate resource is created per replica) will be the target:
API Changes
We will need to add a new field structure to elasticsearchclusters.spec.tls
kind: ElasticsearchCluster
metadata:
  name: my-staging-cluster
...
spec:
  tls:
    enabled: true
    issuerRef:
      name: my-staging-cluster-ca
      kind: Issuer

Initially, only the 'CA' based cert-manager issuer will be supported: https://github.com/jetstack/cert-manager/blob/master/docs/user-guides/ca-based-issuer.md
This may change in future once discussion around generalising the Certificate resource type has been resolved: https://github.com/jetstack/cert-manager/issues/265
Controller changes
navigator-controller will need updating to:

generate a CA/signing keypair for each cluster

can be done in navigator-controller initially
eventually can be moved into a 'selfsigned' cert-manager Issuer: https://github.com/jetstack/cert-manager/issues/84 https://github.com/jetstack/cert-manager/issues/85

create an Issuer to sign certificates from this CA
pass the issuerRef as a CLI arg to each Pilot

Pilot changes
if tls is enabled:

create/retrieve Certificate resource for this pilot
grab generated Secret resource containing keypair
inject them into FS and appropriately configure node for serving

Open questions

(may be more of a general cert-manager problem): should each Pilot be generating its own private key and then creating a CSR for this, instead of storing the private key in the k8s apiserver? This provides a stronger auth model. We'll need to investigate how we can make cert-manager support this.

certificate rotation should be handled by Pilot too

TLS requires x-pack. How do we more generally support x-pack only features in ES? ref #200

/kind feature
/cc @mattbates @wallrj

@munnerz LGTM - except I don't think issuerRef should appear as a field on the ElasticsearchCluster resource as it leans towards a specific implementation. The tls stanza should only have an enabled field - perhaps an annotation would be the best way for users to set the method for certificate creation (e.g. cert-manager/self-signed) and the name of the Issuer to use/create if cert-manager is to be used


Refacto: Split operation 'create' for other operation 'Update/Delete'

We should have a 1-1 cardinality with ProvisioningOperation and 0,n cardinality with UpdateOperation in the Service model.

No more usefull with allow multiple create operation.


Athlete id is modeled as an integer (i.e. Java client becomes Integer)

https://github.com/strava/developers.strava.com/blob/master/swagger/athlete.json.mustache#L6
Thus far, we've been modeling most ids like this as Longs or int64 to prevent any capacity issues down the road.

Thanks for bringing this up! I'm going to close the issue on this page and move it for tracking elsewhere.