undefined method `index' for #Devise::SessionsController:0x007f80c6486c48

I've never seen an error like this for Devise 4.2.1 And I can't find SessionsController in the source code for the gem.
activesupport (5.0.2) lib/active_support/callbacks.rb:382:in block in make_lambda' activesupport (5.0.2) lib/active_support/callbacks.rb:169:in block (2 levels) in halting'
actionpack (5.0.2) lib/abstract_controller/callbacks.rb:12:in block (2 levels) in <module:Callbacks>' activesupport (5.0.2) lib/active_support/callbacks.rb:170:in block in halting'
activesupport (5.0.2) lib/active_support/callbacks.rb:454:in block in call' activesupport (5.0.2) lib/active_support/callbacks.rb:454:in each'
activesupport (5.0.2) lib/active_support/callbacks.rb:454:in call' activesupport (5.0.2) lib/active_support/callbacks.rb:101:in run_callbacks'
activesupport (5.0.2) lib/active_support/callbacks.rb:750:in _run_process_action_callbacks' activesupport (5.0.2) lib/active_support/callbacks.rb:90:in run_callbacks'
actionpack (5.0.2) lib/abstract_controller/callbacks.rb:19:in process_action' actionpack (5.0.2) lib/action_controller/metal/rescue.rb:20:in process_action'
actionpack (5.0.2) lib/action_controller/metal/instrumentation.rb:32:in block in process_action' activesupport (5.0.2) lib/active_support/notifications.rb:164:in block in instrument'
activesupport (5.0.2) lib/active_support/notifications/instrumenter.rb:21:in instrument' activesupport (5.0.2) lib/active_support/notifications.rb:164:in instrument'
actionpack (5.0.2) lib/action_controller/metal/instrumentation.rb:30:in process_action' actionpack (5.0.2) lib/action_controller/metal/params_wrapper.rb:248:in process_action'
activerecord (5.0.2) lib/active_record/railties/controller_runtime.rb:18:in process_action' actionpack (5.0.2) lib/abstract_controller/base.rb:126:in process'
actionview (5.0.2) lib/action_view/rendering.rb:30:in process' actionpack (5.0.2) lib/action_controller/metal.rb:190:in dispatch'
actionpack (5.0.2) lib/action_controller/metal.rb:262:in dispatch' actionpack (5.0.2) lib/action_dispatch/routing/route_set.rb:50:in dispatch'
actionpack (5.0.2) lib/action_dispatch/routing/route_set.rb:32:in serve' actionpack (5.0.2) lib/action_dispatch/routing/mapper.rb:16:in block in class:Constraints'
actionpack (5.0.2) lib/action_dispatch/routing/mapper.rb:46:in serve' actionpack (5.0.2) lib/action_dispatch/journey/router.rb:39:in block in serve'
actionpack (5.0.2) lib/action_dispatch/journey/router.rb:26:in each' actionpack (5.0.2) lib/action_dispatch/journey/router.rb:26:in serve'
actionpack (5.0.2) lib/action_dispatch/routing/route_set.rb:725:in call' rack-pjax (1.0.0) lib/rack/pjax.rb:12:in call'
remotipart (1.3.1) lib/remotipart/middleware.rb:32:in call' warden (1.2.7) lib/warden/manager.rb:36:in block in call'
warden (1.2.7) lib/warden/manager.rb:35:in catch' warden (1.2.7) lib/warden/manager.rb:35:in call'
rack (2.0.2) lib/rack/etag.rb:25:in call' rack (2.0.2) lib/rack/conditional_get.rb:25:in call'
rack (2.0.2) lib/rack/head.rb:12:in call' rack (2.0.2) lib/rack/session/abstract/id.rb:232:in context'
rack (2.0.2) lib/rack/session/abstract/id.rb:226:in call' actionpack (5.0.2) lib/action_dispatch/middleware/cookies.rb:613:in call'
activerecord (5.0.2) lib/active_record/migration.rb:553:in call' actionpack (5.0.2) lib/action_dispatch/middleware/callbacks.rb:38:in block in call'
activesupport (5.0.2) lib/active_support/callbacks.rb:97:in __run_callbacks__' activesupport (5.0.2) lib/active_support/callbacks.rb:750:in _run_call_callbacks'
activesupport (5.0.2) lib/active_support/callbacks.rb:90:in run_callbacks' actionpack (5.0.2) lib/action_dispatch/middleware/callbacks.rb:36:in call'
actionpack (5.0.2) lib/action_dispatch/middleware/executor.rb:12:in call' actionpack (5.0.2) lib/action_dispatch/middleware/remote_ip.rb:79:in call'
rollbar (2.14.1) lib/rollbar/middleware/rails/rollbar.rb:24:in block in call' rollbar (2.14.1) lib/rollbar.rb:145:in scoped'
rollbar (2.14.1) lib/rollbar/middleware/rails/rollbar.rb:22:in call' actionpack (5.0.2) lib/action_dispatch/middleware/debug_exceptions.rb:49:in call'
rollbar (2.14.1) lib/rollbar/middleware/rails/show_exceptions.rb:22:in call_with_rollbar' web-console (3.5.1) lib/web_console/middleware.rb:135:in call_app'
web-console (3.5.1) lib/web_console/middleware.rb:28:in block in call' web-console (3.5.1) lib/web_console/middleware.rb:18:in catch'
web-console (3.5.1) lib/web_console/middleware.rb:18:in call' actionpack (5.0.2) lib/action_dispatch/middleware/show_exceptions.rb:31:in call'
railties (5.0.2) lib/rails/rack/logger.rb:36:in call_app' railties (5.0.2) lib/rails/rack/logger.rb:24:in block in call'
activesupport (5.0.2) lib/active_support/tagged_logging.rb:69:in block in tagged' activesupport (5.0.2) lib/active_support/tagged_logging.rb:26:in tagged'
activesupport (5.0.2) lib/active_support/tagged_logging.rb:69:in tagged' railties (5.0.2) lib/rails/rack/logger.rb:24:in call'

I found the code on github. The #index action is missing for the Sessions Controller. I think #index should be added in order to follow good REST design.

@nathantech2005 Can you explain more about what your use case for this?

I'm closing this issue because it has not had recent activity.
If you're still facing this on the latest version, please open a new one with all the information requested in the template.
Thank you!


[server] Provide data flow diagram fro GraphQL and ObjectManager.

I'm fairly new to GraphQL/Relay and I'm trying to figure out exactly how everything fits together in URB.
The front-end seems fairly self-explanatory but I'm struggling to figure out exactly what the interactions between GraphQL, the object manager, the persister (cassandra) are.
Does anyone have a data flow diagram or detailed explanation that could help?

I'll try to put together something. At any rate I recommend watching the talk explaining DataLoader by @leebyron : DataLoader – Source code walkthrough.

@thelordoftheboards I might be being really stupid here but following the instructions for setting up Cassandra I'm getting "Keyspace system_schema does not exist" after running the npm run setup-database command. When you say  "Verify that the name of the database in /.env is the name of the database you want." in the dev setup docs, what exactly needs to be changed here. Cassandra is up and running on my machine locally so that isn't an issue.

This is indeed poor wording. Sorry about this. The idea is that the name of the keyspace should be specified in .env, instead of the default 'urb'.
Let me delete it locally and try to re-run npm run setup-database with the latest version, maybe it is broken now. Used to work.

Not to be that guy, but "works for me":
$ cqlsh
Connected to Test Cluster at <IP_ADDRESS>:9042.
[cqlsh 5.0.1 | Cassandra 3.3 | CQL spec 3.4.0 | Native protocol v4]
Use HELP for help.
cqlsh> describe keyspaces;

system_traces  system_schema  system_auth  system  system_distributed

cqlsh> exit
$ npm run update-default-persister -- cassandra

> @10.1.5 update-default-persister /Users/alex/Documents/Projects/URB
> babel-node ./scripts/update-default-persister.js "cassandra"

Written: /Users/alex/Documents/Projects/URB/configuration/graphql/defaultPersister.js
$ npm run setup-database

> @10.1.5 setup-database /Users/alex/Documents/Projects/URB
> babel-node ./scripts/setup-database.js

Initializing schema
Initializing Cassandra persister - start
Table ready: logs
Table ready: User
Table ready: Compendium
Table ready: Ensayo
Table ready: ToDo
Table ready: Translaticiarum
Table ready: PrimeNumber
Initializing Cassandra persister - success
$ cqlsh
Connected to Test Cluster at <IP_ADDRESS>:9042.
[cqlsh 5.0.1 | Cassandra 3.3 | CQL spec 3.4.0 | Native protocol v4]
Use HELP for help.
cqlsh> describe keyspaces;

urb  system_schema  system_auth  system  system_distributed  system_traces

cqlsh> use urb;
cqlsh:urb> describe tables;

"Compendium"  "Translaticiarum"  logs  "PrimeNumber"  "User"  "Ensayo"  "ToDo"

Thanks for the quick response! Ah I see what that problem is I think. So i'd already done the above steps but when i describe keyspaces  in cqlsh the keyspace system_schema isnt there. so thinking it might be a problem with cassandra installation.

At this point there is a lot of information online about both graphql and data loader and the value of writing yet another description of how they work together has diminished.


Reauthentication loop when using users from trusted domain

Preflight Checklist

[X] I have installed the latest version of Storage Explorer.
[X] I have checked existing resources, including the troubleshooting guide and the release notes.
[X] I have searched for similar issues.

Storage Explorer Version
1.34.0
Regression From
No response
Architecture
x64
Storage Explorer Build Number
No response
Platform
Windows
OS Version
Server 2022
Bug Description
We are experiencing a weird bug with Storage Explorer. The scenario is as following:
Storage Explorer runs on a server in Domain A (Resource Domain)
Users log in to the server with an identity from Domain B (Identity Forest) that is synced to Entra ID
When using this case, Authentication to Storage Explorer fails and the user is required to reauthenticate (which again doesn't work).
This is reproducable on different users on the same server.
Using a local user account on the server, authentication works fine.
Error message in SE logs:
Failed to get AAD Organizations during account creation because of 'Microsoft.Developer.IdentityService.AccountProvider.NoMatchingAccountException: No matching accounts found in any MSAL cache.
   at Microsoft.Developer.IdentityService.AccountProvider.MsalNetworkServicesImpl.AcquireTokenSilentAsync(String resource, String tenant, UserIdentifier userId, AuthenticationFlowType authenticationFlowType, CancellationToken cancellationToken)
   at Microsoft.Developer.IdentityService.AccountProvider.AadAccountProviderNetworkServicesBase.AcquireGraphTokenAsync(String resource, AuthenticationInfo userInfo, String tenantId, Boolean promptIfNeeded, String queryParameters, AuthenticationFlowType authenticationFlowType, Dictionary`2 additionalAuthProperties, CancellationToken ct)
   at Microsoft.Developer.IdentityService.AccountProvider.AadAccountProviderNetworkServicesBase.GetAADOrganizationInformationAsync(AuthenticationInfo authInfo, Boolean promptIfNeeded, String queryParameters, AuthenticationFlowType authenticationFlowType, Dictionary`2 additionalAuthProperties, CancellationToken cancellationToken)
   at Microsoft.Developer.IdentityService.AccountProvider.AadAccountProviderNetworkServicesBase.GetAADOrganizationInformationAsync(AuthenticationInfo authInfo, Boolean promptIfNeeded, String queryParameters, AuthenticationFlowType authenticationFlowType, Dictionary`2 additionalAuthProperties, CancellationToken cancellationToken)
   at Microsoft.Developer.IdentityService.AccountProvider.AadAccountProviderService.GetAADOrganizationsInfoAsync(AuthenticationInfo authInfo, Boolean promptIfNeeded, String queryParameters, AuthenticationFlowType authenticationFlowType, Dictionary`2 additionalAuthProperties, CancellationToken cancellationToken)
   at Microsoft.Developer.IdentityService.AccountProvider.AadAccountProviderService.CreateAccountFromAadAsync(Account account, ImmutableArray`1 scopes, List`1 errors, AuthenticationInfo authInfo, Boolean promptIfNeeded, String queryParameters, AuthenticationFlowType authenticationFlowType, Dictionary`2 additionalAuthProperties, CancellationToken cancellationToken)'

