Can I add bourbon v5 (beta) to my project with Bower?

I'm using Autoprefixer, so a lot of mixins from bourbon v4 conflict with it. Bourbon v5 (beta) fixed this issue, is there any way to add it to my project using Bower?

Add this to your bower.json
"dependencies": {
        "bourbon5":"bourbon#v5.0.0.beta.7",
    }
```

I’m going to close this issue, as it appears to be resolved.
Couple things worth noting:

Installing the beta from the command line is also possible: bower install bourbon#v5.0.0.beta.7
Autoprefixer will also remove out-of-date prefixes, so there shouldn’t be a conflict per se with using Bourbon 4.x with Autoprefixer, more that the work of prefixing would be happening in two places. I note this because sometimes a Bourbon upgrade is not a quick task, but that shouldn’t keep you from introducing Autoprefixer into your toolchain.

Thanks, that did the trick!
Is there any way to specify the version in a way, that allows checking for updates?
(analogue of "neat": "^1.8.0")
No big deal if that's impossible, just curious.

there shouldn’t be a conflict per se with using Bourbon 4.x with Autoprefixer
I used "Background Image" mixin, and it resulted in two identical "background-image" rules appearing in my css. Not a deal-breaker but it buggered me.
Overall I prefer to move on to Bourbon5, because a big part of B4 documentation is simly wendor-prefix-mixins, which I don't really need to know.

@Trost123  In my workflow i've a folder to store frameworks/libs and my projects load the stuff and tools from this place, so i can deal with multiple versions of bourbon, or others between my projects. Structure and gulp file is here, https://github.com/mistergraphx/Fragments_builder.

@mistergraphx Thanks, but I think you misunderstood my second question there.
It's more of a bower-related question (maybe I should post it there?):
Let's pretend I do "bower install bourbon#v5.0.0.beta.7" and then bourbon#v5.0.0.beta.8 is released.
If I use "bower update" in my console - bourbon will not be updated.
Screenshot of issue
I think there must be something like "bower install bourbon#latest" but to install latest pre-release.

I've understood but not really answered ;-).I gived you an example of switching between multiple versions during the pre-release period.
I'm not a "bower expert" but in the bower registry if your do bower search bourbon it's the version 4 witch is actually downloaded cause it's the stable branch/tag, as in the Ruby gem and It's just the maintainer of a package who choose to publish a new revision of the bower package, see : https://bower.io/docs/creating-packages/#register
That's why we add the specific tag #<tag|branch>, as described in the bower install documentation https://bower.io/docs/api/#install.
You can try to download directly from the master branch using bourbon#master, but i'm not certain it's a good practise if your project is in production ;-)

@mistergraphx
I guess we'll just have to update manually until v5 is released as stable, but that's no big deal!
Thanks for the help. 👍

@Trost123 I don’t use Bower a lot, so can’t speak from experience, but it appears that you can specify a range of versions: bourbon#>=5.0.0.beta.7 <5.1.0. This should match any betas released after beta 7, and also match the stable release of 5.0, including any patch releases (5.0.x).
I just found this neat tool from npm which helps you visualize these SemVer qualifiers: https://semver.npmjs.com/.

@tysongach Thanks, that's exactly what I needed! And that tool sure is handy.
Also noticed a weird thing:
"npm info bourbon" returns all versions, up to 5.0.0-beta.7'
"bower info bourbon --verbose" returns versions up to 4.2.7
So the problem must be on bower's side, as NPM let's me do "bourbon#>=5.0.0.beta.7 <5.1.0" like you advised and bower doesn't.
I'll leave you alone go annoy the Bower team from now on. 😈

Ah, I think there are minor discrepancies between Bower and npm and how they handle SemVer with pre-releases. Some accept a hyphen (-) to denote pre-releases, others only accept periods (.). I can't remember who accepts which formats. I keep meaning to sit down and write it all down for reference later…but just something to watch out for.

@tysongach I don't think it's about that.
See this screenshot: Bower actually thinks that 4.2.7 is latest version. Also note that there are older betas in the list (on the screenshot), like "3.2.0-beta.2", so the naming conventions are not the issue here.
Going to post it on Bower repository to figure it out.

Interesting. Yeah, it would be nice to confirm whether Bower does or does not include pre-release versions when listing.
I think Bower piggy-backs a lot of Git/GitHub tags, so it is possible we didn’t properly tag things right before, or now? It’s very opaque, but I’m intrigued to learn more!

@tysongach I think I found the pattern. Look at all "beta" and "rc" versions that are in my screenshot.
Versions like "3.2.0.beta.1" are not recognized by Bower correctly, while v3.2.0-beta.1 (or 3.2.0-beta.1) are recognized.
Also if you go to https://semver.npmjs.com/ and enter "bourbon" into "pick a package" field and press enter, you'll see versions output in this format: "5.0.0-beta.5", "4.2.0-pre"

So this goes back to my comment above on whether a hyphen or period was used to denote the pre-release. Unfortunately, npm and Bower handle this nomenclature differently than RubyGems (which we also publish to).
The Semantic Versioning spec indicates that “A pre-release version MAY be denoted by appending a hyphen and a series of dot separated identifiers immediately following the patch version” (e.g. 1.0.0-alpha.1).
However—if I remember correctly—RubyGems throws an error and will not publish a pre-release denoted by a hyphen, only if it is a period.
There is an open PR to Semantic Version that tries to clarify the correct method (hyphen) and I hope that RubyGems aligns with everyone else.
I found all of this out through trial and error once I took over maintaining Bourbon. I plan to sit down and map all of this out with learnings and note the conflicts. I may have mistakingly versioned things incorrectly, and between Git/GitHub, npm, Bower and RubyGems, we have confusion.

Here is some documentation from RubyGems on them indicating use of a period to denote pre-releases: http://guides.rubygems.org/patterns/#prerelease-gems
I think the action here is that version number every but RubyGems, needs to utilize the hyphen, in accordance to SemVer. RubyGems appears to be the violator of that spec, so we’ll have to use the period for them here: https://github.com/thoughtbot/bourbon/blob/master/lib/bourbon/version.rb#L2.

Nah, I’m curious what they say and see if our assumptions are correct.

I guess guys at Bower can fix (workaround) it, because NPM actually transforms "." into "-" before "beta"
As seen in "[npm info bourbon](npm info bourbon)"
So they could do the same.


[FEATURE REQUEST] Language Selector

Thank you for developing this app, it is really well made!
My only issue, and here comes my request, is that there should be the option to select the language within the app, because if the system language set is different from German or English, the entire UI will be displayed in German, and for someone like me who doesn't know the language, it is really debilitating.
For now, I have set the system language of my iPhone to English, solving the problem.
Maybe the functionality could simply be modified so that if the system language is different from German, the UI is displayed in English, which is certainly more international.
I encountered this problem on an iPhone 15 Pro with iOS 17.5.1.

Hi, thanks for the request
Yes I'm add a new base language English.
But I'm currently searching for people to help me to add more languages
https://crowdin.com/project/igotify

Hi, thanks for the request
Yes I'm add a new base language English.
But I'm currently searching for people to help me to add more languages
https://crowdin.com/project/igotify

Hi, i'm really happy to help you for italian language!


Add support for side VC's lifecycle events

It seems like the left/right VC's viewWill/Did Appear/Disappear events are never triggered during open and close, thus they never get a proper chance to refresh. This PR adds support for it.

The complete blocks would be a preferred way to refresh the content of the view controllers/views. Apple says calling those view lifecycle methods should be avoided.


Add docs about using JavaScript libraries that render UI

Fixes https://github.com/dotnet/aspnetcore/issues/22974

We need to check carefully ... I started editing before your 2nd and 3rd commits.

Wow @guardrex, you are very quick to response 😄

Yes, ready as far as I'm concerned.


Free use of sdk

Issue Type
[ x ] Question
I'm a little confused because of the free use of the SDK. The first Sentence on the Repo "osmdroid is a (almost) full/free replacement" confused me.
I have read the license file.
Could someone please tell me if I can use this SDK in my App (i want to upload this app also in AppStore) for free and without to publish source code?
I will use my own tile-server and just want to use the map and markers.

It's free to use under the terms of ASL 2.0 license. There are a few
exceptions due to GPL dependencies on specific optional sub modules
It's an almost full replacement for Google maps
On Thu, Oct 20, 2022, 9:52 AM Enrico @.***> wrote:

Issue Type
[ x ] Question
I'm a little confused because of the free use of the SDK. The first
Sentence on the Repo "osmdroid is a (almost) full/free replacement"
confused me.
Could someone please tell me if I can use this SDK in my App (i want to
upload this app also in AppStore) for free and without to publish source
code?
I will use my own tile-server and just want to use the map and markers.
—
Reply to this email directly, view it on GitHub
https://github.com/osmdroid/osmdroid/issues/1861, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPCIGLKFO3JRMGOIPSRCGTWEFFCZANCNFSM6AAAAAARKFXADI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

@spyhunter99
Thank you very much :)


IconToolbarItems's icons replaced by text when Text binding of any item changes

I have a Toolbar with a few IconToolbarItems, some of them displaying Icons via the Icon property, some displaying Text using the Text property.  The Toolbar is part of a IconCarouselPage.
I noticed the following bug:
When the Text property of an icon displaying Text is changed, all other, unrelated IconToolbarItem's icons vanish and only reappear, as soon as there is some major "change" like pushing a new Page or swiping left and right.

would it be possible to add a property "IconText" to IconToolbarItem? When the "Text" property from the base class is used, it calls some private base class methods which cannot be overriden and make the icons disappear.


Mapped ports only available to localhost now?

Maybe it's just me, but I was exposing ports in the PIA docker-compose file for other services that rely on it. Now those ports only seem available on localhost. Did something change?

Hi there!
Are you exposing or publishing ports? Would you mind sharing your docker-compose (take care to remove credentials)?
Nothing changed as far as I can tell. I have however made several changes today so maybe try docker pull qmcgaw/private-internet-access to get the latest version?

The compose file is identical to the one in the repo with the notable exceptions being different username and password and one additional port for mysql. I also had to add a shadowsocks password to get it to run.
mysql-docker-compose.yml.txt
pia-docker-compose.yml.txt

Oops. Accidentally closed this.

I've been trying to create a LAN behind PIA using iptables, not your Docker, although it would be great if I could use it for that purpose. Could that be causing problems? Can't imagine why. Would iptables -F screw things up?

Ok so I removed the silly requirements of having to set the shadowsocks password if it's off, sorry about that.
Maybe my documentation is wrong, as I recall it needed a reverse proxy connected to PIA to access ports of containers connected with "container:pia".
A solution you could try that currently works for me is to have all your PIA related services in the same docker-compose file, see the instructions for Access ports of containers connected to PIA, all in the same docker-compose.yml.
It should look like:
version: "3"
services:
  pia:
    image: qmcgaw/private-internet-access
    container_name: pia
    init: true
    cap_add:
      - NET_ADMIN
    devices:
      - /dev/net/tun
    environment:
      - USER=js89ds7
      - PASSWORD=8fd9s239G
    ports:
      - 3306:3306/tcp
  mysql:
    image: mysql/mysql-server:8.0.16
    command: --default-authentication-plugin=mysql_native_password
    environment:
      - MYSQL_ROOT_PASSWORD=x
    volumes:
      - ./MySQL/var/lib/mysql:/var/lib/mysql
      - ./MySQL/etc/my.cnf:/etc/my.cnf
      - ./MySQL/etc/my.cnf.d:/etc/my.cnf.d
    restart: always
    network_mode: "service:pia"

Actually I just tested with a running PIA container with published port -p 8000:8000/tcp and this command:
docker run -it --rm -e LISTENINGPORT=8000 --net="container:pia" qmcgaw/port-checker

Try accessing your host to :8000 and it works. So I am unsure what your problem is, feel free to elaborate, maybe I skipped some information.


Feedback: RESTORE

Jessie Lin (lin-crl) commented:
Page: https://cockroachlabs.com/docs/v22.1/restore.html
What is the reason for your feedback?
[v] Missing the information I need
[ ] Too complicated
[ ] Out of date
[ ] Something is broken
[v] Other
Additional details

It'll be nice to add a section to show how to restore a backup using AOST RESTORE. Also note this end_time timestamp in show backup may be different from HLC timestamp (in ad hoc backups).
the current doc states AOST RESTORE can only occur on Backups with revision_history and should be corrected

example below
root@:26257/defaultdb> show backup 'nodelocal://1/backup/2022/08/17-185556.43';
  database_name | parent_schema_name |      object_name       | object_type | backup_type |        start_time         |          end_time          | size_bytes |  rows  | is_full_cluster
----------------+--------------------+------------------------+-------------+-------------+---------------------------+----------------------------+------------+--------+------------------
  NULL          | NULL               | system                 | database    | full        | NULL                      | 2022-08-17 18:55:56.43398  |       NULL |   NULL |      true
  system        | public             | users                  | table       | full        | NULL                      | 2022-08-17 18:55:56.43398  |        312 |      4 |      true
root@:26257/defaultdb> restore table shaun from latest in 'nodelocal://1/backup' as of system time '2022-08-17 18:55:56.43398';
ERROR: invalid RESTORE timestamp: restoring to arbitrary time requires that BACKUP for requested time be created with 'revision_history' option. nearest backup time is 2022-08-17 18:55:56.433980423 +0000 UTC

Jira Issue: DOC-5395

the accompanying crdb issue should get addressed before this docs issue.

demo@<IP_ADDRESS>:26257/movr> SHOW BACKUP FROM LATEST IN "userfile:///foo";
  database_name | parent_schema_name |        object_name         | object_type | backup_type | start_time |         end_time          | size_bytes | rows | is_full_cluster
----------------+--------------------+----------------------------+-------------+-------------+------------+---------------------------+------------+------+------------------
  NULL          | NULL               | movr                       | database    | full        | NULL       | 2022-11-08 16:39:36.12194 |       NULL | NULL |        t
  movr          | NULL               | public                     | schema      | full        | NULL       | 2022-11-08 16:39:36.12194 |       NULL | NULL |        t
  movr          | public             | users                      | table       | full        | NULL       | 2022-11-08 16:39:36.12194 |       4911 |   50 |        t
demo@<IP_ADDRESS>:26257/movr> RESTORE database movr FROM LATEST IN 'userfile:///foo' AS OF SYSTEM TIME '2022-11-08 16:39:36.12194' WITH new_db_name='movr2';

As @baoalvin1 demonstrates above, to conduct an AOST restore from non-revision history backups, any end_time displayed from a SHOW BACKUP cmd can be used for an AOST restore


Didn't receive email

On the Admin Activity page http://allready-d.azurewebsites.net/Admin/Activity/Details/16 you can send an email to the volunteers. I sent one to myself but did not receive it (not in junk mail either). I, however, did receive email from allReady when I became a volunteer.

The email arrived the following morning at 10:04. Don't know what the delay was.

Unfortunately, email is not a reliable mechanism for notifications. The fact that it did show up is good, means things do work :)

Closing as email arrived. Thanks for the report!


Deprecate IMPORT, EXPORT and GLOBAL keywords

Deprecated the following keywords:

IMPORT is simply useless, any symbol that isn't found in the current
file is automatically flagged as imported symbol.

EXPORT could be useful if a label is defined as label: instead of
label::, but the second version is preferred as it is less verbose.

GLOBAL imports a symbol if it isn't found in the current file and
exports it if it is found. Both comments above apply in this case.

As far as I know, some people use IMPORT as a way to make it explicit in the code. I don't know if this is something we want to allow or not. The keyword has been completely useless for a long time, it's basically a comment.

I use EXPORT rather than label:: quite a bit in my code, so I'm personally not a fan of depreciating it.

But why? I checked your comments in https://github.com/rednex/rgbds/issues/76 and you essentially use EXPORT as a comment to remind yourself that you are exporting that symbol. But I could say that it makes it less clear when you are checking the rest of the file as you have to go to the top of the file again to see which things you are exporting.
The ':' and '::' thing are clearer, I think.
I'm going to push the other patches and deprecate IMPORT, I'd like to know what others think about it. And, anyway, it's not going to stop working, it's just going to output a warning that can be silenced.

But why?

Because it's clearer for me, and it's how I like to organize it. Which is clearer, EXPORT or label::, is subjective IMO. But if it still works and just issues a warning that can be squelched, I'm fine with it.
Also, I agree that IMPORT is useless.

I'm going to close it,  I've just deprecated IMPORT, that should be enough.


doc(java-sdk-example):example to create tag via java-sdk

This PR adds an example in api tutorials section on how to create datahub tags via java sdk.
Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

@sachinsaju there's a lint error here
[ant:checkstyle] [WARN] /home/runner/work/datahub/datahub/metadata-integration/java/examples/src/main/java/io/datahubproject/examples/TagCreate.java:12:1: Utility classes should not have a public or default constructor. [HideUtilityClassConstructor]

@hsheth2 I have updated the PR after resolving the lint issues.But there is failure in one of the checks in smoke test and I believe it is related to frontend code.


Installation Documentation Missing

How is this built and installed?

@macropin I am working on an operation tool named Singular. Because the ContainerOps depends on Kubernetes, so our tool includes installing Kubernetes.  Singular also install other distribute projects like TiDB/TiKV, Nats. When the Singular working, we will update the documents.
Now the Singular already ready for install Kubernetes in the DigitalOcean.

I think those Singular links should be https://github.com/Huawei/containerops/tree/master/singular

@zoidbergwill Thanks, I updated my comment.


fix: fix bug with polyfill fetch

@microsoft-github-policy-service agree

When using fetch-event-source in the webview of iOS or Android, it is important to note that the fetch method is not implemented as native code. Instead, it is a polyfill that provides functionality similar to the native fetch method. One specific difference is that the polyfill does not have a response with a body of type ReadableStream. Considering this limitation is therefore crucial in such cases.

your code may cause repeated fetch requests. I adjusted it.
export async function getBytes(response: Response, onChunk: (arr: Uint8Array) => void) {
    const reader = response.body?.getReader();
    if (reader) {
        let result;
        while (!(result = await reader.read()).done) {
            onChunk(result.value);
        }
    } else {
        onChunk(new Uint8Array(await response.arrayBuffer()));
    }
}


Feature Request - Ordisrespector patch bonus script

Many raspiblitz users are not interested in storing ordinals on their nodes.
This webpage has an easy way to patch bitcoin core to exclude them.
https://v2.minibolt.info/bonus-guides/bitcoin/ordisrespector
it would be nice if Raspiblitz had a bonus script that would implement these changes.

Ordinals is just a numbering system.
You can not avoid storing these transactions  in the blocks and the UTXO-s in the UTXO set as they are valid in the bitcoin consensus.
The patch is about excluding them from your mempool, but that has undesired side-effects to fee estimation which is very important for lightning nodes.
Will not provide support for this, but you are free to make a custom script for personal use.


Run manual prevalence update without county-level canada data

Prevalence updates have been failing since 4/30 due to a validation error relating to Canada county-level data. I'm not entirely sure how to fix the validation error, so this prevalence update was run without that data at all -- the idea being that having most of the data up to date is better than having all of the data out of date.

Unfortunately, this does take Canada prevalence from lower-than-it-probably-is to zero, which is going to give false assurance.  Of course right now we're giving the whole world false assurance with prevalence numbers that often way lower than they ought to be, so one could argue it's better than the status quo.
I'd suggest using  the manual procedure I laid out in https://github.com/microCOVID/microCOVID/pull/1444#issuecomment-1132795890.  If you want, I can push up a PR using that procedure alone - #1444 combines the procedure with the warning code in #1437

@apiology where are you seeing the canada prevalence data as zero?
It looks to me like the result of commenting out the county-level data is that the microcovid website simply shows country and province as selectable options for canada, and doesn't offer the option to select a county:

https://deploy-preview-1447--microcov.netlify.app/
FYI I've pinged @beshaya (one of the main maintainers at this point) to take a look at this and the other PRs. I don't have authorization to merge.

@justinhaaheim: Ah!  I was probably making a bad assumption that this was the only data source for Canada--my apologies.  Given that, I should adjust my procedure accordingly in #1444.


Generate the initial options.json even if CONTAINER_PRESERVE_CONFIG set to true

🚀 Feature Proposal
https://github.com/felddy/foundryvtt-docker/blob/c780e0f9aafc154fa37bfb7d82624f0368adffba/src/launcher.sh#L22
It only checks CONTAINER_PRESERVE_CONFIG as for now, but didn't check if the file options.json/admin.txt exists. So it won't generate the initial config files if CONTAINER_PRESERVE_CONFIG set to true.
I think it's better to also check if the config files exist, else update/generate.
e.g.:
if [[ "${CONTAINER_PRESERVE_CONFIG:-}" == "true" && -e options.json && -e admin.txt ]]; then

Motivation
It's more convenient to use if generate the initial configs but preserve it form regen without modifying container env var.
Example
Running with "-e CONTAINER_PRESERVE_CONFIG=true", it generates the initial config files.
After start, modify the options.json by FVTT setup panel and the change preserves.
Pitch
FVTT docker container related.

Awesome.  Thank you!  I actually just coded it up and pushed it up to GitHub.  CI is building  and testing the image from the branch now.
The image is on Docker Hub now.
If you want to try it out you can pull  felddy/foundryvtt:improvement-write_config_once .

@hmqgg container 0.7.5+b has been released and addresses this issue:
https://github.com/felddy/foundryvtt-docker/releases/tag/v0.7.5%2Bb
Please let me know if this feature is working for you as request.


error code 429

hello, when i start earnapp with the command:
docker exec -ti picash earnapp start
i have this error message:
✔ IP detected
⠴ Registering Device...Error: Request failed with status code 429
at createError (/snapshot/svc/earnapp_cli/earnapp/node_modules/axios/lib/core/createError.js:16:15)
at settle (/snapshot/svc/earnapp_cli/earnapp/node_modules/axios/lib/core/settle.js:17:12)
at IncomingMessage.handleStreamEnd (/snapshot/svc/earnapp_cli/earnapp/node_modules/axios/lib/adapters/http.js:293:11)

429 is a rate limiting error code, with the container already running earnapp should be running in the background

It's OK now. Thanks

Please feel free to re-open this ticket if it happens again


Replaced CHAOSS Handbook Old Links with The New Link Signed-off-by: V…

…ictoria Udofort<EMAIL_ADDRESS>Signed-off-by: sloaneee<EMAIL_ADDRESS>This PR...
Changes

Screenshots
(prefer animated gif)
Checklist

[ ] tested locally
[ ] added new dependencies
[ ] updated the docs
[ ] added a test

Fixes #

Looks good @sloaneee. However, I've just noticed that some of the old links were to specific chapters of the handbook, so I'll need you to make some changes. I apologise for this oversight. Kindly implement the following changes:

The correct link here is: https://chaoss.community/kbtopic/working-groups/
You clicked *Develop Metrics* \n There are 5 Working Groups that develop metrics based on different aspects of open source community health: Risk, Value, Evolution, DEI, and Common.  More information about each of these groups can be found here: <https://chaoss.community/kb-chaoss-community/> and the metrics are developed during our Working Group meetings.

The correct link here is: https://chaoss.community/kb/development-contribution/
You clicked *Contribute or Review code*\n  You are welcome to contribute. Please see this documentation: https://chaoss.community/kb-chaoss-community/.

The correct link here is: https://chaoss.community/kb/documentation-contributions/
You clicked *Write or Edit Documentation*\n  Please see this documentation: https://chaoss.community/kb-chaoss-community/.

The correct link here is: https://chaoss.community/kbtopic/working-groups/
You clicked *Implement Metrics in my Project*\n  We encourage you to join one of our Working Groups for specific questions about implementing your metrics. You can read more about them here: https://chaoss.community/kb-chaoss-community/.

PS: Don't forget to sign off your commit. 😀
Thank you for contributing!

Closing this duplicate PR


[Bug]: ITMS-91061: Missing privacy manifest

Platform
macOS
Plugin
connectivity_plus
Version
6.1.0
Flutter SDK
3.24.5
Steps to reproduce
I distributed macOS to the App Store. However, I received the following response to the Apple review email:
ITMS-91061: Missing privacy manifest - Your app includes “Contents/Frameworks/connectivity_plus.framework/Versions/A/connectivity_plus”, which includes connectivity_plus, an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements.
Code Sample
No response
Logs
...
[+1527 ms] Caching compiled dill
[ +131 ms] Connecting to service protocol: http://<IP_ADDRESS>:52...
[ +117 ms] Launching a Dart Developer Service (DDS) instance at http://<IP_ADDRESS>:0, connecting to VM service at http://<IP_ADDRESS>:52...
[  +44 ms] DDS is listening at http://<IP_ADDRESS>:52...
[  +77 ms] Successfully connected to service protocol: http://<IP_ADDRESS>:5...
[  +22 ms] DevFS: Creating new filesystem on the device (null)
[  +14 ms] DevFS: Created new filesystem on the device (file:///private/var/mobile/Containers/Data.......
[   +1 ms] Updating assets
[ +680 ms] Manifest contained wildcard assets. Inserting missing file into build graph to force rerun. for more information see #56466.
[   +5 ms] Syncing files to device ip14...
[   +2 ms] Compiling dart to kernel with 0 updated files
[        ] Processing bundle.
[        ] <- recompile package:pp/main.dart 7...
[        ] <- 7...
[   +2 ms] Bundle processing done.
[ +153 ms] Updating files.
[        ] Pending asset builds completed. Writing dirty entries.
[        ] DevFS: Sync finished
[        ] Syncing files to device ip14... (completed in 173ms)
[        ] Synced 0.0MB.
[        ] <- accept
[   +3 ms] Connected to _flutterView/0x1...
[   +1 ms] Flutter run key commands.
[        ] r Hot reload. 🔥🔥🔥
[        ] R Hot restart.
[        ] h List all available interactive commands.
[        ] d Detach (terminate "flutter run" but leave application running).
[        ] c Clear the screen
[        ] q Quit (terminate the application on the device).
[        ] A Dart VM Service on ip14 is available at: http://<IP_ADDRESS>:52...
[        ] The Flutter DevTools debugger and profiler on ip14 is available at: http://<IP_ADDRESS>:91...

Flutter Doctor
❯ flutter doctor -v
[✓] Flutter (Channel stable, 3.24.5, on macOS 14.5 23F79 darwin-arm64, locale ko-KR)
    • Flutter version 3.24.5 on channel stable at /Users/me/fvm/versions/stable
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision dec2ee5c1f (4주 전), 2024-11-13 11:13:06 -0800
    • Engine revision a18df97ca5
    • Dart version 3.5.4
    • DevTools version 2.37.3

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/me/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /Users/me/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.11+0-17.0.11b1207.24-11852314)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 16.1)
    • Xcode at /Applications/Xcode16.1.app/Contents/Developer
    • Build 16B40
    • CocoaPods version 1.16.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2024.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.11+0-17.0.11b1207.24-11852314)

[✓] IntelliJ IDEA Ultimate Edition (version 2024.3.1)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 83.0.4
    • Dart plugin version 243.23177

[✓] VS Code (version 1.95.3)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (6 available)
    • macOS (desktop)                 • macos                     • darwin-arm64   • macOS 14.5 23F79 darwin-arm64
    • Mac Designed for iPad (desktop) • mac-designed-for-ipad     • darwin         • macOS 14.5 23F79 darwin-arm64
    • Chrome (web)                    • chrome                    • web-javascript • Google Chrome 131.0.6778.109

[✓] Network resources
    • All expected network resources are available.

• No issues found!

Checklist before submitting a bug

[X] I searched issues in this repository and couldn't find such bug/problem
[X] I Google'd a solution and I couldn't find it
[X] I searched on StackOverflow for a solution and I couldn't find it
[X] I read the README.md file of the plugin
[X] I'm using the latest version of the plugin
[X] All dependencies are up to date with flutter pub upgrade
[x] I did a flutter clean
[X] I tried running the example project

We have the manifest added for quite some time and even had a fix recently specifically for MacOS.
Please show your pubspec yaml and lock file content to be sure that you really use the latest version.

pubspec.yaml
dependencies:
  flutter:
    sdk: flutter

  cupertino_icons: ^1.0.8
  ...
  connectivity_plus: ^6.1.0
  ...

pubspec.lock
packages:
  ...
  connectivity_plus:
    dependency: "direct main"
    description:
      name: connectivity_plus
      sha256: "876849631b0c7dc20f8b471a2a03142841b482438e3b707955464f5ffca3e4c3"
      url: "https://pub.dev"
    source: hosted
    version: "6.1.0"
  connectivity_plus_platform_interface:
    dependency: transitive
    description:
      name: connectivity_plus_platform_interface
      sha256: "42657c1715d48b167930d5f34d00222ac100475f73d10162ddf43e714932f204"
      url: "https://pub.dev"
    source: hosted
    version: "2.0.1"
  ...

I think I know what the issue may be, the line of the privacy info refers only to ios:
 s.ios.resource_bundles = {'connectivity_plus_privacy' => ['connectivity_plus/Sources/connectivity_plus/PrivacyInfo.xcprivacy']}

should be duplicated and be as well:
 s.ios.resource_bundles = {'connectivity_plus_privacy' => ['connectivity_plus/Sources/connectivity_plus/PrivacyInfo.xcprivacy']}
 s.osx.resource_bundles = {'connectivity_plus_privacy' => ['connectivity_plus/Sources/connectivity_plus/PrivacyInfo.xcprivacy']}

or remove the ios part:
 s.resource_bundles = {'connectivity_plus_privacy' => ['connectivity_plus/Sources/connectivity_plus/PrivacyInfo.xcprivacy']}

I will prepare a PR


Upgrade to trio channels (fixes #41)

Upgrade to Trio 0.9 and use the official channels API. Remove
the prototype channels code that was checked into this repo.
Copy the new, channel-based MemoryListener from trio into our
test suite.
The only surprise here is that closing a channel is now async,
so this changes _close_web_socket and _abort_web_socket from
sync to async functions.

Pull Request Test Coverage Report for Build 50

12 of 14 (85.71%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+8.06%) to 91.622%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

trio_websocket/init.py
12
14
85.71%

Totals

Change from base Build 48:
8.06%

Covered Lines:
339

Relevant Lines:
370

💛  - Coveralls

Pull Request Test Coverage Report for Build 50

12 of 14 (85.71%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+8.06%) to 91.622%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

trio_websocket/init.py
12
14
85.71%

Totals

Change from base Build 48:
8.06%

Covered Lines:
339

Relevant Lines:
370

💛  - Coveralls


Visual State for Keyboard Switches

📝 Provide a description of the new feature
What is the expected behavior of the proposed feature?  What is the scenario this would be used?
It would be nice to have indicators, near the clock, for the keyboard switches (INS, Pause, Scroll, Num & Caps Locks), since there's no indicator for a few of them, depending on your hardware (and no indicator at all for INS or Pause on any machine I know of, before we had difference in cursor types between INS/Overwrite modes).

If you'd like to see this feature implemented, add a 👍 reaction to this post.

This would be part of https://github.com/microsoft/PowerToys/issues/981


Uncaught exception when loading user store configuration blocks majority of tenant operations

Describe the issue:
It seems there's no try-catch statement when attempting to load a given user store configuration file which can break tenant-aware operations such as authentication. This issue was already fixed for WSO2 IS 5.11.0 and above [1], but we need to backport this to 5.10.0 [2] as it's affecting a customer.
How to reproduce:

Create a new database and apply the needed scripts for a secondary user store.
Create a new tenant.
Using the new tenant's management console, add the new secondary user store.
Encode the new tenant's admin username and password in Base64 to use in further requests.
Use GET t/{New_Tenant_Domain}/api/server/v1/userstores to get the userstore ID.
Use the ID on GET t/{New_Tenant_Domain}/api/server/v1/userstores/{UserStore_Domain_ID} to get full user store JSON data.
Keep only the required fields (typeId, name, description, and properties), and change typeId to something invalid. Example: SW52YWxpZA== which is Invalid in Base64.
Update the userstore with this faulty data on PUT t/{New_Tenant_Domain}/api/server/v1/userstores/{UserStore_Domain_ID}.
Attempt to use GET t/{New_Tenant_Domain}/api/server/v1/userstores/{UserStore_Domain_ID} to get userstore information again.
See NullPointerException in wso2carbon.log (Requires DEBUG logs on user.core and identity.core)

Expected behavior:
I'm not sure if a typeId validation was originally expected, but on IS 5.11.0 and above, even though there's an invalid userstore configuration file, other tenant-aware behaviours are not affected by this and proceed normally as the exception is caught and suppressed. Things like authentication, user management, etc, shouldn't care about a faulty configuration.
Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: IS 5.10.0
Userstore: JDBC

[1] wso2/carbon-kernel#2807
[2] https://github.com/wso2/carbon-kernel/blob/v4.6.0/core/org.wso2.carbon.user.core/src/main/java/org/wso2/carbon/user/core/tenant/JDBCTenantManager.java#L779C17-L788C18

Steps to Verify:

Create a new database and apply the needed scripts for a secondary user store.
Create a new tenant.
Using the new tenant's management console, add the new secondary user store.
Encode the new tenant's admin username and password in Base64 to use in further requests.
Use GET t/{New_Tenant_Domain}/api/server/v1/userstores to get the userstore ID.
Use the ID on GET t/{New_Tenant_Domain}/api/server/v1/userstores/{UserStore_Domain_ID} to get full user store JSON data.
Keep only the required fields (typeId, name, description, and properties), and change typeId to something invalid. Example: SW52YWxpZA== which is Invalid in Base64.
Update the userstore with this faulty data on PUT t/{New_Tenant_Domain}/api/server/v1/userstores/{UserStore_Domain_ID}.
Attempt to use GET t/{New_Tenant_Domain}/api/server/v1/userstores/{UserStore_Domain_ID} to get userstore information again.
See NullPointerException in wso2carbon.log (Requires DEBUG logs on user.core and identity.core)
Try to log in to this tenant with admin credentials and should be able to login and access the tenant resources.
Try get the users of the tenant using scim2/Users api and should be able to retrieve. (ex: https://localhost:9443/t/{New_Tenant_Domain}/scim2/Users)

Try get the applications  of the tenant using scim2/Users api and should be able to retrieve. (ex: https://localhost:9443/t/{New_Tenant_Domain}/api/server/v1/applications)

Closing since this was fixed in master branch and and in the reported product version.

Fix : https://github.com/wso2/carbon-kernel/pull/2807

Closing since this was fixed in master branch and and in the reported product version.

Fix : https://github.com/wso2/carbon-kernel/pull/2807


feat: Add toString, equals and hashCode to public domain objects

Along with addressing #134, this PR aims to add convenience when debugging API responses and using the deserialised objects in collections, by implementing the equals and hashCode methods. The toString is implemented based on the class name and serialised JSON value. A reflective approach is taken to all these methods, using a common base object for JSON payloads in the form of com.vonage.client.JsonableBaseObject, which is implemented throughout the entire classs hierarchy / object graph for all JSON responses, and even some requests.

Codecov Report

Merging #508 (2a5b173) into main (a50c7bb) will increase coverage by 0.76%.
The diff coverage is 100.00%.

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #508      +/-   ##
============================================
+ Coverage     94.26%   95.02%   +0.76%
+ Complexity     2892     2876      -16
============================================
  Files           426      426
  Lines          6919     6838      -81
  Branches        449      400      -49
============================================
- Hits           6522     6498      -24
  Misses          204      204
+ Partials        193      136      -57

Files
Coverage Δ

...ain/java/com/vonage/client/JsonableBaseObject.java
100.00% <100.00%> (ø)

...ava/com/vonage/client/account/BalanceResponse.java
100.00% <ø> (ø)

...c/main/java/com/vonage/client/account/Country.java
100.00% <100.00%> (ø)

...com/vonage/client/account/CreateSecretRequest.java
100.00% <ø> (ø)

...com/vonage/client/account/FullPricingResponse.java
100.00% <100.00%> (ø)

...com/vonage/client/account/ListSecretsResponse.java
75.00% <100.00%> (ø)

...c/main/java/com/vonage/client/account/Network.java
100.00% <100.00%> (ø)

...m/vonage/client/account/PrefixPricingResponse.java
100.00% <100.00%> (ø)

...ava/com/vonage/client/account/PricingResponse.java
100.00% <100.00%> (ø)

...java/com/vonage/client/account/SecretResponse.java
100.00% <100.00%> (ø)

... and 129 more


support ligand structure based bias docking

support ligand structure based bias docking

The README is edited according to suggestions.


SpikeGLX: add Ultra and NP-Opto types

Fixes #1451
also adding Ultra-beta variant (1121) ant NP-Opto (1300). All these models are based on NP1.0 technology
@CodyCBakerPhD

This looks fine to me. Are there any test files that could help us double check that adding just there works (other than seeing that it seemed to work in the issue)?

I don't have any, but it should be fine :)

Test data uploaded here: https://gin.g-node.org/NeuralEnsemble/ephy_testing_data/pulls/129
@zm711 could you check (and merge) the GIN PR?

Merged :) and just reran tests.


Do you have plan to support native (or without transpiling) TypeScript in ChakraCore?

+1It would be great

+1
We need full native TypeScript supported dev platform alter node.

There are no plans. You can read about our plans on the roadmap. Thanks!


IDL/winmd d.ts generation

Would be nice for an officially supported solution that matches WinRT's JavaScript transformation.

just stumbled on this issue. I wouldn't say "Too Complex", maybe the Out of Scope label is fitting.
The most complex thing about this is the in-ability for a project like this to sit as long as it has and keep working with how the tooling keeps breaking things...
https://github.com/ToTypeScriptD/ToTypeScriptD/
Any help getting it rebooted with the latest versions of things since MSFT keeps moving forward and breaking the tooling would be appreciated.
It's totally do-able - it worked great back then, I think with some ❤ it could work again...


MF-363 - Add compiled .proto files

This pull requests resolves #363.
This PR adds compiled .proto files to the repo so they are present when mainflux is used as a library (fetched by go get).
Signed-off-by: Sava Radoš<EMAIL_ADDRESS>

Codecov Report

Merging #364 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #364   +/-   ##
=======================================
  Coverage   89.17%   89.17%
=======================================
  Files          43       43
  Lines        1469     1469
=======================================
  Hits         1310     1310
  Misses        110      110
  Partials       49       49

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 6461761...62458f1. Read the comment docs.

@drasko It's still needed for development.


Add election participation count query

add the first box subchain query! 🎉
shows the total number of participants on the current election
if the query fails we simply don't show the component (it means that we don't depend on the box -- I think we should adopt this pattern whenever possible, so other eden communities are not forced to spin up a box with history... I also understand that this might be a deal breaker for some functionalities that depends on nice massaged data from history... hence why "whenever possible" -- thoughts?)
it standardizes the useQuery from ReactSubchain with the same interface as the react-query, then we have a nice object to control when it's loading, has an error or has the query data result in fact.

Approach looks good

if the query fails we simply don't show the component (it means that we don't depend on the box -- I think we should adopt this pattern whenever possible, so other eden communities are not forced to spin up a box with history... I also understand that this might be a deal breaker for some functionalities that depends on nice massaged data from history... hence why "whenever possible" -- thoughts?)

I'm pretty sure we're going all-in on box. At least, the way I've been envisioning it, all RPC queries will be replaced with references to browser-side derived state in the not-too-distant future.
Other Eden communities will have a few options:

spin up their own box (totally do-able)
use a business-in-a-box provider
rely on our box until BIAB providers are available

In this case, I think it's totally fine that we simply show nothing on error. But we'll want fallback error UI in the future as we lean more and more on box.


Move the repository to the typed-mxgraph organization

@hungtcs hi, what do you think about moving this example repository directly to the https://github.com/typed-mxgraph GitHub organization?
This will provide an alternative vanilla Typescript example to the already existing WebPack example: https://github.com/typed-mxgraph/typed-mxgraph-demo
In the meantime, we could also recreate framework related projects (Angular, React, ...) as we had for the old https://github.com/hungtcs/mxgraph-type-definitions:

https://github.com/hungtcs/react-with-mxgraph
https://github.com/hungtcs/angular-with-mxgraph

Hi, @tbouffard, this is a good idea, I would be very happy to receive this repository, and I will create some starter projects about angular and react later.

Hi, @tbouffard, this is a good idea, I would be very happy to receive this repository, and I will create some starter projects about angular and react later.

Ok nice!
I can change the repository name which is very long but at least it describes what the repository does. Do you have any wish on that topic? we can rename it later as well.
My only request would be to keep an 'Admin' role on this repository to be able to maintain everything on it. This will avoid adding more work on your side too.
About the react and angular starters, I could help on this topic (at least review and test) but I have limited knowledges on these topics as I don't use them on daily basis.

Ok nice!
I can change the repository name which is very long but at least it describes what the repository does. Do you have any wish on that topic? we can rename it later as well.
My only request would be to keep an 'Admin' role on this repository to be able to maintain everything on it. This will avoid adding more work on your side too.
About the react and angular starters, I could help on this topic (at least review and test) but I have limited knowledges on these topics as I don't use them on daily basis.

Of course @tbouffard, I have changed the default member repository permissions of typed-mxgraph organization to write, now you should have permissions for all repositories, if not, please contact me to check.
I think there is no harm in having a long name, we can define the naming convention of the sample project, my current thinking is:
typed-mxgraph-example-[describe]

typed-mxgraph-example-react
typed-mxgraph-example-angular
typed-mxgraph-example-vanilla-typescript
typed-mxgraph-example-bundled-with-rollup
typed-mxgraph-example-bundled-with-webpack
and more...

What do you think about this naming conventions, if possible, I will rename typed-mxgraph-demo to typed-mxgraph-example-bundled-with-webpack, and this repository will would be typed-mxgraph-example-bundled-with-rollup.

Of course @tbouffard, I have changed the default member repository permissions of typed-mxgraph organization to write, now you should have permissions for all repositories, if not, please contact me to check.
I think there is no harm in having a long name, we can define the naming convention of the sample project, my current thinking is:
typed-mxgraph-example-[describe]

typed-mxgraph-example-react
typed-mxgraph-example-angular
typed-mxgraph-example-vanilla-typescript
typed-mxgraph-example-bundled-with-rollup
typed-mxgraph-example-bundled-with-webpack
and more...

What do you think about this naming conventions, if possible, I will rename typed-mxgraph-demo to typed-mxgraph-example-bundled-with-webpack, and this repository will would be typed-mxgraph-example-bundled-with-rollup.

👍🏿 for your naming convention and ok to rename this repository into typed-mxgraph-example-bundled-with-rollup
I will trigger the transfer ownership to the typed-mxgraph organization soon.

👍🏿 for your naming convention and ok to rename this repository into typed-mxgraph-example-bundled-with-rollup
I will trigger the transfer ownership to the typed-mxgraph organization soon.

Repository has been renamed.
Transfer is in progress.

Repository has been renamed.
Transfer is in progress.

Transfer done

Transfer done

@tbouffard I have renameed typed-mxgraph-demo to typed-mxgraph-example-bundled-with-webpack, and update readme.

@tbouffard I have renameed typed-mxgraph-demo to typed-mxgraph-example-bundled-with-webpack, and update readme.


Fb dataproc serverless

Add a feature to use dataproc job serverless to sample ingestion and that has free access at relacional database

add example with sakila and remove example of signup


make deb fails on arm64

Output of docker version:
Client:
 Version:      1.10.3
 API version:  1.22
 Go version:   go1.6.1
 Git commit:   20f81dd
 Built:        Wed, 20 Apr 2016 14:19:16 -0700
 OS/Arch:      linux/arm64

Server:
 Version:      1.10.3
 API version:  1.22
 Go version:   go1.6.1
 Git commit:   20f81dd
 Built:        Wed, 20 Apr 2016 14:19:16 -0700
 OS/Arch:      linux/arm64

Output of docker info:
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 42
Server Version: 1.10.3
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 31
 Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
 Volume: local
 Network: bridge null host
Kernel Version: 3.10.101-0-pine64-longsleep
Operating System: Ubuntu 16.04 LTS
OSType: linux
Architecture: aarch64
CPUs: 4
Total Memory: 1.943 GiB
Name: pine64
ID: NANA:36TS:63E4:JM3T:QQEE:CTEP:F324:WJHS:LXOL:7GNL:WNEN:JKKU

Additional environment details (AWS, VirtualBox, physical, etc.):
Physical Pine64 with ubuntu 16.4 for arm64
Steps to reproduce the issue:

download git docker source
execute make deb

Describe the results you received:
---> Making bundle: dynbinary (in bundles/1.12.0-rc3/dynbinary)
Building: bundles/1.12.0-rc3/dynbinary-client/docker-1.12.0-rc3
github.com/miekg/pkcs11
vendor/src/github.com/miekg/pkcs11/pkcs11.go:26:18: fatal error: ltdl.h: No such file or directory
compilation terminated.
Makefile:86: recipe for target 'deb' failed
make: *** [deb] Error 1
Describe the results you expected:
deb docker package for installation
Additional information you deem important (e.g. issue happens only occasionally):
I allready installed libltdl-dev package and even tried to copy the file locally to pkcs11.go dir

We currently don't support aarch64, so this may be expected.

It's a shame. I hope you include it shortly. Do you know if there is any plan on this allready??
In this particular issue it's curious cause seem that probably is happening on other pkcs11 Linux builds  https://github.com/miekg/pkcs11/issues/24
If I can reproduce on i386 or amd64 I'll try to reopen
Supose the only option left in this case & moment is to do my own packages from binaries

It also fails with this on make test on aarch64 so I will reopen this as there should be an arm64 CI soon...

Can you test with https://github.com/docker/docker/pull/24412 applied?

I just tested, took a while but it worked perfectly!! Thanks, I didn't realise that the dependencies where needed on Dockerfile, I was stupidly trying to put them on the host.
Now it stacks on apparmor stuff (I append the error and I'll try to explore a bit) but seems to me that your pull request solves ltdl.h issue
---> Making bundle: .detect-daemon-osarch (in bundles/1.12.0-dev/build-deb)
find: `contrib/builder/deb/aarch64/*/': No such file or directory
---> Making bundle: .integration-daemon-stop (in bundles/1.12.0-dev/build-deb)
+++++ cat bundles/1.12.0-dev/build-deb/docker.pid
++++ kill 5063
++++ /etc/init.d/apparmor stop
 * Clearing AppArmor profiles cache
   ...done.
All profile caches have been cleared, but no profiles have been unloaded.
Unloading profiles will leave already running processes permanently
unconfined, which can lead to unexpected situations.

To set a process to complain mode, use the command line tool
'aa-complain'. To really tear down all profiles, run the init script
with the 'teardown' option."
Makefile:86: recipe for target 'deb' failed
make: *** [deb] Error 1

I've seen that the problem is that contrib/builder/deb/aarch64/ is needed, the only problem is that golang tgz is not yet avaliable for this arch, but I thing I can use https://github.com/hypriot/golang-armbuilds for this purpose. On the other hand I beleive that test errors seems that some kind of arch limitation has been reached.
Anyway, thabks again for the step further!!

Yes the lack of official arm64 Go binaries is annoying, it is also worked
around in the main build. I don't currently have an aarch64 machine with
apparmor so have not tested that yet.
On 8 Jul 2016 7:56 a.m., "Albert Domenech"<EMAIL_ADDRESS>wrote:

I've seen that the problem is that contrib/builder/deb/aarch64/ is needed,
the only problem is that golang tgz is not yet avaliable for this arch, but
I thing I can use https://github.com/hypriot/golang-armbuilds for this
purpose. On the other hand I beleive that test errors seems that some kind
of arch limitation has been reached.
Anyway, thabks again for the step further!!
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker/issues/24380#issuecomment-231289022,
or mute the thread
https://github.com/notifications/unsubscribe/AAdcPFtGgnG6imqPzVgshrXpDAE503I2ks5qTfShgaJpZM4JGVE3
.

@justincormack I still get an error like this building on AARCH64 with docker/docker master branch:
--- FAIL: TestMountMoreThan42Layers (5.20s)

Client:
 Version:      1.12.1
 API version:  1.24
 Go version:   go1.6.2
 Git commit:   23cf638
 Built:        Tue, 27 Sep 2016 12:25:38 +1300
 OS/Arch:      linux/arm64

Server:
 Version:      1.12.1
 API version:  1.24
 Go version:   go1.6.2
 Git commit:   23cf638
 Built:        Tue, 27 Sep 2016 12:25:38 +1300
 OS/Arch:      linux/arm64

# docker info
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 34
Server Version: 1.12.1
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 28
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: host bridge overlay null
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: apparmor
Kernel Version: 4.4.0-38-generic
Operating System: Ubuntu 16.04.1 LTS
OSType: linux
Architecture: aarch64
CPUs: 96
Total Memory: 125.9 GiB


Catastrophic failure on executing NANOPB_GENERATE_CPP() CMake function on ubuntu host machine with system install of nanopb

So, I incorporated nanopb into a CMake project as an in-source tree submodule, and used NANOPB_GENERATE_CPP() to compile my .proto files.  All worked as expected.
Then a colleague cloned my project and attempted to build it on an ubuntu host with a system package manager install of nanopb.
The
find_path(NANOPB_GENERATOR_SOURCE_DIR
    NAMES nanopb_generator.py
    DOC "nanopb generator source"
    PATHS
    ${NANOPB_SRC_ROOT_FOLDER}/generator
    NO_CMAKE_FIND_ROOT_PATH
)

search picks up "nanopb_generator.py" from "/usr/bin", then the
  add_custom_command(
      OUTPUT ${NANOPB_GENERATOR_EXECUTABLE} ${GENERATOR_CORE_SRC}
      COMMAND ${CMAKE_COMMAND} -E copy_directory
      ARGS ${NANOPB_GENERATOR_SOURCE_DIR} ${GENERATOR_PATH}
      VERBATIM)

statement within NANOPB_GENERATE_CPP() proceeds to copy the entire contents of "/usr/bin" into the build directory.
Adding a  NO_DEFAULT_PATH modifier to the find_path() call stopped the problem, but it sorta renders the entire find_path() call pointless..

Related to more general problems described in Issue 481

As a short term stand-alone fix, changing all the find_xxx() function calls in "FindNanopb.cmake" to specify paths with HINTS directives (rather than PATHS) ensures that the suggested paths are searched first, such that the local versions of the desired items are found, even if there is a system install present

The copying of the files to build directory is annoying and mostly unnecessary anyway.
It got added to the CMake rules because someone got annoyed about the autogenerated nanopb_pb2.py in source directory.
In the ideal case the nanopb_pb2.py wouldn't need to be saved to filesystem at all.
There was work started on this in #601, and the dev_dynamic_nanopb_pb2 branch seems to work quite ok, it would just need rebasing & more testing on different platforms.

Version 0.4.7 adds environment variable NANOPB_PB2_TEMP_DIR. Setting it to 1 will store nanopb_pb2.py to a system-wide temp folder, or it can be set to a path.
Using this should avoid need of copying the generator folder to build folder, so that FindNanopb.cmake could be simplified.

I'm not sure if this is still an issue in 0.4.8, but it seems the interoperability of FindNanopb.cmake and the CMakeLists.txt installation has not been designed or tested at all. There is a separate issue #911 about that.

I'm closing this off as I don't have a way to reproduce the problem and I think it may have been fixed by the numerous CMake build rule changes.


”Ilovița”, ”Bahna”, ”Moisești” are listed in the drop-down menu

Description:
When user writes ”Ilovița”, ”Bahna”, ”Moisești” the locations appear in the drop-down menu next to the comune and the county which is a part according to the law.
Precondition:
The website is up an running.

Step 1
Write in the search bar "Ilovița"

Expected results
The location appears in the drop-down menu as "Sat Ilovița, MEHEDINȚI (Ilovița)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Bahna"

Expected results
The location appears in the drop-down menu as "Sat Bahna, MEHEDINȚI (Ilovița)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Write in the search bar "Moisești"

Expected results
The location appears in the drop-down menu as "Sat Moisești, MEHEDINȚI (Ilovița)".


[10.x] Create a method to convert base64 file to a file in the Filesystem class

Description
I added a method in the file facade to convert a base64file to a file data that can be saved in a file. I also create a helper function to check if the string is a valid base64 file and it throws the following exception if it is not a valid base64 file.
Use case
It is a simple out of the box method that allows users convert their base64 images directly into a file data that they can save into a file. I have had to create methods in my laravel applications for handling this so i thought to create a method that will make this seamless and easy.
Additions:
I initially made this compatible for only base64 images but made a new pull request for other file types.

@shaedrich got it!

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


Create Blog “2024-03-10-gotohellwith-gordan-ramsay”

Automatically generated by Netlify CMS

👷 Deploy Preview for stunning-toffee-85d370 processing.

Name
Link

🔨 Latest commit
15451615c6e6002b5bffe27b2dbcae82d2e1c617

🔍 Latest deploy log
https://app.netlify.com/sites/stunning-toffee-85d370/deploys/65ecbd5f6e539900081c80bb


Ui: Add colors to tag labels

Part of #784. Rebased, and changed the design of determining the colours of the tag.
Propsed commit message:
All tags in the address book are displayed with the same color.

It is hard to visually look for contacts sharing the same tags.

Let's add different colors for different tags to make the
differentiation of tags clearer.

Note: For demo purpose, don't merge this to master!

Purely just rebasing, technically should not have any change in logic.


Failed on Compilation

Hi
I am getting this:
   @ line 1, column 1.
     import org.jetbrains.changelog.date
     ^```

I am using the Intellij EAP with the latest version of this plugin in groovy gradle script.

I can supply more info if needed.

Thanks

@Jonatha1983 The full stack trace and your build.gradle file's content would be helpful here.

I ll close it - I can't reproduce it. Sorry tnx.


Push docker images in CD style

removed the line that pushes for any commit
changed Docker tag for pushes from the master branch. The pushed
Docker tag now contains tag of form: "master-<8 char commit SHA>"
the tag pusing remains the same.

Related to https://github.com/microservices-demo/microservices-demo/issues/553


Prevent progress indicator from scrubbing

Hello, is there a way to prevent the user to manually slide the progress indicator?
I want to show it, but not to change it.
Thanks.

I have the same problem. Have you solved it？
iOS 12.0+


The constructor will be repeated when the same tab is selected consecutively

Ionic version:  (check one with "x")
[ ] 1.x
[ ] 2.x
[X] 3.x
I'm submitting a ...  (check one with "x")
[X] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
The constructor will be repeated when the same tab is selected consecutively.
Expected behavior:
Tabs's page's constructor only called once.
Steps to reproduce:

ionic start ionic2-tabs tabs --v2
add console log in constructor function
select the same tab consecutively

Related code:
ionic start ionic2-tabs tabs --v2

Other information:

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
Cordova CLI: 6.5.0
Ionic Framework Version: 3.0.1
Ionic CLI Version: 2.2.2
Ionic App Lib Version: 2.2.1
Ionic App Scripts Version: 1.3.0
ios-deploy version: 1.9.0
ios-sim version: 5.0.10
OS: macOS Sierra
Node Version: v6.9.1
Xcode version: Xcode 8.3.2 Build version 8E2002

I have the same issue...

Duplicate of #11015

it is probably creating new instances of the same page, calling the constructor of the same instance several times is not possible

Hello, all! This has actually already been fixed by this PR https://github.com/driftyco/ionic/pull/11084 that I merged last week and will, therefore, be in the next release. Thanks for using Ionic!


Java 16 Soft Compatibility: use Java SE libraries & stop module force-opening and too much reflecting

This is what the force-opening had done:
jvmArgsPrepend = ['--add-opens java.base/java.util.jar=ALL-UNNAMED --add-exports java.base/sun.security.util=ALL-UNNAMED -Dsecurejarhandler.throwOnMissingModule=false']

Let's also have a look at module-info.java:

import cpw.mods.cl.ModularURLHandler;
import cpw.mods.cl.UnionURLStreamHandler;
import cpw.mods.niofs.union.UnionFileSystemProvider;

module cpw.mods.securejarhandler {
    exports cpw.mods.jarhandling;
    exports cpw.mods.jarhandling.impl;
    exports cpw.mods.cl;
    requires jdk.unsupported;  // This is not a part of Java SE standard libraries. Most of the OpenJDK JREs would abandon this.
    requires org.objectweb.asm;
    requires java.base;
    provides java.nio.file.spi.FileSystemProvider with UnionFileSystemProvider;
    uses cpw.mods.cl.ModularURLHandler.IURLProvider;
    provides ModularURLHandler.IURLProvider with UnionURLStreamHandler;
}

Also see cpw.mods.jarhandling.impl.Jar:
public class Jar implements SecureJar {
    private static final CodeSigner[] EMPTY_CODESIGNERS = new CodeSigner[0];
    private static final UnionFileSystemProvider UFSP = (UnionFileSystemProvider) FileSystemProvider.installedProviders().stream().filter(fsp->fsp.getScheme().equals("union")).findFirst().orElseThrow(()->new IllegalStateException("Couldn't find UnionFileSystemProvider"));
    private final Manifest manifest;
    private final /*java.base/sun.security.util.*/ManifestEntryVerifier mev;  // non-exported class. We cannot guarantee its stability and whether it be moved by Oracle or OpenJDKs.

