White page on startup

After launching the precompiled linux-64 version on Ubuntu 14.04 I get an empty (white) window.
The terminal says:
mirko@mirkobuntu ~/apps/linux-x64 $ ./yakyak
hconnect
asking for login credentials
2016-03-14 9:50:02 WARN no SAPISID cookie
2016-03-14 9:50:02 WARN no SAPISID cookie

Might it be related with the fact that I am using i3 window manager and 2 monitors?

I have the same thing on Ubuntu 15.10 linux-32. Here is what terminal shows after ./yakyak
hconnect
2016-03-15 16:52:17 WARN no SAPISID cookie
2016-03-15 16:52:17 WARN no SAPISID cookie
2016-03-15 16:52:17 WARN no SAPISID cookie
`

I fixed this by changing the electron version to 0.36.10 on Arch Linux

I disabled tray icon to solve this

I'm having same issue on Ubuntu 14.04 linux-64:
~/linux-x64$ ./yakyak
hconnect
asking for login credentials
2016-03-30 17:04:49 WARN no SAPISID cookie
2016-03-30 17:04:49 WARN no SAPISID cookie
2016-03-30 17:04:49 WARN no SAPISID cookie

dupe of #32

I'm having this issue on windows 10 x64


cmd/formulae.sh: fix spaces

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew style with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?
[ ] Have you successfully run brew man locally and committed any changes?

Fix two issues with spaces in the output of brew formulae. The space in front of a formula name is easy to visualize (see below), the other one is more subtle as it appears at the end of one formula name.
Before:
$ brew formulae | head -n 5
 xctool
a2ps
a52dec
aacgain
aalib

After:
$ brew formulae | head -n 5
a2ps
a52dec
aacgain
aalib
aamath

Review period skipped due to critical label.

Thanks @maxim-belkin!


Method name decision: fill vs. render

fill is better, given that nothing as actually being "rendered." Calling the schema method on a root type pieces together the bits of context into a description.


Fixes #809: supports UTF8 route names.

Coverage increased (+0.1%) to 99.577% when pulling e81f032602b0e3db26486f1d5558b186f640a606 on LeFnord:master into 5d15589480171e361edc59aacae212d37a2523b5 on ruby-grape:master.

Coverage increased (+0.1%) to 99.577% when pulling e81f032602b0e3db26486f1d5558b186f640a606 on LeFnord:master into 5d15589480171e361edc59aacae212d37a2523b5 on ruby-grape:master.

Coverage increased (+0.1%) to 99.577% when pulling e81f032602b0e3db26486f1d5558b186f640a606 on LeFnord:master into 5d15589480171e361edc59aacae212d37a2523b5 on ruby-grape:master.

Closes #809


Added CSS Output

For easy copy pasta

Going to close this, since https://github.com/notwaldorf/font-style-matcher/pull/13 added a copy-paste button! :)


Feature request: use == for highlighted text

Hi,
I'm not sure if this is now commonly accepted syntax, but it would be great if you could add the == fences to import/export.
I often use this to highlight important information in my documents and it gets "lost in translation" now.

We can detect highlighted text (or at least text that has some background color) in a Google Doc, but not all Markdown renderers recognize the ==highlighted text== syntax. We can add highlights though. Github Markdown does not recognize either of those but at least the HTML markup doesn't appear literally (except here where I used the character codes).

I'm inclined to add highlight as it fails gracefully if not supported by the Markdown renderer.


ObjectManager interface added

This patch adds org.freedesktop.DBus.ObjectManager interface to the default interfaces of the Node.
The interface implements GetManagedObjects method and it exposes InterfacesAdded and InterfacesRemoved although it doesn't implement automatic signal emission.
In addition this patch adds option to select the way introspection is presented. If expanded_intr option is True (False by default) the interface tree in introspection will be expanded i.e:

/
/com
/com/example
/com/example/sample0

else introspection is presented as before:

/com/example/sample0

Thanks for the contribution. It needs tests.

:+1:


assimp - aiGetMaterialTexture cuts first chars of texture Path

Environment

LWJGL version: 3.2.4
LWJGL build #: 2
Java version: jdk-13.0.1
Platform: Windows
Module: assimp

Description
Assimp retrieves name of the texture cut by first 4 first chars.
insted of "123.jpg"
i get "jpg    " - looks like the buffer is moved by 4 chars more than should be
Some issue with encoding or with buffer read length
Example material and code to retrieve data:
For material:
# Blender MTL File: 'None'
# Material Count: 1

newmtl Material.001
Ns 500.039216
Ka 0.000000 0.000000 0.000000
Kd 1.000000 1.000000 1.000000
Ks 1.000000 1.000000 1.000000
Ke 0.000000 1.200000 0.000000
Ni 0.500000
d 1.000000
illum 2
map_Kd 123.jpg

For fallowing code
AIString mTexPath = AIString.calloc();
			aiGetMaterialTexture(mMaterial, 1, 0, mTexPath, (IntBuffer) null, null, null, null, null, null);

			System.out.println(mTexPath.dataString());

result: "jpg    "
should be "123.jpg"

could this be issue with pointer struct?
public abstract class Struct extends Pointer.Default {
**protected static final int DEFAULT_PACK_ALIGNMENT = Platform.get() == Platform.WINDOWS ? 8 : 0x4000_0000;**
protected static final int DEFAULT_ALIGN_AS       = 0;

similar definition in Pointer interface
/** The value of {@code sizeof(long)} for the current platform. */
int CLONG_SIZE  = POINTER_SIZE == 8 && Platform.get() == Platform.WINDOWS ? 4 : POINTER_SIZE;

Hey @LordAlbion,
No, this is a simple type mismatch in LWJGL's definition for aiString. It was caused by this change, which I missed the last time the assimp bindings were updated. It will be fixed in the next 3.2.4 snapshot.

Thanks


Started a module, using CIM instead of WMI, remote support, credentials

I started building out a module.

I took the WMI settings approach and reworked it to use CIM session.
Added auto discovery of SSRS version.
Switched from username and password strings to using credentials
Added remote support with -ComputerName parameter
Added pipeline support for -ComputerName parameter for easier batch targeting groups of machines
Created new cmdlets that exposes all CIM Methods. Still need to review if some are just clutter and should be trimmed out later.

I know this is a large pull request but it should be all new files in a module folder. The existing standalone scripts are untouched. If we want to continue down the module route, those scripts would be easy to work into it. This would also solve the "install" scenario for the users.

Can you please add instructions on how to download the additional tools (PSake, BuildHelpers, and Pester) by updating the Readme.MD in the Scripts folder?

Yes I will. They are all available via the Find-Module and Install-Module command from PSGet but I will add that documentation.

Hi Kevin, thanks for this great contribution, to be honest we are learning how to do this with you and the community and we were really surprised by the passion and effort you put on it, we really appreciate it although to be honest we were expecting incremental improvements and because it was a big surprise contribution it took us a while to make some time aside of our current efforts (check out https://youtu.be/gkOG9HxRpZs for more details).
I was in the process of merging the pull request and found out the readme.md is still pending, from recent conversations with users of the existing scripts the thing that they have found more challenging is how setup the scripts to start using it, so the get started is key to allow the users to use it

No problem. I know your guys have a lot on your plate especially with
Ignite. I didn't make it out to the conference but I am still watching
sessions from that. Sorry for the overwhelming number of changes. I was
looking for a weekend project and the timing of this was perfect for that.
I just have not looped back to this until now.
With that said, I see you moved the scripts to a new repo and have already
integrated a lot of the ideas I was putting forward. I think what I should
do now is close that existing pull request and clone the new project. I
think the CIM based commands and my approach to the cmdlet parameters still
has value to the community. I'll work them into the new project and open a
new pull request. My plan after that is to build a DSC resource for a few
of them.
On Thu, Oct 6, 2016 at 11:17 AM, Jaime Tarquino<EMAIL_ADDRESS>wrote:

Hi Kevin, thanks for this great contribution, to be honest we are learning
how to do this with you and the community and we were really surprised by
the passion and effort you put on it, we really appreciate it although to
be honest we were expecting incremental improvements and because it was a
big surprise contribution it took us a while to make some time aside of our
current efforts (check out https://youtu.be/gkOG9HxRpZs for more details).
I was in the process of merging the pull request and found out the
readme.md is still pending, from recent conversations with users of the
existing scripts the thing that they have found more challenging is how
setup the scripts to start using it, so the get started is key to allow the
users to use it
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/Reporting-Services/pull/3#issuecomment-252012856,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHgBLfslDIJonj4Rsr8CD_AVUKeyydJNks5qxR8ggaJpZM4JstDf
.

Yes!!!, the new repo is for simplified installation , the CIM commands to access WMI looks pretty interesting and the ability to execute remote WMI sounds like a great next step, the only thing I will suggest to think about is that when I tried your PR it ask for credentials for every function (everybody loves to be asked for credentials every single time as much as everybody loves 2FA or complex passwords with at least 25 characters long ;))

Great feedback. I was crossing domains to a testlab in my testing so I
needed to specify the creds. I'll figure out why it was requiring it. I
truly intended for it to be optional just like the base WMI commands, even
for remote systems.
Publishing to the PS gallery is another option for ease of installation.
On Wed, Oct 12, 2016 at 10:38 AM, Jaime Tarquino<EMAIL_ADDRESS>wrote:

Yes!!!, the new repo is for simplified installation , the CIM commands to
access WMI looks pretty interesting and the ability to execute remote WMI
sounds like a great next step, the only thing I will suggest to think about
is that when I tried your PR it ask for credentials for every function
(everybody loves to be asked for credentials every single time as much as
everybody loves 2FA or complex passwords with at least 25 characters long
;))
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/Reporting-Services/pull/3#issuecomment-253250007,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHgBLZvyy-vYMZRmL2vpojinET-28RCeks5qzP7kgaJpZM4JstDf
.

Yes we plan to do it also in the gallery, still figuring out the best way to keep that one in sync automatically with the repo

Here is one approach that I am aware of:
http://ramblingcookiemonster.github.io/PSDeploy-Inception/
It's on my todo list too for my own modules.
On Wed, Oct 12, 2016 at 4:22 PM, Jaime Tarquino<EMAIL_ADDRESS>wrote:

Yes we plan to do it also in the gallery, still figuring out the best way
to keep that one in sync automatically with the repo
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/Reporting-Services/pull/3#issuecomment-253343561,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHgBLQfvlCOqcgHYPYMwEoj8C37wuu3-ks5qzU-wgaJpZM4JstDf
.

Hi Kevin closing the PR from our last conversation.
BTW the new repo also publish to the gallery so the new cmdlets can be installed using install-module ReportingServicesTools


⚠ Bofrost.be has degraded performance

In a19b66e, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1198 ms

Resolved: Bofrost.be performance has improved in 7ba3c7e.


Update DG and Diagrams

Codecov Report

Merging #221 (dab9bed) into master (7f88234) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #221   +/-   ##
=========================================
  Coverage     70.70%   70.70%
  Complexity      608      608
=========================================
  Files            90       90
  Lines          2062     2062
  Branches        226      226
=========================================
  Hits           1458     1458
  Misses          527      527
  Partials         77       77

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 7f88234...dab9bed. Read the comment docs.


Cleanup unused code, fix event handlers crash

Some weird names and typealiases were cleaned up (I don't think that Int8ArrayOrInt16ArrayOrInt32ArrayOrUint8ArrayOrUint16ArrayOrUint32ArrayOrUint8ClampedArrayOrFloat32ArrayOrFloat64ArrayOrDataView or typealias VoidFunction = (() -> Void) could be useful in any way). GlobalEventHandlers protocol which was only inherited by a single concrete type was removed with its extension becoming the extension of the corresponding class.
I've also cleaned up event handlers to retain and release closures when needed, which makes our single basic test pass in browsers. Basic CI config to verify that is added here.
A few other uses of JSClosure were updated accordingly to fix memory management. Unused ClosureHandler property wrapper is removed, leaving only OptionalClosureHandler.

Great point! I'm going to submit another PR to the generator soon to provide better tokenizer diagnostics, as I'm getting inscrutable errors with some other spec files. I hope I'm more familiar with the codebase by then to find a way to avoid overwriting manually updated files.


Entitlements Error

m trying to package up my electron app with electron-packager and submit to the app store, but App developer keeps failing with 2 errors. My entitlements are not matching its saying, but I have no idea where I am going wrong. I have a provisioning profile, but cannot open it to get the entitlements out of there. Is that what I will need to do?
Errors:
ERROR ITMS-90296: "App sandbox not enabled. The following executables must include the "com.apple.security.app-sandbox" entitlement with a Boolean value of true in the entitlements property list: [( "com.site.app.pkg/Payload/App.app/Contents/Frameworks/App Helper EH.app/Contents/MacOS/App Helper EH", "com.site.app.pkg/Payload/App.app/Contents/Frameworks/App Helper NP.app/Contents/MacOS/QuizzUmmah Helper NP", "com.ahadcove.quizz-ummah.pkg/Payload/QuizzUmmah.app/Contents/Frameworks/QuizzUmmah Helper.app/Contents/MacOS/QuizzUmmah Helper", "com.site.app.pkg/Payload/App.app/Contents/MacOS/App" )] Refer to App Sandbox page at https://developer.apple.com/devcenter/mac/app-sandbox/ for more information on sandboxing your app."
Entitlements Parent:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
  <dict>
    <key>com.apple.security.app-sandbox</key>
    <true/>
    <key>com.apple.security.network.client</key>
    <true/>
  </dict>
</plist>

Entitlements Child:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
  <dict>
    <key>com.apple.security.app-sandbox</key>
    <true/>
    <key>com.apple.security.inherit</key>
    <true/>
  </dict>
</plist>

Facing same issue.. any update?

Hi @saurabhsharma, I don't think @AhadCove posted any updates after opening the issue.
Would you mind posting the command you used to sign the app bundle here and we can try to work on your issue from there?

Hi sethlu,
I'm facing the same exact issue, I also followed the electron guide to packaging for the Mac App Store and getting the error message (please note my parent.plist and child.plist files are identitical to the ones provided in AhadCove's original post):
"ERROR ITMS-90296: "App sandbox not enabled. The following executables must include the "com.apple.security.app-sandbox" entitlement with a Boolean value of true in the entitlements property list: ... Refer to App Sandbox page at https://developer.apple.com/devcenter/mac/app-sandbox/ for more information on sandboxing your app."
The command I used to generate my package was:
electron-packager ./ MackinVIA --app-bundle-id=com.mackin.eReader.desktop --helper-bundle-id=com.mackin.eReader.desktop.helper --platform=mas --version=1.7.9 --icon=icons/mac/icon.icns --overwrite --out=builds --build-version=3900 --protocol=mackinvia --protocol-name=mackinvia app-category-type=public.app-category.education --prune=true && sh codesign-electron.sh
The contents of my codesign-electron.sh file are:
`#!/bin/bash
Name of your app.
APP="MackinVIA"
The path of your app to sign.
APP_PATH="builds/MackinVIA-mas-x64/MackinVIA.app"
The path to the location you want to put the signed package.
RESULT_PATH="builds/$APP.pkg"
The name of certificates you requested.
APP_KEY="3rd Party Mac Developer Application: Mackin Educational Resources (65HQKK7CFN)"
INSTALLER_KEY="3rd Party Mac Developer Installer: Mackin Educational Resources (65HQKK7CFN)"
The path of your plist files.
CHILD_PLIST="installers/child.plist"
PARENT_PLIST="installers/parent.plist"
FRAMEWORKS_PATH="$APP_PATH/Contents/Frameworks"
codesign -s "$APP_KEY" -f --entitlements "$CHILD_PLIST" "$FRAMEWORKS_PATH/Electron Framework.framework/Versions/A/Electron Framework"
codesign -s "$APP_KEY" -f --entitlements "$CHILD_PLIST" "$FRAMEWORKS_PATH/Electron Framework.framework/Versions/A/Libraries/libffmpeg.dylib"
codesign -s "$APP_KEY" -f --entitlements "$CHILD_PLIST" "$FRAMEWORKS_PATH/Electron Framework.framework/Versions/A/Libraries/libnode.dylib"
codesign -s "$APP_KEY" -f --entitlements "$CHILD_PLIST" "$FRAMEWORKS_PATH/Electron Framework.framework"
codesign -s "$APP_KEY" -f --entitlements "$CHILD_PLIST" "$FRAMEWORKS_PATH/$APP Helper.app/Contents/MacOS/$APP Helper"
codesign -s "$APP_KEY" -f --entitlements "$CHILD_PLIST" "$FRAMEWORKS_PATH/$APP Helper.app/"
codesign -s "$APP_KEY" -f --entitlements "$CHILD_PLIST" "$FRAMEWORKS_PATH/$APP Helper EH.app/Contents/MacOS/$APP Helper EH"
codesign -s "$APP_KEY" -f --entitlements "$CHILD_PLIST" "$FRAMEWORKS_PATH/$APP Helper EH.app/"
codesign -s "$APP_KEY" -f --entitlements "$CHILD_PLIST" "$FRAMEWORKS_PATH/$APP Helper NP.app/Contents/MacOS/$APP Helper NP"
codesign -s "$APP_KEY" -f --entitlements "$CHILD_PLIST" "$FRAMEWORKS_PATH/$APP Helper NP.app/"
codesign -s "$APP_KEY" -f --entitlements "$CHILD_PLIST" "$APP_PATH/Contents/MacOS/$APP"
codesign -s "$APP_KEY" -f --entitlements "$PARENT_PLIST" "$APP_PATH"
productbuild --component "$APP_PATH" /Applications --sign "$INSTALLER_KEY" "$RESULT_PATH"`

Hi @bookrides! From the limited info I am not sure about issue you have run into. If you try codesign -d --entitlements - <path-to-app> with the signed app, the output should tell you if your entitlements are added properly.
I'd also recommend checking out https://mintkit.net/electron-userland/electron-osx-sign/guide/, which generates an electron-osx-sign signing script for you.

@sethlu so I figured out what the issue was. I was chaining my npm command electron-packager with the codesign-electron.sh script. The Info.plist file that's generated from the electron-packager command  needs to have the <key>ElectronTeamID</key><string>TEAM_ID</string> added before the shell script is run to sign it. Anywho, I'm just posting this here in case anyone finds it helpful. Make sure before you sign your app that you've added the ElectronTeamID key pair to your Info.plist file


Allow filtering by date

2018 maps are fun sometimes but not always

Sure I'll add, for the while, you can filter by date in better song search and make a Playlist out of it which yoilu can use in shaffuru


Fixed #768.

The broker sent CONNACK even if MQTT connection hadn't been established.
It caused assertion failed.
In this case, the broker should simply close connection.

let me test if this is sufficient to resolve assertion


Update README.md with CLI usage instructions

Documentation for Command Line Interface development.
Some of us like package.json scripts
Thanks so much. Look forward to contributing more!

@jonathantneal #ping

So much words for every package. Can't we just leave a reference on CLI readme?

@TrySound this is true. Have just seen this in some of the plugins and some not. Doesn't seem to be a documenting convention on plugins. If we sit on the side of the fence of less is more then I'll close this PR.  As usual thanks for the input.

I like this. I hope the docs can be simplified,  but I see this as a step forward. Thank you @snuggs !


fix: compensate for invalid log files created by Delta Live Tables

It would appear that in some cases Delta Live Tables will create a Delta table which does not adhere to the Delta Table protocol.
The metaData action as a required schemaString property which simply doesn't exist. Since it appears that this only exists at version zero of the transaction log, and the actual schema exists in the following versions of the table (e.g. 1), this change introduces a default deserializer on the MetaData action which provides a simple empty schema.
This is an alternative implementation to #1305 which is a bit more invasive and makes our schema_string struct member Option<String> which I do not believe is worth it for this unfortunate compatibility issue
Closes #1305, #1302, #1357

Removing mention of #1357 from PR description, since I think tagging that was accidental.


feat: Add tool to compare gluon benchmark outputs

example:
<bin> benchmark/report.json benchmark/report2.json
Benchmark imap-append: Fastest (90th Percentile=3.243148348s) benchmark/report2.json
Benchmark imap-fetch: Fastest (90th Percentile=859.002547ms) benchmark/report2.json


New error message - Telegram

Hi guys,
After download and install new version CSharp, I received a new error message in the dashboard for Telegram Bot:
{"ok":false,"error_code":400,"description":"Bad Request: Can't parse message text: Can't find end of the entity starting at byte offset 89"}
(Despite this problem, the robot answers well)
How can I solve it?
Thanks!

This is the response we get from Telegram when they receive malformed markdown. The bad formatting could have come from your original message, or it could have been due some processing done by our service. An example would be if you included a single asterisk in your message. Telegram tries to interpret this as markdown, and never finds the closing asterisk. Can you check your outgoing message for unmatched markdown symbols?

Hi.
Thank for the answer.
I checked the messages that I am sending and there is none of the characters of the markdown table.
In addition, just now I I configured the TextFormat property to "plain". Even so, the error message on the dashboard remains. Is it necessary to wait some time to check dashboard?

@rmatosaw I've only ever seen this error message in the invalid markdown case, but there could certainly be other scenarios. Could you post a some sample text?
After doing some research, I see that our Telegram handler doesn't recognize the "plain" text format; it unconditionally treats it as markdown.  Sorry for any confusion. Removing bug label.

Hi guys,
today  I got a quite similar issue like @rmatosaw. Yesterday I added telegram to my channels and it worked fine, but today nothing works.

Has anybody a clue what to do ?

@Avartarus-Testicus Could you post a sample of message text that causes this error to be returned? This error is returned by Telegram when we send them invalid markdown. Note: Telegram does not natively support a plaintext message format. It is up to us to strip markdown symbols when your bot specifies plain formatting. Your sample message might help determine whether we have a bug in that process.

Re-adding bug tag. Telegram channel needs to strip markdown when text format is plain.

Ok, it looks like your bot is having trouble responding, but when we try to post a message to this effect back to the user via Telegram, Telegram rejects the message for having invalid markup. Here is the error message we're trying to send:
POST to lord_of_the_bots failed: *Sorry, Lord of the Bots is having a problem responding right now.*

The bot id contains three underscore characters. Telegram is trying to interpret them as markdown, and failing to match the third one.

Hi @eanders-MS , thanks for your fast response. Today I registered a new bot on the microsoft page with no underscore characters in the bot id. I hoped it would be enough, to work with telegram correctly again. But this time again, an issue occurred

Sorry for the slow response this time! Are you still seeing this issue?

@Avartarus-Testicus Closing this issue. Please post a comment here if you need additional assistance and I will reopen.


Remove unneeded calls to simtel_path_no_mock in unit tests

Related to #586
The function simtel_path_no_mock (defined in conf.py) is not needed for some (all?) of the unit tests.

Note: only tests/integration_tests/test_ray_tracing.py requires simtel_no_mock - but see #588 - this should be changed.

Let's discuss first in #588 before you continue with this PR.

I think we should review and merge this one. Should use the mock function (unless simtel_array is really needed).


Any possibility of a C-exported API?

Would it ever be a possibility of a C API for this? I don't know how possible this would actually be, since I haven't got the time to look through the codebase, but I feel like it would be nice as it would open up use to a plethora of different languages rather than just C++. I understand if this is not possible

The framework uses code generation to generate API for other languages. Currently only C# output is supported, but a C one is also possible. That said I have no plans on adding C support myself, it would have to be a contributor.
In the future please use discourse.bsframework.io for questions.

Ah ok, I understand (sorry for the late follow up lmao)


Provide TLS support for listening endpoint

Hi @GreenRover ,
due to our internal demand, I'm going to add TLS support to the listening endpoint of the exporter.
Initial commit is ready, but especially tests, more documentation and adjustments of docker build is outstanding.
So, this is not yet ready to merge - if you even want to include that into the official version - but still any feedback and annotations are appreciated.

Looks good for me!
We have the same issue but operate the exporter with openshift/kubernetes and leave the ssl termination be done by openshift.
But for standalone or pure docker operation makes this totally sense

Yeah, our central installations are running on openshift and k8s as well, so we're using the ingress controller to handle TLS there. However in future we plan to rollout the broker as well as the prometheus exporter in a couple thousand decentralized locations, only running on local Docker/Podman. That's why we need native TLS support.
Maybe I'm going to add at least Basic Auth authentication for the endpoint as well in future, we'll see...
As of now, I feel like the PR is complete. I did some testing with private certificates, extended the documentation, ...
Ready for review 😄

Is this pr ready to merge?

Yes, if you have no other objections to the implementation - it's tested and ready to merge.

Do you like to add auth feature first or needs a release?


enh: partial resync (full-resync fromTs argument) + slack implementation

This PR introduces an optional fromTs argument to the connectors admin client full-resync command to perform a partial resync all the way to an epoch:
./admin/cli.sh connectors full-resync --provider slack --wId <WORKSPACE_ID> --fromTs <MS_SINCE_EPOCH>

It currently only works for the slack connector.

Runbook updated here: https://www.notion.so/dust-tt/Runbook-Slack-connector-e59f50c458a64a9ea64f4fd17dacaffb?pvs=4


Using OpenCM9.04 + Exp 485 boards to communicate directly with ROS

Hello,
I'm currently having problems to communicate the OpenCM9.04 + EXP 485 boards with the dynamixel_workbench ROS package. I can detect the motors fine using the find_dynamixel script with Arduino IDE, but the ROS package node can't find any motors.
https://i.imgur.com/kOls0X9.png
https://i.imgur.com/q6LSFJS.png
I tried to use the script below to send communication from Serial (USB) over Serial3 (OpenCM 485) but ROS package still hasn't detected any motors:
#define CMD_PORT Serial   // USB
#define DXL_PORT Serial3  // UART1
#define DXL_BAUD 1000000

void setup() {
  CMD_PORT.begin(115200);
  DXL_PORT.begin(DXL_BAUD);
}

void loop() {
  update_dxl();
}

void update_dxl() {
  // USB TO UART1
  if (CMD_PORT.available()) {
    DXL_PORT.print((char) CMD_PORT.read());
  }

  // UART1 to USB
  if (DXL_PORT.available()) {
    // toggleLED();
    CMD_PORT.print((char) DXL_PORT.read());
  }
}

Is there any usb_to_dxl script that I can use with the OpenCM9.04 + EXP 485 boards to communicate directly with ROS?
Thanks.

Hi, @Iervolino458
OpenCM does not provide a bypass example separately.
There is a problem with your code. Because DYNAMIXEL is half-duplex, TX and RX must be determined with the DIR pin. Your code does not have this capability, so it seems that communication is not possible.
I think it would be helpful to refer to the usb_to_dxl example in OpenCR.
This is just a reference code and does not guarantee behavior.

@OpusK
I fixed the issue myself using DynamixelSDK to communicate data between Serial and Serial3.
I'm having another problem, however, regarding the motors velocity. I'm using XM540-W270 motors and I can't seem to slow velocity down even when setting velocity and acceleration parameters (control table). The motor is in position mode by the way.
How can I limit the motors velocity keeping the position operation mode?

@Iervolino458
You said you are using the workbench ROS package, are you using the SDK package now?
Anyway, it would be nice to raise the issue for each reporter issue.

Workbench
SDK

@OpusK
I'm using DynamixelWorkbench package to interface the motors with ROS. I've used SDK just as the usb port handler to develop the usb tosser.


Test result comment not shown

Issue:
The test result comment that can be added is not shown in the patient details.
Steps to reproduce:
Add a test result to a patient and add a comment.
Open the patient's detail page.
Desired Solution:
The comment should be saved(?) and shown.

Indeed, the comment field was not saved in the backend. I constructed a fix for that, but I am not sure whether the behaviour I coded is desired.
There are two types of comments that can be entered for tests. The first is entered by the testing site on probe association, the second by the lab performing the test. The question that arose to me is whether both types of comments need to be stored separately such that the latter is not overriding the former. I would greatly appreciate other opinions on that specific issue.


bounding box annotations for object detection

Hi! @mcordts , is there a doc for preparing the dataset for object detection task? do we just convert the polygonal to bounding boxes? Thank you!

Hi, Cityscapes does not officially provide bounding boxes. There is the CityPersons add-on which has boxes for pedestrians and riders.


The react template ships with broken CSS resource in production mode

<environment exclude="Development">
        <link rel="stylesheet" href="~/dist/site.css" asp-append-version="true" />
    </environment>

// Plugins that apply in production builds only
            new webpack.optimize.UglifyJsPlugin(),
            new ExtractTextPlugin('site.css')

Hosting environment: Production

and there is no site.cs there, this yields expected: Failed to load resource: the server responded with a status of 404 (Not Found) - not fancy for template content.
Thanks!

@SteveSandersonMS can you take a look?

I don't think this was really broken. It looks like you were trying to run in production mode without having built in production mode (i.e., having actually published, or at least run Webpack with the --prod flag, which causes it to run the new ExtractTextPlugin('site.css') logic).
In any case, the newer React templates are based on create-react-app and don't even have any custom Webpack config, so this issue could no longer apply anyway. Also I've just verified that the latest React template does publish correctly with its CSS.


404 not found error message for attachment preview

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number:
Reproducible in staging?: Needs Reproduction
Reproducible in production?: Needs Reproduction
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @grgia
Slack conversation (hyperlinked to channel name): expensify_quality
Action Performed:

Send an image as attachment in a chat

Expected Result:
Attachment displayed without any issue in preview and when opened
Actual Result:
404 not found error message for attachment preview but when opened no issue observed
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Standalone
[ ] Android: HybridApp
[ ] Android: mWeb Chrome
[ ] iOS: Standalone
[ ] iOS: HybridApp
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

View all open jobs on GitHub

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

@grgia I'm not able to replicate this, could you please provide more details about it? Were you sharing the image in a workspace chat, or a DM? What file type was it, etc?

Not overdue Melv :)

Bumped @grgia in Slack :)

@grgia small bump :)

If this is no longer happening, let's close it out


Methods for DidlObject.resources[0].uri

I have noticed that I use DidlObject.resources[0].uri quite often and it is also present in the SoCo code multiple times. Hardcoding the index [0] in so many places does not seem very good practice to me.
Therefore, I have added get_uri and set_uri methods to DidlObject as a shortcut.

Coverage decreased (-0.2%) to 60.681% when pulling d72f092ad60ee56ee920e2e6f0d8fea501af6cd0 on ghcs27:didl_object_uri_methods into 1d67f79ddfe2e2dbe8c203fe2b9d821077333c32 on SoCo:master.

Coverage decreased (-0.2%) to 60.681% when pulling df7ce4f4158333fe3fe52d9bcb847f05e381dfc1 on ghcs27:didl_object_uri_methods into 1d67f79ddfe2e2dbe8c203fe2b9d821077333c32 on SoCo:master.

Docstring updated!

Looks good. I'll merge.
BTW @ghcs27 if you feel like it, I have a couple a small documentation PR's waiting for review ;)

@ghcs27 can you add a comment about this change to the release notes thread?


[system] Import error when using Material UI styles with Remix v2

Hello, I'm upgrading my remix application from version 1 to version 2 and I am getting this error:
[info] building...
[info] built (14.8s)
node:internal/process/esm_loader:40
      internalBinding('errors').triggerUncaughtException(
                                ^

Error [ERR_UNSUPPORTED_DIR_IMPORT]: Directory import '/app/node_modules/@mui/material/styles' is not supported resolving ES modules imported from /app/build/index.js
Did you mean to import @mui/material/node/styles/index.js?
    at new NodeError (node:internal/errors:405:5)
    at finalizeResolution (node:internal/modules/esm/resolve:321:11)
    at moduleResolve (node:internal/modules/esm/resolve:980:10)
    at defaultResolve (node:internal/modules/esm/resolve:1193:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:404:12)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:373:25)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:250:38)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:76:39)
    at link (node:internal/modules/esm/module_job:75:36) {
  url: 'file:///app/node_modules/@mui/material/styles',
  code: 'ERR_UNSUPPORTED_DIR_IMPORT'
}

Node.js v18.20.3

I haven't found any possible solution. What should I do?
This is my package.json file:
{
  "name": "my-app",
  "private": true,
  "description": "",
  "license": "",
  "type": "module",
  "sideEffects": false,
  "scripts": {
    "build": "remix build",
    "dev": "remix dev -c 'node ./server.js'",
    "devnextweb": "remix dev -c 'cross-env NODE_ENV=nextweb node ./server.js'",
    "start": "remix build && cross-env NODE_ENV=production node ./server.js"
  },
  "dependencies": {
    "@emotion/react": "^11.9.0",
    "@emotion/styled": "^11.8.1",
    "@faker-js/faker": "^8.0.2",
    "@fortawesome/fontawesome-svg-core": "^6.1.1",
    "@fortawesome/free-solid-svg-icons": "^6.1.1",
    "@fortawesome/react-fontawesome": "^0.2.0",
    "@fullcalendar/core": "^6.1.8",
    "@fullcalendar/daygrid": "^6.1.8",
    "@fullcalendar/interaction": "^6.1.8",
    "@fullcalendar/react": "^6.1.8",
    "@fullcalendar/timegrid": "^6.1.8",
    "@mui/icons-material": "^5.15.19",
    "@mui/lab": "^5.0.0-alpha.170",
    "@mui/material": "^5.15.19",
    "@mui/styles": "^5.15.19",
    "@mui/x-date-pickers": "^7.6.1",
    "@remix-run/node": "^2.9.2",
    "@remix-run/react": "^2.9.2",
    "@remix-run/serve": "^2.9.2",
    "bcryptjs": "^2.4.3",
    "chart.js": "^4.3.0",
    "compression": "^1.7.4",
    "cross-env": "^7.0.3",
    "date-fns": "^2.29.3",
    "dayjs": "^1.11.5",
    "express": "^4.18.1",
    "i18next": "^22.5.0",
    "i18next-browser-languagedetector": "^7.0.2",
    "i18next-fs-backend": "^2.1.2",
    "i18next-http-backend": "^2.2.1",
    "morgan": "^1.10.0",
    "react": "^18.2.0",
    "react-chartjs-2": "^5.2.0",
    "react-dom": "^18.2.0",
    "react-dropzone": "^14.2.3",
    "react-i18next": "^13.2.0",
    "react-swipeable-views": "^0.14.0",
    "remix-i18next": "^5.1.1",
    "remix-utils": "^7.6.0",
    "sweetalert2": "^11.7.1",
    "uuid": "^8.3.2",
    "validator": "^13.7.0"
  },
  "devDependencies": {
    "@remix-run/dev": "^2.9.2",
    "@remix-run/eslint-config": "^2.9.2",
    "@types/bcryptjs": "^2.4.2",
    "@types/react": "^18.2.20",
    "@types/react-dom": "^18.2.7",
    "eslint": "^8.15.0",
    "nodemon": "^2.0.20",
    "npm-run-all": "^4.1.5",
    "typescript": "^4.6.4"
  },
  "engines": {
    "node": ">=18"
  }
}

Search keywords:

Please provide a reproduction using a GitHub repository or a live example on CodeSandbox or StackBlitz. Did you check this Stack Overflow thread: https://stackoverflow.com/questions/64453859/directory-import-is-not-supported-resolving-es-modules-with-node-js?

This should be possible after we release esm support. @DiegoAndai will have more answers. Right now, we are blocked on some issues from Next.js.

@DiegoAndai Hi!
How long do you think is it going to take for you to release the esm support?
Thanks!

Hi! We tried to implement it for v6, but it was not possible due to the Next.js issue mentioned: https://github.com/vercel/next.js/issues/65056. We're currently waiting for a response from the Next.js team, so sadly I cannot provide an estimated date. We'll try to do it ASAP, it's a priority for us.
Marked as on hold, blocked by: https://github.com/mui/material-ui/issues/30671

@DiegoAndai
Thank you! I will be waiting :)

@DiegoAndai Hi!
FYI: this is the issue that I am currently facing:
I have this in the file app/common/Theme/theme.tsx:
import { red } from "@mui/material/colors";

And it is throwing the following error:
Error: Directory import '/app/node_modules/@mui/material/colors' is not supported resolving ES modules imported from /app/build/index.js
Did you mean to import @mui/material/node/colors/index.js?
    at new NodeError (node:internal/errors:405:5)
    at finalizeResolution (node:internal/modules/esm/resolve:321:11)
    at moduleResolve (node:internal/modules/esm/resolve:980:10)
    at defaultResolve (node:internal/modules/esm/resolve:1193:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:404:12)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:373:25)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:250:38)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:76:39)
    at link (node:internal/modules/esm/module_job:75:36)

Thanks!

@titanve you should use serverModuleFormat: 'cjs' in your vite config, like this: https://github.com/mui/material-ui/blob/next/examples/material-ui-remix-ts/remix.config.js#L10. Do you have this?
If not, may I ask you to share your remix config here? Thanks 😊

Hi @DiegoAndai
I haven't installed vite yet. Should I install it as part of the migration process? I think is not necessary, is it?
Thanks!

Hey @titanve!
Remix uses Vite, so you shouldn't have to install it separately; it should already be installed. You should have a config file called remix.config.js, and in there you should have the following setting:
   serverModuleFormat: 'cjs',

(besides your other config options).
Let me know if that works 😊. Our example of a remix app might be a good guide for your app's setup: https://github.com/mui/material-ui/tree/next/examples/material-ui-remix-ts

@DiegoAndai hi!
Sorry for the late reply! This is my remix.config.js file content:
/**
 * @type {import('@remix-run/dev').AppConfig}
 */

module.exports = {
  ignoredRouteFiles: ['**/.*'],
  // appDirectory: "app",
  assetsBuildDirectory: 'public/build',
  serverModuleFormat: 'cjs',  // <--- ADDED THIS LINE AS YOU SUGGESTED
  // serverBuildPath: "build/index.js",
  // publicPath: "/build/",
};

I googled to come here with the same error and I hope this context will help someone
but for @titanve I was not sure if It would work for you. because I followed npx create-remix@latest : https://remix.run/docs/en/main/start/quickstart
it gen vite.config.ts not an old remix.config.js : https://remix.run/docs/en/main/file-conventions/vite-config
I didn't add serverModuleFormat: 'cjs'
and solve by adding '@mui/material',  '@mui/system', etc.. to ssr (for you it should be serverDependenciesToBundle) like this
export default defineConfig({
  ssr: {
    noExternal: [
      /^remix-utils.*/,
      "@mui/system",
      "@mui/icons-material",
      "@mui/lab",
      "@mui/material",
      "@mui/styles",
      "@mui/x-date-pickers"
    ],
  },
  plugins: [
    remix({
      future: {
        v3_fetcherPersist: true,
        v3_relativeSplatPath: true,
        v3_throwAbortReason: true,
      },
    }),
    tsconfigPaths(),
  ],
});

@titanve, could you share your project so I can debug it on my side? For example, upload it to github and share the link. This would be very helpful and speed up the process.

@DiegoAndai Hi
This is a private repo, I wonder how may I provide useful information in order to try to find a solution.
Thanks.

@DiegoAndai Hi!
I upgraded to version 6:
"@mui/lab": "^6.0.0-beta.14",
    "@mui/material": "^6.1.6",
    "@mui/styles": "^6.1.6",
    "@mui/system": "^6.1.6",
    "@mui/x-date-pickers": "^7.22.0",
    "@remix-run/express": "^2.13.1",
    "@remix-run/node": "^2.13.1",
    "@remix-run/react": "^2.13.1",
    "@remix-run/serve": "^2.13.1",

And now I am getting the following error:
[info] building...
[info] built (12.9s)
Error: Directory import '/app/node_modules/@mui/material/styles' is not supported resolving ES modules imported from /app/build/index.js
Did you mean to import @mui/material/node/styles/index.js?
   at new NodeError (node:internal/errors:405:5)
   at finalizeResolution (node:internal/modules/esm/resolve:321:11)
   at moduleResolve (node:internal/modules/esm/resolve:980:10)
   at defaultResolve (node:internal/modules/esm/resolve:1206:11)
   at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:404:12)
   at ModuleLoader.resolve (node:internal/modules/esm/loader:373:25)
   at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:250:38)
   at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:76:39)
   at link (node:internal/modules/esm/module_job:75:36)

Hey @titanve, so sorry for the delay.
May I ask you why do you have "@mui/styles" as a dependency still? Material UI v6 no longer uses this package.
I reiterate the ask for a minimal reproduction. This would help a lot. Either uploaded to GitHub or as a sandbox.


feat(genesis): generate combined allocs

#53  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @jakim929 and the rest of your teammates on  Graphite


D3fc plugin - area and heatmap charts

heatmap
area chart
multi layered axes labels, don't overlap eachother
gridlines spaced evenly to chart edges
minor bug fixes

Thanks for the PR!  This is a really outstanding addition - this plugin is really shaping up to be the future charting of choice for perspective!


Some fixes for slice API

@aldanor  Thanks for reviewing this. I think I've fixed all the issues raised in #26 :

First I've tried pixels.read_slice_1d::<Pixel>(s![.., 1]), which failed to compile:no method named `read_slice_1d` found for type `h5::hl::dataset::Dataset`

Added these methods to Dataset.

Slicing API should really be accessible directly from datasets; but that we can fix pretty easily.
2. Ok, next try: pixels.as_reader().read_slice_1d::<Pixel>(s![.., 1]), also fails to compile:
wrong number of type arguments: expected 2, found 1

Now this one's not very nice, having to provide a _ placeholder for a second type is counter-intuitive and may lead to problems with type inference.

Here's the ndarray slice method: https://docs.rs/ndarray/0.12.1/ndarray/struct.ArrayBase.html#method.slice.  They get around having the S type because they know D (the dimensionality of the input array), and Do, the dimensionality of the output of the slice.  This won't work for us.  What does work is to pass the slice as a trait object &AsRef<[SliceOrIndex]>.  This causes ~2 new virtual calls. Given that we're going to be calling into HDF5 multiple times to carry out this read/write, I'd be shocked if this had a noticeable perf impact.

Next one... pixels.as_reader().read_slice_1d::<Pixel, _>(s![.., 1])... it now compiles but fails at runtime:Error: ndim mismatch: expected 1, got 2

This one's actually strange. Looking up docstring for read_slice_1d(), we see "Reads the given slice of the dataset into a 1-dimensional array. The dataset must be 1-dimensional". Now, why does the dataset have to be 1-dimensional? I'm reading a column of a matrix here, what's wrong with that?..

The dimension checks were not correct. They're fixed here. The output dimension of the slice needs to match the D::NDIM, which can be smaller than the dimensionality of the Dataset

More placeholders...
5. Fixed: pixels.as_reader().read_slice::<Pixel, _, _>(s![.., 1]).. compiles but:
Error: ndim mismatch: expected 1, got 2

Fixed - same problem as 3.

@pmarks Apologies for not merging this sooner (been working on the build system) -- would you please rebase this on the latest master, and we'll then merge it in?
(The question re: slicing API remains open, I still think there's nicer ways to do this, but at least the current implementation won't have bugs and will be generally correct)

@aldanor - sorry quick question: when you say "please rebase this on the latest master", does that mean that I rewrite the history of this branch on top of latest master and force-push the result?  I'm not clear on the standard practice.
I've merged master, but I'm not sure that's what you wanted.

@pmarks Hey - no problem.

Let's say the latest commits in the master branch are A, B, C
You create a new feature branch and do some work, so now it looks like (A, B, C), X, Y, Z
Meanwhile, I've worked on a different branch, so my branch is (A, B, C), P, Q, R
I've merged my branched into master, so the new master is now A, B, C, P, Q, R
If you now rebase your branch onto master, your branch will look like this: (A, B, C, P, Q, R), X, Y, Z (as if you've forked your feature branch off the latest master and started working from there). Your feature branch can now be cleanly fast-forward-merged into the latest master without creating any merged commits.
Note that you will have to force-push your rebased branch.

In what cases git pull can be harmful?
How to avoid merge commits when pulling

@aldanor thanks - that's what I thought but was unsure about the force push. It's rebased now.


enhancement add some decheck log to debug

Proposed changes
now P0 have a case can't pass sometimes.
so add some debug log.
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall


show errors in create team from chat dialog

Not entirely sure how correct but I think this is it.
@keybase/react-hackers

:no_entry: Error rendering the commits 7a565cf9f5b7...adcff0a6d1a9 on linux. :mag_right: 26 errored, 7 new, 36 changed

Error in adcff0a6d1a9: Chat_No_Conversation-normal-ERROR

Error in 7a565cf9f5b7: You_Rekey-Normal-ERROR

Error in 7a565cf9f5b7: Devices_Devices_List-Devices-ERROR

Error in adcff0a6d1a9: Devices_Devices_List-Devices-ERROR

Error in 7a565cf9f5b7: Chat_Input-Normal-ERROR

Error in adcff0a6d1a9: Chat_Input-Normal-ERROR

Error in 7a565cf9f5b7: Chat_Inbox-You_Rekey_Selected-ERROR

Error in adcff0a6d1a9: Chat_Inbox-You_Rekey_Selected-ERROR (view)
Error in 7a565cf9f5b7: Chat_Inbox-You_Rekey-ERROR (view)
Error in adcff0a6d1a9: Chat_Inbox-You_Rekey-ERROR (view)
Error in 7a565cf9f5b7: Chat_Inbox-Selected_Normal-ERROR (view)
Error in adcff0a6d1a9: Chat_Inbox-Selected_Normal-ERROR (view)
Error in 7a565cf9f5b7: Chat_Inbox-Selected_Muted-ERROR (view)
Error in adcff0a6d1a9: Chat_Inbox-Selected_Muted-ERROR (view)
Error in 7a565cf9f5b7: Chat_Inbox-Part_Rekey_Selected-ERROR (view)
Error in adcff0a6d1a9: Chat_Inbox-Part_Rekey_Selected-ERROR (view)
Error in 7a565cf9f5b7: Chat_Inbox-Part_Rekey-ERROR (view)
Error in adcff0a6d1a9: Chat_Inbox-Part_Rekey-ERROR (view)
Error in 7a565cf9f5b7: Chat_Inbox-Normal-ERROR (view)
Error in adcff0a6d1a9: Chat_Inbox-Normal-ERROR (view)
Error in 7a565cf9f5b7: Chat_Inbox-Long_Top-ERROR (view)
Error in adcff0a6d1a9: Chat_Inbox-Long_Top-ERROR (view)
Error in 7a565cf9f5b7: Chat_Inbox-Long_Bottom-ERROR (view)
Error in adcff0a6d1a9: Chat_Inbox-Long_Bottom-ERROR (view)
Error in 7a565cf9f5b7: Chat_Inbox-Empty-ERROR (view)
Error in adcff0a6d1a9: Chat_Inbox-Empty-ERROR (view)
Added: You_Rekey-Normal (view)
Added: Chat_Banner_Invite-Invite (view)
Added: Chat_Banner_Info-Info (view)
Added: Chat_Banner_Error-Error (view)
Added: Chat_Banner_Broken-Broken_Tracker_3 (view)
Added: Chat_Banner_Broken-Broken_Tracker_2 (view)
Added: Chat_Banner_Broken-Broken_Tracker_1 (view)
Changed: Text-Body_Wrap_Announcements (before) (after) (diff)
Changed: Text-Body_Small_Semibold_Italic_Documentation (before) (after) (diff)
Changed: Text-Body_Big_Documentation (before) (after) (diff)
Changed: Colors-white_20_rgba_255_255_255_0_20 (before) (after) (diff)
Changed: Colors-white_0_rgba_255_255_255_0 (before) (after) (diff)
Changed: Colors-orange_ff_6_f_21 (before) (after) (diff)
Changed: Colors-grey_cccccc (before) (after) (diff)
Changed: Colors-green_3_E_8_FAF_3 (before) (after) (diff)
Changed: Colors-dark_Blue_3_0_a_3052 (before) (after) (diff)
Changed: Colors-blue_5_F_8_FAFD (before) (after) (diff)
Changed: Colors-blue_4_ebf_5_fc (before) (after) (diff)
Changed: Colors-blue_2_66_b_8_ff (before) (after) (diff)
Changed: Colors-black_10_rgba_0_0_0_0_10 (before) (after) (diff)
Changed: Colors-black_05_rgba_0_0_0_0_05 (before) (after) (diff)
Changed: Checkbox-Disabled_unchecked (before) (after) (diff)
Changed: Buttons-Unfollow (before) (after) (diff)
Changed: Buttons-Secondary_waiting (before) (after) (diff)
Changed: Buttons-Secondary_small (before) (after) (diff)
Changed: Buttons-Secondary_full_Width_waiting (before) (after) (diff)
Changed: Buttons-Primary_disabled (before) (after) (diff)
Changed: Buttons-Follow_small_waiting (before) (after) (diff)
Changed: Buttons-Danger_small_waiting (before) (after) (diff)
Changed: Buttons-Danger_full_Width (before) (after) (diff)
Changed: Buttons-Danger (before) (after) (diff)
Changed: Avatar-Normal_x_80 (before) (after) (diff)
Changed: Avatar-Normal_x_32 (before) (after) (diff)
Changed: Avatar-Normal_x_24 (before) (after) (diff)
Changed: Avatar-Mutual_Follow_x_64 (before) (after) (diff)
Changed: Avatar-Mutual_Follow_x_48 (before) (after) (diff)
Changed: Avatar-Follows_You_x_80 (before) (after) (diff)
Changed: Avatar-Follows_You_x_16 (before) (after) (diff)
Changed: Avatar-Follows_You_x_112 (before) (after) (diff)
Changed: Avatar-Following_x_32 (before) (after) (diff)
Changed: Avatar-Following_x_176 (before) (after) (diff)
Changed: Avatar-Fallback_x_48 (before) (after) (diff)
Changed: Avatar-Fallback_x_16 (before) (after) (diff)

@buoyad how about now?

@zanderz I'm still seeing the error message persist from dialog to dialog, i.e. if I open one up and error it out and then open it again. I think adding the lifecycle hook from new-team/container.js to new-team-dialog-container.js's compose should fix it!

@buoyad sorry for all the back and forth, I addressed that last thing last week

@keybase/react-hackers @buoyad should be ready now?

@zanderz what I'm seeing is:

Click turn into team & type in bad team name. Hit submit so red bar error shows up
Exit out of the dialog
Click turn into team again -> red bar error still appears

sorry, looks like I had an un-pushed commit locally.


"File is busy" error msg [low priority]

NOTE: This issue appeared to go away after about 10 mins.

This is connected to the Long Password issue on the same system setup.
This
Steps:

Add the file that was used when the program crashed in the last example, use a smaller password

Defect: Get "File is busy" error msg

Perhaps,
It seems that it is caused by the termination processing of the word file.
I will fix it in the next release (version <IP_ADDRESS>).

Perhaps,
This is probably because the word file termination processing is not correctly done when encrypting it.
I will fix it in the next release (version <IP_ADDRESS>).

Closing this case since the long password issue has been resolved.


Add task barrier to workflow graph

Add a generic barrier policy to workflow graph. Move Mistral specific join to the Mistral workflow graph composer.

Codecov Report

Merging #11 into master will increase coverage by 0.01%.
The diff coverage is 95.45%.

@@           Coverage Diff            @@
##           master    #11      +/-   ##
========================================
+ Coverage   91.98%    92%   +0.01%
========================================
  Files          28     28
  Lines        1123   1125       +2
  Branches      242    242
========================================
+ Hits         1033   1035       +2
  Misses         47     47
  Partials       43     43

Impacted Files
Coverage Δ

orchestra/composition.py
89% <100%> (+0.34%)
:arrow_up:

orchestra/composers/base.py
91.66% <100%> (-0.76%)
:arrow_down:

orchestra/composers/mistral.py
93.87% <92.59%> (-1.68%)
:arrow_down:

Continue to review full report at Codecov.

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


[BUG] Wrong Assume pragmas

As pointed out by Piotr Trojanek in the SPARK discussion mailing list, the Assume pragmas were wrong and not correctly catering for the fact that an empty input array with rather "interesting" bound could be passed to Encrypt/Decrypt_Bytes and Process_AAD, This is a rather serious bug as it would have opened the door to a DoS attack on the implementation if runtime checks were enabled.
The prover was right, after all.

Fixed in commit b9d708589c0b39e6498b7c1eb5fdfca681d7f240


Stanford cars download url is broken - HTTP 404

🐛 Describe the bug
The Stanford Cars dataset is not available on the url from source code
https://pytorch.org/vision/main/_modules/torchvision/datasets/stanford_cars.html
Reproduce error:
import torch
import torchvision

train = torchvision.datasets.StanfordCars(root=".", download=True)

I get the following error
HTTPError                                 Traceback (most recent call last)
Cell In[18], line 4
      1 import torch
      2 import torchvision
----> 4 train = torchvision.datasets.StanfordCars(root=".", download=True)

File [~/Projects/diffusion/env/lib/python3.10/site-packages/torchvision/datasets/stanford_cars.py:60](https://file+.vscode-resource.vscode-cdn.net/Users/mo/Projects/diffusion/diffusion/~/Projects/diffusion/env/lib/python3.10/site-packages/torchvision/datasets/stanford_cars.py:60), in StanfordCars.__init__(self, root, split, transform, target_transform, download)
     57     self._images_base_path = self._base_folder [/](https://file+.vscode-resource.vscode-cdn.net/) "cars_test"
     59 if download:
---> 60     self.download()
     62 if not self._check_exists():
     63     raise RuntimeError("Dataset not found. You can use download=True to download it")

File [~/Projects/diffusion/env/lib/python3.10/site-packages/torchvision/datasets/stanford_cars.py:94](https://file+.vscode-resource.vscode-cdn.net/Users/mo/Projects/diffusion/diffusion/~/Projects/diffusion/env/lib/python3.10/site-packages/torchvision/datasets/stanford_cars.py:94), in StanfordCars.download(self)
     91 if self._check_exists():
     92     return
---> 94 download_and_extract_archive(
     95     url="https://ai.stanford.edu/~jkrause/cars/car_devkit.tgz",
     96     download_root=str(self._base_folder),
     97     md5="c3b158d763b6e2245038c8ad08e45376",
     98 )
     99 if self._split == "train":
    100     download_and_extract_archive(
    101         url="https://ai.stanford.edu/~jkrause/car196/cars_train.tgz",
...
File [/usr/local/Cellar/python](https://file+.vscode-resource.vscode-cdn.net/usr/local/Cellar/python)@3.10[/3.10.10_1/Frameworks/Python.framework/Versions/3.10/lib/python3.10/urllib/request.py:643](https://file+.vscode-resource.vscode-cdn.net/3.10.10_1/Frameworks/Python.framework/Versions/3.10/lib/python3.10/urllib/request.py:643), in HTTPDefaultErrorHandler.http_error_default(self, req, fp, code, msg, hdrs)
    642 def http_error_default(self, req, fp, code, msg, hdrs):
--> 643     raise HTTPError(req.full_url, code, msg, hdrs, fp)

HTTPError: HTTP Error 404: Not Found

Versions
PyTorch version: 2.0.0
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A
OS: macOS 13.2.1 (x86_64)
GCC version: Could not collect
Clang version: 14.0.0 (clang-14<IP_ADDRESS>)
CMake version: version 3.19.8
Libc version: N/A
Python version: 3.10.10 (main, Feb 16 2023, 02:58:25) [Clang 14.0.0 (clang-14<IP_ADDRESS>)] (64-bit runtime)
Python platform: macOS-13.2.1-x86_64-i386-64bit
Is CUDA available: False
CUDA runtime version: No CUDA
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True
CPU:
Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
Versions of relevant libraries:
[pip3] mypy-extensions==1.0.0
[pip3] numpy==1.24.3
[pip3] torch==2.0.0
[pip3] torchaudio==2.0.1
[pip3] torchvision==0.15.1
[conda] blas                      1.0                         mkl
[conda] mkl                       2019.4                      233
[conda] mkl-service               2.3.0            py38h9ed2024_0
[conda] mkl_fft                   1.2.1            py38ha059aab_0
[conda] mkl_random                1.1.1            py38h959d312_0
[conda] numpy                     1.20.1                   pypi_0    pypi
[conda] numpy-base                1.19.2           py38hcfb5961_0
[conda] numpydoc                  1.1.0              pyhd3eb1b0_1
[conda] pytorch3d                 0.4.0                    pypi_0    pypi
[conda] torch                     1.9.0                    pypi_0    pypi
cc @pmeier

It's not just the download, the whole website seems to be down: https://ai.stanford.edu/~jkrause/cars/car_dataset.html. Googling for this dataset reveals that this is still the "current" address. Meaning, maybe this is temporary and will come back up. We should monitor this and maybe reach out to the authors in case this persists.
Wondering why our download tests didn't catch this :thinking:

I met the same problem. And I have not find a mirror link to download link. Hope them can fix it as soon as possible.

For people looking for a quick solution:
You can download the dataset from kaggle and use the following class to create a torch Dataset.
class StanfordCars(torch.utils.data.Dataset):
    def __init__(self, root_path, transform = None):
        self.images = [os.path.join(root_path, file) for file in os.listdir(root_path)]
        self.transform = transform

    def __len__(self):
        return len(self.images)

    def __getitem__(self, index):
        image_file = self.images[index]
        image = Image.open(image_file).convert("RGB")
        if self.transform:
            image = self.transform(image)
        return image[None]

Thank you @IamMohitM, we can use data = torchvision.datasets.StanfordCars(root="./", download=True) and with the following steps and avoid changes to the code

Download dataset bundle from kaggle, extract, and remove recursive directory structure (eg stanford_cars/cars_test/cars_test)
Download car_devkit.tgz, also put in stanford_cars

Confirm dataset structures are as follows:
└── stanford_cars
    └── cars_train
        └── .jpg
    └── cars_test
        └── .jpg
    └── devkit
        ├── cars_meta.mat
        ├── cars_test_annos.mat
        ├── cars_train_annos.mat
        ├── eval_train.m
        ├── README.txt
        └── train_perfect_preds.txt

Thank you @IamMohitM, we can use data = torchvision.datasets.StanfordCars(root="./", download=True) and with the following steps and avoid changes to the code
* Download dataset bundle from [kaggle](https://www.kaggle.com/datasets/jessicali9530/stanford-cars-dataset), extract, and remove recursive directory structure (eg `stanford_cars/cars_test/cars_test`)

* Download [car_devkit.tgz](https://github.com/pytorch/vision/files/11644847/car_devkit.tgz), extract it in `stanford_cars`

Confirm dataset structures are as follows:
└── stanford_cars
    └── cars_train
        └── .jpg
    └── cars_test
        └── .jpg
    └── devkit
        ├── cars_meta.mat
        ├── cars_test_annos.mat
        ├── cars_train_annos.mat
        ├── eval_train.m
        ├── README.txt
        └── train_perfect_preds.txt

But the annotation of the test set is still not available.

Thank you @IamMohitM, we can use data = torchvision.datasets.StanfordCars(root="./", download=True) and with the following steps and avoid changes to the code
* Download dataset bundle from [kaggle](https://www.kaggle.com/datasets/jessicali9530/stanford-cars-dataset), extract, and remove recursive directory structure (eg `stanford_cars/cars_test/cars_test`)

* Download [car_devkit.tgz](https://github.com/pytorch/vision/files/11644847/car_devkit.tgz), extract it in `stanford_cars`

Confirm dataset structures are as follows:
└── stanford_cars
    └── cars_train
        └── .jpg
    └── cars_test
        └── .jpg
    └── devkit
        ├── cars_meta.mat
        ├── cars_test_annos.mat
        ├── cars_train_annos.mat
        ├── eval_train.m
        ├── README.txt
        └── train_perfect_preds.txt

But the annotation of the test set is still not available.

A cars_test_annos_withlabels.mat should be placed into  base folder。（something like “stanford_cars\cars_test_annos_withlabels.mat”）

@iamchenxin Just to clarify what you mean:
The original file cars_test_annos.mat in the devkit/ folder you mentioned does NOT contain the annotated labels, so it's not enough to download the dataset from Kaggle and the devkit you sent. I found the cars_test_annos_withlabels.mat file in one of the examples from the Kaggle dataset:
https://www.kaggle.com/code/subhangaupadhaya/pytorch-stanfordcars-classification/input?select=cars_test_annos_withlabels+(1).mat
and I'm sure that other code examples also load this file as part of their input. So to summarize, we need:

The original Kaggle dataset: https://www.kaggle.com/datasets/jessicali9530/stanford-cars-dataset?datasetId=30084&sortBy=dateCreated&select=cars_test
The devkit: car_devkit.tgz
The cars_test_annos_withlabels.mat file: https://www.kaggle.com/code/subhangaupadhaya/pytorch-stanfordcars-classification/input?select=cars_test_annos_withlabels+(1).mat

The directory structure you provided earlier works well once we add the missing file!
└── stanford_cars
    └── cars_test_annos_withlabels.mat
    └── cars_train
        └── *.jpg
    └── cars_test
        └── .*jpg
    └── devkit
        ├── cars_meta.mat
        ├── cars_test_annos.mat
        ├── cars_train_annos.mat
        ├── eval_train.m
        ├── README.txt
        └── train_perfect_preds.txt

data = torchvision.datasets.StanfordCars(root="./", download=True)

Hope that this helps! @pgsld23333 @IamMohitM let me know if I missed something.

@iamchenxin Just to clarify what you mean:
The original file cars_test_annos.mat in the devkit/ folder you mentioned does NOT contain the annotated labels, so it's not enough to download the dataset from Kaggle and the devkit you sent. I found the cars_test_annos_withlabels.mat file in one of the examples from the Kaggle dataset:
https://www.kaggle.com/code/subhangaupadhaya/pytorch-stanfordcars-classification/input?select=cars_test_annos_withlabels+(1).mat
and I'm sure that other code examples also load this file as part of their input. So to summarize, we need:

The original Kaggle dataset: https://www.kaggle.com/datasets/jessicali9530/stanford-cars-dataset?datasetId=30084&sortBy=dateCreated&select=cars_test
The devkit: car_devkit.tgz
The cars_test_annos_withlabels.mat file: https://www.kaggle.com/code/subhangaupadhaya/pytorch-stanfordcars-classification/input?select=cars_test_annos_withlabels+(1).mat

The directory structure you provided earlier works well once we add the missing file!
└── stanford_cars
    └── cars_test_annos_withlabels.mat
    └── cars_train
        └── *.jpg
    └── cars_test
        └── .*jpg
    └── devkit
        ├── cars_meta.mat
        ├── cars_test_annos.mat
        ├── cars_train_annos.mat
        ├── eval_train.m
        ├── README.txt
        └── train_perfect_preds.txt

If the script/notebook we're writing the code in is at the same directory level as the stanford_cars/ folder, we can write:
data = torchvision.datasets.StanfordCars(root="./", download=True)

Hope that this helps! @pgsld23333 @IamMohitM let me know if I missed something.

thanks a lot! it's really helpful

@pmeier Its been almost a year and this hasn't been remedied yet. Whats the plan going forward? removing it or keeping it broken like this?

Thanks all for the reports. Unfortunately the URL has been consistently broken for a while now, so we decided to disable the (broken) download functionality. Passing download=True will now result in an error, and point the users to @thefirebanks 's  https://github.com/pytorch/vision/issues/7545#issuecomment-1631441616, suggesting to download the dataset manually from Kaggle. Thank you @thefirebanks for the very helpful instructions.

Looks like the existing datasets are either missing some files or not fully conforming to the torchvision's required structures. A new dataset is created on Kaggle that is compatible with the latest version of torchvision: https://www.kaggle.com/datasets/rickyyyyyyy/torchvision-stanford-cars
The dataset can be setup with
import kaggle
kaggle.api.dataset_download_files('rickyyyyyyy/torchvision-stanford-cars', path=YOUR_DATA_PATH, unzip=True)

And then can be used by torchvision
import torchvision
data = torchvision.datasets.StanfordCars(root=YOUR_DATA_PATH, download=False)

Hi, and thanks, @rygx, for your help!
I could put this version of the dataset on Zenodo (giving credits to the original owners, and to you if you wish) to make it accessible directly from a URL so as to definitely fix this problem. Let me know if that would be helpful.
Have a great day.

Loading the dataset was not straightforward for me, but I eventually got something to work.
I downloaded this version from kagglehub and saved them in my google drive:
import kagglehub
path = kagglehub.dataset_download("emanuelriquelmem/stanford-cars-pytorch")

This will plot the images:
import os
import matplotlib.pyplot as plt
import matplotlib.image as mpimg

def show_images(dataset_path, num_samples=20, cols=4):
    """ Plots some samples from the dataset """

    # Get a list of all image files in the folder
    image_files = [f for f in os.listdir(dataset_path) if f.endswith('.jpg')]

    plt.figure(figsize=(15,15))

    for i in range(min(num_samples, len(image_files))):
        # Load the image using matplotlib.image
        img = mpimg.imread(os.path.join(dataset_path, image_files[i]))

        plt.subplot(int(num_samples/cols) + 1, cols, i + 1)
        plt.imshow(img)
        plt.axis('off')  # Turn off axis ticks and labels

    plt.show()

# Call the function to display the images
dataset_path = 'drive/MyDrive/stanford_cars/cars_test'
show_images(dataset_path)

This will load the train and test sets:
import os
import scipy.io as sio
from PIL import Image
from torch.utils.data import Dataset, DataLoader
from torchvision import transforms

IMG_SIZE = 64
BATCH_SIZE = 128

class StanfordCarsDataset(Dataset):
    def __init__(self, root_dir, annotations_file=None, transform=None, test=False):
        self.root_dir = root_dir
        self.transform = transform
        self.image_paths = [os.path.join(root_dir, filename) for filename in os.listdir(root_dir) if filename.endswith('.jpg')]

        if annotations_file:
            self.annotations = sio.loadmat(annotations_file)['annotations'][0]  # Load annotations
            if test:
                self.filename_to_label = {ann[4][0]: -1 for ann in self.annotations} #Assign -1 to all test images
            else:
                self.filename_to_label = {ann[5][0]: int(ann[4][0][0]) for ann in self.annotations}  # Create mapping
        else:
            self.filename_to_label = {}  # Empty dictionary if no annotations file is provided

    def __len__(self):
        return len(self.image_paths)

    def __getitem__(self, idx):
        image_path = self.image_paths[idx]
        image = Image.open(image_path).convert('RGB')  # Ensure RGB format

        # Get label if available
        filename = os.path.basename(image_path)
        label = self.filename_to_label.get(filename, -1)  # Use -1 as default label if not in the annotations

        if self.transform:
            image = self.transform(image)

        # Always return a label even if -1
        return image, label

def load_transformed_dataset():
    data_transforms = [
        transforms.Resize((IMG_SIZE, IMG_SIZE)),
        transforms.RandomHorizontalFlip(),
        transforms.ToTensor(), # Scales data into [0,1]
        transforms.Lambda(lambda t: (t * 2) - 1) # Scale between [-1, 1]
    ]
    data_transforms = transforms.Compose(data_transforms)

    train = StanfordCarsDataset(root_dir='drive/MyDrive/stanford_cars/cars_train',
                               annotations_file='drive/MyDrive/stanford_cars/devkit/cars_train_annos.mat',
                               transform=data_transforms, test=False)

    test = StanfordCarsDataset(root_dir='drive/MyDrive/stanford_cars/cars_test',
                               annotations_file='drive/MyDrive/stanford_cars/devkit/cars_test_annos.mat',
                               transform=data_transforms, test=True)

    return torch.utils.data.ConcatDataset([train, test])

data = load_transformed_dataset()
dataloader = DataLoader(data, batch_size=BATCH_SIZE, shuffle=True)


[Android] weex 0.26 c++ btoa、atob

The results of btoa and atob function transformation in weex C + + are different from those of other platforms, which leads to the failure of verification of some third-party platforms.

There is nothing I can do without a demo.
If this still bothers you and you find a solution, you could give us a PR if you can, I am very happy to talk with you implemenation detail or review you PR in mailing list.
I have a busy schedule and I can't read Github issue every day, but I check mailing list every day. I am sorry if this bothers you.


Fine-tuning takes a long time to save checkpoints

I'm running BERT_bataset on IMDB movie review dataset with 60000+ training reviews. When running on gpu (K80) it takes really a long time to save checkpoints (~2 hours and it is only half way so far ) while running on MRPC dataset (5000 pairs of texts) only takes 9 mins.
Is this slow speed anticipated?

@wayfarerjing I had the same problem, were you able to solve this issue?

@DragonAndSky  I had the same problem, were you able to solve this issue?

No I didn't manage to solve it. I think maybe it is expected.

maybe the time cost is not mainly from saving checkpoints. It may come from predicting and evaluating.

Similar situation encountered here. I have been running run_classifier on MRPC dataset, using codes provided in the readme, however it seems it takes longer than expected

Exactly, the similar situation. I thought its expected, and I never open the issue ticket.


Add support for Goldair 101cm Tower Fan

Based on discussion #853 I've updated it a little to make it more compatible. The off button still doesn't work but that's alright.
It's mostly based off the Goldair Platinum Tower Fan but a number of the id's were different as well as oscillate didn't work as string and the timer only worked as a number string.

Updated, thanks.


Remove the deprecated API usage problem

Apple have started to clamp down on the use of deprecated APIs. In AMScrollingNavBar/ScrollingNavbar+Sizes.swift there is reference to this deprecated control.
This fork and pull request fixes the issue.
(ITMS-90809: Deprecated API Usage - Apple will stop accepting submissions of apps that use UIWebView APIs)

Thanks. I was debating on this after #371 whether to leave the UIWebView reference under a compiler level #if of we should just kill it.
At any rate, it's probably best to adopt 5.4.0 as version number, since this can be breaking

Hi andreamazz,
Thanks for the reply.
Just to keep you up to date with proceedings, CI has passed and our continuous deployment at some point will place a binary with iTunes Connect. When this is verified and no warnings are received I will move this pr from draft and update the version number as you suggested.


Incompatibility with other Prettier plugins

https://github.com/tailwindlabs/prettier-plugin-tailwindcss/issues/31
Workaround: https://github.com/tailwindlabs/prettier-plugin-tailwindcss/issues/31#issuecomment-1195411734

Interesting, didn't know that a workaround actually exists.

It is not actually, or failed to understand how Prettier manages it ^^"
After few hours on it, I've just the feeling that we are fighting against Prettier will that do not want to do anything related to sort through it ^^"

Waiting for https://github.com/angular-eslint/angular-eslint/pull/1066, I went for a dirty solution 🙈
-> I run Prettier multiple times, one for each plugin 😅
It doesn't work in IDEs that runs Prettier with all plugins at the same time, so I'm relying on husky & lint-staged to run it automatically before committing (I was already using them to run Prettier, ESLint & other stuff).

package.json"scripts": {
  ...
  "prettier": "prettier . --ignore-unknown --write --plugin=prettier-plugin-organize-attributes && prettier . --ignore-unknown --write --plugin=prettier-plugin-tailwindcss",
  "prettier:check": "prettier . --ignore-unknown --check --plugin=prettier-plugin-organize-attributes && prettier . --ignore-unknown --check --plugin=prettier-plugin-tailwindcss",
},
"lint-staged": {
  "*": [
    "prettier --cache --ignore-unknown --write --plugin=prettier-plugin-organize-attributes",
    "prettier --cache --ignore-unknown --write --plugin=prettier-plugin-tailwindcss"
  ],
  "*.{ts,js,html}": "eslint --cache --fix"
},

and I've added this config to my .prettierrc{
  ....
  "plugins": ["prettier-plugin-tailwindcss"], // depends which one you prefer to run in your team's IDEs
  "pluginSearchDirs": ["./node_modules"], // seams mandatory, I added it here to not repeat it in each above commands
}

This issue has since been addressed by `prettier-plugin-tailwind.
You can refer to their README for configuration on how to get it working correctly:
https://github.com/tailwindlabs/prettier-plugin-tailwindcss#compatibility-with-other-prettier-plugins


