Remove the deprecations when using ember 1.13.0-beta.2

There is a slight non backward compatible change. To register a custom store, you use to be able to name it App.ApplicationStore and it would be picked up by the initializer. You now have to add a property to the main application object like so:
var CustomStore = Ember.Model.Store.extend({ custom: true });
App = Ember.Application.create({
  TestRoute: Ember.Route.extend(),
  Store: CustomStore
});

I updated/built the "released" code too.

Hey, thanks for the PR.
I want to avoid backwards incompatible changes. You updated the computed properties syntax but we can't do that without a shim for backwards compatibility. Should be pretty easy to write a utility method that does the right thing in new and old versions of Ember.

I am not 100% sure of a good way to identify the new computed property version from the old one. Looking at internals or version number is not ideal. Any idea?

@juggy maybe something like this? https://www.npmjs.com/package/ember-computed-polyfill

Thanks @jonnii . There was actually a little bug in this code, it was missing the oldvalue (third params) for the set method.
The code now works on both 1.11 and 1.13 without deprecation warnings.

Thanks!

@ebryn this probably justifies a new release, what do you think?


Installing nostream

Hi yall, pleb here. I'm trying to spin up a nostream relay on a Ubuntu DigitalOcean VPS.
I installed Docker and cloned the repo. I run ./script/start and get the error
Attaching to nostream, nostream-cache, nostream-db, nostream-migrate
nostream-migrate  |
nostream-migrate  | up to date in 692ms
nostream-migrate  |
nostream-migrate  | 3 packages are looking for funding
nostream-migrate  |   run `npm fund` for details
nostream-db       | 2023-03-29 20:17:16.595 UTC [2293] FATAL:  database "nostr_ts_relay" does not exist
nostream-migrate  | database "nostr_ts_relay" does not exist
nostream-migrate  | error: database "nostr_ts_relay" does not exist
nostream-migrate  |     at Parser.parseErrorMessage (/code/node_modules/pg-protocol/dist/parser.js:287:98)
nostream-migrate  |     at Parser.handlePacket (/code/node_modules/pg-protocol/dist/parser.js:126:29)
nostream-migrate  |     at Parser.parse (/code/node_modules/pg-protocol/dist/parser.js:39:38)
nostream-migrate  |     at Socket.<anonymous> (/code/node_modules/pg-protocol/dist/index.js:11:42)
nostream-migrate  |     at Socket.emit (node:events:513:28)
nostream-migrate  |     at addChunk (node:internal/streams/readable:324:12)
nostream-migrate  |     at readableAddChunk (node:internal/streams/readable:297:9)
nostream-migrate  |     at Readable.push (node:internal/streams/readable:234:10)
nostream-migrate  |     at TCP.onStreamRead (node:internal/stream_base_commons:190:23)
nostream-migrate exited with code 1
nostream-db       | 2023-03-29 20:17:16.977 UTC [2301] FATAL:  database "nostr_ts_relay" does not exist
service "nostream-migrate" didn't complete successfully: exit 1

What's going on? I thought docker would handle creating the database.
Thanks

Hi! Yeah the command does handle that but it's possible the size of your VPS is too small. What are the specs on your server?

I'm running 1vcpu 3gb ram 60gb ssd VPS.

Use https://pgtune.leopard.in.ua/ to tune your postgresql.conf file. With that amount of ram the postgres container fails and that's why the database is not created.
After tuning that file, make sure you delete your .nostr/data folder otherwise the postgres container won't attempt to create the database again.

Thanks, that fixed the db issue. Now I'm having issues with migrate, what is that?
nostream-migrate  | connect ECONNREFUSED <IP_ADDRESS>:5432
nostream-migrate  | Error: connect ECONNREFUSED <IP_ADDRESS>:5432
nostream-migrate  |     at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1494:16)
nostream-migrate exited with code 1
service "nostream-migrate" didn't complete successfully: exit 1

I deleted the .nostr and .nostr.local folders in the nostream main directory.

@mattsats looks like the database isn't up.
Before starting, make sure you stop everything first:
./scripts/stop
then
./scripts/start
Make sure you run the scripts from the root of the project not from the scripts directory.

I tried stopping then starting. Still doesn't work. Here's the full error log:
user@digitalocean-ubuntu-sfo2-s-1vcpu-1gb:~/nostream$ ./scripts/stop
[+] Running 5/5
 ⠿ Container nostream          Removed                                                                                0.0s
 ⠿ Container nostream-cache    Removed                                                                                0.6s
 ⠿ Container nostream-migrate  Removed                                                                                0.2s
 ⠿ Container nostream-db       Removed                                                                                0.5s
 ⠿ Network nostream            Removed                                                                                0.1s
user@digitalocean-ubuntu-sfo2-s-1vcpu-1gb:~/nostream$ ./scripts/start
Copying /home/user/nostream/scripts/../resources/default-settings.yaml to /home/user/nostream/scripts/../.nostr/settings.yaml
cp: cannot create regular file '/home/user/nostream/scripts/../.nostr/settings.yaml': Permission denied
[+] Building 0.2s (16/16) FINISHED
 => [internal] load build definition from Dockerfile                                                                          0.1s
 => => transferring dockerfile: 702B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 248B                                                                                0.0s
 => [internal] load metadata for docker.io/library/node:18-alpine3.16                                                         0.0s
 => [internal] load build context                                                                                0.1s
 => => transferring context: 15.98kB                                                                                0.1s
 => [build 1/6] FROM docker.io/library/node:18-alpine3.16                                                                     0.0s
 => CACHED [stage-1 2/6] WORKDIR /app                                                                                0.0s
 => CACHED [stage-1 3/6] RUN apk add --no-cache --update git                                                                  0.0s
 => CACHED [stage-1 4/6] ADD resources /app/resources                                                                         0.0s
 => CACHED [build 2/6] WORKDIR /build                                                                                0.0s
 => CACHED [build 3/6] COPY [package.json, package-lock.json, ./]                                                             0.0s
 => CACHED [build 4/6] RUN npm install --quiet                                                                                0.0s
 => CACHED [build 5/6] COPY . .                                                                                0.0s
 => CACHED [build 6/6] RUN npm run build                                                                                0.0s
 => CACHED [stage-1 5/6] COPY --from=build /build/dist .                                                                      0.0s
 => CACHED [stage-1 6/6] RUN npm install --omit=dev --quiet                                                                   0.0s
 => exporting to image                                                                                0.0s
 => => exporting layers                                                                                0.0s
 => => writing image sha256:5d1b7810ebb51e2e916a30de685e6af2bbabcde77d2d76b4d2702165361f7939                                  0.0s
 => => naming to docker.io/library/nostream-nostream                                                                          0.0s
[+] Running 5/5
 ⠿ Network nostream            Created                                                                                0.1s
 ⠿ Container nostream-db       Created                                                                                0.1s
 ⠿ Container nostream-cache    Created                                                                                0.1s
 ⠿ Container nostream-migrate  Created                                                                                0.1s
 ⠿ Container nostream          Created                                                                                0.1s
