Upgrade google error prone from 2.10.0 to latest (2.32.0)

Describe the bug
The version of google error prone that we are using (7x, 8x, main) dates back from Nov 2021
If you compile DSpace with java 22, you get this error:
https://github.com/google/error-prone/issues/4370 also reported on
https://groups.google.com/g/dspace-tech/c/aDkd-k3ceGQ
This is fixed when upgrading to the latest version of error prone.

Word of warning for anyone attempting this upgrade: some of those new checks immediately start triggering. So it's not as simple as bumping the version number, the new errors likely have to be looked at and resolved.

After the ERRORs are cleaned up, we should all give some attention to what our code quality tools are telling us.  There are hundreds and hundreds of warnings -- so many that we are not seeing them all, because the tools tend to stop reporting after some round number has been reached.  Some of those skipped warnings may be important.


Strange behavior when going throw a portal.

 And also, when I click on the **swich to creative + ** it doesn't switch.
https://user-images.githubusercontent.com/68589851/113552856-580cee00-9629-11eb-8b0e-1fa60d39d72a.mp4
The fix is just changing gamemodes and then it will your files will be visable again.

I can confirm that everything goes a bit weird on dimension change - in my case my hotbar items would.. duplicate when I tried to click on them.
Same as you, a gamemode switch fixes the issue.


Add Aeotec ZW111-C EU firmware version 2.04

Add firmware upgrade for Aeotec Nano Dimmer ZW111-C EU version 2.04.
Firmware page:
https://aeotec.freshdesk.com/support/solutions/articles/6000198943-how-to-update-nano-dimmer-z-wave-firmware-

Is it the integrity of the zip-file or the .exe file that we want as the sha256 sum?

Z-Wave JS doesn't support zip files for firmware updates currently, so we'd need a link to the file contained in the ZIP.
If you run the URL through npx @zwave-js/firmware-integrity <url>, it will give you the correct integrity - if the file is in a supported format.

Z-Wave JS doesn't support zip files for firmware updates currently, so we'd need a link to the file contained in the ZIP.

Aha. Since the file must be hosted by the manufacturer, and since the manufacturer has posted the file as a .zip file, then we cannot get this firmware to work with firmware-updates.

I'll see if i can grab the OTZ files, those can be used instead of the zip files we supply on that article. Hopefully should be able to get these files earlier next week after christmas (may not hear back until after new years).

https://aeotec.freshdesk.com/a/solutions/articles/6000198943 OTZ files posted in this link here @larstobi
Specifically for EU Frequency, this should be the link here: https://aeotec.freshdesk.com/helpdesk/attachments/6189873103
Remember to generate a new SHA key.

Excellent! Thanks, will update the PR.

@AlCalzone this one should be good now. I'll make some for AU and US frequency once i get back to office on Jan 2nd.

Oh, I just saw the PR by @Aeotec-ccheng includes this one.


Improve release management

Add unit tests
Configure CI
Use semantic-release to release new versions

:tada: This issue has been resolved in version 3.3.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


how to refresh page in bottom bar menu when using stateManagement: true

I'm having a problem with state Management: true. It doesn't update the page again, it only updates the first time and after that it keeps the state not updated.
body: PersistentTabView(
          context,
          controller: bottomTabcontroller,
          screens: pages,
          items: _navBarsItems(),
          confineInSafeArea: true,
          backgroundColor: Colors.white,
          handleAndroidBackButtonPress: true,
          resizeToAvoidBottomInset: true,
          stateManagement: true,
          hideNavigationBarWhenKeyboardShows: true,
          decoration: NavBarDecoration(
            borderRadius: BorderRadius.circular(10.0),
            colorBehindNavBar: Colors.white,
          ),
          popAllScreensOnTapOfSelectedTab: false,
          popActionScreens: PopActionScreensType.once,
          itemAnimationProperties: ItemAnimationProperties(
            duration: Duration(milliseconds: 200),
            curve: Curves.ease,
          ),
          screenTransitionAnimation: ScreenTransitionAnimation(
            animateTabTransition: true,
            curve: Curves.ease,
            duration: Duration(milliseconds: 200),
          ),
          navBarStyle: NavBarStyle.style6,
        )

Sorry I couldnt reproduce your issue provided I understand it correctly. Can you provide you full code example and the output of flutter doctor -v?

Thanks for the help, i got it working calling the pageback from the navbar, to update the UI again.

@Sang-Nguyen-25 can you help me with how did you do it?

Thanks for the help, i got it working calling the pageback from the navbar, to update the UI again.

Can you share a bit more info on this?

@Abdelaty and @leossmith
You can update the state of your screen using your state management while keeping the PersistentTabView,          stateManagement: true.


X-ig-www-claim

How to build X-ig-www-claim code

See request.ts.

i see 'X-IG-WWW-Claim': this.client.state.igWWWClaim || '0'
I couldn't figure out how to build it
i need code create igWWWClaim
like hmac......

@m1faridi Why haven't you searched for state.igWWWClaim?

i see 'X-IG-WWW-Claim': this.client.state.igWWWClaim || '0'
I couldn't figure out how to build it
i need code create igWWWClaim
like hmac......

This code is provided in the response headers when you request https://www.instagram.com/account/login/ajax/

hey , can anyone explain me what is x-ig-www-claim?

@sarraayush As I know, header that contains something that allows you upload photos to instagram

@sarraayush As I know, header that contains something that allows you upload photos to instagram

This header typically plays a role in Instagram's security


Event Listener for Final Result or Listening Stopped

Is your feature request related to a problem? Please describe.
On iOS and Android when implementing this plugin, speech recognitions starts and then stops either when the user finishes talking or after a predetermined a mount of time. Whilst it is possible to capture the partial results as the listener is talking. It doesn't seem possible to either listen indefinitely and the use the .stop() method to manually stop listening and process teh final result, nor is there a listener to return the full result.
Describe the solution you'd like
I think the above could be solved with one of two new features:

An event listener for "finalResult" as well as "partialResult".
The ability for the speech recognition to go on indefinitely with a manual .stop() ending it. This could be followed by a .then() which could handle the final results set.

Describe alternatives you've considered

If details could be shared in the documentation for the default listening time on each platform then one could set a Timeout to trigger once listening has stopped.
An isListening() method was proposed in Issue #44, this could be repeatedly called to determine if the listening session ahs ended, were this feature to be implemented.

Is there an update on this one?

For me not having this events makes it unusable for now. Maybe an error event would be nice to have.

I need this feature too! pleaseee @jcesarmobile

for me IOS works fine, records on start and stops recording on stop.
however Android does not work. as stated above, the recording finishes when user pauses or after a few seconds.
PR #83 added a useful isListening method that has 2 problems:
Ios - isListening returns undefined both when recording and not.
Android - isListening  works fine, but can not be used to override the automatic stopping of the recording.

isListening is working fine for me on iOS, if it doesn't work for you, please, create a new issue and provide a sample app that reproduces the problem
it's not possible to do continuous recognition on any of the platforms, iOS stops after a minute, Android when it detects a silence.
You can listen for the listeningState event and when the status is stopped call start again.
iOS was missing some cases where listeningState with stopped value should be fired, fixed on https://github.com/capacitor-community/speech-recognition/pull/95


YML File for a device room alert version 3E

Hello, we request your help in order to get the roomalert.yml for a device version 3E.
This because we currently have the kentik roomalert.yml for a device version 3S and we need the file for version roomalerts3e.
We are attaching the file ROOMALERT3E.MIB for further details.
As additional information we perform tests with the current roomalerts.yml for version 3S  (avtech) and it didn't work.
We apologize for the error with the description at the Issue #511
RA3E-MIB.zip

Based on the instructions when you open an issue in this repo, we don't use MIB files to create profiles, we would need an SNMP walk from the device that you are trying to monitor.  Please provide the information requested in the template
Device Vendor:
Device Model:
System Object Identifier (SysOID):
List of critical metrics that you expect in the profile (does not need to be all-inclusive, just a general idea of your expectations):

If there is a New Relic technical support case related to this request, please provide the case number:
Please provide a public gist with a sanitized (sensitive information removed) SNMP walk of the device. Providing MIB files is not a substitute for an SNMP walk and failure to provide one here will result in delays for closing this issue. The output of these commands shows the "true story" of what a device will respond to in SNMP and is used to ensure that our profiles are efficient and accurate for your devices.
Gist Link:

Example SNMP walk commands:
# v2c example
snmpwalk -v 2c -t 10 -On -c $COMMUNITY_STRING $IP_ADDRESS . >> snmp_walk.out

# v3 example
snmpwalk -v3 -t 10 -l authPriv -u $USERNAME -a MD5|SHA -A $AUTH_PASS -x DES|AES -X $PRIV_PASS -ObentU -Cc $IP_ADDRESS . >> snmp_walk.out

Hi Marc, we are sending you the requested information in the attached file "RoomAlert3E_information.txt"
Thanks in advance for your help.
RoomAlert3E_information.zip

Hi Marc,
It's been a couple of days without updates. We would like to knows if there have been any advance with the roomalert.yml for a device version 3E requested?

Hi Marc,
It's been a couple of days without updates or any notifications from you.
We would like to knows if there have been any advance with the roomalert.yml for a device version 3E requested?
We do really need your help.
Have a nice day.

@EddGH1337 This repo is best effort from our side, so you'll have to be patient.   It is in the back log and it will be completed as we get to them, you are also free to create a profile and submit it as a PR by using the existing profiles and the template document for reference.


Method init(botkit) in FacebookAdapter class and option disable_webserver

The init method from class FacebookAdapter on package botbuilder-adapter-facebook (version 1.0.8) of botkit package receives a Botkit object as parameter and this object can have a property called disable_webserver used for informe the Botkit constructor that the webserver do not be created during the instantiation process.
const adapter = new FacebookAdapter({
verify_token: process.env.FACEBOOK_VERIFY_TOKEN,
app_secret: process.env.FACEBOOK_APP_SECRET,
access_token: process.env.FACEBOOK_ACCESS_TOKEN
});
const controller = new Botkit({
    adapter: adapter,
    disable_webserver: true,
// other options
});