Add onArrowClick event support

Use onArrowClick props to handle event.

Coverage decreased (-0.8%) to 97.704% when pulling 10b5ca18412595dd2c758fe8c26d9fdf21e3a1b5 on mavr1k:onArrowClick into 438c4f53b4f879ea5fb451bf539977ee4374aa2f on alexcurtis:master.


Fix trustline updates with transfer of "0"

If we are triyng to update a trustline and we pass a transfer value of "0"(string) the clientlib will call the overloaded updateTrustline function of the contract. This causes the meta transaction to fail as there is already an existing trustline and when updating we shouldn't be passing a transfer value.

I think this is wrong, you don't allow for strings that are over the number limit for javascript. I would say we need to use something like calcRaw and then compare with bigNumber(0) https://github.com/trustlines-protocol/clientlib/blob/8b30ce108a7e5ec6e90ff3359c2c248ee8a330d4/src/utils.ts#L170

yes, yes. You are right. That was what I thought on my way to work this morning... I'll have to figure something else.


Conference page information

@stanblum I'm trying to list here what information every conference page should contain. Example of such a page: http://localhost:9000/conferences/2008/

[ ] Summary: TDWG yyyy annual conference - Town, Country
[x] Cover image:  CC-BY image, good to recall the place 😄
[ ] Theme: @stanblum should we list the theme of the meeting? Not sure if this is relevant.
[ ] Description: @stanblum is it possible to have a short introduction paragraph for each meeting? Is this relevant?
[ ] Host: persons(s) and/or organizations organizing the conference, with links to websites
[ ] Venue: where conference took place, with link to website. Not necessarily same as host.
[ ] Date (@stanblum or dates?): Monday-Friday dates of the conference (excludes pre/post-conference activities)
[ ] Proceedings: link to BISS or single pdf
[ ] Programme: @stanblum separate link directly to have a single link to file server for programme and presentations?
[ ] Presentations: @stanblum separate link?
[x] Participants: decided to not include this. Participants generally only make consent to have this information be included in regonline/private email

