docs: fix grammar error

Hi Everyone, I’ve signed on CLA.
Thanks!
Enviado do meu iPhone
Em 31 de dez de 2018, à(s) 20:31, googlebot<EMAIL_ADDRESS>escreveu:

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.
What to do if you already signed the CLA
Individual signers
It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.
Corporate signers
Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Kindly squash your commits and rebase instead of merge. So to keep the git history clean

@LuanHenriqueR8, are you interested in fixing this or shall I do it?

Thank you for the patience @alan-agius4.I modified the contributing.ejs
file and the commit title according to the guidelines.But I was trying to
delete this pull request and open another one to fix these commits.Sorry!
Em qua, 2 de jan de 2019 às 12:49, Alan Agius<EMAIL_ADDRESS>escreveu:

@LuanHenriqueR8 https://github.com/LuanHenriqueR8, are you interested
in fixing this or shall I do it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/angular/angular-cli/pull/13336#issuecomment-450881940,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJccg5RWYoaW6VRkKZ_w1QKGG3VezI8uks5u_MbfgaJpZM4Zlr9-
.

--
Att,
Luan Santos


Option to completely disable autocomplete

Problem
Hi all. I'm using the Ansible extension primarily for the syntax highlighting. I'd like to completely disable autocompletion / autosuggestions but there doesn't seem to be a way of doing that at the extension level.
Solution
A single option to completely disable autocompletion / autosuggestions.
Alternatives
No response
Additional context
No response

I'd second this.. the recommendations are wrong about 90% of the time.

We would be more than happy to accept a PR for this.

Can you please assign me this issue.I'd be happy to fix this.


Rotation tool: cancel rotation by pressing "Escape" key

Solution
User should be able to cancel rotation by pressing "Escape" key.
If "Escape" key is pressed while a structure is being rotated:

the rotation should be cancelled and the structure revert to the original position it was in when rotation was started
the structure should stay selected

Example
During rotation:

After Escape key is pressed:

@KonstantinEpam23  I'm wondering if Rotate Tool needs this feature

@yuleicul we are planning to remove this menu from toolbar altogether, so I dont think we need to support this behaviour right now for the rotate tool.


Support empty tags for all WHERE equality operations

A missing tag on a point was sometimes treated as "" and sometimes
treated as a separate null entity. This change modifies the equality
operations to always treat a missing tag as an empty string.
Empty tags are not indexed and do not have the same performance as a tag
that exists.
Also fixes the subset method on tags to behave consistently with empty tags.
Fixes #3773.

@pauldix here's the change we talked about with regards to empty tags. I'm not sure if we're ok with the lack of indexing for empty tags as I don't really know the use case. The performance change shouldn't affect any existing behavior and should actually make WHERE tag !~ /.*/ faster (due to a weird quirk that the previous code didn't account for).

:+1: other than the test failures


Add page listing removed beta versions, replacements, and notable changes

xref https://github.com/kubernetes/website/issues/18675
some 1.16 content pulled from https://github.com/kubernetes/website/pull/19014 and https://github.com/kubernetes/website/pull/19388
preview at https://deploy-preview-26483--kubernetes-io-master-staging.netlify.app/docs/reference/using-api/deprecation-guide/

/assign @soltysh
for kubectl-convert bits
/assign @deads2k
for api-machinery and auth bits (APIService, CRD, webhooks)
/assign @robscott
for ingress/ingressclass bits
/assign @mikedanese @enj
for csr bits

/lgtm

Thanks!
/lgtm

/hold for docs review and kubectl-convert links

Updates: https://github.com/kubernetes/website/compare/76968446e0bc7d852c88ec52779d1e67371ef031..90048824c16cf9f8ed706d718c53b87c67a39fe4?short_path=22dba43#diff-22dba433fbe16d114c2dcd02ee5916e0462a078fcaa1eba9ea95e9a526a7e6d0

Led with the version rather than the type to avoid giving people panic attacks
Clarified the convert command is kubectl convert prior to 1.20

Looking at https://github.com/kubernetes/website/issues/18675#issuecomment-574213524 then I think the more we can make this look like generated output, the easier it becomes to switch over to generation.

Thanks for the detailed review! Will fix up shortly

I recommend hyperlinking to the API reference page for each resource that is mentioned.

are the links stable? from my feedback on https://github.com/kubernetes/website/issues/25505#issuecomment-763656285, I'm not sure they will be

The URLs include the categorizations (".../services-resources/...", ".../workloads-resources/...", etc) which are somewhat arbitrary. Making the URLs based on the API group/version/kind will produce more stable URLs

Looking at #18675 (comment) then I think the more we can make this look like generated output, the easier it becomes to switch over to generation.

I agree, though I don't have a great data source for the "notable changes" bit at the moment. Still, I tried to keep the format identical for each type so that once we do have a good data source for that, we could approximate this structure with a generator.

I recommend editing https://kubernetes.io/docs/contribute/style/style-guide/ to document that this page is an exception from avoid statements about the future.

done

inline comments accepted or tracking issues created, I think the only open question is about whether the hyperlinks to the API reference pages are stable enough to link all of these types to

/hold cancel

the hyperlinks to the API reference pages are stable enough to link all of these types to

That is a big question! Kind of already covered in https://github.com/kubernetes/website/issues/25505

That is a big question! Kind of already covered in #25505
I mean, #25505 asks that question.

Yeah... I'm happy to link to stable reference docs once we have them, but it's not clear the new API reference URLs are what we want long-term.

cc @kubernetes/api-reviewers
/assign @smarterclayton
/sig architecture
For overall page review

/approve
/lgtm
from sig-arch side!

/hold
to wait for @k/api-reviewers LGTM (feel free to unhold if you're part of the API review subproject and are adding LGTM).
/approve

I think this is also going to prompt an issue to mention this page in the SIG Docs part of the release process.

/lgtm
/hold cancel
from API review


There doesn't seem to be a way to change the "normal" mode keybinding

I'm sure the usual shortcut of J K works well for most people, but for those of us who don't use QWERTY (e.g. me on Colemak) it's super awkward. Where can I change this setting? It doesn't appear in the list of keybindings.

If this isn't going to be configurable, can we at least have a normal VS code command to switch to normal mode so that we could introduce our own keybinding?
Many thanks!

OK, current GitHub version now has a oomotion.gotoNormalKeybinding option, you can use "oomotion.gotoNormalKeybinding": "jk" to configure what keys you want to go back to NORMAL state.

OK, current GitHub version now has a oomotion.gotoNormalKeybinding option, you can use "oomotion.gotoNormalKeybinding": "jk" to configure what keys you want to go back to NORMAL state.

The vscode marketplace version seems not updated, can you publish it? thanks!


Wrong Enum Query Variable breaks rendering

Expected Behavior
I can enter anything in the query variable section, even values not understood by my API, and still the UI is rendered and I can keep editing the variables
Actual Behavior
As soon as I type an invalid enum value into a query variable, the API does not render at all anymore.
Reproduction Steps

Create a GraphQL query with a parameter, that references an enum type.
Enter Query variables for this enum type, like "action": "DISCONNECT" in the screenshot below. DISCONNECT is a valid enum value

Change the variable to a value, that is not a valid enum value, for example by deleting a single character

Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
This error is unrecoverable. You have to quit Insomnia and restart. When you then open the query again, it immediately breaks again. You have to delete the query to fix it.
Insomnia Version
2022.7.1
What operating system are you using?
macOS
Operating System Version
Ventura 13.1 (22C65)
Installation method
brew install
Last Known Working Insomnia version
2022.5.1

This is fixed in https://github.com/Kong/insomnia/commit/bdce88d4d3bfd6981daba264884aac05eac01701, will go out in 2022.7.2

Thanks for the quick response. When do you expect to release 2022.7.2 roughly?

@finsterwalder it will go out later today

Wonderful! Thanks a lot!


It is not eligible for getting processed by all BeanPostProcessors

I've got a problem. I configured my config cloud server:
server.port=8888
spring.cloud.config.server.git.uri=http:\\<myrepository>
spring.cloud.config.server.git.search-paths=configuration
spring.cloud.config.server.git.username=myusername
spring.cloud.config.server.git.password=mypassword

@SpringBootApplication
@EnableConfigServer
public class ConfigServerApplication {

	public static void main(String[] args) {
		SpringApplication.run(ConfigServerApplication.class, args);
	}

}

My Client is configured:
bootstrap.properties:
spring.application.name=a-bootiful-client
spring.cloud.config.uri=http://localhost:8888

When I launch server:
2019-06-03 17:45:57.206  INFO 11508 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration' of type [org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration$$EnhancerBySpringCGLIB$$43d13c7f] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)

**When I run my client:**
2019-06-03 17:50:47.600  INFO 10876 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration' of type [org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration$$EnhancerBySpringCGLIB$$231b90bd] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)

2019-06-03 17:50:48.191  INFO 10876 --- [           main] c.c.c.ConfigServicePropertySourceLocator : Fetching config from server at : http://localhost:8888
2019-06-03 17:50:49.188  INFO 10876 --- [           main] c.c.c.ConfigServicePropertySourceLocator : Located environment: name=a-bootiful-client, profiles=[default], label=null, version=d177c93a717120e0ed20f568550c9dc5604c82bf, state=null
2019-06-03 17:50:49.189  INFO 10876 --- [           main] b.c.PropertySourceBootstrapConfiguration : Located property source: CompositePropertySource {name='configService', propertySources=[MapPropertySource {name='configClient'}, MapPropertySource {name='https://almatoolbox.visualstudio.com/GIOTTO_BI/_git/giotto-sb-be/configuration/application.properties'}]}
2019-06-03 17:50:49.193  INFO 10876 --- [           main] i.a.config.ConfigClientApplication       : The following profiles are active: default
2019-06-03 17:50:49.557  INFO 10876 --- [           main] o.s.cloud.context.scope.GenericScope     : BeanFactory id=b9571387-2c61-3e86-9577-81b6523310af
2019-06-03 17:50:49.568  INFO 10876 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration' of type [org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration$$EnhancerBySpringCGLIB$$231b90bd] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2019-06-03 17:50:50.473  INFO 10876 --- [           main] i.a.config.ConfigClientApplication       : Started ConfigClientApplication in 4.487 seconds (JVM running for 5.727)

**Process finished with exit code 0**

Why ?

That's only informational, not an error. What is the problem you are having?

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.

import java.util.Arrays;
import java.util.concurrent.Executor;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import org.springframework.aop.interceptor.AsyncUncaughtExceptionHandler;
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.scheduling.annotation.AsyncConfigurer;
import org.springframework.scheduling.annotation.EnableAsync;
import org.springframework.scheduling.concurrent.ThreadPoolTaskExecutor;
@Configuration
@EnableAsync(proxyTargetClass = true)
public class ThreadConfig implements AsyncConfigurer {
private static final Logger logger = LoggerFactory.getLogger(ThreadConfig.class);

@Override
@Bean(name = "saveEventTaskExecutor")
public Executor getAsyncExecutor() {
    ThreadPoolTaskExecutor executor = new ThreadPoolTaskExecutor();
    executor.setCorePoolSize(2);
    executor.setMaxPoolSize(5);
    executor.setQueueCapacity(10);
    executor.setThreadNamePrefix("ApplicationExecutor-");
    executor.initialize();
    return executor;
}

@Override
@Bean
public AsyncUncaughtExceptionHandler getAsyncUncaughtExceptionHandler() {
    return ((ex, method, params) -> {
        logger.error("[Method : {} ; params : {}]", method, Arrays.toString(params));
        logger.error("Exception while executing async method", ex);
    });
}

}
So this is the configuration and it should create the thread which will run with prefix ApplicationExecutor-
but threads are not creating while calling the @Async in spring boot project and while build it getting above warning, so I thought it's because the bean is not creating that's why the async call not printing the logs with ApplicationExecutor- message.

Waring :-
Refreshing org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext@4f51b3e0: startup date [Wed Jul 31 21:19:03 IST 2019]; root of context hierarchy
2019-07-31 21:19:03.946  INFO 7106 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'threadConfig' of type [com.spring.boot.config.ThreadConfig$$EnhancerBySpringCGLIB$$7ee56746] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2019-07-31 21:19:03.957  INFO 7106 --- [           main] o.s.s.concurrent.ThreadPoolTaskExecutor  : Initializing ExecutorService

@vikas436 please don't comment on unrelated, closed issues. I'd recommend asking on https://gitter.im/spring-projects/spring-boot or stack overflow.


SimpleTcpServer DataReceived method spawns a new task for each DataReceived event

The implementation of the DataReceiver method in the SimpleTcpServer spawns a new Task to call _events.HandeDataReceived. this could potentially lead to problems as there is no guarantee that the tasks will run in the correct order (in high data rate scenarios). As each client runs the DataReceiver as a separate task, I don't think it is necessary to do this (unless I'm missing something?)
Interestingly, the SimpleTcpClient equivalent method does NOT spawn a new Task to call the _events.HandleDataReceived method, which is inconsistent.