But when this object (Botkit) is sended to the init method from FacebookAdapter class this option is not considered and the init method try create a new get route to the default webhook. This action causes a error because is not possible call the get method from botkit.webserver, that is undefined.
public async init(botkit): Promise<any> {
    debug('Add GET webhook endpoint for verification at: ', botkit.getConfig('webhook_uri'));
    botkit.webserver.get(botkit.getConfig('webhook_uri'), (req, res) => {
        if (req.query['hub.mode'] === 'subscribe') {
            if (req.query['hub.verify_token'] === this.options.verify_token) {
                res.send(req.query['hub.challenge']);
            } else {
                res.send('OK');
            }
        }
    });
}

I am using this approach because I have an external web server used with Botkit in my project.
I beliave that this behavior may be modified if on the init method the disable_webserver config option was considered like the code bellow for example
    init(botkit) {
        return __awaiter(this, void 0, void 0, function* () {
            // This condition is the modification
            debug('disable_webserver: ', (botkit._config) ? botkit._config.disable_webserver: false);
            if (botkit._config && !botkit._config.disable_webserver) {
                debug('Add GET webhook endpoint for verification at: ', botkit.getConfig('webhook_uri'));
                botkit.webserver.get(botkit.getConfig('webhook_uri'), (req, res) => {
                    if (req.query['hub.mode'] === 'subscribe') {
                        if (req.query['hub.verify_token'] === this.options.verify_token) {
                            res.send(req.query['hub.challenge']);
                        }
                        else {
                            res.send('OK');
                        }
                    }
                });
            }
        });
    }

This code may be modified on facebook_adapter.js on lib directory and on facebook_adapter.ts on *src directory.
What was the result you received?
I received a error on init method from facebookAdapter class because the code try access the get method form botkit.webserver and this parameter is undefined
What did you expect?
I expected that the botkit constructor was well initialized with the parameters adapter: facebookAdapter and disable_webserver: true, but i received a error when the init method of the facebookAdapter class was excecuted because the webserver associated with the botkit instances was undefined, as requested by disable_webserver parameter
Context:

botbuilder-adapter-facebook version: 1.0.8
Botkit version: 4.5.0
Messaging Platform: Facebook
Node version:  10.15.2
Os: Ubuntu Linux 18.04
Any other relevant information:

This is a bug, thank you for reporting it.

this will be in the next release -> #1929


authorization required while using email activity api

Issue Summary
I started with free and then purchased 30 days to access EMail Activity API but still getting - authorization required error

Hello @carveredison,
Thanks for submitting a GitHub issue! We are very sorry that you are running into this problem. In order to better serve you, as this does not present itself as a library specific issue, we would like to ask that you reach out to our support team at https://support.sendgrid.com.
Thank you!
SendGrid DX Team

Hello @carveredison, how did you get it fixed? i ran into the same error. Thanks


