An empty default value for the macro argument is not supported in all simulators

Some versions of questasim can't compile the project and return the following error:
** Error: ** while parsing file included at /home/user/Projects/ibex/vendor/google_riscv-dv/src/riscv_instr_pkg.sv(1373)
** at /home/user/Projects/ibex/vendor/google_riscv-dv/src/riscv_pmp_cfg.sv(204): (vlog-2266) Expansion of macro 'DV_CHECK' failed: The number of actual arguments (4) are not equal to the number of formal arguments (5).

This error is caused by the empty default value of argument WITH_C_ in macros DV_CHECK and DV_CHECK_FATAL.
`define DV_CHECK(T_, MSG_="", SEV_=error, ID_=`gfn, WITH_C_=) \
...
`define DV_CHECK_FATAL(T_, MSG_="", ID_=`gfn, WITH_C_=) \

The issue can be solved by replacing the empty value with "&& 1".
`define DV_CHECK(T_, MSG_="", SEV_=error, ID_=`gfn, WITH_C_=&& 1) \
...
`define DV_CHECK_FATAL(T_, MSG_="", ID_=`gfn, WITH_C_=&& 1) \

The proposed solution is more universal in terms of simulators support.

Thanks for posting the solution. I was having the same compile error. After adopting the changes, I ran into this error.
** Error: (vlog-13069) ** while parsing file included at /home/asicfab/a/socet06/riscv-dv/src/riscv_instr_pkg.sv(21)
** at /home/asicfab/a/socet06/riscv-dv/src/dv_defines.svh(37): near "if": syntax error, unexpected if, expecting class.


exit status 1: 'C:\Users\Konrad' is not recognized as an internal or external command, operable program or batch file.

My Environment

[x] Windows 10
[x] My Windows installation is non-English.

I'm using NVM4W version:

[x] 1.1.7

I have already...

[x] read the README to be aware of npm gotchas & antivirus issues.
[ ] reviewed the wiki to make sure my issue hasn't already been resolved.
[ ] verified I'm using an account with administrative privileges.
[ ] searched the issues (open and closed) to make sure this isn't a duplicate.
[ ] made sure this isn't a question about how to use NVM for Windows, since gitter is used for questions and comments.

My issue is related to (check only those which apply):

[ ] settings.txt
[ ] proxy support (Have you tried version 1.1.0+?)
[ ] 32 or 64 bit support (Have you tried version 1.1.3+?)
[ ] Character escaping (Have you tried version 1.1.6+?)
[x] A standard shell environment (terminal/powershell)
[ ] A non-standard shell environment (Cmder, Hyper, Cygwin, git)

Expected Behavior
Change node version.
Actual Behavior
exit status 1: 'C:\Users\Konrad' is not recognized as an internal or external command,
operable program or batch file.
It spited my user folder in half by space.
Steps to reproduce the problem:
nvm use 11.1.0

yep, seems like your user folder cannot contain whitespaces.

I see the same problem

Oh I was going to write this earlier but I forgot. You can actually edit config file to use DOS path convention (you can find correct short directory name with dir /x command) and theoretically easiest fix would be to create config using this convention in the first place, but this sounds more like hiding a bug than fixing it.

I would expect nvw-windows to works on windows by default.

same problem +1

thanks @Mourdraug it worked !
Open Cmd, go to the Users directory, type dir /x and you will see the shortened version of the name of the users. (ALEXKA~1 in my case)
Inside the nvm installation (AppData\Roaming\nmv in my case) there is a settings file, edit the first line and instead of having the space name put that shortened version and leave the rest the same like this :
root: C:\Users\ALEXKA~1\AppData\Roaming\nvm

This is fixed in master. I just haven't had time to cut a release of 1.1.8.

If you used scoop to install nvm, the directory for the settings.txt is

If you used scoop to install nvm, the directory for the settings.txt file is
C:\Users\John Doe\scoop\persist\nvm\settings.txt

Intsalled in C:/Program Files/.. couldn't find a workaround to get it working so far...

Hi, i just encountered the same issue on a Windows 10 system... i suspected that the user root path string parser can't deal with a space anywhere in the root path name... so i gave it the 7.3  DOS user path name instead as suggested above... J52B0~1.CLA in our case, and that indeed worked just fine, thanks.

Yep, that's still issue, 1.1.8 isn't out yet ie. the proper fix is still laying somewhere in commit log waiting for the next release. Until then, workaround mentioned above should do the job.

Still broken - spaces in file paths have been a thing for quite a while now!

thanks @Mourdraug it worked !
Open Cmd, go to the Users directory, type dir /x and you will see the shortened version of the name of the users. (ALEXKA~1 in my case)
Inside the nvm installation (AppData\Roaming\nmv in my case) there is a settings file, edit the first line and instead of having the space name put that shortened version and leave the rest the same like this :
root: C:\Users\ALEXKA~1\AppData\Roaming\nvm

C:\Users\ ABHISH~1\AppData\Roaming\nvm could not be found or does not exist. Exiting.
node v11.0.0 (64-bit) is not installed.
It's now showing this error

1] In cmd go to the home directory (User in my case)  Run "dir /x"
2] Find the short name for your directory (In my case Suyash Savji = SAVJIS~1)
3] Go to C:\Users"Home File"\AppData\Roaming\nvm
4] Open settings.txt file and replace the home file name with the short name(In my case, Suaysh Savji :: SAVJIS~1 )
5] In cmd go to the version file installed eg. v11.0.0 and then run "nvm use 11.0.0"

1] In cmd go to the home directory (User in my case)  Run "dir /x"
2] Find the short name for your directory (In my case Suyash Savji = SAVJIS~1)
3] Go to "C:\Users"Home File"\AppData\Roaming\nvm"
4] Open settings.txt file and replace the home file name with the short name(In my case, Suaysh Savji :: SAVJIS~1 )
5] In cmd go to the version file installed eg. v11.0.0 and then run "nvm use 11.0.0"

1] In cmd go to the home directory (User in my case)  Run "dir /x"
2] Find the short name for your directory (In my case Suyash Savji = SAVJIS ~~ 1)
3] Go to C:\Users"Home File"\AppData\Roaming\nvm
4] Open settings.txt file and replace the home file name with the short name(In my case, Suaysh Savji :: SAVJIS~~1 )
5] In cmd go to the version file installed eg. v11.0.0 and then run "nvm use 11.0.0"

Great ! Follox the 5 steps, and it's working

Real big thank you for the solution !

thank you so much this is really helpful

1] In cmd go to the home directory (User in my case) Run "dir /x"
2] Find the short name for your directory (In my case Suyash Savji = SAVJIS ~~ 1)
3] Go to C:\Users"Home File"\AppData\Roaming\nvm
4] Open settings.txt file and replace the home file name with the short name(In my case, Suaysh Savji :: SAVJIS~~1 )
5] In cmd go to the version file installed eg. v11.0.0 and then run "nvm use 11.0.0"

where to find short name of our directory

tl;dr
Solved!!
For someone who is not able to work with ~1 method by @kirkouimet  (Thanks mate) in  #41
Open CMD go to the Users folder and Get the Shortened Folder name.
and type
> dir\x

Now later after copying or Noting down the folder name

Hope it helps

I have to say that fixing this problem manually by the user isn't a fix at all for me.
Windows can have spaces in folders names and many users have this (because of microsoft account) by default.
The fix should be provided in the nvm itself by developers not by the users who want to use it on their end.

@savjisuyash-code Thank you so much. it worked...!

@Swarag-N , thanks for the screenshots

Thank you so much for this

I DONT have any shortened user name what should i do??

I DONT have any shortened user name what should i do??

I DONT have any shortened user name what should i do??

i am also facing the same problem

It didn't work for me...didn't get any shortened user name

It didn't work for me because I am not getting shortened name for my user

Faced the same issue and resolved it using these help

thanks @Mourdraug it worked !
Open Cmd, go to the Users directory, type dir /x and you will see the shortened version of the name of the users. (ALEXKA~1 in my case)
Inside the nvm installation (AppData\Roaming\nmv in my case) there is a settings file, edit the first line and instead of having the space name put that shortened version and leave the rest the same like this :
root: C:\Users\ALEXKA~1\AppData\Roaming\nvm

this worked for me. thank you so much!

This is fixed in master. I just haven't had time to cut a release of 1.1.8.

So coming up on 2 years and the download installer is still 1.1.7...  I get that this is free software (and I'm sure it will be VERY USEFUL once I get it working), but just out of curiosity, how long IS your development cycle?  ;)

Still broken as of Dec/2020

Hi, i just encountered the same issue on a Windows 10 system... i suspected that the user root path string parser can't deal with a space anywhere in the root path name... so i gave it the 7.3 DOS user path name instead as suggested above... J52B0~1.CLA in our case, and that indeed worked just fine, thanks.

How did you do this?

Hi, i just encountered the same issue on a Windows 10 system... i suspected that the user root path string parser can't deal with a space anywhere in the root path name... so i gave it the 7.3 DOS user path name instead as suggested above... J52B0~1.CLA in our case, and that indeed worked just fine, thanks.

How did you do this?

thanks @Mourdraug it worked !
Open Cmd, go to the Users directory, type dir /x and you will see the shortened version of the name of the users. (ALEXKA~1 in my case)
Inside the nvm installation (AppData\Roaming\nmv in my case) there is a settings file, edit the first line and instead of having the space name put that shortened version and leave the rest the same like this :
root: C:\Users\ALEXKA~1\AppData\Roaming\nvm

this worked for me. thank you so much! Especially given that doing everything else would take more time. this is awesomeeeeee

How did you do this?

thanks @Mourdraug it worked !
Open Cmd, go to the Users directory, type dir /x and you will see the shortened version of the name of the users. (ALEXKA~1 in my case)
Inside the nvm installation (AppData\Roaming\nmv in my case) there is a settings file, edit the first line and instead of having the space name put that shortened version and leave the rest the same like this :
root: C:\Users\ALEXKA~1\AppData\Roaming\nvm

this worked for me. thank you so much! Especially given that doing everything else would take more time. this is awesomeeeeee

How did you do this?

thanks @Mourdraug it worked !
Open Cmd, go to the Users directory, type dir /x and you will see the shortened version of the name of the users. (ALEXKA~1 in my case)
Inside the nvm installation (AppData\Roaming\nmv in my case) there is a settings file, edit the first line and instead of having the space name put that shortened version and leave the rest the same like this :
root: C:\Users\ALEXKA~1\AppData\Roaming\nvm

Thanks@Mourdraug it really solved the issue

1] In cmd go to the home directory (User in my case) Run "dir /x"
2] Find the short name for your directory (In my case Suyash Savji = SAVJIS ~~ 1)
3] Go to C:\Users"Home File"\AppData\Roaming\nvm
4] Open settings.txt file and replace the home file name with the short name(In my case, Suaysh Savji :: SAVJIS~~1 )
5] In cmd go to the version file installed eg. v11.0.0 and then run "nvm use 11.0.0"