Attaching to nostream, nostream-cache, nostream-db, nostream-migrate
nostream-cache    | 1:C 07 Apr 2023 18:00:16.464 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
nostream-cache    | 1:C 07 Apr 2023 18:00:16.464 # Redis version=7.0.5, bits=64, commit=00000000, modified=0, pid=1, just started
nostream-cache    | 1:C 07 Apr 2023 18:00:16.464 # Configuration loaded
nostream-cache    | 1:M 07 Apr 2023 18:00:16.471 # Server initialized
nostream-cache    | 1:M 07 Apr 2023 18:00:16.471 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
nostream-db       |
nostream-db       | PostgreSQL Database directory appears to contain a database; Skipping initialization
nostream-db       |
nostream-db       | 2023-04-07 18:00:16.623 GMT [1] LOG:  starting PostgreSQL 15.2 (Debian 15.2-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
nostream-db       | 2023-04-07 18:00:16.625 GMT [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
nostream-db       | 2023-04-07 18:00:16.625 GMT [1] LOG:  could not bind IPv6 address "::1": Cannot assign requested address
nostream-db       | 2023-04-07 18:00:16.634 GMT [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
nostream-db       | 2023-04-07 18:00:16.649 GMT [27] LOG:  database system was shut down at 2023-04-07 18:00:11 GMT
nostream-db       | 2023-04-07 18:00:16.669 GMT [1] LOG:  database system is ready to accept connections
nostream-migrate  |
nostream-migrate  | added 36 packages in 4s
nostream-migrate  |
nostream-migrate  | 3 packages are looking for funding
nostream-migrate  |   run `npm fund` for details
nostream-migrate  | npm notice
nostream-migrate  | npm notice New minor version of npm available! 9.5.0 -> 9.6.4
nostream-migrate  | npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.6.4>
nostream-migrate  | npm notice Run `npm install -g<EMAIL_ADDRESS>to update!
nostream-migrate  | npm notice
nostream-migrate  | connect ECONNREFUSED <IP_ADDRESS>:5432
nostream-migrate  | Error: connect ECONNREFUSED <IP_ADDRESS>:5432
nostream-migrate  |     at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1494:16)
nostream-migrate exited with code 1
service "nostream-migrate" didn't complete successfully: exit 1

It says the database is ready to accept connections, but nostream-migrate fails after 10 seconds or so.

having same issue, ran start for the first time:
nostream-cache    | 1:C 19 May 2023 01:07:41.657 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
nostream-cache    | 1:C 19 May 2023 01:07:41.657 # Redis version=7.0.5, bits=64, commit=00000000, modified=0, pid=1, just started
nostream-cache    | 1:C 19 May 2023 01:07:41.657 # Configuration loaded
nostream-cache    | 1:M 19 May 2023 01:07:41.658 # Server initialized
nostream-cache    | 1:M 19 May 2023 01:07:41.658 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
nostream-db       | The files belonging to this database system will be owned by user "postgres".
nostream-db       | This user must also own the server process.
nostream-db       |
nostream-db       | The database cluster will be initialized with locale "en_US.utf8".
nostream-db       | The default database encoding has accordingly been set to "UTF8".
nostream-db       | The default text search configuration will be set to "english".
nostream-db       |
nostream-db       | Data page checksums are disabled.
nostream-db       |
nostream-db       | fixing permissions on existing directory /var/lib/postgresql/data ... ok
nostream-db       | creating subdirectories ... ok
nostream-db       | selecting dynamic shared memory implementation ... posix
nostream-db       | selecting default max_connections ... 100
nostream-db       | selecting default shared_buffers ... 128MB
nostream-db       | selecting default time zone ... Etc/UTC
nostream-db       | creating configuration files ... ok
nostream-db       | running bootstrap script ... ok
nostream-db       | performing post-bootstrap initialization ... ok
nostream-db       | initdb: warning: enabling "trust" authentication for local connections
nostream-db       | initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.
nostream-db       | syncing data to disk ... ok
nostream-db       |
nostream-db       |
nostream-db       | Success. You can now start the database server using:
nostream-db       |
nostream-db       |     pg_ctl -D /var/lib/postgresql/data -l logfile start
nostream-db       |
nostream-db       | waiting for server to start....2023-05-19 01:08:12.228 UTC [90] LOG:  starting PostgreSQL 15.3 (Debian 15.3-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
nostream-db       | 2023-05-19 01:08:12.228 UTC [90] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
nostream-db       | 2023-05-19 01:08:12.341 UTC [93] LOG:  database system was shut down at 2023-05-19 01:08:11 UTC
nostream-db       | 2023-05-19 01:08:12.416 UTC [90] LOG:  database system is ready to accept connections
nostream-db       |  done
nostream-db       | server started
nostream-db       | 2023-05-19 01:08:17.096 UTC [109] FATAL:  database "nostr_ts_relay" does not exist
nostream-db       | CREATE DATABASE
nostream-db       |
nostream-db       |
nostream-db       | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
nostream-db       |
nostream-db       | 2023-05-19 01:08:19.048 UTC [90] LOG:  received fast shutdown request
nostream-db       | waiting for server to shut down....2023-05-19 01:08:19.082 UTC [90] LOG:  aborting any active transactions
nostream-db       | 2023-05-19 01:08:19.084 UTC [90] LOG:  background worker "logical replication launcher" (PID 96) exited with exit code 1
nostream-db       | 2023-05-19 01:08:19.084 UTC [91] LOG:  shutting down
nostream-db       | 2023-05-19 01:08:19.100 UTC [91] LOG:  checkpoint starting: shutdown immediate
nostream-migrate  |
nostream-migrate  | added 36 packages in 2s
nostream-migrate  |
nostream-migrate  | 3 packages are looking for funding
nostream-migrate  |   run `npm fund` for details
nostream-migrate  | npm notice
nostream-migrate  | npm notice New minor version of npm available! 9.5.1 -> 9.6.7
nostream-migrate  | npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.6.7>
nostream-migrate  | npm notice Run `npm install -g<EMAIL_ADDRESS>to update!
nostream-migrate  | npm notice
nostream-migrate  | connect ECONNREFUSED <IP_ADDRESS>:5432
nostream-migrate  | Error: connect ECONNREFUSED <IP_ADDRESS>:5432
nostream-migrate  |     at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1494:16)
service "nostream-migrate" didn't complete successfully: exit 1```


B and I button but not anything else

Hi,
is it normal that i just have the Bold and Italic button but not all other ?
Best regards

I see that i can add other type of field but could we have standard full option without add on each Form ?
I can't add the ListFIeld

I see that i can add other type of field but could we have standard full option without add on each Form ?
I can't add the ListFIeld

A all-in field will be present in the coming v2 release with all the fields enabled.

I see that i can add other type of field but could we have standard full option without add on each Form ?
I can't add the ListFIeld

I just publish a new tag with the fix for the ListField.
As the v2 may take some days/weeks to come out.

V2 is out
ListField is fixed on v1 and v2 version.
The buildWithAllFields is also available in the v2 version.
thanks


Updated recipe to v1.0.0

Checklist

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

Updating the package version to v1.0.0, for public release tomorrow.

@conda-forge-admin, please rerender

@conda-forge-admin, please update team

@conda-forge-admin, I am a maintainer of bubbledet-feedstock but don't have write access to merge this PR.

Replaced by PR2.


feature: more precise check request

Issue check requests on specific groups of servers using subscribers attributes: described here https://sensuapp.org/docs/latest/api/checks-api.html#request-post-specification
instead of all check subscribers by default
Expected Behavior
Be able to specify which subscribers should receive the check request
Current Behavior
The check request is sent to all the machines that subscribed to this check
Possible Solution
on client view
https://uchiwa:3000/#/client/datacenter/hostname?check=checkname
in right panel (Check details)
add a refresh icon next to silence and elete result icon (top right corner)
that do an API /request with
{
  "check": "checkname",
  "subscribers": [
    "client:hostname"
  ]
}

Steps to Reproduce (for bugs)

Go to checks view: http://uchiwa:3000/#/checks
-Tick a check
Bulk actions
Issue check request

Context
Let's say you have a check that perform an heavy SQL request every 15min in MySQL instance of the sensu-client
You have 50 MySQL servers with this check
You're oncall, the alert rings at 3AM on client1
You fix it.
You don't want to wait 10min the next check run to verify the Alert goes back to green, you want to sleep Now !
You don't want to force a check request on all MySQL server that subscribed to this check, it would causes extra load on your whole platform and you just want to refresh 1 client.

Fwiw, We've accomplished something similar by making every client have a subscription to its own hostname.  Hacky you say, I'd answer probably :). Would be kinda cool to see similar behavior as a first class citizen in sensu.

@johntdyer same hack has been made part of Sensu in 0.26 and later, as clients now add a client:$CLIENT_NAME subscription automatically.
I think adding the capability to target check execution requests using per-client subscriptions is a good idea. 👍

Any plans to move forward with this guys?

The code part in charge of this in the check view:
/opt/uchiwa/src/public/bower_components/uchiwa-web/partials/views/check.html
                  <i class="fa fa-refresh fa-fw"
                    aria-hidden="true"
                    tooltip-placement="top-right"
                    tooltip-trigger
                    uib-tooltip="Issue Request"
                    ng-click="issueCheckRequest(dc, name, subscribers)">
                  </i>

I think we don't have to modify the issueCheckRequest function
I have just replicated this in the client view, in check details panel
graphically, it is what i'm looking for

However, I don't know how to submit the subscription value. I'm big noob with angular
would need something like:
ng-click="issueCheckRequest(dc, name, '[ \"client:'+client.name+'\" ]')"

maybe...


[1.10.2] Major Power issue with Mekanism and Modular Powersuits Power Suit

So im pretty sure a fix needs to come from Modular Powersuits mod but i will post this here anyways :D
Modular Powersuits Version: 1.2.124
Forge Version: <IP_ADDRESS>2
Mekiansm Version: <IP_ADDRESS>
See https://github.com/MJRLegends/Space-Astronomy-2-Feedback-/issues/127 for detals since everything is posted in that issue :D

More than likely their issue, but please let us know if that turns out not to be the case

Modular Powersuits Power Suit devs have confirmed and said it was there bug :D @thiakil


Adding Design icons suggestion

Skill Name
Framer, Krita, Sketch, Canva
Why?
These are design tools used by not only UI designers but also us UX Engineers love to use them.

Framer is a high-fidelity prototyping tool that comes with a lot of built in components and one can even publish website from the design. It's getting popular.
Krita is a professional FREE and open source painting program. It is made by artists that want to see affordable art tools for everyone. Many designers use this to make logos.
Sketch is the go-to application for many MacOS designers and it's also an Apple Design Award Winner. It is the all-in-one platform for digital design — with collaborative design tools, prototyping and developer handoff.
Lastly Canva is used by designers to make stunning presentations and some might use it for smaller design projects.

Reference Image

/* Edit - I added krita for light theme */

upvote for krita


Found and fixed the pesky formatting bug that affected viewport on mobile devices

ready for test

Final checks ok


[1.18] Can't delete words in JEI search bar properly when using the dimensional storage actuator

Describe the bug
If you already have words written in JEI search bar and then you open your dimensional storage actuator, you can't delete the words in JEI. No matter if JEI Sync button is on or not.
To Reproduce
Steps to reproduce the behavior:

Place Dimensional Storage Actuator
type something in JEI Search bar
right click the actuator to open it.
click in JEI search bar to remove the words you previously typed in step 2

Expected behavior
To be able to erase the words in JEI field :)
Screenshots
If applicable, add screenshots to help explain your problem.
System (please complete the following information):

Occultism Version: 1.36.1
OS: [e.g. Windows] Linux
Minecraft Version: 1.18.2
Modpack Link and Version, or list of mods: Occultism and its dependencies + JEI <IP_ADDRESS>

Additional context
Add any other context about the problem here.

Hello again, thank you for bringing a fix so quickly however it looks like it's not fully working. I have to click somewhere outside of occultism search bar before clicking in JEI search bar to erase words.
Here's a more thorough explanation :)
https://streamable.com/tqq450

I'm open to ideas here, but it this might something I cannot control - I can only access the text of the JEI search bar (via API), but not the actual search bar control element, so I cannot set it into "focus".
That you have to click outside of the search bar first is a bit odd though, that might be something I can change.
Continued in #747


Use Pickle+zlib When Applicable

The log message was off a bit when just passing the value to str(). This approach uses the actual way it is done under the hood.

I'm trying to understand the need for this change.  I'm guessing that something like this happened:

You are storing something big, like complete HTML pages, in memcached
You hit the 1 MB limit on cached values
You tried compression to get below the limit, but it didn't completely fix the problem,
You want to know how close to 1 MB you are with compression.

Is this accurate, or did you have another need for this change?

Nope that was it, we were getting a lot of errors and couldn't pinpoint why. Adding this to the logs allows us to check it.
I'm actually fine with closing this PR as we actually swapped to pymemcache for other reasons and our in-house django wrapper for it just rejects objects over 1MB after compressed.

I like the idea of the commit, since the 1 MB limit is not commonly known, and serialization + compression makes it hard to see exactly when it happens.  I'd prefer that pylibmc raises a more specific error that includes the size of the serialized value.  It looks like a libmemcached change might be making this harder than it seems.

Right... until I added this for our fork we were getting a plethora of timeouts caused by sending super large values to memcached. We had no way of knowing, but it turned out our blog posts were attempting to cache 6MB of compressed data because the pickle call was invoking all() on a django model.  Adding this helped better identify what was causing problems.

https://github.com/lericson/pylibmc/issues/184 has been fixed with a code change, so there may be some more options here.


Plugin not available on Runelite, needs update

It appears the plugin has been pulled from Runelite (not available anymore) as of May 18, 2022 due to needing what I assume are compatibility updates with current client versions. Is this something we can resolve? I always miss this super useful tool!

Sorry to hear that it's missing from plugin hub! Thanks for letting me know. I'll take a look and see what it takes to republish the plugin. Due to the holiday weekend (in the US), I will not have access to my normal PC and it may take a few days to resolve.
I'll close this issue when the plugin is republished.

This issue is addressed as of PR 2948. Thanks for reporting this. I'll close the issue.


Integration with a Parse Server

