Feat: New Services

New Services

Private Bin
Redlib

I believed I followed all the contribution rules. Let me know if I missed anything. Thank you.

Please add logos to your services.
Also add healtchecks to both services.
Also test them by inserting the compose into the compose deplyo type, because the first one I tried did not really work.

Sweet I love redlib!

Please add logos to your services.

Also add healtchecks to both services.

Also test them by inserting the compose into the compose deplyo type, because the first one I tried did not really work.

Sure thing man, I had them running on my service actually but I'll follow through with those.

Please add logos to your services.

Also add healtchecks to both services.

Also test them by inserting the compose into the compose deplyo type, because the first one I tried did not really work.

Also redlib on start takes a good couple of minutes to actually start working.

I've observed that Redlib is pretty unreliable. It will need some more testing.

It's weird because redlib not running behine coolify works flawlessly. But when it's behind coolify it often times out. If I ssh into the container and curl the service it always responds basically instantly. It makes me think there's something weird about the reverse proxy config. There's a small chance it could be related to the face that redlib doesn't support head requests but idk.

I will mark it as draft, when you are done pleas make it ready for review.

It's weird because redlib not running behine coolify works flawlessly. But when it's behind coolify it often times out. If I ssh into the container and curl the service it always responds basically instantly. It makes me think there's something weird about the reverse proxy config. There's a small chance it could be related to the face that redlib doesn't support head requests but idk.

I don't think so. It just takes a bit to startup. I think it might have to do with something relating to indexing reddit? But apart from that I got it to work without a problem mostly. I will do some more testing in general with the variables to ensure a stable production experience since its pretty unreliable right now.

I ended up changing the default sub reddit to worldnews due to for whatever reason the example option redlib gives for it doesn't actually work.

Alright, Redlib seems to be pretty stable. And I've implemented the proper coolify environment variables. I think it is ready, I also have been running redlib for about 3 hours and it has no problems accessing various sub reddits and the homepage is working well now that it is set to world news.

Thanks for the PR, next time please make separate PRs for each service. Also, I will not add Gothub because it is too small a service to officially maintain.


Error when associating a PR to my release plan

Error when associating a PR into my Release Planner App.

I tried with the same PR, and got it associated successfully.
@maririos Could you try again to see if you can reproduce it?

I get a different error now:

This happens in PPE

@maririos
When user re-associate API Spec PR with SDK Release milestone in progress, we need to reset the status for SDK Release milestone, which is stored in dataverse table SDK Release Request.
And the Delete permission was missing as the error showed, I have added it in PPE and Prod.
Please try again to see if it works.

That fixed it! No more errors. Thank you!


Remove & Fix Broken Links

Removed:
Mod Install
AWS S3 Baseline
AWS CIS Remediation
Fixed:
Azure Subscription ReadOnly mode

@omerosaienni Can you confirm if the Azure RO baseline is ideally what that link should point to? The section is "azure RO import" but the page is "azure RO create then import" so I don't want to cause any issues.


[CP] dart2wasm async and sync* fixes to stable

Commit(s) to merge
6de879e0f55, 7e237a12aa9, eabb2b3acaa, e44bc22ca3a, 350954ae9d2, 8ccb41284ae, e7dde8377ed, 3863e78e80d, 829261e2ba3, fab56db71b3
Target
stable
Prepared changelist for beta/stable
https://dart-review.googlesource.com/c/sdk/+/368300
Issue Description
Users are currently missing a lot of async and sync* bug fixes, and unable to use exception handling (try/catch) or switch statements (when the statement has a yield in the body).
What is the fix
Cherry pick the fixes and implementations.
Why cherry-pick
Users are missing bug fixes and some of the sync* features are simply unimplemented in the latest release.
Risk
Medium. While these changes include a lot of refactoring, no new features were added and a lot of bugs were fixed.
Issue link(s)
#55347, #55457, #51343, #51342 and probably more. (some of the fix commits didn't link to issues)
Extra Info
No response

LGTM
Since CI is green on this CP, I have no worries about it being risky. It CL looks big but