We've tried to change authentication methods, but none of the offered solutions work. Using different Entra ID accounts does not change the outcome.
Adding Storage Accounts using SAS Token works fine, but is not the targeted solution.
Steps to Reproduce

Login to Server using an account from trusted domain
Start Storage Explorer
Authentication using Entra ID
Authentication is marked as successful but user is required to reauthenticate

Actual Experience

User tries to authenticate to Entra ID
Browser opens for authentication, users authenticated successfully
After authentication, several browser tabs open
Authentication is marked as complete in Storage Explorer
User is asked to reauthenticate, Error Message "No matching accounts found in any MSAL cache."

Expected Experience
No response
Additional Context
No response

Possible duplicate of #8029.

Issue fixed, was a configuration issue on the server:
We had to create a DWORD Regkey "ProtectionPolicy" set to 1 in Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Protect\Providers\df9d8cd0-1501-11d1-8c7a-00c04fc297eb
Not sure why this wasn't set before. Closing Issue


Possibly add 24h delay

http://blog.npmjs.org/post/141905368000/changes-to-npms-unpublish-policy
Since NPM has introduced the policy of 24 hours for 'unpublish' it might be worth delaying update notifications by that time.
Possibly as opt-in

Thanks for your suggestions @nkbt!
As explained here this isn't what we would want to do for now.
If this problem becomes apparent and many users are complaining we will take another look at it.
However I would prefer to check for unpublished versions and simply close affected pull requests automatically.
Happy to reopen this issue then.
Best,
Stephan

No worries, Stephan, that is reasonable. After all I can always postpone merging a PR for a day or so =)


Logical model: result receiver

#128
resultReceiver	1 .. 1	0 .. 1		Is a boolean which is set to True when prescriber wants a feedback. Should we put  "1 .. 1" cardinality or keep it "0 .. 1" even if it is a boolean ? If "1..1", should we set True of False by default ?

WG: we make the field mandatory.

solved in #68


Remove extra spaces from OVMS tag

Description

How Has This Been Tested?

Merge criteria:

[ ] The commits are squashed in a cohesive manner and have meaningful messages.
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has manually tested the changes and verified that the changes work

/rerun

closing it in favour of https://github.com/opendatahub-io/odh-model-controller/pull/315


The website is probably down now.

The website (https://ego4ddataset.com/) says 'NetworkError when attempting to fetch resource.' after I click the submit button.

We can confirm and it will be corrected shortly.  We appreciate you flagging this!


Conditional masking policy with multiple columns always forces replacement

Provider Version
0.70.1
Terraform Version
1.5.4
Describe the bug
We are creating a conditional masking policy with multiple columns in the signature. The masking policy is created correctly in Snowflake, but when running terraform plan afterwards it always claims that the signature has changed which forces replacement.
Expected behavior
The masking policy should not change.
Code samples and commands
Example masking policy that fails:
resource "snowflake_masking_policy" "example_conditional_masking_policy" {
  name = "EXAMPLE_CONDITIONAL_MASKING_POLICY"

  database           = "EXAMPLE_DB"
  schema             = "EXAMPLE_SCHEMA"
  return_data_type   = "NUMBER"
  masking_expression = <<-EOF
  case
    when current_role() in ('ADMIN') then val
    when customer_id <= 0 then 0
    else val
  end
EOF
  signature {
    column {
      name = "VAL"
      type = "NUMBER"
    }
    column {
      name = "CUSTOMER_ID"
      type = "NUMBER"
    }
  }
}

Output from terraform plan:
 # snowflake_masking_policy.example_conditional_masking_policy must be replaced
-/+ resource "snowflake_masking_policy" "example_conditional_masking_policy" {
      ~ id                    = "EXAMPLE_DB|EXAMPLE_SCHEMA|EXAMPLE_CONDITIONAL_MASKING_POLICY" -> (known after apply)
      ~ masking_expression    = <<-EOT
            case
              when current_role() in ('ADMIN') then val
              when customer_id <= 0 then 0
              else val
            end
        EOT
        name                  = "EXAMPLE_CONDITIONAL_MASKING_POLICY"
      ~ qualified_name        = "\"EXAMPLE_DB\".\"EXAMPLE_SCHEMA\".\"EXAMPLE_CONDITIONAL_MASKING_POLICY\"" -> (known after apply)
        # (4 unchanged attributes hidden)

      ~ signature {
          + column {
              + name = "CUSTOMER_ID"
              + type = "NUMBER" # forces replacement
            }

            # (1 unchanged block hidden)
        }
      - signature {
          - column {
              - name = "CUSTOMER_ID" -> null
              - type = "NUMBER" -> null # forces replacement
            }
        }
    }

Additional context
It looks like it also marks the masking expression as changed - could be related to issues with heredocs in https://github.com/Snowflake-Labs/terraform-provider-snowflake/issues/2053?

Verified that it's an issue with trailing newline in the heredoc style row access expression.
I moved the expression to a local variable and changed the row access policy resource to use row_access_expression = trim(local.expression, "\n") and the issue disappeared.


Eloquent Methods Not Triggering Model Touch Relationships

It appears the Eloquent upsert() and insertIgnore() do not trigger model touch relationships for updating owner/parent timestamps as outlined here:
https://laraveldaily.com/eloquent-touch-for-models-and-their-relationships/
These are the relationships defined in the model as $touches.

That's the correct behavior. You need to differentiate between methods like Model::update() and Builder::update(). Only the former one touches relationships, the latter one doesn't:
// Fetches the model from the database and touches relationships.
User::find($id)->update($values);

// Executes the query directly in the database and doesn't touch relationships.
User::where('id', $id)->update($values);

upsert() and insertIgnore() are Builder methods and can't touch relationships.


Add JS diff to artifacts

Follow on from https://github.com/silverstripe/silverstripe-admin/issues/1671#issuecomment-1943436438
When a JS diff fails, generate a new file that shows the diff between the two files that are different and copy it to the artifacts director. Will need to checkout or download the original file again.
If the diff isn't too large, also output it to the console for convenience
git diff --word-diff --word-diff-regex=[^;] is one option to generate the diff
May wish to string replace ; with ;\n before doing the diff for the file

Probably don't need this any more, the random js diff only happens in 4.13 which is now only is security support mode. Workaround solution is to simply rebuild the bundle until the signature matches


chore(apps/prod/tekton/configs/triggers): add trigger for ctl building

The pushing of tidb OCI artifacts will trigger the building for ctl component.
When building it, it juge version with tidb.git repo.

/approve


gf2x: switch to inria gitlab as predicted before

Description of changes
The fetchgit URL has been pointed to the INRIA GitLab instance as scm.gforge.inria.fr doesn't seem accessible anymore. This change has been expected: https://github.com/NixOS/nixpkgs/pull/45299#issuecomment-564477936
Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Can we switch to fetchFromGitLab maybe ?

@nagy Good idea!


"Get Started" button should be a link

On the homepage, the "Get Started" button is a clickable <button> element with a javascript onclick action that updates the page's URL. This prevents normal things like clicking with the middle mouse button to open in a new tab, and presumably it does nothing at all if the user has JavaScript disabled (though I didn't test this). This should be a proper link styled like a button rather than a button with a javascript handler.

Hi again @ogier
You are absolutely right. I know how this happened, too. Originally the "Get Started" button was another "Run code" button, then we changed its behavior but didn't update the HTML implementation of it.
I'm going to create an issue on https://github.com/alantech/homepage referencing this one and then close this one out.


enhanced baselayout for mobile and embedded devices

The base UI with toolbar is optimized for Desktop UI,

optimize the UI to work on small screens
add option to hide/show toolbars

With 2.1 the WorkbenchDecorator is customizable. The default decorator works primary for large screen devices. Currently there are no plans to implement other "default" decorators, but when a specific (mobile) layout is needed you can implement one and register it in your applicationLauncher.


feat: remove --suffix from mktemp

Not all distros provide a version of mktemp which supports --suffix

Thanks for the pull request!

Thanks for your scripts, they are very helpful


Support non-uniform assemblies with detailedAxialExpansion disabled

Description
Added setting nonUniformAssemFlags that allows specific assems to not conform to uniform mesh.

Checklist

[x] This PR has only one purpose or idea.
[x] Tests have been added/updated to verify that the new/changed code works.

[x] The code style follows good practices.
[x] The commit message(s) follow good practices.

[x] The release notes are up-to-date with any bug fixes or new features.
[x] The documentation is still up-to-date in the doc folder.
[x] The dependencies are still up-to-date in setup.py.

Okay, this new CaseSetting seems fine, and I like the unit test.
But... who is planning on using this?  My thought is that since no one has needed this the last ~8 years, I'm surprised this went into armi and not a Plugin or App.  I assume that this was added because you want to use it yourself right now, right?
I'm kind of waffling; do we think this is generally useful enough to be in ARMI?

@john-science, we will likely be using within TP. please call me for a non-public chat i can expain.


Feature/tools

Hi This is the Tools that the agent can use later, for search on the internet or comunicate with diferent apis

Hi I fixed the observations , pls let me know if you can see the changes, this is my first time contributing to an open source project, sorry if I do something wrong :)

Ones the tools are approves and also the stop word I can start working on the Zero shot agent

I checked the implementation and structure in langchain and langchainjs, the tools package should placed under agents sub-directory.

@nekomeowww should I create a new folder called  agents inside exp?

I fixed the file name, pls accept the commit and in a letter commit ill try top add the struct to the serpapi response

Closing in favor of https://github.com/tmc/langchaingo/pull/38


Simplification in Text Helper's character_limiter()

Because the "\s" regex character class includes \r and \n,
there is no need for the str_replace() part

For the record, @nicolas-grekas brought the following upon this cursed land:
/(?:\s{2,}+|[^\S ])/


fix(security): Mismatched types int and int32

