Build failed

There are some errors when building this project. I noticed this merge broke the building. For example, that merge deleted MainTabBarViewModel, but in AppDelegate.swift, it was still required. And the similar things happened to the initializer of EpisodesViewModel.

I'm glad that you're interested in my project! I have started refactoring the architecture but it still work in progress.
I don't have much time at the moment to finish it, but apparently I will!
What can we do right now?

You can fix those problems and I'll review your pull request. You can make some improvements if you want to as well ☺
You can enable notifications and wait for the time when I'll finish refactoring.

Please, let me know what you're about to do


Import/Use Civ3 Data about Whether Terrain Types Allow Cities

Currently, cities can be founded on any terrain that isn't Mountains, and this is hard-coded.
In reality, this data is stored in a BIQ file and is configurable; I've personally modified it in many of my scenarios.  We should import this into C7 and make it something that the AI considers when building cities - as well as something that controls whether the "Build City" option is enabled for the human player, or not.

Currently, this is evaluated in the AssignTileScores method of SettlerLocationAI.cs, in C7Engine.  Right now it just excludes any tile whose key is "mountains".


Fixes #6723 GET API to get a list of functions that can be used for authoring Policy Rule conditions

Describe your changes :

See #6723 for details

Type of change :

[x] New feature

Checklist:

[x] I have read the CONTRIBUTING document.
[x] I have commented on my code, particularly in hard-to-understand areas.
[x] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

Cypress test failures are unrelated to this change where only new APIs are introduced.


RFE: is it possible to start making github releases?🤔

On create github release entry is created email notification to those whom have set in your repo the web UI Watch->Releases.
gh release can contain additional comments (li changelog) or additional assets like release tar balls (by default it contains only assets from git tag) however all those part are not obligatory.
In simplest variant gh release can be empty because subiekt of the sent email contains git tag name.
I'm asking because my automation process uses those email notifications by trying to make preliminary automated upgrades of building packages, which allows saving some time on maintaining packaging procedures.
Probably other people may be interested to be instantly informed about release new version as well.
Documentation and examples of generate gh releases:
https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository
https://cli.github.com/manual/gh_release_upload/
https://github.com/marketplace/actions/github-release
https://pgjones.dev/blog/trusted-plublishing-2023/
https://github.com/jbms/sphinx-immaterial/issues/281#issuecomment-1700933026
tox target to publish on pypi and make gh release https://github.com/jaraco/skeleton/blob/928e9a86d61d3a660948bcba7689f90216cc8243/tox.ini#L42-L58

I have automation for my system calls stuff on todolist still.

This repo will be archived. All system calls things will be in hrw/syscalls-table repository.

Take a look at https://github.com/hrw/syscalls-table/tree/merge-with-python-one branch.

So this repo will be no longer used? 🤔

Exactly - need to write there some doc about 6.6.1 release, move tag and archive this one.


Do not save the video in the gallery

Hello, any idea how to not save the video in the phone gallery?
my code :
var file;
final tmpDir = await getTemporaryDirectory();

 final Map<String, dynamic> response = await LightCompressor.compressVideo(
          path: _attachement.path,
          destinationPath: '${tmpDir.path}/${DateTime.now().millisecondsSinceEpoch}.mp4',
          videoQuality: VideoQuality.high,
          isMinBitRateEnabled: false,
          keepOriginalResolution: false,
);

if (response['onSuccess'] != null) {
          file = File(response['onSuccess']);
} else if (response['onFailure'] != null) {

 } else if (response['onCancelled'] != null) {

}

if (file.existsSync()) {
          file.deleteSync();
}

thx for your time 😇

The problem is in the file "SwiftLightCompressorPlugin.swift"
Just remove:
DispatchQueue.main.async {
   PHPhotoLibrary.shared().performChanges({
     PHAssetChangeRequest.creationRequestForAssetFromVideo(atFileURL: path)
  })
 }

It works like a charm. I hope it will be a fixed for futures versions.
Merci Nicolas ca m'a fait gagner beaucoup de temps.

Thank you for opening the issue and the suggestion to fix it, I added a bool iosSaveToGallery to avoid saving, you can just pass it with false.

Thank you !


Support non-multiple and non-named values in Yields and Receives

This PR fixes https://github.com/mkdocstrings/griffe/issues/263 by applying the same logic from the Returns section parser to the Yields and Receives parser.  The Yields section parser is configured with the same two configuration variables returns_multiple_items and returns_named_value, whereas the Receives section parser is configured via the new receives_multiple_items and receives_named_value configuration variables. Furthermore, the parsing of multiple or single docstring block contents, of named or unnamed parameters, and the unpacking of generator and/or tuple return annotations has been refactored into separate functions.

Contents:

8a78e68e7702d5b874daa21aeca58943eb9cf7d6 duplicates the non-multiple return and the named value parsing support for the Yields and Receives section parsers, essentially via copy-and-paste. Includes suitable tests, based on the Returns section tests.
756118fc0da4866c80fde0b456cbb497124c0a18 implements the aforementioned refactored functions. This commit is functionally optional, but hopefully useful with respect to future ease of maintenance.
e01447a5980ca2c6e94c93f8df7618deb59d627a fixes linting errors.
8e7cb30fac0df5e619da94b102d5c88de0b36a18 adds documentation for the above features.

Concerning code style, I come from a black/ruff environment, and found no settings in your code repository. So my formatting and linting may be off.

GitHub doesn't seem to recognize a PR that has been reset to an earlier, already-reviewed state as already reviewed…
Also, there's an apparently unrelated, failing CI test on Py3.13/Ubuntu-lowest-direct that's been haunting this PR since its inception.

Don't mind the 3.13-lowest failure, it's unrelated indeed and it's allowed to fail.

Concerning code style, I come from a black/ruff environment, and found no settings in your code repository. So my formatting and linting may be off.

Just saw this, sorry. There's a make vscode command you can use to configure VSCode for the project :slightly_smiling_face: It overrides local files.

Thanks again!

I refactored the logic again in https://github.com/mkdocstrings/griffe/commit/a80bd3c0cc14e5f6efc30fb804b8c7fccb319276, I think it's even more readable now.

That's fine. I wasn't sure if I should touch the "where is the annotation looked up in?" part, so my version doesn't quite reap the same readability benefits as yours.


openTSDB service shutdown

Fixes issue https://github.com/influxdb/influxdb/issues/4437
This change ensures:
a) Ensure Open and Close do not run concurrently.
b) Check that the batcher is non-nil before closing it.

@corylanou @jwilder @gunnaraasen

:+1:


Stop Loading When data are ready not before

Is your feature request related to a problem? Please describe.
this is not a feature at all, i have to stop loading when the data is ready not before.
My loading stops but the data is not ready and I have a broken view that is still popping up data one after another
Please help!

Nuxt 2 offers asyncData, which blocks page navigation whilst data is fetched but which only works in page components. Or fetch, which is non-blocking but works in any component.
You can read more at https://nuxtjs.org/docs/features/data-fetching#data-fetching.


Input / State wildcards not in Outputs

When I use dash_extensions.enrich, the following error appears
In the callback for output(s):   82572af3-409b-4eed-8fa6-058307d2c581.children State 0 ({"index":MATCH,"type":"download-btn"}.id) has MATCH or ALLSMALLER on key(s) index where Output 0 (82572af3-409b-4eed-8fa6-058307d2c581.children) does not have a MATCH wildcard. Inputs and State do not need every MATCH from the Output(s), but they cannot have extras beyond the Output(s).

Are you running the latest version (0.0.28)? Could you post a small, self-contained example illustrating the issue?

if i can use Trigger,ServersideOutput,but Output,Input original？
like this
import dash from dash_extensions.enrich import  Trigger, ServersideOutput from dash.dependencies import Input, Output,State,MATCH, ALL app = dash.Dash(__name__,external_stylesheets=[dbc.themes.FLATLY],prevent_initial_callbacks=True)


memory leak, the caller is the owner

Should find a way to make it more obvious (in vtkItkConversion)  to the developer  with a specific pattern in the function name or to use smart pointer (better sol).
I do not have 4D data. if someone can send me a small data I will be happy to test it.
I have check that in vtkImageView a deep copy is done the matrix and here it becomes a smart pointer.

An easy fix (without needing to change the data type) would be have the caller provide the output table as an argument.


1646770778<PHONE_NUMBER> main isort config update make

@bitkarrot - this is the commit/branch that I would like to build on top of... but I need to know if the underscore naming is good/bad standard/non-standard - and what the reason for the syntax error I am getting - I believe it is flake8 that is warning me of the error. (vim plugin flake8) - some where in the docs - the underscore _0x20bf is ok - I am not sure why it wasn't showing up before? anyway I will ping you on TG. :)


upgrade tls module for 0.12

Module has been upgraded for 0.12 compatibility - please merge into master.

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement
Learn more about why HashiCorp requires a CLA and what the CLA includes
Have you signed the CLA already but the status is still pending? Recheck it.

Hi @tlinkin, thanks for the PR! We already have Terraform 0.12 support mostly complete (hopefully merging today) over at #154
I'm going to close your PR in favor of #154 but if you see anything missing once that's merge, please feel free to reopen!


bylawman, dirtboard

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.4
logical conflict every: 100
sleep for: 300s
[pullrequest]
requests per hour: 30
deps=[b,d]

/trunk merge


Jackson + Swagger + jackson2HttpMessageConverter causes invalid json ouput of api-doc when setting WRAP_ROOT_VALUE to true

When setting Jackson serialization feature WRAP_ROOT_VALUE to true it spits out incorrect json.
private MappingJackson2HttpMessageConverter jackson2HttpMessageConverter() {
      ObjectMapper objectMapper = new ObjectMapper();
      // Setting true spits out wrong Swagger api-docs json
      objectMapper.configure(SerializationFeature.WRAP_ROOT_VALUE, true);
      objectMapper.registerModule(new Jdk7Module());

      MappingJackson2HttpMessageConverter converter = new   MappingJackson2HttpMessageConverter();
      converter.setObjectMapper(objectMapper);

      return converter;
}

this incorrect json ouput:
{
"ResourceListing"{
    "apiVersion": "1.0",
    "apis": [
        {
            "description": "circuits",
            "path": "/default/circuits",
            "position": 0
        },
        {
            "description": "constructors",
            "path": "/default/constructors",
            "position": 1
        }
    ],
    "authorizations": {

    },
    "info": {
        "contact": "Contact Email",
        "description": "Api Description",
        "license": "Licence Type",
        "licenseUrl": "License URL",
        "termsOfServiceUrl": "Api terms of service",
        "title": "default Title"
    },
    "swaggerVersion": "1.2"
}
}

