DxThemes.current crashes on Chrome emulating iPhone X when upgrading to 17.2.5.

To help us process the issue more efficiently, please provide the following information:

Specify the version of the devextreme-angular and devextreme packages you are using.
devexteme version: 17.2.5
devextreme-angular version: 17.2.5

Specify the type of the issue (check one with "x"):
[x] bug Report
[ ] feature request
[ ] support inquiry

Windows 7
Chome 63.0.3239.132
Upgrading from 17.1.7 to 17.2.5.
Steps:

Open angular 5.1.1 app in chrome
Open developer tools
Turn on toggle device toolbar
Pick iPhone X(any mobile) and refresh

ERROR Error: Uncaught (in promise): SyntaxError: Failed to execute 'remove' on 'DOMTokenList': The token provided must not be empty.
Error: Failed to execute 'remove' on 'DOMTokenList': The token provided must not be empty.
at Object.setClass (dom_adapter.js:56)
at initRender.webpackJsonp.../../../../devextreme/core/renderer_base.js.initRender.toggleClass (renderer_base.js:165)
at initRender.webpackJsonp.../../../../devextreme/core/renderer_base.js.initRender.removeClass (renderer_base.js:135)
at detachCssClasses (themes.js:242)
at Object.current (themes.js:151)
at AdminLayoutComponent.webpackJsonp.../../../../../src/app/layouts/admin/admin-layout.component.ts.AdminLayoutComponent.setTheme (admin-layout.component.ts:259)
at new AdminLayoutComponent (admin-layout.component.ts:83)
at createClass (core.js:12480)
at createDirectiveInstance (core.js:12315)
at createViewNodes (core.js:13776)
at Object.setClass (dom_adapter.js:56)
at initRender.webpackJsonp.../../../../devextreme/core/renderer_base.js.initRender.toggleClass (renderer_base.js:165)
at initRender.webpackJsonp.../../../../devextreme/core/renderer_base.js.initRender.removeClass (renderer_base.js:135)
at detachCssClasses (themes.js:242)
at Object.current (themes.js:151)
at AdminLayoutComponent.webpackJsonp.../../../../../src/app/layouts/admin/admin-layout.component.ts.AdminLayoutComponent.setTheme (admin-layout.component.ts:259)
at new AdminLayoutComponent (admin-layout.component.ts:83)
at createClass (core.js:12480)
at createDirectiveInstance (core.js:12315)
at createViewNodes (core.js:13776)
at resolvePromise (zone.js:809)
at resolvePromise (zone.js:775)
at zone.js:858
at ZoneDelegate.webpackJsonp.../../../../zone.js/dist/zone.js.ZoneDelegate.invokeTask (zone.js:421)
at Object.onInvokeTask (core.js:4744)
at ZoneDelegate.webpackJsonp.../../../../zone.js/dist/zone.js.ZoneDelegate.invokeTask (zone.js:420)
at Zone.webpackJsonp.../../../../zone.js/dist/zone.js.Zone.runTask (zone.js:188)
at drainMicroTaskQueue (zone.js:595)
at
defaultErrorLogger @ core.js:1427
webpackJsonp.../../../core/esm5/core.js.ErrorHandler.handleError @ core.js:1488
next @ core.js:5498
schedulerFn @ core.js:4339
webpackJsonp.../../../../rxjs/_esm5/Subscriber.js.SafeSubscriber.__tryOrUnsub @ Subscriber.js:240
webpackJsonp.../../../../rxjs/_esm5/Subscriber.js.SafeSubscriber.next @ Subscriber.js:187
webpackJsonp.../../../../rxjs/_esm5/Subscriber.js.Subscriber._next @ Subscriber.js:128
webpackJsonp.../../../../rxjs/_esm5/Subscriber.js.Subscriber.next @ Subscriber.js:92
webpackJsonp.../../../../rxjs/_esm5/Subject.js.Subject.next @ Subject.js:56
webpackJsonp.../../../core/esm5/core.js.EventEmitter.emit @ core.js:4319
(anonymous) @ core.js:4775
webpackJsonp.../../../../zone.js/dist/zone.js.ZoneDelegate.invoke @ zone.js:388
webpackJsonp.../../../../zone.js/dist/zone.js.Zone.run @ zone.js:138
webpackJsonp.../../../core/esm5/core.js.NgZone.runOutsideAngular @ core.js:4701
onHandleError @ core.js:4775
webpackJsonp.../../../../zone.js/dist/zone.js.ZoneDelegate.handleError @ zone.js:392
webpackJsonp.../../../../zone.js/dist/zone.js.Zone.runGuarded @ zone.js:154
_loop_1 @ zone.js:684
api.microtaskDrainDone @ zone.js:693
drainMicroTaskQueue @ zone.js:602
Promise resolved (async)
scheduleMicroTask @ zone.js:578
webpackJsonp.../../../../zone.js/dist/zone.js.ZoneDelegate.scheduleTask @ zone.js:410
onScheduleTask @ zone.js:297
webpackJsonp.../../../../zone.js/dist/zone.js.ZoneDelegate.scheduleTask @ zone.js:401
webpackJsonp.../../../../zone.js/dist/zone.js.Zone.scheduleTask @ zone.js:232
webpackJsonp.../../../../zone.js/dist/zone.js.Zone.scheduleMicroTask @ zone.js:252
scheduleResolveOrReject @ zone.js:856
resolvePromise @ zone.js:803
(anonymous) @ zone.js:728
webpackJsonpCallback @ bootstrap a9a0dd14b38995ed47a8:21
(anonymous) @ dashboard.module.chunk.js:1

