Should support a directory of multiple slide files

Currently, slides must all be in a single, monolithic markdown file. Long presentations built this way become unwieldy. A better solution would be a folder of "sections" of slide files -- each file would define multiple slides, but the files would be stitched together into a full presentation in some way (perhaps the files are numbered, or there's a metadata file in the folder defining the order).

Closed in f2b7793


Cluster creation failed_fetch_and_run - Failed to run boot_as_master postinstall

Environment:

AWS ParallelCluster / CfnCluster version [e.g. aws-parallelcluster-2.5.1]
Configuration file (i.e. ~/.parallelcluster/config) without any credentials or personal data.
config.txt
postinstall.txt

Bug description and how to reproduce:
I have attached the config and postinstall file that used to create cluster. The command that I used is "pcluster create test -nr"
The bug that I got is as follows
"
Cluster creation failed.  Failed events:

AWS::CloudFormation::Stack parallelcluster-test The following resource(s) failed to create: [MasterServerWaitCondition].
AWS::CloudFormation::WaitCondition MasterServerWaitCondition Received FAILURE signal with UniqueId i-0e43dda574dba64a1

I had a look at "/var/log/cfn-init.log" and found some error message
2020-03-09 16:02:37,774 [ERROR] Command runpostinstall (/opt/parallelcluster/scripts/fetch_and_run -postinstall) failed
2020-03-09 16:02:37,774 [DEBUG] Command runpostinstall output: download failed: s3://bucket/path/to/postinstall.sh to - An error occurred (403) when calling the HeadObject operation: Forbidden
parallelcluster: fetch_and_run - Failed to run boot_as_master postinstall
2020-03-09 16:02:37,774 [ERROR] Error encountered during build of shellRunPostInstall: Command runpostinstall failed
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/cfnbootstrap/construction.py", line 542, in run_config
CloudFormationCarpenter(config, self._auth_config).build(worklog)
File "/usr/local/lib/python2.7/dist-packages/cfnbootstrap/construction.py", line 260, in build
changes['commands'] = CommandTool().apply(self._config.commands)
File "/usr/local/lib/python2.7/dist-packages/cfnbootstrap/command_tool.py", line 117, in apply
raise ToolError(u"Command %s failed" % name)
ToolError: Command runpostinstall failed
2020-03-09 16:02:37,776 [ERROR] -----------------------BUILD FAILED!------------------------
2020-03-09 16:02:37,776 [ERROR] Unhandled exception during build: Command runpostinstall failed
Traceback (most recent call last):
File "/usr/local/bin/cfn-init", line 171, in
worklog.build(metadata, configSets)
File "/usr/local/lib/python2.7/dist-packages/cfnbootstrap/construction.py", line 129, in build
Contractor(metadata).build(configSets, self)
File "/usr/local/lib/python2.7/dist-packages/cfnbootstrap/construction.py", line 530, in build
self.run_config(config, worklog)
File "/usr/local/lib/python2.7/dist-packages/cfnbootstrap/construction.py", line 542, in run_config
CloudFormationCarpenter(config, self._auth_config).build(worklog)
File "/usr/local/lib/python2.7/dist-packages/cfnbootstrap/construction.py", line 260, in build
changes['commands'] = CommandTool().apply(self._config.commands)
File "/usr/local/lib/python2.7/dist-packages/cfnbootstrap/command_tool.py", line 117, in apply
raise ToolError(u"Command %s failed" % name)
ToolError: Command runpostinstall failed
2020-03-09 16:02:37,990 [DEBUG] CloudFormation client initialized with endpoint https://cloudformation.eu-west-1.amazonaws.com
2020-03-09 16:02:37,991 [DEBUG] Signaling resource MasterServerWaitCondition in stack parallelcluster-test with unique ID i-0e43dda574dba64a1 and status FAILURE"
error message in "/var/log/cloud-init.log" file:
"
2020-03-09 16:00:59,185 - util.py[DEBUG]: Running command ['/var/lib/cloud/instance/scripts/part-002'] with allowed return codes [0] (shell=False, capture=False)
2020-03-09 16:02:38,075 - util.py[WARNING]: Failed running /var/lib/cloud/instance/scripts/part-002 [1]
2020-03-09 16:02:38,075 - util.py[DEBUG]: Failed running /var/lib/cloud/instance/scripts/part-002 [1]
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 885, in runparts
subp(prefix + [exe_path], capture=False)
File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2069, in subp
cmd=args)
cloudinit.util.ProcessExecutionError: Unexpected error while running command.
Command: ['/var/lib/cloud/instance/scripts/part-002']
Exit code: 1
Reason: -
Stdout: -
Stderr: -
2020-03-09 16:02:38,079 - util.py[DEBUG]: Running command ['/var/lib/cloud/instance/scripts/runcmd'] with allowed return codes [0] (shell=False, capture=False)
2020-03-09 16:02:38,084 - cc_scripts_user.py[WARNING]: Failed to run module scripts-user (scripts in /var/lib/cloud/instance/scripts)
2020-03-09 16:02:38,085 - handlers.py[DEBUG]: finish: modules-final/config-scripts-user: FAIL: running config-scripts-user with frequency once-per-instance
2020-03-09 16:02:38,085 - util.py[WARNING]: Running module scripts-user (<module 'cloudinit.config.cc_scripts_user' from '/usr/lib/python3/dist-packages/cloudinit/config/cc_scripts_user.py'>) failed
2020-03-09 16:02:38,085 - util.py[DEBUG]: Running module scripts-user (<module 'cloudinit.config.cc_scripts_user' from '/usr/lib/python3/dist-packages/cloudinit/config/cc_scripts_user.py'>) failed
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 847, in _run_modules
freq=freq)
File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
return self._runners.run(name, functor, args, freq, clear_on_fail)
File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 188, in run
return (True, results)
File "/usr/lib/python3.5/contextlib.py", line 77, in exit
self.gen.throw(type, value, traceback)
File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 76, in lock
yield self._acquire(name, freq)
File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
results = functor(*args)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_scripts_user.py", line 45, in handle
util.runparts(runparts_path)
File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 892, in runparts
% (len(failed), len(attempted)))
RuntimeError: Runparts: 1 failures in 2 attempted commands"
Error message in "/var/log/cloud-init-output.log" file
"
Error occurred during build: Command runpostinstall failed

error_exit 'Failed to run cfn-init. If --norollback was specified, check /var/log/cfn-init.log and /var/log/cloud-init-output.log.'
cfn-signal --exit-code=1 '--reason=Failed to run cfn-init. If --norollback was specified, check /var/log/cfn-init.log and /var/log/cloud-init-output.log.' --stack=parallelcluster-dhcphuiqing-v2 --resource=MasterServerWaitCondition --region=eu-west-1
exit 1
Cloud-init v. 19.2-36-g059d049c-0ubuntu2~16.04.1 running 'modules:final' at Mon, 09 Mar 2020 16:00:59 +0000. Up 47.96 seconds.
2020-03-09 16:02:38,075 - util.py[WARNING]: Failed running /var/lib/cloud/instance/scripts/part-002 [1]
Not yum system
/usr/bin/apt-get
2020-03-09 16:02:38,084 - cc_scripts_user.py[WARNING]: Failed to run module scripts-user (scripts in /var/lib/cloud/instance/scripts)
2020-03-09 16:02:38,085 - util.py[WARNING]: Running module scripts-user (<module 'cloudinit.config.cc_scripts_user' from '/usr/lib/python3/dist-packages/cloudinit/config/cc_scripts_user.py'>) failed
Cloud-init v. 19.2-36-g059d049c-0ubuntu2~16.04.1 finished at Mon, 09 Mar 2020 16:02:38 +0000. Datasource DataSourceEc2Local.  Up 147.25 seconds"

Hi,
from your logs seems like the master node is unable to fetch the postinstall script from your s3 resource. Please make sure that ParallelCluster has access to your s3 bucket. If you are granting access to it through the s3_read_write_resource parameter (like it seems from your config file), please make sure that its value matches the bucket arn where the postinstall script is located. Additional info is available here: https://docs.aws.amazon.com/parallelcluster/latest/ug/s3_resources.html


python311Packages.cantools: 38.0.2 -> 39.3.0

Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

4 packages built:

python310Packages.cantools
python310Packages.cantools.dist
python311Packages.cantools
python311Packages.cantools.dist

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

4 packages built:

python310Packages.cantools
python310Packages.cantools.dist
python311Packages.cantools
python311Packages.cantools.dist


default slug from title.to_url

https://github.com/owen2345/camaleon-cms/blob/master/app/models/camaleon_cms/post_default.rb#L63
I am not sure why you commented out this line.
I am from Taiwan. We use traditional Chinese.
jquery.slugify won't work for traditional Chinese, I must enter slug manually.
https://github.com/rsl/stringex
There's a helpful method to_url in stringex. It can convert a string to url, even for Chinese.
How about set slug to title.to_url if slug is blank?
  def before_validating
    self.slug = self.title.to_url if self.slug.blank?
  end

@wuboy0307 it was disabled for multisite because post form on submit is sending this format:
<--en-->English<--es-->Spanish.

Then we should deal with multisite string separation. For single site environment, it is still a good idea to generate slug like I proposed. Even for multisite environment, use to_url after local e string been split is still better.
I know it's not quite easy for you to understand. But supports for non-ascii language  are important for me. Maybe you can do something  for this? Thanks.

I now,
can you give a sample of your slug that you are using for? I tried to put this "測試" but it was converted into "%E6%B8%AC%E8%A9%A6".
Also let me know how should be the result.
Note: "string".to_url is not a function.
Regards!

You must include https://github.com/rsl/stringex gem to get the to_url function.
"%E6%B8%AC%E8%A9%A6" is just the UTF-8 encoding format for "測試"
(Chinese, Japan, Korea are encoded with 3 bytes per word)
"測試" .to_url will become "ce-shi", which is the spelling of these two words.
You can listen to it with google translation https://translate.google.com.tw/?hl=zh-TW/en/測試#zh-CN/en/測試

Done!
Please use this plugin:
https://github.com/camaleon-cms/cama_non_ascii_slug

