Flip, and autoUpdate keep last good placement

Hey folks, i couldn't find an answer on this one, so sorry for the ticket if there is an obvious answer. I have a situation where flip and autoPlacement aren't giving the results i want when used with autoUpdate. Basically i have an autocomplete overlay menu that changes height as you type and get results. When you first open the menu close to the bottom of the viewport it flips up correctly to fit. As you type the menu gets shorter and at some point the initial placement will fit again and it shifts back down. This is jarring in context and i'd really like flip to keep the it's placement if it still fits before trying to find a new one. autoPlacement with constraints works for that case but introduces another issue where drop downs shift more than necessary as you scroll which isn't ideal either.
Is there an option or straightforward custom middleware i can write that produces something like a "lazy" version of flip?

In this scenario, you store the first placement on open in state, and use that as the placement prop and disable flip:
const [chosenPlacement, setChosenPlacement] = useState(null);

const {placement, isPositioned} = useFloating({
  placement: chosenPlacement || 'bottom',
  middleware: [
    !chosenPlacement && flip()
  ]
});

if (isPositioned && !chosenPlacement) {
  setChosenPlacement(placement);
}

Demo (scroll container and click button): https://codesandbox.io/s/floating-ui-react-lazy-flipping-mnv2n1?file=/src/App.js.
This keeps it anchored while scrolling in a different context, but prevents flipping after the "first" placement upon open has been chosen.

That works for the first instance but disables flip after the first update right? I really want to keep flip on so that if the menu actually doesn't fit it switches. The case I want to avoid is if the alternative placement and the initial placement both fit, to just leave it placed where it is, instead of switching back to the initial one

Oh ok, then you can leave flip() in the array. The placement: chosePlacement does what you want.

O, perfect. that works great, nice and simple. Thanks


safe_i18n, userconfig, HTMLComponentBase

CHANGES:

created the HTMLComponentBase class and made all components inherit from it instead of HTMLElement. HTMLComponentBase itself inherits from HTMLElement, so all functionality is keept.
-- added a getter for config and dom so all subclasses can use it by this.config / this.dom in a relieable way.
-- safe_i18n is defined in HTMLComponent
--- safer way to get language specific texts by passing a "language path"
---- language path:
------ the language path tells where to find the translated text in the config file dedicated to that language. It is split in subcategories separated by "/"
------ "." as first segment -> uses language specified by user
------ ".." as first segment -> uses always fallback language, defined in config.js
------ if there is no translation for a property, it returns a error message and avoids the app stopping to work

corrected all components and pages to use safe_i18n instead of legacy

added userconfig.js
-- this is where the user specific settings will be stored from now on, language as example. The language set in config.js will be used as fallback

moved the impresum translation from bottom to its own subcategory named top

hab vergessen die database.sqlite raus zu nehmen


Share page is broken on master

Description
The /share page is broken on master. It seems to be generating a
 rather than
 with components of an editor pane and everything. The result is a garbled display of the document scrunched over to one side of the screen and the snippet bar along the top where there should be nothing. I'm guessing this is some confusion with the routing in Homebrew.jsx but I can't pinpoint why this is happening.
The issues also occurs with the /changelog page.
I'd like to figure out what happened here so we can work on pushing out a new version to live at some point.
@stolksdorf @Rae2che5 Are either of you aware of a particular commit that caused this regression?
Share Link:
http://staging.homebrewery.naturalcrit.com/share/S1U_UU5Af
and
http://staging.homebrewery.naturalcrit.com/changelog

Do you also see the weird ; at the bottom of the document and the Warning: Expected server HTML to contain a matching
 in
. thrown by libs.js when running locally? I'm not sure if these are related, but it seems like a place to start - as if there's an unclosed div or something somewhere.
FWIW, if I revert back to using React. as shown in this commit ( https://github.com/stolksdorf/homebrewery/commit/f18a181e2ec5e372121149b3fe9bafbccbe5884d )
along with reverting back to the old version of React, I can get the page to render the splitter correctly. There isn't any brew data showing, but I assume there are related changes to get it to render correctly.
Additionally, the version of modules will continue to be an issue if they are not specifically set in the package.json. It might be a good idea to remove the ^ in each one
Hope this helps!

Found the issue. The Pico-Router module was updated and changed some variable names along the way. It was just 7 characters to change  and now it works. See Pull Request #701 .

Great sleuthing, and confirmed as fixed.


nvidia optimus is gone?

I can not find nvidia optimus ujust toggle as well as info on Post_install page about nvidia optimus. Is it gone forever?
Secureblue Silverblue

The ujust command is gone, mostly because what it did was only effective on a subset of optimus hardware. On other hardware it would have a negative or neutral effect. This is in large part because Nvidia has failed to maintain their drivers properly for older optimus hardware.
Please consult the following for Optimus info:
https://github.com/secureblue/secureblue/wiki/NVIDIA-hardware‐specific-recommendations
Read this one carefully, it's only applicable and required for specific architectures: https://download.nvidia.com/XFree86/Linux-x86_64/565.77/README/dynamicpowermanagement.html#DriverSettingsfe624


Fix APB

Fix the APB interface and prove it works in simulation by creating a GPIO peripheral

Fixed :)


Consider backporting LLVM9 support to the 0.5.x release

https://github.com/rust-embedded/cortex-m-rt/pull/198 fixed an incompatibility with LLVM9 (a new linker section) that looks like it is coming down the pipeline. We should consider making another release in the 0.5.x series to prevent breaking users that use PAC/HALs that have not yet moved to 0.6.x.

cortex-m-rt 0.5 use the semver trick, thus such a backport for an hidden internal thing should not be necessary, no?

Good point. I've just checked and a project depending on cortex-m-rt 0.5 ends up pulling in 0.6.10 now, and the new linker script is the only one that gets used. Convenient!


openapi: Add feature level information for playground APIs/events.

We missed this when adding the new API endpoints/events for
configuring realm "playground" options in the series starting
with 251b415987264a4a18032d0e06b79663e0785a7b.
Also added this step to our REST API endpoint documentation at https://zulip.readthedocs.io/en/latest/documentation/api.html
@timabbott FYI

Nice, merged, thanks @sumanthvrao!


Made the SetCurrentScene function more of a helper function

Currently when you call SetCurrentScene you have to pass arguments so
var args = <String, String>{'scene-name':'amazingSceneHere'};

This will enable you to just pass a string as the name of the scene through
i have also included an example

Thanks, this will be added to the next release as well.


fix autoPlayTimer not cleared after component unmounted

While using react-slick in my application, this warning message occurred periodically:
Warning: setState(...): Can only update a mounted or mounting component. This usually means you called setState() on an unmounted component. This is a no-op.
Seems like it is resulted from an uncleared timer, autoPlayTimer, while using the autoplay feature, and adding the window.clearTimer in componentWillUnMount fixes the problem.

Thanks for the fix!!

@vramana  @akiran  thanks!

Published 0.6.7 version on npm with fix


Version 2.3.1

I have deployed version 2.3.0
I am going to update Version 2.3.1.
Have an error:

2020-01-03 14:38:03 UTC+0200
CheckRequirements
UPDATE_FAILED
Modifying service token is not allowed.

2020-01-03 14:38:04 UTC+0200
AWSWAFSecurityAutomations
UPDATE_ROLLBACK_IN_PROGRESS
The following resource(s) failed to update: [CheckRequirements].

Can someone help me?

Same error for me.

Same here.

I also failed to update an existing stack to the new version. did anyone managed to resolve it?

@ariel-chwat If you're updating an existing stack, using the same S3 bucket parameter, then you will run into a problem with the event that was already created for the bucket. The name of that event is "Call Log Parser" and both the Name and Filter attributes are what cause the problem.
I deleted the event (taking a quick screenshot of the settings to add in case of another problem), and the launched the new stack.

We have deprecated WAF classic version <=2.3.3. Closing this old issue.


Remove version: CrystalDewWorld.CrystalDiskInfo version 8.17.13

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://osdn.net/frs/redir.php?m=ipconnect&f=crystaldiskinfo%2F78047%2FCrystalDiskInfo8_17_13.exe
Response Error: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
(Automated message - build 923)


Change Logging for Header mismatch

@Tratcher
Here a Debug Log is issued when header symmetry fails (there are other examples in this class)
https://github.com/aspnet/BasicMiddleware/blob/dev/src/Microsoft.AspNetCore.HttpOverrides/ForwardedHeadersMiddleware.cs#L80
The code considers the headers untrusted and returns without setting
request.Scheme = currentValues.Scheme;
The result is a redirect loop when
[HttpsRequired]
and
X-Forwarded-For count != X-Forwarded-Proto count
This is a common scenario for

ARR which doesn't add X-Forwarded-Proto by default so is subject to misconfiguration.

nginx which doesn't like appending the proto so very likely the X-Forwarded-Proto is a single value
The best we can do is this map
http://serverfault.com/questions/515957/how-to-have-nginx-forward-the-http-x-forwarded-proto-header

Other SSL load balancers often don't append X-Forwarded-Proto

This situation is not very discoverable and can leave one scratching your head.
Why am I getting a re-direct loop?
Microsoft default LogLevel is Information , so if you look in the logs there is no indication of what actually went wrong aside from a log full of redirects.
Its also a situation which doesn't recover (browser gives up).
At the very least can we change these header checks to _logger.LogError?
Is it a candidate for raising an exception?

We could raise the log level to improve visibility. It should not produce an exception as this is based on arbitrary user input.

That would be great :+1:
If requireheadersymmetry=true (default) I think it would be good to LogError if its not.
I still think requiring header symmetry for X-Forwarded-Proto is broken for anything more than one hop though.  Its really only the first value that is important in determining whether the user arrived at the page through an SSL connection.
so
so if X-Forwarded-Proto is https,http
the http bit is not important and often not added by load balancers etc.
Say you have nginx forwarding to kestrel on your Linux install and you are forwarding from your firewall.
That wont work with requireheadersymmetry=true.
I am hoping to contribute towards the nginx docs as they are quite a bit off :smile:

Actually Warn should be adequate

https://github.com/aspnet/BasicMiddleware/commit/d3816fa458b83603b9e0848baccb1772ab967402


Allow animatronic rotation values above/below +-180

There's currently no way(afaik) to smoothly rotate the animatronic around the 180/-180 area, as it will have to jerk all the way around.
Since rotations are global and not relative to the direction the animatronic was placed, this means a south-facing animatronic can't (for example) wiggle it's body back and forth without doing a full rotation.
Allowing "infinite" rotation values will let the bot spiiiin, etc. You'll probably want to cap the max rotation speed.
If unrestrained rotation isn't preferred(slip rings are expensive!), rotation should be relative to placement direction so south facing robots aren't at a disadvantage, and maybe 180/-180 should be at the back to allow even rotation

