Add shellcheck CI via Code Climate

This will give us a whole bunch of awesome automatic checks on our shell, Ruby, and Python code for free.  More details on shellcheck here:

https://github.com/koalaman/shellcheck/blob/master/README.md
https://codeclimate.com/changelog/56e0b52837af5a008e000ba4
https://docs.codeclimate.com/docs/shellcheck

Note that at first, shellcheck will find a very large number of issues, so we won't configure the repository for codeclimate to be a "Required" status check - it will only give warnings for issues which should be fixed.  Later, when we've fixed all the issues we care about (and disabled the checks we don't care about), we can make it required.

phew.. this is purely awesome, but also a lot of noise right now. can I suggest to blacklist the most noisy ones for now? I rather have a check green but not checking everything than a check red that needs to be manually investigated everytime.

Is this PR still valid? I think now is a good time to test such a new feature.
Are any changes needed to address the latest comments?

@aspiers Is this PR still valid?

It's still needed but it needs rebasing obviously, and maybe the fixme check disabling.

@aspiers Thanks for rebasing
wow, 2128 issues - I guess it takes a while to fix these ...
Are there alternative ways to run these checks resp. report the result?

Can the results be posted as comment or somehow as a warning (instead of marking the PR red)?
Can we run the tests e.g. once per week and send the result to e.g. cloud-devel mailing list?
... at least until we have solved most of the issues.

IMHO it does not help to mark all PRs red from now on and show how many thousand issues are still open.

@jdsn commented on 9 Mar 2018, 11:02 GMT:

@aspiers Thanks for rebasing
wow, 2128 issues - I guess it takes a while to fix these ...
Are there alternative ways to run these checks resp. report the result?

Can the results be posted as comment

Uhhh, do you really want 2128 issues spamming the comment stream? ;-)

or somehow as a warning

I don't think GitHub supports that, maybe CodeClimate does but I couldn't find it.

(instead of marking the PR red)?

Red isn't ideal but it's just cosmetic.  It doesn't affect the merging of the commit.  I agree amber would be better.

Can we run the tests e.g. once per week and send the result to e.g. cloud-devel mailing list?

No, please don't.  That sounds like horrible spam which will be ignored, and it also fails to integrate with any development workflow.  If someone fixes 500 issues, you'd have to wait up to a week to see the results.  And you'd have to run it for every single PR, so then would it all go in a single mail, or one mail per PR?  I really can't see that working well.

... at least until we have solved most of the issues.
IMHO it does not help to mark all PRs red from now on and show how many thousand issues are still open.

I agree it's not ideal but the red is cosmetic.
@bmwiedemann commented on 12 Mar 2018, 08:37 GMT:

IMHO it is only useful when people can actually see some of the 2000 'issues to fix' which is not the case atm.

Yes this seems like a "feature" of CodeClimate :-(

or if it only analyzed the diff like hound does.

Inline commenting would be horrible when we have this many issues ...

Maybe just document how someone can run this check offline?

Yes, that sounds like the best way to get started with this.  I am sure we could go from 2000 issues to 1000 without much work, and then a bit more work from 1000 down to 500 etc... I'm pretty sure it's possible to run offline but haven't got time to look into it currently due to SUSEification work.  Maybe one of you guys could?

@aspiers ...

Can the results be posted as comment [...]

Uhhh, do you really want 2128 issues spamming the comment stream? ;-)

Is this an honest question?  (Phew, there's a smiley)
I am not asking about posting thousands of comments (which is obviously ridiculous) but about an alternative possibility to present the test results.
The easiest that comes to my mind is a comment with a link to a page showing the details.

Red isn't ideal but it's just cosmetic. It doesn't affect the merging of the commit. I agree amber would be better.

Well, its coloring all PRs red if we merged now. Even thought it does not hinder the merging technically, it will affect the people doing the merge. They will get used to merge pull requests with a red test. Thats a bad habit that we should not train.
So its more than 'just cosmetic'.
Therefore I would prefer to receive these results in a different way until we got the issue counter to zero (or at least pretty close).
A solution could also be, to keep this PR open until then and rebase it from time to time to get the latest issue counter. When the counter is close to 0 we could merge this PR.

Can we run the tests e.g. once per week and send the result to e.g. cloud-devel mailing list?

No, please don't. That sounds like horrible spam ...

Again, I am not asking about spamming or bothering people (in fact thats also why I am asking to not make all PRs red with merging this PR early) but rather about a different way to present the results. (Hint: there is a "e.g." in the sentence. So it would be fine to send it somewhere else, or just to me :) )

If someone fixes 500 issues, you'd have to wait up to a week to see the results. [...]

I am not asking to forbid to run such tests on demand when needed.

And you'd have [...]  so then would it [...] or [...] I really can't see that working well.

No I don't "have to" implement what obviously does not make sense. Actually I don't care about how the temporary tests are run. We would have chosen the solution that fits all needs best.
I just don't want to mark all PRs red and thus was looking for a different way to present the results. Postponing the merge of this PR is also a valid solution that solves the issue.

Maybe just document how someone can run this check offline?

Yes, that sounds like the best way to get started with this. [...]

If its easily possible, great.
Otherwise my idea is to rebase this PR once or twice a week (and plan to work on the issues in the next sprints).

Adding "do-not-merge-yet" label in order to have this PR to show the current issue counter (needs rebasing from time to time) and to prevent to mark all other PRs red when merging this before we addressed the issues. (details, see above comments)

J. Daniel Schmidt<EMAIL_ADDRESS>wrote:

@aspiers ...

Can the results be posted as comment [...]

Uhhh, do you really want 2128 issues spamming the comment stream? ;-)

Is this an honest question?  (Phew, there's a smiley)

;-)

I am not asking about posting thousands of comments (which is obviously ridiculous) but about an alternative possibility to present the test results.
The easiest that comes to my mind is a comment with a link to a page showing the details.

Well, that's what we already have in the status check.  But as Bernhard pointed out, the problem is that the link leads to a page which fails to show the list of issues, presumably because CodeClimate can't handle displaying 2128 issues on one page.  So we probably need to figure out how to fix that, as it would be the same problem if the link was posted as a comment.  Or can you think of another way to generate a link which would work?  I'm open to all ideas.

Red isn't ideal but it's just cosmetic. It doesn't affect the merging of the commit. I agree amber would be better.

Well, its coloring all PRs red if we merged now. Even thought it does not hinder the merging technically, it will affect the people doing the merge. They will get used to merge pull requests with a red test. Thats a bad habit that we should not train.

That should not be possible because the important status checks are set to required, so it is impossible to merge if they fail.  Without the correct configuration I would agree with you 100% regarding training bad habits, but since we do have correct configuration (or at least have the script I wrote which can enforce correct configuration!) I don't see the problem here.

So its more than 'just cosmetic'.

It shouldn't be for the above reason.

Therefore I would prefer to receive these results in a different way until we got the issue counter to zero (or at least pretty close).

Yeah, I'm fine with not merging this yet.  I agree we should try to get the number of issues down to a reasonable number first.  But maybe ~100 is low enough.

A solution could also be, to keep this PR open until then and rebase it from time to time to get the latest issue counter. When the counter is close to 0 we could merge this PR.

Yes that sounds good.  I think it's also well worth investigating how to run it locally, documenting that, and encouraging people to do it.

Can we run the tests e.g. once per week and send the result to e.g. cloud-devel mailing list?

No, please don't. That sounds like horrible spam ...

Again, I am not asking about spamming or bothering people (in fact thats also why I am asking to not make all PRs red with merging this PR early) but rather about a different way to present the results. (Hint: there is a "e.g." in the sentence. So it would be fine to send it somewhere else, or just to me :) )

Right ;-)  Sounds like we are on the same page.

If someone fixes 500 issues, you'd have to wait up to a week to see the results. [...]

I am not asking to forbid to run such tests on demand when needed.

True - sounds like we are agreed that the right first step is making it easy for anyone to run them.  I guess it doesn't necessarily matter which technique we choose as long as there is one which works.

And you'd have [...]  so then would it [...] or [...] I really can't see that working well.

No I don't "have to" implement what obviously does not make sense. Actually I don't care about how the temporary tests are run. We would have chosen the solution that fits all needs best.

Sure.  My point was that we would still need to figure out the right solution.  Again I think we are agreed, just coming at it from different directions :-)

I just don't want to mark all PRs red and thus was looking for a different way to present the results. Postponing the merge of this PR is also a valid solution that solves the issue.

Yup, I'm fine with that.

Maybe just document how someone can run this check offline?

Yes, that sounds like the best way to get started with this. [...]

If its easily possible, great.
Otherwise my idea is to rebase this PR once or twice a week (and plan to work on the issues in the next sprints).

Yes, let's aim for both.  But neither are super-urgent :-)

