Error in YAML pipeline:  Deployment strategy: 'Rolling' is not supported for Environment scoped target.

The site shows this example for a rolling deployment:
jobs:

deployment: VMDeploy
displayName: web
environment:
name: smarthotel-dev
resourceType: VirtualMachine
strategy:
rolling:
maxParallel: 5  #for percentages, mention as x%

However, when I run it, this error appears:  Deployment strategy: "'Rolling' is not supported for Environment scoped target."
It is worth noting that when I try the pipeline without environment it give this error:
"
Job ####: Environment is required."
Suggestions?
Thanks,
Bill

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

ID: 5aeeaace-1c5b-a51b-e41f-f25b806155b8
Version Independent ID: fd7ff690-b2e4-41c7-a342-e528b911c6e1
Content: Deployment jobs - Azure Pipelines
Content Source: docs/pipelines/process/deployment-jobs.md
Product: devops
Technology: devops-cicd-process
GitHub Login: @juliakm
Microsoft Alias: jukullam

@bholman77 -- Bill, thank you for your feedback and question.  Please consider these resources:

Azure DevOps Services
Azure DevOps on Stack Overflow

@juliakm -- Julia, please look into this issue.

I've tried and can't reproduce this issue. Here's my working pipeline for reference.
trigger:
- main

pool:
  vmImage: ubuntu-latest

jobs:
  - deployment: VMDeploy
    displayName: web
    environment:
      name: myVM
      resourceType: VirtualMachine
      tags: web1
    strategy:
      rolling:
        maxParallel: 5  #for percentages, mention as x%
        preDeploy:
          steps:
          - script: echo initialize, cleanup, backup, install certs
        deploy:
          steps:
            - script: echo my first deployment
        on:
          failure:
            steps:
            - script: echo Restore from backup! This is a failure
          success:
            steps:
            - script: echo Notify! This is a success

Thank you Julia,
Although I have long-since left the project and the company that owned it, your response it appreciated.
Bill Holmanj
From: Julia Kulla-Mader @.>
Sent: Wednesday, March 1, 2023 10:45 AM
To: MicrosoftDocs/azure-devops-docs @.>
Cc: Bill Holman @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-devops-docs] Error in YAML pipeline: Deployment strategy: 'Rolling' is not supported for Environment scoped target. (Issue #12485)
I've tried and can't reproduce this issue. Here's my working pipeline for reference.
trigger:

main

pool:
vmImage: ubuntu-latest
jobs:

deployment: VMDeploy
displayName: web
environment:
name: myVM
resourceType: VirtualMachine
tags: web1
strategy:
rolling:
maxParallel: 5  #for percentages, mention as x%
preDeploy:
steps:
- script: echo initialize, cleanup, backup, install certs
deploy:
steps:
- script: echo my first deployment
on:
failure:
steps:
- script: echo Restore from backup! This is a failure
success:
steps:
- script: echo Notify! This is a success

—
Reply to this email directly, view it on GitHub https://github.com/MicrosoftDocs/azure-devops-docs/issues/12485#issuecomment-1450465593 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ADJC4ZA74SP44MRKXTRQBGTWZ54IPANCNFSM53QB3PAA .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/ADJC4ZHC2XID4KDPVQQRLQTWZ54IPA5CNFSM53QB3PAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOKZ2FSOI.gif Message ID: @.*** @.***> >


Installing error

This is in a custom build of blender? Does it occur in master?

Yes.But it works in master very well now
Cody Winchester<EMAIL_ADDRESS>于2020年6月7日周日 下午12:12写道：

This is in a custom build of blender? Does it occur in master?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/BlenderNPR/Abnormal/issues/10#issuecomment-640154101,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADQODLJQ47RGWZPDK5YOL2LRVMHR3ANCNFSM4NWWRM6Q
.


config: add etcd authentication

expose username and password configuration options for flannel, fleet, and locksmith to etcd
Addresses https://github.com/coreos/flannel/issues/419 and https://github.com/coreos/fleet/issues/1505

@jipperinbham could you please rebase this PR?

@crawford this PR should be reconciled with @jonboulle and https://github.com/coreos/fleet/issues/1506

Yeah, we have to wait on flannel as well.

@jipperinbham can you squash your commits and rebase onto master? It looks like we can finally merge this.

Ping.

@crawford sorry about that, squashed and rebased

Thanks again.


XSS vulnerability in video-embed plugin

Describe the bug
The following attributes are not sanitized by the video-embed plugin: data-vimeo, data-vimeoparams, data-youtube and data-ytparams which may lead to XSS vulnerability.
Affected source code
The following lines contain the vulnerability:

https://github.com/aFarkas/lazysizes/blob/a2f37ec2371bff523ea8b94800682e4ec3596b9b/plugins/video-embed/ls.video-embed.js#L73
https://github.com/aFarkas/lazysizes/blob/a2f37ec2371bff523ea8b94800682e4ec3596b9b/plugins/video-embed/ls.video-embed.js#L98

To Reproduce
Open the following file and click on the play button:

">
        <button class="play-btn">play</button>

What is the expected behavior
No XSS vulnerability.
What happened instead
alert(1) popup was shown, so the code embedded into the data-ytparams attribute ran.
Similar issues
This was a somewhat similar issue in jQuery UI which was handled as a security vulnerability and also got a CVE: https://github.com/jquery/api.jqueryui.com/issues/281
In what environment (browser/device etc.) does this bug happen/not happen:
Affects all environments, but tested in Chrome 80.0.3987.132 (Official Build) (64-bit) on Windows 10

https://github.com/aFarkas/lazysizes/assets/101028580/6bd0ed3b-683f-46e7-a1a8-e49deec87b57

https://github.com/aFarkas/lazysizes/assets/101028580/4bf505d1-5b19-4286-83b4-51b481dad21a

xss333.svg.webm


git cl presumbit crashes.

@sortie
When trying to upload the CL https://dart-review.googlesource.com/c/sdk/+/3460 the presubmit crashes with the error below.
This is on Windows using the depot tools git (and probably python).
It's possibly caused by the files containing raw non-ASCII characters.
I used --bypass-hooks to overcome the problem (since it's a clean revert, it "should be safe").
λ git cl presubmit
Running presubmit commit checks ...
Traceback (most recent call last):
  File "c:\src\depot_tools\\git_cl.py", line 6112, in <module>
    sys.exit(main(sys.argv[1:]))
  File "c:\src\depot_tools\\git_cl.py", line 6094, in main
    return dispatcher.execute(OptionParser(), argv)
  File "c:\src\depot_tools\subcommand.py", line 252, in execute
    return command(parser, args[1:])
  File "c:\src\depot_tools\\git_cl.py", line 4746, in CMDpresubmit
    change=cl.GetChange(base_branch, None))
  File "c:\src\depot_tools\\git_cl.py", line 1573, in RunHook
    gerrit_obj=self._codereview_impl.GetGerritObjForPresubmit())
  File "c:\src\depot_tools\presubmit_support.py", line 1368, in DoPresubmitChecks
    results += executer.ExecPresubmitScript(presubmit_script, filename)
  File "c:\src\depot_tools\presubmit_support.py", line 1262, in ExecPresubmitScript
    gerrit_obj=self.gerrit, dry_run=self.dry_run)
  File "c:\src\depot_tools\presubmit_support.py", line 451, in __init__
    self.cpu_count, _capture_interrupt)
  File "c:\src\depot_tools\win_tools-2_7_6_bin\python\bin\lib\multiprocessing\__init__.py", line 232, in Pool
    return Pool(processes, initializer, initargs, maxtasksperchild)
  File "c:\src\depot_tools\win_tools-2_7_6_bin\python\bin\lib\multiprocessing\pool.py", line 159, in __init__
    self._repopulate_pool()
  File "c:\src\depot_tools\win_tools-2_7_6_bin\python\bin\lib\multiprocessing\pool.py", line 222, in _repopulate_pool
    w.start()
  File "c:\src\depot_tools\win_tools-2_7_6_bin\python\bin\lib\multiprocessing\process.py", line 130, in start
    self._popen = Popen(self)
  File "c:\src\depot_tools\win_tools-2_7_6_bin\python\bin\lib\multiprocessing\forking.py", line 277, in __init__
    dump(process_obj, to_child, HIGHEST_PROTOCOL)
  File "c:\src\depot_tools\win_tools-2_7_6_bin\python\bin\lib\multiprocessing\forking.py", line 199, in dump
    ForkingPickler(file, protocol).dump(obj)
  File "c:\src\depot_tools\win_tools-2_7_6_bin\python\bin\lib\pickle.py", line 224, in dump
    self.save(obj)
  File "c:\src\depot_tools\win_tools-2_7_6_bin\python\bin\lib\pickle.py", line 331, in save
    self.save_reduce(obj=obj, *rv)
  File "c:\src\depot_tools\win_tools-2_7_6_bin\python\bin\lib\pickle.py", line 419, in save_reduce
    save(state)
  File "c:\src\depot_tools\win_tools-2_7_6_bin\python\bin\lib\pickle.py", line 286, in save
    f(self, obj) # Call unbound method with explicit self
  File "c:\src\depot_tools\win_tools-2_7_6_bin\python\bin\lib\pickle.py", line 649, in save_dict
    self._batch_setitems(obj.iteritems())
  File "c:\src\depot_tools\win_tools-2_7_6_bin\python\bin\lib\pickle.py", line 681, in _batch_setitems
    save(v)
  File "c:\src\depot_tools\win_tools-2_7_6_bin\python\bin\lib\pickle.py", line 286, in save
    f(self, obj) # Call unbound method with explicit self
  File "c:\src\depot_tools\win_tools-2_7_6_bin\python\bin\lib\pickle.py", line 562, in save_tuple
    save(element)
  File "c:\src\depot_tools\win_tools-2_7_6_bin\python\bin\lib\pickle.py", line 286, in save
    f(self, obj) # Call unbound method with explicit self
  File "c:\src\depot_tools\win_tools-2_7_6_bin\python\bin\lib\pickle.py", line 748, in save_global
    (obj, module, name))
pickle.PicklingError: Can't pickle <function _capture_interrupt at 0x031078B0>: it's not found as presubmit_support._capture_interrupt

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "c:\src\depot_tools\win_tools-2_7_6_bin\python\bin\lib\multiprocessing\forking.py", line 381, in main
    self = load(from_parent)
  File "c:\src\depot_tools\win_tools-2_7_6_bin\python\bin\lib\pickle.py", line 1378, in load
    return Unpickler(file).load()
  File "c:\src\depot_tools\win_tools-2_7_6_bin\python\bin\lib\pickle.py", line 858, in load
    dispatch[key](self)
  File "c:\src\depot_tools\win_tools-2_7_6_bin\python\bin\lib\pickle.py", line 880, in load_eof
    raise EOFError
EOFError

TBR

Update: It's not just that CL, I have the same problem with https://dart-review.googlesource.com/c/sdk/+/3620 - which has no fancy non-ASCII characters. So far two out of two CL's fail to run presubmit on Windows.

I believe those issues have been fixed.