Detecting different non-plain text (text/*) mime-types.

I can see that this crate is focused on identifying files/arbitrary data by magic values, but afaict this is the only crate which implements the freedesktop shared mime db spec, so it would be nice if from_filepath also checked for matching extensions since most of the work (parsing the db etc.) is already done here, and would have to be duplicated in another crate.
Alternatively maybe some of that logic could be split out into another crate which then i could use to implement filename checking?

This could be done using the “globs” files from the Shared MIME-info Database:
https://specifications.freedesktop.org/shared-mime-info-spec/shared-mime-info-spec-latest.html#idm45617682177472
I don’t have any plans to work on this, but would welcome contributions.  For now, the mime_guess crate offers a similar feature.


Bundle.run appears to be down/ malfunctioning

Packages that were working yesterday are erring out today. For example, when I hit<EMAIL_ADDRESS>I see

Seems fine for me

Seems fine to me. In what region are you?

I'm around NYC. Still seems there are packages that were working 2 days ago but not today. https://bundle.run/theme-ui gets Gateway time-out for me now


MemoryError sometimes, output.xml become 70 times larger than normal execution

Hi,
I have an execution about 70 testcases in it. Normally it executes correctly and the output.xml is about 7M， while sometimes it crashed and raise a MemoryError, meanwhile the output.xml is about 482M, which is about 70 times larger than before.
Any suggestion would be appreciated, thank you.


Redundant Links on Header

Overview
The Header Content "Join the Index", "Overview", "Civic Tech Organizations" & "RadicalCollaboration"  all are hyperlinked to /home which was pointed out by accessibility Tool
Site Improve

Action Items
Refactor navigation.js and  HeaderLarge.js
Resources
http://civictechindex.org
Accessibility Tool : Site Improve

This is a non-issue. None of those href's are active links. We had a (lengthy) discussion one meeting and it was ultimately decided that we would not use the titles of the nav sections as actual links. This error is being triggered as the titles are set up in such a way that it would be easy to set them as active links should it be decided to do so.


Don't show the config files every time

Currently, the first thing that manim outputs is the line "Configuration files read: [list here]". I find it a bit obnoxious, especially when rapid iterating on a scene, as this message is repeated over and over and over. Further, the paths shown are absolute paths so they take up a bit of space in the console screen. Not only that, but the first two paths will almost always be the same (library-wide and user-wide files), so this output is not super informative most of the time.
I suggest we keep that log line on a DEBUG level only. Thoughts?

I suggest we keep that log line on a DEBUG level only. Thoughts?

Uhhh, noob question: How do we change the log level ( whether we want to see debug messages or not)?
I tried editing the log_level entry in manim.cfg, but no value I set ever worked.

I think right now everything is being printed at the INFO level, so using either DEBUG or INFO would output the same thing. Using ERROR should not print anything. Is this not the case?

Well, setting log_level = DEBUG, log_level = INFO, log_level = ERROR, all result in the same error:
It seems your colour configuration couldn't be parsed. Loading the default color configuration...

Ugh I think this is related to this comment. Try using the verbose flag instead?

Shouldn't it just be a matter of changing a logger.log call to a logger.debug one?

Shouldn't it just be a matter of changing a logger.log call to a logger.debug one?

No, that works.
I wanted to know how I could also see those debug level messages if I wanted to.

Hmm.. maybe try logging.DEBUG instead of DEBUG?

Hmm.. maybe try logging.DEBUG instead of DEBUG?

Nope, that also results in a It seems your colour configuration couldn't be parsed. Loading the default color configuration...

Ugh I think this is related to this comment. Try using the verbose flag instead?

Oookay, so setting verbose = DEBUG works and allows logger.debug messages to come through.
This was really confusing to work out though; what exactly impacted what. End user might expect changing log_level to change, y'know, the log level, not knowing that verbose changes it.
This should, at the very least, be documented somewhere.
Also, what does log_level actually impact? I tried changing it to numbers, to strings like "VERBOSE", or "DEBUG" etc. It only seems to accept rich styles, but setting it to a rich style changes virtually nothing. What does it do? Does it even need to be there? Mentioning @naveen521kk since he PR'd the logger's config section.

@Aathish04 so we can solve the title of the issue by using logger.debug instead of logging.info, and --verbose is the flag that allows you to see debug messages, yes?

@Aathish04 so we can solve the title of the issue by using logger.debug instead of logging.info, and --verbose is the flag that allows you to see debug messages, yes?

Yup, and verbosity can be set from CFG files as well, so I can have it always be on debug, so I'm happy.
PR on this in an hour or so.

@Aathish04  On seeing
https://github.com/willmcgugan/rich/blob/master/rich/_log_render.py#L44-L45
I could see log_level is for  highlighting the word DEBUG or ERROR which is shown in second column of logs.

@Aathish04 On seeing
https://github.com/willmcgugan/rich/blob/master/rich/_log_render.py#L44-L45
I could see log_level is for highlighting the word DEBUG or ERROR which is shown in second column of logs.

@naveen521kk It seems that changing the entry (at least for me), to some other colour doesn't accomplish anything:

You can see that even though I have set it to red, the level information is still a dim purple.


Update #! in shell scripts

Motivation
Some new distributions like nix and guix have stressed the definition of posix compliance and do not provide /bin/bash, breaking pulsar builds for these distros. This PR applies the most straightforward fix, as /usr/bin/env is posix.
Note for those searching in the future: there are still issues with nix builds relating to this ridiculousness, but that's truly a nix issue, not pulsar.
Modifications
fd -e .sh -x sed -i 's/#!\/bin\/bash/#!\/usr\/bin\/env bash/'
Verifying this change

[ ] Make sure that the change passes the CI checks.

This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API: (yes / no)
The schema: (yes / no / don't know)
The default values of configurations: (yes / no)
The wire protocol: (yes / no)
The rest endpoints: (yes / no)
The admin cli options: (yes / no)
Anything that affects deployment: (yes / no/ don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks


404 when accessing panichd installer

I just installer panichd but when accessing the installer page i've a 404 error.
Any idea?

Without more information, please answer the following questions and I'll try to catch what's going wrong:

Did you add PanicHDServiceProvider in your Laravel config\app.php?
Did you access the url http://your-laravel-app-URL/panichd ?
Did you get any error during installation process?

After ending the installation process, there are two routes to get to Panic Help Desk:

http://your-url/panichd : Redirects to dashboard if everything is ok. If not, Install or upgrade menu will be shown
http://your-url/tickets: Opens Panic HD active tickets list

Can it be that the issue is linked to
    "autoload": {         "psr-4": {             "PanicHD\\PanicHD\\": "src"         }     }
With PanicHD while panichd is currently installed under /vendor/panichd/panichd

I'm not sure. I have read at Stackoverflow https://stackoverflow.com/questions/25499637/laravel-psr-4-not-autoloading that it has to be at the same case as namespace is. You just tell me that you have installed it in a Linux environment. I'll search for that, because I don't have it in any of my testing envuronments.

I'm trying to integrate this package inside: jeremykenedy/laravel-auth
but I have the same problem, when I try to access to the web installer to the URL http://localhost/mylaravelapp/public/panichd I'm redirected to http://localhost/panichd that doesn't exists, while with the URL http://localhost/mylaravelapp/panichd I'm redirected to a 404 page.
in the php artisan route:list I don't see any panichd route.
How can I integrate it in this project?

Is your migrations table called migrations or is it something else?


Update example plugin path

Coverage remained the same at 100.0% when pulling c2e9414de1cde90e0712a321c18923e5fc447da4 on retlehs:patch-1 into f17651bea767b858e15acc04420c5fc9609cde77 on austinpray:master.


Exception handling on invalid URI modifications is a breaking change

I know that the Guzzle project doesn't state that it is following SemVer, and the release notes clearly say:

Ensure each URI modification results in a valid URI according to PSR-7 discussions. Invalid modifications will throw an exception instead of returning a wrong URI or doing some magic.

(new Uri)->withPath('foo')->withHost('example.com') will throw an exception because the path of a URI with an authority must start with a slash "/" or be empty

but I just wanted to give a notice that this change break projects that currently use invalid modifications (as it happened with some of mine, shame on me 🙂), in case that the usual "the app doesn't work anymore" bug report is brought to project maintainers. In my case, I had this code at a few places:
$uri = new Uri('http://domain.tld')->withPath('path/to/location');

This also affects projects that require guzzlehttp/guzzle, which specifies guzzlehttp/psr7: ^1.3.1 as a dependency.
:octocat:

Yes, Azure Storage PHP SDK also suffers from this.

The AWS SDK for PHP dodged breaking customer code only because the version constraint in its composer.json was ~1.3.1, which prevented an automatic upgrade to version 1.4 for many SDK users.
I understand that the new error state was added to prevent this library from entering incorrect or obviously wrong states, but it also seems to have broken some working code. I propose that we deprecate the 1.4 tag, remove it from packagist, and retag the current state of master as 2.0. @Tobion and @mtdowling  what would you think about taking that course of action?

I'm going through a breaking change as well, using the Azure PHP SDK.

I would say removing the tag is not an option. People already using it would have breaking code as well. IF we want a 2.0, then this is what I would do:

create an 1.x branch
revert the change on that branch
tag it with 1.4.1
tag master with 2.0

It's still an open question what we should do with this in Guzzle:

mark 1.4.0 as conflicting version
upgrade to 2.0

Note that 6.3 release is in progress, but there is still much to review, so we need to agree on timing.

@sagikazarmark Releasing a 1.4.1 and 2.0 sounds like a good plan.
I think that Guzzle should be able to use a version constraint like ^1.3.1|^2.0 in that case, as I do not believe any tests or code in Guzzle would be directly affected by the new error state added in 1.4.0.

To be honest, after having looked into the implementation, I am wondering, why this exception is thrown anyways. The method signature states

The path can either be empty or absolute (starting with a slash) or rootless (not starting with a slash). Implementations MUST support all three syntaxes.

(see https://github.com/php-fig/http-message/blob/master/src/UriInterface.php#L248)
The changelog mentions "according to PSR-7 discussions" - does this mean that there will be a psr/http-message 2.0 as well?

A quick fix for project maintainers is adding this line to the composer.json file:
"guzzlehttp/psr7": "^1.3.1, !=1.4.0",

Wouldn't conflict be a more proper way?

As far as I know, conflict is for conflicting packages, not versions 🤔

As @jeskew pointed a few comments above, technically nothing conflicts with Guzzle on this front, and as far as I can see he is right.

I just tested it out with one of my projects, I'm writing down the details in case someone wants to reproduce it.
First, with the latest version (which has the line above in its composer.json)
$ composer require guzzlehttp/guzzle # will install guzzlehttp/psr7 1.4.0
$ composer require kreait/firebase-php # will not downgrade to guzzlehttp/psr7 1.3.1
$ composer update # will perform the downgrade

Then, with a testing branch, which has a "conflict": {"guzzlehttp/psr7": "1.4.0"} section:
$ composer require guzzlehttp/guzzle # will install guzzlehttp/psr7 1.4.0
$ composer require kreait/firebase-php dev-composer-conflict-test # will fail and not be installed

What if you try with --update-with-dependencies?
$ composer require guzzlehttp/guzzle # will install guzzlehttp/psr7 1.4.0
$ composer require --update-with-dependencies kreait/firebase-php dev-composer-conflict-test # ???

Fails as well… it's out of scope of this issue anyways, but it was good to discuss it nonetheless.

See #139 that reverts the BC break and triggers deprecations instead. I thought the magic behavior was introduced in 1.3.1 only as explained in https://github.com/guzzle/psr7/pull/94#issuecomment-231339262 but existed before as well. So I underestimated the impact it could cause. Sorry.


Make the ptrauth builtins no-ops when ptrauth is disabled.

5.3 version of #31572. rdar://62855068

@swift-ci Please test.


Interactive inputs do not produce "echo"

Simple example is running read. Unclear what needs to toggle whether or not echoing is enabled. Might have to do some digging in Runnerv1.
config:{program_name:"/bin/zsh" directory:"/Users/sourishkrout/Projects/stateful/oss/vscode-runme/examples" env:"RUNME_ID=01HX7QEZTB94V7A28K766WNRG3" env:"TERM=xterm-256color" commands:{items:"read" items:""} interactive:true mode:COMMAND_MODE_INLINE known_id:"01HX7QEZTB94V7A28K766WNRG3"} winsize:{rows:10 cols:177} session_id:"01HX7QGJ4VNB9YYEC3NCHD908M" store_stdout_in_env:true

https://github.com/stateful/runme/blob/e163a3a9a20284457c8c518b753b62257e66a800/internal/command/command_virtual.go#L98-L100

It's disabled by default: https://github.com/stateful/runme/blob/e163a3a9a20284457c8c518b753b62257e66a800/internal/command/command_virtual.go#L98-L100
Should it be enabled or configurable?

Should it be enabled or configurable?

I wish I could remember the logic because it wasn't just always on or always off. Do you see anything in the runnerv1 implementation that's revelatory?

I wish I could remember the logic because it wasn't just always on or always off. Do you see anything in the runnerv1 implementation that's revelatory?

In the runnerv1 service, echo is always enabled. When using the CLI, executing a program which is a file or shell, and the block is marked as interactive, which is a default, then echo is disabled. I am not sure if it was well thought out, but the fact is that in runnerv2 echo is always disabled. Should I flip it to stay compatible?

@adambabik when you search for DisableEcho it appears that the echo is enabled when a TTY is attached which is always true for a VirtualCommand, no?

This is true and VirtualCommand is used when the block is interactive, which is a default.

@sourishkrout yes, let's go ahead and flip it please. Being "incompatible" otherwise means the integration with the notebook terminal stops working as expected.

@sourishkrout I merged #576. Let me know if there is anything else that should be done as a part of this ticket.

@sourishkrout I merged #576. Let me know if there is anything else that should be done as a part of this ticket.

This looks good now 👍 . Thank you!


make basic CODA searching function

@ChrisC28 : can you drop in links to the 2018 PQ file(s) ?
@BecCowley : anything about DuckDB (?) or bits of code ?


robots.txt Disallow not respected

I have a setup like this in my robots.txt:
User-agent: my_crawler
Crawl-delay: 1

User-agent: * # match all bots
Crawl-delay: 10 # per http://en.wikipedia.org/wiki/Robots.txt#Nonstandard_extensions, sets number of seconds to wait between requests to 5 seconds. may not work
Request-rate: 1/5 # per http://en.wikipedia.org/wiki/Robots.txt#Extended_Standard, maximum rate is one page every 5 seconds. may not work
#--snip lots of directives--
Disallow: /login.action # remove the login page
Disallow: /login.action? # remove the login page derivatives
#--snip some more--

Log snippet from my web server:
crawler.ip.address - - [15/Jan/2018:23:17:39 +0200] "GET /login.action?os_destination=%2F HTTP/1.1" 200 58895

Corresponding snippet from the Collector's log:
wiki: 2018-01-15 23:17:39 INFO -          DOCUMENT_FETCHED: https://wiki.mydomain.fi/login.action?os_destination=%2F
wiki: 2018-01-15 23:17:39 INFO -       CREATED_ROBOTS_META: https://wiki.mydomain.fi/login.action?os_destination=%2F
wiki: 2018-01-15 23:17:39 INFO - REJECTED_ROBOTS_META_NOINDEX: https://wiki.mydomain.fi/login.action?os_destination=%2F

My config:
<httpcollector id="mycrawler">
    #set($http      = "com.norconex.collector.http")
    #set($robotsTxt         = "${http}.robot.impl.StandardRobotsTxtProvider")
    <crawlerDefaults>
        <robotsTxt ignore="false" class="$robotsTxt"/>
        <!-- ... -->
    </crawlerDefaults>

    <!-- ... -->
</httpcollector>

I am using HTTP Collector 2.7.1.

I narrowed it down. My robots.txt contains a section that is an exact match for my crawler's userAgent:
User-Agent: my_crawler
Crawl-delay: 1

This section sets no Disallow directives. However there is another section targeting all user-agents and containing many Disallow directives:
User-Agent: *
Crawl-delay: 10
Disallow: [REDACTED]
-snip-

If I unset <userAgent>my_crawler</userAgent> or change it to string that doesn't match the first section, I get a REJECTED_ROBOTS_TXT event as expected.

Good catch.  Looks like it works as expected then. Can we close this issue?

No. Your implementation is wrong. The problem is in StandardRobotsTxtProvider.
Compare to http://www.robotstxt.org/norobots-rfc.txt, lines 427–486:
4. Examples

   This section contains an example of how a /robots.txt may be used.

   A fictional site may have the following URLs:

     http://www.fict.org/
     http://www.fict.org/index.html
     http://www.fict.org/robots.txt
     http://www.fict.org/server.html
     http://www.fict.org/services/fast.html
     http://www.fict.org/services/slow.html
     http://www.fict.org/orgo.gif
     http://www.fict.org/org/about.html
     http://www.fict.org/org/plans.html
     http://www.fict.org/%7Ejim/jim.html
     http://www.fict.org/%7Emak/mak.html

   The site may in the /robots.txt have specific rules for robots that
   send a HTTP User-agent "UnhipBot/0.1", "WebCrawler/3.0", and

Koster                draft-koster-robots-00.txt                [Page 8]

INTERNET DRAFT        A Method for Robots Control       December 4, 1996

   "Excite/1.0", and a set of default rules:

      # /robots.txt for http://www.fict.org/
      # comments to<EMAIL_ADDRESS>
      User-agent: unhipbot
      Disallow: /

      User-agent: webcrawler
      User-agent: excite
      Disallow:

      User-agent: *
      Disallow: /org/plans.html
      Allow: /org/
      Allow: /serv
      Allow: /~mak
     Disallow: /

   The following matrix shows which robots are allowed to access URLs:

                                               unhipbot webcrawler other
                                                        & excite
     http://www.fict.org/                         No       Yes       No
     http://www.fict.org/index.html               No       Yes       No
     http://www.fict.org/robots.txt               Yes      Yes       Yes
     http://www.fict.org/server.html              No       Yes       Yes
     http://www.fict.org/services/fast.html       No       Yes       Yes
     http://www.fict.org/services/slow.html       No       Yes       Yes
     http://www.fict.org/orgo.gif                 No       Yes       No
     http://www.fict.org/org/about.html           No       Yes       Yes
     http://www.fict.org/org/plans.html           No       Yes       No
     http://www.fict.org/%7Ejim/jim.html          No       Yes       No
     http://www.fict.org/%7Emak/mak.html          No       Yes       Yes

Norconex HTTP Collector explicitly stops parsing after a block with an exact-match User-agent. This is not correct behavior, it should also parse all User-agent: * blocks.

Where do you get it is wrong? If there is a match for your user-agent, that is the record block to be used.  ONLY if there is no match for it that User-agent: * gets used.  This is described in the same specs you mention:

The robot must obey the first record in /robots.txt that contains a User-
Agent line whose value contains the name token of the robot as a
substring. The name comparisons are case-insensitive. If no such
record exists, it should obey the first record with a User-agent
line with a "*" value, if present. If no record satisfied either
condition, or no records are present at all, access is unlimited.

This is also what the examples you copied are illustrating.  If you want my_crawler to disallow some paths, you have to include those under my_crawler.
This is also reinforced by Google (https://developers.google.com/search/reference/robots_txt):

Only one group of group-member records is valid for a particular crawler. The crawler must determine the correct group of records by finding the group with the most specific user-agent that still matches. All other groups of records are ignored by the crawler.

Unless you can find evidence of the contrary in the specifications, I am afraid you will have to modify your robots.txt or change your user-agent (or apply filtering rules yourself in the Collector config).
Please confirm.

Confirmed, you are correct. I have read the documentation incorrectly. Apologies for my previous, unnecessarily blunt message, as well!


Fix small typo in install docs

Something I stumbled upon while reading the install docs.

Thanks for the contribution.
I've changed the base branch to develop (as specified at our docs: https://enigma.co/catalyst/development-guidelines.html#git-branching-structure)
Thanks!

Pull Request Test Coverage Report for Build 131

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

Totals

Change from base Build 117:
0.0%

Covered Lines:

Relevant Lines:
0

💛  - Coveralls


Chapter 2 Code: combine-all

Hi,
I'm not great with GitHub so I'm not sure if I'm using it right. Basically if you look at the full text of chapter 2 you'll see there's a definition there for combined-all, repeated below:
(defun combine-all (xlist ylist)
"Return a list of lists formed by appending a y to an x.
E.g., (combine-all '((a) (b)) '((1) (2)))
-> ((A 1) (B 1) (A 2) (B 2))."
(mappend #'(lambda (y)
(mapcar #'(lambda (x) (append . y)) xlist))
ylist))
Note that the append does not refer to x as it should. This error does not appear in the .lisp file collation of the code from this chapter.

Ah, the error wasn't in the cleaner source, from Safari; it was in the original, OCR'ed version, and I brought it in when I salvaged earlier work.
Copying the code from simple.lisp fixed this.


Normalize: Tencent.qq-devtool version 0.3.4

This is an automated pull request
Microsoft Reviewers: Open in CodeFlow

Duplicate of #76472


Allows custom headers in http requests

I changed the http request functions to allow an extra headers object before the final callback. I added a little hack in the _performSecureRequest() function to prevent this from breaking compatibility.

Is this dead? I'd also like the ability to pass custom request headers on HTTP GET requests. I can add it, with your guys' blessing.

this commit seems to be, there are other outstanding issues offerring the same feature.

Which? I want this badly enough that I'll collaborate/lead getting it in.


Make _cohort.py module a public module

Description
Since classes in _cohort.py are going to be used in user facing notebook, so making this module a public module.
Areas changed

npm packages changed:

[ ] responsibleai/causality
[ ] responsibleai/core-ui
[ ] responsibleai/counterfactuals
[ ] responsibleai/dataset-explorer
[ ] responsibleai/fairness
[ ] responsibleai/interpret
[ ] responsibleai/localization
[ ] responsibleai/mlchartlib
[ ] responsibleai/model-assessment

Python packages changed:

[x] raiwidgets
[ ] responsibleai
[ ] erroranalysis
[ ] rai_core_flask

Tests

[x] No new tests required.
[ ] New tests for the added feature are part of this PR.
[ ] I validated the changes manually.

Screenshots (if appropriate):
Documentation:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Codecov Report

Merging #1253 (092537f) into main (ce9521a) will decrease coverage by 18.66%.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##             main    #1253       +/-   ##
===========================================
- Coverage   65.58%   46.92%   -18.67%
===========================================
  Files          91       46       -45
  Lines        4504     2549     -1955
===========================================
- Hits         2954     1196     -1758
+ Misses       1550     1353      -197

Flag
Coverage Δ

unittests
46.92% <0.00%> (-18.67%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

raiwidgets/raiwidgets/cohort.py
0.00% <ø> (ø)

...idgets/raiwidgets/responsibleai_dashboard_input.py
0.00% <0.00%> (ø)

responsibleai/responsibleai/_tools/__init__.py

...ponsibleai/responsibleai/rai_insights/constants.py

...sponsibleai/responsibleai/managers/base_manager.py

.../responsibleai/modelanalysis/constants/__init__.py

...tools/error_analysis/dashboard_schemas/__init__.py

responsibleai/responsibleai/managers/__init__.py

...bleai/responsibleai/_tools/causal/causal_config.py

...ibleai/responsibleai/managers/explainer_manager.py

... and 37 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 ce9521a...092537f. Read the comment docs.


Midstream errors not working?

I don't know if this is expected but I don't appear to be getting any indication that the invocation failed when calling the function url of the demo:stream_throw example:
$ curl https://XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.lambda-url.eu-west-1.on.aws/
Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

@Nirlah any idea what could be happening here?

The runtime doesn’t interfere with the raw payloads to/from the Lambda service; it’s up to you to catch the error and stream an appropriate response (or take any other action desired).
If you enable CloudWatch Logs for the function, using the Zig’s standard error logs should be tracked over there. Any unhandled error that is returned from the handler is automatically logged by the runtime. (please open a bug if this is not the case 😅)

Ok, it indeed seems that the stream_throw demo no longer work – I will look into it...

Also this is unrelated to this issue but I saw that when calling Channel.write() the data is automatically flushed. In my case I have multiple byte arrays I want to send at the same time in a single chunk. Perhaps it would be better to move out the flush call to a separate Channel.flush() function? I could make a PR for this if you'd like.


Frontend

Mock: https://www.figma.com/proto/MxcADlWgz6Z8XdwXwFuzVU/BTC%2FUSDT?node-id=2%3A81&scaling=scale-down

implement simple ui according to the mock without the browser extension
build variables

~for asset ids (bitcoin, usdt)~. not needed as returned by wallet
~for esplora (blockstream vs localhost)~ dealt with in wallet

done in #31


Skip test_ptds under cuda-memcheck

This is another test that hangs under cuda-memcheck, so a skip is added for it.

gpuci run tests

From OOB conversation with @gmarkall, as I could not reproduce the process hang locally, this is probably hardware/driver specific. Further the test being skipped doesn't have anything to do with out of bounds access so it's probably fine to skip this under memcheck as the convenience of being able to run the entire suite under memcheck outweighs the risk involved with this skipping this PTDS test.


Fixes incorrect usage of except

Instead of depending on an Error on open(), we now use an if-else to check if apikey.yml exists instead before using env variables.
Fixes #3.

Whoops, wrong branch.


Etaler backend re-architecture

The current backend architecture works well of out purpose. But it is not salable (in a programming sense) enough and will cause problems down the line. For the backend system to work, i.e. direct function calls to the correct backend depending using the CPU or GPU, we currently uses C++'s virtual class methods. While this is the obvious and correct solution, Adding new methods to a backend in is pain. First et::Backend and on of et::CPUBackend and et::GPUBackend have to be modified. Causing a total recompilation of the library (since almost everything depends on et::Backend). Furthermore, this changes the vtable layout and makes versions with different backend methods not binary compatible with each other.
The current design also does not allow runtime expansion of the backend. For example, adding linear algebra functions dynamically to a base backend is not allowed. Even with inheritance. It allows one to add new methods, Yet these methods won't be accessible from et::Backend* so no one can access them.
My proposal is to re-architect the backend that the et::Backend class essentially exposes two methods only, register_function and get_function. Where register_function is used to by the backend to register which methods are available from the backend and get_function returns a std::function (a callable object) to the method. This way the frontend could ask the beckend which functions are available at runtime and allows expansion of the backend by adding more methods after initialization.
Here's a tiny Proof of Concept
#include <iostream>
#include <string>
#include <vector>
#include <utility>
#include <functional>
#include <map>
#include <any>

struct BackendBase
{
        std::map<std::string, std::any> funcs_;
        template<typename Class, typename Return, typename ...Args>
        void expose_method(const std::string& name, Return(Class::*func)(Args...))
        {
                funcs_[name] = std::function<Return(Args...)>([this, func](Args ... args){
                        (static_cast<Class*>(this)->*func)(args...);
                });
        }
        template <typename Func>
        std::function<Func> get_method(const std::string& name)
        {
                return std::any_cast<std::function<Func>>(funcs_.at(name));
        }
};

struct Backend1 : public BackendBase
{
        void foo() { std::cout << "foo() from backend1" << std::endl; }
        Backend1() { expose_method("foo", &Backend1::foo); }
};

struct Backend2 : public BackendBase
{
        void foo() { std::cout << "foo() from backend2" << std::endl; }
        Backend2() { expose_method("foo", &Backend2::foo); }
};

int main()
{
        Backend1 b;
        std::cout << b.funcs_["foo"].type().name() << std::endl;
        b.get_method<void()>("foo")();
        Backend2 c;
        std::cout << c.funcs_["foo"].type().name() << std::endl;
        c.get_method<void()>("foo")();
}

Note for myself: Like how one of my old project is written. But better, no dynamic_cast and no more BoxedValues

Note: PyTorch uses a more monolithic approach. PyTorch doesn't have a 'backend` per say, but each tensor operator tries to support computing on different hardware. ex:
void add(const tensor& a, const tensor& b, tensor& out)
{
        if(a.on_cpu())
                add_on_cpu(...);
        else if(a.on_cuda())
                add_on_cuda(...);
}

This doesn't support expansions to be backend, but it may not matter. Just update the tensor operators to support more hardware. This have a lower overhead and doesn't have crazy syntax to access a function. But no expansions allowed.

Quick update, this modified code is slightly faster than the above code. 1. Returns a reference to std::function and reads a reference of std::function from std::any. 2. Use a std::string_view as key instead of std::string. But this feature requires C++20
 struct BackendBase
 {
         std::map<std::string, std::any> funcs_;

         template<typename Class, typename Return, typename ...Args>
         void expose_method(const std::string& name, Return(Class::*func)(Args...))
         {
                 funcs_[name] = std::function<Return(Args...)>([this, func](Args ... args) {
                         (static_cast<Class*>(this)->*func)(args...);
                 });
         }

         template <typename Func>
         const std::function<Func>& get_method(const std::string_view& name)
         {
                 return std::any_cast<const std::function<Func>&>(funcs_.at(name));
         }
 };

This is not the final design tho. I still want to remove the use of std::function and use a custom, more specific class. Hopefully the method wrapper can ensure no allocation what so ever.


reloading frame object

Is there a way to reload the frame object with a new image or video?

Yes, use the .src() method
On Thu, Mar 31, 2016, 10:46 AM aelmahalawey<EMAIL_ADDRESS>wrote:

Is there a way to reload the frame object with a new image or video?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/littlstar/axis/issues/70

Thanks


Moving primitive parameters to cell generator

Moving primitive parameters from annotation to cell generator

Moving primitive parameters from annotation to cell generator

This is a pretty old PR @arvuce22 @kkunal1408
Can we merge master if we still want to get this in? Doesn't look like the main goal of the PR (Moving primitive parameter generation from annotation to cell generator) has been done yet.

we can close this PR. This movement has already been done and integrated into the master.  We may need to improve it though which should be a new PR.


2.07 291 all the 721 token can not be displayed

After kill the app , restart, they display as normal.
Haven’t found out how to reproduce it.

Should be fixed by #1452 and possibly these are related: #1429, #1442


Make a start on the message handlers

Thought it might be better to review in bits, so avat.

Hold that thought, didn't actually review the whole thread!


DBR version for sc and sqlContext support in Python

Hi team, for this portion of the documentation: I wonder if it really means that new limitations exist in newer DBR versions but didn't exist in earlier DBR versions?:
Instead of:
Spark API limitations for Unity Catalog shared access mode

Cannot use RDD APIs, or clients that directly read the data from cloud storage, such as DBUtils.
Spark Context (sc) and sqlContext and not supported for Scala in any Databricks Runtime and are not supported in Python in Databricks Runtime 14.0 and above.

On the second bullet, shouldn't it say:

Spark Context (sc) and sqlContext and not supported for Scala in any Databricks Runtime and are supported in Python in Databricks Runtime 14.0 and above.

or maybe:

Spark Context (sc) and sqlContext and not supported for Scala in any Databricks Runtime and are not supported in Python in Databricks Runtime below 14.0 (i.e., 13.3 and below).

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

ID: 73652598-fdb7-54a6-3dcd-0f73fac5de51
Version Independent ID: 73652598-fdb7-54a6-3dcd-0f73fac5de51
Content: Compute access mode limitations for Unity Catalog - Azure Databricks
Content Source: databricks/compute/access-mode-limitations.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

@veronicagomes-db
Thanks for your feedback! We will investigate and update as appropriate.

@veronicagomes-db
Thank you for bringing this to our attention.
I've delegated this to content author @mssaperla, who will review it and offer their insightful opinions.


Multi-fidelity dgp fixes

Issue #, if available: #224
Description of changes: This notebook should now replicate the experiments in the arxiv paper, before there were a couple of bugs.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #225 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #225      +/-   ##
==========================================
+ Coverage   89.26%   89.27%   +<.01%
==========================================
  Files         109      109
  Lines        3028     3029       +1
  Branches      309      310       +1
==========================================
+ Hits         2703     2704       +1
  Misses        266      266
  Partials       59       59

Impacted Files
Coverage Δ

emukit/test_functions/multi_fidelity/branin.py
100% <100%> (ø)
: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 1ea0578...29d7b72. Read the comment docs.


wip

Codecov Report

Merging #58 (33a2e9f) into master (950ba1a) will decrease coverage by 1.25%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##           master      #58      +/-   ##
==========================================
- Coverage   97.16%   95.90%   -1.26%
==========================================
  Files           7        7
  Lines         423      415       -8
==========================================
- Hits          411      398      -13
- Misses         12       17       +5

Impacted Files
Coverage Δ

service/routes.py
96.53% <50.00%> (-2.92%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


There is no selection to uae4arm core in Retroarch

Game console: R36S (RK3326).
Distro Version: ArkOS 2.0 (12222023)
Retroarch: 1.16.0 (14cb3732eb) 03 Oct. 2023
GCC (8.3.0) 64-bit
In ArkOS menu there are 3 options for AMIGA emulation:

STANDALONE

AUTO

Retroarch

PUAE2021
PUAE

Retroarch32

UAE4ARM

I NEED exactly UAE4ARM (NOT PUAE2021 or PUAE, because of it's BEST of all with good performance for most games).
But it;s not possible to select Retroarch\UAE4ARM (Retroarch32\UAE4ARM only), but in this case, there is NO CD-32 and CDTV support at all in Retroarch32:
AUTO
A500
A600
A1200
But if I run Retroarch directly and load UAE4ARM core, I see ALL of options, including CDTV & CD32:
AUTO
A500
A600
A1200
CDTV
CD32
So, if Retroarch HAVE UAE4ARM core (and it's BETTER, than UAE4ARM core in Retroarch32, why i CAN'T select it in ArkOS menu?!

Because there was never a request to add support for the 64bit version of uae4arm to the Emulationstation menu.

Why?!
It seems like the BEST Amiga\CD32 emulation core for such low\middle end devices (by performance).
And why Retroarch32\UAE4ARM core missing CDTV & CD32 emulation?
In any case, is it possible to add these features?
Thanks in advance.

No need to get so excited.  Everyone doesn't play Amiga.  It's not as popular as other consoles and some are probably satisfied with uae4arm on the 32bit side because it satisfies what they want the emulator to do.  Some prefer puae2021.  Either way support in emulationstation for those emulators have been added as they've been requested where possible.  I will include that in the next update.  The standalone amiberry emulator does not have virtual keyboard support because it hasn't been updated since last year or so.  I'll review the possibility of updating that emulator as virtual keyboard support was added back in January of this year.

Hi Christian!
Do you have any idea when this modification to Amiga support will be available?
Thanks, and keep up the excellent work! :)

Sometime this month

This has been addressed with today's update.


[Question] Pin show label all time

Is there any way to show the labels of all pins in the map at the same time?
Regards

Not support it.
Because Google Maps Android/iOS SDK does not support it.


ArrowFormat does not work with pyarrow 15.0.0

If you try to do something like this:
from yt.wrapper import YtClient
from yt.wrapper.default_config import get_config_from_env
from yt.wrapper.format import ArrowFormat
import pyarrow

def main():
    client = YtClient(get_config_from_env())

    table_stream = client.read_table("//tmp/table", ArrowFormat(raw=True))

    total_size = 0
    with pyarrow.ipc.open_stream(table_stream) as reader:
        print(reader.schema)
        for batch in reader:
            total_size += len(batch)

    print(total_size)

main()

You will gеt
Traceback (most recent call last):
  File "/home/echunaev/.local/lib/python3.11/site-packages/pyarrow/ipc.py", line 52, in __init__
    self._open(source, options=options, memory_pool=memory_pool)
AttributeError: 'ResponseStreamWithReadRow' object has no attribute 'closed'
Traceback (most recent call last):
    with pyarrow.ipc.open_stream(table_stream) as reader:
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
# <some lines>
  File "/home/echunaev/.local/lib/python3.11/site-packages/pyarrow/ipc.py", line 190, in open_stream
    return RecordBatchStreamReader(source, options=options,
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/echunaev/.local/lib/python3.11/site-packages/pyarrow/ipc.py", line 52, in __init__
    self._open(source, options=options, memory_pool=memory_pool)
  File "pyarrow/ipc.pxi", line 972, in pyarrow.lib._RecordBatchStreamReader._open
  File "pyarrow/ipc.pxi", line 596, in pyarrow.lib._get_input_stream
  File "pyarrow/io.pxi", line 2059, in pyarrow.lib.get_input_stream
  File "pyarrow/io.pxi", line 215, in pyarrow.lib.NativeFile.get_input_stream
  File "pyarrow/io.pxi", line 227, in pyarrow.lib.NativeFile._assert_readable
  File "pyarrow/io.pxi", line 224, in pyarrow.lib.NativeFile._assert_open
ValueError: I/O operation on closed file

Make ResponseStream looks more file-like - it seems like a is good idea

Are you sure that this is ok for EmptyResponseStream?
https://github.com/ytsaurus/ytsaurus/blob/4761dbf01008cb5dc9a34f4cc81e2794412ce7aa/yt/python/yt/wrapper/response_stream.py#L156-L158
You will get confusing error because stream is closed before first read from it.


Update project and file level licenses

Type: Incomplete
Summary:
Update project and file level licenses
Details:
The top-level license for this component should be 'LGPL-3.0-or-later'.
Some files were mistakenly identified as 'LGPL-2.0-or-later' when the license headers say '3.0-or-later'. Files following the pattern ''psycopg/adapter*.{h,c}'' and ''psycopg/microprotocol*.{h,c}'' are dual-licensed 'LGPL OR Zlib'.
Resolution:
Updated project level license as well as individual file licenses where incorrect discovery occurred. Files which are dual-licensed under Zlib have also been updated to reflect this...
https://github.com/psycopg/psycopg2/blob/2_8_2/LICENSE (See "Alternative licenses" at bottom)
Affected definitions:

psycopg2 2.8.2

Hi folks - I'd like to see how review of this is going. Do we have any questions that still need answering here? If so, @bduranc could you work with @ariel11 on this? Don't want this to linger without either some issues identified, merge, or close by the 30 days mark.

@fossygirl - No questions at the moment.  I grabbed it from the end of the queue because of the 30 day goal.  However, I have to double-check each file and you can see the diff is 161 lines. Im working on it.  Thanks

Great, thanks for the update, @ariel11!

@bduranc - noting that https://pypi.org/project/psycopg2/2.8.2/ says the “license” is “GNU Library or Lesser General Public License (LGPL), Zope Public License (LGPL with exceptions or ZPL).”  However, I don’t see any reference to the Zope Public License in the source repo.
As you mention above, if you go to the source for tagged version 2.8.2, the license is https://raw.githubusercontent.com/psycopg/psycopg2/324cded1661995cc006e04e2c5e6b00e61ab74ba/LICENSE, which says “LGPLv3 or later” with a “special exception” for linking to OpenSSL  OR a bsd-like license, which is the Zlib license.
It appears that maybe the reference to the ZPL is a mistake on https://pypi.org/project/psycopg2/2.8.2/ ...?

@ariel11: That is my theory as well.
If you look at the history of LICENSE.MD, you will see that older versions as far back as 2.4.0 had some mention of the ZPL as an alternative license (see: https://github.com/psycopg/psycopg2/commit/611606d53294ec68ab61aea9ba9149d3c6da4750#diff-9879d6db96fd29134fc802214163b95a).
I cannot find any obvious mention of the same in 2.8.2.

@bduranc - what do you make of the mention of the Zope license on this file - https://github.com/psycopg/psycopg2/blob/324cded1661995cc006e04e2c5e6b00e61ab74ba/setup.py (row 59)?  It's the only reference I saw on the files curated in this PR.

@bduranc - I am going to change the "Declared" license to "OTHER" because the license for this version says LGPL with a special exception and there is not a SPDX for that scenario. I merged your other file level curations.  Thanks


Clarification of MI_OVERRIDE and mimalloc-new-delete.h

Does MI_OVERRIDE=ON cmake option imply that new/delete are overridden in addition to the C malloc/etc interface?
If I compile with MI_OVERRIDE on Linux, I get "multiple definition" linker errors when I try to #include <mimalloc-new-delete.h>
Here are the messages from gcc-10:
/usr/bin/ld: submodules/mimalloc/libmimalloc-debug.a(alloc.c.o): in function `operator new(unsigned long, std::nothrow_t const&)':
/home/hans/openscad_malloc/submodules/mimalloc/src/alloc-override.c:190: multiple definition of `operator new(unsigned long, std::nothrow_t const&)'; CMakeFiles/OpenSCAD.dir/src/openscad.cc.o:/home/hans/openscad_malloc/submodules/mimalloc/include/mimalloc-new-delete.h:31: first defined here
/usr/bin/ld: submodules/mimalloc/libmimalloc-debug.a(alloc.c.o): in function `operator new[](unsigned long, std::nothrow_t const&)':
/home/hans/openscad_malloc/submodules/mimalloc/src/alloc-override.c:191: multiple definition of `operator new[](unsigned long, std::nothrow_t const&)'; CMakeFiles/OpenSCAD.dir/src/openscad.cc.o:/home/hans/openscad_malloc/submodules/mimalloc/include/mimalloc-new-delete.h:32: first defined here
/usr/bin/ld: submodules/mimalloc/libmimalloc-debug.a(alloc.c.o): in function `mi_free':
/home/hans/openscad_malloc/submodules/mimalloc/src/alloc.c:481: multiple definition of `operator delete[](void*)'; CMakeFiles/OpenSCAD.dir/src/openscad.cc.o:/home/hans/openscad_malloc/submodules/mimalloc/include/mimalloc-new-delete.h:26: first defined here
/usr/bin/ld: submodules/mimalloc/libmimalloc-debug.a(alloc.c.o): in function `mi_free':
/home/hans/openscad_malloc/submodules/mimalloc/src/alloc.c:481: multiple definition of `operator delete(void*)'; CMakeFiles/OpenSCAD.dir/src/openscad.cc.o:/home/hans/openscad_malloc/submodules/mimalloc/include/mimalloc-new-delete.h:25: first defined here
/usr/bin/ld: submodules/mimalloc/libmimalloc-debug.a(alloc.c.o): in function `mi_free_size':
/home/hans/openscad_malloc/submodules/mimalloc/src/alloc.c:576: multiple definition of `operator delete[](void*, unsigned long)'; CMakeFiles/OpenSCAD.dir/src/openscad.cc.o:/home/hans/openscad_malloc/submodules/mimalloc/include/mimalloc-new-delete.h:36: first defined here
/usr/bin/ld: submodules/mimalloc/libmimalloc-debug.a(alloc.c.o): in function `mi_free_size':
/home/hans/openscad_malloc/submodules/mimalloc/src/alloc.c:576: multiple definition of `operator delete(void*, unsigned long)'; CMakeFiles/OpenSCAD.dir/src/openscad.cc.o:/home/hans/openscad_malloc/submodules/mimalloc/include/mimalloc-new-delete.h:35: first defined here
/usr/bin/ld: submodules/mimalloc/libmimalloc-debug.a(alloc.c.o): in function `mi_new':
/home/hans/openscad_malloc/submodules/mimalloc/src/alloc.c:857: multiple definition of `operator new[](unsigned long)'; CMakeFiles/OpenSCAD.dir/src/openscad.cc.o:/home/hans/openscad_malloc/submodules/mimalloc/include/mimalloc-new-delete.h:29: first defined here
/usr/bin/ld: submodules/mimalloc/libmimalloc-debug.a(alloc.c.o): in function `mi_new':
/home/hans/openscad_malloc/submodules/mimalloc/src/alloc.c:857: multiple definition of `operator new(unsigned long)'; CMakeFiles/OpenSCAD.dir/src/openscad.cc.o:/home/hans/openscad_malloc/submodules/mimalloc/include/mimalloc-new-delete.h:28: first defined here

(I got even stranger messages if I tried to build with clang-14, where it claimed they were redefined in boost/system/detail/std_interoperability.hpp which I assume was some kind of compiler bug since I saw no such definitions in that file)
Is the answer specific to target OS?  (i.e. MI_OVERRIDE implies new/delete override, everywhere EXCEPT on Windows?)
I'm wondering about this since MI_OVERRIDE defaults ON, and I see this preprocessor conditional in the tests:
https://github.com/microsoft/mimalloc/blob/38a03229c89afbf2722e48c63da696bf11589dee/test/main-override.cpp#L17-L19

Thanks @thehans for all your feedback!
I can see it is a bit confusing and will try to improve the documentation; However, it is partly confusing because there is inherent complexity in many ways to override malloc: use #defines (mimalloc-override.h), use static linking override (mimalloc-override.o), use dynamic override (e.g. LD_PRELOAD), use from C or C++, and the various ways the different OS's and linkers work.  It would be great if there is was one standard way to do things but there just isn't and the right way depends the application.
Having said that:

MI_OVERRIDE=ON defines all the standard malloc api entry points, and also the C++ new/delete entry points. The only reason to disable this is either that you never use it (as the application calls the mi_ api's specifically), or when you linker would complain about multiple definitions (as on Windows without weak symbols).

On Unix systems, you can thus use static linking override, or LD_PRELOAD, such that all allocation goes via mimalloc.

However, if you compile mimalloc with MI_OVERRIDE=ON, and also include mimalloc-new-delete.h in your application you will now define the overrides for C++ new/delete twice (once in libmimalloc and once in your application) so that it is where your errors come from.

But on Windows, each DLL has its own namespace, and when overriding it uses dynamic patching which can only redirect basic malloc/free calls. That means that each C++ (application) module uses its own new/delete which eventually will call the (redirected) malloc/free. This turns out to be not as efficient as it can be and it is better to then overload the C++ new/delete to directly use the mimalloc ones where possible -- hence, on Windows with dynamic overriding, you should include mimalloc-new-delete.h if you can.

Of course, if Boost for example also overrides C++ new/delete then that is another conflict. Not sure if that is what you saw with clang-14.

And on macOS ...

As you can see, a lot of this is beyond the scope of mimalloc but more about linking C/C++ on various platforms. I will try if I can make this more clear with a nice diagram or something. The current goal is at least to make everything work out-of-the-box on the various platforms without needing special make flags etc.

https://github.com/microsoft/mimalloc/issues/559#issuecomment-1916408486


Refining process maps to inform user stories

The context: This ticket is a continuation of the work done for ticket #998. For ticket #998, the following process maps were created and received feedback from IRC/SMEs and developers: contact management, operation-dependent paths, and sales and transfers
The goal: To refine the following process maps, by soliciting feedback from IRC/SMEs

[ ] Reporting operation and facility events (new, previously sales and transfers process)
[ ] Operation-dependent paths
[ ] Contact management
[ ] Invalidating BORO ID (new)

Acceptance criteria

[ ] Solicit synchronous and asynchronous feedback from IRC/SMEs and developers
[ ] Consolidate a list of user and business area requirements, to be added to the user stories

Hey @hannavovk and @nanyangpro! Could I get your eyes on this ticket I created as a "part 2" for ticket #998? I created this new ticket instead of altering the previous ticket as the acceptance criteria are a bit different


Removing secrets from CICD: Part I Docs and local

First iteration

It seems that the same entrypoint as the centos images (-smp -np 2)
docker run \
    --name mapdl \
    --restart always \
    --health-cmd="ps aux | grep \"[/]ansys_inc/.*ansys\.e.*grpc\" -q && echo 0 || echo 1" \
    --health-interval=0.5s \
    --health-retries=4 \
    --health-timeout=0.5s \
    --health-start-period=10s \
    -e ANSYSLMD_LICENSE_FILE=1055@$LICENSE_SERVER \
    -e ANSYS_LOCK="OFF" \
    -p $PYMAPDL_PORT:50052 \
    -p $PYMAPDL_DB_PORT:50055 \
    --shm-size=1gb \
    -e I_MPI_SHM_LMT=shm \
    -e P_SCHEMA=/ansys_inc/ansys/ac4/schema \
    --oom-kill-disable \
    --memory=6656MB  \
    --memory-swap=16896MB \
    $MAPDL_IMAGE \
    -$DISTRIBUTED_MODE -np 2 > log.txt &

Gives the following error:
Status: Downloaded newer image for ghcr.io/ansys/mapdl:v24.1-ubuntu-student
ghcr.io/ansys/mapdl:v24.1-ubuntu-student
Abort(15) on node 0 (rank 0 in comm 0): application called MPI_Abort(MPI_COMM_WORLD, 15) - process 0
Error: Process completed with exit code 1.

However it seems to work if I remove most of the stuff:
docker run \
    --name mapdl \
    --restart always \
    -e ANSYS_LOCK="OFF" \
    -p $PYMAPDL_PORT:50052 \
    -p $PYMAPDL_DB_PORT:50055 \
    --shm-size=2gb \
    -e P_SCHEMA=/ansys_inc/v241/ansys/ac4/schema \
    $MAPDL_IMAGE > log.txt &
# grep -q 'Server listening on' <(timeout 60 tail -f log.txt)

I had to disable the following tests:
test_license_type_keyword
Because the licenses we were pinging are not the student license. I should look for this license name.
test_license_type_keyword_names
Because it was taking too long (timeout)
I have also seen:
Maximum licensed number of demo users already reached.

Probably because several instances running.... I wonder if this is going to be an issue in the pool module

LGTM

@pyansys-ci-bot LGTM


images/pdm.svg is missing (causing a server error)

When rendering an image with a PD license, OL is blowing up because this image is missing.

Found and fixed


Update phone-number-management-for-the-u-s.md

https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/4011
Changed wording.

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@CarolynRowe PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


'alias as' syntax support

Hey!
Thanks for the great plugin. Unfortunately, closure templates have got a few syntax changes since the last plugin version was released.
This effort is a first step on the way of fixing that. It fixes the support of {alias name.space as sp} construction. For now, it's only parsing, no support for navigation.
The actual changes - are only about 10 lines, but I had to apply some effort in order to compile the project successfully.
Before:

After:

I am no longer involved with or using Closure Templates. I haven't opened this project in about a year. Would you be interested in gaining rights to this project? I would also look into changing ownership on the JetBrains plugin repo, if you are interested.


Is that possible to make ES6/ES5 module configurable?

Hi Conductor team,
I understand how we switch the ES6 and ES5 currently, by using the same "ElasticSearchModule" class presented in both es6 and es5 dependency jar file. Is that possible to make it configurable like how we hook up with other modules? By changing following logic a little bit, maybe using String value of a class name to create the module?
The reason that we request this is, we are currently building conductor server in our own gradle build process by using conductor-server-all.jar It is not easy to replace an individual jar file in that server-all.jar as the server-all.jar mesh all of the classes together from all dependency jar files.
If this is not possible, why dont we keep the ES6 as default version, why use ES5 as default? Is there any reason behind it? We want to use latest version as possible to reduce any security/performance issues.
    if (configuration.isIndexingPersistenceEnabled())
        modules.add(new ElasticSearchModule());
    else
        modules.add(new NoopIndexModule());

@willqiao The ES6 module is currently published as a shadowJar to avoid dependency conflicts with ES5 which is the default ES version in conductor 2.x
When we upgrade Conductor to the next major version 3.x, we plan to make ES6 as the default and remove ES5.


Crash when passing a path parameter created inside useDerivedValue

Description
I'm getting the following error:
Missing one or more required properties path in the skPath component.
Version
0.1.188
Steps to reproduce

Create a path inside a Reanimated useDerivedValue hook. It doesn't matter if it consumes a SharedValue or not.
Pass it to a Path component
The app will crash at runtime complaining that the path parameter is missing. Doing console.log of the path object inside useDerivedValue will log an empty object {}.

Snack, code example, screenshot, or link to a repository

const path= useDerivedValue(() => {
    const p = Skia.Path.Make();
    p.addArc(
      {
        x: 15,
        y: 15,
        width: 15,
        height: 15,
      },
      -90,
      -45
    );
    return p;
  });

<Canvas style={{ width: "100%", height: "100%" }}>
            <Path path={path} color="#ff08" strokeWidth={8} style="stroke" />
</Canvas>

I've updated to REA 3.3.0 on iOS and it still seems to be crashing with the same error.

I wasn't able to reproduce the crash based on the example you provided but please feel free to reopen if you have a small repo to reproduce the issue or other pointer on what the issue might be.

@drookyn any chance you would have a small standalone example that give me an change to reproduce the issue on Android?

I'm running into this issue as well on both Android and iOS. I'm happy to cook up a repro if it's of any use, but have a similar scenario: creating an SkPath inside of a useDerivedValue and passing that to a <Path /> element will intermittently cause the app to crash.

Sorry for spamming, but wanted to just drop in a paste-able example that will reproduce the issue I'm seeing here. In an RN/Expo app with reanimated/skia installed, if you plop this in:
import { Canvas, Path, Skia } from "@shopify/react-native-skia";
import * as React from "react";
import { Button, SafeAreaView } from "react-native";
import {
  useDerivedValue,
  useSharedValue,
  withSpring,
} from "react-native-reanimated";

export default function App() {
  const [color, setColor] = React.useState("red");
  React.useEffect(() => {
    const i = setInterval(
      () => setColor((v) => (v === "red" ? "blue" : "red")),
      500
    );

    const i2 = setInterval(() => {
      t.value = withSpring(t.value === 0 ? 1 : 0);
    }, 1000);

    return () => {
      clearInterval(i);
      clearInterval(i2);
    };
  }, []);

  const t = useSharedValue(0);
  /**
   * ❗ This path will throw with `Missing one or more required properties path in the skPath component.`
   */
  const path = useDerivedValue(() => {
    if (squarePath.isInterpolatable(rectPath)) {
      return squarePath.interpolate(rectPath, t.value);
    }
    return squarePath;
  });

  return (
    <SafeAreaView>
      <Canvas style={{ width: "100%", height: 300 }}>
        <Path path={path} style="stroke" strokeWidth={4} color={color} />
      </Canvas>
    </SafeAreaView>
  );
}

