Add coverage for .check! behavior

Hi there,
This PR increases code coverage percentage to 95% by testing the DotenvChecker.check! behavior.
Please check it out.
Thanks!

@arielj Just addressed your comments. 👍


use machine learning for circuit optimization

Try to use unsupevised ML to learn ZX diagram simplification.

Possible resources:

"Teaching small transformers to rewrite ZX diagrams", Charton, Krajenbrink, Meichanetzidis, and Yeung
"Reinforcement Learning Based Quantum Circuit Optimization via ZX-Calculus", Riu, Nogué, Vilaplana, and Garcia-Saez, Estarellas
"Optimizing ZX-Diagrams with Deep Reinforcement Learning", Nägele and Marquardt


Feature request in adding ExecuteTakeFirstOrThrow

I have had a look through closed issues and wasn't able to find something like this.
So far we have execute(), executeTakeFirst() and executeTakeFirstOrThrow().
We are wondering if there is a take one and one only else throw if you SQL gets more than one row result.
This would be simliar to sqlalchemy's .one() (https://docs.sqlalchemy.org/en/20/core/connections.html#sqlalchemy.engine.Result.one) as opposed the .first() (and also one_or_none() - at most one result or no result else throw an error) methods.

I feel this is kind of feature creep

I feel this is kind of feature creep

Agreed.


OpenRefine adding "\r" to cataloger last name upon export

During the process of uploading a file created by the DigiApp into Specify, this file is first checked for errors in LibreOffice (Excel would change some of the formatting and create problems) and then processed in OpenRefine.
When exporting this processed file from OpenRefine again, there is sometimes a "\r" behind the cataloger last name. This does not appear in OpenRefine itself, only in the exported .tsv file. It is not a huge issue since we can just remove it in the Specify workbench when we want to import it, but it causes duplicate agents to be create if we overlook it.
It seems to only happen in files that we edited and saved in LibreOffice (But not every single one of these files). If there is nothing wrong with the file and we close it again without saving, it doesn't happen. We usually export them with windows-1252 encoding, but we also tried UTF-8 and it produced the same error.
An example OpenRefine Export file can be found here:
"N:\SCI-SNM-DigitalCollections\DaSSCo\DigiApp\Data\6.Archive\NHMD_Herbarium\v1.2.0_20240227\NHMD_Herba_20240517_16_28_SS_processed.tsv"
The file that was edited in LibreOffice and then imported into OpenRefine is here:"N:\SCI-SNM-DigitalCollections\DaSSCo\DigiApp\Data\6.Archive\NHMD_Herbarium\v1.2.0_20240227\NHMD_Herba_20240517_16_28_SS_checked_corrected.csv"

@RebekkaML LibreOffice on MacOS or Windows?

@FedorSteeman I'm using Windows 10.
I saved the file the way you suggested. Most settings were the same, only the default character set was windows 1252, I changed it to UTF-8 now.
But this didn't solve the problem.

I can't replicate the issue, so you could try on another computer and maybe also update your LibreOffice.


Move config.yml to config subdirectory

Allows to use a folder as docker volume (eg. NFS share).
Addresses https://github.com/Lissy93/dashy/issues/1322
Thank you for contributing to Dashy! So that your PR can be handled effectively, please populate the following fields (delete sections that are not applicable)
Category:

Feature

Overview

Moves the conf.yml into a new subdirectory config, so that this whole folder can be bind mounted into the docker container. That way we can have a docker volume from NFS (or similar).

Issue Number (if applicable) #1322
New Vars (if applicable)

If you've added any new build scripts, environmental variables, config file options, dependency or devDependency, please outline here

Screenshot (if applicable)

If you've introduced any significant UI changes, please include a screenshot

Code Quality Checklist (Please complete)

[ ] All changes are backwards compatible
[ ] All lint checks and tests are passing
[ ] There are no (new) build warnings or errors
[ ] (If a new config option is added) Attribute is outlined in the schema and documented
[ ] (If a new dependency is added) Package is essential, and has been checked out for security or performance
[ ] Bumps version, if new feature added

Might also address a subset of #693

Cheers @bajo and @joshbuker  - sorry this took so long to come around to. Given it was a breaking change it made sense to include it with the other breaking changes (for no app rebuilding) and do a major version bump, which took me longer than expected to get finished.

Cheers @bajo and @joshbuker  - sorry this took so long to come around to. Given it was a breaking change it made sense to include it with the other breaking changes (for no app rebuilding) and do a major version bump, which took me longer than expected to get finished.

All good! Really appreciate your work!

Cheers @bajo and @joshbuker - sorry this took so long to come around to. Given it was a breaking change it made sense to include it with the other breaking changes (for no app rebuilding) and do a major version bump, which took me longer than expected to get finished.

Thanks a lot @Lissy93 . Glad it made it into the release. :)


attach orig-binding property (used for occurrence typing)

This pull request changes the infer function so that when it's introducing variables into the environment, it attaches an extra property so that other rules can find the original variable with the original scopes. This is used for occurrence typing.
Is this the right way to do this? What if one of the attached sep properties happens to be the name orig-binding?

Closing because #12 is better for the current implementation of occurrence typing.


Consider making SecureSession::Encrypt/Decrypt const methods

Problem
These methods don't seem to modify any SecureSession state, but are not const.
Proposed Solution
Consider making them const, unless we expect them to mutate state in the future.
@pan-apple

These methods no longer exist.


Ghidra cannot find jdk

jdk：OpenJDK11U-jdk_x64_windows_hotspot_11.0.7_10

run ghidra-Ghidra_9.1.2_build\Ghidra\RuntimeScripts\Windows\ghidraRun.bat

the directory of your Java location needs to be in the $PATH
C:\data\jdk-12.0.1>java --version
openjdk 12.0.1 2019-04-16
OpenJDK Runtime Environment (build 12.0.1+12)
OpenJDK 64-Bit Server VM (build 12.0.1+12, mixed mode, sharing)

C:\data\jdk-12.0.1>echo %PATH%
...;C:\data\jdk-12.0.1\bin;...

thus you should set in your local path:

![image](https://user-images.githubusercontent.com/3347507/83483958-f1dea880-a4f7-11ea-8082-cae04c7222e7.png)

Thank you for your reminder, but it still fails to start, I don't know where the problem is.

I found the reason. The release page of github is the source code, I thought it was a built program.

Go to https://ghidra-sre.org/ to download the built program and it will start normally.


[FLINK-5921] [table] Add custom data types for rowtime and proctime.

We add a custom data type for the result of the rowtime() and proctime() marker functions to easier identify the chosen time semantics in when translating window operations.
Both method return a constant timestamp (0L) which is injected during constant expression reduction.

Updated

@fhueske Thanks for updating, the PR looks very good to me. I look forward to merge.
Best,
SunJincheng

I'm fine with this temporary solution. +1 for merging until FLINK-5884 is fixed.

Thanks for the feedback @sunjincheng121 and @twalthr
Merging this.


[REEF-744] Implement useful subset of YARN REST APIs to be subsequently

used in REEF .NET Client
This change addressed the issue by

Creating a YARN REST client using RestSharp lib
Created data models to de/serialize Rest response
Add unittests and initial functional test

Remaining tasks:

Add newapplication and submit application APIs

JIRA:
REEF-744

@markusweimer @afchung Thanks for reviewing the change.
I have made changes and responded to other comments. Please take a look.

@anupam128 I'm done with my second pass. Mostly minor comments. Thanks!

Looks good to me. Will merge after @markusweimer 's +1.

@anupam128 How will we version this when Hadoop changes its REST schemas? Other than that, this looks good to me.

@afchung You know C# and REST and the APIs involved better than me. Assume a +0 from me and merge when you think it is ready :-)

Looks good, will test and merge.

@afchung I started out with the intention to try and solve API versioning problem but that makes this change too big/solving too many problems. As the API is currently internal only and is intended to stay that way and wrapped with public facing REEF Client API I think instead of over-engineering this right now we can tackle the versioning issue when required.

@anupam128 OK, that sounds good. Could you please resolve the conflicts, and I'll test and merge. Thanks!

@afchung resolved the conflicts.

@anupam128 Thanks! Testing and merging now.

@anupam128 Could you please rebase and ping? I'm having trouble merging this PR. Thanks!

@afchung Rebased. Thanks!

@anupam128 It seems like there was a bad merge. I'm getting this:
Failed reading /vol1/tmp/2015_09_22_21_16_35_reef-job-17/DriverHttpEndpoint.txt
when I try to submit HelloREEF to HDInsight, and although the job ends up submitted, it never begins running. Could you take a look? Thanks!

@anupam128 After doing a deep clean, it seems like although the error above still appears during submission, the job does turn to "running" state. Given that the CR is orthogonal to the error, I will be merging this PR. I will follow up on the error on the dev mailing list. Thanks!

@anupam128 Actually, it seems like this is expected, as seen in YarnJobSubmissionClient.java, though the error messages do seem misleading, as it never writes a success message. I will revisit the logic later to understand exactly what it is trying to do. Sorry for the confusion!

Debug build is broken after sync the change from master.
(CoreCompile target) ->
Properties\AssemblyInfo.cs(59,31): error CS1726: Friend assembly reference 'Org.Apache.REEF.Tests' is invalid. Strong-name signed assemblies must specify a public key in their InternalsVisibleTo declarations. [D:\Reef\ReefApache\reef\lang\cs\Org.Apache.REEF.Client\Org.Apache.REEF.Client.csproj]
Properties\AssemblyInfo.cs(60,31): error CS1726: Friend assembly reference 'Org.Apache.REEF.Client.Tests' is invalid. Strong-name signed assemblies must specify a public key in their InternalsVisibleTo declarations. [D:\Reef\ReefApache\reef\lang\cs\Org.Apache.REEF.Client\Org.Apache.REEF.Client.csproj]
Properties\AssemblyInfo.cs(63,31): error CS1726: Friend assembly reference 'DynamicProxyGenAssembly2' is invalid. Strong-name signed assemblies must specify a public key in their InternalsVisibleTo declarations. [D:\Reef\ReefApache\reef\lang\cs\Org.Apache.REEF.Client\Org.Apache.REEF.Client.csproj]


ZoomView and ScrollView problem

Hello and thank you for this great widget,
I have a problem with ZoomView and ScrollView,
When I put ZoomView intro scrollView it does zoom in but the scrollable area gets smaller and the user can not scroll for example to the top or the bottom of scrollView. It also happens when I put scrollview into the zoomable area like this:
View v = ((LayoutInflater) getSystemService(Context.LAYOUT_INFLATER_SERVICE)).inflate(R.layout.zoomablelayout, null, false);//zoomablelayout contains scrollview
RelativeLayout.LayoutParams params=new    RelativeLayout.LayoutParams(LayoutParams.MATCH_PARENT, LayoutParams.FILL_PARENT);

v.setLayoutParams(params);

ZoomView zoomView = new ZoomView(this);
zoomView.setLayoutParams(new RelativeLayout.LayoutParams(LayoutParams.MATCH_PARENT,     LayoutParams.FILL_PARENT));
zoomView.addView(v);

RelativeLayout   main_container = (RelativeLayout) findViewById(R.id.main_container);
main_container.addView(zoomView);

Thank you.

have you guys found a solution for it ?

the same problem ,for help !

Got the same problem too. Please help.

I have the same problem too. Someone can help ??

i have same problem. i have a GridView in HorizontalScrollView and when zoom GridView many columns of GridView not show.

public class MainActivity extends ActionBarActivity {
GridView gv;
zoom z;
HorizontalScrollView hs;
@Override
protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    setContentView(R.layout.activity_main);

    gv=(GridView)findViewById(R.id.grid);
    hs=(HorizontalScrollView)findViewById(R.id.hs);
    z=(zoom)findViewById(R.id.zoom);

    gv.setAdapter(new GridAdapter(this));
    FrameLayout.LayoutParams linearParams = (FrameLayout.LayoutParams)gv.getLayoutParams();
    linearParams.width=100*20;
    gv.setLayoutParams(linearParams);
    gv.setColumnWidth(100);

    hs.postDelayed(new Runnable() {
        public void run() {
            hs.fullScroll(HorizontalScrollView.FOCUS_RIGHT);
        }
    }, 100L);

    z.setListner(new zoom.ZoomViewListener() {
        @Override
        public void onZoomStarted(float zoom, float zoomx, float zoomy) {
            FrameLayout.LayoutParams linearParams = (FrameLayout.LayoutParams)gv.getLayoutParams();
            linearParams.width=(int)(100*20*zoom)+1;
            gv.setLayoutParams(linearParams);
        }

        @Override
        public void onZooming(float zoom, float zoomx, float zoomy) {

        }

        @Override
        public void onZoomEnded(float zoom, float zoomx, float zoomy) {

        }
    });

}

}

