What is missing? How to help?

Hello. It would be nice some documentation explaining what is still missing for this project or how to help. The project's idea is quite nice.

+1, this library is amazing, I’d like to see it moving forward. @rtsisyk, could you please respond?

Hi guys,
Sorry for the silence for the long time. The primary problem is that I've completely lost my interest in LuaJIT optimizations. I spent several years working with LuaJIT in Tarantool. LuaJIT 2.x was the integral part of our project from the early beginning. I’m definitely sure that we have created the best database and application server for the LuaJIT.
Now I have to say that I don’t buy into LuaJIT anymore. My favorite joke about LuaJIT is that it can be either Lua or JIT, not both at the same time. JIT has never worked out of the box. You need to rewrite all your nice Lua code to deal with NYI, Lua/C functions, suddenly aborted JIT traces and so on. This process is always complicated, time-consuming and unpredictable. The resulting code is unreadable, obfuscated and hard to maintain. Moreover, you have a chance to end with JIT-friendly code which is surprisingly slower that the original interpreted version.
I realized that in terms of human resources it is cheaper rewrite all my performance-critical code using compiled  language, like C/C++/Rust/Go/Swift rather than get stable JIT traces. In other words, JIT optimizations in LuaJIT simply doesn’t pay off in my business.
Anyway, LuaJIT is the best interpreter on the market. Just believe me. Mike Pall has done the very great job. Tracing JIT is the cutting edge technology and LuaJIT and luafun in particular are still very useful for the some cases. JIT just requires some more efforts I can't afford.
My offer is pretty simple. I'd like to grant the full permissions to somebody who has a vision how to move this project forward and can propose a new roadmap for LuaFun. LuaFun is probably the most popular Lua and LuaJIT module on GitHub. A lot of people have interest in this project. I just can't spent enough time on LuaJIT-related stuff anymore. I want LuaFun to become more community-driven rather than my personal one-man project. I'm on GitHub every day, let's have a talk.

The first step is done - I moved this repository to https://github/luafun/luafun/.

Brutal honesty @rtsisyk :-)

Brutal honesty @rtsisyk :-)