ResourceListing is missing a colon.
I'm using Spring MVC Rest 4 + Jackson 2.4.4 + swagger-springmvc 0.9.5

@t0tec not really sure if this is still relevant. I believe its fixed in 1.0.1

Yes, only thing is when setting it to true swagger can't fetch the resource list. Probably because something goes wrong in the ui. Still I just changed WRAP_ROOT_VALUE to false. But it can cause problems with other people if they want to configure Jackson themselves.

Problem indeed still exists when using Springfox 2.0.3.
Reproduced in 'hello world' project https://bitbucket.org/squins/springmvc-swagger-issues
To reproduce, clone this repo, uncomment relevant lines HelloWorldRestConfiguration method jackson2Converter, run the app and go to http://localhost:8099/rest/swagger-ui.html

@keesvandieren I verified the problem! Not sure of a good way to fix it, based on the way spring message converters work. I've tried a bunch of things and they don't seem to work. Do you have a workaround or perhaps a solution that we could use. PR?

Verified the issue still exists in Springfox 2.4.0.
After trying numerous different approaches a colleague and myself came across the following online resource by Marty Pitt:
https://martypitt.wordpress.com/2012/11/05/custom-json-views-with-spring-mvc-and-jackson/
The resulting class allows the JSON root wrapping to be disabled only for Swagger. See attachment
ViewAwareJsonMessageConverter.txt

Hi @ArnoldKesselaar
Looking at the attached workaround, we will be having 2 ObjectMappers,

One ObjectMapper for Swagger with WRAP_ROOT_VALUE=false
One ObjectMapper for others with WRAP_ROOT_VALUE=true

IMHO, this will make the swagger-ui.html work which is great ...
But the JSON request/response shown in the Swagger-UI will be different from the one from the real API i.e the documents shown on the swagger-ui will have no root element....
Can you confirm @ArnoldKesselaar ?
Thanks.

I guess looks like this problem still exists.  Can some one help how to modify this class to just to ignore wrap root value just only for swagger?
`@Component
@Primary
public class CustomObjectMapper extends ObjectMapper
{
private static final long serialVersionUID = -6511257240128676961L;
public CustomObjectMapper() {
    configure(DeserializationFeature.UNWRAP_ROOT_VALUE, true);
    configure(SerializationFeature.WRAP_ROOT_VALUE, true);
}

public String writeValueAsString(final Object obj, String rootName) {
    try {
      final ObjectWriter writer = writer().withRootName(rootName);
      return writer.writeValueAsString(obj);
    }
    catch (Exception e) {
      throw new RuntimeException(e);
    }
}

}`

@Chowdaryonpc you can create mixins for the swagger classes

Is this issue resolved? I'm currently working with springfox v2.7.0 but I'm still facing the same issue. So can you please tell me what is the proper workaround to achieve root level wrapping?

Hey,
if somebody is also struggling with simmilar issue. I can recommend my library for that. You can enable response wrapping by @EnableResponseWrapping annotation and it works with SpringFox.
@hxp1178  In my case suggested solution with TypeResolver also didn't work. 😭
https://github.com/jpomykala/spring-higher-order-components

Is this issue resolve? Does anyone have any solution fix for this?

Hi Team, facing similar Issue , any workarounds?

Hi,
Still KO with SpringBoot 3.0.x and springdoc-openapi-starter-webmvc-ui  2.1.0 with spring.jackson.serialization.wrap-root-value=true, any workarounds ?
Thanks !


Make DevelopmentTools class behavior consistent with compiler wrapper shims and make shims detect versioned compiler formulae

Provide a detailed description of the proposed feature
Following up on discussion in #13768:
DevelopmentTools.clang_build_version

always return the XCode llvm version, while compiler shims such as /usr/local/Homebrew/Library/Homebrew/shims/mac/super/llvm_clang++ will actually use the tools from the llvm formula if it is installed, so it should return that version of llvm.
Furthermore, the shims look for the installed llvm formula via the /usr/local/opt/llvm symlink, and this does not detect versioned llvm and gcc formulae such as llvm@13. This problem could potentially be solved by #13779 if implemented.
What is the motivation for the feature?
Improving how the brew build toolchain works.
How will the feature be relevant to at least 90% of Homebrew users?
It would not be, it would be relevant mostly to users on older OSes and others who do source builds instead of using bottles.
What alternatives to the feature have been considered?
Dunno.

In that case, maybe there should be another method in DevelopmentTools for a formula to find out what version of clang will actually be used for the build, which is the case with snappy.rb, the one I was having problems with. In that particular case, that is the information the formula author was trying to find using that method.

Yes, but /usr/bin/clang is not actually want is used to do the build if llvm is installed, in that case /usr/local/opt/llvm/bin/clang is used, and is a newer version. This is the problem.

I think you misunderstand.
snappy.rb checks the version of /usr/bin/clang to see if it is too old. If it is too old, then it:

adds a dependency on llvm; and,
switches to using llvm instead of /usr/bin/clang.

Note, in particular, that (2) above is done only if /usr/bin/clang is too old. If it is not, then /usr/bin/clang is used, regardless of whether llvm is installed.
A different method that does something else would not work for the above.

How does that happen, is that the fails_with :clang block?

It happens in the two lines that call DevelopmentTools.clang_build_version.
The fails_with :clang code probably doesn't actually have any real function in that formula, but it does help make things more explicit. (i.e. at the moment it's just there for documentation)

In which case is the /usr/local/Homebrew/Library/Homebrew/shims/mac/super/clang shim NOT used when building a formula?

That compiler shim is used, but that eventually just calls /usr/bin/clang.

Ok I see now, depends_on "llvm" => :build will invoke with shim llvm_clang which will use /usr/local/opt/llvm/bin/clang, otherwise it just calls clang++ from the PATH.
And that's another problem here, brew sets its own PATH and I can't just put another version of clang in it before starting a build.
So what I suggested is wrong, but there is still the problem that the actual check here should be for clang > 1100 || llvm_clang > 1100.

Also I was wondering, if llvm is installed, is there any reason to not always use it as opposed to the system clang? Would there be any possible incompatibilities?

And that's another problem here, brew sets its own PATH and I can't just put another version of clang in it before starting a build.

This is intentional.

Would there be any possible incompatibilities?

Yes.
Passing on this for now. The main ask here is "provide better support for using a non-system LLVM" for which we'll review PRs but aren't soliciting for work as it's only really relevant on unsupported macOS versions, sorry.

No, depends_on "llvm" => :build does not result in invoking the llvm_clang shim. Adding a dependency on llvm (:build or otherwise) by itself will still have brew use /usr/bin/clang.

So what in that formula actually causes the shim to be called with llvm_clang rather than clang, which is definitely what is happening here.

The main ask here is "provide better support for using a non-system LLVM" for which we'll review PRs but aren't soliciting for work as it's only really relevant on unsupported macOS versions, sorry.

Yes I intend to do the work myself, I am just trying to figure out what work to do by discussing in issues first as that's generally the right way to go about such things.

https://github.com/Homebrew/homebrew-core/blob/dd1adf690c23bdb4d55387e6786575241eedf7d5/Formula/snappy.rb#L46

I see thank you, I will try to come up with a better proposal for this.

How about adding:
DevelopmentTools.llvm_clang_build_version

, which would get the llvm version of /usr/local/opt/llvm and fall-back to:
DevelopmentTools.clang_build_version

. This would seem to be more in-line with your conventions for this.

