Add Beam Job Service init action

This sets up a Beam Job Service on the master node.  It depends on Flink
and Docker being installed to function correctly.
The Beam team has advised us that Beam is not in a place where the portability
framework can be considered production ready, and as a result the stable
snapshots cannot be relied on.  They advise instead that for the time being,
users build their own Job Service and Worker Image artifacts.  This PR includes
both an init action for the job service, and an automated build script.
Build instructions are also available in the README.

All requested changes added.

Good catch on the bad substitution. Fixed.


Replace H2 db file by DDL-like expressions

Is your feature request related to a problem? Please describe.
Binary files do not support resolving of merge conflicts. It is also dangerous to run random binary from git.
Describe the solution you would like
Replace etc/db/h2db.mv.db file by DDL and a script that creates a file if it does not exist. For example, DDL may be implemented as a SQL files with CREATE TABLE statements and a script will be just a call to H2 Tool RunScript.
Additional context
Security + Maintainability.
For example, this PR is almost impossible to merge because conflict in a binary cannot be resolved. Opposite, SQL statements in DDL files will be just a text and may be easily validated by reviewer and merge conflict won't be a problem anymore.
And it is very dangerous and insecure to distribute a binary file. Anyone can ingest anything to it and there are no automatic checkers of binary files.

Hello @SemyonSinchenko, thank you for the issue! Would it be correct to rephrase the goal to the following points:

Provide a DDL file for managing the DB schema
Provide DML queries that populate the DB with test data
On server startup create DB objects and populate it with sample data as defined by the DDL and DML queries

Is it safe to assume that we want to move away from Hibernate-generated schema? (I am unsure if this is the case since the DB binary is already in the repo and I can't test at the moment)

Would it be correct to rephrase the goal to the following points

Exactly!

Thank you! Sounds like a plan.
I am currently not holding this issue, so if someone is interested they can pick it up. If no one picks it up I will start working on it over the weekend - a comment will be added accordingly.

@filipovskid I would like to try to do it!
So, how I see it:

A bunch of SQL-files that directly creates tables with all the values of the current db file;
An extension of the bin/bin/start-uc-server script: I will add a branch so if the db file does not exist, all the SQL-files should be run one-by-one;

For running I would usu h2 RunScript. A dependency (h2 jar) I would take from the target folder of unitycatalog server. It is already there: https://github.com/unitycatalog/unitycatalog/blob/main/build.sbt#L161

Great! Feel free to ping me on the slack channel if you get stuck. @MrPowers please assign this to @SemyonSinchenko.
As for the implementation, I would say that it is even easier than you think. H2 supports this out of the box, and you can define the DDL and DML files to execute on a client connection. INIT command should do this for you, check Execute SQL on Connection. With this approach we could easily remove this logic if we move to a different DBMS.
The documentation is your best friend.

@ravivj-db @vikrantpuppala these are very good ideas, please take note.
My suggestion is as follows:

I know that there exists a script / code somewhere that we had used to generate this h2 database. let's first put that code out with possibly a test to ensure that starting from an empty database, if that code is run, it does generate the right database that satisfies the tests/test_tutorial.py
then we can figure out which method of generating this database is better and improve things accordingly.

Adding the existing java script to recreate the database via this PR : https://github.com/unitycatalog/unitycatalog/pull/156

Is this done yet?

The original issue is resolved because tests have been added to the tutorial to check the consistency of the sample DB.


How to download SciERC and GENIA datasets ?

How to get SciERC and GENIA datasets ? In the eeqa/proc/DATA.md file, I see instructions to download 2 datasets. But I can't find ./scripts/data/get_scierc.sh and ./scripts/data/get_genia.sh files to download. Thanks

Hi, @Toan-it-mta
I don't see those .sh files either. However, I found the datasets online. You can download them here SciERC and here Genia


proposed change to SchemaManagementTool API for Hibernate Reactive

Hibernate Reactive needs a way to plug its own Vert.x-based database driver into the schema export tool.
Here's my not-very-deeply-thought-out proposal.
Hoping for feedback from @sebersole and @Sanne.

WTH?!


Project

Hello.  Noticed that "Yatagarasu" was complaining when trying to put together a project.  Listen, amizu, maybe you can try to create the project yourself?

I already compiled the project and linked the generated binaries on the Releases page.

I think, he mean about file  "VAC-Bypass-Injector.sln"

And yes, surprisingly, I seem to have the same errors as Yatagarasu.  Today I will try to send bug reports

Hello.  Thanks for helping me, you are the best!  But, I noticed that in the "Releases" tab the file weighs 825 KB, but after my compilation it is only 41 KB.  What is the reason for this?

I think I compiled in debug mode by accident, and all optimizations (including file size optimizations) were off. The release version was also not compiled in Visual Studio, but it is 1:1 the exact source code provided in the repository.
And yes, this issue was unrelated to the source code, it has to do with the way you configured your VS solution. I changed the usage instructions to be more clear about the compilation process, as well as adding a VS solution as a second option (even though you shouldn't need VS to compile, only MSVC++ build tools). If anyone raises similar issues I must make sure that the first thing they should do is provide a through description of their problem, or it won't be practical to help them. It makes it really hard for both of us.
Assuming issue is resolved; contact me on Discord for any further help unrelated to the project (as it was provided) in the repository.


Static properties

Hi,
Is the library able to create static properties on classes - also on static classes?

Hi.
What is static classes in C++ terms?
What do you understand under "static properties"?
And truth to say, I remember how lib actually works a little vague...
From what I see now - looks like "lambda_oriented" branch can only work with immobile "this",
since you have to capture self/this in lambda.
There is "stateless" branch - it passes this/self to your lambda - so it can be moved around...
At least that how it looks like...
Truth to say - there is probably better "properties for C++" libs now...


Defer handshake timeout in case the event loop is completely blocked

Fixes #21.
@Bilge please try with this branch.

Unfortunately this appears to have had no effect. Possible concurrency before failing due to timeout is exactly the same as before this patch.

@Bilge Does the new patch change anything?

Yes! :ok_hand: I can now achieve concurrency up to about ~1500 without changing the timeout. Anything more than that and I just run out of memory, but timeouts no longer seem to occur.

Aside, I'm not sure force pushing is really such a good idea. Obviously your older solution was not the answer but now there's no record it ever existed. It's usually a good idea to keep old ideas around if only for posterity.

@Bilge Nobody needs a non-working fix for an issue. ;-)
It's basically the same idea, but applied a bit differently.

One day you might want to refer back to something you tried that didn't work. Just a thought; I don't mean to tell you how to run your projects.

@Bilge There are cases where keeping the history is beneficial, but not in this case. The new implementation is both more elegant and actually correct. ;-)

@kelunik Is it not possible to write a test case for this? It would be unfortunate if this were to creep back in as a regression later.

@Bilge Definitely! Do you want to provide a PR? Basically it just needs to start a process and then directly call sleep(2); before yielding $process->join();.

That doesn't sound as difficult as I was imagining, but I'm still not sure it is within my ability.

@Bilge Just push a PR with what you have and we can improve it together. :-)


Simplified FindFirstVersionHistoryByItem

What changed?
Modified VersionHistories.FindFirstVersionHistoryIndexByItem to return both index and version history.

Why?
It simplifies the usage.
Currently, in all places that calls this function, index is used solely for retrieving history item. It is already available when we iterate. Furthermore, err check after GetVersionHistory is redundant, as index at that point is always valid.

How did you test it?
Existing tests.

Potential risks

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 0181a579-bdc7-4adb-8fac-27067f76c7bc

7 of 7 (100.0%)  changed or added relevant lines in 4 files are covered.
97 unchanged lines in 10 files lost coverage.
Overall coverage decreased (-0.05%) to 57.958%

Files with Coverage Reduction
New Missed Lines
%

service/history/execution/mutable_state_task_refresher.go
1
73.42%

common/task/weightedRoundRobinTaskScheduler.go
2
89.64%

service/matching/matcher.go
2
91.46%

common/persistence/nosql/nosqlplugin/cassandra/workflow.go
3
57.59%

service/history/task/fetcher.go
3
91.79%

common/task/fifoTaskScheduler.go
4
85.57%

common/persistence/nosql/nosqlplugin/cassandra/tasks.go
14
72.8%

common/persistence/nosql/nosqlTaskStore.go
16
58.37%

common/persistence/nosql/nosqlplugin/cassandra/workflowParsingUtils.go
20
86.11%

common/persistence/nosql/nosqlplugin/cassandra/workflowUtils.go
32
75.82%

Totals

Change from base Build 0181a43a-7b22-4f5e-8393-647a1f5eab87:
-0.05%

Covered Lines:
83901

Relevant Lines:
144762

💛  - Coveralls


[Feature] [SWCK] Supports Kubernetes 1.22.x

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
Apache SkyWalking Cloud on Kubernetes can't be deployed on Kubernetes 1.22.x since some deprecated API is used by the SWCK.
SWCK should have a plan to support the latest Kubernetes.
Use case
To support Kubernetes 1.22.x,  the following API reference need to be upgraded:
apiextensions.k8s.io/v1beta1 -> apiextensions.k8s.io/v1, available since v1.16
apiregistration.k8s.io/v1beta1 ->  apiregistration.k8s.io/v1, available since v1.10
Ingress  networking.k8s.io/v1beta1 -> networking.k8s.io/v1, available since v1.19
Related issues
No response
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Assigned to @RolandMa1986 according to you have selected PR planned.

Hi @wu-sheng ,
What's the minimal version of Kubernetes that needs to be supported by SWCK  in the next release?
It would be very easy to support Kubernetes 1.19 and above only, since all the API versions are compatible. But if SWCK needs to support an older version than 1.19, we need to consider how to change the API version in the Controller and Templates.

I think this should be @hanahmily 's call. He is leading the project.

Yep, we have a plan to upgrade kube runtime by bumping up the kubebuilder v3 in SWCK-0.5.0 which will support the latest Kubernetes.
A canonical strategy is to release major version, for example 1.0.0, to adopt to the new APIs, backporting new feats into the old revision. But, SWCK is not production ready, have not released 1.0.0, I tend to use current major version to do update.


Error : Cannot access video stream (TypeError).

No updates has been done since past 6 months
and suddenly this error arise when calling instascan