As I have said before, I like your way of programming and that's why I would like to receive your opinion. Having to use tables in common with different apps I was thinking of using a parse server with the framework and accessing through the PHP SDK.
It's interesting to access data in different languages, the problem that seems less direct to me.
Let's say that on a separate server from the main app I create a db with data to share with other apps.
Currently I can create $db and $dbw with a remote access restricted by IP and simply maintain a connection with a $dbw->app() ready to use from any controllers via the same function with any kind of query. I do not see same flexible way with the use of the rest API where I should to write code as
use Parse\ParseClient;

ParseClient::initialize( "APPLICATION_ID", "REST_KEY", "MASTER_KEY" );
ParseClient::setServerURL('url', '/');

use Parse\ParseException;
use Parse\ParseObject;

$myCustomObject = new ParseObject("MyCustomClassName");

$myCustomObject->set("myCustomKey1Name", "My custom value");
$myCustomObject->set("myCustomKey2Name", 999);

try {
  $myCustomObject->save();
  echo 'New object created with objectId: ' . $myCustomObject->getObjectId();
} catch (ParseException $ex) {

  echo 'Failed to create new object, with error message: ' . $ex->getMessage();
}

Or simple left join with condition that become long with equal or notequal in cascade.
What do you think about it and if any suggestion if I lost some part of that :)
Thanks.

So this seems to be mainly about Parse, which I don’t know, and not about this library here.
Please feel free to reopen this issue if you can make it more about this library, so that it becomes obvious which problems and questions are related to the project here.

My intention was not to receive support but an opinion on logic. I believe that your db management is fantastic because it is flexible and fast. And as I wrote I think it is better than a system like that offered by a parse server that should be used to speed up development. The only thing I see positive and that's why I was looking for advice is finding a way of integration would open many fast development possibilities such as sharing data with other programming languages up to the creation of CMS Rest API first.
Forgive me if I have gone on but I thought your opinion was useful.

Sure, got that, no problem. It’s just that the description of what exactly is the technical question was not very clear. To be honest, it’s still not clear enough, sorry. Could you give more details, or perhaps examples?

system like that offered by a parse server that should be used to speed up development. The only thing I see positive and that's why I was looking for advice is finding a way of integration would open many fast development possibilities such as sharing data with other programming languages up to the creation of CMS Rest API first.

So you want to speed up development through some integration? What integration? Integrating this library into a Parse application? How would that speed up development? Speed up your development in Parse?
And you want to share data with other programming languages? Sure, APIs, perhaps HTTP APIs and REST APIs are commonly used for that. What’s missing here in this project for you to be able to do this?


SAG+ASD: Greenland Cod stocks

To align inshore Greenland cod with similar stocks (e.g. North Sea cod, 9a anchovy) we need to deprecate the existing stocks (cod.21.1.a-c and cod.21.1.d-f), which become components within the new stock, cod.21.1.isc, allowing SAG and ASD to function as intended.

isc stands for inshore spawning cod, so it should not be repeated in the stock name.
the other two stocks have assessments in SAG, but they should never have existed, so it should be investigated by @odontaster how to deprecate and/or unlink the stocks.

@odontaster to consult the relevant people


New feature: Add in scope environment variables in ENV_VARIABLES

Purpose
Enable kit users to add environment variables to the scope of express' process.env. By default, the kit, only takes HOST, PORT, SSL_PORT, NODE_ENV and DEBUG into account.
This will enable users to define their environments' key values in their config files (e.g., Dockerfile, app.yaml for GAE).
Approach
Users will add a list of environment variable names to be taken into account in the ENV_VARIABLES environment variable using the following template: VAR1:VAR2:VAR3...
Open Questions and Pre-Merge TODOs

[ ] Do we need to add the environment variables to browser_dev.js or browser_prod.js. If so, why?

No need to add additional environment variables to browser_dev.js & browser_prod.js per @leebenson

This is basically exposing all environment variables into the code.

Yeah @nate0001, this needs some more thought. It's not the fault of this PR, but it seems that passing in any environment variable makes its way to browser.js if referenced (at least in development; I haven't tested production).
For security, what should happen is:

Any environment variable that's not in the 'allowed' list - HOST, PORT, etc, should be automatically nulled in the browser bundle.

All environment variables should be allowed on the server.

I'll take care of this locally in the next release.

That's right...that's why I had the previous PR where only variables listed
in ENV_VARIABLES where exposed
On Tue, Oct 24, 2017 at 9:49 AM, Nathan Tomsic<EMAIL_ADDRESS>wrote:

This is basically exposing all environment variables into the code.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/reactql/kit/pull/107#issuecomment-338996365, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AI5CeDAEuuenQovGbxKGKKnMJv5zCvulks5sverggaJpZM4QDUt3
.


Add logstash & filebeat logos

The elasticsearch and kibana logos are in the repo. Maybe you could add beat and logstash ones?
Edit:
Beat logo: https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt4da03cec7fcabcac/5d0cfe4b77f34fd55839b480/logo-beats-64-color.svg
Logstash logo: https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt8d79255492e03260/5d0cfe54561b9b0b537f94e8/logo-logstash-64-color.svg

Added in d108849295d8d92cef1581142d8b012fe34a8e72


upgrade to curator 5.5.4

Upgrade the curator version

/assign @gianrubio
/assign @lachie83

/ok-to-test
/lgtm


Refresh SQL Server Getting Started and Provisioning topics

I just updated these two topics to give links to Windows Azure Scoped library topics. And I also fixed one bug.
http://www.windowsazure.com/en-us/manage/windows/common-tasks/install-sql-server/
http://www.windowsazure.com/en-us/manage/windows/common-tasks/sql-server-on-a-vm/
Please stage them and send me a link for review. Thanks.

@Selcin Thank you for raising this issue.  We're closing old issues.  If you feel this issue should remain open, please comment to let us know that the issue should be reopened.


data.openaddresses.io checking map display

Was just wondering how often the data.openaddress.io page is rebuilt?  I've added an ISO code that should show up, but as it stands, I have no way of checking / testing.

I’m running it twice weekly, typically Tuesdays and Fridays.

Also, currently only the country-level ISO codes will show; we’ve only got Admin-0 geography in the repository.

So as it stands at the moment, the only way to get a sub-country level area to show up on the map is to provide a geojson outline of the region?

I think I've answered my own question.  Thanks for the tip on ISO codes, I'll go ahead and generate some geojson for the coverage extents.

Looks like Natural Earth might have us covered for Admin-1; I’ll determine if it’s addable.

…if you generate GeoJSON, can you be sure to add the ISO-3166-2 codes as well? Natural Earth doesn't have the complete codes, but it does have space for them and I may add them in a PR.

Support for these codes is in-progress at https://github.com/openaddresses/machine/pull/27


Order requests from a tarball based on the sequence folder

Fixes #3978
This change is backwards compatible and works on the old style tarballs which do not contain the sequence folder.

I ran a quick test with one old and one new tarball, both worked fine. Merging.


No dirname if running from recovery mode

The install.sh script calls dirname but this utility/builtin does not appear to be available when running from the recovery mode (boot into Options, Utilities->Terminal) on Mac OS 12.5.1.

will be fixed by #118


Added zend-db 2.9.0 release post

This PR contains a new blog post about the release 2.9.0 of zend-db.

@ezimuel Maybe we should only add a word that PHP 5.5 support has been dropped. And also that version 3 is going to support only PHP 7.1+, isn't it?
... and encourage everyone to switch to newer PHP version.
Somehow I can't see it in changelog, but PHP version has been bumped.
I would add also comparison link, between current release and previous one:
https://github.com/zendframework/zend-db/compare/release-2.8.2...release-2.9.0

@webimpress thanks for the feedback. I added your suggestions. I didn't add the comparison link because people eventually interested can see directly on github.


Gradle error building from main

Error: when building from main v1.5.0
(Release 1.4.6 builds OK)

Plz update your JDK to 17


swift-lang: shuffle the source directory structure (NFC)

This moves the swift-lang library out of the tools/SourceKit directory
and into the stdlib directory.  As it stands, the library required that
the standard library and the SDK overlay was being built.  This is
implicitly done when building the stdlib subdirectory.  Furthermore, it
had an odd tie between the flags for Swift and SourceKit which now have
the logic separated.  This clearly delineates the host and target
components in the repository.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@swift-ci please test

CC: @nathawes @akyrtzi @gottesmm

Build failed
Swift Test OS X Platform
Git Sha - c8de823ce6ccb9bbf1e92417a1092e8d0ef94c0b

Build failed
Swift Test Linux Platform
Git Sha - c8de823ce6ccb9bbf1e92417a1092e8d0ef94c0b

I think SwiftLang's only being used by the stress tester at the moment. Long term it should probably be a package that the stress tester and SourceKit-LSP both use to talk to sourcekitd, but for now we can just copy it (or SourceKit-LSP's sourcekitd wrapper code) into the stress tester repo and remove it. I'm working on something else at the minute but should be able to give that a go tomorrow or early next week.

@karwa this is also related to that change btw

@nathawes - this is going to kinda block some work that I am hoping to get done.  Do you think you could manage to do this today?

@compnerd  could you clarify, are the changes in this PR allowing the stress-tester to build and run successfully?

@akyrtzi this should have no impact on the current status quo.  Moving the sources into the stress-tester repository is a better solution.  This just moves the sources out of source kit and into the stdlib directory.

If it preserves status quo I don't see a reason not to take this PR and move the sources later.

If @nathawes is going to be able to move the sources today, I think that it is a better solution.  But, yes, otherwise, I think that I can fix up the small typo issue, and move forward.

@compnerd I don't think I'll be done by today, sorry, so feel free to go ahead with this PR.

@nathawes, alright, thanks.

@swift-ci please clean test

@swift-ci please clean test

@swift-ci please test Windows platform

@swift-ci please test Windows plaform

@swift-ci please test Windows platform

Build failed
Swift Test OS X Platform
Git Sha - e2f13355ed842c2892c7ec2d78913a19f8a97a94

@swift-ci please clean test

@swift-ci please clean test

@swift-ci please test Windows platform

@swift-ci please test Windows platform

@swift-ci please test Windows platform


V3: Image alt tags not handled by Schema?

Version: ^3.0.0-beta.10
If I don't use schemas I get errors for querying fields that have not been used yet. Recently I have begun getting similar errors on all my image fields ALT tags despite using the schema.
Expected result: Query images and their alt tags even if no image for this field has an alt tag yet.
Actual result: If an alt tag does not exist for this field on this query the build fails. Example error below
I have temporarily 'fixed' this by not querying alt tags for less used fields.
 ERROR  Failed to compile with 1 errors                                        12:38:23 PM

 error  in ./src/templates/prismic_client.js

Module Error (from ./node_modules/eslint-loader/index.js):

/Users/olliejt/Documents/GitHub/VBI/visualsbyimpulse/src/templates/prismic_client.js
  59:13  error  Cannot query field "alt" on type "PrismicStaffDataAvatarSmall"  graphql/template-strings

