Can we add sm, md, lg & large to .no-gutters?

I find when I'm making websites that I'll often want .no-gutters only on small screens, to keep a 3 column grid on small devices. This is dependent on the design of course, but I find it useful.
Can we look at adding .no-gutters-sm, .no-gutters-md, .no-gutters-lg and .no-gutters-xl to use this Bootstrap-specific property with breakpoints?
Current: https://getbootstrap.com/docs/4.0/layout/grid/#no-gutters
Notation with breakpoints: https://getbootstrap.com/docs/4.0/utilities/spacing/#notation

Technically, Bootstrap does not need the .no-gutters class.  You could just use the spacing classes.  But I know what you're saying, it's easier to just have to type into one class attribute.

Duplicate of #26249

Technically, Bootstrap does not need the .no-gutters class. You could just use the spacing classes. But I know what you're saying... it's easier to just type into one class attribute.

@LarryAzevedo, I've used your solution before in most cases. But we have a case where we want to keep gutters on most screens, but then only on sm hide the gutters. Instead of using a media query and setting margin-left: 0; and margin-right: 0; I'd like to use a Bootstrap class.

Yes! Please add this :)

Jumping on the bandwagon. I also don't see how spacing classes can solve the problem with the needed negative margin on the row element as there is not css class available putting a negative margin on an element.

@pepebe You may want to look closer at the documentation: https://getbootstrap.com/docs/4.4/utilities/spacing/#negative-margin

@ffoodd Totally missed that one. Thanks!
.mt-n1 {
  margin-top: -0.25rem !important;
}

u could use

p3=1rem


Local inference example...  not pointing to the correct Ollama endpoint

Hi, I'm trying to use Ollama for local inference but I cant seem to get the code point to the correct endpoint...
I'm  using :
    assistant = VoicePipelineAgent(
        vad=ctx.proc.userdata["vad"],
        stt=deepgram.STT(),
        #llm=openai.LLM(model="gpt-4o-mini"),   !!commented out!!!
        llm = openai.LLM.with_ollama(model="llama3.1",base_url="http://xyz.io:11023/api"),
        tts=openai.TTS(),
        chat_ctx=initial_ctx,
    )

Which points the request to /api/chat/completions on my local server... I can see the request coming through !
BUT THATS NOT THE CORRECT ENDPOINT !
It should be /api/chat but I can't seem to point to that !!!
It seems like the base_url is always appended with /chat/completions ??
Frustrating this one is !
Any pointers would be greatly appreciated ! This software is awesome !

   assistant = VoicePipelineAgent(
        vad=ctx.proc.userdata["vad"],
        stt=deepgram.STT(),
        #llm=openai.LLM(model="gpt-4o-mini"), !!commented out!!!
        llm = openai.LLM.with_ollama(model="llama3.1",base_url="http://xyz:11023/v1"),
        tts=openai.TTS(),
        chat_ctx=initial_ctx,
    )

This is the correct way to request the ollama server -->
The request is sent to /v1/chat/completions , /chat/completions is appended in the openAI code...
Resource that helped me with this: https://ollama.com/blog/openai-compatibility


⚠ Minecraft has degraded performance

In 160826c, Minecraft (https://www.minecraft.net) experienced degraded performance:

HTTP code: 200
Response time: 1269 ms

Resolved: Minecraft performance has improved in f7f517c.


Typos

"nvdia-smi" should read "nvidia-smi". Also, "import Chainer" should be "import chainer" (and all "import X" phrases on the page should really be in tty font).

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

ID: f322439a-d89a-201a-2581-d4d794ea694d
Version Independent ID: 20b98ef0-2396-86bb-bec1-87fa99502ef1
Content: Deep Learning and AI frameworks - Azure
Content Source: articles/machine-learning/data-science-virtual-machine/dsvm-deep-learning-ai-frameworks.md
Service: machine-learning
GitHub Login: @gopitk
Microsoft Alias: gokuma

@gopitk
Thanks for the feedback! We are currently investigating and will update you shortly.

Thank you @sennendoko
We've fixed the typos!
#please-close if user's issue has been addressed.

@sennendoko We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Adding Syosset CSD, primarily for Syosset HS

Syosset Senior High School is part of the wider Syosset Central School District. Even though it is a high school, it does offer a lot of  Higher Level Education Courses, including but not limited to, A.P. courses, SUPA courses, and many more.
a URL of a page on the official website where a long-term (>1 year) IT related course is offered by the school:
https://www.syossetschools.org/Page/659
(Also here is the Curriculum guide website, where you can see all the different Courses Syosset Senior High School has to offer):
https://www.syossetschools.org/domain/283
(Found a better document that satisfies the requirement)
https://www.syossetschools.org/cms/lib/NY50000216/Centricity/Domain/291/SHS Online Learning Plan.pdf

@Chocolate-Jeff First stage of verification passed, official domain is syossetschools.org as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@philipto Sorry for not replying earlier but thanks, lmk if you need any more info, or info that will speed up the process and I will obtain it and send it to you ASAP

@Chocolate-Jeff Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Support receive task message templates

Just like Message Events, Receive Tasks should also be configurable via element templates. Most of the infrastructure is already there, but test coverage is missing. You cannot create a buggy template accidentally as it's not allowed via JSON schema.
### Tasks
- [x] I can create a Receive Task template
- [x] I can configure bpmn:Message#property binding for Receive Task
- [x] I can configure bpmn:Message#zeebe:subscription#property binding for Receive Task
- [x] I can read documentation on receive task templating

Documentation is coming via https://github.com/camunda/camunda-docs/pull/2950


Feature/mc 9537

Added Functionality for a copy of a DataClass to be saved with a new Label, a save as function.
To do this add the json [copyLabel : ] to the post request. The change includes a new command object that can be extended to add the ability to alter other data in the copy if we need to.

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


Wrong values of constants in SearchFilters

The constants of the file xivapi-php/src/XIVAPI/Api/SearchFilters.php seem to be wrong.
It is actually about the constants LESS_THAN and LESS_THAN_OR_EQUAL_TO.
    const EQUAL_TO                  = '=';
    const GREATER_THAN              = '>';
    const GREATER_THAN_OR_EQUAL_TO  = '>=';
    const LESS_THAN                 = '>';
    const LESS_THAN_OR_EQUAL_TO     = '>=';

Fixed ty!


Please elaborate how this is different from gist by GitHub.

I am amazed by this neat little website, but not sure how it is different from gist.

Smaller size limit
Can configure file types in the URL such as https://bpa.st/+pytb+python
Not sure how the APIs vary but Pinnwand has several options
Pastes are immutable (other than removal)

(consider these pluses or minuses as you see fit :])
Gists are public as well afaik, even the private ones.  Private just means they aren't findable by searching, which is also true of Pinnwand.


Release 7.2.0 (OVDB-149)

Signed-off-by: Nick Avramoussis<EMAIL_ADDRESS>Planning to release 9th December
https://jira.aswf.io/browse/OVDB-149
https://github.com/AcademySoftwareFoundation/openvdb-website/pull/31

Looks good. Did you draft a new GitHub release? Perhaps it's not visible to me if you created it?
https://github.com/AcademySoftwareFoundation/openvdb/releases
Also - any notes to add to https://github.com/AcademySoftwareFoundation/openvdb/blob/master/tsc/process/release.md for the new process of releasing AX?

Also - any notes to add to https://github.com/AcademySoftwareFoundation/openvdb/blob/master/tsc/process/release.md for the new process of releasing AX?

None! though some CMake instructions are slightly outdated, I will update this


Upgrade gulp to version 5.0.0

This is a major version bump, and the changelog at https://github.com/gulpjs/gulp/releases/tag/v5.0.0 indicates one breaking change that impacts us, namely that streams are now by default interpreted/transformed to UTF-8 encoding. This breaks gulp.src calls that work on binary files such as images or CMaps, but is fortunately easy to fix for us by disabling re-encoding for all gulp.src calls (see https://github.com/gulpjs/gulp/issues/2764#issuecomment-2063415792 for more information). This restores the previous behavior of copying the files as-is without Gulp performing any transformations to it, which is what we want because Gulp is only used for bundling and we make sure that the source files have the right encoding.
Note 1: I have, similar to previous PRs that touched the Gulpfile or its dependencies, run all commands with Gulp 5 to verify that they still work. Moreover, if output artifacts have been produced by the command I have compared the output with the Gulp 4 output using diff -r <old> <new> and verified that the diffs were either empty (indicating bit-by-bit equality) or only contained expected changes (such as timestamps being stored in the output of e.g. JSDoc that change after every run). I haven't found any meaningful changes in any of the output that should change behavior.
Note 2: This upgrade also fixes four vulnerabilities reported by NPM. Before this patch npm audit reported 39 vulnerabilities (15 moderate, 24 high), but after this patch it reports 35 vulnerabilities (15 moderate, 20 high).
Fixes #17922.

/botio-linux preview

/botio-linux preview

The [13:07:51] Unsupported gulp version log in the preview output above is caused by the bots using an old globally-installed Gulp version instead of the new locally-installed Gulp version. I'll create a PR to fix that on the bots, which after deployment should make this work again.

The bot fix is deployed, so let's try this again:
/botio-linux preview

/botio test

/botio makeref (to test this change in the bot scripts)


ResponseLogger prints raw request on cancellation

On this line of code, we log the result of calling toString on the request:
https://github.com/http4s/http4s/blob/a7e2fc108de12f7b111d688d33288c20f6a5a085/server/src/main/scala/org/http4s/server/middleware/ResponseLogger.scala#L70
This is dangerous, as it may end up logging sensitive information, ignoring the logHeaders, logBody, and redactHeadersWhen options.
In our project, we've solved this by using Logger.logMessage to log the request in this case, re-using the same options as for responses and introducing a constraint on the request type, A <: Message[F].
However, this may not be a good solution for getting this patched upstream, since it technically breaks the API (introducing a new type constraint), and re-uses the response logging configuration for requests.

Ouch. Yeah, we need to get this fixed ASAP.

So if I'm reading the code right, the default will redact these headers, and your problem is that you have other sensitive headers?
val SensitiveHeaders = Set(
  "Authorization".ci,
  "Cookie".ci,
  "Set-Cookie".ci
)

This is tricky.  Constraining A to be a Message[F] defeats the polymorphism of the middleware.  We could pattern match on A and if it's a request, do something safer.  But then we'd need to handle ContextRequest.  And who's to say that people haven't invented their own A with a Request?
The only right answer here might be to be much more careful about what we put in .toString, since we can't pass the sensitive headers filter reliably in this context.

Also, much less gravely, while we're at it, canceled is one l. :smile:

So if I'm reading the code right, the default will redact these headers, and your problem is that you have other sensitive headers?

Well, we actually disable header logHeaders altogether, but we do have additional sensitive headers, yes.

Fixed by #3488.


cannot import name 'is_safe_url'

