Out of memory? GTX 780M - 17.04

Hey,
Trying to train you cool project with new images.
So I tried the example to train, but got these errors.
Error allocating 33554432 bytes of device memory (out of memory). Driver report 17367040 bytes free and<PHONE_NUMBER> bytes total
Wait until the dataprocesses to end
Signal processes
Traceback (most recent call last):
  File "/home/quinten/Documents/3D-R2N2/lib/train_net.py", line 21, in func_wrapper
    return func(*args, **kwargs)
  File "/home/quinten/Documents/3D-R2N2/lib/train_net.py", line 38, in train_net
    net = NetClass()
  File "/home/quinten/Documents/3D-R2N2/models/net.py", line 37, in __init__
    self.setup()
  File "/home/quinten/Documents/3D-R2N2/models/net.py", line 40, in setup
    self.network_definition()
  File "/home/quinten/Documents/3D-R2N2/models/res_gru_net.py", line 70, in network_definition
    t_x_s_update = FCConv3DLayer(prev_s, fc7, (n_deconvfilter[0], n_deconvfilter[0], 3, 3, 3))
  File "/home/quinten/Documents/3D-R2N2/lib/layers.py", line 478, in __init__
    fan_out=self._output_shape[2])
  File "/home/quinten/Documents/3D-R2N2/lib/layers.py", line 74, in __init__
    self.val = theano.shared(value=self.np_values)
  File "/home/quinten/Documents/3D-R2N2/py3/lib/python3.5/site-packages/theano/compile/sharedvalue.py", line 268, in shared
    allow_downcast=allow_downcast, **kwargs)
  File "/home/quinten/Documents/3D-R2N2/py3/lib/python3.5/site-packages/theano/sandbox/cuda/var.py", line 188, in float32_shared_constructor
    deviceval = type_support_filter(value, type.broadcastable, False, None)
MemoryError: ('Error allocating 33554432 bytes of device memory (out of memory).', "you might consider using 'theano.shared(..., borrow=True)'")

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "main.py", line 118, in <module>
    main()
  File "main.py", line 109, in main
    train_net()
  File "/home/quinten/Documents/3D-R2N2/lib/train_net.py", line 24, in func_wrapper
    kill_processes(train_queue, train_processes)
  File "/home/quinten/Documents/3D-R2N2/lib/data_process.py", line 178, in kill_processes
    for p in processes:
TypeError: 'NoneType' object is not iterable
[INFO/MainProcess] process shutting down

I got a GTX 780M shouldn't this be enough to train the samples?
More of the same.
/home/quinten/Documents/3D-R2N2/lib/layers.py:354: UserWarning: DEPRECATION: the 'ds' parameter is not going to exist anymore as it is going to be replaced by the parameter 'ws'.
  padding=self._padding)
/home/quinten/Documents/3D-R2N2/lib/layers.py:354: UserWarning: DEPRECATION: the 'padding' parameter is not going to exist anymore as it is going to be replaced by the parameter 'pad'.
  padding=self._padding)
lib/data_io.py: model paths from ./experiments/dataset/shapenet_1000.json
[INFO/ReconstructionDataProcess-1] child process calling self.run()
lib/data_io.py: model paths from ./experiments/dataset/shapenet_1000.json
Set the learning rate to 0.000100.
[INFO/ReconstructionDataProcess-2] child process calling self.run()
Compiling training function
2017-11-19 10:48:51.435496 Iter: 0 Loss: 0.407328
Compiling testing function
Problem occurred during compilation with the command line below:
/usr/bin/g++ -shared -g -O3 -fno-math-errno -Wno-unused-label -Wno-unused-variable -Wno-write-strings -march=haswell -mmmx -mno-3dnow -msse -msse2 -msse3 -mssse3 -mno-sse4a -mcx16 -msahf -mmovbe -maes -mno-sha -mpclmul -mpopcnt -mabm -mno-lwp -mfma -mno-fma4 -mno-xop -mbmi -mbmi2 -mno-tbm -mavx -mavx2 -msse4.2 -msse4.1 -mlzcnt -mno-rtm -mno-hle -mrdrnd -mf16c -mfsgsbase -mno-rdseed -mno-prfchw -mno-adx -mfxsr -mxsave -mxsaveopt -mno-avx512f -mno-avx512er -mno-avx512cd -mno-avx512pf -mno-prefetchwt1 -mno-clflushopt -mno-xsavec -mno-xsaves -mno-avx512dq -mno-avx512bw -mno-avx512vl -mno-avx512ifma -mno-avx512vbmi -mno-clwb -mno-mwaitx -mno-clzero -mno-pku --param l1-cache-size=32 --param l1-cache-line-size=64 --param l2-cache-size=8192 -mtune=haswell -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -m64 -fPIC -I/home/quinten/Documents/3D-R2N2/py3/lib/python3.5/site-packages/numpy/core/include -I/usr/include/python3.5m -I/home/quinten/Documents/3D-R2N2/py3/include/python3.5m -I/home/quinten/Documents/3D-R2N2/py3/lib/python3.5/site-packages/theano/gof -L/usr/lib -fvisibility=hidden -o /home/quinten/.theano/compiledir_Linux-4.10--generic-x86_64-with-Ubuntu-17.04-zesty-x86_64-3.5.3-64/tmpvcuds4gb/m9124b60ae7623786b4d02a7f8ac06738.so /home/quinten/.theano/compiledir_Linux-4.10--generic-x86_64-with-Ubuntu-17.04-zesty-x86_64-3.5.3-64/tmpvcuds4gb/mod.cpp -lpython3.5m
ERROR (theano.gof.cmodule): [Errno 12] Cannot allocate memory
Wait until the dataprocesses to end
Signal processes
Empty queue
kill processes
Signal processes
Empty queue
kill processes
Traceback (most recent call last):
  File "main.py", line 118, in <module>
    main()
  File "main.py", line 109, in main
    train_net()
  File "/home/quinten/Documents/3D-R2N2/lib/train_net.py", line 21, in func_wrapper
    return func(*args, **kwargs)
  File "/home/quinten/Documents/3D-R2N2/lib/train_net.py", line 71, in train_net
    solver.train(train_queue, val_queue)
  File "/home/quinten/Documents/3D-R2N2/lib/solver.py", line 170, in train
    _, val_loss, _ = self.test_output(batch_img, batch_voxel)
  File "/home/quinten/Documents/3D-R2N2/lib/solver.py", line 218, in test_output
    *self.net.activations])
  File "/home/quinten/Documents/3D-R2N2/py3/lib/python3.5/site-packages/theano/compile/function.py", line 326, in function
    output_keys=output_keys)
  File "/home/quinten/Documents/3D-R2N2/py3/lib/python3.5/site-packages/theano/compile/pfunc.py", line 486, in pfunc
    output_keys=output_keys)
  File "/home/quinten/Documents/3D-R2N2/py3/lib/python3.5/site-packages/theano/compile/function_module.py", line 1795, in orig_function
    defaults)
  File "/home/quinten/Documents/3D-R2N2/py3/lib/python3.5/site-packages/theano/compile/function_module.py", line 1661, in create
    input_storage=input_storage_lists, storage_map=storage_map)
  File "/home/quinten/Documents/3D-R2N2/py3/lib/python3.5/site-packages/theano/gof/link.py", line 699, in make_thunk
    storage_map=storage_map)[:3]
  File "/home/quinten/Documents/3D-R2N2/py3/lib/python3.5/site-packages/theano/gof/vm.py", line 1047, in make_all
    impl=impl))
  File "/home/quinten/Documents/3D-R2N2/py3/lib/python3.5/site-packages/theano/gof/op.py", line 935, in make_thunk
    no_recycling)
  File "/home/quinten/Documents/3D-R2N2/py3/lib/python3.5/site-packages/theano/gof/op.py", line 839, in make_c_thunk
    output_storage=node_output_storage)
  File "/home/quinten/Documents/3D-R2N2/py3/lib/python3.5/site-packages/theano/gof/cc.py", line 1190, in make_thunk
    keep_lock=keep_lock)
  File "/home/quinten/Documents/3D-R2N2/py3/lib/python3.5/site-packages/theano/gof/cc.py", line 1131, in __compile__
    keep_lock=keep_lock)
  File "/home/quinten/Documents/3D-R2N2/py3/lib/python3.5/site-packages/theano/gof/cc.py", line 1586, in cthunk_factory
    key=key, lnk=self, keep_lock=keep_lock)
  File "/home/quinten/Documents/3D-R2N2/py3/lib/python3.5/site-packages/theano/gof/cmodule.py", line 1159, in module_from_key
    module = lnk.compile_cmodule(location)
  File "/home/quinten/Documents/3D-R2N2/py3/lib/python3.5/site-packages/theano/gof/cc.py", line 1489, in compile_cmodule
    preargs=preargs)
  File "/home/quinten/Documents/3D-R2N2/py3/lib/python3.5/site-packages/theano/gof/cmodule.py", line 2294, in compile_str
    p_out = output_subprocess_Popen(cmd)
  File "/home/quinten/Documents/3D-R2N2/py3/lib/python3.5/site-packages/theano/misc/windows.py", line 77, in output_subprocess_Popen
    p = subprocess_Popen(command, **params)
  File "/home/quinten/Documents/3D-R2N2/py3/lib/python3.5/site-packages/theano/misc/windows.py", line 43, in subprocess_Popen
    proc = subprocess.Popen(command, startupinfo=startupinfo, **params)
  File "/usr/lib/python3.5/subprocess.py", line 676, in __init__
    restore_signals, start_new_session)
  File "/usr/lib/python3.5/subprocess.py", line 1221, in _execute_child
    restore_signals, start_new_session, preexec_fn)
OSError: [Errno 12] Cannot allocate memory
[INFO/MainProcess] process shutting down

I've changed the theanoflags for cuda and shutted down al order software (google chrome) to run it and now I'm getting this.
 Though it now keeps 'stuck' at empty queue, but maybe this just takes a long while.

Hi, I also got this problem. Can you tell me how did you sole this issue?

Hi, I also got this problem, my device is GTX 1050ti, can you tell me how to solve this issue, thank you very much.


Add Cypress and BDD folder structure to the New Registry repository

Description:
As the new Testing Sandbox container is available in the New Registry, we can add an E2E tests directory.
As we decided to pursue BDD as a test methodology with use of Gherkin files, we will need a directory for its files too.
I will make a research on best practices of combining Cypress with Cucumber and Gherkin files within a mono repository as ours and implement that.
Defintion of Done:
The tests folder/folders is/are added to the registry app repository.

https://github.com/bcgov/platform-services-registry/pull/1251


Namespace Management APIs

What was changed

Why?

Checklist

Closes

How was this tested:

Any docs updates needed?

Approving under the assumption that this is still technically a beta API that can have changes made as we learn more.


Building a basic web server

It is necessary to build a web server to serve WebXR pages.

Initialized with 018b8d496c72f56773ae49a6793a171e605e943b