The client doesn't need to. It's managing exactly one TCP connection. The server manages many which is why a task is spawned for each. I did not want to implement my own scheduler so I left that to be the job of the underlying operating system.

But each server client connection already spawns a task to run its own data receiver. I don't see the benefit of then also spawning a task to handle the firing of the data received event.

Those events are fired synchronously. By burying them in a task it allows the server to fire more in parallel.


Added new personal blog entry to bloggers.json

Coverage remained the same at 63.779% when pulling b62370506a86c521ee9746ec65769490e23cf511 on ggajos:master into 487e1ca70b5a328a1ab20ca9f321518790fe5c4e on tdziurko:master.


Add additional params to interfaces Reader&Writer

Q
A

Is bugfix?
❌

New feature?
✔

Breaks BC?
✔

Fixed issues

Add additional params to interfaces Reader&Writer
Add validate for category name

@samdark  Thanks :+1:


please help: Academic Theme: custom types of publications

I am helping a friend with her new website for a 501c NGO using Academic. We are both thrilled by Hugo and the Academic. Now here is what we didn't get to work:
For publications there is like a list with definitions on what exactly is the type of publication (e.g. report, book, paper, etc.). What do we need to do if we want our own classification/nomenclature here, e.g. "filed brief", "public submission"? Or alternatively: where can we edit the translation for the publication classes?
Regards,
Guido

Github issues shouldn't be used for support requests. You should probably try https://discourse.gohugo.io/ instead.

Github issues shouldn't be used for support requests. You should probably try https://discourse.gohugo.io/ instead.

Thanks to @ognarb's advice, @GuidoBo has started a new thread on Hugo Discourse at https://discourse.gohugo.io/t/academic-theme-customize-publication-nomenclature/31178
Closing this GitHub issue.


onboarding Microsoft.Azure.ApplicationInsights.Query by updating mapping

OPS Build status updates of commit 25f537c:
:clock10: Preparing: average preparing time is 1 min(s) 36 sec(s)

OPS Build status updates of commit 25f537c:
:clock10: Incremental building: average incremental building time is 34 min(s) 32 sec(s)

OPS Build status updates of commit 25f537c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-mapping/reference.yml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


update golden-query notebook and fix typo in golden docs

updating the documentation to be consistent for Golden query tool and have a better introduction to the tool

thanks @ezpuzz!


fix: added missing capability translations methods

added missing createTranslations and updateTranslations methods for capability translations
fixed upsertTranslations to work as an upsert in code since the API doesn't work that way for capabilities
updated unit tests

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Add Doc Authors option

Description

Added authors to frontmatter. In desktop it displays in the TOC, in mobile it displays at the top of the doc.

Authors takes a list of Github IDs. By default it uses the github ID as the name and github.com/github_id as the URL. authors.json file can be used to overwrite this with fields for name, title, image_url, and url. If image 404's it defaults to Dev at static/img/dev.png.

Added footer to encourage contributing

Added authors to some files, will encourage others to add themselves to their docs. Will also check with authors for updates on their url, title, and image before pushing.

Updated contributing doc to add info on authors frontmatter

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate)

Types of changes

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes if appropriate.
[ ] All new and existing tests passed.

Experimental - Added support to put Authors in footer of docs without a TOC.
See https://pan-dev-f1b58--pr313-lugpd57b.web.app/ansible/docs/panos/info/connectivity/ for an example.


error with lucet-runtime

error with lucet runtime
let module = DlModule::load("output.so").unwrap();
let region = MmapRegion::create(1, &Limits::default()).unwrap();

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: DlError(Custom { kind: Other, error: "output.so: undefined symbol: __wasi_fd_prestat_get" })'

It looks like the lucet-wasi host functions didn't get linked into the executable you made. There are two things required to ensure that:

Call the runtime and lucet-wasi ensure_linked functions somewhere in your executable. The calls don't actually do anything, so putting them at the beginning of main is fine. Just has to be in reachable code.
https://github.com/fastly/lucet/blob/6ae5a401bfd2f3f9d9160623fd7c1312ef312de9/lucet-wasi/src/main.rs#L37-L40

You need to configure the linker to make all symbols available to the dynamic linker. The usual way to do this is with a .cargo/config file with the following flags:

[build]
rustflags = ["-C", "link-args=-rdynamic"]

my executable is in c

rustflags = ["-C", "link-args=-rdynamic"]

allready

I am trying to run a project that is already written in c and compiled to wasm.
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: ModuleError(IncorrectModule("error loading required symbol `lucet_module_data`: /home/aranajhonny/lab/wasm-quickjs/qjs.so: undefined symbol: lucet_module_data")

Do you have any examples of any complete project written in c that runs with this runtime?

Can you run it with lucet-wasi?

are output.so and qjs.so above both the same file?

yes

Maybe I'm doing something wrong, I'm not very expert.

The next thing I'd suggest trying is seeing if you can run lucet-wasi qjs.so to double check that both work the same. For the lucet_module_data error, you can verify that the symbol does or doesn't exist with objdump - you can do something like this:
> objdump -x a.out | grep lucet_module_data
0000000000201000 l     O .data<PHONE_NUMBER>001177 lucet_module_data

lucet_module_data will be present in artifacts from lucetc, and must be present for for DlModule to understand how to load the file. The undefined symbol: lucet_module_data error you saw is usually an indication that the file that it tried loading didn't come from lucetc.

 objdump -x qjs.so | grep lucet_module_data
00000000005eceb0 l     O .data<PHONE_NUMBER>024ed2 lucet_module_data

Here's an example of how to run a compiled WebAssembly module using Lucet:
use lucet_runtime::*;
use lucet_wasi::*;

fn main() {
    lucet_wasi::hostcalls::ensure_linked();
    let dl_module = DlModule::load("a.out").unwrap();
    let region = MmapRegion::create(1, &Limits::default()).unwrap();
    let mut instance = region.new_instance(dl_module).unwrap();
    let wasi_ctx = WasiCtx::new(&[]);
    instance.insert_embed_ctx(wasi_ctx);
    instance.run("entrypoint", &[]).unwrap();
}

thanks but I always get the same result
IncorrectModule("error loading required symbol `lucet_module_data`: a.out: undefined symbol: lucet_module_data"))', src/libcore/result.rs:999:5

https://github.com/lucifer-cpu/lucet-demo

@awortman-fastly @jedisct1 It works, thanks for your patience and help.


Block Audit Scheduled Job

Created a scheduled job to audit block types and refactored the block… type audit to retrieve data from DDS

Have tested locally and this works. Thanks Dan!


Can not move left of first item

Bug / Feature Request?  Be able to insert before the first node in an intuitive way.
Jodit Version:   v.3.19.5
Browser:  Chrome
OS:  Windows
Is React App:  False
Expected behavior:
I would expect when I am on a tag, like a  tag at the start of the document and I move left, it would go before the tag so I could add more.  At least be able to press Ctrl+Enter and get a new line to enter stuff on?  Even that wouldn't be obvious to a person using this as a user, maybe add code to insert a new line at the current position. (before selected node).
Actual behavior:
There is no way that is obvious to the user on how to insert a header or more text above a LI tag (for example) when on the top line.  The document is basically "stuck" with the list tag at the top unless you insert something like a table and clean it all up.
Press the left arrow in the UI and show the HTML - still in the , you can't physically move left of the first li tag element to insert more.
Using this hacky code in the console I was able to insert a new line at the very beginning, just as a rough solution to my problem.
tmpEditor.s.insertCursorAtPoint(1,1) .. then insert a node.

After reading the source, you can double click to create a new line thanks to the add-new-line plugin.  It took a few times but I was able to use double click to add a new line above the  tag.
If the new line feature is used in any element and the cursor is at the beginning of the element and the line - maybe insert before the current element instead of after?
Maybe add a hotkey ['ctrl+enter'] that triggers this anytime without the mouse?  If it checked to assure it was at the start of an element and inserted above, that may be intuitive enough.
Just a thought, feel free to close this anytime as it really isn't a bug or a feature request you aren't already working through.


WASM File is missing in the latests release

Hi, thank you for the work on this plugin.
The WASM File of the latest release (0.4.0) is missing in the assets.
https://github.com/dj95/zjstatus/releases