✖ 1 problem (1 error, 0 warnings)

 @ ./.cache/sync-requires.js 2:487-582
 @ ./.cache/app.js
 @ multi ./node_modules/event-source-polyfill/src/eventsource.js (webpack)-hot-middleware/client.js?path=/__webpack_hmr&reload=true&overlay=false ./.cache/app

✖ ｢wdm｣:
ERROR in ./src/templates/prismic_client.js
Module Error (from ./node_modules/eslint-loader/index.js):

Closing this out as it doesn't seem to be an active issue. Please let me know if this continues to be an issue!


Glide cannot install 5.X with batchv1 reference

This is a copy of https://github.com/Masterminds/glide/issues/945. I wasn't sure if it is an issue with glide or client-go, but since my issue with glide is still unanswered, I'm reaching out here. The issue is as follows:

I'm trying to bump client-go to 5.x, but glide up -v prints:
[ERROR] Error scanning k8s.io/client-go/pkg/apis/batch/v1: cannot find package "." in:
        /home/rodencor/.glide/cache/src/https-k8s.io-client-go/pkg/apis/batch/v1

Minimal example:
glide.yaml:
package: github.com/rcorre/k8stest
import:
- package: k8s.io/client-go
  version: 5.x.x

main.go:
package main

import (
	"k8s.io/client-go/kubernetes"
	batch "k8s.io/client-go/pkg/apis/batch/v1"
	"k8s.io/client-go/rest"
)

func main() {
	conf, err := rest.InClusterConfig()
	if err != nil {
		panic(err)
	}

	kube, err := kubernetes.NewForConfig(conf)
	if err != nil {
		panic(err)
	}

	var jobs []batch.Job
	jobs, err := kube.BatchV1().Jobs(namespace).List(nil)
	if err != nil {
		panic(err)
	}
}

I've tried rm -rf vendor and glide cc.
Let me know if this issue belongs on client-go instead.

I'm not able to glide install client-go v5.0.0 with the same error

Thanks, that got me further (I also had to rename k8s.io/client-go/pkg/api/v1 to k8s.io/api/core/v1).
I'm now hitting:
vendor/k8s.io/kubernetes/pkg/apis/extensions/v1beta1/zz_generated.conversion.go:1122:31: cannot use in.AllowPrivilegeEscalation (type bool) as type *bool in assignment

I'll open a new ticket if I can't figure that one out...

Turns out my subsequent issue is specific to helm: https://github.com/kubernetes/helm/issues/3445


How to compile library with open SSL?

I wish compile library with openssl (for rtmp over ssl)
and, is there anything i have to modify in the cmakelists.txt?

I need this help too.


removed 32px padding in footer

What issue is this referencing?
this pr fixes footer padding issue  #325

Do these code changes work locally and have you tested that they fix the issue yourself?

[ ✓] yes!

Does the following command run without warnings or errors?

[ ✓] yes! npm run pr-checks

Have you taken a look at our contributing guidelines?

[ ✓] yes!

My node version matches the one suggested when running nvm use?

[ ✓] yes!

@allcontributors add @Danbka-Taranbka for code


error while compilng kimera-vio[BUG]

Hello, thanks for your great work!
I have run Hydra without kimera-vio successfully.
However, when I added kimera-vio and tried to compile it, the following error occurred.
Describe the bug
'identity' is not a member of ’gtsam::Pose3‘
Can you help me?

Also, note I transferred this to the Kimera-VIO repo as it was not related to Hydra

Also, note I transferred this to the Kimera-VIO repo as it was not related to Hydra

Thank you for your reply. I had the same problem.  Next, I will try the method you mentioned.


Remove AbstractRenderable restriction on argument types

There is no reason to restrict grid to a vector of AbstractRenderables.
Fix another forgotten swap in calc_nrows_ncols.
Usage:
# remove restriction on these common patterns vvv
p = Any[]
# ...
  # push in some kind of loop
  push!(p, Panel())
# ...
grid(p)

Codecov Report

Merging #117 (363b400) into master (dfe38d8) will decrease coverage by 1.38%.
The diff coverage is 100.00%.

:exclamation: Current head 363b400 differs from pull request most recent head 43e4e35. Consider uploading reports for the commit 43e4e35 to get more accurate results

@@            Coverage Diff             @@
##           master     #117      +/-   ##
==========================================
- Coverage   94.72%   93.33%   -1.39%
==========================================
  Files          34       34
  Lines        1914     1906       -8
==========================================
- Hits         1813     1779      -34
- Misses        101      127      +26

Impacted Files
Coverage Δ

src/grid.jl
100.00% <100.00%> (ø)

src/_repr.jl
63.63% <0.00%> (-27.28%)
:arrow_down:

src/repr.jl
84.21% <0.00%> (-11.58%)
:arrow_down:

src/colors.jl
97.72% <0.00%> (-0.10%)
:arrow_down:

src/progress.jl
97.26% <0.00%> (-0.04%)
:arrow_down:

src/dendograms.jl
98.71% <0.00%> (-0.04%)
:arrow_down:

src/layout.jl
94.93% <0.00%> (-0.03%)
:arrow_down:

src/_progress.jl
97.95% <0.00%> (-0.03%)
:arrow_down:

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 dfe38d8...43e4e35. Read the comment docs.

Nice, but that removes the options to pass no renderables (nothing)?
Perhaps we can split that into a separate method for grid?

Nice, but that removes the options to pass no renderables (nothing)

No, this was already split in https://github.com/FedeClaudi/Term.jl/pull/113 (see https://github.com/FedeClaudi/Term.jl/blob/master/src/grid.jl#L89).
I've however, added more tests.

Ah nice I had missed that.  Happy to merge when you're ready.

You can merge ;)


What is the future of this project?

Hi, I was very hesitant to post this topic here because maybe it is not a technical issue but it is a problem and I want to get an answer.
Where does this project going?
In my opinion, this is the best technology for mobile development. Writing XAML elements with Razor syntax makes the app acts as a native app with a perfect and easy coding experience, so I wait for it eagerly. But the problem is no one talks about it, in confs, lives and any other events, and when I ask I don't get any direct answer. But the most disturbing answer is "MBB will be folded with MAUI blazor".
MAUI blazor is using web technologies for mobile development, and I know that we can use native functions and so on, but still not native, so it is not what I am looking for. I want to use XAML elements and pages but with Razor syntax.
I already started a project with MBB, and I don't care if I had to find workarounds for any issue right now, but I am really afraid to hear that MBB will not release, not because of this particular project, but because MBB is so amazing and I want to make it my main development framework for all next mobile apps.
So the question is: When will we see this framework in a stable release? Can we see it next year with MAUI?

Hello! How close is this to no longer being experimental? is a great tool!

Hello! How close is this to no longer being experimental? is a great tool!

As @Eilon said "Microsoft didn't approve this project yet", so it is still not official. And we think they will continue with it after MAUI gets a stable release

Ok, it's such a shame Microsoft didn't approve it. Its awesome

Ok, it's such a shame Microsoft didn't approve it. Its awesome
Actually what I afraid of is Microsoft thinks that is number of people who want to use XAML with Razor is so little, and that is was Sam Basu's opinion in this video at 4:41:41 when I asked him about MBB

@AmirImam It is not really about that. They are still very unsure what to do. MAUI is still being finalized for Version 1.
What Sam Basu says is speculations as he is not working for Microsoft.
As I see it, MAUI should not be tied to XAML. Adding Blazor to native support would be a great win for those who like the component model. And Comet as an alternative etc.
Microsoft cannot provide everything.
However, this project could be forked and ported to target MAUI instead. It would be minimal work just to make it generate wrappers that use MAUI instead of Xamarin.Forms. They are pretty similar stil, as MAUI is an evolution of the former.
But what remains is how to make it work with the improvements, like handlers. That only Microsoft or close collaborators really know.

@marinasundstrom
Yes, I know that Sam's opinion is just speculation, but it made me afraid because from what I see there is no big audience for MBB yet.
I think there are two types of audience, who want to use native UI with XAML, and who want to use Razor with HTML. The third type is us, who want to use native UI with Razor syntax.
In my opinion native UI with Razor syntax will be the greatest framework for mobile development.
Anyway, I am waiting for MAUI to see what will happen in this project then.

I have forked this repository and published to nuget (renamed to BlazorBindings.Maui).
You can read more details here.
If at any point of time Microsoft developers decide to push this repository moving forward, I'll gladly contribute all of my changes here.

Hello! How close is this to no longer being experimental? is a great tool!

As @Eilon said "Microsoft didn't approve this project yet", so it is still not official. And we think they will continue with it after MAUI gets a stable release

When MAUI will get stable release? Currently it is available in preview version but I am waiting for it to come in community version.


Add functions to access new asset listing endpoints.

Also includes a separate change regenerating our API code.

@thetorpedodog do the new functions require regeneration of the API? Can you tease these apart?

Of course, new endpoints, new YAML. I'm surprised by the number of changed files. Is this with the same version of the API generator as in the committed bash script? Are all of these changes due to updates and improvements in the spec?

Yes; this is strictly the result of running ./update_generated.sh (you can try it yourself). It’s a pretty typical diff in my experience.


jenkinsfiles: add IMAGE_REGISTRY env parameter

Refactoring the various quay.io/cilium hardcoded registry mentions in the Jenkinsfiles will allow easier tweaking from forks, which is notably useful for development.
Also adding possible override from within Jenkins job configuration via JobImageRegistry, just like we have already for other parameters.

/test-jenkins

/test-upstream

/test-upstream-k8s

/test-jenkins

/test-upstream-k8s

/test-1.21-5.4

/test-gke


xDS: remove v2 support

Let's wait for the interop tests to pass on this before we merge

Tests -
https://sponge2.corp.google.com/73dee070-e95e-462a-aced-77aca48a2d94
https://sponge2.corp.google.com/c73dac3a-5336-48fc-887f-63d4184128cf
https://fusion2.corp.google.com/invocations/eea4c34b-14c6-43bb-b7f9-fe6eaeecc4b7/targets


problem plotting sqrt

Plotting the sqrt function now returns an error, due to its behavior for negative argument. I am pretty sure it was working not so long ago. I am using julia 0.4rc1 with Winston 0.11.12.
julia> plot(t->sqrt(t), -1,1)
ERROR: DomainError:
sqrt will only return a complex result if called with a complex argument. Try sqrt(complex(x)).
 in sqrt at ./math.jl:144
 in anonymous at none:1
 in fplot_points at /home/yves/.julia/v0.4/Winston/src/plot.jl:518
 in plot at /home/yves/.julia/v0.4/Winston/src/plot.jl:184
 in plot at /home/yves/.julia/v0.4/Winston/src/plot.jl:240