const squarePath = (() => {
  const p = Skia.Path.Make();
  p.addRect(Skia.XYWHRect(50, 50, 100, 100));
  return p;
})();

const rectPath = (() => {
  const p = Skia.Path.Make();
  p.addRect(Skia.XYWHRect(50, 50, 100, 50));
  return p;
})();

It's almost as if having the color prop passed to <Path /> while its path prop is coming from a derived value eventually falls over.

@gksander thank you for the nicely reproducible example. We can
confirm the issue, and we are currently investigating it.
On Wed, Aug 30, 2023 at 2:45 PM Grant Sander @.***> wrote:

Sorry for spamming, but wanted to just drop in a paste-able example that will reproduce the issue I'm seeing here. In an RN/Expo app with reanimated/skia installed, if you plop this in:
import { Canvas, Path, Skia } from @.***/react-native-skia";
import * as React from "react";
import { Button, SafeAreaView } from "react-native";
import {
useDerivedValue,
useSharedValue,
withSpring,
} from "react-native-reanimated";
export default function App() {
const [color, setColor] = React.useState("red");
React.useEffect(() => {
const i = setInterval(
() => setColor((v) => (v === "red" ? "blue" : "red")),
500
);
const i2 = setInterval(() => {
  t.value = withSpring(t.value === 0 ? 1 : 0);
}, 1000);

return () => {
  clearInterval(i);
  clearInterval(i2);
};

}, []);
const t = useSharedValue(0);
/**

❗ This path will throw with Missing one or more required properties path in the skPath component.
*/
const path = useDerivedValue(() => {
if (squarePath.isInterpolatable(rectPath)) {
return squarePath.interpolate(rectPath, t.value);
}
return squarePath;
});

return (

<Canvas style={{ width: "100%", height: 300 }}>

);
}
const squarePath = (() => {
const p = Skia.Path.Make();
p.addRect(Skia.XYWHRect(50, 50, 100, 100));
return p;
})();
const rectPath = (() => {
const p = Skia.Path.Make();
p.addRect(Skia.XYWHRect(50, 50, 100, 50));
return p;
})();
It's almost as if having the color prop passed to  while its path prop is coming from a derived value eventually falls over.
—
Reply to this email directly, view it on GitHub or unsubscribe.
You are receiving this email because you commented on the thread.
Triage notifications on the go with GitHub Mobile for iOS or Android.

