Getting error while trying to retrieve cost for using Custom timeframe

I am trying to get Azure cost for last month and trying to use Custom timeframe using "from" and "to" date, but getting error,
Error: Object reference not set to an instance of an object.
Here is the stack:
❯ azure-cost show -s XXXXXXXXXXXXXXXXXXXXXXX --timeframe Custom --from 3/1/2023 --to 3/31/2023 --debug
Using token credential: ChainedTokenCredential to fetch a token.
Token retrieved and expires at: 4/16/2023 8:33:02 AM +00:00
Retrieving costs from /subscriptions/XXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.CostManagement/query?api-version=2021-10-01&$top=5000 using
the following payload:
{
"type": "ActualCost",
"timeframe": "Custom",
"timePeriod": {
"from": "2023-03-01",
"to": "2023-03-31"
},
"dataSet": {
"granularity": "Daily",
"aggregation": {
"totalCost": {
"name": "Cost",
"function": "Sum"
},
"totalCostUSD": {
"name": "CostUSD",
"function": "Sum"
}
},
"sorting": [
{
"direction": "Ascending",
"name": "UsageDate"
}
]
}
}
Response status code is OK and got payload size of
Retrieving costs from /subscriptions/XXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.CostManagement/forecast?api-version=2021-10-01&$top=5000 using
the following payload:
{
"type": "ActualCost",
"dataSet": {
"granularity": "Daily",
"aggregation": {
"totalCost": {
"name": "Cost",
"function": "Sum"
}
},
"sorting": [
{
"direction": "Ascending",
"name": "UsageDate"
}
],
"filter": {
"Dimensions": {
"Name": "PublisherType",
"Operator": "In",
"Values": [
"azure"
]
}
}
}
}
Response status code is OK and got payload size of
Retrieving costs from /subscriptions/XXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.CostManagement/query?api-version=2021-10-01&$top=5000 using
the following payload:
{
"type": "ActualCost",
"timeframe": "Custom",
"timePeriod": {
"from": "2023-03-01",
"to": "2023-03-31"
},
"dataSet": {
"granularity": "None",
"aggregation": {
"totalCost": {
"name": "Cost",
"function": "Sum"
},
"totalCostUSD": {
"name": "CostUSD",
"function": "Sum"
}
},
"sorting": [
{
"direction": "Ascending",
"name": "UsageDate"
}
],
"grouping": [
{
"type": "Dimension",
"name": "ServiceName"
}
],
"filter": {
"Dimensions": {
"Name": "PublisherType",
"Operator": "In",
"Values": [
"azure"
]
}
}
}
}
Response status code is OK and got payload size of
Retrieving costs from /subscriptions/XXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.CostManagement/query?api-version=2021-10-01&$top=5000 using
the following payload:
{
"type": "ActualCost",
"timeframe": "Custom",
"timePeriod": {
"from": "2023-03-01",
"to": "2023-03-31"
},
"dataSet": {
"granularity": "None",
"aggregation": {
"totalCost": {
"name": "Cost",
"function": "Sum"
},
"totalCostUSD": {
"name": "CostUSD",
"function": "Sum"
}
},
"sorting": [
{
"direction": "Ascending",
"name": "UsageDate"
}
],
"grouping": [
{
"type": "Dimension",
"name": "ResourceLocation"
}
],
"filter": {
"Dimensions": {
"Name": "PublisherType",
"Operator": "In",
"Values": [
"azure"
]
}
}
}
}
Response status code is OK and got payload size of
Error: Object reference not set to an instance of an object.

Thanks for reporting, I think it is fixed in v0.8.0, released any minute now.


I wondered why each waveform has a 60 seconds ground motion in STEAD. Is there any scientific evidence behind it?

I wondered why each waveform has a 1-minute long ground motion in STEAD. Is there any scientific evidence behind it?

The window lenght is selected based on the distance and msgnitude range of
earthquakes in a way it cover the entire waveform.
On Sat, Aug 13, 2022, 12:22 AM andrewbauras @.***>
wrote:

—
Reply to this email directly, view it on GitHub
https://github.com/smousavi05/STEAD/issues/14, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADHWAPD675UXL4CLAAFTTTLVY5EKHANCNFSM56NWKMVQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thank you for the answer and your prompt response.


mlb_elo heading legend

I'm trying to figure out what the column headings mean in the mlb_elo.csv file and am running into a problem deciperhing what is in the columns that start with elo* and the rating1_post and rating2_post columns
date: date of game
season: year of season
neutral: whether game was on a neutral site
playoff: whether game was in playoffs
team1: abbreviation for home team
team2: abbreviation for visiting team
elo1_pre:
elo2_pre:
elo_prob1:
elo_prob2:
elo1_post:
elo2_post:
rating1_pre: ELO rating for home team before deductions
rating2_pre: ELO rating for visiting team before deductions
pitcher1: name of home team pitcher
pitcher2: name of visiting team pitcher
pitcher1_rgs: home team pitcher run score
pitcher2_rgs: visiting team pitcher run score
pitcher1_adj: home team pitcher ELO score adjustment
pitcher2_adj: visiting team pitcher ELO score adjustment
rating_prob1: probability of home team winning based on adjusted ELO scores
rating_prob2: probability of visiting team winning based on adjusted ELO scores
rating1_post: ELO rating for home team after game decision
rating2_post: ELO rating for visiting team after game decision
score1: home team score
score2: visiting team score

Looking at the data from the 2018-07-01 CHC vs MIN game the csv files has:
date: 2018-07-01
season: 2018
neutral: 0
playoff: 0
team1: CHC
team2: MIN
elo1_pre:	1548
elo2_pre:	1492
elo_prob1:	0.614
elo_prob2:	0.386
elo1_post:	1549.39538447082
elo2_post:	1490.68996714635
rating1_pre:	1562
rating2_pre:	1491
pitcher1:	Jon Lester
pitcher2:	Lance Lynn
pitcher1_rgs:	55.1
pitcher2_rgs:	50
pitcher1_adj:	17.1
pitcher2_adj:	-2.43
rating_prob1:	0.659
rating_prob2:	0.341
rating1_post:	1562.80857309143
rating2_post:	1490.58601631338
score1:	11
score2:	10

The elo1_pre and elo2_pre values don't seem to correspond to what is posted on the website. The pregame ELO scores were 1562 and 1491 (i.e. rating1_pre and rating2_pre). I'm not sure where the elo1_pre and elo2_pre came from nor the elo_prob values (i.e. 1/(1+10^((1491-1562)/400)) = 0.601). Any help?

