Learning typeclasses

Exploring ad-hoc polymorphism and type classes as a solution to some typing problems.

@davidrpugh Interesting, I'm also reading about typeclasses and scalaz at the moment. What are you trying to achieve in this PR?

Apparently structural or duck-typing is quite inefficient (as it requires using reflection) and should generally be avoided.  Going forward it is probably a good idea to sort out a solution that avoids using this feature.  Codacy results discuss this an provide references...

Major objective with this PR is to solve issues related to the return types of the insert, remove, clear methods.  Currently the code in the develop branch does not return the correct sub-type of auction when trying to implement auctions with various quoting policies.
Once could create an auction with a particular quoting policy without issue, but then if you insert an order into the auction you get back the wrong auction type! You will get a more general auction type that no longer has a quoting policy!  This PR uses type-classes and ad-hoc polymorphism to solve this problem.

@bherd-rb If you are interested in Scalaz I would recommend taking a look at TypeLevel and cats as well as all of the rest of the Typelevel projects.

@bherd-rb I am having trouble getting Java to find the implicitly defined methods on the auction instances.  I thought that since Scala is compiled before Java, the Java compiler would have access to the compiler generated methods.  I guess not?

@davidrpugh I have to admit that I haven't really got my head around implicits in Scala yet. They are still a mystery to me. I'll have to do some reading and try to figure out what the problem could be.
Thanks also for the pointers to TypeLevel and cast. I'll take a look.

@bherd-rb After using javap to examine the Java byte code it appears that the Scala compiler weaves together the various components of the type class and creates an anonymous class. For example the UniformPricingImpl of the SealedBidDoubleAuction type class is compiled down into the SealedBidDoubleAuction$UniformPricingImpl$$anon$2.class file. Apply javap to this file shows that the relevant methods are defined inside a public final class of the same name.
In principle it seems like it should be possible to somehow create an instance of this class, but I have not yet worked out how...

@bherd-rb Take a look at the Sandbox.java file.  I managed to sort out a solution that involves manually "weaving" the Ops class and the UniformPricingImpl class together.  Perhaps this logic could be encapsulated inside a JSealedBidDoubleAuction class?
Still not convinced that this is the only solution...

@bherd-rb For reference here is the discussion I started on SO.

@bherd-rb I just made a first attempt at creating a Java wrapper JSealedBidAuction.java for the new Scala type class of similar name.  There is an example use case in the Sandbox.java file.  What do you think? I am not a confident Java programmer so might be a bit of a hack job :)

@bherd-rb I have added an open-bid, double auction with discriminatory pricing to the Java functional sources.  Take a look and tell me what you think.  If this works for you, then I propose that we move the java implementations of the auctions into the core library code, quickly add the remaining auctions, tidy everything up, and merge...

@bherd-rb I went ahead and added Java wrappers for most of the remaining auction types.  I haven't yet implemented Java equivalents for the various companion object methods such as withAskQuotePricingPolicy.  I am not sure that we need to bother with these convenience methods at present. Thoughts?

@davidrpugh Sorry for the delay, I'm quite busy at the moment. I'll take a look at the implementation.

@bherd-rb No worries I am going to work on other things for a bit.  I just want to make sure that you have a working Java implementation that serves your purposes for the first release.  We can optimize things later...

@davidrpugh I've just updated my code and integrated the new wrappers. Great stuff! It's a bit annoying to write and maintain all these separate wrapper classes in ESL but from a Java perspective, it's clearly much more user-friendly now.
We definitely have to switch to Scala as soon as possible in our code ...

@bherd-rb Great! It is a bit annoying, but I probably spent 10x less time writing the wrapper classes in Java then I spent understanding the intricacies of the Scala compiler generated byte code.   I need to add implementations for double auctions with uniform pricing.  Given that you are happy with the work thus far I am going to do this now and then start cleaning things up in preparation for our first release.

@bherd-rb One other thing I want to do is to push the conversion from Scala Stream into the clear method of the various Java wrappers.  Do you have a preference for the Java type? Should I try to keep everything lazy and convert Scala Stream to Java equivalent? Or just convert to a List?

@bherd-rb I just added a JClearResult wrapper that encapsulates the conversion process between a Scala Stream and a Java Stream.  Does this work for you?  I thought preserving the laziness of the pipeline on the Java side was worthwhile in the near term for consistency with the Scala API.  Going forward I am not convinced that a Stream is really the right type of collection to store the fills but I think we need to experiment more before making this choice...

@bherd-rb Take one last look and let me know if you see anything amiss.  Not that now Java auction wrappers make use of a JClearResult which represents fills using a Java Stream.  If all looks good to you I am going to merge to develop...

@davidrpugh The new version including JClearResultworks very well! I'm going to approve the changes so that you can merge everything.


issue #626 show 1 like if there is 1 like else show x likes

What is the change?
If there is only one like then show 1 like else show x likes where x is number of likes (on the post page)
Related issue?
close: #626
How was it tested?
Remove this line and tell us how the code was tested.
Checklist:
Before you create this PR, confirm all the requirements listed below by checking the checkboxes [x]:

[x] Have you followed the Contribution Guidelines while contributing.
[x] Have you checked there aren't other open Pull Requests for the same update/change?
[] Did you lint your code before making the Pull Request?
[] Have you made corresponding changes to the documentation?
[x] Your submission doesn't break any existing feature.
[x] Have you tested the code before submission?

Screenshots or Video:

@Ayush0730  I think for 0 also it should be 0 likes ?
or should it be 0 like ?

@Ayush0730 I think for 0 also it should be 0 likes ?
or should it be 0 like ?

Yes, for 0 it is 0 likes


Update Docusaurus to Alpha 58

Status
In Hold for verification
Related Issues
upgrading Docusaurus to Alpha 58
Description
A few sentences describing the overall goals of the pull request's commits.
Screenshots
Paste here any images that will help the reviewer

@sserrata could you please review?

Looks good. Only one small issue I noticed: the XSOAR logo crowds out the Algolia search input in mobile view. Not sure that there's much we can do.

One possible solution to the logo search bar problem:
@media (max-width: 380px) {
  .navbar__logo {
    width: auto !important;
  }
}

Looks good.
Did you take a look at the following comment from GuardRails: #220 (comment) ?

@glicht I looked into this vulnerability and, in this context, it appears to be benign. The HTML is derived from Docusaurus which means it can be trusted.
I tested using DOMPurify to sanitize the HTML but it wasn't enough for Guardrails not to report the vulnerability. Guardrails appears to simply report on the use of dangerouslySetInnerHTML and doesn't factory in additional steps to sanitize the HTML.

Concurred @sserrata. Was going to bring this up with the docusaurus team, but it looks to be safe here. Going to meet with netlify today to discuss the memory and time issues that are happening with the build before I push this through.

@csestito I've added a .npmrc file that increasing the node available memory to 5GB. Seems to have solved the build failure.

@glicht Thanks for the help, feel free to merge.


ng serve compiling again and again without any changes

I know it's a repeat of https://github.com/angular/angular-cli/issues/13099
and i have tried all the options mentioned in above thread. Nothing worked for me.
Below is the versions . i am using latest version.
ng --version
 _                      _                 ____ _     ___
/ \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|