Uncaught (in promise) DOMException: Failed to execute 'remove' on 'DOMTokenList': The token provided must not be empty.
at Object.setClass (https://localhost/vendor.bundle.js:94712:39)
at initRender.webpackJsonp.../../../../devextreme/core/renderer_base.js.initRender.toggleClass (https://localhost/vendor.bundle.js:95758:20)
at initRender.webpackJsonp.../../../../devextreme/core/renderer_base.js.initRender.removeClass (https://localhost/vendor.bundle.js:95728:17)
at detachCssClasses (https://localhost/vendor.bundle.js:197548:16)
at Object.current (https://localhost/vendor.bundle.js:197457:5)
at AdminLayoutComponent.webpackJsonp.../../../../../src/app/layouts/admin/admin-layout.component.ts.AdminLayoutComponent.setTheme (https://localhost/main.bundle.js:4146:26)
at new AdminLayoutComponent (https://localhost/main.bundle.js:3958:14)
at createClass (https://localhost/vendor.bundle.js:435635:20)
at createDirectiveInstance (https://localhost/vendor.bundle.js:435470:37)
at createViewNodes (https://localhost/vendor.bundle.js:436931:53)

debugging:
DxThemes.current(theme); // step into
detachCssClasses(viewPort()); // throws exception
whole app crashes// does not crash with device toolbar off
Project setup:
index.html:
<link rel="stylesheet" type="text/css" href="assets/devextreme/dx.common.css" />
<link rel="dx-theme" data-theme="default" type="text/css" href="assets/devextreme/default.css" data-active="true" />
<link rel="dx-theme" data-theme="dark" type="text/css" href="assets/devextreme/dark.css" data-active="false" />
<link rel="dx-theme" data-theme="orange" type="text/css" href="assets/devextreme/orange.css" data-active="false" />
<link rel="dx-theme" data-theme="material" type="text/css" href="assets/devextreme/material.css" data-active="false" />
themes are switched with DxThemes.current(theme); where theme is one of   allThemes: Array = ['default', 'dark', 'orange'];
all this worked in  17.1.7

Fixed in #2806


Administrators Cannot Create Advisors

GitHub #10 was the original reference.  Super users can no longer create advisors.  That's good.  Administrators can no longer create advisors.  That's bad.
Reference item 77

@dspCarlson I need help reproducing this one. I just created an advisor using my account on staging so it works for me.

@VassilIordanov I too can create an advisor in staging.  But Craig and I cannot create advisors in production.  See email with graphic.  The advisor button is disabled.  The mouse-over is a red circle with a slanted line.

fixed (albeight accidentally) by 6bed7d5a46424268bf59eb793906ec2733543862


Anyway to do forbidden properties that have a default?

I would like to have an object like so:
export const register = z.object({
  email: z.string().email(),
  password: z.string().superRefine(password),
  first_name: z.string(),
  last_name: z.string(),
  role: z.literal('user'),
  is_email_verified: z.literal(false)
});

But in this object I don't want the role or user to be parsed in but I would like default values if this makes sense. In Joi I would do:
role: Joi.forbidden().default('user')
This way I can add values to the object that weren't there initially.
Is there any way to do this in zod?

I think that
z.never().default(() => "foo")

will maybe help?

Is this what you are looking for?
const register = z.object( {
    email: z.string().email(),
    password: z.string().superRefine( () => true ), // do some refinement here
    first_name: z.string(),
    last_name: z.string(),
    is_email_verified: z.literal( false )
} ).transform( data => ( { ...data, role: 'user' } ) )

console.log(
    register.parse( {
        email<EMAIL_ADDRESS>        password: 'password',
        first_name: 'first_name',
        last_name: 'last_name',
        is_email_verified: false
    } )
)


[Event Request] Codeunit 80 Sales-Post (and codeunit 90 Purch.-Post) - new event OnAfterSetCompressPrepaymentFilters

Hi Team,
BC version - 17;
codeunit - 80 and 90;
procedure - CreatePrepaymentLines;
We need the possibility to manage filters that applied when compress prepayment. Having a new event in the procedure CreatePrepaymentLines would be a suitable solution for both codeunits 80 and 90, below example for codeunit 80:

[IntegrationEvent(false, false)]
local procedure OnAfterSetCompressPrepaymentFilters(var TempPrepmtSalesLine: Record "Sales Line")
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Support segment tables in Theia

[ ] In Trace Compass, segment tables should be implemented using data providers
[ ] Segment tables should be pageable to avoid transmitting too much data


Do clean release build to exclude Jacoco from jar.

Related to discussion in #831.

Codecov Report

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

@@            Coverage Diff            @@
##             master     #836   +/-   ##
=========================================
  Coverage     97.41%   97.41%
  Complexity      791      791
=========================================
  Files            91       91
  Lines          2707     2707
  Branches        305      305
=========================================
  Hits           2637     2637
  Misses           38       38
  Partials         32       32

Continue to review full report at Codecov.

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

Uhhh

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':storio-common:signArchives'.

Cannot perform signing task ':storio-common:signArchives' because it has no configured signatory

Will look later :(

Ok, so I'm not sure why it doesn't work on CI, I've configured local machine very similary and used same release scripting, and it works for me locally.
My guess is that version of gpg is incompatible with one I use on mac


Allow the multiple uploads from the app itself.

The current version of the app only allows multiple uploads when it is used inside of the Gallery. It do not let users to select multiple images to upload.

Agreed. To clarify, MultipleShareActivity only gets called if the user starts from their gallery, selects more than one image, and clicks "share". We should allow multiple image selection from within our app as well. I imagine we would probably need to refactor ShareActivity first though so we can reuse the shared logic.

We may need to think about 'what sort' of multiple uploads we would like to allow. The browser-based Upload Wizard allows any multiple uploads, even of unrelated pictures - all pictures must have their titles, desc, and categories selected separately later.
I propose that we do not allow this, but instead only allow multiple uploads of ONE subject. So instead of having the user type in titles, desc, categories for all of them, they need only do it once (this also simplifies the UI logic IMO). However we need to make this explicit to the user somehow (perhaps in the tutorial or via a one-time popup during the first time they submit multiple images).

I am a heavy user of the app but I have almost never used multiple upload. Is it really needed? It sounds like it might lead some people to upload a lot of pictures with only approximate titles/categories.

Ah, interesting. I would personally use them, especially if I was taking photos of an event or of a particular location from a few angles.
Would anyone else like to weigh in?

This will be done in the later half of the IEG renewal.
Use case:
Currently, the only way to submit multiple uploads (many files in one upload step) is to go to the Android gallery app, select more than one image, and click "share". We would like to implement multiple image selection from within our app as well, to prevent the need for re-submitting many times if the user has several different images of the same item. This might have the beneficial side effect of reducing overwrites, and is also necessary prior to implementation of overwrite prevention at #703 , as otherwise users will be prompted for every single successive image of the same title that they upload.
Scope:

Modify the intent triggered by the "upload from gallery" button to allow multiple uploads -
https://stackoverflow.com/questions/44082151/multiple-images-select-from-gallery
Decide how to handle multiple uploads, and if MultipleShareActivity can be generalized to include multiple uploads from within the app
Decide how we want to handle titles and descs. My suggestion would be to make it explicit to the user somehow that multiple uploads should only be done for multiple pictures of the same thing (similar to how it currently works under "Share"), NOT for pictures of different things (which is allowed by the browser Upload Wizard because they allow you to title each pic individually). If we do this, then we can mostly reuse our current ShareActivity UI, except with the addition of the information above
Handle file titles to ensure we don't overwrite filenames

Based on discussion on the gamification issue #85 , I think it would indeed be a good idea for the multiple upload feature to eventually be dependent on the user's upload vs deletion statistics. Perhaps if we do manage to find a way to ascertain % of reverts for a particular username, we can set a requirement like "at least 50 uploads, and less than 10% of uploads are reverted".
That is out of the scope of both our grant task and GSoC, though. So for the moment, to be safe, my proposal would be:

Multiple uploads should only be done for images of the same thing (ergo only one title and desc, with numbers appended as a suffix automatically). We probably want to make this explicit to the user by having text in the upload screen that says: "Provide a title and description for these [n] images", where we fill [n] in with the number that the user selected.
For the time being, limit the number of uploads per upload round to 5. I think this should be mostly enough for legitimate users (I have never needed more than 3-4 personally), but will prevent new users from "uploading their entire camera roll". Later on, we can consider increasing the limit for users with very good stats?

we need to enforce the limit on the number of images that can be uploaded at one go

Why does such a limit exist anyways?

we need to enforce the limit on the number of images that can be uploaded at one go

Why does such a limit exist anyways?

Just so that anyone doesn't try to upload a lot of random images at once.

That's fair. Shouldn't be too hard to implement :)


null response to commands other than .connect()

I am having a problem running on V7.20-1 Controller.  The Robot Controller is not returning a response for methods other than connect().
Take a look at the screen shot and you will see the "curpos" command and empty response:
cmd.encode(): b'curpos\n'
resp:
The empty response is what is causing the exception when trying to split(":")
I have tried many things, but nothing seems to get a response.
Any ideas?
FYI - the success line at the top of the screen shot is the call to connect() .. and the Robot2 class is my copy of your class just with some print statements for debugging

Can you please try decreasing string length from 254 to 128 in all of the .kl files? I assume that might be the problem for controller versions v7.x

Yes - I forked your project and fixed all the build errors for V7.2  i.e. class or variable names longer than 12 chars and strings set to 128.  The software is definitely running on the Robot Controller, and the .connect() method appears to work, however other commands (move, curpos, curjpos, etc) don't move the robot and don't return a response.

Can you try this simple command:
print(f"Get gripper state: {robot.get_rdo(7)}")
We can start debugging from there.

same result -- I have attached sample code and stacktrace

No difference if when I use your main branch directly -- sample code --

The only difference I have found between your instructions and my v7.2 controller is:  No ability to set port number on Server Tag:

Can you add the following command on line 66 in mappdk_server.kl:
WRITE(resp, CR)
It will output the resp on teach pendant. Let’s see whether we can get the output there.

Where should I see the output?  Should it be on the User screen under the sentence "MAPPDK SERVER started" ??  Because I"m not seeing anything on the User screen:

For reference, here is all I changed in my fork to make your project compile and run on V7.2
https://github.com/bigeetea/fanucpy/pull/2/files

Whenever you run any command from python, it should be visible after MAPPDK SERVER started.

you said python in your last comment.. I think you meant Karel since we're still talking about mappdk_server.kl .... correct?

I figured out why I didn't see anything on the User screen... we aren't taking the ELSE side of the logic:

cmd is definitely uninitialized

You should put:
WRITE("RESP:", resp, CR)
here:
https://github.com/torayeff/fanucpy/blob/1a2141af4abaceac82b93738e815982b9bda228f/src/fanuc-driver/mappdk_server.kl#L66
Then call Python command such as:
print(f"Get gripper state: {robot.get_rdo(7)}")
Please check if the above works and we can continue debugging from there.

same result .. nothing except "MAPPDK SERVER started" is ever printed .. the reason is because we never run line # 66
the reason is because cmd is uninitialized, so we never go into the ELSE side of that logic.. it always runs line # 62 and # 63
        IF UNINIT(cmd) THEN
            keep_conn = FALSE

I believe the problem is something inside of mappdk_comm.kl OPEN_COMM method... it has something to do with line # 48
MSG_CONNECT(server_tag, status)
...something isn't happening correctly with that upon startup
I'd be happy to share my screen via zoom and pair debug this issue if you'd like.

Drop me email at<EMAIL_ADDRESS>

It seems there is a small typo in this line. Can you please also change it to:
'$HOSTS_CFG[' + server_str + '].$SERVER_PORT'


nessie control stats and ignore all dev versions when post stats

Codecov Report

Merging #626 into master will decrease coverage by 1.28%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #626      +/-   ##
==========================================
- Coverage   42.40%   41.12%   -1.29%
==========================================
  Files         129      129
  Lines       11097     9975    -1122
==========================================
- Hits         4706     4102     -604
+ Misses       5851     5336     -515
+ Partials      540      537       -3

Impacted Files
Coverage Δ

config/config.go
31.84% <0.00%> (-0.59%)
:arrow_down:

fileutil/writer_reader.go
55.00% <0.00%> (-6.54%)
:arrow_down:

catalog/cache.go
11.11% <0.00%> (-6.54%)
:arrow_down:

block/gs/compose.go
64.28% <0.00%> (-6.31%)
:arrow_down:

catalog/diff.go
18.51% <0.00%> (-5.73%)
:arrow_down:

auth/cache.go
12.00% <0.00%> (-5.65%)
:arrow_down:

metastore/glue/partition_collection.go
84.61% <0.00%> (-4.58%)
:arrow_down:

api/authorization.go
45.45% <0.00%> (-4.55%)
:arrow_down:

auth/compat.go
52.00% <0.00%> (-4.25%)
:arrow_down:

catalog/model.go
77.77% <0.00%> (-4.05%)
:arrow_down:

... and 120 more

Continue to review full report at Codecov.

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


[BUG] (Packages are not visible)

Please confirm these before moving forward

[X] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
[X] I have tested that this issue has not been fixed in the latest (beta or stable) release.
[X] I have checked the FAQ section for solutions
[X] This issue is about a bug (if it is not, please use the correct template)

Describe your issue
Some packages were installed on my computer, which weren't shown in the Installed Packages.
Steps to reproduce the issue
Go to Installed Packages.
WingetUI Log
https://1drv.ms/t/s!Aqq-Je19xlrfh0YzkmlUNZZn230g?e=ncyq5s

Package Managers Logs
https://1drv.ms/t/s!Aqq-Je19xlrfh0WGlOA6ioLAW7g2?e=ta6SO6

Relevant information
No response
Screenshots and videos

The source called Winget wasn't found, hence the packages weren't found. This is the reason, just for information.

Fixed! Just had to restart the app

I tried to restart the app, but nothing changed.

Please go to WingetUI Settings -> Winget -> Reset Sources
Then, please follow the steps on #1721

Sure, I will try that and tell.

Fixed!


Store ddem example to minimize test/doc computing times

Update examples.py
Added process_coregistered_example to xdem/examples.py that works similarly as download_longyearbyen_examples.
To differentiate the two when loading data from examples, I have renamed FILEPATHS into FILEPATHS_DATA and added a FILEPATHS_PROCESSED.
Now one can load the dDEM example through: examples.FILEPATHS_PROCESSED['longyearbyen_ddem']. I have refactored previous usages of FILEPATHS into FILEPATHS_DATA.
@erikmannerfelt I see most of your test cases for volume/ddem and plot scripts in the documentation simply use the difference between the non-aligned Longyearbyen rasters (rather than doing a N&K like I did in spatial_stats). Should we change those to using the dDEM data now that it is available, or keep them as is?

It's great that you're tackling this!
I wonder about the FILEPATHS_DATA name, however.. Previously, I've been a little annoyed by the fact that users may need to both run a function that doesn't return anything, and call an uppercase dictionary, just to get an example file:
xdem.examples.download_longyearbyen_examples()
filepath = xdem.examples.FILEPATHS[...]

What would have been so much nicer is a function close to what is in geoutils:
filepath = xdem.examples.get_example(...)  # This downloads/creates the example if needed

This could also work with the processed data. If get_example() requires processing, it will do that under the hood.
Some pseudocode could be:
def get_example(name: str) -> str:
    # Return the filepath if it's already downloaded/exists
    if existing:
          return FILEPATHS[name]  # or FILEPATHS_DATA/FILEPATHS_PROCESSED
    # Process the file if need be (if it doesn't exist)
    if name in FILEPATHS_PROCESSED:
          process_coregistered_example()
          return associated_filepath

    # If no processing is needed but it doesn't exist, download the examples.
    download_longyearbyen_examples()
    return xdem.DEM("path/to/example.tif")

Under the hood, the functions and dicts that you made can be used, but in the documentation, a more simple function call like this would be nice.
Thoughts, @rhugonnet @adehecq ?

Fully agree, will modify accordingly!
We also have to keep in mind this is part of test and docs, so not really meant for people other than developers to use ;)

I wrote this:
def get_path(name: str) -> str:
    """
    Get path of example data
    :param name: Name of data
    :return:
    """
    if name in list(FILEPATHS_DATA.keys()):
        download_longyearbyen_examples()
        return FILEPATHS_DATA[name]
    elif name in list(FILEPATHS_PROCESSED.keys()):
        process_coregistered_examples()
        return FILEPATHS_PROCESSED[name]
    else:
        raise ValueError('Data name should be one of "'+'" , "'.join(list(FILEPATHS_DATA.keys())+list(FILEPATHS_PROCESSED.keys()))+'".')

@erikmannerfelt How does this look?

@rhugonnet, that looks perfect to me!! While you're at it though, could you remove/make optional the print statement in download_longyearbyen_examples since this will be run tens of times in the tests?
It's populating the test results everywhere, along with the "No metadata could be read from filename"!
It would be great if all test cases now used this new function instead of the old FILEPATHS system!

@rhugonnet, that looks perfect to me!! While you're at it though, could you remove/make optional the print statement in download_longyearbyen_examples since this will be run tens of times in the tests?
It's populating the test results everywhere, along with the "No metadata could be read from filename"!
It would be great if all test cases now used this new function instead of the old FILEPATHS system!

On it!

It's populating the test results everywhere, along with the "No metadata could be read from filename"!

I thought we had added a verbose setting to SatelliteImage?

It's populating the test results everywhere, along with the "No metadata could be read from filename"!

I thought we had added a verbose setting to SatelliteImage?

Ah I see it's a silent argument but that defaults to False! Well that's a one-line PR ;)


Add textedit event

This makes it possible to dispatch the 'textedit' event added in #5109 by WindowSDL and sub class.
*Sample code to display the text being edited on the label
https://github.com/Adachinski/kivy_textedit_sample

@Adachinski Hi, thanks for the PR. I wonder if you could simplify the example you provide in the separate repository into a single file that shows the feature? I think it'd be a nice addition to the examples section.

@Adachinski @okajun35 I apologize for the delay, the PR seems OK to me.

@KeyWeeUsr Thanks for your work.


Error while executing firenet.py

while issuing command python3 firenet.py models/test.mp4  got the following error.
All necessary packages are installed.
import tflearn
File "/usr/local/lib/python3.6/dist-packages/tflearn/init.py", line 4, in
from . import config
File "/usr/local/lib/python3.6/dist-packages/tflearn/config.py", line 5, in
from .variables import variable
File "/usr/local/lib/python3.6/dist-packages/tflearn/variables.py", line 7, in
from tensorflow.contrib.framework.python.ops import add_arg_scope as contrib_add_arg_scope
File "/usr/local/lib/python3.6/dist-packages/tensorflow/contrib/init.py", line 27, in
from tensorflow.contrib import cudnn_rnn
File "/usr/local/lib/python3.6/dist-packages/tensorflow/contrib/cudnn_rnn/init.py", line 28, in
from tensorflow.contrib.cudnn_rnn.python.ops.cudnn_rnn_ops import CudnnGRU
File "/usr/local/lib/python3.6/dist-packages/tensorflow/contrib/cudnn_rnn/python/ops/cudnn_rnn_ops.py", line 21, in
from tensorflow.contrib.cudnn_rnn.ops import gen_cudnn_rnn_ops
File "/usr/local/lib/python3.6/dist-packages/tensorflow/contrib/cudnn_rnn/ops/gen_cudnn_rnn_ops.py", line 940, in
_op_def_lib = _InitOpDefLibrary()
File "/usr/local/lib/python3.6/dist-packages/tensorflow/contrib/cudnn_rnn/ops/gen_cudnn_rnn_ops.py", line 365, in _InitOpDefLibrary
_op_def_registry.register_op_list(op_list)
File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/framework/op_def_registry.py", line 35, in register_op_list
assert _registered_ops[op_def.name] == op_def
AssertionError
Computing Environment (please complete the following information):

Linux Ubuntu 17.10
Tensorflow Version:  2.0
OpenCV Version: 3.3.1

In essence we do not (and cannot easily) support TensorFlow 2.0 because TFlearn, which this project is based upon, is not available with TensorFlow > 1.15 (google: "tensorflow 2.0 tflearn" for the background).
As you an see - your failure is at the import tflearn line even before you get to the code specific to this project.
[ Why did we use TFlearn ? - because it was 2017 and Pytorch et al., was not mature enough yet and this was the goto "easy to use" package for this type of work ]
A workflow to make this repo work on your system is via a Tensorflow 1 virtual environment. Install the required packages for virtualenv on Linux Ubuntu 17.10 and then ...
virtualenv --system-site-packages -p python3 ./venv/tf-1.1.5-gpu
source ~/venv/tf-1.1.5-gpu/bin/activate
pip install tensorflow-gpu==1.15
pip install tflearn
....
python3 firenet.py models/test.mp4

I am more than happy to be corrected if someone can post a pull request for a set of TF 2.0 fixes (but as far as I can tell the complexity of such a fix  is way beyond the TF 1.x -> TF 2.x translation scripts etc).


ncx pageTarget type not checked

As noted in the samples repository issues (https://github.com/IDPF/epub3-samples/issues/11), the type attribute is not restricted to the values front, normal and special.
The rng definition is currently the very permissive:
			<attribute name="type">
				<text/>
			</attribute>

But should be an enumeration:
			<attribute name="type">
				<choice>
				    <value>front</value>
				    <value>normal</value>
				    <value>special</value>
				</choice>
			</attribute>

Fixed in PullRequest #762. Please have a look.


Site [in progress]

Fixes #7
TODO:

[ ] Logo
[ ] Header
[ ] Footer
[ ] Home page
[ ] Publish site GitHub action
[ ] Add medium blog post to cats-parse blog
[ ] Site versioning (optional) could potentially lift the scripts from courier see: here

so happy to see progress on this! thank you!


feat: support serialization of multiexponentiation handles (PROOF-920)

Rationale for this change
Add API functions to read and write multiexponentiation handles to disk.
With these functions, it can be significantly cheaper to create handles.
What changes are included in this PR?

Add sxt_multiexp_handle_new_from_file and sxt_multiexp_handle_write_to_file to blitzar_api.h.

Are these changes tested?
Yes.

:tada: This PR is included in version 1.81.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[COLLABORATION] P.R to bring Collaboration branch up to date with master

Test PR to review the rebase. Do not merge.

Collaboration should now be up-to-date with master


Create collector to check if an IPAM prefix exists in a Netbox instance

The purpose of this collector is to check if one or more IPAM prefixes exist in a Netbox instance. This is a pre-requisite to automating creation of IPAM prefixes, since Netbox will allow you to add duplicate prefixes.
One reason it allows duplicates is because the tenant group, tenant, VRF, status, etc, can be different. Netbox assumes the user will validate those things before creating a prefix--it does not try to validate it for them.
After reviewing the available Netbox fields, I think the validators should be:

Prefix
Status
VRF
Region
Site group
Site
Tenant Group
Tenant

In an ideal world, the user could choose which fields they want to validate. However, the problem we are solving right now is replicating data from Infoblox into Netbox. So, for now we will stick to defining the validators.


Autocomplete false, and new _() instead of new Awesomplete()

autocomplete="off" no longer works in chrome.
http://stackoverflow.com/questions/15738259/disabling-chrome-autofill
The second commit fixes https://github.com/LeaVerou/awesomplete/issues/16744

Merged, though initialization code should probably be after Awesomplete is exported to self, but that's another issue.
Thanks!

In the future, please try to open 1 PR per issue you're fixing. If I only wanted to merge 1 fix here, I wouldn't be able to.

@mc808 Yes "off" is the correct standard, the problem we have is Chrome doesn't seem to be follow it, at least not for all versions. As many people suggest in the SO link above - "false" fixed it for me. It is indeed bizarre that "off" works for you on Chrome 44/Windows and it does not for me.

This (https://code.google.com/p/chromium/issues/detail?id=468153) see's quite a heated discussion on the matter with the Chromium team. There maybe a better solution out of this, albeit a nice one.

Oops I was commenting on the page for the commit itself, which didn't show this back story.
Looks like there are two different auto-thingies in conflict with each other: autocomplete (showing a dropdown list of previously typed inputs) and autofill (automatically filling in credentials when a login form is detected). If I'm reading right, setting "off" will disable the autocomplete dropdown that was plaguing me, while setting any invalid value such as "false" will disable autofill but won't disable autocomplete...
I hope that's not the case. Otherwise I wonder if it would work to set "off" on the input element and "false" on the form (assuming there's a form)?

For me, using the latest Firefox and Chrome versions (on Ubuntu) I get the native dropdown of previously entered stuff on top of awesomplete’s dropdown with suggestions. If I change to autocomplete="off" (off instead of false) that native dropdown disappears, which is what I want.
As far as I understand, autocomplete="off" was added to awesomplete for one reason: To disable the native dropdown. The linked SO question in the OP does not mention anything (as far as I can see) that autocomplete="off" fails to do so; it seems to be about preventing Chrome from autofilling form fields (such as saved usernames and passwords).
Please revert commit 6611606.


Add "Code of Conduct" link to footer

fixes issue 42!

Thank you for getting to this so quickly.
The code is valid and works but it doesn't have the header change in there. #45 adds the content to both places but I can ensure you that we're going to be making more changes around the Code of Conduct and the website.
I hope you'll take a look at future issues that will be up later today around this.

I just took a second look at this request and the other request.  If you don't mind please add the CoC to the header as described in the original request.

Updates to the website made this not able to approve.
Thank you again for making a contribution and the work that you committed did play a part in the development of the site. Even if the site doesn't show it, we consider you a contributor to this project!
We hope you'll be able to contribute in the future.


figure out how to use a javaagent with Ceylon

I supect, but am not certain, that -javaagent simply doesn't work with ceylon run.

I can attest that at least ceylon test does support -javaagent just fine:
        <!--
            We have to run Java with a special JVM option to add the JaCoCo Java Agent.
            The ceylon-test ant task doesn’t support that, but luckily the 'ceylon test' tool does:
            Set the JAVA_OPTS environment variable.
        -->
        <exec executable="${ceylon.executable}">
            <arg value="test"/>
            <arg value="test.ceylon.ast.core"/>
            <arg value="test.ceylon.ast.create"/>
            <arg value="test.ceylon.ast.redhat"/>
            <arg value="test.ceylon.ast.samples"/>
            <env key="JAVA_OPTS" value="-javaagent:${jacoco.agent.jar}=destfile=${jacoco.exec.file},append=false"/>
        </exec>

From the ceylon.ast build.xml file, for JaCoCo test coverage reports.

Then I hypothesize that the problems might arise mainly when the javaagent is contained in a jar that the Ceylon program itself imports.


nokogiri update due to CVE

see here: https://github.com/sparklemotion/nokogiri/blob/master/CHANGELOG.md#security-notes

Can you update the the source of this dependency or add the peer requirement of >= the insecure version? It'll probably be in Gemfile


add chunk/chunk size to influx shell doc

Thank you, @corylanou! I cherry-picked these over to the new 1.3 directory: https://github.com/influxdata/docs.influxdata.com/pull/1163/commits/47639f5968545edfb29279d30184e8f6e82e8aa2.


dec28Of2019MomentObject.add(1, 'week').('YYYY-ww') is bad

Create a moment object (momentDate) with the date 2019-12-28

momentDate.add(1, 'week').format('YYYY-ww') => "2019-01" which is a bug!

Not a bug.
You need to look for 'week year' in the documentation, and make sure you're using the appropriate 'week year' token when formatting: e.g. 'gggg-ww' instead of 'YYYY-ww' (or, for ISO week numbering: 'GGGG-WW')

Thanks for the workaround! But please, could you describe me why Locale week of year is different than ISO week numbering? Those should match and they don't

ISO has a specific set of rules:

first day of the week is Monday
first week of the year contains January 4th

Your locale may have different rules: e.g. your week may start on a Sunday.


How to keep window size fixed when zooming font?

How can one keep the window size fixed when zooming font?
This is growing to be a critical feature for me. Managing a multiple-display-monitor without this becomes quite tedious. VimR and iTerm2 can do this.
From 2014, 2015:
https://superuser.com/questions/797827/keep-window-size-when-resizing-font-in-macvim

Use set guioptions+=k. I have contemplated making this the default, but generally followed the conservative "don't change defaults" Vim mentality though I'm still back-and-forth on this.

Just found this and am loving 'k' option!    almost.
I'm using a function to cycle thru a font list.  After changing fonts, it displays the font name as a mode msg.
With 'k', the window gets cleared after a brief flash of the font name.
Here's the function:
    " Increment circular list.  See :help expr-%
    let g:fc_current = (g:fc_current + a:dir) % len(g:fc_list)
    if g:fc_current < 0
      let g:fc_current = len(g:fc_list) - 1
    endif
    let &guifont = g:fc_list[g:fc_current]
    redraw
    echohl ModeMsg
    echo g:fc_current ": " &gfn
    echohl NONE
  endfunction```

Is there a way to have 'k' set and keep the message from clearing?

I missed this comment @rwmitchell but in case you still have this issue today, the reason why it flashes is that the different fonts have different font sizes and it causes Vim to resize. Any time Vim is resized, it clears the message (I don't think there's an option to configure this but I could be wrong).
To solve this, you could either turn off the option by doing set guioptions-=k when using your font toggling function. Alternatively, you can use a timer to print the text just a split second later, and this would allow it to be printed right after the resize:
function! DisplayFont(timer)
    echohl ModeMsg
    echo g:fc_current ": " &gfn
    echohl NONE
endfunc

function! FontCycle(dir)
    " Increment circular list.  See :help expr-%
    let g:fc_current = (g:fc_current + a:dir) % len(g:fc_list)
    if g:fc_current < 0
      let g:fc_current = len(g:fc_list) - 1
    endif
    let &guifont = g:fc_list[g:fc_current]
    redraw
    let g:fc_timer = timer_start(10, 'DisplayFont')
endfunction

Thanks!
I had ultimately solved it by adding a function to call ShowFont(), written exatctly as yours, but without the timer arg.  I then used a hotkey to call it.
I added your timer line, but 10 didn't work - changed to 50 and it worked perfectly!
Thanks again!!


Fix typoes, finnish

See #16285 . Two minor typos,
CC @flammie , with some more questions in the issue [re French blocks in this Finnish file]?

if possible @flammie please approve

the typo fixes are correct, not sure if I can approve somewhere?

thanks!


Remove use of defaultProps on functional components

Further to #949
defaultProps should be replaced with default values on functional components
related https://github.com/facebook/react/pull/16210 https://github.com/yannickcr/eslint-plugin-react/issues/2396

Has there been or is there any plan for movement on this? It seems like quite a simple thing to fix and I'm starting to see warnings a lot in newer apps built, even with the latest release.
These warnings are making it difficult to read console logs from the apps.
I'd be happy to take a stab at it, but I have one question before I start. I see a number of components where the defaultProps is setting undefined to props and I don't understand why, maybe using defaultProps you must set it to something. Now if we remove the defaultProps in favour of default params, I don' think doing something like icon = undefined is the right thing to do, but you may disagree. Lets take icon-title as an example:
IconTitle.defaultProps = {
  icon: undefined,
  children: undefined,
};

I would just remove these default props and leave the component as ({ icon, children }), but you may have other ideas.

I'd be happy to take a stab at it

That would be great, thanks!

but I have one question before I start. I see a number of components where the defaultProps is setting undefined to props and I don't understand why

I think this was due to a lint rule we used to have that required it. It's a bit overkill but my understanding was the idea was to ensure defaultProps acted as a form of documentation, to keep that documentation thorough, and to ensure the default props for any new props that are added are considered.

I would just remove these default props and leave the component as ({ icon, children }), but you may have other ideas.

Yes, I think this would be the approach to take

@penx I have gone through all the code and changed all but one Function component, there are uses of defaultProps in class a styled components which I have left as is.
The one Function component I'm having some trouble with is the components/tabs/src/atoms/tab/index.tsx Tab component. I'm having some trouble with the Interface, I believe it is doing some validation on the props, but this is a bit beyond my experience with typescript. I have no idea what to change here, any insight would help.
I tried:
const Tab: TabType = ({ selected = false, ...props }) => (
  <StyledListItem>
    <StyledHyperLink selected={selected} {...props} />
  </StyledListItem>
);

But this gave the error

'selected' is missing in props validation eslint react/prop-types

I have just disabled react/prop-types for this single line, there are other examples of disabling this rule in other code. If there is a better way to resolve this though, I'd happily change the code I have.

Thanks! Are you able to raise a pull request for what you have?

@penx I just tried to create a PR, I tried to push my branch but got a permission denied error. I was under the impression this was an open-source project?
If you can give me the permissions to push a branch, I'll get a PR created for what I have.

You’ll need to fork govuk-react and open a PR from your fork

Okay I've added a PR, you can see at https://github.com/govuk-react/govuk-react/pull/1388, I'm not familiar with the approving workflows model, so not sure what to do next, I either missed it or it wasn't in the contributing doc. Can you advise @penx


Clamp the focusTab action to the number of available tabs

Summary of the Pull Request
When we perform a focusTab action, we currently do nothing if the parameter was greater than the number of tabs. This PR changes that behavior. Now, focus-tab -t 999999 will always focus the last tab, instead of silently doing nothing.
PR Checklist

[x] Closes #9369
[x] I work here
[x] Tests added/passed
[n/a] Requires documentation to be updated

Validation Steps Performed

[x] ran tests
[x] validated commandline manually

Hmmmmmm.
If we're going down this road... For consistency's sake, I need ctrl+alt+9 to focus the last tab. That's how firefox, chromium, chrome, edge, legacy edge, and a bunch of other tabbed interfaces do it.

What's weird actually is how ^9 works in browsers. It is never tab 9. It is always "last tab"!

Well, it is tab 9 if the last tab is tab 9. I should not have said "never."

If we're going down this road... For consistency's sake, I need ctrl+alt+9 to focus the last tab. That's how firefox, chromium, chrome, edge, legacy edge, and a bunch of other tabbed interfaces do it.

I mean, that's not too hard - setting it to
        { "command": { "action": "switchToTab", "index": 99999 }, "keys": "ctrl+alt+9" },

should work 😋


KDE Arch icons randomly becoming unresponsive when alt-tabbing and then nothing is responsive ever

Hyprland Version
 System/Version info
<Paste the output of the command here>

Bug or Regression?
Bug
Description
KDE Arch icons randomly becoming unresponsive when alt-tabbing and then nothing is responsive ever, so I need to force close it.
How to reproduce
It seems to randomly happen when I alt-tab into it
Crash reports, logs, images, videos
No response

what is a kde arch icon?

Nothing anymore, the entire application became unresponsive but I managed to fix it. (Idk why I said icons)


Apply dead code elimination to the configuration-cache-report

For a 10x reduction in size.

@bot-gradle test and merge

OK, I've already triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test and merge

OK, I've already triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test and merge

OK, I've already triggered a build for you.


Allow selection of converters with SpikeGLXConverter Support

fix #174
This PR adds sub-converters to the options available to the user.
There's currently a blocking error when attempting to instantiate the custom converter on the GUIDE backend:
index.js:33 [main-process]: [2023-10-18 11:40:09,245] ERROR in app: Exception on /neuroconv/metadata [POST]
Traceback (most recent call last):
  File "/opt/anaconda3/envs/nwb-guide/lib/python3.9/site-packages/flask/app.py", line 1484, in full_dispatch_request
    rv = self.dispatch_request()
  File "/opt/anaconda3/envs/nwb-guide/lib/python3.9/site-packages/flask/app.py", line 1469, in dispatch_request
    return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)
  File "/opt/anaconda3/envs/nwb-guide/lib/python3.9/site-packages/flask_restx/api.py", line 404, in wrapper
    resp = resource(*args, **kwargs)
  File "/opt/anaconda3/envs/nwb-guide/lib/python3.9/site-packages/flask/views.py", line 109, in view
    return current_app.ensure_sync(self.dispatch_request)(**kwargs)
  File "/opt/anaconda3/envs/nwb-guide/lib/python3.9/site-packages/flask_restx/resource.py", line 46, in dispatch_request
    resp = meth(*args, **kwargs)
  File "/Users/garrettflynn/Documents/Github/nwb-guide/pyflask/apis/neuroconv.py", line 84, in post
    return get_metadata_schema(neuroconv_api.payload.get("source_data"), neuroconv_api.payload.get("interfaces"))
  File "/Users/garrettflynn/Documents/Github/nwb-guide/pyflask/manageNeuroconv/manage_neuroconv.py", line 240, in get_metadata_schema
    converter = instantiate_custom_converter(source_data, interfaces)
  File "/Users/garrettflynn/Documents/Github/nwb-guide/pyflask/manageNeuroconv/manage_neuroconv.py", line 203, in instantiate_custom_converter
    return CustomNWBConverter(source_data)
  File "/opt/anaconda3/envs/nwb-guide/lib/python3.9/site-packages/neuroconv/nwbconverter.py", line 65, in __init__
    self.data_interface_objects = {
  File "/opt/anaconda3/envs/nwb-guide/lib/python3.9/site-packages/neuroconv/nwbconverter.py", line 66, in <dictcomp>
    name: data_interface(**source_data[name])
  File "/opt/anaconda3/envs/nwb-guide/lib/python3.9/site-packages/neuroconv/datainterfaces/ecephys/spikeglx/spikeglxconverter.py", line 55, in __init__
    streams = streams or self.get_streams(folder_path=folder_path)
  File "/opt/anaconda3/envs/nwb-guide/lib/python3.9/site-packages/neuroconv/datainterfaces/ecephys/spikeglx/spikeglxconverter.py", line 26, in get_streams
    return SpikeGLXRecordingExtractor.get_streams(folder_path=folder_path)[0]
  File "/opt/anaconda3/envs/nwb-guide/lib/python3.9/site-packages/spikeinterface/extractors/neoextractors/neobaseextractor.py", line 71, in get_streams
    neo_reader = cls.get_neo_io_reader(cls.NeoRawIOClass, **neo_kwargs)
  File "/opt/anaconda3/envs/nwb-guide/lib/python3.9/site-packages/spikeinterface/extractors/neoextractors/neobaseextractor.py", line 64, in get_neo_io_reader
    neo_reader.parse_header()
  File "/opt/anaconda3/envs/nwb-guide/lib/python3.9/site-packages/neo/rawio/baserawio.py", line 179, in parse_header
    self._parse_header()
  File "/opt/anaconda3/envs/nwb-guide/lib/python3.9/site-packages/neo/rawio/spikeglxrawio.py", line 98, in _parse_header
    data = np.memmap(info['bin_file'], dtype='int16', mode='r', offset=0, order='C')
  File "/opt/anaconda3/envs/nwb-guide/lib/python3.9/site-packages/numpy/core/memmap.py", line 268, in __new__
    mm = mmap.mmap(fid.fileno(), bytes, access=acc, offset=start)
ValueError: cannot mmap an empty file

Fixed this issue. Was just because my testing dataset—specifically the NIDQ file for the SpikeGLX test—wasn't properly resolved

Overall looks great as a first introduction
I like the organization within the search tab too
Two minor comments, both of which can be left as future To-Do items
i)
I like the little hover info in general, but note that a lot of these descriptions were tailored to sphinx. Any idea on how to better parse the inter-sphinx links like seen below? Just looks kinda awkward - and a lot of those are programmatic

ii)
The section headers could be a little more identifiable - larger maybe? Gray background? Different format? The fact that it's not clickable is a decent indicator though

For (i), what would the ideal returned string be for an entry with these inter-sphinx links? Maybe for :py:class ~spikeinterface. it would be transformed to "spikeinterface class"?
I'll get a quick fix ready for (ii) otherwise.

For (i) the ~ before the mock import strips the parent package and it just renders as code-format (and bold I think?) the name of the item being referenced
E.g., :py:class ~spikeinterface.extractors.SpikeGLXRecordingExtractor would be rendered in docs as SpikeGLXRecordingExtractor but it would be a hyperlink to the API documentation on the SpikeInterface website
We don't need to go to that level of course; I would just use the name stripped after the . character


.execute_write(... block=True) should be the default behaviour

Every single piece of code I've written against the write APIs has used the block=True option to wait for the result.
Without that, it instead fires the write into the queue but then continues even before it has finished executing.
block=True should clearly be the default behaviour here!

This is technically a breaking change, but a GitHub code search at https://cs.github.com/?scopeName=All+repos&scope=&q=execute_write datasette -owner%3Asimonw shows only one repo not-owned-by-me using this, and they're using block=True: https://github.com/mfa/datasette-webhook-write/blob/e82440f372a2f2e3ed27d1bd34c9fa3a53b49b94/datasette_webhook_write/init.py#L88-L89

The easiest way to change this would be to default to block=True such that you need to pass block=False to the APIs to have them do fire-and-forget.
An alternative would be to add new, separately named methods which do the fire-and-forget thing.
If I hadn't recently added execute_write_script and execute_write_many in #1570 I'd be more into this idea, but I don't want to end up with eight methods - execute_write, execute_write_queue, execute_write_many, execute_write_many_queue, execute_write_script, execute_write_scrript_queue, execute_write_fn, execute_write_fn_queue.

I'm going to go with execute_write(..., block=False) as the mechanism for fire-and-forget write queries.

Updated documentation: https://github.com/simonw/datasette/blob/00a2895cd2dc42c63846216b36b2dc9f41170129/docs/internals.rst#await-dbexecute_writesql-paramsnone-blocktrue

Re-opening this because I missed updating some of the docs, and I also need to update Datasette's own code to not use block=True in a bunch of places.

Updated docs for execute_write_fn(): https://github.com/simonw/datasette/blob/75153ea9b94d09ec3d61f7c6ebdf378e0c0c7a0b/docs/internals.rst#await-dbexecute_write_fnfn-blocktrue

All of those removed block=True lines in 8c401ee0f054de2f568c3a8302c9223555146407 really help confirm to me that this was a good decision.


Fix eslint errors in generated webpack files

The settings is the main config file never used.
And in the renderer config there that comma is indeed dangling.

Thanks for the fixes @Calamari


Is it production ready?

Hi, i am really like this project and i am interesting do someone use it in production?

Unfortunately, I've been trying to use it. It's not ready. Issues found:

Have to disable MD5 auth settings in pga_hba_conf to use "password" (we don't get to change AWS/GCP settings like this) - immediate strike out for us.
Shutting down connection pool results in hang (bad if you are running a docker container)

I had better luck with the fork: https://github.com/jaceksokol/postgres-async-driver
However, even under the lightest of loads (5 concurrent user clients, with 10 requests each) - doing a single query, it hangs. That was with 30 pool connections, and even tried upping the thread count by multiples of 4 (quad core Mac).
I've had much better luck with this project: https://github.com/vietj/reactive-pg-client - performance wise it seems MUCH faster with no blocking issues - the the API is not as clean. But even that one has issues with the "tuple count" bindings for the reactivex and RxJava flavours.
So in summary, not ready yet. The forks seem to fix some issues, but at this time it's a strong avoid.
Happy to be corrected and shown how to use it in the real world

Shameless plug of my alternative project: https://github.com/cretz/pgnio


Upgrade Electron to 1.7.9

Before submitting, please confirm you've

[x] read and understood our Contributing Guidelines
[x] completed Mattermost Contributor Agreement
[x] executed npm run lint:js for proper code formatting

Please provide the following information:
Summary
Upgrade Electron 1.7.8 -> 1.7.9
I could not find significant changes excepting minor bug or security fixes.
Issue link
N/A
Test Cases
General use cases
Additional Notes
https://circleci.com/gh/yuya-oc/desktop/417#artifacts

Thanks! Downloaded the artifact and will use it for the next couple of days.
The builds for the PRs keep failing, wondering if we should look into resolving them?

Yeah, but I have tried many times to resolve the problem of CI though, I could never solved. Troublingly, recently the test is failing on my Windows. Possibly it would be hard for now.

Didn't find any issues, this is good to merge @yuya-oc

Thanks @jasonblais


Extremely slow hyperclick on a mixed JS/TS project

I like to jump around my project quickly with hyperclick, but it's extremely slow if using JS/TS and clicking on relative paths. My guess is that when baseUrl is configured in tsconfig.json that it really confuses/slows down tsserver and causes slowdowns. In general hyperclick seems to be extremely slow on a mixed project (we're in the process of migrating).
Example:
import { App } from 'apps/small/App'
import fooBar from './fooBar'
import bazBar from './bazBar'

I have "allowJs": false and "checkJs": false so the apps/small/App path doesn't hyperclick like expected, but the relative paths ./fooBar and ./bazBar take FOREVER to navigate to. I see the pending bar animation forever before it finally gets there. Also my CPU usage skyrockets to 100-150%.

VSCode Version: Version 1.32.0-insider
OS Version: OS X Mojave

Does this issue occur when all extensions are disabled?: Yes

Can you please share a small example project that demonstrates this issue

Closing as we need more information to investigate this. The example in the comment does not provide enough context of the project structure or what the tsconfig/jsconfig contains


⚠ Bofrost.at has degraded performance

In fadf8cb, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1857 ms

Resolved: Bofrost.at performance has improved in 57f0f07 after 6 minutes.


All codes are expired

as of now all codes generated they are expired

Same issue

Same issue

Is your switch clock and pc/phone (whatever device you are using to access the website) synced up? Timestamps are encoded into the password and the website uses the clock of your device so the clocks being wrong is the only reason I can think of off the top of my head as to why this is occuring.

This was my issue, I forgot I had adjusted my system clock on the switch. Thank you so much!


Analysis

@agendazhang added basic analysis, but a couple of changes need to be made and I will do them now. A logistic regression model would be better used than a decision tree regressor, and that was not used in DSCI 571 either. The column used should be "Route" while that has not been used.  Performance metrics, and cross validation need to be added as part of the analysis. As mentioned, I will do the aforementioned, but it would be good practice to keep in mind for next time

Completed the mentioned tasks, now only the description is remaining, @agendazhang is working on it

Completed in milestone 1


added a python script to validate the sonar token before it is generated

Added new python script to validate the sonar token generation
If token exists then the process of generation is skipped.

This issue is fixed based on
https://github.com/Accenture/adop-docker-compose/issues/285

Please let me know who can be the reviewer and if anything needs to be fixed or improved.

Hi @RobeDevOps Thank you for the PR! Looks good to me!
Just wondering if it's possible to extend the existing bash script to deal with the case where a token already exists rather than needing an extra python script to do the checking? I think it will make it easier to debug and decipher if all the logic for the sonar auth token generation is encapsulated within one script. What do you think?
/CC @RobertNorthard

@RobeDevOps Yes I think, let's proceed with that approach, this will keep it cleaner and make it easier to debug, thanks!

@dsingh07 I removed the python script and added the python code as simple extension into the bash script file.

If the list is empty return empty token so, token is gonna be generated
Looping the token arrays and it returns the token ( if exists)
Finally returns empty value if not token found.

Please let me know if that is ok. I think the python script is simple and adding jq to the Dockerfile is going to increase the image size and also a new tool and dependencies.

Thanks a lot @RobeDevOps that sounds good to me, I'll try and test it as soon as possible and hopefully merge :)

Thanks @RobeDevOps - I like the approach

I squashed the commits in one. 👍

@RobeDevOps New 0.3.5 release is created: https://hub.docker.com/r/accenture/adop-jenkins/builds/
Please can you create an accompanying to adop-docker-compose to update the image tag?


Update sample config to include opsgenie example

I was trying to figure out how to set up opsgenie and ended up digging out the syntax from an older PR. This seems like the canonical place for it to be documented.

Thanks!


Allow to set the dpi of the output raster

I think we did this in geotransect too.

We probably have to be a bit careful with setting output DPI in seisplot, because it uses ‘real world’ sizes for the plot — traces per inch and inches per second. I have never tested the actual output sizes of things, but I think changing the output DPI will break this — unless you compute a new internal scale to account for it.
All this might be different for PNG vs PDF (which perhaps accounts for real world plot sizes).

Good point. I'll try this for the same 'real world' data dimensions and see if it produces the same size size plot. DPI should only be as big as it needs to be to avoid large image file sizes. Save time seems to take the most amount of time when running seisplot.


arpack fails to build under aarch64 Darwin

Describe the bug
Reported via email by a Nix user without a GitHub account.
Steps To Reproduce
$ nix-build -A arpack
building '/nix/store/pb2102yd1x50ls4592zi48jjirsddmwc-arpack-3.8.0.drv'...
unpacking sources
unpacking source archive /nix/store/vn4vxkl4c218smc8k8yxcww77n9ssl8x-source
source root is source
patching sources
applying patch /nix/store/9apqzvzdlwwy5p72ra1r9a1aswqjci71-pkg-config-paths.patch
patching file CMakeLists.txt
updateAutotoolsGnuConfigScriptsPhase
configuring
fixing cmake files...
cmake flags: -DCMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_BUILD_TYPE=Release -DCMAKE_SKIP_BUILD_RPATH=ON -DCMAKE_INSTALL_LOCALEDIR=
/nix/store/a9qs6hnzwrhgvqhc42762dx25ky35aav-arpack-3.8.0/share/locale -DCMAKE_INSTALL_LIBEXECDIR=/nix/store/a9qs6hnzwrhgvqhc42762dx25ky35aav-arpack-3.8.0/libexec -DCMAKE_INSTALL_LIBDIR=/nix/store/a9qs6hnzwrhgvqhc427
62dx25ky35aav-arpack-3.8.0/lib -DCMAKE_INSTALL_DOCDIR=/nix/store/a9qs6hnzwrhgvqhc42762dx25ky35aav-arpack-3.8.0/share/doc/arpack -DCMAKE_INSTALL_INFODIR=/nix/store/a9qs6hnzwrhgvqhc42762dx25ky35aav-arpack-3.8.0/share/
info -DCMAKE_INSTALL_MANDIR=/nix/store/a9qs6hnzwrhgvqhc42762dx25ky35aav-arpack-3.8.0/share/man -DCMAKE_INSTALL_OLDINCLUDEDIR=/nix/store/a9qs6hnzwrhgvqhc42762dx25ky35aav-arpack-3.8.0/include -DCMAKE_INSTALL_INCLUDEDI
R=/nix/store/a9qs6hnzwrhgvqhc42762dx25ky35aav-arpack-3.8.0/include -DCMAKE_INSTALL_SBINDIR=/nix/store/a9qs6hnzwrhgvqhc42762dx25ky35aav-arpack-3.8.0/sbin -DCMAKE_INSTALL_BINDIR=/nix/store/a9qs6hnzwrhgvqhc42762dx25ky3
5aav-arpack-3.8.0/bin -DCMAKE_INSTALL_NAME_DIR=/nix/store/a9qs6hnzwrhgvqhc42762dx25ky35aav-arpack-3.8.0/lib -DCMAKE_POLICY_DEFAULT_CMP0025=NEW -DCMAKE_OSX_SYSROOT= -DCMAKE_FIND_FRAMEWORK=LAST -DCMAKE_STRIP=/nix/stor
e/jgaarpq3rdfk7gbm0gm3xlh8hhbw15ay-clang-wrapper-11.1.0/bin/strip -DCMAKE_RANLIB=/nix/store/7lfjbip2dvhvnhvdj0kx4d63apqlz83v-cctools-binutils-darwin-949.0.1/bin/ranlib -DCMAKE_AR=/nix/store/7lfjbip2dvhvnhvdj0kx4d63a
pqlz83v-cctools-binutils-darwin-949.0.1/bin/ar -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++ -DCMAKE_INSTALL_PREFIX=/nix/store/a9qs6hnzwrhgvqhc42762dx25ky35aav-arpack-3.8.0 -DBUILD_SHARED_LIBS=ON -DINTERFACE
64=0
CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required):
Compatibility with CMake < 2.8.12 will be removed from a future version of
CMake.
Update the VERSION argument <min> value or use a ...<max> suffix to tell
CMake that the project does not need compatibility with older versions.
-- The C compiler identification is Clang 11.1.0
-- The Fortran compiler identification is unknown
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /nix/store/jgaarpq3rdfk7gbm0gm3xlh8hhbw15ay-clang-wrapper-11.1.0/bin/clang - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Checking whether Fortran compiler has -isysroot
-- Checking whether Fortran compiler has -isysroot - yes
-- Checking whether Fortran compiler supports OSX deployment target flag
-- Checking whether Fortran compiler supports OSX deployment target flag - yes
-- Detecting Fortran compiler ABI info
-- Detecting Fortran compiler ABI info - failed
-- Check for working Fortran compiler: /nix/store/08nypsgnh2skq55xxmv38s45hffj99wn-gfortran-wrapper-11.1.0/bin/gfortran
-- Check for working Fortran compiler: /nix/store/08nypsgnh2skq55xxmv38s45hffj99wn-gfortran-wrapper-11.1.0/bin/gfortran - broken
CMake Error at /nix/store/zpf2rni9fdrx5flx5xab6wjnb16jifr6-cmake-3.21.2/share/cmake-3.21/Modules/CMakeTestFortranCompiler.cmake:54 (message):
The Fortran compiler
"/nix/store/08nypsgnh2skq55xxmv38s45hffj99wn-gfortran-wrapper-11.1.0/bin/gfortran"
is not able to compile a simple test program.
It fails with the following output:
Change Dir: /tmp/nix-build-arpack-3.8.0.drv-0/source/build/CMakeFiles/CMakeTmp
Run Build Command(s):/nix/store/57dwqr6igadm896armq61h96psdni160-gnumake-4.3/bin/make -f Makefile cmTC_3c7b7/fast && /nix/store/57dwqr6igadm896armq61h96psdni160-gnumake-4.3/bin/make -f CMakeFiles/cmTC_3c7b7.dir
/build.make CMakeFiles/cmTC_3c7b7.dir/build
make[1]: Entering directory '/private/tmp/nix-build-arpack-3.8.0.drv-0/source/build/CMakeFiles/CMakeTmp'
Building Fortran object CMakeFiles/cmTC_3c7b7.dir/testFortranCompiler.f.o
/nix/store/08nypsgnh2skq55xxmv38s45hffj99wn-gfortran-wrapper-11.1.0/bin/gfortran
-c /tmp/nix-build-arpack-3.8.0.drv-0/source/build/CMakeFiles/CMakeTmp/testFortranCompiler.f -o CMakeFiles/cmTC_3c7b7.dir/testFo
rtranCompiler.f.o
f951: Warning: command-line option '-iframework /nix/store/ns2z57b334ylk9dn12f7n7wfn9gd3fh6-apple-framework-CoreFoundation-11.0.0/Library/Frameworks' is valid for C/C++/ObjC/ObjC++ but not for Fortran
f951: Warning: command-line option '-iframework /nix/store/ns2z57b334ylk9dn12f7n7wfn9gd3fh6-apple-framework-CoreFoundation-11.0.0/Library/Frameworks' is valid for C/C++/ObjC/ObjC++ but not for Fortran
f951: Warning: command-line option '-Wformat=1' is valid for C/C++/ObjC/ObjC++ but not for Fortran
f951: Warning: command-line option '-Wformat-security' is valid for C/C++/ObjC/ObjC++ but not for Fortran
f951: Warning: '-Werror=' argument '-Werror=format-security' is not valid for Fortran
/private/tmp/nix-build-arpack-3.8.0.drv-0/ccPeIBZ8.s:24:15: error: index must be an integer in range [-256, 255].
ldr
x2, [x2, ___stack_chk_guard];momd
^
/private/tmp/nix-build-arpack-3.8.0.drv-0/ccPeIBZ8.s:46:15: error: index must be an integer in range [-256, 255].
ldr
x0, [x0, ___stack_chk_guard];momd
^
make[1]: *** [CMakeFiles/cmTC_3c7b7.dir/build.make:78: CMakeFiles/cmTC_3c7b7.dir/testFortranCompiler.f.o] Error 1
make[1]: Leaving directory '/private/tmp/nix-build-arpack-3.8.0.drv-0/source/build/CMakeFiles/CMakeTmp'
make: *** [Makefile:127: cmTC_3c7b7/fast] Error 2
CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
CMakeLists.txt:7 (project)
-- Configuring incomplete, errors occurred!
See also "/tmp/nix-build-arpack-3.8.0.drv-0/source/build/CMakeFiles/CMakeOutput.log".
See also "/tmp/nix-build-arpack-3.8.0.drv-0/source/build/CMakeFiles/CMakeError.log".
builder for '/nix/store/pb2102yd1x50ls4592zi48jjirsddmwc-arpack-3.8.0.drv' failed with exit code 1

Expected behavior
Build fines.
Additional context
In the attempt to build GNU octave for aarch64 darwin.
Notify maintainers
@ttuegel @dotlambda
Metadata
$ nix-info
- system: `"aarch64-darwin"`
- host os: `Darwin 20.6.0, macOS 11.6`
- multi-user?: `no`
- sandbox: `no`
- version: `nix-env (Nix) 2.3.15`
- channels(eegenolf): `"nixpkgs-21.11pre318361.a3a23d9599b"`
- nixpkgs: `/Users/eegenolf/.nix-defexpr/channels/nixpkgs`

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute: arpack
# a list of nixos modules affected by the problem
module:

Reported via email by a Nix user without a GitHub account.

I would suggest opening an issue upstream but I guess that's not an option.

Reported via email by a Nix user without a GitHub account.

I would suggest opening an issue upstream but I guess that's not an option.

Perhaps, but it seems peculiar that the user "is not able to compile a simple test program" - as if there's a bug in our gfortran compiler . Related issues: https://github.com/NixOS/nixpkgs/issues/46044 https://github.com/NixOS/nixpkgs/issues/27218
Perhaps the user should try this edit to Nixpkgs:
diff --git i/pkgs/top-level/all-packages.nix w/pkgs/top-level/all-packages.nix
index c53485f5dea..c25c34307a8 100644
--- i/pkgs/top-level/all-packages.nix
+++ w/pkgs/top-level/all-packages.nix
@@ -30503,7 +30503,9 @@ with pkgs;

   amd-libflame = callPackage ../development/libraries/science/math/amd-libflame { };

-  arpack = callPackage ../development/libraries/science/math/arpack { };
+  arpack = callPackage ../development/libraries/science/math/arpack {
+    stdenv = gccStdenv;
+  };

   blas = callPackage ../build-support/alternatives/blas { };

So even on Darwin the compiler that will be used will be gcc, to play nicely with gfortran.

The suggestion to use gccStdenv is good; I think gfortran couldn't possibly work otherwise. Beyond that, I have no idea.

I think gfortran couldn't possibly work otherwise.

But doesn't it work on x86_64 Darwin?

I think gfortran couldn't possibly work otherwise.

But doesn't it work on x86_64 Darwin?

@graham33 perhaps you could help us - does arpack and/or octave build currently on x86_64 Darwin?

Any news here? This also affects other derivations (e.g. openspecfun). @doronbehar: arpack does build on x86_64-darwin.

This issue should be renamed "gfortran broken on aarch64-darwin", as it is not specific to arpack:
$ nix-shell -p gfortran
$ cat > hello.f90
program hello
  print *, 'Hello, World!'
end program hello
^D
$ gfortran hello.f90
f951: Warning: command-line option ‘-iframework /nix/store/c63d4im7hj8273hlrgsnin5kcj7cg6ad-apple-framework-CoreFoundation-11.0.0/Library/Frameworks’ is valid for C/C++/ObjC/ObjC++ but not for Fortran
f951: Warning: command-line option ‘-iframework /nix/store/c63d4im7hj8273hlrgsnin5kcj7cg6ad-apple-framework-CoreFoundation-11.0.0/Library/Frameworks’ is valid for C/C++/ObjC/ObjC++ but not for Fortran
f951: Warning: command-line option ‘-Wformat=1’ is valid for C/C++/ObjC/ObjC++ but not for Fortran
f951: Warning: command-line option ‘-Wformat-security’ is valid for C/C++/ObjC/ObjC++ but not for Fortran
f951: Warning: ‘-Werror=’ argument ‘-Werror=format-security’ is not valid for Fortran
/tmp/ccZiB8pb.s:24:15: error: index must be an integer in range [-256, 255].
        ldr     x2, [x2, ___stack_chk_guard];momd
                         ^
/tmp/ccZiB8pb.s:46:15: error: index must be an integer in range [-256, 255].
        ldr     x0, [x0, ___stack_chk_guard];momd
                         ^

See https://github.com/NixOS/nixpkgs/issues/127608 – but we should really fix this in gfortran, rather than requiring every derivation to copy/paste the disableHardening line.

This issue should be renamed "gfortran broken on aarch64-darwin"

cc @NixOS/darwin-maintainers. To summarize, we should set:
hardeningDisable = lib.optionals (stdenv.isAarch64 && stdenv.isDarwin) [ "stackprotector" ];

In stdenv somehow.. Perhaps this should go here:
https://github.com/NixOS/nixpkgs/blob/436698cab9de492fb44205dacb8ca4a459e811a5/pkgs/build-support/cc-wrapper/add-hardening.sh#L18

We probably don't want to globally disable stack protector support, though; this only affects gfortran. Seems like we'd want to have the cc-wrapper for gfortran (on aarch64-darwin) to never inject the stackprotector options, either through a wrapCCWith option, or in the cc-wrapper.sh script itself.
Actually fixing whatever goes wrong in the toolchain would be preferable, of course.

Here's a proposal: https://github.com/NixOS/nixpkgs/pull/151983


unsupported aggregator: single_value for timestamp

Describe the bug
produced by sqlsmith
https://buildkite.com/singularity-data/pull-request/builds/6770#0182cfe9-5c8c-4561-a542-722735d42120
To Reproduce
dev=> create table t(x timestamp, y int);
CREATE_TABLE
dev=> select single_value(x) from t group by y;
ERROR:  QueryError: internal error: [PlanNode: Ok(Project(ProjectNode { select_list: [ExprNode { expr_type: InputRef, return_type: Some(DataType { type_name: Timestamp, precision: 0, scale: 0, is_nullable: true, interval_type: Unspecified, field_type: [], field_names: [] }), rex_node: Some(InputRef(InputRefExpr { column_idx: 1 })) }] }))] Failed to build executor: internal error: [PlanNode: Ok(HashAgg(HashAggNode { group_key: [0], agg_calls: [AggCall { r#type: SingleValue, args: [Arg { input: Some(InputRefExpr { column_idx: 1 }), r#type: Some(DataType { type_name: Timestamp, precision: 0, scale: 0, is_nullable: true, interval_type: Unspecified, field_type: [], field_names: [] }) }], return_type: Some(DataType { type_name: Timestamp, precision: 0, scale: 0, is_nullable: true, interval_type: Unspecified, field_type: [], field_names: [] }), distinct: false, order_by_fields: [], filter: None }] }))] Failed to build executor: internal error: unsupported aggregator: type=SingleValue input=Timestamp output=Timestamp distinct=false

Expected behavior
No response
Additional context
BTW the error message is not readable🤪

Leaving this open for a while, see if there's some existing usecase for single_value I'm unaware of, as mentioned in #4866 . Otherwise we can probably close this.

Closing this, if we want to support single-value discuss here instead: https://github.com/risingwavelabs/risingwave/issues/4866


Collapsed Sidebar uncollapses without being hovered

The sidebar opens when it shouldn't.
Expected Behavior
When the user has selected the preference to "pin sidebar", it should only open when hovered.
Current Behavior
Sometimes the sidebar randomly opens.
Steps to Reproduce
One way of (unreliably) reproducing is:

open one tab of backstage
unpin the side bar, and leave it on closed state
change tab
go back to the backstage tab
the sidebar is open and you need to hover out the mouse to close it

Your Environment

Mac Big Sur 11.5.2
Browser: Google Chrome v 92.0.4515.159

When not on VPN and interacting with the modal with the Sad Penguin and the "Spotify services unreachable" header, this seems to happen frequently.


Wrong link to store page in "free DLCs" window

Describe the bug
If you open the "show free DLCs not owned" window, the link to the store page is wrong (at least to Steam store).
It displays "https://api.steampowered.com/...." should be "https://store.steampowered.com/...."

For information, the link to the store page is wrong on all dlc, not just the “free not owned” ones.

I'm sorry to report that this issue is in fact not solved. I updated to version 1.2 today and I still see the wrong links.

I am afreid this issue is not resolved.  I updated to verison 1.2 today and still see the wrong URLs.

Did you have refresh data?


Update Github workflows and Go dependencies

This PR updates the Github workflows and Go dependencies to more recent versions:

[x] Bump go directive in respective modules to go 1.22
[x] Github workflows run with latest Go version (fixed to current 1.23)
[x] Update linter and fix errors
[x] Update README to indicate tested Go version for this SDK

Note that I didn't feel the need to bump modules straight to go 1.23 because we don't use the latest language features and go 1.22 seemed sufficient/causing less compatibility issues (or warnings) for users < Go 1.22.

@duglin for review


'sudo code file' doesn't work.

Type: Feature Request
Yeah, I know all the reasons why this is a bad idea, but it's my choice to make.
The user-data-dir is a lot of unnecessary typing.
Sometimes you need to edit a file owned by root.
"sudo vim file" works just fine, "sudo code file" should work just as well. At least put an option to disable this check.
VS Code version: Code 1.74.3 (97dec172d3256f8ca4bfb2143f3f76b503ca0534, 2023-01-09T16:57:40.428Z)
OS version: Linux x64 5.15.0-58-generic snap
Modes:
Sandboxed: No

Sometimes you need to edit a file owned by root

We allow you to save a file as admin by briefly elevating the process, have you tried, or does that not work?

That does work, but it is a hassle. If you have a file open, leave it open,
you have to enter a password every time you change it and save it.
This comes up on development virtual machines. These are low value systems,
if I screw them up, just revert the snapshot. I don't care about security
in this case, I just need to get stuff done without having to enter
passwords all over the place. I set the sudo timeout to 8 hours and don't
worry about it all day.
sudo is for the end user to use as they see fit, without application
software second guessing the end user. An option buried in the settings
would be nice, like the option for workspace trust.
On Fri, Jan 20, 2023 at 10:11 PM Benjamin Pasero @.***>
wrote:

Sometimes you need to edit a file owned by root
We allow you to save a file as admin by briefly elevating the process,
have you tried, or does that not work?
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/171878#issuecomment-1399181367,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQFPEFLL6DN6GQWSN43VPTWTNVYNANCNFSM6AAAAAAUB6SY74
.
You are receiving this because you authored the thread.Message ID:
@.***>

If you run sudo code --no-sandbox --disable-gpu-sandbox file does it work?

If you give it the --user-data-dir it does. That's a lot of verbosity that
'sudo vim my_file" doesn't have, but vim is never my first choice of
editors.
@.:~$ cd /etc/mosquitto/
@.:/etc/mosquitto$ cd conf.d/
@.:/etc/mosquitto/conf.d$ sudo code --no-sandbox
--disable-gpu-sandbox local.conf
[sudo] password for jaustin3:
You are trying to start Visual Studio Code as a super user which isn't
recommended. If this was intended, please add the argument --no-sandbox
and specify an alternate user data directory using the --user-data-dir
argument.
@.:/etc/mosquitto/conf.d$ sudo code --no-sandbox
--disable-gpu-sandbox --user-data-dir /home/jaustin3/ local.conf
Warning: 'disable-gpu-sandbox' is not in the list of known options, but
still passed to Electron/Chromium.
@.***:/etc/mosquitto/conf.d$
On Thu, Jan 26, 2023 at 10:09 AM Benjamin Pasero @.***>
wrote:

If you run sudo code --no-sandbox --disable-gpu-sandbox file does it work?
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/171878#issuecomment-1405326394,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQFPEBUJOPLJ52XB7YC243WUKVVBANCNFSM6AAAAAAUB6SY74
.
You are receiving this because you authored the thread.Message ID:
@.***>

This is the only way sorry. We really do not recommend to run VS Code as sudo.


2661 tests for pc indicator create script

Added tests for the participant indicator create script. I had to omit the test case for test_without_create_disaggs_themes because the script was asking for input which failed on the test job when committing.

Great clean tests! The script also contains a --clean flag. Should we add a test for this as well?

I think we can skip the --clean flag. I tested it locally but was unable to add it to the test cases because it requires input from the user. I found out from the test case for --create_disaggs_themes=False that if the test case includes user input it will fail/freeze when GitHub processes the automatic test cases.

Great clean tests! The script also contains a --clean flag. Should we add a test for this as well?

I think we can skip the --clean flag. I tested it locally but was unable to add it to the test cases because it requires input from the user. I found out from the test case for --create_disaggs_themes=False that if the test case includes user input it will fail/freeze when GitHub processes the automatic test cases.

Thanks Blake! That makes sense! You all good to merge from my end!


[Cloudflare for SaaS] Ngayerie patch 9

Summary
Editing the provider guides
Screenshots (optional)

Documentation checklist

[ ] The documentation style guide has been adhered to.
[ ] If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
[ ] Files which have changed name or location have been allocated redirects.

Please do not merge for now!

Approved from Product


TextStyle.apply is missing shadows argument

It's awesome that @GaryQian introduced shadows for text.
(see https://github.com/flutter/flutter/issues/3402)
However, I think there's a missing piece: TextStyle.apply does not allow applying shadows.
I can work around this by doing style.merge(TextStyle(shadows: [Shadow(...)]), but this would be cleaner using apply.
$ flutter doctor -v
[✓] Flutter (Channel master, v0.11.7-pre.52, on Mac OS X 10.13.6 17G3025, locale
    en-GB)
    • Flutter version 0.11.7-pre.52 at /Users/steve/code/flutter
    • Framework revision 79b5e5bc8a (2 days ago), 2018-11-19 10:37:55 +0100
    • Engine revision cebde437a1
    • Dart version 2.1.0 (build 2.1.0-dev.9.4 f9ebf21297)

[✓] Android toolchain - develop for Android devices (Android SDK 28.0.1)
    • Android SDK at /Users/steve/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling
      support)
    • Platform android-28, build-tools 28.0.1
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_152-release-1024-b01)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 10.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.1, Build version 10B61
    • ios-deploy 2.0.0
    • CocoaPods version 1.5.3

[✓] Android Studio (version 3.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 26.0.1
    • Dart plugin version 173.4700
    • Java version OpenJDK Runtime Environment (build
      1.8.0_152-release-1024-b01)

[✓] VS Code (version 1.29.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 2.20.0

[✓] Connected device (1 available)
    • iPhone XR • 1EE1625B-61BB-421E-B104-CB3C8A5B6076 • ios • iOS 12.1
      (simulator)

• No issues found!

Issue still exist. TextStyle.apply
Code Sample
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Material App',
      home: Scaffold(
          appBar: AppBar(
            title: Text('Material App Bar'),
          ),
          body: Center(child: Text('Hello World', style: TextStyle().apply()))),
    );
  }
}

flutter doctor -v
    en-GB)
    • Flutter version 1.16.4-pre.50 at /Users/taha/Code/flutter_dev
    • Framework revision d14a301e41 (3 days ago), 2020-03-31 19:14:22 -0400
    • Engine revision 8166a91bca
    • Dart version 2.8.0 (build 2.8.0-dev.19.0 fae35fca47)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/taha/Code/sdk
    • Platform android-29, build-tools 29.0.3
    • ANDROID_HOME = /Users/taha/Code/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.4)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.4, Build version 11E146
    • CocoaPods version 1.9.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 44.0.2
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)

[✓] VS Code (version 1.43.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.8.1

[✓] Connected device (4 available)
    • SM M305F   • 32003c30dc19668f • android-arm64  • Android 10 (API 29)
    • macOS      • macOS            • darwin-x64     • Mac OS X 10.15.4 19E266
    • Chrome     • chrome           • web-javascript • Google Chrome
      80.0.3987.149
    • Web Server • web-server       • web-javascript • Flutter Tools

• No issues found!
```

Thanks for the reminder, It looks like apply is missing a lot more than just shadows.


CBC feedback

I tried adding a bean with a roast date May 19th and didn't work. No error msg or crash, the bean profile was just no showing up. Changing the roast date to something more recent worked. new UI in v37
I would add a field in the bean profile for the processing method. coming in v37
Grind size: the current scale is not useful for my current grinders. The Mythos scale is 0 to 9 with subdivisions of 0.2, e.g., 7.2 or 8.4. The Kinu uses 3 numbers for grind size like 1:3:2. So you see the current scale is not applicable and I would suggest something more universal. Perhaps you could just allow the decimal from the current scale to be finer in steps of 0.1 instead of 0.5.
I would also have an option to set the grind size as burr gap in microns, e.g., 120  μm, with an extra binary field specifying if the burr gap is from lock or from chirp.
Add an extra field to specify the grinder and the burrs, useful for people with multiple grinders and burrs
Allow the brew temp to go lower than 87 C. I don't personally use lower temps, but know people who go as low as 80 C. coming in v37
Allow for higher ratios than 1:30. Filter2.0 or allonges can go to even up to 1:15. coming in v37
Allow for longer shot times than 60 s.  Some do shots up to 250 s! coming in v37
Preinfusion: I would like to have more options. I exclusively do dynamic blooms, where preinfusion time is not considered a variable. Instead, I would like to specify the water fill rate in ml/s during preinfusion,  peak pressure, exit pressure, water  rate in ml/s during the shot.
Add an extra field that automatically calculates the extraction yield % (EY) from the TDS and brew ratio. This already exists, but only appears when you set TDS.
add a section for used water specifying the GH and KH values and what was used to get there, like epsom salt, sodium bicarbonate, etc.

For the first issue, there should be a warning in the bean view that it will not show up unless you increase the "bean roast age limit" in the settings tab.

I noticed something else, actual yield is limited to 48. I would increase its limit, or even making limitless. It appears to be limited to 3x dosage weight.

Drink template bug: I can't set the brew temp when using Celsius.
Bean processing methods should be: natural, washed, honey, wet hulled, anaerobic, carbonic maceration
Default dosage could be something more common, e.g., in the 16-18 g range.
Allow for "tamp weight" to be hidden from the UI
Allow for "group head pre-heated" to be hidden from the UI
Allow for "portafilter pre-heated" to be hidden from the UI
Allow for "pre-infususion time" to be hidden from the UI
Allow for "drink time" to be hidden from the UI
Allow for "channeling" to be hidden from the UI
Allow for "puck consistency" to be hidden from the UI

Drink template bug: I can't set the brew temp when using Celsius.

This will be fixed in the next release

Default dosage could be something more common, e.g., in the 16-18 g range.

This will be 16g in the next release

Bean processing methods should be: natural, washed, honey, wet hulled, anaerobic, carbonic maceration

I am going to add wet hulled, anaerobic and carbonic maceration to the list but keep the others for now
This will be in the next release
I will address those hidden UI elements in a following release

@czegledi I'm going to close this issue as I've taken these bits of feedback and put them into their own issues to track separately.

Some more suggestions:
-it would be nice to see the temperature and the additional comments in the shot history. Also the GH/KH of the used water if/when this will be implemented.

I am getting some errors for the displayed yield extraction in the shot history. It shows a certain value when editing the drink, but then a different value is shown in the shot history.
It would be nice to be able to attach photos to the beans avatar. For instance I would take a picture of the bag.
The possibility of inputing the brix measurement instead of TDS and calculating the TDS and Extraction Yield from that. The formula is TDS = 0.85*Brix.
I actually quite liked the previous icons that were less colorful, more inline with iOS settings menu, etc. I would be nice to be able to select themes for the app. (I realize that this may be far fetched, but I am being nit-picking here :)
Selection sliders/menus: there are different types of selecting different numbers: gring size is one, dosage is another type,  temperature is a slider. Is there a reason for this diversity? Personally, I don't quirw like the grind selection, dosage, preinfusion, extraction time, and I would rather have them the same style as dosage.

I am getting some errors for the displayed yield extraction in the shot history. It shows a certain value when editing the drink, but then a different value is shown in the shot history.

I can't recreate this.

Selection sliders/menus: there are different types of selecting different numbers: gring size is one, dosage is another type, temperature is a slider. Is there a reason for this diversity? Personally, I don't quirw like the grind selection, dosage, preinfusion, extraction time, and I would rather have them the same style as dosage.

As I told you on Discord, this will look a lot better on iOS 16. I agree that on iOS 15.5 they don't look good, but these exact picker styles look pretty awesome on iOS 16 and for these particular selectors, I think they are faster than the dosage one. Sent you a video

Not sure what is the intent with the extraction procentage. It's not a standard metric and it took me a while to get what it actually is, but I don't find that it brings too much info.

The intent here is to show you how close you got to the ratio you wanted. For example when I stopped brewing my shot, I get anywhere from 1-4 grams of additional espresso. This is a good indicator to me when I look at the previous day(s) shot how much finer of a grind size I should attempt to use.
I'm going to close this again and take the other comments into tickets to track them.


AQAvit Meeting: Aug 10, 2022

Join via https://bluejeans.com/917304424
This meeting is part of the public Adoptium community calendar, if you wish to import the calendar use this link
Proposed Agenda:

July release summary (actions/outcomes from retrospectives)

Trickiness and implications of a respin (what it means for AQAvit releases)

Adding new platforms (aarch64 windows), documentation for 'how to'

TKG default spec
wiki page

Guidance for reporting upstream

How To and update to wiki page

New feature work

Discussion: naming conventions for <feature> tags
TRSS to AzDo link
Adding TKG smart parallelization to run-aqa

AOB

Add reference repo for git clone (git 2.11.4+)

Forgot to record this one, apologies!


Separate prisma files to manage models

In prisma1, I used to import multiple datamodels in prisma.yml like below.
  - datamodel.prisma
  - datamodel2.prisma
  - datamodel3.prisma

How can I do this in Prisma2 when there is only one file project.prisma when I generated the boilerplate.

Hi,
It is the datamodel spec: https://github.com/prisma/rfcs/blob/0002-datamodel-2/text/0002-datamodel.md#multiple-prisma-in-the-same-directory-get
However, this hasn't been implemented yet.

@hyochan we've updated the schema spec with a concrete syntax proposal to support importing from other .prisma files. You can see the spec here.
I've copied over the snippet for convenience. I'd love to hear your thoughts whether this is what you're looking for or whether you have other suggestions/requirements. 🙏
schema.prisma
import "./post.prisma"

model User {
	posts Post[]
}

post.prisma
model Post {
	title String @pg.varchar(42)
	body  String
}

Since the schema is global anyway, why not do it the v1 way and include multiple prisma files in the config and maybe even supporting globs? This should also be easier to implement, as the files just have to be joined together, no import/parsing/require/resolve stuff needed. I also think that with a huge schema it can get cumbersome to import several types, especially considering that the IDE/editor can't parse and help with those imports (for now I guess).

Hey @steebchen!
So we're not planning on re-introducing the prisma.yml file for Prisma 2 because we want to have the option to consolidate all the Prisma-related configuration into one file. As I see it, this leaves us with the following options:

Pass in schema file paths / globs via the CLI everywhere we need the schema (basically every command)
Introduce Go-style imports where folders gets concatenated together. We'd also need someway to bring in base schemas from other folders.
Introduce a import "user.schema" to the schema.

@matthewmueller could you explain how Go-style import work in this scenario?

@HosseinAgha yep,
prisma/
  base.schema
  post/
    video.schema
    picture.schema
    text.schema

In this scenario, post/video.schema, post/picture.schema, post/text.schema would all be joined as one schema without any additional syntax, so you can reference models and types within the post/ as if it's in one file.
We'd still probably need to introduce syntax to support things like base.schema importing the post package.
Something like:
import "./post"

Which would pull in the models from the whole ./post directory.

In addition to what @matthewmueller mentioned above, would it be possible to support doing the import in the format of a node glob string?
For example, if I were to organize my code into separate folders with one model per file:
models/person.prisma
models/address.prisma
...

Or into feature-specific "modules" directory of some sort:
modules/person/model.prisma
modules/person/object-type.ts
modules/address/model.prisma
modules/address/object-type.prisma

Then in the root schema.prisma file, it would be nice to be able to pull in all of the *.prisma files using a glob string such as:
import models/*.prisma or import modules/**/*.prisma
We have over 400 tables so splitting them out and then importing them with a single glob string would be ideal.

Still no news regarding the development of this feature or an alternative?
I love everything that has been done on prisma2, i would really like to migrate 😞

The links to the docs above seem to be broken, and I can't seem to find any info about this in the docs. Is there any other information on this anywhere?

I write on nestjs and use modular architecture, i want separate prisma schema for each module, i want this feature :pray:

Ditto here.

Any updates here?

Hello everyone!
the original request is to bring back the option of loading multiple PSL files via a YAML config file, the way it was handled in Prisma 1.
We are planning to enable having multiple schema files, but we don't know which implementation path we may end up choosing.
I've created #2377 to describe the high-level problem and I'll be closing this issue. Feel free to subscribe to #2377 to keep track of its progress and for feedback. 🙏

I'm using this bash script to implement modularization, which seems pretty simple to me. It basically just builds a schema using grok.
#!/bin/bash

DEST=schema.prisma

# Ensure we are in this files directory
DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" >/dev/null 2>&1 && pwd )"
cd "$DIR"

echo "// This file generated by schemaGen.sh" > $DEST
cat datasource.prisma >> $DEST
find ../src -type f -name "*.prisma" -exec cat {} >> $DEST \;

echo "SUCCESS: Prisma Schema Generated"

+1

Two years later, a team of 10 still has to mess around in 1 schema file. What could possibly go wrong.

cat command did the tricky for me.

just run cat src/prisma/docs.prisma src/prisma/schema.prisma > src/prisma/schema.prisma.new && mv src/prisma/schema.prisma.new src/prisma/schema.prisma before prisma generate command.

package.json
  "scripts": {
    "gen:schema": "cd ./prisma/schemas && cat *.prisma >> ../schema.prisma && npx prisma format"
  }

package.json
  "scripts": {
    "gen:schema": "cd ./prisma/schemas && cat *.prisma >> ../schema.prisma && npx prisma format"
  }

Thanks! Probably want to use the single ">" right? Otherwise it'll amend the same models.

@khuezy
> redirects output to a file, overwriting the file.
>> redirects output to a file appending the redirected output at the end.

But if you ran the script 2x, you'd get duplicate entries and prisma format would complain.
This also doesn't work too well if you have the prisma VSCode extension b/c it'll complain that String[]: "The current connector does not support lists of primitive types" because of the missing  datasource db provider.

@khuezy you need to use '>>' so that the files are combined. Otherwise they would overwrite each other. You'd prob want to delete the file first so that old entries are cleared. Also, if you run it and leave the schema VS should be happy I would think.
"scripts": {
    "gen:schema": "cd ./prisma/schemas && rm -rf ../schema.prisma && cat *.prisma >> ../schema.prisma && npx prisma format"
  }

cat *.prisma > ../schema.prisma would combine all the .prisma content into a single schema.prisma file, so you wouldn't need to delete the schema.prisma file right? Or am I missing something.
I ended up moving all my models into a single schema.prisma until prisma adds support for separate files. I was still getting syntax errors in VSCode.

You may be right

other method
awk 1 ./prisma/schemas/*.prisma >> ./prisma/schema.prisma && npx prisma format

other method awk 1 ./prisma/schemas/*.prisma >> ./prisma/schema.prisma && npx prisma format

@deyvisonborges as already stated by @khuezy above you should use > instead of >>
>> will append the output to an existing file. So if you run it 5 times you will have all models 5 times in your schema.prisma.
> will "overwrite" the contents of schema.prisma <= this is what you want.
There is a detailed description of output redirection: https://linuxhandbook.com/redirection-linux/

@matthewmueller is this something in the pipeline?

// directory structure

prisma
  |_ schemas
  |   |_ client.prisma
  |   |_ db.prisma
  |   |_ model1.prisma
  |   |_ model2.prisma
  |   |_ model3.prisma
  |_ schema.prisma

// package.json

{
  "scripts": {
    "gen:schema": "awk 1 ./prisma/schemas/*.prisma > ./prisma/schema.prisma && npx prisma format",
  }
}

Single > character to recreate schema.prisma file without duplicate over the next generates

// directory structure

prisma
  |_ schemas
  |   |_ client.prisma
  |   |_ db.prisma
  |   |_ model1.prisma
  |   |_ model2.prisma
  |   |_ model3.prisma
  |_ schema.prisma

// package.json

{
  "scripts": {
    "gen:schema": "awk 1 ./prisma/schemas/*.prisma > ./prisma/schema.prisma && npx prisma format",
  }
}

Single > character to recreate schema.prisma file without duplicates over the next generates

// directory structure

prisma
  |_ schemas
  |   |_ client.prisma
  |   |_ db.prisma
  |   |_ model1.prisma
  |   |_ model2.prisma
  |   |_ model3.prisma
  |_ schema.prisma

// package.json

{
  "scripts": {
    "gen:schema": "awk 1 ./prisma/schemas/*.prisma > ./prisma/schema.prisma && npx prisma format",
  }
}

Single > character to recreate schema.prisma file without duplicates over the next generates

but, how do u relate each other if there is relation between in different files?

Any official updates here?

The feature request is being tracked here: https://github.com/prisma/prisma/issues/2377