Sad, but true :( I'm tired of all this JIT magic. For example, a week good I had to disable JIT in one of Tarantool test cases because LuaJIT degraded from 5-10 ms to (!) 500 ms without any changes in the code itself!
Since Mike has resigned, all we need to join efforts to maintain LuaJIT. Do you plan to fork LuaJIT for Snabb? Tarantool already uses a fork.

I am excited about tracing JIT. I want to master it, document it, and build tools to make it more transparent. I am working on this very actively at the moment as part of a broader performance benchmarking/optimization effort in Snabb.
I understand your frustration though. On the one hand JIT behavior is not well documented, not widely understood, not easy to understand with the tools available. On the other hand you cannot use it effectively without understanding it. I can see this would be especially frustrating for people who are working with PUC Lua rather than targeting LuaJIT exclusively (as we do.)
Having said that, I think LuaJIT complexity is on the same level as other technologies that we are all using successfully like CPUs, GPUs, kernels, databases, etc.
Snabb also has a LuaJIT fork. This has only minimal differences. I am interested in maintaining a branch that has extended profiling and low-level programming (e.g. intrinsics/dynasm) support. I think it will be great for all of us maintaining LuaJIT branches to sync up and establish suitable merging relationships to propagate changes. See also LuaJIT/LuaJIT#219.


[Do not merge] Debug integration test failure

To debug the integration test failure in #14364:

revert all commits after the commit 2a1b9d8, which is merged in master branch on 5-24-2019.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: lei-tang
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: linsun
If they are not already assigned, you can assign the PR to them by writing /assign @linsun in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS
prow/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@lei-tang: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-security-k8s-presubmit-tests.sh
ae59f73fbc3ae26978622de6e529c982cfc37ee3
link
/test integ-security-k8s-presubmit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@lei-tang: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


[SPARK-27863][SQL] Metadata files and temporary files should not be counted as data files

What changes were proposed in this pull request?
DataSourceUtils.isDataPath(path) should be DataSourceUtils.isDataPath(status.getPath).
This pr fix this issue.
How was this patch tested?
unit tests

Test build #105859 has started for PR 24725 at commit a8243b3.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/11115/
Test PASSed.

Test build #105859 has finished for PR 24725 at commit a8243b3.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/105859/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/11121/
Test PASSed.

Test build #105865 has started for PR 24725 at commit fb44905.

Merged build finished. Test PASSed.

OK. I'll make PR later.


trainer.tune() fails when Trainer.init(auto_lr_find=True, auto_scale_batch_size=True)

🐛 Bug
trainer.tune() works just fine when either Trainer.__init__(auto_lr_find=False, auto_scale_batch_size=True) or Trainer.__init__(auto_lr_find=True, auto_scale_batch_size=False)
However, trainer.tune() fails when Trainer.__init__(auto_lr_find=True, auto_scale_batch_size=True)
LR finder stopped early due to diverging loss.
INFO   lr_finder.py:186:lr_find(): LR finder stopped early due to diverging loss.
/home/vin/.local/lib/python3.8/site-packages/pytorch_lightning/utilities/distributed.py:49: UserWarning: You're resuming from a checkpoint that ended mid-epoch. This can cause unreliable results if further training is done, consider using an end of epoch checkpoint.
  warnings.warn(*args, **kwargs)
Failed to compute suggesting for `lr`. There might not be enough points.
Traceback (most recent call last):
  File "/home/vin/.local/lib/python3.8/site-packages/pytorch_lightning/tuner/lr_finder.py", line 353, in suggestion
    min_grad = np.gradient(loss).argmin()
  File "<__array_function__ internals>", line 5, in gradient
  File "/home/vin/.local/lib/python3.8/site-packages/numpy/lib/function_base.py", line 1052, in gradient
    raise ValueError(
ValueError: Shape of array too small to calculate a numerical gradient, at least (edge_order + 1) elements are required.
ERROR  lr_finder.py:357:suggestion(): Failed to compute suggesting for `lr`. There might not be enough points.

Please reproduce using the BoringModel

To Reproduce
Use following BoringModel and post here

In your own environment trainer.tune() should fail when Trainer.init(auto_lr_find=True, auto_scale_batch_size=True). However, if you want to reproduce the bug from my code then go to Github, and fork from https://github.com/vineetk1/conversational-transaction-bot
Then run the following on commandline:
python3 ctbMain.py input_param_files/distilgpt2_params
Expected behavior
trainer.tune() should find the Batch-Size and the initial Learning-Rate

Environment
Note: Bugs with code are solved faster ! Colab Notebook should be made public !

IDE: Please, use our python bug_report_model.py template.

Colab Notebook: Please copy and paste the output from our environment collection script (or fill out the checklist below manually).

You can get the script and run it with:
wget https://raw.githubusercontent.com/PyTorchLightning/pytorch-lightning/master/tests/collect_env_details.py
# For security purposes, please check the contents of collect_env_details.py before running it.
python collect_env_details.py

PyTorch Version (e.g., 1.0): 1.6.0
OS (e.g., Linux): Ubuntu-Linux
How you installed PyTorch (conda, pip, source): pip
Build command you used (if compiling from source):
Python version: 3.8.5
CUDA/cuDNN version: 11.0
GPU models and configuration: Nvidia GeForce GTX 1080
Any other relevant information:

Additional context

I ran into this too, and refactored my code to init two separate trainers and models and tune()d the batch_size and learning_rate separately.  Then, out of an abundance of caution, I re-init the trainer and model again before calling fit().
In case it helps as a clue, when I was debugging this, it seemed that the auto_scale_batch_size functionality does not properly replace the original model weights after tuning.  I believe the LR finder does this, and therefore might have example code.
Working code that tune()s separately:
    dm = BoringDataModule()
    model = BoringModel(...)
    trainer = pl.Trainer(..., auto_scale_batch_size=True)
    trainer.tune(model, datamodule=dm)
    print('Suggested batch size:', dm.batch_size)

    model = BoringModel(...)
    trainer = pl.Trainer(..., auto_lr_find=True)
    trainer.tune(model, datamodule=dm)
    print('Suggested learning rate:', model.hparams.learning_rate)

    model = BoringModel(...)
    trainer = pl.Trainer(...)
    trainer.fit(model, datamodule=dm)

@SkafteNicki


[HIPIFY] is it possible to hipify all included cuda header files in one go?

I encountering a problem when hipify a CU file, which #include some other header files, which include a bunch of other header files like a cascade.
by the way, some headers are in the same folder as cu file, some are not.
it would be really neat, if hipify could process all relevant files in one go and output the hip files in one place.
I also don't really want to process that containing folder, because i just want to port one module each time.
This will make the porting feasible.
Thanks for any helps

What do you mean by relevant files? Include files might be CUDA Toolkit ones, the mixed files CUDA/HIP, or even system files.
hipify-clang uses an approach of the main file: the file specified explicitly as the input source file is only hipified. It supports neither a total folder/subfolders transformation of source files nor all the included header files tree.

You may specify multiple source CUDA files to hipify, including header files.
You may use the -p option for specifying compile command database in JSON format (https://github.com/ROCm-Developer-Tools/HIPIFY#-hipify-clang-usage). [IMP NOTE] Only additional clang options (like -D, -I, etc.) can be specified in that file.


Unable to route packets between different drivers

It's currently not possible to route packets between two interfaces that uses different drivers. The reason is most likely different offsets in the driver.
Should this be possible?
This could easily be tested by using the test/net/integration/gateway service, by changing one of the first devices in vm.json to use a different device.
With the combination
   {"device" : "virtio", "mac" : "c0:01:0a:00:00:2a"},
   {"device" : "vmxnet3", "mac" : "c0:01:0a:00:00:2f"},

I get this crash:
IncludeOS/src/drivers/virtionet.cpp:358:enqueue_tx Expects failed: pckt->layer_begin() == pckt->buf() + sizeof(virtio_net_hdr)

We can at least make a copy of the data and create a new packet for the different driver. As long as the packets size is within the MTU of the destination, that way small packets like TCP SYN and friends can work even when the MTUs differ.
The driver offsets are not optional, and they also contribute to aligning the network layer to 32-bits which allows accessing many things like IPv4 addresses directly with aligned instructions. Any changes made to how the packets are laid out in memory needs to go through a battery of tests, with sanitizers enabled, in the linux platform.

Did you solve the problem? Or do you find other simple methods to test it? I also wanna make a simple test for the function of Router but I dont have good idea. Thanks for helping.


Error panel covers the entire screen (doesn't have a proper max size)

For an file that has a lot of errors (maybe because I accidentally removed a quote mark), Linter fills up the error screen to cover the entire window, making it impossible to even edit the file and remove the error. The only solution is either to undo the change or disable the use of the error panel.

It's actually an error in your theme :)

Closing as invalid. Feel free to continue the discussion.

Uh I'm using the default theme, One Dark, so if that's broken...

I am unable to reproduce this error on the same theme :)
For me, it's max-height works. What's your atom version?

v1.0.2.


Better xcorr

Better, more straightforward auto- and cross-correlations.
Includes numba implementation of xcorr that is very fast even for many thousands of spikes.
TODOs:

[x] add tests
[x] finish docstrings
[x] place some further ideas in issues

(I'll create a notebook example later)


fruit_website

The feature I want to add:

I can make the website more beautiful by adding a good colour combination and design background to make it more appealing to the approaching customers.
I also want to add a slide show wherein all the latest trends and new comings will be shortlisted.
I can also make the text error-free and new catchy lines can be added by me.
I can also make a readme file wherein I can give the description of the project which will help future contributors who want to contribute to this project.
Expected behaviour
It will look more professional and concise and the user will have a good experience while surfing on it.

Please assign me this issue under GSSoC'23, thank you.

sir the work has been done..how to submit it?


Update for mamba 2.0.0rc2

And maybe remove this so that if we missed places we would have errors.

Or we can set MAMBA_EXE to the same path as MICROMAMBA_EXE instead (less replacement)

Or we can just set MAMBA_EXE to the same path as MICROMAMBA_EXE instead (less replacement)

Done in ff16804. FYI, MAMBA_EXE has the same value than MICROMAMBA_EXE i.e "/usr/local/bin/micromamba" after the hook is called.

Closing as this PR only was meant to test mamba 2.0 release candidates.


Build & deploy main branch

Build "main" branch and deploy to jekyll-stage.legumeinfo.org

@nathanweeks please be the PR-boss for this one, and others that deal with GitHub pages, at least until that process is working smoothly. Right now it seems to me like there are two PRs to get jekyll-stage.legumeinfo.org updated: one to merge into main and another to do build/deploy main branch. I hope I'm wrong about that, I want a single merge into main to do the whole shibang. Maybe we just got two PRs on this first round.

@nathanweeks please be the PR-boss for this one, and others that deal with GitHub pages, at least until that process is working smoothly. Right now it seems to me like there are two PRs to get jekyll-stage.legumeinfo.org updated: one to merge into main and another to do build/deploy main branch. I hope I'm wrong about that, I want a single merge into main to do the whole shibang. Maybe we just got two PRs on this first round.

Done. A single merge sufficed (+ updating the repository settings to host the GitHub Pages site from the jekyll-stage.legumeinfo.org branch)


Docs: Modal prop "title" is required

Subject
Modal prop "title" is marked as not required in documentation, but modal component requires it and raises an error on compilation.
Documentation

Error

Expected result
Required: Yes

@dmitry-sidorov Thank you again, for temporary fix you can change the modal component, just add default: nil.
attr :title, :string, doc: "Specifies the title of the element"

To this:
attr :title, :string, default: nil, doc: "Specifies the title of the element"

After this if it does not work please tell me.
I will fix this

Thank you for work around :) I use modals with title for now 😆

Thank you for helping us, you can update your dep from master and i fixed it.
Sorry for these bugs, we will start E2E test after some release.


upgrade the swagger-ui3.1.6  to swagger-ui 3.2.23

Is there a document which helps how to upgrade the swagger-ui3.1.6 ?
I am new to the swagger
Our project is using the swagger-ui 3.1.6 and needed to be upgraded it to swagger-ui 3.2.23 as the swagger-ui 3.1.6 is vulnerable as per the blackduck?
Could you please help me to upgrade or give some information how I can upgrade.
I see the version defined in the swagger-ui-bundle.js with the below details
x = {
PACKAGE_VERSION: "3.1.6",
GIT_COMMIT: "g786cd47",
GIT_DIRTY: !0,
HOSTNAME: "WM-5020",
BUILD_TIME: "Sat, 19 Aug 2017 01:37:07 GMT"
},

Swashbuckle ships with an embedded, specific version of the SwaggerUI. So, to upgrade the swagger-ui, you need to upgrade the Swashbuckle.AspNetCore.SwaggerUI package. The current version of this package ships with v3.32.5 of the swagger-ui.


Dataset Release Issue

Hi everyone,
In the recent one month, I have received a lot of emails and messages regarding to the missing datasets issue. After digging in my lab servers, PC, old laptops and so on, I eventually found a copy of "pre-processed (resize operation)" ground truth data of Matterport3D as well as ScanNetv2. After that, I contacted Yinda Zhang for the news but did not receive any reply for a while. As it can be used for academic advancement, I decided to share them although it might be a bit different from the original data.
In the following 7-14 days, I will organize these data, upload to a "safer place", and publish rules for using datasets on our GitHub. Also, feel free to contact me if you own an "original copy". I will close this issue once I finish it.
Thanks for your patience.

Hi everyone,
we have released our dataset. Please follow in instructions described on our README to obtain dataset access.
Thanks.
Best,
Tsung-Han Wu

Hello,
Thanks for your release! When I open the link of the dataset https://forms.gle/aeQS12fSKPjnEuey9, google shows that I don't have the authority of this form.

Hi @eecoder-dyf,
Sorry for the inconvenience and I have updated the permission. Thanks for your kind reminder.
Best,
Tsung-Han

Hello,
Thanks for your released dataset! When I compare the released resized dataset with the resized dataset generated by your code, I find they are different. And, I think the later one is better from visualized 3D point cloud. Which one should I use?
Thank you for your time.

Hi @Earmu,
Sorry for the delay in my response as I've been really busy lately. For your question, I think the resized data set I provided should be sufficient.
It sounds like the issue you mentioned might be caused by different resize parameters. For example, RGB images are typically best suited for bilinear interpolation, while depth images should use nearest neighbor interpolation to avoid generating interpolated depth values at the boundaries. However, this is just my personal opinion and you may want to do some additional research on this topic if you are interested.
Best,
Patrick

Hello @tsunghan-wu ,
Thank you for reply. Sorry for misunderstanding. Before, I meant I used the method of line 149 in the dataloader.py to resize the depth map of 1280*1024, and I found that the resized result was different from the released dataset in Google driver.
And, I think your opinions about inpterpolation method are reasonable. Now, I should modify the order parameter of  skimage.transform.resize to resize depth map. (0: Nearest-neighbor, 1: Bi-linear (default)).
Thank you for your time!!!

Hi @ZhenshanLiang,
Hmm... excuse me that I can't answer you why the results are inconsistent, as this work was done three years ago and I don't have the original dataset copy on hand .  If you figure out why and would like to share it with me, feel free to let me know!
Hope everything goes well for your ongoing work.
Best,
Patrick

Hello @tsunghan-wu ,
OK! If I get some results, I will share them with you.
Thank you for your patience.

Hello,
Sorry for late sharing. As @tsunghan-wu said, depth images should use nearest neighbor interpolation to avoid generating interpolated depth values at the boundaries. I just want to mention that the if using skimage.transform.resize to downsample depth map, the order parameter is 0 and I use this to generate more data:
from skimage.transform import resize as numpy_resize
downsample_depth = numpy_resize(depth_map, (256, 320), mode='constant', order=0, anti_aliasing=False)


Supporting files not found after installing with setup.py

After installing with setup.py I try running the example from the documentation but resource_filename('awesimsoss','files/scaled_spectrum.txt') fails with the following error:
Traceback (most recent call last):
File "simulate.py", line 17, in
star = np.genfromtxt(resource_filename('awesimsoss','files/scaled_spectrum.txt'), unpack=True)
File "/home/talens-irex/.local/lib/python3.6/site-packages/numpy/lib/npyio.py", line 1737, in genfromtxt
fhd = iter(np.lib._datasource.open(fname, 'rt', encoding=encoding))
File "/home/talens-irex/.local/lib/python3.6/site-packages/numpy/lib/_datasource.py", line 266, in open
return ds.open(path, mode, encoding=encoding, newline=newline)
File "/home/talens-irex/.local/lib/python3.6/site-packages/numpy/lib/_datasource.py", line 624, in open
raise IOError("%s not found." % path)
OSError: /home/talens-irex/anaconda2/envs/py36/lib/python3.6/site-packages/awesimsoss-0.1.0-py3.6.egg/awesimsoss/files/scaled_spectrum.txt not found.

Issue not present anymore in latest release.


delete request

how can i get the whole entity (like in save request) when i call delete service. i changed deleterequest to saverequest but the entity returns null. i get only entityId.(i also changed it inside service)
thanks

Why you want the Delete return the entity that as been deleted? If you call Delete with ID for entity to delete, you can call first a Retrieve with ID to get the full entity.

when i open a row from grid i use retrieve to get data. if i use update i get the whole entity from save request. Instead of using update i push the deletebutton. so inside the delete service i would like to get the whole entity.

You can create yout own delete action in Endpoint and in Repository with personal Request and Retrive. Some like
[HttpPost]
public MyDeleteResponse MyDelete(IUnitOfWork uow, MyDeleteRequest request)
{
    return new MyRepository().MyDelete(uow, request);
}


Specify ava version to avoid crashing of test.js + update isNaN function to match with ECMA262 specification

I have:

Specified ava version in package.json's devDependency to avoid crashing of test.js.
Updated test.js to work with<EMAIL_ADDRESS>Updated isNaN implementation to match as specified by ECMA262 specification.

Thanks, but don't change the code style.

@sindresorhus  do you mean, one should skip checking the typeof the variable?
If that is so, I think it may not be a good idea.  ECMA262 specifies the procedure, and it is possible, in future a new feature is added which requires the function to adhere to the procedure they mentioned.  That would break the idea of ponyfill at the first place.

No, I'm talking the quote and other style changes.

Ah, I should have disabled Prettier for this file.

Updated.


WEBAPP-202: Remove the scrolling to the search input on LandingPage

This pull request belongs to an issue on our bugtracker.
You can find it there by looking for an issue with the key which is mentioned in the title of this pull request.
It starts with the keyword WEBAPP.

I think this can be merged, right?


Tool for capturing query parameters as if they were string interpolations

I've recently written a macro tool for conveniently capturing query parameters as part of a private project. I've found it handy, so I wondered whether people would be interested in having this as part of LibPQ. Or if not, whether you have suggestions for a better home for it.
The general idea is that we should be able to build up queries by pasting together fragments of SQL and interpolated parameters like one might do with strings or Cmd backtick interpolation. But with all interpolations turned into SQL parameters for safety and consistency in converting those to SQL types.
To just paste the readme in here:
The readme
The main thing provided here is the @query macro to allow queries to be
constructed by normal-looking string interpolation but without danger of SQL
injection attacks.
Note that @query does not parse or understand the SQL source text as this
would be a lot of work. Instead, it keeps any literal SQL text you write as-is
and only treats the Julia-level string interpolations specially.
Use runquery to execute queries generated by @query.
Simple usage
Creating a table and inserting some values
conn = LibPQ.connection(your_connection_string)

runquery(conn, @query "create table foo (email text, userid integer)")

for (email,id) in [<EMAIL_ADDRESS>1)
<EMAIL_ADDRESS>  2)]
    runquery(conn, @query "insert into foo values ($email, $id)")
end

Thence:
julia> runquery(conn, @query "select * from foo") |> DataFrame
2×2 DataFrame
 Row │ email              userid
     │ String?            Int32?
─────┼───────────────────────────
   1 │<EMAIL_ADDRESS>     1
   2 │<EMAIL_ADDRESS>       2

Howto: Inserting values from a Julia array into a row
In some circumstances it can be useful to use splatting syntax to interpolate a
Julia collection into a comma-separated list of values. Generally simple scalar
parameters should be preferred for simplicity, but splatting can be useful on
occasion:
email_and_id =<EMAIL_ADDRESS>3)
runquery(conn, @query "insert into foo values ($(email_and_id...))")