Add missing base strategies

For sake of completeness, all possible spectypes should have a supporting strategyclass so we can build strategies for each spec.
Currently only the strategies actually needed and most useful (or most likely) are provided ... we should take an hour to implement all of them.

fixed with 689979bd75fe82b6897118af97b09a0d8be96aa4


Postal Codes

Hi all,
Love the effort so far. I am interested in creating a project that displays this data visually on a map to neighbourhood detail. This won’t be possible without postal codes.
How challenging would it be to get postal codes? I realised just the first three alphanumerics are good enough to show a neighbourhood close up (also mitigating any privacy concerns).
Ratnesh

Hi there-- all of our data is curated from publicly available sources. At the moment the highest level of spatial resolution that is available publicly is at the health region-level, which is what we are reporting. We are not collecting information at the postal code level.

@ratneshchandna
Hi Ratnesh,
I just want to mention that while postal codes aren't available for case data, on https://virihealth.com/full-details/ you can find neighborhood detail for mortality (in the details it mentions the hospital where the person passed away from)
I am not affiliated in any way with the website, but I thought it might help in whatever you are doing.
Thanks,
Devansh


Consider a move to making SukiWindow as the new default.

I've been experimenting locally with making a SukiWindow control and theme, removing DesktopPage and InteractiveContainer from the stack entirely, folding their features into the new SukiWindow
This change means that the NakedWindow style will be the standard for everyone, and core Window features can be depended on to exist as SukiWindow will be the base requirement for any SukiUI based app.
The move to desktop only (for what I guess will end up being a 6.0 release at this point) is a good opportunity to make major breaking changes that would make dev experience smoother, no more need for the secret sauce combination of NakedWindow class applied to a window, containing a DesktopPage with an InteractiveContainer inside.
I'm happy to work on this personally, I've got something basic running locally just need to reorganise everything, but obviously this will be a fairly significant breaking change.

Well showed like that I agree 👍
And for 6.0 focused on desktop only .. that was precisely my goal. Focusing on desktop, removing obsolete mobile controls, polishing last details to make SukiUI more than a UI Theme but a real complete toolkit to make modern richly animated apps easily.
So yes, it's definitely a smart move, let's do that

Fixed by #62


writeFromFile streams file content instead of reading it into memory

It is a bit hurtful to read several GBs into memory at once instead of streaming it.

Hm, please note: dio did throw some error that I'm not really willing to investigate right now, I'd rather close this PR. Btw. why dio, and why not package:http?


Joint simulation of lgsvl and Apollo

Hi! Mr.daohu!
How do you configure the file of 'bridge.sh' during lgsvl simulation?
Where can I find the code of this file?

This is more than what I support, in simple terms, you can refer to lgsvl's tutorials


feat: allow fastify v4 as a peer dependency

Sorry for the late reply and thanks for contributing. There is a typo in the commit message. Could you please fix it? I'll merge the PR afterwards

Yep, typo fixed. Thanks!


MRG: Small change to TrackerBinom docs

Upon closer inspection, it looks like TrackerBinom isn't actually doing what we said it was doing. This PR is just to make the docs make sense.

Thanks for the fix.


Add all argument constructor to generated classes and make setters like a builder

Reason/Context
Now generated classes have only one default no argument constructor and classic setters (set field value and return void).
I suggest at least one changes:

add more constructor to generated classes: all argument constructor
make setters like a builder (set field value and return this object)

This changes can increase readability of generated classes and decrease unnecessary verbose when using models in client services.
Description
Add all argument constructor to generated classes OR (AND) make setters like a builder

Hello @vladigeras
Thank you for the feedback.
I think it's also third option to use records.
About all argument constructor I see a drawback in readability when object has 10+ fields. Maybe argument constructor should be made for required fields.
Builder is also a good option.
I'll think about it

"About all argument constructor I see a drawback in readability when object has 10+ fields".
Kotlin named arguments)).
I suggest, that all argument constructor can be added as optional way to create an object. If it unsuitable way, then programmer can skip it and use another way.
Can we use record for class generation now? For example, with some parameters
Use records = limit minimal Java version as 16


Add psycopg2 to requirements

Just added psycopg2-binary to pipeline/requirements.txt. That's it.
Resolves #91

Absolutely devasting, can't believe you would od such a thing


Support Internet Explorer 11

Icons don't show. I had a similar issue during the tutorial, which I think meant I got stuck, but other Windows 8.1 teething issues meant my network connection kept dying - taken me about two days to get it stable enough to post this feature after a brief comment on #osm-dev before my network connection first died.

Quick update on this issue... None of the IE versions support referencing an external svg file in a <use> element.  However the changes made in #2811 fix this issue, because we now bring the svg sprite file inline: we use d3.xhr to load the sprite svgs contents directly into the <defs> section.  This allows us to do a bunch of clever css styling tricks on the svg symbols, and gives us IE support as a side benefit.
I'm leaving this ticket open because there is still an issue with oneway markers, and potential fix described in #2571.  But this is awesome that we are very close to being able to support IE11.

SVG External files are supported in the latest update :-)
http://blogs.windows.com/msedgedev/2015/11/16/introducing-edgehtml-13-our-first-platform-update-for-microsoft-edge/
perhaps this update gives some progress for iD.


Improve UI in Classifai Homepage.

Description
Added Classifai version, copyright and change main logo to classifai community.
Fixes # (issue)
Type of change

Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[x] UI Improvement

Tested on?

[x] Windows
[ ] Linux Ubuntu
[ ] Centos
[ ] Mac
[ ] Others  (State here -> xxx )

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged

Changes made:

Changes made:

Looking great. Just need one small changes from
Version 2.0.0 Alpha
to
Version: 2.0.0 Alpha
and no other comments from me

in the comment above, thanks


Link to specific timecode of Media Object

As a sports historian,
I want to link to a specific time point in an audiovisual object,
So that the people I'm sharing it with don't have to manual find that point in the recording.
Ideally this would be possible via the persistent URL/ARK.

Dependent: #47 #48


chore(main): release 2.32.0

:robot: I have created a release beep boop
2.32.0 (2024-12-02)
Features

change IM link (#280) (3351c3e)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ai4os/ai4-dashboard/releases/tag/v2.32.0 :sunflower:


Week 4 Review Ticket

Link to my Collegeboard Collaboration notes
Link to my Focus and Habits notes

Link to my video
Comp-Sci Journey

Good work on your video, you clearly explained every step and had all the requirements. Great job on your video notes/hacks for both the psychology video and the college board video. Also I liked how you did the comp sci journey. It's very cool to see how you have progressed and understood more about computers over the years. Good work this week, Ryan!

Hello Ryan,
I liked your video because it includes everything and was easy to follow. I like how you formatted your notes because like your video, your notes were also easy to follow. I believe your work deserves a 2.7 or higher. Higher because your notes are very well done.


Add supportedLocales

Hi @ookami-kb,
I am using this library and would like to create a Pull request to add supportedLocales to the Storybook widget.

In the new version, the storybook doesn't use MaterialApp for its own interface, so you can just provide your own instance of MaterialApp with all the needed parameters as a wrapper.


Fixes uninitialized local variable.

fixes https://github.com/emqx/nanomq/security/code-scanning/1023

indeed


access ports by alias

Some times ref.ports['o1']  we have different port_names ref.ports['in0']
can we add something like?
ref.ports_by_alias['o1']

On a related note, it would be convenient for Ports to implement get, similar to dict.get.

@joamatab what I was thinking of is to do the following:
ref.ports.copy(rename_function) to give you a new Ports object. Now, the problem is that this will first apply the transformation of the instance. But I assume you want the naming scheme applied to the initial cell ports and not the transformed instance ports? In that case this will take a bit longer.

@95-martin-orion what would be the use case for a get? Sure it's not hard to implement, but I would like to know what would be the use case, as I struggle to see where that could ever be useful.

This has been implemented in the method mentioned above

@95-martin-orion what would be the use case for a get? Sure it's not hard to implement, but I would like to know what would be the use case, as I struggle to see where that could ever be useful.

This is primarily a consistency request: Ports already implements most of the functionality of dict, but not having get means that functions which operate on dicts will sometimes fail if applied to Ports. (I had an explicit example when I originally requested this, but I just got back from a month of vacation and can't recall where I left off...)


Game broken

When attempting to access this at https://githubschool.github.io/github-games-ctyler123, I am getting a 404. This could be caused by a couple things:

GitHub pages needs to be enabled on main. You can fix this in the repository settings.
the index.html file is incorrectly named inde.html. We will fix this together in class.

Can you please fix the first bullet, please?

Resolves #3


branch ambiguously defined for ImageUpdateAutomation as well as for git repo

https://toolkit.fluxcd.io/guides/image-update/:
ImageUpdateAutomation takes a branch parameter, but so does the git-repo it refers, this seems ambiguous to me, you want to refer the git repo it was defined in, and that's already defined in the GitRepository - hence it should be sufficient with the gitRepositoryRef.
spec:
checkout:
branch: main <--
gitRepositoryRef:
name: flux-system <-- this repo already has a branch defined
Maybe a bit related to https://github.com/fluxcd/image-automation-controller/issues/85

Also pertinent: the discussion in https://github.com/fluxcd/flux2/discussions/665

@davidkarlsen thank you for reporting this. This has been fixed in version v0.9.0 with the introduction of API version v1alpha2.
The change allows for ImageUpdateAutomation to optionally set checkout references in the same way as in the GitRepository objects and when not set it defaults to the value set in the GitRepository references to by the sourceRef field.
For more information, including the migration path, please check the documentation.
I will be closing this issue now, but feel free add a comment here in case you want this reopened.


radicle: custom CanonicalFormatter

The olpc-json crate's CanonicalFormatter does not escape certain control characters, including new lines. This means that when a COB gets serialized that includes new lines, those new lines are serialized verbatim. Upon deserialization serde_json -- and any other JSON deserializer -- will fail due to the encounter of these control characters.
This behaviour was prevented in radicle-link with the definition of its own CanoncialFormatter that encodes the control characters correctly.
Inline this definition of the formatter, under MIT license, to ensure the correct and remove oplc-cjson.
The behaviour is checked using a multiline test in the issue COB.
Fixes #351

Nice work. Tested locally and seems to have resolved the issue.


Slight refactor of amqp tests

Just a slight refactor to cleanup the amqp tests slightly.

Changes Unknown when pulling dcca21df3b5ad88de05bc4af3db0df84dc4cbeb1 on amqp-test-fake-ready-refactor into ** on master**.


Wrong year displayed in header

When displaying the year on the top ruler the value is one year less then the data. The bottom ruler displays the correct year.
By using the browser debugger, you can see that the "year-2018" element has the value "2017".

Hi there,
Thank you for telling me that.
I'll fix it asap.

It seems to be related to the specification of the format.
If you specify Year : "short" then the year is displayed correct,
but if you specify Year:"numeric", it is displayed wrong

Thank you for information.
I've fixed that displayed years on the ruler at new version.

Great, thank you.


Great stuff

Just wanted to thank you for this cool project, keep up the great work ☺

Thank you! :)


error: expected primary-expression before ‘>’ token

$ cd semantic-histogram-based-global-localization-main
$ mkdir build
$ cd build
$ cmake ..
$ make
~/semantic-histogram-based-global-localization-main/src/pointCloudMapping.cpp:24:63: error: expected primary-expression before ‘>’ token
GlobalCloud = pcl::make_shared<pcl::PointCloud>();
~/semantic-histogram-based-global-localization-main/src/pointCloudMapping.cpp:24:66: error: expected primary-expression before ‘)’ token
GlobalCloud = pcl::make_shared<pcl::PointCloud>();

