Not loading song on Safari

I tried loading "https://m.soundcloud.com/nba-youngboy/youngboy-never-broke-again-put" in Safari on my IPhone and it's not working.
My name is Pedro Pablo Camellon. I just discovered the project and want to help. I know a little about UI/UX design, HTML, CSS, and JavaScript. I'd be really glad to contribute to your project.

These is what I get on the console of Edge v103 on Windows:
Mixed Content:
The page at 'https://www.michaelbromley.co.uk/experiments/soundcloud-vis/?#muse/undisclosed-desires' was loaded over HTTPS, but requested an insecure script 'http://connect.soundcloud.com/sdk.js'. This request has been blocked; the content must be served over HTTPS.
app.js:455

Uncaught ReferenceError: SC is not defined
  at SoundcloudLoader.loadStream (app.js:455:9)
  at loadAndUpdate (app.js:604:16)
  at init (app.js:626:9)


Cannot connect a Docker container to another Docker network

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
I am in a situation where I would like to have a Docker container in two different networks: a Cilium network, and another one.
Steps to Reproduce

Create the Cilium network: docker network create --driver cilium --ipam-driver cilium cilium-net
Create the other Docker network: docker network create other-net
Create an application on the other network: docker run --rm --net other-net cilium/demo-httpd
Connect the container to the Cilium network: docker network connect cilium-net $container_id

We face the following error:
Error response from daemon: failed to add static route <IP_ADDRESS>/0: file exists

If we first create the application in the Cilium network, then connect it to the other network, the error message is different:
Error response from daemon: failed to set gateway while updating gateway: file exists

The following piece of code seems relevant to this issue:
https://github.com/cilium/cilium/blob/36cb0eed03c8bc6576f3fd33a94440c70ae18974/plugins/cilium-docker/driver/driver.go#L496-L505
https://github.com/cilium/cilium/blob/1.13.3/plugins/cilium-docker/driver/driver.go#L496-L505
Cilium Version
vagrant@agent-1:~$ sudo cilium version
Client: 1.13.2 8cb94c70 2023-04-17T23:19:21+02:00 go version go1.19.8 linux/amd64
Daemon: 1.13.2 8cb94c70 2023-04-17T23:19:21+02:00 go version go1.19.8 linux/amd64

Kernel Version
Linux agent-1 5.4.0-150-generic #167-Ubuntu SMP Mon May 15 17:35:05 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Kubernetes Version
n/a
Running without Kubernetes
Sysdump
vagrant@agent-1:~$ sudo cilium-cli sysdump
🔍 Collecting sysdump with cilium-cli version: v0.14.6, args: [sysdump]
failed to create sysdump collector: failed to detect Cilium namespace: Get "http://localhost:8080/api/v1/namespaces/kube-system": dial tcp <IP_ADDRESS>:8080: connect: connection refused

which makes sense as we don't use Kubernetes.
Relevant log output
cilium-agent          | level=info msg="Create endpoint request" addressing="&{<IP_ADDRESS>/32   }" containerID= datapathConfiguration="<nil>" interface=lxc0b8a340f050b k8sPodName=/ labels="[]" subsys=daemon sync-build=true
cilium-agent          | level=info msg="New endpoint" containerID= datapathPolicyRevision=0 desiredPolicyRevision=0 endpointID=2294 ipv4= ipv6= k8sPodName=/ subsys=endpoint
cilium-agent          | level=info msg="Resolving identity labels (blocking)" containerID= datapathPolicyRevision=0 desiredPolicyRevision=0 endpointID=2294 identityLabels="reserved:init" ipv4= ipv6= k8sPodName=/ subsys=endpoint
cilium-agent          | level=info msg="Identity of endpoint changed" containerID= datapathPolicyRevision=0 desiredPolicyRevision=0 endpointID=2294 identity=5 identityLabels="reserved:init" ipv4= ipv6= k8sPodName=/ oldIdentity="no identity" subsys=endpoint
cilium-agent          | level=info msg="Waiting for endpoint to be generated" containerID= datapathPolicyRevision=0 desiredPolicyRevision=0 endpointID=2294 identity=5 ipv4= ipv6= k8sPodName=/ subsys=endpoint
cilium-agent          | level=info msg="Rewrote endpoint BPF program" containerID= datapathPolicyRevision=0 desiredPolicyRevision=1 endpointID=2294 identity=5 ipv4= ipv6= k8sPodName=/ subsys=endpoint
cilium-agent          | level=info msg="Successful endpoint creation" containerID= datapathPolicyRevision=1 desiredPolicyRevision=1 endpointID=2294 identity=5 ipv4= ipv6= k8sPodName=/ subsys=daemon
cilium-agent          | level=info msg="Delete endpoint request" endpointID=2294 ipv4=<IP_ADDRESS> ipv6= k8sNamespace= k8sPodName= subsys=daemon
cilium-agent          | level=info msg="Removed endpoint" containerID= datapathPolicyRevision=1 desiredPolicyRevision=1 endpointID=2294 identity=5 ipv4= ipv6= k8sPodName=/ subsys=endpoint

Anything else?
I can see someone else faced the same issue a couple of years ago (#13161), with no real answer.
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi @EtienneM , thanks for the report.
Unfortunately, the cilium-docker plugin is no longer maintained by the Cilium project and is scheduled to be removed. You're welcome to pick up the code and tweak it to your own use based on the open source license, but it's decreasingly likely that any Cilium developers will be able to assist with this.
The cilium-cni plugin may provide a better alternative as it is still actively maintained, but be aware that the most common deployment platform for Cilium is on top of Kubernetes. Your mileage may vary when deploying Cilium on other platforms.
Closing "won't fix".

Thanks for your prompt answer which includes valuable information for us :)
We will have a look at the CNI plugin to replace the Docker one.


Cannot access extensions search result using the keyboard

VSCode Version: insiders 7/1
OS Version: Windows

Steps to Reproduce:

Open Extensions
Press Tab key
-> Extensions search results get focus, but I can not get to the individual extensions using the arrow keys or the tab key.

I filed a similar bug that the list widget needs to be on par with tree widget in terms of these accessibility features.

Yes, closing as duplicate of #8621


Improve username behavior

Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[x] Appropriate changes to README are included in PR

OK to accept


switch back to runc

coredns doesn't start up with CRI-O, though it can start up with containerd
...
    containerStatuses:
    - image: coredns/coredns:1.6.9
      imageID: ""
      lastState: {}
      name: coredns
      ready: false
      restartCount: 0
      started: false
      state:
        waiting:
          message: |
            container create failed: time="2020-09-02T19:26:04+09:00" level=warning msg="exit status 1"
            time="2020-09-02T19:26:04+09:00" level=error msg="container_linux.go:370: starting container process caused: process_linux.go:459: container init caused: rootfs_linux.go:60: mounting \"/run/user/1001/usernetes/containers/storage/overlay-containers/dad49321dc8b57d4bc65665972bfaccf3a6be9416ed05c0a02cdc98be1ed603b/userdata/hostname\" to rootfs at \"/home/suda/.local/share/usernetes/containers/storage/overlay/9986c016a134d19deffa4793dc57d4036e1362605658260212625cd1baa8ddec/merged/etc/hostname\" caused: operation not permitted"
          reason: CreateContainerError

cc @giuseppe


Suppress anycode in the presence of rust-analyzer

fyi @connor4312
Re: https://github.com/microsoft/vscode-cli/issues/423#issuecomment-1229014615

Oh, this is hardcoded... that explains it 🤦


Sainlogic WS3500 (WS2900_V2.01.08) Data Issue

ecowitt2mqtt version
Latest Version, pulled via pip 20201212
Describe the bug
Configured Sainlogic WS3500 via WSView as described.
Commandline used
 ecowitt2mqtt --mqtt-broker=homeassistant.fritz.box --mqtt-username=tasmota --mqtt-password=xxx --hass-discovery --unit-system metric -l DEBUG

Data is sent by the station and received by ecowitt2mqtt.
Debug output looks as follows.
DEBUG:ecowitt2mqtt:Using arguments: Namespace(endpoint='/data/report', hass_discovery=True, hass_discovery_prefix=None, log_level='DEBUG', mqtt_broker='homeassistant.fritz.box', mqtt_password='tasmota', mqtt_port=1883, mqtt_topic=None, mqtt_username='tasmota', port=8080, unit_system='metric')
DEBUG:asyncio:Using selector: EpollSelector
======== Running on http://<IP_ADDRESS>:8080 ========
(Press CTRL+C to quit)

Data is received and looks as follows
DEBUG:ecowitt2mqtt:Received data from Ecowitt device: {'PASSKEY': '641BC45267D8313205E7DC98CA552E6C', 'stationtype': 'EasyWeatherV1.5.6', 'dateutc': '2020-12-12 16:58:52', 'tempinf': '70.2', 'humidityin': '49', 'baromrelin': '29.616', 'baromabsin': '29.173', 'tempf': '41.7', 'humidity': '97', 'winddir': '313', 'windspeedmph': '0.0', 'windgustmph': '0.0', 'maxdailygust': '1.1', 'rainratein': '0.000', 'eventrainin': '0.213', 'hourlyrainin': '0.000', 'dailyrainin': '0.110', 'weeklyrainin': '0.453', 'monthlyrainin': '1.362', 'totalrainin': '22.051', 'solarradiation': '0.00', 'uv': '0', 'wh65batt': '0', 'freq': '868M', 'model': 'WS2900_V2.01.08'}

Error based on received data looks as follows
ERROR:aiohttp.server:Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/dist-packages/aiohttp/web_protocol.py", line 422, in _handle_request
    resp = await self._request_handler(request)
  File "/usr/local/lib/python3.7/dist-packages/aiohttp/web_app.py", line 499, in _handle
    resp = await handler(request)
  File "/usr/local/lib/python3.7/dist-packages/ecowitt2mqtt/mqtt.py", line 85, in async_publish_payload
    data = data_processor.generate_data()
  File "/usr/local/lib/python3.7/dist-packages/ecowitt2mqtt/data.py", line 326, in generate_data
    pressure_data = self._generate_pressure_data()
  File "/usr/local/lib/python3.7/dist-packages/ecowitt2mqtt/data.py", line 208, in _generate_pressure_data
    data[new_key] = round(inhg_to_hpa(int(self._data[original_key])), 1)