Hi, thank you for notifying me. I somehow missed it (or did'nt verify it). The WASM file is uploaded right now :)


Tweak synchronous memcpy implementation

The existing one can have issues on certain systems, therefore this limits use of direct memcpy via largeBAR to sizes where it is unequivocally better.
Also addresses SWDEV-220030.

Lets merge this in.


double stacked bar graph?

tried with giving the spacing for alternate bars like bar chart, but spacing not working.
{
spacing:40,
stacks: [
{color: '#640B9F', value: 0},
{color: '#E39BC3', 'value': 1}
]
}

Hi @VijinR 👋
Thanks for pointing out the issue.
It is fixed in version 1.0.14🎉


Release notes

Hi @antmsbrito
I just saw that a new version was released. Awesome, congrats!
https://github.com/HenriquesLab/NanoPyx/releases/tag/0.5.0
Would it be possible to put release notes on that page so that people know what was changed? In particular consider listing backwards compatibility breaking changes. That can be key to maintain a good relationship with people who use nanopyx in their own work.
You can generate those notes when making the release (or later) by clicking on the respective button right next to the field where you enter the version number.
Thanks!
Best,
Robert

All done!
Thanks,
AB


Don't build pdfs in readthedocs

Fixes # (provide issue number if applicable)
Feature Summary and Justification
This feature provides ...
References

Pull Request Test Coverage Report for Build 9cb0c0495920ea0a665249d00664b2eb6a9be548-PR-19

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build d9b61d3849ae47d60281768a08497523a1697de0:
0.0%

Covered Lines:
3477

Relevant Lines:
3477

💛  - Coveralls


[BUG]: Perplexity model name does not match models available via the API

How are you running VectorAdmin?
Docker (local)
What happened?
The model name under perplexity is wrong and does not match any model on perplexity model card.
Are there known steps to reproduce?
Follow these steps:
Chat Settings > Workspace LLM Provider > Perplexity AI > Workspace Chat Model > llama-3.1-sonar-huge-128k-chat
Now try chatting and it will say invalid model. That's because llama-3.1-sonar-huge-128k-chat is not the right name for the 405B model. It is llama-3.1-sonar-huge-128k-online as seen in docs here - https://docs.perplexity.ai/guides/model-cards

Would be way more effort than its worth because they also keep changing the docs page too! 😆
~$3B company and can't make a /models endpoint like everyone else, crazy!

Would be way more effort than its worth because they also keep changing the docs page too! 😆
~$3B company and can't make a /models endpoint like everyone else, crazy!

brainstorming here: Maybe a feature where user can type in model name in addition to the preset drop down?


Error "Cannot process argument because the value of argument "path" is null. Change the value of argument "path" to a non-null value."

I can't provide more détails as I don't know how to get more debug info from the tool.
My agent is VSTS online and I guess the error doesn't show up on local agent.
Its consistent everytime I run it.
It doesn't even start to process the git command so I suspect this happen when it tries to locate the path of the scripts
Cheers

I got the same error
2018-05-23T13:11:46.2840001Z ##[error]Cannot process argument because the value of argument "path" is null. Change the value of argument "path" to a non-null value.
Some idea how to fix it?

Me too

Same over here

Anything new there? I'm running into the same error

I found out somehing. The Build Pipeline gets the sources at beginning. So i think, git can find the needed information about the repository inside the pulled sources. The Release Pipeline hasn't the function to get the sources per default. So in my case i have decided to use the mirroring inside the Build pipeline.

Hello @saigkill - I am facing the same issue with my Azure release pipeline. My intention is to push the artifacts to a GIT repo.
Could you please give more idea on how you achieved it ?

Hello @saigkill - I am facing the same issue with my Azure release pipeline. My intention is to push the artifacts to a GIT repo.
Could you please give more idea on how you achieved it ?

Same issue here, with null path, will attempt build path mirror and update

Was able to achieve this by doing the following:

Create a new Azure Project
import repo from github
create a build pipeline that mirrors the two repositories.


Needs more features: split view, web panels, omnisidebar

Needs more features: split view, web panels, omnisidebar

notes!

https://github.com/ric2b/Vivaldi-browser/tree/master/notes

https://github.com/mozilla/side-view/


Add method for fetching organisation samples

Thanks for the contribution @hegga ! I've manually merged this PR.


Implement Gateway status updates

ok, removed the workaround after https://github.com/submariner-io/submariner/pull/506 was merged

E2E tests being handled here: https://github.com/submariner-io/submariner/pull/508

BTW I noticed that logs in gateway node were displayed at TRACE level by default. Pushed the following PR to set it to DEBUG - https://github.com/submariner-io/submariner/pull/509
CC: @tpantelis @skitt @mangelajo

Unrelated globalnet failure, I re-ran that test.

Thanks for the review @skitt

Thanks for the review @skitt

Not much of a review, but it works for me, and my concerns have been raised and addressed already!

@tpantelis I opened this to handle comments as a follow-up https://github.com/submariner-io/submariner/issues/519 if that's ok
Currently lighthouse pushed a new ":latest" image, and this will fail when I submit any new changes.
In such way we are able to release 0.3.0-rc1 and at the same time test the changes you're proposing here (changes that make sense and I agree with).

Wait, may be there's no such chicken-egg, since we don't depend on lighthouse here.. ':D
testing locally and I will send a PR update if it works.

The technical difficulty with the lighthouse images does not exist, so it should be fine :) anyway we are talking on slack about merging this and do the follow up PR so we can cut RC1 now

My comments aren't critical - let's merge this and address in the follow-ups @mangelajo created.


player.getDuration() always returns Infinity on Safari native html5 player

Hi
we are trying to implement a set of custom player controls using Clappr's API
and we've noticed that while streaming a video in Safari(v8.0.8), the html5 player
always returns:
Infinity for player.getDuration();
and
1 for player.getCurrentTime();
making it impossible to calculate a seek value.
(even if we pause the video, player.core.getPlaybackType()
always returns live).
We also noticed that using Clappr's own controls we get the same
behavior. Wondering if you all had come across this limitation before
and/or possible a way around it ?
Thanks,
cc: @jfairley @lkkadiri

Hi @dviramontes
I'm using a Safari 8.0.8 and then I tried a mp4 file at http://cdn.clappr.io and it worked:

p.core.getPlaybackType()
< "vod"
p.core.getCurrentPlayback().getPlaybackType()
< "vod"
p.core.getCurrentPlayback().getCurrentTime()
< 4.237111111111111
p.core.getCurrentPlayback().getDuration()
< 36.44

So I changed the source to "http://www.streambox.fr/playlists/test_001/stream.m3u8" and it still works:

p.core.getCurrentPlayback().getPlaybackType()
< "vod"
p.core.getCurrentPlayback().getCurrentTime()
< 3.2469333333333332
p.core.getCurrentPlayback().getDuration()
< 510
p.core.getCurrentPlayback().getCurrentTime()
< 7.611636596
p.core.getCurrentPlayback().getCurrentTime()
< 9.134704286

I also tested with player.getCurrentTime() and I still couldn't get Infinity, although I used the instance p you should have the same behavior while using the right instance of the Clappr.
can you provide more detail so we can reproduce it ?

I tried using the above mentioned functions
p.core.getCurrentPlayback() but it seems that
getCurrentPlayback() is not longer defined (Using clappr 0.2.8).
but clappr does have something called getCurrentContainer()
so i tried that and I got:

by the way,  we are using a .m3u8 file as well and in our case
while are playing a playlist
p.core.getCurrentContainer().getPlaybackType()  returns live
which is correct
but when pause and play again, the .getPlaybackType()
still returns live
it's as if the playBackType property never gets updated, until it becomes
a vod file again (no longer streaming) then all the normal functionality
works.
To summarize,
while the playBackType is live  .getDuration, .getCurrentTime do not work as expected in Safari
while the playBackType is vod  .getDuration, .getCurrentTime work properly in all browsers we've tested (Firefox, Chrome, Safari)

This is part of the HTMLMediaElement interface on webkit: https://developer.apple.com/library/safari/documentation/AudioVideo/Reference/HTMLMediaElementClassReference/index.html#//apple_ref/javascript/instp/HTMLMediaElement/duration
Clappr wraps these calls to maintain the compatibility between browsers but since we use flashls on chrome and ffox, the result of the calls are not the same across all browsers. Flashls calculates the length in seconds of the playlist while webkit just returns Infinity and 1 for duration and currentTime. I'm afraid there's nothing we can do in this case. Also, I don't think it's possible to seek a live stream when using the video tag directly.

@dviramontes I believe @flavioribeiro is right. Since the beginning, DVR support is not available when using html5 video playback. There's no way to seek back on a live stream using the video tag directly, AFAIK.
In order to support DVR properly, you should use the hls playback provided by Clappr, which uses flashls.

Again thanks for the responses,
is there a way to force Safari to use flashls instead of the native player?
I was not able to find anything about that in the documentation.
Thanks

There's no official way to force using a playback directly, but you could just pass the HLS playback through the plugins parameter. The plugins passed through this parameter have a higher priority than the internal plugins.
var hlsPlayback = Clappr.HLS;
var playerElement = document.getElementById("player-wrapper");
var player = new Clappr.Player({
  source: 'http://mydomain.com/path/to/stream.m3u8',
  poster: 'http://clappr.io/poster.png',
  mute: true,
  height: 360,
  width: 640,
  plugins: { playback: [hlsPlayback] }
});
player.attachTo(playerElement);

Please let me know if this works for you.

thanks @towerz, that worked!
thanks @flavioribeiro for the info
closing issue

Changed the subject to make it easier to search for the solution.

Microsoft edge now supports hls natively as well. With our stream it appears to be broken through, random green pixelated areas, so maybe using flash for that would be good as well?

On 1 Sep 2015, at 17:58, Bruno Torres<EMAIL_ADDRESS>wrote:
Changed the subject to make it easier to search for the solution.
—
Reply to this email directly or view it on GitHub.

@tjenkinson good point, we need to test clappr with ms edge.. gotta create an issue for that

Same problems here. Tried Edge on XBox One and wasn't able to kick a live video back into DVR mode, even using manual seek calls

Apparently Safari and Edge don't support DVR streaming with Clappr.
@towerz proposed an unofficial solution, which is forcing the plugin hlsPlayback to load. But it didn't do for me.
This issue was closed last year. Is there any workaround by now?
Any official way of forcing Flash or HLS playback?
Versão 9.0.3 (11601.4.4)
Mac OS X El Capitain 10.11.3
Clappr 0.2.25
Tested on cdn.clappr.io

@thalleshmm is right
var playerElement = document.getElementById("player-wrapper");

