Declared delimiter now takes the whole next token

This allows for multi-character delimiters.

@harawata can we get this merged in?

Hi @chb0github ,
I have fixed it using regular expression.
Thanks for the report!

I looked at your change - Sitting on it for 2 weeks and changing the impl after I already submitted a PR kinda steals credit for the effort I put in. Granted, it's minimal.

Is this also part of the migrations (snapshot)? @harawata

@svscorp ,
It is now in the latest snapshot bundle.
https://oss.sonatype.org/content/repositories/snapshots/org/mybatis/mybatis-migrations/3.3.2-SNAPSHOT/

Hi @harawata
Thank you very much. It works! There is an issue I ran into - if I use delimiter like this -- @DELIMITER --MYBATIS it doesn't work and I assume it's expected behavior. The question is - is it possible to make this case covered as well?
The reasoning behind is that SQL scripts are passed through SonarQube scanner and having a symbol or  word on a new line / in the end of the line is resulting in syntax error :) In the world of continuous improvement it will be a pain.
Another question maybe worth of opening a feature request - whether it is possible to handle single line comments in SQL files? -- some user comment or ...statement; -- comment. It would be more transparent from developing / debugging point of view as initially it's not clear why it is not supported.

Hi @svscorp ,

if I use delimiter like this -- @DELIMITER --MYBATIS it doesn't work and I assume it's expected behavior.

Does -- @DELIMITER MYBATIS cause the syntax error, too?
-- @DELIMITER MYBATIS

INSERT INTO table1 (id, name) VALUES (1, 'abc')
MYBATIS

-- @DELIMITER ;

If so, it seems like a SonarQube issue to me.
Is the scanner an official one? It's hard to believe that you are the only user who is suffering from this error.

whether it is possible to handle single line comments in SQL files?

Have you tried ## comment syntax?
https://github.com/mybatis/migrations/issues/46#issuecomment-217987494
Personally, I think ScriptRunner should not remove comments from SQL except the special comments prefixed with @.
But I'm not sure if it's safe to change the current behavior.


fix: updated workflow and requirements file

https://github.com/tanx-libs/tanx-connector-python/pull/1#issuecomment-1959351018


add missing libelf dependency to kernel-module-injector image

this PR fixes problem of compiling DRBD module on Rocky Linux 9
more details: https://github.com/deckhouse/deckhouse/issues/2268

Which is the Dockerfie used by piraeus-operator by default?
I would like to update just this, because having libelf-dev makes it working on Rocky Linux 9 as well.

I guess for Piraeus, which uses the Compile method by default, we really could have just a single image. I believe as long as the GCC version is modern enough to support all compile options on modern kernels we should be good.
But that's just speculation. KBuild will issue a warning if you use a different compiler when building the kmod compared to the kernel, and I assume that warning exists for a reason.


Replace disk approach with TCP/IP for data exchange.

Wait wait wait, What is this?...

InForm's editor and the Preview form are two separate application running and exchanging data via a disk file. The Preview is constantly sending the form data back to the editor and the editor sends edits over to the Preview by writing to disk. I intend to replace that paradigm with a local TCP/IP connection between both. Under tests locally already ;-)

Woahhhh that's really smart, what do you think the benefits would be?

Just switching to a more modern approach is already a benefit, but I envision you could load more than a form at once, for one thing (which would make sense considering the planned enhancement described in #20).
I also imagine that the burden on the disk is going to be magnitudes smaller this way, of course - especially considering the many reads/writes per minute that the editor currently has to perform. The first versions of InForm had issues with flushing to disk on Linux machines, which I had to circumvent by opening and close the exchange files multiple times a second.
Now I will consider this switch a success if the end-user ends up not noticing that I've changed it at all. The idea is to make it as seamless as possible.

Effective for Beta 8 starting with 420c0f6e792c23ba6522b812d17aff7b08788526


Inconsistent use of letter case

The coexistence of names like showt and printT is really bothering and confusing. It is an absence of a convention across a single library. It would be so much better if you just picked either one and followed thru with the rest of the library.
I mean it should be either showt and printt or showT and printT. A chaotic mixture of counterconventions is a usability killer.

BTW, the name showt follows none of the existing Haskell conventions. If you were following the truely awkward as per my taste, but at least standard naming convention of fmap, mappend, that would make the function name tshow.
Overall there's clearly a lot of issues with the naming in this library. My suggestion is to provide full names (showText, showLazyText) and leave it to e.g., wrapper libraries, to come up with shorthands and other usability optimizations. That way you'll at least take off the naming optimization problem from yourself altogether.

Hey there. I apologize that the naming conventions are haphazard—trying to come up with satisfying names is the most challenging part of this library.
I'm open to changing some names, but I would like to point out that there is some precedence for the showb/showt/showtl naming convention that I've adopted. Namely, I took it directly from Text.Show in base, where certain show-related functions that return ShowS have an s to mark them as such (e.g., shows, showsPrec).
Admittedly, Text.Show isn't entirely self-consistent, since there also exist showChar and showString, which return ShowS but don't follow the -s suffix convention. But the spirit of the idea seems noble, and text-show's spiritual predecessor bytestring-show also uses a similar -p suffix convention, so I decided to adopt that naming philosophy.
Unfortunately, as you've pointed out, this becomes less satisfying linguistically when you try to tack on suffixes to functions that already end with several consonants. For example, print becomes printtl, which doesn't English well. My attempt to mitigate this was to capitalize the suffixes as necessary to aid in pronunciation. Now we've got a garbled mess of naming conventions.
So what can we do? Some options include:

Spelling everything out, e.g., showb becomes showBuilder, printtl becomes printTextLazy, etc. Personally, I'm disinclined towards this option since it adds a lot more keystrokes for common tasks, e.g., this:
data Example = Example Int Int
instance TextShow Example where
    showb (Example i1 i2) = showb i1 <> showbSpace <> showb i2

becomes this:
data Example = Example Int Int
instance TextShow Example where
    showBuilder (Example i1 i2) = showBuilder i1 <> showBuilderSpace <> showBuilder i2

Turn the suffixes into prefixes, e.g., printtl becomes tlprint. IMO, this doesn't really change much—it just bikesheds about the placement of the keywords. For every function like fmap and mappend, there's also functions like liftA and mapM, so Haskell itself doesn't seem to have made up its mind about which is better :)

Uniformly make all suffixes lowercase. This makes things more consistent without breaking the API too much, but there's also the issue of consonant collision in functions like printtl.

Uniformly make all suffixes uppercase. This makes it easier to predict what to type, and doesn't deviate too much from the convention in Text.Show in base. It would break the API significantly in that many users would have to redefine their TextShow instances (since showb becomes showB) if they're not using Template Haskell or GHC generics.

Personally, if I had to change something, I'd most inclined toward option 4. Then again, you're pretty much the user of text-show at this point (that I'm aware of), so if you feel that 4 would be unacceptable, please speak up.

you're pretty much the user

There's almost 2k Hackage downloads, so I'm hardly the only user :)

Spelling everything out, e.g., showb becomes showBuilder, printtl becomes printTextLazy, etc.

I recommend that option, since it's neutral concerning the naming conventions, and relieves you as the maintainer from the problem of naming conventions altogether. Anyone who wants shorter versions can release a package with aliases or declare them in his project internally.
This package has enough of other concerns besides naming conventions.

Uniformly make all suffixes uppercase.

If you're still determined to go with shortcuts, that one is the most viable option IMO.

I suspect a lot of those downloads are due to Travis-CI, but now that I check, http://packdeps.haskellers.com/reverse/text-show does show that other people are using it! I should probably break stuff sooner than later, in that case :)

If you're still determined to go with shortcuts, that one is the most viable option IMO.

Then I'll probably do just that. I want to try and complete some other big changes before a text-show-3.0 release, so this will probably need to wait a bit.

While we're at it, I believe, the word order is also an issue. "LazyText" makes more sense then "TextLazy", and hence the "LT" abbreviated form instead of "TL" and so on. I'm hardly alone in that, e.g. "string-conversions", "basic-prelude". Also, according to Hayoo, the order I suggest is definitely a winner:
results of "LazyText" vs results of "TextLazy".
I suspect you were strayed off by the namespaces in the "text" library, but this really doesn't have anything to do with the name of the thing. That is, besides the namespacing being quite questionable there.

At this point, I don't think I'm going to be overhauling the naming conventions again.


How to restrict image visible area?

I have an image similar to this one - http://bl.ocks.org/mbostock/1557377 - set of circled objects on one big canvas. I want to restrict user with only one object. For this i do next steps:
1). Set appropriate zoom level to see only one entire object in viewport.
viewer = OpenSeadragon({
  ..,
  minZoomLevel: 9.375,
  ..
});

2). Move viewport to required object:
var rect = new OpenSeadragon.Rect(0.05, .73, .08, .08);
viewer.addHandler("open", function() {
  viewer.viewport.fitBounds(rect, true);
});

3). And finally add my own drag handler to restrict user:
viewer.addViewerInputHook({hooks: [
  {tracker: 'viewer', handler: 'dragHandler', hookHandler: function(event) {
    event.stopHandlers = true;
    var center = viewer.viewport.viewerElementToViewportCoordinates(event.position);
    viewer.viewport.panTo(center, true);
  }}
]});

But when i drag an image it moves almost random. So how i can implement my own correct drag handler?

Do you want to disable all panning? If so, you can use the mouseNavEnabled option (set it to false).

No. I want to write my own drag handler which will disallow to move images beyond required area. For example area restricted by rect variable

Ok, we do something similar in this demo:
http://iangilman.com/osd/test/demo/m2/
...when you go into Page mode. The code for that is here:
https://github.com/openseadragon/openseadragon/blob/master/test/demo/m2/js/main.js#L296
That doesn't use ViewerInputHook...if you want help with that plugin, you might file an issue on its repo:
https://github.com/msalsbery/OpenSeadragonViewerInputHook

Looks like this is it. Thank you!


Change godotscript grammar repository

changed the gdscript grammar provider from https://github.com/beefsack/GDScript-sublime to https://github.com/godotengine/godot-vscode-plugin to fix syntax highlighting as discussed in the issue #4974
closes #4974
Description

Checklist:

[ ] I am associating a language with a new file extension.

[ ] The new extension is used in hundreds of repositories on GitHub.com