Howto: Using the in operator with a Julia collection
There's two ways to do this. First, using in and splatting syntax
julia> ids = (1,2)
       runquery(conn, @query "select * from foo where userid in ($(ids...))") |> DataFrame
       2×2 DataFrame
        Row │ email              userid
            │ String?            Int32?
       ─────┼───────────────────────────
          1 │<EMAIL_ADDRESS>     1
          2 │<EMAIL_ADDRESS>       2

Second, using the SQL any operator and simply passing a single SQL array parameter:
julia> ids = [1,2]
       runquery(conn, @query "select * from foo where userid = any($ids)") |> DataFrame
       2×2 DataFrame
        Row │ email              userid
            │ String?            Int32?
       ─────┼───────────────────────────
          1 │<EMAIL_ADDRESS>     1
          2 │<EMAIL_ADDRESS>       2

Howto: Building up a query from fragments
conn = LibPQ.connection(your_connection_string)

some_condition = true

x = 100
x = 20
# Example of an optional clauses - use empty @query() to disable it.
and_clause = some_condition ? @query("and y=$y") : @query()

# Interpolation of values produces SQL parameters; interpolating @query
# fragments adds them to the query.
q = @query "select * from table where x=$x $and_clause"
runquery(conn, q)

Okay this is pretty great! And best of all it's optional so if someone's using a database which uses the PostgreSQL wire protocol but not the parameter syntax (i.e., $1, $2) they can just not use the macro.
I'm presuming this functions something like this:
julia> @query "insert into foo values ($(email_and_id...))"
Query("insert into foo values (\$1, \$2)"<EMAIL_ADDRESS>3))

Would this make sense as a string macro?

Okay this is pretty great! And best of all it's optional so if someone's using a database which uses the PostgreSQL wire protocol but not the parameter syntax (i.e., $1, $2) they can just not use the macro.
I'm presuming this functions something like this:
julia> @query "insert into foo values ($(email_and_id...))"
Query("insert into foo values (\$1, \$2)"<EMAIL_ADDRESS>3))

Would this make sense as a string macro?

I'm presuming this functions something like this

Very similar (though the interpolation syntax is constructed lazily — this allows multiple such strings to be pasted together dynamically, as in the "Buliding up a query from fragments" section. (It would also allow non-PostgreSQL parameter syntax to be supported for other connection types.)
julia> email_and_id =<EMAIL_ADDRESS>3)
<EMAIL_ADDRESS>3)

julia> @query "insert into foo values ($(email_and_id...))"
insert into foo values ($1,$2)
  $1 =<EMAIL_ADDRESS>  $2 = 3

julia> dump(@query "insert into foo values ($(email_and_id...))")
JHubDbUtils.SafeQuery
  args: Array{Any}((5,))
    1: QueryFragment
      fragment: String "insert into foo values ("
    2: String<EMAIL_ADDRESS>    3: QueryFragment
      fragment: String ","
    4: Int64 3
    5: QueryFragment
      fragment: String ")"

Would this make sense as a string macro?

Yes I tried this, but I found it has a big downside: interpolations aren't syntax-highlighted. In practice I felt this quite outweighed the benefits of a string macro for visually parsing complex queries. (The benefits of a string macro being a separate namespace and no need for parentheses in larger expressions with trailing parts.)

I'm presuming this functions something like this

Very similar (though the interpolation syntax is constructed lazily — this allows multiple such strings to be pasted together dynamically, as in the "Buliding up a query from fragments" section. (It would also allow non-PostgreSQL parameter syntax to be supported for other connection types.)
julia> email_and_id =<EMAIL_ADDRESS>3)
<EMAIL_ADDRESS>3)

julia> @query "insert into foo values ($(email_and_id...))"
insert into foo values ($1,$2)
  $1 =<EMAIL_ADDRESS>  $2 = 3

julia> dump(@query "insert into foo values ($(email_and_id...))")
JHubDbUtils.SafeQuery
  args: Array{Any}((5,))
    1: QueryFragment
      fragment: String "insert into foo values ("
    2: String<EMAIL_ADDRESS>    3: QueryFragment
      fragment: String ","
    4: Int64 3
    5: QueryFragment
      fragment: String ")"

Would this make sense as a string macro?

Yes I tried this, but I found it has a big downside: interpolations aren't syntax-highlighted. In practice I felt this quite outweighed the benefits of a string macro for visually parsing complex queries. (The benefits of a string macro being a separate namespace and no need for parentheses in larger expressions with trailing parts.)

By the way, I found it helpful to add a runquery function which was separate from LibPQ.execute() and only accepted SafeQuery in an effort to discourage use of string interpolation in constructing queries. I'm not sure how this would make sense if we had @query in LibPQ itself; maybe it's something application authors could decide to do separately from LibPQ.
By the way, regarding naming I'm not married to using @query; we could call this @sql or @psql, or something else if it made sense. Some people might find it annoying if this clashed with, eg, Query.@query though that's not an issue for me personally.
In the end, @query is really just a way of capturing interpolations for processing later. Actually it's somewhat similar to an old PR in Julia Base https://github.com/JuliaLang/julia/pull/33711/files#diff-281780f4de49ab611364d45135bc3d40067c69924b7548e5e73cfec655fb356a.  So another option might be to start a new package — LazyStrings, or some such.

By the way, I found it helpful to add a runquery function which was separate from LibPQ.execute() and only accepted SafeQuery in an effort to discourage use of string interpolation in constructing queries. I'm not sure how this would make sense if we had @query in LibPQ itself; maybe it's something application authors could decide to do separately from LibPQ.
By the way, regarding naming I'm not married to using @query; we could call this @sql or @psql, or something else if it made sense. Some people might find it annoying if this clashed with, eg, Query.@query though that's not an issue for me personally.
In the end, @query is really just a way of capturing interpolations for processing later. Actually it's somewhat similar to an old PR in Julia Base https://github.com/JuliaLang/julia/pull/33711/files#diff-281780f4de49ab611364d45135bc3d40067c69924b7548e5e73cfec655fb356a.  So another option might be to start a new package — LazyStrings, or some such.