Shellcheck support is coming in the next release of Hound CI, so that might be even better if it gives inline commenting (although maybe CodeClimate does that too these days, I'm not sure).  But either way, as discussed above we still have to do the work of fixing 1000s of failures before we can enable any checks in the CI.

@aspiers commented on 30 Apr 2018, 09:46 BST:

But either way, as discussed above we still have to do the work of fixing 1000s of failures before we can enable any checks in the CI.

Hrm, maybe not any more ... assuming GitHub's new Checks API would keep the inline comments from a ShellCheck test separate to normal comments from humans.  If so, yes the check would cause spam, but at least that spam wouldn't intrude on our existing code review process so it would be fine.


Exclude specific sub folders

I know you can exclude specific folders like this:
 exclude:  ['media'],
this works if the folder is placed like this:
root
-> media
However, I have a folder like this:
root
-> assets
--> subfolder
---> media
So logic dictates that this exclude should work:
 exclude:  ['assets/subfolder/media'],
But it doesn't... is there some way I can make this work?

Closed via #99. See johnagan/clean-webpack-plugin#usage. Please open a new issue if you continue to have problems.


spring-cloud-gateway webflux ProxyExchange returns 404

I would like to create a simple proxy and aggregator server with spring-cloud-gateway. I am using dependency spring-cloud-gateway-webflux and ProxyExchange to do that. I start the app in localhost and launch it from a browser, however, it returns 404 not found.
If I use spring-cloud-gateway-mvc instead of spring-cloud-gateway-webflux, surprising the proxy works and I can browse stackoverflow in my localhost. But I still would like to find out why spring-cloud-gateway-webflux is not working.
Can anyone help to point out anything that I am missing?
I would like to create a simple proxy and aggregator server with spring-cloud-gateway. I am using dependency spring-cloud-gateway-webflux and ProxyExchange to do that. I start the app in localhost and launch it from a browser, however, it returns 404 not found.
If I use spring-cloud-gateway-mvc instead of spring-cloud-gateway-webflux, surprising the proxy works and I can browse stackoverflow in my localhost. But I still would like to find out why spring-cloud-gateway-webflux is not working.
Can anyone help to point out anything that I am missing?
controller:
@RestController
public class RouteController {
    @RequestMapping(value="/**", method={ RequestMethod.GET, RequestMethod.POST })
    public Mono<ResponseEntity<byte[]>> proxy(ServerHttpRequest request, ServerHttpResponse response, ProxyExchange<byte[]> proxy) throws Exception {
        String path = proxy.path("/");
        if (request.getMethodValue().startsWith("GET")) {
            return proxy.uri("https://stackoverflow.com/" + path).get();
        } else {
            return proxy.uri("https://stackoverflow.com/" + path).post();
        }
    }
}

application.yml:
server:
  port: 8080

I tried with adding the following to application.yml but it doesn't work.
spring:
  cloud:
    gateway:
      httpclient:
        ssl:
          useInsecureTrustManager: true

Closing in favor of stack overflow. Please don't cross post, thanks. https://stackoverflow.com/questions/60710047/spring-cloud-gateway-webflux-proxyexchange-returns-404

Would like to open this again because there is no further response on stack overflow.
I added a ProxyExchangeArgumentResolver bean but that still doesn't work.
@Configuration(proxyBeanMethods = false)
@ConditionalOnWebApplication
@ConditionalOnClass({ HandlerMethodReturnValueHandler.class })
@EnableConfigurationProperties(ProxyProperties.class)
public class ProxyResponseAutoConfiguration {

    @Bean
    public ProxyExchangeArgumentResolver proxyExchangeArgumentResolver(
            Optional<WebClient.Builder> optional, ProxyProperties proxy) throws SSLException {
        WebClient.Builder builder = optional.orElse(WebClient.builder());

        SslContext sslContext = SslContextBuilder
                .forClient()
                .trustManager(InsecureTrustManagerFactory.INSTANCE)
                .build();
        HttpClient httpClient = HttpClient.create().secure(sslContextSpec -> sslContextSpec.sslContext(sslContext));
        ClientHttpConnector httpConnector = new ReactorClientHttpConnector(httpClient);
        WebClient template = builder.clientConnector(httpConnector).build();

        ProxyExchangeArgumentResolver resolver = new ProxyExchangeArgumentResolver(
                template);
        resolver.setHeaders(proxy.convertHeaders());
        resolver.setAutoForwardedHeaders(proxy.getAutoForward());
        resolver.setSensitive(proxy.getSensitive()); // can be null
        return resolver;
    }

}

The full code and other configurations can find from here.
I am not sure if I did anything wrong esp. the annotations.

On the other hand, I did a quick and naive test by creating new WebClient to call API or get site, not to use the ProxyExchange to call nor create a new ProxyExchangeArgumentResolver bean.
It works fine and it does not complain about https or ssl. It is kinda weird and seems the 404 is not related to WebClient configuration.
@RestController
public class RouteController {

    @RequestMapping(value="/**", method={ RequestMethod.GET, RequestMethod.POST })
    public Mono<String> proxy(ServerHttpRequest request, ServerHttpResponse response, ProxyExchange<byte[]> proxy) throws Exception {

        String path = proxy.path("/");

        ExchangeStrategies exchangeStrategies = ExchangeStrategies.builder()
                .codecs(configurer -> configurer.defaultCodecs().maxInMemorySize(1024 * 1024 * 10)).build();

        return WebClient
                .builder()
                .exchangeStrategies(exchangeStrategies)
                .baseUrl("https://stackoverflow.com/")
                .build()
                .method(HttpMethod.valueOf(request.getMethodValue()))
                .uri(path)
                .retrieve().bodyToMono(String.class);
    }
}

Full code and other configuration is here


Feature/bootstrap

Adds the bootstrap command based on the atom feed pulled down from Github.

Github doesn't keep caches of the master.zip for a really long time, so if we weren't able to create the zip we retry another couple of times before dying.

In mitmproxy this is what the requests look like:

And this is the error that is being returned by Shopify:


test: removed empty methods from components

Something similar was proposed already in https://github.com/angular/components/pull/26221.


Radio transmit/receive sometimes does not work

microbit.org-ticket:276
pxt.microbit.org version: 0.6.13
tested: 15 NOV 2016 10:35
A simple radio transmit and radio receive between two micro:bits does not seem to work any more.
TX.hex looks like this

RX.hex looks like this

Zip of hex files TX RX and also a 'radio-ping-pong' that still works if loaded into both micro:bits.
files.zip

Are these used as separate files? The group is autoamatically set based on a hash of the program so it might have worked by luck unless "set group" was used.

Yes, they are separate files. That makes sense @pelikhan I was wondering why some scripts worked and some did not. It also explains some very strange behaviour we were seeing with teleporting ducks a few weeks ago, where some radio interactions worked and some did not.
I see that this fact is indeed documented in the official PXT documentation.
https://pxt.microbit.org/reference/radio/set-group

Does the set group block exist in the block editor. It vanished a while ago?
Sent from my iPhone
On 15 Nov 2016, at 11:49, David Whale <notifications<EMAIL_ADDRESS>wrote:
Yes, they are separate files. That makes sense @pelikhanhttps://github.com/pelikhan I was wondering why some scripts worked and some did not. It also explains some very strange behaviour we were seeing with teleporting ducks a few weeks ago, where some radio interactions worked and some did not.
I see that this fact is indeed documented in the official PXT documentation.
https://pxt.microbit.org/reference/radio/set-group

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/pxt/issues/776#issuecomment-260621114, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ATmGxvQv1DeNcieJZGGYIqtfi1puks3uks5q-ZwggaJpZM4KyYE-.

Yes, it's still there, it's in the ADVANCED bit underneath radio


Question: Is it possible to create a new window in pyfladesk?

I would like to open up a new window if for example a certain link or button is clicked. The new window should render a template for example. Is this possible?
I tried to implement it manually but unfortunately did not succeed.
thanks in advance

Rendering custom templates is a Routing thing, it has nothing to do with PyFladesk. In the following code will just open new windows when opening external links but this windows will be a system default browser.
In case you want to open a new window for an internal link you should think how to do it.
The objective is to keep the code as clean as possible so there are no plans for multiple windows support.
In case you want to add this feature I suggest:

Create a pattern or a way to identify which links should be open in a new window (you could just change something in the domain name, although it seems hacky)
Add the code in the init.py to handle such behaviour, you should work on the acceptNavigationRequest method


pm: device: Add wakeup state property

Add a dts binding property to override the initial wakeup state.
With battery powered boards it is possible that peripheral
devices start in a non-active state (e.g. suspended or off).
Allow to statically override the wakeup state.

@pdgendt It is intended to be used only when system is initializing, or it  should be used every time the SoC becomes ACTIVE (e.g: resumes from PM_STATE_STANDBY) ?
The property name suggest the latter but I'm not sure which is the intention.

That needs to be properly documented because will impact drivers initialization, they will need be "power" aware at this early stage, what does not happen right now.
The idea makes sense for me, just need to understand exactly how is intended to work and and document it.

Hey @ceolin ,

@pdgendt It is intended to be used only when system is initializing, or it should be used every time the SoC becomes ACTIVE (e.g: resumes from PM_STATE_STANDBY) ?
The property name suggest the latter but I'm not sure which is the intention.

The intention is indeed to be used when system is initializing, if the SoC is resuming from standby, it'll probably have the device states still in memory.
I wasn't sure about the naming as well, but figured I could re-use the wakeup prefix. Maybe startup-state makes more sense?

That needs to be properly documented because will impact drivers initialization, they will need be "power" aware at this early stage, what does not happen right now.

The addition of this property can be used IMO for drivers to behave differently during initialization, however my first intention was to play nicely with the device power management API from the application's perspective. Currently all devices are considered active until actively set otherwise. So performing a resume action would return -EALREADY and there is no way around that currently AFAIK.
What changes would you like to see then for this PR?

When the system boots up, all device init functions are called, meaning a device should be in active state. How is a device, e.g. in off state initialized? I'd like to understand what problem is this trying to solve (a real example would be useful), so adding -1 for now.

@gmarull, the scenario where I use it for is on a battery powered board, where the main SoC (running zephyr) is suspended when inactive, and has an external wakeup (from a giro in my case). RAM isn't preserved in this state.
The zephyr application, before going to the suspended state, turns off all peripheral devices that otherwise would drain the battery.
On wakeup I leave it to the application to turn on the peripheral devices, as the init functions aren't dependent on actual communication.
Performing a resume action in the init function regardless of the startup state would result in slower boot times, or potentially wouldn't even work.


./cli deposit ... failed with nonce too low

./cli deposit 9900 DAI

  *********  DutchX CLI - staging  *********
    Operation: deposit 9900 DAI
    Markets: CENSORED
    Ethereum Node: https://mainnet.infura.io
  *********************************

Secp256k1 bindings are not compiled. Pure JS implementation will be used.
2018-10-03T05:09:14.285Z INFO-cli Deposit 9900 DAI into the DX for 0xCENSORED
2018-10-03T05:09:14.287Z INFO-dx-service:services:DxTradeService Fund the account 0xCENSORED with 9.9e+21 DAI

2018-10-03T05:10:40.722Z INFO-dx-service:services:DxTradeService Approved the DX to use 9900 DAI on behalf of the user. Transaction: 0xCENSORED
2018-10-03T05:10:42.737Z ERROR-dx-service:repositories:AuctionRepoImpl Error on transaction "deposit", from "0xCENSORED". Params: [0xCENSORED,9.9e+21]. Gas: 108952, GasPrice:<PHONE_NUMBER>. Error: Error: nonce too low
Error: nonce too low
    at /usr/src/app/node_modules/web3-provider-engine/subproviders/provider.js:19:36
    at XMLHttpRequest.request.onreadystatechange (/usr/src/app/node_modules/web3/lib/web3/httpprovider.js:118:13)
    at XMLHttpRequestEventTarget.dispatchEvent (/usr/src/app/node_modules/xhr2/lib/xhr2.js:64:18)
    at XMLHttpRequest._setReadyState (/usr/src/app/node_modules/xhr2/lib/xhr2.js:354:12)
    at XMLHttpRequest._onHttpResponseEnd (/usr/src/app/node_modules/xhr2/lib/xhr2.js:509:12)
    at IncomingMessage.<anonymous> (/usr/src/app/node_modules/xhr2/lib/xhr2.js:469:24)
    at emitNone (events.js:111:20)
    at IncomingMessage.emit (events.js:208:7)
    at endReadableNT (_stream_readable.js:1064:12)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickDomainCallback (internal/process/next_tick.js:218:9)
cli.js deposit <amount> <token> [--acount account]

Deposit the DX account depositing tokens into it

Positionals:
  amount   Amount to buy, i.e. 0.8  [required]
  token    Name of the token, i.e. WETH  [string] [required]
  account  Address were you send the tokens  [string]

Options:
  --version  Show version number  [boolean]
  -h         Show help  [boolean]

Error: nonce too low
    at /usr/src/app/node_modules/web3-provider-engine/subproviders/provider.js:19:36
    at XMLHttpRequest.request.onreadystatechange (/usr/src/app/node_modules/web3/lib/web3/httpprovider.js:118:13)
    at XMLHttpRequestEventTarget.dispatchEvent (/usr/src/app/node_modules/xhr2/lib/xhr2.js:64:18)
    at XMLHttpRequest._setReadyState (/usr/src/app/node_modules/xhr2/lib/xhr2.js:354:12)
    at XMLHttpRequest._onHttpResponseEnd (/usr/src/app/node_modules/xhr2/lib/xhr2.js:509:12)
    at IncomingMessage.<anonymous> (/usr/src/app/node_modules/xhr2/lib/xhr2.js:469:24)
    at emitNone (events.js:111:20)
    at IncomingMessage.emit (events.js:208:7)
    at endReadableNT (_stream_readable.js:1064:12)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickDomainCallback (internal/process/next_tick.js:218:9)

REPOSITORY                         TAG                 IMAGE ID            CREATED             SIZE
gnosispm/dx-services               staging             21e79b39597e        7 days ago          409MB

docker pull gnosispm/dx-services:staging
staging: Pulling from gnosispm/dx-services
Digest: sha256:09f761a0fb0174261e54487290a2994780cfa6ef31fd08ffbf595392c3a01c06
Status: Image is up to date for gnosispm/dx-services:staging

Hi @reverendus !
Yes, it seems that it has to do with sending the transactions too close.
Our web3 provider takes the nonce from the count of transactions (using pending so we take the mempool into account).
We've been doing now a improvement so we can avoid this kind of problems. It's in our development branch, is done but not ready to be merged to master yet.
@dasanra , can you try to reproduce it and check if in development is fixed? If that's the case, for the time being, just for the CLI you can use the development tag image in Docker hub (https://hub.docker.com/r/gnosispm/dx-services/tags/).


[Translatable] Entities are not saved in ext_translation

Hi,
at first i enter content in default language. But when i enter the translation,  some of the "@Gedmo\Translatable" fields in entity have no entry in the translation table and override the default language content.
The strange thing is when i enter at first the translation and secondly enter the default_language everything works fine.
In my example name is not translated.
Attachment.txt

Hi, for default locale translations extension does not create a record, since these fields are already available in the entity, for any other language it will create a record in the table separately. If you wish to force all translations to be persisted including default locale, there is an option in listener you should set it to true for this reason.


DoT not working according to a PDNS Recursor 4.7.2 with DoT enabled

https://talk.desec.io/t/dot-support-status/502
rec_control dump-dot-probe-map -|grep applied-privacy.net -i
2607:f740:e633:deec::2 applied-privacy.net. 162 Bad 2022-09-16T20:28:55

Can you include whether you observe a difference for connecting via IPv4 or IPv6?

The output for the above command did not include any IPv4 entry.
Fequently the output does not include any entry at all for example if I trigger a DNS query for desec.io, wait for a bit and than run:
rec_control dump-dot-probe-map -|grep desec.io -i
(no output)

relevant config lines in recursor.conf
max-busy-dot-probes=5

pdns recursor version:
4.7.2-1pdns.bullseye

I see this (grepping for desec):
<IP_ADDRESS>      desec.io.       6       Good    2022-09-21T15:35:38
<IP_ADDRESS>    desec.io.       5       Good    2022-09-21T15:37:32
2607:f740:e00a:deec::2  desec.io.       6       Bad     2022-09-19T15:35:35
2607:f740:e633:deec::2  desec.io.       5       Bad     2022-09-19T15:35:42

So it seems DoT is only supported on v4. Also note that the domain listed for an IP is the first name the lead to a DoT probe. Other names might be served by the same IP but wont be listed. The DoT probe draft specifies that if an IP supports DoT, it should do so for all names it is authoritative for. It is best to grep for specific IPs instead of names, as it depends a query history which name is listed with the IP.

Should be resolved by #57. Please reopen if you observe any issues.


fix zerver: Switch do_change_bot_owner to RealmAuditLog

Squashed and merged as 02900ff54af9a1282712a5ed0c41598c611d85cd, thanks @misteraverin!  Notice how the commit message is more polished than what you've been doing; please use the more polished style in the future.  I also added cfe8871dfc43ee18a0c7b3cbc1973c72bdd7c07d on top to simplify writing new tests for this a bit.
Hopefully you can take what you've learned from the last few of these and do the next ones correctly the first time.


Remove vitables from environment.yml

The environment is currently not installable on M1 macOS since ViTables has no macOS M1 support. I opened an issue there (https://github.com/uvemas/ViTables/issues/115) but unfortunately the repo seems quite inactive.
It's pretty annoying to comment the according line in the environment.yml out each time I want to install a new environment and remove the comment again when pushing. Does anybody of you have an alternative to vitables in mind which we could use? Otherwise I would suggest to remove it from the environment.yml completely since this is already just the dev environment and each dev can install it on demand.

It's fine with me.  There are also sometimes missing packages for it conda, so I usually install it in a separate environment to keep it working.  I think it's still developed, but not at a very fast rate.
However, I would suggest not just removing it, but also adding some info in the documentation about how to install it and use it, since it is very useful for understanding the file structure.

Works now for 3.9, I added the osx-arm64 build to the feedstock


OAuth Idea

You say you need OAuth for certain info, you could add message in the JSON output telling apps to ask the user to Auth the api for the extended info
maybe include something like this at the bottom
"extended": [
"message": "The current user needs to authorize the api for extra information, ask the user to grant permission to the app.",
"url": "https://discord.com/...."
]

yeah this is definitely something I could do, might be helpful for some users


Service wizard generates scripts with inconsistent line endings

Reality Collective - Service Framework Bug Report
Describe the bug

Unable to replicate, will try on another machine


[version] Update to 3.2.1

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


feat/intent_plugs

companion pr https://github.com/OpenVoiceOS/OVOS-plugin-manager/pull/47-
key points:

load any number of intent plugins at once
an utterance may match more than 1 intent  (multiple commands in a single utterance)

intents are executed sequentially, not at same time

intent types are intent, keyword_intent, regex_intent
unified bus api from core, skills dont care what plugins are available
weights to modify intent confidence per plugin can be set in mycroft.conf
split intent matching in stages for High/Medium/Low confidence ranges

replaced by #349 for now


What is expected inside a byte[] array for iOS Methods.ScanFromImage?

Hi.
Thanks a lot for your library, it looks like the best thing that can be used for scanning barcodes in MAUI among Open-Source projects.
To make it possible to quickly debug the code that is used after scanning within the emulator, I noticed the Methods.ScanFromImage method and tried to use it. I tried passing PNG and Jpeg bytes, but it wasn't recognized.
I came across this and it looks like a similar problem: https://stackoverflow.com/questions/58270939/how-to-create-image-programmatically-from-byte-array-in-ios
Perhaps it's worth adding explicit xml documentation for this or switching to CGImage.FromPNG? https://learn.microsoft.com/en-us/dotnet/api/coregraphics.cgimage.frompng?view=xamarin-ios-sdk-12

Also a quick question - what is your opinion on the use of dev side dependencies and source generators in general?
Will you accept the PR regarding moving to DependencyPropertyGenerator for this file? https://github.com/afriscic/BarcodeScanning.Native.Maui/blob/master/BarcodeScanning.Native.Maui/CameraView.cs
It will look like:
[DependencyProperty<bool>("VibrationOnDetected", DefaultBindingMode = DefaultBindingMode.TwoWay,
    Description = "Disables or enables vibration on barcode detection.")
public partial class CameraView : View
{

instead
public partial class CameraView : View
{
    public static readonly BindableProperty VibrationOnDetectedProperty = BindableProperty.Create(nameof(VibrationOnDetected)
        , typeof(bool)
        , typeof(CameraView)
        , true
        , defaultBindingMode: BindingMode.TwoWay
        , propertyChanged: (bindable, value, newValue) => ((CameraView)bindable).VibrationOnDetected = (bool)newValue);
    /// <summary>
    /// Disables or enables vibration on barcode detection.
    /// </summary>
    public bool VibrationOnDetected
    {
        get => (bool)GetValue(VibrationOnDetectedProperty);
        set => SetValue(VibrationOnDetectedProperty, value);
    }

and will also allow you to use WeakEvent for the OnDetectionFinished event (there is even more boilerboard code to implement)

Hello.

TBH I really don't remember when did I last tested this methods. As per documentation bot Android and iOS methods should recognise the type of image data that is in the byte array and load it accordingly. But now that you mention this, I'll add an override to load image data directly from image file in next release. I think it will be both more convenient and more reliable.
I'm in for reducing boilerplate. If you want you can do a PR and I'll look into it.

PR is ready.
Other ideas for which I can provide PR:

MacCatalyst support
BarcodeResult IEquatable implementation through SourceGenerator

But now that you mention this, I'll add an override to load image data directly from image file in next release. I think it will be both more convenient and more reliable.

I'm primarily interested in input data as byte[] or as Stream.
To test recognition on iOS/Android in the absence of a camera, I generate a QRCode PNG image in the form of byte[]/Stream and pass it to this method. But this doesn't work for iOS right now. There is a chance that the image is too large to be recognized (the QR code takes up most of the space with some padding around the edges)

Implemented multiple overloads in 1.2.5. See if any fits your use case.


Added memory observations in EDA

My bad if I gave a confusing answer in slack earlier but I added the memory observations and discussion through this pr: #16
Is it ok if we close this one and accept #16 ?

Sure!


Throws warnings on stock AL AMI

Following the instructions in the README on a fresh AL AMI instance, the following warnings are generated:
Rule ID: xccdf_preupg_rule_python_check
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/Babel-0.9.4.egg-info is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/Jinja2-2.7.2.egg-info is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/awscli is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/awscli-1.16.102.egg-info is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/babel is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/backports is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/backports is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/backports.ssl_match_hostname-<IP_ADDRESS>.egg-info is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/boto is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/boto-2.48.0.egg-info is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/botocore is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/botocore-1.12.92.egg-info is owned by an RPM package that was not GPG signed by AL.
preupg.log.INFO: Python directory in dist-packages /usr/lib/python2.7/dist-packages/cfnbootstrap is not owned by an RPM package.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/chardet is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/cloud_init-0.7.6.egg-info is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/cloudinit is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/colorama is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/concurrent is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/daemon is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/dateutil is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/docutils is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/ecdsa is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/futures-3.0.3.egg-info is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/iniparse is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/jinja2 is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/jmespath is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/jmespath-0.9.2.egg-info is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/jsonpatch-1.2.egg-info is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/kitchen is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/kitchen-1.1.1.egg-info is owned by an RPM package that was not GPG signed by AL.
preupg.log.INFO: Python directory in dist-packages /usr/lib/python2.7/dist-packages/oscap_docker_python is not owned by an RPM package.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/paramiko is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/paramiko-1.15.1.egg-info is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/pip is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/pip-9.0.3.egg-info is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/pkg_resources is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/ply is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/preupg is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/preupgrade_assistant-2.6.0.egg-info is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/pyasn1 is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/pyasn1-0.1.7.egg-info is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/pykickstart is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/pystache is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/pystache-0.5.3.egg-info is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/python_daemon-1.5.2.egg-info is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/python_dateutil-2.1.egg-info is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/requests is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/requests-1.2.3.egg-info is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/rpmUtils is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/rsa is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/rsa-3.4.1.egg-info is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/setuptools is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/setuptools-36.2.7.egg-info is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/six-1.8.0.egg-info is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/urlgrabber is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/urllib3 is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/urllib3-1.24.3.egg-info is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/virtualenv-15.1.0.egg-info is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/virtualenv_support is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/yum is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib/python2.7/dist-packages/yumutils is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib64/python2.7/dist-packages/Crypto is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib64/python2.7/dist-packages/MarkupSafe-0.11.egg-info is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib64/python2.7/dist-packages/PIL is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib64/python2.7/dist-packages/backports is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib64/python2.7/dist-packages/curl is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib64/python2.7/dist-packages/gpgme is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib64/python2.7/dist-packages/markupsafe is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib64/python2.7/dist-packages/pyliblzma-0.5.3.egg-info is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib64/python2.7/dist-packages/rpm is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib64/python2.7/dist-packages/simplejson is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib64/python2.7/dist-packages/simplejson-3.6.5.egg-info is owned by an RPM package that was not GPG signed by AL.
preupg.risk.SLIGHT: Python directory /usr/lib64/python2.7/dist-packages/yaml is owned by an RPM package that was not GPG signed by AL.

and:
xccdf_preupg_rule_move-to-extras_check
Amazon Linux 2 provides some software in a more limited-support, but updated
more-frequently source of software, called Extras. Some of the software you
have installed here can be found in Amazon Linux Extras when you move to 2.

In particular, packages
vim-minimal-8.0.0503-1.46.amzn1.x86_64
vim-enhanced-8.0.0503-1.46.amzn1.x86_64
nano-2.5.3-1.19.amzn1.x86_64
vim-common-8.0.0503-1.46.amzn1.x86_64
vim-filesystem-8.0.0503-1.46.amzn1.x86_64

I think this is all valid. You have lot of 3rd party python packages that you need to port to Amazon Linux 2 is what it says. Those packages are installed when you install the pre-upgrade tool though :)


Developer's view of pipeline

This is pretty random and perhaps better left for a separate extension, but as an average developer I spend brief periods working directly and intensely on a build - setting it up, debugging it, etc, i.e. the kind of thing this extension handles - and most of my time developing code and submitting PRs - where I only care about the status of a few particular builds that I'm doing active development on.
It would be handy to have a 'developers mode' or simple separate view that only focussed on the status of a few particular builds (e.g. master + current branch/PR) and had links to build output and dashboard, or the output of failed builds.

Would having filtering on the current view work for this?

@deboer-tim Can you look on https://github.com/redhat-developer/vscode-tekton/pull/144

Fix with #82


[pugixml] Confusion between x86 and x64 with when using clang in Visual Studio

I have a project I just ported to VCPKG.  The regular Visual Studio solution built fine, this was generated using
cmake  -G "Visual Studio 16 2019" -DCMAKE_TOOLCHAIN_FILE="C:\vcpkg\scripts\buildsystems\vcpkg.cmake" -DVCPKG_TARGET_TRIPLET=x64-windows  ../src
The solution uses various packages including pugixml, catch2, protobuf, ... In the generated CMakeCache.txt I see lines like
protobuf_DIR:PATH=C:/vcpkg/installed/x64-windows/share/protobuf
pugixml_DIR:PATH=C:/vcpkg/installed/x64-windows/share/pugixml

which is exactly what I expect.
However we also build in Visual Studio using the built in clang compiler this is generated using
cmake  -G "Visual Studio 16 2019" -T ClangCL -DCMAKE_TOOLCHAIN_FILE="C:\vcpkg\scripts\buildsystems\vcpkg.cmake" -DVCPKG_TARGET_TRIPLET=x64-windows  ../src
Note the "-T ClangCL" to slecect the Clang toolset. This all works apart from then getting link errors from the pugixml library at compile time. After investigation I discovered that the CMakeCache.txt has the following line
pugixml_DIR:PATH=C:/vcpkg/installed/x86-windows/share/pugixml
So it is pointing to the X86 version not the X64. This only occurs for pugixml all the other packages point to X64 as expected.
So I'm assuming this is early on in the CMake configuration of my project and is some issue with the .cmake file in VCPKG. However I'm a bit of a noob at vcpkg so don't really understand what.
I am happy to do more investigation or add logs if someone can point me in the right direction.

Forgot to mention. The work around is to change the
pugixml_DIR:PATH=C:/vcpkg/installed/x86-windows/share/pugixml
to
pugixml_DIR:PATH=C:/vcpkg/installed/x64-windows/share/pugixml
in the generated CMakeCache.txt and rerun cmake, this will use the corrected cache file and things work fine

I don't think vcpkg supports clang very well.
@ras0219-msft What do you think?

cc @BillyONeal

I think this should be correct now? @davidhunter22 can you try again and tell us if it is still broken? If it is, with a repro, I'll work on fixing it :)

Hi, sorry to take so long. Yes I can confirm this is fixed, did a few more experiments to try to break things as well but all looks good.


Allow using ENV var for specifying a different path to a cache dir.

When building node modules with Nix/node2nix node_modules is pre-built and mounted read-only, resulting in node_modules/.cache not being writable. A nice and easy possibility to change the directory would be to allow overriding it with an ENV var (NODE_CACHE_DIR?)

The minimal solution of this issue is to return null if directory is not writable. It will trigger fallback in most of packages which use this.
adding support for some kind of env is still a good idea to make installations more controllable.
@sindresorhus will you take pull-request for minimal solution propose above?

I don't think we want an environment variable, but checking whether the directory is writeable is a good idea. PR welcome for that.

I'll get this sorted when #18 is resolved to prevent conflicts.


hardkernel-firmware: corrects sha256

This patch was required for me to successfully build the image,

Thank you!


python3Packages.notify-py: fix tests

Description of changes
Previously tests failed on Linux with
Cannot spawn a message bus without a machine-id

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@ofborg build python39.pkgs.notify-py python310.pkgs.notify-py

Result of nixpkgs-review pr 172622 run on x86_64-linux 1

6 packages built:

deltachat-cursed
mpdevil
python310Packages.notify-py
python310Packages.toggl-cli
python39Packages.notify-py
python39Packages.toggl-cli

Result of nixpkgs-review pr 172622 run on x86_64-darwin 1

3 packages failed to build:

deltachat-cursed
python39Packages.notify-py
python39Packages.toggl-cli

2 packages built:

python310Packages.notify-py
python310Packages.toggl-cli

I don't have a way to debug the Darwin failures. @austinbutler Would you mind looking into them?

Something new since I last ran the tests on my machine is it pops up a window with "run" or "quit" choices that hangs the tests until you choose one by clicking 😞 .
I'll see if I can suggest any improvements there.
============================= test session starts ==============================
platform darwin -- Python 3.9.12, pytest-7.1.1, pluggy-1.0.0
rootdir: /private/tmp/nix-build-python3.9-notify-py-0.3.3.drv-0/source
collecting ... ^Mcollected 20 items

tests/test_notification.py .F..................                          [100%]

=================================== FAILURES ===================================
_________________________ test_multiline_notification __________________________

    def test_multiline_notification():
        n = notifypy.Notify(enable_logging=True)
        n.message = """
    Lorem ipsum dolor sit amet, consectetur adipiscing elit,
    sed do eiusmod tempor incididunt ut labore et dolore magna
    aliqua. Ut enim ad minim veniam, quis nostrud exercitation
    ullamco laboris nisi ut aliquip ex ea commodo consequat.
    Duis aute irure dolor in reprehenderit in voluptate velit
    esse cillum dolore eu fugiat nulla pariatur.
    Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
    """
>       assert n.send() == True
E       assert False == True
E        +  where False = <bound method Notify.send of <notifypy.notify.Notify object at 0x1070457f0>>()
E        +    where <bound method Notify.send of <notifypy.notify.Notify object at 0x1070457f0>> = <notifypy.notify.Notify object at 0x1070457f0>.send

tests/test_notification.py:26: AssertionError
----------------------------- Captured stderr call -----------------------------
2022-05-11 23:07:15.101 | INFO     | notifypy.notify:__init__:49 - Logging is enabled.
2022-05-11 23:07:15.106 | WARNING  | notifypy.os_notifiers.macos:send_notification:96 - Notification icon is not supported. Read the docs for more information.
/private/tmp/nix-build-python3.9-notify-py-0.3.3.drv-0/source/notifypy/os_notifiers/binaries/Notificator.app/Contents/Resources/Scripts/notificator: line 65: osascript: command not found
=========================== short test summary info ============================
FAILED tests/test_notification.py::test_multiline_notification - assert False...
======================== 1 failed, 19 passed in 38.14s =========================

Result of nixpkgs-review pr 172622 run on x86_64-darwin 1

2 packages failed to build:

python310Packages.toggl-cli
python39Packages.toggl-cli

3 packages built:

deltachat-cursed
python310Packages.notify-py
python39Packages.notify-py

Uh yeah so I changed nothing and now tests pass 🤷 . The toggle-cli failures are also present on master.


Latest updates

Hi everyone,
I've been offline in the past month and a half due to a medical issue but I will have access to my computer next week and I will take a look over the issues.
Bit

By the way: You are featured on the flutter.dev site https://docs.flutter.dev/development/ui/layout/building-adaptive-apps#title-bars

Hi do you have any updates?

I'm back so closing this.


Add a search function

Allow users to search in upcoming, current or past comps.

Implemented in ed49b31cf4a6474e948eff3efdcbf27bdf9190de.


Added a 'scale factor' to the TV Screen.

A quick and dirty edit to correct the scaling issues with the TV screen.
Shout-out to @NWPlayer123 for reverse-engineering the audio/video manager system (avm.rpl).
It works by calling the function AVMSetTVScale(int width, int height); to set the TV's scale factor. Yes, it is that easy! And an unexpected bonus, the operating system automatically corrects the scaling on exit, so the HOME Menu shows up correctly!

Awesome, thanks a lot!
Closes #1 as well! :+1:


Determine if we should keep the netlify.toml file

Decide if the build / plugin configuration should be done on the https://app.netlify.com/ site itself or via the file.

This was removed as part of  #619


uguid: Fix tests

Codecov Report

Merging #95 (98d3bec) into main (8ea323a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #95   +/-   ##
=======================================
  Coverage   93.39%   93.39%
=======================================
  Files          18       18
  Lines        1590     1590
=======================================
  Hits         1485     1485
  Misses        105      105

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


Inspectable with vec of generic type

Hey,
thanks for the awesome crate!
Maybe you can help me with an issue I ran into: I have a resource Table which I want to inspect at runtime:
#[derive(Inspectable)]
pub struct Table<T: Copy + Debug + Clone> {
    pub radius: Distance,
    pub size: Distance,
    pub tiles: Vec<T>,
}

T can be different types of Tiles, therefore it's generic.
It keeps telling me struct defined here, with 1 type parameter: "T"
Is there a way to make the struct inspectable?

It should be fixed now with https://github.com/jakobhellermann/bevy-inspector-egui/commit/181d941abc79cbb458ef1e7b73bdd337733b1b5a, can you try if it works now for you?
You can depend on the git version using
bevy-inspector-egui = { git = "https://github.com/jakobhellermann/bevy-inspector-egui", branch = "main" }

Awesome, works like a charm. Thank you very much 👍


Support of HAL format

Hi.
I'm trying to add support of HAL. I read #42 and #44. But I still have many questions. I've made a first attempt to adapt Restangular. Please, see the commit with my comments: https://github.com/KonstantinLepa/restangular/commit/5b71894aa149de807dbafd5afc5e9256e6e181e8. It doesn't work correctly now.
There are my problems:

Processing of _embedded property. It's optimization only. It can exist or not exist. It must be transparent to the client. How should I implement it?
Chaining of methods. For example, messages, from and unread for $scope.user.one('messages', 123).one('from', 123).getList('unread'); are relations. They are not parts of URL. What will happen if from relation doesn't exist in a data? I think one('from', 123) must return an empty restangular object. Or not?

Thanks
P.S. Also, HAL supports the CURIE syntax http://tools.ietf.org/html/draft-kelly-json-hal-06#section-8.2. But I didn't think about it.

To be supported in V2 with "plug-in" system. Anyone that has already started work on that, please hold on for a couple of weeks to help us when the next version is more stable.

NICE WORK, waiting for that "plug-in" !
I wrote a little post about consuming hypermedia API's with Restangular in case someone needs to check it out while the "plug-in" is not ready:
http://www.javifernandez.me/2014/12/21/consuming-hypermedia-apis-with-restangular/

@mgonto I think we can link that in our FAQ section.

Does anyone know where the native support for HAL is - or is it a case of making custom interceptors and mapping the _links/_embedded accordingly?

+1 to implementation of HAL for Restangular

+1 for adding HAL support

+1

+1

+1

+1

What is the status of this issue?

+1

+1

+1


Multiple s3 buckets

Is it possible to make this work with multiple s3 buckets? I'm using multiple cloud front distributions backed by it's own s3 bucket. It would be great to re-use the lambda by passing the s3 bucket in a header for instance.

I'm also interested in supporting multiple S3 buckets.

I'm also interested

@jontro @OmkarKirpan - The underlying software (thumbor) supports this already, it actually expects the bucket name as the first argument after your image modifications
You need to do two things:
1.) Set the AWS_LOADER_BUCKET to an empty string ('')
https://github.com/awslabs/serverless-image-handler/blob/f47c7c7c8a29e605921297a4bf301a24637f10b1/deployment/serverless-image-handler.template#L366

2.) Pass the bucket as the first argument in the URL
'https://${Domain}/fit-in/100x100/image-name.jpg becomes 'https://${Domain}/fit-in/100x100/bucket_name/image-name.jpg
Please let me know if you have any questions, if you found this helpful, I may consider a PR to add this to the README

@astuyve Thanks, that is very helpful.

If you go in and set TC_AWS_LOADER_BUCKET to '', you can then resize from other buckets via url as you've shown, but those buckets must be public (or at least the images you're using).
I'm assuming the CF template explicitly grants read permission to whatever bucket you set as your OriginS3Bucket…

@timkelty correct, the CloudFormation template creates the AWS S3 read policy for you. So you either need to add extra read policies for your other buckets, or ensure they are publicly available.
https://github.com/awslabs/serverless-image-handler/blob/master/deployment/serverless-image-handler.template#L216-L259

@jontro Thanks for bringing this to our attention, we've added this feature to our backlog to be included in future versions of the solution!

Resolved with v4.0.0

I already have a distribution launched. Uses Python/Thumbor ( not the new nodejs/sharp ).
I am trying to get it to work with multiple buckets like mentioned above.
I tried settings the environment variable,
TC_AWS_LOADER_BUCKET to empty
Once I try access it like:
https://my_distr.cloudfront.net/fit-in/120x150/my_bucket/1_230656.20063.860870_v1_source.jpg
I get the following in error logs
File "/var/task/botocore/handlers.py", line 163, in validate_bucket_name
raise ParamValidationError(report=error_msg)
ParamValidationError: Parameter validation failed:
Invalid bucket name "": Bucket name must match the regex "^[a-zA-Z0-9.-_]{1,255}$"

Okay - it seems like my code version was old and I had to change one line and redeploy the lambda function.
This was in __init.py
My code had
if bucket is None:
Had to replace with
if not bucket:

I see! Glad you got it sorted out.
I trust it works with the latest changes?
Thanks,
Aaron Stuyvenberg
On Thu, Jan 2, 2020 at 5:28 PM Mandy Singh<EMAIL_ADDRESS>wrote:

Okay - it seems like my code version was old and I had to change one line
and redeploy the lambda function.
This was in __init.py
My code had
if bucket is None:
Had to replace with
if not bucket:
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/awslabs/serverless-image-handler/issues/56?email_source=notifications&email_token=AAMGISI46WWS2JW4TY5IKL3Q3XJGZA5CNFSM4FYXZSC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEH6GBIQ#issuecomment-570187938,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMGISK7SQUCLH3P3S2Z67LQ3XJGZANCNFSM4FYXZSCQ
.

Yes, it does @astuyve.

Sorry to bump this, it's my first time deploying this I'm having some trouble understanding using multiple buckets. All I really need is resizing and/or formatting, so i suspect sharp should be fine.
Is it possible to utilize multiple buckets with sharp or the default deployment? I'm not seeing anything in the readme.
If not, what is the path forward to using multiple buckets?

@iredmedia if you are using v4 with Sharp, what you need to do is put the value with multiple buckets separated by commas to SourceBuckets parameter when you deploy the solution. For example, bucket-1,bucket-2,bucket-3.
You can see the implementation guide to deploy the solution.
How many buckets are you trying to add? Do buckets have the similar prefix?

@beomseoklee I have 100-ish S3 buckets.
Specifying each bucket with commas is going to be painful.
Is there any way to choose multiple buckets using a prefix?
Thanks!

@sav-valerio with the latest version, if you have a certain prefix, here is what you can do.
Let's say that all of your buckets have source-bucket, and you have source-bucket, source-bucket-1, source-bucket-2, and so on.
After deploying the solution with source-bucket, which should exist in your account, then you can go to the AWS Lambda console. Then, change SOURCE_BUCKETS with regular expression, for example source\-bucket.*, then you would be able to use whole buckets with source-bucket prefix.
The above one is only available with encoded URL, not Thumbor style URL.
Please let me know if it would work for you or not.

@beomseoklee Cool, it works.
I rather have the possibility to define a regex directly in the CloudFormation template, but this is better than nothing for sure.
Thank you!

Hi
i have added two buckets, comma separated while launching the cloud formation template. but am i only able to access the images from the first bucket.
i am accessing like this
https://cloudfrontdistribution.net/fit-in/380x380/folder_name/imagename
my both buckets have the same folder name inside so bucket structure is like this
bucket1/folder
bucket2/folder
is there any way i can access the contents of both buckets using same cloudfront distribution?

@Husnainkhan2016176 that's an expected behavior of the current solution when you are using Thumbor style URL.
You can refer to https://docs.aws.amazon.com/solutions/latest/serverless-image-handler/backward-comp.html


Fix backup_restore

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

[x] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

Command Guidelines

[x] Each command and parameter has a meaningful description.
[x] Each new command has a test.

(see Authoring Command Modules)

View a preview at https://prompt.ws/r/Azure/azure-cli/5458
This is an experimental preview for @microsoft users.


DNN-8576: Improve scripts load in ajax mode to support load in sequence in FF.

Here is an article which describe the behavior in FF4: http://www.softwareishard.com/blog/firebug/script-execution-analysis-in-firefox-4/.

Thanks @zyhfish, can that link be added as a comment in the source?


Update CameraService.java

http://blog.csdn.net/fnuwfnh/article/details/46698509
AudioSource reset

Looks good for me, but can you modified the commit message?
Update don't mean anything...
You can specified what you change in first line, and describe the reason in the commit message.


ebpf mode can break host networking when calico-node rotates

When ebpf mode is enabled and upon calico-node pod termination, host level networking breaks.
This appears to be due to the bpf prog_array map IDs for calico being zeroed out whilst the
bpf ingress and egress filter rules remain causing DENY action on connections.
Expected Behavior
I rotate / delete a calico-node pod and a replacement pod should come up.
Current Behavior
I rotate / delete a calico-node pod and it appears as stuck terminating via kubectl. The host
becomes unreachable over SSH and other connectivity is broken.
Possible Solution
This is not a proper solution for what is happening, but to remedy the broken state you can
connect via serial console and run (with appropriate interface name):
tc filter del dev ens5 ingress
tc filter del dev ens5 egress
and / or deleting the entire qdisc created by calico
tc qdisc del dev ens5 clsact
Steps to Reproduce (for bugs)

Create cluster in non-ebpf mode
Switch to ebpf mode via https://projectcalico.docs.tigera.io/maintenance/ebpf/enabling-ebpf
Rotate calico-node pod

Context
Here is a long thread with debug output, note this thread did not start out troubleshooting
this exact situation, it switched to this particular behavior at this message:
https://calicousers.slack.com/archives/CUKP5S64R/p1663607646628119?thread_ts=1663261785.681519&cid=CUKP5S64R
Your Environment

Calico version: 3.24.1
Orchestrator version (e.g. kubernetes, mesos, rkt): kubernetes 1.21.10
Operating System and version: Debian bullseye (11.5)
Kernel version: Linux ip-10-49-21-99 5.10.0-18-cloud-amd64 #1 SMP Debian 5.10.140-1 (2022-09-02) x86_64 GNU/Linux
Kubernetes running in AWS ec2 the "hard way"
Docker version tested:

Docker version 20.10.18, build e42327a
Docker version 20.10.12, build 459d0df

Containerd version tested:

containerd containerd.io 1.6.8 9cd3357b7fd7218e4aec3eae239db1f68a5a6ec6
containerd containerd.io 1.4.12 7b11cfaabd73bb80907dd23182b9347b4245eb5d

It seems that mounting /sys/fs/bpf into the calico-node pod will also resolve this behavior!

I am running into same issue. I should mention that  its not just about rotating calico-node pods or when upgrading from <3.24.x this seems to be happening with fresh cluster and calico install as well.
the workaround with deleting qdisc worked for me as well.

Details from my setup and what tried before finding this issue:
After painstaking process and dozen attempts of installs/reinstalls, in/out config from calico deployment (tigera-operator based) with upgrade or even straight fresh install of calico 3.24.x ends up breaking networking on bare-metal nodes, it boils down to this particular behaviour:
https://docs.tigera.io/calico/3.25/operations/ebpf/troubleshoot-ebpf#check-if-a-program-is-dropping-packets
In same cluster which involves RHEL based VMs, all is good however on bare-metal RHEL nodes, as soon calico-node comes up (at stage where bird state to be Ready is reported), the host loses all network connectivity specifically for new connection while existing connections e.g ssh to nodes stay intact.
Initial investigation showed all inbound packets to node simply vanishing until discovered being dropped on physical interfaces. Its not just inbound connections from external hosts but also the connections that node itself generates, outbound packets getting through but return traffic..drop.
Now the articles say “check if program dropping packets” but does not say what to do if it does ?!? I cannot seem to find any other logs/error that would indicate the issue. I even stripped down the configuration from autocreating HEPs and policies for hosts. The only way to restore connectivity is to reboot the node and essentially not let calico-node get scheduled or run again on the node. I even tried wiping iptables etc, does not restore connectivity until host is rebooted.
tc -s qdisc show | grep clsact -A 2
qdisc clsact ffff: dev enp193s0f0 parent ffff:fff1
 Sent 150143 bytes 1313 pkt (dropped 298, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
--
qdisc clsact ffff: dev enp194s0f0 parent ffff:fff1
 Sent 251140 bytes 1416 pkt (dropped 335, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0

Drop counter keeps increasing…

@calerogers we mount /sys/fs/bpf from host to calico-node, but that needs mount propagation to actually stick between different calico-node pods. Can you check it is enabled in your setup?


[translation] skip bad target tests

Service is returning the wrong status at the moment. Trying to get live tests passing again while they investigate the issue.
Tracked in https://github.com/Azure/azure-sdk-for-python/issues/17914

/check-enforcer override


Dimensions check in BinaryCrossEntropy

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): 16.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: NA
TensorFlow installed from (source or binary):Binary
TensorFlow version (use command below):2.0.0-beta1
Python version:3.6
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:

Describe the current behavior
Suppose we build a model for binary classification problem and we want to use BinaryCrossEntropy loss provided in tf.keras.losses. Here is an example:
import numpy as np
import tensorflow as tf

y_true = np.array([[1.], [1.], [1.], [0.], [1.], [0.], [0.], [1.], [1.], [0.]]).astype(np.float32)
y_pred = np.array([[0.], [0.], [0.], [1.], [1.], [0.], [0.], [1.], [0.], [1.]]).astype(np.float32)

print(y_true.shape, y_pred.shape) # prints (10, 1) (10, 1)

# loss function
bce = tf.keras.losses.BinaryCrossentropy()

# Case1:
print(bce(y_true, y_pred).numpy())  # prints 9.23662 correctly

# Case2:
print(bce(np.squeeze(y_true), y_pred).numpy()) # prints 8.006299

Describe the expected behavior
When the dimensions of y_true and y_pred are different, in that case the loss function should raise an error for dimension mismatch or the model will fail silently and no one would be ab;e to debug it until unless they are aware of this behavior
Code to reproduce the issue
Check above

Added a PR #30053 for the shape check.


Prepare beta.6 release

Had a test failure in "ObjCCommunciationUserCredentialTests test_ObjCRefreshTokenProactively_TokenAlreadyExpired" - no code changes here, so probably a flaky test. Re-running the unit test job now, but we should file an issue to fix the test.

Re-ran tests and now I'm getting a failure in "ObjCCommunciationUserCredentialTests test_ObjCRefreshTokenProactively_FetchTokenReturnsError" @JoshuaLai can you assist? I can't see any change in this PR that would cause random tests to start failing, but if I recall you had experienced this before right?

Re-ran tests and now I'm getting a failure in "ObjCCommunciationUserCredentialTests test_ObjCRefreshTokenProactively_FetchTokenReturnsError" @JoshuaLai can you assist? I can't see any change in this PR that would cause random tests to start failing, but if I recall you had experienced this before right?

@bsiegel unfortunately it looks like the tests all pass locally but only on CI it is not passing reliably. For the sake of time I have disabled the objc unit tests.

unfortunately it looks like the tests all pass locally but only on CI it is not passing reliably. For the sake of time I have disabled the objc unit tests.

Thanks @JoshuaLai, this should unblock us. Let's make sure to file an issue to fix the flaky tests.


Byoung merge from 148 wait for custom fonts

Sorry – meant to create this PR on my own fork! Closing.


travis: run integration tests using NM-1.22-git Copr in el8

DockerHub currently breaks the RPM DB in our CentOS 8 container image
making the NM Copr CI jobs fail when updating NM from Copr (see #740).
In order to fix this, we have created a new image repository and have
built the image locally.
Signed-off-by: Fernando Fernandez Mancera<EMAIL_ADDRESS>

Actually, forgot something. Please add the container spec to /packaging, too.

Done, thanks!

Coverage remained the same at ?% when pulling 4dc40cbeebd0df336d2451bdd6d66db23cb5168b on ffmancera:nm1.22_git into 026ed90713784e4421adab06d38159e380a44545 on nmstate:master.

Coverage remained the same at ?% when pulling 4dc40cbeebd0df336d2451bdd6d66db23cb5168b on ffmancera:nm1.22_git into 026ed90713784e4421adab06d38159e380a44545 on nmstate:master.

Coverage remained the same at 65.505% when pulling 4dc40cbeebd0df336d2451bdd6d66db23cb5168b on ffmancera:nm1.22_git into 026ed90713784e4421adab06d38159e380a44545 on nmstate:master.

Rebased! Thanks!


"confirm transaction" button not working?

I'm on Kovan (light node launched before yarn electron)
Select an account> type a receiver's address, click on "send"> type my password> click on "confirm transaction"

No error in electron console, no call fired in network tab, no transaction mined in parity console. As if the button was not doing anything.

fixed in the latest release!

Happened to me too. It happens when the light node is in not-responding mode.
I added a loading state on the button, so that when you click once, it gets greyed out.


Full step file for June 25th build

for the fan box

@DHHwangPhD is this the correct model: Klein Filter 96mm PAPRa?

Explosion animation: https://a360.co/3PSst8k

closed by #84 and by a new assembly diagram in the main papr-print-parts project


Adapted to Cabal 1.20

I made this change to install rounded on Ubuntu 14.04 with ghc 7.8.3 and cabal <IP_ADDRESS>. It worked even in a sandbox.
I am not sure about the 1.20 lower bound on cabal version. With some CPP one could support old versions of cabal too.

I don't actually know how to use CPP to detect the current cabal version while building a Setup.hs, so we may just have to take the bound. rounded has a pretty small pool of users at this point, so that shouldn't be a problem.


[Internal] vendors-sdk - Update the packages

Related Issues
Related: https://github.com/demisto/dockerfiles/pull/34776
Description
This is an internal PR to verify and merge the changes from the original contribution PR https://github.com/demisto/dockerfiles/pull/34776 that currently can't be merged due to technical issues.
@kobymeir FYI

Hi @samuelFain , this looks good to me! Thank you!


Probes not set in carrier

What happened?
The probes are not set when bridging - the pod never gets ready
What did you expect to happen?
The probes to be set.
Please provide the output of gefyra check.

How can we reproduce it (as minimally and precisely as possible)?

What Kubernetes setup are you working with?

$ kubectl version
# paste output here

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Anything else we need to know?
No response

Resolved by #609


AccountStore usage produces warning "This version is insecure, because of default password..."

Xamarin.Auth Issue
I recently installed Xamarin.Auth and started using the AccountStore class. I have noticed recently that android logs are containing messages warning about security:
This version is insecure, because of default password.
Please use version with supplied password for AccountStore:
    AccountStore.Create(Contex, string);

Any ideas as to why I am seeing this message or if anything needs to be done about it?
Version

[ ] component version = <IP_ADDRESS>

Steps to reproduce

Use AccountStore.Create();

Platform:

[] .NET version = 4.61

Expected behaviour
No warnings in the android log
Actual behaviour
Warning in the android log:
Using:
05-07 14:29:19.223 I/mono-stdout(24759): Using:
    AccountStore.Create(Contex);
or
    AccountStore.Create();
This version is insecure, because of default password.
Please use version with supplied password for AccountStore:
    AccountStore.Create(Contex, string);
or
    AccountStore.Create(string);

@moljac
Can you help me understand what the password is used for to make an informed decision on weather to switch to the ? Is it used for further encryption of data stored in SharedPreferences? (assuming that's where the Android instance of the Account Store stores data?)


Authority is used as start URL for window.open

Start URL for PopupWindow set to the configured authority in place of previous start URL
Start URL used in constructor of PopupWindow when invoking window.open
Minor renaming with redirect URL variable

This PR aims to handle #649
@brockallen What version should this PR bump to in package.json?


Improve action callback to send back the onboardingController.

Implemented as extra initializer et convenience initializer to be backward compatible.
Adding some tests to cover this

:+1: Thanks for this!

@mamaral no pb, thx for the rest of the project :tongue:

@huguesbr You got it!


PremiumV2_LRS disks disallows scaling an AKS cluster

When using an Azure Kubernetes Service cluster, it is possible to define a storageclass that uses PremiumV2_LRS disks, as described here: https://learn.microsoft.com/en-us/azure/aks/use-premium-v2-disks.
Once such a disk was provisioned in the Azure Kubernetes Service cluster, scaling the number of cluster nodes is no longer possible with the error message

Failed to scale node pool 'agentpool' in Kubernetes service
'k8s-cluster'. Error: Code="BadRequest" Message="Attaching data disk(s)
with 'PremiumV2_LRS' storage account type requires the VMSS to be
stopped (deallocated) first. (This is a temporary limitation of the
management mode optimized for fast disk Attach/Detach.)"

This is a significant limitation of using PremiumV2 SSDs in the context of Azure Kubernetes Service, which should be mentioned in the "limitations" section.
Any insights into how to avoid this limitation or if this limitation will be mitigated eventually would be appreciated as well. In the current state, using such a disk makes scaling unusable.

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

ID: 1b4f48bd-e5e9-ebca-e29e-9dec927bc2d3
Version Independent ID: 2e032831-dbb6-aaf2-15ce-ac072ef36727
Content: Select a disk type for Azure IaaS VMs - managed disks - Azure Virtual Machines
Content Source: articles/virtual-machines/disks-types.md
Service: azure-disk-storage
GitHub Login: @roygara
Microsoft Alias: rogarana

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

Hello, @ccadruvi. Would you share what region this was in?

@ccadruvi after chatting with the product team, would you go ahead and email them directly? You can reach out to them here<EMAIL_ADDRESS>

Since the customer is reaching out directly via email, we're closing out this issue.
#please-close


update v18.0

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe/meta.yaml:

ℹ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.

For the host section of the recipe, you should usually use python {{ python_min }} for the python entry.
For the run section of the recipe, you should usually use python >={{ python_min }} for the python entry.
For the test.requires section of the recipe, you should usually use python {{ python_min }} for the python entry.
If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

ℹ PyPI default URL is now pypi.org, and not pypi.io. You may want to update the default source url.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/11999290342. Examine the logs at this URL for more detail.

@xylix @martinRenou @rpaframework-core
Could you please review and merge.
I am happy to help maintain, if you need assistance
once https://github.com/conda-forge/staged-recipes/pull/28339 is merged
I will create a PR to update to the latest version 18.9.1 that needs seedir
thanks and regards

@rxm7706, I think you should coordinate directly with @kariharju on the future of the feedstocks related to RPA Framework. He is the only one in the original @conda-forge/rpaframework-core team still involved, and as far as I know, the upstream libraries are no longer being developed.
This feedstock, however, should be owned by the original project anyways. @xylix can maybe help you get in touch with the correct people?

@rxm7706, just to clarify: there is no need to update the existing feedstocks if you don't specifically need them. I appreciate the offer though.
Both robotframework and robotframework-browser were added by our team originally because conda-forge requires all dependencies and transitive dependencies to have their own feedstocks. However, they really should be owned by their corresponding upstream projects.
Robot Framework has a public Slack that the core team also uses. I'll make them aware of this discussion, even if you'd be the one who does the regular maintenance work.


SKBitmap - Surface low-level Lock/Unlock/GetPixels APIs

These are needed for copy-less work which is very common, or to pass to an unmanaged piece of code.

Once the above is done, please update the API docs for SKBitmap.

Implemented.


Any way to find parameters documentation?

Describe the bug
You have a lot of parameters without any description, code comments or typing. Just example
count(entityName: string | EntityClass<T>, where: any): Promise<number>

how where should look here? I have similar issues with entity definition annotations, query conditions and so on. Could you provide any guidance?

All methods should accept FilterQuery<T> type, which is defined as export type FilterQuery<T> = Partial<T> | Record<string, any>;
I see that in AbstractSqlDriver the count method has any, but rest should be correctly typed. Also in entity manager methods you can pass PK directly (like em.findOne(1) instead of em.findOne({ id: 1 })).
Generally you can pass

PK value which will be automatically translated into { [PK]: PKValue }
dictionary of conditions like { prop1: val1, prop2: val2 }
smart query conditions are also supported, so one can write { 'prop1:in': [1,2,3], 'prop2:gte': 5 }

 export type FilterQuery<T> = Partial<T> | Record<string, any>;
FIY: Record<string, any> allows to put near any object that breaks near any object and makes  Partial meaningless here. I will respond with solution in dedicated ticket about em::find typings.

Yeah I know how Record works, the point of having Partial there as well is to allow IDEs to autocomplete.

@B4nan
Thanks for your support! One additional question. When i need to filter collection by foreign key for example find users in one organization should i use reference or there is a shortcut?
I have organization: Organization filed in user and organization_id FK in the table and i  now i do:
const organization = em.getReferene(Organization, organizationId);
const users = em.find(User, { organization });

Is it possible to do something like
const users = em.find(User, { organization:  organizationId});

without reference boilerplate?

Sure, you can pass any of PK, Reference or Entity itself as a value in the query.
const id = 1;
const users = em.find(User, { organization: id });

const ref = em.getReference(Organization, id);
const users = em.find(User, { organization: ref });

const ent = em.findOne(Organization, id);
const users = em.find(User, { organization: ent });

Hi @B4nan!
What is the best way to handle optional DB fields using MikroORM?
I've noticed that I can't mark property as property?: string and then set undefined - the exception was thrown

Hi @B4nan!
What is the best way to handle optional DB fields using MikroORM?
I've noticed that I can't mark property as property?: string and then set undefined - the exception was thrown

Could you be more specific and provide some snippets of how you define the entity and how you try to persist it? Also include the thrown exception and ideally create new issue for this so we do not pollute this one.

Adjusted docs about this in the dev branch, closing as resolved now, but feel free to reach out if it's not enough :]
https://github.com/mikro-orm/mikro-orm/blob/dev/docs/entity-manager.md


abnormal inner hair cell kinocilium location or orientation

Add new term:
abnormal inner hair cell kinocilium location or orientation (as a child of abnormal inner hair cell kinocilium morphology MP:0011061)
DEF: inner hair cell kinocilia are displaced from the normal position and/or do not orient in a typical pattern
SYN: abnormal IHC kinocilium location or orientation
SYN: mispositioned inner hair cell kinocilia
SYN: mispositioned IHC kinocilia

Added new term:
abnormal inner hair cell kinocilium location or orientation MP:0030962


win-17 is low on disk space for local Temp directory.

Type of Request
bug
Infrastructure Environment
LUCI, Github, Cocoon scheduler, Autosubmit, etc...
What is happening?
win-17 is low on disk space for local Temp directory.

Steps to reproduce
Step 1:
Step 2:
..
Step n:
Expected results
I expect to see X when Y is finished.

Removing old files and directories of local Temp directory to free up disk space.


any documents or illustration for cvat user groups, like business, worker, observer?

Great project, and really appreciate it. Is there a document describes more information about Groups in admin panel. The groups "admin, annotator, business, observer, and worker.", more specific illustration. And can we assign annotation and validation to different people?

@nmanovic Hi any update on this? @bsekachev

Dear @nmanovic ,
Thanks for sharing your excellent work.
Any update on this issue?

@edwardnguyen1705 , we have a general article about permissions in CVAT: https://www.cvat.ai/post/cvat-open-policy-agent
I will close the issue. We improve documentation constantly. I don't think we need an issue about that.


Implement levels

Have incremental levels that get steadily more difficult by increasing enemy health and damage.
Play different music in each new level

Closing as complete - music will remain the same throughout


Using 'SharePoint' link in suite bar (partially) reloads current site/page before actually navigating to _layouts/15/sharepoint.aspx

Category

[x] Bug

Describe the bug
From our custom web part, we're seeing quite a lot of logged exceptions related to the pageContext property (of the web part context object) being undefined. For instance, we see the following error messages:

"Cannot read property 'site' of undefined"
"Cannot read property 'web' of undefined"

This happens any time we access a pageContext property directly (e.g. context.pageContext.site.id) but it also happens deeper inside PnP logic when we try to load a list item like this:
        const items = await sp.web.lists
            .getByTitle(SOME_LIST)
            .items.filter(`Author eq 1234`)
            .top(1)
            .get();

The weird thing was that users never reported these issues to us, even though the web part couldn't have rendered correctly in these cases. I now understand why this is the case: it only seems to occur when the user navigates away to the 'sharepoint.aspx' page using the SharePoint button in the suite bar.
In this case, before actually navigating away from the current page, the current page seems to (quickly) reload/rerender. This could happen unnoticably in a split-second but it could also take some time in which case you actually see the page reload, as in the example below, in which case I use a default community site and navigate to the SharePoint page. Notice the reload just after the button click:
https://user-images.githubusercontent.com/16799069/114687549-2de7ba00-9d14-11eb-99df-5ffa674df40d.mov
During this reload we see the aforementioned errors occur as the pageContext  now is/became undefined.
Steps to reproduce
See video above, but in general:

Go to a SharePoint site
Click on the SharePoint button in the Suite Bar
See the page reload/refresh (quickly)
See the navigation to the sharepoint.aspx page take place after the reload

Expected behavior
The reload seems unnessecary but in any case shouldn't cause exceptions to occur (i.e. pageContext shouldn't be undefined)
Expected behavior would be that the navigation takes place immediately without the current page to rerender/reload.
Environment details (development & target environment)

Your Developer Environment: macOS 11.2.3
Target Environment: SharePoint Online
Framework: NA
Browser(s): Issue is seen in all major browsers, but attached videos were with Chrome v89
Tooling: SPFx v1.11.0
Additional details: Environment doesn't seem to matter. It happens in Safari but also in Edge (as I analyzed in the logs). It also doesn't seem to matter if custom web parts are even on the page. As can be seen in the first video, this unexpected reload also happens on a default community site without customizations.

Update 1 (April 16, '21)
Apologies for skipping Environment Details even though it was pointed out that they're important. I've re-added them.
I've done some more research on the behavior and created a dummy project to reproduce what we're seeing in our (much bigger and more complex) solution.
It comes down to the following code (part of HelloWorld.tsx), that shows some async logic that tries to read the pageContext property:
    private timeout: number = 0;

    public componentDidMount() {
        this.timeLog('HelloWorld [MOUNT]');
        this.timeout = setTimeout(() => {
            this.timeLog('HelloWorld [ASYNC]');
            try {
                this.setState({
                    siteId: this.props.context.pageContext.site.id.toString(),
                });
            } catch (err) {
                this.timeLog('HelloWorld [ERROR]: ' + err.message);
            }
        }, 500);
    }

    public componentWillUnmount() {
        this.timeLog('HelloWorld [UNMOUNT]');
        // If we'd clear the timeout we will not have the issue in this case
        // if (this.timeout) {
        //     clearTimeout(this.timeout);
        // }
    }

See what happens in the console when I run this web part and use the "SharePoint" button in the suite bar:
https://user-images.githubusercontent.com/16799069/115037366-adb98400-9ece-11eb-92d4-1fd1272a8126.mov
So in short this is what you see:

*Load the page
[1618582479746] HelloWorld [MOUNT] <- Expected log
[1618582480263] HelloWorld [ASYNC] <- Expected log
*Navigate to SharePoint using button in suite bar
[1618582572356] HelloWorld [UNMOUNT] <- Expected log
[1618582572362] HelloWorld [MOUNT] <- UNExpected log
[1618582572536] HelloWorld [UNMOUNT] <- UNExpected log
[1618582572876] HelloWorld [ASYNC] <- UNExpected log
[1618582572876] HelloWorld [ERROR]: Cannot read property 'site' of undefined <- UNExpected log

In this case I've used a setTimeout to mimic the async logic, but in our actual solution we're mostly waiting for async API calls to complete before we're doing other things (e.g. using the pageContext to access the site id to do some caching). The result however is similar to what you see here.
So I guess my question comes down to:

Why is there even a refresh before navigating away from the page?
Why is the pageContext undefined all of a sudden inside the async code?

I've attached the project I've used to demonstrate in the video.
DemoSolution.zip

Please complete the environment details section that was provided... versions are important. Where are you trying to reference the pageContext in your code?

@andrewconnell Hi Andrew, apologies for leaving the bits out. I've re-added them, as well as some more information after I did some research. I left the original question intact and added an update in the bottom.

Hello @MarksPoint - sorry for the long delay.
I believe the behavior has been fixed already and there is no additional mount/unmount during navigation to the SharePoint page. Could you please check it on your side?
But to be on a safe side of things, I'd recommend to review your code, and clear promises in case if the component is unmounted and/or the web part is disposed.
Otherwise there could be memory leaks and access of disposed resources.

Hi Alex,
Looking at our logs I think the issue is indeed solved. I no longer see these "Cannot read property 'site' of undefined" messages pop up.
Thanks for the feedback!