[config-transformer] Cannot autowire service "Migrify\ConfigTransformer\Converter\ConfigFormatConverter"

Wanting to convert https://github.com/matteosister/GitElephant/blob/ffe22770bf43e755dce7cce892275bf11b8b0041/ecs.yaml to PHP using https://github.com/symplify/config-transformer leads to an error when following the README's instructions.
Steps to reproduce:

Download repo: git clone git@github.com:matteosister/GitElephant.git (assuming git is available.)
Install dependencies: composer install (assuming PHP & composer are installed)
Follow config-transformer's instructions:

composer require symplify/config-transformer --dev
vendor/bin/config-transformer switch-format ./ecs.yaml

If you are from the future, in between steps 1 & 2, you might want to switch to the commit I am currently at using git checkout ffe22770bf43e755dce7cce892275bf11b8b0041.
Then, I get the following error:
[ERROR] Cannot autowire service "Migrify\ConfigTransformer\Converter\ConfigFormatConverter": argument
         "$yamlToPhpConverter" of method "__construct()" references class "Migrify\PhpConfigPrinter\YamlToPhpConverter"
         but no such service exists.

Hi,
this package has been recently migrated and not stable-tagged yet.
Currently you're using old code, as there is no Migrify\\ class use in the package.
Be sure to use @dev version in your composer.json:
{
    "require-dev": {
	    "symplify/config-transformer": "@dev"
    }
}

Hi, thank you for the fast response. This indeed solved the problem.
For anyone else, the following steps were necessary:

change "minimum-stability" in composer.json from "stable" to "dev"
change version of "simplify/config-transformer" to "dev-master"
run composer upgrade --with-all-dependencies -W
(do format switching, potentially with manual interventions)
change "minimum-stability" in composer.json from "dev" back to "stable", remove "simplify/config-transformer" as dependency

@TomasVotruba how is this supposed to work on older projects?

according to this ticket stable is broken
@dev does not install anything other than *
@dev with minimum-stability: dev installs quite a lot of dev packages
phar file with its own dependencies is not an option for you, see #2743
dev master requires php 7.3+
dev master also requires symfony  symfony/dependency-injection ^5.2 what about symfony lts?

am i doing something wrong or is the only way to migrate configs of older projects, to create a new symfony 5.2 project with php 7.4, copy the yaml configs there and copy the php configs back in the project?
is it really necessary to have such high version requirements (both symfony and php)?
also tried to install it globally with https://packagist.org/packages/bamarni/composer-bin-plugin (as i get conflicts otherwise) but then i still get
config-transformer switch-format config -i yaml -o php

 ! [NOTE] Processing "config/app/easy_admin/design.yaml" file

 ! [NOTE] Processing "config/app/easy_admin/entity/login_user.yaml" file

 ! [NOTE] Processing "config/app/easy_admin/entity/news.yaml" file

 ! [NOTE] Processing "config/app/easy_admin/entity/person.yaml" file

 ! [NOTE] Processing "config/app/easy_admin/entity/personGroup.yaml" file

 ! [NOTE] Processing "config/app/easy_admin/entity/publication.yaml" file

 ! [NOTE] Processing "config/app/easy_admin/entity/publicationType.yaml" file
...
...
  Expected to find class "App\Controller\NewsController" in file "myproject\src/Controller\NewsController.php" while importing services from resource "../src/*", but it was not found! Check the namesp
  ace prefix used with the resource.

should it be possible to install it globally?

In this case, there are 2 ways to solve it:

build a scoped version to avoid conflicts, as ECS has
use static reflection like PHPStan, see https://github.com/rectorphp/rector/pull/5665