maybe you can change the PCL version and try, the PCL I used is PCL 1.12.0

ok，i will try. Thanks a lot.

maybe you can change the PCL version and try, the PCL I used is PCL 1.12.0
ok，i will try. Thanks a lot.


update / publish helm chart to artifacthub.io or any other public helm chart repository

currently README has no instructions regarding helm chart installation. I see two months back only helm chart has been added into folder but hasn't been published yet.
We are currently thinking adopting this to complete our internal k8s security to make sure everything under one umbrella. we already use Kyverno and policy-reports.

@fjogeleit

Hey, thanks for your request.
The README has instructions about adding the Helm Chart from Github pages, but I can also will have a look on adding it to artifacthub.

@fjogeleit thanks for the prompt reply. I have also watched one of your talk where your team spoke about falco-adapter and trivy-adapter listed here
little confuse with trivy-adapter vs trivy-operator-polr-adapter ? aren't they same

The Trivy Adapter does not translate the different trivy Reports to PolicyReports. It is a CLI to start a scan of existing workloads and creates a PolicyReport out of them. So its an autonomous for local or workflow usage.
Trivy Operator Polr Adapter is related / has a dependency to the Trivy Operator CRDs. It only watches for those CRDs and translates them into (Cluster)PolicyReports, the actual work is done by the Operator.

Added to artifact hub: https://artifacthub.io/packages/search?repo=trivy-operator-polr-adapter
Will also get the verified badge soon

Thank you @fjogeleit

@fjogeleit https://artifacthub.io/packages/helm/trivy-operator-polr-adapter/trivy-operator-polr-adapter doesn't include a README there. maybe something for later.

Will have a look, thanks


Referencing issues in PR in description or comment does not trigger update and comment added to ADO item

Example can be seen here https://github.com/a11smiles/alz-sync-bicep/issues/3

these are the comments we'd like to see


Update to Node.js v20

When using this action I'm getting:

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20<EMAIL_ADDRESS>For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

There's a PR about it https://github.com/pnpm/action-setup/pull/110


Integration FestoBionicFlower

CHANGES

generated blockly resources
add festobionicActions.js for "festobionicActions_stepmotor"
add ledoff/ledon for festobionicflower in makeblockactions.js
add festobionicflower to robactions.java "robActions_led_on"
change robConfigDefinitions.js for festobionicflower: confBlocks.light.festobionicflower, confBlocks.touch.festobionicflower, confBlocks.rgbled.festobionicflower, confBlocks.stepmotor.festobionicflower
change robcSensorDefinitions.js for festobionicflower: sensors.light.festobionicflower, sensors.touch.festobionicflower, sensors.timer.festobionicflower
change \robMsg\json\de.json , \robMsg\json\en.json , \robMsg\json\qqq.json  , \robMsg\robMessages.json for 4 new Messages
add festobionic_playground.html
add programConfiguration_playground.html

squash, rebase and commit message done

accepted with 2612179ee3542dbb511e73bf6fa582e741655804, but

.gitignore changes are removed by us
core/xml.js changes are removed by us
rebuild are done by us


Changing message name from assertGameIncludes to assertMatchIncludes

Pull Request Test Coverage Report for Build 37

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 34:
0.0%

Covered Lines:
165

Relevant Lines:
165

💛  - Coveralls

Pull Request Test Coverage Report for Build 37

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 34:
0.0%

Covered Lines:
165

Relevant Lines:
165

💛  - Coveralls


Ignore if door is locked option

Option for plugin developers to allow door usage if door has lock and
player is not allowed to open them.

Nice one


limayaml: add a param field for defining variables used to customize scripts and other elements within lima.yaml.

The defined variables can be referenced within lima.yaml as {{.Param.Key}}.
The fields where this can be utilized are as follows:

provision[%d].script
probes[%d].script
copyToHost[%d].{guest,host}
portForwards[%d].{guestSocket,hostSocket}

It also changes:

limayaml: add a check to verify whether the variables defined in param are actually used.

Following change has been merged as a separated PR: https://github.com/lima-vm/lima/pull/2501

limactl start: fix the issue where using --set would overwrite the existing instance's lima.yaml without validation.

Following changes will be opened as a separated PR: https://github.com/lima-vm/lima/pull/2515

docker.yaml: add .param.ContainerdImageStore
By passing the --set .param.ContainerdImageStore=true option to limactl {create,start,edit}, the .features."containerd-snapshotter" option will be enabled in docker/daemon.json inside the VM.
docker.yaml: add .param.Rootful
By passing the --set .param.Rootful=true option to limactl {create,start,edit}, Docker inside the VM will run in rootful mode.
docker-rootful.yaml: make everything common except for setting .param.Rootful=true in docker.yaml.

It might be better to split this into multiple parts, but for now, I’ll open it as a draft.
Thanks,

I have separated the fix for limactl start --set into https://github.com/lima-vm/lima/pull/2501.

can not reproduce panic in Unit Test on local machine
https://github.com/lima-vm/lima/actions/runs/10050557033/job/27778685157?pr=2498#step:5:2584

panic: test timed out after 10m0s
...
FAIL	github.com/lima-vm/lima/pkg/guestagent/kubernetesservice	600.059s

I also want to include the following in lima.yaml:
mounts:
- location: "~/.cache/ubuntu/{{.Name}}/var/cache/apt"
  mountPoint: "/var/cache/apt"
  writable: true
- location: "~/.cache/ubuntu/{{.Name}}/var/lib/apt"
  mountPoint: "/var/lib/apt"
  writable: true

Should this be a separate PR?

This PR has 2 warnings from yamllint:
$ yamllint examples/docker.yaml
examples/docker.yaml
  58:14     warning  too few spaces before comment  (comments)

$ yamllint examples/docker-rootful.yaml
examples/docker-rootful.yaml
  58:14     warning  too few spaces before comment  (comments)

You can fix by adding another space before the comments, like
-- mode: user # configure docker under non-root user
+- mode: user  # configure docker under non-root user

Personally I don't really agree with the requirement for 2 spaces between content and comments, and would change .yamllint config instead:
--- .yamllint
+++ .yamllint
@@ -7,6 +7,8 @@ rules:
     indent-sequences: false
   truthy:
     allowed-values: ['true', 'false', 'on', 'off']
+  comments:
+    min-spaces-from-content: 1
   comments-indentation: disable
   document-start: disable
   line-length: disable

updated and rebased

Updated

opened:

https://github.com/lima-vm/lima/pull/2515

@lima-vm/maintainers
Is this safe to merge in v0.23?

I am not a big fan of mixing in upper case, with the rest of the yaml that uses lower case...
Even if it means having to "translate" a param: key: value into a {{Param.Key}} so that they can each look their best

Even if it means having to "translate" a param: key: value into a {{Param.Key}} so that they can each look their best

To reference param: {key: value}, use {{.Param.key}}. There is no functionality to convert key to Key.

Even if it means having to "translate" a param: key: value into a {{Param.Key}} so that they can each look their best

To reference param: {key: value}, use {{.Param.key}}. There is no functionality to convert key to Key.

I believe there is no way to reference non-exported fields from Go templates, so {{.Param.key}} cannot work.
I think what @afbjorklund meant was that you have this in your lima.yaml:
param:
   containerdImageStore: false
   rootful: false

And we would automatically capitalize the first letter when putting it into the template data struct, so you could reference it as {{.Param.Rootful}}.
Now you could argue that we are already transforming param → .Param, so doing the same for the keys is consistent with that.
Personally I don't like this, and I think param and rootful are semantically different entities, and don't need to be treated the same. I would prefer that the parameters are spelled consistently across the whole lima.yaml file and not magically change their first letter to uppercase.
I would maybe go a completely different way, and use the same conventions I would use for environment variables for params:
param:
   CONTAINERD_IMAGE_STORE: false
   ROOTFUL: false

And then reference them as {{.Param.ROOTFUL}}. While I don't think we should enforce this, it may be something we want to use in the bundled templates.
What do other people think?
Assuming we are not implementing @afbjorklund's suggestion to auto-capitalize param names (I would vote against it), we should catch them in validation.

I believe there is no way to reference non-exported fields from Go templates, so {{.Param.key}} cannot work.

{{.Param.key}} works because Param is a map[string]string.
In my local tests, #2515 actually works when I change it to:
param:
  ContainerdImageStore: true
  rootful: true

and use {{.Param.rootful}} in combination.

Now you could argue that we are already transforming param → .Param, so doing the same for the keys is consistent with that.

The reason it is .Param for the reference is not because text/template is converting it automatically, but because it is being passed to text/template as Param in this line of the code.

{{.Param.key}} works because Param is a [map[string]string]

Thanks, didn't think of that. In that case I'm even more against automatically capitalizing the first letter of params.

The reason it is .Param for the reference is not because text/template is converting it automatically, but because it is being passed to text/template as Param

I understand. And the same way we could capitalize the first letter of k before we assign the values in the param list with param[k] = v.
I just think we shouldn't.
It is also possible that I misunderstand what @afbjorklund is asking for.
Just to be clear: I think the code should be left the way it is right now.

@lima-vm/maintainers Is this safe to merge in v0.23?

I think it is, and would like to see it included!

Thanks! 🙏🏻

I understand. And the same way we could capitalize the first letter of k before we assign the values in the param list with param[k] = v.

That was indeed my suggestion, and it was purely aesthetical (there was something "wrong" to me, with Key = value)
Now the params will work like environment variables, and I suppose there is some Lowest Common Denominator in that.


Urdu Text Detection

Deep Learning Simplified Repository (Proposing new issue)
:red_circle: Project Title : Urdu Text Detection
:red_circle: Aim : Create DL model which will identify the texts written in Urdu.
:red_circle: Dataset : https://www.kaggle.com/datasets/maryambiibii/urdu-artificial-text-text-detection
:red_circle: Approach : Try to use 3-4 algorithms to implement the models and compare all the algorithms to find out the best fitted algorithm for the model by checking the accuracy scores. Also do not forget to do a exploratory data analysis before creating any model.

📍 Follow the Guidelines to Contribute in the Project :

You need to create a separate folder named as the Project Title.
Inside that folder, there will be four main components.

Images - To store the required images.
Dataset - To store the dataset or, information/source about the dataset.
Model - To store the machine learning model you've created using the dataset.
requirements.txt - This file will contain the required packages/libraries to run the project in other machines.

Inside the Model folder, the README.md file must be filled up properly, with proper visualizations and conclusions.