/ △ \ | '_ \ /  | | | | |/ _ | '__|   | |   | |    | |
/ ___ | | | | (| | || | | (| | |      | || | | |
//   __| ||_, |_,||_,||       _|||
|___/
Angular CLI: 8.3.19
Node: 10.16.0
OS: win32 x64
Angular: 8.2.14
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router
Package                           Version
@angular-devkit/architect         0.803.19
@angular-devkit/build-angular     0.803.19
@angular-devkit/build-optimizer   0.803.19
@angular-devkit/build-webpack     0.803.19
@angular-devkit/core              8.3.19
@angular-devkit/schematics        8.3.19
@angular/cdk                      8.2.3
@angular/cli                      8.3.19
@angular/http                     7.2.15
@angular/material                 8.2.3
@ngtools/webpack                  8.3.19
@schematics/angular               8.3.19
@schematics/update                0.803.19
rxjs                              6.4.0
typescript                        3.5.3
webpack                           4.39.2

ng serve
10% building 3/3 modules 0 activei ｢wds｣: Project is running at http://localhost:4200/webpack-dev-server/
i ｢wds｣: webpack output is served from /
i ｢wds｣: 404s will fallback to //index.html
chunk {main} main.js, main.js.map (main) 30 kB [initial] [rendered]
chunk {polyfills} polyfills.js, polyfills.js.map (polyfills) 290 kB [initial] [rendered]
chunk {runtime} runtime.js, runtime.js.map (runtime) 6.15 kB [entry] [rendered]
chunk {styles} styles.js, styles.js.map (styles) 180 kB [initial] [rendered]
chunk {vendor} vendor.js, vendor.js.map (vendor) 6.98 MB [initial] [rendered]
Date: 2019-11-19T11:31:51.206Z - Hash: 03e05c621ab120affcd0 - Time: 150990ms
** Angular Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/ **
i ｢wdm｣: Compiled successfully.
i ｢wdm｣: Compiling...
Date: 2019-11-19T12:00:43.340Z - Hash: 03e05c621ab120affcd0
5 unchanged chunks
Time: 10273ms
i ｢wdm｣: Compiled successfully.
i ｢wdm｣: Compiling...
i ｢wdm｣: wait until bundle finished: /runtime.js
i ｢wdm｣: wait until bundle finished: /polyfills.js
i ｢wdm｣: wait until bundle finished: /styles.js
95% emitting CopyPlugini ｢wdm｣: wait until bundle finished: /vendor.js
i ｢wdm｣: wait until bundle finished: /main.js
Date: 2019-11-19T12:00:52.716Z - Hash: 03e05c621ab120affcd0
5 unchanged chunks
Time: 8826ms
i ｢wdm｣: Compiled successfully.
i ｢wdm｣: Compiling...
Date: 2019-11-19T12:01:00.459Z - Hash: 03e05c621ab120affcd0
5 unchanged chunks
Time: 7302ms
i ｢wdm｣: Compiled successfully.
i ｢wdm｣: Compiling...
i ｢wdm｣: wait until bundle finished: /favicon.ico
Date: 2019-11-19T12:01:05.946Z - Hash: 03e05c621ab120affcd0
5 unchanged chunks
Time: 5126ms
i ｢wdm｣: Compiled successfully.
i ｢wdm｣: Compiling...
Date: 2019-11-19T12:01:26.215Z - Hash: 03e05c621ab120affcd0
5 unchanged chunks
Time: 7585ms
i ｢wdm｣: Compiled successfully.

I don't know of anything that can cause repeat rebuilds without files changing. I imagine there's something in your system changing some of the files in the app folder...

You can try locally altering this file in your node_modules to see what files are triggering the watcher:
https://github.com/angular/angular-cli/blob/7e0d0ff39471f427b34019d9d164e9feee80e885/packages/ngtools/webpack/src/virtual_file_system_decorator.ts#L147-L154

I am not changing anything in app folder. I'll try to modify above file.

You might not be changing anything yourself, but there might be a background process (e.g. spawned by your editor) that is.

In order to check that. I just opened terminal and created helloworld app and then
ng serve
Still got the same problem. It's only happening after upgrading to the latest cli. previously i was using  0.803.5. once i updated to latest. Problem starts occurring.

I'm sorry, but I cannot reproduce that on my windows machine. The most likely reason is that you have some process that is altering in some way the files on disk.
If you can find what files are triggering the watcher maybe you can use the tools described in https://superuser.com/questions/521476/detect-what-process-is-changing-a-file-on-windows to discover what process is changing it.

I am also having the same problem, sometime.
I didn't change my code, but it compiled itself constantly.
[INFO] ... and 94 additional chunks [ng] ℹ ｢wdm｣: Compiled successfully. [ng] ℹ ｢wdm｣: Compiling... [ng] Date: 2020-02-04T09:44:22.144Z - Hash: a24d6bc12a1e418cb268 - Time: 4610ms [ng] 149 unchanged chunks [ng] ℹ ｢wdm｣: Compiled successfully. [ng] ℹ ｢wdm｣: Compiling... [ng] Date: 2020-02-04T09:45:07.502Z - Hash: a24d6bc12a1e418cb268 - Time: 2412ms [ng] 149 unchanged chunks [ng] ℹ ｢wdm｣: Compiled successfully. [ng] ℹ ｢wdm｣: Compiling... [ng] Date: 2020-02-04T09:46:59.372Z - Hash: a24d6bc12a1e418cb268 - Time: 2689ms [ng] 149 unchanged chunks [ng] ℹ ｢wdm｣: Compiled successfully. [ng] ℹ ｢wdm｣: Compiling... [ng] Date: 2020-02-04T09:48:05.631Z - Hash: a24d6bc12a1e418cb268 - Time: 2333ms [ng] 149 unchanged chunks [ng] ℹ ｢wdm｣: Compiled successfully. [ng] ℹ ｢wdm｣: Compiling... [ng] Date: 2020-02-04T09:48:25.501Z - Hash: a24d6bc12a1e418cb268 - Time: 1918ms [ng] 149 unchanged chunks [ng] ℹ ｢wdm｣: Compiled successfully. [ng] ℹ ｢wdm｣: Compiling... [ng] Date: 2020-02-04T09:49:00.456Z - Hash: a24d6bc12a1e418cb268 - Time: 1979ms [ng] 149 unchanged chunks [ng] ℹ ｢wdm｣: Compiled successfully.
my ionic info
`Ionic:
Ionic CLI                     : 5.4.16 (/usr/local/lib/node_modules/ionic)
Ionic Framework               : @ionic/angular 4.11.8
@angular-devkit/build-angular : 0.13.9
@angular-devkit/schematics    : 7.3.9
@angular/cli                  : 7.3.9
@ionic/angular-toolkit        : 1.5.1
Cordova:
Cordova CLI       : 8.1.2<EMAIL_ADDRESS>Cordova Platforms : android 8.1.0, ios 5.1.1
Cordova Plugins   : cordova-plugin-ionic-webview 2.5.3, (and 30 other plugins)
Utility:
cordova-res : not installed
native-run  : not installed
System:
ios-sim : 8.0.2
NodeJS  : v12.13.1 (/usr/local/bin/node)
npm     : 6.12.1
OS      : macOS Catalina
Xcode   : Xcode 11.3 Build version 11C29`.
help me, please!!!


switchCamera while a js webview callback

Hi,
When using a native button, the camera is switching, but when I receive a js callback from a webview, it's enter in the method but it's not switching ...
    // Switch camera from a native button
    fun changeCameraClicked(view: View?) {
        rtmpCamera!!.switchCamera()
    }

    // Switch camera from a button clicked in the webview
    @JavascriptInterface
    fun changeCamera() {
        rtmpCamera!!.switchCamera()
    }

I have tested that the js android interface is working fine.
If someone have any idea ... thanks in advance.

I don't know about js.
This seems a problem related with js like it is working using native code. Remember that switchcamera fail if you change to an invalid resolution for the other camera:
https://github.com/pedroSG94/rtmp-rtsp-stream-client-java/blob/master/app/src/main/java/com/pedro/rtpstreamer/defaultexample/ExampleRtmpActivity.java#L144
https://github.com/pedroSG94/rtmp-rtsp-stream-client-java/blob/master/rtplibrary/src/main/java/com/pedro/rtplibrary/base/Camera1Base.java#L748

Hi,
Yes, that's right, everything works now :) thanks for your work.
Cordialement,


Support Django 4.1 and Python 3.11

CI
Description

Add support for Django 4.1
Add support for Python 3.11
Drop support for Python 3.7 (end of life in 1 month)
Fix compatibility with tox 4
Update isort precommit version to fix CI error

Deferring Django 4.2 to

#486

Error under Django 4.2 seems to be:
ERROR Error sending data
  Traceback (most recent call last):
    File "/home/runner/work/django-dbbackup/django-dbbackup/.tox/py310-django42/lib/python3.10/site-packages/gnupg.py", line 155, in _copy_data
      outstream.write(data)
  TypeError: a bytes-like object is required, not 'str'
  ....ERROR Exception: Foo
    File "/home/runner/work/django-dbbackup/django-dbbackup/dbbackup/utils.py", line 120, in wrapper
      func(*args, **kwargs)
    File "/home/runner/work/django-dbbackup/django-dbbackup/dbbackup/tests/test_utils.py", line 81, in func
      raise Exception("Foo")

  .ERROR Exception: Foo
    File "/home/runner/work/django-dbbackup/django-dbbackup/dbbackup/utils.py", line 120, in wrapper
      func(*args, **kwargs)
    File "/home/runner/work/django-dbbackup/django-dbbackup/dbbackup/tests/test_utils.py", line 91, in func
      raise Exception("Foo")

  ..ERROR Error sending data
  Traceback (most recent call last):
    File "/home/runner/work/django-dbbackup/django-dbbackup/.tox/py310-django42/lib/python3.10/site-packages/gnupg.py", line 155, in _copy_data
      outstream.write(data)
  TypeError: a bytes-like object is required, not 'str'

@Archmonger If you could review that would be great. The project settings will need to be updated so that Python 3.7 is no longer required, and Python 3.11 is set to be required.

Will review soon, but unfortunately I cannot change the GitHub test requirements.
We'll have to wait until Janis transfers us out of Jazzband.


DOC : fix typo

oops just noticed this typo, we probably should correct this

Codecov Report

Merging #935 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #935   +/-   ##
=======================================
  Coverage   90.38%   90.38%
=======================================
  Files          46       46
  Lines        7623     7623
=======================================
  Hits         6890     6890
  Misses        733      733

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ecca65e...d95c47f. Read the comment docs.


update Stack resolver to GHC 8.10.4; more GitHub Actions coverage

GitHub Actions for both Stack and Cabal

LGTM, thanks @peterbecich


does this repo support the sft of InternVL series

does this repo support the sft of InternVL series

CAN we do this?


Update Pytest & enable Pip caching for Travis

This PR updates the versions of Pytest used in Travis and enables Pip caching to speed up the build.

With the recent changes, this has mostly been superseeded. I've added a PR for the final bit of caching pip in #46. Thanks a lot!


Component.PropTypes should be a lowercase p for prop

I'm getting a console error for the component PropTypes snippet, I think
pt→ | Component.PropTypes = {};
should be
pt→ | Component.propTypes = {};
with propTypes spelt with a lowercase 'p'
Thanks!

PR created: https://github.com/jundat95/react-native-snippet/pull/6

thank you !!


Tiktoken.encoding_for_model has bad return value on unrecognized model name

When you pass an unrecognized model name to Tiktoken.encoding_for_model, instead of returning nil it returns an unexpected Hash.
irb(main):001:0> require 'tiktoken_ruby'
=> true
irb(main):002:0> Tiktoken.encoding_for_model 'foo'
=>
{:"gpt-4-"=>"cl100k_base",
 :"gpt-3.5-turbo-"=>"cl100k_base",
 :"gpt-35-turbo-"=>"cl100k_base",
 :"ft:gpt-4"=>"cl100k_base",
 :"ft:gpt-3.5-turbo"=>"cl100k_base",
 :"ft:davinci-002"=>"cl100k_base",
 :"ft:babbage-002"=>"cl100k_base"}

The bug seems to have been introduced by https://github.com/IAPark/tiktoken_ruby/commit/0c1a45b46af6ed250d2eb82303594dab5dc7d813 which lets Hash#each return self if nothing is found.

Good find! What would you expect the response to be? nil probably?

Fantastic. If you have a moment. A failing spec would be a great contribution. The repo is a bit between ownership but this is simple enough that it'd be an easy merge

Fixed by #29


Undat is broken

It never seems to find the url for a few people. I remember someone made a PR for this today, I think. I'm running out of time and I must sail away, I hope someone can fix this 👍
Good luck!

This should be fixed with 67cabc7.


frost-button upversion

#patch#

Rejected - we should hold off on this until the decision on core is made

Should be using ember-frost-core now


Gigantic icon size

To answer both in a single image:

And in the context of the style guide:

They're .... stuff! Some SVG, some PNG!

Yup. Already does.

(I want to make the Express logo an SVG but that's neither here nor there)

Already is :) Just needs publishing\


Sync OpenAPI spec changes after 4th Jan 24

Spec and related changes needs to be synced

the diff can be seen by comparing spec in this repo and upstream repo

Updated in v0.19.0


{"error":"invalid_client"}

Can you help me sar??
i'm tried to curl the command.
the default curl command is
curl -X POST -H "Content-Type: application/x-www-form-urlencoded" -H "Authorization: Basic {BASE64}" -d "grant_type=authorization_code&redirect_uri=http://localhost/callback/&code={CODE}" https://accounts.spotify.com/api/token
and i change the "BASE64" with mine and also the Callback "CODE"
i got this {"error":"invalid_client"}
What's Wrong??

Use the newer version, with a better guide here: https://github.com/novatorem/novatorem


Weather Dataset

Hi, thank you very much for putting your code on GitHub.  In the paper you mention that the weather dataset consists of 1600 locations, however, the link in the README.md contains just one location.  To reproduce the results from the paper was the model trained on the data you link to or all locations?

The data we linked. Thanks.


Throwing needs decoupling from hands

From https://github.com/space-wizards/space-station-14/pull/23996
This isn't the way to force the landtime you want.

Fixed in #29726
I removed the bandaid stuff checking for the hands.
https://github.com/space-wizards/space-station-14/pull/29726/files#diff-b1e4188faa74f0cdb7bb2005aa4a22a61a6c272fb8599227b3eb76f0ca00f92aR174-L148

wtf I love throwing code now


MKFLA completing the Beginning Git video course

HI
I like this course
Now I can pull a request

Hey @mkfla1—congrats on submitting a PR at the end of the git course. I'm hope that you found the course valuable, and that you were able to follow along easily and learn lots.
If you weren't already using git for your code, hopefully this has inspired you to do so. I hope that you enjoy the "Mastering Git" video course as well—you'll soon be able to get git to bend to your will :)
You can now wear this #GitWarrior badge with pride—and Tweet your historic victory!

sam


Mix task to generate changelog

mix multiverse.gen.changelog

Coverage remained the same at 100.0% when pulling edac69a0a934ec779a4564415c451bdd781b2158 on features/mix-gen-changelog into dba2f5f49239364b4ba4c650da1d26a4adbe659c on master.


Added binary compatibility validator

Resolves #305

The next step is to ensure each entity in the ABI has its own documentation

#323


Fixing typos and missing rules field in UserImport model

I wanted to use import, but i get error "Error: Class "RainLab\User\Models\User\UserImport"",
when i inspected the code it's look like there is some typos and missing field.
After this changes it's works.

Thanks!


Feature request:  Automatically select and download files according to configurable rules

When the option "pause-metadata=true" is passed to aria2c, after the metadata download is completed, it will automatically pause to wait for users to select the files they want to download.
Most of the time, the choice is so fixed that it can be summed up in simple rules. For example, when metadata contains only one file, download it directly is the only one choice, and whenever it appears "__ pading_file_%n", we always don't want to download it because it's just an alignment file.
According to the file extension, keyword, directory level and other information to automatically select whether to download or not will greatly simplify the user's operation——after all, some torrents contain too many files.
In addition, automatic file selection allows users not to always pay attention to when .torrent file downloads complete. If aria-ng can automatically pop up the file selection window when "pause metadata", it will be better.

You can exclude padding file in the download result, but you just cannot prevent downloading it, since it is padding file, it is contained in the same block as other files. The only exception is that you are using the same BT client which created this torrent, which actually can pseudo-download it since it knows the content in advance by the padding algorithm.


soundfile.LibsndfileError: <exception str() failed>

I encounter this problem when calling soundfile with ECAPA, how can I solve it?

Please upload an example file that raises this exception when loading.

 I encounter this problem when calling soundfile with ECAPA, how can I solve it?

Did you solve this problem? I am also facing this.

 I encounter this problem when calling soundfile with ECAPA, how can I solve it?

pip install soundfile==0.10.3.post1
Try installing this version of soundfile. That error is resolved for me.

I had this issue too. After some code debugging and analysis, I found that this problem was caused by a corrupt/missing file.
If you're experiencing this problem, first check the filename to make sure it actually exists.

I've had this issue too, while installing 0.10.3.post1 as suggested above didn't help. What did help was the fact that 0.10.3.post1 included the problematic file in the error message. This is not the case in 0.12.1 - would it be possible to print out the problematic wav again?

LibsndfileError messages are generated by libsndfile, not soundfile. While it would be possible to annotate each such error message with a file name, not every soundfile object has a file name. It might be a network stream, or a socket, or a data buffer.
Have you tried debugging into the error and check what is causing it? This should be trivially solvable with a debugger.

@bastibe yes, I think you misunderstood my message.
There is a behavioural difference between SoundFile v0.10.3.post1 and v0.12.1 which results in a less useful error message in v0.12.1.
Specifically the error message in v0.12.1 is soundfile.LibsndfileError: <exception str() failed> whereas in 0.10.3.post1 instead of the str() it has the actual filename of the file which causes the problem - making it much faster to localise the problem.
Yes, a debugger would also highlight this, but it takes much more digging and time. A helpful error message helps trivialising the debugging process even further.
Of course, as you say, if SoundFile simply cascades the error received from the Sndfile library perhaps there is nothing to do. But since it seems to be related to the version of SoundFile installed rather than Sndfile library - it suggests to me there has been a change making debugging that little bit more difficult.

Is this a behavior change of soundfile, or libsndfile? If it's a change in libsndfile, please open an issue in their repository. If it's a change in soundfile, please draft a pull request with the sort of behavior you want.
Also, please post a sound file that causes this issue, so we can reproduce it.

I'm afraid I can't as the file I've got was work related and can't be shared. Try putting in a wav file with a missing RIFF header - that was the particular issue for me.
Since the only thing I changed was to do pip install SoundFile==0.10.3.post1 and back to 0.12.1 there was no output of different libsndfile versions being pulled in the background, it seems to be a change in SoundFile.
I will leave to you whether you or some other maintainer of SoundFile to make this change. I was merely trying to help by pointing out what I thought was a regression. I don't have time to change the repo code.

I encounter this issue in ECAPA-TDNN too ,  it may caused by
import sys
sys.path.append('current root')
I added these when I tried to test the model, and after block these declarement, it works for me.

请问该如何解决呢

Please write in English.

The previous problem has been solved. How did everyone tackle this one?


Documentation - Contributing - Inform potential contributors about used tools

Description
For some types of contributions, specify, if relevant, which technology(ies) Taipy uses
As an example, in order to expand the documentation, explain that the present support is made using MKDocs and propose a link to know more about its usage.
Acceptance Criteria

[ ] Ensure new code is unit tested, and check code coverage is at least 90%
[ ] Propagate any change on the demos and run all of them to ensure there is no breaking change
[ ] Ensure any change is well documented

https://docs.taipy.io/contributing/contributing/


Adding hawkular-tenant headers for the URL rest api.

MiQ ruby client calls this during the tests - https://github.com/hawkular/hawkular-client-ruby/blob/master/spec/integration/inventory_spec.rb#L92:L102
@lucasponce could you please review? This is one of the reasons why the specs were failing against the live services.

LGTM


standard or reporting format in csv_dd guide?

Documentation reference (URL): https://github.com/ess-dive-community/essdive-file-level-metadata/blob/master/CSV_dd/CSV_dd_quick_guide.md
Submitter: Kim
Justification (why is this change necessary?): possibly inconsistent use of terminology

I suggest the following changes: In the dd quick guide short tables should the metadata elements "standard statement" and "standard definition" use the word standard or reporting format?

@regnans Good catch. It shows up the same way in the CSV_quick_guide so it will need to be changed. @robcrystalornelas FLMD has - reporting format statement; reporting format definition
No matter how much you proof . . . .

I updated both guides so that they now say 'reporting format statement' and 'reporting format definition'
Thanks for pointing this out @regnans!


checker inside docker container (path issue)

I'm using a dockerized phpcs.
#!/bin/bash
sudo docker run -i --rm -v "$(pwd)":/app phpcs phpcs --basepath=/app/ "$@"

I use vim+syntastic setup in the following way
let g:syntastic_php_checkers = ['php', 'phpcs']
let g:syntastic_php_phpcs_exec = '/usr/local/bin/phpcs'

I used to have:
let g:syntastic_php_phpcs_args = '--standard=PSR2'
and would often change this global option per project. I'd like to move away from this and have a file inside project root so I don't have to edit .vimrc every time I jump from project to project with different standards.
If I don't define --standard phpcs reads from the root .phpcs.xml file. But it works only for the root files, if I navigate to some other folder and open php files in sub directories, .phpcs.xml is not being found - this is expected because of the container setup, phpcs container doesn't know of any parent directories and files in them. Syntastic always runs checker from current dir.
Is there a way to make Syntastic run checker from project root? and have all file path relative to it?

Please see the FAQ.

You mean 4.9 My favourite checker needs to load a configuration file from the project's root rather than the current directory... right?
That would still not work, because actual file .phpcs.xml is not inside the docker container. So passing full path from host OS to guest Container will result in file not found inside guest phpcs container.
Just to clarify this. We have following structure:

.phpcs.xml
file.php
dir/file.php

$phpcs dir/file.php (works!)
$phpcs file.php (works!)

$cd dir && phpcs file.php (doesn't work!)
This is because when I cd into dir, phpcs container is run from that directory and it has no knowledge of ../.phpcs.xml, this file simply doesn't exist inside.

Same works for vim.
$vi dir/file.php (works!)
$cd dir && vi file.php (doesn't work!)

'makeprg': '/usr/local/bin/phpcs --report=csv dir/file.php' works
cd into directory and and open with vim
'makeprg': '/usr/local/bin/phpcs --report=csv file.php' doesn't work
What I need is for Syntastic or vim whichever handles this part to always start checker from specific root directory of the project.

No.  The point is you can read the file in Vim, and form the command line for phpcs accordingly.  It's a bit of a pain but that's what Vim offers. shrug
Anyway, this is all general Vim-fu that has nothing specific to syntastic.  Perhaps ask on a general Vim forum if you can't figure it out?


"New tag collected" when beaming data

Is it possible to prevent the phone to open the "New tag collected" screen? I think that this screen is provided by Samsung. I just searched if there is any way to disable it but anyone works for me.

Hi, @rogercoll , you're right about the 'new tag collected' view, it's an default Activity provided by Android when no other Activities intercept the NFC related intents.
To prevent the default view, you can simply call registerTagEvent (please refers to example/App.js in this repo) to signal that your app would like to handle the NFC intent, thus the default view wouldn't popup.

@whitedogg13 Hey, yes that was what I thought but I does not work. This is my code:
_onTagDiscovered = tag => {
        console.log('Tag Discovered', tag);
		let text = this._parseText(tag);
		let aux = JSON.parse(text);
		if(aux.name == this.state.whoamI){
			this._isok(aux);
			this.setState({texte: text});
		}
    }

	_startDetection = () => {
        NfcManager.registerTagEvent(this._onTagDiscovered)
            .then(result => {
				console.log('Read OK', result)
            })
            .catch(error => {
                console.warn('registerTagEvent fail', error)
            })
    }

Just call a NfcManager.registerTagEvent() to prevent Android to discover a tag.
Try to await NfcManager.registerTagEvent() and that is all

close due to no further activities


ci: implement ruff

Implement ruff linter and formatter in deeprank in lieu of prospector.
best reviewed one commit at a time:

set up ruff

replace prospector by ruff in CI
add ruff settings to pyproject.toml and remove .prospector.yml
format pyproj.toml

update docs regarding new linting/formatting
update settings.json for vs code

automatically flag linting issues and apply formatting upon save of python files
some additional settings

implement new linting and formatting throughout

this is a huge commit, basically touching the entire code base; probably not worthwhile reviewing in detail. In short

auto-format the entire code base (using ruff format .)
manually or automatically fix all linting issues flagged by ruff . (or suppressed)
remove pylint suppression calls
additional manual formatting to error messages to avoid them printing lots of whitespace/tabs when raised

remove all commented out code (linting issue ERA001), this part should be reviewed.

this was done in a separate commit to check that all deleted code is indeed legacy as opposed to accidentally being commented out
some commented out code may contain information that should be stored in a more appropriate manner

suppress some warnings during testing

I would like to get to the bottom of the warnings thrown during test_trainer, but that took too much time and will be for another issue.

format non-python files

using prettier for most file formats.

closes #541

Nice work :D I left very minor comments and seems all great. Three other things:

You used Prettier on non-python files, what about adding it as the default formatter for non-python files in the vscode settings? It would be even better to have ruff as the default for non-python files as well, but I think that ruff is for python files only, right?

Done in 7dc25266 (edited style: format non-python files)

I had a lower version of ruff (0.1.4 instead of the latest, 0.1.13) and it was giving me 4 errors when running ruff . from local. No errors with the updated ruff version. I'd add the version on the dependencies list in the toml file (ruff >= 0.1.13)

Done in b5767f6b (edited ci: set up ruff linter)

When I run ruff format ., I get the following warning:

The following rules may cause conflicts when used with the formatter: 'ISC001'. To avoid unexpected behavior, we recommend disabling these rules, either by removing them from the 'select' or 'extend-select' configuration, or adding them to the 'ignore' configuration.
86 files left unchanged

Maybe is a good idea to disable ISC001 adding it to the ignore configuration in the toml file?

This is because the format may put strings that are on sequential lines onto the same line but keeps them as two separate strings and this creates the linting issue you reference. I think we do want the formatter to do this and for the linter to pick it up.
I now added that linting issue to the "safe to fix" list (in b5767f6b), so that it automatically get fixed upon saving as well. Stupidly however, you need to save twice (first save will move the two strings onto one line, the second save will merge into a single string) for the full issue to resolve. Also, the warning persists and I haven't found a way to suppress it.


Improved dialog handling.

Coverage decreased (-0.09%) to 47.899% when pulling dac8c205c607d57f5db6628484edd8c7e2889e22 on critics into da9a09de19d7c78d737503c002b27851803d13dd on master.


WIP add some docs

Please don't merge yet, just getting started.

There seems to be no progress here?
ping @anp

Hi! I obviously haven’t had time to pick this back up, am happy to fix it up for merge if the amount here is valuable.

Hey @anp, I think we you're doing is valuable if you can pick this up pretty sure we can merge it. Unsure what you plan on adding exactly but remember that there's the Tutorial.

I think we should land whetever is good enough for now and if you later find more info you can open a new PR.

Hey, this information is very valuable but have you seen that there's some explanation for that variable already on the TUTORIAL.md file. Sorry for making you spend time on this, I'm just jumping here to help. I've just figured that your PR has more than 1 year, probably the TUTORIAL.md file was added later, unsure. Take a look if there's some way that you can fill your information and make it pair nicely with the TUTORIAL or if everything it's already said there we can just close this I guess.

Let’s give this a close then, no worries!


Classes no found

The below classes package not found in app
import com.nlptech.common.constant.Constants;
import com.nlptech.inputmethod.latin.SuggestedWords;
import com.nlptech.inputmethod.latin.utils.TypefaceUtils;

Which zengine edition is in build.gradle of your project？

My project using
implementation "com.nlptech.zengine:keyboardkernel:1.1.0" in build.gradle.

Please clean project and sync again,Maybe there is something wrong with downloading zengine.

@zainriaz If you are using command line to build the project, please use Gradle Wrapper. A higher version of local gradle may cause build failed on some occasion.

This issue is solved in the latest version.


Lower max requests of webseeds to real value

getPipelineLength adds 2 extra more requests possible to each wire. See L1303-L1305
In the case of a webseed, if it already has speed, let the webseed handle its real max requests.
This is merely a temporary attempt to make webseeds more stable and don't let them timeout
#650 is still on the works.

Released 0.83.0.


Allow Change of Icon Color

Enables the user to randomize a blogs icon color with a right click

Current coverage is 85.95%

Merging #91 into master will increase coverage by +0.55% as of 1b62917

@@            master     #91   diff @@
======================================
  Files           30      30
  Stmts          596     605     +9
  Branches         0       0
  Methods          0       0
======================================
+ Hit            509     520    +11
  Partial          0       0
+ Missed          87      85     -2

Review entire Coverage Diff as of 1b62917

Powered by Codecov. Updated on successful CI builds.


Update all references of vendor url https://adoptopenjdk.net/ to https://adoptium.net/

Description
Adoptium vendor url https://adoptium.net/ is available going forward we need to update AdoptOpenjdk vendor url  https://adoptopenjdk.net/ to Adoptium https://adoptium.net/
Tips to solve this particular issue:
To fix this issue, we need to replace https://adoptopenjdk.net/ with https://adoptium.net/ in the repo. Searching https://adoptopenjdk.net/ in the repo there are 7 matches, one is for build parameter, the other one  is for test, 5 others are documents related.
📋 Step by Step
To solve this issue and contribute a fix you should check the following step-by-step list. A more detailed documentation of the workflow can be found here.  Note: that you do not need to add yourself to a Contributors.md file as outlined in the detailed instructions.

[ ] Claim this issue: Comment below.
[ ]  Fork the repository in github by simply clicking the 'fork' button.
[ ]  Check out the forked repository
[ ]  Create a feature branch for the issue. We do not have any naming definition for branches.
[ ]  Commit your changes.
[ ]  Start a Pull Request.
[ ]  Done 👍 Ask in comments for a review :)
[ ]  If the reviewer find some missing pieces or a problem they will start a discussion with you and describe the next steps how the problem can be solved.
[ ]  You did it 🎉 We will merge the fix in the master branch.
[ ]  Thanks, thanks, thanks for being part of this project as an open source contributor ❤

🤔❓ Questions

Hi, i would like to work on this issue. Please assign me this.

a small doubt, 5 others are documents related. other 5 references are in README.md only right?

Hi, i would like to work on this issue. Please assign me this.

You're assigned 🙂

a small doubt, 5 others are documents related. other 5 references are in README.md only right?

There's a couple in other .md documents too https://github.com/AdoptOpenJDK/openjdk-build/search?q=https%3A%2F%2Fadoptopenjdk.net%2F


RecipeParser Read-Only Refactor

This PR contains two major refactors:

The RecipeParser class has been broken up into RecipeParser and RecipeReader
The load_recipe*() functions used in the unit tests have been reduced to load_recipe() using generics

RecipeParser has kept its original name as to not break library users. This change should not affect conda-recipe-manager callers.
This PR does not knowingly/intentionally contain any logic changes.
The RecipeReader is now the definitive base-class for all other Recipe Parsing calsses. It contains all the read-only functionality of RecipeParser. This was done for a few reasons:

Helps cut down the size of the RecipeParser class and unit test files
Increases separation of concerns
Allows callers to analyze recipe files without fear of having editing access
We can use RecipeReader to develop other parsing tools without worrying about the implications of editing access. It looks like we might add support for a Conda Build Configuration (CBC) Parser soon. That file format is close enough to the recipe format  that we want to utilize the parsing capability, but we don't want callers to edit CBC files like recipe files.

Here's a table I created to help me identify which functions needed to be moved.


[Technical Report] Resource Allocation Functions

Technical Report

simplicity: $s = n^{−r}$ where n is the complexity, and r a system parameter
greater than zero (defaulted to 0.5).
• directness: $d = b^{-t}$ where b is the length of the evidential base and, and t
a system parameter.
• Sharpness: $2 * |e - 0.5|$.
• projectedConfidence(): $c \times (t - t' + 1)^d$, where c is the confidence, t the
current time, t′ the creationTime of the truth-value, and d a system pa-
rameter indicating the decay rate (defaulted to 1000).
• Dividing term complexity (positive integer) in budgetInference() in (Bud-
getFunctions.java) is replaced by multiplying by simplicity (real number
in (0, 1])

More Info
We are missing the above functions which are needed to help us with resource allocation.
Simplicity (for Term), Directness, and Sharpness (for Sentences) are not mentioned in the code.
For projected confidence (for Events), a different formula is currently used (TemporalFunctions.py, def project())
For the Budget Inference point, see def Budget_inference()

Simplicity is added in PR #54

The rest are added in PR #54

You are right, its not bounded between (0,1). In ONA  it is a simply decay parameter < 1 (e.g., $d=0.99$) which is applied for each timestep that has passed. i.e., $d^{(t - t')}$

I will change it now

I will also update the technical document

@ccrock4t @bowen-xu should we bring this up in today’s meeting?

@maxeeem I don't think it is necessary, this is generally how we have agreed to project truth values in the past. But, it is not set in stone, meaning we can experiment with other formulas in the future (for example, Pei has suggested using a Logarithm of $t-t'$ to limit the rate of decay)

You are right, its not bounded between (0,1). In ONA  it is a simply decay parameter < 1 (e.g., d=0.99) which is applied for each timestep that has passed. i.e., c′=c∗d(t−t′)

$c^′=c∗d^{(t−t^′)}$ looks more reasonable.

Sorry I've been too busy recently. will review the changes asap.

I guess I’m coming from the perspective that since we’re changing the technical report, we should somehow make it explicit. This case sounds like a typo in the original report based on Bowen’s example., not just another possible formula.

I understand/agree, but which document is the original formula from? The latest conceptual design does not mention it.


Add a Gitter chat badge to README.md

fantasyland/fantasy-land now has a Chat Room on Gitter
@puffnfresh has just created a chat room. You can visit it here: https://gitter.im/fantasyland/fantasy-land.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Someone said we should give this a go. I'm in there!

With the discussions happening on PRs, I love this idea! :+1:

And it'll do IRC: https://irc.gitter.im/ merge this already :D


Copy of Fix the URL of Update an Item

Describe the bug
Update an Item in a Shopcart that uses the wrong Path in the URL.
We are using string:product_name and it should be int:item_id
Observe the 400 bad request response code
To Reproduce
Steps to reproduce the behavior:

Start the server with honcho start
Attempt to update the item's quantity.
Observe the 200 OK status as response code

Expected behavior
It should update an item in a shop cart.
Observed behavior
Our url for the update_item () is wrong. It should be int:item_id
Screenshots
Additional context

This is an duplicated issue


Rename default branch (master ➜ main)

Can we rename the default branch to main, just like many other popular projects, @jezdez?
I'd be ready to apply the necessary changes to the pipeline implementation.

Absolutely, say the word and I rename the branch.


Nvidia-Container-Cli Error: could not start driver service: load library failed: libnvidia-ml.so.1: cannot open

I ran into a nvidia-container-cli error (driver issue?) on the Jetson Nano (jetpack 4.5.1/arm64). Originally, I thought there was an error with nvidia_docker, but the problem only occurs when the nvidia runtime is invoked with docker.
Example: Docker
sudo docker run -it --rm --net=host --runtime nvidia  -e DISPLAY=$DISPLAY -v /tmp/.X11-unix/:/tmp/.X11-unix nvcr.io/nvidia/l4t-base:r32.4.4
Error:
docker: Error response from daemon: OCI runtime create failed: container_linux.go:367: starting container process caused: process_linux.go:495: container init caused: Running hook #0:: error running hook: exit status 1, stdout: , stderr: nvidia-container-cli: initialization error: driver error: failed to process request: unknown.
I ran a few diagnostics...
user@nano:~/Downloads/nvidia/sdkm_downloads$ nvidia-container-cli list --libraries
nvidia-container-cli: initialization error: driver error: failed to process request

user@nano:~/Downloads/nvidia/sdkm_downloads$ nvidia-container-cli -k -d /dev/tty info
-- WARNING, the following logs are for debugging purposes only --
I0416 03:07:42.835547 20727 nvc.c:372] initializing library context (version=1.3.3, build=bd9fc3f2b642345301cb2e23de07ec5386232317)
I0416 03:07:42.835653 20727 nvc.c:346] using root /
I0416 03:07:42.835674 20727 nvc.c:347] using ldcache /etc/ld.so.cache
I0416 03:07:42.835697 20727 nvc.c:348] using unprivileged user 1000:994
I0416 03:07:42.835769 20727 nvc.c:389] attempting to load dxcore to see if we are running under Windows Subsystem for Linux (WSL)
I0416 03:07:42.836068 20727 nvc.c:391] dxcore initialization failed, continuing assuming a non-WSL environment
W0416 03:07:42.836381 20727 nvc.c:254] failed to detect NVIDIA devices
W0416 03:07:42.836820 20728 nvc.c:269] failed to set inheritable capabilities
W0416 03:07:42.836886 20728 nvc.c:270] skipping kernel modules load due to failure
I0416 03:07:42.837351 20729 driver.c:101] starting driver service
E0416 03:07:42.837708 20729 driver.c:161] could not start driver service: load library failed: libnvidia-ml.so.1: cannot open shared object file: no such file or directory
I0416 03:07:42.837944 20727 driver.c:196] driver service terminated successfully
nvidia-container-cli: initialization error: driver error: failed to process request