Signed-off-by: Bryon Nevis<EMAIL_ADDRESS>PR Checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/master/.github/Contributing.md.
What is the current behavior?
Automatic type selection of saltLength constant causes type checking error in numerical comparison.
Issue Number:
Closes #3654
What is the new behavior?
Ensure that the constant is of the same numeric type as Reader.Read() method.
Does this PR introduce a breaking change?

[ ] Yes
[x] No

New Imports

[ ] Yes
[x] No

Specific Instructions
Are there any specific instructions or things that should be known prior to reviewing?
Other information

Codecov Report

Merging #3655 (6bde2d4) into main (a7bcd55) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #3655   +/-   ##
=======================================
  Coverage   47.29%   47.29%
=======================================
  Files         112      112
  Lines        9177     9177
=======================================
  Hits         4340     4340
  Misses       4463     4463
  Partials      374      374

Impacted Files
Coverage Δ

internal/security/kdf/methods.go
85.71% <ø> (ø)

Continue to review full report at Codecov.

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


eink: Buttons Debug info don't show text

Is the bug present when using the default Obsidian theme?
No
Is the bug present when snippets and plugins are disabled?
No
Minimal theme version
7.2.0
Describe the bug
Opening the debug info from the command palette shows a dialog with no text in the buttons.
The text is shown when hovering over the buttons.

Debug info
SYSTEM INFO:
Obsidian version: v1.4.3
Installer version: v1.1.9
Operating system: Windows 10 Pro 10.0.22621
Login status: logged in
Catalyst license: insider
Insider build toggle: on
Live preview: on
Legacy editor: off
Base theme: light
Community theme: Minimal v7.2.0
Snippets enabled: 1
Restricted mode: off
Plugins installed: 12
Plugins enabled: 11
1: Calendar v1.5.10
2: DB Folder v3.4.0
3: Juggl v1.4.0
4: Diagrams v1.5.0
5: Obsidian Git v2.20.7
6: Dataview v0.5.56
7: Footnote Shortcut v0.1.2
8: Excalidraw v1.9.16
9: QuickAdd v1.2.1
10: Projects v1.16.3
11: Minimal Theme Settings v7.2.1
RECOMMENDATIONS:
Custom theme and snippets: for cosmetic issues, please first try updating your theme and disabling your snippets. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community theme and snippets.
Community plugins: for bugs, please first try updating all your plugins to latest. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community plugins.

Fixed in 7.6.2


visualisation and aggregation analytics

Please review if this solves the issue #111

I have used this.reactGAVis(this.props.vis) instead of this.reactGAVis(Visualization[value]) as it updates both 'Radar' as well as 'Table' in reactGA one after another.


Not clear enough that distances need to be set on Y axis in 03_where_is_my_reader

The CIL convention is that distances are set along the Y axis.
In this notebook, for exercise C I tried:
geometry = AcquisitionGeometry.create_Cone2D(source_position=[0,0], detector_position=[source_to_detector_distance, 0], rotation_axis_position=[source_to_object_distance, 0])

This gives an error:
ZeroDivisionError: float division by zero
I don't think this is at all clear to the user what they have done wrong.
The solution is:

geometry = AcquisitionGeometry.create_Cone2D(source_position=[0,0],
                                             detector_position=[0,source_to_detector_distance],
                                             rotation_axis_position=[0,source_to_object_distance])

Previously, we did add a 'common mistakes' section, but this appears a fair bit after this exercise so wouldn't be seen until later.


Gives a message "not found"

After the basic installation when I say "require("gitportal").open_file_in_browser()" it just shows a quick message "not found" and nothing happens.
I am in wsl ubuntu environment, btw. Could it be that there a browser can't be found?
Are there logs that I can see?

@lispercat Sorry you're having trouble! There are not any persistent logs, that's something I need to add. I think this is likely a result of lua not knowing how to find your browser, or how to launch it with the right command.
Can you run the following command inside neovim, via command line mode and let me know if you get the same "not found" error?
:lua os.execute("xdg-open 'https://www.google.com'")
It's possible I'm inaccurately determining when to use what command. Could you run this command inside neovim via the command line mode and let me know if this works for you?
:lua os.execute("open 'https://www.google.com'")
and lastly, could you let me know the output of this command (in neovim via command line mode) so I can ensure your use case is supported?
:lua print(vim.loop.os_uname().sysname)
Sorry for the inconvenience. I'll work on adding logs this weekend

@lispercat Perfect, that's super helpful. I'm going to do some digging this evening (I'm on east coast time in US) and see if I can detect this case and use the appropriate command, but I'm also going to add a setting that lets you specify the command required to open links in browsers as well, I'm sure you're not the only one.
I'll ping you when it's ready! Thanks so much :-)

@lispercat I've added the ability to specify the browser opening command in the config. Instructions are on the readme!
I would still like to make this plugin smarter about which command to use, so I'm leaving this issue open for now as I learn more about how to do that. But in the meantime this should make the plugin usable! :-) Let me know if you have anymore troubles

@lispercat Alright, I think I may know how to make this detect ubuntu from wsl. Can you do me a favor and provide me the output from the following cli command?

uname -a

Alternatively, if you don't wish to provide the whole output, could you just let me know if there is an identifying string in the output? Perhaps something like Microsoft or wsl, or something that gitportal can use to determine if it needs to use an alternate command?

@lispercat Hey! GitPortal should work automatically now for your linux version without any issue, and with no need to specify the browser command. If this issue still persists, please re-open this issue! I really appreciate your feedback and patience with this issue and hope you enjoy using the plugin :-)

Thanks, Trevor
On Fri, Dec 13, 2024 at 12:20 AM Trevor Hauter @.***>
wrote:

@lispercat https://github.com/lispercat Hey! GitPortal should work
automatically now for your linux version without any issue, and with no
need to specify the browser command. If this issue still persists, please
re-open this issue! I really appreciate your feedback and patience with
this issue and hope you enjoy using the plugin :-)
—
Reply to this email directly, view it on GitHub
https://github.com/trevorhauter/gitportal.nvim/issues/46#issuecomment-2540576201,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACCZB2P6CET24OTWR6CYCT2FJVALAVCNFSM6AAAAABSG6ZZDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBQGU3TMMRQGE
.
You are receiving this because you were mentioned.Message ID:
@.***>


add "Play next movie or TV show"

based on #529

Thanks for this! It would be nice to extend it to show the next video with a countdown instead of immediately playing it.


Add Dump command to VS

Talking with @dsyme I implemented Dump command to vs to help anlyze memory issues of F# language service in VS
The dump taken after all operations in Reactor finished
And I used ClrMD https://github.com/Microsoft/clrmd/pull/91 to take the dump so it not waste disk or ram
The dump written to the output window
@cartermp what do you think?
I'm also want to implement this on tests so we can compare memory after every build
One thing missing is thaat even that I added the Microsoft.Diagnostics.Runtime package to FSharp.Editor
and VisualFSharpFull projects the dll is not included in the vsix how I can fix this?

@AviAvni adding to VisualFSharpFull.csproj
  <ItemGroup>
      <VSIXSourceItem Include="$(OutputPath)Microsoft.Diagnostics.Runtime.dll" />
  </ItemGroup>

should probably work, but I have no idea if this is the recommended way to do it.

Sorry for the late reply - was on vacation.  I would tend to prefer that this be added as an extension, perhaps into the "Project System Tools" extension?  Tagging @panopticoncentral

@brettfo and @Pilchie  thanks for feedback
This is in the "Project System Tools" because @dsyme wanted it in a specific state of the language service when all the work on the queue is done
In any case I'll be happy to continue work on this

@panopticoncentral ok so how this is going to work?
can I use classes that declared in this repo there via nuget so I can take the dump when the lang service finished all operations
or I'll just do the dump there and it's need to be taken manually on time
or I'll expose it as a service and use that service here
or you have another idea?

Is the API to know when the lang service is done available publicly? If so, I'd just call it from the extension and then do the dump.

@AviAvni
Hello my friend, is this still an active work item for you?
Thanks
Kevin

I can work on it if you want but as said in comments it belong to other project that I don't know how to implement it there

Thanks for this PR, however it looks to be quite out of date, please reopen, if you want to continue with it.
Kevin


new version for cocoaPods

Hi,
Is it possible to release a 1.2 release with the last patchs, including the one which hide SDK logs ?
Moreover, it will be better to rename your pod, « le » is too short and not very descriptive.
Thank you

+1


Dupe bug with Sponge plugins

hello
I am currently running
Industrial Foregoing Version:  1.12.2-1.5.3-88
TeslaCoreLib Version: 1.12-1.0.10
griefprevention-1.12.1-<IP_ADDRESS>3
spongeforge-1.12.2-2503-7.0.0-BETA-2725
forge-1.12.2-<IP_ADDRESS>5
industrialforegoing-1.12.2-1.5.3-88
LuckPerms v3.4.68
here is how the Dupe glitch works
you will need 2 people for this
1 person make a claim
then place a block near the claim that you want to dupe with example place a diamond block on the border of your claim
the second person that not trusted in your claim place down Block breaker from
Industrial Foregoing mod and power it if you don't know how it works then it would be easier to use Extra Utilities 2 Creative Energy Source block next the block breaker and it start duping check inside of the block breaker and you will get dupe items
here a GIF on how to do this
https://gyazo.com/a5a1e344f77af9484b5c579155908d48
as you he place a block breaker next to my diamond block and it start to dupe
you can use any source of power to power block breaker i just use Creative energy source because it was faster to show you, it really shows no logs
EDIT: Phit had pointed this out
https://github.com/Buuz135/Industrial-Foregoing/blob/master/src/main/java/com/buuz135/industrial/tile/world/BlockDestroyerTile.java#L90
Im not sure if it's help

Having the same issue
version that i am currently at
is
Industrial Foregoing Version: 1.12.2-1.5.4-91
TeslaCoreLib Version: 1.12-1.0.11
griefprevention-1.12.1-<IP_ADDRESS>3
spongeforge-1.12.2-2529-7.0.0-BETA-2730
forge-1.12.2-<IP_ADDRESS>9
LuckPerms-Sponge-4.0.4
this is latest version as of this moment and it i can still dupe

If someone can test this version and tell me if it is fixed I would appreciate it. @JoeSGT @runescapejon
industrialforegoing-1.12.2-1.5.5.jar.zip

tested, don't work
but thanks for trying to fix this

Soooo, it's fixed?

nope it's not fixed i can still dupe with version 1.12.2-1.5.5
the one you just gave us

here is proof of the dupe
https://gyazo.com/a4691b903f7e2057517a0403c048de85

And this one? industrialforegoing-1.12.2-1.5.5.jar.zip

this one does not work

Then I can't fix it, it's on the plugin side, you can disable the machine work in the config.

it's been reported on the plugin issue page and he said it's spongeforge side then they said it's your issue
weird im not sure where to go to get this fix
but thanks it seem i have to disable this and ban it

I do really check anything possible