@gksander the issue here is the overclamp of the spring value that goes above one. But this is really annoying with RN Skia and we will fix it for trim and interpolate on our side.
That being said, it's a bit too bad that we cannot interpolate above one, could produce some cool effects with spring.

@gksander your example now works with the latest Skia/Reanimated release, can you confirm? I was able to reproduce the crash with earlier Reanimated v3 version.

Can confirm this is fixed when using latest RNA and Skia
React-native-reanimated 3.5.4
React-native-skia 0.1.126
NOTE: Both needs to be updated for it to work. It did not work with just skia updated and using rna with 3.3.0 for example


[service] Wire up client version guards

Wire up HttpClientVersionGuard to HTTP controllers
Wire up WsClientVersionGuard to Websockets gateways
Update gateways handleConnect method to check for version as well. (will have to think of a better way to handle this in the future for multiple gateways if required).

Related to issue https://github.com/michaelgambold/pi-garage/issues/104


Fixing the server example code

The example from the docs page is outdated. This PR fixes it

I appreciate your contribution but master branch has some import shortcuts that make this example works as it should. I notice that you added the request parameter to the route but you don't use it, one of the reasons that I made Vibora analyze route parameters was to have enough info about what a user needs and what can be post-poned or not built at all (for performance reasons). I think I should add this explicitely in the docs... Anyway, I'm closing this pull request for now but feel free to discuss (or send another PR) with me, many thanks !


