TypeError: deconv_length() missing 1 required positional argument: 'output_padding'

Traceback (most recent call last):
File "./main.py", line 281, in
main(arguments)
File "./main.py", line 95, in main
model_list = create_model(args=args, input_shape=net_input_shape, enable_decoder=True)
File "/home/nd/capsnet/SegCaps-master (copy)/utils/model_helper.py", line 29, in create_model
model_list = CapsNetR3(input_shape, args.num_class, enable_decoder)
File "/home/nd/capsnet/SegCaps-master (copy)/segcapsnet/capsnet.py", line 55, in CapsNetR3
name='deconv_cap_1_1')(conv_cap_4_1)
File "/home/nd/anaconda3/lib/python3.6/site-packages/keras/engine/base_layer.py", line 457, in call
output = self.call(inputs, **kwargs)
File "/home/nd/capsnet/SegCaps-master (copy)/segcapsnet/capsule_layers.py", line 250, in call
out_height = deconv_length(self.input_height, self.scaling, self.kernel_size, self.padding)
TypeError: deconv_length() missing 1 required positional argument: 'output_padding'

Another problem is: "Too many indices for array, skipping files " , with 10 images and mask. but when i load MSCOCO data set with 10 images and mask it working.

Hi hiteshnitetc,
How many channels in your mask image? It should be only one channel as gray scale images.

@Cheng-Lin-Li Hello, yes my mask images are gray scale only, with channel 1, and keras is set to channel last topology

I have same issue, code works fine with MSCOCO dataset, but have same error with different datasets.

TypeError: deconv_length() missing 1 required positional argument: 'output_padding'.. This issue can be solved using keras=2.1.6 with python 3.6.x

Hello,
I get the same issue
My configuration is : ubuntu 18.04.2, Python 3.6.7, Keras 2.2.4
The data were obtained with
python3 getcoco17.py --data_root_dir ../data --category person --annotation_file ../data/annotations/instances_train2017.json  --number 10 --id 22228<PHONE_NUMBER>94<PHONE_NUMBER>0<PHONE_NUMBER>22<PHONE_NUMBER>12 69578
And then I run
python3 ./main.py --test --Kfold 2 --net segcapsr3 --data_root_dir=data --loglevel 2 --which_gpus=-2 --gpus=0 --dataset mscoco17 --weights_path data/saved_models/segcapsr3/split-0_batch-1_shuff-1_aug-0_loss-dice_slic-1_sub--1_strid-1_lr-0.0001_recon-20.0_model_20180705-092846.hdf5
thanks for your help

Extract from
documentation of  deconv_length line 148 and 149
https://github.com/keras-team/keras/blob/master/keras/utils/conv_utils.py
output_padding: Integer, amount of padding 	along the output dimension,
Can be set to None in which case the output length is inferred
Then I introduced the following modifications in "capsule_layers.py"
ddition on line 250   output_padding = None
New 251 (was 250)          out_height = deconv_length(self.input_height, self.scaling, self.kernel_size, self.padding, output_padding)
New 252  (was 252)          out_width = deconv_length(self.input_width, self.scaling, self.kernel_size, self.padding, output_padding)
addition on line 284       output_padding = None
new 285 (was 283)        output_shape[1] = deconv_length(output_shape[1], self.scaling, self.kernel_size, self.padding, output_padding)
new 286 (was 284)        output_shape[2] = deconv_length(output_shape[2], self.scaling, self.kernel_size, self.padding, output_padding)
and it seems it works. I get 5 output masks
But I now have an other issue : "Unable to find weights path. Testing with random weights".

I found the solution :
In test.py
Line 109 weights_path = join(args.data_root_dir, args.weights_path)
then data should not be repeated in weight_path => command line modified accordingly
python3 ./main.py --test --Kfold 2 --net segcapsr3 --data_root_dir=data --loglevel 2 --which_gpus=-2 --gpus=0 --dataset mscoco17 --weights_path saved_models/segcapsr3/split-0_batch-1_shuff-1_aug-0_loss-dice_slic-1_sub--1_strid-1_lr-0.0001_recon-20.0_model_20180705-092846.hdf5

Thanku you for your detailed reply, i will try out your suggestions.
On Mon, Jul 15, 2019 at 8:04 PM fenaux<EMAIL_ADDRESS>wrote:

I found the solution :
In test.py
Line 109 weights_path = join(args.data_root_dir, args.weights_path)
then data should not be repeated in weight_path => command line modified
accordingly
python3 ./main.py --test --Kfold 2 --net segcapsr3 --data_root_dir=data
--loglevel 2 --which_gpus=-2 --gpus=0 --dataset mscoco17 --weights_path
saved_models/segcapsr3/split-0_batch-1_shuff-1_aug-0_loss-dice_slic-1_sub--1_strid-1_lr-0.0001_recon-20.0_model_20180705-092846.hdf5
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Cheng-Lin-Li/SegCaps/issues/13?email_source=notifications&email_token=AHJSSSX4HX2I54ARU3TBRRLP7SDG7A5CNFSM4H6J6QBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ54NIQ#issuecomment-511428258,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHJSSSWEEGUGQDGO3J3CQPDP7SDG7ANCNFSM4H6J6QBA
.

--
Hitesh Tekchandani
PhD Research Scholar
NIT Raipur
India

Hi fenaux,
Thanks for your findings and suggestions.
I will revise the document and code accordingly.

I get the same issue.
I solved the first problem "deconv_length() missing " using keras=2.1.6 with python 3.6.x.
But,"Too many indices for array, skipping files" still cannot be solved. Have you solved it?

TypeError: deconv_length() missing 1 required positional argument: 'output_padding'.. This issue can be solved using keras=2.1.6 with python 3.6.x

If using the latest version of Keras please use output_padding=None, this seems to solve the issue

Getting following error.
INFO 2020-12-25 19:49:37,131:
path_to_np=data/np_files/train18.npz
INFO 2020-12-25 19:49:37,132:
Pre-made numpy array not found for train18.
Creating now...
DEBUG 2020-12-25 19:49:37,132: STREAM b'IHDR' 16 13
DEBUG 2020-12-25 19:49:37,132: STREAM b'IDAT' 41 32768

----------------------------------------------------------------------------------------------------
Unable to load img or masks for train18
too many indices for array: array is 2-dimensional, but 3 were indexed
Skipping file


MCUboot / smp_svr sample broken in 2.4.0

Describe the bug
since 2.4.0 the smp_svr sample is broken.
I have exactly followed the instructions, but it does not work, its also confirmed by sombody else.
Mcuboot runs fine, but as soon as it jumps to the smp_svr sample its just dead and nothing happens anymore. its also not advertising. This only happens when using the overlay-bt, overlay-bt-tiny works fine. It seems like it has something todo with the image size.
overlay-bt works fine with 2.3.0.
To Reproduce
Steps to reproduce the behavior:
just use west init and then west update to get a clean copy, then:
west build -b nrf52840dk_nrf52840 bootloader/mcuboot/boot/zephyr
west flash
rm -rf build
west build -b nrf52840dk_nrf52840 zephyr/samples/subsys/mgmt/mcumgr/smp_svr -- -DOVERLAY_CONFIG=overlay-bt.conf
west sign -t imgtool -- --key bootloader/mcuboot/root-rsa-2048.pem
west flash --hex-file build/zephyr/zephyr.signed.hex