Thanks for adding the documentation to the README. I'm afraid this doesn't really answer my questions. What is the difference between elo1_pre and rating1_pre1? Also, aside from the numbers inputted to the formulae, is the formula for elo1_prob different from that of rating_prob1? i.e.  1/(1+10^((Rb-Ra)/400

thanks!
On Tue, Jul 3, 2018 at 9:18 AM Pat Schloss<EMAIL_ADDRESS>wrote:

Thanks for adding the documentation to the README. I'm afraid this
doesn't really answer my questions. What is the difference between
elo1_pre and rating1_pre1? Also, aside from the numbers inputted to the
formulae, is the formula for elo1_prob different from that of rating_prob1?
i.e. 1/(1+10^((Rb-Ra)/400
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/fivethirtyeight/data/issues/194#issuecomment-402213403,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AmfvkDhYcsfFnvTJlYlKB6-thaKmAtLYks5uC5lygaJpZM4U_f38
.


Fix wrong name of a terraform example application

What this PR does / why we need it:
This wrong name causes a broken link in the README.md of examples repository.
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:

NONE

Nice catch ⚾
/approve

/approve cancel

please update links to example applications on the docs too 👀
https://pipecd.dev/docs/examples/#terraform-applications

Nice catch!
Thank you. Fixed!

Thx 🚀
/approve


chores: use guarded logs for debug messages in plugins

Along with the other cleanups, it seems to bring some improvements to the plugin execution.
Execution time before all the cleanups:
camel-bundle-plugin:manifest (bundle-manifest) ........... [176.321s]
camel-package-maven-plugin:generate (generate) ........... [118.200s]

With the other cleanups + this one:
camel-bundle-plugin:manifest (bundle-manifest) ........... [140.743s]
camel-package-maven-plugin:generate (generate) ........... [88.600s]

This depends on #6951.


Is it feasible to apply this method to the Semantic3D dataset?

Hi:
 Is it feasible to apply this method to the Semantic3D dataset?

Best!

Hi,
We haven't tried but it should be feasible.
For fine-tuning, the weights pre-trained on SemanticKITTI (available in the repo) can be used to fine-tune the network to Semantic3D.
The pre-training should work but may be necessary to do some adjustments on the RANSAC parameters (for ground removal) and on the DBSCAN (to cluster and segment the remaining objects).

I will close this issue due to inactivity, feel free to reopen it if necessary.


upstream destroy stats missing from HTTP conn pools

Was just doing some debugging and realized that the following stats are not incremented in the HTTP connection pools, but only the TCP connection pool:
upstream_cx_destroy
upstream_cx_destroy_local
upstream_cx_destroy_remote

This is confusing and we should fix. I don't recall the history here but I'm guessing these were implemented for the TCP connection pool and never ported over. I think we could easily have a shared utility function that helps us unify this logic across the pools.

I would be happy to take this one!

Please do @HashedDan!


setValueFromCoords not working correctly

Hi using version v4.2.0,
I have a simple spreadsheet with dimensions minDimensions:[32,50],  defined.. so 50 rows by 32 columns.
If I try to define a value in say cell A34 eg spreadtable.setValueFromCoords(33,0,"X",true); I get a fatal error..
TypeError: obj.records[y][x] is undefined.. only seems to update cells with rows below 33..
Should be able to define values anywhere in the declared spreadsheet.
By the way, a similar issue with the inverse function getValueFromCoords().

Sorry my mistake.. the definition in document of x and y was a bit confusing should be spreadtable.setValueFromCoords(0,33,"X",true); not spreadtable.setValueFromCoords(33,0,"X",true); - x is the column and y is the row... might however be worth adjusting the documentation to state that x is the column and y is the row number...


/stats endpoint

This would be a basic HTTP endpoint that can be turned on or off via config, and would contain useful stats like:

How many DBs are pinned?
What is the size of each DB?
When was each DB last replicated / used?

Open to more stats here as well

Weekly and monthly snapshots so we can track the size of individual DBs over time

Also, please don't literally do log.education/stats because those are Apache logs currently


[AssetInfo] Add Ledger label

Update AssetInfo (src/renderer/components/uielements/assets/assetInfo/AssetInfo.tsx)

Add walletType: WalletType to props
Whenever walletType === 'ledger' show ledger label as follow

^ https://www.figma.com/file/LgRqZCGMShZ2mJ702MIqyV/ASGARDEX-2020?node-id=1307%3A351

Pls quick fix the following with this PR in .storybook/preview.tsx

Without that ^, running storybook is failing currently ...


Unhandled Exception when changing audio devices while device-specific Windows spatial audio filters are active.

Operating system or device - Godot version:
Win10x64pro v1703 b15063.540 w/Asus Sabertooth x79 using Realtek ALC892 audio chipset, Windows spatial sound filters active. Godot v3.0 alpha 1536cc4
Issue description:
I executed Godot, then while it was idle on the project selection interface, I plugged in my headphones. On my system (Win10x64pro v1703 b15063.540 w/Asus Sabertooth x79 using Realtek ALC892 audio chipset) my headphone jack in the front disables the rear speaker and makes the headphones (considered another device) the primary Windows audio output device. When this occurred, Godot crashed. This did not happen when I tried to simulate it by changing my audio device in the Windows audio device manager with a new instance of Godot loaded to the same state. The crash also did not occur when I unplugged my headphones, only when plugging them in. This led me to suspect the problem is not with changing devices. I realized I was using the Dolby Atmos audio filter with 7.1 virtual surround enabled (Windows 10 spatial audio), which is configured only for use with my... headphones. When I right-clicked my audio TSA icon and hit the menu option for Atmos, I found it had silently crashed, and Windows had now detected it, offering to reenable the application. I then disabled Atmos, and all filters. I ran Godot and repeatedly plugged/unplugged the jack. Everything was fine. I activated another filter, Windows Sonic for Headphones, again with virtual surround on. Again Godot crashes on device change. Disabling the virtual surround had no effect, still crashes. Also tested with the editor in other states, like with a project loaded, same result as expected. Opening the editor and toggling the effect on my headphone device settings while they are active causes no error.
MSVS2015 JIT debugger reports an unhandled win32 exception at 0x0007FFF6EF9A7CA5
Breaking execution at the exception puts me on the last brace of RtApi :: error. errorText_ reads "RtApiDs::callbackEvent: error (Buffer lost) getting current write position!"
Conclusion
Changing audio devices while Windows spatial sound filters are enabled causes an unhandled exception due to the output stream buffer being lost. But why is this a problem only when using spatial audio with device changes, not software changes? Is this actually a Windows bug to work around? I'm not sure how to best handle this, so I leave the code to others this time.
Steps to reproduce:
Enable spatial audio filters in Win10CE. With Godot loaded, plug/unplug headphone jack on an audio chipset with jack detection and retasking causing the filter to become enabled/disabled by the device change notification.

Hey I found something else out today. When enabling spatial audio, Windows sets the device to 44khz without telling you... I couldn't make Godot throw an exception by changing bit or sample rates, I tried.

Can you test with 2.1.4 beta? There is an old issue like that (#5211) that's supposed to be fixed.

I tried with the windows binary you provided a link to, I couldn't make it crash no matter what I did. :) Hmm...

Did you test this on latest master? This shouldn't be happening anymore with the new WASAPI driver.

No answer, so assuming fixed in 3.0 and later. Please comment if you can still reproduce the issue in the latest stable or development versions.


feat: implement SHPlonk multipoint opening

Description
There are several feature and refactorings to implement SHPlonk. Now VectorCommitmentScheme has new interface for that and several classes are introduced for opening proof. See polynomial_openings.h.
Feature
These are new added interfaces to VectorCommitmentScheme<Derived>.

CreateMultiOpeningProof()
VerifyMultiOpeningProof

These are new added methods to UnivaraitePolynomial<F, MaxDegree>.

FromRoots()
Linerize()
LinerizeInPlace()
DivByVanishingPolyInPlace()
DivByVanishingPoly()
EvaluateVanishingPolyByRoots()

UnivaraitePolynomial<F, MaxDegree> also supports hashing.
These are new added methods to Transcript<T>.

ToReader()
ToWriter()
SqueezeChallengeAsScalar()

Refactoring

zk::Ref<T> moves to base::Ref<T>

FEATURE: base::Ref<T> is divided into base::Ref<T, true>, base::ShallowRef<T> and base::Ref<T, false>, base::DeepRef<T, false>.

zk::Transcript<T> moves to crypto::Transcript<T>

Performance

Use reference when calling std::accumulate() to avoid copying.
When dividing polynoimal by scalar, do inverse only once.

There is new name of the polynomial, "Minimal polynomial" that can be divided by every (x - ri) and has lowest degree
See, https://en.wikipedia.org/wiki/Minimal_polynomial_(linear_algebra)

Can you fix typo in adeda7f? univaraite -> univariate.

I'm not sure if we need this change fb9547e. Why not just use FromRoots and do division and use Evaluate to get the evaluation of vanishing polys?

Okay I'll fix it to create a vanishing polynomial based on roots and divide by it. FYI, @dongchangYoo also mentioned about this.

@chokobole Can you add math scope for b43a923?

@chokobole

Do we need 60a3c9c as well? Doesn't LagrangeInterpolate do enought for LDEs?
Can you fix typo in 60a3c9c? univaraite -> univariate.

I'll remove it since it is not used at this moemnt.
I'll do


There is haxl-<IP_ADDRESS> on the Hackage

... but this repository has version: <IP_ADDRESS>. Is the development branched privately?
http://hdiff.luite.com/cgit/haxl/diff?id=<IP_ADDRESS>&id2=<IP_ADDRESS> (seems that not, but still weird).

I forgot to push my local commit.  Should be fixed now, thanks for reporting.


[Fused Ops] Add fused version of Elu

Includes refactoring of ONNX importer prelu function to use fused PReLu op

@postrational a few more things to complete this PR

[ ] Add ops to fused_op_tbl (https://github.com/NervanaSystems/ngraph/blob/master/src/ngraph/op/fused_op_tbl.hpp) That will then require you to add support for these ops in the serializer as well.
[ ] Add at least one test to https://github.com/NervanaSystems/ngraph/blob/master/test/backend_fused_op.in.cpp
[ ] Add at least one test to https://github.com/NervanaSystems/ngraph/blob/master/test/type_prop.cpp


New Check - Agent Alerts are configured

Agent alerts are setup.
Glenn Berry suggests 19-25 & 825
https://www.red-gate.com/simple-talk/sql/database-administration/provisioning-a-new-sql-server-instance-part-three/
Brent Ozar suggests 16-25 & 823-825
https://www.brentozar.com/blitz/configure-sql-server-alerts/

Hi
I have started to look at this I have done the following below in my repo. Since we have SCOM monitor at our place we have created an agent job that will write to eventlog incase we have one of these alerts instead of having SQL notify us by email. I choose to set notification by operator as default. Any thoughts? Will add for 823-825 also but since that is on messageID instead of severity I think it will be in another Describe block since I named this Agent Alerts Severity
Set-PSFConfig -Module dbachecks -Name agent.alert.Severity -Value @('16', '17', '18', '19', '20', '21', '22', '23', '24', '25')  -Initialize -Description "Agent alert severity alerts to check if in place https://www.brentozar.com/blitz/configure-sql-server-alerts/"
Set-PSFConfig -Module dbachecks -Name agent.alert.Job -Value $false -Initialize -Description "Agent alert job in place to catch the alert check. Ex job to write to eventlog for SCOM monitoring"
Set-PSFConfig -Module dbachecks -Name agent.alert.Notification -Value $true -Initialize -Description "Agent alert notification in place check"

Describe "Agent Alerts Severity" -Tags AgentAlertSeverity, $filename {
    $severity = Get-DbcConfigValue agent.alert.Severity
    $AgentAlertJob = Get-DbcConfigValue agent.alert.Job
    $AgentAlertNotification = Get-DbcConfigValue agent.alert.Notification
    write-host $severity
    write-host $AgentAlertJob
    write-host $AgentAlertNotification
    @(Get-SqlInstance).ForEach{
        write-host $psitem
        Context "Testing Agent Alerts Severity settings on $psitem" {
            $alerts = Get-DbaAgentAlert -SqlInstance $psitem
            ForEach ($sev in $severity) {
                It "Should have Severity $sev Alert" {
                    ($alerts.Where{$psitem.Severity -eq $sev}) | Should -be $true -Because "Recommended Agent Alerts to check for http://blog.extreme-advice.com/2013/01/29/list-of-errors-and-severity-level-in-sql-server-with-catalog-view-sysmessages/"
                }
                It "Should have Severity $sev Alert enabled" {
                    ($alerts.Where{$psitem.Severity -eq $sev}) | Should -be $true -Because "Configured alerts should be enabled check"
                }
                if ($AgentAlertJob) {
                    It "Should have Jobname for $sev Alert" {
                        ($alerts.Where{$psitem.Severity -eq $sev}).jobname -ne $null | Should -be $true  -Because "Notify by SQL Agent job check"
                    }
                }
                if ($AgentAlertNotification) {
                    It "Should have notification for $sev Alert" {
                        ($alerts.Where{$psitem.Severity -eq $sev}).HasNotification -eq 1 | Should -be $true -Because "Notify by Notifications check"
                    }
                }
            }
        }
    }
}

I like this :-)
Good work @PsPsam , Thank you
Please can you run the Unit checks to ensure that the output is formatted correctly
Please can you create a PR with only those changes to the two files

PR created
I hope I did i right this time. If not let me know, git is new to me and PR is scary for me :D


hide the --tag for solution push/validate commands

Description

Hide the --tag for solution push/validate commands while it is being worked on (as part of PR #85)
Touch up the command help/examples

Type of Change

[ ] Bug Fix
[ ] New Feature
[ ] Breaking Change
[ ] Refactor
[ ] Documentation
[X] Other (please describe)

Checklist

[X] I have read the contributing guidelines
[X] Existing issues have been referenced (where applicable)
[X] I have verified this change is not present in other open pull requests
[X] Functionality is documented
[X] All code style checks pass
[ ] New code contribution is covered by automated tests
[X] All new and existing tests pass

Codecov Report

Merging #88 (f3d5fe8) into main (3d77968) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main      #88   +/-   ##
=======================================
  Coverage   32.45%   32.45%
=======================================
  Files          27       27
  Lines        3556     3556
=======================================
  Hits         1154     1154
  Misses       2312     2312
  Partials       90       90

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


⚠ Bofrost.lu has degraded performance

In 549b5e3, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 3973 ms

Resolved: Bofrost.lu performance has improved in 6360d5c after 45 minutes.


Improve README.md, instructions and first use

I'm a bit nitpicking here, but a few quick notes about the readme.

The / in the build example seems twisted:

-    .\gradlew bootRun
+    ./gradlew bootRun

The requirements should be stated, in particular that JDK 8 is required. It could be noted that JAVA_HOME must point to the correct version, when using ./gradlew. It might be noted that [a list of packages] is downloaded, which can be relevant for someone with a mobile data connection.

It would be great, if there were a few lines to what could be expected, when running ./gradlew bootRun. Before doing so I was wondering, how to use the project (i.e. I missed a "first use" example, and actually assumed the project focuses on a BitcoinJ RPC server), and then I was surprised for a moment, when I saw the rather wild messages of STOMP, until I noticed they are actually network messages. It was more obvious after the first transactions were listed.

It should be stated that bootRun connects to the P2P network.

Other than that, this is really nice! :)
Edit: just found the other gems, like http://localhost:8080/listPeers (login: admin/admin).

I love your nitpicking @dexX7 -- it shows that you care!

Should be resolved in 71397fd8596d5d4959dcec7951ae82038967633e. Closing. Let me know if I missed anything. Thanks!


[Event Request] Codeunit 5700 User Setup Manageemnt - Additional parameter to OnBeforeIsPostingDateValidWithSetup

Hello BaseApp team,
Codeunit 5700 contains an Event Publisher OnBeforeIsPostingDateValidWithSetup - thanks for this - but it is missing one important parameter namely "SetupRecordID"
Could you please add this parameter?
New Code lines:
[External] IsPostingDateValidWithSetup(PostingDate : Date;VAR SetupRecordID : RecordID) Result : Boolean
// OnBeforeIsPostingDateValidWithSetup(PostingDate,Result,IsHandled);               // Old Call
OnBeforeIsPostingDateValidWithSetup(PostingDate,SetupRecordID,Result,IsHandled);    // New Call

IF IsHandled THEN
  EXIT(Result);
.
.

Changed Publisher Event:
LOCAL [IntegrationEvent] OnBeforeIsPostingDateValidWithSetup(PostingDate : Date;VAR SetupRecordID : RecordID;VAR Result : Boolean;VAR IsHandled : Boolean)

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


fix: set root password each boot. Solve edge case for moving install or docker-compose down.

bit of a mess with commit history with how I did the last update to our fork lol, sorry 😆

That's fine I will squash them, thanks!

This resolves #4


Issue while running the demo code

Hello, I'm trying to run the Variant 1 demo with tensorflow:
python train_UGformerV1_Sup.py --dataset IMDBBINARY --batch_size 4 --ff_hidden_size 1024 --fold_idx 1 --num_neighbors 8 --num_epochs 50 --num_timesteps 4 --learning_rate 0.0005 --model_name IMDBBINARY_bs4_fold1_1024_8_idx0_4_1
However I obtain the following error:
`Traceback (most recent call last):
File "train_UGformerV1_Sup.py", line 11, in
from UGformerV1_Sup import UGformerV1
File "/content/Graph-Transformer/UGformerV1_TF/UGformerV1_Sup.py", line 2, in
import universal_transformer_modified
File "/content/Graph-Transformer/UGformerV1_TF/universal_transformer_modified.py", line 32, in
from tensor2tensor.models import transformer
File "/usr/local/lib/python3.7/dist-packages/tensor2tensor/models/init.py", line 51, in
from tensor2tensor.models.research import rl
File "/usr/local/lib/python3.7/dist-packages/tensor2tensor/models/research/rl.py", line 27, in
from tensor2tensor.envs import tic_tac_toe_env
File "/usr/local/lib/python3.7/dist-packages/tensor2tensor/envs/init.py", line 23, in
from tensor2tensor.envs import tic_tac_toe_env
File "/usr/local/lib/python3.7/dist-packages/tensor2tensor/envs/tic_tac_toe_env.py", line 244, in
register()
File "/usr/local/lib/python3.7/dist-packages/tensor2tensor/envs/tic_tac_toe_env.py", line 240, in register
"tensor2tensor.envs.tic_tac_toe_env:TicTacToeEnv", version="v0")
File "/usr/local/lib/python3.7/dist-packages/tensor2tensor/rl/gym_utils.py", line 360, in register_gym_env
return env_name, gym.make(env_name)
File "/usr/local/lib/python3.7/dist-packages/gym/envs/registration.py", line 610, in make
kwargs = spec.kwargs.copy()
AttributeError: 'NoneType' object has no attribute 'copy'
CalledProcessError                        Traceback (most recent call last)
 in
----> 1 get_ipython().run_cell_magic('bash', '', '#cd liblinear\n#cd U2GNN\ncd Graph-Transformer\ncd UGformerV1_TF\npython train_UGformerV1_Sup.py --dataset IMDBBINARY --batch_size 4 --ff_hidden_size 1024 --fold_idx 1 --num_neighbors 8 --num_epochs 50 --num_timesteps 4 --learning_rate 0.0005 --model_name IMDBBINARY_bs4_fold1_1024_8_idx0_4_1\n')
3 frames
/usr/local/lib/python3.7/dist-packages/IPython/core/interactiveshell.py in run_cell_magic(self, magic_name, line, cell)
2357             with self.builtin_trap:
2358                 args = (magic_arg_s, cell)
-> 2359                 result = fn(*args, **kwargs)
2360             return result
2361
/usr/local/lib/python3.7/dist-packages/IPython/core/magics/script.py in named_script_magic(line, cell)
140             else:
141                 line = script
--> 142             return self.shebang(line, cell)
143
144         # write a basic docstring:
 in shebang(self, line, cell)
/usr/local/lib/python3.7/dist-packages/IPython/core/magic.py in (f, *a, **k)
185     # but it's overkill for just that one bit of state.
186     def magic_deco(arg):
--> 187         call = lambda f, *a, **k: f(*a, **k)
188
189         if callable(arg):
/usr/local/lib/python3.7/dist-packages/IPython/core/magics/script.py in shebang(self, line, cell)
243             sys.stderr.flush()
244         if args.raise_error and p.returncode!=0:
--> 245             raise CalledProcessError(p.returncode, cell, output=out, stderr=err)
246
247     def _run_script(self, p, cell, to_close):
CalledProcessError: Command 'b'#cd liblinear\n#cd U2GNN\ncd Graph-Transformer\ncd UGformerV1_TF\npython train_UGformerV1_Sup.py --dataset IMDBBINARY --batch_size 4 --ff_hidden_size 1024 --fold_idx 1 --num_neighbors 8 --num_epochs 50 --num_timesteps 4 --learning_rate 0.0005 --model_name IMDBBINARY_bs4_fold1_1024_8_idx0_4_1\n'' returned non-zero exit status 1.`
I have all requirements up to date, do you have any idea how to fix it please ? I'm really interested in this repo
Thank you !

Any idea please ?

Hi, what do you mean by all requirements up to date? Did you try the code with Tensorflow 1.14, Tensor2tensor 1.13, Networkx 2.3, Scikit-learn 0.21.2?

By up to date I meant the last versions.

I implemented the UGformerV1 TF version around March 2019. Until now, there is a significance change from TF1 to TF2. That's why you could not run the code if you use TF2.

Yes I managed to solve this problem using Torch, the problem come from TF2, it's only compatible with TF1. Anyways thank you for your help !


Declarations being treated as definitions

Consider the following typescript code snippet:
interface Person {
    walk(): void;
}

class Student implements Person {
    walk(): void {
        console.log("Student walking...");
    }
}

Person.walk (line 2) is being recorded by the tool as a definition, although it doesn't have an implementation:
{
    "id": 22,
    "type": "vertex",
    "label": "range",
    "start": {
        "line": 1,
        "character": 4
    },
    "end": {
        "line": 1,
        "character": 8
    },
    "tag": {
        "type": "definition",
        "text": "walk",
        "kind": 7,
        "fullRange": {
            "start": "@{line=1; character=4}",
            "end": "@{line=1; character=17}"
        }
    }
}

This can be particularly troublesome for goto implementation, since it depends on differentiating between definitions and declarations (a declaration cannot be an implementation).
I believe the issue is related to the initializeDeclarations function and propose a check for implementation body before assigning the type of the vertex.

Actually this is interesting: the TS language server doesn't make any difference between declarations and definitions. There is also no Goto Declaration only Goto Definition when executed on something like p.walk(). The only case where the differentiation would make sense is a *.d.ts file where the definition lives in a JS file. But the TS server has not support for that either.
We can still tag this as a declaration, however the tsc lsif code should never make any decision based on the tag. It should always use the underlying TS symbol which tells the truth at the end.
I am not sure I understand why this is troublesome for Goto Implementation since it is a result set anyways and what we put in there should not depend on these tags.
Can you explain this a little ?

Thank you for explaining, I did not know there was no Goto Declaration in Typescript.
In this case, if we Goto Implementation on Person.walk(), we should only get Student.walk() as a result. However, we are passing Person.walk() to recordDeclaration, since we don't differentiate between definitions and declarations. In turn, since I add all declarations to implementation results, we have Person.walk() as part of the results, which is not correct.
A solution would be to check for a body before adding the definition/declaration to implementation results. Another would be treating them separately, even though TS makes no distinction.

I would for now check if the declaration is in an interface and  if so ignore it. I don't know what side effects it will have it we start to distinguish between declaration and definition in TS. Needs some careful thinking. I opened https://github.com/Microsoft/lsif-typescript/issues/19

Thanks for opening the issue, I will close this one for now. I will be working on a fix for that specific situation and push the changes to my open PR.


Implement generalized Pipek-Mezey

I was hoping to get generalized Pipek-Mezey localization in PySCF. Basically this boils down to replacing the Mulliken charges with something that has a basis set limit, and you can use whatever you like as different choices turn out to give very closely the same orbitals as we showed in the original paper and its followup on Pipek-Mezey Wannier functions.
The simplest way to do this is to define the atomic population matrix P^A_{ij} in terms of atomic overlap matrices S^A_{ij} = \int w_A(r) \phi_i(r) \phi_j(r) d^3 r, which can be built with the density functional routines. The simplest choice for the weights is the Becke quadrature, meaning that you can get the grid to build S^A_{ij} for an atom by modifying gen_partition to build only the grid for a single atom https://github.com/pyscf/pyscf/blob/8015c2dbdf242200368e8b29b16a784bd8ec43a8/pyscf/dft/gen_grid.py#L335
In short, the algorithm in metacode
loop over atoms A:
     form Becke grid for A only
     evaluate basis functions phi
     form atomic overlap S^A = phi * grid weight * phi.T
     store population matrix P^A = C.T * S^A * C

This is an extremely simple algorithm. However, given that there's a bunch of parameters you need to pass on to the DFT routines (radial scheme, pruning, etc) I'm not sure how to organize the code within PySCF. I'd be equally happy if someone who already knows the code would put this in.

Is it possible to adapt your proposed population matrix into the PM implementation https://github.com/pyscf/pyscf/blob/master/pyscf/lo/pipek.py#L33 ?

@sunqm I think so; the code would be something like
for A in range(natoms):
    S_A = numint.atomic_overlap(A)
    proj[A] = numpy.dot(mo_coeff.conj().T, numpy.dot(S_A, mo_coeff))

The question is just how to get the atomic overlap matrices by quadrature from the DFT code. atomic_overlap should only evaluate the grid centered on atom A.

Does atomic_overlap have a concrete boundary in real space for each atom or something like the becke grids centered on the atom with some grids sitting at the region of other atoms?

atomic_overlap is only evaluating the integral for atom A, defined by the Becke grid weighting scheme.

Oh great, you were fast. Thanks!


chore: add release cycle

Description
This PR adds a release workflow which builds the project by using the development workflow file, then releases the project and finally deploys to Vercel.
I'm not 100% sure that this is going to work well as I didn't try it and was given the code. We will need to just try it and figure out how to fix issues as we encounter them.
Related Tickets
Fixes #92

@prjctimg you will need to add Vercel tokens in the action configs:

VERCEL_ORG_ID
VERCEL_PROJECT_ID
VERCEL_TOKEN

You also need to switch Vercel deployment from auto to the CLI

So this workflow which requires VERCEL credentials is for the docs site right?

Yes

Which means the workflow file will need to leave on the documentation repository?

Oh my bad, I thought the docs were left in this repo :sweat_smile:
I need to remove the deploy task and move it to the docs then. Nice catch :+1:

So this workflow which requires VERCEL credentials is for the docs site right?

Yes

Which means the workflow file will need to leave on the documentation repository?

Oh my bad, I thought the docs were left in this repo :sweat_smile:
I need to remove the deploy task and move it to the docs then. Nice catch :+1:

@takanome-dev I sent you a collaboration request from the docs repository. Feel free to make necessary changes 👍


Replace references to numeric EPSG codes with the format EPSG:1234

Geocomputation in R recommends at section 7.2:

we recommend the more explicit AUTHORITY:CODE representation to prevent ambiguity and to provide context.

Since this affects almost all the tutorials, it will need to be implemented in the next complete update of the tutorials for January 2023.

This has now been implemented across the tutorials, but not in a single specific commit so this can now be closed manually.


Add Chinese Translation

Add Chinese translation in configuration

Hi @quanzhuo, nice contribution. I am in general in favour of adding support for languages other than English but we need to be careful how we do it, for a couple of reasons.

It needs to be done to all the UI elements not just the package.json i.e. descriptions of settings
We have no way of maintaining it, so it will inevitably end up being out of date whenever we change/add/remove settings. For example see the PR for version 3.0 https://github.com/krvajal/vscode-fortran-support/pull/293

To address the 1st point the implementation would have to look something like what the vscode-cpptools. For the 2nd point I actually have no idea how to address, any thoughts on that?

@gnikit Very considerate of you. I can't find a very convenient way to address the second point. Maybe you can set owner for each language. And only release new version after all the i18n work is done.

@gnikit Very considerate of you. I can't find a very convenient way to address the second point. Maybe you can set owner for each language. And only release new version after all the i18n work is done.

That is a bit of an issue since it will increase the development time quite substantially (currently, I am the only one actively maintaining the extension). I will see if this can be added to version 3.0. and if so I will tag you in that PR.

I will see if this can be added to version 3.0. and if so I will tag you in that PR.

If this PR is merged. And you add new settings afterwards. You can at me, I am glad to help translating it to Chinese.


OTBN loop problem

Loop statements in OTBN lead to variable execution times and occasional kDifOtbnErrBitsIllegalInsn or kDifOtbnErrBitsBadDataAddr errors (as discussed on slack).
This arose during side-channel evaluation of OTBN instructions, which requires constant-time execution so that power traces align properly. Execution time is measured by ChipWhisperer-Husky by counting the number of clock cycles that the "trigger" line is high.
The issue is seen with https://github.com/newaetech/opentitan/commit/f6ab0990bef78e315af44a8acf9a4da74cb7c300
The newae fork is required for the test application (sw/device/sca/otbn_serial.c).
The attached notebooks can be used to compile the OTBN application and observe the problem. Run test_urnd3.ipynb. Modify sca_instructions_part1_test_urnd3.s to try with or without different loops. The notebooks are written for CW-Husky + CW310 target.
Note that this is being done towards calling RND in a non-blocking, constant-time fashion, but no RND call is being made yet.
jupyter.zip

This is a bit confusing to me! I'm pretty certain that loop and loopi have deterministic runtimes. Can you explain exactly what you're seeing? It sounds like this is affected by the variable latency of RND (which OTBN has no control over).
Note that if you just want to get "randomish" behaviour and need deterministic timing, you might have more luck with reading URND which uses a local PRNG and won't block.

Oh: you should also be able to reproduce stuff in simulation with the simulator at hw/ip/otbn/dv/otbnsim/standalone.py. In particular, you mention getting illegal instruction and bad data address errors: those are hopefully just a sign of bugs in your code and are probably much easier to debug in the simulator. Add the -v command line argument to see a trace of all executed instructions.

Copy of the assembly code from jupyter.zip for easier reference:
/* Copyright lowRISC contributors. */
/* Licensed under the Apache License, Version 2.0, see LICENSE for details. */
/* SPDX-License-Identifier: Apache-2.0 */

/**
 * Standalone test for SCA measurement on instructions.
 * This is used to indirectly test whether, upon reboot, first URND call gives
 * the same number everytime or not, by wrapping the argument code to recompile_test_inst()
 * in a loop which iterates a number of time derived from URND, keeping in mind the %8 restriction.
 */

.section .text.start
.global .start
sca_instructions:

  /* Set Up Pointers */
  la       x2, test_data
  la       x3, dptr_test_data
  sw       x2, 0(x3)

  bn.lid    x4++, 0(x2)   /* w0 */
  bn.lid    x4++, 32(x2)  /* w1 */
  bn.lid    x4++, 64(x2)  /* w2 */
  bn.lid    x4++, 96(x2)  /* w3 */
  bn.lid    x4++, 128(x2) /* w4 */
  bn.lid    x4++, 160(x2) /* w5 */

  /* 3760 */

  /* pre-fetch RND value
  li x4, 0
  csrrw x0, 0x7d8, x0 */

  /* short loopi doesn't always work */
  loopi 1023, 4
      nop
      nop
      nop
      nop

  /* longer, nested loopi leads to inconsistent run time
  loopi 1023, 3
    loopi 1023, 1
        addi x4, x4, 1
    nop
  */

  /* so does a nested manual loop
  li x4, 255
  li x5, 0
  li x6, 0
  oloop:
    addi x5, x5, 1
    nop
    nop
    nop
    nop
    nop
    nop
    li x6, 0
    iloop:
        addi x6, x6, 1
        nop
        bne x4, x6, iloop
    nop
    nop
    bne x4, x5, oloop

  li x4, 0
  li x5, 0
  li x6, 0*/

  /* RND should be available now without blocking
  li        x4, 0
  csrrs x5, 0xfc0, x4
  */

  /* NOPs to allow stable powerlines */
  NOP
  NOP
  NOP
  NOP
  NOP
  NOP
  NOP
  NOP
  NOP
  NOP
  NOP
  NOP
  NOP
  NOP
  NOP
  NOP
  NOP
  NOP
  NOP
  NOP
  NOP
  NOP
  NOP
  NOP
  NOP
  NOP
  NOP
  NOP
  NOP
  NOP
  NOP
  NOP

  /* target operations follow */

Sorry, there is some missing context here which was discussed elsewhere: this is for work being done to evaluate the side-channel leakage of different OTBN instructions. For this reason we want identical start-up conditions for each power trace. Currently this means we recompile for each power trace, which is quite slow; I was looking into using RND, with pre-fetch plus a very long idle loop for constant-time execution, to avoid the recompilation step. For the problem reported here I'm not calling RND yet, I'm just trying to get a long constant-time loop.
I could try the simulator but I'm not sure I'll be able to understand much from this since I have zero knowledge of OTBN's inner workings.

Mystery solved: it turns out that what looked like variable execution time, was simply that I was reading Husky's scope.adc.trig_count (its measure of how many clock cycles the output trigger line was high for) before the OTBN application had completed. Sorry for the panic! Thanks @rswarbrick for the discussion which led me to eventually discover my mistake. Everything makes a lot more sense now.


fix(sec): upgrade admin-lte to 3.1.0

What happened？
There are 1 security vulnerabilities found in admin-lte 2.4.18

MPS-2022-13527

What did I do？
Upgrade admin-lte from 2.4.18 to 3.1.0 for vulnerability fix
What did you expect to happen？
Ideally, no insecure libs should be used.
The specification of the pull request
PR Specification from OSCS

Please do test before you submit a new pr. Admin-Lte 3.1.0 is a frontend template based on bootstrap 4, and AriaNg uses bootstrap 3.
By the way, AriaNg is a just webpage for personal use, I don't think the xss vulnerability has any impact to AriaNg.


Write ARCHITECTURE.md

Provide a general overview of the architecture for each plugin and how they interact.

High-level explanation of fp-ts usage (Reader, Tasks, etc.)
Overall flow of data and states through the lifecycle of each plugin

Aimed at providing other developers an introduction to reading and understanding the codebase to encourage contributions.

See here: https://github.com/angeloashmore/gatsby-source-prismic/blob/beta/ARCHITECTURE.md


Use GitHub Actions instead of CircleCI

@emmanuelm41 Can we remove circleci now?
please replace the badge in README.md too (we don't want to leave a broken circleci badge)

I added the release job, but I will be executed after merging, so we cannot be sure it will work. Can we do it anyway and test it? What do you think @jleni?

I am worried about leaving both GitHub and circleci as they will complete
for the release. As this app is unreleased and only in M1, there is no
problem if you need to retry a few times to confirm that GA is working
On Mon, 12 Jul 2021 at 17:31, Emmanuel @.***> wrote:

I added the release job, but I will be executed after merging, so we
cannot be sure it will work. Can we do it anyway and test it? What do you
think @jleni https://github.com/jleni?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Zondax/ledger-tezos/pull/81#issuecomment-878377732,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADIQLWH7XR6VGYPLVENBOH3TXMDE7ANCNFSM476URSUQ
.

--
Juan Leni
Managing Director
@.***
www.zondax.ch http://www.zondax.ch
.
https://www.linkedin.com/company/zondax/ https://twitter.com/_zondax_
https://github.com/Zondax/

Great. If that is the case, we can merge this PR. Remove CircleCI first!


[frameit] Fix offsets for latest Apple shots

Examples below with the new offsets and the latest Apple press shots downloaded earlier today...
Apple why can't you just keep to the same positioning :sob:

Thank you!  The tricky part here is that if we update the offsets for the new frames they'll be wrong for the old frames.  We probably need a solution to somehow determine the "version" of the frame we're using.  I'm not actively working on a solution for that right now but would be happy to discuss possible solutions for review an approach.

Hey @davidrothera, wanted to bump this issue up to see if you had a chance to see @i2amsam's feedback regarding versioning the frames in use? Thanks!

The problem that we have is that there are no version numbers in the images from Apple, the chances are that the ones that are released for each hardware revision should never change but there is no guarantee of that 😦

Hey @davidrothera, I am going to close this PR for now as we are researching a better way to handle the devices images internally. Thank you for the work though and we will update this PR when we have figured out the right move! 🚀

Was this ever solved? Currently having this problem.


notifier: clone and not reuse LabelSet in AM discovery

Not cloning and re-defining the lset variable in the Alertmanager discovery caused unpredictable behavior and made Alertmanager targets appear and reappear regularly. I noticed this using Kubernetes SD to discover Alertmanagers.
Before the fix the prometheus_notifications_alertmanagers_discovered metric looks like this. The prometheus-c-0 instance has constant number of Alertmanagers as them configured statically, whereas prometheus-b-0 fluctuates a lot and on every Kubernetes resync interval (when all the maps are re-instantiated from scratch) the Alertmangers are discovered for a short period and then get scrambled again:

I haven't been running this fix for very long but so far it seems to now be stable:

@fabxc @brian-brazil @beorn7 @juliusv @mxinden

👍
Can we check that behavior in a unit test against that function?

@fabxc done.

👍


[Test] Disable failing SILGen/newtype.swift test

Temporarily disable newtype.swift to get CI passing again.

@swift-ci please smoke test

Closing in favour of https://github.com/apple/swift/pull/39779


Can't use T.let with T.type_parameter to fix pinning error

Input
→ View on sorbet.run
# typed: true
class A
  extend T::Sig

  sig {type_parameters(:U).params(x: T.type_parameter(:U)).void}
  def pinning_error(x)
    result = nil
    [].each do
      result = x # pinning error
    end
  end

  sig {type_parameters(:U).params(x: T.type_parameter(:U)).void}
  def generics_error(x)
    # Can't fix pinning error because generics bug!
    result = T.let(nil, T.nilable(T.type_parameter(:U)))
    [].each do
      result = x
    end
  end
end

Observed output
editor.rb:16: Unspecified type parameter https://srb.help/5004
    16 |    result = T.let(nil, T.nilable(T.type_parameter(:U)))
                                                           ^^

editor.rb:9: Changing the type of a variable in a loop is not permitted https://srb.help/7001
     9 |      result = x # pinning error
                       ^
  Existing variable has type: NilClass
  Attempting to change type to: A#pinning_error#U

  Autocorrect: Use `-a` to autocorrect
    editor.rb:7: Replace with T.let(nil, T.nilable(A#pinning_error#U))
     7 |    result = nil
                     ^^^
Errors: 2

Expected behavior

The pinning error is expected.
The error when trying to use T.type_parameter in the method body is not. I'm pretty sure that type_parameters should be in scope in the method body.

Just when I run into this problem XD I need this feature too

We always parse types present in T.let with an emptySig parameter. As a result, the type parameters aren't available at this point.
https://github.com/sorbet/sorbet/blob/652e0d73a11d85a0c899f345ff9511b2354656ec/resolver/resolver.cc#L1613-L1615

An additional wrinkle is that casts are resolved during ResolveTypeMembersAndFieldsWalk, which happens before signatures have been parsed.


Mac Plus write Error - same as with piscsi

When creating a new ticket please provide information on your environment.

The Pi type: 3 B 1.2

The Pi OS version (output of 'lsb_release -a' and 'uname -a'):

pi@raspi-rascsi:/var/log $ lsb_release -a
No LSB modules are available.
Distributor ID:	Raspbian
Description:	Raspbian GNU/Linux 11 (bullseye)
Release:	11
Codename:	bullseye
pi@raspi-rascsi:/var/log $ uname -a
Linux raspi-rascsi 6.1.21-v7+ #1642 SMP Mon Apr  3 17:20:52 BST 2023 armv7l GNU/Linux

The SCSI2Pi release or git revision:

3.0.0

The computer/sampler connected to the RaSCSI/PiSCSI board:

Mac Plus 4MB, System is 6.0.8 from HD20_512-1GB-MacPlus-6+7.hda downloaded from somewhere
Describe the issue
when writing to an image the log says
Mar  3 20:10:12 raspi-rascsi s2p[852]: [2024-03-03 20:10:12.174] [warning] (ID 5) - Received 32 byte(s) in DATA OUT phase, command requires 512
Mar  3 20:10:15 raspi-rascsi s2p[852]: [2024-03-03 20:10:15.266] [warning] (ID 5) - Received 169 byte(s) in DATA OUT phase, command requires 512
Mar  3 20:10:18 raspi-rascsi s2p[852]: [2024-03-03 20:10:18.602] [warning] (ID 5) - Received 467 byte(s) in DATA OUT phase, command requires 512
Mar  3 20:10:21 raspi-rascsi s2p[852]: [2024-03-03 20:10:21.651] [warning] (ID 5) - Received 57 byte(s) in DATA OUT phase, command requires 512
same behaviour with piscsi in issue #656 ...
PiSCSI is the only device on the bus, it ran flawlessly on a Mac Classic last time I used it. That's a year ago however.
Both termination switches are on the "on" position.

@predecker That there is the same issue is not that surprising. But this ticket is most likely a duplicate, as far as I can tell. Please see https://github.com/uweseimet/scsi2pi/issues/71. Can you please check whether the work-around (source code patch) mentioned in https://github.com/uweseimet/scsi2pi/issues/71 also works for you?

@predecker One more question: Do you have any real SCSI hard drive that works with your Mac? In case you have, which drive model is it?

I applied the patch from #71, but I get a slightly different result. Copying system files (6.0.8) from floppy to the image works now, but the messages did not disappear completely:
Mar  3 22:12:40 raspi-rascsi s2p[825]: [2024-03-03 22:12:40.014] [warning] (ID 6) - Received 0 byte(s) in DATA OUT phase, command requires 512
Everytime the bytes were 0. I got four messages for about 800kB of data. The copy was good enough that the system could boot from it.
I'll do further testing tomorrow. I have to find out how to compare files.
So this is a kind of "hack" as you mentioned in the other issue and not according to the standard. I want to share my piscsi between the Mac Plus and a Classic. Do I have to switch between this hacked version and a normal one everytime I switch the Macs? Can you implement a version with a command line switch or do I have to script something to change the executables for that?

@predecker I am sorry, but I will not implement anything (also not optional) that is not compliant with the SCSI standard. It looks as if the patch in https://github.com/uweseimet/scsi2pi/issues/71 does not work for you anyway, because there are still errors reported in the DATA OUT phase.
As explained in https://github.com/uweseimet/scsi2pi/issues/71, s2p (and also piscsi as far as I can tell) only change the REQ and ACK lines during the data transfer, and they use the timing required by the SCSI specification. These are just a few lines of code and, of course, if somebody finds something wrong I would appreciate feedback. This is the respective code in bus.cpp:
int Bus::ReceiveHandShake(uint8_t *buf, int count)
{
    int bytes_received;

    DisableIRQ();

    if (target_mode) {
        for (bytes_received = 0; bytes_received < count; bytes_received++) {
            SetREQ(true);

            const bool ack = WaitSignal(PIN_ACK, true);

            WaitBusSettle();

            *buf = GetDAT();

            SetREQ(false);

            // Timeout waiting for ACK to change
            if (!ack || !WaitSignal(PIN_ACK, false)) {
                break;
            }

            buf++;
        }
    } else {

Either ACK is not set by the Mac when it should be set, so that the handshake terminates before all data have been transferred, or the Mac interrupts the transfer by raising the SCSI RST signal. This reset condition has not been logged yet. There is an issue_82 branch now which logs this condition. When you do further testing, can you please test with the issue_82 branch? This might reveal more details on what's going wrong.

@predecker One more question: Do you have any real SCSI hard drive that works with your Mac? In case you have, which drive model is it?

I have a Apple SC 20 external disk somewhere in my storage, but I don't actually know which disk is inside. I'm sure it's not 20MB, it's bigger. That enclosure worked all the time with the Mac Plus but I didn't trust the harddisk no more, so I bought the rascsi.

Moin,
I'm running on the issue_82 branch. I compiled with DEBUG=1, but I'm only seeing the same messages as with the development branch.
I'm not able to write to an image. If I boot from one with 6.0.8 the Finder crashes with different messages and the Mac freezes. I now try to format a fresh image while booting from floppy but that does not work. No freeze of the Mac.
First Aid is not able to verify, repair or initialize. Same with HD SC Setup.
Next step?

@predecker Are you running s2p on trace level? Only on trace level all releavant messages are logged. There should be either a message about the reset signal having been received, or about a handshake timeout right before the warning about the problem with the DATA OUT phase.

This block repeats every few seconds:
Mar  4 09:38:31 raspi-rascsi s2p[1860]: [2024-03-04 09:38:31.459] [trace] (ID 6) - All data transferred
Mar  4 09:38:31 raspi-rascsi s2p[1860]: [2024-03-04 09:38:31.459] [trace] (ID 6) - BUS FREE phase
Mar  4 09:38:31 raspi-rascsi s2p[1860]: [2024-03-04 09:38:31.460] [trace] (ID 6) - ++++ Starting processing for initiator ID 7
Mar  4 09:38:31 raspi-rascsi s2p[1860]: [2024-03-04 09:38:31.460] [trace] (ID 6) - SELECTION phase
Mar  4 09:38:31 raspi-rascsi s2p[1860]: [2024-03-04 09:38:31.461] [trace] (ID 6) - COMMAND phase
Mar  4 09:38:31 raspi-rascsi s2p[1860]: [2024-03-04 09:38:31.461] [debug] (ID 6) - Controller is executing WRITE(10), CDB $2a:00:00:00:00:64:00:00:01:00
Mar  4 09:38:31 raspi-rascsi s2p[1860]: [2024-03-04 09:38:31.461] [debug] (ID:LUN 6:0) - Device is executing WRITE(10) ($2a)
Mar  4 09:38:31 raspi-rascsi s2p[1860]: [2024-03-04 09:38:31.461] [trace] (ID:LUN 6:0) - READ/WRITE/VERIFY/SEEK, start sector: 100, sector count: 1
Mar  4 09:38:31 raspi-rascsi s2p[1860]: [2024-03-04 09:38:31.461] [trace] (ID 6) - DATA OUT phase
Mar  4 09:38:31 raspi-rascsi s2p[1860]: [2024-03-04 09:38:31.461] [trace] (ID 6) - Receiving 512 byte(s)
Mar  4 09:38:34 raspi-rascsi s2p[1860]: [2024-03-04 09:38:34.462] [trace] Timeout while waiting for ACK/REQ to change
Mar  4 09:38:34 raspi-rascsi s2p[1860]: [2024-03-04 09:38:34.462] [warning] (ID 6) - Received 22 byte(s) in DATA OUT phase, command requires 512
Mar  4 09:38:34 raspi-rascsi s2p[1860]: [2024-03-04 09:38:34.462] [debug] (ID 6) - ABORTED COMMAND (Sense Key $0b), DATA PHASE ERROR (ASC $4b), ASCQ $00
Mar  4 09:38:34 raspi-rascsi s2p[1860]: [2024-03-04 09:38:34.462] [trace] (ID 6) - Status phase, status is CHECK CONDITION (status code $02)
Mar  4 09:38:34 raspi-rascsi s2p[1860]: [2024-03-04 09:38:34.462] [trace] (ID 6) - Sending 1 byte(s)
Mar  4 09:38:34 raspi-rascsi s2p[1860]: [2024-03-04 09:38:34.462] [trace] (ID 6) - All data transferred
I booted from floppy. As I messed up this image in previous tests, the system is trying to initlalize the image. Took about 5 minutes to "create directory".

@predecker Your log shows that there is a timeout (> 3 s) while waiting for the ACK signal to change. You can see that 3 s elapse before the timeout is reported from the timestamps in the log.
Mar 4 09:38:31 raspi-rascsi s2p[1860]: [2024-03-04 09:38:31.461] [trace] (ID 6) - Receiving 512 byte(s)
Mar 4 09:38:34 raspi-rascsi s2p[1860]: [2024-03-04 09:38:34.462] [trace] Timeout while waiting for ACK/REQ to change
Mar 4 09:38:34 raspi-rascsi s2p[1860]: [2024-03-04 09:38:34.462] [warning] (ID 6) - Received 22 byte(s) in DATA OUT phase, command requires 512
Mar 4 09:38:34 raspi-rascsi s2p[1860]: [2024-03-04 09:38:34.462] [debug] (ID 6) - ABORTED COMMAND (Sense Key $0b), DATA PHASE ERROR (ASC $4b), ASCQ $00

With the latest issue_82 sources (from some hours ago) the log will also tell whether the error happens when wating for a signal to be set or cleared. You might want to update and re-compile your sources to also collect this piece of information.
It's the Mac that controls the ACK line during a data transfer to the board. SCSI2PI/PiSCSI just wait for this signal to change. Obviously the ACK line is not set/cleared as it should. This either means that the Mac does not handle the ACK signal correctly, or that there is a hardware issue that results in the Pi not noticing that the line status has changed. This problem is nothing that can be compensated for by software.
You mentioned in the respective PiSCSI ticket that you have an oscilloscope. It should confirm that the ACK line is in a static state for at least 3 s.

I thought I run the issue_82 version.
There must have been something wrong with my git commands ... I'm not that expert with it.
I did
git pull , that announced the issue_82 branch
git checkout issue_82
make DEBUG=1
stopped the services
sudo make install
reboot
I see the ACK line on the SCSI-side staying on a negative potential for 3 seconds on the oszilloscope. It repeats while copying files.

@predecker This means the oscilloscope confirms what we see in the logfile. I'm afraid I do not know if negative potential means whether the ACK signal is true or false. In order to get the latest sources, which report the line status waited for from the SCSI2Pi perspective, please run "git pull" and re-compile. Please shut down the service before running make install. There is no need to reboot. After make install you can just re-start the service.
Can you please also check the status of the REQ line during the 3 s SCSI2Pi is waiting for ACK to change? During the handshake the Pi manages the REQ line, while the Mac manages the ACK line.

I mixed up the pins on the connector, forget about the potentials. The ACK and REQ lines are low (0V) active. When the ACK line is low in the 3 second phase, the REQ line stays high.

This means that we are at the beginning of the handshake for a new data byte. s2p has set REQ and is waiting for ACK to be set by the Mac:
            SetREQ(true);

            const bool ack = WaitSignal(PIN_ACK, true);  <--- This results in a timeout, i.e. ACK is not set

Please correct me if I am wrong. I would like to confirm this with a logfile from the latest issue_82 branch. Can you please provide the respective log?

I don't know what I'm doing wrong, but the log looks identical to the above one to me.
Mar  4 11:04:38 raspi-rascsi s2p[2394]: [2024-03-04 11:04:38.275] [trace] (ID 6) - ++++ Starting processing for initiator ID 7
Mar  4 11:04:38 raspi-rascsi s2p[2394]: [2024-03-04 11:04:38.275] [trace] (ID 6) - SELECTION phase
Mar  4 11:04:38 raspi-rascsi s2p[2394]: [2024-03-04 11:04:38.276] [trace] (ID 6) - COMMAND phase
Mar  4 11:04:38 raspi-rascsi s2p[2394]: [2024-03-04 11:04:38.276] [debug] (ID 6) - Controller is executing WRITE(10), CDB $2a:00:00:00:10:6a:00:00:01:00
Mar  4 11:04:38 raspi-rascsi s2p[2394]: [2024-03-04 11:04:38.276] [debug] (ID:LUN 6:0) - Device is executing WRITE(10) ($2a)
Mar  4 11:04:38 raspi-rascsi s2p[2394]: [2024-03-04 11:04:38.276] [trace] (ID:LUN 6:0) - READ/WRITE/VERIFY/SEEK, start sector: 4202, sector count: 1
Mar  4 11:04:38 raspi-rascsi s2p[2394]: [2024-03-04 11:04:38.276] [trace] (ID 6) - DATA OUT phase
Mar  4 11:04:38 raspi-rascsi s2p[2394]: [2024-03-04 11:04:38.277] [trace] (ID 6) - Receiving 512 byte(s)
Mar  4 11:04:41 raspi-rascsi s2p[2394]: [2024-03-04 11:04:41.277] [trace] Timeout while waiting for ACK/REQ to change to false
Mar  4 11:04:41 raspi-rascsi s2p[2394]: [2024-03-04 11:04:41.277] [warning] (ID 6) - Received 1 byte(s) in DATA OUT phase, command requires 512
Mar  4 11:04:41 raspi-rascsi s2p[2394]: [2024-03-04 11:04:41.277] [debug] (ID 6) - ABORTED COMMAND (Sense Key $0b), DATA PHASE ERROR (ASC $4b), ASCQ $00
Mar  4 11:04:41 raspi-rascsi s2p[2394]: [2024-03-04 11:04:41.277] [trace] (ID 6) - Status phase, status is CHECK CONDITION (status code $02)
Mar  4 11:04:41 raspi-rascsi s2p[2394]: [2024-03-04 11:04:41.277] [trace] (ID 6) - Sending 1 byte(s)
Mar  4 11:04:41 raspi-rascsi s2p[2394]: [2024-03-04 11:04:41.277] [trace] (ID 6) - All data transferred
Mar  4 11:04:41 raspi-rascsi s2p[2394]: [2024-03-04 11:04:41.277] [trace] (ID 6) - MESSAGE IN phase
Mar  4 11:04:41 raspi-rascsi s2p[2394]: [2024-03-04 11:04:41.277] [trace] (ID 6) - Sending 1 byte(s)
Mar  4 11:04:41 raspi-rascsi s2p[2394]: [2024-03-04 11:04:41.278] [trace] (ID 6) - All data transferred
Mar  4 11:04:41 raspi-rascsi s2p[2394]: [2024-03-04 11:04:41.278] [trace] (ID 6) - BUS FREE phase
pi@raspi-rascsi:~/scsi2pi $ git status
Auf Branch issue_82
Ihr Branch ist auf demselben Stand wie 'origin/issue_82'.
 Soll ich die rausnehmen?

sorry, wrong language ... :-/

:-)
Yes, it is important to remove the changes from #71 and use the unmodified issue_82 branch. Please run these commands:
git reset --hard
git pull
git log -n 1

The commit ID displayed should be 08b33728628c02e81b2781c1fb8e1416cd0ad306. If this is the case, please recompile.

Mar  4 12:57:20 raspi-rascsi s2p[3094]: [2024-03-04 12:57:20.745] [trace] (ID 6) - ++++ Starting processing for initiator ID 7
Mar  4 12:57:20 raspi-rascsi s2p[3094]: [2024-03-04 12:57:20.745] [trace] (ID 6) - SELECTION phase
Mar  4 12:57:20 raspi-rascsi s2p[3094]: [2024-03-04 12:57:20.745] [trace] (ID 6) - COMMAND phase
Mar  4 12:57:20 raspi-rascsi s2p[3094]: [2024-03-04 12:57:20.746] [debug] (ID 6) - Controller is executing WRITE(10), CDB $2a:00:00:00:00:64:00:00:01:00
Mar  4 12:57:20 raspi-rascsi s2p[3094]: [2024-03-04 12:57:20.746] [debug] (ID:LUN 6:0) - Device is executing WRITE(10) ($2a)
Mar  4 12:57:20 raspi-rascsi s2p[3094]: [2024-03-04 12:57:20.746] [trace] (ID:LUN 6:0) - READ/WRITE/VERIFY/SEEK, start sector: 100, sector count: 1
Mar  4 12:57:20 raspi-rascsi s2p[3094]: [2024-03-04 12:57:20.746] [trace] (ID 6) - DATA OUT phase
Mar  4 12:57:20 raspi-rascsi s2p[3094]: [2024-03-04 12:57:20.746] [trace] (ID 6) - Receiving 512 byte(s)
Mar  4 12:57:23 raspi-rascsi s2p[3094]: [2024-03-04 12:57:23.747] [trace] Timeout while waiting for ACK/REQ to change to false
Mar  4 12:57:23 raspi-rascsi s2p[3094]: [2024-03-04 12:57:23.747] [warning] (ID 6) - Received 275 byte(s) in DATA OUT phase, command requires 512
Mar  4 12:57:23 raspi-rascsi s2p[3094]: [2024-03-04 12:57:23.747] [debug] (ID 6) - ABORTED COMMAND (Sense Key $0b), DATA PHASE ERROR (ASC $4b), ASCQ $00
Mar  4 12:57:23 raspi-rascsi s2p[3094]: [2024-03-04 12:57:23.747] [trace] (ID 6) - Status phase, status is CHECK CONDITION (status code $02)
Mar  4 12:57:23 raspi-rascsi s2p[3094]: [2024-03-04 12:57:23.747] [trace] (ID 6) - Sending 1 byte(s)
Mar  4 12:57:23 raspi-rascsi s2p[3094]: [2024-03-04 12:57:23.747] [trace] (ID 6) - All data transferred
Mar  4 12:57:23 raspi-rascsi s2p[3094]: [2024-03-04 12:57:23.747] [trace] (ID 6) - MESSAGE IN phase
Mar  4 12:57:23 raspi-rascsi s2p[3094]: [2024-03-04 12:57:23.747] [trace] (ID 6) - Sending 1 byte(s)
Mar  4 12:57:23 raspi-rascsi s2p[3094]: [2024-03-04 12:57:23.748] [trace] (ID 6) - All data transferred
Mar  4 12:57:23 raspi-rascsi s2p[3094]: [2024-03-04 12:57:23.748] [trace] (ID 6) - BUS FREE phase
I see on the oszilloscope that the after some handshake (and transmission I think) the ACK line suddenly drops to low and stays there without any REQ. The ACK pulse (answer to the last REQ) before this drop however is very short compared to the other (normal) pulses. Is there a minimum pulse length defined? I try to add a screenshot from the oszilloscope.

No need for a screenshot.  There is no minimum pulse length. ACK has to stay asserted until REQ has been released by the target.

I am not an eletronics expert, but is it completely impossible that there is a termination issue. Regarding the Mac Plus I found this:
Power for termination resistors is not provided at the SCSI connector nor is a
termination resistor provided in the Macintosh Plus SCSI circuitry.

Impossible to see a difference between SC20 and s2p. SC20 simply works and there is no 3 second down of the ACK signal.
Is there any chance to do debugging of traffic between Mac and SC20 via the raspberry? With the oszilloscope I see non related behaviour between REQ and ACK. ACK goes up and down while REQ is constant. It seems to react to something else. Busy maybe?
I switched to a Mac Classic and that works also flawlessly. I'm unable to catch a situation comparable to the one with the Mac Plus.

Maybe you can monitor the traffice with the scsimon tool (part of PiSCSI). But I am not sure, I have never used this tool. During the REQ/ACK handshake any other signals remain unchanged, at least s2p/piscsi do not change them.
Isn't it interesting that there only seems to be an issue with the Mac Plus? I wonder whether there is something special with the SC20. Maybe Apple added something vendor-specific to it like they did with other drives. Does the SC20 work with the Mac Classic?

The Classic complained about missing drivers on the SC20 and wanted the "Aktualisierer" to run.
Actually the Mac is connected to the SC20 (powered off) and to the raspberry. Maybe that messes up the signals.

I opened the 20SC (not SC20, I'm wrong the whole time). It's completely passive. Only a power supply and a fan. Cabling is from the outside connectors to the disk without further electronics.

I did not think of Apple modifying the drive electronics but the firmware. Like they did for other drives (hard drives and CD-ROM drives) in order to force users to purchase expensive Apple drives instead cheaper standard drives.

I don't think so. In my 20SC is a random Maxtor 200MB disk and I used the enclosure to connect other disks as well.

Then at least with your setup there does not seem to be anything Apple-specific. With other setups there is, and this is why s2p/piscsi have a custom Apple mode page. Without this mode page some Apple software/drivers do not work because they expect drives with Apple-specific firmware.

I'm actually trying a different approach. As everone is telling Silverlining drivers are the best for the Plus I prepare an image with that driver with the Classic. I messed up my main image which worked last year, so I have to rebuild it anyway.

Good luck, please provide feedback when you have tried the other drivers.

Good morning.
We are not fighting the Mac Plus, we are fighting the Mac Plus with drivers other than from Silver Lining.
As long as there are only images initialized with Silver Lining on the bus, everything works fine with the Plus. If there is only one image with another driver, the Plus does not boot. Sometimes it plays strange noise, as reported elsewhere with the Lido driver.
A PiSCSI formatted image with "Apple+Speedtools" does not work either.
A partition table of a PiSCSI created and with Silver Lining formatted image looks like this (notice the 2nd partition name "Macintosh_SL":
`pi@raspi-rascsi:~/images $ hfdisk -l testdrei.hda
testdrei.hda
#                    type name                length   base    ( size )  system
testdrei.hda1     Apple_partition_map Apple                   63 @ 1       ( 31.5k)  Partition map
testdrei.hda2            Apple_Driver Macintosh_SL            32 @ 64      ( 16.0k)  Driver
testdrei.hda3               Apple_HFS testdrei             20200 @ 96      (  9.9M)  HFS
testdrei.hda4              Apple_Free Extra                  168 @ 20296   ( 84.0k)  Free space
Block size=512, Number of Blocks=20464
DeviceType=0x1, DeviceId=0x1
Drivers-
1: @ 64 for 11, type=0x1`

Well, I'm afraid from the Pi software perspective I don't see anything that can be done. The analysis has shown that the ACK signal is not set by the Mac Plus, at least not by some drivers, when it has to be. The reason for this is unkonwn, but whatever the reason, the software on the Pi cannot compensate for wrong signals on the bus.
This is why I tend to say tickets related to this issue should be closed because SCSI2Pi/PiSCSI cannot resolve this. The only thing that can probably be done is to recommend drivers for the Mac Plus that do not trigger this problem and avoid those that do. This could be done on the PiSCSI Wiki, for instance, because it contains information valid for both PISCSi and SCSI2Pi.

Sounds good. Thanks for your time.

Thank you for doing all these tests. Even though is no resolution for everything, the actual cause of the problem has become much clearer.


Service 'mysql' failed to build on fresh install

Info:
Docker version 1.12.6, build 78d1802

Laradock commit: 586a225c117aa449a9840332f1979b6ccdfba2da
System info: Linux
System info disto/version: Ubuntu 16.04

Issue:
Building mysql
Step 1 : ARG MYSQL_VERSION=8.0
ERROR: Service 'mysql' failed to build: Please provide a source image with from prior to commit
Reproduce:
docker-compose up -d nginx mysql

I am also facing the same issue while yesterday it was working too.

Just I get it working by upgrading the docker version.

Yep, needed to update docker and now it works:
https://docs.docker.com/engine/installation/linux/docker-ce/ubuntu/

@shukebeta Should I use Docker CE?


Supply Chain Security Validation / CodeQL Scanning fails for JVM 17

When using Kotlin targeting JVM 17:
  [2022-06-15 18:25:32] [autobuild] > Task :compileKotlin
  [2022-06-15 18:25:33] [autobuild] > Task :compileJava FAILED
  [2022-06-15 18:25:33] [autobuild] FAILURE: Build failed with an exception.
  [2022-06-15 18:25:33] [autobuild] * What went wrong:
  [2022-06-15 18:25:33] [autobuild] Execution failed for task ':compileJava'.
  [2022-06-15 18:25:33] [autobuild] > error: invalid source release: 17

See full output here: https://github.com/coopnorge/sapcrm-profile-data/runs/6905823342?check_suite_focus=true#step:5:73

I'm going to disable security scanning for repos on which this breaks if nobody is looking at it @coopnorge/github-security-managers @coopnorge/security-guild

I think we can use a similar solution to coopnorge/github-workflow-supply-chain-security-validation#41


setStartTime does not properly work

Hello! Great library!
So, setStartTime() doesn't work currently. It's not fast-forwarding my particles.
I looked into the issue, and it seems to come from updateParticlesBeforeStartTime() being broken. setStartTime() takes a long, and directly sets it to mCurrentTime. mCurrentTime is the current time in milliseconds. And yet, on line 721 in updateParticlesBeforeStartTime(), there's this line:
long currentTimeInMs = mCurrentTime / 1000;

The variable currentTimeInMs is actually the time in seconds! This means that the particles are not properly updated before it starts when you use setStartTime(). If you have something like setStartTime(4000) with a particle rate of 5, there won't be any initial frames since framesCount will be 0, when there should be a lot of initial frames.
What's worse is that the function updateParticlesBeforeStartTime() is private, and it's called from a private function. If you made these functions protected, I could at least subclass the ParticleSystem class to fix this. But as it is, there's no real workaround. So maybe functions like these should be protected instead of private?
My current workaround is that I copied over both ParticleSystem and ParticleField to my project and replaced the updateParticlesBeforeStartTime() function with:
private void updateParticlesBeforeStartTime(int particlesPerSecond) {
    if (particlesPerSecond == 0) {
        return;
    }
    if (mCurrentTime == 0) {
        return;
    }
    for (int i = 0; i <= mCurrentTime; i += 100) {
        onUpdate(i);
    }
}

And now the setStartTime(3000) properly fast-forwards the particles 3 seconds. Obviously the framerate of 10 was chosen arbitrarily and can be fixed, but it suits my purposes. Maybe it can be an optional parameter for setStartTime()?
Anyway, hope this helps.
Thanks!

Thanks for the report.
I recall that method was added from a pull request and it looked fine when I reviewed it, but it may have been broken as a side effect of other changes.
I'll see if I can add this fix in the near future.


Additional Data File Import for DIVE Desktop

This would be an additional file added to the DIVE Desktop when importing data.  It would be an optional file that can be loaded into the system.
This file would then be added as an additional input when running pipelines (I assume it provides some additional context about information).
./platform/desktop/frontend/components/ImportDialog.vue - In here we would add an optional File that can be uploaded along with the existing media, annotation, metadata files.  I'll ask in a comment below for some more information.
./client/dive-common/apispec.ts - Update the openFromDisk to have a new datasetType, which can be the new file type.
You then need to update in the ./client/platform/desktop/forntend/api.ts - the openFromDisk to handle the new file type.
Probably want to add this additional data file to the DIVE meta.json  file.  You can find examples in ~/VIAME_DATA/DIVE_Projects folder the meta.json file.  So add some property to this that can be used to indicate the location of this file.
If you look in ./client/platform/desktop/backend/native/viame.ts you can find were a new command is for the calibration file.  A similar type of input will be needed for this new file it happens to exists.

@mattdawkins

What should be a user face name for this additional File (Metadata file is already taken for DIVE Metadata)?
Is there an example pipeline that incorporates this new data and can you point to it?  Ideally we would like to know the input command for the pipeline to add this new file as an input
Can you provide some sample data to run this pipeline to make sure it gets the proper results?

What should be a user face name for this additional File

Camera file is fine, though I think in the userface it should be listed as camera / metadata file since for some use cases this will be a metadata file and in some a camera file

Is there an example pipeline that incorporates this new data and can you point to it?

Currently only pipelines like this exist for stereo data, though we're making a monocular one in the near future which takes in one of the .json files files I've shared with you (Note some of these files are not public and shouldn't be attached here)


[Enhancement] : Start the song midway in editor mode

What is your suggestion, and why should it be implemented?
So the title might be a bit confusing but what I'm asking is:
To be able to play the song at any point during it, for exemple, start at 30s so I don't need to wait 30s before playing the part I want to test
This would help making charts easier to do since a 5-6min song can start to be annoying to test since you need to wait quite a lot to see if the charting is ok or not. Also things like scroll speed changes, bpm changes or mini-cutscenes that cannot be viewed while simply listening to the song would be easier and faster to fix
Overall a Quality of Life enhancement that would be useful to pretty much everyone

Wtf is this, that is kinda bs, not gonna lie... how the hell is it stale after only 10 (and not 7) days... a month, ok, but 10 days?!


Using UIInputView

Awesome library! Have you considered subclassing from UIInputView?

Hi Colin
I haven't thought about it.
You can try it and send me a pull request!
Date: Mon, 20 Apr 2015 00:02:30 -0700
From<EMAIL_ADDRESS>To<EMAIL_ADDRESS>Subject: [YZKeyboardInputAccessoryView] Using UIInputView (#1)
Awesome library! Have you considered subclassing from UIInputView?
—
Reply to this email directly or view it on GitHub.


Initial implementation

https://github.com/stolostron/backlog/issues/19171

/cc @jamestalton This is essentially a copy of console-chart for the MCE dynamic plugin, with everything not relevant to the plugin removed.

/cc @Randy424 @chenz4027

/hold

/unhold


Upgrade Sonar to Java 17

Hi @lgranie,
Apologies for delayed responses in the PR's. I will merge this one straight away and have a look at the other PR this week.
Thanks for your contributions. It is greatly appreciated :-)


Update quickstart-hybrid-aad.md

Corrected "Bitlocker" typo.
Summarize the change in the pull request title
Describe your change, specifically why you think it's needed.
Fixes #Issue_Number (if necessary)

@cliffhobbs : Thanks for your contribution! The author, @aczechowski, has been notified to review your proposed change.

Editorial fix confirmed.


ci: commitlint on actions

What did you fix?
N/A
commitlint on PR & before attempting to release, help avoid release issues from message resolution

Reproduction steps

Evidence/screenshot/link to line

Considerations

Does this contain a new dependency? [No]
Does this introduce opinionated data formatting or manual data entry? [No]
Does this pr include updated data files in a separate commit that can be reverted for a clean code-only pr? [No]
Have I run the linter? [Yes]
Is is a bug fix, feature request, or enhancement? [Maintenance]

:tada: This PR is included in version 5.0.0 :tada:
The release is available on:

v5.0.0
GitHub release

Your semantic-release bot :package::rocket:


Concatenation operation in InputTransition causing confusion and memory abuse

As described in #01, the Concatenation operation in InputTransition has not been fix. Note that this could cause confusion in training, as the data should be of size() [Batchsize, Channel, Xsize, Ysize, Zsize] and the output to softmax should be of size() [Batchsize, Classnum, Xsize, Ysize, Zsize].
But as the broadcasting between [Batchsize16, XChannel, Xsize, Ysize, Zsize],  [Batchsize, XChannel16, Xsize, Ysize, Zsize] bring [Batchsize16, XChannel16, Xsize, Ysize, Zsize], all the following layers would have 16 times more batchsize.
Mathematically this could be offset by running a lot of epochs, but could also make device suffers from memory issue. And each batch is equivalent to 16 un-shuffled batch.

Thanks #1 ! I was confused for this problem! Now, my thoughts is right!


Make multi-threaded Evaluate(.) easier to interrupt

This gist seems like a great approach.
https://gist.github.com/mrdrozdov/832cce1dd7d5830e66898486712fdea5

closed by https://github.com/stanfordnlp/dspy/pull/981?


Establish linting rules to use across the project

Overview
We need to set up linters for maintaining consistent and readable code throughout the project.
Action Items

[x] Discuss with team which linting technologies & rules to implement.
[x] Publish rules.
[ ] Update documentation to include instructions on how to run linting.

Resources/Instructions
Code Climate
ESLint
Prettier

@shinjonathan Dennis and I noticed that when codeclimate was installed as a linter in vscode that it didn't generate the errors that we see with the PR for the same page.  It would be good for us to have a way for developers to take care of issues before the PR if possible.

@mealthebear please update progress

Update for Thursday, November 12th 2020:

Progress: I finished setting up all the rules so far that we may need in the ESLint file. Now all that's left to do is clean up the code in the other files of the repo so they pass ESLint and Code Climate.
Blockers: None at the moment
Availability: I'll be busy until this Saturday
ETA: 1 week or less to get these changes merged

@mealthebear I searched the readme and the wiki and didn't see any reference to linting.  Please make sure that there are instructions on what we use, how and where to install it, in the appropriate files.  Then this issue can be closed.

@mealthebear I searched the readme and the wiki and didn't see any reference to linting.  Please make sure that there are instructions on what we use, how and where to install it, in the appropriate files.  Then this issue can be closed.

Progress: None
Blocks: None
Availability: 2-3 hours
ETA: 1/7

Progress: None
Blocks: None
Availability: 2-3 hours
ETA: 1/7

PR #203 might be sufficient instructions to close this. It wasn't my issue, but I hopped in. Hope that's okay!

@mealthebear I searched the readme and the wiki and didn't see any reference to linting. Please make sure that there are instructions on what we use, how and where to install it, in the appropriate files. Then this issue can be closed.

PR #203 might be sufficient instructions to close this. It wasn't my issue, but I hopped in. Hope that's okay!

@mealthebear I searched the readme and the wiki and didn't see any reference to linting. Please make sure that there are instructions on what we use, how and where to install it, in the appropriate files. Then this issue can be closed.


Admin user lost when reinstall a HA rancher on K3S

Hi,all
I installed a HA rancher on a K3S cluster with helm.
And I used system-tools to remove it with "system-tools remove --kubeconfig=xxx" by some reson.
Everything was ok, except the namespaces "cattle-system, local,  and some 'p-xxxx'" were in status "Terminating", and I solved to delete them with "k3s kubectl edit namespaces xxxx" and modifed "finalizers" field.
Then, I reinstall rancher with helm.
But when it setted up, I could not login with "admin user".
I suppose to change the admin's password

KUBECONFIG=/etc/rancher/k3s/k3s.yaml
k3s kubectl --kubeconfig $KUBECONFIG -n cattle-system exec $(kubectl --kubeconfig $KUBECONFIG -n cattle-system get pods -l app=rancher | grep '1/1' | head -1 | awk '{ print $1 }') -- reset-password

it shows:
W1126 09:18:36.297686     168 client_config.go:552] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
0 users were found with authz.management.cattle.io/bootstrapping=admin-user label. They are []. Can only reset the default admin password when there is exactly one user with this label.
command terminated with exit code 1

and I used command:

k3s kubectl get users -l authz.management.cattle.io/bootstrapping=admin-user -o json

I got empty user items:
[root@k3s01 ~]# k3s kubectl get users -l authz.management.cattle.io/bootstrapping=admin-user -o json
{
    "apiVersion": "v1",
    "items": [],
    "kind": "List",
    "metadata": {
        "resourceVersion": "",
        "selfLink": ""
    }
}

what I missed? need help!


Can we open popover on the top of textbox when not enough space at the bottom side

I am using supperselectfield inside the table row I am facing problem at the last row when opening drop-down it get hidden behind of my container. same if I check Material UI select it get open at the top when not enough space at the bottom side can we implement same here.

Any Suggestions.. ?

Hi,
I observed that, "canAutoPosition" property of Popover is set to false, because of which popover is not being positioned on top.
can you expose this property?

Can you tell me if the version on branch fix/#41-canAutoPosition works for you ?

Can you tell me if the version1.5.6 works for you ?

Hey, thanks for the fix. It's working


BigQuery: to_dataframe function not working

python: 3.6.3
google-cloud: 0.32.0
when I am trying to run a code based on this test (https://github.com/GoogleCloudPlatform/google-cloud-python/blob/017714cf91a310caafc60181c044d7812c7226b7/bigquery/tests/system.py#L1259) on my side, I am getting the error:
'HTTPIterator' object has no attribute 'to_dataframe'

function call that I am using
df = client.query(query).result().to_dataframe()

Hello,
I tried running that code and I get these objects.  It seems to me google cloud gives the latest google-cloud-bigquery, but what is your version of google-cloud-bigquery?
(Pdb) p Config.CLIENT.query(QUERY).result()
<google.cloud.bigquery.table.RowIterator object at 0x7f81c41869e8>
(Pdb) p Config.CLIENT.query(QUERY)
<google.cloud.bigquery.job.QueryJob object at 0x7f81cab50c88>
(Pdb) p Config.CLIENT
<google.cloud.bigquery.client.Client object at 0x7f81c4186710>
(Pdb) p Config
<class 'tests.system.Config'>

From looking through the code, it does seem like that each of those return those objects and it should return a RowIterator.  I believe that you might be running an older version of BigQuery.

My sample code:
def get_result_dataframe(query):
    try:
        df = client.query(query).result().to_dataframe()
        return df
    except Exception as e:
        print('Error:', e)

print(get_result_dataframe('SELECT sum(attendance), startTime  FROM `bigquery-public-data.baseball.schedules` group by startTime'))

Run log:
Error: 'HTTPIterator' object has no attribute 'to_dataframe'
None

Package info:
$ pip show google-cloud
Name: google-cloud
Version: 0.32.0
Summary: API Client library for Google Cloud
Home-page: https://github.com/GoogleCloudPlatform/google-cloud-python
Author: Google Cloud Platform
Author-email<EMAIL_ADDRESS>License: Apache 2.0
Location: /Users/Vikram/anaconda3/lib/python3.6/site-packages
Requires: google-cloud-spanner, google-cloud-translate, google-cloud-logging, google-api-core, google-cloud-monitoring, google-cloud-datastore, google-cloud-pubsub, google-cloud-vision, google-cloud-dns, google-cloud-runtimeconfig, google-cloud-firestore, google-cloud-error-reporting, google-cloud-bigquery, google-cloud-bigtable, google-cloud-language, google-cloud-container, google-cloud-videointelligence, google-cloud-trace, google-cloud-storage, google-cloud-speech, google-cloud-resource-manager, google-cloud-bigquery-datatransfer, google-cloud-core

OS: OSX 10.13.1


Make vectors trivially relocatable.

Hello,
I'm sorry for making the same issue three times.
I made Vec2, Vec3 and Vec4 trivially relocatable.
I didn't change the behavior of them.
Could you please merge this PR?

@AlexMWells Sorry to drag you into this, but I know that in the past you have gone super deep on how tweaks to these classes can help or inhibit vectorization in loops. Is there anything here that would concern you?

Historically with vectorizing compilers, a data type can have its members turned into scalars with a "scalar replacement of aggregates" optimization pass.  Once a data type has become scalars, its members can live in registers vs. being forced to standard data layout and being kept on the stack.  This is important to minimize the movement between stack and registers when vectorizing as that is when an AOS/SOA transformation might be required and generate extra instructions.  One thing that can disqualify SROA is passing the address of the structure to a function call, as that would require the standard data layout and the object exist on the stack vs registers.
Now the wrinkle is the "default" copy constructor and possibly other default operators is that a compiler could implement a memcpy(*this, &src, sizeof(T).  And the taking the address of "src" could disqualify SROA and end up forcing it to exist on the stack in standard data layout.
Perhaps another optimization pass would convert the memcpy to assignments before SROA is applied, but those can often be specialized (just for 2 or 3 data members in a specific pattern).  So defensive programming technique was to explicitly provide those constructors and operators with member-wise assignment/copies vs. letting the default possibly use memcpy/memset.
Now fast forward many years and std::is_trivially_copyable was introduced in c++11 and then compilers/libraries start adding it to memcpy and other places with warnings, etc.
In short I think you might want to keep both ways of having those default or not controllable by a define.

I fixed codes following a advice, but an assertion failed.
The reason seems that Vec2::normalized returns a wrong Vec2.

I fixed codes following a advice, but an assertion error occured. One of the causes seems that return Vec2 (x / l, y / l) in Vec2::normalized behaves strangely. Unfortunately, I couldn't fix it.

I found that only changing copy constructor from user-defined to default caused an assertion error, so I give up making Vec3 trivially relocatable.
Thank you vary much!

Here is the summary as I understand it:
Using =default makes it trivially moveable, and that might have a number of advantages for the vast majority of users.
But there are a few specialized situations where it could sabotage certain auto-vectorization cases. Those situations can be locally fixed if there's a way to include the header files in such a way that it doesn't use the =default versions in a module-local way (say, by defining a symbol before including the Imath header). OSL is one of these. If Imath itself does not allow this, we might have to do something even uglier like replicate the Imath headers inside OSL and modify them to allow it.

I'm sorry, but what is OSL?

Open Shading Language

Thank you!

We discussed this in today's technical steering committee meeting. We support this addition in principle, the ultimate objective seems sound, but we're concerned about adding additional complexity through another batch of #if's in the code without a thorough analysis of the benefits. As @AlexMWells points out, the actual performance impact is complicated to assess for all cases.
@sukeya, can you describe more about the motivation for the change? Was this motivated by a specific use case? Did you do a performance analysis that quantifies the impact?
We also discussed briefly whether the same objective could be achieved by adding the trivially_relocatable attribute to the class definition itself, rather than adding new class methods.
We are planning a v3.2 release in mid-August, which will be cut from the main branch, so we'd like to wait until after that before merging the PR. That will provide more time for evaluation before official release.
Thanks for the contribution and thanks for your patience.

I see. I will do a performance analysis.
I talk about the motivation for the change. I have been writing a snow simulator which reads polygon meshes from an Alembic file exported by Blender. I think that the exported file generally stores a pair of a transform matrix (Imath::M44f) and a polygon mesh (each type of a point and a normal are std::vector<Imath::V3f>) at each time, so I have to calculate the transformed polygon mesh from them. However, my simulator will heavily use CPU, so I would like to assign this task to GPU asynchronously.
Thank you.

Adding the trivially_relocatable attribute seems good for me.

I have done a performance analysis. The result is the following:

GPU

Test case
Avg time [ms]
Branch name in my forked repository

user defined
175
make_vector_trivially_relocatable_performance_test

default
120
defalut_ver

default and async
118
async_ver

CPU

Test case
Avg time [ms]
Branch name

user defined
24
tbb_ver

default
22.5
tbb_defalut_ver

The environment is the following:

OS
Ubuntu 22.04

CPU
Intel Core i7 8700

GPU
NVIDIA GeForce RTX 2060 (12GB)

Memory
DDR4-2666 32GB

Compiler
GCC 12.1.0

The programs needs oneTBB(2021.5.0 or higher) and CUDA(12.2), and must be cloned recursively.
I didn't calculate the deviation of each test case, but felt that each sample in the test cases using CPU and default and async test case using GPU is in a range [0.95 * avg, 1.05 * avg].

Can you clarify what exactly is the difference between "default" and "user defined"?

I see.
"defalut" means that the following functions of vectors are declared as default:

move constructors or move assignment operators,
copy constructors or copy assignment operators.

"user defined" means that vectors use current implementation of said functions.

The performance difference on GPU is striking.

@lgritz Since you & I debated it earlier in this thread, a half year ago, and pursuant to @Quuxplusone's comments, I'm still of the opinion that we shouldn't guard default with IMATH_VEC_USE_DEFAULT_CONSTRUCTOR. Since we last discussed this PR we've mostly collectively moved forward to C++17, and I just point that out in a spirit of moving forward with language features, and not keeping the old business around.

@meshula Do we not still have the problems that @AlexMWells detailed, where the = default might derail certain vectorization that we rely on? Making sure we could selectively have it the way that's better for vectorization was the point of suggesting the guard in the first place. That's unrelated to C++17.

The website check failed because of a change in required versions at readthedocs. This is fixed in the main branch. @sukeya , could you possibly merge the main branch with yours to pick up those fixes?

@Quuxplusone and @sukeya, I need some more time to refresh my understanding of the proposal, but I think the consensus is it's headed in the right direction.
We'd ideally like to have an analysis like @AlexMWells describes above. Some of the current constructs were set in place after such a careful expert analysis, although that was a long time ago with different compilers. It's definitely worth modernizing, but also good to confirm there aren't unintended consequences.

Sorry to be a pest on this one, but I've been looking at some old optimizations recently with respect to classic tricks such as shortcutting boolean operations' logic by turning boolean expressions into arithmetic expressions (this is not in OpenEXR but in other projects I work on). They made an obvious difference when they were written for vfxplatforms that we no longer support, but godbolt definitively shows that the old tricks generate identical code to the "unoptimized" version. In this thread's topic, I'd be convinced by a godbolt hunk that demonstrates the vectorization goodness, and another demonstrating it going away when default is introduced.
I'm very much a "less is more" person, and rely prefer a simple solution that's obviously correct. If we just have =default, and can't demonstrate a pessimization, then to me the ifdef is technical debt that we'll have to revisit every time we speculate about the state of compilers.
I did hit an Imath performance issue not that long ago, but it wasn't the case that any nicety on the part of Imath would improve things. I had to reengineer an entire processing algorithm to use simd intrinsics to get the 16x speed up that was needed. A couple of percent wouldn't have helped in the slightest. Outside of that real-time image processing case, I can not recall any other case in a literal decade where Imath was measurable in a profile.
I think @sukeya's profile showed default is faster on that small set of cases? so I'm looking for a counter example where Imath falls of a cliff. I hear what you are all saying and I see what @AlexMWells is saying last July, but I would really love to see something quantitative.
As I mentioned earlier, I really don't like configuring the Imath headers via preprocessor because it means you can easily have two subtly different versions of Imath including depending on whether a particular compilation unit happens to hit the same witches brew of preprocessor directives as every other compilation unit. I'd be less adamant over the years if I hadn't personally spent way too many days of my life helping people debug whether or not they had OPENEXR_DLL properly defined.
I realize I expending way too much energy on a trivial change, but somehow this tiny thing is stuck in my mind as something that will bug me if we only speculate and don't measure.

@Quuxplusone and @sukeya, I need some more time to refresh my understanding of the proposal, but I think the consensus is it's headed in the right direction.
We'd ideally like to have an analysis like @AlexMWells describes above. Some of the current constructs were set in place after such a careful expert analysis, although that was a long time ago with different compilers. It's definitely worth modernizing, but also good to confirm there aren't unintended consequences.

FWIW, I believe I see now the scenario that @AlexMWells is worried about: Imagine a compiler that does escape analysis after inlining, and also optimizes a trivial constructor into memcpy, and also its escape analysis does not understand the semantics of memcpy (i.e. that its pointer arguments do not escape). Then we'd have this: https://godbolt.org/z/YjKcd1Pf1 Notice that Clang optimizes the return; but if you change memcpy to not_memcpy, it stops optimizing. This indicates that Clang's escape analysis does understand that memcpy is special and doesn't escape its arguments. Of the compilers on Godbolt, it looks to me like GCC 4.1.2 doesn't understand memcpy but GCC 4.4.7+ do. All Godbolt-available versions of Clang (3+) and MSVC (19.14+) understand memcpy.
I don't understand precisely how this kind of thing would interact with vectorization, but based on these observations I'd be surprised if memcpy interacted poorly with anything (in a recent enough compiler).
I know another surprising pitfall where if a library skips running a trivial (pseudo-)destructor, lifetime analysis might not realize the object is dead; but my test case for that got fixed in GCC 11, and only ever happened on GCC AFAIK anyway. I bring it up merely as another case where making something more trivial can cause worse performance — but I'm quite confident that I wouldn't let that case stop me from making anything more trivial.
Anyway, my main contribution to this PR is to say that "trivially relocatable" should just be "trivial" everywhere it appears in this PR; and to invite people interested in relocatability to comment in support of the Clang implementation https://github.com/llvm/llvm-project/pull/84621 . :)


add command line option to read JSON vector file and process as if it…

… came from server
Should have thought of this sooner :(
Should help with the GCM-SIV stuff as well as testing on ASA
Best used with --verbose mode on

So is this intended to be run in something like gdb, and then inspect the fields after they have run through the "process" step by the crypto module?