Support Analyzer 3

analyzer ^3.0.0

Hey @caoyanglee! I'm currently working to get Floor up and running again, I opened a PR to support analyzer 4.1.0. The idea is to get this merged ASAP and roll out an update within a couple of days.

@caoyanglee do you have a specific use case for analyzer 3.0.0 or are you fine with analyzer 4.0.0?

@vitusortner floor generator is conflicting with chopper generator

Because floor_generator >=1.3.0 depends on analyzer ^4.0.0 and chopper_generator 4.0.5 depends on analyzer ^3.0.0, floor_generator >=1.3.0 is incompatible with chopper_generator 4.0.5.
And because no versions of chopper_generator match >4.0.5 <5.0.0, floor_generator >=1.3.0 is incompatible with chopper_generator ^4.0.5.
So, because mobile depends on both chopper_generator ^4.0.5 and floor_generator ^1.3.0, version solving failed.
pub get failed (1; So, because mobile depends on both chopper_generator ^4.0.5 and floor_generator ^1.3.0, version solving failed.)

@elirehema Chopper team has already pushed PR with analyzer update.

Okay.
Thanks @dkaera

@caoyanglee do you have a specific use case for analyzer 3.0.0 or are you fine with analyzer 4.0.0?

both are ok~


feat: Add python tests script and run python tests in pre-push

@gjreda I've just noticed that the #389 is failing in the CI after merge agains main!
This PR adds an utility to run python tests from the project root using yarn yarn python:tests and updates the git push hook to also run python tests.
@gjreda please fix the error reported in #391 (I don't know how 😅).

@cguedes The tests started to fail when you pushed this commit to the PR: https://github.com/refstudio/refstudio/pull/389/commits/f0266033ed058e459b68b7b0fbf87e54140b8f58
I'll push a fix, but they were failing before merging into main. The root cause is that you changed the filename for projects storage, but did not update the tests.

I suspect the bigger bug here is in your merge process: since we have historically ignored when codecov/patch is failing, I'm going to guess you thought that was the cause of the ❌ on the PR, and not that actual tests were failing.

I know I've been guilty of this in the past too, so we should probably figure out how to make codecov/patch work as we'd like or simply get rid of it, since we do not trust it.

You are right. I thought it was again the codecov/patch issue.
We need to fix our merge process and get rid of codecov/patch. @sehyod what do you think of this?

fixes #391

I know I've been guilty of this in the past too, so we should probably figure out how to make codecov/patch work as we'd like or simply get rid of it, since we do not trust it.

You are right. I thought it was again the codecov/patch issue. We need to fix our merge process and get rid of codecov/patch. @sehyod what do you think of this?

Yes, I 100% agree! codecov/patch is not super useful anyway, the most important is codecov/project


Is this dead ?

we havent heard any updates on this project , is it already dead ?

No, the project is in development

As soon as the KivyMD library version 2.0.0 becomes stable, I will continue to develop this project.


WebTrends integration

Request a new tracking ID from WIG
Integrate JS library into application
Test to make sure data collection is occurring

Accidental duplicate of #82. Thanks ZenHub!


Add Initial platform support for Haiku.

This pull request adds initial platform support for building swiftc and stdlib on 64bit Haiku (x86_64-unknown-haiku) using the build-script as part of my GSoC project with the Haiku project.
It also requires this commit, where the OS check is used here. Other than that, it builds and works fine on Haiku and I'm currently adding more support for the test-suite and the foundation libraries.
Resolves SR-NNNN.

Awesome!

You'll also want to update this file to get standard library command line support for Haiku.

@xwu @CodaFi I have updated the patches to fit the guidelines, could you please review my changes and check if this is OK to test?

@CodaFi @xwu Thank you very much for reviewing my changes, are there anymore changes left todo?

@swift-ci please smoke test

@swift-ci please smoke test

@CodaFi I've already sent a patch for this to LLVM, but this patch isn't included in swift-llvm stable yet. Which is why the build is failing.

@return I suppose you could cherry-pick https://github.com/apple/swift-llvm/commit/aea1537f4d5c3670714cf21aba4762d072a94dbe in a PR for the stable branch.

@korli I've sent a PR to swift-llvm.

@swift-ci please smoke test

@korli PR testing requires privileges. See swift.org
@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@CodaFi thanks for the tests.
@return it seems a change happened on stdlib/public/SwiftShims/LibcShims.h, could you please rebase?

@korli I've rebased my patches and fixed the conflict. @CodaFi Could you please smoke test this commit?

(Drive by smoke test)
@swift-ci smoke test

LGTM

@swift-ci please smoke test

@swift-ci please smoke test

@return If you have no other qualms, this looks good to merge.

@CodaFi These patches are also fine with me.

⛵


network.peers

In the network file we have a .peers() function: https://github.com/datproject/dat-node/blob/1.0/lib/network.js
that mimics the .connected function that already exists on the swarm object. It probably should just keep the same name (.connected()) to reduce confusion across modules

Oh cool! Had no idea discovery swarm exposed that (and as a getter too).

Changed in https://github.com/datproject/dat-node/commit/9e0e9683852fa6ae80401db8efe14d6daa01f475


fix cross refs

fix transformation of crossrefs and add anchors to figures.

I verified locally that this improves many of the reported cases (as well as the zsh link I mentioned). Thanks for tackling this!

Thanks for merging! Could you run book generation for additional languages, please? At least, it would be great to have fr, ja, ko, nl and zh regenerated (they are fully translated).

Sure, done for all those languages. I was a little hesitant to mass-build just because of the problems we ran into with ja recently. Rebuilding those 5, though, it seems to be the only one broken; I manually munged the database again to fix the problem.

Thanks a lot! This will muffle the issues list.

Thanks a lot. This should muffle a bit the issues.


add configurable prometheus env label

This tags prometheus metrics with a configurable 'env' label. The default is either dev or prod.

This tags prometheus metrics with a configurable 'env' label. The default is either dev or prod.

Maybe edit this to mention default is empty.


feat: update get seedlots by user id to get sl by client

Description
Closes #1092
Changelog
New

None;

Changed

Seedlot Endpoint, Service and Repository classes enabling users to fetch seedlots by client id instead of user id.

Removed

None;

How was this tested?

[ ] 🧠 Not needed
[x] 👀 Eyeball
[x] 🤖 Added tests

What gif/image best describes this PR or how it makes you feel?

Thanks for the PR!
Deployments, as required, will be available below:

Frontend
Backend
Oracle-API

Please create PRs in draft mode.  Mark as ready to enable:

Analysis Workflow

After merge, new images are deployed in:

Merge Workflow

Thanks for the PR!
Deployments, as required, will be available below:

Frontend
Backend
Oracle-API

Please create PRs in draft mode.  Mark as ready to enable:

Analysis Workflow

After merge, new images are deployed in:

Merge Workflow

This will make the front-end stop working with the my-seedlots page however, I can make a quick PR for it Wednesday morning, wait for me? perhaps we can use a staging branch again


[ELI5] Tweak wording on the signup screen

People get confused here unsure what "handle" is. "Input your handle" is also confusing.
The first commit replaces the wordings.

This matches our usage of "username" on the login screen.
The second commit is a bit unusual — I'm updating all translations as if this was the wording all along. That's to avoid regressions to translations just before the release. It's fine to update them later (if needed per language) since conceptually the phrasing is the same and the meaning has not changed.
It's a little inconsistent with what we have in Settings. Maybe in the future we'll change it there too. But for now let's make sure people are able to create an account.
Test Plan
Verify above for English.
Then yarn intl:build and verify translations have not regressed and show old strings:

got verbal ok from @pfrazee


Update uglify-js to the current version

An update to uglify-js 3.x did cause failing tests. If anyone wants to fix this, please make a PR to the 4.x-branch.

Closed in d3d39423a3ad138b11d039a498ca8c135635e128


Bug fix: font might not sync to context

This PR changes (delete as applicable)

Nothing, it's a bug fix

Describe the changes below:
Sync font before runWordWrap.
#3389
In Text.updateText() function, style.syncFont() will be invoked before Text.runWordWrap(). But Text.getWrappedText() won't call style.syncFont(), therefore the wrapping result between Text.updateText() and Text.getWrappedText() might not be equal.

Sorry I had not idea how to spit PRs, my mistake.
The 2nd PR is about custom loader.
I had integrated [google webfont loader into loader system by extending File Class. But I could not reference CONST.FILE_POPULATED. Therefore I tried to expose FILE_CONST instead using the value 19 directly.

Thanks. I missed that submit before.


Ionic 2 RC icons color red&blue

Hi,
My project is work but icon's color red and blue. Also navbar is color this like.
Please help me.
Thanks :)

Hello! Thanks for opening an issue with us! As this seems like more of a support question i will urge that you ask this question on our forum. Thanks for using Ionic!


show progress even when output is hidden #1561

Checking for show output has been improved. Progress  is showed  now for the result status "RUNNING"

:+1:


remove azure-core experimental

Docs Build status updates of commit ff07bc6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

package.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


First D3FEND-CCO mappings

First mappings between D3FEND and CCO, developed with @johnbeve and @Finn1928.

[ ] Make sure to merge in d3fend develop to pull in 0.17.0

I went through comments from last meeting and updated to new CCO identifiers. Apologies for the three commits, there was something messed up on my end of things. By next meeting, I will work on some new mappings for the remaining core classes.


Implement touch event manager

Split from #2925

[ ] Depends on #3266
[ ] Depends on #3267

Implements a touch event manager for each touch source to propagate touch events.

Closing as packed up to one PR due to no possible way to test this at its separation: #3269


Grab modules/extensions from Composer

What is the idea?
It would also make sense to add each "module" in separate repos and install them over composer
Why would this be beneficial

Smaller code base
Easier maintainability
-No need to add multiple modules you don't need / want
Users can add easier modules and share them with other users

Please also take #1270 into consideration. I think sharing common dependencies between multiple dependencies would save us from storage space, and possibly make it easier to maintain.
We can also consider going with our "own" extension store, but I think using an already-available one like Composer would be better.
But we should also take users on shared hosting environments into account. Many of them likely won't have access to SSH, thus Composer.

But we should also take users on shared hosting environments into account. Many of them likely won't have access to SSH, thus Composer.

On shared hosting users use FTP for upload sites.
And not SSH!

Idealy yes how ever don't think if a user use softalous knows how to do it...

I think, billing it's tool is not for dummies. ;)

I think, billing it's tool is not for dummies. ;)

We also tell users to use Shared hosting if they don't have any experience with Linux but they all end up using Hestia instead...
So it is a valid concern and we can't just bluf out of it

BB works well on shared hosting. I'm also use it same!
Talking about Softaculos it's only about delivery engine to production. Not problem with shared hosting!

I don't understand where you see problem BB with Softaculos? Softaculos download archived (prebuilded) package and unroll it on hosting server. Where BB problem with Composer???