var player = new Clappr.Player({
  source: 'http://www.streambox.fr/playlists/x36xhzz/x36xhzz.m3u8',
  baseUrl: '/latest',
  plugins: [Clappr.HLS],
  poster: 'http://clappr.io/poster.png',
  mute: true,
  height: 360,
  width: 640
});

player.attachTo(playerElement);

player.on(Clappr.Events.PLAYER_PAUSE, function(){
  alert(player.core.getCurrentPlayback().name)
})

https://github.com/clappr/clappr/issues/1013

#1013


[Sharing NG] getting permissions for drive via driveId doesn't work

Describe the bug
Permissions of a drive currently can't be fetched when using the driveId as itemId.
Steps to reproduce

Create a drive
Try fetching permissions for that drive via the drive's id: curl "https://localhost:9200/graph/v1beta1/drives/{drive-id}/items/{drive-id}/permissions" -u admin:admin -vk | jq

Expected behavior
The permissions for that drive should be returned by the server.
Actual behavior
The server complains about an invalid itemId. This probably happens because the driveId only consists of 2 parts and is missing the nodeId as third part. Appending the last part of the driveId as nodeId works. But consumer of the API shouldn't need to care about id formats.
cc @rhafer

Tested for the personal space. It works properly /graph/v1beta1/drives/storage-users-1$some-admin-user-id-0000-000000000000/items/storage-users-1$some-admin-user-id-0000-000000000000!some-admin-user-id-0000-000000000000/permissions
What format did you use?

Tested for the personal space. It works properly /graph/v1beta1/drives/storage-users-1$some-admin-user-id-0000-000000000000/items/storage-users-1$some-admin-user-id-0000-000000000000!some-admin-user-id-0000-000000000000/permissions What format did you use?

Yeah, this works. But the issue is about using:
-/graph/v1beta1/drives/storage-users-1$some-admin-user-id-0000-000000000000/items/storage-users-1$some-admin-user-id-0000-000000000000!some-admin-user-id-0000-000000000000/permissions`
+/graph/v1beta1/drives/storage-users-1$some-admin-user-id-0000-000000000000/items/storage-users-1$some-admin-user-id-0000-000000000000/permissions`

Permissions of a drive currently can't be fetched when using the driveId as itemId.

Yes a driveId is not itemId. So this is kind of expected I guess. Having that endpoint accept driveId as itemId shouldn't be to hard, however I think we would be better of implementing:
GET /graph/v1beta1/drives/{driveId}/root which basically returns the drives root item,  and /graph/v1beta1/drives/{driveId}/root/permissions which would return the permissions.

GET /graph/v1beta1/drives/{driveId}/root which basically returns the drives root item, and /graph/v1beta1/drives/{driveId}/root/permissions which would return the permissions.

So Web would need to make an extra call to /graph/v1beta1/drives/{driveId}/root just to retrieve the correct itemId?

Ralf is trying to make the item id obsolete for space roots.
The /root url part is basically an alias for the item id of the space root


Project Completion QA Checklist: Reprogrammed_Dendritic_Cells

Project UUID: 116965f3-f094-4769-9d28-ae675c1b569c
Project Title: Single cell profiling of human induced dendritic cells generated by direct reprogramming of embryonic fibroblasts
Project Short Name: Reprogrammed_Dendritic_Cells
Environment: Production
"Reprogrammed_Dendritic_Cells" needs to be re-ingested to correct linking of specimen to cell suspension. Go through Project Completion QA Checklist prior to re-ingest into production.

[x] Process QA of primary bundles
[ ] Metadata tsv validation: Run metadatatsv_validator.py

Process QA found the following issue:
There are 3 bundles associated with this project, 1 specimen and 2 cell lines. Each bundle should produce one empty_drops_result.csv from pipelines, but it is not displayed on browser with the correct associations.

Linking issue with this project is outlined in AUDR ticket HumanCellAtlas/hca-data-wrangling/issues/366

tsv validator outcome...

analysis_file.file_core.format:matrix not in ['bam', 'bai', 'csv', 'npy', 'npz', 'zarr']
analysis_file.file_core.format:unknown not in ['bam', 'bai', 'csv', 'npy', 'npz', 'zarr']
analysis_process.type.text:analysis entered but not analysis_process.type.ontology
analysis_protocol.type.text:analysis entered but not analysis_protocol.type.ontology
library_preparation_protocol.library_construction_method.ontology_label:10X v2 sequencing not in ["10X 5' v2 sequencing", "10x 3' v3 sequencing", "10X 3' v2 sequencing", "10X 3' v1 sequencing", 'Smart-seq', 'Smart-seq2', 'inDrop', 'Drop-seq', 'DroNc-seq', 'CITE-seq', 'MARS-seq']
process.start_time:2018.07.31 does not match pattern
process.start_time:2019.01.21 does not match pattern
sequence_file.file_core.format:fastq.gz not in ['fastq']
sequencing_protocol.10x.pooled_channels:4.0 does not match pattern
specimen_from_organism.organ_parts.ontology:UBERON:0001003 is not a child of specimen_from_organism.organ.ontology:UBERON:0000922

1-4 are known issues across the board. Nothing AUDR-able at the moment.
Similar situation with 8. https://github.com/HumanCellAtlas/hca-data-wrangling/issues/127
I have added the others to https://github.com/HumanCellAtlas/hca-data-wrangling/issues/366

Also noted:

'Differentiation protocol' tab lists 'Direct_reprogramming_protocol' as a protocol, but this protocol was not found in the Cell line nor Cell suspension tabs.
'HEF_Dissociation' protocol is described as 'Dissociation of human embryonic fibroblasts'. 'HEF_Dissociation' is listed as a protocol for Cell_line_1 and Cell_line_2, which are dendritic cells. This 'HEF_Dissociation' should only apply to dissociation of the fibroblasts.


special but accepted characters in method names break parsing

Hi,
The following code:
         public TestSteps create_a_range_from_$_to_$(LocalDate from, LocalDate to) {
            try {
                resultPeriod = new DateRange(from, to);
            } catch (Exception e) {
                thrown = e;
            }
            return this;
        }

gives me the following error:
[error] Expecting: one of these possible Token sequences:
[error]   1. ['[']
[error]   2. ['=']
[error]   3. [',']
[error]   4. [';']
[error]   5. [';']
[error]   6. ['(']
[error] but found: 'to_'

Using $ (and I guess other characters) are accepted in methods name. For the record, in this case it is a classic naming scheme used with JGiven.

Fixed in chevrotain-java

Check out version 0.0.6

thx


devDependencies updates

$ npm outdated
Package           Current  Wanted  Latest  Location
standard            8.6.0   8.6.0  11.0.0  meant
standard-version    2.4.0   2.4.0   4.3.0  meant
tap                 7.1.2   7.1.2  11.1.1  meant

Ahh ok. To support the old versions of Node.js for npm, I'd skip this release.


How could I use this

Hello, could you help me to use this lib? I read the documentation and couldn't get it to work. I currently have a project fully documented with dokka and it exports all of it in html files, used to build this site.
The documentation states which dependency I should add to include the functionality, but after that it just shows me a piece of code without telling me where to put it. Where exactly should I write the following?
var cacheDir: Path = Files.createTempDirectory("dokkaCache")
val runner: KotlindocInvoker = KotlindocInvokerImpl(cacheDir)

val outputDir = File("build/dokka").canonicalFile.toPath()
outputDir.toFile().deleteRecursively()
outputDir.toFile().mkdirs()

val rootDoc = runner.getRootDoc(
    listOf(
        File("widgets/src/main").canonicalFile.toPath(),
        File("kotlin-core/src/main/kotlin").canonicalFile.toPath()
    ),
    outputDir
) { inputStream -> IOStreamUtils.InputStreamPrinter(inputStream, null) }

rootDoc.packages.forEach { processPackage(it) }
rootDoc.classes.forEach { processClass(it) }

After writing this, which task should I call in gradle to generate the documentation in json? Do you have any example of how to add this to a project?
PS: I'm not using kotlin script for gradle, is it necessary?
Thank you in advance for the attention given to this

Kodiak is not a Gradle plugin, it's a JVM library. You'd add it to any normal JVM application and include the snippet above in that application. It was designed to not be part of the Gradle build because it's used in Orchid, which isn't itself tied to Gradle or any other build tool.


How to add existing amplify back end to the amplify front end?

** Which Category is your question related to? **
Auth, Storage, API
** What AWS Services are you utilizing? **
Cognito, AWS AppSync,
** Provide additional details e.g. code snippets **
I accidentally deleted my amplify frontend and I created a new one. How do I add again the existing amplify back end to the newly created amplify app?
I followed the steps on the backend tab

amplify init --appId ("ID OF YOUR NEW AMPLIFY APP").

Instead of amplify add CATEGORY HERE. I use amplify update CATEGORY HERE

Then amplify push
But when I check the amplify app on the AWS console there still no backend integrated to it.
Am I doing correct?
"aws-amplify": "^2.1.0",

@yvescoinpass which version of the CLI are you using?

Hello @nikhname, thanks for the time responding to my question. I am using<EMAIL_ADDRESS>

Try to follow these steps to first recover, and then add a new backend Env if you want to.

amplify pull --appId <your-project-appId> --envName <your-existing-backend-env>
amplify init and select the existing backend env if prompted

Now your amplify folder structure is fully setup, they you can add new backend env by
amplify env add

I got an error while trying to input my the name of the env
Cannot find backend environment master in Amplify Console app
I am really sure that the name of the env was master. I think the env was deleted too when I accedentally deleted the amplify app?

I think the issue was I deleted my the whole amplify project on AWS Console but I still have the existing amplify code base on my github repo.
So what I did was

Created a new amplify project on aws console.
Connect the existing repository on github
On my local machine I git pull the repo.
amplify init --appId ("ID OF YOUR NEW AMPLIFY APP").
Then. I use amplify update CATEGORY HERE
Then amplify push

That's it then the back-end is working again but it is not just showing on Aws Amplify Console Backend Environments tab tab

Same here, when adding an extra environment (add env) it shows up in the backend tab of the console, but the already existing environments are not showing.

Recovering the deleted Amplify Console project is not in the Amplify CLI's normal workflow.
But there's the following hack that triggers the CLI post push check that you can try:

On your local amplify project, run amplify env checkout <the-missing-endName-on-Console>
open the amplify-meta.json files in both the backend and #current-cloud-backend folder, make sure the providers.awscloudformation does not contain the field `AmplifyAppId", remove it if it's there.
open the team-provider-info.json file, make sure the  '.awscloudformation does not contain the fieldAmplifyAppId", remove it if it's there.
make an tiny dummy change in the backend, such as adding a space in in the template file of amplify/backend/storage
run amplify push