narrow NIO dependency to just NIOCore

this package does not need to depend on all of SwiftNIO, NIOCore is sufficient.

Thanks for the PR!


Remove 'file_name' argument from 'record'

Follow up to #27, when we next do a major release it should be removed since it's already deprecated

You mean remove "file_name" not "path"

Done in #36.


Cursor's height is too big when we change lineHeight

Compose 1.1.0
import androidx.compose.foundation.border
import androidx.compose.foundation.layout.fillMaxWidth
import androidx.compose.foundation.layout.height
import androidx.compose.foundation.text.BasicTextField
import androidx.compose.runtime.getValue
import androidx.compose.runtime.mutableStateOf
import androidx.compose.runtime.remember
import androidx.compose.runtime.setValue
import androidx.compose.ui.Modifier
import androidx.compose.ui.graphics.Color
import androidx.compose.ui.text.TextStyle
import androidx.compose.ui.unit.dp
import androidx.compose.ui.unit.sp
import androidx.compose.ui.window.singleWindowApplication

fun main() = singleWindowApplication {
    var state by remember { mutableStateOf("") }
    BasicTextField(
        state,
        { state = it },
        enabled = true,
        modifier = Modifier.fillMaxWidth().height(100.dp).border(1.dp, Color.Red.copy(alpha=0.25f)),
        textStyle = TextStyle(lineHeight = 60.sp)
    )
}