I'm doing tests, I have the buttons: Start / Stop and the error is displayed only when I press the buttons quickly to emulate stressed users.
With Firefox (95.0.2) x64 the error does not occur and seems to be faster in changing the works active / deactivate the webcam.
While on Edge (96.0.1054.62 x64), yes. Update the page, sometimes after a couple of attempts, and everything works.
(Laragon local config)
PHP (7.4.16 x64)
Apache (2.4.35 x64)


add_definition -DUSING_PICOW if board is pico_w

-libraries now have the definition as well

Here is a fix that addresses the pico_w issue.  I have never done a pull request with Github before so if I have not done this correctly let me know.
Basically from what I found out because cli and other directories were being added as a library the definition that was in the hardware_build_extra function was not being propagated to them.  So I added a conditional to the file that added the libraries and now the -DUSING_PICOW is being passed to all files.
I'm open to suggestions if this is not seen as the best way to fix the issue.  And if I need to open the pull request a different way then let me know.
Thanks.

That's a good call.
I just amended my commit and made that change in hardware/rp2040/CMakeList.txt instead.
Probably want to do more testing but It looks like the -DUSING_PICOW is included in all of the files need at this point.  I've attached the build output for review if needed.  It runs on my Pico_W and the led option is still absent as it should be.
Let me know if you need anything else.
build_target.txt


Add excludes to code coverage

This PR

[x] (Re-) adds excludes to the code coverage

This is how the set-up was before the split of Unit and Integration tests, and i see no reason not to exclude these from the total coverage.
I'm partial to adding Models to the excludes for coverage as well, since they would be impossible to test without using the database.

@BackEndTea @mdwheele
I'd suggest to remove dead code and not exclude anything from code coverage.
Excluding code from code coverage or static code analysis might give a false impression on the quality of code, and in the worst case we might miss opportunities to improve the quality.

Hehe exactly. It will make it easier to forget that code.

I'm all for closing this and removing the dead code instead.

Closing and asking that the code we were excluding to be instead removed


VSCode will not run unless there is an internet connection

Issue Type: Bug
VSCode is not opening unless I have an internet connection.  The similar issues are all reported as closed.  Windows 1809 was recently installed and VSCode was at latest version and I have just upgraded before this submission and the same problem.
It will not load unless there is an internet connection.
VS Code version: Code 1.30.0 (c6e592b2b5770e40a98cb9c2715a8ef89aec3d74, 2018-12-11T22:29:11.253Z)
OS version: Windows_NT x64 10.0.17763

System Info

Item
Value

CPUs
Intel(R) Atom(TM) x7-Z8700  CPU @ 1.60GHz (4 x 1600)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
3.92GB (1.64GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions: none

/duplicate of #7570. Fixed in Electron 3 #52629

I have LogMeIn Hamachi installed.  What I have found out is if I have my WiFi not connected to a network and Hamachi "off"  VSCode will not open.
Now, if I am still not connected to Wi-Fi but turn on Hamachi.  Hamachi will detect there is no network connection but ask me if I would like for it to continue to check for a connection.  VSCode will open.  The computer does not have an internet connection but basically the network adapters show up as having a lan port but it does not have a network connection.
A workaround for now.


Add Python general component that may not have a logo to display

Codecov Report

Merging #4746 into master will decrease coverage by 50.80%.
The diff coverage is n/a.

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


Update imports to fsnotify

In your watcher.go and watcher_test.go files, can you update the imports from "gopkg.in/fsnotify.v1" to "gopkg.in/fsnotify/fsnotify.v1"?
See https://github.com/go-fsnotify/fsnotify/issues/1
(go get github.com/ivpusic/rerun is broken because of this)
thanks!

tnx for warning about this. Could you send a PR for this?

there's a patch on v0.19.1 I believe

sorry, probably should have closed this years ago...


Try omitting alpha channel from predrawing

My use cases don't include images with alpha at the moment, perhaps pre drawing could be optimized by  skipping alpha.

Closing this since iOS 15's decoding is so rad.


Reference for B cell subtypes.

Hi, Thanks for this great tool! Just wondering is there a GEP reference for B cell subset (Naive, un/switch-memory, plasmablast)? Or any ways to do a B cell subtype annotation using this tool? Thanks so much!

Hi, thanks for checking out starCAT. I am actively working on a B-cell reference and will keep you updated when it is ready. Cheers,
Dylan


Exceptions should inherit from Terra where suitable

Summary
I only identified one such exception - as @jyu00 pointed out - RuntimeJobFailureError should inherit JobError.
While reviewing the exceptions, I changed the exception type in the fake_account_client.py. I thought QiskitBackendNotFoundError was more suitable here.
One question I had was what is the purpose of double inheritance from IBMError, e.g., IBMQpyError(QpyError, IBMError)?
Details and comments
See also https://github.com/Qiskit/qiskit-ibm-runtime/pull/1120.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.008%) to 51.265%

Totals

Change from base Build<PHONE_NUMBER>:
0.008%

Covered Lines:
3364

Relevant Lines:
6562

💛  - Coveralls


[BUG] no valid OpenPGP data found

Is there an existing issue for this?

[X] I have searched the existing issues

Does this issue exist in the latest version?

[X] I'm using the latest release

Describe the bug?
Since couple of days the pipeline started failing with the following error:
gpg: no valid OpenPGP data found.
Error: Process completed with exit code 2.

To Reproduce
- name: Postgres Dump Backup
        uses: tj-actions/pg-dump@v3
        with:
          postgresql_version: "15"
          github_token: ${{ secrets.BOT_TOKEN }}
          database_url: "postgres://${{ secrets.DB_USER }}:${{ secrets.DB_PWD }}@${{ secrets.DB_HOST }}:${{ secrets.DB_PROD_PORT }}/${{ secrets.DB_PROD_NAME }}"
          path: "backup.sql"
          options: "-O --format=c -b --verbose"

What OS are you seeing the problem on?
ubuntu-latest or ubuntu-22.04
Expected behavior?
postgres to be installed
Relevant log output
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
gpg: no valid OpenPGP data found.
Error: Process completed with exit code 2.

Has all relevant logs been included?

[X] I've included all relevant logs

Anything else?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Sorry, it was a proxy problem on our side.
Closing the issue as is not a bug.


Split up test_events.py

@showell can you rebase this?  It appears to merge conflict with one of your other PRs to these files.

ugh, I created a conflict against my own branch...I will rebase this tomorrow

I rebased the first two and merged them.  The other two I'm moving to a much bigger branch that I'm working on, and I'll just open a new PR for that when it's ready.  Closing.


Hey! Can u add a feature that not only pull down to refresh but also pull up to load ?

Hey! Can u add a feature that not only pull down to refresh but also pull up to load ? Thanks For your sharing!

Yes, I thought about it, but now I don't have enough time. Pull requests are welcome.


Update notebooks to integrate them more easily in doc

rename and number notebooks using 2 digits to ease sorting them,
we let the 00-09 numbers for quick start notebooks which will be the
ones  previously generated from python scripts in examples
scheduling notebook:

move main title and description in first cell (for auto-extraction
by autodoc.py)
remove commented cell
add a level to all titles (by adding a #)
so that only the main title is a html H1
bonus: when using the toc from jupyter nbextensions,
the title will not be numbered (as a H1) and the other
section titles will be well numbered

OK to merge, thanks

You made changes in scheduling notebook, please provide a link to binder to help reviewers.

scheduling notebook for this PR:
scheduling notebok from master


Profile for Main module version 3.1.4

Hi guys. Thankyou very much for this wonderful project. I have some Feit 3 way smart dimmers purchased from Costco. I have been able to cloud cut a few of these devices with main module version 1.1.71 quite easily.
But I am not able to find a profile to match the dimmers running 3.1.4.
Has anyone seen this firmware and know if it is exploitable.
My fear is that this is the version in which tuya has fixed the exploit.
If I want to go about figuring out the profile can someone please guide me.

It has been incredibly rare to see a firmware version 3.x.x and be Beken.  It's not impossible though.  Even patched devices (We've only seen one so far) have just been an incremental on 1.1.x
Does the device have an FCCID printed on the back?  Can you put the device in AP mode, and do a wifi scan and get the BSSID of the AP?
Usually 3.x.x were ESP devices.

I have tried using tuya-convert in the hopes that they might be esp devices but that doesn't work. These devices can be put in AP mode and they give ssid  like "SmartLife-XXXX"

I have them installed but I can try to open one up tomorrow and send you the pictures

The BSSID is different than the SSID.  The BSSID will look like a mac address in the form of 00:00:00:00:00:00.  You'd need a 3rd party program such as Wifi Analyzer on windows.  Linux you can usually find it through nmcli dev wifi
Even if the device is ESP, Tuya-Convert likely won't work, as that has long since been patched.

It seems you were correct. It's based on esp and not BK.

Yeah, nothing CloudCutter can currently do for this device then.


4 allow the user to edit items

Got the functionality to work, but my method was a little... sketchy. Would love to hear your input.

I found your explanation very helpful! I took your suggestions and decided to go the path of a dialog pop-up.
Up for further review!

I found your explanation very helpful! I took your suggestions and decided to go the path of a dialog pop-up.
Up for further review!

Don't forget to remove the "changes requested" label!

This time, I removed the changes requested label :)
Thank you for being patient with me.

Oh! I think I got everything :)


Support of File upload and Google ReCaptcha integration

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #46
Test URLs:
https://46-attachments--mammotome--hlxsites.hlx.page/en/submit-a-tech-support-ticket/

@jalagari we have a rather large CLS - related?

@jalagari we have a rather large CLS - related?

Since form is rendered on client and there is not other content page it, causing CLS of 0.001 but the score is still 100


fix: address system test intermittent failures

The release of version 0.9.0 did not experience issues with the system tests.  I will close this PR at this time and, if the system tests are having issues in the future, a new PR can be opened to address them.


Packaging fails with PyPI sourced pup

DETAILS:

Packaging puppy is failing with the latest PyPI-sourced pup 1.0.0a3 release.

REPRODUCTION:

Create a Python 3.7 venv and update pip.
pip install pup -- grabs 1.0.0a3 from PyPI.
Clone puppy source tree from https://github.com/tmontes/puppy.
Run pup package . on the source tree root.

