Changed topic and added ASCII art

Changed subject to your story. You are free to ask me to do any change you like before approving!

Hi professor, could you change one character of the ASCII art?, it's up to you which one.

Hi professor, could you change one character of the ASCII art?, it's up to you which one.

Sure I can do, but why did you merge the request if you do not approve? Usually one needs to wait until the pull-requester makes the changes before merging.
Let's see what happens if I make the changes on this same branch, but eventually, I will have to submit a new pull request.

Yes, as I thought, once the pull request is merged work cannot continue on the same pull request. I will submit another pull request.
However, since you performed the merge, I consider this part of the homework done. I'll close this part of the homework, but if there is something else you're curious to try and I am available I'll be happy to test.


Fix code style in prime-factors

See #399
Only needed to update example.js, no errors were reported in prime-factors.spec.js

Very well done!! 9 ESLint error less, awesome!
Many thanks for this great work.


PoissonClusterProcess

This PR starts the implementation of a general PoissonClusterProcess, it is still work in progress. We only need to define the process for the parents, process for offsprings and a function that created the offspring domain for each parent. The use case is as follows:
CP = PoissonClusterProcess(
    PoissonProcess(10),
    PoissonProcess(500),
    parent -> Ball(parent, 0.1)
)
D = Box((0,0), (5,5))
ps = rand(CP, D)

It already works, but there is the need to better work with PointSets. In particular we need:

an easy way to make unions of PointSets,
a way to define empty PointSets such as unions with empty PointSets are also allowed.

The lines on
https://github.com/ErickChacon/PointPatterns.jl/blob/7c06f8524771a78c7e080ac2463ed1359630a5b1/src/processes/clustered.jl#L26-L28
could be simplified and could be more robust. Right now it is going to fail when no offsprings are generated for at least one parent which are likely to happen due to the number of parents generated.
Once we agree on a approach to work with unions of PointSets and empty PointSets, I can continue improving and tidying up this PR.

Codecov Report

Merging #36 (7c06f85) into master (90019b2) will decrease coverage by 7.02%.
The diff coverage is 0.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##           master      #36      +/-   ##
==========================================
- Coverage   77.14%   70.12%   -7.02%
==========================================
  Files           5        6       +1
  Lines          70       77       +7
==========================================
  Hits           54       54
- Misses         16       23       +7

Impacted Files
Coverage Δ

src/PointPatterns.jl
100.00% <ø> (ø)

src/processes.jl
86.66% <ø> (ø)

src/processes/clustered.jl
0.00% <0.00%> (ø)

Now we need tests to approve and merge. This implementation is already more general than the R equivalent given that we can combine all sorts of processes and subdomains at each parent point 100

There are still come modifications to do with respect to border issues and offspring intensity that depends on parent location.

@juliohm, I am generalizing our definition to be able to capture more type of cluster point processes. Below are some examples of what we can do with this approach.
In this case the offspring comes from a BinomialProcess, but it can be any custom function to generate the offsprins. For example, the offsprings could be obtained using regular sampling, weighted sampling, so on.

In this case, the offsrprings come from an inhomogeneous process, but the intensity depends also of the position of the parent.

This other example is using a piecewise intensity for the offsprings with a CartesianGrid as a domain around the parent.

All these processes only requires few lines to use. It is very nice!

Before adding test and improving documentation, there are two things to complete:

[ ] Taking into account border effects. It is obvious on boxes.
[ ] Fix the combined offsprings. In order to test other features I changed to PointSet{2,Float64}(points) because our current approach sometimes creates a Vector{Any} for which PoinSet cannot be applied directly.

@ErickChacon I will go ahead and merge this in order to refactor the code a bit more. We can add tests and the docstring in a separate PR.


Unable to connect to electrum-vtc

Hi,
I am unable to connect to electrum vtc even though  i have did unselected ssl,server and tried to load each avilable server manually.

I am having the same issue.  I have already updated my firewall settings to allow permission for electrum

Is this still an issue for you? There are at least three servers up and available via SSL at present.

Duplicate of #52


Negative dates in CF and cftime

