Update azure-sql-database-limitations.md

update a note that reminder when setting cross-tenant mirroring, still the error message will only show some generic interal error instead showing cross-tenant is not supported.
Thank you for contributing to Microsoft Fabric documentation
Fill out these items before submitting your pull request:
If you are working internally at Microsoft:
Provide a link to an Azure DevOps Boards work item that tracks this feature/update.

N/A, the update is meant to reminder users that when they seeing internal connection error for mirroring, still it may caused by cross-tenant is not supported

Who is your primary Skilling team contact? @mention them individually tag them and let them review the PR before signing off.

<EMAIL_ADDRESS>
For internal Microsoft contributors, check off these quality control items as you go

[x] 1. Check the Acrolinx report: Make sure your Acrolinx Total score is above 80 minimum (higher is better) and with no spelling issues. Acrolinx ensures we are providing consistent terminology and using an appropriate voice and tone, and helps with localization.

[x] 2. Successful build with no warnings or suggestions: Review the build status to make sure all files are green (Succeeded).

[x] 3. Preview the pages:: Click each Preview URL link to view the rendered HTML pages on the review.learn.microsoft.com site to check the formatting and alignment of the page. Scan the page for overall formatting, and look at the parts you edited in detail.

[x] 4. Check the Table of Contents: If you are adding a new markdown file, make sure it is linked from the table of contents.

[x] 5. #sign-off to request PR review and merge: Once the pull request is finalized and ready to be merged, indicate so by typing #sign-off in a new comment in the Pull Request. If you need to cancel that sign-off, type #hold-off instead. Signing off means the document can be published at any time. Note, this is a formatting and standards review, not a technical review.

Merge and publish

After you #sign-off, there is a separate PR Review team that will review the PR and describe any necessary feedback before merging.
The review team will use the comments section in the PR to provide feedback if changes are needed. Address any blocking issues and sign off again to request another review.
Once all feedback is resolved, you can #sign-off again. The PR Review team reviews and merges the pull request into the specified branch (usually the main branch or a release- branch).
From the main branch, the change is merged into the live branch several times a day to publish it to the public learn.microsoft.com site.

@WilliamDAssafMSFT
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Thanks @AraragiRyou for contacting Microsoft with a contribution to our product documentation. It could take from a few business days to a few weeks to confirm this error message internally for all use cases. Standby.
By opening a pull request, you're helping the authors add your approved change directly to the documentation. If the article is updated with your commit, GitHub will list you as an article contributor.
Thanks again for this feedback. Your suggestions help improve our documentation.


GLPI 10.0.12 --> Error 500 on plugin page

Hello,
Since I've update my GLPI to 10.0.12, when I click on "Plugins" on left side bar, I have an error 500.
Maybe @DonutsNL your fork is not update for 10.0.12 version ?
Thanks for you help.

In my php-errors.log I have :
[2024-02-05 21:59:30] glpiphplog.ALERT:   *** PHP Compile Error (64): Cannot redeclare plugin_version_phpsaml() (previously declared in /var/www/html/glpi/plugins/phpsaml.bak/setup.php:61) in /var/www/html/glpi/plugins/phpsaml/setup.php at line 56
[2024-02-05 21:59:54] glpiphplog.WARNING:   *** PHP User Warning (512): plugin_version_phpsaml.bak method must be defined! in /var/www/html/glpi/src/Plugin.php at line 1810
Backtrace :
src/Plugin.php:1810                                trigger_error()
src/Plugin.php:1848                                Plugin::getInfo()
src/Plugin.php:517                                 Plugin->getInformationsFromDirectory()
src/Plugin.php:786                                 Plugin->getPluginInformation()
src/Plugin.php:570                                 Plugin->getNewInfoAndDirBasedOnOldName()
src/Plugin.php:505                                 Plugin->checkPluginState()
front/plugin.php:43                                Plugin->checkStates()
public/index.php:82                                require()

Enable or disable (toggle) the message and response compression in the settings in the config.class.php.

I did this :
public const CMPREQ     = true; // Compress requests
public const CMPRES     = true; // Compress response
but I have now this :

It's now a duplicate ticket of #161 and #164 so I'm closing this one and following one of them.
Thanks for your help !


Running new lxc containers does not automatically set env or mounts

$ /bin/linux/aarch64/scope run -- lxc ls
ERROR: ld.so: object 'libscope.so' from /etc/ld.so.preload cannot be preloaded (failed to map segment from shared object): ignored.
(same result with LD_PRELOAD or ld.so.preload)
$ LD_DEBUG=libs lxc ls
results in numerous symbol errors. a few examples:
calling init: /lib/libscope.so
 20015:	/lib/libscope.so: error: symbol lookup error: undefined symbol: SSL_read (fatal)
 20015:	/lib/libscope.so: error: symbol lookup error: undefined symbol: SSL_write (fatal)
 20015:	/lib/libscope.so: error: symbol lookup error: undefined symbol: SSL_get_fd (fatal)

 20015:	/lib/libscope.so: error: symbol lookup error: undefined symbol: PR_SetError (fatal)

 20015:	/lib/libscope.so: error: symbol lookup error: undefined symbol: uv__read (fatal)

 20015:	/lib/libscope.so: error: symbol lookup error: undefined symbol: uv_fileno (fatal)

other libs exhibit symbol errors, such as librt. however, are not preloaded.

Poking around a bit with this. There are 2 independent issues:

The lxc exec is a script which execs /snap/bin/lxc and that is a soft link; /snap/bin/lxc -> lxd.lxc,
that, in turn, is a link; /snap/bin/lxd.lxc -> /usr/bin/snap.
It is the start of lxd.lxc that causes the ld.so issue with loading libscope
An lxc container is started using lxd and not containerd. Therefore, runc is not exec'd. Therefore, we don't attempt to update config.json for the new container.


Query hangs unpredictably

Environment

Python: 3.7 (32-bit)
pyodbc:  4.0.30
OS: Windows 10
DB: SQL Server 2019
driver: ODBC Driver 17

Issue
I have a very strange behavior in that a query suddenly starts to hang (takes very long to complete) and I don't know why. I first thought this might be a SQL Alchemy issue (I'm using SQL Alchemy and pyodbc to talk to a SQL Server). It's super hard for me to reproduce because at some point it runs fine as usual (this might be the next day or even after a few hours).
Usually it is the pyodbc cursor that takes very long to return.
I discussed and investigated this here #5389
I thought that maybe someone here has an idea what could be going on. Some low level C stuff maybe?
Thanks for your help in advance!

Have you been able to reproduce this without SQL Alchemy? PyODBC mostly just calls ODBC APIs, I'm not aware of it doing anything that in and of itself would take a long time (other then call a lot of APIs). If you can catch this with ODBC trace on we can see if unusually large number of function calls is being made.
It may also be waiting on the server, if you can make this happen with Wireshark on you can see if it's waiting for the server or not

The fact that it is intermittent suggests packet loss. If SQL Alchemy uses the ODBC driver in MARS mode, packet loss-induced delays can be greatly compounded: https://github.com/microsoft/msphpsql/issues/1055

MARS will make delays caused by packet loss much worse. If you are not using it, and there is no need to, then don't.
Is there anything about the problematic query which is distinctive compared to the others? e.g. is is (textually) long, and/or returns many rows/columns?

On the face of it, @sebarti , this sounds like a straight SQL performance issue, rather than anything to do with SQLAlchemy or pyodbc.  If the database tables you're querying are large (millions of rows), this might be about SQL execution plans and their re-use (or not), which might explain the intermittent nature of the issue.  Here is one article that might help (although it does get into the weeds somewhat).  There are a number of other articles on the intertubes about SQL performance tuning, and it's not always about indexes.
Have you had a DBA look at the SQL generated by SQLAlchemy, and the execution plans generated by SQL Server?  When the SQL "hangs", what is SQL Server doing under the hood - lots of reads, lots of writes, or what?  If I were you, I would find a tame DBA to check out the SQL statements.

Hi everyone. Sorry for the very late followup but the issue is has no longer appeared for a while now. I think it really just was SQL issue. Thanks for the help and advice anyway. I think you can close the issue.


Create newhallstudent.txt

There is no MX server associated to newhallstudent.net. Wrong domain?

