Loadmance Plugin

Repository URL
https://github.com/virgosol/loadmance-plugin
New Repository Name
loadmance-plugin
Description
We would like to publish the plugin I wrote for our Loadmance product.
GitHub users to have commit permission
@aktoluna
Jenkins project users to have release permission
aktoluna
Issue tracker
GitHub issues

Security audit, information and commands
The security team is auditing all the hosting requests, to ensure a better security by default.
This message informs you that a Jenkins Security Scan was triggered on your repository.
It takes ~10 minutes to complete.
Commands
The bot will parse all comments, and it will check if any line start with a command.
Security team only:

/audit-ok => the audit is complete, the hosting can continue :tada:.
/audit-skip => the audit is not necessary, the hosting can continue :tada:.
/audit-findings => the audit reveals some issues that require corrections :pencil2:.

Anyone:

/request-security-scan => the findings from the [Jenkins Security Scan](https://www.jenkins.io/doc/developer/security/scan/) were corrected, this command will re-scan your repository :mag:.
/audit-review => the findings from the audit were corrected, this command will ping the security team to review the findings :eyes:.
	It's only applicable when the previous audit required changes.

Only one command can be requested per comment.

(automatically generated message, version: 1.17.22)

The Jenkins Security Scan discovered 14 finding(s) :mag:.
For each of them, either apply the recommended correction, suppress the warning or provide a justification.
Once you're done, either re-run the scan with /request-security-scan or request the Security team to review your justifications with /audit-review.

Remoting: Unsafe Callable
You can find detailed information about this finding here.
LoadmanceBuild.java#80
Potentially unsafe Callable implementation LoadmanceBuild#checkRoles

Jenkins: Missing permission check on a form fill web method with credentials lookup
You can find detailed information about this finding here.
LoadmanceBuilder.java#189
doFillTestIdItems should perform a permission check before calling #lookupCredentials

LoadmanceBuilder.java#161
doFillProjectIdItems should perform a permission check before calling #lookupCredentials

LoadmanceBuilder.java#146
doFillCredentialsIdItems should perform a permission check before calling #lookupCredentials

Stapler: Missing POST/RequirePOST annotation
You can find detailed information about this finding here.
LoadmanceBuilder.java#189
Potential CSRF vulnerability: If DescriptorImpl#doFillTestIdItems connects to user-specified URLs, modifies state, or is expensive to run, it should be annotated with @POST or @RequirePOST

LoadmanceBuilder.java#161
Potential CSRF vulnerability: If DescriptorImpl#doFillProjectIdItems connects to user-specified URLs, modifies state, or is expensive to run, it should be annotated with @POST or @RequirePOST

LoadmanceBuilder.java#146
Potential CSRF vulnerability: If DescriptorImpl#doFillCredentialsIdItems connects to user-specified URLs, modifies state, or is expensive to run, it should be annotated with @POST or @RequirePOST

LoadmanceCredentials.java#50
Potential CSRF vulnerability: If DescriptorImpl#doTestConnection connects to user-specified URLs, modifies state, or is expensive to run, it should be annotated with @POST or @RequirePOST

Stapler: Missing permission check
You can find detailed information about this finding here.
LoadmanceBuilder.java#189
Potential missing permission check in DescriptorImpl#doFillTestIdItems

LoadmanceBuilder.java#161
Potential missing permission check in DescriptorImpl#doFillProjectIdItems

LoadmanceBuilder.java#146
Potential missing permission check in DescriptorImpl#doFillCredentialsIdItems

LoadmanceCredentials.java#50
Potential missing permission check in DescriptorImpl#doTestConnection

Jenkins: Plaintext password storage
You can find detailed information about this finding here.
AuthRequestDto.java#5
Field should be reviewed whether it stores a password and is serialized to disk: password

LoginResponseDto.java#5
Field should be reviewed whether it stores a password and is serialized to disk: token

/hosting re-check

/hosting re-check

Hey @aktoluna,
I took a look over your hosting request and have some feedback for you:

https://github.com/virgosol/loadmance-plugin/blob/main/.github/CODEOWNERS should point to your artifact Id
https://github.com/virgosol/loadmance-plugin/blob/9411149fadf1435baae464871ec071b83afb0eac/.github/release-drafter.yml#L2 same point like above
https://github.com/virgosol/loadmance-plugin/blob/9411149fadf1435baae464871ec071b83afb0eac/.mvn/extensions.xml#L5 should be 1.6
https://github.com/virgosol/loadmance-plugin/blob/main/src/main/resources/index.jelly Please fill in a short description what this plugin is about.
https://github.com/virgosol/loadmance-plugin/blob/9411149fadf1435baae464871ec071b83afb0eac/pom.xml#L46-L49 is obsolete and should be removed.
https://github.com/virgosol/loadmance-plugin/blob/9411149fadf1435baae464871ec071b83afb0eac/pom.xml#L71-L99 Remove all dependencies your plugin doesn't depend on
https://github.com/virgosol/loadmance-plugin/blob/9411149fadf1435baae464871ec071b83afb0eac/pom.xml#L100-L104 instead of shading jackson yourself, you can depend on the corresponding Jenkins plugin shipping it: https://plugins.jenkins.io/jackson2-api/dependencies/
https://github.com/virgosol/loadmance-plugin/blob/9411149fadf1435baae464871ec071b83afb0eac/pom.xml#L105-L109 appears to be obsolete and should be removed
https://github.com/virgosol/loadmance-plugin/blob/main/README.md Provide some information what this plugin is about, how it works and how you set it up.
Make sure to address the errors highlighted when building the plugin: mvn clean verify package.

https://github.com/virgosol/loadmance-plugin/blob/9411149fadf1435baae464871ec071b83afb0eac/src/main/java/io/jenkins/plugins/loadmance/LoadmanceCredentials.java#L16 This class seems to be a re-implementation of https://github.com/jenkinsci/credentials-plugin/blob/master/src/main/java/com/cloudbees/plugins/credentials/impl/UsernamePasswordCredentialsImpl.java
So why not simply use https://github.com/jenkinsci/credentials-plugin/blob/master/src/main/java/com/cloudbees/plugins/credentials/common/StandardUsernamePasswordCredentials.java
You implement a Builder, that means it can't be used in pipelines. It should be easy to use SimpleBuildStep instead
https://github.com/virgosol/loadmance-plugin/blob/main/src/main/resources/app.properties should probably be moved into package io.jenkins.plugins.loadmance to avoid conflicts with other plugins in case they also have the idea to create file app.properties

/hosting re-check

https://github.com/virgosol/loadmance-plugin/blob/7311067d233b7ce79f9562242a5031b3567575c0/src/main/java/io/jenkins/plugins/loadmance/LoadmanceBuilder.java#L77 this should override perform(Run, ...) otherwise you're still not able to use it in a pipeline (pipelines do not inherit from AbstractBuild or Build)
https://github.com/virgosol/loadmance-plugin/blob/7311067d233b7ce79f9562242a5031b3567575c0/src/main/java/io/jenkins/plugins/loadmance/LoadmanceBuilder.java#L139 give your extension a meaningful name with @Symbol("loadmance")
Then you can use it in a pipeline by just referring to loadmance credentialsId: mycredId, projectId: myprjId, testId: mytstId

https://github.com/virgosol/loadmance-plugin/blob/7311067d233b7ce79f9562242a5031b3567575c0/pom.xml#L53 the artifactid of the bom is out of sync with the Jenkins version should be bom-2.387.x
https://github.com/virgosol/loadmance-plugin/blob/7311067d233b7ce79f9562242a5031b3567575c0/pom.xml#L54 the version of the bom is outdated

/hosting host

looks good I would say.
Try out if it works in a pipeline

Ok, thank you:) I will try

/hosting re-check

/hosting host

/hosting re-check

/request-security-scan

/hosting re-check

The Jenkins Security Scan discovered 6 finding(s) :mag:.
For each of them, either apply the recommended correction, suppress the warning or provide a justification.
Once you're done, either re-run the scan with /request-security-scan or request the Security team to review your justifications with /audit-review.

Jenkins: Missing permission check on a form fill web method with credentials lookup
You can find detailed information about this finding here.
LoadmanceBuilder.java#219
doFillTestIdItems should perform a permission check before calling #lookupCredentials

LoadmanceBuilder.java#183
doFillProjectIdItems should perform a permission check before calling #lookupCredentials

LoadmanceBuilder.java#164
doFillCredentialsIdItems should perform a permission check before calling #lookupCredentials

Stapler: Missing permission check
You can find detailed information about this finding here.
LoadmanceBuilder.java#219
Potential missing permission check in DescriptorImpl#doFillTestIdItems

LoadmanceBuilder.java#183
Potential missing permission check in DescriptorImpl#doFillProjectIdItems

LoadmanceBuilder.java#164
Potential missing permission check in DescriptorImpl#doFillCredentialsIdItems

/request-security-scan

The Jenkins Security Scan did not find anything dangerous with your plugin, congratulations! :tada:

:bulb: The Security team recommends that you are setting up the scan in your repository by following our guide.

/hosting host

Thanks for addressing the feedback @aktoluna, and thanks @mawinter69 for taking another look. Do you want to take another look?

Thank you @NotMyFault . Everything seems appropriate for me.

the bom version is a bit old but other than that it looks good

the bom version is a bit old but other than that it looks good

Dependabot will pick that up, now worries.

/hosting host


ungoogled-chromium: 113.0.5672.64 -> 113.0.5672.93

Description of changes

Things done

Built on platform(s)

[ ] 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