Making the block facable sounds like a good addition, however, I won't remove the bounds. Simultaneously rotations is something I want to get in however for the body.

Im closing this now because the Animatronic is facable nowerdays, which is fixing this issue.


It disables VS code default autoclose tag function

Very nice add-on, the color highlights of django syntax is great, but it disables VS code default autoclose tag function. Can you fix it please?

I´m thinking in that, thanks for the comment

I´m thinking in that, thanks for the comment

I also I encountered a similar contradictory problem.

autoclose tag works on html, didn't work on django-html;
syntax highlighting works on django-html, didn't work in html.

Can't have both of them at same time.

Came here because I also noticed this. Would be great if you could look into this.

Hey guys, not sure if the issue #1 can solve this, just adding this in the settings file:
"emmet.includeLanguages": { "django-html": "html" }
All is working good to me, Can you try adding it?

Hey guys, not sure if the issue #1 can solve this, just adding this in the settings file:
"emmet.includeLanguages": { "django-html": "html" }
All is working good to me, Can you try adding it?

template tags suggestion didn't work for django-html language mode.

Yes, I know, I tried it, I'll work on it, thanks for report it

Apparently you can't really have both. I have two options:

Setting the language to HTMLonly: I get both HTML and Django autocompletion with nice closing tags for HTML. For example, if I type divand hit tab I get

with the cursor in between and if I hit enter I get the cursor in a line in between the tags with an indent, so super nice. However this option doesn't give syntax highlighting for Django.

Setting the language to Django HTML: I get a nice syntax highlighting and HTML closing tags just fine. However I don't get the nice indented formatting when I type div and hit enter. I mean that I don't get the blank line in between with a proper indent.

Both options considered the emmet thing added to settings.json already. Other Django extensions only give option 2 for both language settings.

Give me word on the issue at hand, please. Has the autoclose been fixed?


chore[fe]: apply license headers for fe (html, scss, tsx)

Summary of Changes
Include a summary of changes then remove this line
Tests
What tests did you add or modify and why? If no tests were added or modified, explain why. Remove this line
Documentation
What documentation did you add or modify and why? Add any relevant links then remove this line
CheckList
Make sure you have checked all steps below to ensure a timely review.

[ ] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[ ] PR includes a summary of changes, including screenshots of any UI changes.
[ ] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[ ] In case of new functionality, my PR adds documentation that describes how to use it.

All the public python functions and the classes in the PR contain docstrings that explain what it does

[ ] PR passes all tests documented in the developer guide

Do we really have to put this on every file? Is there some information you can provide about this and what it means?

I don't have much context, but mostly follow what LFAI suggested. This is from one email Mark cc from LFAI.
 We did notice also that although the repos have top-level LICENSE files, most of the source code files do not have license headers or references in them. We encourage including a license statement in each file where reasonably possible; this provides many benefits, including making it easier for other projects to reuse the open source files without losing track of their license information. One easy way to do this is by adding a single line comment to the top of each file with its SPDX license ID, such as the following for Amundsen source code:

SPDX-License-Identifier: Apache-2.0

or the following for Amundsen documentation, assuming it adopts CC-BY-4.0 for documentation:

SPDX-License-Identifier: CC-BY-4.0

More information about these SPDX short-form identifiers can be found at https://spdx.dev/ids. Using the SPDX license ID will save you from putting a full licensing header and it is also discoverable by source code scanning tools.

Then I look at an existing example of one of LFAI project from UBER (https://github.com/pyro-ppl/pyro/blob/dev/pyro/ops/arrowhead.py#L1-L2) and they did this. Hence that's how I come up with the pr. I think we only need to apply the headers to source code in a best effort.

Also have concerns about what this means legally. For example with some of the css and style choices (example: All color specifications in _colors.scss) are concepts that we are currently allowed take from Lyft's internal design specifications to use in this tool.
But then if we're now applying some copyright to that, I wonder is that will change the decision we originally got from the people who work on Lyft Product Language. I can look into it, but first trying to understand the implications of this copyright text.

good point @ttannis , unfortunately I didn't see any existing project within LFAI that have code using css or HTML. Let me cc you in the same email Mark cc me so that you could clarify with the LFAI folks


Circular dependency

If there is an circular dependency in property types schema parser ends in infinite loop.

@AdamLutka do you have any proposals? References is one way out... Second is if there is circular depedency, we return second one as empty object ({} in OpenAPI notattion) - this is how Apitte handle this

@AdamLutka do you have any proposals? References is one way out... Second is if there is circular depedency, we return second one as empty object ({} in OpenAPI notattion) - this is how Apitte handle this

References are correct way how to fix it. Empty object is better then infinite loop but it is not correct.


Accordion renders with wrong width when collapsed.

I thought this was fixed at one point, but it appears I was wrong.

I was testing with a broken version of 3.x, sorry for the noise.  Looks like this works.


ui: Fix "too many redirects" when using query frontend

Signed-off-by: Prem Kumar<EMAIL_ADDRESS>

[ ] I added CHANGELOG entry for this change.
[ ] Change is not relevant to the end user.

Changes
Fixes #3043
When using the UI via query-frontend we were getting redirected from /new/ to /new/ itself, which causes an infinite loop.
We had a redirect from /new to /new/ (notice the trailing slash) and I suspect this the reason why we are getting this problem. The Query Frontend passes all requests other than query_range directly to upstream but I think that it is removing the trailing slash somehow. So when we request /new/ the query frontend requests /new from upstream and get a 302 Redirection from upstream for /new/ resulting in an infinite loop.
Verification
Tested locally.

Thank you for the quick fix :100: @prmsrswt


Add test_utils::initial_test_state

This change is

crates/blockifier/src/test_utils/initial_test_state.rs line 55 at r1 (raw file):

                address_to_class_hash
                    .insert(contract.get_address(instance_id), contract.get_class_hash());
            }

Suggestion:
            let class_hash = contract.get_class_hash();
            class_hash_to_class.insert(class_hash, contract.get_class());
            for instance_id in 0..N_INSTANCES {
                address_to_class_hash
                    .insert(contract.get_address(instance_id), class_hash);
            }

