Moving forwards with ES6 and ES7

ES6
ES6 is around the door as V8 will get upgraded in node 0.12 (assuming that 0.12 makes it some day soon :smile: ). There is also the io.js initiative which is pushing for a more aggressive adoption of new V8 versions.
This raises a challenge for streamline because ES6 introduces a lot of new syntax in the language. These new syntaxes do not pose any serious conceptual challenge to streamline but they pose a practical challenge: the narcissus compiler / decompiler does not support them and will need to be enhanced.
One way forwards would be to lock streamline at ES5 level and ban ES6 features from streamline code. I don't like the idea at all because ES6 brings a lot of improvements: let and const, destructuring assignments, fat arrow, etc.
The easiest way to move forwards is probably to enhance the narcissus compiler / decompiler layer.
Another way would be switch to a different compiler / decompiler which would support the ES6 syntax. It does not look like uglify does it yet but it is more active than narcissus which hasn't been touched for 3 years. The problem with a different compiler is that the transforms (the tricky code) will have to be adapted for a different AST. I'm not too thrilled.
If we keep narcissus, the move can be done progressively. We don't need to support all ES6 features right away, we can introduce them progressively.
ES6 also introduces promises as part of the standard runtime library. This is not a problem for streamline because interoperability with promises is already there.
ES7
ES7 is likely to bring another very interesting feature: async/await support.
If this happens my intent is to support async/await as another generation option, like fibers and generators. The transformed code will be very close to the original code (especially in fast mode) because streamline is conceptually aligned on async/await. In some sense streamline is ES5 + async/await with a different syntax.
Some people may actually use this option to upgrade their code to ES7 and then abandon streamline because ES7 will give them all they need without a preprocessor.
But there may still be a few reasons to stay with streamline. Syntax is one (async/await is bulkier and does not play as well with chaining). But performance is a more important one in my eyes. The --fibers mode is very fast when you have deep call stacks on top of low level async APIs. So it will be worth benching the await option against other options before deciding to leave streamline. Instrumentation (streamline-flamegraph) may be another reason to postpone the move.
CoffeeScript
ES6 is largely irrelevant for CScripters as they have been programming with the ES6 goodies forever anyway.
ES7 may be relevant though. CS may natively get an async/await at that time and it should not be too difficult to create a script to upgrade to that.
Conclusion
Some of you may find it disappointing that I envision a conversion to ES7 async/await in the long term. But we have to be realistic: there is no way streamline can gather as much momentum as an async/await which would be baked into the language. I think it is much wiser to accept ES7 as a future and prepare for that than to end up cornered into a proprietary approach.
In the short term streamline remains more relevant than ever, especially as it can provide a seamless upgrade path to ES7 async/await later. The preprocessor approach is an advantage because it does tie the code to a specific API and it makes it possible to take advantage of new language features (generators, async/await) as they get delivered. In some sense streamline will have given us a 4+ years head start on native async support in JS.
Thoughts?

Bruno, I forgot to respond to this initially, but it was a fantastic writeup. I agree with you. Thank you!

Thanks @spollack and @aseemk.
I'm having some second thoughts on staying with narcissus though. Esprima could be a better way forwards because it supports source maps and it would allow me to drastically simplify formatting and sourcemap handling.

@bjouhier: another alternative for ES6, instead of re-implementing Streamline on a new parser, is to simply plug in an ES6→ES5 transpiler first. 6to5 is gaining a lot of traction (e.g. Facebook, Atom) and looks very well-implemented. It includes a programmatic API:
http://6to5.org/docs/usage/api/

@aseemk Great idea. That's a bit like running streamline behind the CoffeeScript transpiler. I had looked at 6to5 and seen that it uses esprima but I hadn't thought of using it directly. You just saved me many hours of work :+1:

Nice, glad! Hat-tip to @gasi for pointing me to 6to5. Agreed it's a nice analogy to CoffeeScript.

@jshepard on my team here just suggested the same idea earlier this week of using 6to5 ... very cool!

Great minds think alike :smile:

Just FYI 6to5 has been renamed to Babel.js: https://babeljs.io/

@aseemk @spollack
FYI, I've worked on it today. I decided to go ahead and replace narcissus by esprima, rather than preprocess with babel. It is probably a bit more work but it has several advantages:

streamline will directly generate ES6 code. Should be better for performance and more future proof. For example, let declarations will be compiled natively instead of being emulated with an extra closure.
esprima has good support for sourcemaps. So I can eliminate format.js and use escodegen instead.
the AST is cleaner
I've converted the callbacks transform today (the big one) and I'm at the point where the diskUsage._js example runs. Next step is to run all the unit tests and fix the glitches. Overall it has been a rather easy conversion because most of the rewriting rules are expressed with code templates.

Bruno, that's exciting, nice!

So ES6 is now officially a JavaScript standard: http://developers.slashdot.org/story/15/06/18/132225/ecmascript-6-is-officially-a-javascript-standard

included in 1.0


switch to AsSystemLabel for system set before and after

Fixes #4503

didn't notice #4503 before opening


chore(zookeeper): Allow java to be dropped in

Needed for Java FIPS

are they included in the extra_packages already? 🤔

I checked that they are not so don't you think that we should include them in extra_packages?

default = ["zookeeper", "zookeeper-bitnami-compat"], we should add openjdk-17-jre and openjdk-17-default-jvm here.

Shouldn't these be getting pulled in as package deps?

As part of a Chainguard effort to reduce code duplication and provide higher quality images, we have stopped accepting pull requests for changes to images in this repository. Due to this, we are closing all pull requests today in order to start fresh.
If you think this pull request was closed in error, please feel free to re-open this pull request or open an issue and we will try to help you out. Thank you!


Basics of Glassmorphism and Neumorphism using HTML and CSS.

Hi @praveenscience Sir, This is Titas Nath(batch 6, frontend with HTML, css). May I contribute on this topic?

Hey, @pravee I have built plenty of neomorphic projects. (clock, cards,)
some of them are pushed to my GitHub as well (neuromorphic working clock).
pls assign this issue to me I would love to work on this.

Hey,  @praveenscience  can i contribute to this?

hey  @praveenscience i want to work on this issue

/assign

/assign


java.lang.RuntimeException: Problems reading data from Binary store

Attempt to open a project in IntelliJ IDEA results in falure, caused by issue with binary store. This is a stable reproducer for one more variant of #8489
Expected Behavior
Sync finishes successfully
Current Behavior
during sync, an attempt to resolve :grails-datastore-gorm-hibernate5:testRuntimeClasspath failes due to serialization issue
Context

Steps to Reproduce

clone https://github.com/grails/gorm-hibernate5
use "open or import" in IntelliJ IDEA 2020.1 or 2020.2 EAP

Your Environment

Build scan URL: https://scans.gradle.com/s/h4ckviofqhyy4

Gradle 6.5.1 was released today with a number of fixes in that area.
Could you try it out and let us know if it resolves the issue?

Same error with 6.5.1 unfortunately.

Thanks for checking. The reproducer will help a lot for the investigation.

The underlying issue has been identified and a fix will be published with Gradle 6.6

i am still facing this with gradle 6.9. although, I'm facing this issue only in my local system. It's working fine in was.
some observations I've made :
As soon as i trigger gradle refresh from intellij, 2 bins get created in /private/var/folders. after some time both of them get deleted and the moment they get deleted, i see this build error that
Problems reading data from Binary store in /private/var/folders/5z/t4r01fl1073_1lmpjnkdty8w0000gn/T/gradle5813954742885277157.bin offset 652767 exists? true
I've already tried disabling parallel run for gradle, but that hasn't helped either.

+1 to above.
Seeing the same issue with Gradle 6.9.3 and IntelliJ 2023.1.2
This was in 6.6 according to the above comments. Regression in 6.9.x?


integrate yarn

Coverage remained the same at 100.0% when pulling 03c8d49b50ea02403651b12b0d66a35e51eeed1e on travis-yarn-1 into 8a5c53400245d29909083671bc732f19ccdcf5f0 on master.


Mediapipe code which does drawing of lines on hand

which part of java code does the display of lines on hand

The annotation part is not in java, it's in the calculator AnnotationOverlay

Is it possile to draw 3d object with mediapipe library in java code?

I think what you need is to design a mediapipe graph which can draw the designated object, then run on Android sample app.


Add ability to minimize to System Tray

Add the ability to minimize Station to the Windows system tray.

In the Options Form => General Category add a new On/Off toggle : "Minimize to System Tray"
When toggle is set to Off, Station minimizes to the Windows taskbar as it currently does
When toggle is set to On, Station minimizes to the Windows System Tray

Add a context menu to the Station System Tray icon containing these 2 options:

Open Staion - Open the Staion Main application
Exit - CLose Station Application

Also add the ability to open the Station main application by double clicking over the Station System Tray icon.

https://github.com/sandwichdoge/MinimizeToTray
I'm currently barely able to achieve this function through this program, hopefully it will be officially implemented soon, thanks : )

Yup, I'm gonna upvote this. Station is an excelllent piece of software, the ability to minimize to system tray would be the cherry on top.

Yes please add this feature. This would make the app perfect.


Use latest@version of node for automated-tests.yaml

Maybe it's a good idea to use latest@node version for automated-tests
Actually it's an "random" version
Note: it's already used there in electronRebuild

@khassel : can you rerun failed job ?
code: 'ETIMEDOUT', on fetch


plot_topo_on_ax does not treat relative paths correctly

When opening topography files in the function plot_topo_on_ax, the code doesn't seem to correctly treat paths if they are relative paths:
https://github.com/barbagroup/geoclaw-landspill/blob/032e86793becc959bbc65227a6d73cf89e250f86/geoclaw-landspill/_postprocessing/plotdepth.py#L309
Or, another way to put it, when calling plot_topo_on_ax from plot_soln_frames, we should pre-process the paths first:
https://github.com/barbagroup/geoclaw-landspill/blob/032e86793becc959bbc65227a6d73cf89e250f86/geoclaw-landspill/_postprocessing/plotdepth.py#L148-L151

Aslo in get_topo_lims
https://github.com/barbagroup/geoclaw-landspill/blob/032e86793becc959bbc65227a6d73cf89e250f86/geoclaw-landspill/_postprocessing/calc.py#L282

Aslo in get_topo_lims
https://github.com/barbagroup/geoclaw-landspill/blob/032e86793becc959bbc65227a6d73cf89e250f86/geoclaw-landspill/_postprocessing/calc.py#L282


Resource with binary data can't be created

Describe the bug
If a resource is created that uses yaml binary encoding, an error is displayed: error: error validating "/private/var/folders/_j/ztr5t9y90jq_jpsz1s2ytvk40000gp/T/c2e945a68a4e9610d06d3dc88eb2e662/resource.yaml": error validating data: ValidationError(Pod.spec.containers[0].image): invalid type for io.k8s.api.core.v1.Container.image: got "map", expected "string"; if you choose to ignore these errors, turn validation off with --validate=false.
The same resource can be created with kubectl apply using Lens terminal.
To Reproduce
Steps to reproduce the behavior:

Open a 'Create resource' terminal in Lens
Paste the following:

apiVersion: v1
kind: Pod
metadata:
  name: static-web
  labels:
    role: myrole
spec:
  containers:
    - name: web
      image: !!binary bmdpbng=
      ports:
        - name: web
          containerPort: 80
          protocol: TCP