Search results for each extension:

https://github.com/search?utf8=✓&type=Code&ref=searchresults&q=extension%3AFOOBAR+KEYWORDS+NOT+nothack

[ ] I have included a real-world usage sample for all extensions added in this PR:

Sample source(s):

[URL to each sample source, if applicable]

Sample license(s):

[ ] I have included a change to the heuristics to distinguish my language from others using the same extension.

[ ] I am adding a new language.

[ ] The extension of the new language is used in hundreds of repositories on GitHub.com.

Search results for each extension:

https://github.com/search?utf8=✓&type=Code&ref=searchresults&q=extension%3AFOOBAR+KEYWORDS+NOT+nothack

[ ] I have included a real-world usage sample for all extensions added in this PR:

Sample source(s):

[URL to each sample source, if applicable]

Sample license(s):

[ ] I have included a syntax highlighting grammar: https://github-lightshow.herokuapp.com/
[ ] I have updated the heuristics to distinguish my language from others using the same extension.

[ ] I am fixing a misclassified language

[ ] I have included a new sample for the misclassified language:

Sample source(s):

[URL to each sample source, if applicable]

Sample license(s):

[ ] I have included a change to the heuristics to distinguish my language from others using the same extension.

[x] I am changing the source of a syntax highlighting grammar

Old: https://github.com/beefsack/GDScript-sublime
New: https://github.com/godotengine/godot-vscode-plugin

[ ] I am updating a grammar submodule

[ ] I am adding new or changing current functionality

[ ] I have added or updated the tests for the new or changed functionality.

[ ] I am changing the color associated with a language

[ ] I have obtained agreement from the wider language community on this color change.

[URL to public discussion]
[Optional: URL to official branding guidelines for the language]

Thanks!


Feature: Improve documentation to save maintainer's time on dealing with pinned dependencies alerts

Is your feature request related to a problem? Please describe.
It is not clear to the user how to handle the security alert on dockerfile or bash files regarding some package managers.
I've done some research myself and most of them I wasn't able to even determine if they allow a pinned by hash install or not.
Some examples I've look into were:

yum - it is impossible to pin by hash (AFAIK).
wget - it is impossible to pin by hash (AFAIK).
curl -  it can be possible to pin by hash (AFAIK).

Describe the solution you'd like
To make it easier for the user to remediate Pinned Dependencies alert, we could cover in the documentation the most common package managers and whether it is possible to pin them by hash or not.
It would save maintainers time on useless trying to hash pin a package manager that does not allow it.
And, in these cases when it is impossible to pin by hash, we should suggest they dismiss the alert on github since it cannot be fixed.
Additional context
Although I didn't find a way to pin by hash yum installs, it seems there is some kind of digest verification at least when it is installing local rpm packages (that's what I could get from this link)
Curl seems to have the --pinnedpubkey option but I'm not sure if it would really be considered pinned by hash.

A (clunky) idea would be to check for something like
curl https://www.foo.com -o my_artifact.jar  # or equivalent for wget/yum
echo "1234abcd my_artifact.jar" | sha256sum -c
# or
sha256sum -c hashes.txt
# we'd need to check that hashes.txt actually includes all the downloaded files

That is: make sure they download the file and then check its hash.


Bug: cron page does not work and is not linked in menu

the page /ui/cron/ is not shown in the menu and clicking the delete button does not work (cannot remove ids update entry).

It's disabled for a reason. ;) We will make it public some time during the 16.1.x series.

Items from other application components are locked, but can be disabled. The other component, in this case ids, still has a reference to this object.


Error forever missing

I have tried over and over to do the "sudo npm install forever -g"  so that forever would be installed and quit making the GUI stop.
Any Ideas would be appreciated...
/bin/sh: 1: ./bin/dhcpd-pools: Permission denied
child_process.js:674
throw err;
^
Error: Command failed: ./bin/dhcpd-pools -c /etc/dhcp/dhcpd.conf -l /var/lib/dhcp/dhcpd.leases -f j -A -s e
/bin/sh: 1: ./bin/dhcpd-pools: Permission denied
DO I HAVE TO INSTALL POOLS ???
npm ERR! code 1
npm ERR! path /opt/glass-isc-dhcp
npm ERR! command failed
npm ERR! command sh -c node ./bin/www
./glass_start.sh: line 3: /usr/bin/forever: No such file or directory

Try "/opt/glass-isc-dhcp/node_modules/forever/bin/forever" path instead "/usr/bin/forever"
crontab:
@reboot cd /opt/glass-isc-dhcp && /opt/glass-isc-dhcp/node_modules/forever/bin/forever --minUptime 10000 --spinSleepTime 10000 -a -o ./logs/glass-process.log -e ./logs/glass-error.log ./bin/www


Move to thiserror for errors

failure is leaking into the public API and forcing downstream consumers to either Box up the failure error or depend on failure if they want to explicitly handle the error.
Moreover, error types do not have any precise information in the type about what went wrong. thiserror would allow us to provide very specific error variants, as well as avoiding leaking types into the public API and letting downstream consumers handle the variants as they wish.

I have used failures too much to like it, but at the same time I became kinda skeptical of any new rust error-handling library :/
At a first glance it looks like to be a good one, but before embarking in such a big change, maybe I would wait to see if the Rust community converges on something ;)

The main issues here IMO are the inability for dependents to get more specific error messages, and leaking the failure dependency if you don't want to box everywhere. The convenience of error reporting the way its currently done in avro rs is really for applications, whereas library errors should be as specific and efficient as possible.

FWIW, failure is now officially deprecated:
https://github.com/rust-lang-nursery/failure/pull/347
With all new error handling libs being built around std::error::Error, it's not insanely important what library the community converges towards. Whether you use thiserror or any other of the new libs, other than with failure, the errors can just be converted into a common Box<dyn std::error::Error>.

The specific library doesn't matter. What matters is the way that errors are presented to dependents IMO. The way in which failure is used in avro-rs precludes dependents handling errors in a way that is appropriate for their use.

I have been following a bunch of discussions in the community and it does indeed seem that anyhow and thiserror don't have a clear path to obsolescence in front of them for now, neither there are other "big" enough players to choose from (mark my words, a new revolutionary crate will be announced the minute after I hit "Comment" 😛 ).
Agreed, let's move to thiserror and this time let's make error handling right, as @cpcloud pointed it out.


Lots of duplicate code

While looking around to find help for this: https://forum.thirtybees.com/topic/647/beesblog-module-cannot-be-installed I found that three entire modules get installed twice.
First instance appears because installing Bees Blog also installs Bees Blog Categories, Bees Blog Popular Posts and Bees Blog Recent Posts.
Seconds instance can be found inside the Bees Blog module, in modules/beesblog/widgets/
Both appear to contain identical code and views, but which one is the right one?

I figured out already : modules that are inside modules/beesblog/widgets/ are automatically installed (and re-installed if you try to suppress its)
Personnaly, I don't need all, so I just delete  inside this directory the modules I don't want, before installing the "blog module"

We could use a refactoring of this module since the original developer stole a lot of code for it. https://github.com/thirtybees/beesblog/issues/30

I'm already working on it (only for my use, much customizations)
I don't have time to commit (too much changes needed) but I can send you my code then, like that you can take ideas you want ...

Resolved by upgrading submodules to regular modules


Lazy Loading / Code Splitting breaks tree shaking

Bug report
What is the current behavior?
When a file is imported with import(), tree shaking doesn't work as expected.
If the current behavior is a bug, please provide the steps to reproduce.
Please see this repo: https://github.com/bluepnume/webpack-lazy-loading

Source: https://github.com/bluepnume/webpack-lazy-loading/tree/master/src
Dist: https://github.com/bluepnume/webpack-lazy-loading/tree/master/dist

What is the expected behavior?
There are 6 functions defined in this repo:

foo
lazyFoo
bar
lazyBar
baz
lazyBaz

I expect the following:

foo: should appear in main bundle since it's being required and called by index.js - 👍 works
lazyFoo: should be tree-shaked, not being used by anyone - 👍 works
bar: should appear in main bundle since it's being required and called by index.js - 👍 works
lazyBar: should appear in lazy bundle since it's only being used after import() - ❌ doesn't work -- it's appearing in the main bundle
baz: should appear in lazy bundle since it's only being used after import() - 👍works
lazyBaz: should appear in lazy bundle since it's only being used after import() - 👍works

The main one not working here is lazyBar. It's not being directly imported by any other file, so it should never appear in the main bundle.
It should be tree shaked from the main bundle when the tree shaker does not see import { lazyBar } anywhere in the codebase.
Other relevant information:
webpack version: 4
Node.js version: 8
Operating System: osx
Additional tools: n/a

As per Webpack scope hoisting, lazyBar() will be moved to main chunk.

@NaviMarella but isn't that incorrect? Since nothing in the main chunk (provably) needs lazyBar, and webpack/uglify can derive that?


brave-census bridge

@jorgheymans currently uses brave-instrumentation-grpc and is looking to interop with census for the grpc layer. His application architecture looks like
incoming=rest -> mid tier grpc/kafka/ldap -> outgoing=rest
So, if census-grpc uniformly handles that layer (still reporting to zipkin). Assuming brave doesn't implement the census api layer (which I suppose it could), the essence of this integration are the following:

use grpc context as brave's CurrentTraceContext so that propagation works
When reading the current trace context, look at census to see if there's an upstream span and convert that accordingly to a brave TraceContext.
When writing the current trace context, make a fake Census span which delegates to the current brave span.

In looking at census grpc instrumentation, the parent is only read (not modified), so this should work. It won't work with advanced features like brave's extra field propagation, and it won't propagate things absent in census like the parent ID. However I still think it should work somewhat.
A design note: it would be cleaner if census didn't propagate a span rather just the trace context. Since it propagates the span, we have to create a span object to integrate, which is heavier (because it is stateful type) and makes the integration approach clunky due to this (like us needing to make a more expensive fake span just to get the 'current parent' code which only reads the reference to work). If census had a mode where it only propagated the trace context (impling a recording function based on trace context internally), this integration would be neater imho.
So the alternates I'm aware of are:

brave implementing census tracer api (which makes sense if you are sending to zipkin anyway as the signal loss is the same as exporting to zipkin)
brave implementing the same grpc tracer as census (much easier, but doesn't actually integrate with census)

PS what led to this was some curiosity about latency in a gRPC app. The brave grpc integration still uses interceptor approach (as we are back compat all the way till grpc 1.3). We haven't done a grpc tracer implementation for reasons including it seems the api isn't stable yet, and maybe census integration can solve this.

Thanks for drafting your thoughts on this, as said let me know if there is something you want me to test.


feat: include typescript type definitions

Coverage remained the same at 100.0% when pulling bf4e2c0e4a557e87cfc9c7f8077799e75673f3ed on typescript-types into 355a8dee0998dad6324c7056d63ec79dd921d216 on master.

Coverage remained the same at 100.0% when pulling bf4e2c0e4a557e87cfc9c7f8077799e75673f3ed on typescript-types into 355a8dee0998dad6324c7056d63ec79dd921d216 on master.

Coverage remained the same at 100.0% when pulling bf4e2c0e4a557e87cfc9c7f8077799e75673f3ed on typescript-types into 355a8dee0998dad6324c7056d63ec79dd921d216 on master.

Coverage remained the same at 100.0% when pulling bf4e2c0e4a557e87cfc9c7f8077799e75673f3ed on typescript-types into 355a8dee0998dad6324c7056d63ec79dd921d216 on master.

Coverage remained the same at 100.0% when pulling bf4e2c0e4a557e87cfc9c7f8077799e75673f3ed on typescript-types into 355a8dee0998dad6324c7056d63ec79dd921d216 on master.


Rulesets can't have their status set to be default

What happened?
When creating a ruleset, or attempting to override a ruleset, the status input should have one of three values:

"enabled"
"disabled"
"" (empty string, meant to signify "leave as the default value")

However, when attempting to use the following:
new Ruleset(`CloudflareManagedRuleset-${zoneId}`, {
        zoneId: zoneId,
        kind: "zone",
        name: "managedruleset",
        phase: "http_request_firewall_managed",
        rules: [{
            action: "execute",
            actionParameters: {
                // Cloudflare Managed Ruleset
                id: "efb7b8c949ac4650a09736fc376e9aee",
                version: "latest",
                overrides: {
                    action: "log",
                    status: "", // error if not set to "enabled" or "disabled", i want it to be "default"
                    rules: [{
                        // Log4j Body
                        id: "0c054d4e4dd5455c9ff8f01efe5abb10",
                        status: "disabled"
                    }]
                }
            },
            expression: "true",
            enabled: true,
            description: "Execute Cloudflare Managed Ruleset on my zone-level phase entry point ruleset"
        }]
    });

The error message that is coming back is:
error: cloudflare:index/ruleset:Ruleset resource 'CloudflareManagedRuleset-353614400ad3094b8405f4732c40405d' has a problem: expected rules.0.action_parameters.0.overrides.0.status to be one of [enabled disabled], got . Examine values at 'Ruleset.Rules[0].ActionParameters[0].Overrides[0].Enabled'.

Expected Behavior
The ruleset would be updated to use the default values set by CloudFlare.
Steps to reproduce
See code snippet above
Output of pulumi about
❯ pulumi about
CLI
Version      3.55.0
Go Version   go1.20
Go Compiler  gc

Host
OS       darwin
Version  12.6.3
Arch     arm64

Backend
Name           pulumi.com
URL            https://app.pulumi.com/************
User           ************
Organizations  ************

Pulumi locates its logs in /var/folders/_z/w6qmwg8912d3h1_hn6mt0kmh0000gp/T/ by default
warning: Failed to read project: no Pulumi.yaml project file found (searching upwards from /Users************/Repos/************/infra-automation/global-stack). If you have not created a project yet, use `pulumi new` to do so: no project file found
warning: Failed to get information about the current stack: no Pulumi.yaml project file found (searching upwards from /Users/************/Repos/************/infra-automation/global-stack). If you have not created a project yet, use `pulumi new` to do so: no project file found

Additional context
The TF provider docs suggest that an empty string should be acceptable: https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/ruleset#status
And I can't find anything in the TF provider that would suggest it's limiting the values to be enabled or disabled
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

We are unable to repro on the specific code provided. We're planning to get access to a cloud flare account that will enable us to reproduce and resolve the issue.

Update: We have succeeded in replicating the issue on our and are working on a fix. The basic problem goes like this:
The cloudflare terraform provider distinguishes between an absent value // status = "" and an empty value status = "". In terraform as in pulumi, setting status = "" results in the error shown by the OP.
When a value isn't present in pulumi, the bridge receives the default value for its type. In the case of status, that is the empty string. This causes the error.
There are two possible fixes we are exploring in the short term:

Update the bridging logic for this type to remove empty values of status.
Update our fork to handle the "" value correctly.


FermionicSumOp without primitive

Migrated from 'https://github.ibm.com/BPA/qiskit-nature'.
Creator: '@ikkoham'

Summary
Jupyter note.
https://gist.github.ibm.com/Ikko-Hamamura1/27c70e3d6c7e8c9b383dd04c1a0bd1b0

Creator: '@ikkoham'
I've separated this Pull Request to #23. I will rebase once #23 is merged.

Creator: '@ikkoham'
I've separated this Pull Request to #23. I will rebase once #23 is merged.


React Native Web support without Next.js

Description of the feature
👋 Hi Cedric, and thank you for putting together this example - it's a real help to know how to configure all these tools together.
I'm curious whether you've been able to get web support without using Next. As far as I can tell, this hasn't yet been implemented within this repo. After pnpm install and pnpm build, I'll run pnpm --filter @acme/mobile-app web it prompts me to add the base webpack config.
It looks like you're trying to use web support but don't have the required dependencies installed.

Please install<EMAIL_ADDRESS>by running:

npx expo install<EMAIL_ADDRESS>
If you're not using web, please ensure you remove the "web" string from the platforms array in the project Expo config

After adding the above, running pnpm --filter @acme/app-mobile run web seems happy from the CLI, but when viewing in the browser I get a blank screen. It shows me errors in the console, which when looking at the bundle source seems to indicate a webpack misconfiguration.

Honestly, I wouldn't know where to start amending the Webpack configuration for expo. I would happily pay you for your help getting this configuration to work if that's any consolation.
This is something I really want to get working, although perhaps I'm seeing it from the wrong angle. I'm aware that Next.js has it's perks, but I'm curious for the reason in this monorepo why Next is used rather than Expo's built-in web bundle tooling? It would be great if it demonstrated both cases.
Motivation
This removes the need to maintain two separate packages, separated by pure-web and native bundles.

Hey @midzdotdev! Thanks, I'm happy to keep this example working for everyone as an example of "how you could configure" things :)
As for the choice of Next over Expo Web (with webpack), it's simply because Next is more used than Expo Web (with webpack).
Currently, it seems that we might be transitioning away from Webpack. It has a lot of issues that are really hard to solve. One thing you could try though is using Metro web instead :) It's still in development, and might not be 100% perfect, but Expo Router is currently pushing that really hard.
To try Expo Web (metro), you need to set expo.web.bundler = "metro" in your app.json configuration. This enables the same stuff that we use for Expo Router.
Hope this helps!


error"python preparation_york.py"    KeyError:'line'

here are some errors

how to solve it?

I find the data struct is different from described on website.
So you read like this:  'P1020171/P1020171.jpg' and 'P1020171/P1020171LinesAndVP.mat'?

I find the data struct is different from described on website.
So you read like this: 'P1020171/P1020171.jpg' and 'P1020171/P1020171LinesAndVP.mat'?
Also key_word "lines" is in *LinesAndVP.mat.

yes，it is different from described on website.
It's the same with  'P1020171/P1020171.jpg' and 'P1020171/P1020171LinesAndVP.mat'
The temporary solution is not to execute “python preparation_york.py”
Do you have some good ideas?

I find the data struct is different from described on website.
So you read like this: 'P1020171/P1020171.jpg' and 'P1020171/P1020171LinesAndVP.mat'?
Also key_word "lines" is in *LinesAndVP.mat.

yes，it is different from described on website.
It's the same with 'P1020171/P1020171.jpg' and 'P1020171/P1020171LinesAndVP.mat'
The temporary solution is not to execute “python preparation_york.py”
Do you have some good ideas?
I modified code in preparation_york.py like :
$ test_lst = glob.glob(osp.join(data_root,'P*'))
$ test_lst = [osp.basename(f) for f in test_lst]
$def load_datum(filename):
$    image = cv2.imread(osp.join(data_root,filename,filename)+'.jpg')
$    lsgs = sio.loadmat(osp.join(data_root,filename,filename)+'LinesAndVP.mat')['lines']
mainly changed target pic path and mat path. Then run OK

I find the data struct is different from described on website.
So you read like this: 'P1020171/P1020171.jpg' and 'P1020171/P1020171LinesAndVP.mat'?
Also key_word "lines" is in *LinesAndVP.mat.

yes，it is different from described on website.
It's the same with 'P1020171/P1020171.jpg' and 'P1020171/P1020171LinesAndVP.mat'
The temporary solution is not to execute “python preparation_york.py”
Do you have some good ideas?
I modified code in preparation_york.py like :
$ test_lst = glob.glob(osp.join(data_root,'P*'))
$ test_lst = [osp.basename(f) for f in test_lst]
$def load_datum(filename):
$    image = cv2.imread(osp.join(data_root,filename,filename)+'.jpg')
$    lsgs = sio.loadmat(osp.join(data_root,filename,filename)+'LinesAndVP.mat')['lines']
mainly changed target pic path and mat path. Then run OK

Thanks for your reply.
when I changed the codes like what you left here,
Something still goes wrong.

So could I have your 'preparation_york.py'?
if possible,my email adress is<EMAIL_ADDRESS>

I find the data struct is different from described on website.
So you read like this: 'P1020171/P1020171.jpg' and 'P1020171/P1020171LinesAndVP.mat'?
Also key_word "lines" is in *LinesAndVP.mat.

yes，it is different from described on website.
It's the same with 'P1020171/P1020171.jpg' and 'P1020171/P1020171LinesAndVP.mat'
The temporary solution is not to execute “python preparation_york.py”
Do you have some good ideas?
I modified code in preparation_york.py like :
$ test_lst = glob.glob(osp.join(data_root,'P*'))
$ test_lst = [osp.basename(f) for f in test_lst]
$def load_datum(filename):
$    image = cv2.imread(osp.join(data_root,filename,filename)+'.jpg')
$    lsgs = sio.loadmat(osp.join(data_root,filename,filename)+'LinesAndVP.mat')['lines']
mainly changed target pic path and mat path. Then run OK