[Enhancement] Support multiversion function for simd operations

Why I'm doing:
Currently the simd is compiled based on the preprocessing code, such as #if defined(__AVX2__) #if defined(__SSE2__).
This means the binary will only supoort avx2 or sse2 which is determined at the compilation stage. If you run on a machine which doesn't support avx2, then an error will raised, especially when we try to support avx512.
With function multiversion or indirect function, which implementations will be invoked is determined when start up.
Details could check GNU Function MultiVersioning.
What I'm doing:
Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[x] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)
[ ] I have added documentation for my new feature or new function
[ ] This is a backport pr

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.3
[ ] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

Multiversion function is only supported by x86. This code will fail to be compiled on ARM platform.
We should check whether it is on x86 platform before using multiversion function. A choice is to use the following MACROS.
#if defined(__GNUC__) && defined(__x86_64__)
#define USE_MULTIVERSION_CODE 1
#else
#define USE_MULTIVERSION_CODE 0
#endif

#if USE_MULTIVERSION_CODE
#define SSE2_FUNCTION_ATTRIBUTE __attribute__((target("sse2")))
#define SSE42_FUNCTION_ATTRIBUTE __attribute__((target("sse4.2")))
#define AVX2_FUNCTION_ATTRIBUTE __attribute__((target("avx2")))
#define AVX512_FUNCTION_ATTRIBUTE __attribute__((target("avx512f")))
#define DEFAULT_FUNCTION_ATTRIBUTE __attribute__((target("default")))
#define DEFINE_MULTIVERSION_FUNCTION_IMPL(FUNCTION_DEFINATION, FUNCTION_VERSION) \
    FUNCTION_VERSION                                                             \
    FUNCTION_DEFINATION
#define DEFINE_MULTIVERSION_FUNCTION_SSSE2(FUNCTION_DEFINATION) \
    DEFINE_MULTIVERSION_FUNCTION_IMPL(FUNCTION_DEFINATION, SSE2_FUNCTION_ATTRIBUTE)
#define DEFINE_MULTIVERSION_FUNCTION_SSSE42(FUNCTION_DEFINATION) \
    DEFINE_MULTIVERSION_FUNCTION_IMPL(FUNCTION_DEFINATION, SSE42_FUNCTION_ATTRIBUTE)
#define DEFINE_MULTIVERSION_FUNCTION_AVX2(FUNCTION_DEFINATION) \
    DEFINE_MULTIVERSION_FUNCTION_IMPL(FUNCTION_DEFINATION, AVX2_FUNCTION_ATTRIBUTE)
#define DEFINE_MULTIVERSION_FUNCTION_AVX512(FUNCTION_DEFINATION) \
    DEFINE_MULTIVERSION_FUNCTION_IMPL(FUNCTION_DEFINATION, AVX512_FUNCTION_ATTRIBUTE)
#define DEFINE_MULTIVERSION_FUNCTION_DEFAULT(FUNCTION_DEFINATION) \
    DEFINE_MULTIVERSION_FUNCTION_IMPL(FUNCTION_DEFINATION, DEFAULT_FUNCTION_ATTRIBUTE)

#else
// Drop the multiversion code when it is not supported by the compiler and the platform.
#define DEFINE_MULTIVERSION_FUNCTION_SSSE42(FUNCTION_DEFINATION)
#define DEFINE_MULTIVERSION_FUNCTION_AVX2(FUNCTION_DEFINATION)
#define DEFINE_MULTIVERSION_FUNCTION_AVX512(FUNCTION_DEFINATION)
#define DEFINE_MULTIVERSION_FUNCTION_DEFAULT(FUNCTION_DEFINATION) FUNCTION_DEFINATION
#endif

// Exmaple:
DEFINE_MULTIVERSION_FUNCTION_DEFAULT(int foo(int num) {
    return (0 + num);
})
DEFINE_MULTIVERSION_FUNCTION_SSSE42(int foo(int num) {
    return (0 + num);
})
DEFINE_MULTIVERSION_FUNCTION_AVX2(int foo(int num) {
    return (0 + num);
})


Additional metallb support

Fixes #1115 and #1116 by updating the voyager.sh install script and loadbalancer.go.

Thanks a lot @zsandrus !


Fix cursor on hover expand/collapse icon (#155207)

@TahaTesser Fix undesirable side effects of your refactor away from my solution to add IgnorePointer during your code review of my PR https://github.com/flutter/flutter/pull/147098. I don't have time to implement my whole initial fix a second time, and update the tests that were added to verify your disabled color change. The issue is resolved with only adding the IgnorePointer.
See 155207.
Pre-launch Checklist

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I read the Tree Hygiene wiki page, which explains my responsibilities.
[ ] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[ ] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] I followed the breaking change policy and added Data Driven Fixes where supported.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

@nate-thegrate Can't get master to compile. It doesn't recognise Color.a

Yeah, that was a recent change to the dart:ui library.
Should be resolved by following the instructions here: https://github.com/flutter/flutter/blob/main/docs/contributing/Setting-up-the-Framework-development-environment.md

Hey @BenjiFarquhar do you plan to continue working on this change?

Hey @BenjiFarquhar do you plan to continue working on this change?

Hey @Piinks, I'd appreciate if someone can add a test for this. I may be able to do it soon if there are no takers.

Yeah, if you'd be able to add the test at some point that'd be great!
I believe generally, test changes are up to the PR author. If you're not able to get around to it, we can close this pull request and keep https://github.com/flutter/flutter/issues/155207 open, and we'll see if anyone decides to pick it up!

Oh dang—looks like this change has caused some ExpansionPanel tests to fail…
sadly we cannot merge this until all checks succeed 😞

@nate-thegrate Should be all good now. I think the test was saying the expansion panel header is in an enabled state, and the semantics represent this with the isEnabled flag. Adding isEnabled: true to the expansion panel header semantics test made it happy. Let me know if you have any changes or are not sure about my test fix.

My understanding is the approach in https://github.com/flutter/flutter/pull/147098 was taken to avoid Google testing failures? But it has undesired side effects and this PR is reverting it?

@victorsanni yeah, original issue was it disabled the IconButton when canTapOnHeader is true to give button tap control over to the whole ExpansionPanel header, and the fix from https://github.com/flutter/flutter/pull/147098 was to address the disabled color showing, by changing the disabled color to the normal color. but it broke the mouse pointer  when hovering on the expansion panel header, specifically on the IconButton it became the triangle shape, and on the rest of the header it was the hand to express a tappable area. Disabled button changes the mouse pointer to express that it is not tappable. So I have fixed it here in a different way that fixes all of those things.

@BenjiFarquhar so basically this PR allows the icon to look enabled (i.e darker) instead of disabled (i.e lighter) when canTapOnHeader is set to true?

@victorsanni  Yes. When canTapOnHeader is true, the IconButton now behaves merely as an Icon, signalling to the user that the header can expand/collapse, and doesn't interfere with hovering effects on the expansion panel header.

LGTM pending review from @TahaTesser.


fs.fdatasync isn't modernized

Is there a reason for this omission? Otherwise I think it should be promisified just the same.

I don't think that there is a reason, PR welcome 👍


Vickel: Watch Attorney[\W_]+Marketing[\W_]+Suite[\W_]*+Vol.2

Vickel requests the watch of the watch_keyword Attorney[\W_]*+Marketing[\W_]*+Suite[\W_]*+Vol\.2. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Attorney[\W_]*+Marketing[\W_]*+Suite[\W_]*+Vol\.2 has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Saturated audio

Validation

[X] Game has been updated to the latest RE4HD release (v1.1: https://www.re4hd.com/?p=9552)
[X] Data has been validated with SFV (a guide to using QuickSFV is available at that link, use that with this 1.1 SFV: BIO4-HDProject1.1-SFV.zip)

Describe your issue here (drag+drop ZIP to attach it)
Some audios during gameplay like the movements of the statue of salazar, or the "ganado" throwing fire sounds bad..

Here are the issues in form or video:
https://imgur.com/gallery/DEulNc1
Also, I've noticed enemies sounds start with a "click" (mostly when they speak).  I think this issue could be fixed by adding 0,001 sec of silence at the beginning of every sound, but of course, this is not the most optimized way of doing it XDD. Here's an example:
https://youtu.be/HKecTuS9vkM

Here are the issues in form or video: https://imgur.com/gallery/DEulNc1
Also, I've noticed enemies sounds start with a "click" (mostly when they speak). I think this issue could be fixed by adding 0,001 sec of silence at the beginning of every sound, but of course, this is not the most optimized way of doing it XDD. Here's an example: https://youtu.be/HKecTuS9vkM

https://imgur.com/gallery/r283yxZ  Another one.

@albertre4HD See the #309 issue, thanks.

Having the same issue here. Sounds like "reverbing" sound sources triggering multiple times and overlaping with one another.
Seems to be related to 120+ Hz / FPS, since it does not seem to happen with
config.ini :
resolution 2560 1440 60
variableframerate 60

As a temporary workaround, changing the values as follows help with alleviating the problem (though you can still hear the artifacts)
resolution 2560 1440 90
variableframerate 100

If your monitor supports VRR (G-/Free-sync) enabling it in driver's settings would help precieved smoothness too.


plotutils: fix build with clang 16

Description of changes
Clang defaults to C++, which disallows the register storage class specifier. This causes the build to fail. Remove the specifier to allow clang 16 to build plotutils.
Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[x] x86_64-darwin
[x] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 253947 run on aarch64-darwin 1

6 packages built:

algol68g
autotrace
chickenPackages_5.chickenEggs.plot
plotutils
pstoedit
pstoedit.dev

Result of nixpkgs-review pr 253947 run on aarch64-linux 1

6 packages built:

algol68g
autotrace
chickenPackages_5.chickenEggs.plot
plotutils
pstoedit
pstoedit.dev

Result of nixpkgs-review pr 253947 run on x86_64-darwin 1

6 packages built:

algol68g
autotrace
chickenPackages_5.chickenEggs.plot
plotutils
pstoedit
pstoedit.dev

Result of nixpkgs-review pr 253947 run on x86_64-linux 1

6 packages built:

algol68g
autotrace
chickenPackages_5.chickenEggs.plot
plotutils
pstoedit
pstoedit.dev


Implemented #9, #16, #17, #41 and #59, enhanced Pattern class, added method to fill patterns that repeat

Added an additional check in the constructor of the pattern class to prevent null lines
And added that the string array for lines is copied, so you can't "smuggle" null lines into the pattern instance by changing the original string array
Added wrapAround flag for the Pattern class so, if desired, the values returned from getObject can be repeated
Enhanced the existing javadoc for the normal fillPattern methods in InventoryContents
Added 4 new methods in the style of the existing fillPattern methods in InventoryContents called fillPatternRepeating to make use of the wrapAround flag. It will fill the pattern from one slot to another slot in a rectangle and if the pattern ends will loop around to continue filling the area
Added withPattern and blacklistPattern methods in SlotIterator, according to #17
Added reset() method to SlotIterator to set it back to the first slot position
Added fillSquare method in inventory contents, according to #59
Added endPosition() method to SlotIterator, according to #16
Added additional .open() methods in the SmartInventory class, using #9 as a guideline
Added .findItemStack() method in inventory contents, using #41 as a guideline

That's a very nice work, thank you very much! I'll review that as soon as possible

Just wanted to ask:
Are you going to merge this in the near future or not, because for over 2 weeks you didn't comment in here

Just wanted to ask:
Are you going to merge this in the near future or not, because for over 2 weeks you didn't comment in here

Yes, of course, but, I don't have much time currently but I'll try to merge it this week

Done! Thank you very much for your work :)