I followed the 5 steps and solve the issues. Thank you!

thanks @Mourdraug it worked !
Open Cmd, go to the Users directory, type dir /x and you will see the shortened version of the name of the users. (ALEXKA~1 in my case)
Inside the nvm installation (AppData\Roaming\nmv in my case) there is a settings file, edit the first line and instead of having the space name put that shortened version and leave the rest the same like this :
root: C:\Users\ALEXKA~1\AppData\Roaming\nvm

Thanks... you save my time. 🥇

1] In cmd go to the home directory (User in my case) Run "dir /x"
2] Find the short name for your directory (In my case Suyash Savji = SAVJIS ~~ 1)
3] Go to C:\Users"Home File"\AppData\Roaming\nvm
4] Open settings.txt file and replace the home file name with the short name(In my case, Suaysh Savji :: SAVJIS~~1 )
5] In cmd go to the version file installed eg. v11.0.0 and then run "nvm use 11.0.0"

worked for me, thanks ....
. you saved my time

I DONT have any shortened user name what should i do??

tl;dr
Solved!!
For someone who is not able to work with ~1 method by @kirkouimet (Thanks mate) in #41
Open CMD go to the Users folder and Get the Shortened Folder name.
and type
> dir\x

Now later after copying or Noting down the folder name

Hope it helps

Thank you so much

thanks @Mourdraug it worked !
Open Cmd, go to the Users directory, type dir /x and you will see the shortened version of the name of the users. (ALEXKA~1 in my case)
Inside the nvm installation (AppData\Roaming\nmv in my case) there is a settings file, edit the first line and instead of having the space name put that shortened version and leave the rest the same like this :
root: C:\Users\ALEXKA~1\AppData\Roaming\nvm

thanks is fixed my problem

Spaces are now supported in https://github.com/coreybutler/nvm-windows/releases/tag/1.1.8

Finally 🌟 , thank you very much 😄

thanks @Mourdraug it worked !
Open Cmd, go to the Users directory, type dir /x and you will see the shortened version of the name of the users. (ALEXKA~1 in my case) Inside the nvm installation (AppData\Roaming\nmv in my case) there is a settings file, edit the first line and instead of having the space name put that shortened version and leave the rest the same like this : root: C:\Users\ALEXKA~1\AppData\Roaming\nvm

worked well for me.

Facing the same issue

@savjisuyash-code  Real big thank you for the solution !

Still broken as of Mar/2023.

Still broken as of Mar/2023.

Still having this issue in 1.1.10

Thank it really solved the issue!!

thanks @Mourdraug it worked !
Open Cmd, go to the Users directory, type dir /x and you will see the shortened version of the name of the users. (ALEXKA~1 in my case) Inside the nvm installation (AppData\Roaming\nmv in my case) there is a settings file, edit the first line and instead of having the space name put that shortened version and leave the rest the same like this : root: C:\Users\ALEXKA~1\AppData\Roaming\nvm

@alexkar13 , thx man , you saved my day .

Thanks , this helped me achieving it.

Important information for the short name solution: dir /x  does not work in Power Shell, it NEEDS to be in the simple command prompt.

1] In cmd go to the home directory (User in my case) Run "dir /x" 2] Find the short name for your directory (In my case Suyash Savji = SAVJIS ~~ 1) 3] Go to C:\Users"Home File"\AppData\Roaming\nvm 4] Open settings.txt file and replace the home file name with the short name(In my case, Suaysh Savji :: SAVJIS~~1 ) 5] In cmd go to the version file installed eg. v11.0.0 and then run "nvm use 11.0.0"

This worked.
thanks


ISSUE 40

MCQA 42 question

please merge the pull request

@naitikraj12935 any update on this? please let me know if you need any help. I can help you by making the changes if you are facing any issues

I make a pull request again.so review it.
On Fri, 2 Jun 2023, 18:40 Kiran Dash, @.***> wrote:

@naitikraj12935 https://github.com/naitikraj12935 any update on this?
please let me know if you need any help. I can help you by making the
changes if you are facing any issues
—
Reply to this email directly, view it on GitHub
https://github.com/bgwebagency/who-wants-to-be-a-javascriptaire/pull/48#issuecomment-1573710704,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A3QBO7SWFGUPKF34LZWNTGDXJHQ2VANCNFSM6AAAAAAYR7UFTI
.
You are receiving this because you were mentioned.Message ID:
@.***
com>


improving consistency with let vs const

Using let everywhere is pretty confusing and obfuscates where its actually needed, it also tends to be better in JS to use === wherever possible.
I've tested locally and was looking out for any cases where the original used ==/!= that changing could've changed the behaviour, but as far as I can see, I'm not aware of any edge cases this comes into play.

Thank you for your contribution, though what this plugin really needs is a complete rewrite using Igor instead of GMAssetCompiler.
I do not generally use const (or final in languages that use that) for local variables unless something absolutely shouldn't be touched and cannot realistically promise that future code here will be held to such a high standard, especially since all of my ongoing work to update this plugin is like trying to repair a hole in a ship's hull with adhesive tape - it is but a matter of time until it completely falls apart.
As for changing == to ===, that is not a good idea and is not worth what little performance benefit it might offer. Without running the code, I can tell you that this will break error reporting because obj[missing key] will yield undefined and not null.
As for changing '"' for "\"", that's just an extra backslash for nothing, isn't it? The two are identical by spec.

Thank you for your contribution, though what this plugin really needs is a complete rewrite using Igor instead of GMAssetCompiler.
I do not generally use const (or final in languages that use that) for local variables unless something absolutely shouldn't be touched and cannot realistically promise that future code here will be held to such a high standard, especially since all of my ongoing work to update this plugin is like trying to repair a hole in a ship's hull with adhesive tape - it is but a matter of time until it completely falls apart.
As for changing == to ===, that is not a good idea and is not worth what little performance benefit it might offer. Without running the code, I can tell you that this will break error reporting because obj[missing key] will yield undefined and not null.

Fair enough, this PR overall was a lot of going in and changing it to what felt more readable myself. As for GMAssetCompiler, I was actually pretty curious if there was a specific reason for that, as using Igor took me just a minute to get running and doing the same thing from the commandline.
I'd be interested in making a completely new plugin serving the same purpose built around Igor instead, from what I've seen something basic that can do that doesn't seem overly complicated.

Igor takes environment variables (desired platform, project directory, settings, and so on) and invokes GMAssetCompiler while handling all of the related setup (like calling pre-build/post-build scripts, managing temp directories, and so on).
For example, adding YYC support to builder is a struggle, but with Igor that'd be one extra flag (IIRC).

Another interesting thing on builder I've noticed is it displays the "Made with GameMaker" splash, Igor's build did not (by default, I'd assume).

I've never seen a splash on my end when using builder so that's just another example of why doing it this way is not a good idea


deployment fails using coreos and flatcart , ignition profile is corrupted

Description
after doing terrafom apply the matchbox getting to start the ipxe and on the config step it stuck with
msg="warning parsing Ignition: " on the matchbox logs
and the flatcart linux
failed to fetch config: unable to parse 2.x ignition unsupported
same issue with coreos
Steps to Reproduce
just try to deploy baremetal using latest versions (2 latest)
Expected behavior
the pxe should bootstrap the whole cluster
Environment

Platform: bare-metal
OS: fedora-coreos, flatcar-linux - both "38.20230709.3.0" and "3510.2.6"
Release: Typhoon version 1.27.4 and 1.27.1
Terraform: terraform version v1.5.5
Plugins: Provider plugin versions "0.5.2" and "0.13.0"

Possible Solution
need to check the butane creator library. something there is strange
/ipxe?uuid=56bdc751-1a03-4374-b8c7-60727333366a&mac=96-8d-dc-28-05-69&domain=localdomain&hostname=&serial=
the ipxe don't have hostname and no serial which can cause the issue but i don't know typhoon code enough to clarify it

In my case, the matchbox on k3s causes the problem. I had deployed matchbox on k3s and it appeared to work well for serving HTTP API , except for /ignition. However, when I switched deployment method from k3s to docker, /ignition now returns the full content and typhoon works well. I hope this will help.

I think @westelh is on the right track. The error message you're seeing would correspond to using an old Matchbox version that doesn't understand Ignition v3. Typhoon hasn't used Ignition 2.x since v1.24.2 in Aug 2022.
I suspect you're running into a change to Flatcar Linux support for v1.24.2 (Aug 2022) https://github.com/poseidon/typhoon/blob/main/CHANGES.md#v1244
Since v1.24.2, Typhoon uses Butane Configs to define Flatcar Linux controller and worker nodes configurations (Ignition spec v3.3). This required Flatcar Linux 3185.0.0+ (which first added support for spec v3) and poseidon/ct v1.11+. On bare-metal, this also relies on Matchbox being able to render Ignition v3.3, which was added in Matchbox v0.10.0 https://github.com/poseidon/matchbox/releases/tag/v0.10.0
failed to fetch config: unable to parse 2.x ignition unsupported

It's also possible that Flatcar Linux itself will drop support for 2.x Ignition soon, but since you're seeing the error from Matchbox it would be caused by using an older Matchbox version.

I installed matchbox on vm .
And I used new enough flatcar and core os as per manual and it still didn't work.
I ended just moving to Ubuntu minimal with microk8s and all working good , using cloud-init as bootstrap and not butane

I've hit the same issue and found the root cause (for my case, YMMV):
poseidon/terraform-provider-ct@v0.13.0(latest) will generate Ignition v3.4.0 configs but those aren't supported by<EMAIL_ADDRESS>(latest).
Matchbox doesn't have validation for the write path and instead validates the ignition configs on read. Unfortunately Matchbox uses ignition v3.3.0 during read, which fails for any v3.4.0 configs.

Matchbox v0.11.0 is released

@dghubble mind pushing the TF provider release to the terraform registry? :pray:


Large characters rendered overlapping on PDF.js in Firefox 82

Example pdf: https://www.mass.gov/doc/covid-19-dashboard-october-25-2020/download -- and most of the previous versions (https://www.mass.gov/info-details/archive-of-covid-19-cases-in-massachusetts) as well
Configuration:

Web browser and its version: Firefox v82.0
Operating system and its version: Windows 10
PDF.js version: whatever's bundled with Firefox
Is a browser extension: no

Steps to reproduce the problem:

View pages 18 or 20 of the PDF for examples

Actual results:

Expected results (in Chrome):

Fixed by the PR above.

Wow, that's an unexpected root cause!  Thanks for the quick fix :)

Yes, it's quite surprising, especially since we would expect this to have been reported more often given how long this code already exists. Fortunately it seems to be very rare to trigger in practice, but this PDF file managed to do so. Thank you for reporting it so it could be fixed!


Dark Mode?

There is not an issue, but what about a feature to enable light mode vs dark mode?  basically white background vs black background?
thanks for all you do

Having user-pickable colors would be best :) I've seen many dark modes that (IMHO) were unusable because of the color choices (straight black, weird combos of grays, etc.)

