How to render fire stations

Fire stations are one of the last 'community anchor' POIs (#435) for the style to render. There is no one clear iconography associated with them IMO, so I think we could go a number of directions. Therefore, I thought I'd create an issue to discuss possibilities before starting a PR. A few of the options as I see them (further ideas welcome!):

A classic one used in other OSM maps is a flame icon. This is the approach of e.g. Carto, Maki, and OSMAnd. I find this somehow both intuitive (obviously it's fire) and counter-intuitive (wait, don't firefighters put out fires?!?). It also could be confused with legitimate fire icons we might want in the future, like for firepits.

Another option would be a fire truck symbol. This more clearly represents firefighters to me, and would be pretty recognizable iconography. It might be a challenge to get a good looking 20x20px symbol though. One model might be MUTCD W11-8:

One other option that could work is the "Firefighter's cross", something like below. This would have a nice synergy with our badge symbol for police stations. I don't know whether it's widely associated with firefighters outside the US, or recognizable enough on its own. Maybe with the flame in the center?

Are there other symbols commonly associated with firefighters, but not easily confused with the literal object? Some things that came to mind are hoses, axes, and ladders, but I don't think those would be very clear/distinctive. Maybe those distinctively shaped hats could work?

Anyways, curious what others think.

The first thing that came to my mind was the hat but I wonder if it's distinct enough from other hard hats.

The examples in my collection are rather uninspiring:

I saw these in the road atlas section of a map library, same deal:

I think a firetruck  can be made to work....

I've seen photos of firefighters from other parts of the world using significantly different helmets, but the wide sloping back-brim is maybe common enough to be interpreted globally even if it is not the current model in use everywhere.
See also:

https://www.fireapparatusmagazine.com/ppe/trends-in-fire-helmet-design/#gref
https://www.firerescue1.com/fire-products/personal-protective-equipment-ppe/helmets/articles/code-3-podcast-the-great-helmet-debate-iconic-look-vs-european-design-XtzPiOLkpDCLHney/

That said, I like the little truck too!

I like the truck but I can't quite envision how you could make it discernible at 20 pixels or less. One thought I had was reusing the police badge icon, but with the fire emblem in the middle, something like this:

One thought I had was reusing the police badge icon, but with the fire emblem in the middle, something like this:

I’ve seen this emblem a bit as well, always in red alongside a blue police badge icon, mostly on signs but occasionally on maps. We happen to color police station icons in blue because our color palette assigns blue to any POI in the “Infrastructure” category. Fire stations would also count as infrastructure, but if we take this badge, recolor it in blue, and shrink it down to a POI icon size, I’m not sure it would be easy to distinguish it from a police station.

A few attempts, based on the comments above and on Slack:
Police shield with flame:

Firefighter cross with flame:

Fire truck, roughly traced from https://github.com/ZeLonewolf/openstreetmap-americana/issues/1036#issuecomment-1959303565:

I think the truck might be too finicky/detailed for the style, especially compared to the other "civic" icons. There is some room for the icon to be taller, so I could try that. I feel like making the truck as tall as it is wide will throw off its aspect ratio though. I skipped the hat idea because it seemed harder to draw lol, but I could give it a shot if someone strongly prefers it.
I think either of the first two badges work pretty well! The reused police shield has the pro of increasing style cohesiveness, but the con of making fire stations seem like a subset of police stations. I'd say I'd weakly prefer the cross icon, but would be happy with either.
Opinions and other ideas welcome!

Also, took a photo of a trail map on a hike recently to help me verify some path names, and realized later that I accidentally captured a fire station icon in the wild! It was a firefighter cross style. This was in a California State Park.

I like the "cross" one actually. It looks more American to me than the shield. Is there a way to make the external edges a little less wavy/curvy and more rounded like the California State Park map you have a picture of? I think making it a little less ornate might help it fit in better with the other icons, because there's a lot already going on with the flame in the middle.

Good idea, I think this looks better

Possible the proportions could still be tweaked, but I think this is a good track! Open for input though

Until you look really close, the cross looks like one of those diving bell helmets.  I think if you go with the Maltese cross shaped firefighter symbol, you have to drop the flame from it and go with a clean shaped ones.  If you want the flame, I think the badge shape works better.

I have to say I don't see the helmet, but we could go more in the direction of the FDNY logo, with a divided ring around the flame. A quick mockup (not even centered 😅):

Finally found myself some time to come back to this. I can see where the diving helmet visual impression is coming from, although I can't really say I see it myself. But I can appreciate that maybe the maltese cross with flame has too much going on for its own good. I tried out a version without the flame icon:

Removing the flame also allows one to shrink the circle relative to the "fins", which could be a promising direction:

Although I feel like the proportions of this particular one are somehow not quite right...but maybe that's just me.
I also tried to make the FDNY style one suggested above:

I think this looks a little like a firepit to me, but I'm open to it. Maybe the ring needs to be thicker?
Now with these and the above shield and flame designs, there are many (too many?) options, fair enough for a relativey hard-to-represent POI. Interested to see which direction people like the most, if any!

The police shield/badge emblazoned with a flame got by far the most fire emoji reacts on the Slack channel, so I'll make a PR with that design


Laralexa

Initial commit after forking and refactoring package names. Also updated installation instructions for composer as this code is not in packagist.

Hey there! I just read through the commits and from what I can tell you just changed the name of the app from AlexaApp to LarAlexa or something along those lines?

I think after forking he just had to change the name to not mess with your namespace. He also updated the dependency in composer.json (illuminate/routing) to 5.3 - but this is outdated now that Laravel 5.4 is available.


[iOS] Choose between Debug or Release Signing capabilities in branch configuration

It doesn't really help you when you're facing trouble with the signing capabilities and adhoc/appstore mobile provisioning file.
Let me explain myself.
In XCode, i have two configurations under "Signing and Capabilities".

First one is debug, using a provisioning profile created using Ad hoc type
Second one is release, using a provisioning profile created using App store type

In my AppCenter configuration, in branch configuration.
For my develop branch, i set my ad hoc provisioning profile.
For my master branch, i set my release provisioning profile.
However, it doesn't seems like i can choose which Signing capabilities configuration it is going to be built with
So i'm facing the issue that i'm building an app on my develop branch, using ad hoc provisioning profile, and still it cannot be installed on my testers devices, because it seems like it is always using the "Release type" configuration defined in XCode

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

ID: 1b3efbfa-b70b-9039-4b49-6ba4ce6c36af
Version Independent ID: 73e079aa-bbc3-2a06-a5d1-c4827bd5e3dc
Content: iOS Build Troubleshooting - Visual Studio App Center
Content Source: docs/build/troubleshooting/ios.md
Service: vs-appcenter
Sub-service: app-center-build
GitHub Login: @lucen-ms
Microsoft Alias: lucen


Refactor sidebar

Overview

Created fhir-chart-layout component with sidenav and toolbar
Updated showcase and cardio to use fhir-chart-layout
Use Material Theme color for the sidenav close button
data-layer-toolbar and fhir-chart-layout accept a list of toolbar buttons to show
Cleaned up services that were unnecessarily using providedIn: NgModule so they are now providedIn: 'root'
Removed unnecessary module imports from showcase/app.module and cardio/app.module
Reorganized some files

How it was tested

Ran showcase and cardio apps
Checked for correct toolbar/sidenav state in each app
Added some layers to the chart
Opened the options panel and clicked on a few things
Opened/closed the panel
Tested changing theme colors to make sure toolbar button matches the theme

Checklist

[x] The title contains a short meaningful summary
[x] I have added a link to this PR in the Jira issue
[x] I have described how this was tested
[ ] I have included screen shots for changes that affect the user interface
[ ] I have updated unit tests
[ ] I have run unit tests locally
[ ] I have updated documentation (including README)


chore: increase bottom tabs top padding

This PR resolves:
https://www.notion.so/artsy/Likely-related-but-buttom-navigation-bars-seem-to-have-less-padding-at-the-top-144cab0764a080aa81dcdb81295786fa?pvs=4
Description
This PR increase the top padding on the bottom tabs.

Before
After

PR Checklist

[X] I have tested my changes on iOS and Android.
[x] I hid my changes behind a [feature flag], or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
[X] I added an [app state migration], or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[X] I have added a changelog entry below, or my changes do not require one.

#nochangelog

Warnings

:warning:

✅ No changelog changes

  Generated by :no_entry_sign: dangerJS against f2354a9c3893ad9525d1b609fc96db113f07f58f


Some installed packages could not be loaded because they contain native modules that were compiled for an earlier version of Atom.

Cannot find module '/Users/user-name/.atom/packages/platformio-ide-terminal/node_modules/pty.js/bin'

Same here!

I solved this issue by following the instructions in #297

https://github.com/platformio/platformio-atom-ide-terminal/issues/297


Prisma Integration Errors in React Native with Expo: Warnings and Import Failures

Description
When following documentation for in README.md according to the Expo Section I get various warinings/errors in different scenarios.

Creating a PrismaClient instance anywhere in the application gives this warning

Importing import '@prisma/react-native'; anywhere in the application throws this error

Expected Behavior
When following the guidelines outlined in the README.md under the Expo Section, users should be able to integrate Prisma seamlessly into their React Native projects using Expo without encountering warnings or errors mentioned.
Additional Information
The issues described above were observed not only when using the Expo Go app for live testing and development but also during local builds of the application. This was done to ensure that the problems were consistent across different testing environments provided by Expo. Despite trying various configurations and setups in both Expo Go and local builds, the same warnings and errors persisted.

Issue seems to be related to NativeModules returning an empty object. Trying to reference to NativeModules.Prisma which will give null.
Output: NativeModules {}
https://github.com/prisma/react-native-prisma/blob/9fce36198f53f4b4f8cfa4236fe90560c2c33ac2/src/index.ts#L19-L25

Thank you for reporting this Nabil.
To help me narrow this down, can you confirm that you are doing the following:

Adding the Expo plugin "plugins": ["@prisma/react-native"] and running prebuild npx expo prebuild --clean
setting previewFeatures = ["reactNative"] in the schema as per the readme
generate initial migrations and a database if it doesn't exist: npx prisma@latest migrate dev
generating the client: npx prisma@latest generate
running prebuild to activate the Expo plugin

Prisma relies on a native module, so Expo Go isn't supported at the moment.

Thank you for reporting this Nabil.
To help me narrow this down, can you confirm that you are doing the following:

Adding the Expo plugin "plugins": ["@prisma/react-native"] and running prebuild npx expo prebuild --clean
setting previewFeatures = ["reactNative"] in the schema as per the readme
generate initial migrations and a database if it doesn't exist: npx prisma@latest migrate dev
generating the client: npx prisma@latest generate
running prebuild to activate the Expo plugin

Prisma relies on a native module, so Expo Go isn't supported at the moment.

I'm facing same issue. I've tried all steps above, but prisma failed to initialize

Thanks @Skr1pt1k. Now, I'm wondering what's special about your setup. Would you be able to invite me to a repo or create a minimal reproduction I can debug?

I was able to recreate this issue and even solve it I don't know why but when you define the sceham.prisma in some ./**/ directory the prisma is not able to initialize or sometimes access the database same goes for many other issues created on this repo. I was even able to solve it by creating the schema.prisma in the ROOT_DIR of the project which then allows PrismaClient to work perfectly as expected.

Also having this issue. Interesting is that I don't have the issue with the example project https://github.com/sorenbs/budget-buddy-expo. I tried installing the same version of all prisma dependencies in the package.json from that project and mirroring configuration as closely as possible, but I still can't get rid of the error in my own project...

What version of prisma, @prisma/client and @prisma/react-native are you using

The issue also persists for me, even when I run the base project from @sorenbs : https://github.com/sorenbs/budget-buddy-expo with all the prerequisites steps mentioned above. Any potential fixes?

Estou com mesmo problema....
"@prisma/client": "^5.22.0",
"@prisma/react-native": "^5.22.0",
react-native-quick-base64

Task :prisma_react-native:configureCMakeDebug[arm64-v8a] FAILED
C/C++: CMake Error at CMakeLists.txt:10 (add_library):
C/C++:   Target "react-native-prisma" links to target
C/C++:   "ReactAndroid::turbomodulejsijni" but the target was not found.  Perhaps a
C/C++:   find_package() call is missing for an IMPORTED target, or an ALIAS target
C/C++:   is missing?
C/C++: CMake Error at CMakeLists.txt:10 (add_library):
C/C++:   Target "react-native-prisma" links to target
C/C++:   "ReactAndroid::react_nativemodule_core" but the target was not found.
C/C++:   Perhaps a find_package() call is missing for an IMPORTED target, or an
C/C++:   ALIAS target is missing?
C/C++: CMake Generate step failed.  Build files cannot be regenerated correctly.


request: 1.20.1 update

this mod is very useful, I hope one day to have a version for 1.20.1

Fabric 1.20.1 would be awesome for our modpack <3

up


Run command in container

This adds the "run_exec" and "inspect_exec" API endpoints, as well as the corresponding frontend-UI.
Use case is to run a one-off command in a specific container. For example, for some of our docker-compose projects, we want to re-run "provision" (which is our puppet provisioner) without deleting/restarting the container.

Hi @MichaelMackus and thanks for your contribution.
It seems to me that the output of the command is not displayed, right?

@francescou that's correct. I elected to leave off that functionality. Some commands might have a large amount of output, and won't fit into an alert window. Then we'd have to consider creating another Modal dialog to view the contents of the Exec. There's no technical limitations for this, though - the docker inspect API endpoint does have the option(s) to include results. We'd just have to figure out how to fit it into the existing UI - should we automatically open the modal after success (we might even be able to include a link to view the output in the alert success window), or do we want another area in the UI to view the Execs.

Hi @MichaelMackus sorry for my late reply.
I see your concern. Actually, things would be even more difficult if we want to provide support for streaming output commands (e.g. top). We would need a terminal (as discussed in #4) to do so.

@francescou right, that's why I've left off that functionality. This is PR is just to solve the issue of running a one-off background process in the container (i.e. git pull, install some software via package manager, or temporarily suspend/run a service for testing).

Hello @MichaelMackus, and sorry (again) for my late reply.
I've investigated about how to integrate your work with portainer in order to provide an interactive console.
The frontend should be straightforward to implement but you should modify your code to run /bin/sh and enable tty.
If you're interested we can work on this feature.

Ooo, nice. I will look into portainer as well and let you know what I find.


TypeError: undefined is not a function (near '...', click).transition().duration(750).att...')

I used PieChart in a component. It works when it first rendered. But I got this error after any state update:
TypeError: undefined is not a function (near '...', click).transition().duration(750).att...')
logCapturedError — react-dom.development.js:16477

This is how I used the PieChart:
<PieChart
    size={CHART_SIZE}
     data={[
           { key: 'A', value: 100, color: CHART_RED },
           { key: 'B', value: 200, color: CHART_ORANGE },
          { key: 'C', value: 50, color: CHART_YELLOW },
          { key: 'D', value: 50, color: CHART_GREEN },
           { key: 'E', value: 50, color: CHART_BLUE },
      ]}/>

It works when I forked from the repo and comment out the some lines of codes (transition) like this:
    if (n) { // we don't need to do this, but it's fun
      /*
       * Change current slices
       * Transition current slice dimensions
       */
      path
        .attr('fill', getSliceFill)
        .on('mouseover', mouseover)
        .on('mouseout', mouseout)
        .on('mousemove', mousemove)
        .on('click', click)
        // .transition()
        // .duration(750)
        // .attrTween('d', this.tweenSlice);

      /*
       * Add new slices
       */
      path
        .enter()
        .append('path')
        .attr('class', 'pie-chart-slice')
        .attr('fill', getSliceFill)
        .on('mouseover', mouseover)
        .on('mouseout', mouseout)
        .on('mousemove', mousemove)
        .on('click', click)
        .each((d, i) => currentSlices.splice(i, 1, d))
        // .transition()
        // .duration(750)
        // .attrTween('d', this.tweenSlice);
    }

Versions:
react-easy-chart: 1.0.0
react: ^16.6.0
react-dom: ^16.6.0

Same here

You can solve this issue by going in:
node_modules > react-ease-chart > lid > pie-chart > hybrid > index.js
in index.js you just have to remove
.transition().duration(750).attrTween('d', this.tweenSlice);

that line from:
path.enter().append('path').attr('class', 'pie-chart-slice').attr('fill', getSliceFill).on('mouseover', mouseover).on('mouseout', mouseout).on('mousemove', mousemove).on('click', click).each(function (d, i) {return currentSlices.splice(i, 1, d); }).transition().duration(750).attrTween('d', this.tweenSlice);

this block of code!
I hope this will solve your problem!

Is this safe (editing node_modules by hand). I'm trying it now.

yeah! there is no bad in it!

Okay. When I do, the error starts coming from several other lines. I have to remove those as well yh?
On editing node_modules - When next I do an npm install, the lines will come back yh...

yes! you have to remove .transition() method from all lines! and you have to move the react-easy-chart folder from node_modules to another place! and require it from that path! and don't remove it from package.json! hope it will help.

Thanks a lot. It works.
My 2 cents: You have to restart the app to reflect node_modules changes. I had to do that.

Ok, this is a massive blocker to using react-easy-chart.  Editing node_modules is not a valid solution.  Is clearly a bug with the module, and needs fixing at source :(


Added a message to show why a command does not work at the time

Messages have been added to both '!play' and '!storypoints' to let the user know why they can not continue.
!play returns a message saying "There is already a question in progress."
!storypoints returns a message saying "You are currently not answering a question"
solves #10
(sorry for the small mess up I made when trying to create the pull request, this is my first time using github like this)

This  should  be fine for now! Thanks for your contribution!


[10.x] feat add whereLike() and whereLikeContain()

add methods that handle queries for performing 'where like' searches in the database.

whereLike(), whereNotLike() , orWhereLike()
whereLikeContain() , whereNotLikeContain() , orWhereLikeContain()

 // select * from `users` where `name` like laravel;

 User::whereLike('name', 'laravel')->get();

// select * from `users` where `name` like "%laravel%";

 User::whereLikeContain('name', 'laravel')->get();

 // select * from `users` where `name` like laravel or `name` like forge;
 User::whereLike('name', 'laravel')->orWhereLike('name','forge')->get();

 // select * from `users` where `name` like "%laravel%" or `name` like "%forge%";
 User::whereLikeContain('name', 'laravel')->orWhereLikeContain('name','forge')->get();

 // select * from `users` where `name` not like laravel and `name` not like "%forge%";
 User::whereNotLike('name', 'laravel')->whereNotLikeContain('name','forge')->get();

This has been attempted many times.
We should stop adding more alias methods to Builder.
Btw it does not cover all use cases.
How to produce this query
select * from stores where name like "apple%"

select * from stores where name like "a%e"

There are many others cases

This has been attempted many times. We should stop adding more alias methods to Builder.
Btw it does not cover all use cases.
How to produce this query
select * from stores where name like "apple%"

select * from stores where name like "a%e"

There are many others cases

You Can Use like this or other cover all use cases
Stores::whereLike('name',"apple%")->get();
Stores::whereLike('name',"a%e")->get();

Thank you. Please try to search PR's before submitting. @driesvints

🧐 Hmm, I think it's useful, just like other query builders such as whereBetween() ...etc. and whereLike() it supports many other cases in the where clause.

I'm surprised this is closed without any practical reason.
LIKE is a very common SQL operator and probably the only one that doesn't have a helper method yet.
Sometimes I find myself reaching for it by default, only to realise such a method doesn't exist.
We have helper methods for several operators like IN, NULL, BETWEEN, DATE, FULLTEXT, etc.
Why is LIKE excluded? Are there any downsides?


rxvt_unicode: allow to specify dependencies for plugins

Motivation for this change
I needed to add some perl modules for a urxvt script.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change
[x] Tested execu (usually in ./result/bin/)tion of all binary files
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

LGTM. Thank you

Thank you for the review.


Introduce TSDB changes for appending metadata to the WAL

This is a rehash of the recent PR #10312 for appending metadata to the WAL, but focusing on the TSDB-related changes only.
It includes a new storage format in the WAL, the changes to the Appender interface in the Storage package, stubbing all the implementations, as well testing that the encoding/decoding functionality works as intended.

I merged this PR as an enabler for the scraping and remote-write part. This in itself adds very minimal overhead to the TSDB (additional field in the series struct) until the scraping is connected to it and TSDB starts storing metadata. This can be reverted easily if required.


Fix Axios Image Request Issue

The issue had to deal with Axios trying to process the ArrayBuffer as a JSON string, which causes the 500 error to be thrown (like in issue https://github.com/potmat/homebridge-google-nest-sdm/issues/97). This was fixed by requesting the image as a base64 string and then processing it on the client.

Added changes directly to master due to code unrelated changes to nearby lines.

Should be included in v1.1.20


Awareness is copied on independent instances inside one document

Hi,
I am using the awareness option with a Y.js document that has multiple sub documents for multiple Slate instances.
Awareness is registered on all instances. As you can see, the cursor from one sub doc of the main doc object is also applied on other instances, which is wrong!

the document structure is like:
{
       slate1: [],
       slate2: [],
       ...
}

Hi @creativefctr,
the cursors are synced using awareness (which is bound to the document and not the shared type) so this is to be expected for now.
Since a single user can (under normal circumstances) have only a single selection at a time you could as a workaround store some sort of identifier (like the shared type key) on editor focus in the awareness local state and use that to figure out which editor the user has currently selected.

@BitPhinix Technically speaking, the shared type is a unique node in the document, so per-document awareness should also correctly detect the absolute path of that specific shared type object relative to the whole document.
Anyway, I was thinking about using JavaScript's Proxy Object as a workaround to decorate the awareness object so that the changes are only routed to the currently focused editor (which can be detected by your solution).

Next allows the customization of the cursor state storage key to solve this issue.

Next allows the customization of the cursor state storage key to solve this issue.

Is this available yet?  I'm hitting the same issue right now with the page crashing with the following error:
Uncaught Error: yText isn't a descendant of root element
    getSlatePath location.ts:118
    absolutePositionToSlatePoint position.ts:43
    relativePositionToSlatePoint position.ts:78
    relativeRangeToSlateRange position.ts:272
    getRange useRemoteCursorOverlayPositions.tsx:64
    node_modules bundle.js:202241
    node_modules bundle.js:202236
    React 3
    useRemoteCursorOverlayPositions

If the ability to customize the cursor state storage key is not yet available, can you suggest a workaround?

It is available, you can adjust it using the cursorStateField (and cursorDataField) option in withCursors

Just edited my comment, I found that myself looking at the exported d.ts, but didn't see it in any documentation.  Glad I found this issue :)


[C++] compilation standard to C++20

Describe the enhancement requested
are there any issues with setting the default to c++20 in the codebase? Currently the cmake_modules/SetupCxxFlags.cmake sets CMAKE_CXX_STANDARD to 17.
Component(s)
C++

Yes that's not a quick decision to make. Here is the thread about bumping to 17 2 years ago: https://lists.apache.org/thread/9g14n3odhj6kzsgjxr6k6d3q73hg2njr

I checked and we currently can't switch to 20 because CRAN (R package hub) has several builds with AppleClang <=14. This is a blocker but not necessarily the only one.
You are certainly not alone in preferring to use C++20 but as arrow C++ is a foundational library we have to be more conservative with such thinks.
I will close this issue for now, we can re-visted in time

It seems that "Apple Clang 13<IP_ADDRESS>" is the oldest version based on the last R arrow package check information:

https://cran.r-project.org/web/checks/check_results_arrow.html
https://cran.r-project.org/web/checks/check_flavors.html#r-oldrel-macos-x86_64

It's based on LLVM 12.0.0. See also: https://en.wikipedia.org/wiki/Xcode#Xcode_11.0_-14.x(since_SwiftUI_framework)_2
LLVM 12.0.0 has -std=c++20. See also: https://clang.llvm.org/cxx_status.html#cxx20
So we may be able to use C++20 on CRAM. (We may not be able to use some C++20 features.)

We can use C++20 with GCC 8 or later: https://gcc.gnu.org/projects/cxx-status.html#cxx20

I think before such a move we should properly document our support policy. That will create clarity both for users and contributors.

I think before such a move we should properly document our support policy.

It mentions supported GCC/Clang/MSVC versions explicitly, right?

AFAIK this is the only place we mention it:

A C++17-enabled compiler. On Linux, gcc 7.1 and higher should be sufficient. For Windows, at least Visual Studio VS2017 is required.

https://arrow.apache.org/docs/developers/cpp/building.html


fixed ALTER USER command

removed the word 'with'.

Syntax is correct with WITH here.
Ref: https://www.postgresql.org/docs/10/static/sql-alteruser.html


Refactor/simplify audit log messages

Description
This PR simplifies the messages written in both the asset and account audit logs. Because The logs are already linked to the asset or account, so including the asset name and ID is unnecessary. The following changes have been made:

Removed redundant asset name and ID from the asset audit log messages.

Instead of: Asset '<ASSETNAME>': <ID>; fields: Updated Field: name, From: X, To: Y
Now: Updated Field: name, From: X, To: Y

Shortened the account audit log messages.

Instead of: Account NAME has been updated
Now: Account updated

Look & Feel

Asset AuditLog:

Before:

After

Account AuditLog:

Before:

After :

How to test

Make some updates to an asset (name, attributes) or to the account (name, primary or secondary colors)
Navigate to the audit logs page for assets or account audit log page .
Confirm that the logs entries are in the intended format.

[x] I agree to contribute to the project under Apache 2 License.
[x] To the best of my knowledge, the proposed patch is not based on code under GPL or other license that is incompatible with FlexMeasures

Can this be merged?

Yes, good catch!

Coveralls bitches sometimes without cause


add disk performance to CC cluster creation doc

Per @bobvawter, we list transactions per second on https://www.cockroachlabs.com/docs/cockroachcloud/create-your-cluster.html but need more specific disk performance numbers.
Thread: https://cockroachlabs.slack.com/archives/CBE9QQC4S/p1612809212227300

Moved to Jira: https://cockroachlabs.atlassian.net/browse/CC-4381


[WIP] Guard concurrent reconciliation

Signed-off-by: Pierangelo Di Pilato<EMAIL_ADDRESS>Fixes #

Proposed Changes

Release Note

Docs

Does it really makes sense this? Isn't the Message handler running in the same event loop?

Does it really makes sense this? Isn't the Message handler running in the same event loop?

This diff is part of https://github.com/knative-sandbox/eventing-kafka-broker/pull/568, I was just testing it in isolation, and yes, it does.

This diff is part of https://github.com/knative-sandbox/eventing-kafka-broker/pull/568, I was just testing it in isolation, and yes, it does.


docs: make gssoc banner adaptive to github dark/light mode 💫✨

Close #693
Description

Made GSSOC Banner adaptive to Github's Dark/Light Mode with using picture element with media queries.
This PR will improve the overall readability of Food Recipes Website Repository's Documentation.

Screenshot

LIGHT MODE
DARK MODE

@Anupkjha2601 please make sure to review this PR.


Android Tv problem

I'm submitting a ...

[ ] bug report
[ ] feature request
[x] support request

General infomration
Prerequisites

[ ] Are you running the latest version?

Description
[Description of the bug or feature]
Steps to Reproduce

[First Step]
[Second Step]
[and so on...]

Expected behavior: [What you expected to happen]
Actual behavior: [What actually happened]
Context (Environment)
Installation

[x] I installed the plugin via zip from the Releases page
[ ] I´m using the Netflix Repo
[ ] I´m using a different source (Please tell which)

Operating System

[ ] Linux (x86/x64)
[ ] OSX (x86/x64)
[ ] Windows (x86/x64)
[ ] Linux (ARM)
[x] Android

Additional informatin on the environment
[Descripe your environment a bit more detailed, are you using LibreElec f.e.]
Debug log
[Please include a link to your debug log (use something like http://sprunge.us/) or similar, please do not paste]
Other information
[e.g. detailed explanation, related issues, suggestions how to fix, links for us to have context, etc.]
Screenshots
[Please add a screenshot if that helps understanding your problem]
[You can erase any parts of this template not applicable to your Issue.]

http://pasted.co/dcc1cc4a log
https://ibb.co/NSLv2kQ

@ardatanik
Uninstall the Netflix plugin using the steps from here.
https://forum.kodi.tv/showthread.php?tid=329767&pid=2807374#pid2807374
and install this one
https://codeload.github.com/CastagnaIT/plugin.video.netflix/zip/master
If the problem still exist, report it here with a new debug log.
https://github.com/CastagnaIT/plugin.video.netflix/issues

Looks that you update your addon, instead of uninstalling and deleting userdata files...do that and it will work as usual.

Are you using Home Screen shortcuts or widgets?
If so, yo should delay its startup, because, service is not available while loading it...


Sudo commands failing

I am having a problem when ever I try to execute a command that requires sudo access. The commands work fine without sudo, but as soon as the command is prefixed with sudo, it will not work. I have run the exact same commands on the actual remote server and they work fine, but over sshj they don't.

My bad, needed this: session.allocateDefaultPTY();


Using Messenger for Desktop after account deactivation

I deactivated my Facebook account. I still can use Messenger on my phone, but unfortunately it doesn't work on Desktop version.
When I try to log in, it doesn't give me any error, just refreshes login page.

The programs essentially is a web browser so you are logging in to a web browser check http://messenger.com(the website the program runs off of) to see if you can actually use the default facebook messenger in the browser and ensure its not a problem with the program itself

nodzy i  have the same issue. I don't want to activate facebook again so why is this happening? Did you make it work?

No, unfortunately not - it doesn't work for me.
2016-05-03 17:36 GMT+02:00 zaratustra21<EMAIL_ADDRESS>
nodzy i have the same issue. I don't want to activate facebook again so
why is this happening? Did you make it work?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/Aluxian/Facebook-Messenger-Desktop/issues/382#issuecomment-216568840

I've attempted this also. Even if you create a "Messenger only" account with your phone number, you cannot login to the messenger.com/ service with it.
It requires you've a Facebook account, Messenger only accounts are not available outside of Mobile.

I think the issue as been answered


Diagnose why CUDA runtime not selected

I just upgraded to 1.7.1 to try the new multi-runtime support:
    <PackageReference Include="Whisper.net" Version="1.7.1" />
    <PackageReference Include="Whisper.net.Runtime" Version="1.7.1" />
    <PackageReference Include="Whisper.net.Runtime.CoreML" Version="1.7.1" />
    <PackageReference Include="Whisper.net.Runtime.Cuda.Linux" Version="1.7.1" />
    <PackageReference Include="Whisper.net.Runtime.Cuda.Windows" Version="1.7.1" />

I have NVIDIA cuda installed and working in other applications, but it looks like Whisper.net is using the CPU runtime:

Is there any easy way to diagnose why it's not using CUDA?

Hello @lilhoser ,
Just merged https://github.com/sandrohanea/whisper.net/pull/236 that will add some debug logs for library loading to be able to trace which library is loaded and why.
In order to enable the logs, you can call LogProvider.AddConsoleLogging(minLevel: WhisperLogLevel.Debug); before creating any WhisperFactory in order to write the logs to Console.
You can also use LogProvider.Instance.OnLog += (...) to define custom logic for your logs.
The newly added logs should show any of the following:

Cuda runtime directory cannot be found.
Cuda library cannot be loaded
No cuda device is found.
Which runtime is loaded.

It will be released soon (probably later today) under 1.7.2-preview1 version.
Please, give it a try and let me know if you can identify the problem using these logs.

Thanks, the debug information really helped! It appears CUDA is loading fine:
'pizzaui.exe' (CoreCLR: clrhost): Loaded 'C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\Whisper.net.dll'.
Whisper Information: 1 : 10/29/2024 5:08 PM: Searching for runtime directory Cuda in C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\runtimes\cuda\win-x64
Whisper Information: 1 : 10/29/2024 5:08 PM: Searching for runtime directory Cuda in C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\runtimes\cuda\win-x64
Whisper Information: 1 : 10/29/2024 5:08 PM: Searching for runtime directory Cuda in C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\runtimes\cuda\win-x64
Whisper Information: 1 : 10/29/2024 5:08 PM: Searching for runtime directory Vulkan in C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\runtimes\vulkan\win-x64
Whisper Information: 1 : 10/29/2024 5:08 PM: Runtime directory for Vulkan not found in C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\runtimes\vulkan\win-x64
Whisper Information: 1 : 10/29/2024 5:08 PM: Searching for runtime directory Vulkan in C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\runtimes\vulkan\win-x64
Whisper Information: 1 : 10/29/2024 5:08 PM: Runtime directory for Vulkan not found in C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\runtimes\vulkan\win-x64
Whisper Information: 1 : 10/29/2024 5:08 PM: Searching for runtime directory Vulkan in C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\runtimes\vulkan\win-x64
Whisper Information: 1 : 10/29/2024 5:08 PM: Runtime directory for Vulkan not found in C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\runtimes\vulkan\win-x64
Whisper Information: 1 : 10/29/2024 5:08 PM: Searching for runtime directory CoreML in C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\runtimes\coreml\win-x64
Whisper Information: 1 : 10/29/2024 5:08 PM: Runtime directory for CoreML not found in C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\runtimes\coreml\win-x64
Whisper Information: 1 : 10/29/2024 5:08 PM: Searching for runtime directory CoreML in C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\runtimes\coreml\win-x64
Whisper Information: 1 : 10/29/2024 5:08 PM: Runtime directory for CoreML not found in C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\runtimes\coreml\win-x64
Whisper Information: 1 : 10/29/2024 5:08 PM: Searching for runtime directory CoreML in C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\runtimes\coreml\win-x64
Whisper Information: 1 : 10/29/2024 5:08 PM: Runtime directory for CoreML not found in C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\runtimes\coreml\win-x64
Whisper Information: 1 : 10/29/2024 5:08 PM: Searching for runtime directory OpenVino in C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\runtimes\openvino\win-x64
Whisper Information: 1 : 10/29/2024 5:08 PM: Runtime directory for OpenVino not found in C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\runtimes\openvino\win-x64
Whisper Information: 1 : 10/29/2024 5:08 PM: Searching for runtime directory OpenVino in C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\runtimes\openvino\win-x64
Whisper Information: 1 : 10/29/2024 5:08 PM: Runtime directory for OpenVino not found in C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\runtimes\openvino\win-x64
Whisper Information: 1 : 10/29/2024 5:08 PM: Searching for runtime directory OpenVino in C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\runtimes\openvino\win-x64
Whisper Information: 1 : 10/29/2024 5:08 PM: Runtime directory for OpenVino not found in C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\runtimes\openvino\win-x64
Whisper Information: 1 : 10/29/2024 5:08 PM: Searching for runtime directory Cpu in C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\runtimes\win-x64
Whisper Information: 1 : 10/29/2024 5:08 PM: Searching for runtime directory Cpu in C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\runtimes\win-x64
Whisper Information: 1 : 10/29/2024 5:08 PM: Searching for runtime directory Cpu in C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\runtimes\win-x64
Whisper Information: 1 : 10/29/2024 5:08 PM: Searching for runtime directory CpuNoAvx in C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\runtimes\noavx\win-x64
Whisper Information: 1 : 10/29/2024 5:08 PM: Runtime directory for CpuNoAvx not found in C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\runtimes\noavx\win-x64
Whisper Information: 1 : 10/29/2024 5:08 PM: Searching for runtime directory CpuNoAvx in C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\runtimes\noavx\win-x64
Whisper Information: 1 : 10/29/2024 5:08 PM: Runtime directory for CpuNoAvx not found in C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\runtimes\noavx\win-x64
Whisper Information: 1 : 10/29/2024 5:08 PM: Searching for runtime directory CpuNoAvx in C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\runtimes\noavx\win-x64
Whisper Information: 1 : 10/29/2024 5:08 PM: Runtime directory for CpuNoAvx not found in C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\runtimes\noavx\win-x64
'pizzaui.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\8.0.10\System.Runtime.Intrinsics.dll'. Symbols loaded.
Whisper Information: 1 : 10/29/2024 5:08 PM: Checking if runtime Cuda is supported on the platform: win
Whisper Information: 1 : 10/29/2024 5:08 PM: Checking for CUDA availability.
Whisper Information: 1 : 10/29/2024 5:08 PM: NUmber of CUDA devices found: 1
Whisper Information: 1 : 10/29/2024 5:08 PM: Trying to load ggml library from C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\runtimes\cuda\win-x64\ggml.dll
Whisper Information: 1 : 10/29/2024 5:08 PM: Trying to load whisper library from C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\runtimes\cuda\win-x64\whisper.dll
Whisper Information: 1 : 10/29/2024 5:08 PM: Successfully loaded whisper library from C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\runtimes\cuda\win-x64\whisper.dll
Whisper Information: 1 : 10/29/2024 5:08 PM: Using NativeLibraryWhisper for whisper library
Whisper Information: 1 : 10/29/2024 5:08 PM: whisper_init_from_file_with_params_no_state: loading model from 'C:\Users\lilhoser\AppData\Roaming\pizzawave\model\ggml-large-v3.bin'
Whisper Information: 1 : 10/29/2024 5:08 PM: whisper_init_with_params_no_state: use gpu    = 1
Whisper Information: 1 : 10/29/2024 5:08 PM: whisper_init_with_params_no_state: flash attn = 0
Whisper Information: 1 : 10/29/2024 5:08 PM: whisper_init_with_params_no_state: gpu_device = 0
Whisper Information: 1 : 10/29/2024 5:08 PM: whisper_init_with_params_no_state: dtw        = 0
Whisper Information: 1 : 10/29/2024 5:08 PM: whisper_model_load: loading model
Whisper Information: 1 : 10/29/2024 5:08 PM: whisper_model_load: n_vocab       = 51866
Whisper Information: 1 : 10/29/2024 5:08 PM: whisper_model_load: n_audio_ctx   = 1500
Whisper Information: 1 : 10/29/2024 5:08 PM: whisper_model_load: n_audio_state = 1280
Whisper Information: 1 : 10/29/2024 5:08 PM: whisper_model_load: n_audio_head  = 20
Whisper Information: 1 : 10/29/2024 5:08 PM: whisper_model_load: n_audio_layer = 32
Whisper Information: 1 : 10/29/2024 5:08 PM: whisper_model_load: n_text_ctx    = 448
Whisper Information: 1 : 10/29/2024 5:08 PM: whisper_model_load: n_text_state  = 1280
Whisper Information: 1 : 10/29/2024 5:08 PM: whisper_model_load: n_text_head   = 20
Whisper Information: 1 : 10/29/2024 5:08 PM: whisper_model_load: n_text_layer  = 32
Whisper Information: 1 : 10/29/2024 5:08 PM: whisper_model_load: n_mels        = 128
Whisper Information: 1 : 10/29/2024 5:08 PM: whisper_model_load: ftype         = 1
Whisper Information: 1 : 10/29/2024 5:08 PM: whisper_model_load: qntvr         = 0
Whisper Information: 1 : 10/29/2024 5:08 PM: whisper_model_load: type          = 5 (large v3)
Whisper Information: 1 : 10/29/2024 5:08 PM: whisper_model_load: adding 1609 extra tokens
Whisper Information: 1 : 10/29/2024 5:08 PM: whisper_model_load: n_langs       = 100
Whisper Information: 1 : 10/29/2024 5:08 PM: ggml_cuda_init: GGML_CUDA_FORCE_MMQ:    no
Whisper Information: 1 : 10/29/2024 5:08 PM: ggml_cuda_init: GGML_CUDA_FORCE_CUBLAS: no
Whisper Information: 1 : 10/29/2024 5:08 PM: ggml_cuda_init: found 1 CUDA devices:
Whisper Information: 1 : 10/29/2024 5:08 PM:   Device 0: NVIDIA GeForce RTX 4090, compute capability 8.9, VMM: yes
Whisper Information: 1 : 10/29/2024 5:08 PM: whisper_model_load:    CUDA0 total size =  3094.36 MB
Whisper Information: 1 : 10/29/2024 5:08 PM: whisper_model_load: model size    = 3094.36 MB

What's confusing is that this is the only DLL that shows up in VS's module debug window:
'C:\projects\pizzawave\pizzaui\bin\Release\net8.0-windows\Whisper.net.dll'

That's just the whisper.net managed code (without the whisper.cpp native code).
No runtime is shown there it seems as the symbols for it are not loaded.
If you want to debug the cp code, you can try: debug in mixed mode. That could potentially show the C++ code as well, but this is already built and packed in release mode, so it will be harder to debug.
I'm glad that it was cleared that Cuda was used with the RTX GPU, will close this for now. Feel free to re-open if there are additional questions.
Happy coding! :)


QuickFix menu filter & select by typing

It would be nice to be able to filter and select the options from the QuickFix popup menu by typing, similar to how the Command Palette works. As it is I can only move up and down with the arrow keys or select an option with the mouse. Same would apply to other popup menus like Suggest.

Duplicate of #157719


Implemented multiple reports page

Fixed Issues
21977, 21978, 21979, 21980, 21982, 21983, 21984, 21985, 21986, 21987, 21988, 21990, 21991,21992, 21993
Files Changed

IReportRepository

ReportRepository

ReportController

Report.cs

TestAttendee.cs

TestStatus.cs

testAttendee.ts

report.ts

test-report.component.ts

reports.routing.ts

enum-test-state.ts

startup.cs

test-report.html

question-programming.html

report.services.ts

report.module.ts

test-dashboard.html

Checks

[x] Naming Conventions
[x] Server side code comments (proper English, grammar and no spelling mistakes)
[x] Client side code comments (proper English, grammar and no spelling mistakes)
[x] Unused variables, methods, blank spaces and name spaces.
[x] Optimal Code and code formatting
[x] Commit History is proper, no merge is done.
[x] Commit/pull request messages should be proper to justify your feature
[x] All test cases are executed provided by tester.

Known Issues
Comments

This change is

SonarQube analysis reported 2 issues

 2 minor

Watch the comments in this conversation to review them.

SonarQube analysis reported 1 issue

 1 minor

Watch the comments in this conversation to review them.

SonarQube analysis reported 1 issue

 1 minor

Watch the comments in this conversation to review them.

SonarQube analysis reported 1 issue

 1 minor

Watch the comments in this conversation to review them.

SonarQube analysis reported 1 issue

 1 minor

Watch the comments in this conversation to review them.

SonarQube analysis reported 1 issue

 1 minor

Watch the comments in this conversation to review them.

SonarQube analysis reported 1 issue

 1 critical

Watch the comments in this conversation to review them.

SonarQube analysis reported 3 issues

 3 major

Watch the comments in this conversation to review them.


[zh-cn] Translate /docs/concepts/security/api-server-bypass-risks.md to Chinese

fixed: https://github.com/kubernetes/website/issues/37689
Translate Chinese version for api-server-bypass-risks.md
Preview

/label tide/merge-method-squash

/approve

The preview looks good to me.
/lgtm


Add support for periodic jobs

This adapter currently supports only on-demand jobs.
Scheduled jobs would open buffalo up to a new set of use cases.
I'm keeping this issue and PR to a minimum to invite commentary and critique.

Closing this down as I consider gocraft/work deprecated: https://github.com/gocraft/work/issues/201


Moving all Alma pre-commit hooks under the same hood

We should have all Alma pre-commit hooks in the same repository (ads it seems it should be done).
Doing this small refactoring before we can add more.
pre-commit-cloc that just contains counting comment should be made obsolete.
The hook is here now.

@mgu @Natim thanks for your review (as tou both contributed to the 2 Alam pre-commit repositories.


Building this with GCC 7 causes error.

Platform: OpenSUSE Tumbleweed.
GCC version: gcc version 7.1.1 20170802 [gcc-7-branch revision 250825] (SUSE Linux)
Log:
cc -c -pipe  -O -W -Wpointer-arith -Wno-unused-parameter -Werror -g   -I src/core -I src/event -I src/event/modules -I src/os/unix -I ../nginx-rtmp -I objs -I src/http -I src/http/modules \
	-o objs/addon/nginx-rtmp/ngx_rtmp_init.o \
	../nginx-rtmp/ngx_rtmp_init.c
../nginx-rtmp/ngx_rtmp_init.c: In function ‘ngx_rtmp_init_connection’:
../nginx-rtmp/ngx_rtmp_init.c:81:25: error: this statement may fall through [-Werror=implicit-fallthrough=]
             unix_socket = 1;
             ~~~~~~~~~~~~^~~
../nginx-rtmp/ngx_rtmp_init.c:83:9: note: here
         default: /* AF_INET */
         ^~~~~~~
../nginx-rtmp/ngx_rtmp_init.c:112:25: error: this statement may fall through [-Werror=implicit-fallthrough=]
             unix_socket = 1;
             ~~~~~~~~~~~~^~~
../nginx-rtmp/ngx_rtmp_init.c:114:9: note: here
         default: /* AF_INET */
         ^~~~~~~
cc1: all warnings being treated as errors

Workaround
Manually change objs/Makefile. Remove -Werror (unsafe).

@arut Is there any update on this?

Add -Wimplicit-fallthrough=0 to CFLAGS in obj/Makefile
It's a new default on GCC 7 when using -Werror.

Same problem, "fixed" mine by building it with gcc6 instead.

PR #1125 solves the issue but has yet to be merged.


Add link to the tutorial.

It will be good to add in readme a link back to the tutorial https://docs.microsoft.com/en-au/learn/modules/automatic-update-of-a-webapp-using-azure-functions-and-signalr/

Great suggestion! Thank you.


Question about differentiation

I have been reading your paper "Physics-Informed Neural Operator for Learning Partial Differential Equations". It seems that in equations (14) and (15) in your paper, in which you compute the derivative $u'(x)$ you do not go back recursively to the first Fourier layer i.e. $v_1$. In equation (14) you  stop at $v_{L-1}$ and in equation (15)  you stop at $v_L$.  I just wanted to make sure that I'm not missing anything in my understanding.

My understanding is that these equations are just describing values at one layer in terms of values at the previous layer.

Yes, you are correct David. It took me a while to understand that point. I think the goal of those equations is to get the spatial derivatives without giving co-ordinates explicitly as the input to the neural network, as is done with PINNs. And by using the FFT one can get the spatial derivative on the entire grid efficiently.

Closing, it seems like this is resolved


chore: improve CITATION.cff file

Hello!
I've submitted the same kind of PR (https://github.com/typst/typst/pull/4109) against the Nix project and a contributor improved the citation file and gave the proper justifications for it (thanks @lorenzleutgeb !), here it is: https://github.com/NixOS/nix/pull/10736
Therefore, this PR improves the CITATION.cff file in the same way.

I also stumbled across the identifiers in the initial PR. I like this better, thanks!


EML xml:lang code

Hello,
xml:lang="eng"
should be replaced with
xml:lang="en"
following standards.
Otherwise it fails here: https://knb.ecoinformatics.org/external//emlparser/
It doesn't fail here: https://tools.gbif.org/dwca-validator/eml.do
Best,
Menashè

There is a Q&A here: https://www.w3.org/International/questions/qa-lang-2or3.en.html noting that although "in the past" three-letter codes would have been acceptable, we should now use the shortest code where a language has more than one code (en, eng).


swt(): inference of level=None to depend on axis

Did not check in other functions, but here when level=None, level was infered based on len(data) which is data.shape[0], leading to confusion when using axis~=0

Thanks!  Do you mind adding a test case somewhere in pywt/tests/test_swt.py that would fail prior to this PR?
It looks like swt2 and swtn require an explicit level (no level=None default) so there is no similar issue there.  The wavedec* routines seem okay too, so it seems the problem is isolated to the case resolved in this PR.

Sorry not sure how to do this cleanly: I wrote a quick test but cannot push it from my git desktop (permission pb), and not sure how to edit another file in this PR from the git website.
Any help?
for info:
def test_swt_default_level_by_axis():
# Highlights a bug in swt() when using level=None and axis~=0
# when level=None, expected value is swt_max_level(n) where n is the length of the axis
w = 'db2'
x = np.ones((23,24,2**5))
axisTest = (0,1,2)
for axis in axisTest:
sdec = pywt.swt(x,w,level=None,start_level=0,axis=axis)
assert_equal(len(sdec),pywt.swt_max_level(x.shape[axis]))

Codecov Report

Merging #355 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #355   +/-   ##
=======================================
  Coverage   83.59%   83.59%
=======================================
  Files          21       21
  Lines        3328     3328
  Branches      564      564
=======================================
  Hits         2782     2782
  Misses        482      482
  Partials       64       64

Impacted Files
Coverage Δ

pywt/_swt.py
86.77% <100%> (ø)
: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 0296b30...68d92eb. Read the comment docs.

Any help?

Did you originally make this PR via the website?  I have not done things that way previously, so I am not sure of the procedure.  For future references, the basic sequence of terminal commands I used to make the latest commit was:
git clone https://github.com/0-tree/pywt
cd pywt
git checkout patch-1
**use an editor to make the desired changes to pywt/test_swt.py**
git add pywt/tests/test_swt.py
git commit -m "TST: add test cases for swt default level"
git push origin patch-1

In this case, it appears you had granted me permissions on this branch of your repo, so I was able to push the commit.  In most cases you can only push to your own branches, but in this case I had permission as a project maintainer to push to your PR branch (you can configure GitHub to either allow or disallow this as described here).

Thanks @0-tree.  Congrats on making your first contribution!

Thanks Greg for our help ;)


Study the BFILE data type usage and implementation in oracle database

Description:
Study the BFILE data type internal implementation and feasibility study on supporting the BFILE data type in oracledb module.
Describe your task(s)
Related Issues (optional):
Parent issue: ballerina-platform/ballerina-standard-library#1671

Some useful links:
https://docs.oracle.com/en/database/oracle/oracle-database/12.2/jjdbc/LOBs-and-BFiles.html#GUID-401E10DB-16B5-41C9-965E-E5F286F01E4C
https://docs.oracle.com/en/database/oracle/oracle-database/12.2/jjdbc/Java-streams-in-JDBC.html#GUID-B7ACBCEB-367D-4B39-A9E2-B0EAE6D475BC
https://docs.oracle.com/en/database/oracle/oracle-database/12.2/lnoci/lobs-and-bfile-operations.html#GUID-0A094518-F97C-40BE-A336-259AA82BD0A2
https://docs.oracle.com/en/database/oracle/oracle-database/12.2/adlob/LOB-APIs-for-BFILE-operations.html#GUID-043A9B91-69C8-44D4-A38A-E872B0A2B9A9

findings from the study: https://docs.google.com/document/d/15jIIuq2yPUDtRJD4XO1qg7fWtTaIxeYzMqayUTM0kik/edit?usp=sharing

This task is completed therefore closing the issue ticket.


fix link to plugin guide

The existing link to the plugin tutorial (https://napari.org/plugins/stable/for_plugin_developers.html#plugins-for-plugin-developers) is a 404. (I'm guessing it's a tutorial on the old plugin engine, and was renamed/removed.)
This changes the link to https://napari.org/plugins/.
I also made some small language changes, which I'm not attached to (happy to tweak however folks want, or abandon this PR and let someone else fix the link), but here's an explanation:

changed "tutorial" to "documentation" since npe2 doesn't seem to have a "tutorial" exactly
removed "hook" since that word doesn't seem to be used in npe2.

Here's a screenshot after my changes:

awesome, thanks for catching this @dchudz !!

Is anything in the way of merging this?

@dchudz: thanks for following up. no, I think we're good!


auto-delete the OTP code after successful verification

PR Auto Describe:
Changes in this pull request:

Type: Enhancement
Description: Added a feature to automatically delete the One-Time Password (OTP) code from the system after successful verification. This will help maintain the cleanliness of the data by removing unneeded OTP codes and possibly improve system performance.


String::simplify_path() is not exposed to scripting

Godot version:

6305030ee5ff7576772fb2d7bbb91db7eef455c0
Issue description:

There is no documentation for the String::simplify_path() function.
https://github.com/godotengine/godot/blob/556ee712772b992c8d734dfeb478e0ef8363aa8b/core/ustring.h#L322
https://github.com/godotengine/godot/blob/252c841d7ff5d770e8d2819e4f7955363410744b/core/ustring.cpp#L3125

Is this intended or should I (or someone else) do a PR?

Is this intended or should I (or someone else) do a PR?

.xml doc files are generated automatically form the GDScript API, if simplify_path is not in the documentation it is not exposed to GDScript at all and should be registered in core/variant_call.cpp first.

.xml doc files are generated automatically form the GDScript API, if simplify_path is not in the documentation it is not exposed to GDScript at all and should be registered in core/variant_call.cpp first.

Where is the GDScript API defined?

In core/variant_call.cpp, as mentioned :)

Ok closing


Decrease the height of Header image on the front page of stayus dashboard

Hi team,
I was trying to decrease teh height of the image on the staytus dashboard by decreasing the size of teh image , however it doesn't work.Can someone please help me with this.

As shown above teh height of the section highlighted in yellow


Create functions for battery parameters that were accessed in the code.

This prevents copying the entire params object multiple times each step. Improves battery runtimes, especially for PV smoothing.
Happy to add const pointer changes to this PR as well if we want to do that too.

Any stats on the reduced memory or execution time?

Looks like this shaved 56 seconds off of the PVSmoothing tests. Develop:

This branch:


python setup.py install fatal error: Python.h: No such file or directory

After I type these command
# python setup.py install

I receive these error message:
running install
running build
running build_py
creating build
creating build/lib.linux-x86_64-2.7
copying python/pcre.py -> build/lib.linux-x86_64-2.7
running build_ext
building '_pcre' extension
creating build/temp.linux-x86_64-2.7
creating build/temp.linux-x86_64-2.7/src
x86_64-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fPIC -I/usr/include/python2.7 -c src/pcremodule.c -o build/temp.linux-x86_64-2.7/src/pcremodule.o -fno-strict-aliasing
src/pcremodule.c:29:20: fatal error: Python.h: No such file or directory
 #include <Python.h>
                    ^
compilation terminated.

Building any Python C extension requires that you have the python-dev package installed (the package that includes Python headers).


Pls update packagist to latest version

Please could someone update packagist version to latest tag <IP_ADDRESS> so it could be installed via composer?
https://packagist.org/packages/yiisoft/yii2
Thank you.

see https://github.com/yiisoft/yii2/commit/abb503c284ad371159244c2e7c388827a0f12fe9#commitcomment-27773170
Pls, don't close this issue. You are the third (including me :smile:) who noticed it.

Hi people,
same topic, waiting for <IP_ADDRESS> as well...

@SilverFire is running subsplit now.

https://github.com/yiisoft/yii2/commit/abb503c284ad371159244c2e7c388827a0f12fe9#commitcomment-27773170
https://packagist.org/packages/yiisoft/yii2#<IP_ADDRESS>
You're welcome

Thank you very much :-)


On Completion, insert and replace when there is something after the cursor

for instance, there is "timer", I put the cursor after the t and choose twitter
current result is:
"twitter:kindimer"
expected result would be:
"twitter:kind"
same applies for options.
How to handle the remaining parts if more complex such as:
"timer:value?delay=1000"
if I autocomplete after the t with twitter:kind, what would be the result?
"twitter:kind"
"twitter:kind?delay=1000"
"twitter:value"

This is a client side behaviour from what I found out. In Eclipse it is controlled by Settings for Java but for XML there seems to be no setting at all. For VSCode I haven't checked yet.

this can be done on server side with the textEdit parameter https://microsoft.github.io/language-server-protocol/specification

verified with master branch


Jetty 12: Restore Cross-Context Dispatch

While implementing Jetty 12 support (https://github.com/wiremock/wiremock/pull/2593), it was necessary to change the way NotFoundHandler was configured due to the fact that cross-context dispatch was removed. However, since the  Jetty 12.0.8 release, the cross-context dispatch was reintroduced.
References

https://webtide.com/back-to-the-future-with-cross-context-dispatch/0/
https://github.com/wiremock/wiremock/pull/2593

Submitter checklist

[X] Recommended: Join WireMock Slack to get any help in #help-contributing or a project-specific channel like #wiremock-java
[X] The PR request is well described and justified, including the body and the references
[X] The PR title represents the desired changelog entry
[X] The repository's code style is followed (see the contributing guide)
[ ] Test coverage that demonstrates that the change works as expected
[ ] For new features, there's necessary documentation in this pull request or in a subsequent PR to wiremock.org

What's the benefit of returning to this approach, given that you got it to work without?

What's the benefit of returning to this approach, given that you got it to work without?

Thanks for looking @tomakehurst , I think functionally-wise there is no benefits really, but implementation-wise the code becomes cleaner: the mock context explicitly needed an admin context for initialization (so we could simulate cross context dispatch), that is gone now.


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 1496 ms

Resolved: Bofrost.at performance has improved in 0e32f71 after 6 minutes.


incorrect definitely unassigned error with late

Although it looks correct the following code triggers an error :

The late local variable 'i' is definitely unassigned at this point - line 11

main() {
  late int i;
  bool b = true;
  while(true) {
    switch (b) {
      case true:
        i = 1;
        b = false;
        break;
      case false:
        print(i);
        return;
    }
  }
}

Tested on https://nullsafety.dartpad.dev/ (Based on Dart SDK 2.9.0-edge.2ed302bfbbbad1d10f6c839c504ae3871fc96dc2)

/cc @leafpetersen @lrhn

The example proves that i is not definitely unassigned, so there is a bug in the analysis.
Do we think it's in the specification or the implementation?
I'm guessing we're not going for a fixed-point when we analyse loops for type*, but reachability and definite assignment should be binary properties, so my hunch is that we should be able to find the fixed point of the reachability/assignment analysis in two iterations. (It doesn't depend on types or values, right?)

The example proves that i is not definitely unassigned, so there is a bug in the analysis.

@scheglov this looks like a bug in the analysis.  The analysis may approximate, but it should be sound (that is, it may say something is potentially assigned when it isn't, but it shouldn't say something is definitely unassigned when it isn't).

Right, just as we demote all variables potentially assigned in a loop, we should remove "definitely unassigned" from them.

https://dart-review.googlesource.com/c/sdk/+/151047


[@vercel/postgres] - Error: VercelPostgresError - 'invalid_connection_string' using drizzle orm

When attempting to establish a connection to the PostgreSQL database and drizzle orm using Vercel, the following error occurred:
VercelPostgresError - 'invalid_connection_string': This connection string is meant to be used with a direct connection. Make sure to use a pooled connection string or try 'createClient()' instead.

//db.ts
import { drizzle } from "drizzle-orm/vercel-postgres";
import { sql } from "@vercel/postgres";
import * as schema from "./schema";

const db = drizzle(sql, { schema });

export default db;

//drizzle.config.ts
import { defineConfig } from "drizzle-kit";

export default defineConfig({
  schema: "./src/database/schema.ts",
  out: "./drizzle/migrations",
  driver: "pg",
  dbCredentials: {
    connectionString: process.env.POSTGRES_URL!,
  },
  verbose: true,
  strict: true,
});

I have already set the POSTGRES_URL in the .env file
# npm packages
@vercel/postgres: ^0.7.2 => 0.7.2
drizzle-orm: ^0.29.3 => 0.29.3

You have to use the other connection string that Vercel gives you, the connection pooled one. It should contain -pooler in the hostname. Vercel ensures here that you do not create a local pool against the direct connection string - as that would quickly exhaust he open connecitons on the database side.

Thank you @janpio


Box bracket value attributes

The value input needs to be declared as an angular input property.
Update the docs to reflect the box bracket requirements.

Not true in this case. The value would only need to be wrapped in [] if it was a dynamic value.
In your PR, you had
[value]="nes"

In that case, we'd expect there to be a property in our class called nes that would have the actual value. But if we remove the [], the value property is no longer dynamic, and treats nes as the value.


Cannot use exp without an account

Was wanting to use the software but don't want to create an account with any online service.

You could use create-react-native-app if you want to use most of Expo without an account. exp requires an account because it lets you do things like send push notifications and publish your project, which require a developer account.

Are the sources available for those features anywhere to run on my own server? Thank you for the prompt reply!

The server isn't open source for some technical and product reasons (ex: we ensure that everyone's push notification credentials are encrypted and behind a VPN, our client code doesn't have to be infinitely backwards compatible with old servers). So if you wanted to run your own server you could use create-react-native-app and eject to bare React Native (and not use Expo). Like GitHub, Apple, Firebase, and other common developer services you need a dev account to use Expo services though.
These are some posts about Expo philosophy too:
Open Sourcing the Expo client: https://blog.expo.io/open-sourcing-the-exponent-client-9b37634c13d7#.n3xdmqq0j
Expo is Free (as in 🍺 and as in 💬): https://blog.expo.io/exponent-is-free-as-in-and-as-in-1d6d948a60dc

Okay sounds good. I was very confused as I came from a prominent article that was featured recently but I couldn't find a way to use the software without the service. I think it is really great that the code to interact with the service is open, but that unfortunately isn't useful for me. Thanks again for your prompt replies and best of luck on your business.


wasm performance compared to bevy_audio

Hello! 👋
Thanks for all your work! I really love this crate ❤ ❤
I'm creating this issue because I'd like to document some surprising (to me) behavior of bevy_kira_audio / kira in comparison to bevy_audio 😄
Because of some  crackling audio in the browser (see #27) I recently ported a project of mine to bevy_audio in a branch to experiment.
After porting I noticed a significant speedup to load times as well as the crackling audio going away.
Anecdotally, when using bevy_kira_audio it takes a couple seconds for my "Play" button to display and then a couple more after clicking "Play" for the scene to render. When I switched to bevy_audio, everything much quicker, i.e. no delay between startup and "Play" button or after clicking "Play".
project code: https://github.com/shnewto/limbo_pass
wasm branches

wasm-rodio
wasm-kira

Some of this is definitely a candidate for being system specific, I'm on macOS Monterey 12.3.1. I'd be curious to know if this is or isn't the case for someone with a different setup.

oof, I'm not sure about the behavior I mentioned above anymore. not sure what I bumped (maybe my head 😅)  but my wasm-rodio branch seems to be crackling too and has a delay loading the scene 🤔

Thank you for looking into this!
Let's see if #48 changes anything here. I've had fewer issues with Bevy 0.7 so far, but will investigate again after updating to latest Kira.

Closing because I've spent some time digging and am convinced the crunchy/crackling audio isn't a kira or bevy_kira_audio issue. It's still there when I use rodio. I did get the behavior to change when I increased a default raw audio buffer size in cpal so that's probably where I'll keep looking. Thanks for your time ❤

Could you tell me more about the changes in cpal that improved the situation? Maybe this is something that could be made configurable through Kira/rodio?

@NiklasEi The changes I was experimenting with in cpal were mostly in the build_output_stream_raw function here https://github.com/RustAudio/cpal/blob/223f28262a80ac0b81688eb58507a4fb243e0694/src/host/webaudio/mod.rs#L185.
The crunchy audio while loading made me suspect some buffer underrun so I toggled the configuration buffer size, here https://github.com/RustAudio/cpal/blob/223f28262a80ac0b81688eb58507a4fb243e0694/src/host/webaudio/mod.rs#L202-L211
It does look like kira is building up a cpal config object https://github.com/tesselode/kira/blob/acb99e9e322da95cd91c4529d9a9f520e824ac56/crates/kira/src/manager/backend/cpal/wasm.rs#L51 so it might be feasible to expose it.
Fwiw though, I'm not sure toggling that buffer size is ultimately the fix for my crunchy audio issue because I had to make the buffer a lot bigger and from the documentation it seemed like the main use case is actually making it smaller 😅 .


Some of the Twitter account links in README.md are suspended

Hi there I saw some of the twitter accounts are suspended for example in Full amazing stacks @BenjaminCodes and @EmmaWedekind.
Just wanted to clarify if the list should have some sort of identification on the README.md to show user account that are currently disabled/suspended?

Was thinking if this should utilize the twitter API to check suspended users via "users/lookup" from the user_id to via a cron job. But probably the yearly check through is good for now.

Hi there 👋 Thanks for pointing this out, I will go through them and delete the ones that are not active anymore ☕ I think this can happen if they change their handle also.

No worries glad to help was thinking of putting a PR for it but if your going to do it ill leave it.
Yeah especially coming from twitter it would be better to have the link from the unique identifier that way we dont have to worry of the handle changes


Data cleaning task for যা দেখেছি যা বুঝেছি যা করেছি - chunk 1

This is the data cleanup task for যা দেখেছি যা বুঝেছি যা করেছি - chunk 1.
What to do

Remove all non-Bangla characters and words that do not make any sense or cannot be traced back to the original text.
Fix spelling mistakes in the extracted text. You'll see that some words are incomplete and some words contain garbage characters. To fix it, you can replace it with how it is originally written in the book. As long as the texts match what's in the original book, it's good to go.
Keep the metadata (page numbers, publisher's name, table of content etc.) as it is.

Links
You can download the text file from here.
After clicking the link above, click 'Download raw file' (the download icon) on the top right corner to download the file to your local machine.
Click here for the original book.
Important
Please follow the instructions in CONTRIBUTING.md to start contributiing. Do not assign the issue to yourself right away and start working on it. If you have any questions about the contribution process or you hit a roadblock, please feel free to reach out to me (@dg1223) or any other team/tech leads by commenting here or on our Whatsapp channel.
Thank you for willing to contribute to this project.

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Is this issue done for now. Should I close it?

@Irtizaya This chunk is ready for use


fix(TDI-38446): fix issue with shared bulk connection

What is the current behavior? (You can also link to an open issue here)
NullPointerException is thrown, when use PartnerConnection instead of Bulkconnection in bulk mode.
What is the new behavior?
Store connection holder in container, and share both connection in bulk mode. In non-bulk mode - only PartnerConnection.
Please check if the PR fulfills these requirements

[x] The commit message follows Talend standard
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features) ?
[] The code coverage on new code >75%
[x] The new code does not introduce new technical issues (sonar / eslint)

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 / CI related changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[x] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:

Pull request test result: success :star:


Show an 'optional' tag for optional questions

Instead of showing an asterisk for required questions in the UI, we'll show (optional) next to any optional question.

If we remove the asterisk for required questions, how we should tackle validations in UI when a user tries to submit a response with multiple required questions and more than one is missing?
cc @nataliaElv @Amelie-V

So, the submit button won't be available until all required questions are filled out
cc @keithCuniah @leiyre

This has been already solved, so I'm closing this issue.


Add new FAIR-by-design Microlearning tutorial from Skills4EOSC

According to the agreement for collaboration between the projects, we are submitting a new tutorial to be published as part of the Galaxy Training Materials.
The FAIR-by-Design tutorial is an adaptation of the original FAIR-by-Design Microlearning Unit that was developed for the purposes of the Skills4EOSC project and is available at https://fair-by-design-methodology.github.io/microlearning/latest/
It's focus is on how to integrate the FAIR principles during the process of developing training materials and has thus been added to the contributing topic in the other section.
This version has been adapted to the organisation and rules for development defined for the Galaxy training platform.
The tutorial has been completed and is now Ready for Review

The linter is also complaining a bit with:
CONTRIBUTORS.yaml  has errors
  [/CarolinLeister] key 'joined:' is required.
  [/achim-kit] key 'joined:' is required.
  [/agCleo] key 'joined:' is required.
  [/CRHAD26] key 'joined:' is required.
FUNDERS.yaml  has errors
  [/skills4eosc/github] 'https://github.com/FAIR-by-Design-Methodology': not a boolean.

All required changes have been implemented.
Note that we did not edit the ORGANISATIONS.yaml file that the lint is reporting as erroneous.

All  required changes are implemented.

Dear colleagues from the Galaxy Training Network,
can we have some feedback on the process of the acceptance of the FAIR-by-desing Micro-learning tutorial from Skills4EOSC? I believe that we answered all the comments and addressed all the requirements from your side.
All the best and looking forward to have the tutorial available for the GTN community.

Hi @amisev1971 I see no reason why we cannot merge this in principle, but will need a bit of further work to fully fit with GTN style and guidelines (i.e. minimize the custom html etc). I can help with this, but I just need to find a bit of time. And it could be useful to have a further discussion at some point about how to best align the metadata, to make it fully and optimally machine-readable.
On a practical note, would it be possible for you to give me write permission to your repo so that I can help out with all this? (When creating a PR from an organisational account these permissions aren't always automatically set by GitHub as they are with personal accounts). I tried to fix the merge conflict but was not able to push to your branch. And then I can also implement some formatting changes to fit better with GTN best practices.
We do also have the option of merging your tutorial in 'draft mode' (by setting draft: true in metadata), then it will go online and be accessible via URL, but hidden from the topic page for the time being. But this will allow you/us to shared the rendered tutorial with colleagues and have more detailed discussions around it, while still finalizing the final form of the tutorial. The only requirement for merging in draft mode is that the build test passes (but first we must solve the merge conflict in order for that test to run)


Wind Tunnel scenario execution

Wind Tunnel is most useful when scenarios are run regularly in the same environment. There is already a Nomad cluster which has been set up for testing and can be used for this purpose.
Completion of this issue requires:

[ ] A scenario can be configured as code to be deployed and run on a given number of nodes.

Note: The code deployed is monomorphic, but can behave differently depending on included configuration.

[ ] The required infrastructure for reporting results is deployed (InfluxDB + Telegraf).

Note: We may want a "run-id" to be included with the reporting, so we don't have to clear these between runs and it is still easy to identify which metrics / logs go with each scenario run.

[ ] Target nodes can be cleaned after a run. E.g. so that Holochain is stopped and its data cleared between runs.
[ ] The end of a scenario is understood by the control plane, so that scenarios can be left to run back-to-back without needing manual intervention.
[ ] There are notifications produced when something goes wrong with a scenario or something prevents running the full set of scenarios.

Best estimate for this issue is 2 weeks.

We might need to spike/design more to understand how to implement these requirements: there is currently some flux with tfgrid development, etc.

we should be able to develop scenarios without requiring access to a big real-world execution cluster.


Fixes compilation on MacOS

Advice in the README doesn't really work on modern Macs. What works thou is running xcode's version of clang.

Hey @mynameisdaniil , thanks to point it out, I checked and not able to find the file in my macos 14.6.1 and I tested the xcrun -r clang works.
I'm not familiar with macos, I'm not sure whether it also works well for macos 10.14, could we keep the description in README file for backwards compatibility?

@falood sorry didn't see this comment for some reason. Sure, but I've added a note that on newer versions this file doesn't exist.

Thanks ❤


6-pm-d: LL course form validation

Course form fields now all required--form won't submit until they are all filled out.
Validation on quarter: has to be in the form [first letter of quarter][last 2 digits of year]
e.g (2020 quarters): F20 / W20 / S20 / M20
Validation on email: has to end with<EMAIL_ADDRESS>Back end wont save a course if a course with the same name and quarter already exists.

@lukelewis66 you need to get this green on CI before it can be merged.  If you need help with that, please:

ask in section today
ask during office hours
ask on Slack

Quarter format needs to be changed to "YYYYQ", where Q: 1, 2, 3, 4 for winter, spring, summer, fall respectively

This PR needs a code review from at least one other member of the team before the staff will look at it.

40 pts!


Make build targets more debuggable

This PR changes the uglify options so that the output is more easily debuggable, provided that the minify option is set to either "minify" or "beautify".  the default mode is "mangle" and that is unchanged.

Lint?

@derrell : Is it ok for you now?

@hkollmann I don't think it has changed yet, but if I interpret @johnspackman 's comment correctly, he will make the change I requested to turn off sequences for mangle too.

He did with the last commit!

Indeed. My mistake.

Thanks, @johnspackman !


_rt_to_github_map

It would be good if:

_convert_one_ticket could add to _rt_to_github_map each time it's converted a ticket, so _rt_to_github_map stays up to date; and
There was an option to dump _rt_to_github_map to a JSON file at the end of the conversion.

... so at the end of the process, there's a JSON file with a map of RT tickets to GitHub issues, and that can be used if I need to do any further processing.

Also, if the JSON dump already existed when the script was run a second time, it could provide a shortcut for _build_rt_to_github_map.

Thanks for the suggestion. I think the first part about updating as it goes and dumping the JSON makes sense. A PR to implement that would be great.
I don't know that supplying this JSON file as input is that useful. You'd have to have a huge number of issues before the speed or GitHub API limits made this worthwhile.


Failure to download Facebook reel.

[~group]$ yt-dlp -U Latest version<EMAIL_ADDRESS>from yt-dlp/y t-dlp yt-dlp is up to date<EMAIL_ADDRESS>from yt Latest version<EMAIL_ADDRESS>from yt-dlp/yt-dlp yt-dlp is up to date<EMAIL_ADDRESS>from yt -dlp/yt-dlp)


verify go mod in CI

What type of PR is this?
/kind enhancement
What this PR does / why we need it:
Refer to openyurtio/yurt-app-manager#94
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Does this PR introduce a user-facing change?

other Note

/lgtm
/approve


⚠ Jenkins Plugins Artifactory has degraded performance

In 940a8eb, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1214 ms

Resolved: Jenkins Plugins Artifactory performance has improved in a6dd8e3 after 21 minutes.


"alfred-weather" can't be opened because Apple cannot check it for malicious software

I updated to the most recent release, and I'm seeing this:

This software needs to be updated. Contact the developer for more information.

I'm on macOS 10.15.6

@technicalpickles this is part of security changes made in macOS 10.15.0. Apple now requires binaries to be signed via their developer program, or it will show a message like this & prevent their being opened.
There is a workaround, however!
After seeing that message:

Open System Preferences
Open “Security & Privacy” prefs pane
Switch to the “General” tab
In the lower section, “Allow apps downloaded from:”, there will be a message to the right with an “Open anyway” button; click that, and authorize it via password or fingerprint.
Try running the alfred-weather workflow again, and it should work.

Alternatively, you can:

Click "Show in Finder"
Right click alfred-weather executable
Hold down control on keyboard, and left click Open.
Click Open again.

The process has no been manually opened and macOS says "it's OK to open in future". You can quit Terminal and everything should be fine.
I always find it much faster to do rather than via System Preferences because sometimes you need to open the app/process again, as well as input your password to unlock System Preferences. It might be worth adding a note/tutorial on how to do this for future users, or even link to this issue.

@noahmaranesi, does that work on macOS 10.15 Catalina? My experience has been that the simpler workflow you’re referring to had been removed. But maybe it’s a bit harder to trigger than it used to be is all?

@jeffbyrnes, I believe so. I know it works on at least macOS Catalina!

Current releases are notarized, so this shouldn't be an issue.


WIP refactoring parsers

@maliheha and I are working on this on my fork. These updates aims to separate the parsers for different sections of the log into submodules so things are easier to unit-test and modify as we go.
@mattmilten no need to review for now, we'll let you know when it's in a more complete state.
@ronaldvdv we noticed you're also adding some tests and example data - can we fold this into the refactored code? Just want to make sure we aren't duplicating work and writing tests that may eventually clash with one another. Happy to discuss and coordinate together.

@mattmilten we are pretty close to done with refactoring in this PR :) There are some very minor behaviour changes which we've documented in the changelog. To try to avoid regressions, the previous code is still in the repo, and tests/test_regression.py tests the refactored code against the v1.3.2 code (we should delete both of these before finalising).
When you have a chance to review could you let us know your thoughts? Probably a few things could still be tidied up but we're quite happy with the structure.
Thanks @maliheha for your great work on this so far, and for putting the below summary of the new structure:

In the new design, parsers are the most inner layer, each responsible for parsing a specific section in the log file.
The parsers can be found in src/grblogtools/parsers/. Each parser has a main method parse() that takes a single line as an input and returns True/False in case the line is matched by a pattern associated with the parser.
Each parser has two other methods named get_summary() and get_progress() (if applicable) to return the parsed summary or the detailed progress.
The next layer is the SingleLogParser which is responsible for parsing one single log run.
The SingleLogParser(see src/grblogtools/parsers/single_log.py) has the main method parse() which takes in a line as an input and returns True/False if the line is matched by some patterns. The SingleLogParser has two internal variables: current_parser and future_parsers which keeps them updated as it sees more lines. It initializes by setting the current_parser to the header_parser and the future_parsers to the list of remaining parsers. If a line is not matched by the current_parser, the SingleLogParser checks whether it should pass the parser to any of the remaining parsers or not. As soon as any of the parsers in the list of future_parsers returns True, the current_parser and the future_parsers are updated.
The final layer (API layer) (see src/grblogtools/api.py) has also a method named parse() where it takes in strings of log file patterns as individual arguments and returns a ParseResult object. The methods summary() and progress() of the ParseResult class returns the summary dict and search progress information as before.
The main method of the ParseResult class is parse() that takes in the path to a single log file (the log file can include multiple runs) and uses SingleLogParser objects to parse each log run.
The API also includes a legacy function named get_dataframe(logfiles, timelines=False, prettyparams=False). i.e. the API is unchanged other than dropping merged_logs (these are handled automagically)
The usage example of the API can be found in the header of the api.py module.
Unit tests can be found in tests/ where separate tests are written for individual parsers and api.
There is a file named test_refactor_regression.py including regression tests to ensure the equivalent outputs from the current grblogtools api and the newly designed api.
The tests run against current test data in data folder and newly added test data in tests/assets.
The plotting API is left untouched and there is no plan to re-factor it under this project.
The extension of the current API to tuner, multiple objective optimization, concurrent and distributed optimization are the next steps, which can be directly incorporated into the main grblogtools git repo after the current base code is reviewed and hopefully merged.

Excellent work! One question: would it make sense to define a base class for the different parsers? They all implement the same function anyway but the classes do not seem to be connected by a common base class.

Thanks! I don't think abstract base classes really add much here. There's a common API between classes but the abstract class doesn't add any functionality, so I'm inclined to just leave it as is.

@mattmilten this is ready to go!


Unable to use back/forward mouse buttons for the history.

OS: Windows 10 Pro, Version: 1803, Build: 17134.112
GPMDP Version: 4.6.0
Issue Descriptions: Unable to use mouse back/forward buttons to go back and forward in the history.
Steps to Reproduce: Install the latest version 4.6.0 and try using the back/forward mouse buttons.

Downgraded to 4.5.0 and the back/forward mouse buttons seems to be working fine there, so there must be something in 4.6.0 that causing that not to work.

This is caused by an unhandled exception in the discord rich precense feature.  I'll look at fixing it tomorrow and releasing a patch


Limiting validation to US only server.

Is your feature request related to a problem? Please describe.
Been using Let's Encrypt on a low-traffic server for a consulting project for a few years now.  The validation only recently started failing, and after research it seems to be because we geo-block to US-only access.  This seems like a reasonably standard scenario for a US-based company.  The geo-block has been in place a long time, but it seems the Let's Encrypt service only recently started hitting our validation from non-US server and failing.  For example, the validation worked perfectly in February, but failed in April with no changes on our end.
Describe the solution you'd like
Need a way to verify that only US-based servers will be used for validation request, so that we can maintain automatic renewal.  Or some way to verify the source of the request originated from the Let's Encrypt server to allow it past the geo filter.  Maybe a custom header that is provided by the client to compare?
Describe alternatives you've considered
I'm checking with security team if they are okay relaxing the geo-filter.  I think we can disable the geo filter to do the renewal, but that is obviously not sustainable for automation.  Also looking into the DNS-based verification, but the provider we are currently using (Network Solutions) is not on the list of DNS providers with automation.
Additional context
This is a simple project for a low-budget organization, with very low traffic generally only in a small local area.  Let's Encrypt is an amazing solution for low-budget projects, but this restriction on world-wide geo access is a strange requirement for keeping a strong security perimeter around a very local project for a small company.  I've already spent significant amount of their budget trying to figure out this issue, because the errors and troubleshooting is very difficult with issues like this.  It's getting to the point that it would ironically be cheaper to pay for a non-free SSL certificate, which seems like a step backwards for Let's Encrypt.
Thanks!!

ACME clients like win-acme have zero control over the Certificate Authority.
If you wish to continue using http validation (instead of DNS validation, which would not have the same limitations) you should either unblock all countries, blokc specific countries or allow all http /.well-known/acme-challenge/ requests.
General Let's Encrypt topics like this are best discussions on the Let's Encrypt forum https://community.letsencrypt.org/ and when discussed here should ideally be a Discussion, not an Issue.

What Chris has written is true, the client cannot control this at all.


Make Lua optional

With conditional compilation of Lua we could open the door to other scripting languages.

We can completely replace the Lua C-based interpreter with Rust-based Mun.


GH-238 Rework/Improve Bitfield pin value rendering

Fixes #238

Applied to main (=2.1) and branch 2.0.


Phone Auth with kotlin/js

How can I implement phone auth using this library on a kotlin/js. I searched at many places and also tried to understand from the source but couldn't get it. Can you please help me with that. Thank you.

Did you find any documentation or something on how to implement auth (especially phone number + OTP verification) in Kotlin?
Thank you.


Update branding to 3.0.0-preview

We were using alpha1 as a placeholder. The latest guidance from PMs is to label pre-release packages as 3.0.0-preview-$(buildnumber).
cc @mmitche

Oh BTW do we need to also remove anything related to doing -final? Or is that already gone?

-final is already gone :)


Unexpected crash

Issue description
I dont know how to reproduce

Expected result: What were you expecting to happen? -
Actual result: What actually happened? -

Steps to reproduce the issue

OS and versions

Plugin Version: Dev731
PocketMine-MP: 3.22.0
PHP: 7.4
Game version: Win10

Other Plugins
Some plugins are private

If you remove all other plugins, does the issue still occur? I didnt test it because i dont have more servers
If the issue is not reproducible without other plugins:

Have you asked for help in the community discord before creating an issue?
Can you provide sample, minimal reproducing code for the issue? If so, paste it in the bottom section.

 Please provide a full crash dump. If the server did not crash, then it works as intended.

I have been confused with putting crash, it was an internal server error.
It happened to one of my players and he didn't come back in, I can't know how to reproduce it


Drop Python 2 from master, add Django 1.11

1.11 alpha is out, master is going to become 2.0.

Current coverage is 58.86% (diff: 100%)

Merging #794 into master will not change coverage

@@             master       #794   diff @@
==========================================
  Files           110        110
  Lines          5844       5844
  Methods           0          0
  Messages          0          0
  Branches        713        713
==========================================
  Hits           3440       3440
  Misses         2266       2266
  Partials        138        138

Powered by Codecov. Last update 3904792...dee9a41


Add category top section as static content.

Add category top section as static content.

Fix conflicts

Conflicts resolved


KCE: Add tests with Exasol DB V8

This was implemented in https://github.com/exasol/kafka-connector-extension/commit/42c0ad3e41f6e132facf10090c75dd06fcfba08b#diff-93e5446a47028d87098135fdb2d7031c8d8929270f752dd58db54293a4e877f2


[Slider] Vertical slider tooltips are showing behind other thumbs

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
When using a vertical ranged slider, the value tooltips are showing along the track AND behind the other thumbs.

Expected behavior 🤔

The tooltips should be shown on the right side for vertical sliders? Instead of above
At least, it should show above other thumbs.

Steps to reproduce 🕹
Simple reproduction
https://codesandbox.io/s/mui-slider-vertical-tooltips-1xqly4?file=/src/App.js
Context 🔦
N/A
Your environment 🌎
N/A

Slider need more customization of tooltips like:
For vertical, there is left and right, so user customizes according to their need:

Similarly for horizontal top and bottom.


Fix ESLint configuration

Error: .eslintrc.js:
	Configuration for rule "required" is invalid:
	Severity should be one of the following: 0 = off, 1 = warn, 2 = error (you passed '{ some: [ "nesting", "id" ] }').

See https://github.com/HackYourFutureBelgium/hackyourfuture.be/runs/1194643281?check_suite_focus=true#step:6:11

which rule were you trying to add here? I'm not seeing anything for "required", "nesting", or "id" in the list of available rules here:
https://eslint.org/docs/2.0.0/rules/

a working eslint config for warning on inner block declarations, for example, would look something like:
module.exports = {
  globals: {
    __PATH_PREFIX__: true,
  },
  extends: `react-app`,
  rules: {
    "no-inner-declarations": 1
  },
}

which rule were you trying to add here? I'm not seeing anything for "required", "nesting", or "id" in the list of available rules here:
https://eslint.org/docs/2.0.0/rules/

Indeed, I have no idea. .eslintrc.js was added by @KevinTss in abd8d283db8b84fafc61c61979bd6868737b4ce4

Ah, got it. Just to get CI working we could either remove that bit or add something similar to what I suggested above.