crates/blockifier/src/test_utils/initial_test_state.rs line 36 at r1 (raw file):

    // Declare and deploy instances of all contracts.
    for version in CairoVersion::iter() {
        for mut contract in FeatureContract::iter() {

(This suggestion is very silly).
This tells the story more correctly.
Or does that not match how rust works?
Suggestion:
    for mut contract in FeatureContract::iter() {
        for version in CairoVersion::iter() {

crates/blockifier/src/test_utils/initial_test_state.rs line 55 at r1 (raw file):

                address_to_class_hash
                    .insert(contract.get_address(instance_id), contract.get_class_hash());
            }

@dorimedini-starkware look at slack.


"Show All" button on Welcome page doesn't work

Clicking the link doesn't do anything
(note this is a regression from April release)

@v-bbrady Could you take a look when you get a chance? Seeing what the fix is will help determine whether this meets the bar for fixing in the May release.


Select multiple photos

Is it possible to know whether the function of selecting several photos will be implemented at once?

Related to #128, this feature has been implemented in dev-master.

@g0110280  I did not mean it. Can I select multiple photos when I add them?

Yes, keep holding ctrl(win) or command(mac) and click on multiple files.

@g0110280 any solution?

Has the feature of multiple image selection implemented? I tried the latest version but can't seem to work it out to select multiple images? Need help.

I don't understand why this issue has been closes. I am not seeing where it was resolved.

is there any solution found yet ?


Allow to config db protocol while installing package

Although changesWebAction.js can accept db protocol from param, installCatalog.sh doesn't have a way to config it. It will cause the trigger changes cannot be created successfully when the database cannot accept https connection.
So we need to make db protocol can be configured through installCatalog.sh.

While, I also notice this package cannot manage those Cloudant db which doesn't support https connection. It has been hard coded in the action source files to use "https".
We should fix this too.

I do not follow your original comment about changesWebAction.  I agree with you about the hardcoded files for the other actions.  I use couchdb with http for changes and it works fine.

@jasonpet, you are right. My original comment was wrong. changesWebAction works fine for couchdb with http. I will change the title and description to highlight the hardcoded files.


Documentation/cache-only-leaders

Docs PR: https://github.com/arangodb/docs/pull/1340
Backport 3.10: TBD

@Simran-B backport to 3.10 is required.

@KVS85 Yes, TBD = to be done (after the devel changes are reviewed)


Make type annotations in function type literals mandatory

Too many times do we have new users using function type literals without type annotations on their parameters - recently, #3080. Currently the following:
var x: (number, string) => void;

is implicitly typed like:
var x: (number: any, string: any) => void;

even though a user probably meant to type x like in the following way:
var x: (a: number, b: string) => void;

It is actually extremely strange that parameter names, which function purely for documentation, are mandatory while their type annotations are optional.
While --noImplicitAny catches this, new users often don't know about that flag to begin with.
I don't see a good use case for a user who is wiling to type out an arrow type, but wants their parameters to implicitly be typed as any. While this is a breaking change, I'm sure most of the breaks would be with code like in the given example.

:+1:

it would be interesting to see if this pattern even exists in any of the RWC code bases. i suspect not.

:+1:, current behavior was surprising to me when I first encountered it.

A scan over DefinitelyTyped shows almost no cases where someone wrote a type name as a variable name.
Samples:
C:\github\DefinitelyTyped\bootstrap.paginator\bootstrap.paginator.d.ts:
   11:     itemContainerClass?: (type, page, current) => string;
   18:     tooltipTitles?: (type, page, current) => string;
   22:     onPageClicked?: (event, originalEvent, type, page) => void;
   23:     onPageChanged?: (event, originalEvent, type, page) => void;
   24  }

C:\github\DefinitelyTyped\durandal\durandal-1.x.d.ts:
   15        * Sets the module id on the module.
   16        */
   17:     export var setModuleId: (obj, id: string) => void;

C:\github\DefinitelyTyped\fabricjs\fabricjs.d.ts:
   18:     function parseSVGDocument(doc: SVGElement, callback: (results, options) => void , reviver?: (el, obj) => void );

C:\github\DefinitelyTyped\jquery.contextMenu\jquery.contextMenu.d.ts:
   13      delay?: number;
   14      determinePosition?: (menu) => void;
   15:     position?: (opt, x, y) => void;
   16      positionSubmenu?: (menu) => void;

C:\github\DefinitelyTyped\less\less.d.ts:
  533              mime: string;
  534              error;
  535:             push(path: string, callback: (e, root, imported) => void);

C:\github\DefinitelyTyped\linq\linq.d.ts:
   34      interface Enumerable {
   35          //Projection and Filtering Methods
   36:         CascadeBreadthFirst(func: ($) => any[], resultSelector: (v, i: number) => any): Enumerable;

C:\github\DefinitelyTyped\sharepoint\SharePoint.d.ts:
  808      getToolTop(): string;
  809      getDisabledToolTip(): string;
  810:     getOnClickCallback(): (event, action: CalloutAction) => any;

:-1: RTFM

Aren't those typeless declarations broken when noImplicitAny is used? I would consider that a bug in the definition as they're supposed to work in all modes.

:+1: I find this behavior surprising coming from other strongly typed languages, such as C/C++ and Haskell.
// C++
// Argument types: string, double
// Return type: Type
Type foo(string, double);

-- Haskell
-- Argument types: [Char], Double
-- Return type: Type
foo :: [Char] -> Double -> Type

// TypeScript
// Argument types: any, any
// Return type: Type
function foo(string, number): Type;

And, @spion I agree with that.

A tslint rule for this is trivial and operates at the syntax level. If
there is a result node in the AST for a function then you are good. Can
share code if you want.
On Jun 16, 2015 7:57 PM, "impinball"<EMAIL_ADDRESS>wrote:

And, @spion https://github.com/spion I agree with that.
—
Reply to this email directly or view it on GitHub
https://github.com/Microsoft/TypeScript/issues/3081#issuecomment-112606076
.

TSLint does allow to fix the problem, but it has the downside of disallowing code which is probably okay. I would rather have a static analysis check that the names of the parameters are not also valid types in the scope. So this would be okay shorthand:
function funcFactory(): (_) => void { ... }
but this would be an error:
function funcFactory(): (number) => void { ... }
and also an error:
function funcFactory<T>(): (T) => void { ... }

@alexeagle It should be possible to extend TSLint's typedef rule with a new option that applies the check you are proposing. The part where you compare the argument identifier against all valid types in the scope would require linting programs as a whole, which we don't do yet (https://github.com/palantir/tslint/issues/680).

@alexeagle
That's because you need (_: number) => void and (_: T) => void,
respectively. That's the TypeScript language itself, not TSLint. It's a
gotcha, but it's mainly to me consistent with TypeScript's optional typing
when not using the noImplicitAny option.
On Fri, Oct 9, 2015, 12:58 Alex Eagle<EMAIL_ADDRESS>wrote:

TSLint does allow to fix the problem, but it has the downside of
disallowing code which is probably okay. I would rather have a static
analysis check that the names of the parameters are not also valid types in
the scope. So this would be okay shorthand:
function funcFactory(): (_) => void { ... }
but this would be an error:
function funcFactory(): (number) => void { ... }
and also an error:
function funcFactory(): (T) => void { ... }
—
Reply to this email directly or view it on GitHub
https://github.com/Microsoft/TypeScript/issues/3081#issuecomment-146930581
.

@adidahiya that would be a great check to have, I'd turn that on in Angular right away :+1:
@impinball true, you need those expressions with --noImplicitAny. My point is that I'd like behavior where the untyped parameter named _ is permitted, but not an untyped parameter named number. And that behavior is not currently possible. Does that make sense?

The fact number doesn't work sounds like a bug, to be honest. I would
file a separate issue for that.
On Fri, Oct 9, 2015, 14:29 Alex Eagle<EMAIL_ADDRESS>wrote:

@adidahiya https://github.com/adidahiya that would be a great check to
have, I'd turn that on in Angular right away [image: :+1:]
@impinball https://github.com/impinball true, you need those
expressions with --noImplicitAny. My point is that I'd like behavior
where the untyped parameter named _ is permitted, but not an untyped
parameter named number. And that behavior is not currently possible. Does
that make sense?
—
Reply to this email directly or view it on GitHub
https://github.com/Microsoft/TypeScript/issues/3081#issuecomment-146955159
.

number is currently allowed, and I would like to disallow it.

@alexeagle The behavior I'm used to expecting from TS is that these three are equivalent types:
(number, number) => void
(number: any, number: any) => void
(a: any, b: any) => void

If you change that behavior, it changes the semantics enough that it would break a lot of existing code. Not everyone uses --noImplicitAny, so it's not purely an additive change.
That significant of a change would be concerning for even a major version increment.

I think we are talking past each other here. Those are indeed three equivalent types. But the first one is so wrong, I would like a static analysis check to say "you surely, surely did not mean that, and it is clearly a bug". This would not be a language spec change, and in the current landscape, it fits as a tslint check.
However, our experience at Google has been that linters are rarely run electively by engineers, and we want these rules consistently applied, so we prefer to plug such rules into the compiler, where everyone is bound by them.

Ok...I think we can agree to disagree on what we think should be the case.
On Tue, Oct 13, 2015, 13:22 Alex Eagle<EMAIL_ADDRESS>wrote:

I think we are talking past each other here. Those are indeed three
equivalent types. But the first one is so wrong, I would like a static
analysis check to say "you surely, surely did not mean that, and it is
clearly a bug". This would not be a language spec change, and in the
current landscape, it fits as a tslint check.
However, our experience at Google has been that linters are rarely run
electively by engineers, and we want these rules consistently applied, so
we prefer to plug such rules into the compiler, where everyone is bound by
them.
—
Reply to this email directly or view it on GitHub
https://github.com/Microsoft/TypeScript/issues/3081#issuecomment-147783191
.

I just don't feel like arguing it any more.
On Tue, Oct 13, 2015, 13:28 Isiah Meadows<EMAIL_ADDRESS>wrote:

Ok...I think we can agree to disagree on what we think should be the case.
On Tue, Oct 13, 2015, 13:22 Alex Eagle<EMAIL_ADDRESS>wrote:

I think we are talking past each other here. Those are indeed three
equivalent types. But the first one is so wrong, I would like a static
analysis check to say "you surely, surely did not mean that, and it is
clearly a bug". This would not be a language spec change, and in the
current landscape, it fits as a tslint check.
However, our experience at Google has been that linters are rarely run
electively by engineers, and we want these rules consistently applied, so
we prefer to plug such rules into the compiler, where everyone is bound by
them.
—
Reply to this email directly or view it on GitHub
https://github.com/Microsoft/TypeScript/issues/3081#issuecomment-147783191
.

Its very unfortunate that this issue can't be resolved, and I think it should be on the list if / (for whenever) its decided that there will be a breaking release:
Just take this type for example:
declare function compose<T,U,V>(f1:(u:U) => V, f2: (t:T) => U): (t:T) => V;

It could've been written as
declare function compose<T,U,V>(U => V, T => U): T => V;

which is much more readable.
This may not be as important to people already used to the syntax, but it certainly detracts some people away from the language, e.g. https://news.ycombinator.com/item?id=10420940

@spion
I think it's more of an artifact of basing the function type semantics on the arrow function semantics. If you don't have both, the type of that parameter is implicitly any. It's consistent with the rest of the language, just as JavaScript functions before ES6 were super consistent. [1] If anything, I've picked up that consistency only takes you so far before it starts tripping up people.

[1]
Compare (these are equivalent):
var f: x => number
var f = x => x + 1

var f: (x: any) => number
var f = (x: any) => x + 1

Before ES6, this was actually extremely simple and consistent: every function has its own independent this. Simple as that. For example:
function foo() {
  var self = this; // foo's this
  return function bar() {
    return [
      self, // a closure variable
      this // bar's this
    ];
  };
}

foo.call(1).call(2); // [1, 2]

Or, if s-expressions help make this clearer:
(defun foo ()
  (let self this) ; foo's this
  (defun bar ()
    (list
      self ; a closure variable
      this ; bar's this
    ))
)

((foo.call 1).call 2) ; [1, 2]

And new Class(...arguments) did this under the hood until ES6 introduced new.target. Emulated in ES5 JavaScript (except for then-deprecated __proto__)
function Construct(Class, args) {
  var self = {};
  var proto = Class.prototype;
  if (typeof proto === "object" && proto !== null) {
    self.__proto__ = proto;
  }
  var res = Class.apply(self, args);
  if (res !== undefined) return res;
  return self;
}

It just tripped up a lot of people.

The simplicity is also a reason why I've been slow to adopt the new ES6 object model. I can't stand new. It looks simple and elegant until you come across cases where you have multiple is-a relationships. A dolphin is a mammal, but it also is a fish. You can't model that in a single-inheritance environment.


docs(samples): updated samples code to use async await

Fixes googleapis/google-cloud-node#2869 (it's a good idea to open an issue first for discussion)
Fixes https://github.com/googleapis/nodejs-language

[ ] Tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

@praveenqlogic it looks like many of the sample tests are failing.  Let me know when I should take another look!


Questions about the code

Is this the official realization of the paper？

Yes, the complete cold will be released soon. Thanks for your attention.


Comparator conditions (>, <, =) don't work

I just installed Skript-parser and tested it. I wanted to have a sample script to start, so I downloaded the one linked in this release note: https://github.com/SkriptLang/skript-parser/releases (https://gist.github.com/Blueyescat/8793eecf545088bf78007a18f19a2013)
I'm using the latest nightly build of Skript-parser. I downloaded it here: https://github.com/SkriptLang/skript-parser/actions/runs/233965848
And I've just download the JDK (14.0.1 iirc), on macOS 10.15.6.
The problem is in this code:
on script load:
	set {_numbers::*} to 32.19, 11.81, 12 and 1.6
	loop {_numbers::*}:
		print "a: %loop-number%"
		if loop-number > 12:
			print "b: > 12"
			set {_text} to "adding to >12 list"
			add loop-number to {_>12::*}
		if loop-number < 12:
			print "c: < 12"
			set {_text} to "adding to <12 list"
			add loop-number to {_<12::*}
		if loop-number = 12:
			print "d: = 12"
		print "%loop-number%, greater than 12: %whether loop-value is greater than 12% (%{_text}%)"
	print "Numbers that is greater than 12: %{_>12::*}%"
	print "Numbers that is smaller than 12: %{_<12::*}%"
	remove {_>12::*} and {_<12::*} from {_numbers::*}
	print "Not both: %{_numbers::*}%"

The output is:
[19:31:32] ERROR: Conditionals are not allowed in this section (line 5: "if loop-number > 12", test.sk)
[19:31:32] ERROR: Conditionals are not allowed in this section (line 6: "print "b: > 12"", test.sk)
[19:31:32] ERROR: Conditionals are not allowed in this section (line 7: "set {_text} to "adding to >12 list"", test.sk)
a: 32.19
32.19, greater than 12: true (<empty>)
a: 11.81
11.81, greater than 12: false (<empty>)
a: 12
12, greater than 12: false (<empty>)
a: 1.6
1.6, greater than 12: false (<empty>)
Numbers that is greater than 12: <empty>
Numbers that is smaller than 12: <empty>
Not both: 32.19, 11.81, 12 and 1.6

As you can see it won't parse conditions, which results in an incorrect output...
It should definitely parse conditions here...

This is not the fault of ExprCondCompare yielding false results, I think there is something wrong with the section restrictions. @Syst3ms knows probably more about this. This may have to do with #52 as the error message is the same.

This may have to do with #52 as the error message is the same.

That's what I thought too but the line numbers don't match up. What may be possible however is that it is indeed related, and the showed line is wrong (maybe it does take into account blank lines/comments)

Can you check if this issue and the one described in #52 still occur after the latest commit? It normally should've fixed it.


Additional Extension Points in FormBuilder and FormFieldStreamBlock

This change just refactors the code a bit by creating new methods to override when subclassing FormBuilder or FormFieldStreamBlock for customization:

In FormBuilder, created: create_field_class and create_field_name
In FormFieldStreamBlock, created: instantiate_block
In BaseField, created: get_local_blocks
In BaseField, created: get_form_block_class

Please let me know if there's anything else I can do to help this get merged. If you need me to write tests, if you can you please let me know what the signature of each test should be, I will fill in the blanks.
Thanks!

Merged #170

@leongraumans I wonder if this PR is appropriate for merge? If this'll never be picked up, that's totally fine, please just let me know and I can continue to maintain this work in my fork. Thanks

Caught up to labd's master and added a new extension point: get_local_blocks()

@leongraumans I wonder if this PR is appropriate for merge? If this'll never be picked up, that's totally fine, please just let me know and I can continue to maintain this work in my fork. Thanks

bump, and thank you for maintaining this project!

Hi @rgs258,
Happy new year, and apologies for the late reply!  I'll come back to you later this week.

Added yet another extension point, get_form_block_class, to allow the return of subclass of a structural block for further control over the block class, such as overriding the clean() method to provide custom validation.

I think I might share that we're using this package in a somewhat unconventional way. We've adapted it such that Pages themselves are the definition of the form. That is to say, we've made a subclass of Page for which the body StreamField has as local blocks all of the form elements registered to this package (in addition to the usual subclasses of FieldBlock). With this, an content author may create a page that itself is a form, and they may define that form inline with the page content. The Page, and the entire definition of the form, exist within the normal Wagtail system of revisions, permissions, workflow, etc.. This gives our content authors a great deal of freedom and allows out site to host ~2200 unique forms.
Its a dream of mine to extract the non proprietary parts of our adaptation and open source them as a bolt-on to this package. ...just got to find the time :)

Adjusted wagtailstreamforms/wagtailstreamforms_fields.py to use new self.get_form_block_class() and self.get_local_blocks() methods


Ability to keep static imports

Feature request
Allow keep some static imports, at the top level.
Right now we can disable harmony option in parser and keep all static imports, but they will stays in IIFE

What is the expected behavior?
import /* webpackIgnore: true */ { h } from '//unpkg.com/h-document-element?module';

Do not produce error
Must be on the top level in the bundle

What is motivation or use case for adding/changing the behavior?
Ability to generate esm library.
Browsers support 86.05% (26 Aug 2019) https://caniuse.com/#feat=es6-module
How should this be implemented in your opinion?
By insert special webpack comment (similar to dynamic import)
webpackIgnore: true or webpackKeep: true

It would be nice to have this feature for all ways to import modules.
import defaultExport from "module-name"; import * as name from "module-name"; import { export1 } from "module-name"; import { export1 as alias1 } from "module-name"; import { export1 , export2 } from "module-name"; import { foo , bar } from "module-name/path/to/specific/un-exported/file"; import { export1 , export2 as alias2 , [...] } from "module-name"; import defaultExport, { export1 [ , [...] ] } from "module-name"; import defaultExport, * as name from "module-name"; import "module-name";

This is planned, but not in the way you proposed. It won't be based on syntax, but instead use the existing externals feature.
Maybe like this:
externals: {
  "module-name": "module module-name"
}

or
output: {
  libraryTarget: "module"
},
externals: ["module-name"]

This would probably always result in import * as __WEBPACK_EXTERNAL_MODULE_123__ from "module-name" being generated, as it doesn't make a difference anyway.


Rechunk group to group

Hello,
I'm experimenting with multi-group zarrs, where each group represents a separate tile. The tile themselves are structured the same way (same dimensions, variables, etc) and are created with xarray.
Here's a small example of how it can look like:

/
 ├── h19v07
 │   ├── band (1200, 1200, 5) int16
 │   ├── time (5,) int64
 │   ├── x (1200,) float64
 │   └── y (1200,) float64
 ├── h19v08
 │   ├── band (1200, 1200, 5) int16
 │   ├── time (5,) int64
 │   ├── x (1200,) float64
 │   └── y (1200,) float64
 ├── h20v07
 │   ├── band (1200, 1200, 5) int16
 │   ├── time (5,) int64
 │   ├── x (1200,) float64
 │   └── y (1200,) float64
 └── h20v08
     ├── band (1200, 1200, 5) int16
     ├── time (5,) int64
     ├── x (1200,) float64
     └── y (1200,) float64

I was wondering if there's a way to either

rechunk the band array of each group into a new zarr that has the same structure, or
if there's any standard way to rechunk a group to another group

The only way I was successful in rechunking the groups was in iterating over each one, and running rechunk individually with the group path (i.e. target.zarr/group) set as target_store.
Thanks

Hi @valpesendorfer! 👋  Thanks for this interesting issue.
You're correct: right now, we only support Zarr arrays or flat groups (no groups within group). The challenge here is that Zarr support infinitely deep nesting of groups. It's hard for me to think of the right behavior.
So I have a question for you. What API syntax (call to rechunk) would you like to see here? Specifically, how would you specify target_chunks for these nested groups?

Hi @valpesendorfer! 👋  Thanks for this interesting issue.
You're correct: right now, we only support Zarr arrays or flat groups (no groups within group). The challenge here is that Zarr support infinitely deep nesting of groups. It's hard for me to think of the right behavior.
So I have a question for you. What API syntax (call to rechunk) would you like to see here? Specifically, how would you specify target_chunks for these nested groups?

👋 and may I add, thanks for all your work.
First, good to know I'm not missing something essential, I've started with zarrs only recently.
To answer your Q, I don't know exactly ...
But ideally, the manual work I need to do in iterating over groups would be taken care of by rechunker - and since this all is expected to be executed on a dask cluster (in my case), this could also be more efficient / faster as all the tasks can be passed at once. I've not tried yet to generate all the plans first and then execute them on the cluster ... I was too worried about existing temporary storage killing the processes.
In this specific case, I don't want to do anything fancy, meaning I want to keep the same structure, just with the band array re-chunked.
So to specify target_chunks, this is what I currently do for each group:
target_chunks = {
    'band': (256, 256, 5),
}

This could be extended to each group that has an array band.
Or, more verbosely, using a nested dictionary with a group : array : chunk syntax, something like

target_chunks = {

    "/full/path/to/group1": {
        "band": (256, 256, 5),
    },

    "/full/path/to/group2": {
        "band": (256, 256, 5),
    }
}

Which could be generated dynamically:
zarr_raw = zarr.open("raw.zarr", mode="r")

target_chunks = { group: {"band": (256, 256, 5)} for group in zarr_raw.group_keys()}

👋 and may I add, thanks for all your work.
First, good to know I'm not missing something essential, I've started with zarrs only recently.
To answer your Q, I don't know exactly ...
But ideally, the manual work I need to do in iterating over groups would be taken care of by rechunker - and since this all is expected to be executed on a dask cluster (in my case), this could also be more efficient / faster as all the tasks can be passed at once. I've not tried yet to generate all the plans first and then execute them on the cluster ... I was too worried about existing temporary storage killing the processes.
In this specific case, I don't want to do anything fancy, meaning I want to keep the same structure, just with the band array re-chunked.
So to specify target_chunks, this is what I currently do for each group:
target_chunks = {
    'band': (256, 256, 5),
}

This could be extended to each group that has an array band.
Or, more verbosely, using a nested dictionary with a group : array : chunk syntax, something like

target_chunks = {

    "/full/path/to/group1": {
        "band": (256, 256, 5),
    },

    "/full/path/to/group2": {
        "band": (256, 256, 5),
    }
}

Which could be generated dynamically:
zarr_raw = zarr.open("raw.zarr", mode="r")

target_chunks = { group: {"band": (256, 256, 5)} for group in zarr_raw.group_keys()}


lora: Add support for Llama-3.1

While trying to fine-tune Meta-Llama-3.1-8B-Instruct-4bit with QLoRA, I encountered issues loading the model from the HF cache.
(mlx) ➜ lora (main) python lora.py --model /Users/yexiaodong/.cache/huggingface/hub/models--mlx-community--Meta-Llama-3.1-8B-Instruct-4bit/snapshots/efc01dc1fd006f88344400c099cda5b3e8e524ef --train --iters 600
Loading pretrained model
Traceback (most recent call last):
  File "/Users/yexiaodong/go/src/github.com/yeahdongcn/mlx-examples/lora/lora.py", line 336, in <module>
    model, tokenizer, _ = lora_utils.load(args.model, tokenizer_config)
                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/yexiaodong/go/src/github.com/yeahdongcn/mlx-examples/lora/utils.py", line 149, in load
    model_args = models.ModelArgs.from_dict(config)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/yexiaodong/go/src/github.com/yeahdongcn/mlx-examples/lora/models.py", line 40, in from_dict
    return cls(
           ^^^^
  File "<string>", line 14, in __init__
  File "/Users/yexiaodong/go/src/github.com/yeahdongcn/mlx-examples/lora/models.py", line 33, in __post_init__
    raise ValueError(f"rope_scaling must contain keys {required_keys}")

After merging the changes from https://github.com/ml-explore/mlx-examples/pull/907, it works (so far so good on my M1 MBP).
(mlx) ➜ lora (main) python lora.py --model /Users/yexiaodong/.cache/huggingface/hub/models--mlx-community--Meta-Llama-3.1-8B-Instruct-4bit/snapshots/efc01dc1fd006f88344400c099cda5b3e8e524ef --train --iters 600
Loading pretrained model
Total parameters 1256.657M
Trainable parameters 1.704M
Loading datasets
Training
Iter 1: Val loss 2.791, Val took 105.984s
Iter 10: Train loss 2.557, It/sec 0.055, Tokens/sec 17.900
Iter 20: Train loss 1.946, It/sec 0.064, Tokens/sec 20.569
Iter 30: Train loss 1.730, It/sec 0.102, Tokens/sec 33.227
Iter 40: Train loss 1.636, It/sec 0.155, Tokens/sec 47.487
Iter 50: Train loss 1.532, It/sec 0.146, Tokens/sec 45.864
Iter 60: Train loss 1.386, It/sec 0.145, Tokens/sec 45.199
Iter 70: Train loss 1.424, It/sec 0.127, Tokens/sec 40.711
Iter 80: Train loss 1.433, It/sec 0.142, Tokens/sec 44.833

We don't plan to actively update this example (unless there are bugs or something like that). For a feature complete LoRA please use mlx_lm.lora which already supports Llama3+


Speed up screenshoting

The new approach to screenshoting uses only one adb call instead of three and is much faster than the previous one. However, I would like to ask you guys to test the new implementation on your devices as well to make sure it works properly for all supported platforms. Thanks in advance.

Running this locally I keep getting the PNG_MAGIC stuff not working out. Printing the first few bytes that the check is against, I consistently get efbfbd50.

Many thanks. All fixed

Still having trouble. The file gets produced but jimp complains (and the file can't be opened in an image viewer if I try manually):
  1) actions getScreenshot should return valid base64-encoded screenshot:
     Error: Unsupported MIME type:
      at Jimp.throwError (node_modules/jimp/index.js:82:43)
      at Jimp.parseBitmap (node_modules/jimp/index.js:307:31)
      at node_modules/jimp/index.js:200:29
      at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:380:3)

Fixed the default encoding

Published in<EMAIL_ADDRESS>


Add AzureCluster controller

Towards https://github.com/giantswarm/roadmap/issues/2403
Note: This PR is the part of breaking up https://github.com/giantswarm/azure-private-endpoint-operator/pull/1 into smaller PRs that are easier to review.
This pull request is adding a controller that reconciles AzureCluster resources. The controller is doing few checks and then it calls privateendpoints.Service functions (Reconcile and Delete).

Tried out in our test MC, works as expected :)


chore(master): release butler-sos 10.1.1

:robot: I have created a release beep boop
10.1.1 (2024-08-15)
Bug Fixes

influxdb: Double quote app names in in-memory-apps-lists (a7dbb05), closes #843

Miscellaneous

deps: Update dependencies (a32e32c)
deps: update docker/build-push-action action to v6 (cbe758e)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

butler-sos-v10.1.1
:sunflower:


Update README with GitHub CLI instructions

Add instructions for cloning the repository using GitHub CLI to the README.md.

Cloning the Repository

Add a new section "Cloning the Repository" with instructions for using the GitHub CLI command gh repo clone ghostty-org/ghostty.

I'd just add instructions for git
because most people will have git but not so many will have gh cli
and people who use gh cli should know themselves how to clone a repo using it

This section is specifically for developers and I'd expect they know how to clone a project. If they don't, I'm worried. If you want, feel free to add this sort of information to the website build page, though: https://ghostty.org/docs/install/build
Thank you.


[Feature]: API Client can add a destination to a route

Blockers/Dependencies
Blocked by cloudfoundry/cf-k8s-api#38.
Background
As a client of the CF API
I want to add a destination to a CFRoute resource
So that that I can route traffic to apps on CF on Kubernetes
The behavior of this endpoint should match the existing behavior of the POST /v3/routes/[guid]/destinations endpoint in CF for VMs as closely as possible -- including the error cases. Limit the scope of response data to exclude a distinct destination GUID for now, we would like to defer the decision of destination representation. For basic cases, copying the app guid should suffice, especially given the initial focus on single-process apps
Acceptance Criteria
GIVEN I have the API shim running locally according to the README
AND I have created the sample cfdomain.yaml, cfroute.yaml, and cfapp.yaml resources from cf-k8s-controllers on my target kubernetes cluster.
THEN I can perform the following scenarios
Happy Path
WHEN I make the following request
curl "https://api.example.org/v3/routes/84afc0f2-3dc2-4709-9fc8-8340be584a43/destinations" \
  -X POST \
  -H "Authorization: bearer [token]"
  -H "Content-type: application/json"
  -d '{
    "destinations": [
      {
        "app": {
          "guid": "14dcda7d-1fa1-4a91-b437-fbdba20e8c5a"
        }
      }
    ]
  }'

THEN I get the following response
HTTP/1.1 200 OK
Content-Type: application/json

  {
    "destinations": [
      {
        "guid": "14dcda7d-1fa1-4a91-b437-fbdba20e8c5a",
        "app": {
          "guid": "14dcda7d-1fa1-4a91-b437-fbdba20e8c5a",
          "process": {
            "type": "web"
          }
        },
        "weight": null,
        "port": 8080,
        "protocol": "http2"
      },
    ],
    "links": {
      "self": {
        "href": "https://api.example.org/v3/routes/84afc0f2-3dc2-4709-9fc8-8340be584a43/destinations"
      },
      "route": {
        "href": "https://api.example.org/v3/routes/84afc0f2-3dc2-4709-9fc8-8340be584a43"
      }
    }
  }

Request is invalid (invalid request body)
WHEN I make the following request
curl "https://api.example.org/v3/routes/[guid]/destinations" \
  -X POST \
  -H "Authorization: bearer <some-placeholder-token>" \
  -H "Content-type: application/json" \
  -d 'bad json'

THEN The CFRoute CR is not updated
AND I get back the following response
HTTP/1.1 400 Bad Request

{
  "errors": [
    {
      "detail": "Request invalid due to parse error: invalid request body",
      "title": "CF-MessageParseError",
      "code": 1001
    }
  ]
}

Request is invalid (route does not exist)
WHEN I make the following request
curl "https://api.example.org/v3/routes/not-a-route-guid/destinations" \
  -X POST \
  -H "Authorization: bearer [token]"
  -H "Content-type: application/json"
  -d '{
    "destinations": [
      {
        "app": {
          "guid": "not-an-app-guid"
        }
      }
    ]
  }'