Works like a charm @UnleashedMind, thanks!!

its incredible have so many problems deploying a aws amplify app, and manage more than one env accross different aws accounts...


Rename dev dependency section to dependency-groups in pyproject.toml

A new PEP was recently (2024-10-10) accepted with the goal of standardizing dependency groups.
Soon after this, PDM has published a release that supports the new format proposed in the PEP.
Basically, instead of having a PDM-specific section [tool.pdm.dev-dependencies] in the pyproject.toml, we can now have a standardized [dependency-groups] section. It serves the same purpose and for our case the transition is trivial because we do not use any advanced PDM-specific feature of the [tool.pdm.dev-dependencies] section. We literally just have to rename the section header.
So this is very cool in my opinion.
Lastly, with this release, PDM has somehow changed its default behavior to not install the dependency groups of [tool.pdm.dev-dependencies] by default when running pdm install (before this, it would install everything). This change does not break our CI or our users, but it breaks the proposed installation steps provided in CONTRIBUTING.md: pdm install --frozen-lockfile is now not enough to have every dependency group installed.
With the new header name ([dependency-groups]), pdm install will install everything (unless asked otherwise), so this PR also fixes this issue.
An alternative would be to change pdm install --frozen-lockfile to pdm install --frozen-lockfile --dev in CONTRIBUTING.md.
I think the changes of PDM make sense and are improvements (not bugs), so I think it's good to follow the flow (and merge this PR).

Shouldn't we also change the README in this PR? Maybe we can add the two alternatives there.

You mean the CONTRIBUTING.md? There's no pdm-related step in the README I think.
Also, with this change, it becomes redundant to add --dev to pdm install, so there's not really two choices for contributors.

A changelog entry would be nice though, as this could maybe have some effect that we don't expect yet


✨ Add time ago (next) #14

Adds a widget that displays the time sent to the chat widget

@aguilaair Something I noticed, the gesture does not register if you tap on the text, only on the edges of the chat widget

@aguilaair Something I noticed, the gesture does not register if you tap on the text, only on the edges of the chat widget

Yeah, that's due to selectable: true, on MarkdownBody. We might want to disable it and do long tap to copy text

This is a blocker: https://www.loom.com/share/98702b41aa6c42a1b4ea79e7a736a442. I have no idea why it might be doing that in your PR...

This is a blocker: https://www.loom.com/share/98702b41aa6c42a1b4ea79e7a736a442. I have no idea why it might be doing that in your PR...
Just seeing it now, I have no idea. LOL

Does it happen on your machine too?

Oops didn't mean to close the PR 😅

Does it happen on your machine too?

Yes. I checked out to an earlier commit, it didn't happen

It looks like it is rebuilding constantly as it forgets its state and something strange is happenning with the width of the messages. I'll see if I can fugure it out...

Ok... it turns out that the culprit is selectable: true, if I set it to true I can't reproduce the issue. However, the moment I delete if (set it to false) the behaviour is easily reproducible...

Are you having a similar experience @Fiyiin ?

The commit I've done basically replaces the markdown library for a local version which uses Text.rich instead of RichText and the issue seems to be solved


Folder and Naming standards check using Project health check

Describe the feature
Currently naming standards are verified using dbt packages like https://dbt-labs.github.io/dbt-project-evaluator/0.8/rules/structure/#model-naming-conventions
however it does not provide instant feedback to developers the way an ide can
project health check can be enhanced to support standardization checks like prefix suffix
example
..stage/All models should be prefixed with STG_
..stage/PAYMENT/All models should be prefixed with STG_PMT
..mart/dimension/All models should be prefixed with DIM_
example
Top level folder structure must include stage, mart
Enhance Project Health check to add such capability
Describe alternatives you've considered
Using dbt project evaluator package - Does not provide instant feed back
Writing dbt macros - Not straight forward as graph node has to be looped for all objects
custom code analyzing manifest.json - will be outside ide
Who will benefit?
Most data project follows defined naming standards as dictated by their organization and they will benefitted.
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

This was included in the project governance feature release. You can find more information about it at https://docs.myaltimate.com/govern/governance


Disable projects

It would sometimes be helpful if projects could be temporary disabled instead of deleted.

:tada: This issue has been resolved in version 5.6.0 :tada:
The release is available on:

GitHub release
v5.6.0

Your semantic-release bot :package::rocket:


/tpll

If you get the x / z coords from the minecraft camera settings, and then you put the x / z coords in the reverse fromGeo, the toGeo function, you get a list of lat / lon coords you need in Google Earth.
The other way around you need the fromGeo, then put these coords into minecraft.
https://github.com/HakkaTjakka/project-obj

There is also a camera path mod, maybe that one you can get the coords into more easily.
I don't remember exactly what mod.
Example of output of java/python scrip usage in region creator:
Line 2239 : https://github.com/HakkaTjakka/MinecraftWorldEditor/blob/master/PACMAN_CUBERITE/src/viewer/viewer_my_loadobj.h


Support packages in subdirs

Addresses #157.
I didn't directly follow the last proposed approach, namely "do a sweep in the registry for all packages with the same repo". Instead, I left the subpackage specification to the caller by adding an optional subdir input. In this way, a user can add a separate configuration blob per subpackage that they want to register. (Bonus: this terminology plays nicely with the monorepo support currently in flight for Documenter.jl). While the "register all subpackages" is potentially a follow-up use-case, this "register specific subpackages" approach is one that would suit my team's monorepo needs, and seems lean enough that it doesn't require a huge overhaul of this codebase (as was noted might be required in previous conversation).
Code review notes:

In tagbot/action/changelog.py especially, it looks like there are a lot of changes. In practice, a certain subset of these are renaming rather than logic changes---I found that the version variable name was used for both the literal version of the package registered in the registry AND the value of the git tag added to a registered commit, so updated the latter to be named version_tag. (Previously, these were one and the same anyway; now, the clarity helped me understand how the two things interacted.)

fwiw, I struggled when adding tests due to unfamiliarity with this framework (both the mocking aspect and the Python aspect 😅). If folks have guidance for how to approach adding additional tests and/or suggestions for how to rewrite the ones I did add, I'm open!

Punch list:

[x] Understand where "version" means tag version (aka v3.2.1 or MySubpackage-v3.2.1, i.e. the version that the repo git tags know about) vs package version (3.2.1 regardless of top-level or subpackage, aka version that the registry knows/cares about)

[x] Rename version vars that refer to version tags rather than package versions accordingly, for clarity

[x] action: add new subdir input

[x] Plumb it through

[x] local: add new  subdir input (no plumbing needed, uses same code as action
[x] test - NOTE: I added some, but probably would benefit from more! See note.

[x] tests pass

[x] Update documentation
[x] lint pass
[x] open for review

⭐ amazing ⭐
I dunno when I'll be able to review this tbh, but I'll try to get to it within the month.

it would be great to see this merged

@christopher-dG, any thoughts on when you might have time to review this? (Or anyone else we could ping for review instead?)

I'll bring it up at SRE sync this week and see if I can put it on my schedule. If I can't find time to do it in the near future I agree with Eric, let's just send it and see what happens :)

I'll bring it up at SRE sync this week and see if I can put it on my schedule. If I can't find time to do it in the near future I agree with Eric, let's just send it and see what happens :)

Any luck?


Remove unused bin/init script, conf-quickstart reference

Deletes the unused examples/bin/init script and reference to the conf-quickstart directory, no longer used after https://github.com/apache/incubator-druid/pull/6126

@jon-wei could you backport this to 0.13.0-incubating?


Exporting as local model forces you to upload anyways.

It gives you the model data overflow window, and asks you to upload anyways.
Is the file size too big? Is there a way to change the file size limit? Mine was at 75KB

Yes it's 30 kB, after you have to upload it.


Hide the mode in the output of huh and add an argument to show all details

With details = "all" all information should be printed.
With details="key" only the most important details should be.
What that is exactly can still be figured out.

Also add storage.mode and use an argument lang = c("R", "S"). S will add mode and storage.mode to the output.


convert to go module

This PR converts graphql-go to a go module. Ideally, this would be paired with a release (perhaps a v0.x.y version) so that this package can be released periodically.

Thank you for your contribution


rotating sometimes takes very long to redisplay

may be same as issue #414
See http://MyBeacons.info/station
2,498 rows
2021-12-01T18:58:18-0500,
...
2021-12-02T09:21:08-0500,82.11,28.17,29.33,-63,0.156,0.04,1.012,2.936,5,2425
2021-12-02T09:21:08-0500,82.14,28.19,29.33,-60,0.16,0.04,1.004,2.936,5,2426
moto E4 Nougat
android 7.1.1 sprint version but non account wifi only
RAM 2GB
only other (apparent) app is CPUn monitor

Although is is not as obvious on a Samsung 9,
each time the phone is rotated, while showing a chart, takes seems to take a little longer.
Not sever but this may indicate a problem.

Maybe not. :-)


Add new staging environment

Need to work with PSE DevOps team.
(i think we'd need something like that)

[ ] Work with DevOps team to create a new production environment with a new AWS account
[ ] Setup CI/CD pipeline so main deploys to prod
[ ] Change DNS records to point to that environment
[ ] Deploy a new dev environment using current AWS account
[ ] Setup CI/CD pipeline so dev deploys to dev

Move to high if integration with p0tion

We can mark this issue as closed as we have the staging environment set up correctly and we have access to the logs @vplasencia @aguzmant103


tests: test multi-call logic

I noticed that src/bin/coreutils.rs had abysmal coverage. Turns out, we don't have any tests for most features of our "multi-call binary" logic!
This PR fixes that by adding a few tests, namely:

Calling with an unusual name
Calling with a non-UTF8-name
Calling with invalid arguments (thus exercising the top-level argument error handling)
Generating a manpage
Generating a completion

Thankfully, this revealed no bugs. Let's prevent regressions!
EDIT: From 19% to 68%: https://app.codecov.io/gh/uutils/coreutils/blob/BenWiederhake%2Fcoreutils-rs%3Adev-better-test-coverage/src%2Fbin%2Fcoreutils.rs

Changes since last push:

Rebased to current main
Changed the test with non-UTF-8 filename to require not just cfg(unix) but cfg(target_os = "linux"), and document the exact reason. Long story short, it would otherwise break in MacOS CI.

codecov/project Successful in 2s — 87.27% (+0.13%) compared to abdeead
nice


error when "crystal-lang.problems": "build"

when turn on this option it shows can't find file 'prelude'  in every file

Duplicate: https://github.com/crystal-lang-tools/vscode-crystal-lang/issues/74


fix bootstrap snippet

Why do you need to change breadcrumbs to breadcrumb class? Is this clashing with boostrap default class? In which case, maybe we can rename to breadcrumb-trail or similar?

Hi @piotrmurach :) this is Bootstrap default