@stanblum can you give your feedback on what should (not) be included in your opinion?


Firefox support

I actually use Firefox but I just spent a few hours attempting to make it work on Firefox without any success. MV3, Firefox not implementing things, CSPs, blocking content scripts, etc.


Script hangs indefinitely and fails to produce any video

I'm submitting a ...
[x] bug report

Summary

When running a basic script from the documentation, the program simply hangs indefinitely.  It creates a /test directory, but nothing else.  I'm likely missing something simple as this is my first time using puppeteer.  I apologize if so!  Here is my basic implementation:
import { PuppeteerScreenRecorder } from 'puppeteer-screen-recorder'
import { PassThrough } from 'stream'
import puppeteer from 'puppeteer'

const target = 'http://<IP_ADDRESS>:5500/test.html'
const savePath = './test/test.mp4'

const config = {
	followNewTab: false,
	fps: 25,
	videoFrame: {
		width: 1024,
		height: 768,
	},
	aspectRatio: '4:3',
	recordDurationLimit: 3,
}

const record = async () => {
	const browser = await puppeteer.launch()
	const page = await browser.newPage()
	await page.goto(target)

	const recorder = new PuppeteerScreenRecorder(page, config)
	await recorder.start(savePath)
	const pipeStream = new PassThrough()
	await recorder.startStream(pipeStream)

	await recorder.stop()
	await browser.close()
}

