[FEATURE]"Have we met before" condition, Wait and Stop actions.

It would be great to use these functionalities. For example:
0: Condition: MetBefore Failed=>1 Met=>4
1: Message: Hello %player_name% ! I have a quest for you !
2: Delay: 15 ticks
3: Message: Bring me a good sword if you can !
4: Condition: Item sword Failed=> 9 Met=>5 Take: Enabled
5: Message: Great sword, come again tomorrow.
6: Wait: Time: 12H WaitMessage: See you tomorrow !
// now, this acts like an anchor, when player will come again and talk to a NPC,
// he will start from this moment,
// WaitMessage will be used when player will interact with NPC while he waits
7: Message: I have next quest for you.
// ... and so on
8: Message: I don't have more quests for you, thanks for helping !
// and when we want to stop, we just using Stop action, to prevent see 'helper messages'
8: Stop
9: Message: So do it and bring me one !

With disabled repeat we can make a mini quest story from NPC. This feature will bring plugin to the new level and allow to more complex interactions with NPC. If you don't understand me I can write pseudo code for this. Please let me know what do you think about this !

PixelBuilt-Quests can do quests.

Yeah, I found your plugin after writing this... I will check your plugin when I will be home.
Btw. Cooldown feature will be great in this plugin.


sensor_processing package miss key image copy operation

Hi, your project is very awesome, and I am very inspired by this project.
I found the processImage function in sensor_processing package don't work well as show as below:
cv::Mat sem_edge_img, sem_dil_img, sem_output;
	if(params_.sem_ed){
		cv::Canny(sem_image_, sem_edge_img, params_.sem_ed_min,
			params_.sem_ed_max, params_.sem_ed_kernel);
		cv::dilate(sem_edge_img, sem_dil_img, cv::Mat(),
			cv::Point(-1, -1), 1, 1, 1);
		sem_image_.copyTo(sem_output, sem_dil_img);
	}

	// Publish
	cv_bridge::CvImage cv_semantic_image;
	cv_semantic_image.image = sem_output;

when the if(params_.sem_ed) condition is not true, the sem_output is null image, I think your should add sem_output = sem_image_ above cv_bridge::CvImage cv_semantic_image;.
Thanks!

Thank you Andrew for your kind words! I definitely appreciate this!
And even a bigger thanks for pointing out this flaw :) well spotted!! I’m
gonna make a PR within the next days and make the change you suggested!
Because I love the field of perception of self driving cars and the people
that are working on it as well, I am curious to ask where your from and
what kind of research you pursue? Always interested in this!
And if you have some more ideas or suggestions, please point them out! I
love open source and that’s why I shared my work! Also make sure to give my
repo a star ⭐ to push it further to top :)
Thanks!
Happy hacking,
Simon
On Wed 5. Dec 2018 at 13:01, Andrew Z<EMAIL_ADDRESS>wrote:

Hi, your project is very awesome, and I am very inspired by this project.
I found the processImage function in sensor_processing package don't work
well as show as below:
cv::Mat sem_edge_img, sem_dil_img, sem_output;
if(params_.sem_ed){
cv::Canny(sem_image_, sem_edge_img, params_.sem_ed_min,
params_.sem_ed_max, params_.sem_ed_kernel);
cv::dilate(sem_edge_img, sem_dil_img, cv::Mat(),
cv::Point(-1, -1), 1, 1, 1);
sem_image_.copyTo(sem_output, sem_dil_img);
}
// Publish
cv_bridge::CvImage cv_semantic_image;
cv_semantic_image.image = sem_output;
when the if(params_.sem_ed) condition is not true, the sem_output is null
image, I think your should add sem_output = sem_image_ above cv_bridge::CvImage
cv_semantic_image;.
Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/appinho/SARosPerceptionKitti/issues/11, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ASY4qzWT1sJLzw2T6WHtMB8SmSFwt1LOks5u13LqgaJpZM4ZCI5h
.

Thank you for your reply.
I am a postgraduate student in Beijing Institute of Technology, China.And I am also love the environment perception of autonomous vehicle.
My researh fields maily about DATMO (detection and tracking moving objects) by using sensors fusion techniques, mainly using lidar and camera.
I found your work is very similar with mine, and it's very glad for me to communicate with you. Hope we can keep contact with each other.

No problem!
That’s exactly my expertise as well! What is your GitHub name so I can see
your projects as well :) ?
On Wed 5. Dec 2018 at 16:43, Andrew Z<EMAIL_ADDRESS>wrote:

Thank you for your reply.
I am a postgraduate student in Beijing Institute of Technology, China.And
I am also love the environment perception of autonomous vehicle.
My researh fields maily about DATMO (detection and tracking moving
objects) by using sensors fusion techniques, mainly using lidar and camera.
I found your work is very similar with mine, and it's very glad for me to
communicate with you. Hope we can keep contact with each other.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/appinho/SARosPerceptionKitti/issues/11#issuecomment-444445330,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ASY4q46yM5D7a2K8sGb5-RR0otckJUXDks5u16bigaJpZM4ZCI5h
.

It's https://github.com/zhanghming .
And my frequently used email is<EMAIL_ADDRESS>you can send email to this address.
Thanks a lot!

Done!


nii.zst support

Description
Add Zstd support for NIFTI files so that .nii.zst files can be read and written. Similar to issue #348. This would be great for compression/decompression speed and the file sizes are slightly smaller than those produced by Deflate.

Has .zst support been added to the NIFTI standard?
BTW, there is .iwi.cbor.zst support in ITK-Wasm.

Is a wrapping extension really anything to do with the standard? I would argue its a compression helper.
This is not like minc with built in blocked hdf5 compression, you need to uncompress the whole file to do anything with it.

I understand that it is not widely supported. But that is why I spammed other software boards with this suggestion :) For it to be useful, you are right, it would need to de facto standardized but I guess you have to start somewhere.


fix(footer): use cursor pointer on feedback in footer

Changes

Use a cursor pointer on cover when hovering on Product Feedback

Preview

https://footer-and-nav.firebaseapp.com/

@naomiblack

live and in master!


APIs - Seeking Free Resources

We're building a comprehensive resource collection for developers at Free For Geeks.
We're currently looking for high-quality, free resources on APIs to add to our website.
If you've come across any fantastic free APIs resources that you think would benefit our developer community, please share them in the comments below! We'd love to include them on our site with proper attribution.
Thank you for your contributions to empowering developers everywhere! ✨

organize the APIs


Crash when try use texture from Unit8Array.