:red_circle::yellow_circle: Points to Note :

The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include issue number along with it.
Follow Contributing Guidelines & Code of Conduct before start Contributing.

:white_check_mark: To be Mentioned while taking the issue :

Full name :
GitHub Profile Link :
Email ID :
Participant ID (if applicable):
Approach for this Project :
What is your participant role? (Mention the Open Source program)

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

I would like to take up this issue!

Can you mention all the details please @abhishak3

yeah sure.
Issue No: #26  Urdu Text Detection
Full Name: Abhishek Pandey
Github Profile Link: https://github.com/abhishak3
Email ID<EMAIL_ADDRESS>Approach: Going to experiment with various DL models + figuring out their performance measure
Participant Role : Contributor(SSOC)

Issue assigned to you @abhishak3

Updates please @abhishak3

I will update you in few hours.

@abhisheks008 I am unable to find any label in the given training data. Please have a look!

The dataset is perfect, I have checked that. You need to create a deep learning model which extract the sentences written in Urdu from the video/images.
@abhishak3

LOL! It's okay, it happens. @abhishak3


ActionState action is never released if InputMap is removed while input is held

Version
bevy = "0.8.0"
leafwing-input-manager = "0.5.2"
Operating system & version
Windows 11 & Wasm
What you did
I removed an InputMap from an entity (e.g. it was captured an taken over by an AI.) while pressing a button.
What you expected to happen
When I remove the input map, the related ActionState would no longer report the buttons from that InputMap as being pressed.
What actually happened
The ActionState continued say the action was being pressed after the InputMap was removed.
Additional information
You can see this happening in the 0.3.0 release of my bevy jam 2 game: https://github.com/paul-hansen/bevy-jam-2/releases/tag/v0.3.0
If you are captured while you are boosting (press spacebar) your entity will keep boosting forever even though it should only be boosting if its new leader is boosting.
To work around this, I'm now adding this line during CoreStage::Last to clear the inputs from that frame (idk if this will have undesired side effects?)
action_state.set_action_data(Actions::Boost, ActionData::default());

I'd be happy to work on a PR for this after the jam is over. If you have any info on what you think the desired fix should be let me know.
Also, I run into the same problem of inputs not resetting when I set the action's data manually using set_action_data, though that was a bit more expected. It isn't clear if that's an appropriate way to send inputs for AI or not, but that's related to https://github.com/Leafwing-Studios/leafwing-input-manager/issues/70 .

A naïve solution might be to just reset all of the action data when an InputMap is removed from an entity, but I'm not sure if that might cause missed inputs or something. Perhaps iterate over the inputs from the InputMap and unapply them when the input map is removed would be a more careful solution?
If there isn't a good way to handle this, maybe we should just document that if InputMap is removed the action data is not cleared and will need to be cleared manually if being taken over by an AI or perhaps another InputMap. Could include an example of a system that does this.
Also I wasn't sure if this should be considered a bug or not, feel free to re-label this as usability or whatever.

A naïve solution might be to just reset all of the action data when an InputMap is removed from an entity, but I'm not sure if that might cause missed inputs or something

This would be my initial approach here :)


Provide a hook for an extension to contribute a CI workflow

From https://github.com/aperis-docs/react-static-plugin-aperis-doc-pages/issues/3#issuecomment-753733558:

e.g. we can have workflow files namespaced for Aperis/Paneron. e.g. .github/workflows/aperis_xxx.yml, and do not delete the existing workflow files not created by Aperis? People will want to have custom workflows depending on datasets.

Just a suggestion.

From https://github.com/aperis-docs/react-static-plugin-aperis-doc-pages/issues/3#issuecomment-753733558:

e.g. we can have workflow files namespaced for Aperis/Paneron. e.g. .github/workflows/aperis_xxx.yml, and do not delete the existing workflow files not created by Aperis? People will want to have custom workflows depending on datasets.

Just a suggestion.

I am considering that option. I think it’s a bit of a crutch since any CI flow conceptually applies to a whole repo even if scoped, e.g. a change to one dataset will cause all dataset CIs to run.
We will want cross-dataset CI flows for the updated open project framework anyway, but maybe they could coexist with scoped flows, and scoped flows should be easier to implement.

I am considering that option. I think it’s a bit of a crutch since any CI flow conceptually applies to a whole repo even if scoped, e.g. a change to one dataset will cause all dataset CIs to run.
We will want cross-dataset CI flows for the updated open project framework anyway, but maybe they could coexist with scoped flows, and scoped flows should be easier to implement.

@strogonoff agreed. Namespaced workflows are definitely easily to manage.

@strogonoff agreed. Namespaced workflows are definitely easily to manage.

a change to one dataset will cause all dataset CIs to run.

GitHub actions workflows can be scoped to only run on certain path changes.

a change to one dataset will cause all dataset CIs to run.

GitHub actions workflows can be scoped to only run on certain path changes.

a change to one dataset will cause all dataset CIs to run.

GitHub actions workflows can be scoped to only run on certain path changes.

Okay, I stand corrected, this is great.

a change to one dataset will cause all dataset CIs to run.

GitHub actions workflows can be scoped to only run on certain path changes.

Okay, I stand corrected, this is great.


Error: spawn E2BIG when running in Docker

Hello everyone,
I've been dealing with an interesting and, to me, not very self-explanatory error when running Next.js in Docker using the provided Dockerfile. This whole rabbit hole started after we decided to upgrade from<EMAIL_ADDRESS>to<EMAIL_ADDRESS>(not the latest version due to https://github.com/vercel/next.js/issues/54765).
Basically, what happens is that when running under dev or building and running locally on macOS with a built project, it works fine. However, after building the Dockerfile and running it, it immediately crashes with the following error:
docker run -p 3000:3000 ecommerce-base-storefront
Error: spawn E2BIG
    at ChildProcess.spawn (node:internal/child_process:421:11)
    at spawn (node:child_process:761:9)
    at fork (node:child_process:172:10)
    at ChildProcessWorker.initialize (/app/node_modules/next/dist/compiled/jest-worker/index.js:1:10927)
    at new ChildProcessWorker (/app/node_modules/next/dist/compiled/jest-worker/index.js:1:10815)
    at WorkerPool.createWorker (/app/node_modules/next/dist/compiled/jest-worker/index.js:1:6315)
    at new BaseWorkerPool (/app/node_modules/next/dist/compiled/jest-worker/index.js:1:8183)
    at new WorkerPool (/app/node_modules/next/dist/compiled/jest-worker/index.js:1:6111)
    at new Worker (/app/node_modules/next/dist/compiled/jest-worker/index.js:1:23381)
    at createServerHandler (/app/node_modules/next/dist/server/lib/render-server-standalone.js:21:26) {
  errno: -7,
  code: 'E2BIG',
  syscall: 'spawn'
}