Default it is then! Thanks ❤


Driver returning very strange readings.

Hi, I'm using the provided driver with pretty much the example usage. It works. I can read the firmware version (2.2), the device serial number. And I can apparantly read back the values. The problem  is the values it reads are impossible (over 3000 um/m3 in a home). As others have said, the PM2.5 and PM10 values are identical.
I (3302767) SPS30 Particulate Matter Sensor Task: measured values:
        3032.95 pm1.0
        3207.23 pm2.5
        3207.23 pm4.0
        3207.23 pm10.0
        20713.03 nc0.5
        24136.81 nc1.0
        24205.48 nc2.5
        24213.31 nc4.5
        24217.41 nc10.0
        typical particle size = 0.28

This in fact leads me to believe it is working. Or at least, sort of. I'm also using the SCD30, SHT30, SGP40 devices. And they all seem to be fine. They are using the same common libraries to manipulate bytes to floats. I'm working on an ESP32, which is little endian, but the conversion seems fine for the other sensors.
I don't know what a 'sensible' result should look like. Anyone care to post one and offer an opinion as to what might be causing this? Thanks.
I did a back of the envelope, based on the assumption that particles under 0.5um are all 0.28um diameter. 20,000 particles, based on the density of human skin dust (1500kg/m3), it gives 194 ug/m3. Which is still horrifically high, so I don't think I can trust that either.
additional info
I had a look at the read mesurement command with a scope. The command is W69, 03, 00. All good! The Read back is as follows: R69, 45, 8B, EF, 0E, 23, 39, 45, 93, 15, 0B, a8, etc... To be extra careful, I checked the integrity of the bytes by checking the CRC.
The payload for the first chunk is 0x45, 0x8B, 0x0E, 0x23. I knocked up a little snippet to see what it should be:
#include <stdio.h>
#include <stdint.h>

float bytesToFloat(uint8_t *bytes, int big_endian);

int main()
{
    #define b3 0x45
    #define b2 0x8B
    #define b1 0x0E
    #define b0 0x23

    unsigned char byte_array[] = { b3, b2, b1, b0 };
    float output = bytesToFloat(byte_array, 1);
    printf("Your float is %f.", output);

    return 0;
}

float bytesToFloat(uint8_t *bytes, int big_endian) {
    float f;
    uint8_t *f_ptr = (uint8_t *) &f;
    if (big_endian) {
        f_ptr[3] = bytes[0];
        f_ptr[2] = bytes[1];
        f_ptr[1] = bytes[2];
        f_ptr[0] = bytes[3];
    } else {
        f_ptr[3] = bytes[3];
        f_ptr[2] = bytes[2];
        f_ptr[1] = bytes[1];
        f_ptr[0] = bytes[0];
    }
    return f;
}

The output is
Your float is 4449.767090.
I've had a look at the following resource: single precision float and I'm confident that the interpretation of the bytes is correct. And 4449 is what I actually measured with this library. So, it looks like either I'm sitting inside a volcano, or there is something else wrong that's causing the device to read back crazy values... Sensirion, help me out. This is very odd indeed.
Very last edit
I thought I should completely rule out any misinterpretation of the float format since there was a handy means available in the integer16 data format. I set that with :
#define SPS_CMD_START_MEASUREMENT_ARG 0x0500
and got the exact same results.

What is your supply voltage? I've seen similar high values when using the SPS30 with at 3.3V instead of 5V, e.g. here: https://github.com/Sensirion/arduino-sps/issues/20

It turns out that the power supply (from PC USB) wasn't holding the 5V. It was fine until I added the extra load, and I didn't think to recheck it. Duh! Occam's razor.
Also, would be useful to add the following few lines of code to the code example. Since we aren't really giving it a long run while testing, this doesn't get done. Might help to see nice accurate results while we are in early dev stage.

    ESP_LOGI(TAG, "SPS30 Fan Manual Cleaning Started");
    ret = sps30_start_manual_fan_cleaning();
    if (ret < 0) {
        ESP_LOGE(TAG, "error in cleaning cycle!\n");
    }

    vTaskDelay(10 * 1000 / portTICK_RATE_MS);    /* wait 10s */


Not much happened after I installed. (Slight fps increase but not much.)

So I installed this thinking I would get some performance increases, which kinda helped but didn't really increase any fps well somewhat. I am using an i7-7700K paired with a GTX 1060 6GB but am only able to get 30fps on medium and 28-31fps on high which is much better before so thanks for that but I am under the impression that I should be getting 60+ fps yet I'm not, If you could suggest some things to try, I'm open to it.

I am still having to play on low with a 1060 6GB and Ryzen 5 3600. My FPS is 35-50. I think that despite the fantastic work Yamashi is doing, the game itself has severe issues that need to be fixed by the Devs.

I am still having to play on low with a 1060 6GB and Ryzen 5 3600. My FPS is 35-50. I think that despite the fantastic work Yamashi is doing, the game itself has severe issues that need to be fixed by the Devs.

Yea I agree with you, Yamashi did fantastic work, only the Devs of Cyberpunk 2077 need to fix all the bugs and optimise it. Well the good thing is that I haven’t crashed yet, used to crash after the prologue before Stanley’s cutscene thing but now I don’t so yea. I think CD Projekt Red are planning PC updates in January 2021 and Patch 2 in February 2021 which is alright but should have been sooner or even tested more vigorously but then again they were forced to release a clearly unoptimised game which impacted day one reviews.

For your specs 30fps is quite low but 60fps is not expected. The GTX 1060 is a 4 year old midrange card so I wouldn't expect a whole lot

I would try disabling async compute, it helps with older gpus


Description of project contains misspelled word

"Challange" should be "challenge."
Cheers,
Trevor Sullivan
https://trevorsullivan.net
https://twitter.com/pcgeek86

Thanks! We have rectified the description.


cleanup event observation

Codecov Report

Merging #74 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master    #74   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           6      6
  Lines         131    131
  Branches       15     15
=====================================
  Hits          131    131

Continue to review full report at Codecov.

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


Fix typescript error

#32

This is awesome, thanks a lot @chris--jones !

Oh, seems like the tests are failing, can you please update them accordingly with the new change?

Oh, seems like the tests are failing, can you please update them accordingly with the new change?

Oops, I'll see if I can fix it.
Ironically I couldn't get the tests to run due to that also throwing errors for me, but I see the changes needed in the snapshot.

Merged, thanks @chris--jones ! 🚀


perf: order pods by deleting first

Fixes #N/A
Description
This orders pods for disruption scheduling simulations so that we order pods that are on deleting nodes first. This ensures that our bin-packing will put pods from previous disruption actions on the same nodes that they've been scheduled to. This allows future disruption actions to rely on purely a new node for a replacement action.
This actually speeds up disruption performance depending on the flexibility of the budgets. With a tightly packed cluster with all nodes constantly expired, before this change, we could only expire one node per 30s (as we wait for the replacement to be initialized before being able to do another disruption action). After this, I was able to see at least 5 nodes being disrupted at a time with a budget of 100%.
How was this change tested?
Testing here
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Closing this as we don't need this at the moment.


Support sending to console without execution

Is your feature request related to a problem? Please describe.
fledge calls rstudioapi::sendToConsole(execute = FALSE), this is currently unsupported. Also, we could provide a command that sends to the console without execution, this can be useful when we want to edit the code before executing.
Describe the solution you'd like
I'd like the execute = FALSE variant supported, I think we need to call term.sendText(code, false) in this situation.
Describe alternatives you've considered
I have worked around in fledge for now, would be great to support this out of the box.
Additional context
Comment in original PR: https://github.com/Ikuyadeu/vscode-R/pull/535#issuecomment-792508390
VS Code API link: https://code.visualstudio.com/api/references/vscode-api#Terminal

As far as I can remember this is possible I just didn't do it because the terminal send call is wrapped in a couple of layers of stuff.
Felt a bit weird making so many changes for something I wasn't sure sure would ever get used.

Would you review a pull request?

@krlmlr PR very welcome!


"Open in Normal mode" link

When in presenter mode, the "Open in Normal mode" button assumes the slides are hosted at the root /. When the slides are hosted under a different path, e.g. https://mysite.com/myslides/, then the button's link will wrongly point to https://mysite.com/#0.
I'm on version 1.8.2.
PS: This is my first time using mdx-deck, so far I'm loving it, thanks for all your efforts!

This should work as expected in v2, but please feel free to reopen if you're still seeing issues


add middleware to accept formdata

add middleware to accept formdata

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 95.08%. Comparing base (4c9d44a) to head (64edc56).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #155   +/-   ##
=======================================
  Coverage   95.08%   95.08%
=======================================
  Files          28       28
  Lines        2948     2948
  Branches      395      395
=======================================
  Hits         2803     2803
  Misses        144      144
  Partials        1        1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Vue props throw incomprehensible error when passing variables starting with symbols

Version
2.5.17-beta.0
Reproduction link
https://codesandbox.io/s/r0lr534k94
Steps to reproduce
Open the console and see the error:
proxyConsole.js:72 [Vue warn]: Property or method "$_testMixin_testData" is not defined on the instance but referenced during render. Make sure that this property is reactive, either in the data option, or for class-based components, by initializing the property. See: https://vuejs.org/v2/guide/reactivity.html#Declaring-Reactive-Properties.

found in

---> <TestMixin> at /src/App.vue
       <Root>

What is expected?
It's expected for the prop to be defined
What is actually happening?
The prop is undefined if the variable contains symbols in the beginning

I am not completely sure if this is a bug or intended, since I think it is a bug I opened this issue, yet if this is intended the error shown should be giving more details, it took me some time to understand what was the error because it isn't clear just from the error message.

See https://vuejs.org/v2/api/#data:

Properties that start with _ or $ will not be proxied on the Vue instance because they may conflict with Vue’s internal properties and API methods. You will have to access them as vm.$data._property.

I understand that, yet I was following the style guide for mixins:
https://vuejs.org/v2/style-guide/#Private-property-names-essential
And still the error message is not comprehensible, the developers should be able to fix this problem without reading the whole docummentation, in other words I think a better error message would be more appropriate.


differing results between runs