RESULT (Windows):
(venv-xirro) C:\Users\test\work\github.com\puppy>pup package .
I pup 1.0.0a3 - starting with PID=3156
I Package '.': starting.
I Collecting metadata for '.'.
I About to run 'c:\\users\\test\\work\\github.com\\puppy\\venv-xirro\\scripts\\python.exe -m pip wheel --no-deps C:\\Users\\test\\work\\github.com\\puppy'.
I pip out: Processing c:\users\test\work\github.com\puppy
I pip out: Building wheels for collected packages: puppy
I pip out:   Building wheel for puppy (setup.py): started
I pip out:   Building wheel for puppy (setup.py): finished with status 'done'
I pip out:   Created wheel for puppy: filename=puppy-1.4.0-py3-none-any.whl size=8648 sha256=ff3f236e235e73f658ce6ae95e4f0786a4065d7e8515647b21a8f910a5c80590
I pip out:   Stored in directory: C:\Users\test\AppData\Local\Temp\pip-ephem-wheel-cache-vyuiro5s\wheels\17\26\43\705bd58c4b717c1af27e3ec8fb612c8da7e59b082813f42eb8
I pip out: Successfully built puppy
I Step 'win.distribution-layout': starting.
C Execution failure:
C Traceback below:
Traceback (most recent call last):
  File "c:\users\test\work\github.com\puppy\venv-xirro\lib\site-packages\pup\__main__.py", line 31, in wrapper
    exit_code = command_function(*args, **kw)
  File "c:\users\test\work\github.com\puppy\venv-xirro\lib\site-packages\pup\__main__.py", line 80, in package
    launch_module=launch_module,
  File "c:\users\test\work\github.com\puppy\venv-xirro\lib\site-packages\pup\api.py", line 41, in package
    dsp.run_pluggable_step(step)
  File "c:\users\test\work\github.com\puppy\venv-xirro\lib\site-packages\pup\dispatcher.py", line 79, in run_pluggable_step
    return self._invoke_plugin(name)
  File "c:\users\test\work\github.com\puppy\venv-xirro\lib\site-packages\pup\dispatcher.py", line 68, in _invoke_plugin
    return plugin(self._ctx, self, **kwargs)
  File "c:\users\test\work\github.com\puppy\venv-xirro\lib\site-packages\pup\plugins\win\dist_layout.py", line 63, in __call__
    result_path = generate.generate_files(tmpl_path, tmpl_data, build_dir, overwrite_if_exists=True)
  File "c:\users\test\work\github.com\puppy\venv-xirro\lib\site-packages\cookiecutter\generate.py", line 264, in generate_files
    template_dir = find_template(repo_dir)
  File "c:\users\test\work\github.com\puppy\venv-xirro\lib\site-packages\cookiecutter\find.py", line 34, in find_template
    raise NonTemplatedInputDirException
cookiecutter.exceptions.NonTemplatedInputDirException
I pup 1.0.0a3 - done

(venv-xirro) C:\Users\test\work\github.com\puppy>

RESULT (macOS):
(venv) tiago.montes (~/Temp/i77/puppy): pup package .
I pup 1.0.0a3 - starting with PID=1032
I Package '.': starting.
I Collecting metadata for '.'.
I About to run '/Users/tiago.montes/Temp/i77/venv/bin/python3.7 -m pip wheel --no-deps /Users/tiago.montes/Temp/i77/puppy'.
I pip out: Processing /Users/tiago.montes/Temp/i77/puppy
I pip out: Building wheels for collected packages: puppy
I pip out:   Building wheel for puppy (setup.py): started
I pip out:   Building wheel for puppy (setup.py): finished with status 'done'
I pip out:   Created wheel for puppy: filename=puppy-1.4.0-py3-none-any.whl size=8621 sha256=cea794985820a128e2dfdbccdb480447e05a0f63cfdb04620aea41962d15af88
I pip out:   Stored in directory: /private/var/folders/0m/xy6669f52zdbb6prv46hrghw0000gp/T/pip-ephem-wheel-cache-as8l2gbp/wheels/fe/32/0e/c92f7a965c6b69e2cc9d2076cc0dd7078458303396513efbcd
I pip out: Successfully built puppy
I Step 'mac.app-bundle-template': starting.
C Execution failure:
C Traceback below:
Traceback (most recent call last):
  File "/Users/tiago.montes/Temp/i77/venv/lib/python3.7/site-packages/pup/__main__.py", line 31, in wrapper
    exit_code = command_function(*args, **kw)
  File "/Users/tiago.montes/Temp/i77/venv/lib/python3.7/site-packages/pup/__main__.py", line 80, in package
    launch_module=launch_module,
  File "/Users/tiago.montes/Temp/i77/venv/lib/python3.7/site-packages/pup/api.py", line 41, in package
    dsp.run_pluggable_step(step)
  File "/Users/tiago.montes/Temp/i77/venv/lib/python3.7/site-packages/pup/dispatcher.py", line 79, in run_pluggable_step
    return self._invoke_plugin(name)
  File "/Users/tiago.montes/Temp/i77/venv/lib/python3.7/site-packages/pup/dispatcher.py", line 68, in _invoke_plugin
    return plugin(self._ctx, self, **kwargs)
  File "/Users/tiago.montes/Temp/i77/venv/lib/python3.7/site-packages/pup/plugins/mac/app_bundle.py", line 65, in __call__
    result_path = generate.generate_files(tmpl_path, tmpl_data, build_dir, overwrite_if_exists=True)
  File "/Users/tiago.montes/Temp/i77/venv/lib/python3.7/site-packages/cookiecutter/generate.py", line 264, in generate_files
    template_dir = find_template(repo_dir)
  File "/Users/tiago.montes/Temp/i77/venv/lib/python3.7/site-packages/cookiecutter/find.py", line 34, in find_template
    raise NonTemplatedInputDirException
cookiecutter.exceptions.NonTemplatedInputDirException
I pup 1.0.0a3 - done
(venv) tiago.montes (~/Temp/i77/puppy):

HOWEVER:

It does work when running pup from its development virtual environment.

THUS:

We have a meta-packaging issue.
pup is not properly packaged itself. :-)

DIAGNOSTIC:

The bundled cookiecutter templates for macOS application templates and Windows distribution layout aren't being properly packaged in pup's PyPI artifacts.
Oh the irony!

Fixed with #78, just merged. Closing.


update changelog for v4.1.0

comment about the change in build process for v4.1.0

Pull Request Test Coverage Report for Build #367

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 99.796%

Totals

Change from base Build #366:
0.0%

Covered Lines:
489

Relevant Lines:
490

💛  - Coveralls


[5.10] Add test fixture for --experimental-lto-mode option

Cherry-pick of https://github.com/apple/swift-package-manager/pull/6891.
Adds a test covering experimental lto mode and fixes a bug where the LTO mode was not passed to the linker.
Fixes #6888

@swift-ci test

@swift-ci test windows


yagpdb problems

dont know if i am supposed to post this here but trying to get yagpdb self hosted using this guide not dokerised on ubuntu 22.04 and use the seperate command "./yagpdb -all -pa -https=false" and when I use it it gives me a error

Closing we don't use the issue tracker here for helping people self host. If yoh have issues feel free to join the support server and ask in the selfhosting discussion.


[BUG] Fritter gives a notification saying an update is available in 3.0 beta release.

Describe the bug
Fritter sends a notification for an update is available for v2.16.3 on opening the app in 3.0.0-beta2.
To Reproduce
Steps to reproduce the behavior:

Open the app.

Screenshots
If applicable, add screenshots to help explain your problem.
Device
Redmi Note 9 Pro Max
Android 11
English

+1 for this issue.
Same thing happening to me, even if my app is up-to date with F-droid's latest version

+1
Samsung S22 Ultra
Latest android version


[Question] how to retrieve model id after creation

I am currently working on a multi screen create/edit form for one of my models on a react native application. The idea is to click a "add" button that will create an empty model then mount the edit form component for this freshly created model and allow the user to modify it.
To do so I just dispatch a create action with an empty payload
createNewModel() {
    // dispatch the create action with an empty payload
    this.props.createMyModel({});
    // navigate to the edit screen
    // how to retrieve the myModelID here?
    this.props.navigation.navigate('MyModelEditScreen', {id: myModelID});
}

The reducer is very simple
export class MyModel extends Model {
static reducer(action, MyModel, session) {
    const {payload, type} = action;
    switch (type) {
      case types.MY_MODEL_CREATE: {
        let myModel = MyModel.create(payload);
        // the new id is available here, how can I make it available
        // to the application code?
      }
    }
  }
}

I am new to redux ORM, and did not manage to find any help about this specific scenario. Am I missing something?
I know one solution would be to provide the id myself, but I would prefer to use redux ORM ids.
Thank you for this awesome library.

To do this properly, you really need to put the logic into a thunk so you can access the store state:
function createModelAndNavigate() {
    return (dispatch, getState) => {
        dispatch(createMyModel({}));

        const state = getState();
        const session = orm.from(state.entities);
        const {MyModel} = session;

        const latestModel = MyModel.all().last();

        const modelId = latestModel.getId();
        // do something useful with the ID
    }
}

I finally found an alternate solution
createNewModel() {
    // maxId is undefined if no model have been created yet
    let modelID = (this.props.orm.MyModel.meta.maxId || 0) + 1;
    this.props. createMyModel({id: modelID});
    this.props. selectMyModel(modelID);
    this.props.navigation.navigate('SessionEditScreen');
}

Is this a viable solution or does that break redux ORM in some way?

Eh... it may work, I guess, but I personally wouldn't recommend doing that, just from an architectural perspective.
You might want to read through my "Practical Redux" tutorial series, where I talk about how I use Redux-ORM.  I don't cover creating new entries in that series (yet), but one of the things I do mention is that I I make it a point to not expose Redux-ORM to my components at all.

Yes, you are right, I should definitely keep redux-orm out of the component scope. I will probably go with the thunk solution you propose then.
I am using selectors in that project, what do you think about hiding redux-orm behind a selector e.g.
const orm = new ORM();
orm.register(MyModel);

const ormSelector = state => state.orm;
const nextIdSelector = createSelector(
    ormSelector,
    orm.createSelector(orm => {
        return orm.MyModel.meta.maxId + 1;
    })
);

then on the higher order component
function mapStateToProps(state) {
  return {
    nextId: nextIdSelector(state)
  }
}

This way redux-orm is not exposed to the component anymore.
I have been through your full tutorial series, this is a great resource and I can't wait to see how you will propose to solve the new entries creation.