Expected behavior
Resource is created.
Actual behavior
Error notification is displayed.
Environment (please complete the following information):

Lens Version: v5.4.0-beta.1. (Also broken in Lens: 5.3.3-latest.20211223.1).
OS: Mac
Installation method: make dev

Additional context
I was using a Lens DevCluster.

I suspect the bug is that in Lens the YAML is converted to JSON/POJO, where the binary is converted as an array of numbers, but with kubectl apply it's using Go's unmarshaling library, which does it differently. I noticed that online YAML->JSON converters convert !!binary to number array instead of string.


Change Bundle Qt backend to PyQt5

🚀 Feature

Change backend of the bundled app to PyQt5
Motivation
PyQt5 in version 5.15.4 is released in conda-forge https://anaconda.org/conda-forge/pyqt
PySide2 is still available in version 5.13.2 which uses Qt in version 5.12.9.
Switching to PyQt5 should reduce the problems with lack of features in old  Qt bindings releases (for example QComboBox.addItems for new version accept iterators (ex. dict.keys()), but PySide2 from the conda forge do not accept.

Yup!
Includes macOS arm64 binaries too!
conda create -y -n napari-env python=3.9 napari
JustWorks!

This will happen automatically on arm64 (because PySide2 is not there yet). We also use conda-forge on this platform now, too.
If I remember correctly, PySide is the default option due to the licensing. It's a pity that conda-forge does not have 5.15 yet, but there are ongoing attempts)!

If I remember correctly, PySide is the default option due to the licensing

Yes but currently napari does not ship Qt bindings in the bundle but download it from conda-forge so there is no problem with license.

I am not sure that's how GPL works. The bindings are indeed shipped in the bundled installer (as a conda package downloaded from conda-forge, that part is right).

I have an additional argument for changing the backend. It looks like most of the napari developers are using PyQt5 as the backend. 100% testing is hard. For GUI it is even harder. But such bugs could be found by daily using napari by contributors.
But if most of the contributors are using PyQt5 then PySide2 bugs will be not found. And then casual users, who are not familiar with bug reporting, use bundled versions and meet bugs but do not inform us about the existing problems.
Bug fixed in #4581 exists since 0.4.15 release and I worry this is not the only one.

Yes but currently napari does not ship Qt bindings in the bundle but download it from conda-forge so there is no problem with license.

Yes it does.

But if most of the contributors are using PyQt5 then PySide2 bugs will be not found.

Then we should probably (napari team, contributors) start using pyside2.


Allow custom filtering rules

Hi, thanks for this project.
I would like to see all the search filters together, but in a custom ordered manner. Like I want to see a search UI with three sections - Directory, Host, and Global. That way I don't have to cycle between the filter modes and can just start searching with minimal cognitive effort.

Maybe adding keybindings can solve this. https://github.com/m42e/zsh-histdb-fzf uses F1, F2, etc. as hotkeys for the different modes.


JSCS not showing errors

Getting an odd issue where if I have jscs enabled for a project, it won't show any errors in the sidebar.

So function(chat ) should produce an error because of the space before the closing paren, but it's not (the error shown is from eslint, just to make sure that syntastic is configured correctly)
If I run jscs from the command line, then I get the correct error
Illegal space before closing round bracket at input :
    13 |
    14 |  $scope.chats = Chats.all();
    15 |  $scope.remove = function(chat ) {
---------------------------------------^
    16 |    Chats.remove(chat)
    17 |  };

1 code style error found.

Here is my syntastic config.
  set statusline+=%#warningmsg#
  set statusline+=%{SyntasticStatuslineFlag()}
  set statusline+=%*
  let b:syntastic_checkers = ['jscs', 'eslint']
  let g:syntastic_check_on_open = 0
  let g:syntastic_always_populate_loc_list = 1
  let g:syntastic_auto_loc_list = 1
  let g:syntastic_check_on_wq = 1

  function! JscsFix()
      let l:winview = winsaveview()
      % ! jscs -x
      call winrestview(l:winview)
  endfunction
  command JscsFix :call JscsFix()

  noremap <leader>f :JscsFix<CR>

  let g:syntastic_mode_map = { 'passive_filetypes': ['sass', 'scss','html'] }
  map <Leader>e :lnext<CR>
  map <Leader>E :lprev<CR>

I have jscs 1.13.1 and a correct jscsrc file.
OSX 10.10.3
Vim inside of Iterm
Is this an issue with syntastic or should I report this to the jscs repo? Let me know what other information you might need.

Please open your test file, set g:syntastic_debug to 3, run :SyntasticCheck jscs, then run :mes and post the output.

Alright, so running all of that does produce an error on that line in the sidebar. Here's the output
www/js/controllers.js" 28L, 790C
syntastic: 11.649946: &shell = '/bin/zsh', &shellcmdflag = '-c', &shellpipe = '2>&1| tee', &shellquote = '', &shellredir = '>%s 2>&1', &shellslash = 0, &shelltemp = 1, &shellxquote
= '', &shellxescape = ''
syntastic: 11.650302: UpdateErrors: jscs
syntastic: 11.650740: CacheErrors: jscs
syntastic: 11.651901: g:syntastic_aggregate_errors = 0
syntastic: 11.652215: getcwd() = '/Users/mhartington/GitHub/ionic/tmp'
syntastic: 11.663889: CacheErrors: Invoking checker: javascript/jscs
syntastic: 11.664441: SyntasticMake: called with options: {'subtype': 'Style', 'preprocess': 'checkstyle', 'errorformat': '%f:%t:%l:%c:%m', 'makeprg': 'jscs --no-colors --reporter c
heckstyle www/js/controllers.js', 'returns': [0, 2]}
syntastic: 11.946389: checker output: ['<?xml version="1.0" encoding="utf-8"?>', '<checkstyle version="4.3">', '    <file name="www/js/controllers.js">', '        <error line="15" c
olumn="32" severity="error" message="Illegal space before closing round bracket" source="jscs" />', '    </file>', '</checkstyle>', '']
syntastic: 11.948034: preprocess: ['www/js/controllers.js:e:15:32:Illegal space before closing round bracket']
syntastic: 11.948291: raw loclist: [{'lnum': 15, 'bufnr': 1, 'col': 32, 'valid': 1, 'vcol': 0, 'nr': -1, 'type': 'e', 'pattern': '', 'text': 'Illegal space before closing round brac
ket'}]
syntastic: 11.948501: getLocList: checker javascript/jscs returned 2
syntastic: 11.948612: javascript/jscs raw: [{'lnum': 15, 'bufnr': 1, 'col': 32, 'valid': 1, 'vcol': 0, 'nr': -1, 'type': 'e', 'pattern': '', 'subtype': 'Style', 'text': 'Illegal spa
ce before closing round bracket'}]
syntastic: 11.948777: quiet_messages filter: {}
syntastic: 11.949037: sorted: {'_sorted': 1, '_name': '', '_owner': 1, '_columns': 1, '_rawLoclist': [{'lnum': 15, 'bufnr': 1, 'col': 32, 'valid': 1, 'vcol': 0, 'nr': -1, 'scol': 32
, 'type': 'e', 'pattern': '', 'subtype': 'Style', 'text': 'Illegal space before closing round bracket'}]}
syntastic: 11.949440: aggregated: {'_sorted': 0, '_name': 'jscs (javascript)', '_owner': 1, '_columns': 1, '_rawLoclist': [{'lnum': 15, 'bufnr': 1, 'col': 32, 'valid': 1, 'vcol': 0,
 'nr': -1, 'scol': 32, 'type': 'e', 'pattern': '', 'subtype': 'Style', 'text': 'Illegal space before closing round bracket'}]}

So, what is the problem then?

Shouldn't that run automatically on save? Similar to eslint/jshint?
Mike Hartington

On Jun 3, 2015, at 12:22 PM, LCD 047<EMAIL_ADDRESS>wrote:
So, what is the problem then?
—
Reply to this email directly or view it on GitHub.

It doesn't?  You didn't make that clear in your first report.
Please open your test file, run :SyntasticInfo, and post the output.  Then set g:syntastic_debug to 1, save the file, run :mes, and post the output.  Don't do anything else between these operations.

SyntasticInfo output:
Syntastic version: 3.6.0-90 (Vim 704, Darwin)
Info for filetype: javascript
Global mode: active
Passive filetypes: html sass scss
Filetype javascript is active
The current file will be checked automatically
Available checkers: eslint jscs jshint
Currently enabled checkers: jscs eslint

mes output:
"www/js/controllers.js" 28L, 790C
"www/js/controllers.js" 28L, 790C written
syntastic: 1.910746: &shell = '/bin/zsh', &shellcmdflag = '-c', &shellpipe = '2>&1| tee', &shellquote = '', &shellredir = '>%s 2>&1', &shellslash = 0, &shelltemp = 1, &shellxquote =
 '', &shellxescape = ''
syntastic: 1.911053: UpdateErrors (auto): default checkers
syntastic: 1.911491: CacheErrors: default checkers
syntastic: 1.912083: g:syntastic_aggregate_errors = 0
syntastic: 1.912383: getcwd() = '/Users/mhartington/GitHub/ionic/tmp'
syntastic: 1.917251: CacheErrors: Invoking checker: javascript/jscs
syntastic: 1.917847: SyntasticMake: called with options: {'subtype': 'Style', 'preprocess': 'checkstyle', 'errorformat': '%f:%t:%l:%c:%m', 'makeprg': 'jscs --no-colors --reporter ch
eckstyle www/js/controllers.js', 'returns': [0, 2]}
syntastic: 2.200134: getLocList: checker javascript/jscs returned 2

This shows syntastic running fine again.  Please set g:syntastic_debug to 3 again, save the file, run :mes , and post the output.

output from mes
"www/js/controllers.js" 28L, 790C
"www/js/controllers.js" 28L, 790C written
syntastic: 1.092656: &shell = '/bin/zsh', &shellcmdflag = '-c', &shellpipe = '2>&1| tee', &shellquote = '', &shellredir = '>%s 2>&1', &shellslash = 0, &shelltemp = 1, &shellxquote =
 '', &shellxescape = ''
syntastic: 1.092959: UpdateErrors (auto): default checkers
syntastic: 1.093457: CacheErrors: default checkers
syntastic: 1.094310: g:syntastic_aggregate_errors = 0
syntastic: 1.094477: getcwd() = '/Users/mhartington/GitHub/ionic/tmp'
syntastic: 1.099405: CacheErrors: Invoking checker: javascript/jscs
syntastic: 1.099939: SyntasticMake: called with options: {'subtype': 'Style', 'preprocess': 'checkstyle', 'errorformat': '%f:%t:%l:%c:%m', 'makeprg': 'jscs --no-colors --reporter ch
eckstyle www/js/controllers.js', 'returns': [0, 2]}
syntastic: 1.380622: checker output: ['<?xml version="1.0" encoding="utf-8"?>', '<checkstyle version="4.3">', '    <file name="www/js/controllers.js">', '        <error line="15" co
lumn="32" severity="error" message="Illegal space before closing round bracket" source="jscs" />', '    </file>', '</checkstyle>', '']
syntastic: 1.382158: preprocess: ['www/js/controllers.js:e:15:32:Illegal space before closing round bracket']
syntastic: 1.382518: raw loclist: [{'lnum': 15, 'bufnr': 1, 'col': 32, 'valid': 1, 'vcol': 0, 'nr': -1, 'type': 'e', 'pattern': '', 'text': 'Illegal space before closing round brack
et'}]
syntastic: 1.382807: getLocList: checker javascript/jscs returned 2
syntastic: 1.382975: javascript/jscs raw: [{'lnum': 15, 'bufnr': 1, 'col': 32, 'valid': 1, 'vcol': 0, 'nr': -1, 'type': 'e', 'pattern': '', 'subtype': 'Style', 'text': 'Illegal spac
e before closing round bracket'}]
syntastic: 1.383213: quiet_messages filter: {}
syntastic: 1.383558: sorted: {'_sorted': 1, '_name': '', '_owner': 1, '_columns': 1, '_rawLoclist': [{'lnum': 15, 'bufnr': 1, 'col': 32, 'valid': 1, 'vcol': 0, 'nr': -1, 'scol': 32,
 'type': 'e', 'pattern': '', 'subtype': 'Style', 'text': 'Illegal space before closing round bracket'}]}
syntastic: 1.384069: aggregated: {'_sorted': 0, '_name': 'jscs (javascript)', '_owner': 1, '_columns': 1, '_rawLoclist': [{'lnum': 15, 'bufnr': 1, 'col': 32, 'valid': 1, 'vcol': 0,
'nr': -1, 'scol': 32, 'type': 'e', 'pattern': '', 'subtype': 'Style', 'text': 'Illegal space before closing round bracket'}]}

Hmm, yeah thats really odd, it seems to be working fine now. Sorry for opening an issue :smile:

So after a lot of reading and trying to figure out what was wrong...two things came.

I had let b:syntastic_javascript_checkers = ['jscs', 'eslint'] instead of let g:
jscs wouldn't show because I needed to enable aggregate errors. let g:syntastic_aggregate_errors = 1

Putting this here for future reference.

Your analysis is incomplete.  Syntastic can set checkers locally to the current buffer, but it uses b:syntastic_checkers rather than b:syntastic_javascript_checkers, since the filetype is always the buffer's filetype.  Thus if you set b:syntastic_javascript_checkers, it gets ignored since it has no special meaning to syntastic, and thus the default list of checkers apply.  According to the output of :SyntasticInfo above, that's ['eslint', 'jscs', 'jshint'], so if eslint finds a problem first jscs is not applied.  That's where g:syntastic_aggregate_errors comes into play.  If you set the list of checkers correctly, jscs will show even with the default g:syntastic_aggregate_errors.
There's a small jungle of options, fallbacks, and defaults that syntastic uses.  Some of them exist only for backwards compatibility, and the defaults don't make sense for most people (yet I get to carry them around for the same compatibility reasons).  Sadly, you have to navigate through this jungle all by yourself.  Syntastic can't read your mind and warn you that some syntastic_mumble name doesn't have any meaning.

Good to know. Thanks for the additional info, really appreciate it :smile:


chore(deps): Update aws-sdk-go from v1.34.32 to v1.42.37

This version of the AWS SDK for go includes API changes to support
ED25519 keys for EC2 instance connect.
Prior to this update users with ED25519 keys would recieve the following
error message when trying to use sigil ssh:
Error: InvalidParameter: 1 validation error(s) found.
- minimum field size of 256, SendSSHPublicKeyInput.SSHPublicKey.

After this update, sigil ssh works as expected.

AWS release announcement:
https://aws.amazon.com/about-aws/whats-new/2022/01/ed25519-keys-authentication-ec2-instance-connect/
AWS SDK Go Release:
https://github.com/aws/aws-sdk-go/releases/tag/v1.42.37

bump ?


Headless execution of the code

Is it possible to get the code to work when we have no GUI (for example running the code on a server)? The current code wants the window in the corner or visible in order to capture screenshots - any workaround the same?
Thanks!

since you need the game to let charles see something, i see no reason in running the code on a server. Somehow Charles needs to see something

ATM, I see no way of running this headless, as the crux of this is using the screenshots from the background. I am sure there's a way to instead run GTA V headless and to grab what should be the visual output, but that's not something I am capable of writing.
Would LOVE to see such a thing though!

Managed to solve this - used selenium headless browser to do so - works great thus far!


Detect when database is from old version of redb

We'd like to be able to print a nice error message if the user uses ord to open an index that was built with an incompatible version of redb. Would it be possible to add this case to the Error enum, so we can detect it and display a good error message?
Something like this:
Error {
  VersionMismatch {
    database: u64,
    expected: u64,
  }
}

So we can detect both if our version of ord is newer than the index (user should delete index) and if our version of ord is older than the index (user should delete index or update ord).

Ya, I can have it return an error instead of panicking. Would Error::Corrupted work? I don't think including the version number is necessarily a good idea because you can't expect those to be monotonic (when redb reaches 1.0, I plan to change the version number to 1)

Error::Corrupted is okay, but it would be nice to distinguish a version mismatch from corruption, since corruption is a somewhat extraordinary event, and the user might want to know that they have disk corruption or they otherwise messed up the index.
You could use a version number that used a byte for major, a byte for minor, and a byte for patch, so 0xAABBCC, and 1 would be 0x010000, and earlier versions would be 0x00XXXX.

Does #480 cover your use case? You'll get UpgradeRequired if the on-disk format is too old, and Corrupted if it's too new. I left it returning Corrupted if the format is too new, because that case is basically indistinguishable from a corrupted file.

Yah, that's great!


Fix loading the migration/seed files in some linux systems

I found out that GLOB_BRACE is not available in solaris or alpine linux.
I get this error in my alpine php docker container:
Use of undefined constant GLOB_BRACE - assumed 'GLOB_BRACE'

I also googled that this can be problem in solaris too:
https://lodge.statamic.com/questions/580-getting-notice-use-of-undefined-constant

@onnimonni thanks, 👍  closing in favour of: https://github.com/robmorgan/phinx/commit/28d9afb01175704062277c5365f610a08fed21d4


question on your from t page example

You reference a class called Measurements in your Readme.md example.
I did not find this class in either your source or the influxdb-java source.  This was just a for instance?
Thanks

Hi,
yes, that's just an example. You can use your own measurement/metric object and supply an appropriate converter implementation for it.
Btw, in version 1.3 (published a couple of minutes ago) I tried to simplify the usage of the library. Please check the source code example inside the test space.
Cheers
Michael

Hey,
I released a new version (1.4) where I added a default template implementation (DefaultInfluxDBTemplate). You could use this right away if you are just dealing with Point objects from influxdb-java.
Hope this helps in some way.
Cheers
Michael


Are there better alternatives than uuidtools nowdays?

I'm had been using uuidtools gem for years, thanks for it! 👍
Because the last commit is from Aug 11, 2015, I'm thinking of using another UUID generator,
Are there better alternatives nowadays? In your opinion whats the best UUID generator in ruby (as 2017)?

It depends on what your requirements are.
With modern rubies you can use SecureRandom.uuid for V4 UUIDs (SecureRandom is in the standard library). Rails offerns functions for V3, V4 and V5 UUIDs out of the box.


Second Locationsupport?

Is there any progress on getting it to recognize devices a send location?

You can run 2 versions - or install all devices as one location and then
separate them in "rooms"
Each location requires separate credentials making it difficult
On Wed, Jul 24, 2024 at 6:36 PM RRoyceus @.***> wrote:

Is there any progress on getting it to recognize devices a send location?
—
Reply to this email directly, view it on GitHub
https://github.com/Panda88CO/udi-yolink/issues/32, or unsubscribe
https://github.com/notifications/unsubscribe-auth/APQ7ECUUTL3JYYOI23D5SJ3ZN7JZNAVCNFSM6AAAAABLM3KGBSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQZDQMBSHA4DENA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thanks for the fast reply.  Run 2 versions of what?

Of the node server :-)
I believe it should be possible with pg3x
On Wed, Jul 24, 2024 at 20:25 RRoyceus @.***> wrote:

Thanks for the fast reply. Run 2 versions of what?
—
Reply to this email directly, view it on GitHub
https://github.com/Panda88CO/udi-yolink/issues/32#issuecomment-2248651019,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APQ7ECSLDTYUX3MCIBPFNHTZN7WQBAVCNFSM6AAAAABLM3KGBSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBYGY2TCMBRHE
.
You are receiving this because you commented.Message ID:
@.***>


datetime picker - start/end date

Hello,
is it possible to set a start and/or end date for the datetime picker?
E.g. I would like to show as selection only the last 10 years until today.

@smensel yes you can use a function to disable any date that is < 10 years see https://www.vue-tailwind.com/docs/datepicker#disable-dates


Is tensorflow version 1.8 for sure?

Traceback (most recent call last):
File "decoder.py", line 12, in
from lsgn_data import LSGNData
File "/hltc/0/cl/tools/srl_parsers/l_he_etal_2018/lsgn/lsgn_data.py", line 2, in
import tensorflow_hub as hub
File "/homes/skumyol/venv2.7/lib/python2.7/site-packages/tensorflow_hub/init.py", line 29, in
from tensorflow_hub.estimator import LatestModuleExporter
File "/homes/skumyol/venv2.7/lib/python2.7/site-packages/tensorflow_hub/estimator.py", line 25, in
from tensorflow_hub import tf_utils
File "/homes/skumyol/venv2.7/lib/python2.7/site-packages/tensorflow_hub/tf_utils.py", line 33, in
from tensorflow.python.feature_column import feature_column_v2
ImportError: cannot import name feature_column_v2

@skumyol I spent hours trying to make it work. If you are using Python3, then you also need to add parenthesis around print statements. It didn't work with 1.8 but it worked on 1.14.0 for me. You will also need to add a symbolic link since the .so file in 1.14.0 is different. ln -s libtensorflow_framework.so.1 libtensorflow_framework.so
I pushed all required changes for Python3 here: https://github.com/savan77/lsgn/tree/python3

I'm running it in python 2.7. The error comes comes from tf-hub.
I used ** tensorflow-hub==0.2.0**


bring multi-pv support to get-mount, add get-oplog command

get-oplog synopsis:
$ /root/csi-doctor.sh get-oplog juicefs-app
kubectl -n kube-system exec -it -c jfs-mount juicefs-chaos-k8s-003-pvc-b39ff1c3-5683-4a6d-bddf-579f7ff6f022-xtlxsp -- cat /jfs/pvc-b39ff1c3-5683-4a6d-bddf-579f7ff6f022-xtlxsp/.accesslog
kubectl -n kube-system exec -it -c jfs-mount juicefs-chaos-k8s-003-juicefs-pv-rysqzd -- cat /jfs/juicefs-pv-rysqzd/.accesslog

Codecov Report
Patch and project coverage have no change.

Comparison is base (7d8a03b) 41.45% compared to head (d3f8f4e) 41.45%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #620   +/-   ##
=======================================
  Coverage   41.45%   41.45%
=======================================
  Files          32       32
  Lines        3435     3435
=======================================
  Hits         1424     1424
  Misses       1883     1883
  Partials      128      128

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


add support for symbolic links.

Currently, while decrompressing (extracting files), if any are a symbolic link, archiver will fail. This change adds in support for the tar(gz) format to open, and create tar archives with symbolic links.
Zip files, do not support symbolic links, but this update does allow them to exist, merely skipping over them. There appears to be an issue with zip files and symbolic links.
This change, also preserves the file mode, and chmod according to original file mode. (Not applicable on Windows build)
Working on testing this. Currently the included tests attempt to compress, decompress all the files in test data. I need to write a test that will prevent zip files from messing with the symbolic links.

my git fu (or lack thereof) really jacked my last pull request. Working on a cleaner one. Apologies

Cool - tests seem to be passing as-is, which is good. :+1: Might be worth adding a file mode check to the tests, I imagine that would only be an extra few lines of code to the test.

@jabgibson I'm excited to merge this in to release a '1.0'. Any chance you'd have a few minutes to make the last couple changes (assert file mode in tests & consolidate that if statement)?

@mholt done. Sorry about taking so long, working to too many projects at once.

@jabgibson No need to apologize, I just can never tell if responses just get buried in email inboxes. But I definitely understand the busy aspect of the life of a programmer! :smile: You're a champ, thank you so much for contributing!
I'll give you push rights if you ever feel like contributing again, as a thank you.


Releasing 1.0.0

Hey guys,
eslint-plugin-ava has had plenty of new rules (including all the ones listed in the beginning) since its last publication on npm. Should we publish it now?
Also, I was wondering whether we should release it as 1.0.0. The project is unlikely to have a breaking change soon, so I'd say it's better to move it to a "normal" semver version before it gets used a lot.
What do you guys think?

Yes. Good thought. Already been planning to do a 0.1.0 release for days, but time. I guess 1.0.0 makes more sense though.

Done :)

Thanks!


is forceFetch={true} supported?

Not yet. It doesn't especially make sense, because forceFetch applies to the RootContainer as a whole, rather than an individual route.


SP5: Add lock and unlock render actions to improve support for multi-threading environments

Following discussion with @bclehmann in the Discord (#1966), let's add some empty actions that get invoked at the start and end of each render which advanced users could add their own code into to wait for an optical lock state to be achieved before rendering and stay locked until after rendering.
This functionality should go in the RenderManager class https://github.com/ScottPlot/ScottPlot/blob/main/src/ScottPlot5/ScottPlot5/Rendering/RenderManager.cs

As a basic summary of our discussion:
For users on multithreaded platforms the plot may be mutated and be rendered on separate threads, which can cause unexpected issues. A pre-render action could be a mechanism to ensure plot mutation happens right before rendering on the same thread, eliminating the possibility for interleaving by essentially eliminating multithreading. Note that if someone puts an expensive pre-render action it may delay rendering by a lot, perhaps we should advise them to trigger a render once they've registered an action to avoid paying this cost at an inopportune time.
For users who specifically want multithreading, this gives them an opportunity to get their ducks in a row before rendering starts. For example, if they use locks to synchronize their threads they can wait on their locks in this action. This ensures that once the later actions start running there is no possibility for interleaving.

Done! Here's an example use:
formsPlot1.Plot.RenderManager.PreRenderLock += (s, e) =>
{
    // code here must complete before the frame renders
    System.Threading.Thread.Sleep(100);
};


How exactly does one specify provisioning-profile and signing-identity for a Release-build?

Sorry if this is a newbie question, but how exactly do I tell Fastlane to generate a Release-app and also include the ad-hoc mobile provisioning-profile so it can be installed on our test-devices?
I tried setting the "embed" parameter in Fastfile, but no matter what string I tried for the identity-parameter, it would not work. When I dragged the generated ida-file onto my phone using Xcode it would complain that either "no valid provisioning profile" is found or the entitlements don't match the provisioning profile.
Any help is very appreciated.

The easiest and best way is to configure the provisioning profile and code signing identity in your Xcode project and code signing will work automatically :+1:

Hmm. Ok some progress.
If I manually run the command krausefx-ipa build -d "./ipa" it works. It asks me what Scheme I want and what Configuration I want. The resulting .ipa can be installed on my phone.
However, if I specify everything in the command, by typing krausefx-ipa build -s "Release" -c "Release" -d "./ipa" it creates an .ipa with bad signing. It won't run on the phone.
I want to build in Jenkins so I need to specify it in one line. Is this a bug? I will try using an older version of fastlane next.

Ok, same problem with version 1.2.1.
I don't see how there's a difference between specifying scheme and configuration or being asked for it.

Hm won't work, because in the end the signing is not correct. It could have something to do with https://github.com/nomad/shenzhen/issues/165 , but not sure.

@lukas2 you can look into the example from mindnode: https://github.com/fastlane/examples/blob/master/MindNode/Fastfile There the udid of the right provisioning profile is set via environment variable. Another solutions would be to use the update_project_code_signing-action

@lukas2 @KrauseFx just saw that there is a new readme about codesigning: https://github.com/KrauseFx/fastlane/blob/master/docs/CodeSigning.md 👍🏻

Thanks @mathiasAichinger, I'll close this issue for now :+1:

This link is dead: https://github.com/KrauseFx/fastlane/blob/master/docs/CodeSigning.md
Is setting the profile directly in Xcode still the recommended way of handling this? I would like to switch the profile for different lanes but can also accomplish it with a separate script.

The most up to date documentation on how to do that is using https://codesigning.guide


Feature: Get event data from facebook

Webscrapeeee it, no need to save them just yet.

Isn't actually done, just the functional webscraping part is. Still needs to be ran automatically and connected to the site.

Now the webpage loads the event data from aws, all that is left is to reoccuringly webscrape facebook.


MDTT-34: Fix - Basic auth issue in JSON data source

Codecov Report

Merging #19 (1fce9da) into main (20bb9fb) will decrease coverage by 0.18%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##              main     #19      +/-   ##
==========================================
- Coverage     8.43%   8.25%   -0.19%
- Complexity     140     142       +2
==========================================
  Files           21      21
  Lines          403     412       +9
==========================================
  Hits            34      34
- Misses         369     378       +9

Impacted Files
Coverage Δ

src/Definition/Validate/DataSource/Validator.php
0.00% <0.00%> (ø)

src/Source/Json.php
0.00% <ø> (ø)

src/Utility/DataSource/Json.php
0.00% <0.00%> (ø)

src/Utility/HttpClient.php
0.00% <ø> (ø)

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 20bb9fb...1fce9da. Read the comment docs.


Docker CLI - docker tag --force is no longer an option

Trying to run flynn -a <app> docker push <image name> results in the following log messages and error:
flynn: getting image config with "docker inspect -f {{ json .Config }} <image name>"
flynn: tagging Docker image with "docker tag --force <image name> docker.flynn.mydomain.com/<image name>:latest"
unknown flag: --force
See 'docker tag --help'.
exit status 1

The force flag was deprecated in the CLI version I was using, and I just upgraded to the new Docker for Mac, which removes the force flag. I think the fix is just to remove that argument here, but it's sort of preventing us from doing a whole lot with docker now.

I submitted a PR for this here: https://github.com/flynn/flynn/pull/3106, but not sure if there are any side-effects (I don't have a Go environment set up, so I just deleted it using the GitHub web UI).

This is currently blocking an effort to deploy a docker-registry into our flynn repo...
Does anyone have any suggestions on other peices of software we could deploy to flynn to get a docker registry going on our cluster?

We used a Jenkins server, I can post more info about it and the deploy
script we're using when I'm not on my phone.
On Jul 19, 2016 7:28 PM, "Jon Bardin"<EMAIL_ADDRESS>wrote:

This is currently blocking an effort to deploy a docker-registry into our
flynn repo...
Does anyone have any suggestions on other peices of software we could
deploy to flynn to get a docker registry going on our cluster?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/flynn/flynn/issues/3105#issuecomment-233806121, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAex17bk7C4yD8ykK3Epy8IAQMpFsW6-ks5qXWu_gaJpZM4JKl4O
.

@diclophis the docker-receive app is actually a Docker registry, you can push and pull Docker images directly to / from it if you wish.
We should also fix the CLI (see #3106).

@lmars how might i get the docker/config.json to talk to the docker-receive app?

@diclophis run flynn docker login to update your Docker config with the appropriate credentials (it is just a wrapper around docker login).

great thanks @lmars


Touch: Make the drag start delay configurable

I think the delay before dragging starts with touch needs to be configurable.
When testing on a windows 7 pc with a 22" touchscreen, in chrome this works fine, however in firefox it seems to trigger a bit slower and you end up right clicking before the drag starts.
On windows a press and hold is generally a right click and this period is configurable by the user.

I agree that is should be configurable, I just didn't get around to it.

Cool,
Not really sure where to start on this one otherwise I would take a look.

I just added it: #1699783

I just implemented it 327db321d9911e7aae4075b09c65461f97659ad7 it will be released later today.

Simple :)


Clean up fuse unmount workflow

What changes are proposed in this pull request?
clean up unmount of fuse
Why are the changes needed?
alluxio-fuse  may cause AlluxioFuse continues to hang, and also the current flow to unmount is scattered and all over the place.
Does this PR introduce any user facing changes?
no

hey @huanghua78  i will merge this in ok?

@huanghua78 any comments about this PR?

@huanghua78 any comments about this PR?

Sorry, I will take another look today.

hey @elega i made some changes to FuseHdfsIntegrationTest/AbstractFuseHdfsIntegrationTest to generate mount point to level of test methods instead of entire class.

alluxio-bot, merge this please.

alluxio-bot, merge this please.


[PE-D][Tester C] Multiple Phone numbers and emails not allowed for contacts

Multiple Phone numbers or multiple emails not allowed for contacts. It might be helpful to save more than 1 email of some person.

Labels: severity.Low type.FeatureFlaw
original: ishan-agarwal-05/ped#3

Thanks for the suggestion, this will be included in planned enhancements


myjenkins: Rebase on Jenkins 2.0

See https://jenkins.io/2.0/

Jenkins 2.0-beta-2 released - See https://github.com/jenkinsci/docker/releases

Notice that Jenkins 2.0-rc-1 has been released - See https://hub.docker.com/r/jenkinsci/jenkins/tags/

Jenkins 2.0 released, rebase done in https://github.com/gmacario/easy-jenkins/pull/102


Update elan-web version to 1.0.0b4

New elan-web version tagged, please update

Build uses the elan-web RPM now, so does not require syncing of the version in the Ansible inventory.  Jenkins job has been updated to remove the inventory update and the creation of these issues.


dashboard components import on demand

Codecov Report

Merging #265 (deb39ac) into main (c2495b0) will decrease coverage by 0.07%.
The diff coverage is n/a.

:exclamation: Current head deb39ac differs from pull request most recent head 55b9711. Consider uploading reports for the commit 55b9711 to get more accurate results

@@            Coverage Diff             @@
##             main     #265      +/-   ##
==========================================
- Coverage   97.22%   97.14%   -0.08%
==========================================
  Files          48       48
  Lines        2699     2699
==========================================
- Hits         2624     2622       -2
- Misses         46       47       +1
- Partials       29       30       +1

Impacted Files
Coverage Δ

dtmsvr/trans_type_saga.go
97.20% <0.00%> (-1.40%)
:arrow_down:

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 c2495b0...55b9711. Read the comment docs.


'Add configuration' opens code assist in different editor

Version 1.10.0-insider
Commit 256d76fed7947e7289f921df10658d7a69233b65
Date 2017-02-22T07:09:05.746Z

open launch.json side-by-side with a editor showing a foo.ts file
set the cursor in foo.ts
click on he 'Add configuration' button in the launch.json editor
code assist opens in foo.ts

Hehe nice catch


Fix logarithm of zero bug.

We can't take the logarithm of zero, and some features do have incredibly tiny areas. Instead, cut off so that 16 is the highest zoom we'll return.
@rmarianski could you review, please?

:+1:


[UDropdown] How to prevent dropdown from closing when item clicked?

Hello,
I have a use case where I need to put a form inside a dropdown. How can I prevent the dropdown from closing when user clicks a form input element?
Here is my code:
<UDropdown :items="items" :ui="{ item: { disabled: 'cursor-text select-text' } }"
                :popper="{ placement: 'bottom-start' }">
                <template #form>
                    <form @submit.prevent="handleSubmit">
                        ...form elements here...
                        </form>
                        </UDropdown>

and script section:
const items = [
    [{
        slot: 'form'

    }]
]

Anyone got any ideas?

You might be able to solve this by defining a click function inside your item:
click: (e) => {
  e.preventDefault()
}

Hi! That did work, however, some edge cases I'll need to work around with. I'll test out some more. Thank you.
Also, you could do something like adding a @click.stop to the input:
<UInput color="primary" variant="outline" v-model="formData.childName"
                                placeholder="Child's Name (Optional)" @click.stop />
                                ```


CD and configuring the server

[x] select VPS provider
[x] install docker
[x] create account at dockerhub
[x] working CD
[x] building images
[x] pushing and pulling images to DockerHub

Done.


Added change log for upcoming 2.0.0 release

Also cleaning up migration guide and adding AngularFire2 warning to main README.md.

🚀🚀🚀


bfs: 1.3.3 -> 1.4

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/bfs/versions.
meta.description for bfs is: '"A breadth-first version of the UNIX find command"'.
Release on GitHub
Compare changes on GitHub

Checks done (click to expand)

built on NixOS
/bin/sh passed the binary check.
1 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 1.4 with grep in /nix/store/5b4zi292jgibpahgc4ff7pw9mm1zw456-bfs-1.4
directory tree listing: https://gist.github.com/d3235eaa5a2001f87714d57017c5515c
du listing: https://gist.github.com/9d9b8420c1ed0242d02b74f60f8271d8

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
bfs

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/5b4zi292jgibpahgc4ff7pw9mm1zw456-bfs-1.4 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A bfs https://github.com/r-ryantm/nixpkgs/archive/8a3c824fead236e3f8bfe5e86c578d25a8a758e7.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/5b4zi292jgibpahgc4ff7pw9mm1zw456-bfs-1.4
ls -la /nix/store/5b4zi292jgibpahgc4ff7pw9mm1zw456-bfs-1.4/bin

cc @yesbox for testing.

This pull request has been mentioned on Nix community. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/12

My guess is the Darwin failure is due to make release using LTO.  This looks like the same issue: "https://github.com/NixOS/nixpkgs/issues/19098"
I'm not sure how to fix the toolchain, but it could be worked around by just running plain make, which will pick up CFLAGS from the environment.


Investigate reducing the load time for the Program Indicators page

Opening the Program Indicators page from anywhere else in Tola routinely takes 6-10 seconds from the time I click the Indicators link until the page is loaded and ready for interaction.  I am accounting for this in my tests, but I think it would be more useful to investigate what can be done to reduce the page-load time, or at least its apparent load time.

Played with this on the dev server. Sitting at my desk, page load times are much improved. Anecdotally, load time is down to ~1sec from 7 secs or more. 💯


experiment with web workers

web workers are a means to run scripts in a separate thread. it can be helpful to experiment with launching a waku node in a worker to notice differences, if any
https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Using_web_workers

note: when working on it look out for the cases when a worker can be suspended/terminated

Might be useful to review for timeout bugs, or bugs related to too many connections being opened.


Enable java 11 in alluxio base image

By adding an argument to specify the java version, users will be able to launch Alluxio with java 11 in containers.
Only java 8 and java 11 are supported. If users try build with other versions, the build would fail with error failed to solve with frontend dockerfile.v0: failed to create LLB definition: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed. It is not intuitive at all but there is no way to print an custom error message because the error happens when it's trying to load the metadata for all images used in the dockerfile, before any script runs, where we can put our custom error message.
This is the first step of a series of updates of the images. The documentation will be updated later.

alluxio.client.file.cache.LocalCacheManagerTest timed out

Error: 6.215 [ERROR] Errors:
Error: 6.215 [ERROR] alluxio.master.journal.raft.RaftJournalTest.gainPrimacyAfterSuspend
Error: 6.216 [ERROR]   Run 1: RaftJournalTest.gainPrimacyAfterSuspend:349->promoteFollower:403 » Timeout Tim...
Error: 6.216 [ERROR]   Run 2: RaftJournalTest.gainPrimacyAfterSuspend:349->promoteFollower:403 » Timeout Tim...

LGTM, a small question that can these code be shared between Dockerfile and Dockerfile-dev?

Yes. The refactor will be part of the whole process later.

alluxio-bot, merge this please

@ssz1997 @Xenorith Just a sanity check, any doc update needed for this change?

the release notes should mention this, but could also mention this within the advanced setup seciton in the docker deploy page https://docs.alluxio.io/os/user/edge/en/deploy/Running-Alluxio-On-Docker.html#launch-alluxio-with-the-development-image

Yes we need a doc for this. Working on it.


distributed kvstore doesn't respect shape of ndarrays

Steps to reproduce:
test.py
import mxnet as mx

shape = (4, 2)

def init_kv():
    """init kv """
    kv = mx.kv.create('dist')
    kv.init(3, mx.nd.ones(shape=shape))
    return kv

def test_updater():
    def check_updater(kv):
        # single
        key = 3
        vals = mx.nd.ones(shape)
        outs = mx.nd.empty(shape)
        kv.push(key, vals)
        kv.pull(key, out=outs)
        mx.nd.waitall()

    kv = init_kv()
    kv.set_optimizer(mx.optimizer.SGD())
    check_updater(kv)

test_updater()

Add the following assertion to SGD:update_multi_precision()
    def update_multi_precision(self, index, weight, grad, state):
        assert weight.shape == (4,2), weight
        use_multi_precision = self.multi_precision and weight.dtype == numpy.float16
        self._update_impl(index, weight, grad, state,
                          multi_precision=use_multi_precision)

Run with python tools/launch.py  --launcher=local -n 2 python test.py
Traceback (most recent call last):
  File "_ctypes/callbacks.c", line 315, in 'calling callback function'
  File "/home/ubuntu/haibin2/python/mxnet/kvstore.py", line 83, in updater_handle
    updater(key, lhs, rhs)
  File "/home/ubuntu/haibin2/python/mxnet/optimizer.py", line 1484, in __call__
    self.optimizer.update_multi_precision(index, weight, grad, self.states[index])
  File "/home/ubuntu/haibin2/python/mxnet/optimizer.py", line 545, in update_multi_precision
    assert weight.shape == (4,2), weight
AssertionError: (8L,)

How critical is this issue and what is the use case (beside the test attached)?

In general the kvstore/optimizer API are broken because the shape of the NDArray on the server side is changed. This mean any optimizer that relies on the shape of the inputs (like FTRL, or any custom optimizer whose update depends on the shape).
On the other hand, this bug aborts the program when the shape is flatten to 1-D for large inputs, when the total number of elements is several billions.

I've seen complains about the above two multiple times.


The "data" argument must be of type string or an instance of Buffer, TypedArray, or DataView. Received undefined

When I tried to use it, It showed   this error

Thanks - I hadn't expected next-auth to be installed without drizzle, and so it was trying to pull in drizzle config here. This has been resolved and will be updated once I publish the next version on NPM. Cheers.


add API for initializing a new List

Issue raised in comment from ethereum-consensus
Idea is to avoid something like the below and allow for a new List to be initialized without allocating a Vec and then converting into a List.
let rotate_participation = vec![ParticipationFlags::default(); state.validators.len()];
    state.current_epoch_participation = rotate_participation
        .try_into()
        .expect("should convert from Vec to List");

For example, add impl of new for something like List<T>::new(capacity: usize) (or, in the example above, just allow for state.current_epoch_participation = List::<u8>::new(state.validators.len()).
Based on some initial research, I'm not quite sure how to do this since List obviously takes List<T, N> where N is a const usize...so List<T> would be invalid. And without knowing N at compile time, that introduces concepts like raw pointers,  unsafe rust, Box, Arc, etc. that I couldn't figure out how to use or if they even solve this problem.

E.g., this obviously doesn't work but captures the idea:
impl<T, const N: usize> List<T, N>
where
    T: SimpleSerialize + Clone,
{
    fn new(capacity: usize) -> Self {
        let data = vec![T::default(); capacity];
        data.try_into().unwrap()
    }
}

#[test]
fn create_new_list() {
    const SIZE: usize = 32; // shown to make it "work" but shouldn't be required and use `capacity` to init
    let capacity = 32;
    let value = List::<u8, SIZE>::new(capacity); // aka remove `SIZE` here
    ...
}


Unable to create just a node pool using the workers submodule

I have an existing OKE cluster. I am trying to use the workers submodule to create a node pool. After resolving many missing parameters this is what my terraform code looks like:
data.tf
data "oci_identity_availability_domains" "ads" {
  compartment_id = "<my_compartment_id>"
}

locals.tf
locals {
  ad_numbers_to_names = { for ad in data.oci_identity_availability_domains.ads.availability_domains: ad.name => ad.name }
}

node-pool.tf
module "my_oke_nodepool" {
  source = "github.com/oracle-terraform-modules/terraform-oci-oke//modules/workers?ref=v5.1.2"

  compartment_id = "<my_compartment_id>"
  tenancy_id     = "<my_tenancy_id>"

  cluster_id         = "<my_cluster_id>"
  worker_pool_mode   = "node-pool"
  worker_pool_size   = 3

  kubernetes_version = "<my_kubernetes_version>"
  image_id           = "<my_custom_image_id>"
  image_type         = "custom"
  timezone           = "Etc/UTC"
  assign_public_ip   = false
  shape = {
    shape            = "VM.Standard.E4.Flex",
    ocpus            = 4,
    memory           = 8,
    boot_volume_size = 160
  }

  assign_dns             = true
  cni_type               = "flannel"
  apiserver_private_host = "<my_apiserver_private_host>"
  worker_subnet_id       = "<my_apiserver_private_host>"
  pod_subnet_id          = null
  ad_numbers             = ["1"]
  ad_numbers_to_names    = local.ad_numbers_to_names
  agent_config           = null

  worker_pools = {
    my-nodepool = {
      create           = true,
      size             = 3,
      shape            = "VM.Standard.E4.Flex",
      ocpus            = 4,
      memory           = 8,
      boot_volume_size = 160,

    }
  }
}

However I am currently stuck on this error:
╷
│ Error: Insufficient placement_configs blocks
│
│   on .terraform/modules/my_oke_nodepool/modules/workers/nodepools.tf line 17, in resource "oci_containerengine_node_pool" "workers":
│   17:   node_config_details {
│
│ At least 1 "placement_configs" blocks are required.
╵

I cannot find sufficient submodule docs to help me resolve this I have tried adding some parameters after reading the module code i.e. availability_domains, capacity_reservation_id, and subnet_id under my-nodepool but that doesn't seem to help. Could someone please provide any pointers?

I realized I was using it the wrong way. I have shifted to the main module instead of using the submodule and that resolved all of the problems.


assigning this to default late attributes should be illegal

I figured you guys allow late attributes to be assigned this in a different class because the late attribute can't potentially have a harmful setter. But as it turns out, I can refine that attribute to add a harmful setter that can access an uninitialized attribute. I.e. you shouldn't be allowing people to assign this to default late attributes:
class Child()
{
    shared default late Parent parent;
}

class SubChild()
    extends Child()
{
    shared actual Parent parent => super.parent;
    assign parent
    {
        print(parent.huh);
    }
}

class Parent()
{
    Child child = SubChild();
    child.parent = this;
    shared String huh = "";
}

shared void run() => Parent(); // prints: <null>

In addition, much easier to reproduce, you guys shouldn't be allowing this to be assigned to late attributes in the same class:
class A()
{
    late A self;
    self = this;
    print(self.a);
    String a = "";
}

because the late attribute can't potentially have a harmful setter

I don't understand why it would be less bad without a setter. Isn't the following already 100% wrong?
class A() {
    shared late Anything x;
}

class B() {
    value a = A();
    a.x = this;
    print(a.x);
}

But regarding the setter, note that in #6455 I suggested disallowing default late.

A lot of additions

@jvasileff
As I've said, I figured that you don't allow it because it can't have a setter. That is, you could allow this to be assigned to variable attributes with the same amount of safety. But it is in the semantics of "variable" that the contract of that attribute allows it to be replaced by a getter and a setter and that variable attributes and pairs of getter+setter are interchangeable in implementing an API. That is, you can't assign this to a perceived variable attribute, because it may actually be a getter+setter pair.
But you missed the fact that default late attributes can be refined to add a setter, nullifying the whole point of not allowing variable attributes to be assigned this.

@Zambonifofex I still don't understand. You're saying that it would somehow be ok (or at least less bad) to leak this as long as it is not to an attribute marked variable? It would still a leak of this.

But you missed the fact that default late attributes can be refined to add a setter

That's not the part I'm missing.
Here's a more fleshed version of my example showing the leak w/o assign or variable:
class A() {
    shared late B x;
}

class B() {
    value a = A();
    String b;
    a.x = this; // leaks 'this'
    print(a.x.b); // prints "<null>"
    b = "";
}

shared void run() => B();

That's not the part I'm missing.

I didn't mean "you" you. I meant something more like "the Ceylon team" you, when deciding to allow this to be assigned to late attributes.

Here's a more fleshed out version of my example showing the leak w/o assign or variable

Well, that's the issue you linked me in my other thread (#4273); this is much simpler.
Either way, I think I have a potentially good idea to solve #4273, but I'll have to think a little bit more about it before sharing it. However, even with my idea, you would still be able to leak this when assigning to default late attributes.

Ok, right. So the root problem is the special exception allowing this to be assigned to late attributes, and this problem is in no way mitigated or made worse by default, variable, assign, etc.

I think I have a potentially good idea to solve #4273

cool!

Is it really the case that we now have three issues open, which all refer to the same bug? Can we please close this one, which appears to be a direct dupe of #6455?

Dupe of #6455.

@gavinking
I don't think this is the same as #6455 at all, this is more specific to assigning this to default late attributes. I think prohibiting default late is too heavy-handed, and a different solution to #6455 might still leave this problematic case.
But if your solution for #6455 does indeed end up fixing this, I'm fine with leaving this closed.


Enable RUNE onramping via Banxa

Overview
Just noticed that Banxa added support for RUNE onramping (https://banxa.com/)
Can we enable this?
References and additional details
n/a
Acceptance Criteria
AC:

RUNE is added to the list of assets available to Buy, with Banxa as the provider
THORChain is added to the list of chains to filter by
If a user selects THORChain, they see RUNE
If a user selects RUNE, they see Banxa as an available provider
If a user clicks Banxa with RUNE selected, the Banxa buy flow is opened in a new window and the users' RUNE address and asset selection are passed through

Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response

@willyogo tried building a partner URL using the same parameters as the ones Banxa are using in their landing page (https://checkout.banxa.com//?fiatAmount=100&fiatType=USD&coinAmount=56.65659463&coinType=RUNE&lockFiat=true&blockchain=THORCHAIN&orderMode=BUY), unfortunately it is not supported yet.
Added the blocked tag until this is supported upstream - when that's done, we can simply apply this patch to support it:
diff --git a/packages/caip/src/adapters/banxa/index.ts b/packages/caip/src/adapters/banxa/index.ts
index 92301df4d..5eaf02f93 100644
--- a/packages/caip/src/adapters/banxa/index.ts
+++ b/packages/caip/src/adapters/banxa/index.ts
@@ -16,6 +16,8 @@ import {
   ethChainId,
   optimismAssetId,
   optimismChainId,
+  thorchainAssetId,
+  thorchainChainId,
 } from '../../constants'

 /**
@@ -28,6 +30,7 @@ const AssetIdToBanxaTickerMap = {
   [ethAssetId]: 'eth',
   [avalancheAssetId]: 'avax',
   [optimismAssetId]: 'eth',
+  [thorchainAssetId]: 'rune',
   'eip155:1/erc20:0x7fc66500c84a76ad7e9c93437bfc5ac33e2ddae9': 'aave',
   'eip155:1/erc20:0xbb0e17ef65f82ab018d8edd776e8dd940327b28b': 'axs',
   'eip155:1/erc20:0x4d224452801aced8b2f0aebe155379bb5d594381': 'ape',
@@ -83,6 +86,7 @@ const chainIdToBanxaBlockchainCodeMap: Record<ChainId, string> = {
   [cosmosChainId]: 'COSMOS',
   [avalancheChainId]: 'AVAX-C', // note - the AVAX-C chain is not the same as the AVAX "ticker" on the banxa side
   [optimismChainId]: 'OPTIMISM',
+  [thorchainChainId]: 'THORCHAIN',
 } as const

 /**

@willyogo do you want to follow up with Banxa to see if this has been fixed yet?

You bet, just pinged them discord (https://discord.com/channels/554694662431178782/1136046536585908364/1146206257074671616)

Confirmed that RUNE has been enabled for ShapeShift on Banxa's end @gomesalexandre 🎉
https://shapeshift.banxa.com//?fiatAmount=100&fiatType=USD&coinAmount=56.65659463&coinType=RUNE&lockFiat=true&blockchain=THORCHAIN&orderMode=BUY
They also shared this doc of assets they support so we could spot any others that may be missing: https://docs.google.com/spreadsheets/d/1KU6J1Hl4vxBTIWCwWdrFfSadNltuFheQRoJyPrd0LMQ/edit#gid=366537232
If there are any others @shapeshift/product would like to enable, can ping @maaak in Banxa's Discord partner thread.


Fixed bug in test.

Got the following error message while executing the tests:
>./test
[Started testing]

[Running: tokenizers]

[Started section: 'strspn']
test.cpp:119: (next == __null) failed for: false
[End of section: 'strspn' 1 of 13 assertions failed]

[Finished: 'tokenizers' 1 test case failed (1 of 13 assertions failed)]

[Testing completed. 1 of 3 test cases failed (1 of 31 assertions failed)]

The current pointer in the code was actually moved one position to the
right of the terminal \0 character of the const char string.
Probably the test passed for others, since the memory after the string
was filled with \0 bytes.

LGTM
@b4hand -- thoughts?

Yes, this is correct. The next pointer should not be advanced when it is already pointing to the terminating \0.


MAC address for a raspi 3

The mac address of my raspberry 3 starts with '00:87:33'. Could you pls add to find.js

Sure. Can you tell me what model of chip you have? Is that the chip built into the Pi3?


64 bit support for Unreal Gold

Project Link
https://www.oldunreal.com/
Project License
Proprietary
Steam App Ids

https://steamdb.info/app/13250/

Additional Context
Latest version of OldUnreal patch (v227j) supports x64, SDL2 and ARM. XOpenGL, its default graphic renderer for Linux is a bit problematic though; better keep OpenGL renderer instead. Support for SDL2 makes sdlcl and sdl12-compat unnecessary for Unreal Gold. Also, v227j seems to offer better compatibility with new mods.
https://www.oldunreal.com/downloads/unreal/oldunreal-patches-for-unreal-latest-ver.j/
https://www.oldunreal.com/patch/unreal/oldunreal/UnrealPatch227j.7z

@rea987 It looks like people have some issues with the 64-bit version: https://github.com/luxtorpeda-dev/packages/issues/798
Are you able to run it?

Are you able to run it?

@d10sfan Yes, after installing libxmp4 from distro repos and copying additional libraries from ../Unreal Gold/Help/convenience_libs/System64 into ../Unreal Gold/System64, the game launch and runs fine by running ../Unreal Gold/System64/UnrealLinux.bin.
For the additional libraries, you need to extract ../Unreal Gold/Help/convenience_libs.tar.bz2.
Distro: Mint 21 (Ubuntu 22.04 based)
Kernel: 6.2.0-10007-tuxedo x86_64
CPU: AMD Ryzen 7 4800H
GPU: AMD Radeon RX Vega 6 (integrated)
Mesa: 22.0.5

Also, AA should be disabled for OpenGL and XOpenGL renderers as v227j contains a bug that renders wireframes for invisible objects when there's a lightning. At least for the systems using Mesa. Same goes for UT99 v469c.
https://www.oldunreal.com/phpBB3/viewtopic.php?p=101084#p10108
https://www.oldunreal.com/phpBB3/viewtopic.php?p=101132#p101132
UnrealLinux.ini
[OpenGLDrv.OpenGLRenderDevice]
UseAA=False
[XOpenGLDrv.XOpenGLRenderDevice]
UseAA=False

I'll work on adding an additional option for 64-bit
For AA, like the other one, this should be fixed in newer mesa versions.

I've added an option for this in https://github.com/luxtorpeda-dev/packages/commit/01f25871434f89c751a59655645e9c7e03a46080


Create Firebase Project for Auth

Description

We need to create a Firebase project for authentication within Forgettable.
Acceptance Criteria

[x] Create Firebase account and project

Implementation details

N/A
Testing notes

N/A

I've created the project using the projects gmail account.


Bump Dependencies #10961649751

Bumps dependencies for product-is. Link : https://github.com/wso2/product-is/actions/runs/10961649751

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


bug: v3 Navbar and Footer are not displayed correctly using Sveltekit

What version of daisyUI are you using?
v3.0.1
Describe your issue
After upgrading to v3 the navbar and the footer components stopped working correctly. Here's a screenshot of the Navbar with menu and submenu which I copied from the docs in my project.

Or here the footer with the logo section from the documentation:
.
Other components I checked so far are working just fine.
To check if some of my custom CSS doesn't interfere with DaisyUI, I deleted all of it the custom CSS temporarily but without success. The Navbar and Footer were looking the same. It doesn't make a difference if I use dev mode or the preview of the build. I tried to compare my configs with the sveltekit stackblitz one but this projects is not yet upgrade to v3. Any other ideas?
What browsers are you seeing the problem on?
No response
Reproduction URL (optional)
No response

It's probably a problem with your tailwind.config.js
Make sure the path to all your template files (any file that you have class names inside it) is addressed in content
https://tailwindcss.com/docs/content-configuration
Also make sure you're using the class names as a whole string (not half-variable):
https://tailwindcss.com/docs/content-configuration#dynamic-class-names
Let me know if these didn't fix the issue.

we were absolutely right 👍


Feature Request : adding it in Detectron2

Thank you very much for your project, really looking into it. It would be awesome to integrate it within Detectron2 pipeline as current FPN implementation is super slow.

I think integrating is a great a idea aswell, since you get a lot of functionality for free like:
-dataloaders
-training and test code
-visualization
-anchor generation
the only thing required if i am not mistaken would be to register effnet+bifpn as backbone and use that in the retinanet meta-architure. (or a slightly modified one)
the weights  of the prediction head probably need to be retrained though, not sure if that is a problem.
I have some spare time next week so i hope i can make a pull request!

+1 for this. Any update?

@hiyyg at this point, doubt I'll do it. I've looked at it a few times but just too much work for limited gain. Given how slow / unlikely they are to add 3rd party code, it'd probably end up a lonely fork that I have to maintain against their changes.
I kind of like the fact that this is stand alone, fairly compact. With openimages dataset I support more obj detection datasets now.


⚠ Bofrost.lu has degraded performance

In 478699b, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2202 ms

Resolved: Bofrost.lu performance has improved in 3044ae0 after 6 minutes.


Missing classes in docs

While checking out Lychee Link Checker report I noticed that Python SDK is missing classes in docs.
seems like Dataset,KeyValueStore & RequestQueue are missing maybe others too

You mean in the API docs, correct? The storage classes live in the Crawlee repository now. We are just re-exporting them here... It seems like more work for @barjin. We should either link these storage classes from SDK or take the docstring content from Crawlee and render them in the SDK as well. Both approaches work fine for me. cc @janbuchar

@TC-MO I believe this is resolved now - can you please confirm that?

Indeed it looks like it, we are all green on Lychee, much obliged!


base_query arbitrarily selects one bug for inclusion instead of all bug details

I've put in ANY_VALUE to make this function with MySQL 5.7 but we should probably GROUP_CONCAT or something else less dodgy. GROUP_CONCAT has the disadvantage of making 'classification' no longer reliable to order by. GROUP_CONCAT(cb.classification ORDER BY cb.classification) or similar?

We can squish this into some string format and break it apart upon load like we do with legality.
description,classification,last_confirmed|description,classification,last_confirmed|…
We might want to use a nonprinting character as the separator to minimize the chance of it blowing up. Or store as json. Our own arbitrary string serialization format probably makes little sense compared to json. This was originally not stored it's only the existence of _card_cache that means we are slotting it into a db table. But given that we are it makes me want to do it a bit more sanely (or not at all and use a join on _card_cache?)

Squishing and a bunch more besides in 7fc2337.


Update dependency on httpoison

Can you please update to allow usage of httpoison 1.8?
Thanks!

@HaleTom done here:
https://github.com/etroynov/telegraph

Now that httpoison has been bumped to 2.1+ both nadia and telegraph fail to install


Pipfile needs a way to manually specify package installation order

GDAL is a package that is used by many GIS projects. During installation, GDAL's python bindings are compiled using the headers from the existing numpy version. So you need to install numpy before GDAL, else numpy bindings will not work.
This seems to be a use case for pipenv install --sequential, but I am not able to control the order of the sequential install.
NB: you need to have libgdal-dev on Ubuntu 16 and CPLUS_INCLUDE_PATH=/usr/include/gdal and C_INCLUDE_PATH=/usr/include/gdal to reproduce this.
pipenv install numpy gdal==1.11.2 --sequential works as expected.
Then, pipenv --rm, pipenv install --deploy --sequential  gives me the wrong sequence: numpy is installed after gdal, and my numpy bindings do not work.
The sequence seems to origin from the Pipfile.lock, which is alphabetic. gdal is before numpy in the alphabet, so at least installation fails in a reproducible way.
How should I approach this issue?
Pipfile:
[[source]]
url = "https://pypi.org/simple"
verify_ssl = true
name = "pypi"

[packages]
numpy = "*"
gdal = "==1.11.2"

[dev-packages]

[requires]
python_version = "2.7"

Pipfile.lock:
{
    "_meta": {
        "hash": {
            "sha256": "42b5387796abc5d9542f6213df851d564959e44cd1c1a0789fc9dc5e0e5f5d0f"
        },
        "pipfile-spec": 6,
        "requires": {
            "python_version": "2.7"
        },
        "sources": [
            {
                "name": "pypi",
                "url": "https://pypi.org/simple",
                "verify_ssl": true
            }
        ]
    },
    "default": {
        "gdal": {
            "hashes": [
                "sha256:7827197836690815b0142412a49a97c6c6a18b21a83ece8cd6d8ec66127f10df"
            ],
            "index": "pypi",
            "version": "==1.11.2"
        },
        "numpy": {
            "hashes": [
                "sha256:0074d42e2cc333800bd09996223d40ec52e3b1ec0a5cab05dacc09b662c4c1ae",
                "sha256:034717bfef517858abc79324820a702dc6cd063effb9baab86533e8a78670689",
                "sha256:0db6301324d0568089663ef2701ad90ebac0e975742c97460e89366692bd0563",
                "sha256:1864d005b2eb7598063e35c320787d87730d864f40d6410f768fe4ea20672016",
                "sha256:46ce8323ca9384814c7645298b8b627b7d04ce97d6948ef02da357b2389d6972",
                "sha256:510863d606c932b41d2209e4de6157ab3fdf52001d3e4ad351103176d33c4b8b",
                "sha256:560e23a12e7599be8e8b67621396c5bc687fd54b48b890adbc71bc5a67333f86",
                "sha256:57dc6c22d59054542600fce6fae2d1189b9c50bafc1aab32e55f7efcc84a6c46",
                "sha256:760550fdf9d8ec7da9c4402a4afe6e25c0f184ae132011676298a6b636660b45",
                "sha256:8670067685051b49d1f2f66e396488064299fefca199c7c80b6ba0c639fedc98",
                "sha256:9016692c7d390f9d378fc88b7a799dc9caa7eb938163dda5276d3f3d6f75debf",
                "sha256:98ff275f1b5907490d26b30b6ff111ecf2de0254f0ab08833d8fe61aa2068a00",
                "sha256:9ccf4d5c9139b1e985db915039baa0610a7e4a45090580065f8d8cb801b7422f",
                "sha256:a8dbab311d4259de5eeaa5b4e83f5f8545e4808f9144e84c0f424a6ee55a7b98",
                "sha256:aaef1bea636b6e552bbc5dae0ada87d4f6046359daaa97a05a013b0169620f27",
                "sha256:b8987e30d9a0eb6635df9705a75cf8c4a2835590244baecf210163343bc65176",
                "sha256:c3fe23df6fe0898e788581753da453f877350058c5982e85a8972feeecb15309",
                "sha256:c5eb7254cfc4bd7a4330ad7e1f65b98343836865338c57b0e25c661e41d5cfd9",
                "sha256:c80fcf9b38c7f4df666150069b04abbd2fe42ae640703a6e1f128cda83b552b7",
                "sha256:e33baf50f2f6b7153ddb973601a11df852697fba4c08b34a5e0f39f66f8120e1",
                "sha256:e8578a62a8eaf552b95d62f630bb5dd071243ba1302bbff3e55ac48588508736",
                "sha256:f22b3206f1c561dd9110b93d144c6aaa4a9a354e3b07ad36030df3ea92c5bb5b",
                "sha256:f39afab5769b3aaa786634b94b4a23ef3c150bdda044e8a32a3fc16ddafe803b"
            ],
            "index": "pypi",
            "version": "==1.14.3"
        }
    },
    "develop": {}
}

Oh that’s an interesting one!
Perhaps sequential installs should always start with Pipfile ordering and should always install top level packages first? /cc @uranusjr — do you think this impacts people who depend on things like Cython in their installation ordering?

I just need numpy before gdal. For larger projects, the ideal solution would be specifying just that instead of the slower sequential install.
Is there a way to extend extras=numpy for this use case?

It is probably best for package maintainers to have appropriate extras_require flags for those usages (e.g. gdal[numpy] to require numpy before gdal; I think we account for those already). But yes it would be nice if we can default to ordering in Pipfile, following the “not worst than the predecessor” (predecessor here being requirements.txt) rule.

@uranusjr  That would be the ideal solution indeed. It seems that https://pypi.org/project/pygdal/ may solve the issue for me; they properly specify numpy as a dependency.
Apart from that, I would like to be able to control the --sequential order. To be complete: installation order now is alphabetic, and editable / VCS packages are installed first (but @techalchemy said earlier that a PR addressing the VCS issue is up already)

Another use-case:
On Windows, python-ldap is rather tricky to build and they don't publish wheels to PyPi.
You need to be able to say that your local wheel (e.g. downloaded from https://www.lfd.uci.edu/~gohlke/pythonlibs/) should be installed before anything that requires python-ldap.

I assume this is not yet solved and when you run pipenv install it is still random ?

It is not random, but there is no way to customise ordering I assume this is what you actually intend to ask).

It is not random, but there is no way to customise ordering (I assume this is what you actually intend to ask).

Yes exactly. Thanks for the response, it's clear!

This is not a proper solution, but it might be acceptable for some until (if) this feature is implemented.
pipenv install --dev appears to install dev-packages before the default packages, so after editing the Pipfile by placing the numpy dependency in dev-packages, and GDAL in packages, then pipenv install --dev --sequential seems to install numpy before GDAL and avoids the author's original error.

I believe this can be closed, more recent work on constraints from default and dev may have improved this situation.   Feel free to open a new ticket for any new issues.


JOSS paper manuscript feedback

Hi @Timozen,
here are my remarks on the software paper for the first round of review. Overall, I think it's well written and mostly contains what's required. Find my detailed feedback below (row numbers in brackets).
Major points

[9-11] I feel this passage needs some clarification/extension to fully explain the topic to non-domain-experts. What do you mean by "norm" with respect to facial structures, given that you highlight the significant variations of the human face in the previous sentence? How are deviations from this norm relevant in a medical context?
[14] How do advanced computer vision techniques help to better understand blinking w.r.t. to previous approaches?
[Summary] The transition between both paragraphs could be a bit clearer. Also, are there any general references that could be included which may help the reader to learn more about the general field of application?
[Statement of Need] All text following the first paragraph of this section [40-67] read as if they provide a general description of the software, but do not add much to the statement of need. I'd therefore suggest to restructure this bid, either by including it in the Summary section or by creating a new section.
[State of the field] I'm aware this point has been adressed in a previous issue, but I'm still wondering if there are actual other packages or software products (FOSS or proprietary) that professionals use to do the same task? If yes, these should be mentioned and the difference of JeFaPaTo briefly discussed. If not, this should also be mentioned.
[42-47] This part is a bit confusing to me: Am I correct that the blinking extraction is a two-step procedure to which you refer here as the two main parts of the tool (programming interface and GUI)? It seems to me that both parts (feature extraction and blinking detection) are in fact both included in the GUI? Then what exactly do you mean by extendable programming interface and GUI in this passage?
[Functionality and Usage & Platform Support] A lot of content that is presented in this two sections should be, in my opinion, part of a standalone software documentation rather than the software paper. The paper would benefit greatly in terms of structuring and conciseness if it did not contain elements such as the description of GUI components or a table containing package dependencies. However, I guess this issue should better be discussed elsewhere (please see my comments on the documentation and general remarks on the first round of review). I'd therefore suggest to return to these sections at a later stage.

Minor poinst

[44] high temporal resolution (?)
[53-55] This sentence is rather lengthy and I'm not sure if grammatically correct (not a native speaker)
[134] Extracted Medical ly relevant statistics (?)

References

I'd recommend to use in-text citations where appropriate (e.g. at [30]) throughout the manuscript. I think this can be achieved by removing the brackets, i.e., using @soukupovaRealTimeEyeBlink2016 instead of [@soukupovaRealTimeEyeBlink2016].
I believe the MediaPipe paper published at CVPR should be preferred over the arxiv preprint (https://research.google/pubs/mediapipe-a-framework-for-perceiving-and-processing-reality/)

Thank you very much for this valuable feedback! We highly appreciated it ^^

we added more references to give avid readers more options to inform themselves about blinking in general and the medical context
we also made the distinction between programming API and GUI more clear in the text
the summary transitions have been smoothed :)
the statement of need now includes more existing approaches.

Regarding the [Functionality and Usage & Platform Support], I agree with you that the balance in the paper itself often shifts between explanation and usage documentation.
We are also aware of this issue and are planning to create such external usage documentation together with the medical students who use the software already.


Design doc for clustering.

This is related to #2303 and steals from #2435.

cc: @smarterclayton @kelseyhightower

This LGTM.  Thanks!
--brendan

This looks great!

A few comments, otherwise LGTM

@erictune @smarterclayton Please take another look if you like.  I'll squash before I merge.

LGTM.


Update LlamaComponent.cpp

Refactor to more Unreal standard API (Issue #2)

Use Unreal TQueue Impact two fewer lines.

this is a good update


Automated cherry pick of #8178: fix: error code of external bucket not found error should be 404

Cherry pick of #8178 on release/3.3.
#8178: fix: error code of external bucket not found error should be 404

/lgtm
/approve


KeyError: 'backend' if SqLite

Hello!
I'm using Sqlite Db in my project and starting using django-ddp:
  File "/Users/user/Desktop/HuskyJam/common_venv/lib/python3.4/site-packages/dddp/apps.py", line 28, in ready
    alias, conf['backend'],
KeyError: 'backend'

Ok, now I know, that django-ddp is working only with postgres, but Exception is not reasonable because default sqlite config has no 'backend':
DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.sqlite3',
        'NAME': os.path.join(BASE_DIR, 'db.sqlite3'),
    }
}

As I see in code, Exception have to contain "django-ddp only works with PostgreSQL":
 def ready(self):
        """Initialisation for django-ddp (setup lookups and signal handlers)."""
        if not settings.DATABASES:
            raise ImproperlyConfigured('No databases configured.')
        for (alias, conf) in settings.DATABASES.items():
            if conf['ENGINE'] != 'django.db.backends.postgresql_psycopg2':
                raise ImproperlyConfigured(
                    '%r uses %r: django-ddp only works with PostgreSQL.' % (
                        alias, conf['backend'],
                    )
                )
        self.api = autodiscover()
        self.api.ready()

You're right, and even so with multiple databases the code is wrong. I'll work on a fix this week. Thanks for the report.


preserve filterList state across data prop changes

Expected Behavior

After having initialized the columns filterList, data props changes should not undo any subsequent filterList changes via UI.
Current Behavior

In the context of having initialized mui-datatables with a columns filterList, data props changes undo any subsequent changes to filterList via UI
Steps to Reproduce (for bugs)

You can see an example of how changing the data after changing the filter will just revert back to the earlier filter. Try clicking on the x to delete either of the filters:
https://codesandbox.io/s/muidatatables-change-data-after-onfilterchange-x33ok

new failing test\MUIDataTable.test.js
  it('should not update internal column state on data props change after initial columns options filterList', () => {
    const initColumns = cloneDeep(columns);
    initColumns[0].options.filterList = ['Joe James'];
    const mountShallowWrapper = mount(shallow(<MUIDataTable columns={initColumns} data={data} />).get(0));
    const instance = mountShallowWrapper.instance();
    // now disable Joe James filter
    instance.filterUpdate(0, 'Joe James', 'Name', 'dropdown');
    mountShallowWrapper.update();
    mountShallowWrapper.setProps({ data: [] });
    mountShallowWrapper.update();
    // mimic componentDidUpdate(prevProps) {
    // if (this.props.data !== prevProps.data || this.props.columns !== prevProps.columns) {
    // instance.setTableData(mountShallowWrapper.props(), 1 /* instance.TABLE_LOAD.INITIAL */);

    const updatedState = mountShallowWrapper.state();
    const { columns: updatedColumns } = updatedState;
    // make sure we still no longer have an active filter
    assert.deepEqual(updatedState.filterList, [[], [], [], [], []]);
  });

Your Environment

Tech
Version

Material-UI

MUI-datatables
2.3.0

React

browser

etc

The problem resides on the App rerender when u change the data, the filter value that was set in the const columns will be constant, so u need to control the filters from the table wrapper component, that is, receive the filterList and setState them spreading for your columns.
Today even if you make this changes the filters will not work, maybe the PR #687 could solve the problem.
The code look like this:
import React from "react";
import ReactDOM from "react-dom";
import MUIDataTable from "mui-datatables";

class App extends React.Component {
  state = {
    data: [],
    filterList: [[], ["Franky Miles"], [], [], []]
  };

  render() {
    const { data, filterList } = this.state;

    const columns = [
      {
        name: "Name",
        options: {
          filter: true,
          filterList: filterList[0].length ? filterList[0] : null,
          customFilterListRender: v => `Name: ${v}`,
          filterOptions: ["a", "b", "c", "Business Analyst"]
        }
      },
      {
        name: "Title",
        options: {
          filterList: filterList[1].length ? filterList[1] : null,
          filter: true,
          customFilterListRender: v => `Title: ${v}`,
          filterType: "textField" // set filterType's at the column level
        }
      },
      {
        name: "Location",
        options: {
          filterList: filterList[2].length ? filterList[2] : null,
          filter: false
        }
      },
      {
        name: "Age",
        options: {
          filterList: filterList[3].length ? filterList[3] : null,
          filter: true,
          customFilterListRender: v => `Age: ${v}`
        }
      },
      {
        name: "Salary",
        options: {
          filterList: filterList[4].length ? filterList[4] : null,
          filter: true,
          customFilterListRender: v => `Salary: ${v}`,
          sort: false
        }
      }
    ];

    const options = {
      filterType: "dropdown",
      responsive: "scroll",
      onTableChange: console.log,
      onFilterChange: (columnChanged, filterList) => {
        console.log(filterList);
        const data = [];
        this.setState({ data, filterList });
      }
    };
    console.log(filterList);

    return (
      <MUIDataTable
        title={"ACME Employee list"}
        data={data}
        columns={columns}
        options={options}
      />
    );
  }
}

ReactDOM.render(<App />, document.getElementById("root"));

@gabrielliwerant superseded by fix for https://github.com/gregnb/mui-datatables/pull/711
The only caveat is that the client must keep track of filterList changes and propagate them back down through column props in order to not lose UI based filter state changes.


Wrong exception thrown while setting method return

Laravel Version
10.7.1
PHP Version
8.2
Database Driver & Version
No response
Description
While trying to override Controller return type to View wrongly, site return wrong hint.
Inside Controller I've used by mistake a:
use Illuminate\Support\Facades\View;
instead of:
use Illuminate\Contracts\View\View;
Then inside index method I've wanted to override the return type (by default it's blank) to:
public function index(UserService $userService) : View
{
    return view('user.index')->with('users', $userService->getAllUsers());
}

Inside View I've achieved Error message:

App\Http\Controllers\UserController::show(): Return value must be of type Illuminate\Support\Facades\View, Illuminate\View\View returned

Steps To Reproduce
Inside Controller instead of use Illuminate\Contracts\View\View; use use Illuminate\Support\Facades\View; then try to set type of method return to View and try to use browser.

I'm not sure what you mean. You've required the return type to be a view facade and you're not returning that so this error message seems correct.

I'm not sure what you mean. You've required the return type to be a view facade and you're not returning that so this error message seems correct.

I thought that in this case where is

[...] Illuminate\View\View returned

part with [...]\Contracts\View[...] is missing.
If I'm wrong, please close.


Add getPath method to MaterializedPathRepository

Perhaps related: #1225

Hi, would you care to add a test to ensure stability?

@l3pp4rd Test added and refactored.

great, thanks ;)


Fixes issue #25011

Fixes issue #25011
Hey, I just made a Pull Request!
Removed the MemoryRouter and added a decorator with the WrapInTest app to provide proper routing context
Detailed info can be found in PR #25237 which I closed due to DCO issues
The Members Card List, both aggregate and default are visible now
Thanks  @camilaibs  @vinzscam  @piatkiewicz for help
Tagging a few maintainers for review
@Rugvip  @mtlewis  @benjdlambert

Please let me know if anything else is needed to be done, cheers!
Refrence images added.

@Rugvip , I have removed the in-code comment lines from the code lines, it should be good to go now.
Let me know if anything is to be done, thanks once again for the feedback.
Cheers!

@Rugvip, it would be great if you could review it soon, would love to get my first PR for backstage joined soon :D

@Rugvip, any updates on reviewing this PR?

Sorry for the delay in replying, I'm just back from summer vacation 🙂 . The changes looks great to me, just left a comment on the dependencies list.

Hi @camilaibs, no issues vacations are important!!
For the comment: I have not added them explicitly, maybe they came with the npm package update, do they have any negative impact? Please let me know if I need to change something.

Sorry for the delay in replying, I'm just back from summer vacation 🙂 . The changes looks great to me, just left a comment on the dependencies list.

Hi @camilaibs, no issues vacations are important! :)
For the comment: I have not added them explicitly, maybe they came with the npm package update, do they have any negative impact? Please let me know if I need to change something.

I don't think so, but I'll double-check with @Rugvip 🙌🏻

@Rugvip , @camilaibs , if we need to avoid any changes to package.json, let me rollback the changes made in the package.json (or make the dependencies exactly same as currently in the main)
and then fix the issue.
would it be okay?

Hi @Rugvip  and @camilaibs, I synced my fork with the current main and then checked the package.json.
Seems all the dependencies, and scripts are the same or have similar version updates as the current main package.json, so it checks out.
It all looks good to me. Please let me know if anything else is to be done.

Hi @Rugvip and @camilaibs, I synced my fork with the current main and then checked the package.json.
Seems all the dependencies, and scripts are the same or have similar version updates as the current main package.json, so it checks out.
It all looks good to me. Please let me know if anything else is to be done.

Hi @Arup-Chauhan could please try to remove this line, run yarn install again and see if it removes the dependencies changes?

Hi @Rugvip and @camilaibs, I synced my fork with the current main and then checked the package.json.
Seems all the dependencies, and scripts are the same or have similar version updates as the current main package.json, so it checks out.
It all looks good to me. Please let me know if anything else is to be done.

Hi @Arup-Chauhan could please try to remove this line, run yarn install again and see if it removes the dependencies changes?

Hi @camilaibs I removed the react-router-dom line and then did the yarn install in root of backstage repo fork
The project worked fine, can you see if any more changes are to be made?

Still a couple of yarn installation changes in there that aren't really related to this PR. I'll merge though but in case there are any issues with those bumps we might need to revert the story changes too.

Sure, please let me know if any other changes in the future need to be made.
Although the yarn.lock got updated after yarn.install so I am pretty sure it not cause any issues.
Thanks for all the help @camilaibs
Thanks for merging my PR @Rugvip