ValueError: invalid literal for int() with base 10: '29.173'
INFO:aiohttp.access:<IP_ADDRESS> [12/Dec/2020:17:02:05 +0000] "POST /data/report HTTP/1.1" 500 244 "-" "-"```

**To Reproduce**
Steps to reproduce the behavior:
As described above with a Sainlogic WS3500 which seems to be a WS2900_V2.01.08 under to hood.

Everything seems to work fine but it seems like that the Station sends data as Strings but ecowitt2mqtt expects values sent as numbers (?). Maybe an issue with the station not sending the correct format ?

I changed the following lines in data.py and it works now. I am sure there is a better way to handle this.
208:         data[new_key] = round(inhg_to_hpa(int(float(self._data[original_key]))), 1)
234:         data[new_key] = round(in_to_mm(int(float(self._data[original_key]))), 1)

Thanks, @MarkThielen!

Thanks, @MarkThielen!

Thanks @bachya for building this, great stuff !!


Jenkinsfile simplification

This patch tries to keep the original behavior, but simplifies the Jenkinsfile by

scheduling runs only for develop branch
guarding develop branch from jenkins.branch.BranchIndexingCause by aborting such jobs
making sure, that we descent the list of previous jobs to find the closes non-aborted job

This allowed for simplification of the when{} statements.

bors merge

bors merge

bors retry

bors retry


Player side switch to left?

Describe your problem here.
I have searched for a way to make the player's ui appear on the left and vice versa, however no clear solution was found. For both the arrows and the side of which the icons are on the healthbar, I would like to swap them. How is this done? I've seen both of these in mods before, so I am curious how to do it myself.
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

okok so i just figured out the arrow part but im still stumped on how to switch the health bar

		iconP1Modifier = getProperty('healthBar.x') + ((getProperty('healthBar.width') * getProperty('healthBar.percent') * 0.01) + (150 * getProperty('iconP1.scale.x') - 150) / 2 - 26) 		iconP2Modifier = getProperty('healthBar.x') + ((getProperty('healthBar.width') * getProperty('healthBar.percent') * 0.01) - (150 * getProperty('iconP2.scale.x')) / 2 - 26 * 2) 		setProperty('iconP1.x', iconP1Modifier - 90) 		setProperty('iconP1.origin.x', 240) 		setProperty('iconP1.flipX', true) 		setProperty('iconP2.x', iconP2Modifier + 90) 		setProperty('iconP2.origin.x', - 100) 		setProperty('iconP2.flipX', true) 		setProperty('healthBar.flipX', true)


Simplify a - a to 0

What the rule should do:
Simplify a-a to 0
Example of things the rule would report:
item.quality - item.quality
--> 0

Example of things the rule would not report:
item.quality - (.quality item)

item.quality - (.quality item)

Why would you not want this be reported? Except for the fact that it can be hard to detect (which may actually not be all that complicated).
I also think that we could report the following
item.quality + (-item.quality)
--> 0

And maybe we could also simplify things like (more work though)
item.quality + 3 - item.quality + n
--> 3 + n

though I don't know if this would create for annoyances in how you want to write your code.

It would be reported after the .quality item -> item.quality transformation I guess?
a + (-a) should be fine
a + 3 - a + n would be more work
While we're at it, does it make sense to simplify
a) (a + 1) + 1
b) `a + 1 + 1
?

I don't think we have the .quality item -> item.quality transformation :thinking:
For a) and b), do you mean to transform them to a + 2? I would say no, because that can be related to how you want to write code.
The example I usually have in mind is something like:
Process.sleep (3 * 60 * 1000)

Abole it becomes easy to see how long to wait: 1000 milliseconds is one second, times 60 is one minute, times 3 is 3 minutes.
We could simplify it to
Process.sleep 180000

but that would be a lot harder to read and feel like a much more arbitrary/magic value compared to the broken-down version we had before.

Agreed!

@ future implementor: As with #58, these simplifications aren't always correct with Float
> (0 / 0) - (0 / 0)
NaN : Float
> (1 / 0) - (1 / 0)
NaN : Float
> -(1 / 0) - -(1 / 0)
NaN : Float

I'm closing this in favor of creating https://github.com/miniBill/elm-review-optimize

I'll re-open this one, because I can still see this one being valuable in Simplify :)

Considering what Lue said, I'm guessing that Simplify would have the rule but not the simplification, whereas Optimize could have both?

I don't know if I've written about it somewhere, but I think we'll introduce a configuration option to avoid/enable simplifications on potential NaN. Basically, if the user says "I never willingly work with NaN", then we enable the errors + fixes for things like a - a --> 0 or a == a --> True. If they say the opposite, then we don't.
I think if you enable these changes anyway, then you're (more) at a risk of changing behavior with Optimize.

I like it!


UI: Additional hidden menu item for battery calibration

Thank you :)
I've added it with a couple of changes .. limited adjustment range and restore original setting if user backs out of the menu setting with the exit key.

Want to add your fagci spectrum module next ;)

l setting if user backs out of the menu setting with the exit key.

It already did work like that, I've checked

Want to add your fagci spectrum module next ;)

I already have working code if you want

You have added the old implementation from my repo
This pull request is different it adds new hidden menu. It is much more clear for the user.

oh sorry, hold on then

Corrected the battery menu now.


Version flag

$ hostctl -v || hostctl --version
hostctl 0.10.0

or add it to the output of the help command?

implemented on v0.10.2. :+1:

@guumaster
$ hostctl -v
hostctl version dev

dev as a version is not helpful, because it'll be dev all the time, it seems. (this was true of 0.10.1 and is true now of 0.10.2.)

@guumaster Yes, I'm using the AUR: yay -S hostctl. If you wanna supply a hostctl-bin package, too, I would use it. Less carbon footprint.

@BarbUk do you know how to pass -ldflags parameter to PKGBUILD so the build script add the proper version to the binary?

the pkgbuild is already building with -ldflags:
build() {
  cd $pkgname-$pkgver
  go build \
    -trimpath \
    -ldflags "-extldflags $LDFLAGS" \
    -o $pkgname .
}

How do you pass the version to go build ?

-X github.com/guumaster/hostctl/cmd.version=$pkgver

Made the change in the pkgbuild.
❯ hostctl -v
hostctl version 1.0.2

hostctl -v still outputs hostctl version dev on my end (installed through the AUR).
highlighted line illustrates that I have a feature only available on 1.0.8 https://github.com/guumaster/hostctl/releases/tag/v1.0.8

Ldflags need to be updated following 007b4154c19923e1c59a53ca8d6e2ad4d471de62.
The update is available in https://aur.archlinux.org/cgit/aur.git/commit/?h=hostctl&id=42f1eed07bba06554ffb4f73a3ea9871771ba920
I did not update pkgrel to not break the package release automation.
@smhmd, you can reinstall the package or wait for the next release.

@guumaster, your new commit break the version passed via ldflags.

I fixed the goreleaser yml and also just updated the PKGBUILD file, can you confirm it works on Arch?

yes:
$ hostctl -v
hostctl version 1.0.9


Transport messages

Both SMS and Email transport needs messages for different notification, currently we only have messages for the vote type.
Refs #40

Copying over sneak's comment here so it does not get lost:

These need to pull the user’s i18n language from prefs and should notify them in their chosen language. This is good for a first pass but we cannot assume user knowledge of English.

For wwwpoll this is obviously up to condenser to handle, for other transport types it gets more tricky - can we store the user's language preference alongside transport configuration and have condenser set it to the user's language upon first use?
Default is english, but condenser could easily change that on first usage, or condenser could have a "setup notifications" page and not allow notifications at all until the user visits it.

As for the different notification types, I have a set of templates for sendgrid (email), i'll create another issue to track importing that.
For both SMS and email, on the language issue, we'll need translations to support other languages - how quickly can we get translations?


Kivy-designer should ask whether or not to save the newly created project.

If I create a new project and make some edits or create some new files but close kivy-designer without saving the project somewhere, then KD won't show any warnings or ask something like this.
Your new project is not saved anywhere and all the work done will be lost,
would you like to save it? | Yes || No |

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/28921200-kivy-designer-should-ask-whether-or-not-to-save-the-newly-created-project?utm_campaign=plugin&utm_content=tracker%2F77147&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F77147&utm_medium=issues&utm_source=github).

@aron-bordin  I can fix it, if you like.

sure, go ahead :)

check: https://github.com/kivy/kivy-designer/pull/73/files
the on_request_close checks the self._curr_proj_changed variable
looks like that this variable is not being changed.


Creating User With Additional (custom) attribute

Laravel Version: #.#
Adldap2-Laravel Version: #.#
PHP Version: #.#

Description:
Steps To Reproduce:

Please use attribute handlers described here:
https://github.com/Adldap2/Adldap2-Laravel/blob/master/docs/auth/syncing.md#attribute-handlers

I have tried this:
'sync_attributes' => [
'name' => 'cn',
'user_level' => int(1),
],
But it did not work (although I do see user_level being added to the user insert!); but it breaks.
And I have tried this:
'sync_attributes' => [
'name' => 'cn',
App\Handlers\LdapAttributeHandler::class,
],
with this:
user_level = 1;
    }
}

That did not work either. I think perhaps I'm doing something incorrectly.

Also, try dd()'ing in your attribute handler, and then authenticate and see if it's properly being registered:
<?php

namespace App\Handlers;

use App\User as EloquentUser;
use Adldap\Models\User as LdapUser;

class LdapAttributeHandler
{
    /**
     * Synchronizes ldap attributes to the specified model.
     *
     * @param LdapUser     $ldapUser
     * @param EloquentUser $eloquentUser
     *
     * @return void
     */
    public function handle(LdapUser $ldapUser, EloquentUser $eloquentUser)
    {
        dd($eloquentUser);
        $eloquentUser->user_level = 1;
    }
}

Alright, I tried to dd() it, but it is still not working.
I think I'm probably putting the LdapAttributeHandler file in the wrong spot maybe? Currently it's in app directory.
I have:

    'sync_attributes' => [
        'name' => 'cn',
        App\Handlers\LdapAttributeHandler::class,
    ],

and

    public function handle(LdapUser $ldapUser, EloquentUser $eloquentUser)
    {
        dd($eloquentUser);
        $eloquentUser->user_level = 1;
    }