THEN the CFRoute is not updated
AND I receive the following response
HTTP/1.1 404 Not Found

{
  "errors": [
    {
      "detail": "Route not found",
      "title": "CF-ResourceNotFound",
      "code": 10010
    }
  ]
}

Request is invalid (app does not exist )
WHEN I make the following request
curl "https://api.example.org/v3/routes/84afc0f2-3dc2-4709-9fc8-8340be584a43/destinations" \
  -X POST \
  -H "Authorization: bearer [token]"
  -H "Content-type: application/json"
  -d '{
    "destinations": [
      {
        "app": {
          "guid": "not-an-app-guid"
        }
      }
    ]
  }'

THEN the CFRoute is not updated
AND I receive the following response
HTTP/1.1 422 Unprocessable Entity

{
  "errors": [
    {
      "detail": "App(s) with guid(s) \"not-an-app-guid\" do not exist or you do not have access.",
      "title": "CF-UnprocessableEntity",
      "code": 10008
    }
  ]
}

Request is invalid (app does not exist in the same space as the route)
WHEN I make the following request
curl "https://api.example.org/v3/routes/84afc0f2-3dc2-4709-9fc8-8340be584a43/destinations" \
  -X POST \
  -H "Authorization: bearer [token]"
  -H "Content-type: application/json"
  -d '{
    "destinations": [
      {
        "app": {
          "guid": "different-space-app-guid"
        }
      }
    ]
  }'