Expected behavior
MCUboot loads the sample and runs
Impact
have to go back to 2.3.0
Logs and console output
*** Booting Zephyr OS build v2.4.0-rc3  ***
[00:00:00.376,495] [1B][0m<inf> mcuboot: Starting bootloader[1B][0m
[00:00:00.383,056] [1B][0m<inf> mcuboot: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3[1B][0m
[00:00:00.393,493] [1B][0m<inf> mcuboot: Boot source: none[1B][0m
[00:00:00.399,261] [1B][0m<inf> mcuboot: Swap type: none[1B][0m
[00:00:00.678,283] [1B][0m<inf> mcuboot: Bootloader chainload address offset: 0xc000[1B][0m
[00:00:00.686,309] [1B][0m<inf> mcuboot: Jumping to the first image `slot[1B][0m`

Environment (please complete the following information):

OS: Ubuntu
Toolchain Zephyr SDK

Additional context
It seems like the problem has something todo with the image size, as I tried one of my own apps, and it also doesnt work (its way bigger than the sample)

Bisect shows:
ded737cd5829414b2126a2e9a09dceacd20d1938 is the first bad commit
commit ded737cd5829414b2126a2e9a09dceacd20d1938
Author: Carles Cufi<EMAIL_ADDRESS>Date:   Thu Sep 17 15:44:16 2020 +0200
    boards: nordic: Turn hardware stack protection on by default

    In all Nordic boards that contain ICs that support hardware stack
    protection, turn it on by default so that we detect
    stack overflows easier.

    Signed-off-by: Carles Cufi<EMAIL_ADDRESS> boards/arm/nrf21540dk_nrf52840/nrf21540dk_nrf52840_defconfig         | 3 +++
 boards/arm/nrf52833dk_nrf52820/nrf52833dk_nrf52820_defconfig         | 3 +++
 boards/arm/nrf52833dk_nrf52833/nrf52833dk_nrf52833_defconfig         | 3 +++
 boards/arm/nrf52840dk_nrf52811/nrf52840dk_nrf52811_defconfig         | 3 +++
 boards/arm/nrf52840dk_nrf52840/nrf52840dk_nrf52840_defconfig         | 3 +++
 boards/arm/nrf52840dongle_nrf52840/nrf52840dongle_nrf52840_defconfig | 3 +++
 boards/arm/nrf52dk_nrf52805/nrf52dk_nrf52805_defconfig               | 3 +++
 boards/arm/nrf52dk_nrf52810/nrf52dk_nrf52810_defconfig               | 3 +++
 boards/arm/nrf52dk_nrf52832/nrf52dk_nrf52832_defconfig               | 3 +++
 boards/arm/nrf5340dk_nrf5340/nrf5340dk_nrf5340_cpuapp_defconfig      | 3 +++
 boards/arm/nrf5340dk_nrf5340/nrf5340dk_nrf5340_cpuappns_defconfig    | 3 +++
 boards/arm/nrf5340dk_nrf5340/nrf5340dk_nrf5340_cpunet_defconfig      | 3 +++
 boards/arm/nrf5340dk_nrf5340/nrf5340pdk_nrf5340_cpuapp_defconfig     | 3 +++
 boards/arm/nrf5340dk_nrf5340/nrf5340pdk_nrf5340_cpuappns_defconfig   | 3 +++
 boards/arm/nrf5340dk_nrf5340/nrf5340pdk_nrf5340_cpunet_defconfig     | 3 +++
 boards/arm/nrf9160dk_nrf52840/nrf9160dk_nrf52840_defconfig           | 3 +++
 boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160_defconfig             | 3 +++
 boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160ns_defconfig           | 3 +++
 boards/arm/thingy52_nrf52832/thingy52_nrf52832_defconfig             | 3 +++
 19 files changed, 57 insertions(+)

It turns out that stack protection is enabled by default in mcuboot after this commit. Then, after we jump from bootloader to application code, we end up being "catched" by hw stack protection mechanism.
The solution for now seems to be setting CONFIG_HW_STACK_PROTECTION=n in mcuboot. Here is PR to mainline mcuboot: https://github.com/JuulLabs-OSS/mcuboot/pull/828.

The actual error condition (for my applications at least).
CONFIG_HW_STACK_PROTECTION  changes the default on ARM_STACK_PROTECTION, which selects MPU_STACK_GUARD.
MPU_STACK_GUARD sets a region towards the start of RAM to be Read-Only in the bootloader when the thread is loaded.
This region is still configured when the application is jumped into.
z_bss_zero in z_cstart attempts to zero the region, resulting in a 'Data Access Violation'.
I can confirm that forcing CONFIG_HW_STACK_PROTECTION=n fixes the issue.


Docs : Examples : Blog : blog-sidebar is not used or set

Hello,
https://github.com/twbs/bootstrap/blob/c9cd3e4a083a69bcd2eefb1d1b62e6106e2ce469/site/content/docs/5.0/examples/blog/index.html#L158
blog-sidebar class is not set in https://github.com/twbs/bootstrap/blob/master/site/content/docs/5.0/examples/blog/blog.css nor in site/content/docs/5.0/examples/blog/index.html .
So not used :  not needed or missing.
Thanks,
Eric
Same with blog-main : https://github.com/twbs/bootstrap/blob/c9cd3e4a083a69bcd2eefb1d1b62e6106e2ce469/site/content/docs/5.0/examples/blog/index.html#L87

You can ignore those, they are probably leftovers from refactoring on master. PRs welcome.


Still can pin even logged out of Pinterest app

I've logged out of Pinterest app and when trying to Pin from my app, It doesn't take me to login Pinterest but it successfully gets my borads and pins post to it.

I believe this is expected behavior. A SDK app doesn't know when a user logs out of the Pinterest app.


Only skip invalid wal record

Try to fix https://github.com/prometheus/prometheus/issues/13152
If there is an abnormal record in wal, prometheus will fail to truncate wal and abort this truncate job, and number of wals will grow endlessly and never be cleaned, so prometheus will consume disk space on this situation.
In this pr, if we encounter an abnormal record when reading wal, we skip this record an clean buf if any and won't block wal truncation

@bboreham Thanks for reviewing.
I remove logs in Reader and only keep error logs in LiveReader, so when rebuilding records from WAL during prometheus starting will not log invalid record err.
If stop rebuilding after some number of corruptions, the number and criteria seems need to be decided, and if we give up in the middle, maybe need some extra condition check to continue Truncate WAL to free disk usage?

Would it be worth giving up after some number of corruptions?

If stop rebuilding after some number of corruptions, the number and criteria seems need to be decided

Right, the number would likely be configurable.

if we give up in the middle, maybe need some extra condition check to continue Truncate WAL to free disk usage?

Do you mean build a checkpoint using the (incomplete) data read so far?
By "give up" I meant stop attempting to read the WAL, and leave it up to the administrator to resolve.  Similar to current behaviour after one corruption.

the number would likely be configurable.

If added this parameter to the tsdb options, maybe many places that uses tsdb.Option needs to be changed, I can try, but this may introduce some careless negligence.

By "give up" I meant stop attempting to read the WAL, and leave it up to the administrator to resolve

Sometimes it may be too late for the administrator to take action,in our situation: https://github.com/prometheus/prometheus/issues/13152, Prometheus's WAL directory keeps growing until it eats the root partition and affects other services running on that partition, if we could change the current behaviour to try to rebuild the record && create a checkpoint, but whatever the result is, truncate the WAL, then administrator don't have to clean abnormal dir manually when some serious problem alreay happened

How about a default false bool flag naming IgnoreWALCorruptionOnReplay place at tsdbOptions?https://github.com/prometheus/prometheus/blob/main/cmd/prometheus/main.go#L1562
If setted false we will not attempt to skip any invalid record, which is same with current behaviour, if setted true skip all invalid record and continue truncate whatever, thus Prometheus admin don't have to think how to a proper threshold number.

@bboreham Sorry for bothering, please take a look at this pr, I tested in our machines and works as expected.

Hello from the bug-scrub!  @YukkiKaze do you think you will get back to this?

Yes! @bboreham I will complete the comments and rebase my pr tomorrow, thanks  @aknuds1 for reviewing

The prometheus service was started with the wal file loaded normally： level=info component=tsdb msg="WAL segment loaded"
Why does the following anomaly still occur?
level=error component=tsdb msg="compaction failed" err="WAL truncation in Compact: create checkpoint: read segments: corruption in segment xxx at 180: unexpected full record"

@onlyangelss this is not the right place to ask questions.
Some right places are listed at https://prometheus.io/community/.
Probably you should file a new issue and give full details about your symptoms.

@YukkiKaze are you going to get back to this PR (and fix conflicts)?


Click is not working for pn:menuItem

Hi,
We have upgraded Jquery from 1.5.1 to 3.7.0 and our project is based on Rich faces version 4.0.0
After Jquery upgrade I upgraded htmlunit from 2.17 to 3.4.0. Now after upgrade below test
    @Test
public void testServerClick() throws IOException, SAXException {
    HtmlPage page = environment.getPage("/dropDownMenu_serverMode.jsf");
    HtmlDivision item = (HtmlDivision) page.getElementById("form:saveAll");
    assertNotNull(item);
    DropDownMenuBean.setCurrent("none");
    item.click();
    item = (HtmlDivision) page.getElementById("form:saveAll");
    assertNotNull(item);
    assertEquals("action", DropDownMenuBean.getCurrent());
}

is failing with warning
WARNING: Calling click() ignored because the target element
HtmlDivision[] is not displayed.
I verified item.isDisplayed() , it is returning false only.
I have tried  page.wait or set innerheight etc., but nothing helps.
Could you please let me know how to fix this test?

 Maybe you can do the following

go to the page in question in the real app using a real browser (chrome or ff)
open the developer tool and have a look at the div tag in question, check for the styles
make a screenshot of the devtools showing the div tab
now back to your tests
change the code and add  System.out.println(page.asXml()); right before clicking the div tag
check the output - have a look at the div tag in this output - maybe you can already see the difference that might be the reasons
otherwise send me the output and i will have a look

The page.asXml() helps to get an view how HtmlUnit sees the page - maybe some jQuery actions are not processed or maybe some styles are not applied - let's see.

Hi Thanks a lot for reply!
Replacing item.click() with item.click(false, false, false, true, true,true, false); as per https://htmlunit.sourceforge.io/faq.html#clickNotWorking fixed the issue.

yes, but if the div is visible/clickable in real browsers it should also be in HtmlUnit


Should we deprecate Hyde.css?

The Hyde.css file is used for two things, one, it contains some base compatibility and accessibility styles, second, it contains the Lagrafo (documentation layout) styles.
The first category could easily be added in the default app.css file, which would allow them to be further customized.
The second one, might just as well be in its own file as there is no reason for it to be loaded on non-documentation pages.
Since this is a breaking change I propose it for Hyde/Hyde v0.50.0 which already contains a lot of breaking changes, paired with HydeFront 2.0, putting HydeFront 1.x in EOL with LTS security fixes only. HydeFront as a package would still be used, and the documentation styles would be there as well.

Have thought a bit about this, and yes, I think it should be deprecated.


the problem with the priority of groups

Description
The player has 2 groups:

default (weight=1)
king (weight=3)

the default group has the right:
bending.ability.earthgrab = false
The king group has the right:
bending.ability.earthgrab = true
as a result, the player does not have the right to earthgrab, although this right is in the group with a higher priority.
Reproduction Steps
everything is described above
Expected Behaviour
the plugin will use the group right, with the highest priority
Server Details
PurPur 1.19.4
LuckPerms Version
5.4.128
Logs and Configs
No response
Extra Details
No response


New graphing modes for --graph

I added multiple new modes for different types of graphing. This includes graphing the CPU usage, CPU temperature, and CPU frequency. I also changed the way we parse the --graph command so that the user can provide a graph type.

This is a massive PR please make sure to test rigorously and leave comments!

Implements #285

Great job, this looks really good, I think I have one or two things of feedback.

Everything graphing works as intended and a very good solution!

Laptop tested


stm32: refcount peripheral enable/disable

This appears to work as designed, but the peripherals may currently leak refcounts. That will need to be examined before this can  be merged.

skipping the adc refcount so that I can handle it later


Automation of Migrating Campaign Activity to Runs

FEATURE OVERVIEW
User Story
As a site admin, I'd like to be able to retroactively associate campaign sign ups and reportbacks with the correct run, without having to make an issue/bother a dev.
Additional Information (optional)
Refs: https://github.com/DoSomething/phoenix/issues/6237 and discussion here: https://dosomething.slack.com/archives/campaign-template/p1457449052000240
Why This Matters
Segmenting campaign activity by run is super important for assessing campaign health and data purposes. Because it's sometimes difficult to tell when we need a new run, we anticipate this being a need in the future.
Current Workaround w/o Feature (if applicable)
A dev needs to be manually migrate the data with a scary sql-update command.
cc @mikefantini

sounds like two things need to be updated:

Automate signups and reportbacks to associate themselves with correct campaign run, depending on current time and campaign run dates.
Add to user interface to be able to retroactively associate campaign signups and reportbacks with the correct run.

Is this right @namimody ?

BRILLIANCE IN BULLET POINTS.
Just one amendment @chloealee -- I think the association to a campaign run should be based on sign up time and reportback submission time vs. current time?

ah yes, that's what I meant - thanks for clarifying @namimody !

@weerd Looking at this PR, it seems like dosomething_helpers_get_current_campaign_run_for_user() already associates a new signup with the current campaign run upon building it. I believe when a new campaign run is created, it's also set to the campaign's current run, so #1 (at least for signups) is already done?
cc @namimody

oh, maybe it doesn't update the current run upon creation of new run after all!
Now I see that current run gets set manually here:

So updated steps:

Automate current run to update based on each of the current runs dates.
Add to user interface to be able to retroactively associate campaign signups and reportbacks with the correct run.

@chloealee this issue is about moving the signup and reportback activity to the run node, not about associating the run to the campaign node

@angaither so is this editing the user interfaces here and here (or to create a new interface) to do something like click on the run nid, type in new run nid, backend makes sure the run nid exists and is associated to the correct campaign, and save?

@chloealee you can use this as an opportunity to remove the archive activity form, since this is an unused feature.
you can replace the form with this new migration feature

@namimody do we want to be able to migrate activity from run to run (that belong to the same campaign) or also across campaigns (e.g. migrate Comeback Clothes run 1 activity to Thumb Wars run 1)?

Question (and potential land mine?) -- Now that we've removed the unique key on uid and nid, for data queries based on Run -- couldn't we query by Reportback created date to determine what Run a reportback should associated with, instead using the Run nid value?
If we go this route -- the issue turns into making sure the Start/End dates are accurate for Campaign Runs (and refactoring data queries accordingly), vs whether the Run field is accurate for all signups and reportbacks and building out migrate webforms.
This is the approach I've been considering for v2 / Guardian.

@aaronschachter I don't know too much about how this works, but I guess I have a few initial questions:

From a data perspective, does this mean we would have to input the start and end dates of all runs instead of simply using the run ID? From a simplicity perspective, I feel like simply using the run ID is more simple?
Every so often, we have to add a reportback manually for a member who has missed the deadline for any number of reasons. While this use case is definitely not the majority of reportbacks, if the "Created By" date is outside of the designated start/end dates, we could have a cohort of reportbacks floating around without an assigned run, which would be problematic, right?

@chloealee because of situations like the one detailed in #6237, I'm inclined to say that being able to migrate activity across campaigns would be a handy feature to have!
cc @angaither @mikefantini

From a data perspective, does this mean we would have to input the start and end dates of all runs instead of simply using the run ID?

We wouldn't be adding Run start/end dates to Reportbacks or Signups -- the suggestion is that for a given Signup/Reportback, to find out which Run it belongs to, we query for the Campaign Run that was open during the time submitted. If we go this approach, we longer need to store the Run on the Signup/Reportback at all. This helps to avoid scenarios where Signups and Reportbacks are created with incorrect Runs because of configuration errors -- like the convo you linked to in Slack where it sounds like the Run was created a few days late, after Members had already submitted Signup/Reportbacks to the  now-previous Run.
This for sure would require some code changes and changes to any data aggregation pulls we do -- but I think it would simplify things in the long run and especially help us in migrating to v2.

Every so often, we have to add a reportback manually for a member who has missed the deadline for any number of reasons.. if the "Created By" date is outside of the designated start/end dates, we could have a cohort of reportbacks floating around without an assigned run, which would be problematic, right?

This could be solved by making the Created Date editable, so staff could set the Created Date to a date within the range to associate it to the desired Run.

Because of situations like the one detailed in #6237, I'm inclined to say that being able to migrate activity across campaigns would be a handy feature to have!

My $0.02 is that it's a relatively dangerous feature to add because it opens up a new door to poke holes in our data integrity.  Misfires (users accidentally submitting the Migrate Campaign form, selecting incorrect Campaign) could go unnoticed, and could be quite difficult to troubleshoot if/when the mistakes were made long before we find them.

Thanks @aaronschachter and @namimody ! All really great points and thanks for flagging! Chatted with @angaither this am at our check in and think it's best to move forward by being able to edit campaign run instead of edit dates - there are many reportbacks/signups that need to get migrated to a different run and currently, all runs do not have the correct timestamps and some are associated with the wrong node.

I'm slightly concerned if our Runs don't have the correct timestamps that the migration forms may cause more incorrect data.
Just to clarify: the potential form we're talking about would bulk migrate all activity from one Run to a different Run -- not just a form for a single Signup/Reportback. Is that correct?

@aaronschachter yes, this will bulk migrate all activity and not just a single signup/reportback!
Per our sprint sync, we'll put a hold on this issue for now and revisit after this hackweek sprint and discuss further then!

going to close this one out for meow since we got the inbox down to zero, and leads aren't blocked anymore!

The GL EN translation of Dunk You Very Much (https://www.dosomething.org/node/6647/edit/en-global) didn't have a close date, but it was supposed to have been closed on April 1, 2016 to coincide with the US EN run. We just added the end date to close out this campaign.
We'll need to do a similar thing w/ the data here -- create a new Run (in GL EN) and attribute the activity received after April 2, 2016 to that new run. The run should have a start date of April 2, 2016 and no end date (we want to keep this GL EN translate campaign open indefinitely).


Error when running TreatmentPatterns?

Apologies if this is not the right place to ask, but I've been getting an error when I try to run TreatmentPatterns using code in the package information.
I've tried running the code from here https://darwin-eu-dev.github.io/TreatmentPatterns/articles/TreatmentPatternsStudy.html#step-4-execute-study (as below)
dataSettings <- createDataSettings(OMOP_CDM = FALSE,
cohortLocation =
file.path(system.file(package = "TreatmentPatterns"),
"examples", "other format", "inst",
"cohorts", "input_cohorts.csv"))
cohortSettings <-
createCohortSettings(
targetCohorts = data.frame(cohortId = c(1),
cohortName = c('Hypertension')),
eventCohorts = data.frame(cohortId = c(10, 11, 12, 13, 14),
cohortName = c('Hydrochlorothiazide', 'Metorolol',
'Amlodipine', 'Lisinopril', 'Losartan')),
cohortsFolder = file.path(system.file(package = "TreatmentPatterns"),
"examples", "other format", "inst", "cohorts"))
pathwaySettings <- createPathwaySettings(targetCohortId = 1, eventCohortIds = c(10, 11, 12, 13, 14))
saveSettings <- createSaveSettings(databaseName = "IPCI", rootFolder = getwd())
executeTreatmentPatterns(dataSettings = dataSettings,
cohortSettings = cohortSettings,
pathwaySettings = pathwaySettings,
saveSettings = saveSettings)
But I get the following error:
Warning: Error in &&: 'length = 3' in coercion to 'logical(1)'
3: shiny::runApp
2: TreatmentPatterns::launchResultsExplorer
1: executeTreatmentPatterns
Error in is.call(funBody[[idx]]) && as.character(funBody[[idx]][[1]]) ==  :
'length = 3' in coercion to 'logical(1)'
Any help would be much appreciated, Thanks, Sophie

Hi @SophieScanlon, this approach is outdated with current version of TreatmentPatterns for DARWIN, it is also not available anymore on the latest package website.
I would suggest one of the following solutions: 1) following the updated instructions, if whatever you're trying to do is DARWIN related; or 2) Use the original version found here, with the instructions found here.


Safely inspect bundles for classes

Fixes #1006
Makes sure we don't check classes in not loaded bundles.

@hramos @nlutsenko, we are kinda stuck here with that one. Could you review, advise?

Thanks @hramos !

@flovilmart @hramos . Our startup almost completed our project using ParseSever with iOS&Android SDK. We planning to go live.  Do we expect iOS/Android SDK get the update like facebook does? We need to inform this to investors. Very critical.
Please guide us.

@hramos I'll need the commit access to the repo as Cocoapods require the tag to be pushed before
I can send pod to trunk. Opening #1111

@flovilmart invited

Turns out I don't have access to the pods either ;/
!] You<EMAIL_ADDRESS>are not allowed to push new versions for this pod. The owners of this pod are<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>and<EMAIL_ADDRESS>```

Anyone have pod access to push out 1.14.3? Please?

@flovilmart We manually put this change in our now-production app and are seeing a crash (unknown selector sent to instance). Specifically, it appears that _registerSubclassesInLoadedBundle: can be called with objects (NSString apparently) which are not NSBundle objects, and the loaded message is sent to an object which doesn't handle the selector. I'd guess this is coming from the NSBundleDidLoadNotification note.object but haven't verified that.
An obvious armor for this is to ensure the object is of the intended type in _registerSubclassesInLoadedBundle.
i.e. Change:
if (!bundle.loaded || !bundle.executablePath) {

to
if (![bundle isKindOfClass:NSBundle.class] || !bundle.loaded || !bundle.executablePath) {

(though it would be nice to understand why we're not getting NSBundle objects, this will prevent the crash).
Since 1.14.3 has yet to be released, this change (or similar) prior to release would be appreciated.
Cheers,
Levi

The changes have been merged to master, can you open a Pr with your suggestion and the fix?

@flovilmart Cheers. Here's the pull: https://github.com/ParsePlatform/Parse-SDK-iOS-OSX/pull/1119


Axis Annotations: Unusable table on Windows

To reproduce:

Open any dataset on Windows and view the Navigation->Annotation tab

Needs assessment before fixing.


Can't play particles on forge

I've tried lots of solutions but I can't find a way to play particles on forge 1.18. Any help is appreciated!

Any debug information? like latest.log or debug.log

I have the same problem. It seems like you had a broken Forge setup and that's why I had to download some dependencies. I downloaded everything, launched Forge, Minecraft starts, but it says: "[14:07:47] [Render thread/ERROR] (EffekAssetLoader) Failed to load aaa_particles:fire
[14:07:47] [Render thread/ERROR] (EffekAssetLoader) Failed to load aaa_particles:lightning"
I'll attach the logs to this message.
latest.log
Please help me! (Version 1.19.2 (yours))

same problem

not sure if i have same problem but ive followed the guide in the issues and cant spawn any on neoforge


Wrong scrollbars instruction

Problem/Motivation
The instruction you gave to add the new scrollbars theme is incorrect, coz you can't have duplicate "css" object key.
This will make the scrollbars.css replace the theme.css.
editorTheme: {
    page: {
        css<EMAIL_ADDRESS>        css<EMAIL_ADDRESS>    }
}

(Why the issue was filed)

Node-RED version: version: 1.1.2
Platform/OS: KDE Neon & Ubuntu
Browser: Chrome Version 83.0.4103.116 (Official Build) (64-bit)

Steps to reproduce

(How can someone else see it happen. If possible,
add one or more screenshots)

Proposed changes
The correct way is to put them in an array instead.
editorTheme: {
    page: {
        css<EMAIL_ADDRESS><EMAIL_ADDRESS>    }
}

(If you have a proposed change, workaround or fix,
describe it here)

🤦🏼♂ Thanks for the heads up.


Tabbable Tabs not working in 2.0 docs

The tabbable tabs example in components.html in the 2.0 docs does not work. I could make it work by adding the data-toggle="tab" attribute, changing the ids to be unique, and adding the bootstrap-tab.js script onto the page. Is this the way we should use the tabbable tabs, or is something broken in the code?
If we should use the data-toggle="tab" and the js plugin, the docs should be updated.

I'm sure but you are confusing docs/components.html with docs/javascript.html
Components are not supposed to have JS enabled.

Lots of docs and code changes still brewing in 2.0 - not quite ready to file tickets against them. thanks!

@pokonski I did want docs/components.html, not docs/javascript.html, and the tabbable tabs example is totally useless, because it is not a static tab, and it used to work when I used an older checkout of 2.0.
@fat OK, thats fine if 2.0 is not ready yet, just wondering, is the tabbable tabs going to work in 2.0, or should we use the data-toggle="tab" with the JS plugin

I don't really understand your question. Tabs work, only docs don't use them.


TravisCI yaml parameterized

This change fixes #143, to make some specific TravisCI args parameter.

Pull Request Test Coverage Report for Build 412

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 46.565%

Totals

Change from base Build 409:
0.0%

Covered Lines:
366

Relevant Lines:
786

💛  - Coveralls


How to run a slave on Windows?

Hi, I think I have a server set up on Linux (instructions incredibly unclear!!) and I would like to add a Windows device to help transcode. How do I do this?

Windows is not supported yet, you can use docker or WSL2 to run the transcoder on Linux on Windows 🙂


refactor: Re-rule the RST files in this repo.

Description:
Describe in a couple of sentences what this PR adds
JIRA:
XXX-XXXX
Merge checklist:

[ ] All reviewers approved
[ ] CI build is green
[ ] Changelog record added
[ ] Documentation updated (not only docstrings)
[ ] Commits are squashed

Current dependencies on/for this PR:

master

PR #240   👈

PR #241

This comment was auto-generated by Graphite.


Deployment to Prod isn't happening

As title suggests, new merges are not being pushed to prod. Guessing it might have somethin' to do with #864?
I know for sure #879 and #880 are not live (manually checked).
@EricPedley @ap0nia

          @KevinWu098 @EricPedley I saw that it got merged already but when I visit the site the error is still reproducible. Is there something went wrong maybe?

Originally posted by @JackyZzZz in https://github.com/icssc/AntAlmanac/issues/877#issuecomment-1928757407

I think it's fixed 🤓


Add another workaround for rspec-puppet testing

As a follow up to d6c401045103f299ff3cf9cbdeb2ea2abe554f98, (made before I started using Puppet 6), we need to
bypass actual decryption when using onceover and node_encrypt.secret.
This is needed because rspec-puppet resolves Deferred functions.
See https://github.com/rodjek/rspec-puppet/pull/743
We also can't just mock this function in onceover, because the normal
way to mock a ruby function is with a puppet language function, but
these do not work with Deferred.

Did you try mocking like so?
https://github.com/binford2k/binford2k-node_encrypt/blob/bf4a0f4525266105f3963e2655f59b6c687909c4/spec/defines/file_spec.rb#L38-L40

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Alexander Fisher seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks @alexjfisher for your work on this, but I'm voting to close this due to a long period of inactivity.
Feel free to re-open


Create a QHub -  CLI diagram

cc @asmijafar20

I can see we added more flags to qhub init command. Do we need to change the steps which we already have defined in our docs?

Hi, @asmijafar20. All the flags and commands in the diagram above are already part of Nebari. They are not necessary for a basic deployment (as we have default values for them) but can also be passed for customization once the user already understands its meaning. -- currently on nebari.dev we don't have a page explanation of those yet

Hi, @asmijafar20. All the flags and commands in the diagram above are already part of Nebari. They are not necessary for a basic deployment (as we have default values for them) but can also be passed for customization once the user already understands its meaning. -- currently on nebari.dev we don't have a page explanation of those yet

Okay. So I think we could have a help command where we can also define these flags and add their other customizations. Let me know what do you think.

Hi, @asmijafar20. All the flags and commands in the diagram above are already part of Nebari. They are not necessary for a basic deployment (as we have default values for them) but can also be passed for customization once the user already understands its meaning. -- currently on nebari.dev we don't have a page explanation of those yet

Okay. So I think we could have a help command where we can also define these flags and add their other customizations. Let me know what do you think.

Yup, also, I think drafting a Help message and adding those commands would be a good start on using Typer

We definitely need a help command

Got an idea of having a setup command like qhub setup (any cloud provider) and asks permissions you need to enable for qhub while creating JSON file or exporting cloud provider credentials and project id in this command. And if user didn't setup the cloud provider then it shows the message with the docs link  on how of do it. Like this

Let me how it sound to you folks. @viniciusdc @trallard @iameskild

When we finish our work on the new CLI, we might want to create another such diagram and add it to the docs. For now, I believe this issue can be closed. @trallard @asmijafar20 let me know if you feel otherwise 👍


[ASCII-1022] Use status component for security agent

What does this PR do?
Migrate security agent to use the status component to render the status response and build the flare information.
To use the status component with the current code of the security agent we had to move certain values to fx.Provide options.
fx.Provide(func() startstop.Stopper {
	return startstop.NewSerialStopper()
}),
fx.Provide(func(config config.Component, statsd statsd.Component) (ddgostatsd.ClientInterface, error) {
	return statsd.CreateForHostPort(pkgconfig.GetBindHost(), config.GetInt("dogstatsd_port"))
})

Those are later use on other fx.Provide blocks
fx.Provide(func(stopper startstop.Stopper, log log.Component, config config.Component, statsdClient ddgostatsd.ClientInterface, demultiplexer demultiplexer.Component) (status.InformationProvider, error) {
	hostnameDetected, err := utils.GetHostnameWithContextAndFallback(context.TODO())
	if err != nil {
		return status.NewInformationProvider(nil), err
	}

	runtimeAgent, err := runtime.StartRuntimeSecurity(log, config, hostnameDetected, stopper, statsdClient, demultiplexer)
	if err != nil {
		return status.NewInformationProvider(nil), err
	}

	if runtimeAgent == nil {
		return status.NewInformationProvider(nil), nil
	}

	return status.NewInformationProvider(runtimeAgent.StatusProvider()), nil
})

This way we can continue to pass status provider using value groups 🎉
There is one downside. We call utils.GetHostnameWithContextAndFallback(context.TODO()) twice.
In the previous state the runtimeAgent and the complianceAgent were keep around to get the status output and for the flare output. This is no longer the case as the status component has everything it needs to display and generate the flare.
With those changes we were able to simplify the security agent server and flare generation 😄
The templates added to the new status providers are a copy from the ones in pkg/status/render/templates/*. I'm not deleting those templates until the migration for the status component is fully done. That way if at any time I have to revert we can easily go back to use the pkg/status package.
Example of security agent status using this branch

Example of security agent status using this branch
==============================================
Security Agent (v7.53.0-devel+git.204.0850d24)
==============================================
  Status date: 2024-03-04 15:25:07.654 UTC<PHONE_NUMBER>654)
  Agent start: 2024-03-04 15:24:45.972 UTC<PHONE_NUMBER>972)
  Pid: 10052
  Go Version: go1.21.7
  Python Version: n/a
  Build arch: arm64
  Agent flavor: security_agent
  Log Level: info

  Paths
  =====
    Config File: dev/dist/datadog.yaml
    conf.d: /etc/datadog-agent/conf.d
    checks.d: /etc/datadog-agent/checks.d

========
Hostname
========

  hostname: gustavovm
  socket-fqdn: gustavovm
  socket-hostname: gustavovm
  hostname provider: os
  unused hostname providers:
    'hostname' configuration/environment: hostname is empty
    'hostname_file' configuration/environment: 'hostname_file' configuration is not enabled
    aws: not retrieving hostname from AWS: the host is not an ECS instance and other providers already retrieve non-default hostnames
    azure: azure_hostname_style is set to 'os'
    container: the agent is not containerized
    fargate: agent is not runnning on Fargate
    fqdn: 'hostname_fqdn' configuration is not enabled
    gce: unable to retrieve hostname from GCE: GCE metadata API error: Get "http://<IP_ADDRESS>/computeMetadata/v1/instance/hostname": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

Host Info
=========
  bootTime: 2024-03-04 11:33:43 UTC<PHONE_NUMBER>000)
  hostId: 2277f990-7bde-4dd3-9a48-0df3835454c6
  kernelArch: aarch64
  kernelVersion: 5.15.0-97-generic
  os: linux
  platform: ubuntu
  platformFamily: debian
  platformVersion: 22.04
  procs: 159
  uptime: 3h52m1s
  virtualizationRole: guest

================
Runtime Security
================

  Reliable: Sending compressed logs in HTTPS to runtime-security-http-intake.logs.datadoghq.eu on port 443
  Connected: false
  Events received: 0

  Self Tests
  ==========

    Last execution: <no value>

    Succeeded: none

    Failed: none

  Policies
  ========

==========
Aggregator
==========

  Dogstatsd Metric Sample: 1
  Event: 1
  Events Flushed: 1
  Number Of Flushes: 3
  Series Flushed: 7
  Service Checks Flushed: 3

==========
Compliance
==========

  Reliable: Sending compressed logs in HTTPS to cspm-intake.datadoghq.eu on port 443

  Checks
  ======

=========
Forwarder
=========

  Transactions
  ============
    Cluster: 0
    ClusterRole: 0
    ClusterRoleBinding: 0
    CronJob: 0
    CustomResource: 0
    CustomResourceDefinition: 0
    DaemonSet: 0
    Deployment: 0
    Dropped: 0
    HighPriorityQueueFull: 0
    HorizontalPodAutoscaler: 0
    Ingress: 0
    Job: 0
    Namespace: 0
    NetworkPolicy: 0
    Node: 0
    OrchestratorManifest: 0
    PersistentVolume: 0
    PersistentVolumeClaim: 0
    Pod: 0
    ReplicaSet: 0
    Requeued: 0
    Retried: 0
    RetryQueueSize: 0
    Role: 0
    RoleBinding: 0
    Service: 0
    ServiceAccount: 0
    StatefulSet: 0
    VerticalPodAutoscaler: 0

  Transaction Successes
  =====================
    Total number: 7
    Successes By Endpoint:
      check_run_v1: 3
      intake: 1
      series_v2: 3

  On-disk storage
  ===============
    On-disk storage is disabled. Configure `forwarder_storage_max_size_in_bytes` to enable it.

  API Keys status
  ===============
    API key ending with 72724: API Key valid

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Validate that the security agent status output is correct. Both text security-agent status and JOSN security-agent status -p

Sections that no longer are displayed in the text output:

Clocks The information is part of the header now System time

New Sections that are displayed:

Aggregator
Forwarder

These sections are displayed because the security agent use these components.

Generating a security agent flare remains to work as expected. security-agent flare

/merge


Django 5.0, py3.12 and pre-commit

Add Django 5.0
Drop Django 4.0 and 4.1
Drop python 3.6, 3.7
Replace pep8 and pytest-pep8 with pre-commit with flake8 and autopep (I left off black for now, but I recommend adding that or ruff)

@tim-schilling Thanks for this - I had another branch in flight locally that moves us to ruff, but I'll make sure I add pre-commit as per your suggestions. Sorry not to just merge this as-is, because it's a valid contribution

No worries!

@tim-schilling Absolutely - that's done in spirit along with a move to GHA over in https://github.com/mozilla/django-csp/commit/3eadb4c785c78e1b5ad0e178e7eb13d88572f6fb

Ah, I missed that. Excellent!


Broken link

Under the Microsoft Flow for enterprise developers section the Build Azure Functions link points to https://docs.microsoft.com/azure/azure-functions/functions-flow-scenario which doesn't exist anymore

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

ID: 97e534fb-0608-62e2-e257-77ca64397af6
Version Independent ID: 0f9e11dc-455d-e1cf-fbc1-89a07cb53ef6
Content: Microsoft Flow for enterprise developers, ISVs, and partners - Microsoft Flow
Content Source: flow-docs/developer/dev-enterprise-intro.md
Service: flow
GitHub Login: @mgblythe
Microsoft Alias: mblythe

@rbnswartz The link is fixed now; thanks for the feedback.
Closing the issue.


Refactor protoc-gen-go generator - split up generateMessage

Split actual text generation passes of generateMessage out by
first building a data structure suitable for code generation
and then generate the output for each field in separate methods.
Partially incorrect and unneccessary usage of g.In() and g.Out()
has als been removed throughout the code generation as the output
is properly formatted at the end of code generation anyway.
The functionality is unchanged except for the order of oneof
methods in the output file.

I've now followed the instructions for someone working on the Go team at google. As far as I understand it, the CLA check should now clear.

The generated json differs, will try again when I've fixed that.

With the proper protoc, I could update the golden files without destroying the json names, trying again...


Update sbt-scalafix to 0.9.32

Updates ch.epfl.scala:sbt-scalafix from 0.9.30 to 0.9.32.
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!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "ch.epfl.scala", artifactId = "sbt-scalafix" } ]

labels: sbt-plugin-update, early-semver-minor, semver-spec-patch

Superseded by #198.


Misc changees

Ensure attach() is not run concurrently for a specific buffer
Rework status vars
Dirty fix for #263

Does gitsigns know remote's url as well? I can think of simplifying my custom go to gh command if I could read remote's url from variable rather than rerunning git commands.

It doesn't, but it would be easy to add. Gitsigns is basically just an async framework for running git commands. However simply adding it for no reason doesn't seem like a great idea. Maybe we can find a more generic solution? We already have an on_attach callback so maybe something using that?


Can't import 0.18.2 in a .ts file

Environment details

OS:
Node.js version:
npm version:
@google-cloud/common version: 0.18.2

Steps to reproduce
I tried to import the module like import * as common from '@google-cloud/common'; in ts/src/index.ts of
https://github.com/GoogleCloudPlatform/cloud-profiler-nodejs, and saw the following output during typescript compilation, which seem to come from this module
node_modules/@google-cloud/common/build/src/service-object.d.ts:29:107 - error TS2694: Namespace 'request' has no exported member 'Response'.

29 export declare type GetMetadataCallback = (err: Error | null, metadata?: Metadata | null, apiResponse?: r.Response) => void;
                                                                                ~~~~~~~~

node_modules/@google-cloud/common/build/src/service-object.d.ts:65:77 - error TS2694: Namespace 'request' has no exported member 'Response'.

65     (err: ApiError | null, instance?: ServiceObject | null, apiResponse?: r.Response): void;
                                                                               ~~~~~~~~

node_modules/@google-cloud/common/build/src/service-object.d.ts:68:41 - error TS2694: Namespace 'request' has no exported member 'Response'.

68     (err: Error | null, apiResponse?: r.Response): void;
                                           ~~~~~~~~

node_modules/@google-cloud/common/build/src/service-object.d.ts:157:71 - error TS2694: Namespace 'request' has no exported member 'Response'.

157     setMetadata(metadata: {}, callback?: (err: Error | null, resp?: r.Response) => void): void;
                                                                          ~~~~~~~~

node_modules/@google-cloud/common/build/src/service-object.d.ts:167:58 - error TS2694: Namespace 'request' has no exported member 'Response'.

167     request_(reqOpts: DecorateRequestOptions): Promise<r.Response | r.Request>;
                                                             ~~~~~~~~

node_modules/@google-cloud/common/build/src/service-object.d.ts:177:57 - error TS2694: Namespace 'request' has no exported member 'Response'.

177     request(reqOpts: DecorateRequestOptions): Promise<r.Response>;
                                                            ~~~~~~~~

node_modules/@google-cloud/common/build/src/service.d.ts:84:58 - error TS2694: Namespace 'request' has no exported member 'Response'.

84     request_(reqOpts: DecorateRequestOptions): Promise<r.Response>;
                                                            ~~~~~~~~

node_modules/@google-cloud/common/build/src/service.d.ts:94:57 - error TS2694: Namespace 'request' has no exported member 'Response'.

94     request(reqOpts: DecorateRequestOptions): Promise<r.Response>;
                                                           ~~~~~~~~

node_modules/@google-cloud/common/build/src/service.d.ts:103:63 - error TS2694: Namespace 'request' has no exported member 'Response'.

103     requestStream(reqOpts: DecorateRequestOptions): Promise<r.Response>;
                                                                  ~~~~~~~~

node_modules/@google-cloud/common/build/src/util.d.ts:2:23 - error TS2688: Cannot find type definition file for 'duplexify'.

2 /// <reference types="duplexify" />
                        ~~~~~~~~~

node_modules/@google-cloud/common/build/src/util.d.ts:22:28 - error TS7016: Could not find a declaration file for module 'duplexify'. '/usr/local/google/home/nolanmar/cloud-profiler-nodejs-working/cloud-profiler-nodejs/node_modules/duplexify/index.js' implicitly has an 'any' type.
  Try `npm install @types/duplexify` if it exists or add a new declaration (.d.ts) file containing `declare module 'duplexify';`

22 import * as duplexify from 'duplexify';
                              ~~~~~~~~~~~

node_modules/@google-cloud/common/build/src/util.d.ts:29:13 - error TS2694: Namespace 'request' has no exported member 'Response'.

29     resp: r.Response;
               ~~~~~~~~

node_modules/@google-cloud/common/build/src/util.d.ts:110:17 - error TS2694: Namespace 'request' has no exported member 'Response'.

110     response: r.Response;
                    ~~~~~~~~

node_modules/@google-cloud/common/build/src/util.d.ts:163:18 - error TS2694: Namespace 'request' has no exported member 'Response'.

163     response?: r.Response;
                     ~~~~~~~~

node_modules/@google-cloud/common/build/src/util.d.ts:174:18 - error TS2694: Namespace 'request' has no exported member 'Response'.

174     response?: r.Response;
                     ~~~~~~~~

node_modules/@google-cloud/common/build/src/util.d.ts:178:52 - error TS2694: Namespace 'request' has no exported member 'Response'.

178     (err: Error | null, body: ResponseBody, res: r.Response): void;
                                                       ~~~~~~~~

node_modules/@google-cloud/common/build/src/util.d.ts:195:35 - error TS2694: Namespace 'request' has no exported member 'Response'.

195     shouldRetryFn?: (response?: r.Response) => boolean;
                                      ~~~~~~~~

node_modules/@google-cloud/common/build/src/util.d.ts:218:44 - error TS2694: Namespace 'request' has no exported member 'Response'.

218     handleResp(err: Error | null, resp?: r.Response | null, body?: ResponseBody, callback?: BodyResponseCallback): void;
                                               ~~~~~~~~

node_modules/@google-cloud/common/build/src/util.d.ts:227:45 - error TS2694: Namespace 'request' has no exported member 'Response'.

227     parseHttpRespMessage(httpRespMessage: r.Response): ParsedHttpRespMessage;

Yuck.  This is because request and duplexify are exported types :(  In the short term - you should be able to npm install --save-dev @types/request @types/duplexify
I will start working on a better fix now though.


Fail to install thin-edge on Centos7

Describe the bug
On behalf of Weihan Chan.
I am trying to install thin-edge in Centos7 vm. I have followed the manual installation steps of user guides, but fail .
When I install ‘tedge’ , error message throw.
Unpacking tedge (0.6.1) over (0.6.1) ...
dpkg: dependency problems prevent configuration of tedge:
tedge depends on mosquitto; however:
Package mosquitto is not installed.
But I am sure the mosquitto is installed in Vm, check below info
Installed Packages
mosquitto.x86_64                                           1.6.10-1.el7                                            @epel[wech@daeipresal51156 li
To Reproduce

Expected behavior

Screenshots

Environment (please complete the following information):

Centos7 vm
thin-edge.io 0.6.1

Additional context

@ Weihan , Can you please share the precise commands you used to install thin-edge?

@didier-wenzek  I am weihan.chen from SAG
Yes, in my centos7 vm, I am going to install thin-edge with tedge_0.6.0_amd64.deb
For the dependance , mosquitto is required, then I install mosquitto with ‘ yum install mosquitto ‘.
And the system show that the mosquitto is installed successfully.
I then install tedge with dpkg command , but the message show that Package mosquitto is not installed.

With https://github.com/thin-edge/thin-edge.io/pull/1098, mosquitto will be a recommendation rather than a dependency, fixing the issue you have.

@henrychan What is the status of this issue on your side?
We no responses within 5 days, I will close this issue.


chore(README): fixes typo

cases to testCases

lol cool Atlassian, take my libraries and lock me out of them

I did not realise that. I will check with @jonycheung and get this sorted. 🙂


Documentation website page results in 404 error when there's no trailing slash

Installed product versions

Visual Studio 2019 Enterprise Preview (16.0.0 Preview 2.1)
This extension: v0.1.0

Description
If there's no trailing slash on the website page url, it results in a 404 error.
Steps to recreate

Type https://luminous-software.solutions/extensibility-logs into a browser, without a trailing slash (or click the link above).

Current behavior
https://luminous-software.solutions/extensibility-logs/ (with a trailing slash) opens the web page.
https://luminous-software.solutions/extensibility-logs (without a trailing slash) results in a 404 error.
Both https://luminous-software.solutions/time-savers/ (with a trailing slash) and https://luminous-software.solutions/time-savers (without a trailing slash) have always opened the web page.
Expected behavior
Both https://luminous-software.solutions/extensibility-logs/ (with a trailing slash) and https://luminous-software.solutions/extensibility-logs (without a trailing slash) should open the web page.

The problem seems to have resolved itself


Issue with authentication

There seems to be an issue with the FortniteAuthenticator class
javax.naming.AuthenticationException: Failed to retrieve cookies.         at athena.authentication.FortniteAuthenticator.authenticate(FortniteAuthenticator.java:63)         at athena.AthenaImpl.login(AthenaImpl.java:92)
I was able to fix it by saving all cookies from the https://www.epicgames.com/id/api/csrf response and putting them in the https://www.epicgames.com/id/api/login request.

Yeah, I need to change to using a cookie jar so everything could be simplified. With that being said this project is pretty inactive and there are a few issues that need to be addressed. I started a new version of Athena but I'm only working on it in my free time so its going pretty slow (I'm also really burned out). If you wish to have a newer authentication class I have written a newer one (which also now supports 2FA).
https://hastebin.com/utefiratut.php
Some things may need to be replaced like the JsonFind class and maybe some ResponseConsumer methods since these are new.


Map Tiles are not loading

Do you think this is just another expired subscription? Or is there some incompatibility?

Looks like our access token expired. Not sure of the exact reason. @cncoleman, can you send me the credentials for the Mapbox account for hdlab offline and I will take a look?


Restore fail

Steps to reproduce

Make a backup
Clear data
Restore backup

Expected behavior
Backup should restore read chapters, trackers and categories.
Actual behavior
Only titles are restored. Trackers, categories, reading progress, history fail to restore.
Every title fails with "FOREIGN KEY constraint failed (code 787)".
Crash logs
No response
Tachiyomi version
Preview r532
Android version
LineageOS 20 (Android 13)
Device
Samsung S9
Other details
No response
Acknowledgements

[X] This is a TachiyomiSY specific issue that does not happen in Tachiyomi Preview.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an extension, I should be opening an issue in the extensions repository.
[X] I have gone through the FAQ and troubleshooting guide.
[X] I have updated the app to version 1.9.4.
[X] I have updated all installed extensions.
[X] I will fill out all of the requested information in this form.

I'm having the same issue, but I was able to somewhat circumvent it by;

importing the backup
go through default category and click on every single title until chapters are loaded
import the backup again

This should place the manga in the correct categories and set progress and trackers

Fixed in the next build


pyright: 1.1.378 -> 1.1.380

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for pyright is: Type checker for the Python language
meta.homepage for pyright is: https://github.com/Microsoft/pyright
meta.changelog for pyright is: https://github.com/Microsoft/pyright/releases/tag/1.1.380
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.1.380 with grep in /nix/store/gnn9r0r366yhb02bkj15ixmrfgyxnrag-pyright-1.1.380
found 1.1.380 in filename of file in /nix/store/gnn9r0r366yhb02bkj15ixmrfgyxnrag-pyright-1.1.380

Rebuild report (if merged into master) (click to expand)

110 total rebuild path(s)

110 package rebuild(s)

First fifty rebuilds by attrpath

aider-chat
chatblade
chatgpt-retrieval-plugin
checkov
home-assistant-component-tests.openai_conversation
imaginer
khoj
llm
mealie
open-interpreter
open-webui
openai
openllm
pentestgpt
pyright
python311Packages.graphrag
python311Packages.guidance
python311Packages.inline-snapshot
python311Packages.instructor
python311Packages.langchain
python311Packages.langchain-aws
python311Packages.langchain-azure-dynamic-sessions
python311Packages.langchain-chroma
python311Packages.langchain-community
python311Packages.langchain-core
python311Packages.langchain-huggingface
python311Packages.langchain-mongodb
python311Packages.langchain-openai
python311Packages.langchain-standard-tests
python311Packages.langchain-text-splitters
python311Packages.langgraph
python311Packages.langgraph-checkpoint
python311Packages.langgraph-checkpoint-postgres
python311Packages.langgraph-checkpoint-sqlite
python311Packages.langsmith
python311Packages.litellm
python311Packages.llama-index
python311Packages.llama-index-agent-openai
python311Packages.llama-index-cli
python311Packages.llama-index-core
python311Packages.llama-index-embeddings-gemini
python311Packages.llama-index-embeddings-google
python311Packages.llama-index-embeddings-huggingface
python311Packages.llama-index-embeddings-ollama
python311Packages.llama-index-embeddings-openai
python311Packages.llama-index-graph-stores-nebula
python311Packages.llama-index-graph-stores-neo4j
python311Packages.llama-index-graph-stores-neptune
python311Packages.llama-index-indices-managed-llama-cloud

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/gnn9r0r366yhb02bkj15ixmrfgyxnrag-pyright-1.1.380 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A pyright https://github.com/r-ryantm/nixpkgs/archive/51b23f4d1f0ac7f70fcfdaf869e9b0075c750b1e.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/51b23f4d1f0ac7f70fcfdaf869e9b0075c750b1e#pyright

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/gnn9r0r366yhb02bkj15ixmrfgyxnrag-pyright-1.1.380
ls -la /nix/store/gnn9r0r366yhb02bkj15ixmrfgyxnrag-pyright-1.1.380/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

@NixOS/nixpkgs-merge-bot merge


Some typos fixed

Just some spell checking 😁
Thanks for the project!

Thanks @ivanovv , these have been merged.


Supporting State detection (US and India)

This PR does the following:

Adds support for States (type and properties)
Adds the static state names, isocodes, fips codes json file
Detection of States
Ordering between State properties
Ordering between States and Countries (State given preference)
Updates and adds new unit tests.

Thanks for the review Jennifer! Yes, that commented out code was refactored and I forgot to delete it :(


Change argument name in DataFrame.drop_duplicates

Just a tiny suggestion:
The keyword argument for specifying which columns to consider in drop_duplicates is called col_or_columns. Maybe change the name to col or to columns? Or the strangely long name is intended to make it clear that you can either pass in a label or a sequence of labels?
Thanks,
Marius

Yes, the latter case. You don't actually have to pass any columns at all, which is why it's a keyword and not a positional argument. Probably naming it col is not such a big deal

ok, I changed it to cols, consistent with pivot_table and other places

Cool!
On 5 February 2012 00:55, Wes McKinney
<EMAIL_ADDRESS>wrote:

ok, I changed it to cols, consistent with pivot_table and other places

Reply to this email directly or view it on GitHub:
https://github.com/wesm/pandas/issues/734#issuecomment-3814715


various fixes (mainly WW related) from fresh edison/rpi0 install

also incorpates @jpcunningh https://github.com/openaps/oref0/pull/1085 and https://github.com/openaps/oref0/pull/1086 (sorry for not seperating my PR and @jpcunningh 's)
fixes a problem with WW pumps that the radio_locale is not in the pump.ini. Also reported by @cluckj on https://gitter.im/openaps/oref0?at=5b78b34a802bc42c5f3b4870
fixes a nasty issue with timeouts with pip3/pip packages, see https://github.com/openaps/oref0/issues/1095
upgrade to node 8.11.4 and thus npm 5.6.0

Work in progress / do not merge yet.
The uploading of cgm data with G4-go does not work for me with tokenbased authentication. Working on that.
@scottleibrand can you do a review so far?

@PieterGit, will you incorporate the changes youn requested in this PR such that I should close the other 2 PRs?
Thanks!

Fixed merge conflicts and made a few other small changes in https://github.com/openaps/oref0/compare/dev...PieterGit-201808_upgrade?expand=1 to get it to the point where I think it's ready to merge.  @PieterGit is this/that ready to merge from your perspective?

Testing that, I get:
npm ERR! invalid<EMAIL_ADDRESS>/usr/lib/node_modules/oref0/node_modules/share2nightscout-bridge
npm ERR! invalid<EMAIL_ADDRESS>/usr/lib/node_modules/oref0/node_modules/yargs
Investigating...

The first time I ran oref0-runagain, it errored out completely, complaining about missing packages and files.  Re-running it, it still got a bunch of complaints about share2nightscout-bridge and yargs, but it continued past them successfully.  On the third run, it didn't complain at all.  Not sure if there's some order-of-operations bug here or what: we'll have to keep an eye on what happens on additional rigs.

Looks like the latest yargs is incompatible with node 0.10:
/root/src/oref0/node_modules/yargs/index.js:5
const yargs = require('./yargs')
^^^^^
SyntaxError: Use of const in strict mode.
at Module._compile (module.js:439:25)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object. (/root/src/oref0/bin/oref0-get-profile.js:42:16)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
Could not run oref0-get-profile
So I just updated #1136 to force upgrade to node 8+

Closing in favor of #1136


✨Menu: className and style props are put on outermost element

resolves: #1672
This will allow users to overwrite styles on an element that is also used by popper to set position via position, inset (top, left, bottom, right) and transform, but I think it's fine, users will quickly realize if they try that..

Actually, is there a reason why ...rest is sent to the list inside in the first place?

Actually, is there a reason why ...rest is sent to the list inside in the first place?

I guess its for the components props to get where they are supposed to as they are are used on different parts in the component-tree. Question is where should our users expect changes to occur when they supply their own className and style. I am thinking it should be the outermost elements so that our users can set margins, css-grid, flex etc used for positioning, but this might ofcourse limit the possibility of overriding other styling. I have a gut feeling we need to check all our components to make sure our components are behaving correctly in this manner 🙈

I guess its for the components props to get where they are supposed to as they are are used on different parts in the component-tree. Question is where should our users expect changes to occur when they supply their own className and style. I am thinking it should be the outermost elements so that our users can set margins, css-grid, flex etc used for positioning, but this might ofcourse limit the possibility of overriding other styling. I have a gut feeling we need to check all our components to make sure our components are behaving correctly in this manner 🙈

As long as the outermost element is selectable with css then everything inside is selectable as well with > div > ul etc, of course with the  caveat that internal refactors from us will make breaking changes if you do this. But then again I hope this isn't a commonplace thing to do.

I guess its for the components props to get where they are supposed to as they are are used on different parts in the component-tree. Question is where should our users expect changes to occur when they supply their own className and style. I am thinking it should be the outermost elements so that our users can set margins, css-grid, flex etc used for positioning, but this might ofcourse limit the possibility of overriding other styling. I have a gut feeling we need to check all our components to make sure our components are behaving correctly in this manner 🙈

As long as the outermost element is selectable with css then everything inside is selectable as well with > div > ul etc, of course with the caveat that internal refactors from us will make breaking changes if you do this. But then again I hope this isn't a commonplace thing to do.

I've made an issue #1674 for us to investigate this. If it was wrong in Menu, it might be wrong elsewhere also 🤔


libsrt: init at 20210918

Description of changes
Init libsrt as preparation for obs-studio update (new dependency)
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

  /nix/store/iyygljx5wid0d4m7sjlvl8w753bc2bik-libsrt-20210918.drv
building '/nix/store/iyygljx5wid0d4m7sjlvl8w753bc2bik-libsrt-20210918.drv'...
unpacking sources
unpacking source archive /nix/store/x8d4xyhairxm7dn94libz6cmyrkw84rc-source
source root is source
patching sources
configuring
fixing cmake files...
cmake flags: -DCMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTING=OFF -DCMAKE_INSTALL_LOCALEDIR=/nix/store/dy8mnssy6wvs683sxqv622cny753kw6p-libsrt-20210918/share/locale -DCMAKE_INSTALL_LIBEXECDIR=/nix/store/dy8mnssy6wvs683sxqv622cny753kw6p-libsrt-20210918/libexec -DCMAKE_INSTALL_LIBDIR=/nix/store/dy8mnssy6wvs683sxqv622cny753kw6p-libsrt-20210918/lib -DCMAKE_INSTALL_DOCDIR=/nix/store/dy8mnssy6wvs683sxqv622cny753kw6p-libsrt-20210918/share/doc/libsrt -DCMAKE_INSTALL_INFODIR=/nix/store/dy8mnssy6wvs683sxqv622cny753kw6p-libsrt-20210918/share/info -DCMAKE_INSTALL_MANDIR=/nix/store/dy8mnssy6wvs683sxqv622cny753kw6p-libsrt-20210918/share/man -DCMAKE_INSTALL_OLDINCLUDEDIR=/nix/store/dy8mnssy6wvs683sxqv622cny753kw6p-libsrt-20210918/include -DCMAKE_INSTALL_INCLUDEDIR=/nix/store/dy8mnssy6wvs683sxqv622cny753kw6p-libsrt-20210918/include -DCMAKE_INSTALL_SBINDIR=/nix/store/dy8mnssy6wvs683sxqv622cny753kw6p-libsrt-20210918/sbin -DCMAKE_INSTALL_BINDIR=/nix/store/dy8mnssy6wvs683sxqv622cny753kw6p-libsrt-20210918/bin -DCMAKE_INSTALL_NAME_DIR=/nix/store/dy8mnssy6wvs683sxqv622cny753kw6p-libsrt-20210918/lib -DCMAKE_POLICY_DEFAULT_CMP0025=NEW -DCMAKE_OSX_SYSROOT= -DCMAKE_FIND_FRAMEWORK=LAST -DCMAKE_STRIP=/nix/store/j061mvdxw70xz20r2r0lr5lk0rcsjf9i-gcc-wrapper-11.3.0/bin/strip -DCMAKE_RANLIB=/nix/store/j061mvdxw70xz20r2r0lr5lk0rcsjf9i-gcc-wrapper-11.3.0/bin/ranlib -DCMAKE_AR=/nix/store/j061mvdxw70xz20r2r0lr5lk0rcsjf9i-gcc-wrapper-11.3.0/bin/ar -DCMAKE_C_COMPILER=gcc -DCMAKE_CXX_COMPILER=g++ -DCMAKE_INSTALL_PREFIX=/nix/store/dy8mnssy6wvs683sxqv622cny753kw6p-libsrt-20210918
CMake Warning:
  Ignoring extra path from command line:

   ".."

CMake Error: The source directory "/build/source" does not appear to contain CMakeLists.txt.
Specify --help for usage, or press the help button on the CMake GUI.

Currently not building, due to cmake error like #194518 with cmake (trying to get help in matrix/discourse)

From looking at the other repo and tests reasonable - must have overseen the package. thanks!


write more tests!!

Codecov Report

Merging #391 into experimental will decrease coverage by 59.11%.
The diff coverage is 32.43%.

@@                Coverage Diff                @@
##           experimental     #391       +/-   ##
=================================================
- Coverage         74.72%   15.61%   -59.12%
=================================================
  Files                24       23        -1
  Lines              1476     1499       +23
=================================================
- Hits               1103      234      -869
- Misses              373     1265      +892

Impacted Files
Coverage Δ

tests/test_api_plugins.py
22.35% <21.05%> (-77.65%)
:arrow_down:

tests/test_helpers_meta.py
44.44% <44.44%> (-55.56%)
:arrow_down:

vent/core/rq-dashboard/rq_dash_settings.py
0% <0%> (-100%)
:arrow_down:

vent/core/rq-worker/settings.py
0% <0%> (-100%)
:arrow_down:

vent/core/rq-worker/file_watch.py
2.43% <0%> (-82.93%)
:arrow_down:

vent/api/actions.py
13.22% <0%> (-80.43%)
:arrow_down:

vent/core/file-drop/test_file_drop.py
22.22% <0%> (-77.78%)
:arrow_down:

vent/helpers/logs.py
28.57% <0%> (-71.43%)
:arrow_down:

...ent/core/rmq-es-connector/test_rmq_es_connector.py
29.72% <0%> (-70.28%)
:arrow_down:

... and 14 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 6d72ea5...9b004b4. Read the comment docs.


Navbar v2

Add endpoint for getting all students for the navbar dropdown admin selection menu.
Example Usage:
http://localhost:3333/api/v2/students/getall

Add endpoint for isAdmin using existing helper functions
Example:

Add endpoint for profilepicture
Example:

For John, the application quest scores provided does not match the HAID dataset

For Midway There, the values are correct

For Just Started, the values are correct. There is a separate PR to showcase the 0 values and null values correctly.

For the code check failure, I am trying to not add rows that are not emails with this line:
key.endsWith("berkeley.edu").
However, the code scanner does not like this.

Profile picture implementation through localStorage, jwtDecode, and sanitization (4/24/2024) 5:05pm

4/24/2024 6:31pm get request for http://localhost:3333/api/v2/students:

http://localhost:3333/api/v2/isadmin


Object.hash on type used in static map constructor causes JS error in dart2js builds

Dart SDK version: 2.16.1 (stable) (Tue Feb 8 12:02:33 2022 +0100) on "macos_x64"

Trying to construct a static final map with a type that uses Object.hash in its hashCode implementation will throw a .js error when running in release mode.
Repro:

dart create -t web-simple object_hashcode_repro
Enter the below snippet into object_hashcode_repro/web/main.dart
Run with webdev serve --launch-in-chrome  --release (or switch the debug configuration in build.yaml to use dart2js and omit --debug)

Output:
Uncaught TypeError: $.$get$_hashSeed is not a function
    at Object_hash (object.dart:202:67)
    at Foo.get$hashCode (main.dart:12:23)
    at Object.get$hashCode$ (main.dart.js:2769:42)
    at Object.fillLiteralMap (linked_hash_map.dart:289:43)
    at Object.LinkedHashMap_LinkedHashMap$_literal (collection_patch.dart:541:12)
    at staticFields (main.dart.js:3568:19)
    at dartProgram (main.dart.js:3569:5)
    at js_helper.dart:2666:31

main.dart:
import 'dart:html';

class Foo {
  static const bar = Foo();
  const Foo();

  static final map = {
    bar: "bar",
  };

  @override
  int get hashCode => Object.hash(0, 1);

  @override
  bool operator ==(other) => other is Foo;
}

void main() {
  querySelector('#output')?.text = Foo.map[const Foo()];
}

Optional build.yaml to reproduce in debug builds too:
targets:
  $default:
    builders:
      build_web_compilers:entrypoint:
        generate_for:
        - web/**.dart
        options:
          compiler: dart2js

Fix ready for review: https://dart-review.googlesource.com/c/sdk/+/233942


Update peer dependencies

Otherwise the installing this alongside the latest version of React throws an error.
No incompatible changes on the React or Gatsby side as far as I can tell.

I have another PR ready to update to Gatsby 3 and React 17 if you would like.


Unrecognized text $field-switch-height

I'm submitting a ...

[x] bug report

Do you want to request a feature or report a bug?
a bug

What is the current behavior?

dist/vfg.css contains an unparsed variable $field-switch-height
see: https://github.com/vue-generators/vue-form-generator/blob/v2.2.2/dist/vfg.css
which means importing this stylesheet into a vue component like:
import "vue-form-generator/dist/vfg-core.css"
throws an error (in my case, I'm using vue.js via the nuxt.js framework )
NuxtServerError
Module build failed: Error: Lexical error on line 1. Unrecognized text. 100% - ($field-switch-height --------^ at Parser.parseError ...

this error also prevents the "switch" componet of a form from displaying properly, like rendered in this demo of vue-form-generator demo

What is the expected behavior?

expecting the css file vue-form-generator/dist/vfg-core.css to import without error, and for the Switch component to render like in the vue-form-generator demo

Please tell us about your environment:

Version: [2.2.2 ]
Browser: [all ]
Language: [ES6/7 | ES5]

This bug appears to be present in every release version of VFG 2.x.  The $field-switch-height variable is defined and is parsed properly in the rest of the SASS for the component, so I'm guessing the calc(100% - ($field-switch-height - 1px)); line is confusing the SASS compiler.
The switch component appears to work fine in the JSFiddle examples, using the v2.2.2 release so this bug appears to be a compile-time issue?
Looks like we can just remove the $field-switch-height variable from the calc call and replace it with the hard-coded value of 30px (this variable isn't configurable in the component, it's just defined for convenience).

@zoul0813
Out of curiosity, where is the source file for vue-form-generator/dist/vfg-core.css at or is coming from?
I'm unable to find it in this repo.

The CSS is compiled from the various style tags of the components and merged.
This bug is the fieldSwitch.vue file


Added MSVC definitions for the DISPATCH_* macros in dispatch/base.h

Added MSVC specific definitions of the DISPATCH_* macros to dispatch/base.h. This is one necessary step to make it possible to compile the Swift APIs for ibdispatch. E.g. we need a working definition of DISPATCH_NORETURN to ensure that we can successfully compile his function:
public func dispatchMain() -> Never { 	CDispatch.dispatch_main() }
because its return type is Never.
DISPATCH_* macros which are empty are empty because MSVC has no equivalent to the corresponding clang / gcc attribute.

@swift-ci please test

This is generally not going to end very well.  MSVC doesn't support the swift calling convention nor does it support Blocks.  How do you intend to deal with those?

I think this is more about allowing people to use libdispatch on windows with MSVC, which is IMO sth we should do.
building libdispatch with MSVC makes no sense, but we should support using it in a project.

(as in maybe it's not why @dplanitzer was doing it, but we should still do it anyway for the reason I just gave)

MadCoder stated one reason.
The other reason is that we need proper definitions for macros like DISPATCH_NORETURN for building libdispatch for Swift with the Swift compiler / clang-cl.
Previously compiling the Swift overlay (specifically the Swift function dispatchMain) would fail because the prototype for the dispatch_main function was missing the noreturn annotation.


[GCS FT] GCS FT misconfiguration

Search before asking

[X] I searched the issues and found no similar issues.

KubeRay Component
ray-operator
What happened + What you expected to happen
See this Slack thread for more details.
The user creates a RayService without setting the annotation ray.io/ft-enabled: "true", but they do set RAY_REDIS_ADDRESS and REDIS_PASSWORD. As a result, the RayCluster enables GCS FT and writes data to the external Redis, but KubeRay is unaware of this. KubeRay doesn't configure RAY_external_storage_namespace so that the RayCluster writes data to the key default in the Redis.
When the user triggers a zero-downtime upgrade, the new RayCluster also attempts to read metadata from the default key in Redis. Therefore, the new RayCluster will see some information from the old RayCluster.
Solution:

Explicitly disable GCS FT if KubeRay determines that the RayCluster has not enabled GCS FT.

Reproduction script
TODO
Anything else
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

/assign @rueian

👌


Icp to improve point cloud registration

Hello,
I'm using libpointmatcher_ros to improve registration of successive point clouds obtained from a LIDAR scanner. Point clouds have already been transformed to a global reference frame.
Here's an example input point cloud:

Here's an example of registration without ICP:

Here's an example of registration after ICP with libpointmatcher:

As seen above, I'm getting poor results. Please note that I'm using the default ICP mode. Am I missing something? Should I be using a custom ICP pipeline?
Please let me know if you need more information.
Thanks!
Ven

The basic pipeline is there to work with the example scans, but rarely work in general. The library is there for people to build their own registration solution, which is often custom to their applications.

Hi Francois,
Thanks for your answer. How would you recommend building a registration solution for a LIDAR scan of a simple roof? For eg,

The registration results, without ICP, already look pretty good. I have reasonably accurate pose estimates which I'd like to use to initialize ICP similar to ethzasl_icp_mapping issue#16 . I tried customizing the ICP pipeline, after going through the tutorials, file but I couldn't get it to work.
What's the best way to go about designing a custom registration pipeline for such objects? How do I select a good set of filters for my application?
Thanks!

From the screenshot, your reconstruction seems already good. I would be surprise if a quick ICP setup would make it better. For a more advance solution you would need:

a good knowledge on your sensor noise
a good knowledge on your prior noise
a good knowledge on your velocity model
a way to fuse those information with a registration solution

Libpointmatcher only provides a framework for different registration solutions, which can be used inside an application. The executable that we provide are meant to be demonstration of the capabilities of the library, not a final solution.
As for many issues opened here, we cannot support application specific questions. We too many requests and problems are very specific to the data provided.


Improve the text at the top of the home page

Received the latest home page text from the product team.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: albert-pun sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

pull by mistake


inconsistent sample config type value across repos

(cross-repo issue, filing here as the most central reference place in use)
For the sample configs, gapic-generator expects
type: com.google.api.codegen.samplegen.v1p2.SampleConfigProto

but gapic-generator-python expects
type: com.google.api.codegen.SampleConfigProto

We need to consistently use only one of these! The internal user guide has the latter specified, but DPEs have already been configuring samples with the former.
Options:

Use the latter, and have bw-compatibility code in gapic-generator to allow for samplegen.v1p2. in the type. Pro: more user-friendly: this gets us away from having the schema_version information duplicated in the type. Con: b/w compatibility code in gapic-generator until we do a sweep to update all the configs, and we can't use the python generator until we do.
Use the former, and change the user guide and generator-python to use samplegen.v1p2.. Pro: no bw compatibility code, no config sweep. Con: worse config
Switch to a more user-friendly type such as type: config/sample. This has already been requested and we were putting it off until after the upcoming launch, but given this bug we might want to do it before the launch. Pro: the most user-friendly by far. Con: backward compatibility code in both gapic-generator and gapic-generator-python, until we do a sweep of all the configs.

From the standpoint of user-friendliness and eventually-clean code, I suggest we do (3) ASAP, and in the meantime implement (2) as a stop-gap. @beccasaurus how hard/how automatable would it be to change this one field in all the submitted configs?
(If we weren't going to do (3) at some point, I would lean for (1), since that is the next-best UX, but bw-compatibility is an issue)
Once we decide on a plan, we should agree on the staging sequence so as to not break anything during the transition to the final state.

cc/ @googleapis/samplegen

I don't have any preference between the two. Switching from the former to the latter will make the monolith slightly unhappy, but should be very easy to fix.

I'm actually leaning towards (2); it's not a lot worse of a config, and it means the fewest changes all around.

Okay let's do 2. I'll close it since 2) requires no work in this generator.


Can the Negative Weights be Input?

Dear authors,
can we input the negative weights into our original and target data simultaneously in thundergbm?
With best respect,
BoanSy

BoanSy, negative target values are totally fine. Negative feature values are also acceptable.


[Addition] [Perf] [Forge and Fabric] [1.19.2-1.18.2] Smooth Chunk Save (Reopened)

Checklist

[X] I've checked that my mod suggestion hasn't already been added to one of the lists.
[X] I've checked the latest issues to make sure that this mod hasn't already been suggested.

What is your mod's name?

Preformance
What side dose your mod need to run on?
Server
Input a link to your suggested mod.
https://www.curseforge.com/minecraft/mc-mods/smooth-chunk-save
What is your reasoning for including this mod?
Saves chunks continuously over time, reducing server lag and preventing lagspikes from saving too many chunks at once.
(OPTIONAL) Give some extra information about the mod.
I already posted this addition it has been added, but sinds the remake of the github (Much better then before) it has been removed, is there a reason?

Still is on the list.

It is but the 1.18 version has been removed


Das_Geek: Watch propr.me

Das_Geek requests the watch of the watch_keyword propr\.me. See the MS search here and the Stack Exchange search here.

propr\.me has been seen in 0 true positives, 0 false positives, and 0 NAAs.

Actually does have a tp. I forgot to use Advanced Flagging when I first gave feedback

Approved by Makyen in Charcoal HQ