[ ] 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/)
23.05 Release Notes (or backporting 22.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

[ ] Fits CONTRIBUTING.md.

Hey, I've noticed that you've packaged a Windows only Chromium version. We (ungoogled-chromium) tag a patchset release for every stable version of upstream Chromium, including ones that are Windows only. It would be good if nixpkgs could stick to only package Linux releases (the update script should already take care of this)


Add type="button" to buttons to prevent submit

Otherwise, it breaks usage within <form> elements due to automatically triggering the form submit.

Thank you

Sure thing! Thanks for this amazing library. :D


Allow to unset optional values like vote-threshold, or add command like disable-approval that unsets/cleans up multiple things

At this point calling /enable again is the only way to do it.


WIP : feat(webhook) listen to Slack webhooks

WIP

I am going to close here for now due to the lack of activity. Please let us know when you have more information and we can consider to reopen.


initial commit of footer styling

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

[ ] Feature
[ ] Refactor
[ ] Bug Fix
[ ] Optimization
[ ] Documentation Update
[ ] Other (please specify here: )

Description of what this Pull Request does
(type your description here)
Related Tickets & Documents

Closes # (add the ticket number here, like #1)
Related Issues: (enter ticket numbers here)

QA Instructions, Screenshots, Recordings
(In this section, describe how to QA/review your PR. Feel free to use screenshots and/or short videos)
Added/updated tests?

[ ] Yes
[ ] Not Yet, and here is why: explain here
[ ] I need help with tests
[ ] No, and here is why: explain here

Looks good @Domicaren1 ! For now, take out the tailwind config color 'blue', we're waiting for my PR to be pushed with the correct color hex codes.


Show warning banner if rpc endpoint not synced

Fixes #498

Codecov Report

Merging #503 into master will decrease coverage by 0.14%.
The diff coverage is 3.03%.

@@            Coverage Diff             @@
##           master     #503      +/-   ##
==========================================
- Coverage   19.11%   18.97%   -0.15%
==========================================
  Files         200      201       +1
  Lines        3097     3099       +2
  Branches      522      526       +4
==========================================
- Hits          592      588       -4
- Misses       2114     2117       +3
- Partials      391      394       +3

Impacted Files
Coverage Δ

src/components/tx/TxHistory/history.js
0% <ø> (ø)
:arrow_up:

src/elements/Form/form.js
40% <ø> (ø)
:arrow_up:

src/components/layout/Main/main.js
0% <ø> (ø)
:arrow_up:

src/components/tx/CreateTx/createTxForm.js
75.86% <ø> (ø)
:arrow_up:

src/components/layout/Dashboard/dashboard.js
0% <ø> (ø)
:arrow_up:

...AccountPropertiesDialog/accountPropertiesDialog.js
0% <0%> (ø)
:arrow_up:

src/components/welcome/initialSetup.js
0% <0%> (ø)
:arrow_up:

src/containers/SyncWarning/SyncWarning.js
0% <0%> (ø)

...omponents/welcome/NodeTypeChoice/nodeTypeChoice.js
0% <0%> (ø)
:arrow_up:

src/components/layout/Footer/footer.js
0% <0%> (ø)
:arrow_up:

... and 10 more

Continue to review full report at Codecov.

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


Add support for Linux

A custom binary could be created, similar to iCloud Passwords for Windows, which would register a Native messaging host for Firefox and exchange with the iCloud Keychain API.
This would allow to use the extension on Linux.

@topiga Sure, any progress would be greatly appreciated!
I guess the authentication part will be fairly similar to what has already been documented on the Hack Different and pypush Discord servers, which I see you're already a part of.
The iCloud Keychain API itself could then be reverse engineered from the iCloud for Windows app, I suppose.

Yep, I'll keep you updated on discord if I find anything new. We could also meet in the future if we want to develop an app together, since we are in the same city.

Isn’t it theoretically possible to run iCloud for Windows through Wine or Wine-wrappers like Bottles? You wouldn’t need to reverse engineer the API then.

I guess the authentication part will be fairly similar to what has already been documented on the Hack Different and pypush Discord servers, which I see you're already a part of.

Is this available somewhere else, too? From experience, discord isn’t the best place to look for documentation.

This discord is. Also, I tried running iCloud on wine, but the version with passwords is only available through the Microsoft store, and I don’t know how/don’t want to do that.Le 7 avr. 2024 à 11:47, Jan Fooken @.***> a écrit :
Isn’t it theoretically possible to run iCloud for Windows through Wine or Wine-wrappers like Bottles? You wouldn’t need to reverse engineer the API then.
I guess the authentication part will be fairly similar to what has already been documented on the Hack Different and pypush Discord servers, which I see you're already a part of.
Is this available somewhere else, too? From experience, discord isn’t the best place to look for documentation.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Has any progress been made on this? If not i'd like to pick it up because I would find this very useful


Document How to Turn Off SSL Verification

Additional context in https://github.com/ianunruh/hvac/pull/139

It would also be helpful to document how the verify flag can be used to verify self-signed certificates: verify='/path/to/cert.cer'. If you are using a self-signed certificate, this is preferable to disabling certificate verification.

@Brcrwilliams: That should already be covered by the existing docs I believe. If not, please clarify what is lacking and I can get that added in as well.


CP will not recover files properly

Current Behavior
Background:
All software is up to date, and I recently reinstalled the application, but the issue persists despite multiple reinstall attempts. Running on a QNAP within container station. It worked great before, a few years back .
Problem
CrashPlan fails to recover files properly. It either gets stuck on "preparing" and then completes without downloading anything, or it downloads only a partial set of files (e.g., 283MB out of 500GB). In some cases, it downloads incorrect data—hundreds of folders with unfamiliar names (see picture)
Expected Behavior
I should be able to select folders from CrashPlan Cloud, specify a destination folder, and have the files correctly recovered to that location.
Steps to Reproduce:
CrashPlan is running in a container within my QNAP TS-677 NAS, using the following setup code:
docker run --restart always -d \
Transfer CrashPlan to the new installation.
Allow CrashPlan to fully sync.
Choose "Recover" and input my custom encryption key.
Select the files to recover and specify the destination using "Save selected files to" -> "Other" -> custom storage location.
Choose "Overwrite" if the file already exists.
Set "Original" for file permissions and click "Go."
Steps To Reproduce
Background: my crash plan installation is running I am running this on container station within my ts-677 qnap NAS. All software is the latest version, in fact few weeks ago I reinstalled, set it up. I have tried to reinstall the application several times with no luck. I don't understand it worked fine in the past
1Transfer CrashPlan to the new installation.
Allow CrashPlan to fully sync.
Choose "Recover" and input my custom encryption key.
Select the files to recover and specify the destination using "Save selected files to" -> "Other" -> custom storage location.
Choose "Overwrite" if the file already exists.
Set "Original" for file permissions and click "Go."
Environment
Docker version
Container creation
docker run --restart always -d
--name=CrashplanPro
-e USER_ID=0
-e GROUP_ID=0
-p 5800:5800
-p 5900:5900
-e TZ=America/New_York
-e CRASHPLAN_SRV_MAX_MEM=5120m
-e CRASHPLAN_SERVER_ADDRESS=SMB
-v /share/CACHEDEV3_DATA/Virtualize/Containers/appdata/crashplan-pro/config:/config:rw
-v /share/CACHEDEV7_DATA:/storage:rw
-v /share/CE_CACHEDEV5_DATA/Boy-09/CP_Archive.01.2014-11.2021:/storage/CP_Archive/01.2014-11.2021:rw
-v /share/CE_CACHEDEV5_DATA/Boy-09/CP_Archive.01.2014-10.2021:/storage/CP_Archive/01.2014-10.2021:rw
-v /share/CACHEDEV6_DATA/Container:/storage/Containers:rw
-v /share/CE_CACHEDEV5_DATA/Boy-09/CP_Archive.12.2021:/storage/CP_Archive/12.2021:rw
jlesage/crashplan-pro

Container log
See picture

Container inspect
No response
Anything else?
No response

Can you have a look at /config/log/service.log.0 to see if there is anything obvious ?

I'm also having a similar issue with restoring, but mine involves trying to restore files to a SMB share volume that's mapped into the container.  The container has full write access to the share and in-fact, the CrashPlan app is storing its configurations and working directory structure also on a SMB share.  However for some reason when I try to restore, the CrashPlan app fails in the logs with a permission denied error even though the permissions are definitely set up to be able to read and write.

Hi jlesage,
First thank you so much for creating this container, it has worked like clockwork, and saved me many many times.
Sorry for the delay, I have been trying different things. It appears to work a bit better when I choose to restore the the original location rather than choosing a spot. I see that it does download the correct files rather than hundreds of folders with unfamiliar names. It doesn't always download 100% of the files, but it is getting about 80% at times.
I have located the file you suggested, and I am not really sure what to look for. I searched for an error and did not see any. I would be happy to post the log file if you can confirm that it is safe to do so (i.e. doesn't have my IP address).
Thanks again and thank you for your prompt response.


Question about VideoInstruct_Dataset.json

I found many words like "\nQA_GT_caption_based_noisy" in json file, what's this? Is it just some noisy text that haven't been cleaned out?

"q": "Can you briefly describe the content of the video for me?",
"a": "Of course! The video features various shots of a city followed by a girl playing the violin. Another girl steps in and starts singing, which leads to several others joining in as well. A mime walks in with fireworks while the group still sings, and many around are seen laughing and smiling. Overall, the video features individuals playing the violin in different scenes and locations, making it quite enjoyable to watch.\nQA_GT_caption_based_noisy",
"video_id": "v_GqWH2IYPw6U"

Hi @DarkLighter97,
This is the unfiltered noise from GPT-3.5 and can be cleaned out. Thanks


Logger compatibility with data streams

Elasticsearch.Extensions.Logging:
It seems to me, that unfortunately the Elasticsearch logger for .NET is not compatible with data streams.
Data streams require 'create' actions instead of 'index' to be used for bulk requests.
The ElasticsearchChannel class is currently determining the bulk action to be 'index' always, found in the method WriteBufferToStreamAsync:
private async Task WriteBufferToStreamAsync(List<TEvent> b, Stream stream, CancellationToken ctx)
{
	foreach (var @event in b)
	{
		if (@event == null) continue;
		var indexTime = Options.TimestampLookup?.Invoke(@event) ?? DateTimeOffset.Now;
		if (_options.IndexOffset.HasValue) indexTime = indexTime.ToOffset(_options.IndexOffset.Value);
		var index = string.Format(_options.Index, indexTime);

                // START PROBLEM
		var indexHeader = new { index = new { _index = index } };
                // END PROBLEM

		await JsonSerializer.SerializeAsync(stream, indexHeader, indexHeader.GetType(), ElasticsearchChannelStatics.SerializerOptions, ctx)
			.ConfigureAwait(false);
		await stream.WriteAsync(ElasticsearchChannelStatics.LineFeed, 0, 1, ctx).ConfigureAwait(false);
		if (Options.WriteEvent != null)
			await Options.WriteEvent(stream, ctx, @event).ConfigureAwait(false);
		else
		{
			await JsonSerializer.SerializeAsync(stream, @event, typeof(TEvent), ElasticsearchChannelStatics.SerializerOptions, ctx)
				.ConfigureAwait(false);
		}
		await stream.WriteAsync(ElasticsearchChannelStatics.LineFeed, 0, 1, ctx).ConfigureAwait(false);
	}
}

If my target index is a data stream, all log-event documents will be rejected by Elasticsearch.
It would make sense to have the desired operation type configurable for the logger.

For completeness, package version used was: 1.6.0-alpha1

Just discovered, that #110 addresses this issue by introducing different channel variations. Is there any realistic chance of this being realized in the near future? Tbh this seems like a huge deal breaker, since many will probably use data streams for log scenarios.

@morinow Thanks for raising this issue and apologies for the radio silence on our end.
#110 is now merged and we are gearing up to release an 8.4.0, this will include a rewritten Elasticsearch.Extensions.Logging that takes advantage of the new DataStreamChannel.
Closing this issue ahead of the release (Date still TBD).


Status of run_results.json nodes is not accurate.

Describe the bug
Status is not accurate on nodes of run_results.json. The dbt model's error state is not represented accurately in run_results.json.
Steps To Reproduce
Caveating that I was not able to reproduce this locally with 0.19.0 version of dbt. I am not sure what configuration leads to this scenario.
I've attached relevant artifacts below.

{
"status": "success",
"timing": [
{
"name": "compile",
"started_at": "2021-02-18 21:07:25.082433Z",
"completed_at": "2021-02-18 21:07:26.083771Z"
},
{
"name": "execute",
"started_at": "2021-02-18 21:07:26.085808Z",
"completed_at": "2021-02-18 21:07:26.085831Z"
}
],
"thread_id": "Thread-19",
"execution_time": 1.226057529449463,
"message": null,
"adapter_response": {},
"unique_id": "model.dbt_workspace.hard_deletes__augmented_snapshot_view"
}

Expected behavior
I would expect model value in run_results.json to match output printed in stdout. Seems like they are differing.
Screenshots and log output
Attached below
System information
Which database are you using dbt with?

[ ] postgres
[ ] redshift
[ ] bigquery
[x] snowflake
[ ] other (specify: ____________)

The output of dbt --version:
v0.19.0
The operating system you're using:
The output of python --version:
Additional context
Add any other context about the problem here.
-- target/run/hard_deletes__augmented_snapshot_view.sql
  create or replace  view ANALYTICS.dbt_cloud_pr_15782_12.hard_deletes__augmented_snapshot_view  as (
    with

    snapshot_with_distant_past_and_distant_future_raw as (
        select
            *,

            if(
                dbt_valid_from = min(dbt_valid_from) over (
            partition by id order by dbt_valid_from rows between unbounded preceding and unbounded following
        ),
                TIMESTAMP('1900-01-01 00:00:00+00'),
                dbt_valid_from
            ) as valid_from_with_distant_past,

            if(
                dbt_valid_to is null,
                TIMESTAMP('9999-12-31 23:59:59+00'),
                dbt_valid_to
            ) as valid_to_with_distant_future

        from ANALYTICS.dbt_cloud_pr_15782_12.hard_deletes__snapshot
    ),

    snapshot_with_distant_past_and_distant_future as (
        select
            "ID",
  "COLOR",
  "THE_ANSWER",
  "INSERT_TIME",
  "DBT_SCD_ID",
  "DBT_UPDATED_AT",
  "DBT_VALID_FROM",
  "DBT_VALID_TO",
            valid_from_with_distant_past,
            valid_to_with_distant_future

        from snapshot_with_distant_past_and_distant_future_raw
    ),

    snapshot_with_is_deleted as (
        select
            *,
            first_value(dbt_valid_to) over (
                partition by id order by dbt_valid_to asc rows between unbounded preceding and unbounded following
            ) is not null as is_deleted

        from snapshot_with_distant_past_and_distant_future
    ),

    snapshot_with_current_values as (
        select
            *,

            if(
                is_deleted or (dbt_valid_to is null),
                true,
                false
            ) as is_current

        from snapshot_with_is_deleted
    )

    select * from snapshot_with_current_values

  );

@nave91 just confirming, was this we dbt run or another command?

@kwigley This was with dbt run

@nave91 I checked into the full run_results.json from the associated dbt Cloud job (thanks for sharing with me!), and I confirmed based on the args dict that this was the run_results.json artifact produced by the job's final docs generate step, rather than the earlier run step with the error:
...
    "elapsed_time": 2.8335185050964355,
    "args": {
        "log_format": "default",
        "write_json": true,
        "profiles_dir": "/tmp/jobs/14862592/.dbt",
        "profile": "user",
        "target": "qa",
        "use_cache": true,
        "compile": true,
        "version_check": true,
        "which": "generate",
        "rpc_method": "docs.generate"
    }
...

This seems in line with the execute step taking 0.023 milliseconds, and the entire elapsed time being 2.8 seconds.
The issue here is that dbt overwrites artifacts, and the dbt Cloud run history page makes only the "last" version of each artifact available—though I understand that, behind the scenes, Cloud does a good job of saving the artifact from every run step. For jobs with "Generate docs?" checked, the final run step will always be docs generate, and it isn't skipped if a preceding step fails, so the run_results.json available for download will always reflect docs generate instead of the earlier failing step.
If we can locate the run_results.json artifact for the dbt run step of that job run, we should be able to confirm that model.dbt_workspace.hard_deletes__augmented_snapshot_view has "status": "error".

@jtcohen6 That makes sense to me! Thank you for looking into it.


[Documentation] No example available for Twitter Connector

For a new user who wants to send a Tweet using Ballerina, there's no example available in [1]. The only available information is the API docs [2], which is not much useful for a new user.
[1] https://ballerinalang.org/docs/by-example/
[2] https://ballerinalang.org/docs/api/0.8/org.wso2.ballerina.connectors.twitter.html

As per the current implementation sample will be added to the README file of each connector in the relevant connector repo itself.

Created https://github.com/ballerinalang/connector-twitter/issues/2 for track this


Unix timestamp bug!?!

Arduino board:  RTC PCF8523

Arduino IDE version (found in Arduino -> About Arduino menu):
Version: 2.1.0
Date: 2023-04-19T15:26:42.115Z
CLI Version: 0.32.2

Possible bug ->
Hey, since this is the first time im playing around with RTC modules please take it easy on me.

Now that's out of the way, i noticed something strange while setting up my RTC module, when i run the example code, as suggested in the docs, in order to set up the local time in my module i get back a perfect fine date and time to the second, but when i run the function to get back the Unix time i have an offset of +3 hours. For example, the time function says it is (21:51:37, in Greece) and almost to the second it is correct, but the Unix time(1685656619) does not represent the time that is printed out.
this is the code i used
`
#include "RTClib.h"
void setup() {
if (! rtc.begin()) {
Serial.println("Couldn't find RTC");
Serial.flush();
while (1) delay(10);
}
Serial.begin(57600);
rtc.adjust(DateTime(F(DATE), F(TIME)));
rtc.start();
}
void loop() {
DateTime now = rtc.now();
Serial.print(now.year(), DEC);
Serial.print('/');
Serial.print(now.month(), DEC);
Serial.print('/');
Serial.print(now.day(), DEC);
Serial.print(" (");
Serial.print(daysOfTheWeek[now.dayOfTheWeek()]);
Serial.print(") ");
Serial.print(now.hour(), DEC);
Serial.print(':');
Serial.print(now.minute(), DEC);
Serial.print(':');
Serial.print(now.second(), DEC);
Serial.println();
Serial.print(" since midnight 1/1/1970 = ");
Serial.println(now.unixtime());
}
`
But its gets stranger. When i moved to Sweden from Greece i noticed that the Unix time difference became 2 instead of 3 hours.
The question here is. Can that be a bug where the developers are calculating the time and then take into account the timezone and adding or decreasing some extra hours, for example in Greece 3 hours, or i missed something?

This is a known limitation of the library. From the documentation of the DateTime class:

The class has no notion of time zones, daylight saving time, or leap seconds: time is stored in whatever time zone the user chooses to use.

This means that the unixtime() method cannot account for your timezone, and thus does not return a proper Unix time. This is more clearly stated in the documentation of the constructor from “Unix time”:

This number is analogous to Unix time, with two small differences:

The Unix epoch is specified to be at 00:00:00 UTC, whereas this class has no notion of time zones. The epoch used in this class is then at 00:00:00 on whatever time zone the user chooses to use, ignoring changes in DST. [...]

You wrote:

Can that be a bug where the developers are calculating the time and then take into account the timezone

Quite the contrary. The issue is that the library fails to take into account the timezone, simply because it doesn't know it (and wouldn't want to handle the complexities of timezones anyway).

Oh thank youy, ngl i did not dive that deep to the doc's.


doc: fix typo

For an explanation of how to fill out the fields, please see the relevant section
in PULL_REQUESTS.md
Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes: docs/root/configuration/http/http_filters/router_filter.rst
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Deprecated:]
[Optional API Considerations:]

