Angular 2 and Slideout

Hi,
I have tried to use slideout with angular2 and I have some difficulties and errors.
I have install slideout by npm install. Add slideout in typings (typings install...). Then, in my page.component.ts, import slideout
import 'slideout';
then in the ngOnInit() :
this.slideout = new Slideout(                 {                     'panel':  this.element.nativeElement.querySelector('main'),                     'menu':  this.element.nativeElement.querySelector('nav'),                     'padding': 256,                     'tolerance': 70                 });
Next, in the page.component.scss, add class in the css :
`.slideout-menu {
position: fixed;
left: 0;
top: 0;
bottom: 0;
right: 0;
z-index: 0;
width: 256px;
overflow-y: auto;
-webkit-overflow-scrolling: touch;
display: none;
}
  .slideout-panel {
    position:relative;
    z-index: 1;
    will-change: transform;
}

  .slideout-open,
  .slideout-open body,
  .slideout-open .slideout-panel {
    overflow: hidden;
}

  .slideout-open .slideout-menu {
    display: block;
}`

I save all, compile, and access the page in my browser chrome. I have the following error :
EXCEPTION: Slideout is not defined
Do I miss something here ? Is slideout compatible with angular2 ?
Thanks for any help.

Hi @gillouneos, Could you try to import the module like this?
import Slideout from 'slideout';

Hi @pazguille
I think Slideout is not a module. So it cannot compile.
Error : [ts] Module 'slideout' has no default export.

Hey @gillouneos, Did you try const Slideout = require('slideout');?

@gillouneos @pazguille any word on the final solution?

I have given up right now. Sorry. But if you find out, please, tell me how.

Hello, I am using Webpack Module Bundler and I have added this plugin to the plugins,
and Now it is working with me :)
 new webpack.ProvidePlugin({
   Slideout: "slideout"
 })

As well as in the component.ts
import 'slideout';
declare var Slideout:any;

I think there is maybe something in SystemJS to make like what I made in Webpack


Update cats-effect to 2.5.1

Updates org.typelevel:cats-effect from 2.1.4 to 2.5.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Applied Migrations

github:typelevel/cats-effect/v2_4_0?sha=v2.4.0

Documentation:

https://github.com/typelevel/cats-effect/blob/v2.4.0/scalafix/README.md

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel", artifactId = "cats-effect" } ]

labels: library-update, semver-minor, scalafix-migrations

Superseded by #186.


Erratic PWM behavior

I've been unable to read the current duty cycle percentage.
#include "mraa.hpp"
#include <unistd.h>

int main(){
    mraa::Pwm* led;

    led = new mraa::Pwm(3);
    if(led == NULL){
        return MRAA_ERROR_UNSPECIFIED;
    }

    led->enable(true);

    led->write(0.90);
    fprintf(stdout, "%f\n", led->read());

    sleep(2);

    led->write(0.40);
    fprintf(stdout, "%f\n", led->read());

    sleep(2);

    led->enable(false);
    led->~Pwm();
}

This should:
Turn on the led
Set the duty cycle to 90%
Set the duty cycle to 25%
Turn off the led
This does not work. In fact it looks as if the led changes to 100% upon exiting.
However if I set the duty cycle to 1% prior to disabling the led. It will turn off.
There is no log message generated.

Hello dandyd449,
What board did you use?
I'm using a Galileo v1 and just compiled your code:
g++ -lmraa pwm_test.cpp
and works for me.
Here is my output:
oot@galileo:~/c++_tests# ./a.out
0.899998
0.400000
regarding the led->enable(false); i don't think it should turn off the LED. The reason for this is because what pwm does is to refer to the /sys pwm chip as mapped in kernel:
// from mraa/src/pwm/pwm.c after cloning mraa
snprintf(bu, MAX_SIZE, "/sys/class/pwm/pwmchip%d/pwm%d/enable", dev->chipid, dev->pin);
//... then open the file:
int period_f = open(bu, O_RDWR);
//... then write to it:
if (write(period_f, out, length * sizeof(char)) == -1) {
...
What i'm saying is that i tried manually by setting the pwm enable file in /sys fs and i get the same behaviour. To shut down the led, i used the Gpio part of mraa, but from python(it was easier for me):
import mraa as m

gpio = m.Gpio(3);
gpio.dir(m.DIR_OUT)
gpio.write(0)

Costin

Based on previous issues filed this is on the edsion yes? There is an outstanding issue with the PWM device is that if disabled it acts as a HIGH pin.
There is a patch in the works that works when the pin is being set to a duty of 0% the pin is to change mode into a GPIO and be set to LOW

That is correct. This is an edison.
Whats curious is why it seemly works if I set the duty to 1% prior to led->enable(false) and why at 0% it still outputs something. I look forward to this patch for sure. I was very close to abandoning the platform for something else.
Thanks!

Sorry for the delay in getting to this.
If you could please upgrade your Edison firmware, the team working on the Kernel drivers seems to have fixed a number of issues regarding PWM, making it behave in a much more predictable manner.
https://software.intel.com/en-us/iot/hardware/edison/downloads
Again if you still have the issue, feel free to re-open and Ill try and see whats wrong :)

I was already on the current version. But just in case I reloaded the firmware.
root@edison:~# configure_edison --version
146
root@edison:~# configure_edison --latest-version
146

I still have this issue.

I am also unable to reopen the ticket.

So the problem is with the Kernel for the PWM, on internal newer versions this seems to be fixed, im going to confirm and hope they release it soon.


Add a link to install Azure PowerShell

Something like this at the top of the tab:

Please install the latest Azure PowerShell from here.

Done and live in Staging


Gluster Not releaseing pvcs, showing failed

Err message VolumeFailedDelete: persistenvolume-controller Unable to delete vol_: Unable to execute command on glusterfs- volume delete:
failed: some of the peers are down.
I exec'ed into the container and one of the peers was in fact down. I am not sure why a peer would be down, I did reset the kubelet, but the containers came back and everything reported to be running from the initial kubectl get all. How do I go about debugging this further?

Peer reported "Disconnected"

After closer inspection it looks like I may have labeled a gluster node where the ip and name of the node don't match up. Can I fix this or do I need to tear it all down and start over?

Just going to tear it down. nevermind. Sorry to spam.


Add/update eslint plugin dependencies across repo

Adding dependencies pre-emptively because they'll be needed once #9748 is merged and applied.

This is gross 😕 Are we not able to pull in the dependencies through the eslint-config-fluid package?  Or does that count as a transitive dependency that we need to explicitly specify because of how the tsconfigs from eslint-config-fluid are used?