I'm not much of a coder but can you try adding a check here
https://github.com/Buuz135/Industrial-Foregoing/blob/master/src/main/java/com/buuz135/industrial/tile/world/BlockDestroyerTile.java#L69
and see if it work
im not sure if it work or not but it's worth a try

I check if a fake player can break it. I check if the block has been broken before adding the items to the inventory, nothing more I can do.

hm not sure if it help but take a look on what Gabizou said
https://github.com/SpongePowered/SpongeForge/issues/1830

I dont have to support 3rd party forge programs, there aren't any more checks I can do, I'm using anything forge provides, not what Sponge provides, if there are more Forge known checks just let me know.

alright thanks

@JoeSGT Can you do me a favor and try this version to fix this issue?
industrialforegoing-1.12.2-1.5.9.jar.zip

Same for @runescapejon

great news it break the block and does not dupe
but sadly players can use it for griefing since it bypass the claim's and break the block

Sorry it's fixed

thanks


Bug: XcodeProjFilelist fails if xcodeproj  target name is too long

Describe the bug
XcodeProjFilelist fails with code 36 (cp failure) if the target name of xcodeproj is too long.
Additional context
Since rules_xcodeproj doesn't support multiple Xcode configurations as of now, we duplicate the xcodeproj target with different target names for each configuration.
[
    xcodeproj(
        name = "xcodeproj-{0}-{1}-{2}-{3}".format(
            build_mode,
            ios_simulator_cpus,
            env,
            compilation,
        ),
        build_mode = build_mode,
        config = "rules_xcodeproj_{0}_{1}".format(env, compilation),
        ios_simulator_cpus = ios_simulator_cpus,
        ...
    )
    for build_mode in [
        "bazel",
        "xcode",
    ]
    for ios_simulator_cpus in [
        "sim_arm64",
        "x86_64",
    ]
    for env in [
        "Dev",
        "Prod",
    ]
    for compilation in [
        "Debug",
        "Release",
    ]
]

The target names are quite long in this case to ensure their uniqueness, like xcodeproj-bazel-sim_arm64-Dev-Debug.
The compilation was added recently, but we noticed that build-cache warming has been failing on CI with the following error since it was added.
I haven't completely figured out the cause, but it seems that the too long target name was causing this problem.
//:xcodeproj-bazel-sim_arm64-Dev-Debug.generator
XcodeProjFilelist command exited with code 36
/bin/bash
-c
if [[ $OSTYPE == darwin* ]]; then cp -c "$1" "$2" else cp "$1" "$2" fi
bazel-out/ios-sim_arm64-min14.0-applebin_ios-ios_sim_arm64-dbg-ST-xxx/bin/xxx/xxx/xxx/xxx.indexstore
...
bazel-out/darwin-dbg/bin/xcodeproj-bazel-sim_arm64-Dev-Debug.generator-bi __xxx:xxx ios-sim_arm64-min14.0-applebin_ios-ios_sim_arm64-dbg-ST-xxx.filelist

Reproduction steps

Define xcodeproj target with name xcodeproj-bazel-sim_arm64-Dev-Debug.
Run bazel run //:xcodeproj-sim_arm64-Dev-Debug -- --generator_output_groups=all_targets 'build --remote_download_minimal'

Expected behavior
It works regardless of the length of the target name.
Versions

Bazel: 6.0.0-pre.20220804.3
rules_xcodeproj: 0.10.1
rules_apple: d04edf4136b4818662d7126582ec257aee372339
rules_swift: 6153a848f747e90248a8673869c49631f1323ff3
Environment: CircleCI with BuildBuddy through RBE

This should be fixed in HEAD by https://github.com/buildbuddy-io/rules_xcodeproj/commit/df9425a497a1b871885573cef2882d9dd75dcf11, can you confirm?

I confirmed that it works with 0.11.0. Thanks for the fix!


Remove unnecessary view groups from sample app

At the moment the sample app inflates an unnecessary view group when inflating a view class. The easy fix would be to replace the root view group defined in xml with a merge element.
I think a cleaner approach would be to reference the view itself in xml. I'm still wrapping my head around architect so I don't necessarily know the implications of what I'm about to suggest so bear with me :). Instead of inflating a layout file in the constructor of the view push the inflation to the StackablePath implementation.
So the HomeView / HomeStackable / home_view.xml would look like
public HomeView(Context context, AttributeSet attributeSet) {
  super(context, attributeSet);
  DaggerService.<HomeStackable.Component>get(context).inject(this);
}

@Override protected void onFinishInflate() {
  ButterKnife.bind(this);
}

and
@Override public View createView(Context context, ViewGroup parent) {
  return View.inflate(context, R.layout.home_view, parent);
}

and
<?xml version="1.0" encoding="utf-8"?>
<com.mortarnav.view.HomeView
    xmlns:android="http://schemas.android.com/apk/res/android"
    android:layout_width="match_parent"
    android:layout_height="wrap_content">
...

This would require a signature change on StackablePath, internal record keeping of the parent ViewGroup, and a way to specify a layout file for a view within robot. What do you think?

You are right. I personally prefer using the View class with  on the xml, because I can then better reuse them in other xml files (without having to use  which adds an useless viewgroup).
But it should be up to the developer to choose the way he prefers.
I will update StackablePath createView() method to the following:
public interface StackablePath extends Stackable {
   View createView(Context context, ViewGroup parent);
}

You will then be able to return view by inflating a layout:
public class HomeStackable implements StackablePath {
    @Override
    public View createView(Context context, ViewGroup parent) {
        return LayoutInflater.from(context).inflate(R.layout.home_view, parent, false);
    }

The StackablePath change sounds good. :+1:
Will there be an optional option to provide a layout file via annotation? Also let me know if you need / want help on anything. I'm more than willing. :)

By annotation, do you mean @AutoStackable?
I'm planning to implement the following:
@AutoStackable(
        component = @AutoComponent(includes = StandardAutoComponent.class),
        pathWithLayout = R.layout.slides_view
)
@DaggerScope(SlidesPresenter.class)
public class SlidesPresenter extends ViewPresenter<SlidesView> {
}

Thanks for the help offering. You are actually already helping :)

I do! And that looks good. :+1:

Done in 0.14-SNAPSHOT.

I'll check this out as well. Thanks!


refactor(frontend): commot props for transaction UI

Motivation
A few props are in common with all the transaction UI. So we use TransactionUiCommon.
Tests
Unfortunately, the Transaction type is derived from an external type: meaning that ZOD will not correctly test correct parsing. But I accept any kind of suggestion

test failed


[gym_Website]: Add a Scroll To Top Button According to the Theme

Describe the project you want to add with tech stack
I would like to add a scroll to top button according to the theme of the webpage.
Expected behavior

Screenshots (optional)

Additional context (optional )

@MohitGupta121  @TusharKesarwani sir pls assign me this issue

@MohitGupta121 @TusharKesarwani could you kindly assign me this issue


Replaced provisioner function names with driver

@aarongalang Needs change in azure-cosi-driver/pkg/server/identity/identity.go


Gradients

Is it possible to draw gradients ?
I'm pretty new to graphviz and this javascript library too, but I've tried some examples of gradients and couldn't make it working...
Can you put a working sample for node gradients if this library supports it ?
Thanks

Viz.js now uses Graphviz 2.38.0, which supports gradients.


Button padding

Detailed description
https://www.carbondesignsystem.com/components/button/style/#structure defines the left and right padding as 16px and 64px but 16px and 16px for ghost type.  The 64px part seems odd.  However, checking the code examples on https://www.carbondesignsystem.com/components/button/code/ have a left padding of just 15px and examples with icons have right padding of 19px.
This stems from the left-padding actually being 12px with a 3px border and the right padding being a 16px right position inside of a 3px border.
Also worth noting, the right padding is actually 60px with the 3px border making it 63px total (applied to the text, not the icon).
So the table referencing 64px makes more sense but there is still an inconsistency for ghost style and maybe room to clarify right padding for icon vs no icon.
Side Note
The table lists the padding for ghost as 16 / 2 where the first number is px and the second is rem but 16px is actually 1rem, not 2.
Well, Tertiary style buttons get a little more interesting since they are intended to have a 1px border vs the 3px defined on primary (that blends with the background).  The left padding on a tertiary style button remains 12px so the total visual padding is just 13px from outside of button to the text.
Additional information

Ghost button intentionally has a different padding-right than the other buttons
64px padding right is the correct intended padding-right is a stylistic decision made by IBM Brand.

Confirmed bugs to be fixed:

[ ] The complied padding size does not equal 64px padding right and 16px. I believe this may be because we reduced the width of the focus at one point and the subtracted pixel was not added back into the button size.

[ ]The icon is appearing at 19px from the edge and should be 16px

Closing since this documentation is correct (this is the website repo) but it is still incorrect in code and I have made a new issue for it in the correct repo.
https://github.com/carbon-design-system/carbon/issues/6454
We have added some clarity around padding when using buttons with icons.


Docs site down

material-ui.com is currently showing the github 404 page. Guessing it was the v1 release?

http://www.material-ui.com/v0.16.0/#/

@prescottprue Yeah, sorry, we had some DNS issues, so we couldn't do as seamless a swap-over as we'd have liked.
www should soon redirect to material-ui.com, and you can find the v0.16.0 docs here (But 0.16.0? Srsly? :open_mouth: 😄 )

Cool. Thanks for the quick response!

found this: https://material-ui-1dab0.firebaseapp.com/versions/
has the v1 docs


Add shim for bpf syscall so other go libraries can be ported to windows

From ebpf-for-windows slack channel:
Lorenz Bauer: Have you decided what your ABI / API boundary is going to be? Is it raw syscalls or the libbpf C API?
gmassaro: is there an issue tracking the syscalls support ?
Dave Thaler: @Lorenz Bauer if I understand your question, it's currently the libbpf api.  syscalls themselves work differently on windows vs linux.  We may be able to shim linux-like syscalls for things (like the go library?) that do syscalls directly without libbpf, but haven't done any design work on that yet.  Let us know if that's what you'd like.
Lorenz Bauer: yeah that was my question, thanks :slightly_smiling_face:
Dave Thaler: sure, are you interested in something in particular that makes raw syscalls?   I'd like to file a github issue to track this, so more information would be helpful.
Dave Thaler: or even better, you're welcome to file it :)
Lorenz Bauer: more of an observation: Go packages tend to favour raw syscalls since they are faster than C FFI aka CGo and avoiding CGo makes distribution easier (no need for a C compiler). this is most important to read / write maps i'd say.
Zvi Effron: Plus, disabling CGo entirely makes things easier when writing code in the same repository that is C but not go related, because otherwise the Go compiler will complain about the C files. Especially when cross-compiling (i.e. my team develops on macOS, but we compile for Linux, or, if we started using eBPF for Windows, Windows.). (edited)

To add to info, there are multiple go libraries for ebpf (five of them according to Lorenz):

https://github.com/aquasecurity/libbpfgo : this uses libbpf() APIs
https://github.com/dropbox/goebpf
https://github.com/cilium/ebpf
https://github.com/iovisor/gobpf
...