I use setListener for change width of GridView when zoom in or zoom out. but sometimes many columns of gridView not show and remains white space in right of GridView.
Help me.


parsing cargo:rustc-flags does not support the -L/libdir syntax (no spaces between flag and argument)

Problem

Steps

See: https://github.com/rust-lang/cargo/blob/master/src/cargo/core/compiler/custom_build.rs#L514
Note that the parsing algorithm requires a space between the flag and the flag value.
However, utilities like pkg-config will often print something like: -L/some/dir/local/lib -licui18n -licuuc -licudata, which is correct as far as flags go, but won't parse.

Possible Solution(s)

Perhaps the parsing should be corrected to account for this.  And yes, I can replace -L with -L  (space at end) and do the same for -l but would be nice if this worked out of the box.
Notes
Output of cargo version:
╰─>$ cargo version
cargo 1.37.0-nightly (4c1fa54d1 2019-06-24)

Hi, I've gone ahead and taken a look at this. I believe I fixed the issue in my own fork and would like to write some tests for it. I'm brand new to cargo (and open source contributions in general) and don't really know where these tests would go. Right now I'm thinking tests/testsuite/build_script.rs would be a good place?


[$500] Tooltip is not shown when hovering workspace name in announce detail page

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open the website
Open any #announce room from LHN
click on the header from the #announce page
Hover over the workspace name
Observe the result

Expected Result:
There should be a tooltip since it is linked to the workspace
Actual Result:
There is no a tooltip
Same happening with workspace chat too
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.70-5
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/43996225/4e38ccaf-0faa-44c1-b63b-ceeda98d2a47
https://github.com/Expensify/App/assets/43996225/e1d3c1b2-354d-4d54-859f-4cf2b2a3a3b5
Expensify/Expensify Issue URL:
Issue reported by: @misgana96
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1693296853909699
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01fc5062636cbdb70b
Upwork Job ID:<PHONE_NUMBER>076661760
Last Price Increase: 2023-10-06

Proposal
Please re-state the problem that we are trying to solve in this issue.

Tooltip is not shown when hovering workspace name in announce detail page

What is the root cause of that problem?

Currently, we do not have a tooltip in case the user hovers on the chatRoomSubtitleText
https://github.com/Expensify/App/blob/46e6e202029924025148f6db6be2b378fd3e96e9/src/pages/ReportDetailsPage.js#L162-L176

What changes do you think we should make in order to solve the problem?

We can add the tooltip in case isPolicyAdmin is true like bellow:

{isPolicyAdmin ? (
                                <UserDetailsTooltip
                                    accountID={lodashGet(workspaceIcon, 'id', -1)}
                                    icon={workspaceIcon}
                                >
                                    <PressableWithoutFeedback
                                        disabled={policy.pendingAction === CONST.RED_BRICK_ROAD_PENDING_ACTION.DELETE}
                                        accessibilityRole={CONST.ACCESSIBILITY_ROLE.BUTTON}
                                        accessibilityLabel={chatRoomSubtitle}
                                        onPress={() => {
                                            Navigation.navigate(ROUTES.getWorkspaceInitialRoute(props.report.policyID));
                                        }}
                                    >
                                        {chatRoomSubtitleText}
                                    </PressableWithoutFeedback>
                                </UserDetailsTooltip>
                            ) : (
                                chatRoomSubtitleText
                            )}

with  const workspaceIcon = ReportUtils.getWorkspaceIcon(props.report);
What alternative solutions did you explore? (Optional)

NA

Result
Screencast from 07-09-2023 11:49:39.webm

What is the expected behavior here? What should be shown in the tooltip? cc: @JmillsExpensify @kavimuru @misgana96

When clicking the workspace name it goes to the workspace so that there should be a "workspace" word in the tooltip. It is just like when hovering over the display name is shows a "profile" in the tooltip

It does not take me to the workspace when I click on the workspace name in the details RHN page (same as you screenhots).

I shared the wrong one my report is from #announce. you can try this one

The same is true for #admin too

Thanks, catching up above.

I expect us to deprecate the vast majority of tooltips in the product, so I'm generally not in favor of doing anything here.

Agreed.


Filter improvements

there's still remaining area upon filtering rows, this particular issue will be addressed in a different PR (see image)

I don't see any options for the filters regardless of the column


keylime_verifier

Is your an issue a feature request? If so, please raise it as an enhancement
Environment Ubuntu

OS / version: focal
Processor architecture: x86
TPM Manufacturer: sw tpm
Keylime version:

Description
keylime_verifier fails to start after ^C.
Expected behavior vs. actual behavior
Expected it to start.
Steps to reproduce problem

^C a running keylime verifier
start it again

Is there any documentation on how to restart keylime after a change to the configuration?
Relevant logs
Attach any relevant log files that can help to debug your issue.
keylime_verifier
Using config file /etc/keylime.conf
2021-03-05 15:30:27.417 - keylime.keylime_db - WARNING - database_url is not set, using deprecated database configuration options
2021-03-05 15:30:27.499 - keylime.keylime_db - WARNING - database_url is not set, using deprecated database configuration options
2021-03-05 15:30:27.503 - alembic.env - INFO - Migrating database cloud_verifier
2021-03-05 15:30:27.503 - alembic.runtime.migration - INFO - Context impl SQLiteImpl.
2021-03-05 15:30:27.504 - alembic.runtime.migration - INFO - Will assume non-transactional DDL.
2021-03-05 15:30:27.544 - keylime.cloudverifier - INFO - agent ids in db loaded from file: [('D432FBB3-D2F1-4A97-9EF7-75BD81C00000',)]
2021-03-05 15:30:27.544 - keylime.cloudverifier - INFO - Starting Cloud Verifier (tornado) on port 8881, use  to stop
2021-03-05 15:30:27.544 - keylime.cloudverifier_common - INFO - Setting up TLS...
2021-03-05 15:30:27.545 - keylime.cloudverifier_common - INFO - Existing CA certificate found in /var/lib/keylime/cv_ca, not generating a new one
2021-03-05 15:30:27.546 - keylime.cloudverifier - INFO - Starting service for revocation notifications on port 8992
2021-03-05 15:30:27.657 - keylime.cloudverifier - INFO - connection to <IP_ADDRESS> refused after 1/10 tries, trying again in 1.000000 seconds
2021-03-05 15:30:28.681 - keylime.cloudverifier - INFO - connection to <IP_ADDRESS> refused after 2/10 tries, trying again in 1.000000 seconds
2021-03-05 15:30:29.717 - keylime.cloudverifier - INFO - connection to <IP_ADDRESS> refused after 3/10 tries, trying again in 1.000000 seconds
2021-03-05 15:30:30.742 - keylime.cloudverifier - INFO - connection to <IP_ADDRESS> refused after 4/10 tries, trying again in 1.000000 seconds
2021-03-05 15:30:31.775 - keylime.cloudverifier - INFO - connection to <IP_ADDRESS> refused after 5/10 tries, trying again in 1.000000 seconds
2021-03-05 15:30:32.809 - keylime.cloudverifier - INFO - connection to <IP_ADDRESS> refused after 6/10 tries, trying again in 1.000000 seconds
2021-03-05 15:30:33.838 - keylime.cloudverifier - INFO - connection to <IP_ADDRESS> refused after 7/10 tries, trying again in 1.000000 seconds
2021-03-05 15:30:34.869 - keylime.cloudverifier - INFO - connection to <IP_ADDRESS> refused after 8/10 tries, trying again in 1.000000 seconds
2021-03-05 15:30:35.903 - keylime.cloudverifier - INFO - connection to <IP_ADDRESS> refused after 9/10 tries, trying again in 1.000000 seconds
2021-03-05 15:30:36.936 - keylime.cloudverifier - INFO - connection to <IP_ADDRESS> refused after 10/10 tries, trying again in 1.000000 seconds
2021-03-05 15:30:37.969 - keylime.cloudverifier - WARNING - agent D432FBB3-D2F1-4A97-9EF7-75BD81C00000 was not reachable for quote in 10 tries, setting state to FAILED
2021-03-05 15:30:37.969 - keylime.cloudverifier - ERROR - Polling thread error: 'first_verified'
2021-03-05 15:30:37.969 - keylime.cloudverifier - ERROR - 'first_verified'
Traceback (most recent call last):
File "/usr/local/lib/python3.8/dist-packages/keylime/cloud_verifier_tornado.py", line 583, in process_agent
if agent['first_verified']:  # only notify on previously good agents
KeyError: 'first_verified'

This is having trouble connecting to the agent, if your agent running?

No, the aent was not running.  My rough notes on how to start keylime say to start the verifier first.  That sometime works.  Is there a better order?
I thought the verifier was on the server and the agent(s) were on the client.  Is that wrong?
Is there any documentation on how to start keylime?  And how to wipe the state and start over after a patch?
I have a sense that there are a lot of parts connected through TCP sockets and DBUS.  Is there a picture or documentation on how the parts connect - the client and server ports?

Just a note that I have also encountered this while developing the Rust agent in a F33 VM. My understanding is also that the verifier does / should not depend on the agent.