I'm not blaming next-translate-routes; however, after several hours, I decided to delete all _routes.json files, and voilà - it started. So I reverted it back and started deleting routes.json one by one (with docker build after each file was deleted). It was fairly time-consuming, but I managed to find a few pages where after deleting _routes.json, projects started working again.
However, there's nothing that would allow me to relate these _routes.json files together and find some actual issue. They're all valid JSONs with a valid structure for this library (it worked under 12.2.12) and the pages, of course, build with no issues.
The worst part? I'm unable to reproduce this error in a "cleaner" environment than our main project, so I'm quite stuck in a situation where a few routes cannot be translated. I primarily wanted to ask if somebody else has seen this error as well. 😞
EDIT:
Okay, so it turns out (at least now), that this error is caused by large amount of _routes.json files that are parsed (?). I endedup naming some files as stoproutes.json (so that they don't get parsed) and it works.
@cvolant don't you have some inside to this, please?  Can I somehow print out number of rewrites, etc. to debug this a bit more?
EDIT2:
Okay, now I'm almost sure, it's caused by large amount of something. As previously mentioned - i renamed some of my routes to stoproutes.json. I set
translateRoutes: {
    routesDataFileName: "stoproutes",
    debug: true,
  },

and it works. Of course, many pages are not translated, but it works, so there's no syntactical issue or something.

Strange... We run our project under docker too, without any issue.
Could you count the number of elements in your routes tree? Just execute the following code in the console of your browser while it displays your website:
count = (children) => children?.reduce((acc, child) => acc + 1 + count(child.children), 0) || 0;
count(__NEXT_TRANSLATE_ROUTES_DATA.routesTree.children)

I get 80. Do you have a lot more?

Hi @cvolant ,
thank you for your response! I get 108 elements and 18 routes.json. However, I've reduced number of routes.json in order to prevent this error.
I tried to add few more and 109 elements and 20 files + 1 file would make it crash with this error.
Hope it makes sense like this. I've a feeling it has something to do with my _routes.json having quite a lot of languages?
{
	"/": {
		"cs": "objednavka",
		"sk": "objednavka",
		"en": "order",
		"de": "auftrag",
		"pl": "zamowienie",
		"default": "objednavka",
		"cs-CZ": "objednavka",
		"en-BE": "order",
		"en-BG": "order",
		"en-CY": "order",
		"en-DK": "order",
		"de-DE": "auftrag",
		"en-EE": "order",
		"en-FI": "order",
		"en-FR": "order",
		"en-GR": "order",
		"en-HU": "order",
		"en-IE": "order",
		"en-IT": "order",
		"en-LV": "order",
		"en-LT": "order",
		"en-LU": "order",
		"en-MT": "order",
		"en-NL": "order",
		"pl-PL": "zamowienie",
		"en-PT": "order",
		"en-RO": "order",
		"en-SI": "order",
		"sk-SK": "objednavka",
		"en-ES": "order",
		"en-SE": "order",
		"en-GB": "order",
		"de-AT": "auftrag"
	}
}

I'm honestly not sure why I don't use fallback languages as of #66 since it's quite some time since I digged into this issue and ended up banging my head against wall and just not translating some of the routes 😅

:open_mouth: I can't imagine what your redirects/rewrites look like ! :smile:
Indeed, fallback languages is probably the way to go.  I hope it will solve you issue.

Well! They're pretty big 🙈. However, this ended up beeing the best solution for making Next.js locale feature work with locale-COUNTRY coding in eCommerce 👎.

@cvolant So I rewrote several _routes.json into fall back languages. I  tested that and it sadly did not help 😞.

Could you tell me how big are your rewrites?
JSON.stringify(__BUILD_MANIFEST.__rewrites).length

Mine has 9300 characters...

Interesting and thank you - mine in the working situation (so few _routes.json less) has 8686 characters. 🤔 So it might not be what I think...

Difficult to say. Do you have a working configuration without Docker but with all the routes files ? If you reach ~8000 with a few routes files, you probably end up with a lot bigger rewrites objet... The redirects object could be the cause too : it is bigger than the rewrites one, but is more difficult to measure since it does not reach the browser...

Hi! I'm sorry it took me that long; it has been a hectic period on my end lately.

Do you have a working configuration without Docker but with all the routes files

Yes, of course! I modified my project so that it's in the state where docker looks like:

But npm run build && npm run start works flawlessly (actually never had issue running it outside of docker):

Commands you suggested previously output following:

#elements in the routes tree: 109
#routes.json files: 20
#characters in rewrites:  10814

Number of rewrites has a significant increase, but I guess it's mostly due to the fact that some of my routes look like .../.../shipping-billing-details.
Do you think that might be the cause of the issue? So that the Node worker can't maybe allocate enough memory inside of the container to store that?
Thank you very much for your help 🙏

I am a total newbie on Docker, so I am quite helpless here, but the numbers you gave don't seem to be that much, and we use Docker too with similar numbers, without such an issue...

I asked our Docker master Jedi, and he says that it looks more like a Node issue than a Docker issue, but that you seem to be on MacOS where Docker could behave a bit differently. Could you try to run your project on a Linux distro and check if you still have the issue? What version of Docker do you use?

Thank you very much for quick response! Sadly, it crashes on both MacOS and on our production Ubuntu 22.04 with Docker 23.0.1 🙁

Thank you very much for quick response! Sadly, it crashes on both MacOS and on our production Ubuntu 22.04 with Docker 23.0.1 🙁

By the way, I'm using 1:1 Dockerfile from https://github.com/vercel/next.js/blob/canary/examples/with-docker/Dockerfile and tested node:20-alpine and node:21-alpine

Is there any possible solution here?

Is there any possible solution here?

Do you have the same issue? 🤔 I haven't resolved it, we just kept only most crucial urls translated and all new ones are untranslated for now.

Is there any possible solution here?

Do you have the same issue? 🤔 I haven't resolved it, we just kept only most crucial urls translated and all new ones are untranslated for now.

Yes, I have the same issue 😞 I have to proceed with the solution that some languages will not have translations.

That's how I managed to solve this case. It was enough to update next to version 13.5.2 and slightly modify next-translate-routes.
In version 13.5.2 a new thing  cleanup was added.

That's how I managed to solve this case. It was enough to update next to version 13.5.2 and slightly modify next-translate-routes.
In version 13.5.2 a new thing cleanup was added. The new thing added in next seems to have solved this problem.

Good point! So you're now running with no issues? I was stuck on older version (13.4.2) due to this (Next.js problem)[https://github.com/vercel/next.js/issues/54159#issuecomment-1861883691]. However I think it's time to give it a try. Would you mind sharing how did you fixed the ROUTER_CONTEXT_PATH errir comming from<EMAIL_ADDRESS>Thanks!

So after some trial and error, I think I'm back on previous version (both next and next-translate-routes). Even though E2BIG seems to be fine, other errors occured which are mentioned in other currently open issues.
https://github.com/hozana/next-translate-routes/issues/77


Create External Table: should clear column mapping cache when go previous page then next again

Issue Type: Bug

Open Create External Data wizard and connect to Oracle
Get to table mapping page on create external data wizard
Expand database and rapidly click a bunch of tables until you error
The column mappings for current table will be empty
Go back to the connection page and click "Next" again. This reconnects and on expanding databases, clearly updates the list of tables
Click on the table name which previously errored and showed empty column mapping.

Expected:

Should re-query the column mappings and update with correct data
Actual:
This instantly shows as being empty like before. This shows the cache isn't being cleared out on going back. It's important to do this (which we currently do for the tables cache) so that we can accurately update data and handle weird error cases cleanly.

Azure Data Studio version: Azure Data Studio 1.2.3-insider (8439cde6106ec3bf443fff5e8a8b54c5e98ac170, 2018-11-01T03:48:03.475Z)
OS version: Darwin x64 18.2.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz (8 x 2200)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: enabledrasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 2

Memory (System)
16.00GB (0.31GB free)

Process Argv
/Users/kevcunnane/Downloads/insiders_nov/Azure Data Studio.app/Contents/MacOS/Electron

Screen Reader
no

VM
0%

@geleems please confirm this is fixed and close it out, thanks! I believe you already solved this one.

this was fixed.


Add checks

This PR adds pre-commit checks and CI to the repo

To get the Windows test to pass I needed to upload the MinGW64 library as a zip file. This is something we could move to another location if need be. It is also worth noting that the windows test can still be a bit flaky, I think it picks up the wrong compiler as it will fail at the compilation stage.

mac CI test will be done in https://github.com/mantidproject/quasielasticbayes/issues/14

want to update the linux and window tests to use a matrix:
https://stackoverflow.com/questions/57946173/github-actions-run-step-on-specific-os
https://ncorti.com/blog/howto-github-actions-build-matrix

Im closing this as the history has become a mess and opening a new PR with a clean history


Creating associations initialized via 'build' no longer works in FactoryBot 5.0

He guys,
After upgrading to v5.0 of FactoryBot today we started having the following issue.
Out factory is defined like this:
FactoryBot.define do
  factory :task_profile do
    profile
    task { build(:task, account: profile.account) }
  end
end

Where TaskProfile is a model, that belongs_to :profile and belongs_to :task.
This allows us to make sure both profile and task belong to the same account.
So now after we do create(:task_profile), it creates the entry with task_id: nil. Previously it was correctly filled in with id of associated task.
Could you please suggest a fix for the problem? Thank you.

I wasn't able to reproduce this. Can you update this script to produce the error you described?
require "bundler/inline"

gemfile(true) do
  source "https://rubygems.org"

  git_source(:github) { |repo| "https://github.com/#{repo}.git" }

  gem "rails", "5.2.2"
  gem "sqlite3"
  gem "factory_bot", "5.0.0"
end

require "active_record"
require "minitest/autorun"
require "logger"
require "factory_bot"

# This connection will do for database-independent bug reports.
ActiveRecord::Base.establish_connection(adapter: "sqlite3", database: ":memory:")
ActiveRecord::Base.logger = Logger.new(STDOUT)

ActiveRecord::Schema.define do
  create_table :task_profiles, force: true do |t|
    t.integer :profile_id
    t.integer :task_id
  end

  create_table :tasks, force: true do |t|
    t.integer :account_id
  end

  create_table :profiles, force: true do |t|
    t.integer :account_id
  end

  create_table :accounts, force: true do |t|
  end
end

class Account < ActiveRecord::Base
end

class Profile < ActiveRecord::Base
  belongs_to :account
end

class Task < ActiveRecord::Base
  belongs_to :account
end

class TaskProfile < ActiveRecord::Base
  belongs_to :profile
  belongs_to :task
end

FactoryBot.define do
  factory :account do
  end

  factory :profile do
    account
  end

  factory :task do
    account
  end

  factory :task_profile do
    profile
    task { build(:task, account: profile.account) }
  end
end

class BugTest < Minitest::Test
  def test_factory_bot_stuff
    task_profile = FactoryBot.create(:task_profile)

    assert task_profile.task_id.present?
  end
end

@composerinteralia I have entered my versions to your script and couldn't reproduce as well. We're using pg v. 0.21.0 as a database adapter and Postgres 9.6 and also Rspec v.3.8.2. Unfortunately pg setup in this script seems a bit more complicated and didn't work for me straight away. I'll try to play with it over the weekend and make it reproducing the issue. Thank you.

Upgrading to factory_bot_rails v5 broke some factories for me too, for what appears to be the same reason.

This may also be related to https://github.com/thoughtbot/factory_bot_rails/issues/314

@composerinteralia, here is the test for the failing scenario. Feel free to uncomment the earlier version of FactoryBot gem to make it passing. Hope it helps
require "bundler/inline"

gemfile(true) do
  source "https://rubygems.org"

  git_source(:github) { |repo| "https://github.com/#{repo}.git" }

  gem "rails", "<IP_ADDRESS>"
  gem "sqlite3", '1.3.13'
  gem "factory_bot", "5.0.0"
  # Uncomment to make the test pass
  # gem "factory_bot", "< 5"
end

require "active_record"
require "minitest/autorun"
require "logger"
require "factory_bot"

# This connection will do for database-independent bug reports.
ActiveRecord::Base.establish_connection(adapter: "sqlite3", database: ":memory:")
ActiveRecord::Base.logger = Logger.new(STDOUT)

ActiveRecord::Schema.define do
  create_table :task_profiles, force: true do |t|
    t.integer :profile_id
    t.integer :task_id
  end

  create_table :tasks, force: true do |t|
    t.integer :account_id
    t.integer :profile_id
  end

  create_table :profiles, force: true do |t|
    t.integer :account_id
  end

  create_table :accounts, force: true do |t|
  end
end

class Account < ActiveRecord::Base
end

class Profile < ActiveRecord::Base
  belongs_to :account
end

class Task < ActiveRecord::Base
  belongs_to :account
  belongs_to :profile

  validates :account_id, presence: true
end

class TaskProfile < ActiveRecord::Base
  belongs_to :profile
  belongs_to :task
end

FactoryBot.define do
  factory :account do
  end

  factory :profile do
    account
  end

  factory :task do
    profile
    account { profile.account }
  end

  factory :task_profile do
    profile
    task { build(:task) }
  end
end

class BugTest < Minitest::Test
  def test_factory_bot_stuff
    task_profile = FactoryBot.create(:task_profile)
    assert task_profile.task_id.present?
  end
end

Thanks so much! I'll try to take a proper look at this before the end of the week, but based on a quick glance seeing validates :account_id, presence: true, I am thinking this is similar to https://github.com/thoughtbot/factory_bot_rails/issues/314.
A temporary workaround would be to set FactoryBot.use_parent_strategy = false (we changed the default value for that configuration option). But I will see if I can come up with another solution that works with the new default for use_parent_strategy.

Just for additional context on this issue: The upgrade is breaking a quarter of spec suites according to meta analysis by depend-a-bot
https://dependabot.com/compatibility-score/?dependency-name=factory_bot_rails&package-manager=bundler&previous-version=4.11.1&new-version=5.0.0

I'm also seeing something that I think is related to this.
Instead of doing the following:
factory :service
  product # Service has a many_to_one relationship with Product
end

factory :product
  name { 'Product' }
end

I have to do
factory :service
  product { create(:product) } # Service has a many_to_one relationship with Product
end

factory :product
  name { 'Product' }
end

@pboling thank you for that information. That makes sense, since changing the default value for FactoryBot.use_parent_strategy was an intentional breaking change.
@jrgns I'm glad you were able to set FactoryBot.use_parent_strategy = false to go back to the old behavior and get your test suite passing again. If at some point you want to try out the new behavior, instead of updating the product association in the service factory, it might be worth looking at the specific tests that are failing (if there aren't too many of them). In places that you are using FactoryBot.build(:service) you may need to switch to FactoryBot.create(:service) instead.
@k-rudy your issue might be a little bit different. I still haven't had a chance to look into it too closely, but I will try to take a look soon!

@k-rudy I was able to get your test passing again by changing the task_profile factory from:
  factory :task_profile do
    profile
    task { build(:task) }
  end

to:
  factory :task_profile do
    profile
    task
  end