First of all, thank you for sharing this nice implementation.  I've been experimenting with porting it to zig in hopes of using it in zig's universal headers project.  The aim of that project is to compress their distributed c headers and so quine-mccluskey has come up.
I've been randomly generating ones and checking the results of qm.simple(random_ones) against my port.  While doing so, i think I've found some type of problem with the results.  The following script shows either 28 or 29 for the length of the simplified implicants.  When run in a loop 100 times, the length is the same each 100 times but varies between runs - once again either 100 28s or 100 29s.
# tmp.py
import qm
q = qm.QuineMcCluskey()
simple = q.simplify([1,2,3,5,6,7,8,9,10,11,12,13,14,15,142,399,20,21,22,279,24,25,23,29,31,38,39,44,45,46,179,51,53,54,185,60,62,196,211,87,89,227,101,235,238,495,239,242,243,244,118,120,508,125])
print(len(simple))

$ python --version
Python 3.9.2
$ python tmp.py
29
$ python tmp.py
28

So I am not sure what to make of this.  I'm not sure if its a bug or just an inherent limitation.  I've been doing a some print debugging and noticed that the length of essential_implicants seems change between 33 and 34.  This is as far as I've looked so far and thought i would ask for advice before digging any further.  Any idea why this might be happening?

Here is a smaller example with fewer ones which also shows different results between runs - alternating between 5 and 6 (usually 6).
# tmp.py
import qm
q = qm.QuineMcCluskey()
simple = q.simplify([1,2,5,6,7,8,9,10,11,12,13,14,17])
print(len(simple),  simple)

$ python tmp.py
6 {'01-0-', '0011-', '0--10', '-0001', '010--', '0--01'}

$ python tmp.py
5 {'001-1', '-0001', '01-0-', '010--', '0--10'}

Hi. I just wanted to add that I have similar effects and that I can reproduce the effects on @travisstaloch's minimal example.
quine_mccluskey % python3 ./test.py
5 {'0--10', '01-0-', '001-1', '010--', '-0001'}
quine_mccluskey % python3 ./test.py
6 {'-0001', '0011-', '010--', '0--01', '01--0', '0--10'}

I'm doing some investigation of what the problem might be. I'm working with @travisstaloch's example.
First thing I have noticed is that the result of the call to __get_prime_implicants is in different order. This suggest that there is some inherent non-determinism but I'm not sure yet on where is it coming from.
I then sorted the results and in runs returning 28 and 29 the implicants are the same. This is not the case for essential_implicants. This means that the non-determinism is likely somewhere in the function __get_essential_implicants. Here are the differences between two sets of essential_implicants
>>> for x in a.union(b): print(x, x in a, x in b)
...
001111000 True True
110001111 True True
011110100 True True
0-0001110 True True
01110-011 True False
0000-100- True True
011000100 True True
000--0110 False True
000-10101 True True
00000--1- True True
010111001 True True
-11101111 True True
000001--- True True
001100101 True True
0001-11-0 True True
111111100 True True
-00010111 True True
011-10011 True True
01-110011 True True
00-011001 True True
0000-1-01 True True
0000101-- True True
0000--1-1 True True
011101-11 True True
0000-011- True False
001111101 True True
000-0110- True True
0111-0011 False True
0001--110 True True
00000---1 True True
01111001- True True
000-0011- True True
0-0110011 True True
01110111- True True
00-110110 True True
00-010111 True True

I have also tried hard-coding only one version of the prime_implicants and the result was also non-deterministic. Then I tried fixing the value of essential_implicants and the non-determinism disappeared.
After drilling down into the __get_prime_implicants  I discovered that the variables groups and ei_range are the same but this is not the case for ei. Here is again comparison of eis from both runs
>>> sorted(a)
['-00010111', '-11101111', '0-0001110', '0-0110011', '00-010111', '00-011001', '00-110110', '000--0110', '000-0011-', '000-0110-', '000-10101', '0000--1-1', '0000-1-01', '0000-100-', '00000---1', '00000--1-', '000001---', '0000101--', '0001--110', '0001-11-0', '001100101', '001111000', '001111101', '01-110011', '010111001', '011-10011', '011000100', '01110-011', '011101-11', '01110111-', '01111001-', '011110100', '110001111', '111111100']
>>> sorted(b)
['-00010111', '-11101111', '0-0001110', '0-0110011', '00-010111', '00-011001', '00-110110', '000-0011-', '000-0110-', '000-10101', '0000--1-1', '0000-1-01', '0000-100-', '00000---1', '00000--1-', '000001---', '0000101--', '0001--110', '0001-11-0', '001100101', '001111000', '001111101', '01-110011', '010111001', '011-10011', '011000100', '0111-0011', '011101-11', '01110111-', '01111001-', '011110100', '110001111', '111111100']

I added this print print(f"{t: >2} {g}, {not perms[g] <= ei_range}") into the second for-loop and shows that the order of the inner for-loop is different. Adding sorted to the inner for-loop fixed the non-determinism bug.
Original code: non-deterministic
for t in sorted(list(groups.keys()), reverse=True):
    for g in groups[t]:
        if not perms[g] <= ei_range:
            ei.add(g)
            ei_range |= perms[g]

Code with sort: deterministic
for t in sorted(list(groups.keys()), reverse=True):
    for g in sorted(groups[t]):
        if not perms[g] <= ei_range:
            ei.add(g)
            ei_range |= perms[g]

This is not a surprise as the sets have no order. Bad thing is that with the sort all the tests are now failing.

Wow. Thanks @tomas789 for your in-depth investigation.
Would be great if @tpircher-zz  could take a look at your investigation and the PR.


General info issue in openSUSE Leap 42

/usr/bin/lsb_release -ds;/bin/uname -r | sed -e 's/^"//' -e 's/"$//' command from general_info.sh return 2 lines:
"openSUSE Leap 42.1 (x86_64)"
4.1.12-1-default
we have extra quotes in json:
{ "OS": ""openSUSE Leap 42.1 (x86_64)" 4.1.12-1-default", ...
I suggest to change command to /usr/bin/lsb_release -ds | sed -e 's/^"//' -e 's/"$//';/bin/uname -r or something like this. It works in my case.

@CAI79 : The sed pipe should already be removing any double quotes generated by  /usr/bin/lsb_release -ds;/bin/uname -r.
For example, if we run the following in bash
$ echo "openSUSE Leap 42.1 (x86_64)" 4.1.12-1-default | sed -e 's/^"//'  -e 's/"$//'

It generates:
openSUSE Leap 42.1 (x86_64) 4.1.12-1-default

Can you please share the output of the following command from your server?
/usr/bin/lsb_release -ds

Please pull down latest commit for fix. General Info module was tested to work on openSUSE Leap 42.1.
You can see the changes here. Essentially a modified version of your recommendation.
Thanks for bringing up the issue.
Also, I had no idea that openSUSE Leap had such an awesome interface. Seriously considering switching.

Thanks!
Sorry for delay, it was a deep night and I gone to bed =)
As I can see, You don't need my server's output anymore...
New version shows info correctly.
P.S. openSUSE my favorite distro, glad You liked it =)


Packetization of v8 w/ PictureID and skip samples

Packetization of v8 w/ PictureID and skip samples
VP8 should include the picture ID for the sake of SLI when packetizing. The number of skipped samples during packetization needs to be factored as well.

will replace https://github.com/pion/rtp/pull/115


Tab UI position

Is it possible to put tab in header?  There are some space for it.

I try to change the top attribute of UI inline style, but I can't click tab after that operation.

Curious about this. Did you make it work then close the issue?

Trying to do the same and facing the same issue of tabs not being clickable when their position is moved to the top via CSS.
What is the fix?


APIGOV-24229 - updates to using apigee stats for central metrics

this will remain open until the issues with business insights is resolved


Upgrade to porqupine v2.0

Porquipine v2.0 has been released with performance improvements and should be used.

Implemented by #4 and is now released as 0.3.0 :tada:


.to_table() TypeError, possible bug