https://user-images.githubusercontent.com/5963351/155567951-00e5d40c-41d4-4a38-a576-7b6bbc097fab.mp4
We can see, that cursor is normal, but when we switch to another line, it became bigger.

duplicate: https://github.com/JetBrains/compose-jb/issues/1892

fixed  in https://github.com/JetBrains/androidx/pull/277

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Added Limitations to ReadMe

Provided Limitations on the ReadMe as this is currently not clear in the documentation.

@sukhans I think to accept this edit those limitations should be identified so users know if they run into a new bug/limitation or something that has been documented. Plus allow them to accept the known limitations vs discover on their own.

@sukhans I think to accept this edit those limitations should be identified so users know if they run into a new bug/limitation or something that has been documented. Plus allow them to accept the known limitations vs discover on their own.

That's a fair ask. @davidknise can we publish a generic list of Linux related bugs/issues that we have open w.r.t. MSDO?
I know we have a list published internally. We could probably sanitize that.

@davidknise  just bumping this.

@davidknise @sukhans   bumping this as customer was asking in regards to known limitations.

I've just spent 2 hours trying to get the pipeline working only to discover that linux agents don't work. Please can you merge this. The issue backlog is full of similar reports

@JFolberth we made the fixes and this should be fixed now. Linux should work with the tools.