please don't get me wrong, i really appreciate your effort, i always read your blog and also changed some of my coding behavior according to your suggestions. thanks for that. i think you are a very good coder. i only try to give feedback even if it is inconvenient. hope my writings don't make me lose the opportunity to meet you some day and have some nice discussions while having a drink.
as you might imagine i am quite unhappy with the current situation of this tool. if we don't look at this tool as an opensource tool where you simply share code which you made for yourself for free with the community this text would end right here with the words "thank you for your work, sadly it doesn't fit my needs but keep it up".
if we take a few steps back and look at it as a tool which should make things easier and be helpful, the UX/DX (user/developer experience) is really not good (really sorry for saying that. again please don't get me wrong).
in the end it's a tool which should convert yaml config to php comparable to json2yaml from caltechs datatools. it's like you say:
no, you can't convert this json file to yaml with a standalone version of this tool, you have to install this converter as dependency of your go project but your go project has to use the version x of go. and by the way, it also requires you to change one other dependency of your project to the version y. to overcome this you can compile it in a special way you have never done before.
you can also play this game with a hammer and no, you can't put your nail in, you need a nail version 2.0 and of course you also need wall 4.0, so you can't use the hammer in your house.
does that really fit to your libaries mantra of "simplify"?
my usecase was to slowly migrate a symfony1 (yes one) project running on php 5.6 to symfony3 to pave the way to migrate it later to symfony4.4 on php7.4. one step would have been to use php configs from the start but sadly there are not so many examples of more complex php configs out there, so your tool looks like it is the right choice but i can't even use it on my most current projects which are symfony4 on php 7.4 without quite a lot of effort.
again i fully understand if you say "i have no time for that and i don't care" as of course all the work you are doing here is for free (thanks for that), i just wanted to give you some insights on how your tool could have been used and how some decisions of you simply block it from really being used. have a look at composer which still has quite low php version requirements and works as phar.
i really hope to see all or some of the following features in your tools

standalone phar support (as phpstan, phpunit, php-cs-fixer)
lower php version support
lower symfony support (at least symfony4.4)
out of the box prefixed or static reflection (didn't have a look at what this exactly is yet. just listed it here because you wrote about it) version

Hi, thanks for sharing that.
I basically don't have time for more free work here, as I fully focus on @rectorphp and private clients.
But I'd be happy to merge pull-request, if you decided to contribute Symplify. Your idea are valid and if I would come across the same problem, I'd solve them as you suggest :+1:


chore(documentation): Document the event function

adding some documentation to the event function..

I'm closing this PR since the UI code it is modifying no longer exists in the influxdb repo and is now contained in the influxdata/ui repo - feel free to re-open it in influxdata/ui if it would still be useful to have there!


Checkpointing not possible with LR scheduler

Bug description
It seems like that there is a bug (or at least some unintended effect) when using checkpointing and and lr-scheduler in combination.
I wrote a project based on lighting and used both a checkpointing callback and a lr-scheduler with the following configuration:
# Setting up callbacks
lr_monitor = LearningRateMonitor(logging_interval='step')
early_stopping = EarlyStopping(monitor="val_loss", mode='min', verbose=True)
checkpointing = ModelCheckpoint(
    save_top_k=3,
    monitor="val_loss",
    mode="min",
    verbose=True,
    auto_insert_metric_name=True,
    save_last=True
)

trainer = nni.trace(pl.Trainer)(
    max_epochs=50,
    auto_scale_batch_size='binsearch',
    accelerator="auto",
    devices=[0] if torch.cuda.is_available() else None,
    accumulate_grad_batches=1,
    logger=tensorboard,
    log_every_n_steps=1,
    fast_dev_run= True if not torch.cuda.is_available() else False,
    callbacks=[
    lr_monitor,
    early_stopping,
    checkpointing
    ]
)

The configure optimizer is defined like this:
def configure_optimizers(self) -> Any:
    optimizer = nni.trace(torch.optim.AdamW)(self.parameters(), lr=self.learning_rate, weight_decay=1e-4)
    scheduler = {
        "scheduler": nni.trace(torch.optim.lr_scheduler.OneCycleLR)(optimizer=optimizer, max_lr=self.learning_rate, total_steps=self.trainer.estimated_stepping_batches),
         "interval": "step",
         "name": "LR"
    }

    return [optimizer], [scheduler]

Checkpointing works fine when uncommenting everything scheduler related. However as soon as I turn on the scheduler the checkpointing seems to explode (see below). Setting
import sys

sys.setrecursionlimit(10000)

does not help. I don't have any insight into the inner workings of schedulers in lightning, but it seems odd that adding a scheduler to the mix lets everything explode.
If you need anything other than the provided code snippets let me know, I'll see what I can provide.
How to reproduce the bug
No response
Error messages and logs
Epoch 0, global step 17: 'val_loss' reached 6.63835 (best 6.63835), saving model to 'logs/lightning_logs/version_21/checkpoints/epoch=0-step=17.ckpt' as top 3
Output exceeds the [size limit](command:workbench.action.openSettings?%5B%22notebook.output.textLineLimit%22%5D). Open the full output data [in a text editor](command:workbench.action.openLargeOutput?f1ce7000-9b0b-4855-8751-b8a9b3113f0f)
---------------------------------------------------------------------------
RecursionError                            Traceback (most recent call last)
File /opt/conda/envs/eml/lib/python3.10/site-packages/cloudpickle/cloudpickle_fast.py:632, in CloudPickler.dump(self, obj)
    631 try:
--> 632     return Pickler.dump(self, obj)
    633 except RuntimeError as e:

File /opt/conda/envs/eml/lib/python3.10/site-packages/cloudpickle/cloudpickle_fast.py:735, in CloudPickler.reducer_override(self, obj)
    734 if is_anyclass:
--> 735     return _class_reduce(obj)
    736 elif isinstance(obj, types.FunctionType):

File /opt/conda/envs/eml/lib/python3.10/site-packages/cloudpickle/cloudpickle_fast.py:444, in _class_reduce(obj)
    443     return _builtin_type, (_BUILTIN_TYPE_NAMES[obj],)
--> 444 elif not _should_pickle_by_reference(obj):
    445     return _dynamic_class_reduce(obj)

File /opt/conda/envs/eml/lib/python3.10/site-packages/cloudpickle/cloudpickle.py:256, in _should_pickle_by_reference(obj, name)
    255 if isinstance(obj, types.FunctionType) or issubclass(type(obj), type):
--> 256     module_and_name = _lookup_module_and_qualname(obj, name=name)
    257     if module_and_name is None:

File /opt/conda/envs/eml/lib/python3.10/site-packages/cloudpickle/cloudpickle.py:287, in _lookup_module_and_qualname(obj, name)
    285     name = getattr(obj, '__name__', None)
--> 287 module_name = _whichmodule(obj, name)
...
--> 639     raise pickle.PicklingError(msg) from e
    640 else:
    641     raise

PicklingError: Could not pickle object as excessively deep recursion required.

Environment

Current environment
#- Lightning Component (e.g. Trainer, LightningModule, LightningApp, LightningWork, LightningFlow):
#- PyTorch Lightning Version (e.g., 1.5.0): 1.9.4
#- Lightning App Version (e.g., 0.5.2):
#- PyTorch Version (e.g., 2.0): 1.13.1
#- Python version (e.g., 3.9): 3.10.9
#- OS (e.g., Linux): Linux
#- CUDA/cuDNN version: 11.7
#- GPU models and configuration: T4
#- How you installed Lightning(`conda`, `pip`, source): conda
#- Running environment of LightningApp (e.g. local, cloud): GCP

More info
No response

Hi @funnym0nk3y
The call to nni.trace is looking suspicious to me. This probably causes the optimizer or scheduler state to become pickle-unfriendly.
Could you please check whether the following works?
scheduler = nni.trace(your_scheduler)
pickle.dumps(scheduler.state_dict())

If this doesn't work, we need to check whether something can be done either on the nni side or here.


{Freeway-Bug}[Adaptive Cards- Home- Flight Itinerary]: Talkback focus move to hidden element and announce it as "departs from" using swipe right gesture.

Target Platforms
Android
SDK Version
2<IP_ADDRESS>
Application Name
Adaptive Cards
Problem Description
Test Environment
Device: S21+ 5G
Screen Reader: Talkback
AdaptiveCard Android App version: 2<IP_ADDRESS>
Repro Steps:

Turn on Talkback.
Open Adaptive Cards Visualizer Application.
Home Page will opened.
Now Navigate to 'Sample card' button and select it.
Now navigate to "choose sample" expands/collapse control and select "Flight Itinerary" list item.
Now Navigate to Visual tab and select it.
Now navigate to Flight Itinerary card using swipe gesture and observe the issue.

Actual Result:
Talkback focus move to hidden element using swipe right gesture. talkback focus move to hidden element after "Tue, May 20, 2017 12:25PM" text and announce it like "departs from"
Expected Result:
Talkback focus shouldn't move to hidden element using swipe right gesture. Talkback focus shouldn't move to hidden element after "Tue, May 20, 2017 12:25PM" text or Visually text should be appears on the card.
User Experience:
When focus order does not follow the visible reading order, the experience can create a different interaction pattern, and/or unintended content relationships for assistive technology users. On rare occasions, there is a logical reason the focus order is different from the reading order, but the meaning of the content and interactions must remain the same.
WCAG Reference:
https://www.w3.org/WAI/WCAG21/Understanding/meaningful-sequence
"Have feedback to share on Bugs ? Please help fill Trusted Tester Bug Feedback (office.com) “
Screenshots
https://user-images.githubusercontent.com/89897257/230121731-f06e5031-a35e-400b-ad63-d9c4a70904b1.mp4
Card JSON
NA

Sample Code Language
No response
Sample Code
No response

@MengliElmendorf137 : Can you pls review this.

{
  "type": "TextBlock",
  "text": "Departs From",
  "wrap": true,
  "style": "default",
  "weight": "bolder",
  "color": "light"
}

This is working as expected. There is a clash between the text color and the background color. Both are light colors. This experience exists in web, android and iOS. See screenshots below of light and dark team for Android and web.

Hi @ardlank,
Downgrading its severity from Sev 2 to Sev 3 as discussed with Team.
Also, this issue needs to be fixed as this will impact visually the user as well. Departs from and Arrives At label should be visible in Light mode as well as it is getting visible in Dark mode. Also, as a screen reader user they are getting infomration about the label, but it does not visually appear for them it will treat as hidden element as well. hence, reactivating this issue.


[Feat]: Extensibility for the environment attestor

Describe the solution you'd like:
A way to add environment variables to the default denylist, or a way to optionally only attest a specified list of environment variables.
User value:
Some environments may have sensitive information stored in environment variables which are not covered in the denylist now. Using the environment attestor will store them in recoverable plaintext in generated attestations.
Expected behavior:
Environment variables can be selectively denied or allowed to be attested.
Proposed solution:
Add a flag to decide between allowlist / denylist, and another flag to append to either list for later filtering.
Anything else you would like to add:
Testing changes required:
Add tests to make sure environment variables are correctly filtered.
Documentation changes required:
Add flags to the CLI reference and modify the Environment attestor page.

This would be very valuable to have! A list that you add would be helpful. Also a more generic approach of excluding all *_TOKEN could be helpful too.
@jkjell maybe this could have a feature label.

One thing for future conversation about this is what to do with environmental variables that modify the behavior of a process. If someone decides to compile a program with ENABLE_INSECURE_BEHAVIOR=1 but, has a DENY * config for the environment attestor, a policy could still need to be able to verify the presence or absence of that flag. This is a long way of saying we'll probably need to include the config options of the attestor in the attestation itself.

we'll probably need to include the config options of the attestor in the attestation itself.

Agree. I think this is something that all attestors should have.

Would a PR that protects vars by hidding the value be a good first step?

@joshdabosh please see the PR and the conversation that is happening there. Curious to hear your thoughts on proposed enhancements there.


⚠ Bofrost.de has degraded performance

In 9bdfe80, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1010 ms

Resolved: Bofrost.de performance has improved in 380b439.


fix for issue #1014

calculated field creation must be done after all fields referenced in formula
https://www.yammer.com/itpronetwork/#/Threads/show?threadId=555937464

You have a good reasoning here. However, this would mean that the order of the fields in which they go into the list will be changed. E.g. calculated fields will always show up in the bottom of the list, and as a result, in the bottom of the default list forms. This would affect templates already out there which have the fields in a working order in the template, as calculated fields will show up in the bottom for new deployments. We decided that that is un unwanted side effect of this PR and we will not merge this one. Nevertheless, I do think the reasoning behind this PR is valid, and we need to implement something like this in the future, however we then need to retain the field order as defined in the template too. I will make an issue to put this action on the todo list.


[Event Request] Page 498 Function SetSalesLine

Publisher needed in function SetSalesLine in the page 498:
IsHandled := FALSE;
OnSetSalesLineOnBeforeTestJobNo(var CurrentSalesLine:Record "Sales Line",var IsHandled: boolean);
IF NOT IsHandled THEN
CurrentSalesLine.TESTFIELD("Job No.",'');

We cannot add more events to reservation area now due to major rework of reservation system. Please check latest preview builds from Master to check if this is still relevant for new design.


allow users to create their own wrappers

This fixes #16718. Some layouts require the targeted input to remain siblings with other elements - this PR accommodates through the following changes:

allow the user to create their own wrapper div via the awesomplete-wrapper class
if an input bearing the awesomplete class does not have such a wrapper at runtime, Awesomplete will make one just as before, albeit with the awesomplete-wrapper class for consistency/simplicity
CSS selectors updated accordingly
docs updated as well (hopefully they work, you'll want to test)

My apologies for not writing tests for this, didn't have time to get to it.

Good idea, thanks! See comments. Sorry for the delay in replying.

Has this been abandoned? I'd be happy to incorporate Lea's comments into this.
Should I just open a new pull request as there seem to be conflicts with current code?

@TxHawks you can fork  @erquhart's repo and do your work there, then submit a pull request here.

Yeah, this PR seems to be abandoned. :(
Closing, please send a new one.

Is there a conflict or just these style pref comments?

Just these style pref comments :)

Cool. I moved to a different solution, but you're welcome to use the feature addition if someone wants to make the adaptations.


feat: add confetti from button variant

can you do the same with other buttons that require animations around button or should i create a pull req for that

ill take care of it @gursheyss @prakashsp23
thanks for adding this btw i wanted to add this too

ty for this code @gursheyss
refactored it a bit and merged a new component called <ConfettiButton /> in in latest commit #126
will close this for now


Update CodeceptJS to version 3.2.2

During UI Hackathon I worked on e2e tests, one of the things done was to update CodeceptJS to the latest version and Playwright to the version used by this new version of CodeceptJS.
The only change required (breaking change introduced in 3.2.0) was to update the timeout in the config file. Now the global timeout property is in seconds (not in ms) and apparently this property was not working properly before for some tests. Had to use 100 200 seconds here as 10 seconds were not enough for some tests. (We should keep an eye on this to update this value if needed)
https://codecept.io/advanced/#timeout
https://codecept.io/changelog/#_3-2-0
https://github.com/Percona-Lab/pmm-submodules/pull/2235

As per the report https://pmm.cd.percona.com/job/pmm2-ui-tests/11291/allure/#suites/7cd6353420db44afc4108c7e94fbf4a1/4e6fddb5200eaa82/ Backup tests failed due to reaching the 100s timeout so I'm doubling it.

Mainly tests related to IA seem to be failing now: https://pmm.cd.percona.com/job/pmm2-ui-tests/11298/allure/#suites/01c7aebf2d5a4e8294c1e113379120cd/ec3bfc02e8c60ad2/
Seems unrelated to this PR though, need to check those. But the problems with the timeout were fixed

@tiagomotasantos I've tested a few times. Looks like this one is failing on your branch consistently https://pmm.cd.percona.com/blue/organizations/jenkins/pmm2-ui-tests/detail/pmm2-ui-tests/11366/tests

@yurkovychv the problem here is with the logic of the test. We are waiting for "MySQL exporter" agent and there's no MySQL exporter in our test container neither by default in PMM.
I see the following options:

Try with Postgres exporter or Node exporter since it's by default in pmm server;
Add MySQL exporter to test container (might still fail locally);
Remove the test

I prefer the first solution. What do you suggest? Maybe you know why this was working before and not now or have a better solution

@yurkovychv solved it in a different way: by using add instance API to add MySQL instance at the beginning of the test. Now every test passes!

@tiagomotasantos I have looked, seems good to me, just trying to understand why nightly failed, I have asked @vyarosh to help look into it.

@tiagomotasantos , @puneet0191  the issue is the following:
https://github.com/percona/pmm-ui-tests/blob/codecept-3.2.2/tests/dashboards/pages/searchDashboardsModal.js#L118 this method is called with undefined argument in test here: https://github.com/percona/pmm-ui-tests/blob/codecept-3.2.2/tests/dashboards/verifySearchDashboards_test.js#L37
I'm tying to findout why

Fixed. The access model to the 'current' object has been changed. Adjusted test accordingly.


[PROPOSAL] Day 2 Operations - In-place Upgrades

Rancher currently supports doing in-place upgrades (i.e. upgrading the version of kubernetes of a node without creating a new node).
CAPI currently assumes that you can create a new node.
We need to find a way to support in-place upgrades.

The functionality will likely come from upstream.

From @alexander-demicev: https://hackmd.io/ZO8fqUOQQSuR1MHp1-43wQ

More up-to-date link to draft proposal: https://hackmd.io/Wv_u2xXJQsaj4wWFQ3PqCQ?view


read in pdfs

figure out how we can deal with pdf resume uploads

no time or reason to do this anymore


Validation of a FHIR resource

I'm trying to validate a JSON string respect a FHIR resource, specifically for a FHIR Questionnaire resource (https://www.hl7.org/fhir/questionnaire.html).
Attachments to the issue you can find:

used swagger definition (obtained with tool fhir-swagger with some minor changes);
JSON string to validate respect given swagger (it is an official FHIR example: https://www.hl7.org/fhir/questionnaire-example-f201-lifelines.json)

Runing this script:
var Validator = require('swagger-model-validator'); var swagger = require('./fhir_swagger.json'); var validator = new Validator(swagger); var objToValidate = require('./Questionnaire-example-f201-lifelines.json'); var validation = swagger.validateModel("Questionnaire", objToValidate, true, true); console.log(validation);
I obtain this output:
{ valid: false,   errorCount: 1,   errors: [ [Error: contained is a required field] ],   GetErrorMessages: [Function],   GetFormattedErrors: [Function] }
I don't understand this error because it seems to me that the "contained" field is not mandatory (in line 17209 of swagger definition you can see the definition of "contained" field provided for the Questionnaire object). I've also tried to delete at all the definition of "contained" field (lines 17209-17290) but I have the same error, I' think I'm using the swagger-model-validator tool in a wrong way, can you help me please?
Marco
fhir_swagger.txt
Questionnaire-example-f201-lifelines.txt

Line 17456 of the swagger definition seems to show that contained is a required field.  You would have to remove it from the required array (starting on 17452) for it to be non-required.  Removing it as a property will not remove it from the required list.

It looks like the definition does not match the example.  Removing 'contained' from the required array (line 17456) should make the example match the definition properly.

You are right. Thanks.


Add support for FOSSA

With this commit we add support in Rally to run license checks on third-party
dependencies with a separate tool called fossa. Note that this work is only a
preparation on the Rally side. This is intended to be run in CI and needs to be
supplemented by a corresponding CI job.

I am going to spin up a test machine to ensure this works properly
@elasticmachine run tests

Not sure how I could have altered the tests by being on the machine but Im going to rerun them just in case on a pristine machine that I do not get on.
@elasticmachine run tests

Thanks for the review!

This looks good. It complained about an environment variable but I dont think that needs to be solved in this PR.

I checked the logs from the CI run as well and I think this is because I've created this PR before #1105 has been merged to master. I've merged master now and retriggered a CI run.

My only question is ive seen some projects make the project field the entire github URL, whereas some do not. I dont know enought about fossa to know what is correct, and I assume you do :)

The Github URL is autopopulated when you create a fossa configuration on the command line (with fossa init) and this property is used in the fossa UI to identify the project (see also their docs). I've explicitly changed this so it shows the nicer name "Rally" instead of the somewhat clunky URL. I hope that answers your question.


Failed to run macos

Environment

OS: macos
Erlang/OTP: 20
EMQ: v2.3.11

Description
I started ./emqttd console but it failes:

2018-08-22 14:38:49 Unable to load crypto library. Failed with error:~n"~p, ~s"~nOpenSSL might not be installed on this system.~n
	load_failed
	"Failed to load NIF library: 'dlopen(/Users/.../Downloads/emqttd/lib/crypto-4.2.2/priv/lib/crypto.so, 2): Library not loaded: /usr/local/opt/openssl/lib/libcrypto.1.0.0.dylib\n  Referenced from: /Users/.../Downloads/emqttd/lib/crypto-4.2.2/priv/lib/crypto.so\n  Reason: image not found'"
2018-08-22 14:38:49 crash_report
    initial_call: {supervisor,kernel,['Argument__1']}
    pid: <0.1110.0>
    registered_name: []
    error_info: {exit,{on_load_function_failed,crypto},[{init,run_on_load_handlers,0,[]},{kernel,init,1,[{file,"kernel.erl"},{line,217}]},{supervisor,init,1,[{file,"supervisor.erl"},{line,294}]},{gen_server,init_it,2,[{file,"gen_server.erl"},{line,365}]},{gen_server,init_it,6,[{file,"gen_server.erl"},{line,333}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,247}]}]}
    ancestors: [kernel_sup,<0.1085.0>]
    message_queue_len: 0
    messages: []
    links: [<0.1086.0>]
    dictionary: []
    trap_exit: true
    status: running
    heap_size: 610
    stack_size: 27
    reductions: 235
2018-08-22 14:38:49 supervisor_report
    supervisor: {local,kernel_sup}
    errorContext: start_error
    reason: {on_load_function_failed,crypto}
    offender: [{pid,undefined},{id,kernel_safe_sup},{mfargs,{supervisor,start_link,[{local,kernel_safe_sup},kernel,safe]}},{restart_type,permanent},{shutdown,infinity},{child_type,supervisor}]
2018-08-22 14:38:50 crash_report
    initial_call: {application_master,init,['Argument__1','Argument__2','Argument__3','Argument__4']}
    pid: <0.1084.0>
    registered_name: []
    error_info: {exit,{{shutdown,{failed_to_start_child,kernel_safe_sup,{on_load_function_failed,crypto}}},{kernel,start,[normal,[]]}},[{application_master,init,4,[{file,"application_master.erl"},{line,134}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,247}]}]}
    ancestors: [<0.1083.0>]
    message_queue_len: 1
    messages: [{'EXIT',<0.1085.0>,normal}]
    links: [<0.1083.0>,<0.1082.0>]
    dictionary: []
    trap_exit: true
    status: running
    heap_size: 376
    stack_size: 27
    reductions: 213
2018-08-22 14:38:50 std_info
    application: kernel
    exited: {{shutdown,{failed_to_start_child,kernel_safe_sup,{on_load_function_failed,crypto}}},{kernel,start,[normal,[]]}}
    type: permanent
{"Kernel pid terminated",application_controller,"{application_start_failure,kernel,{{shutdown,{failed_to_start_child,kernel_safe_sup,{on_load_function_failed,crypto}}},{kernel,start,[normal,[]]}}}"}
Kernel pid terminated (application_controller) ({application_start_failure,kernel,{{shutdown,{failed_to_start_child,kernel_safe_sup,{on_load_function_failed,crypto}}},{kernel,start,[normal,[]]}}})

Crash dump is being written to: log/crash.dump...done

i have installed openssl but it does not work yet

Did you install the erlang OTP from source? Then check the output of ./configure, make sure the openssl libs can be found by the building process.

no i used compiled  version emqttd-macosx-v2.3.11.zip, my macos version is 10.13.6 and http://emqtt.io/static/brokers/emqttd-macosx10.13-v2.3.11.zip  version for 10.13 is not found

Could you check if the path /usr/local/opt/openssl/ exits on your Mac?
Install the openssl and create links to /usr/local/opt/openssl/ if it does not exist. Hope it works.

i link openssl to path
$ ls /usr/local/opt/openssl
aes.h		buffer.h	conf_api.h	dtls1.h		err.h		lhash.h		ocsp.h		pkcs7.h		safestack.h	ssl23.h		ui.h
asn1.h		camellia.h	crypto.h	e_os2.h		evp.h		md4.h		opensslconf.h	pqueue.h	seed.h		ssl3.h		ui_compat.h
asn1_mac.h	cast.h		des.h		ebcdic.h	hmac.h		md5.h		opensslv.h	rand.h		sha.h		stack.h		whrlpool.h
asn1t.h		cmac.h		des_old.h	ec.h		idea.h		mdc2.h		ossl_typ.h	rc2.h		srp.h		symhacks.h	x509.h
bio.h		cms.h		dh.h		ecdh.h		in		modes.h		pem.h		rc4.h		srtp.h		tls1.h		x509_vfy.h
blowfish.h	comp.h		dsa.h		ecdsa.h		krb5_asn.h	obj_mac.h	pem2.h		ripemd.h	ssl.h		ts.h		x509v3.h
bn.h		conf.h		dso.h		engine.h	kssl.h		objects.h	pkcs12.h	rsa.h		ssl2.h		txt_db.h

sadly it did not worked!

➜  ls /usr/local/opt/openssl/
CHANGES              LICENSE              README               include              share
INSTALL_RECEIPT.json NEWS                 bin                  lib

You have installed openssl library on your mac os, but it doesn't mean that you have configured openssl library correctly in your erlang runtime.
Try to install erlang OTP 20 by homebrew.
brew install erlang@20
brew unlink erlang
brew link erlang@20 --force

thanks
i re link openssl
sudo ln -s /Users/../homebrew/Cellar/openssl/1.0.2p/ /usr/local/opt/openssl
$ ls
CHANGES			LICENSE			README			include			share

it worked!


python312Packages.aiolifx: 1.1.1 -> 1.1.2

Changelog: https://github.com/aiolifx/aiolifx/releases/tag/1.1.2

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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/)
25.05 Release Notes (or backporting 24.11 and 25.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

[ ] Fits CONTRIBUTING.md.

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

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 365203

x86_64-linux

:white_check_mark: 17 packages built:

home-assistant-component-tests.lifx
python311Packages.aiolifx
python311Packages.aiolifx-connection
python311Packages.aiolifx-connection.dist
python311Packages.aiolifx-effects
python311Packages.aiolifx-effects.dist
python311Packages.aiolifx-themes
python311Packages.aiolifx-themes.dist
python311Packages.aiolifx.dist
python312Packages.aiolifx
python312Packages.aiolifx-connection
python312Packages.aiolifx-connection.dist
python312Packages.aiolifx-effects
python312Packages.aiolifx-effects.dist
python312Packages.aiolifx-themes
python312Packages.aiolifx-themes.dist
python312Packages.aiolifx.dist


macOS 11.6 latest builds crash on startup

VS Code Version: 1.57.0-insider
OS Version: Mac OS X 10.11.6

Steps to Reproduce:

Download and unpack Visual Studio Code
Run Visual Studio Code

Insiders build too.

Does this issue occur when all extensions are disabled?: Yes/No

Process:               Electron [5997]
Path:                  /Users/USER/Downloads/Visual Studio Code - Insiders.app/Contents/MacOS/Electron
Identifier:            com.microsoft.VSCodeInsiders
Version:               1.57.0-insider (1.57.0-insider)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Electron [5997]
User ID:               501
Date/Time:             2021-05-12 16:48:51.090 +0100
OS Version:            Mac OS X 10.11.6 (15G22010)
Report Version:        11
Anonymous UUID:        638E88C7-B579-E5B5-CC91-39F0159388D3
Sleep/Wake UUID:       73BEA146-E287-481B-9F45-4B0F7EBF38DD
Time Awake Since Boot: 30000 seconds
Time Since Wake:       29000 seconds
System Integrity Protection: enabled
Crashed Thread:        0  CrBrowserMain  Dispatch queue: com.apple.main-thread
Exception Type:        EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes:       0x0000000000000001, 0x0000000000000000
Thread 0 Crashed:: CrBrowserMain  Dispatch queue: com.apple.main-thread
0   spdlog.node                   	0x00000001115e24c3 std::__1::unordered_map<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator >, std::__1::shared_ptrspdlog::logger, std::__1::hash<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > >, std::__1::equal_to<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > >,

It's pretty much the same Electron based spdlog.node logging crash reason as under OSX 10.11.6 (El Capitan) too.
See also this issue here.

Merging to https://github.com/microsoft/vscode/issues/123374


Optionally allow lenient handling of tag versions for semver

We use git describe style versioning, which is unfortunately close but nominally incompatible with semver. I propose adding a lenient option on the resource definition to enable parsing these versions.
The underlying semver library in use by the source-controller, Masterminds/semver, will safely and correctly interpret this style of versioning when using the semver.NewVersion constructor. source-controller uses the central flux pkg version, which in turn calls semver.StrictNewVersion.
Since this is my first contribution and I'm touching an API resource, I'm submitting a pretty sparse PR for feedback before enriching with tests. Existing tests cover that there are no regressions from this strictly additive change.

Ah, sorry, it seems like I was mistaken about the support for git-describe style versions from the Masterminds/semver/v3 library. On further testing it looks like support was transient at some point but no longer.


Impact of redundant features

In my data, I have a few features which are constant in the training data and thus, should be redundant. Yet, depending on whether I include them when using LightGBM or not, impacts the results, usually with better results on those models that exclude them. Sometimes the differences are only extremely minor, but I have also seen some larger impacts.
I am struggling in understanding how this can happen. From my understanding the trees should never split for constant features anyways.
Code for exclusing features and LightGBM model currently look like:
import lightgbm as lgb
from sklearn.feature_selection import VarianceThreshold
pipeline = Pipeline(memory=None,
        steps=[
            ('variance_threshold', VarianceThreshold(0.0)),
            ('clf', lgb.LGBMRegressor(n_estimators=100))
        ])

@psinger yeah, the constant features should be ignored by lightgbm.
Did you use the feature_fraction(sub_feature) ?
If yes, that is possible, as LightGBM use original feature index to sample features.

ping @psinger

@psinger Don't have the data at hand any longer unfortunately, but I did not use feature sampling. But issue can be closed, I will re-ping if I identify issue again.

@psinger Thanks for letting us know! Of course, feel free to reopen in case it'll happen again.


[WIP] Import genome browser static files from a github repository

Try importing browser static files from a github repo using npm.
(as an alternative approach to https://github.com/Ensembl/ensembl-client/pull/180)
Current status: works for development.
TODO:

Update production build

The production build needs updating so that:

builds that get pushed are deployed to git and have their hashes updated.
builds that don't get pushed are copied into node_modules.
some kind of git hook to make sure that we never forget to do the former.

There's already approximately difference between pushed and non-pushed builds (deploy and deploy-check).
Though sometimes it's useful to do deploy builds in non-push circumstances (when you expect there to be a bug or performance hit from the debug code), it's never right to do the opposite.
Probably there needs to be a third category, "deploy-strip" which does a to-push build but deploys into node_modules.
deploy-check: [has debug symbols, unoptimised, console messages] [to node_modules]
deploy-strip: [no debug symbols, optimised, no console messages] [to node_modules]
deploy: [no debug symbols, optimised, no console messages] [to github]
Probably we can do the push to github in the build script and use the git prepush hook (via husky) to verify its presence via http. Passing the correct hash to use around this system might be fun, but we'll see.

#197 has now unblocked this PR.

OK, well that rebase messed up this PR. Still working out how to fix it.

Sorry, our dev got broken when I updated the packages. I am trying to sort it out now; hopefully nearly there...

Fixed tests and updated production build from the React side.

Deploy builds fixed. Issue with jest I'll look at later. May be temporary while in broken state. Should fix non-deploy builds first.

Pushed commits that got overwritten during the last force-push. They fix the jest error and also add instructions for copying the wasm file to dist/static folder during production build.

Current status:

[X] deploy builds
[X] non-deploy builds
[ ] prune script
[ ] switch repo into ensembl-org

Pruning script finished. Ready to go.

@ens-ds23 From the npm-related perspective, this looks great. Can't approve this PR, because I created it, but whenever you are happy with pruning scripts, feel free to squash-and-merge!


[Don't Merge] Question on perf data ETA for new SKUs

Hi team. Any ETA when you want to publish the performance data for the new SKUs (D*V5)? I got several customers asking for it already :)
Thanks!

@alexmpmenezes : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hi @alexmpmenezes - This pull request can't be merged into the repository. Would you open an issue or send email to the article author at their Microsoft alias? Thanks! We'll close this pull request.
@mimckitt

We are working on those numbers. No ETA as of yet.

CC @joelpelley


Service autodiscovery

Automatically register all service instances, so that shouldn't be explicitly listed

Closed in favour of #72


Should default to \r\n on windows

When running on a windows box this should default to \r\n as a delimiter. This works pretty poorly ith the stdin input without this.

I wonder if we can specify this so that it's the equivalent of \r?\n. I can't think of anyone that actually wants the \r in there, whether they're using a file or stdin.

One first improvment would be to use java System.lineSeparator() to set the default, feasible?

Maybe we make it a setting, maybe called "line_terminator" and have valid settings of "windows", "mac", "unix", or "network" ? (windows and network are identical, \r\n; mac is \r, unix is \n)

But Mac doesn't do \r anymore. It does \n now. But, it is a good point.
As long as it's settable, then it really doesn't make a huge difference to me, but I think the default should really be "either of (\n|\r\n)" or  "any of (\r|\n|\r\n)". There is an undocumented delimiter field that serves this purpose, but I think it requires it to be the exact delimiter rather than the match:
https://github.com/logstash-plugins/logstash-codec-line/blob/ceee8659e7bac14911a39d9662494632a4e25504/lib/logstash/codecs/line.rb#L31

@jordansissel this plugin already has a 'delimiter' setting. I'm really curious if it works correctly with escaped characters in the logstash config however.

Also, the only reason delimiter is undocumented is that our doc generator hasn't run recently on this.

I think @wiibaa makes a great point, but I agree that we should look for either \r\n or \n. No one wants the \r.

Some Mac apps still use \r (FileMaker) even on OS X. :/
On Monday, June 20, 2016, Chris Earle<EMAIL_ADDRESS>wrote:

But Mac doesn't do \r anymore. It does \n now. But, it is a good point.
As long as it's settable, then it really doesn't make a huge difference to
me, but I think the default should really be "either of (\n|\r\n)" or
"any of (\r|\n|\r\n)". There is an undocumented delimiter field that
serves this purpose, but I think it requires it to be the exact delimiter
rather than the match:
https://github.com/logstash-plugins/logstash-codec-line/blob/ceee8659e7bac14911a39d9662494632a4e25504/lib/logstash/codecs/line.rb#L31
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/logstash-plugins/logstash-codec-line/issues/10#issuecomment-227245170,
or mute the thread
https://github.com/notifications/unsubscribe/AAIC6o0ZGpvvhE9b57eM4DsrCCLWbzalks5qNurtgaJpZM4I6AdE
.


MedT Direct: handle case where bolus event is more than 5 seconds after bolus wizard

Currently we expect a bolus record to be within 5 seconds of its corresponding bolus wizard record to match them (usually they have the same timestamp, but not always). During alpha testing we discovered a bolus record that came 13 seconds (!) after the bolus wizard record. This PR changes the window to 30 seconds to make sure we can match these records.

  Medtronic Alpha Test - Issue Resolution Card [uploader]

Does the timing have to do with the size of the bolus? For example, would the bolus record for an 8U bolus take longer to appear after the BWZ record than a 2U bolus, for example?
What about a square wave?

I thought that may be the case too. However, most of the time the bolus wizard record timestamp matches the corresponding bolus record timestamp exactly, and since it takes at least some seconds before a bolus is delivered, I would expect there to always be a non-zero difference if it waited for the bolus to complete first.


Only one photo is kept in gallery after toggling "Is public" off and back on.

Hello. I have a Photologue gallery with 6 photos, initially correctly displayed. In the admin page "Change gallery", if I toggle "Is public" off, save the settings, and later toggle "Is public" back on, only one of the 6 photos is ticked in the Photos section. If I try to manually re-select the other 5 photos and save, it will have no effect, only one photo will be displayed in the gallery.
Is this a bug? Can someone reproduce it? Thanks.

Hi,
I can't seem to reproduce this bug.
Could you provide more details please: Django version, Photologue version, Python version, ...

Hi. Sorry, should have done that first:
Working in a Vagrant VM and a virtualenv local environment. Server is Apache 2.4.
python —version
Python 3.4.3
pip show django
Metadata-Version: 2.0
Name: Django
Version: 1.8.7
pip show django-cms
Metadata-Version: 2.0
Name: django-cms   [Note: does not yet support django 2.9]
Version: 3.2.0
pip show django-photologue
Metadata-Version: 2.0
Name: django-photologue
Version: 3.4.1
sudo pip3 show virtualenv
Name: virtualenv
Version: 13.1.2
lsb_release -a
Distributor ID:	Ubuntu
Description:	Ubuntu 14.04.3 LTS
Release:	14.04
Codename:	trusty

On Jan 8, 2016, at 4:54 AM, Richard Barran<EMAIL_ADDRESS>wrote:
Hi,
I can't seem to reproduce this bug.
Could you provide more details please: Django version, Photologue version, Python version, ...
—
Reply to this email directly or view it on GitHub https://github.com/jdriscoll/django-photologue/issues/150#issuecomment-169802181.

Hi,
Thanks for the extra information; even armed with that, I still cannot reproduce this bug. There must be something specific to your environment that is causing the issue.
If it's a problem with Photologue, then presumably someone else will encounter this bug; so I will leave this ticket open for a while, to see if more information becomes available.

Understood and thank you for looking into this. I will investigate further at my end to see whether I can find out which peculiarity in my own settings may be causing the problem, which I can still easily reproduce for the moment. I will let you know if I find out.

On Jan 10, 2016, at 1:19 AM, Richard Barran<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
Hi,
Thanks for the extra information; even armed with that, I still cannot reproduce this bug. There must be something specific to your environment that is causing the issue.
If it's a problem with Photologue, then presumably someone else will encounter this bug; so I will leave this ticket open for a while, to see if more information becomes available.
—
Reply to this email directly or view it on GitHub https://github.com/jdriscoll/django-photologue/issues/150#issuecomment-170261049.

I have the same issue. If I select multiple images from gallery and view my site only one image is shown.
when I go back to gallery only one image is shown as selected. I am using django 1.10 and apache.

Im having the same issue where if I select multiple photos to add to my gallery and hit save only the first selected photo gets added to that gallery. At first when I was setting up photologue I was following the steps in the documentation. I created my own folder called "photoGallery" and inside there it had a models.py file which looked like this
https://pastebin.com/AZ2ibQwP
and it also had an admin.py file which looked like this.
https://pastebin.com/uzQHrBPc
In the end I wasnt able to figure out how to view the gallery on the front end of my website so I just ended up using all the default files from the photologue folder instead of the custom folder that I made. On my site i can view any galleries I make but each gallery only saves one picture.
Here is a link to my websites gallery page
http://www.vacationcondos.vegas/photologue/gallery/
python --version
2.7.6
pip show django
name: django
version: 1.11.3
pip show django-photologue
name: django-photologue
Version: 3.7
lsb_release -a
Distributor ID: Ubuntu
Description Ubuntu 14.04.4 LTS
Release 14.04
Codename trusty

Hi @Tedgar20 apologies for the slow response. What version of django-sortedm2m is installed on your system?

@richardbarran thanks for responding back. How would I go about checking that?

@Tedgar20 the command pip freeze will list all 3rd party packages installed - there will be a line with django-sortedm2m and its version number.

@richardbarran django-sortedm2m==1.4.0

Hi again - I thought that maybe the issue was caused by an old version of django-sortedm2m - but 1.4.0 is a recent release. So that's not the issue.
So I'm still confused by this issue, as I cannot reproduce it. From your description, I'm wondering if the Javascript in the admin page is broken, and that when you select multiple photos and hit 'save', only the first photo's information is sent back to the server. But this is just speculation by me.

Yeah maybe thats it. Thanks anyway for responding though I really appreciate it.

I figured out what was causing the problem. The static js and css files belonging to sortedm2m were getting a 404 on the production website.
To identify if this is the issue with you, check the Networks tab of the developer console in your browser to see if all files are loading with code 200.
When I checked on the localhost website, I found all those files being fetched normally (200 OK).

To solve this I copied the js and css files belonging to sortedm2m into
project_root_directory/static/sortedm2m/
Running a python manage.py collectstatic after this solved my problem.
@richardbarran I think the sortedm2m static files should be added inside this directory-
https://github.com/jdriscoll/django-photologue/tree/master/example_project/example_project/static
Not sure if it's the right practice.
If anyone faces the same issue, please try the above steps and confirm if the solution works for you.

I can confirm @nihal111 solution.

@richardbarran Confirming that sortedm2m was in fact inside INSTALLED_APPS in my settings.py file.

Yes, I can confirm @richardbarran

Thanks both for the input.
If anyone has this issue again - could you please paste a screenshot of the Networks tab of the developer console in your browser. I'd be very interested in seeing which files are not being loaded.


SPIKE: State Public Health Dept Notification When New SimpleReport User Has Signed

Description
As a state public health department, I would like to be notified when a new user has signed up for SimpleReport and before they start reporting results so I can make the necessary changes in the systems to accommodate the new reporter.
Proposed solution
Will let the team brainstorm potential options. Some might include:

For states that need notification (e.g. AZ, CA, or others) - delay the ability to start using SimpleReport for 24 - 48 hours and auto-generate an email to the state PHD.
Pop a message to the user with please contact your state public health department at<EMAIL_ADDRESS>to let them know that you are using SimpleReport.
Probably many, many more since you are more creative than me.

Additional context
This request has been requested by more than one state and hence the weekly emails we send with new facilities, including SimpleReport.

@LGFranklin since I can't assign this to anyone

We can assign at cross-team sorting

Waiting for feedback from states. Current report is probably fine based on what we need.

@LGFranklin have there been any additional requests from states around this report, or are we ok to close this issue?


Add function arrayFlatten

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en
For changelog. Remove if this is non-significant change.
Category (leave one):

New Feature

Short description (up to few sentences):
Add a new function which transforms a 2D array to an 1D array.
Detailed description (optional):

Sorry, isn't it what you need?: https://github.com/yandex/ClickHouse/pull/4555

What you can do?

add arrayFlatten as a synonim to flatten;
add documentation (probably missing documentation is the issue);
add your tests just in case;
compare implementation;
compare performance;

Do you want to make something related to this pull request?


Upgrade Storybook to v7

We're on v6.5.16 and it's nudging us to upgrade to v7 for some neat new features.

Task

[x] Update npm dependencies using yarn.
[x] Update Story format to CSF3.0

[x] Others complete
[x] TableComplex
[x] TableSimple
[x] TextInput

[ ] Address errors blocking Netlify build/deploy

[x] Could not find a declaration file for module '@cfpb/cfpb-expandables/src/Expandable'
[x] [Page.tsx] Expected 1 arguments, but got 0
[x] Cannot find type definition file for 'vite-plugin-pwa/client'
[x] yarn build-storybook errors about stuff that cannot be named...?

[ ] Verify nothing is broken.
[ ] Optional: Check out the new features and let us know if anything is particularly exciting.

Last remaining error blocking Netlify deployments


For the new "format 2", focusing on "4 pages + minicalendar" layout, create and implement the respected new logic in the "open_composite_png.js", store it separately from the "format 1"-specific files

Implemented the "layout2" logic for "open_composite_png.js"
Placed it into the "layout2"-specific directory.


hw/drivers/bme280: Fix writes to I2C

I2C writes when driver was enabled clear MSB of register address.
This prevented any write to control registers.
Now registers MSB is cleared on write only for SPI.

That fixes my problem with bme280 and i2c.


sortable request

@aristath I use sortable control and found it super easy to use for displaying social link. But the problem is that there is no text field for the link. Do you have any plan to add text type to sortable or I'd better use repeater control ?
Thanks

@robbisy Repeater control won't be handy in this case. I second the request for text field in sortable control.

Added as a feature request.

We have done this in our Premium Add-On for Page Builder Framework by conditionally displaying an input field, if certain fields in the sortable field are turned on. It's additional work but gets the job done.


Navigate to procedure definition opens schema definition

SQL Operations Studio Version: sqlops 0.23.6 (8a3011756318a2ded1e6e84332230a2b2bf9c544, 2017-11-06T21:51:43.232Z)
OS Version: Windows_NT x64 10.0.16299

Steps to Reproduce:

type 'exec schema_name.procedure_name'
Set typing cursor on procedure_name
Press F12

Expected:
4. Definition of procedure is opened in new query window
Actual:
4. Definition of schema is opened in new query window

@llali @abist another candidate for investigation in the general scripting area.

Fixed in sqltoolservice v1.2.0-alpha.39. It will be in the next release


Add support for Astra

Nice!
Two questions…

Can this be here instead ? https://github.com/spring-projects/spring-ai/tree/main/spring-ai-spring-boot-autoconfigure/src/main/java/org/springframework/ai/autoconfigure/vectorstore/cassandra
1a. Furthermore, could it be part of spring-boot-autoconfigure ?
How to make it optional, e.g. datastax.astra.enabled=true ?

this isn't intended to be closed…


Dart does not throw compile time error when wrong type is assigned to a variable using the if null operator (??)

Dart VM version: 2.3.0-dev.0.5.flutter-a1668566e5 (Tue Apr 30 20:35:41 2019 +0200) on "macos_x64"
Dart does not throw compile time error when wrong type is assigned to a variable if you use the "if null" operator. Following example compiles without error and then throws a runtime error:
class ExampleClass {}

void main() {
  ExampleClass example = 'string' ?? ExampleClass();
}

I believe this is a classical example of the way our unification interacts with implicit downcasts.
The static type of 'string' ?? ExampleClass() is the least supertype of String and ExampleType, which is Object. Since Object is a supertype of ExampleClass, the assignment is allowed statically as an implicit downcast, and it fails at run-time.
With non-nullable types, the 'string' ?? ... will likely become either a warning or an error (the expression cannot be null, so the ?? is irrelevant), and when implicit downcasts are disallowed, that particular error will be caught as well.
Until then, the analyzer option implicit-casts can warn you about all downcasts, which will catch cases like this ... and a lot of other downcasts which are probably perfectly fine.

I see, thank you for the explanation.

Closing since NNBD will also disable implicit casts and there are no specific actions to take on this issue.
https://github.com/dart-lang/language/issues/192


Error buildAgentGraph - Invalid update for channel start:supervisor. Values: start,start

After deploying the Flowise in GCP cluster I am encountering below error for sequential agents
Error buildAgentGraph - Invalid update for channel start:supervisor. Values: start,start
Error: EphemeralValue can only receive one value per step.

Got the same error as well.

Flowise stdout output:
2024-08-27 08:15:50 [INFO]: [server]: Chatflow 6db3b82b-2cad-49d9-8196-3c305251dc2d_5adaf888-1d10-4aaa-bbdd-a3eeeec2831d added into ChatflowPool
2024-08-27 08:15:50 [ERROR]: [server]: Error: Invalid update for channel start:frontline_support. Values: __start__,__start__
Error: EphemeralValue can only receive one value per step.
Error: Invalid update for channel start:frontline_support. Values: __start__,__start__
Error: EphemeralValue can only receive one value per step.
    at buildAgentGraph (/usr/local/lib/node_modules/flowise/dist/utils/buildAgentGraph.js:339:19)
    at async utilBuildAgentResponse (/usr/local/lib/node_modules/flowise/dist/utils/buildChatflow.js:363:31)
    at async utilBuildChatflow (/usr/local/lib/node_modules/flowise/dist/utils/buildChatflow.js:159:20)
    at async createInternalPrediction (/usr/local/lib/node_modules/flowise/dist/controllers/internal-predictions/index.js:7:29)

To reproduce:
1 . Clone "Support Routing System" marketplace agentlow

2 . Choose OpenAI creds here

3 . Remove these edges

4 . Start chat , type anything as a first message

Error was reproduced for v2.0.5
For 2.0.4, it works OK

I have same problem reproduced to v2.0.5

hmm im not able to replicate the issue, have my Docker instance v2.0.6 deployed on Railway:


Generalize to multiple buckets

The set of buckets is static and ordered, which simplifies reasoning about the 'Peers' values we're working with, as well as integration in the settlement layer.

I've given this some more thought and I think I see what you mean now; I don't think it's necessarily worse than the situation before we introduced multiple buckets, but it's true that we can now do better.
Consider the situation as it was before we had multiple buckets. We have two threads racing: thread A removes node n, and thread B adds node n and enqueues a message to n. The interleaving that you're worried about it
A                    B
remove n,
compute `removed`
                     reintroduce n,
                     enqueue message to n
dequeue all
messages to n

where we end up in a situation with n registered, but a message to n lost. Admittedly, this isn't a great scenario (since it violates linearizability of updatePeersBucket), but my point above was: if we have two threads racing, one removing n and one reintroducing n, we already have the following  interleaving also
                    introduce n (no-op: it's already there),
                    enqueue message to n
remove n,
dequeue all
messages to n

This is a perfectly linearizable interleaving (in that sense one that would still be possible if updatePeersBucket was atomic) I'm not sure that the outcome is so much better from the point of view of the next layer up.
However, now that we have multiple buckets, the above linearizable interleaving is no longer possible: when B introduces n into its bucket, A can then remove n from it's own bucket all it wants, n will still be considered to be part of the total set of all peers and hence we will not dequeue any messages.
So the property we would like to have, I think, and can now guarantee, is that
Invariant: if thread T adds node n to its peers bucket, and then enqueues a message to it, that message should not be deleted.
We can guarantee this provided that each bucket is updated by a single thread only; and indeed, the easiest way to do that is to have a single MVar qBuckets, just like you suggested (I deserve an "I told you so" :-) ).


Add ibm_db_sa TimeStamp and Datatime Grain Spec.

Add ibm_db_sa TimeStamp and Datatime Grain Spec. for db2 iseries

Thanks for the patch! Could you please fix the codeclimate issues?


Spelling Mistakes

First paragraph of README.md: witten should be written;
Section 1.7.2 of the book on page 11: tooolchain should be toolchain.

多谢，已更正。


Calculated column type is guessed incorrectly if first 100 rows are null

v1.16.7
Steps to reproduce

Open SPGI
Open 'Add new column' dialog > type is 'String' by default
Drag 'CYP 3A Induction (PXR Reporter Gene Assay) % max' (its type is 'double') column into the formula editing area

Expected results: calculated column is auto detected as 'double' after dragging this column to the formula editor.
Actual results: calculated column type is still displayed as 'String'.

Type is still auto detected as 'String' when this column is combined with other numerical columns using arithmetic operations:

Issue can be reproduced for any column where first 100 rows are null.

This issue has been mirrored in Jira: https://reddata.atlassian.net/browse/GROK-14616

This issue has been mirrored in Jira: https://reddata.atlassian.net/browse/GROK-16142


Calling moment.utc("2016-07-01").year(2013).toString() provides the wrong date

Description of the Issue and Steps to Reproduce:
It seems like when setting the date to a date in the past and then setting the year to anything will push the outputted date to be at the end of the month.
If you call moment.utc("2016-07-01").year(2013).toString() you will get Wed Jul 31 2013 00:00:00 GMT+0000. Notice how it is Jul 31 and not Jul 01.
Environment:
I've reproduced this in Chrome 61 as well as in Node 5.10.1
Other information that may be helpful:
This seems to only be an issue if you are using a date from the year 2016. If you try moment.utc("2015-07-01").year(2013).toString() it works fine.
I can confirm that this is not an issue previous to moment 2.19.0+. It only is an issue from 2.19.0+
If you are reporting an issue, please run the following code in the environment you are using and include the output:
console.log( (new Date()).toString())
console.log((new Date()).toLocaleString())
console.log( (new Date()).getTimezoneOffset())
console.log( navigator.userAgent)
console.log(moment.version)

Thu Oct 12 2017 23:10:36 GMT-0300 (ADT)
10/12/2017, 11:10:36 PM
180
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36
2.19.1

In version 2.19.0 the function set$1() was changed.
Because of this change, setting a new year for a leap year moment, it always sets the last day of the month as date.
moment('2010-02-25').year(2017) // result is: 2017-02-28
moment('2010-10-15').year(2017) // result is: 2017-10-31

Current (incorrect) implementation
function set$1 (mom, unit, value) {
    if (mom.isValid() && !isNaN(value)) {
        if (unit === 'FullYear' && isLeapYear(mom.year())) {
            mom._d['set' + (mom._isUTC ? 'UTC' : '') + unit](value, mom.month(), daysInMonth(value, mom.month()));
        }
        else {
            mom._d['set' + (mom._isUTC ? 'UTC' : '') + unit](value);
        }
    }
}

Because the special case is only needed for th 29th of Februar in leap years, the correct implementation should be:
function set$1 (mom, unit, value) {
    if (mom.isValid() && !isNaN(value)) {
        if (unit === 'FullYear' && isLeapYear(mom.year()) && mom.month() === 1 && mom.date() === 29) {
            mom._d['set' + (mom._isUTC ? 'UTC' : '') + unit](value, 1, daysInMonth(value, 1));
        }
        else {
            mom._d['set' + (mom._isUTC ? 'UTC' : '') + unit](value);
        }
    }
}

Because this is a critical error it should be corrected as soon as possible.

sorry just noticed i wrote "I can confirm that this is not an issue previous to moment 1.19.0+. It only is an issue from 1.19.0+" but I actually meant 2.19... ive updated this in the original post

@HolgerFrank Would you mind submit a PR to fix this? It's a pretty critical bug which should be fixed asap..

Closing in favor of PR.


PHP 8.2 does not match composer.json dependencies

Hello,
I'm trying to upgrade our php version from 8.1 to 8.2. Unfortunately your package throw me an error when I do a composer install because of php version limited to 8.1.
I will open a PR to increase this version dependency 🙏🏻
Regards

Can you clarify what you mean? ^8.1 does not forbid to use the package with PHP 8.2. Which issues did you end up with?

this repository is now abandon.


Throw UnspecifiedError when change Percent of UnsignedMixerControl instance

Please help me, thanks!!
In some case, It throws an exception below:
NAudio.MmException   UnspecifiedError calling mixerSetControlDetails
public double MicrophoneLevel
{
get
{
return _desiredVolume;
}
set
{
_desiredVolume = value;
if (_mixerControl != null)
{
_mixerControl.Percent = value;
}
}
}
it invoke on "  _mixerControl.Percent = value;"

What value are you setting it to?


feat: add support for checkov

Adding setup-checkov and checkov-version Github Action input parameters to setup checkov
Example config in digger.yml
projects:
  - name: project_a_d
    dir: ./project_a/development
    workflow: project_a

workflows:
  project_a:
    plan:
      steps:
        - init
        - plan
        - run: ./checkov -d . --framework terraform

See https://github.com/diggerhq/francios-tests/actions/runs/4999052252/jobs/8955062270

Adding setup-checkov and checkov-version Github Action input parameters to setup checkov
The binary gets installed under ./python_venv/bin/checkov and can be executed as this in digger.yml
projects:
  - name: project_a_d
    dir: ./project_a/development
    workflow: project_a

workflows:
  project_a:
    plan:
      steps:
        - init
        - plan
        - run: ../../python_venv/bin/checkov -d . --framework terraform

See https://github.com/diggerhq/francios-tests/actions/runs/4999052252/jobs/8955062270

Updated the PR, to avoid having to do "../../python_venv/bin/checkov". It should work with just "checkov"

@JamesWoolfenden
It can run by configuring the digger.yaml file, as the example I included in this PR description.
The command would be hardcoded per project


Add the EOS_TOKEN to generated text in scoring/vibe_score.py

I enabled the verbose mode in scoring/vibe_score.py and got this:
Last user message:  *Smiles slyly, lowering her voice* Ah, the infamous "BB Meatball"... Now there's a houseguest who knows how to make an entrance! *Winks conspiratorially* The game was never the same after she took the stage, and not just because of her cooking skills.<|eot_id|>
Generated text:  *Smiles slyly, lowering her voice* Ah, the infamous "BB Meatball"... Now there's a houseguest who knows how to make an entrance! *Winks conspiratorially* The game was never the same after she took the stage, and not just because of her cooking skills.
Vibe score: 0.9265049695968628

As you can see the messages are identical, but the score is ~0.92. This is because the scoring.dataset.StreamedSyntheticDataset.__getitem__ method returns the character_response with the EOS_TOKEN, while the decoded_messages variable from the scoring/vibe_score.py:53 script doesn't have it. I suggest to add the EOS_TOKEN before calculating the length of the decoded message.
We can accept input_tokenizer in the calculate_vibe_match_score function and then change this:
decoded_len = len(decoded)

to this:
decoded_len = len(f"{decoded}{input_tokenizer.eos_token}")

Please check this : https://github.com/impel-intelligence/dippy-bittensor-subnet/pull/123


GPT Tags with React-GPT do not change on other pages and use parent page GPT

Hi,
I Added GPT tags with react-gpt and when I use  tag to call other pages, the GPT tags do not change and stay at the same position at it was on the previous page.
Can you help me identify what I am doing wrong here?

This issue seems to be related to react-gpt, not react-static.
Also, without code we can't even begin to help you.

Yes this is an issue with react-gpt. Let us know if there is anything else we can help you with on the react-static side.


Unable to run invariant tests using handler pattern

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.0.2 (a69c479 2024-09-06T00:32:22.954024000Z)
What command(s) is the bug in?
forge test --zksync
Operating System
macOS (Apple Silicon)
Describe the bug
When running the invariant test, the test seems to be passing but strangely the functions in the handler contract are not being called for some reason.
To replicate, run forge test --match-contract PoolInvariants -vv --show-progress on this branch and you would see the following output in the terminal:
forge test --match-contract PoolInvariants -vv --show-progress

No files changed, compilation skipped
tests/core/pool-invariant/PoolInvariants.t.sol:PoolInvariants
  ↪ Suite result: ok. 2 passed; 0 failed; 0 skipped; finished in 23.04s (44.22s CPU time)

Ran 2 tests for tests/core/pool-invariant/PoolInvariants.t.sol:PoolInvariants
[PASS] invariant_checkHealthFactor() (runs: 25, calls: 25000, reverts: 0)
[PASS] invariant_summary() (runs: 25, calls: 25000, reverts: 0)
Logs:
  Supply Success Calls USDX: 71
  Borrow Success Calls USDX: 62
  Borrow Fail Calls USDX: 43
  Withdraw Success Calls USDX: 70
  Withdraw Fail Calls USDX: 47
  Repay Success Calls USDX: 85
  Repay Fail Calls USDX: 91

  Supply Success Calls WETH: 51
  Borrow Success Calls WETH: 55
  Borrow Fail Calls WETH: 22
  Withdraw Success Calls WETH: 47
  Withdraw Fail Calls WETH: 22
  Repay Success Calls WETH: 55
  Repay Fail Calls WETH: 38

  Supply Success Calls WBTC: 55
  Borrow Success Calls WBTC: 34
  Borrow Fail Calls WBTC: 14
  Withdraw Success Calls WBTC: 29
  Withdraw Fail Calls WBTC: 27
  Repay Success Calls WBTC: 43
  Repay Fail Calls WBTC: 39

Suite result: ok. 2 passed; 0 failed; 0 skipped; finished in 23.04s (44.22s CPU time)

When the same test is being run in zksync, we see that the handler functions are not being called. To run the same test in zksync and replicate: checkout to this branch, copy .env.examples to .env and run FOUNDRY_PROFILE=zksync forge test --zksync --match-contract PoolInvariants --rpc-url https://mainnet.era.zksync.io -vv --show-progress.
This is the output we are getting when running the same test in zksync:
FOUNDRY_PROFILE=zksync forge test --zksync --match-contract PoolInvariants --rpc-url https://mainnet.era.zksync.io -vv --show-progress

[⠃] Using zksolc-1.5.3

No files changed, compilation skipped
tests/core/pool-invariant/PoolInvariants.t.sol:PoolInvariants
  ↪ Suite result: ok. 2 passed; 0 failed; 0 skipped; finished in 1160.67s (21.18s CPU time)

Ran 2 tests for tests/core/pool-invariant/PoolInvariants.t.sol:PoolInvariants
[PASS] invariant_checkHealthFactor() (runs: 1, calls: 2, reverts: 0)
[PASS] invariant_summary() (runs: 1, calls: 2, reverts: 0)
Logs:
  Supply Success Calls USDX: 0
  Borrow Success Calls USDX: 0
  Borrow Fail Calls USDX: 0
  Withdraw Success Calls USDX: 0
  Withdraw Fail Calls USDX: 0
  Repay Success Calls USDX: 0
  Repay Fail Calls USDX: 0

  Supply Success Calls WETH: 0
  Borrow Success Calls WETH: 0
  Borrow Fail Calls WETH: 0
  Withdraw Success Calls WETH: 0
  Withdraw Fail Calls WETH: 0
  Repay Success Calls WETH: 0
  Repay Fail Calls WETH: 0

  Supply Success Calls WBTC: 0
  Borrow Success Calls WBTC: 0
  Borrow Fail Calls WBTC: 0
  Withdraw Success Calls WBTC: 0
  Withdraw Fail Calls WBTC: 0
  Repay Success Calls WBTC: 0
  Repay Fail Calls WBTC: 0

Suite result: ok. 2 passed; 0 failed; 0 skipped; finished in 1160.67s (21.18s CPU time)

We see that none of the actions of the invariant test, including Supply, Borrow, Withdraw, Repay are being called for some reason but the same test in normal foundry works fine.

Hey @brotherlymite, thanks for the report!
We investigated the issue and found that this behavior can be observed when using the handler pattern.
In particular, when the handler is called it is done thru the zkVM, thus when the handler makes use of cheatcodes, it causes the unexpected behavior you are observing (in this case, the execution is equivalent to a no-op).
There's no way for us to determine if the target selectors are handler contracts or not, thus it's not possible to determine whether to run it in EVM or zkVM automatically.
We are working on a new feature (#569) which will make calling cheatcodes in external contracts a lot easier to work with, without having to switch zkvm on or off manually.

Unfortunately, there's no workaround available to make it work today, but if you wish to maintain this type of test I can suggest migrating to a fuzz test instead, for example:
struct SummaryInput {
  uint8 tokenIndex;
  uint128 amount;
  uint8 opIdx;
}

/// forge-config: zksync.fuzz.runs = 25
/// forge-config: zksync.fuzz.show-logs = true
function testFuzz_summary(SummaryInput[1000] memory inputs) external {
  address(vm).call(abi.encodeWithSignature("zkVm(bool)", false));

  FuzzSelector memory pool = targetSelectors()[0];

  for (uint i = 0; i < inputs.length; i++) {
    SummaryInput memory input = inputs[i];

    uint8 idx = (input.opIdx % uint8(pool.selectors.length));
    bytes4 op = pool.selectors[idx];

    address(s_poolHandler).call(abi.encodeWithSelector(op, input.tokenIndex, input.amount));

  }

  s_poolHandler.summary();
}

You can tweak the runs paramters like usual, and the depth is represented by the array length. In the snippet above I made it match the original (non-zksync) test configuration you reported (please note that show-logs might be undesirable).
Note that the calls to PoolHandler will happen in EVM, thus zkVM must be switched on inside it for the contract under test to be ran inside zkVM. Additionally, it's important to ensure that PoolHandler is either deployed in EVM or be made persistent, otherwise its deployment in setUp will happen in zkVM only, not allowing it to be called from within the test.

Hey @brotherlymite, upon further review we actually determined the issue to be a bit different.
The handler is actually being called via EVM, so cheatcodes would be fine, but the deployment happens in zkEVM (during setUp), thus the contract wouldn't be present in EVM and cause this behavior.
The fix in this case would be to deactivate zkVm before doing the deployment of the handler, which resolves the issue above, and allows invariant tests to run as normal.
Unfortunately, this means we have the opposite problem: non-handler pattern is not working as intended.
Additionally, in the version you originally encountered the issue there's still a bug, in particular when the deployment happening in EVM instead of zkVM, it wouldn't be detected for the invariant executor, but this has been resolved as of #572, therefore an upgrade is required to run invariant tests with the handler pattern.

There are a few more adjustments that need to be made to make the invariant test to run successfully, but these are relatively easy and are just to account for zkVM specifics:

use profile.zksync.invariant.no_zksync_reserved_addresses, this prevents reserved addresses to be used for fuzzed senders
deal ETH to the user to allow the transaction to be ran, otherwise the bootloader will error out because the balance is insufficient
ensure that tx.origin is set correctly - in particular startPrank(user) should change to startPrank(user, user), otherwise the tx originator will be set to the caller of PoolHandler, instead of the pranked sender. If the fuzzed sender is the originator, you'll need to deal ETH to it, for the same reason as dealing to user

Please let me know if you have any more questions about this issue! Thank you

Hey @brotherlymite! We have fixed the issue with invariant testing as of #581!
We also added 2 tests and improved an existing one to ensure this stays the case in the future, you could make use of them as reference, in particular the reproduction test for this issue!
Please let me know if you still encounter issues!


FIX: Pydantic v2 patch upgrade

Hi Dan,
Hope you are well!
hdl21 is conflicting with some other packages that have updated to pydantic v2. I've tried to do the proper migration, only to realise it is quite involved and will take me far longer than I can.
However, instead, what I have done in this PR is to do the patch migration where everything stays compatible to the original version using the pydantic.v1 submodule they provide. This makes the migration much easier and can be progressively implemented if required.
This is still a draft because when I ran the pytest I got this:
>       return vlsir.Prefixed(string_value=str(pref.number), prefix=prefix)
E       ValueError: Protocol message Prefixed has no "string_value" field.

hdl21\proto\exporting.py:434: ValueError
======================================================================================================= short test summary info =======================================================================================================
FAILED examples/test_examples.py::test_ro - ValueError: Protocol message Prefixed has no "int64_value" field.
FAILED examples/test_examples.py::test_rdac - ValueError: Protocol message Prefixed has no "int64_value" field.
FAILED examples/test_examples.py::test_diff_ota - ValueError: Protocol message ParamValue has no "int64_value" field.
FAILED examples/test_examples.py::test_idac - ValueError: Protocol message Prefixed has no "int64_value" field.
FAILED hdl21/pdk/sample_pdk/test_sample_pdk.py::test_netlist - ValueError: Protocol message Prefixed has no "int64_value" field.
FAILED hdl21/sim/tests/test_sim.py::test_sim2 - ValueError: Protocol message Prefixed has no "int64_value" field.
FAILED hdl21/sim/tests/test_sim.py::test_simattrs - ValueError: Protocol message Prefixed has no "int64_value" field.
FAILED hdl21/sim/tests/test_sim.py::test_sim_decorator - ValueError: Protocol message Prefixed has no "int64_value" field.
FAILED hdl21/sim/tests/test_sim.py::test_proto1 - ValueError: Protocol message Prefixed has no "int64_value" field.
FAILED hdl21/sim/tests/test_sim.py::test_delay1 - ValueError: Protocol message Prefixed has no "int64_value" field.
FAILED hdl21/tests/test_builtin_generators.py::test_mos_generator - ValueError: Protocol message Prefixed has no "int64_value" field.
FAILED hdl21/tests/test_exports.py::test_prim_proto1 - ValueError: Protocol message Prefixed has no "int64_value" field.
FAILED hdl21/tests/test_exports.py::test_ideal_primitives - ValueError: Protocol message Prefixed has no "int64_value" field.
FAILED hdl21/tests/test_exports.py::test_spice_netlister - ValueError: Protocol message Prefixed has no "int64_value" field.
FAILED hdl21/tests/test_exports.py::test_roundtrip_external_module - ValueError: Protocol message ParamValue has no "int64_value" field.
FAILED pdks/Gf180/gf180_hdl21/test_netlists.py::test_xtor_netlists - ValueError: Protocol message Prefixed has no "int64_value" field.
FAILED pdks/Gf180/gf180_hdl21/test_netlists.py::test_2_term_res_netlists - ValueError: Protocol message Prefixed has no "int64_value" field.
FAILED pdks/Gf180/gf180_hdl21/test_netlists.py::test_3_term_res_netlists - ValueError: Protocol message Prefixed has no "int64_value" field.
FAILED pdks/Gf180/gf180_hdl21/test_netlists.py::test_diode_netlists - ValueError: Protocol message Prefixed has no "string_value" field.
FAILED pdks/Gf180/gf180_hdl21/test_netlists.py::test_3T_bjt_netlists - ValueError: Protocol message Prefixed has no "int64_value" field.
FAILED pdks/Gf180/gf180_hdl21/test_netlists.py::test_4T_bjt_netlists - ValueError: Protocol message Prefixed has no "int64_value" field.
FAILED pdks/Gf180/gf180_hdl21/test_netlists.py::test_cap_netlists - ValueError: Protocol message Prefixed has no "int64_value" field.
FAILED pdks/Gf180/gf180_hdl21/test_pdk.py::test_netlist - ValueError: Protocol message Prefixed has no "string_value" field.
FAILED pdks/Sky130/sky130_hdl21/test_netlists.py::test_xtor_netlists - ValueError: Protocol message Prefixed has no "int64_value" field.
FAILED pdks/Sky130/sky130_hdl21/test_netlists.py::test_2_term_res_netlists - ValueError: Protocol message Prefixed has no "int64_value" field.
FAILED pdks/Sky130/sky130_hdl21/test_netlists.py::test_3_term_res_netlists - ValueError: Protocol message Prefixed has no "int64_value" field.
FAILED pdks/Sky130/sky130_hdl21/test_netlists.py::test_diode_netlists - ValueError: Protocol message Prefixed has no "int64_value" field.
FAILED pdks/Sky130/sky130_hdl21/test_netlists.py::test_pnp_netlists - ValueError: Protocol message Prefixed has no "int64_value" field.
FAILED pdks/Sky130/sky130_hdl21/test_netlists.py::test_npn_netlists - ValueError: Protocol message Prefixed has no "int64_value" field.
FAILED pdks/Sky130/sky130_hdl21/test_netlists.py::test_mim_cap_netlists - ValueError: Protocol message Prefixed has no "int64_value" field.
FAILED pdks/Sky130/sky130_hdl21/test_netlists.py::test_var_cap_netlists - ValueError: Protocol message Prefixed has no "int64_value" field.
FAILED pdks/Sky130/sky130_hdl21/test_pdk.py::test_netlist - ValueError: Protocol message Prefixed has no "string_value" field.
======================================================================================== 32 failed, 180 passed, 4 skipped, 5 xfailed in 3.69s ==================================

However, as far as I can tell, these are all issues in vlsirtools when tested from hdl21. The latest github versions are straightup incompatible, so this is when using vlsirtools==4.0.0 release.
What do you think? I'm going to try to keep debugging to get the tests to pas. They're all related to int64_value fields so maybe that makes some sense to you. It'd be nice to have a patch release of this in pypi when we get tests to pass so that hdl21 can be used in a compatible environment with the other pydantic v2 tools.
Re https://github.com/dan-fritchman/Hdl21/issues/157 and maybe https://github.com/dan-fritchman/Hdl21/issues/174

I've realised this has to do with the latest protobuffer changes, so I don't think it necessarily has to do with the pydantic upgrade.
dario@DESKTOP-1T2BQKV MINGW64 ~/Documents/phd/software/Hdl21 (pydantic_v2_patch_upgrade)
$ python -m pytest
ImportError while loading conftest 'C:\Users\dario\Documents\phd\software\Hdl21\conftest.py'.
conftest.py:8: in <module>
    from vlsirtools.pytest import (
..\vlsir\vlsirtools\vlsirtools\__init__.py:8: in <module>
    from . import spice
..\vlsir\vlsirtools\vlsirtools\spice\__init__.py:2: in <module>
    from . import spectre
..\vlsir\vlsirtools\vlsirtools\spice\spectre.py:15: in <module>
    from ..netlist.spectre import SpectreNetlister
..\vlsir\vlsirtools\vlsirtools\netlist\__init__.py:16: in <module>
    from .spectre import SpectreNetlister
..\vlsir\vlsirtools\vlsirtools\netlist\spectre.py:14: in <module>
    from .spectre_spice_shared import SpectreSpiceShared
..\vlsir\vlsirtools\vlsirtools\netlist\spectre_spice_shared.py:2: in <module>
    from .base import Netlister
..\vlsir\vlsirtools\vlsirtools\netlist\base.py:13: in <module>
    from .. import primitives
..\vlsir\vlsirtools\vlsirtools\primitives.py:255: in <module>
    value=ParamValue(int64_value=0),

Ahh thanks for the merge of the fix! I am trying it now.
In here they describe that this notation should mean pydantic v1 is available within pydantic v2, but I know it introduces breaking changes with the v1 original dependency, as this version is v1 inside v2. I'd be happy to help port the project you care about too if it's public! Unsure how to test best those subtle changes!
Unfortunately it is the latest versions >7.3 of gdsfactory and the collection of gplugins which I use quite often with hdl21 so it affects a fair bit when using both tools! Would it work to have a 4.0.1alpha version for the future pydantic upgrade so that when the time comes this helps port to it and is just a pre-release but does not replace 4.0.0? I think that might work but sorry to ask putting a bit more work for you. Would be most appreciated!

OK thanks.
And sadly I don't expect the peer project is gonna sign up for your contributions. Much less to a particular schedule.
I can imagine Hdl21 (or any similar library) detecting which version it has and reacting with something like:
# In, like, hdl21/our_pydantic_stuff.py
import pydantic

# Sort out which namespace to use
if figure_out_version_2_or_greater():
  our_pydantic_stuff = pydantic.v1
else:
  our_pydantic_stuff = pydantic

# "Export" the stuff we want to expose directly in this module namespace
dataclass = our_pydantic_stuff.dataclass
BaseModel = our_pydantic_stuff.BaseModel
# ... all other such things we use

# Everywhere else in Hdl21

## from pydantic.dataclasses import dataclass ## <= No! Bad!
from .our_pydantic_stuff import dataclass ## <= that's the idea

Does, like, their migration tool do something like this already?
I also don't know whether those "v1" types actually work when bundled in with v2. But you could try.


Searching for resource tokens doesn't work

Problem description
Searching for a resource from the search box at https://www.pulumi.com/registry/ does not work. For example, searching for aws.s3.Bucket (our intro resource in our most common language) does not show the API docs for that resource.

Hitting enter, the results change but it's still almost always examples. A resource doc is mentioned, but its for aws.s3, not aws.s3.Bucket.

Searching for the pulumi token aws:s3/bucket:Bucket doesn't work either:

Originally, this issue included the following, but @jkodroff pointed out that is a duplicate of https://github.com/pulumi/registry/issues/1515.
Searching for a resource from the search box at https://www.pulumi.com/registry/ does not work. For example, searching for aws.s3.Bucket (our intro resource in our most common language) does not show the API docs for that resource.

Hitting enter, the results change but it's still almost always examples. A resource doc is mentioned, but its for aws.s3, not aws.s3.Bucket.


Add tests

#30

@paskal Hi, it is PR in WIP, he is not ready

Current PR coverage 66.7%
@umputun @paskal
I suggest merge this PR and don't close issue, to continue working further


Missing Falco driver for EKS machines

Falco not able to load driver module. Getting the below error:
* Setting up /usr/src links from host
* Running falco-driver-loader for: falco version=0.32.2, driver version=2.0.0+driver
* Running falco-driver-loader with: driver=module, compile=yes, download=yes

================ Cleaning phase ================

* 1. Check if kernel module 'falco' is still loaded:
- OK! There is no 'falco' module loaded.

* 2. Check all versions of kernel module 'falco' in dkms:
- There are some versions of 'falco' module in dkms.

* 3. Removing all the following versions from dkms:
2.0.0+driver

- Removing 2.0.0+driver...

------------------------------
Deleting module version: 2.0.0+driver
completely from the DKMS tree.
------------------------------
Done.

- OK! Removing '2.0.0+driver' succeeded.

[SUCCESS] Cleaning phase correctly terminated.

================ Cleaning phase ================

* Looking for a falco module locally (kernel 5.4.209-116.367.amzn2.x86_64)
* Trying to download a prebuilt falco module from https://download.falco.org/driver/2.0.0%2Bdriver/x86_64/falco_amazonlinux2_5.4.209-116.367.amzn2.x86_64_1.ko
curl: (22) The requested URL returned error: 404
Unable to find a prebuilt falco module
* Trying to dkms install falco module with GCC /usr/bin/gcc
DIRECTIVE: MAKE="'/tmp/falco-dkms-make'"

Creating symlink /var/lib/dkms/falco/2.0.0+driver/source ->
                 /usr/src/falco-2.0.0+driver

DKMS: add completed.
* Running dkms build failed, couldn't find /var/lib/dkms/falco/2.0.0+driver/build/make.log (with GCC /usr/bin/gcc)
* Trying to dkms install falco module with GCC /usr/bin/gcc-8
DIRECTIVE: MAKE="'/tmp/falco-dkms-make'"
* Running dkms build failed, couldn't find /var/lib/dkms/falco/2.0.0+driver/build/make.log (with GCC /usr/bin/gcc-8)
* Trying to dkms install falco module with GCC /usr/bin/gcc-6
DIRECTIVE: MAKE="'/tmp/falco-dkms-make'"
* Running dkms build failed, couldn't find /var/lib/dkms/falco/2.0.0+driver/build/make.log (with GCC /usr/bin/gcc-6)
* Trying to dkms install falco module with GCC /usr/bin/gcc-5
DIRECTIVE: MAKE="'/tmp/falco-dkms-make'"
* Running dkms build failed, couldn't find /var/lib/dkms/falco/2.0.0+driver/build/make.log (with GCC /usr/bin/gcc-5)
* Trying to load a system falco module, if present

AWS EKS 1.23
OS Image: Amazon Linux 2
Kernel version: 5.4.209-116.367.amzn2.x86_64_1
Falco Loader: version: 0.32.2
Falco version: 0.32.2

Same problem here

I have same issue in for all the same version mentioned above. When can we get the fix?

Hi @xavidop, as you can see here, https://falcosecurity.github.io/kernel-crawler/?arch=x86_64&target=AmazonLinux2&search=5.4.38-17.76.amzn2.x86_64,  the kernel-crawler has found the kernel and it has been built. The kernel module can be downloaded using the following link: https://download.falco.org/driver/2.0.0%2Bdriver/x86_64/falco_amazonlinux2_5.4.209-116.367.amzn2.x86_64_1.ko.
Sometimes it could happen that the latest kernels are not found and built immediately. Currently, the scraping and building of new kernels are done weekly.

I just checked and its working! thank you very much! Good to know that you have that kernel-crawler running!

Great!
Can we please close this issue then?

YES! thank you very much!


why do not release a jar file

why do not release a jar file ....

What do you mean? I publish all jars as maven artifacts to maven central. There you could download jar files. Or do you request, where the release 0.9.5 is?


Support ember bind to attribute syntax

I am trying to add support for binding to attribute syntax but it's hard to achieve it. A very simple example is the one below:
string source =@"<div {{bind-attr class='className'}}>{{title}}</div>";
var template = Handlebars.Handlebars.Compile(source);
var data = new {
  className = "foo",
  title = "My new post"
};
var result = template(data);

The main problem is that I am able to register a custom helper with the name "bind-attr" but then the arguments array has one element that is undefined. Do you think is feasible to achieve something like this with a custom helper or it needs more changes?

Interesting, how does the Handlebarsjs library handle that?

I set up a JSBin test and I see how the JS library handles it - it creates a hash structure that is passed in as an argument. Need to think about how this would translate over to the .NET version from a dev experience standpoint; and also currently the lexer cannot handle complex structures like name=value... that is a TODO listed in the Tokenizer.

I think we can close this issue. After deeper investigation on Ember I found that the bind-attr will be removed from the code and from version 1.11, currently in beda, will support the standard way of binding to attributes, e.g. class="{{className}}".
I saw also the TODO in the Tokenizer and by doing this I understood better this project. If I can help on further improvement please let me know.


PBJ zone_asset addition

Description

Checklist

Adding Assets

If adding a new asset, please ensure the following:

[x] Asset is registered to the Cosmos Chain Registry.
[x] Add asset to bottom of zone_assets.json.

[x] chain_name and base_denom are provided and use values exactly as defined at the Chain Registry.
[x] path is provided, and the IBC channel referenced is registered at the Chain Registry (unless native to Osmosis).
[x] osmosis_verified is set to false
[x] listing_date_time_utc is specified and accurate
[x] Optional: transfer_methods, peg_mechanism, override_properties, canonical, categories, where necessary (see README for details).

Adding Chains

If adding a new chain, please ensure the following:

[ ] Chain is registered to the Cosmos Chain Registry.

Chain's registration must have staking defined, with at least one staking_token denom specified.
Chain's registration must have fees defined; at least one fee token has low, average, and high gas prices defined.

[ ] IBC Connection between chain and Osmosis is registered.
[ ] Add chain to bottom of zone_chains.json

[ ] rpc and rest does not have any CORS blocking of the Osmosis domain, and RPC node has have WSS enabled.
[ ] explorer_tx_url correctly directs to the transaction when the hash is inserted into the URL.

Upgrading Asset to Verified

If upgrading an Asset to Verified, please see the requirements specified at LISTING, and ensure the following:

[ ] Asset is defined thoroughly at the Cosmos Chain Registry.

[ ] A meaningful description (and extended_description, unless classified as 'meme').
[ ] Associated socials, including website and twitter.
[ ] Logo Image has a square Aspect Ratio, < 250 KB file size, and appropriate visual contrast with Osmosis Zone colors.

[ ] This pool contains contains at least $1k USD-worth of liquidity of the asset (Provide Pool ID): ______

'Verified' Status Validation Checklist (to be completed by Osmosis Zone maintainers):

[ ] Verify appearance and metadata
[ ] Accurate Price
[ ] Trading and routing functionality
[ ] Withdraw and Deposit

[ ] Deposit Transaction URL (if in-app)

Noticed my formatter went a little wild this JSON, but not on my Chain Registry PRs. Both using VS code to edit the files.
Sorry about overlooking that. Let me know if I need to revert commits or make a new PR.


Resource: derived column

A resource to manage the derived columns of a dataset.
More information: https://docs.honeycomb.io/working-with-your-data/customizing-your-query/derived-columns/
Reference: https://docs.honeycomb.io/working-with-your-data/customizing-your-query/derived-columns/reference/#docs-sidebar
API: there is no API yet for this
Possible Terraform schema:
resource "honeycombio_derived_column" "example" {
  dataset     = "my-dataset"
  alias       = "duration_ms_log10"
  description = "Log10 of duration_ms"

  function = "LOG10($\"duration_ms\")"
}

Is there any info on when this API might be available?

Not that I'm aware of. I have seen this been requested before on the Pollinators Slack, so they are already tracking it. But I don't know if it is part of the roadmap for the near future.
Your best bet is probably to post something on Slack again.


Scaffold react components

Resolves https://github.com/silverstripe/silverstripe-session-manager/issues/11
Marked as draft as this is only the scaffolding for the react field. So it might be a good idea to just approve this without merging, then I'll merge the actual rendering of the field back into this branch later before we merge back into 1.
I'll also update code coverage after this.

A few bits to trim and rename, otherwise this is a solid base to build on 👍

@Cheddam I've fixed up the things you requested. :)


Grammatical Change

changed  the last question
from
Create an nginx deployment of 2 replicas, expose it via a ClusterIP service on port 80. Create a NetworkPolicy so that only pods with labels 'access: granted' can access the deployment and apply it
to
Create an nginx deployment of 2 replicas, expose it via a ClusterIP service on port 80. Create a NetworkPolicy so that only pods with labels 'access: granted' can access the pods created by nginx deployment and apply it
AFAIK Pods can access other Pods and Pods cannot access Deployments. So I got confused when I read the question for the first time.

question changes if ok


First run

i embed the init view controller but the Intro have a problem! (the bar)
I cant find solution, any idea.. thanks
image:
https://www.dropbox.com/s/2er5usimb2e6zjg/Captura de pantalla 2016-07-04 a las 7.33.07 p.m..png?dl=0

I guess you are using the NDParallaxIntroView within a UINavigationController, which has a NavigationBar by default. You could hide the NavigationBar or use a ViewController which is presented modally not embedded in the UINavigationController structure which I would be the preferred solution.
Hope that helps a bit... :)

try
[self.navigationController.view addSubview:self.introView];


Prepare to Rector next 2.0 with PHPStan 2 and PHPParser 5

Rector is upgrading to PHPStan 2 and PHPParser 5 at PR:

https://github.com/rectorphp/rector-src/pull/6431

this PR upgrade for compatiblity syntax.

Ready when Rector 2.0 released, rector/rector can be updated to:
- "rector/rector": "dev-main as 1.2.10",
+ "rector/rector": "~2.0.0",

@carlos-granados bumped to Rector ~2.0.0, ready to merge 👍

Thanks @samsonasik I am preparing a bigger PR with more changes, I'll cherry pick yours

Thanks @samsonasik, I incorporated these changes to the latest version on a separate merge


Installation fails in Dalamud and download link on website does not work

Below button just redirects to the same page

Hi!
I apologize for any inconvenience. The issue was due to a failure in deploying to Cloudflare Pages.
It is now available for use without any problems.