Problems with zoom

I have two actions, userEnableFocus and userDisableFocus.
I want to focus map on the user (marker) with zooming.
For now, I click on user in my sidebar and map focuses on user. I can change map position (navigation through dng) and all is ok. But with zoom param this trick doesn't work(when I disable focus) and zoom, if I understand, converts to 0 and I can see entire world.. What value for zoom should be used to keep zoom unchanged? undefined also not works (there are no zoom in this case). Or I should use another way?
        <GoogleMap
          style={ googleMapStyles }
          defaultCenter={ this.props.defaultCenter }
          defaultZoom={ this.props.defaultZoom }
          center={ this.props.center }
          zoom={ this.props.zoom }
          bootstrapURLKeys={{ key: GOOGLE_API_KEY }}
        >
 ....

function select(state) {
  let center = null
  let zoom   = null
  if (state.map.focusedUser !== null) {
    center = R.props(['lat', 'lng'], state.server.users[state.map.focusedUser].position)
    zoom = 17
  }
  return { center,    zoom }
}

Please read.
https://github.com/istarkov/google-map-react/issues/87#issuecomment-171331940
Then this http://facebook.github.io/react/docs/forms.html#controlled-components
And this again https://github.com/istarkov/google-map-react/issues/87#issuecomment-171331940
The same you will get even on simple input field without getting the idea of controllable and uncontrollable state.
Also you can write non working examples on jsbin https://jsbin.com/lepadusowo/edit?js,console,output
It will be easier for me to understand your issue.
;-) Ivan ;-)

@istarkov this was my second idea :) thank you.


Error when converting model

I have downloaded the Llama-2 (13B) models and I have them in .pth format.
Environment check passes, so does setting up & dependency check. When it reaches the conversion step, I see this:
Writing vocab...
Traceback (most recent call last):
File "/var/folders/m0/872knsrj62s8zllz2f18nhpr0000gn/T/E7FD53F2-B53D-4439-9AE7-898FE0607B18/convert-pth-to-ggml.py", line 11, in
convert.main(['--outtype', 'f16' if args.ftype == 1 else 'f32', '--', args.dir_model])
File "/private/var/folders/m0/872knsrj62s8zllz2f18nhpr0000gn/T/E7FD53F2-B53D-4439-9AE7-898FE0607B18/convert.py", line 1144, in main
OutputFile.write_all(outfile, params, model, vocab)
File "/private/var/folders/m0/872knsrj62s8zllz2f18nhpr0000gn/T/E7FD53F2-B53D-4439-9AE7-898FE0607B18/convert.py", line 953, in write_all
for i, ((name, lazy_tensor), ndarray) in enumerate(zip(model.items(), ndarrays)):
File "/private/var/folders/m0/872knsrj62s8zllz2f18nhpr0000gn/T/E7FD53F2-B53D-4439-9AE7-898FE0607B18/convert.py", line 875, in bounded_parallel_map
result = futures.pop(0).result()
File "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.9/lib/python3.9/concurrent/futures/_base.py", line 438, in result
return self.__get_result()
File "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.9/lib/python3.9/concurrent/futures/_base.py", line 390, in __get_result
raise self._exception
File "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.9/lib/python3.9/concurrent/futures/thread.py", line 52, in run
result = self.fn(*self.args, **self.kwargs)
File "/private/var/folders/m0/872knsrj62s8zllz2f18nhpr0000gn/T/E7FD53F2-B53D-4439-9AE7-898FE0607B18/convert.py", line 950, in do_item
return lazy_tensor.load().to_ggml().ndarray
File "/private/var/folders/m0/872knsrj62s8zllz2f18nhpr0000gn/T/E7FD53F2-B53D-4439-9AE7-898FE0607B18/convert.py", line 489, in load
ret = self._load()
File "/private/var/folders/m0/872knsrj62s8zllz2f18nhpr0000gn/T/E7FD53F2-B53D-4439-9AE7-898FE0607B18/convert.py", line 497, in load
return self.load().astype(data_type)
File "/private/var/folders/m0/872knsrj62s8zllz2f18nhpr0000gn/T/E7FD53F2-B53D-4439-9AE7-898FE0607B18/convert.py", line 489, in load
ret = self._load()
File "/private/var/folders/m0/872knsrj62s8zllz2f18nhpr0000gn/T/E7FD53F2-B53D-4439-9AE7-898FE0607B18/convert.py", line 549, in load
ndarrays = [load_unquantized(tensor) for tensor in lazy_tensors]
File "/private/var/folders/m0/872knsrj62s8zllz2f18nhpr0000gn/T/E7FD53F2-B53D-4439-9AE7-898FE0607B18/convert.py", line 549, in
ndarrays = [load_unquantized(tensor) for tensor in lazy_tensors]
File "/private/var/folders/m0/872knsrj62s8zllz2f18nhpr0000gn/T/E7FD53F2-B53D-4439-9AE7-898FE0607B18/convert.py", line 297, in load_unquantized
tensor = lazy_tensor.load()
File "/private/var/folders/m0/872knsrj62s8zllz2f18nhpr0000gn/T/E7FD53F2-B53D-4439-9AE7-898FE0607B18/convert.py", line 489, in load
ret = self._load()
File "/private/var/folders/m0/872knsrj62s8zllz2f18nhpr0000gn/T/E7FD53F2-B53D-4439-9AE7-898FE0607B18/convert.py", line 695, in load
return UnquantizedTensor(storage.load(storage_offset, elm_count).reshape(size))
File "/private/var/folders/m0/872knsrj62s8zllz2f18nhpr0000gn/T/E7FD53F2-B53D-4439-9AE7-898FE0607B18/convert.py", line 679, in load
raise Exception("tensor stored in unsupported format")
Exception: tensor stored in unsupported format
Am I doing something wrong?

Same issue with #36


jquery.slim.min.js not found

Describe the bug
Connections tab is not working. There's alert:
$ is not defined
Check browser console for more info.

To Reproduce
Run Linux or Windows binary.
Expected behavior
http://<IP_ADDRESS>:9448/node_modules/jquery/dist/jquery.slim.min.js is returning:
{"message":"Route GET:/node_modules/jquery/dist/jquery.slim.min.js not found","error":"Not Found","statusCode":404}

So file is missing. Should return jquery.slim.min.js content
Specifications:

OS: Linux, Windows 10
Version: miscord-5.0.4-linux.zip, miscord-5.0.4-win.zip
Node.js version: -

Fixed in https://github.com/miscord/miscord/commit/c99f6d4148088698aa2d992b5b6f82d836ffa890, waiting for a merge to stable.

Hi, any updates regarding the merge to stable?


Fix docs: choose_merge_request's open_reviewer default value is true

Hi Harry,
Thanks so much for writing this plugin. I've recently started a job at a company that uses Gitlab so I'm giving it a go. I noticed that the default value of open_reviewer when calling choose_merge_request was wrong in the docs, so here's a tiny PR to fix it.
Cheers!

Thanks!

Hi @harrisoncramer, I don't think the require("gitlab").choose_merge_request({ open_reviewer = false }) was a mistake -- it was supposed to demonstrate how to override the default behaviour. @eclbg probably understood "This is the default behaviour" as saying: "the following code shows you the default behaviour". I think the following would be a more appropriate change:
diff --git a/doc/gitlab.nvim.txt b/doc/gitlab.nvim.txt
index c7af27f..426a866 100644
--- a/doc/gitlab.nvim.txt
+++ b/doc/gitlab.nvim.txt
@@ -631,11 +631,12 @@ default arguments outlined under "Configuring the Plugin".
 gitlab.choose_merge_request({opts}) ~

 Choose a merge request from a list of those open in your current project to review.
-This command will automatically check out that branch locally, and optionally
-open the reviewer pane. This is the default behavior.
+This command will automatically check out that branch locally, and by default
+also open the reviewer pane (this can be overridden with the `open_reviewer`
+parameter).
 >lua
   require("gitlab").choose_merge_request()
-  require("gitlab").choose_merge_request({ open_reviewer = true })
+  require("gitlab").choose_merge_request({ open_reviewer = false })
 <
     Parameters: ~
         • {opts}: (table|nil) Keyword arguments to configure the checkout.

Thanks for merging it!
@jakubbortlik I see your point, and agree that it would be a valid solution too. I have no attachment to my proposal so feel free to go with whatever you prefer @harrisoncramer.
Thanks again


Data Wrangling using Pandas

Hey DCP participants, good to see you here
This issue will helps readers in giving all the guidance that one needs to learn about Data Wrangling using Pandas. Tutorial to Data Wrangling using Pandas and how it's applied using sample code.
"Project Title" should be the "Issue Title" mentioned here.
If you like to work on this issue, follow the given guidelines for code as well as for the README. You have to be as elaborative as possible. Make sure you also maintain the project structure provided. Just comment and get it assigned. Issues are alloted on FCFS basis.
The main intention of this repo is to educate beginners with all the concepts related to datascience so that they could feel confident to apply these things learnt in practical exposure.
Enjoy your open source journey ahead. 😎

Please assign me as I am a contributor in Deveincept


[Apploader] Sometimes installing/updating apps become impossible

Affected hardware version
Bangle 2
Your firmware version
2v13
The bug
Describe the bug
Sometimes it get impossible to install/update apps.
Expected behaviour
The apploader and watch should never get into a state where it's impossible to update/install apps
Steps to reproduce
I am not sure of what's trigger it. The watch can work fine with the app loader for days/weeks and then it doesn't work anymore.
When it doesn't work it will not work for any apps so it's easy to reproduce then.
By trying a lot of stuff I succed to make it work again, but I am not really sure what is able to solve (temporary) the issue.
I put the logs from the JS console in the attach file. If you need anything let me know.

Seems to be the same issue than #1759


empty collection properties are deserialized as null

When expanding a collection property this may be an empty collection like in this example:
TripPinService/People('keithpinckney')?$expand=Trips&$select=Trips,UserName
{
<EMAIL_ADDRESS>"http://services.odata.org/V4/(S(wbn5c1lovxzbzubnfi3a1uz1))/TripPinServiceRW/$metadata#People(Trips,UserName)/$entity",
<EMAIL_ADDRESS>"http://services.odata.org/V4/(S(wbn5c1lovxzbzubnfi3a1uz1))/TripPinServiceRW/People('keithpinckney')",
<EMAIL_ADDRESS>"W/\"08D5CD60F1CAA892\"",
<EMAIL_ADDRESS>"http://services.odata.org/V4/(S(wbn5c1lovxzbzubnfi3a1uz1))/TripPinServiceRW/People('keithpinckney')",
    "UserName": "keithpinckney",
<EMAIL_ADDRESS>"http://services.odata.org/V4/(S(wbn5c1lovxzbzubnfi3a1uz1))/TripPinServiceRW/$metadata#People('keithpinckney')/Trips",
    "Trips": []
}

The ReponseReader currently does not return empty collection properties, which results in them not beeing initialized and thus null. This may cause further unexpected NullReferenceExceptions on explicitly expanded properties.

Merged your PR and released 5.2.2.


fix: Correct typo in classifier.ipynb from "alborithm" to "algorithm"

Corrected a typo in the markdown cell of the file classifier.ipynb where "alborithm" was incorrectly spelled. The correct term is "algorithm".