Hmm.  I haven't yet actually played with Redux-ORM's selector integration yet, so I'm not exactly sure how that works.  However, that code looks very suspicious in two ways - the entire orm.MyModel.meta thing, and then calling a selector that's going to return a new ID every time the state changes.

That's assuming that you let the reducer handle generating the ID, which is only really acceptable if you're also using sequential numeric IDs.

I'm finding that Book.all().toRefArray() doesn't give the updated array of the objects from the store.
const state = getState();
const session = orm.session(state.orm);
const { Book } = session;
dispatch({ type: CREATE_BOOK, payload: "Lorem Ipsum" });
console.log(Book.all().toRefArray()); // returns []

Model.prototype.create is synchronous right?

@liaujianjie : I'm not sure what you're seeing there.  This works fine for me:
import {ORM, Model} from "redux-orm";

class MyModel extends Model {}
MyModel.modelName = "MyModel";

const orm = new ORM();
orm.register(MyModel);

const state = orm.getEmptyState();
console.log(state);

const session = orm.session(state);
const MM = session.MyModel;

MM.create({name : "Model 1"});

console.log(session.state);

const items = MM.all().toRefArray();
console.log(items);

CodeSandbox link: https://codesandbox.io/s/xo4572or1w

Oops, I made a silly mistake. I did some other query with an older session and forgot that I needed to get the state again after dispatch:
const oldSession = orm.session(getState().orm);
console.log(newSession.Book.all().toRefArray()); // returns []

// ... do something with oldSession
dispatch({ type: CREATE_BOOK, payload: "Lorem Ipsum" });

const newSession = orm.session(getState().orm);
console.log(newSession.Book.all().toRefArray()); // returns [{...}]

Is this in a thunk somewhere?  Then yeah, if you want to have a session with the "current" values after a dispatch, you would indeed need to call getState().

Yup. I've edited my comment above in case anyone else makes the same error.

Closing due to lack of activity.


iosTranslucentBars not working as in iOS 13

In iOS 13, the translucent bars are only translucent on scrolling. On initial load, they are NOT translucent. You can check it easily with activated dark theme. The contacts app shows deep dark and a kind of gray on scrolling, Framework7 is gray initially.
Anyway, thank you Vladimir for the great and quick adaption to the new style!

What you are refering called navbar-large-transparent in F7 https://framework7.io/docs/navbar.html#large-transparent-title

@nolimits4web - My mistake, thanks, works very well!

@nolimits4web - My mistake, thanks, works very well!


Always fill "empty" on return from gpr_mpscq_pop_and_check_end

gpr_mpscq_pop_and_check_end may leave "empty" flag uninitialized in certain exit scenarios.
Luckily, this flag does not seem to be used anywhere except for
https://github.com/grpc/grpc/blob/f4a94b61266dc468af2de213ea50b997a39b7508/src/core/lib/surface/completion_queue.cc#L401
where it only affects performance counters.

****************************************************************

libgrpc.so

     VM SIZE                                       FILE SIZE
 ++++++++++++++ GROWING                         ++++++++++++++
  +2.4%     +16 src/core/lib/gpr/mpscq.cc           +16  +2.4%
       +12%     +11 [Unmapped]                          +11   +12%
      +3.5%      +5 gpr_mpscq_pop_and_check_end          +5  +3.5%

 -+-+-+-+-+-+-+ MIXED                           +-+-+-+-+-+-+-
  +0.0%     +16 [None]                               -8  -0.0%

  +0.0%     +32 TOTAL                                +8  +0.0%

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences


Propose a Dark mode

Some users would love to see a proper dark mode implemented directly in FFBEEquip.
Plugins that turns page into darker page doesn't fare well with the site.
It could be a user's settings (a toggle somewhere?) that the user can set.
It should be stored in user's settings.
This thread aims to discuss on what needs to be made dark(er).

Question: where should the dark/light toggle be situated?

I think we should have a "user account setting" button somewhere. Probably
near the log out button, when logged in
On Wed, Aug 29, 2018 at 10:58 AM Guillaume<EMAIL_ADDRESS>wrote:

Question: where should the dark/light toggle be situated?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/lyrgard/ffbeEquip/issues/206#issuecomment-416878921,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA9h7XrHh9FlgRLI5mmWmKfrDFWc1cw2ks5uVlfBgaJpZM4WPDKM
.

WIP:

Looks really nice !
On Wed, Aug 29, 2018 at 12:10 PM Guillaume<EMAIL_ADDRESS>wrote:

WIP:
[image: image]
https://user-images.githubusercontent.com/7137528/44781369-76163600-ab84-11e8-887d-6d49217a4afb.png
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/lyrgard/ffbeEquip/issues/206#issuecomment-416900181,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA9h7QY103Poe_LxhsTbGT0Ubrv6crpYks5uVmiIgaJpZM4WPDKM
.

@lyrgard The main issue I can see is actually applying the dark theme.
Doing this in JS leads to seeing first the default version, then the dark version (i.e. like a "flash").
 It's going to be much worse when using user's settings (i.e. have to wait for everything to load from user).
The best thing would be to switch dark/light theme from server side switch. However, we can't because there is no server side information on users.
The only solution I can think of is something along the way reddit handle dark mode: with a subdomain (e.g. https://dm.reddit.com/r/FFBraveExvius).
Hence, server side, we could decide which style to give according to the subdomain or not.
Is it something possible? What do you think?

wip theme looks nice, though still too bright for my taste.
the subdomain idea is intriguing. if i understand it correctly, it could make managing css files easier, at least.

Dark Mode arrived, huzzah! Can close this one.


studio: send non-dvclive info

DVCLive should be able to send all info collected by DVC, not only that logged by DVCLive. Context:

Update on DVCLive + Studio:
For context, this is a relatively fresh repo using Lightning and it contains no commits with a metric. I can see live experiments, but they're missing both metrics (the columns don't exist yet) and parameters.
Looking into the Lightning callback code, I notice that you use Live.log_params on the LightningModule hyperparameters, but I don't think that's right, since they're usually a (differently labelled) subset of DVC parameters. I'll probably monkey patch the DVCLogger method, but it'd be nice to have that an option to use /params.yaml as the hyperparameters transmitted to Studio.

DVCLive should be able to send all info collected by DVC, not only that logged by DVCLive. Context:

I would prefer that DVC info is sent by DVC.
When using dvc exp run, DVC params are sent by DVC and DVCLive params are sent by DVCLive.
There is a bug in the UI that doesn't display the DVC ones https://github.com/iterative/studio/issues/5034


unexpected ZernikeWFE.get_opd() behavior

Kudos to @tukyab for helping find this one.
setup of problem:
r=.0254
osys = poppy.OpticalSystem()
osys.add_pupil(poppy.CircularAperture(radius=r))
osys.add_pupil(poppy.ZernikeWFE(radius=r,coefficients=[0,0,0.000001,0]))

Expected behavior:
plt.imshow(osys.planes[1].get_opd(osys.input_wavefront(wavelength=600e-9)))
plt.colorbar()

gives:

unexpected behavior:
plt.imshow(osys.planes[1].get_opd(600e-9))
plt.colorbar()

This works when the aperture is a few meters across, but only there, it doesn't rescale at all (if you make r=8 then you can't see the circle anymore), the pixel_scale seems to be getting lost when you just pass a wavelength to get_opd().
The documentation says you can pass a wavelength as a float or a wavefront, but I don't actually see why it doesn't throw an error, since the self.circular_aperture.get_transmission(wave) function tests that wave is a wavefront.
@josePhoenix ?

Well, that's weird. I'll take a look.

Something having to do with the physical dimensions of the input wavefront is getting set in osys.input_wavefront but not when creating a wavefront all on its own. Further investigation is required.

By the way: thanks for the high-quality bug report, @douglase!

The relevant section of OpticalSystem.input_wavefront is:
        # somewhat complicated logic here for historical reasons.
        # if we have a first optical plane, check and see if it specifies the entrance sampling.

        npix=None
        diam=None
        if len(self.planes) > 0:
            if self.planes[0].shape is not None:
                npix=self.planes[0].shape[0]
            if hasattr(self.planes[0], 'pupil_diam') and self.planes[0].pupil_diam is not None:
                diam = self.planes[0].pupil_diam

        # if sampling is still undefined, fall back to what is set for this optical system itself
        if npix is None:
            npix=self.npix if self.npix is not None else 1024
        if diam is None:
            diam = self.pupil_diameter if self.pupil_diameter is not None else 1

        # if the diameter was specified as an astropy.Quantity, cast it to just a scalar in meters
        if isinstance(diam, u.Quantity):
            diam = diam.to(u.m).value

What's happening is that in your first case, you're computing the Zernike disk on a 1024 px square array that corresponds to a diameter of 2 * 0.0254. Because the Zernike disk has the same diameter, it's well-sampled and looks like your first plot. From poppy.optics.CircularAperture.__init__:
        self.pupil_diam = pad_factor * 2 * self.radius

(Pad factor is 1.0 unless otherwise specified.)
In the second case, you're computing the Zernike disk on a Wavefront that's created "just in time" by a wrapper called _accept_wavefront_or_meters in wfe.py. It doesn't know the diameter of the pupil at initialization, so it defaults to 8 meters. This was probably a good choice for API ergonomics when POPPY was primarily used to simulate space telescopes with pupils several meters across 😄 Now, we need to decide how to proceed.

Here's a workaround:
import poppy
zernike_optic = poppy.ZernikeWFE(radius=r,
                                 coefficients=[0, 0, 0.000001, 0])
r = 0.0254
osys = poppy.OpticalSystem()
osys.add_pupil(poppy.CircularAperture(radius=r))
osys.add_pupil(zernike_optic)
osys.display(what='both')
plt.imshow(zernike_optic.get_opd(poppy.Wavefront(600e-9, diam=2 * r)))

Thanks for clearing that up, I didn't see that  _accept_wavefront_or_meters wrapper was creating a wavefront. It seems like that function should at least check for pixelscale and diameter before generating a wavefront? (or radius, or pupil_diam, we might want to make a list of all the ways we define the physical extent of a optic first).

agreed, this is not the least astonishing API. The decorator there should be used consistently as well; a lot of optics have some variant of that test copied and pasted in their various methods. It's on my to-do list, though far from the top...


PP-6362: Delete EpdqOrderRequestBuilder

EpdqOrderRequestBuilder was a class that had lots of indirection which it made
it difficult to figure out how a GatewayOrder was being built from the
operations (e.g. capture, authorise, cancel etc). This commit simplifies this
indirection by

