Some old algorithms in PKCS#12 files don't work any more

Using alpha16-dev (1f3b58d8413cfa) compiled with ./config enable-md2 enable-rc5 no-shared enable-ec_nistp_64_gcc_128 -ggdb on Fedora 32.
Some files that are readable with 1.1.1 aren't readable with 3.0.0-alpha16-dev, even with legacy provider loaded.
Algorithms affected:

PBES2 with RC2-CBC-128
PBES2 with RC2-CBC-40
PBES2 with RC2-CBC-64
PBES1 with pbeWithSHAAnd128BitRC4
PBES1 with pbeWithSHAAnd40BitRC4

Reproducer for RC2-CBC-128:
# compile openssl with old algorithms enabled
# checkout the keyfile corpus in parallel directory:
git clone https://github.com/redhat-qe-security/keyfile-corpus.git
cd openssl
apps/openssl pkcs12 -provider-path providers/ -provider legacy -provider default -in ../'keyfile-corpus/rsa(2048,sha256),cert&key(PBES2(PBKDF2(salt(8),iter(2048),keyLen(16),prf(default)),rc2-cbc(keyBits(56=128bit),IV(8)))),mac(sha1,salt(8),iter(2048)),pass(ascii).p12' -out /dev/null -info -nodes -passin file:../keyfile-corpus/password-ascii.txt

OpenSSL output:
MAC: sha1, Iteration 2048
MAC length: 20, salt length: 8
PKCS7 Encrypted data: PBES2, PBKDF2, RC2-CBC, Iteration 2048, PRF hmacWithSHA1
Error outputting keys and certificates
4057DE1C127F0000:error:0680006D:asn1 encoding routines:ASN1_TYPE_get_octetstring:data is wrong:crypto/asn1/evp_asn1.c:37:
4057DE1C127F0000:error:0300007A:digital envelope routines:evp_cipher_asn1_to_param_ex:cipher parameter error:crypto/evp/evp_lib.c:230:
4057DE1C127F0000:error:0300007A:digital envelope routines:PKCS5_v2_PBE_keyivgen:cipher parameter error:crypto/evp/p5_crpt2.c:149:

Reproducer for RC4:
apps/openssl pkcs12 -provider-path providers/ -provider legacy -provider default -in '../keyfile-corpus/rsa(2048,sha256),cert&key(pbeWithSHAAnd128BitRC4,salt(8),iter(2048)),mac(sha1,salt(8),iter(2048)),pass(ascii).p12' -out /dev/null -info -nodes -passin 'file:../keyfile-corpus/password-ascii.txt'

OpenSSL output:
MAC: sha1, Iteration 2048
MAC length: 20, salt length: 8
PKCS7 Encrypted data: pbeWithSHA1And128BitRC4, Iteration 2048
Error outputting keys and certificates
40374D13F17F0000:error:1180006A:PKCS12 routines:PKCS12_PBE_keyivgen:iv gen error:crypto/pkcs12/p12_crpt.c:61:

Other reproducers:
apps/openssl pkcs12 -provider-path providers/ -provider legacy -provider default -in '../keyfile-corpus/rsa(2048,sha256),cert&key(PBES2(PBKDF2(salt(8),iter(2048),keyLen(5),prf(default)),rc2-cbc(keyBits(160=40bit),IV(8)))),mac(sha1,salt(8),iter(2048)),pass(ascii).p12' -out /dev/null -info -nodes -passin 'file:../keyfile-corpus/password-ascii.txt'
apps/openssl pkcs12 -provider-path providers/ -provider legacy -provider default -in '../keyfile-corpus/rsa(2048,sha256),cert&key(PBES2(PBKDF2(salt(8),iter(2048),keyLen(8),prf(default)),rc2-cbc(keyBits(120=64bit),IV(8)))),mac(sha1,salt(8),iter(2048)),pass(ascii).p12' -out /dev/null -info -nodes -passin 'file:../keyfile-corpus/password-ascii.txt'
apps/openssl pkcs12 -provider-path providers/ -provider legacy -provider default -in '../keyfile-corpus/rsa(2048,sha256),cert&key(pbeWithSHAAnd40BitRC4,salt(8),iter(2048)),mac(sha1,salt(8),iter(2048)),pass(ascii).p12'  -out /dev/null -info -nodes -passin 'file:../keyfile-corpus/password-ascii.txt'

Hmm, did this regress recently? Could you try some previous alphas?

I can try to fix this issue.

I did try alpha1: did not compile; alpha2: doesn't support the -provider-path option so can't make it load the legacy provider; alpha10 fails in the same way

@sahanaprasad07 you are welcome to try.

#14434 does some major updates in this area, I don't know if it fixes this but it does make the code provider aware.

@paulidale Oh yes, I'll wait and see what impact it has on this issue. Thanks!

I confirm that the PR fixes the cases with RC4, but not RC2

@jon-oracle any idea?

I can manage to read a file with RC2/MD5 PBE encryption as long as both legacy and default providers are loaded. Using the PR in #14434 I ran:
./apps/openssl pkcs12 -provider-path=./providers -provider legacy -provider default -in 1key_ciph-PBE-MD5-RC2-64_iter-1000.p12
The file came from the PKCS#12 test app which was run using:
./test/pkcs12_format_test -test 2 -write
Note that I had to set OPENSSL_MODULES=./providers to pick up the legacy provider.

Yes, I can see that PBES1 ciphers that use RC2 work, it's the combination of RC2 with PBES2 that's problematic

Yes, I can see that PBES1 ciphers that use RC2 work, it's the combination of RC2 with PBES2 that's problematic

Ah, ok.
I've added NID_rc2_cbc to the list of algorithms in ./test/pkcs12_format_test.c in #14434 and generated a P12 file using PBES2. The file can be read using the v3.0 pkcs12 app but does fail with the v1.1.1 app installed on the system, which points to some incompatibility between the versions. This will need more investigation.

@tomato42 could you post the steps you're using to create the file (or the file itself) with 1.1.1?

@tomato42 could you post the steps you're using to create the file (or the file itself) with 1.1.1?

@jon-oracle the files are here:
git clone https://github.com/redhat-qe-security/keyfile-corpus.git

I don't remember exactly how I created the files in the keyfile-corpus git repo, I think they were using -keypbe RC2-CBC -certpbe RC2-CBC, but that's just one key size, I might have generated the other key sizes by modifying the sources of the pkcs12 util.
What's a bit atypical in RC2-CBC in PKCS#8 encoding/PBCS#5 is that the key size is not specified directly, see https://tools.ietf.org/html/rfc8018#appendix-B.2.3

@tomato42 this appears to be an issue with the provided cipher implementation. I've added a commit to fix this.
BTW - the keyfiles in your repo could be useful to add to OpenSSL regression tests, maybe as another external test. Do you foresee any problems with this?

I published it so that people would use them :)
One possible gotcha is that there are few NSS-created files that are malformed, they have malformed in the name, you'll likely want to skip those


Adding IsTXCurr in the linelist

Hey @Marymary-dev . Since this seems  like a line list report. Shouldn't it be moved to the new reporting database?
Reporting dir

@Marymary-dev . We can also give the files .sql extension for consistency

@Marymary-dev this is already taken care by your other PR, yeah?


How to forward Android (USB) device to container?

