Aerie version discovery endpoint

Background
In the near future we're planning to release some breaking changes to the Aerie backend (for procedural scheduling), and we'll also need to release a new version of the aerie-cli tool to support this. There is some (valid) concern from aerie-cli users about accidentally running an old version of the CLI against a new version of the Aerie backend, causing errors or unexpected results.
The plan for handling this is to have future versions of aerie-cli query the Aerie backend to check its version, & throw an error to the user if they are incompatible (eg. "Unsupported aerie version 2.18.0 - update your aerie-cli version to run this command"). However, there aren't any endpoints on the backend today which expose the current Aerie version.
Describe the feature request
Add a new endpoint called /version to aerie-gateway which reports the Aerie version. It should be safe to assume that Gateway and the other backend services will be running the same versions. The response from the endpoint should look like:
{
  "gateway_version": "2.17.0",
  "db_schema_version": 19
}

Notes/Questions

The db_schema_version would be the schema version from the database ie. would tell you if you're fully migrated to the latest schema or not. This is a bonus and not required if difficult.
Any special handling/additional fields for if the backend is on a non-release version ie. a development branch? Per discussion with @Mythicaeda we think it's most valuable to include the "base" version as is - ie. if you're running a local branch based on 2.18.0 + some additional local changes it should report the version as 2.18.0. But if there is any better way of handling this, we're open to it.

Thanks for filing this @cartermak - I updated the description above based on discussion with @Mythicaeda today, let me know if there are any more details to hash out. Assigning to @Mythicaeda

There is some (valid) concern from aerie-cli users about accidentally running an old version of the CLI against a new version of the Aerie backend, causing errors or unexpected results.

The concern from Clipper is more that we have users try to run new Aerie-CLI against old Aerie. While Clipper GDS manages Aerie deployments, we can't control which of client software is installed by users. Still, having any future version of Aerie-CLI identify that an Aerie 2.11.2 host is out-of-date will address this issue.

Any special handling/additional fields for if the backend is on a non-release version ie. a development branch? Per discussion with @Mythicaeda we think it's most valuable to include the "base" version as is - ie. if you're running a local branch based on 2.18.0 + some additional local changes it should report the version as 2.18.0. But if there is any better way of handling this, we're open to it.

I'll just state my case here and let you both make any final call. IMO, it's safer to have a develop branch report a non-release version tag. That could be just develop or something on top of a release tag (e.g., 2.18.0+dev), but I think that two use cases are better-served by this strategy:

Users who are interacting with an Aerie host without knowing that it's running an unreleased version may be misled by having an endpoint return a release version.
Breaking changes would need to be developed on Aerie-CLI without changing the manifest of allowed Aerie versions until the final release, because Aerie-CLI would need to accept the previous version.

The second point would also be addressed by making the "base" be the upcoming version release and updating Aerie-CLI to accept that version as soon as development starts on that release, which I'm open to, but I think making Aerie-CLI give special treatment to a "develop" tag is a cleaner solution.

The concern from Clipper is more that we have users try to run new Aerie-CLI against old Aerie.
Thanks - I typo'ed that and meant what you said - will update in the description.

I'll just state my case here and let you both make any final call. IMO, it's safer to have a develop branch report a non-release version tag.

I agree with your points, however we're going to proceed with just exposing the base (most-recently-released) version for the first implementation & discuss options for doing that as a follow up. It will take quite a lot more work to detect and report a development branch, and there are some tricky implementation details re: how to represent the branch name/commit & how to handle it on the CLI side. I'd like to get the base version implemented & released ASAP so we can work on the proposed CLI changes which rely on it.

@cartermak the version endpoint has been added to aerie-gateway and is available in the most recent 2.18.0 release.

The response looks like {version: "2.18.0" }
It only reports the "base" version (ie. most recent release version) & doesn't display anything different for a develop branch

We're going to keep this ticket open for now because we'd like to also discuss including other useful version information here such as the database schema version & potentially git branch information (if possible) - but the currently-released version should be enough to implement version-checking on the CLI side now.

Closing this - will consider adding other version info at a later date.


[Feature request] Add predefined regions from python's regionmask

I mentioned this on Slack a little while ago, but I thought I'd open an issue for your record, in case you have time to look into it.
It would be great to add the regions that python's regionmask currently offers on top of scientific regions:

[ ] countries / states
[ ] land masks regions
[ ] and marine / ocean regions

I'm also pinging @asinghvi17 since I stumbled upon his related (but empty!) NaturalEarth.jl repository, since all of the regions listed above seem to come from naturalearthdata.com!

Hi @briochemc, do you have the shapefiles, or some form of raw data that I can have a look at to see how best to extract and put into the package?  I definitely would be interested in putting all the regions above into GeoRegions.jl

No but they are downloaded automatically via cartopy in the python regionmask tool, so I think you can probably translate ideas from https://github.com/regionmask/regionmask/blob/stable/regionmask/defined_regions/natural_earth.py, no?

That probably means that I'll need to download the files directly from natural earth and explore them.  I can do that.
Alternatively, I could have a look and see if there is output from regionmask in the lon/lat form and then export it to a textfile or something.  But thanks or bringing this up - need some documentation of what to do.

I would also add that a global landmask isn't really possible with the functionality of GeoRegions since this would require the combination of multiple GeoRegions that are not otherwise spatially connected.
What would be more appropriate for a landmask would be do download a land-sea mask and apply a filter based on land-sea mask values onto the data.

Yep, I had to do some manual stitching for OceanBasins myself :)
An ideal solution would be to have polygon/region shapes defined on the globe but I don't know where to look for that directly 🤷 . Meshes.jl maybe?

@briochemc if you are interested I might getting around to tackle adding the shapefiles from OceanBasins.jl to GeoRegions.jl myself

Yes, please do!

Did you end up doing this in the end?

Oops not yet, I'm kinda swamped with other things and rewriting GeoRegions.jl (again). Many apologies. I'll get to it.

You can probably just get the regions from NaturalEarth.jl if you're ok with downloading on the fly!

No need to apologize! 😅

Hey @briochemc, I want to let you know that I have had a look at the OceanBasins dataset from NaturalEarth. At this time, because there are several regions in the OceanBasins dataset which comprise multiple polygons, GeoRegions.jl is not really compatible with this dataset, because each GeoRegion is a singular polygon.
However, in v8 of GeoRegions.jl, I intend to add GeoRegions type for regions which are defined by multiple Polygonal shapes, so hopefully this feature will not be too far off in the future (within the next few months, hopefully). I just need to get RegionGrids.jl and LandSea.jl off the ground first.


[BEAM-13768] Fix NullPointerException in BigQueryStorageSourceBase

This NullPointerException is preventable, easily caught by checkerframework, but it was disabled. Found it via a user report so fixed checkerframework for just this class.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[x] Update CHANGES.md with noteworthy changes.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @pabloem have a minute for this one?

Or also R: @kmjung


Cards in Testimonials are not of same size

Description
The Cards in the testimonials are not of same size. Please assign me this task
Screenshots

Go for it! For support join our discord community: https://discord.com/servers/codein-community-831388874118660156

Hey is this closed? Or can I work on this


Never truncate when writing output to file

When writing console output to file with *>>, lines should not be truncated. Currently, output is truncated to 85 characters. This makes Powershell fundamentally unusable for me.

Actually, stuff should never be truncated in general. Pretty much every command I run in powershell has things truncated with ...
THere is plenty of space in my screen and in the window, yet, after 15 characters powershell will truncated some stuff.
Man, how I really hate microsoft tools.

@pedrogarcia Thanks for your report! The Issue is duplicate #1908.
Currently PowerShell Core format all output based on console width, we want enhance the behavior for pipes with native commands.

Man, how I really hate microsoft tools.

PowerShell Core is an open project - feel free to show how need to build systems correctly. Welcome to make the enhancement and fix the Issue!

@iSazonov - I'm reopening because fixing this issue might require different work than #1908, and this issue can be fixed without fixing #1908.

@pedrogarcia could you please add a repro?

Sure.
Run a long copying task for rclone, with verbose output flag, for example:
‘
rclone -vv copy “drive:/folder1” “drive:/folder2” *>> cmd_output_log.log
‘

I see the code in Out-File which computes the console width, but I'm not able to repro this.  In fact, the -width parameter doesn't even get honored.
$text = "0123456789"
while ($text.Length -lt [console]::WindowWidth) { $text += $text }
$text | Out-File ./test.txt -Encoding ascii

Not even able to repro with Windows PS 5.1

@SteveL-MSFT I believe Out-File don't send simple objects to formatting system before output. If you replace string variable in your test with a hash or array you'll get repo.

@iSazonov but the original repro was a native command outputting to stdout

I wonder. Maybe Out-File detect a file provider in input strings?