Hi @kaisark. Jetson support for libnvidia-container is currently limited to a specific version due to how the platform differs from "standard" platforms in terms of drivers and libraries. Please ensure that you have the version that is included in JetPack installed instead of the version you mention.
We are working on ensuring that later versions of the NVIDIA container runtime can be used on multiple platforms, but we don't as yet have a clear date for when this may be ready.

There were some package version conflicts (apt package repository issue), so I uninstalled and reinstalled nvidia_docker (and related packages) and cleaned up the apt repository issues (disabled some of the auto updates/upgrades, etc). I essentially restored the Jetpack versions of the packages downloaded with nvidia's sdkmanager tool.
nvidia_docker and nvidia_container_cli are working again and I can run nvidia containers from nvidia's container catalog( https://ngc.nvidia.com).
Steps:

uninstall nvidia_docker2 (sudo apt remove nvidia_docker) - nvidia_container_toolkit and nvidia-container-runtime also removed in the process
sudo apt remove libnvidia-container1
sudo dpkg -i libnvidia-container-tools_0.9.0_beta.1_arm64.deb
sudo dpkg -i libnvidia-container-tools_0.9.0_beta.1_arm64.deb
sudo dpkg -i nvidia-container-toolkit_1.0.1-1_arm64.deb
sudo dpkg -i nvidia-container-runtime_3.1.0-1_arm64.deb
sudo dpkg -i nvidia-docker2_2.2.0-1_all.deb
restart docker (sudo systemctl restart docker)

