Setting 3D int array to null produces does not set the variable to null

From experience, setting a 3-dimensional integer array to null does not null the variable as intended, leading to unintended consequences/issues. For example, the following code would not print true, and would only set the inner arrays to null.
int[][][] exampleArray = null;
if (exampleArray == null)
	System.out.println("True");

Furthermore, if you tried to get the length of the exampleArray, it would return 4, but if you tried to get the length of any interior arrays ("exampleArray[0].length"), it would throw an error. This caused issues in my own project that are difficult to diagnose, so after spending some time trying to figure out the cause, the 2 images provided compare what works and what threw an error.
Error: https://imgur.com/ZhFgwsx
Working: https://imgur.com/vnSomuk

Could not reproduce.  I remember that it's a case several times: you just leave an issue which I'm unable to reproduce, I write about it and no feedback from your side. I'm not a wizard and without knowing where the problem is I can't guess by some sort of magic, telepathy, etc.
When you posted this piece of code:
int[][][] exampleArray = null;
if (exampleArray == null)
	System.out.println("True");

did you try to run it out of your context? Just create a new project, create a class with public static void main and paste it? What did you get? I did and got 'True' output. So I presume that the problem is not with assigning null to array variable. Perhaps, is has nothing to do with arrays at all. From your screenshot I see that your code is much more complex than these 3 lines of "reproducer" (BTW, NEVER EVER do you use screenshots to share some code). I only can presume that if you build your project without optimizations, problem goes.
So what to do? You can try to find out the real case. Try to isolate your problem. Start with isolating your particular method and then try to remove various parts until problem disappears. You can try to build JS without obfuscation and see what code was generated. Anyway, if it's too complex, you can just ask me to do that: just give me your entire code base and provide with full info: how to build your project, which exact steps I should perform to reproduce the issue on my side.

Hi,
I apologize for the lack of detail and messiness in the original report. Moving forward, I'll do my best to try to reproduce a simple test case be as detailed as possible when I encounter bugs with TeaVM.
I just spent some more time testing this to really see what's wrong, and what I found was quite peculiar. I tried to produce as many test cases as possible for you. Out of 4 test cases, the first two work, and the last two fail on TeaVM but work fine on Java. Note that the test cases use a boolean that is always set to false.

In the first case, I have an if-else statement checking the false boolean like so and then initializing the array. This works fine, and I can access tileArray afterwards:
        int[][][] tileArray;      if (!alwaysFalseBoolean)          tileArray = exampleArray1;      else          tileArray = null;      System.out.println("tileArray[0][0][0]=" + tileArray[0][0][0]);

The 2nd test case is flipped (array setting would be in the else statement), and works fine because if (false) will always be false:
        int[][][] tileArray2;      if (false)          tileArray2 = null;      else          tileArray2 = exampleArray2;      System.out.println("tileArray2[0][0][0]=" + tileArray2[0][0][0]);

The 3rd test case is where things start to get interesting. I have a statement that is equivalent to the 2nd test case, the only difference is that it checks our boolean that is always false... Somehow, this throws an error in TeaVM. I even have a line printing out the value of alwaysFalseBoolean before this if-else statement, which properly prints out "false" as expected, yet this method of assigning the array leads to an exception being thrown.
        int[][][] tileArray3;      // Line below prints out false (as intended)      System.out.println("Value of alwaysFalseBoolean=" + alwaysFalseBoolean);      if (alwaysFalseBoolean)          tileArray3 = null;      else          tileArray3 = exampleArray3;      System.out.println("tileArray3[0][0][0]=" + tileArray3[0][0][0]);

The 4th case is similar to the 3rd, except I use ternary to set the array rather than an if-else statement. It produces the same result as the 3rd case though (when using alwaysFalseBoolean as the ternary condition check) and throws an exception. (if I use "false" in the ternary check instead, it works, similar to 3rd case):
`        int[][][] tileArray4 = alwaysFalseBoolean ? null : exampleArray4;
if (tileArray4 != null)
System.out.println("Test #4 Passed null-check"); //Works
 if (tileArray4 != null) {
     // Line below causes crash
     System.out.println("tileArray4[0][0][0]=" + tileArray4[0][0][0]);
 }`

So it seems like whatever is causing this has to do with checking a boolean before initializing an array, and somehow that check only works in one order, the "if (!condition) doAction()" but not the other way around. You should be able to easily test it out using the file I attached.
Let me know if you need any other information.
Attached file:
TeaVMTest.txt
Sample output in browser:

===Attempting Test #1 [If-Else setting, 1st order]===
exampleArray1[0][0][0]=0
Value of alwaysFalseBoolean=false
tileArray[0][0][0]=0
===Attempting Test #2 [If-Else setting, 2nd order, using 'false' instead of a boolean set to false]===
exampleArray2[0][0][0]=0
tileArray2[0][0][0]=0
/n/n/===Attempting Test #3 [If-Else setting, 2nd order, using alwaysFalseBoolean]===
exampleArray3[0][0][0]=0
Value of alwaysFalseBoolean=false
Uncaught TypeError: Cannot read properties of undefined (reading 'data')
at CO (classes.js:51:19)
at Eh (classes.js:44:42)
at Y.runner (classes.js:3:25)
at Y.run (classes.js:35:359)
at Y.start (classes.js:35:171)
at DY (classes.js:36:253)
at classes.js:3:15
at basic/:8:5

The real cause of issue is following: when we declare multidimensional array variable depending on some condition (this produces phi-node), one of branches of which produces null literal, and then take first dimension of this array, it's by mistake treated as a JS object and TeaVM (actually, JSO) inserts JS unwrap method.

@aloraps can you please build TeaVM locally and test your app against local build?


Pronunciation of reas

Yeah, I created this library and gave it a name that I don't even know how to pronounce.

I'm creating this issue to see how people read it and finally learn how to pronounce it correctly.
So, let's rebund it.

Around here we call it ray-ass so, there's that.

Google Translate reads this word very close to "reez", and it sounds distant from "ass" which is read like "us".
I also have a proposal: you may add an article before "reas" and get the interesting effect:
"the reas" sounds like "there us"
"a reas" sounds like "areas" which is a completely safe name for a UI library.

My take on Reakit: ree - ACK - it


[OPPRO-228] Cast to int by truncate

What changes were proposed in this pull request?
To align with Spark's behavior, set casting to int by truncate in Velox.
How was this patch tested?
Verified on Jenkins.

To fix the incorrectness of TPC-DS q54.


Scaffolding : upgrade templates to new format

:warning: Depends on #114
Description

Upgrade to the new function arguments documentation format (e.g. https://docs-v2.kuzzle.io/plugins/1/accessors/execute/)
Modify the scaffolding generate command:

Inject the extracted API description into the scaffolded file, instead of printing it on the console
Inject the extrated function signature into the scaffolded file, instead of printing it on the console

 Snippets tests reports   SDK Version Tests overview      v6        v5                                   :heavy_minus_sign:                    v1        v1        v1


Scopes documentation

Ready to be published from our (IDServices) point of view.
:)

@SBourgarel-mendix please refork to get rid of all these old commits in the future. For now, please sign the CLA.

@Adam-Dupaski Ok sure. I just clicked the Fork button on the top, then git-clone it locally, then made a new branch and committed on that. How should I have done?
I signed the CLA

@SBourgarel-mendix I don't know how you managed to get all the old commits unless:

You forked a long time ago
You forked from a historic commit instead of from the current dev.

If neither of these, then I have no idea how it happened!
@Adam-Dupaski are you happy for this to go in the "Mendix Profile" category for now?

@MarkvanMents sorry we continued this discussion over Slack. I also don't know how it happened, as @SBourgarel-mendix forked and committed via SourceTree just today. Anyway, the PR will merge.

@MarkvanMents I think we should take a closer look at the doc and decide where it should go tomorrow.


Popup menus are not positioned properly (Linux GNOME)

Godot version
4.2-rc [ad72de508]
System information
Manjaro Linux, X11 (X.Org), Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3060 Laptop GPU () - 11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz (16 Threads)
Issue description
When created close to the screen's edge, popup menus are cut off intead of being properly positioned (GNOME 45, Manjaro Linux). This happens while Single Window Mode is disabled.
Didn't test in other Linux Distro + DE combinations.
I can reproduce it in 4.0.2 and 4.1.3.

Workaround
Use Single Window Mode (enabled in Editor Settings).
Steps to reproduce

Build & run the latest Godot 4.2-rc on the GNOME v45 desktop.
Right-click on a property in the Inspector close to the screen's edge.

Minimal reproduction project
N/A

Are you using a X11 or Wayland session? Use echo $XDG_SESSION_TYPE in a terminal to know.
Also, try enabling Single Window Mode in the Editor Settings.

@Calinou
I use X.Org, didn't test with Wayland. Single Window Mode helps the issue, thanks, but we loose the floating windows functionality. It's a workaround if you don't need those. I'll add it into the OP.

@Calinou
I can reproduce it in 4.0.2 and 4.1.3.

I am unable to replicate this problem on Debian X11 Xfce with v4.2.beta.custom_build [c455cb655] when using only Godot builtin nodes.
Does this happen only for your BTPlayer node or also for standard nodes?

@Sauermann
On builtin node properties too. Happens also on official builds version 4.1.3 and 4.0.2. It only breaks when Single Window Mode is disabled.