is_writable function produces the wrong boolean output when run on AWS Lambda with EFS storage attached

The function in question
I need to debug further, but I am 100% sure the drive is writable, as I was able to create folders (e.g. Path(os.environ['NLTK_DATA']).mkdir(parents=True, exist_ok=True))
This being returned as False causes environment variable NLTK_DATA not to function. I think you should trust users to know that they are using NLTK_DATA for good reason and in the case where path == os.environ['NLTK_DATA'], skip the iswritable check. If in fact it is unwritable, the user would be able to be told that the environment variable (potentially with a typo) is not writable.
I will now attempt to log the same checks of is_writable to provide more info on what is failing.

Can confirm that the lambda function would have returned an error (e.g. NLTK_DATA=/cache/nltk) if the supplied nltk_data directory was read-only.
It would have been of the following format:
Traceback (most recent call last):
  File "/var/lang/lib/python3.9/pathlib.py", line 1323, in mkdir
    self._accessor.mkdir(self, mode)
FileNotFoundError: [Errno 2] No such file or directory: '/cache/nltk'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/var/lang/lib/python3.9/pathlib.py", line 1327, in mkdir
    self.parent.mkdir(parents=True, exist_ok=True)
  File "/var/lang/lib/python3.9/pathlib.py", line 1323, in mkdir
    self._accessor.mkdir(self, mode)
OSError: [Errno 30] Read-only file system: '/cache'

The results of the following:
import stat
statdata = os.stat(os.environ['NLTK_DATA'])
perm = stat.S_IMODE(statdata.st_mode)
# is it world-writable?
if perm & 0o002:
    print("It is world-writable")
else:
    print("It is NOT world-writable")
# do we own it?
if statdata.st_uid == os.getuid() and (perm & 0o200):
    print("We do own it")
else:
    print("We do NOT own it")
# are we in a group that can write to it?
if (statdata.st_gid in [os.getgid()] + os.getgroups()) and (perm & 0o020):
    print("We are in a group that can write to it")
else:
    print("We are NOT in a group that can write to it")

are:
  | 2021-12-20T01:12:02.903+07:00 | It is NOT world-writable
  | 2021-12-20T01:12:02.903+07:00 | We do NOT own it
  | 2021-12-20T01:12:02.903+07:00 | We are NOT in a group that can write to it

I have a feeling this code would fail on any NFS type filesystem too

Anyone here with a similar issue. The workaround I am going to try is to change NLTK_DATA=/tmp/nltk_data. I only really need Amazon EFS for the library that is calling ntlk (allenNLP).

That would have worked if NLTK data required was < 512MB, however it is not.
I get the following:
[ERROR] OSError: [Errno 28] No space left on device Traceback (most recent call last)

I am going to have to investigate monkeypatching to get this to work.
For what reason can you not use try / except in this case? It is a much more portable solution to try write a file. If it fails handle exception, if it passes then delete temporary file.
I am happy to submit a PR but only if the maintainer agrees that this is the way to go.

That would have worked if NLTK data required was < 512MB, however it is not.
I get the following: [ERROR] OSError: [Errno 28] No space left on device Traceback (most recent call last)

nltk_data is about 3.37GB in size if all packages are installed. However, it's possible to only install the required sections. If, by chance, you have installed all of nltk_data (i.e. with import nltk; nltk.download("all") or python -m nltk.downloader all), then reducing this to merely the sections that are required, then you might be able to make some progress here.
That said, I'm assuming allenNLP already downloads the minimal nltk_data for its purposes.
Perhaps https://docs.python.org/3/library/os.html#os.access would be an appropriate replacement of the current system, but it is possible that the current function is specifically written because of the second note on that documentation:

I/O operations may fail even when access() indicates that they would succeed, particularly for operations on network filesystems which may have permissions semantics beyond the usual POSIX permission-bit model.

I don't have control here. NLTK is called through another library, AllenNLP.
Anyway, I found a way. I call the module which results in the downloads during build time of the docker image and use NLTK_DATA variable to reference the now populated read-only directory at lambda invocation time. This way, the downloader does not need to be called and we work around the problem.
FYI, the size of what ends up being downloaded for NLTK in this case is 155M!
I think in looking up that answer, I just figured out that it was AllenNLP writing to /tmp, not NLTK. I solved the problem of AllenNLP's use of /tmp by setting TMPDIR=/mnt/efs/tmp... that way AllenNLP won't use the 512MB limited resources available on /tmp, and instead use the EFS mount.
And with this in place it should be safe to got back to NLTK_DATA=/tmp/nltk_data (which would mean that the image doesn't need to be prebuilt as mentioned before).

Wonderful! Glad to hear you got it working.
That said, my understanding is that there is still a bug in is_writable on AWS Lambda with EFS storage? Or do you not expect this to be a problem?
My understanding of the usage of is_writable is that it will defer to downloading to ~/nltk_data if is_writable is bugged to exclusively return False on certain systems, which might not commonly be a problem.

Yeah despite my workaround, the NLTK library would still fail to make use of EFS with the checks in their current form. And in Lambda's case ${HOME} or ~/ is read-only so ~/nltk_data is not suitable.


install from pip

Being able to install this via pip either from pypy itself or as a zip would make using this project easier for new users and collaborators.
There are a few ways to approach this, personally I was going to use a combo of pipenv pipenv-setup and setuptools the distributing it via pypy.
If your not opposed to that I'd be more than happy to share my setup.py, setup.cfg and pipfile once they are ready.
Then you would be able to upload the repo to pypy using setuptools.

This is one of the items on my list. The only reason I haven't done it yet is that I need to look into the requirements (I have never pushed anything to PyPi before).

I have this sample module that covers a basic setup.py
https://github.com/Nalisarc/samplemod
From what I understand we can then upload it to pypi using twine.
You'll need to register an account here: https://pypi.org/account/register/

I'm continuing to work on this, but I wanted to help out more.
I've started work on the github actions, these should help the project be more robust as you, I, and any other collaborators work on this.
I'm also trying to be better about my branches.

Okay so a couple of directory rearrangements were needed. But I haven't needed to make any changes to the code itself!
If we structure the directory like so:
orgmunge/

pyproject.toml
README.org
tests/
src/

orgmunge/

This allows build and pip-tools to build a  copy of the library and install it like a module.
I can then use twine to upload to test-pip. Once this is done I'll send you another message with instructions to upload it to real pip.
I'm super excited about making this library more usable.

Was this package not put on pypi by you? https://pypi.org/project/orgmunge/

Yeah that looks like us!
It also installs version 0.1.1.
Thanks for bring this to my attention.

@Nalisarc, I know I've been delaying looking into this because I have no past experience with publishing to PyPi, but I don't think it's fair that you published this package and listed yourself as author. Please change the author field to my name.

@durableOne you're listed as maintainer on pypi too are you sure you're not able to do this?

I took a look and made sure you're listed as owner. Then removed myself as an owner.
You should now be the only owner there.
It was never my intention to claim ownership over the project.
My apologies for the confusion.

I took a look and made sure you're listed as owner. Then removed myself as an owner. You should now be the only owner there.
It was never my intention to claim ownership over the project. My apologies for the confusion.

I apologize if my initial message sounded too harsh. I now see the misunderstanding that happened. I never meant for you to remove yourself as a co-maintainer. I just meant that I should be listed as author. This should be fixed on a re-upload since I fixed the pyproject.toml file.
Please add yourself back as a maintainer on the package if you are still willing to work on it, I really value your contribution.

No worries! I am still willing to work on this.
From what I gather, the scripts I wrote for the .github/workflow used me as the author. Which was never my intention.
You might need to re-add me as a contributor on pypi? the username I used was deltazeeter.
I've always thought that this is your project. I'm just happy to contribute what skill I have.


Translate contribute/review/reviewing-prs into Japanese

This is a Feature Request
What would you like to be added
Translate contribute/review/reviewing-prs into Japanese.
Why is this needed
This page has not been translated.
Comments
/language ja
/assign

/triage accepted

/remove-lifecycle stale


Browser distribution is not IE11 complainant

Brief bug description
While importing the browser distribution inside my bundle, it turns out that it's not fully compatible as it contains a Symbol at the end of the file:
var e=Symbol("codename")
Which breaks on IE11.
Repro steps

Import the browser umd distribution (doing it with webpack in my case)
Run it on a browser

Expected behavior
It should work.
Browser distribution doesn't contains class, so it should not contains Symbol too.
Test environment

Platform/OS: Windows
Browser IE
Version 11

Additional context
Add any other context about the problem here.
Screenshots
Add links to screenshots, if possible.

Symbol("codename") is coming from reflect-metadata, which is a dependency. What's the suggested solution for this case?

@ematipico Can you try using this legacy bundle and let me know how that works?
kentico-cloud-delivery-sdk.browser.legacy.umd.min.zip

Thanks for your answer! I am using the browser umd version as workaround of this issue https://github.com/Kentico/kentico-cloud-js/issues/94.
I eventually made it working by sticking babel polyfills at the beginning of the generated bundle. This solution works!

Great to hear that :-) I'll be releasing new legacy bundle for both CM and Delivery starting from the next releases. Its definitely good you brought this up again :)

Thanks! This is really appreciated!


Changes to Hook building instructions...

…  based on recent changes in Hook repo
Issue #, if available:
Description of changes:
Testing (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/retest