BTW, this is how eslint works by default -- plugins are resolved relative to the local package, not relative to the parent (inherited) config package, and they punted on changing that. So without the rushstack modern-module-resolution patch, everyone using shared configs has this problem. :(

i don't know if it is right or wrong, but what i did with type validation only requires tools to be installed at the root. this has the downside of not being able to build packages directly, but keeps our packages light weight and easy to maintain in terms to tooling. we could consider something similar with eslint.


Update aws-java-sdk-dynamodb to 1.12.125

Updates com.amazonaws:aws-java-sdk-dynamodb from 1.11.1034 to 1.12.125.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.amazonaws", artifactId = "aws-java-sdk-dynamodb" } ]

labels: library-update, early-semver-minor, semver-spec-minor

Superseded by #197.


useMenu CORS in local

useMenu in layout page
Access to fetch at 'http://local.nextjs.com:8888/jsonapi/menu_items/main' from origin 'http://localhost:3000' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
index.esm.js?84fa:186 GET http://local.nextjs.com:8888/jsonapi/menu_items/main net::ERR_FAILED

@ambercit Do you have CORS enabled?

https://www.drupal.org/node/2715637
https://drupal.stackexchange.com/questions/245903/how-do-i-set-up-cors

@ambercit did you figure this out?

@shadcn we solve by the links you offer，is this will support drupal  layout build later

@ambercit For Layout Builder we are currently blocked by this issue: Expose Layout Builder data to REST and JSON:API


feat(footer): slot alignment

Describe pull-request

Aligned the naming of the slots in the footer
Added docs for slots in readme.

Solving issue
Fixes: https://tegel.atlassian.net/browse/DTS-2021
How to test

Go to Footer
Check in Notes
Check the slots section
Test the top part controls
Make sure the styling is correct.

How do we feel about naming here? Are the slots named correctly?

Not sure if this is part of this PR, but it seems like the top part of the footer gets the primary mode variant background color even when put in secondary mode

I think it's due to the top part not having a secondary variant in dark mode? Can't find one in design


Feature Request: pyscript.reload to support new files.

Currently, calling pyscript.reload with a global_ctx= set to a newly created file results in an error indicating the global context cannot be found, which makes sense because a full reload hasn't happened yet so that global context has never been loaded, and, therefore, can't be reloaded.
For deleted files, pyscript.reload works just fine. The global_ctx is unloaded and, since the file no longer exists, is not reloaded.
It would be great if reload could look for the new file and cause it to load. Optionally, pyscript.load could be used instead to establish a difference between a new file and a reload. Though, if this happens, I suggest that reload does not work on deleted files and a pyscript.unload gets added.
This is a nice stepping stone to having full autoREload support in pyscript since this functionality will be needed for that.

Good points.  Actually, how about reload (with no params) looks for differences (comparing file contents and maybe mtimes, and checking for new and deleted files) and just makes the minimum changes - unloads deleted files, reloads changed files, and loads new files?  Files with no changes aren't touched.
The existing global_ctx param could be a force reload (even if no changes), and also handle the new file case as you mention.  We could also use global_ctx='*' to force reload everything.
It make the default of plain reload do what you want 99% of the time (although it would be a breaking change).

That is EVEN BETTER! This way, if something changes, just call reload and it will do what is needed.
And yes, on Linux, with #74, reload won't be needed manually. But, the logic inside reload is likely the SAME logic that will be needed when #74 detects a change. So the code itself will still be used.
Some harder questions: YAML and modules.
When a module (in pyscript/modules) changes, a reload to modules.filename reloads the module, but any existing scripts using that module hold on to the old copy until they are also reloaded. If modules.filename is NOT reloaded, then reloading the script file does NOT cause the new module file to be used. To sum up, both the module AND the script using the module need to be reloaded in order to really see the module changes. Since pyscript already dips into how "import" works, is there a way to track the imports each script uses and, if that import is a module and that module is reloaded, also reload the script?
When YAML changes, reloading JUST the script that uses the YAML results in that script seeing the new YAML. This is great. Is there anyway to detect when YAML changes? If so, could the old YAML be compared to the new YAML and if changes are detected at pyscript/apps/appname then apps.appname would be reloaded as well? This doesn't affect me directly in most cases, because I use a different YAML format than the convention suggested by pyscript because I like to separate my YAML by functionality. So I use pyscript/apps_list/[{app: appname, a: 1}, {app: appname, a: 2}] format instead. I think the only way to get MY YAML usage to autoreload would be some kind of YAML registration function called in the app code to indicate which parts of YAML it uses. But I can write that in user code if there's a way to detect YAML changes.
For YAML changes, what if there was a @time_trigger('reload')? Somewhere during pyscript.reload new YAML is picked up. Even if pyscript is unable to detect changes, if @time_trigger('reload') was triggered on ANY reload, then user code could pull in YAML, compare as needed and call pyscript.reload on anything that needed reloading.  This way, if I change the YAML, I only need to call pyscript.reload manually to get those changes to be picked up and all the things that need to reload could do so.

I just pushed a significant rewrite of reload.  It now only reloads changes, and changes do include an app's configuration.  A changed module/package causes any scripts, apps or other modules to be reloaded too if they import (directly or indirectly) the changed module.
While this is a breaking change, the old behavior can be forced with global_ctx set to *.

!!!! Thank you!
I'll pull "master" this morning and test it.

This worked perfectly with everything I threw at it.

changes made in pyscript/scripts/somefile.py
changes made in pyscript/somefile.py
changes made in pyscript/apps/someapp/init.py
changes made in pyscript/modules/somemodule.py (which also reloaded scripts that imported it)
commenting out (#) a file name
commenting out (#) a directory name
creating a new file
deleting a file

In each case, above, after making changes, I only called "pyscript.reload" with no parameters.
The only request I have, and it's not a big deal, is... when a script is loaded a message of "Loaded /config/pyscript/test.py" is generated. This is useful to know that something loaded (or reloaded). However, when a script is deleted (so, unloaded and then NOT reloaded), there is no confirmation in the log.
Adding a "Unloaded /config/pyscript/test.py" log message would be useful. If this happens before the "Loaded" log line on a reload (because it is both unloaded and then loaded) that's okay. Optionally, the log could say "Loaded", "Unloaded", or "Reloaded", depending on which of the three things are happening.

Another thing I just tested that worked perfectly...
If a script has an exception during load (not in a trigger function, but in the code that defines trigger functions), then pyscript does NOT count it as loaded. So the next call to reload will try to load that file again, even if no changes have been made to the file.
I tested it like this:
CNT = 0

if pyscript.manually_set == "on":
    @time_trigger("period('2020-01-01',1)")
    def counter():
        global CNT
        CNT = CNT + 1
        log.info(f"7 Counter at {CNT}")

pyscript.manually_set did not exist in my system. Every time I issued pyscript.reload I'd correctly see:
Exception in </config/pyscript/test.py> line 3:
    if pyscript.manually_set == "on":
       ^
NameError: name 'pyscript.manually_set' is not defined

Once I manually set that entity and value, I issued pyscript.reload again and the script started up as expected.

I was able to reduce the complexity of my own file change "watchdog" script thanks to these changes to reload. Together, they are working exactly as expected.
https://gist.github.com/dlashua/f7d88f9a5afdcf7af17ce24266925a0b

Reworked the watchdog to use aionotify instead. This should be easier to incorporate into pyscript core if desired.
https://gist.github.com/dlashua/f7d88f9a5afdcf7af17ce24266925a0b
The except OSErrors are there because I couldn't get it to be reliable if it was going to flag a renamed directory with MOVE_SELF, MOVED_FROM, or BOTH, and the second attempt to "unwatch" would fail because it was no longer being watched because of the first attempt.

I pushed a commit that now logs Loaded/Unloaded/Reloaded.  Note that a change to something that is imported (eg, a module or a sub-file in an app) will separately report Unloaded then Loaded (rather than a single Reloaded), since reload just unloads those files and they only get loaded later when the code executes the import (eg, it could be the new code doesn't even do the import anymore, in which case you would see Unloaded and no Loaded).


[$300 bounty] Ford Q3 Hybrids have occasional incorrect PCM message checksums

This is causing controls mismatches for some users, including at least a Maverick and Escape. Haven't hit it on our Bronco yet however. I checked all three message checksums we check in panda (one from RCM, one from ABS, and one from PCM) and only the PCM message has these mismatches (it's behind a gateway, other two are on the same bus...).
Results: 2114
f8eaaccd2a90aef8|2023-05-05--12-27-53--18  FORD ESCAPE 4TH GEN    addr 0x202: 1 mismatches / 3000 msgs
f8eaaccd2a90aef8|2023-05-05--12-58-21--10  FORD ESCAPE 4TH GEN    addr 0x202: 1 mismatches / 2999 msgs
bd37e43731e5964b|2023-05-05--21-42-22--19  FORD MAVERICK 1ST GEN  addr 0x202: 3 mismatches / 3000 msgs
f8eaaccd2a90aef8|2023-05-05--12-27-53--22  FORD ESCAPE 4TH GEN    addr 0x202: 3 mismatches / 3000 msgs
933ad9d04ac82693|2023-02-08--09-19-55--22  FORD MAVERICK 1ST GEN  addr 0x202: 1 mismatches / 3000 msgs
f8eaaccd2a90aef8|2023-05-05--12-58-21--192 FORD ESCAPE 4TH GEN    addr 0x202: 2 mismatches / 2999 msgs
bd37e43731e5964b|2023-05-05--21-42-22--7   FORD MAVERICK 1ST GEN  addr 0x202: 1 mismatches / 3000 msgs
933ad9d04ac82693|2023-03-23--12-18-36--15  FORD MAVERICK 1ST GEN  addr 0x202: 1 mismatches / 2999 msgs
bd37e43731e5964b|2023-05-04--17-29-57--31  FORD MAVERICK 1ST GEN  addr 0x202: 1 mismatches / 3000 msgs
933ad9d04ac82693|2023-03-07--15-35-14--16  FORD MAVERICK 1ST GEN  addr 0x202: 1 mismatches / 3000 msgs
bd37e43731e5964b|2023-05-05--21-42-22--20  FORD MAVERICK 1ST GEN  addr 0x202: 1 mismatches / 3000 msgs
bd37e43731e5964b|2023-05-05--16-59-49--26  FORD MAVERICK 1ST GEN  addr 0x202: 1 mismatches / 3000 msgs
bd37e43731e5964b|2023-05-04--20-59-54--8   FORD MAVERICK 1ST GEN  addr 0x202: 1 mismatches / 3000 msgs
bd37e43731e5964b|2023-05-04--17-29-57--18  FORD MAVERICK 1ST GEN  addr 0x202: 2 mismatches / 3000 msgs
bd37e43731e5964b|2023-05-04--12-06-21--5   FORD MAVERICK 1ST GEN  addr 0x202: 2 mismatches / 3000 msgs
bd37e43731e5964b|2023-05-05--21-42-22--27  FORD MAVERICK 1ST GEN  addr 0x202: 1 mismatches / 2999 msgs

Matches by addr {514: 6199603, 1045: 6211839, 145: 12395638}
Mismatches by addr {514: 23793, 1045: 0, 145: 0}

Checked segments:
FORD BRONCO SPORT 1ST GEN 793
FORD FOCUS 4TH GEN 147
FORD ESCAPE 4TH GEN 243
FORD EXPLORER 6TH GEN 205
FORD MAVERICK 1ST GEN 726

Checked dongles:
FORD BRONCO SPORT 1ST GEN 4
FORD FOCUS 4TH GEN 1
FORD ESCAPE 4TH GEN 3
FORD EXPLORER 6TH GEN 4
FORD MAVERICK 1ST GEN 3

Checked platforms:
FORD BRONCO SPORT 1ST GEN {'54827bf84c38b14f': 717, '62241b0c7fea4589': 38, 'bbe75f19590890c4': 33, '5a08e8ef78cebd9f': 5}
FORD FOCUS 4TH GEN {'86d00e12925f4df7': 147}
FORD ESCAPE 4TH GEN {'f8eaaccd2a90aef8': 205, '26b2cace68e36212': 34, '62241b0c7fea4589': 4}
FORD EXPLORER 6TH GEN {'59a107f5793d9cc0': 22, '62241b0c7fea4589': 16, 'f0709d2bc6ca451f': 151, '8e1bab39e558e773': 16}
FORD MAVERICK 1ST GEN {'bd37e43731e5964b': 374, 'c845bd8c366e6f3d': 96, '933ad9d04ac82693': 256}

No reason to make a new duplicate issue for this

Is this going to be in before 1.0?  I can get whatever data is needed to help you solve it.

Is there anything we can do about this?

The bounty is for root causing the incorrect checksums and getting the Hybrids shipped.

@adeebshihadeh do you have any suggestions for getting a repro, I have force-enabled my hybrid and have yet to see an error present in the UI. Would it be in the logs somewhere under some recognizable tag or message?

Matt the gas for a few seconds is 100% reproduce or ACC acceleration from 60 to 80mph is like 75% reproduce. I can get you some more logs. If you look on the discord at #ford hybrid broke there is the story

I did a lot of work around this in the comma discord. Adeeb banned me, so forgive me if I remember incorrectly. It should be under Ford then a thread for "Ford hybrid broke".
I took the messages that Koopa got behind the gateway for the different BUSes and then ran through all the messages on Identifier 514 (hex 0x202) for checksum issues:

Anyways most if not all the data is in that thread.

Matt the gas for a few seconds is 100% reproduce or ACC acceleration from 60 to 80mph is like 75% reproduce. I can get you some more logs. If you look on the discord at #ford hybrid broke there is the story

Mash the gas? Tap the gas? Sorry

Matt the gas for a few seconds is 100% reproduce or ACC acceleration from 60 to 80mph is like 75% reproduce. I can get you some more logs. If you look on the discord at #ford hybrid broke there is the story

Mash the gas? Tap the gas? Sorry

100% full throttle for a few seconds will rack up enough mismatches to throw an error.  Also, it is a safety concern that code is blocked while mismatches count up.  You get a good half a second or so of comma holding course regardless of whatever is changing on the road.

@ncoop23 i full throttled for several seconds several times and never got any messages on the comma via UI
Does it only present in logs?

@ncoop23 i full throttled for several seconds several times and never got any messages on the comma via UI
Does it only present in logs?

What is your vehicle?  This only happens on Hybrids that have the mobile eye v3

on

2023 Ford Maverick Hybrid

on

2023 Ford Maverick Hybrid

This is good news for you and could solve the issue for others. Can you get a drive to do public share of the route?

on

2023 Ford Maverick Hybrid

Can you share a route of you going 100 throttle from 50 to 80 mph on the freeway?

Yes, let me get that tomorrow

on

2023 Ford Maverick Hybrid

Can you share a route of you going 100 throttle from 50 to 80 mph on the freeway?

I can't use the gas pedal can I? I just thought this 😂

on

2023 Ford Maverick Hybrid

Can you share a route of you going 100 throttle from 50 to 80 mph on the freeway?

I can't use the gas pedal can I? I just thought this 😂

If comma is engaged, you can still steer and use the gas pedal.  If you hit the brake it will disable.  Think passing a car, you can have comma engaged and turn signal and hit the gas to get around a guy.
What we need is you to record a log of going like 50 with comma engaged on the freeway and go 100% throttle till you are going as fast as you are able to go safely.  Ideally 80 mph or more.  If you could start lower than 50 mph, it would help.
I ran some when the freeway was empty early on a weekend morning by pulling off the road till there was a large opening, then getting aligned in a lane, setting comma and matting the gas till I was going as fast as was safe to trigger the error more than once.   If it pops up with a controls mismatch error, press resume for your cruise control and keep accelerating if possible.

on

2023 Ford Maverick Hybrid

Can you share a route of you going 100 throttle from 50 to 80 mph on the freeway?

I can't use the gas pedal can I? I just thought this 😂

Any luck with the route?

I got a 2022 Ford Escape Plug in hybrid with the code change to get out of dashcam etc.  Using Sunnypilot currently.  I could try some time.  Do car testers get any part of the bounty?  Just curious.  I work night shift so may not be until 11PM.

I got a 2022 Ford Escape Plug in hybrid with the code change to get out of dashcam etc. Using Sunnypilot currently. I could try some time to do such a run on my commute route. Do car testers get any part of the bounty? Just curious. I work night shift so may not be until 11PM. I have a week or two old Comma 3X.

When you floor it for a couple seconds with comma active, do you get a controls mismatch error?

I have an Escape SE (not titanium) 2021 without ACC. Only have Cruise Control and Line Assist. Can work in this car?

I have an Escape SE (not titanium) 2021 without ACC. Only have Cruise Control and Line Assist. Can work in this car?

If you add acc. I'd look at the escape forum for that.

The on-ramp I take is a circle so I can turn cruise/pilot on but have to help it steer since it’s over steering limit.  Do you want me to do in all electric mode or both mode?  I assume both gas and electric combined.  I have some old logs of gassing it but I’ll plan on doing one in the morning and try to get that out to you.On Feb 21, 2024, at 3:33 PM, InfoIntegra @.***> wrote:
I have an Escape SE (not titanium) 2021 without ACC. Only have Cruise Control and Line Assist. Can work in this car?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

The on-ramp I take is a circle so I can turn cruise/pilot on but have to help it steer since it’s over steering limit.  Do you want me to do in all electric mode or both mode?  I assume both gas and electric combined.  I have some old logs of gassing it but I’ll plan on doing one in the morning and try to get that out to you.On Feb 21, 2024, at 3:33 PM, InfoIntegra @.> wrote: I have an Escape SE (not titanium) 2021 without ACC. Only have Cruise Control and Line Assist. Can work in this car? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.>

The plug in hybrid is a bit different. This error is for normal hybrids but your log would be helpful. Ideally, the best log would be to:
find a location on the side of an empty freeway early on a weekend morning, pull off the side of the road and stop. Put on hazard's.  Wait for cars to clear,  pull out into a lane, accelerate to 20 mph, turn on cruise/comma, floor the gas 100% until about 70-80 depending on speed limits in your area.

You mean Only have Cruise Control and Line Assist Can work in this car? Please tell me how! i tried everything!
This is the error:

Please get on discord app and go to the Ford channel and someone can point you in the right direction.  You may need to add a module to your car. This is unrelated to the topic of this issue though.

Yes, i ask in Ford Channel but nobody knows why do not work.

I took a 200 mile trip and had cruise control with speed limit 75.  Steep hill and it had to high rpm and I saw it cut out with me having to enable again 2 or 3 times.  Was the only time on trip.  When I got to destination I tried to see trip pop up in feed but it did not yet.  I took device out of my car and can try to yank it off once I get somewhere tomorrow.On Feb 23, 2024, at 10:40 AM, ncoop23 @.***> wrote:
The on-ramp I take is a circle so I can turn cruise/pilot on but have to help it steer since it’s over steering limit.  Do you want me to do in all electric mode or both mode?  I assume both gas and electric combined.  I have some old logs of gassing it but I’ll plan on doing one in the morning and try to get that out to you.On Feb 21, 2024, at 3:33 PM, InfoIntegra @.> wrote: I have an Escape SE (not titanium) 2021 without ACC. Only have Cruise Control and Line Assist. Can work in this car? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.>
The plug in hybrid is a bit different. This error is for normal hybrids but your log would be helpful. Ideally, the best log would be to:
find a location on the side of an empty freeway early on a weekend morning, pull off the side of the road and stop. Put on hazard's.  Wait for cars to clear,  pull out into a lane, accelerate to 20 mph, turn on cruise/comma, floor the gas 100% until about 70-80 depending on speed limits in your area.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

I took a 200 mile trip and had cruise control with speed limit 75.  Steep hill and it had to high rpm and I saw it cut out with me having to enable again 2 or 3 times.  Was the only time on trip.  When I got to destination I tried to see trip pop up in feed but it did not yet.  I took device out of my car and can try to yank it off once I get somewhere tomorrow.On Feb 23, 2024, at 10:40 AM, ncoop23 @.> wrote: The on-ramp I take is a circle so I can turn cruise/pilot on but have to help it steer since it’s over steering limit.  Do you want me to do in all electric mode or both mode?  I assume both gas and electric combined.  I have some old logs of gassing it but I’ll plan on doing one in the morning and try to get that out to you.On Feb 21, 2024, at 3:33 PM, InfoIntegra @.> wrote: I have an Escape SE (not titanium) 2021 without ACC. Only have Cruise Control and Line Assist. Can work in this car? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.> The plug in hybrid is a bit different. This error is for normal hybrids but your log would be helpful. Ideally, the best log would be to: find a location on the side of an empty freeway early on a weekend morning, pull off the side of the road and stop. Put on hazard's. Wait for cars to clear, pull out into a lane, accelerate to 20 mph, turn on cruise/comma, floor the gas 100% until about 70-80 depending on speed limits in your area. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.>

So comma basically agreed that sometimes an OEM message will be faulty and removed this message from the list of things that will boot you out of cruise.  I don't know if we will be able to get to the root of the issue ever though this works.  The steering is something that still needs love but that's for another ticket.


Whitespace changing

If I commit some code, then someone else commits and pushes, then I run git up so it rebases, sometimes the whitespace changes from 4 spaces to a tab.
Any ideas please?

git up  --ignore-whitespace
or
git rebase --whitespace=fix to have Git automatically fix whitespace issues as it’s rewriting the patches.


adding 400gzr testbed file to tb mapping

adding 400g zr testbed file to mapping for automatic allocation

This code is a Contribution to the OpenConfig Feature Profiles project ("Work") made under the Google Software Grant and Corporate Contributor License Agreement ("CLA") and governed by the Apache License 2.0. No other rights or licenses in or to any of Nokia’s intellectual property are granted for any other purpose. This code is provided on an "as is" basis without any warranties of any kind.

Pull Request Functional Test Report for #3449 / f42136cff64f16e2a0c8d7ebaa86535038aca5d6
No tests identified for validation.
Help

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.268%

Totals

Change from base Build<PHONE_NUMBER>1:
0.0%

Covered Lines:
1983

Relevant Lines:
3588

💛  - Coveralls


cmd/link: -ldflags -X option does not work with -linkshared

Please answer these questions before submitting your issue. Thanks!

What version of Go are you using (go version)?
go version devel +748aa84 Wed Aug 10 20:33:11 2016 +0000 linux/ppc64le

What operating system and processor architecture are you using (go env)?
ppc64le Ubuntu 16.04

What did you do?
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
Simple testcase:
test-setX.go:
package main

import (
"fmt"
)
var VERSION string
func main() {
fmt.Printf("Hello, World! Version is: %s\n", VERSION)
}
Make sure there is a shared std libary
go install -buildmode=shared std
go build -linkshared -ldflags '-X main.VERSION=123' test-setX.go

What did you expect to see?
Successful build and execution.  Output without -linkshared is:
./test-setX
Hello, World! Version is: 123

What did you see instead?
Program didn't build, error message was:
cannot use -X with non-string symbol main.VERSION type.TwVfYA92
(I modified src/cmd/link/internal/ld/data.go to print out the actual type at the end of the message.  That does not appear by default.)
I also just tried removing the test in data.go where this error message occurs, and then the program built successfully but panicked at runtime.

Pretty sure that type.TwVfYA92 is actually type.string, type symbols get their names compressed (in general, it's actually getting expanded here). A fix would be to not mangle type names when the mangling would in fact make the names longer (@crawshaw?)


Let's try Continuous Integration!

Recently, @bwbush, @paluh and I decided to do a trial of a continuous integration workflow, where we contribute commits directly to a mainline branch and regularly integrate work with one another. This is a placeholder PR to track differences from main.
Rules of this branch:

Push your work frequently (at least once a day, but preferably more regularly)
Pull (integrate) regularly and resolve any merge conflicts
Commit all work directly to this branch
Close JIRA tickets as they become "fixed" on this branch. Tag commits with a fixes SCP-xxx message when a commit addresses a JIRA ticket.
The absolute highest priority is maintaining a "Green" build status. If you break the build, fix it immediately!
Do pair programming if you need code review.

@jhbertra, should we put this PR into "draft" status and leave it there until we're ready to review and push to main?

@jhbertra, @paluh , this marlowe-run-development branch lets me restore a wallet and add contacts (which I see in local storage), but it doesn't display the contacts or let me use the in contracts.

@jhbertra, @paluh , this marlowe-run-development branch lets me restore a wallet and add contacts (which I see in local storage), but it doesn't display the contacts or let me use the in contracts.

Issue fixed


Please yank lobot 0.9.1 from rubygems

Ruby 1.9.3-p0
Bundler 1.1rc
Rubygems 1.8.10
(latest and greatest all around)
When we try to bundle with lobot in our Gemfile, bundler blows up because of the existence of lobot 0.9.1, which has bad metadata. It won't even use lobot 0.9.2 even when specified in the Gemfile and already installed into the gemset.
worth:~/workspace/scebusiness (master)$ bundle
Fetching gem metadata from http://rubygems.org/.
Unfortunately, the gem lobot (0.9.1) has an invalid gemspec. As a result, Bundler cannot install this Gemfile. Please ask the gem author to yank the bad version to fix this issue. For more information, see http://bit.ly/illformed-requirement.

I'd heard this might be a problem.  0.9.1 is now Yanked.
I <3 Rubygems.

Many thanks!


Fix loading snackbar while searching for a new word

Presently the loading snackbar is not properly connected to state. It doesn't wait for the result to arrive before getting dismissed.
Connect the snackbar to state, such that:

The loading snackbar keeps showing till a result has arrived.
The snackbar is dismissed as soon as a result has arrived from the API.

Hello!
May i take this on?

Hello!
May i take this on?

Since, it hasn't been solved it. Sure, why not!
Also, you might want to take a look at the project. If you find any potential improvement scopes/bugs, please open an issue. I would put the issue under hacktoberfest as well!
Thanks!


helmfile template doesn't pass release name to helm template

Need to call helm with --name of the release name when running helmfile template.  This is especially important if you are templating the release name and want to test the templating without installing into a stack.

Good catch! I think this is a bug. I'll try to fix it asap.


Prepend deployment name to hostname

If reporting from multiple deployments that happen to use the same job
names, Datadog will get confused.
For example, we have 2 Concourse deployments. Whichever instance starts
the datadog-agent jobs last will be considered the "real" e.g. worker.0
or db.0 and the other deployment will "refuse" to report metrics for that
instance name.

Great catch, thank you for fixing this!


L2: (Prover) test performance

Motivation
We need to track, measure and test the zkVMs to see if we can:

improve the performance
compare between different implementations
have time estimates

to fix your trouble check this solution click
maybe this will solve your problem.


Rename ParemeterError::NO_ERROR to ParameterError::SUCCESS

🦟 Bug fix
Fixes https://github.com/gazebosim/gz-transport/pull/305#issuecomment-1221045181.
Summary
To avoid conflicts with winerror.h macro.
Checklist

[x] Signed all commits for DCO
[ ] Added tests
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

testing with gz-transport in https://github.com/gazebosim/gz-transport/pull/349 using the following commits:

https://github.com/gazebosim/gz-transport/pull/349/commits/8ffcfd68721310421c9a490a18231e342b681c7d
https://github.com/gazebo-tooling/gazebodistro/commit/c3dd97a573bd7de45f1bb8d2a1cf76ae1aca54ec
https://github.com/osrf/homebrew-simulation/commit/a88134e7400aea018c7fe2492e86bf72c21ea8cb

ABI checker failure is expected and ok since these changes have not yet been released


ios TypeError:Attempted to assign to readonly property

webview Error

@Super-invincible sorry for late reply, please update to the latest version to solve the problem.

@Super-invincible sorry for late reply, please update to the latest version to solve the problem.

Hello,muff.I have updated to the latest. But it still returns the same mistake when i drag and drop it.

I think this is a compatibility issue with the Webkit browser. I'll fix it as soon as possible.

I think this is a compatibility issue with the Webkit browser. I'll fix it as soon as possible. Can you provide more information, such as browser version or IOS version? @Super-invincible
sorry for late reply, it‘s no problem in the safari, google browser and Android.This issue on IOS webview(my version is 17.0)

@Super-invincible Please update to the latest version to see if this issue has been resolved. Due to device limitations, I am unable to accurately verify if the issue has been fixed

@Super-invincible Please update to the latest version to see if this issue has been resolved. Due to device limitations, I am unable to accurately verify if the issue has been fixed

Thank you so much! The bug has been fixed!


Docs: update search to be "inline" and not require leaving the page

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/3249
Originally created by @tayloramurphy on 2022-02-15 23:19:12

Related to #3248.
FYI @afolson @alexmarple

View 3 previous comments from the original issue on GitLab

@alexmarple - This is lower pri than the Gridsome stuff some I'm tentatively putting into Iteration 5 (2 weeks out). We can push back again if needed or assign to another enigneer if possible.

Closing this. (Won't do.) Prioritizing Gridsome deployment and will iterate from there.

@aaronsteers @alexmarple are docs moving to gridsome too? Where is the discussion thread on that?

@afolson - My mistake. I thought this was re: hub search.
Reopening.

In scope for docusaurus redesign


libjpeg.so.62: cannot open shared object file

Hi i am getting the following error with this buildback:

File "/app/.heroku/python/lib/python3.4/site-packages/django/contrib/gis/gdal/prototypes/ds.py", line 8, in
from django.contrib.gis.gdal.libgdal import lgdal
File "/app/.heroku/python/lib/python3.4/site-packages/django/contrib/gis/gdal/libgdal.py", line 48, in
lgdal = CDLL(lib_path)
File "/app/.heroku/python/lib/python3.4/ctypes/init.py", line 351, in init
self._handle = _dlopen(self._name, mode)
OSError: libjpeg.so.62: cannot open shared object file: No such file or directory

i did use the
https://github.com/dulaccc/heroku-buildpack-geodjango.git#e017204
repo

Is this on a fresh new heroku app ?
If yes, can you add the steps you've used to deploy your heroku app, so that I can reproduce it

Hi,
I'm having the same issue. I just tried to deploy a new app today on a Cedar-14 stack and that seems to be a problem as referenced in this thread:
https://github.com/cyberdelia/heroku-geo-buildpack/issues/22
It builds fine, but if I try to use python manage.py shell I get the same error:
OSError: libjpeg.so.62: cannot open shared object file: No such file or directory

Hello,
I'm having the same issue with the last version of the buildback.
Didn't managed to fix it yet.

Hi,
Actually this problem is related to the new cedar-14 stack.
So I will use original cedar until a solution is provided.
Thanks!

I need to compile a version of GDAL especially for the cedar-14 stack, but still support the original cedar stack. So for that, I'll to rebuild a little bit the way precompiled-libs are stored on the S3.
Come back to you tomorrow with a fix.
Cheers

Awesome, thanks!

I am also facing the same issue. Any updates as to how this can be fixed?

@staranjeet Just downgrade to cedar stack. It doesn't seems to change that much for a Python/Django stack.

@santiagomalter I am on cedar-14 stack.. do I need to downgrade more from there? Im getting the same error. Also how do I downgrade to another stack?

heroku stack:set cedar (instead of cedar-14) and then push something to deploy again.

awesome thank you that worked! Is there anything bad about using the old cedar stack?

It depends of your needs. But I'd say it doesn't change a lot for 99‰ of Django apps. Cedar 14 is basically cedar with upgraded Ubuntu. But I'll personally upgrade as soon as a patch is provided for the build pack. Unfortunately I don't have the competencies to provide a solution by myself  for cedar14.

@santiagomalter ok that sounds good to me! Thank you! I just learned of build packs today so I definitely am no help to fix it.

just ran into this exact same issue trying to deploy my first geodjango project and followed suggestions to switch to cedar stack, however I am still getting a different error as seen here

FYI, Heroku has put a deadline on this particular migration.  Here's the note I get when deploying:
!   Cedar-10 will reach end-of-life on November 4th, 2015.
!   Upgrade to Cedar-14 at your earliest convenience.
!   For more information, check out the following Dev Center article:
!   https://devcenter.heroku.com/articles/cedar-14-migration

The cedar-14 stack support, that fix the libjpeg issue, has been brought with the mentioned e6d02f2 commit. Finally :)
Cheers

Hi,
I started getting the following error today with both Cedar-10 and Cedar-14
File "manage.py", line 10, in
execute_from_command_line(sys.argv)
File "/app/.heroku/python/lib/python2.7/site-packages/django/core/management/init.py", line 338, in execute_from
ommand_line
utility.execute()
File "/app/.heroku/python/lib/python2.7/site-packages/django/core/management/init.py", line 312, in execute
django.setup()
File "/app/.heroku/python/lib/python2.7/site-packages/django/init.py", line 18, in setup
apps.populate(settings.INSTALLED_APPS)
File "/app/.heroku/python/lib/python2.7/site-packages/django/apps/registry.py", line 108, in populate
app_config.import_models(all_models)
File "/app/.heroku/python/lib/python2.7/site-packages/django/apps/config.py", line 198, in import_models
self.models_module = import_module(models_module_name)
File "/app/.heroku/python/lib/python2.7/importlib/init.py", line 37, in import_module
import(name)
File "/app/.heroku/python/lib/python2.7/site-packages/django/contrib/auth/models.py", line 41, in
class Permission(models.Model):
File "/app/.heroku/python/lib/python2.7/site-packages/django/db/models/base.py", line 139, in new
new_class.add_to_class('_meta', Options(meta, **kwargs))
File "/app/.heroku/python/lib/python2.7/site-packages/django/db/models/base.py", line 324, in add_to_class
value.contribute_to_class(cls, name)
File "/app/.heroku/python/lib/python2.7/site-packages/django/db/models/options.py", line 250, in contribute_to_class
self.db_table = truncate_name(self.db_table, connection.ops.max_name_length())
File "/app/.heroku/python/lib/python2.7/site-packages/django/db/init.py", line 36, in getattr
return getattr(connections[DEFAULT_DB_ALIAS], item)
File "/app/.heroku/python/lib/python2.7/site-packages/django/db/utils.py", line 240, in getitem
backend = load_backend(db['ENGINE'])
File "/app/.heroku/python/lib/python2.7/site-packages/django/db/utils.py", line 111, in load_backend
return import_module('%s.base' % backend_name)
File "/app/.heroku/python/lib/python2.7/importlib/init.py", line 37, in import_module
import(name)
File "/app/.heroku/python/lib/python2.7/site-packages/django/contrib/gis/db/backends/postgis/base.py", line 8, in
from .features import DatabaseFeatures
File "/app/.heroku/python/lib/python2.7/site-packages/django/contrib/gis/db/backends/postgis/features.py", line 1, i

from django.contrib.gis.db.backends.base.features import BaseSpatialFeatures
File "/app/.heroku/python/lib/python2.7/site-packages/django/contrib/gis/db/backends/base/features.py", line 3, in <
dule>
from django.contrib.gis.db.models import aggregates
File "/app/.heroku/python/lib/python2.7/site-packages/django/contrib/gis/db/models/init.py", line 7, in
from django.contrib.gis.geos import HAS_GEOS
File "/app/.heroku/python/lib/python2.7/site-packages/django/contrib/gis/geos/init.py", line 9, in
from .libgeos import geos_version, geos_version_info  # NOQA: flake8 detects only the last all
File "/app/.heroku/python/lib/python2.7/site-packages/django/contrib/gis/geos/libgeos.py", line 61, in
lgeos = CDLL(lib_path)
File "/app/.heroku/python/lib/python2.7/ctypes/init.py", line 365, in init
self._handle = _dlopen(self._name, mode)
OSError: libgeos-3.4.2.so: cannot open shared object file: No such file or directory

I've just find the fix, sorry for having missing this one

Pierre,
Thank you for bringing this buildpack into Cedar-14!
We had a bit of a nasty surprise when this build broke us this evening.  It looks like these changes result in an LD_LIBRARY_PATH of:
LD_LIBRARY_PATH=/app/.heroku/vendor/lib:/app/.heroku/python/lib:/app/.geodjango/geos/lib/libgeos_c.so/lib:/app/.geodjango/proj4/lib:/app/.geodjango/gdal/lib/libgdal.so/lib:
Which is clearly incorrect, as the GDAL_LIBRARY_PATH and GEOS_LIBRARY_PATH environment variables actually reference binary files.
This can be fixed with a little bash trickery (using dirname), which I've implemented in a fork at
https://github.com/samcheng/heroku-buildpack-geodjango
I will submit a pull request.
In the mean time, in production, we're just depending on the most recent non-broken version:
git://github.com/dulaccc/heroku-buildpack-geodjango.git#628ad0c
Best Regards,
Sam

Thanks @samcheng for your work !
And sorry for the nasty surprise... I should have used tags before now to avoid these kind of issues.
So now you can refer to a stable release with the tag 1.0 by pinning the buildpack version :
$ heroku buildpacks:set https://github.com/dulaccc/heroku-buildpack-geodjango.git#1.0

Next releases will increment the minor version counter
Cheers

I'm running into this error: OSError: libgeos-3.4.2.so: cannot open shared object file: No such file or directory since yesterday when running collectstatic. Curiously, heroku run python manage.py collectstatic works post-deploy, but of course that's useless. I have been able to use the build pack successfully in the past, and I've verified that nothing changed in my configuration. I've tried on both cedar, and cedar-14.
I've also tried 1.0, 1.1, latest, and 562bf5f to no avail. Ideas?

@maroux Did you fix this?  We're running into exactly the same problem.

I had to resort to sticking to the last commit before the most recent changes (this is a Cedar 10 or whatever install).
heroku buildpacks:set git://github.com/dulaccc/heroku-buildpack-geodjango.git#59fde6c

@maroux did you manage to try on a new app ?

I'm still seeing this error using v1.1 on both Cedar-10 and Cedar-14.


how to resume in the same folder

when i launch the pytorch lightning trainer fit(), to resume it seems you can pass one old checkpoint, but i am not sure if it is possible (or perhaps it is chosen not to) to simply resume the current training in the same "version" sub-folder?

I can't get mine to ever create a new "version" folder, no matter what. We seem to have opposite problems.

i launch my training like this:
trainer = pl.Trainer(
default_root_dir=params.log_dir,
gpus=1,
precision=16,
progress_bar_refresh_rate=20,
max_epochs=20,
check_val_every_n_epoch=4,
resume_from_checkpoint=ckpt,
)

I have the same question. When trying to resume training with
python3 main.py fit --config /default_root_dir/lightning_logs/version_34/config.yaml --ckpt_path /default_root_dir/lightning_logs/version_34/checkpoints/last.ckpt, the new checkpoints and events get saved to /default_root_dir/lightning_logs/version_35/ and not to /default_root_dir/lightning_logs/version_34/

Same issue. Any workarounds?


perf: Ignore unnecessary exception stack trace in testcase

What is the purpose of the change
see #8419
Brief changelog

Ignore of printing exception stack trace in ConfigCenterConfigTest#testOverrideConfig
Ignore of printing exception stack trace in MethodConfigTest#testVerifyMethodConfigOfService
Ignore of printing exception stack trace in ReferenceConfigTest#test1ReferenceRetry

Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[x] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[x] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #8420 (0d5012d) into 3.0 (c125b99) will decrease coverage by 0.16%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                3.0    #8420      +/-   ##
============================================
- Coverage     63.07%   62.91%   -0.17%
  Complexity      312      312
============================================
  Files          1102     1102
  Lines         46242    46196      -46
  Branches       6980     6947      -33
============================================
- Hits          29169    29065     -104
- Misses        13809    13861      +52
- Partials       3264     3270       +6

Impacted Files
Coverage Δ

...ng/transport/dispatcher/all/AllChannelHandler.java
62.06% <0.00%> (-20.69%)
:arrow_down:

...ng/transport/dispatcher/WrappedChannelHandler.java
43.47% <0.00%> (-15.22%)
:arrow_down:

...dubbo/common/status/support/LoadStatusChecker.java
50.00% <0.00%> (-11.54%)
:arrow_down:

...in/java/org/apache/dubbo/common/utils/JVMUtil.java
81.13% <0.00%> (-11.33%)
:arrow_down:

...mmon/threadpool/support/fixed/FixedThreadPool.java
80.00% <0.00%> (-7.50%)
:arrow_down:

.../remoting/transport/netty4/NettyClientHandler.java
61.01% <0.00%> (-6.78%)
:arrow_down:

...moting/transport/netty4/NettyEventLoopFactory.java
30.00% <0.00%> (-6.37%)
:arrow_down:

...pache/dubbo/remoting/transport/AbstractServer.java
57.14% <0.00%> (-5.72%)
:arrow_down:

.../threadpool/support/limited/LimitedThreadPool.java
83.33% <0.00%> (-5.56%)
:arrow_down:

...ache/dubbo/remoting/api/NettyEventLoopFactory.java
36.36% <0.00%> (-5.31%)
:arrow_down:

... and 39 more

Continue to review full report at Codecov.

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


🎨 Update Gov UK Frontend and MOJ Frontend in Control Panel

User Story
As a AP user
I expect the Control Panel to use the latest gov uk and moj frontend styles and components
So that I get a better user experience
Value / Purpose
The frontend dependencies have fallen far behind the latest versions, which means we use some outdated styles and logos (such as the crown image on login and used as the favicon).
Useful Contacts
No response
User Types
No response
Hypothesis
No response
Proposal
Update GOV UK Frontend and MOJ Frontend libraries to the latest version.
As there are major version increases, this will need some manual work within the codebase to ensure it is working. For example, GOV UK frontend has changed the path where assets sit, so we need to update our sass files to reference the new location for the static to build.
In order to do this correctly and accurately, we need to read through the release notes for the major version releases to check for breaking changes. For GOV UK frontend this is:

v4.0.0
v5.0.0

For MOJ Frontend:

v2.0.0

Once we have the static building locally successfully, run the application and check everything looks and works as expected.
Additional Information
No response
Definition of Done

[x] Update Gov UK Frontend to latest version, following release notes
[x] Update MOJ Frontend to latest version, following release notes
[x] Static builds locally
[x] Run application locally and check it appears correct
[x] Ensure latest images/logos (such as the crown) are correct
[x] Deploy to dev for further testing from the team
[ ] Deploy to prod

Updates to MoJ frontend and GovUK Frontend in control panel. Added some functionality to hide/show forms when something is selected. Dev PR created here

Deployed to production on 6/8/24


Fix assertion error when calling the cdps getter of the Stabilization contract

Fixes AssertionError from the
assert isinstance(return_value, tuple)

assertion when calling the cdps getter of the Stabilization contract.
The reason for failing the assertion is that for this call the contract
function wrapper returns a list instead of the expected tuple.
To work around it, cast the return value to a tuple.
Note that according to web3.py docs1, the function wrapper's call()
method "returns the return value of the executed function" i.e. there is
no guarantee that the return value is either a list or a tuple, however
I don't think we should worry about it until we run into similar errors.
Fixes https://github.com/autonity/autonity.py/issues/37.

Do we know why we are getting back a list instead of a tuple? I think it is worth investigating otherwise we're just guessing what is the right type instead of selecting the right one.
This is a good starting point: https://github.com/ethereum/web3.py/blob/e94e5e8cf79eed324534fdf77127a49545aba20a/web3/contract/utils.py#L66

Do we know why we are getting back a list instead of a tuple?

I've done the investigation.
The contract function call is performed by call_contract_function from which we should focus on the part:
    try:
        output_data = w3.codec.decode(output_types, return_data)
    except DecodingError as e:
        ...

    _normalizers = itertools.chain(
        BASE_RETURN_NORMALIZERS,
        normalizers,
    )
    normalized_data = map_abi_data(_normalizers, output_types, output_data)

It first calls w3.codec.decode that has the return type Tuple[Any, ...] i.e. we could assume that the return type is always a tuple.
However, map_abi_data passes the output data through a chain of normalizer functions, of which the first one, abi_data_tree converts the tuple into a list (has return type List[Any]).
Therefore, if the contract function has multiple outputs, the expected behaviour of Web3 is that the return type is a list.
I could verify this with performing other contract calls, e.g. calling the config function of the Autonity contract as:
aut -v contract call --abi ../autonity.py/autonity/abi/Autonity.abi --address 0xBd770416a3345F91E4B34576cb804a576fa48EB1 config

also results in assertion error.

Anyway, it seems to me that the entire decoding logic in autonity.abi_parser is redundant with built-in Web3 functionality.
Web3.Contract objects have a Contract.decode_tuples flag (default False):

If a Tuple/Struct is returned by a contract function, this flag defines whether to apply the field names from the ABI to the returned data.

I'd propose a refactoring that autcli should use the built-in ABI parser instead of our own implementation.


Cannot add interface in Devices Interface

Issue type:
Not able to add device interfaces.
<class 'django.db.utils.IntegrityError'>
null value in column "enabled" violates not-null constraint
DETAIL:  Failing row contains (224, ETH-P0, 1000, f, , 39, null, null, null, null).

**Python version:2.7.5
**NetBox version:2.0.10

This bug report needs more information. Per the contributing guidelines:

When submitting a bug report, please be as descriptive as possible. Be sure to include:

The environment in which NetBox is running
The exact steps that can be taken to reproduce the issue
Any error messages generated
Screenshots (if applicable)

Please ensure that your issue includes all of the listed information. If no response is received within a week, this issue will be closed.

hi Jeremy
think have found some leads.
i have go into the database table " dcim_interface" and change table's Columns "enabled" to No "Not NULL?". and it allow for me to add interface in devices.
Im not sure where is the script store so i go to change the DB. will doing this cause other issue?

sorry like like i accident closed this thread

hi jeremy
The environment in which NetBox is running : CentOS 7

after upgrade from 2.1beta to 2.0.10

You shouldn't be downgrading from the beta to a production release. This requires rolling back the database migrations, though ideally you'd have used a different database entirely. This error is occuring because the 2.0.10 code isn't aware of the enabled column.

thanks jeremy. got it, think i will disable for the enable column in the database. as i encounter some error on beta 2.1. stable release 2.0.10 work .
Thanks alot for the info


Move Yokis Clusters definition to device definition

When https://github.com/Koenkk/zigbee-herdsman/pull/1019 is ready, migrate the clusters definition from ZH to ZHC.

Completed with https://github.com/LaurentChardin/zigbee-herdsman/commit/5ee728f5afb92011909fc405e180143d4942f47e.
See also https://github.com/LaurentChardin/zigbee-herdsman-converters/commit/1060fa912a83a2e69ba6434742111ef3ab74373e


Login impossible on iPhone SE Gen 1

Summary
You can't scroll the login popup so that you can press on log in with "Gitlab" button
Environment Information

Device Name: iPhone SE
OS Version:15.7.5
Mattermost App Version: v2.3.0
Mattermost Server Version:

Steps to reproduce
I am connected to 2 servers and for the default server I've used log in using Gitlab.  The App has gone through several updates since the last log in and now I can't select the button to tell it to use Gitlab.  I can scroll it up to expose the button but when I remove my finger the dialog goes back to the top.
Expected behaviour
The dialog allow you to press the Gitlab button
Observed behaviour (that appears unintentional)
Possible fixes

Not quite impossible but I had to reduce the font size for the entire phone to succeed in logging in.  Buttons should be accessible without have to resort to changing font sizes.


fix(karma): karma conf filename

Hey, this is actually intentional to make all the config files the same. Good eye, though!


Doesn't work with Poetry

It seems something is incompatible with poetry. I'm still debugging but I can't seem to install public-hello
poetry source add test https://astariul.github.io/github-hosted-pypi/
poetry add --source test public-hello

Returns Could not find a matching version of package public-hello

It is connecting correctly to https://astariul.github.io and searching for the package at /github-hosted-pypi/public-hello/

I believe poetry doesn't support git urls in the pep 503 directory https://github.com/python-poetry/poetry/issues/5548


Assertion Error using LB-guess with ECP

So while I was re-generating SPAHM-e for Yuri's transition metal complexes with LB guess and ECP, I get an assertion error arising from this test.
How important is it ?
Do you know how to fix it ?
Here's a xyz to try out (comes from Yuri). params: spin=4, charge=0, guess=LB, basis=minao, ecp=def2-svp
HOYHOS.xyz.txt
carefull I had to change the file extension, gh wouldn't accept .xyz extensions :laughing:
Traceback (most recent call last):
    e_spahm = qstack.spahm.compute_spahm.get_spahm_representation(mol, guess)
  File "qstack/spahm/compute_spahm.py", line 56, in get_spahm_representation
    e, v  = get_guess_orbitals(mol, guess, xc)
  File "qstack/spahm/compute_spahm.py", line 18, in get_guess_orbitals
    fock = guess(mol, xc)
  File "qstack/spahm/guesses.py", line 89, in LB
    return LB20(parameters='HF').Heff(mol)
  File "qstack/spahm/LB2020guess.py", line 353, in Heff
    self.H     = self.Hcore + self.HLB20(mol)
  File "qstack/spahm/LB2020guess.py", line 343, in HLB20
    self.check_coefficients(mol, acbasis)
  File "qstack/spahm/LB2020guess.py", line 337, in check_coefficients
    assert numpy.isclose(ch1, ch2)
AssertionError

Yes I made a mistake so the inner shells were removed twice because there were 2 iodines

Ah yees I see it!


[Extensions] Delete user details to scheduled job identity index on postDelete of a plugin/extension deleting a scheduled job

This issue refers to the implementation of deleteUserDetails as described on the interface proposed in this issue: https://github.com/opensearch-project/security/issues/2626
On a call to deleteUserDetails the security plugin should delete the entry associated with a scheduled job in the scheduled job identity index.
The JobSweeper is an IndexingOperationListener which means it can override postIndex to listen and react to new job details documents being indexed across any of the indices that are registered with job scheduler. In this method, the method described in this issue can be invoked within JobScheduler to trigger the identity system.

[Triage] This is part of the ongoing work with Extensions.


Add RPC price oracle service

Closes https://github.com/lightninglabs/taproot-assets/issues/906
I have minimized changes to ensure this can be included in version 0.4 with minimal review effort.

Scope One Endpoint
let's code work as it currently works
let's users use their own price oracle
Aperture will be a helpful testing apparatus
In unit tests, can define struct that set
dummy grpc server

Price oracle RPC client unit tests added. Thanks Oli for the TLS RPC server-client fix!

Replaced with https://github.com/lightninglabs/taproot-assets/pull/926
because of merge blocking due to requested changes


Option to disable image extraction

I'm finding the image extraction behavior a little inconsistent, and I don't really want to clutter the file uploads in my graph anyway. A way of disabling image extraction altogether would be wonderful.
Thanks for the wonderful extension, by the way!

I can definitely add something like that, what are you finding inconsistent about the current image extraction?

It didn't extract the image in this tweet: https://twitter.com/ShriramKMurthi/status/1047286807757565953, but does extract the one here: https://twitter.com/htmlenergy/status/1666949290525171713
When the Tweet Template includes {IMAGES} but the tweet has no images (or the extractor fails to find them, like with the ShriramKMurthi tweet), the text {IMAGES} appears in the result.

A couple other things I've noticed, not image related:

There also seems to be a big variance in how long it takes between triggering the extraction and seeing the result. Sometimes it's very snappy and other times theres a 5 second wait or I just have to trigger it again.
The effect of my change to the Tweet Template seems to be lost when I close and re-open Roam. I can see it there in the settings, but the behavior has reverted to the default template. To get mine to take effect I have to remove my customized template, then re-insert it.

These should all be addressed in the latest version, just released on the depot. Some tweets just don't extract and there's nothing I can do but for the ones that do I've added a little spinner to show that the extraction is happening

Nothing I can do about that if really if things haven't synced to roam yet. Though be aware that sometimes it can take a little bit for the tweet extraction passthrough server to 'wake up'
I keep running into this and there doesn't seem to be a real way to solve it on my end unfortunately

Yeah I've noticed some delay from waiting for the server to wake up, but it does seem like the issue of pasting and then triggering the extract too quickly is consistently reproducible independently of that.
I wonder if there'd be a way to fix it by using the .addPullWatch API method to register a watcher that would notice when the change is eventually committed to the graph. Probably more complicated than it's worth though.
Better feedback about failure might make it less of a problem---if the spinner goes away and the tweet hasn't been extracted, the user would have a better idea they should retry and aren't just waiting for the server to start.


‘bgzf_thread_count’ is not a member of ‘seqan3::contrib’

Hi,
when compiling RLM I get the following error:
(base) root@c7e1a36b5d5f:/build# make
Scanning dependencies of target RLM
[  0%] Building CXX object src/CMakeFiles/RLM.dir/RLM.cpp.o
/RLM/src/RLM.cpp: In function ‘int real_main(cmd_arguments&)’:
/RLM/src/RLM.cpp:147:22: error: ‘bgzf_thread_count’ is not a member of ‘seqan3::contrib’
     seqan3::contrib::bgzf_thread_count = 1;
                      ^~~~~~~~~~~~~~~~~
make[2]: *** [src/CMakeFiles/RLM.dir/build.make:63: src/CMakeFiles/RLM.dir/RLM.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:91: src/CMakeFiles/RLM.dir/all] Error 2
make: *** [Makefile:95: all] Error 2

Cmake and GCC versions are all fine from what I can see - any clue whats going on?
(base) root@c7e1a36b5d5f:/build# cmake --version
cmake version 3.13.4

CMake suite maintained and supported by Kitware (kitware.com/cmake).
(base) root@c7e1a36b5d5f:/build# gcc --version
gcc (Debian 8.3.0-6) 8.3.0
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Hi - I unfortunately can't reproduce this error with gcc 8.3.0 or 8.4.0. Did you check out the submodules, i.e. cloned with submodules or ran git submodule update --init --recursive?

Hey, the reason very likely is that zlib is not installed on your system. You have two options:

install zlib or
remove this single line (I am going to fill a bug in seqan3, it is kind of a seqan3 bug)

Thanks @SGSSGene for helping out - also my mistake for not adding zlib to the requirements, I will update the README (I think it should be necessary for bam support).

@t-neumann Could you check whether installing zlib fixes the problem for you?

Great!


Update the RegExp constructor to ECMA-262 v6

The following methods have been implemented:

RegExpAlloc, based on ECMA-262 v6, <IP_ADDRESS>.1
RegExpInitialize, based on ECMA-262 v6, <IP_ADDRESS>.2
RegExpCreate, based on ECMA-262 v6, <IP_ADDRESS>.3

Co-authored-by: Robert Fancsik<EMAIL_ADDRESS>JerryScript-DCO-1.0-Signed-off-by: Adam Szilagyi<EMAIL_ADDRESS>

Made an update according to the suggestions. Now we have different methods for creating a RegExp object from pattern, bytecode, and with parsed flags.


Expose lambda functions to frontend using API gateway

https://docs.aws.amazon.com/lambda/latest/dg/services-apigateway.html

Follow this documentation for REST API


Update intl version

reactive_forms just updated their intl version which is causing a dependency conflict with this package. Please update the version of intl

Technically there were no need to update intl in reactive forms. As far as 0.17.0 utilizes nonullability feature while reactive forms does not.

@vasilich6107 Can you update to the latest reactive_forms version?

updated in 0.5.0

I started extraction packages into separate repos
first one is https://pub.dev/packages/reactive_date_time_picker


Make it easier to customize buttons?

I feel the current button solution isn't easy to extend. I have a little demo running at http://bebraw.github.io/reactabular/ . As you can see, the form styling isn't that great. Besides #19 it would be useful if I could define buttons that are external to the form itself.
For this to work I would require some kind of hooks that I could trigger. I'm not sure what the correct API would look like. Perhaps something could be done through refs? In pseudocode something like this would work:
onOK() {
    this.refs.form.submit();
}

...

<Form ref='form' ... />

I guess ref works to some extent already. The problem is that if you are constructing a Form dynamically (no parent element yet), React won't allow you to assign a ref... Maybe ideal design is something else then.

Maybe we could start by introducing a buttonClass property that is copied into className for buttons. If that's not enough, we might also add renderButton function which allows users to specify an arbitrary function to be called when rendering a button.
I think the key to completely separating the button rendering from the form component itself, which I definitely see the appeal of, might be the submitOnChange property. This should make it quite easy to write a wrapper which monitors the state of the form and renders its own buttons.
Come to think of it, we might even make submit on change be the default behaviour in the core Form component and add a standard wrapper FormWithButtons which would take on the role of the current Form. Users who want different button rendering or different submit semantics could then simply copy and modify the FormWithButtons code.

Come to think of it, we might even make submit on change be the default behaviour in the core Form component and add a standard wrapper FormWithButtons which would take on the role of the current Form. Users who want different button rendering or different submit semantics could then simply copy and modify the FormWithButtons code.

Yeah. It could make sense to separate the concepts of a Form and Buttons. It would be enough for me if it was possible to inject custom buttons to the current Form. Technically the easiest way to achieve this would be to do something like this:
    var buttonValues = this.props.buttons;

    var buttons = this.props.buttons || function(submit) {
      return $.p(null,
                 (buttonValues || ['Cancel', 'Submit']).map(function(value) {
                   return $.input({ type   : 'submit',
                                    key    : value,
                                    value  : value,
                                    onClick: submit })
                 }));
    };

    return $.form({ onSubmit: this.preventSubmit,
                    onKeyPress: this.handleKeyPress
                  },
                  this.props.extraButtons ? buttons() : $.span(),
                  fields,
                  buttons(this.handleSubmit));
  }

If you want to override the buttons now, all you need to do is to implement the same interface and bind submit handler.

Sounds good to me. I think I'll implement both buttonClass and buttons-as-a-custom-function for now, and think a bit more about that refactoring idea.

Support for a user-supplied buttons function is provided as of @20c2c0d68d962a060e57fa935edbe9cfa89b7438.


loss nan

hello, when I run epic_verb_slowfast_script.sh, it shows loss nan and cls_loss nan, is that correct?

Hi, that's not correct and I can not reproduce the problem. Could you please check your data?

Hi, that's not correct and I can not reproduce the problem. Could you please check your data?
I downloaded this dataset from the following Baidu Cloud link, is this?

yes, have you changed any part of the code?

yes, have you changed any part of the code?

no, I only downloaded and unpacked the dataset, leaving the rest unchanged

Could you please provide some information about your environment? Do this situation only happen on EPIC-verb dataset?

Could you please provide some information about your environment? Do this situation only happen on EPIC-verb dataset?

solved, It's really the environment that causes the problem

Could you please provide some information about your environment? Do this situation only happen on EPIC-verb dataset?

solved, It's really the environment that causes the problem

ok.


release 1.2.0 final

final release

updated VERSION file
updated CI
updated README with ARNs
updated CHANGELOG

@vincentsarago can you take a look at this and see if there's anything else that should be included in this version?
The current master branch is 1.2.0rc2, and those base and python Lambda layers are published, along with the images on Docker Hub.
The Layer ARNs provided on the develop branch don't yet exist, but once they are merged to master they would get published.

@matthewhanson all seems ok.
Only question, for PREFIX we use /usr/local/ (https://github.com/developmentseed/geolambda/blob/develop/Dockerfile#L36) so I'm wondering if we are ending up with a layer that has more files that the gdal/proj libs (meaning I think we are packaging files from lambci/lambda:build-provided image)

The /usr/local directory isn't used by system files normally, it's for user built libraries.
I just checked lambci/lambda:build-provided and the /usr/local/lib folder is empty except for python2.7 and python3.6 directories, there's no other .so files so the only ones installed are the ones built in the Dockerfile.

👌 thus we still endup adding python2.7 and python3.6 dirs to the layer right ?

No, it's just copying .so files:
cp -P ${PREFIX}/lib/*.so* $DEPLOY_DIR/lib/
cp -P ${PREFIX}/lib64/libjpeg*.so* $DEPLOY_DIR/lib/

and doesn't recurse into directories


Add Affine to homebrew ?

I had a quick look and on ubuntu there is python3-affine, and at least on rpm distros there is a package of the same name, so things are looking pretty good for linux outside of pip (which is pretty big for beginners).
On the mac side I couldn't find Affine on homebrew, would it be possible to add a formula for it there ?
https://docs.brew.sh/Adding-Software-to-Homebrew

@stuaxo I don't use homebrew, so I'm not personally motivated to do this, but I wouldn't mind if you maintained a formula and added some supporting files to this repo.


KAFKA-10085: correctly compute lag for optimized source changelogs

Split out the optimized source changelogs and fetch the committed offsets rather than the end offset for task lag computation
Must be cherrypicked to 2.6

Ok to test

Hey @vvcephei, I addressed your comments and added tests.  Let me know if there's any test coverage that still seems missing

Java14 build passed, Java 11 and 8 builds failed with env issue

Test this please

Test this please

Test this please

Retest this please.

Retest this please.

Retest this please.


[Feature Request] File / Folder Editor

It would be great to see some way to edit files online like we can with GitHub, as well as create new files and folders, and of course, commit things. So far I am really liking Gogs since I can run it on my own servers, but this is one feature I really miss.
Thanks for all the great work! However, if this could be added, Gogs would definitively be comparable with GitHub.

See #1071

Closed as duplicate

@bkcsoft Suggestion: Add a duplicate tag to this issue tracker.


GeoSIR error: _recreate_rtree() missing 1 required positional argument: 'new_agents'

Dear GeoSIR friends:
I have tried to run GeoSIR project but I have two issues:

Firefox does not display neither map nor data
How can I configure my browser in order to display the map?

Chromium displays the map and data, but when I tried to run the model, I get the next message:

ERROR:tornado.application:Uncaught exception GET /ws (<IP_ADDRESS>)
HTTPServerRequest(protocol='http', host='<IP_ADDRESS>:8521', method='GET', uri='/ws', version='HTTP/1.1', remote_ip='<IP_ADDRESS>')
Traceback (most recent call last):
File "/lib/python3.7/site-packages/tornado/websocket.py", line 649, in _run_callback
result = callback(*args, **kwargs)
File "/lib/python3.7/site-packages/mesa_geo/visualization/ModularVisualization.py", line 199, in on_message
self.application.model.step()
File "/mesa-geo-master/examples/GeoSIR/model.py", line 217, in step
self.grid._recreate_rtree()  # Recalculate spatial tree, because agents are moving
TypeError: _recreate_rtree() missing 1 required positional argument: 'new_agents'
Do you know how can I fix it?
My platform is LinuxUbuntu 18.04 and python 3.7 .
Thanks.

GeoSIR requires the latest (unreleased) version of mesa_geo. Try to install from GitHub or clone the repo and install locally

The latest version of mesa_geo fixed this issue


Add pagination to my surveys page

Add pagination to my surveys page using usePagination hook. Similarly to how it is done on surveys answers page.

#143
I implemented the pagination feature on my surveys page and created a pull request. Review my pull request and let me know if I need to change anything.


Pressing slash in Organization Description jumps to search

Describe the bug
When attempting to create a new organization, I'm filling out the form and I want to add a URL to the description. When I press the slash key, the UI jumps to the search box in the header, making it impossible to enter a slash without some sort of workaround like copy/paste.
Expected behavior
Slash character should be allowed, or if it's disallowed, it should be validated out and not jump to the search box. Jumping to the search box should only happen when there's no focus on an input control.
To Reproduce

Create a new organization.
In the Description, type a slash.

My Platform

Firefox 128.0.3
macOS 14.5

Additional context
Here's a screen recording of the issue:
https://github.com/user-attachments/assets/dbc22a87-9a99-48ae-bcad-3aa0f4a71616

Related code is here: https://github.com/pypi/warehouse/blob/b28d08f5b375c9537aa880019aff8db624233619/warehouse/static/js/warehouse/controllers/search_focus_controller.js#L20

That's lightning fast. Thanks!


Delete duplicate content in fork-a-repo.md

Why:
Closes #17509

What's being changed:
delete duplicate content in Fork a repo#next-steps.

Check off the following:

[x] I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

@mhsiungw
Thanks so much for opening a PR! I'll get this triaged for review :zap:


Configurable build dir

It would be nice if the build dir can be set to something other than "build". Either via the binding.gyp or via an option of the node-gyp commands.

I would also like to see this. We separate our build artifacts from our source tree, and while @springmeyer's stopgap might work, I don't think it will help when the build fails for example -- going to have to do manual clean up to get any junk out of the source tree.

Was there an update to this? See also: https://github.com/nodejs/node-gyp/issues/631

@peterbraden - looks like there has not been any action by anyone to make this configurable. It would not likely be too hard, but it is still hardcoded right here: https://github.com/nodejs/node-gyp/blob/625c1515f9e00a9ea933ef78c00463ffba642f19/lib/configure.js#L257.

I might be missing something but it still doesnt' alow me to change build directory. I'm running
node-gyp --build-dir=foo rebuild

but it still create the build folder and not the foo

It is so sad this has not been fixed since 2013. :(

I too once had this deep desire filling my soul to change my output directory.  Upon further research, I have learned it is unsupported.  This saddens me.  I have laid awake several nights in a row now pondering life's great questions, and this is one of them.
I appreciate you taking the time to read this, and hopefully one day this issue will be dominated in the most satisfying possible way, which is committed, completed, and compiled.
Thanks,
Your loving friend,
Michael, ThePrimeagen, Paulson

Literally the worst comment ever

Honestly its a pretty beautiful comment

Heads up: I'm putting this issue on notice. If you want to see this feature merged, please pick up #919 - it's close but it needs minor fixes and a rebase and its original author no longer has time.

It's been a week and no one stepped up so I'm going to close this out. For anyone still wanting to move forward with this, please adopt #919 and we'll take it from there.

The closing of this issue has brought forward feelings I have not felt in many of years.  Again, my nights have interrupted with what some describe as fever dreams.  Yearning, no... passionately desiring change but ill equipped to make change happen.  We have all been here, we have all been at the mercies of life, peering over the edge, but unable to move the stones in our body to make the leap of faith required to make change that will ultimately affect history as we know it.
Unfortunately, this isn't for me, as I only program in Rust, btw.  Have you heard rust?  Its a type safe, memory safe, blazingly fast compiled language that is pretty new and amazing.  You should give it try.
Aka ThePrimeagen

Output directory is still hard-coded and this 8 year old issue has been closed without a fix - what a disappointment.
https://github.com/nodejs/node-gyp/blob/cff9ac2c3083769a383e00bc60b91562f03116e3/lib/configure.js#L212
Hope one day we can build NodeJS add-ons without this Python crap.

Bruh, like why hasn't someone just changed :

let outputDir = "build";

to this:

let outputDir = process.env.NODE_GYP_OUTPUT_DIR ?? "build";

Literally small quick and easy, like I can PR that in minutes. Kind of shocked that hasn't been done yet.

Also, you have it set up to completely ignore the outputDir variable on windows, and default to a separate hard coded path to the same spot?
https://github.com/nodejs/node-gyp/blob/cff9ac2c3083769a383e00bc60b91562f03116e3/lib/configure.js#L17


improve DenomTrace grpc

Description
I change the TraceDenom gRPC so that it takes in either an ibc denom or a hash instead of only accept hash as input
closes: #101

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards.
[ ] Wrote unit and integration tests
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added relevant godoc comments.
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer
[ ] Review Codecov Report in the comment section below once CI passes

Codecov Report

Merging #1342 (ad226c6) into main (7bb609c) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main    #1342   +/-   ##
=======================================
  Coverage   80.27%   80.28%
=======================================
  Files         166      166
  Lines       12023    12029    +6
=======================================
+ Hits         9652     9658    +6
  Misses       1916     1916
  Partials      455      455

Impacted Files
Coverage Δ

modules/apps/transfer/keeper/grpc_query.go
80.00% <100.00%> (+1.73%)
:arrow_up:


docs: better arch to add connection between cri manager and pouchd

Signed-off-by: Allen Sun<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did
After discussing with @fanux about the architecture of PouchContainer, we found that we should add a connection between pouchd and cri-manager, and this will tell users that with using Kubernetes, pouchcontainer can still provide containers with powerful runtime support, like lxcfs and diskquota and so on.
Ⅱ. Does this pull request fix one issue?

none
Ⅲ. Describe how you did it
none
Ⅳ. Describe how to verify it
none
Ⅴ. Special notes for reviews
none

Codecov Report

Merging #1465 into master will increase coverage by 23.71%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master    #1465       +/-   ##
===========================================
+ Coverage   16.36%   40.08%   +23.71%
===========================================
  Files         207      250       +43
  Lines       13816    16351     +2535
===========================================
+ Hits         2261     6554     +4293
+ Misses      11399     8952     -2447
- Partials      156      845      +689

Impacted Files
Coverage Δ

daemon/logger/jsonfile/utils.go
70% <0%> (ø)
:arrow_up:

pkg/debug/debug.go
22.22% <0%> (ø)

cri/stream/errors.go
0% <0%> (ø)

internal/generator.go
100% <0%> (ø)

cri/stream/portforward/httpstream.go
0% <0%> (ø)

storage/volume/core.go
51.66% <0%> (ø)

registry/auth_challenge.go
62.5% <0%> (ø)

cri/v1alpha1/service/cri.go
0% <0%> (ø)

daemon/daemon.go
56.25% <0%> (ø)

cri/criservice.go
12.5% <0%> (ø)

... and 111 more

LGTM


Add MTGAN Preprocessing

Creating the Preprocessing logic, so the input MedRecord can be preprocessed so that MTGAN can actually use it.
Example:

medrecord = create_medrecord()
preprocessor = MTGANPreprocessor()
preprocessed_medrecord = preprocessor.preprocess(medrecord)

Closed by #200


[FEATURE]: Support GOTO/move back previous Task

Feature Request
Allow the workflow to back to the previous task.
My Workflow Definition
My workflow is like task A -> task B -> task C -> task D -> task E -> ...
My Business Requirement
The requirement is when task D is IN_PROGRESS. The user can select to move the workflow back to task B.
My Current Solution
My current solution is when the user selects move back. Our system will call the Terminate Workflow API first and then the Rerun Completed Workflow API(with the reRunFromTaskId being task B).
This solution can work but it will clear previous task B and task C related history from Task List.
Preferred Solution
The conductor can provide an API to allow the workflow to go to the previous task.

I am no expert - but that sounds like a
task_a();

variable a = 0

while( a == 0 ) {
  task_b();
  task_c();
  task_d();
  if(!something(user))  {
    a = 1;
  }
}

task_e();


update operator tools

The newer versions don't fix any specific issue that we are having, but staying
closer to upstream is always good. For example, we can rule out that the
ancient operator-sdk caused the install problem with OLM 0.19.1.
operator-sdk 1.13.1 complains during validation if the deployment file provides
the service account. Therefore it gets removed via kustomize.
The PR also contains a workaround for the currently broken upstream weavenet install YAML and cleans up operator.make.

make test fails:
[2021-11-17T14:31:49.502Z] hack/verify-generated.sh

[2021-11-17T14:31:49.502Z] + make generate

[2021-11-17T14:31:49.502Z] make[1]: Entering directory '/mnt/workspace/pmem-csi_PR-1052'

[2021-11-17T14:31:49.502Z] make[1]: Leaving directory '/mnt/workspace/pmem-csi_PR-1052'

[2021-11-17T14:31:49.502Z] make[1]: *** No rule to make target 'controller-gen', needed by 'operator-generate-k8s'.  Stop.

[2021-11-17T14:31:49.502Z] ERROR: code generation failed.

[2021-11-17T14:31:49.502Z] make: *** [test/test.make:33: test_generated] Error 1

make test fails

Fixed.
Somehow I can no longer reproduce the validation error about the service account, which makes me nervous. Something is fishy here, but I don't know what it is.
I've taken out the service account removal.


usage issue : comma in image name / text message with minus / text message with return to the line

Hello
I remark the following issues :
bsky post -image "my_picture,project.jpg" "- topic1

topic2
topic3
"

1/
In the picture name, if there is a comma : the bsky will look for "my_picture," and miss the rest of the filename.
It seems to be linked to :
--image value, -i value [ --image value, -i value ]
the commit could be in the filename, it s not a advised separator
2/
In the message, I remark , by doing as the example

topic1  =>  flag provided but not defined: - topic1
A message can't start with a "-" ?

3/
the return to the line seems not managed?
my lines seem ignored ?

topic2
topic3

About 3
You can use "--"
bsky post -- "- topic1
topic2
topic3
"

In general UNIX command line programs, arguments after -- are not treated as flags, even if they start with -.

About 1
Now I fixed in https://github.com/mattn/bsky/commit/4f885a8e7e5ee0b52fe06ad9eafd25c4e03faea9

So closing.

Thank you!


[Bug]: MsSQL: connection string is rejected when trying to connect to Azure SQL server instance.

Is there an existing issue for this?

[X] I have searched the existing issues

Description
Error: Driver.microsoft.sqlserver.jdbc.SQLServerDriver claims to not accept jdbcUrl
Ref: https://theappsmith.slack.com/archives/C0341RERY4R/p1683087333331029
Steps To Reproduce
https://theappsmith.slack.com/archives/C0341RERY4R/p1683087333331029
Public Sample App
No response
Environment
Production
Issue video log
No response
Version
self hosted, cloud
 Front conversations

Hi, is there any way for me to check the steps the reproduce this? The Slack channel link doesn't have access to non-appsmith people,

Hi @abhishekS14 , this issue was reported for connecting to MsSQL server setup on Azure cloud. You may try to spin up a MsSQL server on Azure cloud and try to connect to it to check if you are able to reproduce the issue.

Could not reproduce it on my local setup, waiting to get an account on cloud (credit card details required) before we can test on cloud.

Hello there,
I am also experiencing this bug. Happy to share whatever is needed privately.
I can reproduce the error when using a MSSQL Server 2019 instance.
Sincerely,
MLC

Hi @mlcsyd can you please share your setup details:
(1) MsSQL version
(2) Is MsSQL hosted on Azure cloud ?
(3) Is this a named instance ?

Hi @mlcsyd can you please share your setup details: (1) MsSQL version (2) Is MsSQL hosted on Azure cloud ? (3) Is this a named instance ?

Hello there, thank you for your response.

MS SQL Server 2019 (15.0.4312.2) running on Windows Server 2019 Datacenter
No, it is hosted on an AWS VM. We can connect to Azure SQL Serverless Instances and do not receive this error.
It is not a named instance.

Update:
version MS SQL Server 2019 (15.0.4312.2) seems to be working fine when tested on Mac via an Ubuntu based docker image.
docker pull mcr.microsoft.com/mssql/server:2019-CU20-ubuntu-20.04
docker run -e 'ACCEPT_EULA=Y' -e 'MSSQL_SA_PASSWORD=P@assw0rd' -p 1433:1433 -d mcr.microsoft.com/mssql/server:2019-CU20-ubuntu-20.04

Update: I am able to reproduce the error now. Fix is under review.


Assertion on a for loop variables assignment

Compiler fails with assertion on following code:
actor Main
  new create(env: Env) =>
    let foo: Array[(U8,U8)] = [('a','b'), ('c','d')]

    for (i, (c1, c2)) in foo.pairs() do
      None
    end

Error:
ponyc: src/libponyc/codegen/genoperator.c:277: assign_tuple: Assertion `0' failed

Thanks! Two separate bugs, one with nested tuple codegen and another with discarding an undefined LHS on tuple assignment. Both fixed.


Updating KFP compiler to using TFX 1.9.1 and Python 3.9.13

This PR upgrades the KFP Operator compiler to use newer versions of Python packages. Potentially addressing the issue that KFP Operator cannot deploy TFX pipelines built with newer version of Python packages.

ok to test

Solved by #164 maintaining Python 3.7 compatibility as well.


 I was surprized there was none.
It could be a special pipe (or several tiers of it), or slotted item for existing pipes. With blacklisting and whitelisting.
Tag support also would be very useful.
Hope for 1.19,2 version, as it is still the most usable and popular.

I would be in favour of a sort of filter, even if it's just placing a copy of an item in the end of a pipe going into the back of a storage container or another pipe, this way I can sort my dozens of chests and barrels into a tidy manner even just five slots like a hopper with a GUI button to enable or disable the filter :)

once i get the bugs in the 1.20 version fixed, i'll add a filter to the 1.20 version.
unfortunately though, i have no current plans to support 1.19 or anything prior due to the level of stress it will put me under, i've recently started a new job, i have to work on a couple other mods, and i have to continue writing and recording and mixin music.
it's a lot to keep track of all at once, so i personally think it's for the best that 1.20 receives the new updates. eventually people will move from 1.20 anyway.

it used to be the same situation with people sticking in 1.18 for the longest time, but ive seen that trend die down as well.

1.20 is fine by me since I'd already plans to use that for a pack update in the coming months and know the pains of trying to keep several mods updated (heck I even gave away some mods so I could lessen the workload) thanks for the reply though and I wish you all the best in your new job too :D

any updated on this for 1.21?


Changing channels shouldn't un-mute audio/video

Steps to reproduce:

mute audio (and/or video)
change to another channel

expected behavior:
audio/video is still muted/unmuted, similar to the state in the previous channel
observed behavior:
audio and video are always unmuted

Seems to still be an issue in the ICFP version.

This is not on my milestone for ICFP, and I definitely do not have bandwidth to implement this by then, sorry. I am happy to point you to where in the code to get started with this though.

Closing as the new UI has been developed after this issue was opened and this issue relates only to the old UI.
(The new UI has a pre-join screen that remembers previous settings)


Dev: finalizing pipeline support and testing

@powershellshock,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


LibWasm: Remove Wasm::ValueType::Kind::Null* variants

As far as I know, they're not in the spec and don't serve any purposes in the internals of LibWasm.

I think at some point "null reference to type T" was also a type, or maybe I misread the spec (possible, it was still a proposal iirc) at the time.
This looks alright.

Strange because I feel like I remember reading something like that a while ago...

Is this browser going to be for Windows 11 also?
Tyler Havlicek
Executive Committee Member
Ability 4 Us Advocacy
Long Island NY
934.345.1148
CONFIDENTIAL: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

From: Diego Frias @.>
Sent: Monday, July 8, 2024 3:57:28 PM
To: LadybirdBrowser/ladybird @.>
Cc: Subscribed @.***>
Subject: Re: [LadybirdBrowser/ladybird] LibWasm: Remove Wasm::ValueType::Kind::Null* variants (PR #500)
Strange because I feel like I remember reading something like that a while ago...
—
Reply to this email directly, view it on GitHubhttps://github.com/LadybirdBrowser/ladybird/pull/500#issuecomment-2215090543, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BFWGZYO4DTLMOSJCUIMJUEDZLLVKRAVCNFSM6AAAAABKP4QU4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJVGA4TANJUGM.
You are receiving this because you are subscribed to this thread.Message ID: @.***>