ensures cache dir does exist

I ran into a problem when installing another project with flit for development purpose using flit install --pth-file.  The user had a non-existing home directory set (`/nonexistent') and therefore the download of the trove classifiers failed.
The /nonexistent "home" directory is used on POSIX systems to denote a user without a home directory, e.g. user nobody or users only set up for services.
These proposed changes ensures that a valid directory is returned by the flit.validate.get_cache_dir() function.
If the flit-subdirectory of the cache-directory does not exist and could not be created, a temporary directory is used instead. To ensure that always the same temporary directory is used, the function is wrapped with the functors.lru_cache().
A tests for this new behavior is also included. The tests passed so far on Mac OS X (Python 3.7 and 2.7) and on FreeBSD (Python 3.6)

That solves the cleanup problem, but if we create a new 'cache directory' each time the function is used, we're not really caching anything, so we can probably simplify things.

I know that it's not caching anything. But this will only be in effect for (posix) users that don't have a (writable) home directory set, so probably related to some service / daemon.  And also only while using flit to install the project (not if the install is done via pip).
Since I can't think of an posix path that has guaranteed write access for all users, I think not caching in this simple case is acceptable.
Currently an install in such a case fails, so this is an improvement IMHO.
Another possibility would be to introduce and check for a "FLIT_CACHE_DIR" environmental variable (similar to the suggestion in #320). In a case where there is no writable automagical cache path, the flit command could be prefixed like FLIT_CAHCH_DIR=/vatr/tmp/cache flit install --pth-file.

Another possibility would be to move the check for FLIT_NO_NETWORK to the start of the function, so when FLIT_NO_NETWORK is set, the trove classifier check is passed completely.

Sorry to be unclear. I was thinking, if there's nothing being cached anyway, we don't need to bother creating a temporary directory and saving a file to disk - we can just get the data from the network and use it directly. If it's not clear how to do that, I can have a go myself next time I have a bit of spare time to work on it.

Since I had some time this morning, I removed the caching. Should I add the changes to this pull request or if you want to close this I'll open a new one.

But it can still cache when there is a normal home directory, right?
If you're happy with the changes, feel free to push them to this PR. Or if you're not sure, it's fine to make another PR and we can work out what's best.

With the changes I made today (not pushed so far), caches would be created and used as before if it is possible.
After a download of the classifiers an attempt is made to create a cache file for later use, but it doesn't matter if this is successful or not.

Thanks for your patience with me and my changes ;-)

Sure no problem.

I removed the two tests as you proposed. Thanks again for your work and the patience with this pull request :-)

Thanks for your patience with my reviewing. :slightly_smiling_face:

👍


UIAPPS-88 Bring all packages in line

Motivation

As explained in https://github.com/DataDog/apps/pull/88#issuecomment-1006172133, our setup was starting to break. We take a minute and try to get things more consistent

Changes
This almost all infrastructure changes.

We make all examples follow a consistent naming scheme: datadog-app-example-<directory>. This lets us more easily find examples. It also lets us use globs more easily.
We move all formatting/linting to the top-level and only require those scripts at the top-level. This means it's easier to add a new package and still stay in line with what others are doing.
We pull typescript to the top-level. Similar to the formatting/linting changes, we can more consistently develop this way.
We make sure examples all use the same latest version of the SDK. This means changes should keep things up to date as we iterate.
Because there's so many changes here (and they're mostly whitespace changes), I'll make a review for any additional context that I think is useful to know.

Testing

We added a few new scripts to test that we are actually inline with the package changes: naming, versions, etc.

Releases

Choose one:

[ ] No release is necessary.
If you're only updating examples/documentation, this is likely what you want.
[x] All packages that need a release have a changeset.

📦 Published PR as canary version: Canary Versions

:sparkles: Test out this PR locally via:
npm install<EMAIL_ADDRESS>npm install<EMAIL_ADDRESS>npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>yarn add<EMAIL_ADDRESS>yarn add<EMAIL_ADDRESS>

Thanks for the reviews!

Awe geez, I said I was going to make a contextual review, made a bunch of comments and didn't submit it. I'm sorry about that.


Docs Storage link is rutning 404

following docs link is not working
http://ionicframework.com/docs/v2/api/platform/storage

Storage has been removed from the core of the framework.

Then, docs should not return broken link, when I search docs for storage keyword


laggy feed

my email:
Hello,
I wanted to thank you for sharing h264-live-player. I have just started playing with a camera I got for my remote controlled raspberry-pi car - my weekend toy project.
Running node server-rpi.js got me going but I was wondering if you have some example implementations that are more robust. server-rpi.js crashes quite frequently, I think it sometimes leaves raspivid spawned process hanging.
Once the server is more stable I would want to stop serving the client code from the pi and integrate it with my client application (I use Ember). Any hints on how to do that?
best regards,
Andrzej

answer:
The whole server-*.js stuffs are mostly dummy implementation of what the client side decoder is able to do.
A sample integration with a buffered payload might look like (raw extract for another project)
    var separator = new Buffer([0,0,0,1]);
    var stack = [];

    this.stream   = this.stream.pipe(new Splitter(separator));
    this.ws_path = /wslivefeed";
    console.log("Register %s as ws path", this.ws_path);
    this.ws = new this.WebstreamServer({ server: this.server, path : this.ws_path, perMessageDeflate : false});

    // ws on error
    this.ws.on('error', (err) => {
      this.log.error("ERROR on ws" , err);
    });

    // ws on connection
    this.ws.on('connection',  (client) => {
      console.log("NEW WS CLIENT FOR feed ", this.ws_path);
      var width = 960, height = 540;
      client.send(JSON.stringify({action : "init", width: width, height : height}));

      var stackInterval = setInterval(() => {
        if(!stack.length)
          return;

        if (stack.length > 50) {
          console.log("Dropping Frames!");
          stack = [];
          return;
        }

        if(client.busy)
          return;

        var data = stack.shift();

        client.busy = true;

        client.send( Buffer.concat([separator, data]), {binary: true}, () => {
          client.busy = false;
        });
      }, 20); //never be below 25 fps

      client.on("close", function(){
        console.log("Cleanup ws stream");
        clearInterval(stackInterval);
      });
    });

    var input = 0;
    // stream on data
    this.stream.on('data', (data) => {
        input ++;
        stack.push(data);
    });

    var inputInterval = setInterval(function(){
      console.log("Input flow is %d, stack is %d len", input, stack.length);
      input = 0;
    }, 1000);

    this.stream.on('end', function(){
      clearInterval(inputInterval);
    });


wip: card expandable

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Input Group] Input group is overflowing parent column in flex mode

Foundation 6.2.4
This is a vanilla custom download with flex-mode and forms:
http://simshaun-static.s3-website-us-east-1.amazonaws.com/foundation/6.2.4/
I'm seeing the input-group overflow its parent column in both Win 10 Firefox & Win 10 Chrome. The issue is even more pronounced
It has something to do with row collapsing. Taking the collapse class of the parent .row makes the problem go away.

Edit:
This may just be a problem with the demo page not including the columns class on the .row.collapse element. Adding it solves the issue. In fact, it doesn't seem that collapse is doing anything then...

@simshaun do you know if this was corrected in later versions? Thanks.

The issue appears to have been fixed. http://simshaun-static.s3-website-us-east-1.amazonaws.com/foundation/6.4.2/

Thank you!


disable faulty host annoucne test

I would lol if that build failed

I was actually pretty close to disabling the wrong test lol


SRS - Scope

Needs to be rewritten to be both comprehensive but not too detailed. This section is an executive summary.

This is done and ready for review.


v8: Support scalar globals

Needed for LV_LAYOUT_*, LV_STYLE_*.
See https://github.com/lvgl/lvgl/issues/1763#issuecomment-816937927

Fixed by 7f8640b


Nx_web_http_server_secure_configure() improper remote certificate list management

When there is more than one remote certificate being allocated, nx_web_http_server_secure_configure() attempts to re-add the same certificate to remote certificates list, because certificates are being indexed by session index instead of certificate index.  This problem went away when the following change was made to nx_tcpserver.c, line 533:
            //status = nx_secure_tls_remote_certificate_allocate(tls_session, remote_certificates[i],
            status = nx_secure_tls_remote_certificate_allocate(tls_session, remote_certificates[cert_count],

@leobbditestcom Thanks for reporting this issue, we will fix it in the next release.

@leobbditestcom closing, the bug fix is released in 6.1.12 now.


🐛 [Nextcloud] Addon option data_directory: is not working

Description
When you add the option data_directory: to the addon option it does not change the data directory at startup.
The data directory are always the path that you have add at the installation.
Reproduction steps
I have installed Nextcloud with the standart data folder `/share/nextcoud`
After i have add a networkdisk in the addon option and add `data_directory:` with the path to the option.
At startup you see in the logs that the network disk is mountet. But it will always take the old data_directory path.

Addon Options

Full_Text_Search: false
OCR: false
OCRLANG: deu
PGID: 1000
PUID: 1000
additional_apps: inotify-tools
certfile: fullchain.pem
elasticsearch_server: <ip:port>
keyfile: privkey.pem
trusted_domains: xxxx
use_own_certs: false
data_directory: /mnt/home
cifspassword: xxxxx
cifsusername: xxxxx
networkdisks: //<IP_ADDRESS>/home

### Addon Logs

```bash
[09:48:37] INFO: ... //<IP_ADDRESS>/home successfully mounted to /mnt/home with options ,uid=1000,gid=1000,iocharset=utf8

Architecture
No response
OS
HAos

Hi, indeed it is by design : once installed, the data locations are yard coded in the database. Nextcloud does not support changing the data path as I understand it. What this option does is ensure adequate permissions with the data folder uses for installation, and prefill (hopefully) the default data folder during installation template

Hello.
Thank you for the quick reply.
Ahh I understand. This is only for the first setup.
Maybe a small note by the option would be good.
Theoretically you can change the data_directory if you have access to the config.php

Honestly I've done it myself and it was a nightmare :) I had to manually edit my sql tables to correct all entries and reminded files. Well it IS possible by using a tool like portainer just not recommended :)
Thanks i'll add a note to the readme

Ok thanks for the note in the readme.
Yes I have now deleted everything again and started from the beginning.
Thanks for your support.


Update to remove exception for codeaction at end of line.

Fixes #296
Based on the following snippet in Roslyn (CodeFixContext.cs).
/// All the diagnostics must have the same <paramref name="span"/>.

Best of both worlds now. If you have a precise span, it will only match exactly. If you only have a point-wise location within a span, then it searches for the first match and returns all other diagnostics matching said span.

Checked in VS Code and the exception is now gone.

@troydai  @DustinCampbell any input, otherwise looks good to me

Applied feed-back.

I think this is good to go, I haven't tested it in an editor yet, anyone else have any opinions?  @DustinCampbell @troydai

looks good to me, too.

Thanks again @hal-ler !


Cube v6 support

This PR starts work on version 3 in which oxidicom sends PACSSeries registration requests to CUBE via celery tasks. CUBE support for PACSSerires registration via celery is implemented in https://github.com/FNNDSC/ChRIS_ultron_backEnd/pull/572
oxidicom no longer connects to the database directly.
Decoupling is improved, and miniChRIS-docker is no longer used for development nor testing.

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:

TODO

[ ] Figure out why test is flaky in GitHub Actions. Sometimes, not all NATS messages are received.
[ ] Illegal value for tag error is not being sent through NATS. It should be.
[ ] Fix the error No tasks were received for the series.


Koa error

I get this error when using with Koa.
Error: ENOENT: no such file or directory, open 'D:\web\ai_ledger\views\index.ejs.html'
I'm guessing it's because I'm using @koa/router instead of koa-router which is not supported anymore.

Hi @dan335
It looks like it is not related to the router version.
For some reason, this line is not working.
Check the reason for that (maybe you are using bundler for the node part?)
Anyway, you can provide options.uiBasePath by yourself, it shoud get the path to the node_modaules/@bull-board/ui folder.

Still can't get this to work.  See anything wrong?  The output of console.log(uiBasePath) is the correct path.
const serverAdapter = new KoaAdapter();

serverAdapter.setBasePath('/admin/queues');

const uiBasePath = join(__dirname, '../', 'node_modules', '@bull-board', 'ui');

console.log(uiBasePath)

createBullBoard({
  queues: [
    new BullMQAdapter(queueUpdateTransactionCategory),
    new BullMQAdapter(queueTrainModel),
    new BullMQAdapter(queueSyncTransactions),
  ],
  serverAdapter,
  options: { uiBasePath }
});

await app.use(serverAdapter.registerPlugin());

This is weird, can you debug it, maybe it is related to the fact that you are using windows.

Any update?

Going to do a bit of necromancy here, but at work we use the Koa library to write our web server and I've been wanting to use the @bull-board/koa middleware, but without luck. I'm getting the same error as he is but I think I'm one step further. I actually get the HTML page but it's not loading the static assets.
I made an attempt to use the library on a clean project and it works right off the bat, so my question is, would there be some kind of issue if I bound a bunch of routers and middlewares and then bound that bullboard plugin at /bullmq for example?

For sure you can add any middleware before the mount of bull-board (check the auth with koa example)
You should debug the adapter (probably something is interfering with the setup)

For sure you can add any middleware before the mount of bull-board (check the auth with koa example)
You should debug the adapter (probably something is interfering with the setup)

Interesting, already started toying around but what do you mean by debugging the adapter. With the actual debugger or you mean there are some kind of debug logs that get dumped somewhere?

No logs, you can modify the code (print to console paths)
Actually there is only one route that handles static files...check it

This seems reasonable no? I replaced some parts of the path but the actual path printed to my terminal is right, it leads me to the right place with the static files.
KoaAdapter {
  basePath: '/ui',
  uiConfig: {
    boardTitle: 'Bull Dashboard',
    favIcon: {
      default: 'static/images/logo.svg',
      alternative: 'static/favicon-32x32.png'
    }
  },
  viewPath: '<path-to-project>/<root-dir>/node_modules/@bull-board/ui/dist',
  statics: {
    route: '/static',
    path: '<path-to-project>/<root-dir>/node_modules/@bull-board/ui/dist/static'
  },
  entryRoute: {
    method: 'get',
    route: [ '/', '/queue/:queueName', '/queue/:queueName/:jobId' ],
  }
}

Did you set the basePath of the adapter (what is the value of the base tag in the returned HTML?)

Did you set the basePath of the adapter (what is the value of the base tag in the returned HTML?)

Modified my previous comment with some more details.

What is the path of the 404 request of static flies that fails?

What is the path of the 404 request of static flies that fails?

For example: http://localhost:8000/ui/static/js/lib-router.73947a57.js with 404.

Ur client side paths looks OK
Try to remove the uiBasePath (it should resolve automatically)

Ur client side paths looks OK Try to remove the uiBasePath (it should resolve automatically)

Same behaviour, unfortunately.

Side question, can we .use from a Router instance from the koa-router package?

I'll be able debug it with you tomorrow, ping me here?

I'll be able debug it with you tomorrow, ping me here?

Alright.

I'm available in Discord, my nick isfelixmosh

Very helpful, added.


Codesigning RP: adding first 2024-02-05 public preview version

ARM (Control Plane) API Specification Update Pull Request

[!TIP]
Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

[!NOTE]
As of January 2024 there is no PR assignee. This is expected. See https://aka.ms/azsdk/pr-arm-review.

PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

 Click here to see the details of Step 1
Breaking changes review (Diagram Step 1)
If the automation determines you have breaking changes, i.e. Step 1 from the diagram applies to you,
you must follow the breaking changes process.
IMPORTANT This applies even if:

The tool fails while it shouldn't, e.g. due to runtime exception, or incorrect detection of breaking changes.
You believe there is no need for you to request breaking change approval, for any reason.
Such claims must be reviewed, and the process is the same.

 Click here to see the details of Step 2
ARM API changes review (Diagram Step 2)

For help with Step 2 / "ARM review", see https://aka.ms/azsdk/pr-arm-review.

 Click here to see the diagram footnotes
Diagram footnotes
[1] See ARM review queue (for PR merge queues, see [2]).
[2] public repo merge queue, private repo merge queue (for ARM review queue, [1])
The ARM reviewer on-call engineer visits the merge queue twice a day, so the approximate ETA for merges is 12 - 24 hours.

Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!

[X] New resource provider.
[ ] New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been generated using OpenAPI Hub).
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix OpenAPI spec quality issues in S360.
[ ] Other, please clarify:

edit this with your clarification

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[X] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[X] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

 Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
For help with PR workflow diagram Step 2 (ARM review), see https://aka.ms/azsdk/pr-arm-review.
If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

Couldn’t merge PRs in OpenAPIHub, so generated this PR based on the below two private repo PRs.
https://github.com/Azure/azure-rest-api-specs-pr/pull/17068
https://github.com/Azure/azure-rest-api-specs-pr/pull/16461

Please check and fix the errors: https://github.com/Azure/azure-rest-api-specs/pull/27888/checks?check_run_id=21895395872

Please check and fix the errors: https://github.com/Azure/azure-rest-api-specs/pull/27888/checks?check_run_id=21895395872

We have already designed with this and rolled out to private preview. We are due for public preview and cant afford these changes now.
Also for sku.name we have seen many RPs implemented this way and we have done similarly.

@mikekistler is the LintDiff failure a regression? If so, mayhap it is caused by this?

https://github.com/Azure/azure-openapi-validator/pull/661

From this Teams chat:

False Positive Report for PatchBodyParametersSchema
In PR 27888, properties is the only one property in the body of PATCH. In this case, shall we allow this property to be labeled as required?
Konrad Jamrozik
CC Roopesh Manda

@konrad-jamrozik Yes that is a regression. The check for "required" should only be at the top level. The check for "default" needs to be nested. Please open an issue and assign it to me.

@konrad-jamrozik Actually this is not straight-forward. We should discuss.

/azp run


Support for asyncio

At the moment, duckdb-engine only supports non-async I/O. Could you add async driver as well? I think it's gonna touch lots of code but it would boost  performance a lot

Given DuckDB itself isn't Async, this probably isn't a worthwhile exercise.
I'd recommend looking at the async support in sqlalchemy itself instead: https://docs.sqlalchemy.org/en/20/orm/extensions/asyncio.html


Deprecate use of KafkaConsumer#committed by locally cached committed offset

fixed #16
By deprecating use of KafkaConsumer#committed, the issue is likely fixed but I guarded offsetCommit aginst TimeoutException as well to avoid future repeat of the same situation.
3rd commit contains completely unrelated change that I found when looking at some code.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Code unreachable in nested inheritance

Environment data

Language Server version: 2022.10.31
OS and version: Ubuntu 22.04.1 (WSL)
Python version: 3.10.7

Code Snippet
class TestParent():
    def __init__(self):
        print("test")

    def GetValNested(self):

        return self._getValue()

    def _getValue(self):
        raise Exception()

    def GetVal(self):
        raise Exception()

class TestChild(TestParent):

    def _getValue(self):
        return 10

    def GetVal(self):
        return 20

testvar = TestChild()
#Uses TestChild GetVal
testvar.GetVal()

#Pylance uses TestParent _getValue which returns noReturn
testvar.GetValNested()
#Code unreachable
print("Hello")

Expected behavior
All code should be reachable, since _getValue of TestChild is called and no Exception is thrown.
Actual behavior
Everything after testvar.GetValNested() is shown as unreachable, since pylance resolves self._getValue() inside this function to be calling the _getValue function of TestParent instead of TestChild.
Logs
test
Hello

This behavior is expected given the way you've written the code.
There are several ways you can fix this:

Indicate that the TestParent class is an abstract base class (i.e. it derives from abc.ABC) and mark _getValue as an @abstractmethod. This is the recommended way to write an abstract base class. This not only documents the fact that it's abstract (and must be overridden), but it helps tools like pylance warn you if you attempt to instantiate the base class without implementing the required method overrides.
Instead of raising Exception(), raise a `NotImplementedError(). This is the standard way of implementing a method that must be overwritten.
Provide a return type annotation for _getValue, as in def _getValue(self) -> int:.
Provide a return type annotation for GetValNested, as in def GetValNested(self) -> int:.

Ideally, you would do all of the above, but any one of them is sufficient to tell the static code analyzer in pylance that the intent of the code is not to always raise an exception along that code path.

Thanks for the answer.
I understand that there are several workarounds for the problem but it originates from a library I am using. The reason why I opened this issue is that in my oppinion it is inconsistent that getVal() correctly analyzed while GetValNested() isn't.

You'll need to work with the maintainer of the library to incorporate a fix if you want the library to work with static type analyzers like the one used in pylance.


Xcode build script sources user environment

Provides for user-specific nvm/ndenv installs (which should live in ~/.bashrc), although we still auto-detect both nvm and ndenv should they be installed in standard locations in order to support non-Bash shells.
Also added node_modules/.bin to $PATH to fix "react-native: command not found" errors.
If there's no objection, mind if I move nvm and ndenv detection into a conditional for only non-Bash shells? This will preserve current behavior, but give Bash users a bit more flexibility.

This seems sensible, though my knowledge of both shell scripting and the build scripts are both very limited.

On Jan 4, 2016, at 20:05 , Louis Pilfold<EMAIL_ADDRESS>wrote:

This seems sensible, though my knowledge of both shell scripting and the build scripts are both very limited.

Many moons ago I was a Unix sysadmin, which means that dark and arcane lore of the shell was burned into my mind. :)
Would love to know that a few people other than myself ran the build script and everything looked good before it goes into master, though.

Hey @matadon, thanks for the PR! But what problem are we actually fixing here? Non-standard nvn/ndenv setups? Could you please explain a little bit what it means?

I ran into a bunch of problems whereby react-native (0.17.0) would throw out "react-native: command not found" and "node: command not found" errors unless the PATH was specifically hacked into the Xcode build script, which appears to run as a non-login shell (xcode 7.2 on osx 10.11.2).
Failed with fresh installs of node (4.2.4), either directly, or via nvm, which was a frustrating out-of-the-box experience. Figured that allowing the user to specify their build environment via .bashrc would be a workable solution, and might dovetail into doing builds with shenzhen, but I am totally open to a better way to do this.

Hey @matadon! Thanks for making the pull request, but we are closing it due to inactivity (75 days with no activity) to make sure all pull requests are either being worked on or closed. If you want to get your proposed changes merged, please rebase your branch with master and send a new pull request :)
Based on:

Figured that allowing the user to specify their build environment via .bashrc would be a workable solution, and might dovetail into doing builds with shenzhen, but I am totally open to a better way to do this.


No Mean and STD used

Hi, I noticed that the code only normalizes the input image to 0-1 range during the forward function in net_desc.py
Is there are the reason why a Mean and STD is not used?
img = ((img - self.MEAN[None, None, :]) / self.STD[None, None, :])

Hi @geetankr ,
There is no specific reason for not standardising the input in the way that you described. This was just did this for simplicity. You are welcome to try standardising the input to see if there are any noticeable differences in the results. I suspect that the difference would be negligible.


FEATURE: Make the Navbar look more attractive.

Hello, this is Vibhu Patel,
I hope you're doing well. I'm interested in improving our website's functionality.
We can make the navigation bar look more attractive, using vibrant colors, adding hover effects, using stylish fonts.
I am eager to contribute under GSSoC'24 and help enhance our website’s functionality and user experience. Please assign this task to me.
Thank you!

@Vibhu315
Thank you for raising this issue but now it has placed inside menu. If you have any additional issues, feel free to reach out. To keep our issue tracker organized, I will be closing this issue.


Fix MIG/RC terminology usage

@ewiseblatt
I'm going to enable this test in the nightly builds next.

I'll let you do another PR to add the test since there are probably others you'd add as well.


Geteway Regional URIs information was added to the ApiManagementServi…

…ceResource
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[ +] The title of the PR is clear and informative.
+[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[+ ] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[+ ] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[+ ] I have read the contribution guidelines.
[+ ] My spec meets the review criteria:

[+ ] The spec conforms to the Swagger 2.0 specification.
[+ ] The spec follows the guidelines described in the Swagger checklist document.
[+ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

LGTM, but including the new property in the examples would look even better :D

@mcardosos Done :)

No modification for AutorestCI/azure-sdk-for-ruby

No modification for AutorestCI/azure-sdk-for-ruby

No modification for AutorestCI/azure-sdk-for-node

No modification for AutorestCI/azure-sdk-for-python


Postcode component

Hello!
The address components are super handy, would it be possible to add a vs-postcode directive?
Thanks for the awesome module!

Hello!
Yes, addition of vs-postcode directive is possible, but not all google addresses contain information about postal code.
Thanks for your feedback!

+1, and postal code could be set to '' if no info is available. Thanks !

Useful for addresse witch contain postal code PR #6

+1


Way to select certain fields from related tables for prisma2

Hello *,
if I query a table together with a related table, how can I select only certain fields of that related table?
const productsResult = await pt.products.findOne({
where: {
product_id: id
},
include:{
product_variants: true
}
});

In this case, I just want to have the "SKU" field of the "product_variants" table and the "name" field of "products".
Is that possible at all?
Thank's for answering!

Yes, that behavior is documented here: https://github.com/prisma/prisma2/blob/master/docs/relations.md#nested-reads-eager-loading
Does that answer your question?

Thank's for your support!
Unfortunately not.
Setting a field selection leads to the following error message:
const productsResult = await pt.products.findOne({       where: {         product_id: id       },       select: {         name: true       },       include:{         product_variants: true,       }     });
Property 'name' does not exist on type '"Please either choose select or include"'.
But I want to select certain fields of products and/or product_variants to

@P4trik Can you please create a small reproduction with your schema file and the steps to reach this error?

@P4trik
You can achieve result using the following code:
const users = await pt.products.findOne({
	where: {
	  product_id: id
	},
    include: {
      product_variants: {
        select: {
          id: true,
          name: true, // or any other field you want from the relation
        },
      },
    },
  })

Feel free to close this if this solves your issue, otherwise please share your schema.

@pantharshit00 Thats exactly what I'm looking for but unfortunately I receive that error:

Can you please share your datamodel? Looks like I assumed the type of the product_variants incorrectly.

`model products {
product_id    Int    @id
name String
description String?
product_variants product_variants[]
}
model product_variants {
product_variants_id Int @id
sku String?
product products @map(name: "product_id")
category categories?
descriptions String?
}
`

Reproduction: https://github.com/harshit-test-org/prisma-prisma2-653
Ok, the following query works in JS:
const users = await photon.products.findOne({
    where: {
      product_id: 1,
    },
    include: {
      product_variants: {
        select: {
          sku: true,
          descriptions: true,
        },
      },
    },
  })

Returns the following result:

But the code itself is throwing type errors in TypeScript:

That means the reported problem is type generation issue rather than a runtime issue.
So for now, while we fix the typings, you can add a ts-ignore to get rid of type warning temporarily:
  const data = await photon.products.findOne({
    where: {
      product_id: 1,
    },
    include: {
      product_variants: {
        //@ts-ignore
        select: {
          sku: true,
          descriptions: true,
        },
      },
    },
  })


Problematic version requirement update in 0.12.2

The update of 0.12.1 to 0.12.2 changed the sdl2-sys requirement from 0.7 to 0.8.
This is problematic because now crates like sdl2_image or sdl2_ttf break because they specify requirements like "sdl2 0.12" and "sdl2-sys 0.7" which leads to conflicts, and having to downgrade to =0.12.1 explicitly, which is not the intent of semver.
Updating a version dependency on a crate that can only be linked in once should be considered an incompatible change, and therefore lead to a new minor (or, when >1.0.0, major) version.
I guess that if you want to fix this, you'll have to yank 0.12.2, and republish it as 0.13.

Argh, sorry about that, I'll sort that out now

Thanks!

Published 0.13.0


ITAD updated and borked enhanced GOG

Enhanced GOG shows error message on gog games storepages:
Woops. Enhanced GOG encountered an error. Try another region or click here to try again.

So it's finally happened. Time to review the new API changes. Thanks for the headsup.

Their API docs seem to be in flux right now. The only endpoints I see are v01 versions, and they are returning the .deprecated flag: https://itad.docs.apiary.io
I'm also not able to authorize enhanged-gog on the ITAD website at all. I'll have to look more closely, but seems like they're behind in setting up docs for the new API.

Bundles endpoint is also totally borked and not returning the specification: https://itad.docs.apiary.io/#reference/game/bundles/get-info-about-where-the-game-was-bundled?console=1

They are at the starting point of migration yet, you might go back into the hibernation :)
https://steamcommunity.com/groups/isthereanydeal/announcements/listing

Thanks; I was trying to find a place to keep up to date with the changes.
In the meantime, I've found out I can ignore the .active flag when grabbing the game ID as a temporary fix, since the old endpoint is still live. This will probably break soon as well, so I'll keep this issue open. The bundle endpoint is busted so will show 0 at all times at the moment.

Woohoo, new API is detailed here: https://docs.isthereanydeal.com
I'll get to work on fixing the userscript this week.

Hey all, I just pushed up version 1.5.0 which should fix these issues. Please open a new ticket if you encounter any problems.


Stamp float right?

Ive tried adding a 'float' and a 'right' to the stamps/cornerstamp div class but it seems to get over written with a 'left:0;' style.
is there a way to float a stamp on the right hand side?

This I'm not sure about.. Do you have som example code? :-)

Thanks for the response :)
ok so i set the stamp in the masonry options using:
stamp: '.featured-contributors'
which points to the div:

 This is my stamp

*Generally this should be the first div within in your masonry container i believe.
My less styles are as so - setting the stamp to sit on the right:
.featured-contributors{
width: 240px;
height: 365px;
background-color: #ffffff;
border: 1px #d2d2d2 solid;
margin: 10px;
border-radius: 10px;
right: 0;
}
.. but when the page loads the 'right:0' is getting over written with a 'left:0'.
This is the browser code after render:
 This is my stamp
So that left property must be getting set somewhere, but there arent any style sheets to edit so thats why im hoping you can help :)


Backwards compatibility sub-project to old api

New sub-project to bridge Apache Commons Configuration
New sub-project to provide backwards compatibility support for the legacy API

archaius-pull-requests #130 FAILURE
Looks like there's a problem with this pull request


Fix for 8

Fixes #31022
Code fixed in this PR which adds app.UseAntiforgery();

Internal previews

📄 File
🔗 Preview link

aspnetcore/security/anti-request-forgery.md
Prevent Cross-Site Request Forgery (XSRF/CSRF) attacks in ASP.NET Core

@jeffpapp outstanding work. I'm so sorry I missed that change. My sample test code worked when I first published this. It failed today when I ran it. I fixed the code and this PR fixes the article.
Public review  of the doc build:

download the HTML files
unzip
view HTML file in a browser.
For links outside the doc, remove the review. from URL.

@jeffpapp  please review.

@jeffpapp please review.

Yep, that is looking better.  It was just confusing to have the commented code in the old docs that said the middleware should be added but wasn't getting added.


fix issue #7 -  accounts have insufficient funds

Problem,
refund_user.ts does not work. as state in #7
Solution:
The cause is that missing authority.json in folder and also does not run yarn install. Fix by adding these 2 steps.

run buildkite pass.  @KirillLykov
log-file
mango_bencher-dos-log/247


feature(Consents): Store unset consents when term or person is created

Changes the way unset consents work. Stores the unset consents after a conversation with François wanting to see them in the admin view.
Fixes https://github.com/carpentries/amy/issues/1877

@pbanaszkiewicz once this is merged plus https://github.com/carpentries/amy/pull/1862 It should be fine to deploy the consents features so that folks can see it.

@pbanaszkiewicz since we are now storing unset consents, I'm realizing we will have quite a few consents since each time consents change they are stored in the database. I'm assuming we're fine on space here, but if not, I did just realize that Django Admin has a default change history feature that I can explore. Let me know if space is an issue I should be worry about and I can change how the change history is stored.

@pbanaszkiewicz once this is merged plus #1862 It should be fine to deploy the consents features so that folks can see it.

So I should use CONSENTS=1 envvar?

@pbanaszkiewicz since we are now storing unset consents, I'm realizing we will have quite a few consents since each time consents change they are stored in the database. I'm assuming we're fine on space here, but if not, I did just realize that Django Admin has a default change history feature that I can explore. Let me know if space is an issue there.

Space is not an issue. :)

@pbanaszkiewicz CONSENTS=1 should work great. Thanks!


short read star align rule (3a) doesn't obey thread # assigned by config file

8 cores were designated in the config file, but when rule 3a started running, it did so using 24 cores.
snakefiles.zip

Could you share what you ran from the command line to launch the pipeline, and the log output by snakemake? And are you running the pipeline locally or with slurm? Thanks!
And just to clarify, I assume you mean rule ilmn_3a_STARsolo_firstPass?

Of course! I am now realizing what -j 56 is instructing... but yes run locally using the example command line from the readme.md.
snakemake -k -p --use-conda --conda-frontend mamba -j 56
And yes, rule ilmn_3a_STARsolo_firstPass.

Can you check what version of snakemake you are using? If you are using v8, as specified in slide_snake/envs/slsn.yml, then it is likely using the "default" snakemake profile when run locally. You can specify resource usage for each rule in slide_snake/profiles/default/config.yaml
So you should be able to just change the value for "  ilmn_3a_STARsolo_firstPass" under the "set-threads" section (line 19 in the current version) to whatever best suits your needs.
The threads: config["CORES"] is a leftover from older versions of snakemake, before profiles were introduced.

snakemake v8.16.0 per slide_snake/envs/slsn.yml
Thanks! I can confirm that the value for ilmn_3a_STARsolo_firstpass is 24 in slide_snake/profiles/default/config.yaml, and will update these accordingly next time.
If run with slurm, will the same thing happen with slide_snake/profiles/slurm/config.yaml?

Yes! Be sure to update the values in that config file to your setup (slurm_partition and slurm_account) before running, or you will get an error.


Update THIRD-PARTY file for Data Prepper 2.1.0

Update THIRD-PARTY file.

https://github.com/opensearch-project/data-prepper/pull/2201


websocket handshake error crash vue-cli

Version
4.5.9
Reproduction link
https://github.com/yandixuan/cli-crash
Environment info
 Node: 14.15.1 - C:\node-v14.15.1-win-x64\node.EXE
 Yarn: 1.22.5 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
 npm: 6.14.8 - C:\node-v14.15.1-win-x64\npm.CMD

Steps to reproduce
clone the demo which is just created by official cli (i only added code in App.vue and also i added proxy config in vue.config.js)
the cli crashed when websocket handshake error return 200 or 301
What is expected?
cli service does't crash
What is actually happening?
exit when it occurs error

then i changed node version to v8.9.4 it's ok,the cli service never crash when connection failed

hi, i got the same error, how did you solved？@yandixuan


GraphEdit's minimap can be resized to be wider than the view.

Godot version: master (62e134a) and 3.x (f50c806)
OS/device including version: not graphics-related
Issue description: The minimap of GraphEdit can be resized to be wider than the view, and could not be resized back because the resize handle on the top left corner of the minimap is outside the view.
Steps to reproduce:

Create a VisualScript or create an AnimationTree node and create an AnimationNodeBlendTree as root.
Drag the handle on minimap to the very top left corner of the screen.

Minimal reproduction project: Not project specific, create an empty VisualScript is faster.

Reproducible:

I'm investigated on this issue.
I think we should also resize the minimap when setting the graphEdit is resized to a smaller size than minimap.

Yes, I was aware of this when I implemented it. However, logic here is that user has to do this on purpose, and at a reasonable size this does not happen and cause discomfort. And if you resize the editor itself to be smaller than the minimap, you can likely extend it back to a normal size and make minimap smaller beforehand.
In other words, I don't see a reasonable limit that we can implement, and it's up to the user.

OK, resizing the minimap when GraphEdit resized is not so important. And could even be annoying when we just resizing the editor inspector or tree panel for a short time (we need to re-enlarge the minimap after that...)
On the other hand, I think that preventing resizing the minimap larger than the graphedit need a fix.
In some case, there isn't any way to drag the grabber to resize minimap (when all other tabs are allready at mininum size).

Sure, we can prevent it a bit. But even if you stop the size at the GraphEdit size user can still resize the GraphEdit after that to be smaller than the minimap, producing the same state. Which is why I deemed this unimportant initially. But I guess you can prevent weird accidents this way at least.

As you said, if the user set a smaller graphEdit manually, he can still set it back larger by hand. (You convince me that my proposal was useless).
That's not always the case after changing minimap size. User can be stuck because he can't enlarge the graphedit enough.


CMake support

This PR adds CMake build support for The Forge libraries (OS and Renderer), unit tests, and the AssetPipelineCmd utility (desktop platforms only).
This has been tested on:

Arch Linux (6.10 kernel, g++ 14, and clang++ 18)
Windows 11 (MSVC 2019)
macOS 14.5 (Xcode 15.4 / clang++ 15)
Android (NDK 26.1.10909125)
iOS (Xcode 15.4 / clang++ 15)

NOTE: This PR contains no source code changes. A couple of directories have been renamed to fix typos and improve consistency:

Examples_3/Unit_Tests/macOS Xcode/14_WaveIntrinsincs/ renamed to Examples_3/Unit_Tests/macOS Xcode/14_WaveIntrinsics/
Examples_3/Unit_Tests/macOS Xcode/19_CodeHotReload_Main/ renamed to Examples_3/Unit_Tests/macOS Xcode/19_CodeHotReload/

Important information:

Unit tests and AssetPipelineCmd builds can be disabled by setting CMake variables BUILD_UNIT_TESTS and BUILD_ASSETPIPELINECMD to OFF (default is ON).
The CMake implementation has been checked with cmake-lint and cmake-format tools from cmakelang.
Specific builds have been created for the following libraries: OS, Renderer, ozz_base, ozz_animation, ozz_animation_offline, gainput, SpirVTools, ispc_texcomp, and Buny, along with their dependencies.
Shaders are automatically processed with FSL and redeployed when any changes are made to .fsl files.
cmake/TheForgeUtils.cmake provides new functions that make it easy to add new unit tests and shaders in the future.
A new section has been added into README.md with CMake build instructions.
Art.zip is automatically downloaded at first CMake run.

Known issues:

Direct3D11 usage: The FSL tool is currently unable to generate/compile D3D11 implementations. This PR currently enables D3D12 for Windows builds.
Release mode on Linux: Everything builds fine, but unit tests fail at runtime with: "Office preset is not supported by The Forge." Debug mode works fine.
Linux with vulkan-icd-loader 1.3.285: Unit tests crash with this package version. They work fine with 1.3.279. Reported here.
Support for Android/iOS package creation and deployment for unit tests: This PR currently does not implement Android/iOS package creation and deployment to devices. I see some assets for that purpose at Common_3/OS/Android/Packaging/. I could work on this as a future task if you find it worthwhile.

Credits: this was developed while working at Buildbox/AppOnboard. Thanks to Adam Piechowicz for reviewing and suggestions.

Hi Wolfgang,
Would you mind providing any feedback or reasons for closing this pull request?
Thanks,

Sandro I am not affiliated with The-Forge but im pretty sure the closed it because they don't want to support CMAKE in the official github repository... many people have tried to create branches/PR's and they always get turned into forks instead of merging

Hi Jonah,
Thanks for your comment; I appreciate it. If ConfettiFX expects external contributions for this project, it would be helpful to have some contribution guidelines outlining wanted and unwanted features. Also, silently closing PRs with no minimal feedback doesn't sound like a community-friendly stance.


Add newtype for launch::Slice path globs

As per spec, these are Go standard library globs and must follow that syntax (https://pkg.go.dev/path/filepath#Match). This is potentially more complex to implement as a newtype than the ones we currently have.

I'd be inclined to wontfix this to be honest. Usage of slice layers is likely going to be pretty rare, and people using it can just read the docs. Whilst it's nice that libcnb.rs can prevent a subset of errors at runtime though typing and nice DX, I don't think it's viable for it to prevent every class of issue.


Potential deprecation of concolor

I'm posting this as this project is reported as a dependent of concolor and wanted to both give you a heads up to prepare and an opportunity to discuss in case we should re-evaluate this.
We are proposing deprecating concolor in favor of either

anstream
application-specific solutions built on colorchoice, colorchoice-clap, and your choice of environment detection crates including anstyle-query and supports-color.

We welcome feedback on this topic at rust-cli/concolor#47

Thank you! I commented on the linked issue.


Update datafile in background for speed

The default $PROMPT_COMMAND is
$ echo $PROMPT_COMMAND
_z --add "$(command pwd -P 2>/dev/null)" 2>/dev/null

For me (on Cygwin, Windows 8.1), the default configuration makes it so that if I hold down the Enter key in Bash, the prompts start to lag behind. Overall, the prompt feels slow.
So I changed it to
$ echo $PROMPT_COMMAND
(_z --add "$(command pwd -P 2>/dev/null)" 2>/dev/null &)

This seems to mostly fix the issue. The z datafile is updated in the background, silently.
Is there any harm in doing this or reason why this isn't the default?

interested in this too. I removed z from my setup because it seemed to lag my prompt by a large margin.

Glad I'm not the only one! Did you try my fix? (I modified this line, but I believe you could also set $_Z_NO_PROMPT_COMMAND and then set $PROMPT_COMMAND.)

@guoguo12 is this the right way to implement your proposed modification?

That looks about right. Does it work?
Allen
On Jul 12, 2016 7:13 PM, "Filipe Silva"<EMAIL_ADDRESS>wrote:

@guoguo12 https://github.com/guoguo12 is this
https://github.com/ninrod/z/commit/a14affb6b90f845f9600ae0b656acd347b3b1472#diff-020ace7637fa3870bdb6af242b3fac53L244
the right way to implement your proposed modification?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rupa/z/issues/191#issuecomment-232235585, or mute
the thread
https://github.com/notifications/unsubscribe/AB2c-QmGD5mZuw5fA-RYHfqmYtMFmGOnks5qVEnXgaJpZM4JIh1G
.

No. it remains lagging my prompt.

I actually have
PROMPT_COMMAND="$PROMPT_COMMAND"$'\n''(_z --add "$(command pwd '$_Z_RESOLVE_SYMLINKS' 2>/dev/null)" 2>/dev/null &)'

Try that?

then i get: _z_dirs:1: no such file or directory: /Users/ninrod/.z
but afterwards, it kind of works, but it is laggy all the same.

Interesting. Well... mine definitely runs faster now. The difference seems to be about 0.1 seconds:
$ time _z --add /cygdrive/c/Users/guogu_000

real    0m0.103s
user    0m0.030s
sys     0m0.060s

$ time (_z --add /cygdrive/c/Users/guogu_000 &)

real    0m0.006s
user    0m0.000s
sys     0m0.000s

hum are you under cygwin?

Yeah, but that shouldn't make a difference because it's still Bash.

I'm in zsh on osx.

are you folks playing with this change seeing:

lots of .z. files accumulating in ~/
inaccurate counts in ~/.z (hard to test) (from temp files getting clobbered)

not sure how much i really care about accurate counts, but also i don't care a lot about prompt speed - the speed's never mattered to me when i'm actually working.

@ninrod: I believe you'll want to edit this line to get it to work in zsh.
@rupa: Hey, thanks for chiming in. (BTW, I really appreciate this project!) To answer your questions:

I see 19 .z* files in my home directory right now, but only three have last-modified dates from after when I made the tweak. Does that count as a lot?
Not sure about inaccurate counts. Why would forking mess up the counts?

I agree the speed difference isn't that noticeable. (Although I imagine it's worse on Cygwin than Linux/Mac.) But if there aren't any negative side effects, I think it's a worthwhile improvement.

Hi @rupa. Well I do care for prompt speed. Without your plugin, my prompt displays as fast as if I had invoked zsh with zsh -f. With your plugin loaded, I can actually see my computer trying to draw the prompt letter by letter. It's fast, but those 120ms are enough to bother me.
Now, why must z do something every time that a prompt is redrawn? couldn't z only do it's thing when a user cd into a directory? What z does every time that a prompt is redrawn? Does z use some kind of zsh hook for that?

Sorry, @rupa, but the difference with and without z in my configuration is very noticeable. I reported this issue a while ago in another source of slowness of my configuration, zsh-autosuggestions: https://github.com/zsh-users/zsh-autosuggestions/issues/136#issuecomment-210010601
Unfortunately, both autosuggestions and z are very important in my daily workflow (especially z, can't live without it). If you just cd across your directories, you may not even notice the delay. However, if you start using MidnightCommander, things get horribly slow. This is maybe due to the fact that MC sends cd command to the underlying shell character by character. I created an issue about that: https://github.com/MidnightCommander/mc/issues/101. I have little hopes this will ever be fixed on their side, though.
I also tried hacking MC and surrounded the cd command with zsh's bracketed paste magic to avoid triggering zsh hooks: https://github.com/balta2ar/mc/commit/f17ebb89791ce5ff64608929f62658fa04f4556d. It didn't really help. Maybe I'm missing something.
Besides of the suggested fix (which I haven't tried yet, but I will), would you be willing to consider asyncronous extension similar to this pull request, @rupa? https://github.com/zsh-users/zsh-autosuggestions/pull/134

I've pushed an async branch containing this change. I'll run it for a few days and if everything seems basically fine, I'll merge to master. Would appreciate any reports from others:

faster?
increase in ~/.z.XXXX garbage
counts off
anything else

I've just noticed that suggested change is for bash only. I did the same change in the corresponding zsh if branch above (two places). I've finally managed to conduct an experiment and obtain actual numbers.
Maybe this is not really strict and rigorous, but it visualizes the difference. First, I created a nested directory structure (110 dirs) with this code:
$ for n in $(seq 110); do DN="${DN}/notsolongdirnametotestnested_$n"; done; mkdir -p "./${DN}"

Next I wrote an automation script that runs mc with time command, traverses 30 of these directories and exits. time prints seconds it took to enter these 30 dirs. Here is the script:
#!/bin/bash

# To find out the window id use this command:
# $ xdotool selectwindow
WINDOW_ID=$1

echo "Starting test"

xdotool type --window $WINDOW_ID "time mc"
xdotool key --window $WINDOW_ID Return
# Without this keys that follow are not processed correctly
sleep 1

COMMAND=""
for i in $(seq 30); do
    COMMAND="$COMMAND Down Return"
done

xdotool key --window $WINDOW_ID $COMMAND ctrl+o
xdotool type --window $WINDOW_ID "exit"
xdotool key --window $WINDOW_ID Return

echo "Test has been finished"

Next I ran 5 different set ups 5 times each. Each setup was run in a new terminal tab. In setups I tried different combinations of zsh-autosuggestions and z. Setups are:
no_z_no_zus — z and zsh-autosuggestions are disabled
with_z_with_zus — z async and zsh-autosuggestions are enabled
only_z_async — only z async is enabled
only_z_sync — only z sync is enabled
only_zus — only zsh-autosuggestions is enabled

No
no_z_no_zus
with_z_with_zus
only_z_async
only_z_sync
only_zus

0
4.446000
8.720000
4.39200
4.862000
8.67900

1
4.447000
8.646000
4.37500
4.959000
8.58700

2
4.455000
8.867000
4.39300
4.993000
8.76600

3
4.415000
8.882000
4.38200
4.829000
8.54600

4
4.536000
8.697000
4.48900
4.892000
8.41800

mean
4.459800
8.762400
4.40620
4.907000
8.59920

std
0.045252
0.105912
0.04688
0.067886
0.13229

As you can see from only_z_async vs only_z_sync it's 4.4 vs 4.9 (I don't know why only_z_async is faster than no_z_no_zus). Unfortunately, in my configuration zus shadows z to a very big extend, but I still think it's worth it.
No new ~/.z.XXXX garbage appeared after these tests.

@balta2ar woops - can you post the changes you made for zsh support? I'm not great at zsh stuff.

So almost half a second difference from zsync to noz_nozus. seems about what I get from my end.

@rupa The idea of changes is exactly the same: offload --add to background process:
diff --git a/z.sh b/z.sh
index 197c536..b9638b5 100644
--- a/z.sh
+++ b/z.sh
@@ -216,11 +216,11 @@ if type compctl >/dev/null 2>&1; then
         # populate directory list, avoid clobbering any other precmds.
         if [ "$_Z_NO_RESOLVE_SYMLINKS" ]; then
             _z_precmd() {
-                _z --add "${PWD:a}"
+                (_z --add "${PWD:a}" &)
             }
         else
             _z_precmd() {
-                _z --add "${PWD:A}"
+                (_z --add "${PWD:A}" &)
             }
         fi
         [[ -n "${precmd_functions[(r)_z_precmd]}" ]] || {

@ninrod Are you sure? The difference that I have demonstrated is a difference of cumulative traversal of 30 directories in a row conducted specifically for the experiment to amplify the effect. That's absolutely unrealistic case. What's your set up? Please don't get me wrong, I'm not denying your delays, — I have them too, — I just I don't want to mislead anyone comparing apples to oranges.

Yeah: 500/30 = 16ms.
i get something like 30-50ms delta difference just listing directories with rupa/z turned on.

@rupa. please protect cd against user alias shenanigans.
I actually defined a function called cd here that uses your plugin which in turn uses cd alias, which in turn uses z, which in turn uses... well, I've got a segmentation fault.
So instead of using plain cd please use builtin cd instead to protect against alias and name shadowing shenanigans.

good point. done.

Thanks zupa. but maybe that is not as simple as that?
 I'm getting screwed by that. I suppose we should check if a ~/.z exists and if not, create one?

Checked out the async branch, haven't run any benchmarks but it looks like a great improvement. Would love to see it merged

merged into master. sorry I waited so long, slow and steady :)

Cool, thanks!


Coordinate origin on Kinect v2 with single-camera tracking

Hello,
Since I need to transform the OpenPTrack joint coordinates to a different coordinate system, I need the exact position of the origin on the Kinect v2.
The original MS Kinect v2 origin lies on the depth sensor, I guess on the front surface of the Kinect v2:

Am I right in assuming that you choose the same origin, that your coordinate axes have a different orientation? I assumed the following OPT single-camera coordinate origin/orientation:

Thanks for your help!

Issue can be closed.
OPT Single Camera Pose Tracking origin lies exactly as I assumed in the second picture above.
The origin has aproximately following position:

X-origin lies on the front surface of the camera.

Cool- closing!


In parseCognitoWebResponse(), added onFailure() callback for code response type

Issue #, if available:
Description of changes:
In parseCognitoWebResponse(), onFailure() callback is needed for both code response type and token response type.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Fixes #176

Fixes #176


how to implement the 'like' bool expression using expr

hello maintainers. I am trying to parse bool expression like this using expr a>10 && b like '%abc' && c not in ['a', 'b'].
But expr does not support like natively. So is there any ways to make expr support 'like' bool expression.
Thanks, in advance!

The matches operator is likely to meet your requirements. It verifies whether the left-hand operand conforms to the regular expression specified by the right-hand operand. For instance:
"aaa" matches "^a+$" == true
"abc" matches "^a+$" == false

https://expr-lang.org/docs/language-definition#operators


Installation Hanging

I am trying to create a new cluster.  I have added a project to Hetzner, created a API key and tried to run the create command using the yaml provided in your example on the main page.  The only difference is that I have added my api key.  The installation never completes and just sits waiting for the servers.  I can see in Hetzner that the objects have all been created.
Am I missing something obvious?

Hi, there is likely a problem with your key. If you are using an old type RSA key this happens because SHA1 has been deprecated in Ubuntu 22 (which is the default used by the tool) and other tools. I recommend you create new ed25519 keys and create a new cluster in a new project. There is a workaround with old keys but since you haven't used this cluster yet anyway it's easier to create a new one.

Thanks for your response, I will look into the keys and try again.  Will post back my findings.

I was using a Ubuntu 20.04 distro on WSL.  I created a 22.04 distro, created a new project on Hetzner and used the yaml file from your blog.  It gets further but still gets stuck on the third master?

Which key are you using now? Did you try with an ed25519 key?

Sorry, yes I am using a ed25519 key

Dropped the master pool to 1 and it now installs K8S

Did you just change the masters instance count from 3 to 1? if yes you need to delete the extra masters manually from the Hetzner console.

I deleted the entire cluster, then updated the yaml to specify just one master.  That worked successfully.  It just fails with masters set to 3.

When you changed the key, did you try creating a new cluster with 3 masters or did you try to update the existing one?

@vitobotta   I'm creating a brand new cluster on Hetzner and am facing the same issue as described in this ticket.
My config file is below:
---
hetzner_token: <REDACTED>
cluster_name: siliconcloud
kubeconfig_path: "./kubeconfig"
k3s_version: v1.26.1+k3s1
public_ssh_key_path: "~/.ssh/id_ed25519.pub"
private_ssh_key_path: "~/.ssh/id_ed25519"
use_ssh_agent: true
ssh_allowed_networks:
- <REDACTED>/32
- <REDACTED>/24
- <REDACTED>/32
api_allowed_networks:
- <IP_ADDRESS>/0
schedule_workloads_on_masters: true
enable_encryption: true
masters_pool:
  instance_type: cpx21
  location: nbg1
  instance_count: 3
worker_node_pools:
- name: autoscaled-nbg1-cx21
  instance_type: cpx21
  location: nbg1
  instance_count: 0
  autoscaling:
    enabled: true
    min_instances: 0
    max_instances: 2

I have generated my ssh keys as such: ssh-keygen -t ed25519
This is the output from hetzner-k3s
$ hetzner-k3s create --config cluster.yaml
Validating configuration......configuration seems valid.

=== Creating infrastructure resources ===
Network already exists, skipping.
Creating firewall...done.
SSH key already exists, skipping.
Creating placement group siliconcloud-masters...done.
Creating server siliconcloud-cpx21-master1...
Creating server siliconcloud-cpx21-master3...
Creating server siliconcloud-cpx21-master2...
...server siliconcloud-cpx21-master1 created.
...server siliconcloud-cpx21-master3 created.
...server siliconcloud-cpx21-master2 created.
Waiting for server siliconcloud-cpx21-master1...
Waiting for server siliconcloud-cpx21-master3...
Waiting for server siliconcloud-cpx21-master2...

Unhandled exception in spawn: timeout after 00:00:05 (Tasker::Timeout)
  from /workspace/lib/tasker/src/tasker/timeout.cr:37:9 in '->'
  from /usr/share/crystal/src/fiber.cr:146:11 in 'run'
  from ???
Unhandled exception in spawn: timeout after 00:00:05 (Tasker::Timeout)
  from /workspace/lib/tasker/src/tasker/timeout.cr:37:9 in '->'
  from /usr/share/crystal/src/fiber.cr:146:11 in 'run'
  from ???
Unhandled exception in spawn: timeout after 00:00:05 (Tasker::Timeout)
  from /workspace/lib/tasker/src/tasker/timeout.cr:37:9 in '->'
  from /usr/share/crystal/src/fiber.cr:146:11 in 'run'
  from ???

@psavva that setting is defaulted to false, and I'd expect who enables it to know what the SSH agent is and why they enable it. Anyway I have added a mention about it and a link to a page which explains what it is etc.

I think we can close this issue. If anyone is still having problems feel free to reopen.


Dynamic Strided Slice

This PR splits the dynamic-parameter version of strided slice from the constant parameter version, improves the shape funcs to pass more unit test, and supports executing the constant parameter version of the op on dynamically shaped inputs.
I was able to pass most tests, the only except is that on the static op with a dynamic input tensor, I can't pass tests with negative begin values.
There's a lot of te::compute being thrown around here, but I haven't seen a clean way to simplify it yet. I would love suggestions.
Thanks!
cc @zhiics @kevinthesun @yongwww @lixiaoquan @electriclilies

cc @kevinthesun  @zhiics

@mbrookhart #6314 introduced another strided slice usage, you might need to update that too.

I don't think so, it's already targeting the dynamic op
        # squeeze the two outputs of nms for strided_slice
        size = get_relay_op("squeeze")(nms_ret[1], axis=[1])
        data_slice = get_relay_op("squeeze")(nms_ret[0], axis=[0])

        # strided slice to get the dynamic result
        return get_relay_op("strided_slice")(data_slice, begin=_expr.const([0]),
                                             end=size, slice_mode="size")

@yongwww @electriclilies Can you take another look?

@mbrookhart please rebase

@mbrookhart #6337 has been merged. You can try to enable the GPU tests now

I think I'd like to do it as a separate PR after we get this merged, I don't want to conflate the strided slice op with the others too much, but I'm excited to start on this :) I'll split a branch and start playing with that.

@mbrookhart no problem
BTW, I would suggest moving the compute to topi and make dynamic version there in the next PR. Do we need to change the topi strided_slice definition to let it use dynamic/static version?

@masahi @electriclilies could you take another look and approve/comment?

@zhiics Could you take another look?

Thanks @mbrookhart @yongwww @masahi @electriclilies


participationChance seems a bit buggy

I'm getting double replies from clvr at the moment.. Not sure what happens. Invetigate.

Rewritten and changed to a probability in the closed range [0, 1] instead - hopefully new tests can get this under control.

Yep. Turns out the message handler subscribes to both pms and channel messages. We could actually output two events with this..


bug: editing non-file documents with ignore file enabled causes errors

Version
main f2e64874
Describe the bug
When editing a file that doesn't have a file URI (such as my workspace settings - although it's not clear to me why that's not a file URI), I see errors like this in the console:

Expected behavior
No errors
Additional context
No response

@abeatrix I'm not sure whether we intend to ignore or not-ignore any no-file URIs, but it actually seems like there's code here that almost handles this, but specifically lets the user-data scheme through (but ignore helper then fails on it because we expected only file URIs):
https://github.com/sourcegraph/cody/blob/cfa212c03ad33ffb99c4605cf0eebae4b6b0eaca/vscode/src/completions/context/retrievers/jaccard-similarity/jaccard-similarity-retriever.ts#L101-L109

@abeatrix I'm not sure whether we intend to ignore or not-ignore any no-file URIs, but it actually seems like there's code here that almost handles this, but specifically lets the user-data scheme through (but ignore helper then fails on it because we expected only file URIs):
https://github.com/sourcegraph/cody/blob/cfa212c03ad33ffb99c4605cf0eebae4b6b0eaca/vscode/src/completions/context/retrievers/jaccard-similarity/jaccard-similarity-retriever.ts#L101-L109

Interesting! I wasn't aware of the 'vscode-userdata' file but I'd assume we would want that to be ignored by default? wdyt 🤔 ?

Probably - but I wonder if there's other code that might be passing other URIs like this. Should we update IgnoreHelper to just reutrn true (always ignore) for non-file URIs instead of throwing? 🤔

I'm failing to reproduce this now.. if you have any ideas what I might've done to go through this code path, let me know! I've tried opening the settings files both as JSON and the UI, having it active, in the background, opened and closed... Unfortunately I didn't keep the full stack trace to know why it was going in jaccard-similarity-retriever.

Probably - but I wonder if there's other code that might be passing other URIs like this. Should we update IgnoreHelper to just reutrn true (always ignore) for non-file URIs instead of throwing? 🤔
When I wrote it, passing a non-file URI seemed like a bug, but perhaps it's very easy for documents to be non-files and it's a pain for every caller to have to handle this.
(this won't fly if we need to support virtual workspaces or similar now or in future though)

For this stage, imo we should just focus on supporting files and return true for all non-files like you suggested, since non-files cannot be indexed and are not supported by Sourcegraph anyway. Wdyt?
jaccard-similarity-retrieve is used by auto completion so we can probably reproduce by trying to trigger an autocomplete iirc.

This error will also completely break autocomplete if a non-code file is open (e.g. vs code settings) as the error bubbles through.
Not sure about what would be a good use case. Maybe we make the the isIgnored function nullable and let the caller decide what it should do with this?


Generation of go msgs fixed

"full_size" key is deprecated now (updated to "static_size")

Is better to call local variable also static_size.

Fixed


Start RocksDBMetaStore in Worker constructor

What changes are proposed in this pull request?
Starts RocksDBMetaStore in Worker constructor and check the result.
If exception happens, worker continues working without persistent MetaStore.
Why are the changes needed?
We cannot do RocksDB init in register() because when heartbeat timeouts, Worker
will do register again.
Does this PR introduce any user facing changes?
N/A

Thanks to @yyongycy and @dbw9580 for reporting and analyzing the root cause.

rebased to dora branch

alluxio-bot, merge this please.


fix(popup-menu): Onclick action of nested menu not working

Pull request type

Bug fix (non-breaking change which fixes an issue)

Description
Cause:
When you nest two popup menu's, the onclick action of the inner menu doesn't work. This is caused by the "handleOnClickOutsideElement" event of the outer menu, which is blocking the click event of the inner menu.
Fix:
By using the onClickCapture event on the custom item, the click event will be fired in the capturing phase, which runs before the bubbling phase (of the "onClickOutsideElement" handler of the outer menu). By also removing e.stopPropagation in the custom item click event, the click event is allowed to travel up the React tree to the click event of the "onClickOutsideElement" handler.
What should be covered while testing?
The onclick action of (nested) popup menu items.

Nice find! However, just applying your change doesn't work for me. Neither does your branch 455.
I have attached a small test project below which includes my widget changes. You will get a dialog when clicking on the nested menu item.
When replacing the widget with one of your versions, it will not run the nanoflow and you will not get the dialog.
TEST_BlankApp_PopUpMenuWeb_Nested_Bug.mpk.zip
I guess a combination of both is required to fix the widget properly.
Sorry for my late reply, I forgot about the PR as we don't use this widget anymore. So feel free to close it and continue in your own PR :)

Closing this one as it get's outdated.


Callsite inference of a conditional string literal type fails when the literal type of the parameter would produce a valid expansion

This is a bit of a weird one, bear with me...
As a hobby project/exercise, I've been working on (parts of) a literal regex engine using recursive TypeScript types.  It is flatly impossible to do much of interest along these lines with first-class types, so instead I've been using conditional types to write validators that either resolve to never or to identity.  This allows validation of literal function params, like a sort of SFINAE:
// this type can only be inferred to nonempty values
type NonEmpty<S extends string> = S extends "" ? never : S;
// we cannot call this with an empty string literal unless we intentionally lie to TSC about the type
function onlyAcceptsNonEmpty<S extends string>(param: NonEmpty<S>) ...

While mucking around with this, I found myself in a situation where TSC fails to infer such a parameter type in situations where the literal type of a provided string literal argument produces a valid expansion.  Instead, it falls back to the broader string type, which fails to expand.
I've extracted a repro case here.  Curiously, the behavior depends on the order of the recursive branches in the parameter type; if we swap the success check to the beginning of the type, the inference works as expected.
The relevant change between the two:
// this does not work for callsite inference
type ResolveQuantifiers<
  Regex extends string,
  Match extends string,
  S extends string = Match,
> = Regex extends `${NotQuantified<infer Prefix>}${Quantifier}${infer Suffix}`
  ? Regex extends `${Prefix}*${Suffix}`
    ? ResolveZeroOrMore<Prefix, Suffix, Match, S>
    : never
  : Match extends Regex
    ? S
    : never;

// this works for callsite inference
type ResolveQuantifiers<
  Regex extends string,
  Match extends string,
  S extends string = Match,
> =
  Match extends NotQuantified<Regex>
    ? S
    : Regex extends `${NotQuantified<infer Prefix>}${Quantifier}${infer Suffix}`
      ? Regex extends `${Prefix}*${Suffix}`
        ? ResolveZeroOrMore<Prefix, Suffix, Match, S>
        : never
      : never;

Note that in both cases, the ResolveQuantifiers type itself seems to behave as we would like, and if we provide a copy of the parameter as an explicit generic argument the compilation error goes away.
This seems like an unintended and undesirable behavior.  Naively, I'd expect the inference engine to check the exact literal type of a literal parameter first, and infer the resulting generic if it evaluates to something other than never.  What's going on here?

No idea how the duplicate tag got on this; maybe from the "issue type" dropdown selector?  Could someone either link the issue this duplicates or remove it?

No idea how the duplicate tag got on this

You used the wrong issue type. You used this one: https://github.com/microsoft/TypeScript/blob/main/.github/ISSUE_TEMPLATE/types-not-correct-in-with-callback.md?plain=1
This issue type is only meant to tell you: the described behavior is correct and intentional, as per #9998.
You should use the bug report issue type if you think you have a big report, or the "Other" one and acknowledge that issues using this template may be closed without further explanation at the maintainer's discretion.

Probably best to close this and file a new correct issue following the templates.


Bug: User color and message color mismatch

When using message_user_color = true and changing the colors of a user with "@saygo.2:tchncs.de" = { color = "none" } the color of the message does not change, and still uses the default option creating a mismatch. It also happens with colors other than none

my messages here should be in white (color "none")

Debug info
Config
[profiles."example.com"]
user_id = "@saygo.2:tchncs.de"
[layout]
style = "restore"
[settings]
default_room = "@ronniehoney:matrix.org"
message_user_color = true
username_display = "localpart"
user_gutter_width = 9
[settings.notifications]
enabled = true
[macros."normal"]
";" = ":"
[settings.users]
"@saygo.2:tchncs.de" = { color = "none" }
"@ronniehoney:matrix.org" = { color = "red" }
"@toasterbirb:tchncs.de" = { color = "yellow" }

Output of iamb --version:
iamb 0.0.9 (83b90c84)

Thank you for catching this! I've pushed a fix in #245. You can grab the binary from the CI job if you want to try it out.


dependabot

coverage: 82.254%. remained the same
when pulling fefd3ca7e582910ddcf4f184c264e07317bd2816 on dependabot
into 098272866cf892f3e939b1835c41d36661e3a537 on main.


Failed to download chromium in test project

Trying to get this setup in a test project and getting failures:
connect ETIMEDOUT <IP_ADDRESS>:443
Failed to download chromium, caused by
The command "playwright.cmd install" exited with code 1.

Is this a Microsoft owned IP ?
Is there a way to specify proxy settings during this outreach attempt?

Hey @Jojoshua.

It is.
Playwright will try to download the required browsers during the build. If you need to set up a proxy, you could run playwright.cmd install manually (you will find it in your bin folder). This link will help you setup a proxy https://playwright.dev/docs/installation#install-behind-the-firewall-or-proxy

Hey @kblok , thanks for the quick reply! No luck so far getting the right mix going. Doing testing on my home environment I see that doing npm install of playwright vs the playwright-sharp install will provide different browsers. The result install of the npm install won't satisfy the playwright-sharp browser requirement as I think they are looking for different browser versions.
However taking a different perspective, as a .NET developer I wouldn't necessarily know or expect to have to dig into npm configuration to get playwright-sharp setup.
Could we have a .NET flavor of matching configuration where if you add some well defined configuration keys in your project's appSettings it would override if available? I feel like this would also help certain CI/CD scenarios as well.
For example..

That makes totally sense @Jojoshua

@Jojoshua could you try this with your proxy? So, instead of calling npm install call the driver install
set HTTPS_PROXY=https://<IP_ADDRESS>
playwright.cmd install

@kblok so exactly how should I run that?
This is what I tried..
I opened up a powershell session with the root being \Debug.playwright\win-x64\native
Then ran set HTTPS_PROXY=http://proxy:80   *note that I'm not sure if we have our internal proxy as https but i've heard it is http
Then I ran .\playwright.cmd install but got same error
t also may be that our proxy requires authentication as well. I also tried set HTTPS_PROXY=http://user:pw@proxy:80 but that did not work either.
Do these set commands write anything to disk or are they only for your powershell session in memory?

@kblok How can I just bypass this automated setup and manually configure the browsers so that playwright-sharp thinks everything is good to go?
I found in source code the CDN locations and I am able to download zips directly.
For example I can grab https://playwright.azureedge.net/builds/chromium/857950/chromium-win64.zip
What would be the correct URLs(chromium,Firefox,FFMpeg) I would need to grab and where should they be unzipped to?

I am stuck at the same issue. I am behind a proxy and  not sure how do I pass the proxy detail to playwright sharp setup.

I ended up just manually downloading each requirement by mapping the name/revision from the browsers.json file then unzipping into C:\Users[user]\AppData\Local\ms-playwright with the appropriate named folder and adding a INSTALLATION_COMPLETE file as well.

This typically happens due to a misconfigured proxy. Please feel free to reopen if this still is an issue.

This typically happens due to a misconfigured proxy. Please feel free to reopen if this still is an issue.

@pavelfeldman could we still consider the feature request from my 2nd posting? We still need a nice way to customize the environment/install variables in a
.Net way.


Start with semantic version

Summary
It would be greatly beneficial if the growthbook proxy was versioned using semantic versioning and had regular releases.
Expected Behavior
In order to properly run growthbook-proxy in a production setting, I require the ability to pinpoint and utilize a specific version of the associated image.
Actual Behavior
It seems that the Growthbook proxy has not been versioned or released yet.

The current "versioning" also breaks dependency auto update tools like renovate

Good call, implementing better habits now!


[Bug] Overlay Notification doesn't appear unless XSOverlay Notification is enabled?

Describe the bug
Lately been having this issue where unless XSOverlay Notification is enabled, the OverLay sometimes appear and sometimes don't?
To Reproduce
Steps to reproduce the behavior:

Go to VRChat in VR
It's quite common that it will be borked already xD

Expected behavior
Overlay to show up everytime
Screenshots

What version you are running
Version 2024.09.02

Try toggle the user images option maybe it's related to that, I cannot reproduce this issue and no one else has reported it so we'd need more info before looking into it.

Gotcha I'll give it a go!
On 10/12/2024 2:24:52 AM, Natsumi @.> wrote:
Try toggle the user images option maybe it's related to that, I cannot reproduce this issue and no one else has reported it so we'd need more info before looking into it.
—
Reply to this email directly, view it on GitHub [https://github.com/vrcx-team/VRCX/issues/926#issuecomment-2408438111], or unsubscribe [https://github.com/notifications/unsubscribe-auth/AIUSSNZGO6EPZ4XBQMZ3J4TZ3DFEHAVCNFSM6AAAAABO7G5GG2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBYGQZTQMJRGE].
You are receiving this because you authored the thread.Message ID: @.>
[9205eaa3-2b52-4acd-9db8-ce6c3557ce1e]


Halo ID & RTD Documentation Update

Updates to match the Prebid.js module md files.

@MartianTribe the requested changes have been made.. i'll be sure to update our Prebid.js documentation to match next push.  Please let us know if there are any other changes needed

@bretg @MartianTribe if there are no other edits required here please merge this.. otherwise happy to make any updates


CKS: check access when get kubernetescluster config

Description
This PR fixes #7618

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[ ] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

@blueorangutan package

@weizhouapache a [SF] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: el9 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 6752

@blueorangutan test rocky8 kvm-rocky8

[SF] Trillian test result (tid-7388)
Environment: kvm-rocky8 (x2), Advanced Networking with Mgmt server r8
Total time taken: 44874 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr7854-t7388-kvm-rocky8.zip
Smoke tests completed. 108 look OK, 0 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

@kiranchavala
can you please test it ? thanks

Execute API call with user 2 API key and secret key and k8s cluster's ID get from User1

thanks @kiranchavala for the testing
merging


Is JQuery Required?

Looking at the main writeup here:
http://bgrins.github.io/spectrum/

The title is "the no hassle jquery color picker", and all of the examples include jquery, but at the bottom there are identical links to "javascript color picker", "jquery color picker", etc.
Then in the devtools section you talk about removing a "jquery dependency".
Anyway, just curious because I really like what spectrum offers but my project doesn't use jquery.
Thanks!
(And sorry, I didn't know of a better way to ask a question without spamming your twitter account)

Hi, thanks for the interest in the project.  See also #255, specifically https://github.com/bgrins/spectrum/issues/255#issuecomment-58209204.  Right now there isn't a version that has all the same features and doesn't rely on jQuery, but I've thought about changing it to make jQuery optional.  It would require reorganizing things in the project a fair amount, which I've been interested in doing but just haven't had the time to.

Thanks for the quick response!  Sorry I didn't see the previous question.  Thanks again for the tool.


NeomakeDisable -> NeomakeEnableBuffer -> Neomake status: disabled

Expected behavior
I use coc.nvim everywhere but for nix files as nix-lsp is not ready yet.
Thus I want to keep neomake only for nix files.
What I've done is disabling Neomake globally via NeomakeDisable https://github.com/teto/home/blob/eec122314be144f81a559f76c644066a180149b1/config/nvim/after/plugin/neomake.vim#L96 (the rest of the config shouldn't matter, it's historic leftover).
Then in nix.vim I call NeomakeEnableBuffer https://github.com/teto/home/blob/eec122314be144f81a559f76c644066a180149b1/config/nvim/after/ftplugin/nix.vim#L7
Finally I open a nix file, run NeomakeStatus but still see Neomake status: disabled (there could be per-buffer/global status). It should show "Enabled for this buffer" i believe.
 :Neomake nix_instantiate works fine.
 Async support: 1
Current filetype: nix
Windows: 0
[shell, shellcmdflag, shellslash]: ['/run/current-system/sw/bin/zsh', '-c', 0]
makeprg=make

##### Enabled makers

For the current filetype ("nix", used with :Neomake):
 - nix_instantiate
   - args: ['--parse-only']
   - auto_enabled: 1
   - errorformat: 'error: %m at %f:%l:%c'
   - exe: 'nix-instantiate'
   - version information (/run/current-system/sw/bin/nix-instantiate --version): nix-instantiate (Nix) 2.2.2
NOTE: you can define g:neomake_nix_enabled_makers to configure it (or b:neomake_nix_enabled_makers).

For the project (used with :Neomake!):
 - makeprg
   - append_file: 0
   - args: []
   - auto_enabled: 1
   - errorformat: '%*[^"]"%f"%*\D%l: %m,"%f"%*\D%l: %m,%-G%f:%l: (Each undeclared identifier is reported only once,%-G%f:%l: for each function it appears in.),%-GIn file included from %f:%l:%c:,%-GIn file included from %f:%l:%c\,,%-GIn file included from %f:%l:%c,%-GIn fi
le included from %f:%l,%-G%*[ ]from %f:%l:%c,%-G%*[ ]from %f:%l:,%-G%*[ ]from %f:%l\,,%-G%*[ ]from %f:%l,%f:%l:%c:%m,%f(%l):%m,%f:%l:%m,"%f"\, line %l%*\D%c%*[^ ] %m,%D%*\a[%*\d]: Entering directory %*[`'']%f'',%X%*\a[%*\d]: Leaving directory %*[`'']%f'',%D%*\a: Entering
directory %*[`'']%f'',%X%*\a: Leaving directory %*[`'']%f'',%DMaking %*\a in %f,%f|%l| %m'
   - exe: 'make'
   - version information (/run/current-system/sw/bin/make --version): GNU Make 4.2.1
     Construit pour x86_64-pc-linux-gnu
     Copyright (C) 1988-2016 Free Software Foundation, Inc.
     Licence GPLv3+ : GNU GPL version 3 ou ultérieure <http://gnu.org/licenses/gpl.html>
     Ceci est un logiciel libre : vous êtes autorisé à le modifier et à la redistribuer.
     Il ne comporte AUCUNE GARANTIE, dans la mesure de ce que permet la loi.
NOTE: you can define g:neomake_enabled_makers to configure it.

Default maker settings:
 - output_stream: 'both'
 - remove_invalid_entries: 0
 - buffer_output: 1

##### Settings

###### New-style (dict, overrides old-style)

g:neomake: {
  'disabled': 1,
  'automake': {
    'ignore_filetypes': [
      'startify',
    ],
    'events': {
      'BufWritePost': {
        'delay': 0,
      },
    },
  },
}
b:neomake: unset

at first I thought the NeomakeEnableBuffer call would work only within nix.vim but even If I run it the command from the buffer, the result is the same.

Yeah, it should work according to this test: https://github.com/neomake/neomake/blob/acb5cb35500bec16cd8e7d01469503375c8bfbe8/tests/toggle.vader#L27-L32
But could just reproduce it.

Thanks for the report, should be fixed.

thanks for the help, NeomakeStatus now reports correctly Neomake is enabled (buffer) [global: disabled] but the maker doesn't run on save even though I have in after/plugin/neomake.vim
call neomake#configure#automake('w')
silent NeomakeDisable

and the nix maker is correctly registered (:Neomake nix_instantiate works fine)
##### Enabled makers

For the current filetype ("nix", used with :Neomake):
 - nix_instantiate
   - args: ['--parse-only']
   - auto_enabled: 1
   - errorformat: 'error: %m at %f:%l:%c'
   - exe: 'nix-instantiate'
   - version information (/run/current-system/sw/bin/nix-instantiate --version): nix-instantiate (Nix) 2.2.2
NOTE: you can define g:neomake_nix_enabled_makers to configure it (or b:neomake_nix_enabled_makers).

For the project (used with :Neomake!):
 - makeprg
   - append_file: 0
   - args: []
   - auto_enabled: 1
   - errorformat: '%*[^"]"%f"%*\D%l: %m,"%f"%*\D%l: %m,%-G%f:%l: (Each undeclared identifier is reported only once,%-G%f:%l: for each function it appears in.),%-GIn file included from %f:%l:%c:,%-GIn file included from %f:%l:%c\,,%-GIn fil
e included from %f:%l:%c,%-GIn file included from %f:%l,%-G%*[ ]from %f:%l:%c,%-G%*[ ]from %f:%l:,%-G%*[ ]from %f:%l\,,%-G%*[ ]from %f:%l,%f:%l:%c:%m,%f(%l):%m,%f:%l:%m,"%f"\, line %l%*\D%c%*[^ ] %m,%D%*\a[%*\d]: Entering directory %*[`'']
%f'',%X%*\a[%*\d]: Leaving directory %*[`'']%f'',%D%*\a: Entering directory %*[`'']%f'',%X%*\a: Leaving directory %*[`'']%f'',%DMaking %*\a in %f,%f|%l| %m'
   - exe: 'make'
   - version information (/run/current-system/sw/bin/make --version): GNU Make 4.2.1
     Construit pour x86_64-pc-linux-gnu
     Copyright (C) 1988-2016 Free Software Foundation, Inc.
     Licence GPLv3+ : GNU GPL version 3 ou ultérieure <http://gnu.org/licenses/gpl.html>
     Ceci est un logiciel libre : vous êtes autorisé à le modifier et à la redistribuer.
     Il ne comporte AUCUNE GARANTIE, dans la mesure de ce que permet la loi.
NOTE: you can define g:neomake_enabled_makers to configure it.

Default maker settings:
 - output_stream: 'both'
 - remove_invalid_entries: 0
 - buffer_output: 1

##### Settings

###### New-style (dict, overrides old-style)

g:neomake: {
'disabled': 1,
'automake': {
'ignore_filetypes': [
'startify',
],
'events': {
'BufWritePost': {
'delay': 0,
},
},
},
}
b:neomake: {
'disabled': 0,
}

For your use case I suggest to rather enable Neomake explicitly for buffer's where you want it, i.e. via a filetype plugin: call neomake#configure#automake_for_buffer('w').
But I will look into if there's another bug / unexpected behavior.

So what you're doing is the following, right?
  call neomake#configure#automake('w')
  NeomakeDisable
  NeomakeEnableBuffer

The problem/issue here is that NeomakeEnableBuffer will only re-enable already existing automake config (https://github.com/neomake/neomake/blob/80cf08c8b8ec79326700a2a4fc96aa7f2b4a9dac/autoload/neomake/configure.vim#L724-L729).
So using call neomake#configure#automake_for_buffer('w') is required here, and that brings us back to the recommendation to enable/configure it only for when you need it in the first place.
But I will think about doing this then by default, or something alike.
Feedback appreciated as always.. :)

ah I see, replacing my previous instructions with a simple  autocmd FileType nix call neomake#configure#automake_for_buffer('w') fixed it.
It's a bit surprising that the status displays enabled when it does nothing but I am very happy it works now. I easily make mistakes in nix so Neomake provides huge value here.

Cool, re-opening this for now to keep track of it.


Disable regex feature of env_logger

An effort to reduce binary sizes and compilation times.
Based on current HEAD (4a04e48f8a712f22feacfe61276b65d05bf775c8) and rustc 1.38.0 (625451e37 2019-09-23)
# env_logger with regex
$ cargo build --release --no-default-features --features 'alsa-backend'
$ ls -la --block-size=k ./target/release/
-rwxrwxrwx 1 ash ash     4K Nov  6 14:32 liblibrespot.d
-rwxrwxrwx 2 ash ash    11K Nov  6 14:36 liblibrespot.rlib
-rwxrwxrwx 2 ash ash 13177K Nov  6 14:36 librespot

# env_logger with no regex
$ cargo build --release --no-default-features --features 'alsa-backend'
$ ls -la --block-size=k ./target/release/
-rwxrwxrwx 1 ash ash     4K Nov  6 14:32 liblibrespot.d
-rwxrwxrwx 2 ash ash    11K Nov  6 14:46 liblibrespot.rlib
-rwxrwxrwx 2 ash ash 11896K Nov  6 14:47 librespot

I did wonder where the regex dependency came from. Seems like quite a heavy one in something like env_logger by default

env_logger is nice, but I don't believe people utilise the regex capabilities.
The next suspect is the url crate - but that is a matter for another day ;-)

I like the effort!
On a side note if you happen to build for an cortex-a (Raspberry Pi 2 etc) you want to use the thumbv7neon-unknown-linux-gnueabihf target and not the armv7 ones since it is a better match for the hardware. Thumb mode is enabled which is going to drop the .text size significantly. That combined with panic=abort and lto and the usual tricks brings the binary down to around 2.2 mb.
Also rust binaries compress very well so by running something like squashfs or ubifs with compression enabled makes things much better on the footprint.

On a side note if you happen to build for an cortex-a (Raspberry Pi 2 etc) you want to use the thumbv7neon-unknown-linux-gnueabihf target and not the armv7 ones since it is a better match for the hardware. Thumb mode is enabled which is going to drop the .text size significantly.

Thanks for the tip, also didn't realise that armv7 disabled neon stuff as default as well.


Update warp-logs.md

Logs and diagnostics update

Thanks for the PR! To fit into our content strategy, I suggest reworking this content into a "How do I contact Support?" FAQ. See comment in PCX-7554 .


python solution

The solution to issues #160 and #163 in python

@adityabisoi, please check.

Readme file has error /Algorithms/Viral%20Advertising/solution.py merged file has this location