Thanks!!


Swagger Models not displayed when spring security is enabled

I am not able to see the Model definitions when spring security is enabled.
definitions: {
Response: {
type: "object"
},
eventhough Response object contains multiple fields and i tried documenting all gets using @ApiModelProperty.
I am using 2.4.0 release.
The model object is not part of /v2/api-docs if I add @ImportResource("classpath:spring-security.xml").  ONLY model objects are missing, everything else is displayed correctly.
Everything works fine if I don't load the spring-security XML file.
Any ideas?

Can you create a reproducible sample using springfox-demos?

What does spring-security.xml look like?

 But still no luck!
Tried removing
and defined bean using @Component. no luck still.
So, at this point, if I enable the filter which does nothing I can't view the models in swagger. In api-docs response the "parameters": object/element (which contains the object details) itself is missing. Works just fine if I remove the filter (api-doc returns the "parameters": object with all the details).
Any ideas?

Could you try with the latest snapshot?

@dilipkrish
Tested with io.springfox:springfox-swagger2:2.4.1-SNAPSHOT. Same issue.
Based on more debugging, issue is not with the Filter itself... but with the AuthenticationService in the filter:
@Autowired
AuthenticationService authenticationService;

As long as I have it Autowired, swagger object does not show (even if I remove all references to the service).


Re-disabling with different options makes for jumpy scroll

I found that disabling scroll with default options on load, and re-disabling with handleScrollbar=false for the duration of animate to then re-re-disable completely makes the page simply skip the animation part and jump to where it was going.
Calling undo before re-disable fixes the problem, which made me discover another quality of life improvement. Chaining can't be done.
Added a return this to the end of  $.fn.disablescroll = function(method) { in my local copy for now.

You're right, there's no reason it shouldn't return this. I'll add this when I get a chance.

@realjoshharrison Any updates on this or the PR you have waiting?


Less: support @import keywords

This follows up on commit 8736eac (#322)
See http://lesscss.org/features/#import-options
Demo page: https://github.com/less/less-docs/blob/315c5b3633d2ff2b94054574cfdf57132aa95eed/styles/index.less#L13

Awesome!!! Thank you


S3 content_type is not preserved in moto.

It seems moto don't honor content type set in boto.key.Key.content_type, as the following code demonstrates:
import moto
import boto, boto.s3.key
mock = moto.mock_s3()
mock.start()

conn = boto.connect_s3()
conn.create_bucket('mybucket')
bucket = conn.get_bucket('mybucket')

key = boto.s3.key.Key(bucket, 'foo')
key.content_type = 'application/json'
key.set_contents_from_string(b'{"bar"}')

key = boto.s3.key.Key(bucket, 'foo')
print (key.get_contents_as_string())
print (key.content_type)

mock.stop()

$ python moto-content_type-test.py
b'{"bar"}'
text/plain; charset=utf-8

Content type works when real s3 is used.
I peeked code but couldn't find where "text/plain; charset=utf-8" comes from.

Can you try upgrading to the latest moto version?

The latest version fixed this problem, thanks!


Made plasma grindable

About the PR
Made plasma grindable just so we can finally make dexaline and dexaline plus to cure airloss damage
Screenshots

Changelog

:cl: Seth

tweak: Made plasma Grindable

Meaningless to have because plasma is not attainable and the grinder doesn't take into account stack of a material.

so now plasma works on grinder how do I reopen this


Add bin firmware format.

Describe the bug
When trying to update the firmware or my inovelli switch, I get an error when trying go update target one. It says it is unable to detect firmware format.
Installation information
How did you install node-zwave-js?

[ X] zwavejs2mqtt (latest) docker image
[ ] zwavejs2mqtt (dev) docker image
[ ] ioBroker.zwave2 adapter
[ ] Pkg
[ ] Manual Docker build

node-zwave-js branch:
zwavejs2mqtt branch:

[ ] Manually built (as described in the docs)
[ ] Other:

The firmware in question can be found below.
https://support.inovelli.com/portal/en/kb/articles/firmware-change-log-lzw31-sn-dimmer-switch-red-series

@robertsLando these bin files are for firmware target 1 (i.e. not the z-wave chip) - do you have a way of selecting that?

#1703 fixes this. Note that you need to select the firmware target 1 when updating the .bin files. Not sure if that is possible yet.

Yes you can do that now with https://github.com/zwave-js/zwavejs2mqtt/pull/501 on zwavejs2mqtt.


Data-toggles require double jQuery import

Problem
I have a web app with several data-toggles, i.e. dropdown menus, toggle paragraph visibility etc.. They work fine in several browsers but are "non-functional" after packaging with electron.
The error message says that jQuery is needed by bootstrap.
I confirmed the issue by using the w3c schools data toggle example.
More information and solution: electron forum
I posted this issue here on the electron forum, where you find images of the html source codes and the package.json.
I discovered the following workaround/solution: A double import of jquery seems solving the problem. It's strange but works.
Comment
I use the current versions (2017-01-23). electron v.1.4.14 and electron-prebuilt v0.35.6
As I am an electron newby, I am not sure if the current electron fixes this problem but electron-prebuilt has it not yet integrated. However, I didn't this issue in any of the bug rackers before staring creating a new issue ticket.
Source code for testing
Please find the sources attached as .zip archive
sources.zip

@tobiasrm
electron and electron-prebuilt are actually the same package, you should only be using the electron package as of 1st Jan 2017.
In order to use jQuery in Electron you need to either

Disable nodeIntegration on your BrowserWindow
Or, install jquery locally and use window.$ = window.jQuery = require('jquery');

This is not an Electron or Electron Packager issue.  If you have any questions regarding using of Electron I would recommend directing them to the community or to the Slack Channel.

Works perfectly fine. Thanks a lot for your professional help.

Thank bro because of you I could solved bootstrap js requires jquery issue in electron.


Current Version (.81) Produces Runtime Errors on Unity 5.0.2

Pretty much every example scene (circle, Delegate) produces either a runtime exception or Lua exception when run in Unity 5.0.2. Havent tested in Unity 4, but I imagine it would be the same.

fixed, need update 64bit dll and remake ui/custome wrap.


Support winetricks commands with spaces/multiple args

I've contributed to a DEB package that sets up a Windows app via wine. The setup script runs a few winetricks commands, one of which is a single command with two arguments: winetricks settings fontsmooth=rgb
installs=( \
    "corefonts" \
    "ddr=gdi" \
    "settings fontsmooth=rgb" \
    "dotnet48" \
)
for i in "${installs[@]}"; do
    winetricks_install $i
done

I would like to be able to use this same command winetricks settings fontsmooth=rgb in an app installed with sommelier, but it would need to be somehow reworked, because it currently assumes that each space-separated term passed to TRICKS is a separate winetricks command. Consider this a request for an enhancement, or maybe a request for ideas on a workaround?

Oof, that's a big oversight from our part!
As a workaround, you can use the pre-install hook:
https://github.com/snapcrafters/sommelier-core/blob/bac81b4a3907e3f661feaf76b8eedf4061d370e4/scripts/sommelier#L124-L128
This feature isn't documented yet as its main use is to workaround bugs in sommelier-core and we want people to report and fix the bugs instead of working around them ;)

I don't see how we can fix the TRICKS environment variable in a backwards-compatible way. I think we will need to create a new environment variable which used ; as separator instead of spaces. Maybe we can just call it SOMMELIER_TRICKS, since all new environment variables of sommelier-core are prefixed with SOMMELIER_.

Well, this may still be a necessary improvement in general, but I just discovered that running winetricks fontsmooth=rgb works just the same as ```winetricks settings fontsmooth=rgb". So in my case I can just simplify my TRICKS list by omitting "settings" from it. This appears to be what I've done with ddr=gdi already.

I will close this issue for the moment. Please re-open it if you find a trick that still requires spaces and the workaround above doesn't work.


Order tasks by distance

Cards on the main view should be ordered as closest first.

Easy if geolocation is implemented.


GRID | Node should register on the grid in form of http://{host}:{port}

This issue blocks me to switch on selenium 3. I was thinking that is selenium issue but it is not.
see https://github.com/SeleniumHQ/selenium/issues/3385 for details.
When I create a NODE using SGE, my NODE is connected on the HUB with friendly name instead of url of the remoteHost, and because of that only one NODE is able to connect on the HUB
there is a part of my node_5555.json file created by SGE
"loadedFromFile": "node_5555.json",
"proxy": "com.groupon.seleniumgridextras.grid.proxies.SetupTeardownProxy",
"maxSession": 3,
"port": 5555,
"register": true,
"unregisterIfStillDownAfter": 10000,
"hubPort": 4444,
"hubHost": "<IP_ADDRESS>",
"registerCycle": 5000,
"nodeStatusCheckTimeout": 10000,
"downPollingLimit": 0
so without "id" config property but for some reason it is connected with id="friendlyNameOfMyComputer"

when I use selenium-server-standalone-3.0.1.jar to setup GRID, all NODES are connected since they are connected without specified "id" property.

Please HELP!

I will try and look at this this weekend.

@mstankovic86 The code to be fixed is here I believe : https://github.com/groupon/Selenium-Grid-Extras/blob/master/SeleniumGridExtras/src/main/java/com/groupon/seleniumgridextras/grid/GridStarter.java#L227-L234

It looks like with selenium3, we do NOT use friendlyHostName. What version of Selenium Grid Extras are you on?

Oh, It looks like it is fixed on master. I will make a release tonight or tomorrow at the latest. Sorry for taking awhile.

@mstankovic86 I made a new release, v1.12.10  . Please try it and let me know. Thanks.

@smccarthy YES! it works! Thanks a lot. You can close this issue. thanks again


Data Archival during tenant offboarding

Data Archival during tenant offboarding

Closing this issue since this is a duplicate of https://github.com/sourcefuse/arc-saas/issues/6


php generated css file

i'm unable to minify a css file generated by PHP, even if my PHP file is sending CSS header on first line... I also tried htaccess to rewrite css.php to css.css but i'm still unable to minify it
is there any fix for this ?
I really need php generated CSS because i parse variables in the CSS file

you need to use the php api if you need to write css from php. i.e code css minifying yourself.


ContentDialog does not map DefaultButton

Describe the bug
When assigning to ContentDialog.DefaultButton, it should be expected that the specified button receives IsDefault="True". I assume it to be a missed propagation in ContentDialog. This breaks the ability to use the Enter key to ok/confirm a dialog.
Repro for later screenshot
Start with FluentAvaloniaSamples and change the ContentDialogPageViewModel so that it has:
DefaultButton = ContentDialogButton.Primary

Run app, open dialog, press enter, and no action will be taken.
In the debug tools, set IsDefault to True for the primary button and Enter works. The escape key already works as-is.
Screenshots

Desktop/Platform (please complete the following information):

Win10
FluentAvalonia latest
Avalonia 11preview2

Additional context
I first produced in my own app (11preview2) while building a more MVVM-friendly wrapper. It's a bit complex and I'm unfamiliar with ContentDialog, so I reproduced in the sample.

Yep this seems to be a bug. IIRC I didn't use IsDefault or IsCancel because I thought they also close the window after invoking which isn't desirable since ContentDialog is overlaid and not in its own Window - though it doesn't do this so I'm not sure where I got that from (maybe WPF or Winforms behavior?).  Anyway, I also thought I at least handled this in a key up or down handler - which after just checking I don't. Will add this to the list to fix though
More as a note to myself - I believe this is the same for TaskDialog.

Thanks for investigating. I'm not tied to IsDefault, a key handler for Enter will do fine, too.


Requirements aren't found when using FunctionTransformer

When using sklearn's Pipeline with FunctionTransformer step, some requirements that are used in that step aren't found.

if function from the custom library passed to FunctionTransformer, and MLEM can't find that library.
if decorator func for logging (azure) is used - MLEM doesn't always find that dependency.

I have an example from a customer, so now I need to reproduce and investigate. From the top of my head, 2 solutions:

Allow to pass in mlem.api.save (list of) libs to be added as requirements
Enable "deep inspection mode" with an option for mlem.api.save
Fixing both cases, keeping the same mechanics in place

Ok, this is an instruction how to make it work and find these requirements. First, let's see a script to reproduce the problem:
# run.py
from sklearn.pipeline import make_pipeline
from sklearn.preprocessing import FunctionTransformer
from func import f
from mlem.api import save

pipe = make_pipeline(
    FunctionTransformer(
        f,
    ),

)

save(pipe, "pipeline", sample_data=0)

If you run python run.py, you'll see pipeline.mlem doesn't have other dependencies except for sklearn:
# pipeline.mlem
...
requirements:
- module: sklearn
  package_name: scikit-learn
  version: 1.1.1

there's a way to find those now, using DEEP_INSPECTION setting in MLEM config.
E.g. If you run MLEM_DEEP_INSPECTION=true python run.py, they're found:
# pipeline.mlem
...
requirements:
- module: numpy
  version: 1.23.5
- module: sklearn
  package_name: scikit-learn
  version: 1.1.1
- is_package: false
  module: func
  name: func
  source64zip: eJxLSU1TSNOo0LTiUgCCotSS0qI8hQouAE2bBoU=
  type: custom
- module: scipy
  version: 1.9.3

You can also set this as a variable for the MLEM project, so MLEM will pick it up automatically, so you don't need to set it via shell vars like in the example above:
$ mlem init
$ mlem config set core.DEEP_INSPECTION true

This will generate .mlem.yaml config file with this setting set.


[#1471] feat(server/dashboard): Add Reg time to ServerNode

What changes were proposed in this pull request?
Add reg time to ServerNode, and update method to update ServerNode when server heartbeat to coordinator rather than replace serverNode object.
Why are the changes needed?
Fix: #1471
Does this PR introduce any user-facing change?
User can get registrationTime from dashboard server page.
How was this patch tested?

@xianjingfeng Thanks for your suggestion, but I'm worried of the new ServerNode state cannot be updated, any thoughts?

@advancedxy @xianjingfeng Thanks for your suggestion, I addressed your comments, PTAL

Thanks for your contribution. @maobaolong
Thanks for your reviews @xianjingfeng @advancedxy
Merged to master.

@rickyma @advancedxy @xianjingfeng thanks for your review


Packages potentially breaking version parsing

Issue description
According to the Nix source, the 'version' of a package is determined from the name as follows:

Parse a derivation name. The name part of a derivation name is everything up to but not including the first dash not followed by a letter. The version part is the rest (excluding the separating dash).

... however, there are currently various packages that violate this pattern - for example, the various git- versions. One example is velox-git-2015-11-03, which should be parsed (according to the package author's intentions) as:

Name: velox
Version: git-2015-11-03

... but is instead parsed as:

Name: velox-git
Version: 2015-11-03

This problem has two consequences:

Tools that attempt to parse the version of a package according to the rules described in the source, will get back the wrong package names/versions.
Removing the git- prefix for a package (whether to fix this issue, or because a package switches to 'real' versioned releases), might result in upgrades breaking - velox-git and velox would be considered to be different packages, and even if the git prefix were to be ignored internally, 2015-11-03 might still be considered a higher version than for example 1.2.

I'm not sure whether the solution here is in changing the parsing rules, or in changing the package names. For example - if a git prefix were not available for use, how would one package unversioned releases that come straight from Git?
(EDIT: I was just pointed at the existence of the package naming guidelines. Should this not be amended to call them rules rather than guidelines? As it stands, it's not obvious at all that there are technical consequences to not following them...)
Steps to reproduce
A full listing of affected packages due to the git prefix can be obtained as follows:
nix-env -qaP | grep '\-git\-'

... however, there may be other version prefixes that I am not aware of, that have the same issue.
Technical details

System: 16.03.1242.c5cbda2 (Emu)
Nix version: nix-env (Nix) 1.11.2
Nixpkgs version: 6.03.1242.c5cbda2

Should this not be amended to call them rules rather than guidelines?

The community on the whole seems to dislike hard rules. My view is that you need a good-enough reason to diverge from the "guidelines".
Note that not too long ago those guidelines were saying that you should put the "git" in there...

I understand that and would normally agree with it - but in this case it's not just about "what should it look like", there are actual Nix internals relying on the package name format that is used. In this case, it's highly likely that using prefixes like git will break the upgrade process down the road.
I think this discussion is more akin to "should we allow comments in a JSON file" (which would break compatibility with parsers), than to "should we use newlines in a certain way".

It acts as a package with a different name. Usually that seems fine to me.

Sure, it'll be fine until a package switches to a non-git version, and now suddenly the package is parsed as "velox" instead of "velox-git".

Yes, it will break exactly when we try to "fix this issue" ;-)

It'll also break if you don't, the difference is technical debt. 5 years from now, guides can either say "oh by the way, some packages used to have a -git suffix but don't anymore" or "oh yeah if you ever have a git- prefix on your version string, that's stuck there". Either you break a few packages now, or you have a few packages constantly breaking because of this.

Constantly breaking?

Another approach that sounded interesting was mentioned on the ML in this message.

Another solution is to abandon parsing of derivation name and include
"meta" to derivation. Then the name and version representations can be
included as meta.name and meta.version in whichever format is liked by
maintainer.

@ericsagnes That seems like the most reasonable solution to me. We'd still have to work out a migration path for the existing packages, though - the version and/or package name 'jump' would still be there.
As a side-note, I'm currently writing a version parser for a Nix-related project that also correctly understands 'non-compliant' versions, and there are quite a few weird edge cases. I think that for these kind of purposes, specifying a meta.version would also help a lot.

Some packages have already migrated to style where you can access foo.version (i.e. not in meta).

From the manual:

If a package is not a release but a commit from a repository, then the version part of the name must be the date of that (fetched) commit. The date must be in "YYYY-MM-DD" format. Also append "unstable" to the name - e.g., "pkgname-unstable-2014-09-23".

so "pkgname-unstable-${version} with version = "YYYY-MM-DD". git, svn, etc. should be updated to this format.
With the functions for building Python packages I intend to make the version a parameter and let the functions put the name and version together, the reason being that if we automate the updating of packages further the version  would be needed for selecting a different version of the package.

Since this is an older discussion, I’m gonna close.


pfe-datetime: schema and getter and setter conflicts

The schema has a property for datetime, type, and timestamp. Those three properties also have getters and setters in the component which causes a naming conflict. If the schema is included in the component, it causes a javascript error in the _mapSchemaToProperties method in pfelement.js.

Closing this. We're no longer using schemas.


Helm range when multiple values.yaml specified

As we know helm will append maps from multiple values files as shown below:
values.yaml 1:
app:
  env:
    name1: value1

values.yaml 2:
app:
  env:
    name2: value2

So, when we specify both files during chart installation, we'll have these values provided to the chart
app:
  env:
    name1: value1
    name2: value2

But if we remove value from values.yaml 2 like this:
values.yaml 2:
app:
  env:
    # name2: value2

We will get our values erased:
app:
  env: null

For me it looks like such arithmetic operation:
1+1 = 2
1+0 = 0
This is weird behavior, isn't it?
Output of helm version:
version.BuildInfo{Version:"v3.8.0", GitCommit:"d14138609b01886f544b2025f5000351c9eb092e", GitTreeState:"clean", GoVersion:"go1.17.5"}
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.5", GitCommit:"5c99e2ac2ff9a3c549d9ca665e7bc05a3e18f07e", GitTreeState:"clean", BuildDate:"2021-12-16T08:38:33Z", GoVersion:"go1.16.12", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.13", GitCommit:"ddb8dba0a4420ec79de95cebfa4bd7d41aed848a", GitTreeState:"clean", BuildDate:"2021-11-01T16:41:29Z",
GoVersion:"go1.15.14", Compiler:"gc", Platform:"linux/amd64"}
Cloud Provider/Platform (AKS, GKE, Minikube etc.):
AKS

This is standard yaml parsing.
app:
  env:

converts to this json:
{
  "app": {
    "env": null
  }
}

To get your desired merge, you'd need to specify that env is a map:
app:
  env: {}
    # name2: value2


SSO: AttributeError: 'CloudAdapter' object has no attribute 'exchange_token'

Version
Installed using instructions 'Using the SDK locally` in README
Describe the bug
SSO for singe tenant with Cloud Adapter does not work in Teams web/desktop client. Works in Web Chat.
To Reproduce
Steps to reproduce the behavior:

Install the repo
Enable SSO using https://learn.microsoft.com/en-us/microsoftteams/platform/sbs-bots-with-sso?source=recommendations&tabs=ngrok&tutorial-step=4
Upload Manifest and try sending a message to the bot

Expected behavior
SSO was working as of last week but is not working anymore. There was a bot infra outage a few days ago that caused an error when uploading manifest.json on the web/desktop app. Could it be related to that?
Additional context
Fails here:
 elif not getattr(context.adapter, "exchange_token"):
                # Token Exchange not supported in the adapter.
                await context.send_activity(
                    self._get_token_exchange_invoke_response(
                        int(HTTPStatus.BAD_GATEWAY),
                        "The bot's BotAdapter does not support token exchange operations."
                        " Ensure the bot's Adapter supports the ExtendedUserTokenProvider interface.",
                    )
                )

in botbuilder-python/libraries/botbuilder-dialogs/botbuilder/dialogs/prompts/oauth_prompt.py

Ya.  This is a bug.  Looks to be missing the equivalent implementation as JS and DotNet SDK's, or even the 'exchange_token' on CloudAdapter as the Python BotFrameworkAdapter has.

Correction notes:
OAuthPrompt, line 480 (mentioned above) should likely be removed.  This appears to be code for the original implementation.  The 'else' statement matches DotNet which uses a UserTokenAccess object to make the correct call for new vs old adapter.
However, UserTokenAccess should be reviewed, especially around TurnState having had a UserTokenClient set.


Revert "Add GradientsDebugger to tfdbg"

This reverts commit 31f1375c01782f53cf12ce2aa4efa584483c14ea.

Testing Github UI. CLosing soon.


"Unrecognized K8s API" and having zero vulnerabilities in old K8s version

I'm just trying to figure out if kube-hunter is working correctly here.
We have a k8s-cluster using v1.18.9. I ran kube-hunter --k8s-auto-discover-nodes --kubeconfig ~/.kube/config locally on my machine which has network access to the cluster.
The output is the following:
2021-10-11 17:36:28,236 INFO kube_hunter.modules.report.collector Started hunting
2021-10-11 17:36:28,236 INFO kube_hunter.modules.report.collector Discovering Open Kubernetes Services
2021-10-11 17:36:28,593 INFO kube_hunter.modules.discovery.kubernetes_client Listed 3 nodes in the cluster
2021-10-11 17:36:36,175 INFO kube_hunter.modules.report.collector Found open service "Unrecognized K8s API" at xx.xxx.xx.141:6443
2021-10-11 17:36:36,175 INFO kube_hunter.modules.report.collector Found open service "Unrecognized K8s API" at xx.xxx.xx.142:6443
2021-10-11 17:36:36,176 INFO kube_hunter.modules.report.collector Found open service "Unrecognized K8s API" at xx.xxx.xx.143:6443
2021-10-11 17:36:36,176 INFO kube_hunter.modules.report.collector Found open service "Unrecognized K8s API" at our-own-internal-dns-1:6443
2021-10-11 17:36:36,177 INFO kube_hunter.modules.report.collector Found open service "Unrecognized K8s API" at our-own-internal-dns-2:6443
2021-10-11 17:36:36,178 INFO kube_hunter.modules.report.collector Found open service "Unrecognized K8s API" at our-own-internal-dns-3:6443

Nodes
+-------------+----------------------+
| TYPE        | LOCATION             |
+-------------+----------------------+
| Node/Master | our-own-             |
|             | internal-dns-3       |
+-------------+----------------------+
| Node/Master | our-own-             |
|             | internal-dns-2       |
+-------------+----------------------+
| Node/Master | our-own-             |
|             | internal-dns-1       |
+-------------+----------------------+
| Node/Master | xx.xxx.xx.143        |
+-------------+----------------------+
| Node/Master | xx.xxx.xx.142        |
+-------------+----------------------+
| Node/Master | xx.xxx.xx.141        |
+-------------+----------------------+

Detected Services
+----------------------+----------------------+----------------------+
| SERVICE              | LOCATION             | DESCRIPTION          |
+----------------------+----------------------+----------------------+
| Unrecognized K8s API | our-own-internal     | A Kubernetes API     |
|                      | -dns-3:6443          | service              |
+----------------------+----------------------+----------------------+
| Unrecognized K8s API | our-own-internal     | A Kubernetes API     |
|                      | -dns-2:6443          | service              |
+----------------------+----------------------+----------------------+
| Unrecognized K8s API | our-own-internal     | A Kubernetes API     |
|                      | -dns-1:6443          | service              |
+----------------------+----------------------+----------------------+
| Unrecognized K8s API | xx.xxx.xx.143:6443   | A Kubernetes API     |
|                      |                      | service              |
+----------------------+----------------------+----------------------+
| Unrecognized K8s API | xx.xxx.xx.142:6443   | A Kubernetes API     |
|                      |                      | service              |
+----------------------+----------------------+----------------------+
| Unrecognized K8s API | xx.xxx.xx.141:6443   | A Kubernetes API     |
|                      |                      | service              |
+----------------------+----------------------+----------------------+

No vulnerabilities were found

Questions

Why is the K8s API unrecognized? Is that something to be concerned about
I'm a little bit sceptical about not having any vulnerabilities in our cluster. Is this normal? I found CVE-2021-25741 which is stated to affect any version "up to and including" 1.19.14. Or is kube-hunter only looking for open vulnerabilities from the outside of the cluster? So frome the view of an outside attacker and not an inside user who wants to do harm?

Hi @moritzluedtke
Answering your questions:

They way kube-hunter works is by first categorizing k8s apis and then reassuring them as what they truly are. it seems like it could do it. (if you could attach a run with --log debug flag I could help you figure out why this happend)
Starting from #482 . We made cve hunting optional. this means if you want to see CVE results you need to pass the flag --enable-cve-hunting


[CELEBORN-1660] Cache available workers and only count the available workers device free capacity

What changes were proposed in this pull request?

cache the available workers
Only count the available workers device free capacity.
place the metrics_AvailableWorkerCount_Value in overall and metrics_WorkerCount_Value in Master part

Why are the changes needed?
Cache  the available workers to reduce the computation that need to loop the workers frequently.
To have an accurate device capacity overview that does not include the excluded workers, decommissioning workers, etc.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
UT.

This may increase the computational cost of these two metrics. What do you think?

I think we can cache available workers(we can manually update the cache when occur exclude/shutdown..), the current process of computing the list of available workers can be resource-intensive, especially in large clusters.

I think we can cache available workers(we can manually update the cache when occur exclude/shutdown..), the current process of computing the list of available workers can be resource-intensive, especially in large clusters.

Before this, how about using map instead set for workers?
https://github.com/apache/celeborn/pull/2839
cc @RexXiong

This PR is ready. cc @FMX @RexXiong @zaynt4606

will rebase the code

gentle ping @FMX and @RexXiong

Hi @FMX and @RexXiong  by any chance to help review this PR, thanks very much

also cc @pan3793 to take a look

Merge to main(v0.6.0)

thanks all for the review!


JSON-input internal validation - part 1

This is Part 1 (of 2) on internal validation of TBD JSON input. Internal refers to logical consistency of file content (not flagged by schema validation per se), either concerning:

TBD structure & built-in default values
internal logic of the file itself (e.g. a surface's custom PSI-set requires a matching library PSI-set on file)
correspondence with OSM objects (e.g. a surface's id requires a matching OSM surface name)


fix(@ngtools/webpack): resolve file name before invalidating cached files

Fix WebpackCompilerHost cache invalidation behavior on Windows systems. Previously, invalidate made no call to _resolve, causing paths with backslashes not to match the file cache. This caused a watch build to continuously emit the same result.
Fixes #4422
Fixes #4345
Fixes #4338

Thanks! I problem makes a lot of pain to me

Good stuff!

LGTM. You're right, this was an oversight and we were missing e2e tests for this. I'll add a test. Thanks!

@hansl Btw, this caching has made watched builds so much faster. Thanks!

I'm kinda hoping it's just me, and just this project, but while this fix almost completely resolved #4422, I'm noticing sometimes when I make minor changes (I just changed a variable from 2500 to 2000), it still uses the old has and forces me to stop ng serve and restart. I'm not sure if I should have noted this here or in 4422, but thought this was better? It seems to work the vast majority of the time, but on some small changes (not even all), it still reuses a hash.

@hansl Any plans to release a next beta? This issue is a showstopper for windows users((

@quanterion If you install latest webpack (1.2.8) problem is fixed. If you delete node_modules and redo npm install you'll get that version with current cli release as it pulls in latest (I think)

@rohitsodhia The behavior I've noticed is that sometimes after running for a long time the build freezes up and doesn't emit new files consistently, especially for small changes on a file I've been editing a lot recently.
Is this consistent with your experience?

@msmorgan I didn't notice any freezing... it always emitted, just not updating the hash. Following the upgrade path resolved the problems for me.


don't trust X_DOWNLOADED_FULL flag, consider messages with missing data incomplete (WIP)

This is an experimental fix for #1243 with the following changes, the overall idea is to allow recovery from a state where part files which should be on disk are missing.

the flag which decides whether a message is complete, and whether the "Download Complete Message" button is shown, is moved into MessageViewInfo, the relevant logic into MessageViewInfoExtractor
if a file-backed part is missing its related file, the FileBackedBody won't be created (leaving the part with a null body)
a message is considered incomplete if either it doesn't have an X_DOWNLOADED_FULL flag, or it is missing the body of any message part
automatic download of (partial) message content on view is triggered only if neither X_DOWNLOADED_PARTIAL nor X_DOWNLOADED_FULL flags is set, to avoid loops if a message can't be downloaded properly
loadMessageRemoteSynchronous will always download a message. This is currently only called exactly if the user clicks the "Download Complete Message" button, so this seems reasonable?

Feedback welcome

:+1:
Please rebase and merge.


Add german translation

add the translation file de_de.json for germany

Would love to approve this, but do you mind adding the translations for the accessories?
On a somewhat related note, how would you like me to credit you in the changelog?

just added the translations for the accessories

On a somewhat related note, how would you like me to credit you in the changelog?

don't know, probably the github name?


Enhancement: Chat while in Motion

I don't know if it's possible to make this, but here's the idea:
The mod should watch for when you open the chat box by pressing T.
If you are riding in a boat AND you were actively holding down W when you press T, then the mod should continue "holding" W for you until the chat box is closed.
This way you could remain in motion while still being able to use the in-game chat.
(Especially useful when boating on a long straightaway.)
This should work while boating on any surface. No ice check.
This should, however, be configurable. A config option that defaults to Off, I think.
(I can supply config text and hovertext, as usual, if we get to that stage.)
(And this should go without saying, but I'll specify this anyway: the mod shouldn't rely on W or T literally. It should still work if the user has remapped the Forward and Open Chat keys.)

Definitely possible
I will have a look at how invmove does movement when a screen is open for reference.
https://github.com/PieKing1215/InvMove/blob/e1c6e4334a7cd85976d3f679dfed5161a4aaa9c6/common/src/main/java/me/pieking1215/invmove/InvMove.java#L252

Okay, cool.
Remember, I'm not asking for steering or turn priming or snap key support, just sustained forward movement.
Keep this one simple.

Added and released in 1.3.0


Bug: (Adding audience prop to KindeProvider generates accesss_token without "aud" with custom domain)

Prerequisites

[X] I have searched the repository’s issues and Kinde community to ensure my issue isn’t a duplicate
[X] I have checked the latest version of the library to replicate my issue
[X] I have read the contributing guidelines
[X] I agree to the terms within the code of conduct

Describe the issue
Initializing KindeProvider with audience (all setup in Kinde react app > APIs is done and API is authorized)
<KindeProvider
      clientId={import.meta.env.VITE_KINDE_CLIENT_ID}
      domain={import.meta.env.VITE_KINDE_DOMAIN}
      logoutUri={import.meta.env.VITE_KINDE_LOGOUT_URL}
      redirectUri={import.meta.env.VITE_KINDE_REDIRECT_URL}
      audience={import.meta.env.AUDIENCE_URL}
    >
      <App />
</KindeProvider>

We are using custom domain and I can see that {custom_domain}/oauth2/token is returning JSON response with access_token.
Decoding this access_token "aud" is an empty array []
Latest react SDK version 4.0.2 is throwing sometimes the following error and SignIn:
Error: (aud) claim mismatch. Expected: "{OUR_AUDIENCE}", Received: ""
    at isTokenValid (@kinde-oss_kinde-auth-react.js?v=e686e7b6:216:13)
    at setStore (@kinde-oss_kinde-auth-react.js?v=e686e7b6:284:5)
    at handleRedirectToApp (@kinde-oss_kinde-auth-react.js?v=e686e7b6:417:9)
    at async init (@kinde-oss_kinde-auth-react.js?v=e686e7b6:527:7)
    at async createKindeClient (@kinde-oss_kinde-auth-react.js?v=e686e7b6:542:3)

Library URL
https://github.com/kinde-oss/kinde-auth-react
Library version
4.0.1, 4.0.2
Operating system(s)
macOS
Operating system version(s)
Venrtura 13.3.1 (a)
Further environment details
"react": "^18.3.1"
Chrome version 126.0.6478.185 (Official Build) (arm64)
using pnpm
node v20.11.1
Reproducible test case URL
No response
Additional information
Issue is reproducible also with https://github.com/kinde-starter-kits/react-starter-kit with CLIENT_ID, DOMAIN and AUDIENCE_URL from our account.
Appears locally and in staging env

Hi @jenny-beteende I've taken a look and was unable to reproduce your issue using a custom domain.
Typically the reason you would see this error is if the audience hasn't been authorized inside of Kinde admin - which I know you said you had, but would you mind double checking?

I double checked it and found the problem, I set it up with a "/" in the end and tried to use it without it. Thanks!


Overlap checker tool

Added overlap checker tool from DAGMC to check and identify overlapped regions in .h5m faceted files.

Checks for overlaps by looping through every triangle vertex in a mesh.
Added as a new tool
Cannot sample additional points along triangle edges (like DAGMC's version) as XDG::MeshManager does not have support to call MOAB functions that return entity adjacencies

Tested the tool on some h5m files locally and it seems like its working okay. It identifies when there are overlaps and which volumes are overlapped in agreement with DAGMC's version. Also added a new test file that runs the 5 test cases that DAGMC does for its overlap-checker tool.
One thing to note, the overlap location printed when running the tool doesn't necessarily match DAGMC's. I'm not sure what the cause of that is or if that is a major concern? Maybe due to differences in the order in which vertices are checked between the libraries?
Edit - CI fails because the .h5m files needed for those tests are missing from the repository. The files to be used with overlap-check's test's can be found here - test_files.zip. The CMakeLists.txt expects these files to be placed in ${XDG_ROOT}/tests/test_files

Fixed the inconsistent indentations you highlighted and a couple more I noticed, lmk if anything else needs editing.
I also removed the parsing of an argument to hold the number of points along a triangle edge to sample since I don't think we will be implementing that feature anymore and will instead go straight to ray_fire along edges check.

@Waqar-ukaea it looks like CI is still unhappy. Did the submodule get updated after that PR to the test files repo?


Kotlin Multiplatform PoC migration

Created kotlin multiplatform module using store4 module to migrate and test functionality slowly.  Replaced references in sample code referencing store4 with kmp code. So far, with disabled cache, functionality / testing works as expected.
Notes:

Commented out caching layer in RealStore. Multiplatform caching to be reimplemented. Tests referencing a cached store request were also commented out as the code path leads to hanging as is.

In Multicaster the ChannelManager was instantiated using a lazy delegate and initialization mode. This caused kotlin native to throw an unsupported exception despite documentation stating that it is.  This was removed and changed to simple assignment; I'm unsure of the performance impact of this change.

3a) Truth testing library has been swapped out for multiplatform Turbine for flow testing.  .emitsExactly functionality split to .emitsExactly (checks emitted values in order and does not expect a completion event) and .emitsExactlyAndCompletes (which does).  Testing that utilizes the standard flow { } builder emit a completion event.
3b) Kotlin-test-common required changes in assertion formats.

coroutine-test library classes necessary to implement TestCoroutineScope migrated to kmp under testutils/coroutines.  Most were lift and shift; however, TestCoroutineExceptionHandler required a small rework as it relied on synchronized(owner) to manipulate the exceptions list which is not supported in kmp.  Instead, I wrapped the exceptions in an atomic reference.

Some builds fail with Metaspace exception. Subsequent builds work and testing / running application is unaffected. I have as of now not looked into the cause.

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

Now that the new memory model is stabilizing I'd be curious to see what it would take to get the multicaster to be kmp compact too https://blog.jetbrains.com/kotlin/2021/08/try-the-new-kotlin-native-memory-manager-development-preview/

With Store 5 stable out I think we can close this now. Thanks all 🙏🏽


invalid websocket response: 522 Origin Connection Time-out

**use cloudflare before server. port ~8000,http mode
but got error when check connecting to bing.com:
so where is broken  in the connection path? (server? CF -> server? or me -> CF?) **
(use $ symbol hide private info)

client.go:394, ERROR ,"Dial failed: invalid websocket response from bing.com:443: HTTP/1.1 522 Origin Connection Time-out
Date: Sun, $ Nov 2018 $$:$$:$$ GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: keep-alive
Set-Cookie: __cfduid=$$$; expires=$-Nov-19 $$:$$:$$ GMT; path=/; domain=$$$; HttpOnly
Set-Cookie: cf_use_ob=0; path=/; expires=$-Nov-18 $$:$$:$$ GMT
Expires: Thu, 01 Jan 1970 00:00:01 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Server: cloudflare
CF-RAY: $$$

cmdline: -up="cf://$$:$$" -k="$$$$" -l=":8100" -web-port="8101" -lv=dbg -g -U=http
version: v2.0.0 rc1 win x86_64
Thanks!

522 Origin Connection Time-out means cloudflare can't connect to your server

Confirmed. Thanks!

@binus Hi, How do you solve this error?


Web Hooks

Regarding:
"After you have published your content to a DOC bureau’s public GitHub repository, you must email<EMAIL_ADDRESS>with the link to your repository so that the DOC GitHub account can “watch” your repository and be notified of updates. DOC will do this by selecting the “Watch” button at the top of your repository."
From @benbalter:
"This can be somewhat automated by organization-wide web hooks (https://github.com/blog/1933-introducing-organization-webhooks) which could subscribe to repository-creation events and kick off a follow request via the API."

Sounds better, but does DOC really want to watch the repos? Anything can be investigated after the fact, I just don't see how DOC will be able to actually monitor things in real time.


CommandBlock could take the "script" meta category to reduce some rows

i dont know what this means either


Support EF-specific interfaces for notification change tracking

Suggesting that EF define it's own copies of notification interfaces, say EntityFrameworkCore.INotifyCollectionChanged, EntityFrameworkCore.IPropertyChanged. and EntityFrameworkCore.INotifyPropertyChanging. If an entity implements these then notification change tracking is enabled and EF uses them for notification tracking. This would be a non-breaking change.
Following are two challenges with notification change tracking that would be nicely solved by this approach.

Say we would like to implement a concurrent data structure, such as a tree, that is stored in the database. We want to lock changes to the structure using a normal synchronous signature and a lock such as SemaphoreSlim.Wait. We must notify changes outside of the lock, because running user event code from inside the lock is a recipe for deadlock. But when we notify the changes outside of the lock, EF's relationship fix-up kicks in and EF then makes additional changes to the data structure, such as adding children due to change of a parent pointer. Those EF-initiated collection changes then run outside the lock, even though we need these data structure changes to occur within the lock. With the proposed approach we could notify EF from within the lock and notify users from outside the lock.

Say we have a tree structure that is implemented using entities with notification change tracking, and we are using these entities in the ItemsSource of a UWP TreeView. This means that instances of the entity are stored in TreeViewNode.Content. Now, we drag and drop a node in the TreeView and want to update the entity tree structure accordingly. To do so, we must disable collection change notification. If change notifications were enabled, then since the entities are bound as the ItemsSource, the TreeView would detect the changes and attempt to update itself to match -- causing havoc since at this point we are trying to change the entity tree structure to match the dragged TreeViewNodes structure, not vice versa. However, when we disable collection change notifications in the entity tree structure, it interferes with EF's notification change tracking. Specifically it means that EF cannot detect changes to the collections and fix-up the corresponding principle entity navigations and foreign keys. We then have to be careful to only manipulate the entity tree structure using principal entity navigations, rather than the navigation collections. With the proposed approach we could disable collection changed for the TreeView while leaving collection changed in place for EF.

@divega to follow up.

@sjb-sjb thanks for sharing the details of these scenarios. We discussed your feature request in triage today. Given that we haven't received any similar requests in the past, and that adding EF Core-specific change tracking interfaces would add significant complexity, we currently don't think we should do this, at least until we get more evidence that this is widely required and that there aren't reasonable workarounds.
Here are a few alternative approaches I believe customers can take to address a scenario similar to yours:

Avoid notification-based change tracking: You can still implement the interfaces for the purpose of binding your entity types to your UI, and implement the same logic you described to lock the graph or disable change notifications in its collections. If you don't explicitly enable notification change tracking in EF Core (e.g. you don't call HasChangeTrackingStrategy) then you can rely on automatic snapshot change tracking to discover any changes in the graph of objects any time it is needed, or even explicitly invoke change tracking APIs such as DetectChanges, or setting current values explicitly on entity entries.

Using the model–view–viewmodel pattern (or similar) to separate the two layers: You can use notification entities in the EF Core model, but use separate types to binding to the UI. The view model types can either wrap the data classes or there can be an adapter between them.

@divega thanks for your thoughtful comments.
I agree there's always a way to work around things. All of the workarounds require a similar amount of work to solve the same underlying problem. I think that the examples I gave do identify concrete challenges. Obviously it's up to you whether these should be addressed in EF or not. I am not arguing against the triage decision: based on the great quality of EF it is clear that you're doing a great job on design!
The conflicting demands between multiple uses of collection and property change notifications could be viewed as a system-wide challenge rather than only an EF question.
Noting I am already using MVVM. I happen to be driving my View Model updates off of the Model notifications; but even if I were not, the same problem (2 in my post) would occur. I would have to suspend my VM collection change notifications for the same reason. The difference would be that this workaround would be more decoupled from EF.

I guess that a work-around to (1) might be to predict all of the changes that EF would make (such as adding children, in the example) and execute them in advance within the lock.

I am catching up with old issues assigned to me, and I think I am ready to either close this discussion (since we don't have plans to implement the original feature request for now, but we can always revisit this decision in presence of new data) or move it to the backlog with the following idea:
We could abstract a bit more how we bind to the events from the INotifyPropertyChang* interfaces to allow advanced users to provide their own interfaces and their own binding logic. I haven't fully investigated this, but here are a few steps that I believe would be required:

The user would need to somehow replace a state management service, IInternalEntityEntrySubscriber (currently internal) to implement subscription an un-subscription for the events in their custom interfaces.

Something on the InternalEntityEntry needs to carry the actual event handlers. Currently we have InternalEntityEntry.HandleINotifyPropertyChang* which watch the shape of the event handlers from the INPC interfaces. If the events on the custom interface happen to take the same parameter types (object sender and object sender, PropertyChangingEventArgs eventArgs) then you shouldn't need any changes. These handlers in turn invoke the mehtods on IInternalEntityEntryNotifier, but at this point the code is agnostic of the interfaces.

In places like https://github.com/aspnet/EntityFrameworkCore/blob/fc69488be0a725530bd213d41d8b086e8c013018/src/EFCore/Metadata/Internal/EntityType.cs#L2426-L2445, we validate that the actual INotifyPropertyChang* interfaces are implemented by entities. We could allow that to be overridden too.

All in all, for someone that implements both the standard INotifyPropertyChange* interfaces and custom ones, they can probably get away with just doing (1), but this requires replacing an internal service.

Hi Diego
I don't think it needs to be so complex. At the places noted in (3) where EF currently tests for INotifyPropertyChang*, it could simply test to see whether a specific alternative interface defined by EF is implemented, say INotifyEfPropertyChang*. If the EF version is implemented then EF would subscribe to that, otherwise it would use the normal interface.
Steve
Sent from my iPhone

On Jul 5, 2019, at 8:25 PM, Diego Vega<EMAIL_ADDRESS>wrote:
I am catching up with old issues assigned to me, and I think I am ready to either close this discussion (since we don't have plans to implement the original feature request for now, but we can always revisit this decision in presence of new data) or move it to the backlog with the following idea:
We could abstract a bit more how we bind to the events from the INotifyPropertyChang* interfaces to allow advanced users to provide their own interfaces and their own binding logic. I haven't fully investigated this, but here are a few steps that I believe would be required:
The user would need to somehow replace a state management service, IInternalEntityEntrySubscriber (currently internal) to implement subscription an un-subscription for the events in their custom interfaces.
Something on the InternalEntityEntry needs to carry the actual event handlers. Currently we have InternalEntityEntry.HandleINotifyPropertyChang* which watch the shape of the event handlers from the INPC interfaces. If the events on the custom interface happen to take the same parameter types (object sender and object sender, PropertyChangingEventArgs eventArgs) then you shouldn't need any changes. These handlers in turn invoke the mehtods on IInternalEntityEntryNotifier, but at this point the code is agnostic of the interfaces.
In places like https://github.com/aspnet/EntityFrameworkCore/blob/fc69488be0a725530bd213d41d8b086e8c013018/src/EFCore/Metadata/Internal/EntityType.cs#L2426-L2445, we validate that the actual INotifyPropertyChang* interfaces are implemented by entities. We could allow that to be overridden too.
All in all, for someone that implements both the standard INotifyPropertyChange* interfaces and custom ones, they can probably get away with just doing (1), but this requires replacing an internal service.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Note from triage: closing this based on Diego's analysis since this is something we are very unlikely to implement.


Typescript - missing some types in vue-cool-select/types/types.d.ts

Low priority - it throws errors messages in the compiler but everything still works fine.
Version 3.0.2
Specific messages are:
Parameters implicitly have 'any' type:
Line 9, 10, 11, 41 through 48
Functions lack return-type annotation, implicitly have 'any' return type:
Line 41 through 48

The reason is that you have "noImplicitAny": true enabled, any is used in my types, so the compiler complains.
You can use "skipLibCheck": true, as described in this answer.
Hope this helps.

Got it - thanks!
Great work too


[Bug]: flax_gpt2 produces wrong results when using semi2k with a custom MatMulAA operator

Issue Type
Currentness/Accuracy
Modules Involved
MPC protocol
Have you reproduced the bug with SPU HEAD?
Yes
Have you searched existing issues?
Yes
SPU Version
74c6d54e5bff9e5d35ab5a73dda98cd9ccf0bfc8
OS Platform and Distribution
Ubuntu 20.04.6 LTS, x86_64
Python Version
3.10.8
Compiler Version
gcc 10.5.0
Current Behavior?
Hi, I am studying semi2k protocol, and I changed the MatMulAA operator of semi2k protocol to a very simple and unsecure implementation. In my implementation, party0 sends x0 and y0 to party1, and party1 computes the cleartext of x and y, then use the cleartext of x and y to compute cleartext of z. The output of party0 is zero. The output of party1 is cleartext of z.
However, when I run flax_gpt2 using semi2k protocol with my implementation of MatMulAA, SPU output is wrong.
My modifications (based on commit id 74c6d54e5bff9e5d35ab5a73dda98cd9ccf0bfc8):
diff --git a/examples/python/ml/flax_gpt2/2pc.json b/examples/python/ml/flax_gpt2/2pc.json
new file mode 100644
index 0000000..edbac4f
--- /dev/null
+++ b/examples/python/ml/flax_gpt2/2pc.json
@@ -0,0 +1,43 @@
+{
+    "id": "outsourcing.2pc",
+    "nodes": {
+        "node:1": "<IP_ADDRESS>:61921",
+        "node:2": "<IP_ADDRESS>:61922",
+        "node:3": "<IP_ADDRESS>:61923",
+        "node:4": "<IP_ADDRESS>:61924"
+    },
+    "devices": {
+        "SPU": {
+            "kind": "SPU",
+            "config": {
+                "node_ids": [
+                    "node:1",
+                    "node:2"
+                ],
+                "spu_internal_addrs": [
+                    "<IP_ADDRESS>:61931",
+                    "<IP_ADDRESS>:61932"
+                ],
+                "runtime_config": {
+                    "protocol": "SEMI2K",
+                    "field": "FM64",
+                    "enable_pphlo_profile": true,
+                    "enable_hal_profile": true,
+                    "fxp_exp_mode": 1
+                }
+            }
+        },
+        "P1": {
+            "kind": "PYU",
+            "config": {
+                "node_id": "node:3"
+            }
+        },
+        "P2": {
+            "kind": "PYU",
+            "config": {
+                "node_id": "node:4"
+            }
+        }
+    }
+}
diff --git a/libspu/mpc/semi2k/arithmetic.cc b/libspu/mpc/semi2k/arithmetic.cc
index 017c464..19b0970 100644
--- a/libspu/mpc/semi2k/arithmetic.cc
+++ b/libspu/mpc/semi2k/arithmetic.cc
@@ -348,6 +348,7 @@ NdArrayRef MatMulAP::proc(KernelEvalContext*, const NdArrayRef& x,
   return ring_mmul(x, y).as(x.eltype());
 }

+#if 0
 NdArrayRef MatMulAA::proc(KernelEvalContext* ctx, const NdArrayRef& x,
                           const NdArrayRef& y) const {
   auto* comm = ctx->getState<Communicator>();
@@ -362,6 +363,43 @@ NdArrayRef MatMulAA::proc(KernelEvalContext* ctx, const NdArrayRef& x,
   }
   return z.as(x.eltype());
 }
+#endif
+
+NdArrayRef MatMulAA::proc(KernelEvalContext* ctx, const NdArrayRef& x,
+                          const NdArrayRef& y) const {
+  auto* comm = ctx->getState<Communicator>();
+  const auto field = x.eltype().as<Ring2k>()->field();
+  const auto xshape = x.shape();
+  const auto yshape = y.shape();
+  const auto zshape = Shape({xshape[0], yshape[1]});
+
+  if (comm->getRank() == 0) {
+      // send y0 to party1
+      comm->sendAsync(1, y, "matmulaa_y0");
+      // send x0 to party1
+      comm->sendAsync(1, x, "matmulaa_x0");
+
+      // z0 = 0
+      return ring_zeros(field, zshape).as(x.eltype());
+  }
+  else if (comm->getRank() == 1) {
+      // compute y_pub
+      const NdArrayRef y0 = comm->recv(0, y.eltype(), "matmul_aa_y0").reshape(yshape);
+      const NdArrayRef y_pub = ring_add(y0, y);
+
+      // compute x_pub
+      const NdArrayRef x0 = comm->recv(0, x.eltype(), "matmul_aa_x0").reshape(xshape);
+      const NdArrayRef x_pub = ring_add(x0, x);
+
+
+      // z1 = z_cleartext
+      NdArrayRef z1 = ring_mmul(x_pub, y_pub);
+      return z1.as(x.eltype());
+  }
+  else {
+      SPU_ENFORCE(false, "party exceeds 2");
+  }
+}

Standalone code to reproduce the issue
In one terminal, run command:

bazel run -c opt //examples/python/utils:nodectl -- --config `pwd`/examples/python/ml/flax_gpt2/2pc.json up

In another terminal, run command:
bazel run -c opt //examples/python/ml/flax_gpt2 -- --config `pwd`/examples/python/ml/flax_gpt2/2pc.json

### Relevant log output

```Shell
------
Run on CPU
I enjoy walking with my cute dog, but I'm not sure if I'll ever

------
Run on SPU
I enjoy walking with my cute dogbank,ottesville, testifying dep purchaser,,ION

Will take a look.

Semi2k for two-party will run the local truncation, which will fail when one of the share is zero.

Semi2k for two-party will run the local truncation, which will fail when one of the share is zero.

It seems to be another bug that causes this problem. Will be fixed soon.


Allow up to 5 retries if fetch returns a recoverable error; Made VA t…

…olerant to individual counties erroring

@lazd you want to review?


Add http server/client json and blob nodes - v2

Changes since v1:

using sol_util_memdup()
Removed some SOL_WRN()s in favor or error packets

merged


Fix default config file path

fixes #4.

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

Revisiting project with /search/all refresh. Thanks!

Revisiting project with /search/all refresh. Thanks!


--locale=zh-Hans does not prompt for language pack install

Testing #52960

VSCode Version: 1.25 build for testing
OS Version: High Sierra

Starting with --locale=zh-Hans does not prompt for the language pack install.

Same for zh-Hant.

Only zh-cn and zh-tw are supported. Its an issue with the test case


include printf

Is there a reason that printf is not exposed in the crate? It can be used anyway at least on some platforms.

Nah there's no particular reason why it isn't bound just yet, but you may be interested in this RFC which should help ease the expansion of this library!

Is libc open to have printf defined now?

Certainly!


Rename "getting-started guides" to "cluster creation guides"

The so-called "getting-started guides" are misnamed. They're about cluster creation and porting Kubernetes (getting-started from scratch). We should change the names to reflect that.
Of course, we'll need to magically forward all the links.
Getting started should really just require executing one command, to create a single-node cluster.
cc @pwittrock @janetkuo @dlorenc

When you say "Rename" do you mean changing the URL of everything under getting-started-guides?

yeah, I agree with this statement.  I think we need to figure out what we're going to do with the getting started guides long term with the new site structure.


Updated composer install instructions

Using the new require command you can make the install instructions a whole lot easier.

:+1:

:+1:

Looks good, merging

Thanks for the contribution!


Prototype MQTT Mosquito Connection not working

Hi, I am attempted to connect to mosquitto broker but since MQTTFX is no longer free, I've been trying to use MQTT Explorer, MQTTBOX, MQTTLens, EMQX Client ( MQTTX ) with no luck connecting to mosquitto, any help is appreciated.
( I will test selfsigned now, then move on to Lety's Encrypt )
self signed could not complete as error states: IP does not match certificate's altenames: IP: <IP_ADDRESS> is not in the cert's list:
I edited the generate-certs.sh with the following:
CN=$(<IP_ADDRESS> -I
Certbot folder is missing
00-install-certbot.sh
01-generate-certs.sh

🤔

@dualizeo Thanks for reporting this. Let me get back to you on this once I do some local tests and see if I can reproduce it

@dualizeo you are right, the script files were deleted, I have reintroduced the scripts in certbot directory

Also I am not sure why you would do CN=$(<IP_ADDRESS> -I). The actual way would be to just set CN=<IP_ADDRESS>

Also I am not sure why you would do CN=$(<IP_ADDRESS> -I). The actual way would be to just set CN=<IP_ADDRESS>

Thank you for adding the scripts, I will test out Certbot soon, however I did managed to get self signed certificates working using MQTTX client :) and based on that CN code I was looking at the following:
https://github.com/InfluxCommunity/tiguitto/tree/master/selfsigned/generate-certs.sh
# Use IP Address for CN
CN=$(hostname -I | awk '{print $1}')

so Instead I will try CN=My IP
as you mentioned, or I will replace it with a local dns record created in my router.
Thank you !

@dualizeo I am closing this issue. If you have similar problems please reopen this issue


fix: Avoid access of resource not created when sqs_queue_arn is defined

What
Hey all, 👋🏽
There is a case when passing the sqs_queue_arn variable to the module the output tries to access the resource not created.
Why
fix: To use the module with a pre-existent sqs queue.
Notes
The function one is supported since Terraform 0.15 https://developer.hashicorp.com/terraform/language/functions/one

Hi @thauanz do you have an example handy by any chance of how this fails when a queue arn is passed in?

Hey @schattingh, yes, check it out! (I redacted some of the real names for public reasons 😄 )
module "register_lambda" {
  source = "git::https://github.com/harrison-ai/harrison-terraform-module-aws-lambda?ref=v0.1.1"
  # source = "/harrison-ai/harrison-terraform-module-aws-lambda/"

  name                           = "${local.project}-register-${local.env_name}"
  description                    = "Register Lambda"
  image_uri                      = "${data.aws_ecr_repository.register.repository_url}:${local.register.image_tag}"
  architectures                  = ["arm64"]
  memory_size                    = 1024
  timeout                        = 300
  batch_size                     = 1
  lambda_policy                  = data.aws_iam_policy_document.register.json
  sqs_visibility_timeout_seconds = 900

  envvars = {
    AWS_ENV              = local.env_name
    RECORD_CONCURRENCY   = "1"
    RUST_BACKTRACE       = "1"
  }

  # setting this parameter it fails to the output
  sqs_queue_arn = data.aws_sqs_queue.this.arn

  # with the sqs_queue_name it works
  # sqs_queue_name = "${local.project}-register-${local.env_name}"
}


Better github workflow and fix invalid environment variables error

I made minor changes in the GitHub workflow, this should be slightly faster. Resolved environment error in GitHub workflow.

Thanks a lot


Darwinia - NFT Bridge Protocol

Grant Application
This application is (select one):

[x] Speculative (use this by default)
[ ] an RFP response

This application is (select one):

[ ] Public (fully)
[x] Public with private finances

Abstract
This proposal is about the design and protocol of cross-chain NFT, it is also a response to Polkadot Bridges RFP, and an improvement to XClaim framework on NFT cases. The scope includes.

The description and specification about the NFT bridge protocol, mainly focusing on the improvement.

Introducing new price finding methods for NFTs using Harberget Tax model.
Improve XClaim frame works on cases when both blockchains supporting smart contract and chainRelay. The Vault can be implemented in a more trustless way using chainRelay contract.

Minimal POCs for demonstrating the ability of the protocol, and full implementation of the specification.

NFT Standards on Polkadot, and the design on normalization process for bridged tokens to resolve indentifiability and resolution issues.

Read the Full Proposal →
Checklist

[x] The grants document has been read and understood.
[x] The Google Form will be completed accurately. Note that the Google Form requires the pull request URL.
[x] Abstract (above) is succinct and complete.
[x] The application is being included into the correct directory: either 'targeted' or 'speculative'.
[x] The application includes a project description.
[x] The application includes all names of team members.
[x] The application includes a description of the team's experience.
[x] The application includes all necessary links (e.g. GitHub and LinkedIn)
[x] The "Development Roadmap" section in the application has a timeline of development ("milestones").
[x] The "Development Roadmap" section in the application has an estimate of funds required.
[x] The "Development Roadmap" section gives an indication of the team's long term plans.
[x] The "Development Roadmap" section includes documentation as a deliverable for at least one milestone.

Just closing some old grant PRs to help bring 2019 activities to a conclusion.
New grant applications are welcome in 2020. Please reach out if you have any questions.


Secrecy or Vault should close on screen locking

Case 1 :
At the Secrecy main activity (Vault selection screen) screen locking (click on device power button hardware key and again unlocking the device) does not do anything.
Case 2 :
Inside the vault, Screen locking and unlocking will returns the app to the Main Activity.
Case 3 :
Inside the vault while viewing an image, Screen locking and unlocking does not do anything.
After unlocking the phone the encrypted image is still open. This is a problem and it should be Fix.
PS :
I recommend that Secrecy should be closed on screen locking on the above 3 cases.

#119 fixed number 3.
We'll think about a way to exit the app instead of returning to the vault list.

"Case 2 :
Inside the vault, Screen locking and unlocking will returns the app to the Main Activity."
Considering case 3, viewing encrypted content after screen unlock is not ok - because a vault is basically a collection of encrypted files I would think the app is doing the right thing (returning to the Main activity).
My opinion is that 1&2 are not bugs. Closing the app on screen lock would be a useful feature (but I would apply it only when stealth mode is activated)

@StelianMorariu good point. Only directly closing the app when in stealth mode sounds very reasonable.

Sorry for accidentally closing this.
stealth mode hide still needs another PR to be implemented.


[Fix issues/120] add check if encode -> decode value is the same as the original value

https://github.com/long2ice/fastapi-cache/issues/120
This is a correction to the issue reported here.
In JsonCoder, if the encoded and decoded value does not match the original value, a ValueError is returned.
Also, together with this PR, I was able to fix the PickleCoder error.
Using redis, if decode_responses is false, the value of decode will be bytes.
JsonCoder works fine whether it comes in bytes or str, but PickleCoder gives an error if it is bytes.
Therefore, we fixed it.
    redis = aioredis.from_url(
        "redis://localhost",
        encoding="utf8",
        decode_responses=False, # False by default.
    )
    FastAPICache.init(RedisBackend(redis))

https://github.com/long2ice/fastapi-cache/issues/120

@mjpieters Thanks


Release 1.5

Update following JB site redesign.
Add the Friday Stream.

I've published new flatpaks with latest git master.

I'm not sure what happened to this?
I've now added more for release:

Add Jupiter Extras.
Add Linux Headlines.

Cool. I hope to make a new Nuvola release this month. Flatpak builds has started failing last week so I need to figure out what's wrong. That's the very last blocker.

Release 1.5 tagged and will be announced later today.


After updating to 1.2.2 - Error while setting up polestar_api platform for sensor

Hi,
after updating from 1.2.0 to 1.2.2 it stopped working with the following error:
Logger: homeassistant.components.sensor
Source: helpers/entity_platform.py:361
Integration: Sensor (documentation, issues)
First occurred: 9:23:00 PM (1 occurrences)
Last logged: 9:23:00 PM
Error while setting up polestar_api platform for sensor
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 361, in async_setup_platform
await asyncio.shield(task)
File "/config/custom_components/polestar_api/sensor.py", line 392, in async_setup_entry
sensors = [
^
File "/config/custom_components/polestar_api/sensor.py", line 393, in
PolestarSensor(device, description) for description in POLESTAR_SENSOR_TYPES
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/polestar_api/sensor.py", line 416, in init
self.translation_key = f"polestar{description.key}"
^^^^^^^^^^^^^^^^^^^^
AttributeError: property 'translation_key' of 'PolestarSensor' object has no setter

Fixed in 1.2.3


Kotlinx Coroutines 1.5.0

Kotlinx Coroutines version bump

@moljac since you were upgrading KotlinX Coroutines and the version 1.5.0 was released on Friday, I opened this PR to try to help with the KotlinX Couroutines upgrade

LGTM

@moljac this is the current error, but I don't know how to fix them, or what's the right thing to do here.
Do you have any ideia?
obj/Release/monoandroid9.0/generated/src/Xamarin.KotlinX.Coroutines.DelayKt.cs(72,49): error CS0111: Type 'DelayKt' already defines a member called 'Delay' with the same parameter types [XamarinComponents/Android/KotlinXCoroutines/source/KotlinX.Coroutines.Core.Jvm/KotlinX.Coroutines.Core.Jvm.csproj]
obj/Release/monoandroid9.0/generated/src/Xamarin.KotlinX.Coroutines.TimeoutKt.cs(61,49): error CS0111: Type 'TimeoutKt' already defines a member called 'WithTimeout' with the same parameter types [XamarinComponents/Android/KotlinXCoroutines/source/KotlinX.Coroutines.Core.Jvm/KotlinX.Coroutines.Core.Jvm.csproj]
obj/Release/monoandroid9.0/generated/src/Xamarin.KotlinX.Coroutines.TimeoutKt.cs(99,49): error CS0111: Type 'TimeoutKt' already defines a member called 'WithTimeoutOrNull' with the same parameter types [XamarinComponents/Android/KotlinXCoroutines/source/KotlinX.Coroutines.Core.Jvm/KotlinX.Coroutines.Core.Jvm.csproj]
obj/Release/monoandroid9.0/generated/src/Xamarin.KotlinX.Coroutines.Flow.FlowKt.cs(928,70): error CS0111: Type 'FlowKt' already defines a member called 'Debounce' with the same parameter types [XamarinComponents/Android/KotlinXCoroutines/source/KotlinX.Coroutines.Core.Jvm/KotlinX.Coroutines.Core.Jvm.csproj]
obj/Release/monoandroid9.0/generated/src/Xamarin.KotlinX.Coroutines.Flow.FlowKt.cs(2151,70): error CS0111: Type 'FlowKt' already defines a member called 'Sample' with the same parameter types [XamarinComponents/Android/KotlinXCoroutines/source/KotlinX.Coroutines.Core.Jvm/KotlinX.Coroutines.Core.Jvm.csproj]

@4brunu Bom dia and thanks for reporting.
I'll need to take a look... it can be quite a lot of things involved. Generic parameters as Java.Lang.Object and then you have 2 method/function signatures that are the same in managed world, but not in java world...
Right now I need to publish tons of new AndroidX packages...

Nice touch with bom dia :)
Dobro jutro! (I think? 🤔 )
Go ahead, and thanks for helping 👍

@moljac CI is now passing.
The solution was to remove some experimental API.


Added to_dict() method to troposphere.Template

This removes the JSONrepr methods and replaces with to_dict() which
handle creating dicts for each of the individual objects. The to_json()
method then just calls to_dict() on self and marshals the resulting
dictionary. Adding to_dict() allows for output into other formats such
as YAML without needing to output JSON and then reload it back just to
output in another format.
This can be considered a breaking change if others are calling JSONrepr. If needed I can re-add the JSONrepr functionality back to make this backwards compatible.

I had not seen the YAML branch but I will take a look. We also had the desire to compare an existing JSON template with a potentially updated template and use a dict compare so adding a native to_dict() makes it a little easier as well.

Looks good to me!

Updated with to_dict() in the AWSHelperFn class and overriding only when necessary.

This is a nice change. Thank you for submitting it.

I don't believe we need to support the JSONrepr() interface as I can't imagine people are calling it outside of to_json().

FWIW, we were using JSONrepr() outside of to_json(). I'm currently in the process of rewriting a bunch of tests to use the new interface.
Maybe we shouldn't have been using JSONrepr, maybe we shouldn't have been pulling Troposphere from GitHub instead of PyPI… but since I don't think JSONrepr was marked as an internal function it might have been better to deprecate it more slowly instead of removing it suddenly.

@bpholt my apologies for causing you an issue with this change. I never considered JSONrepr() to be a troposphere interface and wasn't aware anyone was using it other than through to_json(). I appreciate you letting me know and glad you think it is better. Could you let us know your use case for using it so I make sure we don't make the same mistake again?

@markpeek Thanks. We have a helper function in our tests that used JSONrepr to convert Troposphere objects to a format that can be compared/expected with the robber library. It basically did exactly what encode_to_dict does (and has now been replaced entirely with a call to encode_to_dict).

@bpholt TIL 1) reminded again to send a message to the mailing list to solicit feedback on potential breaking changes and 2) there is a robber library. Sorry again but glad is was a straightforward change for you.


React ComponentType not checked correctly in the presence of a library definition importing it.

Flow version
0.73.0
Unexpected behavior
The following program type checks with no errors, but should have a missing prop error
// @flow

import React, { type ComponentType } from 'react';

const X: ComponentType<{ foo: string }> = () => null;

export const test = <X />;

when I have a library definition containing the line
import type { Component, ComponentType } from 'react';

... in my flow-typed directory.

Replacing ComponentType with React$ComponentType in the failing example causes the error to be reported correctly.

Removing the import and using React$ComponentType in the libdef causes the failing example to be reported correctly (in my case, along with a few hundred new - seemingly valid - issues in my code base)

Expected
Either of

Flow reports the missing prop error in the presence of this import
Flow reports the library defintion as invalid instead of silenty failing.

Can you supply a minimal example? I can't reproduce your issue on Try Flow. Are you saying the line in the library definition is silencing this error?

@fishythefish I'm not sure it is possible to reproduce this on try flow. I can only repro this with a .flowconfig and with library file present in the flow-typed folder. To repro you can create three files
./index.js
// @flow

import React, { type ComponentType } from 'react';
const X: ComponentType<{ foo: string }> = () => null;
const test = <X />;

./flow-typed/test.js
import type { Component, ComponentType } from 'react';

.flowconfig
[libs]
./flow-typed/.*

The error will be silenced as described on flow 0.73.0.

This was fixed in v0.144 (with 5148a475c0fe77e7a0d5c561ff0ee73070fd5fb1), so this issue should now be closed.
The repros above now give the following error:
Cannot use an import statement at the toplevel of a library file. Import statements may only
appear inside a `declare module`. [toplevel-library-import]

     1│ import type { Component, ComponentType } from 'react';

Moreover, even when you do have such an import, Flow correctly gives an error at the line that's wrong (and this part may have been true before v0.144, too; not sure):
Cannot create X element because property foo is missing in props [1] but exists in object
type [2]. [prop-missing]

 [2]  6│ const X: ComponentType<{| foo: string |}> = () => null;
      7│
      8│ // $ExpectError
 [1]  9│ const test = <X />;

Oh, and in fact the fix was released a bit earlier, in v0.143.0; the commit was cherry-picked as d35f6dc6495d63d6a33fe18608c3ec962c4463b9.
Just before that fix was the one in fc121d6a18b84f88c697d667c2bec6cb7650c407, which explains how the issue led to a lack of type-checking:
Raise all lib errors

Summary:
Before, we would collect the errors encountered in each lib file, right
after the pass over the code of the library, but before merging all library
contexts into a single "master" context, and optimizing it. This resulted
in us missing a number of errors. See for example the previous couple
of diffs. Crucially, we would miss a lot of `[cannot-resolve-name]`
errors, which meant that these types would silently turn into `any` for
every file in the repo.

This diff changes this by collecting the errors from the master context
after context optimization. It then filters suppressions and stores the
errors together with the rest of the errors in the server environment.

[…]


Crash on garbage collection

0   libnode.dylib                 	0x0000000113066322 v8::internal::Heap::IterateAndMarkPointersToFromSpace(v8::internal::HeapObject*, unsigned char*, unsigned char*, bool, void (*)(v8::internal::HeapObject**, v8::internal::HeapObject*)) + 386
1   libnode.dylib                 	0x0000000113065bfe v8::internal::Heap::DoScavenge(v8::internal::ObjectVisitor*, unsigned char*) + 574
2   libnode.dylib                 	0x00000001130647e9 v8::internal::Heap::Scavenge() + 937
3   libnode.dylib                 	0x0000000113063353 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) + 915
4   libnode.dylib                 	0x0000000113062bce v8::internal::Heap::CollectGarbage(v8::internal::GarbageCollector, char const*, char const*, v8::GCCallbackFlags) + 606
5   libnode.dylib                 	0x000000011303098f v8::internal::Factory::NewUninitializedFixedArray(int) + 95

It seems that there is a patch available:
https://chromium.googlesource.com/v8/v8/+/8d6a228819d2a45a20e1dd5982ad53bf23145667


refactor: count Carpentry skill towards Skill Average

Description
Closes #1602
Closes #1649
Example

Oops, branch was merged with #1654 ;-;
Doesn't really matter but still :/

Updated Description

This gives NaN on senither skill on a profile with API off: http://localhost:32464/stats/dukioooo/Lemon
My solution would be to just hide weight if API is off, carpentry is a skill now so it must count towards weight... and without that the weight values are just wrong imo

Sure, I guess 🤷♂

@dukio Why waiting label?

@dukio Why waiting label?

https://github.com/SkyCryptWebsite/SkyCrypt/pull/1655#discussion_r968825549

@SkyCryptWebsite/developers 2 approvals 😄

About weight systems, they don't seem to be working on any profiles.

Solved, accidentally reverted that as well ;-;


After upgrade to 4.1.1 Sql Lab does not execute saved queries

Bug description

Go to saved queries
Edit query (any of them)
Click run

Bum, error
Screenshots/recordings

Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist

[X] I have searched Superset docs and Slack and didn't find a solution to my problem.
[X] I have searched the GitHub issue tracker and didn't find a similar bug report.
[X] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

The issue is not related to network issues. Here is some extract o f the error from the log:

superset_app          | INFO:superset.commands.sql_lab.execute:Triggering query_id: 48
superset_app          | INFO:superset.sql_lab:Query 48: Executing 1 statement(s)
superset_app          | INFO:superset.sql_lab:Query 48: Set query to 'running'
superset_app          | INFO:superset.sql_lab:Query 48: Running statement 1 out of 1
superset_app          | INFO:superset.sql_lab:Query 48: Storing results in results backend, key: xxx
superset_app          | WARNING:root:Exception raised while handling cache file '/app/superset_home/sqllab/2029240f6d1128be89ddc32729463129'
superset_app          | Traceback (most recent call last):
superset_app          |   File "/usr/local/lib/python3.10/site-packages/cachelib/file.py", line 207, in get
superset_app          |     with self._safe_stream_open(filename, "rb") as f:
superset_app          |   File "/usr/local/lib/python3.10/contextlib.py", line 135, in __enter__
superset_app          |     return next(self.gen)
superset_app          |   File "/usr/local/lib/python3.10/site-packages/cachelib/file.py", line 328, in _safe_stream_open
superset_app          |     fs = self._run_safely(open, path, mode)
superset_app          |   File "/usr/local/lib/python3.10/site-packages/cachelib/file.py", line 322, in _run_safely
superset_app          |     output = fn(*args, **kwargs)
superset_app          | PermissionError: [Errno 13] Permission denied: '/app/superset_home/sqllab/2029240f6d1128be89ddc32729463129'
superset_app          | WARNING:root:Exception raised while handling cache file '/app/superset_home/sqllab/2029240f6d1128be89ddc32729463129'
superset_app          | Traceback (most recent call last):
superset_app          |   File "/usr/local/lib/python3.10/site-packages/cachelib/file.py", line 207, in get
superset_app          |     with self._safe_stream_open(filename, "rb") as f:
superset_app          |   File "/usr/local/lib/python3.10/contextlib.py", line 135, in __enter__
superset_app          |     return next(self.gen)
superset_app          |   File "/usr/local/lib/python3.10/site-packages/cachelib/file.py", line 328, in _safe_stream_open
superset_app          |     fs = self._run_safely(open, path, mode)
superset_app          |   File "/usr/local/lib/python3.10/site-packages/cachelib/file.py", line 322, in _run_safely
superset_app          |     output = fn(*args, **kwargs)
superset_app          | PermissionError: [Errno 13] Permission denied: '/app/superset_home/sqllab/2029240f6d1128be89ddc32729463129'
superset_app          | WARNING:root:Exception raised while handling cache file '/app/superset_home/sqllab/162ff78da3a563f9f99605a7d15a433e'
superset_app          | Traceback (most recent call last):
superset_app          |   File "/usr/local/lib/python3.10/site-packages/cachelib/file.py", line 246, in set
superset_app          |     fd, tmp = tempfile.mkstemp(
superset_app          |   File "/usr/local/lib/python3.10/tempfile.py", line 357, in mkstemp
superset_app          |     return _mkstemp_inner(dir, prefix, suffix, flags, output_type)
superset_app          |   File "/usr/local/lib/python3.10/tempfile.py", line 256, in _mkstemp_inner
superset_app          |     fd = _os.open(file, flags, 0o600)
superset_app          | PermissionError: [Errno 13] Permission denied: '/app/superset_home/sqllab/tmpr_cjv83e.__wz_cache'
superset_app          | <IP_ADDRESS> - - [27/Nov/2024:17:46:11 +0000] "POST /api/v1/sqllab/execute/ HTTP/1.1" 200 11227 "https://xxx/sqllab/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36"
superset_app          | WARNING:superset.views.error_handling:SupersetErrorException
superset_app          | Traceback (most recent call last):
superset_app          |   File "/usr/local/lib/python3.10/site-packages/flask/app.py", line 1484, in full_dispatch_request
superset_app          |     rv = self.dispatch_request()
superset_app          |   File "/usr/local/lib/python3.10/site-packages/flask/app.py", line 1469, in dispatch_request
superset_app          |     return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)
superset_app          |   File "/usr/local/lib/python3.10/site-packages/flask_appbuilder/security/decorators.py", line 95, in wraps
superset_app          |     return f(self, *args, **kwargs)
superset_app          |   File "/app/superset/views/base_api.py", line 119, in wraps
superset_app          |     duration, response = time_function(f, self, *args, **kwargs)
superset_app          |   File "/app/superset/utils/core.py", line 1364, in time_function
superset_app          |     response = func(*args, **kwargs)
superset_app          |   File "/usr/local/lib/python3.10/site-packages/flask_appbuilder/api/__init__.py", line 183, in wraps
superset_app          |     return f(self, *args, **kwargs)
superset_app          |   File "/app/superset/utils/log.py", line 303, in wrapper
superset_app          |     value = f(*args, **kwargs)
superset_app          |   File "/app/superset/sqllab/api.py", line 342, in get_results
superset_app          |     result = SqlExecutionResultsCommand(key=key, rows=rows).run()
superset_app          |   File "/app/superset/commands/sql_lab/results.py", line 105, in run
superset_app          |     self.validate()
superset_app          |   File "/app/superset/commands/sql_lab/results.py", line 73, in validate
superset_app          |     raise SupersetErrorException(
superset_app          | superset.exceptions.SupersetErrorException: Data could not be retrieved from the results backend. You need to re-run the original query.

It turned out to be a permission problem of sqllab folder onwed by root instead of superset.