I'm building an Android app in a container using the Android SDK and Cordova, but can't get the device forwarding to work. I haven't the slighest idea how to forward the Android device connection from my Mac OS X to the container itself.
I think the problem lies in the missing device descriptor (in /dev), since Mac OS X does not make them but uses the IOKit Registry instead (which I read about on http://stackoverflow.com/a/11787544/1453912).
Anyone who can help me out here? I'm unexperienced with device descriptors, mounting, etc. in Mac OS X.

You need to capture your usb device into virtual machine. Please look up virtualbox usb filtering. Then when you start a container you use --privileged flag and map /dev/bus/usb as a volume.

Little correction on what @RomanSaveljev said: instead of using --privileged + bind mount, you should be able to simply do --device=/dev/bus/usb:/dev/bus/usb:rwm.

Thanks for the quick response! I have tried both before, but without any luck.. Does boot2docker forward the USB devices automatically to the boot2docker-vm? When checking the VirtualBox configuration of the VM, under Ports > USB, "Enable USB controller" is disabled.
I hadn't tried the device param with :rwm before, but that also doesn't seem to work..

@mauvm before doing anything with Docker you'll need to forward the USB device into the VM. Boot2docker does not do that automatically as far as i know.
You should be able to modify the VM settings in VirtualBox's UI, if you stop the VM. But if you want it to be scriptable, you should use VBoxManage.

Thanks! I have installed the VirtualBox extension pack, relaunched the VirtualBox daemon, rebuild the boot2docker-vm, turned on the USB and USB 2.0 (EHCI) controllers, and added the filter:
VBoxManage usbfilter add 0 --target boot2docker-vm --name 'Android Device Filter' --product "Android Phone" --action hold

Finally I have tried both -v /dev/bus/usb:/dev/bus/usb and --device=/dev/bus/usb:/dev/bus/usb:rwm. The first one mounts OK, and makes /dev/bus/usb/{001,002}/001 available to the container. The latter gives an error:
FATA[0000] Error response from daemon: Cannot start container 4cfd924d09e399e915345389405d051fe243c00108620d810f66d3957fd0c105: error gathering device information while adding custom device "/dev/bus/usb": not a device node

When the boot2docker-vm is running VBoxManage list usbhost does not show my Android phone, while if it's turned off, it does get listed. Could this be a conflict between the host and VM?

yes, it could - I'd use the vbox GUI to test - including starting the b2d virtual machine from the GUI, and then using the GUI to attach the USB device.

Did you manage to solve this? I am also trying to the same thing, plug my Android device into my Macbook and forward the device to my Docker container so that I can launch the app from Cordova on my Android device using cordova run android.

@jonbjo Nope, but haven't tried the suggestion from @SvenDowideit though.

@mauvm I managed to get it to work by basically following the steps above. The only difference is that I added the usbfilter in Virtualbox's GUI. It listed the connected devices and automatically created a filter for me that works. The settings in the filter automatically created seems to be a lot more specific than what you have in your VBoxManage string. Don't know if that makes a difference, but maybe. I also had to connect the device after starting Boot2Docker to be able to authorise the device. Now when I run "cordova run" in my Docker container it builds and deploys to my Nexus 5 connected to my MacBook. I have a sample Dockerfile at https://github.com/wisobi/leanbean/tree/master/leanbean-docker if that helps.

@jonbjo Thanks. Will definitely check it out!

Did you get this working with the --device=/dev/bus/usb:/dev/bus/usb:rwmoption on docker run? For me this works fine when using -v /dev/bus/usb:/dev/bus/usband privileged, but it does not work with the device option. I had a look into the Dockerfile from jonbjo and it seems he is not using the --device option as well.
Any ideas why the suggested --device option does not work?

@suchja No, both of them didn't seem to work. Are you also on Mac OS X? I don't think the problem lies in the Boot2Docker > Docker container part. Purely the Mac OS X > Boot2Docker device mounting part.

@mauvm Yes, Mac OS X here as well. Okay, that's wired. After establishing the device filter via the GUI it works well for me except for the --device part. Do you know of any information how to debug this issue?

@suchja Sorry, but no. Why not keep using the -v? Because hey, at the end of the day it simply works!

I didn't get --device to work either. I think I read somewhere an explanation to why one should use privileged for USB devices, but if I did, I can't find back to that explanation. But at least for me it works with Mac OS X, Boot2Docker and --privileged.

If this issue is still happening to someone nowadays on Mac OS X, I fixed it installing the extension package for Virtual box, and then going to >>settings>>ports>>usb and enabling the connection. After that it worked like a charm.

FYI, this doesn't work if you use Docker 1.12 any more because it uses the OSX Hypervisor instead of Virtualbox :-(

@kenyee have you found any other way to get it working?

@suchja : nope....AFAIK, the hypervisor doesn't support USB port access.  I'm going back to using an older version of docker so I can run it inside virtual box on the Mac.  What's annoying is it doesn't work on a Windows machine either....HAXM is incompatible w/ Hyper-V and Virtualbox, so again, you're stuck w/ the old version of Docker 1.11 that runs inside Virtualbox.

Thanks for clarification!

Am 31.07.2016 um 23:27 schrieb Ken Yee<EMAIL_ADDRESS>@suchja : nope....AFAIK, the hypervisor doesn't support USB port access. I'm going back to using an older version of docker so I can run it inside virtual box on the Mac. What's annoying is it doesn't work on a Windows machine either....HAXM is incompatible w/ Hyper-V and Virtualbox, so again, you're stuck w/ the old version of Docker 1.11 that runs inside Virtualbox.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

If you are using Docker Toolbox to install Docker on OSX/Windows then it will be the most up to date docker (1.12) and use VirtualBox.  The only time you will not be using VirtualBox is when you are using Docker for Mac and Docker for Windows which do not even use the boot2docker project.

In VMware Workstation/Fusion, this can be done by adjusting adding usb.autoConnect.device0 = "0x1234:0x1234" to the VMX.


Fix Bircom messages

Correctly look for the last known position

Summary by Sourcery
Fix the message association logic to correctly use the last known position by referencing the most recent timestamp in the track data, and update the corresponding test cases to validate this behavior.
Bug Fixes:

Correct the logic to associate messages with the last known position by using the most recent timestamp in the track data.

Tests:

Update test cases to reflect the changes in message association logic by adjusting timestamps and expected results.

/cc @ketan @cyberorg


Multidat

WIP for viewing stacks of dat files, including serving them over HTTP as ND chunks.
Performance is horrendous.

This should just be replaced by a zarr store.


Reporting Example

Hi @nikolajlovenhardt, Thanks for this wrapper.
Could you provide a sample or some hints how we can implement https://github.com/googleads/googleads-php-lib/blob/master/examples/AdWords/v201702/Reporting/DownloadCriteriaReportWithAwql.php using this Laravel wrapper ?
Thanks.

Hey @mansouralex
Something like this:
<?php

namespace App\Http\Controllers;

use Google\AdsApi\AdWords\Reporting\v201609\ReportDownloader;
use Google\AdsApi\AdWords\AdWordsSession;
use LaravelGoogleAds\Services\AdWordsService;

class ReportController extends Controller
{
    /**
     * @var AdWordsService $adWordsService
     */
    private $adWordsService;

    public function __construct()
    {
        $this->adWordsService = new AdWordsService();
    }

    /**
     * @return void
     */
    public function report()
    {
        /** @var AdWordsSession $session */
        $session = $this->adWordsService->session('CLIENT_CUSTOMER_ID');

        // Create report query to get the data for last 7 days.
        $reportQuery = 'SELECT CampaignId, AdGroupId, Id, Criteria, CriteriaType, '
            . 'Impressions, Clicks, Cost FROM CRITERIA_PERFORMANCE_REPORT '
            . 'WHERE Status IN [ENABLED, PAUSED] DURING LAST_7_DAYS';

        $reportDownloader = new ReportDownloader($session);
        $reportDownloadResult = $reportDownloader->downloadReportWithAwql($reportQuery, $reportFormat);

        print "Report was downloaded and printed below:\n";
        print $reportDownloadResult->getAsString();
    }
}

You need to provide a CLIENT_CUSTOMER_ID!

@yooouuri Thanks for your reply. Have already solved it.


Running on iPad

I'm running your project on an iPad with iOS 7.1 and I can't save any of your pdf files. Everything works in the simulator.
I get the Object Stream error.

Hi,
I am using your framework, after saving data pdf interactive features lost completely. Please let me is it possible to save pdf with its interactive features by ILODFKit framework?


enable node builtin modules polyfills when target is node

Bug report
What is the current behavior?
when I set node attribute to true in the webpack config file, the bundled file still contains require(xxx) for nodejs builtin modules
If the current behavior is a bug, please provide the steps to reproduce.
Here is the related configuration in my webpack.config.js:
target: 'node';
node: true;
What is the expected behavior?
When we set node: true, the nodejs builtin modules will be bundled into the output file, instead of containing require('stream') or other node builtins
Here is the use case:
We are bundling a React project for server-side rendering by webpack, and running the bundled files inside vm2 in the node environment. Since vm2 is a sandbox, just like the browser environment, so we cannot contain any require(xxx) statements in the bundled files
Other relevant information:
webpack version:  4.28.4
Node.js version:
Operating System:
Additional tools:

Apparently you are compiling something for node target, so I strongly recommend do not mock Node.js modules, this makes no sense, just set node: false

We are bundling a React project for server-side rendering by webpack, and running the bundled files inside vm2 in the node environment. Since vm2 is a sandbox, just like the browser environment, so we cannot contain any require(xxx) statements in the bundled files

https://github.com/patriksimek/vm2#quick-example
You need use this
For webpack@5 we don't mock built-in global and modules by default for target: node https://github.com/webpack/webpack/blob/master/lib/config/defaults.js#L479


[ca]:  Add RequestAndSaveNewCertificates test with intermediates

This fixes the last TODO in the certificates test, and ensures that the ca testutils can handle a RootCA with intermediates as well.

LGTM


removed obsolet variable from PR #1582

Hi,
if the extra method introduced with 7a8765a would keep the object-oriented interface. But as it was removed, the extra variable can also be removed

Oops! Thanks for catching this.


Fix clone return type

Purpose

$title

Fixes #24875
Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[ ] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Fixes https://github.com/ballerina-platform/ballerina-lang/issues/24664 as well

closing this in favour of #25028


Opt for source-based code coverage

I'm a bit hesitant about running all tests twice. once with coverage instrumentation and once without.


The package is not working with a fresh install

I did not digged into it, but what I actually have, is an Error on a fresh installation with config & boilerplate generation, where the /register route is responding with this Error:
UndefinedFunctionError at GET /register
function TestAddict.Addict.AddictController.init/1 is undefined (module TestAddict.Addict.AddictController is not available)

I could't find where it is mistaken, why the controller is misspelled (I guess TestAddict.Addict.AddictController should be Addict.AddictController instead..)
Note: I could't install it just straight forward, because it seams like the package/or its deps are using some old versions of the current phoenix stack, so I had to unlock mix, before the installation could complete.

I found my issue.. I had to create a new scope without the Module as the second param
instead of
scope "/", TestAddict do
  addict :routes
end

define a new scope
scope "/" do
  addict :routes
end


Running instructions

While creating a new project, reading the readme file, it says to run the file like
deno run -A --watch main.ts

And that produces
error: TS2304 [ERROR]: Cannot find name 'URLPattern'.
        const pattern = new URLPattern({
                            ~~~~~~~~~~
    at https://crux.land/api/get/2H5yPV.ts:145:29

But if I run the file like
./main.ts

It works OK, this is a bug or is just needed to update the docs?

I think this is duplicate of https://github.com/lucacasonato/fresh/issues/76
How about adding --no-check? It will resolve this issue.

I think this is duplicate of #76

Yep, closing in favor.


feat: replace reflections lib with classgraph

The reflections library is no longer maintained. There is no point in employing workarounds to the "SubTypesScanner not found issue" (for reference, one would have to build the reflections differently like here).
Instead, do the same as other libraries do: move to classgraph instead.
It's faster, still being maintained, and doesn't have this annoying bug.
Extra upside: no need to change the context classloader. classgraph has a more explicit classloader handling than reflections.
This fixes #96.

Thanks for the contribution. I am not using the plugin in my daily work anymore but I'll try to find the time to create a new release as soon as possible.

Hi @langecode,
Sorry to bother you again. Just wondering whether I need to create the new release myself (for use by collaborators) or do you have a rough idea, when you have time to look at this and potentially create a new official release?


Support x-logo extension

Should be provided as opts to converter

Hi, is still pending but if this task is something interesting for you I will prioritize, just looking for have time to develop ;-)

Thank you very must ;-). It's perfect.


docker pull not working

Hello, starting at this page https://hub.docker.com/r/graylog/graylog/ and trying to run docker pull graylog/graylog returns:

$ docker pull graylog/graylog
Using default tag: latest
Error response from daemon: manifest for graylog/graylog:latest not found: manifest unknown: manifest unknown

Trying to read the docs linked from hub.docker.com returns 404

he @e-volusian
this is not an error by Graylog. We have on purpose no latest tag. You always need to specify the Graylog version you want to have.
But you are right that this might be not correct to have that command on the page - so I asked in the Docker Hub community for help how to remove that: https://forums.docker.com/t/change-docker-pull-command-on-page/89274

Thanks for your response. The question is answered.


Add more keepalive info logging

Why
Adding the sample load logging seemed to keep the connection alive in concourse, next step is to add more in (and refine it slightly with a configurable level).
What

Use configurable sample load log frequency
Use configurable log level
Add info logging in queue drain wait
Add info logging in print file wait

Wherefore
https://trello.com/c/xNdUzmdK/801-why-does-concourse-stop-outputting-performance-test-logs-during-30-million-test-1-day
https://github.com/ONSdigital/census-rm-sample-loader/pull/30

 Why does concourse stop outputting performance test logs during 30 million test (1 day)

same thought @NickGrantONS  wrt the logging frequency, but we can always tweak the later.


Reloading twice loses changes

Testing microsoft/vscode-jupyter#6813
Open editor with custom editor
Make changes
Put custom editor on background tab
Reload VS code twice
Changes are lost

What happened:

First reload, we found a custom editor backup, and then create a notebook editor input
Before the notebook editor input resolves the backup and save it with working copy, another reload happens
Workbench reopens the notebook editor input, but it doesn't know where to find the backup

The fix is attaching the backup info the notebook editor input until we resolves it.


ci: publish workflow improvement

But you still need manually bump version / create a tag and write a changelog, right?

Yes
currently, it's not a big deal because we do not have a lot of activity here, but definitely needs to be improved in the future


Fake zero copy protector

This CL implements two items

If zero-copy protector exist, secure_endpoint will use zero-copy protector to protect/unprotect
Implement zero-copy grpc protector for fake TSI

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences

Jenkins: Please run the tests.

Jenkins, test this please.

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences

Thanks Mark for quick review. All comments addressed. Will squash before merge.

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences


pull request for e2e test at 01/18/2017 07:56:09

:x: Validation status: errors
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Consider using Jekyll-seo-tag

https://github.com/jekyll/jekyll-seo-tag

No longer appliable; the theme uses jekyll-seo-tag behind the scenes for a while now.


New Changes

User Story: Implement Password Field for LoginSuccess Component
As a user, I want to have a password field in the LoginSuccess component, So that I can securely log out of my account.
Acceptance Criteria:
When I am on the LoginSuccess screen, I should see a password field.
The password field should be masked so that my password is not visible when I type it.
There should be a label for the password field that clearly indicates it is for the password.
The password field should be required. If I attempt to log out without entering my password, I should see an error message prompting me to enter my password.
The password field should accept a minimum of 8 characters and a maximum of 64 characters.
The password field should support special characters, numbers, and both uppercase and lowercase letters.
The 'Login out' button should only become clickable once a valid password is entered.
The password field should be cleared after successful logout

GitHub Agent testing from CustomApp


Swap out murmurhash v2 implementation

Use the more concise https://github.com/garycourt/murmurhash-js
implementation. It's used in various other open source libraries
and more concise than the previous one.
It's functionally equivalent and I've made sure that the seed value
matches, which is also covered by some unit tests.

Pull Request Test Coverage Report for Build 104

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

Totals

Change from base Build 103:
0.0%

Covered Lines:
183

Relevant Lines:
184

💛  - Coveralls

Pull Request Test Coverage Report for Build 104

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

Totals

Change from base Build 103:
0.0%

Covered Lines:
183

Relevant Lines:
184

💛  - Coveralls


houdini.closeContent

if use simple houdini.closeContent('#show') without toggle.
Uncaught TypeError: Cannot read property 'callbackClose' of undefined on line 306

toggle not defined in
settings.callbackClose(content, toggle)

This is working on the demo site.
houdini.closeContent('#section1');

Can you please provide a reduced test case that I can look at?

https://codepen.io/anon/pen/qPjrzm?editors=1011
Click on '+'

Got it. I was calling the wrong callback. The latest (version 9.4.1) should fix this.
https://github.com/cferdinandi/houdini/pull/63


Skooner + keycloak integration problem (403 http)

Hello.
We are trying to set up skooner + keycloak.
Keycloak offers the following configuration for skooner:
{
"realm": "kip",
"auth-server-url": "http://kc.kip./auth/",
"ssl-required": "none",
"resource": "skooner",
"verify-token-audience": true,
"credentials": {
"secret": "*****-6a17-448b-9d89-5d775b9c6d07"
},
"confidential-port": 0,
"policy-enforcer": {}
}
Added configuration to skooner as required by the instructions: https://skooner.io/install/#running-oidc-on-skooner
OIDC_URL="http://kc.kip./auth/realms/kip/"
OIDC_CLIENT_ID="skooner"
OIDC_SECRET="*****-6a17-448b-9d89-5d775b9c6d07"
When entering the skooner website, after entering the username / password, we get errors:
http://skooner.kip.***/apis/authorization.k8s.io/v1/selfsubjectrulesreviews
POST
403 Forbidden
http://skooner.kip.***/oidc
POST
200 OK
http://skooner.kip.***/apis/authorization.k8s.io/v1/selfsubjectrulesreviews
Метод запроса: POST
401 Unauthorized
...
The skooner instruction also mentions "OIDC_METADATA='{"token_endpoint_auth_method":"client_secret_post"}", but adding this parameter did not solve the problem.
The question is, there is an example of a working skooner + keycloak scheme - can I get acquainted with your configuration to solve the problem?

Have you set up kube-apiserver to accept OIDC tokens? There are some resources in the README of how to set that up.
Since /oidc is returning 200, but the other is not, it's likely an issue where kube-apiserver is rejecting the token.
Check your kube-apiserver logs

Thanks for commenting! I'll try this when I have more bandwidth.. Recently start to have more work internal

We pushed out updated patches to stable release, could you try that again?

New stable was released and we fixed two pieces of documentation flaws.
Please follow through with the keycloak troubleshooting section and report any issues with a new ticket or reopen this. Thanks!


fixed home page card UI

Pull Request Checklist
Fixes #1569

[X] I have added screenshots and videos to show before and after the working of my code.
[X] I have ensured that the screen size is set to 100% while making the video.
[X] I have synced the latest fork with my local repository and resolved any conflicts.
[X] I have mentioned the issue number which I created before making this PR .(format to mention issue number is : fixes #(issue number) )
[X] I understand that if any the above conditions are not met , my PR will not be MERGED .
Before:

After:

Minor changes

Minor changes

yes what?

@hiteashgupta1  can you please review  #1618 pr


Remove trailing slash

Hi @mickael-kerjean, I'm debugging https://github.com/mickael-kerjean/filestash/issues/200 and in the process, I setup go.mod in filestash to pull in all the deps.
In the process, when I ran
go mod download
make

It threw this error:
go: github.com/mickael-kerjean/filestash/server/ctrl imports
	github.com/mickael-kerjean/net/webdav<EMAIL_ADDRESS>parsing go.mod:
	module declares its path as: github.com/mickael-kerjean/net/
	        but was required as: github.com/mickael-kerjean/net
make[1]: *** [build_backend] Error 1
make: *** [all] Error 2

Comparing your go.mod to the official net repo, the fix looks like it could be removing the trailing slash here.
Cheers.

Thank you!


Feature/201 assign reviewers

@zerolab Includes a little refactor to make the forms more robust.

requires #191

👍 merge when green


RuntimeError: Not compiled with GPU support

I tried both conda, pip with many combinations of torch (1.11+) and cuda (10.2, 11.3, 11.6) but have not managed to make it work.

I tried both conda, pip with many combinations of torch (1.11+) and cuda (10.2, 11.3, 11.6) but have not managed to make it work.

Hi, I met the same problem, have you solved it?

For future reference, I found this repo: https://github.com/inspiros/tvdcn/tree/master is fantastic for deformable convolution.


Initialization failure of AppInsights with RuntimeConfig

With the last version, if you provide a connection string to the module, Application Insights will fail to initialize.

The config provided to AppInsights is a Proxy and not a raw object, and AppInsights tries to set its own observer on the object and it fails. One way to fix it would be to use toRaw:
config: toRaw(runtimeConfig.public).applicationinsights ?? {}

damn, i probably forgot to add it back while refactoring. Thanks for the issue !


Add a "Getting Started Section"

Add a Getting Started Section.
The section would show how to set up the font.

This should probably be on the README as well.

PRs are always welcome :wink:
Until then:
npm add --save rpg-awesome

app.jsx
// Assuming you are using css-loader
import 'rpg-awesome/css/rpg-awesome.css';

// ...
<i className="ra ra-aura" />

It looks like the package.json could also be updated to have a  main entry as well. I'll go ahead and add an issue for that.


ci: make deploy require migration tests

Issue #, if available:
Description of changes:
Make migration tests a dependency of deployment for stricter releases
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

LGTM!


Allows users to conduct global search via the URL

This PR adds the global search query to the URL, providing a way to copy & paste the search query, and allowing direct access to search results via URL. For instance, https://dispatch.com/org/search/results/281 will show the search results for the query "281".

Thoughts on using a query param here? When I think of a search query I typically think of something like /search?q=foo mostly because I'd expect the result to be dynamic. Where as if it's directly in the URL id expect the results to be the same every time.

Thanks for the suggestion, @kevgliss. I changed to a query parameter and improved further by updating the URL bar and search results when user types in the inputbox.


Use other ports also available for SSL cetificates intead of 443/80 only

Is your feature request related to a problem? Please describe.

For some reasons, I don't want to give 443 and 80 to NPM. I want to use other ports, like 8080 or 4443, to replace them in docker-compose.yml file:
ports:
      - '8080:80'
      - '8181:81'
      - '4443:443'

However, if I do so, the process of getting a SSL cetificates would meet a internet error.
Describe the solution you'd like

I do hope I could suceed with other ports.

Commenting to keep issue open. Definitely need the ability to remap ports.


Update readme

Update installation instructions and citation info

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

Codecov Report

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

@@           Coverage Diff           @@
##           master     #167   +/-   ##
=======================================
  Coverage   96.11%   96.11%
=======================================
  Files          36       36
  Lines         669      669
=======================================
  Hits          643      643
  Misses         26       26

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 128de0f...699c5e4. Read the comment docs.


Flutter: Deliver repo README and reference docs for SDK GA

Eng:

Update repo README to reflect features in the GA version of the Flutter SDK
Update code annotations to generate reference docs that reflect features in the GA version of the Flutter SDK

Docs (@jhaaaa)

Provide copy and style edits to repo README. In addition to publishing the README to the repo, J-Ha will also publish the README content as a quickstart tutorial on xmtp.org.
Coordinate with Eng to generate reference docs in a format that J-Ha can publish to xmtp.org

Generated HTML reference docs for xmtp-flutter.
Hoping to be able to generate Markdown to easily insert the content into Docusaurus. Can't seem to find command to do it. @dmccartney offered to help on Monday. TY!

Reference docs: Team made the call to link to reference docs here https://pub.dev/documentation/xmtp/latest/xmtp/xmtp-library.html -- instead of reshaping generated docs to fit on xmtp.org.

README/Quickstart tutorial: Opened PR to update README in repo to reflect GA. Dan reviewing:
https://github.com/xmtp/xmtp-flutter/pull/45

Opened draft PR to publish README/Quickstart and link to reference docs on xmtp.org: https://github.com/xmtp/xmtp-dot-org/pull/262

Open item: Setting up Algolia to index the reference docs on the external site. I don't think it is a blocker for publication, but I have customer support and discussion forum issues open asking for guidance about a theory I have about how it could work. If I don't get guidance, I'll just try it in the repo - but wanted to get some hint of validation first.

Heard back from Algolia about indexing external sites. They call it "multi-index search" and it requires using an InstantSearch.js file: https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/multi-index-search/js/
Currently, xmtp-dot-org uses an algolia.config.json file for Algolia configuration - not InstantSearch.js. Switching might take some work - I'm asking Algolia for some guidance on this - but it takes them days between messages to reply - so this might take a while.
This feature might also become very simple once we get access to their crawler UI - which Matt and I have also been pinging them about.
For launch, we may just need to link - and set up multi-index search once we have the info and resources to do so.
In the meantime, I can just list the classes, properties, and enums to make at least those high-level keywords searchable on xmtp.org.

Delivered in https://github.com/xmtp/xmtp-dot-org/pull/311


Add tag to inventory for remote ELANs

Part of multi-host support.  We need to add a tag to the inventory file so that Ansible can identify the remote ELANs.  This will also allow actions to be driven against the set of remote ELANs.

This is being done as part of the remote-DNS support in #162.


after_sign_in_path_for return "null"

I use recoverable devise module so the user receive a mail to create a new password. When the user click on the email link, he's redirected to the device/password/edit.html.erb view. He completed the two fields and when he clicked on Validate, Devise redirect him to {root_path}null !!!
I made some investigation and I saw that the callback passed through "after_sign_in_path_for" method that return null as a string. So to fix this problem I have to do this ugly thing in application_controller.rb:
  # Devise callback after sign_in success

  def after_sign_in_path_for(resource)

        redirect_url = super

        # Redirect url is null (and not nil) on change password recovery callback

        redirect_url != "null" ? redirect_url : root_path

    end

Can you fix that ?

@ckornaros Thank you for your report!
I think this issue is fixed, you can take a look at this method. The "null" inside of the string should not happen anymore.
Could you please provide more information?
Like for example:

Rails version
Devise version
Steps to reproduce the error

Will be even more helpful if you provide a sample application or a test case that reproduces the error.
Best

I'm closing this issue. Feel free to reopen if the problem persists.


Feature Request: Add more light controllability

Would be nice to have full on/off control and dimming capabilities of the main and up lights on both the i6 and Haikus.
Also, my i6s es6s have the “UV-C Clean Mode” so would be nice to be able to toggle that on and off as well.
Thanks for the amazing plugin!

If I understand correctly, the plugin should give full on/off control and dimming capabilities of the main and up lights on fans that have uplights.  If the plugin recognizes the uplight is equipped it should present two lights that you can control independently.  I'm guessing the plugin doesn't recognize that there's an uplight and we'll need to figure out why.
It should look something like this:

What are you seeing?
As for the UV-C Clean mode, we should be able to add a switch for that.  I'd need to see what messages get sent when the UV-C is turned on and off.  We could do that after we resolve the issue with the uplights.

Oh very cool, must be an issue on my end then. Correct, I don't see any lighting controls at all. Here's a room with a Haiku in it, but it's the same for all 5 fans (2 i6 and 3 Haiku):

Ahh ok... Well looking at it a bit more, looks like the 2 fans aren't i6 they are es6, so I changed that in the config and I also went into the fan settings in HomeKit and selected "Show as Multiple Tiles". I see the light controls now. Sorry for the churn there 🤦♂

The single vs separate tiles thing can be confusing.
I haven't dealt with a fan that only has an uplight but no downlight yet.  Chances are the plugin is not recognizing your configuration correctly.
Do you want to add some debugging parameters to your config.json file that will output detailed logs of the messages your fan is sending?  Then I can look at the logs and try to see what's going on.  If so, I'll lay out what to do.

Please add the following to the config for one of your es6 fans;
"debugLevels": [
  [ "network", 11 ]
]

Then restart homebridge with the -D option and email the logs from when it restarts until a couple minutes after that.  Send the logs to<EMAIL_ADDRESS>If you're using Homebridge-UI you can tell it to use the -D option when restarting homebridge:

Thanks.

Logs sent!

Logs received!  I reproduced the issue using them and now I'll try to see what to do about it.  Thanks!

I've published<EMAIL_ADDRESS> The intent is to resolve the light issues for the es6 fans and provide a switch to control the UV light.
You'll probably need to clear your es6 caches for their downlights to go away.

Would you try<EMAIL_ADDRESS>This version takes a guess why the light control doesn't work.
Also, I think it will fix the bogus "Fan Light" appearing sometimes after a restart.

Tried removing the fans from cache and disable/enabled the plugin and still no dice on the light control. Would collecting some more logs help?

If debugLevels for "network" is 7 or more you should see sending c0120712051a03900501c0 which tells the fan which light to use and "sending c0120712051a03a00401c0 for "on" and c0120712051a03a00400c0 for off.  If you see those being sent when you try to turn the light on or off from the Home app, then the next thing to try would be to different possibilities for the "which light" value.
Tomorrow I can make a beta that lets you try different "which light" values or you can connect to your fan directly from the terminal and send the raw binary, for instance, if you have a unix-like system with something like:
echo c0120712051a03900501c0c0120712051a03a00401c0 | xxd -r -p | nc LivingRoomFan.local 31415 > /dev/null
The above would be useful just to verify that sequence (which the plugin should be  sending now) doesn't work.  Then try c0120712051a03900500c0c0120712051a03a00401c0 and c0120712051a03900502c0c0120712051a03a00401c0.  If none of those turn the light on, then I think we need to sniff the wire when you control the light from the BAF app to see what it's sending.
I'm going to call it a night now.

Ok. By chance I tried rebooting the fans and the light control is working now!

Do I understand correctly that BAF remote can control the light now and the plugin still doesn't control the light?

So, everything is good for now or are there still some issues?

There was some weirdness around the plug-in state after the reboot (light/fan was on, but plug-in saw it as off). But I think I can file those separately as I narrow them down if need be.
I'd say this one is solved. Great success! Thank you!

All your fan are belong to us😁.   We'll leave this issue open for a while in case things revert back to the unstable state.  But yes, please open new issues as new problems present themselves.
Thanks for your help.

Thank you! Appreciate the quick work!


Keyboard navigation issue when links/button in content - Intermittent

Getting intermittent focus issue when the content has button to expand / collapse the content. This makes navigation challenging for keyboard users.
Screenshots

Version
webchat es5 version 4.13.0
https://cdn.botframework.com/botframework-webchat/4.13.0/webchat-es5.js
Integrating the CDN version js directly on the page using script tag (No Iframe). Desktop Chrome Browser.
<meta name="botframework-directlinespeech:version" content="4.13.0">
<meta name="botframework-webchat:bundle:variant" content="full-es5">
<meta name="botframework-webchat:bundle:version" content="4.13.0">
<meta name="botframework-webchat:core:version" content="4.13.0">
<meta name="botframework-webchat:ui:version" content="4.13.0">

Describe the bug
The virtual agent has adaptive card response with expand/collapse option button. When trying to navigate using up/down to select card and hit enter to set focus on the first element on the selected card, nothing happens. This issue is intermittent.
Steps to reproduce

Deploy Web App Bot with adaptive cards.
Open the web app bot on browser.
Interact with the bot till the adaptive card response arrives using up/down arrow key.
Hit enter to set focus on first element (which should be the expand/collapse option).

Expected behavior
After selecting the card and hit enter, The read more/read less button should be focused.
Additional context
This issue is intermittent. The button getting focus sometimes, But sometimes it's not focus. Adaptive card json given below. The lengthy response has been stripped in the backend to show short version at first. Read more option shows the full content. Please advice if any change has to be done in this expand/collapse implementation.
{
  "type": "message",
  "serviceUrl": "http://localhost:56223",
  "channelId": "emulator",
  "from": {
    "id": "db8f84e0-b217-11eb-b23***********89",
    "name": "Bot",
    "role": "bot"
  },
  "conversation": {
    "id": "4dff8ba0-b246-11**************"
  },
  "recipient": {
    "id": "ffb569b4-b872-4ab2**************",
    "role": "user"
  },
  "locale": "en-US",
  "inputHint": "expectingInput",
  "attachments": [
    {
      "contentType": "application/vnd.microsoft.card.adaptive",
      "content": {
        "type": "AdaptiveCard",
        "version": "1.0",
        "body": [
          {
            "type": "TextBlock",
            "id": "firstresponse",
            "text": "This is a sample response from the virtual agent. This is 2nd line for long response testing. This is 3rd line for long response testing. This is 4th line for long response testing. This is 5th line for long response testing. This is 6th line for long response testing. This is 7th line for long response testing...."
          },
          {
            "type": "TextBlock",
            "id": "secondresponse",
            "text": "This is a sample response from the virtual agent. This is 2nd line for long response testing. This is 3rd line for long response testing. This is 4th line for long response testing. This is 5th line for long response testing. This is 6th line for long response testing. This is 7th line for long response testing. This is 8th line for long response testing. This is 9th line for long response testing. This is 10th line for long response testing. ",
            "isVisible": false
          },
          {
            "id": "showmorebtns",
            "type": "ActionSet",
            "actions": [
              {
                "type": "Action.ToggleVisibility",
                "targetElements": [
                  {
                    "elementId": "firstresponse",
                    "isVisible": false
                  },
                  {
                    "elementId": "secondresponse",
                    "isVisible": true
                  },
                  {
                    "elementId": "showmorebtns",
                    "isVisible": false
                  },
                  {
                    "elementId": "hidemorebtns",
                    "isVisible": true
                  }
                ],
                "title": "Read more"
              }
            ]
          },
          {
            "id": "hidemorebtns",
            "type": "ActionSet",
            "actions": [
              {
                "type": "Action.ToggleVisibility",
                "targetElements": [
                  {
                    "elementId": "secondresponse",
                    "isVisible": false
                  },
                  {
                    "elementId": "showmorebtns",
                    "isVisible": true
                  },
                  {
                    "elementId": "firstresponse",
                    "isVisible": true
                  },
                  {
                    "elementId": "hidemorebtns",
                    "isVisible": false
                  }
                ],
                "title": "Read less"
              }
            ],
            "isVisible": false
          },
          {
            "type": "TextBlock",
            "text": "Does this answer your question?"
          }
        ],
        "actions": [
          {
            "type": "Action.Submit",
            "id": "Success",
            "data": {
              "IsSatisfied": "true",
              "UserAskedQuestion": "How are you today",
              "ResolvedIntent": "howareyou_general"
            },
            "iconUrl": "******************************"
          },
          {
            "type": "Action.Submit",
            "id": "Failure",
            "data": {
              "IsSatisfied": "false",
              "UserAskedQuestion": "How",
              "ResolvedIntent": "howare_you_general"
            },
            "iconUrl": "******************************"
          },
          {
            "type": "Action.Submit",
            "id": "return",
            "data": "Main Menu",
            "title": "Main Menu"
          }
        ]
      }
    }
  ],
  "replyToId": "815ef170-b2******************************e",
  "id": "868a7d90-b******************************9ee29c2ede",
  "localTimestamp": "2021-05-11T16:19:13+05:30",
  "timestamp": "2021-05-11T10:49:13.961Z"
}

[Bug]

Duplicate of https://github.com/microsoft/BotFramework-WebChat/issues/3798 Please visit for more information.

@corinagum This issue is not related to #3798
Please tag appropriately and provide some solution.

Please answer the questions I asked above, and after confirmation I will request to reopen.


how to take photos of a particular size using react native vision camera?

Question
how to take photos of a particular size using react native vision camera? i want to take photos of a particular size how can I do that in react native cli?
How can I change width to 5200 in numbers and '130%'
What I tried
I tried adding a style prop to the camera but it didn't work like that
export default function Camera({ navigation }) {
  const [cameraPermission, setCameraPermission] = useState();

  useEffect(() => {
    (async () => {
      const cameraPermissionStatus = await Camera.requestCameraPermission();
      setCameraPermission(cameraPermissionStatus);
    })();
  }, []);

  const devices = useCameraDevices();
  const cameraDevice = devices.back;
  const cameraRef = useRef();

  return (
    <View style={{ flex: 1, backgroundColor: 'black' }}>
      {
        cameraDevice && cameraPermission === 'authorized' ?
          <Camera
            ref={cameraRef}
            style={styles.camera}
            device={cameraDevice}
            isActive={true}
            photo={true}
            focusable={true}
            fps={60}
            frameProcessorFps={1}
            preset={true}
            enableZoomGesture={true}
            hdr={true}
            AutoFocusSystem="phase-detection"
            qualityPrioritization="quality"
          />
          :
          <ActivityIndicator color='white' size='large' />
      }
    </View>
  );
}

const styles = StyleSheet.create({
  camera: {
      borderTopLeftRadius: 30,
      borderTopRightRadius: 30,
      borderBottomLeftRadius: 30,
      borderBottomRightRadius: 30,
      overflow: 'hidden',
      width: '130%',
      aspectRatio: 1
  },
});

VisionCamera Version
2.15.4
Additional information

[ ] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar questions in the issues page as well as in the discussions page and found none.

That's not how VisionCamera works. Read the docs on selecting Camera Devices and Formats. Then select a format with you target size.

@mrousavy I looked that the docs but I know understand how to get 2448 x 3264 pixels camera format like everyone can only take photo in 2448 x 3264 pixels How can I do that? Can you give code examples ?


Incorrect documentation regarding omitting the expression syntax for if conditionals

What article on docs.github.com is affected?

https://docs.github.com/en/actions/reference/context-and-expression-syntax-for-github-actions#about-contexts-and-expressions
https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idif
https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsif

What part(s) of the article would you like to see updated?
All the sections linked above contain the following snippet:

When you use expressions in an if conditional, you may omit the expression syntax (${{ }}) because GitHub automatically evaluates the if conditional as an expression, unless the expression contains any operators. If the expression contains any operators, the expression must be contained within ${{ }} to explicitly mark it for evaluation.

However, according to my own experience (and a lot of examples I find on the web), the exception (“unless the expression contains any operators”) does not seem to be true. For example, the expression of the following if is evaluated.
jobs:
  my-job:
    runs-on: ubuntu-latest
    if: github.event_name == 'push' && github.ref == 'refs/heads/master'

Note that == and && are both operators. I think it is pretty confusing that a lot of examples on the web omit ${{ }} while the documentation claims that it would not work.

@JojOatXGME Thanks so much for opening an issue! I'll triage this for the team to take a look :eyes:

Thanks for raising this, @JojOatXGME; I can confirm this behavior as well, but I'll double-check with engineering that the current behavior is intended.

Confirmed with engineering that it's not necessary 👍. PR opened here: https://github.com/github/docs/pull/8786

Thanks for fixing the documentation. Good to know that my confusion was not caused by some fundamental misconception on my site. :D


Follow-up for parsing YAML dates

Small follow-up commit for https://github.com/silverbulletmd/silverbullet/commit/2eb7e25854000090bdb3a8729aed3c3c1f06e381#

removes pad function in favour of String.prototype.padStart
adds test cases for the date formatting

Thank you @zefhemel for not only taking the time to respond but also to fix a small bug in date parsing (discussion here https://community.silverbullet.md/t/struggling-with-yaml-frontmatter-date-attribute-and-date-comparison-query-in-silverbullet/454/13)
I thought I would also thank you for putting some of my time in. Let me know if this looks OK or if you want me to make any changes.
Since this is a pure refactoring, there doesn't have to be any CHANGELOG entry 👍

Thanks for cleaning this up 🙏


A request.

Hi! I didn't manage to find your contacts anywhere, so I only can write there. I can delete this issue later.
I am a sociology student, writing a graduate diploma thesis about cinema. I own statistical packages and plan to collect data from the sites kinopoisk, IMDb, rotten tomatoes, make descriptive statistics on them, twist a little data on python, build networks and conduct network analysis in R and Pajek. Parsing a kinopoisk is very difficult, but you know it yourself. Could you provide a csv copy of the database of films and actors of kinopoisk? I will be immensely grateful to you.... Maybe you have a sparse database of users and their reviews, ratings?
thank you in advance.
All the best,
Stepan.
<EMAIL_ADDRESS>

@stephen-iv Hi! Unfortunately, I don't have such a database, it's just a client for the API.

Oh, Thank you anyway. Do you think it's possible to get whole database from
this api within 500 available requests or 1 request is equal to 1 film in
output?
On Wed, Mar 1, 2023, 18:15 Master Weber @.***> wrote:

@stephen-iv https://github.com/stephen-iv Hi! Unfortunately, I don't
have such a database, it's just a client for the API
https://kinopoiskapiunofficial.tech/.
—
Reply to this email directly, view it on GitHub
https://github.com/masterWeber/kinopoisk-api-unofficial-client/issues/18#issuecomment-1450319371,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A6GQBMIYNOH4VXSYRAPTYU3WZ5RZNANCNFSM6AAAAAAVMBKYNY
.
You are receiving this because you were mentioned.Message ID:
@.***
com>

@stephen-iv I think you can, but it will take some time.


Storage Remove the redundant accessTier option in IBlockBlobCommitBlockListOptions.

Optimize the code in master branch.

Optimized it with a non-breaking approach. Keep this as a candidate fix to master branch, so it can be released with future master code if necessary.

Is this still relevant?
Should we take it for Track2?

@ramya-rao-a, This is fixed in preview 3 of v12 whereas 10.5 was released before the fix.
This is a breaking change for V10 which we wanted to avoid.
It is irrelevant to the current master branch since the master branch has V12 storage.
This PR can be ignored or should be appropriated by rebasing to a HotFix branch for V10.

If fix already in track2, it's safe to ignore it in v10. @jiacfan Sounds good?

We havent heard back from @jiacfan whether this is still relevant.
@XiaoningLiu believes that it is safe to ignore this as v12 has the fix.
Am closing this PR as master branch has already moved on to v12.
If this is still relevant, please make a hotfix for v10 following the hotfix branches intstructions


Partial Slashing

addresses #76
implements partial slashing. validator is not slashed until withdrawal period is up so that total slashed amount can be ascertained for the entire 2*withdrawal_period. Amount slashed scales as total slashable amount in the period increases. If 1/3 validators slashed, 100% is slashed (thus the 3* when calculating fraction_to_slash)

good to merge for me


[TextField] Fixed ie9-ie10 click focus problem

When using a hint, clicking on the span containing the hint removes the focus from the input (IE9-10). Weirdly, changing the background-color to rgba fixes the problem.

@Nic128 Could you try again on the master branch? We have merged https://github.com/callemall/material-ui/pull/3055 and https://github.com/callemall/material-ui/pull/3240 that might fix this. Otherwise a gif would be great. Thanks!

@oliviertassinari The issue still persist on master.

Retested my fix, and it works.

Retested my fix, and it works.

:flushed: I can't test on IE10. @alitaheri @newoga @mbrookes someone wants to test this or we just merge the PR?

The docs weren't opening on IE9 until I opened the console then refreshed the browser. (If anybody gets this problem testing)

I just checked my Windows VM and I have IE11 already, and I think going back a version is tough or impossible... :anguished: (couldn't reproduce in that version).
IE makes me sad.

I have IE11 already

So do I. This seems to be safe :+1:.

@Nic128 Thanks.


Change the button

Hey, I want to change the button UI according to the UI of website.

don't forget to add screen shot in pr

don't forget to add screen shot in pr

Yeah Sure!


 Is there a way to load the json files using an API?

Hey @AnkitaNaik were you able to figure this out? If not, can you give me the steps to recreate it?

@ShishirPatil Hey it seems that the problem still has not been solved. It comes from the fact that some rows have different data types for the same column. For example, api_arguments data type isn't consistent across rows (some are arrays and some are string) and so is python_environment_requirements
How can we solve this quickly?

The steps the reproduce are exactly as Ankita mentioned above:
from datasets import load_dataset
dataset = load_dataset("gorilla-llm/APIBench", split = 'train')


Lightweight viewer and logger to run from console

Should generate static web page, save to file and view in browser. Also log in memory for many stages.

Committed a quick and dirty interface in provingground.QDI. To use import this, and use view command on either html or something with an implicit conversion to html (at present including finite distributions)


[WIP] fix error not finding shared file lipoppler.so.76 when building the docs on CI

This is a hotfix for a follow-up problem when building the docs on CI because of the current restriction geopandas<0.5.0, see #227
This fix does not fix the issues with building the docs on readthedocs.

Coverage decreased (-0.3%) to 87.869% when pulling 0362843f21694668fcbaf748f457d9845084e66e on danielhuppmann:hotfix/libpoppler into 3a83f912ff2b5e59b6a39eddefdbb7b2fb42a86e on IAMconsortium:master.

lgtm, thanks @danielhuppmann!


[SPARK-47741] Added stack overflow handling in parser

What changes were proposed in this pull request?
Parser can throw stack overflow because of complex queries being generated.
We need to throw proper error, so clients can adjust their code based on error class.
This PR proposes we throw ParserException with proper error class, when parser hits StackOverflow
Why are the changes needed?
So client can catch and act on proper error classes parser errors.
Does this PR introduce any user-facing change?
Yes it adds new error
How was this patch tested?
Unit test
Was this patch authored or co-authored using generative AI tooling?
No

thanks, merging to master!

As reported by @LuciferYang , this PR seems to cause a flakiness in CIs. Let me reduce (1 to 20000) to (1 to 5000) while keeping ParseException.

Here is a follow-up.

https://github.com/apache/spark/pull/48092

Instead of the above, I proposed this temporarily. I filed SPARK-49622 to enable it back.

#48096


init pull request, merge azure-auto-deploy to open-hackathon in progress

please resolve conflicts ASAP than I can merge in


Provide "into-common-type" function

It would be useful to have this kind of method:
impl <L, R> Either<L, R> {
    fn into_common<T>(self) -> T where T: From<L> + From<R> {
        match self {
            Either::Left(l) => l.into(),
            Either::Right(r) => r.into(),
        }
    }
}

Does it sound a good idea?  If so, I'll send a PR.  I'm wondering what function name would be nice.

Sgtm


Change get_targets_for_source to use correct params

Source needs to be src and the last param in this call needs to be the correct association name.
Previously, cloud network list was only updated after selection of security group, or change of tab, or a select set of other actions that completely voided the list of parameters passed to the filtering method. This issue was fixed in https://github.com/ManageIQ/manageiq/pull/16688. Unfortunately I also introduced an issue where get_targets_for_source was not returning the right things because I wasn't calling it correctly, which this PR should fix.
Related to:
https://github.com/ManageIQ/manageiq-content/pull/241
https://bugzilla.redhat.com/show_bug.cgi?id=1518847

@gmcculloug @d-m-u Since this PR was backported to gaprindashvili, don't we want to also backport the spec file change PRs that are linked in this PR?

@simaishi Yes I would agree with that.  There is also a non-spec PR listed above: https://github.com/ManageIQ/manageiq-providers-openstack/pull/197
The remaining ones all appear to be spec only.  @d-m-u Are there any other PRs related to this work that may not be listed here?

Ignore that first part, I found that PR https://github.com/ManageIQ/manageiq-providers-openstack/pull/197 was replaced by https://github.com/ManageIQ/manageiq-providers-openstack/pull/202 which is already back-ported.

@d-m-u Can you please add gaprindashvili/yes labels to the appropriate PRs?  It seems there are more than what's linked in this PR.  For example.. this PR has a link to https://github.com/ManageIQ/manageiq/pull/16824 (this fixes what this PR broke?), which says https://github.com/ManageIQ/manageiq-providers-amazon/pull/394 is a related test change.


Availability Issues on AWS

Describe the bug
I had qhub working yesterday and was able to access JupyterHub and start my own kernel, but unfortunately, the hub and conda-store pods died. This seems to be a recurring problem in that the pods aren't stable and are perpetually stuck in "pending" after a couple hours. Would really appreciate some help on this!

Your environment
Conda version is 4.10.1
Qhub version is 0.3.11

Hey @rileyhun, have you had a chance to deploy a fresh QHub with the latest version (0.3.13)? We're hoping this resolves a lot of the issues you've been seeing :)

Hello @iameskild, I deployed and seems to be okay so far. Will know for sure tomorrow after more time has elapsed.
One follow-up question: are we supposed to install dask_gateway separately. From the installation instructions, I thought it would be out of the box working, but it's saying ModuleNotFoundError: No module named 'dask_gateway'

One follow-up question:
I'm trying to scale my dask cluster but I am not sure if it's working. The # workers and memory are still stuck at 0.

Hi @rileyhun, I'm glad to hear that things are working for you! Checkout this gist to get started using Dask:
https://gist.github.com/iameskild/1a45cbd114595fa371d2d127448c5e33
Closing issue.


fix: move type field to dist/esm/package.json

Fixes #204 as suggested in https://github.com/wagmi-dev/abitype/issues/204#issuecomment-1783939226.

PR-Codex overview
This PR focuses on adding the type field to the packageJson object and updating the build:esm+types script in the abitype package.
Detailed summary

Added type field to the packageJson object in .scripts/formatPackageJson.ts
Updated build:esm+types script in packages/abitype/package.json to include type as "module" and sideEffects as false

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Could you add a changeset?

Done


Better type for Apify.launchPlaywright()

The Apify.launchPlaywright() function returns any type but shouldn't it return the Browser type from the Playwright SDK?
const browser = (await Apify.launchPlaywright()) as Browser;

I'm currently using it like the above.

Current TS support is "experimental". At the beginning of next year we will release V3 which will be fully in TypeScript and the types will be much better.

cc @vladfrangu, not sure if this is covered in your PR, if not please address it afterwards in the TS repo
https://github.com/apify/apify-ts/blob/master/packages/apify/src/browser_launchers/playwright_launcher.ts#L148

It's already fixed in the PR 🎉
https://github.com/apify/apify-ts/blob/ts/strictess/packages/apify/src/browser_launchers/playwright_launcher.ts#L148

good, let's close this once we move the TS fork to this repository


⚠ Samsung has degraded performance

In 8e87eea, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2517 ms

Resolved: Samsung performance has improved in 5c62361.


kubecolor breaks on first argument after kubectl

Starting with kubectl v1.22, the first argument has changed.
kubectl v1.21.1

kubectl v1.22.12

This causes issues with tab completion using kubecolor.
kubecolor using kubectl v1.22 on first argument

kubecolor using kubectl v1.22 with all other arguments after the first

This is fixed in the new clone of the project.
Get it at https://github.com/kubecolor/kubecolor or brew install kubecolor/tap/kubecolor

I think this is fixed now


New generic inteface feasibility

Hello Roland,
The second part of my previous question was about the feasibility of a more generic
interface not binded to your primitives.  The rationale for this is that it would be lead to
more flexibilty and it will allow any kind of queries like in C# world with dapper.
https://github.com/StackExchange/Dapper
In dapper we have:
var sql = "SELECT * FROM Invoice WHERE Kind IN @Kind;";
using (var connection = My.ConnectionFactory())
{
	connection.Open();
	var invoices = connection.Query<Invoice>(sql, new {Kind = new[] {InvoiceKind.StoreInvoice, InvoiceKind.WebInvoice}}).ToList();
}

In a similar world would be:
auto queryText = "Select * from Cats where Color =%Color% and Age > :Age";
auto dynamicParameters = new sqlpp11::dynamic_params<string, int>({{ "Color", "Blue },
{ "Age", 2 }}});
auto prepared = db.prepare(queryText,dynamicParameters);
for(auto && row : db(prepared))
{
std::cout << row.color << std::endl;
}

Is it feasible? how is it difficult to do that?

Hi Roland,
Uhm looks like a constexpr to be parsed and enforce but i dont have yet enough spare cycles to do.

Closing this as out of scope for sqlpp11 (but could be a nice project)

@giorgiozoppi
Try sqlite_orm.


Backport new vendors support from master-qa.

Asana task A17
Signed-off-by: Jérôme Benoit<EMAIL_ADDRESS>

I will merge with master-qa as the unit tests have been delivered.
Thanks for this PR


Not letting me push to github

Pre-flight checklist

[X] I have read the contribution documentation for this project.
[X] I agree to follow the code of conduct that this project uses.
[X] I have searched the issue tracker for a bug that matches the one I want to file, without success.

Electron Forge version
5.2.4
Electron version
v27.0.1
Operating system
Windows 11
Last known working Electron Forge version
No response
Expected behavior
Create a github release
Actual behavior
An unhandled rejection has occurred inside Forge:
Error: In order to publish to github you must set the "github_repository.owner" and "github_repository.name" properties in your Forge config. See the docs for more info
at PublisherGithub.publish (C:\Users\user\Documents\GitHub\desktop-app-code\node_modules@electron-forge\publisher-github\dist\PublisherGithub.js:30:19)
at Task.task (C:\Users\user\Documents\GitHub\desktop-app-code\node_modules@electron-forge\core\dist\api\publish.js:45:41)
at Task.run (C:\Users\user\Documents\GitHub\desktop-app-code\node_modules\listr2\dist\index.cjs:978:35)
Steps to reproduce
try pushing to github
Additional information
{
"name": "yuriz",
"version": "1.2.0-canary",
"description": "The official Yuriz app",
"main": "main.js",
"scripts": {
"start": "electron-forge start",
"make": "electron-forge make",
"publish": "electron-forge publish",
"build:canary": "electron-forge publish canary",
"build:beta": "electron-forge publish beta",
"build:latest": "electron-forge publish latest"
},
"author": "Yuriz",
"config": {
"forge": {
"packagerConfig": {
"asar": true,
"icon": "assets/icon.png",
"extraFiles": [
{
"from": "config.json",
"to": "resources/app"
}
]
},
"makers": [
{
"name": "@electron-forge/maker-squirrel",
"config": {
"name": "yuriz",
"icon": "assets/icon.ico"
}
}
],
"publishers": [
{
"name": "@electron-forge/publisher-github",
"config": {
"github_repository": {
"owner": "TeamRCD",
"name": "desktop-app"
},
"channels": {
"canary": {
"url": "https://github.com/TeamRCD/desktop-app/releases/tag/canary",
"name": "Canary"
},
"beta": {
"url": "https://github.com/TeamRCD/desktop-app/releases/tag/beta",
"name": "Beta"
},
"latest": {
"url": "https://github.com/TeamRCD/desktop-app/releases/tag/latest",
"name": "Latest"
}
}
}
}
]
}
},
"license": "CC0-1.0",
"devDependencies": {
"@electron-forge/cli": "^6.0.0",
"@electron-forge/maker-squirrel": "^6.4.2",
"@electron-forge/publisher-github": "^6.4.2",
"electron": "^27.0.1"
},
"dependencies": {
"@electron/remote": "^2.0.12",
"electron-is-dev": "^2.0.0",
"electron-log": "^4.4.8",
"electron-updater": "6.1.4",
"undici": "^5.26.4"
}
}

As described in the Github publisher documentation, the correct property name is repository, not github_repository, so your publishers object should look like this:
"publishers": [
  {
    "name": "@electron-forge/publisher-github",
    "config": {
      "repository": {
        "owner": "TeamRCD",
        "name": "desktop-app"
      },
      "channels": {
        "canary": {
          "url": "https://github.com/TeamRCD/desktop-app/releases/tag/canary",
          "name": "Canary"
        },
        "beta": {
          "url": "https://github.com/TeamRCD/desktop-app/releases/tag/beta",
          "name": "Beta"
        },
        "latest": {
          "url": "https://github.com/TeamRCD/desktop-app/releases/tag/latest",
          "name": "Latest"
        }
      }
    }
  }
]

The error message you got is wrong (our bad), I'll fix that to reflect the correct property that we're expecting.
As an aside, I recommend you move your Forge configuration from your package.json to the forge.config.ts file in your project root, this makes it easier to catch any configuration errors. Here's an example:
// forge.config.ts

import { PublisherGitHubConfig } from '@electron-forge/publisher-github';
import { ForgeConfig } from '@electron-forge/shared-types';

const forgeConfig: ForgeConfig = {
  packagerConfig: {
    asar: true,
    icon: 'assets/icon.png',
    extraFiles: [
      {
        from: 'config.json',
        to: 'resources/app',
      },
    ],
  },
  makers: [
    {
      name: '@electron-forge/maker-squirrel',
      config: {
        name: 'yuriz',
        icon: 'assets/icon.ico',
      },
    },
  ],
  publishers: [
    {
      name: '@electron-forge/publisher-github',
      config: {
        repository: {
          owner: 'TeamRCD',
          name: 'desktop-app',
        },
        channels: {
          canary: {
            url: 'https://github.com/TeamRCD/desktop-app/releases/tag/canary',
            name: 'Canary',
          },
          beta: {
            url: 'https://github.com/TeamRCD/desktop-app/releases/tag/beta',
            name: 'Beta',
          },
          latest: {
            url: 'https://github.com/TeamRCD/desktop-app/releases/tag/latest',
            name: 'Latest',
          },
        },
      } as PublisherGitHubConfig,
    },
  ],
};

export default forgeConfig;

// package.json

{
  "name": "yuriz",
  "version": "1.2.0-canary",
  "description": "The official Yuriz app",
  "main": "main.js",
  "scripts": {
    "start": "electron-forge start",
    "make": "electron-forge make",
    "publish": "electron-forge publish",
    "build:canary": "electron-forge publish canary",
    "build:beta": "electron-forge publish beta",
    "build:latest": "electron-forge publish latest"
  },
  "author": "Yuriz",
  "license": "CC0-1.0",
  "devDependencies": {
    "@electron-forge/cli": "^6.0.0",
    "@electron-forge/maker-squirrel": "^6.4.2",
    "@electron-forge/publisher-github": "^6.4.2",
    "electron": "^27.0.1"
  },
  "dependencies": {
    "@electron/remote": "^2.0.12",
    "electron-is-dev": "^2.0.0",
    "electron-log": "^4.4.8",
    "electron-updater": "6.1.4",
    "undici": "^5.26.4"
  }
}

Note that you'll need to install ts-node as a dev dependency for the forge.config.ts file to work.


Heroku App is broken :(

For whatever reason, the live version of this on Heroku is broken.  It has been a phenomenal resource to the GURPS community, I hope it can be fixed.

Logs are unclear about what is happening. I've restarted it and it appears to work. Please notify me again if you find it crashing. Not sure why its doing this, last update was back in March 2020 and its been fine for months...


[RFC] Refactoring bitsandbytes/cuda_setup for enhanced cross-platform and device support.

Summary
This RFC aims to discuss and gather community input on refactoring the  bitsandbytes/cuda_setup module. The goal is to enhance its functionality, simplify the user experience across different hardware and operating systems, and prepare it for upcoming device support expansions.
Background
bitsandbytes has become instrumental in democratizing AI, thanks to its deep integration with hardware. Despite millions of monthly downloads, a fraction of users encounter issues, such as those detailed in #914. Our objective is to make bitsandbytes as easily usable (e.g. as easy as pip install bitsandbytes and load_in_4bit=True ) as possible while mostly hiding the complexities of the software-hardware boundary under the hood, maintaining the ease of installation and use, while improving error reporting and handling.
Current Challenges
Setup Module Issues

Bug Reports from python -m bitsandbytes: This feature, intended to simplify debugging, sometimes presents similar tracebacks for different underlying issues, causing confusion in the issue threads.
CUDA Install and Environment Challenges: Many problems arise not from bitsandbytes itself, but from user-side issues with CUDA installations, environment settings (e.g. LD_LIBRARY_PATH), or hardware configurations.
Perceived Reliability: There are some issues with the setup code that need be fixed. The code quality could be much better.

Diverse Hardware Landscape

GPU-Nvidia Variability: Different generations and capabilities (e.g., Compute Capability, tensor cores, data types).
Emerging GPU-AMD Support: Efforts like PR #756 are in progress to integrate AMD hardware.
Apple Silicon Requests: Interest shown in PR #257 and other contributions.
CPU Quantization: The initiative by Intel with PR #898 for device abstraction.

Operating System Variability

Linux as Primary OS: Continued focus on Linux support.
Windows and Apple Support: Evaluating and integrating community contributions for broader OS support:

Windows: Limited support atm, but high impact - need to evaluate the status quo, community contributions and come up with a roadmap
Apple: Currently, no support - Ongoing discussions, community contributions that weren't accepted so far and quite a high interest - need to further evaluate the status quo, community contributions and come up with a roadmap.

Proposed Improvements

Refactoring cuda_setup: Enhancing code quality and clarity to better handle the diverse hardware and OS scenarios.
Error Reporting Enhancement: Develop a more nuanced error reporting mechanism that reflects the source of issues as accurate as possible, while making the conflation of issues harder by providing distinct traces.
Community Engagement: Actively seeking community input, especially for cross-platform compatibility and new device support.
CI/CD Strategies: Discussing and implementing robust CI/CD processes to facilitate testing across various platforms and hardware.

Call to Action
We invite the community to provide feedback and suggestions on the following:

Improvements to the cuda_setup module.
Strategies for handling diverse hardware and operating systems.
Ideas for an effective CI/CD setup - we'll provide a separate RFC for that, but feel free to mention initial thoughts here as well.
Any other relevant insights or experiences.

Timeline and Milestones
We'll take an incremental take on improving the setup module. The more actionable and commonly agreed, the quicker we can implement.
Contribution and Feedback Mechanism
Please share your thoughts, suggestions, and feedback in the thread below.
Summary and Next Steps
This RFC serves as a starting point to get feedback and coordinate the collaborative effort to refine bitsandbytes's setup process. We aim to address the current challenges, embrace the diversity of hardware and operating systems, and build a robust, user-friendly setup. Your participation in this process is crucial, and we look forward to your valuable input.

See also PR #876, PR #873 for windows and PR #908

CPU Quantization: The initiative by Intel with https://github.com/TimDettmers/bitsandbytes/pull/898 for device abstraction.

Hey, one thing to clarify. The device abstraction proposed in https://github.com/TimDettmers/bitsandbytes/issues/894 and the PR https://github.com/TimDettmers/bitsandbytes/pull/898 are not only about CPU quantization but also for Intel GPU. Therefore, we tried to abstract out the interfaces that the backend needs to implement and also provided a registration mechanism for supporting new devices.

Hi @jgong5 @wkpark
Are you connected through slack to discuss more details about bnb refactor and iterate quickly on this? Can use your emails to send Slack invites?

This is really exciting!

Ideas for an effective CI/CD setup - we'll provide a separate RFC for that, but feel free to mention initial thoughts here as well.

GPU runners now appear to be available on GitHub Actions and I can't think of a more useful project to begin trialling their usage.
There is a lot of complexity regarding the number of different CUDA versions, hardware and other dependencies. For now one goal could be to get the test suite automated and running cleanly for a limited combination of CUDA versions/hardwares and then building out the build/deployment process from there.

Please see prior discussion in #252. I think the bullet points from your initial suggestion has been discussed prior to this, and some efforts have been made previously, including by myself (in PR #257 for example).
The key point here is if there is interest form the maintainer of this repo, @TimDettmers to support this effort here. This comment https://github.com/TimDettmers/bitsandbytes/issues/485#issuecomment-1636948744 seems to have indicated so, but it seems to have since died out.
Otherwise my input to this is

Figure out if portability is handled here, with the blessing of the maintainer(s). The alternative is to maintain a fork.  @Titus-von-Koeller do I understand you have interest in driving these changes to be mainlined in this repo?
See my comment here https://github.com/TimDettmers/bitsandbytes/issues/485#issuecomment-1656587288. Mainly, build in CMake, focus on getting everything to build on GitHub actions, test coverage. Get feature parity on CPU to be able to have test coverage on all hardware.
Then port kernel by kernel to hardware like MPS or Intel
As OP indicated, CUDA setup code is quirky. I think it tries to solve some edge cases better solved by following standard installation processes (look att PyTorch). But I am no expert. In any case, I think this library should focus on the kernels and leave CUDA setup to other frameworks/libraries.

I'm happy to spend some time reviving/rebasing any of the work on PR #257 that are of interest to the community, but I would like to get some commit from a maintainer that this actually has a chance of getting merged so it's not just a dead end.

@TAJD

GPU runners now appear to be available on GitHub Actions and I can't think of a more useful project to begin trialling their usage.
There is a lot of complexity regarding the number of different CUDA versions, hardware and other dependencies. For now one goal could be to get the test suite automated and running cleanly for a limited combination of CUDA versions/hardwares and then building out the build/deployment process from there.

Yes, getting build + testing automated is quite high up our list.
I also saw that Github blog post about GPU runners (this is still in beta) and already signed up for the beta in December, but we didn't get selected. Atm, the only way to get GPU runners is to self-host them, which in our case would mean we would need to spin them up in the cloud on demand. However, we decided that the engineering effort to get that working is currently better targeted at more pressing / high impact matters. Hugging Face is willing to support us with compute costs, once we decide to move ahead with this. If anyone is willing to contribute / collaborate on this topic, please let me know and we can figure out how/when to move forward.

@Titus-von-Koeller, I would like to find time to contribute. It's awesome that HF has capacity to support this!
Do let me know how the project would like to proceed - once there's a plan we can start to chip away at elements of it 🙂

Ah, I wasn't even aware of this conversation before opening #996 :)

Archiving this, because it's out of date and we ended up favoring other modes of interaction to coordinate.


training function error

Hi,
First, thank u for having shared ur code with us
I tried to apply ur code on my own data but I am getting this error

Can u help plz
Thank u

Make sure your dataset has the same format as https://github.com/synalp/NER
.
--
With Regards,
Dhanachandra | Research Engineer
+91-7600776547|<PHONE_NUMBER>
Dhanachandra<EMAIL_ADDRESS>ezDI
Healthcare Data Intelligence
"Empowering people to deliver innovative solutions that enhance human
life."
On Mon, Nov 23, 2020 at 1:21 AM rajae-Bens<EMAIL_ADDRESS>wrote:

Hi,
First, thank u for having shared ur code with us
I tried to apply ur code on my own data but I am getting this error
[image: Screen Shot 2020-11-22 at 8 50 21 PM]
https://user-images.githubusercontent.com/58187895/99915498-5be84580-2d04-11eb-8e9d-11f3788d82d3.png
Can u help plz
Thank u
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Dhanachandra/bert_crf/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACSTW4K2MAJ3GR3PCRB3MDLSRFTUJANCNFSM4T6V4OFQ
.

Yes it does and all the process before training is going very well
but as u see in the screen shot it stops when it starts the execution of the train function
I think because the memory is exhausted  it may be due to the length of my data be
I tried to change the maxlen in the pad function but It gave me an error
can u plz explain when to change the length of the data before feeding to BERT?

In Line number 113 make maxlen = 50 or whatever length of your choices.

First, thank s for the quick answer
Yes as I said I ve already dit this I fixed maxlen to 128 but it gave me an error

do u have any idea plz?
thank u

Please change the below line
do_pad = lambda x, seqlen: [sample[x][:128] + [0] * (seqlen - len(sample[x])) for sample in batch] # 0:

Hi,
Thank s for ur answer. The train function works now but it gave me an error in the conlleval.py file
when I read ur remarks in this file u said that it works for IOB2 or IOBES but I use only IOB in my data.
Is it possible to adapt it for IOB ? or it requires a big change for it?
here is the error

Can you share me a sentence of your dataset in conll formal. And also check if your chunk tag (B-ENTITY) is spitted by underscore( _ ) if so, replaced it by hyphen( - ).

As I said before my dataset has the IOB scheme
ex
Le O
restaurant B
se O
trouve O
en O
centre O
ville O

what is after B for the second token restaurant? If it is only B then make it something like B-TAG or B-ENTITY.
Also check the line number 42 return chunk_tag.split('-', maxsplit=1) in Conlleval.py

Yes It worked, I am really grateful for ur help
another question plz
How to predict one instance?

import spacy
import torch
spacy_tokenizer = spacy.load("en_core_web_sm", disable=["tagger", "parser", "ner"])
tokens = spacy_tokenizer(sentence)
bert_tokens = np.array(['[CLS]'])
orig_to_tok_map = np.array([], dtype="i")
begins = np.array([], dtype="i")
ends = np.array([], dtype="i")
original_token = np.array([])
for tmp_tok in tokens:
    new_token = np.array(self.bert_tokenizer.tokenize(tmp_tok.text))
    original_token = np.append(original_token, new_token)
    orig_to_tok_map = np.append(orig_to_tok_map, bert_tokens.shape[0])
    bert_tokens = np.append(bert_tokens, new_token)
    offset = sentence.find(token, offset)
    begins = np.append(begins, offset)
    ends = np.append(ends, offset + len(token))
    offset += len(token)
bert_tokens = np.append(bert_tokens, '[SEP]')
tok_ids = bert_tokenizer.convert_tokens_to_ids(bert_tokens)
attn_mask = [1] * len(tok_ids))
tok_ids = torch.LongTensor([tok_ids])
attn_mask = torch.LongTensor([attn_mask])
token_ids, attn_mask, org_tok_map
inputs = {'input_ids': token_ids.to(device),
          'attn_masks' : attn_mask.to(device)
         }
with torch.torch.no_grad():
    tag_seqs = model(**inputs)
for j, orig_tok_idx in enumerate(org_tok_map):
    print(token[i][j] + '\t')
    pred_tag = unique_labels[tag_seqs[0][orig_tok_idx]]
    if pred_tag == 'X':
        pred_tag = 'O'
    print(pred_tag + '\n')

Hi,
thank s for the code
But It gave me an error
in this line:  offset = sentence.find(token, offset)
NameError: name 'token' is not defined

Replace all token by tmp_tok.text

ok but for the offset variable, it must be referenced first no?

Obviously. And I just shared you the idea how you can get the prediction for a single sentence. I actually didn't run and test the code.You must be able to solve those small errors.

ok thank s for ur help


Stale or incorrect information in Nodes concept page

This page talks about pod-eviction-timeout (an argument passed to the [kube-controller-manager](https://kubernetes.io/docs/reference/command-line-tools-reference/kube-controller-manager/)) but the page referred does not contain anything about pod-eviction-timeout.
Looks like either Nodes is outdated or kube-controller-manager is missing this pod-eviction-timeout documentation.

Page: https://kubernetes.io/docs/concepts/architecture/nodes/

pod-eviction-timeout was deprecated in k8sv1.26 and rwill remove in k8sv1.27
Here is the PR: #113710

As it is deprecated we have to mention this as a note in the docs for v1. 26 and in v1.27, remove this from the docs.
Let's wait for others members, what they think about it.

/kind bug
/sig apps

/retitle Stale or incorrect information in Nodes concept page

/remove-sig apps
It's nice if people who deprecate a thing also track a docs update issue. However, I wouldn't expect SIG Apps to pick this up.

It's nice if people who deprecate a thing also track a docs update issue.

yeah, that will be really helpful.

As it is deprecated we have to mention this as a note in the docs for v1.26 and in v1.27, remove this from the docs.
Let's wait for others members, what they think about it.

@sftim your thoughts on this?

@kubernetes/sig-node-bugs: Could you please take a look?

/triage accepted

/assign @tzneal

@tzneal thanks for the PR. It is Ok for v1.27.
But I have one concern regarding v1.26 if we click on kube-controller-manager as mentioned above, we can't find pod-eviction-timeout as it is deprecated in v1.26. Either we have to remove this from v1.26 also or mention the Note in v1.26 docs regarding the depreciation.

It is mentioned under kube-controller-manager till k8s v1.25. Here is the following link for it:
https://v1-25.docs.kubernetes.io/docs/reference/command-line-tools-reference/kube-controller-manager/

But I have one concern regarding v1.26 if we click on kube-controller-manager as mentioned above, we can't find pod-eviction-timeout as it is deprecated in v1.26. Either we have to remove this from v1.26 also or mention the Note in v1.26 docs regarding the depreciation.

Hi @SergeyKanzhelev , @tzneal
Your thoughts on this


Wondering whether if there are segmentation labels

do you have human instance segmentation labels in your dataset?

Sorry, we don't!


chore(merge-back): 1.14.0

See CHANGELOG

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 4a2ca8a34f1f8439c74c22c2061c3542670202e3
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Improve accessibility

Material-UI provides lots of accessibility features that are not currently being taken advantage of.
Make sure that the page is very accessible.

@axe-core/react is set up and produces no errors.


update contributing.md

With reference to issue #91
Added the following -

Update your local and forked repo using upstream
Add an upstream
Squashing your commits into one
@avinashkranjan have a look!

@Utkarsh1999 is my PR ready to merge?

@all-contributors please add @khareyash05  for documentation


Mission changes

-Style layout change
-reserve mission on profile

Hi @leonard33 😎

Great work! This branch is okay to merge. 🎉
Highlights 🥳

Great design ✔
No linter errors ✔
Great job writing clean code. 🔥

Recommended Changes ♻

[x] Please try to improve the styles on the buttons when clicking the Join Mission and/or Leave Mission.
[x] Kindly make the missions page adapt to the mobile version

We can create a new branch for incoming changes.

Thanks 🥂
@mavericks-db
Feel free to leave any comments on any of the issues for better feedback in case you don't fully understand something. Make sure to tag @mavericks-db so that I can get notified.
Cheers and happy coding! 🥳


python3Packages.pykeyatome: init at 1.1.2

Motivation for this change
Python module to get data from Atome Key
https://github.com/jugla/pyKeyAtome
Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

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

2 packages built:

python38Packages.pykeyatome
python39Packages.pykeyatome