Hi!
I have problems with the newer versions of astroplan.
With 0.4 and astropy-3.2  I have no problem, but with 0.6 and 0.7.dev1234 the
priority_schedule.to_table() method drops the following error:
Traceback (most recent call last):
File "rc80_scheduler.py", line 447, in
out_table = priority_schedule.to_table()
File "/usr/local/lib/python3.7/site-packages/astroplan-0.7.dev1234-py3.7.egg/astroplan/scheduling.py", line 304, in to_table
u.Quantity(ra), u.Quantity(dec), config],
File "/usr/local/lib/python3.7/site-packages/astropy/units/quantity.py", line 387, in new
raise TypeError("The value must be a valid Python or "
TypeError: The value must be a valid Python or Numpy numeric type.
I use python3.7 and astropy-4.0.
I managed to circumvent the problem by changing the code in
/usr/local/lib/python3.7/site-packages/astroplan-0.7.dev1234-py3.7.egg/astroplan/scheduling.py
in line 303 to:
return Table([target_names, start_times, end_times, durations, ra, dec, config],
names=('target', 'start time (UTC)', 'end time (UTC)',
'duration (minutes)', 'ra', 'dec', 'configuration'))
It seems the ra,dec unit conversion (u.Quantity(ra), u.Quantity(dec)) caused the problem.

Yes I confirm this is a bug, it does not occur if the parameters show_transitions, show_unused are set to False, only if one of these is set to true.

Hi @Vincentbruga, I just went through the examples in the docs and it seems to work fine when I add the show_transitions=True and/or show_unused=True. The line mentioned by the OP has also already been changed.
If you are having problems can you post the code and version of python and astropy you are using? Thanks!

I'm having a similar problem in astropy version 0.8, python 3.10.7, astropy both 5.2.2 and 5.3.
Though I can see it's been changed in the github, locally line 303 still reads
return Table([target_names, start_times, end_times, durations,                       u.Quantity(ra), u.Quantity(dec), config],                      names=('target', 'start time (UTC)', 'end time (UTC)',                             'duration (minutes)', 'ra', 'dec', 'configuration'))
Pip says astroplan doesn't need an update, but I guess it's wrong. I ran the astroplan tests; the results are here if that's helpful in fingerprinting what release I actually have. Thanks!


DNS resolution happens only on startup

Hi again everyone.
I use a DNS service for my services (specifically Mesos-DNS, but it can be Consul or any other), therefore I use Prometheus' dns_sd_configs configuration option to give my services addresses
The problem is:
Prometheus resolves the SRV DNS addresses only on its startup ,so if Prometheus starts before the DNS server, it won't show all of these Targets. They won't even appear as "Down", but they'll just never appear until I'll restart Prometheus.
Version: 0.18.0

Can you try starting DNS first? We use DNS SD a lot and don't hit this. The
only difference I see is DNS being unavailable at startup, so the bug might
be triggered by that condition. What I would expect in that case is that
subsequent updates properly reflected.

It happens only when I start DNS after Prometheus.
Anyway, I'm trying to reproduce now with the latest version 0.19.1

OK, it seems like it doesn't reproduce with 0.19.1. Please close the issue and I'll report if it happens again. Thanks a lot!

OK, it seems like it doesn't reproduce with 0.19.1. I'm closing the issue and I'll report if it happens again. Thanks!


HDDS-10410. Avoid creating ChunkInfo.

What changes were proposed in this pull request?
In the container-service code, it often creates a ChunkInfo object from a proto in order to get length/name. It should get length/name directly from the proto.
What is the link to the Apache JIRA
HDDS-10410
How was this patch tested?
By existing tests.

Thanks @szetszwo for the patch, @ChenSammi for the review.

@ChenSammi , @adoroszlai , thanks a lot for reviewing this!


Doesn't explain how to install

I haven't been able to find how to install the plugins. I don't find the plugin file [plugin].aar nor the the config file plugin.gdap
Sorry, i'am not an adroid expert. So maybe with the modification of the build.gradle something should happened so i can use something from gdscript to use google libraries, but still i would't know how.
Sorry if i just dont find the documentation, but i have look all over the repository and havent find it.
Thanks for the reply and sorry for comunicating here but i dont know other way.

Pre-build files are in the release section,
https://github.com/FrogSquare/GDFirebase/releases/download/0.1/gdfirebase-0.1.zip

Alternatively you can use the script as well
https://gist.github.com/RameshRavone/5b00e9d098e1f7bf034aed4cafac8c80#file-gdfirebase

Thank you very much for the very fast response. I'll try it now.


Thoughts about security

Hello

I noticed in order to make an app work, the base/entry file is changed from the normal /public/index.php to a /bref.php in the root. I'm used to the normal web server (like nginx) approach - where the root folder is defined in the nginx conf to be something like /public, and then code, like /app, is outside of that. So /app would be a sibling of /public and can't be got to using a web request. So I wondered is that an issue where everything is in the same folder when served using bref?

Or is it not an issue as presumably there isn't an equivalent of try_files where a file will be served, so perhaps someone can't request /path/to/something.php to access settings etc.

Again, from a normal web server background, I would edit php.ini to lock it down a bit. Disabling file uploads, turning off allow_url_fopen, things not needed. Presumably the PHP bref uses is using the default ini ... perhaps this?
https://github.com/php/php-src/blob/master/php.ini-production
Is that an issue, security-wise?

Thanks.

Thanks for asking these questions!

This is not an issue. AWS lambda called via HTTP (i.e. it means via API Gateway) works by calling a single file: handler.js which calls bref.php.

As far as I know there is no way for HTTP clients to call another file. So we don't have the same problem as Nginx/Apache setups where we need a public/ folder.

Or is it not an issue as presumably there isn't an equivalent of try_files where a file will be served, so perhaps someone can't request /path/to/something.php to access settings etc.

That's correct.

This is the php.ini used by default by bref: https://github.com/mnapoli/bref/blob/master/template/php.ini

You can set flags through .bref.yml: https://github.com/mnapoli/bref#php-configuration
File uploads would be handled through your framework through PSR-7 but they are not implemented yet (https://github.com/mnapoli/bref/blob/4eaf0e49e16162a6457009dce9de6faa99763af1/src/Bridge/Psr7/RequestFactory.php#L44), so disabling them through php.ini wouldn't affect that. For the rest we use the default php.ini settings. If you see a specific issue feel free to mention it.

I see, thank you.
I am new to all this so that clarifies things a bit.
Can any PHP setting be set via that .bref.yml? I saw the documented ones and assumed it was limited to just those ones. If so, I could set them there.

Indeed you can set any flag, I've pushed a commit to improve the documentation to reflect that.
Thanks for the feedback!


Fix #1721

Q
A

Bug fix?
[ ]

New feature?
[ ]

New sample?
[x]

Related issues?
fixes #X, partially #Y, mentioned in #Z

What's in this Pull Request?
This PR will fix #1721
Guidance

You can delete this section when you are submitting the pull request.
Please update this PR information accordingly. We'll use this as part of our release notes in monthly communications.
Please target your PR to dev branch.

Hi @nsoeth,
Thanks for this PR!
Regarding the addition of $top query operation, I'd suggest to make it available as optional because it depends on use case and maybe it would not fit for everyone to load 5000 items at once.
Since the DynamicForm lookup field relies on ListItemPicker control, and in order to be available as a field override prop for the DynamicForm, here are the different files to update according to me:

SPService.ts
IListItemPieckerProps
ListItemPicker (ListItemPickercontrol doc will have to be updated as there will be a new prop available)
IDynamicFieldProps
DynamicField

Like this, the developer will be free to set the number of items he wants to get 🙂
A suggestion of prop name could be itemsQueryCountLimit or ODataTopCount for example but feel free to suggest!
Let me know if something's not clear or if you need help.

Hi @michaelmaillot ,
Thanks for your suggestions, I updated the PR.
Kind regards,
Niels

Hi @nsoeth,
Are you still working on this one? Do you need any kind of help?

Hi @michaelmaillot
Sorry, lot of things to do the last few months but I updated the PR according to your review.

Merged manually, thank you!


questions about the function 'prepare_test_data_semseg( )'

Hi, Thank you for your good works.
I noticed that you in the function 'prepare_test_data_semseg( )', it run the scripts 'prepare_data/collect_indoor3d_data.py' and 'prepare_data/gen_indoor3d_h5.py' to transform the raw dataset 'Stanford3dDataset_v1.2_Aligned_Version' to 'indoor3d_sem_seg_hdf5_data_test'.
However, as descripted in the pointnet repo https://github.com/charlesq34/pointnet/tree/master/sem_seg#dataset, the two scripts will transforms the raw data to the training dataset which is sampled 4096 points in each block and is not suitable for testing which requires the all points but not the sampled ones.

Actually, if you look into the code in charlesq34/pointnet/sem_seg carefully, you will find charlesq34 does sample 4096 points in each block (1m x 1m x height of the room) to test the network. The main difference between training and testing set is that each block in training set overlaps with its neighbor blocks in 0.5m, i.e. all blocks in a given room are cropped with stride=0.5m, while each block in testing set are not overlap.

Thank your for your prompt reply.
I agreed with your opinions about the difference between the training and testing dataset after I look into the scripts 'gen_indoor3d_h5.py' and 'batch_inference.py'.
Do you think this means that Charlesq34 disobey the promise that he made in the paper which says 'At test time, we test on all the points' ?

It's a good question haha😁 and I suggest you ask Charlesq34 to confirm.
In my opinion, Charlesq34's original intention is to test his model on all points in testing set to meet the testing standard. But as you know the model is trained with 4096 points per block so it may not work well with arbitrary number of input points.
You can also find points of each shape in testing set are sampled under fixed number in classification and part segmentation task. It's a common choice to sample fixed number of points per shape to test model.

Hhhh thank you. I would share my opinions with you once I got new understanding about this issue.


Update nmrshll/gphotos-uploader-cli

As per https://github.com/nmrshll/gphotos-uploader-cli/issues/59, nmrshll/gphotos-uploader-cli upgraded some core libraries. Can you update the docker package?

Will do as soon as I find some time available :)

Waiting for https://github.com/nmrshll/gphotos-uploader-cli/issues/53 so I can properly update gphotos-uploader-cli and test it thoroughly...

You'll also need to wait for https://github.com/nmrshll/gphotos-uploader-cli/issues/64. gphotos-uploader-cli is rather broken at the moment :(

@avidrissman  Are you running the version with your modifications?

@beed2112 You must have me mistaken for a different poster; I made no modifications.

@avidrissman There's a new build in the oven (should be ready in 10mins or so) which includes a few workarounds for both issues described above. Please let me know how that works out for you :)

Comment when the new build is ready, and I'll give it a try. Thanks!

Comment when the new build is ready, and I'll give it a try. Thanks!

It's been ready for more than a day now 😄

I tried installing it earlier and fetched the “latest” tag. I just went to the docker page and see that there are three new versions (“arm32v6-latest”, “arm64v8-latest”, and “amd64-latest”) from yesterday, and there is indeed a “latest” tag from 5 months ago!
If grabbing the “latest” tag is the wrong thing to do (as it seems to be), can you remove that tag so that people don’t accidentally use it? Have I been using a 5-months-old version all this time?

If grabbing the “latest” tag is the wrong thing to do (as it seems to be)

It's not, it's the correct one.
The latest tag is supposed to be a multi-architecture tag which will pick the correct architecture for your device (one of arm32v6, arm64v8 or amd64). If you know the correct architecture for your device, you can pick that tag instead.
As for latest, I need to fix it, for some reason it wasn't updated automatically.

The latest tag should now be fixed.
To be sure, pull rfgamaral/gphotos-uploader:latest and then do docker inspect rfgamaral/gphotos-uploader:latest | grep 2019-06-28T11:20:49Z. If you didn't get any output, it didn't work. Please let me know if that's the case.

I’m doing this on a Synology, and the UI collapsed the two rows of “latest” and “amd64-latest” into one. It’s also confirmed by the commandline.

and the UI collapsed the two rows of “latest” and “amd64-latest”

I also have a Synology and I have no idea what you meant with this 😞
I'm also not sure if your problem is fixed or not, based on your response, can you please clarify?

There used to be two lines in the Synology UI, one with “latest” and one with “amd64-latest”. After the update of yours, now there’s one line with both tags, which indicates that they’re the same.

I also ran the command you requested, for which you said:

If you didn't get any output, it didn't work.

But I did get output, so I’m confirming it worked that way.

Thank you for the clarification :)

FYI, every time it runs I see an error in the log about not having an auth token. I can authorize and authorize, and each time I auth it works once, and then continues to fail auth. The old version didn’t do that for me.

FYI, every time it runs I see an error in the log about not having an auth token. I can authorize and authorize, and each time I auth it works once, and then continues to fail auth. The old version didn’t do that for me.

Can you please open a new issue for that and describe it the best you can, please?

@avidrissman Please follow #8 for the issue above :)

I will comment on that issue.
To be clear, the old version stayed authenticated for me. The new version does not.


Accept sites state when adding sites

Ops wants to start with sites in Down state and then rely on SSB to switch them to Normal.
This way we can keep onlySSB=False, such that it does not shutdown sites if SSB gets in trouble.
Tested in my VM. @ticoann I'll check and create patches missing for 1.0.8 branch and then we go for a new tag

Beginning pylint and unit tests.
See https://cmssdt.cern.ch/jenkins/job/DMWM-PR-test/256/ for details

No pylint warnings for pull request 6128:

No changes to unit tests for pull request 6128