Either way but light/dark modes until full features are still cool.

I've created a pull request for a dark theme (themes in general) implementation.  #146

:+1:


[SPARK-12926][SQL] SQLContext to display warning message when non-sql configs are being set

Users unknowingly try to set core Spark configs in SQLContext but later realise that it didn't work. eg. sqlContext.sql("SET spark.shuffle.memoryFraction=0.4"). This PR adds a warning message when such operations are done.

Can one of the admins verify this patch?

Thanks for working this!  I'm worried that throwing an exception could break existing applications (i.e. I know for a fact that spark-sql-perf uses the conf for its own options).  What about changing this to a warning?

@marmbrus : Makes sense. I have updated the diff with your suggestion.

ping !!

ok to test

Test build #50008 has started for PR 10849 at commit 7f1e317.

Test build #50008 has finished for PR 10849 at commit 7f1e317.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/50008/
Test FAILed.

Fixed scala style test

Test build #50082 has started for PR 10849 at commit f982d54.

Test build #50082 has finished for PR 10849 at commit f982d54.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/50082/
Test PASSed.

ping !!

Please update the title and description (these become the commit message when merging).

@marmbrus : Updated the title and description.

Thanks, merging to master.

Thanks, merged to master.


Add tf.util.range()

Compatible with np.arange().
Fixes https://github.com/tensorflow/tfjs/issues/1049

This change is

@nsthorat Yes. As I commented in the issue https://github.com/tensorflow/tfjs/issues/1049, I think a method like this will still be useful, because tf.range() returns a tensor, not an array of numbers. It's cumbersome to get an uniformly spaced array of numbers by using a tensor method, because the it'd be necessary to call data() or dataSync() and do memory management.

Maybe a Generator instead of an Array output might be worth considering:
function* range( start, end, step ) {
  // ...
  for( let i=0; i < end; i+=step )
    yield i
}

This way, less memory is used and it can still easily be converted into an Array using [...tf.range(start,end,step) ].

@DirkToewe I like that idea. I think we should support both an array return type and a generator return type The former is easier to use and just works for smallish problems. The latter scales up well. How about I make the signature of the function like  function range(start, end, step, isGenerator = false)?

To be honest I wouldn't worry about memory consumption too much on the CPU. Let's cross that bridge if we find this to be a problem in practice. At the end of the day you're likely to store that as a TypedArray anyways.
Also, one more question, what are you going to use this for? Maybe return a TypedArray so that this is much faster?

Not sure if the question is directed at me or @caisq. Personally,I'm probably not gonna use it since I would rather use either itertools or something like Float32Array.from({length: 1337}, (_,i) => 10*i). In Python, range is used as way more idiomatic replacement of the awful C-style for(;;) loop which is prone to terrible and sometimes hilarious mistakes.
for( const i of tf.arange(100) )
for( const j of tf.arange(100) )
  // ...

Is way more idiomatic than:
for( let i=0; i < 100; i++ )
for( let j=0; j < 100; i++ )
  // ...

(I hid an bug in the for(;;) loop just to point out how problematic it is)
If that is what @caisq had in mind, using a generator would be preferrable (Python first introduced xrange and then changed range to a generator in Python 3 because creating a list, everytime range() is called, turned out to be a memory and performance issue).

Gentle ping on this -- going through all the tfjs-core PRs.

Gentle ping, what's going on with this?

The use case isn't super clear. Closing this PR for now.


Providing a 5-minute setup process

I will provide a 5-minute setup process.  This involves adding scripts to the source code, and I will be documenting the steps here for my reference.

No pg setup: "PG::ConnectionBad: fe_sendauth: no password supplied"

cp config/database.yml.example config/database.yml, configure PostgreSQL for more open settings:
PG::ConnectionBad: FATAL:  Peer authentication failed for user "postgres"

Resolved the peer authentication failure with the command "sudo /etc/init.d/postgresql reload" and then by creating the databases.  The new issue:
StandardError: Directly inheriting from ActiveRecord::Migration is not supported. Please specify the Rails release the migration was written for

Entered the following command to update the migration scripts:
grep -rl "ActiveRecord::Migration$" db | xargs sed -i 's/ActiveRecord::Migration/ActiveRecord::Migration[4.2]/g'

Getting the following message when I enter "rails db:migrate":
Directly inheriting from ActiveRecord::Migration is not supported. Please specify the Rails release the migration was written for

I understand that I'm supposed to add "[4.2]" right after the "< ActiveRecord::Migration" in the migration scripts, but I have some questions:

Why do I get this message when you don't?
I recently upgraded a project to Rails 5.1 (https://github.com/OpenTwinCities/adopt-a-tree), but it doesn't demand that I make that modification to each of the migration scripts.  So why would it be necessary for some Rails apps with Rails 5.1 but not for others?

Do you want me to make the change to each database migration script?

If I do make the demanded changes in the database migration spec, I get "error [object Arguments]" when I run the integration tests.

Object argument errors are in spec/features/interest_gathering_spec.rb

Resolved or added to my personal branch


error! helper: symbol to JSON conversion

Hi,
In 0.11.0:
error! :unauthorized, 401

Was returned as:
{ "error": "unauthorized" }

In 0.12.0 I get:
""unauthorized""

Does anyone else experience this?

Something is going on with either the error format or with what is being returned in a handled error. Read through https://github.com/intridea/grape/blob/master/UPGRADING.md carefully in case there's a clear answer (there're some things around errors), and if that doesn't help put up a project where this is reproduced?

I found nothing relevant in the upgrading documentation. I'll try to reproduce it in a small project.

@dblock see https://github.com/ruby-grape/grape/blob/master/lib/grape/error_formatter/json.rb#L8
result = message.is_a?(String) ? { error: message } : message

I believe this is resolved via #1216 and some left-overs in #1309. Closing. Please reopen or add comments to #1309.


Not all tokens are being indexed

I have the following setup:
    records = [
      {
        id: 1,
        title: 'Test 1',
        description: 'It is her couch',
        url: 'www.example.com',
        tags: 'a,b,c'
      },
      {
        id: 2,
        title: 'Test 2',
        description: "The couch is her's",
        url: 'www.sample.com',
        tags: 'x,y,z'
      }
    ];

    const idx = lunr(function () {
      this.ref('id');
      this.field('title', { boost: 100 });
      this.field('description');
      this.field('tags');
      this.field('url');

      this.pipeline.remove(lunr.stemmer);
      this.searchPipeline.remove(lunr.stemmer);

      for (const record of records) {
        const tunedRecord = {
          ...record,
          description: record.description,
          tags: record.tags.split(','),
          url: record.url.split(/\W+/)
        };

        this.add(tunedRecord);
      }
    });

The resulting invertedIndex is:

Notice that her's (from record 2) was indexed, but her (from record 1) was not.
The same happens if I remove record 2. A single record with the word her does not get indexed.
Is there a trick to this or is this a bug?
FYI: I have found other similar occurrences.

I ran into this too and realized what was going on
see #480
basically, there's a default pipeline "stopWordFilter" that filters out a set of small words (including "her" or in my case "get"). If you want to include those, just remove the pipeline
config.searchPipeline.remove(lunr.stopWordFilter)

cheers!

I thin my point is that the stopWordFilter is where the bug is


'helm list' doesn't seem to filter by user

$ helm registry list -u ant31 quay.io
<full list of repos instead of just ant31's>

@gtaylor you can use the -o;
helm registry list -o ant31 quay.io

but from you suggestion we will replace that on the next release by
helm registry list quay.io/ant31

the -u isn't implemented on quay.io.
It should show all repositories a user have explicitly access to (at least read permission) include privates if the request-user have perm too.

It doesn't seem to list all repositories that I may have access to.  I created a few public application repositories but they do not appear in the list.
helm registry list quay.io|grep venezia
returns nothing

@venezia are you sure they are public. By default it's private and you need to set it to public.
helm registry list quay.io   without option returns only the 'first' page, it the future it will probably be ordered by 'highlight' or number of downloads.
You can use:
helm registry list quay.io --search
Not that private repo are never returned yet.

You're right - it is a private repo issue.  Thanks.  Will private repos eventually be surfaced?

@ant31 How do I see private repos?  Related... how would I make a repo public?

@ryanwalls

You can't 'list' private repos yet
make a repo public:  the command is missing

By default apps are private on quay.io, to switch you can go on quay.io in the setting tab of your application

@ant31 Thanks for the clarification.  To further clarify, there is no way to see what private repos you have, even from the quay.io UI?

@ryanwalls I was speaking from the CLI, also those features (in the cli) will be added
On quay.io you can see all your private/public repo:  on the page https://quay.io/application/


Issue with DTEND

Hey, I have been using this plugin and things have been great, but I am getting this error randomly today and I am hoping you can help resolve this:
parsestring.js:98 Uncaught (in promise) Error: Unknown RRULE property 'DTEND'

Everything looks right in my CMS:

Hi @wuebkers,
I just answered your support question on Wordpress.org.
It looks like you're using a Javascript library that does not support the DTEND property (I would guess this one?)
This incompatibility with the rrule.js library must have been introduced by this change. It looks like this changed has never been tagged until several months later in v1.3.0. I will have to take a deeper look at it to understand why it has been introduced. In the meantime can you try to roll back to v1.2.5?

I just removed the DTEND attribute from the generated RRULE string which appeared to be completely unnecessary. The RRULE string already contains the UNTIL attribute with the exact same value.
In order to ensure backwards compatibility with previous versions of the plugin where DTEND attribute was not implemented, the attribute is automatically removed from the string if it exists in database (see here).
Latest release v1.3.4 has been pushed to packagist.org and Wordpress plugin repository 🚀


Webstorm live template to create a component

Thanks for the contributions. Can you help get some folks to review this?
I dont use WebStorm, so before we merge it I want to make sure it's up to date.
Perhaps some of the folks from webstorm team , even

Hi @jacobwarduk! Thanks for you PR. I've noticed that it's missing a comma in the line with templateUrl.

Thanks for pointing this out @prigara, it has been fixed.

@prigara as part of the WebStorm team, could you give this a quick review to see if we can get it merged into the repo please?
Kind regards, Jacob.

@jacobwarduk hey, Jacob! Tried it in WebStorm 2017.3, works fine for me!
@johnpapa can you please merge it? Thank you!

done
and thank you all!


Issue deleting tasks with identical tags

I have found that if several tasks are submitted with a given tag, deleting a single task via the API deletes all of the tasks.
Appears to be an issue with the unique constraint on the tags.names column and the bi-directional relationships between the tasks, tasks_tags and tags tables as defined in database.py.
Adding two samples with tag 'a':
curl -F<EMAIL_ADDRESS>--form_string "tags=a" http://server/tasks/create/file
curl -F<EMAIL_ADDRESS>--form_string "tags=a" http://server/tasks/create/file
sees the following in the DB tables:
tasks
id=1, target=sample.exe
id=2, target=sample.exe
tasks_tags
task_id=1, tag_id=1
task_id=2, tag_id=1
tags
id=1, name=a
Then issuing 'curl http://server/tasks/delete/1', both tasks 1 and 2 are deleted and I am left with:
tasks
tasks_tags
tags
Both tasks have been deleted despite only requesting task 1 to be deleted.
The proposed change addresses the issue.

Very interesting issue. I'll have to confirm the bug later, thanks.

This sounds like a cascading delete issue. I'm not sure if the right approach is to create multiple tags with the same name (which might hamper searching, and is the point of tasks_tags "joing" table) vs. resolving the issue that deleting a task also deletes tags associated with that task, even if there are other tasks using the same tag.

I'd certainly be interested to know if there is an alternate solution that maintains the uniqueness in the tags table.
Perhaps @jekil has some thoughts given he authored that part of the DB schema?

I have done some more testing of this and found a solution that addresses the initial bug but still maintains the uniqueness on the tags table.  Any orphaned tags are automatically cleaned up once they are no longer referenced by any machines or tasks.
This is based off the example provided here:
http://stackoverflow.com/questions/9234082/setting-delete-orphan-on-sqlalchemy-relationship-causes-assertionerror-this-att/9264556#9264556

I've recently run into the same issue. Given this issue is around tags though I'd be in favour of getting rid of the whole cascade="all, delete" at all - in practice there are only, at the very most a few dozen tags anyway.
Getting rid of it also fixes this issue. Thoughts?

I believe that will work OK as well.  It just means that every time a user submits a task and typos the tag or uses a non-existent tag, it will end up left in the tags table.  That was why I proposed the event listener to clean up any orphans along the way.

Sorry for the delay. I've just committed the patch that I proposed upstream. In this case I prefer simplicity over relatively complex logic with the event listeners etc.
Anyway, closing this issue as it is resolved for me. Please re-open or create a new issue if you're still experiencing issues.. :)


When would websocket.remote_address be None?

I have a simple chat server, in onSocket method I cache the websocket object for later use. At sometimes later, websocket.remote_address become None (The websocket object is still present, e.g <websockets.server.WebSocketServerProtocol object at 0x7efcdcaefeb8)
So when would this attribute be None?

Not 100% sure, but I think remote_address becomes None once the connection is closed. Is that what you're seeing?
If so, it's a documentation bug.

Looks like that way. It became None when self.transport is None

I'd like to update the docstring to reflect this.


Remove erroneous comma for multiple actions

I only tested postgresql.

I will merge this PR when work on tests refactoring will be finished


redux-form doesn't work with immutablejs

I went through the example code and found that redux-form doesn't work with redux-immutable or redux-immutablejs as shown in the docs. I don't even think all of the props are being passed to the form. For example, formKey is undefined. I copy/pasted the examples to try to get it working below. I created a super minimalist app to test this out at this repo. Hitting the reset button dispatches an action but the state doesn't get changed. pristine is still set to false and the changed values are still in the form.
import React from 'react'
import ReactDOM from 'react-dom'
import {Router, Route, browserHistory } from 'react-router'
import {Provider} from 'react-redux'
import {createStore} from 'redux';
import {reducer as formReducer} from 'redux-form';
import {reduxForm} from 'redux-form';
import { combineReducers } from 'redux-immutablejs';
import Immutable from 'immutable';

export const reducer = combineReducers({
  form: (state = Immutable.fromJS({}), action) => Immutable.fromJS(formReducer(state.toJS(), action))  // <--- IMPORTANT PART
});

const store = createStore(reducer, Immutable.Map());

class ContactForm extends React.Component {
  render() {
    const {fields: {firstName, lastName, email}, handleSubmit, resetForm} = this.props;

    const _this = this
    const reset = () => {
      resetForm()
      console.log(_this.props)
    }
    return (
      <form onSubmit={handleSubmit}>

          First Name
          <input type="text" placeholder="First Name" {...firstName}/>

          Last Name
          <input type="text" placeholder="Last Name" {...lastName}/>

          Email
          <input type="email" placeholder="Email" {...email}/>

        <button type="submit">Submit</button>

        <button type="button" onClick={reset}>Reset</button>
      </form>
    );
  }
}

ContactForm = reduxForm({ // <----- THIS IS THE IMPORTANT PART!
  form: 'contact',                           // a unique name for this form
  fields: ['firstName', 'lastName', 'email'], // all the fields in your form
  getFormState: (state, reduxMountPoint) => state.get(reduxMountPoint).toJS()
})(ContactForm);

ReactDOM.render((
<Provider store={store}>
    <Router history={browserHistory}>
    	<Route path="/" component={ContactForm}/>
    </Router>
  </Provider>
), document.getElementById('app'));

If you want to use ImmutableJS, I would highly recommend upgrading to v6, which has built in  ImmutableJS support.

ah ok cool, thanks

ah ok, cool. Thanks. Wasn't sure how ready v6 is.

Gonna close this since I'm not going to debug the problem in v5. Others are welcome to, though.


SDL2 backend

Agar currently has SDL 1.2 backend. I think you choose it because SDL 1.2 is more portable than the new SDL2 but it's no longer to be the case. SDL2 now available from Windows to Linux, BSDs, SunOS and even HaikuOS. It's pretty stable now.
What do you think about a SDL2 backend?

Yes, the addition of a standard SDL2 driver is definitely one of the top items planned for the upcoming 1.7 release (https://github.com/JulNadeauCA/libagar/blob/master/CHANGELOG.md#unreleased).
The code that needs to be ported is in drv_sdl_common.c, drv_sdlfb.c and drv_sdlgl.c.  The main difference will be that SDL2 being multi-window, the SDL2 driver class will be derived from AG_DriverMw as opposed to AG_DriverSw.


Support Compression in parquet-fromcsv

Which issue does this PR close?

Closes #3721
Rationale for this change

What changes are included in this PR?

Are there any user-facing changes?
add new arg for parquet-fromcsv : -C/--csv-commoression

Looking good thank you, only thing left I think is some feature flag shenanigans
I believe running with cargo run --bin parquet-from-csv --no-default-features --features arrow,cli will result in compilation errors now

thanks, I'll fix this soon


Web3Modal vanilla js example demo is broken when trying to login with metamask from pc.

Try to go to https://web3modal.github.io/web3modal-vanilla-js-example/ and login from PC using metamask after you just reopened the browser or if it is the first time you connect. It won't let you, giving the following errors:
Unchecked runtime.lastError: The message port closed before a response was received.
Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
If you close and reopen the page however (and weirdly enough if the console is open, but not sure if this is just a weird correlation) then the login will work perfectly.
This error seems to occur if you close your browser after logging in, then reopen the browser and try to login again, but only with metamask on PC (so it seems).
May anyone fix this? It's confusing my users a lot
Do this to replicate the error:
go to the demo from pc, login using the metamask option. close your browser. reopen the browser and try to login again from pc using the metamask option. it won't work.

anyone?

With stable version 2.0.0 of Web3Modal now released, we are officially dropping support for version 1.x
Due to this this issue/pr was marked for closing. It is highly recommended to upgrade as 2.x will be receiving further updates that will enable functionality for some of our newer sdks like auth and push as well as support for WalletConnect v2 (See this post about WalletConnect v1 being deprecated https://medium.com/walletconnect/walletconnect-v1-0-sunset-notice-and-migration-schedule-8af9d3720d2e)
If you need to continue using Web3Modal 1.x and require this feature/fix implemented, we suggest adding it via forking V1 branch.


Add multi-source support

This PR adds support for generating URLs across multiple imgix sources.
Multiple sources can be specified through the following configuration:
imgix:
  sources:  # imgix source-secure_url_token key-value pairs.
    assets.imgix.net: FACEBEEF12
    assets2.imgix.net:            # Will generate unsigned URLs
  default_source: assets.imgix.net  # (optional) specify a default source for generating URLs.

and used in the following manner:

This is a completely backwards compatible change.

Ran into this exact issue today! Would love to see this merged

Hey @smithtimmytim sorry for the very delayed response here. Multi-source support is now available via v1.2.0 🎉


Unable to successfully run "amplify init"

For Section II of the demo, "Amplify Setup", I'm not able to get past step 6 (initialise your project).
I followed directions exactly, except that the method for getting access keys has changed since the demo was published. When I attempt to initialise my project I get the following output:

E:\AWS\react-amplify>amplify init --debug
Note: It is recommended to run this command from the root of your app directory
? Enter a name for the project reactamplify
The following configuration will be applied:
Project information
| Name: reactamplify
| Environment: dev
| Default editor: Visual Studio Code
| App type: javascript
| Javascript framework: react
| Source Directory Path: src
| Distribution Directory Path: build
| Build Command: npm.cmd run-script build
| Start Command: npm.cmd run-script start
? Initialize the project with the above configuration? No
? Enter a name for the environment dev
? Choose your default editor: Sublime Text
√ Choose the type of app that you're building · javascript
Please tell us about your project
? What javascript framework are you using react
? Source Directory Path:  src
? Distribution Directory Path: build
? Build Command:  npm.cmd run-script build
? Start Command: npm.cmd run-script start
Using default provider  awscloudformation
? Select the authentication method you want to use: AWS profile
For more information on AWS Profiles, see:
https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-profiles.html
? Please choose the profile you want to use default
🛑 We are unable to process your request. Please reach out to your support representative.
Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/
ProjectInitFault: We are unable to process your request. Please reach out to your support representative.
at init (C:\snapshot\amplify-cli\build\node_modules@aws-amplify\amplify-provider-awscloudformation\lib\amplify-service-manager.js:163:13)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Object.run (C:\snapshot\amplify-cli\build\node_modules@aws-amplify\amplify-provider-awscloudformation\lib\initializer.js:96:9)
We are unable to process your request. Please reach out to your support representative.
UnauthorizedException: We are unable to process your request. Please reach out to your support representative.
at Object.extractError (C:\snapshot\amplify-cli\build\node_modules\aws-sdk\lib\protocol\json.js:80:27)
at Request.extractError (C:\snapshot\amplify-cli\build\node_modules\aws-sdk\lib\protocol\rest_json.js:61:8)
at Request.callListeners (C:\snapshot\amplify-cli\build\node_modules\aws-sdk\lib\sequential_executor.js:106:20)
at Request.emit (C:\snapshot\amplify-cli\build\node_modules\aws-sdk\lib\sequential_executor.js:78:10)
at Request.emit (C:\snapshot\amplify-cli\build\node_modules\aws-sdk\lib\request.js:686:14)
at Request.transition (C:\snapshot\amplify-cli\build\node_modules\aws-sdk\lib\request.js:22:10)
at AcceptorStateMachine.runTo (C:\snapshot\amplify-cli\build\node_modules\aws-sdk\lib\state_machine.js:14:12)
at C:\snapshot\amplify-cli\build\node_modules\aws-sdk\lib\state_machine.js:26:10
at Request. (C:\snapshot\amplify-cli\build\node_modules\aws-sdk\lib\request.js:38:9)
at Request. (C:\snapshot\amplify-cli\build\node_modules\aws-sdk\lib\request.js:688:12)
at Request.callListeners (C:\snapshot\amplify-cli\build\node_modules\aws-sdk\lib\sequential_executor.js:116:18)
at Request.emit (C:\snapshot\amplify-cli\build\node_modules\aws-sdk\lib\sequential_executor.js:78:10)
at Request.emit (C:\snapshot\amplify-cli\build\node_modules\aws-sdk\lib\request.js:686:14)
at Request.transition (C:\snapshot\amplify-cli\build\node_modules\aws-sdk\lib\request.js:22:10)
at AcceptorStateMachine.runTo (C:\snapshot\amplify-cli\build\node_modules\aws-sdk\lib\state_machine.js:14:12)
at C:\snapshot\amplify-cli\build\node_modules\aws-sdk\lib\state_machine.js:26:10
at Request. (C:\snapshot\amplify-cli\build\node_modules\aws-sdk\lib\request.js:38:9)
at Request. (C:\snapshot\amplify-cli\build\node_modules\aws-sdk\lib\request.js:688:12)
at Request.callListeners (C:\snapshot\amplify-cli\build\node_modules\aws-sdk\lib\sequential_executor.js:116:18)
at callNextListener (C:\snapshot\amplify-cli\build\node_modules\aws-sdk\lib\sequential_executor.js:96:12)
at IncomingMessage.onEnd (C:\snapshot\amplify-cli\build\node_modules\aws-sdk\lib\event_listeners.js:417:13)
at IncomingMessage.emit (node:events:525:35)
at IncomingMessage.emit (node:domain:489:12)
at endReadableNT (node:internal/streams/readable:1359:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Session Identifier: 095ed2b4-4ea8-440c-a8b6-5c1edbe3eeeb

You'll notice the name of the app differs from the demo as I've tried the process a number of times with different names for the app. I've also tried reinstalling the AWS CLI, installing both version 1 and version 2 in case there was a breaking change.
I've also added a second profile just to make sure that wasn't the issue, but I still get the same error.
Any help with this issue would be much appreciated! Thanks!

It turns out that it was an account issue. I'll close this issue - cheers!


A malform AndroidManifest file

Describe what actually happened
Androguard parse failed with this malform AndroidManifest.xml file.
ApkInspector parse OK
System Information
Malform_AndroidManifest.zip.txt

Androguard Version: master
Python Version: 3.9.7
Operating System: Windows 10

@HongThatCong thank you for reporting this. Would it be possible to share this apk as well please? You can use a service like https://tria.ge/

Of course, here is the link:
https://tria.ge/240311-b3mlraha95/behavioral1
Brgds

Using the apk, I provided a more suitable fix.
Please try it out by installing the version with the latest commits:
pip install git+https://github.com/androguard/androguard


features request

Great and useful app. I have some ideas that might improve it a little more.
1- add new shortcuts to increase or decrease the tdp by 1+ or 1- and 5+ or 5-. with combination for example R1+L1+Right thumb up to increase...and so on.
2- when launching a game with a profile attached to it, add the ability to overwrite it with combination settings value. because currently when doing so it reverts back to the profile.
3- add in game overlay to show the tdp and other values like fps...etc. or if possible to control everything via in game overlay would be perfect, same as Aya neo app overlay

this software is not being supported anymore. find my latest here:
https://github.com/project-sbc/Power-Control-Panel-v2
some of these features are already available or will be added


Minor refactoring CTC forced alignment

Codecov Report

Merging #248 (41b5f8a) into master (2fd5730) will increase coverage by 0.00%.
The diff coverage is 23.07%.

@@           Coverage Diff           @@
##           master     #248   +/-   ##
=======================================
  Coverage   64.67%   64.67%
=======================================
  Files          84       84
  Lines       10128    10127    -1
=======================================
  Hits         6550     6550
+ Misses       3578     3577    -1

Impacted Files
Coverage Δ

neural_sp/models/seq2seq/decoders/ctc.py
48.27% <23.07%> (+0.15%)
:arrow_up:

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 2fd5730...41b5f8a. Read the comment docs.

Codecov Report

Merging #248 (41b5f8a) into master (2fd5730) will increase coverage by 0.00%.
The diff coverage is 23.07%.

@@           Coverage Diff           @@
##           master     #248   +/-   ##
=======================================
  Coverage   64.67%   64.67%
=======================================
  Files          84       84
  Lines       10128    10127    -1
=======================================
  Hits         6550     6550
+ Misses       3578     3577    -1

Impacted Files
Coverage Δ

neural_sp/models/seq2seq/decoders/ctc.py
48.27% <23.07%> (+0.15%)
:arrow_up:

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 2fd5730...41b5f8a. Read the comment docs.


May I take over leap wallet on SDK?

Requested functionality area

[ ] Wallet
[ ] Chain
[ ] Provider
[ ] Other

Details
@ice-chillios
I am a Web3 full stack developer and want to contribute to SDK project.

@promisingdev425 sure, we had no plans in upcoming month to do so.
BTW. you could comment a main issue #379 😅


Example refactor?

Most of the examples have a line:
from prompt_toolkit import prompt
Was this interface renamed?
eg:

from prompt_toolkit.contrib.completers import WordCompleter
from prompt_toolkit import prompt
Traceback (most recent call last):
File "", line 1, in
ImportError: cannot import name prompt

I'm using the newest toolkit version, aka prompt-toolkit (0.52)

Hi @sac2171,
That is right. The function was renamed yesterday from get_input to prompt, but this is not yet released on Pypi. I will probably release today, but in any case, the old name should keep working for a while.
Currently, I'm busy writing extensive Sphinx documentation, and I try to iron out inconsistencies and bad names.

I released a new version to Pypi.
New documentation is work in progress (There are still many gaps, but we keep improving.)
http://python-prompt-toolkit.readthedocs.org/en/latest/


Redis shim, with append-only sets.

Depends on func-scheduling (in vsreekanti) and ordered set lattices (in master).

Have you tested this shim?

@cw75 no, the test will just be the retwis code.

Let's not merge this into master for now. Let's test this single file on your own branch with the retwis stuff @xyclin .

@xyclin @cw75 we should figure out what we want to do with this code. Probably makes sense to put it in a separate applications repo or something?

@vsreekanti sure. The fluent user library should stay in master though yeah?

Yes, definitely to the user library. Same comment as on the other PR -- let's figure out what to merge and how we should structure the code.


WARNING: Illegal reflective access by com.google.protobuf.UnsafeUtil to field java.nio.Buffer.address

What version of OR-tools and what language are you using?
Version: v7.6.7691
Language: Java 11 (Scala 2.12.4)
Which solver are you using (e.g. CP-SAT, Routing Solver, GLOP, BOP, Gurobi)
Routing Solver
What operating system (Linux, Windows, ...) and version?
Ubuntu-18.04-64bit
What did you do?
Steps to reproduce the behavior:
n/a
What did you expect to see
n/a
What did you see instead?
When starting the sbt shell with java 11 I got the following warning
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.google.protobuf.UnsafeUtil (file:/home/erik/.sbt/boot/scala-2.12.4/org.scala-sbt/sbt/1.1.4/protobuf-java-3.3.1.jar) to field java.nio.Buffer.address
WARNING: Please consider reporting this to the maintainers of com.google.protobuf.UnsafeUtil

Anything else we should know about your project / environment
Happy to provide more information if needed.
Further information
It seems related to protobuf issue 3781 which appears to be a well-known issue. I suspect you are aware of the issue, nevertheless I thought I ought to report it.

It seems you have an old version of protobuf installed.
This was corrected in later versions.
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
Le sam. 30 mai 2020 à 10:52, CervEdin<EMAIL_ADDRESS>a écrit :

What version of OR-tools and what language are you using?
Version: v7.6.7691
Language: Java 11 (Scala 2.12.4)
Which solver are you using (e.g. CP-SAT, Routing Solver, GLOP, BOP,
Gurobi)
Routing Solver
What operating system (Linux, Windows, ...) and version?
Ubuntu-18.04-64bit
What did you do?
Steps to reproduce the behavior:
n/a
What did you expect to see
n/a
What did you see instead?
When starting the sbt shell with java 11 I got the following warning
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.google.protobuf.UnsafeUtil (file:/home/erik/.sbt/boot/scala-2.12.4/org.scala-sbt/sbt/1.1.4/protobuf-java-3.3.1.jar) to field java.nio.Buffer.address
WARNING: Please consider reporting this to the maintainers of com.google.protobuf.UnsafeUtil
Anything else we should know about your project / environment
Happy to provide more information if needed.
Further information
It seems related to protobuf issue 3781
https://github.com/protocolbuffers/protobuf/issues/3781 which appears
to be a well-known issue. I suspect you are aware of the issue,
nevertheless I thought I ought to report it.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/2044, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACUPL3OV2MWSYFDWRS4Y3A3RUDCNVANCNFSM4NOTKZHQ
.


Support for SSL client cert authentication and server certificate validation when connecting to RabbitMQ

This pull request adds two of the features we were missing for fully secure and verified connections to RabbitMQ message bus:

Support for client based certificate authentication
Support for verifying server certificate on the client side with the provided CA cert (bundle)

Both of those features were already supported for database (MongoDB) connection, but not for RabbitMQ.
Keep in mind that secure SSL / TLS connections to RabbitMQ were already possible (without verifying server certificate), but that wasn't documented anywhere. https://github.com/StackStorm/st2docs/pull/848 fixed that.
Nice thing is that we can use same naming for those options for database and messaging section (ssl_keyfile, ssl_certfile, ssl_cert_reqes, ssl_ca_certs).
Example config entries:
[messaging]
url = amqp://guest:guest@<IP_ADDRESS>:5671/
ssl = True
ssl_keyfile = /home/vagrant/client/private_key.pem
ssl_certfile = /home/vagrant/client/client_certificate.pem
ssl_ca_certs = /home/vagrant/testca/ca_certificate_bundle.pem
ssl_cert_reqs = required

Implementation wise, I needed to refactor some code so we now retrieve a properly configured Connection object in a single centralized place.
TODO

[x] Regenerate sample config
[x] Update documentation - https://github.com/StackStorm/st2docs/pull/850
[x] Tests

@armab @warrenvw Do we already handle CA authority and SSL certificate generation and management somewhere in our kubernetes-ha work?
If we do, it would also be good to eventually utilize it for MongoDB and RabbitMQ connections.

@Kami No, we don't auto-generate SSL/CA in K8s/HA work, leaving that part for user consideration/configuration.

I pushed changes so we now also expose SSL listener when running RabbitMQ on Travis (67fc03f8ed2b672c44c290d8dcc0b26ffe8ded31, 3b7744939e4b7adbb69762b1ef0ac7f0befbbcb1, 922cb23c2d3480849819ea6eb94d7191793c12ff) and added some basic tests which verify that those parameters work as expected (88a6d575f179aba684857b46af2da419579902cf).
In the future, we should do the same for MongoDB (we don't have any integration tests for SSL related parameters, just unit ones which are lacking).
NOTE: At the moment we only run those tests on Travis, because RabbitMQ SSL listener is not set up on local vagrant dev VMs.


Dose anyone receive this email use AFN

I received this warning message this morning. When check out code I find AFN use
static inline void af_swizzleSelector(Class theClass, SEL originalSelector, SEL swizzledSelector) {
Method originalMethod = class_getInstanceMethod(theClass, originalSelector);
Method swizzledMethod = class_getInstanceMethod(theClass, swizzledSelector);
method_exchangeImplementations(originalMethod, swizzledMethod);
}
which use the method apple give in the message.
Dose anyone have ideal about this?

’Your app, extension, and/or linked framework appears to contain code designed explicitly with the capability to change your app’s behavior or functionality after App Review approval, which is not in compliance with section 3.3.2 of the Apple Developer Program License Agreement and App Store Review Guideline 2.5.2. This code, combined with a remote resource, can facilitate significant changes to your app’s behavior compared to when it was initially reviewed for the App Store. While you may not be using this functionality currently, it has the potential to load private frameworks, private methods, and enable future feature changes.
This includes any code which passes arbitrary parameters to dynamic methods such as dlopen(), dlsym(), respondsToSelector:, performSelector:, method_exchangeImplementations(), and running remote scripts in order to change app behavior or call SPI, based on the contents of the downloaded script. Even if the remote resource is not intentionally malicious, it could easily be hijacked via a Man In The Middle (MiTM) attack, which can pose a serious security vulnerability to users of your app.
Please perform an in-depth review of your app and remove any code, frameworks, or SDKs that fall in line with the functionality described above before submitting the next update for your app for review.
Best regards,
App Store Review‘

AFNetworking doesn't do the described behaviour. Swizzling is fine; swizzling based on instructions downloaded via network is not.

@tewha Thanks, I will check other code

I received this warning message too. When check out code I find AFN use
static inline void af_swizzleSelector(Class theClass, SEL originalSelector, SEL swizzledSelector) {
Method originalMethod = class_getInstanceMethod(theClass, originalSelector);
Method swizzledMethod = class_getInstanceMethod(theClass, swizzledSelector);
method_exchangeImplementations(originalMethod, swizzledMethod);
}
Apple message :The code referenced in our initial rejection message includes any code which passes arbitrary parameters to dynamic methods such as dlopen(), dlsym(), , method_exchangeImplementations(), and running remote scripts in order to change app behavior or call SPI, based on the contents of the downloaded script


Make sure README has continuous integration badges

From the requirements: Implements continuous integration (e.g., via GitHub Actions), and all tests pass (lint, tests, and code coverage). Must also include badges in your project’s overall README file reporting your continuous integation status AND code coverage.

https://docs.coveralls.io/app-notifications#badges

#88 Added in this PR


SAMBRO: FTP Sync

Thanks for updating it - but not quite ready yet, I'm afraid.
No point to review this further until you've resolved the issues indicated so far - will continue after the next update.


audit-ci is Incompatible with yarn version 4

Running audit-ci with yarn 4.1.1 is broken, and does not report vulnerabilities at all.
It seems that v4 introduced major changes to the json output format of yarn npm audit that break audit-ci.
Example output in a project with vulnerabilities:
$ npx audit-ci
audit-ci version: 6.6.1
Yarn Berry audit report results:
undefined
undefined
[truncated]
undefined
undefined
Passed yarn security audit.

I updated one of the existing tests in test/yarn-berry-moderate to use yarn 4, and it (obviously) fails.

I am definitely interested in supporting this. I have some draft PRs that touch on adding test cases. I hope to release support in audit-ci v7.

After further investigation, Yarn v4 seems to support many of audit-ci's features directly: documentation on yarn npm audit.
With the recently released audit-ci v7, I decided not to support Yarn v4 out of the gate because I wanted to see feedback from the community before investing the time into supporting it.
The main functional gap in Yarn v4's implementation is that it doesn't support audit-ci's NSPRecord` feature, which allows you to set advisories' expiry.

+1 for this

@quinnturner I haven't explored yarn 4's npm audit in detail yet. What immediately stood out to me though  was the lack of a file-based configuration and ignore list. Of course, creating a wrapper script around the native yarn audit which provides that functionality is not a huge lift, but still something that needs to be documented, maintained, and published (or copy/pasted ugh).
audit-ci provides a nice abstraction across different package managers (and their versions). It enables a consistent mechanism to configure and manage audits in an org with a large number of repos that are - for various reasons - using different package managers and versions.


Calls to deprecated description() on external crate errors

Describe the bug
Certain errors, when formatted using Display, result in the message:
description() is deprecated; use Display

While Lettre itself still relies on description() for several of its Error implementations, I believe this is only really an issue when it calls into description() of external crates. External crates may have already transitioned away from the deprecated description() without the knowledge of Lettre.
One specific case of lettre::smtp::Error I encountered:
Io(Custom { kind: Other, error: Failure(Ssl(Error { code: ErrorCode(1), cause: Some(Ssl(ErrorStack([Error { code: 337047686, library: "SSL routines", function: "tls_process_server_certificate", reason: "certificate verify failed", file: "../ssl/statem/statem_clnt.c", line: 1915 }]))) }, X509VerifyResult { code: 62, error: "Hostname mismatch" })) })

To Reproduce
The specific case above can be reproduced by connecting to a secure SMTP server using an incorrect hostname. It looks like trying to connect by IP address is often enough to trigger a similar error. Otherwise, I've confirmed this with STARTTLS and smtp.routit.nl:25 (which should be .net, as the cert indicates).
Expected behavior
A more specific error message.
Environment (please complete the following information):

Lettre 0.9.2
Linux

Here's a branch of v0.9.x that fixes all clippy warnings, including this issue: https://github.com/lettre/lettre/compare/v0.9.x...stephank:v0.9.x-portier
This now reports the same error as: The certificate was not trusted. A little more helpful.
But it's a slight BC issue, because while dependant crates still build, they may now also receive description() is deprecated; use Display from lettre itself.
I guess this could be fixed by having duplicate formatting implementations in Display::fmt and Error::description, and ignoring the clippy warnings.

Fixed in 0.9.3 and master


chore(ui): Delete normalizr from saveCluster and dependencies in ui

Description
Follow up delete next-to-last occurrences of normalizr in #6782
Problems

Even more difficult than understanding data flow when containers share data in reducers via sagas, invisible data transformations outside of containers because classic network graph needed to access clusters as an object map with id as key.
Add external insult to internal injury: normalizr dependenct is no longer maintained.

Analysis

The only saveCluster call is in ClustersSidePanel when user clicks Next button.
Response always included new or updated cluster. Since last year, it also includes clusterRetentionInfo property.

Solution

Simplify service function and its call.

Residue

I supposed that initial attempt to use cluster object in response as source of truth did not work for new cluster, because several fields are null for uninitialized cluster:

healthStatus: null
helmConfig: null
status: null

But I see that { ...selectedCluster, id: newId } also causes the same logimbue request for overallHealthStatus property. After I click Finish and click the row, there is no such error.
Therefore, this contribution has minimal changes out of an abundance of caution, but it seems like clusters side panel has an invisible weakness.

@vjwilson Is this cluster creation workflow still enough on the critical path that you imagine we will ever update and unskip its integration test:
https://github.com/stackrox/stackrox/blob/master/ui/apps/platform/cypress/integration/clusters/clusters.test.js#L34-L104
I have kept it as possible useful documentation of the flow, but if it has passed its expiry date and benefit-to-cost for active maintenance, I would like to delete it as a follow up.

Investigate console warning:

Failed prop type: The prop clusterRetentionInfo is marked as required in ClusterSummary, but its value is null.

Checklist

[x] Investigated and inspected CI test results
[x] ~Unit test and regression tests added~

Testing Performed

yarn lint in ui
yarn build in ui and then compute branch - master for the following

wc build/static/js/*.js
main.js -6245 = 4691544 - 4697789
total -6225 = 11146821 - 11153046
ls -al build/static/js/*.js | wc
files 0 = 82 - 82

yarn start in ui

Manual testing
Add temporary console.log with JSON.stringify to compare:

cluster property in response
clusterWithId local value with updated with only id from response to support case of new cluster.

Visit /main/clusters and click a row

See GET /v1/clusters/id request

Click Next

See PUT /v1/clusters/id request

Integration testing
Too bad, so sad. Cluster creation flow is skipped. See Residue item 2.

ocp-4-10-ui-e2e-tests failure is unrelated

failed to create cluster

@vjwilson Is this cluster creation workflow still enough on the critical path that you imagine we will ever update and unskip its integration test:
https://github.com/stackrox/stackrox/blob/master/ui/apps/platform/cypress/integration/clusters/clusters.test.js#L34-L104
I have kept it as possible useful documentation of the flow, but if it has passed its expiry date and benefit-to-cost for active maintenance, I would like to delete it as a follow up.

There are been serious discussions about removing the ability to enter or edit cluster values in the UI, and only allow Helm or operator installs. However, removing manifest based installs is uncertain.

Some clusters still rely on them, despite our wishing they used better practices.
They offers a way to download new Helm values, so the UI form is not entirely useless, even if manifest based installs go ahead.

At this point in time, I think the best course is the status quo: leave the cluster tests as-is, neither removing nor updating them, until there is a definite decision.

I supposed that initial attempt to use cluster object in response as source of truth did not work for new cluster, because several fields are null for uninitialized cluster:

healthStatus: null
helmConfig: null
status: null

But I see that { ...selectedCluster, id: newId } also causes the same logimbue request for overallHealthStatus property. After I click Finish and click the row, there is no such error.
Therefore, this contribution has minimal changes out of an abundance of caution, but it seems like clusters side panel has an invisible weakness.

The code should degrade gracefully if any of the "status" nested objects are not available, was they wouldn't be for a newly created, but uninitialized cluster. But again, because we do not know the ultimate fate of manually entered clusters, let's hold off on running this down, as it may have a low ROI.


Add standard as dependency

Added standard as a dependency in case a future contributor doesn't have it globally installed. Also, I fixed one line in the cli so it conforms to standard.

:v: :horse: :+1:


Please add support for System.ServiceModel.Syndication in .NET Core

Original post here https://github.com/dotnet/wcf/issues/76 on the WCF GitHub project. I thought I'd post this here also for visibility.
The gist of it is that we need System.ServiceModel.Syndication.SyndicationFeed to build Atom/RSS feeds but it does not exist in .NET Core.

@RehanSaeed I don't think there's anything for ASP.NET or DNX to do for this. It's just a matter of the code in that repo being made available to such projects. As such, I'll close this issue.


Documentation should specify the types of databases we can create.

At this point in the Documentation:
https://github.com/orbitdb/orbit-db/blob/master/API.md#orbitdbcreatename-type-options
We are shown how to create a database, however, we don't have any list of the types of databases we can create (the example shows: 'eventlog') however it's unclear if KeyValue store should be 'kvstore' or 'keyValue', etc...
We should list the various types and the strings that corespond to them here.

Sounds good to me. Would you be able to craft a PR?

Almost forgot about this comment! I'm a little tight for the next week but I'll try to do it, would be a pleasure to contribute!!!

Keeping this here until the docs are updated but then will move to the field-manual repo after

I made this #702 . is this okay?

@1-byte-man Totally OK! Some small changes are needed for that PR, but it looks pretty great to me. :)

Resolved by #702, thank you @1-byte-man!


App规则改动

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

？没事别乱开iss

对不起点到了，手残（


feat(oauth2) hash 'provision_key'

Summary
I'm not sure I expect this to get merged, but I just wanted to share it and open up for comments or alternatives. This change stores a hash of the provision_key rather than the actual provision_key. The relative complexity of the code change is due to the fact that I intend to do this for client_secret as well, and that we still need to return the auto-generated values unhashed on the first call.

Create to_dao_transform and from_dao_transform functions. I'm not sure I got the direction right on these names - or perhaps it should be to_dal and from_dal. The point is that these modify the object on the way in to and way back from the database.
Add logic to oauth plugin to validate hashed values

@djMax I was thinking to move /authorize behind the admin API, thus removing the need for a provision_key.
The problem of hashing credentials (or data in general) is really a broader feature that other plugins could use as well. So we should think of it in more broader terms and not limited to the OAuth 2 plugin.


Bump version to Elastic 7.0.0

For supporting latest upgrade to 7.0.0.
Here : https://www.elastic.co/blog/elastic-stack-7-0-0-released?elektra=products&storm=main

Just FYI - I've been running the stack on 7.0.0 since Friday and every night when Logstash wants to roll over the index, it stops working with this message:
[2019-04-14T00:00:01,445][WARN ][logstash.outputs.elasticsearch] Could not index event to Elasticsearch. {:status=>400, :action=>["index", {:_id=>nil, :_index=>"logstash-2019.04.14", :_type=>"_doc", :routing=>nil}, #<LogStash::Event:0x5b565b59>], :response=>{"index"=>{"_index"=>"logstash-2019.04.14", "_type"=>"_doc", "_id"=>nil, "status"=>400, "error"=>{"type"=>"illegal_argument_exception", "reason"=>"The [default] mapping cannot be updated on index [logstash-2019.04.14]: defaults mappings are not useful anymore now that indices can have at most one type."}}}}

I searched my configuration up and down and through the containers but I cannot find a defaults mapping setting. Yesterday, I created the logstash-2019.04.13 index manually and it worked again until the roll over tonight.
I'm quite new to Elastic Search and use it to mirror my rsyslogs to a searchable database (so nothing critical is lost), but I find it quite frustrating to debug such issues.

@sdellenb did you start a new Stack or upgrade from 6.7? My gut feeling is that the Logstash index template may have changed between the 2 versions and needs to be replaced.

I upgraded from 6.7, with the same changes as this PR (except the port). I'll check the index template.

@sdellenb the release notes mention the field reference parser is now more strict. Are you using a specific plugin to ship your logs to Logstash?

No plugin, just an rsyslog template generating a JSON for logstash.
I've managed to get it working again by updating the index template with a simplified version of the mappings of the current index as posted above. Thanks for the hint! 👍
On a different note regarding the upgrade to 7.0.0:
discovery.zen.minimum_master_nodes has been deprecated.
I'd have no idea how to address it, but so far it doesn't break anything.

Thanks for the feedback, much appreciated  🙏  We'll have to address this in the default configuration indeed.

@kg-ops 7.0.1 is out. Would you mind updating the PR so we can test the upgrade path from 6.7.x?


model produces multiple responses in one after training with conservation datasets using sft

I am using sft trainer to fine-tune mistral 7b on a multi-round conversation dataset.
I format the conversation as such:
###Human: ...
###Assistant: ...
###Human: ...
###Assistant: ...
Within the prompt, I ask the model to produce the results in a json format: { key:value }
However, after training, the model would produce multiple { key:value } within a single response. Each instance of value
would be slightly different.
I am not sure what the issue issue is. Does anyone have a solution?

It's a bit hard to know without seeing the dataset. Is it possible that maybe the EOS tokens are missing during training and thus the model keeps on generating?

That is most likely the issue, you can mitigate that by making sure the EOS token is different from the PAD token. Before training you can do tokenizer.pad_token = tokenizer.unk_token and make sure the values of tokenizer.pad_token is different from tokenizer.eos_token


[RAC][Table] add aria-colindex to Column and Cell

Provide a general summary of the feature here
In react-spectrum each column and cell gets a aria-colindex attribute: https://react-spectrum.adobe.com/react-spectrum/TableView.html. This is very helpful for testing and I'd love to see the exact same thing supported for RAC.
🤔 Expected Behavior?
Expose an index prop in some way so that is can be applied to the columns and cells. Or even better would be for it to be applied behind the scenes.
😯 Current Behavior
There is no way to add aria-colindex to the Cell or the Column.
💁 Possible Solution
No response
🔦 Context
This helps a lot with testing, ideally when testing you want to assert a cell's content based on the column. In order to do that you need to know the index of the column inside the row.
💻 Examples
No response
🧢 Your Company/Team
No response
🕷 Tracking Issue
No response

We do this in React Spectrum't TableView because we are using virtualization.

If all of the columns are present in the DOM, it is not necessary to set this attribute as the user agent can automatically calculate the column index of each cell or gridcell. However, if only a portion of the columns is present in the DOM at a given moment, this attribute is needed to provide an explicit indication of the column of each cell or gridcell with respect to the full table.

From https://www.w3.org/TR/wai-aria-1.2/#aria-colindex
That being said, we may want to offer a way to enable this in RAC for those using virtualization, or see if we could detect it automatically.

We do this in React Spectrum't TableView because we are using virtualization.

If all of the columns are present in the DOM, it is not necessary to set this attribute as the user agent can automatically calculate the column index of each cell or gridcell. However, if only a portion of the columns is present in the DOM at a given moment, this attribute is needed to provide an explicit indication of the column of each cell or gridcell with respect to the full table.

From https://www.w3.org/TR/wai-aria-1.2/#aria-colindex
That being said, we may want to offer a way to enable this in RAC for those using virtualization, or see if we could detect it automatically.

Slightly off-topic, but are you folks planning to bring virtualization into RAC Table? I was unsuccessful when trying to integrate something like tanstack virtual, with regards to accessibility, drag and drop and some other RAC Table features.

@jaknas It isn't in the near-term plans. We will definitely remove that from the docs before the GA release. I think it is something we will consider adding in the future, however.

Again, just to clarify, the reason I'm interested in this is testing. There is no other  straightforward way to assert a cell's value based on the column it is in. Also seems like y'all already maintain the index internally so I'm assuming it shouldn't be to crazy to apply it. I'm willing to take a crack at it if any of you are willing to review it.

We're happy to review a contribution!
Side note, what testing library are you using? You could make use of data-testid https://codesandbox.io/s/romantic-shtern-knsyck?file=/src/App.js

I don't think this attribute is supposed to be there unless some of the columns are missing as Reid mentioned. I'd recommend using a custom data attribute for testing instead.

I'm using Playwright to test and I'm totally fine with using a data-attribute. I just need some indication on the cell to what column it is in. From what I can tell, there is no way for me to do that in user land.


How safe is this to use?

title said it all.

This is just a webserver, It's do nothing with PUBG. You should care about your PUBG-map-hack, and make it undetected.


Drop "one or more" from index description, follow up #644

Signed-off-by: Lei Jitang<EMAIL_ADDRESS>

LGTM


Latest Flutter roll causes a compilation error for

See https://buganizer.corp.google.com/issues/173774628. Escalated to roller, engine chats.

Should be fixed by https://github.com/flutter/buildroot/pull/414

https://github.com/flutter/buildroot/pull/414 seems to be merged now. Is it safe to close this issue? I can't verify if this was fixed or not.

This should be fixed once the commit that updates the reference to the buildroot has rolled into Google3. There doesn't seem to be anything actionable here.


Request  for -invert-hash type feature as in Vowpal Wabbit.

Is your feature request related to a problem? Please describe.
The getReadableModel() gives hash with the weight.  The PR https://github.com/microsoft/SynapseML/pull/821 does refer to the requested feature but it was not committed.
Describe the solution you'd like
We want  feature: weight
Additional context
Similar to -invert-hash of vowpal wabbit.

@eisber I was looking at your reply for  https://github.com/microsoft/SynapseML/issues/1364.
I am finding it difficult to understand your statement "> Additionally it depends on the learning algo how the features are mapped to weights."
If there are some additional transformations at the feature level happening within the VowpalWabbitRegressionModel, then it makes sense otherwise I am unable to understand the statement.
Pls, correct me if I am wrong.

not all algos in VW have just a single weight for each feature.
@jackgerrits  can help explain too.

For exampling if using bagging, then internally VW maintains several models. Each occupying a different hash space. You need to know the number of bags in order to decipher what each hash may correspond to.


Blending between the UKV and MOGREPS-UK

As the product owner I want IMPROVER to be able to blend time-lagged UKV forecasts with time-lagged MOGREPS-UK forecasts
Related issues: #166
Sub tasks:

[ ] Produce a software strategy and process chain for inter-model blending to meet scientific needs #176
[ ] Develop capability to blend UKV probabilities/percentiles with MOGREPS-UK probabilities/percentiles for a single time
[ ] Develop and test blending chain for several lead times

Acceptance criteria:

Written strategy document # 176
Add capability to merge UKV probabilities/percentiles with MOGREPS-UK probabilities/ percentiles into a single cube for a single validity date and time.
Add any additional capability required to blend UKV and MOGREPS-UK together (associated ticket #166) Ensure that sensible and sufficient metadata is stored on the resulting cube. Some initial subjective weightings will be required.
Adapt test suite to enable blending of MOGREPS-UK and UKV data together. Some method of determining what new data is available at that time for each validity date and time will be required. The processing should be separate from the processing for each individual Model.
Demonstrate the results of blending together the two models in the test-suite.

Closing as covered by other Jira tickets on suite development.


Add JustList: {C23}

Checklist

[*] I understand that this is not the place to request a token listing.
[*] I have tested that my JustList is compatible by pasting the URL into the add a list UI at justswap.org.
[*] I understand that filing an issue or adding liquidity does not guarantee addition to the justlists website.

JustList URL:  https://c23token.com/c23.ts
JustList Name:  C23
Link to the official homepage of the JustList manager: https://c23token.com

Thanks for reaching out.
We are currently very tight on development resources and adding new lists on a case-by-case basis.
If timing is a key issue for you, we recommend you join the existing community SUNSWAP list, for example: Tron Alliance List: https://github.com/listtronalliance/tronalliance.
Thanks.

Hello,c23token.I hope you have a good day.
The c23 token can not find in SunSwap V1 ,V1.5 and V2, you must first create createExchange in SunSwap by youself. Specific methods can be referred to https://www.sunswap.com/docs/sunswap-interfaces_en.pdf.

Sorry, this issue will be closed . If you want to add a new list, please resubmit.


Typing activity not disappearing before message arrives IOS

Bot Info

SDK Platform: .NET
SDK Version: <IP_ADDRESS>
Active Channels: Facebook
Deployment Environment: App Service

Issue Description
When sending a TypingActivity, the "typing" bubble does not dissapear when the actual message arrives. Its delayed by a few seconds, creating a "bouncing"-effect. This only seems to be a problem in messenger on IOS.
Code Example
// Send "typing" information
var typeReply = context.MakeMessage();
typeReply.Type = ActivityTypes.Typing;
typeReply.Text = null;
await context.PostAsync(typeReply);

// some other code

// send actual message
await context.PostAsync(actualMessage);

Expected Behavior
Typing bubble disappearing the moment the actual message is delivered.
Actual Results
Typing indicator not disappearing when the message arrives, it's delayed about a second. Works fine on web and android.

I will look into this to see if there is something on our end causing this, but it sounds like an issue with the facebook IOS app and I highly encourage you to reach out to Facebook support as well.  On our side, the behavior of the typing indicator should not change when using different platforms.  As I said I will look into this to confirm.

Ok, a little more research led to the conclusion this is a Messenger on IOS-bug, not BotBuilder. The problem persists even if there is a human typing the message. I have filed a bug report at Facebook.

Thanks for the update, good luck!


Typo in Flatpak subtitle

"A fast, beautifull browser" should be "A fast, beautiful browser"
https://github.com/zen-browser/flatpak/blob/e4635f77e53fd8e7fb6764e52587a4a3a9ddfd4e/io.github.zen_browser.zen.metainfo.xml#L11

After I heard about Zen Browser for the first time, my first step was to search for it in my package manager. It's a little off-putting when the third word has a typo.

@Jafner: to me it was pretty obvious the dev must be a non-native English speaker, which was a correct assumption. What is important is the tool itself 😉


ERA returns NaN with ForwardDiff

When trying to compute a derivative with ForwardDiff, the iers_era function returns a NaN type, which does not allow the AD computation of the GCRF-to-ITRF rotation
julia> using IERSConventions
julia> using JSMDUtils.Math: D¹

julia> D¹(t->iers_era(iers2010a, t), 1)
NaN

This is caused by the usage of the mod function:
julia> ForwardDiff.derivative(t->mod(t, 1), 2)
NaN


Automated releases

How about we use semantic-release for automated releases and then no one has to make a release?
https://semantic-release.gitbook.io/semantic-release/
I'm willing to implement.

The release process is fairly automated now, so I think we don't need this. Some manual control is good


Doesn't work with homebrew aws cli?

I use the homebrew install of the cli - aws-cli/2.0.0 Python/3.8.1 Darwin/19.3.0 botocore/2.0.0dev4.
After installing this plugin, I see the plugin config in ~/.aws/config, but attempting to use it results in:
$ aws s3 touch my-bucket
usage: aws [options] <command> <subcommand> [<subcommand> ...] [parameters]
To see help text, you can run:

  aws help
  aws <command> help
  aws <command> <subcommand> help
aws: error: argument subcommand: Invalid choice, valid choices are:

ls                                       | website
cp                                       | mv
rm                                       | sync
mb                                       | rb
presign

Exactly the same for me. Would really like to fix.

Same for me, I uninstalled the homebrew awscli. I am using conda w/ python 3.8 and that is working after installing boto3 as well


Solarized Dark Line Numbers

The line number coloring was difficult to read, changed to a shade of white for readability.
issue 2594

Sorry, can you do this change below this line - it allows us to copy and paste updated themes into the block above (so we don't lose your adjustment).
Do this also work with both the light and dark theme?

No problem probably should of paid attention more to the file. This won't work for the light theme, as it changes the color to a white ish color.

@remy I suppose this can be closed as this was fixed?

👍


problems with zeroed_width argument in pulse.continuous

There seems to be some issues with initial/final discontinuity in some pulses in the pulse library.
g_disc = discrete.gaussian(duration=240, amp=0.1, sigma=80)
g_disc.draw(scaling=0.2)

g_disc = discrete.gaussian_square(duration=240, amp=0.1, sigma=15, risefall=20)
g_disc.draw(scaling=0.2)

So you want first sample and last sample to be 0? or just the first?
I also think I need to fix drag and gaussian_deriv.

Yes (at least by default). I think the gaussian part of drag will automatically be fixed, but there is some difficulty with the gaussian_deriv component due to its antisymmetry.


fix: race condition in workflow reconciler

Signed-off-by: Chris Laprun<EMAIL_ADDRESS>

Which one is here caused the issue? AFAIK concurrentHashMap should cover those usages here

I thought so as well but it seems that the results might not be updated correctly with the proper visibility, resulting in conditions tests not seeing the actual results (e.g. in the test that was failing, it seemed like the unmet condition on DR2 was not seen when checking whether DR4 should be reconciled)


add EFCore.SoftDelete

An implementation for soft deleting entities for EntityFramework Core.

LGTM

Thanks @AshkanAbd, and thanks @ErikEJ for the reviews.


Fix config URL

Description
Fix config url in build doc
Related Issues

https://github.com/threefoldtech/tfgrid-sdk-ts/issues/1459

Checklist

[ ] Tests included
[ ] Build pass
[ ] Documentation
[ ] Code format and docstrings
[ ] Screenshots/Video attached (needed for UI changes)

verified the config file is now generated in the new path


docs: update wording of nodejs prerequisite

Please note that the Nodejs version dependency of todo-list-with-Azure-backend-M365 is the same as that of todo-list-with-Azure-backend, while the Nodejs version dependency of NPM-search-connector-M365 is the same as that of hello-world-bot.

Please note that the Nodejs version dependency of todo-list-with-Azure-backend-M365 is the same as that of todo-list-with-Azure-backend, while the Nodejs version dependency of NPM-search-connector-M365 is the same as that of hello-world-bot.

Thanks, since you have tested these 2 samples on nodejs 12, I will note they're fully tested on this version. For other samples, we will test the samples on nodejs 12 in next sprint and update the prerequisites.


gh-page rebuild failing.

Actual Behaviour
gh-page rebuild is failing.
Expected Behaviour
All webgen assosciated websites should reflect new changes.
Would you like to work on the issue?
Yes, but would need write access to this project.@mariobehling please check this.

@agbilotia1998 You can send PR to the gh-pages branch manually. We can try it & see if the auto deploy on gh-pages start working again.

@geekyd @mariobehling  I would be needing gh-token of this repository to test if the problem is something like travis-ci timeout or something else.

The issue is still there.

@mariobehling @geekyd @ParthS007 please check this screenshot

@agbilotia1998  I think there is problem with token , will check this :+1:


Entity change composite validator refactoring

Entity change composite validator refactoring fix the bug of ancestor validator when the changed entity does not contain any changed fields.

@galkoren
I fixed the test according to the review. It is hard to implement toggle and I think we can release the fix without it. Please, approve my change.


Added new exercise 'darts'

exercises/settings.gradle might conflict once the pull request for custom-set is merged as they are alphabetically close.

Sorry, I guess IntelliJ tried to do clever things... I deleted those two Gradle files.

Thanks, @lathspell !


feat(book): Batches

Description
Adds documentation around Batch types.

📚 $\text{Stack Overview}$
Pulls submitted in this stack:

#252 👈
#251
#226
main

This comment was automatically generated by st.


uppercase admonition style directives

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@41d4cce). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #6006   +/-   ##
=========================================
  Coverage          ?   83.12%
  Complexity        ?    12391
=========================================
  Files             ?     1429
  Lines             ?    46864
  Branches          ?     5766
=========================================
  Hits              ?    38957
  Misses            ?     5225
  Partials          ?     2682

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 41d4cce...5a7c23a. Read the comment docs.


OSPP 2021: Wechaty Piggy Bro

Please make sure to check the following boxes creating your pull request, thank you very much!

[*] Add Blog Header, including title, author, image, categories, tags, etc.
[*] Keep all filenames lowercase, and use - to connect words instead of space. e.g. 2017-10-06-wechat-pc-impactor.md instead of 2017-10-06-WeChat PC Impactor.md
[*] Embed video/pdf from YouTube/Bilibili/local (if there's any) by using {% include iframe.html src="URL_or_PATH" %}. (Learn more about how to embed file/url in the post by reading this blog post
[*] Save photo to local before publishing, to a folder named by ${MONTH}-${YOUR_BLOG_SLUG}/ under /assets/2021/ directory.
[*] Select a beautiful and meaningful teaser image for your blog
[*] Create your contributor profile (if you are a first time contributor)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@ReiKohaku Please make github action green then I will review this blog.
You can run npm run test locally, only when you pass test locally, it may make github green online.