record()

I'm running the following:
node: v16.13.1
puppeteer-screen-recorder:  latest
os: latest MacOS

I just realized I was starting a stream, but that's not what I want to do.  The README had the steps as 1 and 2, (as opposed to a or b), and I misunderstood that as meaning both steps are required.  My mistake!

I did the exact same thing as you LOL
Should prob get that README to clarify a bit better lol


Monitor EVE Character Location

Poll the API, using the cache info to set the timer properly.
Information should be broadcasted to the websocket service


Error on missing consumer documents

Coverage decreased (-0.002%) to 90.934% when pulling ca5f0e61993f5009825907c92544b3eab8d3f295 on hsiliev:error_on_missing_consumer into c2ab2cdf940495d5d151503ff58a9959b3317e0f on cloudfoundry-incubator:master.


feat: Add transition effect to the Sidebar

Is your feature request related to a problem? Please describe.
I would like to add some transition effects to the sidebar. The sidebar doesn't have any transition effect when it slides from left to right, it just pops out suddenly.
Current Sidebar sliding from left to right (without transition)
https://user-images.githubusercontent.com/85433137/176629746-d0624367-48fd-47b5-96af-c9a9b8d86906.mp4
Describe the solution you'd like
I would like to add transition effects to the sidebar ( watch the below video for transition reference only)
https://user-images.githubusercontent.com/85433137/176632289-43ab651e-32a5-4d77-a5cf-a36faa6b9fd2.mp4
Are you working on this? (Yes/No)
yes