Update
I was able to fix this error by doing the following:

Starting up the keylime_ima_emulator, registrar, and agent on the VM
Then starting up the keylime_verifier on the same VM

Then, I was able to use this tenant command to delete the agent:
keylime_tenant -v <IP_ADDRESS> -t <IP_ADDRESS> -f /root/excludes.txt --uuid D432FBB3-D2F1-4A97-9EF7-75BD81C00000 --allowlist /root/allowlist.txt --exclude /root/excludes.txt -c delete

After deleting the agent, everything ran normally in the expected order (keylime_verifier could be started up without running the agent).
Based on this solution and the fact that the error seems to originate somewhere around here as part of process_agent(), it seems like the verifier is getting stuck in a mid-way state and expecting to launch back into that state when it is started again. I'm not sure if this is expected behavior; from a UI standpoint this seems surprising.
Solution?
When running the components together, delete the agent before stopping the verifier to avoid an unexpected state. (Or is there a documented better way to shut these down nicely?)
Background information on the error
Environment
F33 VM
keylime commit: 3a5c8c8f6dd17e68e02b68ad961ed71b71267e5d
TPM: swtpm run with this script (minus --allow-signing)
Previous success conditions
The keylime_verifier routinely ran after starting keylime_ima_emulator and before starting keylime_registrar or keylime_agent on this same VM.
Attempts to resolve that didn't work

Rebooting the VM
Stopping and restarting keylime_ima_emulator with and without restarting the tpm2_abrmd
Seeing if another process is using <IP_ADDRESS>:8992 in the VM or on the host (does not look like it)
Setting setenforce 0 both in the VM and on the host

I don't understand how the verifier can depend on the agents acting properly.  They run on different machines, right?  How can the verifier delete all the agents.

That attribute first_verified no longer exists and the event loop has changed a lot, so I'm closing this.


Expand selection in words with underscores is inconsistent

Issue Type: Bug

Open any file which contains word consisting of letters with underscores (f.e. hello_world). For simplicity let's assume only one underscore is present.
Place cursor in various places of this word and activate expand selection command (either via keyboard shortcut or keybinding)
Observe:
3a. cursor is not near underscore (underscore is not immediately to the left or right of cursor) - part of the word selected, bounded by word beginning/end and underscore - OK
3b. underscore is immediately left to the cursor - part of word to the right of cursor is selected - OK
3c. underscore is immediately right to the cursor - the whole word is selected - UNEXPECTED.

For 3c I expected only part of the word selected as well, not the whole word.
VS Code version: Code 1.42.0 (ae08d5460b5a45169385ff3fd44208f431992451, 2020-02-06T10:51:34.058Z)
OS version: Windows_NT x64 10.0.18362

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz (8 x 2112)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: disabled_softwaremetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: enabledrasterization: enabledskia_renderer: disabled_offsurface_control: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_offwebgl: enabled_readbackwebgl2: enabled_readback

Load (avg)
undefined

Memory (System)
15.75GB (4.81GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (10)

Extension
Author (truncated)
Version

quick-open-prefill-selection
col
0.0.1

vscode-eslint
dba
2.0.15

gitlens
eam
10.2.1

EditorConfig
Edi
0.14.4

vscode-great-icons
emm
2.1.47

intellij-idea-keybindings
k--
0.2.37

camelcasenavigation
map
1.1.1

material-icon-theme
PKi
3.9.3

partial-diff
ryu
1.4.1

terminal-tabs
Tyr
0.2.0

(5 theme extensions excluded)

Tried to fix this in the PR #90736
PS - this is my first PR for a OSS, ever... please forgive me for any mistake or misconduct.


[New Event Request] Codeunit "Sales-Post", OnBeforePostATOAssocItemJnlLine

[New Event Request] Codeunit 80 "Sales-Post", OnBeforePostATOAssocItemJnlLine
Some of our partners have greatly enhanced the Assembly-to-Order functionality and need to basically enhance all of the ATO functions in the codeunit "Sales-Post" with their own code. In a lot of cases the easiest approach is to replace the existing functions by implementing the Handled Pattern.
To be implemented right at the beginning of procedure PostATOAssocItemJnlLine:

Integration Event:
OnBeforePostATOAssocItemJnlLine
Signature:
SalesHeader: Record "Sales Header";
SalesLine: Record "Sales Line";
var PostedATOLink: Record "Posted Assemble-to-Order Link";
var RemQtyToBeInvoiced: Decimal;
var RemQtyToBeInvoicedBase: Decimal;
var ItemLedgShptEntryNo: Integer;
var IsHandled: Boolean

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


NONCONfirmable message missing option

I'm using a CoAP request node to send message to a coap-server hosted on a distant machine. I can't find the way to choose NONCON (non confirmable) option.

Thank you, @SalarJamal, I think this feature is currently not supported yet (at the moment, all messages are confirmable). I'll add an option to make this behavior configurable.

Thank you Mr. @JKRhb

I added the feature in #78 and will release a new version shortly :)


Feature Request: Automatically Implement a ProtobufSrcInfo Trait to provide i.e. the original full protobuf name

Description:
I would like to request a new feature for prost-build to automatically implement a ProtobufSrcInfo trait for each generated struct.
Currently, the only info I would like in the trait at the moment would be a constant PROTOBUF_FULL_NAME to return the full protobuf name of the struct (i.e. the protobuf package + message name), similar to the DESCRIPTOR.full_name attribute in Python's protoc generated code. I'm sure there would be additional information people might want later.
Rationale:
In many cases, it  would be useful to have access to the full protobuf name of a message in Rust code, for purposes such as debugging, logging, or interfacing with systems that use the same protobuf API and potentially require the full protobuf names. Currently, prost-build does not generate this information, and users need to manually add it somewhere in their code.
My Specific Use Case
My specific use case for this feature is cross-language interoperability. Specifically for implementing pyo3 conversion traits on prost generated types. If I can extract the original protobuf path on the rust side at the struct level, I can derive implementations of pyo3 conversion traits as the protobuf path can be used to find the full python path for the equivalent python class that needs to be returned from pyo3 trait implementations.
Some details of my proposed solution
Add a trait in prost.
pub trait ProtobufSrcInfo {
    const PROTOBUF_FULL_NAME: &'static str;
}

Add a method to tonic_build::prost::Builder
builder.impl_protobuf_src_info()

or if we need to support the option to only implement this on some messages, we could have a path argument, as we do with
Builder::message_attribute
builder.impl_protof_src_info(my_specific_protos_path)

Isn't this already provided by the prost::Name trait, which can be enabled with prost_build::Config::enable_type_names?

Thanks @romac I'm not sure how I missed this, nothing jumped out of the docs to me, and I failed to find it when grepping around the source code. But yes, this is exactly what I was looking for, so I'll close this.

prost_build::Config::enable_type_names could use some extra documentation to make it more discoverable.
@BaxHugh Are you willing to add an example to the documentation?


ccccccgentierhfjtgnvjvcgcvigdcbiutrjntlduuiv

Steps to reproduce
Tell us about your environment:

Puppeteer version:
Platform / OS version:
URLs (if applicable):
Node.js version:

What steps will reproduce the problem?
Please include code that reproduces the issue.

What is the expected result?
What happens instead?

I'm so sorry, my keyboard just had a stroke


Setup portfolio mobile website

Fix the path to the images folder
Applied the mobile-first approach
Fix measurement units

Greetings, I have corrected the size of my nav-var, and I have also corrected my image position and responsive settings.


Closures

Should surface the limitation that closures cannot be copied because the closed over scope is inaccessible and unserializable.
Otherwise this is good!
If you want to see an example of where I handle bigints, date objects, and other edge cases check out weird-json

Hi @i5ik ,
If following test case covers the closure senario that you are thinking about, it has been already supported:
describe('Closures', () => {
  it('should keep closures', () => {
    const user = {
      name: 'User 1',
      speak: function () {
        function speakWithMic(name) {
          return 'My name is ' + name + ' and I speak with Mic';
        }
        return speakWithMic(this.name);
      },
    };

    const newUser = deepCopy(user);
    newUser.name = 'User 2';

    expect(user.speak()).toBe('My name is User 1 and I speak with Mic');
    expect(newUser.speak()).toBe('My name is User 2 and I speak with Mic');
  });
});

BTW, I found weird-json is interesting and I will spend some time on playing around it.
Thanks for sharing it.
Greetings from Yuchao :)

Hey Yuchao :)
I was thinking more along the lines of:
describe('Closures', () => {
  it('should keep closures', () => {
    const firstName = 'Heg';

    function userSpeak() {
      return `My name is ${firstName} and I speak with Mig`
    }

    const newUserSpeak = deepClone(userSpeak);

    expect(userSpeak()).toBe('My name is Heg and I speak with Mig');
    expect(newUserSpeak()).toBe('My name is Heg and I speak with Mig');
  });
});

Functions look more like a procedure value, what would be a real use case that requires deep clone a function?
In above test case, looks like two functions are doing the same thing.

Ah, I think I see what you're saying, you don't see any use case for deep cloning of functions because you may as well just pass them around by reference, and if you want to create a new function or closure, just invoke the parent function. That's fair enough. I was coming at it from the "serialize" point of view, but I see your use case doesn't need that. All good then!

Functions look more like a procedure value, what would be a real use case that requires deep clone a function?
In above test case, looks like two functions are doing the same thing.

😂 Sounds like you think my example is no good, but just remember, I based it on your example, so if you think it's no good then that's on you. 😆 😂
But I guess you're just coming at it from a different perspective...I think I now see what you're saying, you don't see any use case for deep cloning of functions because you may as well just pass them around by reference, and if you want to create a new function or closure, just invoke the parent function. That's fair enough. I was coming at it from the "serialize" point of view, but I see your use case doesn't need that. All good then!

I provided the initial example for clusure purpose only. Since I am not sure what use case does function cloning serve, that's why I am asking for it. In addition, it doesn't do any serialisation but just treat function as a "procedure value" and assign it to new cloned object.

Yep that's what i thought your view was. Thanks for sharing! 😊


[WIP] px4io: move to WQ to reduce control latency

I noticed the px4io control latency increased substantially (> 1 ms), likely due to the number of things that have moved to work queues (sensors most recently) that further reduced the relative priority of the px4io task. Moving px4io to the inner loop WQ thread (wq:rate_ctrl) gives it the lowest possible latency. It also saves a little bit of memory (~3.3 kB) and cpu (~1%) relative to current master.

Master vs PR on fmu-v3.
io control latency: 34647 events, 31857745us elapsed, 919.50us avg, min 203us max 3971us 776.776us rms
px4io: control latency: 37762 events, 11297506us elapsed, 299.18us avg, min 142us max 1890us 349.106us rms

@PX4/testflights could you please give this a quick flight test on any board that has a px4io? That's any of the px4_fmu-v2, px4_fmu-v3, px4_fmu-v4pro, px4_fmu-v5 boards. Testing only 1 or 2 should be sufficient. Thanks!