Thanks for the doc fix.


iOS : cannot forward GPS metadata

I started from SDK code in "samples/source/ModifyingXMP.cpp".
I just extract XMP metadata from my photo source and reinject it in my new photo.
Result is that my new photo has all metadata from my photo source except GPS metadata.
Problem only on iOS, no problem on Android.

Thanks for reporting it. Could you please share the test files with which you are facing the issue.

You can reproduce the issue with any photo with GPS metadata.

This issue is not reproducible.


latest code-insiders snap update crashes immediately on ubuntu 18.04 and 20.04

Related to: https://github.com/microsoft/vscode/issues/103060 (where reports say the snap is broken, but the apt install works)

VSCode Version: latest code-insiders
OS Version: ubuntu 20.04 and 18.04
snap list
Name                Version                     Rev   Tracking         Publisher     Notes
code                17299e41                    38    latest/stable    vscode✓       classic
code-insiders       8c426f9f                    485   latest/stable    vscode✓       classic

Steps to Reproduce:

code-insiders --verbose --disable-extensions .

Does this issue occur when all extensions are disabled?: Yes
code-insiders --verbose --disable-extensions .
/usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so: undefined symbol: g_date_time_format_iso8601
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
[39806:0722/110214.849277:ERROR:appcenter_api.cc(52)] expecting appcenter url prefix
[main 2020-07-22T17:02:14.906Z] Starting VS Code
[main 2020-07-22T17:02:14.907Z] from: /snap/code-insiders/484/usr/share/code-insiders/resources/app
[main 2020-07-22T17:02:14.907Z] args: {
  _: [ '/home/jonathan.morrison/IML/wiwh/wiwh-web' ],
  diff: false,
  add: false,
  goto: false,
  'new-window': false,
  'reuse-window': false,
  wait: false,
  help: false,
  'list-extensions': false,
  'show-versions': false,
  version: false,
  verbose: true,
  status: false,
  'prof-startup': false,
  'disable-extensions': false,
  'disable-gpu': false,
  telemetry: false,
  logExtensionHostCommunication: false,
  'skip-release-notes': false,
  'disable-restore-windows': false,
  'disable-telemetry': false,
  'disable-updates': false,
  'disable-crash-reporter': false,
  'crash-reporter-id': '0a86566f-2e15-4709-8740-8a4d00788a1e',
  'disable-user-env-probe': false,
  'skip-add-to-recently-opened': false,
  'unity-launch': false,
  'open-url': false,
  'file-write': false,
  'file-chmod': false,
  'driver-verbose': false,
  force: false,
  'do-not-sync': false,
  trace: false,
  'force-user-env': false,
  'open-devtools': false,
  'no-proxy-server': false,
  nolazy: false,
  'force-renderer-accessibility': false,
  'ignore-certificate-errors': false,
  'allow-insecure-localhost': false
}
[main 2020-07-22T17:02:14.908Z] Resolving machine identifier...
[main 2020-07-22T17:02:14.908Z] Resolved machine identifier: add1801b442928cb4a35c33217ada96563c3b8e69783e2f0970561dc4f97bad4
[main 2020-07-22T17:02:14.922Z] update#setState idle
[main 2020-07-22T17:02:14.927Z] [storage state.vscdb] open(/home/jonathan.morrison/.config/Code - Insiders/User/globalStorage/state.vscdb, retryOnBusy: true)
[main 2020-07-22T17:02:14.927Z] lifecycle (main): phase changed (value: 2)
[main 2020-07-22T17:02:14.928Z] windowsManager#open
[main 2020-07-22T17:02:14.929Z] window#validateWindowState: validating window state on 1 display(s) { mode: 1, x: 1922, y: 18, width: 1916, height: 2121 }
[main 2020-07-22T17:02:14.929Z] window#validateWindowState: 1 monitor working area { x: 0, y: 0, width: 3840, height: 2160 }
[main 2020-07-22T17:02:14.930Z] window#ctor: using window state { mode: 1, x: 1922, y: 18, width: 1916, height: 2121 }
[39810:0722/110214.946502:ERROR:appcenter_api.cc(52)] expecting appcenter url prefix
[main 2020-07-22T17:02:14.984Z] lifecycle (main): phase changed (value: 3)
[main 2020-07-22T17:02:14.985Z] telemetry/optInStatus { optIn: true }
[main 2020-07-22T17:02:14.985Z] telemetry/machineIdFallback { usingFallbackGuid: false }
[main 2020-07-22T17:02:15.000Z] [storage state.vscdb] Trace (event): PRAGMA user_version = 1;
[39824:0722/110215.003369:ERROR:appcenter_api.cc(52)] expecting appcenter url prefix
[main 2020-07-22T17:02:15.004Z] [storage state.vscdb] Trace (event): CREATE TABLE IF NOT EXISTS ItemTable (key TEXT UNIQUE ON CONFLICT REPLACE, value BLOB)
[main 2020-07-22T17:02:15.005Z] [storage state.vscdb] Trace (event): SELECT * FROM ItemTable
[main 2020-07-22T17:02:15.005Z] [storage state.vscdb] getItems(): 75 rows
[39806:0722/110215.051492:ERROR:gl_surface_glx.cc(90)] glXGetFBConfigs failed.
[39806:0722/110215.051575:ERROR:gl_surface_glx.cc(130)] Failed to get GLXConfig
[39806:0722/110215.051638:ERROR:gl_surface_glx.cc(479)] CreateDummyWindow(gfx::GetXDisplay()) failed
[39806:0722/110215.051697:ERROR:gl_initializer_x11.cc(148)] GLSurfaceGLX::InitializeOneOff failed.
[39806:0722/110215.053369:WARNING:x11_util.cc(1520)] X error received: serial 432, error_code 8 (BadMatch (invalid parameter attributes)), request_code 78, minor_code 0 (X_CreateColormap)
[39806:0722/110215.053438:ERROR:viz_main_impl.cc(152)] Exiting GPU process due to errors during initialization
[39844:0722/110215.055267:ERROR:appcenter_api.cc(52)] expecting appcenter url prefix
[main 2020-07-22T17:02:15.108Z] [storage state.vscdb] updateItems(): insert(Map(3) {storage.serviceMachineId => 57fc85a9-ffa6-4e13-9f99-3b31c9538a62, telemetry.lastSessionDate => Wed, 22 Jul 2020 17:00:35 GMT, telemetry.currentSessionDate => Wed, 22 Jul 2020 17:02:15 GMT}), delete(Set(0) {})
[main 2020-07-22T17:02:15.110Z] [storage state.vscdb] Trace (event): BEGIN TRANSACTION
[main 2020-07-22T17:02:15.111Z] [storage state.vscdb] Trace (event): INSERT INTO ItemTable VALUES ('storage.serviceMachineId','57fc85a9-ffa6-4e13-9f99-3b31c9538a62'),('telemetry.lastSessionDate','Wed, 22 Jul 2020 17:00:35 GMT'),('telemetry.currentSessionDate','Wed, 22 Jul 2020 17:02:15 GMT')
[main 2020-07-22T17:02:15.112Z] [storage state.vscdb] Trace (event): END TRANSACTION
/dev/fd/3: No such file or directory
Server response:
[39777:0722/110215.257343:WARNING:gpu_process_host.cc(1222)] The GPU process has crashed 1 time(s)
[39854:0722/110215.258643:ERROR:appcenter_api.cc(52)] expecting appcenter url prefix
[39777:0722/110215.269359:WARNING:gpu_process_host.cc(985)] Reinitialized the GPU process after a crash. The reported initialization time was 10 ms
/dev/fd/3: No such file or directory
Server response:
[39777:0722/110215.403908:WARNING:gpu_process_host.cc(1222)] The GPU process has crashed 2 time(s)
[39864:0722/110215.405166:ERROR:appcenter_api.cc(52)] expecting appcenter url prefix
[39777:0722/110215.416028:WARNING:gpu_process_host.cc(985)] Reinitialized the GPU process after a crash. The reported initialization time was 10 ms
/dev/fd/3: No such file or directory
Server response:
[39777:0722/110215.549557:WARNING:gpu_process_host.cc(1222)] The GPU process has crashed 3 time(s)
[39874:0722/110215.550822:ERROR:appcenter_api.cc(52)] expecting appcenter url prefix
[39777:0722/110215.553914:WARNING:gpu_process_host.cc(985)] Reinitialized the GPU process after a crash. The reported initialization time was 0 ms
[main 2020-07-22T17:02:15.559Z] getShellEnvironment: running on CLI, skipping
/dev/fd/3: No such file or directory
Server response:
[39777:0722/110215.699289:WARNING:gpu_process_host.cc(1222)] The GPU process has crashed 4 time(s)
[39890:0722/110215.700625:ERROR:appcenter_api.cc(52)] expecting appcenter url prefix
[39777:0722/110215.703733:WARNING:gpu_process_host.cc(985)] Reinitialized the GPU process after a crash. The reported initialization time was 0 ms
/dev/fd/3: No such file or directory
Server response:
[39777:0722/110215.847331:WARNING:gpu_process_host.cc(1222)] The GPU process has crashed 5 time(s)
[39907:0722/110215.848412:ERROR:appcenter_api.cc(52)] expecting appcenter url prefix
[39777:0722/110215.851799:WARNING:gpu_process_host.cc(985)] Reinitialized the GPU process after a crash. The reported initialization time was 0 ms
/dev/fd/3: No such file or directory
Server response:
(node:39824) Electron: Loading non-context-aware native module in renderer: '/snap/code-insiders/484/usr/share/code-insiders/resources/app/node_modules.asar.unpacked/node-pty/build/Release/pty.node'. This is deprecated, see https://github.com/electron/electron/issues/18397.
[39777:0722/110215.932690:INFO:CONSOLE(1669)] "%cTRACE color: #888 [storage state.vscdb] open(/home/jonathan.morrison/.config/Code - Insiders/User/workspaceStorage/d4b77e1ba3b3cd5958b15c1f62cdfd17/state.vscdb, retryOnBusy: true)", source: file:///snap/code-insiders/484/usr/share/code-insiders/resources/app/out/vs/workbench/workbench.desktop.main.js (1669)
(node:39824) Electron: Loading non-context-aware native module in renderer: '/snap/code-insiders/484/usr/share/code-insiders/resources/app/node_modules.asar.unpacked/vscode-sqlite3/build/Release/sqlite.node'.  Goodbye.
/dev/fd/3: No such file or directory
Server response:
/dev/fd/3: No such file or directory
Server response:

strace -e trace=openat,readlink ls -l /dev/fd/
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libselinux.so.1", O_RDONLY|O_CLOEXEC) = 3
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libpcre2-8.so.0", O_RDONLY|O_CLOEXEC) = 3
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libdl.so.2", O_RDONLY|O_CLOEXEC) = 3
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libpthread.so.0", O_RDONLY|O_CLOEXEC) = 3
openat(AT_FDCWD, "/proc/filesystems", O_RDONLY|O_CLOEXEC) = 3
openat(AT_FDCWD, "/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
openat(AT_FDCWD, "/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 3
openat(AT_FDCWD, "/usr/share/locale/en_US.UTF-8/LC_TIME/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en_US.utf8/LC_TIME/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en_US/LC_TIME/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en.UTF-8/LC_TIME/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en.utf8/LC_TIME/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en/LC_TIME/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/gconv/gconv-modules.cache", O_RDONLY) = 3
openat(AT_FDCWD, "/etc/nsswitch.conf", O_RDONLY|O_CLOEXEC) = 3
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libnss_files.so.2", O_RDONLY|O_CLOEXEC) = 3
openat(AT_FDCWD, "/etc/passwd", O_RDONLY|O_CLOEXEC) = 3
openat(AT_FDCWD, "/etc/group", O_RDONLY|O_CLOEXEC) = 3
openat(AT_FDCWD, "/dev/fd/", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = 3
readlink("/dev/fd/0", "/dev/pts/2", 65) = 10
readlink("/dev/fd/1", "/dev/pts/2", 65) = 10
readlink("/dev/fd/2", "/dev/pts/2", 65) = 10
readlink("/dev/fd/3", "/proc/40021/fd", 65) = 14
openat(AT_FDCWD, "/usr/share/locale/en_US.UTF-8/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en_US.utf8/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en_US/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en.UTF-8/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en.utf8/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale-langpack/en_US.UTF-8/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale-langpack/en_US.utf8/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale-langpack/en_US/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale-langpack/en.UTF-8/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale-langpack/en.utf8/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale-langpack/en/LC_MESSAGES/coreutils.mo", O_RDONLY) = 3
total 0
openat(AT_FDCWD, "/etc/localtime", O_RDONLY|O_CLOEXEC) = 3
lrwx------ 1 jonathan.morrison jonathan.morrison 64 Jul 22 11:04 0 -> /dev/pts/2
lrwx------ 1 jonathan.morrison jonathan.morrison 64 Jul 22 11:04 1 -> /dev/pts/2
lrwx------ 1 jonathan.morrison jonathan.morrison 64 Jul 22 11:04 2 -> /dev/pts/2
lr-x------ 1 jonathan.morrison jonathan.morrison 64 Jul 22 11:04 3 -> /proc/40021/fd
+++ exited with 0 +++

Now I have to look for a way to sync all my extensions and settings to VS-Code through a tedious way.

Can you paste the terminal output and the crash dump generated at /tmp/vscode-crash running the following
code-insiders --verbose --crash-reporter-directory /tmp/vscode-crash --disable-gpu

Hi, I have the same issue.
Ubuntu 20.04 LTS, 5.4.0-40-generic
I use the vscode insiders snap (https://snapcraft.io/code-insiders)
Verbose output:
code-insiders --verbose --crash-reporter-directory /tmp/vscode-crash --disable-gpu Found --crash-reporter-directory argument. Setting crashDumps directory to be '/tmp/vscode-crash' [3326:0723/084228.668822:ERROR:appcenter_api.cc(52)] expecting appcenter url prefix /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so: undefined symbol: g_date_time_format_iso8601 Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so [3352:0723/084229.072742:ERROR:appcenter_api.cc(52)] expecting appcenter url prefix pci id for fd 30: 8086:3e98, driver (null) [main 2020-07-23T06:42:29.215Z] Starting VS Code [main 2020-07-23T06:42:29.215Z] from: /snap/code-insiders/485/usr/share/code-insiders/resources/app [main 2020-07-23T06:42:29.215Z] args: {   _: [],   diff: false,   add: false,   goto: false,   'new-window': false,   'reuse-window': false,   wait: false,   help: false,   'list-extensions': false,   'show-versions': false,   version: false,   verbose: true,   status: false,   'prof-startup': false,   'disable-extensions': false,   'disable-gpu': true,   telemetry: false,   logExtensionHostCommunication: false,   'skip-release-notes': false,   'disable-restore-windows': false,   'disable-telemetry': false,   'disable-updates': false,   'disable-crash-reporter': false,   'crash-reporter-directory': '/tmp/vscode-crash',   'disable-user-env-probe': false,   'skip-add-to-recently-opened': false,   'unity-launch': false,   'open-url': false,   'file-write': false,   'file-chmod': false,   'driver-verbose': false,   force: false,   'do-not-sync': false,   trace: false,   'force-user-env': false,   'open-devtools': false,   'no-proxy-server': false,   nolazy: false,   'force-renderer-accessibility': false,   'ignore-certificate-errors': false,   'allow-insecure-localhost': false } [main 2020-07-23T06:42:29.216Z] Resolving machine identifier... [main 2020-07-23T06:42:29.216Z] Resolved machine identifier: f2c8babd63a89ecdc5dc1ee5d169ff76b72418527b08e1b83a52fc91d6642d7d [main 2020-07-23T06:42:29.256Z] update#setState idle [3367:0723/084229.266628:ERROR:appcenter_api.cc(52)] expecting appcenter url prefix [main 2020-07-23T06:42:29.337Z] [storage state.vscdb] open(/home/rienk/.config/Code - Insiders/User/globalStorage/state.vscdb, retryOnBusy: true) [main 2020-07-23T06:42:29.338Z] lifecycle (main): phase changed (value: 2) [main 2020-07-23T06:42:29.338Z] windowsManager#open [main 2020-07-23T06:42:29.340Z] window#validateWindowState: validating window state on 2 display(s) { mode: 0, x: 2185, y: 251, width: 1386, height: 752 } [main 2020-07-23T06:42:29.340Z] window#validateWindowState: multi-monitor working area { x: 1920, y: 27, width: 1920, height: 1053 } [main 2020-07-23T06:42:29.340Z] window#ctor: using window state { mode: 0, x: 2185, y: 251, width: 1386, height: 752 } [main 2020-07-23T06:42:29.500Z] lifecycle (main): phase changed (value: 3) [main 2020-07-23T06:42:29.502Z] telemetry/optInStatus { optIn: true } [main 2020-07-23T06:42:29.502Z] telemetry/machineIdFallback { usingFallbackGuid: false } [3379:0723/084229.520989:ERROR:appcenter_api.cc(52)] expecting appcenter url prefix [3326:0723/084229.617659:WARNING:gpu_process_host.cc(1222)] The GPU process has crashed 1 time(s) [main 2020-07-23T06:42:29.617Z] [storage state.vscdb] Trace (event): PRAGMA user_version = 1; [3386:0723/084229.618669:ERROR:appcenter_api.cc(52)] expecting appcenter url prefix pci id for fd 30: 8086:3e98, driver (null) [3326:0723/084229.631278:WARNING:gpu_process_host.cc(985)] Reinitialized the GPU process after a crash. The reported initialization time was 12 ms [main 2020-07-23T06:42:29.634Z] [storage state.vscdb] Trace (event): CREATE TABLE IF NOT EXISTS ItemTable (key TEXT UNIQUE ON CONFLICT REPLACE, value BLOB) [main 2020-07-23T06:42:29.635Z] [storage state.vscdb] getItems(): 85 rows [main 2020-07-23T06:42:29.635Z] [storage state.vscdb] Trace (event): SELECT * FROM ItemTable [3326:0723/084229.713713:WARNING:gpu_process_host.cc(1222)] The GPU process has crashed 2 time(s) [3394:0723/084229.714631:ERROR:appcenter_api.cc(52)] expecting appcenter url prefix pci id for fd 30: 8086:3e98, driver (null) [3326:0723/084229.725048:WARNING:gpu_process_host.cc(985)] Reinitialized the GPU process after a crash. The reported initialization time was 10 ms [main 2020-07-23T06:42:29.741Z] [storage state.vscdb] updateItems(): insert(Map(3) {storage.serviceMachineId => d8eb38c7-0dcf-48b6-9240-c40ea31edd39, telemetry.lastSessionDate => Thu, 23 Jul 2020 06:41:23 GMT, telemetry.currentSessionDate => Thu, 23 Jul 2020 06:42:29 GMT}), delete(Set(0) {}) [main 2020-07-23T06:42:29.742Z] [storage state.vscdb] Trace (event): BEGIN TRANSACTION [main 2020-07-23T06:42:29.742Z] [storage state.vscdb] Trace (event): INSERT INTO ItemTable VALUES ('storage.serviceMachineId','d8eb38c7-0dcf-48b6-9240-c40ea31edd39'),('telemetry.lastSessionDate','Thu, 23 Jul 2020 06:41:23 GMT'),('telemetry.currentSessionDate','Thu, 23 Jul 2020 06:42:29 GMT') [main 2020-07-23T06:42:29.742Z] [storage state.vscdb] Trace (event): END TRANSACTION [3326:0723/084229.801441:WARNING:gpu_process_host.cc(1222)] The GPU process has crashed 3 time(s) [3403:0723/084229.802436:ERROR:appcenter_api.cc(52)] expecting appcenter url prefix pci id for fd 28: 8086:3e98, driver (null) [3326:0723/084229.805265:WARNING:gpu_process_host.cc(985)] Reinitialized the GPU process after a crash. The reported initialization time was 0 ms [3326:0723/084229.883314:WARNING:gpu_process_host.cc(1222)] The GPU process has crashed 4 time(s) [3416:0723/084229.884390:ERROR:appcenter_api.cc(52)] expecting appcenter url prefix pci id for fd 27: 8086:3e98, driver (null) [3326:0723/084229.886952:WARNING:gpu_process_host.cc(985)] Reinitialized the GPU process after a crash. The reported initialization time was 0 ms [3326:0723/084229.964448:WARNING:gpu_process_host.cc(1222)] The GPU process has crashed 5 time(s) [3424:0723/084229.965613:ERROR:appcenter_api.cc(52)] expecting appcenter url prefix pci id for fd 23: 8086:3e98, driver (null) [3326:0723/084229.968301:WARNING:gpu_process_host.cc(985)] Reinitialized the GPU process after a crash. The reported initialization time was 0 ms [3326:0723/084230.046925:WARNING:gpu_process_host.cc(1222)] The GPU process has crashed 6 time(s) [3326:0723/084230.046942:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye.
This just started happening yesterday (july 22), now I work with the standard vscode until this one starts working again
The /tmp/vscode-crash folder is empty so no crash-report seems to be written.
Hope this helps...

code-insiders --verbose --crash-reporter-directory /tmp/vscode-crash --disable-gpu

Found --crash-reporter-directory argument. Setting crashDumps directory to be '/tmp/vscode-crash'
[146471:0723/084613.652828:ERROR:appcenter_api.cc(52)] expecting appcenter url prefix
/usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so: undefined symbol: g_date_time_format_iso8601
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
[146500:0723/084613.741352:ERROR:appcenter_api.cc(52)] expecting appcenter url prefix
[main 2020-07-23T14:46:13.800Z] Starting VS Code
[main 2020-07-23T14:46:13.800Z] from: /snap/code-insiders/485/usr/share/code-insiders/resources/app
[146510:0723/084613.801814:ERROR:appcenter_api.cc(52)] expecting appcenter url prefix
[main 2020-07-23T14:46:13.800Z] args: {
  _: [],
  diff: false,
  add: false,
  goto: false,
  'new-window': false,
  'reuse-window': false,
  wait: false,
  help: false,
  'list-extensions': false,
  'show-versions': false,
  version: false,
  verbose: true,
  status: false,
  'prof-startup': false,
  'disable-extensions': false,
  'disable-gpu': true,
  telemetry: false,
  logExtensionHostCommunication: false,
  'skip-release-notes': false,
  'disable-restore-windows': false,
  'disable-telemetry': false,
  'disable-updates': false,
  'disable-crash-reporter': false,
  'crash-reporter-directory': '/tmp/vscode-crash',
  'disable-user-env-probe': false,
  'skip-add-to-recently-opened': false,
  'unity-launch': false,
  'open-url': false,
  'file-write': false,
  'file-chmod': false,
  'driver-verbose': false,
  force: false,
  'do-not-sync': false,
  trace: false,
  'force-user-env': false,
  'open-devtools': false,
  'no-proxy-server': false,
  nolazy: false,
  'force-renderer-accessibility': false,
  'ignore-certificate-errors': false,
  'allow-insecure-localhost': false
}
[main 2020-07-23T14:46:13.802Z] Resolving machine identifier...
[main 2020-07-23T14:46:13.802Z] Resolved machine identifier: add1801b442928cb4a35c33217ada96563c3b8e69783e2f0970561dc4f97bad4
[main 2020-07-23T14:46:13.821Z] update#setState idle
[main 2020-07-23T14:46:13.824Z] [storage state.vscdb] open(/home/jonathan.morrison/.config/Code - Insiders/User/globalStorage/state.vscdb, retryOnBusy: true)
[main 2020-07-23T14:46:13.825Z] lifecycle (main): phase changed (value: 2)
[main 2020-07-23T14:46:13.825Z] windowsManager#open
[main 2020-07-23T14:46:13.827Z] window#validateWindowState: validating window state on 1 display(s) { mode: 1, x: 1922, y: 18, width: 1916, height: 2121 }
[main 2020-07-23T14:46:13.827Z] window#validateWindowState: 1 monitor working area { x: 0, y: 0, width: 3840, height: 2160 }
[main 2020-07-23T14:46:13.827Z] window#ctor: using window state { mode: 1, x: 1922, y: 18, width: 1916, height: 2121 }
[146471:0723/084613.866458:WARNING:gpu_process_host.cc(1222)] The GPU process has crashed 1 time(s)
[146524:0723/084613.871862:ERROR:appcenter_api.cc(52)] expecting appcenter url prefix
[main 2020-07-23T14:46:13.876Z] lifecycle (main): phase changed (value: 3)
[main 2020-07-23T14:46:13.878Z] telemetry/optInStatus { optIn: true }
[main 2020-07-23T14:46:13.878Z] telemetry/machineIdFallback { usingFallbackGuid: false }
[146471:0723/084613.890161:WARNING:gpu_process_host.cc(985)] Reinitialized the GPU process after a crash. The reported initialization time was 16 ms
[146526:0723/084613.898521:ERROR:appcenter_api.cc(52)] expecting appcenter url prefix
[main 2020-07-23T14:46:13.902Z] [storage state.vscdb] Trace (event): PRAGMA user_version = 1;
[main 2020-07-23T14:46:13.906Z] [storage state.vscdb] Trace (event): CREATE TABLE IF NOT EXISTS ItemTable (key TEXT UNIQUE ON CONFLICT REPLACE, value BLOB)
[main 2020-07-23T14:46:13.906Z] [storage state.vscdb] Trace (event): SELECT * FROM ItemTable
[main 2020-07-23T14:46:13.906Z] [storage state.vscdb] getItems(): 75 rows
[main 2020-07-23T14:46:13.950Z] getShellEnvironment: running on CLI, skipping
[main 2020-07-23T14:46:14.007Z] [storage state.vscdb] updateItems(): insert(Map(3) {storage.serviceMachineId => 57fc85a9-ffa6-4e13-9f99-3b31c9538a62, telemetry.lastSessionDate => Thu, 23 Jul 2020 14:45:05 GMT, telemetry.currentSessionDate => Thu, 23 Jul 2020 14:46:13 GMT}), delete(Set(0) {})
[main 2020-07-23T14:46:14.008Z] [storage state.vscdb] Trace (event): BEGIN TRANSACTION
[main 2020-07-23T14:46:14.008Z] [storage state.vscdb] Trace (event): INSERT INTO ItemTable VALUES ('storage.serviceMachineId','57fc85a9-ffa6-4e13-9f99-3b31c9538a62'),('telemetry.lastSessionDate','Thu, 23 Jul 2020 14:45:05 GMT'),('telemetry.currentSessionDate','Thu, 23 Jul 2020 14:46:13 GMT')
[main 2020-07-23T14:46:14.009Z] [storage state.vscdb] Trace (event): END TRANSACTION
[146471:0723/084614.013978:WARNING:gpu_process_host.cc(1222)] The GPU process has crashed 2 time(s)
[146553:0723/084614.015103:ERROR:appcenter_api.cc(52)] expecting appcenter url prefix
[146471:0723/084614.028118:WARNING:gpu_process_host.cc(985)] Reinitialized the GPU process after a crash. The reported initialization time was 12 ms
[146471:0723/084614.143341:WARNING:gpu_process_host.cc(1222)] The GPU process has crashed 3 time(s)
[146561:0723/084614.144427:ERROR:appcenter_api.cc(52)] expecting appcenter url prefix
[146471:0723/084614.147570:WARNING:gpu_process_host.cc(985)] Reinitialized the GPU process after a crash. The reported initialization time was 0 ms
[146471:0723/084614.269885:WARNING:gpu_process_host.cc(1222)] The GPU process has crashed 4 time(s)
[146576:0723/084614.271344:ERROR:appcenter_api.cc(52)] expecting appcenter url prefix
[146471:0723/084614.274290:WARNING:gpu_process_host.cc(985)] Reinitialized the GPU process after a crash. The reported initialization time was 0 ms
(node:146526) Electron: Loading non-context-aware native module in renderer: '/snap/code-insiders/485/usr/share/code-insiders/resources/app/node_modules.asar.unpacked/node-pty/build/Release/pty.node'. This is deprecated, see https://github.com/electron/electron/issues/18397.
[146471:0723/084614.342096:INFO:CONSOLE(1675)] "%cTRACE color: #888 [storage state.vscdb] open(/home/jonathan.morrison/.config/Code - Insiders/User/workspaceStorage/d4b77e1ba3b3cd5958b15c1f62cdfd17/state.vscdb, retryOnBusy: true)", source: file:///snap/code-insiders/485/usr/share/code-insiders/resources/app/out/vs/workbench/workbench.desktop.main.js (1675)
(node:146526) Electron: Loading non-context-aware native module in renderer: '/snap/code-insiders/485/usr/share/code-insiders/resources/app/node_modules.asar.unpacked/vscode-sqlite3/build/Release/sqlite.node'.  The reported initialization time was 0 ms
[146471:0723/084614.515381:WARNING:gpu_process_host.cc(1222)] The GPU process has crashed 6 time(s)
[146471:0723/084614.515397:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye.

Merging this to https://github.com/microsoft/vscode/issues/103060, please follow that issue for updates.

This appears to be a snap issue.
I uninstalled the snap (https://snapcraft.io/install/code-insiders/ubuntu) and re-installed via ppa and apt (instructions: https://wiki.debian.org/VisualStudioCode) and it is working fine.
sudo snap remove --purge code-insiders
sudo apt -y install code-insiders


⚠ ClamAV has degraded performance

In 4f69238, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 62 ms

Resolved: ClamAV performance has improved in 47c89f4.


Stripe Elements has the same variable declared

How can we use Stripe Elements if the same variable Stripe is used by Elements and this plugin?

Unless something changed with Capacitor, this plugin doesn't use window.Stripe variable. It uses window.Capacitor.Plugins.Stripe.
You can import the plugin into your .ts files in many ways without using the name Stripe, example:
import { Plugins } from '@capacitor/core';
const CapStripe = Plugins.Stripe;

Alternatively refer to the Stripe JS library by window.Stripe instead of Stripe.

Unless something changed with Capacitor, this plugin doesn't use window.Stripe variable. It uses window.Capacitor.Plugins.Stripe.
You can import the plugin into your .ts files in many ways without using the name Stripe, example:
import { Plugins } from '@capacitor/core';
const CapStripe = Plugins.Stripe;

Alternatively refer to the Stripe JS library by window.Stripe instead of Stripe.

Ok, but the main problem is that Stripe Elements can’t be used in Capacitor because of https requirement.
How can I fix this?

Not 100% sure. You can try playing with the config values (see https://capacitorjs.com/docs/config) or ask in the Capacitor community (Slack, Reddit, Stackoverflow..etc)
From the config above it looks like you are able to change the server scheme to https but I'm not sure how that would work out (SSL certificates, platform limitations...etc).
Out of curiosity, what are you looking to use Stripe Elements for?
I would like to add UI components to this plugin, so it helps to learn more about how it can be useful in other apps. (e.g what features, fields, or customization options would be useful)

Elements is very useful because it manages form’s style, validation...
Il giorno mer 9 dic 2020 alle 23:10 Ibby Hadeed<EMAIL_ADDRESS>ha scritto:

Not 100% sure. You can try playing with the config values (see
https://capacitorjs.com/docs/config) or ask in the Capacitor community (Slack,
Reddit, Stackoverflow..etc)
From the config above it looks like you are able to change the server
scheme to https but I'm not sure how that would work out (SSL
certificates, platform limitations...etc).
Out of curiosity, what are you looking to use Stripe Elements for?
I would like to add UI components to this plugin, so it helps to learn
more about how it can be useful in other apps. (e.g what features, fields,
or customization options would be useful)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/capacitor-community/stripe/issues/43#issuecomment-742094974,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADEOXWW3O3IOFUF6AUV4LJLST7YV7ANCNFSM4UTGXFAQ
.

--
Stefano Tauriello
<EMAIL_ADDRESS>[image: facebook] https://www.facebook.com/stefano.tauriello[image:
linkedin] https://www.linkedin.com/in/stefano-tauriello-9036784a/[image:
twitter] https://twitter.com/stauriello[image: instagram]
https://www.instagram.com/stefanotauriello/


Fixed str method for prog ex lang imp model. (Fixes #95)

Also added language implementation to loader output.

Should move the log output for prog ex to be before language.


Sync between Teams and Outlook Calendar with notifications?

Hi
I returned back to work today after being on leave last Friday.
This was set as an Out Of Office in my Office 365 Calendar.
On Friday a colleague sent me a conversation using Teams.
I did not reply as I was on Leave and Teams did not say anything.
How can we get Teams to check with Office 365 and then notify the conversation sender that I was OOO?
Cheers
Gordon

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

ID: 2c9b7f77-061d-a224-ff1c-8d3e15d21221
Version Independent ID: 00fa9550-c4c4-3398-ffbb-271cc724048f
Content: Manage Microsoft Teams features in your Office 365 organization
Content Source: Teams/enable-features-office-365.md
Service: msteams
GitHub Login: @LolaJacobsen
Microsoft Alias: lolaj

@214866f Thank you for this feedback
I want to make sure that this OOO issue gets worked on as soon as possible. Support will be able to work this issue to resolution.
I think the best way forward is if you can open a service ticket in your tenant so this can get resolved ASAP. Based on outcome let me know if it is something that can be called out in the docs.
Here is a quick video on opening a ticket: https://www.youtube.com/watch?v=puuOy0sEg1Y
If you don't mind please keep us posted here on the resolution and I really want to get this information you are discovering back into the docs.


Disallow PHP 8.1 support for 6.x

This fixes PHP constraint to "8.0" for 6.1 since PHP 8.1 gives this:

During inheritance of ArrayAccess: Uncaught Return type of Illuminate\Container\Container::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Maybe it's worth to also port these changes to 7.x and 8.x

Moreover, this only allows 8.0.0, and not 8.0.1!

Hm, sorry, this should be probably converted to a draft. Anyways, to give you more context, I have a requirement like this:
{
    "php": "^7.4|^8.0|^8.1",
    "laravel/framework": "^6.0|^7.0|^8.53",
    ...
}

And I run composer update --prefer-lowest since this is a requirement for a lib. Could you please suggest any other solutions?

^8.0|^8.1 is the same thing as ^8.0.

There is nothing you can do to stop Laravel 6 from being installed on PHP 8.1.

Thanks @GrahamCampbell! Closing this then, thanks for helping out!


Added option, disabled by default, to skip adding files to install.  …

…This is useful when the library is being linked statically.

@ladislav-zezula I'm sorry I didn't know about this before, but I wanted to mention that this change was actually not necessary.  There is an undocumented option with cmake whereby a user of stormlib can exclude install() calls from stormlib by doing:
add_subdirectory(stormlib EXCLUDE_FROM_ALL)


perfetto tool trace_to_text eat too much memory

perfetto tool trace_to_text eat too much memory when processing large binary log to systrace text log.
when I record 1 hour long trace log (6.8G) and want to transform it to a systrace text log, my PC was crashed because the trace_to_text.exe occupied all memories. You know, my PC has 16G memory, even through it also not enough for processing the logs.
Can we optimize it?

Add more swap, it's as easy as a dd + swapon (https://linuxize.com/post/create-a-linux-swap-file/)
It's a hard problem and no, you cannot expect that processing a trace takes just as much as the trace size itself. Unfortunately it's not a 1:1 transformation. Many things (even just emitting the right process names) requires first seeing all the set of ftrace events (To track thread start/end) and /proc pollers.
trace_to_text systrace is not as easy as a stream-transformation, it involves queries on the processed data.
If you want to operate with large traces, get more memory or just more swap. your OS can deal with a large swapfile, there is no reason why we should re-implement file-based paging within trace_to_text.


How to convert COCO json to label studio json for polygon segmentation?

Hello,
thank you for the great tool!
I have some image segmentation annotations in format of polygon coco labels. I want to refine this annotations using your tool, so I converted them in the label studio json format. But when I import my converted json file along with input image, the interface only visualizes input image and in right it shows list of 25 polygons, but do not share there overlay on image. But when I import the annotations alone (no input image), I can see my segmentation mask in the interface.
I suspect that there could be one of the two problems :

either your tool does not support overlaying imported segmentation mask (polygons) on images
I referred to your "convert to coco" (opposite of what I want) functionality to convert my coco type annotation to label studio json and there you create points by dividing x, y coordinates by 100 and multiplying by width and height, do you think there is some problem there?

Thank you
Shipra

In case the labels in the annotation do not match the ones you setup when creating your label config, all polygons are shown in light grey and are hardly visible. That is a problem I encountered.
For the inverse conversion (COCO polygon points to LSCF) you need to convert via: p_new = (p*100)/widthOrHeight

WIP: https://github.com/heartexlabs/label-studio-converter/pull/69

Now COCO import is a part of label-studio-converter:
label-studio-converter import coco -h

@shipra25jain how did you convert the coco annotations .json file into label studio json format?

@shipra25jain how did you convert the coco annotations .json file into label studio json format?你们是如何将 Coco Annotations .json 文件转换为 Label Studio JSON 格式的？

When I type label-studio-converter import coco -i result.json -o output.json
Tip: with open(input_file, encoding='utf8') as f:
FileNotFoundError: [Errno 2] No such file or directory: '/home/wjt/PycharmProjects/pythonProject/label-studio-converter/result.json'


Is fastlane compatible with xcode 9?

I changed my commandline version of xcode to 9.0 and my projects timeout when running fastlane. Is this because its not supported yet?

Yeah, it's mostly working with the exception of screenshots.
Please file any issues you see, as we're trying to make sure it works 💯
👍

@taquitos what is the best issue to follow for the screenshots work?

The PR we're working on is: https://github.com/fastlane/fastlane/pull/9570
I think because there are so many issues, it's best to just watch that PR 😄


Icon for vscode tsconfig.json, tasks.json and settings.json

All vscode configs should have the vscode icon instead of default json icon.
jsconfig.json and .vscode/launch.json have the vscode icon but tsconfig.json, .vscode\tasks.json and .vscode\settings.json have the default json icon.

IMHO, if the file has an extension .json, this is JSON file.

In my opinion vscode icons for vscode specific configuration files are fine, but that wasn't my point. This issue is about consistency. At the moment launch.json and jsconfig.json have both vscode icons but other vscode specific configs have json icons. Those files have all the same file extension!

@skolmer, It sounds logical. Perhaps, I agree.

I'm including tsconfig.json for the moment. settings.json and tasks.json are too generic to apply a vscode icon to them. As I cannot set the icon depending on the file's container folder I have no way to discern the correct use of the icon and, therefore, I've decided to keep the json icon for them.


Adding Google Analytics to minikube website

Hello
I am from Minikube team and per conversation with @jimangel I am creating this issue, to request adding Google analytics to minikube website https://minikube.sigs.k8s.io/ (similar to what Kubernetes website has)
I would like to start this request and would like to know what is the next step, and do we create our own Google analytics account or share with Kubernetes Website?

/sig cluster-lifecycle
/sig docs

Thanks for filing @medyagh! We are currently in the process of migrating to a new versions of google analytics, but i think it should be straightforward to set up the minikube site as a new property under the GA4 account we have.
@chalin do you mind weighing in here and letting us know your thoughts about the best way to add a new site? thanks!

The recommended account structure under GA4 differs from that for UA. For context, I'd suggest first reading Google Analytics 4 account structure.
I see the Kubernetes organization like Example B in that GA4 docs page, which would suggest that we'd use the same property (and it's single web data stream) to track all websites under the Kubernetes organization. With such a setup, we'll be able to track user journeys across all k8s sites. Also with this approach, we'll probably have to define custom reports for each website, but we would have to do that anyways if we want the equivalent of the UA views defined as part of the original Kubernetes UA account (it had 4 defined views).
I'm still learning about this (GA4 is quite different from UA), so the above is to the best of my understanding. Comments are welcome. I'd be willing to hop onto a VC to discuss this if that could help.
/cc @nate-double-u

Question: how urgent is this? Or, to ask this another way, by when would you like GA to be setup for the site?

we'll probably have to define custom reports

Ok, I've finally gotten the GA4 i/f to cooperate: I'm now able to create, save and make easily accessible custom reports that filter, for example, by hostname.

The simplest way to enable analytics to the minikube website is via Netlify snippet injection, as is done for kubernetes.io. @medyagh - I'd be glad to set that up, or guide someone into doing so, If someone grants me access to the minikube Netlify account.
FYI: the Docsy version of the minikube website is too old to support GA4, so Docsy would need to be updated if we'd want to enable GA4 via Docsy config.

Thank you very much @chalin we will update our docsy submodule, what code do we need to inject to our template ? and after that how do we access the metrics ?

Should this issue be moved to the minikube website repo?

I'm happy to move it (I think we'd need to open a new issue and close this one).

@a-mccarthy et al.: are you ok with what is proposed in https://github.com/kubernetes/website/issues/37801#issuecomment-1309395460?

Thank you very much @chalin we will update our docsy submodule, what code do we need to inject to our template ? and after that how do we access the metrics ?

@medyagh - it won't hurt to update the Docsy module in the meantime, but I'd hold off on enabling analytics via Docsy. As I mention in https://github.com/kubernetes/website/issues/37801#issuecomment-1310569148, I recommend using snippet injection instead. Do you know if the website is hosted by Netlify?

Thanks @chalin we just updated the Docsy https://github.com/kubernetes/minikube/pull/15342
I am not familiar with snippet, is there any action needed on our end ? and how do we accesses the analytics metrics

@chalin I agree with your assessment. It appears that example b in the linked page is the closes to how we currently have the analytics set up, as well as how we'd like to collect analytics going forward. In this model, we'd have one account and a separate property for each website we collect analytics for. Do we have a list of all the current websites we are tracking our should add to the new G4 account? So we know what should be migrated over, if anything?
You've raised questions about what sites should be connected to the Kubernetes analytics account before, and i'm note sure if there was a final answer there. But this feels like something we should decide on and keep track of somewhere. Hopefully we can write down the criteria and process for getting added so folks know how to ask for this in the future.
(ps sorry for my delayed response)

@a-mccarthy: thanks for your response. Actually, "Example B" in the Google Analytics 4 account structure page suggests a single property for all websites, and in fact, a single web stream for all websites (so that, e.g., we can configure cross-domain tracking).
For a list of k8s websites (at least those that I currently know about), see rows 2 - 12 of the CNCF project GA4 migration status.

You've raised questions about what sites should be connected to the Kubernetes analytics account before, and i'm note sure if there was a final answer there.

Yes, that is the main question to be answered, and the one that will impact how we choose to setup the GA4 account. As you proposed elsewhere, maybe we should meet to discuss this.

But this feels like something we should decide on and keep track of somewhere. Hopefully we can write down the criteria and process for getting added so folks know how to ask for this in the future.

Agreed.

thank you both @a-mccarthy and @chalin to get this updated, and glad we are making this a process for next websites,   is there any action on our end (minikube team) to do ?

Not that I can see @medyagh, thanks.

hi @chalin @a-mccarthy @sftim  just following up on this, is there any instruction for minikube maintainers how we can register/login to see the analytics ?

@medyagh - the GA4 measurement ID is G-JPP6RFM2BP. You can add it to the project's Hugo config file: search for "analytics" and replace the bogus ID that's there with the GA4 ID. Let me know which email address(es) to grant access to.

thank you @a-mccarthy and also @chalin, we just added the ID to our config,
@chalin would you mind sharing the access with me ? if needed to share personal email, maybe we could exchange info on slack ?

@medyagh - sure, DM me via Slack (K8S or CNCF)

I can confirm with the Tag Assistant that the GA4 ID is being used by the minikube site. Can we close this issue now?

FYI, the console is showing MiniKube events:

Also, I added a custom MiniKube report so that you can easily determine page views for the site:


add a flag to mark automatically answered questions

We need to discuss this, at the moment there is a flag for disabled assessments (either because of the pre-session form or because of dependencies), and I added a flag for automated assessments.
But we need to decide when this automated flag should be set to True, and if we need other ones

Well, everything that can not be changed by direct user interaction should be flagged as automated.

questions that are answered based on the preleminary assessment
questions which answers are derived from their dependencies

Is the automated flag is currently always set to false?

Is the automated flag is currently always set to false?

Yes, I added the attribute but it is not modified yet in the code.

Well, everything that can not be changed by direct user interaction should be flagged as automated.
* questions that are answered based on the preleminary assessment

* questions which answers are derived from their dependencies

I just added the change in the develop branch. When the task is created, I set the automated attribute to True if the default status is not queued. This covers both cases.


Concierge: Agreement should be optional

User should be able to proceed irrespective of whether they select the

Note that without clicking agree the shring of the app state should be disabled and the user should be prompted to confirm this

Also "for analytics" seems like a wrong title here

Modall should just be removed as discussed

Modal has be updated for it


How to interpret the exel file and use it to improve the modelisation

Hi,
I recently discover this tool and thank you for the port in python.  I have' some questions:

i understand very well the first sheet and I see it is a kind of feature importance by each score
we have the same principle in sheet 2 for interaction but first what you understand by interraction here ?
for example in the iris data, the interaction petal length (cm)|petal width (cm) has the best gain score. How to use this information in the modlisation ?

thanks you for your answer

I was also wondering what the Leaf Statistics show? What information can you glean about the model from these statistics?


improve Collapsible component UI + APIs #528

Added changes to the collapsible component

The usestate values or the trigger button can be given by the user.
when the users don't provide any value or trigger component it uses the default components
added simple styling
Can set the default values using the default prop
Can use the disabled prop to enable or disable the collapsing property

Summary by CodeRabbit

New Features

Enhanced Collapsible component with new properties for improved configurability and dynamic rendering.
Introduced new context for managing collapsible UI state across components.
Added new components: CollapsibleContent, CollapsibleItem, CollapsibleRoot, and CollapsibleTrigger for better structure and usability.

Bug Fixes

Improved rendering logic to handle disabled state and default open items correctly.

Style

Added new SCSS styles for collapsible components to enhance visual presentation.

Documentation

Updated stories for the Collapsible component to reflect new data structures and props.

https://github.com/user-attachments/assets/65b42526-84db-4faf-b97c-faf56785f99a
A video example


Issue trying to recovery our custom stack using logical contexts at async mvc controller.

Initially, I've updated our dummy MDLC impl. for tests.. and implemented the interface ILogicalThreadAffinative for our CustomStack<>

Looking for more information, I've founded some relevant posts where explain 'the problem'..
https://stackoverflow.com/questions/43391498/asynclocal-value-is-null-after-being-set-from-within-application-beginrequest
https://stackoverflow.com/questions/66500737/asynclocalt-doesnt-reach-controllers

Finally, this problem will be handled different.


feature in about section

in about section last part is not appropriate I want to work on It please assign this feature under gssoc label

the main box can utilize the width and then the wrtitten text about congniguard as 2 boxes are not looking good side by side
the font family can be improved as well,
plz assign it to me

@Aashka19  Currently it is very basic. It's better to change the whole design of the page,
propose the design if you interested.

sure the page can be changed on the basis of what all you need in this page
tell me your requirements
i can propose a design accordingly

⚠[URGENT]⚠ Reminder for Closing of Contribution period for GSSoC 24'
Finish your work and raise the PRs ASAP to get your points.
Thanks💗 for your valuable Contributions!


Supports class variables in attr binding

Combined with https://github.com/voltrb/volt/pull/190 you can do
e.g. <input type='text' value='{{ Volt.fetch_current_user._name }}' />

Class variables work in attr bindings as is, why is this needed?  Also, your example isn't using class variables.

I have trouble naming the thing I was referring to. If it is not class variables it is more of anything starting with a capital Class. Right now in attribute_scope it only allows setting a setter with lower case letters.

Can you make a spec for this?  This will fail if you just put in a Class directly.

That's intended, you are not allowed to just put a class in the attribute binding because it doesn't make sense to bind to a class. It checks to see if there is a "." in the expression.

Sorry, my bad, I read it wrong.  I was referring to something else.


Add tilde to surrounding pairs in markdown

This pull request simply adds the tilde (~) symbol to the list of surrounding pairs, which makes it possible to select text, press the tilde key and have the text be automatically surrounded with ~. This is primarily useful for quickly making text ~~strikethrough~~, or if you prefer to use the tilde symbol for code blocks (~~~ is an alternative to ```).
I am guessing that the tilde symbol was simply forgotten in the list of surrounding pairs, since e.g. * and _ are nicely supported.

Sorry, as this PR wasn't linked to any issue I merged #216394 instead even though it came in later
Closing since this is now a duplicate


Cannot update on 19.1.604.3

Hello,
I have this message :
Severity	Code	Description	Project	File	Line	Suppression State
Error		Unable to find a version of 'eXpandLib' that is compatible with 'eXpandExcelImporter 19.1.604.3 constraint: eXpandLib (>= 19.1.604.3)', 'eXpandModelArtifactState <IP_ADDRESS> constraint: eXpandLib (>= <IP_ADDRESS>)', 'eXpandPivotChart <IP_ADDRESS> constraint: eXpandLib (>= <IP_ADDRESS>)', 'eXpandValidation <IP_ADDRESS> constraint: eXpandLib (>= <IP_ADDRESS>)', 'eXpandWorldCreator <IP_ADDRESS> constraint: eXpandLib (>= <IP_ADDRESS>)'.
Should i wait a bit ?

I did not update the VSIX but i do not think that is has something to do. Does it ?

pfff now me too. sorry it seems that tried to early...


why index.js is needed in each folder

Hi,
I am not sure why we need a index.js in each of the folders (actions, routes, views).
For ex: we have views/HomeView.js and we are doing export default in it.
Why do we need to explicitly do export HomeView in index.js ??
Thanks

Hey @mars76, you're right, this project could use a lot of cleanup. I plan to do a full re-write in the coming weeks.


Add CLI paramter: sending interval

The data gets send in a specific interval. This interval is currently hard coded. It would be nice if the user could decide which sending frequency best tests their own use cases.
Implementation analagously to #1

Done CLI parameter -i (sending_interval)


Issues for dogfooding

rad> (def iss (create-issues-chain! "http://localhost:8000/chains/issue"))
()
rad> (def pk (gen-key-pair! (default-ecc-curve)))
()
rad> (new-issue! iss pk "first post!" "ha!")
()
rad> (update-chain-ref iss)
:ok
rad> (list-issues iss)
{"80ebe1f7-af53-4b06-8fec-c0e650f67aa0" {:author [:PublicKey
                                         {:public_curve [:CurveFP
                                          [:CurvePrime
                                          1.15792089237316195423570985008687907853269984665640564039457584007908834671663e77
                                          [:CurveCommon
                                          {:ecc_a 0.0
                                           :ecc_b 7.0
                                           :ecc_g [:Point
                                           5.506626302227734366957871889516853432625060345377759417550018736038911672924e76
                                           3.2670510020758816978083085130507043184471273380659243275938904335757337482424e76]
                                           :ecc_h 1.0
                                           :ecc_n 1.15792089237316195423570985008687907852837564279074904382605163141518161494337e77}]]]
                                          :public_q [:Point
                                          5.9605107679519374434469409600953760933308171403411196742136326186373746341841e76
                                          9.2569644742926593965522568976910626768947416743413547335392774207052135301848e76]}]
                                         :body "ha!"
                                         :id "80ebe1f7-af53-4b06-8fec-c0e650f67aa0"
                                         :signature [:Signature
                                         {:sign_r 2.2542684324337681569912169481489129996977395863760827563302384549855514104967e76
                                          :sign_s 1.04442519962667784337264909323918544758291644047798063968699158377487007797443e77}]
                                         :title "first post!"}}
rad>

list-issues could do a better job of keeping only crucial signature information, and we evidently don't have the world's best pretty-printing, but a basic amendable issue chain now works (without any actual checking of sigs).
This PR also fixes the broken :enter-chain, and adds it to the test. Part of that involved mocking send! and receive!, so now we can write tests involving those. However, should-bes are a little trickier; they'll use the mocked networking when run as part of the test suite, which is nice, but they'll run against the real send!/receive! when run on normal startup, so we still need a little more work there.
EDIT: I've now also made tests only be run with the Haskell test suite by having should-be check that a variable is defined. We should now be good to test remote-chain interactions directly in radicle files. (Also, I fixed the fact that the rad source files weren't actually being tested in the Haskell test suite, but only when run directly.)

Gah, I rewrote should-be as a macro so it'd be nicer and more importantly not eval its arguments (so we can have tests that do mocked networking but don't do any harm when run in non-test envs). But it turns out eval redef doesn't work in remote chains because we wrap everything in a do block when sending. So this whole thing is going to become a bigger and deeper rabbit hole.

At last!


zulip_botserver: Handle all requests from the root / endpoint.

Previously, the Botserver determined which bot to run by
dispatching on a different URL endpoint /bots/ for each bot.
Now, instead, the Botserver determines which bot to run by the section
header of the bot in the flaskbotrc.
This implementation simplifies the setup of the Botserver. However,
without the dispatch on the URL endpoint, the Botserver cannot tell
anymore which bot to run for an incoming message. Therefore, it now
inspects each message for the bot name that is @mentioned in it. It
then looks for a section in the flaskbotrc that has this name as a
property and runs the associated bot. The name property is newly
introduced with this commit.
This depends on https://github.com/zulip/zulip/pull/9493.

Hmm, this implementation will not work with private messages that do not @-mention the bot. So I guess we should first always try to find a bot email in the recipients, and only try to match the name if there is no email match.

Superseded by #398.


pnpm install -g not supported

To Reproduce

Run asdf plugin install pnpm
Running pnpm install -g <any global package> gives the following error:

ERROR  Unable to find the global bin directory
Run "pnpm setup" to create it automatically, or set the global-bin-dir setting, or the PNPM_HOME env variable. The global bin directory should be in the PATH.

I think it's related to this issue, which is that unlike npm, pnpm doesn't try to autodetect where to put the global installations.
And while you could configure it by running pnpm setup, then it would configure all asdf's pnpm installations to use the same directory, regardless of what version of pnpm you're using, which seems counter to asdf's purpose of allowing multiple versions being installed.

I'll defer this issue to see what approach pnpm takes upstream

@jonathanmorley, hi. Do you've any news on this issue?


Missing Support for on premises AzDevOps Repos

Duplicate of #12 ?

Yes, closing as duplicate of #12.


Fix qualifier in purge_stale_instances

Remove cluster name from instance name when returning list of stale instances to prevent qualifier from being added twice by calling functions.

Code is modified with the above corrections.

Updated the code with the above suggestion.

Thanks!


train with my own dataset

Thanks for this great work！
Can you tell me how to train with my own dataset？ I am a little confused with the construction of the dataset.
Can you help me? Thanks so much.

Hey, did you get any luck getting this running?


Hugo Install Not Being Detected

I am not sure what is being looked for exactly. This is a publication problem for I believe all branches.
I have created a fake branch to investigate the problem. It was that they had changed tar structure. However hugo is certainly on path and the HugoPlugin believes it to not be installed.
Here is the travis build
Here is generic script so it should be handled anywhere. As you can see the .local and local were both on path and which finds the program correctly.
      script:
        - source $TRAVIS_BUILD_DIR/bin/setup.sh
        - curl -s -L "https://github.com/gohugoio/hugo/releases/download/v${HUGO_VERSION}/hugo_${HUGO_VERSION}_Linux-64bit.tar.gz" | tar xzf -
        - ls -lah
        - mkdir -p $HOME/.local/bin
        - mv "$TRAVIS_BUILD_DIR/hugo" "$HOME/.local/bin/hugo"
        - echo $PATH
        - which hugo
        - sbt ";makeSite"

Fairly certain we could fall back to an old version of Hugo where we know the tar archive behaves as we expect for a temporary fix, however it looks like there is something wrong with the Hugo-Plugin in the new format.
Any ideas are welcome.


feat(tutorial): complete step 5

Closes #
{{short description}}
Changelog
Click here to access the deployed app.

{{new thing}}

Changed

{{change thing}}

Removed

{{removed thing}}

Done!


Publish 07/28/2021, 10:30 AM

Docs Build status updates of commit 1652a4e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Get-OrganizationSegment.md
:white_check_mark:Succeeded
View (exchange-ps)

skype/skype-ps/skype/Enable-CsUser.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Get-CsTenantNetworkSite.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsApplicationAccessPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

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