Thanks, it works!


Update google-cloud-bigquery to 2.9.3

Updates com.google.cloud:google-cloud-bigquery from 2.9.0 to 2.9.3.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.google.cloud", artifactId = "google-cloud-bigquery" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #190.


Difference in handling of context bounds and anonymous using arguments

During the minimization of the crash found in OpenCB for https://github.com/takapi327/ldbc I've observed that context bounds and anonymous using arguments are treated differently by the compiler in cases where they're mixed with named using arguments.
When using context bounds we now get an ambiguous implicit resolution, but it's not the case in when the anonymous using arguments. This behaviour seems strange since both ways of declaring implicit ends up as being synthetic implicit parameters introduced by the compiler.
Compiler version
3.6.0-RC1-bin-20240716-bbb45ca-NIGHTLY
Minimized code
trait Functor[F[_]]:
  def map[A, B](fa: F[A])(f: A => B): F[B] = ???
trait Monad[F[_]] extends Functor[F]
trait MonadError[F[_], E] extends Monad[F]:
  def raiseError[A](e: E): F[A]
trait Temporal[F[_]] extends MonadError[F, Throwable]

trait FunctorOps[F[_], A]:
  def map[B](f: A => B): F[B] = ???
implicit def toFunctorOps[F[_], A](target: F[A])(implicit tc: Functor[F]): FunctorOps[F, A] = ???

class ContextBounds[F[_]: Temporal](using err: MonadError[F, Throwable]):
  def useCase = err.raiseError(new RuntimeException())
  val bool: F[Boolean] = ???
  def fails = toFunctorOps(bool).map(_ => ())  // warns under -source:3.5, // error under -source:3.6

class UsingArguments[F[_]](using Temporal[F])(using err: MonadError[F, Throwable]):
  def useCase = err.raiseError(new RuntimeException())
  val bool: F[Boolean] = ???
  def works = toFunctorOps(bool).map(_ => ()) // warns under -source:3.5

Output
-source:3.5
[warn] ./src/main/scala/test.scala:15:33
[warn] Given search preference for Functor[F] between alternatives (ContextBounds.this.evidence$1 : Temporal[F]) and (ContextBounds.this.err : MonadError[F, Throwable]) will change
[warn] Current choice           : the first alternative
[warn] New choice from Scala 3.6: none - it's ambiguous
[warn]   def fails = toFunctorOps(bool).map(_ => ())  // warns under -source:3.5, // error under -source:3.6
[warn]                                 ^
[warn] ./src/main/scala/test.scala:20:33
[warn] Given search preference for Functor[F] between alternatives (UsingArguments.this.x$1 : Temporal[F]) and (UsingArguments.this.err : MonadError[F, Throwable]) will change
[warn] Current choice           : the first alternative
[warn] New choice from Scala 3.6: the second alternative
[warn]   def works = toFunctorOps(bool).map(_ => ()) // warns under -source:3.5
[warn]                                 ^

-source:3.6
[error] ./src/main/scala/test.scala:15:33
[error] Ambiguous given instances: both value evidence$1 in class ContextBounds and given instance err in class ContextBounds match type Functor[F] of parameter tc of method toFunctorOps
[error]   def fails = toFunctorOps(bool).map(_ => ())  // warns under -source:3.5, // error under -source:3.6
[error]

Expectation
There might be a hole in implicit resolution logic that should be fixed.

Minimization:
trait A
trait B extends A

def implicitB(using A)(implicit b: B) = summon[A] // error: ambiguous
def usingB(using A)(using b: B) = summon[A] // ok

Note that, as we can see in test3, the change in rules for given prioritization #19300 does not apply to implicit (as opposed to using) parameters, which is what context bounds expand to. For example:
trait A[X]
trait B[X] extends A[X]

def test[X : A/* as a*/ : B/* as b*/] = summon[A[X]] // still picks b (not the most general)

I'm not sure where/if this behavior is documented, but it appears to be an intentional one: https://github.com/scala/scala3/blob/a046b0014ffd9536144d67a48f8759901b96d12f/compiler/src/dotty/tools/dotc/typer/Applications.scala#L1864


Add markdown support to exercise card and exercise preview

How to test:

Go to /exercises/js0
Check that markdown looks good

Before:

After:

I approved it but there's a small issue though, you may want to check the comments on the vercel preview.

I approved it but there's a small issue though, you may want to check the comments on the vercel preview.

Thanks for finding that bug! I fixed it by adding "d-block" CSS classes to the Markdown components so all markdown is display: block.


Able to add Header

Hello man, your library is very great!!!
I',m think, you can make getItem(position) public to be able override, because i need override this method =/
example:
getItem(position - 1) and getItemCount(size + 1); to include the header on RecyclerView, you can change this? or anyone solution? Sorry my poor english.

@ygorcesar
Hi, friend, thank you  for support and issue.
I understand your issue, firstly because  getItem(poisition) return  ItemWrapper<P,C>  which is used by library privately , if want to get your parent/child item,  you don't have to override getItem(position), you can call ExpandableAdapter#getParent(position)/getChild(parentPosition,childPosition) .
Also . because library use your passed data to init inner data as you extend ExpandableAdapter and need to pass your data to it, if you override ExpandableAdapter 's getItemCount() and not return the real data size, ExpandableAdapter can not determine the itemType in getItemViewType(position) method, as well as can not  determine to which  ViewHolder(parent/child)  need to create in ExpandableAdapter's  onCreateViewHolder  method.
So, if you need to add a header or/and footer , there are many ways you can do this:

you can make your all  header/footer and other parent model class  implement library's Parent interface, and you can override getParentType(parentPosition) and use parentPosition and parent model class (header or other parent which implement Parent)  to determine the parent type.

if you need multiple or/and different type of header or/and footer , you can check this HeaderAdapter


Improvement proposal for section "Who can view the sensitivity label insights report..."

Hi,
Currently the documentation states:
"Who can view the sensitivity label insights report in Microsoft Purview Data Estate Insights?
All users with at least data reader access to the Microsoft Purview Data Map have permissions to view sensitivity label insights reports in Microsoft Purview Data Estate Insights."
I think this is not the complete answer because:

You also need the "Insights reader" role
a user with the "Insights reader" role will only have access to information for collections that they also have at least data reader access to

My suggestion is to describe it like this:
"Who can view the sensitivity label insights report in Microsoft Purview Data Estate Insights?
All users with the insights reader role and at least data reader access for the applicabable collections will have permissions to view sensitivity label insights reports in Microsoft Purview Data Estate Insights."
Best regards,
Henri

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

ID: 2f391208-c028-c931-ffab-f8f99e6d6dc2
Version Independent ID: c8186d8b-776b-8a39-a9e0-6d83a2028479
Content: Sensitivity labels in the Microsoft Purview Data Map FAQ - Microsoft Purview
Content Source: articles/purview/sensitivity-labels-frequently-asked-questions.yml
Service: purview
Sub-service: purview-insights
GitHub Login: @ajaykar
Microsoft Alias: ajaykar

@HenriHeijltjes
Thanks for your feedback! We have assigned the issue to author and will provide further updates.
@MashaMSFT
could you please review this and update as appropriate.

@HenriHeijltjes - Thanks very much! Quite right. I'll get that added. You can expect changes to go out later this week!

The changes will be tracked there. Once you see that request is merged, you'll see the updates by the next business day.
Thank you again for your feedback!
#please-close


material instance issue in ue4.19

hi!
when i using unrealPythonAPI create a material instance in ue4.19, after the material instance created,
when the material instance is opened and modified again(change value by manual, not API ), and then saved, the material uasset will be lost and become a 1kb invalidation file. At the same time, the shader(material instance) in the UE Editor( Content Browser ) will disappear (although the asset using the material will look fine at the time, reopening the project file will turn the asset gray -->  uasset of material-instance "lost").
tested both in py27 and py36 version. found same issue.
There is no such phenomenon in UE418.

here is the code
import unreal_engine as ue
from unreal_engine.classes import Material,MaterialInstanceConstant
parent_material = ue.load_object(Material,'/Game/Materials/M_base')
mat_inst_object = MaterialInstanceConstant()
mat_ball_name = 'M_test2'
mat_inst_object.set_name(mat_ball_name)
mat_inst_object.set_material_parent(parent_material)
save_path = '/Game/Materials2/MI_test2'
mat_inst_object.save_package(save_path)
run the codes, we got a material-instance at content browser.

change the value

save it

now the material-instance disappeared...

PS:
in Content Browser, When you change to another folder (eg Geometry) and then switch back to the Materials2 folder, you will find that the material is still there (again). It seems no problem at present. But when you close the current project and reopen it, the texture ball really disappears.

PS:
in Content Browser, When you change to another folder (eg Geometry) and then switch back to the Materials2 folder, you will find that the material is still there (again). It seems OK at present. But when you close the current project and reopen it, the material-instance asset really disappears.

Hi, i strongly suggest you to use factories for creating assets:
import unreal_engine as ue
from unreal_engine.classes import Material, MaterialInstanceConstantFactoryNew

parent_material = ue.load_object(Material,'/Game/Materials/M_base')
factory = MaterialInstanceConstantFactoryNew()
factory.InitialParent = parent_material

mat_inst_object = factory.factory_create_new('/Game/Materials2/MI_test3')
mat_inst_object.save_package()

that's works(use MaterialInstanceConstantFactoryNew). thank you very much ;-)


Update policy package cmdlets documentation

Docs Build status updates of commit c78bfe6:
:clock10: Full build: the average full build time is 17 min(s) 47 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit c78bfe6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