@adarrssh Open this issue in this repo

okay @vedant-jain03

I have open the this issue in different repo @vedant-jain03


issue with Payu money

Hi,
i am using loopj lib (android-async-http-1.4.2.jar) in my android project but after integrating with PayU Money sdk my project showing some conflicts because PayU Money also using loopj lib in their sdk('com.loopj.android:android-async-http:1.4.6').so i have tried to remove my loopj lib and used it from PayU sdk. everything is working well but there is one more issue the override method of version 1.4.2 has changed in 1.4.6 .
Problem: I want to use version 1.4.2 override method in 1.4.6 please suggest me any solution.
version 1.4.6 method
@Override
    public void onSuccess(int statusCode, Header[] headers, byte[] response) {
        // called when response HTTP status is "200 OK"
    }

    @Override
    public void onFailure(int statusCode, Header[] headers, byte[] errorResponse, Throwable e) {
        // called when response HTTP status is "4XX" (eg. 401, 403, 404)
    }

version 1.4.2 methods
                    @Override
                    public void onFinish() {
                        super.onFinish();

                    }

                    @Override
                    public void onSuccess(String s) {
                        super.onSuccess(s);
                 }

onFinish is not successor of onFailure method
Also you're overriding bad AsyncHttpResponseHandler, if you're receiving byte[] it's not TextAsyncHttpResponseHandler which returns Strings