it's mostly moving code from one place to another (i.e. includes a refactoring)
fixes a number of issues (i.e. makes our stable branch more stable - which is it's purpose)
it makes the code on stable branch closer to main, so any future CPs, will get easier to merge if need be (**)

(**) The alternative is to hand-craft a fix for stable channel, which could make the CL a bit smaller, but will cause diverging of the main & stable branches.

Cherry-pick merged as fbbb836a023556b9ea3786f499892d4f72539b4d.

I think the issue stays open until it was released on stable (see https://github.com/dart-lang/sdk/blob/main/docs/Cherry-picks-to-a-release-channel.md#submitting-the-cherry-pick)


Ensure tracing properly happened in kafka ProcessBatch

Following https://github.com/elastic/apm-queue/pull/102, this adds assertions checking that the manual span is indeed created and stopped.

The consumer doesn't do any manual tracing. So it doesn't need a tracer provider. We can add one when we add manual tracing to it.


Adds async reissue notifications

This PR allows celery to handle reissue notifications (send_reissue_no_endpoints_notification and send_reissue_failed_notification) for PendingCertificates upon their resolution to a full Certificate, as opposed to sending reissue notifications while a cert is still in a pending state. This is a subtle change that unlocks, for example, the ability to further customize notifications to include more details about the final certificate, such as its expiration date, rotation settings, and so forth.

This has been merged. Thanks for the contribution @havron !


[Authy] Some records are showing corrupted

Extension
https://www.raycast.com/guga4ka/authy
Raycast Version
1.77.1
macOS Version
14.5 (23F79)
Description
3 of my authy tokens (facebook, instagram and bitfinex) where showing "corrupted". I removed and reinstalled the extension and now all except 1 of my authy tokens show "corrupted".
Steps To Reproduce
N/A
Current Behaviour
Authy extension is showing corrupted for almost all tokens.
Expected Behaviour
Tokens should work.

@raycastbot rename this issue to "[Authy] Some records are showing corrupted"

@leopoldo920c00l Did you try the sync action?

I dont see a sync action under the actions.

Check for the sync option on the non-corrupted token. If that doesn't work, maybe try changing your backup password.

Thanks it´s working after changing backup key.

We have reset the backup key but still no luck. We are on Mac. Also since the update there is no sync action.

since the @leopoldo920c00l's problem has been fixed i'm going to close this ticket @StirStudios we have a follow up ticket i will post update there #13092
@raycastbot close this issue


SortableContainer parent to render the SortableElements

Hopefully not a silly question. I've a pretty long component which is  managing grand grand children. Is it possible some-how to use this library in a declarative way so that a SortableContainer is not encapsulated but its parent can, for instance, render directly the SortableElements? I'm finding myself passing too many things to the list which then passes it to the items. Thanks!

Can you share a snippet of code to illustrate? Your question is a bit unclear

Ops, sorry I missed this. I think it was a silly question. Sortable containers are too dynamic for allowing the grand parents of sortable elements to declare them.


Programming model for runTransaction is hard to use with promises.

For single operations, using promises is straightforward:
function getUser() {
  return transaction
    .run(query)
}

return getUser().then((result) => console.log(result)).catch((err) => console.log(err))

However, the story becomes a lot more complicated with Database.runTransaction. It takes a callback, and doesn't return a promise.
I have a use-case that involves reading from the database, making a request to a remote service, then conditionally writing a row. Finally, I need to do some post-processing on the result. A read-write transaction is important for data integrity. However, the remote request is made with a promise.
Programming this is really quite complicated. In the happy case, I need to put all the post-processing code inside the transaction callback because this:
let user
db.runTransaction(async (err, transaction) => {
 user = await transaction.run(userQuery)
 // ...
})

convertUser(user)

clearly doesn't work because the transaction is run asynchronously and user isn't set by the time convertUser is executed. However, it seems wrong to put object marshalling code inside the transaction when I'm done with all the data needs earlier than that. Error handling for the bad case is also a pain, because any failures in the query or remote request will trigger a promise-rejection, and the handling of that looks pretty confusing code-wise when you're inside a callback.
Ideally, I'd love to be able to do something like the simple case:
user = await db.runTransaction(async (err, transaction) => {
  user = await transaction.run(queryQuery)
  // ...
  transaction.update('users', {updated: data})
  return transaction.commit().then(() => user)
})
.catch((err) => {
  console.log("Error: ", err)
})

where runTransaction takes care of running the callback, returning the result of the commit, or rejecting a promise with an error that happens inside the callback.
(As a side-node, the callback would then no longer need to take an error as its first parameter, because runTransaction could just reject with it before the callback is even started. As it stands, I have to handle the possibility of that error on the first line of every transaction.)
Environment details

Node.js version: 8.11.2
@google-cloud/spanner version: 1.5.0

This has been suggested before, but truthfully I can't remember what the reasoning was for shooting it down. The only tricky thing I see with this proposal would be continuing support for a callback mode.
@stephenplusplus @googleapis/yoshi-nodejs thoughts?

I recall we had promise support and had to ditch it because we can't replay a promise chain when retrying a transaction.

^ Yeah this is the blocker I've run into when going down this path.  This is something we're actively working on creating a cleaner, less error-prone, way to do that fits a bit better with promise based codebases.
I'll report back with any findings, our current idea is to use a using/disposer pattern.
http://bluebirdjs.com/docs/api/promise.using.html

I think what @majelbstoat is proposing is not trying to keep track of the entire promise chain, but allow the callback to return a promise.
database.runTransaction(async (err, transaction) => {
  return transaction.run(`SELECT * FROM Table`)
    .then(([rows]) => transaction.commit());
}).then(() => {
  // transaction finished
});

I know this has been pitched before and shot down

Hmm, could you see if you can find those discussions?

We also get same pain, but we used follow method to kinda make it compatible with async/await .
exports.withTranscation = (fn) => {
	return new Promise((res, rej) => {
		database.runTransaction(async (err, transaction) => {
			if (err) return rej(err);
			let result;
			try {
				result = await fn(transaction);
			} catch (error) {
				return transaction.rollback((rollBackError) => {
					if (rollBackError) {
						logger.error({message: 'Rollback error occur', error: rollBackError});
					}
					return rej(error);
				});
			}

			return transaction.commit((commitError) => {
				if (commitError) {
					logger.error({message: 'Commit error occur', error: commitError});
					return rej(commitError);
				}
				return res(result);
			});
		});
	});
};

@callmehiphop: Yeah, I understand you might want to re-run that callback multiple times, which makes sense (and which I'm glad of!). But when it finally succeeds, getting the final result of it back would be very helpful.

@eric4545, thank you for sharing your code :) do you ever have problems with that if the inner callback runs multiple times due to retries or something? Like promise resolved after rejected, or similar?

@majelbstoat, inner callback you mean the runFn of database.runTransaction ?

@eric4545 yes. As I understand it, the spanner client will under certain circumstances run that callback more than once. (In case of transaction conflicts, IIRC?)

Yes, we did some load test to our system, and our APM show that the runFn have called 26 times.
You are right, the spanner client will exec runFn again and again as long it is retry-able error.

Typically we only retry runTransaction calls for ABORT errors - these usually happen when one or more transactions perform conflicting operations. We also expose a getTransaction method that does not retry, you could use this method to either:

Not retry aborted errors
Create a promisified version of runTransaction

const retry = require('p-retry');
const Spanner = require('@google-cloud/spanner');

const ABORTED = 10;

const spanner = new Spanner();
const database = spanner.instance('my-instance').database('my-database');

function runTransaction(fn) {
  return retry(async () => {
    const [transaction] = await database.getTransaction();

    try {
      return await fn(transaction);
    }
    catch (e) {
      if (e.code === ABORTED) throw e;
      throw new retry.AbortError(e.message);
    }
  });
}

runTransaction(async (transaction) => {
  const [rows] = await transaction.run('SELECT * FROM MyTable');
  const data = rows.map(row => row.thing);

  await transaction.commit();
  return data;
}).then(data => {
  // ...
});

That's really helpful, thanks, @callmehiphop.

If it's helpful to anyone else struggling with this, here's a Typescriptified wrapper:
import { Query, Row, Database as SpannerDatabase, Table, Transaction } from '@google-cloud/spanner'
import retry from 'p-retry'

const ABORTED = 10

type TransactionFn<T> = (transaction: Transaction) => Promise<T>

class Database {
  private db: SpannerDatabase
  constructor(db: SpannerDatabase) {
    this.db = db
  }

  runTransaction = <T extends {}>(fn: TransactionFn<T>): Promise<T> => {
    return retry(async () => {
      const [transaction] = await this.db.getTransaction()

      try {
        return await fn(transaction)
      } catch (e) {
        if (e.code === ABORTED) throw e
        throw new retry.AbortError(e.message)
      }
    })
  }

  run = (query: Query): Promise<[Row[], object]> => {
    return this.db.run(query)
  }

  table = (name: string): Table => {
    return this.db.table(name)
  }
}

export default Database

(This uses typescript types that i defined and submitted to DefinitelyTyped. Currently failing some of their strict lint cases, and probably slightly wrong in one or two places, but mostly usable anyway. Gist of them here: https://gist.github.com/majelbstoat/cfe80d665baec8631d25f10a7b23e917)

Trying to make a version of this without retries but am finding some conflicting info on how to handle errors from commit.
I remember being told on a call with the Spanner team that we should be calling .end() after .commit() if we receive an error from the .commit() call.
Is this correct or is the usage described here what I should follow [0]?
[0] https://github.com/googleapis/nodejs-spanner/issues/103#issuecomment-362056756

Here's what we've cooked up thus far on this front, requires Bluebird:
We're calling rollback() in case a non-spanner related error occurs in the transaction.  I think I remember this function being referred to as safe to call in this way.  .end() call refers to my previous question if commit() fails.  Users of this function could also bail out manually by calling dbTxn.rollback() and returning from their trxFunc below.
// Add disposer to getTransaction
function getTransaction(spannerConn) {
  return spannerConn.getTransaction()
  .disposer((dbTrx, trxActionResultPromise) => {
    if (trxActionResultPromise.isRejected()) {
      dbTrx.rollback();
      dbTrx.end();
    }
  });
}

/*
 * Background info: https://github.com/googleapis/nodejs-spanner/issues/249
 *
 * Promisified transaction helper
 * Returns Promise with transaction result.
 * Will *not* retry automatically on transient errors.
 *
 * @param {Database} spannerConn - Spanner db instance
 * @param {Function} trxFunc - Function to run with db transaction as an argument to perform operations
 */
export function getAndRunTransaction(spannerConn, trxFunc) {
  return Promise.using(getTransaction(spannerConn), ([dbTrx]) => trxFunc(dbTrx));
}

// Elsewhere...

const spanner = new Spanner();
const doStuff = (dbTxn) => {
  dbTxn.insert(...);
  /* ... */
  dbTxn.commit();
};
getAndRunTransaction(spanner, doStuff) // txn cleanup handled for you via disposer
.then((result) => {
  // do success stuff
}).catch((err) => {
  // Do failure things
});

Could fairly easily be combined with the above approaches to retry on transient errors as well.
Disposer docs: http://bluebirdjs.com/docs/api/disposer.html
.using docs: http://bluebirdjs.com/docs/api/promise.using.html

@walshie4 you should call end() after commit() if you're not retrying (if there's an error). end() will release the session from that transaction.

@callmehiphop The documentation says end() should only be called in a readonly transaction. Is that incorrect? https://cloud.google.com/nodejs/docs/reference/spanner/1.4.x/Transaction#end

@majelbstoat generally that is true. All end() does is release the associated session back into the session pool. We basically assume that whenever commit() or rollback() are called, that you are done with the Transaction. In the event that either of those calls fail, we don't call end() in case you start making more requests.

The takeaway is that our users want a Promise friendly version of runTransaction. I think our best plan of action would be to wait and follow the changes outlined in https://github.com/GoogleCloudPlatform/google-cloud-node/issues/2556#issuecomment-402016599 - which will make supporting this feature much easier.

We basically assume that whenever commit() or rollback() are called, that you are done with the Transaction. In the event that either of those calls fail, we don't call end() in case you start making more requests.

A bit confused by this.  What do you mean by in case you start making more requests?
Would that include the case of the transaction being retried automatically?
Related to that, if .end() were called inside a transaction after a transient .commit() or .rollback() error was thrown would the retry try to acquire a new session or because the one it was holding was released would fail with a non-transient error?

A bit confused by this. What do you mean by in case you start making more requests?

If for some reason commit or rollback throw an error (this includes us retrying internally and it still failing) we don't release the session. I think the main use case is to allow users to try and rollback on a failed commit. @snehashah16 should we always call end here?

Would that include the case of the transaction being retried automatically?

We don't throw an error until after we've retried internally.

Related to that, if .end() were called inside a transaction after a transient .commit() or .rollback() error was thrown would the retry try to acquire a new session or because the one it was holding was released would fail with a non-transient error?

Assuming the callback for rollback/commit was called, we've already stopped retrying the transaction function. These two functions callbacks shouldn't get called until we've either 1. succeeded or 2. hit our retry limits.
As far as retrying a transaction goes, we do not fetch a new session, but instead begin a new transaction on the same session that was used prior.

Made a gist here [0] with a sample runTransaction setup to help explain this in the future, would really appreciate it if @callmehiphop @stephenplusplus or someone else could chime in if this is correct.
The main thing I'm unsure of is if I need to call rollback if commit fails.
On that note regarding your answer above:

I think the main use case is to allow users to try and rollback on a failed commit.

Can you elaborate here?  How could one rollback a failed commit?  If it failed isn't there nothing to rollback?  Or are you referring to the locally queued operations?
[0] https://gist.github.com/walshie4/d340f7f91cf396326933af5a7b835fa6

@walshie4 currently that is correct, there would be nothing to rollback, however my understanding is that soon there will be other asynchronous ways to update/insert data besides commit.

"soon there will be other asynchronous ways to update/insert data besides commit"
that is intriguing 🤔

Yeah for sure, @callmehiphop do you have any other details or general examples in the space you could point to for more details about this future functionality?
Also less related will either you or @stephenplusplus be at Google Next next week in SF?

Just to update this, you actually get (further) errors if you're trying to rollback after an error on commit():
Cannot rollback a transaction after Commit() has been called
It does make it a bit tricky to write a single general-purpose wrapper for a transaction where you don't know if commit was called or not (if the error happened earlier in the transaction, like a not found error or something). Would be nice if rollback() after commit() was just a no-op.

@walshie4 I've probably already said too much! And I wish, but I am unable to attend. :frowning:
@majelbstoat I'm not sure if the client library is the right place to make a change like that, but we could add a committed property to the Transaction object that indicates whether or not a commit occurred, making it easier to determine. Thoughts?


azure/login pre step takes up to 1 minute to execute

Observed behavior:
The pre step in azure/login takes up to 1 minute to execute. Very seldom does it take a few seconds to execute. In some of our builds this accounts for half the total build time.
Expected behavior:
The step should consistently execute in a few seconds.
Information:

azure/login@v2
Authenticating against Azure public cloud
Using OIDC credentials
Running on GitHub hosted runners

Used as:
- name: Login to Azure
  uses: azure/login@v2
  with:
    tenant-id: ${{ secrets.AZURE_TENANT_ID }}
    client-id: ${{ secrets.AZURE_CLIENT_ID }}
    subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }}

Resulting in:

What can be done to speed this up?

Agreed, this needs to be sped up or should be made conditional.

This step is consuming 10 to 15 percent of our GitHub Actions build minutes as is costing us money. This should be fixed as a high priority please.

Hi @olafurnielsen and @damianh, we've released a new version v2.2.0. In this version, we removed the pre step and add 2 env variables to enable/disable pre or post cleanup.
v2 is aligned with v2.2.0 now.
Please try the new version. You can also refer to Enable/Disable the cleanup steps.
Just FYI, the time cost is mainly for login context initialization. After we remove pre step, the main step may need more time.

Hi @YanaXu, thanks for your reply.
Replying to your questions:

We do use self-hosted runners, which are provided on our enterprise github instance. They run ubuntu.
My idea would be to optimize the best I can.. For instance, imagine that I provide a composite action that fetchs secrets from key vault; If I could cache that login for posterior invocations of that same action it would improve the time consumed... To make It useful, it would have to keep that "state" through different workflows.

Regarding the time cost you present, I haven't been able to reproduce logins near those ones values.. The full roundtrip of login + fetch one secret from key vault took from 1m:13s up to 1:50s.

Any news here? I’m experiencing timings in the ballpark of 30-45 seconds at times when using this action. Surely something as simple (I know it’s not actually that simple, but still) shouldn’t take more than 5 seconds.