By letting task be an association instead of a regular attribute, factory_bot will know to create the associated task when you call FactoryBot.create(:task_profile).
What you have before used to work because although you were using the build strategy for the task, its associated profile and account were still constructed using the create strategy. factory_bot 5 changed the default for use_parent_strategy to true, thus causing the build strategy to build associations, rather than create them. building the associates doesn't quite work here, since you are validating the presence of an id.

@k-rudy thanks for the info, in the test I slightly simplified the factory, as it originally was:
factory :task_profile do
  profile
  task { build(:task, account: profile.account) }
end

To make sure when we don't pass the task explicitly, it is created for the same account as profile. From what you have said - seems like it will no longer be possible in 5.0?

@k-rudy got it. So there is something you can do, but it is not currently documented anywhere.
task { association(:task, account: profile.account) }

I have been thinking about documenting this way of creating associations inside the block, and this is a good case for it. It came up in https://github.com/thoughtbot/factory_bot/issues/1063 as well.
Using association will build the association when you are using FactoryBot.build and create the association when you are using FactoryBot.create. If you want to see the details, the method lives on the FactoryBot::Evaluator class.

@composerinteralia the proposed solution to replace build with association works like a charm for us. This is how it looks at the end:
FactoryBot.define do
  factory :task_profile do
    profile
    task { association(:task, account: profile.account) }
  end
end

Evaluator#association is now officially documented: https://github.com/thoughtbot/factory_bot/issues/1268#issuecomment-656226689


API Route Updated #6333

Issue Reference
Link: https://github.com/bagisto/bagisto/issues/6333

@devansh-webkul
There should not be a blank value on the country dropdown. Please find the screenshot Here.

Mentioned changes have been done.


Improve the UI of user and server info

Simple UI Improvements :)

Improve the UI of user and server info.
The user and server info commands should be improved :) I mean the UI

Describe the solution you'd like
Make the user and server info commands somewhat like these Dredd and R.Danny

Describe alternatives you've considered
Add some relative emojis to the support server. Well its done :) from my side

I checked user & server commands. If you don't mind; then can i give a shot to improve it?

fixed


How to connect to the ECS cluster over internet

Hi,
I have adapted the sample to run my cluster with nginx as a reverse proxy. However, I am not sure how to connect to the cluster / EC2 instance over internet. I have the private ips but I don't see a public ip except in the nat gateway.
I am new to AWS/ECS/Terraform etc. Please advice.
Thanks

Hi,
https://docs.aws.amazon.com/AmazonECS/latest/developerguide/instance-connect.html
Please ask such general questions on StackOverflow or other designated forums.


Updated and Styled Loan Calculator with new components

It solves issue #1522
Its working video,
https://user-images.githubusercontent.com/75881393/120096363-a7166180-c148-11eb-8877-3f8cd86067bf.mp4

Please @Vishal-raj-1 @ridsuteri @991rajat @urvashi-code1255 review this PR.


Awesome books: plain JavaScript with objects

Awesome books: plain JavaScript with objects 🤓
For this activity my partner @KingKowa  and I apply the next features to the project:

Implement only a basic UI with plain HTML 💯
Create a function to add a new book to the collection 📖
Create a function to remove a book from the collection 🖥

Plain JavaScript with objects
Required changes done:

Delete the commented lines
Change the license in the Readme.md file


add support for certificate challenge response

to enable registration of Let's encrypt certificates - add support for http challenge response

reverted it from main, there is some required changes.. will open a new PR


[BUG] - Uncaught SyntaxError: Unexpected token ':' when using Vite React

NextUI Version
2.3.6
Describe the bug
Getting Uncaught SyntaxError: Unexpected token ':' while using React Vite, I am not started to use any components yet, the error showing when i'm added NextUIProvider in the Main.tsx
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
.
Expected behavior
.
Screenshots or Videos
No response
Operating System Version
.
Browser
Chrome

please provide a minimal reproducible environment.

I think it because some of my chrome extensions, It is working perfectly on Incognito mode and other browsers

Closing due to no minimal reproducible environment provided.


Update cart actions to support async

Description
From discord and dev feedback we've seen it is difficult to:

batch mutations
determine action errors without looking at a global error

linesAdd(lines) // did the action finish without errors
linesUpdate(lines) // Cannot wait for this action to finish without

this PR makes the Cart actions async, and return with them the snapshot of the cart and any error
const {cart, error} = linesAdd(lines)
if(!error && cart) {
  linesUpdate(lines)
}

Feedback
The more the look at our current implementation of cart actions the more I see slight chances of race conditions.
Can we consider dispatch will return us to idle status when the async function returns?
TODO:
I'll add more docs after I gather some feedback for this
Before submitting the PR, please make sure you do the following:

[ ] Read the Contributing Guidelines
[ ] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123)
[ ] Update docs in this repository according to your change
[ ] Run yarn changeset add if this PR cause a version bump based on Keep a Changelog and adheres to Semantic Versioning

Tested with @frandiox. We do have race conditions.


Corrected example typo on README

The example uses the export keyword to import the dependencies. This PR corrects the typo.

Coverage remained the same at 100.0% when pulling 04d9167fa498693846a105f8c3360ee05f4268c9 on guioconnor:patch-1 into 03a7c6f3d86352e9960fa4a3e0dd707e67bb8b1c on trendmicro-frontend:master.

This is not a typo, it was purposed to create a Button component rather than directly importing from @trendmicro/react-buttons. In this way, you don't need to additionally import CSS files in your app, just import the Button component in your code:
import { Button } from './components/Buttons';

Ah, I see, I misread the docs. Sorry.


Type support: generic types

Please describe what you would like to see in this project
Some tasks require a step to be able to accept any, or almost any input. We need a way to support generic types without sacrificing type checking.
Possible solutions for inputs:

A step may accept any input, disabling type checking in the process.
The user must manually declare the input and output for steps that can deal with any kind of data
The step has a two-stage process where first you must declare some parameters statically in the workflow, and the step then forms a schema
The step will gain an opportunity if it can accept the give input schema
?

Possible solutions for outputs:

A user must manually declare the output schema
The step may provide its schema based on the database schema
?

Is this resolved by #71?


[BUG] Homebridge warning

Describe the bug
Since Homebridge 1.3.x I'm getting lots of warnings like this:
[3/2/2021, 11:54:14 PM] [homebridge-dingz] This plugin generated a warning from the characteristic 'Current Ambient Light Level': characteristic was supplied illegal value: number 0 exceeded minimum of 0.0001. See https://git.io/JtMGR for more info.
To Reproduce
Install latest Homebridge 1.3.1, latest homebridge-dingz v3.1.5 and check log

Thanks for reporting. I haven't yet fully tested the plugin with<EMAIL_ADDRESS>The fix should be fairly easy in the plugin.

Still doesn't seem to be resolved in latest update. Log is getting flooded in total darkness with this:
[3/16/2021, 8:01:09 PM] [homebridge-dingz] This plugin generated a warning from the characteristic 'Current Ambient Light Level': characteristic was supplied illegal value: number 0 exceeded minimum of 0.0001. See https://git.io/JtMGR for more info.
[3/16/2021, 8:01:09 PM] [homebridge-dingz] This plugin generated a warning from the characteristic 'Current Ambient Light Level': characteristic was supplied illegal value: number 0 exceeded minimum of 0.0001. See https://git.io/JtMGR for more info.
[3/16/2021, 8:01:30 PM] [homebridge-dingz] This plugin generated a warning from the characteristic 'Current Ambient Light Level': characteristic was supplied illegal value: number 0 exceeded minimum of 0.0001. See https://git.io/JtMGR for more info.
[3/16/2021, 8:01:30 PM] [homebridge-dingz] This plugin generated a warning from the characteristic 'Current Ambient Light Level': characteristic was supplied illegal value: number 0 exceeded minimum of 0.0001. See https://git.io/JtMGR for more info.
[3/16/2021, 8:01:51 PM] [homebridge-dingz] This plugin generated a warning from the characteristic 'Current Ambient Light Level': characteristic was supplied illegal value: number 0 exceeded minimum of 0.0001. See https://git.io/JtMGR for more info.
[3/16/2021, 8:01:51 PM] [homebridge-dingz] This plugin generated a warning from the characteristic 'Current Ambient Light Level': characteristic was supplied illegal value: number 0 exceeded minimum of 0.0001. See https://git.io/JtMGR for more info.
[3/16/2021, 8:02:09 PM] [homebridge-dingz] This plugin generated a warning from the characteristic 'Current Ambient Light Level': characteristic was supplied illegal value: number 0 exceeded minimum of 0.0001. See https://git.io/JtMGR for more info.

You really have a dark-room. :-D I made a silly mistake in the limit check, will push a fix ASAP.


Module 1.1 Assignment

GitHub is an Excellent platform for code management.

Given what you have learned about Git, why would you want to use Git in your classroom?
Ans: It is an excellent platform for Version Control and collaborative work. It will help me to work in a team.