Node cannot find module when deploying to Heroku

Thanks for the great module!
I am importing your module in my program using var mturkApi = require('mturk-api') and it all works find on my local machine. When I deploy my app to heroku, npm throws an error 'Error: cannot find module 'mturk-api'
Any idea what is going on here?
Thanks!

So i have a work around. For some reason your module does not get commited to git correctly and hence does not get deployed to heroku correctly. Is there something strange with your npmignore? Here is what I used for reference:
http://stackoverflow.com/questions/23987571/node-js-app-works-locally-but-heroku-says-missing-module


Extra Credit : Add in gravitar support step 1

Did this in some free time, we don't have to merge, but kind of fun.

:+1:


能不能增加个 题目中英文显示啊 。

🚀 Feature Proposal
A clear and concise description of what the feature is.
Motivation
Please outline the motivation for the proposal.
Contribution
Please describe the solution if you'd like to submit a PR.

+1

+1

+1

+1

fixed by #690


Design: Change our current monospace font choice to a Google Fonts supported monospace font

We are currently using "Menlo" as our recommended monospace font, which Google Fonts doesn't support. We use Google Fonts for our other 2 fonts (Lato & Noto sans). Let's replace "Menlo" with a font that Google Font supports to have all 3 fonts coming from the same place.

Decision record: Monospace font