I tried using the native echo on Linux as well as testexe -echoargs to get long output, but nothing gets truncated.
Objects being truncated during formatting is currently expected (although I'm open to consider changing it...) and -width does work in that case.

Downloaded rclone and was able to repro it

The easy fix is to not truncate in all cases.  I'm not convinced that having the text log have the same width as the console used during runtime is useful.  The console I'm using to generate the log is probably not the same console I used to read the log.

would that also apply to collections of complex objects with lengthy string members? If so, how would that work or look like? I know I'm in the minority opinion on the usefulness of the console width in Out-File, but I think completely removing truncating may have some undesirable side effects too.

@markekraus I would prefer to add a -TruncateToConsoleWidth type switch if needed, but I don't think even that is needed.  For objects with lengthy string members that's only a problem if you view the log in the console, in that case, I'd rather have a switch to Get-Content to truncate.

@SteveL-MSFT I'm just curious what this would look like?
$LoremIpsum = "Lorem ipsum dolor sit amet, bibendum cum ornare, integer ultrices, donec augue, ultricies vitae hendrerit vestibulum et sed iaculis, potenti montes libero. "

1..100 |  %{
    [PsCustomObject]@{
         Column1 = $LoremIpsum*(1..100 | Get-Random)
         Column2 = $LoremIpsum*(1..100 | Get-Random)
         Column3 = $LoremIpsum*(1..100 | Get-Random)
    }
} | Out-File -FilePath C:\temp\outfile.txt

Currently that is a truncated single column, which i agree isn't great. But, how would not truncating this work? Would it be coerced to a list? What id the user wants to retain columns? if so based on what logic? or would it be in un-truncated columns? and if so, how would column width work? would it really need to calculate the max width of each column  and then build the output file? What kind of performance impact would that have? or would columns just be all different widths with no discernible column alignment?

So it is dup 3813 and 1491.
Please see @lzybkr comments in https://github.com/PowerShell/PowerShell/pull/4006 about a fix direction.

Resolving as dupe of https://github.com/PowerShell/PowerShell/issues/3813, let's carry on with that one.

Here is the solution of all the truncation issues https://mcsaguru.com/how-to-fix-truncated-powershell-output/. He explain very well why truncation happens and hwo to fix them.

_Here is the solution of all the truncation issues https://mcsaguru.com/how-to-fix-truncated-powershell-output/.  .....

a broken link


Add support for deploying Nested Applications

Issue:
There appears to be no way deploy a nested application
Using a nested local application referenced in the template as documented here:
https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-sam-template-nested-applications.html requires the "CAPABILITY_AUTO_EXPAND" capability to be specified as documented here: https://docs.aws.amazon.com/serverlessrepo/latest/devguide/acknowledging-application-capabilities.html
There does not appear to be a way to specify this using the AWS Tookit for Visual Studio.
Since there is a hard limit 200 of resources, its seems there is no way to deploy an application using the toolkit with more than 200 resources.
To reproduce

Specify A.yaml to use in aws-lambda-tools-defaults.json
In A.yaml, reference B.yaml locally, using a resource of type: AWS::Serverless::Application

HI AWS Team, Kindly any update for this issue


[BUG] pagination nzPageIndex double binding not work.

I'm submitting a...

[x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Support request => Please do not submit support request here

Current behavior

pagination nzPageIndex double binding not work.
Expected behavior

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Environment

Angular version: X.Y.Z

ng-zorro-antd version: X.Y.Z

Browser:
- [ ] Chrome (desktop) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] IE version XX

For Tooling issues:
- Node version: XX
- Platform:

Others:

I bind nzPageIndex to a variable named currentPage, first I execute currentPage++ then request server after response I set nzTotal to the new value but not set currentPage to the new value (because they are the same), this situation nzPageIndex double binding doesn't work.  I have to set currentPage once more after setting nzTotal. this took me some time to solve. The version of ng-zorro is 0.7.1, I have no idea whether the lastest version has the same problem. @vthinkxie

@Renhj90520 please submit a new issue with repro link.


refactor: rename a channel in Store/sync for clarity

#538  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @rphmeier and the rest of your teammates on  Graphite


Upload API should accepts any valid index name as input

Upload API accepts requests only when index name ends with -map. This was added because api was initially planned to call only by Region maps. With Maps from 2.5, the upload API should allow user to upload any valid GeoJSON with any acceptable valid index name ( no mandatory suffix ). This won't affect Region maps, since front end already have this validation in place.

This won't affect Region maps, since front end already have this validation in place.
Is that mean, we need such restriction for Region map? We cannot rely on frontend validation. Customer request can hit the backend directly.

@VijayanB The description poses 2 questions:

For region maps do need maps as suffix on the index name?
With 2.5 release of dashboard are we thinking that a valid geojson can be applied apart from region maps?

I would like to understand that more and then check the PR.
and +1 on @heemin32 comment, we need to have validations at both the places.

For question 2, yes, you can use it in cluster and document layers

@VijayanB I think it make sense, but as region maps older UI will also be supported in 2.5 release the check on the OSD will still remain. We need to make sure that we are removing that check also in this case.

Is there other ways to identify index that was created by file upload without using the suffix now?

Sorry it was not clear from description. Let me try to explain how it is handled now. From OpenSearch Dashboards 2.3 onwards, region map will call this API by adding suffix "-map" as index name. For ex: if user gives test-index, then OSD sends index name as test-index-map as input name. In the backend, this input is validated for suffix. This was added as extra validation to make sure that this API is used only for Region Maps. This "-map" suffix is  required so that region map can ask list of index that ends with "-map" and suggest only those index for custom vector map.
Now, we can leverage the same API to create an index for non-Region map use cases . Hence, i am proposing to remove this check only from backend. We still have to add "-map" suffix from OSD for Region map for older UI in-order to be available for Custom Vector Map.
What changed now with this change?
It was expected ( only supported ) that users will use OSD UI to upload Custom Vector Map .
Before this Change:
If they tried to do this from curl or non-dashboard, it will be rejected unless api includes expected suffix.
After this change:
The request will be succeeded, since, this request can be used to create an index that can be used independent of Region Map. Here, we are successfully decoupling backend API from OSD requirements.
IMO, i don't think this breaks any backward compatibility.
@navneet1v @heemin32 Please let me know wdyt and do you have any other suggestions?

Thanks @VijayanB. It is clear for me now. Agree that we can remove the validation in backend side.
One more question. In the new release, I assume we have another way to get a list of Custom Vector Map without relying on the "-map" suffix?

We are taking a different direction where going forward customer can use any index with geospatial field types as custom vector map

The needs to remove the validation from backend side is clear as it needs to be used by cases other than Custom Vector Map.
We should have a better way to track a group of indices in OSD without relying on suffix. @VijayanB, could you create an issue in dashboards-maps repo?

Feature is merged.


navigate() throws exception when title is an

Edit: The below applies when the header title is an  component.
This works fine:
public static navigationOptions = {
  title: 'foobar', //...

This causes this error:
public static navigationOptions = {
title: <Image source={require('../images/header_logo.png')} />, //...
It looks like a react-navigation bug to me.  Thanks for taking a look.
Current Behavior
Attempting to call this.props.navigation.navigate() results in this error message.  I've tried it with different components.  It seems like some prop name is being passed as an object, not a string.

log-ios gives a bit more detail:

Sep  7 14:14:56 MacBook-Pro-5 mobile2mr[25676] : Error setting property 'accessibilityLabel' of RCTView with tag #196: JSON value '{

Here's my StackNavigator setup (within a TabNavigator):
const trackingTabWithHeader = { screen: StackNavigator(
  {
    Tracking: { screen: TrackingScreen },
    Workout: { screen: WorkoutGroupScreen },
  },
  {
    ...stackNavigatorConfig,
    initialRouteName: 'Tracking',
  },
)};

Expected Behavior
Should navigate!
Environment

software
version

react-navigation
v1.0.0-beta.11

react-native
0.47.1

node
8.0.x

npm or yarn
yarn 1.0.1

I think you should use headerTitle not title

@bennygenel Yes - thanks.  Thought I saw this example somewhere, that was a costly erroneous type.
Will increase reliance on TS in the future esp since this lib provides good defs.

@bennygenel I am using headerTitle but it still breaking for me, any suggestion

@manjeetwadi hard to say without any code and more info about how its breaking.

@bennygenel  your solution works


[FLINK-33058][formats] Add encoding option to Avro format

What is the purpose of the change
Initially proposed in https://issues.apache.org/jira/browse/FLINK-33058
Avro supports two serialization encoding methods: binary and JSON (cf. Avro docs)
flink-avro currently has a hard-coded assumption that Avro data is binary-encoded (and cannot process Avro data that has been JSON-encoded).
This pull request introduces a new optional format option to flink-avro: avro.encoding
It supports two options: 'binary' and 'json'.
It unset, it will default to 'binary' to maintain compatibility/consistency with current behaviour.
Brief change log
Flink uses Avro Decoder and Encoder classes for deserializing/serializing Avro data.
However it was hard-coding the use of factory classes to only use the binary-encoding implementations of these abstract classes.  (DecoderFactory.get().binaryDecoder and EncoderFactory.get().directBinaryEncoder)
In this pull request, I'm using the value of the new avro.encoding option to create the JSON Decoder/Encoder classes where appropriate.
Verifying this change
This change modified existing tests by re-running all of the tests that perform Avro serialization/deserialization to repeat the test using both binary and avro encoding.
This verifies that the existing binary behaviour is unaffected by the new option, as well as the new JSON support.
I've also manually verified the new support using Flink SQL such as:
CREATE TABLE JSONAVRO
(
    ... my columns ...
)
WITH (
    'connector' = 'kafka',
    'topic' = 'MY.TOPIC',
    'properties.bootstrap.servers' = 'localhost:9092',
    'properties.group.id' = 'my-group',
    'scan.startup.mode' = 'earliest-offset',
    'format' = 'avro',
    'avro.encoding' = 'json'
);

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): yes
The serializers: no
The runtime per-record code paths (performance sensitive): yes
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? yes
If yes, how is the feature documented? update to the Avro format page to explain the new option

Apologies for the flurry of follow-on commits - this is my first contribution to Flink so I'd missed the checkstyle and spotless rules when testing locally.
I think it's ready to review now, but I'm sure there are still other things I've unwittingly missed! Please let me know if there is anything else that I should do to get this PR into an acceptable state.

Thanks for the reviews - much appreciated 👍

@flinkbot run azure

@flinkbot run azure

That being said, @afedulov, do you think it's worthwhile bringing up the new feature on the mailing list to discuss?

This was my initial thought, yes. Ideally we do not want to introduce functionality for very niche use cases, but this one makes sense to me, especially for building demos etc. Although this change, in my opinion, does not deserve a FLIP, I think it still makes sense to do a quick vote in the dev mailing list. The idea would be to prepend the topic with [VOTE], briefly describe the proposal, why it is useful and the downsides of it not being the best practice (Ryan's concerns). If no one comments - this is a silent yes.

I took the liberty of bringing it up in the mailing list -- I thought that was fair!

@afedulov Is there anything else that you think is needed here?

@afedulov @JingGe @RyanSkraba It looks like this is approved by all and ready to go for some time now, please could one of you merge this - so this is not forgotten. Many thanks.

From us three only Jing has the permissions to merge.

@JingGe Thanks very much - I've done the squash and rebase now


Add support for the azure client

Wouldn't hurt to just use aws from here too ...

I added this to my aliases:
alias az="docker run -it --rm -w `pwd` -e DB_SHARD_HOME=$DB_SHARD_HOME -e HOME=$HOME -v $HOME:$HOME azure-cli az"

This is my azure cli Dockerfile
FROM mcr.microsoft.com/azure-cli
RUN az extension add --name azure-cli-iot-ext

Mostly i wanted Brian's fancy environment cloning logic but it wouldn't hurt to just fold these tools in.

Why do you need a separate Dockerfile? Isn't the stock microsoft/azure-cli Docker image enough?


Android support

Adding support for Android native events on "_onStartShouldSetResponderCapture"

Really thanks @juanmunozg  for me its working exactly. @baijunjie can you merged please?

Thank you for your support


Distribution requires MANIFEST.in file to include setup.json

As it stands the setup.json file will not be included and the distribution will be broken as the setup.py will not be able to load the file

Fixed in #14


Add extended glib_wrapper syntax for cross-crate inheritance

Thanks.

Merge then.

Good for me as well. Thanks @gkoz!


Added JAVA JDBC codes

Add resources not codes
Add resources like courses, certifications, roadmaps, notes, cheat sheet, etc


Update MULTI_NIC_SETUP.md

minor fix

Coverage increased (+0.08%) to 76.876% when pulling 0d7a231ceda1afc338919e457eb512222c8a6e00 on gilesheron-patch-2 into 968dc84e61b3ebad379f102faae5773fa966a98c on master.


[AutoDiff] Remove flaky SR-12650 negative test.

@noDerivative parameter mangling was added in https://github.com/apple/swift/pull/31201, so the negative test is not meaningful.
The test occasionally flaked during CI, so it's better to remove it:
14:20:50 FAIL: Swift(linux-x86_64) :: AutoDiff/compiler_crashers_fixed/sr12650-noderivative-parameter-type-mangling.swift (13232 of 13264)
14:20:50 ******************** TEST 'Swift(linux-x86_64) :: AutoDiff/compiler_crashers_fixed/sr12650-noderivative-parameter-type-mangling.swift' FAILED ********************
14:20:50 Script:
14:20:50 --
14:20:50 : 'RUN: at line 1';   /home/buildnode/jenkins/workspace/swift-PR-Linux-smoke-test@2/branch-master/buildbot_linux/swift-linux-x86_64/bin/swiftc -target x86_64-unknown-linux-gnu -toolchain-stdlib-rpath  -module-cache-path '/home/buildnode/jenkins/workspace/swift-PR-Linux-smoke-test@2/branch-master/buildbot_linux/swift-linux-x86_64/swift-test-results/x86_64-unknown-linux-gnu/clang-module-cache' -swift-version 4  -Xfrontend -ignore-module-source-info  -g<EMAIL_ADDRESS>14:20:50 --
14:20:50 Exit Code: 254
14:20:50
14:20:50 Command Output (stderr):
14:20:50 --
14:20:50
clang-10: error: unable to execute command: Bus error (core dumped)
14:20:50 clang-10: error: linker command failed due to signal (use -v to see invocation)
14:20:50 <unknown>:0: error: link command failed with exit code 254 (use -v to see invocation)

@swift-ci Please smoke test


Write messages directly onto message buffer instead of allocating on own buffer

pgbench -t 1000 -c 16 -j 2 --protocol extended -C:
PR:
Stats {
allocations: 3873384,
deallocations: 3870448,
reallocations: 130708,
bytes_allocated: 497650190,
bytes_deallocated: 496466494,
bytes_reallocated: 3722992,
}
Original:
Stats {
allocations: 4578799,
deallocations: 4575881,
reallocations: 130689,
bytes_allocated: 509003135,
bytes_deallocated: 507846373,
bytes_reallocated: 3716031,
}
Results in about a 15% decrease in allocations
pgbench -t 1000 -c 16 -j 2 --protocol extended:
PR
Stats {
allocations: 2656700,
deallocations: 2653782,
reallocations: 2808,
bytes_allocated: 65691251,
bytes_deallocated: 64544049,
bytes_reallocated: 742898,
}
Original
STATS: Stats {
allocations: 3361868,
deallocations: 3358897,
reallocations: 2863,
bytes_allocated: 77151598,
bytes_deallocated: 75935794,
bytes_reallocated: 757720,
}
Results in about a 20% decrease in allocations

This is very neat!


Migrate AWS to new LFEnergy root account

Since we have a new Root Account for AWS from LFEnergy, we need to migrate the AWS services to this new root account.
This includes:

ECS migration
Load balancer Migration + HTTPS + point demo.compas.energy to this loadbalancer
Check that Github Actions still work
Auth0 Migration
Update documentation (taks definitions)
Document manual steps  that are not described in deployment documentation: https://github.com/com-pas/compas-deployment/tree/main/aws
Export "old" AWS environment

Once everything works, we can/need to change the Auth0 migration to the LFEnergy Auth0 instance.

It is unclear where the what the open tickets are at the LF energy servicedesk.

It oder to swith more easy: use 2 browers (e.g. 1 in private mode); deployment take sometimes multiple minutes

Currently we are missing a fix in the redirect after auth0 login and an upgrade of the compas-open-scd version, but demo.compas.energy is successfully moved to the LFEnergy AWS account. #171 will fix this.


Taskefile: Add cmake and remote utils; update checksum data path to an array.

Description
This PR adds two new sets of utility tasks, while also updating the checksum util tasks.
cmake utils
This PR adds two new tasks related to building a cmake project. The first runs build and configure, while the second performs the installation. Separating these tasks allows up to build a project once, but install it multiple times to different locations.
remote utils
The main utility task is fetch-src which will download and extract a remote tar ball. The curl task is separated out to allow directly downloading any files.
checksum utils
Previously the checksum utils only operated on a single data path, which is an issue for tasks that generate files across multiple directories. This PR just changes the arguments to be an array of paths rather than a single path.
Validation performed
Used in ffi-go irv2 beta branch.

Summary by CodeRabbit

New Features

Enhanced checksum computation and validation tasks now support multiple input paths.
Introduced new tasks for CMake operations (cmake-build, cmake-install) and remote file handling (curl, download-and-extract-tar).

Bug Fixes

Improved error handling to prevent task failures during checksum operations.

Some quick high-level comments before a detailed review:
* The Rabbit has some suggestions that I think are valid.

* Can `fetch-src` replace CLP's [download-and-extract-tar](https://github.com/y-scope/clp/blob/53c4f52b3ae2ef0e990a8d66a7be87fd1e85cfbe/Taskfile.yml#L329)? If so, can we rename `fetch-src` to `download-and-extract-tar`?

* What docstring format are you basing things on?

New commits have added in Rabbit's suggestions, updated fetch-src to provide functionality of download-and-extract-tar (and renamed it), and updated docstrings based on disucssion.

Review incoming.


def optional parameters, long & short parameters, help messages for parameters

I was testing out #530 while porting my weather script to engine-q.
This works great.
def foo [x?:int] {
  if $x != $nothing {
    $x + 10
  } else {
    5
  }
}

But while trying to emulate that with multiple parameters I couldn't get it to work. I'm not sure if it's the ?, the spacing, the parameter delimiter, the comments, the long(short) params, so I tried a bunch of different things.
I've tried these:
space comma space between params
update: works 🎉
def foo3 [l?:int , u?:string] {
  let is_l = ($l == $nothing)
  let is_u = ($u == $nothing)
  $"l is ($is_l), u is ($is_u)"
}

comma space between params
update: works 🎉
def foo3 [l?:int, u?:string] {
  let is_l = ($l == $nothing)
  let is_u = ($u == $nothing)
  $"l is ($is_l), u is ($is_u)"
}

just space between params
update: works 🎉
def foo3 [l?:int u?:string] {
  let is_l = ($l == $nothing)
  let is_u = ($u == $nothing)
  $"l is ($is_l), u is ($is_u)"
}

params on separate lines
update: works 🎉
def foo3 [
l?:int
u?:string
] {
  let is_l = ($l == $nothing)
  let is_u = ($u == $nothing)
  $"l is ($is_l), u is ($is_u)"
}

params on separate lines with a comma
update: works 🎉
def foo3 [
l?:int,
u?:string
] {
  let is_l = ($l == $nothing)
  let is_u = ($u == $nothing)
  $"l is ($is_l), u is ($is_u)"
}

params on separate lines with parameter help messages
update: works 🎉
def foo3 [
l?:int # some param
u?:string # some other param
] {
  let is_l = ($l == $nothing)
  let is_u = ($u == $nothing)
  $"l is ($is_l), u is ($is_u)"
}

and what i really wanted to work, which was the first try
long(short) params, separate lines, param help messages
update: still does not work with $l or $locIdx 😢
def foo3 [
--locIdx?(-l): int # The location id 0-3
--units?(-u): string # The units "f" or "c"
] {
  let is_l = ($l == $nothing)
  let is_u = ($u == $nothing)
  $"l is ($is_l), u is ($is_u)"
}

all give this error
update: this is still true - you can't call the ones that work above like foo -l 3 -u "C" 😢
> foo3 -l
Error: nu::parser::unknown_flag (link)

  × The `foo3` command doesn't have flag `-l`.
   ╭─[entry #97:1:1]
 1 │ foo3 -l
   ·       ┬
   ·       ╰── unknown flag
   ╰────
  help: use foo3 --help for a list of flags

clearly i'm missing something fundamental because the foo example works.

All of the positional parameter test seem to work okay for me. Was there any other code involved outside of the example?

@fdncred - can you try these again with the latest e-q and see if you still see them?

@jntrnr i updated the issue above with an update line.

need to circle back eventually and perhaps give a better error message that ? isn't required for things like this.
def foo3 [
--locIdx?(-l): int # The location id 0-3
--units?(-u): string # The units "f" or "c"
] {
  let is_l = ($locIdx == $nothing)
  let is_u = ($units == $nothing)
  $"l is ($is_l), u is ($is_u)"
}

but for now, let's close it and move on.


fix: wrapper initialize in handler

Codecov Report

Merging #288 (81d4918) into master (2ce7c9e) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #288   +/-   ##
=======================================
  Coverage   87.93%   87.93%
=======================================
  Files          40       40
  Lines        3937     3938    +1
  Branches     1155     1156    +1
=======================================
+ Hits         3462     3463    +1
  Misses        437      437
  Partials       38       38

Impacted Files
Coverage Δ

packages/cli-plugin-scf/src/index.ts
88.67% <ø> (ø)

packages/serverless-spec-builder/src/wrapper.ts
87.28% <100.00%> (+0.10%)
:arrow_up:

Continue to review full report at Codecov.

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

beta下


[MINOR] [SQL] Ignores Thrift server UISeleniumSuite

This Selenium test case has been flaky for a while and led to frequent Jenkins build failure. Let's disable it temporarily until we figure out a proper solution.

cc @tianyi

Merged build triggered.

Merged build started.

Test build #33327 has started for   PR 6345 at commit 09996fe.

Test build #33327 has finished for   PR 6345 at commit 09996fe.

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

Merged build finished. Test PASSed.

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


Robot verification page displays an exception [mainland China]

Since Cloudflare is not using Google reCAPTCHA in mainland China, I am not sure if this issue is extensive.
https://steamdb.info/cdn-cgi/scripts/baidu.challenge.js

I removed the custom page.


email connector issue with new designer and save problem in new designer.

Describe the Bug with repro steps
We have identified the list of issues recently with new designer . 2 with Email connector and 2 in general view of designer.
ISSUE 1 :
Create a new email action using new designer .
It gets delivered without break and spaces when I had typed it to be with spaces.

When I create the same action with old designer , the mail is structured as it should be . The new designer is not adding the spaces rightly.

Also we  see tags such as  and  in the send email action  in designer view . In old designer we don't see such tags (.Tags are only added when the action is created using old designer ;with proper spacing and when you view in new designer it loads them as  , etc.)

Fallbackurl to old :

ISSUE 2 :
The runhistory of new designer makes it difficult to read in send email action .

old designer has structured message:

ISSUE 3 :
I do a  double click anywhere inside the designer (any action ) , the save button gets enabled !!
The workarounds for the above 3 issues are using fallback URL .
Home - Microsoft Azure
ISSUE 4 :
We are unable to copy the run ID from Logic app Standard. -no workaround for this
What type of Logic App Is this happening in?
Standard (Portal)
Are you using Preview Designer or GA Designer
Preview
Workflow JSON
No response
Screenshots or Videos
No response
Browser
edge
Additional context
No response

@shabMS thanks for reporting this issue, for the first 3 items this is a missing feature that we plan to get in our next release which can be tracked #1842, and as for the 4th issue, we can track the item with #2009


New Language ?

I searched the documentation for any instructions to add/create a new language.
Sorry if I missed something.
Please, what are the steps to add language to locale directory.
I was hoping to start with en_GB file and make a few small changes before saving as en_AU or en_US.
Seems there's no en_GB file/s in locale.
TIA's for any tips or clues.
Edit.  It looks like the following steps might be working ;

Create directory .../Locale/en_US
Create the file translations.php, containing ONLY the words/labels desired to be changed.  Omit all other words that can use defaults.

Am I doing this "the-right-way" (tm) ?

https://kanboard.net/documentation/translations

I had searched the official documentation for the string "language".  Sorry I missed the "translation" page.
Looking at "the-right-way" per documentation, I'm thinking my method my work better since it will likely survive any update to the file app/Model/Language.php (or its later equivalent).
Thx for helps.


Grid is collaped inside the tab control

Issue: ngx-datatable is collapsed inside the tab control
Step1 : Tabset have different tabs  Example : BIOSContnet,SiliconInfo
Step2 : when the user clicked on the tab loading the data based tab click.here grid is collapsed but data is binded.
Can please suggest and let me know where it went wrong?
Attached the sample code and issue (image) for your reference.
<tab *ngIf="selected_program_details && selected_program_details.length>0" tabindex="19"
(select)="GetChoosenTabData('BIOS')" heading="BIOS Content" id="tabBIOS">

                                        <fieldset>
                                            <legend> Choose Platform</legend>

                                                    <input tabindex="20" type="radio" name="bios_platform" value="{{plt}}"
                                                        [checked]="i==0" (change)="GetBIOSContents(plt)" /> {{plt}}

                                        </fieldset>

                                        <ngx-datatable class="bootstrap gridcommonheight100" id="ngx-bios" [rows]="build_bioscontents"
                                            [headerHeight]="30" [footerHeight]="30" [rowHeight]="30" [scrollbarV]="true"
                                            [columnMode]="'force'">
                                            <ngx-datatable-column name="Base BIOS" prop="BaseBIOS">
                                            </ngx-datatable-column>
                                            <ngx-datatable-column name="Custom BIOS" prop="CustomBIOS">
                                            </ngx-datatable-column>
                                        </ngx-datatable>

                            </tab>

The same issue. Any suggestions?

The issue is raised nearly 1 year back but no one is replied now.
Let me know any one is fixed the issue .It is really urgent

The issue is raised nearly 1 year back but no one is replied now.
Let me know any one is fixed the issue .It is really urgent

I fixed temporary this issue with a really awful patch : when i click on a tab, i emit a resize event :
    detectChange() {
        setTimeout(() => {
            window.dispatchEvent(new Event('resize'));
        }, 0);
    }

it's really really bad, but the job is done until a better way

Thank you


StateDiff mismatch in Nonce

Running Starknet Replay with state_dump, native vs VM, there is a mismatch in State's nonce track
Txs:

block747115/0x281d91c5ee939b6548e1e039b381b3f6e5c200f5808b3ef389bbbd6fdb0c6ec
block747122/0x469cd089b00448e2816aa799299bafc50d160850fd25f1d34c1926929833b05
block747113/0x6310e7dc70754b898689fd45a5242c8a6a97875c3634cae4d0bd27befe43194
block749209/0x770f05cb6d47bd3ce54422d06742b45da92d21f23f4f33b4cd4d00d501000b3

commits
Cairo Native: 82c25b377f50904e1253b614c8719388277530e6
Starknet replay: e125989afa77022995b3989c1d64292755312a87
blockifier = { git = "https://github.com/lambdaclass/sequencer", branch = "native2.8.x"},  1eaaa4b9902cd9f4a867b111ca87c3a3bfce5d29

I think 0x469cd089b00448e2816aa799299bafc50d160850fd25f1d34c1926929833b05 diff is caused by the previous tx (0x1575f53142109a24350541cf9a6019390f298478b0b2757157c818a3b74cf51). The previous tx reverts in Native, but not in CairoVM.
This is missed by the state dump feature as the unexpected error causes the state dump of 0x1575f53142109a24350541cf9a6019390f298478b0b2757157c818a3b74cf51 to not even be generated.

Cairo Native:2024-10-14T22:18:16.278546Z ERROR replay: execution failed unexpectedly: Transaction validation has failed:
0: Error in the called contract (
 contract address: 0x010b685e795f70a7fb32d473878154e38a2668372dfe5d01d6cbdd9309d1be7f,
 class hash: 0x032e17891b6cc89e0c3595a3df7cee760b5993744dc8dfef2bd4d443e65c0f40,
 selector: 0x0162da33a4585851fe8d3af3c2a9c60b557814e221e0d4f30ff0b2189d9c7775):
Native execution error: invalid-owner-sig

Cairo VM:2024-10-14T22:16:06.878264Z  INFO replay: execution finished successfully,
  transaction_hash: "0x1575f53142109a24350541cf9a6019390f298478b0b2757157c818a3b74cf51",
  chain: "mainnet",
  execution_status: "SUCCEEDED", rpc_execution_status: "SUCCEEDED",
  n_events_and_messages: "{ events_number: 4, l2_to_l1_messages_number: 0 }",
  rpc_n_events_and_msgs: "{ events_number: 4, l2_to_l1_messages_number: 0 }",
  da_gas: "{ l1_da_gas: 448, l1_gas: 0 }",
  state_changes_for_fee_str: "{ n_class_hash_updates: 0, n_compiled_class_hash_updates: 0, n_modified_contracts: 2, n_storage_updates: 5 }"

Fixed here
https://github.com/lambdaclass/starknet-replay/pull/75
https://github.com/lambdaclass/cairo_native/pull/874


Docs for contributing don't tell you to install docker buildx

While following the guide on this page I got stuck when running make images because gives weird unknown flag: --build-arg error, but installing the docker-buildx package on arch fixed it.

Oh, thanks! I think it's included with docker by default on a lot of systems, but maybe not arch. It's a good idea to add a note about this to the contributing docs. And I know it is a bit confusing, but it should be updated in the main repo, a github workflow will automatically update it here after.

I will take care of this update. I'm trying to practice and get comfortable contributing.

Should this issue be closed out now that I've worked on it and the changes accepted?

Yes, I just need to figure out why the workflow bot didn't replicate the changes. 🤔

We fixed it, we had forgotten to enable actions for this repo :sweat_smile:


[BUG]:Can't infer props from view in schema

What version of drizzle-orm are you using?
0.36.0
What version of drizzle-kit are you using?
No response
Describe the Bug
Can't use the type api from docs in views: https://orm.drizzle.team/docs/goodies#type-api
Example: https://drizzle.run/piy3qe6lr8d7eanurd3q191u
Expected behavior
No response
Environment & setup
No response

This one was fixed in latest<EMAIL_ADDRESS>


don't suppress the 'koji' plugin for module-only-composes

If resolve_composes was run to only compose modules, it would
still suppress the 'koji' plugin which handles adding the koji target
build tag repo to container builds. But modules assume that there's a base
package set coming from somewhere else. So, if we have a compose that only
involves modules, with no packages, pulp repos, inherited repourls, or
user-specified repourls, set the new force_tag_repo(*) parameter on the
client builds, to avoid suppressing the 'koji' plugin.
(*) https://github.com/containerbuildsystem/osbs-client/pull/956
Signed-off-by: Owen W. Taylor<EMAIL_ADDRESS>Maintainers will complete the following section:

[ ] Commit messages are descriptive enough
[ ] "Signed-off-by:" line is present in each commit
[ ] Code coverage from testing does not decrease and new code is covered
[ ] JSON/YAML configuration changes are updated in the relevant schema
[ ] Changes to metadata also update the documentation for the metadata
[ ] Pull request includes link to an osbs-docs PR for user documentation updates
[ ] New feature can be disabled from a configuration file

So far LGTM, please address CI errors

LGTM, but tests need fixing

No action is needed for the the failing tests (see containerbuildsystem/osbs-client#957). They should pass when the fixes for the linter warnings are pushed

Thanks! - was scratching my head how my changes could have anything to do with that failure.

Stickler linter errors seems unrelated to osbs-client, right?

Release notes:

don't skip koji plugin when no repos are defined/inherited for flatpak builds to work with modules which assume that there is a package set coming from somewhere else


fix(module:steps): fix steps width bug in tab component

close #83
PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Application (the showcase website) / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information

Coverage remained the same at 52.233% when pulling 450c95f871acd1a4e166f747a8efd42a8c6c35f0 on vthinkxie:nz-steps-fix into 2bcddc7458181567030ccb0d124189b6c2aa2363 on NG-ZORRO:master.


TeamsInfo.GetMeetingInfoAsync not working in OneToOne or Group call

We have tried calling the  await TeamsInfo.GetMeetingInfoAsync(turnContext);  in OneToOne and Group call but getting error as
The meetingId can only be null if turnContext is within the scope of a MS Teams Meeting.
In the doc it is mention that it is supported in one to one and group call and we have tried it in dev preview only-

Also in the API response details.type it is also mentioned that it can be OneToOne or Group call.

We have added both OnlineMeeting.ReadBasic.Chat and  ChannelMeeting.ReadBasic.Group permissions in manifest following the example but it's always giving error.
It is working fine in meeting only but failing in one to one and group call.
Please confirm if additional permission or configuration is required to run?

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

ID: 805dc242-7b5a-cc81-ee0e-6acf0078a653
Version Independent ID: 11c0e023-2514-9639-6052-2cbbbef50663
Content: Meeting apps API references - Teams
Content Source: msteams-platform/apps-in-teams-meetings/API-references.md
Service: msteams
GitHub Login: @surbhigupta
Microsoft Alias: lajanuar

@HunaidHanfee-MSFT - We have raised a bug for it. We will let you know once we have any update.


Adding and removing data in 2.0

The docs in the 2.0.0-beta and 2.0.0-dev branches say that adding and removing data can be done with addData and removeData methods. I do not see these in the Chart.js code though. Mentioned in another issue is the possiblity for a removeAllData method. But in another, a mention of adding data is by way of using the internal datasets.
Are the docs just out of date? And what's the proper way to add and remove data?

Also seen this. Neither addData() nor removeData() exist, but I have a new dataset that comes in and I'd like to update the chart. What's the best way of doing this?

We're working on official documentation for 2.0 as we speak. As for this question, we have improved the api for adding and removing data by actually removing the api.  All you need to do now is manipulate the existing data objects you passed, and call chart.update()!  Pretty simple, and it allows you to update your data objects however you see fit.

But @tannerlinsley if I look at the chart.js object, there are many places these data objects are stored:

chart.config
chart.scales.x-axis-0.data
chart.scales.y-axis-0.data
chart.data

(as far as I can tell from inspecting it at runtime).
Say I have some newData arriving, how do I update the chart?

Ok, here's my solution:
chart.data.labels = nextData.labels;
chart.data.datasets[0].data = nextData.datasets[0].data;
chart.update();

Technically the intended location for changes is the same data object you passed in your chart config.  Doing it any other way will work as well, as any data property on the chart object is merely a reference to the original. I hope that makes sense.
I would personally do this:
var config = {
  type: 'bar',
  options: {...}
  data: {...}
};

var myChart = new Chart(canvas, config)

config.data.datasets[0].data[0] = 10;

myChart.update();

Updated v2 documentation is available at http://nnnick.github.io/Chart.js/docs-v2/
After #1646 was merged, the entire data object can now be replaced and then update() is called.

That latest URL does not exist...


7: More Repetition, wrong exercise description

In the readme of 7: More Repetition in the exercise it is described that the macro if_any! should be implemented. But it actually should be hashmap!. The description what the macro should do is also wrong.
Probably a copy paste error of 6

Fixed by #4 :)


Migrate from ngx-translate

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[x] Feature request
[x] Documentation issue or request
[ ] Support request
[ ] Other... Please describe:

Current behavior
After running the migration from ngx-translate to transloco I noticed that a lot of translations did not work anymore.
The thing is that in my code I fetch a bunch of translations in a single statement, by passing the translation keys as array.
this.translateService.stream(['translation.key.one', 'translation.key.two']);

After converting the array remains in the transloco variant of the code, but this no longer works.
this.translateService.selectTranslate(['translation.key.one', 'translation.key.two']);

Expected behavior
First of all, I'm not sure what the equivalent of the array of keys is in transloco, but I think it should have been the following.
this.translateService.getTranslateObject('translation.key', {
  one: {},
  two: {}
});

Minimal reproduction of the problem with instructions
For bug reports please provide the STEPS TO REPRODUCE and if possible a MINIMAL DEMO of the problem, for that you could use our stackblitz example
What is the motivation / use case for changing the behavior?

Environment

Angular version: 8.2.14

Browser:
- [x] Chrome (desktop) version 80
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX

For Tooling issues:
- Node version: 13.10.1
- Platform:  Windows

Others:

'translation.key.one', 'translation.key.one' returns strings or objects?

'translation.key.one', 'translation.key.two' returns strings or objects?

they return strings

I tried it and it works. https://stackblitz.com/edit/ngneat-transloco-hzabmt?file=src%2Fapp%2Fhome%2Fhome.component.ts

stream and selectTranslate returns an observable. You need to subscribe.

@jochenjonc just to clarify, when passing several keys in ngx-translate stream function you get an object back? in transloco passing an array will resolve in an array with the translated strings.

I tried it and it works. https://stackblitz.com/edit/ngneat-transloco-hzabmt?file=src%2Fapp%2Fhome%2Fhome.component.ts

This works, and returns an array but the key is not availble, you cannot do the following:
console.log(v['some.nested.key'])

This works, but is not safe to use if you have a lot of keys:
console.log(v[0])

@jochenjonc just to clarify, when passing several keys in ngx-translate stream function you get an object back? in transloco passing an array will resolve in an array with the translated strings.

Correct, that is way I was wondering if it shouldn't be changed to:
this.translateService.getTranslateObject('translation.key', {
  one: {},
  two: {}
});

@jochenjonc I see. I will add a note in the migration file so people will know they need to change this to the selectTranslateObject (since stream returns an observable).
This will not be part of the migration script as of now, but you are welcome to extend it and create a PR 🙂

First of all thank you for the awesome lib =)
I am wondering, is any alternative to ngx-translate "extract" marker..
It is just empty function, but some strings can be marked in code without translation.
In transloco I can do it within special commend /** t(term) */ but in this case I have to repeat this term twice.. once in code and second time in comment. am I right? or there is something like 'extract' in ngx-translate?
thank you for support

@swayf Thanks for your support!
Let's take this in our gitter channel since it's not really related to this issue, you can always ask for help there 🙂

@jochenjonc I have updated our ngx-migration doc.
Closing this, thanks again for the report, feel free to open a PR and implement the functionality 🙂

Not directly related to original question, but to the ngx-translation migration - I haven't found anything on defining translation-keys in source-code.
For example with ngx-translate I have a service and define a member:
public readonly traslation_key( 'test' )
which then creates the key 'test' when running the e cli extractor tool. Is there something like this in transloco, or can i only define keys using the structural directive?

@FloNeu Have you seen the transloco keys manager

@shaharkazaz first, thx for the fast response...
yes, i have - but I took a look at it again... maybe I didn't get it first - are you referring to section
'dynamic keys' and that I should use these
*/** t(key.typeOne.postfix, key.typeTwo.postfix) */-comments?
for example, like:
/** t( test ) */ public readonly test
to have it picked up by the extractor? But how can I use the scope-features when I have this in
a service where there isn't a 'provider' section in the @Injectable()-Decorator?
My use-case is that i have a service-containing members representing my application routes, like so:
@Injectable( { providedIn: 'root' } )
export class RouteTranslationKeys {
  /** t(  route_home ) */  // Ok, yes that worked
  public readonly ROUTE_HOME = translation_key( 'route_home );
  // Maybe add as a feature request that it would be cool to have it also
  // work with function-style in code to have it clear that this performs a function
  // and people unfamiliar with transloco maybe delete translation-key comments
  public readonly ROUTE_LOGIN = translation_key( 'route_login' );
  constructor( ) {}
}

and i now try to get them into their own 'scope'-file.

@FloNeu I think that this feature is what you are looking for.

Yes indeed... that means it will be available soon. very nice... just short
question because I still have problems.
Key-Extractor only picks up keys from comments? or should it also pick up
the keys from normal use
within the t( 'key' ) function? Because i can't get this to work
Am Do., 3. Sept. 2020 um 20:30 Uhr schrieb Shahar Kazaz <
<EMAIL_ADDRESS>
@FloNeu https://github.com/FloNeu I think that this feature
https://github.com/ngneat/transloco-keys-manager/issues/59 is what you
are looking for.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ngneat/transloco/issues/252#issuecomment-686671593,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKPZ6CYVCNMF2BA4CF5YRLSD7OFPANCNFSM4LCGUHZA
.

@FloNeu Let's leave this thread since it's no longer related to the original issue.
If you have any questions you can try getting help in our gitter lobby or open an issue with reproduction in the keys manager repo.

Right. i will delete my comments shortly...


Can not concatenate SafeString

In Pebble 1.x I used to be able to concatenate the output of a macro with the output of another macro.  Something like:
{{ macro1() + macro2() }}

In Pebble 2.x I can no longer do that and I think the problem is this hunk of code which only checks for String and does not consider SafeString.

I added a proposed fix for this issue.


Narrow screen width hides some controls

I use my secondary monitor in portrait mode, but it's only 768px wide/high. Apparently Google decided that this screensize isn't important anymore. The global minimum width seems to be around 980px, while the controlbar minimum width is around 850px.
Result: you have to horizontally scroll to see playtimes and the queue and miniplayer buttons are completely hidden. This is the default behaviour on the normal web player as well.
Perhaps you could change this behaviour by removing the album art or scaling the controls?
A simpler option would be to allow us to set a default zoom level.

I'm working on documentation for this but you can actually set a zoom level (woo hoo).  Just use the shortcuts you would use in any other browser
Ctrl + --> Zooms in
Ctrl - --> Zooms out
Ctrl 0 ---> Resets Zoom


Mysql schema

Hi, I noticed there are 2 fields in matrix_users table, namely depth and number. May I know what should we put in number?? Is it the number of the position?

oh, I did not translate comments in the MySql schema, sorry.
depth - it is your level in the matrix.
number - your number in level.
For example:
.....0.....
...012...
0123456
This matrix consists of 3 levels. Each level has numbers.
Now we can work with coordinates. For example:
Level:1 number: 2
.....0.....
...01(x)...
0123456

Cool, now I got it. Great plugin to start with.
On Thu, Oct 17, 2019 at 5:43 AM Nepster<EMAIL_ADDRESS>wrote:

oh, I did not translate comments in the MySql schema, sorry.
depth - it is your level in the matrix.
number - your number in level.
For example:
.....0.....
...012...
0123456
This matrix consists of 3 levels. Each level has numbers.
Now we can work with coordinates. For example:
Level:1 number: 2
.....0.....
...01(x)...
0123456
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nepster-web/php-mlm-matrix/issues/9?email_source=notifications&email_token=AABQ5AEB6Y6EEHKYEDGCPIDQO6DJBA5CNFSM4JAWEKLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBOA7PY#issuecomment-542904255,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABQ5AG7U5NFVJJ43PQU3UDQO6DJBANCNFSM4JAWEKLA
.

--
Mohd Fadli Saad
<EMAIL_ADDRESS>|<PHONE_NUMBER> | fadli.my

Thank you.


FE / API Epic before next video release

It seems like perfecting the listing and history api may take a bit of time, so maybe we can focus on the main search and get to those later.
We can link this into other issues I may have created in the project.
Right now I think the top issues are:

~update react to send the universals_list_uid as an empty string and send filters as an array of ints instead of ints. https://github.com/ff14-advanced-market-search/saddlebag-with-pockets/issues/49~
~update the list of filters to show the new -2 and -3 filters https://github.com/ff14-advanced-market-search/Aetheryte/issues/62~

Top desires are:

getting scroll bars to always be visible  https://github.com/ff14-advanced-market-search/saddlebag-with-pockets/issues/26
~fix the out of stock check box, right now it wont send False if you uncheck that box in the options https://github.com/ff14-advanced-market-search/saddlebag-with-pockets/issues/43~
getting the different queries with different default search values working https://github.com/ff14-advanced-market-search/saddlebag-with-pockets/issues/3
~showing npc vendor links (low priority because we could also just use the workaround in dev right now)~

Fur Daddy checked out the site and likes it, I will sync with him soon to go over the details.


Add MD5 checksums to GUDB

Fixes #111.

@hofaflo let me know what you think. Since the checksums are not downloadable (I think), I just dropped them into a dict.


lambda: Allow setting postgres as the metastore

Give the user the full control over the lambda metastore uri.
Backwards compatible.

 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.

Thanks @tontinton for your contribution!
The reason why we forced the metastore to be S3 for now is because:

a Posgres instance is pretty much the absolute opposite of Lambda in terms of scalability. In particular, it doesn´t scale well to 0
setting up Lambda to work properly with long lived and VPC based Postgres connections requires a bit of extra work

Before offering this feature, I think we would need to:

implement and test a CDK script that sets up Quickwit Lambda functions that can connect to a database on VPC (e.g RDS)

maybe we can skip this step if we consider that publicly exposed databases  over SSL are now a "common enough" thing (Neon, Supabase Postgres...)

test how the Lambda function warm start behaves after a period of inactivity greater than the Postgres timeout
assess whether we should recommend the RDS proxy

What kind of tests have you performed on your end? Have you tried to run your change on a long running example? Can you tell us a bit more about your usecase?

I don't care about having a Postgres that scales to 0 (although I might migrate to neon in the future).
I just want to be able to have multiple of these lambdas running concurrently and not have data races.
I'm currently trying to have a setup where I use this lambda to run on every new S3 file, but also to have it run on already stored files in S3 (a bootstrap indexing pipeline of sorts), basically running a pool of these lambdas on old files, meaning I can't use the file backed metastore.
About RDS and proxies, I currently use AWS Aurora. I can easily point to it from my lambda, I just need this change of course to be able to do it.

Also, I just remembered Aurora also enables scaling to 0: https://aws.amazon.com/rds/aurora/serverless/
So why not allow for this lambda to run with postgres?

I'm currently trying to have a setup where I use this lambda to run on every new S3 file, but also to have it run on already stored files in S3 (a bootstrap indexing pipeline of sorts), basically running a pool of these lambdas on old files, meaning I can't use the file backed metastore.

Interesting use case! One small remark: I don't know how big your Lambda pool will be, but keep in mind that the Lambda compute is very expensive (10x an EC2 instance). So if you want to process 100s of GBs, you would probably get away for a fraction of the price by spinning up a cluster for your backfill. We are about to publish a new file source that uses SQS based S3 notifications. We could very well imagine a hybrid setup where your backfill is performed by an ECS cluster but your continuous low volume ingestion is done by AWS Lambda (this would still require Postgres to enable the concurrency between the writers)

About RDS and proxies, I currently use AWS Aurora. I can easily point to it from my lambda, I just need this change of course to be able to do it.

 Have you performed more sustained tests on this? My concern is about Postgres connections with Lambda containers that were paused for a couple of minutes (warm starts), and how the metastore client recovers in that case.

Also, the Lambda feature is in beta, so I would rather avoid retro compatibility dis-junctions and make a breaking change if we decide to go in this direction.

I see, you say I should create a temporary cluster for the backfill, and that in the near future we'll be able to simply point quickwit to an SQS stream of events instead of using this lambda.
Very nice! Looking forward to the release.
I haven't tested my setup yet, still in the design stage, but your concern on connections being kept alive is valid. Couldn't we set a connection timeout to the metastore with quickwit to solve this? Maybe this is also a change that should be made?
Also is it really a problem? I'm fine with having multiple connections alive to my postgres currently.
Lastly, I want to ask you: What do you think is the simplest way to solve the backfill problrm until the SQS release? I thought the lambda pool was simple (albeit a bit expensive), maybe the ECR solution is the simplest? How do I configure it to index the old files?

Shouldn't Quickwit reopen the connection on a cold start?

On cold start, yes. On a warm start the behavior should be tested.

What do you think is the simplest way to solve the backfill problem until the SQS release?

This is a bit off topic for this issue, but right now we don´t have a straightforward way to do it. I think the easiest would be to use the local ingest  (using an S3 URI as file is not well documented but should work). You would need to come up with a simple script that runs a controlled number of them in parallel using a thread pool (a few lines of Python with concurrent.futures.ThreadPoolExecutor and subprocess should do the trick). Running one ingest process every 4 cores should give you the best hardware usage (provided that you are in the same region as your S3 files).

Ok thanks, I'll close the PR for now, and if I'll get to test the warm start, I'll reopen without backwards compatibility.

note: I tested it and the support for S3 URIs from the CLI is not supported in the current release. To ingest files from s3 you would need to copy them to your local filesystem in the script first. It will be supported in the new release!


No Fullscreen at Vimeo and Youtube on default

Hey,
i am adding the videos by help of the code:
{{ embed.safeHtml|raw }}
Soo far so fine, but for Vimeo and YouTube Videos no Fullscreen is available.
Is there a possibility? For example something i can put into the parameters in the plugin settings in craft itself?
Best Regards,
Marcel

@benjamminf  so no idea dude how to solve this?
best,
marcel

Isn't this a dup of #40?

But still no solution i guess right?

No, but I would close this issue and comment on that one.
My guess it's an attribute in the HTMLPurifier_Config that needs to be allowed.

@awcross  thx. i will close it

@awcross is right, the HTML purifier removes it. If you're okay with the slight security risk, you can use the html attribute which doesn't purify the embed data.


EgorBot for EgorBo in #52

Processing https://github.com/EgorBot/runtime-utils/issues/52#issuecomment-2325344969 command:
Command
-profiler --runtimes net9.0
using BenchmarkDotNet.Attributes;
using System.Collections.Generic;

public class Bench
{
    List<string> _list = new() { null };

    [Benchmark]
    public void Test() => _list[0] = "hi";
}

(EgorBot will reply in this issue)

Benchmark results on Intel
BenchmarkDotNet v0.14.0, Ubuntu 22.04.4 LTS (Jammy Jellyfish)
Intel Xeon Platinum 8370C CPU 2.80GHz, 1 CPU, 16 logical and 8 physical cores
  Job-SSOLAX : .NET 9.0.0 (<IP_ADDRESS>507), X64 RyuJIT AVX-512F+CD+BW+DQ+VL+VBMI
Runtime=.NET 9.0  Toolchain=net9.0  StdDev=0.0098 ns

Method
Mean
Error

Test
3.971 ns
0.0110 ns

BDN_Artifacts.zip
Flame graphs: Main vs PR 🔥
Hot asm: Main vs PR
Hot functions: Main vs PR
Counters: Main vs PR
For clean perf results, make sure you have just one [Benchmark] in your app.

cc @EgorBo (logs)


Bugs in navigating from model to dashboard when iterating on the model file

Bugs in navigating from model to dashboard when iterating on the model file
- screen was going blank

this bug didn't have any additional context. We'll try to reproduce with these steps


Problem while installing python-relic via pip

I tried to install python-relic with this command "pip install python-relic" on VSCode with Python 3.12 and latest version of pip but
I encountered this error: "It's not possibile to open the inclusion file: 'relic/relic_core.h': No such file or directory",
"Could not build wheels for python-relic, which is required to install pyproject.toml-based projects".
What can I do?
Thanks a lot ;)

@sebastinas

Thank you, but on the  https://github.com/relic-toolkit/relic in the wiki session, they suggest to run CMake with this command:
cmake ../relic- but idk where download relic library to run this command.

Ok thank you, i've just found the latest release but I still have problem with build and install relic, i get
make: *** "No rule to make target ';'. Stop.

That's probably best discussed with @dfaranha or somebody else from the relic project.

@sebastinas

Most of the functions and types have docstrings and there are some examples in the examples folder.

Solved by using WSL


Makefile supported?

Hello,
Here I have a question about debugging.
I'm using a Makefile with make install command to deploy the app to Roku device in my project.
Is this supported in this extension to debug?
Thanks.

The extension needs to be in control of creating the zip and deploying it to the Roku.
If your build process is simply zip creation and deployment, then you can use the files array in the vscode launch config to specify the list of files and you're good.
If your make process is more involved, then you will need to customize your make process to place all your files into a staging directory and then point vscode's rootDir launch config parameter to that directory.

Closing this since I believe the question has been answered.


suggestion: use 24-hour clock instead of AM/PM

Fr, 9 Sep 12am
First Anniversary Celebration: Neevo. Cosmic-danc, tropical-rock, afro-disco
Su, 11 Sep 12am
First Anniversary Celebration: DJ OMG Luc, Mach Schnell, Brl. Spicy bubblegum, garage, r'n'r

Events that start at midnight are displayed as 12am which this is rather confusing and not correct: https://www.quora.com/Is-12-00-at-midday-12pm-or-12am
😬✌🏽

The Quora post you linked is about midday, but the examples are for midnight. When using the am/pm notation then "12am" seems to be what's commonly used.
But I agree that am/pm notation might not be the best idea, since most website visitors will be used to the 24h format.
@patrickwermelinger wdyt?

Overview from Wikipedia:

https://en.wikipedia.org/wiki/12-hour_clock#Confusion_at_noon_and_midnight


chore: replace lint-staged with nano-staged

Nano Staged knows how to run commands to changed files between two index. This will help speed up the format of the workflows test.
You can test it yourself! Thank!

@usmanyunusov Could you please rebase your branch on latest dev?
This will fix the CLA signing again.


Feature request for addition in contributing guidelines

Is your feature request related to a problem? Please describe.
The contributions guidelines help a new open-source programmer to contribute to this project. However when there are changes in the remote repository and it's not reflected in local computers, then a lot of confusion arises. So there should be guidelines to fetch updated repository.
Describe the solution you'd like
Addition of points stating using the fetch and upstream command to update local repository.
Describe alternatives you've considered
Addition of Github docs links related to resolving conflicts in contributing.md file.
Approach to be followed (optional)
Add the following points:

Add a reference to the original repository.

git remote add upstream https://github.com/Neilblaze/Anyxz.git

Check the remotes for this repository.

git remote -v

Always take a pull from the upstream repository to your master branch to keep it at par with the main project(updated repository).

git pull upstream master

Umm I don't it's that necessary? Cause I guess, it's there in the NWOC Get started Guide.

In NWOC Get Started guide the guidelines are only until creating a pull request. They have not given what to do in case a person's repo is behind the main remote repo.


Segmentation fault upon syntax error

I'm using grunt-sass to compile several files across my project. If there are no syntax errors, everything runs smoothly. If I run into a syntax error or any similar error, I encounter a segmentation fault. I've used node-segfault-handler to get the following log:
PID 25667 received SIGSEGV for address: 0x0
0   segfault-handler.node               0x0000000101ce91c8 _ZL16segfault_handleriP9__siginfoPv + 280
1   libsystem_platform.dylib            0x00007fff882e952a _sigtramp + 26
2   binding.node                        0x000000010893f9d8 _ZN4Sass15names_to_colorsE + 30520
3   binding.node                        0x0000000108825b45 _ZN4Sass13color_to_nameEd + 31
4   binding.node                        0x0000000108893522 _ZN4Sass7InspectclEPNS_5ColorE + 968
5   binding.node                        0x00000001088908fb _ZN4Sass7InspectclEPNS_11DeclarationE + 207
6   binding.node                        0x00000001088a035f _ZN4Sass6OutputclEPNS_7RulesetE + 1185
7   binding.node                        0x0000000108890383 _ZN4Sass7InspectclEPNS_5BlockE + 149
8   binding.node                        0x00000001088357d6 _ZN4Sass7Context6renderEPNS_5BlockE + 50
9   binding.node                        0x00000001088d2a7d sass_compiler_execute + 107
10  binding.node                        0x00000001088d2697 _Z20sass_compile_contextP12Sass_ContextPN4Sass7ContextE + 34
11  node                                0x000000010096e28a worker + 90
12  node                                0x000000010097a494 uv__thread_start + 25
13  libsystem_pthread.dylib             0x00007fff967e999d _pthread_body + 131
14  libsystem_pthread.dylib             0x00007fff967e991a _pthread_body + 0
15  libsystem_pthread.dylib             0x00007fff967e7351 thread_start + 13

The issue also seems connected to how many files or how many @import statements are being processed. If I move all the files out of the watched directories and leave just one file, it fails on syntax error just fine without a segfault. If I add two, three, four files with just a few imports, it's still fine. But then I add another file with a lot of imports, and the segfault appears again. If I leave that last file where the segfault was just introduced, and I remove all the others, there's no issue, so it doesn't appear to be connected to particular files.
I've searched for solutions to this issue for a while but I've picked up on few patterns between the failures and none of the other Sass segfault solutions out there have worked. I've tried:

rm -rf node_modules && npm cache clear && npm install
Downgrading grunt-sass to previous versions (which track previous versions of node-sass)
Downgrading node to previous versions
Disabling sourcemaps

@montchr can you try to prepare some minimal case to reproduce the problem?

Okay I've been able to track it down to @importing partials with color gradients.
https://gist.github.com/montchr/2d725069a91abc25f8db3462342f98f6
The main _colors.scss file in the Gist contains a set of three rules repeated several times throughout the file, originally sourced from the Spectrum project's spectrum.css.
There are some other files:

valid.scss: Imports _colors.scss and that's it
invalid.scss: introduces invalid syntax to trigger an error, then imports _colors.scss
Gruntfile.js

If the set of three rules in _colors.scss only appear once, I don't run into an issue. If they appear three times, then Sass causes a segfault occasionally. After six repetitions of the three rules, segfaults happen 100% of the time.
Two important things to note:

I still get segfaults if I paste the contents of _colors.scss into the two other scss files, but here it's in a partial for clarity
If there's an error in both valid.scss and invalid.scss, I do not get a segfault at all

I'm running node-sass 3.8.0 and libsass v3.3.6 on macOS 10.11.6

As a side note, I've searched my project and its libraries for references to gradient and DXImageTransform and I've disabled all those sections of code. However, I'm still experiencing segfaults. Even with the segfault logger enabled, I don't see an error message or any indication of the segfault besides the grunt-sass process hanging and requiring me to close the terminal window.

The good news is that with
sassc: 3.3.6-11-g077a
libsass: 3.3.6-92-g014a61
sass2scss: 1.0.6
sass: 3.4

I cannot reproduce this problem anymore. Running sassc invalid.scss produces:
Error: Invalid CSS after "f": expected 1 selector or at-rule, was "fnord"
        on line 1 of invalid.scss
>> fnord
   ^

Running node-sass (on FreeBSD):
node-sass	3.8.0	(Wrapper)	[JavaScript]
libsass  	3.3.6	(Sass Compiler)	[C/C++]

The output is:
{
  "formatted": "Error: Invalid CSS after \"f\": expected 1 selector or at-rule, was \"fnord\"\n        on line 1 of invalid.scss\n>> fnord\n   ^\n",
  "message": "Invalid CSS after \"f\": expected 1 selector or at-rule, was \"fnord\"",
  "column": 1,
  "line": 1,
  "file": "/home/saper/sw/sass-bug-test/2d725069a91abc25f8db3462342f98f6/invalid.scss",
  "status": 1
}

Can you check what are you getting just by running node-sass invalid.scss ?

With node-sass invalid.scss I get the same as you:
{
  "formatted": "Error: Invalid CSS after \"f\": expected 1 selector or at-rule, was \"fnord\"\n        on line 1 of invalid.scss\n>> fnord\n   ^\n",
  "message": "Invalid CSS after \"f\": expected 1 selector or at-rule, was \"fnord\"",
  "column": 1,
  "line": 1,
  "file": "/Users/montchr/Sites/node-sass-issue-1672/invalid.scss",
  "status": 1
}

Can you check if grunt is not installing an older version of node-sass by chance?

I have used the following package.json:
{
  "name": "2d725069a91abc25f8db3462342f98f6",
  "version": "1.0.0",
  "description": "",
  "main": "Gruntfile.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "repository": {
    "type": "git",
    "url": "git+https://gist.github.com/2d725069a91abc25f8db3462342f98f6.git"
  },
  "keywords": [],
  "author": "Marcin Cieślak<EMAIL_ADDRESS>  "license": "ISC",
  "bugs": {
    "url": "https://gist.github.com/2d725069a91abc25f8db3462342f98f6"
  },
  "homepage": "https://gist.github.com/2d725069a91abc25f8db3462342f98f6",
  "dependencies": {
    "grunt": "^1.0.1",
    "grunt-sass": "^1.2.1"
  }
}

and after npm install (with node v6.2.2 and npm 3.9.2) I get the following:
> ./node_modules/.bin/grunt sass
Running "sass:dev" (sass) task
>> Error: Invalid CSS after "f": expected 1 selector or at-rule, was "fnord"
>>         on line 1 of invalid.scss
>> >> fnord
>>    ^
Warning:  Use --force to continue.

Aborted due to warnings.

grunt-sass is installing 3.8.0 as well.
My package.json:
{
  "name": "node-sass-issue-1672",
  "version": "1.0.0",
  "main": "Gruntfile.js",
  "author": "Chris Montgomery",
  "private": true,
  "devDependencies": {
    "grunt": "^1.0.0",
    "grunt-sass": "^1.2.1"
  }
}

I should also mention that a collaborator on my project is working with the same set of files and they're getting segmentation faults as well. This issue only appeared for us in the past couple weeks, but even with the minimal project in my gist and clearing out node_modules there I still get segmentation faults.

er, can you take nvm out of the way?

Since it looks like an environmental issue to me, can you please follow https://github.com/sass/node-sass/blob/master/TROUBLESHOOTING.md and post the output?

I downgraded to 5.5.12 and I still get the issue.
Here's the output of some of those commands. If you want me to run anything else let me know.
$ npm -v
3.10.3

$ node -v
v6.4.0

$ node -p process.versions
{ http_parser: '2.7.0',
  node: '6.4.0',
  v8: '<IP_ADDRESS>',
  uv: '1.9.1',
  zlib: '1.2.8',
  ares: '1.10.1-DEV',
  icu: '57.1',
  modules: '48',
  openssl: '1.0.2h' }

$ node -p process.platform
darwin

$ node -p process.arch
x64

$ ./node_modules/.bin/node-sass --version
node-sass       3.8.0   (Wrapper)       [JavaScript]
libsass         3.3.6   (Sass Compiler) [C/C++]

$ node -p "console.log(require('node-sass').info)"
node-sass       3.8.0   (Wrapper)       [JavaScript]
libsass         3.3.6   (Sass Compiler) [C/C++]
undefined

What happens if you run ./node_modules/.bin/node-sass invalid.scss ?

That's what I ran above actually:
{
  "formatted": "Error: Invalid CSS after \"f\": expected 1 selector or at-rule, was \"fnord\"\n        on line 1 of invalid.scss\n>> fnord\n   ^\n",
  "message": "Invalid CSS after \"f\": expected 1 selector or at-rule, was \"fnord\"",
  "column": 1,
  "line": 1,
  "file": "/Users/montchr/Sites/node-sass-issue-1672/invalid.scss",
  "status": 1
}

Can you post the full output of ./node_modules/.bin/grunt -v sass ?

$ node_modules/.bin/grunt -v sass
Initializing
Command-line options: --verbose

Reading "Gruntfile.js" Gruntfile...OK

Registering Gruntfile tasks.
Initializing config...OK

Registering "grunt-sass" local Npm module tasks.
Reading /Users/montchr/Sites/node-sass-issue-1672/node_modules/grunt-sass/package.json...OK
Parsing /Users/montchr/Sites/node-sass-issue-1672/node_modules/grunt-sass/package.json...OK

node-sass      	3.8.0  	(Wrapper)      	[JavaScript]
libsass        	3.3.6  	(Sass Compiler)	[C/C++]

Loading "sass.js" tasks...OK
+ sass
Loading "Gruntfile.js" tasks...OK
>> No tasks were registered or unregistered.

Running tasks: sass

Running "sass" task

Running "sass:dev" (sass) task
Verifying property sass.dev exists in config...OK
Files: _colors.scss -> dist/css/_colors.css
Files: invalid.scss -> dist/css/invalid.css
Files: valid.scss -> dist/css/valid.css
Options: precision=10, includePaths=["assets/vendor"]
Options: precision=10, includePaths=["assets/vendor"]
Options: precision=10, includePaths=["assets/vendor"]
>> Error: Invalid CSS after "f": expected 1 selector or at-rule, was "fnord"
>>         on line 1 of invalid.scss
>> >> fnord
>>    ^
Warning:  Use --force to continue.

Aborted due to warnings.
[1]    82592 segmentation fault  node_modules/.bin/grunt -v sass

I also created a new user account on my machine and tested there. I still get a segfault, but with a slightly different message Segmentation fault: 11.

Thanks. It seems that the node (JavaScript) thread continues normally and we are getting the error message back. The back-end libsass thread crashes though. Looks like a race condition somewhere. Unfortunately, I cannot reproduce this locally on my systems, so I might need access to a Mac to troubleshoot this.

@xzyfer can you reproduce this as well?

The "condition" is probably just grunt-sass running multiple instances of render. It does an async forEach over the set of matched files. It's probably one instance segfault'ing but the loop continues through the rest of the files.

Reproducible with Node v5.10.1
➜  tmp ./node_modules/.bin/node-sass -v
node-sass	3.8.0	(Wrapper)	[JavaScript]
libsass  	3.3.6	(Sass Compiler)	[C/C++]

Confirmed this issue is present going to back to<EMAIL_ADDRESS>

Thanks. The stacktrace also points to the color name conversion routines. In my file there are two files that grunt tries to process, valid.scss and invalid.scss. Do we also get a segmentation fault when there is only one file to be processed?

Do we also get a segmentation fault when there is only one file to be processed?

If I change src to process only invalid.scss I do not get a segmentation fault.

I have been able to confirm the issue is only present when colors"` is present. Inline that code into the scss files does not produce the segfault.

Actually I've found that if I copy the contents of _colors.scss into the two other files, I still get a segmentation fault as mentioned later in https://github.com/sass/node-sass/issues/1672#issuecomment-241207842. At first I thought it was @importing only but later realized that was a mistake. Should have edited my comment to reflect that.

Actually I've found that if I copy the contents of _colors.scss into the two other files, I still get a segmentation fault as mentioned towards the end

@montchr I saw this comment but was not able to reproduce the segfault in that case

Do we also get a segmentation fault when there is only one file to be processed?

I was not able to reproduce the segfault in this case.

I also tried executing multiple instances of the node-sass cli in a loop and was not able to reproduce this. Would be good if you could confirm this @saper.

Thanks @xzyfer, this is helpful. This is probably related to multiple parallel calls to render() and to reproduce this one needs to run them within one process. Probably it can be reproduced with a simple async loop that invokes render four times in parallel. This is as I understand the way grunt behaves for us here.
I have two theories why it fails, the pessimistic one is that we got bitten by mixing of C++ on MacOS, we use a modern C++11 library when compiling libsass and the stock GNU one to talk to node, as explained in https://github.com/sass/node-sass/pull/1110
I can't reproduce this at all on other platforms, unfortunately.

I ran into an extremely similar issue today using node v12.6.0, node v12.13.0 and node v13.1.0, with node-sass v4.13.0. It occurs even after completely fresh npm installs, on my and my colleague's OS X machines and in our Docker based GitLab runners. Coincidentally my stack trace also includes name_to_color even though the error occurs on an import error:
MartijnHols-MacBook-Pro:layout martijnhols$ tsdx build
✓ Creating entry file 3.6 secs
(postcss plugin) Error: File to import not found or unreadable: ../breakpoints.
Error: File to import not found or unreadable: ../breakpoints.
    at options.error (/Users/martijnhols/Workspace/react-components/node_modules/node-sass/lib/index.js:291:26)

PID 7693 received SIGSEGV for address: 0x0
0   segfault-handler.node               0x0000000102ae6066 _ZL16segfault_handleriP9__siginfoPv + 310
1   libsystem_platform.dylib            0x00007fff785d6b5d _sigtramp + 29
2   binding.node                        0x0000000107858efc _ZNKSt3__14lessINS_12basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEEEEclERKS6_S9_ + 98
3   binding.node                        0x0000000107837aed _ZNKSt3__16__treeINS_12__value_typeIPKcPKN4Sass5ColorEEENS_19__map_value_compareIS3_S8_NS4_11map_cmp_strELb1EEENS_9allocatorIS8_EEE4findIS3_EENS_21__tree_const_iteratorIS8_PNS_11__tree_nodeIS8_PvEElEERKT_ + 45
4   binding.node                        0x00000001078374ae _ZN4Sass13name_to_colorERKNSt3__112basic_stringIcNS0_11char_traitsIcEENS0_9allocatorIcEEEE + 133
5   binding.node                        0x00000001078ed66c _ZNK4Sass6Parser15color_or_stringERKNSt3__112basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEE + 32
6   binding.node                        0x00000001078ec007 _ZN4Sass6Parser11parse_valueEv + 1301
7   binding.node                        0x00000001078e8fef _ZN4Sass6Parser12parse_factorEv + 2379
8   binding.node                        0x00000001078e7eee _ZN4Sass6Parser15parse_operatorsEv + 136
9   binding.node                        0x00000001078e642c _ZN4Sass6Parser16parse_expressionEv + 140
10  binding.node                        0x00000001078f339c _ZN4Sass6Parser22parse_media_expressionEv + 472
11  binding.node                        0x00000001078f2b87 _ZN4Sass6Parser17parse_media_queryEv + 595
12  binding.node                        0x00000001078d9da1 _ZN4Sass6Parser19parse_media_queriesEv + 213
13  binding.node                        0x0000000107870e1b _ZN4Sass6ExpandclEPNS_11Media_BlockE + 583
14  binding.node                        0x000000010786fd4f _ZN4Sass6Expand12append_blockEPNS_5BlockE + 183
15  binding.node                        0x000000010787320b _ZN4Sass6ExpandclEPNS_2IfE + 353
16  binding.node                        0x000000010786fd4f _ZN4Sass6Expand12append_blockEPNS_5BlockE + 183
17  binding.node                        0x00000001078731c5 _ZN4Sass6ExpandclEPNS_2IfE + 283
18  binding.node                        0x0000000107877735 _ZN4Sass6ExpandclEPNS_10Mixin_CallE + 3147
19  binding.node                        0x000000010786fd4f _ZN4Sass6Expand12append_blockEPNS_5BlockE + 183
20  binding.node                        0x0000000107874f35 _ZN4Sass6ExpandclEPNS_4EachE + 3343
21  binding.node                        0x0000000107877735 _ZN4Sass6ExpandclEPNS_10Mixin_CallE + 3147
22  binding.node                        0x000000010786fd4f _ZN4Sass6Expand12append_blockEPNS_5BlockE + 183
23  binding.node                        0x000000010786fc02 _ZN4Sass6ExpandclEPNS_5BlockE + 384
24  binding.node                        0x00000001078491a8 _ZN4Sass7Context7compileEv + 522
25  binding.node                        0x0000000107848e4d _ZN4Sass12Data_Context5parseEv + 833
26  binding.node                        0x00000001079088f3 sass_compiler_parse + 192
27  binding.node                        0x00000001079086b1 _ZL20sass_compile_contextP12Sass_ContextPN4Sass7ContextE + 26
28  node                                0x00000001008650da worker + 196
29  libsystem_pthread.dylib             0x00007fff785df2eb _pthread_body + 126
30  libsystem_pthread.dylib             0x00007fff785e2249 _pthread_start + 66
31  libsystem_pthread.dylib             0x00007fff785de40d thread_start + 13
Segmentation fault: 11

We're using tsdx and rollup-plugin-postcss to build the code. The rollup-plugin-postcss uses 4 threads by default, but setting that to 1 does not fix the issue. I can reproduce this in my pipelines running on a node:12.6 Docker image, so this doesn't appear to be an OS X exclusive issue.

Can you produce a minimal reproduction case?

Looks like I was running into 2 issues, and I might have concluded too soon that they're all caused by the segmentation fault. Upon making a reproduction repository I learned that the segmentation fault seems to indeed only be reproducible on macOS.
The other issue completely freezes the build process upon process.exit(x). This appears to only be reproducible when doing multiple builds in parallel and this is the only thing that I could reproduce with GitHub Actions. You can see this here: https://github.com/EmicoEcommerce/node-sass-segfault-repro/runs/311335174 (I set a timeout of 15 minutes, so look for cancelled jobs). I have no idea what causes this, but I think its cause might be similar to the segmentation fault.
I made a reproduction repository with minimal SASS code and minimal build configuration to reproduce these two issues. I also configured GitHub Actions to make debugging easier (see the actions tab on the repository). There is also a readme with steps to reproduce, possible outcomes and my observations. You can find it all here: https://github.com/EmicoEcommerce/node-sass-segfault-repro

Great, thanks! Regarding hanging processes - I think this might be the architectural problem we are facing documented in #857. Can you try a workaround as documented there with environment variable and see if that helps?

Split out the parallel imports problem to #2789

Your segmentation fault looks to me like stack overflow. I can generate a crash setting ulimit -s 80 on my FreeBSD, don't know if this is the same.
https://github.com/libuv/libuv/issues/669 MacOS X was affected by a small stack size, and it is known that alpine has very small stacks, too. See also https://github.com/libuv/libuv/pull/2310 https://github.com/libuv/libuv/issues/1507

I have another theory:
From the backtraces we can see that Exception::NestingLimitError is about to be thrown.
It looks to me that we explicitly turn off exception handling for MacOS X in binding.gyp.
Could anyone with Mac OS X rebuild the binding with 'GCC_ENABLE_CPP_EXCEPTIONS': 'YES' instead and see if this continues to crash?
Do we have a test case for the nesting error?

Seems like that using catch throw in the gdb and stopping on C++ allows me to finish the program even with parallel builds. Maybe C++ exceptions and multiple libsass threads (#2789) do not go well together.

On non-macOS systems we also inherit -fno-exceptions from node:
clang++ '-DNODE_GYP_MODULE_NAME=binding' '-DUSING_UV_SHARED=1' '-DUSING_V8_SHARED=1' '-DV8_DEPRECATION_WARNINGS=1' '-DV8_DEPRECATION_WARNINGS' '-DV8_IMMINENT_DEPRECATION_WARNINGS' '-D_LARGEFILE_SOURCE' '-D_FILE_OFFSET_BITS=64' '-DBUILDING_NODE_EXTENSION' -I/usr/local/include/node -I/usr/local/src -I/usr/local/deps/openssl/config -I/usr/local/deps/openssl/openssl/include -I/usr/local/deps/uv/include -I/usr/local/deps/zlib -I/usr/local/deps/v8/include -I../node_modules/nan -I../src/libsass/include  -fPIC -pthread -Wall -Wextra -Wno-unused-parameter -m64 -O3 -fno-omit-frame-pointer -fno-rtti -fno-exceptions -std=gnu++1y -std=c++0x -MMD -MF ./Release/.deps/Release/obj.target/binding/src/sass_types/number.o.d.raw -I/usr/local/include -g -c -o Release/obj.target/binding/src/sass_types/number.o ../src/sass_types/number.cpp

Could anyone with Mac OS X rebuild the binding with 'GCC_ENABLE_CPP_EXCEPTIONS': 'YES' instead and see if this continues to crash? cc @xzyfer

I think I did this right: clone, install, change that value in binding.gyp, build, npm link, verify it uses the correct binary by reading the output of npm rebuild node-sass in the target repo.
I don't see a difference when using that binary.


Escaping brackets {

We want to be able to have { inside of strings.
Perhaps {{ --> { as escape?

Yeah, good idea


Wrong input from multipart/form-data

Hi,
If I send input with ampersand sign from a form with files: true, I only get the part before the & sign.
So as a simple test 1&2 becomes 1.
My problem is I need to submit encoded html values from an editor, which only get received until the first & entity.
Thanks,
András

Mind sharing the code where you are reading these values?

I read a list of related datas, but its simply
description = request.input(`description-${i}`, '')
console.log(description)

If my input was 1&2, 1 is logged to the console.
In Chrome Dev Tools is see
------WebKitFormBoundarypbXmRTmeTjxIfZrM
Content-Disposition: form-data; name="description-0"

1&2

I created a new empty project.
routes.js:
'use strict'

const Route = use('Route')

Route.get('/', 'TestController.index')
Route.post('/', 'TestController.print')

TestController:
'use strict'

class TestController {
  * index (request, response) {
    yield response.sendView('welcome')
  }

  * print (request,response) {
    response.send(request.input('stuff'))
  }
}

module.exports = TestController

welcome.njk:
{% extends 'master' %}

{% block content %}
  {{ form.open({ action: 'TestController.print', files: true }) }}
    {{ csrfField }}
    <input name="stuff" />
    <input type="submit" />
  {{ form.close() }}
{% endblock %}

It acts the same way. Works fine without files: true.

Identified bug, working on the fix

This issue was moved to adonisjs/adonis-middleware#10


docker compose 'context' is case sensitive

https://github.com/amancevice/pandas/blob/a0d98a24800ef5122aae5de1b46e1822bed13f04/docker-compose.yml#L17
jupyter should be replaced by Jupyter

Weird, but I think I’ll change the folder name instead. Thanks for raising.


Add Postgres version requirement

Making this implicit requirement explicit!

Just to document one reason why Postgres 14+ is required, @lognaturel wrote on Slack:

From @eyelidlessness about postgres 14 now being required: it’s about keywords that now can be used as column labels without AS

-- Syntax error in 12, 13
SELECT '' action;

-- No syntax error in 14+
SELECT '' as action;
SELECT '' "action";