Some bpf syscalls to prioritize are listed in https://github.com/microsoft/ebpf-for-windows/discussions/673

BPF_OBJ_GET (issue Add shim for bpf syscall so other go libraries can be ported to windows #559)
BPF_MAP_GET_FD_BY_ID
BPF_PROG_LOAD
BPF_PROG_TEST_RUN
BPF_OBJ_PIN
BPF_MAP_UPDATE_ELEM
BPF_MAP_LOOKUP_ELEM
BPF_MAP_DELETE_ELEM
BPF_OBJ_GET_INFO_BY_FD

See https://www.kernel.org/doc/html/latest/userspace-api/ebpf/syscall.html for docs.


Nose Tests discovery fails when tests are split by folders and imported to init.py (wantModule and wantDirectory are not parsed)

Environment data

VS Code version: 1.37.1
Extension version (available under the Extensions sidebar): 2019.8.30787
OS and version: Windows 10 running VS Code, remote plugin connects to Ubuntu 18.04.2 via SSH
Python version (& distribution if applicable, e.g. Anaconda): python 2.7.15rc1
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): virtualenv
Relevant/affected Python packages and their versions: Django==1.11.23; django-nose==1.4.6; nose==1.3.7
Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info #3977): jedi

Expected behaviour
Test discovery for nose should scan for both wantFile and wantModule and/or wantDirectory log outputs
Actual behaviour
We have a django project with django-nose test runner. Tests are split into modules, and all tests are imported to __init__.py. I think these are some obsolete tests, from default django test runner. But nose runs them perfectly.
I create a simple script, that translates the nosetests call to ./manage.py test call.
Basically it just strips -vvv and replaces it with --verbosity

#!/bin/bash
function arg_remove ()
{
    local array=("${@:3}")

    for ((i=0; i<"${#array[@]}"; ++i)); do
        case ${array[i]} in
            "$2") unset array[i]; break ;;
        esac
    done

    # clean up unset array indexes
    for i in "${!array[@]}"; do
        new_array+=( "${array[i]}" )
    done
    array=("${new_array[@]}")
    unset new_array

    # assign array outside function scope
    local -g "$1=(  )"
        eval ${1}='("${array[@]}")'
}
arg_remove ARG_PASS "-vvv" "$@"
echo $@
direnv exec /home/igor/myproject/backend/ /home/igor/.virtualenvs/myproject/bin/python /home/igor/myproject/backend/manage.py test --settings=core.local_settings --verbosity=3 -l nose.selector --nologcapture "${ARG_PASS[@]}"

The structure of tests is (stripped)
File backend/apps/tests/__init__.py

from .action import ActionTestCase

File backend/apps/tests/action.py

from apps.myproj.tests.base import BaseTestCase

class ActionMSFTestCase(BaseTestCase):
    pass
    # stripped

The output of --collect-only command is different to what vscode-python expects.
Relevant output to tests above is:
nose.selector: DEBUG: wantDirectory /home/igor/ata_portal/backend/apps/api/tests? True
nose.selector: DEBUG: Test name /home/igor/ata_portal/backend/apps/api/tests resolved to file /home/igor/ata_portal/backend/apps/api/tests, module None, call None
nose.selector: DEBUG: Final resolution of test name /home/igor/ata_portal/backend/apps/api/tests: file /home/igor/ata_portal/backend/apps/api/tests module apps.api.tests call None
nose.selector: DEBUG: wantModule <module 'apps.api.tests' from '/home/igor/ata_portal/backend/apps/api/tests/__init__.pyc'>? True
nose.selector: DEBUG: wantClass <class 'apps.api.tests.action_msf.ActionMSFTestCase'>? True

parserService here scans only for wantFile output.
In case above it founds wantClass above any wantFile ... py? True line. That causes testFile.suites.push(testSuite); to fail
Steps to reproduce:

Create a package tests
Add a module action.py to package with some real test case
import action inside tests/__init__.py
Configure nose tests for workspace
Run Python: Discover Tests command

Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
Test Discovery failed:
TypeError: Cannot read property 'suites' of undefined

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)
notificationsAlerts.ts:40 Test discovery error, please check the configuration settings for the tests.
onDidNotificationChange @ notificationsAlerts.ts:40
console.ts:137 [Extension Host] Python Extension: displayDiscoverStatus TypeError: Cannot read property 'suites' of undefined
	at t.forEach.t (/home/igor/.vscode-server/extensions/ms-python.python-2019.8.30787/out/client/extension.js:75:1015174)
	at Array.forEach (<anonymous>)
	at h.parseNoseTestModuleCollectionResult (/home/igor/.vscode-server/extensions/ms-python.python-2019.8.30787/out/client/extension.js:75:1014343)
	at e.split.forEach (/home/igor/.vscode-server/extensions/ms-python.python-2019.8.30787/out/client/extension.js:75:1013968)
	at Array.forEach (<anonymous>)
	at h.getTestFiles (/home/igor/.vscode-server/extensions/ms-python.python-2019.8.30787/out/client/extension.js:75:1013849)
	at h.parse (/home/igor/.vscode-server/extensions/ms-python.python-2019.8.30787/out/client/extension.js:75:1013661)
	at h.discoverTests (/home/igor/.vscode-server/extensions/ms-python.python-2019.8.30787/out/client/extension.js:75:1012881)
	at process._tickCallback (internal/process/next_tick.js:68:7)

Thanks for letting us know about this, @IBestuzhev.  This sounds similar to a problem with the latest version of pytest (#6990), where the XML output changed.  We use JUnit XML files to get the output from nose.  Was this working on an earlier version of nose?  If so then we can look into that further.
Just in case that isn't the problem, I have some questions that may help us figure out what is going on:

what version of nose are you using?  (Presumably  it is nose2 since nose "1" is effectively EOL.)
what happens when you run the nose directly in the terminal?
what is the command (with args) that you use to do so?
how is the bash script you included above related to running the tests?
what is in your workspace settings.json?

Also note that our support for nose is fairly low, due to lack of demand.  However, that doesn't mean we won't try to help you resolve this issue. :)

Thanks @ericsnowcurrently
Yes, I understand it's quite rare issue, the project is legacy and so it uses not recent versions.

Was this working on an earlier version of nose?

Never checked before.

what version of nose are you using?

nose==1.3.7

what happens when you run the nose directly in the terminal?
what is the command (with args) that you use to do so?

That is Django project, so I can't run nosetests command directly. It fails to import most of the tests and they require django.setup() to be called.
The error is AppRegistryNotReady: Apps aren't loaded yet. And I think it's not relevant to this issue.
But I can run python manage.py test, and this command does some django setup and then runs nosetests --verbosity=2 --with-id
So for test discovery I run ./manage.py test --settings=core.local_settings --verbosity=3 -l nose.selector --nologcapture --collect-only

how is the bash script you included above related to running the tests?

It translates nosetests call to python manage.py test command

what is in your workspace settings.json?

"python.testing.cwd": "/home/igor/project/backend",
"python.testing.nosetestPath": "/home/igor/custom_nose",  # custom bash script
"python.testing.promptToConfigure": false,

@IBestuzhev, we've added a fix for our JUnit XML parsing.  Please see if that fixes the problem.  It is available through the "insiders" build of the extension (set the "python.insidersChannel" in your user settings to "daily").

Hi @ericsnowcurrently
Thanks for letting me know.
I downloaded insiders build and run test discovery.
Nothing changed.
Also, my initial problem was with parsing of Nose output, not JUnit output.

@IBestuzhev, sorry for the confusion.  I was able to reproduce the problem using the steps you originally provided.  It looks like we expect a file to be picked if a class is picked, but that isn't the case here.  In my nose output I see the following:
...
nose.loader: DEBUG: Load from module <module 'tests' from '/home/esnow/projects/work/test_projects/gh-7124/tests/__init__.py'>
nose.selector: DEBUG: wantClass <class 'tests.action.ActionTestCase'>? True
...
nose.selector: DEBUG: wantFile /home/esnow/projects/work/test_projects/gh-7124/tests/action.py? None
...

We'll investigate further.