It has been suggested that my issue may be of interest/discussed/resolved through this group. I’ll present the questions pre-emptively as it may help understand the description of my problem:
Are CF dates constrained as being positive years?
Are code updates planned/required to allow for the use of the ISO/DIS 8601-2 standard to allow for negative dates?
We have NetCDF data files (with SeaDataNet and CF conventions) with a date channel as http://vocab.nerc.ac.uk/collection/P01/current/CJDY1101/
double TIME(INSTANCE) ;
TIME:long_name = "Chronological Julian Date" ;
TIME:sdn_parameter_urn = "SDN:P01::CJDY1101" ;
TIME:sdn_parameter_name = "Julian Date (chronological)" ;
TIME:sdn_uom_urn = "SDN:P06::UTAA" ;
TIME:sdn_uom_name = "Days" ;
TIME:units = "days since -4713-01-01T00:00:00Z" ;
TIME:standard_name = "time" ;
TIME:axis = "T" ;
TIME:ancillary_variables = "TIME_SEADATANET_QC" ;
TIME:calendar = "julian" ;
TIME:_FillValue = -99999. ;
byte TIME_SEADATANET_QC(INSTANCE) ;
….
Running the data file through the CFchecker software (http://pumatest.nerc.ac.uk/cgi-bin/cf-checker.pl) fails with
File "netcdftime/_netcdftime.pyx", line 715, in netcdftime._netcdftime.utime.init (netcdftime/_netcdftime.c:11201)
ValueError: negative reference year in time units, must be >= 1
This was reported to the CFchecker software, with the response from the developer that
cfunits is throwing the error
"netCDF4-python throws an error if real world calendars have negative years (https://github.com/Unidata/cftime/blob/master/cftime/_cftime.pyx#L140-L147)"
The following trail seems to imply that we are working correctly with the date, in particular having a negative year for the time origin:
http://cfconventions.org/Conformance/conformance.html
https://www.unidata.ucar.edu/software/netcdf/docs/BestPractices.html#bp_Calendar-Date-Time
refers to the udunits using ISO8601
https://en.wikipedia.org/wiki/ISO_8601
refers to
To represent years before 0000 or after 9999, the standard also permits the expansion of the year representation but only by prior agreement between the sender and the receiver.
https://www.iso.org/news/2017/02/Ref2164.html
refers to simply adding a minus sign.
https://www.unidata.ucar.edu/software/thredds/current/netcdf-java/CDM/CalendarDateTime.html refers to a minus date.
I hope this rather long description makes some sort of sense.
Ray

In principle, we should support this.  Unfortunately, the Meeus algorithm that we currently use to do date arithmetic does not work for negative Julian days.  Fixing this would require upgrading the algorithm.  Can anyone has suggest a better way to do these calculations ?

I've reworked the calendar calculations in the calcalcs branch - this branch should work with negative reference years (although year 0 is not allowed).

That’s great, txs Jeff
Ray
From: Jeff Whitaker<EMAIL_ADDRESS>Sent: 19 October 2018 20:36
To: Unidata/cftime<EMAIL_ADDRESS>Cc: Cramer, Raymond N<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Unidata/cftime] Negative dates in CF and cftime (#71)
I've reworked the calendar calculations in the calcalcs branch - this branch should work with negative reference years (although year 0 is not allowed).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Unidata/cftime/issues/71#issuecomment-431475306, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AqHI-OtKJHrvgeT4ih3O0nYvSTWvqm41ks5umimpgaJpZM4Xb5q3.

This message (and any attachments) is for the recipient only. NERC is subject to the Freedom of Information Act 2000 and the contents of this email and any reply you make may be disclosed by NERC unless it is exempt from release under the Act. Any material supplied to NERC may be stored in an electronic records management system.

this has been merged into master - please let us know how it works.  I hope to make a new release (1.0.2) with this included in the next week or two.


Instructions doesn't match the test

https://github.com/exercism/purescript/blob/bd3c772ec6da6f2d1d018ce36c337ced984102ad/exercises/practice/bob/test/Main.purs#L42
Instruction says:
"""
He answers 'Calm down, I know what I'm doing!' if you yell a question at him.
"""
In the test, the assert was incorrect. It should be:
test "forceful questions" do
      Assert.equal "Calm down, I know what I'm doing!"

@ErikSchierboom : This issue has been solved by #219 and may now be closed. Thanks!

Thanks


Is this still maintained/supported?

Love the idea of this project.
I see that this GitHub page says it's currently failing.
But is this still maintained?
If not, do you have suggestions for other projects with the same philosophy?

Hi! Sorry for the delay.
I'm planning on rewriting it if you're still interested.
Thanks for using it.


Formset in the step

Hello,
Does it anyway to create a formset in the step of Wizard?

it does my man


Responsive

I want work on responsiveness of the project

Hi @Ammarbashirharuna sure you can start working.

okay i will


How to enable amx?

Hi,
I am trying to compile a gemm code with amx instructions. I used the most recent clang version which is supposed to support amx.
I set LIBXSMM_TARGET as spr, but the sample code in the repo still generates avx512 codes.
If you can provide a simple gemm code which will be translated into amx instructions, it would be really helpful to begin with.
Thanks in advance.

Can you specify what you mean with sample code?
All deep learning primitives with BF16 will use AMX if the sizes fit and the sample/xgemm/kernel.c also uses AMX when the sizes fit.

Thank you for the quick reply.
I tried sample/smm/, sample/hello/. I also tried to use /bin/libxsmm_gemm_generator to get amx instructions, but they only generated avx 512. According to your answer, maybe it's due to the data type or size doesn't fit. I just want to compile simple gemm code with amx to see how it will look like in the real binary file.
If I can just directly run xgemm/kernel to generate codes with amx instructions, could you give me the right arguments that I need to pass to kernel (should be related to the sizes that fit, but I'm not sure what they should be)?

we don't support static code generation for AMX, all it just JIT, unless you use sde the code will not run.
./kernel 32 32 32 32 32 32 1 1 0 0 0 0 nopf BF16 nobr 1 1 1
would use AMX

Thank you for providing an example. So it will not generate amx instructions even though I manually change all 19 arguments into the constant in kernel.c and objdump the binary file?

don't know what you mean. What I shared generates AMX when target is SPR.

Hmm.. I was asking since I coudn't see any amx insts after running objdump, but I could see many instructions marked as (bad). Maybe the clang that I'm using is the problem. Could you share which compiler version did you use for amx?

again, the compiler is irrelevant, the code is JIT'ed for AMX when kernel is running. Therefore, of course when objdumping the "kernel" there is not a single AMX instruction.

I see, I may be misunderstanding the concept of jit compilation. Thank you for the clarification. As you mentioned, there is no way to get amx instructions from libxsmm as of now since it doesn't support static code gen, correct?

It seems you want to inspect the code that would be generated on a capable target?
You can do the following:
export LIBXSMM_TARGET=spr
export LIBXSMM_VERBOSE=-1
[ run some example code like Alex mentioned ]
objdump -D -b binary -m i386 -M x86-64 [JIT-dump-file]

I think objdump belongs to GNU Binutils. I doubt it can decode AMX instructions (at least as far as v2.34 goes).

Please note, the above mentioned flow of commands may only produce a single dumpfile corresponding to the first kernel requested by the sample code. This is because the sample code may attempt to run the kernel after requesting it, if so you need an AMX capable system (or SDE).

and LIBXSMM moves to JIT only for no feature. So we have no plan to add static code gen for AMX. But LIBXSMM has AMX suppoer, just through JIT though.

Feel free to open an issue in any case.

Thank you for the response. In summary, objdumping the binary file itself will not give the amx instructions while objdumping jit-dump-file (which should be generated when I use JITDUMP=1) may generate amx instructions (If I'm wrong, please correct me). I will try to use the most recent objdump (both from llvm and gnu) and see whether they supports.

gcc  -D__BLAS=0 -DNDEBUG -D__STATIC=1 -DLIBXSMM_OPENMP_SIMD -DLIBXSMM_PERF -DLIBXSMM_PERF_JITDUMP -DLIBXSMM_BUILD=2  -Iinclude -I./src  -msse4.2 -fPIC -g -Wall -O2 -fopenmp-simd -funroll-loops -fdata-sections -ffunction-sections -fvisibility=hidden -pthread -c ./src/libxsmm_perf.c -o  obj/intel64/libxsmm_perf.o ./src/libxsmm_perf.c: In function 'libxsmm_perf_init': ./src/libxsmm_perf.c:145:3: warning: implicit declaration of function 'LIBXSMM_MEMZERO127' [-Wimplicit-function-declaration]    LIBXSMM_MEMZERO127(&header);    ^ ./src/libxsmm_perf.c:151:23: warning: implicit declaration of function 'libxsmm_timer_tick' [-Wimplicit-function-declaration]    header.timestamp  = libxsmm_timer_tick();                        ^ ./src/libxsmm_perf.c: In function 'libxsmm_perf_dump_code': ./src/libxsmm_perf.c:260:8: error: 'struct jitdump_record_code_load' has no member named 'internal_perf_codeidx'      rec.internal_perf_codeidx = internal_perf_codeidx++;
I got the above error while I compile the library.. make JITDUMP=1 BLAS=0 OMP=0
Both from clang and gcc. Could you take a look at?

Will do, thank you for the report!

This is (hopefully) fixed and better tested now (LIBXSMM/master). The log reads like "Test at least compilation of Linux-perf facility. Updated Linux-perf facility for proper compilation. Please note: we have not received maintenance for Linux perf facility since years, and we maintain (and support) profiling JIT-code using Intel VTune Amplifier (https://libxsmm.readthedocs.io/libxsmm_prof/)."

I overlooked some of your previous comments.

jit-dump-file (which should be generated when I use JITDUMP=1)  [...] If I'm wrong, please correct me

The facility enabled by JITDUMP=1 (at compile-time) enables our support for "Linux Perf" (performance profiler). Dumping our JIT-code is way easier (no special build flags needed); see the earlier comment (specifically, LIBXSMM_VERBOSE=-1 is an environment variable/value which triggers the JIT-dump).

I will try to use the most recent objdump (both from llvm and gnu) and see whether they supports.

Perhaps have a look at GNU Bintools (which is separate from GNU GCC version).

Thanks for clarifying many points! I will try what you've suggested.
In the mean time, I have a quick question. Do you know whether it is possible to run PIN with jit-code? In other words, the binary file xgemm/kernel can be directly used by PIN? I am curious since you've mentioned at some point to use Intel SDE, and it seems like it uses PIN internally.

Do you know whether it is possible to run PIN with jit-code?

Yes, it is!  Please note, Pin generally does not depend on files in order to instrument code.

In other words, the binary file xgemm/kernel can be directly used by PIN?

Pin performs code transformation and instrumentation in-memory (always), and naturally supports JITted code.

I am curious since you've mentioned at some point to use Intel SDE, and it seems like it uses PIN internally.

Yes, Pin is internally used by Intel SDE. SDE replaces new instructions that would require certain CPU features (not available on actual execution target). In particular, SDE is used to test such code prior to hardware available.

Thank you for the answer again!
I was able to get amx instructions generated from libxsmm by looking at SDE traces.
I want to compare the same gemm program under other old architectures like snb/hsw/skx, but it seems like I can only use skx. Others failed to finish jit (says JIT failed, please run with LIBXSMM_VERBOSE=-1 and/or with debug mode LIBXSMM library!).
I've used the following command as you suggested.
./kernel 32 32 32 32 32 32 1 1 0 0 0 0 nopf BF16 nobr 1 1 1
I guess the reason is that I need to use BF16 to exploit amx instructions while the architectures before skx do not support BF16. Am I guessing correct or is there any other way to compare different architectures?

but it seems like I can only use skx

Bf16 is available by an AVX-512 domain and with upcoming Intel AMX. The AVX-512 also remains useful even with AMX for instance when performing type-conversions and quantization/rounding (copy-in/out). Bf16 support is present in "Cooperlake" (CPX), which is a recently released 4-socket platform. Please also note, VNNI is available since "Cascadelake" (CLX) and evolved out of KNM. Intel AMX resembles the important type-combinations (input+accumulator) as present with VNNI and AVX512/Bf16, i.e., int8-input and int32-accumulator for quantized data (common order of magnitude)), and Bf16-input with FP32-accumulator (individual magnitude by FP-element).
Rely on LIBXSMM_TARGET environment variable and try at least the following values: clx (VNNI), cpx (AVX512/Bf16), and spr (AMX). Regarding quantized integers (VNNI), you may have a look at question #408.

@hfp Thanks to your help, I was able to play with gemm with amx instructions.
Can I ask you whether convolution operations in libxsmm also support amx instructions? If so, could you provide an example of something like this for convolution?
./kernel 32 32 32 32 32 32 1 1 0 0 0 0 nopf BF16 nobr 1 1 1

@ghjeong12 LIBXSMM started with direct convolution kernels, i.e., specialized convolution kernels. However, our research and recent work transitioned LIBXSMM to "Deep Learning via a Single Building Block" (see the 1st reference for more details). This means convolutions are performed using a universal batch-reduce kernel which in turn is a small matrix multiplication (C += A * B). Since you already checked GEMM with AMX, you are very close (just replace nobr to get even closer).

Thank you for the response. I thought since im2col is expensive, directly supporting convolution kernels would be more efficient. I will take a look at the reference you suggested. Could you also explain what nobr stands for?

I think im2col is a "standard methodology" and our work is not about im2col (otherwise I would not call it "research").

@ghjeong12 The nobr (your command line was ./kernel 32 32 32 32 32 32 1 1 0 0 0 0 nopf BF16 nobr 1 1 1) stands for "no batch-reduce". What you want is batch-reduce, and there are several flavors (batches of SMMs can be specified with an array of pointers to matrices, indexes, etc.).

Very high level: integrating LIBXSMM´s convolutions (BR/batch-reduce) comes down to writing loop-nests related to the preferred format of your tensors, and then using BR inside of the loop-nest. We found that typical frameworks want to control the loop nest anyway and then relying on an highly optimized inner-most kernel comes in very handy. All the nasty corner/special cases with direct convolutions are gone for our kernel and also the loop nest becomes more focused (as it mostly deals with NHCW etc. permutations).


Phy pads

New pads and offsets for the PHY guys.

We'll merge this once full_chip passes LVS and we have the new dragonphy RDL for this.

Sounds good. For the record I want to include the full plan here, in the pull conversation thread. Plan is

wait for PHY guys to give us their new RDL/GDS
incorporate that in garnet branch "bumps" and get it working
finalize this merge and the "bumps" merge (https://github.com/StanfordAHA/garnet/pull/716) at the same time


Poll: what test runner + script language do you use?

We'd like to know more about how people are using WinAppDriver to help us prioritize work.
To help please do one of:

If your IDE + runner + language isn't already mentioned on this issue please add a comment with it
If your IDE + runner + language is mentioned, please upvote that comment

Thank you!

VS Test/MS Test + C#

VS 2017 Pro + xUnit.net + C#

VS2017 Ent + C# + Nunit + Specflow

From: Alex Li<EMAIL_ADDRESS>Sent: Wednesday, June 14, 2017 10:20:07 AM
To: Microsoft/WinAppDriver
Cc: Subscribed
Subject: Re: [Microsoft/WinAppDriver] Poll: what test runner + script language do you use? (#205)
VS 2017 Pro + xUnit.net + C#
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/WinAppDriver/issues/205#issuecomment-308374474, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ADQA12uXjrIvIfuHtK5Caqo4A8VCqdXJks5sD6XHgaJpZM4N5RYo.

Node.js + Mocha

IntelliJ IDEA Java Studio + Java8(Lombok) + Maven + Gauge for test client during development.
TeamCity + console Maven step + Gauge or Junit for test client on virtual machine.
VS2015 Pro, Xamarin  C#,  xUnit for game
We also test Android, iOS app with appium by the same java test (have some platform specific selector)

eclipse + jUnit + Java
Used with Cucumber-JVM

VS IDE + C#
Regards
Mahendra
On Friday, June 30, 2017, 12:04:52 AM GMT+5:30, ReaperMantis<EMAIL_ADDRESS>wrote:
eclipse + jUnit + Java
Used with Cucumber-JVM
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks everyone, this is very helpful!

Visual Studio Code + NodeJS + Mocha and WebDriver.IO or WD.JS

NetBeans + TestNg + Java

VS Code + Python

RubyMine + Cucumber + Ruby (WinAppDriver call via Appium)

VS Code + Cucumber + Ruby (Once I figure out ruby API for WinAppDriver)

IntelliJ idea with java Cucumber...more productive way to achieve automation!

cucumber + Ruby + Appium

Eclipse + TestNg + Java

VS & VS Code + C# + NUnit


unable to creater react app

hai
i am tryinr to create a react app from visual code studio.
by using the command  npx Create-react-app hello-world also i coulnt create the react app
so pleasae try to fix this

Yeah I'm getting the same issue too

Try using lowercase for create-react-app,
npx create-react-app hello-world

That's not the issue... I do that every time, and the issue still happens

I'm still experiencing the same issue guys. Tried using lowercase and everything but still doesn't seem to work.

Okay, so I was experiencing the same issue until a while ago. Then fixed it by first installing it through npm i create-react-app which should install create-react-app in persistence mode and then run your code 'npx create-react-app hello-world'


More SVG options

I'd like to have a good solution for SVG icons without much configuration but SVGs are a bit tricky.
There are a couple of places we could use SVGs and we probably want them to work a bit differently.

Use in url()s in SCSS

We'd probably want file-loader here. So that the url() ends up pointing to the right file in the production build

Usage in our React components

I'm thinking of using the svg-sprite-loader with a special component that will create a sprite sheet of the svgs (example below)

import React from 'react'
import classnames from 'classnames'

const Svg = ({filename, className, ...props}) => (
  <svg
    {...props}
    className={classnames('Svg-Icon', className)}
    dangerouslySetInnerHTML={{
      __html: `<use xlink:href="${require('!!svg-sprite!svgo!assets/${filename}.svg')}"></use>`
    }}
  />
)

export default Svg

// Usage

<Svg filename="monogram" />

(the !! in the require call disable all loaders established in the webpack config to allow bypassing the file-loader that's probably be turned on for all svgs by default.)
Now that I'm writing this out, the svg-sprite-loader and associated component could be their own module and people could install it if they needed it. The question then is how to get a separate file in production.
Very open to ways to do this. I'd really really really like to avoid adding an additional step outside of the webpack config.
@trunkclub/ui

In exploring these options I'd like to keep an eye towards server compatibility.
is there a way for loaders to be used and still be ok on the server?

@kellyrmilligan Yes, using webpack to create the server build.

That has been a non starter in the past, so I would rather not depend on that being the answer.

I'm not opposed to webpack-for-the-server-build. I think we did it wrong
with CMApp (particularly, working it around a messy and non server friendly
flux framework) and there's likely been a lot more momentum on different
ways to attack the problems we had. Not saying it's the cleanest answer,
but it could be an answer 😅
On Mon, Nov 7, 2016 at 8:05 PM Kelly<EMAIL_ADDRESS>wrote:

That has been a non starter in the past, so I would rather not depend on
that being the answer.
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
https://github.com/trunkclub/create-react-app/pull/30#issuecomment-259024129,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AApPlBJrQS-d92GuYIY25Z-ZXwCRG6PJks5q79jsgaJpZM4Kr8c7
.

 I think we did it wrong
with CMApp (particularly, working it around a messy and non server friendly
flux framework) and there's likely been a lot more momentum on different
ways to attack the problems we had. Not saying it's the cleanest answer,
but it could be an answer 😅
On Mon, Nov 7, 2016 at 8:05 PM Kelly<EMAIL_ADDRESS>wrote:
That has been a non starter in the past, so I would rather not depend on
that being the answer.
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
https://github.com/trunkclub/create-react-app/pull/30#issuecomment-259024129,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AApPlBJrQS-d92GuYIY25Z-ZXwCRG6PJks5q79jsgaJpZM4Kr8c7
.

@jblock we can explore it again, and I don't want to use cm app as our only example. I tried it, dan tried it, and both times we ran into issues. I have found its best to let node be node and webpack be webpack.

@kellyrmilligan @jblock If you don't mind, I'd rather we discuss how we should handle SVG loading and save the server side rendering for another time. I don't think that we should avoid using webpack loaders for the sake of potential server-side support. My goal is to have all of the features that<EMAIL_ADDRESS>had and server-side rendering support wasn't one of them. That being said, I do think that if we do server-side rendering, running both client and server builds through webpack will have the lowest barrier to entry and thus get the most support and then adoption.
As far as SVGs go, the https://github.com/kisenka/svg-sprite-loader is working rather nicely for using SVGs from react components (using the reference component I included in my initial post) but currently has issues when being used with the ExtractTextPlugin.
Ideally we'd want the spritesheet to be a separate file in production to reduce the size of our initial JS bundle (although we can get similar perf using code-splitting).
Another option would be to use something like the raw-loader to pull in the SVG source itself and use dangerourlySetInnerHTML to inject the entire svg source into the page.
I'd really like to get the svg-sprite-loader working and I'm happy to take a look at https://github.com/kisenka/svg-sprite-loader/issues/66.
What are your thoughts on these options? Do you have other ideas?

👍 Good point--we'll just want to make sure that we're not explicitly designing against SSR as a pattern, but I have very high confidence that most webpack-loader strategies won't do that (so long as the assets can be extracted out during the build, and more desirably, we can intelligently include those extracted assets without userland configuration).
I like the semantics of the svg-sprite-loader (and subsequently, think that the remaining issue is with the ExtractTextPlugin is probably pretty straightforward to fix)--my main concern is with having inline loader syntax. Do you think it's fair to have this build pipeline enforce a naming scheme for these icons as to prescribe their path through this loader? *-sprite.svg or something?
My other major concern is having the SVG (or any asset references, for that matter) be analyzable during build-time--e.g, if I create an Icon component with a filename="krull", then I'd expect that Webpack throws an error that it can't find the file with the name of "krull" and output that to the console. Does this do that?

@jblock 🤔  An enforced naming scheme would also enforce where things could be used. If you're using an svg in your CSS, you'd have to duplicate it with another name to use it in your JS somewhere else. Still an option though.
We can get build time analysis of svg imports if we don't use expressions from the require statements. We can do that by moving the require out of the <Svg /> component and using it when passing in props (in most cases) but then we either have to enforce naming or have a bunch of requires with loader syntax. I'm cool with loader syntax in one place and in module code, but not thrilled about telling people to use it. I don't want people to have to know what webpack is doing and I think that breaks that rule.

If you don't mind, I'd rather we discuss how we should handle SVG loading and save the server side rendering for another time. I don't think that we should avoid using webpack loaders for the sake of potential server-side support. My goal is to have all of the features that<EMAIL_ADDRESS>had and server-side rendering support wasn't one of them.

@zperrault I think you hit the nail on the head. 4.0 has no concept of this, and for the time being neither should 5.0 if it's goal is feature parity.  I'm bringing out the consensus card on this one. This should be discussed at the summit with the group, and until then we favor the status quo, which at the moment is up to the the team that is responsible for the particular app.
As for server side rendering being potential, it is not. Until the business tells us we do not need cm_app to be searchable by google, server rendering is a real thing for us to contend with. We know that if we use regular javascript and do not have loader syntax that it will work. We do not know enough at this time if using webpack to build the server bundle will work fully with combinations of  loaders, etc. By that measure alone, we should not have loader syntax in files.
so what I propose is to drop this issue entirely for now until we get more apps on this system, and can reach consensus on if we need a built in approach for icons.

@kellyrmilligan

4.0 has no concept of this, and for the time being neither should 5.0 if it's goal is feature parity.

This is untrue<EMAIL_ADDRESS>uses file-loader to load SVGs. I'll keep it that way and bring this up at the next UI summit.

@zperrault good point, forgot the file loader was in there. sounds good.


PHP sdk sets 'predefinedAcl' to 'private' by default.

PHP sdk sets 'predefinedAcl' to 'private' by default for GCS objects.
It's confusing and inconsistent with gsutil, Google Cloud Console and with API documentation that lists it as an optional parameter:
https://cloud.google.com/storage/docs/json_api/v1/objects/insert
Google Cloud Console and gsutil omit this parameter and objects get assigned default object permissions set for the bucket (gsutil defacl get gs://<your_bucket_name>), which is what developers expect it to be.

Closed by https://github.com/GoogleCloudPlatform/google-cloud-php/pull/313
Thanks again @amoiseiev!


[Expected Downtime] Emergency reboot

Completed

@jaiden-04 you forgot to lock the issue

I am now on the status page :D


Where is the SQL Scripts

At present it seems that all schemas will be dynamically created at runtime.
In a controlled production and test environment, this is not possible.
Do you have an artefact (even with only the default values), which covers the create table commands for an Oracle environment for a Saga Store and Event Source Store?

Currently, besides copying from others:wink:, the recommended approach is to have JPA generate the tables for you on a dev environment, tweak the table structure to the desired aspects en generate a SQL script for more formal environments.
The reason is that each database implementation has its own specifics for storing blob data. We decided that we'd rather not have any scripts than scripts that are suboptimal for each environment.


Add type inference to Options API provide / inject or add docs for not supporting it

Version
3.0.5
Reproduction link
https://github.com/l0rn/inject-provide-types/tree/options-api
Steps to reproduce
Use the Provide/Inject mechanism using the Options API and Typescript.
Injected properties won't be inferred and will throw type errors complaining the property is not defined on the component.
On the main branch of the same repository you will find the same being achieved using composition API, which works fine.
As far as I understand only using Typescript should not be a reason to use the Composition API I think it would be a cool effort trying to add typing support to inject using the Options API. If that's not feasible I think a warning in the documentation would be appropriate.
What is expected?
Best case scenario:

Use provide / inject in options API, all types are properly inferred
If any additional type declaration is needed, a paragraph on inject / provide in the typescript section of the docs is provided

What is actually happening?
Using provide / inject in my typescript code, wondering why the injected property is not available in typescript:
ERROR in src/components/Marker.vue:23:19
TS2339: Property 'map' does not exist on type 'ComponentPublicInstance<Readonly<{ location: LocationDto; } & {}>, {}, {}, {}, {}, Record<string, any>, Readonly<{ location: LocationDto; } & {}>, {}, false, ComponentOptionsBase<...>>'.
    21 |     marker
    22 |       .setLngLat([this.location.lng, this.location.lat])
  > 23 |       .addTo(this.map.value)
       |                   ^^^
    24 |
    25 |   }
    26 | })

Would have been helpful to keep the repro online, but it seems you delete the branch demonstrating your issue. :/

Would have been helpful to keep the repro online, but it seems you delete the branch demonstrating your issue. :/

Hm, i just double checked. I clicked the link in a non-logged in private window and it still shows correctly :thinking:

Hm, i just double checked. I clicked the link in a non-logged in private window and it still shows correctly :thinking:

I think this is a request to get the type when using inject with Options API
defineComponent({
 inject: [ 'myVar'],
 mounted(){
   this.myVar // doesn't exists
 }
})

Ideally we would also be able to get the typing information, it would be cool to use the InjectionKey<T> for that
const myVar: InjectionKey<{a: 1}> = Symbol()

defineComponent({
 inject: [ myVar],
 mounted(){
   this.myVar // it should have type of `{a: 1}`
 }
})

I think this is a request to get the type when using inject with Options API
defineComponent({
 inject: [ 'myVar'],
 mounted(){
   this.myVar // doesn't exists
 }
})

Ideally we would also be able to get the typing information, it would be cool to use the InjectionKey<T> for that
const myVar: InjectionKey<{a: 1}> = Symbol()

defineComponent({
 inject: [ myVar],
 mounted(){
   this.myVar // it should have type of `{a: 1}`
 }
})

Yes so basically I ran into what I believe is the issue that l0rn is trying to raise here.
Given a vue-cli generated Vue 3 project, the typescript compiler will complain about the injected value not being present on the component when using TypeScript in combination with the Options API. Now, I might be missing something here but I have yet to figure out a way to tackle this.

Yes so basically I ran into what I believe is the issue that l0rn is trying to raise here.
Given a vue-cli generated Vue 3 project, the typescript compiler will complain about the injected value not being present on the component when using TypeScript in combination with the Options API. Now, I might be missing something here but I have yet to figure out a way to tackle this.

I just ran into this as well. Here's a tweet from @sstephenson showing an example type definition for a similar api in StimulusJS. It doesn't look like he was able to keep the array syntax to make this work.
I'm going to convert my component to the Composition API and see if that fixes that issue.

Im not familar with inject. If it only accepets string or symbol, best we can do is infering this.map as a unkown or any.

Yeah this would be really useful, its pretty frustrating to not be able to use inject, options API, and TypeScript together

I've since implemented this by overriding the useStore method with my own typed store and InjectionKey. See the gist below for a complete example:
https://gist.github.com/99linesofcode/bbf9fcf0b195fa3a2f0ec161df8fa41f.
Note that you don't necessarily have to override the Store type as I do here but it does add some additional feedback and payload typechecking, which I'm sure you'll like.
Be sure to import and pass the key inside your main.ts like so:
import { createApp } from 'vue';
import { store, key } from '@/store';
import { router } from './routes';
import App from './app.vue';

createApp(App)
  .use(store, key)
  ...
  .mount('#app');

I inject the store and router inside my tests like so:
import { routerKey } from 'vue-router';
import { key as storeKey } from '@/store'; // this is where the overwritten useStore function lives.

  return mount(UploadBankStatement, {
    global: {
      provide: {
        [storeKey as symbol]: mockStore,
        [routerKey as symbol]: mockRouter,
      },
    },
  });

Inside your component files you can simply call useStore.
import { useStore } from '@/store';

export default defineComponent({
  ...
  setup(props) {
    const store = useStore()
  }
  ...
});

Hope this helps someone while we wait for Vuex 5 with proper TS support.

Okay, I ran into the same issue, and ended up using the inject method, inside a setup function in my Options API component. It's goofy, but it does the trick:
<script lang="ts">
import { defineComponent, inject } from 'vue'

import type { A, B } from './things'

export default defineComponent({
  setup () {
    return {
      a: inject<A>('a'),
      b: inject<B>('b')
    }
  },

  data () {
    return {
      thingUsingInjects: this.a! + this.b! // need the `!` as typescript types injects as optionals
  }
  props: { ... },
  computed: { ... },
  methods: { ... }
}

@8bitDesigner that's the correct behaviour, for non optional you need to pass a default.
The reason is depending where you are in the tree it might be or not provided by a parent. Even though "you know" that will never happen, it wouldn't be the first time during refactoring or someone else changing the code that might place that component where it shouldn't be.

That totally makes sense, and I fully admit that I will break this the minute I refactor my code, if I haven't already.


Add missing LICENSE file & question related to repo on pub.dev

Hey,
I was looking around for Flutter/Dart projects that are tinkering with ML/AI stuff and found this repo. Keep it up!
Is this pub.dev package owned by you?: https://pub.dev/packages/tokenizerx
There's no repo linked on that page and neither the author is stated.
Did you manage to inference with an rwkv model through Dart?

I do not own that package, but it was very useful.
I was able to do inference with this project,
the file converter is over at my rwkv-cpp-accelerated project

Thanks for replying quickly.
I also just noticed you added a license https://github.com/harrisonvanderbyl/rwkv-dart/commit/80d13d8dcff3fb9f11b9134781de34df9fac8358 thus this issue is resolved 👍


Documentation $TRAEFIK_SERVICE does not match actual service

Currently the documentation lists the $TRAEFIK_SERVICE as traefik-pages@docker, but the service is created using a file and is therefore traefik-pages@file so traefik cannot find the service. Either $TRAEFIK_SERVICE should point to the file service or the docker-compose example should include tags to create the docker service.
I'm happy to submit an MR for the change, but thought you might have a preference for which solution was used.
Thanks for building this, btw. It's really handy.

Ah I see what the problem is. It's mixed up a few examples whilst I was building it.
The solution is to remove the file provider entirely, and instead set traefik.enable=true on the pages container, so it then is defined in docker. That's how I've deployed it.
I'd absolutely welcome a PR for this! :smile:

Same. I didn't even think to look at your deployment code, though. I just wasted a half an hour figuring it out on my own :facepalm:


Added avatar

A png of a dead lizard.

L:eyes:Ks like a thing.

I think we need to have @BeefKnuckleback approve though?

Does it meet all the reqs in the README and follow the templates in https://github.com/desert-planet/arrakis-hubot/tree/master/ayp-template-images/ayp-templates :question:

ALMOST! It does now, Im closing this request and creating one that meets all reqs.


TypeError: mappings.map is not a function

C:\Users\Jan\Documents\throwaway\planetscaleMigrationPreview>npx prisma generate
Environment variables loaded from .env
Prisma schema loaded from prisma\schema.prisma
Error:
TypeError: mappings.map is not a function
    at getMappings (C:\Users\Jan\Documents\throwaway\1363\node_modules\@prisma\client\generator-build\index.js:179983:21)
    at Object.externalToInternalDmmf (C:\Users\Jan\Documents\throwaway\1363\node_modules\@prisma\client\generator-build\index.js:179943:19)
    at Object.getPhotonDMMF (C:\Users\Jan\Documents\throwaway\1363\node_modules\@prisma\client\generator-build\index.js:181811:67)
    at buildClient (C:\Users\Jan\Documents\throwaway\1363\node_modules\@prisma\client\generator-build\index.js:172049:32)
    at Object.generateClient (C:\Users\Jan\Documents\throwaway\1363\node_modules\@prisma\client\generator-build\index.js:172129:43)
    at Object.onGenerate (C:\Users\Jan\Documents\throwaway\1363\node_modules\@prisma\client\generator-build\index.js:173638:33)
    at Object.<anonymous> (C:\Users\Jan\Documents\throwaway\1363\node_modules\@prisma\client\generator-build\index.js:157919:46)
    at Generator.next (<anonymous>)
    at C:\Users\Jan\Documents\throwaway\1363\node_modules\@prisma\client\generator-build\index.js:157906:71
    at new Promise (<anonymous>)

Schema:
// This is your Prisma schema file,
// learn more about it in the docs: https://pris.ly/d/prisma-schema

datasource db {
  provider          = "mysql"
  url               = env("DATABASE_URL")
  shadowDatabaseUrl = env("SHADOW")
}

generator client {
  provider = "prisma-client-js"
}

model foo {
  id  Int    @id
  bar String
}

// The following model is created manually so that the Prisma Migrations table is visible
model PrismaMigrations {
    id                  String    @id @db.VarChar(36)
    checksum            String    @db.VarChar(64)
    finished_at         DateTime?
    migration_name      String    @db.VarChar(255)
    logs                String?
    rolled_back_at      DateTime?
    started_at          DateTime  @default(now())
    applied_steps_count Int       @default(0)

    @@map("_prisma_migrations")
}

package.json (as the client is not installed yet):
{
  "name": "planetscaleMigrationPreview",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "prisma": "^2.25.0"
  }
}

Does not happen after nuking node_modules and npm install 🤷

I am also unable to reproduce this. Maybe you installed an older version of the client at first accidentally?

I would love to have a better reproduction, as this is one of those scary cases where everything just implodes. But as I do not, let's close this and see if someone pops up again via the error message.


[ENH] Multiclass classification reduction using Histograms

Reference Issues/PRs

fixes #378
What does this implement/fix? Explain your changes.

It adds an adapter to sklearn multiclass classifiers and expresses them as a Histogram probability distribution.
Does your contribution introduce a new dependency? If yes, which one?

Did you add any tests for the change?

No
PR checklist

For all contributions

[ ] I've added myself to the list of contributors with any new badges I've earned :-)
How to: add yourself to the all-contributors file in the skpro root directory (not the CONTRIBUTORS.md). Common badges: code - fixing a bug, or adding code logic. doc - writing or improving documentation or docstrings. bug - reporting or diagnosing a bug (get this plus code if you also fixed the bug in the PR).maintenance - CI, test framework, release.
See here for full badge reference
[x] The PR title starts with either [ENH], [MNT], [DOC], or [BUG]. [BUG] - bugfix, [MNT] - CI, test framework, [ENH] - adding or improving code, [DOC] - writing or improving documentation or docstrings.

For new estimators

[ ] I've added the estimator to the API reference - in docs/source/api_reference/taskname.rst, follow the pattern.
[ ] I've added one or more illustrative usage examples to the docstring, in a pydocstyle compliant Examples section.
[ ] If the estimator relies on a soft dependency, I've set the python_dependencies tag and ensured
dependency isolation, see the estimator dependencies guide.

@fkiraly , I have completed the classifier and all checks have passed. Let me know if you want any modifications.

I have made some changes to the name and the folder structure please let me know if this is suitable.

blocking: the 1D array case is not covered by tests, can be done in get_test_params or separately

Is it possible to check for 1D case in get_test_params itself? as I will not be able to modify any inputs for predict and predict_proba other than the classifier instance and number of bins.

yes, but we know that the inputs for y are numbers, so we should be able to come up with a reasonable range.
We should also think of the casewhere the user specifies bins and some y fall outside - in this case, I think the estimator should not break but do sth sensible (move to closest bin, or discard - perhaps even as an option on what to do)

yes, but we know that the inputs for y are numbers, so we should be able to come up with a reasonable range.

Sorry I didn't quite get how this would help in testing for 1D case in get_test_params.

We should also think of the casewhere the user specifies bins and some y fall outside - in this case, I think the estimator should not break but do sth sensible (move to closest bin, or discard - perhaps even as an option on what to do)

I have handled this and moved y values outside bin range to the closest bin.

Sorry I didn't quite get how this would help in testing for 1D case in get_test_params.

I meant, there should be a test case in get_test_params, where the bins passed ar an 1D array, currently there isn't one.

Sorry I didn't quite get how this would help in testing for 1D case in get_test_params.

I meant, there should be a test case in get_test_params, where the bins passed ar an 1D array, currently there isn't one.

Ahh I see. Now that the y values outside bin range are also handled it makes all the more sense to include the array case for bins. I hadn't included earlier as I did not know the range of y and that might break the code when the bins are pre-meditated.
Thanks for noticing.

Are we waiting on something for this merge ?

no, not in particular - just in case any other devs want to give it a review


Discuss roles allowed for production deployment within the team

Because of the small size of the team these days, perhaps this is not so much needed.
Perhaps a check-list of what we need to do before pushing the button is a better idea?

Write a release guide/documentation

Manual of good practices:
https://github.com/equinor/energyvision-internal/discussions/81

Looks good to me.


Issues with Security Keychain when running remotely

New Issue Checklist

[ ] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
Hello! I am getting these keychain access errors when running these jobs remotely on Circle CI. The stack overflow links in the error messages suggest that I have expired certificates, but that is not the case.
security: SecKeychainSearchCopyNext: The specified item could not be found in the keychain.

security: SecKeychainUnlock: The user name or passphrase you entered is not correct.
security: SecKeychainItemImport: User interaction is not allowed.

I have also submitted a ticket to Circle CI, but thought you guys might know what is going on.
PS - I know there are a lot of very redundant steps in my Fastfile. I have a ticket to clean that all up, I promise!
Complete output when running fastlane, including the stack trace and command used

[07:15:59]: Updated ios/piedpiper.xcodeproj/../piedpiper/Supporting/Info.plist 💾.
[07:15:59]: ---------------------
[07:15:59]: --- Step: produce ---
[07:15:59]: ---------------------
+-----------------------------------+---------------------------------+
|                     Summary for produce 2.125.2                     |
+-----------------------------------+---------------------------------+
| app_identifier                    | com.mycompany.ios-beta-13-purple |
| app_name                          | Pied Piper Purple                    |
| enable_services.push_notification | on                              |
| sku                               |<PHONE_NUMBER>                      |
| username                          |<EMAIL_ADDRESS>              |
| platform                          | ios                             |
| language                          | English                         |
| skip_itc                          | false                           |
| skip_devcenter                    | false                           |
| team_id                           | TEAMID32874                      |
| itc_team_id                       | 123456789                       |
+-----------------------------------+---------------------------------+
[07:16:02]: [DevCenter] App 'com.mycompany.ios-beta-13-purple' already exists, nothing to do on the Dev Center
[07:16:04]: App 'com.mycompany.ios-beta-13-purple' already exists<PHONE_NUMBER>), nothing to do on App Store Connect
[07:16:04]: -------------------
[07:16:04]: --- Step: match ---
[07:16:04]: -------------------
WARNING: You are running Ruby 2.3.7, which is nearing end-of-life.
The Google Cloud API clients work best on supported versions of Ruby. Consider upgrading to Ruby 2.4 or later.
See https://www.ruby-lang.org/en/downloads/branches/ for more info on the Ruby maintenance schedule.
To suppress this message, set the GOOGLE_CLOUD_SUPPRESS_RUBY_WARNINGS environment variable.
+-----------------------+------------------------------------------------------------+
|                             Summary for match 2.125.2                              |
+-----------------------+------------------------------------------------------------+
| app_identifier        | ["com.mycompany.ios-beta-13-purple"]                        |
| type                  | appstore                                                   |
| git_url               | git@github.com:mycompany/piedpiper-codesigning-certificates.git |
| readonly              | false                                                      |
| username              |<EMAIL_ADDRESS>                                         |
| team_id               | TEAMID32874                                                 |
| storage_mode          | git                                                        |
| git_branch            | master                                                     |
| shallow_clone         | false                                                      |
| clone_branch_directly | false                                                      |
| keychain_name         | login.keychain                                             |
| force                 | false                                                      |
| force_for_new_devices | false                                                      |
| skip_confirmation     | false                                                      |
| skip_docs             | false                                                      |
| platform              | ios                                                        |
| verbose               | false                                                      |
+-----------------------+------------------------------------------------------------+
[07:16:05]: Cloning remote git repo...
[07:16:05]: If cloning the repo takes too long, you can use the clone_branch_directly option in match.
[07:16:06]: 🔓  Successfully decrypted certificates repo
[07:16:06]: Verifying that the certificate and profile are still valid on the Dev Portal...
[07:16:07]: Installing certificate...
security: SecKeychainSearchCopyNext: The specified item could not be found in the keychain.
[07:16:07]: There are no local code signing identities found.
You can run security find-identity -v -p codesigning to get this output.
This Stack Overflow thread has more information: https://stackoverflow.com/q/35390072/774.
(Check in Keychain Access for an expired WWDR certificate: https://stackoverflow.com/a/35409835/774 has more info.)
[07:16:08]: Setting key partition list... (this can take a minute if there are a lot of keys installed)
[07:16:08]: security: SecKeychainUnlock: The user name or passphrase you entered is not correct.
[07:16:08]: security: SecKeychainItemImport: User interaction is not allowed.
+-------------------+---------------------------------------------------+
|                         Installed Certificate                         |
+-------------------+---------------------------------------------------+
| User ID           | TEAMID32874                                        |
| Common Name       | iPhone Distribution: My Company, Inc. (TEAMID32874) |
| Organisation Unit | TEAMID32874                                        |
| Organisation      | My Company, Inc.                                   |
| Country           | US                                                |
| Start Datetime    | 2019-05-01 15:40:56 UTC                           |
| End Datetime      | 2020-04-30 15:40:56 UTC                           |
+-------------------+---------------------------------------------------+
[07:16:08]: Installing provisioning profile...
+---------------------+------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------+
|                                                                                Installed Provisioning Profile                                                                                |
+---------------------+------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------+
| Parameter           | Environment Variable                                       | Value                                                                                |
+---------------------+------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------+
| App Identifier      |                                                            | com.mycompany.ios-beta-13-purple                                                                                |
| Type                |                                                            | appstore                                                                                |
| Platform            |                                                            | ios                                                                                |
| Profile UUID        | sigh_com.mycompany.ios-beta-13-purple_appstore              | 9e011f5d-ad0c-409e-80c1-147871d55a51                                                                             |
| Profile Name        | sigh_com.mycompany.ios-beta-13-purple_appstore_profile-name | match AppStore com.mycompany.ios-beta-13-purple                                                                   |
| Profile Path        | sigh_com.mycompany.ios-beta-13-purple_appstore_profile-path | /Users/distiller/Library/MobileDevice/Provisioning Profiles/9e011f5d-ad0c-409e-80c1-147871d55a51.mobileprovision |
| Development Team ID | sigh_com.mycompany.ios-beta-13-purple_appstore_team-id      | TEAMID32874                                                                                |
+---------------------+------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------+
[07:16:09]: All required keys, certificates and provisioning profiles are installed 🙌
[07:16:09]: Setting Provisioning Profile type to 'app-store'
[07:16:09]: ---------------------------
[07:16:09]: --- Step: build_ios_app ---
[07:16:09]: ---------------------------
[07:16:09]: $ xcodebuild -showBuildSettings -workspace ios/piedpiper.xcworkspace -scheme piedpiper
[07:16:12]: Detected provisioning profile mapping: {:"com.mycompany.ios-beta-13-purple"=>"match AppStore com.mycompany.ios-beta-13-purple"}
+---------------------------------------------------------------------+--------------------------------------------------------------+
|                                                      Summary for gym 2.125.2                                                       |
+---------------------------------------------------------------------+--------------------------------------------------------------+
| workspace                                                           | ios/piedpiper.xcworkspace                                        |
| scheme                                                              | piedpiper                                                        |
| export_method                                                       | app-store                                                    |
| output_directory                                                    | build/ios                                                    |
| clean                                                               | true                                                         |
| export_options.provisioningProfiles.com.mycompany.ios-beta-13-purple | match AppStore com.mycompany.ios-beta-13-purple               |
| destination                                                         | generic/platform=iOS                                         |
| output_name                                                         | piedpiper                                                        |
| build_path                                                          | /Users/distiller/Library/Developer/Xcode/Archives/2019-06-20 |
| silent                                                              | false                                                        |
| skip_package_ipa                                                    | false                                                        |
| result_bundle                                                       | false                                                        |
| buildlog_path                                                       | ~/Library/Logs/gym                                           |
| skip_profile_detection                                              | false                                                        |
| xcode_path                                                          | /Applications/Xcode-10.1.app                                 |
+---------------------------------------------------------------------+--------------------------------------------------------------+
[07:16:12]: $ set -o pipefail && xcodebuild -workspace ios/piedpiper.xcworkspace -scheme piedpiper -destination 'generic/platform=iOS' -archivePath /Users/distiller/Library/Developer/Xcode/Archives/2019-06-20/piedpiper\ 2019-06-20\ 07.16.12.xcarchive clean archive | tee /Users/distiller/Library/Logs/gym/piedpiper-piedpiper.log | xcpretty
[07:16:15]: ▸ Cleaning Pods/Amplitude-iOS [Debug]
[07:16:15]: ▸ Check Dependencies
THEN AT THE END
▸ Check Dependencies
** ARCHIVE FAILED **
The following build commands failed:
Check dependencies
(1 failure)
[07:21:37]: Exit status: 65
[07:21:37]:
[07:21:37]: Maybe the error shown is caused by using the wrong version of Xcode
[07:21:37]: Found multiple versions of Xcode in '/Applications/'
[07:21:37]: Make sure you selected the right version for your project
[07:21:37]: This build process was executed using '/Applications/Xcode-10.1.app'
[07:21:37]: If you want to update your Xcode path, either
[07:21:37]:
[07:21:37]: - Specify the Xcode version in your Fastfile
[07:21:37]: ▸ xcversion(version: "8.1") # Selects Xcode 8.1.0
[07:21:37]:
[07:21:37]: - Specify an absolute path to your Xcode installation in your Fastfile
[07:21:37]: ▸ xcode_select "/Applications/Xcode8.app"
[07:21:37]:
[07:21:37]: - Manually update the path using
[07:21:37]: ▸ sudo xcode-select -s /Applications/Xcode.app
[07:21:37]:
+---------------+------------------------------+
|              Build environment               |
+---------------+------------------------------+
| xcode_path    | /Applications/Xcode-10.1.app |
| gym_version   | 2.125.2                      |
| export_method | app-store                    |
| sdk           | iPhoneOS12.1.sdk             |
+---------------+------------------------------+
[07:21:38]: ▸ === BUILD TARGET piedpiper OF PROJECT piedpiper WITH CONFIGURATION Release ===
[07:21:38]: ▸ Check dependencies
[07:21:38]: ▸ Code Signing Error: No signing certificate "iOS Distribution" found:  No "iOS Distribution" signing certificate matching team ID "TEAMID32874" with a private key was found.
[07:21:38]: ▸ Code Signing Error: Code signing is required for product type 'Application' in SDK 'iOS 12.1'
[07:21:38]:
[07:21:38]: ⬆  Check out the few lines of raw xcodebuild output above for potential hints on how to solve this error
[07:21:38]: 📋  For the complete and more detailed error log, check the full log at:
[07:21:38]: 📋  /Users/distiller/Library/Logs/gym/piedpiper-piedpiper.log
[07:21:38]:
[07:21:38]: Looks like fastlane ran into a build/archive error with your project
[07:21:38]: It's hard to tell what's causing the error, so we wrote some guides on how
[07:21:38]: to troubleshoot build and signing issues: https://docs.fastlane.tools/codesigning/getting-started/
[07:21:38]: Before submitting an issue on GitHub, please follow the guide above and make
[07:21:38]: sure your project is set up correctly.
[07:21:38]: fastlane uses xcodebuild commands to generate your binary, you can see the
[07:21:38]: the full commands printed out in yellow in the above log.
[07:21:38]: Make sure to inspect the output above, as usually you'll find more error information there
[07:21:38]:
+------------------------------------+---------------------------------------------------------------------------------------+
|                                                        Lane Context                                                        |
+------------------------------------+---------------------------------------------------------------------------------------+
| PLATFORM_NAME                      | ios                                                                                |
| LANE_NAME                          | ios release_beta                                                                      |
| PRODUCE_APPLE_ID                   |<PHONE_NUMBER>                                                                            |
| SIGH_PROFILE_TYPE                  | app-store                                                                             |
| MATCH_PROVISIONING_PROFILE_MAPPING | {"com.mycompany.ios-beta-13-purple"=>"match AppStore com.mycompany.ios-beta-13-purple"} |
+------------------------------------+---------------------------------------------------------------------------------------+
[07:21:38]: Error building the application - see the log above
+------+-------------------------------+-------------+
|                  fastlane summary                  |
+------+-------------------------------+-------------+
| Step | Action                        | Time (in s) |
+------+-------------------------------+-------------+
| 1    | xcversion                     | 0           |
| 2    | Switch to ios build_beta lane | 0           |
| 3    | update_url_schemes            | 0           |
| 4    | update_info_plist             | 0           |
| 5    | produce                       | 5           |
| 6    | match                         | 4           |
| 💥   | build_ios_app                 | 328         |
+------+-------------------------------+-------------+

Environment
✅ fastlane environment ✅
Stack

Key
Value

OS
10.14

Ruby
2.4.3

Bundler?
false

Git
git version 2.15.0

Installation Source
/usr/local/bin/fastlane

Host
Mac OS X 10.14 (18A391)

Ruby Lib Dir
/usr/local/Cellar/ruby/2.4.3_1/lib

OpenSSL Version
OpenSSL 1.0.2n  7 Dec 2017

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
10.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
#     https://docs.fastlane.tools/actions
#

# Uncomment the line if you want fastlane to automatically update itself
# update_fastlane

# If Fastlane asks you for a password check for it in One Password

xcversion(version: "10.1")

GIT_URL = 'git@github.com:mycompany/piedpiper-codesigning-certificates.git';

if ENV['CIRCLE_BRANCH'].split('robot/beta/ios/build/')[1]
  BETA_SKU_MAP = {
    'blue' => '4200769917',
    'pink' => '4200769540',
    'purple' => '4200967692',
  };
  BETA_ID_MAP = {
    'blue' => '4208969068',
    'pink' => '4208969223',
    'purple' => '4206964798',
  };
  BETA_RELEASE_CHANNEL = ENV['CIRCLE_BRANCH'].split('build/')[1];
  BETA_APP_SLUG = BETA_RELEASE_CHANNEL.split('-')[3];
  BETA_CHANNEL_NAME = BETA_RELEASE_CHANNEL.split('-').last;
  BETA_URL_SCHEME = 'piedpiper-beta-' + BETA_CHANNEL_NAME;
  BETA_APP_IDENTIFIER = 'com.mycompany.' + BETA_RELEASE_CHANNEL;
  BETA_APP_DISPLAY_NAME = 'Cameo ' + BETA_RELEASE_CHANNEL.split('-').last.capitalize;
  BETA_SKU = BETA_SKU_MAP[ BETA_APP_SLUG ];
  BETA_ID = BETA_ID_MAP[ BETA_APP_SLUG ];
end

platform :ios do
  desc 'Build an IPA file and sign the code'
  lane :build_production do
    match(
      app_identifier: 'com.mycompany.piedpiper',
      type: 'appstore',
      git_url: GIT_URL,
      readonly: true
    )
    build_ios_app(
      workspace: 'ios/piedpiper.xcworkspace',
      scheme: 'piedpiper',
      export_method: 'app-store',
      output_directory: 'build/ios',
      clean: true
    )
  end
  desc 'Build a signed IPA file and submit it to the App Store'
  lane :release_production do
    build_production
    upload_to_app_store
  end
  lane :build_beta do
    update_url_schemes(
      path: 'ios/piedpiper/Supporting/Info.plist',
      url_schemes: [BETA_URL_SCHEME]
    )
    update_info_plist( # Target a specific `xcodeproj` rather than finding the first available one
      xcodeproj: 'ios/piedpiper.xcodeproj',
      plist_path: 'piedpiper/Supporting/Info.plist',
      app_identifier: BETA_APP_IDENTIFIER,
      display_name: BETA_APP_DISPLAY_NAME
    )
    produce(
      app_identifier: BETA_APP_IDENTIFIER,
      app_name: BETA_APP_DISPLAY_NAME,
      enable_services: {
        push_notification: 'on',
      },
      sku: BETA_SKU
    )
    match(
      app_identifier: BETA_APP_IDENTIFIER,
      type: 'appstore',
      git_url: GIT_URL,
      readonly: false
    )
    build_ios_app(
      workspace: 'ios/piedpiper.xcworkspace',
      scheme: 'piedpiper',
      export_method: 'app-store',
      output_directory: 'build/ios',
      clean: true
    )
  end
  lane :release_beta do
    build_beta
    upload_to_testflight(
      groups: ['piedpiper internal'],
      reject_build_waiting_for_review: true,
      apple_id: BETA_ID,
      app_identifier: BETA_APP_IDENTIFIER
    )
  end
  lane :simulator_build do
    # to get help get output path, you can use:
    # xcodebuild -project ios/piedpiper.xcodeproj -showBuildSettings
    xcbuild(
      workspace: 'ios/piedpiper.xcworkspace',
      scheme: 'piedpiper',
      xcargs: '-configuration "Release" -sdk "iphonesimulator12.1" -destination "generic/platform=iOS Simulator"'
    )
  end
end

platform :android do
  desc 'Build APK file'
  lane :build do
    gradle(task: 'clean', project_dir: 'android')
    gradle(
      task: 'assemble',
      build_type: 'Release',
      project_dir: 'android'
    )
  end
  desc 'Build APK file and submit it to Play Store'
  lane :release do
    build
    upload_to_play_store
  end
end

`./fastlane/Appfile`
<EMAIL_ADDRESS># Your Apple email address

itc_team_id("123456789") # App Store Connect Team ID
team_id("TEAMID12234") # Developer Portal Team ID

# For more information about the Appfile, see:
#     https://docs.fastlane.tools/advanced/#appfile

fastlane gems

Gem
Version
Update-Status

fastlane
2.125.2
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.1.0

slack-notifier
2.3.2

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

terminal-table
1.8.0

plist
3.5.0

public_suffix
2.0.5

addressable
2.6.0

multipart-post
2.0.0

word_wrap
1.0.0

babosa
1.0.2

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

excon
0.64.0

faraday
0.15.4

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20180417

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
2.1.5

gh_inspector
1.1.3

mini_magick
4.5.1

multi_xml
0.6.0

security
0.1.3

xcpretty-travis-formatter
1.0.0

dotenv
2.7.2

bundler
2.0.1

faraday_middleware
0.13.1

naturally
2.2.0

simctl
1.6.5

jwt
2.1.0

uber
0.1.0

declarative
0.0.10

declarative-option
0.1.0

representable
3.0.4

retriable
3.1.2

mime-types-data
3.2019.0331

mime-types
3.2.2

multi_json
1.13.1

signet
0.11.0

memoist
0.16.0

os
1.0.1

googleauth
0.6.7

httpclient
2.8.3

google-api-client
0.23.9

google-cloud-core
1.3.0

digest-crc
0.4.1

google-cloud-storage
1.16.0

emoji_regex
1.0.1

tty-cursor
0.7.0

tty-spinner
0.9.1

tty-screen
0.7.0

openssl
2.0.5

json
2.2.0

io-console
0.4.6

rubyzip
1.2.3

CFPropertyList
3.0.0

mini_portile2
2.4.0

nokogiri
1.10.3

atomos
0.1.3

claide
1.0.2

colored2
3.1.2

nanaimo
0.2.6

xcodeproj
1.10.0

unicode-display_width
1.6.0

psych
2.2.2

generated on: 2019-06-20

@tvongeldern Heyyy 👋 I always put this setup_circle_ci action in my Fastfile when I use CircleCi. I don't see it in your Fastfile so it seems like that could be the cause 🤔
https://docs.fastlane.tools/best-practices/continuous-integration/circle-ci/#circleci-integration

Thank you for the response, @joshdholtz! I added that at the beginning of my iOS lane and I still got the following:
[11:00:20]: Cloning remote git repo...
[11:00:20]: If cloning the repo takes too long, you can use the `clone_branch_directly` option in match.
[11:00:21]: 🔓  Successfully decrypted certificates repo
[11:00:21]: Installing certificate...
security: SecKeychainSearchCopyNext: The specified item could not be found in the keychain.
[11:00:22]: There are no local code signing identities found.
You can run `security find-identity -v -p codesigning fastlane_tmp_keychain` to get this output.
This Stack Overflow thread has more information: https://stackoverflow.com/q/35390072/774.
(Check in Keychain Access for an expired WWDR certificate: https://stackoverflow.com/a/35409835/774 has more info.)
[11:00:22]: Setting key partition list... (this can take a minute if there are a lot of keys installed)
[11:00:22]: security: SecItemCopyMatching: The specified item could not be found in the keychain.
[11:00:22]: Setting key partition list... (this can take a minute if there are a lot of keys installed)

Actually, when I use the before_all command like it says to in the docs, it works. For some reason, it wasn't working when I just put it as the first line in my build_beta lane.
Thank you!


function-uses-loop-variable (B023) - option to define functions where lambda is executed immediately

in my codebase there's a find function where the lambda is executed immediately which means it's safe to use the loop variable this way, so i have to suppress this rule on all of its usages:
foo = [1, 2, 3]
for bar in foo:
    find([1, 2, 3], lambda value: value == bar)  # noqa: B023

it would be nice if there was an option to specify functions where the lambda is executed immediately, like with extend-immutable-calls:
[tool.ruff.flake8-bugbear]
lambdas-executed-immediately = ["find"] # perhaps also a way of specifying which argument takes the lambda

Related: https://github.com/python/typing/issues/1070

I understand the use-case, and it'd be nice to have a way to express this in the type system that we could leverage in Ruff, but I think this is too niche to justify a dedicated setting at present. Every setting adds some additional cognitive burden for users and has an implementation + ongoing maintenance cost, so it needs to meet some threshold for general usefulness and applicability. If we see this need arise again in the future, we can always reconsider.


Presumably it's stuck in a loop that would never terminate; or it might if given more memory, but would require an astronomical amount to succeed--notice, however, that the header contents are hardly exotic: just preprocessor junk and C declarations.
Repro with systemd-run --user -p MemoryMax=8G -S, then in the shell, run clangd --log=verbose --check=mathlink.h (you don't have to use systemd-run, but beware of systemd/systemd#25376 if you don't!)
Logs
clangd-stderr.txt
System information
Output of clangd --version:
clangd version 15.0.3 (https://github.com/llvm/llvm-project 4a2c05b05ed07f1f620e94f6524a8b4b2760a0b1)
Features: linux+grpc
Platform: x86_64-unknown-linux-gnu

Editor/LSP plugin:
Emacs 28.1 + lsp-mode
Operating system:
Linux arch-vm 6.0.7-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 03 Nov 2022 18:01:58 +0000 x86_64 GNU/Linux

This is still broken on clangd 16.0.2.
clangd version 16.0.2 (https://github.com/llvm/llvm-project 18ddebe1a1a9bde349441631365f0472e9693520)
Features: linux+grpc
Platform: x86_64-unknown-linux-gnu

There's a newer version of the header file I attached in the initial post that parses successfully, but the diff is a bit large to be able to wager a guess at exactly what causes the problem in the original file. I've attached it anyway in case it's useful: mathlink2.txt

I tried this locally, and attached a debugger during the hang to get a stack trace.
The stack trace shows us being in clang::format::guessLanguage(), which makes this another case of https://github.com/llvm/llvm-project/issues/60151 (which has been reported for clangd with other libraries such as miniaudio.h, e.g. in https://github.com/clangd/clangd/issues/719).

Thanks for looking into this. It's almost definitely the same root cause as the bug you linked, since renaming the file makes the issue go away here too.
I started following the stack trace down from guessLanguage() and arrived at the extremely dodgy-looking UnwrappedLineParser::parseLevel()--will you be surprised if I tell you it accumulates tokens in do ... while (!feof()) loop? Given llvm/llvm-project#78263 has a minimized repro and my original file exercises the exact same combination of tokens/state, this is looking promising. See also llvm/llvm-project#64328.

That said, after some experimentation with the file I provided, it seems less likely that it's an issue of outright non-termination, but rather that the algorithm is susceptible to exponential blowup (see llvm/llvm-project#64328).

Yeah, Sam came to the same conclusion in https://github.com/llvm/llvm-project/issues/48863#issuecomment-981039782.
I tried to come up with a way to work around this in clangd (see https://github.com/clangd/clangd/issues/719#issuecomment-1789776339 and subsequent comments) but we don't seem to have great options.
I'm now thinking a better avenue would be to add some sort of guard against algorithmic blowup into the relevant clang-format code (whether a depth limit, or a maximum iteration count, or somethig like that), and bail if we hit that limit, possibly having guessLanguage() produce a suboptimal result which is still much better than OOM-ing.

I agree with your comments.
Frankly, I'd remove the silly heuristic entirely--it's slow, failure-prone, and does a disservice to the majority of users in favor of offering dubious benefit to a much smaller minority, who would only have to add overrides in order to view .h objc headers that hadn't already been inferred by clangd as objc (easy to track, since objc uses #import). Just add a handful of default paths that are typically known to contain objc headers or whatever--/usr/include/objc, wherever Apple's framework paths look like these days, etc.

I'm now thinking a better avenue would be to add some sort of guard against algorithmic blowup into the relevant clang-format code (whether a depth limit, or a maximum iteration count, or somethig like that), and bail if we hit that limit, possibly having guessLanguage() produce a suboptimal/incorrect result which is still much better than OOM-ing.

I implemented this in https://github.com/llvm/llvm-project/pull/78925, and confirmed that it addresses the OOM in guessLanguage() in the various libraries for which this bug was reported (mathlink.h, miniaudio.h, a couple of others).

Frankly, I'd remove the silly heuristic entirely--it's slow, failure-prone, and does a disservice to the majority of users in favor of offering dubious benefit to a much smaller minority, who would only have to add overrides in order to view .h objc headers that hadn't already been inferred by clangd as objc (easy to track, since objc uses #import). Just add a handful of default paths that are typically known to contain objc headers or whatever--/usr/include/objc, wherever Apple's framework paths look like these days, etc.

I didn't pursue this because currently there isn't a mechanism for clangd to tell clangd-format the file type, and in any case as discussed here, a discrepancy between "filetype detected when invoked via clangd" and "filetype detected when invoked on the command line" would be problematic. One could conceivably add a way to configure file type overrides at the clang-format level (e.g. in a .clang-format file); if you or someone would like to pursue that and remove guessLanguage() altogether, please feel free.

I implemented this in llvm/llvm-project#78925, and confirmed that it addresses the OOM in guessLanguage() in the various libraries for which this bug was reported (mathlink.h, miniaudio.h, a couple of others).

Thank you so much!!

I didn't pursue this because currently there isn't a mechanism for clangd to tell clang-format the file type, and in any case as discussed here, a discrepancy between "filetype detected when invoked via clangd" and "filetype detected when invoked on the command line" would be problematic. One could conceivably add a way to configure file type overrides at the clang-format level (e.g. in a .clang-format file); if you or someone would like to pursue that and remove guessLanguage() altogether, please feel free.

I see; makes sense.


[INTERNAL] builder: Improve JSDoc

Coverage remained the same at 91.513% when pulling fbff9e0d24ecf67de89a889debd207c12b14f235 on builder-jsdoc into 97b339f9c5dbddc8b80ed11c68f557d4eddc7f0a on master.


problème assignation de touche

Bonjour,
merci pour ce merveilleux plugins qui fonctionnait à merveille jusque ici.
Mais depuis que j'ai réinstaller SC sur un nouveau disque dur le plugins ne fonctionne plus.
un voyant jaune apparait lorsque j'appui sur les touche du plugin sur mon streamdeck.
j'ai l'impression  que le chemin d'accès au touches n'est pas trouvé.
J'ai pourtant suivis les instruction et rentré manuellement le bon chemin d'accès... :/ pouvez-vous m'aider je suis a bout de solution.
Cordialement merci.

English please I don't speak French
Please check plugin log file for any errors and set directory of the game files manually in config file

Hello, thank you for your feedback.
I have already set directory of the game files manually in config file.

When i check plugin log :
(I only took the last 3 lines)
2024-04-15 14:39:49.7161|DEBUG|com.mhwlng.starcitizen|1|Logger Initialized
2024-04-15 14:39:49.7451|INFO|com.mhwlng.starcitizen|1|Init Star Citizen
2024-04-15 14:39:49.7531|INFO|com.mhwlng.starcitizen|1|E:\RSI\StarCitizen\LIVE\Data.p4k
Sincerely
thx.

please post the complete log file here
please post the actionmaps.xml here

please post the files, not screenshots

pluginlog.log

actionmaps.xml.txt
the format hml isn't support here so I transformed the file into ".txt". is ok for you ?

I still can't reproduce the problem.
can you please zip the whole plugin directory and post it here
also try to start streamdeck.exe as administrator
it seems that the plugin cannot read the pk4 file ?
Your log
Init Star Citizen
E:\RSI\StarCitizen\LIVE\Data.p4k
my log
Init Star Citizen
C:\Program Files\Roberts Space Industries\StarCitizen\LIVE\Data.p4k needs update : False
C:\Program Files\Roberts Space Industries\StarCitizen\LIVE\USER\Client\0\Profiles\default\actionmaps.xml
Keyboard Detected, language : 409 keyboard : 409 culture : en-US
Keyboard Detected, language : 409 keyboard : 409 culture : en-US
Keyboard Detected, language : 409 keyboard : 409 culture : en-US
monitoring key binding file
Finished Init Star Citizen

Your files are the same as mine.
the plugin tries to read the pk4 file and crashes
compared mine to yours:
all extra files are created automatically and this doesn't happen on your system.

please try to start streamdeck.exe as administrator
if that doesn't help then I have no idea what the problem is on your pc?

I just tried to run it as administrator and the result is the same.
pluginlog.log
the problem has persisted since the installation of RSI launcher 2.0.
could there be a link?

today I also installed the launcher 2.0 and all is ok for me
the pk4 is todays date (when I installed launcher 2.0):

I'm sorry, but I don't know what else to suggest...

ok thank you for your time I am also short of solutions :(
I completely rebooted my pc for nothing lol
kind regards

I had the problem from the moment I installed the new luncher and completely reinstalled the games. I didn't have the problem with the new luncher in beta without having to reinstall all the games.

I delete the game and re-installed it and now I see the same problem with the p4k file.
I see that the P4k is now a smaller size than before. (from 102GB to 96.7GB)
I have to investigate further if I can read the new file format.
This is will take a while. I am not sure if I will be able to.
I will try to find some time this weekend.

well I did a test, I reinstalled the old luncher and then I reinstalled the game and the plugin works. I then reinstalled the new luncher without reinstalling all the games and the plugin still works. the problem comes from the installation from the new luncher.

the new plugin version 1.1.2 should be able to read the new p4k format

oh perfect man!!! I'm going to test this right away. thank you very much for your feedback.


apology

Hey Sean,
I'm very sorry for the way I spoke to you yesterday.  I was excited to finally work on a UI project with you after a year of mostly fixing performance and reliability issues and there was no reason for me to voice my frustrations towards you.  I think you are doing exactly what I would in your situation so rock on, just wanted to apologize since I missed my chance earlier.

Hey Tyler, I really appreciate the apology. Thanks.
I wish you all the best now and in the future.
Cheers,
Sean


Is it able to multi select rows with Ctrl button in keyboard?

STOP
We do not use Github to track general support. Please use our public support forum at https://spectrum.chat/react-table.
NOTE: If a support/help/question issue is opened, it will be closed immediately and be redirected to the forum. Thanks for helping us keep our issues clean and productive!

https://spectrum.chat/react-table


Verify that we can now use unicode in GR-based labels, etc. with Plots

The latest versions of GR might support using unicode labels.  If so, we can slowly make transitions towards those.
But first lets verify that it is true in the whole pipeline.
Maybe on https://julia.quantecon.org/getting_started_julia/julia_by_example.html#A-Slightly-More-Useful-Function  and see if something like the following works:
using Distributions

function plothistogram(distribution, n)
    ϵ = rand(distribution, n)  # n draws from distribution
    histogram(ϵ, label = "ϵ")
end

lp = Laplace()
plothistogram(lp, 500)

By works I mean that (1) the HTML that is generated by jupinx displays the label correct, (2) the generated jupyter notebooks do as well; and (3) no ugly warnings show up.

Verified


Update sidekiq worker to job in readme

Pull Request
Fixes #136
Workers have been depreciated in Sidekiq in favor of jobs. I have updated the readme so it reflects the change in order to prevent confusion.

Hi @jmarsh24 thanks for contributing to Meilisearch! ❤
Can you send me some sidekiq references which mention this change?

Of course. I should have provided it in the initial issue and pull request. Here you go!
https://github.com/mperham/sidekiq/blob/main/Changes.md

bors merge