But it's not hitting the dd() - so I don't even think it's hitting the LdapAttributeHandler class.
My error message looks like:
Column not found: 1054 Unknown column '0' in 'field list' (SQL: insert into users (email, password, name, **0** (this should be the user_level), updated_at, created_at) values<EMAIL_ADDRESS>hashedpassword, me, (user level should be here but isn't) , 2017-04-20 13:24:44, 2017-04-20 13:24:44))

I think I'm probably putting the LdapAttributeHandler file in the wrong spot maybe? Currently it's in app directory.

Did you create the app/Handlers directory and insert the hanlder class inside? You have namespaced in as such, and it won't be autoloaded otherwise.

I created the directory 'Handlers' under 'app' and placed the class in there.
Same result unfortunately - same error message (no, there is no caching going on). Still not seeing the dd().

@stevebauman your link is broken

Hi @jlsjonas, here's the updated link:
https://github.com/Adldap2/Adldap2-Laravel/blob/master/docs/auth.md#syncing-attributes
This may change in the future. The best way to browse the docs is from the index tree on the home page:
https://github.com/Adldap2/Adldap2-Laravel


Upgrade to Netty 4.1.112.Final

Motivation:
Netty 4.1.112.Final is available and we should use it.
Modification:
Updated to Netty 4.1.112.Final
Result:
Up-to-date Netty version

Hey
Have you considered dependabot for this?

Yeah, going to integrate now. Painful to track manually.


Increasing intervals

I had once a digital picture frame from canon and it had a feature which I liked: when interacting with the frame (startup, new pictures, touch etc.) the intervals between picture changes were short, and with time grew longer. This way the frame was less disturbing when in the background and more active when you were sitting in front of it. I think it would be a great feature for this implementation, too.

Here is a first implementation in form of an addon:
Any comments?
How should I submit my code?
 * introduces quicker image changes after interactions and slows down with time
 * @param  {AddonBase inherited} interface   object to register and send events
 */

// import interval from config.json
var fs = require('fs');
var configfile = fs.readFileSync("./config/config.json", "utf8");
var config = JSON.parse(configfile);
var maxInterval = (config.interval) ? config.interval:45000;
const additionalChanges = (config.imageCount) ? config.imageCount:30;
var counter = 1;

const functionFlexIntervals = (interface) => {

  //interface.registerListener('newImage', (sender, type) => counter = 1);

  interface.registerListener('images-loaded', () => counter = 1);

  interface.registerListener('imageDeleted', () => counter = 1);

  interface.registerListener('paused', (status) => counter = 1);

  interface.registerListener('muted', (status) => counter = 1);

  interface.registerListener('recordStopped', () => counter = 1);

  interface.registerListener('unstarImage', index => counter = 1);

  interface.registerListener('starImage', index => counter = 1);

  interface.registerListener('changedActiveImage', index => {
        // introduce an additional picture change:
        if (counter < additionalChanges) {
		var additionalChange = Math.round(maxInterval*counter/additionalChanges);
                interface.logger.info("additional change in: " + additionalChange);
		setTimeout(() => { interface.sendEvent('next'); }, additionalChange);
		counter += 1;
	};
  });
};

/*************** DO NOT EDIT THE LINE BELOW ***************/
if (typeof module !== "undefined") {
  module.exports = functionFlexIntervals;
}```

Nice idea, exactly for these requirements the addon interface was implemented.
A few hints:
You do not need to read the configuration file itself. The configuration is provided by the addon interface and all keys have a valid value. So you can access the values directly.
For example:
//...

const functionFlexIntervals = (interface) => {
  var config;
  var counter = 1;

  interface.registerListener('teleFrame-ready', teleFrameObjects => {
    config = teleFrameObjects.config;
  });

//...

  interface.registerListener('changedActiveImage', index => {
    // introduce an additional picture change:
    if (counter < config.imageCount) {
      var additionalChange = Math.round(config.interval*counter/config.imageCount);
      interface.logger.info("additional change in: " + additionalChange);
      setTimeout(() => { interface.sendEvent('next'); }, additionalChange);
      counter += 1;
    };
  });

How should I submit my code?

Please create a repository for the addon yourself and we will link it on the Available TeleFrame addons - wiki page.

Cool!
Here you go:
https://github.com/call-me-matt/teleframe-flexintervals

It' s done.

Another little hint:
You can specify the events you want to listen to using an array if you want to do the same thing every time.
interface.registerListener([
  'images-loaded', 'imageDeleted', 'paused', 'muted',
  'recordStopped', 'unstarImage', 'starImage'
], index => counter = 1);

Thank you so much for your help.
I really like this addon-interface.
Thought about the description in the wiki, maybe "introduces quicker image changes which slow down with time" is a catchier description.
PS: You re-opened the issue?

I'd enjoy it.

Thought about the description in the wiki

You can edit the Wiki page yourself 😃

PS: You re-opened the issue?

Yes, because @LukeSkywalker92  has marked the extension as a enhancement and I also think it's a feature that is interesting for everyone. I am currently looking for an easy way to install addons that are interesting for everyone. There are some ideas already, but not yet fully realized.
So that the topic is not forgotten, I have reopened the issue.

is there a way to detect if a picture or video is shown?
(call-me-matt/teleframe-flexintervals#3)

I suppose you've noticed the problem with video playback time. It almost drove me crazy yesterday, too.
You can use interface.images[index].src to check for .mp4
These changes should solve the problem
@@ -68,13 +68,16 @@ const functionFlexIntervals = (interface) => {
     }
     const additionalChange = Math.max(minChangeTime, Math.round(config.interval*counter/config.imageCount));
     nextChangeTime = new Date().getTime() + additionalChange;
     // introduce an additional picture change:
     if (!isPaused && counter < config.imageCount) {
-      setChangeTimer(additionalChange);
+      // ignore videos because the duration is unknown
+      if (!interface.images[index].src.match(/\.mp4$/i)) {
+        setChangeTimer(additionalChange);
+      }
       counter += 1;
-    };
+    }
   });
 };

Great, thank you


Named sessions?

Any plans on adding named sessions? In order to allow to switch between groups of related files or folders.

No. Happy to review and riff on a PR though.
I really want to keep this plugin as a "Simple session management" one. That being said, if someone can add a new feature and keep it simple, I'll be happy to accept.


v0.29.0 ROADMAP

The purpose of this roadmap is to let anyone know about the different steps in the Meilisearch release.
Draft phase (weeks 1-4)
Start: 2022-06-13
End: 2022-07-11

[ ] Planification of the next release content (features, improvements, bug fixes). Meeting with the PM & and the core manager to discuss and agree on what we are going to put in the next release.
[ ] Presentation of the next release content to the core team. Discussions with the team that can lead to some corrections.
[ ] The PM writes specifications by organizes working groups and product squad works.
[ ] At the middle/end of the Draft phase, the PM and the core manager review together and agree a firm version of the next release plan. Nothing is strongly definitive, still needs to be validated by Guillaume.
[ ] The core manager shares the firm version of the next release plan on #ms-release (internal Slack). It’s for information at this stage, no team can start working since the specs are not fully available yet.
[ ] The PM provides the firm version of the specs, which means the implementation phase can begin.
[ ] The core manager opens issues (including an issue for the version update in the Cargo.toml files) to add them to the Milestones. Issues related to bugs could also be added to the Milestones.

Implementation phase (weeks 5-8)
Start: 2022-07-11
End: 2022-08-08

[ ] The core manager posts a summary of the release dates on #ms-releases (internal  Slack), links the milestones, and gives an over iew of the main features. This could interest other teams, especially DevRel.
[ ] At the beginning of the Implementation Phase, sync meeting with each manager of the open-source teams about the current implemented release. It’s an opportunity to remind where we need their review regarding the specs.
[ ] Core team implements the planned content of the release according to the specifications. The code changes are merged into the main branch.
[ ] Docs team organizes their preparation: identify the effect of new changes on the documentation, discussion phase and planning.
[ ] According to the feedback we receive from the devs, changes may be made to feature specs
[ ] At the end of the Implementation Phase, the core manager writes the changelog for the release
[ ] Docs team reviews the changelogs.
[ ] Integration team opens a central issue on integration-guides gathering all the release changes that will impact the integration team and how they will handle them
[ ] Integration team opens draft branches in every repository to make the integrations up-to-date with the new version of Meilisearch.
[ ] At the end of the Implementation Phase, all the issues related to the Milestone are solved, meaning every implementation has been merged into main. If something differs from the original plan, the core manager should inform the other teams on #ms-releases (internal Slack).

Pre-release phase (weeks 9-12)
Start: 2022-08-08
End: 2022-09-05

[ ] Core team release the first RC (release candidate) using the prepared changelogs.
[ ] At the beginning of the Pre-release Phase, sync meeting with each manager of the open-source teams about the coming release. It’s an opportunity to plan and identify the parts where sync will be needed between the different teams during the Pre-release Phase.
[ ] Integrations team updates the SDKs and their integrations according to the new release.
[ ] Docs team updated the documentation to reflect the changes of the new release.
[ ] Optional - The mini-dashboard might also need an update involving the integration team to release beta version of meilisearch-js and/or instant-meilisearch.
[ ] According to feedback and bug reports from the integrations and the docs teams, the core team modify the code and fix bugs as soon as possible. Other RCs are released if necessary.
[ ]  DevRel team write a blog post “What’s new in v0.X.Y?”.
[ ] The core manager, the PM, and the docs team review the blog post.
[ ] Integration team confirms the latest RC (so at the end of the Pre-release Phase) works with their DevOps tools

Release phase (week 13)
Release date: 2022-09-05

[ ] Core team releases the official version and lets the other teams know when the binary and the Docker images are available on #ms-releases (internal Slack).
[ ] New documentation deployment by the docs team
[ ] Release of all the updated integrations by the integration team
[ ] DevRel team takes care of external communications (blog, socials, etc) but might want for the documentation and the assets of the release to be ready (including Docker image)
[ ] Bring changes from stable branch of Meilisearch into the main branch
[ ] Close every part relating to the release in the product repository: discussions, issues, PRs of the specs are merged...
[ ] Close the release Milestones
[ ] Close the discussions in the product repo.

@meilisearch/docs-team @meilisearch/devrel-team @meilisearch/integration-team @meilisearch/core-team FYI 🤟

Hell everyone, due to the summer Holiday at Meili, and according to our internal discussions, I've updated the date of this sprint

start of the sprint: still 11th July
end of the implementation, so beginning of the pre-release: 29th August instead of 8th August (7 weeks instead 4 weeks)
end of the pre-release, so the official release date: 26th September instead of 5th September (still 4 weeks)

Thanks for your understanding, and have nice holidays!

Sorry, some date changes again! Due to an internal seminary at Meili, we chose to increase the pre-release phase.
The ore-release phase still starts on 29th August but will end on 3rd October, meaning the official v0.30.0 release will be on the 3rd of October
I updated this issue description accordingly 😊

Released done!


Doing certain actions resets zoom

Performing certain actions in the game resets your camera zoom to default. These actions include opening the bank, using the 'exchange' option of the tool leprechaun, using grimy herbs on the tool leprechaun, changing spellbook on the occult altar and probably many more.

Can confirm this happened also.

Fixed in master


Special counter plugin counting "absolute unit" reflect damage

I was doing Corp on SRL and noticed that the spec counter plugin would fail to track my spec damage if my absolute unit effect would recoil damage at the moment I used the BGS spec. I then tested with Arclight and the same would happen, the plugin would register the recoil damage as the spec hit.
One thing worth pointing is that the "Damage" counter at Corp would properly pickup weapon damage only and ignore the recoil damage.

Duplicate of #12008
btw, why the corp plugin works fine is due to the vanilla corp damage overlay; we take the data used from that for your damage.


Error occurs when configure client auth

To Reproduce
From @evfurman:
I got authentication configured on the brokers.
  <meta http-equiv="Content-Type" content="text/html;charset=utf-8"/> <title>Error 401 Authentication required</title>
HTTP ERROR 401 Authentication required

URI:	/admin/v2/brokers/health

STATUS:	401

MESSAGE:	Authentication required

SERVLET:	org.glassfish.jersey.servlet.ServletContainer-3051e0b2

Powered by Jetty:// 9.4.33.v20201020

However, when I try to produce with the pulsar-perf client, I get the following error:
22:30:33.866 [pulsar-client-io-2-1] INFO  org.apache.pulsar.client.impl.ConnectionPool - [[id: 0x1327459b, L:/<IP_ADDRESS>:59344 - R:pulsar-pluster-01.qa.corp.mparticle.com/<IP_ADDRESS>:6651]] Connected to server
22:30:33.883 [pulsar-client-io-2-1] WARN  org.apache.pulsar.client.impl.ClientCnx - [id: 0x1327459b, L:/<IP_ADDRESS>:59344 - R:pulsar-pluster-01.qa.corp.mparticle.com/<IP_ADDRESS>:6651] Received error from server: Unable to authenticate
22:30:33.883 [pulsar-client-io-2-1] WARN  org.apache.pulsar.client.impl.ClientCnx - [id: 0x1327459b, L:/<IP_ADDRESS>:59344 - R:pulsar-pluster-01.qa.corp.mparticle.com/<IP_ADDRESS>:6651] Received unknown request id from server: -1
22:30:33.884 [pulsar-client-io-2-1] INFO  org.apache.pulsar.client.impl.ClientCnx - [id: 0x1327459b, L:/<IP_ADDRESS>:59344 ! R:pulsar-pluster-01.qa.corp.mparticle.com/<IP_ADDRESS>:6651] Disconnected

The client.conf is:
webServiceUrl=https://pulsar-pluster-01.qa.corp.mparticle.com:8443/
brokerServiceUrl=pulsar+ssl://pulsar-pluster-01.qa.corp.mparticle.com:6651/
authPlugin=org.apache.pulsar.client.impl.auth.AuthenticationKeyStoreTls
authParams=keyStoreType:JKS,keyStorePath:/opt/pulsar/tls/keystore.jks,keyStorePassword:XXXXXXXXXXXX
tlsAllowInsecureConnection=false
tlsEnableHostnameVerification=false
useKeyStoreTls=true
tlsTrustStoreType=PEM
tlsTrustStorePath=/opt/pulsar/tls/truststore.jks
tlsTrustStorePassword=XXXXXXXXXXXXX
useTls=true

Workaround from @sijie : try to configure authParam as JSON string.

When converting the authParams to JSON, the error disappears.
authParams={"keyStoreType":"JKS","keyStorePath":"/opt/pulsar/tls/keystore.jks","keyStorePassword":"XXXXXXXXXXX"}
However, it seems we are still unable to authenticate.
16:03:27.855 [main] INFO  org.apache.pulsar.testclient.PerformanceProducer - Dumping latency stats to perf-producer-1607529807855.hgrm
16:03:27.857 [pulsar-perf-producer-exec-1-1] INFO  org.apache.pulsar.testclient.PerformanceProducer - Started performance test thread 0
16:03:28.891 [pulsar-perf-producer-exec-1-1] INFO  org.apache.pulsar.testclient.PerformanceProducer - Adding 1 publishers on topic persistent://public/default/test-partitioned-perftool
16:03:29.333 [pulsar-client-io-2-1] INFO  org.apache.pulsar.client.impl.ConnectionPool - [[id: 0x673e3f02, L:/<IP_ADDRESS>:42828 - R:pulsar-pluster-01.example.com/<IP_ADDRESS>:6651]] Connected to server
16:03:29.527 [pulsar-client-io-2-1] WARN  org.apache.pulsar.client.impl.ClientCnx - [id: 0x673e3f02, L:/<IP_ADDRESS>:42828 - R:pulsar-pluster-01.example.com/<IP_ADDRESS>:6651] Received error from server: Unable to authenticate
16:03:29.528 [pulsar-client-io-2-1] WARN  org.apache.pulsar.client.impl.ClientCnx - [id: 0x673e3f02, L:/<IP_ADDRESS>:42828 - R:pulsar-pluster-01.example.com/<IP_ADDRESS>:6651] Received unknown request id from server: -1
16:03:29.530 [pulsar-client-io-2-1] INFO  org.apache.pulsar.client.impl.ClientCnx - [id: 0x673e3f02, L:/<IP_ADDRESS>:42828 ! R:pulsar-pluster-01.example.com/<IP_ADDRESS>:6651] Disconnected

@evfurman Thanks for your feedback. I've refined the "brokerClientAuthenticationParameters" as json type as well to configure the client auth.
Have you met issues in configuring other auth, for example, token auth?

@sijie  Except in TLS keystore, in Token auth, JWT, Athenz, Keberos, brokerClientAuthenticationParameters is used. Shall we change all of them as JSON string?

@ In https://github.com/apache/pulsar/pull/9313, do you mean that since 2.7.1, brokerClientAuthenticationParameters supports JSON format for TLS keystore, JWT, Athenz, Keberos?


Add a brew cask

Would be nice!

there is actually a cask but it points to the previous v1.0 release


FluentToken updates

Problem
Root cause
Fix

Define interface IAliasTokens, IControlTokens to extend it to add custom token support. AliasTokens extends IAliasTokens. ControlTokens extends IControlTokens. This help to create abstraction layer for modules.
Moved AliasTokens to FluentAliasTokens class. Rename GlobalTokens to FluentGlobalTokens for parity.
Merged AppThemeController functionality with FluentTheme object & removed AppThemeController.
Refractor FluentTheme to refresh on themeMode update."

Validations
(how the change was tested, including both manual and automated tests)
Screenshots

Before
After

Screenshot or description before this change
Screenshot or description with this change

Pull request checklist
This PR has considered:

[x] Light and Dark appearances
[ ] Automated Tests
[x] Documentation and demo app examples
[ ] VoiceOver and Keyboard Accessibility
[ ] Internationalization and RTL layouts
[ ] Size classes and window sizes (notched devices, multitasking, different window sizes, etc)

Please Fix Merge conflicts and proceed with merge.


instrumentation-mongodb: performance degradation due to _scrubStatement

What version of OpenTelemetry are you using?
@opentelemetry/api: 1.9.0
@opentelemetry/sdk-trace-base: 1.26.0
@opentelemetry/sdk-trace-node: 1.26.0
@opentelemetry/instrumentation-mongodb: 0.48.0

What version of Node are you using?
node: v20.17.0

What did you do?
Insert/update mongo documents that have large datasets (BinData, Arrays, etc).
Namely using GridFS to upload large files (which are chunked into 255KiB documents)
What did you expect to see?
GridFS upload of a 430MiB file takes around a minute (as of instrumentation-mongodb: 0.44.0)
What did you see instead?
GridFS upload of a 430MiB file takes over 5 minutes  (as of instrumentation-mongodb: 0.45.0 and after)
Additional context
We were able to deduce that the introduce of _scrubStatement as being the culprit: https://github.com/open-telemetry/opentelemetry-js-contrib/pull/1728/files#diff-0dd65d8fe0cee39d03f2ddd06f60730b20553e33521842fdb553056bfc1c8231R929
It is iterating the mongo cmd operation (which includes the document) recursively through nested objects and arrays, namely with disregard of the operation (for GridFs upload) to contain binary data upwards of (by default) 261120 items in an Array/BinData/Buffer. I will also note, the implementation would not (IMO) handle Date, ObjectId, etc. correctly either.

I added some notes at https://github.com/open-telemetry/opentelemetry-js-contrib/issues/2281#issuecomment-2489881451 that relate to this issue as well.


Feature card playing animation - TRY 2

Closes issue: https://github.com/sopra-fs22-group-36/screw-your-neighbor-react/issues/71


⚠ SceneTime has degraded performance

In ad454b9, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1563 ms

Resolved: SceneTime performance has improved in 1b33cb2 after 6 minutes.


InstanceInfoReplicator register service after unregistered when shutting down

20:36:28.856 [Thread-8] INFO   c.netflix.discovery.DiscoveryClient.shutdown 852 - Shutting down DiscoveryClient ...
20:36:28.857 [Thread-8] INFO   c.netflix.discovery.DiscoveryClient.unregister 884 - Unregistering ...
20:36:28.861 [Thread-8] INFO   c.netflix.discovery.DiscoveryClient.unregister 886 - DiscoveryClient_SHOWOFF/<IP_ADDRESS>:showoff:19001:0.1.0 - deregister  status: 200
20:36:28.862 [DiscoveryClient-InstanceInfoReplicator-0] INFO   c.netflix.discovery.DiscoveryClient.register 795 - DiscoveryClient_SHOWOFF/<IP_ADDRESS>:showoff:19001:0.1.0: registering service...
20:36:28.865 [DiscoveryClient-InstanceInfoReplicator-0] INFO   c.netflix.discovery.DiscoveryClient.register 804 - DiscoveryClient_SHOWOFF/<IP_ADDRESS>:showoff:19001:0.1.0 - registration status: 204
20:36:28.867 [Thread-8] INFO   c.netflix.discovery.DiscoveryClient.shutdown 873 - Completed shut down of DiscoveryClient

Thread "Thread-8" is shutting down discovery client, but thread "DiscoveryClient-InstanceInfoReplicator-0" is still scheduling.
See the code in com.netflix.discovery.InstanceInfoReplicator.java
    public void stop() {
        scheduler.shutdownNow();
        started.set(false);
    }

in JDK 8, shutdownNow says "This method does not wait for actively executing tasks to
* terminate.  Use {@link #awaitTermination awaitTermination} to
* do that."
Should we change shutdownNow to awaitTermination to avoid this situation?

PR #974


Port the DUSK faucet to the new architecture

Describe what you want implemented
One node should be preloaded with a LOT of Dusk. The existing faucet API should be able to be adapted to transfer DUSK tokens to those that complete the Testnet procedure
Describe "Why" this is needed
This is needed to speed up the participation to the Testnet
Describe alternatives you've considered
Although inconvenient, we can spawn a manual procedure for this. Upon communication of a wallet from the requestor, a transaction could be done manually with the CLI to transfer the Testnet DUSK requested.

The faucet is now completely automated. After @Fulviuus modifications, upon a cluster deployment, a new faucet gets created with the latest codebase and an updated DNS


Publish to maven central

Could you please release to https://central.sonatype.com/
FYI https://central.sonatype.org/publish/publish-guide/

Thx for the info @CoderYellow.
gatling-sftp has been deploy to Maven Central on version 0.0.5


BSD License and GPL source file headers conflict

1f4e2394 changed the license to BSD however the source headers still say GPL:
./Text/Pandoc/JSON.hs:23:   License     : GNU GPL, version 2 or above
./Text/Pandoc/Definition.hs:24:   License     : GNU GPL, version 2 or above
./Text/Pandoc/Builder.hs:25:   License     : GNU GPL, version 2 or above
./Text/Pandoc/Walk.hs:29:   License     : GNU GPL, version 2 or above
./Text/Pandoc/Generic.hs:22:   License     : GNU GPL, version 2 or above

Could you please update them?

Thanks!


sql default syntax error

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
https://github.com/wenerme/ent-demo/blob/e2d349bcc4fc5c90e1d3df5bfff22aad9345eb44/ent/schema/mixin_id.go#L91-L106
type TenantSidMixin struct {
	mixin.Schema
}

func (TenantSidMixin) Fields() []ent.Field {
	return []ent.Field{
		field.Int("sid").Immutable().Annotations(
		),
		field.Int("tid").Immutable().Annotations(
			// this line failed
			&entsql.Annotation{Default: "current_setting('tenant.id')::bigint"},
		),
	}
}

panic: sql/schema: modify "service_accounts" table: ERROR: invalid input syntax for type bigint: "current_setting('tenant.id')::bigint" (SQLSTATE 22P02)

Expected Behavior 🤔

default works as expected
Steps to Reproduce 🕹
https://github.com/wenerme/ent-demo/blob/e2d349bcc4fc5c90e1d3df5bfff22aad9345eb44/test/migrate_test.go#L17-L46
Your Environment 🌎

Tech
Version

Go
1.18.1

Ent
latest

Database
postgres

Driver
pgx

Seems I misunderstood the schema.WithDir(dir), I thought this is where I put migration sql files.


Row length too small

Hello,
not sure why but for me the rows are displayed too short (on Windows).
This input file

is displayed as:

This issue is correlated to the first one; it is all caused by poor API communication with the windows terminal. As you can see the "current size" values are -1,-1 which is a flag I used to denote errors with the terminal size API. I'll close this issue and merge it in the first one.


Adjust contributor-page (first step in workflow)

heading field - remove from common, move to detailed section
type field in detailed section = first field, most important.
conditional fields: if type=exposition / technical - then show subverse widget
conditional fields: if type=application, then show heading + tags, else hide them

Heading and type fields are moved in commit 20da27d88388078152f9d8468b8d3613aa8e74d5
This depends on Issue #7

Conditional fields require the "type"s to be defined by the module, and not in a Taxonomy... See issue #14

The type stays taxonomy_term_reference, but the taxonomy terms now have a field which determines the sort behaviour: "lw_listing_order". Pseduo-code for the last two TODOs:
x = the lw_listing_order field of the taxonomy term references by the 'position' (a.k.a. type) field
switch x
  case LIVING_WORD_LISTING_ORDER_SINGLE_SUB_VERSE
    show subverse widget
  case LIVING_WORD_LISTING_ORDER_APPLICATION_TAGS
    show heading field
    show tags field
  case LIVING_WORD_LISTING_ORDER_PREDOMINANT_MULTI_VERSE
    ???
  default
    show nothing extra

@krokkie Please verify if this makes sense...

Lyk reg.
It does not only define the sort order, but also which fields are "required" in the editor, where it is presented in a list, etc.

Hmm... in that case, we need new names for the behaviours, and the field should be called lw_listing_behaviour and not lw_listing_order.

I propose that we name the possible values of _listing_behaviour as follows:

LIVING_WORD_LISTING_BEHAVIOUR_BROAD
LIVING_WORD_LISTING_BEHAVIOUR_NARROW
LIVING_WORD_LISTING_BEHAVIOUR_TOPICAL

On the edit page for taxonomy terms in the position vocabulary, one can now select:

Since commit 1f28b6a44a2360f5578481102c84766a13eeb741, the heading field only appears when application (or any taxonomy term where the field lw_listing_behaviour == LIVING_WORD_LISTING_BEHAVIOUR_TOPICAL) is selected.
Issue #16 blocks this.


dt.order fires also dt.search

the dt.order event also fires a dt.search event.
example:
https://datatables.net/examples/advanced_init/dt_events.html
I would expect that a order-event only fires a dt.order event, but not both.
Or am I wrong? :-)

You aren't wrong as such, but this is just how DataTables operates. A sort will always trigger a search because of how DataTables works internally. I may separate them eventually, but don't currently have plans to do so.


Better regex anchors for upstream

The first commit is a tiny fix for regex mangling - it simply changes a non-raw string into a raw string.
The second commit enables more expressive regular expressions in the action alias parser/mangler.
Instead of blindly adding anchors to action alias format regexes, it now searches the existing regex for anchors and does not add anchors if it already contains them.
This allows users to create regexes that already contain anchors
re.compile(r"^jira issue {{ issue_key }}$")

or regexes that can match multiple times per string, like when you want to find multiple Jira issues in a Slack message:
re.compile(r"(?:^|\b)(?P<issue_key>[A-Z][A-Z0-9]+-\d+)(?:\b|$")

I have included tests for the new parse tree searching function.
I will be working to upstream our changes to the Stackstorm Jira pack once this gets merged.

Thanks for your contribution - from a high level perspective it looks good.

I don't see why the Travis test is failing as it seems to be unrelated to my change. Can you give me some help or pointers debugging that test?

It might be a race or something, I will restart the build and see if it passes.

Rebased against master.

Merged, thanks.

On a related note - can you please also add some documentation for this change and new functionality - https://github.com/stackstorm/st2docs

@Kami Sorry for the late response. I've thought about adding documentation for this, but I actually think this is a feature best left undocumented.
The Regular Expressions of the StackStorm documentation on action aliases seems to steer users away from using regexes:

They can be as complex as you want, just exercise reasonable caution as regexes tend to be difficult to debug. If you think you have a problem that can be solved by a regex...well now you have two problems to solve.

In general, I agree with that decision. Regexes are a tool that many pack authors will (hopefully) never need to use. Add even though I authored this patch, I only have one alias that uses this feature!
So, while I think if we are going to support regular expressions we should make them Just Work (tm), so I'm happy that this PR was merged, but if we aren't going to go "all in" on fully supporting regular expressions in action aliases - including recommending them to pack authors - I think it would be best to leave this particular feature undocumented.
If you disagree, I'm happy to document this. I would probably include something like this:

When you write a regular expression, keep in mind that StackStorm will insert beginning and ending anchors to the beginning and end of the regex string.
To avoid the anchors being added, you can add an alternation group:
formats:
  - display: ...
    representation:
      - (?:^|\b)jira issue (?P<issue_key>[A-Z][A-Z0-9]+-[0-9]+)(?:\b|$)

Note that the alternatives are not limited to \b, they can be any valid regex subexpression.
Examples:
formats:
  - display: ...
    representation:
      - jira issue (?P<issue_key>[A-Z][A-Z0-9]+-[0-9]+)

will be converted to:
^jira issue (?P<issue_key>[A-Z][A-Z0-9]+-[0-9]+)$
formats:
  - display: ...
    representation:
      - (?:^|\b)jira issue (?P<issue_key>[A-Z][A-Z0-9]+-[0-9]+)

will be converted to:
(?:^|\b)jira issue (?P<issue_key>[A-Z][A-Z0-9]+-[0-9]+)$
formats:
  - display: ...
    representation:
      - jira issue (?P<issue_key>[A-Z][A-Z0-9]+-[0-9]+)(?:$|\b)

will be converted to:
^jira issue (?P<issue_key>[A-Z][A-Z0-9]+-[0-9]+)(?:$|\b)
formats:
  - display: ...
    representation:
      - (?:^|.*)jira issue (?P<issue_key>[A-Z][A-Z0-9]+-[0-9]+)(?:$|.*)

will be converted to:
(?:^|.*)jira issue (?P<issue_key>[A-Z][A-Z0-9]+-[0-9]+)(?:$|.*)

Please let me know what your final determination is.
Thanks!


⚠ 366.ru has degraded performance

In 28cecac, 366.ru (https://366.ru) experienced degraded performance:

HTTP code: 200
Response time: 9340 ms

Resolved: 366.ru performance has improved in a19dd95.


Per email from Brad Maggard on 2015-09-16, addfieldusingcontext() doe…

Per email from Brad Maggard on 2015-09-16, addfieldusingcontext() doesn't have access to the new field, making calculations like running sum more complicated.
The generator yields the tuple from the original table.  It now creates a new Record() object with the additional field and the previous row's value, providing access to the prior row's new field.
I profiled both time and memory usage - the extra step of creating the Record() instance is minimal.
On a random table of 1MM rows, it added 100KB of memory at runtime and changed execution time from 63 seconds to 65 seconds on my test.

Thanks a lot Roger, I'll review asap.
On Wednesday, September 16, 2015, Roger Woodley<EMAIL_ADDRESS>wrote:

Per email from Brad Maggard on 2015-09-16, addfieldusingcontext() doesn't
have access to the new field, making calculations like running sum more
complicated.
The generator yields the tuple from the original table. It now creates a
new Record() object with the additional field and the previous row's value,
providing access to the prior row's new field.
I profiled both time and memory usage - the extra step of creating the
Record() instance is minimal.
On a random table of 1MM rows, it added 100KB of memory at runtime and
changed execution time from 63 seconds to 65 seconds on my test.
You can view, comment on, or merge this pull request online at:
https://github.com/alimanfoo/petl/pull/343
Commit Summary

Per email from Brad Maggard on 2015-09-16, addfieldusingcontext()
doesn't have access to the new field, making calculations like running sum
more complicated.

File Changes

M petl/test/transform/test_basics.py
https://github.com/alimanfoo/petl/pull/343/files#diff-0 (33)
M petl/transform/basics.py
https://github.com/alimanfoo/petl/pull/343/files#diff-1 (5)

Patch Links:

https://github.com/alimanfoo/petl/pull/343.patch
https://github.com/alimanfoo/petl/pull/343.diff

—
Reply to this email directly or view it on GitHub
https://github.com/alimanfoo/petl/pull/343.

--
Alistair Miles
Head of Epidemiological Informatics
Centre for Genomics and Global Health http://cggh.org
The Wellcome Trust Centre for Human Genetics
Roosevelt Drive
Oxford
OX3 7BN
United Kingdom
Web: http://purl.org/net/aliman
Email<EMAIL_ADDRESS><EMAIL_ADDRESS>Tel: +44 (0)1865 287721

Thank you Roger, sorry it took so long to get to this.

Oh, no need to apologize - you have your regular life, managing releases, etc. to worry about.


product.json location

In the documentation about how to point code-server to a different extension gallery (https://coder.com/docs/code-server/latest/FAQ#how-do-i-use-my-own-extensions-marketplace), reference is made to either setting environment variables (which works fine) or setting values in product.json. There does not seem to be such a file in ~/.local/share/code-server and I cannot locate where it is supposed to be. Can its typical location be documented?

I think there is some misunderstanding. The docs read

If you own a marketplace that implements the VS Code Extension Gallery API, you can point code-server to it by setting $SERVICE_URL and $ITEM_URL. These correspond directly to serviceUrl and itemUrl in VS Code's product.json.

You can't modify the product.json in your instance of code-server but these values (the default values) live in product.json.
Hope that makes sense! I'm going to close this.

No, not really. I think the docs should include that file's location -- I certainly can't find it.

No, not really. I think the docs should include that file's location

Sorry, maybe it wasn't clear in my last message. I can see why it would be confusing. We don't recommend editing the product.json. This would be the equivalent to editing the source code and is not recommended because we can't guarantee things will still work after. And JSON (as you probably know) is fragile so I wouldn't recommend changing that file.
You should use the environment variables, which is why that's the only thing in the docs.

I see. Then I think the reference to product.json should be removed as extraneous.

Good point! I'll reopen and track here


Add button border option with color

With the most recent changes, including exposing the entire action button itself as a property, this no longer applies. Thanks for contributing nonetheless!


[DataFactory]Add sensitive fields extracted from connection string in swagger for AKV reference

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[ ] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[ ] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[ ] The spec conforms to the Swagger 2.0 specification.
[ ] The spec follows the guidelines described in the Swagger checklist document.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Can one of the admins verify this patch?

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-python

Automation for azure-sdk-for-js

Automation for azure-sdk-for-java

Automation for azure-sdk-for-go

Automation for azure-sdk-for-node

@jhendrixMSFT May I know which file to update? If LinkedServices_Create.json in examples folder, those fields I added is optional and will only be used in some special cases, so may not need to be added there.

@boxiao-o If these fields are optional then perhaps it makes more sense to add a new example that uses them?

@jhendrixMSFT Seems based on our convention, we usually do not update example here, but I will update the examples in sdk JsonSamples

@boxiao-o I'm not sure what you mean by "based on our convention".  The example files are used to generate documentation so if you want these fields doc'ed you should add an example for them.


font icon glyph missing

Hello, the font that is being used by vi-mongo is missing on my machine.

could you provide the font name so i could install it?. thanks!

sheesh, just went through the styles config and saw that i could customize the symbol.

Hi @noornee , I'm using noto-fonts with kitty terminal (it looks realy good for me):

but I know that ttf-Symbola is also a way to install them.
Also in welcome page there was a button to turn on/off better-looking symbols

If you didn't notice it maybe I should make it more visable for the user?

Hi @noornee , I'm using noto-fonts with kitty terminal (it looks realy good for me):

Hii @kopecmaciej
ooh, i dont have that installed on my machine. I'll try it out. I use Iosevka Nerd Font on kitty

If you didn't notice it maybe I should make it more visable for the user?

No, i think its okay where it is. I actually did notice it but i was more focused on finding out why the font glyph was missing. it didnt occur to me that it could be turned off

just toggled it off, saved and connected. the default font it provides looks great!


🐛 [crashlytics][release] Information from recordFlutterFatalError shows up as 'Instance of 'DiagnosticsProperty'

Is there an existing issue for this?

[X] I have searched the existing issues.

Which plugins are affected?
Crashlytics
Which platforms are affected?
Android
Description
All errors I'm getting from Firebase right now have "Logs & Breadcrumbs" like this:

I think this is because the previous fix for #7912 was not a fix at all, but just a way of allowing users to use Objects in addition to DiagnosticsNode. But that workaround doesn't apply to FlutterErrorDetails and recordFlutterFatalError, which still involve an InformationCollector that returns DiagnosticsNodes.
I'm confused how this can still be a thing after all this time. Are Crashlytics users intended to use Debug builds in production?
Reproducing the issue
I've had trouble with Firebase not recording issues from my debug builds, but we are getting reports for Fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError in production so I think the repro is to add a onError handler...
  FlutterError.onError = (FlutterErrorDetails details) {
    FirebaseCrashlytics.instance.recordFlutterFatalError(details);
  };

...and then cause any kind of Flutter error.
Firebase Core version
3.1.0
Flutter Version
3.19.5 (from flutter pub deps; pubspec.lock says 0.0.0)
Relevant Log Output
# Crashlytics - Custom logs
# Application: ca.barreleye.barreleye_app
# Platform: android
# Version: 0.9.6 (54)
# Issue: 7f9e10f113ea918fb87e3450ffcee32c
# Session: 66900C9601B500072F9E507F5802217C_DNE_0_v2
# Date: Thu Jul 11 2024 10:47:18 GMT-0600 (Mountain Daylight Time)

0 | Thu Jul 11 2024 11:11:32 GMT-0600 (Mountain Daylight Time) | Instance of 'DiagnosticsProperty<void>'
1 | Thu Jul 11 2024 11:11:32 GMT-0600 (Mountain Daylight Time) | Instance of 'DiagnosticsProperty<void>'
2 | Thu Jul 11 2024 11:11:32 GMT-0600 (Mountain Daylight Time) | Instance of 'DiagnosticsProperty<void>'
3 | Thu Jul 11 2024 11:11:32 GMT-0600 (Mountain Daylight Time) | Instance of 'DiagnosticsProperty<void>'

Flutter dependencies

Expand Flutter dependencies snippet

Dart SDK 3.3.3
Flutter SDK 3.19.5
barreleye_app 1.0.0+56

dependencies:
- connectivity_plus 6.0.2 [flutter flutter_web_plugins connectivity_plus_platform_interface web meta nm]
- cupertino_icons 1.0.6
- date_field 5.0.1 [flutter intl]
- dropdown_button2 2.3.9 [flutter meta]
- expressions 0.2.5+1 [quiver petitparser rxdart meta]
- firebase_analytics 11.0.1 [firebase_analytics_platform_interface firebase_analytics_web firebase_core firebase_core_platform_interface flutter]
- firebase_core 3.1.0 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_crashlytics 4.0.1 [firebase_core firebase_core_platform_interface firebase_crashlytics_platform_interface flutter stack_trace]
- flutter 0.0.0 [characters collection material_color_utilities meta vector_math sky_engine]
- flutter_app_badger 1.5.0 [flutter]
- flutter_easyloading 3.0.5 [flutter flutter_spinkit]
- flutter_markdown 0.6.22+1 [flutter markdown meta path]
- flutter_native_splash 2.2.16 [args flutter flutter_web_plugins js html image meta path universal_io xml yaml]
- fluttertoast 8.2.4 [flutter flutter_web_plugins]
- hive 2.2.3 [meta crypto]
- hive_flutter 1.1.0 [flutter hive path_provider path]
- http 1.2.1 [async http_parser meta web]
- intl 0.19.0 [clock meta path]
- json_annotation 4.8.1 [meta]
- logging 1.2.0
- open_file_plus 3.4.1+1 [flutter ffi]
- package_info_plus 7.0.0 [ffi flutter flutter_web_plugins http meta path package_info_plus_platform_interface web win32 clock]
- passwd_gen 1.1.2
- path 1.9.0
- path_provider 2.1.3 [flutter path_provider_android path_provider_foundation path_provider_linux path_provider_platform_interface path_provider_windows]
- provider 6.1.2 [collection flutter nested]
- shared_preferences 2.2.3 [flutter shared_preferences_android shared_preferences_foundation shared_preferences_linux shared_preferences_platform_interface shared_preferences_web s
hared_preferences_windows]
- synchronized 3.1.0+1
- upgrader 10.3.0 [flutter device_info_plus html http os_detect package_info_plus shared_preferences url_launcher version xml]
- url_launcher 6.2.6 [flutter url_launcher_android url_launcher_ios url_launcher_linux url_launcher_macos url_launcher_platform_interface url_launcher_web url_launcher_windows]
- uuid 4.4.0 [crypto sprintf meta fixnum]
- version 3.0.2

dev dependencies:
- build_runner 2.4.9 [analyzer args async build build_config build_daemon build_resolvers build_runner_core code_builder collection crypto dart_style frontend_server_client glob gr
aphs http_multi_server io js logging meta mime package_config path pool pub_semver pubspec_parse shelf shelf_web_socket stack_trace stream_transform timing watcher web_socket_chann
el yaml]
- flutter_launcher_icons 0.9.2 [args image path yaml]
- flutter_lints 3.0.2 [lints]
- flutter_test 0.0.0 [flutter test_api matcher path fake_async clock stack_trace vector_math leak_tracker_flutter_testing async boolean_selector characters collection leak_tracker
leak_tracker_testing material_color_utilities meta source_span stream_channel string_scanner term_glyph vm_service]
- hive_generator 2.0.1 [build source_gen hive analyzer source_helper]
- json_serializable 6.7.1 [analyzer async build build_config collection json_annotation meta path pub_semver pubspec_parse source_gen source_helper]

transitive dependencies:
- _fe_analyzer_shared 67.0.0 [meta]
- _flutterfire_internals 1.3.37 [collection firebase_core firebase_core_platform_interface flutter meta]
- analyzer 6.4.1 [_fe_analyzer_shared collection convert crypto glob meta package_config path pub_semver source_span watcher yaml]
- archive 3.4.10 [crypto path pointycastle]
- args 2.5.0
- async 2.11.0 [collection meta]
- boolean_selector 2.1.1 [source_span string_scanner]
- build 2.4.1 [analyzer async convert crypto glob logging meta package_config path]
- build_config 1.1.1 [checked_yaml json_annotation path pubspec_parse yaml]
- build_daemon 4.0.1 [built_collection built_value crypto http_multi_server logging path pool shelf shelf_web_socket stream_transform watcher web_socket_channel]
- build_resolvers 2.4.2 [analyzer async build collection convert crypto graphs logging package_config path pool pub_semver stream_transform yaml]
- build_runner_core 7.3.0 [async build build_config build_resolvers collection convert crypto glob graphs json_annotation logging meta package_config path pool timing watcher yaml]
- built_collection 5.1.1
- built_value 8.9.2 [built_collection collection fixnum meta]
- characters 1.3.0
- checked_yaml 2.0.3 [json_annotation source_span yaml]
- clock 1.1.1
- code_builder 4.10.0 [built_collection built_value collection matcher meta]
- collection 1.18.0
- connectivity_plus_platform_interface 2.0.0 [flutter meta plugin_platform_interface]
- convert 3.1.1 [typed_data]
- crypto 3.0.3 [typed_data]
- csslib 1.0.0 [source_span]
- dart_style 2.3.6 [analyzer args collection path pub_semver source_span]
- dbus 0.7.10 [args ffi meta xml]
- device_info_plus 10.1.0 [device_info_plus_platform_interface ffi file flutter flutter_web_plugins meta web win32 win32_registry]
- device_info_plus_platform_interface 7.0.0 [flutter meta plugin_platform_interface]
- fake_async 1.3.1 [clock collection]
- ffi 2.1.2
- file 7.0.0 [meta path]
- firebase_analytics_platform_interface 4.0.1 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_analytics_web 0.5.7+9 [_flutterfire_internals firebase_analytics_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins]
- firebase_core_platform_interface 5.1.0 [collection flutter flutter_test meta plugin_platform_interface]
- firebase_core_web 2.17.2 [firebase_core_platform_interface flutter flutter_web_plugins meta web]
- firebase_crashlytics_platform_interface 3.6.37 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- fixnum 1.1.0
- flutter_spinkit 5.2.1 [flutter]
- flutter_web_plugins 0.0.0 [flutter characters collection material_color_utilities meta vector_math]
- frontend_server_client 4.0.0 [async path]
- glob 2.1.2 [async collection file path string_scanner]
- graphs 2.3.1 [collection]
- html 0.15.4 [csslib source_span]
- http_multi_server 3.2.1 [async]
- http_parser 4.0.2 [collection source_span string_scanner typed_data]
- image 3.3.0 [archive meta xml]
- io 1.0.4 [meta path string_scanner]
- js 0.6.7 [meta]
- leak_tracker 10.0.0 [clock collection meta path vm_service]
- leak_tracker_flutter_testing 2.0.1 [flutter leak_tracker leak_tracker_testing matcher meta]
- leak_tracker_testing 2.0.1 [leak_tracker matcher meta]
- lints 3.0.0
- markdown 7.2.2 [args meta]
- matcher 0.12.16+1 [async meta stack_trace term_glyph test_api]
- material_color_utilities 0.8.0 [collection]
- meta 1.11.0
- mime 1.0.5
- nested 1.0.0 [flutter]
- nm 0.5.0 [dbus]
- os_detect 2.0.1
- package_config 2.1.0 [path]
- package_info_plus_platform_interface 3.0.0 [flutter meta plugin_platform_interface]
- path_provider_android 2.2.3 [flutter path_provider_platform_interface]
- path_provider_foundation 2.3.2 [flutter path_provider_platform_interface]
- path_provider_linux 2.2.1 [ffi flutter path path_provider_platform_interface xdg_directories]
- path_provider_platform_interface 2.1.2 [flutter platform plugin_platform_interface]
- path_provider_windows 2.2.1 [ffi flutter path path_provider_platform_interface win32]
- petitparser 6.0.2 [meta]
- platform 3.1.4
- plugin_platform_interface 2.1.8 [meta]
- pointycastle 3.8.0 [collection convert js]
- pool 1.5.1 [async stack_trace]
- pub_semver 2.1.4 [collection meta]
- pubspec_parse 1.2.3 [checked_yaml collection json_annotation pub_semver yaml]
- quiver 3.2.1 [matcher]
- rxdart 0.27.7
- shared_preferences_android 2.2.2 [flutter shared_preferences_platform_interface]
- shared_preferences_foundation 2.4.0 [flutter shared_preferences_platform_interface]
- shared_preferences_linux 2.3.2 [file flutter path path_provider_linux path_provider_platform_interface shared_preferences_platform_interface]
- shared_preferences_platform_interface 2.3.2 [flutter plugin_platform_interface]
- shared_preferences_web 2.3.0 [flutter flutter_web_plugins shared_preferences_platform_interface web]
- shared_preferences_windows 2.3.2 [file flutter path path_provider_platform_interface path_provider_windows shared_preferences_platform_interface]
- shelf 1.4.1 [async collection http_parser path stack_trace stream_channel]
- shelf_web_socket 1.0.4 [shelf stream_channel web_socket_channel]
- sky_engine 0.0.99
- source_gen 1.5.0 [analyzer async build dart_style glob path source_span yaml]
- source_helper 1.3.4 [analyzer collection source_gen]
- source_span 1.10.0 [collection path term_glyph]
- sprintf 7.0.0
- stack_trace 1.11.1 [path]
- stream_channel 2.1.2 [async]
- stream_transform 2.1.0
- string_scanner 1.2.0 [source_span]
- term_glyph 1.2.1
- test_api 0.6.1 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph]
- timing 1.0.1 [json_annotation]
- typed_data 1.3.2 [collection]
- universal_io 2.2.2 [collection meta typed_data]
- url_launcher_android 6.3.0 [flutter url_launcher_platform_interface]
- url_launcher_ios 6.2.5 [flutter url_launcher_platform_interface]
- url_launcher_linux 3.1.1 [flutter url_launcher_platform_interface]
- url_launcher_macos 3.1.0 [flutter url_launcher_platform_interface]
- url_launcher_platform_interface 2.3.2 [flutter plugin_platform_interface]
- url_launcher_web 2.3.0 [flutter flutter_web_plugins url_launcher_platform_interface web]
- url_launcher_windows 3.1.1 [flutter url_launcher_platform_interface]
- vector_math 2.1.4
- vm_service 13.0.0
- watcher 1.1.0 [async path]
- web 0.5.1
- web_socket_channel 2.4.5 [async crypto stream_channel web]
- win32 5.4.0 [ffi]
- win32_registry 1.1.3 [ffi win32]
- xdg_directories 1.0.4 [meta path]
- xml 6.5.0 [collection meta petitparser]
- yaml 3.1.2 [collection source_span string_scanner]

Additional context and comments
No response

Hey @qwertie - unfortunately, FlutterErrorDetails diagnostics renders differently in release mode. As mentioned here.
The workaround is to use the recordError() directly which will allow you to pass strings to the information list. Under the hood, both recordFlutterError() & recordFlutterFatalError() use recordError(). You could use the following code:
https://github.com/firebase/flutterfire/blob/master/packages/firebase_crashlytics/firebase_crashlytics/lib/src/firebase_crashlytics.dart#L139-L155

So, something like this?
void recordFlutterFatalError(FlutterErrorDetails details2) {
  // In production builds, calling `recordFlutterFatalError` discards all messages in all
  // `DiagnosticsNode`s for no apparent reason. As a workaround, convert `DiagnosticsNode`s
  // to strings. (DP: I haven't tested it; I need a production build to ensure that it works
  // and I don't know how to trigger a fatal error)
  // https://github.com/firebase/flutterfire/issues/13066
  //FirebaseCrashlytics.instance.recordFlutterFatalError(details2);

  final information = details.informationCollector?.call() ?? [];

  FirebaseCrashlytics.instance.recordError(
    details.exceptionAsString(),
    details.stack,
    reason: details.context
        ?.toStringDeep(minLevel: DiagnosticLevel.info)
        .trim(),
    information: information.map((node) => node.toDescription()),
    printDetails: false,
    fatal: true,
  );

  FlutterError.presentError(details);
}


Remove unused field and improve error messages

Description

Remove unused field and improve error messages

What has Changed?
What specific problem were you aiming to address, and how did you successfully resolve it? If tests were not uploaded for this pull request or if coverage decreased, please provide an explanation for the change.

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[ ] included the correct type prefix in the PR title
[ ] added ! to the type prefix if API or client breaking change
[ ] targeted the correct branch (see PR Targeting)
[ ] provided a link to the relevant issue or specification
[ ] followed the guidelines for building modules
[ ] included the necessary unit and integration tests
[ ] included comments for documenting Go code
[ ] updated the relevant documentation or specification
[ ] reviewed "Files changed" and left comments if necessary
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed ! in the type prefix if API or client breaking change
[ ] confirmed all author checklist items have been addressed
[ ] reviewed state machine logic
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

Deployment Notes
Are there any specific considerations to take into account when deploying these changes? This may include new dependencies, scripts that need to be executed, or any aspects that can only be evaluated in a deployed environment.
Screenshots and Videos
Please provide any relevant before and after screenshots by uploading them here. Additionally, demo videos can be highly beneficial in demonstrating the process.

Since you changed the data structure, a migration won't be needed?

thanks
you are right, updating the script

For this I am thinking to wait now as there is already a lot of things in migration, going to merge this after upgrade


ERC2771ContextUpgradeable doesn't follow Upgradeable Pattern

I've upgraded my contracts to the latest 4.5 and noticed that I can no longer call __ERC2771Context_init_unchained(trustedForwarder) due to the immutable _trustedForwarder variable. This breaks the upgradeability pattern and there should be a way to work around this.

💻 Environment

<EMAIL_ADDRESS>🔢 Code to reproduce bug
Missing __ERC2771Context_init_unchained from the codebase. See https://github.com/OpenZeppelin/openzeppelin-contracts-upgradeable/commit/842bef827058dc37b81bc0c96956bb381b6cf789

Related to: https://github.com/OpenZeppelin/openzeppelin-contracts/pull/2917

Hello @tpae
It was decided to use an immutable variable here because we thought the gas savings would be significant enough, and we did not imagine that multiple proxies using the same underlying implementation would want to use different trusted forwarders.
Are you using ERC2771Context with multiple forwarders? If so, my solution would be to build your own ERC2771ContextFromStorage module, that uses non-immutable variables, and includes an initializer.
Maybe we should provide both versions in the future @frangio

Hello @Amxx, thank you for your reply and suggestions. I'm not using multiple forwarders; I have a factory that instantiates minimal proxies with implementations that extends ERC2771Context.
My understanding is that when we instantiate a minimal proxy, it does not call the constructor which is required to set the initial values of the trusted forwarder. By defining the variable as immutable, does that mean our implementation contract will need to be deployed with a trusted forwarder address, and all of the instantiated proxies will use that same address?
I could build my own ERC2771ContextFromStorage, but I want to understand how to use ERC2771ContextUpgradeable in a way meant to be used.

In that case you should use the new ERC2771ContextUpgradeable.
The good thing with immutable variables is that, once they are set at construction, minimal proxy that point to the implementation WILL not need to set these values in the constructor.
Here is an example
import<EMAIL_ADDRESS>
contract TestInstance {
    uint256 public immutable someValue;

    constructor(uint256 value) {
        someValue = value;
    }
}

contract TestFactory {
    address public immutable template = address(new TestInstance(17));

    function createClone() external returns (address) {
        address instance = Clones.clone(template);

//        require(TestInstance(instance).someValue() == 0, "this would fail");
        require(TestInstance(instance).someValue() == 17, "this will not fail");

        return instance;
    }
}

The bottom line is: when constructing the "template" for your proxy, use the constructor to set the immutable variable in the template. All the proxies will benefit from it, without requiring it to be set in the initializer.
This is cheaper to initialize AND cheaper to use.

Amazing! Thank you so much for your guidance!

Hello
My use case is a bit different. My erc20 will need to use metatx in the future but I don't have the trusted forwarder address yet so I cannot set it at deployment. How are we supposed to do in that case? Use the previous version?

@mvanmeerbeck I would make your contract upgradeable, and add the trusted forwarder as part of a future upgrade.

If I use ERC2771ContextUpgradeable, do I need all of the following boilerplate code? Seems the contract won't compile without:
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.13;

import<EMAIL_ADDRESS>import<EMAIL_ADDRESS>
contract MyContract is Initializable, ERC2771ContextUpgradeable, AccessControlUpgradeable {
    bytes32 public constant FORWARDER_ROLE = keccak256("FORWARDER_ROLE");
    bytes32 public constant ADMIN_ROLE = keccak256("ADMIN_ROLE");

    /// @custom:oz-upgrades-unsafe-allow constructor
    constructor() ERC2771ContextUpgradeable(address(0x0)) {}

    function initialize() public initializer {
        __AccessControl_init();
        _setupRole(ADMIN_ROLE, _msgSender());
        _setRoleAdmin(FORWARDER_ROLE, ADMIN_ROLE);
    }

    function isTrustedForwarder(address forwarder) public view override(ERC2771ContextUpgradeable) returns (bool) {
        return hasRole(FORWARDER_ROLE, forwarder);
    }

    function _msgSender() internal view virtual override(ContextUpgradeable, ERC2771ContextUpgradeable) returns (address sender) {
        return super._msgSender();
    }

    function _msgData() internal view virtual override(ContextUpgradeable, ERC2771ContextUpgradeable) returns (bytes calldata) {
        return super._msgData();
    }
}

notice especially _msgData and _msgSender which are only needed to disambiguate between ContextUpgradeable and ERC2771ContextUpgradeable. Am I doing something wrong here?


How to routing a request with "multipart/form-data"?

in console:
Error applying predicate for route: 25528710-acd4-4cf0-942e-10b6bcf90189 org.springframework.web.server.UnsupportedMediaTypeStatusException: Response status 415 with reason "Content type 'multipart/form-data;boundary=----WebKitFormBoundaryuJbdRWDS4mmZQfTa' not supported"

先这样，再那样就好了

How do you do routing forwarding? Take a look at GlobalCorsProperties.
Attempt to add configuration spring.cloud.gateway.globalcors.cors-configurations.xx.allowed-headers[0]=Content-type.
Hope to help you.

-> builder.routes().route(Function<PredicateSpec, Route.AsyncBuilder> fn)
if this method call many times，
although route info is  valid,
but in the first call, header set will apply to  the after route.
so i must use  this method builder.routes().route(String id,Function<PredicateSpec, Route.AsyncBuilder>)


Mac/Ios tasks are timing out when rebooting the devices

Log:
https://ci.chromium.org/p/flutter/builders/prod/Mac_staging integration_ui_ios_screenshot/384
[integration_ui_ios_screenshot] [STDOUT] "/opt/s/w/ir/k/recipe_cleanup/tmpOrlw9Z/flutter sdk/bin/flutter" exit code: 0
[integration_ui_ios_screenshot] [STDOUT]
[integration_ui_ios_screenshot] [STDOUT]
[integration_ui_ios_screenshot] [STDOUT] ═══════════╡ ••• Checking running Dart processes after task... ••• ╞════════════
[integration_ui_ios_screenshot] [STDOUT]
[integration_ui_ios_screenshot] [STDOUT] Checking for reboot
[integration_ui_ios_screenshot] [STDOUT] rebooting

This is happenning because the command used to reboot the ios phones is actually collecting the syslog continuously.

Requesting cherrypicking https://github.com/flutter/flutter/commit/4597b51cbc2121ad8bcfd38cb925a497867e80cc to fix devicelab. This is a test-only fix, and thus low-risk.


Display issue with hashtable: only the first field is shown and if it's null it looks like it's empty

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
Run these commands:
@{ id = "id"; KeyCredentials = @(@{ Key = $null; DisplayName = "CN=MyServicePrincipalCert"})} | select KeyCredentials
@{ id = "id"; KeyCredentials = @(@{ Key = "Test Key"; DisplayName = "CN=MyServicePrincipalCert"})} | select KeyCredentials

In the first command output, it looks like the KeyCredentials is empty whereas it isn't. I think it's because it shows its first field, Key, which is $null
But this is surprising in my opinion, and it led me to thinking there was a bug in the Microsoft Graph PowerShell SDK whereas there wasn't any: https://github.com/microsoftgraph/msgraph-sdk-powershell/issues/1849
The second command is a more normal case, and its output looks more natural to me.
Expected behavior
PS C:\> @{ id = "id"; KeyCredentials = @(@{ Key = $null; DisplayName = "CN=MyServicePrincipalCert"})} | select KeyCredentials

KeyCredentials
--------------
{$null}
# or perhaps:
# Key = $null; DisplayName = "CN=MyServicePrincipalCert"
# or even the second field considering the first one is $null:
# DisplayName = "CN=MyServicePrincipalCert"

PS C:\> @{ id = "id"; KeyCredentials = @(@{ Key = "Test Key"; DisplayName = "CN=MyServicePrincipalCert"})} | select KeyCredentials

KeyCredentials
--------------
{Test Key}

Actual behavior
PS C:\> @{ id = "id"; KeyCredentials = @(@{ Key = $null; DisplayName = "CN=MyServicePrincipalCert"})} | select KeyCredentials

KeyCredentials
--------------
{}
# this {} is surprising to me. Is the array empty? Is there nothing? No! There's something

PS C:\> @{ id = "id"; KeyCredentials = @(@{ Key = "Test Key"; DisplayName = "CN=MyServicePrincipalCert"})} | select KeyCredentials

KeyCredentials
--------------
{Test Key}

Workaround
Instead of using | select, if I access the property directly the hashtable output is clearer:
PS C:\> $Object1 = New-object psobject -Property @{ id = "id"; KeyCredentials = @(@{ Key = $null; DisplayName = "CN=MyServicePrincipalCert"})}
PS C:\> $object1.KeyCredentials

Name                           Value
----                           -----
DisplayName                    CN=MyServicePrincipalCert
Key

Error details
None

Environment data
PS C:\> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      7.4.0-preview.1
PSEdition                      Core
GitCommitId                    7.4.0-preview.1
OS                             Microsoft Windows 10.0.19045
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Visuals
No response

Conceptually related:

#17683

I haven't looked at the source code, but it appears that there is hard-coded logic in the formatting system for properties whose array elements happen to be of type [hashtable]: they are rendered by the value of an entry whose key is 'Key', if present, and otherwise by the value of whatever happens to be the first entry in the (inherently unordered) hash table.
By contrast, [ordered] hashtables and [System.Collections.Generic.Dictionary[T1, T2]] instances (unhelpfully) stringify by their type name (i.e. they are rendered with .ToString()).

Bug still valid with latest version:
PS C:\> @{ id = "id"; KeyCredentials = @(@{ Key = $null; DisplayName = "CN=MyServicePrincipalCert"})} | select KeyCredentials

KeyCredentials
--------------
{}

PS C:\> @{ id = "id"; KeyCredentials = @(@{ Key = "Test Key"; DisplayName = "CN=MyServicePrincipalCert"})} | select KeyCredentials

KeyCredentials
--------------
{Test Key}

PS C:\> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      7.3.9
PSEdition                      Core
GitCommitId                    7.3.9
OS                             Microsoft Windows 10.0.22621
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Same with 7.4.2:
PS C:\> @{ id = "id"; KeyCredentials = @(@{ Key = $null; DisplayName = "CN=MyServicePrincipalCert"})} | select KeyCredentials

KeyCredentials
--------------
{}

PS C:\> @{ id = "id"; KeyCredentials = @(@{ Key = "Test Key"; DisplayName = "CN=MyServicePrincipalCert"})} | select KeyCredentials

KeyCredentials
--------------
{Test Key}

PS C:\> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      7.4.2
PSEdition                      Core
GitCommitId                    7.4.2
OS                             Microsoft Windows 10.0.22621
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0


added api keys as headers for all grpc messages

What does this PR change?

Does the PR depend on any other PRs or Issues? If yes, please list them.

126

Checklist
I confirm, that I have...

[ ] Read and followed the contributing guide in CONTRIBUTING.md
[ ] Added tests for this PR
[ ] Formatted the code using go fmt (if applicable)
[ ] Updated documentation on the Paralus docs site (if applicable)
[ ] Updated CHANGELOG.md

Codecov Report

Merging #163 (a5ff0c0) into main (aba1dd8) will decrease coverage by 0.21%.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #163      +/-   ##
==========================================
- Coverage   34.66%   34.45%   -0.21%
==========================================
  Files          74       74
  Lines       11682    11682
==========================================
- Hits         4049     4025      -24
- Misses       7084     7113      +29
+ Partials      549      544       -5

see 1 file with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Remove unnecessary namespace prefixes in code

Though already imported
https://github.com/datafuselabs/opendal/blob/7848fbc17ef60765aef6c9026566a356cec64fa3/src/services/gcs/backend.rs#L25
Some unnecessary namespace prefixes are still represented in the code
https://github.com/datafuselabs/opendal/blob/7848fbc17ef60765aef6c9026566a356cec64fa3/src/services/gcs/backend.rs#L434
https://github.com/datafuselabs/opendal/blob/7848fbc17ef60765aef6c9026566a356cec64fa3/src/services/gcs/backend.rs#L452
Originally raised by @ClSlaid in https://github.com/datafuselabs/opendal/pull/526#discussion_r946380497

/assignme

Lint error is found, but the linter does not warn. Looks strange.
cargo clippy --workspace --all-targets --all-features -- -D warnings

https://github.com/datafuselabs/opendal/blob/main/src/services/obs/backend.rs#L347

Lint error is found, but the linter does not warn. Looks strange.
cargo clippy --workspace --all-targets --all-features -- -D warnings

https://github.com/datafuselabs/opendal/blob/main/src/services/obs/backend.rs#L347

Issue submitted https://github.com/rust-lang/rust-clippy/issues/9372

Please leave this issue open before all lint errors are fixed.

Updated https://github.com/rust-lang/rust/issues/100979

I prefer to close this issue now. We need to wait for rust.
If rust has fixed this, we will see the warning again. And until then, we will fix this.


adds a composable component

This PR adds a the compose branch back to to repo to support the updates we are doing to this blog

@martinbonnin 👋

Sorry I missed that one! Looking into it now.

@martinbonnin 👋 I pushed up the final changes, I think this is finished! DO we just leave this branch un-merged as it's going to be reference from the blog?

@martinbonnin 👋 I pushed up the final changes, I think this is finished! DO we just leave this branch un-merged as it's going to be reference from the blog?

I think so. Until we rewrite the full tutorial, an un-merged branch seems 👌 . I'll protect this branch to make sure it doesn't get deleted

Superseded by #39. Thanks for looking into this ❤


Add mux for thruster and fin commands

This PR add a multiplexer with priorities for thruster and fin commands.
The priority was set as:

mission_control -> autopilot subsystem. * Low priority *
OCU -> jaus_ros_bridge subsystem. * High priority *
This priority can be changed in actuator_mux.yaml file

The Mux publishes which input is in control in the topic "active" on
/CmdActuatorMuxNodelet/fin_angle_active
/CmdActuatorMuxNodelet/set_rpm_active
This PR was tested on the vehicle.

close PR. It was integrated and applyed in #160


28 July Meeting Points

Is there a documentation on Nathaniel's freeze and how it was generated?
Starting from moving the necessary components to work as a package (data, dependencies etc) -> one of the aims and good for maintainability (eg. can't overwrite shiny functions if you want to work as a package)
Note that current data generation relies on a mix of live API calls and nathaniel's freeze
Should the resulting package be entirely self contained? There seems to be data sources we might not be allowed to share (drugbank)

My 2p, and some asterisks that I can think of:

I have a couple non-production forks of packages used in the original code (shinypanels, maybe async, maybe one other that I should have made note of in dependencies.R). This will likely complicate acceptance on Bioconductor, and packaging in general.
It's likely to work more efficiently on Linux machines due to some async usages IIRC, and I believe it also has non-R dependencies (specifically for Rfast IIRC) which may limit users
My personal opinion is that it would be nice to package up the enrichment algorithm aside from the Shiny app so that users can just run it programmatically without all the fat of the Shiny app (which introduces the majority of the hard-to-get-Bioc-approved stuff). Unless the big picture is to fully democratize access outside of just PavLab servers.

For your 3rd point, Paul's plan seems to involve making a package that makes API calls to a server on our end which runs the analysis. The main driver for this approach, to my understanding is the data size. It does make a few things easier such as keeping your own forks in without anyone complaining.


Give the possibility of working with HTML only

I think completely possible, just need to implement logic for other content type.
#/8e38e

By having the JSON wrapper though you have more options for how to use that data perhaps from other tools than eldarion-ajax in parallel.  What is the motivation for this?

I only have the option to work with html. The server side can only return html and as there is no way to configure it in "eldarion-ajax", so I thought it would be a good proposition for you.
Even because your plugin will be more flexible if you give the possibility to work with other content.


enh(multi-actions assistant builder): bury action name in advanced

Description
fixes https://github.com/dust-tt/dust/issues/5438

Risk
N/A
Deploy Plan
N/A

Can we have it at the top 😬

@spolu not a gigantic fan but I don't mind

I would maybe align it right to make it less "in your face" ?
It's just that action name at the bottom is not super logic, but maybe anything else is bad.
In Instructions we do have the advanced at the top though and it works well?

But that likely mean it's a dropdown

Input in a dropdown not that great though no ?

I think we should invoke @Duncid

Maybe same design as the advanced settings we have on the Instructions screen?

See new screenshot in OP @PopDaph @spolu


[dashboard widgets] Add "multi_compute" field to dashboard logs queries

The current "compute" field is a single object, but we need multiple "compute" aggregations for the columns of the table widget. To solve this problem without doing a painful migration of the type of the "compute" field, we decided to add a field called multi_compute which contains an array of "compute" objects. This validation is already in place in the dashboards backend, and this PR adds it to the Go API.

LGTM, merging. Thanks for the PR!


Support ClExpr

Description
Support for ClExpr
Related issues
#175
Checklist

[x] I have performed a self-review of my code.
[x] I have commented hard-to-understand parts of my code.
[x] I have made corresponding changes to the public API documentation.
[x] I have added tests that prove my fix is effective or that my feature works.
[x] I have updated the changelog with any user-facing changes.

Thanks for the pointers on the semantics for the undefined operations. I will add these, and throw an error on overflow for now. I will bring up the need to agree on semantics of these extended QASM operations in the cross-team standup today.


Custom UIDynamics / Disable wobble animation

Maybe others would like to disable the wobble effect from UIDynamics?
Set uiDynamics in SPPermissionDialogDataSource to 1.0 to disable the wobble animation.
(#47)

Good day!
Please, change source code not in example. See ‘source’. If you can not do it, I can do it after merge.
Wait your response.

I see details preview. For disable UIDynamics animation need set start translation to zero. When in your project set 1.0 for uiDynamics - translation not do.
I think more  clear will be customise startTranslation or other parameter.
But for now property uiDynamics not change anything for dynamic animation.
Thanks!
If need, I can implement it. Or you)


"Gulp build" removes assets from production.js

(Sorry for my english)
I just finished my Mean.JS application and i try to pull it in production mode on my web server.
When i try to run "grunt prod" or "gulp prod", it removes some assets from my production.js and default.js files like jquery.js or bootstrap.js before build, so my website doesn't work properly.
Thanks for help

@Eswan we're deprecating Grunt for Gulp so can you please describe the problem better with sharing the code you've added that gets removed?

Here is my production.js asset file before i run "gulp prod" command : http://hpics.li/f8feeaf
Then after i run this command : http://hpics.li/07f8dec
As you can see, theses two lines has been removed from js assets :
'public/lib/jquery/dist/jquery.min.js',
'public/lib/bootstrap/dist/js/bootstrap.min.js',
jQuery and Bootstrap aren't include in application.min.js so i have multiples error like "$ not defined..."
Here gulpfile.js code : http://hpics.li/e72d3bb, maybe this part is the origin of my problem ?
Thanks

I just resolved my problem by adding bootstrap and jquery in "overrides" attribute in bower.json

Thanks for the update @Eswan

@Eswan i have same problem :(
can i get your bower.json ?

Thanks! solved my problem.
here is "overrides" in my bower.json
  "overrides": {
    "bootstrap": {
      "main": [
        "less/!(variables).less",
        "dist/fonts/*",
        "dist/js/*",
        "dist/css/bootstrap.css",
        "dist/css/bootstrap-theme.css",
        "less/bootstrap.less"
      ]
    },
    "jquery": {
      "main": [
        "dist/*.js"
      ]
    }
  },

thanks


Should have TLS FV tests including IP SANs

Looks like we have a gap in our testing of the policy agent in that we don't have tests for TLS or IP SAN support when talking to etcd or the k8s API server.  (The two communication channels use different libs so we need to test both.)
TLS might be covered in another repo (which is fine), but #69 shows that we have a  gap.

Now that we're using k8s client-go and Calico libcalico for both API + etcd access I think this function is tested in other repos.