BC break – Drupal 9 & 10 config_sync_directory now unconditionally overridden by settings.ddev.php

Description
Trying out DDEV v1.19.0-alpha3 I noticed it comes with its own settings.ddev.php file for Drupal 9 & 10 now which has no condition anymore around $settings['config_sync_directory'] = 'sites/default/files/sync';.

https://github.com/drud/ddev/tree/v1.19.0-alpha3/pkg/ddevapp/drupal/drupal9
https://github.com/drud/ddev/tree/v1.19.0-alpha3/pkg/ddevapp/drupal/drupal10

In the settings.php file you normally define $settings['config_sync_directory'] quite on top of the file. Best practice it so set it to a location outside the webroot, which is version tracked:
https://github.com/drud/ddev/blob/e54753a09c9f3f68c49383fe00a03805cdee4f75/pkg/ddevapp/drupal/drupal9/settings.php#L253-L264
Only quite on bottom of that settings.php file settings.ddev.php gets included:
https://github.com/drud/ddev/blob/e54753a09c9f3f68c49383fe00a03805cdee4f75/pkg/ddevapp/drupal/drupal9/settings.php#L759-L762
But this settings.ddev.php file now unconditionally overrides any prior $settings['config_sync_directory']:
https://github.com/drud/ddev/blob/e54753a09c9f3f68c49383fe00a03805cdee4f75/pkg/ddevapp/drupal/drupal9/settings.ddev.php#L42-L43
Proposed resolution:
Similar to Drupal 8 let's wrap the $settings['config_sync_directory'] line in the Drupal 9 settings.ddev.php to check if it has already been set: https://github.com/drud/ddev/blob/e54753a09c9f3f68c49383fe00a03805cdee4f75/pkg/ddevapp/drupal/drupal8/settings.ddev.php#L43-L55

Thanks, not sure how that happened.
Easy to do a PR if you want to...
Here's what it looked like in v1.18.2, https://github.com/drud/ddev/blob/0ee9cfb16ed1dd789f4648265849aaf899f4f6fa/pkg/ddevapp/drupal.go#L118-L136

I moved the settings.ddev.php 's to their own directory so they aren't embedded in go code, and must have messed up. But it means that PHP devs can now super easily contribute to improvements. Sorry to have messed it up.

Cool, I'll create an PR now. My first contribution I think.

RTBC++. We have a lot of projects with existing settings.php files that rely on how it used to work, and those now break with DDEV 1.19-alpha3

This has returned

@stewest - I don't know of any changes in this area, but please don't make a cryptic comment in an old issue; open a new issue with full info and link to this one.  While you're there, please make sure that the type in your project is the type you want.


QUIT: Use a thread-safe queue

I merged cinchrb/cinch#195 into master.
It introduced the quit thread, but the thread uses a busy loop.
The thread should sleep until needed, so it is preferable to use a condition variable.

Hmm...
lib/cinch/bot.rb:235:in `synchronize': can't be called from trap context (ThreadError)

9cb42b0d0953ebb1f206e9ed10b964106fe0adc8: A thread-safe queue is suitable for this purpose. Mutex#synchronize must not be called in a signal handler.


Samigo is sending over values of "0" instead of nulls when no grades have been recorded

Currently, when students have not yet received a score in a Samigo assessment, the tool is reporting scores of "0" to the Gradebook:

These should be null values, as this is affecting course grade calculations.
By comparison, when a student has not received a score in Assignments, a null value is delivered to the Gradebook.

Created Samigo JIRA issue:
https://jira.sakaiproject.org/browse/SAM-2824


[AdViewer] Merge legacy repository

Let's merge the last internal repo to ease working on test app with sdk built from source

Can you add the licensing headers like we did on the SDK?

This PR is just a merge of legacy code history w/o any change, but ok will do on following PR


Workspaces & Splash Screens

Microsoft PowerToys version
0.84.1
Installation method
GitHub
Running as admin
No
Area(s) with issue?
Workspaces
Steps to reproduce
Setup a workspace to open an program that has a start-up splash screen, when the workspace is activated PowerToys Workspace tries to size and move the splash screen and fails and then the application opens to the wrong size and in the wrong place!
✔ Expected Behavior
To open the application, wait for the splash screen to close and then move the application window to the required size and place.
❌ Actual Behavior
When the workspace is activated PowerToys Workspace tries to size and move the splash screen and fails and then the application opens to the wrong size and in the wrong place!
Other Software
No response

@allisongsa can you provide an example of an application you are seeing this with? Different app splash screens can often behave differently so it's helpful to know which apps are exhibiting this issue.
/needinfo

Hello, the application that is the worst is a program called BankTree (used for accounting), their web site is:
https://www.banktree.co.uk/
I have asked their support to request an option to turn off the splash screen but don't expect them to be agreeable!
Best regards, Geoff.

@allisongsa can you provide an example of an application you are seeing this with? Different app splash screens can often behave differently so it's helpful to know which apps are exhibiting this issue.
/needinfo

Microsoft Word

@allisongsa can you provide an example of an application you are seeing this with? Different app splash screens can often behave differently so it's helpful to know which apps are exhibiting this issue.
/needinfo

Microsoft Word

@pbargiona try adding /q as a CLI argument for Word in the Workspaces Editor. This arg is generally used in Office Apps to disable splash screen.

@allisongsa can you provide an example of an application you are seeing this with? Different app splash screens can often behave differently so it's helpful to know which apps are exhibiting this issue.
/needinfo

Microsoft Word

@pbargiona try adding /q as a CLI argument for Word in the Workspaces Editor. This arg is generally used in Office Apps to disable splash screen.

Currently I don't think it is worth it because there is a bug messing with fancy zones snapping and splash-screended applications seem not to be affected. I can get Word to the proper size with macros.


Add option to add certificate for taget(s)

I have an issue with certificate when trying to use internal elastic server as target to send errors with policy-reporter
(k logs pod/***-policy-reporter-b9756956d-j9x4n)
2022/09/16 12:40:44 [ERROR] Elasticsearch PUSH failed: Post "https://***:9260/sec-kyverno-2022.09.16/event": x509: certificate signed by unknown authority

Can you please add an option to add custom CA certificate(s)?

With the PR I created, you are able to add your cert as volume and configure the path as RootCA for your target. Would this work for your?

I released v2.13.0 of the helm chart with the new certificate config for most outputs including elasticsearch

Hi! This does not seem to work for me. Was this tested?
Does not work if I set "certificate" as a path to a mounted cert file from configmap, nor if I just set "skipTLS: true"
Logs of pod:
2022/09/23 11:46:51 [ERROR] Elasticsearch PUSH failed: Post "https://***/sec-kyverno-2022.09.23/event": x509: certificate signed by unknown authority
My cert is ok - I confirmed it with curl on same server

I was not able to test it because I have elasticsearch with custom cert setup.
So you mounted your cert secret as volume in the container and then configured the path in the certificate property right?

Hell, sorry, my bad!
I used same helm values config with only adding new parameters, so I didn't change image versions. I will fix as soon as I can to confirm everything works

2022/09/24 09:41:20 [INFO] Elasticsearch PUSH OK
All good

Ah Great, thanks a lot for your feedback


all: add license to every module

@giulliano-bueno could you approve this PR? It's just updating the license to each individual go module to allow pkg.dev.go to display the documentation as per their license policy.

ping @giulliano-bueno, @mcrakhman, could you approve this PR? It's just updating the license to each individual go module to allow pkg.dev.go to display the documentation as per their license policy.

ping @giulliano-bueno, @mcrakhman, could you approve this PR? It's just updating the license to each individual go module to allow pkg.dev.go to display the documentation as per their license policy.

I was talking with Lluis exactly about this problem this week. Thanks @Hiccup-C137


resource key in links result

Is this designed to work this way?
I tried
$item = new Item($data, $this->transformer, 'teachers.students');
$this->manager->setSerializer(new JsonApiSerializer($route));
the links in my url looks like this
"self": "http://testing-api.dev/api/v1/teachers/2/students/teachers.students/8/relationships/students",
"related": "http://testing-api.dev/api/v1/teachers/2/students/teachers.students/8/students"
If you notice "teachers.students" appends on the self and related key in the result json
should be http://testing-api.dev/api/v1/teachers/2/students

fixed the issue 💃


No module named 'networks'

When i try to run training_scripts/exp083.py file appears this error:
Traceback (most recent call last):
File "training_scripts/exp083.py", line 21, in
from networks import largest as Net
ModuleNotFoundError: No module named 'networks'

Apologies for the late reply. I just uploaded the missing file.
Thanks for reporting it!


Addressbook: Cannot set property 'state' of undefined

UI Version: 0.X.X
Description:
electron  [Unhandled Promise Rejection] TypeError: Cannot set property 'state' of undefined
              at Addressbook.flagNodeIncompatible (/Users/federico/Projects/voyager/app/src/main/addressbook.js:119:5)
              at _callee9$ (/Users/federico/Projects/voyager/app/src/main/index.js:572:17)
              at tryCatch (/Users/federico/Projects/voyager/node_modules/regenerator-runtime/runtime.js:62:40)
              at Generator.invoke [as _invoke] (/Users/federico/Projects/voyager/node_modules/regenerator-runtime/runtime.js:296:22)
              at Generator.prototype.(anonymous function) [as throw] (/Users/federico/Projects/voyager/node_modules/regenerator-runtime/runtime.js:114:21)
              at step (/Users/federico/Projects/voyager/node_modules/babel-runtime/helpers/asyncToGenerator.js:17:30)
              at /Users/federico/Projects/voyager/node_modules/babel-runtime/helpers/asyncToGenerator.js:30:13
              at <anonymous>
              at process._tickDomainCallback (internal/process/next_tick.js:228:7)

Doesn't happen anymore.


added initial set of descriptions for VM and VMSS properties

@veronicagg thanks for the review! Addressed the comments above. This particular PR is meant to get a jump start on descriptions, but look forward to more incremental follow-up PRs over time to bring it up to 100% description coverage :)

 https://github.com/Azure/azure-sdk-for-ruby/pull/922

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

 https://github.com/Azure/azure-sdk-for-python/pull/1388


Changes to Contour package for new namespace-scoped Role (in Contour v1.21.0)

Feature Request
The next release of Contour (v1.21.0) will switch from using a ClusterRole to a namespace-scoped Role to configure RBAC for leader election resources (Leases and Events). This is a small security change to limit Contour's access footprint in a cluster.
As this change adds a new resource (a new Role) to Contour's base deployment configuration, some steps will need to be taken in TCE to accommodate this change (e.g. setting the namespace on the new Role correctly).
Describe alternatives you've considered
N/A
Additional context
See Contour change: https://github.com/projectcontour/contour/pull/4204
cc @vmware-tanzu/pkg-contour-owners @vmware-tanzu/contour-owners

This will come into effect in Contour v1.21.0 which is due out soon


⚠ Bofrost.at has degraded performance

In fb70b3d, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2181 ms

Resolved: Bofrost.at performance has improved in 617d2da.


Add end-to-end JS ping

In addition to knowing the ping from server to internet exit, would also be interesting to know the ping time from browser to server. This will have to be done via JavaScript.

Should this just be automatically done as part of the ping function (and added as a second line) or a separate one?


[WIP] Idea for Integration Test

Just a sketch/ WIP of thinking about integration tests (see integration.test.js not integration.sh). The idea is to run a few docker containers in a jest test and test that everything works that way. This can then be part of our standard test suite (though it'll be slow, so it might be skipped by default).
Thoughts on this direction?

Closing since we merged integrations based on this already


PDF page contents with a null value in its DecodeParms are rendered blank

PDF file: Dokument_ohneOCR.pdf
Configuration:

Web browser and its version:

Chrome 49.0.2623.112
Firefox 45.0.2

Operating system and its version: Mac os X 10.11.3 (15D21)
PDF.js version: 1.3.91
Is an extension: No

Steps to reproduce the problem:

Open the PDF with the viewer
A blank page is displayed. The console shows this message: 'Warning: Invalid stream: "TypeError: params.get is not a function'

What is the expected behavior?

The viewer must display the text of the page (a Lorem ipsum text)

What went wrong?
The attached pdf file contains a null value in the DecodeParms array of the /Contents of the /Page.

The following lines are the source PDF objects
9 0 obj
<</Type/Page/Parent 3 0 R/MediaBox[0 0 595.275591 841.889764]/Contents 10 0 R/Resources 12 0 R>>
endobj
10 0 obj
<</Filter/FlateDecode/Length 165/DecodeParms[null]>>stream
x�u�1AE{N�D`�a�71�Sy�c��լ��'�l�4��X������=��DZZ3Jͬ�Y��yI���n��|3
��nт�5��%�0X���e���B�4���F�\�M8"�`ҨTQ�����<�VȱZk16�T)e��������L������7�*�9�
endstream
endobj