instantiating concrete subclasses of EpdqPayloadDefinition.  These are
EpdqPayloadDefinitionFor[Cancel|Capture|Maintenance|New3ds2|New3ds|NewOrder|Query|Refund]Order.java.
moving the building of the GatewayOrder into
EpdqPayloadDefinition.createGatewayOrder
removing inappropriate uses of inheritance and interfaces where possible

Thanks for the review @alexbishop1. I'll make the "Not for now" and "Perhaps not for now" changes in the next PR.


Create new types of collections

BEGINRELEASENOTES

New types of collections. The collections to be implemented are Cluster, Reconstructed Particle, Particle, Vertex, and Track.
The information about each collection has been obtained from EDM4hep yml file.

ENDRELEASENOTES
The task for GSoC week 1 is almost done. We only need to finish previews. So, I have started to do the task for week 2.

Currently, not only types are created. But also the loading functionality.

Foresee a version check in the loading of the different types and / or a possibility to change the loading dynamically depending on the file contents

And, there is also a version check, so these types only work with a set of versions. Also, the particle properties are assigned according to the data in the JSON.

Hey @tmadlener, I think we should continue with #36 instead.

superseded by #36


tracing: always enable cluster id

Please provide a description of this PR:
inspired by kiali's doc, I think it's good to enable it by default.

@zirain: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
1c9c8e4891f2dbb517bcfe8acd451bcd55733f17
link
true
/test release-notes

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

@zirain: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
1c9c8e4891f2dbb517bcfe8acd451bcd55733f17
link
true
/test release-notes

unit-tests-arm64_istio
1c9c8e4891f2dbb517bcfe8acd451bcd55733f17
link
true
/test unit-tests-arm64

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

@zirain: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
1c9c8e4891f2dbb517bcfe8acd451bcd55733f17
link
true
/test release-notes

unit-tests-arm64_istio
1c9c8e4891f2dbb517bcfe8acd451bcd55733f17
link
true
/test unit-tests-arm64

unit-tests_istio
1c9c8e4891f2dbb517bcfe8acd451bcd55733f17
link
true
/test unit-tests

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

@zirain: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
1c9c8e4891f2dbb517bcfe8acd451bcd55733f17
link
true
/test release-notes

unit-tests-arm64_istio
1c9c8e4891f2dbb517bcfe8acd451bcd55733f17
link
true
/test unit-tests-arm64

unit-tests_istio
1c9c8e4891f2dbb517bcfe8acd451bcd55733f17
link
true
/test unit-tests

integ-telemetry_istio
1c9c8e4891f2dbb517bcfe8acd451bcd55733f17
link
true
/test integ-telemetry

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

@zirain: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
1c9c8e4891f2dbb517bcfe8acd451bcd55733f17
link
true
/test release-notes

unit-tests-arm64_istio
1c9c8e4891f2dbb517bcfe8acd451bcd55733f17
link
true
/test unit-tests-arm64

unit-tests_istio
1c9c8e4891f2dbb517bcfe8acd451bcd55733f17
link
true
/test unit-tests

integ-telemetry_istio
1c9c8e4891f2dbb517bcfe8acd451bcd55733f17
link
true
/test integ-telemetry

integ-telemetry-discovery_istio
1c9c8e4891f2dbb517bcfe8acd451bcd55733f17
link
true
/test integ-telemetry-discovery

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

@zirain: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
1c9c8e4891f2dbb517bcfe8acd451bcd55733f17
link
true
/test unit-tests-arm64

unit-tests_istio
1c9c8e4891f2dbb517bcfe8acd451bcd55733f17
link
true
/test unit-tests

integ-telemetry_istio
1c9c8e4891f2dbb517bcfe8acd451bcd55733f17
link
true
/test integ-telemetry

integ-telemetry-discovery_istio
1c9c8e4891f2dbb517bcfe8acd451bcd55733f17
link
true
/test integ-telemetry-discovery

release-notes_istio
aea2b09f3ca064e6af301d3a5e649a933cb147fe
link
true
/test release-notes

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

@zirain: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio
1c9c8e4891f2dbb517bcfe8acd451bcd55733f17
link
true
/test integ-telemetry

unit-tests-arm64_istio
853abeec7d47c95eecb0b862d2900342f0a83ba5
link
true
/test unit-tests-arm64

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

@zirain: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio
1c9c8e4891f2dbb517bcfe8acd451bcd55733f17
link
true
/test integ-telemetry

integ-ambient_istio
6b139df9a7aa04e6be7d89b9c847dc1bd401795b
link
true
/test integ-ambient

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

@zirain: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio
1c9c8e4891f2dbb517bcfe8acd451bcd55733f17
link
true
/test integ-telemetry

integ-ambient_istio
6b139df9a7aa04e6be7d89b9c847dc1bd401795b
link
true
/test integ-ambient

integ-telemetry-discovery_istio
6b139df9a7aa04e6be7d89b9c847dc1bd401795b
link
true
/test integ-telemetry-discovery

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

@zirain: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio
6b139df9a7aa04e6be7d89b9c847dc1bd401795b
link
true
/test integ-ambient

integ-telemetry-discovery_istio
6b139df9a7aa04e6be7d89b9c847dc1bd401795b
link
true
/test integ-telemetry-discovery

integ-telemetry_istio
6b139df9a7aa04e6be7d89b9c847dc1bd401795b
link
true
/test integ-telemetry

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

@zirain: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-discovery_istio
6b139df9a7aa04e6be7d89b9c847dc1bd401795b
link
true
/test integ-telemetry-discovery

integ-telemetry_istio
867c8f8c8842443a8420c930af79efe5b5aad2be
link
true
/test integ-telemetry

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

@zirain: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio
867c8f8c8842443a8420c930af79efe5b5aad2be
link
true
/test integ-telemetry

integ-telemetry-discovery_istio
867c8f8c8842443a8420c930af79efe5b5aad2be
link
true
/test integ-telemetry-discovery

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

@zirain: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio
867c8f8c8842443a8420c930af79efe5b5aad2be
link
true
/test integ-telemetry

integ-telemetry-discovery_istio
867c8f8c8842443a8420c930af79efe5b5aad2be
link
true
/test integ-telemetry-discovery

integ-ambient_istio
4929f46b6d68d3c007cc254aee15cfafc2e57b64
link
true
/test integ-ambient

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

@zirain: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio
4929f46b6d68d3c007cc254aee15cfafc2e57b64
link
unknown
/test integ-ambient

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

/test integ-ambient


Please export EditorConfiguration

The options for Codemirror is of type EditorConfiguration.
This type is not exported so when using the component options comes up as "any" type, thus intellisense/autocomplete is not available to see the available types in the editor (e.g., vscode).
A fix is to change "declare type CodemirrorProps" in index.d.ts to "export declare type CodemirrorProps", or in other words export the type for the options from the es module.
Thanks.