Yes I tried this, but I found it has a big downside: interpolations aren't syntax-highlighted. In practice I felt this quite outweighed the benefits of a string macro for visually parsing complex queries. (The benefits of a string macro being a separate namespace and no need for parentheses in larger expressions with trailing parts.)

If it was a string macro you could choose to use the @macro_str form if you wanted, whereas it doesn't work the other way around.
The laziness actually presents a nice argument for this being a generic separate package, since the same syntax could be used for many different database systems.

Yes I tried this, but I found it has a big downside: interpolations aren't syntax-highlighted. In practice I felt this quite outweighed the benefits of a string macro for visually parsing complex queries. (The benefits of a string macro being a separate namespace and no need for parentheses in larger expressions with trailing parts.)

If it was a string macro you could choose to use the @macro_str form if you wanted, whereas it doesn't work the other way around.
The laziness actually presents a nice argument for this being a generic separate package, since the same syntax could be used for many different database systems.

The laziness actually presents a nice argument for this being a generic separate package, since the same syntax could be used for many different database systems.

Yes that's a good point. I've taken a stab at refactoring this a bit and put the code into a new package SqlStrings.jl. I'll probably register a first version of this shortly:
https://github.com/JuliaComputing/SqlStrings.jl

If it was a string macro you could choose to use the @macro_str form if you wanted, whereas it doesn't work the other way around.

In SqlStrings, I've made it @sql_cmd because:

It's important to have syntax highlighting for interpolations, but editors typically disable this within normal string macros.
@sql_cmd is very conceptually similar to the builtin backticks and Base.Cmd: it's a lightweight layer which deals only with preserving the structure of tokens in the source text.

At the moment it requires a small amount of glue code to integrate with LibPQ, but it would be great to make that unnecessary.
I'm not 100% sure of the best way forward for integration. We could make SqlStrings a dependency of LibPQ and make LibPQ.execute optionally take an SqlString?
A longer term goal might be to make the publicly exported execute() not take a normal string which would heavily discourage people from using plain string interpolation to construct queries. But obviously that would be quite breaking. Thoughts?


Update Ubuntu installation instructions

The basics are the same, I just incremented some version numbers so it's easy for people to get a hold of 27.1 on Ubuntu.

Hi! Thanks for the PR, but I'm afraid I must refuse it because it comes at a bad time: getting_started.org (and other org files in docs/) is undergoing a rewrite at the moment. The versions in the Ubuntu section have been bumped and expanded (and includes the modifications in this PR). Until this is complete I am not accepting PRs to our docs. Sorry for the trouble!

No worries, just glad the instructions will be updated. Thanks!


Small bugfixes, behavior changes on clicking buttons, some security, …

…and initial work on organizing hikes

Redirects if trying to organize hike as not the user logged in
Some html/css changes throughout
Redirects to login for creating trails and organizing hikes if not logged in
Unfinished organize hike page at the moment

Oh boy quite a bit of changes:

Fixed bug with messages giving heap error
Profile picture changes and saves
Added user profile data to datastore
Changed a bit of html/css


Updated README.md for QEMU pre-reqs on Ubuntu Linux

$ uname -a
Linux ubuntu 5.0.0-27-generic #28-Ubuntu SMP Tue Aug 20 19:53:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Hey @janitha09 -- thanks for your PR! Can you please take care of signing all your commits by adding -s to git commit and also take care of the following feedback provided by our static checker:
https://3067-182198941-gh.circle-artifacts.com/0/tmp/yetus-out/diff-patch-markdownlint.txt


Non-Serializable Errors in Redux Store for DateTime Values

Looks like when we process the dataView and take in date/time values, we bring in the entire object, which is bad for Redux, e.g.:

We should type check these and store the raw value, which will be better for Redux.

This was an issue exposed when attempting something else, so we can ignore for now.


IPeriodList does not include TzId during serialization

[Test]
public void NoTzIdInPeriodListSerialization()
{
    var somePeriod = new Period(new CalDateTime(_nowTime, _tzid), new CalDateTime(_later, _tzid));
    var periodList = new PeriodList {somePeriod};
    periodList.TzId = _tzid;
    var someEvent = new Event
    {
        DtStart = new CalDateTime(_nowTime, _tzid),
        DtEnd = new CalDateTime(_later, _tzid),
        ExceptionDates = new List<IPeriodList> {periodList}
    };

    var calendar = new Calendar();
    calendar.Events.Add(someEvent);
    var serialized = SerializeToString(calendar);
    Assert.IsTrue(serialized.Contains("EXDATE;TZID=Eastern Standard Time:"));
}

Output is:
BEGIN:VCALENDAR
PRODID:-//github.com/rianjs/ical.net//NONSGML ical.net 2.2//EN
VERSION:2.0
BEGIN:VEVENT
DTEND;TZID=America/New_York:20160912T183326
DTSTAMP:20160912T213326Z
DTSTART;TZID=America/New_York:20160912T173326
EXDATE:20160912T173326/PT1H
SEQUENCE:0
UID:e2944545-37fe-47d9-bb74-19c134128023
END:VEVENT
END:VCALENDAR

EXDATE really should be EXDATE;TZID=Eastern Standard Time:20160912T173326 (I think?)

After a long debugging session, we were stumbling over this issue.
If the server does not run in the same TZ as the event, effectively the EXDATEs are ignored, e.g., assume the server runs in UTC and we are using TZ of Europe/Berlin (UTC+0100):
This does not work:
BEGIN:VEVENT
DTEND;TZID=Europe/Berlin:20170117T171000
DTSTART;TZID=Europe/Berlin:20170117T164000
EXDATE:20170124T164000
RRULE:FREQ=WEEKLY
SEQUENCE:0
UID:45878d4d-ebe7-e72b-9ffd-22a7ac617444
END:VEVENT

This does work when deserializing (with 2.2.28) (note the different EXDATE definition).
BEGIN:VEVENT
DTEND;TZID=Europe/Berlin:20170117T171000
DTSTART;TZID=Europe/Berlin:20170117T164000
EXDATE;TZID=Europe/Berlin::20170124T164000
RRULE:FREQ=WEEKLY
SEQUENCE:0
UID:45878d4d-ebe7-e72b-9ffd-22a7ac617444
END:VEVENT

Yeah, I think time zones are an area of weakness for ical.net, but they're more important that ever. When dday.ical was written (which is what ical.net has evolved from), it was the mid 2000s, and client-server scenarios weren't as prevalent as they are now.
Now everything's a service (or a client of a service), and these shortcomings are going to become more painful.

Yes the timezone issues are our showstopper to migrate from dday.ical for outlookcaldavsynchronizer.
The code is painful slow compared to ical.net there but at least the VTIMEZONE serializer works more or less.

I would love a PR that fixes it. :)
I improve ical.net as part of my day job--that's really the only way improvements get made--and I'm pretty liberal in who I give commit rights to. So open a reasonable PR, and I'll leave feedback, and then probably just give you commit rights.

I will if time permits, but since the vcard library we use has even more problems and is abandoned as well, I started forking and improving that first :)

I completely understand. :)
I recently added a "get occurrence" endpoint to a REST service here at work. No one is using it yet, but as soon as they start, this will become a higher priority I'm sure. :)

@aluxnimm - nuget version 2.2.34 should include the fix for PeriodLists.
Note that you should explicitly set the TzId on the PeriodList itself. The serialization is a little backward in that while CalDateTime's do indeed have a time zone, there are no correctness guarantees regarding the time zones of child CalDateTimes in your PeriodList. You'll have to enforce this in the application layer.
Example:
[Test]
public void ExDateTimeZone_Tests()
{
    const string tzid = "Europe/Stockholm";

    //Repeat daily for 10 days
    var rrule = new RecurrencePattern(FrequencyType.Daily, 1) { Count = 10 };

    var e = new CalendarEvent
    {
        DtStart = new CalDateTime(_now, tzid),
        DtEnd = new CalDateTime(_later, tzid),
        RecurrenceRules = new List<RecurrencePattern> { rrule },
    };

    var exceptionDateList = new PeriodList { TzId = tzid };
    exceptionDateList.Add(new Period(new CalDateTime(_now.AddDays(1))));
    e.ExceptionDates.Add(exceptionDateList);

    var serialized = SerializeToString(e);
    const string expected = "TZID=Europe/Stockholm";
    Assert.AreEqual(3, Regex.Matches(serialized, expected).Count);

    e.ExceptionDates.First().Add(new Period(new CalDateTime(_now.AddDays(2))));
    serialized = SerializeToString(e);
    Assert.AreEqual(3, Regex.Matches(serialized, expected).Count);
}