My full nose output:
$ /usr/bin/python3.7 -m nose --collect-only -vvv tests
nose.config: INFO: Ignoring files matching ['^\\.', '^_', '^setup\\.py$']
nose.plugins.manager: DEBUG: Configuring plugins
nose.plugins.manager: DEBUG: Plugins enabled: [<nose.plugins.capture.Capture object at 0x7f09e6b18748>, <nose.plugins.logcapture.LogCapture object at 0x7f09e6bb30b8>, <nose.plugins.deprecated.Deprecated object at 0x7f09e6b4ef60>, <nose.plugins.skip.Skip object at 0x7f09e68ab4e0>, <nose.plugins.collect.CollectOnly object at 0x7f09e68ab5f8>]
nose.core: DEBUG: configured Config(addPaths=True, args=(), configSection='nosetests', debug=None, debugLog=None, env={}, exclude=None, files=[], firstPackageWins=False, getTestCaseNamesCompat=False, ignoreFiles=[re.compile('^\\.'), re.compile('^_'), re.compile('^setup\\.py$')], ignoreFilesDefaultStrings=['^\\.', '^_', '^setup\\.py$'], include=None, includeExe=False, logStream=<_io.TextIOWrapper name='<stderr>' mode='w' encoding='UTF-8'>, loggingConfig=None, options=<Values at 0x7f09e631a208: {'version': False, 'showPlugins': False, 'verbosity': 4, 'files': None, 'where': None, 'py3where': None, 'testMatch': '(?:^|[\\b_\\./-])[Tt]est', 'testNames': None, 'debug': None, 'debugLog': None, 'loggingConfig': None, 'ignoreFiles': [], 'exclude': [], 'include': [], 'stopOnError': False, 'addPaths': True, 'includeExe': False, 'traverseNamespace': False, 'firstPackageWins': False, 'byteCompile': True, 'attr': None, 'eval_attr': None, 'capture': True, 'logcapture': True, 'logcapture_format': '%(name)s: %(levelname)s: %(message)s', 'logcapture_datefmt': None, 'logcapture_filters': None, 'logcapture_clear': False, 'logcapture_level': 'NOTSET', 'enable_plugin_coverage': None, 'cover_packages': None, 'cover_erase': None, 'cover_tests': None, 'cover_min_percentage': None, 'cover_inclusive': None, 'cover_html': None, 'cover_html_dir': 'cover', 'cover_branches': None, 'cover_xml': None, 'cover_xml_file': 'coverage.xml', 'debugBoth': False, 'debugFailures': False, 'debugErrors': False, 'noDeprecated': False, 'enable_plugin_doctest': None, 'doctest_tests': None, 'doctestExtension': None, 'doctest_result_var': None, 'doctestFixtures': None, 'doctestOptions': None, 'enable_plugin_isolation': None, 'detailedErrors': None, 'noSkip': False, 'enable_plugin_id': None, 'testIdFile': '.noseids', 'failed': False, 'multiprocess_workers': 0, 'multiprocess_timeout': 10, 'multiprocess_restartworker': False, 'enable_plugin_xunit': None, 'xunit_file': 'nosetests.xml', 'xunit_testsuite_name': 'nosetests', 'enable_plugin_allmodules': None, 'collect_only': True}>, parser=<optparse.OptionParser object at 0x7f09e837e7b8>, parserClass=<class 'optparse.OptionParser'>, plugins=<nose.plugins.manager.DefaultPluginManager object at 0x7f09e837e3c8>, py3where=(), runOnInit=True, srcDirs=('lib', 'src'), stopOnError=False, stream=<_io.TextIOWrapper name='<stderr>' mode='w' encoding='UTF-8'>, testMatch=re.compile('(?:^|[\\b_\\./-])[Tt]est'), testMatchPat='(?:^|[\\b_\\./-])[Tt]est', testNames=['tests'], traverseNamespace=False, verbosity=4, where=(), worker=False, workingDir='/.../gh-7124')
nose.importer: DEBUG: Add path /.../gh-7124
nose.plugins.collect: DEBUG: Preparing test loader
nose.core: DEBUG: test loader is <nose.loader.TestLoader object at 0x7f09e631a358>
nose.core: DEBUG: defaultTest .
nose.core: DEBUG: Test names are ['tests']
nose.core: DEBUG: createTests called with None
nose.loader: DEBUG: load from tests (None)
nose.selector: DEBUG: Test name tests resolved to file tests, module None, call None
nose.selector: DEBUG: Final resolution of test name tests: file /.../gh-7124/tests module tests call None
nose.importer: DEBUG: Import tests from /.../gh-7124
nose.importer: DEBUG: Add path /.../gh-7124
nose.importer: DEBUG: find module part tests (tests) in ['/.../gh-7124']
nose.loader: DEBUG: Load from module <module 'tests' from '/.../gh-7124/tests/__init__.py'>
nose.selector: DEBUG: wantClass <class 'tests.action.ActionTestCase'>? True
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.addCleanup>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.addTypeEqualityFunc>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.assertAlmostEqual>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.deprecated_func>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.assertCountEqual>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.assertDictContainsSubset>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.assertDictEqual>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.assertEqual>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.deprecated_func>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.assertFalse>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.assertGreater>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.assertGreaterEqual>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.assertIn>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.assertIs>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.assertIsInstance>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.assertIsNone>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.assertIsNot>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.assertIsNotNone>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.assertLess>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.assertLessEqual>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.assertListEqual>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.assertLogs>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.assertMultiLineEqual>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.assertNotAlmostEqual>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.deprecated_func>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.assertNotEqual>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.deprecated_func>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.assertNotIn>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.assertNotIsInstance>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.assertNotRegex>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.deprecated_func>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.assertRaises>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.assertRaisesRegex>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.deprecated_func>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.assertRegex>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.deprecated_func>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.assertSequenceEqual>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.assertSetEqual>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.assertTrue>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.assertTupleEqual>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.assertWarns>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.assertWarnsRegex>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.deprecated_func>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.countTestCases>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.debug>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.defaultTestResult>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.doCleanups>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.fail>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.deprecated_func>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.deprecated_func>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.deprecated_func>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.deprecated_func>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.deprecated_func>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.deprecated_func>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.deprecated_func>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.id>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.run>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.setUp>? None
nose.selector: DEBUG: wantMethod <bound method TestCase.setUpClass of <class 'tests.transplant_class.<locals>.C'>>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.shortDescription>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.skipTest>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.subTest>? None
nose.selector: DEBUG: wantMethod <unbound method ActionTestCase.tearDown>? None
nose.selector: DEBUG: wantMethod <bound method TestCase.tearDownClass of <class 'tests.transplant_class.<locals>.C'>>? None
nose.plugins.collect: DEBUG: TestSuite(<map object at 0x7f09e631a9b0>)
nose.loader: DEBUG: Load tests from module path /.../gh-7124/tests?
nose.loader: DEBUG: path: /.../gh-7124/tests os.path.realpath(/.../gh-7124/tests): /.../gh-7124/tests
nose.loader: DEBUG: load from dir /.../gh-7124/tests
nose.importer: DEBUG: Add path /.../gh-7124/tests
nose.importer: DEBUG: Add path /.../gh-7124
nose.selector: DEBUG: __init__.py matches ignoreFiles pattern; skipped
nose.selector: DEBUG: wantFile /.../gh-7124/tests/action.py? None
nose.plugins.collect: DEBUG: TestSuite(<nose.suite.ContextList object at 0x7f09e631a9b0>)
nose.plugins.collect: DEBUG: Add test <nose.plugins.collect.TestSuite tests=[]>
nose.plugins.collect: DEBUG: TestSuite([<nose.plugins.collect.TestSuite tests=[<nose.plugins.collect.TestSuite tests=[]>]>])
nose.plugins.collect: DEBUG: Add test <nose.plugins.collect.TestSuite tests=[<nose.plugins.collect.TestSuite tests=[]>]>
nose.core: DEBUG: runTests called

----------------------------------------------------------------------
Ran 0 tests in 0.000s

OK

I'm experiencing a similar (or same) issue. Also using nose 1.3.7, but on Python 3.7, macOS 10.15, and VSCode 1.45.0.
@IBestuzhev your shell script idea worked for me, although I modified it to work on macOS. Thanks!

Closing via #16371


retroarch menu orientation is wrong.

Hi,
When I load up the retroarch menu, on the egret mini 2, in game, the orientation is the opposite to what it should be.
When playing a game like street fighter in its correct screen orientation and I hit the hotkey + B, the menu is sideways,
adjusting the screen so its then vertical makes the menu the correct way up but doesn't display properly.
I have added in the following configuration as per the documentation
`global.retroarch.input_rotate_landscape_btn = "14"
global.retroarch.input_rotate_portrait_btn = "15”`
UPDATE: I just noticed that display.rotate=1, If I disable that then play with the screen I can get the retroarch menu to display the correct orientation temporarily

Thanks, yes, it needs to be fixed but it wasn't ready for the alpha. Will be fixed later on a beta release.
Note that if you manually modify the display.rotate you are going to break the auto rotation capability. So while that works to temporarily show the menu correctly it has several side effects.

Current fix: pop the screen out and rotate while you work through the menu (while the screen is popped out) - then return screen to its orientation, get back in the game.

Thanks, however when I do this the menu is upside down.On 6 Jan 2023, at 10:20 am, NeoCverA @.***> wrote:
Current fix: pop the screen out and rotate while you work through the menu (while the screen is popped out) - then return screen to its orientation, get back in the game.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

I just change the menu driver to "rgui" on retroarchcustom.cfg, and it works perfectly!


vtpm fix : use domain uuid instead of full domain name

Domain name contains UUID, version and app number,the version number might get changed, so use only the
UUID part to preserve the vtpm state.

This PR is based on a observation in @OhmSpectator code comment :

each time the configuration is changed, it updates the domain name, increasing the counter after UUID

I'll be happy if someone point me to part of the code that actually makes this change to ~app~ version number, I couldn't find it myself.

I'll be happy if someone point me to part of the code that actually makes this change to app number, I couldn't find it myself.

Config Num comes from the cloud. They increase it with each config update.

The virtualization test suite has failed three times. Strange.

