GPT-2 segfaults when used through the CLI

Trying any GPT-2 GGML model through the CLI appears to cause an immediate segfault:
llama-rs # cargo run --bin llm gpt2 infer -m models/gpt2/cerebras-2.7b-q4_0.bin -p "Now, this is a story all about how"

[...]
[2023-05-01T23:43:17Z INFO  llm::cli_args] Model fully loaded! Elapsed: 75ms
zsh: segmentation fault  cargo run --bin llm gpt2 infer -m models/gpt2/cerebras-2.7b-q4_0.bin -p

This appears to be true regardless of the model (Cerebras and base GPT-2 seem to both suffer from this).
This doesn't happen when run through the GPT-2 example.

I wonder if this has to do w/ loading through the snapshot.

I am not able to reproduce this problem
llama-rs: ./target/release/llm gpt2 infer -m ~/.ggml-models/cerebras-gpt-13b.bin -p "Hello my name is"
[2023-05-03T17:55:57Z INFO  llm::cli_args] ggml ctx size = 7857.04 MB

[2023-05-03T17:55:57Z INFO  llm::cli_args] Loaded tensor 8/485
...
[2023-05-03T17:56:02Z INFO  llm::cli_args] Loaded tensor 480/485
[2023-05-03T17:56:02Z INFO  llm::cli_args] Loading of model complete
[2023-05-03T17:56:02Z INFO  llm::cli_args] Model size = 0.00 MB / num tensors = 485
[2023-05-03T17:56:02Z INFO  llm::cli_args] Model fully loaded! Elapsed: 5008ms
"Hello my name is 'Celest,' and you're looking for a guy named..." "Marius." ""I'm looking for Marius^C

How weird... is that q4 or f16?

Is this wrong?
https://github.com/rustformers/llm/blob/be56c36/crates/models/gpt2/src/lib.rs#L314-L316

Ok, just tested with https://huggingface.co/xzuyn/GPT-2-124M-ggml-q4_1/blob/main/ggml-model-q4_1.bin on macOS:
# cargo run --bin llm gpt2 infer -m models/gpt2/GPT-2-124M-ggml-q4_1.bin -p "1 + 2 = "
    Finished dev [unoptimized + debuginfo] target(s) in 0.08s
     Running `target/debug/llm gpt2 infer -m models/gpt2/GPT-2-124M-ggml-q4_1.bin -p '1 + 2 = '`
✓ Loaded 149 tensors (125.8 MB) after 153ms
zsh: segmentation fault  cargo run --bin llm gpt2 infer -m models/gpt2/GPT-2-124M-ggml-q4_1.bin -p

Is this wrong?
https://github.com/rustformers/llm/blob/be56c36/crates/models/gpt2/src/lib.rs#L314-L316

Aha - I think you've figured it out...
Running with --num-ctx-tokens 1024 doesn't segfault for me. Our default of 2048 doesn't work for all models. Oops.

Quick findings with a debugger:

Only seems to happen with the mmap'd model
The segfault occurs here: data is invalid https://github.com/ggerganov/ggml/blob/ff6e03cbcd9bf6e9fa41d49f2495c042efae4dc6/src/ggml.c#L9146
The only place get_rows is used is here: https://github.com/rustformers/llm/blob/7c2edb13149ff78765134e97190fb1f80a2fa39d/crates/models/gpt2/src/lib.rs#L152-L153
Thus, one of these two tensors is likely not loading correctly through mmap
Using a sane context length and --no-mmap seems to circumvent this for now

This is definitely something we should investigate and fix, but not a showstopper for now, I think.


Source JavaScript used on xto6.js.org example contains an error

It's just a low priority issue on the homepage of http://xto6.js.org/
The source JavaScript in the example transpilation contains an error:
Person.prototype.getAge = function (birthYear) {
  var age = 2015;
  age -= birthYear;

  return result;
};

which should be
Person.prototype.getAge = function (birthYear) {
  var age = 2015;
  age -= birthYear;

  return age;
};

Also this is incorrect, and I'm not sure what it was meant to be:
Object.defineProperty(Person.prototype, 'age', {
  get: function () {
    return this.getAge();
  }
});

The getAge() function call needs a parameter birthYear otherwise you get NaN.

@mohebifar, what's the story with xto6.js.org site? Shouldn't it be redirected to lebab.io?
Similarly there's xto6 package available on npm. It should be deprecated to direct users to lebab instead:

Deprecate a version of a package

xto6.js.org site has now been redirected to lebab.io.


ImportError: cannot import name 'PILLOW_VERSION' from 'PIL'

🐛 Describe the bug
Importing torchvision fails. I used the following install command :
conda install pytorch torchvision torchaudio cudatoolkit=10.2 -c pytorch
My Pillow version is 9.2.0.
Versions
Collecting environment information...
PyTorch version: 1.12.1
Is debug build: False
CUDA used to build PyTorch: 10.2
ROCM used to build PyTorch: N/A
OS: Ubuntu 20.04.4 LTS (x86_64)
GCC version: (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
Clang version: Could not collect
CMake version: version 3.16.3
Libc version: glibc-2.31
Python version: 3.8.13 | packaged by conda-forge | (default, Mar 25 2022, 06:04:18)  [GCC 10.3.0] (64-bit runtime)
Python platform: Linux-5.15.0-1017-aws-x86_64-with-glibc2.10
Is CUDA available: True
CUDA runtime version: 11.6.124
GPU models and configuration: GPU 0: Tesla V100-SXM2-16GB
Nvidia driver version: 510.73.08
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True
Versions of relevant libraries:
[pip3] numpy==1.23.3
[pip3] torch==1.12.1
[pip3] torchaudio==0.12.1
[pip3] torchvision==0.2.2
[conda] blas                      2.116                       mkl    conda-forge
[conda] blas-devel                3.9.0            16_linux64_mkl    conda-forge
[conda] cudatoolkit               10.2.89             h713d32c_10    conda-forge
[conda] libblas                   3.9.0            16_linux64_mkl    conda-forge
[conda] libcblas                  3.9.0            16_linux64_mkl    conda-forge
[conda] liblapack                 3.9.0            16_linux64_mkl    conda-forge
[conda] liblapacke                3.9.0            16_linux64_mkl    conda-forge
[conda] mkl                       2022.1.0           h84fe81f_915    conda-forge
[conda] mkl-devel                 2022.1.0           ha770c72_916    conda-forge
[conda] mkl-include               2022.1.0           h84fe81f_915    conda-forge
[conda] numpy                     1.23.3           py38h3a7f9d9_0    conda-forge
[conda] pytorch                   1.12.1          py3.8_cuda10.2_cudnn7.6.5_0    pytorch
[conda] pytorch-mutex             1.0                        cuda    pytorch
[conda] torchaudio                0.12.1               py38_cu102    pytorch
[conda] torchvision               0.2.2                      py_3    pytorch

This is solved when installing torchvision==0.13.0, but i don't know why this version wasn't chosen automatically


Consider using source generator

At the moment parts of your code base are using reflection to register your dialogs. eg https://github.com/LukeMoody01/Moody.DialogService/blob/afa36861ede71282d9a6a2225c4ce30cbdc2fd2c/Moody.DialogService/Services/DialogService.cs#L81
Consider using source generator similar to https://github.com/reactivemarbles/Splat.DI.SourceGenerator
Main advantage is performance.
Also the reflection code is a bit manual which can cause a bit of breakage easily

So with source generators btw, the actual code you produce isn't all that different, just you know the types at compile time and generate the code then.


Add use cases to DG:

Add, Delete, Update Students.
Assign, View Homework.

Please have a look at the DevGuide before merging here (on my fork).
Major Changes:

Added some Non-Functional Requirements
Added 2 extra User Stories that were not originally in our Google Docs (related to Exams), but have been implemented in v1.2.
Added use cases.


bugfix(tiller): replace + with _ in "helm create" template Chart version

Fixes #1698
In order to comply with the Kubernetes contraint

Tested with helm create foo and helm install foo/ --dry-run --debug. Looks good

Thanks!


[Question] Is there any way to set the max db connection idle time in the gorm.Open() function?

Your Question
Hi folks,
Just wondering if there's any way to set the max db connection idle time in the gorm.Open() function configs? I can't find there's any related key in the gorm Config struct.
Like in the codes below,
db, err = gorm.Open(postgres.Open(dataSourceName), &gorm.Config{/*Any available key here?*/})
is there available setting to set the connection max idle time? Or should I only set it by the way way below:
db, err = gorm.Open(postgres.Open(dataSourceName), &gorm.Config{})
if err != nil {
	return nil, err
} else {
	sqlDB, err := db.DB()
	sqlDB.SetConnMaxIdleTime(60 * time.Second)
	if err != nil {
		return nil, err
	}
}

Thanks.
The document you expected this should be explained

Expected answer

https://gorm.io/docs/generic_interface.html

this is the only way to change the db connection idle time currently.


Add an initial test for SSH.

@quinton-hoole @cjcullen @krousey

comment addressed, ptal.
--brendan

Looks reasonably sane to me.  LGTM.

LGTM, other than the 1 nit.

comment addressed.  ready for submit.


what's the equivalent function like:   page._client.on

Please help to translate the function below to C#
await page._client.on('Page.downloadProgress', ({ state }) => {
if (state === 'completed') {
console.log('download completed. File location: ', downloadPath + '/' + fileName);
}
});

The equivalent would be Page.Client.MessageReceived received. There you can check for MessageID == "Page.downloadProgress" and parse MessageData (it's a JToken) to the object you need.

Thanks kblok!


updating installation info and example notebook to reference mvn repo

addressing #19

need to change java 11 references to java 8


Separate update-check method for client

Description
The client currently has a single Client.update() method that checks for available updates and asks for confirmation via the command line before downloading and applying the update:
https://github.com/dennisvang/notsotuf/blob/1321f81b499c36c743287de3c6e1106bdb01344c/src/notsotuf/client.py#L84
This works for simple applications, but a separate update-check method would provide more flexibility.
Current:
notsotuf_client = Client(...)
notsotuf_client.update(...)

Proposed:
notsotuf_client = Client(...)
if notsotuf_client.check_for_updates(...):
    notsotuf_client.update(...)

Looking forward to this.
Feel free to tag me on relevant issues I can help with :)

Ohh. And in addition, it would also be nice to be able to provide a callback, for update progress monitoring, when the app being updated is a gui application

@NicklasTegner Thanks, happy to see you're interested. I would actually prefer to stick with pyupdater and improve that, but as there does not seem to be any activity there, I decided to create a minimal implementation based on tuf myself.
As for the progress-callback: I agree that would be nice to have, but it is python-tuf that does all the network handling (downloading), and, as far as I can see, they do not offer such functionality. Perhaps there is a way around that, e.g. via the underlying requests pacakge, but I would have to look into that some more.
In any case, my aim with notsotuf is to keep things as simple as possible, to minimize the maintenance burden.

@dennisvang  kind of answered my question already.
But just want to clarify.
Do you plan to make this into a viable solution in production (to switch from PyUpdater to this), or is this only a minimum viable product?

@NicklasTegner I am currently working to make notsotuf production ready, and plan to maintain it that way.
Our company's applications are going to be migrated from pyupdater to notsotuf, so that is my incentive for making sure everything works.
To minimize the amount of maintenance required, I do want to keep the number of "bells and whistles" to an absolute minimum.
So, the goal is for notsotuf to be production-ready, but it will not be a drop-in replacement for pyupdater in terms of extra functionality.
A bit more background
Basically, we use python-tuf as a means to download files securely. It handles all aspects related to file manifests and file authenticity, including cryptographic signing on the repo side, as well as downloading files and verification of file authenticity on the client side.
However, python-tuf only knows about a "list of files" (targets) and a way to distribute these files securely. It does not know what these files are. It assumes that a client already knows which specific file they want to download, and it stops once that file has been downloaded and verified. It does not do anything with the downloaded file. It is unaware of any "application versions".
This is where notsotuf steps in: notsotuf knows two specific types of file, viz. application archives and patches, and provides a layer around python-tuf that defines an "application version" (PEP440). It knows how to check the manifest to determine which files need to be downloaded. This is all very similar to pyupdater.
On the client side, based on the "application version", we determine whether an update is available, and, if so, allow the user to decide if they want to download, extract, and "install" the update, again very much like pyupdater.
The installation part is platform dependent, and, whereas pyupdater provides several built-in ways to handle this "installation" on different platforms, notsotuf only provides one way (currently only for Windows), out-of-the-box. Nevertheless, we do allow the app developer to provide their own, platform specific, callable to handle the installation part, as mentioned in issue #6.
On the repo side, notsotuf provides some tools to set up a basic TUF repository, e.g. creating keys, initializing file manifests, and updating them. We also provide some tools to create gzip archives and patches. We do not make any assumption as to what is inside the archive. Whereas PyUpdater is built around PyInstaller, notsotuf does not care what you use to build your application (could be PyInstaller, could be something else).
Other PyUpdater functionality that is not supported by notsotuf (out-of-the-box):

upload plugins to upload files to a server, for example to AWS S3
asset updates (although these are basically supported via the underlying python-tuf)

that is all fine and all. I would suggest the following features from PyUpdater should also be ported over

A cli interface to manage building, signing and placing files in the right place.
As I said in another issue, MacOS support

I can do the above, when the library is more mature, if you'll like

A cli is already a work in progress, but I'm currently playing around to figure out the most convenient implementation before publishing.
Building will not be supported by notsotuf. I use PyInstaller separately, and just point notsotuf to the resulting pyinstaller bundle.
Of course, your help is much appreciated. :-)