In a perfect world, you could do something like:
var time = DateTime.Parse("2017-04-06T14:09:55");
foo.Events.RecurrenceDates.Add(new Period(new CalDateTime(time, "America/New_York")))`;
foo.Events.RecurrenceDates.Add(new Period(new CalDateTime(time, "Europe/Stockholm")));

...and the library would create two separate PeriodLists, and make sure that each time zone is kept separately. But we're not there yet.

Thanks for the update and great work! Hopefully, we can migrate soon. Any news on the VTIMEZONE serializing by chance?

No, we don't use it at work, so I'm unlikely to get to it within a reasonable timeframe. (My main non-work priority is getting the .NET Core version working.)

Fixed in nuget version 4.0.0: https://www.nuget.org/packages/Ical.Net/4.0.0


feat: updated with package @fagbokforlaget/edtech-interfaces to use c…

feat: updated with package @fagbokforlaget/edtech-interfaces to use common interfaces

@espresse I am confused why would we use a private package in a public package?

@iapain yes, I'm also confused about that.

we cannot add private packages to our public ones


[CELEBORN-630] Binary release artifact should package all versions of Spark and Flink clients

…link version

What changes were proposed in this pull request?
Why are the changes needed?
Does this PR introduce any user-facing change?
How was this patch tested?

Thanks, merge to main/0.3


Blog posts - switch Comments and Read similar posts sections

@rubyrat can you clarify, do we want:

comments above the similar posts, or
similar posts above comments

This is the code that needs to be moved: https://github.com/verifa/website/blob/2996f0d3149df1f665c01c941f2cfd0f7d9fae53/src/lib/posts/layout.svelte#L82

@rubyrat can you clarify, do we want:

comments above the similar posts, or
similar posts above comments

similar posts above comments


FeatureFormView - Update example usage

[x] Update FeatureFormTestView.swift
[x] Update tutorial steps

Are you going to update the Tutorials with this PR? I see a checkbox for it in the description.

Yes, meant for this to be a draft. Changes coming shortly.

Okay ready to go now, sorry about that!


Ldap support for traefik dashboard

Please is there any integration to make possible to use ldap authentication for traefik dashboard ?

Dup of https://github.com/containous/traefik/issues/498


use SGVector instead of plain pointer in GMM

During I'm working on the global random removing, I found we have a lot of plain pointer in GMM. I thought maybe we want this pr, please feel free to close it if it's not. :)
Thank you

@MikeLing if you wanna insist on these changes then let's switch as well all the CMath methods and other SGVector/SGMatrix methods to linalg plz! :) lemme know if you need help there which one and how!

Hi @vigsterkr , sure,  please tell me more about that! But I'm not sure I could start to work on it right away, let me finish these issues on my hand first :)
BTW, update this pr due to I found I forget to remove some debug statement in the pr :P

@MikeLing i dont see the point of doing halfway things in this case. if you started this then plz do it properly if not then close this PR. the change of Malloc to SGVector is really not enough here... that can be done with a regex script automatically...

Once this is done (very nice initiative), let's re-design the Gaussians and mixture models a bit. I can help with that, let me know once you are ready with this stuff

Hi @vigsterkr, I misapprehend your comment. I thought you are saying we need to add more mathematic function in SGVector and SGMatrix :P  Had update the pr, plz tell me if there are anything else to do in this pr. Thank you

@MikeLing ok there are some debug stuff that should be removed, otherwise it's looking good. once those debug things are removed and some of those minor problems address we should merge this... later as @karlnapf mentioned we might wanna do a refactor and then get rid of that lapack dependency...

@MikeLing my only concern is that GMM is tested nowhere automatically only in a notebook :S

mmm, do i need to add some unit test for it? Or we could test and merge it after micmn add unit test for GMM?

@MikeLing i'm not aware of anybody planning to add unit test for GMM ;)
one easy way that you manually try to run the ipython notebook locally and check if it's the same output as here: http://shogun.ml/notebook/latest/GMM.html

@vigsterkr oh, I see what you mean. We do have meta test for GMM( integration_meta_cpp-clustering-gmm ) actually, but I'm not sure if that's good enough to test it. Let me test gmm on notebook anyway :)

@MikeLing oh yeah that's should at least as well assure that we are still having the same output :)))

@MikeLing ok lemme know when you've done with the notebook test as this seems to be ok so i'm gonna merge once you are done with double-checking.thnx

@vigsterkr Hi, sorry for the late reply. So, first of all, I would say "yes, we are still having the same output for GMM." But, however, the GMM notebook may broken already. I send you some screenshots on irc already. (here is the output of develop branch

#3866

let's re-design the Gaussians and mixture models a bit
Hi @karlnapf , even this haven't been merged yet, could you tell me something about Gaussian and mixture models' redesign? Thank you!

Hi @MikeLing
Let me know when you are done with the clean-up and I can help you re-designing the class.

ask review for this pr :)

Mmmh the unit test thing is quite concerning ....
I think for simple re-factoring, we can merge without having tests, but generally, we should add some
notebook checks:

visually works
unit tests:
compare with sklearn on a simple toy example with the same initialization as sklearn and only single iterations
domain/math tests
free energy increases in every iteration of EM (this is a really good sanity check)
all probability vectors always sum to 1 (logsumexp is 0)
when initialized with a good solution, it doesnt jump around but convergence quickly to the same solution as initialized

@karlnapf this has nothing to do with the new random.

Ah ok.
So this test then must not change integration test results ....

travis seems ok.
i think we can risk it then if we do a visual check ....

@MikeLing can we please finish up this one by friday? what is missing is couple of matrix multiplications instead of using for loops... ping me if you need help, plz! just let's have this finally merged!


SHIP-0006: Add SHIP for BuildRun Status Results

This SHIP provides a proposal on how to surface Tekton Task Results into the BuildRun Status subresource.
It proposes three types of new fields under the .status subresource, these being:

.status.results
.status.sources
.status.output

@imjasonh @SaschaSchwarze0 this one is ready for review, fyi

@qu1queee I merged your PR that brought in the old enhancement proposals. Please update the title and numbering to SHIP-0022 so we don't have collisions. Thanks!

I´m closing this one as I cannot provide updates here for the next upcoming weeks. @SaschaSchwarze0 you might wanna re-open with a cherry-pick and changes on top. @HeavyWombat fyi.


.gitlab-ci.yml: Switch to new runner on sonoma

[ ] ReportGenerator step fails, see https://gitlab.byte-physics.de:4001/mirror/igortest/-/jobs/115314

@Garados007 Still the same error, see https://gitlab.byte-physics.de:4001/mirror/igortest/-/jobs/115650.

I logged into the CI machine to have access to the docker image (it would take ages to download the image) and found the issue. I am working on a solution.

I logged into the CI machine to have access to the docker image (it would take ages to download the image) and found the issue. I am working on a solution.

Nice. Sure, do log in. We have it exactly for this.

Restarted CI.

@Garados007 ✨

Well looks like automation killed your idea. But I do think this is good to go anyway.


[Request] Decrease the bundle size

Current Behavior
@transifex/native increases bundle size significantly when added as a dependency. Bundlephobia says it's 135.7kb minified and 43.2kb minified/gzipped, which is in line with what we're seeing in our bundles. This is larger than react and react-dom combined, which is fairly ridiculous.
Expected Behavior
@transifex/native should ideally be more like 30-40kb minified.
Steps to Reproduce
Add @transifex/native as a dependency and bundle your application.
Possible Solution
I have four suggestions that could improve the situation. Two of these could be considered breaking changes and would require a major version bump, but would not necessarily be difficult upgrades for people to make. I've noted which ones below.
The general themes of these suggestions are:

Stop targeting very old browsers and Node versions
Give the application bundler more control over how this package and dependencies are handled

If any of these suggestions are interesting, we could split them out into separate issues. I'd also be willing to help with some of them.
Transpile Fewer Features
This would be a breaking change.
Currently all the packages in this repo use @babel/preset-env with defaults, which targets extremely old browsers, and thus has to emit quite a bit more code during transpilation.
I can't speak for all users of these packages, but we would be totally fine targeting ES2018+, removing the need to transpile most or possibly even all the code in @transifex/native. All major browsers have supported these features for nearly 4 years.
@messageformat/core already uses the browserlist query:
> 0.5%, last 2 versions, Firefox ESR, not dead

This is equivalent to browserlists' defaults and seems like a reasonable starting point.
People who care about older browsers still have the option of transpiling dependencies.
If I remove babel-loader from the browser Webpack config, the browser bundle goes from 136kb to 119kb.
Ship an ES Module Bundle
This would not need to be a breaking change, since it could be additive.
Browsers commonly support ES modules, and modern bundlers like Rollup and Webpack prefer working with ES modules. ES modules allow for easier size optimization through tree-shaking.
For people who care about older environments, you could continue shipping a UMD or CommonJS bundle alongside the ES module one.
If I enable experiment module output in Webpack and set output.library.type to 'module', the browser bundle actually increases slightly from 119kb to 120kb. I'm hopeful that we could make up for this in the final application with tree-shaking.
Remove Axios
This would be a breaking change.
The fetch API is widely supported in browsers and in all current versions of Node. It should provide functionality to replace Axios, which is 11.6kb minified/gzipped -- roughly a quarter of @transifex/native's size.
For people who care about older environments, you could provide a way to pass in a fetch function. They could then choose to pull in a fetch polyfill and pass that in.
If I remove Axios and replace it with fetch, the browser bundle goes from 120kb down to 91kb.
Treat Dependencies as External
This would not need to be a breaking change (IMO).
@transifex/native bundles its dependencies, but also lists them inside package.json under dependencies, which is redundant since they aren't actually needed at runtime. It should either:

Not bundle dependencies and mark them as external in Webpack
Bundle dependencies, but list them under devDependencies

I would prefer the first. That would:

Allow me to make minor/patch updates to those dependencies without updating @transifex/native itself
Give me more control over how they're bundle and transpiled
Allow combining them with other packages that might have common dependencies. (This would be the case with md5, which would save us 2.2kb minified/gzipped. Not huge, but I'll take free savings if I can get it.)

I can see there's further room for improvement in @messageformat/core, but I can take that up with that project if we can get started on some of the improvements here.

Hey @edsrzf, those are some nice suggestions and we would appreciate your help.
For starters, I have created this PR: https://github.com/transifex/transifex-javascript/pull/204 that addresses the following and is reducing the bundle size for the browser version by around 40K minified:

Added the proposed browserslist query
Replaced axios with cross-fetch

For the latter, native fetch support is introduced in NodeJS 17+, so using cross-fetch looks like a safer path, so that we can support older Node versions as well.

Thanks! cross-fetch is definitely an improvement!
For the next major release, I'd note that the oldest currently-supported version of Node is 18, and so it shouldn't be much of a leap for most to use native fetch. (Though technically fetch is marked as unstable until Node 21, so I guess you could wait wait a few years if you're worried about that.) I still think exposing a way to optionally pass a fetch implementation gives the best of both worlds.

First batch of optimizations have been released on<EMAIL_ADDRESS>

Given the fact Node 16 is now well past End of Life (https://nodejs.org/en/blog/announcements/nodejs16-eol), can you bump the Node version from 16 to 18 as the minimum, and drop cross-fetch in favour of fetch?
That would provide another sizeable decrease in bundle size.


Pull Request #1018 stuck on validate step.

My pull request is stalled waiting for status on validate step.  Can you please tell me what I'm missing?

I was able to resolve the issue


how to load a local pdb file?

this might be a very basic question. but I tried replacing builder.download with builder.parse_file, but doesn't work.
Thanks.

Hi @luwei0917,
the builder only supports .download() and can't make use of local files. Your structure data must be publicly available via some URL. That's the only way for the specification to work when shared with other people who won't have access to your local file.
Hope that helps,
Sebastian


Samsung keyboard composing region duplication on subset of devices

Extracted/continued from https://github.com/flutter/flutter/issues/31512
When typing, hiding and reshowing the keyboard and typing punctuation like . can cause the composing region to duplicate.
The original issue linked above impacted most Samsung devices. Since then, changes have landed that workaround the issue for most devices (https://github.com/flutter/engine/pull/16547 and https://github.com/flutter/engine/pull/15701). These workarounds have been confirmed to work on most devices.
However, it seems that a much smaller subset of devices are still seeing this bug even with the workaround, some with additional minor regressions in the form of the first letter sometimes repeating.
Devices confirmed to still exhibit the bug:

Galaxy Tab A 10.1" SM-T510

Devices that may have the bug in some form:

Galaxy S8 (based off report by @exptk3)
J6+

We have been in contact with Samsung to work on resolving this. See b/150639528
Please continue to report any specific models that are still experiencing the bug!

Hello,
I'm running a Samsung Tab S6 (SM T865) and i'm still running into text duplication issues. This issue occur to me when i'm trying to write down an email. Bellow you will be able to see a gif of the actual behavior :

This issue is really problematic as it is impossible to production deploy any app as samsung devices are very popular.
Flutter doctor Output :
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, v1.15.19-pre.9, on Mac OS X 10.15.3 19D76, locale en-FR)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 11.3.1)
[!] Android Studio (version 3.5)
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
[!] IntelliJ IDEA Ultimate Edition (version 2019.3.3)
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
[✓] VS Code (version 1.42.1)
[✓] Connected device (1 available)

! Doctor found issues in 2 categories.

Thank you and i hope we will find a fix soon

@GaryQian

The Samsung Fold has the Problem too.

As a partial workaround just install Gboard on yoiry device and the problem will be fixed as the issue is just coming from the keyboard and not the os itself

@MichelMelhem Unfortunately, "installing a different keyboard" is not a solution to this. The problem in itself is that Samsung keyboards specifically are not working, and switching keyboards doesn't solve the problem for anyone other than one single end user. Thanks for the additional reports! Will be useful in continued work tackling this problem!

I can confirm still happening on Galaxy Tab A (SM-T380) with Flutter version 1.12.13+hotfix.8

I can confirm still happening on J6 with Flutter version 1.12.13+hotfix.8

Samsung S9, S9+ has same problem. I tested it on device.
Flutter version is 1.15.19-pre33

I reproduced this with Samsung Galaxy S8 on Flutter Stable: 1.12.13+hotfix.8

Is there any update on the way to fix this issue ???

Facing similar issue on GalaxyS10e android 10.

It seems that it happens more often while typing email.

I have landed https://github.com/flutter/engine/pull/17426 which seems to fix many of the bugs on my test devices. It would be great if others could confirm that this also fixes bugs for them.
Please try the change on master channel after it has rolled into the engine (it has not yet, I will update this comment when the change does roll in and is ready for testing).

I just tried and it is fixed for me. Thank you!
Is it safe to switch to master channel for an app in production?

We don't recommend it as there may be major bugs that we still have not caught, but every few days we roll to dev channel, which is still not recommended, but quite a bit safer than master. However, the final decision is still up to you to determine how important certain bugfixes are to include and which channel to use. As a rule of thumb, we try our best to keep master channel usable, and that succeeds a lot of the time, but there is no guarantee.

@GaryQian Thank you!

[ Test divice : Galaxy s8 ]
[ Test sdk : Flutter Master Channel ]
*** Problems found in the last test

Time delay of the keyboard up and down
abnormal display of the keyboard even after the app is closed (on device home screen)
word duplication input
input line can not be changed during keyboard input

*** I tested it on the same device (Galaxy s8) as in the last bug report.
—> This time, during the test, the above problems were confirmed.
—> Results of test
3, 4 : resolved.
1,2 : not resolved.
The duplicate input problem, which was a major problem, did not appear, but the time delay occurred when the keyboard was hidden or visible.
It seems that there is no delay time at the beginning of input, but if it is more than 3 ~ 4 lines of text input, the longer the sentence, the longer the delay time.
--> The delay time increases by more than 10 seconds, the performance is difficult to use in a real app.
I hope you reproduce the above bugs on your Galaxy s8 device.
================================================
*** Log when Keyboard up
…
W/IInputConnectionWrapper(27651): getExtractedText on inactive InputConnection
W/IInputConnectionWrapper(27651): getExtractedText on inactive InputConnection
W/IInputConnectionWrapper(27651): getExtractedText on inactive InputConnection
So many times
…
*** Log when Keyboard down
D/ViewRootImpl@b02d8a6MainActivity: ViewPostIme pointer 0
D/ViewRootImpl@b02d8a6MainActivity: ViewPostIme pointer 1
D/InputMethodManager(27651): HSIFW - flag : 0 Pid : 27651
==================================================
Thank you.

I will close this for now, if anyone still sees this bug, please let me know and we can reopen this!
Thanks everyone for the patience given for this quite longstanding issue and the assistance provided in resolving it!

@GaryQian Thanks for all the hard work on this. Do you plan on looking into the 2 remaining issues @exptk3 mentioned in their post above? Is there a separate bug logged for that?
Thanks

@GaryQian Great work! As mentioned by @dannyvalentesonos, there are two remaining issues.
Especially, I also confirmed "Time delay of the keyboard up and down" issue.
I tested more than 5 devices, It happened on only Galaxy Note 10, not Galaxy 9&9plus, iPhone X etc.
so I don't know whether it is flutter issue or device issue.

I'll go ahead and open a separate issue if one doesn't already exist. Those symptoms seem separate from the primary problems tracked in this bug.

@TykanN "Time delay of the keyboard up and down" issue happens on Galaxy 9 Plus as well.
@GaryQian I am using 1.15.17 and the keyboard is almost not usuable in production due to delay. This issue never happened on 1.12.8.

https://github.com/flutter/flutter/issues/54310 Is the new bug I filed for the remaining issues mentioned


pgrep: Add command pgrep

fix #94

regex is too slow, need to write algorithm for parsing /proc/self/stat
cargo run --release -p uu_pgrep -- -n  17.00s user 0.73s system 107% cpu 16.563 total

after rewrite algorithm
./pgrep -o  0.04s user 0.05s system 98% cpu 0.092 total
./pgrep -n  0.04s user 0.05s system 98% cpu 0.089 total

for benchmarking, you should use hyperfine :)

I came up with a better idea, I think make the handle_* method just collect the required pid and let the uumain method decide the output format based on the flag, the code will be more understandable and concise than before.

codecov shows that some stuff could be tested :)
see:
https://github.com/uutils/procps/pull/95/files

The pgrep command is implemented as far as I can understand it, can I see what else needs to be improved?

Good work :)


Increase encapsulation of UniquePersonList

It's a bit odd to have a getInternalList() method. On the surface it looks like a violation of encapsulation. To be investigated further.

It's there because javafx methods require ObservableLists, we can make ``UniquePersonList` itself implement that interface but that will be a lot of additional boilerplate code for the class. Thoughts?