You might want to close the issues that I referenced if you think this is a sufficient implementation of them


Logging JMeter might leak sensitive information

Is your feature request related to a problem? Please describe.
Once passing sensitive information over systemPropeties, e.g.:
jmeter {
   systemProperties.put("javax.net.ssl.keyStorePassword", "Some pwd")
}

The following line reveals the javax.net.ssl.keyStorePassword value in the logs, thanks as part of msg: Running jmeter with jvmArgs: {} and cmdArgs: {}  (https://github.com/qualersoft/jmeter-gradle-plugin/blob/develop/src/main/kotlin/de/qualersoft/jmeter/gradleplugin/task/JMeterBaseTask.kt#L203)
Describe the solution you'd like
I'd like to be able to supress the msg in the logs completely, or to be able to selectively supress specific system properties.

Hi @typekpb,
thank you very much for reporting, the output is just a left over from the early days, therefor never thought about this issue.
For me it would be ok to remove the output completely but I can also think of case where the output might become handy, so I guess best solution would be to wire the output to gradles debug flag.

@mathze , thanks for the fast reply.
Debug output would be perfect for me (=> still an option to debug if needed).
hope to see the change, released in maven central soon :)

@mathze your response time is really incredible, thanks for the fast fix!

@typekpb, you're welcome and thank you helping to improve the plugin.


Add .NET Core support

Includes a .NET Core Starter Pack and an example

@alexpilotti,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

Codecov Report

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

@@           Coverage Diff           @@
##           master     #159   +/-   ##
=======================================
  Coverage   33.15%   33.15%
=======================================
  Files          17       17
  Lines        1098     1098
=======================================
  Hits          364      364
  Misses        686      686
  Partials       48       48

Continue to review full report at Codecov.

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

23,000 LOC?! Can't we commit a much smaller example app? This seems a bit excessive for a hello world app.

That's the very basic sample generated with "dotnet new mvc ..." as by readme.txt. I'm going to replace it with a smaller one :)

@bacongobbler I replaced the sample. LOC count dropped significantly. :)

this looks much better, thank you.
You'll also need to do 2 things:

call make generate to autogenerate the pack files
fix up the unit tests to show 7 packs instead of 6

Once that's done, I'd be happy to merge.

@bacongobbler done, I put the autogenerated file change in a separate commit

thank you so much! :)


Several Users - use file as userlist arg ~Pielco11

Is there the option to get the tweets of several users in the same CSV file? That is, with a command like this:
python Twint.py -u ursername -o file.csv --csv
How can I add more than one user to get all their tweets at the same time?
I had thought about looping or creating a list. But in the Command Prompt it does not allow it. So I would not know how I could do it.

Hi, I added a new arg, userlist, to let you do so. Try with something like python Twint.py --userlist user1,user2 -o file.csv --csv

Great!!!
It works perfectly.
Thank you very much for your input.

You can also parse files as input, nothing change just do python Twint.py --userlist path/to/file.txt --csv -o file.csv be sure to have one user for line

The truth is that it is very useful to analyze files as input.
However, I have used the command that you have given me, indicating the TXT file address, but I do not know why I extracted tweets from other users. I've put the users well and one on each line.
It's very strange.

Hmmm, going to check right now!

Now it works, there were readline instead of readlines but with the 2nd one you had annoying \n

Nothing. The same thing keeps happening to me. That is to say that it analyzes other users and not those that I have the TXT file.
I do not know if I'm doing something wrong. But I have a user per line and I put the address of entries well. So I do not know.

Ok, now it uses abspath, should work!

Would it be something like this?
python Twint.py --userlist os.path.abspath("user.txt") --csv -o file.csv
I do not know very well how to use abspath

Don't worry about that, the abspath is included in the code. Just try as earlier python Twint.py --userlist path/to/file.txt --csv -o file.csv

Nothing. The same thing keeps happening to me. I do not know why. But do not worry, I will put one by one the users in the code. But it is strange.

Really really strange

This happens to me. I have the txt document on my desktop and when I run the command it does not return the tweets from this users. If not of others. And I have tried to put the address of the txt document in different ways and nothing.

Hmm, maybe with Windows there are problems with slashes...
Can you add print(url) in twint/get.py at line 73, please?
So that you have something like:
    self.config.Near = self.config.Near.replace(",", "%2C")
    url+= "%20near%3A{0.Near}".format(self.config)
    print(url)
return url

Try adding the line and post the output, please

In Twint.py can you also do
(lines 59-60)
def loadUserList(ul):
    print(os.path.abspath(ul))
    if os.path.exists(os.path.abspath(ul)):

please?

I've only read this briefly, but on Windows use \ instead of / for path to file:
Example:
Desktop\file.txt

@DavidPerea While we try to find a solution, I suggest you to use a string as --userlist arg
Sorry for the inconvenience

Nothing. Upside down. Thank you very much for the help and the contribution of the string as --userlist.
I will do so meanwhile.

Sorry to ask again here.
But I've been working with strings as userlist  arg but it gives me a problem. And it happens when I put more than 25 users does not get tweets.
So see if you know how to solve this problem and increase the limit of users. That now stands at 25 users.

Hmm, well I tried something and I can get results with no more than 27 users
To be sure that's not an issue with Twint, try printing the url and search with the browser

@pielco11 Thank you for the amazing tool for scraping Twitter. I'm facing the same issue with the user limit of ~25 when getting usernames from the text file (my file has ~1000 usernames). I'm using it with time range to get tweets from specific period from all users in txt file: twint --userlist parth/to/file.txt --since 2018-07-01 --until 2018-09-19 -o file.csv --csv The error is CRITICAL:root:twint.run:Twint:Feed:noData'items_html which I know you've discussed also in #360
Is there any way around those limits? I guess I could loop through my list 20 at the time but I'm new to Python so making this loop is quite tricky for me. Any other solutions that emerged since you've discussed it here?

@GeekOnAcid that limit is imposed by Twitter. You would have to split your file in chunks of 25 users and then run the command with every list


GitHub integrations page

We list GitHub Enterprise in our integrations page. It'd be great to list GitHub (github.com) as well to make it clear that we have integration, and briefly mention what is supported and how to link GitHub and Buildkite accounts. Maybe even a brief note about noreply email handling.

Great idea! I'll leave this open until it's added 😊Thanks @sj26!

Hey @sj26 do you have a link somewhere to what you mean by noreply email handling?

Gotcha.
Does it handle the username@ OR username+IDnumber@ variant?
And at first glance, it is isn't findable in your Buildkite settings, is that correct or am I looking in the wrong place?

So my advice wasn't technically correct — we add whatever email github gives us to your account. For me, this is my actual email address. For others, it'll be the latest flavour of github's noreply email. So disconnecting and reconnecting might sometimes give a newer or updated email. This is an implementation detail so isn't spelled out in any settings page, although you can see the effects (if any) in the user email settings page.

Thanks! Can you check if 15fd91a  is a reasonable distillation of what you've just said?

@plaindocs sounds right to me! :+1:


Long Periods of Seasonality (m=112) takes long time in auto_arima

Description

Hi All,
I am trying to use auto-arima for a long periods of seasonality. However, it seems that it takes a long time to run. In R, we can give fourier function in xreg to convert long seasonality to non-seasonal.
https://www.rdocumentation.org/packages/forecast/versions/8.5/topics/fourier
https://robjhyndman.com/hyndsight/longseasonality/
is there any equivalent in pmdarima?
Any help will be appreciated.
Steps/Code to Reproduce

Here is my statement:
model_fit = auto_arima(user_data.iloc[:, i], error_action='ignore', suppress_warnings=True, m = 112, seasonal= True, D=1, stepwise=True)

This is really a duplicate of #102. While there is some work being done for the v1.2.0 release that will dramatically speed up tests of seasonality, the core time waster is actually the internal SARIMAX computation, which is just a slow thing. Can you share R vs Python benchmarks (without Fourier transform) so we can compare apples to apples?
In regards to transforming your data, you could try any of scipy's many Fourier methods. I'd be interested to know whether that speeds things up...

... but you raise a good point. Maybe specific Fourier functions could be a good addition to the package.

Fourier featurizers were added in #121 and will be released in v1.2.0


Python 3

I tried to run this, but python 2 is deprecated, cv2 is not in pip anymore, there is opencv-python, but when I installed that and other dependences, I get errors...
╰─➤  page_dewarp.py example_input/boston_cooking_a.jpg
loaded boston_cooking_a.jpg with size 2448x3264 and resized to 490x653
Traceback (most recent call last):
  File "page_dewarp.py", line 1001, in <module>
    main()
  File "page_dewarp.py", line 954, in main
    cinfo_list = get_contours(name, small, pagemask, "text")
  File "page_dewarp.py", line 489, in get_contours
    mask, cv2.RETR_EXTERNAL, cv2.CHAIN_APPROX_NONE
ValueError: need more than 2 values to unpack

Robert Sachunsky (@bertsky) has worked on converting the project to Python 3. See PR #20.

in the code find for ,contours,
change ,contours, to contours,_
@reagle


gollvm: supporting i386/i686 builds (Intel)

I am creating this issue for a future patch (and others should be expected, for the same purpose), observable on/threw Gerrit.
It would be referenced (a bit) later.
This is about compiling & running 32bit userspace Go applications on (under?) 32bit CPU/hardware/OS kernel  (system-on-board).
Something for 32bit AMD's CPUs would be a good cause for a separate Github issue.
This is not covering the following (corresponding options/use cases should be covered within separate Github issues):

running 32bit userspace apps on 32bit hardware/CPU/OS kernel, for micro-controllers (system-on-chip);
running 32bit containerized Go apps, on 64bit hosts (system-on-board);
running 32bit containerized Go apps, on 64bit hosts (system-on-chip);
running 32bit bare metal/in-kernel firmware (probably on 32bit system-on-chip), compiled from Golang source code
.

I am attaching the specification,  System V Application Binary Interface
intel386-psABI-1.1.pdf

@thanm, I was dealing with Gerrit's issues (Git hooks and "codereview" tool) - and I think I cab start submitting mini-patches, for a review, today.

My first patch, submitted for a review is https://go-review.googlesource.com/c/gollvm/+/270219 .
This one is related to CMake's configuration files:

AutoGenGo.cmake mostly contain the constants, which are valid for "yonah" ;

GoVars.cmake contains some basic support for the arch. dependent rules (at least CMake's generator wouldn't crash) and some Linux system folder naming conventions (would affect installation prefix, for sure) ;

LibbacktraceUtils.cmake defines stuff for building libbacktrace dependency;

LibffiUtils.cmake defined stuff for building libffi dependency
.

My next patch would cover driver/ArchCpusAttrs.h
Since it is required to perform pre-checks of supported CPU features (in my case - I have a relic Intel Celeron M440), which is resolved by Clang (common code for any LLVM related projects, for these checks - so both llvm-goc and pre-installed Clang would both act similar, on a specific hardware) - I used the following tool:

#include "llvm/ADT/StringRef.h"
#include "llvm/ADT/StringMap.h"
#include "llvm/MC/SubtargetFeature.h"
#include "llvm/Support/Host.h"
using namespace llvm;
SubtargetFeatures Features1;
int main (int argc, char **argv)
{
sys::getHostCPUName();
StringMap HostFeatures;
if (sys::getHostCPUFeatures(HostFeatures))
for (auto &F : HostFeatures)
Features1.AddFeature(F.first(), F.second);
printf("test %s", Features1.getString().c_str());
printf("\nsomething else\n");
return 0;
}

.
Many thanks to @topperc for guiding me threw this.

I see that CPU instructions are defined in the following files:
https://github.com/llvm/llvm-project/blob/756f5978410809530150f5e1cd425e85ad94d1cd/llvm/lib/Target/X86/X86InstrFormats.td
https://github.com/llvm/llvm-project/blob/756f5978410809530150f5e1cd425e85ad94d1cd/llvm/lib/Target/X86/X86InstrInfo.td
https://github.com/llvm/llvm-project/blob/756f5978410809530150f5e1cd425e85ad94d1cd/llvm/lib/Target/X86/X86.td
https://llvm.org/doxygen/X86TargetParser_8cpp_source.html
. ABI specific stuff could be found here:
https://clang.llvm.org/doxygen/CodeGen_2TargetInfo_8cpp_source.html
available calling conventions
.

I missed a file, where library path should be handled: https://go.googlesource.com/gollvm/+/refs/heads/master/driver/Driver.cpp#70
I think I will submit the change within one of my future patches (yet to be submitted, as for now).

@thanm, @cherrymui: I don't understand why CABIOracle contains "Oracle" in it's naming.
What does Oracle corp. has to do with you naming convention?
Attaching some diagrams, as a rude summary:

I see some adoptions of EightByteInfo::determineABITypesForLLVM's calling convention function.
Looks like EightByteInfo class has a constructor, which initializes private variable typeManager_ with the same of the second passed argument (of type *TypeManager).
Correct me/elaborate, if I have an improper understanding/vision of the API.
It's not currently cleat whether the switch (cconv) is a good location to define the logic of handling 32bit and 64bit calling conventions (calling conventions for 32bit variation of a specific arch. has pretty diverse ABI handling, compared to how it is done for 64bit variation of that arch.).

@advancedwebdeveloper "oracle" happens to  be the name of a company but it is also an English word.  It also has a well established meaning specific to computer programming: https://en.wikipedia.org/wiki/Oracle_machine .

Ian is correct. "Oracle" is being used in the non-commercial sense (as in "Oracle of Delphi"), e.g. some entity that you ask questions of.

Referencing http://llvm.org/docs/LangRef.html#parameter-attributes - specific considerations would be added later

Reminding about unresolved issue https://github.com/golang/go/issues/42975

You are referencing System V x86_64 ABI spec. , on https://go.googlesource.com/gollvm/+/refs/heads/master/bridge/go-llvm-cabi-oracle.cpp#61 .
It looks like that's https://raw.githubusercontent.com/wiki/hjl-tools/x86-psABI/x86-64-psABI-1.0.pdf#page=22 :

The classification of aggregate (structures and arrays) and union types works as follows:

If the size of an object is  larger than eight eightbytes,  or it  contains  un-aligned fields, it has class MEMORY12.

In the same time - I am able to extract the following statements, from i386 ABI spec. http://www.sco.com/developers/devspecs/abi386-4.pdf#page=29 :

The Intel386 architecture does not require all data access to be properly aligned.
But I suspect that it would be aligned by LLVM/Clang, in some way.

Unsure if the following contains any useful statements, for elaborating this:

For example, double-precision values occupy 1 doubleword (8-bytes), and their natural alignment is a word boundary, meaning their addresses are multiples of 4
.

I am able to extract the following, from i386 ABI spec., on http://www.sco.com/developers/devspecs/abi386-4.pdf#page=36 :

The stack is word aligned.  Although the architecture does not require any
alignment of the stack, software convention and the operating system
requires that the stack be aligned on a word boundary.

And by taking

the term word refers to a 32-bit object

into an account, on http://www.sco.com/developers/devspecs/abi386-4.pdf#page=27 - that would be 32/8=4 bytes

So if it differs from what happens on x86_64 - the struct EightByteRegion should not be compiled on i686.
And there have to be another structured type, for the similar purpose.
Probably that i686 oriented struct should contain such functions:
void determineABITypesForC();
void determineABITypesForC();
It's constructor should contain

case llvm::CallingConv::C:
determineABITypesForC();
break;

Probably related to https://github.com/golang/go/issues/42440#issuecomment-735389706 : we could provide such functions:
CABIOracleC::CABIOracleC(TypeManager *typeManager): CABIOracleArgumentAnalyzer(typeManager) ;
CABIParamDisp CABIOracleC::classifyArgType(Btype *btype);
CABIParamInfo CABIOracleC::analyzeABIParam(Btype *paramType, ABIState &state);
bool CABIOracleC::canPassDirectly(unsigned regsInt, unsigned regsSSE, ABIState &state);

Stack alignment on 32-bit x86 has become quite complex.  Search for "stack" in https://gcc.gnu.org/onlinedocs/gcc-10.2.0/gcc/x86-Options.html#x86-Options.

@marmolejo  , please elaborate regarding 32bit soft-CPU implementation and consideration for stack alignments.
There where some relic i386/i686 ASIC CPUs produced, in the past - so not all options have sense.
I was curious if future re-implementations of i686 compatible soft-CPUs could could assume specific alignments.

@jamieiles , perhaps you could explain your design considerations?

CC @MicroCoreLabs

@JonChesterfield , could you elaborate regarding relic 32bit AMD's CPUs?
Which stack alignments should be considered, for old CPUs?

Did you try to perform any specific optimizations, by using stack alignment?

@kcadieux , @GreatKeeper : could you elaborate about MSVC's stack alignment, when compiling (and linking, by using Microsoft's linker) for 32bit Windows 10 (i686) ?

Citation from https://reviews.llvm.org/D60748 :

Please also exclude FreeBSD from these changes, since we care a lot about backwards compatibility, and specifically about alignment requirements. (We have run into many issues in our ports collection where upstream assumes everything is 16-byte aligned on i386, which is NOT ABI compliant.)

I didn't new about about that, btw.
@emaste , @kostikbel : could you explain more?
@pcordes , found your old post here .
Could you explain more about Clang vs GCC behavior?

Currently, Clang always aligns to 4 bytes on i386 standard calling conversion. This is not strictly following psABI/gcc. Chen had a new patch https://reviews.llvm.org/D78564 to fix the problem after D60748 abandoned. But it hasn't been accepted.

D78564 is trying to fix the wrong alignment when the parameters are unnamed parameters(Only for __m128, __m256 and __m512).
From what I know, When clang uses the stack to pass struct, it will always be aligned to 4 bytes, except __m128, __m256 and __m512, no matter the parameter is named or unnamed. I have described the rule of __m128/256/512 in that D78564 . This is totally different from gcc. For example:
struct __attribute__((aligned(64))) X {
 int x;
};

gcc will align to 64 byte but clang will align to 4 byte.
For D78564, when the parameter is unnamed, the callee will always assume that the alignment of the unnamed parameter is align to 4 byte.  For common struct there is no problem. But for __m128/256/512, caller will align these parameters to 16/32/64 bytes, the callee will get wrong result.

Looks like I missed https://go.googlesource.com/gollvm/+/refs/heads/master/unittests/BackendCore/TestUtils.h#35

@thanm, could you provide an extended explanation of 16 bytes sizing?
https://go.googlesource.com/gollvm/+/refs/heads/master/bridge/go-llvm-cabi-oracle.cpp#156
https://go.googlesource.com/gollvm/+/refs/heads/master/bridge/go-llvm-cabi-oracle.cpp#374
https://go.googlesource.com/gollvm/+/refs/heads/master/bridge/go-llvm-cabi-oracle.cpp#447
https://go.googlesource.com/gollvm/+/refs/heads/master/bridge/go-llvm-cabi-oracle.cpp#809
https://go.googlesource.com/gollvm/+/refs/heads/master/bridge/go-llvm-cabi-oracle.cpp#856
https://go.googlesource.com/gollvm/+/refs/heads/master/bridge/go-llvm-cabi-oracle.cpp#996
https://go.googlesource.com/gollvm/+/refs/heads/master/bridge/go-llvm-cabi-oracle.cpp#1047
https://go.googlesource.com/gollvm/+/refs/heads/master/bridge/go-llvm-cabi-oracle.cpp#1134
Which of those are ABI specific (System V x86_64, not related to the current i686 issue)? Which are specific to https://tour.golang.org/basics/11 (int16)? Specific to LLVM itself?

could you provide an extended explanation of 16 bytes sizing?

Mailing list is a better place for questions of this sort.  Happy to respond on golang-dev.


ITP Trainee: withdrawal and target

Background
We want to define a target for trainee numbers
A/C

Identify withdrawal (archived) people
Identify possible trainee target
Add it to ITP number sheet

Added it the sheets with previous data.


:sparkles: expose types

like we discussed the adapters are flagged as @internal and all *.d.ts files are renamed to *.model.ts so that they are included in the build.

Tests are failing, did you also adjust the imports there?

It might also be a better option to simple use .ts instead of .model.ts as replacement for .d.ts s.t. there will be less file changes

did change .model.ts to .ts now


Any thought on using Preact instead of React

What I'm trying to achieve
Getting rid off lib dependency which is made by Facebook and improve performance.
Describe a proposed solution
Switch to React. It's not that hard
Other solutions I've tried and won't work
Unless you stop using vdom
Screenshots or mockups

import Preact from "preact"

We dont have plans for switching to preact. We are not observing performance issues while using our frontend apps so far. Personally I dont see benefits of doing such switch but you are more then welcome to fork and test this ;)


Output does not copy to clipboard with newlines

Environment

Elixir & Erlang/OTP versions (elixir --version): 1.12.1-otp24
Operating system: OS X 10.13
How have you started Livebook (mix phx.server, livebook CLI, Docker, etc): livebook server
Livebook version (use git show if running with mix): 0.2.0
Browsers that reproduce this bug (the more the merrier): Chrome
Include what is logged in the browser console: no errors
Include what is logged to the server console: no messages