So the EditorConfiguration is imported from `@types/codemirror', no need of double exporting it from this repo


Provide more details about client evaluation logging

“Entity Framework Core blocks such client evaluation and throws a runtime exception.”
Could  you please specify which exception is thrown and details that exception includes?
More details about criteria what is consider  as poor performance will be useful .
“ Since this behavior could cause unnoticed performance issues, EF Core logged a client evaluation warning.”
Does it mean that such warning is removed in current version?
If the query doesn’t cause “poor performance exception” , a developer may not realized, that the query includes client evaluation portion. The log message(info or warning) describing that a part of the query is evaluated on the client will be useful for current version as well.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: fd35b912-445c-e801-7f70-de73839db80d
Version Independent ID: e558a081-5397-1e3f-1d58-abea3f72cad6
Content: Client vs. Server Evaluation - EF Core
Content Source: entity-framework/core/querying/client-eval.md
Product: entity-framework
Technology: entity-framework-core
GitHub Login: @smitpatel
Microsoft Alias: avickers

Could you please specify which exception is thrown and details that exception includes?

Can you clarify in what way this information would be useful/actionable? We try to keep docs short and to the point, and overloading them with information that isn't needed is detrimental. In general, when a user attempts to perform a query with unsupported client evaluation, at that point they get the explicit exception including all the details.

More details about criteria what is consider as poor performance will be useful .

An example is given just above: if a Where filter can't be translated to the server, "all the data needs to be pulled into memory to apply the filter on the client.". Isn't this sufficient?

Does it mean that such warning is removed in current version?

As explained on the page, current versions simply disallowed allow client evaluation (outside of the top-level projection). In previous versions, the same thing caused a warning instead.

The log message(info or warning) describing that a part of the query is evaluated on the client will be useful for current version as well.

As above, client evaluation outside of the top-level projection causes an exception in current versions, so a log message isn't needed.

“ We try to keep docs short and to the point” link to the other place, that provide more details, will be sufficient.
“ the explicit exception including all the details.” As a reader of the page, currently I have no idea , what data is reported in the exception and how easy it will be to to interpret it. Ability to view it (in a link) will be useful.
2., "all the data needs to be pulled into memory to apply the filter on the client.". Isn't this sufficient?”
The statement about all data is talking just about the particular example. It is not clear if the query will have combination of server and client evaluation clauses, but after server evaluation still return to client millions of rows, will exception be thrown? If “all data” is only 5 rows, will exception be thrown? If I wish to  know more details about criteria what is consider as poor performance(not just an example), where can I find it?       Again, if you consider this article just as a top-level overview, please provide a link, where more details can be read.
3. My question was about currently  allowed client evaluation, i.e. the top-level projection.  (Sorry If it wasn’t clear)
Does it  log a  warning about client evaluation ?
If not, the log message(info or warning) describing that a part of the query is evaluated on the client will be useful for current version as well, because a developer may not realised, that the query includes client evaluation portion. By seeing  such log message  a developer may consider to revise the query.

As the docs explain, EF simply throws whenever you do client evaluation outside of a top-level projection. This doesn't depend on how many rows are brought back - EF has no way of knowing the number of rows that will be returned by a query. In any case, the idea is that even if client evaluation causes only 5 rows to be returned today, the table's data may change and return a lot more tomorrow; we want developers to be aware very early about the issue, so we don't allow any queries with such client-evaluation to execute.

My question about warning was about currently allowed client evaluation, i.e. the top-level projection. (Sorry If it wasn’t clear)
Does it log a warning about client evaluation ?

No - no warning is logged about client evaluation in the top-level projection, because that kind of client evaluation doesn't create performance problems; it does not cause more rows to be fetched than would be if no client evaluation occurred. The top-level projection is simply a "transformation" (or projection) of the results coming back from the query; it generally doesn't matter if that transformation occurs in the database (before results are transferred to the client) or afterwards. Contrast this with a Where clause, which determines which rows are returned; client evaluating that means that all rows must be transferred to the cilent.

“As the docs explain, EF simply throws whenever you do client evaluation outside of a top-level projection.”
Now you confused me even more. From the article I understood there are 2 independent validations in Microsoft implementation.
1. “If EF Core detects an expression, in any place other than the top-level projection, which can't be translated to the server, then it throws a runtime exception.”
2. “Based on the filter and the amount of data on the server, client evaluation could result in poor performance. So Entity Framework Core blocks such client evaluation and throws a runtime exception.”
My question is about second validation:where a reader can find more about criteria  the filter and the amount of data on the server?
Your consideration about “the table's data may change and return a lot more tomorrow;we want developers to be aware very early about the issue, so we don't allow any queries with such client-evaluation to execute” is seems about the first “other than the top-level projection”, but in document it is also described as runtime exception. Does your “EF has no way of knowing the number of rows that will be returned by a query” means that it  is a compile-time check rather than runtime?

The 2nd point explains the 1st point, i.e. the performance issue explains why EF throws when it detects client evaluation (other than in the top-level projection).

Does your “EF has no way of knowing the number of rows that will be returned by a query” means that it is a compile-time check rather than runtime?

No, this is a runtime check, but it occurs before the query is actually executed in the database, i.e. when EF pre-processes it and prepares to translate it to SQL, etc.

“The 2nd point explains the 1st point”
It is not true, at least it is not how it is written in the document.
The section https://learn.microsoft.com/en-us/ef/core/querying/client-eval#unsupported-client-evaluation is independent, it doesn’t mention ”other than the top-level projection”, but talks about poor performance with the example due to “all the data”.
Is the example in the section apply to the top-level projection?

The first section - Client evaluation in the top-level projection, discusses client evaluation in top-level projections; this is supported and does not warn, and an example is given.
The second section - Unsupported client evaluation - is about other types of client evaluation (not in the top-level projection); the example seems to make that pretty clear. This isn't supported in modern versions of EF Core (runtime exception), and caused a warning in very old versions (pre-3.0), with the reasoning being that it may unintentionally bring huge amounts of data to the client.
I can see how the relationship between the two sections might no be 100% clear, and in general the page could use a bit of improvement. But beyond that I'm having trouble understanding what you're suggesting or saying.

I will try to explain my suggestions again:
1.” If EF Core detects an expression, in any place other than the top-level projection, which can't be translated to the server, then it throws a runtime exception. “
People like me maybe curious what  exactly included in the exception. You mentioned that “ the explicit exception including all the details.” The article doesn’t have even this not-specific statement. Ideally a link to an example of the exception with all details will be good.

“The second section - Unsupported client evaluation - is about other types of client evaluation (not in the top-level projection); the example seems to make that pretty clear. “
The example makes clear the concept , but not specific details. I’ve asked  questions about other examples.

It is not clear if the query will have combination of server and client evaluation clauses, but after server evaluation still return to client millions of rows, will exception be thrown? If “all data” is only 5 rows, will exception be thrown? If I wish to know more details about criteria what is consider as poor performance(not just an example), where can I find it?

Neither the document, nor you doesn’t give the answer for them at the moment. Again link to in-depth information will be useful.
2.1  The  section - [Unsupported client evaluation](https://learn.microsoft.com/en-us/ef/core/querying/client-eval#unsupported-client-evaluation) is talking about” filter and the amount of data on the server”.
According to the document , the evaluation is current  and the section doesn’t have any mention about not modern versions of EF Core.
If your statement is correct, it should be clearly mention in [Unsupported client evaluation](https://learn.microsoft.com/en-us/ef/core/querying/client-eval#unsupported-client-evaluation) section.
Description of Previous Versions is a separate section at the bottom of the document, and in the current document not related to the modern sections described above.

3.From your explanation I understand that the modern version do not generate warning logs.My suggestion to include info or warning is not about documentation, but a feature request, that I will submit via another channel.

People like me maybe curious what exactly included in the exception. You mentioned that “ the explicit exception including all the details.” The article doesn’t have even this not-specific statement. Ideally a link to an example of the exception with all details will be good.

Our docs don't generally detail exactly what each and every exception includes; that would make them longer, and I frankly don't really see what a user would do with this information (except for just general curiosity)... We're discussing in error case: users typically unintentionally trigger the exception, and at that point they're exposed to what details it contains; I'm not sure of the value of explaining ahead of time what an exception will contain if the user does something that isn't permitted. But am definitely open to hearing why you think this should be documented.

Neither the document, nor you doesn’t give the answer for them at the moment. Again link to in-depth information will be useful.

I'm sorry, but I simply don't understand what you find unclear here. As I've written several times above - and as the document also makes clear - client evaluation outside of the top-level projection can cause huge amounts of unwanted data to be brought back to the client, and so is always disallowed.
I do agree that this page should be improved, specifically to make it clearer exactly which kind of client evaluation is being discussed in each section - but otherwise I don't see what's missing.

3.From your explanation I understand that the modern version do not generate warning logs.My suggestion to include info or warning is not about documentation, but a feature request, that I will submit via another channel.

Which warning do you want us to add?

Client evaluation in the top-level projection isn't problematic in any way - it is 100% fine for users to do this, as it doesn't cause extra data to be brought to the client. As a result, it doesn't make sense to add a warning.
Client evaluation outside the top-level projection is unsupported and already causes an exception to be thrown. We generally never warn when we already raise exception, because the exception already needs to be handled etc.

1.You are the author, and it is up to you to determine what level of detail to provide.
From your reply you prefer the approach “you do not need to know details, when you run, you will see how it works” My expectation is that if I want to have better understanding (synonym of curiosity) how it would work without  need  to run it, I should be able to get it from the documentation. The document should have something like “for more information see  the link(…)”

Your  answers re Unsupported client evaluation completely different from the way how the section is written at the moment.

According to the document   Unsupported client evaluation  section is not refer to client evaluation outside of the top-level projection.  It is talking about separate exception related to poor performance based on the volume of data even if the clause is for  top-level projection. The code example in the section has top-level projection, but suppose to fail due to “all the data” poor performance.
You are telling that Unsupported client evaluation section is just an explanation why client evaluation not in the top-level projection should not be allowed. If your explanation is correct, the section should be  re-written.
Btw, if the document would specify the names of “non top-level projection” and “poor performance” exceptions, it will be obvious, are we talking about the same or two different validations.
3

Which warning do you want us to add?
Client evaluation in the top-level projection isn't problematic in any way - it is 100% fine for users to do this, as it doesn't cause extra data to be brought to the client. As a result, it doesn't make sense to add a warning.

Is this thread a right place to discuss feature request? Or should I click “Product feedback”?
The log message(info or warning) describing that a part of the query is evaluated on the client will be useful , because a developer may not realised, that the query includes client evaluation portion. By seeing such log message a developer may consider to revise the query.
I have a particular example, when a developer used proprietary client function IsEquivalent that forced client evaluation. If such warning will be logged, he world likely to  revise the query  and use simple == comparison, and the evaluation will occur on the server with better performance.

The log message(info or warning) describing that a part of the query is evaluated on the client will be useful , because a developer may not realised, that the query includes client evaluation portion. By seeing such log message a developer may consider to revise the query.
I have a particular example, when a developer used proprietary client function IsEquivalent that forced client evaluation. If such warning will be logged, he world likely to revise the query and use simple == comparison, and the evaluation will occur on the server with better performance.

I think you're missing a fundamental point that I've been trying to explain... Client evaluation - when in the top-level projection - does not cause performance issues. There's therefore no reason for the developer to rewrite their query, and evaluation on the server would not cause better performance.


PushSecret vault expecting a JSON (while AWS SM can take any type of data)

Describe the bug
I've tried to push the same data (a string) using AWS Secret Manager and Vault. While I'm able to push the data to AWS Secret Manager, when trying to do the same to Vault it fails with an JSON encoding error:
status:
  conditions:
  - lastTransitionTime: "2023-05-12T13:28:05Z"
    message: 'set secret failed: could not write remote ref token to target secretstore
      vault-backend: failed to convert value to a valid JSON: invalid character ''e''
      in literal true (expecting ''r'')'
    reason: Errored
    status: "False"
    type: Ready
  syncedPushSecrets:
    SecretStore/vault-backend: {}

I've found this PR that might have caused it
To Reproduce
Steps to reproduce the behavior:

provide all relevant manifests

apiVersion: external-secrets.io/v1beta1
kind: ExternalSecret
metadata:
  name: get-token
spec:
  refreshInterval: "15s"
  secretStoreRef:
    name: vault-backend
    kind: SecretStore
  data:
  - secretKey: hello
    remoteRef:
      key: secret/demo
      property: secret

provide the Kubernetes and ESO version

kubernetes v1.26.3
ESO: v0.8.1
Expected behavior
I would expect to be able to point to a different SecretStore to change where the secrets are going to be pushed: Same behavior across providers.

Vault can't handle simple strings: every secret is a json object. That's a small but important detail when using the vault provider.
We recently updated the docs:

Vault supports PushSecret features which allow you to sync a given kubernetes secret key into a hashicorp vault secret. In order to do so, it is expected that the secret key is a valid JSON object.

hi @jordiprats ! the issue is that we cannot assume what is the value of the json key when transforming it.
Imagine a kubernetes Secret with values:
foo: bar

When calling push secret, only bar is sent to the provider.

Hi @gusfcarvalho, that's not exacly what I mean:
For a foo: bar Secret I would expect to be able to push "bar" into vault, not the entire secret.
To be completely transparent, I have only tested this with AWS Secrets Manager: this creates a secret with the contents of the key:
apiVersion: external-secrets.io/v1alpha1
kind: PushSecret
metadata:
  name: set-token
spec:
  refreshInterval: 5s
  secretStoreRefs:
    - name: aws-sm
      kind: SecretStore
  selector:
    secret:
      name: test-sa-token
  data:
    - match:
        secretKey: token
        remoteRef:
          remoteKey: demo/test-sa-token

I would expect to be able to just by changing spec.secretStoreRefs to use a different backend.

That’s the issue. Hashicorp vault does not allow a secret which is not a json. So you simply can’t upload bar in it

Besides, I think it make more sense to the user if the data is transformed into vault as a json like:
{"string"}

Rather than having to actually provide a json beforehand

Your example is not a valid Json :)

Having said all that, this is unfortunately not a bug, rather a limitation of the provider.
There is an underlying feature request here (dataFrom support for PushSecret), but that would still not be a bug 🐛. I’m removing the labels and adding kind/feature

I think this can be closed with #2361. Please let me know if something is missing.

I just tested version 0.9.4 of the operator and the value of the secret key for the PushSecret for Hashicorp Vault still needs to be a valid JSON. Otherwise, it returns an error when tries to unmarshal it:
Warning  Errored  94s (x16 over 4m19s)  pushsecret  set secret failed: could not write remote ref foo to target secretstore test: error unmarshalling vault secret: invalid character 'b' looking for beginning of value
The secret that works:
apiVersion: v1
kind: Secret
metadata:
  name: source-secret
stringData:
  source-key: "{\"foo\":\"bar\"}"

The secret that doesn't work:
apiVersion: v1
kind: Secret
metadata:
  name: source-secret
stringData:
  foo: "bar"

IMHO this issue should be reopened as otherwise this feature is mostly unuseful for most of the use cases where the secret is generated by a third party and we do not manage the content. For instance, when we use crossplane.

Just noticed that there is a hidden parameter (not documented) that allows add/update the secret in Vault from a raw string (not JSON).
apiVersion: v1
kind: Secret
metadata:
  name: source-secret
stringData:
  source-key: "{\"foo2\":\"bar2\"}"
  foo: bar3
---
apiVersion: external-secrets.io/v1alpha1
kind: PushSecret
metadata:
  name: pushsecret-example
spec:
  refreshInterval: 10s
  secretStoreRefs:
    - name: vault-backend
      kind: SecretStore
  selector:
    secret:
      name: source-secret
  data:
    - match:
        secretKey: foo
        remoteRef:
          remoteKey: my-secret/secret
          property: foo # <-- this is an optional parameter not documented in the API reference


Indeed the action is failing with:
💥 maturin failed
  Caused by: Failed to parse Cargo.toml at Cargo.toml
  Caused by: missing field `package` at line 9 column 1

that happens because the Cargo.toml it is looking is the one of the workspace, rather than the one of the crate I would like to package.
Is it possible to get an option to use with with: in order to specify which directory (and thus which crate) to use?

You can pass -m/--manifest-path to a Cargo.toml that you want to package in args, for example
- uses: messense/maturin-action@v1
  with:
    maturin-version: latest
    command: build
    args: --release -m path/to/Cargo.toml

It worked wonderfully, thank you very much


2.1 索引 | Computer Cookbook School Recruitment

https://books.grayson.top/school-recruitment/docs/database/2MySQL/2.1-索引/

https://books.grayson.top/school-recruitment/docs/database/2MySQL/2.1-索引/
索引这一章节 很多索引失效的都错了 比如 in like ，建议重新看一下


Sonoff RFR3 no longer being detected by Hassio

Hello,
I had a RFR3 setup and working through Hass.io but as of today the entity was showing as unavailable.  Reboots have achieved nothing.  I deleted the Sonoff device from the entities list in the hope it would be detected as new and reappear.
The device works with Alexa, the light is solid blue.  I've also run a constant ping test to the device to see if it was disconnecting from my wireless network but it never missed a beat.
How best should I proceed?
Are there logs I can export off for you to review?
Would really welcome any support.
My stats are:
Home Assistant 0.113.2
HACS 1.3.0b1
Sonoff LAN 2.30
Kind regards
Boyd

Please show config

Same like me. I have couple devices did not show up anymore. All SONOFF POW v2.6.1.

Config?

Config?

Closed because no response


feat(theme-translations): translation for Uzbek (uz)

Pre-flight checklist

[ ] I have read the Contributing Guidelines on pull requests.
[ ] If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
[ ] If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation

Test Plan

Test links

Deploy preview: https://deploy-preview-_____--docusaurus-2.netlify.app/
Related issues/PRs

I wonder if we should have a threshold to limit the number of languages we have. I understand that every language is potentially useful to some users, but we need to weigh between out-of-the-box usefulness and the extra install size this brings to everyone, including the 99.9% of users that don't need it. Plus there's maintenance issues, etc.
@slorber WDYT?

I wonder if we should have a threshold to limit the number of languages we have. I understand that every language is potentially useful to some users, but we need to weigh between out-of-the-box usefulness and the extra install size this brings to everyone, including the 99.9% of users that don't need it. Plus there's maintenance issues, quality control, etc.
@slorber WDYT?

This probably does not increase install size that much IMHO. There are lower hanging fruits to consider, like inlining our dependencies like Next.js does, which as a much more significant impact. I don't think it's time to optimize this part yet, and the maintenance remains reasonable so far.


Can't apply smaller width, or padding on right side

Hello there.
I'm getting pretty desperate, as I've tried doing everything to make this look, however the right marker always seems to be out of screen. Applying width or padding, or even margin to containerStyles doesn't do the trick.
Here's the code
import React from 'react';
import Slider from '@ptomasroos/react-native-multi-slider';
import theme, { Text } from '@common';
import styled from 'styled-components';

const Container = styled.View`
  height: auto;
  flex: 1;
  margin-top: -15px;
  width: 100%;