The warning message is thrown because the PredictorStream function from stream.js starts with the following line:
    var predictor = this.predictor = params.get('Predictor') || 1;

The previous code fails if params is an array containing a null value. The rest of the PredictorStream logic is not executed, so no stream is returned.
I have been able to render the document property by enclosing that line in a try/catch block:
    try {
      var predictor = this.predictor = params.get('Predictor') || 1;
    } catch (e) {
      predictor = this.predictor = 1;
    }

Maybe it's not the best solution, but it works (The last time I did something serious with JS was with Netscape :-P).
Just a little bit of additional information: Mac OS X Preview behaves exactly like PDF.js whereas the file is rendered properly by Adobe Acrobat Reader DC.
Link to a viewer.

@eljolge Thanks for the very thorough bug report!
Are you the creator of the PDF file, and if so can we include it in our test-suite?

No, I am not -directly- the creator, but you can include it in your test-suite. No problem.

No, I am not -directly- the creator, but you can include it in your test-suite. No problem.

Thank you! The fix for this issue has now landed.


[TUTORIAL] kept-in-a-box installation fails with only two CPUs awarded to the VM

Hello,
According to https://tutorials.keptn.sh/tutorials/keptn-in-a-box-08/#1 sizing section, a VM with 2 vCPUs is the minimum needed for a default installation.
Tutorial was spinned up on a Mac and through multipass with the following settings: multipass launch --name keptn --cpus 2 --mem 8G -d 20G
ubuntu@keptn:~$ cat /proc/cpuinfo | egrep '(processor|name)'
processor	: 0
model name	: Intel(R) Core(TM) i5-1038NG7 CPU @ 2.00GHz
processor	: 1
model name	: Intel(R) Core(TM) i5-1038NG7 CPU @ 2.00GHz
The installation failed due to the jmeter pod not starting:
ubuntu@keptn:~$ sudo kubectl describe pod jmeter-service-679fd5b56c-xs4cf -n keptn | grep FailedScheduling
Warning  FailedScheduling  2m30s (x37 over 52m)  default-scheduler  0/1 nodes are available: 1 Insufficient cpu.
Lowering drastically requests of the jmeter-service container allowed it to start, but I guess that's not how it is supposed to be done !
Maybe has an external component recently bumped their CPU requests ?
All in all either a tweak need to be found or the minimal spec be bumped a little for Scrooge-Mc-Ducks like me !
Regards

Completed successfully with a 4 CPU VM but did encounter a small issue of pvc binding with gitea-0:
pod stuck in init mode claiming 'pod has unbound immediate persistentvolumeclaims' despite the matching pvc showing as claimed:
Events:
Type     Reason            Age                From               Message

Warning  FailedScheduling  20m (x3 over 20m)  default-scheduler  0/1 nodes are available: 1 pod has unbound immediate PersistentVolumeClaims.
Normal   Scheduled         20m                default-scheduler  Successfully assigned git/gitea-0 to keptn
Normal   Pulling           20m                kubelet            Pulling image "gitea/gitea:1.12.5"
Normal   Pulled            8m24s              kubelet            Successfully pulled image "gitea/gitea:1.12.5" in 12m0.394958605s
Normal   Created           8m23s              kubelet            Created container init
Normal   Started           8m23s              kubelet            Started container init
Normal   Pulling           8m20s              kubelet            Pulling image "gitea/gitea:1.12.5"
ubuntu@keptn:~$ sudo kubectl get pvc -n git
NAME                      STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS        AGE
data-gitea-postgresql-0   Bound    pvc-b70c6cd4-535e-47ee-ba1b-27d8b0284518   10Gi       RWO            microk8s-hostpath   22m
data-gitea-0              Bound    pvc-8b04b947-8eb4-4347-b8ba-b2ab5adc3abf   10Gi       RWO            microk8s-hostpath   22m
Resolved by deleting the pod

thanks for bringing this up - looping in @sergiohinojosa as the maintainer of this tutorial

Hi @fcoquelet,
thanks for noticing and sorry for not updating the sizing requirements. A couple of months ago I added gitea (self-hosted git server) for exposing and showing how Keptn manages the projects and configuration with GitOps. Since I'm adding gitea in the default bundle, it makes the whole installation a bit heavier (to say the least). I have added a ticket or noteToSelf  in the KIAB repo https://github.com/keptn-sandbox/keptn-in-a-box/issues/12
In order to do the sizing properly I would want to add and review the requests and limits for all deployments to trim everything down. Then spinning different sizes and check that everything works. So as you see is an easy but time consuming task and I'm lacking at the moment of it.
Now, regarding the PVC issue, I have not seen it, but if recycling the pod solved it, means that there was some sort of race condition while enabling storage in Microk8s.
Thanks and best regards
Sergio

should we increase the resource limits in the tutorial @sergiohinojosa ?

@jetzlstorfer I just added a warning on the tutorial and how to disable the Gite module. I just don't want to solve this by adding more resources without properly measuring and trimming the deployments. There are some deployments that can be trimmed. I send a PR for 0.8.3 and also how to solve this., we can close this

@sergiohinojosa if this can be closed, please close :) thank you!


Update binder notebook

Preview: https://github.com/qiskit-community/prototype-entanglement-forging/blob/binder/README.md

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Object's builtin properties are exposed

The SelectFormat string
{VAR, select,
  male {He}
  female {She}
  other {It}
}

called with VAR = "toString" produces "[object Object]" as result.
Similar results for hasOwnProperty, valueOf, constructor, ... and for PluralFormat and SelectOrdinalFormat.

Oh, and you are able to use plural as a replacement for select:
{VAR, plural,
  male {he}
  female {she}
  other {it}
}

actually works when called with VAR = "male" or VAR = "female".

Yup, that was a bug. Should be fixed now that we check data.hasOwnProperty(value) rather than value in data. Added some tests for that too.

Thanks for your quick response :) The example which I posted above works smoothly now.
Unfortunately, the following MessageFormat expression would overwrite hasOwnProperty.
I think Object.prototype.hasOwnProperty.apply(data, value) should do the trick here.
{VAR, select, hasOwnProperty{true} other {something}}

In addition, there is a similar issue with user provided format functions:
{VAR, __defineSetter__}

I switched the check to {}.hasOwnProperty.call(data, value), and modified one of the new tests to account for this. Thank you for the pentesting!
Regarding the __defineSetter__ case, can you come up with an example that doesn't work like it should? After (admittedly only a little) testing, all I could manage are slightly different errors compared to more common cases. If so, please open another issue for that, as it's really a different thing.

Perfect!
Well, you are right, __defineSetter__ is a separate topic. I am going to open another issue for the discussion of it.


Make graphsage link prediction reproducible

Part of #749

Codecov Report

Merging #925 into develop will increase coverage by 0.2%.
The diff coverage is 100%.

@@           Coverage Diff            @@
##           develop   #925     +/-   ##
========================================
+ Coverage     83.8%    84%   +0.2%
========================================
  Files           53     53
  Lines         5653   5112    -541
========================================
- Hits          4735   4292    -443
+ Misses         918    820     -98

Impacted Files
Coverage Δ

stellargraph/mapper/sequences.py
92.1% <100%> (ø)
:arrow_up:

stellargraph/mapper/sampled_link_generators.py
91.5% <100%> (+9.4%)
:arrow_up:

stellargraph/data/edge_splitter.py
89.6% <0%> (-2.7%)
:arrow_down:

stellargraph/layer/graphsage.py
79.4% <0%> (-0.4%)
:arrow_down:

stellargraph/datasets/datasets.py
50% <0%> (+6%)
:arrow_up:

Continue to review full report at Codecov.

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

Oh, also, should this have a changelog entry?

I'm trying a rebuild since I couldn't reproduce the failure on CI locally to check whether it's intermittent.. but it did seem like a legitimate failure for the specific test I'm adding here. I'm trying to run it locally with num_iter=100 now

@huonw @kieranricardo I've rebuilt CI a few more times and run it locally after copying the pip freeze in CI to a new local environment, and I'm not able to reproduce the error in this build - I'll file an issue if it ever comes up again?

Hm, that's suspicious, but yeah, let's merge if we can't reproduce easily now.

Hmm I ended up reproducing the error locally, which also happened only for test_link_prediction[shuffle=True]...
It's not obvious to me at the moment where the problem is coming from since the mechanism for link prediction is pretty much the same as (or even a subset of) unsupervised learning. I think it's also unlikely to be a problem with the code in Model.fit_generator(shuffle=True) in general since we haven't seen the other tests fail intermittently.
I think I might just take out shuffle=True from the test for now and include a FIXME. I don't think it's super critical that we need to support reproducibility with shuffle=True turned on, since all it does is mix up the batches before passing them to the model, but our sequence objects already have an internal shuffling mechanism, so it would be like double shuffling.


Decide which functions to export