Recommend MaybeUninit now that it's stable

The nomicon still recommends mem::uninitialized in the "Unchecked Uninitialized Memory" section.

cc @RalfJung @steveklabnik

Cc @Gankro this basically needs incorporating your blog post :)

I submitted a PR at https://github.com/rust-lang-nursery/nomicon/pull/153.


Old Distributions

There are a couple of distributions in qinfer/distributions.py that I think have been superceded by new ones in qinfer/tomography/distributions.py and should be deprecated:

HaarUniform
GinibreUniform
HilbertSchmidtUniform

Also, I think MVUniformDistribution has a confusing name. I think maybe it should eventually just be replaced with a more general Dirichlet distribution.

I agree, and will PR soon to mark those as deprecated. I also think it makes sense, in light of your point about MVUniformDistribution having a confusing name to deprecate that as well, pending a better named or more general class.

Thanks. The PR could also include a link between the tomography.distributions and distributions in the API docs.

That's a good suggestion, I'll add that as well.


Monitored Regions are Exited when they really weren't

Currently I have the standard notification app example up and running. I post a local notification using UNNotificationCenter on iOS 10.3.2 when the iPhone device enters and exits a beacon's region.
The setup was fairly simple and pretty much emulates what the Estimote tutorial outlines. For some reason, when I watch the sample for a long enough time (5 mins) the delegate method beaconManager:(id)manager didExitRegion:(CLBeaconRegion *)region is called. This means that in a matter of minutes the didEnterRegion will also be called. Thus we are getting so many notifications even though the phone or beacon hasn't moved. At first I thought it may have been an issue with the beacon,  but I have tried this same code with multiple different Estimote beacons.
Is this something that is expected to happen or a bug? If this is expected, is there any accepted workaround that people are using today? I assume that I may have to locally debounce the calls in a sense so that if you leave and then enter in a minute or two, that the leave didn't really happen.
Any help is definitely appreciated. Thanks in advance!

Looks like this is a common issue with Core Location.


Fix monkey kitchen spike dragdrop

I also aligned the behavior with tg (need combat mode on + mob alive).
It still needs to do damage over time and buckle the target but baby steps.
:cl:

add: Monke kitchen spikes

Closes  #3427 ?

fix conflicts

I'll fix your conflicts


Updates vendor directory

Cleans up grunt tasks. Part of DF-1857.
Additions

Added box-sizing-polyfill to exportsOverride as needed for grunt-bower-task to work correctly. box-sizing-polyfill is installed by cf-grid.
Added grunt watch:js task for completeness.
Added vendor directory variable to main.less.
Adds warning for concat:cf-less Grunt task when sourcefiles are missing.

Removals

Removed unneeded entries from exportsOverride in bower.json.
Removed CF fonts, "chosen" images, and other vendor files from repo.

Changes

Changed vendor directory to src/vendor and updated paths.
Changed to using jit-grunt in place of load-grunt-tasks.

Testing

Run:

./setup.sh

Site should function/look the same.
Review

@sebworks
@jimmynotjim
@KimberlyMunoz

Notes

Fixes https://github.com/cfpb/cfgov-refresh/issues/302, with the exception of using the existing vendor task in place of compile-cf, since compile-cf doesn't just compile CF components. Also, fixes errors in bower:process that exist in generator-cf.
Sorry for the weekend update. This needed a lot of testing and since I'm out most of next week I wanted to get it in before I forgot what on earth I was doing. Doesn't have to be in this sprint.

Looks pretty good. Small note about parens but I think this can be merged after the Sprint PR is merged to make sure we're not dropping a bomb right before sprint review and to give us the next sprint to debug any possible issues.

Fixes https://github.com/cfpb/cfgov-refresh/issues/515 in https://github.com/cfpb/cfgov-refresh/commit/e34401e4933f418bb4ee686b4e695c750f6e3b9b

After merging this and #554 into a test branch I'm getting a grunt error for the 'default' task.

Holding off on this one till after all hands meeting @2pm 5/20.

Can be tested by dropping test_grunt_tasks.sh in the root directory with the contents of
https://gist.github.com/anselmbradford/60d0a17d04639ee704e1 and running ./test_grunt_tasks.sh

I keep getting a git diff with changed paths on some of the images that chosen is pulling in. I'm double checking to see if there's old stuff from another branch that's causing that.

@KimberlyMunoz That looks correct. It's being set here. Those are analogous paths, the structure is:
static
|
+— css
|   |
|   +— main.ie.css
+— img
|   |
|   +— chosen-sprite.png

I'm forgetting why I updated it to be absolute vs relative, but the bower task moves the chosen images so maybe just to make it clearer where the image was coming from. This should probably be re-visited in https://github.com/cfpb/cfgov-refresh/issues/559

In that case, can you commit the different built files there so they don't get added in another pull request?
Also, is there an issue to just get rid of checking in built files in general? :stuck_out_tongue_closed_eyes:

@KimberlyMunoz SOON! :smile:

@KimberlyMunoz Ah! Certainly. Sorry I misunderstood, I didn't realize there were compiled assets that weren't included. Fixed in https://github.com/cfpb/cfgov-refresh/commit/c4abfbc484d1c9591bea9d90ef47a39099cebcd9

How's this look now?

:+1:


Reformat to Google Style for C++ and Add CI Linting

Reformat files to Google C++ style guide standard. Files included are all *.cpp, *.h, and *.hpp excluding those in external or nmpc_controller/gen.
Add scripts/ folder in root with lint_soft.sh and lint_hard.sh which check the repo for formatting with relaxed and strict requirements respectively
Update CircleCI config to require lint_soft.sh to pass without errors.


refactor: project upgrade

:tada: This PR is included in version 0.56.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


morning

"To maintain a stable job and give the best of me, I must continue to train and provide my best effort to succeed as a very responsible professional capable of solving big and small problems."

I agree, that's a very good attitude. Good luck with it.


search-bug-fix

bug fix - #22

@devjainofficial check it.
also label it under hacktoberfest and hacktoberfest-accepted.

@devjainofficial also please add "hacktoberfest-accepted" label so hacktofest org. can recognize this PR.


add yamato security log config guide

Just saw #11 already suggested my addition but did not include a description for it. Maybe you can use a combination...

Since #11 submitted in parallel but short time earlier I'll close this. Maybe next time.
Anyway thank you for your contribution!


Icon list that we can use in SidebarNav

LOCAL ENVIRORMENT

Operating system and version (Windows, Win10)
Browser and version (Chrome)

ISSUE
in: src\containers_nav.js
Can't use for example:
icon: 'cil-blind',
I would like to have a list of usable icons for SideBarNav.
cil-speedometer: works
cil-pencil: works
cil-blind: not works
cil-bar-chart: not works
and so on...

Hi,
In scr/main.js a set of icons is made globally available by importing iconsSet from src/assets/icons/icons.js:
https://github.com/coreui/coreui-free-vue-admin-template/blob/9d65013c0f683a70d986040e63e84459a4933d5d/src/main.js#L6
To utilize more icons in _nav.js (or wherever) import/export them in icons.js.
For more information about working with the Icons component i would recommend reading the Icons section in the CoreUI docs.

Thanks a lot!


Fix browser markdown

Fixes #451. Based on PR #505.
I also wrote a test to verify the conditions mentioned by the deleted user from #505 and @lvxianchao. We were returning null in the browser.

@j-rewerts I just looked and there's one markdown related test failing on this PR

@clayreimann Okay I think it should be good.


Initialize CredScan Job in CI

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:
docker run -it microsoft/azure-cli:latest
export EXT=<NAME>
pip install --upgrade --target ~/.azure/cliextensions/$EXT "git+https://github.com/haroldrandom/azure-cli-extensions.git@credscan#subdirectory=src/$EXT&egg=$EXT"


HUD Freezes On Reaching OT, OT2, etc.

So I took the HUD for a spin today, and hopefully got some valuable information for you! https://www.twitch.tv/videos/1940631033
However a glaring issue is that the HUD will partially lock up when you first enter OT, and every time a new OT starts, i.e. OT1, OT2, etc, and the only fix being a forced refresh every time a new OT is reached.
Similarly, in Overtime, the round counter up the top will show 1/6, 2/6, and then not change for Round 3 but updates to Round 4 afterwards.
You should be able to find examples of both of these in my VOD linked above, in the first two matches. Match 1 has OT2, Match 2 has OT5. I hope this VOD helps with seeing things in live production!

These were CS2 matches, right?
Are there demos available for one of the OT matches by any chance?
Overtimes in CS2 matchmaking seem to work perfectly fine, I didn't find any CS2 demos on HLTV, and I couldn't get any Faceit demos to even play at all :D
If you don't have any demos, could you try to record a POV demo next time you're casting? Might still not work, would like to give it a try :D

Sorry for the hella late reply! I investigated into if I could share demo files externally, and the answer was a no, I'm afraid.
There is a match on tonight that I'll be broadcasting, I'll happily link you the VOD once I'm done, but for now here's the hltv link: https://www.hltv.org/matches/2367227/hsg-fe-vs-stacks-of-cash-esl-impact-league-season-4-finals-asia-pacific-open-qualifier
Hopefully this will help nail down the cause(s)! Otherwise, I'm hearing plenty of positive feedback around your HUD, and I've also been plugging it every time someone mentions it, with a link in my bio on Twitch.