I'll post the solution on the nvidia_docker git repository as well.

@kaisark we have recently released version 1.7.0-rc.1 of the NVIDIA Container Toolkit to our experimental repositories. The components of the NVIDIA container stack have been updated with better (packaging) support for Jetson.
If you install nvidia-docker2=2.8.0~rc.1-1 (which depends on nvidia-container-toolkit=1.7.0~rc.1-1) this should also work on your Jetson device.
Note that this will install both libnvidia-container0=0.9.0~beta.1 or libnvidia-container0=0.10.0+jetpack as well as libnvida-container1=1.7.0~rc.1-1, with libnvida-container-tools=1.7.0~rc.1-1 selecting the applicable library at runtime.
Since you mention that you were able to solve your problem, I'm closing this issue. Please feel free to reopen it or create a new one if something else comes up.

@kaisark the rc.1 packages have been promoted to GA and are available from our stable repositories.
See: https://github.com/NVIDIA/nvidia-container-toolkit/releases/tag/v1.7.0


famistudio: 4.2.1 -> 4.3.0

Release: https://github.com/BleuBleu/FamiStudio/releases/tag/4.3.0
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 366804

x86_64-linux

:white_check_mark: 1 package built:

famistudio


s3 providers

sems that https://github.com/aliyun/aliyun-oss-go-sdk is the only option ?
would be cool with ability to use any s3 provider. I think there are quite a few golang libs that can do this.