THEN the CFRoute is not updated
AND I receive the following response
HTTP/1.1 422 Unprocessable Entity

{
  "errors": [
    {
      "detail": "App(s) with guid(s) \"different-space-app-guid\" do not exist or you do not have access.",
      "title": "CF-UnprocessableEntity",
      "code": 10008
    }
  ]
}

Dev Notes
No response

@acosta11 ,cf map-route works now so can this issue be closed? Or was there still more to be done?

Indeed, this was just the base add destination functionality which is done. Closing.


file watching glob pattern: ignoring certain directories

We'd like to ignore certain directories for file watching in the Go language server (directories starting with . or _, testdata directories, etc.). However, it's not clear how to do this with a GlobPattern without a lot of additional complexity (a glob pattern that watches every directory in the workspace) or without sacrificing certain types of notifications (golang/go#41504). Is there a simple way to write a glob pattern that watches all files in the workspace, except for those in certain directories? Wanted to check here in case we were missing something obvious.
I asked this question in the vscode repo (https://github.com/microsoft/vscode/issues/117796) since I know the file watching is based on the VS Code API, but the issue was closed, and it probably makes more sense here, since it is part of the LSP.
Thanks!

watching is based on the VS Code API

only in one particular client...

watching is based on the VS Code API

only in one particular client...

I just meant that the GlobPattern in the LSP is based on this: https://code.visualstudio.com/api/references/vscode-api#GlobPattern.

LSP has its own specification if the GLOB pattern to ensure all clients follow the same implementation. Since the glob pattern has no great negation support it will be hard to build a glob pattern that can handle this.
You could try to filter the events on the client side if the client library has a middleware support.
I will keep the issue open as a feature request.


non-manifold edges warning when holes/multiple components

Hello, and thanks for such great software.
I'm trying to use BFF to flatten my segmentation of a brain region. The structure has manifold connectivity (according to Blender); however, when I attempt to load the .obj file, BFF tells me it contains non-manifold edges.
The structure does have holes and multiple components, which if I'm reading your documentation correctly, should be ok (?).
Could you please confirm if the holes/multiple components can be handled, or must be filled/connected?

Apologies! Just realized the structure did not have manifold connectivity after all.


Create LICENSE

As you do not offer a LICENSE, I'm suggesting one, the same you currently have in https://github.com/grafana/grafana-openapi-client-go/blob/main/LICENSE

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Metadata diff NW 752/04

I have this diff in my NW752/04 system with latest abapGit.

Doesn't occur on other systems with NW > 752.
#5755
https://github.com/sbcgua/ajson/pull/132

@christianguenter2 try again
https://github.com/abapGit/abapGit/pull/5771

Works. Closing.


Add isFinal to Type

Especially for generating mock subclasses it is very important if the type is final (because then it's not possible). I don't see a possibility do determine this from the type Type, so I would like to suggest adding it.

Hey @BenchR267 it's indeed may be useful 😄
On the side note, could you share how you generate mock subclasses? Do you use AutoMockable template?

Regarding the issue, as far as I can see: method, variable and class already have isFinal property. Have you tried to use it?

@BenchR267 as @Antondomashnev correctly noted you can use isFinal property of Class, Method or Variable. It was added with #346

Mu current approach was this: (not working for all cases and maybe protocol mocks would be a better idea)
import Foundation
import UIKit
@testable import LOVOO

{% macro stubIfNeeded method %}
{% if method|!initializer and method.selectorName|!hasPrefix:"deinit" and method.accessLevel != "private" and method.accessLevel != "fileprivate"%}

    {% if method.isClass %}static {% endif %}var count_{{ method.shortName }} = 0
    {% if method.isClass %}static {% endif %}var stub_{{ method.shortName }}: (({% for parameter in method.parameters%}{{ parameter.typeName }}{% if not forloop.last %}, {% endif %}{% endfor %}) -> {{ method.actualReturnTypeName }})?
    override {% if method.isClass %}class {% endif %}func {{ method.name }} -> {{ method.actualReturnTypeName }} {
        self.count_{{ method.shortName }} += 1
        if let stub = self.stub_{{ method.shortName }} {
            return stub({% for parameter in method.parameters %}{{ parameter.name }}{% if not forloop.last %}, {% endif %}{% endfor %})
        }
        return super.{{ method.shortName }}({% for parameter in method.parameters%}{{ parameter.argumentLabel }}{% if not parameter.argumentLabel == nil %}: {% endif %}{{ parameter.name }}{% if not forloop.last %}, {% endif %}{% endfor %})
    }

{% endif %}
{% endmacro %}

{% for type in types.based.AutoMockable %}{% if type.kind == 'class' and type.name|!hasSuffix:"Mock" %}
class {{ type.name }}Mock: {{ type.name }} {
    {% for method in type.allMethods %}
        {% call stubIfNeeded method %}
    {% endfor %}
}
{% endif %}
{% endfor %}

For a class like this:
class A: AutoMockable {
    func loadSomething(count: Int, completion: ([String]) -> Void) {
        // … some implementation
    }
}

it would generate a mock-class like this:
class AMock: A {
    var count_loadSomething = 0
    var stub_loadSomething: (Int, ([String]) -> Void)?
    override func loadSomething(count: Int, completion: ([String]) -> Void) {
        self.count_loadSomething += 1
        if let stub = self.stub_loadSomething {
            return stub(count, completion)
        }
        return super.loadSomething(count: count, completion: completion)
    }
}


Support for DISTINCT in the operator algebra

Add a DISTINCT operator to replace UNION DISTINCT and Set projection

This should now be possible by adding an Aggregate(Seq(cols), Seq(), ...)


Remove version constraints to fix pinning mechanism

Checklist

[ ] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Shouldn't things that are not pinned have version constraints? Like CMake, for example, which must be above 3.9 to build ROOT.

The issue is that having things like numpy >=1.10 causes the global conda-forge pinnings to be ignored as there is already a version constraint and the packages are built against the latest version instead. It could be avoided by using something like:
    - numpy >=1.10
    - numpy

which would then get rendered with the pinnings to be
    - numpy >=1.10
    - numpy =1.14

but that's messy to my eyes. It's not so bad for root itself as it just causes other packages to be updated. The issue comes when something else, like root_numpy, depends on root as then the version has the be >=1.17 (from root) and =1.14 (from the global pinnings).
As downstream packages were being built against older builds of root which didn't have these pinnings. I've only noticed now as the Python 3.8 means there isn't an old build to fallback to.
I originally just fixed it for numpy but then gsl became a problem and it I think it's better to just not have them.


Update w2grid.js

added possibility to get columndata from script, that delivers json records

Ok, the refresh is a point. Solved it with replacing the for loop with
$.extend( true, this.columns, loadedData.columns );
onLoad also works with that, but why not use a general nativ solution in gridrendering? in 1.4.x it worked!

Will think about it, but since there is a good work-arround, it is not critical.


docker.#Copy fail when exclude is used

What is the issue?
I have the following docker.#Copy:
docker.#Copy & {
  contents: app
  dest:     "/app"
  exclude: [
    ".gradle/",
    ".idea/"
  ]
}

Log output
failed to execute plan: task failed: actions.build._build._dag."1"._copy: failed to copy file info: failed to chown /var/lib/buildkit/runc-overlayfs/cachemounts/buildkit3698781898/app/.gradle/7.4.2/checksums: lchown /var/lib/buildkit/runc-overlayfs/cachemounts/buildkit3698781898/app/.gradle/7.4.2/checksums: no such file or directory
Steps to reproduce
Create a plan with docker.#Copy and use exclude in a directory (Host).
Dagger version
dagger 0.2.32 (624e5bb94) darwin/arm64
OS version
MAC OS 12.4

I attest that there is an issue with Dagger, I created a simple ready to run repro case to demonstrate it.
Steps

Download and unzip repro case
dagger project init && dagger project update to load dependencies
dagger do build: see the issue

Click to download dagger-2990-repro.zip
I still meet this error when I'm trying to use Dagger from main. It's definitely broken.

FYI: When using absolute, it works.

Closing since CUE is no longer supported.


Give useful error message on SSL errors, e.g. self-signed certificate

If a user tries to connect to a server that uses a self-signing certificate be able to detect that and give a reasonable error (instead of generic one)
React Native does not allow us to differentiate or to override this. We do not want to patch it.
In RealmScreen.js if const serverSettings = await getServerSettings(realm); fails, call a native function that tries to connect to the same URL but ignoring SSL.
If successful, then the server is using a self-signed certificate. Show a specific error detailing this.
The task can be worked by two people, one doing the Android work and another doing the iOS code.

The current behavior seems to be that we give the error message "Network request failed". This doesn't give much idea that there might be an issue with the certificate -- instead it just looks like the app is broken. We regularly get people reporting this as an issue in the app; here's one today.
If we can just distinguish between a network failure (like the server doesn't exist, or our network connection is down) vs. an SSL error (like a self-signed, otherwise untrusted, or invalid certificate), that'd allow us to do much better. E.g., for the SSL error we can say something like "This server can't provide a secure connection (help)", with "help" a link to our SSL docs.

Alternatively, if it really is super hard to distinguish "the server or network is down" from "the server is on the network but SSL is busted", @timabbott points out that we could make the situation a lot better even without that distinction: we just need to make the error message more verbose, explaining that it could be this issue and again linking to docs.

I will edit this issue and will suggest it as a potential task for GSoC candidates.

I can work on this.

@zulipbot claim

@borisyankov what is a self-signing certificate?

Currently, this is what I have so far. I just need to know what a self-signing certificate is
  `tryRealm = async () => {

 const { realm } = this.state;

   this.setState({
   realm,
   progress: true,
   error: undefined,
});

const { actions } = this.props;

try {
  const serverSettings = await getServerSettings(realm);
  actions.realmAdd(realm);
  actions.navigateToAuth(serverSettings);
  Keyboard.dismiss();
} catch (err) {
  this.classifyError();
} finally {
  this.setState({ progress: false });
}
};`

and in ClassifyError function, this is what I have
`  classifyError = async () => {
let err = '';
const isConnected = await NetInfo.isConnected.fetch();
if (!isConnected) {
  // network connection is down
  err = 'Network connection is down';
} else {
  // two cases either the server doesn't exist or SSL problem
  // I don't know much about SSL
  // but if I realized that it's an SSL issue set the error message to that
  // otherwise the server doesn't exist
  err = 'Cannot connect to the server';
}

this.setState({ error: err });
};`

@borisyankov  You suggested this  "call a native function that tries to connect to the same URL but ignoring SSL" can you guide me more on this so that I can complete the function and send a PR.

@ebouJ read the description of the task carefully. You are missing key points of it!

Should I bridege and write a native function to ignore SSL when connecting to a URL? @borisyankov

Yes!

I have set up this server for testing self-signed certs. If anyone wants then feel free to use it. PM me for the certificate.

@ebouJ this is a cool opportunity to test if your code works. Let us know if you need help.

See the out of using his self-signed certificate. I also tried a couple of them yesterday from https://badssl.com. @borisyankov

Oh, https://badssl.com/ is great!
Can you distinguish between https://self-signed.badssl.com/ and any other? That is what we care about.

I did that for my first implementation but had to change because of the approach I took. For now, all SSL related issues are classified as the same error. What I did before was to classify them based on the error message I get if I try to connect.  Each of the SSL problems returns a unique error message but I feel like it was hardcoded and if the error change it's going to break the code. So I can try to look into it more and see if I can come up with a more solid solution, if not I will get directions from you. @borisyankov

Nice!
I don't think it's necessary, or even helpful, to give different error messages for different kinds of SSL errors. For most users that will be more confusing than helpful and not at all actionable; and for the server admin, they have better tools to investigate the SSL issue if they want to.
Like I said above, if we can just distinguish between

a network failure (like the server doesn't exist, or our network connection is down)
an SSL error (like a self-signed, otherwise untrusted, or invalid certificate)

then we'll be in good shape.

@gnprice the current  pull request is doing exactly that. The first thing I did was to check if the user has active internet connection, if not then that's the problem. Otherwise it's either SSL or the server doesn't exist. I then try to connect using the native function and ignoring all the SSL trust issues if the connection was successful then I gave a generic error message like "This server can't provide a secure connection" otherwise I assume the server doesn't exist. The PR isn't complete yet because I have to write native module for IOS, I only know swift so I want to look into Objective C and complete the module. For now, it's only working for Android.

the current pull request is doing exactly that

Yep, understood. (We're talking about #2145 -- linking that just because it took me a minute to find just now.) There was a comment above suggesting that we needed to make a different distinction, so I wanted to make clear that that's not needed.

hello, just rolling out a self-hosted self-signed zulip server and wondering if there is a solution to allow the android app to connect?

I meet the same problem, ios app cannot connect the self-hosted and self-signed zulip server, could this be supported in the future?

my certificate is not self-signed, I got "cannot connect to server" stop.
There some other issue opened about it?
browser does not complain about the certificate (it is signed by a CA)

it is a wildcard certificate, it serves more subdomain on the same machine. It is served by traefik, all the subdomain, so with the same certificate.
I wrote what I wrote because I was meaning what I wrote.
Also "browser does not complain about the certificate" is something common when no proper certificate chain is provided to nginx? (it is a real question, not retorical, maybe there are additional requirements from android net api)

Well, one of the reason I commented is that I expected that this issue was closed, so the message should have been "This server can't provide a secure connection", is it right?
But no, I have "Cannot connect to server"

If you’re missing part of the chain, your server may work with some browsers, but not others and not the Zulip mobile and desktop apps.

I just discovered something usefull


Bitauth update

Please review these changes. I think this will allow the latest @bitauth/libauth version to work on cashscript.
Regards Sydwell

thanks for the PR upgrading libauth, this is something we already did on the @next branch.
We've just merged the next changes and released CashScript v0.10.0 which is using libauth v3...
so I think this issue is resolved 😄 👍


Also log server version on startup

We should also log the server version on startup

Good idea.
But please edit to keep line lengths under 80 characters.

Ack. Will update PR next time I'm at my computer...

@chris-belcher
done


New Feature Request

Please include a page to scan the nearby access point and
Change SSID to one which is surrounded you.
Also add a administration page to change SSID, View password instead of <IP_ADDRESS>/pass and 172.0.01/ssid.

Feature added by @Alpha-1729


Add a github/travis bot to the #perkeep IRC channel

If no one has better ideas I'll probably use
https://github.com/matrix-org/go-neb
I can also highly recommend using Matrix/Riot as your IRC client.  It's awesome.

There's a Matrix github bot that I can activate.  Might want to run that as perkeepbot?


Add TypeScript types

Gidday @scottdj92, thanks for the PR :)
Believe it or not, I'm actually migrating this project from Flow to Typescript entirely! So, I'm going to leave this parked for now while I work on the migration. Again though, thanks for your efforts.

Let me know what I can do! Looking forward to your efforts :)

Closing, as this package will be migrated over to TS completely.


WIP: add Credentials class

Changes Unknown when pulling 7f3156f7ab5aff39c8de2e6708283d56f26d87aa on matiu:ref/credentials into ** on bitpay:master**.

Looking good so far :)

closed in favor of #96


Revert "Expose mod input handlers for better integration between mods"

Reverts maximegmd/CyberEngineTweaks#912

PR broke GetMod API, I suggest adding another function to keep the GetMod API stable.


make it so players can use skills on saves.

rollSave now takes a skill as an additional argument. Its logic is now identical to rollStat. rollRest must pass a null skill argument, since rest rolls a save without an added skill. This fixes issue #3.

Made a new request by making a specific feature branch for this bugfix. Ignore the previously-closed pull request.

Thanks for the PR! Sorry I haven't replied to the previous one. I will look into it.

I finally took the time to review and test & it looks good!


Images on initial (non-scrolled) cells of table view not displayed until scrolling down and back again

I'm pulling avatars into the image on a uiTableView cell.
When the table first loads, the images are not visible on the cells that are immediately in the scope of the phone's dimensions. When you scroll down, the other images are already loaded (even if you scroll down immediately). Then when you scroll back, the images at the top of the table are now visible. If you never scroll down and back, the images at the top will never appear.
Using xcode 7.3.1 with Swift 2.

can this be replicated in the demo project as well?

What is the demo project?

when you download the library there is a demo project that you can test it with. check it out

Ah. Gotchya. Will test and get back to you.

I couldn't get that working but I found a duplicate of my issue here: https://github.com/rs/SDWebImage/issues/9
Changing: cell.imageView!.sd_setImageWithURL(NSURL(string: self.Avatars[indexPath.section][indexPath.row]))`
To: cell.imageView!.sd_setImageWithURL(NSURL(string: self.Avatars[indexPath.section][indexPath.row]), placeholderImage: UIImage(named:"add-user"))`
solved the problem.


update examples/cassandra to api v1beta3

related: #6584

LGTM, thanks!

I ran through the tutorial, but I didn't check if Cassandra worked properly. I submitted a PR for rethinkdb before I left today. I will ask @nikhiljindal to hold that PR.


Scrolling Down in Cloud Drive View Causes Visual Glitch in Column Header Rendering

Discord username
npekin
What type of issue is this?
Intermittent – Occurring irregularly
Is this issue blocking you from using Enso?

[ ] Yes, I can't use Enso because of this issue.

Is this a regression?

[ ] Yes, previous version of Enso did not have this issue.

What issue are you facing?
When scrolling down rapidly in the Cloud Drive view, the contents of the rows sometimes "spills over" onto the column headers. This usually occurs when scrolling up/down very rapidly.

re: the visual glitch... yeah, i think the HTML renderer often struggles to update the clip path before paint. not sure whether it's solveable, but it's not a bad idea to open an issue for it

Originally posted by @somebody1234 in https://github.com/enso-org/enso/issues/9378#issuecomment-1997830935
Expected behaviour
Row contents should never visually overlap with the column headers.
How we can reproduce it?

Open Cloud Drive in Enso GUI
Try to scroll up/down rapidly

Issue is more likely to occur on the first scroll down, so try to refresh and repeat if it doesn't occur at first
Issue may be more likely to occur if you have more elements in your root directory, so try to fill it with files/folders first

Screenshots or screencasts
https://github.com/enso-org/enso/assets/641547/ec96fedd-ca15-435a-bb6c-18f24d0d6081
Logs
No response
Enso Version
2024.1.1-dev (2024.1.1-dev) (a2507abcdb2c375d094dc4d4ce4e7c731cba69f1)
Browser or standalone distribution
Standalone distribution (cloud project)
Browser Version or standalone distribution
standalone
Operating System
MacOS
Operating System Version
Sonoma 14.1.1 (23B81)
Hardware you are using
M2 Macbook Air 24GB

no longer relevant as the background is a solid color now.


Typo

Typo in Quickstart section. It reads:

https;//graph.microsoft.com for both the Base Resource URL and Azure AD Resource URI.

But it should be

https://graph.microsoft.com

Semicolon instead of double colon

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

ID: 8c049c09-0ffb-1994-6c5e-acd549988983
Version Independent ID: 8c049c09-0ffb-1994-6c5e-acd549988983
Content: CoE CLI ALM accelerator for Microsoft Power Platform - Power Platform
Content Source: power-platform/guidance/coe/cli/alm/overview.md
Service: power-platform
GitHub Login: @Grant-Archibald-MS
Microsoft Alias: grarchib

@femo1de This is fixed now; thanks for your feedback.


Unable to give SMS permission on xiaomi Note 4

Basic Information
Device type: xiaomi note 4
OS version: Nougat[16]
EasyPermissions version: 1.1.3
Describe the problem
Unable to give SMS read permission.
What happened?  What did you expect to happen?
I have installed the my application on above mentioned mobile. After giving the read SMS permission unable to read SMS from above mentioned mobile. Same code is working fine in all other mobiles except Xiaomi mobiles.
Code and logs
// TODO(you): show the code that produces the problem,
//            and any relevant logs.

Closing this issue because it's old with no response.


chore(docs): add metadata and header tag info

Summary

add metadata and header tag backlink from custom-page section

Related Issue
N/A
Checklist

[ ] Tests updated (or not required).
[x] Documentation updated (or not required).

Thanks a lot! Are you familiar with Chinese? Can you help translate the docs of Chinese version?

@zmzlois can you check the above comments


[ENG-733] Add registries layout

Ticket: ENG-733
Feature flag: n/a

Purpose
Use a consistent layout for registries.
|            Heading               |
|  Left   |  Main  |  Right    |
Summary of Changes

Move all gutters components from lib/registries to osf-components
Update/merge gutters sass variables into global sass variables
Add handbook page
Update registries overview page

Side Effects
n/a
QA Notes
The changes touch the registries overview page.

Pull Request Test Coverage Report for Build 3402

18 of 22 (81.82%)  changed or added relevant lines in 2 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.01%) to 75.541%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/registries/addon/components/registries-layout/component.ts
17
21
80.95%

Files with Coverage Reduction
New Missed Lines
%

app/application/route.ts
1
67.8%

lib/registries/addon/overview/controller.ts
1
76.92%

Totals

Change from base Build 3396:
0.01%

Covered Lines:
7804

Relevant Lines:
9067

💛  - Coveralls

@aaxelb, made suggested changes.

Closed in favor of #799


fix: make sure to not create more than one reusable container

Sorry for spamming you with PRs recently, but found one more potential issue.
Namely, if reusable containers are triggered in parallel (for example via jest's it.concurrent), it can lead to multiple of the reusable containers being spawned. This is generally not an issue, but in test suites that have dozens or more test cases, it can quite quickly rack up a large number of running containers, ultimately leading to resource constraints.
This proposed approach is hopefully simple enough - checking whether the container already exists or creating it are two separate async processes, but as they are dependent, we should do them in a locked fashion. I added a really simple async lock (no timeouts, no fancy options for re-entry etc.), which can be used to make sure each reusable container hash is checked and created as an atomic set of steps (at least within one node process).
Let me know if I need to add some further functionality or if I missed anything.

@cristianrgreco sorry to bother you, but any way this could get reviewed, it is blocking us from adopting testcontainers - would prefer not to fork the library as it is otherwise an excellent fit!

Hi @henrinormak, not a bother, I am grateful for your contributions! The PR looks great, would it be possible to use an existing lib for async-lock? https://www.npmjs.com/package/async-lock. Seems to have a similar API and is less to maintain. Other than that LGTM

Sure, I originally used that, but thought that it was actually the opposite in terms of maintenance burden (i.e having to update it and what not). I'll swap back to that one.

Released in 9.1.3, thanks again!


adds units to hitbox radius attribute

This pull request makes Nodes selectable/moveable on Firefox.
Non-Null values for r need to have a unit to be valid in Firefox.

Is it a good idea to use px here in sense of different monitor sizes? But searching for em or rem inside the css did not bring up any hits. Only %. Seems like px was used a lot all over.
So this should be quite save I think to merge. Did you tested it with a chromium or webkit based browser?

Afaik, generally speaking, a unitless svg value in a web browser defaults to px, so the explicit declaration as px shouldn't change how the circle is rendered (and it doesn't as far as I have tested)
I've tested it in Firefox and Chromium.

so thanks a lot for the fix 🙇


#145 Failsafe from rollbar-gem. ArgumentError: "invalid byte sequence in UTF-8" in /usr/local/rvm/gems/ruby-2.2.1/gems/rollbar-2.7.1/lib/rollbar/request_data_extractor.rb:197:in `=~': build_payload in exception_data

We are getting this error so much. Once every 20 minute. What is the reason of this error, how can we avoid this?

@codem4ster can you send us an email to<EMAIL_ADDRESS>and tell us your account name and project?
Do you have any chance to start a debugger before that line and inspect the variables there?

@jondeandres I found the problem. '=~' operator doesn't work on non UTF-8 encodings. We try sending data to rollbar which we get from an external service. This service sends us ISO-8859-9 encoded data. I solved my problem by force_encode('ISO-8859-9').encode('UTF-8').
If you want to solve this globally, you can reproduce the error by doing these;

create a file in text editor
write into it 'ŞşĞğİıÇçÜü' and save as ISO-8859-9 (Turkish) encoded
in a ruby script File.read() this file
try to use '=~' operator on taken string

If you can solve this, can you share with me? I would be very appreciate.

@codem4ster awesome, thank you very much for the details. We'll will work on a fix as soon as possible and we'll contact you, ok?
Thank you very much!


[Bug]: pycharm-professional file "pycharm.exe.vmoptions" no longer exists

Prerequisites

[X] I have written a descriptive issue title.
[X] I have searched all issues/PRs to ensure it has not already been reported or fixed.
[X] I have verified that I am using the latest version of Scoop and corresponding bucket.

Package Name
pycharm-professional
Expected/Current Behaviour
JetBrains Pycharm no longer contains 32-bit executable program.
The file "pycharm.exe.vmoptions" no longer exists and should not be in the persist field.
Steps to Reproduce
PS> scoop install extras/pycharm-professional

Possible Solution
Remove the "pycharm.exe.vmoptions" file from the persist field.
The same issue is also persists in other JetBrains products, like extras/webstorm.
Should I create a PR?
Scoop and Buckets Version
PS> scoop --version

Current Scoop version:
v0.3.1 - Released at 2022-11-15

'extras' bucket:
15b9e879e (HEAD -> master, origin/master, origin/HEAD) sidekick-browser: Update to version <IP_ADDRESS>481-d6e815c

'java' bucket:
947c6fa2 (HEAD -> master, origin/master, origin/HEAD) temurin8-nightly-jre: Update to version 8.0.392-3.0.202309081856

'lesscode' bucket:
807d75f (HEAD -> master, origin/master) hashtools: Update to version 4.8

'lesscode-internal' bucket:
c62a08b (HEAD -> master, origin/master, gitee/master) feat: add packages

'main' bucket:
39f5b0ad8 (HEAD -> master, origin/master, origin/HEAD) passbolt-cli: Update to version 0.3.0

'nirsoft' bucket:
bc1d033 (HEAD -> master, origin/master, origin/HEAD) Updated DNSLookupView and FileTypesMan

'nonportable' bucket:
efd7b5f (HEAD -> master, origin/master, origin/HEAD) spotx-np: Update to version 1.8-20230909-ff9d98

'sysinternals' bucket:
db7ddd5 (HEAD -> main, origin/main, origin/HEAD) zoomit: Update to version 7.1

Scoop Config
PS> scoop config

last_update   : 2023-09-09T18:48:09.6895989+08:00
debug         : True
aria2-options : --async-dns=false --remote-time=true
proxy         : <IP_ADDRESS>:10809
scoop_branch  : master
scoop_repo    : https://github.com/ScoopInstaller/Scoop

PowerShell Version
PS> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.19041.1682
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.19041.1682
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

Additional Softwares
No response

Should I create a PR?

Please.


CRUD for "application"

Current Behavior

Meshery is going to support a new construct "application" which the users can use to configure and deploy their applications.
The application configuration will be declared in a YAML file.
Desired Behavior

Meshery Server should have API endpoints that support CRUD actions on these files.
Implementation

This would be an exact copy paste of the functionality in "pattern" and "filter".

Contributor Guide

The initial offering of functionality has been in delivered in v0.5.20.


New release

@javiergarea, can you please do a new release? Or feel free to add me as an owner to hex.pm, and I can do it. :)