Because a lot of the functions/terms have meanings outside the context of theory of interest, Yields.jl has avoided exporting a lot of functions. For example, you need to call: Yields.Continuous(0.1) instead of just Continuous(0.1). Combined with the ability to import Yields: Continuous to bring specific items into scope.
This issue is to discuss the inclusion/exclusion of certain exports before v1 milestone.

Maybe it's because I use C# in my day job, but I would prefer giving concepts long and descriptive names that don't collide with other contexts, and then export them. Like ContinuousCompounding() over Yields.Continuous(), or ContinuousRate(0.1) over Yields.Continuous(0.1). In this case, the long names would also provide a clearer distinction between what is a compounding frequency and what is a rate with a particular compounding frequency.
A general question is, whether structs should be exported. Ideally, they should be implementation details that the user should not worry about, but that would require that Yields.jl export some nice helper function that construct them. This is done presently for YieldCurves, but I'm not sure it's universal.
One thing that confuses me is the distinction between the rate and zero functions. Are there curves where they would meaningfully differ? Should all implementations of AbstractYieldCurve be required to provide both? Also, the name zero is a little unfortunate, since it is generally used for the additive identity for a type.

I'll try and take the time to think more about the points/examples you gave about the names and respond about them when I get more time, but I wanted to quickly answer this part:

One thing that confuses me is the distinction between the rate and zero functions. Are there curves where they would meaningfully differ? Should all implementations of AbstractYieldCurve be required to provide both? Also, the name zero is a little unfortunate, since it is generally used for the additive identity for a type.

zero
I think I probably chose zero because I was referencing "Options, Futures, and Other Derivatives" which preferred the term zero over spot but I think it may be more common in other places to use spot. Do you think that would be preferable?

rate
rate is effectively convert(Float64,rate<:Rate), or said in plain english: the way to get the floating point value inside, e.g., rate(Periodic(0.03,1)) returns 0.03.
I'm open to other names or maybe just enforce the convention of using convert explicity?
This brings up a related issue, which is that in ActuaryUtilities.jl, a function like irr currently returns a Float64 instead of a Yields.Periodic. I've thought about whether it should return a Rate type so that it carries the semantic information that it's a periodic rate (instead of, e.g. continuous) and for consistency across the JuliaActuary packages. I haven't felt so strongly about it to initiate that change, but I'm curious what you think?

Ah, ok, I get the distinction between zero and rate then, thanks. I think what confused me was that rate(::Constant{T}) returns a T which is often a Rate.
As for naming, I actually think zero would be a good name if it hadn't been a semi-reserved word. Maybe zerorate or zero_rate? I think spot could be confusing, e.g, a spot swap (as opposed to forward starting) is still quoted as a par rate.
I think it would be neat to have irr and similar return a Rate. It would provide the user with a lot of safety to work only with Rate instances and not with naturally ambiguous Float64s - no accidental mess-ups in compounding convention (as I have done uncountably many times myself in every other language I have ever used - plus Excel 😆).

Ah, ok, I get the distinction between zero and rate then, thanks. I think what confused me was that rate(::Constant{T}) returns a T which is often a Rate.

Do you prefer rate(r:<Rate)::Float or enforce the convention of convert(Float,r:<Rate)? I lean towards the first unless the name is too confusing.

As for naming, I actually think zero would be a good name if it hadn't been a semi-reserved word. Maybe zerorate or zero_rate? I think spot could be confusing, e.g, a spot swap (as opposed to forward starting) is still quoted as a par rate.

I think zero is okay: the only usage in Base/stdlib is a one-argument zero(x) whereas Yields only has a multple argument version, e.g. zero(yield,time).
I could see a use for a additive identity element, e.g. if additively reducing over a collection of rates representing yield components (e.g. risk free + credit + liquidity + ...), which makes me think maybe zero should be reserved for a yield curve with zero rates. #82

I think it would be neat to have irr and similar return a Rate. It would provide the user with a lot of safety to work only with Rate instances and not with naturally ambiguous Float64s - no accidental mess-ups in compounding convention (as I have done uncountably many times myself in every other language I have ever used - plus Excel 😆).

I agree: https://github.com/JuliaActuary/ActuaryUtilities.jl/issues/62

Sorry, I got too many notifications and missed that there was a question here.

Do you prefer rate(r:<Rate)::Float or enforce the convention of convert(Float,r:<Rate)? I lean towards the first unless the name is too confusing.

I don't have that much of an opinion here. I would be fine with both. I could add in a third possibility which is to not provide these at all. That would make it clear to the user that they are leaving the protected space of typed rates by using my_rate.value. But maybe that would just be annoying 😄.

I think zero is okay: the only usage in Base/stdlib is a one-argument zero(x) whereas Yields only has a multple argument version, e.g. zero(yield,time).

👍

Maybe it's because I use C# in my day job, but I would prefer giving concepts long and descriptive names that don't collide with other contexts, and then export them. Like ContinuousCompounding() over Yields.Continuous(), or ContinuousRate(0.1) over Yields.Continuous(0.1).

Sorry, I thought I remembered responding to this point but maybe I never submitted it...
For the naming, I think a pretty common pattern, especially in production code, is to qualify imported functions with the pacakge name to make it clear where a particular function is coming from.
E.g.
import Yields

r = Yields.Continuous(0.05)
Yields.discount(r,...)

over
using Yields

r = Continuous(0.05)
discount(r,....)

So in this case, having a name like ContinuousCompounding would end up being being Yields.ContinuousCompounding which is pretty verbose and Compounding and Yields becomes pretty redundant.
I agree that, on it's own Continuous would be a bit vague but I think the package name can provide the needed context and is my preferred solution in the tradeoff between conciseness, lack of ambiguity, and ergonomics.
The above is attempting to keep the argument self contained and stand on its own without a comparison to other languages, but in comparison to other languages my opinion is that it strikes a balance between the LongCamelCaseNames found in some languages and the abstract terseness of, e.g. Haskell.

In this case, the long names would also provide a clearer distinction between what is a compounding frequency and what is a rate with a particular compounding frequency.

The distinction is really Rate vs CompoundingFrequency and could be enforced by only allowing a Rate construction explicitly: e.g. Rate(0.05,Continuous()) instead of Continuous(0.05) but out of convienince and ergonmoics the former was removed from the exported API (#83) per this suggestion (maybe I misinterpreted).

A general question is, whether structs should be exported. Ideally, they should be implementation details that the user should not worry about, but that would require that Yields.jl export some nice helper function that construct them. This is done presently for YieldCurves, but I'm not sure it's universal.

In summary: I feel like the names are in the right place and has been pleasant in everyday usage, but maybe that's not representative of other's experience. Please let me know if you feel like that's the case and worth further consideration. Thanks for the continued thoughts.


A hosts entry should be added for each link

In Docker links a hosts entry is added for each linked container. Flocker does not add these lines to /etc/hosts.
https://docs.docker.com/userguide/dockerlinks/#updating-the-etchosts-file

We are moving our development planning to JIRA. This is issue is now being tracked at https://clusterhq.atlassian.net/browse/FLOC-929. You are welcome to file additional issues in GitHub if that's easier for you.


KOGITO-766: Kogito Keyboard Shortcuts API

On this PR:

Created and exposed Keyboard Shortcuts API for editors to use inside Kogito channels
Created an overlay to display active keyboard shortcuts. The experience is the same across all Kogito channels (see Video below)
Unified PatternFly configuration across all channels, since now the envelope needs a "full" version of PatternFly inside it. Build configuration files are less complex and we're now sure that everyone is using the same PatternFly loaders. Artifact size reduced a little bit too.
Exposed a new "context" variable with the current Operating System

Video: https://issues.redhat.com/secure/attachment/12467822/Screen Recording 2020-03-16 at 12.59.11.mov
VSIX for testing: https://drive.google.com/file/d/1pKGSpn6xHm3sll8TH0XOc3fp6FMHjkN6/view?usp=sharing
Related PRs:
https://github.com/kiegroup/lienzo-core/pull/102
https://github.com/kiegroup/lienzo-tests/pull/84
https://github.com/kiegroup/appformer/pull/922
https://github.com/kiegroup/kie-wb-common/pull/3221
https://github.com/kiegroup/kogito-tooling/pull/86

@ederign Sure. I'll do when I resume this task.

Resuming this PR, I'll start writing tests.

@jomarko @karreiro can you please take a look at this?

Manual Check
This list is just for my easier tracking progress

[ ] VS Code
[ ] Online Editor
[ ] Desktop
[ ] Github Extension

Code review
Is pending

Manual review - 01
See pr-review-popups attached to https://issues.redhat.com/browse/KOGITO-766. There is minor issue with shortcuts panel when other popup is shown.
Firstly search overlays shortcuts panel and secondly shortcuts panel can be shown when dmn constraint popup active.
It is minor issue. I would like to ask what is your opinion. Should I create some ticket for it or there is chance ~0 prevent these overlays.

Manual review - 02
We have set DMN specific shortcuts. In DMN grids we invoke context menu with Ctrl + Space. In DMN data types we can edit, save, insert field data type by keyboard. Those Shortcuts are not listed. I expect it is because we register them differently than using new API. Do we plan to unify registration?
For more details see pr-review-dmn-specific attached to https://issues.redhat.com/browse/KOGITO-766

Manual review - 03
Shouldn't we list also shortcuts below? I am not sure as they kind of conflict what is generally available in applications:

Undo/Redo
Save
Zoom

Manual review - 04
Similar to 01, however this is on desktop app. When shortcuts panel is active it is in foreground and the editor is in background. however save and close buttons are still usable. Not sure if this is real issue so asking what the rest of the team thinks about it.

Manual review - 05
Just question. The shortcuts icon is in left down corner of screen, not left down corner of  canvas of online editor. Is that OK?

Manual review - 06
We miss shortcuts panel in chrome github extension

Manual review - 07
Do we plan some ordering in the shortcuts panel? Just asking. As there is no option to search in panel.

@jomarko Thanks for the review. See remarks below. Code review will be replied inline.
Manual review - 01
Wil fix.
Manual review - 02
Those shortcuts were left out of this first iteration. An effort [1] was made to enable them to be added in the future, but they'll be addressed separately.
Manual review - 03
Undo/redo shortcuts are channel-specific. We have to think better about that, so we probably should create a new JIRA.
Manual review - 04
We don't want to block saving because the Keyboard Shortcuts overlay is displayed. The editor is still open, so you should be able to save your work normally.
Manual review - 05
Well... :)
This icon is added in the envelope, not in the editor, so it's not aware of UI changes in the editor. We can probably address that in the future, but I'd say not in this PR.
Manual review - 06
The icon should be there. If you built the Chrome Extension using yarn build:prod, the extension is pointing to the latest release, instead of your local changes. Please refer to README.md to more details on how to run the Chrome Extension with locally modified editors/envelope.
Manual review - 07
Adding a "search" option is a good idea. Since this panel is assembled dynamically, it will be "weird" to sort it IMHO. The shortcuts overlay respects the order in which they were registered.
CC @ederign