N3 Regularizer

To make regularizer modularized and replaceable in our implementations.
The details are mentioned in this paper:
https://arxiv.org/pdf/1806.07297.pdf

N3 regularizer added to complex model. ComplexN3.


Swift3

I made a swift3 fork & branch. If you make a swift3 branch I can submit a pull request.

Done. Thanks!

I have added this library in my exisiting swift 3 project using cocoapods as pod 'libPhoneNumber-iOS'. 1) Now the problem is I can't access NBTextField class. 2) As shown in the example for Swift Demo I can't import libPhoneNumberiOS in swift.

Can you give us more details on how to repro? Step by step would be great.
On Wed, Jun 21, 2017 at 5:47 AM, gmansata6290<EMAIL_ADDRESS>wrote:

I have added this library in my exisiting swift 3 project using cocoapods
as pod 'libPhoneNumber-iOS'. 1) Now the problem is I can't access
NBTextField class. 2) As shown in the example for Swift Demo I can't import
libPhoneNumberiOS in swift.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/iziz/libPhoneNumber-iOS/issues/146#issuecomment-310067481,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AATiycVGEE8MRV5WuIYkvAExhlhxu5yIks5sGRDKgaJpZM4KAQxP
.


Support for lambda integration type in addition to lambda-proxy?

Hi, the readme clearly states that only lambda-proxy integration is supported. However, async execution seems to require using the lambda integration type. Would extending to support that be within scope of this project? I could look into implementing at least basic support if so.
It would be a somewhat limited subset of the functionality, probably. For my needs responses don't even make sense, although in general they do...