fix for crash when generating thumbnail for NULL image

  File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 149, in get_response
    response = self.process_exception_by_middleware(e, request)
  File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 147, in get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/usr/local/lib/python2.7/dist-packages/django/views/decorators/csrf.py", line 58, in wrapped_view
    return view_func(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/rest_framework/viewsets.py", line 87, in view
    return self.dispatch(request, *args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/rest_framework/views.py", line 466, in dispatch
    response = self.handle_exception(exc)
  File "/usr/local/lib/python2.7/dist-packages/rest_framework/views.py", line 463, in dispatch
    response = handler(request, *args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/rest_framework/mixins.py", line 45, in list
    return self.get_paginated_response(serializer.data)
  File "/usr/local/lib/python2.7/dist-packages/rest_framework/serializers.py", line 674, in data
    ret = super(ListSerializer, self).data
  File "/usr/local/lib/python2.7/dist-packages/rest_framework/serializers.py", line 239, in data
    self._data = self.to_representation(self.instance)
  File "/usr/local/lib/python2.7/dist-packages/rest_framework/serializers.py", line 614, in to_representation
    self.child.to_representation(item) for item in iterable
  File "/usr/local/lib/python2.7/dist-packages/rest_framework/serializers.py", line 472, in to_representation
    ret[field.field_name] = field.to_representation(attribute)
  File "/usr/local/lib/python2.7/dist-packages/sorl_thumbnail_serializer/fields.py", line 90, in to_representation
    return super(HyperlinkedSorlImageField, self).to_native(image.url)  # NOQA
AttributeError: 'super' object has no attribute 'to_native'

avoiding this for None value

Looks good. The Travis setup is incomplete, that's why the build fails.

Thank you for merging my little fix.
BTW: do you think about putting your package into pip.
Don't like requirements.txt dependencies pointed to git.

@theromis I definitely intend to do so, but unfortunately haven't got around to it yet. A few months ago this repo was a just mere python file with a code example :smile:
There are a few things I would like to see to first though, mainly complete the test suite and setup Travis CI integration. So far there are a few basic tests, but I think it needs a bit more coverage and the Travis setup needs more work. Once that's done I think we're ready to submit it to pip. Ill look into that one of the coming weekends.
I've also not been quite sure of the scope of the project (just this single serialiser field, a field collection, or try to get it included in DRF?), but as a few people seem to find it useful I think it's best just to leave it in its current form.

May be I can help with tests later. I have another issue.
Here is my structure:
'''
class ProfileSerializer(serializers.HyperlinkedModelSerializer):
portrait = HyperlinkedSorlImageField(
'88x88',
options={"crop": "center"},
source='picture',
read_only=True
)
class Meta:
    model = User
    fields = (... 'portrait', ...)

class ContactSerializer(serializers.HyperlinkedModelSerializer):
thumbnail = HyperlinkedSorlImageField(
'40x40',
options={"crop": "center"},
source='picture',
read_only=True
)
class Meta:
model = User
fields = (... 'thumbnail', ...)
class UserViewSet(viewsets.ModelViewSet):
serializer_class = ProfileSerializer
.............
.............
@list_route()
def contacts(self, request):
    serializer = ContactSerializer(contacts, many=True, context={'request': request})
    return Response(serializer.data)

def retrieve(self, request, slug=None):
    user = get_object_or_404(User, slug=slug)
    serializer = ProfileSerializer(user)
    return Response(serializer.data)

'''
As described in schema, I expect have to variants of image 40x40 and 88x88.
However for user-contacts view I'm getting same image(same link), as I'm getting for ProfileSerializer.
Do you know the reason if I made mistakes here? Or may be potential fix for that?

I think I found problem, typo retrive  versus retrieve

I need to put image width and height using this extention in rest response, do you know how I can do it?


getResultWithRange(), can you please precise?

Could you please precise in the documentation how  getResultWithRange() behaves outside the boundaries min,max?
Extrapolate or clip?

It extrapolates, since it uses the map function.

Thank you, I mean it would be useful to mention that fact in the PDF list of commands, just to be complete and to avoid questions.


Integrate with autocomplete plus

The autocomplete feature of the running kernel is quite beautiful. Now that autocomplete plus is part of Atom, it would be nice to somehow merge the autocomplete suggestions so you get the best of the static analysis and dynamic running kernel.

This is already acting as an autocomplete+ provider, and does not exclude the suggestions from other providers.

Nevermind me, I thought it was overriding the autocomplete+ look and feel with the jupyter output.


Add cloud volume snapshots to google provider

Also includes @agrare's fixes for quadicon and additional VCR recordings
/cc @blomquisg @agrare

:clap:


[Bug] Brutally Honest Review & Final Thoughts About This Project ♻

Is there an existing issue for this?

[X] Yes, I have searched the existing issues and none of them match my problem.

Product Variant
Self-Hosted
Current Behavior
I am extremely flabbergasted by the Author @AmruthPillai he has so much self promotion for this polished-from-the-outside-web-app that is what turns out to be just a time sucking monster! ISTG every where you look you will find his self-promotion.. That Mr. @AmruthPillai just reminds me every time who am I to Blame whenever I'm falling for one of the other time-wasting hoops you've knowingly or unknowingly set up or the erroring out or hitting an obstacle because of the lack of features & the non-existent flexibility just renders the web-app completely useless and a just a scheme to rob a person of the most valuable thing he/she has.. TIME 😞.

NOTE: Okay I will just say this piece then am gonna completely purge this instance from my infra, my intent is not to attack but to give eye-opening statements or face slaps if need be... to ultimately benefit the project, the community who need jobs and feed their families (Which is why I am very critical about it) I Don't believe in critique that is not followed by appreciation for what was implemented correctly, and then advise and guidance or just recommendations on what to do, think of me as your angry grandpa who ultimately just wants you to do things right.
My Motto Always: When you decide to Make Something, Do it right, Then Master it.

That chart you've put for how many users starred your repo?? IT'S A USELESS SUPERFICIAL INDICATOR! probably I did star it for when I had a hunch this would happen when I was like "Oh, Looks Promising hope he picks things up or manages to make it actually work.." and I am sure most of the sane-minded not really bound by deadlines and able users who cold thoroughly verify the web-app before diving through the rabbit hole, all would do the same.
The REAL KPI (Repo In-Depth Analysis using RepoSense. Notice how most of the the Owner's Inflated contribution is mostly Translation Files) is how many issues you have OPEN! Almost 500!!  Also there is blame on the community for not contributing but mostly on the author though for over-self promoting no one likes/wants to work with a self-proclaimed narcissist (not saying that the owner is one but I am just giving insights on how things look from different prospectives) and the collaborators WHAT ARE THEY DOING? is most of em here just to boast and self-promote? Then all this self-promotion really just becomes self-demotion & defamation!.
Expected Behavior
Look @AmruthPillai I understand, it's brutal out there and you've gotta stand-out and looks are important but I would definitely love it if you'd just market the thing as a front-end for a concept app.. maybe then you will meet like-minded niche’ers and you would find an excellent Full-Stack dev whose more focused on the back-end side of things then this would actually become great and not such a time hogging slippery slope, even the market is always looking for Masters of a Certain Niche, Being the "Best UI Button's Designer" for an example... maximise your profit and maybe even go down in history as the world’s greater Buttonist. 🏅
Steps To Reproduce

[x] 1- Tinker with BabelJS to create a damned-from-the-Start Project that should help job seekers.
[x] 2- Act like a narcissist while you are at it.
[x] 3- Limit Admins and be the only sole person responsible person for said project, not taking into account the community, the world, and that you might die at any moment.
[x] 4- Ignore most of the Issues and just ✨label✨ em and put ✨stickers✨ on em.
[x] 5- EVER MORE Vercel/NextJS TEMPLATES!!!
[ ] 6- Get the Medal of Shallot from the devil and de-brief to antichrist :)

Obviously joking....  am I?
What browsers are you seeing the problem on?
No response
What template are you using?
None
Anything else?
And For the others reading this don’t waste your time here.. over-prepping or trying to find the perfect thing, either implement it yourself or pay for other paid alternatives, or reach a comfortable point of comporimise.. somewhere else! (especially when you are on a deadline like how I was)
AND ALWAYS LOOK AT THE ISSUES.
  Please just provide good feedback instead of ranting about how you're not having the experience you want. I'm sorry but all of this just comes off as a waste of a post to the rest of us.
In the meantime kudos to @AmruthPillai, I really like this project. Been wanting a resume builder for a long time.

@YR3 Looking at how your contributions mostly dropped off somewhere in May I would say that you need to either seek professional help or reach out to some friends for support.
The feedback given here could have been said in far less words and in a much more productive way. You're doing nothing here but tearing down someone for the sake of wanting credit for their work and wanting to be the steward of their own project.
If you don't like the way things are done in the project, then go fork it yourself.

Mãe, eu tô no print!!!!!


Viewport filtering: got empty FilterModel

Hello, ceolter. Today I've met strange behaviour and would be grateful if could help me.
My gridOptions(just in case):
enableSorting: true,
enableColResize: true,
viewportRowModelPageSize: 130,
viewportRowModelBufferSize: 200,
rowGroupPanelShow: 'always',
rowModelType: 'viewport'

In template I have (filterChanged) = setFilterOption($event).
When I open filter menu, there's no options except Select All and an empty search field, but the data is showed.
When I change selection, I and try to see event and filterModel
console.log(event);
console.log(this.gridOptions.api.getFilterModel());

both event and filterModel are empty objectsObject{__proto__}.
I get an empty object no matter if Select All is ticked or not. Nothing happens when I enter something in the search field and hit Enter. Filter model seems not to refresh with this move.
However, when I do this without implementing viewport (all rows are loaded and showed at once), this.gridOptions.api.getFilterModel() gives me an object with correct information:
Object { department: Array[2] }

Also other options besides Select All appear.
The questions are: How to get filterModel in viewport? Should I set it manually every time I do setViewportRange?

I think you are using setFilter
setFilter will work with viewport, but the filtering has to be done server side.
setFilter cannot populate the list of available values as these are only available from the server, as the whole dataset is not loaded into the grid.
so you need to provide the values to the filter. this is done in the second example on this page:
https://www.ag-grid.com/javascript-grid-virtual-paging/index.php
the 'Select All' only selects all the values (checkboxs) in the filter. if no values, then it's useless.


How to expose Levelgraph API over Multilevel

Hi!
https://github.com/juliangruber/multilevel/issues/90#issuecomment-267648801

Thanks for sending me a link :). I do not have time right now to assess this issue, but I'm very happy to review/merge one of your pull requests.
As you can guess, I need help in maintaining this module.
There are also several open PRs and issues, so you might found something useful there, too.
Closing, as a "link" is not a real issue. Feel free to reopen or to send a PR.


Svelte 5 ecosystem CI is failing

Describe the bug

I don't understand why this is failing though

I should also note that TemplateNode is declared in the types twice. Once in the root of the types as a non-exported type and once exported from 'svelte/types/compiler/interfaces'
Reproduction
Upgrade enhanced-img to the latest Svelte 5 and run pnpm check
Logs
No response
System Info
`main`

Severity
blocking an upgrade
Additional Information
Should have been fixed with https://github.com/sveltejs/svelte/issues/12292, but for some reason it seems not to be working

There's no real good to make this work other than to keep exposing the old AST types through that never-meant-to-be-public interface. And I'm not sure if that is the right solution. I'd rather switch to redeclaring those types within enhanced image for the time being, and once it has a peer dependency of Svelte 5 minimum you can switch to a) the modern parse output b) use the types exported along with it.

Ah, we can switch to modern parse output. I didn't realize until just the other day that there's a flag for that and it can return two different AST.
It's probably a bit late in the game, but I would have made it version: 5 so that we don't have moreModern: true if we switch to some other implementation in the future.

The old AST will probably be gone in 6, and I sure don't hope we already have changes by then, so if we ever have another AST we can just use modern again

Oh yeah, good call. Maybe we should deprecate the non-modern one now.

I mean, it is deprecated. It's just for a seamless switch that we default to the old one

It's not showing deprecated for me. I upgraded the project to Svelte 5, but don't see any indication in the IDE.


About hyper-parameters

I found that the default hyperparameters in your repository are not consistent with what are described in the paper.
Specifically, the crop size and the number of epoch in your repository are set to 256x448 and 1000 respectively, while in the paper they are 320x256 and 200.
What are the correct hyperparameters for reproducing the results?

Sorry for my late reply. If I remember correctly, you can use 320x256 for 200 epochs. I can reconfirm with you after CVPR deadline if necessary, by retraining it. In case there is anything broken with the training scripts.


multi.exec() not sending commands

Hi
It took a while to trace this down, and we are totally baffled by this case. Our simple case:
  const multi = redisClient.multi();
  logger.info(`init multi.length [${multi.length}]`);
  redisClient.watch('aaa');
  someFunction(multi);
  logger.info(`before multi.length [${multi.length}]`);
  const results = await multi.exec();
  logger.info(`after multi.length [${multi.length}]`);
  if (results === null) {
     logger.info('Txn aborted');

Occasionally, we see in our logs there is a Txn aborted, so we decided to run monitor on the redis server, and we captured:
13:57:42.609 [0 <IP_ADDRESS>:51188] "watch" "aaa"
13:57:42.611 [0 <IP_ADDRESS>:51188] "get" "bbb"
13:57:42.612 [0 <IP_ADDRESS>:51184] "get" "ccc"
13:57:42.620 [0 <IP_ADDRESS>:51188] "multi"
13:57:42.620 [0 <IP_ADDRESS>:51188] "exec"

In our logs we can see:
init multi.length [1]
before multi.length [5]
after multi.length [6]

We can confirm the multi object in ioredis contains the 4 set and hset commands called by someFunction() above, but they do not make it to the server!
So the queue is definitely getting filled up on the app side, can someone point me to the right direction to track this down further? ioredis version is 5.2.3.

Please ignore, we were reusing the client for making transactions (sequentially), and the previous one did not discard the multi when there were no sets to exec...


Py go diff

Addressing:
https://github.com/open-traffic-generator/openapiart/issues/272
https://github.com/open-traffic-generator/openapiart/issues/274
https://github.com/open-traffic-generator/openapiart/issues/276
https://github.com/open-traffic-generator/openapiart/issues/277
https://github.com/open-traffic-generator/openapiart/issues/273

I would suggest some error message changes in order to ensure that both python and go refer to same names in the data models.

Do not expose internal names in error message:
PrefixConfig.required_object is a required field from path prefixConfig.Validate()

Recommended:
required field `self.required_object` must not be empty

Rephrasing error message for length
length of PrefixConfig.str_len shall be in the range of [3, 6] but Got 2 from path prefixConfig.Validate()

Recommended:
length of field `self.str_len` must be in range [3, 6], instead of 2

Will add more points as I find them (w.r.t. error messages)

Following snippet runs without issues, even though I did not set EB (required field) in ja.
func TestNewAndSet(t *testing.T) {
	c := openapiart.NewPrefixConfig()
	c.RequiredObject()
	c.SetA("hello")
	ja := c.J().Add().JA()
	ja.SetEA(2.4)
	c.SetE(openapiart.NewEObject().SetEA(123.456).SetEB(453.123))
	c.SetF(openapiart.NewFObject().SetFA("fa string"))
	yaml1, err := c.E().ToYaml()
	assert.Nil(t, err)
	yaml2, err := c.F().ToYaml()
	assert.Nil(t, err)
	log.Println(yaml1)
	log.Println(yaml2)
	log.Println(c.ToYaml())
}

For Clone, try converting to and from PbText instead of JSON since former would be faster (since our core data structure is in protobuf and not JSON)

shall be merged as part of https://github.com/open-traffic-generator/openapiart/pull/320


[Enhancement Feature Request] Star Tree support for sumprecesion

Right now we support big decimal via BYTES column and process data by functions like sumprecesion. It seems we cannot pre-build star tree for sumprecesion. Furthermore we need a mechanism to specify the parameter to that function. It can be a fixed value of sumprecision(my_column, 40, 12) but the 40, 12 needs to be specified

#6668


[LIVY-394][BUILD] Update branch 0.4 to version 0.4.1-incubating-SNAPSHOT

This PR updates branch-0.4 Livy version to 0.4.1-incubating-SNAPSHOT.

Codecov Report

Merging #41 into branch-0.4 will increase coverage by 0.01%.
The diff coverage is n/a.

@@               Coverage Diff               @@
##             branch-0.4     #41      +/-   ##
===============================================
+ Coverage         70.48%   70.5%   +0.01%
  Complexity          777     777
===============================================
  Files                97      97
  Lines              5370    5370
  Branches            806     806
===============================================
+ Hits               3785    3786       +1
+ Misses             1048    1044       -4
- Partials            537     540       +3

Impacted Files
Coverage Δ
Complexity Δ

...java/org/apache/livy/rsc/rpc/KryoMessageCodec.java
94.64% <0%> (-3.58%)
18% <0%> (-1%)

...cala/org/apache/livy/scalaapi/ScalaJobHandle.scala
52.94% <0%> (-2.95%)
0% <0%> (ø)

...in/java/org/apache/livy/rsc/rpc/RpcDispatcher.java
68% <0%> (+4%)
20% <0%> (+1%)
:arrow_up:

Continue to review full report at Codecov.

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


Refactor location installation path code

Now it is possible to set the installation path by setting POWERLEVEL9K_INSTALLATION_PATH. If set, this path will always be used. If it was not set manually, we try to determine the path automatically.
This fixes #264
@protist could you double-check? Especially with your ZSH 5.0.7. That would be great. Thanks.

Patching works perfectly on my zsh 5.0.7. Thank you for the quick fix.

Lots of changes here, not all of which I can easily test. The code looks good, though! Merging into next for further dev testing.
Thanks so much, @dritter! Looks like it fixed @protist's issue, as well, which is awesome. Nice work.


fetch schema only once per batch operation

Scope & Purpose
Fetch collection's schema only once per batch operation, not once per document.
Because the schema is an atomic shared_ptr, fetching it only once per batch can reduce contention when dealing with large concurrent batch operations.

[ ] :hankey: Bugfix
[ ] :pizza: New feature
[x] :fire: Performance improvement
[ ] :hammer: Refactoring/simplification

Checklist

[ ] Tests

[ ] Regression tests
[ ] C++ Unit tests
[ ] integration tests
[ ] resilience tests

[ ] :book: CHANGELOG entry made
[ ] :books: documentation written (release notes, API changes, ...)
[ ] Backports

[ ] Backport for 3.9: (Please link PR)
[ ] Backport for 3.8: (Please link PR)
[ ] Backport for 3.7: (Please link PR)

Related Information

[ ] Docs PR:
[ ] Enterprise PR:
[ ] GitHub issue / Jira ticket:
[ ] Design document:

PR run: https://jenkins.arangodb.biz/view/PR/job/arangodb-matrix-pr/21820/


Error when building with Material 3 Theme

Im using my own custom Material 3 Theme which is giving this error when i try to run my app:
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.mcnut.banking/com.mcnut.banking.fragments.LoginActivity}: java.lang.IllegalStateException: You need to use a Theme.AppCompat theme (or descendant) with this activity.
Manifest File:
<EMAIL_ADDRESS>Activity Class:
class LoginActivity : AppCompatActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)

        WindowCompat.setDecorFitsSystemWindows(window, false)
        setContent {...

Themes.xml:
<style name="Theme.Budgeting" parent="Theme.Material3.Dark.NoActionBar">...
Is there any way i can avoid this error coming up or is it just not possible to use the charts in a theme like this.
Thanks

Facing same issue. Were you able to resolve it ? @RedSunMaster


configuration via curl not working as expected

Environment

Application Services Version: 3.51.0
BIG-IP Version: <IP_ADDRESS>

Summary
Sending declaration through Postman is working, but throws an error using cURL.
Steps To Reproduce
Steps to reproduce the behavior:
Using Postman this is working on a blank configuration:

POST https://{{cbip}}/mgmt/shared/appsvcs/declare
{
"class": "ADC",
"schemaVersion": "3.0.0",
"id": "generated-for-testing",
"test": {
"class": "Tenant",
"application-a": {
"class": "Application",
"my-virtual-a": {
"class": "Service_HTTP",
"virtualAddresses": [
"<IP_ADDRESS>"
],
"virtualPort": 80,
"pool": "my-pool-a"
},
"my-pool-a": {
"class": "Pool",
"members": [
{
"servicePort": 80,
"serverAddresses": [
"<IP_ADDRESS>",
"<IP_ADDRESS>"
]
}
]
}
}
}
}

When putting the body into a file and issuing this cURL, its working fine as well:
curl -sku admin:password -H “Content-Type: application/json” -X POST -d @initapp https://<IP_ADDRESS>/mgmt/shared/appsvcs/declare
When adding a second app to the same tenant using Postman I end up with two apps in the "test" tenant - as expected.
POST https://{{cbip}}/mgmt/shared/appsvcs/declare/test/applications/
{
"schemaVersion": "3.0.0",
"id": "generated-for-testing",
"application-b": {
"class": "Application",
"my-virtual-b": {
"class": "Service_HTTP",
"virtualAddresses": [
"<IP_ADDRESS>"
],
"virtualPort": 80,
"pool": "my-pool-b"
},
"my-pool-b": {
"class": "Pool",
"members": [
{
"servicePort": 80,
"serverAddresses": [
"<IP_ADDRESS>",
"<IP_ADDRESS>"
]
}
]
}
}
}
But if I'm using a cURL command to add the second app I'm having issues. Again I'm adding the body in a second file (application) and use:
curl -sku admin:password -H “Content-Type: application/json” -X POST -d @application https://<IP_ADDRESS>/mgmt/shared/appsvcs/declare/test/applications
But instead of adding a second VIP I'm getting this error:
{"code":422,"message":"Invalid data property: Per-app declaration must contain at least one application","declaration":{}}
I'm not understanding why the first call is working using cURL but the second doesn't.
Thx,
Marcus

Please submit an SR with F5 support and provide the number

Case # is 00704327.

Hi Marcus,
I believe you're using wrong double quote characters in:
-H “Content-Type: application/json”
Can you try with this:
-H "Content-Type: application/json"

Great catch Adam. That was the problem.


Find leftmost non repeating character in a string

🚀 Feature
Given a string, find the index of the leftmost non repeating character in it.
Example: s = "hello", output should be: 0 (index of h)
s = "aabcdb", output should be: 3 (index of c)
s = "xxyyzz", output should be -1 (since there is no non repeating character in this string)
Have you read the Contributing Guidelines on Pull Requests?
Yes
Motivation
Helps in understanding strings.
Pitch
This will increase the understanding of string manipulation.

I would like to work on this issue in C++

I would like to work on this issue in python

I would like to take this in Java for CH20

I would like to work on this issue in C

In which folder do I need to add the above solution?

We are logging the scores for the Contributor's Hack 2020. If you have one or more than one PR merged during the program, make sure to fill this form


Large Graph Processing

Currently, we do not have a way to limit graph sizes. For example, if we have a large graph stored in ArangoDB that may take up 1TB if loaded into memory. It would be nice to explore limiting the extracted graph from ArangoDB via hard limits or sampling.
Additionally, this relates to optimizing vertex/edge dictionaries currently used to create the NetworkX graph.

Some things to consider:

Parallel Batch Processing via multithreading in python
Providing arangoexport and arangoimport as an option for ArangoDB to NetworkX & vice-versa

(Low priority)

This really should be expanded so that there is a bridge to Graphistry - it's a fairly slick GPU enabled web based network visualization tool - similar in spirit to Gephi, but much more capable in terms of volume. They have a free plan that you can use for an hour, then you have to reset the API key. It's not much of a burden, an hour is a LONG time to be messing with any given graph visualization.


Bundle size

Checklist:

[x] Code contains relevant tests for the problem you are solving
[x] Ensure all new and existing tests pass
[x] Update any relevant READMEs and docs
[x] Submit to the develop branch instead of master

Description:

Removes the ipfs-api dependency
Reduces origin.js bundle size by half

@nick Should probably not have the solidity stuff in this PR, right?