Thanks for your reply.
I did it like what you had done.
It's ok now.Thanks!!
My requirement is to train the images in outside scenes.

I read the  "afm_atrous.yaml" and "readme.md"，only "wireframe" can train,the "york" folder can only be tested.
The "wireframe" folder have the "train.json" ,while the "york" folder didn't
Do you have some ideas? thank you!

I find the data struct is different from described on website.
So you read like this: 'P1020171/P1020171.jpg' and 'P1020171/P1020171LinesAndVP.mat'?
Also key_word "lines" is in *LinesAndVP.mat.

yes，it is different from described on website.
It's the same with 'P1020171/P1020171.jpg' and 'P1020171/P1020171LinesAndVP.mat'
The temporary solution is not to execute “python preparation_york.py”
Do you have some good ideas?
I modified code in preparation_york.py like :
$ test_lst = glob.glob(osp.join(data_root,'P*'))
$ test_lst = [osp.basename(f) for f in test_lst]
$def load_datum(filename):
$    image = cv2.imread(osp.join(data_root,filename,filename)+'.jpg')
$    lsgs = sio.loadmat(osp.join(data_root,filename,filename)+'LinesAndVP.mat')['lines']
mainly changed target pic path and mat path. Then run OK

Thanks for your reply.
I did it like what you had done.
It's ok now.Thanks!!
My requirement is to train the images in outside scenes.

I read the "afm_atrous.yaml" and "readme.md"，only "wireframe" can train,the "york" folder can only be tested.
The "wireframe" folder have the "train.json" ,while the "york" folder didn't
Do you have some ideas? thank you!
On the way of training .

I find the data struct is different from described on website.
So you read like this: 'P1020171/P1020171.jpg' and 'P1020171/P1020171LinesAndVP.mat'?
Also key_word "lines" is in *LinesAndVP.mat.

yes，it is different from described on website.
It's the same with 'P1020171/P1020171.jpg' and 'P1020171/P1020171LinesAndVP.mat'
The temporary solution is not to execute “python preparation_york.py”
Do you have some good ideas?
I modified code in preparation_york.py like :
$ test_lst = glob.glob(osp.join(data_root,'P*'))
$ test_lst = [osp.basename(f) for f in test_lst]
$def load_datum(filename):
$    image = cv2.imread(osp.join(data_root,filename,filename)+'.jpg')
$    lsgs = sio.loadmat(osp.join(data_root,filename,filename)+'LinesAndVP.mat')['lines']
mainly changed target pic path and mat path. Then run OK

Thanks for your reply.
I did it like what you had done.
It's ok now.Thanks!!
My requirement is to train the images in outside scenes.

I read the "afm_atrous.yaml" and "readme.md"，only "wireframe" can train,the "york" folder can only be tested.
The "wireframe" folder have the "train.json" ,while the "york" folder didn't
Do you have some ideas? thank you!
On the way of training .

okay , I'm waiting for your reply~
If possible,My email is<EMAIL_ADDRESS>We can email each other~

I find the data struct is different from described on website.
So you read like this: 'P1020171/P1020171.jpg' and 'P1020171/P1020171LinesAndVP.mat'?
Also key_word "lines" is in *LinesAndVP.mat.

yes，it is different from described on website.
It's the same with 'P1020171/P1020171.jpg' and 'P1020171/P1020171LinesAndVP.mat'
The temporary solution is not to execute “python preparation_york.py”
Do you have some good ideas?
I modified code in preparation_york.py like :
$ test_lst = glob.glob(osp.join(data_root,'P*'))
$ test_lst = [osp.basename(f) for f in test_lst]
$def load_datum(filename):
$    image = cv2.imread(osp.join(data_root,filename,filename)+'.jpg')
$    lsgs = sio.loadmat(osp.join(data_root,filename,filename)+'LinesAndVP.mat')['lines']
mainly changed target pic path and mat path. Then run OK

Thanks for your reply.
I did it like what you had done.
It's ok now.Thanks!!
My requirement is to train the images in outside scenes.

I read the "afm_atrous.yaml" and "readme.md"，only "wireframe" can train,the "york" folder can only be tested.
The "wireframe" folder have the "train.json" ,while the "york" folder didn't
Do you have some ideas? thank you!
On the way of training .

okay , I'm waiting for your reply~
If possible,My email is<EMAIL_ADDRESS>We can email each other~


 Remove DX9 Support and update IsLaneMinion offset.

How can i remove DX9 support and update IslaneMinion cuz i looked for a while and still have no clue how to do it

R3nzSkin removed dx9 support.

Mee too

me too. Did you manage to solve it?

me too. Did you manage to solve it?

Like you have no see the photo ?

?????????, I saw it, but I didn't understand it. I already downloaded this version and when I click start, nothing happens.

me too. Did you manage to solve it?

Like you have no see this photo before your post

I saw it, but I didn't understand it. I already downloaded this version and when I click start, nothing happens.

Read 14.9 patch notes and also it was also this when Vanguard was only in PBE

me too. Did you manage to solve it?

Like you have no see this photo before your post

I saw it, but I didn't understand it. I already downloaded this version and when I click start, nothing happens.

me too. Did you manage to solve it?

Like you have no see this photo before your post

I saw it, but I didn't understand it. I already downloaded this version and when I click start, nothing happens.

Read 14.9 patch notes and also it was also this when Vanguard was only in PBE

me too. Did you manage to solve it?

Like you have no see this photo before your post

I saw it, but I didn't understand it. I already downloaded this version and when I click start, nothing happens.

Read 14.9 patch notes and also it was also this when Vanguard was only in PBE

me too. Did you manage to solve it?

Like you have no see this photo before your post

I saw it, but I didn't understand it. I already downloaded this version and when I click start, nothing happens.

Read 14.9 patch notes and also it was also this when Vanguard was only in PBE

So does that mean the era of lol skins is over?

me too. Did you manage to solve it?

Like you have no see this photo before your post

I saw it, but I didn't understand it. I already downloaded this version and when I click start, nothing happens.

Read 14.9 patch notes and also it was also this when Vanguard was only in PBE

So does that mean the era of lol skins is over?

No over this tool work with Vanguard


Validate Jira 9 release - EAP

EAP is here https://www.atlassian.com/software/jira/download-eap?_ga=2.227824606.291373623.1647880020-2043599991.1647029962
Looking for a smoke test to ensure plugin is still compatible. No known big backwards breaking changes.

Hi @knoppanthony
We will perform the checks and let you know.

@knoppanthony I have tested the plugin and can confirm that it's fully compatible with the Jira EAP version. Please note that users will have to install it manually as the version is not set in the marketplace listing. The latest version of the addon can be downloaded from here

Hi team, do you have any ETA on bumping the compatibility of this plugin on MPAC? Thanks!


Only add entries to database that have not been added with --resume tag

The spatial transformer currently adds all the entries that it is keeping track of with the datatracker, but that does not make sense for when the --resume tag is added to the command for the failsafe. Only add the entries that were not already processed because they were added at the time of the failure.

A change has been written in, it needs a bit more testing to make sure it works nd interacts with how the layers are added to the gdb and the database

refer to comment in another issue https://github.com/cat-cfs/twobilliontoolkit/issues/18#issuecomment-2145579940


react-transform-catch-errors and webpack-dev-server

I made redbox-react work using the method from react-transform-boilerplate, very similar to your example.
Then I tried to make it work using webpack-dev-server (still using babel-plugin-react-transform and react-transform-catch-errors). While hot reloading works fine, catching the errors and showing them with redbox-react does not.
I have no idea if this is an issue with redbox-react or with react-transform-catch-errors not actually catching any errors or not giving them to redbox-react or something? Does this actually depend on webpack-hot-middleware to work?
I have an example project here: https://github.com/kevinrenskers/react-transform-webpack-dev-server. I was hoping that maybe you could take a look and see what's wrong with this approach. Of course it works fine when I don't use webpack-dev-server but instead use express and webpack-hot-middleware and all that, but it feels a bit complicated to me, a lot of moving parts and dependancies. Using just webpack-dev-server, configured from the webpack config file, saves some dependancies and an external devServer.js file.

@kevinrenskers did you ever find a solution to this as I've ran into the same problem -- works fine using webpack-hot-middleware but not with webpack-dev-server?