I see. Perhaps rename the method to avoid the word internal? getObservableList()?

.asObservableList and probably we can use the UnmodifiableObservableList as the return type


ffmpeg-qsv:Add 8/10bit VVC decode test

check failures caused by upstream regression, not this pr.


SOLR-16442: upgrade to Lucene 9.4 (do and document)

https://issues.apache.org/jira/browse/SOLR-16442
Collaboration welcome e.g. open questions:

[X] what to do about the sortMissingLast logic in the SortableBinaryField class?
[ ] what documentation needs changes for a Lucene dependency upgrade?
[X] in SchemaCodecFactory lucene93 vs. lucene94 use?
[X] properly read https://lucene.apache.org/core/9_4_0/MIGRATE.html

LGTM. One thought on the docs, would it make sense to reference back to this PR and SOLR-16442 for the next person to see an example? For repetitive tasks, it's great to have a nice model to follow that shows all the types of changes required....

I'd broken up the change into distinctive commits with that sort of use and potentially review ease in mind.
In terms of explicitly referencing back to the PR and/or JIRA issue, I'm not so convinced on that for two reasons:

ideally the documentation should mention all that needs doing i.e. for the upgrade to be done based on documentation rather than past example(s)
it might be off-putting or restrictive to see 13 commits i.e. working through a documented list incrementally is one thing but perceiving that things should be done in separate commits might not be everyone's cup-of-tea


Website link not working

Same in Chrome

Found the problem..

Reported to F-Secure about false positive

Thanks!