Also see cpw.mods.jarhandler.impl.SecureJarVerifier:
    static {
        /* ... */
        try {
            jarVerifier = JarInputStream.class.getDeclaredField("jv");
            sigFileSigners = jarVerifier.getType().getDeclaredField("sigFileSigners");
            existingSigners = jarVerifier.getType().getDeclaredField("verifiedSigners");
            parsingMeta = jarVerifier.getType().getDeclaredField("parsingMeta");
            anyToVerify = jarVerifier.getType().getDeclaredField("anyToVerify");
            jarVerifier.setAccessible(true);
            sigFileSigners.setAccessible(true);
            existingSigners.setAccessible(true);
            parsingMeta.setAccessible(true);
            anyToVerify.setAccessible(true);
        } catch (NoSuchFieldException e) {
            throw new IllegalStateException("Missing essential fields", e);
        }

Using reflect to handle the private methods in java.base/java.util.jar.JarInputStream is not so secure as constructing your own Jar Security API.

Something Nonsense Some advice
Although I'm a Fabric Modder, I am always keeping concerning the development of Minecraft Forge. Before Minecraft 1.17, Forge does not compat Java 9+ (for sun.security.util.* and other package accessibility changes) as well as OpenJ9 VM (?).
The release of Minecraft Forge 37.0 has started a new era of Minecraft modding cuz Forge has to compat the Java 9 Module System.
However I am very disappointed at the way handling the solution of the Java 9 issue. Of course JDK includes many things useful, some of them are for JDK inner use and some of them are even deprecated (i.e. `jdk.unsupported/sun.misc.*`). Is it good to expose the "unstable" clothes under the jacket of Java API? If it is good, I can even throw `org.objectweb.asm` away and use `jdk.internal.org.objectweb.asm` and kick `com.ibm.icu4j` off and invoke `jdk.internal.icu` to shrink my third-party libraries.
See? Using these unstable libraries are harmful to the stability of `securejarhandler` itself. Why don't you construct your own library based on jdk.unsupported, sun.security.util, JarVerifier or something like that. Although Fabric lacks of the functionality, it is stable, from Java 8 to Java 16, from Hotspot to OpenJ9, from Minecraft 1.14 to Minecraft 1.17. In many ways Minecraft Forge is more experienced than Fabric, and I believe Forge can improve its stability and make us mod players more free on playing.

Some issues on 1.16.x compatibility
In my opinion, using a Java-9-compatible patch to Minecraft Forge 36 (Minecraft 1.16.x) can benefit 1.16.x players who use Java 16  and hate Java 1.8.

Is it good to expose the "unstable" clothes under the jacket of Java API? If it is good, I can even throw org.objectweb.asm away and use jdk.internal.org.objectweb.asm and kick com.ibm.icu4j off and invoke jdk.internal.icu to shrink my third-party libraries. See?

You're just going off on a tangent/slippery slope argument there.
We are not 'exposing' anything. Java already 'exposes' it. We're just using it.
Us using something doesn't 'expose' it to modders any more then it already is.
Forge is stable just fine, you're really walking on thin ice with your advocation/fanboying over Fabric. You do not know what you're actually talking about in regards to the differences in the two projects. Here is your one and only warning. Stop it.
There are a lot of places that need to use reflection and other internals to do the things that need to be done. Yes it could be cleaned up and probably made to touch a smaller area. But we wernt really in the mood to flat out copy pasta large swafts of JDK code.
If you have actual actionable suggestions we'll entertain them. However, it's one of the many manpower vs priority things that exist in open/community projects such as this.

Sorry to reply late.

exports cpw.mods.cl;
__requires jdk.unsupported;__
requires org.objectweb.asm;

I have double-checked this dependency and found that using jdk.unsupported is just fine. The Unsafe API have to be used in many ways. Even LWJGL is using it. In this way, Forge is stable across JREs.

jvmArgsPrepend = ['--add-opens java.base/java.util.jar=ALL-UNNAMED --add-exports java.base/sun.security.util=ALL-UNNAMED -Dsecurejarhandler.throwOnMissingModule=false']

Using this is necessary in developing environment, of course. However, when securejarhandler is packed into a jar, maybe adding Add-Exports and Add-Opens to META-INF/MANIFEST.MF is a better solution so that MinecraftForge launcher meta JSONs can shrink these --add-opens & --add-exports JVM arguments.
Maybe you'll say this is useless, but if other developers use MinecraftForge/securejarhandler, they don't need to add these annoying args ever.

In my opinion, using a Java-9-compatible patch to Minecraft Forge 36 (Minecraft 1.16.x) can benefit 1.16.x players who use Java 16.

Maybe this is not a huge framework. I think the best solution is using Add-Exports and Add-Opens in MANIFEST.MF, and replace legacy securejarhandlers to the latest.

Good luck.

Manifest based exports/opens do not work properly with the module system (even tho the spec says it should) in our tests with both executable jars as well as normal module paths.

If you can provide some actual function tests we can work with I'd be willing to entertain it. However 1/2 the jres out there work one way and the other 1/2 work another. So it would have to be some framework where we can easily test.

Manifest-based add-opens and add-exports should be valid only when the java -jar command is used, and must be written in the main jar, so it is invalid to write it in securejarhandler.
However, it is most likely to write Add-Opens and Add-Exports in the 1.16.5 forge server launcher jar, so that you can start the forge 1.16.5 server with only java -jar forge.jar in Java 16 without having to add additional parameters.
This is the launcher jar that I added the corresponding Add-Opens and Add-Exports to MANIFEST.MF. Just extract and replace the installed forge server launcher jar. Used on your risk
forge-1.16.5-36.2.4-repack.jar.zip

@ZekerZhayard That tells us nothing new. We already know that the manifest functions with executable jars. That has absolutely nothing to do with what we are talking about.
As I said this system DOES NOT work with the module system.
You statement/example has nothing to do with 1.17, SJH, or anything going on right now.
Right now there are two tasks, and two tasks only:

Provide a way to get UnSafe without use of reflection/need for additional Opens.
Provide a implementation of verification of jar signatures and production of CodeSource values without the violation of OpenJDK's GPL license or the use of reflection.

Those are the main issues at this point.

This doesn't seem to be an issue that SJH can fix? It seems you're complaining about the fact that we use AddOpens? This is necessary because the minecraft launcher launches the game using classpath mode - there is no -jar we can rely on to get our AddOpens in that way. We do use it for the server as lex noted.
A standalone JarVerifier is a huge amount of development effort, and would be a maintenance nightmare. I looked into doing that and you end up having to implement all of the certificate code as well, because guess what, none of THAT is open either. Adding an opens and exports seems to be far more viable and is the "proper way to do it". Just go look at your favourite IDE running under J11 and tell me that "add opens is bad" mmmkay.


Support Docker 20.10

Current situation
Docker version 20.10 is not yet available (not even optional) for Flatcar, but would bring a bunch load of new features, see:
https://docs.docker.com/engine/release-notes/#20100
Impact
Missing out on new features, especially around using devices from within services.
Ideal future situation
I would propose to have Docker version 20.10 available as an optional torcx package, but still default to the more stable 19.03 for now.

Hi,
you can follow this guide to run a custom version through Ignition:
https://kinvolk.io/docs/flatcar-container-linux/latest/container-runtimes/use-a-custom-docker-or-containerd-version/
Maybe some adjustments are needed but the first thing to do is switching a newer version in the url: https://download.docker.com/linux/static/stable/x86_64/docker-19.03.14.tgz line.

Thanks for the information, but are there plans for Docker 20.10 availability in Flatcar?

There is ongoing work-in-progress PR on Docker 20.10 support in Flatcar https://github.com/kinvolk/coreos-overlay/pull/931

Docker 20.10 is in Flatcar v2969.0.0.


Flutter 2.8, color, and speed support

I've updated the dependencies to work with Flutter 2.8, Added color rendering to match what is output in your IDE, removed the ANSI color escape markings from the logs, and sped up the rendering speed by calling setState only when required.
I tested with 1000 logs in the buffer that the default is, and the logs render as expected

Consider merging this pull request, it contains many QoL updates you may find useful


Update the content of the try-it.md

Update the content of the try-it.md to be aligned with the current state of the metal3 project.

/cc fmuyassarov

/lgtm
/cc @hroyrh

/approve

Not sure what's the issue with the Prow that it doesn't automatically merge PRs on this repo. Not to block others meanwhile, I'm going to merge this myself.


[vb] Switch to a more active grammar for VB

VSCode Version: 1.7.2
OS Version: Windows 10 14393.577

Steps to Reproduce:

Open a modern VB.NET file, such as VBEditAndContinueAnalyzer
Observe that 'Imports', 'Namespace', 'Friend', 'Inherits', 'Protected', 'Override', and perhaps other keywords are not colorized, but simply appear as white text.

This same issue repros with the same grammar on:

TextMate editor for Mac
VS Code for Windows
Visual Studio 2017 RC

I am fairly certain that this is a TMLanguages issue, as doing a quick search through the grammar file, there is no pattern for matching these keywords.
I'd recommend either switching to an alternative grammar, such as Angry Ant's, or better yet, updating and contributing the corrected grammar file back to the TextMate Grammar.

@chrisdias got a PR accepted in https://github.com/textmate/asp.vb.net.tmbundle. I'm not opposed to switching to a better one, but it would be great to try that.

To keep the number of issues in our inbox on a manageable level, we're closing issues that have been on the backlog for a long time but haven't gained traction: We look at the number of votes the issue has received and the number of duplicates issues filed.
If you disagree and feel that this issue is crucial: We're happy to listen and to reconsider.
Maybe you want to give it a try yourself and provide the feature through an extension or a PR: We're happy to give advise and get you started.
Thanks for your understanding. Thanks for helping and happy coding!


2 column layout, gene rectangle colour change

https://github.com/tskit-dev/tsqc/assets/25925005/c4bd353d-d852-4639-a398-36bbfab0be40

Can't seem to figure out how to remove the bokeh toolbar on the far right. Another minor issue is that it doesn't se straightforward to centre the table title. Otherwise happy with this layout.

Looks great!


Chore remove unused lock on fragment mrg

Proposed changes
remove unused lock on fragment mrg
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


ReferenceError: window is not defined

first off:
kudos & chapeaux!
my problem:
I'm trying to integrate this into an existing nextjs-project (that's based on the solana-labs/dapp-scaffold)
and am weirdly getting a "ReferenceError: window is not defined" that I can't seem to find a fix for.
Do you have any idea or hint where this could be stemming from? I've been trying all day now to no avail.
ReferenceError: window is not defined     at /Users/.../node_modules/@google/model-viewer/dist/model-viewer-umd.js:572:20     at /Users/.../node_modules/@google/model-viewer/dist/model-viewer-umd.js:2:68     at Object.<anonymous> (/Users/.../node_modules/@google/model-viewer/dist/model-viewer-umd.js:5:2)     at Module._compile (node:internal/modules/cjs/loader:1097:14)     at Object.Module._extensions..js (node:internal/modules/cjs/loader:1149:10)     at Module.load (node:internal/modules/cjs/loader:975:32)     at Function.Module._load (node:internal/modules/cjs/loader:822:12)     at Module.require (node:internal/modules/cjs/loader:999:19)     at require (node:internal/modules/cjs/helpers:102:18)     at Object.<anonymous> (/Users/.../node_modules/@liqnft/candy-shop/dist/index.es.js:7:366) {   page: '/'

Hi @BloodyBee ,
You have to make sure of the 2 following things.

Wrapping pages/_app.ts with the CandyShopDataValidator (See example)
Using dynamic imports for the CandyShopDataValidator and other candy shop components. (Dynamic Import Example)

Hope that helps.

Hi @gonwi,
that does help massively indeed.
Thanks a lot!


Add vertical slider

Hi team, could you please add a vertical slider.
At that moment it could be only horizontal.

Could you please suggest that in Google's issue tracker, as this looks like generic component requirement.

@LAP2, isn't androidx.compose.foundation.VerticalScrollbar what you need?

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


phase curve plot func

Fixes #112.
This is a start at adding some plotting utility functions, e.g. making phase curve plots from adler objects. I have tried to write this such that a matplotlib figure object is returned by the function, this can either be displayed or manipulated further.
Review Checklist for Source Code Changes

[ ] Does pip install still work?
[ ] Have you written a unit test for any new functions?
[ ] Do all the units tests run successfully?
[ ] Does adler run successfully on a test set of input files/databases?
[ ] Have you used black on the files you have updated to confirm python programming style guide enforcement?

If this approach looks sensible I would like to add more plotting functions and improve the demo notebook notebooks/plotting_utilities.ipynb (and add unit tests of course)


Update year in header

Not sure if this is needed. But I saw some was some years behind.

@swift-ci please test

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test

c-syntax-nodes.h needs to match SwiftSyntaxCDataTypes.h in the main Swift repo. I’ll leave it up to you to either update the date in that repo as well or leave the copy right of that file in this repo as-is.

Updated in https://github.com/apple/swift/pull/41453

@swift-ci Please test

https://github.com/apple/swift/pull/41453
@swift-ci Please test


[BUG] Cuda 11.7 cannot start int4 model

Cuda 11.7 cannot start int4 model   help me!!!!

Hi @mayu123mayu feel free to share more details on this issue.


ENH: multi-gpu Random Forest [SPMD]

Description
This PR is enhancement for #949, #1175:

Adding spmd and spmd.ensemble module
multi-GPU SPMD interface for Random Forest Onedal4py implementation
Examples for RF spmd

Waiting #1059 #1064 and https://github.com/oneapi-src/oneDAL/pull/2156

Outdated. Implemented on #1214


A11y_SQL Azure Data Studio_Notebooks - Code cell_Screenreader : The +code and +text options are reading as links but they perform like buttons.

"Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier."
GitHubTags: #A11yMAS;#A11yTCS;#A11ySev2;#BM_SQLAzureDataStudio_Win32_Jun2021;#SQL Azure Data Studio;#Win10;#FTP;#DesktopApp;#WCAG4.1.2;#NVDA;#JAWS;#STP
Environment Details:
Application Name: SQL Azure Data Studio
Windows Version: Win10
Screen reader : JAWS, NVDA2020.2
Repro Steps:

Launch Azure Data Studio Insiders application.
Connect to server.
Press the context menu key on connection and click New Notebook
Click on cell and select code cell.
Run the screen reader and navigate to the "+code" and "+text" options.
Check the options by activating them by enter key , the options perform like button.

Actual:
Screen reader is announcing the "+Code" and "+text" options as link but they are performing their operations like buttons. The functionality is opening in the same window screen.
This issue is observed in both the screen readers JAWS and NVDA.
Expected:
The links should not be read as buttons as they are performing like buttons.
User Impact:
Screen reader only user will face difficulty to understand and differentiate the functionality of the control.

Verified this issue in the below environment.
App Name: Azure data studio Insider
Version: 1.42.0-insider (user setup)
Commit: 99a924dbcdce7bbaa0ab78b19f84e83035e54651
Date: 2023-02-08T06:58:10.882Z
VS Code: 1.67.0
Electron: 19.1.8
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22623
GitHub Tag:#Closed;


Added comment to docs regarding ToTensor transform

Description
Added note in documentation regarding order of transforms.
User mentioned this in https://github.com/apache/incubator-mxnet/issues/10906.
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[x] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes): tiny change!
[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage: N/A
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[x] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[x] Added comment to docs

CI failure seems unrelated (ARMv7 build failure).
@thomelane can you please re-trigger the CI so we have a clean build?
Looping in @piiswrong and @zhreshold for review.

@lupesko just re-triggered, thanks for heads up!

@piiswrong @zhreshold @sandeep-krishnamurthy Could you please take a look at this PR?
@mxnet-label-bot [pr-awaiting-review]


Do you have a working example?

First, thanks for this module.
Do you have any working example page using plunker, jsfiddle, or any?
I am an author of react-openlayers, and tried to implement with  ol.layer.VectorTile with MapBox style json object.
Currently, I am trying to achieve this with the current version of olms, but not successful yet.
Ref. https://github.com/allenhwkim/react-openlayers/issues/2
https://rawgit.com/allenhwkim/react-openlayers/master/app/index.html#/layers/vector-tile-2

I just tried your example at https://rawgit.com/openmaptiles/www.openmaptiles.org/master/maps/ol.html, and it seems to work fine for me.
The official example of ol-mapbox-style is here, with a hosted version here.

I have a similar problem with angular 2 app(

The working one is using this olms.js
https://github.com/openmaptiles/www.openmaptiles.org/blob/master/maps/olms.js
and this repo. has index.js
https://github.com/boundlessgeo/ol-mapbox-style/blob/master/index.js
Where is this olms.js coming from?
The current package.json is pointing to index.js
  "main": "index.js",

When I import like the following, it comes from index.js, not dist/olms.js. Am I right?
import { apply } from 'ol-mapbox-style';

You are right. olms.js is a standalone build for use without a bundler. When you use a bundler, you do not need it. And actually the recommended use is with a bundler.
See https://github.com/boundlessgeo/ol-mapbox-style/blob/master/test/test.js for a typical app that uses a bundler.
mapbox-to-ol-style has a lower level API and less dependencies. You can use it when you just style a single layer and do not need automatic font and sprite loading.
All that said, I still do not get from the comments on this ticket what the actual problem is. The stack trace in the first comment indicates a problem with OpenLayers. Maybe you are using an OpenLayers version that is too old?

`
public drawMap(): void {
this.map = new Map({loadTilesWhileAnimating: true, loadTilesWhileInteracting: true, pixelRatio: 1, controls: []});
this.view = new View({
  projection: 'EPSG:3857',
  center: proj.transform(this.centerCoords, 'EPSG:4326', 'EPSG:3857'),
  zoom: this.zoom,
  extent: this.bounds,
  maxZoom: this.maxZoom,
  minZoom: this.minZoom
});

//this.view.on('change:resolution', this.constrainPan.bind(this));
//this.view.on('change:center', this.constrainPan.bind(this));

//map events Observable
this.map.on('pointermove', (event: MapBrowserEvent) => this.onPonterMove.next(event));
this.map.on('moveend', (event: MapEvent) => this.onMoveEnd.next(event));
this.map.on('singleclick', (event: MapBrowserEvent) => this.onSingleClick.next(event));
this.map.on('click', (event: MapBrowserEvent) => this.onClick.next(event));

//this.createLayers();
this.map.setView(this.view);
this.map.setTarget(this.mapEl);
this.map.addControl(new control.ScaleLine());
let mousePosition = new control.MousePosition({projection: 'EPSG:4326', className: 'mouse-position'});
mousePosition.setCoordinateFormat((coord) => coordinate.format(coord, 'Координаты курсора: {y}, {x}', 6));
this.map.addControl(mousePosition);

let tileGrid = tilegrid.createXYZ({tileSize: 512, maxZoom: 22});

let lay = new layer.VectorTile({
  source: new source.VectorTile({
    projection: '',
    format: new format.MVT(),
    tileGrid: tileGrid,
    tilePixelRatio: 8,
    url: 'http://localhost:8080/data/v3/{z}/{x}/{y}.pbf'
  })
});

//this.map.addLayer(lay);

this.http.get('http://localhost:8080/styles/osm-bright.json')
  .map(res => res.json())
  .subscribe(res => {
    applyStyle(lay, res, 'openmaptiles').then(() => {
      this.map.addLayer(lay);
    })
  });

}
`
with openlayers 4.0.1

@hankypanky666 Your snippet does not give me any clue. Can you put up a live example, e.g. with a CodePan, that shows the issue?

I've also encountered this issue when trying to use ol-mapbox-style on an OpenLayers VectorTile source in a React app. It doesn't occur when using the standalone olms.js.
Here's a tiny project based on create-react-app that reproduces the issue as simply as I can, throwing errors similar to that reported by the OP:
https://github.com/metazool/ol-vectortile-react
Uncaught TypeError: c.Y is not a function
    at Mt (:3000/static/js/bundle.js:73642)

The frustrating part is that when I switch from ol.js to ol-debug.js (by changing the line in node_modules/openlayers/package.json to read "browser": "dist/ol-debug.js",) to try to get an insight into what OL is doing, then the tile layer just starts working with no changes to the code and no errors in the console!
I've had no trouble with the standalone build. This is all the latest release as of writing - OL ^4.2.0, ol-mapbox-style ^2.4.0, React ^15.6.1. I appreciate the issue may not even belong to this repo but this is the only place i've seen discussion of it.

I have published an update yesterday, and we now also pull in ol ^4.2.0. Maybe this fixes your issue?

Thank you for the update @ahocevar
I've updated to 2.5.1 but unfortunately still see the problem occurring - ol.js:617 Uncaught TypeError: c.Y is not a function etc etc
Suspicion is the problem may lie with webpack, I can look harder into this side of things but it's a bit beyond my JS ken ;)

@metazool: Looks like you're using the wrong OpenLayers package in your app. Use ol, not openlayers.

OK brilliant, when I switch to the ES6 'ol' npm package then this works well! I've updated my toy example repo accordingly.
Thanks very much for your help.

@allenhwkim, you'll also have to switch from the openlayers npm package to the ol package.


Fix return type of saveAttachment

Merge after #71

Thank you for the fix!

@Fevol Ready to merge


Add condition for enhancing performance

More detail at: https://github.com/viivue/frontend-debug/issues/18

About remark #18 (2):

[ ] Define refresh method: onScroll or RAF or none.

I still use the old method that we have implemented before but I have changed it a lot:

Item without isNotChange property -> only update when there's a new value.
Item with isNotChange property -> after this item has value, we will remove this item from our stats (reduce the size of the stats array).


[feat|sde-backend] : Policy-hub external service api integration.

Description
Added

Policy-Hub service api integration.

Pre-review checks
Please ensure to do as many of the following checks as possible, before asking for committer review:

[x] DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
[x] Copyright and license header are present on all affected files

@adityagajbhiye9 @sachinargade123  Please review and approve the PR for merge.

@sachinargade123  Please review