The version of /usr/local/opt/llvm is supposed to be given by Formula["llvm"].version (unless the user has tampered with /usr/local/opt/llvm, but that's not a use-case we intend to support).
We don't need to check Formula["llvm"].version, so I don't see how adding DevelopmentTools.llvm_clang_build_version would be useful anywhere.

As I said, the problem I want to solve is to make it simpler to check, for example, that system_llvm > 1100 || brew_llvm > 1100 and take the appropriate action, while still keeping formula code simple. If you don't believe this is a worthwhile goal I will drop this discussion.

But we already know the version of Homebrew llvm, and we don't need another method in DevelopmentTools to query it.
I also don't see what adding a check for the version of Homebrew llvm will add to the formula, unless we are considering the case where the user might have a tampered Homebrew llvm. As I've mentioned previously, that's not a use-case we wish to support.

It doesn't necessarily need to be tampered, it may just be pinned. It should also support versioned llvm formulae as I proposed in #13779 (if and in whatever way that gets implemented.)

Avoiding build failures that are a consequence of brew pin is not something we wish to support either.
That said: I'm not even sure brew will let you install/upgrade something when a pinned dependency is outdated.

It should also support versioned llvm formulae as I proposed in #13779 (if and in whatever way that gets implemented.)

Adding support for alternative compilers other than the one we use in CI isn't something we wish to add to formulae. See also the output of passing --cc to brew install.
To be clear: I'm not necessarily opposed to brew falling back to a versioned LLVM formula if the unversioned one is not available, but I don't think we need to, or should, add checks for this in formulae. That just creates more code paths that never get tested in CI.

Also, note that Formula["llvm"].any_version_installed works even if llvm is pinned. We haven't added any checks for this because, as mentioned, it doesn't really make sense for the formula to do this.

To be clear: I'm not necessarily opposed to brew falling back to a versioned LLVM formula if the unversioned one is not available, but I don't think we need to, or should, add checks for this in formulae. That just creates more code paths that never get tested in CI.

How would you propose implementing this then?
There are two parts here that would need to be addressed,

The dependency:

depends_on "llvm" => :build

, would have to allow being satisfied by a versioned llvm as opposed to only the new one. This would still not match the intended llvm version, but the user could deal with that.

The compiler shims would need to be able to find a versioned llvm for llvm_clang, possibly by implementing #13779 or manually.

I don't necessarily have an implementation in mind. What I do know if that what's been suggested so far is not suitable.

What's wrong with my last one? Either the formula code has to change a bit or these two things have to change, otherwise it's not possible to do is it?

What about something like:
depends_on "clang>=11" => :build

, this would do the necessary checks, checking both the macOS llvm version and any installed versions of llvm and automatically add ENV.llvm_clang when needed.
This would make the formula code even simpler, instead of more complex.
If neither this nor my last proposal above would not work, I'll just drop this for now as I don't see any way forward, unless you can suggest one.
I am following up on the build failures in llvm-project by the way.

What's wrong with my last one? Either the formula code has to change a bit or these two things have to change, otherwise it's not possible to do is it?

The issue is that the current calls to DevelopmentTools.clang_build_version are hacks/workarounds for limitations of fails_with. I don't want to pile on further hacks on top of the existing ones -- that just makes the problem worse.
The correct implementation would be for fails_with to handle compiler selection properly/better, so that we can get rid of all of the calls to DevelopmentTools.clang_build_version in the formula and just keep fails_with.

I am following up on the build failures in llvm-project by the way.

Do you have a link to an upstream issue?

Would you support the fails_with method automatically handling the llvm dependency and environment setting for a formula? I could start working on this.

I'm not sure, because we would need to make sure this doesn't break the way existing formulae use fails_with. For example, openblas and fftw use fails_with :clang because they expect to compile with gcc. We don't want to use the llvm formula to compile those.
On the other hand, the formulae that do fails_with :clang do typically try to build with llvm, since this usually avoids an extra runtime dependency (whereas compiling with gcc will introduce a runtime dependency on gcc).
If there is a sensible way to automatically handle the llvm dependency while also accounting for the cases above, then that would be useful.

Any changes to fails_with also needs to make sure this code doesn't break:
      def install_gcc_if_needed(formula, deps)
        installed_gcc = false
        begin
          deps.each { |dep| CompilerSelector.select_for(dep.to_formula) }
          CompilerSelector.select_for(formula)
        rescue CompilerSelectionError => e
          unless installed_gcc
            test "brew", "install", "gcc",
                 env: { "HOMEBREW_DEVELOPER" => nil }
            installed_gcc = true
            DevelopmentTools.clear_version_cache
            retry
          end
          skipped formula.name, e.message
        end
      end

Thank you, I'll do some more research.

One way of handling this might be to check the dependencies for gcc first and use that if declared.
Otherwise it should fall back to llvm. This may need to wait for LLVM 15 (Homebrew/homebrew-core#106925) so we don't get undesirable linkage with LLVM's libc++.
If llvm is not available, it can fall back to a versioned llvm. We'll probably want a way to avoid this fallback and fail if we're in CI.
This is probably going to be a complicated project. CC @Bo98 for thoughts here.


pull request for e2e test at 01/06/2017 17:45:10

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


Train 142

#1240
#1275
#1342
#1361
#1362
#1373
#1374

@mesosphere-mergebot bump-ee

@lingmann , @spahl , @alberts , @adam-mesos  - this is ready for review / ready to ship.

@orsenthil This all goes into master (1.10+), but should any of it be backported to 1.9?
cc: @spahl

@adam-mesos - that will not be my call. That will be for @spahl to take.

@orsenthil please add high level description for each PR in the issue summary (makes it easier for a high level review).
@spahl some of these are likely needed for 1.9. for example #1373 which enables upgrade tests to succeed. Have any 1.10 features landed yet? If not I propose we cut the next 1.9 point release off of master.

@lingmann  - done for both open and ee.

@orsenthil @vespian @mellenburg @karlkfi @amitaekbote can all of you please review your PR's in this train for work that should be backported to 1.9? If a PR should be backported, please add a comment or annotate in the train summary. Thanks!

#1373 - Check CI flags in upgrade tests, should get back ported

@lingmann EE Train has changes that would make my life much easier if they got into 1.9 EE You can find them here: https://github.com/mesosphere/dcos-enterprise/pull/715 These changes are already in Open.


Support for Swift Package Manager

SwiftLint found issues
Warnings

File
Line
Reason

Package.swift
8
Function parameters should be aligned vertically if they're in multiple lines in a method call. (vertical_parameter_alignment_on_call)

Package.swift
10
Collection literals should not have trailing commas. (trailing_comma)

Package.swift
16
Collection literals should not have trailing commas. (trailing_comma)

Package.swift
29
Collection literals should not have trailing commas. (trailing_comma)

  Generated by :no_entry_sign: Danger

👍 good stuff, thanks for the PR


Use DB transaction for post cleanup

Description
As you said in the previous issue, as a next step I want to use db transaction for the cleanup of post.
Screenshots
No response
Additional information
No response
Record

[X] I agree to follow this project's Code of Conduct
[X] I have checked the existing issues
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

Description
As you said in the previous issue, as a next step I want to use db transaction for the cleanup of post.
Screenshots
No response
Additional information
No response
Record

[x]  I agree to follow this project's Code of Conduct
[x]  I have checked the existing issues
[x]  I'm a GSSoC'23 contributor
[x]  I want to work on this issue

Sure, go ahead!


[BUG] C# Region Text color super bright green and not configurable

Which Glance version and IDEA version?
Glance 1.9.2
JetBrains Rider 2024.2.7

This is the About page with some work stuff deleted:
Build #RD-242.23726.100, built on October 22, 2024
Runtime version: 21.0.4+13-b509.26 aarch64 (JCEF 122.1.9)
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Toolkit: sun.lwawt.macosx.LWCToolkit
macOS 15.1
.NET Core v8.0.4 ARM64 (Server GC)
JetBrains IDE Services version: 2<IP_ADDRESS>91-ij242
GC: G1 Young Generation, G1 Concurrent GC, G1 Old Generation
Memory: 4096M
Cores: 10
Metal Rendering is ON
Registry:
ide.experimental.ui=true
i18n.locale=
Non-Bundled Plugins:
com.nasller.CodeGlancePro (1.9.2)

Can you show the complete config page picture and minimap picture?

I thought changing the "Viewport Border Color" would affect this, but it doesn't seem to be the case.

What is the file type used and provide text or an example of the issue that occurred?

Any .cs file

What steps will reproduce the issue?

Make a #region Foobar for example, in any C# file
I use the Rider Dark color scheme. I've had to disable CodeGlance for now because my team uses #region a lot and the color of region names are so bright in the editor that it makes my eyes hurt. I don't mind the region name colors in the minimap, but in the editor, the contrast is too intense and it's too bright.
This is what region names look like without the bright green, it is a dimmer light gray

CodeGlancePro-1.9.3-SNAPSHOT-2024-11-04T13-26-signed.zip
try this, now you can modify the mark line color by errorstrip color in color settings page


Understand if EIGEN_DEFAULT_TO_ROW_MAJOR used in manifpy compilation is problematic in blf Python bindings

Not something urgent, but apparently manifpy is being compiled with the EIGEN_DEFAULT_TO_ROW_MAJOR Eigen option (see https://github.com/artivis/manif/blob/0.0.4/python/CMakeLists.txt).
As you can see in https://gitlab.com/libeigen/eigen/-/issues/422, this option actually breaks ABI and API, so it can create problems if Eigen::MatrixXd or similar classes created in manifpy are passed to "normal" Eigen functions compiled with the standard Eigen options. In particular some matrices may be silently transposed. We should understand if this can create problems in the future (at the moment, I don't understand enough of the manifpy/blf python machinery to given an appropriate opinion on this) and if this can create problems, and in that case understand how to deal with them.

By the way, Eigen docs are quite clear that their recommendation is never to use EIGEN_DEFAULT_TO_ROW_MAJOR option except for testing Eigen itself, see from https://eigen.tuxfamily.org/dox/TopicPreprocessorDirectives.html :

These macros are mainly meant for people developing Eigen and for testing purposes. Even though, they might be useful for power users and the curious for debugging and testing purpose, they should not be used by real-word code.

On the other hand, manifpy links pybind11 docs, that itself do not refer to EIGEN_DEFAULT_TO_ROW_MAJOR, explicitly, see https://pybind11.readthedocs.io/en/stable/advanced/cast/eigen.html#storage-orders .

FYI @artivis: we still did not looked into this in depth and we still do not understand/know if this can be a source of problem, but nevertheless you may still like to be aware of this.

Thanks for the heads up.
I wasn't aware of Eigen's strong recommendation against this feature. I initially developed the binding without EIGEN_DEFAULT_TO_ROW_MAJOR which led to an ugly and, most importantly, error-prone API (see e.g. here). I thus imagine that reverting this would be fairly straightforward if necessary.
If I'm not mistaken the ordering only concern matrices (e.g. here Jacobians) and thus group/tangent types are not impacted - they use vectors underneath. Furthermore, the option is only enabled for the Python lib; since there are no pointer manipulation/mapping across types like on the C++ side, I suppose this won't be trouble.
I haven't had any related issue so far but you guys definitely have a more extensive use of manifpy than I do, so please do feel free to open a ticket if you spot anything wobbly.


⚠ Bofrost.at has degraded performance

In f89542b, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1289 ms

Resolved: Bofrost.at performance has improved in 9ef8e26 after 8 minutes.


Remove -Xlint:unchecked, suppress all existing violations

Fixes #1323  ☕
This will prevent further violations from being added without explicit suppressions.
A future step would be to review all existing violations and fix instead of suppressing them.

@sinelaw thanks for the contribution, it makes sense, please see a single nit comment

Added another commit - PTAL


design website

the website needs some styles…
git clone git@github.com:medialize/ally.js.git
cd ally.js
git checkout master
npm install
npm run build-website

Will clone the repository, install the tools and generate the website to ally.js/web.
Assets (like stylesheets, images, …) are maintained in ally.js/metalsmith/assets.

I was hoping for a real™ designer to spend some time on the website and asked @dirkweber to help me out. Unfortunately his spare time is limited and it looks like he might make it around Christmas 2015. I didn't want to wait another month so I "designed a website" (excuse the blasphemy) that will serve until then. I'm therefore taking this off the 1.0.0 milestone.
Holler if you're a designer and want to help out ;)

maybe ally.js should have a logo? maybe something along the lines of http://www.un.org/webaccessibility/logo.shtml for "topic recognition"?

@rodneyrehm Are you still looking for help with the website design?

well, @dirkweber showed me some ideas a couple weeks ago, but we haven't had the talk about them since.
If you're interested in helping out, maybe a draft of what an API page could look like is a good start?

pinging @dirkweber to notify that the changes I wanted to make to how the website is built are all in now :)


fix 'rasa test core'

Proposed changes:

Add flag --evaluate-models-in-dir to test command rasa test core to be able to compare models that were trained via rasa train core -c <config-1> <config-2>
rasa test core can handle compressed model files
moved utils methods (list_files, list_subdirectories, list_directory, create_dir) from rasa.nlu.utils to rasa.utils.io

closes https://github.com/RasaHQ/rasa/issues/4016
Status (please check what you already did):

[x] made PR ready for code review
[x] added some tests for the functionality
[x] updated the documentation
[x] updated the changelog
[x] reformat files using black (please check Readme for instructions)

The test is failing as the models are not properly trained right now. I guess something went wrong in one of the merge commits. Need to find the bug. Will let you know, once it is fixed.

@arthurTemporim @wochinge Issue is solved. Ready for review.


Descriptions for Grader assignments (fixes #189)

This PR introduces a description field to the Assignment class and furthermore assigns links to the descriptions.
@aemonk created a nice reference for all assignments on the grader branch. This PR will merge parts of the grader branch up until the last commit that introduced changes to the reference.
The links will result in an 404 error until the branch has been merged because it references the master branch.

Right now, the description value is not used, though. It is solely useful for people that inspect the source. I tried to print them after the assignment name, but I think it looks rather messy:

Maybe we could introduce a flag to print the URI of a given assignment?

What if we add /grader/compiler-assignments.md to the heading "Compiler Assignments" in the self.py output?
Then the students could look for themselves and since we have equality called assignments, this should be easy to do, right?

Can you reorder how the assignments appear in the output of self.py without any arguments?
Also, please rename "Usage:" to "synopsis:".

The assignments should appear in the order of how they are assigned in class.


Enable https protocol for TestHttpsAsyncTimeout, so timeout will be tested for real

Without this test finishes immediately with IOException: SSL not supported, so not real handshake testing performed

Committed to SVN and 4.4.x branch
http://svn.apache.org/r1683402


webpack 5 has outputed incompatible export.default

Bug report

What is the current behavior?
As we all known, exports.default is not compatible with ES3 syntax, and developers always use babel to convert it into exports['default'], but recently I found that Webpack 5 has incorrectly converted exports['default'] again into exports.default, and is there any workaround?
If the current behaviour is a bug, please provide the steps to reproduce.
To put it simply, we can compile a module with Webpack directly without Babel:
exports['default'] = {}

and you can find that after Webpack compilation, it has been converted to:
exports.default = {};

What is the expected behaviour?
Do not convert it.

Other relevant information:
webpack version: 5.48.0
Node.js version: 13.14.0
Operating System: Windows

Followed the code and found that whether preserved words is safe under a ES3 syntax environment?
https://github.com/webpack/webpack/blob/400a0f94ab45ca20b10f219c8311e87d3d3f108c/lib/util/propertyAccess.js#L8

We don't support es3

@alexander-akait It is not the problem about whether Webpack support ES3, it is the problem that Webpack has made any libraries supported under ES3 broken after compilation.

@alexander-akait what is the problem if outputting es3 styles? unnecessary code to maintain? The best solution is not to change the original source.

@alexander-akait what is the problem if outputting es3 styles? unnecessary code to maintain?

Yes, we don't want to support outdated ES3

We can merge your PR, but we do not want to guarantee ES3 compatibility

@alexander-akait  I know your thought, and as mentioned above, it is smart to implement a complicated detection to solve the problem, but it should be a height overhead.

Fixed https://github.com/webpack/webpack/pull/13972/


models: blacklist and whitelist not working

config.excluded_models and config.included_models are not working
i have 2 cases:

config.excluded_models << [AdminUser]

It shows every model including AdminUser

config.included_models << [Answer, Category, Course, Question, Subscription, User]

It does not show any model at all!
im using ruby 1.9.2p290, rails 3.1.0 and thin server v1.2.11

To exclude a single model, the proper syntax would be config.excluded_models << AdminUser (notice that there is no brackets and the use of << to push into the array).
To include multiple models, the proper syntax would be config.included_models = [Answer, Category, Course, Question, Subscription, User] (notice that this time, we use brackets but there is an equal sign to assign the content of the array to the included_models variable).

config.excluded_models are arrays.

thanks! its working ok.. but it should be documented in rails_admin.rb :)

@nahue Dammit! Fixed it in initializer.erb. Thanks for the head's up!


sm2: fix error raise to not fail make update

An old style error function code is used and the name is wrong.  This breaks make update and is hence urgent.

Merged, thanks.


Enable static consistent hash ring

By default, we build a dynamic consistent hash with the live worker list that comes from master or ETCD. Sometimes we want to build a static consistent hash ring to make sure we won't write data to other worker node when a worker node is offline temporarily (especially when other worker nodes are running out of disk space).
This PR provides allows us to build a static consistent hash ring by setting alluxio.user.dynamic.consistent.hash.ring.enabled=false. In this case, client will read from UFS if the worker where the specified file locate is down.

By default, we build a dynamic consistent hash with the live worker list that comes from master or ETCD. Sometimes we want to build a static consistent hash ring to make sure we won't write data to other worker node when a worker node is offline temporarily (especially when other worker nodes are running out of disk space).
This PR provides allows us to build a static consistent hash ring by setting alluxio.user.dynamic.consistent.hash.ring.enabled=false. In this case, client will read from UFS if the worker where the specified file locate is down.

actually if its etcd it has already been using a static consistent hash ring.

By default, we build a dynamic consistent hash with the live worker list that comes from master or ETCD. Sometimes we want to build a static consistent hash ring to make sure we won't write data to other worker node when a worker node is offline temporarily (especially when other worker nodes are running out of disk space).
This PR provides allows us to build a static consistent hash ring by setting alluxio.user.dynamic.consistent.hash.ring.enabled=false. In this case, client will read from UFS if the worker where the specified file locate is down.

actually if its etcd it has already been using a static consistent hash ring.

@lucyge2022 This PR makes us use dynamic consistent hash ring by default (no matter using ETCD or master). I changed the logic to get getLiveMembers instead of getAllMembers from ETCD by default.

@jja725 wondering if the hash ring change impacts the logic of distributedMv related?

@yyongycy this doesn't affect cp/mv, but probably affect distributed load, have to take a closer look.

@yyongycy this doesn't affect cp/mv, but probably affect distributed load, have to take a closer look.

Actually, we do want to affect distributed load. That is why we want to have this change. If there is a worker that is offline temporarily, static consistent hash ring allows user to avoid writing data to other worker nodes when executing load command and reading a file cached on the offline worker.

@yyongycy this doesn't affect cp/mv, but probably affect distributed load, have to take a closer look.

Actually, we do want to affect distributed load. That is why we want to have this change. If there is a worker that is offline temporarily, static consistent hash ring allows user to avoid writing data to other worker nodes when executing load command and reading a file cached on the offline worker.

Then we can update DefaultWorkerProvider.getWorkerInfos

@yyongycy this doesn't affect cp/mv, but probably affect distributed load, have to take a closer look.

Actually, we do want to affect distributed load. That is why we want to have this change. If there is a worker that is offline temporarily, static consistent hash ring allows user to avoid writing data to other worker nodes when executing load command and reading a file cached on the offline worker.

Then we can update DefaultWorkerProvider.getWorkerInfos

I updated DefaultWorkerProvider.getWorkerInfos. Please take a look when you have time. @jja725

btw, please do test it.

my understanding is that "master" mode is only used for backward purpose, will not be used for membership in the future.
correct?

my understanding is that "master" mode is only used for backward purpose, will not be used for membership in the future. correct?

Yes, it is only used for backward purpose. But some features still depends on master, for example load command requires master which has Scheduler for distributed load.

LGTM, But I'm still a little fuzzy what's the exact behavior/exception when we lost a worker which is still running the task or send a request to lost worker. Do you think we can add some comment on those behaviors?

The request will throw an exception after timeout. If we want to add a comment for this case, we need to identify the exact type of exception.

alluxio-bot, merge this please


Linux tests failing

🐛 Bug
Most of our linux tests are failing right now, and i'm not sure why. I noticed it a couple days ago :-(
I'm hoping it's just a CI think that will resolve, but I'm making this issue so we can have discussion
https://github.com/napari/napari/runs/1433860671

  File "/root/conda/lib/python3.7/threading.py", line 890 in _bootstrap

Current thread 0x00007f795adc1740 (most recent call first):
  File "/root/conda/lib/python3.7/site-packages/pytestqt/plugin.py", line 57 in qapp
  File "/root/conda/lib/python3.7/site-packages/_pytest/fixtures.py", line 930 in call_fixture_func
  File "/root/conda/lib/python3.7/site-packages/_pytest/fixtures.py", line 1124 in pytest_fixture_setup
  File "/root/conda/lib/python3.7/site-packages/pluggy/callers.py", line 187 in _multicall
  File "/root/conda/lib/python3.7/site-packages/pluggy/manager.py", line 87 in <lambda>
  File "/root/conda/lib/python3.7/site-packages/pluggy/manager.py", line 93 in _hookexec
  File "/root/conda/lib/python3.7/site-packages/pluggy/hooks.py", line 286 in __call__
  File "/root/conda/lib/python3.7/site-packages/_pytest/fixtures.py", line 1070 in execute
  File "/root/conda/lib/python3.7/site-packages/_pytest/fixtures.py", line 689 in _compute_fixture_value
  File "/root/conda/lib/python3.7/site-packages/_pytest/fixtures.py", line 605 in _get_active_fixturedef
  File "/root/conda/lib/python3.7/site-packages/_pytest/fixtures.py", line 1046 in execute
  File "/root/conda/lib/python3.7/site-packages/_pytest/fixtures.py", line 689 in _compute_fixture_value
  File "/root/conda/lib/python3.7/site-packages/_pytest/fixtures.py", line 605 in _get_active_fixturedef
  File "/root/conda/lib/python3.7/site-packages/_pytest/fixtures.py", line 1046 in execute
  File "/root/conda/lib/python3.7/site-packages/_pytest/fixtures.py", line 689 in _compute_fixture_value
  File "/root/conda/lib/python3.7/site-packages/_pytest/fixtures.py", line 605 in _get_active_fixturedef
  File "/root/conda/lib/python3.7/site-packages/_pytest/fixtures.py", line 585 in getfixturevalue
  File "/root/conda/lib/python3.7/site-packages/_pytest/fixtures.py", line 572 in _fillfixtures
  File "/root/conda/lib/python3.7/site-packages/_pytest/python.py", line 1633 in setup
  File "/root/conda/lib/python3.7/site-packages/_pytest/runner.py", line 448 in prepare
  File "/root/conda/lib/python3.7/site-packages/_pytest/runner.py", line 151 in pytest_runtest_setup
  File "/root/conda/lib/python3.7/site-packages/pluggy/callers.py", line 187 in _multicall
  File "/root/conda/lib/python3.7/site-packages/pluggy/manager.py", line 87 in <lambda>
  File "/root/conda/lib/python3.7/site-packages/pluggy/manager.py", line 93 in _hookexec
  File "/root/conda/lib/python3.7/site-packages/pluggy/hooks.py", line 286 in __call__
  File "/root/conda/lib/python3.7/site-packages/_pytest/runner.py", line 256 in <lambda>
  File "/root/conda/lib/python3.7/site-packages/_pytest/runner.py", line 310 in from_call
  File "/root/conda/lib/python3.7/site-packages/_pytest/runner.py", line 256 in call_runtest_hook
  File "/root/conda/lib/python3.7/site-packages/_pytest/runner.py", line 216 in call_and_report
  File "/root/conda/lib/python3.7/site-packages/_pytest/runner.py", line 121 in runtestprotocol
  File "/root/conda/lib/python3.7/site-packages/_pytest/runner.py", line 110 in pytest_runtest_protocol
  File "/root/conda/lib/python3.7/site-packages/pluggy/callers.py", line 187 in _multicall
  File "/root/conda/lib/python3.7/site-packages/pluggy/manager.py", line 87 in <lambda>
  File "/root/conda/lib/python3.7/site-packages/pluggy/manager.py", line 93 in _hookexec
  File "/root/conda/lib/python3.7/site-packages/pluggy/hooks.py", line 286 in __call__
  File "/root/conda/lib/python3.7/site-packages/_pytest/main.py", line 338 in pytest_runtestloop
  File "/root/conda/lib/python3.7/site-packages/pluggy/callers.py", line 187 in _multicall
  File "/root/conda/lib/python3.7/site-packages/pluggy/manager.py", line 87 in <lambda>
  File "/root/conda/lib/python3.7/site-packages/pluggy/manager.py", line 93 in _hookexec
  File "/root/conda/lib/python3.7/site-packages/pluggy/hooks.py", line 286 in __call__
  File "/root/conda/lib/python3.7/site-packages/_pytest/main.py", line 313 in _main
  File "/root/conda/lib/python3.7/site-packages/_pytest/main.py", line 257 in wrap_session
  File "/root/conda/lib/python3.7/site-packages/_pytest/main.py", line 306 in pytest_cmdline_main
  File "/root/conda/lib/python3.7/site-packages/pluggy/callers.py", line 187 in _multicall
  File "/root/conda/lib/python3.7/site-packages/pluggy/manager.py", line 87 in <lambda>
  File "/root/conda/lib/python3.7/site-packages/pluggy/manager.py", line 93 in _hookexec
  File "/root/conda/lib/python3.7/site-packages/pluggy/hooks.py", line 286 in __call__
  File "/root/conda/lib/python3.7/site-packages/_pytest/config/__init__.py", line 165 in main
  File "/root/conda/lib/python3.7/site-packages/_pytest/config/__init__.py", line 187 in console_main
  File "/root/conda/bin/pytest", line 8 in <module>
/tmp/scripts4592d2572bcd0668d2d6c52f5054e2d0.sh: line 8:  3568 Aborted                 (core dumped) pytest -v --cov-report=xml --cov=./napari

Exit status: 134

I'll add that versions installed look the same for both a passing test from two days ago and a failing test from yesterday, so it doesn't look like there was a new package released, but more likely something on the CI side

I'll add that versions installed look the same for both a passing test from two days ago and a failing test from yesterday, so it doesn't look like there was a new package released, but more likely something on the CI side

The main important difference is PySide2 version. Two days ago it was 5.15.1 and not it is 5.15.2. I think it should be checked first.

@sofroniewn please see # #1925

The main important difference is PySide2 version. Two days ago it was 5.15.1 and not it is 5.15.2. I think it should be checked first.

Wow, i completely missed that!! Thanks

So we know the issue is 5.15.2 and that tests can pass locally. I wonder if the following has any useful information? https://wiki.qt.io/Qt_5.15.2_Known_Issues

There is also PyQt5 released (2 minutes ago). It should be checked.

I found proper bug report https://bugreports.qt.io/browse/QTBUG-88688

So the option is to switch from gcc:latest to some ubuntu based image.

So I have little of time today and propose some fix in  #1937

@sofroniewn close?

Yes, thanks!! Closed by #1937


TTP Updater can't check when run manually on Linux and BSD

By fixing the internet connection bug in Tic Tac Py and its updater, I may have caused another issue, this time only affecting Linux and BSD where Tic Tac Py Updater can't be run manually - or, to be precise - opens an empty window. I hope to resolve this situation soon but at least you can play again without an internet connection.

It's fixed with a new update, but please don't forget to update.


histogram: add a fast coarse timer

Coarse timer uses CLOCK_MONOTONIC_COARSE, it is faster but less precise, and linux only.
Benchmark
test histogram::bench_histogram_coarse_timer            ... bench:          48 ns/iter (+/- 0)
test histogram::bench_histogram_timer                   ... bench:          86 ns/iter (+/- 0)

test histogram::bench_local_histogram_coarse_timer      ... bench:          48 ns/iter (+/- 0)
test histogram::bench_local_histogram_timer             ... bench:          85 ns/iter (+/- 0)

I prefer using a coarse feature. We should either use coarse or not.  /cc @BusyJay

CI failed @overvenus

any update? @overvenus


Navigation, History, etc, without using INavigable

I love template 10 and want to be able to leverage the navigation service to create a UWP version of an app I've written for Universal 8.1 and Xamarin Forms. However, this app was written with MvvmLight, with the Viewmodels in the PCL, shared to both the Windows 8.1 and Xamarin platforms.
As a result, I cannot inherit from INavigable in my PCL project to get the automatic navigation that calls the OnNavigatedTo, OnNavigatedFrom, etc., from the View in the UWP UI project passing to the ViewModels as you would do if everything was in the win10 project.
So far, the only way I've been able to achieve some success is by inheriting from my core PCL viewmodels in my UWP UI project and adding the INaviable interface to these, and passing the INaviable methods to the corresponding base viewmodel methods to activate them and pass parameters on navigate (as well as save them on navigate away).
this works (pretty well actually, I even kept my design time support from the pcl viewmodels) but it's a bit cumbersome and wordy.
Ideally (well for me of course, not template 10) the INavigable interface would be in a PCL so that I could just add it to my core project and be done with it.
Since this is obviously not possible (given dependencies on Win10 for Dispatcher, navigationmode, etc used by the navigation service), am I on the right/only track to make this work by using inheritance to decorate my viewmodels with the INavigable interface in the UI project?
the only other way I can think of getting the same kind of result is ditching template 10's navigation service entirely and copying over the suspension manager from Win8.1 to handle the navigation, back stack, etc. this works (I blogged about how to do that here), but I much prefer to use template 10 than recycling bits from my 8.1 project...
This is likely a case of that 20% of projects that just don't fit template 10, but I sure hate to lose all the work I did making my original project cross platform only to discover I locked myself out of using template 10 as a result.
I'd appreciate any insight or advice on how I might best achieve this, or if I am indeed on the right/only track for doing this, that'd be good to know too. thanks!

I just realized after submitting this isn't really an "issue" to be logged (other than to perhaps suggest the INavigable be portable, which is probably not possible), so if this would be better posted on StackOverflow please let me know and I'll direct such questions there in the future. thanks agian

We'll move all the interfaces in Template 10 to a cross-platform PCL when we release the Anniversary Update version of the library. That is the current plan. I can't solve your problem now, but that update should come pretty soon. We will not build it until the Anniversary Update is RTM. That when we start, not when we ship. Remember. Open Source. Volunteers.
By the way, thanks. I know this is important.


[AIRFLOW-1560] Add AWS DynamoDB hook for inserting batch items

Dear Airflow maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[x] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-1560

Description

[x] Here are some details about my PR, (No UI Changes):

The PR addresses airflow integration with AWS Dynamodb.
Currently there is no hook to interact with DynamoDb for reading or writing items (single or batch insertions). To get started, we want to push data in DynamoDB using airflow jobs (scheduled daily). Idea is to read aggregates from S3 and push in DynamoDB (write data job will run everyday to make this happen). First we want to create DynamoDB hooks (this PR addressed the same) and then create operator to move data from S3 to DynamoDB.
http://boto3.readthedocs.io/en/latest/reference/services/dynamodb.html#service-resource
Tests

[x] My PR adds the following unit tests :

test_aws_hook.py
adds mock_dynamodb2 from moto (https://github.com/spulec/moto). Wrote a test case to get aws resource object for dynamodb and create table via resource object and assert if count of items in table is 0 (implies table was created).

test_dynamodb_hook.py
adds mock_dynamodb2 from moto (https://github.com/spulec/moto). Wrote a test case to get aws resource object for dynamodb and create/insert data in dynamodb table. Then this unit test writes 10 items in the table using write_batch_data operation

Commits

[ ] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Codecov Report

Merging #2560 into master will decrease coverage by 0.06%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2560      +/-   ##
==========================================
- Coverage   70.88%   70.81%   -0.07%
==========================================
  Files         150      150
  Lines       11585    11585
==========================================
- Hits         8212     8204       -8
- Misses       3373     3381       +8

Impacted Files
Coverage Δ

airflow/www/app.py
94.11% <0%> (-2.36%)
:arrow_down:

airflow/configuration.py
83.01% <0%> (-0.95%)
:arrow_down:

airflow/jobs.py
77.67% <0%> (-0.37%)
:arrow_down:

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 9df0ac6...5883371. Read the comment docs.

This is my first PR for airflow. Still getting my head around the build errors :)

@artwr @criccomini seems like you guys reviewed similar AWS related PR - https://github.com/apache/incubator-airflow/pull/1630
Would be great if you could help review my PR. Any inputs are welcome (this is my first contribution to airflow) :)


Review draft procurement policy from TBS

Since 2014 TBS has been working on a reset of the various procurement policies.

https://www.gcpedia.gc.ca/wiki/Procurement_Policy_Division,_Treasury_Board_of_Canada_Secretariat/Policy_Suite_Reset


annotations: introduce example annotation

Motivations
When looking at the nit libraries, it's not rare to find external files used only to store examples that cannot be expressed as docunit.
The example annotation aims at tag pieces of code that may be considered as examples and thus be:

ignored be the compilation tools
used by documentation tools (and testing tools)

Why a new annotation?
Rather than the examples/ folder convention?

Examples can now be included directly in the module code if needed
Makes it easier to separate real code example from helper code and example tests
More flexibility in project organization and namming
To be coherent with the test annotation

How to use it?
Simply tag the MEntity with example:
module my_example_module is example

Can also be applied on classes and methods:
module my_module # is not example

# Abstract class A, we should provide an example of subclass...
# So let's see `ExampleA`.
abstract class A
end

# This class provides an example of how to sublass A.
class ExampleA is example
   super A
end

class C
    # This method provides an example of how to instantiate `A` sublcasses
    fun example_init_a is example do
        var a: A = new ExampleA
    end
end

Incoming work
This PR only introduces the annotation and applies it to the existing source code.
Next PR will make tools like nitweb, nitdoc and nitx use it (via commands #2580).

Reroll:

moved annotation to the primitive liste
factorized annotation parsing
is_example depends on mexample != null
added a test

reroll rebased on master to fix conflicts with #2580

Reroll: fix more tests.

Borken?

@ablondin : https://www.urbandictionary.com/define.php?term=borken


VM/VMSS: incorporate credentials validation logic used by portal

Fix #2010.  Fix #1943

Codecov Report

Merging #2537 into master will increase coverage by 0.06%.
The diff coverage is 81.08%.

@@            Coverage Diff             @@
##           master    #2537      +/-   ##
==========================================
+ Coverage   72.02%   72.08%   +0.06%
==========================================
  Files         362      362
  Lines       19766    19791      +25
  Branches     2913     2921       +8
==========================================
+ Hits        14236    14266      +30
+ Misses       4612     4602      -10
- Partials      918      923       +5

Impacted Files
Coverage Δ

...cli-vm/azure/cli/command_modules/vm/_validators.py
71.42% <81.08%> (+2.57%)
:white_check_mark:

src/azure-cli-core/azure/cli/core/_util.py
66.66% <0%> (ø)
:white_check_mark:

...-cli-role/azure/cli/command_modules/role/custom.py
17.89% <0%> (ø)
:white_check_mark:

...dback/azure/cli/command_modules/feedback/custom.py
34.69% <0%> (ø)
:white_check_mark:

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 ac03b51...7f545da. Read the comment docs.


Added support for multiple expressions with passing tests

@lilleyse @Dylan-Brown
Keys inside the expressions object and the key "expression" are now all used in parsing conditions.
Had a bit of trouble with having to learn and fix the new RegEx parsing, but it all works now!

This is for Ticket #5153.
For now, the support is for ${key}, where the keys are case sensitive.
I haven't really thought about reserved expression names, especially since I don't know which ones are reserved. Since it looks like all reserved expressions are in full uppercase, one idea would be to standardize all keys in this spec to be .toLowerCase(). I would love your input on this issue!

RE: New comments under original issue
I did indeed implement this as string replacement. Therefore, I guess this isn't really a performance improvement, but I think this feature still has value as a development tool / convenience tool, as it'll be much more convenient for developers to write conditions with multiple expressions .

For now, the support is for ${key}, where the keys are case sensitive.
I haven't really thought about reserved expression names, especially since I don't know which ones are reserved. Since it looks like all reserved expressions are in full uppercase, one idea would be to standardize all keys in this spec to be .toLowerCase(). I would love your input on this issue!

This is probably the right approach. If a batch table property or built-in property (like POSITION) and expression happen to use the same name, precedence goes towards the expression.

Looks great overall!
As just one extra thing can you edit one of the examples in 3D Tiles Point Cloud Styling or make a new example to use multiple expressions? Visual testing is always nice.

@Jane-Of-Art @lilleyse what is the plan here?  Do we want to get this into 3d-tiles soon so we get that branch in shape for master?

@lilleyse do you plan to finish this up?

This was pretty close already, so I'm fine with finishing it up.

@pjcozzi this is ready now.

Spec issue: https://github.com/AnalyticalGraphicsInc/3d-tiles/issues/226
This is a breaking change for any styles that use the ${expression} inside a conditions list.

@pmconne heads up for this small breaking changing in the styling language: https://github.com/AnalyticalGraphicsInc/cesium/pull/5232#issuecomment-303422510
Thanks again @Jane-Of-Art @lilleyse!


Add support for adding arbitrary groups via the UI

1.6.14 +
Currently, there is no way to add arbitrary groups (groups that the currently logged in user is not a part of) to Rancher from the UI while using SAML access controls. Rancher will see the arbitrary group as a user. This feature will need API parity, and should support the full DN when adding groups.

Expected behavior: Adding a arbitrary Active Directory group to an environment's Access Control list from the UI results in a group being added that gives all of the members of that group access to an environment
Actual behavior: Adding a arbitrary Active Directory group to an environment's Access Control list from the UI results in the group being interpreted as a user

This functionality should work in all places where a user can be authorized for an environment, namely:

The access control page for an individual environment
The admin access control page

Validation of LDAP groups is not required for our use case, as the SAML assertion must be used for the group information.

With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.


remove "Mask Alpha" as a button depending on Path Trace

Only show "Mask Alpha" if users select "Path Trace", just like "Density"

Issue addressed


incompatible vector issue

https://github.com/drofphilosophe/USElecData/blob/ef18a2f4986708677f49509d8e42a1b7968a0eea/src/EPA-CEMS/netToGrossCalculation.R#L310
im getting this error here:
Error in stop_vctrs(x_size = x_size, y_size = size, x_arg = x_arg, class = c("vctrs_error_incompatible_size",  (netToGrossCalculation.R#302): Can't recycle input of size 287 to size 0.
Show stack trace
when I run just the rename i get a tibble: 0x6. wondering if it was supposed to be empty?

A zero-length data frame was loaded resulting from a bug that failed to create monthly data. This has been resolved.


Markdown reference generator - disable toc

This small PR updates the clap_markdown dependency, replaces display_name with bin_name, and adds disable_toc for markdown reference generator
Checklist

[x] Changelog updated

Not sure why the tests are failing here - didn't touch that part of the code 🤷

Not sure why the tests are failing here - didn't touch that part of the code 🤷

Rust was updated to 1.72, that also means that clippy was updated.


Misc cleanup and general change suggestions

Cleanup

requirements.txt and especially requirements-dev.txt - do we need everything there ? Some dependencies may be redundant (e.g. mthree in dev reqs - is it really needed?)
tools/deploy_documentation.sh - the script is written for runtime docs, need to be adapted or removed
qiskit_ibm_experiment

constants.py - QISKIT_IBM_RUNTIME_API_URL - is it the right URL/name for the experiment service API ?
client/session.py - some runtime related constants. Should they adjusted for the experiments service or removed ?

Simple changes

Documentation

Update CONTRIBUTING.md for the repo
Write some informative text in README.md

Change the 'experiment' folder name to 'service'.

Done in #20


Voting percentages on snapshot.page differ from those calculated with data in downloaded report

There could be a bug in the calculation of vote result percentages if the downloaded report vote data is accurate.
There appears to be a discrepancy in the calculated voting percentages presented on the snapshot.page was for the core vote https://snapshot.org/#/aavegotchi.eth/proposal/QmNqRry73rWXb9tdyHummihcK58ga83Ru15AJRF3beFJ35.  Data was provided in the available downloadable report.
The final result percentages were reported as follows:
Option

2.51m GHST - 38.46%
377.55k GHST - 5.78%
3.54m GHST - 54.25%
98.41k GHST - 1.51%
Totaling 100%

Analysis of the data in the download CSV report file, however, generated these final result percentages:
Option

2510680.55326219 GHST - 37.99%
377552.411966031 GHST -  9.30%
3541698.81338083 GHST - 49.49%
98408.5243795093 GHST -  3.22%
Totaling 100%

The raw token vote counts appear to agree but the percentages calculations differ significantly.  The CVS report file was converted to XLSX so it could be attached.  It may be that the fractional token votes less than one (1.00) in the CVS file are tallied incorrectly; there are 232 of 1657 entries meeting this criteria.
snapshot-report-QmNqRry73rWXb9tdyHummihcK58ga83Ru15AJRF3beFJ35.xlsx

Hi @letscrypto, the data seems to match the downloaded report now, you can see my results here: https://docs.google.com/spreadsheets/d/1Z2eVDt2MAUmyit5PmKJb2pTG4TfDT5c19bSBk6QLorM/edit?usp=sharing

I agree with samuveth's spreadsheet.  The displayed and the reported percentages are essentially the same. I must have miscalculated with the downloaded data. Sorry for the wild goose chase.


docs: end user llm monitoring demo notebook

MVP / first pass at a user-facing walkthrough of setting up openai API monitoring & viewing autoboard.
TODOs:

[x] best way to save/direct folks to board (concrete instructions)
[x] big splash image
[x] redo gifs for human frame rate
[x] copy-edit for save, rename, publish flow
[ ] more helpful example for stream of messages?
[x] more UX walkthrough / screenshots
[x] correct openai authentication
[x] remove devmode + try without it
[ ] count tokens for streaming?, will we do that?
[ ] extend/continue experiments?

MVP ready to go!
notes

gifs will not load until merge to main (paths are hardcoded to main)
leaving wandb entity blank so notebook will error unless this is set
can remove brief note about token counting in streaming message case after that is implemented.


Php Intellisense to include variable suggestions without having to type the dollar sign first

Type: Feature Request
When coding php scripts, I can only get variable suggestions if I type the dollar sign first. It would be nice to have variable suggestions to show by just typing the name of the variable without having to type the dollar sign first, similar to IntelliJ PhpStorm.
VS Code version: Code 1.82.2 (abd2f3db4bdb28f9e95536dfa84d8479f1eb312d, 2023-09-14T05:55:25.390Z)
OS version: Windows_NT x64 10.0.22621
Modes:

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.83.0. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

I updated to the latest version and it's still the same

Built-in PHP support is very basic- this would be a good request for one of the PHP extensions


SecureRandom.getInstanceStrong is backed by /dev/random on Linux/MacOS

On Java 1.8.0_92, SecureRandom.getInstanceStrong() returns an instance which uses the NativePRNGBlocking algorithm, which pulls from /dev/random.
Would it be better to just try the NativePRNG algorithm and if that doesn't exist simply use the default instance? I'd be happy to put a PR together for this.

Sorry — I meant NativePRNGNonBlocking, not NativePRNG.

👍


[Monitoring] Add automatic size limit for database

The database should be limited to a certain size. If the size is exceeded old events should be deleted. To make this consistent we should create another table with the state at the beginning before all update events. When the database is compressed all events should be processed and the starting table must be updated.
As limits it would be great to have to options:

time limit
database size limit

Doesn't seem to be necessary even after monitoring for a month the data usage stays relatively healthy.


chore: pass auth headers from http request to jsonrpc request (WIP)

Re #5787

I don't think it's it's worthwhile anymore.


Typo fix on specifying-the-master-page-programmatically-cs.md

Corrected the typo error on line #137 (Alternate.master)
No Issue is related to this fix.

@cmelo05 Thank you for taking the time to fix this, and congrats on your 1st contribution to this repo!


blooket hacks tokens

in the past i have used your global hacks and they have been fine but for the last 3 months they have stopped working maybe
you could use one of your past hacks so that it might work than do nothing

repository is made by a skid and impersonator, i do not suggest using it

no plans to :)

repository is made by a skid and impersonator, i do not suggest using it

the person who first owner the repo was the fake, the current owner is real as he posted the files with no obfuscation.

repository is made by a skid and impersonator, i do not suggest using it

the person who first owner the repo was the fake, the current owner is real as he posted the files with no obfuscation.

he stole it from twitter. he is not gliz. gliz is done w blooket.

@Greenlio does gliz have a GH anymore, even?

@vantr-o read #445

Oh wow LOL so an impersonator stole this repo from a impersonator just because, thats sad.

@Greenlio does gliz have a GH anymore, even?

no

??

who impersonate

gliz actually took this account from a skid and lost the email and password, we're working on getting it back

gliz actually took this account from a skid and lost the email and password, we're working on getting it back

being geniune good luck hope you get it back


Completed Questionnaire w/o progress bar

In creating this PR request, I:

Create functional components per question.
Transferred user input across pages
Improved UI using the provided Colors in the folder structure.
Used useStates and useEffect() for synchronous updates to the data.

In a future PR I will expect to implement a progress bar across the top of the questionnaire. I will also connect the questionnaire to the home page, and connect the data collected to the server.

Hey Erick, I ran your code and it shows that it hassuccessfully implemented the required features and has not shown any conflicts with the main branch. It's great to see that you have used functional components, transferred user input, improved UI, and used appropriate hooks for updates. Your plan for future improvements is also impressive. Overall, your efforts seem to be in line with the project requirements, and I look forward to your next feature on the sprint. If I could make one request, I do think the files could be refactored into separate components, as testing those functions would become a lot clearer on the unit tests. Other than that,  Keep up the good work!


⚠ main has degraded performance

In 0e01a5a, main ($MAIN_API_URL) experienced degraded performance:

HTTP code: 200
Response time: 28785 ms

Resolved: main performance has improved in abdbbc4.


Spec is unclear about how much of the key response needs to be signed

In practice synapse includes a tls_fingerprints (as carryover from a legacy spec) however it is not described as needing covering by the signing algorithm. We should spell out for notaries that they need to verify signature and sign the whole object, non-standard keys and all.

yeees, although they just follow the standard Signing JSON algorithm...

True, but it's a bit of a trap that notaries have to be designed to store arbitrary JSON rather than well-defined JSON it can pick apart in a database. Just needs a small note to say that other fields might be present to aid development, I think.


Parsing of escaped QualifiedGraphNames

When executing something like
FROM GRAPH `foo.bar` ....
the resulting parsed qualified graph name is
`foo.bar`
instead of
foo.bar

Parsing an escaped namespace works fine in FROM GRAPH
 FROM GRAPH `a.b.c`.graph returns the correct result
However CONSTRUCT `a.b.c`.graph does not work


Add Support for Glamor / Aphrodite (CSS-in-JS)

Currently, glamor (and im guessing aphrodite) styles aren't rendered by Phenomic in the build process.

We will need to find a way to detect when this libs are used (maybe just trying to require those?) and adjust the rendering method automatically by handling this requirements:

https://github.com/threepointone/glamor/blob/master/docs/server.md
https://github.com/Khan/aphrodite#server-side-rendering

Or alternatively, we can offer user a way to handle global html generation, like requested in #826 (but I guess we can do both, plug and play is what I want at the end)

@MoOx
Hi Moox. I think i fixed an issue with my site's homepage address and it is rendering glamor styles correctly now.
The only slight problem is the flash of unstyled content while it loads the styles. I'm not super experienced but I assume the fix is to make sure these are being rendered in the document  somehow?

The only slight problem is the flash of unstyled content while it loads the styles. I'm not super experienced but I assume the fix is to make sure these are being rendered in the document somehow?

Exactly, we need to implement this. Should be pretty easy to do.
I guess detection of glamor/aphrodite can be made using a simple try catch :)

Ahh okay, at first my issue was the Glamor styles not loading at all (which was my fault, not Phenomics) so I thought I had misrepresented the issue. Glad we're on the same page.

@mxstbr is there any similar requirement for styled-components (for static rendering as css)?

Absolutely none, you can use CSS just as-is! Would love for you to try it and let me know how it goes, I haven't done your use case yet so it might break?

@mxstbr I see there is an open issue about that https://github.com/styled-components/styled-components/issues/124 and I understand from the very first lines that you use Glamor under the hood, so I guess adding support from glamor ssr will make it work for styled-components as well.
The idea is to be able to pre-render styles as CSS so pages work without JavaScript.


Multiplayer: default difficulties take 3 clicks to remove

not sure why, but I think #317 fixes this?


Show file details for uploaded documents

We need to show all available file details to the document owner. Ideally we can show this in a nice form as designed in #338.

Today we only show:

We should show:

"pretty file name" (editable)
Boolean for visibility (editable)
full document name (i.e. "24234_xcsdd_3242.xlsx")
doc size in KB
MIME Type if available
uploaded by / uploaded on

@NolanChan @diegoaad This could be a good small improvement based on a user feedback call I just had...

Hi @dottorer , can I assume this specific issue just concerns the edit page? And if it does, how would you like the extra information to be shown on the page? Is there a similar page that I can look to?

Were you thinking of something like this?

@NolanChan when talking to @dottorer I understood that we'd still allow only the Name and the option "Visible to all helpers" available for edition. But on top of that we should show the File info including doc name, size, mime type and uploaded by/on. This could be a new widget on top of the page, like this one:

@NolanChan Yep, this is what I am dreaming of. We would then have a reusable representation of any document with its core data displayed. I will create some mockups asap to make my thoughts more clear.

@NolanChan On the page 'Edit document', the solution you shown above would be a quick stop gap and can be helpful. I would request that for the immutable fields (anything but pretty name and visibility), we do not show the frame around the field but only the value. Maybe it is possible to condense the info in 2 cols or something neater without too much work.
Also, on this specific page it would be great to have a button on the very right bottom spot that says 'Delete'. Since we currently do not allow for update the stored file, we require people to actually delete the document and create a brand new one. This sucks as any bookmarked URL will be broken, so I am opening a separate issue in #442 for that one.

Hey @dottorer , I'm trying to make a simple code representation of your mock up. Could I get that default Lale picture?

Hi @NolanChan : were you thinking about the tulip icon? I think we could use this for it...

I can send you the SVG directly as well...

Hi @dottorer , here's a rough draft of my mock up so far. Could you give me some pointers on how it is so far? I haven't coded in any of the back-end yet to show any actual values.


repo names should be clickable

Is your feature request related to a problem? Please describe.
I see my repos listed. but there is no link to my repo
Describe the solution you'd like
change all repo names to a clickable link
Describe alternatives you've considered
I need to search manually my github repos
Additional context

@muescha, I apologize for the delayed response. Currently, clickable support is only available in Insight mod dashboards.
@MichaelBurgess, Could you please check this one to see if it is feasible?

@bigdatasourav the control results are just JSON and I believe the control message is plain text, so we can’t link to the repo. In order to do that we’d need to support richer text in the message, such as markdown and that would be a core change to controls - we’d need to run the idea past @johnsmyth and @cbruno10.
Also, the tags are plain text, so it’s not possible to interpret as a link.


Could you add MeowForms badge?

Hello,
I am using MeowForms in my project I already added Deno, Drash, Tailwind CSS badges, now I need MeowForms haha. Please!!!

sure , i would work on that :) adding a badge in meowform would be great :cat\

Hi, I am very much interested to work on this issue. Can you please assign it to me?


DateTimePicker broken

Django renders the field as "#id_" but JS is looking for "#id__picker". As of Django 1.7.

Same problem here, is there some patch? is related with the django version ?


add expiration label to build-service pull-request builds

STONEBLD-2204
Checklist:

PR has reference to the issue(s) it resolves
Write / update unit tests
Write / update integration (envtest) tests
Ensure there is an issue for e2e tests if needed
Ensure make test passes
Ensure test coverage hasn't decreased
Test code changes manually
Update readme and documentation
Write PR description that highlights overall changes and add usage examples if applicable

/retest


Pandas data frame agent hallucinates when asking a quesry: Sending python code insted of actual result

I created a pandas dataframe agent when i am querying over multiple csv files sometimes it is giving correct answer some time it is hallucinates by giving the python code to run to get the answer.
Here's the response I am getting:
To determine the region with the highest total revenue, we can group the data by region and calculate the sum of the total revenue for each region. Then, we can find the region with the highest sum.

Here is the corresponding Python code to find the region with the highest total revenue, as well as the corresponding country and item type:

# Group the data by region and calculate the sum of total revenue for each region
region_revenue = df.groupby('Region')['Total Revenue'].sum()

# Find the region with the highest total revenue
highest_revenue_region = region_revenue.idxmax()

# Find the corresponding country and item type for the highest revenue region
corresponding_country = df[df['Region'] == highest_revenue_region]['Country'].iloc[0]
corresponding_item_type = df[df['Region'] == highest_revenue_region]['Item Type'].iloc[0]

highest_revenue_region, corresponding_country, corresponding_item_type

The region with the highest total revenue is Middle East and North Africa. The corresponding country is Azerbaijan and the corresponding item type is Snacks.

here is the agent i initiated:
create_pandas_dataframe_agent(
            ChatOpenAI(temperature=0.0, verbose=True,
                       model='gpt-3.5-turbo'
                       ),

            self.df,
            verbose=True,
            max_iterations=20,
            agent_type=AgentType.OPENAI_FUNCTIONS,
            # handle_parsing_errors=True,
            agent_executor_kwargs={
                "handle_parsing_errors": True
            }

        )

Do you think the chain is stopping in between before completing the response?

@dosubot Here's some additional response from command prompt that will help you analize:
ould not parse tool input: {'name': 'python', 'arguments': "import matplotlib.pyplot as plt\n\nregion_counts = df['ship_region'].value_counts()\n\n# Plotting the distribution of orders by ship_region\nplt.figure(figsize=(10, 6))\nplt.bar(region_counts.index, region_counts.values)\nplt.xlabel('Ship Region')\nplt.ylabel('Number of Orders')\nplt.title('Distribution of Orders by Ship Region')\nplt.xticks(rotation=45)\nplt.show()"} because the `arguments` is not valid JSON.Invalid or incomplete response
- Invoking: `python_repl_ast` with `{'query': "import matplotlib.pyplot as plt\n\nregion_counts = df['ship_region'].value_counts()\n\n# Plotting the distribution of orders by ship_region\nplt.figure(figsize=(10, 6))\nplt.bar(region_counts.index, region_counts.values)\nplt.xlabel('Ship Region')\nplt.ylabel('Number of Orders')\nplt.title('Distribution of Orders by Ship Region')\nplt.xticks(rotation=45)\nplt.show()"}`

I can take on this issue if this is not resolved yet!

I can take on this issue if this is not resolved yet!
Hi @umair313
Sure I am using langchain V 0.0.320, also if you like we can connect.

I can take on this issue if this is not resolved yet!
Hi @umair313
Sure I am using langchain V 0.0.320, also if you like we can connect.

can you share the input you given to the chain ?

It is normal user query, about the data frame


check_syntax: SHIFT with CSEQUENCE

REPORT zfoobar.
CLASS lcl_foobar DEFINITION.
  PUBLIC SECTION.
    METHODS test EXPORTING ev_foo TYPE csequence.
ENDCLASS.
CLASS lcl_foobar IMPLEMENTATION.
  METHOD test.
    SHIFT ev_foo LEFT DELETING LEADING space.
  ENDMETHOD.
ENDCLASS.

/zfoobar.prog.abap[8, 5]: Shift, Target not char like(check_syntax)
PS: Highlighting for CLASS doesn't work properly

highlighting: yea, I'm messing with the semantic highlighting feature, it has issues on the playground

@mbtools try again, 2.79.0

👍


Create a "Instance Admin" Tutorial.

At the end of this task we will have a tutorial page describing the basic reading and writing from Bigtable APIs. The page will be linked from the top-level Bigtable documentation here:
https://googlecloudplatform.github.io/google-cloud-cpp/latest/bigtable/index.html
It is enough to create a document in bigtable/doc, like the existing bigtable-hello-world.dox.
The tutorial should cover (each one of these tasks should become its own GitHub issue):

[ ] Create an InstanceAdmin object.
[ ] Create a development instance with HDD.
[ ] Create a production instance with SSD.
[ ] Get the details of an instance.
[ ] Use GetInstance + CreateInstance() to create an instance if it does not exist.
[ ] ListInstance to list all the instances.
[ ] UpdateInstance: change something (maybe number of nodes)?
[ ] Delete an instance: with a lot of warnings!!
[ ] Create a new cluster.
[ ] Get the details of a cluster.
[ ] List all the clusters.
[ ] Update a cluster
[ ] Delete a cluster.
[ ] Show how to use more than one cluster per instance.

This is subsumed by #615


Example fails to run with "Grow undefined (type *styles.Style has no field or method"

This is on my 2023 MacBook Pro, Go version 1.21.4,  I installed the Vulcan drivers with all options
I searched around and couldn't find anyone having the same issue
Here is the full error:
reuben@ThinBoy:~/git/gi/examples/widgets$ go build
# goki.dev/gi/v2/gi
../../gi/button.go:174:6: s.Grow undefined (type *styles.Style has no field or method Grow)
../../gi/button.go:187:7: s.Gap undefined (type *styles.Style has no field or method Gap)
../../gi/button.go:191:7: s.Min undefined (type *styles.Style has no field or method Min)
../../gi/button.go:192:7: s.Min undefined (type *styles.Style has no field or method Min)
../../gi/button.go:195:7: s.Align undefined (type *styles.Style has no field or method Align)
../../gi/button.go:199:7: s.Min undefined (type *styles.Style has no field or method Min)
../../gi/button.go:200:7: s.Min undefined (type *styles.Style has no field or method Min)
../../gi/button.go:210:7: s.SetNonSelectable undefined (type *styles.Style has no field or method SetNonSelectable)
../../gi/button.go:211:7: s.SetTextWrap undefined (type *styles.Style has no field or method SetTextWrap)
../../gi/button.go:214:7: s.Max undefined (type *styles.Style has no field or method Max)
../../gi/button.go:214:7: too many errors

Apologies for the issue. It should be fixed now if you pull the latest version of gi. There is currently some instability in the codebase due to an ongoing major redesign, but things should be more stable now, and the latest released version (currently v2.0.0-dev0.0.11) will always work. The documentation is currently out of date and will be significantly improved soon, and many tutorials and tests will be added. Currently, examples/demo provides the best demonstration of the features of the framework and how to write code with it.

It builds now but fails to run, I'll switch to latest
Here is the error if you're interested:
$ ./widgets
2023/11/14 15:50:56 ERROR open /Users/reuben/Library/GoGi/prefs.json: no such file or directory
[mvk-error] SPIR-V to MSL conversion error: Unsized array of descriptors requires argument buffer tier 2
[mvk-error] VK_ERROR_INVALID_SHADER_NV: Fragment shader function could not be compiled into pipeline. See previous logged error.
panic: vulkan error: vulkan error: invalid shader (NV) (-1000012000)

goroutine 1 [running, locked to thread]:
goki.dev/vgpu/v2/vgpu.IfPanic(...)
	/Users/reuben/go/pkg/mod/goki.dev/vgpu/v2@v2.0.0-dev0.0.15/vgpu/errors.go:39
goki.dev/vgpu/v2/vgpu.(*Pipeline).Config(0x1400022a200)
	/Users/reuben/go/pkg/mod/goki.dev/vgpu/v2@v2.0.0-dev0.0.15/vgpu/pipeline.go:194 +0x4d4
goki.dev/vgpu/v2/vgpu.(*System).Config(0x140001d59a0)
	/Users/reuben/go/pkg/mod/goki.dev/vgpu/v2@v2.0.0-dev0.0.15/vgpu/system.go:277 +0xdc
goki.dev/vgpu/v2/vdraw.(*Drawer).ConfigSys(0x140001d59a0)
	/Users/reuben/go/pkg/mod/goki.dev/vgpu/v2@v2.0.0-dev0.0.15/vdraw/config.go:106 +0x7cc
goki.dev/vgpu/v2/vdraw.(*Drawer).ConfigSurface(0x140001d59a0, 0x14000318a50, 0x1400032a480?)
	/Users/reuben/go/pkg/mod/goki.dev/vgpu/v2@v2.0.0-dev0.0.15/vdraw/vdraw.go:51 +0x9c
goki.dev/goosi/driver/desktop.(*appImpl).NewWindow.func2()
	/Users/reuben/go/pkg/mod/goki.dev/goosi@v0.0.11/driver/desktop/app.go:250 +0x11c
goki.dev/goosi/driver/desktop.(*appImpl).mainLoop(0x10723ab20)
	/Users/reuben/go/pkg/mod/goki.dev/goosi@v0.0.11/driver/desktop/app.go:158 +0xf4
goki.dev/goosi/driver/desktop.Main(0x14000066728?)
	/Users/reuben/go/pkg/mod/goki.dev/goosi@v0.0.11/driver/desktop/app.go:80 +0xa4
goki.dev/goosi/driver.driverMain(...)
	/Users/reuben/go/pkg/mod/goki.dev/goosi@v0.0.11/driver/driver_desktop.go:20
goki.dev/goosi/driver.Main(...)
	/Users/reuben/go/pkg/mod/goki.dev/goosi@v0.0.11/driver/driver.go:27
goki.dev/gi/v2/gimain.Run(0x1069e5360)
	/Users/reuben/git/gi/gimain/gimain.go:26 +0x60
main.main()
	/Users/reuben/git/gi/examples/widgets/widgets.go:22 +0x24
	```

Same error when trying to run on latest

This is a new bug with the recent vulkan drivers on mac -- if you grab 1.3.250 from here: https://vulkan.lunarg.com/sdk/home  it should work.

Here's an updated ticket tracking this issue: https://github.com/goki/vgpu/issues/9


Cannot Load Recombination Module

Have update 1.54.6 but recombination module won't loadd on startup.  I try to launch the AHK file from the modules folder and I get an error.

You can't launch modules individually. You have to launch the Lailloken UI.ahk file in the main folder, and the tool will run in the background while PoE is open. Here's a quick-start/setup guide, and most features also have their own entry in the wiki (sidebar on the right).

Yeah I did that but it wasn't loading into the main UI, hence I tried to launch it to "add" it to the UI.

The recombination simulator doesn't have its own settings section because the feature is rather simple and doesn't need it. This is mentioned in the wiki, and it also explains how to use the feature.

Thank you.  I finally got it to work but I don't see any of the NNN, EXCL or DESIRED BASES check boxes.
Any ideas?

You're running an older version (v1.54.6), which I missed earlier. You can use the built-in updater to get the latest version.


Pub Serve doesn't work in 1.22.0-dev.7.0

Summary:
I was trying to run the simple web application from the sample content, but "pub serve" doesn't appear to work properly.
After the line: "Loading dart_to_js_script_rewriter transformers...", I just get a list of global options and available commands for pub.
What steps will reproduce the problem?
Create a new project with the sample content named: "Simple Web Application". After resolving dependencies, run web/index.html
What is the expected output? What do you see instead?
Expected:
The following text in the Pub Serve window (likely using a different port):
"C:\....\dart-sdk\bin\pub.bat" serve web --port=57064
Loading source assets...
Loading dart_to_js_script_rewriter transformers...
Serving Test7 web on http://localhost:57064
Build completed successfully
[web] GET Served 4 assets.

as well as the web app launching in Chromium
Actual:
"C:\....\dart-sdk\bin\pub.bat" serve web --port=57258
Loading source assets...
Loading dart_to_js_script_rewriter transformers...
Pub is a package manager for Dart.

Usage: pub <command> [arguments]

Global options:
-h, --help             Print this usage information.
    --version          Print pub version.

etc.
ending with
Run "pub help <command>" for more information about a command.
See http://dartlang.org/tools/pub for detailed documentation.
Pub Serve terminated

and Chromium only showing a 502 Bad Gateway error
What version of the product are you using?
Dart 1.22.0-dev.7.0
WebStorm 2016.3 (but also the case for IntelliJ 2016.3)
On what operating system?
Windows 10(64bit) (in the above example, but the same was the case on OS X Sierra)
Please provide any additional information below.
Also tried to run pub serve from the terminal, with the same result.
Running pub get in WebStorm I get this message:
Resolving dependencies...
Got dependencies!
Process finished with exit code 0

While in IntelliJ I get:
Resolving dependencies...
Got dependencies!
Precompiling dependencies...
Loading source assets...
Loading dart_to_js_script_rewriter transformers...

followed by the pub help information.

https://github.com/dart-lang/sdk/issues/28346

Like @alexander-doroshko notes, this is a duplicate of https://github.com/dart-lang/sdk/issues/28346.


Add Dependabot configuration

In accordance with RFC 126, we're configuring Dependabot to only
raise Pull Requests for the following three categories:

Security updates
Internal libraries
Framework libraries

Things have moved on slightly since the RFC; we're now using
GitHub native configs rather than the legacy .dependabot
approach. The syntax is slightly different to the example config
provided in the RFC but most of it is easily transferable.
For (1), there is no longer a config option, as
security updates are configured in the GitHub repository
'security' settings tab itself.
We've handled (2) and (3) in config, and have set it to only raise
PRs for direct updates, i.e. updates to subdependencies of the
named dependencies will not raise PRs. Unfortunately the
default behaviour would be to update all dependencies in the
lockfile.
We've chosen a govuk* wildcard to cover things like
gds-api-adapters and govuk_app_config and other unknown future
dependencies. Having govuk as a suffix is not encouraged
so instead of a *govuk wildcard we've named rubocop-govuk
explicitly. We explicitly name dependencies beginning with gds
for the same reason.
Trello: https://trello.com/c/uPoriyfJ/2049-add-dependabot-configuration-to-each-repo-blitz-pair

All good, just missing scss_lint-govuk maybe?