Created https://issues.redhat.com/browse/KOGITO-2268 for Manual review - 03

Created https://issues.redhat.com/browse/KOGITO-2267 for Manual review - 05

There was already https://issues.redhat.com/browse/KOGITO-1459 for Manual review - 02


Feat: Scrape IMDb Website

Describe the feature
IMDb website is famous for maintaining the movies database with all necessary information. I would like to scrape it for movies data.
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC 23 contributor
[X] I want to work on this issue

@Tisha6661 | We already do have a class for IMDB, check here.
Still you can add your method on the top of the same class, creating a new method.

@nikhil25803 I have created a pull request regarding this issue, please verify.


ui: Notify users of new VM password on resetting VM's SSH key

Description
This PR notifies users of the new password assigned to the VM when SSH key is reset

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[X] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[X] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?
Post Fix:

@blueorangutan ui

@Pearl1594 a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/5153 (SL-JID-283)


Default CertIdentityRegexp and CertOidcIssuer in SignOptions

What type of PR is this?
/kind feature
What this PR does / why we need it:

Default CertIdentityRegexp to (prow-build<EMAIL_ADDRESS>in default signer options
Default CertOidcIssuer to https://accounts.google.com/ in default signer options

Those two options/flags are required now that we use cosign v2. Identity should always be the same, and issue should match all identities that we use currently.
Which issue(s) this PR fixes:
None
Does this PR introduce a user-facing change?
- Default CertIdentityRegexp to `(prow-build@k8s-infra-prow-build.iam.gserviceaccount.com)|((krel-trust|krel-staging)@k8s-releng-prod.iam.gserviceaccount.com)` in default signer options
- Default CertOidcIssuer to `https://accounts.google.com/` in default signer options

/assign @saschagrunert @cpanato
cc @kubernetes-sigs/release-engineering

thanks
/lgtm
lets try again :)


Bump oauth version

$subject

Merging as the PR builder has passed for https://github.com/wso2-extensions/identity-inbound-auth-oauth/pull/2557

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/10539561900

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/10539561900
Status: success


Licence

Hi,
is it possible to add a licence?

Hello Manuel!
Very good point, I will add that to the agenda. Do you have a favorite one for your usecases? Otherwise, I think in the direction of Apache or Creative Commons.

This issue has been solved with #9


Sphinx server configuration file

Add support for a Sphinx configuration file to remove the .credentials, .gitignore and env vars requirement.
File: .sphinx-server.yml
Structure example:
credentials:
    username: user
    password: pwd
ignore:
    - .git/
    - another.file
environment: dev

The default values if the file or one section is missing:
credentials: ~
ignore:
    - .git/
environment: prod

Thx !

I have renamed sphinx-config file to sphinx-server.

Some changes:
Default file in this repository (on /):
credentials:
    username: ~
    password: ~
ignore:
    - .git/
autobuild: false

Moved to /opt/sphinx-server (with the server.py).
Then, the user can change this configuration by adding a .sphinx-server.yml file at root of his documentation (in web/):
credentials:
    username: user
    password: pass
ignore:
    - .git/
    - anotherfile
autobuild: true

Both files must be parsed, the second generated array (dictionaries) will erase values in the first one (recursively).
https://stackoverflow.com/questions/38987/how-to-merge-two-python-dictionaries-in-a-single-expression

Thx, @PLoic


Adding executable JavaScript code blocks

Any interest in allowing JavaScript code blocks to become executable? I've implemented a simple version of this already. Clicking on a JavaScript code block uses eval() to execute the code, and redirects the output from console.log to appended text at the end of the code block.
Right now every code block is self-contained. Defining a function in one code block won't be accessible in another code block. This behavior could definitely be configured so code blocks are accessible between each other on a per-slide level, or in some global-level section.
See it in action: http://5tephen.com/slideshow/slideshow.html#3
See the changes here: https://github.com/geluso/remark/commit/5dbb1de8e090f7090701c88d1e508a34db4f24ac
Is anyone interested in something like this?

eval() is strongly discouraged (but I understand this may be impossible without it).
We may be opening a security hole if someone copies a chunk of Markdown, or an entire HTML page containing a Remark presentation, to their own domain, and run those blocks of JS: users without good knowledge of how security sandboxes work may execute malicious snippets. We can't rely on users reading and understanding the code before clicking it because the attacker may have hidden malicious statements via CSS, for example.
I'm not rejecting the proposal entirely, only raising security concerns to discuss and see what others think :)

Totally. Thanks for the response. I'm absolutely interested in hearing more of the security concerns. I know eval can be extremely dangerous, but it doesn't seem totally bad when I host presentations on my own domain. I'm not evil! Maybe including eval would open some hole for someone to inject malicious JS even when linking to a presentation on my own domain. I just don't know.
Security concerns aside I'm also curious to hear if anyone else yearns for this feature. It's a small target in that it affects only JS code blocks, and it's most effective for ones with small output.
I like having it in my own presentations because I do lots of teaching and it's nice to click on something and prove that it works, or ask students to reason about what the output of something will be before it's executed.
Thanks again for responding!

While we wait for others to weigh in, have you considered simply revealing the output or the solution on your slides, @geluso? Not actually evaluating any code on the fly, but pasting the output when you're working on your presentations, and hiding it with -- initially, so that your students can guess before it's shown to them…


Moved tqdm to get rid of issues with pickling

Fixes pickling issue by moving tqdm bars around. Actually just gets rid of them in favor of the loop wrapper. Moves along https://github.com/CUNY-CL/yoyodyne/pull/197
Also added flag to allow the em loop to skip validation (not really necessary to monitor unless you want to add a patience function in there).

This is a necessary fix but it seems to revert a bit of other progress. To wit:

The custom formatting of the bar was nice, I think, and made the bars look like the ones in Yoyodyne. That's dropped here, I believe?

All that formatting is available for the wrapper if needed. Unsure if customizability is that important given that this is a lightweight library to offset Yoyodyne dependencies.

The previous design was modular and honestly read pretty clearly; this pushes the whole thing into a "God method" that is by all accounts less clear. To make this more concrete I think you should restore the log_likelihood method and use it inside the em method, which will make the latter easier to read. Is there some technical reason why this is not possible?

Log_likelihood is only ever called by em and even that is only occasional given the new bool. And it's only like, four locs. So the readibility is only so strong as an argument. Leaving it as its own method meant I needed to keep tqdm in another method. I'd rather have all the tqdm in one method so formatting fixes can be targeted to only the one method. So makes more sense to me to just merge the two.

This is a necessary fix but it seems to revert a bit of other progress. To wit:

The custom formatting of the bar was nice, I think, and made the bars look like the ones in Yoyodyne. That's dropped here, I believe?

All that formatting is available for the wrapper if needed. Unsure if customizability is that important given that this is a lightweight library to offset Yoyodyne dependencies.

I spent a lot of time figuring out how to do it...would you consider using it?

I spent a lot of time figuring out how to do it...would you consider using it?

I'll toy around with adding back in, but push comes to shove I'm going to go for the wrapper instead of including a whole set of novel methods just for progress bars. That fair?

I spent a lot of time figuring out how to do it...would you consider using it?

I'll toy around with adding back in, but push comes to shove I'm going to go for the wrapper instead of including a whole set of novel methods just for progress bars. That fair?

Sure; I asked because I think it's just an argument that has to be passed to the tqdm object you're creating.

@kylebgorman this takes care of progress bar preferences?

One nit, otherwise looks good to me. Should I merge?

Yes please, helps cascade other PRs to done.

@kylebgorman what's with the circle ci fail?

Oh, unit tests. Aight i'll fix those.


Create function code action doesn't work in lhs expression in ternary conditional expression

Consider the following case
function testConditional3(int arg) {
    string res = isGreaterThanZero(arg) ? "a" : "b";
}

currently create function code action creates following method while we expect a boolean return
function isGreaterThanZero(int i) returns string {
    return "";
}

Originally posted by @gayalkuruppu in https://github.com/ballerina-platform/ballerina-lang/pull/35815#pullrequestreview-981097638

Assignee: @bimsarapathiraja


Docker build stage in which to inject helper not correctly detected

What happened?
Failing to devspace dev on multistage Dockerfile
$ devspace dev
[snip]
[fatal]  Error building image: Error during image build: cannot inject restart helper into Dockerfile because neither ENTRYPOINT nor CMD was found.

How to fix this:
- Option A: Define an ENTRYPOINT (or CMD) in your Dockerfile
- Option B: Set `images.*.entrypoint` option in your devspace.yaml
- Option C: If you don't want to inject the restart helper, set `images.*.injectRestartHelper` to false

Tried to add ENTRYPOINT / CMD since they are defined in FROM  image, but that didn't help.
Dockerfile looks like this :
FROM python:3.7-alpine AS temp
[snip]

FROM logilab/cubicweb
COPY --from=temp dist/asset-*.tar.gz .
[snip]

So copied the ENTRYPOINT/CMD from logilab/cubicweb which felt wrong, but trial'n'error...
FROM python:3.7-alpine AS temp
[snip]

FROM logilab/cubicweb
COPY --from=temp dist/asset-*.tar.gz .
[snip]
ENTRYPOINT ["/entrypoint.sh"]
CMD ["start"]

Still had the problem. So commented out some parts (the temp stage) and it failed, so I found :
version: v1beta9
images:
  app:
    image: registry.logilab.fr/francearchives/cubicweb-francearchives
    preferSyncOverRebuild: true
    injectRestartHelper: true
    appendDockerfileInstructions:
    - USER root
    build:
      docker:
        options:
          target: temp

After removing the build section which targets temp, it works. Is this multistage incorrectly detected by the devspace init stage ?
What did you expect to happen instead?
How can we reproduce the bug? (as minimally and precisely as possible)
See above extracts of the Dockerfile multistage to use.
Local Environment:

DevSpace Version: 1.5.5
Operating System:  linux
Deployment method: n/a

Kubernetes Cluster:

Cloud Provider: n/a
Kubernetes Version: n/a

Anything else we need to know?

/kind bug

@arthurlogilab thanks for reporting this issue! The error message refers to an ENTRYPOINT or CMD within the build stage temp, you have defined it in the next build stage which does not affect temp anymore. So this would work:
FROM python:3.7-alpine AS temp
[snip]

ENTRYPOINT ["/entrypoint.sh"]
CMD ["start"]
FROM logilab/cubicweb
COPY --from=temp dist/asset-*.tar.gz .
[snip]

Hi @FabianKramm thanks for a prompt response.
I'm interested in having the 'restart helper' in the main part of my docker instance, not the temp part which is only used at build time. My point is that the devspace init points to temp when it should not.

@arthurlogilab I see, we probably should filter the targets that have no ENTRYPOINT or CMD during the devspace init process to avoid such errors in the first place.

From the little I understand of devspace as a new user, it would seem a good solution yest.

@arthurlogilab this should now be fixed with v5.6.1


wrong result from forward_test