Sure! makeup_html v0.1.1 has been published on hex.pm. Regarding the ownership, I can't make the task succeed:
❯ mix hex.owner add makeup_html<EMAIL_ADDRESS>Local password:
Adding owner<EMAIL_ADDRESS>with ownership level full to makeup_html
Adding owner failed
Page not found

@javiergarea please use @gmail.com :)

Done! :shipit:

@josevalim should we close this?


Add internationalization to tray

With this pull request I want to add an internationalization function and demonstrate it's usage on the system tray which is the part of the application I use most.
I would be happy if we could also internationalize other parts of the application.

I think you really need to check out branch 0.3.0🙁, I have already translated the app.

That's great to hear. I'm sorry for not pushing this earlier...These commits have been sitting on my local machine since December. I hope you can at least reuse the translated FAQ.
Is there anything that I can help you with or are you already done?

You can recreate the pr in 0.3.0 with the changes of FAQ, I'll be glad to merge them.
Thank you for your contribute. 🖖


[Spinner] adds inline styles to body

Description

The spinner is adding overflow: inherit; to the body as an inline style when added in it's most basic form to a page. Took a look and it seems to be happening from the following code:

enableBodyScrolling() {
    document.body.style.overflow = 'inherit'
}

Reproduction Steps

[ ] Add spinner to page <Spinner spinning />
[ ] Observe inline style on body