I'm not really sure about how WSGI fits into async execution? Could you explain your use case?
A couple of alternatives to consider:

Since you are not going to respond to the HTTP request, maybe you don't even need WSGI. You could just have a plain Python handler and have it process the raw Lambda event.
Transform your event into something that resembles the event structure for lambda-proxy and pass it to the WSGI handler yourself.

The use case is that a couple of end points in a set of backend apis ran into lambda's timeout limits, so they had to be made async. There is still a response of sorts even with async apis, the difference is that it is handled by api gateway (ok/retry/dlq) and the client always sees an immediate 202 response.
I am currently parsing the raw event in application code, but the annoying thing is that it requires making it a separate lambda function due to the different handler function. So split logs, monitoring, etc. It also bypasses the normal routing and parameter logic, making for very different logic than normal apis.
Transforming and calling the WSGI handler would still allow using all the normal routing/parsing functionality, though. Actually, yes, I could add a shim that handles all requests, transforming them based on the integration type before passing it on to wsgi_handler.handler. So, yeah, that's the way I'll go if you don't think that would be a useful fit inside serverless-wsgi.
Thanks

Thanks for the explanation. The main obstacle that I see is that the Lambda integration is not bound to follow any conventions in the event schema. So you'd essentially have to write VTL that transforms the event into something that's equivalent to the Lambda proxy integration and then no changes would be needed in serverless-wsgi anyway. You'd just have to use the right VTL in order to make it work, and we could add that to the README.
Or do you see any specific changes that you would need in serverless-wsgi to make it work?

Hmm... I wasn't going to do anything so fancy. Just define the parameters in serverless.yml, e.g.
          path: /async/{bar}
          method: any
          async: true
          request:
            querystrings:
              foo: true
            paths:
              bar: true

(application/json gets automatic passthrough for the body) and then handle the incoming event format in code: https://www.serverless.com/framework/docs/providers/aws/events/apigateway/#example-lambda-event-before-customization

Right, I wasn't aware that the LAMBDA event was so complete before any VTL transformations. It's been a while since I used it last.
I think it makes sense to support this. Ideally, we could identify whether the incoming request is a LAMBDA or LAMBDA-PROXY event and handle it accordingly. Not sure if it's feasible, but I would prefer it to be as automatic as possible rather than requiring additional configuration.


fix(plugin-search-react): improve SearchPagination page limit change handling

Hey, I just made a Pull Request!
Currently the SearchPagination component:

does not reset the page cursor when page limit changes.
This can cause some weird situations, for example:

User clicks 4 times on 'next page' with page limit 10
user now sees search result 40-50
now the user switches page limit to 100
he now sees search results 400-500  => this is way past what results the user went through

This PR fixes this behavior by resetting the page cursor when the page limit is changed.
Also, this PR fixes typescript typings by replacing the inexistent props omission onPageLimitChange prop with the correct onLimitChange.
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Hi @gtestault, thanks for the fix! 🎉


Vanilla Attribute Error

Problem description
I have been trying to use your package to make risk parity portfolios with ease. Although, I have been facing some issues running the first tutorial. At first I've tried running it with a local installation, then I've moved to Colab environment. Faced the same issue on both situations.
Example
!pip check
!pip install pybind11
!pip install riskparityportfolio

import riskparityportfolio as rp

b = df_portfolio_prices_parity

optimum_weights = rp.vanilla.design(cov, b)

Behavior
Since it was a simple example provided on the documentation, I thought it would be straight-forward execution, but I'm facing the error below:
AttributeError                            Traceback (most recent call last)
<ipython-input-12-0745d4c9a058> in <module>()
      8 b = df_portfolio_prices_parity
      9
---> 10 optimum_weights = rp.vanilla.design(cov, b)

AttributeError: module 'riskparityportfolio' has no attribute 'vanilla'

Environment:

Colab environment: running Ubuntu 18.04.3 LTS
installation method: pip

Hi @ralphscoz: thanks for reporting this.
Could you try installing the dev version as follows:
$ git clone https://github.com/dppalomar/riskparity.py.git
$ cd riskparity.py
$ python setup.py install

Let me know if you face any other issue.

Hi @mirca, I installed the dev version as you say above, but still get the error reported here:
AttributeError: module 'riskparityportfolio' has no attribute 'vanilla'
Love the work that you and Daniel Palomar are doing with risk parity by the way, I appreciate it, so thanks!

Hi @DanielPNewman, could you show the version of riskparityportfolio in the output of
$ pip list?
Thanks!

Hi @mirca, yes it's: riskparityportfolio  0.1.2

@DanielPNewman thanks! I can't seem to be able to reproduce the issue right now, but I will find some time to investigate it soon!

@DanielPNewman @ralphscoz in the meantime
from riskparityportfolio import vanilla

should work!

@DanielPNewman @ralphscoz I was able to reproduce the issue. Thanks again for reporting!
It should be solved via
$ git clone https://github.com/dppalomar/riskparity.py.git
$ cd riskparity.py
$ pip install -e .

Let me know! :)

Hey guys! Thank you so much for your help! It actually worked.

Nice one @mirca, this works for me too now, thanks :)

Thank you for reporting this issue @DanielPNewman @ralphscoz!


Updated index.md with numeration, emphasis and grammatical corrections.

[x ] I have read freeCodeCamp's contribution guidelines.
[x ] My pull request has a descriptive title (not a vague title like Update index.md)
[x ] My pull request targets the master branch of freeCodeCamp.
[x ] None of my changes are plagiarized from another source without proper attribution.
[x ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@PJurc Thank you for  creating this PR.  However, since it was created, the underlying document has changed.  Can you please review and resolve the current merge conflicts?  It could be the changes to the underlying document are so significant that your changes are no longer relevant.  If the latter is the case, it might be easier to just close this PR and create a new PR with any changes you still feel are important to make.
If you need any assistance or have questions about resolving the merge conflicts, please reply back or contact someone in the Contributors Room on Gitter.
Thank you.

Hi @PJurc
As there has been no response from your end for a while, we are closing this PR.
Feel free to request this PR to be reopened or create a new PR, if you still wish to make the changes you originally added plus any additional change requests asked of you.  Also, remember to update your fork, so you have the latest version of master in case it has changed significantly.
Happy Coding!