I get a wrong result by forward_test.
The result will be correct when I reverse the y coordinate

Hi! Please share more details with us, like which model you are running or if it is the notebook demo that you are testing. And also you might want to post the "wrong" and "corrected" results here so that we can know what's going on. Thanks!


email are going in spam

hi my email are going in spam on gmail or yahoo.
http://prntscr.com/pj215x
http://prntscr.com/pj21rt

What is your SPF record?

v=spf1 a mx include:spf.mail.webexpertsonline.co ~all

Your screenshots tell you how you can improve however if that isn't sufficient, there isn't a lot you can do.


Wrong search result match

I think the AC rate should not be matched.

@taoweicn
One solution is to move AC Rate from the details to description. As below:

But I still prefer the original UI layout.

Hey @taoweicn ,
I'm sorry that I'll close this issue since we do not get feedback from other users about the UI and it's currently a limitation about the VS Code API.
But still, thank you for your engagement.


Proposition (and solution): COMPRESION Technique idea

Hi,
You JSFuck compiler is very interesting however it has some drawback - it produce very large code from small code JS :( . So I have following idea:

Lets Compress our STRING with CODE by switch it to base4 (not 64!) characters, however instead using character 0,1,2,3 we change '3' to letter 'a' becouse in brainfuck letter 'a' is shorter than '3' representation:

var input = "alert('Hello world' + \x22 in 2018! :) \\uC548\\uB155\\uD558\\uC138\\uC694 \x22)"; // our input program as STRING (we can only use code which use ASCII character - for utf8 characters we need to use escape characters as in this example)

// code string
var encode = function(input) {
    let output = ""
    input.split('').map(function(letter) {
    let c =letter.charCodeAt(0).toString(4).split('3').join('a');
    if(c.length==3) c="0"+c;
    if(c.length==2) c="00"+c;
    if(c.length==1) c="000"+c;
    if(c.length==0) c="0000";
    output = output + '' + c;
})
return output;
};

var code = encode(input);

Ok so in variable 'code' we get following value (remeber number '3' in our base4 we change to letter 'a'):
120112a012111a021a100220021a1020121112a012a012aa02001a1a12aa1a0212a01210021a0200022a020002020200122112a202000a020a000a010a20020102000a220221020011a01a11100a0a110a100a2011a01a1110020a010a110a1111a01a1110100a110a110a2011a01a11100a0a010a0a0a2011a01a11100a0a120a210a10020002020221

Then we put this string in our decoding/eval procedure:

var b='',c = "120112a012111a021a100220021a1020121112a012a012aa02001a1a12aa1a0212a01210021a0200022a020002020200122112a202000a020a000a010a20020102000a220221020011a01a11100a0a110a100a2011a01a1110020a010a110a1111a01a1110100a110a110a2011a01a11100a0a010a0a0a2011a01a11100a0a120a210a10020002020221";c.split('').map(function(d,i){if(i%4==3) {b=b+String.fromCharCode(parseInt(c.slice(i-3,i+1).split('a').join('3'),4));}});eval(b);
and thats all - we can put this code to our JSFuck compiler and it works (produce 150885 chars) :)

Tests

a) let say our js ode is  alert(1)  then clear JSFack produces 1227 chars and after our 'compresion' we get 148563 chars (~150KB - this is approximation of size of our compresion 'library')
b) if we add lets say 50 characters alert('1abcdefgh iklmnoupr stuvwyzx12 abcdefghi klmnouprs') then pure JSFack result increases to 39465 chars - so 39465-1227=38238bytes ~39KB growth compare to case a). If we use compression we get 150635 chars so<PHONE_NUMBER>63=2072bytes ~2KB growth compare to case a). So as we see our output code increase more thant 10 times ( !!!!!!!! ) without compression (excluding 'compress library size').

When I try to compile larger compresed code i get following error (index):162 Uncaught RangeError: Maximum call stack size exceeded  at HTMLAnchorElement.$.onclick... - however I think If you build in this technique directly to compiler it will be easy to avoid this error.

The point isn't to produce a very small code base. It's to show lack of variation in generation. Literally,

It uses only six different characters to write and execute code.

The second you use an encoding decode eval procedure, you require more than six characters. That's demonstrating a different type of fuckery, but it's not clear that it's a step up. I think more fuckery without encode/decode is a good idea. I think we're deluting the fuckery barking up this tree.

My proposition is to add above middlestep-compression to BF compiler as option (and publish it on jsfuck.com) - people can use it to produce 3x smaller code

Because this project have more theoretical character
this task is done in/as separate project: small-jsfuck


ocamlPackages.lablgtk3: 3.1.1 → 3.1.2

Motivation for this change
Fixes & improvements: https://github.com/garrigue/lablgtk/releases/tag/3.1.2
Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@vbgl The use of the GitHub archive instead of a dune-release tarball like previously has broken the version detection. See https://github.com/coq-community/coq-nix-toolbox/pull/92#issuecomment-1017421131.
@garrigue Is this a mistake that there is no dune-release tarball in the assets for this new release?

I did the release by hand rather than using dune-release, but this was probably a bad idea in the end.
The opam package was fixed to allow version detection, without a new release. Do you access the release without opam?

Yes, this is about the Nix package. I guess we can adapt the fix from the opam package.


Corrected name of email environment variable

Corrected the name of the environment variable containing the list of email recipients. Emails were not being sent successfully.

a473b48


The context menu for the directory background is actually the context menu for the directory

Description
When you press right mouse button on the  directory background,what really shows is the context menu which should be shown when you press right mouse button on a directory
Steps To Reproduce
Press right mouse button on a directory background
Requirements

e.g. Fix crash that occurs when...

Files Version
<IP_ADDRESS>
Windows Version
Windows 11 23H2
Log File
debug.log

Thanks for the report, What do you expect to happen? Right clicking the background area is operations for the current folder you are in.

The context menu for the directory background is displayed based on "HKEY_CLASSES_ROOT\Directory\Background\shell".
The context menu for the directory is displayed based on "HKEY_CLASSES_ROOT\Directory\shell".
This is not a big deal, but it is indeed a problem.

I'm not sure I understand the issue, can you send a screenshot of what's displayed on your side?

First,I created an element in HKEY_CLASSES_ROOT\Directory\Background\shell,it should be shown in the background context menu

But it didn't

Then I create an element in HKEY_CLASSES_ROOT\Directory\shell

The element was shown in the context menu.It should't happend.

I have the exact same issue
Plz fix it asap:

If you right-click on the empty space in a folder, the "background menu" should appear but in fact, the folder menu is shown. This is different from the behaviour of Windows Explorer.
The background menu uses HKEY_CLASSES_ROOT\Directory\Background\shell instead of HKEY_CLASSES_ROOT\Directory\shell.

I'm not sure I understand the issue, can you send a screenshot of what's displayed on your side?


Remove unnecessary 'unsigned' literals.

Probably because I am lazy, I started using unsigned literals when
comparing to an unsigned. This is not needed, warnings are produced when
comparing signed vs. unsigned variables, but the literals are promoted
to the larger (unsigned) type.
This fixes #2742.

This change is

I really didn't intend for you to go change these. I was just wondering if there was a warning somewhere about these comparisons. But anyway, I hope it wasn't too much of a hassle. Thanks.

It was not a hassle at all. And (good news!) we had no such warning enabled.


Is it possible to customize the new user creation?

Hi, when a person login for the first time with Facebook it creates a new user and sets the email as username, but when the user's Facebook account is with phone number, it sets the name instead, is it possible to customize this so I can set the phone number in this case instead of the name?

You'll need to have a look into the facebook backend in python social auth repo


Improve workflow for when the API key cannot be found by the script: …

…Ask the user for the key, and tell them how to obtain one

Oh oh, I think we did the same thing twice ... Have a look at feat/store_api_key

It's not the same feature, I saw that branch. This code works with the store_api_key feature as well.
But it's quite similar - you can remove the user-entering-the-key part from this PR if you want :)

OK, you are right. I'll merge it :-)


The loss does not decrease during training a flow model

Hi,
I tried to train a optical flow model, follow this command:
bash scripts/train_tsn.sh ucf101 flow

But the loss does not decrease during training TSN. Any suggestions? By the way the rgb model is OK!
I0905 10:36:53.966650 24339 solver.cpp:240] Iteration 20, loss = 4.61511
I0905 10:36:53.966797 24339 solver.cpp:255]     Train net output #0: loss = 4.615 (* 1 = 4.615 loss)
I0905 10:36:53.966809 24339 solver.cpp:631] Iteration 20, lr = 0.005
I0905 10:37:39.902165 24339 solver.cpp:240] Iteration 40, loss = 4.61494
I0905 10:37:39.902279 24339 solver.cpp:255]     Train net output #0: loss = 4.61514 (* 1 = 4.61514 loss)
I0905 10:37:39.902290 24339 solver.cpp:631] Iteration 40, lr = 0.005
I0905 10:38:25.729789 24339 solver.cpp:240] Iteration 60, loss = 4.61493
I0905 10:38:25.729914 24339 solver.cpp:255]     Train net output #0: loss = 4.6159 (* 1 = 4.6159 loss)
I0905 10:38:25.729926 24339 solver.cpp:631] Iteration 60, lr = 0.005

I0905 22:13:58.890894 24339 solver.cpp:240] Iteration 19820, loss = 4.61208
I0905 22:13:58.891036 24339 solver.cpp:255]     Train net output #0: loss = 4.62788 (* 1 = 4.62788 loss)
I0905 22:13:58.891048 24339 solver.cpp:631] Iteration 19820, lr = 5e-05
I0905 22:14:39.989903 24339 solver.cpp:240] Iteration 19840, loss = 4.60292
I0905 22:14:39.990012 24339 solver.cpp:255]     Train net output #0: loss = 4.65203 (* 1 = 4.65203 loss)
I0905 22:14:39.990025 24339 solver.cpp:631] Iteration 19840, lr = 5e-05
I0905 22:15:21.071648 24339 solver.cpp:240] Iteration 19860, loss = 4.59892
I0905 22:15:21.071779 24339 solver.cpp:255]     Train net output #0: loss = 4.63011 (* 1 = 4.63011 loss)
I0905 22:15:21.071791 24339 solver.cpp:631] Iteration 19860, lr = 5e-05

Should I modify the solver file (tsn_bn_inception_flow_solver.prototxt)? change the learning rate?
Thanks!

Please see #7 also

Thanks!


Removed PYC files

In the previous PR, I forgot to remove PYC files. This PR removes them.

Merged!


Document the full installation process

This task should follow the points below:

Try to go through the installation process of fresh copy of Basic RUM and document all the steps in INSTALL.MD file.
Run the command basicrum:beacon:init-folders and provide more verbose info if some of the folders are already created.

Thanks @korzol
Merged your changes! Closing the issue!


Add a licence

Please add a licence to this. I would fork this if the were a licence. For this Project I would use the GPL 2.0.

Done

Nice