[Bug] SAS workspace start with error

I had trouble starting a SAS workspace after the upgrade:

A known bug I'm working on getting debugged and fixed, didn't show up during testing, that occurs when only 1 "My Study" is linked to any type of workspace.  I had hoped to get it resolved by now but Fate intervened, it is a priority item I'm working on.  The workaround in the meantime to avoid the error (which is specifically "Policy statement must contain resources") is to select the "My Study" desired for use, as well as one of the Organization or Public studies, and then the IAM policy gets resources populated and the workspace will launch.  As soon as I figure out why it does this with just the 1 "My Study" linked, I'll update this issue.  I'm getting the minor-version upgrade from 5.2.2 to 5.2.7 tested and rolled out ASAP, which may fix the issue, but if not I have some idea where to start.

What I did was selecting the previsioned Organization Study "GROUSE-MUIRB2057285-BC" (our recommended way to researchers),

and deployed the SAS workspace under it.
Are you suggesting that we should first create a My Study , selecting both the My Study and targeted Org Study, and then deploy SAS?

It just needs to be more than 1 study selected as far as I've seen yet, one of which can be one of the public data sources (third tab). However, creating and selecting a My Study as well as their Org Study would also work, and might be a better idea to provide them a non-shared space for storing things, as a workspace launch procedure adjustment, which would also buy more time to get this issue resolved without blocking use... yeah, I recommend that. I'd only seen this occur with My Study selections, not Org Study selections (and I tested that, but not against the Research-GPC account yet), so this gives me another use case to debug.
Note that its any workspace type, not just SAS, that this impacts...

Just tried the recommended approach, and still ended up with error:

Argh.  Well, the only difference I can see from what I had tested as working, is it being a Research-GPC project and study... :(  Can you test the workaround approach against a non-Research-GPC project and study, please?  Regardless, working on getting it fixed ASAP still, as I know it presents a major problem.

Can you give me 1 week please?

By next Wednesday or sooner, I mean...

That should work.

Actually, as I think about it, connecting a MyStudy with a Org Study makes sense to me, operation-wise. In that way, the researcher will be able to have both a personal storage space and a shared storage space. I will just need to modify my training instruction accordingly.

I will report my testing with "UMBMI-Application-Prod-Project" in a little bit.

Updating the account onboard stacks again is one of the things I'll be trying today, very carefully, yeah :)

I will report my testing with "UMBMI-Application-Prod-Project" in a little bit.

Still errored out...

(weird... I can't attach figures...)
The following is the error message:
Error provisioning environment Song-test-upgrade-windows-workspace. Reason: Errors from CloudFormation: [{LogicalResourceId : SC-564303459249-pp-ovfbbwj2h4fqe, ResourceType : AWS::CloudFormation::Stack, StatusReason : The following resource(s) failed to create: [IAMRole]. Rollback requested by user.}, {LogicalResourceId : IAMRole, ResourceType : AWS::IAM::Role, StatusReason : Policy statement must contain resources. (Service: AmazonIdentityManagement; Status Code: 400; Error Code: MalformedPolicyDocument; Request ID: be5238ca-d25f-43bb-8baf-a581b7e3a744; Proxy: null)}, {LogicalResourceId : IAMRole, ResourceType : AWS::IAM::Role, StatusReason : Resource creation Initiated}, {LogicalResourceId : SecurityGroup, ResourceType : AWS::EC2::SecurityGroup, StatusReason : Resource creation Initiated}, {LogicalResourceId : InstanceRolePermissionBoundary, ResourceType : AWS::IAM::ManagedPolicy, StatusReason : Resource creation Initiated}, {LogicalResourceId : SC-564303459249-pp-ovfbbwj2h4fqe, ResourceType : AWS::CloudFormation::Stack, StatusReason : User Initiated}]

It may have worked for me due to the admin role and having my user linked to all existing projects.

The issue does not seem to be manifesting under the from-fresh Sandbox SWB environment, so I can use that as a comparison (it's relatively customization-free also) to find and fix the potentially missing or incorrect piece of the puzzle.  The account onboard stacks are up-to-date, verifying both in CloudFormation against the onboard.cfn.yml shipped with the v5.2.2 source, and in SWB's Accounts section, so the problem may be in the workspace templates or parameters; I'm  reviewing and comparing stack parameters being passed in between these 2 working and not-working SWB environments for the same workspace type also.  The error seems to indicate that a policy that is supposed to be passed in, is empty, but the parameters for the workspace stacks that failed don't show an empty IamPolicyDocument (what I first suspected) and that parameter is as-expected for the selected study/studies.  However, even though the new Egress Store feature they introduced is disabled (since we haven't had time to test that or train people on its use if we wanted to implement it), I do see an empty EgressStoreIamPolicyDocument parameter being passed in still, which may be the empty policy statement that's tripping the whole stack up... starting there on fixing this...

@fergusonsha-umkc please feel free to reach out to SWB support team (Nathan and Travis) if needed.

OK, figured out why the org study I tested under the Dev environment, passed, alone and in combination... it is from an external data source, not an org study under the host account.  Seems this is impacting studies living under the host account, only.  This helps me narrow things down and explains some mysteries... I also identified the empty Resource value in the iamPolicyDocument parameter (the parameter itself is not empty, but that value is, for a permission set its trying to add), now I can trace back through the templates, where iamPolicyDocument gets built, to determine why.

Going to do the minor-version upgrade to latest 5.2.7 release, minimally disruptive, in the hopes of introducing positive change and to make sure we're on their latest release before reporting a bug.

Can you include the wiki page url here?

https://github.com/Missouri-BMI/NextGen_Cloud_Architecture_AWS/wiki/AWS-SWB-Minor-Release-Upgrade-Procedure
I've already added it and the major-version upgrade process I performed, going from v3 to v5, in the wiki's nav sidebar under Change Management also :)

Update: Sagemaker and Linux workspaces and configurations are rebuilt and pass iterative testing across single and multiple combinations of study selections, in the Dev SWB 5.2.7 environment.  Working on rebuilding and testing Windows, SAS, and CLAMP workspaces and configurations....

Update: Windows and SAS workspace configurations are recreated and tested as launching against studies ok, however I am now debugging an issue in our v5.2 Windows templates, under v5.2.7 the powershell preinstall scripts created in the template are not running properly.  Initial suspicion is that they changed or removed a variable that was being used in the Powershell commands to specify the environment-bootstrap-scripts bucket.  Always some new wrinkle... but on track still!

HAH!  Problem was not in the templates, whew.  The 5.2.7 upgrade reset the contents of the bootstrap-scripts bucket, which would be why none of our custom files could be found when running the installerDonwload.ps1 constructed script 🤦♂ So I should just need to restore our custom scripts and installer files from the Prod or Sandbox bucket to fix it... short-term, along with adding instructions to the upgrade wiki doc to compensate for this possibility.  Long-term, will probably move our custom files into our own custom bucket instead of using their bucket, so it doesn't get clobbered during an upgrade again.

Wiki doc updated and installer files/scripts restored, testing all Windows workspaces again.

Windows workspace testing is showing positive results, for both single and multiple study connections; going to do further testing for all workspace types under the researcher role now, this morning, and then begin prepping to upgrade Production in kind aiming for minimal disruption.

@sxinger if you have time today could you also do some testing in Dev SWB to give additional validation?  Appreciate it :)

I've been hesitant to add Research-GPC to the Dev SWB environment in case it should conflict with the Prod SWB stack resources, but I'll look into that.

All my tests have passed under Dev, so I am preparing everything to get Production updated and tested after-hours today.

@sxinger if you have time today could you also do some testing in Dev SWB to give additional validation? Appreciate it :)

I tried out several use cases which I think is more relevant, my acceptance test reports are as follows:

Single Org Study with SAS workspace - pass
Org Study + Public with Sagemaker - pass
Org Study + MyStudy with standardized windows - pass
Org Study + MyStudy with standardized linux - pass

Excellent, thanks very much!

Doing Production upgrade now...

Production upgrade complete, workspace configurations updated, testing and re-enabling workspaces as they succeed

All workspace types passed launch testing against various study selections, in Production.  Please also test things out before we close this issue as resolved.  Thanks!
(P.S. Making another attempt to influence the display order of workspace types for better flow, is still on my radar also.)


rule idea: check OS version new/update

Add new rule or update existing to detect OS version checks via following kernel32 APIs:

VerSetConditionMask
VerifyVersionInfo

Hello @mike-hunhoff .
I will work on that rule.

sample: 8ed9a60127aee45336102bf12059a850

Hi @johnk3r! Thank you for finding a sample. I will assign this task to you, thank you!

[ ]     VerSetConditionMask
[ ]     VerifyVersionInfo

@mike-hunhoff ,
Would it be interesting to leave in the same rule?
I ask why the API GetVersion (Ex) was deprecated, too, we will need to make adjustments to the rule that is in production.
https://github.com/fireeye/capa-rules/blob/master/host-interaction/os/version/get-os-version.yml

@johnk3r looking back at the existing rule get-os-version.yml I feel it should instead be named check-os-version.yml to better fit the intention. With this change the rule you added in fdf3afe could be combined with the existing rule.
Does it sound reasonable to rename the existing rule get-os-version.yml to check-os-version.yml and combine it with your rule committed in fdf3afe? I feel this is a better fit all around and improves the existing rule.

Hello @mike-hunhoff ,
I have an open PR. Once it's completed, I'll update this rule.
Grateful

Hi,
I will work on that rule again.

Hi,
I will work on that rule again.


clusteredSegmentation is broken

commit f2945963d
trying it with a valid file, works for the FluidNoveltySlice but then aborts:

Traceback (most recent call last):
File "clustered_segmentation.py", line 21, in
w.run()
File "/Users/pa/Documents/documents@hudd/research/projects/fluid corpus navigation/research/ftis/ftis/ftis/world.py", line 109, in run
c.walk_chain()
File "/Users/pa/Documents/documents@hudd/research/projects/fluid corpus navigation/research/ftis/ftis/ftis/corpus.py", line 47, in walk_chain
forward_connection.walk_chain()
File "/Users/pa/Documents/documents@hudd/research/projects/fluid corpus navigation/research/ftis/ftis/ftis/common/analyser.py", line 167, in walk_chain
forward_connection.walk_chain()
File "/Users/pa/Documents/documents@hudd/research/projects/fluid corpus navigation/research/ftis/ftis/ftis/common/analyser.py", line 151, in walk_chain
self.run()
File "/Users/pa/Documents/documents@hudd/research/projects/fluid corpus navigation/research/ftis/ftis/ftis/analyser/meta.py", line 144, in run
singleproc(self.name, self.analyse, self.input)
File "/Users/pa/Documents/documents@hudd/research/projects/fluid corpus navigation/research/ftis/ftis/ftis/common/proc.py", line 28, in singleproc
process(x)
File "/Users/pa/Documents/documents@hudd/research/projects/fluid corpus navigation/research/ftis/ftis/ftis/analyser/meta.py", line 116, in analyse
mfccs = fluid.mfcc(
File "/Users/pa/anaconda/envs/ftis4dummies/lib/python3.8/site-packages/flucoma/fluid.py", line 469, in mfcc
fftsettings = fftsanitise(fftsettings)
File "/Users/pa/anaconda/envs/ftis4dummies/lib/python3.8/site-packages/flucoma/utils.py", line 15, in fftsanitise
int(fftsettings[2])
IndexError: list index out of range

Hi PA,
It looks like fftsettings for the mfcc() function are not able to be sanitised because it expects to get 3 values as a list and it cannot index the last value.
Can you post the script here for reference?

This is fun, since I am not changing them at all...
`from ftis.world import World
from ftis.corpus import Corpus
from ftis.analyser.meta import ClusteredSegmentation
from ftis.analyser.slicing import FluidNoveltyslice
from ftis.adapter.reaper import render_tracks
from ftis.common.io import get_sr
from pathlib import Path
c = Corpus("/Volumes/machins/projets/newsfeed/sons/textes/Audio/synth/fromtexttospeech-AmE-George.wav")
nov = FluidNoveltyslice(threshold=0.05, minslicelength=1, fftsettings=[1024,128,1024], filtersize=5, kernelsize=29)
if we dont set the minslicelength to 2 then we might generate slices too short for the analysis
seg = ClusteredSegmentation()
c >> nov >> seg
w = World(sink="~/Desktop/clustered_segmentation")
w.build(c)
if name == "main":
w.run()
tracks = {}
for media, slices in seg.output.items():
    pos = 0
    sr = get_sr(media)
    items = []
    for start, end in zip(slices, slices[1:]):
        start /= sr
        end /= sr

        item = {
            "file" : media,
            "length" : end - start,
            "start" : start,
            "position" : pos
        }

        pos += end - start

        items.append(item)

    tracks[media] = items

render_tracks(
    Path("~/Desktop/clustered_segmentation/clustered_slices.rpp").expanduser(),
    data = tracks
)

`

Okay, I do remember we edited the FTIS class ClusteredSegmentation() though so could you dig into that class definition and see what the internal MFCC fftsettings are?

I deleted the edits, this is a new env and a new pull. So the internals are as is in the commit:
       fftsettings=[4096, 1024, 4096],

Gotchya, I shall investigate and report back

It is a missing comma. Fixed (I think). Can you test? dcd9f1f168dc3844fdf7dd612ffa54ddd5b88d17

not working despite the comma, but a new bug:
Traceback (most recent call last):
  File "clustered_segmentation.py", line 21, in <module>
    w.run()
  File "/Users/pa/Documents/documents@hudd/research/projects/fluid corpus navigation/research/ftis/ftis/ftis/world.py", line 109, in run
    c.walk_chain()
  File "/Users/pa/Documents/documents@hudd/research/projects/fluid corpus navigation/research/ftis/ftis/ftis/corpus.py", line 47, in walk_chain
    forward_connection.walk_chain()
  File "/Users/pa/Documents/documents@hudd/research/projects/fluid corpus navigation/research/ftis/ftis/ftis/common/analyser.py", line 167, in walk_chain
    forward_connection.walk_chain()
  File "/Users/pa/Documents/documents@hudd/research/projects/fluid corpus navigation/research/ftis/ftis/ftis/common/analyser.py", line 151, in walk_chain
    self.run()
  File "/Users/pa/Documents/documents@hudd/research/projects/fluid corpus navigation/research/ftis/ftis/ftis/analyser/meta.py", line 144, in run
    singleproc(self.name, self.analyse, self.input)
  File "/Users/pa/Documents/documents@hudd/research/projects/fluid corpus navigation/research/ftis/ftis/ftis/common/proc.py", line 28, in singleproc
    process(x)
  File "/Users/pa/Documents/documents@hudd/research/projects/fluid corpus navigation/research/ftis/ftis/ftis/analyser/meta.py", line 123, in analyse
    stats = get_buffer(fluid.stats(mfccs, numderivs=self.numderivs), "numpy")
AttributeError: 'ClusteredSegmentation' object has no attribute 'numderivs'

but I solved it, line 91

Okay, thanks. That is also pushed to: 7fe83d124a1ca9b3748002e8c8258105c1398e3f
As you can see these classes are not great for extending 👎 and their interface sucks quite a lot but thanks for sticking with it


Authorization rules

In this pull request, I, @lengushuru, and @TaiwoEnoch implemented all functionalities for authorization rules by following these steps:

[ ] Install CanCanCan in your project.
[ ] Add a role column to the user's table. Remember to use migration for this.
[ ] A user can delete a post if it is theirs or if they have an admin role (column role has value "admin"). Use CanCanCan for this authorization.

[ ] For that you need to implement the post-deleting functionality. Add the "Delete" button to the view and make sure that only authorized users can see it.

[ ] A user can delete a comment if it is theirs or if they have an admin role (column role has value "admin"). Use CanCanCan for this authorization.

[ ] For that you need to implement the comment-deleting functionality. Add the "Delete" button to the view and make sure that only authorized users can see it.

@brainconnect93, thank you for approving our project.


remove the use of $PARAM

I find the use of $PARAM variable and respective files to just make thing
unneccessary complicated.
Service scripts also runs fine without it, making it redundant.
the content of $PARAM can also just be housed locally in the service scripts,
similarly to other service managers.

fixed in #4


Update gems

Coverage remained the same at 86.158% when pulling f9401c35dc9d6353c6207f1d2fc9ca53008f45f1 on update-gems into 5c61d9489b66ebba404feeb3033f8986931f5a57 on master.


test(live): wait longer on job kill

It sometimes may take over 30 seconds for a job to be killed in CI and there's nothing reasonable we can do about it for now.
Adding this as a temporary measure.

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

Comparison is base (67c71fa) 78.46% compared to head (47ba718) 40.69%.

Additional details and impacted files
@@             Coverage Diff             @@
##             main      #45       +/-   ##
===========================================
- Coverage   78.46%   40.69%   -37.78%
===========================================
  Files          16       16
  Lines        2234     2209       -25
===========================================
- Hits         1753      899      -854
- Misses        481     1310      +829

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

Good idea to test this with a backoff, rather than just using a single timeout.


how work this?


Can compile but cannot run in MultiMC

I can compile and run code in RetroMCP
but I can't run this in MultiMC
It throws these errors:
Exception in thread "Minecraft main thread" java.lang.NoSuchMethodError: java.nio.IntBuffer.clear()Ljava/nio/IntBuffer

and
Exception in thread "Minecraft main thread" java.lang.NoSuchMethodError: java.nio.ByteBuffer.clear()Ljava/nio/ByteBuffer

These errors appears in "RenderEngine.java" file
Version that I have modified: b1.7.3
I'm using Azul Zulu's JDK 1.8.0_392

You are compiling using Java 9+. In Java 9, Buffer#clear methods return the subclasses type I.E. IntBuffer#clear instead of Buffer. Make sure you are compiling using Java 8 instead of Java 9+ and try again.

Closing issue as inactive.


[Foundation] Rework NSFastEnumerationIterator to be more performant

Previously the implementation of NSFastEnumerationIterator would cause many allocations and was overly complex; leading to poor performance in certain cases like DirectoryEnumerator etc. This version instead acts more similarly to how the objc for-in syntax works.
Resolves:
rdar://problem/30905263
and partially addresses some of the concerns backing:
rdar://problem/30195113

@swift-ci test

@jckarter This includes the changes you were concerned about previously with the iterator.

This will work if you're certain that the only inner pointer to the struct will be the exact itemsPtr. I still think it would be more robust, and better for the platform as a whole, to investigate whether stack promotion is already taking effect on the class-based iterator and make it work if it isn't already.

From what I could tell stack promotion was not occurring. Pulling this out and building in whole module optimization it was invoking malloc multiple times; I presumed since it is a reference type that was perfectly valid behavior. (which from a performance standpoint is definitely not)

@eeckstein Is there something obvious blocking stack promotion of NSFastEnumerator classes in "for" loops?

Is this an objc class? We only do stack promotion for native swift classes.

the previous code was final public class NSFastEnumerationIterator : IteratorProtocol so it certainly should not have been @objc or inherited from NSObject etc.

Can you file a radar with an example for-loop where stack promotion does not occur (although it should)?

I am not fully certain where the exact set of failures stem from but there are definitely more problems than just stack promotion here.
rdar://problem/31685067
I could revert this back to a final class since the overall change is much more performant even without the stack based iterator. In practice collections do not carry huge amounts of elements but when they do this is a pretty gnarly bottleneck in that the previous code calls malloc way too many times.


No such file or directory on MacOS.

➜  luke-swing-7.6.0 ./luke.sh
Unable to find the LUKE_PATH environnement variable.
Set LUKE_PATH to /Users/jonnyzzz/Work/luke-swing-7.6.0
./luke.sh: line 22: /Users/jonnyzzz/.luke.d/luke_out.log: No such file or directory

Thanks for the report. This occurs when Luke is freshly installed. (When upgrading, the log directory should already exist.)
I fixed this (#159) and created the release <IP_ADDRESS>. https://github.com/DmitryKey/luke/releases/tag/luke-swing-<IP_ADDRESS>


Projects: Configure a Slice by field

Summary
Users will be able to select a Slice by field that pulls all field values into a panel on the left side, with the project items associated with those values in the view on the right side. Clicking through the values in the panel will filter and adjust the items that appear in the view, allowing users to quickly page through their items and make adjustments.

Intended Outcome
By providing users with the ability to create this view on their projects, we can help them accomplish tasks such as

Visually separating and breaking down epics from the individual tasks by the Tracked by field, giving a hierarchical view of your items powered by tasklists to understand how larger work items are progressing in a single view
Planning out current and upcoming iterations by the Iteration field, allowing users to quickly make adjustments to when work will begin if plans change
Understanding team capacity with by the Assignee field, breaking down work items by each distinct assignee and giving an easy canvas to move items between team members to reassign work

How will it work?
Users will be able to specify a Slice by field on any of their table, board, or roadmap layouts. The panel allows a user to select a value from the list that populates and filters the work items that appear in the view on the right.

🚢 This has shipped: https://github.blog/changelog/2023-08-10-github-issues-projects-august-10th-update/#slice-by
Leaving open to track for GHES release!

This shipped with GHES 3.11<EMAIL_ADDRESS>


Configuration fails with Joomla 2.5.28 and Virtumart 2.0.2 and Icepay version 1.0.1

The configuration tab is empty, showing only this notice:
Undefined property: JSimpleXMLElement::$params in /public/sites/www.makayama.net/libraries/joomla/html/parameter.php on line 398

Hi vincentmakayama,
This payment module is compatible only with VirtueMart 3.0.9. Please try installing ICEPAY Payment Module for VirtueMart 2. You can download the latest version here.

I hope your problem is solved. Please let me know if you have any other questions.


Added contactflowhelper function

Description of changes: Adding new contactflowhelper function and updating main readme file.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Made changes.


Python Environment missing: {86767848-40B4-4007-8BCC-A3835EDF0E69}\3.5

I've set up my Visual Studio 2017 with the Python tools to develop for Windows 10 IoT Core.
Creating a project works, but in the Solution Explorer under Python environments, a reference is missing:
UnknownInterpreter{86767848-40B4-4007-8BCC-A3835EDF0E69}\3.5
This ID isn't referenced by any file in my Hello World app. Seems like it is included by: https://github.com/Microsoft/PTVS/blob/master/Python/Product/Uwp/Microsoft.PythonTools.Uwp.targets
The ID appears to be related to PythonUwpIoT according to: https://github.com/Microsoft/PTVS/blob/master/Python/Product/PythonTools/PythonTools/Project/PythonProjectFactory.cs
The project can still compile, but it's strange to have an error in a Hello World app built using the Visual Studio Python template. (based on: https://developer.microsoft.com/en-us/windows/iot/samples/helloworldpython )
My environment:

Visual Studio 2017 15.2 (26430.16)
Installed through VS Installer: Python + UWP workloads + manually selected: Python IoT support.
Also installed: https://github.com/ms-iot/python/releases (latest version 1.4)

So theoretically, that should be it. The Visual Studio about dialog also lists Python as installed (including UWP support) - everything with version 3.0.17114.1
So I'm wondering what is my environment missing that causes this missing reference, and why is this missing component not part of the complete installation that I did?

It's actually a lingering reference from our previous version. You're right that it is an error and we should clean it up, but you are not actually missing anything.
If you remove the InterpreterReference line from that targets file then it will go away and you shouldn't have any other problems. The reference in PythonProjectFactory is an upgrade step for converting the value into the new style one, and if you start from an up-to-date template (which you have) then it isn't ever used.
(cc @alanch-ms)


test: upgrade ut of package config to make it more self-contained and…

… exact

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?

Additional documentation e.g., design docs, usage docs, etc.:

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
11 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.06%) to 73.96%

Files with Coverage Reduction
New Missed Lines
%

pkg/config/util.go
2
64.44%

pkg/config/operator.go
2
80.78%

pkg/cmd/destroy/options.go
7
81.86%

Totals

Change from base Build<PHONE_NUMBER>:
-0.06%

Covered Lines:
7487

Relevant Lines:
10123

💛  - Coveralls


Recommend a domain to host the playground

It would be nice to have the playground not be on https://ahnafyy.github.io/mama-lang/ but on a domain.
I would prefer to keep the budget under 100$ if possible
SO NOT THIS

Please recommend what you think the domain should be

This would be great. Per my research, the maximum language is hosted under the .org domain name, but this one is so cheap and doesn't make much difference.

I just bought it.

Will configure with https://gist.github.com/plembo/84f80c920bb5ac6f19e53fe6f8db1ff7 when I have some more time!
Thanks @Aryan3212 @zhshakib


Disable the ES6 module test file temporarily pending test hook changes

Simple change to disable the ES6 module test temporarily. This is breaking internal builds due to missing test hook. We'll turn this test back on after Yong checks-in his module test hook.

Hi @boingoing, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Taylor Woll). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;


fix: #2964 Update message for segmentation error loading due to orien…

Fixes https://github.com/OHIF/Viewers/issues/2964
Fix summary:
Update the error message for segmentation load failure due to orientation tolerance value.
Direct user to change the tolerance value under Segmentation settings.

Thanks, @igoroctaviano !

We already display the inconsistency warning in the thumbnail. The warning message in the thumbnail is the original message from dcmjs. Please refer the picture.

The modified message aims at redirecting the user to segmentation panel settings in order to support viewing of segmentations that are detected as non-planar due to the 32 bit float rounding error (for example, for segmentations converted from nii  to dcm, original issue here https://github.com/OHIF/Viewers/issues/2869#issuecomment-1228331103) .
Since dcmjs is an external library, I think we are good keeping this modified message containing information about the UI of the upper level App within OHIF.


BUG: Adjust TemplateFieldsFileInner cycle date in PrepVariational

https://github.com/NCAR/MPAS-Workflow/blob/35be181d85eea73038180a12ebf715d3bee35fb9/PrepVariational.csh#L369
In order to fix the dual-mesh DA application (i.e. O30kmIE60km), the following change needs to be made starting from the line referenced above.
-    set FirstCyclingFCDir = ${CyclingFCWorkDir}/${prevFirstCycleDate}${memDir}/Inner
-    cp -v ${FirstCyclingFCDir}/${self_StatePrefix}.${FirstFileDate}.nc $tFile
+    set FirstCyclingFCDir = ${CyclingFCWorkDir}/${FirstCycleDate}${memDir}/Inner
+    cp -v ${FirstCyclingFCDir}/${self_StatePrefix}.${nextFirstFileDate}.nc $tFile

After that change, there may no longer be a need for variables related to prevFirstCycleDate.  If true, then prevFirstCycleDate and all associated commands can be removed from config/modeldata.csh.

There are is another problem in GetWarmStartIC.csh.  The inner loop mpasout file is sourced from the outer loop archive directory instead of the inner loop archive directory.
I think this change should fix it:
-        set InitialMemberFC = "$firstFCDirOuter"`${memberDir} ens $member "${firstFCMemFmt}"`
+        set InitialMemberFC = "$firstFCDirInner"`${memberDir} ens $member "${firstFCMemFmt}"`


Add coverage to util.py for IPv6 and write_index

Just a couple small test cases.

[Current coverage][cc-pull] is 38.29%

Merging [#1534][cc-pull] into [master][cc-base-branch] will increase coverage by 0.62%

@@             master      #1534   diff @@
==========================================
  Files            51         51
  Lines          5771       5771
  Methods           0          0
  Messages          0          0
  Branches       1116       1116
==========================================
+ Hits           2174       2210    +36
+ Misses         3400       3361    -39
- Partials        197        200     +3

Powered by Codecov. Last updated by [1be88cd...695043f][cc-compare]
[cc-base-branch]: https://codecov.io/gh/graphite-project/graphite-web/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/graphite-project/graphite-web/compare/1be88cdf88b1ccdfaddcc0b74a4a23b2a08a1054...695043ff82e80fdc3b0186dea268dd0eff79d642
[cc-pull]: https://codecov.io/gh/graphite-project/graphite-web/pull/1534?src=pr

I love that you're putting some effort into testing!  I'm not really competent with python, but having useful tests makes me more confident to make changes.

Tests are always appreciated, thanks!


Can't access record fields, only id

So, when i want to search for a recor for ex
const record = $app.dao().findFirstRecordByData("users", "id", "iw173nymwtka2s9")  console.log(record); console.log(JSON.stringify(record)); console.log(typeof record);
This is the output:
2023/12/04 14:55:22 [object Object] 2023/12/04 14:55:22 {"avatar":"","collectionId":"_pb_users_auth_","collectionName":"users","created":"2023-12-04 17:37:11.424Z","emailVisibility":false,"id":"iw173nymwtka2s9","name":"USER","updated":"2023-12-04 17:37:11.424Z","username":"teste","verified":true} 2023/12/04 14:55:22 object
But i can't access anything other than the record.id, if i try to access record.avatar, or record.name etc, it just goes blank, does anyone have a solution for me?

The returned record is not a POJO.
For accessing the record data you'll have to use the designated getter and setters, eg. record.get("yourField"). List with commonly used methods and helpers you can find in https://pocketbase.io/docs/js-records/#getset-record-fields.


INFRA: Initialize Provisioning project

The commit history of this PR is not pure.
We have to commit each component individually.
Start over. one commit - one action. Just like in the video.


fix: [IDP-2205]: Added the limitation info for bitbucket cloud connector

Harness Developer Pull Request
Added the limitation info for bitbucket cloud connector
What Type of PR is This?

[ ] Issue
[ ] Feature
[x] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[x] Tested Locally
[ ] Optional Screenshot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65caf5d1122991535f04dd7f--harness-developer.netlify.app


Adding test that verifies for 4369 to be fixed

flyby: clean up CMakeFile.txt for this test

Fixes #4369

This was still missing some changes (see comments above). I'll create a new PR for those.


Removed dependency for php-http/promise

There is no technical dependency on php-http/promise. Since we only use it in docs I think we should remove it.
Packages that need the php-http/promise should require it directly. See https://github.com/php-http/guzzle6-adapter/pull/26

There is: the async client requires it.

No, it does not as I can see it.
The async client interface use it in the PHP doc to say that the method should return a Promise. "Technically", it is no requirement.

See the reasoning here: php-http/guzzle6-adapter#26
I think it is still part of the contract, no matter if it is in the same package or not.
In the future if we release new versions of the promise library (for example a major version with BC breaks) we have to make sure that it continues working with the relevant httplug version. With other words: httplug needs to specify the supported versions, since it is part of the contract.

Hm, yeah, it makes sense. You are correct.
If this was PHP7 and we were using return types it would be obvious that we should have php-http/promise in composer.json.
Thank you.
I stil think https://github.com/php-http/guzzle6-adapter/pull/26 is valid though.

I stil think php-http/guzzle6-adapter#26 is valid though.

I will have to think about it. I can imagine cases where you might need bigger control over the exact promise version.


Inside view + uploads for volumes

Heya Portainer Community,
i couldn't find duplicates on that topic. If it is a duplicate, then just close it.
Is your feature request related to a problem? Please describe.
Currently, the Volume screen does not display any information on what is stored in it.

Describe the solution you'd like
Having an (navigatable) inside view over the contents of a volume with the possibility to create/move/delete files and folders. A possibility to upload and download files over a web-gui might come handy as well.
Describe alternatives you've considered
At the moment i use a container that displays a webgui, like dropbox, but it becomes very tedious to change/mount the individual volumes since i cycle through them quite fast.

Please have a look at the documentation: https://documentation.portainer.io/v2.0/volumes/browse/

Please have a look at the documentation: https://documentation.portainer.io/v2.0/volumes/browse/

Thank you for the info, thats what i was looking for. Sadly, that option is not presented if used with simple docker and not docker swarm.

@Renegat27 you need to use the Portainer agent to gain access to this feature.
The agent can be deployed on a Docker standalone environment, see the instructions here: https://documentation.portainer.io/v2.0/deploy/ceinstalldocker/
Once deployed, you can connect Portainer to the agent by adding it as a new endpoint:
Endpoints -> Add endpoint -> Agent and use MACHINE_IP:9001 as an endpoint URL (replace MACHINE_IP with the IP address of your machine).


Running Voyager Ingress metacontroller fails, because of the need to reconcile internal resources of Voyager

When running other resources managed by another operator (Voyager) via metacontroller, he tries to reconcile state of internal resources of Voyager (service, etc.).

Sorry, I don't understand. Can you give a code snippet or log entries to show what you're trying to do, and what the resulting behavior is?

So, I has
childResources:
    - apiVersion: v1
      resource: pods
    - apiVersion: v1
      resource: persistentvolumeclaims
    - apiVersion: voyager.for.example
      resource: ingress
    - apiVersion: v1
      resource: services
      updateStrategy:
        method: InPlace

When I try to utilise ingress, it create additional resources (Voyager Operator creates it) and looks like metacontroller tries to reconcile them. But I expect Voyager resource have to be black box and not expose underling resources to metacontroller

It sounds like the Voyager Operator is not adding ControllerRef to the objects it creates. That's an important rule that controllers need to follow in order to maintain the "black box" isolation you mentioned.
If it's not possible for you to fix the Voyager Operator (e.g. you didn't write it), one way you might be able to work around this is to make sure that the label selector for the parent object in your controller does not match the objects created by the Voyager Operator.


✨[Feature] An idea about a new feature in Torch-TensorRT Version for Windows

[ ] Version for Windows

### Tasks
- [ ] Version for windows with installation via pip

Upvoting this request.
Building the library on Windows isn't straightforward, very error prone, and according to the installation guide, with the recommended method using CMake, the Python API isn't created.

Upvoting this request. Building the library on Windows isn't straightforward, very error prone, and according to the installation guide, with the recommended method using CMake, the Python API isn't created.

I wanted to ask you, is there a way to create the python api somehow or download a pytorch version with trt support somehow or is is not possible?

We are working on Python on windows but it will likely be Dynamo only. Getting good UX for the build system (both for linux and windows) has been the blocker. https://github.com/pytorch/TensorRT/tree/windows_dynamo_testing


[Perf] Optimize creation of VDD

Fixes #3906
ViewDataDictionary of TModel type is now created using the cached delegate as opposed to Activator.CreateInstance for improved performance.
Tagged as Design because build fails with unrelated errors.

Hi @mnltejaswini, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

:watch: Direction looks good. Would like to see the cache on RazorPageActivator used instead, and a little cleanup avoiding the use of object[] that needs to be allocated per-request

Perf comparisons
Testapp: https://github.com/aspnet/Performance/tree/dev/testapp/LargeStaticView
loadtest -k -n 10000 -c 250 http://localhost:5000/TagHelpers
Before fix
RazorPageActivator.Activate takes ~448ms of CPU time and the hot spot is

After fix
RazorPageActivator takes ~178ms of CPU time and the hot spot is no longer Activator.CreateInstance

:watch:

:shipit: - looks good!


Missing proper exception mapdesign without player

If a user tries to parse a map without putting a player on that map, an IndexOutOfBoundsException will be thrown. This exception doesn't tell the user anything about his possible error. It would be better to throw a PacManConfigurationException, because this will tell the user what is going wrong, and gives an indication as to how this problem can be fixed.

Linking to the fix in #33.

An invariant exists here. Can we close this issue or do we want to turn it into a isEmpty() check which throws the PacManConfigurationException?


append feature

Hello, I added an append feature that I used in one of my projects for automatically generating separate files for flipped sprites. I thought this might be a nice addition to the main branch as well.
The feature works by adding an ' append:  ' to the converts and then convimg just adds the string to the name of the corresponding generated files. I already added a test and docs for the feature.
Let me know what you think!

Thanks! Do you think you could rename it from append to suffix? And maybe add a prefix?

yeah sure, i’m on to it!

I changed it to suffix and prefix and also made sure the strings are both initialized as NULL.

Thank you! Merged


Published Server API reference

Would be really great to have a published Server API reference.
The reference can be generated from the openapi specs and published to Github similar to https://resonatehq.github.io/resonate-sdk-ts/
The specs currently live in https://github.com/resonatehq/resonate/tree/main/api

Closed by #433


Clicking on referenced list ids does nothing

From @manuelnaranjo on Gitter:

guys anyone has a fix for the referenced_list id issue?
it happens even on the demo site http://ng-admin.marmelab.com/#/posts/edit/1 when you go to the bottom list of comments and click on one, it doesn't switch the page, it used to be working before

Fixed, as you can see on demo: http://ng-admin.marmelab.com/#/posts/show/1


CAMEL-10178: Added Google PubSub Component

Google PubSub component with producer and consumer endpoints, unit and integration tests. Speed optimisation (mini batching, async processing) will be done in subsequent releases - dependent on the new client library from Google. For now it is synchronous, message by message processing.

Can you please run mvn -Psourcecheck and fix all the codestyle errors?
Thanks.

Sure. Is there a Intellij Scheme that would make it easy?

@evmin no, there isn't at the moment.
https://github.com/apache/camel/tree/master/buildingtools

No issues. Is there some sort of a guideline.
I am getting cryptic errors like these:
`
[ERROR] /projects/camel/camel/components/camel-google-pubsub/src/main/java/org/apache/camel/component/google/pubsub/consumer/ExchangeAckTransaction.java:8: Line does not match expected header line of ' *'. [Header]
[ERROR] /projects/camel/camel/components/camel-google-pubsub/src/main/java/org/apache/camel/component/google/pubsub/consumer/ExchangeAckTransaction.java:24: Wrong order for 'java.util.ArrayList' import. [ImportOrder]
`
Just to get me started.

Usually, it's like an exploration. Point after point. Otherwise you can open your project in eclipse, import the checkstyle from camel repo and update the indentation.

Not sure if there is any scheme somewhere for Idea. We can ping @davsclaus for this :-)

@oscerd : No issues, I'll get cracking. I got what was the problem - I just copied the disclaimer from one of the Camel files and it came with the <p>

@oscerd Could you please check if the warning is correct?
[ERROR] /projects/camel/camel/components/camel-google-pubsub/src/main/java/org/apache/camel/component/google/pubsub/GooglePubsubConstants.java:19:1: Utility classes should not have a public or default constructor. [HideUtilityClassConstructor]
I am declaring an enum - is this warning correct?

Yes, it is.
You'll need to define your utility class as final and then add a private constructor
   private blablabla() {
      //not called
   }

http://stackoverflow.com/questions/14398747/hide-utility-class-constructor-utility-classes-should-not-have-a-public-or-def

Hi @evmin,

[ERROR] /projects/camel/camel/components/camel-google-pubsub/src/main/java/org/apache/camel/component/google/pubsub/consumer/ExchangeAckTransaction.java:8: Line does not match expected header line of ' *'. [Header]

This should mean you should not use <p> in the header comment. Compare the entire comment with other classes.

[ERROR] /projects/camel/camel/components/camel-google-pubsub/src/main/java/org/apache/camel/component/google/pubsub/consumer/ExchangeAckTransaction.java:24: Wrong order for 'java.util.ArrayList' import. [ImportOrder]

This means java.* should come first.

[ERROR] /projects/camel/camel/components/camel-google-pubsub/src/main/java/org/apache/camel/component/google/pubsub/GooglePubsubConstants.java:19:1: Utility classes should not have a public or default constructor. [HideUtilityClassConstructor]

I think it's just you should declare the private default constructor like this:
private GooglePubsubConstants() {
}

Thank you very much, @oscerd and @tadayosi !
Appreciate the guidance and your help - love the exercise.

@oscerd Done. Could you please advise on what else needs to be fixed?

@evmin looks good to me. The only thing you can is a test in tests/camel-itest-karaf to test the karaf feature like the other components do.
@davsclaus what do you think of this PR? Do you have any other thought?

One other thing why using SEVERE in logging.properties?

logging.properties is being used by the PubSub Emulator. With any other option it becomes a bit too verbose and produces a lot of output that is being registered by mvn as ERROR (even when it is INFO).  I have raised this with Google, but not sure when (or if) it is going to be addressed.
Should I add a comment?
P.S. IN regards of Karaf - I will check out. How important is it, given that we have tested the component with unit and integratin tests?

@evmin no problem then for SEVERE. I didn't notice it was in test. Sorry, my mistake.
Karaf integration is important. A lot of users are based on Karaf and on OSGi, so it is important that Karaf feature installs correctly.

@oscerd Ok I will have a look. Though I do not have any experience with PaxExam. Is there a guide how to start an environment or run a test?

@evmin You can take a look here. For example the camel-facebook itests-karaf test
https://github.com/apache/camel/blob/master/tests/camel-itest-karaf/src/test/java/org/apache/camel/itest/karaf/CamelFacebookTest.java
You just need to create your own test for the component. Then you need to follow these steps:

enter in platform/karaf/features and run

mvn clean install

enter in tests/camel-itest-karaf and run

mvn clean test -Dtest=<your test class name>

This will spin up a karaf instance (4.0.7 on master) and installs your feature.

Additionally you can also download a Karaf distribution (4.0.7 for example) and run a karaf instance with

/bin/karaf

In the shell you'll just need to run the following commands
> features:repo-add camel 2.19.0-SNAPSHOT
.
.
.
> features:install -v camel-google-pubsub

and verify the feature installs correctly

@oscerd Thank you very much. I think I got it.
Would you be so kind to check as to what might be the issue with features.xml?
There were no problem this morning. I have checked out the master features, updated it again and pushed - the conflict seems to still be there. What do I miss?

Then simply push the branch again

git push -f origin CAMEL-10178

Let me know. You just need to rebase.

You pushed one more commit to resolve the conflict.
Do a

git reset --hard HEAD~1

and go back to the PR with this as last commit
CAMEL-10178: Karaf Test
Than rebase and push with -f

@oscerd Not sure I am getting it. If I checkout the apache master features - all looks good, no conflicts. But if I update it with the pubsub feature - it is in conflict.

Let me have a look.

@oscerd I can prep a new pull request - from scratch - if required.

This seems to be ok.
https://github.com/oscerd/camel/tree/CAMEL-10178
I added one commit and removed the conflicts and it seems to be able to merge without conflicts.

Thank you!

Maybe it would be good to create a new PR.
I try to run the test and I get the following error
Running org.apache.camel.component.google.pubsub.unit.PubsubComponentTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.456 sec - in org.apache.camel.component.google.pubsub.unit.PubsubComponentTest
Running org.apache.camel.component.google.pubsub.unit.PubsubEndpointTest
Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 1.638 sec <<< FAILURE! - in org.apache.camel.component.google.pubsub.unit.PubsubEndpointTest
testEndpointConfiguration(org.apache.camel.component.google.pubsub.unit.PubsubEndpointTest)  Time elapsed: 1.614 sec  <<< ERROR!
org.apache.camel.FailedToCreateRouteException: Failed to create route route1: Route(route1)[[From[google-pubsub://test-project:test-sub-na... because of The Application Default Credentials are not available. They are available if running on Google App Engine, Google Compute Engine, or Google Cloud Shell. Otherwise, the environment variable GOOGLE_APPLICATION_CREDENTIALS must be defined pointing to a file defining the credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information.
Caused by: java.io.IOException: The Application Default Credentials are not available. They are available if running on Google App Engine, Google Compute Engine, or Google Cloud Shell. Otherwise, the environment variable GOOGLE_APPLICATION_CREDENTIALS must be defined pointing to a file defining the credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information.
testEndpointConfiguration(org.apache.camel.component.google.pubsub.unit.PubsubEndpointTest)  Time elapsed: 0.011 sec  <<< ERROR!
org.apache.camel.FailedToCreateRouteException: Failed to create route route2: Route(route2)[[From[google-pubsub://test-project:test-sub-na... because of The Application Default Credentials are not available. They are available if running on Google App Engine, Google Compute Engine, or Google Cloud Shell. Otherwise, the environment variable GOOGLE_APPLICATION_CREDENTIALS must be defined pointing to a file defining the credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information.
Caused by: java.io.IOException: The Application Default Credentials are not available. They are available if running on Google App Engine, Google Compute Engine, or Google Cloud Shell. Otherwise, the environment variable GOOGLE_APPLICATION_CREDENTIALS must be defined pointing to a file defining the credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information.
testEndpointConfiguration(org.apache.camel.component.google.pubsub.unit.PubsubEndpointTest)  Time elapsed: 0.01 sec  <<< ERROR!
org.apache.camel.FailedToCreateRouteException: Failed to create route route3: Route(route3)[[From[google-pubsub://test-project:test-sub-na... because of The Application Default Credentials are not available. They are available if running on Google App Engine, Google Compute Engine, or Google Cloud Shell. Otherwise, the environment variable GOOGLE_APPLICATION_CREDENTIALS must be defined pointing to a file defining the credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information.
Caused by: java.io.IOException: The Application Default Credentials are not available. They are available if running on Google App Engine, Google Compute Engine, or Google Cloud Shell. Otherwise, the environment variable GOOGLE_APPLICATION_CREDENTIALS must be defined pointing to a file defining the credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information.
Running org.apache.camel.component.google.pubsub.unit.PubsubProducerTest
Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 0.031 sec <<< FAILURE! - in org.apache.camel.component.google.pubsub.unit.PubsubProducerTest
testProducerConfiguration(org.apache.camel.component.google.pubsub.unit.PubsubProducerTest)  Time elapsed: 0.011 sec  <<< ERROR!
org.apache.camel.FailedToCreateRouteException: Failed to create route route4: Route(route4)[[From[direct://from]] -> [To[google-pubsub://t... because of Failed to create Producer for endpoint: google-pubsub://test-project:test-topic-name. Reason: java.io.IOException: The Application Default Credentials are not available. They are available if running on Google App Engine, Google Compute Engine, or Google Cloud Shell. Otherwise, the environment variable GOOGLE_APPLICATION_CREDENTIALS must be defined pointing to a file defining the credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information.
Caused by: org.apache.camel.FailedToCreateProducerException: Failed to create Producer for endpoint: google-pubsub://test-project:test-topic-name. Reason: java.io.IOException: The Application Default Credentials are not available. They are available if running on Google App Engine, Google Compute Engine, or Google Cloud Shell. Otherwise, the environment variable GOOGLE_APPLICATION_CREDENTIALS must be defined pointing to a file defining the credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information.
Caused by: java.io.IOException: The Application Default Credentials are not available. They are available if running on Google App Engine, Google Compute Engine, or Google Cloud Shell. Otherwise, the environment variable GOOGLE_APPLICATION_CREDENTIALS must be defined pointing to a file defining the credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information.
testProducerConfiguration(org.apache.camel.component.google.pubsub.unit.PubsubProducerTest)  Time elapsed: 0.009 sec  <<< ERROR!
org.apache.camel.FailedToCreateRouteException: Failed to create route route5: Route(route5)[[From[direct://from]] -> [To[google-pubsub://t... because of Failed to create Producer for endpoint: google-pubsub://test-project:test-topic-name. Reason: java.io.IOException: The Application Default Credentials are not available. They are available if running on Google App Engine, Google Compute Engine, or Google Cloud Shell. Otherwise, the environment variable GOOGLE_APPLICATION_CREDENTIALS must be defined pointing to a file defining the credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information.
Caused by: org.apache.camel.FailedToCreateProducerException: Failed to create Producer for endpoint: google-pubsub://test-project:test-topic-name. Reason: java.io.IOException: The Application Default Credentials are not available. They are available if running on Google App Engine, Google Compute Engine, or Google Cloud Shell. Otherwise, the environment variable GOOGLE_APPLICATION_CREDENTIALS must be defined pointing to a file defining the credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information.
Caused by: java.io.IOException: The Application Default Credentials are not available. They are available if running on Google App Engine, Google Compute Engine, or Google Cloud Shell. Otherwise, the environment variable GOOGLE_APPLICATION_CREDENTIALS must be defined pointing to a file defining the credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information.
testProducerConfiguration(org.apache.camel.component.google.pubsub.unit.PubsubProducerTest)  Time elapsed: 0.009 sec  <<< ERROR!
org.apache.camel.FailedToCreateRouteException: Failed to create route route6: Route(route6)[[From[direct://from]] -> [To[google-pubsub://t... because of Failed to create Producer for endpoint: google-pubsub://test-project:test-topic-name. Reason: java.io.IOException: The Application Default Credentials are not available. They are available if running on Google App Engine, Google Compute Engine, or Google Cloud Shell. Otherwise, the environment variable GOOGLE_APPLICATION_CREDENTIALS must be defined pointing to a file defining the credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information.
Caused by: org.apache.camel.FailedToCreateProducerException: Failed to create Producer for endpoint: google-pubsub://test-project:test-topic-name. Reason: java.io.IOException: The Application Default Credentials are not available. They are available if running on Google App Engine, Google Compute Engine, or Google Cloud Shell. Otherwise, the environment variable GOOGLE_APPLICATION_CREDENTIALS must be defined pointing to a file defining the credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information.
Caused by: java.io.IOException: The Application Default Credentials are not available. They are available if running on Google App Engine, Google Compute Engine, or Google Cloud Shell. Otherwise, the environment variable GOOGLE_APPLICATION_CREDENTIALS must be defined pointing to a file defining the credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information.
Results :
Tests in error:
org.apache.camel.component.google.pubsub.unit.PubsubEndpointTest.testEndpointConfiguration(org.apache.camel.component.google.pubsub.unit.PubsubEndpointTest)
Run 1: PubsubEndpointTest>CamelTestSupport.setUp:261->CamelTestSupport.doSetUp:360->CamelTestSupport.startCamelContext:676 » FailedToCreateRoute
Run 2: PubsubEndpointTest>CamelTestSupport.setUp:261->CamelTestSupport.doSetUp:360->CamelTestSupport.startCamelContext:676 » FailedToCreateRoute
Run 3: PubsubEndpointTest>CamelTestSupport.setUp:261->CamelTestSupport.doSetUp:360->CamelTestSupport.startCamelContext:676 » FailedToCreateRoute
org.apache.camel.component.google.pubsub.unit.PubsubProducerTest.testProducerConfiguration(org.apache.camel.component.google.pubsub.unit.PubsubProducerTest)
Run 1: PubsubProducerTest>CamelTestSupport.setUp:261->CamelTestSupport.doSetUp:360->CamelTestSupport.startCamelContext:676 » FailedToCreateRoute
Run 2: PubsubProducerTest>CamelTestSupport.setUp:261->CamelTestSupport.doSetUp:360->CamelTestSupport.startCamelContext:676 » FailedToCreateRoute
Run 3: PubsubProducerTest>CamelTestSupport.setUp:261->CamelTestSupport.doSetUp:360->CamelTestSupport.startCamelContext:676 » FailedToCreateRoute
Tests run: 3, Failures: 0, Errors: 2, Skipped: 0
Maybe also these tests must be skipped.

Will do a new PR.
As for failed tests - I will have a look. Could be the local setup leaking in where it should not.

Many thanks @evmin :-)
By the way this is a great work. Glad you'd like donating it to Apache Camel project.

Absolutely. BTW it is indeed a leak within the local environment. Will get it fixed.

Ok, we'll waiting your new PR. Thanks.


[Event Request] Codeunit 86 Sales-Quote to Order - OnAfterInsertSalesOrderHeader

Can we get an Event OnAfterCreateSalesHeader after the creation of the new SalesOrderHeader:
    local procedure CreateSalesHeader(SalesHeader: Record "Sales Header"; PrepmtPercent: Decimal)
    begin
        OnBeforeCreateSalesHeader(SalesHeader);

        with SalesHeader do begin
            SalesOrderHeader := SalesHeader;

            ......

            OnBeforeModifySalesOrderHeader(SalesOrderHeader, SalesHeader);
            SalesOrderHeader.Modify();
        end;
        OnAfterCreateSalesHeader(SalesOrderHeader, SalesHeader); //NEW
    end;

Can we get an similiar event for codeunit 96 "Purch.-Quote to Order"
OnAfterCreatePurchHeader(PurchOrderHeader, PurchHeader);

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Support for inspecting multiple RaptorJIT processes

This adds an intermediary step/class that will scan the product path, if there is more than one RJITProcess it will instantiate a listing of processes.
Additionally, 99677de adds a percentage to the samples column in "Profiler datatsets".

This is a very good feature!
I have folded this into the work over on the new UI in #124. I rewrote quite a bit of the relevant code so I took the idea from your screenshot rather than the exact changes. I have tried to make data loading a bit more "DWIM" with a recursive search for auditlog and vmprofile files.
Screenshot:

This should be covered in the new version of Studio living on master now :)


Improvement and Pipeline for K8s Deployment

Currently we already succeed to use container(etc: docker) and orchestration tool(etc: kubernetes) to deploy OSRM(Including binary, data, live traffic solution).
But we still need to improve the deployment:

release pipeline for dev/stage env;
mapdata should be injected during container startup;

Let's use this issue to track and discuss these improvements.

This release pipeline is heavily depends on telenav's internal running environment and how we collaborate with each other. I think it's not that meaningful for community. Also, the "inject mapdata during container startup" seems not that important since we run "engine+mapdata" together docker image very well.

You should most likely be using osrm-datastore, that way you can easily swap the data without any sort of rolling update. K8s supports IPC as well so it should work in theory. I have it working in an AWS ECS setup on my own EC2 server. This also allows you to setup a DaemonSet for the worker/osrm-datastore so you can have multiple nodes but only have one datastore running on them and then you can spin up as many routing containers as you need on those nodes for scaling purposes.

@nhaskins01  You're right! If you look at https://github.com/Telenav/osrm-backend/blob/c9e9cc98e395fb1fc164741da63abcfc7d2172ae/docker-orchestration/osrm-backend/docker-entrypoint.sh#L65, osrm-datastore already in place. We have launched it in our AWS EKS Clusters and it works well. This approach is much better than the rolling update: easier to deploy, easier to maintain.
But I have a question on This also allows you to setup a DaemonSet for the worker/osrm-datastore so you can have multiple nodes but only have one datastore running on them and then you can spin up as many routing containers as you need on those nodes for scaling purposes., do you mean run multiple containers together to share 1 data set via shared memory?

Ah got it, I was looking at the k8s rolling update file.
yeah exactly. So you would have a DaemonSet run the worker container which should be customizing the data and loading it into the datastore, which would be available to all pods on that node via IPC resources/shared memory.
So imagine 2 nodes dedicated to OSRM and each running the DaemonSet. Now you can spin up as many osrm-routed instances as you want and they will connect to the shared memory segment, you also are removing a single point of failure by having 2 nodes and removing a single point of failure on the pods by having more than 1 on each node.
However, im not sure about the overhead of the containers and if you are better off running one osrm-routed container per node and giving it all of the nodes resources. If this is the case, then I would just probably run 3 nodes with it.
One improvement I think you can make is doing the data transformation in a single place instead of in each application. So you could have a worker on a cron or just constantly running that does the osrm-customize and uploads to s3, the osrm-routed/datastore application now just has to download the data from s3 and load it into the datastore(be sure to use a lock file so you dont have the customize process uploading files while the routed/datastore process is downloading them). Doing the customize on the application container can cause a large spike in RAM usage and other resources which can lead to performance issues according to the osrm-backend team.
Overall this is a really solid looking project though, mine looks very similar to how you have yours setup, im working on migrating it to k8s now and updating the setup a bit to take advantage of a few things I didnt think of in the beginning.

The DaemonSet you said only can solve the single point failure issue that if osrm-routed crashes. However, from my testing it's quite stable. So it may be overhead than benifit, and you have to spend time on it.
A simple way to prevent single point failure issue is to run two replicas(PODs) per deployment in Kubernetes, both process and node failure can be covered.
I run this approach on 16 vcpus instance , and customize cpu has been limited by 12 to balance the customize and route performance. The data transformation makes sense to improve it, but s3 may be too slow. EFS might work, but there're more stuff that need to care about it: all the customziing, uploading, downloading and datastore take time. It's valuable to have a try if need that a many instances setup.


Configure CI clusters maintenance window

We are occasionally seeing flakes, especially on GCP, that seem to be caused by infrastructure (.e.g. network connectivity) issues. We are wondering whether those are not caused by cluster updates that coincide with periodic tests executions. Maybe we could configure maintenance windows for our clusters and stop running periodics during that time.
GCP maintenance windows documentation
We are not seeing such issues on AWS that often, however maybe it is worth to see whether we can configure such maintenance intervals for AWS clusters as well.

We have enabled the maintenance window of the pr-e2e cluster to be every Saturday, all day long

Done, and looks like it made a difference!


Fixes up some of the newer UI features

Makes it prettier, more generic, and more useful.
Changes
How I tested this
Notes
Checklist

[ ] PR has an informative and human-readable title (this will be pulled into the release notes)
[ ] Changes are limited to a single goal (no scope creep)
[ ] Code passed the pre-commit check & code is left cleaner/nicer than when first encountered.
[ ] Any change in functionality is tested
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged / future TODOs are captured in comments
[ ] Project documentation has been updated if adding/changing functionality.


[SPARK-10437][SQ] Support aggregation expressions in Order By

JIRA: https://issues.apache.org/jira/browse/SPARK-10437
If an expression in SortOrder is a resolved one, such as count(1), the corresponding rule in Analyzer to make it work in order by will not be applied.

Merged build triggered.

Merged build started.

Test build #41996 has started for   PR 8599 at commit 452cfb5.

Test build #41996 has finished for   PR 8599 at commit 452cfb5.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41996/
Test PASSed.

Merged build finished. Test PASSed.

Merged build triggered.

Merged build started.

Test build #42003 has started for   PR 8599 at commit e65f4db.

Test build #42003 has finished for   PR 8599 at commit e65f4db.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42003/
Test PASSed.

LGTM except a minor comment for test.
cc @marmbrus

Merged build triggered.

Merged build started.

Test build #42036 has started for   PR 8599 at commit 8f73c40.

Test build #42036 has finished for   PR 8599 at commit 8f73c40.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42036/
Test FAILed.

Merged build finished. Test FAILed.

retest this please.

Merged build triggered.

Merged build started.

Test build #42038 has started for   PR 8599 at commit 8f73c40.

Test build #42038 has finished for   PR 8599 at commit 8f73c40.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42038/
Test FAILed.

Merged build triggered.

Merged build started.

Test build #42040 has started for   PR 8599 at commit 6023c8b.

Test build #42040 has finished for   PR 8599 at commit 6023c8b.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42040/
Test FAILed.

retest this please.

Merged build triggered.

Merged build started.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42046/
Test FAILed.

retest this please.

Merged build triggered.

Merged build started.

Test build #42057 has started for   PR 8599 at commit 6023c8b.

Test build #42057 has finished for   PR 8599 at commit 6023c8b.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class BlockFetchException(messages: String, throwable: Throwable)

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42057/
Test PASSed.

ping @liancheng

ping @liancheng @marmbrus

Merged build triggered.

Merged build started.

Test build #42186 has started for   PR 8599 at commit 046a8cb.

Test build #42186 has finished for   PR 8599 at commit 046a8cb.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
 case class Instance(w: Double, a: Vector, b: Double)
class WeibullGenerator(

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42186/
Test PASSed.

[SQ] in the PR description should be [SQL].

@liancheng Updated. Thanks.

@liancheng Any more comment?

Thanks, merged to master.


Theme: File Manager hot-keys don't work while filtering

When you filter files/folders, then using arrow keys for navigating up and down, the hot keys don't work, like hitting delete will not do anything.

Will be fixed in 18.04

18.04 is out, please upgrade! :wink:


Unmet dependancy(?) for jinja2 when using miniconda

From<EMAIL_ADDRESS>on 2015-01-16T07:42:01Z
Please note that reporting bugs from Spyder's help menu ("?" > "Report
issue...") will fill version details for Spyder, Python and Qt in this description for you.
What steps will reproduce the problem?
1.Install miniconda, then install spyder through "conda install spyder"
2.Run spyder from start-menu 3.
What is the expected output? What do you see instead?
Expected: Working spyder session. Got: Crash on start (pythonw.exe has stopped working) What version of the product are you using? On what operating system? Spyder 2.3.2, conda 3.7.4, python 2.7.8.final.0, win 7 professional 64-bit, SP1.
Please provide any additional information below
. In issue #2081 comment #5 Dan reports to having similar problem due to a unmet dependancy for jinja2. After installing jinja2 through conda, the crashing at startup stops also for my installation. To me this looks like an unmet dependancy that ought to be included in the dependancy list. Currently the following packages are there (copypasta from conda info spyder).
dependencies:
docutils
ipython
pygments 2.0.1
pyqt 4.10.4
python 3.4*
pyzmq 14.*
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=2120

From ccordoba12 on 2015-02-08T10:55:26Z
Thanks for your interest in improving Spyder.
Please report this issue with the Anaconda guys. We can't do anything about it.
Status: Invalid


Fix: DO-2781 Fix multiple index df deserialization

Motivation and Context
The previous deserialise method will turn tuple to ["'mean'", "'median'"] instead of  ["mean", "median"]
Implementation Description
For each string, will split by , first, then check it the result start and end with ' or ", if so, remove it.
Any new dependencies Introduced

No
How Has This Been Tested?
Integration tested
PR Checklist:

[x] I have implemented all requirements? (see JIRA, project documentation).
[x] I am not affecting someone else's work, If I am, they are included as a reviewer.
[x] I have added relevant tests (unit, integration or regression).
[x] I have added comments to all the bits that are hard to follow.
[x] I have added/updated Documentation.
[x] I have updated the appropriate changelog with a line for my changes.

Screenshots (if appropriate):

Looks good, can we add a test case to ensure the tuple serialization->deserialization is correct?

I have a test to cover serialization->deserialization already, but it didn't have a assert before, hence, the error is not been find out. But the assert is added and it pass the test :)


Merge awslabs upstream

It's good to be inline with original repo ;)

Hi @marinomeneghel,
last time when I tried to merge with the upstream repo, I had to fix lots of things. In the past git-secrets was modified by the Scout24 to adapt it to our needs.
However, the Security team (I'm the maintainer) works on a bigger project called codestripper. git-secrets is currently one plugin inside codestripper. But I think in the future we'll replace git-secrets due to several reasons:

high false-positive rate
a huge bash script is not really manageable

Hey @dorneanu , thanks for the explanation. I did the merge in the process of troubleshooting why we were receiving email from<EMAIL_ADDRESS>saying "ALERT: Possible credential leak detected in one/more of the git commit(s) that was pushed to Github.com recently." even tho we adding them with git config --add secrets.allowed (that doesn't seem to add to .gitallowed).
As far is you know, is there any simple solution we can put in place while waiting for codestripper to be released? :)
Given the context you provided, please feel free to close the PR 👍

That's interesting coz we don't send mails to the commit authors (yet). Can you send that mail to me (Victor Dorneanu)? I guess it's from GitHub directly.
On your local machine you can still use git-secrets or gitleaks. I even think that gitleaks might be a good replacement for git-secrets. OR we implement the same functionality in codestripper directly. I don't know yet.
BR,
Victor


Improve Docker Image extraction speed for linux ec2 instances

Description
Added Pigz to allow for parallel image extraction within al2023 instances.
Issues Resolved
Closes #374
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Thanks @chawinphat , the extraction is mainly using unpigz, but when installing pigz, normally both pigz and unpigz will be installed.
Can you make sure to install both here? And confirm this?
Thanks.

@peterzhuamazon What are the steps to confirm this since the Docker Image for ec2 instances?


Intercooler events not firing when building with Webpack

Hi,
I have been using this plugin for a while without issues, however since I've tried to upgrade to the latest version it never worked again.
I'm using Webpack to build the project, and since the package does not play well with a Webpack build, I had to set an alias so it points to the file library location intercooler: "intercooler/src/intercooler.js"
Problem is, event though the project builds and I get Intercooler in the global Scope (https://cl.ly/3s010V1L3B1y), the events are not firing. Things like beforeSend.ic or pushUrl.ic work, event though nothing change on the codebase where I'm creating those listeners.
Weirdly enough, the URL does update (i have push configured) the actual contents it should replace does not change either.
Any idea on where this might be going wrong?

It sounds like Intercooler isn't initalizing properly when it loads.
Do you see anything in the console?  Is the "Intercooler" global symbol available?
Cheers,
Carson

-------- Original Message --------
Subject: [LeadDyno/intercooler-js] Intercooler events not firing when building with Webpack (#221)
Local Time: October 5, 2017 11:16 AM
UTC Time: October 5, 2017 6:16 PM
From<EMAIL_ADDRESS>To: LeadDyno/intercooler-js<EMAIL_ADDRESS>Subscribed<EMAIL_ADDRESS>Hi,
I have been using this plugin for a while without issues, however since I've tried to upgrade to the latest version it never worked again.
I'm using Webpack to build the project, and since the package does not play well with a Webpack build, I had to set an alias so it points to the file library location intercooler: "intercooler/src/intercooler.js"
Problem is, event though the project builds and I get Intercooler in the global Scope (https://cl.ly/3s010V1L3B1y), the events are not firing. Things like beforeSend.ic or pushUrl.ic work, event though nothing change on the codebase where I'm creating those listeners.
Weirdly enough, the URL does update (i have push configured) the actual contents it should replace does not change either.
Any idea on where this might be going wrong?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi @carsongross,
Thanks so much for the feedback.
I see one of two things happening.
Using the version 1.0.3, and loading it via Webpack with the Expose Loader require("expose-loader?Intercooler!intercooler"); when I inspect the Intercooler object on the console I get an empty object. Interestingly enough, it shows the same output on the currently live site but there it works just fine.
If I use the latest version, loading it into the app using the same method, I still get an empty object.
On both situations above, when I click links the URL changes (using the push to history feature) but the content stays unchanged and the events I'm listening don't fire.
Btw, these are the event listeners I have declared:
       jQuery(".js-loopNavigation a").on("beforeSend.ic", function(
            evt,
            elt,
            data
        ) {
            console.log("BEFORE SEND IC");
            self.onBeforeLoadPosts(evt, elt, data);
        });

        jQuery("body").on("complete.ic", function(
            evt,
            elt,
            data,
            status,
            xhr,
            requestId
        ) {
            console.log("COMPLETE IC");
            self.onPostsLoaded(evt, elt, data, status, xhr, requestId);
        });

        jQuery("body").on("pushUrl.ic", function(evt, target, data) {
            console.log("IC PUSH URL");
            self.triggerGAEvents();
        });

This is a WordPress site, where I'm loading the default jQuery version (2.2.0), so I've also tried loading the script directly from the CDN and strangely I get the same result.
Any idea why the push URL would work but not the events?

@carsongross maybe I can get around it in a different way.
I'm loading the script from the CDN, instead of including it on the Webpack build. For some reason the events don't fire still, but I do get the contents from the response.
The issue with this approach, and this might be a different issue altogether, is that the library breaks other libraries functionality. This site uses a library called FacetWP, which is also ajax based.
Once I load Intercooler from the CDN, any ajax call from FacetWP is halted by an error on Intercooler script:

Which refers to this part of the script:

Finally, inspecting the Intercooler object on the console does retrieve a non-empty object this time:

Thanks so much for any help you may provide.

I'm fine with that fix, can you create a pull request against development?


doc: add history section to the Jitter RNG source

This should have been included originally.  I've included the same commit as part of #25498 which modifies the history section and thus will avoid a conflict later.

[x] documentation is added or updated
[ ] tests are added or updated

This pull request is ready to merge

@t8m  - Do we have a dedicated Info Dev or technical publishing team to review documentation?

Merged to the 3.4 branch. Thank you for your contribution.


Undo changes from PR #4420

Undo changes from PR #4420
See: https://github.com/ReactTraining/react-router/pull/4420
.babelrcs intended location was modules dir., so lets move it back.
In tests.webpack.js, replace const with var, so code works in browsers that do not support the const keyword.
Error caused due to use of const keyword is as below.
See: https://travis-ci.org/ReactTraining/react-router/builds/197028565
IE 10.0.0 (Windows 8 0.0.0) ERROR
  Syntax error
  at /home/travis/build/ReactTraining/react-router/packages/react-router-dom/tests.webpack.js:47 <- webpack:///tests.webpack.js:1:0

Thanks!

🎉  Thanks, @mayani 💃


[Event Request] Report 5753 Get Source Documents - OnBeforePostReport

Hi, would it be possible to add the parameter WhseReceiptLine in OnBeforePostReport, like this :
trigger OnPostReport()
begin
    OnBeforePostReport("Warehouse Request", RequestType, OneHeaderCreated, WhseShptHeader, WhseHeaderCreated, ErrorOccured, LineCreated, ActivitiesCreated, Location, WhseShptLine, WhseReceiptHeader, HideDialog, WhseReceiptLine);
    if not HideDialog then
        case RequestType of
            RequestType::Receive:
                ShowReceiptDialog();
            RequestType::Ship:
                ShowShipmentDialog();
        end;
    if SkippedSourceDoc > 0 then
        Message(CustomerIsBlockedMsg, SkippedSourceDoc);
    Completed := true;

    OnAfterPostReport("Warehouse Request", RequestType, OneHeaderCreated, WhseShptHeader, WhseHeaderCreated, ErrorOccured, LineCreated, ActivitiesCreated, Location, WhseShptLine);
end;

[IntegrationEvent(false, false)]
local procedure OnBeforePostReport(WhseRequest: Record "Warehouse Request"; RequestType: Option; OneHeaderCreated: Boolean; var WhseShptHeader: Record "Warehouse Shipment Header"; var WhseHeaderCreated: Boolean; var ErrorOccured: Boolean; var LineCreated: Boolean; var ActivitiesCreated: Integer; Location: record Location; var WhseShptLine: record "Warehouse Shipment Line"; var WhseReceiptHeader: Record "Warehouse Receipt Header"; var HideDialog: Boolean; var WhseReceiptLine : record "Warehouse Receipt Line")
begin
end;

?
Thanks for your work

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 11255.


Parse input expressions for dbg! invocations in remove_dbg

Instead of inspecting the input tokentree manually, parse the input as , delimited expressions instead and act on that. This simplifies the assist quite a bit.
Fixes #8455

bors r+

bors retry


Trigger bullets on signal?

Hey @Moonzel!
How would I go about adding a shoot on click function?
right now my gun rotates around the player and has a Marker2D at the muzzle position

i then created a node2d which simply sets its position to mouse on physics process and use this as the PlayerTracker to aim towards my mouse. Now to my issue: I am currently recreating the PatternManager and the Spawner each time I click my attack button, I then move the spawner to the WeaponAttackPivot global_position and add first the spawner then the PatternManager to the scene. the bullet appears and then I queue free the PatternManager.

however this way the node id cant fire in quick succession and i run into several race conditions. Is there an easier way to start the pattern, shoot it once (number of shots is at 1) and wait until the player clicks again? Been sitting at it for several hours now and I don't think where I am going is the right way...

I do not believe that this is the best way to do this, as Spawners being created in this way could potentially lead to some issues with Godot's Physics system. I am in the process of adding a way to start a pattern by emitting a signal, and will comment here again when I have finished. Thanks for letting me know about this problem!

@vexxvakan The Update 1.2 is now live! I hope you enjoy the new MANUAL mode. This should be just what you needed!

@vexxvakan The Update 1.2 is now live! I hope you enjoy the new MANUAL mode. This should be just what you needed!

@Moonzel Amazing news, let me try the update today and I'll add some feedback later!!


Errors when running dune build

When running dune build in the project directory, it returns the following errors:
*** Warning: in file iris.v, library language is required from root iris.program_logic and has not been found in the loadpath!
*** Warning: in file iris_use.v, library language is required from root iris.program_logic and has not been found in the loadpath!
*** Warning: in file iris_use.v, library tactics is required from root iris.proofmode and has not been found in the loadpath!
*** Warning: in file iris_use.v, library weakestpre is required from root iris.program_logic and has not been found in the loadpath!
*** Warning: in file iris_use.v, library gen_heap is required from root iris.base_logic and has not been found in the loadpath!
*** Warning: in file iris_use.v, library proph_map is required from root iris.base_logic and has not been found in the loadpath!
*** Warning: in file interpreter_func_sound.v, library StrongInduction is required from root StrongInduction and has not been found in the loadpath!
*** Warning: in file interpreter_func_sound.v, library Inductions is required from root StrongInduction and has not been found in the loadpath!
*** Warning: in file interpreter_sound.v, library StrongInduction is required from root StrongInduction and has not been found in the loadpath!
*** Warning: in file interpreter_sound.v, library Inductions is required from root StrongInduction and has not been found in the loadpath!
*** Warning: in file properties.v, library StrongInduction is required from root StrongInduction and has not been found in the loadpath!
*** Warning: in file type_progress.v, library Omega is required from root Coq and has not been found in the loadpath!
*** Warning: in file type_checker_reflects_typing.v, library StrongInduction is required from root StrongInduction and has not been found in the loadpath!
*** Warning: in file type_checker_reflects_typing.v, library Inductions is required from root StrongInduction and has not been found in the loadpath!
*** Warning: in file type_preservation.v, library Omega is required from root Coq and has not been found in the loadpath!
File "./theories/bytes_pp.v", line 3, characters 0-20:
Error: Required library Byte matches several files in path (found
/home/june/.opam/default/lib/coq/theories/Strings/Byte.vo and
/home/june/.opam/default/lib/coq/theories/Init/Byte.vo).

File "./theories/floats.v", line 2, characters 0-20:
Error: Required library Byte matches several files in path (found
/home/june/.opam/default/lib/coq/theories/Strings/Byte.vo and
/home/june/.opam/default/lib/coq/theories/Init/Byte.vo).

File "./theories/list_extra.v", line 134, characters 4-61:
Error: Unknown interpretation for notation "_ <- _ ;; _".

File "./theories/numerics.v", line 1159, characters 23-24:
Error: The reference Z was not found in the current environment.

I understand that this may not be a supported build method.

Indeed as you stated, the project currently uses esy packaging for managing the dependencies, so it would be unlikely for a direct dune build outside of esy to compile the codebase successfully.
We based ourselves on esy as some of our dependencies are sensitive on the version numbers, plus that some dependencies are quite tricky to compile.


Allow overriding subcommand of superclass in subclass

An example is, say, a FileCommand class, with a new subcommand. Then there's a TextFileCommand that extends FileCommand. It would be nice for TextFileCommand to be able to provide its own new subcommand, as opposed to having to create a subcommand with a new name, like newtxt.

Oh thanks I'll try that. Still would be more convenient to be able to do it with annotations though.

Is it possible that the fix for #619 also fixed this issue or is this unrelated?


Updated free-programming-interactive-tutorials-en.md

learn python step by step easily
What does this PR do?
Add resource(s) | Remove resource(s) | Add info | Improve repo
For resources
Programming Tutorials ,Python Tutorials, DSA, OS
Description
Programiz is an online educational platform that provides a wide range of programming tutorials, resources, and tools to help individuals learn, practice, and master programming and related topics.
Why is this valuable (or not)?
It is free of cos and very easy to use
How do we know it's really free?
It doesn't demand any money
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[x ] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

Be sure to check the free-programming-books-lint output for linter errors. Alphabetical order and spacing are the most common problems.

LGTM!Ready to Merge

duplicate -  listed in the courses list


Allow using images

Hello, thanks for developing this plugin. I was wondering if it would be possible to add items with images (not only icons). I was imagining something like this example in the Material Design's  website:

Thanks for the idea. The problem it's that I don't think flutter's FAB does have a constructor for passing images as background. I'll look into it.


Fix test failure by making clean shutdown handler optional

Issue Number
#1314
Overview

Fixes integration test failure which occurs locally - https://github.com/input-output-hk/cardano-wallet/issues/1314#issuecomment-594061933

bors try

Seems like bors wants its commands as normal comments.
bors r+


Add RHEL/CentOS systemd service handling

For now if Nexus is stopped on RHEL/CentOS, puppet agent sync can't start it. These changes fix it.

Closing this since it was done in: https://github.com/hubspotdevops/puppet-nexus/pull/76


Provide a way to figure out if Raven has been installed.

The Raven browser lib has a member Raven.isSetup() which is useful to figure out if Raven was installed or not. Having a similar feature in raven-node would be interesting.
Right now, when one of the APIs is used without first configuring Raven, the following exception is thrown (from REPL)
> var Raven=require('raven');
undefined
> Raven.captureMessage('test')
TypeError: Cannot read property 'user' of undefined

Yea, that error has actually come up in issues/support tickets more than once - people running into that error and not realizing that it's just because they never did Raven.install().
If you need a workaround for now, Raven.installed is a(n undocumented) boolean property that will tell you if you've done Raven.install() (and it also flips back to false if you Raven.uninstall() but that's mostly for our testing).
This is definitely something I want to improve, though; Raven-js mostly does it how we want to: if you try to send an event before installing, it refuses and warns you. We could do that (or maybe be even more strict) and provide an isSetup() or isInstalled() method.
I'll address this in v2.1.0 which should go out sometime next week.

@LewisJEllis  Raven.installed is always returning undefined for me.

I misspoke in my earlier comment, Raven.installed is undefined until you do Raven.install() and then it should be true. Either way you should be able to do if (Raven.installed) {.

Is the Raven.installed something that could be promoted as 'official', i.e. that would still be available in future versions (at least until a major version update) ?

Sure, it's safe to say .installed won't go away on 2.x, but I won't add anything to the docs (outside of these comments) until we have an isSetup() or isInstalled() method.

Raven.installed should be sufficient for use-cases like this. Please feel free to reopen an issue if you think this should be improved.

This seems to be Raven._isRavenInstalled for us.


Factor the formatter out of the GraphiteClient.

This makes it easier to send multiple metrics through a single graphite connection. And it separates concerns between connection management and metric naming.

Coverage decreased (-0.9%) to 92.542% when pulling 828cc879c4ef0c88705496fb070f91f1f9d7486a on zillow:factor_formatter into bd6e73e3b49793231c248182cfd439b4cd4ceb31 on daniellawrence:master.

Coverage increased (+0.2%) to 93.706% when pulling 8e0dac6043eb407e468f97414340a2e3e8b73c71 on zillow:factor_formatter into bd6e73e3b49793231c248182cfd439b4cd4ceb31 on daniellawrence:master.

g'day @jonathanultis,
This looks pretty interesting, the most important thing when it comes to changes with the lib is making sure that the metric names will remain the same with any refactoring.
The fact that no changes have been the tests and they are all still passing with increased coverage makes me think that you have do this :+1:.
I need to have a better read over the changes, however I do not have any objections to the approach.
cheers,
Danny

LGTM :+1:
@Shir0kamii - Any thoughts on this PR?

Hi, sorry for doing this review this late.
This work is pretty cool! Maybe refactoring the code of the formatter would be a good thing instead of simply copying it from the internal of the client. I have some ideas that could make the code more simple. But It may be better in another PR. I think I will try it out.
Anyway we can merge it in this state. I will do it on command line instead of asking a rebase to make amend for doing my work this late. :stuck_out_tongue:
@jonathanultis Thanks for the contribution!


Can't Parse Encoding With Non Ascii Characters

Hello Spark-xml team,
We have been using spark-xml a lot, thanks for the package!
Recently trying spark-xml with ISO_8859-1 encoded XML that contains Nordic characters, e.g
name="Företagsinteckningar"
Could not get the Nordic characters to parse correctly, despite setting the charset to ISO_8859-1.
Traced the issue to this method in com.databricks.spark.xml.util.XmlFile:
def withCharset(
context: SparkContext,
location: String,
charset: String,
rowTag: String): RDD[String] = {
// This just checks the charset's validity early, to keep behavior
Charset.forName(charset)
context.hadoopConfiguration.set(XmlInputFormat.START_TAG_KEY, s"<$rowTag>")
context.hadoopConfiguration.set(XmlInputFormat.END_TAG_KEY, s"</$rowTag>")
context.hadoopConfiguration.set(XmlInputFormat.ENCODING_KEY, charset)
context.newAPIHadoopFile(location,
classOf[XmlInputFormat],
classOf[LongWritable],
classOf[Text]).map { case (_, text) => new String(text.getBytes, 0, text.getLength, charset) }
}
Problem with (_, text) => new String(text.getBytes, 0, text.getLength, charset) seems to be that the text already contains UTF8 encoded bytes, populated by Xml Parser, it is not charset encoded.
After changing above code to (_, text) => text.toString(), the Nordic characters parsed correctly.
This seems to be a common problem for parsing xml with non ascii characters, would be great to get the fix into the package.
Thanks

What characters are you talking about? I don't think those are in ISO-8859-1

It seems those characters got truncated on posting, trying again
name="Allmänna företagsuppgifter"

You'll need to use UTF-8 - this and much of Hadoop/Spark assume that pretty deeply for text files.
The charset param is actually pretty misleading here - it just affects things like how the row tag and line separators are interpreted as bytes.

In this case though the Xml input reader has already converted the Xml to UTF-8 text, while the code above (_, text) => new String(text.getBytes, 0, text.getLength, charset) is written as though the text could contain charset bytes, that seems inconsistent with the assumption above? So what issues do you see with the fix?

I'm not sure it has. It read something as UTF-8, gave you the bytes, and you tried to interpret it as a different charset. That won't necessarily work. Are you sure the text is coming through as you intend there?

Not sure which code you are referring to now?
This is the code in Spark Xml source today:
classOf[Text]).map { case (_, text) => new String(text.getBytes, 0, text.getLength, charset)
Like you say the text is UTF-8, but this code "tried to interpret it as a different charset. That won't necessarily work"
My fix is:
"After changing above code to (_, text) => text.toString(), the Nordic characters parsed correctly."
Please see initial description of the case.

Ah right, I had forgotten this is what XmlFile does. Hm, I'm actually not sure where this new String(..., charset) construction originated, as that should not work unless charset is UTF-8 (except in special cases like ASCII). Similar Spark code just calls .toString too which seems more natural.
I guess I'm still surprised if it works, if the Hadoop TextInputFormat is reading your data as UTF-8, but maybe it is otherwise converted by those APIs or something. OK I will make that change - seems better in any event and if it fixes this case, good.

The XmlFile is using XmlInputFormat here, XmlInputFormat seems to be converting the data from charset to UTF-8.

Ah right, I've forgotten so much about how this works. Of course, right. Then that is definitely the right fix, I'll commit it after tests pass.

Thank you!