julia> plot(t->sqrt(complex(t)), -1,1)
ERROR: InexactError()
 in convert at complex.jl:18
 in fplot_points at /home/yves/.julia/v0.4/Winston/src/plot.jl:526
 in plot at /home/yves/.julia/v0.4/Winston/src/plot.jl:184
 in plot at /home/yves/.julia/v0.4/Winston/src/plot.jl:240

Same behavior with the vectorized syntax
 let t = -1:0.01:1 ; plot([t ; sqrt(t)]) end

This is a julia change, not a Winston issue.


Make sure users without access to build logs can not download artifacts from failed builds

Users that are only allowed to download build artifacts should not be able to download the artifacts from a failed build. It could contain source files which have not been removed by the build script.

The commit linked above contains a wrong issue number. Isn't related at all.


Linking.getInitialUrl never returns

System:
OS: macOS Mojave 10.14.6
CPU: (8) x64 Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
Memory: 30.13 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 8.15.1 - /usr/local/bin/node
npm: 6.9.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 13.0, DriverKit 19.0, macOS 10.15, tvOS 13.0, watchOS 6.0
IDEs:
Android Studio: 3.4 AI-183.54<IP_ADDRESS>52501
Xcode: 11.0/11A420a - /usr/bin/xcodebuild
npmPackages:
react: 16.9.0 => 16.9.0
react-native: 0.61.2 => 0.61.2
npmGlobalPackages:
react-native-cli: 2.0.1
React Native version:
0.61.2
Steps To Reproduce

On simulator / emulator / live iOS or Android phone run the command await Linking.getInitialUrl().

this command never returns and just hands
Describe what you expected to happen:
I expected an event to be returned. This worked in previous versions. This is the 4th app i've updated to v61.2 and had this issue on.
Snack, code example, screenshot, or link to a repository:
async function someFn() {
     let event = await Linking.getInitialURL()
     // Next line of code never runs
     ....
}

Edit: I've confirmed that this only happens when using async await. Using .then.catch the event seems to return as normal.

Try putting a catch on there to see if you're getting an error.
async function someFn() {
     let event = await Linking.getInitialURL().catch(err => console.log(err))
     // Next line of code never runs
     ....
}

We have the same problem on Android after updating to Expo SDK 36 (React Native 0.61).

Duplicate of #25675

Hi,
my team has discovered that debug mode is breaking something since we have the correct and expected behavior in a real iOS device.
Unfortunately, this is not true for android. In a real device, without debug, we are experiencing a return of null value when calling getInitialUrl for cold-start (app is not running).
I hope this can help, and if someone figures how to make it work for android, please post.
System:
OS: macOS 10.15.2
CPU: (8) x64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
Memory: 68.70 MB / 16.00 GB
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 11.9.0 - /usr/local/bin/node
npm: 6.5.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
IDEs:
Xcode: 11.3/11C29 - /usr/bin/xcodebuild
npmPackages:
react: 16.9.0 => 16.9.0
react-native: 0.61.2 => 0.61.2
npmGlobalPackages:
react-native-cli: 2.0.1

Thx a lot for the idea! the app behaves differently if you call Linking. getInitialUrl in debugging mode

still happen in "react-native": "0.63.0", and it's always "null"

Closing as duplicate of #25675


React-waterfall-persist like Redux persist?

Any Plans for this? I have tried to store the state in AsyncStorage,
But the state gets updated on return from action creator failed. any callbacks, hooks to know if the state is updated? and any async way to set initial state?

@sreevisakh I give up this and change to use mobx


Drop explicit RSA, ECDSA, etc types in favour of ssh.SSHKeyType only

          This should eventually drop the explicit RSA, ECDSA, etc types. We want just SSH here.

Originally posted by @adityasaky in https://github.com/gittuf/gittuf/pull/436#discussion_r1638653883

To add, this has two dimensions. We want to drop support for these keys in "standard formats" (now handled by the ssh-keygen signer/verifier) as well as in the custom securesystemslib format (dropping entirely). The latter will cause a lot of diffs possibly, especially in tests. 😬

Reopening this: we added back support for legacy key types for verification only so as to not lose the gittuf metadata we've initialized on this repo and elsewhere. This is only used for historical policy states and the verification of its metadata, but we may still want to drop this ahead of a 1.0.


[Feature]: CMD+Click navigation

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
CMD+Click navigation, which allows users to get from an invocation of a function to the definition of a function in VS code. We would like to navigate across appsmith in the same way, where every reference to a widget or action, can be used to link back to it.
When I hover on an action reference, it should be highlighted, showing the entity/property/action you are navigating to. When I press command on my keyboard, it is underlined, the same way as a hyperlink does, and when I click on it, it takes me to that widget.
(Job stories to follow)
Why should this be worked on?
At the moment, users spend a large amount of time scanning the entity explorer, trying to figure out where the entity they are trying to edit is. Ideally this should not be the case, and all users are able to get to their entities as easily as possible.
While we have the omnibar, and other solutions for this, it seems that a highly requested feature is CMD+Click navigation

Stats

Stat
Values

Reach
10000

Effort (months)
1


Added Status check for mcg-ms-console pod

Signed-off-by: Aayush Chouhan<EMAIL_ADDRESS>

@achouhan09 please fix lint error

/approve


release on f-droid (help wanted)

Would be nice to have an f-droid version
https://f-droid.org/en/docs/FAQ_-_App_Developers/#how-do-i-get-my-app-included

https://f-droid.org/packages/com.wuxialearn.wuxialearn/


pool.map crashes on Mac (Apple silicon + docker) in dashboard utils with getpwuid(): uid not found