Some js native classes have a set method but not have a copy.
Map/Set/TypedArray (UInt8Array for example).
Ok, there are not reason handle a Map/Set as props because there are not API what use it, but should be way pass ArrayBuffer view.
This line try to use copy method that wrong for this case:
https://github.com/pmndrs/react-ogl/blob/main/src/utils.ts#L144
Possible fix:
// we should bypass set for array buffer, because it not resizable. You cant set a 4 values to array of 0.
if (target?.set && !ArrayBuffer.isView(value)) {
      if (target.constructor.name === value.constructor.name && target.copy) {
        target.copy(value)
      } else if (Array.isArray(value)) {
        target.set(...value)
      } else {
        // Support shorthand scalar syntax like scale={1}
        const scalar = new Array(target.length).fill(value)
        target.set(...scalar)
      }
} else {

This sometime can be used for API's like a :
{ /* texture 2x2 filled to red */ }
<texture
     width={2}
     height={2}
     image={new Uint8Array([255, 0, 0, 255, 255, 0, 0, 255, 255, 0, 0, 255, 255, 0, 0, 255]}
/>

Published a fix in 0.4.3. This was a bit of a blindspot, but we have good coverage now.


Feature: when removing a selection (click on X), should not open the dropdown

As per the title. It's quite annoying.
Or, should be just an option, with false as default.

Duplicate of https://github.com/select2/select2/issues/3209#issuecomment-149663474


Espresso fails

Without this change the ./gradlew connectedCheck fails with the following error:
Conflict with dependency 'com.android.support:support-annotations'. Resolved versions for app (22.1.0) and test app (22.0.0) differ.

@vogella You should not have to "force" the configuration. See my Robolectric deckard-gradle pull request: https://github.com/robolectric/deckard-gradle/blob/master/build.gradle#L39.

This is not needed anymore i just pushed 0.3/2.2 updates to the samples which resolves this issue.


One guess per team

Issue: after a failed guess, members from that team can still buzz in for another attempt
Expected: one guess per team

Done!


blurr Translation High Level API broken

On running a minor modification of Blurr Translation High level API, it looks broken.
The issue looks like the variable NLP is missing in file
NameError                                 Traceback (most recent call last)
Input In [21], in <module>
      1 #hide-output
----> 2 learn = BlearnerForTranslation.from_data(
      3     translation_df,
      4     pretrained_model_name,
      5     src_lang_name="English",
      6     src_lang_attr="en",
      7     trg_lang_name="Malayalam",
      8     trg_lang_attr="ml",
      9     dl_kwargs={"bs": 16},
     10 )

File /opt/conda/lib/python3.8/site-packages/blurr/text/modeling/seq2seq/translation.py:111, in BlearnerForTranslation.from_data(cls, data, pretrained_model_name_or_path, src_lang_name, src_lang_attr, trg_lang_name, trg_lang_attr, max_length, max_target_length, dblock_splitter, hf_tok_kwargs, text_gen_kwargs, dl_kwargs, learner_kwargs)
    109 model_cls = cls.get_model_cls()
    110 model = model_cls.from_pretrained(pretrained_model_name_or_path)
--> 111 hf_arch = NLP.get_model_architecture(type(model).__name__)
    113 if hf_arch == "mbart":
    114     hf_tok_kwargs = {**{"src_lang": "en_XX", "tgt_lang": "en_XX"}, **hf_tok_kwargs}

NameError: name 'NLP' is not defined

Issue can be reproduced with this gist:
https://gist.github.com/kurianbenoy/812512abae60a57851786958e33c1144

facing the same issue here ! :(

Good catch.
Had to remove the NLP singleton because it made the library unusable on kaggle.  Will fix this in next couple of days and issue a new release.


Added cloche recipes for all Pams Harvestcraft 2 Crops.

Verified they all show up in JEI, and also tested a few of them in action, and it seems to all work.

Mystical Flowers have a time value of 480 for rich soil, but should have 320 for rich soil to speed them up.

Done!


Regression in .input-group vs. grid cols

I'm testing update to the latest build from alpha6. I don't know if it's possible to create JSBin with unreleased bootstrap files, so here's the simple snippet:

    Label

Problem is that label is above the input which has width:100% defined in _input-group.scss, which has precedence over the width defined for .col-10 class.
The label should be on the left according to col-2 and col-10 classes used here, as it was in alpha6.

You can create a CodePen and you copy/paste last dist files in CSS and JS 😉

Don't put grid classes right on input groups—put it on the parent. That'll likely fix it.

Really? I don't know about v3, but it definitely worked in v4 alpha6. I know you'd like to move forward with v4 releases, but please, reconsider. You use similar structure for normal form-controls, using the same with group inputs sounds reasonable and consistent. No?

You're not using the correct markup—your column class shouldn't be on the input group (which has it's own flex styles and more that interfere with column classes) and your <input> is actually a
 for some reason. See https://jsbin.com/lopocakeho/edit?html,css,js,output.

Ok, I get it. It just worked before, so I thought you may want to support this case. Anyway, thank you for your work.


[Bug]: [intermittent ]The G sheet Authorisation fails when user tries to authorise

Is there an existing issue for this?

[X] I have searched the existing issues

Description
1.Gsheet breaks on user tries to authorize the data source
Steps To Reproduce

Import a json app that has gsheet datasource
now try to authorize the app the Users are navigated to "https://cs.appsmith.com/api/v1/integrations/oauth/authorize?appsmithToken=eyJhbGciOiJIUzUxMiJ9.eyJwbHVnaW4iOiJnb29nbGUtc2hlZXRzLXBsdWdpbiIsImlhdCI6MTY4NDMyMTEwNCwiZXhwIjoxNjg0MzIxNDA0LCJzdWIiOiIyY2YzNGFkZi1lZTg4LTRlOWEtOTcxMi03NDhlM2JlZDJkNWUifQ.ONHRjiohpsrCF9juo_6zqjLQ-L7KuKfsXQWIMdcXBcpHL488-PGxtOntJNzHk-KdoXZrteSXGTGh95M4CzLGcA"

the authorization fails

Public Sample App
No response
Environment
https://ee-1483.dp.appsmith.com
Issue video log
No response
Version
v1.9.20

As per discussion changing the priority to high, as it exits in the prod

@prapullac @btsgh This issue is intermittently occurring as the DP is intermittently pointing to production cloud-services url. And issue seems to be with how DP was generated. Right now I am not able to reproduce it even on DP

@sneha122: Closing the above issue as per the above comment and accepting the issue occurance is intermittent


Convert NRF based boards to use DT for LED & Buttons

Codecov Report

Merging #10388 into master will decrease coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #10388      +/-   ##
==========================================
- Coverage    52.9%   52.85%   -0.06%
==========================================
  Files         210      210
  Lines       25732    25732
  Branches     5672     5672
==========================================
- Hits        13614    13600      -14
- Misses       9802     9816      +14
  Partials     2316     2316

Impacted Files
Coverage Δ

lib/posix/clock.c
33.33% <0%> (-38.89%)
:arrow_down:

Continue to review full report at Codecov.

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


Override supplied transaction nonce in do_call

What was wrong?
If the user supplies a nonce other than 0, do_call with fail.
How was it fixed?
Add nonce to the do_call override parameters.
Cute Animal Picture

While writing tests, Im grasping why you (@pipermerriam ) didn't think do_call shoudnt be a vm state method.  Now, trying to include a json-rpc level concept in the core api is biting me with a circular reference.  I will move the functionality added with do_call into a helper function for use by the gas estimation.

The existing gas estimation test now covers the original problem with the transaction nonce: mixing the actual sender nonce with the dummy address.
These lines in the original do_call method made the non-zero nonce valid:
                if not hasattr(_transaction, "get_sender"):
                    _transaction.get_sender = \
                        lambda: to_bytes(hexstr=DEFAULT_DO_CALL_SENDER)
                    _transaction.sender = to_bytes(hexstr=DEFAULT_DO_CALL_SENDER)

The conditional has been removed so the sender is always replaced with the dummy address. Now the case is caught, validation will fail with the dummy sender mixed with the original sender nonce.

@dylanjw does this mean that msg.sender will always be 0x7760c6D8c0eA7A764F13fb5b034A574f59c1fdd4 during transaction execution?

@pipermerriam It would be the hardcoded address just during gas estimation.  its not ideal, because contract code that is conditional to the transaction sender will get wrong gas estimation results.
Saying that out loud, I realize thats a problem.  The dummy address and nonce should only be set in the case of unsigned transactions, where there is no sender address.  I'll make that change.

Saying that out loud, I realize thats a problem. The dummy address and nonce should only be set in the case of unsigned transactions, where there is no sender address. I'll make that change.

I think at the py-evm level, this should accept only signed transactions, or an explicit from override. At the trinity or eth-tester level, we can pick a default from address. Calls/gas-estimations etc should never run from a surprise sender.

Yeah, we need a different mechanism.  The sender needs to remain the same whether it's signed, or not.  Like @carver said, we can move the requirement to set a from address up to the trinity/eth-tester level.

At the py-evm level, an unsigned transaction has no defined sender.
This is the problem that im trying to overcome, which I dont think is solvable with the current py-evm api without overriding the sender at some point in the stack:

with a locally managed account you want to do a gas estimation prior to making a signed transaction in web3.
eth_estimateGas call is made to eth-tester.
eth-test builds a transaction to send to py-evm, on which to run gas estimation.  At this point, creating a signed transaction is impossible, because eth-tester does not have the key.  So the options are to override the sender, or to send the transaction on as an unsigned transaction (no sender).  There currently exists no way to pass the sender to py-evm except by signing a transaction.

The sender override is not ideal, in either py-evm or eth-tester.  I think ideally there would be a mechanism to run computations on a set of transaction parameters the can happen outside the normal signed transaction pathway.  I believe this is what geth does.  It takes the transaction parameters, creates a temporary state pre-funding the transaction senders address, and then runs the computation circumventing some of the normal transaction computation pre-steps.
What do you thin about bringing the spoof transaction object forward where is can totally replace the signed or unsigned transaction early enough to allow the real sender to be passed through to the gas estimation without the need for the key.  Im not sure how this would look.  Could SpoofTransaction be part of the api?

Could SpoofTransaction be part of the api?

Yes, but not explicitly. I think it's reasonable to use SpoofTransaction to build the transaction that's sent to estimate_gas here: https://github.com/ethereum/py-evm/blob/master/evm/chains/base.py#L502
It's supposed to be a drop-in replacement for a transaction, so the API shouldn't actually have to change.


Add native view config for {margin,padding}{block,inline} props

Summary:
The margin/padding props were introduced in this diff: D41267765
Changelog: [Internal]
Reviewed By: javache
Differential Revision: D56846578

Merged as https://github.com/facebook/react-native/commit/457372c87eaaf669e8569432b1c8d4f8a0ebdb57


.NET Standard 2.0 Support?

.Net Standard 2.0 has been finalized and available in VS 2017 with the last update. Any plans to release this great little DB with it for all platforms?

4.0.0 beta on nuget seems to be compatible with .Net standard. But plain Insert(object) gives exception that Bson Id cannot be null, I am using Insert(Guid.New(), myObject) that works fine.

Hi guys, v4 is NetStandard 1.3 compatible, but I will change to 2.0 before release final version. In NETStandard v2 FileStream.Lock is supported and it's much better than 1.3

@mbdavid Hi!
Please notice, that .Net Standard 2.0 is not supported in UWP min. target version older than 16299.
Is it possible to support 1.3 (or 1.4) with minimal functional for it?

LiteDB current v4 version works fine with netstandard 1.3 and 2.0.
https://github.com/mbdavid/LiteDB/blob/master/LiteDB/LiteDB.csproj#L60
Only v5 will need netstandard2


testing pull-request -o

body message

-o seems to simply open the recently created PR in the browser.


ValidatorDelegations not loading

Bug description

On opening the bigdipper website I saw that validator delegations were not loading, so I checked the network tab and saw that the response for the specific query had timed out .
Steps to reproduce

The bug can be clearly seen in the website for example check page (https://cosmos.bigdipper.live/validators/cosmosvaloper1udpsgkgyutgsglauk9vk9rs03a3skc62gup9ny) in the delegations tab
When I run the graphql query on my local instance on bdjuno I get the response

Expected behavior

The query should respond with the validator's delegation addresses and amounts

Was looking into this a little more, realised this is only a problem with cosmos , rest of the chains are working perfectly

After testing it's because of the count-total is making this query time-out. It should be fixed somehow on the frontend to disable count-total and implement another way for displaying next pages.
ref.  forbole/big-dipper-2.0-cosmos#1010


Implement Database Design to store user data after auth

working on it

https://lucid.app/lucidchart/50fb27e1-4aae-4e02-82cc-98392016f9fc/edit?viewport_loc=211%2C118%2C1975%2C671%2C5BKVUKC8m.QG&invitationId=inv_14f7eadd-74b5-4e26-9ea3-943c0419e393

Design is complete

Verified with Talend:
Am able to

Load User Data into the userpref index
Get User Data from index
Delete User Data from index

next step is to integrate this logic via api requests and using #107 #108


malloc: *** error for object: pointer being freed was not allocated

I'm getting the following error when connecting to redis from my Kitura project:
myFirstProject(78932,0x700000187000) malloc: *** error for object 0x7fb2fb602d50: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug

I get a response back from the request, however the server crashes after the request has been served. I think this has to do with the deinit of reds, but I am not sure how to debug.
Here's the code:
router.get("/visits", handler: {
    request, response, next in

    let redis = Redis()
    redis.connect("localhost", port: 6379, callback: { (error: NSError?) in
        if let error = error {
            Log.verbose(error.localizedDescription)
        } else {
            redis.incr("visits", by: 1, callback: { (visits: Int?, error: NSError?) in
                if let error = error {
                    Log.verbose(error.localizedDescription)
                } else {
                    if let visits = visits {
                        response.status(HttpStatusCode.OK).send("Visits: \(visits)")
                        next()
                    }
                }
            })
        }
    })
})

I now finally have solved this issue.
I removed our dependency on Hiredis and replaced it with a pure swift implementation of the REdis Serialization Protocol (RESP). This code is found in our develop branch. To use it you must:
1. Upgrade to the 05/03 drop of Swift
2. In your Package.swift file, update:
      - The minor of Kitura to13.
      - The minor of Kitura-redis to 13.
      - If present, the minor of HeliumLogger to 7.
     **Note:** You may have to update other dependencies as well, depending on what is in your Package.swift file

Do an rm -rf .build Kitura-Build Packages
Do a make run

Please note that the migration of Kitura and it's associated packages is still work in progress. Not all of the packages have been migrated yet.


storage ui staying open after round end happens again

Description
yes

storageuicontroller just needs to dump all the windows on IStateChanged / IStateExited.


DAF-4330: Notifications on Samsung Android 11 do not display thumbnails, and the seek bar is not working

Ticket: https://dw-ml-nfc.atlassian.net/browse/DAF-4330
Problem: Notifications on Samsung Android 11 do not display thumbnails, and the seek bar is not working
Solution:

I will load the image right during the setupNotificationParameter phase, and then place it into METADATA_KEY_ART. I will also include the duration from ExoPlayer for METADATA_KEY_DURATION to enable seekbar functionality.
Since the bitmap has already been loaded, I will store it in a singleton class and use it in the BetterPlayerNotificationService instead of reloading the image once again. I'm using a singleton instead of an intent because at times, a large bitmap could lead to a TransactionTooLargeException

@noboru-i pls review this PR, thanks 🙇


Outputs only so much text in its answer

Outputs only so much text in its answer, cuts off every time. How do I increase this? Better yet is there settings somewhere?

I related to the context size, in the coming release I will add an option to change the settings

Cli option added to change the config, checkout on the README


"Longest common prefix () is not accessible" on Windows

Which packages are impacted by your issue?
@graphql-codegen/cli
Describe the bug
On Windows, running graphql-codegen --watch prints this warning:
[Watcher] Longest common prefix () is not accessible
[Watcher] Watching current working directory (C:\Projects\oss\bugs\graphql-codegen-windows-repro\app) instead

This is problematic if your GraphQL schema file is outside of the directory in which graphql-codegen is run.
The issue does not occur on macOS or Linux.
Your Example Website or App
https://github.com/srmagura/graphql-codegen-windows-repro
Steps to Reproduce the Bug or Issue
See the README of the GitHub repository.
Expected behavior
No warnings when running graphql-codegen --watch.
Screenshots or Videos
No response
Platform

OS: Windows 11
NodeJS: 18.16.0
graphql version: 16.7.1
@graphql-codegen/* version(s): 4.0.1

Codegen Config File
schema: ../schema.gql
documents:
  - "src/**/*.ts?(x)"
  - "!src/gql/**/*"
generates:
  src/gql/:
    preset: client

Additional context
No response

Hey, can you please try this build, this better handles Windows paths for the watcher, but I need to verify if it solved it or not, I don't have a Windows machine with me.
<EMAIL_ADDRESS>

Thanks for looking into it! Unfortunately, I tried build 4.0.2-alpha-20230706143738-f59fb0497 and the behavior was unchanged.

do you get a different output or is it still the same?

Exact same output.

For anyone facing this issue, my solution was to pass the documents array of strings in a config file through this map:
.map((path) => path.replace(/\\/g, '\\'))

Basically, the problem was that Windows was setting path to be something like this:
C:\\Users\\username\\project\\some-path\\**\\*.ts

but the watcher thinks the path separator is just one \, so it ends up splitting the path wrong when trying to find the common parent.


h2/ready

fix unknown field in testing yaml due to camel case change (#933)
Track outbound connections (#939)
Bump rustls from 0.23.4 to 0.23.5 in /fuzz (#945)
Make socks5 optional, off by default (#943)
[release-1.22] Automated branching step 4 (#951)
Revert "[release-1.22] Automated branching step 4 (#951)" (#952)
metrics: Don't log 'hbone_target' as a string. (#946)
Automator: update common-files@master in istio/ztunnel@master (#955)
metrics: make traffic metrics faster (#940)
Pass original service over HBONE for debugging (#942)
metrics: add flag for deny by policy (#956)
Stop denying 15008 for sandwich case (#966)
test: run namespaced tests without root (#962)
Automator: update common-files@master in istio/ztunnel@master (#969)
rbac: log unknown policies for debugging purposes (#959)
Implement better "namespaced" tests (#970)
Test sandwich waypoints (#973)
Support running tests in docker (#977)
Verify workload consistency with CNI for outbound (#979)
admin: support setting log of a specific scope (#972)
Better-behaved HBONE pooling (#931)
Fix build for jemalloc feature (#980)
logging: disable regex (#987)
performance: reduce and test size of futures (#985)
pool: do not indefinitely leak timers (#992)
Replace hyper with direct h2 usage for outbound HBONE (#990)
h2: poll ready before using

PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

test_ztunnel_release-1.22
600b7f0b283747b93d34be182f55ebd965bc4b85
link
true
/test test

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


HTML conversion doesn't properly convert text that's center aligned

Thank you for writing this software! It's awesome.
When I convert something to HTML, stuff that is center aligned in the Google doc gets converted to left justified in the HTML. If it's right-justified in the Google doc, then it converts properly to HTML, but not center.
Is this intended behaviour, or is this a bug?
Thanks!

Also, a particular request, if you do fix this. The site I'm posting to doesn't seem to obey the  code, but it does obey . Would it be possible to have an option for center to work that way?

I am having the same issue. Centered text has no modification in the HTML conversion.

Sorry I missed this -- it should be possible, since there is a horizontal alignment attribute for paragraphs in Google Docs. I'm leaving a link to the docs for myself when I get to this: https://developers.google.com/apps-script/reference/document/attribute.
I do have a bit of time and I'm trying to fix a few of the outstanding bugs and maybe add some nice features as well.

I'm not sure what site you're posting to, but I'll probably implement this as <p style="text-align: center"> instead of using <center> tags.
Note: GitHub wiki doesn't seem to observe either tag: all the test paragraphs are left-justified.


Switch to Energinet.DataHub namespace

I personally wouldn't do this now. I would wait for a "very definitive" decision at the ART level before I would invest anything in this namespace change.


Split README.md into two files

README.md should contain a placeholder for description, a Quick Start section (as in Recipes), and a reference to HELP.md.
HELP.md should contain all information about directories structure, data manipulation, available commands, etc.

This change will make it easier to apply Cookiecutter template updates to the projects. Also, it will have the most relevant information in README.md, keeping it short.

closed by https://github.com/neuromation/cookiecutter-neuro-project/pull/345


WAT-838 | Feature | Refactor business hour component adding rules

:ticket: Jira WAT-838
Counterpart Classic
Go to talk PR
:memo:  Changes
Change 1:

“Opens” and “Closes” are placeholders and are disabled to prevent the possibility of making a selection.
When you select the opening time for the first time, the closing time is automatically set 9 hours later.
When you select the closing time for the first time, the opening time is automatically set 9 hours earlier.
After the initial selection, you can freely choose the time for each selector.
If you need to set additional hours for the same date, the new opening time will start immediately after the closing time of the previous selector.

Holding this merge until the release


Update documentation?

The readme says

Grab python 2.7.x (this app is not compatible with python 3.4.x)

I notice 3 support was added in https://github.com/octohub/GroupMeAnalytics/commit/3372f1a9083e53587a5df4debea277f327b2bf24
I just lost a good chunk of time hitting errors trying to run it in 2.7, I should of noticed it was written in 3 though honestly, but updating that line of the readme should help others not be a dummy like me :P
Edit: Sorry I just noticed this is sorta a duplicate of #7

This is much more specific than #7. I will make a pull request to fix this.

Fixed.


[23.05] bitwarden: 2023.4.0 -> 2023.9.3

Description of changes
as requested in https://github.com/NixOS/nixpkgs/pull/262797#issuecomment-1784944113
depends on https://github.com/NixOS/nixpkgs/pull/242266

Things done

Built on platform(s)

[x] 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/)
23.11 Release Notes (or backporting 23.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

[x] Fits CONTRIBUTING.md.

cc @luftmensch-luftmensch @mariomarin
closes closes https://github.com/NixOS/nixpkgs/pull/264492

Can someone with a 23.05 system confirm this works?

Can someone with a 23.05 system confirm this works?

Tested out, and it works as expected


python311Packages.service-identity: 21.1.0 -> 23.1.0

Diff: https://github.com/pyca/service-identity/compare/refs/tags/21.1.0...23.1.0
Changelog: https://github.com/pyca/service-identity/releases/tag/23.1.0
Description of changes

Things done

Built on platform(s)

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

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

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

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

@ofborg build python311Packages.autobahn python311Packages.scrapy python311Packages.trustme python311Packages.twisted

Included in #244135


Add save draft redirect and gone items

This commit allows us to create draft redirect and gone items. This requirement has come to light whilst migrating the HtmlAttachment (HtmlPublication) format. This format does not have draft functionality as such but is attached to formats that do.
When deleting an HtmlAttachment from a draft Edition that has been previously published we need to save a redirect to the draft content store so that it can be published with the Edition and the redirect activated.
This is a step towards that functionality.
Trello

Looks reasonable to me, but worth getting a second opinion from someone who isn't working on this story.

:+1:


Auth per connection

It would be cool if we could specify different auth options per connection. What do you think about making the auth option optionally take a function that takes the client index and a sender boolean?
const instance = anger({
  ...
  auth: (i, sender) => {

    return { headers: { ... } }
  },
  ...
})

👍 ,
I'll just do auth: (sender, i) => , just because it fits with forEach.


Hide the 'explore' button when not enabled for a particular database

Summary of Changes
Include a summary of changes then remove this line
Tests
What tests did you add or modify and why? If no tests were added or modified, explain why. Remove this line
Documentation
What documentation did you add or modify and why? Add any relevant links then remove this line
CheckList
Make sure you have checked all steps below to ensure a timely review.

[ ] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[ ] PR includes a summary of changes, including screenshots of any UI changes.
[ ] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[ ] In case of new functionality, my PR adds documentation that describes how to use it.

All the public python functions and the classes in the PR contain docstrings that explain what it does

[ ] PR passes all tests documented in the developer guide

Codecov Report

Merging #366 into master will decrease coverage by 0.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #366      +/-   ##
==========================================
- Coverage   76.19%   76.18%   -0.02%
==========================================
  Files         167      167
  Lines        4147     4148       +1
  Branches      525      525
==========================================
  Hits         3160     3160
- Misses        950      951       +1
  Partials       37       37

Impacted Files
Coverage Δ

.../js/components/TableDetail/ExploreButton/index.tsx
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Codecov Report

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

@@            Coverage Diff             @@
##           master     #366      +/-   ##
==========================================
+ Coverage   75.38%   75.81%   +0.43%
==========================================
  Files         168      168
  Lines        4208     4210       +2
  Branches      522      522
==========================================
+ Hits         3172     3192      +20
+ Misses       1000      982      -18
  Partials       36       36

Impacted Files
Coverage Δ

.../js/components/TableDetail/ExploreButton/index.tsx
100.00% <0.00%> (+100.00%)
:arrow_up:

...sen_application/static/js/config/config-default.ts
75.00% <0.00%> (+25.00%)
:arrow_up:

Continue to review full report at Codecov.

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

Codecov Report

Merging #366 into master will increase coverage by 0.43%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #366      +/-   ##
==========================================
+ Coverage   75.41%   75.85%   +0.43%
==========================================
  Files         169      169
  Lines        4227     4229       +2
  Branches      526      526
==========================================
+ Hits         3188     3208      +20
+ Misses       1003      985      -18
  Partials       36       36

Impacted Files
Coverage Δ

...ndsen_application/static/js/config/config-utils.ts
100% <100%> (ø)
:arrow_up:

.../js/components/TableDetail/ExploreButton/index.tsx
100% <100%> (+100%)
:arrow_up:

...sen_application/static/js/config/config-default.ts
75% <0%> (+25%)
:arrow_up:

Continue to review full report at Codecov.

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

Why is codecov commenting through my account on this repo?!


vsix file is not reproducible

The .vsix file generated by vsce package contains timestamps that prevent it from being easily reproducible. It looks like everything inside the zip is reproducible, so the vsix file itself is likely the only issue. I believe all the daffodil and daffodil-sbt releases are reproducible, so this is the last remaining piece that when fixed will allow us to switch to tag/CI based automated release building/signing, which should make the release process significantly easier.
I've done some digging and it looks like the issue is vsce includes the mtimes of the files in the zip/vsix file.
I've tried adding a new script in build/yarn-scripts.ts that is run just before we package the vsix file to change all the timestamps to SOURCE_DATE_EPOCH if defined. This works for most files included in the vsix file, but there are a couple that vsce generates during the package process that I don't think we can modify like that. So this likely is not a complete solution.
Another option is to create a PR to vscode-vsce to update it to use SOURCE_DATE_EPOCH when creating the vsix. I've skimmed vscode-vsce and think it could probably done with just a few lines, but I'm not all that familiar with node.js or how to test those kinds of changes. Also, even if we did make the changes, it requires getting a PR merged and updating the dependency to it. The first is probably doable, but daffodil-vscode depends on a pretty old version of vscode-vsce--is there anything blocking us from updating to a newer version if one were released with this kind of fix?
An alternative approach might be to just add a post processing script that unzips the contexts of the vsix file to a temp directory, modifies all the timestamps to SOURCE_DATE_EPOCH, and then rezips it. That's a bit of a pain, but doesn't have any dependency concerns.

For reference, this patch to vscode-vsce seems to fix it so it can create reproducible zips by sorting the files and using SOURCE_DATE_EPOCH if defined:
diff --git a/src/package.ts b/src/package.ts
index d27b71c..9416b45 100644
--- a/src/package.ts
+++ b/src/package.ts
@@ -1800,13 +1800,21 @@ function writeVsix(files: IFile[], packagePath: string): Promise<void> {
 			() =>
 				new Promise((c, e) => {
 					const zip = new yazl.ZipFile();
-					files.forEach(f =>
+
+					const sde = process.env.SOURCE_DATE_EPOCH;
+					const epoch = sde ? parseInt(sde) : undefined;
+					const mtime = epoch ? new Date(epoch * 1000) : undefined;
+
+					files.sort((a, b) => a.path.localeCompare(b.path)).forEach(f => {
+						let options = {
+							mode: f.mode,
+						} as any;
+						if (mtime) options.mtime = mtime;
+
 						isInMemoryFile(f)
-							? zip.addBuffer(typeof f.contents === 'string' ? Buffer.from(f.contents, 'utf8') : f.contents, f.path, {
-								mode: f.mode,
-							})
-							: zip.addFile(f.localPath, f.path, { mode: f.mode })
-					);
+							? zip.addBuffer(typeof f.contents === 'string' ? Buffer.from(f.contents, 'utf8') : f.contents, f.path, options)
+							: zip.addFile(f.localPath, f.path, options)
+					});
 					zip.end();

 					const zipStream = fs.createWriteStream(packagePath);

I imagine there's a cleaner syntax to deal with the undefined stuff, but otherwise this seems fairly straightfoward and maybe something vscode-vsce would be willing to accept.
I think the question is if we did try to upstream this to vscode-vsce, would daffodil-vscode be able to update to the newer version, or is there a reason we need to stick with an older version.

@stevedlawrence I don't think there is necessarily a reason for not upgrading vsce other than possibly needing to update other dependencies in order for it to work? I just tested running yarn package with the latest version of vsce and it seemed to build fine. So this might be a good PR to add to the vscode-vsce repository

Thanks for looking into this @stevedlawrence, and I think regardless what we decide for this project, it's worth opening an upstream PR for vscode-vsce as there is certainly value to be had in terms of maintaining reproducibility for projects beyond Daffodil.
As for us upgrading to a newer version... what we need to consider is how it affects our minimum supported version of VSCode.  Now that 1.4.0 has been released, we can start to take a look at where we need to be in terms of minimum requirements for Node, Java/Scala, and VSCode.  This is a handy reference for Node <-> VSCode https://github.com/ewanharris/vscode-versions requirements.
In the meantime, the unpack and repack of the .vsix, while a pain, is something in our immediate realm of control, with little risk, and gets us the reproducibility property that we're seeking.

@stevedlawrence The syntax and way you went about the change looks fine to me. Feel free to open a PR to the vscode-vsce repo with your changes, I can also do this based on your decision, just let me know.

@shanedell does the .vsix still work fine on VSCode 1.82.0, our minimum required version?  That's my concern.  We want to be able to support about a year's worth of VSCode releases.
Ref: https://github.com/apache/daffodil-vscode/wiki/Apache-Daffodil™-Extension-for-Visual-Studio-Code:-v1.4.0#prerequisites

I've created a PR to update vscode-vsce: https://github.com/microsoft/vscode-vsce/pull/1100
I did notice vscode-vsce README says they require Node.js 20+. I don't know if you're also trying to maintain support for older versions of nodejs, or if vsce really does require a newer version of node or if that's just all they officially support.
Also, I built a vsix with the the current vcse 2.2.0 dependency and with the latest version with my patch, and contents were basically the same. The only functional difference that I see is the new extension.vsixmanifest file adds these two new properties:
<Property Id="Microsoft.VisualStudio.Code.EnabledApiProposals" Value="" />
<Property Id="Microsoft.VisualStudio.Code.ExecutesCode" Value="true" />

I imagine older versions of vscode would just ignore these if they don't support them.
One side note is that org.apache.daffodil.daffodil-debugger-1.4.0.jar is not exactly the same in the two .vsix files I built, so there might be another source of non-reproducibility to investigate. I don't think I saw that in previous tests, so it might not be as simple as a timestamp.

Just a little more investigation, the differences in the org.apache.daffodil.daffodil-debugger-1.4.0.jar are in the JAXB generated classes (e.g. tdml/DFDLBaseType, tdml/DFDLChoiceType, etc.). Disassembling and diffing those .class files shows they have the same members and methods, but defined in a different order. I guess JAXB output is not entirely deterministic? This sounds familiar but I thought that was fixed?

The change to VSCode has been merged, looks like it will be in the next 3.2.2 release. I think it's still TBD whether or not newer versions of VSCode and its dependencies (e.g. node.js >= 20) breaks minimum version support.


Deployment does not work

Somehow the build module does not find the pyproject.toml file.

This is related to #2

As of this commit MuviMaker is pip installable.
Do pip install muvimaker


Add logo to emails

Try both banner and logo

I was able to add the image but it is also displayed as an attachment and creates issues with caltech spam filters - I'm unable to send emails with images to my caltech account. I think that we should revisit the idea of adding the logo to emails.

Sounds good. We can discuss this tomorrow

Are you sending the emails as html with the image in an  pointing to the URL of the image ?  I haven't used the gmail api much, so I don't know what's possible.  Previously sending through sendmail, I think one could send emails as html and then nothing would be an attachment.  I realize you wouldn't want to send through sendmail though.

I'm sending the email as html with the image embedded. I read the file from python and add it as a mime image. I think that the way it is displayed depends on the client and with gmail it is displayed both in the email body and as an attachment. There's also the issue that caltech servers are blocking the message, maybe temporarily but it means that there may be more rules for emails with images and I think it's more important to reach the authors and avoid spam filters than having the image in all emails but with the risk of being blocked

If it's always the same image, could just hotlink it to the URL instead of mime attaching it ?  I guess that wouldn't look good if they view the email without internet connection ?  I agree on prioritizing reaching authors, I don't have a stake on this, just wondering technical things.  Thanks.

Thanks @azurebrd I haven't thought of adding the image as html. It works, and in this way caltech email server is not blocking the messages!

I deployed the version with the logo to dev but I can switch to the banner depending on what @draciti and @vanaukenk prefer

Pasting the email here for discussion

all agree banner is better, need to replace with  a smaller one after talking to shannon


Document how to use Docker images to self-host GraphQL Hive

#311

Any update on the documentation? Thanks in advance for looking into this.

@usama-gyg 😉

Hi! Is there any estimate date when this would be released?

Today :)

I am sorry for disturbing, but where can I find the guide for self-hosted solution that is on your screenshot? It is not here. Or it is not released yet?

We had to revert something but now it's back, check again.

@SpeedyGonzaless Here you go:

Docs: https://docs.graphql-hive.com/self-hosting/get-started
Blogpost: https://the-guild.dev/blog/announcing-self-hosted-graphql-hive


Google Drive URL: [70608200] Unable to retrieve name for external entry of type ExternalUrl

I've noticed an issue with downloading certain Google Drive URLs which are too large for Google to scan for viruses, do not download with the following error:
[70608200] Unable to retrieve name for external entry of type ExternalUrl:
(Apologies, rather not post the URL as they're from a NSFW Patreon user I subscribe to, happy to email a link.)
I've tested a couple of Drive links, one which works and one which doesn't work, the links are in the same style, the only difference seems to be that when you open the link the Google says "Google Drive can't scan this file for viruses. Download anyway?". Smaller sized files will go straight through to the download immediately.
The link is to a 500MB+ ZIP file.

I see that there's quite a few Stack Overflow questions on this, one person has suggested using:
https://www.googleapis.com/drive/v3/files/fileid/?key=yourapikey&alt=media
Instead of "yourapikey" the authorisation header should be possible. I've tried this manually and it appears to work, with the only caveat being that it doesn't keep the original filename, using "download.{extension}" instead.

This really looks to me like the file is not being passed to google drive plugin. Please send json files produced when you run the app with --json parameter and link(s) you are having issues with to<EMAIL_ADDRESS>I will take a look when I have free time.

No worries! Sent along now, thanks for taking a look!


The thing with abstracted away promises

Because the async nature is not encoded in the type system, you never know if you compose something if the effect has any async code. It would not be a problem if it was not relevant for you. But when you want to run the effect, it does matter and using runSync on async will blow up at runtime.
Sure, you could just drop it and always runPromise, because await 4 works as await Promise.resolve(4) but that requires you to bring the scope into async making it promise itself. So not really a solution.
What is the reasoning behind not having the async nature in the type system like fp-ts? IMO this makes you NEED to know internals of everything you compose, in order to"run" it properly. My concern in the library is simply that it tries to pack all in Effect to streamline it, so that you do not have to explicitly transfer (lift) between the worlds, but that removes information which is one of the key points of such a library when you describe a program.

I'm pretty sure that the return type of the effect will represent the async nature.
e.g. if you return a promise from an Effect creating function then the type signature will be:
Effect.Effect<never, never, Promise<number>>
I personally adding an API to the library to represent async functionality is redundant and will make the library unnecessarily verbose. Effect is not a functional programming library and it isn't advertised to be. Its a library to add composability to a JS code base.
Watch this video for more details https://www.youtube.com/watch?v=zrNr3JVUc8I, and if you want a more strict functional library than use fp-ts.

You are talking about a different thing. Example:
https://www.effect.website/docs/essentials/creating#effecttrypromise
Promise not encoded in type system, yet try run it sync -> runtime error.

We had tried a few different options to track the Async Effect, in reality they all lead to worst DX without actually being safe. Namely even a fully Sync type should support a fromCallback combinator to enable usage with APIs that implement CPS, if such function exist it is impossible at the type level to assert that such function is called immediately and not deferred. So at the end we decided that the price of tracking (lack of composability) together with the inherent lack of safety (if Sync has to be complete it can't be safe) we decided that it isn't worth having separated types.
Notice that in general one should only run Effect at the edges of your app, in an app that uses Effect for everything that is a single call to the main effect and in such case the best way to run is directly using runFork, sync execution is a special case that is needed in environments where async execution is impossible and should be considered an edge case, i.e. use runPromise/runFork when you can, use runSync when you really have to.

I understand. Thank for you reply.
I've did some experimentation and realized, due to the nature of Promises in JS its hard to really ensure handling them properly, regardless whether you try to make them explicit in the type or not. Any attempt to tackle it leads to unnecessary calls required to ensure it was not left unhandled or it leaves open holes and hence does not remove the unsafe feeling of "is it actually safe to run or not".
I think its simply a natural limitation and manifests itself in different forms, no matter how you try to move it.
I guess I'll close this one then. In case there is any reason to leave this open, just reopen.
Thank you.


merge from arlac77/npm-package-template-esm-only

package.json

chore(package<EMAIL_ADDRESS>chore(scripts): cover@#overwrite c8 -x 'tests/**/*.mjs' --temp-directory build/tmp ava && c8 report -r lcov -o build/coverage --temp-directory build/tmp

Coverage remained the same at 85.96% when pulling 26f477d4efacc6f8a7541bc282c2083830633452 on npm-template-sync/1 into 0f3d58a7d9e0c180e7e9b090d35a8c2c2efc8f18 on master.

Codecov Report

Merging #586 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #586   +/-   ##
=======================================
  Coverage   84.51%   84.51%
=======================================
  Files           3        3
  Lines         891      891
  Branches       62       62
=======================================
  Hits          753      753
  Misses        138      138

Continue to review full report at Codecov.

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

:tada: This PR is included in version 3.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add Read-Only handling and Silent parameter

Adds readonly and opposing writable API methods and handling.
Adds second silent boolean parameter to API methods.

+1

+1

Does readonly attribute works? seems it has no effect:
<input type="checkbox" data-toggle="toggle" readonly="readonly" />


Preview without audio

When I start a session for the first time, it shows a dialog asking the user for a microphone permission. I do not want the microphone to be used and have audio processed, all I want is a camera preview. How can I disable the audio recording?
Thanks

Hum, it's actually not difficult at all to mute the sound for a video. since the video, and the sound, are written independently. I need to add a property like :
public var sound: Bool = true {
  didSet {
     //do stuff here.
  }
}

I will add the feature.

Actually, that is not what I meant. It's actually requesting permission to use the microphone the first time I open my app. I don't need that permission.

+1
I encountered the same issue/feature at first time open my app. The app crashes at second launch, if I cancel the mic permission.


Use a free port for fable daemon

Avoid things breaking up when other projects are building or being watched at the same time

It's actually where I need it. I had an other VSCode watching some other project & it stopped this one from building.
Don't understand why it isn't the default.
I also disable the task that kill dotnet in this build.fsx, with more and more things using dotnet it's not so great...


dataset

The pointclond looks good,looking forward to your page:Make-Your-Active-Data.

The project Make-Your-Active-Data will be opened in a while.


fix: id param in fetch method should be number|string

This is when someone for example uses UUID rather than Integer. I think docs, are mentioning that just code wasn't align with it.

@rolandjitsu fixed. Thanks for review 👍

The package is published on NPM now.

@rolandjitsu awesome! Thanks!


Find or create with non-unique fields (findFirstOrCreate or upsertFirst)

Problem

Most of the time upsert covers this use case, but if you need to find by a non-unique field, you can't use upsert.
This is similar to the difference between findFirst vs. findUnique.
Suggested solution

Alternatives

Additional context
One additional consideration is a composite unique may solve your problem, then you can use upsert again.
Reference issue: https://github.com/prisma/docs/issues/640

bumping 😊 please don't forget this feature

Note for future reference: While upsert already allows emulating findUniqueOrCreate, it forces the use of at least one unique criterion. There are cases where you might want to find or create a record without the use of a unique criteria. eg:
model User {
  id Int @id @default(autoincrement())
  name String
}

await prisma.user.findFirstOrCreate({ where: { name: "Prisma" } })

or
await prisma.user.upsertFirst({ where: { name: "Prisma" }, update: {}, create: { name :"Prisma" } })

Bump.. this feature is definitely required

Has anyone found a workaround for upsertFirst (when the properties to be searches for aren't unique)? I only came up with solutions across multiple queries (find an id + upsert on that id), which produces pretty bad results in some scenarios:

find a document id that matches the query
Change the content of that document inbetween so it doesn't fit the query anymore
upsert a document that has that id and fits the query
upsert creates a new document, even though there probably are more documents fitting the initial query.

I have no more ideas on how to stay inside the prisma world with this pretty easy scenario.

bump

ran into same issue where upsert wih non-unique where condition doesn't work and there is no alternative otehr than 2 queries.


feat: Create versioned documentation pages

Will require a reorg of the gh-pages branch to work correctly.
This is still in draft as there are design questions around the versioning dropdown. Here's how it looks like now

@melissawm here's my thoughts on what designn might look like:

reduce the size of the version name in the nav, and make it gray so it doesnt compete with the content
if you can, have dropdown below the selector (not important to do this though)
Consider giving versions a comparable name or number and labeling "latest" or "stable" as extra context

Design link: https://www.figma.com/design/3yyR5H3PRJjWVeE4U4rkPr/Doc-Site---Version-Dropdown?node-id=2-4993&t=1RHey8VcOA36OilJ-1


Throw warning if we can't find condor_chirp

Impact of the bug
Things like cmsRun exitcode won't be set as a condor job classad, hence won't be present in ElasticSearch.
We set different things in the cmssw executor here
But if can't find condor_chirp, we simply do nothing.
Describe the bug
If condor_chirp is not present, we don't throw any errors or warnings here:
https://github.com/dmwm/WMCore/blob/master/src/python/WMCore/WMSpec/Steps/Executor.py#L193-L197
It seems GlideinWMS has recently (1 week ago) started to use a new implementation to provide singularity support at the Submission Infrastucture level, and this has broken condor_chirp, which can't be found in the environment anymore.
How to reproduce it
Inject a CMSSW workflow and after it has finished, look for Chirp classads. If not found, chirp didn't do anything. Example:
[khurtado@vocms0290 /data/khurtado/chirp]$ condor_history cmst1 -limit 5
 ID     OWNER          SUBMITTED   RUN_TIME     ST COMPLETED   CMD
 106.158 cmst1           5/5  00:10   0+22:01:07 C   5/5  22:19 /data/srv/wmagent/v1.3.3.patch3/sw/slc7_amd64_gcc630/cms/wmagent/1.3.3.patch3/etc/submit.sh amaltaro_TaskChain_Nano
 106.181 cmst1           5/5  00:10   0+20:31:17 C   5/5  20:53 /data/srv/wmagent/v1.3.3.patch3/sw/slc7_amd64_gcc630/cms/wmagent/1.3.3.patch3/etc/submit.sh amaltaro_TaskChain_Nano
 106.182 cmst1           5/5  00:10   0+20:07:36 C   5/5  20:31 /data/srv/wmagent/v1.3.3.patch3/sw/slc7_amd64_gcc630/cms/wmagent/1.3.3.patch3/etc/submit.sh amaltaro_TaskChain_Nano
 179.0   cmst1           5/5  17:52   0+00:00:24 C   5/5  17:58 /data/srv/wmagent/v1.3.3.patch3/sw/slc7_amd64_gcc630/cms/wmagent/1.3.3.patch3/etc/submit.sh amaltaro_TaskChain_Nano
 178.0   cmst1           5/5  15:21   0+02:23:56 C   5/5  17:48 /data/srv/wmagent/v1.3.3.patch3/sw/slc7_amd64_gcc630/cms/wmagent/1.3.3.patch3/etc/submit.sh amaltaro_TaskChain_Nano
[khurtado@vocms0290 /data/khurtado/chirp]$ condor_history 106.158 -l | grep -i Chirp
[khurtado@vocms0290 /data/khurtado/chirp]$

Expected behavior
We should probably not abort the job, but at least print some warnings in the logfiles so that we can spot this issue.
Additional context and error message
Besides condor locally, you can also compare JSON documents from ES from current dates vs older dates when Chirp classads were present
** Update **
Current central chirp issue has been issued a hotfix here:
https://cdcvs.fnal.gov/redmine/issues/24381

Note most sites don't find condor_chirp, but T1_US_FNAL is an exception.

@amaltaro Regarding this, I have created a grafana plot that shows the impact:
https://monit-grafana.cern.ch/d/ljWo3r6Zz/wmcore-chirp_wmcore_cmsrun1_exitcode?orgId=11
This is assuming all WMAgent jobs should always create the chirp_wmcore_cmsrun1_exitcode classad via chirp though, which seems to be a close enough assumption, looking at the plots before the issues started on 04/29.
As of today at least, I do not see any improvement yet, but maybe that's because the hotfix is recent, the pilots need to update and our jobs take long?


Height Control Method

Hi,
In your calendar's tutorial, there is an option to control the width of the Calendar but there isn't any option to control the height of the calendar. I tried a lot to control the height with CSS but it doesn't seem to work at all. Could you please tell the way in which I could adjust the height along with width of the calendar.
Thank You

Hi,
there is no defined height for the calendar, it's too tricky to calculate height for each cell with a defined height on the global calendar.
You can play with padding on L.57 of the css file :
.picker-top-row, .picker-day {
  padding: 10px 0;
}

If you want to only change day cells, define in your css file :
.picker-day {
  padding: 10px 0;
}


Error when running: now domains rm domain.com

When running now domains rm yourdomain.com, I get following error:
tima@tima-HP:~$ now domains rm findharbor.com
> The following domain will be removed permanently
  findharbor.com      331d ago
> Warning! This domain's 1 alias will be removed. Run `now alias ls` to list them.
> Warning! This domain's 4 certificates will be removed. Run `now cert ls` to list them.
> Are you sure? [y/N] y
> Success! Domain findharbor.com removed [2s]
> Error! An unexpected error occurred!
  Error: unexpected end of file
    at Zlib.zlibOnError [as onerror] (zlib.js:133:17) Error: unexpected end of file
    at Zlib.zlibOnError [as onerror] (zlib.js:133:17)

According to Zeit dashboard, domain gets successfully removed, yet this error is still confusing.

This is fixed now!


Transaction signing

Closes: #47
Description
This PR includes the logic to sign Tx. Currently there is logic to sign a MsgConnectionOpenInit against a gaia stargate-4 chain.
Will open this PR as a draft because even though the code works there's a few things to be worked on (bugs, tests) but it's easier to track through a PR than on the issue.

For contributor use:

[ ] Updated the Unreleased section of CHANGELOG.md with the issue.
[ ] If applicable: Unit tests written, added test to CI.
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Updated relevant documentation (docs/) and code comments.
[ ] Re-reviewed Files changed in the Github PR explorer.

Tests are failing because there's an issue with the way the signer is specified on tests. In the transaction signing of the raw message (proto) the signer is the bech32 account address.

Codecov Report

Merging #345 into master will increase coverage by 21.4%.
The diff coverage is 64.5%.

@@            Coverage Diff            @@
##           master    #345      +/-   ##
=========================================
+ Coverage    13.6%   35.0%   +21.4%
=========================================
  Files          69     137      +68
  Lines        3752    8582    +4830
  Branches     1374    2964    +1590
=========================================
+ Hits          513    3012    +2499
- Misses       2618    5380    +2762
+ Partials      621     190     -431

Impacted Files
Coverage Δ

modules/src/events.rs
0.0% <0.0%> (ø)

modules/src/ics02_client/events.rs
0.0% <ø> (ø)

modules/src/ics02_client/raw.rs
0.0% <0.0%> (ø)

modules/src/ics03_connection/error.rs
13.6% <0.0%> (-19.7%)
:arrow_down:

modules/src/ics04_channel/error.rs
75.0% <ø> (+50.0%)
:arrow_up:

modules/src/ics04_channel/packet.rs
0.0% <0.0%> (ø)

modules/src/ics07_tendermint/client_def.rs
0.0% <0.0%> (ø)

modules/src/ics07_tendermint/error.rs
75.0% <ø> (+75.0%)
:arrow_up:

modules/src/ics18_relayer/error.rs
0.0% <0.0%> (ø)

modules/src/ics26_routing/msgs.rs
0.0% <0.0%> (ø)

... and 254 more

Continue to review full report at Codecov.

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

I believe we discussed most of the reviews on this draft PR and should be good for Review. Some of the discussions will lead into other issues/features that are outside the scope of this PR for now.


Using this on codeigniter + grocery crud with bootstrap theme

Hello, I've loaded all the scripts and css files, but the select combobox is still works as normal... What can I do?

Hi there, is this still an issue? if so please include the code and I'll have a look, thanks


python310Packages.optimum: init at 1.11.1

Description of changes
🚀 Accelerate training and inference of 🤗 Transformers and 🤗 Diffusers with easy to use hardware optimization tools
https://github.com/huggingface/optimum
This is required by openllm.
cc @happysalada

Things done

Built on platform(s)

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

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

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

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 249114 run on x86_64-linux 1

4 packages built:

python310Packages.optimum
python310Packages.optimum.dist
python311Packages.optimum
python311Packages.optimum.dist


CSIRO Causal Network Def and Dataset

@nicholascar : Hold this over to next control body training, or do it now?

This has been approved by the Control Body so now that tests pass, it can be merged

True, but not an answer to my question.
I'll answer it myself: "Do it now."

Deployed.


RecordNotFound not working

`cePivots := []m.CustomerEventPivot{}
if err := gorm.Where("event_id = ?", eventId).Where("registered_time IS NOT NULL").Where("preferences IS NOT NULL").Find(&cePivots).Error; err != nil {
	if err == g.RecordNotFound {

`
I run a query which should return RecordNotFound error.
For some reason it doesn't, hence I must check if the len(cePivots) is 0.
is this a bug?

RecordNotFound error will only raise when find with struct, but not slice. it is an expected behaviour


DRAFT: GEODE-4187: Fix PersistentColocatedPartitionedRegionDistributedTest

Flakiness was fixed by:

clean up messy uses of AsyncInvocation
replace uses of Thread.sleep with Mockito.verify using timeout()
Use GeodeAwaitility timeout for all timeouts

High level changes to tests and product code:

Rename PersistentColocatedPartitionedRegionDUnitTest to
PersistentColocatedPartitionedRegionDistributedTest
Extract single-JVM tests to colocation integration tests
(ModifyColocationIntegrationTest, PersistentColocationIntegrationTest)
Move ColocationLogger to internal.cache.partitioned.colocation package
Extract factory and interfaces from ColocationLogger
Create unit tests for ColocationLogger and factory
Pass ColocationLoggerFactory into PartitionedRegion constructor
Use ColocationLogger via interfaces instead of implementations
Clean up PartitionedRegionTest (unit test)
Clean up colocation IllegalStateException message
Add getLogger(Class) to LogService

Update PersistentColocatedPartitionedRegionDistributedTest:

Make the code readable and understandable
Update to non-deprecated APIs
Inline super-class and lots of methods
Use TemporaryFolder Rule for all files
Use RestoreSystemProperties Rule instead of finally blocks
Replace MockAppender with cleaner inlined use of Mockito
Clean up usages of AsyncInvocation
Replace messy try-catch blocks with AssertJ catchThrowable
Throw failures and unexpected exceptions instead of catching them to invoke fail
Use descriptive variable and method names
Replace use of Admin API for shutdown with Cache.close()
Use lambdas instead of SerializableRunnable variables
Use lambdas instead of lots of tiny inner-classes
Use tearDown instead of try-finally blocks
Reimplement broken waits with Awaitility

ModifyColocationIntegrationTest is flaky because of the hardcoded 2-second sleeps. These need to be replaced by some more deterministic approach to detecting when the Cache and System are completely closed.

ModifyColocationIntegrationTest is fixed.

DistributedTestOpenJDK11 PASSED but seems to have hung during archival.

DistributedTestOpenJDK11 had one failure in ClientDataAuthorizationUsingLegacySecurityWithFailoverDUnitTest involving client-server protocol -- unrelated to this PR.


VAE reparameterization randomness

The example VAE does not inject randomness into the reparameterization during training.

Fix is provided in this #789 merge request.


unHover doesn't work anymore with aframe master and GearVR

See my comments on https://github.com/aframevr/aframe/pull/3126/files#r143173528
Let's continue the discussion here.

The onHit listener will break too once https://github.com/aframevr/aframe/pull/3125 is merged.

Ok, so https://github.com/aframevr/aframe/pull/3125 will not break super-hands after all, they manage to keep the api.
For unHover/unWatch, the function will need to be adapted to use clearedEls property on the event, see
https://github.com/aframevr/aframe/pull/3128

@wmurphyrd I did https://github.com/wmurphyrd/aframe-super-hands-component/pull/80
It should be the only changes required to work for next version of aframe (0.8.0). It works well with current aframe master and GearVR.
This means once the PR is merged, that the next release of super-hands will only be compatible with aframe 0.8.0 for GearVR/Daydream.


Echidna publication with images broken

Trying to bisect this...

failed run with latest build
successful run published with bf3136d31f2a87677999ff304772d73833896ddc
failed run with 6c2c66e56c99fcf6565bd519828ebfcdafd0f231
successful run with a199ec99ba0a0fd53695476aa6fe58e280f82617
successful run with 0fe3edbd9b38d5275e0027ec435752291bf3c4f0
failed run with 30dede717a52c1142c2ec8ae48509d6533440a4a
failed tarfile build with 4961a98f64f2a1ba42c232fda28a86d7efdddcc4

Offending commits seem to be the last two. The last successfully publishing commit was 0fe3edbd9b38d5275e0027ec435752291bf3c4f0.

(I'm really confused because I know I thought I published css-pseudo-4 with an up-to-date Bikeshed yesterday, but maybe I was working with an old copy?)

Hm, my relative-path code must be screwing up here. I'll see what's going on.


CDO and NCL not working at DKRZ after recent environment update

NCL and CDO do not work anymore after the recent environment update.
NCL returns:
ncl: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory

CDO returns:
cdo: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory

As a workaround, I manually load the local modules for NCL and CDO instead of using the conda versions.

With
ldd `which ncl`
you get all the shared libs  of the ncl command
In the current incarnation of the environment it shows:
libcrypto.so.1.0.0 => not found
At DKRZ there is a more modern version of this library installed.
If you want a q&d fix you can:
mkdir <MY_LIB_FOLDER> && cd <MY_LIB_FOLDER>
ln -s /lib64/libcrypt.so.1 libcrypto.so.1.0.0
export LD_LIBRARY_PATH=<MY_LIB_FOLDER>:$LD_LIBRARY_PATH

However, I would say the ncl conda package is broken for us.

This is getting nasty: using the NCL from the local module strange errors are occurring.
Apparently NCL cannot recognize color strings anymore (potentially affecting all diagnostic scripts!)
For example a simple script like this:
begin
  wks = gsn_open_wks("ps", "test")
  xx = ispan(1, 10, 1)
  yy = ispan(1, 20, 2)
  res = True
  res@gsnDraw = False
  res@gsnFrame = False
  plot = gsn_csm_xy(wks, xx, yy, res)
  resL = True
  resL@gsLineColor = "LightGray"
  dum = gsn_add_polyline(wks, plot, (/2, 5/), (/3, 6/), resL)
  draw(plot)
  frame(wks)
end

returns:
fatal:CvtStringToColorIndex: Unable to convert string "LightGray" to requested type
warning:Error retrieving resource gsLineColor from args - Ignoring Arg

The same script works on another machine with NCL 6.5.0.
The problem occurs also when deactivating the esmvaltool environment.
I also do not know whether the problem with conda and this error are related.

having a look at it right now, guys :radio:

Hey guys, I have not updated the envrionment yet and for me everything still works.
So, a caution to everyone: don't update your environment!

@DSenftleben give us the output of:
ldd `which ncl` | grep cryp

I tested the simple script above on a colleague's account (no conda, no esmvaltool) and it works.
I tried to deactivate conda and load just the NCL module, the problem still occurs.

(esmvaltool) valeriu@valeriu-PORTEGE-Z30-C:~/esmvaltool_alpha$ ldd `which ncl` | grep cryp
	libcrypto.so.1.0.0 => /home/valeriu/anaconda3/envs/esmvaltool/bin/../lib/./libcrypto.so.1.0.0 (0x00007fa41fba5000)
	libk5crypto.so.3 => /home/valeriu/anaconda3/envs/esmvaltool/bin/../lib/./libk5crypto.so.3 (0x00007fa41fa5a000)

ldd `which ncl` | grep cryp
        libcrypto.so.10 => /usr/lib64/libcrypto.so.10 (0x00007fb352b5e000)
        libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x00007fb34fba1000)
        libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007fb34d7e9000)

So @valeriupredoi, you have the needed shared lib in your environment that we miss.

And @mattiarighi, you are using the one in the system.

Yes, that works, but my test scripts crashes with a strange error message that does not occur for other users on the same machine.

@mattiarighi : Is it the new released ncl:
https://www.ncl.ucar.edu/current_release.shtml

That might be the reason, indeed...

sorry guys, had to leave for a bit tell a colleague how to git.
So, even after a fresh pull of version2_development, environment update, reinstall the tool, I can use ncl ok:
ncl 0> x = 2
ncl 1> print(x)

Variable: x
Type: integer
Total Size: 4 bytes
            1 values
Number of Dimensions: 1
Dimensions and sizes:	[1]
Coordinates:
(0)	2

(this is the only NCL syntax I know :grin:  )
I have done this with two different OS's: Ubuntu and Scientific Linux
ldd output:
(esmvaltool) [valeriu@jasmin-sci2 esmvaltool_alpha]$ ldd `which ncl` | grep cryp
	libcrypto.so.1.1 => /home/users/valeriu/anaconda3Feb19/envs/esmvaltool/bin/../lib/./libcrypto.so.1.1 (0x00007fa8dfc06000)
	libk5crypto.so.3 => /home/users/valeriu/anaconda3Feb19/envs/esmvaltool/bin/../lib/./libk5crypto.so.3 (0x00007fa8dfabb000)

and for Ubuntu:
(esmvaltool) valeriu@valeriu-PORTEGE-Z30-C:~/esmvaltool_alpha$ ldd `which ncl` | grep cryp
	libcrypto.so.1.1 => /home/valeriu/anaconda3/envs/esmvaltool/bin/../lib/./libcrypto.so.1.1 (0x00007f6f3ec76000)
	libk5crypto.so.3 => /home/valeriu/anaconda3/envs/esmvaltool/bin/../lib/./libk5crypto.so.3 (0x00007f6f3eb2c000)

and ncl version:
(esmvaltool) valeriu@valeriu-PORTEGE-Z30-C:~/esmvaltool_alpha$ conda list ncl
# packages in environment at /home/valeriu/anaconda3/envs/esmvaltool:
#
# Name                    Version                   Build  Channel
ncl                       6.5.0           blas_openblashd40de8d_1  [blas_openblas]  conda-forge

and
(esmvaltool) [valeriu@jasmin-sci2 esmvaltool_alpha]$ conda list ncl
# packages in environment at /home/users/valeriu/anaconda3Feb19/envs/esmvaltool:
#
# Name                    Version                   Build  Channel
ncl                       6.5.0           blas_openblashd40de8d_1  [blas_openblas]  conda-forge

Should we inform DKRZ about this problem?
@bjoernbroetz what do you think?

note that conda env update WILL NOT pick up 6.6.2 https://anaconda.org/conda-forge/ncl but rather 6.5.0 still; I suspect the new version will be installed with a fresh env build (conda env create)

I am just building a new virtual env see if 6.6.2 gets installed and if I have issues with it, stay tuned :radio:

conda env create still picks up 6.5
# packages in environment at /home/valeriu/anaconda3/envs/esmvaltool_ncl:
#
# Name                    Version                   Build  Channel
ncl                       6.5.0           blas_openblash04324b8_3  [blas_openblas]  conda-forge

that works fine still; in the environment -
conda install -c conda-forge ncl
still picks up 6.5.0 but changes some hashes and updates some deps, but still works well
conda install -c conda-forge ncl=6.6.2
will remove a lot of needed stuff:
The following packages will be REMOVED:

  cdo-1.9.3-1
  r-base-3.5.1-he45234b_1005
  r-rcpp-1.0.0-r351h29659fb_1000
  r-xml-3.98_1.16-r351h96ca727_1000

and change a LOT of others, and at the end of it all:
ncl 0> x = 2
ncl 1> print(x)

Variable: x
Type: integer
Total Size: 4 bytes
            1 values
Number of Dimensions: 1
Dimensions and sizes:	[1]
Coordinates:
(0)	2

so it still works (on Ubuntu, dont have time to test on Jasmin's SL)
(esmvaltool_ncl) valeriu@valeriu-PORTEGE-Z30-C:~/esmvaltool_alpha$ ldd `which ncl` | grep cryp
	libcrypto.so.1.0.0 => /home/valeriu/anaconda3/envs/esmvaltool_ncl/bin/../lib/./libcrypto.so.1.0.0 (0x00007f57191e3000)
	libk5crypto.so.3 => /home/valeriu/anaconda3/envs/esmvaltool_ncl/bin/../lib/././libk5crypto.so.3 (0x00007f571584f000)

BUT the R tools are gone:
(esmvaltool_ncl) valeriu@valeriu-PORTEGE-Z30-C:~/esmvaltool_alpha$ conda list r-rcpp
# packages in environment at /home/valeriu/anaconda3/envs/esmvaltool_ncl:
#
# Name                    Version                   Build  Channel
(esmvaltool_ncl) valeriu@valeriu-PORTEGE-Z30-C:~/esmvaltool_alpha$ vim environment.yml
(esmvaltool_ncl) valeriu@valeriu-PORTEGE-Z30-C:~/esmvaltool_alpha$ conda list r-rxml
# packages in environment at /home/valeriu/anaconda3/envs/esmvaltool_ncl:
#
# Name                    Version                   Build  Channel

So I'd say let's stick with 6.5.0 for now

oh and cdo is gonzo as well

Setting up the esmvaltool environment up new (conda env remove ... etc.) fixes the ncl issue. The cdo problem persists.

yes @bjoernbroetz - have a look at my workflow that I posted above, setting up a new env still installs ncl=6.5.0 which works fine; only problem is that if we want ncl=6.6.2 that by default removes the R packages and cdo; I have installed manually cdo after and at least cdo --help works

Setting up the esmvaltool environment up new (conda env remove ... etc.) fixes the ncl issue. The cdo problem persists.

I did the same and I can confirm that NCL works but cdo still has problems.
As a workaround, we can use the local cdo (module load cdo) but it would be good to understand what is going wrong.

@mattiarighi what ncl and cdo versions do you have that are making things go tits up for you?

cdo                       1.5.2                    pypi_0    pypi

NCL is 6.5.0 but now works.

your cdo is older than Moses @mattiarighi I have 1.9.3 with ncl=6.5 and 1.9.6 with ncl=6.6.2

This is version I get running the standard installation procedure.

yes and that is ye olde - my installations are via conda-forge and that supersedes the pip one

Can we change our setup accordingly?

frankly I am very surprised your cdo is from pip since my environments are stock esmvaltool environments and not anything custom, it's just that the pip one gets superseded by the conda one at some point during the environment creation and you should have the same conda=based cdo

aah! who set cdo=1.9.3 in environment.yml and didnt remove it from the pypi list in setup.py? That one will owe me a beer because: 1. now I kmow why the base ncl=6.5 even if the latest is 6.6.2 and 2. that may blow your stuffs up at your end @mattiarighi

git blame is your friend :smile:

The cdo in setup.py is the Python cdo package (called python-cdo on conda-forge). This seems to confuse conda env export, but should be no problem. @mattiarighi can you run which cdo; cdo --version to get the actual version of cdo you have?

Note that we had to pin cdo to 1.9.5 in current pull requests to get it working with ncl 6.5 if you install both from conda.

@bouweandela you mean 1.9.3
working 1.9.3:
Climate Data Operators version 1.9.3 (http://mpimet.mpg.de/cdo)
Compiled: by unknown on 7202286a92ec (x86_64-unknown-linux-gnu) Apr 18 2018 20:54:15
CXX Compiler: g++ -fPIC -DPIC -g -O2 -std=c++11 -fopenmp -fPIC -DPIC  -fopenmp
CXX version : g++ (GCC) 4.8.2 20140120 (Red Hat 4.8.2-15)
C Compiler: gcc -std=gnu99 -fPIC -DPIC  -fopenmp
C version : gcc (GCC) 4.8.2 20140120 (Red Hat 4.8.2-15)
F77 Compiler:
F77 version : ./configure: line 21772: -V: command not found
Features: 7GB C++11 DATA PTHREADS OpenMP3 HDF5 NC4/HDF5/threadsafe OPeNDAP UDUNITS2 PROJ.4 XML2 CURL FFTW3 SSE2
Libraries: HDF5/1.10.1(1.10.2) proj/4.93 xml2/2.9.8 curl/7.64.0(h7.59.0)
Filetypes: srv ext ieg grb1 grb2 nc1 nc2 nc4 nc4c nc5
CDI library version : 1.9.3 of Apr 18 2018 20:52:33
CGRIBEX library version : 1.9.0 of Jan 22 2018 09:24:03
GRIB_API library version : 2.8.2
NetCDF library version : 4.6.1 of Oct 22 2018 00:13:28 $
HDF5 library version : 1.10.2 threadsafe
EXSE library version : 1.4.0 of Apr 18 2018 20:52:29
FILE library version : 1.8.3 of Apr 18 2018 20:52:27

which cdo returns the conda path
/miniconda3/envs/esmvaltool/bin/cdo

cdo --version does not work due to the problem above

@mattiarighi is your error
cdo: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory

?

Yes

@bouweandela you mean 1.9.3

No, I mean 1.9.5

(cdo+ncl from conda): 1.9.3 works fine with 6.5 on certain machines as well as 1.9.3 or 5 doesn't work at all with 6.5 on other machines; it's a machine-specific bug - am looking at it right now

cdo --version does not work due to the problem above

Haha, they're not making it easy for you.
Use LD_LIBRARY_PATH=/some/path/to/libssl cdo --version instead

ok @mattiarighi - create a new environment with this environment.yml:
---

name: esmvaltool
channels:
  - conda-forge

dependencies:
  # Python packages that cannot be installed from PyPI:
  - iris
  - matplotlib<3  # Can be installed from PyPI, but is a dependency of iris and should be pinned.
  - python-stratify
  - esmpy
  - xarray  # Can be installed from PyPI, but here to get a consistent set of depencies with iris.
  # Non-Python dependencies
  - graphviz
  - cdo=1.9.3

  # Multi language support:
  - ncl=6.5.0
  - jasper!=1.900.31  # pinned NCL dependency
  - r-base
  - r-rcpp
  - r-xml
  - libunwind  #  specifically for Python3.7+
  # TODO: add julia

and remove cdo from setup.py - that will get you back on tracks :train2:

Can we implement this as general solution?

@bouweandela @mattiarighi the problem here is that both cdo and ncl have evolved and they have evolved in different directions as conda sees it: ie if we pin cdo<1.9.6 and let ncl free the environment is hard to solve since conda will sometimes try grab ncl=6.6.2 that doesn't work with cdo=1.9.3 or 5 (interestingly enough on a machine with older conda 4.6.4 this is not a problem because the older conda will not know of the new ncl=6.6.2); if we install cdo=1.9.6 that will remove ncl=6.5.0 and the other way around -- it looks like there is a lot of hatred between the older ncl and cdo=1.9.6; if we pin cdo=1.9.6 and ncl=6.6.2 then it will complain about r-base/r-xml/r-shits that get slashed with the new ncl (all the R libraries get slashed!) - so yes, I think the best intermediary solution is to pin both cdo and ncl to their older versions unless we can install the R packages from pip (havent tried that yet)

note that this environment works well as well (from an esmvaltool/ncl/cdo functional point of view but the r-shits are s;ashed and need to be installed from elsewhere but conda):
---

name: esmvaltool
channels:
  - conda-forge

dependencies:
  # Python packages that cannot be installed from PyPI:
  - iris
  - matplotlib<3  # Can be installed from PyPI, but is a dependency of iris and should be pinned.
  - python-stratify
  - esmpy
  - xarray  # Can be installed from PyPI, but here to get a consistent set of depencies with iris.
  # Non-Python dependencies
  - graphviz
  - cdo=1.9.6

  # Multi language support:
  - ncl=6.6.2
  - jasper!=1.900.31  # pinned NCL dependency
  #- r-base
  #- r-rcpp
  #- r-xml
  - libunwind  #  specifically for Python3.7+
  # TODO: add julia

ah but I have good news for you python-dependency-lovers :grin: - the R shits can be installed no problemo from the r channel eg conda install -c r r-base and so on, no deps will be removed and we'll have the latest ncl and cdo versions talking to each other, so we just need to add the r channel to our environment.yml -  :beer: to me

also no need to pin ncl or cdo since if conda gets those R shits from the r channel then there will be no need to stay at ncl=6.5 hence ncl will go up and cdo will go up with it too; am going home, have had enough of this :bus:

(esmvaltool_cdo2) [valeriu@jasmin-sci2 esmvaltool_alpha]$ conda list cdo
# packages in environment at /home/users/valeriu/anaconda3Feb19/envs/esmvaltool_cdo2:
#
# Name                    Version                   Build  Channel
cdo                       1.9.6             he2b4288_1005    conda-forge
(esmvaltool_cdo2) [valeriu@jasmin-sci2 esmvaltool_alpha]$ conda list ncl
# packages in environment at /home/users/valeriu/anaconda3Feb19/envs/esmvaltool_cdo2:
#
# Name                    Version                   Build  Channel
ncl                       6.6.2           blas_openblashde02c1e_0  [blas_openblas]  conda-forge
(esmvaltool_cdo2) [valeriu@jasmin-sci2 esmvaltool_alpha]$ conda list r-base
# packages in environment at /home/users/valeriu/anaconda3Feb19/envs/esmvaltool_cdo2:
#
# Name                    Version                   Build  Channel
r-base                    3.2.2                         0    r
(esmvaltool_cdo2) [valeriu@jasmin-sci2 esmvaltool_alpha]$ conda list r-rcpp
# packages in environment at /home/users/valeriu/anaconda3Feb19/envs/esmvaltool_cdo2:
#
# Name                    Version                   Build  Channel
r-rcpp                    0.12.2                r3.2.2_0a    r
(esmvaltool_cdo2) [valeriu@jasmin-sci2 esmvaltool_alpha]$ conda list r-xml
# packages in environment at /home/users/valeriu/anaconda3Feb19/envs/esmvaltool_cdo2:
#
# Name                    Version                   Build  Channel
r-xml                     3.98_1.3              r3.2.2_0a    r
(esmvaltool_cdo2) [valeriu@jasmin-sci2 esmvaltool_alpha]$ cdo --version
Climate Data Operators version 1.9.6 (http://mpimet.mpg.de/cdo)

We just tried to install the newest environment @ETH and got the message ncl=6.5.0 and hdf5=1.10.3 are conflicting. Solved it by removing the hdf5 package definition and removing r-base (since we are not using R). But other people might run into the same issue.

Please try the environment in #936. That works at DKRZ and on Jasmin.
We will merge it hopefully today.

thanks, ok, just saw that there is more.....

Sorry, I mean #958.
The branch is called version2_development_solve_environment_March2019

the cdo-ncl broken relation is now solved (hence I changed the name of this issue); the r-base-ncl relation is still broken (really badly!) and I have opened an issue on the NCL gitHub since I am not able to find any conda-elegant solution: https://github.com/NCAR/ncl/issues/87
Note that if you don't need the R diags you can cleanly create the environment with the files from https://github.com/ESMValGroup/ESMValTool/pull/958 (don't be scared of the failing CircleCI tests, they are because I am still keeping the R tests but there is no R installation at the moment).
@mattiarighi @bouweandela we should patch version2_development with the files from #958 asap since users the environment in it is currently broken and users will start complaining soon


[sil] When the immutable address use verifier errors due to an unknow…

…n instruction, print the instruction to improve debuggability.

@swift-ci smoke test and merge


Add a stub wl_drm implementation

This will allow us to remove all of our EGL wl_drm support code
and remove some weird stuff we need just for wl_drm support. For
instance the only reason why our wl_compositor implementation needs
a wlr_renderer is to query the size of wl_drm buffers.

This PR will break on split render/display devices, because of https://gitlab.freedesktop.org/mesa/mesa/-/issues/4178. I don't really want to advertise a primary node via wl_drm because we'd need to handle legacy authenticate requests.

For instance the only reason why our wl_compositor implementation needs
a wlr_renderer is to query the size of wl_drm buffers.

Not quite, we also use it to create a texture on surface commit. So can't get rid of this part now, although I'd like to eventually get rid of it.

I don't really want to advertise a primary node via wl_drm because we'd need to handle legacy authenticate requests.

Well, the primary node can't be used for rendering on these platforms anyways, so DRM authentication shouldn't matter. Added a fallback to the DRM primary node.

Another blocker for this is Mesa's Wayland WSI, which currently prefers to use wl_drm over linux-dmabuf.

Pushed a new set of commits to add support for wl_drm buffers.

This is now ready for review.

LGTM, good riddance :D


Confidence Limits Not Retained in Flow-Frequency Display

When creating a flow-frequency function, you can select Compute Confidence Limits to show the 2.5% and 97.5% confidence limits. However, when you save the function, close and reopen it, the confidence limits are no longer displayed. This can cause confusion with users that the confidence limits aren't being retained when they are. This ticket was prompted by a user that submitted a ticket in Discourse thinking the confidence limits were being lost.

A simple response would be to change "compute confidence limits" to "visualize confidence limits"


Document cfssljson version verification

It seems there Is a way to verify cfssljson version now

This should be fixed on master.


How to add validation to FormFieldPresetFactory.fields

How to add the validation for the textfields and access those valid value from it.
let textFields = FormFieldPresetFactory.fields(by: [.email], style: style)
I assume textFields.text shows the enter text value inside the textfields.
How to access those value from the FormFieldPresetFactory.fields (with given parameters)

There is no way to do this (at the moment) using the SwiftEntryKit's presets, so until it's implemented, you will have to use your own custom entry view.

Closing as it won't be implemented in the intermediate future.


Autorest Regen Preview to 3.0.0-alpha.20230921.8 by Dapeng Zhang from refs/pull/3760/merge

Triggered from https://github.com/Azure/autorest.csharp/pull/3760

API change check
API changes are not detected in this pull request.


Feature ge display of rooms scheduled appointments

In this PR I have displayed scheduled appointments in each room with option for canceling any of appointments (regular examination, equipment relocation and renovation).

 (0) PR Feature ge display of rooms scheduled appointments

 (0) PR Feature ge display of rooms scheduled appointments


MiKo_6044 enhanced to report also on prefix/postfix unary expressions

(resolves ##534)

@CodiumAI-Agent /describe


Assign a string to flags.Filename

I have an object with attributes of type flags.Filename. How do I assign dynamically generated string to it ?
for example, both input and output are of type flags.Filename below
str := "hello world" //this will be generated dynamically in the code
opt := &model.TestObj{
input: "teststring",
output: str}           ///this line gives an error

Just like anything in go, you'll need to cast it explicitly, i.e. flags.Filename(str). For the second issue, looks like you have several versions/packages of go-flags being linked in. Types between packages (even if they are actually the same package) aren't compatible.


UI: epoch component

Does not seem like we keep a record of this with soljuno. Is this something I need to get from the rpc or will be logging this?

One epoch is 432000 slots, let's see if it can be solved by a function, or by storing the info by a table.

Oh i mean in this case, it's a fairly easy calculation if we are starting from slot 0. We can calculate this on the frontend

@ryuash Okay, the epoch can be calculated with slot / 432000, then the time of until next epoch is 432000 - (slot%432000) * avg_slot_time.

Yes let me move this issue to my repo. No action is needed on your end except for getting the avg_slot_time

@ryuash Okay, the avg_slot_time just have done by #84.


Azure built-in role for AKS

In Azure AD, Is there a built in role that I can assign to a group of Azure AD members that can be limited to AKS in scope (or something equivalent on your documentation page for built in roles? https://docs.microsoft.com/en-us/azure/role-based-access-control/built-in-roles#documentdb-account-contributor. I would like to start creating groups for aks specific use but dont see this there. If there's a different way to accomplish this can you please share? Trying to limit access and not give contributor access to an entire resource group.

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

ID: a47c6df7-5103-1336-eb0b-68f95155e6c8
Version Independent ID: f4420b08-9b57-f581-fcb4-f069afdd5b0c
Content: Integrate Azure Active Directory with Azure Kubernetes Service
Content Source: articles/aks/aad-integration.md
Service: container-service
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

This can be closed, I believe I have found the custom roles section that will meet the needs for this.

Thanks for the update @jdogg89. If you need additional assistance just let us know and we can reopen and continue.


Assertion failure in HttpTransact::is_response_valid() when a parent proxy is down.

When testing on a debug master build, a failure to connect to an upstream parent proxy that is down, an assertion crash occurs at HttpTransact::is_response_valid():334.  s->current.state is set to BAD_INCOMING_RESPONSE which is not in the list of current.state values accepted in the ink_assert().
In 9.1.x, when a parent is down, the current.state comes in as CONNECTION_CLOSED but in master it's now BAD_COMING_RESPONSE.

other problem


Sign up with Github

User should be able to sign up with rector-ci.org and activate Rector CI for his repositories.

Closed via #53


Update entry-context.mdx

multiple js config entry added
the technical document in which you wanted to determine the input and output names of different files was not included. That's why I added this.

I believe it's already documented in https://webpack.js.org/concepts/entry-points/#multi-page-application

@chenxsan thats right but
"entry: {
exampleFolder/pageOne:
paths.src + '/index.js'
},"
you cant do it like that so you cant select the folder, only you can define the file.


Add  "workerIndexing": "true" in nativehost worker config

Add  "workerIndexing": "true" in nativehost worker config. This is needed for the host to use worker indexing.
This change is a follow up to #1258

/check-enforcer evaluate