@gedw99 that part of code is only used for putting frontend files into CDN. It's optional. BTW are you using this project?

Hey @hsluoyz
thanks for the response. I am usibg it for similar purposes

Are you planning to make this more s3 agnostic ?

@gedw99 finally it will switch to use the provider: https://casdoor.org/docs/provider/storage/storage , can you make a PR for it?

@hsluoyz
I had a look and that link refers to the following code ?
https://github.com/casdoor/casdoor/blob/master/storage/storage.go
Which itself uses: https://github.com/casdoor/oss.

Closed as stale.


Support for plotly express

Hello - I really like this tool! Just wondering if it currently supports plotly express figures (specifically px.scatter). If not, is this in the roadmap for the near future?
Thanks!
Sam

Hey @sstripps1,
Can you elaborate some more on how you envision supporting plotly express figures? Perhaps your thoughts are in line with the comments of Apprehensive_Sun_420 in this reddit thread thread?
At the moment, we already support plotly express figures, as plotly-resampler can wrap any plotly Figure. See this code snippet for example;
import numpy as np
import plotly.express as px
from plotly_resampler import FigureResampler

x = np.arange(10_000)
noisy_sin = (3 + np.sin(x / 200) + np.random.randn(len(x)) / 10) * x / 1_000

fig = px.scatter(noisy_sin)
fig = FigureResampler(fig)  # wrap the plotly express figure
fig.show_dash(mode="inline")

One (significant) drawback is that we cannot use the hf_x and hf_y arguments in the plotly express interface. This is quite essential when visualizing very large sequential data (as you will otherwise suffer from the slow construction time from plotly graph_object constructors).
Cheers, @jvdd

Hey @jvdd, thanks for the quick response! My question was primarily in reference to the ability to use the hf_x and hf_y arguments (as is the case with Scattergl), so thanks for clarifying that.
I hadn't considered the case described by Apprehensive_Sun_420 but I would be interested in a feature like this as well - as little repetitive code as possible is always ideal :)

Should be fixed with #70, and #72, will be released with plotly-resampler 0.7.0 🔥

This is great, thank you so much @jonasvdd ! 🚀

Also major credits to @jvdd ! 🚀


[agents] New agent 'dispatch' for message routing

Implements #454
Summary:

this patch adds a new processor 'dispatch' that is able to dispatch the record to different topics depending on a condition

This is an example:
topics:
  - name: "input-topic"
    creation-mode: create-if-not-exists
  - name: "topic1"
    creation-mode: create-if-not-exists
  - name: "topic2"
    creation-mode: create-if-not-exists
  - name: "default-topic"
    creation-mode: create-if-not-exists
pipeline:
  - name: "Dispatch"
    type: "dispatch"
    input: input-topic
    output: default-topic
    id: step1
    configuration:
      routes:
         - when: properties.language == "en"
           destination: topic1
         - when: properties.language == "fr"
           destination: topic2
           action: dispatch
         - when: properties.language == "none"
           action: drop

Important notes:

the routes are evaluated in order, as soon as one condition is verified the message is sent to the destination and the processing stops
if no route matches then the record is sent to the "output", that can be a topic or another agent, as usual
for each route you can define an action: dispatch or drop, the default is "dispatch" that means to send the message, with "drop" the message is silently discarded (not emitted to the downstream agent)

@nicoloboschi I added support for "action: dispatch|drop" PTAL


Update/Unify release process and changelog management

The current release process is different for modules and applications, we should analyze if it's possible to make them more similar in order to avoid confusion. Moreover, there are two different changelog generators currently used.
github-changelog-generator used in Weacast, Krawler, KDK and derived applications creates a log file based on tags, issues and merged pull requests from :octocat: GitHub (so it cannot work with eg GitLab). It requires to install (e.g. for Windows) Ruby and its DevKit. Last but not least, it suffers from the following issue so you might have to edit the generated changelog when pushing on different branches or systematically merge changes to master before generating the changelog so that all issues are closed in Github.
generate-changelog used in Kaabah, Kargo and Krawler jobs creates a log file based on git commits (so it can work with eg GitLab). It does not require any third-party dependency. However it suffers from an issue so that if the commit message includes a URL it will break. Morevover, we did not test it with branches. Last but not least, it does not allow to integrate into the changelog issues that have been closed without any related commit (eg a bug appearing in an app and coming from the KDK dependency).
The following automated process applies when releasing a patch, minor or major version of a module using the first changelog (eg KDK):

increase the package version number in the package.json file
publish the module on the NPM registry
create a tag accordingly in the git repository and push it
generates the changelog in the git repository and push it

A different process applies for the apps as:

it is not published on the NPM registry but in the Docker Hub
it is far less automated to ensure more flexibility so that the build artifacts of the different flavors can be managed independently.

Imagine we are currently working on the next version of the app (1.2.0 in package.json =>1.2.0-dev image in Docker Hub) on the master branch:

start a new release by creating a test branch from the master branch (test-1.2 =>1.2.0-test image in Docker Hub)
increase the version number (major or minor) of the master branch so that the previously generated artifacts will not be erased by new commits (1.3.0 =>1.3.0-dev image in Docker Hub)
when you are ready to release create a tag on the test branch (prod-v1.2.0 =>1.2.0-prod image in Docker Hub) in the git repository and push it
generates the changelog in the git repository and push it
increase the version patch number of your test branch (1.2.1 in package.json =>1.2.1-test image in Docker Hub) so that the previously generated artifacts will not be erased by new commits entering pre-production

The following automated process applies when releasing a patch, minor or major version of a module using the second changelog (eg Kargo):

generates the changelog in the git repository and push it
increase the package version number in the package.json file
publish the module on the NPM registry
create a tag accordingly in the git repository and push it

The process used for the modules does not allow to manage multiple branches. Indeed, each commit on the master branch erases the latest tag on the Docker Hub while any tag generates a release (eg 1.2.0 tag).
We have tried to use a similar process for customer-specific applications based on Kano, eg GIFT. However, it is not really finished and causes some problems. First by erasing the previous image while committing on the next release, ie the version number remains eg 1.2.0 until the 1.3.0 release has been published so that the 1.2.0-dev image in Docker Hub actually contains the next 1.3.0 release code. Second because we assume that similar versions exist in dev/test flavor while patch versions only exist in test flavor.

A solution to be able to use a similar process between modules and apps is to avoid versioning dev/test Docker app images and only number prod images. Indeed, there is no need, in this case, to increment the version number on the master/test branch after a release as the previously generated artifacts (dev/test) will be erased anyway.
Test this process first on customer-specific applications based on Kano to ensure it works fine with branches.

About changelog we now use GitHub/GitLab issues to track changes in order to simplify the release process.

Since we we use Github/Gilabl track changes, we can close this issue


Doesn't load in the latest Obsidian Insider-build

I can install it to the Community Plugins in my vault but I cannot enable it. I'm on 0.12.10.

I haven't been able to recreate this with any of the release or insider builds that are in distribution at the moment.
I'm closing this for now but if you still have this issue please let me know!


iptables switch for docker

Statically disable iptables management for docker

Docker 1.13 changes the behaviour of iptables defaults from allow
to drop. This patch disables docker's iptables management as it was
in Docker 1.12 [1]

[1] https://github.com/docker/docker/pull/28257

ci check this


Does the client id need to be random?

No. The client ID must be unique to that device. You cannot have two clients connect with the same ID. Making it random is one convenient way to have the same sketch on multiple devices and not worry about giving each its own unique id.