Version Number of TDS
0.29.0

Core team will be addressing this shortly: https://telusdigital.atlassian.net/browse/TDS-95

@heathervv I am removing this code from Spinner, as well as the fullScreen functionality. This will be a breaking change for Spinner so it will only be released as new major version on the individual package @tds/core-spinner.

Spinner no longer affects body scroll as of<EMAIL_ADDRESS>


[Question] How to add ComboBox to Toolbar

Need to have dynamic data to select item in dropdown.  Are there any examples of adding ComboBoxes to a toolbar?  While on the topic, how to add any other simple controls like Labels.  Thx

Unfortunately, this is not something we have support for yet, but it is on our backlog. We will update this thread when we have this implemented! Thanks!

We've created a suggestion ticket for this issue so folks can upvote it: https://developercommunity.visualstudio.com/t/VisualStudioExtensibility-Support-add/10689873. Closing this issue on GitHub.


HLM-299 | Revoke VC - API for revocation

@vishwajeet-eGov the story mentions maintaining a revocation list. That has not been done.
cc @prasanna-egov


MacOS build fails

Hi,
I'm trying to build pupnp on Mac, but I'm getting errors.
Could you help with this? Thanks!
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: .libs/libupnp-1.8.a(libupnp_1_8_la-inet_pton.o) has no symbols
libtool: link: ranlib .libs/libupnp-1.8.a
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: .libs/libupnp-1.8.a(libupnp_1_8_la-inet_pton.o) has no symbols
/usr/local/bin/gsed: can't read Files/Mirror/gerbera/pupnp-release-1.8.1/ixml/libixml-1.8.la: No such file or directory