I don't think I can do much with a VOD unfortunately :/ But different strategy, this might work:
Open up the HUD in your browser (http://localhost:31982/hud), and press Ctrl+Shift+J. Then get to an OT where the HUD breaks (I'd assume this happens when watching a demo if you have one available, but if it doesn't, maybe you could leave this browser tab open in the background during your broadcast tonight?)
Then, when the HUD breaks (before you refresh it!), right-click in the Console panel (the one that opened when you pressed Ctrl+Shift+J), right click, Save as... (Chrome)/Save all messages to file (Firefox) -- then either upload it here or send me an email with it.
That log file should tell me where the issue is :D

Is this still an issue on v2.3.0?

Gonna close this one for now, feel free to reopen if you're still seeing this.


Update operations don't currently check against any signature

This line:
https://github.com/itchio/butler/blob/e8ae88f002a8e830b24538f76f9738c775990164/cmd/operate/upgrade.go#L235
is a lie.
It doesn't actually fetch signature info, and it never actually checks.
We need a way for the patcher to tell us which files were touched, or to validate in advance the files that are read from for patching (probably better?).

TODO:

[ ] Write a failing test for that

That test should install a version of a game, mess with its files, then install an update which relies on the old files being intact
The upgrade should actually work, but we should make sure it used a heal fallback

[ ] Add facility to pwr/patcher to pass in a validating pool instead


Internet Explorer 11 Broken

It looks like the most recent release of docsify v4.6.1 isn't compatible with IE11.
This crashes IE :(
new RegExp(/^!?\[((?:\[[^\]]*\]|\\[\[\]]|[^\[\]]|\](?=[^\[]*\]))*)\]\(\s*<?([\s\S]*?)>?(?:\s+['"]([\s\S]*?)['"])?\s*\)/, 'g')

Blame 62ce447fc3dd1ced843437b70f981490df69b856
https://github.com/QingWei-Li/docsify/blob/master/src/core/render/embed.js#L54

Oops, duplicate of #389


Add support for HiDPI (Retina) screens in Qt GUI.

Proposing minor change to add HiDPI (Retina) support to the Qt GUI.
It is activated by setting NSHighResolutionCapable to true in the Info.plist of the application.
Here are two screenshots showing the Qt GUI before and after the change:

Thanks.  Applied as commit a41ebd4ee5b01c92958a28ca2e57b2b6446bf334 with minor tweaks to the commit message.


Partial support for multiple views in Scene

Extracted from  https://github.com/AnalyticalGraphicsInc/cesium/pull/6934. Review after https://github.com/AnalyticalGraphicsInc/cesium/pull/6957
Scene.js now has a concept of Views where each view contains framebuffers, command lists, cameras, and viewports specific to that view. The coming sampleHeight and pickRay functions use a separate 1x1 orthographic view.
While working on this I've been thinking a lot about how we might eventually support multiple views on the same screen. I think this PR brings us like 50% there but there is still a lot of work to do. drawingBufferWidth/Height is hard coded almost everywhere... Getting full multiple viewport support goes beyond this PR.
This doesn't add new functionality to the API so no tests or CHANGES.md update are needed.
@bagnell can you review this one as well?

Thanks for the pull request @lilleyse!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:

I changed the base to scene-cleanup for an easier review. When they're both ready, I'll merge this and merge the other into master after the next release.

This looks good. The motivation for moving most of the camera/frustum culling into view is so we can do something like this in the future:
for (var i = 0; i < views.length; ++i) {
    var view = views[i];
    updatePrimitives(scene, frameState, view);
    view.createPotentiallyVisibleSet();
    executeCommands(scene, view);
}

I'm not sure how we consolidate all of the framebuffers yet (like the post-processing step for OIT).

There were no issues when testing (except switching log depth like in the other branch), even using different render paths. 👍

@bagnell thanks for the ideas for improving the organization, this should be ready now.

:+1:


navigator move parameters out of MissionBlock interface

MissionBlock is an interface with 10 derived classes (Mission, RTL, etc), so we need to be careful when giving it additional state.
The fairly simple rearranging in this PR (mostly moving a few things) saves 1.5K of memory.
I'll do some careful testing here, then ask @PX4TestFlights to test.
@sanderux @bresch could you review the vtol changes?

Did you test weathervane in sitl?

I'll rebase and do some SITL testing.

I will test this next week

Tested in SITL.

@PX4TestFlights please help test, @dagar please guide the test team

The main thing this PR needs is to verify that all VTOL weathervane functionality hasn't regressed.

Consider my question obsolete.

MC POSCTL mode: https://logs.px4.io/plot_app?log=17d97314-60a4-44cc-8859-b11ad1c2047f#Nav-Yaw-Angle


fix: qr visibility improvements

This should fix #1120 the only thing I have left on this is to make the square a circle. @kevmo314 Whats the best way you think to do this without modifying the package?

This should fix #1120 the only thing I have left on this is to make the square a circle. @kevmo314 Whats the best way you think to do this without modifying the package?

Screenshot of what it looks like right now?

we should get the middle part to look something like


Error: Couldn't create downloads directory

I follow the build instruction on an aarch64 machine. Building itself was successful, but when running bob list I got
ERROR Error: Couldn't create downloads directory

@kumkee What OS are you using on ur aarch64 machine?

@kumkee What OS are you using on ur aarch64 machine?

Debian on Chromebook.

@kumkee could you manually run mkdir ~/.local/share/bob and see if it still works?

@kumkee could you manually run mkdir ~/.local/share/bob and see if it still works?

Sure, but I won't be able to do that until tomorrow. Will let you know the result. Thanks for your prompt response.

@kumkee no problem! intuitively I think the problem might be caused because you don't have /.local/share in ur home dir but that is just a guess.

I can install neovim after manually creating the folder.
However, it got
zsh: permission denied: .local/share/neovim/bin/nvim

Does it have anything to do with the fact that I am using an ARM architecture?

What was the command that you ran that caused this permission error?

nvim

@kumkee weird... can you show me your PATH?

can you run bob ls?
also what happens if u run sudo nvim?

can you run bob ls?

$ bob list
Version | Status
--------+----------
v0.8.0  | Used

also what happens if u run sudo nvim?

$ sudo .local/share/neovim/bin/nvim
.local/share/neovim/bin/nvim: 11: Syntax error: "(" unexpected

@kumkee what if u change in path from $HOME to the full path?(I doubt if it would matter but I have no idea what is causing this weird error)

Just found out $HOME/.local/share/neovim/bin/nvim is a symlink to $HOME/.local/share/bob/v0.8.0/nvim-linux64/bin/nvim.
The name of the latter suggests it is for x86_64 instead of arm64.

Yeah that's true but neovim doesn't really publish any arm64 binaries as far as I know

That is the answer then.
Does bob provide an option to build neovim from source?

@kumkee yeah for sure with the latest release!
But i am unsure if it will work on arm... but you can try.

@kumkee any luck with building?

Haven't got a chance to try yet.
What is the bob installation flag for building neovim from source? I don't see that in your readme.

bob install <commit-hash>

No update step for 'unibilium'
[ 49%] No patch step for 'unibilium'
[ 50%] No configure step for 'unibilium'
[ 51%] Performing build step for 'unibilium'
make[4]: Entering directory '/home/[username]/.local/share/bob/neovim-git/.deps/build/src/unibilium'
make[4]: libtool: No such file or directory
make[4]: *** [Makefile:69: unibilium.lo] Error 127

I have confirmed that I have libtool and met building requirement

@kumkee hmmm I see,
listen what you can try...
git clone neovim repo and run this command make CMAKE_BUILD_TYPE=RelWithDebInfo
its more or less the commands bob uses, but I just want to see if u get the same errors if u do them manually...
And I don't really see any arm specific docs in their wiki.

@kumkee I suggest we move this to a discussion and close this issue.

Makes sense.
It unrelated to the title now


Add CException library to project

Added on commit. https://github.com/Nietaktowny/esp32_oscilloscope/commit/1af128302f8cc6af178e9b4bf5bd3ee749870a6c


Fixed errors

Fixed figure3.py and evaluator.py.
Let me know if there is something wrong.

Needed additional changes


Remove unnecessary label title

Remove unnecessary title attribute on <InputLabel/>. Currently there is a title that says "required field" when the input is marked as required which can end up overriding the accessible name for the input. The first screenshot shows how the a11y labels are parsed when trying to use getByRole('textbox', {name: TEXTINPUTFIELD_LABEL_TEXT}). As you can see, the title overrides the label text which will be particularly confusing on a page with multiple required inputs as the a11y tree will show multiple text inputs all with the "required field" name.
In this PR I simply remove the title attribute because the necessary "required" information is already passed to the <input/> itself with the required attribute.
Screenshots

No visual changes (unless you count the lack of a title when hovering as one).
Merge checklist

[X] Added/updated tests
[X] Tested in Chrome
[X] Tested in Firefox
[ ] Tested in Safari // I'm on windows
[X] Tested in Edge

Bonus side-effect showing how it fixes the issue with Testing Playing (for testing-library):
For required fields with fix applied:

Trying to do the same without the fix applied:

@pksjce Do you think you could take a look or assign the right person? Thanks!

LGTM. Thanks for raising this PR @PeterYangIO.
@alliethu @mperrotti  - Do you see any issues if we stop the title attribute automatically being applied to required fields? It also seems to prevent users from applying custom title values in the InputField component.

Hi @rezrah I do not have merge permissions for the repo, if you think it looks good do you think you could merge it?
Thanks!


Native templates

Description
Merge native templates implementation into main.

https://github.com/googleads/googleads-mobile-flutter/pull/727
https://github.com/googleads/googleads-mobile-flutter/pull/732
https://github.com/googleads/googleads-mobile-flutter/pull/740
https://github.com/googleads/googleads-mobile-flutter/pull/742
https://github.com/googleads/googleads-mobile-flutter/pull/744
https://github.com/googleads/googleads-mobile-flutter/pull/747

Related Issues
*Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See [Contributor Guide]).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the [Flutter Style Guide].
[x] I signed the [CLA].
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

This is great!
Any plan for releasing new version on pub.dev?


Raise test coverage to at least 80%

[x] 10%
[x] 20%
[x] 30%
[x] 40%
[x] 50%
[x] 60%
[ ] 70%
[ ] 80%
[ ] Make test suite more portable between php versions (use @group for specific versions)

A mayignore group was added to ignore redundant tests on travis.


Explicitly set fill_value when saving netCDF3 masked non-byte data

Workaround for https://github.com/Unidata/netcdf-c/issues/499.
To be honest, I'm not that happy with this. I'm pretty sure there's actually no issue with saving netCDF3 datasets with no fill value - the _NoFill attribute isn't being set in the file. The issue is reading them back again. There's currently no easy way to determine whether _NoFill is set on a dataset via the netCDF4 Python or libnetcdf APIs, so our only option is to explicitly set the fill value.
Just to be absolutely clear:  the only thing this PR gets us is round-tripability.

Here's the issue in the netCDF4 Python repo: https://github.com/Unidata/netcdf4-python/issues/725#issuecomment-337011129.
It looks like there may be a temporary fix coming shortly in that library to disable 'no fill' for netCDF3 files.

Having spoken to @djkirkham in person, we agreed to reject this PR in favour of updating the round-trip test to explicitly set the fill value. This is supported by the fact that this is recognised as a bug in the netcdf4-python layer and will be fixed post 4.5.0.


Previous/next functionality not working correctly for hierarchy topics with paging

Describe the bug
The code inside SearchPrevNextSection class appears to not be handling paged results inside hierarchy topics correctly, when you use the previous/next buttons to navigate between results. Once you get to the end of the first page of results inside hierarchy topic a standard search (via searching.do) is performed, which causes the wrong item it be displayed. You can see this code on line 109 of SearchPrevNextSection.java
All of the code in that file is a real spaghetti mess, and looks to be fragile. Tread lightly
To Reproduce
Steps to reproduce the behavior:

Configure a hierarchy topic that will have multiple pages of results
Click on the hierarchy topic to display the first page of results
Navigate to the second page of results, make a note of what the item at the top of the page is.
Go back to page 1 of the results
Click on the item at the bottom of the hierarchy search results on page 1 to bring up the item summary
On the item summary page click the grey 'Next' button (top right of the page)
The item you are taken to will be different to the one you noted down in step 3

Expected behavior
Clicking the next/previous buttons should always take you to the next item within the same search
Platform:

OpenEquella Version: 6.4, 6.5, 6.6, 2018.2, 2019.1
OS: Windows 10
Browser Chrome

Verified in 2019.1


Run scheduler only for production

I'm trying to run the scheduler in the production environment only, however it seems to work in any environment. I've tried disabling scheduler using SidekiqScheduler::Scheduler.instance.enabled but it doesn't seem to work (below you will find my config files).
When Sidekiq starts it states that it runs in the development environment, however it still loads the schedule.
# initializers/sidekiq.rb
Sidekiq.configure_server do |config|
  config.on(:startup) do
    SidekiqScheduler::Scheduler.instance.enabled = Rails.env.production?
  end
end

# sidekiq.yml

:concurrency: 10
production:
  :concurrency: 10
:queues:
  - default
:limits:
  tim_integration: 5
:schedule:
  # Warehouses tasks
  grodno_update_stocks:
    cron: '0 3-23 * * *'
    class: Grodno::Inventory::UpdateStocksWorker

@tomaszwojcik I'm not sure how to do this with the schedule embedded in sidekiq.yml, but we achieve this by using a separate yml schedule for each environment, some of which may be blank:
  config.on(:startup) do
    Sidekiq.schedule = YAML.load_file(Rails.root.join("config/scheduler/#{Rails.env}.yml"))
    SidekiqScheduler::Scheduler.instance.reload_schedule!
  end

If you use this approach, move the contents of the schedule block from sidekiq.yml to config/scheduler/production.yml. You could either create empty schedules for the other environments or add a guard close to prevent error on file load.

@bpo Seems to work, also good idea to separate them! Thanks!


What do you need to add support for iOS 15.3.1?

I’m on 15.3.1, which is not supported by the tweak. What do you need to add support for iOS 15.3.1? Thanks in advance!

It's supported for arm64e.
If you are on arm64, you would have to provide your bluetoothd located at /usr/sbin/bluetoothd.


Does not compile on Windows, windows_sys::Win32::Storage missing

I'm trying to use is_terminal as a dependency in my project but it doesn't compile on Windows, complaining that the module windows_sys::Win32::Storage doesn't exist. Modifying is_terminal's Cargo.toml like this makes it work:
[target.'cfg(windows)'.dependencies.windows-sys]
version = "0.42.0"
features = [
    "Win32_Foundation",
+   "Win32_Storage_FileSystem",
    "Win32_System_Console",
]

So the fix should be straightforward, however, I'm not really sure how all those other people who presumably use this crate on Windows managed to get it to compile without this feature flag?

Cargo unifies features across all dependencies, so if other projects depend on something else which depends on windows-sys with "Win32_Storage_FileSystem", then it gets enabled for is-terminal too. That's my guess of how this works for everyone else, at least.
I've now opened #14 to fix this.

This is now fixed in 0.4.2.


chore: fix the config in scheduler_perf

What type of PR is this?
/kind cleanup

What this PR does / why we need it:
The previous one is the old format, which is not valid anymore.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?

NONE

What are the benchmark results of this change?

/cc @Gekko0114 @utam0k


Supress deprecated message in SensorFacade

this is test (python script) problem.
In android 5, deprecated cause application error...


Upgrade TransactionHandler: Improve readability and error handling

Simplified the String() method for TransactionHandlerType:

Removed the error return, as it's not necessary for a String() method.
Used a switch statement without fallthrough for better readability.
Added a named error ErrInvalidTransactionHandlerType for better error handling.

Improved the Call method:

Used make to pre-allocate the values slice with a capacity of 2.
Renamed someResp to response for better clarity.

Refactored the NewTransactionHandler function:

Extracted the validation logic into a separate validateTransactionHandler function for better readability and maintainability.
Used fmt.Errorf with %w to wrap the error and provide more context.

Improved error messages:

Used errors.New for static error messages.

Used fmt.Errorf for dynamic error messages.

Updated the struct initialization in NewTransactionHandler to use field names for better clarity.

Signed-off-by: Bhaskar Allam<EMAIL_ADDRESS>

I should update transaction_handler_test.go also and run Unit Tests againest transaction_handler.go , right ?


How do I provide release variables when invoking via a trigger, REST or an Azure Logic App?

There doesn't appear to be documentation anywhere about how to provide this, yet I can set variables when I manually create them in the dashboard.
Related

https://feedback.azure.com/forums/287593-logic-apps/suggestions/36074281-azure-devops-releases-allow-variables-to-be-spec
https://developercommunity.visualstudio.com/content/idea/388532/specify-variables-with-release-trigger.html
https://twitter.com/Omega_/status/1065271010876903425

Without an option to provide variables when triggering builds, I end up having to do this, which is less than ideal:

The problem here is that if I need to update my pipeline, I now have to hand-edit it in two places rather than using a single consistent one.

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

ID: 611642f0-881f-10b9-ae94-3c562001d1f0
Version Independent ID: 41efb94b-4c7a-64a3-b23b-70c8634ae727
Content: Release variables in Azure Pipelines - Azure Pipelines & TFS
Content Source: docs/pipelines/release/variables.md
Product: devops
GitHub Login: @alexhomer1
Microsoft Alias: ahomer

Thank you for your feedback. I have passed this on to the product team for advice.

@atrauzzi Can you please look at method CreateRelease in this file  and see whether it works for you or not?

@bansalaseem - I have no idea what this file is doing or how it pertains to my original issue.

I am also very interested in some documentation or tutorials on the matter.
Also i've noticed this line when creating a draft release but couldn't find the informations in the linked documentation (learn more link).

It seems documentation isn't even available through basic trigger, let alone through Rest API.
Thanks you.

@bansalaseem - I'm still waiting for you to respond. I'm not sure you understood the original question.

@atrauzzi , I am assuming that you are looking for a rest API with which you can specify variables at release creation time. If yes, this API should help.
https://docs.microsoft.com/en-us/rest/api/azure/devops/release/Releases/Create?view=azure-devops-rest-5.0

This ticket specifically states for an Azure Logic App task.  So I'm not responsible in this case for constructing an API request.

I did not get your question then. Can you please share the screenshots of the mechanism that you follow via RM UI today so that I can tell you how can achieve the same thing via API?


Missing "VpnConnectionOptionsSpecification" options in the LZA

**Is your feature request related to a problem? yes, we don't have option to specify the LocalIpv4NetworkCidr  & RemoteIpv4NetworkCidr in the LZA code.
LocalIpv4NetworkCidr -> (string)
The IPv4 CIDR on the customer gateway (on-premises) side of the VPN connection.
Default: <IP_ADDRESS>/0
RemoteIpv4NetworkCidr -> (string)
The IPv4 CIDR on the Amazon Web Services side of the VPN connection.
Default: <IP_ADDRESS>/0
Describe the feature you'd like
Need to have the options to add specific CIDR to the VPN connection

Hello,
Thank you for using the Landing Zone Accelerator on AWS solution. I have gone ahead and file a feature request for this. In the meantime, I will leave this issue open for further communication and we will keep you up to date on this feature.


test/secmemtest.c: clarify limitations for huge secure memory arena test.

[skip ci]
Pure commentary update related to #3455.

This is not applicable to 1.1.0, at least not yet...


Errors when accessing UI with firefox on Linux

I receive errors when attempting to connect to PCUI with firefox 115.7.0esr (64-bit) on Rocky-linux 8 running on an EC2 machine in same VPC.
Upon attempting to connect, after entering username/passord, I get error message:

Then clicking through, I ultimately get two red error bars at the top that state:
Error retrieving images: Iinternal server error

Yet I can click on images and they are there.
I have cleared my cookies and I have no plug-ins on my firefox session.
Then functionality seems to continue as per normal - though I haven't done much other than view the
Official and Custom Images
View Cluster configuration YAML.
I do not get this when running google-chrome on Rocky 8.
My cluster is running 3.8.0.

Follow up on this.  I logged out, logged back in, and just keep getting the first error with the Go Back to Home Page. I click on it, and I just come back to this same error screen.  Ultimately, just a white screen.  Even more dead. That said, chrome on Linux and Windows work just fine, as well as Edge on Windows.

Confirmed that this is still happening on 3.10.1. Created a completely new AWS account with nothing else in it, ran the PCUI CF template. Created successfully with no errors, Firefox brings up the "Something Went Wrong" window. Chrome no issues.


Use ast_decompiler from pypi when ast.unparse isn't available

I generally don't like adding dependencies to projects, but I think it's justified in this case:

The dependency does something nontrivial. It is about 1100 lines of code.
The dependency is used only with older Python versions.
We trust the author of the dependency.
We can do better error messages with the dependency.
Code is cleaner with the dependency.

This is great.

Should we maybe add something to the changelog about dropping the attrs dependency and adding this one?

We can switch to a different library later if needed, but we shouldn't need a well-maintained library, because the library is used only on the ast of older Python versions.


IP Address range public over VPN

All the screen shots show private IP address ranges, can you clarify that they should be used instead of public ones.
Also,if using a VPN we still use these ranges or do we need to use the public IP address of the VPN far end?

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

ID: 84b26750-880c-8f14-1628-436293de915e
Version Independent ID: 518b727f-79e8-b5c2-bcb3-ff4de3444c6f
Content: Configure Azure Multi-Factor Authentication - Azure Active Directory
Content Source: articles/active-directory/authentication/howto-mfa-mfasettings.md
Service: active-directory
Sub-service: authentication
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@HareBear Thanks for your feedback! We will investigate and update as appropriate.

@HareBear  it should not need to be private. If you don’t have a federated environment, you can add public IPs into the field of “Skip multi-factor authentication for requests from following range of IP address subnets." This will skip MFA regardless of if the user is federated or managed, once the request comes from a whitelisted IP. https://blogs.technet.microsoft.com/latam/2018/08/18/skip-mfa-o365/
For your second question, you should just be able to list the public egress IP of the VPN.
I made a pull request to add a note that you can use either private or public. https://github.com/MicrosoftDocs/azure-docs-pr/pull/94561
@MicrosoftGuyJFlo can you confirm that this is accurate before merging this?


log: set level=error for .LogError and .LogErrorf

Previously you could get logs at info/debug/etc levels with errored=true that aren't level=error.

Talked this over. It's probably too much of a breaking change to make this many years later.


Avx

👍 Thanks!

@alexcrichton this PR broke the rustfmt build. We should either check that it doesn't break or... just allow the build to fail because of it. I mean, worst case we can't commit one day because rustfmt fails to build but... that is fixed quickly, and as soon as it is shipped with rustup this will never fail.

@gnzlbg oh I'm in "if it's green we merge it" mode, I'm not looking at the test results to see if the "allow fail" entries are failing.

I'm in the same mode :D
On Thu 2. Nov 2017 at 03:32, Alex Crichton<EMAIL_ADDRESS>wrote:

@gnzlbg https://github.com/gnzlbg oh I'm in "if it's green we merge it"
mode, I'm not looking at the test results to see if the "allow fail"
entries are failing.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rust-lang-nursery/stdsimd/pull/163#issuecomment-341300274,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA3Npr409IGFqb2w-qi2tmvjaG0fFHGNks5sySnKgaJpZM4QOCau
.


Disable region change popup

Greetings. When switching from Honkai to Genshin or vice versa, a popup says that the game region will be changed even when the region is the same. I have never installed or played either game on servers other than the global server, so I'd like to request the option to disable this popup and streamline switching games.

Thank you for your suggestion on this.
However, this has been issued and a duplicate of #18.
I think we will implement a toggle to disable this confirmation dialog in the future.
For now, we will be tracking this suggestion on Issue No. #18.


Fix container components

Fixes containers not working as reported in https://github.com/mui/mui-toolpad/discussions/2613
When changing things so that we don't need PageRow components to wrap single elements, I forgot to adjust container components, which relied on this row being created when the first component is dropped.
Also adds a basic test for dropping components in a container component.
Also fixes the children: [] we've been getting in the .yaml files for components where it doesn't make sense, I can separate this change if it's too much.

Looks good, thank you!
The test case covers the original issue, right?

Yep, in a simple way but it does - it would fail without these fixes.

Just noticed there are still some bugs in containers... will add fixes very soon.


Some fixes in the astro config

Removed mode: 'mdx' because it's no longer necessary
Formatted
Moved remark-gfm and remark-smartypants to remarkPlugins
Removed rehype-slug because it's no longer necessary - Astro has it's own implementation (see https://github.com/withastro/astro/pull/3234)

I guess this needs to wait for https://github.com/withastro/astro/pull/3234 to be merged right? Looks like removing remark-slug with the current Astro version breaks the heading links (the little link icons next to headings).
Might be a good idea to mark this PR as a draft until it's safe to merge or split it up to apply the slug changes in a later PR?

@delucis actually, no. If you see the preview, you'll see everything working just fine. That's because that PR only removes extra work but doesn't change any functionality

@delucis it should be fixed!

Yep, looking good now! Thanks for figuring that out.


Cannot find name 'Simplify'.

Hey,
I'm getting this error when trying to build my project. I looked into your source code and it seems like the Simplify type isn't exported and your code references it without an import. How does that work?
I've tried playing around with the tsconfig, using the one you provide here, but I can't get it to work.
I'm mostly just curious as to why it seems to work in other projects :D I've used this package in one of my projects without a problem before and now I've come back after a while to continue working on the project and this error came up. I don't remember this from before, so I'm extra confused.
Best regards,
Luke

Well, this looks totally broken: https://github.com/sam-goodwin/typesafe-dynamodb/blob/main/src/get-item.ts#L33
Looks like an easy fix.

Sorry for the late reply - got buried in my notifications.

I think this should be fixed in v0.2.5 - LMK if it works for you.

Works for me, thanks!


Mistake in documentation

Overview
TL;DR
Is this a mistake in the documentation here?
Extra Detail
Please see the red indications.
Screenshots

How to Contribute

[ ] Comment on this issue if you'd like to work/collaborate on it!
[ ] Fork the repository.
[ ] Use the GitHub Flow to make changes to your fork. This is a refresher course if you're unsure about how to make a change on GitHub.
[ ] Push your changes to your repository.
[ ] Submit a Pull Request

Base Dropdown: github/training-kit
Compare Dropdown: Your fork

Testing Locally
If you'd like to make and test changes locally (and see how they would look if merged), do the following:

In your command line:

Install Git
Install Ruby
[ ] Run script/setup
[ ] Run script/server.

When successful, the script will initiate a local server at http://<IP_ADDRESS>:4000/.

Questions?

Leave a comment on this issue! Make sure to use @mentions if you want a specific person's attention!

I would like to take up this issue. I am participating for Hacktoberfest. Will be more than happy to help.

I'd like to work on this issue for Hacktoberfest, I'll fork the repository and make the change!

Nevermind, looks like the markdown file has already been updated, a new build just needs to be pushed out and then the changes should show up.


resume property for blocked events

Hi,
I'm not in particular need of this since I'm working more with db.js, but just in examining your nicely modular projects, I thought I'd share a novelty I added to db.js for blocked connections that you might find of use.
Within the db.js open request (and the delete one which also has a couple of other browser bug workarounds you may be interested in), you should see a resume property we add to the onblocked error object so that the user can, as per our README open docs, recover from a blocked event with a promise catch followed by a then.

This resume feature is really nice, thank you for sharing!

Sure... If versionchange handlers have already been set up and if they close their own connections, there will be no blocked event, so by using best practice, there shouldn't be too much of a need for this, I think but if one wants to control the behaviors at the point of making the open request, it may come in handy.


Page refresh and re-login after starting server

Looks like I need to refresh the page to see the server "Status" update. But that makes me have to re-login

looking into this

@sitapriyamoorthi i think this is fixed now, can you please try again?

AFAICT this is fixed

Yes! Works now!


Beerwarts, Beer Bank Banker | Errors when using double quotes in custom name

If using a double quote in custom names the part after the first double quote will be removed if editing the name again.
If naming a Beer Bank Banker with a double quote and opening the modal for the Beer Bank Banker's training session afterwards, this results in an undefined label:

What if I call a banker Robert"); DROP TABLE STUDENTS; --?

@2ndK16 nothing. The value just isn't handled properly during HTML templating.

Named trading routes are also affected

Fixed


first version on types

The first and incomplete version of the ADR on types. It will be extended, as we go.

One question: do you think it could be worth considering separate interface files? This would have some of the benefits of annotations in comments, but different pros and cons.

As far as I understand, Leslie's advice is to avoid over-engineering of TLA+ specs. In this sense, we should not produce modules without the need to. (But my understanding may be also wrong.)

As far as I understand, Leslie's advice is to avoid over-engineering of TLA+ specs. In this sense, we should not produce modules without the need to. (But my understanding may be also wrong.)

Just to clarify: I mean a file that was specific to apalache, using whatever syntax we want, that specifies the types in the accompanying .tla file, not a separate file encoded in TLA+. So this would be a bit like .h files or ML.s .mli or mypy's .pyi files, but for Apalache types. One potential additional use here could be (in the future) to add additional directives that are specific to Apalache.

Ah, I see. We will probably have an external file for the inferred types after all. But for the type annotations, it is a bit hard to do. It is easy to refer to CONSTANTS, VARIABLES, and top-level operators. There is also a (tricky) labeling syntax for the expressions inside operators. But in general, it is hard to refer to the names that are declared inside operators.

in general, it is hard to refer to the names that are declared inside operators.

Ah, I see. So, to make it concrete, in a case like
Bar ==
    LET foo == "Three" IN
    foo

Baz(A, B) ==
    LET foo == 3 IN
    foo

There's no great way to annotate the two different occurrences of foo, so we still need an inline syntax for such cases. :+1:

Yes. In theory, we solve this problem by renaming (which is fancily called alpha-conversion in the functional world). But we cannot require the user to only use unique names.

Type annotations as assumptions do not seem to work, as ASSUME over state variables is rejected by SANY.


merge develop

Please do not create a Pull Request without creating an issue first.
What is the purpose of the change
XXXXX
Brief changelog
XX
Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[ ] Run mvn -B clean package apache-rat:check findbugs:findbugs -Dmaven.test.skip=true to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 7 committers have signed the CLA.:white_check_mark: Wuyunfan-BUPT:x: godhth:x: xiebin123456:x: dependabot[bot]:x: luxiao0000:x: shengbinxu:x: juhuanYou have signed the CLA already but the status is still pending? Let us recheck it.


Clean calibre packaging

Description of changes

This PR remove removeReferencesTo since it makes no difference for calibre now, you can check it using nix path-info -S .#calibre.

This PR avoid wrapping PYTHONPATH into program, instead I use python.withPackages and let fixupPhase replace !/usr/bin/env python to the wrapped python automatically.
I'll open another PR to build calibre from git source after 7.13 is released. This change ensure sphinx won't be regarded as a runtime dependency due to PYTHONPATH.

This PR add two args (popplerSupport and speechSupport) for users to override.
In arch linux repo, poppler_utils and speechd are optional dependencies, so I add these options. Another reason is that someone wants the option.

Format the code using nixfmt-rfc-style

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

cc the maintainer: @pSub

Byt the way, I was wondering why we wrap calibre with gappsWrapperArgs while calibre is a qt app.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/1016/151

Please split formatting to another commit.

This PR avoid wrapping PYTHONPATH into program, instead I use python.withPackages and let fixupPhase replace !/usr/bin/env python to the wrapped python automatically.

Just to make sure, it doesn't use python from somewhere else right?

Please split formatting to another commit.

Done.

This PR avoid wrapping PYTHONPATH into program, instead I use python.withPackages and let fixupPhase replace !/usr/bin/env python to the wrapped python automatically.

Just to make sure, it doesn't use python from somewhere else right?

As far as I test, all functions of calibre I use works well after this change.
@Aleksanaa

Your PR will be more likely to be merged if you squash commits.

Your PR will be more likely to be merged if you squash commits.

No need to, they are changes regarding different aspects.


API next json key loops on itself with MAX_PAGE_SIZE=0 and limit=0

Environment

Python version:  3.7
NetBox version:  2.4.4

Steps to Reproduce
Set MAX_PAGE_SIZE=0 to disable the pagination, and do a GET on a list of items (/api/dcim/devices/ for example) with the GET parameter limit=0.

Expected Behavior
The next value in the response should be null, as the pagination is disabled.

Observed Behavior
The next is looping on the same GET query, with limit=0&offset=0 (/api/dcim/devices/?limit=0&offset=0 for example). It is an issue for some API clients that just loop over the next key until it is null.

Thanks a lot!


System.TypeInitializationException: The type initializer for 'OpenCvSharp.Internal.NativeMethods'

Summary of your issue
---> System.DllNotFoundException: Unable to load shared library 'OpenCvSharpExtern' or one of its dependencies. In order to help diagnose loading problems, consider setting the LD_DEBUG environment variable: libOpenCvSharpExtern: cannot open shared object file: No such file or directory
at OpenCvSharp.Internal.NativeMethods.redirectError(CvErrorCallback errCallback, IntPtr userdata, IntPtr& prevUserdata)
at OpenCvSharp.Internal.ExceptionHandler.RegisterExceptionCallback()
at OpenCvSharp.Internal.NativeMethods.LoadLibraries(IEnumerable`1 additionalPaths)
at OpenCvSharp.Internal.NativeMethods..cctor()
Environment
Ubuntu 18.04.6 LTS  i also encounterd the same issue on Mac OS  ,, but there is no issue in Windows system
Example code:
           string imagePath = Environment.GetEnvironmentVariable("HOME") +"/Pictures/Screenshot.png";
            Mat image = Cv2.ImRead(imagePath, ImreadModes.Unchanged);
            DetectSensitiveAreas(image);

the error hits on second line

Having the same issue on an up2date M1 Air. Really annoying since I am trying to port some apps to Avalonia to be multiplatform, and now its an OpenCV issue being a show-stopper...


Сompatibility with Django 1.6 and python 3.4

@RahimovIR do you mind updating your branch and fixing the build errors?


narrate "per_player" don't work as expected

https://one.denizenscript.com/haste/63195
The output of /version on my server is: git-Paper-31 (MC: 1.15.1) (Implementing API version 1.15.1-R0.1-SNAPSHOT)
The output of /version denizen on my server is: version: 1.1.2-SNAPSHOT (build 4504-DEV), core version: 1.60-SNAPSHOT (Build 490)
The issue is:
Player related tags are not parsed depending of the player reading the output of the narrate command even with "per_player" set

Woops.
Fixed.
Thanks!


Speed up dev docs builds by excluding past releases

Description
Fixes #479
Docs builds are taking increasingly long. This PR adds a optional config file which excludes all past releases, allowing users to quickly iterate on master docs in a development environment
Todos

[n/a] Tests
[x] Documentation
[x] Release note

lgtm


Is there any conflict in the provided environment?

Requirements
This implementation is only tested under Ubuntu/CentOS environment with Nvidia GPUs and CUDA installed.
Python >= 3.8
PyTorch >= 1.6
requirements.txt:
numpy==1.18.1
torch==1.6.0
torchvision==0.7.0
tensorflow-gpu==2.3.0
opencv-python==<IP_ADDRESS>
opencv-python-headless==<IP_ADDRESS>
protobuf==3.20.1
tqdm
kornia
pillow
scipy
tensorboard
scikit-image
albumentations
torchsummary
numba
einops
trimesh
face-alignment
ninja
imageio
Is there any confict?

nvdiffrast Installation
Minimum requirements:
Linux or Windows operating system.
64-bit Python 3.6.
PyTorch (recommended) 1.6 or TensorFlow 1.14. TensorFlow 2.x is currently not supported.
A high-end NVIDIA GPU, NVIDIA drivers, CUDA 10.2 toolkit.

pytorch3d
Installation
Requirements
Core library
The core library is written in PyTorch. Several components have underlying implementation in CUDA for improved performance. A subset of these components have CPU implementations in C++/PyTorch. It is advised to use PyTorch3D with GPU support in order to use all the features.
Linux or macOS or Windows
Python 3.8, 3.9 or 3.10
PyTorch 1.10.0, 1.10.1, 1.10.2, 1.11.0, 1.12.0, 1.12.1, 1.13.0, 2.0.0 or 2.0.1.
torchvision that matches the PyTorch installation. You can install them together as explained at pytorch.org to make sure of this.
gcc & g++ ≥ 4.9
fvcore
ioPath
If CUDA is to be used, use a version which is supported by the corresponding pytorch version and at least version 9.2.
If CUDA older than 11.7 is to be used and you are building from source, the CUB library must be available. We recommend version 1.10.0.


Rasa Tutorial includes commands that don't work on Windows

Operating system (windows, osx, ...):
Windows
Issue:
Some code snippets that are shown in the Tutorial (https://rasa.com/docs/rasa/user-guide/rasa-tutorial/) do not work in the Windows command line.
Proposed solution:
Wherever it says cat, e.g. cat data/nlu.md, mention that on Windows you should instead use type.

Closing this because the tutorial will be removed in the new docs anyways


docs: Added database creation on startup to the todo app with SQLAlchemy tutorial

Pull Request Checklist

[x] New code has 100% test coverage
[ ] (If applicable) The prose documentation has been updated to reflect the changes introduced by this PR
[ ] (If applicable) The reference documentation has been updated to reflect the changes introduced by this PR
[x] Pre-Commit Checks were ran and passed
[x] Tests were ran and passed

Description

This PR adds an on_startup function to the tutorial Improving the TODO app with SQLAlchemy  to create database.
This PR also adds apostrophes to for pip install for improved platform independence

Close Issue(s)

Addresses issue #2468.

@all-contributors, add @orgarten for docs

Thank you @orgarten!

Thank you @orgarten!

My pleasure!


[ENH] pivot_longer_spec

PR Description
Please describe the changes proposed in the pull request:

Improve performance when sort_by_appearance is True
Added pivot_longer_spec, which allows unpivoting by hand - this allows more granular control on how the final dataframe should look in long form.
general refactoring

import pandas as pd; import janitor as jn

In [11]: events = pd.DataFrame(
    ...:             {
    ...:                 "country": ["United States", "Russia", "China"],
    ...:                 "vault_2012_f": [
    ...:                     48.132,
    ...:                     46.366,
    ...:                     44.266,
    ...:                 ],
    ...:                 "vault_2012_m": [46.632, 46.866, 48.316],
    ...:                 "vault_2016_f": [
    ...:                     46.866,
    ...:                     45.733,
    ...:                     44.332,
    ...:                 ],
    ...:                 "vault_2016_m": [45.865, 46.033, 45.0],
    ...:                 "floor_2012_f": [45.366, 41.599, 40.833],
    ...:                 "floor_2012_m": [45.266, 45.308, 45.133],
    ...:                 "floor_2016_f": [45.999, 42.032, 42.066],
    ...:                 "floor_2016_m": [43.757, 44.766, 43.799],
    ...:             }
    ...:         )

In [12]: events
Out[12]:
         country  vault_2012_f  vault_2012_m  ...  floor_2012_m  floor_2016_f  floor_2016_m
0  United States        48.132        46.632  ...        45.266        45.999        43.757
1         Russia        46.366        46.866  ...        45.308        42.032        44.766
2          China        44.266        48.316  ...        45.133        42.066        43.799

[3 rows x 9 columns]

events = pd.concat([events]*100_000)

# dev
In [848]: %timeit events.pivot_longer(index='country', names_to=['event','year','gender'], names_sep='_',sort_by_appearance=False)
62.9 ms ± 361 µs per loop (mean ± std. dev. of 7 runs, 10 loops each)

In [849]: %timeit events.pivot_longer(index='country', names_to=['event','year','gender'], names_sep='_',sort_by_appearance=True)
165 ms ± 1.01 ms per loop (mean ± std. dev. of 7 runs, 10 loops each)

# PR
In [842]: %timeit events.pivot_longer(index='country', names_to=['event','year','gender'], names_sep='_',sort_by_appearance=False)
53.2 ms ± 264 µs per loop (mean ± std. dev. of 7 runs, 10 loops each)

In [843]: %timeit events.pivot_longer(index='country', names_to=['event','year','gender'], names_sep='_',sort_by_appearance=True)
48 ms ± 486 µs per loop (mean ± std. dev. of 7 runs, 10 loops each)

Performance test for lots of columns (YMMV):
events = pd.DataFrame(
     ...:             {
     ...:                 "country": ["United States", "Russia", "China"],
     ...:                 "vault_2012_f": [
     ...:                     48.132,
     ...:                     46.366,
     ...:                     44.266,
     ...:                 ],
     ...:                 "vault_2012_m": [46.632, 46.866, 48.316],
     ...:                 "vault_2016_f": [
     ...:                     46.866,
     ...:                     45.733,
     ...:                     44.332,
     ...:                 ],
     ...:                 "vault_2016_m": [45.865, 46.033, 45.0],
     ...:                 "floor_2012_f": [45.366, 41.599, 40.833],
     ...:                 "floor_2012_m": [45.266, 45.308, 45.133],
     ...:                 "floor_2016_f": [45.999, 42.032, 42.066],
     ...:                 "floor_2016_m": [43.757, 44.766, 43.799],
     ...:             }
     ...:         )

events
         country  vault_2012_f  vault_2012_m  vault_2016_f  vault_2016_m  floor_2012_f  floor_2012_m  floor_2016_f  floor_2016_m
0  United States        48.132        46.632        46.866        45.865        45.366        45.266        45.999        43.757
1         Russia        46.366        46.866        45.733        46.033        41.599        45.308        42.032        44.766
2          China        44.266        48.316        44.332        45.000        40.833        45.133        42.066        43.799

events = events.set_index('country')
events = pd.concat([events.add_suffix(f'_{num}') for num in range(100)],axis=1)
events = pd.concat([events]*10_000)
events = events.reset_index()
In [143]: events.shape
Out[143]: (30000, 801)

# dev
In [147]: %timeit events.pivot_longer('country', names_to=['event','year','gender','num'],names_sep='_',values_to='score', names_transform={'year':int}, sort_by_appearance=True)
2.85 s ± 34.4 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)

In [148]: %timeit events.pivot_longer('country', names_to=['event','year','gender','num'],names_sep='_',values_to='score', names_transform={'year':int}, sort_by_appearance=False)
687 ms ± 7.2 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)

# this PR
 In [13]: %timeit events.pivot_longer('country', names_to=['event','year','gender','num'],names_sep='_',values_to='score', names_transform={'
    ...: year':int}, sort_by_appearance=True)
420 ms ± 3.15 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)

In [14]: %timeit events.pivot_longer('country', names_to=['event','year','gender','num'],names_sep='_',values_to='score', names_transform={'
    ...: year':int}, sort_by_appearance=False)
470 ms ± 2.52 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)

This PR resolves #1361 .

PR Checklist

Please ensure that you have done the following:

[x] PR in from a fork off your branch. Do not PR from <your_username>:dev, but rather from <your_username>:<feature-branch_name>.

[x] If you're not on the contributors list, add yourself to AUTHORS.md.

[x] Add a line to CHANGELOG.md under the latest version header (i.e. the one that is "on deck") describing the contribution.

Do use some discretion here; if there are multiple PRs that are related, keep them in a single line.

Automatic checks
There will be automatic checks run on the PR. These include:

Building a preview of the docs on Netlify
Automatically linting the code
Making sure the code is documented
Making sure that all tests are passed
Making sure that code coverage doesn't go down.

Relevant Reviewers

Please tag maintainers to review.

@ericmjl

🚀 Deployed on https://deploy-preview-1362--pyjanitor.netlify.app

i will reopen after other PRs are ok

Ok, I just had a chance to look through the PR. Super high quality work! There was one file that was a tad too long where the implementation happened; I'm going to trust that it works fine. Otherwise, thank you for keeping the code test coverage high, @samukweku!

I am going to approve. Please do the honors of merging!

@ericmjl thanks for the feedback... I have to figure out how to break up such PRs into small chunks


virtual machine detected

when i try that, im getting "virtual machine detect" error, should I any edit on bypass.file?

i know, will fix.
isin acele mi? aceleyse instagram ver

can you try new release? it should work now.

when i try that, im getting "virtual machine detect" error, should I any edit on bypass.file?

can you try new release? it should work now.

ekleyebilir misin? muratef.e

Any way to bypass SEB lite exam tool on windows 11 Ivan VMware on apple silicon Mac


Build fails with  "String types not allowed (at 'slideEdge' with value 'end')."

Tried Gradle 2.2.1 and 2.3 for the same result.
Full transcript of error message:

What went wrong:
Execution failed for task ':app:processReleaseResources'.
com.android.ide.common.internal.LoggedErrorException: Failed to run command:
c:\adt\sdk\build-tools\21.1.2\aapt.exe package -f --no-crunch -I c:\adt\sdk\platforms\android-21\android.jar -M C:\work\androidtv-Leanback-master\app\build\intermediates\manifests\full\release\AndroidManifest.xml -S C:\work\androidtv-Leanback-master\app\build\intermediates\res\release -A C:\work\androidtv-Leanback-master\app\build\intermediates\assets\release -m -J C:\work\androidtv-Leanback-master\app\build\generated\source\r\release -F C:\work\androidtv-Leanback-master\app\build\intermediates\res\resources-release.ap_ --custom-package com.example.android.tvleanback -0 apk --output-text-symbols C:\work\androidtv-Leanback-master\app\build\intermediates\symbols\release
Error Code:
1
Output:
C:\work\androidtv-Leanback-master\app\build\intermediates\res\debug\transition-v22\lb_browse_entrance_transition.xml:23: error: Error: String types not allowed (at 'slideEdge' with value 'end').
C:\work\androidtv-Leanback-master\app\build\intermediates\res\debug\transition-v22\lb_browse_return_transition.xml:18: error: Error: String types not allowed (at 'slideEdge' with value 'start').
C:\work\androidtv-Leanback-master\app\build\intermediates\res\debug\transition-v22\lb_browse_return_transition.xml:27: error: Error: String types not allowed (at 'slideEdge' with value 'end').

Thanks for the report. We're looking into it.
Internal: 19836282

I'm getting the same error. Is there any update on this bug?

I merged in an update for V22.  I wonder if the gradle dependecy Leanback-v17:+ was causing the issue.  It's compiling fine for me on mac.  Can you guys try again?

Thanks, now it works. By the way, is it OK, that I have to correct required Build Tools to currently available 22.0.1, as 22.0.0 is in no way available after ADT update?


sched/signal: Fix compilation errors for MSVC.

Summary
This commit removed the empty struct to fix compilation errors for the MSVC compiler.
Impact
Fixed compilation errors for the MSVC compiler
Testing
Tested with the MSVC compiler.

[Experimental Bot, please feedback here]
No, this PR does not meet the NuttX requirements.
Missing Information:

Summary:

Lacks details about the specific struct removed and its location (file/module).
No explanation of why the empty struct caused compilation errors in MSVC.

Impact:

Needs to be more specific. Which architectures and boards are affected by this MSVC compilation error?
Should explicitly state "NO" for all other impact categories if they don't apply.

Testing:

Provide:

MSVC version used
Target architecture(s) tested on
Relevant snippets of the compilation errors before the change.
Confirmation that the errors are gone after the change.

Recommendations:

Expand the Summary:  Clearly identify what was changed and why.
Specify Impact: Be explicit about affected architectures, boards, and compilers.
Detailed Testing Information:  Include specific details about your testing environment and the errors resolved.


Fixed #15. Reworked threading logic in SortController and allowed all algorithms to be stopped mid-sort

Awesome, everything works as expected, thank you so much for the contribution!


Status requests from unvanquished.net flagged as DRDoS

On my server, I periodically get log lines of this form (from SV_CheckDRDoS):
Possible DRDoS attack to address <IP_ADDRESS>, ignoring getinfo/getstatus connectionless packet

This is the IP of unvanquished.net. I suppose these requests can be coming from either the Wordpress plugin for unvanquished.net/servers, or the master servers.

can you look how often you get getstatus requests and the port?
I get every 10 seconds 2 requests from unvanquished.net per server.
I believe it is coming from mantis https://gitlab.com/Viech/Mantis

I get every 10 seconds 2 requests from unvanquished.net per server.

I get the same pattern.
I can also make an additional request appear by refreshing unvanquished.net/servers.

From Mantis' unvquery.h:
// Minimum query periods for printActiveServers
#define PRINTACTIVESERVERS_LISTPERIOD   120
#define PRINTACTIVESERVERS_STATUSPERIOD 10

// Minimum query periods for checkPeekActivity
#define CHECKPEEKACTIVITY_LISTPERIOD    120
#define CHECKPEEKACTIVITY_STATUSPERIOD  10

First query is probably to build a list of active servers to answer !list commands, second query is the one done to tell users in channel there are players on a server.


Require() doesn't work with CustomJS

Hi - I am trying to use danfojs-node within CustomJS using require as shown below but running into an error. Do you have any suggestions on how to get this working?
callback = CustomJS(args=dict(source=source), code="""
                    const dfd = require("danfojs-node")
                    ... some other code..
                    """)

Error from Chrome Developer tools for require() function

Hello - I have not tried to mix these things up. You have also not tried to stretch the bokeh CustomJS since it may or may not interfere with Angular or/and is even not compatible with require.
require is here the problem: see e.g. https://stackoverflow.com/questions/23603514/javascript-require-function-giving-referenceerror-require-is-not-defined

Yes, require() is a server-side method and won't work on client-side such as browsers. Though it we try browserify, I will look for other alternatives on how to create dynamic charts. Thanks again!


Update README.md

Add From NAND to TETRIS to Computer Architecture

@kashwaa this course already is in our extras section.


Instance: USP Course ; Angele Martins

Cloud Computing Instance Flavor
g3.xl - GPU instance (32 CPUs, 125 GB RAM and A100 GPU)
Description
I am a brazilian professor at Universidade de Brasilia, and I currently work with micro CT images of blindsnakes, threadsnakes and wormsnakes.
ORCID
0000-0002-0193-4011
Email
U2FsdGVkX18wVJ7ciWHxuUHou/t7V4y1VtKYwUN8ViuPuYvwWTA+8siyzp4WxLD3
Confirm Email
U2FsdGVkX18wVJ7ciWHxuUHou/t7V4y1VtKYwUN8ViuPuYvwWTA+8siyzp4WxLD3
Instance Name
instance-122
The instance name is derived from the GitHub issue number using the template instance-NNN. The instance may also be located in the exosphere interface using this name.
Volume Name
My-Data-122
The volume name is derived from the GitHub issue number using the template My-Data-NNN. The volume may also be located in the exosphere interface using this name.

/email

/email

/email

/unshelve

/unshelve


does express support async and await?

dose express support async and await for next function?
this is my code:
const express = require('express');
const app = express();

async function sleep(timeout) {
    return new Promise((resolve) => {
        setTimeout(resolve, timeout);
    });
}

app.use(async (req, res, next) => {
    await sleep(100);
    console.log("router prefix");
    await sleep(100);
    await next();
    await sleep(100);
    console.log("router post");
    await sleep(100);
});

app.use(async (req, res, next) => {
    await sleep(100);
    console.log("log prefix");
    await sleep(100);
    await next();
    await sleep(100);
    console.log("log post");
    await sleep(100);
});

app.get('/', async (req, res) => {
    await sleep(100);
    console.log("process prefix");
    await sleep(100);
    res.send({});
    await sleep(100);
    console.log("process post");
    await sleep(100);
});

app.listen(3000, function () {
    console.log('Example app listening on port 3000!');
});

the output is that:
router prefix
log prefix
router post
process prefix
log post
process post

rather than :
router prefix
log prefix
process prefix
process post
log post
router post

is it a bug, or something wrong with my code?

Your example is how the Koa web framework works. The next() function in Express does not return a promise.

Purely out of interest, what is the reason v5 doesn’t return a promise from ‘next’, are there technical / performance challenges or is it simply a design decision?