Thanks. I am using esp8266 so all good as I can then use chip is.
On Sat, 24 Nov. 2018, 6:39 pm knolleary<EMAIL_ADDRESS>wrote:

No. The client ID must be unique to that device. You cannot have two
clients connect with the same ID. Making it random is one convenient way to
have the same sketch on multiple devices and not worry about giving each
its own unique id.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/knolleary/pubsubclient/issues/533#issuecomment-441351214,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABsMK7dSS3WH4bsiuepUxs0C1TRa-i_xks5uyP7PgaJpZM4YxTqw
.


Updating to remove admin Views related strings.

Updates #5200
What's this PR do?
This PR updates the extracted POT file for the dosomething_user module to remove strings that only apply to the Views admin interface.
Where should the reviewer start?
Double check the removed code.
What are the relevant tickets?
#5200

@angaither

:+1:


[model] address always evaluates to true (warning)

models.c:3425:59: warning: address of array
      'data->materials[i].pbr_metallic_roughness.base_color_factor' will always
      evaluate to 'true' [-Wpointer-bool-conversion]
            if (data->materials[i].pbr_metallic_roughness.base_color_factor)

Not really sure how to handle this to be sure, but it looks like it might not work as intended....

Hmm... kind of a strange warning. The data pointer is the gltf data parsed, so it shouldn't actually always be true.. but perhaps it shouldn't be evaluated that way. If that material didn't exist, then would it be "" or null?

Not really sure how to handle this to be sure, but it looks like it might not work as intended....

Remove the condition and run the if clause unconditionally.

Hmm... kind of a strange warning. The data pointer is the gltf data parsed, so it shouldn't actually always be true..

It's not about data, but about the .base_color_factor member that's an array and thus always unequal to NULL.

It's not about data, but about the .base_color_factor member that's an array and thus always unequal to NULL.
Which is exactly why I reported this issue this is likely not the intention ...

@chriscamacho Can you make a pull request?

no, I'm not sure of the intention of the code concerned.

@chriscamacho I'm working with the LoadGLTF function already, so don't worry about it :) It will be awhile before a pull request is out though.. My first goal is to fully support loading materials, since it only loads diffuse/albedo right now.

Just reviewed this detail.


Staking bust in rc16

Context
bee-v1.10.0-rc16-10f4fd1f-dirty.exe on goerli testnet
Summary
I staked with the following curl command:
curl -X POST http://localhost:1632/stake/101000000000000000
{"txhash":"0xddc15c39d97ec17559caa9f99a7be722fd05515f6c691d58efc324b6505a89db"}

But a subsequent stake query returns zero:
curl http://localhost:1632/stake
{"stakedAmount":"0"}

If you check the goerli transaction log at https://goerli.etherscan.io/tx/0xddc15c39d97ec17559caa9f99a7be722fd05515f6c691d58efc324b6505a89db
it is indeed a depositStake with the proper owner and amount:
Function: depositStake(address _owner,bytes32 nonce,uint256 amount) ***

MethodID: 0x1ed2cd40
[0]:<PHONE_NUMBER>00000000000000a5e44b91b4790fa21765a204024281e75569f224
[1]:  7f9df10400000000000000000000000000000000000000000000000000000000
[2]:<PHONE_NUMBER>000000000000000000000000000000000000000166d2f702508000