I can't reproduce this on 4.2.beta da0b1eb12 (Fedora 39, KDE Plasma 5.27.9). Even if I resize the window to a tiny size (using KDE window overrides to disable Godot's minimum size) and spawn a context menu while the window is on the right edge of the screen, the context menu is positioned correctly:

I finally figured it out! So I found out that it only happens with Linux kernel 6.5 and 6.6 (Intel+NVIDIA laptop with X11) and is somehow related to simpledrm driver. I can't reproduce it on kernel 6.1.
When this bug happens, I also have the following weird thing - when I run xrandr my output shows a ghost monitor device None-1-1:
> xrandr
Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-4 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm
   1920x1080    165.00*+
None-1-1 connected (normal left inverted right x axis y axis)
   1920x1080     60.00 +

To fix it, I added these lines to /etc/default/grub:
# /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="nvidia_drm.modeset=1"

Then I ran update-grub and rebooted.
Enabling nvidia_drm disables simpledrm. Both ghost device and the popup menus in Godot stopped being an issue for me, at least for now.

I doubt we can do about anything if there's no way to detect this "ghost" monitor from Godot. It's also a system configuration issue that will affect other applications negatively anyway, so it's better to fix it on your end.

Thing is, it doesn't affect other applications. GTK apps, Qt apps and their popup menus work as expected in these conditions. But I'm not saying it should be fixed. Likely, it is an issue with the nvidia drivers and/or kernel. I'm not sure how many nvidia users are actually affected by this. I only found a thread on Arch forums: https://bbs.archlinux.org/viewtopic.php?id=288009


generate browserslist command fails

Command
generate
Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
According to the documentation we can use ng generate browserslist to create a .browserslistrc file.
Just created a new Angular workspace/application which does not include a browserslist configuration file by default.
However, running the suggested command fails:
Error: A collection and schematic is required during execution.
Minimal Reproduction

npm i @angular/cli@15
ng new ...
ng generate browserslist

Exception or Error
Error: A collection and schematic is required during execution.

Your Environment
Angular CLI: 15.1.3
Node: 16.13.2
Package Manager: npm 8.1.2
OS: win32 x64

Angular: 15.1.2
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1501.3
@angular-devkit/build-angular   15.1.3
@angular-devkit/core            15.1.3
@angular-devkit/schematics      15.1.3
@angular/cli                    15.1.3
@schematics/angular             15.1.3
rxjs                            7.8.0
typescript                      4.9.4

Anything else relevant?
No response

Looks like there is a mistake in the docs as the correct command is ng generate config browserslist

Looks like there is a mistake in the docs as the correct command is ng generate config browserslist.

 Opening the ng generate browserslist link shows the command properly.
Thank you for the fast reply!


Feature/vuepress sidebar fixes

Updated vuepress.
Fixed sidebar and nav issues.
Cleaned up .html references for consistency.
Fixes: https://github.com/OXRS-IO/OXRS-IO-WEBSITE/issues/44

@sumnerboy12 I'd hope so too :P haha
But looks good - code is live, you can check it out and let me know if there are any issues.
I did a bunch of cleanup of the side bar to make it easier for others to add/remove pages.


[OIS] Fix lock-app integration test

Increase ZCL command request timeout in lock-app
the integration tests.
The PSA backend causes more operational overhead.
This requires a longer timeout.