Yeah, it looks like something is broken...
[stdout]
Docker app's state test
=== RUN   TestAppStatus
apps: '[eclient]' state: 'RUNNING' secs: 1800
time: 2024-09-19T02:04:00.913252133Z out: 	appName eclient state changed to UNKNOWN
time: 2024-09-19T02:04:03.570037979Z out: 	appName eclient state changed to RESOLVING_TAG
time: 2024-09-19T02:04:04.570522093Z out: 	appName eclient state changed to DOWNLOAD_STARTED
time: 2024-09-19T02:04:05.571844887Z out: 	appName eclient state changed to DOWNLOAD_STARTED (0%)
time: 2024-09-19T02:04:08.574364348Z out: 	appName eclient state changed to DOWNLOAD_STARTED (11%)
time: 2024-09-19T02:04:08.574380459Z out: 	appName eclient state changed to DOWNLOAD_STARTED (23%)
time: 2024-09-19T02:04:09.57494185Z out: 	appName eclient state changed to DOWNLOAD_STARTED (64%)
time: 2024-09-19T02:04:09.574978076Z out: 	appName eclient state changed to LOADING
time: 2024-09-19T02:04:10.576055852Z out: 	appName eclient state changed to CREATING_VOLUME
time: 2024-09-19T02:04:14.578651073Z out: 	appName eclient state changed to INSTALLED
time: 2024-09-19T02:04:15.579136424Z out: 	appName eclient state changed to BOOTING
time: 2024-09-19T02:05:54.653641582Z out: 	appName eclient state changed to HALTING: [description:"Giving up waiting to connect to QEMU Monitor Protocol socket /run/hypervisor/kvm/7418b0e3-96e3-4e0f-b977-3720d7464f1c.1.1/qmp from VM 7418b0e3-96e3-4e0f-b977-3720d7464f1c.1.1, error: [attempt 1] qmp status failed for QMP socket '/run/hypervisor/kvm/7418b0e3-96e3-4e0f-b977-3720d7464f1c.1.1/qmp': err: 'dial unix /run/hypervisor/kvm/7418b0e3-96e3-4e0f-b977-3720d7464f1c.1.1/qmp: connect: connection refused'; (JSON response: ''); [attempt 2] qmp status failed for QMP socket '/run/hypervisor/kvm/7418b0e3-96e3-4e0f-b977-3720d7464f1c.1.1/qmp': err: 'dial unix /run/hypervisor/kvm/7418b0e3-96e3-4e0f-b977-3720d7464f1c.1.1/qmp: connect: connection refused'; (JSON response: ''); [attempt 3] qmp status failed for QMP socket '/run/hypervisor/kvm/7418b0e3-96e3-4e0f-b977-3720d7464f1c.1.1/qmp': err: 'dial unix /run/hypervisor/kvm/7418b0e3-96e3-4e0f-b977-3720d7464f1c.1.1/qmp: connect: connection refused'; (JSON response: '')" timestamp:{seconds:1726711530 nanos:262492703} severity:SEVERITY_ERROR]
time: 2024-09-19T02:15:47.104054215Z out: 	appName eclient state changed to BOOTING
time: 2024-09-19T02:17:26.189625019Z out: 	appName eclient state changed to HALTING: [description:"Giving up waiting to connect to QEMU Monitor Protocol socket /run/hypervisor/kvm/7418b0e3-96e3-4e0f-b977-3720d7464f1c.1.1/qmp from VM 7418b0e3-96e3-4e0f-b977-3720d7464f1c.1.1, error: [attempt 1] qmp status failed for QMP socket '/run/hypervisor/kvm/7418b0e3-96e3-4e0f-b977-3720d7464f1c.1.1/qmp': err: 'dial unix /run/hypervisor/kvm/7418b0e3-96e3-4e0f-b977-3720d7464f1c.1.1/qmp: connect: connection refused'; (JSON response: ''); [attempt 2] qmp status failed for QMP socket '/run/hypervisor/kvm/7418b0e3-96e3-4e0f-b977-3720d7464f1c.1.1/qmp': err: 'dial unix /run/hypervisor/kvm/7418b0e3-96e3-4e0f-b977-3720d7464f1c.1.1/qmp: connect: connection refused'; (JSON response: ''); [attempt 3] qmp status failed for QMP socket '/run/hypervisor/kvm/7418b0e3-96e3-4e0f-b977-3720d7464f1c.1.1/qmp': err: 'dial unix /run/hypervisor/kvm/7418b0e3-96e3-4e0f-b977-3720d7464f1c.1.1/qmp: connect: connection refused'; (JSON response: '')" timestamp:{seconds:1726712221 nanos:781452343} severity:SEVERITY_ERROR]
time: 2024-09-19T02:27:09.631665355Z out: 	appName eclient state changed to BOOTING
time: 2024-09-19T02:28:48.707869707Z out: 	appName eclient state changed to HALTING: [description:"Giving up waiting to connect to QEMU Monitor Protocol socket /run/hypervisor/kvm/7418b0e3-96e3-4e0f-b977-3720d7464f1c.1.1/qmp from VM 7418b0e3-96e3-4e0f-b977-3720d7464f1c.1.1, error: [attempt 1] qmp status failed for QMP socket '/run/hypervisor/kvm/7418b0e3-96e3-4e0f-b977-3720d7464f1c.1.1/qmp': err: 'dial unix /run/hypervisor/kvm/7418b0e3-96e3-4e0f-b977-3720d7464f1c.1.1/qmp: connect: connection refused'; (JSON response: ''); [attempt 2] qmp status failed for QMP socket '/run/hypervisor/kvm/7418b0e3-96e3-4e0f-b977-3720d7464f1c.1.1

I'll be happy if someone point me to part of the code that actually makes this change to app number, I couldn't find it myself.

Config Num comes from the cloud. They increase it with each config update.

It is the version number (and not the app number) which is changed, right? If so it makes sense to update the PR description.

@shjala, will you take a look at why the same Eden test fails all the time?

@shjala, will you take a look at why the same Eden test fails all the time?

All are green except virtualization, do you mean that or there is more?

Yeah, I mean that one. I don't see the same test failing in other PRs all the time. Maybe it's just a coincidence, but it's better to check.

@OhmSpectator should be fixed now, rerun?

All green! What exactly have you done? Just rebase?

All green! What exactly have you done? Just rebase?

Eden rerun is appreciated.


Java Eclipse based projects

Pull Request
Update

[x] Template - Update existing .gitignore template

Details
According to the Eclipse documentation.
These files should keep in tracking.

This is a very old (Nov 7, 2013) and controversial topic, but these are going to remain in the templates.
https://github.com/github/gitignore/pull/805
https://github.com/github/gitignore/pull/1304
https://github.com/github/gitignore/pull/1217#issuecomment-69902666


Update view-transitions.mdx

Not 100% sure about these changes, but I figured might as well see what y'all think.

Description (required)

Remove code block in ### Transitions with forms because it does not add any value ( in my opinion )

Add tip to ### Transitions with forms about event.preventDefault() because this was not obvious to me personally

Add tip to ## Script behavior during page navigation about DOMContentLoaded ( struggled with the wording here, not sure if it is the best, potentially could remove this tip altogether ) because this is a very common question in the discord

Add link to Update Scripts Tutorial in ## Script behavior during page navigation because this is a very valuable resource that most don't seem to find and is relevant to this section

Hey @OliverSpeir , thanks so much for hopping in here, and just a quick note to let you know this is now finally on my plate for this week!
One reason I haven't yet looked over this is because I know it's going to take a bit of time/work, and I'll let you in on a little secret how I know: suggestions that add "tips" are almost never the right way to go about adding new information... and you added two of them!  :sweat_smile:
Asides should almost always be left to truly tangential information. If I let everyone add their idea in a note or a tip or a caution, then that's all docs would be.. people tacking on notes all over the place! Without even reading your submission, what this tells me is we need some content rework here so that the necessary information is actually part of our text: if we say things right the first time, then we don't NEED flashy tips pointing things out!
So, that's why this one has taken me a while to return to (not a "quick win" for me during a busy launch week), and I'll be spending time on this before the weekend for sure!

Makes sense! I figured as much 😅

Thanks for your patience @OliverSpeir ! I tried to rework the content into the text here. Please check this for accuracy and make any corrections, and let's see whether we can get your content incorporated in more like this kind of style/structure!

Love it,
I reworded to clarify both post and get methods will transition the page

Fantastic! Happy with this one! 🥳


Issue/PR labels arc-green contrast issue introduced by #13181

Gitea version (or commit ref): Gitea version 1.14.0+dev-56-ge964c6ec1 built with GNU Make 4.3, go1.15.3 : bindata, sqlite, sqlite_unlock_notify
Git version: git version <IP_ADDRESS>1.g38ddec7408
Operating system: Arch Linux
Built from source:

[x] Yes

Run with:

[x] systemd

Database:

[x] SQLite

Can you reproduce the bug at https://try.gitea.io:

[x] No

Description
I just recently noticed there has been a change to how labels are displayed in Issue/PR feeds when using arc-green theme.
Colourful labels are gone due to an addition from #13181 , precisely - file theme-arc-green.less, line 622.
This overrides the labels original colours and everything now looks grim.
While I understand the line was added for a reason, this was most certainly was not it.
Screenshots
now - grim:

before - colourful:

ping @ivanvc

And now we see why !important is a bad idea...

Darn, I had to add !important as another style was overriding the color for the labels I added. I can take this issue :D


Use standard Vert.x config

We don't need an extra dependency and our needs in terms of config are very minimum.

We'd need couple of more items for s3 upload, but vert.x configuration should be fine


Add Align Option

I made an app with wallpapers. I want to support it through many device that's why the wallpapers are large in width. Is it not possible to add a little option to align the Wallpaper to Left, Center and Right? So,the wallpaper's main subject will not get cut.
I don't know if this feature was requested before. Although, Thanks for making app like this.

It

Yup, duplicate of #13, #62, and #64


Create Telegram Bot documentation

The Telegram bot has many configurability and commands that need to be documented

Wiki for the Telegram bot created https://github.com/nminaya/grammar-nazi-bot/wiki/GrammarNazi-Telegram-Bot


Initializer from endpoint specs directory

The initializer for SapiClient Application currently takes a path to the sapi-nt application.yml configuration file
This YAML file is parsed and the sapi-nt.config.loadSpecPath path is read, any classpath ignored and the resulting directory used to find all endpoint configuration YAML files used to create proxy Ruby classes and methods.
See https://github.com/epimorphics/sapi-client-ruby/blob/main/lib/sapi_client/application.rb
In order to separate out these endpoint configuration files, we would like to provide a way to initialize the SapiClient Application directly with this spec path directory.
Proposal: keep backward compatibility by still allowing a path to application.yml; check whether the path is a directory or file; if a directory, just use directly for endpoint_group_files.

I'm marking this as fixed as the test suite includes parallel checks for initializing with the endpointSpecs directory. The functionality still needs to be tried out as part of epimorphics/fsa-rpa-api#13.


Adding info about Dependency Caching to docs

Proposed changes

Adding infromation about Dependency Caching

Unreleased product version (optional)

Related issues (optional)

https://github.com/pulumi/pulumi-service/issues/20210
https://github.com/pulumi/pulumi-service/issues/20211

Updated according to comments

Updated according to comments, thank you for detailed feedback!


Added update_parameters to EMA to fix calculation

Resolves https://github.com/pytorch/vision/issues/4391.
Output logs:
resnext101_32x8d_training_log_ema_fix.txt
resnet18_training_log_ema_fix.txt
cc @datumbox

this

Makes sense. Will follow-up on this.

LGTM, thanks Prabhat.
As @kazhang this is an issue on PyTorch core. Ideally the base class should include all state not just the params. We use a similar approach in other averaging schemes (see this) so this is aligned to what we've seen in the past. Though this workaround will do for our use-case, I think it's still worth raising it on PyTorch core and either correcting it or introducing better control over which params we should consider.

Makes sense. Will follow-up on this.


Remaining variables issues

[x] moving variable blocks above variable defs can cause program to lock
[ ] set [name] to... blocks should not have anything selected to start.  item can still be pre-populated.  This prevents weirdness. (Possible that future improvements could make this moot)
[ ] change wording for selecting vector components from all to vector in dropdown

This one wasn't on the board so may have gotten overlooked.  I set it as a todo there.  We can add repro steps when we groom.

This bug occurred because of how the onChange  function was written and called. On a previous pull request I disabled onChange as it was making coding and test every other bug frustrating. It may be more appropriate to make a task or story to build a comprehensive real time type update system. We can talk more about it Monday

@hgclose the newest bullet is in reference to the discussion we had previously about changing confusing language when referring to vectors and there components in the "get" and "set" variable blocks from just all to vector. Do you still agree with this solution?

yes, I agree

@hgclose during the process of programming get and set blocks with no defaults it became apparent that writing a block that was disabled until you made a selection was going to be about the same difficult as making a block that automatically detects its assigned type and updates. @eah13 I have a feature branch that I was going to finish the auto type updating set block on, but it closes the original issues of this task and I don't think any of the bugs left are program breaking. I'm not sure what our process dictates we should do with the 'issue', but I think what is left to do is try and build programs and find logical inconsistencies with how we think they should behave and fix them. We can talk more about it today


adding spanish to the translate languages

Excellent. Thank you very much!
If possible I am inclined to name the file english_to_espanol.py and the internal dictionary ENG_ESPANOL to be consistent with the native language spelling of the existing translators. What do you think?
Also within the translation dictionary, do you think it would it be preferable to include the missing accent characters for CALIBRACIÓN, ESPAÑOL, INVÁLIDO, and MÁXIMO?
I appreciate your help with the translation. It will certainly help make the library more useful.

Hello, yes you are right and correct, the discussion if you need to to put accent in Capital letters is older than me... :)
https://www.rae.es/noticia/preguntas-frecuentes-tilde-en-las-mayusculas
I think I am just use not to.
I made the changes according to your recommendations. :)

Ah, I wasn't aware that accents on all caps had been debated. Good to know.
Again, thank you for the submission. I'll run the workflow and merge the changes later tonight. It'll be great to have Spanish added my portable quality tester.

There's an issue with the cookiecutter-generated Community Bundle CI, so I'll create a release using the source code from this pull request.

No worries, have a lot of trouble figuring out regarding the CI, last week. If there is anything I can do to help let me know.

Thanks for the offer to help; Git isn’t strongly represented in my vocabulary yet. @tekktrik is going to submit a PR to each of my Community Bundle source repos with the current library CI update. Hopefully that’ll do the trick.

LOL, it seems that you need ENG_GIT dictionary  as I do :)

Indeed!


add -p as first-run flag