Would very much like to help. What can I start working on, that you aren't alreadytoying around with on your end?

@NicklasTegner I could assign you to issue #6, if you wish?

yes. That sounds good :)


Adding ixnayokay sales channel

probs should hold off merging until @chefboyarsky confirms artbot is added to his server and has permissions to post in this channel

Sounds good, I'll hold off until he's able to confirm 👍🏻

looks like i need to fix something with the build-check too so that forks are able to merge like this...

All 3 PRs are failing from an undefined token (they all have this build error). Is ARTBOT_IS_PROD a newer var and do you think it could be a part of the problem?
Run timeout [1](https://github.com/ArtBlocks/artbot/actions/runs/3868162140/jobs/6608826408#step:5:1)m yarn start || ( [[ $? -eq 124 ]] && echo "WARNING Timeout reached, but that's OK" )
yarn run v1.22.1[9](https://github.com/ArtBlocks/artbot/actions/runs/3868162140/jobs/6608826408#step:5:10)
$ ts-node src/index.ts
ARTBOT_IS_PROD:  undefined
Server is listening on port  3001
/home/runner/work/artbot/artbot/node_modules/discord.js/src/client/Client.js:214
    if (!token || typeof token !== 'string') throw new DiscordjsError(ErrorCodes.TokenInvalid);

The bot should be added with permissions to post in the channel


WIP: Disallow multiple events

Check if there is already another event running for the same advisory.

@qixiang Can you please take a look if this is what you meant in the ticket?
https://issues.redhat.com/browse/CWFHEALTH-688

@qixiang Please review.

@qixiang I fixed everything. Please review again.

LGTM


update reva to include spaces shares improvements

This PR introduces the changes for this issue: https://github.com/owncloud/ocis/issues/3370
tl;dr: All members of a space can list the shares in that space, even if they didn't create those shares.

:boom: Acceptance test Core-API-Tests-ocis-storage-4 failed. Further test are cancelled...


SignalEntry with csv file + refactorings

new

added option to read & write signal entries with csv files
changed writing of binary signal entries to match the reading

changed

moved channel naming and data type inference to separate methods
simplified _get_index and Entry.add_entry, CustomAttributes.to_element
-> caution: stacked entries will still be removed only partially with remove_entry()
separated remove_entry method for unisens class
restricted read_unisens to internal use
fixed writability of attrib when passed at initialization
setting kwargs always with set_attrib independent of passing to init or set_data
removed cause for _autosave exception: always have a _parent attribute (even when copying)
removed unreachable code and removed 'return True' where raising exceptions instead of  returning False
refactored paths: no addition of strings, using os.path...
many minor additions in formatting, typing, comments and docstrings

Thanks for the PR, I'm no longer involved with the project, so I'm currently not able to review it.
Do you want to take over maintenance for now?

Ok, I can take on the maintenance for now as I'm using the package a lot currently.

@jottenbacher could you add @Saskia-K as a collaborator with the corresponding rights?

(not sure if @jottenbacher actively reads github, maybe you want to shoot him an email instead referencing this PR)

Updated description of changes:
new

added option to read & write SignalEntry with csv file

changed

moved channel naming and data type inference to separate methods
simplified Entry._get_index() and Entry.add_entry(), CustomAttributes.to_element()
-> caution: stacked entries will still be removed only partially with Entry.remove_entry()
separate remove_entry method for Unisens class
fixed writability of attrib when passed at initialization
setting kwargs always with set_attrib independent of passing to __init__ or set_data
removed cause for exception in Entry._autosave(): always have a _parent attribute (even when copying)
removed unreachable code and removed 'return True' where raising exceptions instead of returning False
refactored paths: no addition of strings, using os.path...
many minor additions in formatting, typing, comments and docstrings

deprecated

read_unisens: will be restricted to internal use
SignalEntry.get_data() default value for argument scaled: will change from True to False, matching Java implementations SignalEntry.read() and SignalEntry.readScaled()
SignalEntry.get_data() argument return_type: argument is unused and will be removed
Entry subclass CustomAttribute: no use since it doesn't match CustomAttributes.add_entry(); usable alternative is CustomAttributes.set_attrib()

Updates to the last description of changes:
new

added option to read & write SignalEntry with csv file

changed

moved channel naming and data type inference to separate methods
simplified Entry._get_index() and Entry.add_entry(), CustomAttributes.to_element()
-> caution: stacked entries will still be removed only partially with Entry.remove_entry()
separate remove_entry method for Unisens class
fixed writability of attrib when passed at initialization
setting kwargs always with set_attrib independent of passing to __init__ or set_data
removed cause for exception in Entry._autosave(): always have a _parent attribute (even when copying)
removed unreachable code and removed 'return True' where raising exceptions instead of returning False
refactored paths: no addition of strings, using os.path...
many minor additions in formatting, typing, comments and docstrings

deprecated

read_unisens: will be restricted to internal use
SignalEntry.get_data() default value for argument scaled: will change from True to False, matching Java implementations SignalEntry.read() and SignalEntry.readScaled()
SignalEntry.get_data() argument return_type: argument is unused and will be removed
Entry subclass CustomAttribute: no use since it doesn't match CustomAttributes.add_entry(); usable alternative is CustomAttributes.set_attrib()
SignalEntry / ValuesEntry.set_data() will require channel names (deprecating the automatic naming). They can be supplied by passing the argument ch_names or by copying and passing the channel attribute from another entry. In the future, channels will be used to verify data orientation.

@skjerns would you please add me as collaborator for the corresponding PyPI project or upload the new release yourself?

sure, what's your username there?

Might make sense to create a GitHub action for automatic wheel upload on release creation
e.g. using https://github.com/pypa/cibuildwheel

Yes, my PyPI user name is Saskia-K too.
For the extensive version of an automatic upload, I currently don't have the capacity. I can set up a basic actions script though.

Perfect, then I added the right Saskia-K. Let me know if there's anything else I can do.

Sorry for the late reply. Shouldn't I have received an email or anything for the PyPI access? This is my account: https://pypi.org/user/Saskia-K/

Nope, @jottenbacher needs to do that or give you full repo admin rights.

@mkirst just added my token for us. So we can test the workflow with the next release. I uploaded version 1.5.0 manually yesterday.


Merge KTX compare tests to main

This MR contains all tests for the ktx compare tool, alongside other changes related to fixes needed to be done in order for ktx compare to work as expected (including the fixes related to the handling of the D24S8 format).
@MarkCallow, @lexaknyazev, FYI.

Ran into the GitHub 3000 file limitation again. Looked at a random sample of the tests locally. They seem reasonable. Clearly I've not been able to review every file.


[Feature proposal] Additional width ch 50-70

This is a feature idea.
What the ch unit is
In  short it calculates the with by the number of characters in a text.
https://meyerweb.com/eric/thoughts/2018/06/28/what-is-the-css-ch-unit/
Optimal text line length 50-70

https://baymard.com/blog/line-length-readability
https://ux.stackexchange.com/questions/108801/what-is-the-best-number-of-paragraph-width-for-readability

Tailwind suggestion
As soon as I was aware of the ch unit I use it on every site. I think people in general are not yet aware of it.
I suggest three good widths:

.w-ch-50
.w-ch-60
.w-ch-70

Update 2020-05-01
After thinking about it more, the max-width is more important. Also alpabetically names may be more Tailwind like.
.max-w-ch-sm
.max-w-ch-md
.max-w-ch-lg

Unfortunately IE11 treats ch very differently to other browers which, in my experience, makes it pretty useless if you have to support IE11.

@nternetinspired When looking into it, you are right.
https://caniuse.com/#feat=ch-unit

IE supports the ch unit, but unlike other browsers its width is that specifically of the "0" glyph, not its surrounding space.

On the other hand IE11 is now 7 years old. I'm not sure how long it's going to be supported by Tailwind? Not forever hopefully. Personally when building stuff I support 2 major versions back. I think that is a common pattern.
Grid is supported by Tailwind, but not supported by IE11. It's also pretty useless if you have to support IE11, but awesome for the rest of us.

The issue is not that it isn't supported, the issue is that is leads to radically different results. Besides, you can get the same results, with x-browser consistency, using em instead.

Unfortunately IE11 treats ch very differently to other browers which, in my experience, makes it pretty useless if you have to support IE11.

I think a warning about Internet Explorer support should be enough. If you still need IE support (poor dev), either don't use ch or use some hack to support it.

The issue is not that it isn't supported, the issue is that is leads to radically different results. Besides, you can get the same results, with x-browser consistency, using em instead.

em units are exactly one-half a ch unit. So 70ch is the same as 35em. If you can do math, then you don't need to worry about using ch units. The one main "gotcha" is with rem units. rem is based on root font size, whereas em and ch are based on their direct or nearest parent element. As of right now...tailwind predominately uses rem units. I would argue that em units would be more useful than ch units with tailwind since they have better browser support.

em units are exactly one-half a ch unit.

There are not, check out this demo:
https://codepen.io/royvanv/pen/ZEQwKML

em units are exactly one-half a ch unit. So 70ch is the same as 35em.

This is not correct. While both are relative units, the width of ch is tied to a single glyph, 0 and will vary by typeface.

I would argue that em units would be more useful than ch units with tailwind since they have better browser support.

Whilst I am personally a fan of using em for typography, I would argue that using rem for layout spacing provides a far more predictable and consistent experience, espescially to novices, as you do not have to consider the cascading nature of css. With em you really have to understand and embrace the cascade. In a utility-first approach like Tailwind's, predictability is a huge plus point and, IMHO, greaty outweighs most other concerns.
In browser support terms, if you are not supporting IE8 then rem support is a non-issue. IE has supported rem since 2011.


Replace dict() with {}

What does this PR do?

Replaces dict() with {} in the entire codebase.
Before submitting

[ ] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[X] Did you read the contributor guideline, Pull Request section?
[X] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests? [not needed for typos/docs]
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] If you made a notable change (that affects users), did you update the CHANGELOG?

PR review

[X] Is this pull request ready for review? (if not, please submit in draft mode)

Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃
CC: @akihironitta

Just for the record, see also: https://github.com/PyTorchLightning/pytorch-lightning-bolts/pull/455#discussion_r544219231


Ensure all roles are properly tagged

role_name
role-name
role_name_debug
role-name-debug

Completed with commits:

a37949aa689587c435a66611f1d9ac69b6e9f2c2
2fc1cbdcb2246266a862449a41b04d63ac466ed0


Migrate LSBC Prod Agent to Askar and wire to endorser service

These configurations have already been deployed and tested.  Details here; https://github.com/bcgov/DITP-DevOps/issues/83


code of lambda is None after build

Hi , It seems\ __code__ can only use for function after build.For lambda, it will become None, the example is:
def func(a,b):
    return a+b
print("func __code__:", func.__code__)
out : ('func __code__:', <code object func at 0x7f7bc5b71e40, file "hello.py", line 2>)

lam = lambda a, b: a+b
print("lam __code__:", lam.__code__)
out : ('lam __code__:', None)

and my setup.py is as follows
from Cython.Build import cythonize
from distutils.core import setup

setup(name="Hello",
	ext_modules=cythonize("hello.py"))

I use python3 setup.py build_ext to build and then import .so
is this a bug or I use it wrong, thanks

Looks like a bug to me. There is no reason why lambdas shouldn't have code objects. Probably just an oversight.
PR welcome.


Add flood filter

https://www.w3.org/TR/SVG11/filters.html#feFloodElement

Any news on this?

Any news on this one?


[#69] Deprecate build.s2i.galleonLayers and build.s2i.featurePacks

Add notes that these fields are deprecated and using
wildfly-maven-plugin is the recommended way to provision WildFly during
S2I.
The build.s2i.featurePacks field must now specify all feature packs
(including WildFly own) if build.s2i.galleonLayers is set.
This fixes #69.
Signed-off-by: Jeff Mesnil<EMAIL_ADDRESS>

@jfdenis, could you please review?


add column_display_actions option to ModelView

Adds the column_display_actions option to ModelView to allow for hiding the row actions column without modifying list.html. Useful for when you don't want the blank column to appear when you have can_edit, can_delete, and can_view_details disabled.
column_display_actions=True (default):

column_display_actions=False:

This approach preserves backwards compatibility for projects that have can_edit + can_delete disabled and have custom row actions.
Discussion about this is here: #1005

Probably a good idea to review this one with whitespace differences disabled: https://github.com/flask-admin/flask-admin/pull/1069/files?w=1

@pawl can you resolve conflicts?

@mrjoes Done


chore: update license list

I simply updated the license list with the command : go run scripts/generate-licenses.go

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@d9a0ba2). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #9436   +/-   ##
=========================================
  Coverage          ?   41.49%
=========================================
  Files             ?      570
  Lines             ?    74324
  Branches          ?        0
=========================================
  Hits              ?    30842
  Misses            ?    39644
  Partials          ?     3838

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 d9a0ba2...486e995. Read the comment docs.


Only s removal

please accept this pull request this will mean a lot to me.

@AchintKr I would love to, but this isn't grammatically correct or would be in my best interest legally. "persons" is more legally correct; I hope you understand. Feel free to open a PR with any other improvements you see fit and I can review 'em and git it merge.


Update tutorial w/ npx script

Checklist

[x] Use a separate branch in your local repo (not master).
[x] Test coverage is 100% (or you have a story for why it's ok).

Hey @mgmarlow thanks for the PR!
npx is great, but since this is the very first article that users are likely to encounter in the docs, I'd prefer to keep the number of concepts low.
Most people are familiar with npm, but may not know what npx is.
Is there anything else on the docs that you think could use improvement?

@nicolodavis Thanks for the quick reply on this one, this is just something that popped out at me after running through the create-react-app docs. Haven't had any other issues running through the rest of the docs.

That's good. People have often had trouble with the multiplayer section. Did everything work as intended for you?


lfs: 1.3.1 -> 1.4.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/Canop/lfs/releases.
meta.description for lfs is: "Get information on your mounted disks"
meta.homepage for lfs is: "https://github.com/Canop/lfs"
meta.changelog for lfs is: ""
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
/nix/store/ljnd4434qdiad3zyignhczfri5d5mgyg-lfs-1.4.0/bin/lfs passed the binary check.
1 of 1 passed binary check by having a zero exit code.
1 of 1 passed binary check by having the new version present in output.
found 1.4.0 with grep in /nix/store/ljnd4434qdiad3zyignhczfri5d5mgyg-lfs-1.4.0
found 1.4.0 in filename of file in /nix/store/ljnd4434qdiad3zyignhczfri5d5mgyg-lfs-1.4.0

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

4 total rebuild path(s)

2 package rebuild(s)

2 x86_64-linux rebuild(s)
2 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
docbookrx
lfs

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ljnd4434qdiad3zyignhczfri5d5mgyg-lfs-1.4.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A lfs https://github.com/r-ryantm/nixpkgs/archive/a2f83d086916c74b4f8db83b7d22c8ea339a35c0.tar.gz

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

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

lfs

Maintainer pings
cc @k0ral for testing.

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

1 package built:

lfs


Refactor and Clean

Track agent's position as a field inside the Agent struct (as opposed to a field inside the environment struct)
Factor out (env::AbstractGridWorld)(::MoveForward) behaviour for vanilla goal-based environments (EmptyGridWorld, FourRooms, SequentialRooms)
Add method get_world_with_agent to make terminal rendering more modular.
Add method get_num_objects, just like get_height and get_width
Little bit of cleaning up here and there.

Codecov Report

Merging #86 (fea893c) into master (5e59b36) will decrease coverage by 0.84%.
The diff coverage is 63.63%.

@@            Coverage Diff             @@
##           master      #86      +/-   ##
==========================================
- Coverage   75.68%   74.84%   -0.85%
==========================================
  Files          15       15
  Lines         658      640      -18
==========================================
- Hits          498      479      -19
- Misses        160      161       +1

Impacted Files
Coverage Δ

src/terminal_rendering.jl
0.00% <0.00%> (ø)

src/abstract_grid_world.jl
65.07% <68.96%> (+5.50%)
:arrow_up:

src/envs/collectgems.jl
97.77% <100.00%> (-2.23%)
:arrow_down:

src/envs/doorkey.jl
96.55% <100.00%> (-1.73%)
:arrow_down:

src/envs/dynamicobstacles.jl
98.46% <100.00%> (-1.54%)
:arrow_down:

src/envs/emptygridworld.jl
100.00% <100.00%> (ø)

src/envs/fourrooms.jl
100.00% <100.00%> (ø)

src/envs/gotodoor.jl
100.00% <100.00%> (ø)

src/envs/sequentialrooms.jl
99.16% <100.00%> (-0.07%)
:arrow_down:

src/grid_world_base.jl
74.46% <100.00%> (+2.72%)
:arrow_up:

... and 5 more

Continue to review full report at Codecov.

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


Feature Request: More specific Verification Status

I love the SmartyStreets integration with NPSP 3! I've been looking through my "Pending Verification" addresses and I notice that the API Response has much more useful information than the Verification Status. API Response says things like, "Invalid Zip Code" and "Conflicting Zip Code/City/State" and "Invalid City for given State". I was hoping that you could add that kind of information into the Verification Status field.

Glad you like it! "Pending verification" should be the status we give the address only until we receive the response from SmartyStreet. Once we do, it should change, even if the verification isn't successful. For example, this is where we set the status when the zipcode is invalid: https://github.com/SalesforceFoundation/Cumulus/blob/dev/src/classes/ADDR_SmartyStreets_Validator.cls#L256
There are definitely things to improve with the address validation integrations. If by any chance you are interested in contributing to the project in this area, just let me know. I could help you get set up.

I've got about 50k records with Verification Status = Pending Verification
so it looks like it's not always being updated. Should the be a bug request
then? I would be happy to help in any way I can, but I'm not a developer
(I'm a certified SF consultant). Are there still ways I can lend a hand?
On Fri, Feb 27, 2015 at 11:30 AM, Carlos<EMAIL_ADDRESS>wrote:

Glad you like it! "Pending verification" should be the status we give the
address only until we receive the response from SmartyStreet. Once we do,
it should change, even if the verification isn't successful. For example,
this is where we set the status when the zipcode is invalid:
https://github.com/SalesforceFoundation/Cumulus/blob/dev/src/classes/ADDR_SmartyStreets_Validator.cls#L256
There are definitely things to improve with the address validation
integrations. If by any chance you are interested in contributing to the
project in this area, just let me know. I could help you get set up.
—
Reply to this email directly or view it on GitHub
https://github.com/SalesforceFoundation/Cumulus/issues/1412#issuecomment-76423357
.

No worries. We can keep tracking this issue here. Could you maybe provide
some screenshots and a reproducible case?
On Fri, Feb 27, 2015 at 1:35 PM, NathanSpiwak<EMAIL_ADDRESS>wrote:

I've got about 50k records with Verification Status = Pending Verification
so it looks like it's not always being updated. Should the be a bug request
then? I would be happy to help in any way I can, but I'm not a developer
(I'm a certified SF consultant). Are there still ways I can lend a hand?
On Fri, Feb 27, 2015 at 11:30 AM, Carlos<EMAIL_ADDRESS>wrote:

Glad you like it! "Pending verification" should be the status we give the
address only until we receive the response from SmartyStreet. Once we do,
it should change, even if the verification isn't successful. For example,
this is where we set the status when the zipcode is invalid:

https://github.com/SalesforceFoundation/Cumulus/blob/dev/src/classes/ADDR_SmartyStreets_Validator.cls#L256

There are definitely things to improve with the address validation
integrations. If by any chance you are interested in contributing to the
project in this area, just let me know. I could help you get set up.
—
Reply to this email directly or view it on GitHub
<
https://github.com/SalesforceFoundation/Cumulus/issues/1412#issuecomment-76423357

.

—
Reply to this email directly or view it on GitHub
https://github.com/SalesforceFoundation/Cumulus/issues/1412#issuecomment-76447125
.

Carlos,
I have over 5,000 records with "Pending Verification" and an API response
(Invalid Zip, Conflicting Zip/City/State Information etc.). I'm not sure
how to reproduce it. I've just been importing and updating contact
addresses. Maybe using the Bulk API has something to do with it? Let me
know if there's anything else you need from me.
[image: Inline image 1]
On Fri, Feb 27, 2015 at 2:02 PM, Carlos<EMAIL_ADDRESS>wrote:

No worries. We can keep tracking this issue here. Could you maybe provide
some screenshots and a reproducible case?
On Fri, Feb 27, 2015 at 1:35 PM, NathanSpiwak<EMAIL_ADDRESS>wrote:

I've got about 50k records with Verification Status = Pending
Verification
so it looks like it's not always being updated. Should the be a bug
request
then? I would be happy to help in any way I can, but I'm not a developer
(I'm a certified SF consultant). Are there still ways I can lend a hand?
On Fri, Feb 27, 2015 at 11:30 AM, Carlos<EMAIL_ADDRESS>wrote:

Glad you like it! "Pending verification" should be the status we give
the
address only until we receive the response from SmartyStreet. Once we
do,
it should change, even if the verification isn't successful. For
example,
this is where we set the status when the zipcode is invalid:

https://github.com/SalesforceFoundation/Cumulus/blob/dev/src/classes/ADDR_SmartyStreets_Validator.cls#L256

There are definitely things to improve with the address validation
integrations. If by any chance you are interested in contributing to
the
project in this area, just let me know. I could help you get set up.
—
Reply to this email directly or view it on GitHub
<

https://github.com/SalesforceFoundation/Cumulus/issues/1412#issuecomment-76423357

.

—
Reply to this email directly or view it on GitHub
<
https://github.com/SalesforceFoundation/Cumulus/issues/1412#issuecomment-76447125

.

—
Reply to this email directly or view it on GitHub
https://github.com/SalesforceFoundation/Cumulus/issues/1412#issuecomment-76451623
.

The main problem is that when the address is invalid, we don't change the status from "Pending Verification" to anything else. It's verified in the sense that we have sent the verification request (we don't want to send it again), but it's not valid, so we never change the status. We just need to add the error info from the response.
I believe we give more granular information regarding the problem with the address if we are using the SmartyStreets zipcode endpoint, but not if we are using the address endpoint.

That sounds like a great improvement. Thanks!
On Wed, May 13, 2015 at 12:35 PM, Carlos<EMAIL_ADDRESS>wrote:

The main problem is that when the address is invalid, we don't change the
status from "Pending Verification" to anything else. It's verified in the
sense that we have sent the verification request (we don't want to send it
again), but it's not valid, so we never change the status. We just need to
add the error info from the response.
I believe we give more granular information regarding the problem with the
address if we are using the SmartyStreets zipcode endpoint, but not if we
are using the address endpoint.
—
Reply to this email directly or view it on GitHub
https://github.com/SalesforceFoundation/Cumulus/issues/1412#issuecomment-101739351
.

**lurch: attach W-007061

Tracking W-007061


⚠ ClamAV has degraded performance

In 0cabd2b, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 88 ms

Resolved: ClamAV performance has improved in 52bc833.


Allow to specify a session configuration per project

Run cargo update
add home_config() (intermediate step)
Add DmuxConf trait

This is my take on #11.
The code is not perfect, but it's a starting point. I cannot afford to spend more time on it, I'm just hoping it'll be helpful.
It adds such -D | profile_from_dir option.
When -D is specified, such as
dmenu -D ~/my/project/dir

then the configuration file is expected to be found within the selected_dir path (~/my/project/dir in the above example).
The name of the config file is currently hardwired to dmux.conf.toml (did I say that the code was just a starting point...?).
Cheers !

I really like the DmuxConf trait idea, I'll be able to look though this in more detail later today, thanks!


wizard: problems and improvements for etl dashboard and step updater

One-liner
This tracking issue will list all problems and improvements for the ETL dashboard and StepUpdater.
Issues

[x] The button “Add all dependencies” in the Operations list becomes useless if one of the dependencies is population, because it suddenly adds lots of dependencies that do not need update. A possible solution would be to have a tick box to ignore population.

[x] The "Clear Operations list" button needs to be pressed twice to work.

[x] Bug: Column "step" in steps_df (from StepUpdater) contains only active steps (since they are the only needed ones). However, "direct_usages" (and probably other columns of dependencies) includes also archive steps. This means that, in the Operations list, when adding direct usages, archive steps suddenly appear (and also the dashboard raises an IndexError when trying to access archive steps in steps_df. Fixed by https://github.com/owid/etl/pull/2448

[x] Bug: Steps:

Add the latest garden step of long_term_crop_yields to the Operations list.
In the Operations list, click on "Add direct dependencies" of long_term_crop_yields.
Click on "Add direct dependencies" of long_term_wheat_yields.
Click on "Add direct dependencies" of faostat_qcl.

An error appears: DuplicateWidgetID: There are multiple widgets with the same key='remove_data://garden/faostat/2024-03-14/faostat_qcl'. To fix this, please make sure that the key argument is unique for each widget you create.

[ ] Bug: Function that writes to dag removes the comment below a step that has been updated. For example, when updating the climate change impacts explorer latest step, it removes the comment of the next step.

[ ] Loading and processing analytics makes VersionTracker and StepUpdater slower. And analytics are only needed for the ETL dashboard. A solution would be to add an optional flag argument to StepUpdater and VersionTracker so that analytics are loaded only optionally. Use it when using it for the dashboard, but not for updates.

Improvements and ideas

[x] It would be useful to be able to interact with the new steps after they have been created. One possibility would be to have a checkbox "Replace steps in operations list with updated ones". Alternatively, add another operations list below the update button for the new steps.
[x] Add a button below the Operations list to remove non-updateable steps from the list.
[x] Add a button below the Operations list to run ETL on all steps in the Operations list.
[ ] owid/owid-issues#1435
[ ] Add a button to each entry in the operations list to edit the metadata of the ETL step.
[ ] Instead of running updater and etl under the hood, it would be good to run it step by step, and have a progress bar (and log?) shown. If that's not possible, at least it would be good to show the logs in the terminal that runs the dashboard (otherwise, you may see something running for a long time, without knowing what's going on).

Hi! I am starting to update World Bank PIP. I selected all the grapher/explorer steps containing world_bank_pip, I added them to the Operations list, then I added all dependencies for the three steps I selected and then I updated the 7 resulting steps.
The files were generated, but the dag was updated not the way I expected:

The garden dependency from the explorer step was replaced, I assume because the platform always considers a date by default and not latest.

The updated steps were added at the bottom without the explorer step mentioned above:

The step updater deleted the comment to distinguish another set of steps from the World Inequality Database:

The step updater also adds the steps right next to the previous dependencies. It would be nice to have a line jump between them:

I think the new folders and files work fine, so I only need to correct the dag. Thank you very much!

Hi @paarriagadap, thanks a lot for reporting these issues! The issue of removing comments is already known (listed above). I'll try to fix that soon.
If I understand correctly, the issues are related to the formatting of the written files (either the dag or the snapshot metadata files), but the step updater is behaving as expected. In other words, the code generated by the tool is correct, although not great in terms of style. Is that right?
Currently, the step updater either (1) writes new steps in the dag, or (2) overwrites dependencies of existing steps. Steps with "latest" version correspond to case (2) because the step already exists, and its dependencies need to be updated. So you would prefer those updated "latest" steps to be moved the bottom of the dag, as if they were new steps. Is that right?
Please let me know if I misunderstood your issues. Thanks!

Hi @pabloarosado, yes, it's mostly formatting and that is better that the latest steps go to the bottom (or it's replicated in both old and new steps). Thank you!
A tiny one I found now is that I had an additional script to extract the data from PIP in the snapshot folder (pip_api.py here), and it wasn't copied to the new step, while there are shared.py scripts in garden that were carried over to the new steps.

Thanks for the clarification, I added the suggestion about "latest" steps to the list of improvements.
Regarding pip_api.py file, I think that's expected. The expected scenario is that there is only one code file per snapshot. In this case, that file is actually not generating snapshot, so it's a bit of a special case. Maybe we can figure out a solution for it, but I guess it's very uncommon.


popular section changes added issue no#50

@adityakmrmishra plz accept my pr

Hi, @farehax pls open issue before making pr or atleast provide a description for pr .

this issue is already assigned to me by @GuryonAnkit

Hi, @farehax pls open issue before making pr or atleast provide a description for pr .

you can check issue no #50

Hi, @farehax pls open issue before making pr or atleast provide a description for pr .

you can check issue no #50

From next time provide a small description of

Hi, @farehax pls open issue before making pr or atleast provide a description for pr .

you can check issue no #50

From next time remember to put description of pr it's a good practice and mention the issue no in it 🙂


Outdated typings?

For some reason, the npm module seems to have outdated typings -
    export class AkairoClient extends Client {
        public constructor(options: AkairoOptions, clientOptions: ClientOptions);

        public akairoOptions: AkairoOptions;
        public commandHandler: CommandHandler;
        public databases: Object;
        public inhibitorHandler: InhibitorHandler;
        public listenerHandler: ListenerHandler;
        public mem: Object;
        public ownerID: string | string[];
        public selfbot: boolean;
        public util: ClientUtil;

        public addDatabase(name: string, database: SQLiteHandler): this;
        public build(): this;
        public loadAll(): void;
        public login(token: string): Promise<string>;
    }

is the definition it is using, rather than what is found in this repo

Ah, looks like 7.x is the release branch at the moment. The typings should probably be fixed there


Add discord link to new uptane site

Link to discord invite here.
https://discord.gg/uWyT6gDCqx

Hey, just created a PR for the same

Please assign the issue to me


Should there be a PassLine bet placed initially after a new shooter for the Place682Come Strategy?

Currently, if a player is using the Place682Come strategy and the table is new (meaning no bets and point is Off) or there is a new shooter they will not place a PassLine bet. They wait until the point is Off and the player has either a Place6 or a Place8 bet to place a PassLine bet. Is this the correct way this strategy is supposed to work?
It would seem to me like the Player would want to place the PassLine bet initially, and then if the PassLine point is 6 or 8 Place the 5 or 9 and either the Place6 or Place8 depending on the PassLine point, and then the added Come bet. This would have the same desired outcome of getting the four distinct numbers.  Currently, it seems like it is artificially increasing the number of rolls the strategy would last as it is arbitrarily waiting to bet the PassLine until after a point has already been established and completed.

The strategy is correct as you understand it. It's interesting to test strategies that don't use the pass line and don't pass bets because they are less correlated to the way that most people play.

That's where the confusion is though. I could see that being true if the player never places PassLine bets. This strategy does use PassLine bets, it just waits until the player has a Place6 or Place8 bet to do it:
    if player.num_bet("Come", "PassLine") < 2 and len(player.bets_on_table) < 4:
        if table.point == "On":
            player.bet(Come(unit))
        if table.point == "Off" and (
            player.has_bet("Place6") or player.has_bet("Place8")
        ):
            player.bet(PassLine(unit))

For consistency should place68_dontcome2odds work the same way in that it does a DontPass at some point? Right now that one never places a DontPass bet.

Yeah, probably that would be best for consistency.  I don't think I ever published results with that strategy so we can modify.  It's not a high priority issue though


Release 0.3.0 -- update to cloudflare provider version 4

Changed (breaking)

Use new content attribute in place of deprecated value attribute on cloudflare_record resources. Requires Cloudflare provider version 4.

@briskt It looks like this feature branch didn't get automatically deleted after the merge. Is it still needed for anything? (Just trying to catch this while we're more likely to still remember, rather than in a year or two when we come back to clean things up.)

@briskt It looks like this feature branch didn't get automatically deleted after the merge. Is it still needed for anything? (Just trying to catch this while we're more likely to still remember, rather than in a year or two when we come back to clean things up.)

Thanks for noticing that. You've got a good eye!


nom::combinator::not doesn't give back result

Hi,
first of all: thanks a lot for this crate and the work you put into it!
I am trying to parse a string til some tag arrives, like "give me any char until $tag". I could use a regexp but I thought using not(tag("some string") would be easier to understand and make things more clear.
However, the code doesn't compile, since not gives back () and not the parsing result.
Prerequisites

Rust version : rustc 1.46.0 (04488afe3 2020-08-24)
nom version : 5
nom compilation features used: regexp
user status: total rust newbie

Test case
Example test case:
#[macro_use]
extern crate nom;
use nom::bytes::complete::tag;
use nom::combinator::not;

fn not_eof (i: &[u8]) -> IResult<&[u8], &[u8]> {
    let (i, value) = not(tag("eof"))(i)?;
    Ok((i, value))
}

fn eof_test() {
    assert_eq!(not_eof(&b"stuffEOF"[..]), Ok((&b"EOF"[..], &b"stuff"[..])));
}

This doesn't compile, I get (ignore the line numbers, my actual source file is larger):
error[E0308]: mismatched types
   --> src/parser.rs:296:12
    |
296 |     Ok((i, value))
    |            ^^^^^ expected `&[u8]`, found `()`

I can't tell if I misunderstood the docs or if it's a bug. Any help would be much appreciated anyway!
Thanks in advance,
Tom

Silly me! This does the job: take_until("eof").
:)


Notifications dismiss themselves

I use the dlang.org install script to install LDC. Nova has trouble finding my D installation in the environment. Regardless, this extension shows error notifications while trying to initialize the language server.

These notifications dismiss themselves after less than about 6 seconds. Notifications from Nova itself and other extensions let me read and dismiss them myself.

Yeah, I think for error notifications like this we should do that.  I think part of this is how serve-d uses the LSP API to send these notifications -- I don't think they are classed as "errors" needing to be acknowledged.
I know that for other ones, like the "Language server restarted." notification, they are meant to be auto-dismiss, because there is no further user action needed.  But notices that need to be acknowledged or corrected should not automatically dismiss.

@webfreak001 - any ideas here?

these notifications are sent as error messages / have MessageType error - so probably a bug on your end? They stay there on vscode; unless of course it comes from restarting the language server, where it might clear the notifications from the previous run (vscode doesn't do that though, although there is no specification what to do)

Errors are displayed using nova'sworkspace.showErrorMessage API and warnings are displayed using workspace.showWarningMessage.
These don't provide any way to make the display modal. Nova claims it may bring the workspace to the foreground, but it says nothing about requiring confirmation, and there is no way to make them so using that API.
I think this is a limitation of Nova itself.

I'm going to close this for now, because there is no way I can do anything more with it.  I'll also submit this to the Nova people.

One option here is to use a NotificationRequest instead of workspace.showErrorMessage. It's not documented well, but if you don't add actions the notification will auto-dismiss. But if you do add actions the alert will stay on the screen until dismissed.


enableWholeSummaryUpload for azure-client

This enables support for the new version Azure Fluid Relay being deployed for Public Preview.

@znewton For context, the plan is to have AzureClient always use the "SummaryStorage" as oppose to git. So we decided to turn the flag on by default. I believe thats the only thing we need to tweak, but double checking just in case.

For context, the plan is to have AzureClient always use the "SummaryStorage" as oppose to git. So we decided to turn the flag on by default. I believe thats the only thing we need to tweak, but double checking just in case.

Yes, that's correct!


[NEW FEATURE] Delete / Remove containers

Describe the solution you'd like
I would like an additional option to delete / remove containers. The current cotnainer options are start, pause, restart, and stop.

Thanks, yeah it should really have that feature.
I think it should probably pop-up a warning (akin the the help panel), displaying something along the lines of
"Are you sure you want to delete container: [container-name]"?
And then have a continue/cancel button selection?

Yep that sounds perfect!

Don't expect any other features to be implemented this fast! I just happened to be about to release a new version, and was able to introduce it quickly


Switch the default rpc node to mainnet.teia.rocks

mainnet.api.tez.ie has been down for a couple of hours already, people are going to start to notice pretty soon :sweat_smile:

Tchoop tchoop!
What is the reasoning for moving the keys around? If it's to "force" reset user config we can just use versioning on the config

My bad I looked at the commits not the final diff so I was confused.

My bad I looked at the commits not the final diff so I was confused.

yeah sorry, I was fumbling around a bit :laughing:
anyway, it looks like the original node is fixed now https://mainnet.api.tez.ie/chains/main/blocks/head/header but I think switching would still be a good idea
that node hasn't been very stable


Fix InferStorage for sparse fallback in FullyConnected

Description
#11448
Checklist
Essentials

[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[x] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[x] Fix storage fallback in backward

Comments

@eric-haibin-lin

@haojin2 could you write a unit test?

@zheng-da unit test added.

@eric-haibin-lin @zheng-da


[Rancher2] AzureAD integration: Invalid version

Request Summary:
Integration with Azure AD results in Error.
Details:
Despite the old documentation regarding the integration of Rancher 2.6.3 with Azure AD, I've tried to do this. I did everything right except that "Azure Active Directory Graph" that is deprecated and changed to "Microsoft Graph" which as I saw here should not be a problem.
Still I get this error which I cannot figure out which version is invalid.
server error while authenticating: graphrbac.UsersClient#Get: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="BadRequest" Message="Invalid version." InnerError={"client-request-id":"XXX","date":"2022-03-11T10:11:13","request-id":"XXX"}
Thanks for the help in advance.

the code produced by this error will be replaced by efforts in this issue https://github.com/rancher/rancher/issues/29306

Hi. thanks for the follow up.
Is there an estimate in which version the issue will be resolved?

@mokhos , looks like it will be in v2.6.6
https://github.com/rancher/rancher/issues/29306

Closing this, since there is no defect.
@mokhos, the issue was originally resolved in v2.6.7 when Rancher added support for the new flow via Microsoft Graph. The old flow is still supported, but only for existing setups. Rancher encourages to upgrade to the new flow through a simple, one-time operation. For new setups, Rancher allows to configure Azure AD only with the new flow.
Note that there have been changes in subsequent v2.6 and v2.7 releases for the new flow of Azure AD.
Here are the docs for the latest v2.7 release of Rancher:
https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/authentication-config/configure-azure-ad


Added support for client-defined locale detection rules

Added instance property this._localeDetectionRule with, as a default value, the previously hard-coded rule that consists in reading the value of the lang query-string parameter when present;
Added function setLocaleDetectionRule(rule) that allows client code to replace the default locale detection rule with a custom rule;
Moved the locale detection code into its own separate function.
Added TS type signature for the new setLocaleDetectionRule(rule) function.

Yes, of course! How could I have missed that.


Consider setting up GitHub wiki

I think we should consider putting the documentation on the repo’s GitHub wiki section for easier navigation.

as the wiki is not necessarily in sync with the main repository.

What do you mean by this? I don’t see a Wiki to begin with.
Improving readers experience is the main goal of creating a wiki. With a mandate that every code change (via pull request or any other means) should be properly documented. Spdlog, Drogon and many other packages that have their documentation on GitHub use GitHub wiki over a ReadME file. That’s why GitHub wiki was put for repositories.
Having a GitHub wiki is never a bad idea.

What do you mean by this?

What I meant is that while the repository usually contains all previous versions in an organized manner (tags and branches), the GitHub wiki only focuses on the most recent version. For instance, say you have to use spdlog v1.6.1, obviously you'd like to read the documentation for that specific version. But when you go to the wiki, you can't simply select v1.6.1 and read the documentation as it was at the point in time where v1.6.1 got released.
You can view an older version of a wiki page (example), but you don't know whether this one relates to v1.6.1. Also, every link on the wiki will take you back to the up-to-date version.
Neither does a GitHub release (example) provide a copy of the corresponding version of the wiki.
For spdlog, I assume the documentation in the wiki currently refers to v1.x as this appears to be the main branch. But there is also a v2.x branch -- the major version difference suggests that the API has changed substantially. Where do I find the documentation for that branch?
I hope this illustrates my point sufficiently.

Well then GitHub pages will do the trick then. With a GitHub action for new releases. My point is that using just a ReadME file gives poor user experience. Consider giving this an enhancement label. Great project by the way.


Very slow when edit files from other software

I store some of my code in google drive. When I edit my code in some IDEs, such as pycharm, the IDEs become very slow. In addition, most of the operations on the files in google drive folder are much slower compared to the official google drive clients of Windows and Mac. I was wondering is there anything wrong with my configuration? The following is my configuration file. Thank you for your time!
apps_script_format=json
apps_script_icon=
async_upload=true
cache_directory=
client_id=
client_secret=
connect_timeout_ms=5000
curl_debug_off=false
data_directory=
delete_forever_in_trash_folder=false
docs_file_extension=true
document_format=odt
document_icon=
download_docs=true
drawing_format=png
drawing_icon=
form_format=zip
form_icon=
fusion_table_format=desktop
fusion_table_icon=
keep_duplicates=false
large_file_read_only=false
large_file_threshold_mb=16
log_directory=
lost_and_found=false
low_speed_limit=0
low_speed_time=0
map_format=desktop
map_icon=
max_cache_size_mb=15000
max_download_speed=0
max_memory_cache_size=10485760
max_retries=8
max_upload_chunk_size=1099511627776
max_upload_speed=0
memory_buffer_size=1048576
metadata_cache_time=20
presentation_format=pdf
presentation_icon=
read_ahead_buffers=3
read_only=false
root_folder=
shared_with_me=false
spreadsheet_format=ods
spreadsheet_icon=
sqlite3_busy_timeout=5000
stream_large_files=true
team_drive_id=
umask=0o002
verification_code=

Yes it's too slow to be used on daily bases. I'm using Ubuntu 18.04. And when saving plain text files it take like up to 10 seconds for file to saved and program to be responsive. I'm editing in vim.
Can I do anything? Like async save? I'm on version 0.7.0

No, sorry, I had to remove the async upload option because it increased the probability of losing data.


Still failing to login to Azure via https://localhost

Azure Data Studio Version: 1.20.1, 1.21.0-rc1, 1.21.0-insider

Steps to Reproduce:

Click Azure > Sign into Azure... > Add account
Browser window opens at https://localhost:<some_port>/signin?nonce=<some_base64_value>
Nothing else happens

The fact that this is still happening, months after I reported basic usability issues with logging in to Azure (#8331) and after others have reported the same issue (https://github.com/microsoft/azuredatastudio/issues/8829#issuecomment-572046339), gives me very little confidence in the team developing this application.
To be blunt, Azure Data Studio is not fit for purpose. It is broken in the most fundamental ways. Apart from not being able to login to Azure, attempting to launch a profiling session against an Azure SQL DB added via the "Servers" area (the only reason I have this terrible piece of software installed) gives "Cannot profile Azure system databases" (I didn't realise I was trying to do that). Yes, the toast error messages are beautiful, but they don't provide any sort of guidance as to what the actual problem is or how I might go about fixing it. You may as well dump the errors to console.out, they're that useful.
"Open source" does not mean "release to the public without any sort of internal testing". It does not mean "use customers as alpha testers". The Microsoft of a decade ago would never have allowed an application in this state to get into customers' hands. I want that Microsoft back.

@aaomidi any idea why the localhost auth page isn't loading?
@IanKemp have you tried using Device Code auth to add the Azure account?  I don't think that method requires opening a localhost socket.

@IanKemp regarding the SQL Profiler error, the issue there is connections to servers use the master database as the DB for the connection.  So when Profiler is launched from this node it tries to use master, which is blocked on Azure.  A workaround is to specify the database in the connection dialog when creating the connection and launch the profiler from this node.  I'll open a separate bug to resolve this issue as part of taking the SQL Profiler extension out of preview.

The issue here is that your browser has an HSTS tag attached to localhost, this means your browser will force localhost to load with https - and that will just fail.
If you're on edge:

Visit edge://net-internals/#hsts
Delete domain security policies
Enter localhost

If you're on chrome, do the same thing as edge except the address is chrome://net-internals/#hsts. Other browsers have similar settings but I'm not sure where they are.

Please comment back if the hsts problem didn't solve your issue and we can look into it more!


compilation failure with RxJS operators

Known issue, resolved in RxJS beta.0. - awaiting next angular bump to fix.

This should be fixed by 0b663bebbeba7f5551c66d30a7dc8fe07da43d57


Access Denied

System.UnauthorizedAccessException: Access to the path 'C:\Users\Admin\AppData\Local\Bloxstrap\Bloxstrap.exe' is denied.

Where's the log file?

having the same isddue
Bloxstrap_20230925T173330Z.log

Try out the latest build at https://github.com/pizzaboxer/bloxstrap/suites/16541311997/artifacts/944883048.

Relocated to #791


[EN] Feedback for: /web/updates/2015/07/interact-with-ble-devices-on-the-web?hl=en

Linking directly to https://developers.google.com/web/updates/2015/07/interact-with-ble-devices-on-the-web?hl=en#user-gesture-required doesn't scroll to the right place on the page.

Duplicate of #2253

@sgomes @petele please sort asap, this is getting beyond a joke now.  I know we are planning to migrate back into devsite soon but right now we need to get this fixed, people can't use our site.

This is not an MDL issue, as it only affects Web Fundamentals. WF seems to be modifying page and MDL layout styles, and is triggering a Safari bug. Workaround on #3118.

I'm using Chrome.

Bad dupe, sorry. The follow up to this is on #2291.


How do you use the AMD specification?

How do you use the AMD specification?

https://github.com/surmon-china/vue-awesome-swiper/blob/master/dist/vue-awesome-swiper.js
The dist files using the UMD specification, you can use UMD-compatible methods


Add Advisor Configurations API and api-version 2017-04-19

Add Advisor Configurations API to api-version 2017-04-19.
Add Create, Read/List and Update APIs for new Advisor Configuration entity at Subscription and Resource Group scopes.
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[X] The title of the PR is clear and informative.
[X] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[X] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[X] If applicable, the PR references the bug/issue that it fixes.
[X] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[X] I have read the contribution guidelines.
[X] My spec meets the review criteria:

[X] The spec conforms to the Swagger 2.0 specification.
[X] The spec follows the guidelines described in the Swagger checklist document.
[X] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

@johanste / @fearthecowboy would you mind taking a look at the new functionality that is added in this PR too?

Also, for folks reviewing, I've rebase this on my fork to help ignore the whitespace changes that were made as part of this PR. You can see my version here: https://github.com/marstr/azure-rest-api-specs/tree/FixFaceSwagger

The whitespace changes in my change are desired. They came out of a swagger generation tool (Swashbuckle) and not hand-edited. The pre-existing swagger had many one-off edits following generation as well as validation errors that I fixed by making the desired swagger spec directly generated by the tool (for example, the missing int32 format issue was because it was one-off hand-edit, and I fixed it by making it directly associated and generated by code).

yep! for sure @davidwa-msft! We'll make sure to preserve them, but for the sake of reviewing I'd like to isolate them into one commit so that we can consider just the semantic changes that you made. :)

Are there any more concerns to address?
We have updated our swagger to use two-space indents, and we also removed the PATCH verb that we added in this change as we realized it was no longer necessary, so the change is smaller.

Ouch, please don't move the file --
specification/advisor/resource-manager/Microsoft.Advisor/2017-04-19/swagger/advisor.json
should be
`specification/advisor/resource-manager/Microsoft.Advisor/2017-04-19/advisor.json
I'll finish reviewing this today.

I was reading docs and other team's structure and realized that the swagger and the examples should be sibling directories instead of parent/child. So, I first made a commit to move it, then follow up diffs.

I moved the swagger back to the original location and updated the x-ms-examples links to match and pass validation.

No modification for AutorestCI/azure-sdk-for-python

No modification for AutorestCI/azure-sdk-for-node

No modification for AutorestCI/azure-sdk-for-ruby


Tekla Structures Selection of wall elements not working properly

selection of wall elements don't result in sending (selection by hand).

closing as stale


fix incorrect imports/fqn usages

mostly of the form import a.b : sym; a.b.sym();, which is wrong b/c
selective imports do not add the module to the current scope

Please do not merge until we've decided on https://github.com/D-Programming-Language/dmd/pull/5426.

rebased and ready


ISPN-11197 Server JMX Docs

https://issues.redhat.com/browse/ISPN-11197
Needs backport to 10.1.x

Merged, thanks


Add SortPreservingMerge fuzz tester

Which issue does this PR close?
Re https://github.com/apache/arrow-datafusion/issues/1676
Rationale for this change
Despite pretty good testing in SortPreservingMerge there was at least one case that is not yet covered.
What changes are included in this PR?
A "fuzz" tester that tests merging various combinations of streams (broken into multiple batches, as well as various ranges)
Are there any user-facing changes?
No -- this is a testing tool onlt

Marking as a draft as I still plan to add a few more cases to this tester (as I work on #1676 )


Fix helm 3.8 digest validation issues

Our current code does not use the manifest digest when retrieving charts. The digest is not used, and so the clients are falling back to grabbing the highest semver tag.
Helm 3.8 does not support pulling by sha256 as of 3.8.
We need to do two things:

Change our bundle generation to use the version tags in addition to the digest.
Once we pull a chart, verify the sha256 in its manifest against the digest from the bundle.

There is a PR out there, just need to work it through the helm system


Display categories information in its fragment

As a user, I want to display categories in their fragment so that I can see all categories as a list
Acceptance Criteria

I can see categories in its fragment
I can see categories as a ListView

Dependencies

[x] #6

Notes:

Jugoterapia image is just a reference
We expect to see only text without any UI format/icons on the list

References


Best way to handle your rootSaga

First of all, I love using this library in my react redux app to handle all the side effects. But I'm quite confuse what's difference between this approach in composing your root saga function.
See example below.
Example 1:
// fooSaga.js
import {fork, takeLatest} from 'redux-saga/effects';

function* foo() { /* code logic here */}

function* watchFork() {
  yield takeLatest('FOO_SAGA, foo);
}

export default function* rootSaga() {
   yield fork(watchFork);
}

// sagas.js
import {all} from 'redux-saga/effects';
import fooSaga from './fooSaga';

export default function* rootSaga() {
  yield all([fooSaga()]);
}

vs
// fooSaga.js
import {takeLatest} from 'redux-saga/effects';

function* foo() { /* code logic here */}

export default function* watchFork() {
  yield takeLatest('FOO_SAGA, foo);
}

// sagas.js
import {all, fork} from 'redux-saga/effects';
import fooSaga from './fooSaga';

export function* rootSaga() {
  yield all([ fork(fooSaga()) ]);
}

Appreciate your response.

This is just a matter of organizing the code, doesn't matter much - I would only suggest using effects over directly yielding iterators and avoid the unnecessary nesting.
// fooSaga.js
import {takeLatest} from 'redux-saga/effects';

function* foo() { /* code logic here */}

export default function* watchFork() {
  yield takeLatest('FOO_SAGA, foo);
}

// sagas.js
import {all, fork} from 'redux-saga/effects';
import fooSaga from './fooSaga';

export function* rootSaga() {
  yield all([ fork(fooSaga) ]);
}

Thank you for your response. I will close this now.

@Andarist @llauderesv
I have a question about this. if we have more generators in the file fooSaga.js, how can I write it in watchFork()?
e.g.
// fooSaga.js
import {takeLatest} from 'redux-saga/effects';

function* foo() { /* code logic here */}
function* foo2() { /* code logic 2 here */ }

export default function* watchFork() {
  yield takeLatest('FOO_SAGA', foo);
  /* can I write like this? or any better solution */
  yield takeLatest('FOO2_SAGA', foo2);
}

Thanks a lot.

Hi, @alexya.
Yes that would work. But I suggest to separate the logic into two separate files so that your code will much more cleaner.
Like this one.
function* foo() { /* code logic here */}
export default function* watchFork() {
  yield takeLatest('FOO_SAGA', foo);
}

function* foo2() { /* code logic 2 here */ }
export default function* watchFork2() {
  /* can I write like this? or any better solution */
  yield takeLatest('FOO2_SAGA', foo2);
}

// root saga index.js
import {all, fork} from 'redux-saga/effects'
import {watchFork, watchFork2} from './sagas'
export default function* main() {
  yield all(fork(watchFork), fork(watchFork2));
}


Assertion gets thrown when app runs when screen of mobile is turned off using power button

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
Not tested on iOS, because the application is android only.

Created a sample app using flutter create bug.
After running the sample application modify the main.dart file with the code given in code sample section.
Before running it on a real android device, "Make sure the screen of mobile is turned off and locked, by pressing the power button."
Run the app and see the crash. If the screen of mobile is turned on, it doesn't crash.
Also, before doing another test, the app must be uninstalled or it doesn't crash.

Expected results
It should build successfully and run without any errors.
Actual results
When the screen of mobile device is turned off and the app is run, it throws many errors.
Code sample
Code sample
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        body: SafeArea(
          child: LayoutBuilder(builder: (context, constraints) {
            if (constraints.maxWidth > 500) {
              return SingleChildScrollView();
            }
            return SingleChildScrollView(
              child: Column(
                children: [
                  Padding(
                    padding: const EdgeInsets.only(top: 32),
                    child: Text("My Home Page",
                        style:
                        Theme.of(context).textTheme.displayLarge?.copyWith(
                          fontSize: 60,
                        )),
                  ),
                  Padding(
                    padding: const EdgeInsets.all(32),
                    child: Text(
                      "Name",
                      style: Theme.of(context).textTheme.titleLarge,
                    ),
                  ),
                  Padding(
                    padding: const EdgeInsets.fromLTRB(16.0,16.0,16.0, 0),
                    child: Form(
                      child: Container(
                        constraints: BoxConstraints(
                          minWidth: 0.0,
                          maxWidth: MediaQuery.of(context).size.width,
                        ),
                        child: TextFormField(
                            maxLength: 20,
                            initialValue: "",
                            onChanged: (value) {
                              //Handle name change
                            },
                            decoration: const InputDecoration(
                              disabledBorder: OutlineInputBorder(
                                borderSide: BorderSide(
                                  color: Color(0xFF6200EE),
                                ),
                              ),
                              prefixIcon: Icon(Icons.person),
                              labelText: "Name",
                              helperText: "Enter Name",
                              enabledBorder: OutlineInputBorder(
                                borderSide: BorderSide(
                                  color: Color(0xFF6200EE),
                                ),
                              ),
                            ),
                            validator: (value) {
                              if (value!.isEmpty) {
                                return "nameMustNotBeEmpty";
                              } else if (value.length < 3) {
                                return "nameMustHave3OrMoreCharacters";
                              } else {
                                return null;
                              }
                            }),
                      ),
                    ),
                  ),
                  const SizedBox(
                    height: 30,
                  ),
                  ElevatedButton(
                      onPressed: () {
                        //Handle button press
                      },
                      child: const Icon(Icons.done_outlined)),
                ],
              ),
            );
          }),
        ),
      ),
    );
  }
}

Screenshots or Video
No response
Logs
Logs
https://pastebin.com/UsReMKV0

Flutter Doctor output
Doctor output
C:\Users\lenovo>flutter doctor -v
[√] Flutter (Channel stable, 3.10.1, on Microsoft Windows [Version 10.0.22621.1778], locale en-US)
• Flutter version 3.10.1 on channel stable at C:\Users\lenovo\AppData\Local\Flutter\flutter_windows_2.10.3-stable\flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision https://github.com/flutter/flutter/commit/d3d8effc686d73e0114d71abdcccef63fa1f25d2 (6 weeks ago), 2023-05-16 17:59:05 -0700
• Engine revision b4fb11214d
• Dart version 3.0.1
• DevTools version 2.23.1

[√] Windows Version (Installed version of Windows is version 10 or higher)

[√] Android toolchain - develop for Android devices (Android SDK version 34.0.0-rc4)
• Android SDK at G:\Android\Sdk
• Platform android-UpsideDownCake, build-tools 34.0.0-rc4
• ANDROID_HOME = G:\Android\Sdk
• Java binary at: C:\Program Files\Android\Android Studio\jbr\bin\java
• Java version OpenJDK Runtime Environment (build 17.0.6+0-b2043.56-9586694)
• All Android licenses accepted.

[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.11.2)
• Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\Community
• Visual Studio Community 2019 version 16.11.31624.102
• Windows 10 SDK version 10.0.19041.0

[√] Android Studio (version 2022.2)
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin can be installed from:
https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 17.0.6+0-b2043.56-9586694)

[√] VS Code (version 1.79.2)
• VS Code at C:\Users\lenovo\AppData\Local\Programs\Microsoft VS Code
• Flutter extension version 3.66.0

[√] VS Code (version 1.79.0-insider)
• VS Code at C:\Users\lenovo\AppData\Local\Programs\Microsoft VS Code Insiders
• Flutter extension version 3.64.0

[√] Connected device (1 available)
• Windows (desktop) • windows • windows-x64 • Microsoft Windows [Version 10.0.22621.1778]

[√] Network resources
• All expected network resources are available.

• No issues found!

Hi @abhineetchandan. Thanks for filing this issue. I am able to reproduce this issue on the latest master and stable channels. This doesn't occur with the sample main.dart code in newly created flutter project and is replicable only on Android devices.


Docs: Some questions re: Reckless drivers

Are there any restrictions on which vehicles can become reckless drivers (eg. can post vans, busses, ships, planes, etc., be reckless)?
As per discussions in #11, am I correct in saying that reckless drivers will no longer enter blocked junctions (and this also applies to on-call emergency vehicles)?
As per https://github.com/krzychu124/Cities-Skylines-Traffic-Manager-President-Edition/issues/41#issuecomment-461673615 , is it true that reckless drivers will obey custom lane connectors?
How do reckless drivers behave at timed traffic lights?
Do they obey the recently introduced turn on red feature (specifically when a junction does not allow it)?
Do they obey junctions that disallow u-turns?

Are there any restrictions on which vehicles can become reckless drivers (eg. can post vans, busses, ships, planes, etc., be reckless)?

I don't think so. I will check that.

How do reckless drivers behave at timed traffic lights?

They are ignoring traffic lights state (vanilla and timed too)

As per discussions in #11, am I correct in saying that reckless drivers will no longer enter blocked junctions (and this also applies to on-call emergency vehicles)?

They should no longer enter blocked junctions.
Unfortunately it seems that under some unknown conditions for me at one junctions with level crossings (one way bus lane) regular vehicles ignored closed level crossing (with disabled enter on blocked junction option) I've had to delete this node and replace with new to fix this behavior. I have no idea how reproduce that now...

As per #41 (comment) , is it true that reckless drivers will obey custom lane connectors?

I didn't check that yet but it is on my very long TODO list 😃

Do they obey the recently introduced turn on red feature (specifically when a junction does not allow it)?

Doesn't matter because that's still junction with traffic lights, so they ignore it

Do they obey junctions that disallow u-turns?

I have never seen Ambulance doing U-turn 😄

Docs updated: https://github.com/krzychu124/Cities-Skylines-Traffic-Manager-President-Edition/wiki/Reckless-Drivers


[0.7.1] Autocomplete 的键盘选择支持不会更改滚动条位置缺陷

What problem does this feature solve?
希望和nz-select一样在键盘选择项超出时 对滚动条进行重新设定

What does the proposed API look like?

fixed in #1533
will be released in next version.


Modify loopback size

Modify the loopback size in the blockfile snapshotter test setup. Set the loopback size to 16MB when the page size is greater than 4096. This prevents smaller storage devices from running out of free space while the test is running. Addresses issue #8767.

@Jenkins-J would you mind to share the test result? just wonder that 16MiB is good enough for the test. Thanks

@fuweid Here are the test results from the blockfile snapshotter testsuite. I ran the test with go test -v -test.root -run TestBlockfile. If there are any other tests you'd like me to run or a better way to execute the testsuite, let me know.
blockfile-testsuite.txt


Where's Netherboard lastest version (1.2.3) on maven?

        <dependency>
            <groupId>fr.minuskube</groupId>
            <artifactId>netherboard-bukkit</artifactId>
            <version>1.2.3</version>
        </dependency>

fr.minuskube:netherboard-bukkit:jar:1.2.3 was not found
Doesn't work.

Oops, forgot a step to release it! It should be available now, thanks :)

Still was not found.

That must be some cache issue, I don't know how maven handles this, maybe there's a way to clean it. Otherwise, try again in a few hours


Error creating the source Testin

Creating Testin the origin of the route is always http: // localhost although set in config / app.php url => 'http: // localhost / laravel-app / public'
$this->response->original

You need to set the base url in the test case.

@GrahamCampbell ok. in case it is as you would? where I specify the url base. Sorry you do not find where it is. Greetings.


Import deeppavlov in notebook problem

Hi everyone,
I have created a virtuel environment and installed in it deeppavlov
aio-pika==6.4.1
aiormq==3.2.1
certifi==2019.11.28
cffi==1.14.0
chardet==3.0.4
click==7.1.1
cryptography==2.8
Cython==0.29.14
DAWG-Python==0.7.2
deeppavlov==0.8.0
docopt==0.6.2
fastapi==0.47.1
fuzzywuzzy==0.17.0
h11==0.9.0
h5py==2.10.0
idna==2.8
joblib==0.14.1
multidict==4.7.5
nltk==3.4.5
numpy==1.18.0
overrides==2.7.0
pamqp==2.3.0
pandas==0.25.3
pycparser==2.20
pydantic==1.3
pymorphy2==0.8
pymorphy2-dicts==2.4.393442.3710985
pymorphy2-dicts-ru==2.4.404381.4453942
pyOpenSSL==19.1.0
pyTelegramBotAPI==3.6.7
python-dateutil==2.8.1
pytz==2019.3
requests==2.22.0
rusenttokenize==0.0.5
scikit-learn==0.21.2
scipy==1.4.1
six==1.14.0
starlette==0.12.9
tqdm==4.41.1
urllib3==1.25.8
uvicorn==0.11.1
websockets==8.1
yarl==1.4.2
Then I have launched a jupyter notebook in that virtual environment, but I can't import deeppavlov in it.
I have tried :
import sys
!{sys.executable} -m pip install --user deeppavlov

But then I have this error :
ERROR: wrangle 0.6.7 has requirement scipy==1.2, but you'll have scipy 1.4.1 which is incompatible.
WARNING: The script tqdm.exe is installed in 'C:\Users\ABA19328\AppData\Roaming\Python\Python37\Scripts' which is not on PATH.
Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
WARNING: The script uvicorn.exe is installed in 'C:\Users\ABA19328\AppData\Roaming\Python\Python37\Scripts' which is not on PATH.
Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
WARNING: The scripts cygdb.exe, cython.exe and cythonize.exe are installed in 'C:\Users\ABA19328\AppData\Roaming\Python\Python37\Scripts' which is not on PATH.
Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
What can I do to import it in my notebook ?
Thanks

Hi, @anoukbnd
I apologize for long absence of any answer. I could not reproduce this error. Could you please describe how you started the notebook and send results of !pip freeze command execution?


Add an option for limiting completion results to only imported symbols

If you use autocompletion with cquery, it will include the entire C standard library and more in completion results. It would be nice if there was an option to only include symbols that have been included in the current file in completion results.

Sorry; at the moment we rely on clang_codeCompleteAt; this level of filtering is not easily doable. I'd like to integrate clangd as the completion backend instead of clang_codeCompleteAt, because it does a better job for this kind of thing.

Cool, sounds good to me. :+1:


How to disable import?

I only want to support import. Can export be disabled somehow?

Err the obvious way to do it is via permissions: https://django-import-export.readthedocs.io/en/latest/installation.html#import-export-import-permission-code

Yes, you can use permissions to control which users have access, or to remove the functionality completely, you can modify which mixins you link to the model.
e.g.
# Export only
class BookAdmin(ExportMixin, admin.ModelAdmin):
    pass

# import only
class BookAdmin(ImportMixin, admin.ModelAdmin):
    pass

e.g. import only:

Docs


UP-4525 : Handle errors around profile selection event publication.

Fire the profile selection event safely, catching, logging, and ignoring exceptions that arise in response to the profile selection event, figuring that failing the entire login is an inappropriate escalation of a failure in honoring the user's expressed desire to use a particular profile.
(Safety added in response to an issue in MyUW where a glitch in the profile selection persistence code broke portal login for affected users, when those users would have been better off being able to log in even if not being able to switch among available profiles.)
See also portal-dev@ thread.

:+1:

:+1:


Added basic template for timer support, and windows implementation

After this commit, timers are working, documented and tested on windows/cmake/c++.
!! WARNING !! This may cause the mac or linux version to fail to compile, but it will likely be a small and fixable error.
Timers are also not yet implemented on mac or linux, since I haven't been able to test either one yet. I may be able to add linux timers myself, but I will need external help for mac timers.

Great, thanks.
I'm keen on having finally added tests to pugl recently, and this seems like an easy one, so I'll try to write one and implement it for the other platforms based on that.
Would probably be good to use in a demo too though.  Maybe one of them can rotate the cube or whatever every second or so when not running continuously...

This is way harder on both MacOS and especially X11.
It might be easier if pugl allocates the ID instead, but even then things don't quite line up...

Would it be easier if the function template looked more like:
PuglTimer* registerTimer(PuglView* view, double rate)
I could fix up the windows version to do that, if it helps

Don't bother, it's going to need to be massaged along with the implementations, but thanks.
A pugl-allocated uintptr_t ID will probably work for MacOS.  X11 has an xsync extension, but it doesn't allow associating any extra data with timers, and does not send events to windows at all, so... still no idea what to do there.
I imagine that reworking the event loop functions is going to have to happen for this.

I ended up doing this from scratch but after a few misadventures it turned out basically the same in the end anyway: a54361853bdfa08437c2858e603ce6202fb341b2
It wasn't too much of a nuisance to do the ID thing like the Windows API, since both X11 and MacOS (annoyingly) required storing a record of all the timers anyway.
It reliably gets about 2ms precision on X11 and MacOS (really more like the ideal 1, but these things are never perfect), but only 10ms on Windows which is the minimum period there.  There's some other "multimedia timers" API there that can apparently do better, but it's a whole different thing that doesn't work in the usual way and I don't care enough to bother.
We'll see how common functioning XSync extension support actually is, I have no idea...


Refactor operator with controller runtime

Description
refactor operator with controller runtime.
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #1859
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[ ] Created/updated tests
[x] Unit tests passing
[ ] End-to-end tests passing
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

Hey @yittg, can you fix the linter issues?
pkg/diagnostics/grpc_monitoring.go:13:2      staticcheck  SA1019: Package github.com/golang/protobuf/proto is deprecated: Use the "google.golang.org/protobuf/proto" package instead.
pkg/grpc/api_test.go:28:2                    staticcheck  SA1019: Package github.com/golang/protobuf/proto is deprecated: Use the "google.golang.org/protobuf/proto" package instead.
pkg/operator/handlers/dapr_handler.go:208:3  staticcheck  SA1019: client.MatchingField is deprecated: Use MatchingFields

/cc @youngbupark, it seems that with the latest version of proto the "github.com/golang/protobuf/proto" is deprecated.

@yaron2 use the lower version controller runtime to avoid the issue in proto.
we can replace proto with the preferred lib in another change if needed.

/ok-to-test

Generally looks good, some minor refactors.

/ok-to-test

LGTM

Thanks for your contribution @yittg


Add cmd flags

Firstly, I wanted to express how grateful we are for this tool. It's going to drastically change the way we do access management for the better across our engineering org. I was wondering if you think the following change is acceptable?
The first commit adds optional flags for the add command in lieu of asking for user input. We want to be able to roll this out for all engineers with an on-boarding process that's as seamless as possible. The flags will help us automate the things we already know about and only prompt for the things we don't.
The second commit is attempting to make the add command idempotent for the "okta-creds" key on a given backend. This makes it easy to run the add command every time and not get an error if the user already has their credentials populated in their keychain.
Happy to discuss our goals further and open to other ideas in accomplishing the same.

I just realized I duplicated this PR (almost exactly too!) sorry about that: https://github.com/segmentio/aws-okta/pull/137

oh cool! thanks @vivianho , no worries! great minds think alike. as long as it gets done. 🤷♂

Ah, sorry @devinburnette I missed this one. #137 is merged. Thanks for your PR though.