FYI, had to revert here, this is failing all our CI :(  https://github.com/project-chip/connectedhomeip/pull/27391


docs: add adr-1 proposal for msg server and keeper consistency.

Purpose / Abstract

Summary by CodeRabbit
Summary by CodeRabbit

Documentation

Introduced a proposal for refactoring core components to enhance separation of concerns and testing framework within the Nibiru Chain documentation.

LGTM, just want everyone here to pinky promise that we will never do a binding from msg to keeper ever again. Any binding (like wasm for example) needs to go to msg server and not touch the keeper, otherwise we can lose the msg validation from the msg server.


How can I set the ClusterDomain in AlertManager?

I would like to know how can I set ClusterDomain in AlertManager to support FQDN DNS
I found this Pull 3138 but I could not find any docs do handle with this.
Thanks

You can pass --cluster-domain="some.domain.example.org" to prometheus-operator.

As @paulfantom already answered, I'm gonna close this here, but feel free to keep commenting and or create another issue should you feel there is a problem with Prometheus Operator :)


Implement of import and export

Would be AWESOME use import and export features (es6) in LS.

I use them all the time... like this:
``import lala from './lala'``
lala!

#705


doc: Fix some typos on the Kconfig best practices page

Found some copy-paste errors while going through it.

Codecov Report

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

@@           Coverage Diff           @@
##           master   #11289   +/-   ##
=======================================
  Coverage   51.55%   51.55%
=======================================
  Files         216      216
  Lines       27659    27659
  Branches     6934     6934
=======================================
  Hits        14260    14260
  Misses      10652    10652
  Partials     2747     2747

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 ef11776...06568d1. Read the comment docs.


SortedSet methods like #rangebyscore broken with redis_object >= 0.9.1 and use of multi

Up until redis-objects 0.8.0, it was possible to do something like the following so one could atomically find and remove elements from a SortedSet with a rangebyscore.
require 'redis'
require 'redis/objects'
require 'redis/sorted_set'

class Obj
  include Redis::Objects
  sorted_set :things

  def id
    rand(1_000_000)
  end

  def add(idx)
    self.things.add(idx, idx)
  end

  def pop_things(pop_size)
    results = self.redis.multi do
      self.things.rangebyscore(0, pop_size)
      self.things.remrangebyscore(0, pop_size)
    end
  end
end

obj = Obj.new
100.times { |idx| obj.add(idx) }
puts obj.pop_things(10)

With the introduction of the following commit (0.9.1), this functionality has been broken. Trying to map and unmarshal all the items would work fine if we're not in a multi block. But when in a multi-block, the result is a Redis::Future object.
https://github.com/nateware/redis-objects/commit/7c41fb6#diff-f4e12a534beaeeff971c9c7b3a1e67e2R123
/Users/me/.rvm/gems/ruby-2.0.0-p353@redis-example/gems/redis-objects-0.9.1/lib/redis/sorted_set.rb:122:in `rangebyscore': undefined method `map' for <Redis::Future [:zrangebyscore, "obj:885330:things", 0, 10]>:Redis::Future (NoMethodError)
from redis-example.rb:20:in `block in pop_things'
from /Users/me/.rvm/gems/ruby-2.0.0-p353@redis-example/gems/redis-3.2.0/lib/redis.rb:2148:in `block in multi'
from /Users/me/.rvm/gems/ruby-2.0.0-p353@redis-example/gems/redis-3.2.0/lib/redis.rb:37:in `block in synchronize'
from /Users/me/.rvm/rubies/ruby-2.0.0-p353/lib/ruby/2.0.0/monitor.rb:211:in `mon_synchronize'
from /Users/me/.rvm/gems/ruby-2.0.0-p353@redis-example/gems/redis-3.2.0/lib/redis.rb:37:in `synchronize'
from /Users/me/.rvm/gems/ruby-2.0.0-p353@redis-example/gems/redis-3.2.0/lib/redis.rb:2141:in `multi'
from redis-example.rb:19:in `pop_things'
from redis-example.rb:33:in `<main>'

Unfortunately this is not an issue with redis-objects, it's because redis.rb changed multi to return a Redis::Future object.  There's another ticket in here open on it.  I can't revert the commit you linked because it fixed other bugs with nested arrays.


maintenance: Add .lock files to .gitignore

Goal

Remove system-updated lock files from version control.

Design
Following private Slack discussion .gitignore was updated to ignore Podfile.lock and Gemfile.lock.  The git cache was aligned with the ignored files, effectively removing them from version control.  A changelog entry is not required since this is a non-functional, repo maintenance update.
Tests
Full Unit and CI tests were run coincidentally and passed.
Review
Outstanding Questions

This pull request is ready for:

[ ] Initial review of the intended approach, not yet feature complete
[ ] Structural review of the classes, functions, and properties modified
[X] Final review

[ ] The correct target branch has been selected (master for fixes, next for
features)
[ ] Consistency across platforms for structures or concepts added or modified
[ ] Consistency between the changeset and the goal stated above
[ ] Internal consistency with the rest of the library - is there any overlap between existing interfaces and any which have been added?
[ ] Usage friction - is the proposed change in usage cumbersome or complicated?
[ ] Performance and complexity - are there any cases of unexpected O(n^3) when iterating, recursing, flat mapping, etc?
[ ] Concurrency concerns - if components are accessed asynchronously, what issues will arise
[ ] Thoroughness of added tests and any missing edge cases
[ ] Idiomatic use of the language

... removing the root-level Gemfile.lock

Good info, thanks, TIL.  Changes made and pushed.


Render Scratch images (fixes #71)

This issue renders Scratch images within Markdown converted by Kordac, using the Gulp script to render Scratch SVGs. There is an issue with Scratch files being watched by the Gulp script, see #72.

Justification of PR: The bug doesn't impede the rendering of Scratch files, but limits our ease in using the Gulp script. If the bug didn't render the files, then I wouldn't accept the PR.

okies, happy with that. Will approve once that code is moved to it's own function.


implement p2p repo

implement p2p repo

Pull Request Test Coverage Report for Build 618

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at ?%

Totals

Change from base Build 619:
0.0%

Covered Lines:

Relevant Lines:
0

💛  - Coveralls


Train and mIOU on ShapeNet

Nice job! could you also provide the training script?
I also have a question concerning the ShapeNet taxonomy. Which json file did you use?
I received an error message while evaluating on Shapenet.  " sample_count = len(taxonomy[self.dataset_type]) KeyError: 'test'"

Hi,
I have shared the training code in the repository.
About the json file for ShapeNet taxonomy, we downloaded the file from ShapeNet website.
I also provide in the repository.
Please ensure that the directory is under "dataset/ShapeNet".
Thanks

Thank you very much!
Lastly, it appears that the file loss.py is missing. Could you also share this one?
ModuleNotFoundError: There is no module called 'utils.loss'.


Dealing with warnings in test-compilation of examples

(Continues discussion in commit e01b3ca)
Some examples get warnings when test-compiled. Most are of this kind
WARNINGS for /home/jmerelo/Code/forks/perl6/doc/EVAL_76:
Useless use of constant string "..." in sink context (lines 4, 5)
ok 73 - doc/Language/5to6-perlfunc.pod6 chunk 12 starts with “q/.../” compiles

(You've probably realized I've added the starts with in 4eda9f8 to make the identication of said chunks easier)
This particular one relates to    q/.../;  # is still equivalent to using single quotes. which is a syntactically fine construct, but it's not so good according to this issue #1748 I raised some time ago: express intent with examples. My point is that warnings warn about something, and maybe we should pay some attention to them.
Besides, there are not so many, and they can be dealt with easily. It can help improve the documentation too. Probably not a priority, but useful anyway.
Another option is to add :skip-test to those pieces of code, and of course to turn warnings into errors.

Fair enough. I'll close the issue then, unless you want to keep it open as a reminder to update the example compiler. Right now there are only two types of warnings: one is that one illustrated above and the other is Space is not significant here;


Add OVPN_COMPANY to Env Vars

I just setup two-factor auth with OTP, which is awesome... however I noticed that ovpn_otp_user is not setting the -i (issuer) option.  This results in a random label like a12345678 being listed in Google Authenticator... where ideally this should be something like company name.
Having an optional OVPN_COMPANY environment var, and then passing that as -i $OVPN_COMPANY with ovpn_otp_user would be a nice addition.

+1, that random code would make the users so confused if they use lots of OTP/issuers.


Create Basic Enemy IA

CReate a basic IA for enemy based on 2 sensors:

distance sensor trigs the enemy to follow its target (mainly the player) when the distance between enemy and target is lower than the sensor distance,
view Sensor trigs off the following action of the target when distance between enemy and target is greater than view sensor value.

Added a EnemyBehavior basic component to b eadded natively into Sample Enemy game object.


[Bug] easymde is not using basset

Bug report
What I did
I use easymde in my CrudController. I am also using a Content-Security-Policy.
What I expected to happen
I expect the editor to be loaded properly.
What happened
The editor does not load properly because the asset is blocked by content security policy. So it looks like the assets of the editor are not properly loaded via Backpack Basset.
What I've already tried to fix it
I figured out that it was loaded from the following file:

Is it a bug in the latest version of Backpack?
After I run composer update backpack/crud the bug... is it still there? => Yes
Backpack, Laravel, PHP, DB version
When I run php artisan backpack:version the output is:
### PHP VERSION:
PHP 8.1.11 (cli) (built: Sep 28 2022 11:08:17) (ZTS Visual C++ 2019 x64)
Copyright (c) The PHP Group
Zend Engine v4.1.11, Copyright (c) Zend Technologies

### LARAVEL VERSION:
<IP_ADDRESS>

### BACKPACK PACKAGE VERSIONS:
backpack/basset: 1.2.1
backpack/crud: 6.2.3
backpack/generators: v4.0.2
backpack/pro: 2.0.15
backpack/theme-tabler: 1.1.1

Hey @BernhardK91 thanks for the report. 🙏
I've just tagged Backpack/PRO 2.0.18 that fixes this. Our repository should pick the new version in the next couple hours and you will be able to get the fix with a composer update backpack/pro.
Cheers


feat(onboarding): [sc-11513] increase k8swatcher memory limit

Story details: https://app.shortcut.com/groundcover/story/11513

@nitzangr you should be explicit about values as it should override different scenarios


Week view events

I have a particular case where all my events are only one day long and I was wondering if there is any way to display the events in week view  in the same line versus cascade? If there is not such an option can you please guide me what should I change to do this like an option for one day events? Thanks.

Hi @iulianmihai,
I tried editing your week-days.html template, is this how it suppose to look like?

@ErathiaChia yes, looks good like that.

@ErathiaChia this is how looks in my app


Fix test

Fix for the test failure

https://github.com/wso2-extensions/identity-inbound-auth-oauth/pull/2642

Successful dependency updater
https://github.com/wso2/product-is/actions/runs/12173399826


Update qiskit-ibm-runtime to 0.21.0.

Solves https://github.com/CQCL/pytket-qiskit/issues/282

Waiting for https://github.com/CQCL/pytket-qiskit/issues/278 to be solved, will reopen when that is available

@cqc-alec It would be good to check if the xfail is required, from my understanding it might be possible to remove it. When that is checked, feel free to merge this.

Seems it is still required:
============ 86 passed, 27 skipped, 1 xfailed, 4 warnings in 19.95s ============


Inaccurate logout times with multiple sessions by the same user

The behavior for tracking a user's log out time needs to be updated to account for multiple sessions by the same user.
Currently, when a user logs out, the most recent AccessLog row has its logout_time set to the current time. (See https://github.com/django-security/django-axes/blob/1.3.6/axes/signals.py#L26-L33)
However, if there are multiple sessions open, this simple logic may set the incorrect record.
Possible solution
A session_key field could be added to AccessLog to allow tracking of the login session in watch_login. Then the logout signal handler should look up the correct AccessLog row using session_key.

Sounds reasonable, can you elaborate a PR?

Hi,
I haven't looked at this issue in over two years but I just briefly checked the source for the latest version, this still seems to be an issue.

Cool, can you please help us elaborating a PR ?

Unfortunately, I'm not working on integrating django-axes with our project anymore and currently don't have the time to do a PR.
If I get a chance to come back to this, I'll open a PR.


Newer improved version

Improved README
Now delete method may be undefined
No using of version_names method (as it is deprecated)
Made small refactoring

I'm not sure about versions.
With rails_admin (1.4.2) and shrine (2.12.0) it works perfectly

rails_admin will support shrine soon, starting from v2


Pulsar throws NPE when closing consumer

This happens when Pulsar is not able to create reader for some reason while fetching metadata and tries to close it. Adding a null check should prevent this error.

Codecov Report

Merging #8913 (b3e4cf9) into master (7024a6d) will decrease coverage by 3.30%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #8913      +/-   ##
============================================
- Coverage     69.72%   66.42%   -3.31%
+ Complexity     4856     4670     -186
============================================
  Files          1809     1356     -453
  Lines         94331    68480   -25851
  Branches      14069    10690    -3379
============================================
- Hits          65777    45490   -20287
+ Misses        23974    19748    -4226
+ Partials       4580     3242    -1338

Flag
Coverage Δ

integration1
?

integration2
?

unittests1
66.42% <ø> (+0.03%)
:arrow_up:

unittests2
?

Flags with carried forward coverage won't be shown. Click here to find out more.

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


"Year" marker character is missing for Chinese/Japanese/etc

In the Japanese language, moment().format('YYYY MMM') should return something like "2016年 3月", but it returns "2016 3月"
It seems like examples on the site have this problem as well:
moment().format('MMMM Do YYYY, h:mm:ss a');  // 三月 15日 2016, 4:56:42 下午 moment().format("MMM Do YY");               // 3月 15日 16
This issue is very similar to https://github.com/moment/moment/issues/2807.

@baryon @suupic @zenozeng @XueWei - Thoughts?

hokei is right, patch please

I see.  Yes, that seems correct, as the local-specific formatters already include this.

Thank you, that's what I will do!

Is there any update on this issue?

How about some more locale-specific formatters to cover this case? If I could call moment().format('LY') to get the year with or without the 年, without my having to manually parse the locale and decide whether or not to add it?


Avoid rewrite html charset

Coverage increased (+16.1%) to 84.0% when pulling 9159dd2f58260f1b438370c37648317266adfcf5 on next into 4c17485ce2a660c5ae9d21294b7d42e16edf417f on master.

Coverage increased (+16.1%) to 84.0% when pulling 9159dd2f58260f1b438370c37648317266adfcf5 on next into 4c17485ce2a660c5ae9d21294b7d42e16edf417f on master.


Commercial Use

Provide a description of requested docs changes
We would like to know if we can install and use PowerToy(s) on a commercially owned machine. We just want to use the utilities, not to try and develop anything that could be resold or anything like that. The TOU at https://docs.microsoft.com/en-s/windows/powertoys/ leads me to believe that you can't install and use the tools on/in a commercial environment so I wanted to double check before we decide if we are going to make these utilities available for employees.
Thanks!

Yup, just follow the license (https://github.com/microsoft/PowerToys/blob/master/LICENSE) and you're fine.

Thanks! I saw the reference to a 'person' however there is no reference to a business, so am I understanding correctly that it cannot be used by a business?

MIT license does allow commercial usage.


Incorrect calculation of a VM memory

I create VM with the specification:
...
    resources:
      requests:
        memory: 64Mi
...

I assume that VM domain will have 64Mi of memory, but it has 65Mi
</metadata>
  <memory unit='KiB'>66560</memory>
  <currentMemory unit='KiB'>66408</currentMemory>

When we talk about regular memory, it does not really important, but in case of hugepages, it will fail to start a VM at all.
I think the problem occurs under quantity conversion
func QuantityToMegaByte(quantity resource.Quantity) Memory {
	return Memory{
		Value: uint(quantity.ToDec().ScaledValue(6)),
		Unit:  "MB",
	}
}

Good catch!

Assigning this to myself to hand it off.

/assign-to mfranczy

@cynepco3hahue isn't because we add a memory overhead?
Did you request any cpus as well?

@vladikr We calculate memory overhead for a virt-launcher pod, a VM still must receive the value that we specified under VM spec.
No I did not requested CPU's.

As @cynepco3hahue mentioned before, there is a problem with
Value: uint(quantity.ToDec().ScaledValue(6))
Unit:  "MB",

if you will request let's say 67108864 bytes of memory (which is equal to 64MB) then you will receive different value because of scaling and rounding.
To resolve that problem i suggest to change it to:
Value: uint64(quantity.AsInt64())
Unit:  "B",

and pass memory size in bytes to have exact size which you requested.
It will require change as well in Memory.Unit type from uint to uint64
I checked that solution quickly by changing scaling to 0
Value: uint(quantity.ToDec().ScaledValue(0))
Unit: "B"

and it works, below result from my virtual machine:
...
<memory unit='KiB'>65536</memory>
<currentMemory unit='KiB'>65536</currentMemory>
<vcpu placement='static'>1</vcpu>
...

@cynepco3hahue @fabiand any suggestions or thoughts to this?
If not I will create PR with updated tests

@mfranczy No objections from my side

Sounds promising, I'd expect some test to the edge cases :)

@fabiand We have some common test for the converter, we just need to change it, from:
var convertedDomain = fmt.Sprintf(`<domain type="%s"
...
<memory unit="MB">9</memory>
...

to
var convertedDomain = fmt.Sprintf(`<domain type="%s"
...
<memory unit="MB">8</memory>
...

I wonder if you want to add a new test, to cover even and uneven numbers.

If you don't mind I think I can add some tests for memory calculations, like checking if you are receiving exactly this what you requested in schema, although I don't have big picture and maybe it doesn't make sense?

I think it makes sense, a special when you can specify different quantities under memory request(Mi, Gi, M, G,... see https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/ for the full list)

I have prepared PR for this issue with extended tests for vm memory calculation.

Closed with #1106


Add support for KCP connection statistics collector

Hi,
The KCPTUN tool has support for printing the data from the connection statistics collector included in the KCP protocol. This is a function incorporated internally inside the kcp.go implementation.
I suggest to replicate this for logging the status of the KCP connection.
I see that only minimal changes are required:

Add the function "snmpLogger": http://github.com/xtaci/kcptun/blob/master/server/main.go#L376
And the "signal.go" interface: http://github.com/xtaci/kcptun/blob/master/server/signal.go

You agree?

The xtaci/kcp-go library has changed a lot since I used it, so the better choice is to merge the latest commits.

Hi @ginuerzh ,
Can you, please, release a version 2.4rc1 with last commits?
I see the branch 2.4 in development with the updated vendor "kcp-go.v2" and I like to test it.
Another question: This 2.4 branch has the statistics of the KCP connection?
Thank you!

No, I just updated the dependent libraries, some new features have not yet been merged.

Hi @ginuerzh ,

No, I just updated the dependent libraries, some new features have not yet been merged.

But the updated library improves the KCP connection? In this case, I like to test it. ;)

I will merge the features this weekend, and a dev version will be released.

I will merge the features this weekend, and a dev version will be released.

Great! Thank you!

The latest dev version has been released, you can test the kcp now.


Empty Graph is getting generated

🐛 Describe the bug
Empty Graph is getting generated each time.
My Modified README file
Dependency Diagram
```mermaid
%%{
  init: {
    'theme': 'neutral'
  }
}%%

graph LR

## Gradle Wrapper

distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-7.5.1-all.zip
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists

## 📱 Tech info
 - Android Studio Electric Eel | 2022.1.1 Patch 2
 - Mac OS: 13.3 (22E252)

Hey! Can you please run ./gradlew projects and post the output?
Ty.

Configure project :
Build was configured to prefer settings repositories over project repositories but repository 'Google' was added by build file 'build.gradle'
Build was configured to prefer settings repositories over project repositories but repository 'BintrayJCenter' was added by build file 'build.gradle'
Build was configured to prefer settings repositories over project repositories but repository 'MavenLocal' was added by build file 'build.gradle'
Build was configured to prefer settings repositories over project repositories but repository 'maven' was added by build file 'build.gradle'
Build was configured to prefer settings repositories over project repositories but repository 'maven2' was added by build file 'build.gradle'
Build was configured to prefer settings repositories over project repositories but repository 'maven3' was added by build file 'build.gradle'
Build was configured to prefer settings repositories over project repositories but repository 'maven4' was added by build file 'build.gradle'

Configure project :app
WARNING:The option 'android.useDeprecatedNdk' is deprecated.
The current default is 'false'.
It has been removed from the current version of the Android Gradle plugin.
NdkCompile is no longer supported
WARNING:The option 'android.enableR8' is deprecated.
It was removed in version 7.0 of the Android Gradle plugin.
Please remove it from gradle.properties.
Warning: The 'kotlin-android-extensions' Gradle plugin is deprecated. Please use this migration guide (https://goo.gle/kotlin-android-extensions-deprecation) to start working with View Binding (https://developer.android.com/topic/libraries/view-binding) and the 'kotlin-parcelize' plugin.
Build was configured to prefer settings repositories over project repositories but repository 'maven5' was added by build file 'app/build.gradle'
Build was configured to prefer settings repositories over project repositories but repository 'Google2' was added by build file 'app/build.gradle'
Build was configured to prefer settings repositories over project repositories but repository 'MavenRepo' was added by build file 'app/build.gradle'
Build was configured to prefer settings repositories over project repositories but repository 'flatDir' was added by build file 'app/build.gradle'
WARNING:DSL element 'dexOptions' is obsolete and should be removed.
It will be removed in version 8.0 of the Android Gradle plugin.
Using it has no effect, and the AndroidGradle plugin optimizes dexing automatically.
WARNING:DSL element 'dexOptions' is obsolete and should be removed.
It will be removed in version 8.0 of the Android Gradle plugin.
Using it has no effect, and the AndroidGradle plugin optimizes dexing automatically.
WARNING:Using flatDir should be avoided because it doesn't support any meta-data formats.
Values of variant API AnnotationProcessorOptions.arguments are queried and may return non final values, this is unsupported
Values of variant API AnnotationProcessorOptions.arguments are queried and may return non final values, this is unsupported
Values of variant API AnnotationProcessorOptions.arguments are queried and may return non final values, this is unsupported
Values of variant API AnnotationProcessorOptions.arguments are queried and may return non final values, this is unsupported
Values of variant API AnnotationProcessorOptions.arguments are queried and may return non final values, this is unsupported
Values of variant API AnnotationProcessorOptions.arguments are queried and may return non final values, this is unsupported
Values of variant API AnnotationProcessorOptions.arguments are queried and may return non final values, this is unsupported
Values of variant API AnnotationProcessorOptions.arguments are queried and may return non final values, this is unsupported
Values of variant API AnnotationProcessorOptions.arguments are queried and may return non final values, this is unsupported
Values of variant API AnnotationProcessorOptions.arguments are queried and may return non final values, this is unsupported
Values of variant API AnnotationProcessorOptions.arguments are queried and may return non final values, this is unsupported
Values of variant API AnnotationProcessorOptions.arguments are queried and may return non final values, this is unsupported
Values of variant API AnnotationProcessorOptions.arguments are queried and may return non final values, this is unsupported
Values of variant API AnnotationProcessorOptions.arguments are queried and may return non final values, this is unsupported
Values of variant API AnnotationProcessorOptions.arguments are queried and may return non final values, this is unsupported
Values of variant API AnnotationProcessorOptions.arguments are queried and may return non final values, this is unsupported
Values of variant API AnnotationProcessorOptions.arguments are queried and may return non final values, this is unsupported
Values of variant API AnnotationProcessorOptions.arguments are queried and may return non final values, this is unsupported
Values of variant API AnnotationProcessorOptions.arguments are queried and may return non final values, this is unsupported
Values of variant API AnnotationProcessorOptions.arguments are queried and may return non final values, this is unsupported
Values of variant API AnnotationProcessorOptions.arguments are queried and may return non final values, this is unsupported
Values of variant API AnnotationProcessorOptions.arguments are queried and may return non final values, this is unsupported
Values of variant API AnnotationProcessorOptions.arguments are queried and may return non final values, this is unsupported
Values of variant API AnnotationProcessorOptions.arguments are queried and may return non final values, this is unsupported
Values of variant API AnnotationProcessorOptions.arguments are queried and may return non final values, this is unsupported
Values of variant API AnnotationProcessorOptions.arguments are queried and may return non final values, this is unsupported
Values of variant API AnnotationProcessorOptions.arguments are queried and may return non final values, this is unsupported
Values of variant API AnnotationProcessorOptions.arguments are queried and may return non final values, this is unsupported
Values of variant API AnnotationProcessorOptions.arguments are queried and may return non final values, this is unsupported
Values of variant API AnnotationProcessorOptions.arguments are queried and may return non final values, this is unsupported
app: 'annotationProcessor' dependencies won't be recognized as kapt annotation processors. Please change the configuration name to 'kapt' for these artifacts: 'androidx.annotation:annotation:1.0.0', 'com.github.bumptech.glide:compiler:4.8.0'.

Task :projects

Root project 'doorapp-consumer'
Root project 'doorapp-consumer'
--- Project ':app'
To see a list of the tasks of a project, run gradlew :tasks
For example, try running gradlew :app:tasks
Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

It looks like you only have a single module:
--- Project ':app'

You need more modules for this plugin to be useful for you.
For instance, on this project  I get this when running the same command:
Project ':modules'
+--- Project ':modules:app'
|    +--- Project ':modules:app:main'
|    \--- Project ':modules:app:playground'
+--- Project ':modules:core'
|    +--- Project ':modules:core:common'
|    +--- Project ':modules:core:design-system'
|    +--- Project ':modules:core:footballdata'
|    \--- Project ':modules:core:reddit'
\--- Project ':modules:features'
     +--- Project ':modules:features:match-day'
     \--- Project ':modules:features:match-thread'


Add idr0093, idr0097 and idr0098

See title.
I had to skip diskusage for idr0093, but strangely it still gave me a value for Size, just the number of files is missing. I'll try estimate it via omero fs usage on Plate level for a few plates.
Also releases.tsv still needs to be updated.

Numbers look good.
If the disk usage command is skipped, my memory is that the stats calculation code makes a best effort to computing the size of the pixel data from the database i.e. using the pixel dimensions + the pixel type per image. Obviously this calculation ignores a number of factors including sub-resolutions and everything related to the file format esp. file compression.
@dominikl this PR is still in draft mode, are you expecting to push additional changes or should we merge and adjust in follow-ups?

I can't get the number of files for idr0093. If someone else can fill them in (and add them to the respective field in releases.tsv too)...

idr0093 number of files added. Thanks @joshmoore !

Thanks all. We can always come back to the estimation of the file size for idr0093 post release


Insert Date field is required!

After latest update Serenity.Web 3.12.0.
While inserting new row, System prompt for error message "Insert Date field is required!" Which is part of interface on respective rows.
Additionally, all Not null -read only fields on form are prompted error to input field while saving.
Please advise.

Do you have NotNull on that field? If you are setting InsertDate yourself somewhere like SetInternalFields etc, you'll need to add [Insertable(false)] to the field or remove NotNull.
In older versions there was a bug that didn't validate NotNull/Required constraint for non-string fields properly.

Yes, Its not null field on insert date.  which was updating though IInsertLogRow.
So , should we remove Not null?

Ok thanks for update.

but why is this happening before SetInternalFields?
I have behaviour, that sets internal fields, but it's not triggered before validation

If you are setting a field in SetInternalFields it is not a [NotNull] field, or you have to add Insertable(false) or Updatable(false) or both.
This was working as it is now for all String fields, it wasn't working for non-string fields so far, we just fixed the bug, so this is how it should have been working.


Integrate Netlify CMS

It's time to integrate this website with Netlify CMS! Will probably do this during the livestream I promised.
Reference implementation: https://github.com/netlify-templates/gatsby-starter-netlify-cms
Todo

[ ] Move all post images to /static/uploads

Bonus: Enable Git LFS?

[ ] Enable gatsby-remark-relative-images to let gatsby-remark-images resolve to absolute paths
[ ] Install Netlify CMS + configure for posts

[ ] Article
[ ] Bookmark
[ ] Jam
[ ] Note
[ ] Photo
[ ] Video

Closing this. Still re-evaluating the CMS choices we want.


XGBoost & LightGBM on Apple M1 & M2

XGBoost and LightGBM won't compile / segfault on Apple M1s (and M2s) aarch64. The issue comes from openmp which appears to break and requires special workarounds which seem to be unreliable.
XGBoost issue: https://github.com/dmlc/xgboost/issues/7039

It looks like xgboost expects libraries to be linked from places that brew doesn't install by default.
This fixed it on my mac, and allows building:
brew install openblas
sudo mkdir -p /usr/local/opt/openblas
sudo ln -s /opt/homebrew/Cellar/openblas/0.3.21/lib /usr/local/opt/openblas/lib

brew install libomp
sudo mkdir /usr/local/opt/libomp
sudo ln -s /opt/homebrew/Cellar/libomp/15.0.2/lib /usr/local/opt/libomp/lib

cd /usr/local/lib
sudo ln -s /opt/homebrew/opt/libomp/lib/libomp.dylib .

Did you try training something with XGBoost? I remember being able to build it at some point, but running segfaulted.

Yep. Training and predictions work.
On Tue, Oct 18, 2022 at 5:50 PM Lev Kokotov @.***>
wrote:

Did you try training something with XGBoost? I remember being able to
build it at some point, but running segfaulted.
—
Reply to this email directly, view it on GitHub
https://github.com/postgresml/postgresml/issues/364#issuecomment-1283196722,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACDNHOYW3XE2JXN3ZN5VKLWD5AWDANCNFSM6AAAAAAQ563U7A
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


Change url for docker-volume-glusterfs

File: engine/extend/legacy_plugins.md
https://github.com/calavera/docker-volume-glusterfs is no more maintained
Can you update the page with one of fork ?
ex: https://github.com/amarkwalder/docker-volume-glusterfs

Closing this ticket due to its age, and the impending refactor. If you think this is in error, feel free to reopen. Thanks!


Correct the links.

Correct the links.

Dear @jellodiil,
I have a minor update for the link (the link is not found). Please help me to review the PR.
Thanks,

Lam


jira: if no minimum severity configured, findings are never pushed

if no minimum severity is configured in system settings, findings are never pushed

hmm, I think I had opened something on that at some point. But indeed, probably still holds true.

I thought so to, but look at the code it still goes wrong. maybe because the fixtures for the unit tests are having null as value there

Maybe. I think the simple "fix" I had made was the have the default value set to Low instead of null back in the days.

fixed in dev, so 1.10.0


Fixes issues with  and l10n

Translation strings were split when a <p> contains <br> and <a>.
See https://www.transifex.com/projects/p/elementary-mvp/translate/#es/get-involved/40056505

Thank you very much for the fix, @emersion :grinning:

@Fitoschido You're welcome ;-)


PSA: backport maintenance releasse 1.x

I have created a new branch 1.x specifically for this purpose. So that we can backport important fixes to 1.x (anything after 1.7.0 will be maintenance release). While we don't want to backport all changes, if users are not comfortable using 2.x alpha for up-to-date Fetch Spec compatibility, then 1.x continue to be an option.

1.x backport is no longer being worked on as 2.x stable releases, so closing this.


Adding bower package to a secondary file without having it removed from main?

How can I add a bower package to a secondary file without having it removed from the main file?

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/36156436-adding-bower-package-to-a-secondary-file-without-having-it-removed-from-main?utm_campaign=plugin&utm_content=tracker%2F8853550&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F8853550&utm_medium=issues&utm_source=github).

on the secondary file include the bower js in a vendor object
...
"secondary.js": {
    "vendor": [
        "../bower_components/package/package.js"
    ]
},
...

this works for js files but does not want to work for css files.


Concurrent vm

Coverage decreased (-0.06%) to 62.856% when pulling e52a2b7142525b86445112b7a3a203595da9096b on concurrent-vm into 404a0d07855d8987fdc63b3d5fb7d1c982aabb2f on master.


async/await feature request

python3.5 async/await feature will be a good feature to see split the issue https://github.com/pybee/voc/issues/245 seperate.
clojurescript like csp feature is another way to solve instead of callbacks

I would like to work on this project. Can I get details about it ?


Mismatch of calendar week and corresponding row of days

Before Submitting: Double-check that you are running the latest version of the plugin. The bug might have already been fixed 😄

Describe the bug
The week row doesn't correspond with the week it should be aligned to. While week 52 of the year should be from 2021-12-27 until 2022-01-01 it is aligned with the week before that (2021-12-20 to 2021-12-26).

This might just be a visual bug, however, there is more to it. It seems that the creation by click doesn't translate the calendar week to determine the date range but takes the aligned week row.
This leads to following error:

The 2nd week of 2022 is supposed to be week afterward. https://weeknumber.com/2
Steps to reproduce
Requires Periodic Notes.

Create a weekly template that makes use of the weekday formatting  {{monday:YYYY-MM-DD}} - {{sunday:YYYY-MM-DD}}
Link the weekly template to periodic notes
Create the weekly template via the calendar by pressing the desired week
Error

Expected behavior
In my opinion, the best approach would be to align the weeks properly to their corresponding week row so there isn't any confusion
Screenshots

Environment (please specify)
OS
[Windows/macOS]
Obsidian Version (e.g. v0.10.6)
v0.13.14
Theme (if applicable):
Obsidian Nord, but also the same with the main theme

The confusion is the incorrect determination of the FIRST week of the year.
According to link in README.md concerning week numbering wiki page https://en.wikipedia.org/wiki/Week#Week_numbering where it says:
Determining Week 1
In practice week 1 (W01 in ISO notation) of any year can be determined as follows:

If January 1 falls on a Monday, Tuesday, Wednesday or Thursday, then the week of January 1 is Week 1.
If January 1 falls on a Friday, Saturday, or Sunday however, then January 1 is considered to be part of the last week of the previous year and Week 1 will begin on the first Monday after January 1.

So in 2022 Jan1 is Saturday and so the first week should be, Jan 3 to 9.
The calendar plugin first week is Dec 27 to Jan 2 tho.
Hope it helps with debugging works. Thanks!

This bug messes up the week numbers on the Calendar for 2022 and seems to trickle down to Periodic Notes using the wrong week number as well.
According to the ISO-8601 standard, the first week of the year is the week that contains that year's first Thursday (='First 4-day week').

Hi @DM1NIK  and @xeeban,
I discovered, that changing locale settings is what is governing this 'bug'.
For me, the cs is working as stated on the wiki and in ISO-8601. Since I'm in Czech Rep. and cs is our locale it is logical, but I've totally missed this setting for the first time.
Hope it helps!

Setting mine to en-gb seems to work, but it feels weird to have to set it to that as I am not in the UK

I agree with above posters. The issue is that the first week of the year is incorrectly determined with respect to the ISO standard. If we fix that calc it should fix the problem. Thanks to @xeeban on the en-gb fix (sadly en-ca did not work... :-) ). I used that as a workaround so as not to have this drive me crazy. Lol.  =]

Still not solved


[Feature request]: Wish it could remove a default setting for a specific file extension or program language

Currently, it conflicts with the extension AutoHotkey v2 Language Support.

The extension of the picture can automatically distinguish the syntax for the same extension file *.ahk, and then apply a dedicated icon for AutoHotkeyV2 while another icon for AutoHotkeyV1 which is the old icon for old Autohotkey.
But with Material Icon Theme installed, all above will not work, but apply its own icon to all of the **.ahk instead.
I came up with a very simple and effective idea:
Just add an option or setting to remove its own default icon setting for .ahk.
It's perhaps like that:

I think this feature is very necessary, not only for AutoHotkey but also for any other language whose icon has got controled with its dedicated language extension.
This feature could avoid Material Icon Theme interfering other extensions.

or just false.

It's a valid request. The logic of the extension already covers this by having a "disabled" flag at the icon associations but it's not exposed yet so that it can be adjusted via settings. I think we can enhance the settings at this point to make that possible.

It's a valid request. The logic of the extension already covers this by having a "disabled" flag at the icon associations but it's not exposed yet so that it can be adjusted via settings. I think we can enhance the settings at this point to make that possible.

I tested it just now.  But currently, it does not work.  All the icons of *.ahk turn out to be blank.

Is there anything I missed?  Wait for your good news. 👍

Is there anything I missed? Wait for your good news. 👍

The disabled "flag" is implemented internally, but it's not exposed in the public API of the extension as a setting.

Yeah sorry for the misunderstanding, it's currently not possible to adjust it 🫣

Although exposing the disabled option is a great idea, I was thinking that maybe we can also provide two different icons for this case. The extension probably defines two separated language ids for each version of the language (I haven't checked it though).

Although exposing the disabled option is a great idea, I was thinking that maybe we can also provide two different icons for this case. The extension probably defines two separated language ids for each version of the language (I haven't checked it though).

yeah that would be even better to make sure that these icons still fit to the other Material Design icons.
@PythonYunfei Can you give an example how these icons look like - I mean the icons which are provided by the extension?

@lucas-labs @PKief
Thank you for the clarification👍

Although exposing the disabled option is a great idea, I was thinking that maybe we can also provide two different icons for this case.

yeah that would be even better to make sure that these icons still fit to the other Material Design icons. @PythonYunfei Can you give an example how these icons look like - I mean the icons which are provided by the extension?
This is the icon for the new AutoHotkey i.e. V2 version:

The extension probably defines two separated language ids for each version of the language (I haven't checked it though).
The language id of the new AutoHotkey is ahk2. The language id of the old AutoHotkey is ahk.

When VSCode is starting, the extension AutoHotkey v2 Language Support will apply the new icon to all **.ahk files firstly. But when one of the **.ahk files is opened, the extension will distinguish the file's syntax and switch it to the old AutoHotkey icon, if the syntax is old AutoHotkey.


Refactor dumpindex package

@Peilin-Yang this is for you:
We seem to have inadvertently created anserini.DumpIndex and anserini.dumpIndex packages. I don't think we need a separate package - refactor and move everything into anserini.index?

@lintool PR sent.

@Peilin-Yang Thanks!


navigation bar added in header

Issue #350

Convert navbar link to black and then will merge it.

@anushbhatia  done 👍

Convert navbar link to black and then will merge it.

@anushbhatia  done 👍


Add package to nixpkgs

currently the installation is not ideally. (adding specific packages to the system and then sourcing the bashrc.)
I would prefer to have a package, that contains a bash script called: nixpkgs-review-checks which does the same as sourcing the bashrc and running nixpkgs-review.

I am currently working on the required changes to make everything work with nixpkgs-review-checks and a default.nix. If that is finished I think about adding it to nixpkgs.

https://github.com/jtojnar/nixpkgs-hammering is not in nixpkgs currently and I am hard depending on it but I think I can create a flake instead.

Any news here?

The tool is still very experimental and not ready to use for the broad public. I am not planning to upstream it.


Move standard libraries into std module

For example, math::abs should become std::math::abs.
Additionally, expand unqualified names in with module statements (eg. with module math)

Leaving cfg, schema, and sys as top level modules.


Forms do not provide action endpoint to call custom ask slot actions

Rasa version: 2.0.0a2
Rasa SDK version (if used & relevant):
Rasa X version (if used & relevant):
Python version: 3.6.8
Operating system (windows, osx, ...): Ubuntu 18.0.4
Issue:
When providing a custom action to ask for a slot in a 2.0 form, the call fails because it the action endpoint is not passed to the custom action. I reproduced this case easily with the formbot in the examples. I added this action:
class ActionAskCuisine(Action):
    def name(self) -> Text:
        return "action_ask_cuisine"

    def run(
        self,
        dispatcher: CollectingDispatcher,
        tracker: Tracker,
        domain: Dict[Text, Any],
    ) -> List[Dict[Text, Any]]:
        dispatcher.utter_message(template="utter_ask_cuisine")

        return []

in actions.py, and
actions:
  - action_ask_cuisine

in domain.yml, and changed nothing else. The action can be called if named directly in the rules but not if called by the restaurant form, getting the following result:
Error (including full traceback):
2020-08-26 16:45:44 DEBUG    rasa.core.actions.forms  - Request next slot 'cuisine'
2020-08-26 16:45:44 ERROR    rasa.core.actions.action  - The model predicted the custom action 'action_ask_cuisine', but you didn't configure an endpoint to run this custom action. Please take a look at the docs and set an endpoint configuration via the --endpoints flag. https://rasa.com/docs/rasa/core/actions
2020-08-26 16:45:44 ERROR    rasa.core.processor  - Encountered an exception while running action 'restaurant_form'. Bot will continue, but the actions events are lost. Please check the logs of your action server for more information.
2020-08-26 16:45:44 DEBUG    rasa.core.processor  - Failed to execute custom action.
Traceback (most recent call last):
  File "/home/kdery/.local/lib/python3.6/site-packages/rasa/core/processor.py", line 644, in _run_action
    events = await action.run(output_channel, nlg, tracker, self.domain)
  File "/usr/lib/python3.6/asyncio/coroutines.py", line 110, in __next__
    return self.gen.send(None)
  File "/home/kdery/.local/lib/python3.6/site-packages/rasa/core/actions/loops.py", line 29, in run
    events += await self.do(output_channel, nlg, tracker, domain, events)
  File "/usr/lib/python3.6/asyncio/coroutines.py", line 110, in __next__
    return self.gen.send(None)
  File "/home/kdery/.local/lib/python3.6/site-packages/rasa/core/actions/forms.py", line 586, in do
    tracker, domain, output_channel, nlg, events_so_far + events
  File "/usr/lib/python3.6/asyncio/coroutines.py", line 110, in __next__
    return self.gen.send(None)
  File "/home/kdery/.local/lib/python3.6/site-packages/rasa/core/actions/forms.py", line 424, in request_next_slot
    domain, nlg, output_channel, slot_to_request, temp_tracker
  File "/usr/lib/python3.6/asyncio/coroutines.py", line 110, in __next__
    return self.gen.send(None)
  File "/home/kdery/.local/lib/python3.6/site-packages/rasa/core/actions/forms.py", line 472, in _ask_for_slot
    output_channel, nlg, tracker, domain
  File "/usr/lib/python3.6/asyncio/coroutines.py", line 110, in __next__
    return self.gen.send(None)
  File "/home/kdery/.local/lib/python3.6/site-packages/rasa/core/actions/action.py", line 557, in run
    raise Exception("Failed to execute custom action.")
Exception: Failed to execute custom action.
2020-08-26 16:45:44 DEBUG    rasa.core.processor  - Action 'restaurant_form' ended with events '[]'.

Command or request that led to error:
rasa run actions&
rasa shell -m models --endpoints endpoints.yml --debug
...
Your input -> I want to find a restaurant

Content of domain file (domain.yml) (if relevant): (Same as formbot and modified as mentionned)
The problem seems to be in the FormAction definition, right where I commented in the following code (although I didn't try it). I could submit a PR, unless there is some kind of ramification I don't see/know about.
class FormAction(LoopAction):
    ...
    async def _ask_for_slot(
        self,
        domain: Domain,
        nlg: NaturalLanguageGenerator,
        output_channel: OutputChannel,
        slot_name: Text,
        tracker: DialogueStateTracker,
    ) -> List[Event]:
        logger.debug(f"Request next slot '{slot_name}'")

        action_to_ask_for_next_slot = action.action_from_name(
            self._name_of_utterance(domain, slot_name), None, domain.user_actions # None should be self.action_endpoint
        )
        events_to_ask_for_next_slot = await action_to_ask_for_next_slot.run(
            output_channel, nlg, tracker, domain
        )
        return events_to_ask_for_next_slot

Thanks for the issue, @tabergma will get back to you about it soon!
You may find help in the docs and the forum, too 🤗

same issue here.

@Ghostvv @wochinge Can you please verify that this can happen?

Just verified that this is a bug! Thanks for trying out the new forms 🙏 Do you want to the PR or should I @NetBKarine ? The solution is as you pointed out to pass the self.action_endpoint instead of None.

@wochinge I just submitted the PR since I already had it ready. It's my first one on this repo, so tell me if I forgot something in the process.


Handle NameError exception if an invalid variable name reaches method_missing

When using sprockets and specinfra together, our project would occasionally run into problems when compiling assets due to specinfra attempting to create an instance variable with an invalid name. While I'm not entirely sure why this behavior would occur, it was more straightforward to patch specinfra than go down the rabbit holes to determine what was causing the two libraries to occasionally not play nicely together.
This change simply wraps the calls to #set_instance_variable and #get_instance_variable in a begin/rescue block. Please let me know if you would prefer to have this fixed in a different way, and I'll be happy to update.
Thanks!

Thanks.

Released as v2.11.6.


Schedule as JSON emits error

Traceback:
File "/home/daaray/.virtualenvs/pycon/local/lib/python2.7/site-packages/django/core/handlers/base.py" in get_response
  113.                         response = callback(request, *callback_args, **callback_kwargs)
File "/home/daaray/django/pycon/symposion/schedule/views.py" in schedule_json
  195.                 "abstract": slot.content.abstract.raw,

Exception Type: AttributeError at /2015/schedule/conference.json
Exception Value: 'unicode' object has no attribute 'raw'

As this was fixed by 5bff17a, I am going ahead and closing this issue now. Thanks for the fix!


question

hi there,
I forked this repo and added the Ios part, discovery and print.
the code is a mess but it's working great, how can I contribute to this repo on pub.dev?

just create a PR :)


Added plugin tailwind-scrollbar with examples

Added pretty scrollbars to some inner components with tailwind-scrollbar plugin.
Two examples : sidebar nav and TOC (see Calendar builder for scrollable TOC) :

Sidebar uses scrollbar scrollbar-w-2
TOC uses scrollbar-thin

I prefer the sidebar one (pretty much the same on Chromium based browser, but nicer on Firefox).
Check the doc for more info on the plugin : https://adoxography.github.io/tailwind-scrollbar/examples
Screenshots :
Chrome :

Firefox :

Thank you for the PR! We used to have stylized scrollbars, but I opted to remove them due to some weird browser behaviours. I also don't think it makes sense to add them to component examples using a TW plugin, since the plan is to sunset using tailwind on examples, and opting instead to only use CSS.
I'll be closing this, unfortunately, but I really do appreciate the effort!

Ahh I see! I was about to add them in CSS first but since the website is done with tailwind I tought I'd follow the path... (I'm not a tailwind user myself) Didn't knew you were going away!
Btw, I was adding examples for you to see how it would be applied on MeltUI site, not for example components for the lib.
Anyway, I understand, scrollbars are behaving pretty weird across different browsers and styling is unnecessary, but the default are so ugly in Chrome lol!
Thanks for your answer :) ✌


Rendering text with blending colors?

I'm too lazy to fill the text here, but I can post 2 pictures to compare:

First one, it looks is not blending the colors, it seems separated.
Second one, it does blend the colors.

Duplicate of https://github.com/zeit/hyper/issues/1968


Adding oisd.nl as an source

I'm using Energized Ultimate on AdGuard Home and works well!
The second blocklist source I'm using is oisd.nl (adblock-format - normal), there are some not detected urls there, I think it would be good if you include the list as well in the current list, since oisd.nl is really good, clean, almost no FP blocklist

Seems like user could subscribe as you have.  Why merge?

Same reason why /energized merges any other sources (see sources list), also osid.nl have a huge overlapping domains but still many unique ones

OSID is the gold standard for me. Love it. Huge number of lists but very few false positives. Both great community feedback and maintainer responses on the false positives that do slip through. A rare find!
Both Energized and OISD curate a blocklist from many sources, so just subscribe to both.
The creators of Energized are more than able to add sources that OISD uses that it lacks.

Personally, I use OISD + Energized (with some other blacklists, such as 1Hosts) all together.  Even though they cover mostly the same domains, there are some that only exist in one of the aggregated lists, and not the other.

OISD Basic list has been added.

@AdroitAdorKhan
why not the full version?


Update tokenlist - Add $WIF

Your token does not currently qualify for listing, please keep it up and continue building up liquidity/volume on TJ

Closing, please resubmit when your token surpasses 6 figures in liquidity


Ballerina language server does not provide resolving for ballerina standard libraries

Description:
Current ballerina language server implementation does not have resolving support (goto definition) for the references of ballerina standard library related methods and types.
Steps to reproduce:
Please use the following code snippet in VSCode and try Goto Definition for println() method.
import ballerina/io;

public function main() {
    io:println("Hello World");
}

Affected Versions:
0.983.0 and below
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

This has been implemented in the latest master. Hence closing the issue


improve default plugins

use json-stable-stringify replace JSON.stringify, as before same args maybe not available.

add retry option, now we can define the specific retry time and times.

Can you split these into 2 separate Pull Requests please?
I like your work on the retry plugin!
Why are you switching to json-stable-stringify?  JSON shouldn't be deterministic, and this ads some overhead that I'm not convinced we need.

Alright, I agree.

I have done, is it right ?

Looks good!
I'll merge it in.
Please add some more more tests:

test the Resque Retry Max Attempts
test that jobs really will clear the retry attempts

npm publish

<EMAIL_ADDRESS>

👍 Cool!
And I will add tests shortly.


Workbox 6.0.2 docs

R: @petele @philipwalton
This updates the generated Workbox docs to accompany the 6.0.2 release, and fixes the issue with the PrecacheInstallReportPlugin being inadvertently added to the top-level docs.

Whoops!
There were 103 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/tools/workbox/_shared/workbox-latest-version.html#L1 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/_shared/workbox-sw-cdn-url.html#L1 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/index-all.html#L246 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/index.html#L1244 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-background-sync.BackgroundSyncPlugin.html#L80 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-background-sync.Queue.html#L326 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-background-sync.html#L45 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-broadcast-update.BroadcastCacheUpdate.html#L208 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-broadcast-update.BroadcastUpdatePlugin.html#L103 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-broadcast-update.html#L95 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-build.html#L1377 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-build.html#L217 - Common typo found: 'node' Should it be 'Node'?
src/content/en/tools/workbox/reference-docs/latest/module-workbox-build.html#L229 - Common typo found: 'node' Should it be 'Node'?
src/content/en/tools/workbox/reference-docs/latest/module-workbox-build.html#L241 - Common typo found: 'node' Should it be 'Node'?
src/content/en/tools/workbox/reference-docs/latest/module-workbox-build.html#L255 - Common typo found: 'node' Should it be 'Node'?
src/content/en/tools/workbox/reference-docs/latest/module-workbox-build.html#L573 - Common typo found: 'node' Should it be 'Node'?
src/content/en/tools/workbox/reference-docs/latest/module-workbox-build.html#L585 - Common typo found: 'node' Should it be 'Node'?
src/content/en/tools/workbox/reference-docs/latest/module-workbox-build.html#L597 - Common typo found: 'node' Should it be 'Node'?
src/content/en/tools/workbox/reference-docs/latest/module-workbox-build.html#L611 - Common typo found: 'node' Should it be 'Node'?
src/content/en/tools/workbox/reference-docs/latest/module-workbox-build.html#L789 - Common typo found: 'node' Should it be 'Node'?
src/content/en/tools/workbox/reference-docs/latest/module-workbox-build.html#L801 - Common typo found: 'node' Should it be 'Node'?
src/content/en/tools/workbox/reference-docs/latest/module-workbox-build.html#L813 - Common typo found: 'node' Should it be 'Node'?
src/content/en/tools/workbox/reference-docs/latest/module-workbox-build.html#L827 - Common typo found: 'node' Should it be 'Node'?
src/content/en/tools/workbox/reference-docs/latest/module-workbox-build.html#L949 - Common typo found: 'node' Should it be 'Node'?
src/content/en/tools/workbox/reference-docs/latest/module-workbox-cacheable-response.CacheableResponse.html#L140 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-cacheable-response.CacheableResponsePlugin.html#L104 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-cacheable-response.html#L47 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-core.html#L234 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-expiration.CacheExpiration.html#L196 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-expiration.ExpirationPlugin.html#L154 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-expiration.html#L58 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-google-analytics.html#L110 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-navigation-preload.html#L84 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-precaching.PrecacheController.html#L382 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-precaching.PrecacheFallbackPlugin.html#L105 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-precaching.PrecacheRoute.html#L138 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-precaching.PrecacheStrategy.html#L342 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-precaching.PrecacheStrategy.html#L104 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-precaching.PrecacheStrategy.html#L156 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-precaching.PrecacheStrategy.html#L253 - Common typo found: 'it                 it' Should it be 'it'? If this is intentional you can comma separate to 'it, it' for better clarity.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-precaching.html#L502 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-range-requests.RangeRequestsPlugin.html#L49 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-range-requests.html#L93 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-recipes.html#L348 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-recipes.html#L296 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/tools/workbox/reference-docs/latest/module-workbox-routing.NavigationRoute.html#L124 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-routing.RegExpRoute.html#L99 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-routing.Route.html#L93 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-routing.Router.html#L344 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-routing.html#L363 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-strategies.CacheFirst.html#L255 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-strategies.CacheFirst.html#L69 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-strategies.CacheFirst.html#L166 - Common typo found: 'it                 it' Should it be 'it'? If this is intentional you can comma separate to 'it, it' for better clarity.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-strategies.CacheOnly.html#L254 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-strategies.CacheOnly.html#L68 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-strategies.CacheOnly.html#L165 - Common typo found: 'it                 it' Should it be 'it'? If this is intentional you can comma separate to 'it, it' for better clarity.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-strategies.NetworkFirst.html#L342 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-strategies.NetworkFirst.html#L102 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-strategies.NetworkFirst.html#L156 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-strategies.NetworkFirst.html#L253 - Common typo found: 'it                 it' Should it be 'it'? If this is intentional you can comma separate to 'it, it' for better clarity.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-strategies.NetworkOnly.html#L318 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-strategies.NetworkOnly.html#L132 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-strategies.NetworkOnly.html#L229 - Common typo found: 'it                 it' Should it be 'it'? If this is intentional you can comma separate to 'it, it' for better clarity.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-strategies.StaleWhileRevalidate.html#L331 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-strategies.StaleWhileRevalidate.html#L105 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-strategies.StaleWhileRevalidate.html#L145 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-strategies.StaleWhileRevalidate.html#L242 - Common typo found: 'it                 it' Should it be 'it'? If this is intentional you can comma separate to 'it, it' for better clarity.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-strategies.Strategy.html#L368 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-strategies.Strategy.html#L104 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-strategies.Strategy.html#L139 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-strategies.Strategy.html#L276 - Common typo found: 'it                 it' Should it be 'it'? If this is intentional you can comma separate to 'it, it' for better clarity.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-strategies.StrategyHandler.html#L512 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-strategies.StrategyHandler.html#L474 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-strategies.StrategyHandler.html#L415 - Common typo found: 'fo' Should it be 'of'?
src/content/en/tools/workbox/reference-docs/latest/module-workbox-strategies.html#L94 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-streams.html#L185 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-webpack-plugin.GenerateSW.html#L444 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-webpack-plugin.InjectManifest.html#L268 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-webpack-plugin.html#L51 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-window.Workbox.html#L688 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-window.Workbox.html#L37 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-window.Workbox.html#L94 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-window.Workbox.html#L110 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-window.Workbox.html#L117 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-window.Workbox.html#L131 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-window.Workbox.html#L257 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-window.Workbox.html#L267 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-window.Workbox.html#L317 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-window.Workbox.html#L318 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-window.Workbox.html#L319 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-window.Workbox.html#L320 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-window.Workbox.html#L337 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-window.Workbox.html#L347 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-window.Workbox.html#L407 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-window.Workbox.html#L417 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-window.Workbox.html#L538 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-window.Workbox.html#L548 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-window.Workbox.html#L592 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-window.Workbox.html#L609 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-window.Workbox.html#L620 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/tools/workbox/reference-docs/latest/module-workbox-window.html#L88 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/reference-docs/latest/module-workbox-window.html#L57 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/tools/workbox/reference-docs/latest/workbox.html#L279 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful


Prefix

Switch to substr to replace /^[a-z0-9]+-/ with ${var.prefix}-

Decided this is unnecessary. Closing.


[1.16-1.18, Bug] Lodestone compasses gained from SU Areas freak out

What am I gonna do!???

even more interesting
for me it points to world spawn

even more interesting
for me it points to world spawn

Occurs in 1.18 as Well

Renamed to follow new bug reporting (Only doing this for Bugs present across both versions)


Can this coder reproduce the results of the orgininal paper?

Thanks for your contribution. I'd like to confirm whether this work can reproduce the results of the paper.
I also have another question, the testing set of CNN/DAIL dataset have the separator of  , In testing stage, do these symbols need to be removed? I'm not sure if the experimental results of this paper remove these special symbols.

Hi, this is also the question I want to answer and this still requires a bit of work.
Regarding the preprocessing, I have not seen any mention of differences between the preprocessing of the training and validation sets and the preprocessing of the test set in the paper.

I have the same question, have you reproduce the results of the paper using this code?


Added comments for the fuctions

setup.py is a standard format used by all Python projects; it's not necessary to add such high level of commenting to it. Our setup.py is actually very simple compared to most other projects.
If you want to learn more about how setup.py works there is a great amount of detail here: https://docs.python.org/3.7/distutils/setupscript.html


unpickling error

Trying to run the script on python 3 using the following command:
run survey_classifier.py --size 10 --num_layers 5 --model_type GRU --survey_files data/macho/full.pkl --drop_frac 0.5 --lr 0.0001 --sim_type train
gives me an error related to unpickling in the joblib.load line.
Has the pickling been done using python2?
KeyError                                  Traceback (most recent call last)
/content/IrregularTimeSeriesAutoencoderPaper/survey_classifier.py in ()
104
105 if name == 'main':
--> 106     X, X_raw, Y, model, args = main()
4 frames
/content/IrregularTimeSeriesAutoencoderPaper/survey_classifier.py in main(args)
31     classes = ['RR_Lyrae_FM', 'W_Ursae_Maj', 'Classical_Cepheid',
32                'Beta_Persei', 'Semireg_PV']
---> 33     lc_lists = [joblib.load(f) for f in args.survey_files]
34     combined = [lc for lc_list in lc_lists for lc in lc_list]
35     combined = [lc for lc in combined if lc.label in classes]
/content/IrregularTimeSeriesAutoencoderPaper/survey_classifier.py in (.0)
31     classes = ['RR_Lyrae_FM', 'W_Ursae_Maj', 'Classical_Cepheid',
32                'Beta_Persei', 'Semireg_PV']
---> 33     lc_lists = [joblib.load(f) for f in args.survey_files]
34     combined = [lc for lc_list in lc_lists for lc in lc_list]
35     combined = [lc for lc in combined if lc.label in classes]
/usr/local/lib/python3.6/dist-packages/joblib/numpy_pickle.py in load(filename, mmap_mode)
596                     return load_compatibility(fobj)
597
--> 598                 obj = _unpickle(fobj, filename, mmap_mode)
599
600     return obj
/usr/local/lib/python3.6/dist-packages/joblib/numpy_pickle.py in _unpickle(fobj, filename, mmap_mode)
524     obj = None
525     try:
--> 526         obj = unpickler.load()
527         if unpickler.compat_mode:
528             warnings.warn("The file '%s' has been generated with a "
/usr/lib/python3.6/pickle.py in load(self)
1048                     raise EOFError
1049                 assert isinstance(key, bytes_types)
-> 1050                 dispatchkey[0]
1051         except _Stop as stopinst:
1052             return stopinst.value

Can you try {up,down}grading to joblib==0.11?

Update: actually the data is no longer present, but it's now mirrored at https://gitlab.com/cesium-ml/IrregularTimeSeriesAutoencoderPaper.

The same problem persists. Even after cloning from gitlab, I note that the
file size for data/linear/full.pkl hasnt changed.
Linn
On Sat, May 25, 2019 at 12:14 AM Brett Naul<EMAIL_ADDRESS>wrote:

Update: actually the data is no longer present, but it's now mirrored at
https://gitlab.com/cesium-ml/IrregularTimeSeriesAutoencoderPaper.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bnaul/IrregularTimeSeriesAutoencoderPaper/issues/3?email_source=notifications&email_token=AGJ7VZGV5BBCCDMOCDWAQL3PXAZQZA5CNFSM4HOZZSWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWGIZHY#issuecomment-495750303,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGJ7VZCEC7JHSF4KGEUOHV3PXAZQZANCNFSM4HOZZSWA
.


Created 1.21-15 docs

Issue #, if available:
closes #1025
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


Fix issue when using base64 encoded images in glTF loader

Fixes #5533

@bghgary Can you add it in the readme (for references) ? Thanks a lot

Oops, missed your comment, sorry. I will update the readme.


No map suggestions for base mods.

No maps suggested when you chose just base mods, not recipes. If map search was implemented only for recipes, than count this as suggestion :)

Yeah, woopsie. I recently re-added the ability to add base mods to the prio-list, but then forgot to adapt the optimal drop locations to apply to them as well. There should be a new release today once I get home -- only a few finishing touches left -- and I'll include this.