`;

const SliderWrapper = styled.View`
  width: 85%;
  padding-right: 40px;
  margin-right: 40px;
  height: auto;
`;

const TimeLabelsWrapper = styled.View`
  flex-direction: row;
  justify-content: space-between;
  width: 100%;
  margin-bottom: 15px;
`;

const TimeLabel = Text.extend`
  width: auto;
`;

const containerStyle = {
  height: 'auto',
};

const trackStyle = {
  height: 5,
  borderRadius: 5,
};

const selectedStyle = {
  backgroundColor: theme.orange,
};

const unselectedStyle = {
  backgroundColor: theme.darkGray,
};

const markerStyle = {
  backgroundColor: theme.primary,
  width: 26,
  height: 26,
  borderRadius: 26,
};

const pressedMarkerStyle = {
  width: 29,
  height: 29,
};

export default function AvailabilitySlider(...props) {
  return (
    <Container>
      <TimeLabelsWrapper>
        <TimeLabel bold size={13}>
          12:00 AM
        </TimeLabel>
        <TimeLabel bold size={13}>
          9:00 AM
        </TimeLabel>
      </TimeLabelsWrapper>

      <SliderWrapper>
        <Slider
          {...props}
          trackStyle={trackStyle}
          containerStyle={containerStyle}
          selectedStyle={selectedStyle}
          unselectedStyle={unselectedStyle}
          markerStyle={markerStyle}
          pressedMarkerStyle={pressedMarkerStyle}
          values={[0, 5]}
        />
      </SliderWrapper>
    </Container>
  );
}

I am running into the same problem. Would like to know if there is a workaround.

His slider does take a property called "sliderWidth" that accepts a number as the width of the slider.
sliderWidth={250}
It is 280 by default.

Hi there! Sorry for not being able to respond sooner. I'm very fed up with work coming weeks and won't be able to help out here before the beginning of April most likely. Hope the community can help out.

@cmcaboy for me it was sliderLength and yeah setting it to 250 made it look good. However I think this still would be better if you could use percentages. Also I'm not quite sure the differences between sliderWidth and sliderLength.

@ptomasroos Could you please give us a hint what's the difference between sliderWidth and sliderLength or if there's a quick way to make these values accept values like 100% or auto

Can you please point me to where sliderWidth is used?

Sorry for confusion. It was the previous comment that mentioned sliderWidth. That slider uses sliderLength.
So any way to make this value dynamic? i.e 100%

It is sliderLength. Sorry. I misspoke.

I'm also wondering if it's possible to use percentage values instead of absolutes. So the slider would take up an entire width of the screen both vertically and horizontally.

To get a relative slider length you could make use of react-native's window dimensions and optionally consider to remove the container's left and right padding:
import { Dimensions } from 'react-native';
import MultiSlider from '@ptomasroos/react-native-multi-slider';

...

render () {
  const { width } = Dimensions.get('window');
  optionalPadding = 10;
  const mySliderLength = width - 2 * optionalPadding;

  <MultiSlider
    ...
    sliderLength={mySliderLength}
  />
}


Removing not allowed characters from module names before saving content

I tried to download Coursera content with the scraper, but it kept failing on writing asset files to disk on Windows. I've removed special characters from module names while saving assets as well.

There was a similar issue with saving videos, and there was a fix for that as per #5 . This PR replicates this solution for saving assets as well. Cheers


Settings Modal makes scrollbar disappear

Tested on Chrome 44, Firefox 24, IE 9.  Problem exists in all browsers.

From Center in the dropdown menu choose "Settings"
In the settings modal choose "Save"
The scrollbar on your browser is now missing.

Passed testing (IE11, FF24, CH36) for User, Org Steward, Admin in both environments: Latest (develop) & Release (master).  Scrollbar can be seen after choosing Save (no change save and 'Open in Webtop' save).

Passed testing on HS -Staging IE10, FF, 31 and Chrome 36
Steps Used to Test-
Log into Apps Mall
Menu | Settings |  Cancel
RESULTS - Scroll bar is still available
Menu | Settings | Don't change anything | Save
RESULTS - Scroll bar is still available
Menu | Settings | Change to "Open in Webtop" | Save
RESULTS - Scroll bar is still available


Syntax and indentation issues fixed

There were indentation errors in verification.py , helpers.py and misc.py cogs. There were a few unterminated strings and syntax errors. These are now fixed.

Kinda broke more stuff than expected, not merging, sorry


Create WIX files for building Windows Installer

LICENSE.rtf can be removed, unless you have a particular reason to add it.

Since this ends up being a small change, please git rebase to reduce to one commit.
This is a significant moment in the Kingdom of Connector. Thanks a million. I'll test it out tomorrow.

Never mind the LICENSE.rtf comment. I see that you mentioned it's required for Windows Installer. Please place it with the other wix-specific files.

Done.

@arastooz Thank you.


What is doc?

Hi eli5,
I'm looking at explain_prediction_xgboost but am unable to understand the mandatory arg doc stand for. Is it suppose to a X_test pandas DataFrame? I do not see it being mentioned in the docs: https://eli5.readthedocs.io/en/latest/autodocs/xgboost.html
def explain_prediction_xgboost(
        xgb, doc,
        vec=None,
        top=None,
        top_targets=None,
        target_names=None,
        targets=None,
        feature_names=None,
        feature_re=None,  # type: Pattern[str]
        feature_filter=None,
        vectorized=False,  # type: bool
        is_regression=None,  # type: bool
        missing=None,  # type: bool
        ):

hi @Kevin-Chen0 , doc means one example (or input) to the classifier - and this method explains prediction for it. In case of pandas dataframe, I hope X_test.iloc[i] should work but not 100% sure.

Can u pass in an entire DataFrame or multiple rows, or does explain_prediction*() only work for one row or observation at a time?

currently, explain_prediction work only for one row/example at a time. There is also explain_weights which needs only the trained model and gives a summary of overall feature importance.


feat: Series.str.to_datetime

What type of PR is this? (check all applicable)

[ ] 💾 Refactor
[x] ✨ Feature
[ ] 🐛 Bug Fix
[ ] 🔧 Optimization
[ ] 📝 Documentation
[ ] ✅ Test
[ ] 🐳 Other

Related issues

Related issue #1120
Closes #

Checklist

[x] Code follows style guide (ruff)
[x] Tests added
[x] Documented the changes

If you have comments or can explain your changes, please do so below.

I saw in https://github.com/narwhals-dev/narwhals/issues/1120 that it is desirable to add some parameters to it. I can take a look at it later in a separate PR.

Thanks @raisadz !
Could you please add to_datetime to https://github.com/narwhals-dev/narwhals/blob/main/docs/api-reference/series_str.md ? Looks like we don't currently check for that in CI (yet!) 🙈

Thanks for your review, @MarcoGorelli ! I added it to the api reference.


Uncaught exception while refreshing vips

I'm encountering the following exception after the bot has been running for a few minutes.
The channel has no vips available and the bot is running on it's own channel for development purposes.
Python version 3.8.5 running in Alpine linux inside docker.
[2020-08-11 10:23:16,393] [ERROR  ] Logging an uncaught exception (ActionQueue)
Traceback (most recent call last):
  File "/app/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1179, in _execute_context
    context = constructor(dialect, self, conn, *args)
  File "/app/venv/lib/python3.8/site-packages/sqlalchemy/engine/default.py", line 681, in _init_compiled
    self.compiled_parameters = [
  File "/app/venv/lib/python3.8/site-packages/sqlalchemy/engine/default.py", line 682, in <listcomp>
    compiled.construct_params(m, _group_number=grp)
  File "/app/venv/lib/python3.8/site-packages/sqlalchemy/sql/compiler.py", line 694, in construct_params
    raise exc.InvalidRequestError(
sqlalchemy.exc.InvalidRequestError: A value is required for bind parameter 'id' (Background on this error at: http://sqlalche.me/e/cd3x)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/app/pajbot/utils/time_method.py", line 18, in wrap
    ret = f(*args, **kwargs)
  File "/app/pajbot/modules/vip_refresh.py", line 84, in _process_vip_logins
    db_session.execute(
  File "/app/venv/lib/python3.8/site-packages/sqlalchemy/orm/session.py", line 1268, in execute
    return self._connection_for_bind(bind, close_with_result=True).execute(
  File "/app/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 988, in execute
    return meth(self, multiparams, params)
  File "/app/venv/lib/python3.8/site-packages/sqlalchemy/sql/elements.py", line 287, in _execute_on_connection
    return connection._execute_clauseelement(self, multiparams, params)
  File "/app/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1101, in _execute_clauseelement
    ret = self._execute_context(
  File "/app/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1181, in _execute_context
    self._handle_dbapi_exception(
  File "/app/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1473, in _handle_dbapi_exception
    util.raise_from_cause(sqlalchemy_exception, exc_info)
  File "/app/venv/lib/python3.8/site-packages/sqlalchemy/util/compat.py", line 398, in raise_from_cause
    reraise(type(exception), exception, tb=exc_tb, cause=cause)
  File "/app/venv/lib/python3.8/site-packages/sqlalchemy/util/compat.py", line 152, in reraise
    raise value.with_traceback(tb)
  File "/app/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1179, in _execute_context
    context = constructor(dialect, self, conn, *args)
  File "/app/venv/lib/python3.8/site-packages/sqlalchemy/engine/default.py", line 681, in _init_compiled
    self.compiled_parameters = [
  File "/app/venv/lib/python3.8/site-packages/sqlalchemy/engine/default.py", line 682, in <listcomp>
    compiled.construct_params(m, _group_number=grp)
  File "/app/venv/lib/python3.8/site-packages/sqlalchemy/sql/compiler.py", line 694, in construct_params
    raise exc.InvalidRequestError(
sqlalchemy.exc.StatementError: (sqlalchemy.exc.InvalidRequestError) A value is required for bind parameter 'id'
[SQL: INSERT INTO vips(id, login, name) VALUES (%(id)s, %(login)s, %(name)s)]
[parameters: [{}]]
(Background on this error at: http://sqlalche.me/e/cd3x)

need to test the command in a channel with 0 vips


Incorrect tagging of cycleway+footway

iD is breaking years old standard of tagging ways, which are designated for both foot as well as bicycle. Such ways have always been tagged with:
highway=path
foot=designated
bicycle=designated
segregated=yes|no

Now iD is braking this and changing highway to footway or cycleway. If a way has foot=designated - it cannot be cycleway. If a way has bicycle=designated - it cannot be footway. Therefore path is the only possible value.

@tomass Thanks for your feedback. It turns out cycle paths with pedestrian access are tagged differently in different parts of the world. See #6836 for discussion on this topic in France.
Just let me know what other countries use the highway=path pattern and I will prevent iD from showing the preset in them.

Thank you.
Lithuania uses the original OSM tagging scheme described in the first post.

@tomass Okay, I made it so the preset in question won't appear in Lithuania. This will be live in the upcoming 2.15.6 release.
FYI in most places highway=cycleway is about more than access—it's considered a class in the road hierarchy with higher status than highway=path.

Please add Poland as well. We only use highway=cycleway where there are no pedestrians allowed and the standard OSM tagging for shared paths.

Please add Poland as well.

@rmikke This was done in 1bde4dd936d2514118bd69e4d42021b34fd8bfbe. Somebody messaged me about it outside GitHub.


Typo on Bootstrap JS Tabs page

The code example on page http://twitter.github.com/bootstrap/javascript.html#tabs
should read
    $('#myTab').tabs('show')

rather than
    $('#myTab').tab('show').

Same for the example a little further down that includes this
    <script>
    $(function () {
    $('.tabs a:last').tab('show')
   })
   </script>
```javascript
It should be tabs('show').