Nope :(

I've also been trying to get this to work without webpack-hot-middleware but running into the same issue. I am able to get hot reload with webpack-dev-server using react-transform-hmr but no luck with react-transform-catch-errors.

observed the same issue as well :(

I am also having the same issue, doesn't work with webpack-dev-server

I tried this project and it works just fine. I think there may be confusion as to what is handled by react-transform-catch-errors, and what is not.
Errors handled by React Transform Catch Errors

Runtime errors inside render() method or methods it calls

Errors handled only by Webpack Hot Middleware

Syntax errors

That's it! So if you mistype props as shprops in your render() method, react-transform-catch-errors will catch it, but it is not able to catch syntax errors or runtime errors outside render().
The syntax errors won't be caught with WebpackDevServer because it's Webpack Hot Middleware that catches them. And the overlay it displays is different from (and unrelated to) redbox-react.
Hope it helps!


Refactor Makefile: only list the spec names once

Issue
Every time I added a new spec, I forget to add it to the linter and test coverage scope.
How did I fix it
Add a list ALL_EXECUTABLE_SPECS = phase0 altair bellatrix capella deneb. So we only have to update this variable for future specs.
Note: we still have to manually update MARKDOWN_FILES content because the paths differ.

I just found that MARKDOWN_FILES is only for check_toc and all the files under specs are ToC-checked. So we can wild-card all files under specs now.


Add zeppelin-solidity support

Currently, the artifact isn't able to discern the sourcePath of zeppelin contracts.
This PR fixes it.
Also, updated the README.md a bit

Can you please resolve conflicts and remove package json changes?

@nakajo2011 cherrypicked commits. Closing for now.


Add support for null and undefined variable values

NULL is a valid variable value, which translates to an empty string for strings, 0 for numbers and false for booleans. Alternatively, scriban templates can explicitly check for NULL values.
UNDEFINED variables are invalid variables. After resolving the variables, if any variable is UNDEFINED, then an error should be thrown. UNDEFINED is useful to define a variable at a root-level folder, but we don't have a value at that level.
In the variables.ini file, we can define these values with special keywords:
[Section]
ANullValue = _NULL_
AnUndefinedValue = _UNDEFINED_

Implemented support for undefined variables with _UNDEFINED_

Cannot find a valid usage for NULL. Closing this issue with only UNDEFINED variables implemented.
We'll revisit NULL support in the future, if needed.


Unittest and crypto should be dev dependencies.

The unittest and crypto packages are only used in tests, so these should be made dev dependencies. This will allow projects depending on base32 to use more recent versions of unittest and crypto without causing a dependency conflict in pub.

Awesome, thanks for the change. I had completely forgotten about the dev_dependencies stuff. I made that pubspec before that was introduced. Merging and pushing shortly.


Add completion for --pod in run and create

Signed-off-by: haircommander<EMAIL_ADDRESS>

LGTM

@rh-atomic-bot r+

Travis died unhappily.  Doesn't look related, but a time-out test is the python tests that I've not seen before.


Require that discussions-to points to Ethereum Magicians

As opposed to a GitHub issue or back to the PR itself.

References:

https://github.com/ethereum/EIPs/pull/2917#issuecomment-683444423
https://github.com/ethereum/eipv/issues/10

I don't think Ethereum Magicians should be a requirement? It can't be the issue itself, but there's no requirement that it be any one forum.

The latest agreement among editors (after many months of discussion) is that all discussion links should be on Ethereum Magicians.  The primary argument is that you can login to Ethereum Magicians via GitHub account with minimal permissions, so there isn't any reason someone wouldn't be able to post there and it keeps discussion in one cohesive place.
There is an outstanding issue to remove the edit timer on Ethereum Magicians, and we should get that fixed prior to implementing this.

You can also log on to a variety of other forums via GitHub, including GitHub issues.
This proliferation of unwritten rules is making the EIP process needlessly bureaucratic and difficult to navigate. Why aren't these proposed as amendments to EIP 1, at least?

Why aren't these proposed as amendments to EIP 1, at least?

Because we are woefully understaffed and things often don't make it to EIP-1 like they should.  Pull requests very welcome!

You can also log on to a variety of other forums via GitHub

This doesn't solve the problem of consistency across EIPs and simplicity of implementation (editors don't need to make judgement calls on what discussions-to locations are appropriate).

including GitHub issues

We are wanting to use GitHub issues for tracking EIP process changes/improvements/suggestions.  This is easier/simpler when the issues are full of discussion links for various EIPs.

Because we are woefully understaffed and things often don't make it to EIP-1 like they should. Pull requests very welcome!

I'm not sure how I could do this, since these rules seem to only exist in the heads of a few EIP editors.
How much editor time is wasted explaining these unwritten rules to people when they unwittingly violate them?

This doesn't solve the problem of consistency across EIPs and simplicity of implementation (editors don't need to make judgement calls on what discussions-to locations are appropriate).

Why is it important that all EIPs have their discussions in the same place?
Are you dealing with a lot of users trying to use forums other than Ethereum Magicians? If so, doesn't that tend to indicate they're not being well served by the current system? If not, what purpose does this new rule serve?
One example I would love to see become a best-practice that this rule prohibits is linking to an issue tracker as the discussions-to URL; this permits actually tracking individual queries and proposed changes and closing them out when they're implemented, which reduces the probability of feedback being accidentally forgotten and should lead to more robust EIPs.

We are wanting to use GitHub issues for tracking EIP process changes/improvements/suggestions. This is easier/simpler when the issues are full of discussion links for various EIPs.

I assume you meant to say this is easier/simpler when the issues are not full of discussion links. Isn't this what tags are for, though? You could also use a separate repo for meta-discussion.

TL;DR: The best way to get better rules is to figure out how to get more active editors.  Understaffing is an underlying motivation behind many rules we have.

I'm not sure how I could do this, since these rules seem to only exist in the heads of a few EIP editors.

I just meant you are welcome to create a PR to update EIP-1 with this rule.  😄

How much editor time is wasted explaining these unwritten rules to people when they unwittingly violate them?

Much!  We definitely should get better at updating EIP-1 with new rules.  It is one of the tasks that often falls by the wayside when understaffed though.

The underlying theme behind a lot of the recent rule changes is that we are woefully understaffed.  One of the major driving forces behind most rules we create is reducing editor workload.  In the case of discussions-to, editors having one less thing they have to review decreases editor workload.  The way to remove this work is by having automated checks against it.  To achieve this, we have 2 options:

Allow any HTTP link.
Allow only one specific link type.