I'm running mpire on a Mac with an M3 processor and getting the following error:
  File "/workspace/quantization_and_background_removal/processable_folders_compressor.py", line 179, in compress_images_in_processable_folder_by_parts
    results = pool.map(
              ^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/mpire/pool.py", line 467, in map
    results = self.map_unordered(
              ^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/mpire/pool.py", line 534, in map_unordered
    return list(self.imap_unordered(func, iterable_of_args, iterable_len, max_tasks_active, chunk_size,
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/mpire/pool.py", line 742, in imap_unordered
    with ProgressBarHandler(self.pool_params, self.map_params, progress_bar, progress_bar_options,
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/mpire/progress_bar.py", line 56, in __init__
    self.function_details = get_function_details(map_params.func)
                            ^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/mpire/dashboard/utils.py", line 132, in get_function_details
    func_details = {'user': f'{getpass.getuser()}@{socket.gethostname()}',

     ^^^^^^^^^^^
^^^^^^

  File "/usr/local/lib/python3.11/getpass.py", line 169, in getuser
    return pwd.getpwuid(os.getuid())[0]
           ^^^^^^^^^^^^^^^^^^^^^^^^^
KeyError: 'getpwuid(): uid not found: 501'

when executing
with WorkerPool(n_jobs=available_cores, start_method='spawn') as pool:
    results = pool.map(
         self.compressor.remove_background_and_compress,
         make_single_arguments(parameters_to_perform),
          iterable_len=len(images_to_perform),
          progress_bar=True,
          progress_bar_options={
               "desc": f"Compressing images: chunk {chunk_index} ", "smoothing": 0
          }
)

The error started to occur with version 2.9.0. Previous versions (e.g., 2.8.1) didn't have this problem and are running fine on my machine.
The setup is a little bit special, but nothing super-fancy, because the code is executed within a docker container (so I'm technically running Linux). When executing the code directly on my Mac, it works fine. So I assume it's related to the combination of an Apple Silicon + Docker + Use Rosetta for x86_64/amd64 emulation on Apple Silicon + mpire.
But anyway, it's a bit unfortunate that some dashboard utility function causes the whole process to crash and I can't figure out how to disable this function. I'm not using the dashboard functionality and certainly didn't start the dashboard, so I don't quite get why this code in progress_bar.py:55 even gets called in the first place?
if show_progress_bar and DASHBOARD_STARTED_EVENT is not None:
    self.function_details = get_function_details(map_params.func)
    self.function_details['n_jobs'] = pool_params.n_jobs
else:
    self.function_details = None

I tried to change my code to
with WorkerPool(n_jobs=available_cores, start_method='spawn') as pool:
    results = pool.map(
         self.compressor.remove_background_and_compress,
         make_single_arguments(parameters_to_perform),
         iterable_len=len(images_to_perform),
         progress_bar=False,
)

but the same function still gets called and I'm still getting the same error.

Thnx for the detailed report.
There's indeed no need to obtain the function details when the dashboard hasn't started yet. I will make this change later today.
As a quick workaround, uninstall the dashboard requirements (e.g., flask) and then it should not invoke that part. Alternative, patch the DASHBOARD_STARTED_EVENT like so:
from unittest.mock import patch

with WorkerPool(n_jobs=available_cores, start_method='spawn') as pool, patch("mpire.progress_bar.DASHBOARD_STARTED_EVENT", new=None):
    results = pool.map(...)

@sybrenjansen Thanks for the fix! Are there plans for a bugfix release? I've been running into the exact same issue in a k8s environment.

I made a new release just now. Should be available in a few minutes


Repostore crash debug

I'm going to apply this change in branch debug/extra-logging, bake a new image, and run tests.


New package: Stressify v0.1.0

Registering package: Stressify
Repository: https://github.com/jfilhoGN/StressifyPerformanceTest
Created by: @jfilhoGN
Version: v0.1.0
Commit: 0a0cb53306818e2652e2f4693fd7804ac65abb7a
Git reference: HEAD
Description: Repository to create a framework of performance testing with JuliaLang
Release notes:

Stressify Performance Test is a performance testing tool written in Julia, inspired by tools like K6. Its primary focus is on collecting, analyzing, and generating customizable metrics to help developers gain deeper insights into the performance of APIs under various load conditions. With Stressify, you can easily track performance indicators and extend the tool to create new metrics tailored to your needs.

Closed in favor of #120953.


Use recursive circom proofs for UST

Barry has said that recursive circom proofs are close to being ready to use. Once this is the case we should be able to rework a lot of our UST logic so that the bulk of it can be done by a server, then the user just proves that those proofs are valid plus some additional logic.
Related #128 (makes DOS less impactful because work can be delegated to large servers by non-users)

@vimwitch about this issue, do you think we need to tackle in short term?

No, we'll probably want to do this with PLONK, and circom support is still very poorly optimized and halo2 is not ready for use yet. Something we can do in the longer term.


Roll Flutter Engine from c090055485cf to da611f8b7e48 (2 revisions)

https://github.com/flutter/engine/compare/c090055485cf...da611f8b7e48
2022-08-18<EMAIL_ADDRESS>[Impeller] Linear Gamma to sRGB filter implementation. (flutter/engine#35388)
2022-08-18<EMAIL_ADDRESS>Avoid object creation during each frame (flutter/engine#35343)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Aptly mirror resource does not support the -ignore-signatures option

Cookbook version
current
Chef-client version
any
Platform Details
Any
Scenario:
Aptly does not currently support non-armored detached keys (https://github.com/aptly-dev/aptly/pull/780) until 1.4.0 releases. This is an issue when trying to mirror the ubuntu cloud archive repo (https://github.com/aptly-dev/aptly/issues/773). As we are unable to verify the keys with the current production release of aptly, and even the latest nightly release that's on the repo, ignoring the signature is the only way to mirror this repo using Aptly at all today.
See:
https://www.aptly.info/doc/aptly/mirror/create/
https://www.aptly.info/doc/aptly/mirror/update/
The above functions would need to incorporate this into the cookbook to make it work properly - some experimentation shows that simply doing aptly mirror create with -ignore-signatures and then trying to do aptly mirror update results in the update attempting to verify the signature anwyay.
Steps to Reproduce:
Look at https://github.com/sous-chefs/aptly/blob/master/resources/mirror.rb#L19-L32 and see there is no ignore_signatures property.
Expected Result:
Ability to ignore the signatures and use the repo anyway.
Actual Result:
Unable to do so using this cookbook.

(This is similar to #49 , and like that one, I'm perfectly willing to do the lifting and send in a PR for it myself, assuming everyone's fine with adding this option in.)

Hi,
Sorry for the delay.
Is it only aptly mirror create and aptly mirror update that has the argument -ignore-signatures?

Certainly looks like it. Also aptly mirror edit, but this cookbook doesn't do that (yet?).
Once you have the mirror updated, you can take snapshots and publish the snapshot regardless of whether the signature was verified or not.

Ok, I've started working on a PR

This should be resolved now too with the merge of #94.

@freakinhippie Great work. I totally dropped the ball on this...


Roqoqo documentation - modules

circuit appears on the list of Modules in docs.rs although in lib.rs it says:
#[doc(hidden)]
mod circuit;

It is intended that users access Struct 'Circuit' (not module circuit) in order to get the documentation, so module circuit should be hidden from the Modules list.

#[doc(hidden)] was re-added to the lib.rs in src


Include an example of the dashboard in the README

I am interested in this gem however I would love to know more about:

This gem is used to report opinionated statistics about modularization

Rather than needing to dive into the dashboard json, I would like to see an image showing the dashboard for a sample project so that I could get a better idea of what these opinionated statistics are.

Hi @Catsuko,
I don't have a dashboard of a sample project but I can give you the titles of the graphs we use in ours:

Violations by package
Violations by team
Packwerk usage by teams (which packs enforce different violation types)
Overall violations
% of packs with non empty API's
Packs most depended on

hello @tstannard
Are those graphs provided by this gem or something your team has put together? Mainly I want to know if I add this gem and add the dashboard, what do I get? 🤔

Hi @Catsuko
Is this what you are looking for?

yes, thank you for the update 🙏


Simplify geo_factors_codegen w/ skip_dir_nesting

Previously, geo_factors_codegen.py was using an ad-hoc system of
generating all the C++ factors into a factors folder. It did this by
calling Codegen.generate_function to generate the code into a
temporary file, read the file into a string, then re-wrote the string
into the desired location. I assume this was to avoid all the fluff
that's generated by default with Codegen.generate_function.
However, there is the skip_directory_nesting optional argument for
Codegen.generate_function which does precisely that (I think the code
in this file might have been written before that option was added).
So, to reduce confusion (such as the confusion I faced when I first
started looking at this file) and complexity, I rewrote the code to
instead use the skip_directory_nesting argument.
Topic: geo_factors_use_skip_directory_nesting

Reviews in this chain:
└https://github.com/symforce-org/symforce/pull/295 Simplify geo_factors_codegen w/ skip_dir_nesting
　└https://github.com/symforce-org/symforce/pull/294 Add diagonal & isotropic sqrt_infos in geo factors

#
head
base
diff
date
summary

0
f9a6f2d0
4c368815
diff
Feb 1 10:39 AM
1 file changed, 13 insertions(+), 56 deletions(-)


feat: Point In Time Recovery (PITR) samples

Adds samples for PITR.

This should only be merged after we release a client library version with the PITR feature. (Before that we need to rebase over master).

This should only be merged after we release a client library version with the PITR feature. (Before that we need to rebase over master).

@thiagotnunes New samples should be added as standalone samples and follow the guideline in https://github.com/GoogleCloudPlatform/java-docs-samples/blob/master/SAMPLE_FORMAT.md. The AddNumericColumn sample could be used as an example.

@thiagotnunes New samples should be added as standalone samples and follow the guideline in https://github.com/GoogleCloudPlatform/java-docs-samples/blob/master/SAMPLE_FORMAT.md. The AddNumericColumn sample could be used as an example.

Closes in favour of https://github.com/googleapis/java-spanner/pull/837


Deamon does not start after fresh install on Windows 10

I need to use Windows for a while. After install hotel and run hotel start but it never starts. I can know this easily running:
netstat -ano | Select-String "2000"

which doesn't return any results.

Where is the daemon.log file in Windows?

System info

Windows 10 x64 Creators Update
Node 8.2.1
Hotel 0.7.6 (latest)

Thanks

Hi @gugadev,
In your user home, you should find a directory ./hotel.
Feel free to paste the content of the daemon.log.

Hi @typicode, thanks for reply. The folder exists but there is no any daemon.log, just startup and conf.json files.

I have Windows 10 too and last time I tested it, it worked.
Maybe there was an update that broke something.
I'll give another try.
Maybe it can help debugging, hotel start creates a vbscript in AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup then starts the vbscript to start hotel.
https://github.com/typicode/user-startup#how-it-works

I'll do that, @typicode. I'll update this issue very soon. Thanks for help.

I've retried on Windows 10 with Node 8.1.0 and didn't have problems. I'll update Node.

I ran the vb script with no errors but the daemon.log is not created.

You're welcome, happy to help (and hope a solution will be found). If you can find hotel module directory, you can run manually the daemon with the following command:
node lib/daemon

This way, you can excude the vbscript and you'll see directly the daemon output with perhaps a stacktrace.
I've not yet had feedback about rights issues on Windows, but some people said to have issues with Antivirus blocking the vbscript (not saying you should disable it ^^). I've tried with Windows Defender on my machine and there's no particular issue.

Yup @typicode, running the daemon directly with node works as expected. Also, I added the hotel.vbs script to exclusions in Windows Defender, but it doesn't works.

Same for me, running the daemon directly works fine. As a workaround I'm running a bash script at startup of my computer, which runs the daemon directly

@typicode:

Maybe it can help debugging, hotel start creates a vbscript in AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup then starts the vbscript to start hotel.

I have the same problem and the reason is actually that the hotel.vbs file is not created in folder:
%AppData%\Microsoft\Windows\Start Menu\Programs\Startup


Upload to pypi registry

It would be great to upload this project to pypi so that it is more easily installable from other package management tools. Right now, we install our package dependencies using a conda lock file. It is a bit tricky to add a new dependency from a github repository. It should be fairly straightforward to upload the most recent release: (e.g. https://openmdao.org/newdocs/versions/latest/other_useful_docs/building_a_tool/release_process.html). This would make it easier to include this package in our deployment setup.

That's a great suggestion, and I appreciate your input. I initially considered this approach but decided against it primarily due to concerns related to dependencies.
Releasing the package on PyPI without resolving these dependencies might lead to incomplete installations, potentially confusing users who expect seamless functionality upon installation – perhaps my expectations are a bit high here, but it's essential to ensure a smooth user experience.
Currently, the package relies on either Tesseract or Paddle for captcha recognition. However, resolving these dependencies can be platform-dependent, and I haven't had the chance to address these issues yet.
Another alternative to consider is implementing a mechanism that informs users if their environment lacks the necessary dependencies when they attempt to import the package. This way, users would receive immediate feedback about missing requirements.
I'd love to hear your thoughts on how we should approach managing these dependencies when uploading the package to PyPI. Your input and insights are valuable in making the right decision.

Hi @urbanogilson!
Happy to help out with packaging here! Probably the easiest way forward here is to check for the respective binaries to be present and raise a verbose error message in case neither tesseract nor paddle are present as you proposed. The alternative would be to make sure that there is a wheel present for either, but that seems unlikely and a high lift.
However, once there is a PyPi package, I'm happy to also package this on conda-forge, where we could depend on the existing tesseract package. So users could install sicar as simple as
conda install sicar

Does that sounds good to you? If so, the plan would be:

[ ] Add guradclauses which check dependencies to the library
[ ] Add automatic release to PyPi
[ ] Add conda-forge release

Hi @bstadlbauer !
Apologies for the delayed response; I was on vacation 🏝.
Your plan sounds great. Let's definitely move ahead with it!
 I'll also explore automating the release process on PyPi using GitHub actions.

Action to automatic release to PyPi pushed to #17

@urbanogilson We've noticed that the format of the download has changed, which breaks this library. We've thus moved away from it, so I'm not sure whether there's a strong incentive to put it on PyPi?

@bstadlbauer the format changed, and I updated it to support the new version.
I will keep this issue open to monitor interest in this implementation


Multiple Languages

Ballots in multilingual communities often require, by law, that ballots and other official election-related information be made available in multiple languages. Consider supporting multilingual representations via the Accept-Language header, or otherwise.

@kemitchell FYI, the Voting Information Project recently added internationalization / multi-language support to their upcoming version 5.0 spec.  I'm also in the process of making multi-lingual data available at the SFBED project (at least for the election data in San Francisco that is "fixed" like office and government body names).  I'm aiming for the seven languages officially supported by the SF Department of Elections.

Unsure how to do this with Jekyll and Github Pages.

@diafygi Have a look at this blog post:
https://www.klaasnotfound.com/2017/02/16/proper-multilingual-site-with-github-pages-and-jekyll/


NULL pointer exception on existing dump BF save

Hi Flippers,
I'm getting a NULL pointer exception when I try to save a key from BF from an existing dump. Please check the video. In this case I'm using NICE 12 433 as a starting dump file:
Filetype: Flipper SubGhz Key File
Version: 1
Frequency: 433920000
Preset: FuriHalSubGhzPresetOok650Async
Protocol: Nice FLO
Bit: 12
Key: 00 00 00 00 00 00 0A 6F

FW: unlshd-066e
APP: v3.9.X subghz_bruteforcer.fap.zip
https://github.com/DarkFlippers/flipperzero-subbrute/assets/3976868/e43654db-182d-4c7e-b708-187ca6c2606d

@oleynikd please check fixed version:
https://github.com/DarkFlippers/flipperzero-subbrute/releases/tag/v3.10.0

@derskythe  Tested version v3.10.1 - problem solved. Thanks.


[TOOLS] Update dcos_launch to latest SHA

See https://github.com/dcos/dcos-launch/pull/162

Created Cluster with new dcos-launch at https://teamcity.mesosphere.io/viewLog.html?buildId=1155447&buildTypeId=DcosIo_DcosCommons_PrJobs_HelloWorldStrictPr&tab=buildLog

Thanks, @takirala  / @nickbp !


Split blkinfo test into multiple tests

When trying to diagnose https://github.com/anatol/booster/issues/172, I had (admittedly, not very much) trouble discerning which assertion was actually failing in TestBlkInfo. To this end, I propose splitting this test into multiple tests, allowing problems to be highlighted more easily, and adhering to the general maxim that only one logical component should be included per test.

The change looks good. It has a conflict with the previous change though.

Cheers; have now merged earlier fix into this commit.


MANAGE FIREWALL_CONFIGURATION

Is your feature request related to a problem? Please describe.
resource "snowflake_account_grant" "grant" {
  roles                  = "MY_ROLE"
  privilege              = "MANAGE FIREWALL_CONFIGURATION"
  with_grant_option      = false
  enable_multiple_grants = true
}

Docs
Error:
Error: expected privilege to be one of [CREATE ACCOUNT CREATE INTEGRATION CREATE USER MANAGE GRANTS MONITOR USAGE ATTACH POLICY CREATE DATABASE CREATE NETWORK POLICY CREATE ROLE EXECUTE TASK MONITOR EXECUTION APPLY MASKING POLICY CREATE DATA EXCHANGE LISTING CREATE SHARE CREATE WAREHOUSE MANAGE ORGANIZATION SUPPORT CASES MANAGE USER SUPPORT CASES APPLY ROW ACCESS POLICY APPLY TAG IMPORT SHARE OVERRIDE SHARE RESTRICTIONS EXECUTE MANAGED TASK MANAGE ACCOUNT SUPPORT CASES], got MANAGE FIREWALL_CONFIGURATION

Describe the solution you'd like
I wanted to implement the setting in the docs.
Describe alternatives you've considered
N/A
Additional context
N/A

Hey 👋
Closing the issue as it's referring to the deprecated resource and we're not supporting them. Please, try to use the latest provider version with the non-deprecated resources (e.g. snowflake_grant_privileges_to_account_role). If the issue persists on the non-deprecated resource (or the feature is present in Snowflake, but not in the provider), please create a new GitHub issue. The migration guide may help during migration to the latest resources. Here's a list of the latest, non-deprecated, grant resources:
Resources
snowflake_grant_privileges_to_database_role
snowflake_grant_privileges_to_account_role
snowflake_grant_account_role
snowflake_grant_database_role
snowflake_grant_application_role (coming soon)
snowflake_grant_privileges_to_share
snowflake_grant_ownership (coming soon)
Data sources
snowflake_grants


chore(master): release 1.0.12

:robot: I have created a release beep boop
1.0.12 (2023-02-20)
Bug Fixes

left-align labels (931828c)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/builder555/PineSAM/releases/tag/v1.0.12 :sunflower:


removing smartgateway: white label

Requires co-ordinating change in telemetry-framework: https://github.com/redhat-service-assurance/telemetry-framework/pull/43

 [SAF] Resolve issues with smoketest not completing when running downstream vs upstream image imports


Persistent command history

Command history is a traditionally essential functionality of the shell UI. Elvish now has a per-session, in-memory command history, but no persistent history yet.
Despite of the apparent simplicity, there is a particularly annoying issue about command history - how multiple parallel shell sessions should interact with the persistent history and with each other. See http://zsh.sourceforge.net/Doc/Release/Options.html#History for zsh's struggles on this issue. Like always, the zsh way is to implements all (suboptimal) solutions to the problem and let the user choose...

This is the solution I find most reasonable:

The persistent history is part of the persistent storage and initially empty.

A session starts with its per-session history inheriting all items of the persistent history.

Command lines are appended to both histories, after successful parsing and compilation and before execution. This implies that command lines with static errors do not get appended to the histories but those with runtime errors do.

This is also the way fish adopts, as well as zsh with the inc_append_history option enabled. The shortcomings of this approach are:

Command line order is not preserved in the persistent history when multiple sessions append to it in a interlaced manner, making it difficult to reproduce a series of command lines in a later session. This use case is covered by the record mode (#1) though.

Simultaneous sessions do not share their history, so the history cannot be (ab)used to pass command lines.


Make list_operations impl efficient

I left this comment a long time ago that we rediscovered it today:
https://github.com/fedimint/fedimint/blob/6249552fd55d599a4972d4c1e2bd8028e8c75b4b/fedimint-client/src/oplog.rs#L71-L78
The pagination of operation listing is horribly broken and requires a rewrite. Luckily, the second point is now possible after @dpc implemented find_by_range in https://github.com/fedimint/fedimint/pull/6005

From deep dive (@dpc): maybe we can change the data model to make querying n entries afyer a given entry easier. Basically make the key and auto-incrementing integer.

@elsirion After looking a bit longer into it:
We can quickly get and cache in the memory the timestamp of the first entry in the oplog to bound the search.
Afterwards we can just fetch using forward range, e.g. last_ts-period..=last_ts, filter and until we have limit. By avoiding iterating backwards, we should get much better performance anyway. The period could be proportional  period = expect_avg * limit.


Unable to drag and drop from Explorer to browser window

Version: 1.47.3 (system setup)
Commit: 91899dcef7b8110878ea59626991a18c8a6a1b3e
Date: 2020-07-23T13:12:49.994Z
Electron: 7.3.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.19041
Steps to Reproduce:

Open https://www.dragdrop.com/test/ (applies to other drag and drop capable sites such as Moodle.org deployments)
Open VSCode
Open a folder in VSCode Explorer
Drag file from Explorer to drop area on the website in your favorite browser

Does this issue occur when all extensions are disabled?: Yes
Expected: File upload box appears
Actual: Nothing happens upon releasing file
When using Windows Explorer, actual matches expected but not via VSCode Explorer. Reproducible on latest Chrome and Firefox.

Seems like a dup of https://github.com/microsoft/vscode/issues/91132


Backport Altering - cluster-altering app shows error after upgrading Rancher

Backport https://github.com/rancher/rancher/issues/21323

Failed to validate the bug fix.
Steps:

run Rancher: v2.2.4 container
as admin, enable Github auth
log in as Github user user1
add the following three clusters: DO single-node, DO 3-node, and GKE
adds cluster notifier and cluster alerting for all three clusters
upgrade Rancher to v2.2.5-rc9

Results:

in the clusters DO single-node and GKE, the app cluster-alerting and monitoring-operator get upgraded successfully, meaning there is only 1 workload left under the app cluster-alerting, and the altering feature is functional
in the cluster DO 3-node, the app cluster-alerting does NOT get upgraded, meaning there are still 2 workloads under the app  cluster-alerting, but the cluster altering still works
and Rancher's log shows

2019/07/08 20:56:00 [ERROR] ProjectController c-44pq6/p-jmpkk [system-image-upgrade-controller] failed with : upgrade system service alerting failed, cluster c-44pq6 not ready
2019/07/08 20:56:00 [ERROR] ProjectController c-44pq6/p-scrx7 [system-image-upgrade-controller] failed with : upgrade system service alerting failed, cluster c-44pq6 not ready

More Info 1

adding a new single-node cluster and a new 3-node cluster in the same setup and enabling the cluster altering fails
Rancher shows the following errors

Failed to ensure monitoring project name: failed to move Namespace cattle-prometheus into a Project: Operation cannot be fulfilled on namespaces "cattle-prometheus": the object has been modified; please apply your changes to the latest version and try again

Rancher's log shows

2019/07/08 21:31:58 [ERROR] ClusterAlertGroupController c-28fpf/cag-8cwmg [cluster-alert-group-deployer] failed with : failed to get Alertmanager Deployment information, statefulsets.apps "alertmanager-cluster-alerting" not found, [cluster-alert-group-controller] failed with : Failed to get service for alertmanager, service "cattle-prometheus/alertmanager-operated" not found
2019/07/08 21:32:00 [ERROR] ClusterAlertRuleController c-28fpf/car-8fw8v [cluster-alert-rule-deployer] failed with : failed to get Alertmanager Deployment information, statefulsets.apps "alertmanager-cluster-alerting" not found, [cluster-alert-rule-controller] failed with : Failed to get service for alertmanager, service "cattle-prometheus/alertmanager-operated" not found
2019/07/08 21:32:04 [ERROR] ClusterAlertGroupController c-28fpf/cag-8cwmg [cluster-alert-group-deployer] failed with : failed to get Alertmanager Deployment information, statefulsets.apps "alertmanager-cluster-alerting" not found, [cluster-alert-group-controller] failed with : Failed to get service for alertmanager, service "cattle-prometheus/alertmanager-operated" not found

More Info 2

tried the same steps in a fresh-installed Rancher v2.2.5-rc9 setup and the cluster altering works with no issues
tried the same steps in a fresh-installed Rancher v2.2.5-rc8 setup and the cluster altering works with no issues

Hi, the original issue https://github.com/rancher/rancher/issues/21323
Problem: Upgraded the rancher server, even the cluster is not ready but the cluster-alerting app continue to upgrade,  then get error waiting for cluster agent to connect
Solution: Check cluster status, only upgrade when the cluster status is ready, if not ready will throw error upgrade system service alerting failed, cluster c-44pq6 not ready, then rancher will retry. So in the first DO 3-node you see the log [system-image-upgrade-controller] failed with : upgrade system service alerting failed, cluster c-44pq6 not ready. This error should not happen after the cluster is ready and retry upgrade, the upgrade should be ok. Whether the cluster-alerting work after a while(auto error retry happened)?
For the Update 1 above: Because we don't release new charts to fix this two operators issue, but fixed by update the app's, so it still has 2 workloads if you directly upgrade the app cluster-alerting in the UI, it's expected now.
Others error may not be related to this PR, but I will also try to reproduce, thank you

@aiwantaozi   , once we see this error in the logs when cluster alerting upgrade was attempted and it fails , [system-image-upgrade-controller] failed with : upgrade system service alerting failed, cluster c-44pq6 not ready , do you expect the upgrade to be attempted again and succeed at some point ?
This never happened . The  the app cluster-alerting does NOT get upgraded, meaning there are still 2 workloads under the app cluster-alerting.
For the Update 1 above: Because we don't release new charts to fix this two operators issue, but fixed by update the app's, so it still has 2 workloads if you directly upgrade the app cluster-alerting in the UI, it's expected now. ==> There was no attempt made to update "cluster-alerting"  the app from UI .
"adding a new single-node cluster and a new 3-node cluster in the same setup and enabling the cluster altering fails" ==> Is there any chance that the earlier attempt to auto upgrade cluster alert being prevented( because of cluster state not being "active")  result in enabling alerts in other cluster having a problem ?

Find a history problem will cause some clusters upgrade system services failed when there are multiple clusters, it's included since v2.1.0.
Root cause:
this cause by only one alert/logging/pipeline upgradeService was inited, when there are multiple clusters, the former clusterName will be overwritten by the laster one, so only one cluster's system service is upgraded success.
Steps to reproduce:
run Rancher: v2.2.4 container
add the following three clusters: DO single-node, DO 3-node
adds cluster notifier and cluster alerting for all three clusters
upgrade Rancher to v2.2.5-rc9
only one cluster upgrade success

Please create another issue to check More Info 1 section. It’s a separate issue.

The decision was made to not put this fix to 2.2.5 due to a chance of regressions. Will be fixed in 2.3

Please create another issue to track issues in More Info 1 section. It’s a separate issue.

it is tracked here: https://github.com/rancher/rancher/issues/21399

From @loganhz
If you hit this issue in 2.2.4 or 2.2.5, please upgrade the cluster-alerting app and add operator.enabled=false answer manually to workaround it.
It will get fixed in 2.3.
FYI, when you hit this issue only the state of the cluster app is in red. But alerting feature is still functional in your cluster.


Feature Request: Solarized Dark

Would it be possible to add Solarized Dark as a dark theme in the options?

I don't plan to do so, but you can give it a go by overwriting the custom properties. Let me know if you need help with that.

If you have a PR that adds a single theme that I could reference, I should be able to throw together a PR to add the theme.


Setup storekitMode blocks debugger

Description
When we execute
setup({ storekitMode:  <store_kit_mode> });
We no longer able to use Debugger in debug mode.
Expected Behavior
When setting storekit mode, debug is not broken
Screenshots

Environment:

react-native-iap: 12.4.8
react-native: 0.69.7
Platforms (iOS, Android, emulator, simulator, device): iOS 16.1 simulator
React Native Debugger: 0.13.0

To Reproduce
Steps to reproduce the behavior:

Enable debug mode in simulator/emulator
Open React Native Debugger/Chrome DevTools
Error 'Invariant Violation: Calling synchronous methods on native modules is not supported in Chrome.' is shown

I'm thinking this is related to the method used to see if Storekit2 is available 🤔

@professorkolik Have you tried any of these proposed solutions: https://stackoverflow.com/questions/61067004/invariant-violation-calling-synchronous-methods-on-native-modules-is-not-suppor ?

@andresesfm sure we did, and it does the job, but it's a hack, which is not ok. On of the possible solutions I do see is setting storekitMode through env variables, wdyt?

I meant not as a permanent solution but to know if you had tried something that worked

@andresesfm ah, sorry, yeah the stackoverflow solution works, but it's smth would be nice to avoid.

It's strange that here: https://stackoverflow.com/a/69849801/570612 they mentioned it was fixed on rn 0.66

I will close this issue, since, nobody else experiences it. Will raise a PR if I find proper solution

I am facing this issue as well (using v 12.10.5 with RN 0.70.9). Did you find a proper solution for this @professorkolik ?
Also, I didn't even find the option to configure StoreKit-mode in the official docs, just stumbled across it in this migration guide. I think the docs could use a little upgrade in this regard..

@c-goettert
My recommendation would be to drop ReactNativeDebugger and switch to Flipper 😄
To configure store kit just call
setup({ storekitMode: <store_kit_mode> }); in your index file


How to use?

Hi!
First of all, thanks for the effort on this open-source project! :)
I'm having some trouble getting it to work though - I'm trying to use this as a skeleton for a new plugin.
However, when running wpppb-init, it asks for WordPress core tests directory. I don't intend to contribute to WP Core. Did I understand something wrong about the purpose of this project?
Thanks!!

Hey @Luc45. I've been meaning to write some better docs, sorry I haven't made things clearer. The project is for testing plugins, however, it builds on top of the testing tools that WP core uses. Basically, WP core has built some custom WP-specific stuff that is useful for testing any WP-related code, whether core, plugin, theme, etc. So instead of reinventing the wheel, WPPPB just builds on top of some of the things that the WP core team has already built. That is why it asks for the core tests directory.
Here is an older tutorial that I wrote on plugin unit testing, which includes the WP tests set up step (although the later steps are now replaced by WPPPB). However, in more recent years, I have switched to using VVV to set this up, since it includes the WP develop repo (which has the core tests directory in it). Even if you aren't planing to contribute to core (which is probably bound to happen anyway, since you'll likely find some bugs as you build anything complex on top of WP), I'd recommend getting VVV set up if you haven't already. It is very useful in plugin development. Then, once you have VVV, you can point WPPPB to the tests directory included with it.


update to work with K8up 1.0+

Deploy CRD's
Refactor to expose all Helm Values

Solves #17

Checklist

[x] Keep pull requests small so they can be easily reviewed.
[x] Update the documentation.
[x] Update the ./CHANGELOG.md.
[x] Link this PR to related issues.

Please replace inv.parameters.customer.name with inv.parameters.cluster.tenant in to close #4
https://github.com/projectsyn/component-backup-k8up/blob/upgrade_v1_0_0/lib/backup-k8up.libjsonnet#L41

@srueg please have a look at https://github.com/projectsyn/component-backup-k8up/pull/20/commits/8897df9edf145906cfc44a70008c9587b8e1b67a, not sure if I got the right ones (grep -r customer)


this plugin can not support style grammar in .vue file while the idea version is 2016.2 ?

when i coding at a .vue file, there is no code hinting at the style block. And the style scoped can not be identified.
this issue only happen in idea 2016.2 version, it does work well in idea 2016.1 version

+1 please fix this!


AttributeError: 'VAE' object has no attribute 'clone'

Python 3.10.6 (tags/v3.10.6:9c7b4bd, Aug  1 2022, 21:53:49) [MSC v.1932 64 bit (AMD64)]
Version: f0.0.14v1.8.0rc-latest-184-g43c9e3b5
Commit hash: 43c9e3b5ce1642073c7a9684e36b45489eeb4a49
Launching Web UI with arguments:
Total VRAM 24564 MB, total RAM 16174 MB
Set vram state to: NORMAL_VRAM
Device: cuda:0 NVIDIA GeForce RTX 4090 : native
VAE dtype: torch.bfloat16
Using pytorch cross attention
ControlNet preprocessor location: D:\BaiduNetdiskDownload\webui_forge_cu121_torch21\webui\models\ControlNetPreprocessor
Loading weights [f99f3dec38] from D:\BaiduNetdiskDownload\webui_forge_cu121_torch21\webui\models\Stable-diffusion\realisticStockPhoto_v20.safetensors
2024-03-03 13:36:14,199 - ControlNet - INFO - ControlNet UI callback registered.
Running on local URL:  http://<IP_ADDRESS>:7860
To create a public link, set share=True in launch().
Startup time: 20.7s (prepare environment: 5.5s, import torch: 5.2s, import gradio: 1.6s, setup paths: 1.2s, initialize shared: 0.2s, other imports: 1.0s, load scripts: 3.1s, create ui: 0.8s, gradio launch: 1.8s).
model_type EPS
UNet ADM Dimension 2816
Using pytorch attention in VAE
Working with z of shape (1, 4, 32, 32) = 4096 dimensions.
Using pytorch attention in VAE
extra {'cond_stage_model.clip_g.transformer.text_model.embeddings.position_ids', 'cond_stage_model.clip_l.logit_scale', 'cond_stage_model.clip_l.text_projection'}
loaded straight to GPU
To load target model SDXL
Begin to load 1 model
To load target model SDXLClipModel
Begin to load 1 model
Moving model(s) has taken 1.41 seconds
Model loaded in 16.3s (load weights from disk: 1.0s, forge instantiate config: 1.5s, forge load real models: 11.2s, calculate empty prompt: 2.5s).
[Layer Diffusion] LayerMethod.FG_ONLY_ATTN
*** Error running process_before_every_sampling: D:\BaiduNetdiskDownload\webui_forge_cu121_torch21\webui\extensions\sd-forge-layerdiffusion\scripts\forge_layerdiffusion.py
Traceback (most recent call last):
File "D:\BaiduNetdiskDownload\webui_forge_cu121_torch21\webui\modules\scripts.py", line 835, in process_before_every_sampling
script.process_before_every_sampling(p, *script_args, **kwargs)
File "D:\BaiduNetdiskDownload\webui_forge_cu121_torch21\webui\extensions\sd-forge-layerdiffusion\scripts\forge_layerdiffusion.py", line 130, in process_before_every_sampling
vae = p.sd_model.forge_objects.vae.clone()
AttributeError: 'VAE' object has no attribute 'clone'

i had the same problem.

Update "Forge" to the latest

Update "Forge" to the latest

That fixes it!

I'm having the same problem. Everything is updated that I can tell. Any ideas?
*** Error running process_before_every_sampling: D:\Ai\stable-diffusion-webui-forge-main\extensions\sd-forge-layerdiffusion\scripts\forge_layerdiffusion.py
Traceback (most recent call last):
File "D:\Ai\stable-diffusion-webui-forge-main\modules\scripts.py", line 835, in process_before_every_sampling
script.process_before_every_sampling(p, *script_args, **kwargs)
File "D:\Ai\stable-diffusion-webui-forge-main\extensions\sd-forge-layerdiffusion\scripts\forge_layerdiffusion.py", line 130, in process_before_every_sampling
vae = p.sd_model.forge_objects.vae.clone()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'VAE' object has no attribute 'clone'

i am having this issue as well. I think it is the checkpoint model being used. For instance, I have two Flux Dev models. I think flux dev fp8 works with checkpoint loader, the flux dev1 works for unet diffusor node. if that makes sense.


PRIO - Android Wallet Ticketing - for NOK status the injured rule should be displayed like in iOS App

When validating a booking code against certificate the injured rule should be displayed when status NOK.

Actual behaviour:
Validating this 1/2 vaccination certificate against DEV-TEST validation service (https://4b49927aadc0653d.dcc-validation.eu/) the new fixed behaviour shows the correct NOK (red) status in the wallet app but it does not show the injured rule.

Expected behaviour:
Please add the injured rule like it is in iOS:

!Please note the acc and test validation service has the old behaviour and the status is app i shown as OPEN (yellow icon). So you have to check and test against DEV-TEST validation service

retested successfully with 1.2.8.-acc(35)


List data-sets that are currently downloaded in our cache

This should be part of a find-dataset command. Connected with whatever happens for #108... So we can view the whole world with one unified view.