Thanks a lot for your time and effort to get this approved, @theel0ja!


disable the codecov check on the global coverage

For future reference, settings on commit status are described here: https://docs.codecov.io/docs/commit-status


Add Extension Target for Reorder Flow

Background
Fix #122087
This PR adds the reorder target in the ui-extensions directory.
Checklist

[ ] I have :tophat:'d these changes
[ ] I have updated relevant documentation

Requesting another set of reviews as I noticed the extension-targets file moved since I last put up this PR, so I'd like to make sure the files (including the .changeset is still valid before merging. Thanks!


Export to Modrinth modpack format

Modrinth modpack support is very near. Despite not being on production yet, there should probably still be an option to export to the Modrinth pack format in anticipation :)
https://github.com/modrinth/labrinth/wiki/Modpack-Format

Similarly to #28, a way to publish modpacks directly to Modrinth would be nice.


Update readme with Jetstream

Update the readme and examples.md for Jetstream.
Signed-off-by: Colin Sullivan<EMAIL_ADDRESS>

Thanks Wally!


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_68q2dp663y/clone/recipe/meta.yaml:20: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_68q2dp663y/clone/recipe/meta.yaml:26: missing_pip_check: For pypi packages, pip check should be present in the test commands
ERROR: /tmp/abs_68q2dp663y/clone/recipe/meta.yaml:30: incorrect_license: The recipe's about/license key is not an SPDX compliant license or license exception, reference https://spdx.org/licenses/
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_8d4ektg69j/clone/recipe/meta.yaml:20: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_8d4ektg69j/clone/recipe/meta.yaml:26: missing_pip_check: For pypi packages, pip check should be present in the test commands
ERROR: /tmp/abs_8d4ektg69j/clone/recipe/meta.yaml:30: incorrect_license: The recipe's about/license key is not an SPDX compliant license or license exception, reference https://spdx.org/licenses/
Errors were found


disk_partitioner system installation implementation

Merging this, not fully tested (waiting for hardware) but will clean up later as needed.


Update README to include steps used in build to prevent blank workflow in dev mode

Resolves #856

Came across this problem when running st2web during development process, updated README as per the information suggested in #856.

I don't know much about lerna. If that's what needs to happen then cool. Bring on the docs!

Nor do I - but its exactly what we do when we do the build process and it definitely solved my problem!


Request panel scroll position moves to bottom of request folder when sending or editing requests

Expected Behavior
The scroll position should not move on the request panel unless I scroll
Actual Behavior
The scroll position appears to move to the bottom of the open folder the request is in

Reproduction Steps

Select a request from the side panel
Hit send or edit the request

Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
This appears to be the sames as this issue but for HTTP requests
https://github.com/Kong/insomnia/issues/7606
Insomnia Version
9.3.2
What operating system are you using?
macOS
Operating System Version
macOS Sonoma Version 14.5 (23F79)
Installation method
download
Last Known Working Insomnia version
9.2 I think

Thanks for the video, this helps a lot. I will sync with the team to see if we can ship this in the upcoming 9.3.3

Hi @JoeyBoolean this is now fixed in the latest beta and will be out on the next patch release.
Thanks for the feedback!

Hi @JoeyBoolean this is now fixed in the latest beta and will be out on the next patch release. Thanks for the feedback!

It works perfectly now. Thanks!


Send true as boolean rather than "true"

Im using this plugin for fileupload, in one case i want to send the file as well as some other fields to server, so i have written like this

 for (var i = $scope.path.length - 1; i >= 0; i--)
                names.push("pictures[" + i + "]");

 Upload.upload({
                url: 'server/uri',
                fields: $scope.files,
                file: $scope.path,
                fileFormDataName: names,
                sendFieldsAs: 'form',
                formDataAppender: function (formData, key, val) {
                    console.log(formData);
                    console.log(key)
                    console.log(val)
                },
            })

where the one key in $scope.files is is_common which has boolean value, but when i inspected it in chrome network it is sending as "true", but my server recieves only the boolean true. is there a way to send the values as boolean true rather than "true"

You don't need the formDataAppender.
Can you create a jsfiddle?

Sorry for late, actually now i dont have resource for making jsfiddle, but i will explain a little bit more,
if the scope object is
$scope.somthing={
  'has_partner':true,
  'physical_location':null
}

when i send this object with Upload service along with file object in server im getting the has_partner as "true" and physical_location as "null",but  when i send this object using $http angular service in server im getting has_partner as true (bool type) and physical_location is null (object null). so this is my problem, can you tell me something why it is happening or want jsfiddle

Duplicate of this: https://github.com/danialfarid/ng-file-upload/issues/904
You can send everything as json and parse it on the server.
That would be the only workaround for now I could think of.


fix: parse left and right when eval failed for logic expr

Fixes #4997
Parsing of left and right expressions should continue even if the evaluation of the logical expression fails.

!canary


Unable to run Mocha Tests