Without using -p the first time, no output occurs, so you're not sure that things are setup or working. If it's logging someplace, it's not indicated where in the documentation nor is it in the current working directory.

Nice!


Dynamic Course Configurable EC calculation

Note: This PR is coupled with the corresponding sensai changes which use the added API endpoints.
API changes:

Add new API endpoint for bot to use to submit liked meme events
Add new API endpoint for bot to use to submit thanks events
Add new API endpoint for bot to get individual thanks count
Add new API endpoint for bot go get individual memes count
Add new API endpoint for obtaining thanks leaderboard

DB changes:

Adds DiscordUserActivity, a generic table tracks actions users can apply to each other such as liking memes or thanking each other
Adds several methods to DiscordUser to query DiscorduserActivity
Adds start_date to Dojo object, which currently returns first earliest visible module as a proxy for course start

Course Grades page Changes

Adds assignment type helpfulness and memes

Both of these have an optional, but necessary max_credit property

sets individual max limits if course requires
Default is 1.00 max (100% of course)

helpfulness has a functionally required method property identifying the calculation method to use

Current valid values:

1337log2 uses 1.337 ** log2(thanks) / 100 with a hard cap of max_credit` if set
log50 uses log50 approaching the max_credit value

Adds course.yml course level property ec_limit

Serves as a dynamic global cap on all extra credit (thanks, memes, and extra)
Extra credit values on the grades page will be dynamically reduced to ensure total cannot exceed this threshold

Adds dynamic progress indicators for helpfulness (total count) and memes (week ranges)
Meme and helpfulness grade time frames are calculated as dojo.start_date (described above) to start_date + 16 weeks

I believe this setup is sufficient to represent all currently live ASU EC scenarios based on course syllabus.

Oh yeah.. and I also made DiscordUser IDs numbers.. because they are.

I have no authority to approve this, but LGTM other than that one apparent typo for the thanks leaderboard calc!

Couple things I realized this morning I need to address before merging.

[ ]  DiscordAction Timestamp is "time of action", but we also want "time of target message" (ex: when meme was posted)
[ ]  Similarly, the meme grade calculation should use "time of message", not "time of action"
[ ]  Do we want thanks calculation to be "time of message" as well?  Less important, but that'd be consistent
[ ]  Update memes and thanks queries to be unique on message_id or (channel_id, message_id).  I do think it's worth storing duplicate actions in the DB for accurate data, but de-duping for grades.

Agree with the first 3 of these. Although I'm not sure what purpose the last point has? AFAICT, all discord message ids are unique, even between channels, so being unique on just message_id should be sufficient?

Agree with the first 3 of these. Although I'm not sure what purpose the last point has? AFAICT, all discord message ids are unique, even between channels, so being unique on just message_id should be sufficient?

From the Discord API docs
These IDs are guaranteed to be unique across all of Discord, except in some unique scenarios in which child objects share their parent's ID.

You're probably correct that just being distinct on message _id is sufficient.  I was not aware the discord guaranteed uniqueness across all of discord (mostly).

@ConnorNelson any thoughts?  I'd like merge this in late tonight.

YOLO


Downloads on On-demand assessement page not working

Describe the bug
Download on page not working
To Reproduce
Steps to reproduce the behavior:

Go to https://docs.microsoft.com/en-us/services-hub/health/assessment-prereq-docs
Click on Microsoft Azure
New window opens to https://opdhsblobprod04.blob.core.windows.net/contents/3832eb6e467d45c4aed5538d8c2d8797/84eea9aa481b09e0efc3f4afaeca1d06?sv=2018-03-28&sr=b&si=ReadPolicy&sig=RSGLrkHF0PH1tlCQ2q4mNT70rAxWcNODJJX%2BAujBYwE%3D&st=2020-04-08T17%3A50%3A28Z&se=2020-04-09T18%3A00%3A28Z
White page

Expected behavior
Download of a document
Screenshots
If applicable, add screenshots to help explain your problem.

Issue is only on one of my computers.. perhaps being blocked by some mechanisme there. Anyway.. I can access the docs from another computer, so most probably an incident.. Will close this issue.


METRON-570 Add Profiler Link to README

METRON-570
There was no link from the project's root README for user to find information on the Profiler.  Fix'd'it

+1


"Sign in with Slack" is unsupported by Bolt and its underlying OAuth module

Description
Currently, I am developing a slack app, build with bolt. I have implemented OAuth as suggested here. So, naturally bolt has created this endpoint /slack/install for installing and authorizing the slack app into a workspace, when I (the creator) click it and try to authorize it, it works perfectly fine, however from time to time with some small issuers, but when somebody else from the exterior does it, it always throws an error: Something went wrong when authorizing this app.. Logs:
[DEBUG]  web-api:WebClient:0 initialized
[DEBUG]  web-api:WebClient:0 apiCall('oauth.v2.access') start
[DEBUG]  web-api:WebClient:0 will perform http request
[DEBUG]  web-api:WebClient:0 http response received
[DEBUG]  web-api:WebClient:1 initialized
[DEBUG]  web-api:WebClient:1 apiCall('auth.test') start
[DEBUG]  web-api:WebClient:1 will perform http request
[DEBUG]  web-api:WebClient:1 http response received
[DEBUG]  web-api:WebClient:2 initialized
[DEBUG]  web-api:WebClient:2 apiCall('auth.test') start
[DEBUG]  web-api:WebClient:2 will perform http request
[DEBUG]  web-api:WebClient:2 http response received
[ERROR]  OAuth:InstallProvider:0 Error: An API error occurred: invalid_auth
    at Object.platformErrorFromResult (/path-to-/node_modules/@slack/web-api/dist/errors.js:51:33)
    at WebClient.apiCall (/path-to-/node_modules/node_modules/@slack/web-api/dist/WebClient.js:158:28)
    at processTicksAndRejections (internal/process/task_queues.js:93:5) {
  code: 'slack_webapi_platform_error',
  data: {
    ok: false,
    error: 'invalid_auth',
    response_metadata: { scopes: [Array] }
  }
}
[DEBUG]  OAuth:InstallProvider:0 calling passed in options.failure

What type of issue is this? (place an x in one of the [ ])

[x] bug
[ ] enhancement (feature request)
[x] question
[ ] documentation related
[ ] example code related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report
Here is the code:
import { App, LogLevel, ExpressReceiver } from '@slack/bolt';
import { Low, JSONFile } from 'lowdb';
import { join } from 'path';
import { sendWelcomeMessage } from './views/messages.js';
import { createUserProfile } from './auth/authGetTilo.js';
import { newUserHomePage } from './views/homePage.js';

const file = join('./db.json');
const adapter = new JSONFile(file);
const db = new Low(adapter);

const receiver = new ExpressReceiver({
  signingSecret: process.env.SLACK_SIGNING_SECRET,
  logLevel: LogLevel.DEBUG,
  clientId: process.env.SLACK_CLIENT_ID,
  clientSecret: process.env.SLACK_CLIENT_SECRET,
  stateSecret: 'someStateSecret',
  scopes: ['commands', 'chat:write'],
  installationStore: {
    storeInstallation: async (installation) => {
      // change the line below so it saves to your database
      console.log('installation', installation);
      await db.read();
      db.data = db.data || {};
      db.data.installation = installation;
      await db.write();
      // save to db

      sendWelcomeMessage(app, installation);
      createUserProfile(app, installation, db)
    },
    fetchInstallation: async (installQuery) => {
      // change the line below so it fetches from your database
      console.log('installQuery', installQuery);
      await db.read();
      if (db.data.installation) {
        return db.data.installation;
      }

      throw new Error('Failed fetching installation');
    },
    deleteInstallation: async (installQuery) => {
      // change the line below so it deletes from your database
    },
  },
  installerOptions: {
    userScopes: ['identity.basic', 'identity.email'],
    callbackOptions: {
      success: (installation, installOptions, req, res) => {
        res.end('success');
      },
      failure: (error, installOptions, req, res) => {
        res.end('failure');
      },
    },
  },
});

const app = new App({ receiver });

// All the room in the world for your code
app.event('app_home_opened', params => newUserHomePage(params, db));

(async () => {
  // Start your app
  await app.start(process.env.PORT || 3000);

  console.log('⚡ Bolt app is running!');
})();

please ignore the LowDB part, it's just for testing
Reproducible in:
package version: "^3.5.0"
node version: v14.13.1
OS version(s): macOS Big Sur
Expected result:
Users are able to correctly authorize the app
Actual result:
An error is being thrown, without any message on how to solve it

Hi @justman00, thanks for asking the question!

userScopes: ['identity.basic', 'identity.email'],

Your app cannot have identity.* user scopes along with others such as commands. When your app has those, only identity.* should be passed to the authorize URL. If you need some user token scopes, other user scopes can co-exist with bot scopes.
Also, we've recently renewed "Sign in with Slack" to make it compatible with OpenID Connect. The new way requires openid, email (optional), profile (optional) instead of identity.*. If you are building a new app using "Sign in with Slack" functionality, consider the latest one for it. https://api.slack.com/authentication/sign-in-with-slack
I hope this was helpful to you!

I did remove the commands scope but the issue seems to be happening still, after revoking my own access, I can reproduce this all the time

Hi @justman00, I checked this issue today and found that @slack/bolt and its underlying @slack/oauth package does not support "Sign in with Slack" feature at this moment.
We may update the package to support the functionality in the future (we haven't decided it yet) but in the short term, please consider implementing the "Sign in with Slack" flow on your own. The code should be quite simple. Here is a simple example app built with Koa: https://github.com/slackapi/node-slack-sdk/pull/1310
I hope this was helpful to you.

thank you @seratch looking forward to what's next for the bolt framework and its integrations

@seratch Quick heads-up that the Slack API documentation for the new OpenID method openid.connect.token is inaccurate (see screenshot).

The App Review team already asked us to update our sign-in with the new OpenID tokens but this means that we have to do a manual post request (we do everything with BoltJS until now) and then later change again if Bolt 3.11.0 comes out 😅

@ErwinAI Indeed, the "Powered by Bolt" part is incorrect but it just means that client.openid.connection.token({ ... }) is available in your App instance.
We still have this task in the milestone v3.11 now. However, probably we have to move it to v3.12 or newer version. We are mainly working on other OAuth related improvements in the release and it still requires my time.
For the time being, please consider going with your own implementation that directly use the underlying API client. Here is an example for the OpenID Connect compatible one: https://github.com/slackapi/node-slack-sdk/blob/main/examples/openid-connect/app.js
That being said, I understand that, if bolt-js supports it out-of-the-box, it's much simpler and easier-to-maintain for developers. We will work on the enhancement in the near future.

Hi @seratch Any updates on this feature ? When can we expect it ?

Hi @SujayPrabhu96, no updates on this so far. Also, we may not be able to work on it for a while due to our priorities.
Implementing your server-side for "Sign in with Slack" is relatively simple. So, if you need to add the feature to your app right now, please consider having additional code like this. If you want to add it to your existing bolt-js app, implementing OpenID Connect handlers as custom routes is an option too.

Great, thank you @seratch