teams/teams-ps/teams/Get-CsPolicyPackage.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsUserPolicyPackage.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsUserPolicyPackageRecommendation.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Grant-CsGroupPolicyPackageAssignment.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Grant-CsUserPolicyPackage.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/New-CsBatchPolicyPackageAssignmentOperation.md
:white_check_mark:Succeeded
View (teams-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 663993b:
:clock10: Full build: the average full build time is 17 min(s) 46 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 663993b:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

filemap.json
:x:Error

Details

:x:Error

Details

filemap.json

[Error-PublishToDHSFailed] Publishing of document 'filemap.json' to document hosting service failed with asset id: filemap.json locale: en-us, depot name: MSDN.sharepoint-ps, branch name: pr-en-us-6000. Error: A task was canceled.

[Error-BackendEngineExceptionError] An exception occurred during the build process. Please check the raw log and retry building your content again. If the issue persists, please open a ticket in https://SiteHelp and include the URL of publishing report as well as below information: One or more errors occurred..

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit be3322c:
:clock10: Full build: the average full build time is 17 min(s) 46 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit be3322c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

teams/teams-ps/teams/Get-CsPolicyPackage.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsUserPolicyPackage.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsUserPolicyPackageRecommendation.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Grant-CsGroupPolicyPackageAssignment.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Grant-CsUserPolicyPackage.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/New-CsBatchPolicyPackageAssignmentOperation.md
:white_check_mark:Succeeded
View (teams-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 2dc863a:
:clock10: Full build: the average full build time is 17 min(s) 44 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 2dc863a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

teams/teams-ps/teams/Get-CsPolicyPackage.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsUserPolicyPackage.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsUserPolicyPackageRecommendation.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Grant-CsGroupPolicyPackageAssignment.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Grant-CsUserPolicyPackage.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/New-CsBatchPolicyPackageAssignmentOperation.md
:white_check_mark:Succeeded
View (teams-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

@icchan8
Could not find Grant-CsGroupPolicyPackageAssignment on 1.0.25, is it coming in 1.0.26? Asking this because when the article becomes published, people usually start to open issues if they do not find it in the module. Thanks

@get-itips It is coming in the next two weeks. We can merge this PR after the cmdlet is released.

@get-itips It is coming in the next two weeks. We can merge this PR after the cmdlet is released.

No trouble to merge it now I think, two weeks is closer.

Docs Build status updates of commit 26d3723:
:clock10: Full build: the average full build time is 17 min(s) 38 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 26d3723:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

teams/teams-ps/teams/Get-CsPolicyPackage.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsUserPolicyPackage.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsUserPolicyPackageRecommendation.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Grant-CsGroupPolicyPackageAssignment.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Grant-CsUserPolicyPackage.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/New-CsBatchPolicyPackageAssignmentOperation.md
:white_check_mark:Succeeded
View (teams-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 3d74b1f:
:clock10: Full build: the average full build time is 17 min(s) 38 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 3d74b1f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

teams/teams-ps/teams/Get-CsPolicyPackage.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsUserPolicyPackage.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsUserPolicyPackageRecommendation.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Grant-CsGroupPolicyPackageAssignment.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Grant-CsUserPolicyPackage.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/New-CsBatchPolicyPackageAssignmentOperation.md
:white_check_mark:Succeeded
View (teams-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

@chrisda Please merge this PR. Thnaks

Docs Build status updates of commit 5bdc56a:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-RunPsScriptFriendlyFailed] Run script failed with no detailed information. Please retry building your content again. If the issue still happens, open a ticket in https://SiteHelp and include the error report for our team to troubleshoot

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 5bdc56a:
:clock10: Full build: the average full build time is 17 min(s) 36 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 5bdc56a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

teams/teams-ps/teams/Get-CsPolicyPackage.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsUserPolicyPackage.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsUserPolicyPackageRecommendation.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Grant-CsGroupPolicyPackageAssignment.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Grant-CsUserPolicyPackage.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/New-CsBatchPolicyPackageAssignmentOperation.md
:white_check_mark:Succeeded
View (teams-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


How to run CloudDrift's analysis functions in parallel?

Dask
ProcessPoolExecutor?
Inside apply_ragged or some other way?

Let's keep discussing this one and propose solutions if any.

I took some time to read on concurrent.futures and dask.futures, and it looks like it's basically a drop in replacement!
I believe it shouldn't be too hard to use dask in apply_ragged. I'll try to find some time to test it out over the next weekend/week.
See, https://docs.dask.org/en/stable/futures.html.
PS: I also want to see if we can move away from threads in the default case and use processes.

So with the latest update to apply_ragged.
I tried the following:
import clouddrift as cd
from clouddrift.analysis import position_from_velocity, apply_ragged

from dask.distributed import Client
client = Client("tcp://<IP_ADDRESS>:62864")
client

#ds = cd.datasets.gdp1h().load()
import xarray as xr
ds = xr.open_dataset("gdp_v2.00.nc")

u, v = apply_ragged(
    position_from_velocity,
    [ds.ve, ds.vn, ds.time],
    ds.rowsize,
    0,
    0,
    coord_system="cartesian",
    integration_scheme="centered",
    executor=client, # passing the Dask client here
)

and it does seem to be processing the trajectories in parallel.

AS you can see on the next screenshot, it's creating 17324 tasks... it might be more efficient to be able to run a group of trajectories at the same time, but I guess that's a first step.

PS: It doesn't start when I used the AWS source.

I think that's great! So did it complete?

Yes, it completed fine.

FYI, just ran this again today as a test after talking with someone at COAPS.
With the data loaded in memory:
ds = cd.datasets.gdp1h().load()

The following:
%%time
x, y = apply_ragged(
    position_from_velocity,
    [ds.ve, ds.vn, ds.time],
    ds.rowsize,
    0,
    0,
    coord_system="cartesian",
    integration_scheme="centered",
    executor=client, # passing the Dask client here
)

finishes in
CPU times: user 15.5 s, sys: 6.1 s, total: 21.6 s
Wall time: 55.4 s

With lazy loading (removing .load()), there is a small delay at the beginning. But it still finishes pretty fast.
CPU times: user 24.1 s, sys: 8.03 s, total: 32.1 s
Wall time: 1min 13s

I don't remember it being that fast! So it might be due to some of the optimization that were done on apply_ragged.

Ok but what was the "client"?

Same as here, local dask cluster.

ok so 12 cores, 6 workers (whatever this means) and 38GB or memory?

Using the default cluster that it creates in the extension.

I just tried on the default cluster for the jupyterhub on triton and it took 2 min21s wall time ...

By the way, how would you use position_from_velocity in parallel so that it integrates from the starting lat/lon position  of each trajectory? This would imply passing x_origin and y_origin of size rowsize but right now the function only accepts floats ... That's a ragged array problem for clouddrift! @kevinsantana11


Throw an error if itemsFactory returns the same view twice

@sunshinejr Please review and let me know if this looks good.

Hey, thank you so much for the PR! Really good job! 🎉I've made few comments, let me know if everything is clear!

@sunshinejr: Thanks for your comments! Just pushed a couple of commits, let me know how it looks now.

Nice! Looks perfect! Thank you once again! 🎉


CSS is always injected

Hello,
i tried to disable injecting css with directive injectCSS: false but css is always injected with map init.
Test:
in example/src/demos/heatmap.tsx changed line 9 to:
const Map = ReactMapboxGl({ accessToken: token, injectCSS: false });
Screenshot with injectCSS: false

Always tested on production:
React: 16.5.2
Mapbox: 0.50
React-Mapbox: 4.0

Same issue. Simple if (injectCSS) in code doesn't mean css is not injected with some webpack setups. Peronally I think this "feature" should be reverted asap :(

That is CSS compilation works almost always at build time, not runtime. Webpack doesn't habe access to value of injectCSS variable so it just imports all require('*.css') it can find in code, and it happens it finds yours.

@sheerun you are right about Webpack. It always preprocess required CSS.
I think auto requiring CSS for component is not the right thing. It forcing to use predefined design every time.
We are using React Leaflet as fallback for MapboxGL and there are not any CSS. Must be imported manually or make own. It allows us have CSS under control.
By my opinion injectCSS should be removed completely and let the user to make own decision.

Having the same issue, which is preventing us from upgrading to 4.0.0. Our webpack config does not have a css loader, and we do not wish to add one as it will introduce a burden on all the consuming applications of the package that depends on react-mapbox-gl.
The issue is that, even with injectCSS: false, webpack (or most other bundlers) will still import the css at build time, as it sweeps through this line:
https://github.com/alex3165/react-mapbox-gl/blob/bd2827f79cdc4e84b94d247541dd2b138c623cfb/src/map.tsx#L144
And will consequently fail the import because it has no css loader.
Perhaps a solution here is to use dynamic imports, so the if (injectCSS) runtime condition is respected.
On a separate note, the docs have the wrong casing for the config option:
injectCss (Default: true): boolean If false, the factory won't require the mapbox-gl.css sheet.

Should be injectCSS instead.

I think I'm running into the same issue after attempting to upgrade to 4.0.2 from 3.8.0.
I get the following error from mapbox-gl.css:1:
Uncaught SyntaxError: Unexpected token .
    at createScript (vm.js:80)
    at Object.runInThisContext (vm.js:139)
    at Module._compile (module.js:606)
    at Object.Module._extensions..js (module.js:653)
    at Module.load (module.js:561)
    at tryModuleLoad (module.js:504)
    at Function.Module._load (module.js:496)
    at Module.require (module.js:586)
    at require (internal/module.js:11)
    at ReactMapboxFactory (map.tsx:144)

I'm guessing I don't have some webpack rule to be able to process that css file the way it's expecting to be processed. I tried disabling injectCSS but as others above have mentioned, webpack still attempts to process the css file

Pleeeese remove this require from code... It just doesn't play well with bundlers.
I don't want to use this built-in .css I have my own. And now it's nearly impossible for me to make webpack ignore this css require from react-mapbox-gl so there is no duplicate css bundled

Just hit this issue as well... seems like a bad architectural decision, but maybe too early for me to say.  I got around this using this webpack plugin: https://www.npmjs.com/package/ignore-loader
Was able to use it because our team does not create any CSS files so we can simply have webpack ignore any attempt to require any CSS file.

I agree, think it should be removed for v5. Don't think there's anything to do for v4 releases in the meanwhile, though.

My solution is
const path = require("path");
module.exports = {
  resolve: {
    alias: {
      "mapbox-gl/dist/mapbox-gl.css": path.resolve(__dirname, "src/empty.js"),
    },
  },
};

This issue looks pretty old and important for me, so I create this pull request.
I hope get approved.
https://github.com/alex3165/react-mapbox-gl/pull/843

this also doesnt play well with the new Next.js version where you HAVE to import css fils in _app. Only solution is to use the, now not recommended, @zeit/next-css plugin...

this also doesnt play well with the new Next.js version where you HAVE to import css fils in _app. Only solution is to use the, now not recommended, @zeit/next-css plugin...

not familiar with the next-css plugin so how did you use it to work around this?

I faced the same problem... I spent some hours to understand and how could be the solution. And, as Mapbox allow "injectCSS: false" what is great at compilation time as @vasturiano said. But breaks at build time... so using both solutions: @vasturiano and @ryan-mahoney I was able to solve the problem.
next.config.js at custom webpack
config.module.rules.push({       test: /\.css$/,       loader: 'ignore-loader'     })
Some tsx
export const Map = ReactMapboxGl({   accessToken: config.get('accessToken'),   injectCSS: false })

this also doesnt play well with the new Next.js version where you HAVE to import css fils in _app. Only solution is to use the, now not recommended, @zeit/next-css plugin...

my PR solve this issue in new Next versions.
you add this in your _app
import 'mapbox-gl/dist/mapbox-gl.css';

and then you import your map inside your page
import ReactMapboxGl from 'react-mapbox-gl/src';

NOTE: because next try to do serverside render (SSR) and Mapbox require window object (that not exist in server)
you should have in mind that you will need load dynamics your component.
const MapView = dynamic<MapViewProps>(
  () => import('../../components/MapView/MapView').then(mod => mod.MapView),
  {
    loading: () => <LoadingLayer />,
    ssr: false,
  }
);


Uncaught Type error - exists is not a function. Integrating C library into node js

I am integrating a C library into a chrome app codebase that uses node js as well. I am using node-ffi for integration. But, when I am getting this weird error when I am trying to launch my application. I did replace your fix in bindings.js file as below
, exists = ((fs.accessSync && function (path) { try { fs.accessSync(path); } catch (e) { return false; } return true; }) || fs.existsSync || path.existsSync)
Still I am getting the same error. It is not allowing me to launch my application. Removing my ffi integration runs the chrome app well. Could you please help me with this issue?

This issue gets solved by removing the above line completely and replacing the exists(join code with fs.accessSync(join(dir, ........ code within a try...catch.

@TooTallNate Any suggestion on this issue?

Hello, I have this problem too. I'm trying to use node-rdkafka which depends on node-bindings. Is there any solution?

Also having this issue on a Raspberry Pi running Node 8.x<EMAIL_ADDRESS>Tried the fix mentioned in #20, which OP mentions with no luck. Any help?

I found out that both require('fs') and require('path') are returning undefined, and that's why exists remains undefined too (thus, 'not a function'). Maybe it has something to do with our environment and how things are set up? I'm using angular 4 and angular cli 1.2.3.

Can you try v1.3.0 please?

@TooTallNate, thank you very much for looking into this. V1.3.0 still gives the same error because there were no changes in the code, the last commit only removed a trailing space. Maybe you did a mistake when committing?

Are you sure? This should be the diff between v1.2.1 and 1.3.0: https://github.com/TooTallNate/node-bindings/compare/v1.2.1...v1.3.0

@alis-sol @EsoterikStare @TooTallNate  Hi People... Sorry for being late. I was not successful in solving it with direct integration. I had to run NodeJS server application and make a REST API call from AngularJS. I kinda worked around the problem.

@TooTallNate sorry for not being clear. I was already using commit 228973f because I previously had the problem related in issue #20. I meant that the only commit after that just removed a whitespace.
Besides "exists is not a function", I also get these warnings:
WARNING in ./~/bindings/bindings.js
81:22-40 Critical dependency: the request of a dependency is an expression
WARNING in ./~/bindings/bindings.js
81:43-53 Critical dependency: the request of a dependency is an expression
I found out that exists is undefined because require('fs') and require('path') both return undefined, but didn't throw any errors. I'm using angular 4 with angular cli 1.2.3. Maybe I'm doing something wrong / incompatible?
@rakeshgn31 thanks for taking the time to reply.

@TooTallNate @EsoterikStare any news?

@alis-sol I'm sorry to day, but this is an issue with your build setup/configuration. This module is intended to work with Node.js directly and if your build tooling is complaining then you kind of need to figure it out from there. There's not really anything I can do in this module to help.
@rakeshgn31 As for the original issue, if you're trying run this C library in the web browser, you might have better luck compiling the C library with Emscripten, though I warn that it's not the most user-friendly tool to get working nicely.
Please open a new issue for any further discussion. Thanks!


tomcat-vault doesn't work with older tomcats

There is Tomcat 8.0.15+ mentioned as required to run this library, but initializing vault with Tomcat 8.0.28 ends in exception:
Initializing Vault
Exception in thread "main" java.lang.NoSuchMethodError: org.apache.tomcat.util.res.StringManager.getManager(Ljava/lang/Class;)Lorg/apache/tomcat/util/res/StringManager;
	at org.apache.tomcat.vault.security.plugins.PBEUtils.<clinit>(PBEUtils.java:49)
	at org.apache.tomcat.vault.VaultSession.computeMaskedPassword(VaultSession.java:161)
	at org.apache.tomcat.vault.VaultSession.startVaultSession(VaultSession.java:191)
	at org.apache.tomcat.vault.VaultInteractiveSession.start(VaultInteractiveSession.java:77)
	at org.apache.tomcat.vault.VaultTool.main(VaultTool.java:120)

This is because getManager(Class<?> clazz) isn't in older version of tomcat-util.
Files with getManager(Class<?> clazz):
~/dev/tomcat-vault/src $ ack "getManager\(.*\.class\)" -l | sort
main/java/org/apache/tomcat/vault/security/ExternalPasswordCache.java
main/java/org/apache/tomcat/vault/security/Util.java
main/java/org/apache/tomcat/vault/security/plugins/PBEUtils.java
main/java/org/apache/tomcat/vault/security/vault/PicketBoxSecurityVault.java
main/java/org/apache/tomcat/vault/security/vault/SecurityVaultData.java
main/java/org/apache/tomcat/vault/security/vault/SecurityVaultFactory.java

I changed "newer" invocations of this method on my fork to use method with String attribute and it works just fine.

This should be closed since #53 was accepted.


Svelte Transition doesn't work on latest release 3.50.0

We will postpone upgrading svelte related dependencies.
As currently, the svelte transition doesn't work like before anymore.
This is the build with upgraded dependecies that does NOT work as expected:
bfcecdd56393ef493fc28bbca21007a030cda455: https://qwer-h6koe9ly0-kwchang0831.vercel.app
This is the expected behavior:
https://svelte-qwer.vercel.app
The issue is also noted @ sveltejs/svelte/issues/7828
Thanks 😄

It is now resolved with svelte 3.50.1.
See sveltejs/svelte/pull/7831.


fixed issed #34 : minPoint and maxPoint not properly mapped in dataformatter.cpp

I added a red rectangle to indicate the maxPoint position in VideoRoi.qml.
Note it is set as visible: false by default.
I used the same size as radSpotMeterRoi, I'm not sure if that makes sense.

Looks good to me. Thanks!


Support Remote Audio Clip Streaming

Issue #604
Problem: Remote Audio clips were not streamable

I fixed the tests so that it works. I had to provide the config via the function instead of access the global config.
I verified with "SAB PWA Test" in Matthew 4:12 (Remote Audio Clip) and Matthew 4:11 (Asset Audio Clip).
@Christopher-Shiu, thanks for working on this feature!


Parser improvements

I am currently getting started with MessageFormat and as a starting point I was reading your definition of the MessageFormat grammar.
Doing so, I noticed some minor things which could be done to simplify the pegjs grammar:

PegJS grammar:

Remove messageFormatPatternRight and directly use messageFormatElement within messageFormatPattern
Remove pluralStyle and selectStyle which were just forwarding to pluralFormatPattern respectively selectFormatPattern
simplified parsing of strings and ids

automatically compile the grammar in the development version
I added two new testcases for trailing and leading whitespace in strings

All testcases are passing for messageformat.js and lib/messageformat.dev.js

It looks like there are a bunch of failing tests in Travis, are those not from this change set?

Well, the Travis CI tests are not passing since I wrote them for the new grammar and the new syntax tree. For my local tests I replaced test/common.js with:
MessageFormat = require('../lib/messageformat.dev');

instead of
MessageFormat = require('../messageformat');

But I did not want to commit this change since it might break your testing infrastructure.
What should I do about this?

Or should I apply the changes I applied to lib/messageformat.dev.js to messageformat.js as well?
Sorry, I guess I just didn't understand your workflow

Ok, after having a look at some other pull-requests I noticed that changes have to be applied to both messageformat.js and lib/messageformat.dev.js. So I copied my changes over.
The tests in Travis CI on nodejs version 0.10 are passing now. The failing tests under nodejs 0.8 were not from this changeset and are already failing on your current master branch.

messageformat.js is a generated file. It's mostly a wrapper and adds in the parser. If my memory serves me right, you'd just run make in the root. (Might need some npm love first)

make worked almost immediately, but I modified the var mparser line so your regexp did not match anymore. Therefore I had to adapt my changes of lib/messageformat.dev.js first.
In order to avoid broken tests in the individual commits, I rebased my branch.

Thank you @vogelsgesang! I merged this, together with a couple more PEG optimizations & some whitespace cleanup. The previously failing node 0.8 tests were taken out in #88; we now test in node 0.10 & 0.12 and in iojs.
The current custom inlining of the compiled PEG parser will require some thought, and probably replacement.


Have one way to build static/karma.js

I just discovered the hard way that static/karma.js can be created with

grunt browserify or
npm scripts/client.js build

It seems like grunt watch relies on the first and travis relies on the second.
I propose to remove grunt browserify
@devoto13 WDYT?

I agree with grunt browserify removal. We should probably add watch mode support to the scripts/client.js at the same time as we remove Grunt counterpart to not reduce functionality.
And sorry that you had to learn it the hard way, I probably should have made the complete switch in a single commit instead of doing only part of the work.
PS The correct way to build the client it is outlined in the docs:
npm run build

If you use the watch feature please give a shot at the PR.  I've not used it so would have to learn ;-)


Cannot filter model years in query that uses comstock/resstock

copying from emails...
DAN:
Problem: Filtering model_year doesn't work with comstock/resstock because those datasets only have one year. If you query for model_year 2020, you will get nothing because 2018 is filtered out.
Proposed solutions:
Original behavior: Each dataset provides a duplication mapping. 2018 would map to every project year. The downside is that the intermediate dataset is duplicated 40+ times with redundant data. But I could go with this. We will usually have an exploded projection dataset.
Alternate 1: Apply filters after growth rate application. The downside is that you lose the chance to apply other filters before doing the growth rates.
Alternate 2: Make a new mapping type. Something like duplication_noop. While the duplication mapping uses the to_id column of the mapping and explodes the data, this would do nothing. It would prevent the filtering from removing anything. The downside is that it's a bit hacky.

ELAINE:
Long term: ExponentialGrowth datasets should be able to report out that they are, e.g., expanding the dimensionality of model_years, so can we filter non-affected dimension types first, apply growth rates, and then filter everything else?

DAN:
Special-case handling of model year would involve a redesign of the query code, possibly minor but maybe not. We currently attempt to treat all dimensions the same (some exceptions exist). The query code has one function to process a standalone dataset and another to process projections. The latter calls the former for each constituent standalone dataset. The function that processes a standalone dataset applies the filters.
Do we create a modified version of the filters before processing resstock/comstock based on this special case? That adds complexity and mucks up the data structures in the context object. But possible.

ELAINE:
I see how my preferred long-term solution is potentially challenging because of the (standalone datasets) -> (projections) workflow. Thus I propose that we sit on this for a while.

Yeah, I think w could split the filters into two types, one that can be applied to standalone datasets at the front and the other the end,  as the last query step before results. I think we can programmatically determine these filter types based on dimension records of standalone, project, and what is asked in the filter?

We already have a way to specify post-filtering (https://github.com/dsgrid/dsgrid/blob/dt/apply-growth-rates/dsgrid/query/models.py#L402). It didn't work until yesterday.
I suppose we could reduce the filter specifications from two to one, and then figure out the optimal time to apply them. It does make sense. Many users just want the data filtered and don't care when it happens.
Previously, we talked about giving the user fine-grained control over when the filters happen. For the main issue discussed here, pre-filtering 1-2 model years would save a ton of work over post-filtering (40x reduction in data that has to be mapped to the project's dimensions). So, regardless of the point, I think we need to be able to pre-filter ResStock model years.

My current opinion is that no changes are required for now.

Most users should specify post-filters.
For cases where a power user wants to specify a pre-filter they need to include all required dimension records for each dataset. In the example in this case, the query should have included 2018 in the pre-filter and then excluded it in the post-filter.

We could develop something more intelligent in the future.


[Bug][Module Name] CircleCI regex is not working to collect dat

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
When configuring the scope config the regex is not working

What do you expect to happen
It should collect data and show in DORA metrics.
How to reproduce
Go to - project - connections - scope config - transformations

No data collected when run.

Anything else
This is present since the installation.
Version
v0.21.0@ac4f7fe
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi, can you check if there is any records in the cicd_pipelines and cicd_deployments tables?

It seems to working fine on my local machine:


[NzSider] nzCollapsed is not respected when nzBreakpoint is set and viewport is larger than breakpoint

Reproduction link
https://stackblitz.com/edit/ngzorro-sider-not-respecting-collapsed-with-breakpoint
Steps to reproduce
Expand app window to open sider, and then refresh app. Sider will open by default.
What is expected?
Sider should not open by default when nzCollapsed is set to false.
What is actually happening?
It appears that the NzSider is overwriting nzCollapsed when the nzBreakpoint would force the drawer open (i.e., when going from a smaller viewport to a larger viewport).

Environment
Info

ng-zorro-antd
11.4.2

Browser
All

Can confirm this happens for me with ng-zorro-antd 12.1.0 / angular 12.
Any chance this will be fixed?
Are there any workarounds? The breakpoints are fixed, I'd rather not fork the project to adjust breakpoints/add bigger ones

I don't believe I had a workaround, I think we just removed the nzBreakpoint and let nzCollapsed do its thing.


[ISSUE-962] Distinguish between Disk LED Failure and Disk Recovery Failure of DriveRemovalFailed Event in Drive Replacement Procedure

Signed-off-by: Shi, Crane<EMAIL_ADDRESS>Purpose
Resolves #962
Create New Event type DriveLocateLEDFailed for LED lighting failure during drive replacement procedure
PR checklist

[ ] Add link to the issue
[ ] Choose Project
[ ] Choose PR label
[ ] New unit tests added
[ ] Modified code has meaningful comments
[ ] All TODOs are linked with the issues
[ ] All comments are resolved

Testing
Manually trigger the drive replacement procedure and its corresponding fake drive locate LED failure on an Atlantic (rke2) cluster. And then, from the restful API of listing Kahm events and issues, I've found the DriveLocateLEDFailed event produced and sent to Kahm.

So does this now show up as Reason "DriveLocateLEDFailed" under CSI-01 symptom code? How does this effect DriveRemovalFailed - error - failed lot locate LED as documented in https://confluence.cec.lab.emc.com/display/ATLANTIC/CSI+alerts+for+KAHM
Are there any KHAM changes required?

a) With this CSI code change, the following is the event I got from KAHM after locating drive LED failure in drive replacement procedure:
{
"id": "csi-baremetal-default-d612ba8b-9a91-4257-b07a-4211537ca060.17439bcb922e26d7",
"symptomid": "CSI-01",
"type": "Error",
"component": "csi-baremetal-node",
"message": "Failed to locale LED, Drive Details: SN='WSD6YXLR', Model='ATA ST8000NM012A-2KE', Type='HDD', Size='8001000000000', Firmware='CALD', Slot='/dev/sg13-15'",
"reason": "DriveLocateLEDFailed",
"appname": "csi-baremetal",
"namespace": "default",
"createdon": "2023-02-14T06:06:26Z",
"remedies": [
"Refer to www.dell.com/support/objectscale disk replacement procedure document to perform disk replacement",
"For additional information on this event, go to www.dell.com/support/objectscale and use the SymptomID to search support for the knowledge base article"
],
"updatedon": "2023-02-14T06:06:24Z",
"resourceID": "Drive/d612ba8b-9a91-4257-b07a-4211537ca060",
"count": 1
}
b) After this CSI code change, DriveRemovalFailed event will only cover "Failed to remove volume" and "Failed to release volume" in drive replacement procedure. The original "Failed to locale LED" in drive replacement procedure will not be covered by DriveRemovalFailed event anymore and will be covered by new independent DriveLocateLEDFailed event instead according to your requirement of distinguishing disk LED failure and disk recovery failure. After this PR merged to CSI master code branch, this change will be immediately synced to the doc https://confluence.cec.lab.emc.com/display/ATLANTIC/CSI+alerts+for+KAHM accordingly. The doc can't be changed now before code merge for consistency.
c)  I don't think there are any KHAM changes required. You can confirm this with KAHM developer.

Thanks for the response and example - Looks fine and based on what I see you are using CSI-01 so most likely no changes to KHAM since it does not have the ability to filter on "reason" field

OK.


App stuck in Riot animation on cold start

This happens in case of a cold start triggered by selecting a Riot notification.

After investigation, the app stuck on Riot animation in the 2 following cases:
1 - trigger a cold start from a Riot notification
2 - trigger a cold start after leaving a room

Done, assigned to @jeangb for testing

Validated


Denormalize quantity allocated

I want to merge this change because it uses denormalized field "quantity_allocated" from stock level in resolvers and calculations.

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Task linked: SALEOR-5064 Denormalize quantity allocated part 2.


[SDA-7436] Ensure operator roles have attached policies

Related issue: https://issues.redhat.com/browse/SDA-7436
What
Ensures operator roles have expected attached policy
Why
Upgrading of cluster could happen even though operator role didn't have attached policy

/hold

/retest


Suppress bootsnap require on DISABLE_BOOTSNAP

Bootsnap interferes with debuggers to the extent that breakpoints can't
be hit, so optionally, don't set up bootsnap when a debugger using
ruby-debug-ide is detected.
@mec this supersedes the solution you might have seen in your email in that it doesn't require any config change; we just detect the debugger and elect to not set up bootsnap when it's there.
This should let you get away from having to constantly check that the require you've commented out isn't being committed by accident 😄
Source: https://youtrack.jetbrains.com/issue/RUBY-20684#focus=streamItem-27-3183071-0-0

Nah, you haven't committed anything (but you have to be vigilant a lot and it's only a matter of time right?)
I went with the DISABLE_BOOTSNAP env var route before looking down the YouTrack bug report about it at JetBrains and finding that you can detect a debugger via ENV['RUBYLIB']. Both approaches would stop you having to be vigilant, but this approach means we don't have to configure anything either.
Sorry I didn't mean to drag you into it on a Sunday, I just had the time and knew I wouldn't get around to it tomorrow 😄
Are you still requesting changes?

Oh, the commit message. Damn, thought I'd fixed that.

Ok fixed the commit, thanks for spotting


Make the example copy pastable for noobs like me

This line actually causes an error:
// Rest of App come ABOVE the action button component!
Either mention that this line needs to be removed when using that block of code or mention it in a comment outside the return statement

I also added a PR with a complete example project. #39


OpenWhisk is not working properly

It seems OpenWhisk was updated and it no longer works with BluePic.

Turns out the issue I was having was not just me, Paul Castro was able to reproduce https://github.com/openwhisk/openwhisk/issues/1705
I will attempt a workaround by using REST API instead of Whisk.invoke

Since all the other functionality of BluePic is still working, we will wait on an OpenWhisk fix.

the open whisk issue was resolved and is working well now.


Prune repack: Failed to refresh lock

Output of restic version
restic 0.14.0 (v0.14.0-117-g7112a132c) compiled with go1.19.2 on darwin/amd64
How did you run restic exactly?
./restic -r sftp:backup:backup/foobar -p repo_pwd.txt prune --repack-uncompressed --compression max
repository a7513e38 opened (repository version 2) successfully, password is correct
loading indexes...
loading all snapshots...
finding data that is still in use for 24 snapshots
[0:09] 100.00%  24 / 24 snapshots
searching used packs...
collecting packs for deletion and repacking
[1:43] 100.00%  117952 / 117952 packs processed

to repack:        712588 blobs / 566.320 GiB
this removes:        429 blobs / 183.161 MiB
to delete:             0 blobs / 184.361 MiB
total prune:         429 blobs / 367.522 MiB
remaining:        712159 blobs / 566.113 GiB
unused size after prune: 0 B (0.00% of remaining size)

deleting unreferenced packs
[0:00] 100.00%  11 / 11 files deleted
repacking packs
Fatal: failed to refresh lock in timeked
[3:24] 0.03%  38 / 117952 packs repacked
Fatal: context canceled

What backend/server/service did you use to store the repository?
Sftp to a local network disk.
Expected behavior
I'd expect Restic to run the prune without failing.

Actual behavior
At 3 minutes in repacking packs restic puts out an error message Fatal: failed to refresh lock in time and ends the process a few seconds afterwards.

Steps to reproduce the behavior
I tried a few times with the same result every time.

Do you have any idea what may have caused this?
I was using the latest from master. After a few tries I downgraded to v0.14.0, recompiled, and the process seems to run without problems (the process is not finished yet though - I thought I'd report the possible bug now from fresh memory instead of waiting for the potentially very long time repacking).
So, could be related to #2715 ? IIRC the pull request landed to master a few days ago.
Other issue that I thought might be relevant is https://github.com/restic/restic/issues/3908#issuecomment-1231739981. However,  the memory usage by restic seems to be quite stable at around 550M, so no problems there.
Do you have an idea how to solve the issue?
A workaround for me was to use v0.14.0.
Did restic help you today? Did it make you happy in any way?
Restic is a delightful secure backup solution that works well in multiple environments (incl. RaspberryPi). 🙂👍

That is fallout from merging #3569. Actually the bug is quite embarrassing, see #3956.


Update the install instructions for golint

github.com/golang/lint/golint is no longer a valid URL.

https://secure.phabricator.com/book/phabcontrib/article/contributing_code/#no-pull-requests
See also #245?


allow to remove dimensions

allow to remove dimensions using empty values on the "replace_dimensions" parameters.
Example usage:
parameter: replace_dimensions
value: DIM1=,DIM2=newValue

I think we should be able to close this as #28 was merged and covers this functionality.

superseded by #28


Better BootstrapCDN output

More info https://github.com/MaxCDN/bootstrap-cdn/issues/460

If there were an easier way to extract the necessary information for the variation of bootstrap & "themes" (from Bootswatch) it would help reduce/eliminate the following code:
http://cgit.drupalcode.org/bootstrap/tree/includes/cdn.inc#n121
Especially the need for this:
http://cgit.drupalcode.org/bootstrap/tree/includes/cdn.inc#n224

#15 would semi-help with this I believe, but this issue goes a little further in "filling out" the missing/required assets... which may, incidentally, be more of a BootstrapCDN issue?

@jimaek we can do this but we'd essentially have to replicate @markcarver's parsing logic. This would be done in api-sync and would result in an enhanced bootstrap/bootswatch assets array, ala
{
        "version": "2.1.0",
        "themes": [
          "amelia",
          "cerulean",
          "cyborg",
          "journal",....
        ],
        "files": [
          "amelia/bootstrap.min.css",
          "amelia/bootstrap.no-icons.min.css",
          "cerulean/bootstrap.min.css",
          "cerulean/bootstrap.no-icons.min.css",
          "cyborg/bootstrap.min.css",
          "cyborg/bootstrap.no-icons.min.css",
          "img/glyphicons-halflings-white.png",
          "img/glyphicons-halflings.png",
          "journal/bootstrap.min.css",
          "journal/bootstrap.no-icons.min.css",
          "readable/bootstrap.min.css",
          "readable/bootstrap.no-icons.min.css",
          "simplex/bootstrap.min.css",
          "simplex/bootstrap.no-icons.min.css",
          "slate/bootstrap.min.css",
          "slate/bootstrap.no-icons.min.css",
          "spacelab/bootstrap.min.css",
          "spacelab/bootstrap.no-icons.min.css",
          "spruce/bootstrap.min.css",
          "spruce/bootstrap.no-icons.min.css",
          "superhero/bootstrap.min.css",
          "superhero/bootstrap.no-icons.min.css",
          "united/bootstrap.min.css",
          "united/bootstrap.no-icons.min.css"
        ]
      }

Unless I'm misunderstanding the issue, this would be a singular case that does not apply generically to any other library w/i the bootstrap cdn.

@UnbounDev How would the response format differ from our normal one in v2?

The structure of assets would differ; ala ~

Normal v2 assets

{
  mainfile: "",
  files: []
}

Bootswatch library v2 assets

{
  files:[],
  themes:[
    <themeName_1>,
    <themeName_2>,
    ...
  ]
}

@markcarver is that the format you're looking for?

Sorry, I've been a little busy lately. I'll try to word this a little differently and give some examples.
I don't think these need a dedicated themes category per se. They can, in theory, still remain in assets (like #15 suggests).
I don't think it really has much to do with how jsDelivr actually provides them via the API exactly, but I could be wrong. I still think the issue really lies in how BootstrapCDN provides its assets to begin with. That is why I had originally created https://github.com/MaxCDN/bootstrap-cdn/issues/460 instead of one in jsDelivr's issue queue.
The biggest pain-point is that while yes there are "themes" provided, they really lack any sort of context in which dependents are necessary to get said "theme" actually working.
The problem is further compounded by the fact that "themes" are also different per version, i.e.
the "paper" theme was introduced in versions 3.2.0 and higher, while the "amelia" theme was actually removed starting with versions 3.3.1 and higher.
For instance, for one to actually get the "paper" theme working (properly), they have to load: bootstrap.js in addition to the paper.css (which have different base paths too btw).
{
  "3.3.4": {
    "paper": {
      "css": ["//cdn.jsdelivr.net/bootswatch/3.3.4/paper/bootstrap.css"],
      "js": ["//cdn.jsdelivr.net/bootstrap/3.3.4/js/bootstrap.js"],
      "min": {
        "css": ["//cdn.jsdelivr.net/bootswatch/3.3.4/paper/bootstrap.min.css"],
        "js": ["//cdn.jsdelivr.net/bootstrap/3.3.4/js/bootstrap.min.js"]
      },
      "title": "Paper"
    }
  }
}

It's also even a little weirder when someone chooses the bootstrap_theme (the one provided by Bootstrap itself, not Bootswatch). The main bootstrap.css file must be loaded first too:
{
  "3.3.4": {
    "bootstrap_theme": {
      "css": [
        "//cdn.jsdelivr.net/bootstrap/3.3.4/css/bootstrap.css",
        "//cdn.jsdelivr.net/bootstrap/3.3.4/css/bootstrap-theme.css"
      ],
      "js": ["//cdn.jsdelivr.net/bootstrap/3.3.4/js/bootstrap.js"],
      "min": {
        "css": [
          "//cdn.jsdelivr.net/bootstrap/3.3.4/css/bootstrap.min.css",
          "//cdn.jsdelivr.net/bootstrap/3.3.4/css/bootstrap-theme.min.css"
        ],
        "js": ["//cdn.jsdelivr.net/bootstrap/3.3.4/js/bootstrap.min.js"]
      },
      "title": "Bootstrap Theme"
    }
  }
}

These JSON examples are just examples from the generated output of the links mentioned above.
Here is a the full list: http://pastebin.com/TqeLDgJc
Ignore the fact that the file is nested under "jsdelivr -> themes", that is just how I have currently configured the Drupal base-theme, "themes" could easily just be "assets".
IMO, what really needs to happen is that BootstrapCDN just needs to split out it's different "themes" into a proper structure based on:

Versions
Dependent assets
Min/non-min support

Oh, I guess I should also mention that I'm not entirely expecting all those variations met per se, more so that they are, at the very least, nested under the version and each respective "theme" name (as well as including the missing assets too).
I am certainly capable/willing to parse out the additional variations of css/js/min via based on matching the endings of the files:
{
  "assets": {
    "3.3.4": {
      "bootstrap_theme": [
        "//cdn.jsdelivr.net/bootstrap/3.3.4/css/bootstrap.css",
        "//cdn.jsdelivr.net/bootstrap/3.3.4/css/bootstrap-theme.css",
        "//cdn.jsdelivr.net/bootstrap/3.3.4/js/bootstrap.js",
        "//cdn.jsdelivr.net/bootstrap/3.3.4/css/bootstrap.min.css",
        "//cdn.jsdelivr.net/bootstrap/3.3.4/css/bootstrap-theme.min.css",
        "//cdn.jsdelivr.net/bootstrap/3.3.4/js/bootstrap.min.js"
      ],
      "paper": [
        "//cdn.jsdelivr.net/bootswatch/3.3.4/paper/bootstrap.css",
        "//cdn.jsdelivr.net/bootstrap/3.3.4/js/bootstrap.js",
        "//cdn.jsdelivr.net/bootswatch/3.3.4/paper/bootstrap.min.css",
        "//cdn.jsdelivr.net/bootstrap/3.3.4/js/bootstrap.min.js"
      ]
    }
  }
}

Also, I realize that my examples have the following base paths in them:
//cdn.jsdelivr.net/bootstrap/3.3.4/
//cdn.jsdelivr.net/bootswatch/3.3.4/
Currently these aren't included, but maybe they should be? I'm not entirely sure, especially given that these are technically two different repositories/libraries? I'm not sure how that actually works, because I thought it was provided by a single provider: BootstrapCDN.

Thanks for the details!
The JsDelivr data is not taken from the bootstrap api, rather, it is taken by scraping the relative github repo (an example being this folder relating to the bootswatch 3.3.4 version). This scrape is currently generic across all CDN's served by the API, as is the format of the associative assets field, where the goal is to provide component-style information on the desired projects and the files therein. While this structure works well for most libraries it fails a bit in the case of bootswatch b/c each bootswatch version is actually a collection of theme libraries.
I do not see malforming the assets field as an appropriate sol'n to the issue (as this is really pretty specific to the bootswatch library), I do see providing additional fields to compensate for the structures limitations in this case; e.g.
{
  "assets": {
    "3.3.4": {
      "files": [<files as usual>],
      "bootstrap_theme": [
        "css/bootstrap.css",
        "bootstrap-theme.css",
        "js/bootstrap.js",
        "css/bootstrap.min.css",
        "css/bootstrap-theme.min.css",
        "js/bootstrap.min.js"
      ],
      "paper": [
        "bootstrap.css",
        "js/bootstrap.js",
        "/bootstrap.min.css",
        "js/bootstrap.min.js"
      ]
    }
  }
}

Where each additional theme field maintains a list of files w/i that theme library. I don't see building the full url as advantageous given that the API's intent is to provide suitably formatted components not full paths to a given CDN.
@jimaek thoughts?

Yes, I thought that's what jsDelivr did (scrapping), but it is still just scrapping the single BootstrapCDN's repo (just in the bootswatch sub-folder).
i.e.:
https://github.com/MaxCDN/bootstrap-cdn/tree/develop/public
vs.
https://github.com/thomaspark/bootswatch
That's why I was thinking this is still somewhat of a BootstrapCDN issue (to provide the proper data structure to begin with)?
Yes, I agree about the paths (I hadn't considered different CDNs), but http://api.jsdelivr.com/v1/bootstrap/libraries doesn't include a base (or default) CDN base path at all.
Which is something that still confuses me is the disconnect between the api:
http://api.jsdelivr.com/v1/bootstrap/libraries (which includes all the sub-directories from BootstrapCDN)
and the actual path to said resource:
cdn.jsdelivr.net/bootstrap vs. cdn.jsdelivr.net/bootswatch
Why are these different? Am I using the wrong base path/URL? Isn't this kind of vital information to an API, even as an abstract top level property?

Cant we just consider each theme as a separate project and keep the exact same structure and format for all CDNs?

It's a good idea but we'd be losing the ability to see that those libraries actually belong to bootswatch, they'd have to be prefixed w/ something (i.e. bootswatch.<themeName>) and it would mean parsing all bootswatch theme library versions into their own library bucket on the back end (in api-sync). All of that is making this feel more like a hack.

I guess its  bootswatch.<themeName> vs special structure just for Bootstrap.
I personally vote for bootswatch.<themeName> what everyone else thinks?

@markcarver I'll defer judgement to you as you have the most insight into this use case; would you find a special structure just for the bootswatch library or the bootswatch.<themeName> approach more suitable?

@jimaek so we are going with each theme as a project named bootswatch.<themeName>, right?

yeah, lets do that

@jimaek I'm pretty sure v1 just got borked: http://api.jsdelivr.com/v1/jsdelivr/libraries/bootstrap (x-ref: https://www.drupal.org/node/2657138)
It no longer has the bootswatch stuff from BootstrapCDN
Shouldn't any changes made have only been applied to v2 stuff? I'm a little confused with how y'all are defining v1 and v2 stuff TBH. This isn't the first time that stuff like this has happened.

Sorry, wrong URL above:
http://api.jsdelivr.com/v1/bootstrap/libraries has the new bootswatch.<theme> entries, but it's v1! These changes should ONLY be showing up in v2... whatever that URL is...
Also, sorry for the late reply, I did not see https://github.com/jsdelivr/api/issues/56#issuecomment-109637810 till just now.

bootswatch.<themeName> vs special structure just for Bootstrap
bootswatch.<themeName> is fine by me (I just saw the new structure). I can parse the themes individually easily enough by matching bootswatch. from the key.

@markcarver you are right. All versions use the same datastore and it isn't really possible to return a different list of projects for each API version (ok, it certainly is possible, but not without extremely ugly hacks), so this affected v1 as well.
I recognize that this is somewhat a breaking change, but I also don't think returning a different set of projects depending on whether you use v1 or v2 is a good idea. I think we could add all those theme files back to bootswatch, while also keeping them as individual projects. What do you think?

so this affected v1 as well

Um... no! The whole reason APIs have "versions" is to assist with not breaking other software that consumes it (which is also versioned and deployed itself).
https://www.drupal.org/project/bootstrap has >94,000 installs and y'all just broke every single one of those install's UIs (which relies on this API to provide versions and themes in a select dropdown https://www.drupal.org/node/2657138).

I think we could add all those theme files back to bootswatch, while also keeping them as individual projects.

That would certainly (temporarily) "fix" the problem, but you're kind of also missing the point of what API "versions" are. You shouldn't be fiddling around with existing (stable) APIs. That's just ludicrous.

I'll be honest, I'm a little miffed by such a cavalier response to this.

it isn't really possible to return a different list of projects for each API version (ok, it certainly is possible, but not without extremely ugly hacks)

What is the point of the v1 in the URL then??? I know it may not be "easy" on the backend, but a simple change in the URL to v2 and bam, different results.

but you're kind of also missing the point of what API "versions" are.

The API version gives you a guarantee of where you can get the data (i.e., endpoints), and what shape the data are (i.e., response model). The data itself are (almost) always dynamic. If you were using GitHub API to get a list of files in a repository and the repository got deleted, you would end up in the same situation.
The only difference here is that with CDNs, once the files get published, we expect them to be there indefinitely. That's why I said removing them can be seen as a breaking change in this case, but new projects can be (and are being) added all the time...

what shape the data are (i.e., response model)

Exactly........ which is what changed.........
What I'm talking about has absolutely nothing to do with the  "projects" or "files" themselves. The underlying BootstrapCDN/files really hasn't changed all that much, for a long time actually.
It has everything to do with how this "API" parses and reconstructs BootstrapCDN's assets into a new data modal. This process is what constitutes jsDelivr as "authoritative" since YOU determine where the parsed and reconstructed files "show up" in this compiled data model.
This is why existing code broke when you suddenly changed what it expected from "v1".
This has happened before (#94). This kind of behavior is not acceptable from an "API".
If you can't clear up what "v1" and "v2" means by a URL, then you have no business calling them two different "versions" when you actually only have ONE endpoint.
This is extremely misleading and almost enough for me to consider abandoning this "API" since you keep messing around with existing endpoints.

I agree 100% with @markcarver on this one. I have hundreds of sites using the Bootstrap theme, and they are all currently broken because of this. This is the second time this has happened.
Can you please revert the commit until a proper solution is figured out?

Thanks for reverting @MartinKolarik - does this go live immediately, or is there a deployment process? Just want to know if I need to start putting out fires, or if they will go out by themselves...

@mstenta If I could I'd have reverted it right away, but we need to wait for @jimaek to merge it. Expect a couple of hours as he's in UTC+1 timezone.

At first I thought this just affected the UI (which is still a pretty big bug), but it turns out that it actually causes sites to become completely broken after its Drupal cache has been cleared. Example: https://dreditor.org/

I understand the timezone thing, here's hoping the revert can be deployed ASAP.

Sorry for any problems that this caused. The change was reverted earlier today and the API now works as before.
@markcarver

but it turns out that it actually causes sites to become completely broken after its Drupal cache

To be honest, that seems like something that could be improved on your end. Once the user selects a theme, you can store the needed URLs in some kind of persistent storage. Even if the API went down, it shouldn't affect anyone except people trying to change the theme at that moment. Correct me if there's actually a good reason why you can't do this.
Once again, this was clearly a problem on our end, and we'll do our best to prevent this from happening in the future. Just saying that you also have the ability to make your theme more reliable.

Once the user selects a theme, you can store the needed URLs in some kind of persistent storage. Even if the API went down, it shouldn't affect anyone except people trying to change the theme at that moment.

Sure. I can certainly take some responsibility here on that front. I'm not entirely sure how I'll do it though given how convoluted Drupal's theming system is. I'll likely have to manually build in even more redundancies.
I get this isn't a perfect world and things break. However, the "versioning" jsDelivr thinks it is providing needs some very serious refactoring as I have said in https://github.com/jsdelivr/api-sync/issues/48#issuecomment-175834957.


[UNDERTOW-930] Setting default encoding doesn't affect HttpServletRequest.characterEncoding

https://issues.jboss.org/projects/UNDERTOW/issues/UNDERTOW-930

Can one of the admins verify this patch?

Squashed and merged, thanks


Plugin options schema

Motivation
https://www.gatsbyjs.com/docs/configuring-usage-with-plugin-options
TODO:

[ ] Change version number
[ ] Release beta

Checklist

[ ] Code follows coding conventions held in this repo
[ ] Automated tests have been added
[ ] Tests are passing
[ ] Docs have been updated (if applicable)
[ ] Temporary settings (e.g. variables used during development and testing) have been reverted to defaults

How to test
If manual testing is required, what are the steps?

I have added a test and add the forgotten includeRawContent property in options.

I have added a test and add the forgotten includeRawContent property in options.


Add alias for loading YouTube Music albums

Lavaplayer does support loading YouTube Music album/playlist only if its in a correct form.
Currently lavaplayer doesn't support loading this type of youtube music album urls.
Here's an example album url (/browse): https://music.youtube.com/browse/MPREb_d8mqe4d4UR0
Lavaplayer will just raise error upon passing this album url. (which eventually redirects to actual playlist url upon clicking manually)

Doesn't this already exist inside the code? YouTube Music Albums are not different from YouTube Playlists?
And if so, removing the music. at the domain directs you towards a youtube playlist.

Just tested it with my bot using latest release.

I am unsure thou, how the url in the Issue description has been found, its valid but redirects to a playlist url.

Just tested it with my bot using latest release.
I am unsure thou, how the url in the Issue description has been found, its valid but redirects to a playlist url.

Hey, pardon, I just updated the issue. Its true lavaplayer can load /playlists/... format albums but it cannot load /browse/... format albums. Why does it matter if you say, some youtube music searcher returns /browse/... type of albums rather than /playlists/... which makes it hard to directly pass the url in lavaplayer.
Yes, we can indeed find out the redirected url ourselves. But i think lavaplayer still should support this url alias.

I tried solving this thing sadly couldn't do much. Since there is no active redirect but rather a location change via js. But it seems like if you get past the consent page that loads first you should be able to just check if there is any entry for
https:\/\/music\.youtube\.com\/playlist\?list=([a-zA-Z0-9_-]{11})

Because the playlist id is written into the site.


Unfold line handle

The unfold handle hit-box from right edge of relevant "..." button to end of the folded line are much less ergonomic than if it would be a normal space that would place cursor to end of the line without the unfolding.

@Ilias48rus Can you add a screenshot to help illustrate what you mean?

@RMacfarlane

@Ilias48rus  Is this a dup of https://github.com/Microsoft/vscode/issues/53886 ?

@aeschli yes, sor

np, just wanted to be sure. Marking as dup of #53886


Fix quote

When adding extra config
{{- if .Values.cluster.config }}
{{ toYaml .Values.cluster.config | indent 4 }}
{{- end }}

Will produce invalide configuration
    gateway.recover_after_master_nodes: ${RECOVER_AFTER_MASTER_NODES:2}
    gateway.recover_after_data_nodes: ${RECOVER_AFTER_DATA_NODES:1}
    'thread_pool.bulk.queue_size: 350'
  log4j2.properties: |-
    status = error
    appender.console.type = Console

Bump for CLA check.

A good pattern that you may want to follow here is the with statement.
{{- with .Values.cluster.config }}
{{ toYaml . | indent 4 }}
{{- end }}

@jmdots
helm upgrade --install eslog ./charts/elasticsearch --namespace kube-system --set cluster.config="thread_pool.bulk.queue_size: 350" --dry-run --debug
 {{- with .Values.cluster.config }}
{{ toYaml . | indent 4 }}
{{- end }}

Generate this code
     gateway.recover_after_master_nodes: ${RECOVER_AFTER_MASTER_NODES:2}
    gateway.recover_after_data_nodes: ${RECOVER_AFTER_DATA_NODES:1}
    'thread_pool.bulk.queue_size: 350'

  log4j2.properties: |-

/ok-to-test

cc @icereval

/assign

ping @icereval

/lgtm

/LGTM

/lgtm

/retest

Are the pull-charts-e2e Job test new since the last merge PR ? https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/pr-logs/pull/charts/4721/pull-charts-e2e/7987/
Because, I do not think these tests have ever worked.
Charts Default number of master seems incorrect.
I0523 18:56:37.105] [2018-05-23T18:38:29,959][WARN ][o.e.d.z.ZenDiscovery     ] [elastic-10083-1-elasticsearch-client-6864d58669-r5zt5] not enough master nodes discovered during pinging (found [[]], but needed [2]), pinging again
I0523 18:56:37.106] [2018-05-23T18:38:32,970][WARN ][o.e.d.z.ZenDiscovery     ] [elastic-10083-1-elasticsearch-client-6864d58669-r5zt5] not enough master nodes discovered during pinging (found [[]], but needed [2]), pinging again```

@azman0101 Please merge int the latest master.

The chart has changed a lot in the mean time. I'm closing this as more or less obsolete.


Expand generative panel

In collaboration with @JbIPS, the generative panel is going to be refactored
General philosophy
Discussed with @eollion
A panel allowing the user to use third-party end points to annotate text elements with a prompt :

Configure the third-party end point
Expertimental step : Enter a prompt and experiment with its results on a few elements (type of inference, format of the result) + Rules to check the formating of the inference (check list : JSON format, regex extraction, etc.)
Complete step Launch a complete inference on a specific sample (all elements, a number of elements, all untagged elements, etc.) + manage the process (possibility to stop it, prevision of time, error management)

Identified Tasks

[ ] Add openai endpoint + key
[ ] Prototype of a design for the frontend separating experimentation / complete prediction

(to be updated)

I just found a project that could be an inspiration for models integration: https://github.com/open-webui/open-webui
I'll look into it and use any piece of code that could help for OpenAI integration.

Mmmh not a bad idea to have a chat-like section for the exploration part, using such connector, for people to try their prompt etc. with their API, before launching the process on the complete dataset.


Fix registration or setup errors for the migration to 1.18.2 to 1.20.1

This may also cover anything not covered by:
#96 Fix errors in chessmod.client.gui and chessmod.client.render
#98 Fix errors related to networking changes between 1.18.2 and 1.20.1

Registration.java:

[ ]  Fix SoundEvent. This can Be done by looking at source code of open source 1.20 projects (such as Rats)


On the front page, I do not understand explanation of 4:2:2 etc

The text says "y is the number of changes of chroma samples between the first and seconds rows of a pixels."
But isn't it more accurate to say:
"y is the number of changes of chroma samples between the first and last rows of a pixels."
If not, I still don't understand how chroma subsampling is used!

The sentence referes to the grid that is taken as a reference for chroma subsampling. When you say 4:*:* you mean a grid that has 4 columns and 2 rows (the 2 is fixed). So the y is the number of changes between the first row in the grid and the second row in the grid.
We had a discussion about chroma subsampling previously in #24, you might find useful reading it :)

So the grid is not always 4 by 4 pixels? I don’t know why I assumed that but I did...

25 juni 2019 kl. 18:33 skrev Matteo Contrini<EMAIL_ADDRESS>The sentence referes to the grid that is taken as a reference for chroma subsampling. When you say 4:: you mean a grid that has 4 columns and 2 rows (the 2 is fixed). So the y is the number of changes between the first row in the grid and the second row in the grid.
We had a discussion about chroma subsampling previously in #24, you might find useful reading it :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

It's usually 4 by 2, with some uncommon exceptions like 4:1:0 and 4:2:1, according to Wikipedia.

I may create sample images of how I understand the situation... but later in that case.

Sampling of components VS itensity


No OpKernel was registered to support Op 'Ceil'

I'm running tensorflow on android. And it reports a exception of one of my op 'Ceil'. The exception info is as below:
Caused by: java.lang.IllegalArgumentException: No OpKernel was registered to support Op 'Ceil' with these attrs.   Registered devices: [CPU], Registered kernels:  <no registered kernels> [[Node: model/frame/Ceil = Ceil[T=DT_DOUBLE](model/frame/truediv)]]    at org.tensorflow.Session.run(Native Method)
I believe Ceil is a basic op and it should has CPU implement. So maybe I miss sth. ?   ( I clone tensorflow master branch and build the lib and java interface on that)

@petewarden can you take a look? I never touched Android or Java side of TensorFlow, but it doesn't seem like there's anything special about Ceil that would cause it not to work

This is most likely due to double not being supported by ops by default on mobile TF. You can try converting your double ops to float, or building with ANDROID_TYPES_FULL defined, which will enable doubles in types.cc)

@liuzqt Try including cwise_op_ceil.cc in tensorflow/core/kernels/BUILD file under filegroup "android_extended_ops_group1" and rebuild..

@andrewharp: Casting the argument of tf.ceil to float32 does not help.

@anandcu3
It works! My steps are like this:

Clone tensorflow1.4.0
including cwise_op_ceil.cc in tensorflow/core/kernels/BUILD file under filegroup "android_extended_ops_group1"
including "tensorflow/core/kernels/cwise_op_ceil.cc" in "tensorflow/contrib/makefile/tf_op_files.txt"
Import projects "tensorflow/examples/android" using Android Studio.
Modify build.gradle:  def nativeBuildSystem = 'bazel'  --> "makefile"
Rebuild the android projects.

It has been 14 days with no activity and the awaiting tensorflower label was assigned. Please update the label and/or status accordingly.

Nagging Awaiting Response: It has been 14 days with no activityand the awaiting response label was assigned. Is this still an issue?

Automatically closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!

@anandcu3
It works! My steps are like this:
1. Clone tensorflow1.4.0

2. including cwise_op_ceil.cc in tensorflow/core/kernels/BUILD file under filegroup "android_extended_ops_group1"

3. including "tensorflow/core/kernels/cwise_op_ceil.cc" in "tensorflow/contrib/makefile/tf_op_files.txt"

4. Import projects "tensorflow/examples/android" using Android Studio.

5. Modify build.gradle:  def nativeBuildSystem = 'bazel'  --> "makefile"

6. Rebuild the android projects.

Hello, I recently transplanted the tensorflow project to Android. When I transplanted tf-detection, I encountered the same problem as you. When I transplanted the detect-model  to Android, I encounter the same error. I still don't understand your steps. I still can't run through Android at present. Can we contact by email<EMAIL_ADDRESS>thank you very much.


ConnectionEndPoint and _clientNodeEdgePoint/_serverNodeEdgePoint

While working on a Service connection, got a doubt.
ServiceConnectivity owns a Connection. A Connection owns ConnectionEndPoint.
A ConnectionEndPoint as the following two properties: _clientNodeEdgePoint and _serverNodeEdgePoint
What is the use/difference of the two?
@karthik-sethuraman

W.R.T the figure about, in a multi-layer network stack, a ConnectionEndPoint (and associated connection) in a given layer (e.g. ODU) is supported by the NodeEdgePoint (and the associated Link) at that layer. This relationship is captured via the _serverNodeEdgePoint property. At the same time, this connection (and associated ConnectionEndPoint) and its associated trail could support client-layer Links (and client-layer NodeEdgePoints). This relationship is captured via the _clientNodeEdgePoint property.


Starter kit package update (Nuxt2-pinia-tailwind) - Minor updates/patches only

Background
This ticket aims to update the Nuxt2-pinia-tailwind starter kit to address out-of-date package patch cycles.
Only do yellows and greens.
Don't do major upgrades with breaking changes or changes that would change the identity of the kit, prioritize bringing minor patches up to current.

Acceptance

[ ] Update yellow and green packages
[ ] Verify everything still works as expected

Is there anything you can update on this @danecando? I noticed this is attached to the closed https://github.com/thisdot/starter.dev/pull/1027 from a couple of hrs ago.

@WillHutt I'm gonna open a new ticket this one just needs a full update even the minor updates of the important packages are a lot of breaking changes