File "C:\Users\Admin\AppData\Local\Programs\Python\Python311\Lib\site-packages\currencies\urls.py", line 4, in
from currencies.views import set_currency
File "C:\Users\Admin\AppData\Local\Programs\Python\Python311\Lib\site-packages\currencies\views.py", line 4, in
from django.utils.http import is_safe_url
ImportError: cannot import name 'is_safe_url' from 'django.utils.http' (C:\Users\Admin\AppData\Local\Programs\Python\Python311\Lib\site-packages\django\utils\http.py)

You are probably using a too old version of the package.

Had the same issue while using django 4.2.14
To avoid open redirects for security reseasons, I installed is_safe_url as a stand alone package
pip install is_safe_url
Then,
from is_safe_url import is_safe_url
implementation
if is_safe_url(next_url, allowed_hosts={request.get_host()}):
return redirect(next_url)
else:
return redirect('home')

Django has renamed is_safe_url to url_has_allowed_host_and_scheme in Django 3.0 and is_safe_url has been removed in Django 4.0. Django-two-factor-auth supports Django 4.2 and later and thus imports url_has_allowed_host_and_scheme  and not is_safe_url. If you get an import error for is_safe_url, this is likely a problem  in your own code or another package and this can be fixed by changing is_safe_url to url_has_allowed_host_and_scheme.

Thanks
On Sun, 20 Oct 2024, 16:49 Jeroen Dekkers, @.***> wrote:

Django has renamed is_safe_url to url_has_allowed_host_and_scheme in
Django 3.0 and is_safe_url has been removed in Django 4.0.
Django-two-factor-auth supports Django 4.2 and later and thus imports
url_has_allowed_host_and_scheme and not is_safe_url. If you get an import
error for is_safe_url, this is likely a problem in your own code or
another package and this can be fixed by changing is_safe_url to
url_has_allowed_host_and_scheme.
—
Reply to this email directly, view it on GitHub
https://github.com/jazzband/django-two-factor-auth/issues/714#issuecomment-2424971901,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATXJ273OO4LOUQFXTGR6EI3Z4OYF3AVCNFSM6AAAAABQHOQTLWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRUHE3TCOJQGE
.
You are receiving this because you commented.Message ID:
@.***>


<EMAIL_ADDRESS>fails to autoupdate

Bug Report
Package Name: virtualbox-with-extension-pack-np
Current Behaviour
Checkver.ps1 fails to update manifest
Expected Behaviour
When running checkver.ps1 I expect the manifest to update to latest version, 7.1.2
Additional context/output
PS C:\Users\xxxxx\scoop\buckets\nonportable\bucket> ..\bin\checkver.ps1 -App virtualbox-with-extension-pack-np

virtualbox-with-extension-pack-np: 7.1.2 (scoop version is 7.0.20) autoupdate available

PS C:\Users\xxxxx\scoop\buckets\nonportable\bucket> ..\bin\checkver.ps1 -App virtualbox-with-extension-pack-np -Update -Force

Forcing autoupdate!
Autoupdating virtualbox-with-extension-pack-np
Searching hash for VirtualBox-7.1.2-164945-Win.exe in https://www.virtualbox.org/download/hashes/7.1.2/SHA256SUMS
Found: 95be216f865155f64cf461b712462405e25c600bd92b873d89ac43e8b564c15c using Extract Mode
Searching hash for Oracle_VM_VirtualBox_Extension_Pack-7.1.2.vbox-extpack in https://www.virtualbox.org/download/hashes/7.1.2/SHA256SUMS
Could not find hash in https://www.virtualbox.org/download/hashes/7.1.2/SHA256SUMS
Downloading Oracle_VM_VirtualBox_Extension_Pack-7.1.2.vbox-extpack to compute hashes!
The remote server returned an error: (404) Not Found.
URL https://download.virtualbox.org/virtualbox/7.1.2/Oracle_VM_VirtualBox_Extension_Pack-7.1.2.vbox-extpack is not valid
ERROR Could not update virtualbox-with-extension-pack-np, hash for Oracle_VM_VirtualBox_Extension_Pack-7.1.2.vbox-extpack failed!

Possible Solution
Oracle has changed the download name of for the 7.1.2 Extension Pack.
Change autoupdate url to https://download.virtualbox.org/virtualbox/$matchHead/Oracle_VirtualBox_Extension_Pack-$matchHead.vbox-extpack
System details
Windows version: 11
OS architecture: 64bit
PowerShell version: 7.4.5
Additional software: [(optional) e.g. ConEmu, Git]
Scoop Configuration

{
  "last_update": "2024-10-06T17:55:30.5398217-04:00",
  "scoop_branch": "master",
  "scoop_repo": "https://github.com/ScoopInstaller/Scoop",
  "debug": false,
  "aria2-warning-enabled": false
}

Working on PR.


example: add hello-world ingress case

What type of PR is this?

/kind documentation
What this PR does / why we need it:
Sub of #9
Which issue(s) this PR fixes:
Fixes
Does this PR introduce a user-facing change?:

xref: https://github.com/kubernetes-sigs/ingress2gateway/issues/21

@Xunzhuo let us know if you want to follow up on these, for now I'm going to close out in favor of more recent PRs.


Fix Hash for RussellBanks.Komac.Nightly

Pull request has been created with Komac v1.9.1 :rocket:
CC @russellbanks
Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/114862&drop=dogfoodAlpha

@wingetbot run


feat: only do autofmt on main

for issue: https://github.com/TBD54566975/ftl/issues/1075
Not sure of best way to test - I may try it on another branch perhaps?
edit: tested it by having it push to this branch as if it was main, and it did what I expected. Doesn't need the FTL_AUTOFIX_TOKEN anymore, and won't trigger a rebuild (flip side of that is if it does have a rebuild, there won't be a build run against it - is that suitable @alecthomas ?)

@alecthomas this may be what you mean - runs only on main. I tested it on this branch first.

Roger that! Let's give it a shot!
Want to add some formatting that will be changed on merge so we can test?

Thanks @michaelneale!!


Steps for integrating CoreUI Pro Vue with Laravel

I'm desperately attempting to integrate the CoreUI Pro admin theme with Laravel but haven't the slightest clue as to how to accomplish this. If anyone could help or get me started that would be incredibly helpful.

I am in the same situation as you. Have you managed to do it?

Thank you ;)


Unable to sweep coins from lnd wallet

Background
I want to sweep my balance of 185 877 031 sats from the lnd wallet to another wallet. However, when I issue the sendcoins command with the flag --sweepall, Ind throws an 'incorrect usage' error with the message flag provided but not defined: -sweepall
Your environment

version of lnd : lncli version 0.5.2-beta commit=v0.5.2-beta
which operating system : Linux 4.15.0-43-generic #46-Ubuntu SMP
version of bitcoind: Bitcoin Core Daemon version v0.17.1
running on a scaleway x86-64 VPS

Steps to reproduce
$ lncli --network=testnet sendcoins --sweepall --addr tb1qv9rvjrxl69yztu0t4xmyxzakszj44883ug687h
Incorrect Usage.

NAME:
   lncli sendcoins - Send bitcoin on-chain to an address.

USAGE:
   lncli sendcoins [command options] addr amt

CATEGORY:
   On-chain

DESCRIPTION:

  Send amt coins in satoshis to the BASE58 encoded bitcoin address addr.

  Fees used when sending the transaction can be specified via the --conf_target, or
  --sat_per_byte optional flags.

  Positional arguments and flags can be used interchangeably but not at the same time!

OPTIONS:
   --addr value          the BASE58 encoded bitcoin address to send coins to on-chain
   --amt value           the number of bitcoin denominated in satoshis to send (default: 0)
   --conf_target value   (optional) the number of blocks that the transaction *should* confirm in, will     be used for fee estimation (default: 0)
   --sat_per_byte value  (optional) a manual fee expressed in sat/byte that should be used when crafting the transaction (default: 0)

[lncli] flag provided but not defined: -sweepall

Expected behaviour
lnd should sweep my wallet balance to the destination address
Actual behaviour
lnd throws up an 'incorrect usage' error

@hex17or as the error message indicates, --sweepall is not available in 0.5.2. this capability is in master and will be available in the coming 0.6 release


Use agent as name where it fits

TL;DR
Use agent as name where it fits
Type

[x] Bug Fix
[ ] Feature
[ ] Plugin

Are all requirements met?

[x] Code completed
[ ] Smoke tested
[ ] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
This is some leftover of #368 where we should have aligned the naming better. Note that this PR has no breaking change.
Tracking Issue
https://github.com/flyteorg/flyte/issues/3823
Follow-up issue
NA

@pingsutw Wanna merge this?


Issues with installing azureingressprohibitedtarget crd on Azure k8s v1.16.9

Describe the bug
After upgrading our Azure k8s cluster to v1.16.9 (current version) we are unable to use the existing helm crd for AzureIngressProhibitedTargets due to various errors.

The graph initially failed to apply due to the api version being set to v1beta1. This was changed back to v1 based on online recommendations

Next the problem appeared to be to do with the fact that a crd_hook was specified in the existing code that was not supported in helm v3. This was removed as a template and added into a /crd folder in the chart.

The format of the crd was then reported as incorrect with the following error:

Error: failed to install CRD crds/azureingressprohibitedtarget.yaml: CustomResourceDefinition.apiextnsions.k8s.io "azureingressprohibitedtargets.appgw.ingress.k8s.io" is invalid: [spec.versions: Invald value: []apiextensions.CustomResourceDefinitionVersion(nil): must have exactly one version marked s storage version, status.storedVersions: Invalid value: []string(nil): must have at least one store version, metadata.annotations[api-approved.kubernetes.io]: Required value: protected groups must hae approval

After following an online example (https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/) all the errors were cleared up except

'protected groups must have approval annotation "api-approved.kubernetes.io", see https://github.com/kubernetes/enhancements/pull/1111'
This appears to be a problem due to the use of the ingress.k8s.io namespace. This is preventing us deploying AzureIngressProhibitedTargets to our cluster. Can you advise if there is a workaround or if we will need to wait until the next release?

Cluster k8s version: v1.16.9
Api version: v1
Helm version: v1.20
Chart version: v1.20

To Reproduce:
Attempt to install crd for AzureIngressProhibitedTargets on versions above

Hi @gavinwakeley1 , may I ask the AGIC version you used? we have a fix to install CRD via helm3 in 1.2.0-rc2

Hi @3quanfeng , yes indeed it is 1.2.0-rc3 so that would be brilliant - thank you!
Typo on my 'versions' list at the end of my post - corrected now.

Hello, please can anyone help with this issue? It is causing us issues with using this in our production environment.
Thank you for any assistance you can give.
Kind Regards,
Gavin


Should C# ReadCsv have skipTypeInference:true as default?

I believe F# skips as default, but C# does not.

We have a bit odd design here, but the defaults are the same.
In C#, the parameter is skipTypeInference and the default is false. In F#, the parameter is inferTypes and the default is true. So, the parameters represent opposite things, but the defaults mean the same thing.
I think the reason is that skipTypeInference is an optional parameter and it will always default to false (so to make the default true, we had to invert the name of the parameter...). That said, we could use inferTypes of type Nullable<bool> and that would work equally well.
We can certainly change this - but it would be a breaking change (probably a good one for consistency though).

Oh, I see ... the inconsistent API threw me off... my fault for not reading the parameter names closely. I'd be in favor of a breaking change here.

+1 for doing a breaking change


Conflict information is not available

We can use something like Toast
https://ionicframework.com/docs/api/toast
Blocked by offix listener issue

Is this fixed? Need it for the demo


bamboo service - Does not support branch names with /

https://github.com/github/github-services/blob/master/lib/services/bamboo.rb#L22
Seems this could be handled better than just anything after the last / .
I'll have to get familiar with how to test this before I make a commit trying to fix.

I believe replacing this line with
commit_branch = ref.sub(/\Arefs\/(heads|tags)\//, '')

which matches functionality of "ref_name" function from push_helpers.rb is all that is needed for a fix.
Can anyone confirm?

The change was merged and I just tested on production. Fixed! Thanks


Create 10-pg_clean.en.md

译文

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


ssh: Permit root login by pubkey only

This is useful in the context of hashbang/admin-tools#12 as it gives admins access to the root account in case of emergency.
I already deployed SSH keys for root (the admins') while testing hashbang/admin-tools#12

This looks good to me.

Deployed, sshd config reloaded and tested.


View with column definition including " AS <alias" (in SELECT) not parsed properly by converter

Describe the bug
We have a view whose definition looks something like the following:
CREATE VIEW <schema>.<view> AS
SELECT DISTINCT
  MAX(RPT_DTTM) AS FILTER_RPT_DTTM
  ,'yes' as CRRNT_RPT_DTTM
FROM <tablename>
WHERE <expr>
UNION
<more horribleness>

I believe the regular expression parsing this view is greedy and treats the second AS keyword as the beginning of the view definition, thus eliding SELECT and everything that comes immediately after.
I suspect the problem is in the greediness of this regexp: https://github.com/littleK0i/SnowDDL/blame/c7ca3c48a533340bc88ac690b6664840005093ec/snowddl/converter/view.py#L11
I'm still fiddling around, but my suspicions are pretty strong at this point.
Expected behavior
Full text of the view definition appears in the yaml generated by snowddl-convert.
Attach log
(Later, if necessary.)
Attach YAML config (if applicable)
(No minimal reproduction at this time. Maybe later.)

Wish we could find a way to extract VIEW text without relying on parsing. Maybe new REST API endpoints can do that, I'll take a look at some point.
Otherwise the only way to do it reliably is to introduce actual SQL parsing.

Yeah, I hear you. Was thinking of that StackOverflow post on parsing HTML with regexps. (And, yes, parsing SQL is Hard.)

Ok, so, for what it's worth, making the following change to regexp solved my one particular issue for this one particular view:
view_text_re = compile(r"^.*?\sas(\n|\s)+(.*)$", DOTALL)

(Changed * operator to *?.)
No telling what other damage I've caused. :)

Upd in 0.36.0: applied your change, regexp looking for  as keyword is now non-greedy.
Naturally, it may still fail if  as is being used somewhere in the comments for individual columns or view itself.
I'll experiment with pyparsing soon and see if we can introduce more permanent solution.

Fwiw, pyparsing docs:
ignore(expr) - function to specify parse expression to be ignored while matching defined patterns; can be called repeatedly to specify multiple expressions; useful to specify patterns of comment syntax, for example

Per note on #149 , this can be closed.


corrected output text below input box

Main typo was “your data are looking healthy”
fixed overall error readability

Hi @VirenMohindra,
Thanks @VirenMohindra  for taking the time to help out on Chartbuilder!

"Data are" is not a typo, but an intentional stylistic choice based on "data" being the plural of "datum"
The current phrasing of the column chart warning is also how we'd like to keep it.
Changing "to" into "into" does perhaps make that phrase clearer.

If you modify this request to only include that final change we'd be happy to merge

I've modified the request to include the final change only. Let me know if this works out.


Minimal API Versioning - Endpoint not found

As per description in https://fast-endpoints.com/docs/api-versioning#mark-endpoint-with-a-version, we tried to enable versioning in existing minimal API.
In Configuration we put
app.UseFastEndpoints(c =>
{
    c.Versioning.Prefix = "v";
    c.Versioning.DefaultVersion = 1;
});

And in Endpoint Configuration
public override void Configure()
    {
       // Before Versioning
        Post("v1/accounts/{@id}/status", x => new {x.Id});
        // After Versioning
        Post("accounts/{@id}/status", x => new {x.Id});
        Version(1);
    }

After enabling Versioning, I get 404 when I hit
POST http://localhost:5000/v1/accounts/1/status
I don't know where I am failing..

If I remove versioning, Endpoint works.

try POSTing to http://localhost:5000/accounts/1/status/v1 because by default the version is appended to the url. you should setup swagger to see what the available endpoint URLs are.

@dj-nitehawk   We want to use http://localhost:5000/v1/accounts/1/status  ,  we can not change our url...

Is this possible? if it is not is should be there , as in  MVC Route we can set version in  route templete

see SuffixedVersion at the bottom of the page you linked above.


COCO annotation labels incorrect when downloaded

My actions before raising this issue

[x] Read/searched the docs
[x] Searched past issues

COCO annotation labels are incorrect when downloaded.
For example if I have two annotation labels , "visible Orange" and "hidden Orange". Each are applied to every image once each. When downloaded in COCO format I will get a images that only have "visible orange" and images that only have "hidden orange"
Expected Behaviour

When I download in COCO format, it should have the same label to image as for CVAT format.
Current Behaviour

Annotation label is change when downloaded in COCO format
Steps to Reproduce (for bugs)

Create data set with atleast two labels (mine has two for masks and one skeleton)
Download an annotated dataset that has both annotations on the images
Upload or look at the annotation .json file to see the mistake

Context

Greatly as I need my annotations in COCO format for one of my work projects.
Your Environment

Git hash commit (git log -1):
commit https://github.com/opencv/cvat/commit/6acab035f2ad2cb9501d814c9c5c38e49bf8e628

Docker version docker version (e.g. Docker 17.0.05):
Client:
Version: 20.10.12
Server:
Engine:
Version: 20.10.12

Operating System and version (e.g. Linux, Windows, MacOS):
Linux-20.04

I have attached two images below showing the difference between CVAT annotation upload and COCO annotation
COCO_annotation_error.zip

@jitaxis , I will close the issue. If you can provide more information how to reproduce the issue on our side, feel free to reopen.


Add feder proto

Signed-off-by: cai.zhang<EMAIL_ADDRESS>Co-author: zhenshan.cao<EMAIL_ADDRESS>issue: #118

/approve
/lgtm


Release to PyPI using Trusted Publishing

PyPI has introduced "Trusted Publishers", a method to release files from CI using OIDC and generated, short-lived tokens, rather than long-lived tokens on the developer's own machine. This is both safer, and makes releasing easier and more convenient.
https://docs.pypi.org/trusted-publishers/
This PR adds a workflow to deploy to PyPI for new GitHub releases.
It also deploys to Test PyPI on merges to main, to make sure the release machinery is well oiled.
I've set up the PyPIs with this:

https://test.pypi.org/manage/project/flake8-implicit-str-concat/settings/publishing/
https://pypi.org/manage/project/flake8-implicit-str-concat/settings/publishing/

PEP 740 ("Index support for digital attestations") introduces signatures which links the PyPI package to the GitHub repo, and helps users verify the source and authenticity of packages. This is only available with Trusted Publishing.
PyPI is still implementing support, but we can already start using it, which should also help them test out.

https://peps.python.org/pep-0740/
https://github.com/pypa/gh-action-pypi-publish#generating-and-uploading-attestations
https://github.com/pypi/warehouse/issues/15871

All we need to do to enable this is add:
        with:
          attestations: true

Merging, let's see if this works on main to Test PyPI, and if so, I'll also do a regular release. It's been a while since the last one in Feb 2023.

Merging, let's see if this works on main to Test PyPI

Hmm, didn't work:

https://github.com/flake8-implicit-str-concat/flake8-implicit-str-concat/actions/runs/11427092599

Uploading distributions to https://test.pypi.org/legacy/
Uploading flake8_implicit_str_concat-0.4.0-py3-none-any.whl
WARNING  Error during upload. Retry with the --verbose option for more details.
ERROR    HTTPError: 400 Bad Request from https://test.pypi.org/legacy/
         Bad Request

It'll be because there's already a file named that:
https://test.pypi.org/project/flake8-implicit-str-concat/0.4.0/#files
I'll make a fix, we'll need a way to change the version for dev versions, and https://github.com/ofek/hatch-vcs works well for that.

After merging https://github.com/flake8-implicit-str-concat/flake8-implicit-str-concat/pull/60, it now successfully uploaded 🚀

https://github.com/flake8-implicit-str-concat/flake8-implicit-str-concat/actions/runs/11427297782/job/31791265407
https://test.pypi.org/project/flake8-implicit-str-concat/0.4.1.dev47/

Will next do a full release.

Will next do a full release.

Success!

https://github.com/flake8-implicit-str-concat/flake8-implicit-str-concat/actions/runs/11427319392
https://github.com/flake8-implicit-str-concat/flake8-implicit-str-concat/releases/tag/0.5.0
https://pypi.org/project/flake8-implicit-str-concat/0.5.0/


Implement Recursive Proofs Scheme in Bootloader

Description
This task focuses on understanding the functioning of bootloaders and managing tasks within a scheduler. The primary objective is to implement a recursive proofs scheme. The implementation will be carried out in two main phases:

Cairo Verifier Integration: The first step involves integrating the Cairo verifier into our system. This will lay the groundwork for handling recursive proofs and ensuring that the system can effectively verify each step of the recursion.

Progressive Recursion Implementation: After the Cairo verifier is in place, the next phase is to develop and integrate the recursion mechanism.

Goals

Gain a deeper understanding of bootloader functionality.
Efficiently manage tasks within the scheduler.
Integrate the Cairo verifier as the foundation for recursive proofs.

cairo-lang/src/starkware/cairo/bootloaders/simple_bootloader/utils.py is missing
waiting for SW response

DONE


Support referencing accessories by mac address

When IP is changed we shouldn't need to reconfigure.
The plugin can also hint all the discovered device on startup so people can edit the config accordingly.

Added in 1.0.0 - Please read the release notes https://github.com/lprhodes/homebridge-broadlink-rm/releases/tag/1.0.0

@clkao the wrong MAC address was being returned, this has been fixed in 1.1.19 (check out the release notes if it doesn't work)


Removed fallback authentication logic and modified ValidateMptPAT.

Packages impacted by this PR
@azure/microsoft-playwright-testing
Issues associated with this PR
Remove fallback logic in authentication
Improved validation of Pat token.
Describe the problem that is addressed by this PR
Earlier, we used to have fallback logic in authentication. Entra -> PAT
or PAT -> Entra. This PR removes the fallback logic.

API change check
API changes are not detected in this pull request.


vector_unproject

Unproject a vector from a view plane

This one is interesting, since going from 2D to 3D is not unique. Would unproject return a line or would we specify a distance from the camera, too, so we can actually find a unique 3D point?

See https://github.com/pygfx/pygfx/blob/6642d1cd907f068cc7e7ca4cc4e42c4763e76c81/pygfx/linalg/vector3.py#L189

Yes, see #6 :+1:


Fix EraCast Certificate instance

Changelog
- description: |
    Fix EraCast Certificate instance. There is no straightforward way to handle the different certificates that are allowed/disallowed across an era boundary due to the use of type families in the Certificate era data type. Therefore currently we don't allow casting to other eras.
  # no-api-changes: the API has not changed
  # compatible: the API has changed but is non-breaking
  # breaking: the API has changed in a breaking way
  compatibility: breaking
  # feature: the change implements a new feature in the API
  # bugfix: the change fixes a bug in the API
  # test: the change fixes modifies tests
  # maintenance: the change involves something other than the API
  # If more than one is applicable, it may be put into a list.
  type: bugfix

Context
Addititional context for the PR goes here.
If the PR fixes a particular issue please provide a
link
to the issue.
Checklist

[ ] Commit sequence broadly makes sense and commits have useful messages
[ ] The change log section in the PR description has been filled in
[ ] New tests are added if needed and existing tests are updated.  These may include:

golden tests
property tests
roundtrip tests

[ ] The version bounds in .cabal files are updated
[ ] CI passes. See note on CI.  The following CI checks are required:

[ ] Code is linted with hlint.  See .github/workflows/check-hlint.yml to get the hlint version
[ ] Code is formatted with stylish-haskell.  See .github/workflows/stylish-haskell.yml to get the stylish-haskell version
[ ] Code builds on Linux, MacOS and Windows for ghc-8.10.7 and ghc-9.2.7

[ ] The changelog section in the PR is updated to describe the change
[ ] Self-reviewed the diff

Note on CI
If your PR is from a fork, the necessary CI jobs won't trigger automatically for security reasons.
You will need to get someone with write privileges.  Please contact IOG node developers to do this
for you.

Subsumed by #170


setup.cfg: set version using platformdirs.version

otherwise the generated PKG-INFO would contain a version of "0.0.0"
Signed-off-by: Kefu Chai<EMAIL_ADDRESS>

This is only true if you don't satisfy the build dependencies, but then you're violating Python packaging requirements.

thank you Bernát for the quick review. yeah, i think i just failed to install setuptools_scm beforehands.

@tchaikov How did you install platformdirs? I'd like to better understand situations in which build dependencies are unmet.

@ofek hello Ofek! sorry for the text wall. tl;dr: it's story of a lazy RPM packager.
i am trying to package python-virtualenv v20.6.0 on RHEL9. and it turns out it requires python3-platformdirs to build. so i moved on to python-platformdirs. fortunately, this package was already packaged [0] by fedora. but unfortunately, the fedora packaging maintainer uses the pyproject_buildrequires[1] rpm macro to collect the build dependencies of python-platformdirs package in the RPM spec file.  this macro does its job[2] just fine. but i ran into two issues:

the package offering this macro is not yet packaged in EPEL repo.
one of the dependencies,python3-setuptools_scm, is not available in EPEL, and it depends on mercurial!

instead of diving into this rabbit hole, i cowardly manually translated the build dependencies defined by pyproject.toml to the BuildRequires lines in rpm spec, and dropped python3-setuptools_scm in hope that i could get away without it..
and i built platformdirs using
python3 setup.py  bdist_wheel

this was what i got using %py3_build_wheel RPM macro.
and installed it using
python3 -m pip install -I dist/platformdirs-*-py3-none-any.whl \
  --root /home/kchai/rpmbuild/BUILDROOT/platformdirs-2.2.0-1.x86_64 --strip-file-prefix /home/kchai/rpmbuild/BUILDROOT/platformdirs-2.2.0-1.x86_64 --no-deps

this was what i got using '%py3_install_wheel'. i guess it was --no-deps which ignores the required dependencies. this macro is defined by https://src.fedoraproject.org/rpms/python-rpm-macros/blob/rawhide/f/macros.python3#_56 . guess the author of the macro believe that maintainers should do the right thing instead of cutting the corner like me =(..

[0] https://src.fedoraproject.org/rpms/pyproject-rpm-macros/branches?branchname=rawhide
[1] https://src.fedoraproject.org/rpms/python-platformdirs/blob/rawhide/f/python-platformdirs.spec#_32
[2] https://src.fedoraproject.org/rpms/pyproject-rpm-macros/blob/rawhide/f/pyproject_buildrequires.py#_184

its unfortunate that setuptools_scm is packaged incorrectly
mercurial is by no means a hard dependency

ahh, it is not a hard dependency. see https://src.fedoraproject.org/rpms/python-setuptools_scm/blob/rawhide/f/python-setuptools_scm.spec#_18
i will try again with "tests" disabled.


chat: fix for embeds overriding formatted links.

Fixes #2161
If a user specifically formats some text as a link we should just show that, even if it's a link to embed-able content.

lgtm, will this have an underline to show it's a link?

yep


Add the Subjects method

Codecov Report

Merging #3 into master will increase coverage by 5.82%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master       #3      +/-   ##
==========================================
+ Coverage      75%   80.82%   +5.82%
==========================================
  Files           2        2
  Lines          56       73      +17
==========================================
+ Hits           42       59      +17
  Misses         13       13
  Partials        1        1

Impacted Files
Coverage Δ

client.go
100% <100%> (ø)
:arrow_up:

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 3a77ed6...074dcfc. Read the comment docs.


Error when build to Android studio

When I download q-municate-android-master 2.0 and build to android studio, have a issues :
Error:(41, 0) Could not find property 'prodAppID' on project ':Q-municate_app'.
Open File
How to can I fix it ?

please, see our documentation for running Q-municate app by link http://quickblox.com/developers/Q-municate#Q-municate_Android

the easy fix is to create a new android studio project, then copy the properties(gradle.properties) file in your Q-municate folder, edit the file as followed:
#QB credentials
prodAppID="00000"
prodAuthKey="xxxxxxxxxxxx"
prodAuthSecret="xxxxxxxxxxxx"
prodFacebookAppID="xxxxxxxxxxxxx"
prodPushRegistrationAppID="xxxxxxxxxxxxx"
replace the "xxxxxx" by your infos.

@JuniorVouma , Sir! I did the above on my app but my friend requests goes to q-municate not my app.
But the users created are available on quickblox account of the app.
Help out pliz

@ckibuchi hi! you've to go to your quickblox app then settings "allow to retrieve all users" then all you need to do is to search by name in the search button.     for the friend request, go to quicblox, users, settings then set the path as written in that section.

@tatanka987
I did follow exactly from the  http://quickblox.com/developers/Q-municate#Q-municate_Android but
still this issue can't solve it yet. I think most of the developer have all same issues.
Please provide more specific answer for this issues. Thanks


FIX: made the site responsive and updated the landing page

Add responsiveness to the site
Update the Hamburger Icon on all the pages
Update the Landing Page
Chips link added in card page
Drawer hiding bug in drawer component
Add menu button on drawer page
Add a note for sliders support on slider page

Screenshots
Landing Page

Installation Page when Sidebar is Closed

Installation Page when Sidebar is Open

Some feedback I have Vishal
* In card page the, the next page button i.e `chips` page button is missing the `href` attribute

* Since the `drawer` class hides your sidenavigation this affects your `drawer` component and hides the drawer in drawer component as well, in the drawer page

* Hamburger icon in drawer page is missing

* I am using Chrome, and I dont think the slider styles support it

* Card with badge (product card), the badge text overflows badge in mobile view

* Landing page has horizontal scroll

* The `+` and `-` buttons on badge can have `pointer` cursor as it will tell the user its a clickable item

* This last suggestion is my personal opinion that whenever a user clicks on a modal, they should be allowed to close it by clicking outside of it too. (Your modal works good too, this is just a suggestion)

* Also a `pointer` cursor on the backdrop (which opens in mobile view when clicked on the hambuger icon) would be great

Other than this your website looks great 🔥

Chips link fixed in Cards page
Drawer Components visibility issue fixed in drawer page
Hamburger icon added in Drawer page
Slider styling is the part of component library, hence I'll have to fix that in that repo. I'll do this later or maybe in Version 2.0
Card Badge and + - buttons are the part of component library, hence I'll have to fix that in that repo. It would get fixed when I add responsiveness to the components also. As of now components are not responsive.
cursor: pointer; on backdrop when sidebar is visible is added.

These were some great suggestions @kart-c. Thank You for a great review!


Generator hangs indefinitely if enum value is named "_"

If I create an enum like the following, the compiler will hang until I terminate the process:
enum HttpMethod {
  _      = 0;
  GET    = 1;
  POST   = 2;
  PUT    = 3;
  PATCH  = 4;
  DELETE = 5;
}

Thanks for reporting.
This is the function that loops: https://github.com/google/protobuf.dart/blob/9cf05f6e9f53d88b4b6c1f6f1accec09bcd5cca7/protoc_plugin/lib/names.dart#L84-L99
We need to remove or replace the _ somehow as _ as prefix makes the generated Dart identifier private, but when the name is just _ I'm not what to convert it to.
Documentation of the quoted function above says _ is not a valid protobuf field name, but I can't find where the lexical syntax for identifiers is specified.
@sigurdm do you have any ideas on this?

I think we may want to abort compilation when an identifier is just _.

Yeah - I think aborting is the right choice.

Documentation of the quoted function above says _ is not a valid protobuf field name, but I can't find where the lexical syntax for identifiers is specified.

I asked this to protobuf team. There isn't a spec that specifies .proto file lexical syntax so we need to look at the code.
This is the lexer code for identifiers: https://github.com/protocolbuffers/protobuf/blob/8d3a7327606b115dda871be54c8b8cb66d41ff90/src/google/protobuf/io/tokenizer.cc#L675-L677
It starts with one "Letter", followed by zero or more "Alphanumeric", and "Letter" allows underscores: https://github.com/protocolbuffers/protobuf/blob/8d3a7327606b115dda871be54c8b8cb66d41ff90/src/google/protobuf/io/tokenizer.cc#L138-L139
So _ is a valid field name.

I think: https://developers.google.com/protocol-buffers/docs/reference/proto2-spec#letters_and_digits and https://developers.google.com/protocol-buffers/docs/reference/proto2-spec#identifiers actually specifies the lexical syntax for field names. from that it is clear to me that '_' is not a letter (I think that is what the comment refers to).
The actual implementation differs from this.
Perhaps we should file a bug to update the documentation (as it is probably too late to break this now).
To fix our implementation I think we could have a special case that turns a single _ into '$_' or something other.


Query builder crash when selecting non-existent field in subquery

Steps to reproduce
Run a query with a subquery selecting a non-existent field.
await db.user.select("id", {
  posts: user => user.posts.select("id", "no_such_field"),
})

Expected
The SQL query runs, and fails with database error: column post.no_such_field does not exist.
This is exactly what happens when selecting that field in the root query:
await db.post.select("id", "no_such_field") // proper SQL generated, crashes in Postgres

Alternatively (although less preferred), the query builder crashes with meaningful error, something like "no_such_field is not a field or relation in PostTable".
Actual result
The query builder fails to generate SQL and crashes with cryptic error:
file:///Users/is/test/node_modules/.pnpm/pqb@0.23.5/node_modules/pqb/dist/index.mjs:1844
  return isSubQuery && column.data.name ? setColumnData(column, "name", void 0) : column;
                              ^

TypeError: Cannot read properties of undefined (reading 'data')
    at maybeUnNameColumn (file:///Users/is/test/node_modules/.pnpm/pqb@0.23.5/node_modules/pqb/src/queryMethods/select.ts:493:51)
    at addColumnToShapeFromSelect (file:///Users/is/test/node_modules/.pnpm/pqb@0.23.5/node_modules/pqb/src/queryMethods/select.ts:487:26)
    at getShapeFromSelect (file:///Users/is/test/node_modules/.pnpm/pqb@0.23.5/node_modules/pqb/src/queryMethods/select.ts:423:9)
    at queryFrom (file:///Users/is/test/node_modules/.pnpm/pqb@0.23.5/node_modules/pqb/src/queryMethods/from.ts:114:20)
    at queryWrap (file:///Users/is/test/node_modules/.pnpm/pqb@0.23.5/node_modules/pqb/src/queryMethods/queryMethods.utils.ts:12:5)
    at queryJson (file:///Users/is/test/node_modules/.pnpm/pqb@0.23.5/node_modules/pqb/src/queryMethods/json.utils.ts:16:13)
    at Db.json (file:///Users/is/test/node_modules/.pnpm/pqb@0.23.5/node_modules/pqb/src/queryMethods/json.ts:328:12)
    at processSelectArg (file:///Users/is/test/node_modules/.pnpm/pqb@0.23.5/node_modules/pqb/src/queryMethods/select.ts:302:25)
    at file:///Users/is/test/node_modules/.pnpm/pqb@0.23.5/node_modules/pqb/src/queryMethods/select.ts:517:41
    at Array.map (<anonymous>)

Complete reproduction

Complete reproduction
import process from "node:process"

import { createBaseTable, orchidORM, testTransaction } from "orchid-orm"

const BaseTable = createBaseTable()

class UserTable extends BaseTable {
  readonly table = "user"

  columns = this.setColumns(t => ({
    id: t.identity().primaryKey(),
  }))

  relations = {
    posts: this.hasMany(() => PostTable, {
      required: true,
      columns: ["id"],
      references: ["user_id"],
    }),
  }
}

class PostTable extends BaseTable {
  readonly table = "post"

  columns = this.setColumns(t => ({
    id: t.identity().primaryKey(),
    user_id: t.integer().foreignKey("user", "id").index(),
  }))
}

const db = orchidORM(
  { databaseURL: process.env.DATABASE_URL, log: true },
  {
    user: UserTable,
    post: PostTable,
  },
)

await testTransaction.start(db)

await db.$query`
  create table "user" (
    id serial primary key
  );
  create table post (
    id serial primary key,
    user_id integer not null
  );
`

// SELECT "post"."id", "post"."no_such_field" FROM "post"
// Error: column user.no_such_field does not exist
await db.post.select("id", "no_such_field")

// Doesn't prepare any SQL, crashes with meaningless error
await db.user.select("id", {
  posts: user => user.posts.select("id", "no_such_field"),
})

await testTransaction.close(db)

I appreciate your complete reproduction, though in this case, it's excessive.
It was crashing because of an unknown column before it could execute the query, that's why it was a different error.
I added ? to where the error happens and now it will execute the query and will be a clear db error saying there is no such column, published this fix.
Why wasn't it caught up by TS error?
In general, for the sake of micro-optimizations, when something can be caught by a TS error, I'm trying to keep as few JS checks in the logic as possible. That means there might be more cases like this one, but all should be covered with type-system so shouldn't be a problem.

Why wasn't it caught up by TS error?

It would have been caught if Orchid was used directly in user-land code, however, I'm also using orchid as an underlying query builder engine for the GraphQL query builder (orchid-graphql). I didn't yet come up with full type transparency through the entire GraphQL request-resolver-query builder-response stack (and I'm not sure it's possible at all) so such errors only happen in runtime.

Cool project!
Yeah, the same in my code in this repo - no type-safety in the guts, dirty type-casts everywhere. Definitely not our fault, and I believe not a fault of TS, because library code is dynamic and tricky by its nature, and use cases go beyond what probably any type-system could support.


ensure checkbox is vertically centered

In many cases we need to make the checkbox smaller but then the box would not be aligned with the text. The box should be kept vertically centered. So this PR just tries to do that.

when do you need to make the checkbox smaller?

we need to make it smaller so that it can fit in the UI better.
as in team schedule:

I dont really see at difference in the styleguide and i dont think transform is the best way of changing position/size of a element we have total control over in the first place

If i look in the project right now i can see that the checkboxes are smaller in the team schedule. There it is done by changing width and height, would this be kept if this pr was merged?
Exuse me but i still dont see why they need to be smaller since they dont take any less space. If it wasnt for the fact that i can click the whole row in this case it just makes the trigger area of the checkbox harder to hit

lets close this for now and review if the need arrises for smaller checkboxes


metal support

Currently we support CUDA as the only accelerator. Metal would be a nice addition and is very well supported by llama.cpp

some work done in #65 - not working yet.

I am not familiar enough with either cpp or mac to debug this - I think I'm mostly along the right track, but if someone could take this across the finish line that would be great.

fixed in #65


Make Code2Vec accesable thru DS4Se

Create the interfaces for code2vec in the representation module.

Code2Vec cannot be easily integrated into ds4se. However, we are using it as an external library under /notebook folder in the root. We are able to generate a dataframe with the embedding vectors for a given system.

Code2Vec cannot be easily integrated into ds4se. However, we are using it as an external library under /notebook folder in the root. We are able to generate a dataframe with the embedding vectors for a given system.


⚠ ClamAV has degraded performance

In 7a3e1c4, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 91 ms

Resolved: ClamAV performance has improved in e652862.


Argument validation initial implementation

Implementation of arguments, including command line specifications.
Tests of command line arguments and method parameter arguments.
Bolus of test data files and utility to access their paths.

Ok so after talking to John Parejko and looking over RFC-793, LSST DM are able to use pytest only features in their unit tests and they only continue to write in unittest because they don't want to go back and rewrite all their old tests, so I think it should be fine for us to just use pytest for lsd2 and other things (which honestly I would prefer since the test code is much cleaner 😭 ). going to go ahead and approve this change and we can discuss this further/confirm with everyone next week!


Installation fails on starting services

Hi,
I am trying to install Redis-x64-3.0.501.msi on my Win10 laptop
The process is stucked on status: starting services
Error is Service Redis failed to start. Verify that you have  sufficient privileges to start system services.
I am admin on my workstation. Do you know how I can fix this?
Thank you for your help

Hi @viellepeau
what version of Windows 10 are you using?
Have you made any changes to the MSI setup option?

Microsoft Windows 10 Home
Version 10.0.10586 Build 10586
I chose all default options in the installer except add to PATH env var

@viellepeau
we never tested the Home version, I don't know if that may be the problem.
Try creating the install log running the following command from a command windows that has admin privilegies: msiexec /i Redis-x64-3.0.501.msi /l*v redis-msi.log

redis-msi.log.txt
Please find attached the log

@viellepeau
the MSI log shows the error but without adding more info to the already known problem.
Check the application event log to see if there is any Redis entry.
You may also uninstall the current installation and try using the binaries from the .zip file https://github.com/MSOpenTech/redis/releases/download/win-3.0.501/Redis-x64-3.0.501.zip
and see if the Redis starts when running as an app and then try to install it using the command line command: redis-server --service-install redis.windows.conf --loglevel verbose

It works :) Thank you


add video share stories

add method video to instagram stories.

It’s an really good improvement. I was looking for something like this!
I hope this PR is approved

@rafaelcamaram good to know!
I am also excited with this new feature.
Could you please help us testing this PR?

We also implemented this feature. It would be great to have it in the module

Can you confirm is this PR is working? 🤔 I forced an update with our master, but it would be nice to test this on real life case.

We also implemented this feature. It would be great to have it in the module

Can you confirm is this PR is working? 🤔 I forced an update with our master, but it would be nice to test this on real life case.

We have not tested this PR specifically but our solution is the same and it works fine on Iphone 11. OS Version 13.x. We were able to share a video as Insta Story

It works fine on iPhone 10, 13.4.1 👍

One thing missing is support for backgroundTopColor/backgroundBottomColor, but it's missing for Image as well, so probably best to add support for both in a separate PR.

@rpavlovs I think we already have something similar in the current version of this library. Would you mind checking: https://github.com/react-native-community/react-native-share#static-values-for-instagram-stories.
Maybe we can use some improvements in this PR as well. 🤔

Looks like background colours are set for stickers only: https://github.com/react-native-community/react-native-share/blob/master/ios/InstagramStories.m#L107-L127
Not sure if we end up using share to insta stories, because of the 20 sec video limit (we need 1 min), but I'll make those changes if we do.

@slaycky would you mind to fix conflicts? Thanks.

Any update? We really need this feature. Any way I can help to do it faster? I am new to how this process works

@alexandruenache19 right now it looks like there is a big conflict in the README which @slaycky needs to resolve then it might be good to go - @slaycky hasn't responded in a while though, if you made a fresh PR just in case, with everything cleaned and resolved based off this one and confirmed it worked, it might be merge-able?

@alexandruenache19 right now it looks like there is a big conflict in the README which @slaycky needs to resolve then it might be good to go - @slaycky hasn't responded in a while though, if you made a fresh PR just in case, with everything cleaned and resolved based off this one and confirmed it worked, it might be merge-able?

We can follow this approach if you feel comfortable with that @alexandruenache19. I only think that we need to give the credits to @slaycky for that.

Hello Guys, Sorry for not responding at time. I resolved the conflict. waiting for 1 approving

Hello Guys, Sorry for not responding at time. I resolved the conflict. waiting for 1 approving

Actually we to move these changes on README.MD explaining this to our docs. Let me know if you need any help. 😄

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

@MateusAndrade, I noticed the commits reflect only iOS but the docs don't mention any limitation on Android, will this param backgroundVideo  work on Android as well?

@MateusAndrade, I noticed the commits reflect only iOS but the docs don't mention any limitation on Android, will this param backgroundVideo  work on Android as well?

I did a quick search and it looks that it's working on iOS only. I think we need to add a new column regarding of the limitation of the options passed when sharing with Instagram Stories. Which can be seen here.
Would you mind helping us with that @vforvasile ? 😅


Calls to this module should be wrapped with env check

I'm explaining this here - problem is that minifiers are not always smart enough to recognize that those functions are noop in production and that calls to them can be safely removed.

Hey man thanks for opening this - for some reason I wasn't subscribed. I'll take a look.

You could auto-wrap those with https://github.com/4Catalyzer/babel-plugin-dev-expression


Deployment and Downtime Clarification

** Please describe which feature you have a question about? **
Deployments
** Provide additional details**
I have a few general question about deployments and downtime.

During the backend phase of the build when CloudFormation stacks are updating, what kind of downtime should I expect? Does it depend on the change set and services changing? Can you offer some information about how the main services are affected during deployment including AppSync, APIGW, Lambda and DynamoDb?
Similar question to 1 but with respect to the front end deployment phase. How is CloudFront and S3 affected during deployment.

For (1) I'll need to transfer this issue over to the CLI team.
The answer to (2) is there's no downtime. We perform an atomic config change so that the latest assets are served instantly. We also continue to serve the assets for the last 6 deploys (resolving to the latest version if the name is the same but contents are not), so old assets don't suddenly disappear for users currently using the site during a deployment.

Thanks for the timely and detailed response! WRT the front end deployment, this is perfect. Feel free to close/transfer me to the CLI team for the backend answer.

@alexkates The CLI uses Cloudformation to deploy stacks and changes to configurations. The downtime would depend on what changes you're making to your schema or API. If you're deleting a model@ and adding a new one - which your frontend depends on, then you'll have a downtime until the old table is deleted and the new one is created as a part of the Cloudformation deployment. There wouldn't be any downtime if you're just updating an already existing resource.


Slow firestore listener performance with large data sets

Xcode version: 9.4.1
Firebase SDK version: 5.3.0
Firebase Component: Firestore
Component version: 0.12.4

I’ve been experiencing surprisingly slow performance with Firestore listeners with larger data sets (thousands of documents).  There are three issues that are seemingly related…let me know if you’d like me to break this up into separate issues.
All testing has done using a simple sample app running on an iPhone 7.
Slow listener response when querying large data set
For a data set with thousands of documents, it takes several seconds for the initial update from the listener.  For example, a listener querying a data set with 3000 simple one-key documents takes 1-2 seconds for the initial listener update closure to be called.  From what I’ve seen this appears to be simply the time it takes to query the local cache and return the 3000 documents. This seems surprisingly slow for locally persisted data.  I’ve tested this both online and offline with the same results.
I found this closed issue which seems similar, but I wasn't sure if it was the exact same problem or not:
https://github.com/firebase/firebase-ios-sdk/issues/413
Steps to reproduce:

Create listener to query a data set of 3000 documents.
Measure the time it takes for the first listener update to be called.

Paging with limit() does not help (actually a bit slower)
I looked into using limit(to: 100) on my listener query to only return the first 100 results, thinking this might get me faster results from the listener.  But it was actually a bit slower when I did this.  Should paging using limit() improve the performance of the listener query?
Steps to reproduce:

Create listener to query a data set of 3000 documents, with a .limit(to: 100) added to the end of the query.
Measure the time it takes for the first listener update to be called.
It will take slightly longer time compared to without the limit (maybe 10% longer).

Listener performance is worse immediately after adding the large data set
If I set up the listener after adding the 3000 documents from the app (without delete/reinstall in between), then the initial listener query seems to take MUCH longer, around 20 seconds.  This happens even after a re-launch of the app, and after I’ve made sure all the documents have been added to the cloud.  If I then delete and reinstall the app, then the listener performs back at the 1-2 second timing again.  It almost feels like after adding the 3000 documents that the local cache is in some degraded-performance state and a re-install allows it to re-cache everything cleanly (but I have no evidence this is what is actually happening).
Steps to reproduce:

From an empty database, add 3000 simple documents from the app.  Wait for all documents to be written to the cloud.
Create listener to query that same set of 3000 documents.
Measure the time it takes for the first listener update to be called.
It will take much longer, like 20 seconds or so.
Kill and force quit the app, repeat steps 2-4, same result.
Delete and re-insatll the app, repeat steps 2-3, measured time now is 1-2 seconds.

I first ran into these issues with our own in-development app.  But I’ve been able to consistently reproduce them using a very simple test app (which I can share if that would help).

@KabukiAdam Thank you for this detailed performance feedback! This is useful and I appreciate you taking the time to provide it.  I haven't dug in too deep, but I'll briefly respond with my initial analysis.
Your first point (slow w/ large data set) is semi-expected. We may be able to optimize this some, but on the order of ~1 second per 1000 documents is probably expected right now.  We generally assume apps will be querying smaller result sets (on the order of what fits on a screen).
Your second issue (paging with limit() does not help) is expected right now but we have planned improvements that should help a lot. Currently the client does not implement its own indexing of data which means that in order to satisfy your limit(), we need to load all of the data, sort it, and then apply the limit in-memory. As you noticed, this is just as slow (or slower) than querying the full data unfortunately. Once we implement client-side indexing, limit(100) should be ~30x faster than the full 3000 documents.
Your 3rd item (listener performance worse immediately after adding the large data set) is very surprising to me.  I could imagine there could be some performance quirks while those writes have not yet been committed to the backend, but once they're committed I don't know why there would be a lingering performance issue.  Can you confirm your completion block(s) were called?  And were you using the WriteBatch API to do multiple writes at once?  Or just 3000 individual setData() calls or similar?  If it's easy to provide a repro app, that would make it much faster for us to investigate.  Else we'll try to get this assigned to somebody for repro and investigation in the coming weeks.
Thanks again for the feedback!

@mikelehen Thank you for the prompt and helpful reply.
Regarding the listener performance with a large data set, it's good to hear that my results are not unexpected. However I can't help but feel this is still "slow" relative to what one would typically expect for locally-persisted data queries (similar queries using core data or sqlite are ~100 times faster). I do agree that 3000 documents is way more than would ever fit on a screen, but it is fairly common to have a very long list of things in a list in the UI, and allow the user to quickly scroll through it (even it only a small subset appears on the screen at once).  And there are cases where even a screen-full of data could number 100 documents (for example "events" on a month-view calendar), which would take ~0.1 seconds to query, just barely fast enough given the expected UI latencies for native mobile apps. Anyway, that's just some extra feedback on the performance in general...if there's a better place to give this kind of feedback, I'd be happy to do so and go more detail.  :)
Regarding the issue of paging with limit(), I'm very glad to hear that there are plans to implement client-side indexing to proportionally improve performance.  Is there any information about the plan/timeframe for this to be implemented?  I know time estimates (especially public ones) are somewhat tricky, but it would be extremely helpful if we had some idea about the timeframe you're shooting for.  (Our app will depend on paging to deal with querying these larger data sets).
Regarding the issue of listener performance being worse right after adding the large data set.  In my tests, it was doing 3000 individual setData() calls (called in a tight loop).  And yes I can confirm that the completion block is called for each write.
I’ve pushed a copy of our test app to Github here:  https://github.com/KabukiAdam/FirestoreListenerTest
Steps to reproduce using the above test app:

Run app, tap “Test Large Data Set” to create the 3000 documents.  The on-screen log will show when each callback is called after creating the document.  Check Firebase console to confirm that all documents have been created.
Force-quit app, disable networking (to guarantee local query), open app, tap Create Listener.  Takes ~20s.  NOTE if you tap Create Listener at the end of step 1, then it only takes ~7s here in step 3…not sure why the difference?
Delete the app from the device (to start with empty local cache), enable networking, open app, tap Create Listener.  First time it needs to query from cloud so it will take a bit longer, but on subsequent Create Listener taps it only takes ~1.2s.
Force-quit app, disable networking (to guarantee local query), open app, tap Create Listener.  Takes ~1.2s.  Will always take ~1.2 forever after.

Results summary:  ~1.2 sec seems to be the “normal” time, but I only see this after a delete/re-installl.  The listener time right after adding the documents takes much longer (and it never seems to go down in time on its own).
Thanks again for your help with this.

We faced the same issues where we have 10 collections with an average 500-3000 docs each - all must be listened when the app starts. When the number of docs for each is small e.g 100 each, the performance is fine, but now on an average 500-3000 docs (each docs is less than 2kb), it becomes extremely slow both online and offline.
Profiling:

Local DB Cache: 23Mb

@rsgowman We're interested on how you do compacting the leveldb for a quick remedy right now. Can you please tip us on that? Thanks.

@businessengine Check out https://github.com/firebase/firebase-ios-sdk/pull/1494. It's not a finalized PR, but demonstrates the issue.
However, note that the specific performance degradation that this seems to help only applies to offline queries. When online, simply creating the query is enough to cause leveldb to perform quickly, so this may not be relevant at all for your use case.
As Mike pointed out up-thread, performance for large query sets could run as slow as ~1 second per 1000 docs. So if you're querying for (10 collections * 3000 docs each = ) 30000 docs, and it's taking ~30s (according to your image capture of your profiler) then this may be in line with current expectations.
Nonetheless, if you'd like to try patching your copy of firestore with the change in the above PR and report back here, it'd be incredibly useful for us to know if that improved things for you or not. (Alternatively, if you can provide a minimal repro app, I can make the above change and see if that helps.)

Thanks @rsgowman, we applied the patch and noticed the leveldb size reduced from23 to 15MB, however, overall performance is still the same (or unnoticeable). We may have to consider the solution where we cache big collections ourselves with alternate db such as realm or snappydb. Do we have any roadmap/milestones on when Firebase team will work on the client-indexing feature which may help improve performance for cases like this? Thanks.

@KabukiAdam Thanks for a great repro case! Experimenting with the test app you provided locally, it appears to me that #1533 significantly speeds up creating a listener for several K documents. If you have the opportunity, it would be great if you could try out that branch on your side, just to check whether you see a similar performance improvement. (I slightly modified the app to create 9K documents. In release mode using iPhone 8 Plus simulator in XCode 9.4, I get ~54.3s delay before listener creation on master and ~2.9s on the branch. If you see comparable numbers, I think it should solve the issue).
@businessengine I can't verify locally, but #1533 optimizes the code path that shows up in the stack trace you provided, so it's reasonable to presume it should improve performance for your case as well. If you have the opportunity to try out that branch on your side, I'd be very interested to know the results. Thanks!

Thanks @var-const Great news! We will try it out today.

Tried the branch varconst/coll-opt but got the following header missing: 'FirebaseCore/FIRAppEnvironmentUtil.h' file not found
We used
  pod 'FirebaseCore', :git => 'https://github.com/firebase/firebase-ios-sdk.git', :branch => 'varconst/coll-opt'   pod 'FirebaseFirestore', :git => 'https://github.com/firebase/firebase-ios-sdk.git', :branch => 'varconst/coll-opt'

@businessengine Oh, really sorry about the trouble. There was some project restructuring recently, this failure looks related to that. The way I had it in my podfile was to only use the non-standard pod for Firestore:
pod 'Firebase/Core'
pod 'GoogleUtilities'
pod 'FirebaseFirestore', :git => 'https://github.com/firebase/firebase-ios-sdk.git', :branch => 'varconst/coll-opt'

I'll look into this more closely tomorrow.

Our pod structure is in flux until the next release and installing from branches will vary for component and over time until we release the M30 milestone. More background at #1535.
Since Firestore is still compatible with both the latest and last release dependencies, it should be sufficient to add the one line to the Podfile:
pod 'FirebaseFirestore', :git => 'https://github.com/firebase/firebase-ios-sdk.git', :branch => 'varconst/coll-opt'

@var-const Yes, I was able to confirm that #1533 does seem to fix the long listener times that I was experiencing right after creating a large set of documents (the issue I described under Listener performance is worse immediately after adding the large data set in my original post).  The listener time now seems to be the same as it would be after a fresh install.
Thanks for quick investigation and fix!

@KabukiAdam That's great to hear, thanks for the confirmation!
@businessengine To echo what @paulb777 Paul said, I could successfully build FirestoreListenerTest by only pointing the FirebaseFirestore pod to a Git branch, so that the Podfile looks like:
use_frameworks!

target 'FirestoreListenerTest' do
   pod 'Firebase/Core'
   pod 'FirebaseFirestore', :git => 'https://github.com/firebase/firebase-ios-sdk.git', :branch => 'varconst/coll-opt'
end

However, if I change FirebaseCore to also point to Git, I start having issues similar to those you're describing. Please let us know if you still run into build errors when having a Podfile similar to the snippet above.

Thanks @var-const we used that same Pod content too.

@businessengine Are you still seeing build errors when using a similar podspec? If errors persist, then if you could share the Firestore-related bits of your podspec and the errors you're seeing, I could take a look.

@var-const sorry for the misunderstanding, we were able to build successfully with the above pod lines. Notice a hug performance boost in batch writing, but caching big 10-15 collections when the app starts is somehow similar as before. We can extract our code and send you via email for further investigation. Please let us know if that works for you.

@businessengine Would you be able to upload a snippet of the problematic code to Github (doesn't necessarily have to compile as long as it clearly demonstrates the issue; of course, a minimal test app is best if at all possible)?

I noticed that Firebase 5.5.0, which contains Firestore-0.13.0, was released and I tried to use it.
I was troubled with this performance issue before v5.5.0, but after updated to v5.5.0, it seems to be fixed 👍

This fix was released as a part of Firebase 5.5.0.

@var-const Thanks, and sorry for the late reply.  It looks like this only fixes the 3rd part, which is what I expected.
From previous replies, it sounds like the first issue I reported ("Slow listener response when querying large data set") might simply be the intended performance.
The second issue ("Paging with limit() does not help (actually a bit slower)") is still an issue.  Should I create a new Github issue so it can be tracked separately from this one?

@KabukiAdam Thanks for clarifying! Yes, it would be great if you could create a new issue.


AntTweakBar

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Proposed solution
AntTweakBar is a small and easy-to-use C/C++ library that allows programmers to quickly add a light and intuitive graphical user interface into graphic applications based on OpenGL (compatibility and core profiles), DirectX 9, DirectX 10 or DirectX 11 to interactively tweak parameters on-screen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered if applicable.
Additional context
Add any other context or screenshots about the feature request here.

If you wish to add this port in the future, you can reopen this issue, but we're closing it for now.


fix: major lib update + increase MSVR

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


Node Download Progress Never Fires

I'm trying to use the .on('progress', cb) method for a download in my Node application, but the callback function is never called. For uploads, .on('progress', cb) works just fine.
Relevant versions:

node: 12.14.1
superagent: 6.1.0
typescript: 4.0.5
ts-node: 9.0.0

Download example (does not work):
agent()
  .get(downloadUrl)
  .maxResponseSize(this.maxDownloadSize ?? 200_000_000)
  .on('progress', ev => {
    console.log('Progress: ', ev.loaded);
   })
  .then(r => {
    console.log("Response body: ', r.body);
  });

Upload example (works):
agent()
  .post(uploadUrl)
  .attach('file1', bufferToUpload, {filename: 'thing1.zip', contentType: 'application/zip'})
  .on('progress', ev => {
    console.log('Progress: ', ev.loaded);
  })
  .then(r => {
    console.log("Response body: ', r.body);
  });

I met the same problem.


System setup for the ML course

Discussed in https://github.com/microsoft/ML-For-Beginners/discussions/252

Originally posted by cjd2003 July 30, 2021
Hi,
In order to configure my system for this course, I tried clicking the link in the first lesson 1 - Into_to _ML but it took me to a set of videos for "Introduction to Python".. I was wondering if I could get the correct link.
Thank you.

All the links are correct as I can see...  Can you specify exactly which link is Wrong.

All the links are correct as I can see... Can you specify exactly which link is Wrong.

@ravindranath-sawane see my comments on #252 and the corresponding PR with a proposed fix at #304


setFilter doesn't filter subRows

I'm trying to add a filter functionality on my table that has expandable rows, then the filter is applied only on first level rows, not on subRows.

As far as I know, you should be getting filtered sub rows:
https://github.com/react-tools/react-table/blob/50f2e84929f38f257a198206ded3100f85ad9856/src/plugin-hooks/useFilters.js#L204-L216
Please open a new issue with a codesandbox example demonstrating this problem so we can better help you. Thanks!


A mechanism for influencing order of AutoPlugins *settings additions

I have some keys in my AutoPlugin that I want to provide default values for. In projectSettings in my plugin, I use myKey := Seq(someDefaultValue), and in the build.sbt that uses my plugin, I write myKey += anotherValue. Unfortunately, the projectSettings seem to get added afterward, so my build fails complaining that myKey has no value.
Alternately, I just need a mechanism for defining the "default value" of a key.

Please open a new, more specific issue if you ever reproduce this one day. :)


"Open Recent" not containing saved files

Issue Type: Bug
"File > Open Recent" should also contain files which were recently created and saved - not just recently opened files.
VS Code version: Code 1.68.1 (30d9c6cd9483b2cc586687151bcbcd635f373630, 2022-06-14T12:52:13.188Z)
OS version: Darwin x64 21.5.0
Restricted Mode: No

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Use short form for private studies too. Fix #1164

This makes it so editing is done properly for studies that are private, as well as ones that are public and sandbox.

:+1:

Coverage increased (+0.01%) to 79.04% when pulling d686dfa03efe0c2bde4da07d28299675a52ba410 on squirrelo:issue-1164 into 9021ae36a3d29905f49ac2bdaa53d90e9ecc9827 on biocore:master.


WIP: Allow the redactor to redact values with non-ascii characters

superseded by the much more sensible #1809. Thanks @DrJosh9000!


CRUD many-to-many relatioships between 3 interconnected collections

Hi @mitar
I have 3 collections: Markets, Producers and Organizations.
Markets might have many Producers and vice versa
Producers might have many Organizations and vice versa
Organizations might have many Markets and vice versa
My question is, how should I design the schemas in order to perform atomic inserts, updates and deletes? so all the information is consistent and stays in sync
Thanks in advance for any help

join tables

Atomic inserts is not something PeerDB facilities for you in any special way. Read MongoDB two-phase commit documentation if you want such types of atomicity in MongoDB.
But often you do not really need atomicity. Why would you need it in this case? You want consistency, not atomicity of updates. And often you are OK with eventual consistency.
So, here you could just define something like:
class Market extends Document
  @Meta
    name: 'Market'
    fields: =>
      producers: [@ReferenceField Producer]

class Market extends Document
  @Meta
     name: 'Market'
     fields: =>
       organizations: [@ReferenceField Organization]

class Organization extends Document
  @Meta
    name: 'Organization'
     fields: =>
       markets: [@ReferenceField Market]

This will make sure many-to-many references between your documents are eventually consistent.


Tree is not rendering

Hi there,
I don't know why the tree is just render root, the children are not on version 6.0.1 and up. It works well on v3.2.3. Could you please help to check?

This is my code:
import { Component, OnInit, OnChanges } from '@angular/core';
import { ITreeOptions } from 'angular-tree-component';

declare var require: any;
@Component({
selector: 'app-async',
template:       <tree-root #tree [options]="options" [nodes]="nodes"></tree-root>   ,
styles: []
})
export class StartPageComponent implements OnInit {
ngOnInit() {
}
options: ITreeOptions = {
getChildren: this.getChildren.bind(this)
};
  nodes: any[] = [];

  asyncChildren = [
    {
      name: 'child1',
      hasChildren: true
    }, {
      name: 'child2'
    }
  ];

  constructor() {
    this.nodes = [
      {
        name: 'root1',
        children: [
          { name: 'child1' }
        ]
      },
      {
        name: 'root2',
        hasChildren: true
      },
      {
        name: 'root3'
      }
    ];
  }

  getChildren(node: any) {
    const newNodes = this.asyncChildren.map((c) => Object.assign({}, c));

    return new Promise((resolve, reject) => {
      setTimeout(() => resolve(newNodes), 1000);
    });
  }

}

It renders as bellow:

This bug happen with webpack, angular cli works well.

@taiducnguyen , could you please elaborate? I am facing the same issue. What steps should I take to rectify this?

I am also having the same issue

Has anyone figured out how to get around this? I'm also stuck on this issue.

Make sure you have imported the stylesheet in your main styles.scss or equivalent:
@import "~angular-tree-component/dist/angular-tree-component.css";

We just upgraded to angular 5 and angular-tree-component version 7 and our trees do not render. Only the root nodes.

Yes you should import the CSS. Thanks @keathmilligan

The problem was the missing import also in my case, many thanks @keathmilligan

This bug happen with webpack, angular cli works well.

@taiducnguyen i am facing the same issue with angular 7 and tree-component v8.3.0 ,can you please help me,how to fix.

I have the same problem and i added the css import also but still continue to have the problem.
But for me the import line is @import<EMAIL_ADDRESS>and not @import<EMAIL_ADDRESS>since dist is not an available location in the library.
I don't know if that makes a difference though


[Lighthouse / Blocking Resources / Helpful]

Page Affected:
https://developers.google.com/web/tools/lighthouse/audits/blocking-resources
What needs to be done?
The page offers no meaningful solutions to render-blocking, non-critical CSS. Consider adding some.
The page claims that the (non-standard) "disabled" attribute will prevent browsers from downloading stylesheets. This is not true for all browsers and should be removed.

Thank you for feedback @shakyjake
Yeah... that doc definitely has "room for improvement"

Re: the disabled attribute I changed the phrasing to say that "some browsers won't download the stylesheet" when that attribute is present. I'm leaving it in the doc because it's part of Lighthouse's algorithm.
Can you file a bug at https://github.com/googlechrome/lighthouse/issues/new if you think that they should remove this check?

I'm also noting that it's not supported in all browsers.

Regarding meaningful solutions for CSS, I'm adding a mention to Addy's "critical" tool.


[Logger] Show output log during running job runner

This commit shows output log during running job runner.
ONE-vscode-DCO-1.0-Signed-off-by: Jiyoung Yun<EMAIL_ADDRESS>

/cc @hyunsik-yoon This changes is what you said at offline meeting. When user request to install, uninstall or any job runner event, it changes to focus on the output log of ONE-vscode.


"ScaledObject doesn't have correct scaleTargetRef specification" in logs

Please provide us with the following information:

This issue is a: (mark with an x)

[x ] bug report -> please search issues before submitting
[ ] documentation issue or request
[ ] regression (a behavior that used to work and stopped in a new release)

Issue description
In the azure portal, the 'revision management' screen shows my latest revision is Provisioned.  But clicking to 'Log stream' page shows
'This revision is scaled to zero.' message.  Scaling is set to 1-1 for this app.
Steps to reproduce

.  Create a new revision
.  Once provisioned, navigate to Log Stream screen.

Expected behavior [What you expected to happen.]
I'd have expected a status of Provisioned once the replicas have been created.
Actual behavior [What actually happened.]
Status of provisioned but no replicas created.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Ex. Did this issue occur in the CLI or the Portal?

Hi @nickraphael! There are a few different ways to access observability in ACA: https://learn.microsoft.com/en-us/azure/container-apps/observability . There are times when an app is provisioned but something has happened to affect the health. I'm working on a feature to add health observability. When the log stream can't observe anything, the "logs" blade might help you instead. Here's a tutorial for using log analytics: https://learn.microsoft.com/en-us/azure/azure-monitor/logs/log-analytics-tutorial

Let me know if that helped!


JBPM-4902: Table/Column case issues in Proc&Task dashboard

Fix + test

+1

master: 6a5b507d1b2f4b9d8f3c751bb2ddd564040083ce


Merge code into andrew-register

Code merge is complete. I've broken up the changes into smaller commits.
Done Checklist

[ ] Task has been completed as per the Trello card
[ ] All acceptance criteria are met
[X] Developer has tested this locally
[X] Developer has reviewed their own PR
[ ] Design has been reviewed by design team
[ ] Tests have been added or updated
[X] Views are responsive for mobile devices
[ ] Feature files have been written or updated
[ ] Changelog updated

Made the changes according to Andrew's suggestions. Already pushed to andrew-register branch. See 17e3e93


Not all chips in chip Input are selectable via keyboard arrows

Bug, feature request, or proposal:
Not all chips in chip Input are selectable via keyboard arrows.
What is the expected behavior?
All chips in chip input are selectable via keyboard arrows.
What is the current behavior?
When at least 3 chips exist, the third chip is not selectable via arrow keys. Instead only the first two chips take turns.
What are the steps to reproduce?
Go to chip input with tab (or select the first chip with mouse) and navigate via arrow key (-->) to the third chip (or further when available).
Use StackBlitz/Example from Material doc: https://gaxpxeeookb.angular.stackblitz.io/ (with code here: https://stackblitz.com/angular/gaxpxeeookb?file=app%2Fchips-input-example.ts)
What is the use-case or motivation for changing an existing behavior?
Accessibility.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
I'm using latest (non beta) Material version 6.4.7
Is there anything else we should know?
Material is awesome! :)

This has been fixed by https://github.com/angular/material2/pull/12987.

Ok, seems like an fix is available in 7.0.0-beta.2 here: https://github.com/angular/material2/commit/959c827fe4908d45dd428a1c3141a2f28437a211


Expand the documentation on the EntityFeature  method

This is just an update to the documentation.
I found that the css keyword argument was not documented, and it differs from the js argument. This PR could be a little better if I know what the possible values for 'medium' are, but I at least documented that the css= argument needs to be a dict, and that 'all' is one value that works.

I just updated the documentation to include a link to the django docs here:
https://docs.djangoproject.com/en/2.0/topics/forms/media/
These docs would be helpful to understand the values for those arguments.


Office365 behind SSO

hi,
In our organization, we use SSO based authentication to access e-mails in Office 365.
How do I use this plugin to monitor mailbox using SSO?
Thanks!

Hi @suseendare ,
I'm not sure to be honest - I'm not familiar with SSO, and the way I understand it, there are many SSO applications/implementations. At the end of the day though, the SSO will still be authenticating with Office365 (somehow) - I imagine you can still login to Office365 using credentials? (have you tried?)
If we had more detail, someone (out there) might be able to help?
Which SSO software are you using:

Microsoft Online Services Sign-In Assistant (MOS SIA)
Active Directory Federation Services (ADFS)
??

Kind regards,
Nick

No response, Closing issue.


Add a test-suite section for testing QuickCheck properties

by running stack test.

As mentioned also here, it can be possible that stack test will not be able to load the modules because of the MaîtreDXyz filenames.
Notice the "Ma├«treDTests.o: No such file or directory" below:
$ stack test
BookingApi-<IP_ADDRESS>: build (lib + test)
Preprocessing library BookingApi-<IP_ADDRESS>...
[1 of 4] Compiling MaîtreD          ( MaîtreD.hs, .stack-work\dist\2672c1f3\build\MaîtreD.o )
[2 of 4] Compiling MaîtreDTests     ( MaîtreDTests.hs, .stack-work\dist\2672c1f3\build\MaîtreDTests.o )
[3 of 4] Compiling DB               ( DB.hs, .stack-work\dist\2672c1f3\build\DB.o )
[4 of 4] Compiling Composition      ( Composition.hs, .stack-work\dist\2672c1f3\build\Composition.o )
In-place registering BookingApi-<IP_ADDRESS>...
Preprocessing test suite 'discordia' for BookingApi-<IP_ADDRESS>...
[1 of 3] Compiling MaîtreD          ( MaîtreD.hs, .stack-work\dist\2672c1f3\build\discordia\discordia-tmp\MaîtreD.o )
[2 of 3] Compiling MaîtreDTests     ( MaîtreDTests.hs, .stack-work\dist\2672c1f3\build\discordia\discordia-tmp\MaîtreDTests.o )
[3 of 3] Compiling Main             ( Discordia.hs, .stack-work\dist\2672c1f3\build\discordia\discordia-tmp\Main.o )
Linking .stack-work\dist\2672c1f3\build\discordia\discordia.exe ...
realgcc.exe: error: .stack-work\dist\2672c1f3\build\discordia\discordia-tmp\Ma├«treDTests.o: No such file or directory
realgcc.exe: error: .stack-work\dist\2672c1f3\build\discordia\discordia-tmp\Ma├«treD.o: No such file or directory

--  While building package BookingApi-<IP_ADDRESS> using:
      C:\sr\setup-exe-cache\x86_64-windows\Cabal-simple_Z6RU0evB_<IP_ADDRESS>_ghc-7.10.3.exe --builddir=.stack-work\dist\2672c1f3 build lib:BookingApi test:discordia --ghc-options " -ddump-hi -ddump-to-file"
    Process exited with code: ExitFailure 1
Progress: 1/2

However, everything seems to work when I rename MaîtreD to MaitreD and MaîtreDTests to MaitreDTests:
$ stack test
BookingApi-<IP_ADDRESS>: build (lib + test)
Preprocessing library BookingApi-<IP_ADDRESS>...
In-place registering BookingApi-<IP_ADDRESS>...
Preprocessing test suite 'discordia' for BookingApi-<IP_ADDRESS>...
[3 of 3] Compiling Main             ( Discordia.hs, .stack-work\dist\2672c1f3\build\discordia\discordia-tmp\Main.o )
Linking .stack-work\dist\2672c1f3\build\discordia\discordia.exe ...
BookingApi-<IP_ADDRESS>: copy/register
Installing library in
C:\Users\Nikos\Documents\dependency-rejection-samples\Haskell\.stack-work\install\4cd6b5f1\lib\x86_64-windows-ghc-7.10.3\BookingApi-<IP_ADDRESS>-Hp2KjzTb44a8SAanX5uJ4C
Registering BookingApi-<IP_ADDRESS>...
BookingApi-<IP_ADDRESS>: test (suite: discordia)

tryAccept behaves correctly when it can accept: +++ OK, passed 100 tests.
tryAccept behaves correctly when it can not accept: +++ OK, passed 100 tests.

Completed 2 action(s).

Then, running stack test again is faster when there are no file changes:
$ stack test
BookingApi-<IP_ADDRESS>: test (suite: discordia)

tryAccept behaves correctly when it can accept: +++ OK, passed 100 tests.
tryAccept behaves correctly when it can not accept: +++ OK, passed 100 tests.

It's a shame I used that circumflex, but sometimes I just think it's funny to use Unicode in source code, and the word maître d' is spelled like that...
Had I known it'd cause problems, I'd just have named the modules MaitreD and so on...
I'm concerned that accepting this will give people an impression that it ought to work, but it doesn't.
I think we can rename the modules, though, because I don't think I ever mentioned the Haskell modules by name in my blog posts. If you agree, I think we should change the names.
Unless, of cause, there's a way to make the tools understand Unicode...

Unless, of cause, there's a way to make the tools understand Unicode...

For now I've opened this issue in SublimeHaskell which uses hsdev as its primary backend.
It does – somehow – seem to work in Atom's ide-haskell, which uses ghc-mod as its primary backend, but when you try to stack test from inside Atom you're getting the same kind of issue(s)...
So, I think we should go ahead and rename those files. I'll do this on a separate pull request, if that's OK? And then, I may update this one.

I think we can rename the modules, though, because I don't think I ever mentioned the Haskell modules by name in my blog posts.

I don't think it'll be a breaking change since you haven't linked these files in any post (IIRC).

I've now updated the PR to use Maitre* instead of Maître*, and if https://github.com/ploeh/dependency-rejection-samples/pull/7 gets merged, stack test works fine.

Thank you 👍


[Feedback wanted] Fix for first launch fail if casper theme is missing.

closes #4866
During validation a check is run if the activeTheme is present and
fails if missing. New logic is to return another possible theme and
updates the current activeTheme to the alternative.

Issues I see:

Might be mis-using error for the exception flow
Test missing yet
Not sure this could hide an error when some one assigns a non-existing theme as activeTheme and it will silently fallback to another theme.

Not ignoring this - thinking about it :wink:

Thanks for letting me know. I couldn't find any place that would actually fix pre-launch things so let me know if you have better places to put this logic.

Thanks for your work @olsio 👋
This PR is pretty old and has many conflicts. Closing it now.
We would be happy about a new PR if you have time - the issue is still open.


CONTACTS_NOTES for exchange 2007

How to retrieve or add or update CONTACTS_NOTES if server version is 2007.

Have you tried using the item body? This should contain the contents of the note field.

yes body issue is resolved.
On Wed, Nov 30, 2016 at 7:22 AM, James Armes<EMAIL_ADDRESS>wrote:

Have you tried using the item body? This should contain the contents of
the note field.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jamesiarmes/php-ews/issues/360#issuecomment-263759198,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFRKSUDkFBgeJgxcoG0g6NYYqRI2sk9Iks5rDNbwgaJpZM4Kq3Rs
.


Support GHC 8

Done.

I notice that this merge includes a revert of<PHONE_NUMBER>dec9b5a015d666e4a2fe1ab119a7e0 -- was that intentional?


first cut of models that also include an optional string compatible version name

I'm going to close this for now until next week, I think we should get Casey's PR through first as this might break/complicate some stuff.


Fix/maintenance peer dependencies

This PR gives the possibility to use more recent versions of postcss-loader with this plugin
and fixes a gap between readme and peerDependency definition in package.json
Would be nice to have a fix release, thanks.

Thanks ernst 👍
I am not at home right now but I will take a look once I am back