However, if you look at the third event log on that transaction:
https://goerli.etherscan.io/tx/0xddc15c39d97ec17559caa9f99a7be722fd05515f6c691d58efc324b6505a89db#eventlog
Address
[0x53968057779266f3bd57601ed4cee0e51ad8a012](https://goerli.etherscan.io/address/0x53968057779266f3bd57601ed4cee0e51ad8a012)
Topics
0 0x61e979698346a2aa868a3a9f08d30c846174841dc9b074bbf2a82d20554bc682
1 0xfbcbe9f9f19d38c82b40c6f6e0c67c92784691323a8522d6d548245252d9fd27
Data
0000000000000000000000000000000000000000000000000166d2f702508000
000000000000000000000000a5e44b91b4790fa21765a204024281e75569f224
00000000000000000000000000000000000000000000000000000000007c0727

And cross-reference that back to the definition of the StakeUpdated event from
  {
    "anonymous": false,
    "inputs": [
      {
        "indexed": true,
        "internalType": "bytes32",
        "name": "overlay",
        "type": "bytes32"
      },
      {
        "indexed": false,
        "internalType": "uint256",
        "name": "stakeAmount",
        "type": "uint256"
      },
      {
        "indexed": false,
        "internalType": "address",
        "name": "owner",
        "type": "address"
      },
      {
        "indexed": false,
        "internalType": "uint256",
        "name": "lastUpdatedBlock",
        "type": "uint256"
      }
    ],
    "name": "StakeUpdated",
    "type": "event"
  },

It would seem that the overlay being credited with the stake action is 0xfbcbe9f9f19d38c82b40c6f6e0c67c92784691323a8522d6d548245252d9fd27 which is NOT the overlay of the node that posted the stake, although the ethereum address definitely matches.
curl http://localhost:1632/addresses -s | jq
{
  "overlay": "86d7a00d43cbb9810b85031cb655ce073ab99acf78956520e0b287c847424249",
  "underlay": [
    "/ip4/<IP_ADDRESS>/tcp/1631/p2p/16Uiu2HAmUcvVUx4uDs91SLmnEZP9zqbVxqFDUvzuB4H87uz4PMYQ",
    "/ip4/<IP_ADDRESS>/tcp/1631/p2p/16Uiu2HAmUcvVUx4uDs91SLmnEZP9zqbVxqFDUvzuB4H87uz4PMYQ",
    "/ip6/2603:9001:8500:6500:ccbd:81d0:2046:e3cb/tcp/1631/p2p/16Uiu2HAmUcvVUx4uDs91SLmnEZP9zqbVxqFDUvzuB4H87uz4PMYQ",
    "/ip6/::1/tcp/1631/p2p/16Uiu2HAmUcvVUx4uDs91SLmnEZP9zqbVxqFDUvzuB4H87uz4PMYQ",
    "/ip4/<IP_ADDRESS>/tcp/1664/p2p/16Uiu2HAmUcvVUx4uDs91SLmnEZP9zqbVxqFDUvzuB4H87uz4PMYQ"
  ],
  "ethereum": "0xa5e44b91b4790fa21765a204024281e75569f224",
  "publicKey": "036025e455bcfb9c9ebea1454ef081fcb35a6e951185d0742aaa7fa5cc2295ee91",
  "pssPublicKey": "03995620c57d7c1d892ec51d8db6c7a54249ba158482fe554c821559d6594649a4"
}

Expected behavior
I expected the stake to show up.
Actual behavior
As you can see, the stake is still zero.
Steps to reproduce
If the ABI had been registered with the goerli blockchain explorer, I could probe further to see which overlay actually received the stake.
Possible solution

The constructor invocation of the previous staking contract had a network ID of 0xa.   The most recent staking contract constructor has a network ID of 0x5.
The network ID is the last bytes of the constructor input data and is used to translate the owner Ethereum address to an overlay address when staking.   This is causing the stake to go to the wrong overlay address, not the node's overlay.
Previous: https://goerli.etherscan.io/tx/0x4d945ae78ddc3a5e64da42605270a407f0cb1dd05629cdc5b7218db6a4b8a443
Newest: https://goerli.etherscan.io/tx/0x362c2ea6e772dcd68432f149dd3c83a480768e071c55d195f23198e492495a16


Can we have a section on how to customize the relative date range slicer to show Data ranges according to the Fiscal year and not the auto calendar year?

It by defaults uses jan 1st and dec 31st as start and end of year. Would be good to have a document that shows how to use Fiscal year to be displayed.
Thanks.

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

ID: ab98c7ec-c151-af65-c116-d03d6b2506a2
Version Independent ID: 8767e90e-0f08-0dc6-a52f-10298a6128b7
Content: Overview of report visualizations in Power BI service and Desktop - Power BI
Content Source: powerbi-docs/visuals/power-bi-report-visualizations.md
Service: powerbi
Sub-service: powerbi-service
GitHub Login: @mihart
Microsoft Alias: mihart

Hi, @dhruvinushah -- a useful idea. I'm assigning it to the author for consideration.
Thanks!

Hi @dhruvinushah ,
This has been added to our backlog. We will try to add this scenario to the slicer documentation the next time it is updated.


Added the option to play music and video? #132

Add Files via upload is the file which I have commented for music and video

Please update the main README.md and also have readme.md for each script that you include @CrypticRevenger

@DhanushNehru Please check the PR no. #178 where I have created the Readme.md file.
Thank you.

@DhanushNehru  Sir you have merged the Readme.md file of this PR. Can you please merge this PR.
Thank you


Can't update any mod

Whenever I tryin' to update mod from the download manager in game, it always failed.

duplicate of #90

Oh man, didn't notice.
Thanks alot


Fix typos in AzureEventSourceListener class description

Fixes a couple typos I noticed in the API reference page on docs.microsoft.com:

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


Unexpected skimage==0.0

First, thanks for the great tool!
I have
from skimage.util import random_noise
from skimage import morphology

in my code.
When I use pipreqs to generate requirements.txt, it genertates
scikit_image==0.14.2
skimage==0.0

scikit_image==0.14.2 is actually correct, while skimage==0.0 is not necessary I think.

Any updates on this? I see the same problem

same. print(skimage.__version__) shows me '0.14.1`

I just ran into this issue and had to remove the skimage==0.0 manually, any updates?

Problem still exists.

Still a problem, up.
Even adding a flag to filter output packages would be helpful, as a workaround.

Still an issue in pipreqs-0.4.11

Still a issue in 0.4.13 😕


Implement resourceContent query

Description
Implement query to retrieve content of a specific resource. This will be useful when the goal is to drill down into details of a specific resource, for example status and health details.
Acceptance Criteria:

[x] resource_content.go implements resourceContent graphql query
[x] resource_content_test.go provides required unit test coverage

GraphQL Query Details:
Example Query
query ($orgId: String!, $clusterId: String!, $resourceSelfLink: String!) {
  resourceContent(orgId: $orgId, clusterId: $clusterId, resourceSelfLink: $resourceSelfLink) {
      id
      content
  }
}

Defined Schema
  type ResourceContentObj{
    id: String!
    histId: String!
    content: String!
    updated: Date!
  }

In progress.

completed.


Add more species to term enrichment dropdown

Add more species to term enrichment dropdown from the reference supplied by @mugitty .
http://www.pantherdb.org/webservices/garuda/search.jsp?type=organism

Also fixed for geneontology.org.


test/netsim: expand netsim test with different NAT types

Also run rustfmt
Sorry the rustfmt changes are mixed in with the actual changes. I should have commited the actual changes first. The only actual change is to the netsim test for UDP sockets.

This has already made it into master somehow :/. Closing.


unable to load VQA model from json string

hi I am unable to load the model from json string. I am using keras 1.0.1 version.
I am getting KeyError: class_name

Hi Suraj
This was written in Keras 0.3.2 (the previous version). The new version of Keras (1.-+) changed the way it represents a model.
This means model built in older versions will not be loadable without some changes.
It seems they might add the legacy support to load old models, see this
https://github.com/fchollet/keras/blob/master/keras/models.py#L26
However, I will try to compile the model in newer version, but training will take time. Give me a day or two.
In the meantime you could easy have a alternate directory of older version of keras and use that to run this.

@suraj-deshmukh I have pushed the code which should work on Keras 1+


Build failed

Open folder in vs2022, wait cmake configuration, then select Chapter01_Triangle.exe to execute.

I'm also having the same issue. Did you find a solution for this?

@AmilaCG - See if this helps -> https://github.com/PacktPublishing/The-Modern-Vulkan-Cookbook/issues/11, otherwise we are connected on LinkedIn, feel free to message me there


Improve promql tracing

First, a bugfix - assigning to evaluator.ctx in eval() broke the parent-child relationship.
Pass the Context down through function calls instead.
Then, for aggregates, operators, calls, show what operation is performed.
Add a method ShortString() to keep the changes together with other AST printing code.
Also add a span when series are expanded, typically time spent accessing TSDB.
MatrixSelector nodes typically don't reach eval(), so this way they are covered.
Fixes #12099

Rebased and squashed some commits.


Parser does not respect default values

pub fn main() !void {
    var parser = toml.Parser(Watah).init(std.heap.page_allocator);
    var parsed = try parser.parseString(
        \\forsen = "abc"
    );

    std.debug.print("{s} {any}\n", .{ parsed.value.forsen, parsed.value.fdefault });
}

const Watah = struct {
    forsen: []const u8,
    fdefault: u8 = 2,
};

Even though fdefault has a default value of 2 here, the parser returns an error because it doesn't find it in the string:
> zig run src/main.zig
error: MissingRequiredField
D:\VSRepos\test\src\zig-toml\src\struct_mapping.zig:37:25: 0x7ff7eb4876a9 in intoStruct__anon_4214 (main.exe.obj)
                        return error.MissingRequiredField;
                        ^
D:\VSRepos\test\src\zig-toml\src\main.zig:98:17: 0x7ff7eb4888d8 in parseString (main.exe.obj)
                return err;
                ^
D:\VSRepos\test\src\main.zig:6:18: 0x7ff7eb488c65 in main (main.exe.obj)
    var parsed = try parser.parseString(

Good point 👍 I'll push a fix.

The default value in the struct does not seem to be used by the parser as a fallback value.

@yehuthi Could you submit a code snippet to get better insights? I added a test last time that addresses this issue. But maybe not all cases were covered 🤔

Ah, I see, the value is never checked in the test. I'll have a look. 👀

@yehuthi Indeed the issue was not fixed correctly. Now it should be. I added a test to check default struct values. Thanks for reporting. 👍


Unexpected Application Error! Cannot assign to read only property '0' of string 'python ./plex_debrid/main.py'

Describe the bug
TypeError: Cannot assign to read only property '0' of string 'python ./plex_debrid/main.py'
    at code (http://<IP_ADDRESS>:8083/assets/index-dc228d4a.js:204:14984)
    at RC (http://<IP_ADDRESS>:8083/assets/index-dc228d4a.js:38:19538)
    at AF (http://<IP_ADDRESS>:8083/assets/index-dc228d4a.js:40:44055)
    at kF (http://<IP_ADDRESS>:8083/assets/index-dc228d4a.js:40:39787)
    at pV (http://<IP_ADDRESS>:8083/assets/index-dc228d4a.js:40:39715)
    at wg (http://<IP_ADDRESS>:8083/assets/index-dc228d4a.js:40:39568)
    at y1 (http://<IP_ADDRESS>:8083/assets/index-dc228d4a.js:40:35933)
    at cR (http://<IP_ADDRESS>:8083/assets/index-dc228d4a.js:40:36737)
    at Oi (http://<IP_ADDRESS>:8083/assets/index-dc228d4a.js:38:3279)
    at http://<IP_ADDRESS>:8083/assets/index-dc228d4a.js:40:34263

Please describe your setup

[x] How did you install letta?

git clone memgpt , docker compose up

[x] Describe your setup

What's your OS (Windows/MacOS/Linux)?
How are you running letta? (docker in ubuntu )

Additional context
i downloaded "https://onedrive.live.com/view.aspx?resid=7B8BC7AAEBA7A500!61548&authkey=!AP1942sZUGKvNdU"
i added it in letta
i asked about how to install plex with zurg and then the error happend
Letta Config
Please attach your ~/.letta/config file or copy past it below.
where do  i find this using docker ?
If you're not using OpenAI, please provide additional information on your local LLM setup:
Local LLM details

[x] The exact model you're trying to use (qwen2.5:latest)
[x] The local LLM backend you are using (Ollama)
[x] Your hardware for the local LLM backend (local computer)

Where did you see the error? On the server logs, or on the browser?
I was able to upload you example into a data source and attach it to the agent's (the passages are in "Archival Memory")

Maybe there is an issue specific to Ollama. Can you double check that the archival memories are successfully attached? You can do this by viewing the agent in the ADE.

It was in the browser and i asked it to look and show the code
I had eveything in archival memory where around 38 passages and it worked like u did but when i asked code the error comes to the brozser and the agent becomes unusable


Latest hotfix breaks mod

This mod fails to compile with redscript on launch after today's hotfix patch. May be related to jackhumbert/mod_settings#12

Just updating to confirm that the mod is still broken, even with the resolution of
jackhumbert/mod_settings#12 (thanks for that update btw!).

I can also verify that this mod currently is not working.


Fixed few things in the code

I'll explain my additions in the code in a coming meeting

Please squash merge all of the commits as one, I have done all those above commits for my ease


Loner doesn't delete key in redis with some conditions

Hello,
we're using resque-loner and first of all Thank you for such a great product!
We're currently investigating, but looks like with some specific conditions as for now we found
just difference in Redis version 2.4.2 and 2.4.4 loner doesn't remove key after successful run.

Exactly!
We're using EngineYard on stagings we recently upgraded stack to 2.4.4 and it doesn't works.
On production we still have 2.4.2 and everything ok.

Looks like we found reason.
There was Redis 2.2.11 zombie process which caused this problem.
Thanks for attention!

@a-b hmmmmm, so the job was writing the loner key delete to another redis than it received it's job from?

Not sure, during investigation I found that redis-cli info return 2.2.11
Then I found that /etc/init.d/redis restart doesn't change pid
I double checked with sudo netstat -anp that clients connected to the same process.
Than I killed this zombie process and start redis again.
Now everything looks ok.

Strange situation but today we got the same situation on production, with working redis.

I'm having a similar situation. I reported it in #18, but feel free to merge my ticket with this one if it is the same underlying issue.

Ok looks like we figure out our issue: the reason is the different hashes. For the same object instance it:
deploy@ip-10-244-122-6 /data/plumdistrictcom/current $ tail -f log/staging.log|grep loner
Redis >> GET resque:loners:queue:critical:job:9fa60418c1cd879c8b5e06bb61c24a4a
Redis >> SET resque:loners:queue:critical:job:9fa60418c1cd879c8b5e06bb61c24a4a 1
Redis >> DEL resque:loners:queue:critical:job:03404ed9435a725bed8cb3a296a675ac
Redis >> GET resque:loners:queue:critical:job:b5f73ac16ba00b5683482752fe9502df
Redis >> GET resque:loners:queue:critical:job:9fa60418c1cd879c8b5e06bb61c24a4a
because we owerride self.redis_key

# key to identify job for resque-loner
def self.redis_key(payload)
  payload[:args] = job_identity_arguments(*(payload[:args] || payload["args"]))
  super(payload)
end

to be able to specify exact attributes hoe to determine uniqness

def self.job_identity_arguments(user_id, attributes = {}, *args)
  [user_id]
end

as result it produced

Redis >> RPUSH resque:queue:critical {"class":"MyClass","args":[415079,{"card_verifi
....
Redis >> SET resque:worker:alpha:1065:* {"payload":{"class":"MyClass","args":[415079],"args":[415079,{"billing_addre....

@a-b I'm not sure I see what you're talking about. Could you elaborate a bit more? Did you find a way around it?

@a-b so you're saying it had some arguments set with the same key, but as a symbol in the one case and a string in the other resulting in a json-represenation where the same key exists twice?

Exactly!

I will close this, continuning discussion in https://github.com/jayniz/resque-loner/issues/18


When running in antrea-agent in container(on ExternalNode), ANP with FQDN is not working as expected.

Describe the bug
When running antrea-agent/ovs as container on the VM(ExternalNode), we hit an issue where FQDN for maps.google.com was using Ipv6 address instead of Ipv4 address.
Configuration:

ANP policy configured with FQDN (maps.google.com) and action as REJECT.
On the container host, we had disabled Ipv6 by running the command(sysctl -w net.ipv6.conf.all.disable_ipv6=1)

To Reproduce
We hit this issue as part of the VM agent CI. Below is the testrun.
http://<IP_ADDRESS>:8080/job/antrea-vm-e2e-for-pull-request/169/console
Expected

Expect that curl to FQDN(maps.google.com) should be denied.

Actual behavior

Observed that curl to FQDN(maps.google.com) works, as it using Ipv6 address.

Versions:

Antrea version 1.9.

With sysctl -w net.ipv6.conf.all.disable_ipv6=1, none of the interfaces will have IPv6 addresses, how could it use IPv6 address to connect server?
Or the traffic test is done in non host netns? disable_ipv6 is per namespace conf, it may not be reflected in new netns.


Template binding bypasses element class get/set methods

Dart supports class get and set methods for customizing access to object properties. Polymer support template binding to tie object properties to the DOM. These two features should interact nicely, but instead Polymer's template binding appears to bypass Dart's property methods.
In particular, setting an object attribute via a Polymer template binding doesn't invoke the class's set method.
A minimal example:
@CustomTag('my-example-element')
class MyExampleElement extends PolymerElement {

    @published
    String get myExampleProperty => readValue(#myExampleProperty);

    set myExampleProperty(String newValue) {
        writeValue(#myExampleProperty, newValue);
        print('Property value changed!');
    }
}

Now, if we do:
$['id-of-an-instance-of-my-example-element'].myExampleProperty = 'foo';

Our setter gets called, the value of the property is updated in any template bindings, and the print() message in the setter shows up.
However, if instead we do:
<my-example-element myExampleProperty="foo"></my-example-element>

Then our setter is not called, and although the value of the property is updated in template bindings and in code within the Dart class that makes use of it, the print() in the setter isn't invoked.
Ideally, these two should be equivalent, and they should both go through the class's set method.

Thanks for opening this issue! Just to bring here some of the information we discussed by email:
The reason behind this is that when you create a binding in the HTML, we create a binding object. This binding object stores the current value represented by the element attribute (the template-binding system assigns values directly to it). The get/set pair pattern with readValue/writeValue are not the source of truth for the value of the binding. They instead connect to the binding object to retrieve the value when you access the property programatically.
With all the changes we saw in polymer.js 0.8, we have room for making bigger changes in the future. We should consider new design options in this space for polymer-dart that would make this less convoluted.

In the new polymer this is no longer an issue, everything goes through the normal getters/setters


F-strings doesn't contain bytes literal

Summary

Test Plan

Current dependencies on/for this PR:

main

PR #8675   👈

This stack of pull requests is managed by Graphite.


feat: default (runtime) Node.js version

🔗 Linked issue

Closes #2716
❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[x] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

A preset should accept the user's choice of Node.js runtime, as long as it is supported by the platform. In cases where the user's choice is not supported, or the user does not specify a runtime, a sensible default/fallback should be used.
Currently, the fallback is defined per preset. However, to ensure all deploy providers behave uniformly, we should define this globally at the Nitro level.
See https://github.com/unjs/nitro/pull/2654#discussion_r1746677267 for reference.
Methodology
To decide an appropriate fallback, we need to know two pieces of information:

Node versions supported by the platform
How to define a runtime from a node version

To do this, we can export a getDefaultNodeVersion utility which takes the supported Node versions as a set of numbers, and a function to convert the number to a runtime defintion. It then compared this to a globally set default. As Nitro is updated and newer Node features are used, this global can be increased to bump all presets.
Examples
const supportedNodeVersions = new Set([18, 20]);
const defineRuntime = (version) => `nodejs-${version}`;

const default = getDefaultNodeVersion(supportedNodeVersions, defineRuntime);

const supportedNodeVersions = new Set([16, 18, 20]);
const default = getDefaultNodeVersion(supportedNodeVersions, String);

Considerations
This utility should consider the case where the Nitro default is not supported by the platform yet.
The documentation for preset authors should be updated to only list GA node versions in supportedNodeVersions.
📝 Checklist

[x] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

Hi @pi0 I have written up my idea and implemented it into a couple of presets. Before I continue and implement it into others, I thought it would be wise to seek some feedbadk.
What do you think of the idea? Do you think the utilities and constants are located in the right places? Is there anything else you would like me to consider?


Cherry-picks for the 4.0 branch (future 4.0.3) - 5th batch

Final batch before building 4.0.3-stable.

Two previous cherry-pick have been reverted.

https://github.com/godotengine/godot/pull/71670 required further changes, which aren't safe for a patch release.
https://github.com/godotengine/godot/pull/64388 causes a regression which needs to be fixed, so it's better to err on the side of caution and give it a bit more time to be tested in master.

Several documentation changes and very safe fixes (including crashes) added.
Changelog should be up to date.
Still needs a version bump ahead of starting the build 🙃

Godot-cpp was updated to match #76406

We probably need this change in the 4.0 branch:
diff --git a/.github/workflows/linux_builds.yml b/.github/workflows/linux_builds.yml
index 44765ee32e..9ef0e731c9 100644
--- a/.github/workflows/linux_builds.yml
+++ b/.github/workflows/linux_builds.yml
@@ -5,7 +5,7 @@ on:
 # Global Settings
 env:
   # Only used for the cache key. Increment version to force clean build.
-  GODOT_BASE_BRANCH: master
+  GODOT_BASE_BRANCH: 4.0
   SCONSFLAGS: verbose=yes warnings=extra werror=yes module_text_server_fb_enabled=yes
   DOTNET_NOLOGO: true
   DOTNET_CLI_TELEMETRY_OPTOUT: true
@@ -182,6 +182,7 @@ jobs:
         uses: actions/checkout@v3
         with:
           repository: godotengine/godot-cpp
+          ref: ${{ env.GODOT_BASE_BRANCH }}
           submodules: 'recursive'
           path: 'godot-cpp'

And only the second part in the master branch, for consistency.

Yeah, I just arrived to the same conclusion. Will add a commit.

I made a PR as other files needed a fix too: #77204. But feel free to include that commit directly in this PR and supersede mine.

Ah, then I'll just merge and rebase 👍 Thanks!

Thanks!


Have websocket connections been forgotten about?

Currently the docs for setting up a websocket rpc connection state to whitelist an rpc origin, but there is no way to do that in your application settings.
The Discord client seems to check for rpc_origins in the app's json when you connect, but I can't find any way to set them on my app. So all sockets get closed due to having an invalid origin.

I realize that RPC used to be whitelisted through the Gamebridge program but that seems to have disappeared as it's a 404 now. Since anyone can use IPC, is WSS just lost forever?
I don't know if I'm misinformed or if I missed an update, but any info on getting Web-socket connections working would be useful.
Thanks for reading

Looks like this comment is still valid. https://github.com/discordapp/discord-rpc/issues/192#issuecomment-395514108

Charlotte is correct. WebSocket connections are not currently supported for interfacing with Discord for Rich Presence functionality; you'll need to use IPC or RPC. We removed the GameBridge marketing material a while ago, as it's since been deprecated.
If you have a local application, connecting via RPC shouldn't be an issue. However, if you're trying to do something like connecting from a browser, it will fail. We've whitelisted the Rich Presence commands over RPC/IPC to not require auth, but they do require you to not have an origin header, as we don't want arbitrary websites opening connections to Discord.


Updating process document

Re-submitting the process document update from a few months ago.

Closing this for now, as there's enough already on my plate and things seem to be moving smoothly.


Migrating the FINOS-hosted instance of Legend Studio

Dear Legend data modeling community,
Following the success and increased demand for collaboration on the FINOS hosted instance of Legend Studio, we’re migrating the CDM, Product Control Common Template, Commodity Reference Data, and Currency Reference Data projects and models that are currently in our GitLab hosted instance (gitlab.legend.finos.org) to gitlab.com/finosfoundation/legend on August 10th, 2021.
Why are we migrating to GitLab.com?
This migration is part of the Legend roadmap, and represents the final maturity step for the Legend SDLC component (now compatible with the latest version of GitLab public APIs!) and for the FINOS hosted instance infrastructure. The migration will not only facilitate the onboarding of any existing gitlab.com user, but more importantly, it will allow us to leverage our partnership with GitLab to provide a more stable and resilient environment to host Legend models.
What are we asking from you?
If you wish to continue accessing any of the CDM, Product Control Common Template, Commodity Reference Data, and/or Currency Reference Data projects and models that are currently hosted on the FINOS-hosted shared instance of Legend Studio, please follow the below steps by Friday, July 23rd, which should take no more than 2 minutes of your time:

If you do not have a GitLab account: Sign up for a GitLab account

If you already have a GitLab account OR once you have created one (see step 1): email<EMAIL_ADDRESS>with (i) your GitLab username and (ii) the projects you’d like to get access to, so that we can restore your entitlements.

What are the practical implications of the migration?
Project lead maintainers will be able to access the projects and models throughout the migration process and the commit history will be preserved. Main projects will also be migrated and preserved.
However personal/scratch projects will not be migrated or preserved. If you have created any private/scratch projects you would like to preserve, please make sure to back them up/ recreate them by August 10th.
Questions?
If you have questions, the Legend team will be available to answer them at the Q&A section of the upcoming Legend Community meetings on July 27th "Legend 101” and July 29th “Legend Deep Dive”. Meeting details for these sessions are available at finos.org/hosted-events and on the FINOS Community calendar. For any other questions, please email<EMAIL_ADDRESS>Thanks,
The Legend and FINOS teams

Thank you to everyone who has submitted their GitLab usernames, FINOS will restore your access to the CDM, Product Control Common Template, Commodity Reference Data, and Currency Reference Data projects and models on or after August 11th, 2021.
For anyone else who would like to get access to the FINOS-hosted shared instance of Legend Studio, please submit a request at finos.org/legend


Split mt, add snps_not_on_gnomad

Add a metric: number of SNPs not in gnomad (snps_not_on_gnomad)
Move VQSR reference files to an Australian bucket.
Write the final mt table with multiallelics split, and GT instead of LGT field. The reason is that the VQSR annotations are also per-allele, so annotation only works properly with a split mt.
Refactor the evaluation against the truth data.

FYI @KatalinaBobowik, @tiboloic, @pdiakumis about the final table having GT instead of LGT now.

FYI @KatalinaBobowik, @tiboloic, @pdiakumis about the final table having GT instead of LGT now.

Thanks for the FYI @vladsaveliev!


bg/LWMIOPEN-189 : use DataInvokeParams for non-fused solver

Address https://github.com/ROCmSoftwarePlatform/MIOpen/issues/2239

I can confirm that this PR resolves #2239

[R] @bghimireamd Maybe it is worth renaming this. Like in C++ comments, I recommend explaining why we are doing this, not what or how we are doing (because the latter should be clear from the diff). Proposal: "Fix tuning of legacy OCL solvers (resolves issue #2239)". Up to you.

[Attribution] @junliume

https://github.com/ROCmSoftwarePlatform/MIOpen/labels/urgency_blocker
https://github.com/ROCmSoftwarePlatform/MIOpen/labels/bug
Proposed reviewer: @DrizztDoUrden


Write test to check again escaped html

current test
def test_page_content_is_markup_safe(self, page_with_content_path):

        # TODO: Write Test with Markup data
        assert page_with_content_path.content == Markup(page_with_content_path.html)

This isn't really testing anything

News tests will be built in next update


fix: Fix missing bash function in allocate.sh script

Changes

fix: Fix missing bash function in allocate.sh script

/cc @lkingland
Release Note

NONE

Thanks for the quick fixup!
/lgtm
/approve


Support deinit_existential_addr

Issue #98

Empty node is now returned. But I think we should wait until #106 merged, as the new organization might be messed up

@bryantam, could you please resolve the conflicts now after merging Mark's PR?

It's ready now

Hmm, it still shows some conflicts :S That’s a bit weird, given that the other PR didn’t have any merge conflict issues when I just approved it moments ago. Could you please resolve this one as well?
Thanks!


Unify default window size on all platforms

Prob make them consistent with windows.

This also demonstrates the issue!
https://www.youtube.com/watch?v=cpAmJuYZYKo&feature=youtu.be


Status and Events for Istio CRDs

This work item tracks the progress of
Istio Config: Status Field Requirements
https://docs.google.com/document/d/1kS1X5GYVyxx1_yuMsi96eZ0u7UXc8M1FugFpt7fT6zM/edit?ts=5d24b8a2
Istio Config: Validation Approach
https://docs.google.com/document/d/1Ag0H7BAsAcW8BeIArQ57bX3U0rLc1cKwN1B5oVRN1Yw/edit
@ozevren @rvennam

@ozevren Should we move this to 1.4?

I am assigning this to @sushicw as he has been ramping up on this area.

https://github.com/istio/istio/pull/16350 has a lot of the groundwork for this.

https://github.com/istio/istio/pull/17360 adds this into master.
Closing this issue, https://github.com/istio/istio/issues/882 is still open and tracks this area more comprehensively.


Move service classes into sub-directories / namespaces

Most of the service classes are only used in a single controller, but all the services were in a single directory and it was hard to see just the services used by a single controller.
This PR moves all of the service classes into sub-directories / namespaces based on the model class which they manipulate. Initially I used the controller name prefixes for the sub-directory names, but that didn't feel quite right. I also contemplated getting rid of the Service class name suffix on all the service classes, but I thought that made the code a bit harder to read/understand.
I'm not 100% sure the way I've done it is ideal, but I do think it's an improvement having the service classes in separate directories like this.

I also loaded these changes in development to make sure the autoloading was working.

@chrislo: Thanks for reviewing. I'll get it merged shortly.