Current behavior

Create a new notebook with an Elixir cell containing:

IO.puts("one thing")
IO.puts("two thing")

Evaluate the cell.
Create a new Markdown cell.
Select the output text from the Elixir cell and copy it.
Paste the output text into a ``` block in the Markdown cell.
Observe that there is no newline or other whitespace between one thing and two thing.

Expected behavior
Ideally, the text would paste with the same line breaks as originally output by IO.puts.
At a minimum, the text should paste with line breaks that match what's displayed in the notebook; "copy the output and paste it into a Markdown cell" does not work as a workaround for #206 if the output isn't paste-friendly.

Closed via #385.

@benjreinhart @jonatanklosko thanks for the fast turnaround on this! 🎉


Git Accounts > Convey user to use token instead of password in case of github

Summary
Github has deprecated password usage.
Users face issue if they use password instead of token.
Motivation
Lack of messaging on UI which hampers the workflow and leads to a negative experience.
Proposal
Global Config > Git Accounts > Show a message: If using Github, use token instead of password.
https://www.figma.com/file/z5oh20tbYNDZkDQGrSYgol/Global-Configurations?node-id=1%3A89

Fixed.


Backport to Humble: Pass more distance information out from FCL collision check #2572

See #2572

Thanks for this backport!


Mismatch in time steps in the residual convergence checker

Based on checking the array sizes in DREAM output files in which the timesteps!=savesteps I believe the solver (nonlinear in my case) contains saved data about the residual max error as well as the number of iterations needed for convergence at each timestep, not just at each savestep. This is supposedly a bug in the C++ code.
The issue is apparent when trying to call solver.plot(), solver.plotResidualConvergence() or solver.plotResidualMaxError() in the CLI (DREAM/py/cli/cli.py). The different plotting routines return with errors due to size mismatches of the arrays which would be plotted.

Quoting Mathias:

The DREAM output file should not contain any traces of how many time steps were actually taken (except under the "settings" category). It should only contain the saved time steps. If the non-linear solver contains information about the residual convergence in every time step, this is a bug which should be fixed in the C++ code.

Suggestion for solution: in the Solver, save a separate time which is used exclusively for diagnostic quantities from the solver. This time should be stored at every time step, regardless of whether its a save step or not.


Connector uncorrectly determines the number of partitions

What kind an issue is this?

[x] Bug report. If you’ve found a bug, please provide a code snippet or test to reproduce it below.
The easier it is to track down the bug, the faster it is solved.

Issue description
It seems that there is an issue in how Elasticsearch Hadoop's RestService is calculating the slice paritions for a specified, index/shard. In my opinion there are two issues:

Number of produced tasks is not correct: There seems to be an issue with the division being executed here We  can see the code calculating the number of parititions is using an casting the result of the division to integer. This will cause one partition lower than the expected partitions. E.g:
If we have 3 shards with 184 items each, and we want 30 documents per partition(setting es.input.max.docs.per.partition equal to 30). Then for each shard the following number of partitions will be calculated:For shard 0:

(int)Math.max(1, 184 / 30) => (int)Max.math(1, 6.1) => (int)(6.1)

so 6. We should expect 7 because 6* 30 = 180 and there are 184 documents in that shard. The same should stand for shard 1 and 2. As a result, we should be expecting 21 partitions, but ES-Hadoop will give us 18.

Slices create empty tasks: From the same file we can see here that for each shard, it creates one sliced partition, always starting from zero to the total number of partitions per shard. It also uses the preference query parameter to target each query to the specified shard of the Partition. In the above example this would lead to the following paritions(slices)

For shard0:
(0, 6), (1, 6), (2, 6) (3, 6) (4, 6), (5, 6)
for shard 1:
(0, 6), (1, 6), (2, 6) (3, 6) (4, 6), (5, 6)
and for shard 2:
(0, 6), (1, 6), (2, 6) (3, 6) (4, 6), (5, 6)
According to the scroll documentation here sliced scroll is executed on the shards first, meaning that for the first shard, shard  0, queries only (0, 6) and (3, 6) are going to fetch data. All the other slices will just create empty tasks. The same will go for all the other shards, thus creating 6 tasks with data, and 12 empty tasks. Furthermore instead of 30 documents per task we are now fetching actually 90 docs per partition.
Version Info
Elasticsearch cluster
OS:         :  Ubuntu
JVM         :  1.8.0
Hadoop/Spark:  2.2.1
ES-Hadoop   :   elasticsearch-spark-20_2.11-6.3.2
ES          :  6.3.2

Number of produced tasks is not correct:

We could round to the closest integer but the idea is to get approximatively es.input.max.docs.per.partition documents per slice which is what you get with the current computation so I am not sure what you mean by "is not correct".

Slices create empty tasks:

This is a known issue that we fixed in 6.4 with https://github.com/elastic/elasticsearch/pull/29533. Slices are now computed based on the number of shards that participate in the request so your example would get the same number of documents per slice if you upgrade your cluster to the latest 6.4 version.

We could round to the closest integer but the idea is to get approximatively es.input.max.docs.per.partition documents per slice which is what you get with the current computation so I am not sure what you mean by "is not correct".

Agreed. The max docs setting has always been an approximation - not a guarantee. Its inclusion into ES-Hadoop was to allow for higher levels of parallelism than just the shard level scrolling would allow. Additionally, there were cases where Spark users with particularly large shards in ES could not read using the connector - since Spark has a hard limit of documents that are allowed per partition (they use an integer per document in a split).
All that said, I'm not against making the setting more of a guarantee, though I think there are a decent number of things that we can and should be doing to improve the use of this property - starting with increasing the default value by quite a bit. 100k documents is fine in many cases, but in practice it can cause significant slowdowns when querying very large shards, leading to the default value almost always needing to be tuned higher or disabled all together.

I am sorry, maybe I should have used the word misleading. From the documentation of the es.input.max.docs.per.partition I read:

this parameter advises the connector on what the maximum number of documents per input partition should be.

So I thought that partitions should as many as to not go over the set max limit.  Thank you for making it clear to me :)
Either way please proceed with closing since the most important issue for me is solved in v6.4

starting with increasing the default value by quite a bit. 100k documents is fine in many cases, but in practice it can cause significant slowdowns when querying very large shards, leading to the default value almost always needing to be tuned higher or disabled all together.

Maybe we should not set any default here and restore the one partition per shard by default ? I see how the default value can be deceptive, creating a lot of partitions for little benefit on large shards. One partition per shard is more predictible and users can use the extra option if they want to increase parallelism.

So I thought that partitions should as many as to not go over the set max limit.

I agree that the wording in the documentation is ... misleading ;). We should mention that it's a best effort.

Maybe we should not set any default here and restore the one partition per shard by default ? I see how the default value can be deceptive, creating a lot of partitions for little benefit on large shards. One partition per shard is more predictible and users can use the extra option if they want to increase parallelism.

My thinking is the same along these lines, but in the case of using Spark it might make sense to set the default number to the hard limit of records per Spark partition. If the shard that we're examining comes back with a count that is less than this amount, we should probably just skip the slicing all together and read from the shard alone. I think I'll pull together a fix for that soon and put it in for 7.0. I feel a little wary changing the default on a non-major release.
As for the documentation, I'll push a quick change and backport it.

but in the case of using Spark it might make sense to set the default number to the hard limit of records per Spark partition.

After posting this I realized that the Spark hard limit is at 2GB of data, not based on the limitations of an integer, but rather based on the maximum size of byte buffers. In this case, I think it makes more sense to simply have the user set the max docs per partition in the case that they run into issues with Spark.

I've pushed up some changes to the documentation around the max docs per partition setting. I've also remove the default from the master line (7.0.0) and deprecated the use of a switch property in 6.X (6.5.0).
Thanks for the input all!

Thanks @jbaiera !


How to update vocab.txt

Hi, I am trying to implement this repo in a different domain . I have updated the vocab file by manually appending new vocabs in the pretrained vocab.txt but it doesnt seems to work . What is the correct way of adding the vocabs of my desried domain in the pretrained vocab.txt

Updating the vocabulary manually should be fine, the new words should be at the bottom part of the vocab file.
Can you show me more detail of the error? Thanks!

Dear @taiwen97
First of all, thank you all for the work and dedication.
You did use the BERT model tokenizer WordPiece on your biomedical domain corpus and then append those(new vocab) to the exBERT_vocab.txt, is that right?
My ques is that, did you do any kind of preprocessing on the biomedical data before doing tokenization?
Also, can I use another type of tokenizer that does not use WordPiece type tokenization?
About the data_preprocess.py file, is there any format for the raw text file? I did try a raw text file from Wikipedia using python data_preprocess.py -voc ./exBERT_vocab.txt -ls 128 -dp ./wiki.txt -n_c 5 -rd 1 -sp ./wiki_data.pkl.
But it gave me this output [[], []]
What am I doing wrong here?


orderDocs removes documents from result if the document has an id key

It looks like the orderDocs function in cache.ts is removing (or not returning) documents when they contain the id property in the document itself.
I haven't dug deeper into this, but it shouldn't be too difficult to find why this is happening.
Consider:

a dummy Firestore collection, and 2 documents inside: A: {id: "123", value: "hidden"} and B: {value: "notHidden"}.
a FirestoreDataSource for this collection: dataSource

Expected result:
When calling findOneById, with either A or B, I expect A or B to be returned respectively.
Observed result:
findOneById(A) is returning null, whereas findOneById(B) is returning the B document properly.
This can be tested by adding the following test:
  describe('findOneById', () => {
    it('Should find a doc by ID', async () => {
      // make sure we have extra users in the DB
      // also make sure they are created outside of the DataSource
      // as things will be cached on creation
      const dRefOne = await usersCollection.add({
       id: "something",
        email<EMAIL_ADDRESS>      })
      const dSnapOne = await dRefOne.get()

      const foundOne = await userSource.findOneById(dRefOne.id)

      assert.deepStrictEqual(foundOne, { ...dSnapOne.data(), id: dRefOne.id, collection: dRefOne.parent.id, createdAt: dSnapOne.createTime, updatedAt: dSnapOne.updateTime })
    })

This might not be actually accurate.
I was using version 5.2.0, which did itself rely on dataloader 2.0.0, and this is what I observed.
However, after upgrading to the latest version (6.0.1 at this point), which upgraded to dataloader 2.2.2, it seems that the issue is not occurring anymore.


Crash when clicking a resource property in the inspector while no scene is open

Godot version
4.0 83d26737727f281afcb33f66fea5d09ed6c48d5a
System information
Windows 10 64 bits GLES3 GeForce GTX 1060 6GB/PCIe/SSE2
Issue description
I have a resource containing another. If I open it in the inspector and click the property, Godot crashes.

EditorPropertyResource::_resource_selected assumes there is an open scene, causing an access violation.
Steps to reproduce

Close all scenes
Create a GradientTexture
Assign gradient to a new Gradient in place
Save the GradientTexture as a .tres file
Double-click the .tres file in the file system to open it in the inspector
Click the gradient property: observe a crash

Minimal reproduction project
InspectorEditSubResourceCrash.zip

From #59496, CC @KoBeWi
Maybe it should skip when the resource is a builtin subresource.


[terra-form-radio] Updated legend styles for radio field to handle long text

Summary

Added style display: inline-block; to legend-group to better handle long text

Closes #3142
Deployment Link

https://terra-core-deployed-pr-#.herokuapp.com/
Testing

Additional Details

Thank you for contributing to Terra.
@cerner/terra

we might need to test the checkbox-field also for long text scenario in IE. since it has similar implementation for legend.

@supreethmr should we log an issue to investigate and/or update if this change is needed?

@supreethmr should we log an issue to investigate and/or update if this change is needed?

I verified in checkbox field. yes the long text does gets truncated in checkbox-field too. logged issue for checkbox-field : https://github.com/cerner/terra-core/issues/3156

@supreethmr Awesome! thank you thank you! 😄


Front camera not opening in iOS OS version 16.4

The camera automatically switches to the rear camera in iOS 16.4

This is caused by invalid media track constraints used to get front facing camera.
AFrame:
https://github.com/hiukim/mind-ar-js/blob/41e3e264c6861c45512364d724c620412cc67180/src/face-target/aframe.js#L105
ThreeJS:
https://github.com/hiukim/mind-ar-js/blob/41e3e264c6861c45512364d724c620412cc67180/src/face-target/three.js#L107
Should use 'user' instead of 'face'
Reference:
https://developer.mozilla.org/en-US/docs/Web/API/MediaTrackConstraints/facingMode

any solution for this?
I tried modifying to "user" in "mindar-facec-aframe.prod.js" but still no luck on iPad with 16.4.1.

really? I don't think that "," has any effect. It's a valid syntax.
You have error running the code with ","?

really? I don't think that "," has any effect. It's a valid syntax.
You have error running the code with ","?

I don’t see any error, but seems likely only iOS16.4 or later will trigger this bug. My last modification only fixed safari, not Google Chrome.
*The facingMode does trigger this bug on the latest iOS, I remembered that I tried removing facing mode completely, it seems fixing Google Chrome bug too. I will verify it again later tonight.

I'm struggling with this problem, but this is my solution,.
in mindar-face-aframe.prod.js file
instead of using face or user. I change both, so I don't use environment
default: 'face': 'environment'
solution: 'face': 'user'
because of that code, I can't use my external webcam when using my laptop (which has a front camera).
This could be a temporary solution.

really? I don't think that "," has any effect. It's a valid syntax.
You have error running the code with ","?

the answer confuse me too, @wuiyang means
Change From :
facingMode: (this.shouldFaceUser ? 'face' : 'environment'),
To :
facingMode: (this.shouldFaceUser ? 'user' : 'environment'),
in mind-ar-js/src/face-target/aframe.js & mind-ar-js/src/face-target/three.js

fixed in v1.2.2. thx


Write a C++ program to check leap year

Description
Write a C++ program to check leap year
Leap years are years that are divisible by 4, but not by 100, unless they are also divisible by 400. For example, 1996 is a leap year, but 1900 is not. Write a function that takes a year as a parameter and returns True if the year is a leap year, False otherwise.
Input  : 2016
Output : Leap Year

How to contribute

Save the solution in program/CheckLeapYear.cpp file
Add CheckLeapYear.cpp file in check-leap-year folder

!assign


Prepare for v3.5.3

✨ ✨ ✨ ✨ ✨ ✨ ✨ ✨ ✨ ✨ ✨
///🚫3////5🚫///🚫3/////////⚡//////////////////
✨ ✨ ✨ ✨ ✨ ✨ ✨ ✨ ✨ ✨ ✨

https://github.com/danger/danger/blob/2d734e13789a1075bf37feab4157d2f93b125689/.travis.yml#L28-L31 is not working 😓

          1 Message

  :book:
  :tada:

  Generated by :no_entry_sign: danger

Check out the end of the build results for circle, something really odd there - at least it's not greening

Yeah, I wonder if the deploy scripts run on a different machine, they do say they run on 1.9.x

Let's merge to see if 099e1c5 is working .

Fine with me, it's non-critical infrastructure 👍

Check out the end of the build results for circle, something really odd there

👉 https://github.com/rspec/rspec-core/issues/2337 Opened an issue on RSpec Core.

Check out the end of the build results for circle, something really odd there
👉 rspec/rspec-core#2337 Opened an issue on RSpec Core.

It's from https://github.com/orta/rspec_junit_formatter/commit/00c773db3abcea1082243bd568e02d830a5db753, please see https://github.com/orta/rspec_junit_formatter/commit/00c773db3abcea1082243bd568e02d830a5db753#commitcomment-19352389.


Problems with searching within Keybase files and messages

Keybase GUI Version: 1.0.48-20180516160420+b56432f520
Hi!
Search function:
We seem to be unable to search the text of messages in Keybase or within files in Finder on our Macs. We have a large volume of files and messages so not having the ability to search is really difficult.
Thank you!!

keybase chat search

I don't know what that means or how it helps, but thank you! :)

@mmattimoe Were you able to find a solution for searching within Files? ...or at minimum searching file names?
I'm trying to kill off Google Drive and just realized that searching for files in kbfs  is kind of a critical part of doing that.
Thanks.

No, we never did, unfortunately. It's definitely a pain.
On Mon, Apr 1, 2019 at 3:34 AM Mike Chu<EMAIL_ADDRESS>wrote:

@mmattimoe https://github.com/mmattimoe Were you able to find a
solution for searching within Files? ...or at minimum searching file names?
I'm trying to kill off Google Drive and just realized that searching for
files in kbfs is kind of a critical part of doing that.
Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/keybase/client/issues/12148#issuecomment-478468473,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AkjzEcEJUSWuKkWTBhFQZhsjCoX_KtmWks5vcbZxgaJpZM4UV1Cn
.

--
Sincerely,
Megan K. Mattimoe, J.D.
Executive Director
Advocating Opportunity
1119 Adams Street, Second Floor
Toledo, Ohio 43604
Phone<PHONE_NUMBER>, ext. 700
Fax<PHONE_NUMBER>
Mobile<PHONE_NUMBER>
Email<EMAIL_ADDRESS>Website     www.advocatingopportunity.com
Facebook  www.facebook.com/advocatingopportunity
Twitter       https://twitter.com/AOAdvocate
Confidentiality Statement: This electronic message contains information
from the law firm of Megan K. Mattimoe, Esq., and may be confidential or
privileged. The information is intended to be for the use of the individual
or entity named above. If you are not the intended recipient, be aware that
any disclosure, copying, distribution or use of the contents of this
message is prohibited. If you have received this electronic message in
error, please notify the sender immediately by reply e-mail.

This could be a blocking issue for me to migrated from Google Drive to Keybase. Halp!

One piece of good news: from the Keybase native app, navigate to Files, search does seem to work correctly.

I think this is a duplicate of this: https://github.com/keybase/client/issues/18417
@strib Perhaps consider merging and closing?

Hi!
I don’t know how to merge and as of yet it remains unresolved. I’ll check
18417 but form what I can tell it’s still an issue - we can’t search, it’s
maddening.
On Tue, Jul 16, 2019 at 10:00 AM Denali Lumma<EMAIL_ADDRESS>wrote:

I think this is a duplicate of this: #18417
https://github.com/keybase/client/issues/18417
@strib https://github.com/strib Perhaps consider merging and closing?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/keybase/client/issues/12148?email_source=notifications&email_token=AJEPGEOZY3BBPWGOXSA4Z5LP7XIAJA5CNFSM4FCXKCT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2A6FGY#issuecomment-511828635,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJEPGEKUDXX3K3IFVDUZ37DP7XIAJANCNFSM4FCXKCTQ
.

--
Sincerely,
Megan K. Mattimoe, J.D.
Executive Director
Advocating Opportunity
1119 Adams Street, Second Floor
Toledo, Ohio 43604
Pronouns:  She/Her/Hers
Phone<PHONE_NUMBER>, ext. 700
Fax<PHONE_NUMBER>
Mobile<PHONE_NUMBER>
Email<EMAIL_ADDRESS>Website     www.advocatingopportunity.com
Facebook  www.facebook.com/advocatingopportunity
Twitter       https://twitter.com/AOAdvocate
The information contained in this communication may be confidential, is
intended only for the use of the recipient named above, and may be legally
privileged.  If the reader of this message is not the intended recipient,
you are hereby notified that any dissemination, distribution, or copying of
this communication, or any of its contents, is strictly prohibited.  If you
have received this communication in error, please resend this communication
to the sender and delete the original message and any copy of it from your
computer system.
[image: Safe Space Small]


Resolves in my case #16

#16
No tests yet
And I haven't tested it on dfferent browsers

I'm closing this, because if this should be fixed, I would fix this with an option enhancement rather than just ignoring CORs like iframes. Also, there are a few things that would must be fixed:

Use === instead of ==
Include a test
Put the filter into filterElements instead of highlight

Anyway thank you for your contribution. I'm sure we will find a solution for your problem.


Implement a "review mode" for autofix application

This has been discussed in a few other issues (#2395, #3642), but I want to create a parent issue to track the scope and implementation.
We'd like to implement a new CLI mode in which users are presented with autofix suggestions one-by-one and given the opportunity to accept or reject fixes iteratively.
This likely wouldn't be the default, but rather would be put behind a --interactive or --fix-interactive flag.
elm-review is a good example of the behavior we want to implement -- see here:

Here's the behavior I'm imaging:

User runs ruff --fix-interactive src/.
Internally, check the files.
If there are any fixable violations, present them iteratively, accepting-and-applying or skipping as we go.
Once we've cycled through, if at least one fix was applied, re-check the file.
Repeat this process, since fixes can cause new fixable violations to appear (e.g., removing a usage could then cause an import to be unused). (We might end up showing duplicates here that need to be skipped again.)
Once the review process is a no-op (all skipped, or no fixable violations), finish the interactive session and print out the remaining violations.

If a contributor is interested in taking this on, I'm happy to help with scoping and create separate issues for the various subtasks.
A few things that come to mind:

We likely need is a variant on autofix::apply_fixes that prompts the user when applying each fix and prints out the diagnostic to the CLI.
Right now, we process each file independently in parallel, apply fixes + re-check each file iteratively on its own, and then aggregate the results (How many errors were fixed? Which errors remain?). In order to support this, we likely need to move the fix application + re-checking up a level, such that we lint all the files, collect all the diagnostics, then iterate through to apply fixes on a file-by-file basis, and re-run the linter phase if any fixes were applied.

I can look into this! Seems like a fun one. Any scoping help would be much appreciated

@charliermarsh I could give this a shot !, I might just need some extra guidance as I am still getting used to the codebase

@sladyn98 I've also been eyeing this one as a fun project — happy to help out if you want to collaborate.

Ha, so was I!  @sladyn98 I'm also happy to help out if you'd like.

Lets go  ! @madkinsz @evanrittenhouse we can all do this together.

Since this is a pretty substantial project, I might suggest that someone start by scoping out the work involved in whatever form they see fit for comments / questions, perhaps via a GitHub Discussion? This should probably also involve a little bit of hacking on Ruff (e.g., prototyping) to see around any corners and inform decisions.

@charliermarsh Yeah I am happy to open a discussion thread, I have been going through the rust code and have some questions.

(Author of elm-review here) I'm happy to answer questions as well (not on the implementation though, I don't know Rust not the Ruff codebase)

https://github.com/charliermarsh/ruff/discussions/4937 I Started a discussion here. Feel free to comment. I have started hacking a bit hoping to learn and implement more as I go on : )

I was recently contributing to an open source project and trying to help them get started with the Ruff linter. The maintainer of the project requested that I only fix one type of issue per commit to make it easier for them to review. It is a small-medium sized project (8,443 lines of Python across 23 files), but they had never used a Python linter or formatter before, so there were over 900 errors from the subset of rules I decided to enable.
Anyway, because Ruff does not support this natively, I decided to write a simple wrapper script to allow interactively applying the autofixes per rule. The script also optionally supports committing the changes. In case it is helpful for anyone else, the script is available on GitHub: https://gist.github.com/tdulcet/c1f6415bcae66a4b0cfb6eb96b15444b. Feedback is welcome. For reference, the resulting PR is here: https://github.com/mail-in-a-box/mailinabox/pull/2343.
The script first runs the ruff check --output-format json command to get the full list of errors in JSON format. It then groups those errors by rule. For each rule, it shows the output of the ruff rule <code> and ruff check --select <code> commands. Then it checks if there are any autofixes available from the JSON output. If so, it additionally shows the output from the ruff check --diff --select <code> command (#7352 could eliminate the need for this). It then asks the user if they want to apply the autofixes. If the user says yes, it runs the ruff check --select <code> --fix command. Lastly, it gives the user a chance to make any manual fixes. After the user presses Enter, it continues on to the next rule. It only checks each rule once, but users can of course run the script multiple times as needed until everything is fixed.
Any command line options provided to the script are forwarded to that first ruff check command. There is also a ARGS list near the top of the script that allow providing additional arguments to every ruff check command, such as --preview or --unsafe-fixes.

That is pretty neat! I just a few days ago did the same thing slowly by hand, repeatedly running ruff check --select ... while running over each error code in UP to see if there was anything to fix. Same rationale of wanting to commit each type of fix in its own commit. That script could have saved me some time...


Creating new environment in Watson Studio based on custom image not possible with cpdctl

We would like to use cpdctl to create a new environment in Watson Studio based on a custom image that contains python packages needed to execute our automated platform tests. We already use cpdctl to create custom environments in WML, which are then used for our deployment tests.
The creation of a new environment in Watson Studio via UI based on this image works as expected.
We used the following example to implement the creation of new environments in Watson Studio via cpdctl: https://github.com/IBM/cpdctl/blob/master/samples/Notebook-and-Environment-samples-for-Projects.ipynb
An example call of us would look like this:
cpdctl environment create --project-id xyz --type notebook --name "Default IBM Runtime 22.1 on Python 3.9 (custom)" --display-name "IBM Runtime 22.1 on Python 3.9 (custom)" --hardware-specification '{"guid": "f3ebac7d-0a75-410c-8b48-a931428cc4c5"}' --software-specification '{"guid": "24d8d3f7-ac80-508f-80f9-d86f7140098a"}' --tools-specification '{"supported_kernels": [{"language": "python", "version": "3.9", "display_name": "IBM Runtime 22.1 on Python 3.9 (custom)"}]}' --jmes-query metadata.asset_id --output json
This creates a new environment in the Watson Studio project, but fails to reference the correct software configuration.  It follows that this environment can not be used to execute our tests due to the job returning that an environment has been used that is no longer available.

This has been tested on CP4D 3.5.14 and 4.5.0 on ppc64le.
As far as we know, a software specification is a term used only in WML, not in Watson Studio.  Are we using the tool incorrectly or does cpdctl not support the creation of environments in Watson Studio yet?
Help is greatly appreciated!

Hi @luca-janas ,
WS does have the concept of software specifications. The UI looks like a SW spec with this guid can't be found on the system, and thus, not rendered.
Are you following all the steps listed in "Demo 4: Adding additional packages for custom environment" of https://github.com/IBM/cpdctl/blob/master/samples/Notebook-and-Environment-samples-for-Projects.ipynb. ? You start by creating a custom software specification, and use then that to create an environment...

Hi @alexlang74,
thank you for your answer!
We do not create a custom software specification with a package extension via cpdctl as shown in the example. We are using an existing custom software specification whose software specification id we query using cpdctl. This existing custom software specification is based on a custom image with additional python packages.
Here an example for the query to get the id of the custom software specification:
cpdctl environment software-specification list --project-id xyz --name custom-sw-spec-name --jmes-query resources[0].metadata.asset_id --output json
This returns the software specification id: 24d8d3f7-ac80-508f-80f9-d86f7140098a
So the software specification we are trying to use already exists. We create a new environment in the project with this software specification with the cpdctl call shown in the original issue statement.
Is it possible to use the existing custom software specification to create a new environment in a project?

Hi @rafalbigaj could you please have a look at this ?
In what time frame can cptctl be extended for this use case ?

@alexlang74 are you able to answer Luca's question?

Sorry, yes. Looking into this now...

Have not found a good way with cpdctl yet... What you need in CPD here is the reference for a custom runtime definition, which "points" to the custom runtime image. This is different from WML, where "all you need" is a software specification. I'm now checking whether it's possible to specify this definition via cpdctl...

I need to check whether Rafal can do this, or actually Fang from our team (who is on vac right now)

So @luca-janas ,
I have not found a way to do this via cpdctl yet. The key thing that is missing is a reference to the runtime definition that you created when you uploaded the custom Watson Studio image. The following flow works (outside cpdctl):
Assumption: You followed the steps in https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=environments-building-custom-images to create a custom image. One part (https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=images-uploading-changed-configuration) involves uploading the custom runtime configuration for your custom image. One recommendation: when creating the custom runtime configuration, change its display_name attribute to a custom value. This will allow you to find it better in the steps below.
To create a custom environment that references your custom image:

Get the platform access token curl <CloudPakforData_URL>/v1/preauth/validateAuth -u <username>:<password>
Store that in the environment variable TOKEN
Run curl -k -H "Authorization: Bearer $TOKEN" "https://${cluster_name}/v2/runtime_definitions" | jq -r ".resources[] | {guid: .metadata.guid, display_name: .entity.display_name}"
This will return a list of runtime definitions, similar to...
{
  "guid": "17f0181e-1840-5e04-bdba-237d53266c0c",
  "display_name": "Jupyterlab Notebook IDE with Python 3.9 and GPU"
}
{
  "guid": "8a5849c6-949c-5ac9-ba8f-0b4e07efb107",
 "display_name": "Alex Jupyter with Python 3.7"
}
...

Find the guid of your custom runtime definition (this is where a custom display_name comes handy)
To create a custom environment, runcurl -k -X POST -H "Authorization: Bearer ${TOKEN}" -H "accept:application/json" -H "Content-Type:application/json" -d '{"type": "notebook", "name": "Custom_Py39_Env", "display_name": "Custom Python3.9 environment", "hardware_specification": {"type": "referenced", "guid": "f3ebac7d-0a75-410c-8b48-a931428cc4c5"}, "software_specification": {"type": "referenced", "guid": "12b83a17-24d8-5082-900f-0ab31fbfd3cb"}, "tools_specification": {"supported_kernels": [{"name": "python3", "language": "python", "version": "3.9", "display_name": "Python 3.9"}]}, "runtime_definition": "<YOUR RUNTIME DEFINITION ID">' "https://<YOUR CLUSTER>/v2/environments?project_id=<YOUR PROJECT>"

Thanks, @luca-janas , my apologies that this took so long...

Hi everyone, please excuse my reply. Thank you for providing the API calls and the functionality in cpdctl! We were able to implement our test cases.


Overhaul pubsub module and update docs

Overhaul the pubsub module. Add classes Topic, Subscription, Consumer, Alert, Response.
Add auth module supporting authentication via a service account or oauth2
Add exceptions module with class OpenAlertError
Add "Overview" section in docs
Add classes in utils module: ProjectIds, Cast
Add files: CHANGELOG.md, pittgoogle_env.yml, requirements.txt
Cleanup some issues flagged by Codacy

@djperrefort will you review the pyproject.toml and poetry.lock files? I added a couple of dependencies. When I ran poetry lock to update that file it changed stuff unrelated to the dependencies I added.
Also, do I understand correctly that we no longer need a requirements.txt file, and that we're no longer using Read The Docs?

@hernandezc1 Take a look at what's included here. Particularly:

pubsub module
auth module
docs

You don't need to look in detail, just enough so that you're a little more familiar with what's in this repo.


Markdown region folding

Closes #45118.
In some cases the region comments get parsed as nested children of other elements and are not registered as being proper folding regions. This seems to only occur with wacky formatting, so I'd vote to keep the simple implementation as is unless it comes up in more common cases.

Sure, makes sense

@mjbvz this should be good to merge now

@JacksonKearl Thanks. Please keep an eye on incoming issues for markdown folding (in insiders only of course)


pinia example added

Added example of using vite-plugin-ssr with Vue and Pinia.

@luke951 Looks good 👌. One thing: let's align the example with the boilerplate, so that we can run the boierlplate tests, see https://github.com/brillout/vite-plugin-ssr/pull/296/commits/dd89816ae7c6e405348153bf761209d32e1c3e06.

@brillout OK, I updated the example with the boilerplate.

Good idea to create a custom test instead of re-using the boilerplate test suite.
Let's push it forward:

Let's reduce the test to the bare minimum (only testing that the counter button is working)
Let's reduce the example code to the bare minimum. No logo, no layout, only one page, only a counter.

Let me know if you object.
Looking forward to merge!

@brillout  I updated .testRun let me know if that works 'cos I cannot run this test locally for some reason.

The tests are failing. Seems like you modified the libframe/ submodule?

I cannot run this test locally for some reason.

What's the error?

@brillout As far as I know if you want to test pinia state management you need to use @pinia/testing library so I added this package. I don't think unit tests are that important when it comes to the counter. I just wanted to add an example of using pinia similarly to an example with vuex.

I didn't mean unit testing. Same test you had earlier but stripped to down to test only one page.

Closing. But feel free to re-work on this and I'll gladly re-open.