We could achieve this motivating goal with (1), but it results in people putting discussion-to links all over the place like Twitter, Reddit, Pull Requests, etc.  (2) on the other hand gives us a very easy to implement automated check that reduces editor workload while maintaining some level of consistency and quality in EIPs.
One could argue, "well, you can allow Ethereum Magicians + GitHub Issues" or "Ethereum Magicians + X, Y, and Z", but now we need to maintain a labeling system on the issues which is "more work" and deal with debates around which discussion targets should be allowed and which shouldn't.  All of these things are individually small, but they add up to a non-trivial amount of work.  Also, I do think there are benefits to consolidating discussion in a consistent place, though I can appreciate that those benefits are marginal.
If we had more people working on the EIP Editing process there would be a whole lot more good options available to us like maintaining a whitelist, individually gauging and curating each discussions-to location, doing much more complicated/fancy things with issue tracking systems, etc.  As soon as we have ample people regularly doing EIP Editing I would become much more open to all of these options.  At the moment though, we have a skeleton crew and every little bit of automation we can add (without huge amounts of engineering effort) is another step toward having an EIP process that is functional and away from a process that is completely defunct (like it was for a year or two a while back, where people's EIPs would sit for over a year awaiting editor review).

At the risk of derailing this discussion, ideally I'd like to see discussions-to only point to places where regular backups are taken and can be replicated by any interested party. Something like gollum perhaps?

@SamWilsn Does Discourse not have a system in place for backups?  Or is your concern that those backups are not in some open/portable format?

Discourse is fine too! Are there publicly available backups for the Ethereum Magicians instance, and scripts to restore it?

This is an excellent question for the Ethereum operations team.  @pooja do you know who we bring into this conversation who would know?

I think you're looking for another Pooja (Pooja Ranjan)
On Sun, Feb 27 2022 at 23:38, Micah Zoltu < @.*** > wrote:

This is an excellent question for the Ethereum operations team. @pooja (
https://github.com/pooja ) do you know who we bring into this conversation
who would know?
—
Reply to this email directly, view it on GitHub (
https://github.com/ethereum/eipv/issues/43#issuecomment-1053880982 ) , or unsubscribe
(
https://github.com/notifications/unsubscribe-auth/ABLH2S4OETL2D4U6GLH67JTU5L32TANCNFSM5M3L66ZQ
).
Triage notifications on the go with GitHub Mobile for iOS (
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
) or Android (
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub
).
You are receiving this because you were mentioned. Message ID: <ethereum/eipv/issues/43/1053880982
@ github. com>

I hope the editing timer issue can be looked into by the FEM team. Adding @jpitts to weigh in!

I think you're looking for another Pooja (Pooja Ranjan)

Yes, sorry!  I edited my comment immediately after submitting, I was hoping an email notification wouldn't go out but alas, I was not quick enough.  😢

Discourse is fine too! Are there publicly available backups for the Ethereum Magicians instance, and scripts to restore it?

Last I checked, Discourse supports manual S3 backups with a provided frequency
For automated backups, I found this bash script picked from discussion here
@jpitts thoughts?


Posting Reportback to API does not store source

BUG
Current Behavior

Neither the dosomething_reportback or dosomething_reportback_file tables contain a source column, which means we're not tracking the platform a Reportback is submitted for -- even though we're sending a source value when posting from the mobile app.

The campaigns/:id/reportback endpoint calls dosomething_reportback_save, which calls dosomething_reportback_set_properties, which doesn't check for a source  -- it wouldn't have a column to set it to.. unless we hijack the dosomething_reportback_files.review_source column. That feels quite 😷  but a little less than work than creating a new column -- plus would it go on the Reportback or the Reportback Files table?
Desired Behavior

Store the posted Reportback source, either in DS Reportback or DS Reportback Files

Why This Matters
Don't have a clean (or any?) way to tell if a Reportback was submitted via mobile app, web, or SMS. I think the hack we used (and likely still use?) is checking the IP in remote_addr for a Mobile Commons IP (cc @jonuy )

I was just talking to @Bladt about this yesterday!

I talked to @Bladt about this just a couple hours ago! Being able to tell if RBs are coming from the mobile apps is a key data point that has lots of juicy implications. Also useful to formalize the SMS procedure and future-proof for other platforms.

One hack that seems a little smaller 👕  than adding a new column(s) to the DS Reportback table is to store the newly created Reportback ID in Northstar, at least to associate the source for both letsdothis_ios and mobileapp_android

Since these requests are being proxied through Northstar, we could likely filter remote_addr by Northstar's IP. We could also (with potentially less fidelity) use the StatHat stat for that route.


Add Support for primitives in let parameters

https://github.com/GuilhE/KMP-ComposeUIViewController/blob/d77607d5fbab8a525b5e5d74171f73a1f625a563/kmp-composeuiviewcontroller-ksp/src/main/kotlin/com/github/guilhe/kmp/composeuiviewcontroller/ksp/Processor.kt#L127
Add support for primitive types like Int to be used in Callbacks
(Int -> KotlinInt in Representable code)
Without that when adding a parameter like (Int) -> Unit, in Swift it will result the following error
Cannot convert value of type '(Int) -> Void' to expected argument type '(KotlinInt) -> Void'

Thanks for you issue.
Fixed and published to maven, the release is expected to be out soon.

Great!


Disable Docker cookbook acceptance tests until the cookbook or Chef is fixed

Acceptance tests for Docker are currently failing due to a problem starting a service. For now we'll disable this test and file an issue to track fixing the cookbook or Chef if it's a product issue, or otherwise fixing the test if it's a test issue (which seems more likely given that simply starting the service is failing).

They work fine on my local box - that's what's been confounding me about all these tests.  We keep turning them off one at a time due to flakiness when really, we should just turn it all off if it's not providing us with value.  Currently we can't debug any of them and they're all flaky in some aspect or the other.

@ksubrama  I agree that we need more investigation, but the priority is to keep the pipeline unblocked. If the tests are unreliable, they don't really provide value. We will pay for those missing tests with the cost of having to explicitly launch this verification on builds already in current.

👍


Sliding Panel + Embeded Container View + Scroll View

Please provide some samples how to use scroll view in slide panel, how to use top constraints.
the issue is when I move the slide panel up, it is went into the full screen then it cannot be moved down.
thanks

In addition to that how can I reset the sliding panel back to normal position (ie. open from Bottom view as an visible height)

Hi, this is resolved I found the issue and solution.
thanks

@muzammilsahib Any details or examples as to how you achieved this?


Feature/259 urlrequest httpbody function

Checklist

[x] I've checked that all new and existing tests pass
[x] I've updated the documentation if necessary
[x] I've added an entry in the CHANGELOG to credit myself

Description
Fixed the URLRequest.ohhttpStubs_httpBody in Swift 3 and 4.
Motivation and Context
Fixes #259 and allows users to make assertions on the HTTP POST body of a URLRequest in OHHTTPStubsTestBlocks and OHHTTPStubsResponseBlocks.
Sorry about the sloppy commits. I didn't want to download Xcode 7 again so I did a little guess and check with Travis.

@AliSoftware one of the Travis CI builds failed, but it appears to be unrelated to my code changes. Have you had problems with NSURLSessionTests.test_SharedNSURLSession failing in the past?

Yeah don't worry, unfortunately that's a random failure we have on Travis sometimes due to some tests and simulator being extra slow or non responsive when Travis is under heavy load. I  planned to switch to Circle CI for a long time (that's what I use for all my other OSS projects) but haven't had time to migrate OHHTTPStubs on it yet.
I'll restart the failing jobs usually the failure is only temporary.

🎉  Thanks again for your contribution @mplorentz !


Error command not found

I was trying to build the network with this fablo-config.json, but it gave me an error message saying: "/IdeaProjects/fablo/fablo-target/fabric-docker/scripts/chaincode-functions.sh: row 141: jq: comand not found". Someone could give me some advise? Thanks.
{
  "$schema": "https://github.com/softwaremill/fablo/releases/download/1.0.0/schema.json",
  "global": {
    "fabricVersion": "2.4.1",
    "tls": false
  },
  "orgs": [
    {
      "organization": {
        "name": "Orderer",
        "domain": "orderer.example.com"
      },
      "orderers": [
        {
          "groupName": "group1",
          "type": "solo",
          "instances": 1
        }
      ]
    },
    {
      "organization": {
        "name": "Org1",
        "domain": "org1.example.com"
      },
      "peer": {
        "instances": 2,
        "db": "CouchDb"
      }
    }
  ],
  "channels": [
    {
      "name": "my-channel1",
      "orgs": [
        {
          "name": "Org1",
          "peers": [
            "peer0",
            "peer1"
          ]
        }
      ]
    }
  ],
  "chaincodes": [
    {
      "channel": "my-channel1",
      "name": "chaincode1",
      "lang": "java",
      "version": "0.0.1",
      "directory": "./chaincodes/chaincode-java-simple"
    }
  ]
}

Fablo uses jq to parse some JSONs, just install it and it should be fine (it is available both in Linux and OS X package registries)


Optionally poison modules known to not work with pyfakefs

Is your feature request related to a problem? Please describe.
https://github.com/pytest-dev/pyfakefs/blob/main/docs/troubleshooting.rst#modules-not-working-with-pyfakefs documents a number of modules, most obviously multiprocessing and subprocess, as not playing nice with pyfakefs.
Describe the solution you'd like
I'd like to have a way for tests that call into functions in these modules to raise an exception (or at least raise a warning).
Describe alternatives you've considered
Trying to track down failures based on when pyfakefs does fail (often long after the call into problematic code in those modules).

Thanks, this may be a good idea! I have to check how feasible this is (also performance-wise), but I can give it a go. I see that as an add-in feature, and probably configurable regarding the excluded modules.
Not sure when I will get to it though (first have to tackle a couple of bugs).


PyCon AU 2016

Schedule (with links to videos):

https://2016.pycon-au.org/programme/schedule/friday [Note: IoT miniconf already included in PR #160]
https://2016.pycon-au.org/programme/schedule/saturday
https://2016.pycon-au.org/programme/schedule/sunday

Speaker Slides:

https://2016.pycon-au.org/wiki/SpeakerSlides

YouTube Playlists (IoT miniconf excluded):

https://www.youtube.com/playlist?list=PLs4CJRBY5F1Jn2JbfMLX8vblYMC_kKjp-
https://www.youtube.com/playlist?list=PLs4CJRBY5F1JufM2b_FaQT-MTWWx5Oj0o
https://www.youtube.com/playlist?list=PLs4CJRBY5F1Jh6fFqT1p5TZRx5q06CcaR
https://www.youtube.com/playlist?list=PLs4CJRBY5F1IU2xckJUEj5ILWd4cta3vo

Thanks! This issue has been moved to the pyvideo/data repo.


Endpoint for tx count

We need an endpoint, where we get the count of all transactions an address have

Suggested query pattern from frontend:
// start first page shows loading
// pagination shows loading
// limit = 50, offset = 0
// request the first page and the tx count independent of each other so you can show immediately the UI for whichever completes first
requestTransactions(0, 50, address).then(() => { /*show first page*/ });
requestTransactionCount(address).then(() => { /* show pagination links*/ });


Is available mock-server in preview mode ?

The mock-server does serve files in dev mode, is there a way to make the mock-server available in preview mode.

It's a good idea to support preview mode !


I encountered the problem of the server to handle the exception packet

Server crashed when client sent message that cannot be serialized. I think it should be compatible with this dirty data. Reading stream was broke exceptionally caused by the wrong numMessages. I've been reading your code for a week, and I'm trying to fix it. It works. Did I mess it up? This is my backtrace and modification.
(gdb) bt
#0  0x00007f6664949625 in raise () from /lib64/libc.so.6
#1  0x00007f666494ae05 in abort () from /lib64/libc.so.6
#2  0x00007f666494274e in __assert_fail_base () from /lib64/libc.so.6
#3  0x00007f6664942810 in __assert_fail () from /lib64/libc.so.6
#4  0x00000000004214b5 in yojimbo::ChannelPacketData::Free (this=0x226c220, messageFactory=...) at yojimbo_channel.cpp:39
#5  0x0000000000417e5b in yojimbo::ConnectionPacket::~ConnectionPacket (this=0x226c2b0, __in_chrg=) at yojimbo_connection.cpp:45
#6  0x000000000041c494 in yojimbo::PacketFactory::DestroyPacket (this=0x1d24200, packet=0x226c2b0) at yojimbo_packet.cpp:309
#7  0x000000000041b7d5 in yojimbo::Packet::Destroy (this=0x226c2b0) at yojimbo_packet.cpp:40
#8  0x000000000041c0a6 in yojimbo::ReadPacket (info=..., buffer=0x7fff34e07d00 "", bufferSize=93, errorCode=0x7fff34e07c98) at yojimbo_packet.cpp:239
#9  0x000000000042b284 in yojimbo::PacketProcessor::ReadPacket (this=0x1d22080, packetData=0x7fff34e07d00 "", sequence=@0x7fff34e08d50, packetBytes=93,
encrypted=@0x7fff34e08d5f, key=0x0, encryptedPacketTypes=0x1d24120 "\001\001\001\001\001\001\001\001",
unencryptedPacketTypes=0x1d24120 "\001\001\001\001\001\001\001\001", streamAllocator=..., packetFactory=...) at yojimbo_packet_processor.cpp:237
#10 0x000000000041e9d0 in yojimbo::BaseTransport::ReadPackets (this=0x7fff34e08df0) at yojimbo_transport.cpp:367
#11 0x0000000000401c9b in ServerMain () at tests/server.cpp:145
#12 0x0000000000401e22 in main () at tests/server.cpp:181
template  bool SerializeOrderedMessages( Stream & stream, MessageFactory & messageFactory, int & numMessages, Message ** & messages, int maxMessagesPerPacket )
{
const int maxMessageType = messageFactory.GetNumTypes() - 1;
    bool hasMessages = Stream::IsWriting && numMessages != 0;

    serialize_bool( stream, hasMessages );

    if ( hasMessages )
    {
        serialize_int( stream, numMessages, 1, maxMessagesPerPacket );

        int * messageTypes = (int*) alloca( sizeof( int ) * numMessages );

        uint16_t * messageIds = (uint16_t*) alloca( sizeof( uint16_t ) * numMessages );

        memset( messageTypes, 0, sizeof( int ) * numMessages );
        memset( messageIds, 0, sizeof( uint16_t ) * numMessages );

        if ( Stream::IsWriting )
        {
            assert( messages );

            for ( int i = 0; i < numMessages; ++i )
            {
                assert( messages[i] );
                messageTypes[i] = messages[i]->GetType();
                messageIds[i] = messages[i]->GetId();
            }
        }
        else
        {
            Allocator & allocator = messageFactory.GetAllocator();

            messages = (Message**) allocator.Allocate( sizeof( Message* ) * numMessages );
        }

        serialize_bits( stream, messageIds[0], 16 );

        for ( int i = 1; i < numMessages; ++i )
            serialize_sequence_relative( stream, messageIds[i-1], messageIds[i] );

        for ( int i = 0; i < numMessages; ++i )
        {
            if ( maxMessageType > 0 )
            {
                serialize_int( stream, messageTypes[i], 0, maxMessageType );
            }
            else
            {
                messageTypes[i] = 0;
            }

            if ( Stream::IsReading )
            {
                messages[i] = messageFactory.Create( messageTypes[i] );

                if ( !messages[i] )
                    return false;

                messages[i]->AssignId( messageIds[i] );
            }

            assert( messages[i] );

            if ( !messages[i]->SerializeInternal( stream ) )
            {
                numMessages = i+1;    // fix processed messages amount
                return false;
            }
        }
    }

    return true;
}

Thank you for your great job. It's helpful. I will continue to pay attention to.

Please provide code that reproduces this issue.

I've taken a look at this fix. I don't lke returning numMessages = i+1, so instead I think I will try to fix it by clearing each message[i] to NULL, and not cleaning up NULL messages later on. -- cheers

There is also some equivalent code in SerializeUnorderedMessages that needs the same fix.

Fixed. Checking in shortly.

Fixed in this commit: https://github.com/networkprotocol/libyojimbo/commit/9da237133cf82e08a7a8eab348eaee03637ff4d3


Security rule builder in Mission Control

Right now, a user has to configure security rules in Mission Control in a JSON editor. However, it would be great, if we provide a visual builder to do so.

Done. Coming in v0.19.0


f-strings in closures don't have access to outer scope

For example:
func foo(a, b, c) {
	return func(d) {
		return '{a} {b}'
	}
}
foo("hello")("go")

Results in a panic: runtime error: invalid memory address or nil pointer dereference
However, when I bring the closure's variables into scope, I get the correct string:
func foo(a) {
	return func(b) {
		a := a
		return '{a} {b}'
	}
}
foo("hello")("go")

💯 Good find.
I'll work on this.

This is fixed in the new v0.14.0 release.


[Umbrella][Doc] Datasource Connector documentation improvement

Code of Conduct

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

Search before asking

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

Describe the proposal
This section describes the connectors available for different kyuubi engines to access data from various data sources.
User Documentation Writing Principles:

General ones http://www.cypressmedia.net/articles/article/26/six_principles_of_technical_writing
Using markdown or reStructuredText(recommended)
More about how users or developers shall use an API, feature etc, less about what it is.

Task list

Connectors #3060

Connectors for Spark SQL Query Engine

Delta Lake
Delta Lake with Microsoft Azure Blob Storage
#3067
#3068
#3069
Kudu
#3154
#3211
#3228
** Add more connectors if missing **

Connectors For Flink SQL Query Engine

#3070
#3071
#3072

Connectors For Hive SQL Query Engine

#3083
#3084
#3085

Connectors For Trino SQL Query Engine

#3080
#3081
#3082

Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Most of the subtasks are done, and it's should be a long-term story, should we keep it open for the next release? @yaooqinn


This and mosca, a little guidance...

This is not a real issue but a question for guidance. I've played with Mosca and everything worked well. I was curious about QOS 2, and then found this project as a result (it implements it where the Mosca did not, even though I don't need it).
At the bottom of the readme for aedes it says "This addresses your concerns about performance and stability.".
I was curious if this could be elaborated further. What issues are people finding? My feeling was that mosca was a fairly small layer running on top of redis or your backend of choice (which made me assume that is was very performant and ready for production as you can just launch more instances and as long as the backend can handle it then you are good, assuming you have a load balancer and stuff).
At this juncture, especially if using redis (which allows clusters and running on multi-cores for aedes if I'm understanding things), would aedes be the better project to use in a production environment over mosca? Especially if we have just been playing with mosca at this point?

@cendrizzi Aedes is mosca++. It will be the same small layer, but faster, and easier to build and test. It's break down in lots of small modules that can be tested and released independently.
It is hard to contribute to Mosca. This project should lower that barrier as well.
Mosca has lots of internal quirks and if-then-else because of some poor choices of the internal data structures it is using. Those have been fixed in Aedes as well.
In the end, i will move Mosca on top of Aedes. Aedes is not ready yet.

Thanks for the explanation!


HADOOP-18982. Fix doc about loading native libraries.

Description of PR
When we want load a native library libmyexample.so, the right way is to call
System.loadLibrary("myexample") rather than System.loadLibrary("libmyexample.so").

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 50s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
47m 39s

trunk passed

+1 :green_heart:
mvnsite
1m 25s

trunk passed

+1 :green_heart:
shadedclient
85m 49s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 54s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
1m 18s

the patch passed

+1 :green_heart:
shadedclient
38m 11s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
asflicense
0m 36s

The patch does not generate ASF License warnings.

130m  7s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6281/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6281

Optional Tests
dupname asflicense mvnsite codespell detsecrets

uname
Linux f5f2e5b3ec60 5.15.0-88-generic #98-Ubuntu SMP Mon Oct 2 15:18:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 57a2b02932417792ef0c9b8dd3d329e030ef2d38

Max. process+thread count
530 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6281/1/console

versions
git=2.25.1 maven=3.6.3

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
18m 37s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
48m 24s

trunk passed

+1 :green_heart:
mvnsite
1m 25s

trunk passed

+1 :green_heart:
shadedclient
87m  5s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 55s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
1m 17s

the patch passed

+1 :green_heart:
shadedclient
38m 16s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
asflicense
0m 35s

The patch does not generate ASF License warnings.

149m 23s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6281/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6281

Optional Tests
dupname asflicense mvnsite codespell detsecrets

uname
Linux e89ff0e81a8e 5.15.0-88-generic #98-Ubuntu SMP Mon Oct 2 15:18:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 0b6693ff85cb9b31d4dbf868b93b27c3048c48f7

Max. process+thread count
536 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6281/2/console

versions
git=2.25.1 maven=3.6.3

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.


roctracer-proto header find_path

@eshcherb There are merge conflicts with this PR. Please resolve them in case this PR is still needed. Otherwise we can go ahead and close this.


add support for additional aggregations by time period and other geographies

Logging some ideas from conversation with a developer who integrates our data using BQ now. These could be future additions to the stats-pipeline, or could be fulfilled by producing examples using the existing planned statistics:
Geographies:

State (v0)
County (v0)
County Subdivision (FUTURE)
Census-Defined Place (FUTURE)
Tribal Areas (FUTURE)
School districts (unified, secondary, elementary)  (FUTURE)
Congressional districts (FUTURE)
State legislative districts (upper, lower) (FUTURE)

Example time period aggregations:

day
week
month
quarter
year

Aggregation by any of the time periods above is possible using the current output. By querying the stats tables in BigQuery, we can add summary statistics over any day, week, month, quarter, year, or multi-year.
For example, the query below would provide stats for US counties in the first quarter of 2021:
WITH
mlab_us_counties AS (
	SELECT * FROM `measurement-lab.statistics.v0_us_counties`
	WHERE date BETWEEN '2021-01-01' AND '2021-06-30'
)
SELECT
	MIN(download_MIN) AS download_MIN,
	AVG(download_MED) as download_MED,
	MAX(download_MAX) AS download_MAX,
	MIN(upload_MIN) AS upload_MIN,
	AVG(upload_MED) AS upload_MED,
        MAX(upload_MAX) AS upload_MAX,
	county_fips_code,
  county_name
FROM mlab_us_counties
GROUP BY county_fips_code, county_name


Not displaying values until the value of the sensor updates

Describe the bug
When I open a popup, the value of my gauges for example just doesn't display until th sensor updates the value, its kinda problematic
To Reproduce
Steps to reproduce the behavior:

Create a popup
add a gauge on an entity
save
restart the app
open the popup

Expected behavior
To instantly display the correct values
Screenshots

Smartphone (please complete the following information):

Device: Samsung galaxy s20 5g
OS: Android 13
Browser Home Assistant Companion App
Version 2024.1.5-full

the funny thing is that the gauge level is correct its just the value that isnt displayed

oh i found that if i enable "Update cards in background" it works BUT its not recomended... ?

Hi, this issue was already discussed here:
https://github.com/Clooos/Bubble-Card/issues/399
And like I said on that issue, if it works for you you don't have to worry about the "Not recommended" warning.


Add build support for OpenCv 3.4

It seems cvIplImage(cv::Mat) is required above CV 3.3 ... ;-)
With this fix cs::Apex seems to work like a charm on my setup :-)

Sorry, took a while to test this. The actions on this repo were not yet triggered by pull requests, so I had to test this manually.
Works as expected, though :+1:


Avoid storing any unnecessary variable after fit

Some algorithms currently store a reference to the data at fit time (having a self.X_ attribute for instance). According to scikit-learn guidelines (https://scikit-learn.org/stable/developers/contributing.html#fitting), we should avoid this:

Note that the model is fitted using X and y, but the object holds no reference to X and y. There are, however, some exceptions to this, as in the case of precomputed kernels where this data must be stored for use by the predict method.

If we really need all the data we could maybe store a copy of X but I don't think it is the case in metric-learn's algorithms

Currently in the PR preprocessor #117 it was present in LFDA, LMNN, and MLKR, but I changed it in commit https://github.com/wdevazelhes/metric-learn/commit/f2d0cd7f989cc1c41e34cb41b69b2f6982fbe413 (and the following commit) so when the PR is merged this issue should be closed

So once the API branch is merged we can close this as well?

Yes !

I just updated the title, see comment https://github.com/metric-learn/metric-learn/pull/139#issuecomment-450863654


enhance: add log for create container exec operation for debugging

Signed-off-by: Zou Rui<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did
This pr adds log for create exec operation for debugging. The daemon side will print related args, which is the configuration for create exec.
Ⅱ. Does this pull request fix one issue?

fixes #1563
Ⅲ. Describe how you did it
Ⅳ. Describe how to verify it
pouch exec -it ab4edf sh

Here is the log from daemon side:
create container exec with args: {"AttachStderr":true,"AttachStdin":true,"AttachStdout":true,"Cmd":["sh"],"Tty":true}

Ⅴ. Special notes for reviews

Codecov Report

Merging #1569 into master will decrease coverage by 23.69%.
The diff coverage is 0%.


Again, how much does it optimize?

Here’s the statistics diff: https://github.com/Optiroc/SHVC-LZ/commit/8c2ff61c5f0f3ab1d2f77c478a4e4bae17924f78
Another 1KB/s, roughly. Which is cool enough; the mean speed over the test corpus now reached 200KB/s. 👍


Request for future support of AVIF image format.

Hi there! Could you please add support for AVIF image format? The compression rate of AVIF is great for photos. 😄

Hello! Thanks for the suggestion. While AVIF offers excellent compression rates, it's true that its compatibility across browsers and devices is still evolving. As of now, AVIF is supported by some modern browsers like Chrome and Firefox, but not by all. We need to consider broader compatibility to ensure a smooth user experience for everyone.
We'll keep an eye on the adoption and compatibility of AVIF and consider adding support in the future when it becomes more widely supported. In the meantime, we'll continue to support formats that have broader compatibility to ensure everyone can enjoy the content without issues.
Thanks for understanding! 😊

Thank you for your response, looking forward to its growth.😍


Update maintainers to point at team email

Spotted while reviewing deployment of chart for v0.3.0! I don't think there any reason for the maintainers field to vary in any chart in the cert-manager org.

Thanks for spotting this!
Can you also run helm-docs to update the README.md?

Good spot, thanks! Have updated now :+1:

/lgtm

(this need a github-style approve, I'll add the label manually because it's trivial and this is clearly lgtm'd)


FAQ: I want to add an external script

tl;dr: https://phenomic.io/docs/usage/configuration/document-head/

Easy with v1. Will be part of docs


SyncPermissionResults's method names aren't consistent with RealmCollection

Goals
The query and sorting capability on SyncPermissionResults is exposed using the Objective-C API's naming conventions rather than those used in the Swift API.
Expected Results
// Not available!
permissions.filter(predicate)
permissions.sorted(byKeyPath: keyPath, ascending: true)

// Instead:
permissions.objects(with: predicate)
permissions.sortedResults(using: keyPath, ascending: true)

addNotificationBlock exists and is tested, from what I can see.

In the other cases, it looks like the methods exist but are exposed using names consistent with the Objective-C API rather than the Swift API (objects(with:) instead of filter(_:), sortedResults(using:ascending:) instead of sorted(byKeyPath:ascending:)).

Note that the Swift API starts with public typealias SyncPermissionResults = RLMSyncPermissionResults, which exposes the Objective-C type to Swift under a different name. That means all API on RLMSyncPermissionResults is available from Swift (with the exception of symbols annotated with NS_SWIFT_UNAVAILABLE), even though they don't appear to have been exposed using the expected names.

Ah, ok I was misreading this then.

I will update the issue to reflect the naming changes needed.

I'm planning on refactoring SyncPermissionResults to be a subclass of Results<SyncPermissionValue>, so the issues you raised in this ticket should be resolved by that.

#5168 addresses this.


Add Authorization section to README (follow the new format)

See GoogleCloudPlatform/gcloud-meta#3 for what we're hoping to be the shared (mostly) format.

I'm updating the title based on my comment "Holding off on Authorization until we finalize this behavior and unify across services." in #673.

@jgeewax What do we want to do about this?

We obviously need extra stuff outside of the shared docs, but anything that is common would (ideally) get pushed back up into gcloud-common... Otherwise, we can call this done.


Position field in add and edit category pages should only take integer values.

Terms

[X] Before you openning this issue, i have checked if the issue has already been reported.

Bagisto Version(s) affected
2.2.2
Issue Description
Open Admin->catalog->categories->create fill all data enter any word in Position field and save category. It should not save.
Open Admin->catalog->categories->edit enter any word in Position field and save category. It should not save.
Preconditions
Open Admin->catalog->categories->create fill all data enter any word in Position field and save category. It should not save.
Open Admin->catalog->categories->edit enter any word in Position field and save category. It should not save.
Steps to reproduce

Go to 'Admin'
Click on 'Catalog'
Click on 'Category'
Click on 'Create Category'
Fill any word in Position field
See error

Expected Result
Only integer value should accepted
Actual Result
Alphabets can enter and save.
Screenshots

Additional context
No response

Checked and found that the category position issue has been fixed and working fine. Please check the video for reference.
Video
https://github.com/user-attachments/assets/518b29da-6182-4a28-b218-2cfe61bc6155


Upgrade path from 6.x (Multi instance) to 7.x + (Single instance

Feature Description
As described in the module description:
"Therefore in-place upgrades from version 6.x of this module to 7.x, or migrations from multi-instance to single deployment is not currently supported.
We hope to add support for this in a future release."
Its been some time since the 7 support was released.
Could You comment on when You think an upgrade path will be provided.

First of all, I would like to thank all the maintainers of this package for that they've ever made a lot of effort for its creation, so that a lot of users have opportunity to deploy their Elasticsearch instances with Puppet.
But also with that, I am very confused with their decision of dropping multi-instance support in v7 of the package. I believe that my feelings have already been expressed by a lot of people many times over the years, nevertheless, I'll say it once again. Multi-instance configuration is still being supported in Elasticsearch itself, so, logically, end of its support in this Puppet package should not have happened. This decision has affected everyone with such a deployment type, making all these people find out how to fix what has always been worked and should have continued working well. The choice was made for them: either not upgrading from v6 (which becomes way too old), or not using multi-instance setup, or not using this package at all, in favor of Docker or some other workarounds.
I also ask the maintainers to help all those people, who used/still use multi-instance ES by whatever reason, and return the absent functionality back. Thank you.

This was the "recommended" method a few years ago in order to maximise the memory utilisation for a given host containing more than 32GB of RAM. However other methods have become more prevalent since, such as running Elasticsearch in Docker.

ref #1068
Maybe we're in the minority here, but there are other installation methods besides for docker, especially when we've got some beefy hardware instead of adding another unnecessary layer. I see others asking for the same thing, but I would also love to see support for multiple instances come back. The removalhas left us in a bind with being unable to keep updated with this module, and leaving us in a forked state for now :(


[BACKPORT][1.1.x] Restored volume show 'scheduled' with 2 replicas running and 1 unscheduled replica

https://github.com/longhorn/longhorn/issues/3183

Still failing, will keep on eyes to the next test results. Ref.: https://ci.longhorn.io/job/public/job/v1.1.x/job/v1.1.x-longhorn-tests-sles-amd64/73/testReport/tests/test_basic/test_allow_volume_creation_with_degraded_availability_restore_s3_/

Turns out  expect_fail=2 is missing in common.wait_for_replica_scheduled(...) under v1.1.x branch
PR: https://github.com/longhorn/longhorn-tests/pull/949

Validation - PASSED
No more failing with test_allow_volume_creation_with_degraded_availability_restore after the fix backport to v1.1.x-head image.
Reference test result: here


I do not see an "angle" parameter for "cutoutsBase" in v1.4

I do not see an "angle" parameter for "cutoutsBase" in "library/YAPPgenerator_v14.scad".  Was there is reason for that?
Originally posted by @bdlightner in https://github.com/mrWheel/YAPP_Box/issues/5#issuecomment-1066878083

My mistake.
Updated the library just now


Fix encoder nlp transformer 192

This fixes CLS vector issue mentioned in #192

Debugging details in this notebook.


update react-native-webview peerDependency

Updated peerDependencies to avoid cross-version problems within complex react-native projects.

OK， it's a good fix. and i removed lock file, case component library don't nedd.


logging: remove OrderBy option, replace with ReverseChronology

This is for what is currently preview/logging
Logging team says that sorting by time forward and backward are the only likely orderings, so default to ascending and provide a nullary option for reverse order.
@bradfitz @cbro @okdave Ideas for a better name?

Anything but ReverseChronology sounds good to me. :-)
logging.NewestFirst()?
If the default is ascending (oldest first, right?), then where do I specify the starting time? In some totally opaque Filter(f string) EntriesOption?

What could be less opaque than timestamp >= "2014-10-02T15:01:23.045Z"? :)
NewestFirst SGTM.

That's kinda gross. Can we have a constructor for that, using Go types?
logging.EntriesFrom(time.Time) or something?

We really don't want to go there. We're going to get caught in a maze of twisty passages. https://cloud.google.com/logging/docs/view/advanced_filters
People will want to filter on more than timestamp, like log name. We will end up either building an AST for the filter language or having a mix of filter strings and options.

Then at least add some documentation to the filter, and an Example of how to construct that "advanced" filter (timestamp >= "2014-10-02T15:01:23.045Z") from a time.Time.


Gantt - suitable xAxis for longer project

In the example I posted above, I have from 2015-01-22 to 2015-07-15. I would like the axis labels to have ticks every week and the label to be the Monday of each week. 03/09, 03/16, 03/23, etc.

I realize that would be ~25 week ticks in this case which seems like a lot but the only good way I can tell to show that "sprint 3 starts on the week of 03/23" for example.

@nickwynja I have boosted the range for which week ticks are applied. This is in the master branch now but not release. Try it out and see how it works.

This is looking better for me. Thanks!
I figured out the custom formatting you have in axisFormatter and used the following to get the axis labels the format that we work in:
 // Monday a week
    ["%-m/%-d", function (d) {
        return d.getDay() == 1;
    }],

That outputs this and makes it easy to say "Sprint 3 starts on 5/11" as my managers typically ask:

Good! Will keep it as it is then.

I am closing issues and see this one as closed. Let me know if you feel differently!


Fix/sprites not displaying

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Fixes for the issues seen in #419 where sprites and backgrounds were sometimes corrupted.

What is the current behavior? (You can also link to an open issue here)
A project referenced in #419 came across two issues caused by errors in handling large projects.

Sprites were appearing corrupted in some scenes
This was caused by an inbuilt limit of 256 unique sprites in GB Studio, though if you went over this limit there were no warnings and the sprites would appear either using incorrect data or corrupted data.

Some scenes were loading incorrect background images
While GB Studio did have support for over 256 unique background images there was a bug with the function ReadBankedUWORD which causes it to sometimes returns an incorrect value (I believe it's when the value isn't aligned correctly in memory)

What is the new behavior (if this is a feature change)?

I have added support for theoretically 65,536 unique sprites and have fixed the issues with large numbers of backgrounds again giving a limit of 65,536, though I'm sure the ROM would run out of space long before these limits are hit.

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

It shouldn't, I need to do some more testing on a range of projects before merging though

Other information:

In my first round of testing I noticed two more related issues that you probably would have come across soon @tofa2403

Setting the player sprite was only allowing the first 256 sprites to be used

Saving / Loading the game was only working for the first 256 scenes

I've pushed a fix for both issues though the fix for 2 could potentially cause corrupted game save data for anyone who is in the process of making their game.
Save data was previously stored in RAM as
0: is_save_data_stored
1: current_scene_index
2: player_x
3: player_y
4: player_direction
5: player_sprite_index
and in this PR is now stored as
0: is_save_data_stored
1: current_scene_index_high_byte
2: current_scene_index_low_byte
3: player_x
4: player_y
5: player_direction
6: player_sprite_index_high_byte
7: player_sprite_index_low_byte
Saving in game will cause the corrupted data to switch to the new format though.
I'll continue testing incase I've missed anything else like this.

This is great !! Thank you so much for your help @chrismaltby