Apologies, it is newhallschool.co.uk
Thank youKapil Pau
Date: Tue, 28 Jul 2015 06:26:34 -0700
From<EMAIL_ADDRESS>To<EMAIL_ADDRESS>CC<EMAIL_ADDRESS>Subject: Re: [swot] Create newhallstudent.txt (#909)
There is no MX server associated to newhallstudent.net. Wrong domain?
—
Reply to this email directly or view it on GitHub.

I will create a new file in the .co.uk folder

Sorry, there does not appear to be a .co.uk folder and I cannot create one, what would you like me to do?

.co.uk folder. Please read the doc next time :wink:

Sorry, I was thinking of my previous school, got a bit confused
Thank youKapil Pau
Date: Tue, 28 Jul 2015 06:35:43 -0700
From<EMAIL_ADDRESS>To<EMAIL_ADDRESS>CC<EMAIL_ADDRESS>Subject: Re: [swot] Create newhallstudent.txt (#909)
.co.uk folder. Please read the doc next time
—
Reply to this email directly or view it on GitHub.


The Key Distribution Service (KDC) - is it about 'kdc' or 'kdssvc' Service?

Hello,
Referring to the note in the Documentation:

Deleting and recreating the root key may lead to issues where the old key continues to be used after deletion due to caching of the key. The Key Distribution Service (KDC) should be restarted on all domain controllers if the root key is recreated.

It is not clear, what is meant under the term "The Key Distribution Service (KDC)". It is about 'kdc' or 'kdssvc':
PS C:\Windows\system32> Get-Service kdc, kdssvc

Status   Name               DisplayName
------   ----               -----------
Running  kdc                Kerberos Key Distribution Center
Stopped  kdssvc             Microsoft Key Distribution Service

Please kindly clarify it and also mention - what Startup Type should have 'kdssvc' service, when starting to use gMSA accounts for the first time? Should it be changed from existing 'Manual (Triggered Start)' to 'Automatic'?
Additionally, please - if 1 key already exists and we create new one - should we restart 'kdssvc' service?
Thanks!
Regards,
Andrejs

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

ID: 5d689602-4103-4688-0ca4-dadd3069e3ea
Version Independent ID: 7402857f-bbf0-008e-ceaa-9fd879d95770
Content: Create the Key Distribution Services KDS Root Key
Content Source: WindowsServerDocs/security/group-managed-service-accounts/create-the-key-distribution-services-kds-root-key.md
Product: windows-server
Technology: security
GitHub Login: @JasonGerend
Microsoft Alias: jgerend

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


Not working with nested text

Hi,
Really cool plugin. Trying to create a design system with nested text so I can change button colour and it doesn't seem to work when the text is converted into a symbol

Sorry, the plugin doesn't support nested structures and unfortunately I don't have spare time to evolve the plugin further.  Have a look at the guidelines for what is supported: https://github.com/kenmoore/sketch-relabel-button/raw/master/Relabel Button Guidelines.sketch


Add eraser tool

Currently the only way to erase is to draw the same color as the background. It would be nice to be able to remove strokes

Hmm, this was closed as completed but I don't see it implemented? Is there something I'm missing?


Moving to rutorrent v4.0 in a develop tag?

Hi @crazy-max
Would it be possible to get a docker tag (nightly / dev) which use the latest versions of rutorrent?
https://github.com/Novik/ruTorrent/releases/tag/v4.0-beta.1
They have released interesting changes including some to make plugins like File Manager back on track.
https://github.com/nelu/rutorrent-filemanager/issues/33
Thank you for your help and answer!

I will not publish nightly releases but I will take a look to add support for v4.0 on another branch.

@crazy-max We are pleased to announce ruTorrent version 4.0 is now stable. We highly recommend using it over 3.10. There is significant enhancements. The web client is also more polished. https://github.com/Novik/ruTorrent/releases/tag/v4.0-stable

FWIW, I rebuilt the image with the latest commit from rutorrent (06222a00375bdd0f1f1b5b58bda29e7025316428) and geoip (f63f84c18f00c19622b83e96ae9dd8632e318183), and it "just works" -- stoked to see all these perf improvements!

Can be tested with:
crazymax/rtorrent-rutorrent:edge@sha256:d3f3e4d3dfdc6340e083047fdaf82ea53ad34df4e60c77106e7420bd7b176ad7


Create AzureApplicationCredential

This issue is to track the design and implementation of the AzureImplementationCredential for applications calling service APIs not suited for DefaultAzureCredential. Details can be found here

Related PR: https://github.com/Azure/azure-sdk-for-python/pull/19403


Guide: Sublime3 sbt build guide for openstrat

will have a go this week
maybe focus on lessons

sublime make this pretty easy now so closing


[typescript-operations] @skip, @include doesn't respect avoidOptionals config

Describe the bug

Related to #3836
When using @skip, @include with plugin typescript-operations it always uses MakeOptional.
When using avoidOptionals in the config, it should instead use MakeMaybe
To Reproduce
Steps to reproduce the behavior:

My GraphQL schema:

type Query {
    user(id: ID!): User!
}

type User {
    id: ID!
    username: String!
    email: String!
}

My GraphQL operations:

query user {
    user(id: 1) {
        id
        username
        email @skip(if: true)
    }
}

My codegen.yml config file:

schema: schema.graphql
documents: document.graphql
generates:
  types.ts:
    plugins:
      - typescript
      - typescript-operations
    config:
      avoidOptionals: true

Expected behavior

// Note this type is much simpler than the one currently used
type MakeOptional<T, K extends keyof T> = Omit<T, K> & { [SubKey in K]?: Maybe<T[SubKey]> };
type MakeMaybe<T, K extends keyof T> = Omit<T, K> & { [SubKey in K]: Maybe<T[SubKey]> };

export type UserQuery = (
  { __typename?: 'Query' }
  & { user: (
    { __typename?: 'User' }
    & MakeMaybe<Pick<User, 'id' | 'username' | 'email'>, 'email'>
  ) }
);

Now UserQuery['user']['email'] is Maybe, but not optional
Environment:

@graphql-codegen/typescript: no versions published with this new feature
@graphql-codegen/typescript-operations: 1.17.10

Thank you for reporting this @Cellule ! You are right, the avoidOptionals was missed in that implementation.
@gilgardosh is working on a fix in https://github.com/dotansimha/graphql-code-generator/pull/5104 :)

Fixed :)


Looks like Actions SDK is not closing the request with async methods gracefully!

https://stackoverflow.com/questions/53154510/google-actions-sdk-second-request-in-conversation-is-failing-with-typeerror-st
I am building a Google Action using Actions SDK V2 library.
I am able to make the conversation work when I am using plain conv.ask and conv.close methods. But the moment I add async methods in to the processing chain, I am facing issues. I am using
    "actions-on-google": "^2.4.1",
    "firebase-admin": "^6.0.0",
    "firebase-functions": "^2.1.0",

Exactly after every 3 failed attempts, the 4th attempt gets through. Looks like the previous request is hogging up my firebase cloud function!
First request to the fulfillment works just fine and the subsequent ones fail with "TypeError: standard is not a function at /srv/node_modules/actions-on-google/dist/framework/express.js"
  severity:  "ERROR"
    textPayload:  "TypeError: standard is not a function
       at /srv/node_modules/actions-on-google/dist/framework/express.js:27:13
       at omni (/srv/node_modules/actions-on-google/dist/assistant.js:44:53)
       at cloudFunction (/srv/node_modules/firebase-functions/lib/providers/https.js:57:9)
       at /worker/worker.js:700:7
       at /worker/worker.js:684:9
       at _combinedTickCallback (internal/process/next_tick.js:131:7)
       at process._tickDomainCallback (internal/process/next_tick.js:218:9)"

I understand that when I've asynchronous functions in the processing chain, I should return Promise to the Intent handler. And I am doing that. But still the subsequent request fails.
const app = actionssdk();
   // ... app code here

    app.middleware((conv) => {
      console.log('Conversation in Middleware:', conv);
      conv.hasScreen =
        conv.surface.capabilities.has('actions.capability.SCREEN_OUTPUT');
      conv.hasAudioPlayback =
        conv.surface.capabilities.has('actions.capability.AUDIO_OUTPUT');
    });

  // Welcome Intent
  app.intent('actions.intent.MAIN', (conv, input) => {
    // conv.ask('How are you');
    console.log('Conversation: ' + JSON.stringify(conv), conv);
    console.log('actions.intent.MAIN', input)
    return new Promise((resolve, reject) => {
      processIntents({conv: conv, input:input}).then(r => {
        console.log('Passing response from the handler!', r);
        for(let a of r) {
          conv.ask(a);
        }
        resolve();
      }).catch(e => reject(e));
    });
  });

  // React to a text intent
  app.intent('actions.intent.TEXT', (conv, input) => {
    console.log('actions.intent.TEXT', input)
    // conv.ask('How are you');
    console.log('Conversation: ' + JSON.stringify(conv), conv);
    console.log('actions.intent.TEXT', input)
    return new Promise((resolve, reject) => {
      processIntents({conv: conv, input:input}).then(r => {
        console.log('Passing response from the handler!', r);
        for(let a of r) {
          conv.ask(a);
        }
        resolve();
      }).catch(e => reject(e));
    });
  });

  // React to list or carousel selection
  app.intent('actions.intent.OPTION', (conv, params, option) => {
    // conv.ask('How are you');
    console.log('actions.intent.OPTION', {input: conv.input, option: option, params:params})
    console.log('Conversation: ' + JSON.stringify(conv), conv);
    console.log('actions.intent.OPTION', option)
    return new Promise((resolve, reject) => {
      processIntents({conv: conv, params: params, option: option}).then(r => {
        console.log('Passing response from the handler!', r);
        for(let a of r) {
          conv.ask(a);
        }
        resolve();
      }).catch(e => reject(e));
    });
  });
  app.intent('', (conv) => {
    // conv.ask('How are you');
    console.log('Empty Intent for direct WEB requests / ALEXA requests', conv);
    let input = ((conv.request.originalRequest ||{}).result ||{}).resolvedQuery;
    return new Promise((resolve, reject) => {
      processIntents({conv: conv, input: input}).then(r => {
        //TODO: send raw HTTP Response
        //TODO: Yet to figure out how this can be done@!
        resolve();
      }).catch(e => reject(e));
    });
  });

  const processIntents = (args) => {
      let conv = args["conv"];
      let params = args["params"];
      let option = args["option"];
      let input = args["input"];
      // Async Function here that responds with a Promise
      // Based on the request, it will send either array of responses to use in conv.ask calls
     // OR send response JSON body that can be sent to Amazon Alexa / WEB requests
    return Promise.resolve(response);
  }
  exports.apiaifns = functions.https.onRequest(app);

I am sending an array of conversation responses from the processIntents method and iterating through the array while responding.
I've tried many possible permutations and combinations of this, but still the subsequent request fails.
Update : Testing with Google Cloud Functions instead of GCF for Firebase
Updated my app code to make it an express app and deployed to GCFs with the same name. Now the situatio is worse. Only first request after deployment of the Cloud Function is successful and all subsequent requests fail with the same error as before!
Here is my update to the function:
```
const express = require('express')
const bodyParser = require('body-parser')
var morgan = require('morgan')
.
.
.
const expressApp = express().use(bodyParser.json())
expressApp.use(morgan('dev'))
expressApp.post('/fulfillment', app)

exports.apiaifns = functions.https.onRequest(expressApp);

I've also changed the actio invocation URL to "https://us-central1-my-project.cloudfunctions.net/apiaifns/fulfillment"

This is litarally driving me crazzy, and I couldn't find a reason for the issue! Kindly help.

Due to more than 5 months of inactivity, this issue is being closed.
If you think the resolution is in error, please re-open the request with fresh information.


After a forced generational rotate, ensure new writes go to the new file.

Keep track of the base filename for log files, so when a forced
generational rotate is performed, the existing log file becomes a
new version and subsequent writes go to the new file.

Thanks!


Errors during make minikube-install

Running make minikube-install mostly seems to work, but between loading the images into minikube and applying the yaml, spits out these errors:
/bin/bash: ./release-tools/generate-keys.sh: No such file or directory
/bin/bash: line 1: /tmp/tmp.w89e0ut2NV/ca.crt: No such file or directory
W0921 17:11:40.845263  162519 helpers.go:535] --dry-run is deprecated and can be replaced with --dry-run=client.
error: Cannot read file /tmp/tmp.w89e0ut2NV/webhook-server-tls.crt, open /tmp/tmp.w89e0ut2NV/webhook-server-tls.crt: no such file or directory
error: no objects passed to apply
/bin/bash: line 5: ./src/dataset-operator/deploy/webhook.yaml.template: No such file or directory
error: no objects passed to apply

It seems like the generate-keys.sh stuff happens in-cluster now, so maybe this is nothing to worry about? It's a bit disconcerting though :-)

Apologies @lukemarsden the documentation is all over the place currently! I have been updating the wiki ( https://github.com/IBM/dataset-lifecycle-framework/wiki/Installation ) but not the README.md (promise to fix it the next few days)
Instead if you use make deployment it should work without a problem, let me know if that's not the case.

Hi @lukemarsden, with the updated instructions and yamls this should be resolved right?


srpc2-refiner err

-08-07T10:43:05.151801Z  INFO indexer: Load config from /near...
2024-08-07T10:43:05.151974Z  WARN neard: /near/config.json: encountered unrecognised fields: network.external_address, network.reconnect_delay, consensus.reduce_wait_for_missing_block, consensus.state_fetch_horizon
2024-08-07T10:43:05.151985Z  INFO config: Validating Config, extracted from config.json...
2024-08-07T10:43:05.153906Z  WARN genesis: Skipped genesis validation
2024-08-07T10:43:05.153931Z  INFO config: Validating Genesis config and records. This could take a few minutes...
2024-08-07T10:43:05.154122Z  INFO config: All validations have passed!
2024-08-07T10:43:05.154276Z  INFO db_opener: Opening NodeStorage path="/near/data" cold_path="none"
2024-08-07T10:43:05.154289Z  INFO db: Opened a new RocksDB instance. num_instances=1
2024-08-07T10:43:05.180126Z  INFO db: Closed a RocksDB instance. num_instances=0
2024-08-07T10:43:05.180137Z  INFO db_opener: The database exists. path=/near/data
2024-08-07T10:43:05.180142Z  INFO db: Opened a new RocksDB instance. num_instances=1
2024-08-07T10:43:05.405891Z  INFO db: Closed a RocksDB instance. num_instances=0
2024-08-07T10:43:05.405919Z  INFO db: Opened a new RocksDB instance. num_instances=1
2024-08-07T10:43:05.429022Z  INFO db: Closed a RocksDB instance. num_instances=0
2024-08-07T10:43:05.429035Z  INFO db: Opened a new RocksDB instance. num_instances=1
2024-08-07T10:43:05.627934Z  INFO runtime: Error when getting the gc stop height. This error may naturally occur after the gc_num_epochs_to_keep config is increased. It should disappear as soon as the node builds up all epochs it wants. Error: DB Not Found Error: epoch block: CcwdTNoD3roE54wwZJ4GyJ7rBhzubHhAf4L8oUyLqvpN
2024-08-07T10:43:05.629219Z  INFO memtrie: Loading tries to memory for shards []...
2024-08-07T10:43:05.654150Z  INFO memtrie: Memtries loading complete for shards []
2024-08-07T10:43:05.654163Z  INFO chain: Init: header head @ #125131253 6KPYo1zCS6ob5yyhWJFjg2wDPqs3ZSGUkbtKaKc7efsH; block head @ #125076785 CcwdTNoD3roE54wwZJ4GyJ7rBhzubHhAf4L8oUyLqvpN
thread 'main' panicked at /usr/local/cargo/git/checkouts/nearcore-5bf7818cf2261fd0/1e199de/chain/client/src/client_actor.rs:168:6:
called Result::unwrap() on an Err value: Chain(DBNotFoundErr("epoch block: CcwdTNoD3roE54wwZJ4GyJ7rBhzubHhAf4L8oUyLqvpN"))
stack backtrace:
0: rust_begin_unwind
1: core::panicking::panic_fmt
2: core::result::unwrap_failed
3: near_client::client_actor::start_client
4: nearcore::start_with_config_and_synchronization
5: nearcore::start_with_config
6: near_indexer::Indexer::new
7: aurora_refiner::input::nearcore::get_nearcore_stream
8: <tokio::task::local::RunUntil as core::future::future::Future>::poll
9: aurora_refiner::main

how to resolve it


Mostly working ALL enum support

For pages there's still some bugs left to squash.
Also design input required: Now that we don't anymore have numerical indexes, workflows like Close Page  1  ALL  ALL wouldn't make sense anymore since all indices are unique to the specific pages. Flows like Close Page  ALL  ALL  CURRENT could still be supported but closing all pages in all contexts without closing the contexts seems a bit nonsensical.

I guess the most common use case is to close all pages and the currently active context. Like I have two context open, because I want to test the webapp with two different logins/pages. But then I want to close all pages and the context from the first user, but leave second context and pages open because I want to continue testing with that user. Also I do not want close the browser. Something like this:
 | Close Page | ALL | CURRENT | None |

If I understood your description correctly, wouldn't it make more sense to just Close Context  CURRENT in that case?

Hmmm, yes, you right, using | Close Context | CURRENT | is better.

Some notes from daily:
This does not make sense now: Switch Page   someid   ALL.

Close Page  uuid, does not switch context nor browser unless uuid = CURRENT.
Switch Page  uuid, switch page, context and browser.
${page_id}=   New Page
${popup_id}=   Switch page   NEW
${popup_id}=   Get Current Page Id
Get Browser Catalog   then   value[dsksdjsa]


Missing tag for 1.0.1 release

Hi, could you please push tag for 1.0.1 release that is available on pypi?

+1

Done, thanks for the advice.

much appreciated 😃


Break the CIP action tests into a sh script.

Signed-off-by: Ville Aikas<EMAIL_ADDRESS>
Summary
Break the actual tests for CIP into a separate shell scripts to make it possible to run
e2e tests from a local machine.
Ticket Link

Fixes
Release Note

Codecov Report

Merging #1767 (e71631b) into main (1bd6871) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1767   +/-   ##
=======================================
  Coverage   31.26%   31.26%
=======================================
  Files         144      144
  Lines        8830     8830
=======================================
  Hits         2761     2761
  Misses       5741     5741
  Partials      328      328

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 1bd6871...e71631b. Read the comment docs.


[Feature]: Support Installation/Initialization of single packages

Description
This Feature should allow the installation of single packages in addition to installing always all packages referenced in .velocitas.json
Suggested Solution
velocitas init --package [packageName]
--> check in velocitas.json for version -> init only single package with configured version
--> not in velocitas.json -> check velocitas "standard" packages for latest version -> add to velocitas.json und download & init package
some additions (examples which should work):
--> if package is not in .velocitas.json add it respectively
velocitas init --package devenv-runtimes@versionSpecifier
velocitas init --package https://github.com/anyRepository.git
velocitas init --package https://github.com/eclipse-velocitas/devenv-devcontainer-setup.git@versionSpecifier

Added with #254


lemon-graph: init at 1.3.1

Motivation for this change
Add the LEMON graph library: "a C++ template library providing efficient implementations of common data structures and algorithms with focus on combinatorial optimization tasks connected mainly with graphs and networks".
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase 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.

/marvin opt-in
/status needs_reviewer

Result of nixpkgs-review pr 131736 at e394959f run on aarch64-linux 1

1 package failed to build:

lemon-graph

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.


don't do mass storage usb work inside timer interrupt task

Also add support for disabling the stdio part of stdio_msc_usb with STDIO_MSC_USB_DISABLE_STDIO.
Using SPI for the sd-card now works.

On Windows everything works OK. On OSX and MacOS the Volume gets mounted after u command and I can access the card. After ejecting the drive the Volume gets unmounted, but the GEEK still is waiting for eject, seems it not getting the information from the OS that the Volume was unmounted.
So far not tried it with my Pi 4, going to test that too, curious what will happen there.

Or maybe not, can't plug the GEEK into one of the USB sockets, to close together and doesn't fit with the other stuff plugged in.


YAML generation return incorrect tags definition

When I generate the specs without specifying any tags the output yaml format get inconsistent.
In particular, in many case is correct:
      tags:
      - Supercon

with Supercon as the name of the application
However, for certain cases (see the whole method):
@bp.route('/record/<id>/flag', methods=['PUT', 'PATCH'])
@output(Flag)
def flag_record(id):
    object_id = validateObjectId(id)
    connection = connect_mongo(config=config)
    db_name = config['mongo']['db']
    db = connection[db_name]
    tabular_collection = db.get_collection("tabular")
    record = tabular_collection.find_one({"_id": object_id})
    if record is None:
        return 404
    else:
        new_status = 'invalid'
        new_type = 'manual'

        changes = {'status': new_status, 'type': new_type}

        tabular_collection.update_one({'_id': record['_id']}, {'$set': changes})
        return changes, 200

the array is invalidated:
  /supercon/record/{id}/flag:
    patch:
      parameters:
      - &id001
        in: path
        name: id
        required: true
        schema:
          type: string
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Flag'
          description: Successful response
        '404':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPError'
          description: Not found
      summary: Flag Record
      tags: &id002
      - Supercon
    put:
      parameters:
      - *id001
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Flag'
          description: Successful response
        '404':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPError'
          description: Not found
      summary: Flag Record
      tags: *id002

if I define the app.tags("supercon") the problem disappears..
Environment:

Python version: 3.8.12
Flask version: 2.0.2
APIFlask version: 0.11.0

Hi, what do you mean by "the array is invalidated"? I don't see any tag defined in your view function (with doc decorator).

@greyli if I'm not wrong, the array
      tags: &id002
      - Supercon

is not well formed, as it should be
      tags:
      - Supercon

am I correct?

The &id002 and *id002 is anchor and alias in YAML, just like id and # in HTML. They are valid YAML symbols.

OK. I guess it's not a problem of this library then. 😅


Charge market fee only

Make _sendMessage not depend on msg.value

use endpoint(message handle) instead


DOC: add PeriodIndex.asfreq docstring

Part of https://github.com/pydata/pandas/issues/6384
I guess PeriodIndex don't show up in the API docs at all. Not sure if I'll get to any more.

@jorisvandenbossche thanks. Should be good now I think

@TomAugspurger added some more .. :-)

@TomAugspurger can you update?

@jreback done. Merge when you're ready.

@TomAugspurger I think you forgot to add your changes

Seems to be good now.

I realize after we merge index-repr prob need to fix s bunch of doc strings :(

e.g. will be.
In [1]: pidx = pd.period_range('2010-01-01', '2015-01-01', freq='A')

In [2]: pidx
Out[2]: PeriodIndex(['2010', '2011', '2012', '2013', '2014', '2015'], dtype='int64', freq='A-DEC')

In [3]: pidx.asfreq('M')
Out[3]: PeriodIndex(['2010-12', '2011-12', '2012-12', '2013-12', '2014-12', '2015-12'], dtype='int64', freq='M')

In [4]: pidx.asfreq('M', how='S')
Out[4]: PeriodIndex(['2010-01', '2011-01', '2012-01', '2013-01', '2014-01', '2015-01'], dtype='int64', freq='M')

Indeed. A search for <class 'pandas.tseries.period.PeriodIndex'> and alike can help there maybe. I will open an issue for that.


Error on Microsoft.AspNetCore.Authorization.* attributes on Hot Chocolate resolvers / types

Fixes #7688

Would be cool if this could be back-ported to v14. The ErrorOnAspNetCoreAuthorizationAttributes schema option simply has to be set to false then, so it's not a breaking change.


Add bar chart dashboard item

Yes!  Nice!

https://github.com/jasonroman/flot-barnumbers-enhanced looks good for enhancing discrete_bar_chart


Implement dev/release build commands

I'd like to perform various optimizations and other changes to make dev builds faster, release builds smaller, and other tweaks .
For Leptos, our build tool cargo-leptos allows us to define these things depending on whether we're building for dev or prod in concert with Cargo. I'd like to be able to give spin different invocations of cargo leptos depending on situation.
Ideally, this would match cargo, so spin build builds the dev version, spin build --release builds the release version, and a --profile= version would all allow users to add different commands in spin.toml

Looks like there was some discussion internally on this that didn't make it onto the issue.  Some stuff that came up:

What do we do about different output locations for dev and release builds?
Is this effectively going to turn into some npm run <script> kind of thing?  How do we feel about that?
How much complexity are we okay with investing into spin build?  Accreting a feature here and a feature there is going to be more effort for less delight than going "welp looks like we're building a build system, let's do some design."

For me, part of the challenge is that spin build and spin up/spin deploy are decoupled.  If I do a dev build followed by spin up, presumably I want to run the dev build... but that means we need to either dev and release build to the same place, or we need to remember the last build command, neither of which feel lovely.  Conversely we don't want spin deploy or spin registry push to roll out a dev build just because that's the last one the user happened to build.

Definitely some concerns there, I think it would have to remember the last build. I guess it's up to you whether you want people to be able to push the dev profile, although if I choose a different release profile that checking might get interesting. Perhaps a setting for the desired release-profile as well as different commands?
You could build a full on npm run kinda thing, but at least for this purpose I'm happy to delegate it to Cargo with a few Spin additions.
This is very much a Rust specific thing though, I imagine there's a more general way to do it, perhaps I could build a plugin that does this


Add GitHub Actions workflow files

This PR adds GitHub Actions workflow file. This doesn't change programs but is useful for improving productivity.
This allows us to do some checks automatically when:

new commits are pushed to master branch
someone created a new PR against master branch

Currently it checks:

proton.json

Job name: proton_json

Generate Proton AppId list from proton.json
Check whether proton.json is valid

truckersmp-cli

Job name: download_files

Check whether download_files() function works properly
HTTP redirection handling is also tested

Job name: flake8

Check main script by flake8 with flake8-docstrings and flake8-import-order

truckersmp-cli.c

Job name: build

Compile C source by mingw-w64
Create binary .tar.xz files (GitHub Actions "Artifact" file)

These jobs run in parallel.

First of all, thank you so much for your time and feedback.

Besides the things mentioned in the comments this should be as resource saving as possible by doing the necessary tasks because the free plan has only limited amount of use time which could potentially bill the repository owner.

According to official document (About billing for GitHub Actions), GitHub Actions usage is free for public repositories. Since this repo is public, we don't need to worry about billing.

GitHub Actions usage is free for public repositories

Great, I've somehow missed the part about private free repositories in the documentation and only have seen the free included minutes.

I haven't looked in the new changes yet but I think you're mixing some things up or I'm just thinking too far further ahead.
Keep this PR and the actions for verification and debugging only.
I think you want to do an automatic upload for the end users and yes, we're doing that totally. But not here. We need another action for releases which listens for the release tag and bundles everything up nicely. But I think the script needs some preparation for releases and (distro-)packaging, I'm going to put an issue up for that later.

Only updating my first comment (It's outdated).
Commits have been combined into one (Sorry for force-pushing twice, I changed "workflow file" to "workflow files").
If you want to merge now, you can. If you think it's better to keep this PR open for a while, you can.
Thank you for reviewing.


Do not require an editor restart when toggling xr/openxr/enabled

The editor itself never starts in XR mode and the setting still successfully applies to projects when hitting play (F5) without needing an editor restart.

Are the openxr shaders being loaded in editor affected by this setting though?

Nevermind I see the xr action map editor will not open without a restart of the editor


High Datastore Query Latency

I am reporting an issue I am seeing when using the java-datastore library within an Apache Beam transform (running on GCP Dataflow). The beam job was running slow so i decided to profile it using the GCP Profiler. I was able to identify that most of the wall time was spent waiting on calls to Datastore (within a beam transform) using the Java Datastore library. I wrote a test job that just makes simple datastore reads within a beam transform and saw the same results. Here is a screenshot of the profiler:

You can see in the screenshot that on average it is taking around 19s to run these simple Datastore queries. I understand it is best practice to use the beam datastore library in order to parallelize/batch these calls to Datastore but for our use case we need these sequential synchronous reads (that the Java Datastore library provides) within the beam transform. Anyways I was wondering if anyone had any insight into why these calls might be taking as long as they do? You can see in the screenshot that most of the wall time is spent waiting on the SocketInputStream.socketRead0() method which indicates possible network or remote server latency.
Here is a screenshot of the test job DoFn code i wrote that i ran the above profile on:

Just an update. I ended up putting log statements (with timestamps) before and after the query. As it turns out the query was, for the most part, taking around 50ms with some outliers around 200ms. This completely contradicts what we saw in the profiler. Or maybe our interpretation of the profile. So it is either the profiler is wrong or our interpretation of the profile is wrong. Still looking into this.


SQLite.delete() not delete one to many related items

DBFlow Version:4.0.0-beta5
Issue Kind (Bug, Question, Feature):
Question
Description:
I have this parent table written like this:
@Table(database = AppDatabase.class, allFields = true)
public class StepResult extends AppModel {
    @PrimaryKey public String stepId;
    @ColumnIgnore public List<DataItemResultTable> items;

    @OneToMany(methods = OneToMany.Method.ALL, variableName = "items")
    public ArrayList<DataItemResultTable> getFormItems() {
        if (items == null) {
            items = SQLite.select()
                    .from(DataItemResultTable.class)
                    .where(DataItemResultTable_Table.stepInfoNewForeignKeyContainer_stepId.eq(stepId))
                    .queryList();
        }
        return (ArrayList<DataItemResultTable>) items;
    }
}

and child table
@Table(database = AppDatabase.class, allFields = true)
public class DataItemResultTable extends AppModel {
    @ForeignKey(stubbedRelationship = true)
    public StepInfoNewTable stepInfoNewForeignKeyContainer;
    @PrimaryKey public String dataItemId;
    public String stepDataItemValue;
    public long insertTime;
}

when I execute
        SQLite.delete(StepResult.class)
                .where(StepResult_Table.orderId.eq(workOrderId))
                .async()
                .execute();

stepResult can be deleted but DataItemResultTable related with StepResult has not been deleted. I have set OneToMany option to OneToMany.Method.ALL but seems does not work.

OneToMany is a local to model only relation and is not a real sql relation. Thus you must delete each individual model from your list to properly delete the relations. You cannot use the wrapper language for this feature.


Updated the Kahuna Kit to support Kahuna Android SDK 2.3.1

@rayleeriver @sharekris please review.

Looks good otherwise.

LGTM


[Enhancement] Set cookie path & http_only to make it more safe

Why I'm doing:
Using the HttpOnly flag when generating a cookie helps mitigate the risk of client side script accessing the protected cookie.
What I'm doing:
Set cookie path & http_only to make it more safe
Fixes #51241
What type of PR is this:

[ ] BugFix
[ ] Feature
[X] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[X] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[ ] This is a backport pr

Bugfix cherry-pick branch check:

[X] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.3
[ ] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

@mergifyio backport branch-3.3


RP2040 Raspberry Pico W  SPI not working

I'm facing some issue with the Raspberry Pico W spi (both). Compiling for example the  raspberrypi-pico-w:st7735  project  using  raspberry SDK v1.4.0 and attaching an oscilloscope to the spi1 pins I can't  see any transaction executing the fb application. Same example but for the pico let me see the spi transaction.  Maybe test some version just after st7735 support was added to confirm it was working.

Same test done with  commit 74f1bfbfd7d578ba74f1885548a8be0901df0c34 confirm the problem. Be careful is not an issue related to the specific application, I'm facing same problem with my personal projects, spi working fine on raspberry pico and fails on raspberry pico-w

After some more investigation I found that compiling nuttx with raspberry pico sdk 1.5.0 fix the issue BUT the wifi doesn't work with the newer sdk because the firmware blob files are changed between sdk 1.4 and 1.5.

Hi @paolovolpi thank you for this investigation! We need to find some way to do hardware debug.
Some CI test on real hardware is definitely required!
Few days ago I tested ESP32-Devkit  with GT911 touchscreen and discovered that I2C is not sending all the data correctly. It sends the I2C Address, two bytes of GT911 internal register (ie. 0x8040) but doesn't send the value to that register. Same gt9xx.c driver tested on STM32F4Discovered board worked fine.

Hi after a lot of more investigation I was able to fix the issue using the  raspberry pico sdk 1.5.0. Still not working with the 1.4.0 but with the 1.5.0 the spi is working as expected (we had some hardware issue with our dev board). I had to replace the sdk 1.5.0 wifi driver (/lib/cyw43-driver) with the 1.4.2 one, because the file structures is changed and is not compatible with the nuttx sources.

@paolovolpi it worked here! I clone 1.4.0 updated the firmware submodule lib/, then cp -a lib /tmp, clone 1.5.0 removed lib and cp -a /tmp/lib .

The problem with the spi was related to my custom pcb. The issue related to the SDK still remain. If you want to use sdk 1.5 you need to replace the sdk direcotry lib/cyw43-driver with the one from version 1.4


Introduced Consumer interface

Simple functional interface which (surprisingly) lacks in Google Base.

Forgot to insert license text.


[Question] Monday as a first day of a week

Is there a way to set Monday as a first day of a week instead of Sunday? For example in react-datepicker there is a property calendarStartDay.

No there isn't any way to change the fist day of week. maybe in future.


[<IP_ADDRESS>] Possible cross-mod issue with storage drawers

I had an odd issue with the Mekanism logistical system and the new storage controller of Storage Drawers.
Full story of the incident:
thephoenixlodge/Regrowth-Stuff#18
I was later able to reproduce it in SSP, although not reliably (includes stacktrace):
jaquadro/StorageDrawers#52

No way this can me on my end - there's some form of faulty ISidedInventory implementation going on by the Storage Drawers.  I simply iterate over the list of slots given by getAccessibleSlotsFromSide(), the crash is basically saying that the list returned contains missing element(s).

Mekanism makes an assumption that all slot numbers are less than the length of the slot array.  While I have not encountered an issue with other transport systems I've tested, I feel like I'm the only mod challenging that assumption, and so I've changed the behavior on my end.


error with The connection to the server localhost:8080 was refused - did you specify the right host or port when installing minnaker

gabriel@gebi:~/gitspace/learn-spinnaker/local/minnaker-0.1.3$ ./scripts/install.sh
[INFO ] Using Armory Spinnaker
[INFO ] Running minnaker setup for Linux
[INFO ] Cloning repo: https://github.com/armory/spinnaker-kustomize-patches#minnaker into /home/gabriel/gitspace/learn-spinnaker/local/minnaker-0.1.3/spinsvc
[WARN ] /home/gabriel/gitspace/learn-spinnaker/local/minnaker-0.1.3/spinsvc exists already.  FOLDER CONTENTS WILL GET OVERWRITTEN!
[WARN ] PROCEEDING in 3 secs... (ctrl-C to cancel; use -B option to specify a different directory)
Cloning into '/home/gabriel/gitspace/learn-spinnaker/local/minnaker-0.1.3/spinsvc'...
remote: Enumerating objects: 1381, done.
remote: Counting objects: 100% (221/221), done.
remote: Compressing objects: 100% (169/169), done.
remote: Total 1381 (delta 106), reused 110 (delta 49), pack-reused 1160
Receiving objects: 100% (1381/1381), 422.31 KiB | 3.04 MiB/s, done.
Resolving deltas: 100% (787/787), done.
[INFO ] Installing yq
[INFO ] Installing jq
[INFO ] Trying to detect endpoint
[INFO ] No cloud metadata endpoint detected, detecting interface IP (and storing in /home/gabriel/gitspace/learn-spinnaker/local/minnaker-0.1.3/spinsvc/secrets/public_ip): <masked my public IP>
[INFO ] Generating password [/home/gabriel/gitspace/learn-spinnaker/local/minnaker-0.1.3/spinsvc/secrets/spinnaker_password]:
<masked my password>
[INFO ] Updating spinsvc templates with new endpoint: <IP_ADDRESS>
[INFO ] Creating spin_endpoint helper function
#!/bin/bash
#echo "$(kubectl get spinsvc spinnaker -n spinnaker -ojsonpath='{.spec.spinnakerConfig.config.security.uiSecurity.overrideBaseUrl}')"
echo "$(yq e '.spec.spinnakerConfig.config.security.uiSecurity.overrideBaseUrl' BASE_DIR/expose/patch-urls.yml)"
[[ -f BASE_DIR/secrets/spinnaker_password ]] && echo "username: 'admin'"
[[ -f BASE_DIR/secrets/spinnaker_password ]] && echo "password: '$(cat BASE_DIR/secrets/spinnaker_password)'"
[INFO ] --- Installing K3s ---
[INFO]  Using v1.19.7+k3s1 as release
[INFO]  Downloading hash https://github.com/k3s-io/k3s/releases/download/v1.19.7+k3s1/sha256sum-amd64.txt
[INFO]  Downloading binary https://github.com/k3s-io/k3s/releases/download/v1.19.7+k3s1/k3s
[INFO]  Verifying binary download
[INFO]  Installing k3s to /usr/local/bin/k3s
[INFO]  Skipping /usr/local/bin/kubectl symlink to k3s, already exists
[INFO]  Creating /usr/local/bin/crictl symlink to k3s
[INFO]  Skipping /usr/local/bin/ctr symlink to k3s, command exists in PATH at /usr/bin/ctr
[INFO]  Creating killall script /usr/local/bin/k3s-killall.sh
[INFO]  Creating uninstall script /usr/local/bin/k3s-uninstall.sh
[INFO]  env: Creating environment file /etc/systemd/system/k3s.service.env
[INFO]  systemd: Creating service file /etc/systemd/system/k3s.service
[INFO]  systemd: Enabling k3s unit
Created symlink /etc/systemd/system/multi-user.target.wants/k3s.service → /etc/systemd/system/k3s.service.
[INFO]  systemd: Starting k3s
[INFO ]  --- END K3s ---
[INFO ] Setting Kubernetes context to Spinnaker namespace
Context "default" modified.
[INFO ] Spinnaker Operator Version: 1.2.7
[INFO ] Spinnaker flavor: armory
The connection to the server localhost:8080 was refused - did you specify the right host or port?
[ERROR] Unable to list namespaces of the kubernetes cluster:
[KUBE ] kubectl apply -f https://engineering.armory.io/manifests/pacrd-1.0.1.yaml -n spinnaker
[ERROR] Error executing command:
unable to recognize "https://engineering.armory.io/manifests/pacrd-1.0.1.yaml": Get http://localhost:8080/api?timeout=32s: dial tcp <IP_ADDRESS>:8080: connect: connection refused
unable to recognize "https://engineering.armory.io/manifests/pacrd-1.0.1.yaml": Get http://localhost:8080/api?timeout=32s: dial tcp <IP_ADDRESS>:8080: connect: connection refused
unable to recognize "https://engineering.armory.io/manifests/pacrd-1.0.1.yaml": Get http://localhost:8080/api?timeout=32s: dial tcp <IP_ADDRESS>:8080: connect: connection refused
unable to recognize "https://engineering.armory.io/manifests/pacrd-1.0.1.yaml": Get http://localhost:8080/api?timeout=32s: dial tcp <IP_ADDRESS>:8080: connect: connection refused
unable to recognize "https://engineering.armory.io/manifests/pacrd-1.0.1.yaml": Get http://localhost:8080/api?timeout=32s: dial tcp <IP_ADDRESS>:8080: connect: connection refused
unable to recognize "https://engineering.armory.io/manifests/pacrd-1.0.1.yaml": Get http://localhost:8080/api?timeout=32s: dial tcp <IP_ADDRESS>:8080: connect: connection refused
unable to recognize "https://engineering.armory.io/manifests/pacrd-1.0.1.yaml": Get http://localhost:8080/api?timeout=32s: dial tcp <IP_ADDRESS>:8080: connect: connection refused
unable to recognize "https://engineering.armory.io/manifests/pacrd-1.0.1.yaml": Get http://localhost:8080/api?timeout=32s: dial tcp <IP_ADDRESS>:8080: connect: connection refused
unable to recognize "https://engineering.armory.io/manifests/pacrd-1.0.1.yaml": Get http://localhost:8080/api?timeout=32s: dial tcp <IP_ADDRESS>:8080: connect: connection refused
unable to recognize "https://engineering.armory.io/manifests/pacrd-1.0.1.yaml": Get http://localhost:8080/api?timeout=32s: dial tcp <IP_ADDRESS>:8080: connect: connection refused
unable to recognize "https://engineering.armory.io/manifests/pacrd-1.0.1.yaml": Get http://localhost:8080/api?timeout=32s: dial tcp <IP_ADDRESS>:8080: connect: connection refused

I fixed it myself.
I should have exportted  KUBECONFIG=/etc/rancher/k3s/k3s.yaml first because
export KUBECONFIG=/etc/rancher/k3s/k3s.yaml


[Bug] Failed to deserialize column statistics

Search before asking

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

Version
1.2.1
What's Wrong?
When successfully upgrade from 1.1.5 to 1.2.1 and run a sql query , warning occured as bellow:
`2023-01-04 08:59:48,133 WARN (ForkJoinPool.commonPool-worker-7|10741) [StatisticsCacheLoader.lambda$asyncLoad$0():76] Failed to deserialize column statistics
java.lang.NullPointerException: null
at org.apache.doris.statistics.util.StatisticsUtil.deserializeToColumnStatistics(StatisticsUtil.java:105) ~[doris-fe.jar:1.0-SNAPSHOT]
at org.apache.doris.statistics.StatisticsCacheLoader.lambda$asyncLoad$0(StatisticsCacheLoader.java:74) ~[doris-fe.jar:1.0-SNAPSHOT]
at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1590) ~[?:1.8.0_181]
at java.util.concurrent.CompletableFuture$AsyncSupply.exec(CompletableFuture.java:1582) ~[?:1.8.0_181]
at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289) ~[?:1.8.0_181]
at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056) ~[?:1.8.0_181]
at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692) ~[?:1.8.0_181]
at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157) ~[?:1.8.0_181]
`
It seem like the StatisticsCacheLoader failed, the query result is ok but  more slow than before.
What You Expected?
no warning
How to Reproduce?
Every time run a nomal sql query, the warning occured.
Anything Else?
No response
Are you willing to submit PR?

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

Code of Conduct

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

I can't reproduced it, Do you sure you are using 1.2.1 instead os 1.2.0?

selectdb-doris-1.2.0-1-caeed14 ， show backends telling this @Kikyou1997

seem like https://github.com/apache/doris/issues/16672 ?


function call return address

I've got main_1, main_2, an invocation, the main_1 cfg, and the main_2 cfg. This comes back SAT with this countermodel and it looks like the return address being pushed onto the stack right before the function call (tid %00000026 in main_1 and %0000009b in main_2) is the culprit. I believe this is because CBAT chooses a value for RBX that is on the stack and includes part of this return address. mem[rbx] is then read into a temporary variable. And then that temporary variable is then moved into RAX, which is our refuted goal. I did confirm that the tid has a spec (_start has spec_arg_terms), and thus stack pointer is incremented. However, if one removes the offset label and instruction in main_2 that cause the pushed return address to be different, the programs are unsat. Does this make sense?
This feels like something that can be corrected by adding in an assertion afterwards that the stack memory below RSP after a function is called is equal between programs. However, maybe this is this too strong of an assumption?

I'm pasting in the gist metadata. main_1's code :
.global _start

.text

safe_hasher:

push %rbx
#callq *0x30(%rbx)
callq _start
add (%rbx),%rax
pop %rbx
retq

main:
    ret

_start:
    call    main

main_2's code:
.global _start

.text

this_creates_an_offset:
push %rbx

safe_hasher:

push %rbx
#callq *0x30(%rbx)
callq _start
add (%rbx),%rax
pop %rbx
retq

main:
    ret

_start:
    call    main

main_1's cfg:
digraph {
node[shape=box];

subgraph "cluster__start" {
  label="_start"

  "\%0000001c"[label="\%0000001c
0000002f: RSP := RSP - 8\l00000032: mem := mem with [RSP, el]:u64 <- 0x4000E5\l00000035: call @main with noreturn\l"]
}
"\%0000001c" -> "\%0000002b";

subgraph "cluster___libc_start_main" {
  label="__libc_start_main"

  "\%0000002b"[label="\%0000002b
0000003d: #2 := mem[RSP, el]:u64\l00000040: RSP := RSP + 8\l00000044: call #2 with noreturn\l"]
}

subgraph "cluster_safe_hasher" {
  label="safe_hasher"

  "\%00000008"[label="\%00000008
0000000f: #1 := RBX\l00000013: RSP := RSP - 8\l00000016: mem := mem with [RSP, el]:u64 <- #1\l00000020: RSP := RSP - 8\l00000023: mem := mem with [RSP, el]:u64 <- 0x4000DA\l00000026: call @_start with return %00000046\l"]
  "\%00000046"[label="\%00000046
00000053: #3 := RAX\l00000056: #4 := mem[RBX, el]:u64\l00000059: RAX := RAX + #4\l0000005c: CF := RAX < #3\l0000005f: OF := high:1[#3] = high:1[#4] & (high:1[#3] | high:1[RAX]) & ~(\lhigh:1[#3] & high:1[RAX])\l00000062: AF := 0x10 = (0x10 & (RAX ^ #3 ^ #4))\l00000065: PF := ~low:1[let $1 = RAX >> 4 ^ RAX in let $2 = $1 >> 2 ^ $1 in\l$2 >> 1 ^ $2]\l00000068: SF := high:1[RAX]\l0000006b: ZF := 0 = RAX\l00000073: RBX := mem[RSP, el]:u64\l00000076: RSP := RSP + 8\l0000007f: #6 := mem[RSP, el]:u64\l00000082: RSP := RSP + 8\l00000086: call #6 with noreturn\l"]
  "\%00000008" -> "\%00000046"
}
"\%00000008" -> "\%0000001c";
}

main_2's cfg:
digraph {
node[shape=box];

subgraph "cluster__start" {
  label="_start"

  "\%0000002b"[label="\%0000002b
0000003e: RSP := RSP - 8\l00000041: mem := mem with [RSP, el]:u64 <- 0x4000E6\l00000044: call @main with noreturn\l"]
}
"\%0000002b" -> "\%0000003a";

subgraph "cluster___libc_start_main" {
  label="__libc_start_main"

  "\%0000003a"[label="\%0000003a
0000004c: #3 := mem[RSP, el]:u64\l0000004f: RSP := RSP + 8\l00000053: call #3 with noreturn\l"]
}

subgraph "cluster_safe_hasher" {
  label="safe_hasher"

  "\%00000018"[label="\%00000018
0000001f: #2 := RBX\l00000022: RSP := RSP - 8\l00000025: mem := mem with [RSP, el]:u64 <- #2\l0000002f: RSP := RSP - 8\l00000032: mem := mem with [RSP, el]:u64 <- 0x4000DB\l00000035: call @_start with return %00000055\l"]
  "\%00000055"[label="\%00000055
00000062: #4 := RAX\l00000065: #5 := mem[RBX, el]:u64\l00000068: RAX := RAX + #5\l0000006b: CF := RAX < #4\l0000006e: OF := high:1[#4] = high:1[#5] & (high:1[#4] | high:1[RAX]) & ~(\lhigh:1[#4] & high:1[RAX])\l00000071: AF := 0x10 = (0x10 & (RAX ^ #4 ^ #5))\l00000074: PF := ~low:1[let $1 = RAX >> 4 ^ RAX in let $2 = $1 >> 2 ^ $1 in\l$2 >> 1 ^ $2]\l00000077: SF := high:1[RAX]\l0000007a: ZF := 0 = RAX\l00000082: RBX := mem[RSP, el]:u64\l00000085: RSP := RSP + 8\l0000008e: #7 := mem[RSP, el]:u64\l00000091: RSP := RSP + 8\l00000095: call #7 with noreturn\l"]
  "\%00000018" -> "\%00000055"
}
"\%00000018" -> "\%0000002b";

subgraph "cluster_this_creates_an_offset" {
  label="this_creates_an_offset"

  "\%00000008"[label="\%00000008
0000000f: #1 := RBX\l00000013: RSP := RSP - 8\l00000016: mem := mem with [RSP, el]:u64 <- #1\l0000009b: call @safe_hasher with noreturn\l"]
}
"\%00000008" -> "\%00000018";
}

Note that the only difference between main_1 and main_2 is the offset symbol and instruction in the second binary such that the return address pushed on in the bir differs between binaries.
The bap invocation:
gcc  -nostdlib main_1.S -o main_1
gcc  -nostdlib main_2.S -o main_2
bap --pass=save-project --no-byteweight --save-project-filename=main_1.bpj main_1
bap --pass=save-project --no-byteweight --save-project-filename=main_2.bpj main_2

BAP_DEBUG=1 bap /bin/echo --pass=wp --wp-compare=true --wp-file1=main_1.bpj --wp-file2=main_2.bpj --wp-function=safe_hasher --wp-inline=false --wp-num-unroll=0 --no-byteweight --wp-use-fun-input-regs=false --wp-mem-offset=false --wp-compare-post-reg-values=R12,R13,R14,R15,RBX,RSP,RBP,RAX --wp-show=bir,refuted-goals,paths

And finally, the resulting model:
Model:
	ZF  |->  0x0
	SF  |->  0x0
	RSP |->  0x0000000040000000
	RBX |->  0x000000003fffffed
	RAX |->  0x0000000000000000
	PF  |->  0x0
	OF  |->  0x0
	CF  |->  0x0
	AF  |->  0x0
	mem_orig |-> [
		else |-> 0x00]
	mem_mod |-> [
		#x000000003fffffed |-> 0x00 ;
		#x000000003fffffee |-> 0x00 ;
		#x000000003fffffef |-> 0x00 ;
		#x000000003ffffff0 |-> 0x00 ;
		#x000000003ffffff1 |-> 0x00 ;
		#x000000003ffffff2 |-> 0x00 ;
		#x000000003ffffff3 |-> 0x00 ;
		#x000000003ffffff4 |-> 0x00 ;
		#x000000003ffffff8 |-> 0x00 ;
		#x000000003ffffff9 |-> 0x00 ;
		#x000000003ffffffa |-> 0x00 ;
		#x000000003ffffffb |-> 0x00 ;
		#x000000003ffffffc |-> 0x00 ;
		#x000000003ffffffd |-> 0x00 ;
		#x000000003ffffffe |-> 0x00 ;
		#x000000003fffffff |-> 0x00 ;
		#x0000000040000000 |-> 0x00 ;
		#x0000000040000001 |-> 0x00 ;
		#x0000000040000002 |-> 0x00 ;
		#x0000000040000003 |-> 0x00 ;
		#x0000000040000004 |-> 0x00 ;
		#x0000000040000005 |-> 0x00 ;
		#x0000000040000006 |-> 0x00 ;
		#x0000000040000007 |-> 0x00 ;
		else |-> 0xda]

Refuted goals:
RAX0 = RAX09:
	Concrete values: = #x00004000da000000 #x00004000db000000
	Z3 Expression: = #x00004000da000000 #x00004000db000000
	Path:

Initial state:
| address (8 bytes) | value |        |
|        0x40000000 |       | <- RSP |
|        0x3ffffff8 |       |        |
|        0x3ffffff0 |       |        |
|        0x3fffffe8 |       |        |

Then (see cfg), RSP is decremented:
RSP := RSP - 8

| address (8 bytes) | value |         |
|        0x40000000 |       |         |
|        0x3ffffff8 |       | <- RSP  |
|        0x3ffffff0 |       |         |
|        0x3fffffe8 |       |         |

Then, RBX is pushed onto the stack and decremented:
mem := mem with [RSP] <- \#1
RSP := RSP - 8

| address (8 bytes) | value    |        |
|        0x40000000 |          |        |
|        0x3ffffff8 | init_RBX |        |
|        0x3ffffff0 |          | <- RSP |
|        0x3fffffe8 |          |        |

Then the return address is pushed onto the stack:
mem := mem with [RSP] <- 0x4000DA/0x4000DB (DIFFERENT BETWEEN PROGRAMS)

| address (8 bytes) | value             |        |
|        0x40000000 |                   |        |
|        0x3ffffff8 | init_RBX          |        |
|        0x3ffffff0 | 0x4000DA/0x4000DB | <- RSP |
|        0x3fffffe8 |                   |        |

Then, the function is called:
call @_start with return %00000046

| address (8 bytes) | value             |        |
|        0x40000000 |                   |        |
|        0x3ffffff8 | init_RBX          | <- RSP |
|        0x3ffffff0 | 0x4000DA/0x4000DB |        |
|        0x3fffffe8 |                   |        |

Then:
\#4 = mem[RBX]

From the countermodel, RBX is 0x3fffffed, so we read in some of the bytes from
0x3ffffff0 (which is differing between binaries as that is the address of the
pushed return address)
RAX := RAX + \#4

RAX is not touched for the rest of the program and thus ends up in the
countermodel.
A more detailed model of that last step:
| address (8 bytes) |             value |        |
|        0x40000000 |                   |        |
|        0x3ffffff8 |          init_RBX | <- RSP |
|        0x3ffffff7 | 0x4000DA/0x4000DB |        |
|        0x3ffffff6 |                00 |        |
|        0x3ffffff5 |                00 |        |
|        0x3ffffff4 |                00 | <----+ |
|        0x3ffffff3 |                00 |      | |
|        0x3ffffff2 |                40 |      | |
|        0x3ffffff1 |                00 |      R |
|        0x3ffffff0 |             DA/DA |      B |
|        0x3fffffef |                   |      X |
|        0x3fffffee |                   |      | |
|        0x3fffffed |                   | <----+ |
|        0x3fffffec |                   |        |
|        0x3fffffeb |                   |        |
|        0x3fffffea |                   |        |
|        0x3fffffe9 |                   |        |
|        0x3fffffe8 |                   |        |
|                   |                   |        |

I took a quick look at this, and it does look like having different values in RAX is the correct behavior if the initial value of RBX is pointing to uninitialized places on the stack. Saying that the memory on the stack below RSP is equal makes me a bit uncomfortable because anything can go there since it is as uninitialized region of memory.
That said, I'm not sure what the best approach for this would be. I feel like this is a case where it would be a good idea to check the possible inputs for RBX similarly to how we wanted to check if inputs are pointers, but I am unsure.

I haven't understood the behavior of the program yet, but based on Chloe's description, I agree with her assessment.  Assuming memory below RSP is equal seems maybe scary (though also possibly not the worst thing in the world if allows us to make quick progress).  Better would be to say RBX points into a region we do know is equal (or are already assuming to be equal).
In general this is the kind of requirement we'd expect to have on a function (something like, "It behaves correctly IF the pointer it is passed points to an initialized, 'live' region of memory").  I certainly expect this is the kind of thing we will want to add as we develop more complex function summaries, and we'll want to check both that the function obeys this spec and that when the function is called its argument satisfies these requirements.

I think Chris's ideas are really good! For this specific example, we can have a precondition that RBX is pointing to a live region of memory. I guess the question would be how to express this property.

Following our conversation yesterday, I revisited some examples. Here's a couple symbols in the grammatech examples where I think the differing pushed return address allows CBAT to choose some inputs pointing to places on the stack that result in SAT:

mb_copy: This example is subtle. Differing RBP registers is the refuted goal. This is because the stack gets smashed using the return address. Here's a brief summary of what happens:

00001990: RBX := RSI
...
00001a15: mem := mem with [RSP, el]:u64 <- 0x41B7C (DIFFERING BTWN BINARIES)
00001a18: call %00128c6a with return %00001a1a
...
00001a34: RAX := pad:64[pad:32[mem[RBX + 0x10]]]
...
00001a61: mem := mem with [RBP + 0x10] <- low:8[RAX]
...
00001e78: RBP := mem[RSP, el]:u64

Note that this example is also run with mem_offset set to false. Here's the BIR and the returned model. Essentially RSI points onto the stack, and then gets read into RBX. This is then used  to access the return address of a function. This is then written back into memory where RBP was saved, resulting in RBP having part of the return address as its value. This is evidenced in the refuted goal:
Z3 Expression: = #x0000041b7c100002 #x0000041cec100002

is_dumpdir. This is pretty representative of the bug, I think. Here's the BIR
brief summary:

000ccd85: RBX := RDI
000ccd91: mem := mem with [RSP, el]:u64 <- 0x1D749 (DIFFERING BTWN BINARIES)
000ccd94: call %00128763 with return %000ccd96
...
000ccd9b: RAX := pad:64[pad:32[mem[RBX + 0x188]]]

Basically, the input RDI points onto the stack (see the countermodel) and more specifically, is the address on the stack that a return address is pushed. This return address (that differs between programs) is then read into RAX. (Note that this countermodel was generated without mem_offset as well)


[stable/cerebro] run with security context and be able to run  as non…

…Root
Signed-off-by: David J. M. Karlsen<EMAIL_ADDRESS>What this PR does / why we need it:
This version will allow pod to run in strict environments which require nonRoot execution. With the removal of the init container the volume still looks correct and cerebro is able to create its database.
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[X] DCO signed
[X] Chart Version bumped
[X] Variables are documented in the README.md
[X] Title of the PR starts with chart name (e.g. [stable/chart])

/assign @cpanato

/lgtm


Develop action items to harmonize ABCD & HBCD documentation

with @laikevin128
from Damien: Sections, Titles, Warnings, expectations, responsible data use, etc are a few things that came up in the meeting. Because the data is going to be on the same platform with the same functionality it is probably important we are doing our best to keep things as similar as possible to avoid any confusion for users across these issues.

Next steps: once available, Luci will add yellow warnings and red alerts for HBCD to relevant data measure sections - alerts should be directly linkable so links can be added to data dictionary


always retry when the server returns InternalError

What changes were proposed in this pull request?
always retry when the server returns InternalError
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.姜正 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

close stale PR


Updates to luma 8.0 alpha 9

Biggest update was adding some architecture so extensions can add their module injections to a ProgramManager local to a given LayerManager as the global shader hook logic has been deprecated.
Smaller changes:

Update BitmapLayer and IconLayer to explicitly set flip y unpacking behaviour as the flip y default is deprecated.
getParameter -> getParameters as getParameter has been deprecated.

Coverage increased (+0.01%) to 83.884% when pulling 4d586da49bf56948d5c9524a0640ac13eb6a753e on luma-updates into ba339f378efc3a2f42ed300307910b72293e2208 on master.


Have individual edit UI for product items

Don't just show the latest unrecognized barcode, but have possibility for there to be many.
And also show ok product items (not just unrecognized ones).


Preview: storage & boot API for Image manager

Low-level modules modules for DFU support:

module for interact with mcuboot.
module for storage the image.

related PRs

DT flash write alignment property: https://github.com/zephyrproject-rtos/zephyr/pull/860

Signed-off-by: Andrzej Puzdrowski<EMAIL_ADDRESS>

@d3zd3z, @agross-linaro I've opened separate PR for addition of flash alignment description. https://github.com/zephyrproject-rtos/zephyr/pull/860

@nashif I apply requested changes.
Regards exercising the code

sample code: I want to wait for DFU protocol support contribution for building sample DFU application. We will contribute DFU protocol support as one of next step.

tests: I can add test for verification whether added APIs modifies flash memory according to expectations. Will you be happy with such  tests?

@nashif @mbolivar @d3zd3z @rsalveti I added tests for new modules. Tests verifies flash content which is writing by modules.

@nashif @cvinayak could you re-review this at your convenience?


Getting a bunch of errors in Dashboard.tsx imports

Hello, I am trying to test out this example project (the full example in src/, not trying to rewrite it myself), but after cloning this project and running the yarn command from the readme, npm is running into compilation errors, and VS Code is showing me the following errors in the import statements:

'"@rarible/protocol-ethereum-sdk"' has no exported member named 'isErc1155v1Collection'. Did you mean 'isLazyErc1155Collection'?
Cannot find module '@rarible/ethereum-api-client' or its corresponding type declarations
It looks to me like @rarible/ethereum-api-client may have been renamed to @rarible/protocol-api-client, though I don't have a lot of experience with any of this. I tried changing it in the import statement, but it seems @rarible/protocol-api-client does not have exactly the same exported members, i.e. '"@rarible/protocol-api-client/build/models/NftCollection"' has no exported member named 'NftCollectionType'. Did you mean 'NftCollection_Type'?
Am I doing something wrong? I still need to really learn how to use React, but I was hoping by using the full example and following the steps in the readme that I could just press go and see it in action, so to speak.

@webthethird We updated README. You should initialize and start the project by following commands
yarn && yarn start without installing additional dependencies

don't work for me

yarn start
yarn run v1.22.17
error Command "start" not found.

You should invoke "yarn start" from project folder


Game exported to iOS trough test flight or the app store doesn't have localization files

Godot version
Godot Engine v3.4.2 stable
System information
Linux, Fedora 34, OpenGL ES 3.0 Renderer: Mesa Intel(R) UHD Graphics 620 (KBL GT2)
Issue description
My exported app localization works as expected on android published on the play store. However on iOS for some reason the app installed trough test flight or the app store isn't localized while the app build from Xcode and running it on a physical device is localized.
Steps to reproduce
Localize your project and export to xcode then to test flight or the appstore. The locale used is not the one from the system.
Minimal reproduction project
No response

CC @godotengine/ios

In fact, this looks like this only happen when I add localization trough the xcode iterface to localize permissions access using the plist.

What are you using for localization?
If you are using Xcode localization files, you might have setup localization incorrectly.
To localize .plist files, you should use InfoPlist.strings file that are already added to the project. In it you should set localization for each plist string, like this NSCameraUsageDescription = "Camera Permission String";

Thanks I was going it the wrong way. It turns out that you must check languages boxes on the InfoPlist.strings and not on the file right above.

I'm encountering the same problem with Godot 4.2. I have set up some localizations that work in the editor and work when I install it on my local device using XCode, but they are ignored when installing via TestFlight. I don't quite understand the statement "you must check language boxes." The InfoPlist files seem to be for iOS system things like NSCameraUsageDescription, whereas I'm trying to localize text in my game elements. Is there something I need to do in XCode beyond setting up localization files in the editor?


Remove scrollbars

@Nikhil-Ladha here's an item (the scrollbars) that you might take a look at:

Originally posted by @leecalcote in https://github.com/layer5io/meshery.io/pull/237#issuecomment-651340896

Yes, @leecalcote I saw this. But the thing is that this scrollbar is coming only in the browser for netlify preview and it wont come up when it's actually deployed. I tried it out for small screens in my mobile and pc and there a more friendly transparent scrollbar comes up which doesn't has any effect.
But if still, this needs to be removed I can do this by changing the code to pre-formatted style.

@Nikhil-Ladha, oh, interesting. Yes, I only looked at the netlify preview. Thank you for double-checking on this.

I checked on meshery.io and I do not see this behavior on the site. Closing issue.

Cool 👍🏼🙂


SECRET_KEY - autogeneration broken

From reading the source, intended behaviour is, if SECRET_KEY is not in netbox_config parameter, it will be generated. But
      - include_role:
          name: "netbox"
        vars:
          netbox_stable: true
          netbox_database_host: localhost
          netbox_database_user: "netbox"
          netbox_database_password: "netbox"
          netbox_superuser_password: "netbox"
          netbox_socket: "<IP_ADDRESS>:9000"
          netbox_load_initial_data: false
          netbox_application_log: "file:{{ netbox_shared_path }}/application.log"
          netbox_requests_log: "file:{{ netbox_shared_path }}/requests.log"
          netbox_scripts: []
          netbox_config:
             ALLOWED_HOSTS:
               - <IP_ADDRESS>
             MEDIA_ROOT: "{{ netbox_shared_path }}/media"
             REPORTS_ROOT: "{{ netbox_shared_path }}/reports"
             SCRIPTS_ROOT: "{{ netbox_shared_path }}/scripts"
          #   SECRET_KEY: "" # auto-generated

Is ailing with:
    qemu: TASK [_netbox : Run database migrations for NetBox] ****************************
    qemu: fatal: [localhost]: FAILED! => {"changed": false, "cmd": "./manage.py migrate --noinput", "msg": "\n:stderr: Traceback (most recent call last):\n  File \"./manage.py\", line 10, in <module>\n    execute_from_command_line(sys.argv)\n  File \"/srv/netbox/current/venv-py3/lib/python3.7/site-packages/django/core/management/__init__.py\", line 381, in execute_from_command_line\n    utility.execute()\n  File \"/srv/netbox/current/venv-py3/lib/python3.7/site-packages/django/core/management/__init__.py\", line 375, in execute\n    self.fetch_command(subcommand).run_from_argv(self.argv)\n  File \"/srv/netbox/current/venv-py3/lib/python3.7/site-packages/django/core/management/base.py\", line 323, in run_from_argv\n    self.execute(*args, **cmd_options)\n  File \"/srv/netbox/current/venv-py3/lib/python3.7/site-packages/django/core/management/base.py\", line 361, in execute\n    self.check()\n  File \"/srv/netbox/current/venv-py3/lib/python3.7/site-packages/django/core/management/base.py\", line 390, in check\n    include_deployment_checks=include_deployment_checks,\n  File \"/srv/netbox/current/venv-py3/lib/python3.7/site-packages/django/core/management/commands/migrate.py\", line 64, in _run_checks\n    issues = run_checks(tags=[Tags.database])\n  File \"/srv/netbox/current/venv-py3/lib/python3.7/site-packages/django/core/checks/registry.py\", line 72, in run_checks\n    new_errors = check(app_configs=app_configs)\n  File \"/srv/netbox/current/venv-py3/lib/python3.7/site-packages/django/core/checks/database.py\", line 9, in check_database_backends\n    for conn in connections.all():\n  File \"/srv/netbox/current/venv-py3/lib/python3.7/site-packages/django/db/utils.py\", line 216, in all\n    return [self[alias] for alias in self]\n  File \"/srv/netbox/current/venv-py3/lib/python3.7/site-packages/django/db/utils.py\", line 213, in __iter__\n    return iter(self.databases)\n  File \"/srv/netbox/current/venv-py3/lib/python3.7/site-packages/django/utils/functional.py\", line 80, in __get__\n    res = instance.__dict__[self.name] = self.func(instance)\n  File \"/srv/netbox/current/venv-py3/lib/python3.7/site-packages/django/db/utils.py\", line 147, in databases\n    self._databases = settings.DATABASES\n  File \"/srv/netbox/current/venv-py3/lib/python3.7/site-packages/django/conf/__init__.py\", line 79, in __getattr__\n    self._setup(name)\n  File \"/srv/netbox/current/venv-py3/lib/python3.7/site-packages/django/conf/__init__.py\", line 66, in _setup\n    self._wrapped = Settings(settings_module)\n  File \"/srv/netbox/current/venv-py3/lib/python3.7/site-packages/django/conf/__init__.py\", line 157, in __init__\n    mod = importlib.import_module(self.SETTINGS_MODULE)\n  File \"/usr/lib/python3.7/importlib/__init__.py\", line 127, in import_module\n    return _bootstrap._gcd_import(name[level:], package, level)\n  File \"<frozen importlib._bootstrap>\", line 1006, in _gcd_import\n  File \"<frozen importlib._bootstrap>\", line 983, in _find_and_load\n  File \"<frozen importlib._bootstrap>\", line 967, in _find_and_load_unlocked\n  File \"<frozen importlib._bootstrap>\", line 677, in _load_unlocked\n  File \"<frozen importlib._bootstrap_external>\", line 728, in exec_module\n  File \"<frozen importlib._bootstrap>\", line 219, in _call_with_frames_removed\n  File \"/srv/netbox/releases/netbox-2.6.7/netbox/netbox/settings.py\", line 46, in <module>\n    \"Required parameter {} is missing from configuration.py.\".format(parameter)\ndjango.core.exceptions.ImproperlyConfigured: Required parameter SECRET_KEY is missing from configuration.py.\n", "path": "/srv/netbox/current/venv-py3/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin", "state": "absent", "syspath": ["/tmp/ansible_django_manage_payload_79_dlb_l/ansible_django_manage_payload.zip", "/usr/lib/python37.zip", "/usr/lib/python3.7", "/usr/lib/python3.7/lib-dynload", "/usr/local/lib/python3.7/dist-packages", "/usr/lib/python3/dist-packages"]}

Fancied the feature, but have no time to cure myself. Should be light one though.

I did some debugging and the secret key is properly generated and slurped, but netbox_config is not updated with it. Is set_fact not supposed to work if you're using include_role? I'm not sure how one should fix this. The role works fine if you use the roles attribute in a playbook definition (hence why this hasn't been caught by any of the tests).

Looks like there's an upstream Ansible issue opened about this, and it seems to be a stale/forgotten issue: https://github.com/ansible/ansible/issues/32713
After some testing it looks like the netbox_config variable on the include_role task takes precedence over facts. If I remove it from the include_role task/move it to the playbook vars, the role completes fine. It also works fine if I use an import_role task and keep the netbox_config var on the task like you have. I think this might be intended behaviour for Ansible (set_fact documentation also states: "Per the standard Ansible variable precedence rules, many other types of variables have a higher priority, so this value may be overridden."), so I'm closing this as wontfix.

Looks like there's an upstream Ansible issue opened about this, and it
seems to be a stale/forgotten issue: ansible/ansible#32713
https://github.com/ansible/ansible/issues/32713
After some testing it looks like the |netbox_config| variable on the
|include_role| task takes precedence over facts. If I remove it from
the |include_role| task/move it to the playbook vars, the role
completes fine. It also works fine if I use an |import_role| task and
keep the |netbox_config| var on the task like you have. I think this
might be intended behaviour for Ansible (|set_fact| documentation also
states: "Per the standard Ansible variable precedence rules, many
other types of variables have a higher priority, so this value may be
overridden."), so I'm closing this as wontfix.

Thanks so much Musee for swift reaction. Intriguing and non-intuitive
behavior by ansible if you asked me.
--
BR
Matthias Tafelmeier

As more people are starting to use the include_role pattern they will step into this, I just did :1st_place_medal:
Would you be open to an implementation that did the same for netbox_config as you do in tasks/load_variables.yaml for other values? If we keep _netbox_config private the combine can work without overwriting with set_fact ...
What do you think @lae ?

I had a go at fixing this so that the way of using the role that @cherusk posted here also works. Not many changes are needed, so I think I'll open a PR soon and discuss this there.


Stop using corepack

close #228

Enforce the use of pnpm.
Remove the reference to corepack from the package manager.
Update the version of pnpm.

I think the settings on the Vercel side need to be corrected.
@saicaca

It seems Vercel doesn't allow the use of use-node-version for some reason.
https://github.com/orgs/vercel/discussions/2436
Would the engines and pnpm.executionEnv.nodeVersion serve the same purpose?

It seems Vercel doesn't allow the use of use-node-version for some reason. https://github.com/orgs/vercel/discussions/2436
Would the engines and pnpm.executionEnv.nodeVersion serve the same purpose?

I think it's possible.
Change this from the original.

🤔

I tried deploying it with a Vercel account, but it passed normally...
I wonder what it is...

 ERR_PNPM_INVALID_NODE_VERSION  "~22" is not a valid Node.js version

Maybe an exact version is needed🤔

Apparently there is no way to specify the node version in Vercel. (Also, it seems that it is not possible to make only Vercel be ignored.)


question about this fork

does this fork have some of speed optimizations from reverse engineered clone of Zelda 3 with LakeSnes
since official repo has been archived and there link in readme to your fork

Hi,
Sorry for the -very- late response, for some reason the issues here didn't tag me :(
No, their fork basically neutered the ppu, making it unusable with any game but Zelda 3
best regards,

dink


Add IDs to navigation list items

Addresses #1337 @sploiselle @kuanluo
IDs can be changed in sidebar_doc.yml

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/ecef4155bbfe5aa29282a63dddb5ac9f8cbc8efc/

Reviewed 2 of 2 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Thanks @deronjohnson !

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/2d0fa29c31be0a788fcbfa71fab8d7afd6827f00/

Thanks, @deronjohnson ! It turns out we found ways to circumvent the need for this feature. I'm going to save the work as a PoC in case we need to reimplement it in the future, but because we don't currently need it, going to close this without merging.


[Python] Windows 10 Access Violation exit(5) application crashes when mysql-connector-python==9.1.0 is used and pyarrow installed

Describe the bug, including details regarding any error messages, version, and platform.
As I have seen some issues ( like #40100 ) related to Access Violation on Windows in pyarrow I have decided to open this issue here. Maybe for other not reproducible issues with the same crash reason it is related to conflicts with other dependencies.
We have a Python (3.12.5) Flask application which uses Flask==3.1.0 and Flask-SQLAlchemy==3.1.1.
As a connection driver, we had mysql-connector-python==9.1.0.
On Windows 10, when pyarrow is installed (I have tested all versions from pyarrow 15, and Python 3.12 and 3.13, PyPi) application crashes when SQLAlchemy tries to open connection to MySQL (in our case just localhost with standard 3306 port).
Here is faulthandler traces:

We have changed mysql-connector-python to mysqlclient and issue disappear.
Component(s)
Python

#44855 may be related.


ERROR INSTALLING with npm install -g node-sass

npm ERR! Windows_NT 5.1.2600
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Documents and Settings
\Bob\Application Data\npm\node_modules\npm\bin\npm-cli.js" "install" "-g"
"ionic"
npm ERR! node v4.4.2
npm ERR! npm  v3.8.5
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>postinstall: node scripts/build.js
npm ERR! Exit status<PHONE_NUMBER>
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script 'node scripts/build.js
'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the node-sass package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node scripts/build.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs node-sass
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls node-sass
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     C:\Documents and Settings\Bob\npm-debug.log
npm ERR! code 1

This is #1283 please upgrade to node-sass v3.5.0-beta.1 to have this fixed.


✨ 💡 Add and configure PHP 5.6, 7.0, and 7.1

Do you guys have an article that explains how to use different PHP versions per site?
I'm trying
Sites:
    - map: test.dev
       to: /path/to/public
       php: "5.6"

but it's still showing as PHP 7.1 when i run phpinfo()

@mortscode
The docs have been updated: https://laravel.com/docs/5.4/homestead#multiple-php-versions

Do I need to checkout Homestead 6.x in my ~/Homestead directory?
Your docs still say:
// Clone the desired release...
git checkout v5.4.0

yes, it's impossible to keep the docs updated >.< Always checkout the latest tagged release: https://github.com/laravel/homestead/releases

Awesome.
Thanks @svpernova09. I'll give it a go.

I'm not too worried about it because i'm using 7.0 or 7.1 pretty exclusively now, but i'm getting an error in my homestead provision for 5.6:
Job for php5.6-fpm.service failed because the control process exited with error code. See "systemctl status php5.6-fpm.service" and "journalctl -xe" for details.

Any thoughts?

Hrm, their may be a bug in the version, someone in slack was having a similar issue. can you fill out a new issue: https://github.com/laravel/homestead/issues/new and I'll see if I can recreate

It looks like php 5.6 is missing mcrypt.
@mortscode Can you try removing your variables? I removed mine and that error went away for me.

@dmyers nice catch, fixed via https://github.com/laravel/settler/pull/115

what @svpernova09 said.


Getting a a grpc.FutureTimeoutError while using Reformulator from the checkpoint

Thank you for your interesting paper & open-sourcing it!
Running the code given in: https://github.com/google/active-qa/issues/9#issuecomment-432807557 but getting a grpc.FutureTimeoutError:
python2 reformulate.py
Num encoder layer 2 is different from num decoder layer 4, so set pass_hidden_state to False
# hparams:
  src=source
  tgt=target
  train_prefix=None
  dev_prefix=None
  test_prefix=None
  train_annotations=None
  dev_annotations=None
  test_annotations=None
  out_dir=/tmp/active-qa/reformulator
# Vocab file data/spm2/spm.unigram.16k.vocab.nocount.notab.source exists
  using source vocab for target
# Use the same embedding for source and target
Traceback (most recent call last):
  File "reformulate.py", line 10, in <module>
    environment_server_address='localhost:10000')
  File "/root/active-qa/px/nmt/reformulator.py", line 130, in __init__
    use_placeholders=True)
  File "/root/active-qa/px/nmt/model_helper.py", line 171, in create_train_model
    trie=trie)
  File "/root/active-qa/px/nmt/gnmt_model.py", line 56, in __init__
    trie=trie)
  File "/root/active-qa/px/nmt/attention_model.py", line 65, in __init__
    trie=trie)
  File "/root/active-qa/px/nmt/model.py", line 137, in __init__
    hparams.environment_server, mode=hparams.environment_mode))
  File "/root/active-qa/px/nmt/environment_client.py", line 152, in make_environment_reward_fn
    grpc.channel_ready_future(channel).result(timeout=30)
  File "/root/active-qa/venv/local/lib/python2.7/site-packages/grpc/_utilities.py", line 134, in result
    self._block(timeout)
  File "/root/active-qa/venv/local/lib/python2.7/site-packages/grpc/_utilities.py", line 84, in _block
    raise grpc.FutureTimeoutError()
grpc.FutureTimeoutError

Does the gRPC server have to run in order to use the Reformulator or am I missing something else here?

Are you running the environment server before running the reformulator code?

That fixed it. Thanks, @graviraja!


Documentation Eueler's Totient

Do the checklist before filing the issue:

[x] Do you have Node.js and all the relevant dev-dependencies installed?
[ ] Is this a bug fix?
[x] Is this an enhancement?
[ ] Is this a feature request?

NOTE: Provide a clear and concise description of the feature that needs to be added! Or if its a bug, then provide the necessary steps to reproduce it along with screenshots.

Provide a brief description of  M.phi(), you can refer the implementation for the same here.
Also, follow the documentation format followed for other functions such as here.
Make sure to cover the edge cases, as well as the error cases. Add relevant links as well, pertaining to implementation and use of eueler's totient function.
The important thing here is to make user aware of what does this function do, and what is its time complexity.
Here is the issue related to this-
#118

May I work on this!

@Manvityagi you're assigned


fix: update the changelog in preparation for 24.09

What does this PR do ?
Add a one line overview of what this PR aims to accomplish.
Changelog

Please update the CHANGELOG.md under next version with high level changes in this PR.

Usage

You can potentially add a usage example below

# Add a code snippet demonstrating how to use this

Before your PR is "Ready for review"
Pre checks:

[ ] Make sure you read and followed Contributor guidelines
[ ] Did you write any new necessary tests?
[ ] Did you add or update any necessary documentation? Make sure to also update the NeMo Framework User Guide which contains the tutorials

Checklist when contributing a new algorithm

[ ] Does the trainer resume and restore model state all states?
[ ] Does the trainer support all parallelism techniques(PP, TP, DP)?
[ ] Does the trainer support max_steps=-1 and validation?
[ ] Does the trainer only call APIs defined in alignable_interface.py?
[ ] Does the trainer have proper logging?

Additional Information

Related to # (issue)

the rebasing + 3way merge looked to mess up the change log, i'll fix


Wrap redundant reduce and reduceRight code in helper

The loops could be further abstracted, but I didn't like how it looked after going that far
Fixes #1734

Nice. One tiny style thing -- comments should be full sentences. Periods and all.

Nice. One tiny style thing -- comments should be full sentences. Periods and all.

Yes, agreed, comments should be fully comprehensible sentences.


[FLINK-7155] [metrics] Add Influxdb reporter

Hi @patricklucas ,
Coding guidelines “No WIP pull requests.”
Maybe you should see: http://flink.apache.org/contribute-code.html
BTW, If you do not have free time to finish it, I am willing to take over. :smile:
Best,
Hai Zhou


Dynamic frontend features based on module federation and the new frontend system

Hey, I just made a Pull Request!
This PR contributes support for the dynamic frontend features, which completes the already-existing support for backend dynamic features provided by package backend-dynamic-feature-service.
Dynamic frontend features are based on both the module federation support and the new frontend system.
In more details:

On the backend it exposes the module federation assets of any frontend dynamic plugin found in the dynamic plugins root folder, as well as a list of all frontend dynamic plugins module federation manifests
On the frontend side, it provides a CreateAppFeatureLoader which loads the exposed module federation remote modules through the module federation runtime library.

:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Hi! Feel free to rebase this while waiting for us to get back up to speed.


Add issues relations

It would be nice to be able to link issues with each other like:

#234 is blocked by #204
#234 resolves #125
etc.
Several links can be grouped like this:

Resolves
  #125 Some issue title
  #126 Another issue title
  ...
Blocked by
  #204 Issue 204 title

Corresponding issue should list corresponding links in it's own page like this:
Resolved by
  #234 Some major issue title
  ...
Blocks
  #235 Blocked issue title
  ...

So the used can see the lists of issue references and easily jump between them.

Hi, what makes this issue different from https://github.com/gogits/gogs/issues/1014?

#1014 seems to just be a request to show when issues are referenced in other issues (in the comments), like as in the following image:

This is a severely needed feature.
However, this current issue seems to be a request for a feature to add specific relations, like marking one issue blocked by another issue or marking one issue as resolving another issue.

@SystemDisc thanks! Your explanation helped.

I'm glad to be of service.

+1


Missing test.sh referenced in Jenkinsfile

There is a stage Test in Jenkinsfile which should execute test.sh.
But it seems that the file is missing from the repository.

I've just removed the dockerfile and jenkinsfile as they're no longer needed


Remove setPrincipalFactory and setOrder methods on AbstractAuthenticationHandler

Part of #2184

Can't see the build log. Can anyone?