Hello,
I am working to add timespan to Thoth, but I am unable to run Tests from current version 77caf44fe5cdb5a44843224e4588be9087d418d8
when running
fake build -t ExpectoTest
I get
Error is
Starting target 'MochaTest'
Starting task 'DotNet:version': running dotnet --version
D:\DEV\Thoth> "C:\Program Files\dotnet\dotnet.EXE" --version (In: false, Out: true, Err: true)
2.1.402
Finished (Success) 'DotNet:version' in 00:00:00.1600861
D:\DEV\Thoth\tests> "C:\Program Files\dotnet\dotnet.EXE" fable fable-splitter -- -c tests/splitter.config.js (In: false, Out: false, Err: false)
Fable (2.0.11) daemon started on port 65323
CWD: D:\DEV\Thoth
cmd /C "D:\DEV\Thoth\node_modules/.bin/fable-splitter.cmd" -c tests/splitter.config.js
D:\DEV\Thoth\node_modules\fable-splitter\dist\index.js:19
    throw new Error("This version is not compatible with dotnet-fable cli tool, "
    ^

Error: This version is not compatible with dotnet-fable cli tool, see https://www.npmjs.com/package/fable-splitter#usage
    at Object.<anonymous> (D:\DEV\Thoth\node_modules\fable-splitter\dist\index.js:19:11)
    at Module._compile (module.js:653:30)
    at Object.Module._extensions..js (module.js:664:10)
    at Module.load (module.js:566:32)
    at tryModuleLoad (module.js:506:12)
    at Function.Module._load (module.js:498:3)
    at Module.require (module.js:597:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (D:\DEV\Thoth\node_modules\fable-splitter\dist\cli.js:6:17)
    at Module._compile (module.js:653:30)
Closing Fable daemon...
Finished (Failed) 'MochaTest' in 00:00:01.4564324

I able to run tests only from c1bdb4c4f4df4cccc822424bc7bd5ea47deb0f5d

Hello,
will be fixed by https://github.com/MangelMaxime/Thoth/pull/84
You can start your PR from this PR as it approved in principle. I am just waiting to work on the documentation.


Unable to pip install on macos

Similar to #12 , has anyone else run into trouble installing this library on macos?  M1 chip with macos 13.5.1.
I'm trying to my development locally and then actually run on a raspberry pi, but running poetry add rpi-ws281x gives me:
   × Building wheel for rpi-ws281x (pyproject.toml) did not run successfully.
    │ exit code: 1
    ╰─> [20 lines of output]
        running bdist_wheel
        running build
        running build_py
        Compiling ws281x library...
        creating build
        creating build/lib.macosx-13.2-arm64-cpython-311
        creating build/lib.macosx-13.2-arm64-cpython-311/rpi_ws281x
        copying rpi_ws281x/rpi_ws281x.py -> build/lib.macosx-13.2-arm64-cpython-311/rpi_ws281x
        copying rpi_ws281x/__init__.py -> build/lib.macosx-13.2-arm64-cpython-311/rpi_ws281x
        running build_ext
        building '_rpi_ws281x' extension
        creating build/temp.macosx-13.2-arm64-cpython-311
        creating build/temp.macosx-13.2-arm64-cpython-311/lib
        clang -Wsign-compare -Wunreachable-code -DNDEBUG -g -fwrapv -O3 -Wall -I/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include -I/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include -I. -I/Users/ian/Library/Caches/pypoetry/virtualenvs/freenode-led-1BZ2-4XO-py3.11/include -I/Users/ian/.pyenv/versions/3.11.2/include/python3.11 -c lib/dma.c -o build/temp.macosx-13.2-arm64-cpython-311/lib/dma.o
        clang -Wsign-compare -Wunreachable-code -DNDEBUG -g -fwrapv -O3 -Wall -I/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include -I/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include -I. -I/Users/ian/Library/Caches/pypoetry/virtualenvs/freenode-led-1BZ2-4XO-py3.11/include -I/Users/ian/.pyenv/versions/3.11.2/include/python3.11 -c lib/mailbox.c -o build/temp.macosx-13.2-arm64-cpython-311/lib/mailbox.o
        lib/mailbox.c:40:10: fatal error: 'sys/sysmacros.h' file not found
        #include <sys/sysmacros.h>
                 ^~~~~~~~~~~~~~~~~
        1 error generated.
        error: command '/usr/bin/clang' failed with exit code 1
        [end of output]

    note: This error originates from a subprocess, and is likely not a problem with pip.
    ERROR: Failed building wheel for rpi-ws281x
  Failed to build rpi-ws281x

same error with plain old pip install rpi-ws281x.
I'm not seeing why sysmacros.h should be missing or any indication that its a linux-specific file, so I assume I should be able to install?

You'd need stubs or a dummy library for this. Installing on anything but a Pi is very much out of scope.

ok, thanks for the clarification.


fix Splash 1.8 docs after /examples folder move

Is there some problem with 1.8 docs? I cant see any evident bugs in docs: http://splash.readthedocs.org/en/1.8/index.html

The last link at http://splash.readthedocs.org/en/1.8/faq.html#how-to-run-splash-in-production became incorrect after /examples folder move to 'splash' directory. Fixing it is a matter of grepping splash/docs for /examples and changing URLs.

(and figuring out how to do that for 1.8 release docs)


Update install-kubectl-linux.md

Fix docs in case of apt-key deprecated
In Ubuntu 22.04 apt-key is deprecated throwing a warning and apt update does not work.
$ sudo apt-key add apt-key.gpg
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
OK
$

$ sudo apt update
Hit:1 https://download.docker.com/linux/ubuntu jammy InRelease
Hit:2 https://linux.teamviewer.com/deb stable InRelease
...
Reading package lists... Done
W: GPG error: https://packages.cloud.google.com/apt kubernetes-xenial InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B53DC80D13EDEF05
E: The repository 'https://apt.kubernetes.io kubernetes-xenial InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
$

To fix we must use gpg --dearmor like the following:
$ sudo curl -fsSL https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo gpg --dearmor -orm /etc/apt/keyrings/kubernetes.gpg
$ sudo apt-get update

closing in favor of https://github.com/kubernetes/website/pull/41429


Shipwrecks generating entirely above ground on dry land in lagoons

Not sure if this is considered an issue, but in my opinion it's a bit jarring to see

I'll see what I can do when I get the time

I'll see what I can do when I get the time

I'm not sure if there's a way to control the orientation of them, but as long as it's the upright ones it gives off a stranded ship look and i think that's quite cool.


Migrate away from _utilities.legacy.scss

Is your proposal related to a problem?

For contributors it is currently not clear what utilities classes should be used as some code uses the Tailwind classes and some uses the legacy utility classes.
It would be good to remove the client/scss/overrides/_utilities.legacy.scss file and replace those usages with the appropriate Tailwind classes OR remove their usage completely (e.g. .clear).
Note: There is confusion also about when to use Tailwind classes for a whole component vs just a sub-set of adjustments, but that can be covered elsewhere.

Describe the solution you'd like
Remove the utilities legacy file and replace each usage if needed with either SCSS mixins OR the equivalent tailwind utility class.

class
Note

.u-hidden
Replace with w-hidden - but validate each usage

.clearfix
Remove, replace with mixin clearfix() if used anywhere else, will be removed completely in the near future

.nice-padding
Convert to a Tailwind utility

.divider-before
Remove, not used

.divider-after
Review, may not be needed and does not add anything useful

body.reordering
Should probably be in layouts

.show-transparency
Convert to Tailwind utility

.inline
Replace usage with w-inline (validate each usage)

.inline-block
Replace usage with w-inline-block (validate each usage)

.block
Replace usage with w-block (validate each usage)

.unlist
Remove, only current usage is in Styleguide and this example could either removed or replaced with Tailwind classes

.overflow
Replace usage with appropriate w-overflow-... Tailwind class (validate each usage) OR remove if not used

Describe alternatives you've considered

Leave as is, each contributor can just keep using these for now.

Additional context

We really need to provide a clearer guide somehow as to what Tailwind classes are available and the general approach that is recommended for contributions.
There is separate work happening for removing floats https://github.com/wagtail/wagtail/issues/8126

@thibaudcolas any thoughts on this?

Created after reviewing https://github.com/wagtail/wagtail/pull/8855  - new code added using .u-hidden class.

All of this makes sense to me. Note u-hidden uses !important, so the logical Tailwind replacement would be !w-hidden.

Hi @thibaudcolas
Is this issue still open?

Go for it @Lovelyfin00 - this is still open. Try to address a few small ones in one PR before you tackle them all.
A good place to start is just the removal of unused ones. Be sure you check the code yourself, and also search for partial matches in the code.

@Lovelyfin00 best to search the code for any usage.
Tailwind classes get generated based on the tailwind config file https://github.com/wagtail/wagtail/blob/main/client/tailwind.config.js

I can't find where these html are displayed on the wagtail bakery. I have searched edit post on the baskery admin but I still can't find what I'm looking for.
/wagtail/wagtail/documents/templates/wagtaildocs/documents/edit.html
/wagtail/wagtail/snippets/templates/wagtailsnippets/snippets/edit.html

https://docs.wagtail.org/en/stable/editor_manual/documents_images_snippets/documents.html
https://docs.wagtail.org/en/stable/editor_manual/documents_images_snippets/snippets.html

Thank you so much @lb-
Last one for tonight I promise 😅😅
/wagtail/wagtail/contrib/forms/templates/wagtailforms/list_submissions.html

@Lovelyfin00 in the menu click forms - then click the contact form responses listing.

File: client/src/tokens/typography.jsAdd (maybe after lineHeight)
const listStyleType = {
  none: 'none',
};

Then ensure you export it at the bottom
module.exports = {
  systemUIFontStack,
  monoFontStack,
  fontFamily,
  fontSize,
  fontWeight,
  letterSpacing,
  lineHeight,
  listStyleType,
  typeScale,
};

Then import that listStyleType in client/tailwind.config.js
const {
  fontFamily,
  fontSize,
  fontWeight,
  letterSpacing,
  lineHeight,
  listStyleType,
  typeScale,
} = require('./src/tokens/typography');

Then include it in the module export
    fontWeight,
    lineHeight,
    listStyleType,
    letterSpacing,
    borderRadius,

Based on https://tailwindcss.com/docs/list-style-type

@Lovelyfin00  just a heads up divider-before is not used but divider-after is used in multiple places and serves a purpose.

See the line between the 'filesize/usage' column.
We possibly could migrate that to Tailwind utility classes but just flagging based on feedback on https://github.com/wagtail/wagtail/pull/9535

As of #11365, all that’s listed here has been changed except show-transparency and nice-padding. I’m not entirely sure what to do with those two so will hold off creating a further issue. show-transparency could probably stay as-is, and for nice-padding I have a feeling it could become a "component".


Cannot refresh data set

Hello,
I was trying to use a Refrech Dataset feature, however I met the following error:

##[error]Invalid dataset refresh request. Number of refresh requests in last 24 hours exceeded limit

It was the first time that we tried to refresh a dataset, so I don't understand why it returns such error. Do you have any ideas?

No did you refresh the dataset by hand?


Sharepoint 2.3 Sharing settings cannot be more restrictive than the tenant level

💡 Summary
The external sharing slider set in 2.2 sets the minimum restriction for the tenant. You cannot set more restrictive sharing settings for sites (2.3). Research if it would be better to change the external slider to the most restrictive setting in 2.2 & change the site settings to less restrictive than necessary OR should this policy be removed entirely.
Motivation and context
Currently users are directed to set the external sharing settings to New & Existing Guests, so sites can only be changed to allow Anyone links if necessary. The intention of this setting is to restrict certain sites to a more restrictive sharing setting when necessary.
Implementation notes
One or the other:

Policy 2.2 updated to be a more restrictive setting
Policy 2.3 removed

Acceptance criteria
How do we know when this work is done?

[ ] Updated policy has the change noted in implementation notes
[ ] Sharepoint code is updated to not have the check for 2.3 if policy 2.3 is removed from baseline

I believe CISA needs to make a choice on directive. Either 2.2 should be set to something more restrictive like "only people in the organization" & 2.3 indicates each SharePoint site should be set to the appropriate sharing level, in org only -> Anyone. OR  keep 2.2 as it is currently & delete 2.3 because the only changes you can make to the SharePoint sites are to allow anyone to see them

Decision is to delete 2.3 & change slider setting to Existing Guests.

decision updated to keep 2.3


Options to exclude files of certain size

It seems likely that users will want to exclude:

Files with less than e.g. 10 lines
Files with more than e.g. 2000 lines

These numbers can be subjective so probably best to allow this to be standard configurable options.
Also, it might be smart to add an underlying maximum to stop the CLI from hanging when passed a huge file (e.g. 1m lines). Example use case could be accidentally trying to parse a binary, or some huge web bundle.

I have doubts about specific new options for this.
Users can already ignore directories and files using the existing options, which should achieve the same thing.

I have doubts about specific new options for this.
Users can already ignore directories and files using the existing options, which should achieve the same thing.


Remove erroneous loadbalancer prefix from commands

It looks like this was a copy and paste issue.

Thanks @gerrywastaken . Added a note to login to loadbalancer instance.


Update zio, zio-streams, zio-test, ... to 2.1.2 in series/1.x

About this PR
📦 Updates

dev.zio:zio
dev.zio:zio-streams
dev.zio:zio-test
dev.zio:zio-test-sbt

from 1.0.18 to 2.1.2 ⚠
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "dev.zio" }
}]

labels: library-update, early-semver-major, semver-spec-major, commit-count:1

Superseded by #48.


feature/#52 - display network SVG files with optimized asset files as default

New files:

svg_cache.dart: displays a SVG from the network, with an asset as default
119 SVG (optimized) files

Impacted files:

attribute_card.dart: replaced SvgPicture with the new class SvgCache
pubspec.yaml: added the assets/cache/ folder
user_preferences_view.dart: replaced SvgPicture with the new class SvgCache

@stephanegigandet Cool!
Tell me when your "nuts" are ready.
Have also a look at the list of the icons I put in assets: it's just a list I built myself without knowing the whole list, and there may be missing icons.

@stephanegigandet Cool!
Tell me when your "nuts" are ready.
Have also a look at the list of the icons I put in assets: it's just a list I built myself without knowing the whole list, and there may be missing icons.