Sorry if this has already been reported.

I believe you're wrong. Check out the new 2.0 js files. They renamed bootstrap-tabs.js to bootstrap-tab.js. Also, the js file itself reflects the changes if you check out the functions.

@moollaza is correct, the jQuery plugin is $.fn.tab and so $('#myTab').tab('show') is the correct syntax for the master branch of bootstrap.

yep it's singular now. thanks!


Show Assistant chip in version details

Resolves this issue
Description

Added assistant chip to version details view and diff view that links to the working version
Ideally in the future we'd have a dropdown showing what's inside each version.

User Impact

User will be able to navigate to the assistant and assistant version

Easy way to navigate to the assistant

Demo

Docs

Codecov Report
Attention: Patch coverage is 20.00000% with 4 lines in your changes missing coverage. Please review.

Files with missing lines
Patch %
Lines

apps/experiments/models.py
20.00%
4 Missing :warning:

Additional details and impacted files

:loudspeaker: Thoughts on this report? Let us know!


DOC: Update recommendation for computing a Bounding Region in IndexSpace

Since MyBoundingBoxInObjectSpace is computed via Update(), it can be converted to a bounding itk::Region defined in IndexSpace.
Updated example code is provided.  It offers significant speed improvement by using the already-computed MyBoundingBoxInObjectSpace as a basis for the index space box.

Nice!


Inference with c++

Hi @leimao
Thank you for the work. How to make inference with the model created with tf 2.x in c++

I have not investigated it. Maybe I will do it in the future if I get a chance.


Should natively Handle AzureSQL Serverless - Sleep/Pause Mode and not fail

When connecting to AzureSQL Serverless which are configured to go to sleep/pause mode [Mostly in Dev/Stage], Spark should not fail, rather it should wait for 5-7 sec and retry 3 times before throwing exception

Support for Azure SQL serverless. @rajmera3 @arvindshmicrosoft FYI

@sandeep540 could you please also paste the error message and the environment you are testing in - Spark standalone? Databricks?

Spark standalone

You can always set the connection timeout property to >30s in the jdbc url and in my experience this works

Spark does re-try based on configuration, and connector retry depends on Spark driver/executor retrying. Closing as non-issue/resolved.


Using as a stateless provider

Hi
We are building an mobile app and would like to use this provider with an Laravel backend.
But have a question.
For Facebook and Google we use:
$socialiteUser = Socialite::driver('facebook')->stateless()->userFromToken($request->token);
Where $request->token is the token sent from the app.
Both the Facebook and the Google provider now runs: getUserByToken() and does an request to verify the user. See:
https://github.com/laravel/socialite/blob/4.0/src/Two/GoogleProvider.php#L61
But in this provider the getUserByToken() function just decodes the token:
https://github.com/GeneaLabs/laravel-sign-in-with-apple/blob/1a2aabe7146ecd0dc7876e49d6891b29203649f7/src/Providers/SignInWithAppleProvider.php#L83
Wouldn't it be a good idea to be consistent with how the other providers work? Or is there something specific with Apple login that works different? Or could this provider still work but call some other function to verify the user?
I understand that this provider is build for the web implementation first but just wanted to raise the question!
Otherwise, great work!

Hi @andreasbergqvist, thanks for writing in! Apple doesn't work exactly like other OAuth providers. With SIWA you have to request a new token with each login, from what I remember, the token is not stored for reuse.

@andreasbergqvist
Use can use this package: SocialiteProviders/Apple
After login with apple on iOS device, your app will obtain the token, send this token to your server.
This token already has user information such as: email, name... You need to verify this token - this is already implement by the package.

There is a list of known public keys from Apple to do the job: https://appleid.apple.com/auth/keys