Hi Tibbs,
The file ./upnp/src/inet_pton.c is completely commented out unless you are compiling it for WIN32. For some reason, the Mac linker is complaining, but the linux linker here is not.
I can suggest you two things:

Come up with some configure time variable and use an "if" in ./upnp/Makefile.am to exclude inet_pton.c from beeing compiled:

if WIN32
# inet_pton (needed on Win32, compiles to nothing elsewhere)
libupnp_1_8_la_SOURCES += \
        src/inet_pton.c \
        src/inc/inet_pton.h
endif

Delete the previous code snippet from ./upnp/Makefile.am and see if that solves the issue.

I must admit I would rather see a patch with the first option ;)
Regards,
Marcelo.

It worked! Thank you very much

Is there a Mac user that could generate and test a patch for this?
I cannot test it here, no Mac around.
I'd like to close this issue, it's been open for too long.
Regards,
Marcelo.

@mrjimenez
I pulled the latest master branch and was able to ./configure && make without any special changes on macOS Sierra 10.12.6 with:
Darwin Kernel Version 16.7.0:  root:xnu-3789.70.16~2/RELEASE_X86_64 x86_64
Is there any steps in particular to try to reproduce the failure?
I successfully compiled gerbera + pupnp-release-1.8.1

Hi Eamonn,
Thank you for your attention. I'll close the issue, then.
Best regards,
Marcelo.


Fix broken QSO-Detail-Links

DisplayContactsOnMap were broken, since Orbit was added.
This one should fix it.

Nice catch. It's in use in too many places ;)


[WFCORE-6642] Remove obsolete eap-repo profile in test

Issue: https://issues.redhat.com/browse/WFCORE-6642 [WFCORE-6642] Remove obsolete eap-repo profile in test

Thanks @soul2zimate


Feat/hash in memory source

Related to #365
This adds support for location.hash in createMemoryRouter.
Let me know what you think!

In case you're interested, I've added support for close to all fields on location in https://github.com/SimenB/router/commit/29d46685e2cfd9d8548ca3a3587114b75a6542d5
I've hard-coded origin there, but it'd be trivial to take that as an optional arg next to the pathname, defaulting to e.g. http://localhost. We use that via patch-package in our project, so it was just more convenient

I'm not gonna PR it as it relies on new URL and I dunno if that'd be accepted. This repo isn't really maintained, so I don't have the energy to pursue it getting merged. It's pretty quick and dirty, but it works great for us 🙂

Looks like we need to add support for hash in the push and replace state functions.

@SimenB This repo is maintained, just in my spare time. Gatsby get's the main focus :) Your commit looks good. I don't love requiring a polyfill on URL though.

Looks like we need to add support for hash in the push and replace state functions.

@blainekasten , ah my apologizes. Would you like me to continue working on this (i.e. are you accepting PRs?) or would you want to take the feature over?

@ricokahler if you could finish it up that would be super great! Make sure to add some tests for the pushState and replaceState too! I'd be happy to accept this

@ricokahler Hey! I'm curious why you closed this?

@blainekasten i closed this because i no longer have the bandwidth to make the change and i’m also no longer using this library.
Sorry for the lack of notice and thanks for maintaining it!

I did leave the issue open if someone else wants to implement


Fix a bug of TokenSymbol

I think it's the other way around. I read the code carefully and thought base should be left and quote should be right.

Thanks for your fix!


Preview is wrong for some stories

Bug Description
See video for more: Wrong preview
Expected Behaviour

Steps to Reproduce

Screenshots

Additional Context

Plugin Version:
Operating System:
Browser:

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

Implementation Brief

Hopefully solved by #2375, will close this as dupe


Create Custom Namespace test not possible from Cypress

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Currently it is not possible to automate with Cypress the custom namespace tests due to the error commented here:

https://github.com/epinio/epinio-end-to-end-tests/issues/180#issuecomment-1161884954
https://github.com/epinio/epinio-end-to-end-tests/pull/193#issuecomment-1163269858

In nutshell, the create/next buttons are not executable after creating a custom namespace in Applications, Configurations and Instances.
It is not possible to do these tests until this is fixed.
So this issue blocks currently that automation.
Expected Behavior
Create/Next buttons should be enabled after all fields have been correctly filled.
Steps To Reproduce

Install Epinio
Download this Cypress test branch to run the code in cypress: https://github.com/epinio/epinio-end-to-end-tests/pull/193
Export the variables needed for the environment. For instance:

export RANCHER_USER=admin RANCHER_PASSWORD=password
export RANCHER_URL=https://epinio.<IP_ADDRESS>.sslip.io
export SYSTEM_DOMAIN=<IP_ADDRESS>.sslip.io

Run npx cypress open -C cypress-with-epinio-cert.json
In namespaces.spec.ts, change  it('Create a Namespace from multiple services' to it.only('Create a Namespace from multiple services'
In the runner option, select namespaces.spec.ts

Environment
No response
Logs
No response
Anything else?
No response

@mmartin24 did something change here? I sadly cannot reproduce it on the UI, seems to happen only on Cypress and not sure what we could do here.

@scures not since the last time I tried. However, I just opened this issue and I wonder if it could be related: https://github.com/epinio/ui/issues/205
I'd suggest taking a look at it and if after fixing it does not solve this, we can close it as "Won't fix" or something similar

Closing issue. Managed to make it work. Closing as not planned