document API resources

Create an API document identifying all the currently available endpoints and the elements within each endpoint.

@sonalikatara Can I help you with this ?

@thesparrow please coordinate with @tanyagupta she has started on this however there is more to do if you would like to help

@thesparrow @sonalikatara we will be implementing apidocs to capture documentation. I plan to update the issue description with a detailed task list soon. Look forward to working with both of you on that

Thanks for the reply - I can do the first bulletin - it seems like the rest of the bulletins are tied to the second stage? Or is that a wrong assumption? @motosharpley  @tanyagupta  Also I'm not sure - do I need to tag you in the posts - or is this seen by people already making comments on the thread? thanks

@thesparrow we would need an admin for the first if I am not mistaken. Let me get the guidelines out as soon as I can (the second one) and that should free up the rest of the bullets.  All subscribed folks will automatically get copied on this thread. It looks like @motosharpley @sonalikatara @jkwening and us :)

Ok! Sounds good! I'll be scoping out the code in the meantime - let me know.

We can use this as a master ticket and reference other smaller issues that need more description and are able to be completed in isolation.
I will have to to look at  apidocs again but I would assume issue 1 would just be a matter of adding devDependencies to the package.json
Also since multiple people are working on this lets submit PR's to the api-docs feature branch

Thanks Bryan. Will push further PRs to the api-docs branch feature.
Sonali and Anna please look at docs folder document name Api_instructions in the api-docs branch.
That should help us tackle the rest of the sub issues under this issue. Please post a comment if there are questions.
Sent from my iPhone

On Mar 30, 2018, at 3:55 PM, Bryan<EMAIL_ADDRESS>wrote:
We can use this as a master ticket and reference other smaller issues that need more description and are able to be completed in isolation.
I will have to to look at apidocs again but I would assume issue 1 would just be a matter of adding devDependencies to the package.json
Also since multiple people are working on this lets submit PR's to the api-docs feature branch
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@thesparrow and @sonalikatara wanted to check in and see if you saw the instructions and have any questions. I am posting the link  here =>
https://github.com/TheDevPath/Navi/blob/api-docs/docs/API_instructions.md
Essentially api-docs helps the automation of documents and the attached describes the kind of changes that need to be made to the files. The list of the files are in the task list above.
I will work on it further but the essentials of what needs to be done are there. We won't be opening new issues so you can pick any one and post a comment so we all know
Please let me know if you have any questions.
Thanks  :)

Thank You @tanyagupta I am setting up the Navi project on my local machine
right now. Will get back to you if I have any questions,  will c\post a
comment as soon as I get started.
On Sat, Mar 31, 2018 at 3:41 PM, tanyagupta<EMAIL_ADDRESS>wrote:

@thesparrow https://github.com/thesparrow and @sonalikatara
https://github.com/sonalikatara wanted to check in and see if you saw
the instructions and have any questions. I am posting the link here =>
https://github.com/TheDevPath/Navi/blob/api-docs/docs/API_instructions.md
Essentially api-docs helps the automation of documents and the attached
describes the kind of changes that need to be made to the files. The list
of the files are in the task list above.
I will work on it further but the essentials of what needs to be done are
there. We won't be opening new issues so you can pick any one and post a
comment so we all know
Please let me know if you have any questions.
Thanks :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/TheDevPath/Navi/issues/123#issuecomment-377728551,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD-IV0_q2IR_Ne1O7pw1wcJSw2AjTqNHks5tkAX9gaJpZM4SJaIA
.

@tanyagupta , the api documentation is already there in all the controllers, do I need to check it or am i missing something.
regarding the item : Update contributing guidelines doc to ensure all programmers follow the guidelines before introducing new API code
Isn't this https://github.com/TheDevPath/Navi/blob/api-docs/docs/API_instructions.md
Please suggest how I can start .

@sonalikatara those are really good questions. Let me update my post so that those answers are there for others to review as well.


add treatment at the end of every treatment classes except the regimen ones

not sure what to do with the regimen classes

Should the regimen classes be changed to treatment?
If not (at least for now) I think that the PR can be checked and merged
@cmungall @austinmeier @cooperl09

Yes, if we are keeping this branch as treatments (which I think is more appropriate) and not exposures.  Most of them were changed already in the past, for example #52, #73, #76

Agreed.  There is no discernable difference between "treatment" and "regimen"


context_length_exceeded when generating title

Error generating title!
{
  "error": {
    "message": "This model's maximum context length is 4097 tokens. However, your messages resulted in 7403 tokens. Please reduce the length of the messages.",
    "type": "invalid_request_error",
    "param": "messages",
    "code": "context_length_exceeded"
  }
}

Either use the 16k model to generate the title, or just truncate the input (which should be good enough for generating a title)

I am encountering the same error.

I'm getting the same error but it looks like the max_tokens data isn't even sent to the API

Is this the expected behavior? I don't see any changes when I edit the max_tokens setting.

I'm getting the same error but it looks like the max_tokens data isn't even sent to the API

Is this the expected behavior? I don't see any changes when I edit the max_tokens setting.

Max tokens is a property of each model, but isn't published through the API. I've asked them to add that

I'm getting the same error but it looks like the max_tokens data isn't even sent to the API

Is this the expected behavior? I don't see any changes when I edit the max_tokens setting.

Max tokens is a property of each model, but isn't published through the API. I've asked them to add that openai/openai-python#448

I'm confused. It's already implemented in the api: https://platform.openai.com/docs/api-reference/chat/create#chat/create-max_tokens
I could copy the request from the browser inspect network tab (in curl format), set the max_tokens and run it in the cli terminal. Looks like it's working. I must be missing something...

It is a bit confusing indeed but the max_tokens parameter is never sent to begin with. It should be calculated and sent with each request like context_length - content-tokens (for lack of better wording) = max_tokens
As I said it should probably be 1% or 2% less than that to avoid errors (I tried with a precise number and it gave me errors anyway)

I get this every time, it's frustrating

This is fixed in my fork. unfortunately, I fixed it after changing a lot more stuff to do with model context and max tokens (and detaching fork from parent), so I can't easily make a diff. Feel free to try to steal my implementation.


How to save log to log file in production mode?

Since dflogger is based on pandas dataframe, you can save to any format that is supported by pandas.  In their documentation, I don't see a log file supported since it's not practical to save a table in a log file. To be clear, dflogger is meant for logging or tracking machine learning experiments. You can track the hyperparameter used and the metric score. Hope this helps


Support SQL-Style Joins between Xarray datasets and Dask/Pandas dataframes

Here's an example workflow that I'd like to support once this feature exists. This is from Jake Wall of the Mara Elephant Project. Here, he would make use of raster and table data from Earth Engine.

Yeah, so one example, is to extract a NDVI value from an IC for every GPS point recorded by an elephant. We have millions of points that get translated into features. Then a reduce operation is run on the point to get the closest n values in time to when the GPS point occurred. We then spit this back out as an array and join it with the original geopandas dataframe.

I'm imagining this would look like a left join from a Dask Dataframe that had the elephant coordinates to an EE ImageCollection that was opened with Xee via Qarray. Some details are fuzzy, like how we'd interject a NN lookup (maybe, this could be done via a SQL aggregation?).
In general, I think there is broad demand for being able to join raster and tabular data with each other. Later in the line, I bet we could implement geo-aware joins that would make use of geometry.

I’ve been reading more into how this is done in the status quo. The best example I can find for joining rasters and point data (and vectors) comes from using a hierarchical spatial index like h3 or s2.
https://github.com/uber/h3-py-notebooks/blob/master/notebooks/unified_data_layers.ipynb
I wonder if this is the technique that underpins Fused.io.

For non-geospatial data, could we use a kdtree to create a hierarchical index? 🤔

This podcast episode is incredibly validating of the use case that this library (and issue) solves.
https://overcast.fm/+AAU1XJb7r0Y/6:55

https://github.com/DahnJ/H3-Pandas
This gives me more confidence that an index system (geospatial via s2 and h3, or pre-computed via kdtrees) is a good integration. To me, this is proof of demand for such features.


FE-238 - auto-login support on core web UI

Scope & Purpose
This adds measures to handle auto-login support on the web UI:

Logout button is hidden is auto-login via ArangoGraph is enabled
We were using jwtUser set in sessionStorage during login. Since login is now skipped, we have switched to using /whoAmI response to add that value

[x] :pizza: New feature

Checklist

[x] Tests

[x] Manually tested

[x] :book: CHANGELOG entry made

Related Information
(Please reference tickets / specification / other PRs etc)

[x] GitHub issue / Jira ticket: https://arangodb.atlassian.net/browse/FE-238

Moving back to draft as there might be some messaging changes

@ansoboleva @palashkaria
What will happen if there is a non-AG deployment with this header being set but not JWT token is provided?
What will happen to a a non-AG deployment with this header being set but no authentication enabled?

@KVS85

If this header is set, and you are logged in, you will see this:

If the header is set, and you are not logged in, you will be asked to log in.

This header is not dealing with authentication, it is only used to show/hide the logout button. The authentication (& setting of this header) is handled by the auth middleware on the AG side.

[ ] https://jenkins.arangodb.biz/job/arangodb-ANY-jslint/28594/


"voice-synthesis" tag

Why is our project tag with "voice-synthesis" when we don't actually synthesize any voice? We just analyze it. I think it should be changed. Also I don't know how to do it. Pls someone help.

According to https://www.merriam-webster.com/dictionary/synthesis, synthesis means deductive reasoning. I think that is what we are working on. Based on the data read from the audio files, we analyse them and deduce the gender of the author of the voice.

I'm not sure you can change it. Me as an owner has this additional button (top right)

Tag don't fit the subject of this repo.


QSem vs TSem

We currently have QSem, QSemN, and TSem. I'd like to profile these types and (hopefully) abandon QSem(N) in favor of TSem if the performance is close enough.


Allow specifying overlay positions

(see also other issue about configuration)
The user should be able to specify the overlay sizes and position either by command line or config file. It should be possible to specify the overlays as a percent which allows for different sized input video.

A config file feature was added that allows specification of overlay sizes and positions. It does not use percent but this is satisfactory resolution.


How to save as a Folder using Tabular Editor Command Line

When running the following shell command only one file is generated (database.json) which looks like the .bim file. It doesn't create the whole folder structure. Any advice?
& "$tabularEditorPath" "$bimFilePath" -F "$folderPath"

I have Tabular Editor 2.25.0

Hi @tiagotfsilva
The issue is that the bim file does not contain the specification on how the model should be serialized. This specification is stored as an annotation on the model. The easiest option is to load the model once in the TE UI, then go to File > Preferences > Current Model and set the checkmarks according to the depth of serialization you would like to have:

After clicking "OK", you should see the following annotation on the model:

If you then save the .bim with this annotation, then subsequently running the CLI with the -F switch should give you the folder structure you want.
Alternatively, you can use a C# script as part of the CLI execution to specify the same annotation. This way, you don't have to open the model in the TE UI. Here is an example on how to do this.


XCode Project generated by Flutter

Steps to Reproduce

From VSCode use the Flutter: New Project command.
Enter myapp for the project name, let Flutter build the project files
Use XCode 10 to open the project
Press CMD+B to build the project - (Update, turns out this step is unnecessary. The warning is present the first time the workspace is opened in XCode 10.)
The following warning is generated:

Please update the generated project settings to conform with the recommended settings.
While this would be a convenience, the validator fixes the problem, its annoying to have to update so many settings that just work if I create a new project with XCode. This kind of experience is not going to help with adoption. The experience needs to be as smooth and reliable as the behavior provided by XCode.
[✓] Flutter (Channel stable, v1.0.0, on Mac OS X 10.14.2 18C54, locale en-US)
    • Flutter version 1.0.0 at /Users/seamus_mcgowan/Flutter
    • Framework revision 5391447fae (5 weeks ago), 2018-11-29 19:41:26 -0800
    • Engine revision 7375a0f414
    • Dart version 2.1.0 (build 2.1.0-dev.9.4 f9ebf21297)

[✓] Android toolchain - develop for Android devices (Android SDK 28.0.3)
    • Android SDK at /Users/seamus_mcgowan/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 10.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.1, Build version 10B61
    • ios-deploy 1.9.4
    • CocoaPods version 1.5.3

[✓] Android Studio (version 3.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 31.3.1
    • Dart plugin version 181.5656
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)

[✓] VS Code (version 1.30.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 2.21.1

[✓] Connected device (1 available)
    • Seamus' iPhone • deb505af77f116bc6e4c38f89cbe5f3e1779bf58 • ios • iOS 12.1.2

• No issues found!

Please add the output of flutter doctor -v.

I'm getting this warning as well, and all builds fails unless I apply the recommended settings.


Calling Remove-Module from an Import-Module -Scope local scope doesn't remove imports from ancestral scopes

[Obsoleted by #9582.]
Based on the discussion in https://github.com/PowerShell/PowerShell/issues/5503, the assumption is that Remove-Module operates at the session-state level, which implies that calling it from any scope should unload the module and remove its imports from all scopes in the session.
However, it seems that if a module is imported both in a given scope and then also locally in a child scope, calling Remove-Module from that child scope doesn't remove the imports from the calling scope. It does appear to unload the module, however.
Steps to reproduce
'function f1{"[f1]"} '> t1.psm1  # create sample module with 1 export: function "f1"

Import-Module ./t1.psm1  # import it into the current scope domain's root scope

"[$((Get-Module t1).Name)]"  # verify that Get-Module sees it.

# Also import the module *locally* into a *child* scope, and call
# Remove-Module from the same scope.
& { Import-Module -Scope Local ./t1.psm1; Remove-Module t1 }

# Call the exported function - if Remove-Module operates at the *session-state* level,
# the function should no longer exist.
f1

# Test if Get-Module still sees the module, which it shouldn't after Remove-Module.
"[$((gmo t1).Name)]"

Expected behavior
[t1]
f1 : The term 'f1' is not recognized as the name of a cmdlet, function, script file, or operable program.
...
[]

Actual behavior
[t1]
[f1]
[]

unexpected: the f1 function was not removed from the parent scope and still works.

expected: Get-Module no longer sees the module.

This suggest that while the module may have been unloaded, its imports weren't removed from the ancestral scopes.
Note that if you remove -Scope Local from the Import-Module call, things work as expected.
By contrast, adding -Scope Local to the outer scope's Import-Module call makes no difference.
Environment data
PowerShell Core v6.1.0-preview.3 on macOS 10.13.6
PowerShell Core v6.1.0-preview.3 on Ubuntu 16.04.4 LTS
PowerShell Core v6.1.0-preview.3 on Microsoft Windows 10 Pro (64-bit; Version 1803, OS Build: 17134.165)
\Windows PowerShell v5.1.17134.165 on Microsoft Windows 10 Pro (64-bit; Version 1803, OS Build: 17134.165)

See  #9582 for a reframing of this issue.


fix: sync language files

Description
SYnc language files
Linked Issues/Tasks
Type of change
Refactoring
Tests
No test

@pwltr Should I remove German language again?

@pwltr Should I remove German language again?

yes please, I need to review/edit them still


problem with mirrors getField

i dont know to what extend mirrors should work, but this little sample produces the following error:
Error compiling to JavaScript:
MemcacheError(status: Status(ERROR), message: Error storing item)
import "dart:mirrors";
class Address {
String zip;
String city;
}
class Order{
Address sender;
Address receiver;
}
void main() {
Order order = new Order()
..sender = (new Address()..zip="1160"..city="Wien")
..receiver = (new Address()..zip="7163"..city="Andau");
InstanceMirror im = reflect(order);
// this works
//var sender = im.reflectee.sender;
String s = "sender";
// getField produces error
var sender = im.getField(#sender).reflectee;
// does produce the same error
//var sender = im.getField(new Symbol("sender").reflectee;
//var sender = im.getField(new Symbol(s)).reflectee;
// this works
var receiver = im.reflectee.receiver;
print("sender: ${sender.zip}, receiver: ${receiver.zip}");
}

This looks like a temporary problem with a component of the server. I'll add in error protection. Please try again - sorry about that

Moving this issue to https://github.com/dart-lang/dart-services/issues/190. Thanks for the report!


Cmd error

H:\Download\MCEdit-Unified-master>python mcedit.py
File "mcedit.py", line 69
print '[ ****** ] ~~~~~~~~~~ %s' % start_msg
^
SyntaxError: Missing parentheses in call to 'print'. Did you mean print('[ ****** ] ~~~~~~~~~~ %s' % start_msg)?
H:\Download\MCEdit-Unified-master>

What version of python do you have installed? It seems like you've installed a version of Python 3 instead of Python 2.7

Yeah，Python3 I had used.Do it needs python2.7?

Now I use python 2.7.

but it still happened

Please look through the readme.md for the project. There are a number of modules you need to install first.

thanks


33 Build Errors when adding latest package for Xamarin.MobileAds

When adding latest packages into a brand new project currently getting 33 build errors.

can you post the build errors?

I can indeed please see below, the below is from a brand new project pulling down the following packages.
Xamarin.Google.iOS.mobileAds SDK - 7.57.0
Xamarin.Firebase.iOS.Core - 6.6.6
/Users/name/Projects/Test/iOS/MTOUCH: Error MT5210: Native linking failed, undefined symbol: _GULIsLoggableLevel. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. (MT5210) (Test.iOS)
/Users/name/Projects/Test/iOS/MTOUCH: Error MT5210: Native linking failed, undefined symbol: _GULLogBasic. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. (MT5210) (Test.iOS)
/Users/name/Projects/Test/iOS/MTOUCH: Error MT5210: Native linking failed, undefined symbol: _GULLogError. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. (MT5210) (Test.iOS)
/Users/name/Projects/Test/iOS/MTOUCH: Error MT5210: Native linking failed, undefined symbol: _GULLogInfo. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. (MT5210) (Test.iOS)
/Users/name/Projects/Test/iOS/MTOUCH: Error MT5210: Native linking failed, undefined symbol: _GULLogWarning. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. (MT5210) (Test.iOS)
/Users/name/Projects/Test/iOS/MTOUCH: Error MT5210: Native linking failed, undefined symbol: _GULSetLoggerLevel. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. (MT5210) (Test.iOS)
/Users/name/Projects/Test/iOS/MTOUCH: Error MT5211: Native linking failed, undefined Objective-C class: GULAppDelegateSwizzler. The symbol 'OBJC_CLASS$_GULAppDelegateSwizzler' could not be found in any of the libraries or frameworks linked with your application. (MT5211) (Test.iOS)
/Users/name/Projects/Test/iOS/MTOUCH: Error MT5211: Native linking failed, undefined Objective-C class: GULAppEnvironmentUtil. The symbol 'OBJC_CLASS$_GULAppEnvironmentUtil' could not be found in any of the libraries or frameworks linked with your application. (MT5211) (Test.iOS)
/Users/name/Projects/Test/iOS/MTOUCH: Error MT5211: Native linking failed, undefined Objective-C class: GULMutableDictionary. The symbol 'OBJC_CLASS$_GULMutableDictionary' could not be found in any of the libraries or frameworks linked with your application. (MT5211) (Test.iOS)
/Users/name/Projects/Test/iOS/MTOUCH: Error MT5211: Native linking failed, undefined Objective-C class: GULNetwork. The symbol 'OBJC_CLASS$_GULNetwork' could not be found in any of the libraries or frameworks linked with your application. (MT5211) (Test.iOS)
/Users/name/Projects/Test/iOS/MTOUCH: Error MT5211: Native linking failed, undefined Objective-C class: GULSwizzler. The symbol 'OBJC_CLASS$_GULSwizzler' could not be found in any of the libraries or frameworks linked with your application. (MT5211) (Test.iOS)
/Users/name/Projects/Test/iOS/MTOUCH: Error MT5210: Native linking failed, undefined symbol: _kGULNetworkHTTPStatusCodeCannotAcceptTraffic. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. (MT5210) (Test.iOS)
/Users/name/Projects/Test/iOS/MTOUCH: Error MT5210: Native linking failed, undefined symbol: _kGULNetworkHTTPStatusCodeNotFound. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. (MT5210) (Test.iOS)
/Users/name/Projects/Test/iOS/MTOUCH: Error MT5210: Native linking failed, undefined symbol: _kGULNetworkHTTPStatusCodeNotModified. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. (MT5210) (Test.iOS)
/Users/name/Projects/Test/iOS/MTOUCH: Error MT5210: Native linking failed, undefined symbol: _kGULNetworkHTTPStatusCodeUnavailable. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. (MT5210) (Test.iOS)
/Users/name/Projects/Test/iOS/MTOUCH: Error MT5210: Native linking failed, undefined symbol: _kGULNetworkHTTPStatusNoContent. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. (MT5210) (Test.iOS)
/Users/name/Projects/Test/iOS/MTOUCH: Error MT5210: Native linking failed, undefined symbol: _kGULNetworkHTTPStatusOK. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. (MT5210) (Test.iOS)
/Users/name/Projects/Test/iOS/MTOUCH: Error MT5210: Native linking failed, undefined symbol: _pb_decode. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. (MT5210) (Test.iOS)
/Users/name/Projects/Test/iOS/MTOUCH: Error MT5210: Native linking failed, undefined symbol: _pb_decode_varint. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. (MT5210) (Test.iOS)
/Users/name/Projects/Test/iOS/MTOUCH: Error MT5210: Native linking failed, undefined symbol: _pb_encode. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. (MT5210) (Test.iOS)
/Users/name/Projects/Test/iOS/MTOUCH: Error MT5210: Native linking failed, undefined symbol: _pb_encode_string. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. (MT5210) (Test.iOS)
/Users/name/Projects/Test/iOS/MTOUCH: Error MT5210: Native linking failed, undefined symbol: _pb_encode_submessage. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. (MT5210) (Test.iOS)
/Users/name/Projects/Test/iOS/MTOUCH: Error MT5210: Native linking failed, undefined symbol: _pb_encode_tag_for_field. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. (MT5210) (Test.iOS)
/Users/name/Projects/Test/iOS/MTOUCH: Error MT5210: Native linking failed, undefined symbol: _pb_encode_varint. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. (MT5210) (Test.iOS)
/Users/name/Projects/Test/iOS/MTOUCH: Error MT5210: Native linking failed, undefined symbol: _pb_istream_from_buffer. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. (MT5210) (Test.iOS)
/Users/name/Projects/Test/iOS/MTOUCH: Error MT5210: Native linking failed, undefined symbol: _pb_ostream_from_buffer. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. (MT5210) (Test.iOS)
/Users/name/Projects/Test/iOS/MTOUCH: Error MT5210: Native linking failed, undefined symbol: _pb_read. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. (MT5210) (Test.iOS)
/Users/name/Projects/Test/iOS/MTOUCH: Error MT5201: Native linking failed. Please review the build log and the user flags provided to gcc: -ObjC -lc++ -lsqlite3 -lz -ObjC -lz -lsqlite3 (MT5201) (Test.iOS)
/Users/name/Projects/Test/iOS/-[APMMeasurement networkUploadCompletionHandlerWithResponse: Error: ] in GoogleAppMeasurement(APMMeasurement_87bdad44f2b9aa68c2d607a36be1b8c5.o) (Test.iOS)
/Users/name/Projects/Test/iOS/-[APMMeasurement networkUploadCompletionHandlerWithResponse: Error: ] in GoogleAppMeasurement(APMMeasurement_87bdad44f2b9aa68c2d607a36be1b8c5.o) (Test.iOS)
/Users/name/Projects/Test/iOS/-[APMMeasurement networkUploadCompletionHandlerWithResponse: Error: ] in GoogleAppMeasurement(APMMeasurement_87bdad44f2b9aa68c2d607a36be1b8c5.o) (Test.iOS)
/Users/name/Projects/Test/iOS/-[APMMeasurement networkUploadCompletionHandlerWithResponse: Error: ] in GoogleAppMeasurement(APMMeasurement_87bdad44f2b9aa68c2d607a36be1b8c5.o) (Test.iOS)
/Users/name/Projects/Test/iOS/clang: Error: linker command failed with exit code 1 (use -v to see invocation) (Test.iOS)

I just hit this on a new project also. Once I added code that referenced the code it linked but then on second build I get the same as this  : https://github.com/xamarin/GoogleApisForiOSComponents/issues/412
Without cleaning everything everytime it does not run.
As noted down grading xamarin.ios framework to <IP_ADDRESS> and it all works again.

it looks similar to the errors I get as well:
https://github.com/xamarin/GoogleApisForiOSComponents/issues/421
I will try downgrading to <IP_ADDRESS>

Ugh I see links for downgrading visual studio enterprise but not community.  Do I need to contact microsoft for that or something?

On Mac go to /Library/Frameworks and change the shortcut called current to point to the older folder and delete the newer one.
Restart VS Mac and it links against older one

for info I tracked my problems down to this
https://github.com/xamarin/GoogleApisForiOSComponents/issues/423

I found the libraries for my mac but do I all my dev on a PC that links to it.  I have to downgrade that version of Visual Studio before it will work

Is there an update on this? Is it a problem with the nuget package or dependencies? Can I resolve it without downgrading? I'm having the same problem with Xamarin.iOS.Places

doesnt seem like anyone is maintaining this repo :(

Hey All,
Not sure anyone is maintaining this repo which is sad, however it seems i'm only getting this issue on simulator builds.
I can get this to work with the latest version of admob on device however on simulator it just doesn't build.

Facing the exact same issue with analytics and crashlytics.

I'm trying to follow the instruction in hope that I can apply some fixes myself but dotnet cake --target=externals failed:
Error: One or more errors occurred. (Could not reach target 'externals' since it was skipped due to a criteria.)
And the externals folder is empty. @RobertWildgoose @StoatsOnAPlane have you successfully build this repo locally?

I'm trying to follow the instruction in hope that I can apply some fixes myself but dotnet cake --target=externals failed:
Error: One or more errors occurred. (Could not reach target 'externals' since it was skipped due to a criteria.)
And the externals folder is empty. @RobertWildgoose @StoatsOnAPlane have you successfully build this repo locally?

Same happened to me. have you resolved the issue @motoko89 ?


Add assembly instruction for hashing long sequences of values

Current hash instructions allow hashing between 1 and 4 field elements. Hashing of more than 4 elements is possible but requires the user to manually calculate the number of hash instructions needed. Ideally, we should have a single digest.n instruction which can be used to hash arbitrarily many elements.

Do we need to make an upper limit for the n number?

I don't think it matters too much (if the user wants to hash GBs of data they should be able to) - but I think we can put a limit on n to make sure it fits in a 32 bit integer.


ClimateBench dataset

Dataset Name
ClimateBench
Dataset URL
https://zenodo.org/record/7064308
Description
I propose to create a pipeline so that more climate models and variables, at a higher temporal resolution can be easily ingested into ClimateBench transparently and efficiently. These consist of post-processed and harmonized CMIP6 input and output files split across experiments/scenarios. This would allow others to expand upon the ClimateBench protocol and apply climate model emulation more generally.
Size
Roughly 10Gb files totaling around 1Tb (depending on storage availability)
License
Unknown
Data Format
NetCDF
Data Format (other)
No response
Access protocol
HTTP(S)
Source File Organization
The CMIP6 data is organized in ESGF into time sharded files per experiment, per model, per variable. I'm not sure how they're stored in Pangeo, which might be a more natural source.
Example URLs
No response
Authorization
No; data are fully public
Transformation / Processing
The data needs to be put onto a common grid, the piControl subtracted, and units harmonized. Some common statistics may be used for some variables (e.g. 99th percentile of precipitation).
Target Format
Zarr
Comments
Original Pangeo-Forge recipe: https://github.com/pangeo-forge/staged-recipes/issues/134
Pull request regarding processing daily data with pangeo-forge-esgf: https://github.com/jbusecke/pangeo-forge-esgf/pull/9
It might make sense to create this recipe as just a 'pointer' to the underlying CMIP data rather than storing it, but it depends on the compute/storage costs I guess.
Thanks!

Hey, I'm standing with @cisaacstern and keen to figure out how to make this work 😊

Fantastic. Thanks for pinging this issue. I propose that we formalize this effort into a working group.
I would like to include @SammyAgrawal in this group, since I think this is a perfect way to learn more about apache beam and fits right into sammys project work of building reproducible ML/climate science pipelines. Sammy I hope this works well for you, I think this is a real great ✨synergy🤗.

Proposed next steps:

Schedule a Meeting (if possible early January?)
Pre Meeting TODO:

[x] Make a repository (https://github.com/leap-stc/science_orchestration) to keep our efforts neat and organized
Add a minimal example of the processing for a single ClimateBench dataset to the repo (|Duncan| might have provided this at some point, but I think I lost track)

Milestones:

Build an Apache Beam Pipeline that can achieve the minimal example provided.
Expand the pipeline to all datasets available in the public bucket

What I hope we will learn:

How to build a reproducible and efficient pipeline that executes xarray commands.

Are we going to use https://github.com/google/xarray-beam for this?

How to best parameterize this over different inputs (in this case different models, experiements etc)

Perfect, thanks @jbusecke! Please send a doodle for January.
I have a single-model version pulling from ESGF here: https://github.com/duncanwp/ClimateBench/blob/main/prepare_data.py

When2Meet Poll

Just wanted to ping this thread. @cisaacstern could you fill out your availability? @SammyAgrawal could you double check the dates next week? It would be fantastic if we could make Tue (16th) or Wed (17th) work.
Also a quick check back to @duncanwp: I think the code you provided up top is only to download from ESGF. I was under the assumption we want to avoid this step and load directly from the cloud zarr stores? What code is used to process the final output? Is that this notebook: https://github.com/duncanwp/ClimateBench/blob/main/prep_input_data.ipynb
Excited to push this ahead!

I sent an invite for Tue (Jan 16) 3-4PM EST!

Hi all,Apologies but that time slot is now filled for me and I can’t move it… was there another that worked?Cheers,DuncanSent from my iPhone, at a time that suits me. Please feel free to respond at a time that suits you.On Jan 10, 2024, at 11:17, Julius Busecke @.***> wrote:
I sent an invite for Tue (Jan 16) 3-4PM EST!
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

The ranges that worked according to the poll were:

Tue 16th Jan 2-4pm EST
Wed 17th Jan 3-5PM EST

Do you have availability in those ranges?

Yes, any of the times on Wednesday would still work!

I moved it to wed 3pm! Looking forward.


Add option for hiding pagination for one page

Add option for hiding pagination for one page. For example, sales order lines are shown in one page, and no need for pagination.
Solution: allow rowsPerPage to be nullable ( int? ). If null, hide the pagination.

You can use hidePaginator and rebuild the widget


fix: conflicts-PR_GUIDELINES

Pull Request Details
Description
This PR addresses the conflicting instructions in the repository regarding which branch PRs should be submitted against. The current guidelines have contradictory statements, causing confusion among contributors. This PR aims to clarify the correct branch for PR submissions.
Fixes
This PR resolves issue #[976] (Conflicting Pull Request Guidelines). Edited the documentation to only submit PRs against the main branch.
Type of PR

[ ] Bug fix
[ ] Feature enhancement
[x] Documentation update
[ ] Refactoring
[ ] Other (specify): _______________

Summary

Updated the PR_GUIDELINES.md to specify the correct branch of PR submissions

Screenshots (if applicable)

Additional Notes
Please review the updated guidelines and confirm that the specified branch for PR submissions is correct. This will help in maintaining a clear and consistent contribution process.
Checklist

[x] I have read and followed the Pull Requests and Issues guidelines.
[x] The code has been properly linted and formatted using npm run lint:fix and npm run format:fix.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, snapshots, and videos after making the changes.
[x] I have not borrowed code without disclosing it, if applicable.
[x] This pull request is not a Work In Progress (WIP), and only completed and tested changes are included.
[x] I have tested these changes locally.
[x] My code follows the project's style guidelines.
[x] I have updated the documentation accordingly.
[x] This PR has a corresponding issue in the issue tracker.

Please make a new branch for PR next time.

🚀 Congratulations on the successful PR merge! 🌟
Thank you for your valuable contribution! 🎉
Let's continue to make waves in open source. Share your achievement on social media and tag Digitomize to help spread the word.
Thank you for your dedication!
@all-contributors please add @RohittCodes for docs


Get tests passing in Node v5

Node 5 is the version running on the server.
Rest parameters are enabled by default in Node 6, but require a
compatibility flag in Node 5.
http://node.green/#ES2015-syntax-rest-parameters
Fixes #802

I upgraded the servers to node 6 (the lowest version in production is now v6.2.1), so that my fanciness not be defeated by such petty considerations!

Ah nice! I don't see any reason to support Node < 6, do you?

No. It's not even LTS.


Enhance Alerts component with dynamic colored notes using AlertColors

[!NOTE]
We are meticulous when it comes to merging code into the main branch, so please understand that we may reject pull requests that do not meet the project's standards. It's never personal. Also, game-related scripts have a lower chance of being merged.

Description
This pull request includes updates to the Alerts component and related configurations to enhance the handling and styling of alert messages. The changes involve defining a new AlertColors configuration and updating the Alerts component to utilize this configuration for dynamic styling based on alert types.
Updates to Alerts Component:

frontend/src/app/scripts/_components/ScriptItems/Alerts.tsx: Introduced a new NoteProps type and updated the Alerts component to use AlertColors for dynamic styling of alert messages.

Configuration Additions:

frontend/src/config/siteConfig.tsx: Added a new AlertColors configuration object to define styles for different alert types (warning, danger, info).

Type Definitions:

frontend/src/lib/types.ts: Imported AlertColors and updated the Script type to use keyof typeof AlertColors for the type property in notes. [1] [2]

Fixes # (issue)
Type of change
Please check the relevant option(s):

[ ] Bug fix (non-breaking change that resolves an issue)
[x] New feature (non-breaking change that adds functionality)
[ ] Breaking change (a fix or feature that would cause existing functionality to change unexpectedly)
[ ] New script (a fully functional and thoroughly tested script or set of scripts.)

Prerequisites
The following efforts must be made for the PR to be considered. Please check when completed:

[ ] Self-review performed (I have reviewed my code, ensuring it follows established patterns and conventions)
[ ] Testing performed (I have tested my changes, ensuring everything works as expected)
[ ] Documentation updated (I have updated any relevant documentation)

Additional Information (optional)
Provide any additional context or screenshots about the feature or fix here.
Related Pull Requests / Discussions
If there are other pull requests or discussions related to this change, please link them here:

Related PR #

i have not tested this, since im working on my main branch on the json generator.


Update sort.cpp

Hey @manav1234
Links only appear in the Markdown version of the file not in the sample snippets
For e.g see sort.md
I already has a Run Code link

It already has a Run Code link
so are you telling me that i dont have to add links in the snippets
then do I have to check all the .md files to add links ?

so sir where should I add the links now
in the markdown files?
also sir can I have your WhatsApp number because it is extremely difficult
to communicate and I need some help since I am beginner
On Wed, Jun 26, 2019, 2:28 PM Bhupesh Varshney<EMAIL_ADDRESS>wrote:

Hey @manav1234 https://github.com/manav1234
Links only appear in the Markdown version of the file not in the sample
snippets
For e.g see sort.md
https://github.com/Bhupesh-V/30-seconds-of-cpp/blob/master/algorithm/sort.md
I already has a Run Code link
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Bhupesh-V/30-seconds-of-cpp/pull/83?email_source=notifications&email_token=AEOERQOZDCNWBLLPEYEY62TP4MVRVA5CNFSM4H3P6XV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYS27DA#issuecomment-505786252,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEOERQJ2B3TDS6NBFBQWG4LP4MVRVANCNFSM4H3P6XVQ
.


Overly complicated system

Hey, I've tried using this library multiple times over the past year or so.. Every time I always run into two issues, the api constantly changes to the point where I have to rewrite and figure out how to do stuff over again from version to version.
And this library is WAY too complicated to actually use for anything, too many options in the first readme alone.
IMO this is a great project that needs some actual documentation and the main structure cant change every too seconds.

Hey, I've tried using this library multiple times over the past year or so.. Every time I always run into two issues, the api constantly changes to the point where I have to rewrite and figure out how to do stuff over again from version to version.
And this library is WAY too complicated to actually use for anything, too many options in the first readme alone.
IMO this is a great project that needs some actual documentation and the main structure cant change every too seconds.

I agree with you on the frequent changes, I just love to code so I frequently switch things up. That's why I've changed the project's artifact to cobalt and I will commit to no breaking changes starting from release 0.1
On the other hand I'd say that the documentation is excellent, and that the complexity is justified because there just are a lot of things you can do with this library. If you are not familiar with asynchronous programming in Java and modern features like lambdas I can see how it could be overwhelming, but that's not an issue of the library.

It's so overly complicated I can never tell if theres a bug or if I messed something up..
like some listeners plain out right dont work and I dont know if its me that is using them wrongly or its just broken.
also the examples are outdated.

It's so overly complicated I can never tell if theres a bug or if I messed something up..
like some listeners plain out right dont work and I dont know if its me that is using them wrongly or its just broken.
also the examples are outdated.

As I said I don't feel like the library is hard to use, about your question realistically it's a bug as the master branch has been updated for a long time without a release. When I release 0.1 these issues should be resolved. About the outdated examples, I'll update them when I release 0.1

Is 0.1 stable and if so is there a way for me to use it

It's on the master branch, but no, it's not stable as of now. You can try it if you want though


SUBMARINE-499. Refactor job API to experiment API

What is this PR for?

Refactor the training job to experiment
Redefined the experiment spec

What type of PR is it?
Refactoring
Todos
What is the Jira issue?
https://issues.apache.org/jira/browse/SUBMARINE-499
How should this be tested?
Screenshots (if appropriate)
Questions:

Does the licenses files need update? Yes/No
Is there breaking changes for older versions? Yes/No
Does this needs documentation? Yes/No

Thanks @tangzhankun for the review. This is a draft PR which means it still work in progress, I'm still working for this.

If i understand correctly, the environment's spec like below:
"environment": {
    "name": "tensorflow",
    "dockerImage": "gcr.io/kubeflow-ci/tf-mnist-with-summaries:1.0",
    "cmd": [
         "python",
         "/var/tf_mnist/mnist_with_summaries.py",
         "--log_dir=/train/log",
         "--learning_rate=0.01",
         "--batch_size=150"
      ]
}

and the task level can overwrite the environment.
@wangdatan Sorry for the late delivery. The current pr failed by the Integration Testing caused by parse the response from submarine server. I will fix it ASAP and modify the propose.

No worries @jiwq .
I think environment can be either uniquely named, or anonymously. See my comment on:
https://issues.apache.org/jira/browse/SUBMARINE-507?focusedCommentId=17119816&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17119816 (you can search "One thing I realized is")
So I think we don't have to specify name and docker-image name at the same time. Also specify cmd in the environment doesn't make sense to me. Environment is supposed to be libraries and dependencies, not code. If user want to use code embedded inside an environment (docker image), that's their choice, but we may not want to add it to the environment API.
So the environment you listed I think it is sufficient to leave docker image for now:
"environment": {
    "dockerImage": "gcr.io/kubeflow-ci/tf-mnist-with-summaries:1.0"
}

We can improve this part once SUBMARINE-507 finished.

I spent some time checking the new Swagger Python API generated by this PR. Foud that it seems more complex than the previous JobSpec.
Here's the original JobSpec for tensorflow (Pytorch is very similar. The differences are taskSpec has {"master": ms", "worker":worker}):
jobLibrarySpec = JobLibrarySpec(name='tensorflow',
                                version='2.1.0',
                                image='gcr.io/kubeflow-ci/tf-mnist-with-summaries:1.0',
                                cmd='python /var/tf_mnist/mnist_with_summaries.py'
                                    ' --log_dir=/train/log --learning_rate=0.01'
                                    ' --batch_size=150',
                                env_vars={'ENV1': 'ENV1'})
ps = JobTaskSpec(name='ps',
                     image=None,
                     cmd=None,
                     env_vars=None,
                     resources='cpu=2,memory=1024M',
                     replicas=1)
worker = JobTaskSpec(name='worker',
                     image=None,
                     cmd=None,
                     env_vars=None,
                     resources='cpu=4,memory=2048M',
                     replicas=1)

body = JobSpec(name='mnist',
               namespace='submarine',
               library_spec=jobLibrarySpec,
               task_specs={"Ps": ps", "Worker": worker})
submarine_client.create_job(body=body)

Here's how we define an ad-hoc experiment spec for Tensorflow:
codeSpec = CodeSpec(mode = 'docker',
                      url= 'gcr.io/kubeflow-ci/tf-mnist-with-summaries:1.0')
resourceSpec = ResourceSpec(cpu = '4', memory = '2048M')
psSpec = AdhocDistRoleSpec(replicas = 1,
                                name = 'ps',
                                cmd = 'Python ./train.py',
                                env_vars=None,
                                resource = resourceSpec
                                )
workerSpec = AdhocDistRoleSpec(replicas = 1,
                                name = 'ps',
                                cmd = 'Python ./train.py',
                                env_vars=None,
                                resource = resourceSpec
                                )
distTFSpec = AdhocDistTFSpec(image = None,
                                type = "tensorflow",
                                ps = psSpec,
                                worker = workerSpec,
                                chief = None,
                                evaluator = None,
                                )
body = AdhocExperiemntSpec(name = 'minist',
                                namespace = 'default',
                                code = codeSpec,
                                type = 'adhoc',
                                spec = distTFSpec
                                )
submarine_client.create_experiment(body=body)

Here's how we define an ad-hoc experiment spec for PyTorch:
codeSpec = CodeSpec(mode = 'docker',
                      url= 'gcr.io/kubeflow-ci/tf-mnist-with-summaries:1.0')
resourceSpec = ResourceSpec(cpu = '4', memory = '2048M')
masterSpec = AdhocScriptSpec(replicas = 1,
                                name = 'ps',
                                cmd = 'Python ./train.py',
                                env_vars=None,
                                resource = resourceSpec,
                                image = Node)
workerSpec = AdhocScriptSpec(replicas = 1,
                                name = 'ps',
                                cmd = 'Python ./train.py',
                                env_vars=None,
                                resource = resourceSpec,
                                image = Node)
distPYSpec = AdhocDistPyTorchSpec(image = None,
                                type = "pytorch",
                                master = masterSpec,
                                worker = workerSpec)
body = AdhocExperiemntSpec(name = 'minist',
                                namespace = 'default',
                                code = codeSpec,
                                type = 'adhoc',
                                spec = distTFSpec)
submarine_client.create_experiment(body=body)

@jiwq , @wangdatan , @kevin85421  Please check it to have a feeling of the generated API.
I'm fine if we go with this PR, but we should use AdhocDistRoleSpec for PyTorch as well as Tensorflow instead of AdhocScriptSpec. It's too confusing.

And this is JSON format of this PR:
{
  "name": "mnist",
  "namespace": "default",
  "type": "adhoc",
  "spec": {
    "type": "tensorflow",
    "ps": {
      "name": "tensorflow",
      "cmd": [
        "python",
        "/var/tf_mnist/mnist_with_summaries.py",
        "--log_dir=/train/log",
        "--learning_rate=0.01",
        "--batch_size=150"
      ],
      "envVars": {
        "ENV_1": "ENV1"
      },
      "resource": {
        "cpu": "1",
        "memory": "512M"
      },
      "replicas": 1
    },
    "worker": {
      "name": "tensorflow",
      "cmd": [
        "python",
        "/var/tf_mnist/mnist_with_summaries.py",
        "--log_dir=/train/log",
        "--learning_rate=0.01",
        "--batch_size=150"
      ],
      "envVars": {
        "ENV_1": "ENV1"
      },
      "resource": {
        "cpu": "1",
        "memory": "512M"
      },
      "replicas": 1
    }
  },
  "code": {
    "mode": "docker",
    "url": "gcr.io/kubeflow-ci/tf-mnist-with-summaries:1.0"
  }
}

And our Job Spec in JSON format:
{
  "name": "mnist",
  "librarySpec": {
    "name": "TensorFlow",
    "version": "2.1.0",
    "image": "gcr.io/kubeflow-ci/tf-mnist-with-summaries:1.0",
    "cmd": "python /var/tf_mnist/mnist_with_summaries.py --log_dir=/train/log --learning_rate=0.01 --batch_size=150",
    "envVars": {
      "ENV_1": "ENV1"
    }
  },
  "submitterSpec": {
    "type": "k8s",
    "namespace": "submarine"
  },
  "taskSpecs": {
    "Ps": {
      "name": "tensorflow",
      "replicas": 2,
      "resources": "cpu=4,memory=2048M,nvidia.com/gpu=1"
    },
    "Worker": {
      "name": "tensorflow",
      "replicas": 2,
      "resources": "cpu=4,memory=2048M,nvidia.com/gpu=1"
    }
  }
}

And our new expected experiment spec:
{
  "name": "mnist",
  "namespace": "default",
  “type”: “adhoc”,
  "environment": {
      "dockerImage": "gcr.io/kubeflow-ci/tf-mnist-with-summaries:1.0"
  }
  "cmd": "python /var/tf_mnist/mnist_with_summaries.py --log_dir=/train/log --learning_rate=0.01 --batch_size=150",
  "spec": {
    “type”: "TensorFlow",
    "Ps": {
      "name": "tensorflow",
      "replicas": 2,
      "resources": "cpu=4,memory=2048M,nvidia.com/gpu=1"
    },
    "Worker": {
      "name": "tensorflow",
      "replicas": 2,
      "resources": "cpu=4,memory=2048M,nvidia.com/gpu=1"
    }
  }

Thanks @tangzhankun , the last one

And my understanding of the new expected experiment spec in the discussion. @jiwq ,
@wangdatan , @kevin85421 do you feel the below is better?

Is way better to me, even if it may not be exactly same as the final API, it looks very similar to what we want, so we can release it in the 0.4.0.

Thanks @tangzhankun , the last one is better to me. If no more comments, I'll do it in 0.4.0 and release it soon.

When I try to refactor this structure, I found the spec can't deserialize to Java Map. So I think we can do some modify. The experiment spec like:
{
  "meta": {
    "name": "mnist",
    "namespace": "submarine",
    "framework": "TensorFlow",
    "cmd": "python /var/tf_mnist/mnist_with_summaries.py --log_dir=/train/log --learning_rate=0.01 --batch_size=150"
  },
  "environment": {
    "dockerImage": "gcr.io/kubeflow-ci/tf-mnist-with-summaries:1.0"
  },
  "spec": {
    "Ps": {
      "replicas": 1,
      "resources": "cpu=4,memory=2048M"
    },
    "Worker": {
      "replicas": 2,
      "resources": "cpu=2,memory=1024M,nvidia.com/gpu=1"
    }
  }
}

Python client:
meta = Meta(name='mnist', namespace='submarine', framework='TensorFlow',
           cmd: "python /var/tf_mnist/mnist_with_summaries.py --log_dir=/train/log --learning_rate=0.01 --batch_size=150")
environment = Environment(docker-image='gcr.io/kubeflow-ci/tf-mnist-with-summaries:1.0')
ps = Task(environment = None, cmd=None, env_vars=None,
           resources='cpu=2,memory=1024M', replicas=1)
worker = TaskSpec(environment = None, cmd=None,  env_vars=None,
           resources='cpu=4,memory=2048M', replicas=2)
body = ExperimentSpec(meta=meta, environment = environment,
           spec={"type":"tensorflow", "Ps": ps, "Worker": worker})
client.create_experiment(body=body)

@jiwq , thanks for the update. I think this spec looks good to me too.
{
  "meta": {
    "name": "mnist",
    "namespace": "submarine",
    "framework": "TensorFlow",
    "cmd": "python /var/tf_mnist/mnist_with_summaries.py --log_dir=/train/log --learning_rate=0.01 --batch_size=150"
  },
  "environment": {
    "dockerImage": "gcr.io/kubeflow-ci/tf-mnist-with-summaries:1.0"
  },
  "spec": {
    "Ps": {
      "replicas": 1,
      "resources": "cpu=4,memory=2048M"
    },
    "Worker": {
      "replicas": 2,
      "resources": "cpu=2,memory=1024M,nvidia.com/gpu=1"
    }
  }
}

My biggest worry is, does it mean we need to double our efforts since we will do two big changes (rename Job to Experiment, and move old Experiment spec to new) to our code and SDK? If it is not two big changes, I will be fine with this proposal.

I have written a script to auto-generate client SDK code, so there is less effort to refactor.
{
  "meta": {
    "name": "mnist",
    "namespace": "submarine",
    "framework": "TensorFlow",
    "cmd": "python /var/tf_mnist/mnist_with_summaries.py --log_dir=/train/log --learning_rate=0.01 --batch_size=150"
  },
  "environment": {
    "dockerImage": "gcr.io/kubeflow-ci/tf-mnist-with-summaries:1.0"
  },
  "spec": {
    "Ps": {
      "replicas": 1,
      "resources": "cpu=4,memory=2048M"
    },
    "Worker": {
      "replicas": 2,
      "resources": "cpu=2,memory=1024M,nvidia.com/gpu=1"
    }
  }
}

The new job spec is very clear to me.
After this PR is merged, I will update SDK ASAP.

Thanks @jiwq!
The latest spec looks good to me, even it may not be exactly same as what we will release in 0.5 or after, but it is shaped in a similar way which we can migrate them to a more stable version in 0.5.
Just one thing, I think we need to highlight now Experiment API is in alpha stage which is subjected to incompatible changes in the future releases. We need to target to move it to beta version from 0.5 release.
I will rely on other folks to do detailed code reviews.

@jiwq Thanks for the update! I'll commit this soon.


Update dependencies in v1 to support react v17

Installing react-popper@1 in a project containing react@17, with npm@7 results in the following error:
> npm i react-popper@1
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/react-dom
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!   1 more (react-popper)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>|| ^15.0.0 || ^16.0.0" from<EMAIL_ADDRESS>npm ERR! node_modules/react-popper/node_modules/create-react-context
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/react-popper
npm ERR!     react-popper@"1" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

While there are active pull requests to create-react-context to support v17, it seems to be abandoned. A fork has been made to support it, and uploaded to npm as @hypnosphi/create-react-context. https://github.com/jamiebuilds/create-react-context/pull/32#issuecomment-758158196
I hope react-popper can use this package instead. Will add a merge request.

Keeping this one open until it's released 🙂

1.3.10 includes this fix :-)

Oh sorry, I was too quick. Thanks! 😄


QS v3.0 breaks the Qlik style.

The extension appears to be broken by the upgrade to 3.0.

Try downloading the latest version, where this is fixed.

Thanks Erik - we've downloaded the latest QS build and extension. The Qlik style does not seem to be being applied? i.e. the buttons don't look as they normally do and you cannot see which option is selected.

I apologize, you are right. I made a mistake when I updated this. Should be OK now, please try again.

Thanks Erik, I’ll ask the team to test and come back to you if there are any issues.
Kind regards,
Chirag
Chirag Kotecha
Advisor, Management Consulting
Technology Enablement
T: +44 (0)207 311 2589
M: +44 (0)7766 247 933
From: Erik Wetterberg<EMAIL_ADDRESS>Sent: 07 July 2016 14:33
To: erikwett/qsVariable<EMAIL_ADDRESS>Cc: Kotecha, Chirag<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [erikwett/qsVariable] QS v3.0 breaks the Qlik style. (#4)
I apologize, you are right. I made a mistake when I updated this. Should be OK now, please try again.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/erikwett/qsVariable/issues/4#issuecomment-231078320, or mute the threadhttps://github.com/notifications/unsubscribe/ATXCDDvAM1pWvQQZcmTkSoW77h2k6t3lks5qTP_9gaJpZM4JFMSZ.
This email has been sent by and on behalf of one or more of KPMG LLP, KPMG Audit plc, KPMG Resource Centre Private Limited or a company under the control of KPMG LLP, including KPMG United Kingdom plc and KPMG UK Limited (together, "KPMG").
This email, and any attachments, is confidential and may be privileged or otherwise protected from disclosure. It is intended solely for the stated addressee(s) and access to it by any other person is unauthorised. If you are not the intended recipient, you must not disclose, copy, circulate or in any other way use or rely on the information contained herein. If you have received this email in error, please inform us immediately and delete all copies of it.
Any communications made with KPMG may be monitored and a record may be kept of any communication.
Any opinion or advice contained herein is subject to the terms and conditions set out in your KPMG LLP client engagement letter.
A list of members of KPMG LLP is open for inspection at KPMG's registered office.
KPMG LLP (registered no. OC301540) is a limited liability partnership registered in England and Wales. Each of KPMG Audit plc (registered no. 03110745), KPMG United Kingdom plc (registered no. 03513178) and KPMG UK Limited (registered no. 03580549) are companies registered in England and Wales. Each entity's registered office is at 15 Canada Square, London, E14 5GL.
For full details of our professional regulation please refer to https://www.kpmg.com/uk/en/about/aboutkpmg/pages/regulatory-information.aspx.

Hi Erik
I am facing the same issue .
I am also using ver 3 QS .
I have try to re-install the latest extension , still the same , may i know where i go wrong ?
Paul

Hi chirag
I am still facing the same issue , even I re install var extension twice
In case you have solve the issue
Pls info me
Paul


Alias default to is_default for customer addresses

WHY are these changes introduced?
Closes #754
As pointed out in the issue, we currently have 2 instances of default in the CustomerAddress resource:

The method to set an address as default
The response field indicating whether an address is the default

WHAT is this pull request doing?
Aliasing the read-only field to is_default so they don't overlap and cause breakages in apps.
Question: is this actually a breaking change? Are we breaking apps that expect default to be the boolean value in certain contexts?
Type of change

[x] Patch: Bug (non-breaking change which fixes an issue)

Checklist

[x] I have used yarn changeset to create a draft changelog entry (do NOT update the CHANGELOG.md files manually)
[x] I have added/updated tests for this change

In the next API release do we want to make this the default functionality?

Yes I think so - the current behaviour is technically broken, even if only some scenarios.


Return proper status code for errors

Return 404 for nonexistent problems at least.

It might be better to create a dedicated page for 404.


Port 3000 not listening inside Docker container after upgrade

Bug Description
I have upgraded my container instance, however, HTTP server in it didn't come up.  netstat does not show it is listening on port 3000.  However, when I bring it up fresh (no volumes), it IS listening on port 3000.
Gogs Version
gogs/gogs:latest
Git Version
git --version outputs git version 2.11.1 inside the container.
System Type
Docker container gogs/gogs:latest.
Error Log
Docker container output,
3/28/2017 11:14:09 PMinit:socat  | Linked container DB will be binded to localhost on port 3306
3/28/2017 11:14:09 PMinit:socat  | Can't bind linked container GOGS_MYSQL_1 to localhost, port 3306 already in use
3/28/2017 11:14:09 PMinit:socat  | Can't bind linked container GOGS_GOGS_MYSQL_1 to localhost, port 3306 already in use
3/28/2017 11:14:09 PMMar 29 06:14:09 syslogd started: BusyBox v1.25.1
3/28/2017 11:14:10 PMMar 29 06:14:10 sshd[32]: Server listening on :: port 22.
3/28/2017 11:14:10 PMMar 29 06:14:10 sshd[32]: Server listening on <IP_ADDRESS> port 22.
3/28/2017 11:14:36 PM2017/03/29 06:14:36 [TRACE] Custom path: /data/gogs
3/28/2017 11:14:36 PM2017/03/29 06:14:36 [TRACE] Log path: /data/app/gogs/log
3/28/2017 11:14:36 PM2017/03/29 06:14:36 [TRACE] Build Time: 2017-03-28 08:52:49 UTC
3/28/2017 11:14:36 PM2017/03/29 06:14:36 [TRACE] Build Git Hash:
3/28/2017 11:14:36 PM2017/03/29 06:14:36 [TRACE] Log Mode: File (Trace)
3/28/2017 11:14:36 PM2017/03/29 06:14:36 [ INFO] git.xxxxxxxxxxxx <IP_ADDRESS>8 / 0.11 RC
3/28/2017 11:14:59 PM2017/03/29 06:14:59 [TRACE] Custom path: /data/gogs
3/28/2017 11:14:59 PM2017/03/29 06:14:59 [TRACE] Log path: /data/app/gogs/log
3/28/2017 11:14:59 PM2017/03/29 06:14:59 [TRACE] Build Time: 2017-03-28 08:52:49 UTC
3/28/2017 11:14:59 PM2017/03/29 06:14:59 [TRACE] Build Git Hash:
3/28/2017 11:14:59 PM2017/03/29 06:14:59 [TRACE] Log Mode: File (Trace)
3/28/2017 11:14:59 PM2017/03/29 06:14:59 [ INFO] git.xxxxxxxxxxxx <IP_ADDRESS>8 / 0.11 RC

Notice it doesn't say listening on 3000.  A fresh instance does.
app/gogs/log/serv.log doesn't have anything timestamped later than upgrade timestamp.
app/gogs/log/xorm.log has some stuff,
2017/03/29 05:57:52 [xorm] [warn]  2017/03/29 05:57:52.862555 Table repository Column name db nullable is false, struct nullable is true
2017/03/29 05:57:53 [xorm] [warn]  2017/03/29 05:57:53.601704 Table repository has column lower_name but struct has not related field
2017/03/29 05:57:53 [xorm] [warn]  2017/03/29 05:57:53.601753 Table repository has column description but struct has not related field
2017/03/29 05:57:53 [xorm] [warn]  2017/03/29 05:57:53.601776 Table repository has column website but struct has not related field
2017/03/29 05:57:53 [xorm] [warn]  2017/03/29 05:57:53.601800 Table repository has column default_branch but struct has not related field
2017/03/29 05:57:53 [xorm] [warn]  2017/03/29 05:57:53.601822 Table repository has column num_watches but struct has not related field
2017/03/29 05:57:53 [xorm] [warn]  2017/03/29 05:57:53.601844 Table repository has column num_stars but struct has not related field
2017/03/29 05:57:53 [xorm] [warn]  2017/03/29 05:57:53.601904 Table repository has column num_forks but struct has not related field
2017/03/29 05:57:53 [xorm] [warn]  2017/03/29 05:57:53.601926 Table repository has column num_issues but struct has not related field
2017/03/29 05:57:53 [xorm] [warn]  2017/03/29 05:57:53.601947 Table repository has column num_closed_issues but struct has not related field
2017/03/29 05:57:53 [xorm] [warn]  2017/03/29 05:57:53.601969 Table repository has column num_pulls but struct has not related field
2017/03/29 05:57:53 [xorm] [warn]  2017/03/29 05:57:53.601990 Table repository has column num_closed_pulls but struct has not related field
2017/03/29 05:57:53 [xorm] [warn]  2017/03/29 05:57:53.602011 Table repository has column num_milestones but struct has not related field
2017/03/29 05:57:53 [xorm] [warn]  2017/03/29 05:57:53.602033 Table repository has column num_closed_milestones but struct has not related field
2017/03/29 05:57:53 [xorm] [warn]  2017/03/29 05:57:53.602056 Table repository has column is_private but struct has not related field
2017/03/29 05:57:53 [xorm] [warn]  2017/03/29 05:57:53.602077 Table repository has column is_bare but struct has not related field
2017/03/29 05:57:53 [xorm] [warn]  2017/03/29 05:57:53.602099 Table repository has column is_mirror but struct has not related field
2017/03/29 05:57:53 [xorm] [warn]  2017/03/29 05:57:53.602120 Table repository has column enable_wiki but struct has not related field
2017/03/29 05:57:53 [xorm] [warn]  2017/03/29 05:57:53.602141 Table repository has column enable_external_wiki but struct has not related field
2017/03/29 05:57:53 [xorm] [warn]  2017/03/29 05:57:53.602162 Table repository has column external_wiki_url but struct has not related field
2017/03/29 05:57:53 [xorm] [warn]  2017/03/29 05:57:53.602193 Table repository has column enable_issues but struct has not related field
2017/03/29 05:57:53 [xorm] [warn]  2017/03/29 05:57:53.602221 Table repository has column enable_external_tracker but struct has not related field
2017/03/29 05:57:53 [xorm] [warn]  2017/03/29 05:57:53.602243 Table repository has column external_tracker_format but struct has not related field
2017/03/29 05:57:53 [xorm] [warn]  2017/03/29 05:57:53.602265 Table repository has column external_tracker_style but struct has not related field
2017/03/29 05:57:53 [xorm] [warn]  2017/03/29 05:57:53.602304 Table repository has column enable_pulls but struct has not related field
2017/03/29 05:57:53 [xorm] [warn]  2017/03/29 05:57:53.602326 Table repository has column is_fork but struct has not related field
2017/03/29 05:57:53 [xorm] [warn]  2017/03/29 05:57:53.602348 Table repository has column fork_id but struct has not related field
2017/03/29 05:57:53 [xorm] [warn]  2017/03/29 05:57:53.602369 Table repository has column created_unix but struct has not related field
2017/03/29 05:57:53 [xorm] [warn]  2017/03/29 05:57:53.602393 Table repository has column updated_unix but struct has not related field

app/gogs/log/xorm.log keeps getting appended with the following,
2017/03/29 06:18:36 [TRACE] Log Mode: File (Trace)
2017/03/29 06:18:36 [ INFO] git.xxxxxxxxxxxx <IP_ADDRESS>8 / 0.11 RC
2017/03/29 06:18:36 [ INFO] Cache Service Enabled
2017/03/29 06:18:36 [ INFO] Session Service Enabled
2017/03/29 06:18:36 [ INFO] Mail Service Enabled
2017/03/29 06:18:36 [ INFO] Register Mail Service Enabled
2017/03/29 06:18:36 [ INFO] Notify Mail Service Enabled
2017/03/29 06:18:36 [ INFO] Migration: remove invalid protect branch whitelist
2017/03/29 06:18:36 [FATAL] [...s/routers/install.go:67 GlobalInit()] Fail to initialize ORM engine: migrate: do migrate: Error 1146: Table 'gogs.protect_branch_whitelist' doesn't exist

Other information
Here is my /data/gogs/conf/app.ini,
APP_NAME = git.xxxxxxxxxxxx
RUN_USER = git
RUN_MODE = prod

[database]
DB_TYPE  = mysql
HOST     = db:3306
NAME     = gogs
USER     = root
PASSWD   = xxxxxxxxxxxx
SSL_MODE = disable
PATH     = data/gogs.db

[repository]
ROOT = /data/git/gogs-repositories

[server]
DOMAIN       = git.xxxxxxxxxxxx
HTTP_PORT    = 3000
ROOT_URL     = https://git.xxxxxxxxxxxx/
DISABLE_SSH  = false
SSH_PORT     = 2222
OFFLINE_MODE = true

[mailer]
ENABLED = true
HOST    = xxxxxxxxxxxx:25
FROM    = git@xxxxxxxxxxxx
USER    = git@xxxxxxxxxxxx
PASSWD  = xxxxxxxxxxxx

[service]
REGISTER_EMAIL_CONFIRM = true
ENABLE_NOTIFY_MAIL     = true
DISABLE_REGISTRATION   = true
ENABLE_CAPTCHA         = false
REQUIRE_SIGNIN_VIEW    = true

[picture]
DISABLE_GRAVATAR        = true
ENABLE_FEDERATED_AVATAR = false

[session]
PROVIDER = file

[log]
MODE      = file
LEVEL     = Info
ROOT_PATH = /data/app/gogs/log

[security]
INSTALL_LOCK = true
SECRET_KEY   = xxxxxxxxxxxx

I am guessing migration is failing?  How would I fix this?

Hi, this is fixed in https://github.com/gogits/gogs/pull/4361, you can now pull the latest Docker image again.

I just checked https://hub.docker.com/r/gogs/gogs/tags/, looks like it was updated 12 mins ago.
I tried to upgrade but I still get the same problem.

Tell me your exact version of Gogs.

How would I find out?  Is it in a file somewhere?

It can be found in file: templates/.VERSION

bash-4.3# cat /app/gogs/templates/.VERSION
<IP_ADDRESS>8 / 0.11 RCbash-4.3#

The latest is <IP_ADDRESS>9.

Oops.. didn't pull.
Seems to be working perfectly now.


Ensure 'Save' button is enabled after diagram element change

At present if the 'Save' button is greyed out, ie no changes have been made to the diagram since the last save, then if:

an element is moved
the save button is still inactive
the diagram can only be saved using the Electron pull down menu 'Save'
or if another element/background is selected then save button becomes active

It would be good for the 'Save' button to become active as soon as any change to the diagram is made, such as moving an element.

Duplicate of #96 , now fixed


EISDIR error

I receive an error message which I have no idea how to resolve. I guess it's a bug in this library?
Error:
events.js:48
    throw arguments[1]; // Unhandled 'error' event
                    ^
Error: EISDIR, illegal operation on a directory '/var/storage/1/2011/11/19'

Compressed code:
var fullPath = '/var/storage/1/2011/11/19';
fs.mkdir(fullPath, 0777, true, function(err){ console.log(err); });

Hi Ronni,
Please tell me which version of node you're running.
Thanks!

Hi Bruno,
I'm running the latest version, v.0.6.2.
Best,
Ronni Egeriis Persson
+45 31 24 54 34
<EMAIL_ADDRESS>http://egeriis.me
On Mon, Nov 21, 2011 at 01:34, Bruno Pedro <
<EMAIL_ADDRESS>
wrote:

Hi Ronni,
Please tell me which version of node you're running.
Thanks!

Reply to this email directly or view it on GitHub:
https://github.com/bpedro/node-fs/issues/2#issuecomment-2809656

Ever resolved? Same issue here


Add quirk to deny certain device capabilities

Most devices annouce a whole set of capabilities print,scan,fax
and users wants to choose to disable some of them because their
either broken or some other reason.
It fixes an issue where ipp-usb would reset a device usb connection
every few seconds because one of the caps is broken on the device.
Example deny print and fax to keep only scan
[HP Photosmart 6520 series]
  blacklist-caps = 5

Hi @izissise,
as for now, disabling certain capabilities will only allow to disable probing and DNS-SD (Avahi) announcing of the IPP fax service support. For other services (IPP printing and eSCL scanning), disabling capabilities bits literally will not change anything.
What if the final purpose of your patch, and how device with some capabilities disabled should behave? Should it affect only DNS-SD device announcing, or some other aspects of device functionality as well?

Hello @alexpevzner
I have a HP Photosmart 6520 series with everything stripped out except the scanner, my problem was that ipp-usb would reset the usb link mid-scan because ipp-usb was also probing for print and fax and the device was not responding.
Removing print and fax using this patch stopped ipp-usb resetting the usb link.
But in light of this new information maybe disabling the fax is the reason for it to work.
If disabling fax works on it's own, a better patch would be to add an option to disable fax. I'll come back to you once the test is done

For future reference here tail -f of /var/log/ipp-usb compiled with current master (without this patch):
==> main.log <==
06-03-2022 16:57:48:   ===============================
06-03-2022 16:57:48:   ipp-usb started in "udev" mode, pid=45487
06-03-2022 16:57:48: + PNP Bus 005 Device 003: added

==> 03f0-af11-XXXXXXXXXXXXXP-HP-Photosmart-6520-series.log <==
06-03-2022 16:57:48:
06-03-2022 16:57:48:   ===============================
06-03-2022 16:57:48: + Bus 005 Device 003: added Photosmart 6520 series
06-03-2022 16:57:48:   Device info:
06-03-2022 16:57:48:     Ident:         03f0-af11-XXXXXXXXXXXXXP-HP-Photosmart-6520-series
06-03-2022 16:57:48:     Manufacturer:  HP
06-03-2022 16:57:48:     Product:       Photosmart 6520 series
06-03-2022 16:57:48:     SerialNumber:  XXXXXXXXXXXXXP
06-03-2022 16:57:48:     MfgAndProduct: HP Photosmart 6520 series
06-03-2022 16:57:48:     BasicCaps:     print,scan,fax,http
06-03-2022 16:57:48:
06-03-2022 16:57:48:   Device quirks:
06-03-2022 16:57:48:     from [*] (/usr/share/ipp-usb/quirks/default.conf:3)
06-03-2022 16:57:48:       blacklist = false
06-03-2022 16:57:48:       usb-max-interfaces = 0
06-03-2022 16:57:48:       http-connection = ""
06-03-2022 16:57:48:
06-03-2022 16:57:48:   USB stack parameters
06-03-2022 16:57:48:     authorized_default:          -1
06-03-2022 16:57:48:     autosuspend:                 2
06-03-2022 16:57:48:     blinkenlights:               N
06-03-2022 16:57:48:     initial_descriptor_timeout:  5000
06-03-2022 16:57:48:     nousb:                       N
06-03-2022 16:57:48:     old_scheme_first:            N
06-03-2022 16:57:48:     quirks:
06-03-2022 16:57:48:     usbfs_memory_mb:             16
06-03-2022 16:57:48:     usbfs_snoop:                 N
06-03-2022 16:57:48:     usbfs_snoop_max:             65536
06-03-2022 16:57:48:     use_both_schemes:            Y
06-03-2022 16:57:48:
06-03-2022 16:57:48:   USB interfaces:
06-03-2022 16:57:48:     Config Interface Alt Class SubClass Proto
06-03-2022 16:57:48:        1       0      0   255    204     0
06-03-2022 16:57:48:        1       1      0   7      1       2
06-03-2022 16:57:48: *      1       1      1   7      1       4
06-03-2022 16:57:48:        1       2      0   8      6       80
06-03-2022 16:57:48:        1       3      0   255    4       1
06-03-2022 16:57:48: *      1       3      1   7      1       4
06-03-2022 16:57:48:
06-03-2022 16:57:48:   USB[0]: open: Bus 005 Device 003 Interface 1 Alt 1
06-03-2022 16:57:48:   USB[1]: open: Bus 005 Device 003 Interface 3 Alt 1
06-03-2022 16:57:48: > IPP request:
06-03-2022 16:57:48: > {
06-03-2022 16:57:48: >     VERSION 2.0
06-03-2022 16:57:48: >     OPERATION Get-Printer-Attributes
06-03-2022 16:57:48: >
06-03-2022 16:57:48: >     GROUP operation-attributes-tag
06-03-2022 16:57:48: >     ATTR "attributes-charset" charset: utf-8
06-03-2022 16:57:48: >     ATTR "attributes-natural-language" naturalLanguage: en-US
06-03-2022 16:57:48: >     ATTR "printer-uri" uri: http://localhost:60000/ipp/print
06-03-2022 16:57:48: >     ATTR "requested-attributes" keyword: color-supported document-format-supported media-size-supported mopria-certified printer-device-id printer-dns-sd-name printer-icons printer-info printer-kind printer-location printer-make-and-model printer-more-info printer-uuid sides-supported urf-supported
06-03-2022 16:57:48: > }
06-03-2022 16:57:48:
06-03-2022 16:57:48: > HTTP[000]: POST http://localhost:60000/ipp/print
06-03-2022 16:57:48: > HTTP[000]: request body: got 462 bytes; closed
06-03-2022 16:57:48: > HTTP[000]: body is small (462 bytes), prefetched before sending
06-03-2022 16:57:48: > HTTP[000]: HTTP request header:
06-03-2022 16:57:48: >   POST /ipp/print HTTP/1.1
06-03-2022 16:57:48: >   Host: localhost:60000
06-03-2022 16:57:48: >   User-Agent: ipp-usb
06-03-2022 16:57:48: >   Content-Length: 462
06-03-2022 16:57:48: >   Content-Type: application/ipp
06-03-2022 16:57:48: >
06-03-2022 16:57:48:   USB[0]: connection allocated, 1 in use: a-- ---
06-03-2022 16:57:48:   HTTP[000]: connection 0 allocated
06-03-2022 16:57:48: > USB[0]: write: wanted 586 sent 586 total 586
06-03-2022 16:57:48: < USB[0]: read: wanted 4096 got 0 total 0
06-03-2022 16:57:48: !  USB[1]: zero-size read
06-03-2022 16:57:48: < USB[1]: read: wanted 4096 got 0 total 0
06-03-2022 16:57:48: ! USB[1]: zero-size read
06-03-2022 16:57:48: < USB[1]: read: wanted 4096 got 0 total 0
06-03-2022 16:57:48: ! USB[1]: zero-size read
06-03-2022 16:57:49: < USB[1]: read: wanted 4096 got 0 total 0
06-03-2022 16:57:49: ! USB[1]: zero-size read
06-03-2022 16:57:50: < USB[1]: read: wanted 4096 got 0 total 0
06-03-2022 16:57:50: ! USB[1]: zero-size read
06-03-2022 16:57:51: < USB[1]: read: wanted 4096 got 0 total 0
06-03-2022 16:57:51: ! USB[1]: zero-size read
06-03-2022 16:57:52: < USB[1]: read: wanted 4096 got 0 total 0
06-03-2022 16:57:52: ! USB[1]: zero-size read
06-03-2022 16:57:53: < USB[1]: read: wanted 4096 got 0 total 0
06-03-2022 16:57:53: ! USB[1]: zero-size read
06-03-2022 16:57:54: ! HTTP[001]: Device initialization timed out
06-03-2022 16:57:54:   USB[1]: connection released, 0 in use: --- ---
06-03-2022 16:57:54: ! IPP FaxOut probe failed: HTTP: Post http://localhost:60000/ipp/faxout: Device initialization timed out
06-03-2022 16:57:54: - Bus 005 Device 003: resetting Photosmart 6520 series
06-03-2022 16:57:54:   USB[0]: closed
06-03-2022 16:57:54:   USB[1]: closed
06-03-2022 16:57:54: - Bus 005 Device 003: removed Photosmart 6520 series

==> main.log <==
06-03-2022 16:57:54: ! PNP Bus 005 Device 003: Device initialization timed out

06-03-2022 16:57:56: + PNP Bus 005 Device 003: retry

==> 03f0-af11-XXXXXXXXXXXXXP-HP-Photosmart-6520-series.log <==
06-03-2022 16:57:56:
06-03-2022 16:57:56:   ===============================
06-03-2022 16:57:56: + Bus 005 Device 003: added Photosmart 6520 series
06-03-2022 16:57:56:   Device info:
06-03-2022 16:57:56:     Ident:         03f0-af11-XXXXXXXXXXXXXP-HP-Photosmart-6520-series
....

It reset the usb connection and goes on forever

Here the log with the following quirks:
[HP Photosmart 6520 series]
  blacklist-caps = 4

06-03-2022 17:04:16:   ===============================
06-03-2022 17:04:16:   ipp-usb started in "udev" mode, pid=46876
06-03-2022 17:04:16: + PNP Bus 005 Device 004: added

==> 03f0-af11-XXXXXXXXXXXXXP-HP-Photosmart-6520-series.log <==
06-03-2022 17:04:16:
06-03-2022 17:04:16:   ===============================
06-03-2022 17:04:16: + Bus 005 Device 004: added Photosmart 6520 series
06-03-2022 17:04:16:   Device info:
06-03-2022 17:04:16:     Ident:         03f0-af11-XXXXXXXXXXXXXP-HP-Photosmart-6520-series
06-03-2022 17:04:16:     Manufacturer:  HP
06-03-2022 17:04:16:     Product:       Photosmart 6520 series
06-03-2022 17:04:16:     SerialNumber:  XXXXXXXXXXXXXP
06-03-2022 17:04:16:     MfgAndProduct: HP Photosmart 6520 series
06-03-2022 17:04:16:     BasicCaps:     print,scan,http
06-03-2022 17:04:16:
06-03-2022 17:04:16:   Device quirks:
06-03-2022 17:04:16:     from [HP Photosmart 6520 series] (/usr/share/ipp-usb/quirks/HP.conf:18)
06-03-2022 17:04:16:       blacklist = false
06-03-2022 17:04:16:       usb-max-interfaces = 0
06-03-2022 17:04:16:       blacklist-caps = fax
06-03-2022 17:04:16:     from [*] (/usr/share/ipp-usb/quirks/default.conf:3)
06-03-2022 17:04:16:       blacklist = false
06-03-2022 17:04:16:       usb-max-interfaces = 0
06-03-2022 17:04:16:       blacklist-caps =
06-03-2022 17:04:16:       http-connection = ""
06-03-2022 17:04:16:
06-03-2022 17:04:16:   USB stack parameters
06-03-2022 17:04:16:     authorized_default:          -1
06-03-2022 17:04:16:     autosuspend:                 2
06-03-2022 17:04:16:     blinkenlights:               N
06-03-2022 17:04:16:     initial_descriptor_timeout:  5000
06-03-2022 17:04:16:     nousb:                       N
06-03-2022 17:04:16:     old_scheme_first:            N
06-03-2022 17:04:16:     quirks:
06-03-2022 17:04:16:     usbfs_memory_mb:             16
06-03-2022 17:04:16:     usbfs_snoop:                 N
06-03-2022 17:04:16:     usbfs_snoop_max:             65536
06-03-2022 17:04:16:     use_both_schemes:            Y
06-03-2022 17:04:16:
06-03-2022 17:04:16:   USB interfaces:
06-03-2022 17:04:16:     Config Interface Alt Class SubClass Proto
06-03-2022 17:04:16:        1       0      0   255    204     0
06-03-2022 17:04:16:        1       1      0   7      1       2
06-03-2022 17:04:16: *      1       1      1   7      1       4
06-03-2022 17:04:16:        1       2      0   8      6       80
06-03-2022 17:04:16:        1       3      0   255    4       1
06-03-2022 17:04:16: *      1       3      1   7      1       4
06-03-2022 17:04:16:
06-03-2022 17:04:16:   USB[0]: open: Bus 005 Device 004 Interface 1 Alt 1
06-03-2022 17:04:16:   USB[1]: open: Bus 005 Device 004 Interface 3 Alt 1
06-03-2022 17:04:16: > IPP request:
06-03-2022 17:04:16: > {
06-03-2022 17:04:16: >     VERSION 2.0
06-03-2022 17:04:16: >     OPERATION Get-Printer-Attributes
06-03-2022 17:04:16: >
06-03-2022 17:04:16: >     GROUP operation-attributes-tag
06-03-2022 17:04:16: >     ATTR "attributes-charset" charset: utf-8
06-03-2022 17:04:16: >     ATTR "attributes-natural-language" naturalLanguage: en-US
06-03-2022 17:04:16: >     ATTR "printer-uri" uri: http://localhost:60000/ipp/print
06-03-2022 17:04:16: >     ATTR "requested-attributes" keyword: color-supported document-format-supported media-size-supported mopria-certified printer-device-id printer-dns-sd-name printer-icons printer-info printer-kind printer-location printer-make-and-model printer-more-info printer-uuid sides-supported urf-supported
06-03-2022 17:04:16: > }
06-03-2022 17:04:16:
06-03-2022 17:04:16: > HTTP[000]: POST http://localhost:60000/ipp/print
06-03-2022 17:04:16: > HTTP[000]: request body: got 462 bytes; closed
06-03-2022 17:04:16: > HTTP[000]: body is small (462 bytes), prefetched before sending
06-03-2022 17:04:16: > HTTP[000]: HTTP request header:
06-03-2022 17:04:16: >   POST /ipp/print HTTP/1.1
06-03-2022 17:04:16: >   Host: localhost:60000
06-03-2022 17:04:16: >   User-Agent: ipp-usb
06-03-2022 17:04:16: >   Content-Length: 462
06-03-2022 17:04:16: >   Content-Type: application/ipp
06-03-2022 17:04:16: >
06-03-2022 17:04:16:   USB[0]: connection allocated, 1 in use: a-- ---
06-03-2022 17:04:16:   HTTP[000]: connection 0 allocated
06-03-2022 17:04:16: > USB[0]: write: wanted 586 sent 586 total 586
06-03-2022 17:04:16: < USB[0]: read: wanted 4096 got 0 total 0
06-03-2022 17:04:16: !
I would accept this patch with the following changes:

Disabled capabilities will be listed by name (say, print, scan, fax, web), not by their numerical values
All prohibitions must be actually honored. I.e., if you disable printing, printing capability should actually be removed from the DNS-SD announce
New syntax must be documented in the ipp-usb.8 (please, update ipp-usb.8.md and recompile; don't update generated ipp-usb.8 directly. It should be noted, that disabling some particular capability only affects DNS-SD advertising and probing for the device parameters associated with the disabled capabilities, as ipp-usb doesn't somehow filter traffic that goes through it
Rules for your device will be added to the ipp-usb-quirks/HP.conf

Note, full implementing of 1 and 2 items may be quite noticeable amount of work, so may be it makes sense for now only to add a parameter to disable fax (say disable-fax = true | false)
Note also that  HP Photosmart 6520 series doesn't implement true faxing, but instead implements internet-based eFax, which makes no sense when connected via USB so can be safely disabled for this kind of devices.

Hello,
thanks for the response, indeed a disable-fax option is more than enough for my needs.
I created a new PR which I hope follow your given guidelines: https://github.com/OpenPrinting/ipp-usb/pull/46


Allow enclave executables to use both C and C++.

Previously, oelibcxx unconditionally added libcxx to the include path.
When a C file includes a header that is common between C and C++ say
stdint.h, the C++ version would be picked up which has C++ syntax
(extern "C") and causes compile errors.
This fix changes 3rdparty/libcxx so that the c++ include path is added
only if the file being compiled is a cpp file. This is enforced
via the COMPILE_LANGUAGE:CXX generator expression.

bors try

No, we don't need an equivalent for C.
C headers are needed for C++ code since C++ headers reference/forward to C headers.
Note: We have this ugly requirement that C++ enclave declare their target_rependencies in this order:
target_dependencies(enclave_name   oelibcxx oeenclave)
This ensures that C++ header directory comes first in the include list in the compiler command-line so that when C++ headers look for a C header, they can find it.

bors r+

Found the old issue created by Jork: #127
Our fix is the same as what he recommends - use COMPILE_LANGUAGE generator expression.
Unlike his observation, it now works with cmake.

Found another similar issue; with the older IDL implementation: #176
This is the same symptoms as @Paul encountered.


Remove words from DQA output

Related to (unfortunately) private slack convo (here).
originally from @Rocketknight1 :

Hey, for document-question-answering, the JS spec has "words", which is:
The index of each word/box pair that is in the answer
In transformers we don't output this at all. I'm not really sure how it's generated/used in the spec, since transformers already had start, end, answer, etc.

and then

Update: I think the words output never exists because of a pipeline bug. The pipeline has two code paths in several functions, one for VisionEncoderDecoder models and one for everything else.
In preprocess(), the VisionEncoderDecoder path always sets words to None which means it cannot be passed through to the output.
In postprocess() , the non-VisionEncoderDecoder path calls postprocess_extractive_qa. However, this function rewrites the answers dict without a words key
In other words, the preprocess() method deletes words for VisionEncoderDecoder models and the postprocess() method deletes it for everything else, so it always gets deleted! The right solution is just to remove it from the docstring and the JS spec.

Also to mention: DQA is only served from transformers in the Inference API.

(closing as duplicate of https://github.com/huggingface/huggingface.js/pull/1040)


Error when use tab-pills if have many tab and use  watch-tabs

When you use tab-pills and have many tab, class scrtabs-tabs-movable-container have witdh incorrect

Hi there,
v0.0.26 should fix this issue.
Thanks for letting me know about it--I never tested with >35 pills, but apparently beyond that number the width calculation is slightly off.


Sort the partitions before checking with toEqual

While toEqual does a deep equality, it won't be able to see that the partition arrays are "equal enough" when
they are reordered.

Output from a failing run:
FAIL  src/broker/__tests__/txnOffsetCommit.spec.js
● Broker > TxnOffsetCommit › request

  expect(received).toEqual(expected) // deep equality

  - Expected  - 2
  + Received  + 2

  @@ -3,15 +3,15 @@
      "topics": Array [
        Object {
          "partitions": Array [
            Object {
              "errorCode": 0,
  -           "partition": 0,
  +           "partition": 1,
            },
            Object {
              "errorCode": 0,
  -           "partition": 1,
  +           "partition": 0,
            },
          ],
          "topic": "test-topic-e9910243da64e6938ba1-30855-77acdeb3-2eb9-4659-ae00-d0bb5c5e0b2b",
        },
      ],

    101 |     })
    102 |
  > 103 |     expect(result).toEqual({
        |                    ^
    104 |       throttleTime: 0,
    105 |       topics: [
    106 |         {

    at Object.<anonymous> (src/broker/__tests__/txnOffsetCommit.spec.js:103:20)
        at runMicrotasks (<anonymous>)

FYI, we have jest-extended in the project, which has a toIncludeSameMembers matcher, which will match any array that contains the same elements, even if they are in a different order.
In this case, that would require you to rewrite the assertion a fair bit, so don't worry about it, but could be useful in the future.


feat(DDIDS-312): trap the focus inside the modal when tab or shift+ta…

feat(DDIDS-312): trap the focus inside the modal when tab or shift+tab used
Build Trap Focus as separate component

:tada: This PR is included in version 4.0.0-alpha.13 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0-alpha.71 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0-alpha.13 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0-alpha.6 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Parallelize Xilinx tests/move to pytest

[x] Parallelize Xilinx tests (done in PR #682)
[ ] Move to parallel pytest.

@definelicht Isn't this done?


UP sender transform existing data

This PR adds the ability to use Fhir Transform Schemas to make adjustments to fhir bundles. Most of the new functionality in FhirTransformer.kt is based off of similar functionality in FhirToHl7Converter.kt. The transform method allows for fhir bundles to be transformed based on a fhir transform schema. As demonstrated by the new tests, this supports the following:

updating existing properties based on a FHIR Path specified value
using conditional property updates
adding some properties to the bundle if they don't yet exist
using resource on a schema element to set the focus resource of the bundle
using the first of a list of values that has a valid non-empty value for property updates

Test Steps:

Since this is another intermediate step along the process of getting this functionality into the Universal Pipeline, at this point, this is only testable through the written tests. There are new tests in FhirTransformerTests.kt and FhirBundleUtilsTests.kt, and some existing tests were updated (mostly minor changes due to small updates to existing function signatures).

Changes

Added FhirTransformer.kt, based on FhirToHl7Converter.kt, to handle processing of FHIR transform schemas on a bundle
Common elements were extracted from FhirToHl7Converter.kt and placed into ConfigSchemaProcessor.kt. Part of this included making a distinction between getValue and getValueAsString, also changed params for getFocusResources. Updated tests accordingly.
Added FhirBundleUtils.kt to support updates using values of different fhir types
Refactored existing code to change FHIRTransformSchema to FhirTransformSchema and similar.

Checklist
Testing

[x] Tested locally?
[x] Ran ./prime test or ./gradlew testSmoke against local Docker ReportStream container?
[x] Added tests?

Process

[ ] Are there licensing issues with any new dependencies introduced?
[ ] Includes a summary of what a code reviewer should test/verify?
[ ] Updated the release notes?
[ ] Database changes are submitted as a separate PR?
[ ] DevOps team has been notified if PR requires ops support?

Linked Issues

Fixes #7246
Also relevant to #7247, since some (or maybe all) of that work was handled in these changes

Responded to a few of the comments, still need to go back and check the missing code coverage, I'll either add more tests or respond to those comments to say why I skipped code coverage of those. I can't remember off the top of my head how intentional some of those skips were, it might have just been aiming for parity with the existing tests for the Hl7toFhirConverter, but that's not a great reason to tolerate lower code coverage if it would be easy enough to cover. Will aim to respond later tonight or first thing tomorrow morning, thanks for the reviews so far!


Implements functionality of #40 (recipient autocomplete)

Further work to be done to improve appearance of dropdown.

Good work


KTLS

althought main idea of this project is performance, ktls and sendfile does not exist on node side, i do not think that setsocketopt for rx and tx which is two line of code should not be hard, please add them :(

uWS is older than KTLS, esp. if you think of any widespread kernel releases with support. If we want to add it, it should be as part of the io_uring feature which is also Linux only

freebsd has also ktls with async sendfile support, but it would be awesome to add that feature to boost performance of this library since it is for performance, thank you for information

We don't support Freebsd and KTLS is definitely not 2 lines of code. There is also little use for further optimization of a JS plugin that already has been measured to perform for small messages with TLS, 7x better than Node.js, where the majority of perf. loss is not from any low level feature but from the JS runtime itself.
Sure, if you plan to send huge files over HTTPS with uWS, it can perform with less than ideal performance but for anything small message (like websocket traffic) it performs very good.

Sure, if you plan to send huge files over HTTPS with uWS, it can perform with less than ideal performance but for anything small message (like websocket traffic) it performs very good.

You are right, there is a great performance in small messages now.
But from personal experience, projects are developing and often initially there are no requirements to send large responses, but sooner or later the business comes up with a functionality where you need to send a large response.
Now, you have to do it with Node.js streams, the speed is trash, you are not to blame for this, but the sendfile is really missing.

There's no plan to take on further scope - if Node.js sucks in perf. then move to Bun, they use sendfile.


Closes : #1

Updated validations.py python script.
Fixed the behavior of validate_user function in validations.py
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[x] Tests pass
[x] Appropriate changes to README are included in PR

los cambios ya estan hechos


bcrypt 4.0.0 and 4.0.1 missing

for sdist, setuptools_rust is missing: https://github.com/DavHau/pypi-deps-db/blob/99323880924a90acd689a4f23b56551d06d3f780/sdist-errors/d8.json#L927
and a wheel is not detected for python 3.8 though they are available https://pypi.org/project/bcrypt/4.0.1/#files

After a closer look, the wheels provided require at least python 3.6 but are also meant for anything above.

So I can confirm, bcrypt 4.0.1 is building on master & with the latest pypi-debs-db.