Is local inference actually feasible at the current state

I have been trying to get this working with Ollama, but I have been running into issues. First it was crashing due to bind_tools not being implemented in ChatOllama, but I was able to fix that by swapping the import from langchain_community.chat_models to the newly released langchain_ollama that has proper tool support.
However, after getting it working it quickly became apparent that none of the models that are reasonable to run on consumer hardware are able to actually comprehend the toolkit to produce any tool calls. I'm using an RTX 4090 (24 GB VRAM). Using the system memory for additional capacity, I'm able to run models like Llama 3.1:70b (131072 context length) with acceptable speed. I've additionally tried other tool-focused models such as mistral-nemo:12b-instruct-2407-q8_0, firefunction-v2 and llama3-groq-tool-use:70b.
I tried to strip down the tool set significantly, which eventually results in at least some valid calls, but would come with the loss of a lot of the functionality. Additionally, I'm uncertain if the LLM would lose its grasp on the remaining tools once the context starts getting filled up with the previous calls, the decompilation, etc.
I wonder if I'm missing something here and I'm getting worse performance from the LLM than I'm supposed to. Or is OpenAI just that far ahead the local alternatives in terms of performance, and it's just not feasible to use such a big toolkit?

I am working on some new features to improve performance on smaller models. I have some success with mixtral and other models larger than 70b. These models do not run well on my 3090, but they do run well on my MacBook.
I am working on a langgraph implementation that will remove the tool output from the context. The graph will try a plan -> research -> action -> summary flow. I hope I can use a small model and a large model for this to reduce compute and context size.


Decomposition of Copy button

As some browsers can only work with 'text' in terms of adding data to clipboard, Copy button should be decomposed into 3:

copy as Mol
copy as Ket
copy as image (already being implemented in the scope of https://github.com/epam/ketcher/issues/691)
in order to insist on choosing one type.

Copy as Mol should be main button. List of options should appear after clicking in the bottom right corner (example: Selection list of options)
This will also help not to waste resources on converting data into 3 types every time Copy button is used.

No prompt for user in IE when saving Simple Object with Copy (Ctrl+C) that coping does not work.
Steps:
Create Simple Object
Select created object
Click Copy button (Ctrl+C)
Actual result:
No prompt for user in IE when saving Simple Object with Copy (Ctrl+C) that coping does not work.
Expected result:
Some prompt - in Help module or alert window.


As a learner, I want to test my coding skills, so I can ensure I understand how to use IBM Quantum’s tools

Background
learners are currently able to submit coding exercises to the autograder. however, while scoring is supported it is currently not being used. scoring will need to supported and updated to properly meet assessment criteria.
Goal

Learners should be able to submit their solution to the autograder
After submitting a solution to the autograder, the autograder report a learner’s score for the problem

Acceptance criteria
No response
Out of scope
No response
Future of feature
No response
Resources
No response
Tasks
No response

This repository is no longer maintained. It has been superseded by IBM Quantum Learning.


Question

Is this correct in the API docs? It caught me out:
1 - Sinclair 2 (67890)
2 - Kempston 2
3 - Kempston 1

In particular, 2 being Kempston 2, and 3 being Kempston 1.

Yeah, that seems weird, but I decided to follow the pattern used in the own NextReg $05 (check out the manual), mainly because it would mean less code in the driver. Ideally, I would define a straightforward list and internally convert it, but that would mean less features in the driver and I definitely didn't want to exceed the 512-byte limit.
Another option would be simply ignore the NextReg $05 entirely and go with my own route but that wouldn't make sense for a driver as it would be incompatible with the peripheral settings in the firmware.

I think what you're doing makes sense - particularly under the 512 byte constraints. Useful to have context (for me certainly). Cheers again.


Still maintained?

Is evt-tls dead or will stuff happen?
Seems like it's bug-ridden, incomplete, and undocumented. But there doesn't seem to be SSL alternatives for libvu.

It is not dead for sure but slow but due to unavailability of work. Would appreciate any collaborator

Closing this as this is a query which, I believe, have been answered


Document developer experience when creating database taps

Hi there,
while working on GH-1, we've encountered some struggles to make the plugin work. The most probable reason is that we didn't work much with Singer/Meltano before (as a plugin developer), and that we didn't follow the upstream documentation closely enough, effectively boiling down to plain ignorance ;]. Still, we wanted to write down where we have been running into obstacles, to have the chance to improve the documentation.
Please find the report and corresponding thoughts below. Saying all that, after you know how things are connected, I want to say the Singer ecosystem is amazing, and the Meltano layer adds the right convenience abstractions to consume it better. Thanks to all who make it better each day. 💯
With kind regards,
Andreas.

I struggled very hard to discover the corresponding mechanisms around "stream/table selection" as a newcomer/developer.
Specifically, when developing the tap, even when using tap-postgres as a blueprint, I found it hard to connect the dots regarding entity selection rules and the select extra of Meltano fame, because they naturally don't have any representation within the Singer SDK. This may revolve around topics discussed at https://github.com/meltano/sdk/discussions/1652, but also naturally, those are topics you are being discussed by the system architects, and I only have been able to discover them much later when starting off not knowing anything about those.
As a newcomer developer, while having been so amazed that the SQLAlchemy-based reflection machinery thoroughly discovered and reflected all the system tables of CrateDB, all of them have been deselected, and I haven't been able to figure out how to select them: First, folowing the Singer way, I discovered that using a catalog would be the right way, and I edited deeply nested JSON structures, trying to get data flowing out of our sys.summits table. Eventually, I discovered the entity/stream selection service added to the baseline Singer implementations on behalf of Meltano, but still it did not work: All the streams have been deselected, and you can imagine my frustration because, well, you see the light at the end of the tunnel, but there seems to be an invisible barrier grid between you and the tunnel exit.
In a tinge of despair, I already started to work around it somehow by mimicking the select: attribute into our tap implementation, hooking it into settings.select_beta, only to finally discover that I needed to add the capabilities: section to the Meltano project definition, to make the select: thing work without futher ado. You can imagine my relief at this point to finally have discovered one of the holy grails of Meltano.  Still, I wanted to share that story with you, and I hope you can appreciate it.
Just revisiting the documentation about Creating a Custom Extractor, also admitting I didn't follow it, I think I also got confused within learning about the difference of config: vs. settings:, and that select: is a completely different thing, not mentioned on that page at all. Maybe it is special for database taps?

Well, it is all right there:

Plugins
Plugin extras
How to use: Plugin extras
Capabilities

However, I don't know why, but I haven't been able to connect the dots between those concepts sitting on top of Singer. One reason might have been that I studied the documentation wrongly, and that I tried to discover something about "Meltano Services" (apparently the underlying machinery for those plugins/extras), which I had picked up from the code base.
So, I think everything is excellently documented from a user's perspective, and it's only me who took the wrong "bottom up" approach. 🤦

We converged our report into Learning Singer » Creating a database tap.


feat(TDI-40977): Apply proxy feature for Salesforce

What is the current behavior? (You can also link to an open issue here)
What is the new behavior?
Please check if the PR fulfills these requirements

[ ] The commit message follows Talend standard
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features) ?
[ ] The code coverage on new code >75%
[ ] The new code does not introduce new technical issues (sonar / eslint)

What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[x] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:

Pull request test result: failure :x:

Failing because of talend-proxy:jar not deployed in nexus yet

Pull request test result: failure :x:

Pull request test result: failure :x:

Pull request test result: success :star:
Sonar results


synchronize rook/ceph/ceph-csi configuration across all clusters

The pillan configuration, which already included s3 & nfs, was copied to ruka for development and testing/updates. Rook was updated to 1.9.9, ceph to 16.2.10, and ceph-csi to 3.6.2.  Recent rook releases now properly support managing nfs with ceph >= 16.2.7. Also note that rook 1.10 will drop support for ceph 15.x and all clusters need to be migrated to ceph >= 16 in order to update rook in the future. The changes developed on ruka were then copied to the other clusters as a single commit.
Other notable changes are:

ceph pool quotas set on CRD resources
most ceph related pods have resources.limits set
the ingress resource for the ceph dashboard is now managed by the rook-ceph-cluster chart

I'm converting this to a draft as I've discovered I need to make changes to the rook-ceph-cluster chart values.


How to calculate fee and transferring USDT trc20 to another wallet?

Hello!
I have a problem, after call the estimateEnergy, I call the method triggerSmartContract in the options of which I set the feeLimit.
I expect triggerSmartContract to return the object transaction, but it ends up returning the same as estimateEnergy
      const estimateEnergy = await tronWeb.transactionBuilder.estimateEnergy(addressContractUSDT_Test, functionSelector, options, parameter, addrTRON);
      console.log('estimateEnergy >> ', estimateEnergy);
      const listTokens = await tronWeb.trx.getChainParameters();
      const priceFee = _.find(listTokens, { 'key': 'getEnergyFee' })?.value;
      const feeLimit = estimateEnergy.energy_required * priceFee  || 100000000;
      options.feeLimit = feeLimit;
      const tx = await tronWeb.transactionBuilder.triggerSmartContract(addressContractUSDT_Test, functionSelector, options, parameter, addrTRON);
      console.log('tx >> ', tx);

  LOGS:
   LOG  estimateEnergy >>  {"energy_required": 15109, "result": {"result": true}}
   LOG  priceFee >>  420
   LOG  tx >>  {"energy_required": 15109, "result": {"result": true}}

The first time you call estimateEnergy, TronWeb will set estimateEnergy prop to options parameter. Thus, the second time you call triggerSmartContract, options still has a estimateEnergy prop which has been set to true. You'll have to use delete options.estimateEnergy before you call triggerSmartContract.

Thanks!

The first time you call estimateEnergy, TronWeb will set estimateEnergy prop to options parameter. Thus, the second time you call triggerSmartContract, options still has a estimateEnergy prop which has been set to true. You'll have to use delete options.estimateEnergy before you call triggerSmartContract.

Thanks!


moveit_opw_kinematics_plugin: 0.3.1-2 in 'noetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository moveit_opw_kinematics_plugin to 0.3.1-2:

upstream repository: https://github.com/JeroenDM/moveit_opw_kinematics_plugin.git
release repository: https://github.com/JeroenDM/moveit_opw_kinematics_plugin-release.git
distro file: noetic/distribution.yaml
bloom version: 0.10.7
previous version for package: null

moveit_opw_kinematics_plugin
* First release in noetic.
* update to new opw_kinematics API (with std::array)
* Add opw_kinematics dependency to package.xml and CMakeLists.txt.
* Remove opw_kinematics submodule.
* Change moveit_resources to more specific moveit_resources_fanuc_moveit_config
* Minor changes:
  - It's not a service based IK solver.
  - Parameters don't always come from 'kinematics.yaml'.
* Contributors: JeroenDM, gavanderhoorn.

Holding for Noetic sync


Add Backoff::TimeoutUntilNextAttempt

Per discussion with @markdroth , this requires a cross-language agreement about backoff behavior: whether it's interpreted as an absolute frequency or as a wait between one event and another. Closing this PR, we'll circle back to an implementation when that's decided.


[Discussion] items vs. children for components that render lists

Just chatted with @blackswanny and wanted to get some additional clarification/alignment on whether we should always prefer to pass-thru and render children for components that end up rendering a list, or use something like a items attribute and take configurations.
For example, right now, the RadioGroup component assumes that the users will be rendering their own children complete, so in order for you to render a RadioGroup, the simplest way is:
import {RadioGroup, StyledRadio} from '@uber/base-ui';

<RadioGroup {...allProps}>
  <StyledRadio value="1">First</StyledRadio>
  <StyledRadio value="2">Second</StyledRadio>
  <StyledRadio value="3">Third</StyledRadio>
</RadioGroup>

Whereas for Menu the current simple usage is this
import {StatefulMenu} from '@uber/base-ui';

const items = [
  {label: 'my-item'},
  {label: 'my-item2'},
];

<StatefulMenu
  items={items}
  getItemLabel={(item) => item.label}
  ... />

Is there a need to unify approaches here (i.e. should we not use items attributes and instead always expect users to render children manually? I see how that would be more idiomatic React, but my concerns with it are:

Isn't explicitly rendering your own children what StatefulContainer is for, via render props? With the RadioGroup approach, what's the difference between using RadioGroup vs. StatefulRadioGroupContainer?
It isn't clear how/what you can override via the overrides prop and what you can override directly if you just pass in your own children.

Thoughts? @schnerd @nadiia

Is there a need to unify approaches here
Consistency is nice but I think it's fine to be inconsistent when there's a good reason to do so.

I'd vote for an items array here. The biggest reason is that autocomplete selects can often have hundreds or thousands of items. Enumerating all those as an <Option> is a waste of cpu/mem resources – when internally the select could just choose to render the first 20 rows or use something like react-virtualized / react-window for windowed rendering. This is very different than a RadioGroup, which probably only has 10 children at most.
react-select also uses an items array. There's a reason its so popular, I think we should probably try to align with the paradigms they use where possible, rather than reinventing the wheel.

Our select should also support async results, as you often have too many options and need to filter results using elasticserach or something similar. react-select implements this as , but we could also just accept items as () => Promise<Option[]> (a function that returns a promise resolving to the options).
This behavior seems much easier to implement using an items/options prop rather than passing options as children.

Not sure whether this would help, but from my experience:
children
Use children if you for sure won't manipulate it at all.
As in, you won't traverse through the children and do something with it.
Or even pass in magic props by React.cloneElement for each children, etc.
As long as all you do is just to render it, then it's fine.
items prop
This is the most common one that I've seen, and it's actually more "powerful" than using children.
For each element, you can do something like:
const items = [
  {itemComponent: (/* pass some extra props here from base-ui component, such as onClick, etc */) => {
    /*
    they can return either <StyledRadio> or whatever they want as
    long as they understand that if it's a radio group, it needs to be an input type radio, etc...
    */
  }}
];

You could actually do that with React.cloneElement with each element of children, but this way is a lot safer.

I'd prefer using items prop :)

I would incline to itemsarray prop, that will also be a better approach in the case of nested items, and give more flexibility for any additional manipulations with it. @schnerd brought up a very good reason for lazy loading of the items.

Thanks for the inputs!
I agree with @schnerd's point about virtualizing the list, which is easier than with an items array. Just for clarifications, this is for the Menu component, which we will re-use inside Select but could also be used by itself (not sure if that changes anyone's opinion).
The point about length and use case is also valid. I'm happy to agree on the diverging pattern here!

Ok, lets do items attribute.
But want to remind that children is just a concept, and the same attribute of props as anything else. I googled. No evidence that children affects performance more than attribute. It has only some defaulted behavior, which we amend in many of our components already. If children are not provided as a part of markup, they will not be rendered. So far children work with async rerendering of them the same way as items in Select component
So we leave items in Menu, but do you want the same for Select component?
From: Anh Mai<EMAIL_ADDRESS>Reply-To: uber-web/baseui<EMAIL_ADDRESS>Date: Tuesday, August 14, 2018 at 11:31 PM
To: uber-web/baseui<EMAIL_ADDRESS>Cc: Oleg Gomozov<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [uber-web/baseui] [Discussion] items vs. children for components that render lists (#129)
Thanks for the inputs!
I agree with @schnerd's point about virtualizing the list, which is easier than with an items array. Just for clarifications, this is for the Menu component, which we will re-use inside Select but could also be used by itself (not sure if that changes anyone's opinion).
The point about length and use case is also valid. I'm happy to agree on the diverging pattern here!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

If the assumption is that Select will use Menu, I think we should keep the interface similar, so I'd vote for going with items there too. The discussions here at least seem to have been based on the Select assumption as well?

Yeah, I assumed this discussion was about Select. I think we should use an options array in both.
I also kind of like options better than items, might map more closely to existing  naming. ¯_(ツ)_/¯

But want to remind that children is just a concept, and the same attribute of props as anything else. I googled. No evidence that children affects performance more than attribute. It has only some defaulted behavior, which we amend in many of our components already. If children are not provided as a part of markup, they will not be rendered. So far children work with async rerendering of them the same way as items in Select component

you're right that children is essentially just a prop, but you're still instantiating Option classes for each item, which react will have to chug through when doing virtual dom diffs (check keys to see if things have been re-ordered, etc.). Diffing a single Select element with an items array should in theory be faster than diffing a Select with hundreds or thousands of children.
Yes, I think we want the same for Select.

I've got no opinion on specific prop names, happy to change items to options. You're right that it probably is more idiomatic.

Been giving this some more thoughts as I try to expand Menu to cover all of these:

It might be that users want to mix & match between a simple string-only list item and the profile item in a single list. With the way it is right now, we're locked to only one kind of list item (either all simple or all profile).
I can see how to let users mix & match with the children approach, but less clear with the items approach. @ardok's comment is one solution to this, but do we want to overload items with a ton of options? If we do, would we need to have helpers to create items so we can have proper type checking for each item?


Add .terraform.lock.hcl to .gitignore

.terraform.lock.hcl was added in terraform 0.14 and should be ignored.
https://www.terraform.io/docs/language/dependency-lock.html

Thanks for the PR! 🚀✅ Lint checks have passed.


Minimum rotation required to get the same string

Steps implemented -

Initialize result = 0 (Here result is count of rotations)
Take a temporary string equals to original string concatenated with itself.
Now take the substring of temporary string of size same as original string starting from second character (or index 1).
Increase the count.
Check whether the substring becomes equal to original string. If yes, then break the loop. Else go to step 2 and repeat it from the next index.

Ex. -
Input : s = "name"
Output : 4
Input : s = "aaaa"
Output : 1

Hey unfortunately I haven't gotten into adding a format yet, PR looks fine but trying to maintain a format on the PR and codebase so can you just follow this.
naming convention of file:  problem name (inside the folder of the corresponding language and concept)
PR format:
steps and example looks good
add a screenshot of ur answer submission percentile (make sure >70% people's solution in terms of runtime and complies with the space as per question)
+any extra info


Koa 2 and async/await in node

Hi,
Thanks for this great repo!
Could you upgrade koa to Koa 2 to use async/await in node?
Thanks.

Hi @ngduc Koa 2 is still in alpha. However, you could send in a Pull Request if you want to help us prepare for the final release.


SAP Cloud Platform Cloud Connector setup for secure on-premise connectivity

I am trying to setup SAP Cloud connector.
The documentation informs me to specify Landscape host, but in my installation of the cloud connector I don't see that field.
Furthermore it is not clear to me what I have to specify in the field Subaccount.

The UI of the Cloud Connector changed, apologies that this is not yet reflected in this tutorial.
The following tutorial describes how to connect your Cloud Connector with SAP Cloud Platform and with your ABAP system in more detail:
https://developers.sap.com/tutorials/cp-connectivity-create-secure-tunnel.html
We are currently re-organizing the Cloud Connector tutorials and will probably soon remove the one that still refers to an old Cloud Connector version.

@WilbertKarremans : Did this solve your issue? If so I'd like to close this issue. - Thanks

Yes, please close it. Many thanks!
Wilbert
From: Jens Haley<EMAIL_ADDRESS>Sent: Wednesday, 20 February 2019 15:15
To: SAPDocuments/Tutorials<EMAIL_ADDRESS>Cc: Wilbert Karremans<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [SAPDocuments/Tutorials] SAP Cloud Platform Cloud Connector setup for secure on-premise connectivity (#2834)
@WilbertKarremanshttps://github.com/WilbertKarremans : Did this solve your issue? If so I'd like to close this issue. - Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/SAPDocuments/Tutorials/issues/2834#issuecomment-465592119, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AXvwoBwoFp53fOvjpjK2RdFZc8hDoSgPks5vPVhQgaJpZM4Y8Y5l.

@WilbertKarremans For next time, if the issue you opened is resolved, you can close it yourself. Thanks for the feedback.


Error: No available formula with the name ...

[x] Ran brew update and retried your prior step?
[x] Ran brew doctor, fixed as many issues as possible and retried your prior step?
[x] If you're seeing permission errors tried running sudo chown -R $(whoami) $(brew --prefix)?

Bug reports:
Hi,
Every time I try to install something, I receive:
Error: No available formula with the name "wget"
==> Searching for similarly named formulae...
Error: No similarly named formulae found.
==> Searching taps...
Error: No formulae found in taps.
Please help me figure out what is the cause of this issue.

Sorry but you have not followed the requested steps on the Troubleshooting page
Please follow (all of) these steps and post the information here so we can help you with your problem.
Thanks!

No probs,
176-67-23-67:~ roman$ brew gist-logs wget
Error: No available formula with the name "wget"
176-67-23-67:~ roman$ brew update
Already up-to-date.
176-67-23-67:~ roman$ brew update
Already up-to-date.
176-67-23-67:~ roman$ brew doctor
Your system is ready to brew.
176-67-23-67:~ roman$ brew gist-logs wget
Error: No available formula with the name "wget"
OS X El Capitan
Version 10.11.6

Can I see your brew config output?

Sure
HOMEBREW_VERSION: 1.0.3-31-gb432f8e
ORIGIN: https://github.com/Homebrew/brew.git
HEAD: b432f8e9cb2d03c8f1d7a65b9d6df2e04b3d37a7
Last commit: 33 minutes ago
Core tap ORIGIN: https://github.com/Homebrew/brew.git
Core tap HEAD: b432f8e9cb2d03c8f1d7a65b9d6df2e04b3d37a7
Core tap last commit: 33 minutes ago
HOMEBREW_PREFIX: /usr/local
HOMEBREW_REPOSITORY: /usr/local/Homebrew
HOMEBREW_CELLAR: /usr/local/Cellar
HOMEBREW_BOTTLE_DOMAIN: https://homebrew.bintray.com
CPU: quad-core 64-bit ivybridge
Homebrew Ruby: 2.0.0-p648
Clang: 8.0 build 800
Git: 2.7.1 => /usr/local/bin/git
Perl: /usr/bin/perl
Python: /usr/bin/python
Ruby: /usr/bin/ruby => /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby
Java: 1.8.0_91
macOS: 10.11.6-x86_64
Xcode: 8.0
CLT: <IP_ADDRESS>.1.1461711523
X11: N/A

Also I forgot to Check that Command Line Tools for Xcode (CLT) and/or Xcode are up to date:
gcc --version
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1
Apple LLVM version 8.0.0 (clang-800.0.38)
Target: x86_64-apple-darwin15.6.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

Core tap ORIGIN: https://github.com/Homebrew/brew.git

This is the issue. Run rm -rf /usr/local/Library/Homebrew/Taps/homebrew/homebrew-core and then try to reinstall.

@MikeMcQuaid thank you! My problem is solved.

Glad to hear it!


alike in crucial ways

Awesome book.  Eagerly looking forward to chapter 2 and generators!

Hey, also, as an option, it's possible to edit a GitHub repo title and put the link to the book in the "description".

Awesome book. Eagerly looking forward to chapter 2 and generators!

Thanks! Hope I can find some time during Christmas break :pray:

Hey, also, as an option, it's possible to edit a GitHub repo title and put the link to the book in the "description".

Yep, done.


DOCS-910: Updating proxy and console configurations

Summary
Closes #910
So NGINX is not my strong suit, but enough of our users use it, so here we go.
https://github.com/minio/console/pull/2818 <- added better support to subpath behaviors
I also recall there being an issue related to how the upstream blocks were configured, but I can't find it now. Fixed that while I was here.
Finally, documented MINIO_DOMAINS, but did not fully test it as I don't have the stretch to set up apps and poke around that behavior.
Local environment

Latest Stable NGINX on CentOS Stream
Disable SELinux, it only makes your life harder
MinIO latest stable

Set /etc/hosts to have the preferred main hostname for the server on both the VM and local machine
Set nginx to proxy to hostname/ and hostname/minio/ui for the S3 API and Console API respectively
Set MINIO_SERVER_URL and MINIO_BROWSER_REDIRECT_URL based on the new proxy URLs
Tested both Console and mc, was able to connect, create a bucket, copy an object, generate a presigned URL, and wget the object using that URL.
Staged
http://<IP_ADDRESS>:9000/staging/DOCS-910/linux/reference/minio-server/minio-server.html#envvar.MINIO_DOMAIN
http://<IP_ADDRESS>:9000/staging/DOCS-910/linux/reference/minio-server/minio-server.html#envvar.MINIO_BROWSER_REDIRECT_URL
http://<IP_ADDRESS>:9000/staging/DOCS-910/linux/reference/minio-server/minio-server.html#envvar.MINIO_SERVER_URL
http://<IP_ADDRESS>:9000/staging/DOCS-910/linux/integrations/setup-nginx-proxy-with-minio.html

Ping to engineers, I'm going to merge this EoD absent any other commentary.


Analysis of SimplifiedExpr class

There is a lack of documentation in scope of the SimplifiedExpr class either in all method.
https://github.com/bogumilchilinski/dynpy/blob/e329156cae2d4c986aeb10b6cf73cf4ad2c0766f/solvers/nonlinear.py#L34
Analyze particular methods flow and prepare the documentation. The new module for solver's tools could be consider. Currently, it is in nonlinear.py. Any suggestions are really much appreciated xD.

https://cocalc.com/projects/f5eacfa1-ad37-41af-beea-da7216cf5881/files/Sandbox/Szymon Kozłowski/Tasks/Simplified_Expresion_documentation.ipynb
Ready to check


Cache reference assemblies between tests to improve performance

The testing framework does a bunch of heavy lifting to resolve references for set of ReferenceAssemblies, including potentially running the NuGet client to download packages. This class caches the ReferenceAssemblies class (which is thread-safe), so that package resolution only happens once for a given configuration.
The is the same approach taken by https://github.com/dotnet/roslyn-analyzers/blob/4d5fd9da36d64d4c3370b8813122e226844fc6ed/src/Test.Utilities/AdditionalMetadataReferences.cs.
This cuts test time from ~40 seconds to ~20 seconds on my machine.

Nice!

I also opened a PR to update the test docs to make this clearer: https://github.com/dotnet/roslyn-sdk/pull/1160

This addresses part of #64.


Make unlock behavior configurable

Hi @patrickhilker ,
sorry for the PR spam, but I figured it would be nice, if the previous unlock behavior could be restored optionally (e.g. for HomeKit locks), so I added a config flag which controls whether the unlock pulls the latch or not (configurable only in integration settings)

No problem - thank you for your work!


Fix sig

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[x] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

fixes #3019

@MSSedusch

Can you fix the error in Github checks?
If you expect the change to take effect, please update history notes and version number.

I'll have a look at the checks. @qwordy what do you mean by history notes? Can you send me a link to the file I need to update?

@qwordy GitHub checks are green now and I updated the AEM version

@MSSedusch Example file: src/blueprint/HISTORY.rst
I find aem does not have HISTORY.rst. No problem. If you have time, you can add one. Great software always has release notes. Do you want to merge now?

@qwordy  I added the history. Thanks


Radiant::Cache.clear has no effect when using Memcache

I'm running radiant on heroku cedar with memcache. Radiant::Cache.clear has no effect and thus when saving a page an outdated version is saved as the cache isn’t cleared. This is my cache config
  require 'active_support/cache/dalli_store23'
  config.cache_store = :dalli_store

  config.middleware.use ::Radiant::Cache,
    :metastore => "memcached://#{ENV['MEMCACHE_SERVERS']}/meta",
    :entitystore => "memcached://#{ENV['MEMCACHE_SERVERS']}/body"

I'm using the following monkey patch as a workaround
  module ::Radiant::Cache
    def self.clear
      Rails.cache.clear
    end
  end


Cannot find name 'Promise'

Hi,
it's amazing library, which can help me in my project. Unfortunately, I've problem with correct compilation by tsc.
I receive this error:
node_modules/routing-controllers/middleware/MiddlewareInterface.d.ts(14,60): error TS2304: Cannot find name 'Promise'.
Is it problem with this lib or it's my problem with incorrect configuration ?

As long as your version of Node supports most ES6 features, you can easily solve this by changing TypeScript's compilation target to es6 in your tsconfig.json: {"compilerOptions": {"target": "es6"}}.

@migace you can follow JD-Robbs, or if you still want to use es5 target you can simply install es6-shim throw the typings, .e.g typings install dt~es6-shim --save --global

Hi guys,
I came back from work and tried your tips... It's work. Thank very much for interesting and so fast response. It's nice and I am very happy. It's power of Open Source 👍 Thanks again :)


Clients can see questions without a valid code, if their frontend is modified.

If a client modifies the frontend code, it can gain access to the questions and their answers. The client is not able to answer the question however. Is this a problem?

How can you gain access to the questions and answer if you do not have a valid access code?

Because the code:
"var es = new EventSource("/sse");
es.onmessage = function (event) {...}"
can be injected to 'index.ejs' and used to establish a SSE connection, even though the client hasn't passed the login step. The client will then get information regarding the newly created questions sent via the SSE connection, since there is no authentication before the connection is established.

I see. I think it is bad that we supply more information than the user should have access too. Upon connection there should be some sort of handshaking validating the accessCode before sending out a question.

Yes, it's not optimal. It won't however be accessible to users who don't have good programming knowledge. In previous versions there existed a handshake, but it was removed since the accessCode was sent via a query string, which is considered bad practise. We could investigate if there is another way to perform the handshake that is much more secure.

I should point out that they can't access the given answers (what people have voted on) but the available answers to choose among.

Why not just encapsulate it away from the global scope so the methods no longer are accessible?

Can you provide a code example to clarify what you mean?

http://stackoverflow.com/a/2421949/823725

The problem isn't that the backend has public methods, it's that the code used in vote.ejs can be injected into the index.ejs file. This would allow a user to establish the SSE connection before passing the accessCode validation step. So the backend need some handshake logic based on the accessCode before a connection is created.

I'd say this is not an issue, anyone on a meeting / reading the irc can know the question as it is.


Ask to confirm the export when the tarball already exists in the directory

If I already downloaded the backup of volume yesterday and download it today, the tarball may already exist. I wish it asked me to either replace it, keep it and use a  (1) suffix or cancel as MacOS does maybe.

Hi! Can I work on this issue?

@VoidCupboard Sure!

Thanks :3

I'm sorry for not being able to fix this issue since I am using an Arch-based distro and Docker Desktop seems not to work. I will try to fix it (I have been trying for some time but have no hope) and make a PR if possible. By the time anyone else can work on this issue

@felipecruz91 I would love to give it a shot.


Variable lookups with bracket lookups don't work on dashboards

To reproduce try viewing
bucket = v["bucket"]

from(bucket: bucket)
  |> range(start: v.timeRangeStart, stop: v.timeRangeStop)

in a dashboard. While the query builder the query will execute just fine.
The root cause here is that the variable matcher we have today only detects variables described by v.<varname> and do not catch v["<varname>"]

postponing this one to wait for better support by the flux wasm in this issue
https://github.com/influxdata/influxdb/issues/18834


custom logformatter

How does one use multiple formatters: one for the xcode debug window (as shown below), another to go into a log file, a third to go in the ASL log file?
Here is a sample custom log formatter for anyone who is interested.
import Foundation
import CleanroomLogger

public struct LogFormatterTTY : LogFormatter
{
    private static let timestampFormatter: NSDateFormatter = {
        let fmt = NSDateFormatter()
        fmt.dateFormat = "hh:mm:ss.SSS"
        return fmt
    }()
    public static func stringRepresentationOfTimestamp(timestamp: NSDate)
        -> String
    {
        return timestampFormatter.stringFromDate(timestamp)
    }

    public static func stringRepresentationOfSeverity(severity: LogSeverity)
        -> String
    {
        var severityTag = severity.printableValueName.uppercaseString
        severityTag = severityTag.substringToIndex(severityTag.startIndex.advancedBy(1))

        return severityTag
    }
    public static func formatLogMessageWithSeverity(severity: String, caller: String, message: String, timestamp: String?, threadID: String?)
        -> String
    {
        var fmt = "\(severity) "
        if let timestamp = timestamp {
            fmt += "\(timestamp) "
        }
//        if let threadID = threadID {
//            fmt += "\(threadID) "
//        }
        fmt += "\(caller) \(message)"
        return fmt
    }
    public static func stringRepresentationForCallingFile(filePath: String, line: Int, function: String)
        -> String
    {
        let filename = NSURL(fileURLWithPath: filePath).URLByDeletingPathExtension?.lastPathComponent ?? "(unknown)"

        return "\(filename).\(function):\(line)"
    }

    public func formatLogEntry(entry: CleanroomLogger.LogEntry) -> String?
    {
        let severity = LogFormatterTTY.stringRepresentationOfSeverity(entry.severity)
        let caller = LogFormatterTTY.stringRepresentationForCallingFile(entry.callingFilePath, line: entry.callingFileLine, function: entry.callingFunction)
        var message = DefaultLogFormatter.stringRepresentationForPayload(entry)

        var timestamp: String?
            timestamp = LogFormatterTTY.stringRepresentationOfTimestamp(entry.timestamp)

        var threadID: String?
            threadID = DefaultLogFormatter.stringRepresentationOfThreadID(entry.callingThreadID)

        if message == entry.callingFunction {
            message = ""
        }

        return LogFormatterTTY.formatLogMessageWithSeverity(severity, caller: caller, message: message, timestamp: timestamp, threadID: threadID)
    }
}

public struct LogConfigurationTTY : LogConfiguration
{
    /** The minimum `LogSeverity` supported by the configuration. */
    public let minimumSeverity: LogSeverity

    /** The list of `LogFilter`s to be used for filtering log messages. */
    public let filters: [LogFilter]

    /** The list of `LogRecorder`s to be used for recording messages to the
     underlying logging facility. */
    public let recorders: [LogRecorder]

    /** A flag indicating when synchronous mode should be used for the
     configuration. */
    public let synchronousMode: Bool

    public init(minimumSeverity : LogSeverity = .Info){
        self.minimumSeverity = minimumSeverity
        self.filters = []
        self.recorders = [ASLLogRecorder(formatters: [LogFormatterTTY()])]
        self.synchronousMode = false
    }
}

Hi Navi,
I've added the relevant sample code to a comment on your other open ticket, and will close this one.
E.


[T4A3][F12-A4]Wang Si Qi

@coyotestarrkwsq
Some comments added. Please ack & close the PR after reading comments.


fix: remove auto self-contained build for .NET 8 beanstalk deployments

Issue #, if available:
DOTNET-7212
Description of changes:
In order to support deploying .NET8 apps on Beanstalk prior to Beanstalk adding .NET8 support, we had to force .NET8 apps to be self-contained in order to allow for Beanstalk support. Beanstalk has since added .NET8 support, so this PR removes this restriction to allow .NET8 apps to be deployed to Beanstalk not as self-contained apps.
This PR also improves the sorting of Beanstalk platforms to show the latest .NET versions first.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Add a platform version check for the version that added .NET8. If a user is redeploying we shouldn't break them.


Cheatsheet for Vim

Thank you so much! I'm currently far away from my computer. I will merge tonight :-)

Thank you again!

Hello Lucifer, your cheatsheet is trending! :)
https://www.reddit.com/r/vim/comments/7vkenp/vim_cheatsheet_everything_you_should_know_in_one/

Happy to contribute, Julien
I am Prateek,by the way
On Tue, Feb 6, 2018 at 5:02 PM, Julien Le Coupanec<EMAIL_ADDRESS>
wrote:

Hello Lucifer, your cheatsheet is trending! :)
https://www.reddit.com/r/vim/comments/7vkenp/vim_
cheatsheet_everything_you_should_know_in_one/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/LeCoupa/awesome-cheatsheets/pull/5#issuecomment-363395422,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AcBh6AjwEDRKJYbehsZMm1rBYqostYhMks5tSDhFgaJpZM4R5eWB
.

Nice to meet you :-)


Third Release (v4.2.0)

Release the code with all the completed and tested search functionalities.

[ ] Ensure all searches are implemented and tested.
[ ] Create and publish version v4.2.0-release.


flarectl: Move api invocation to checkEnv()

Since 586e5a5 cloudflare.New() will error if the API email and key are
not defined. Since flarectl was instantiating the API object at the
start, this meant that flarectl would not operate at all without having
the environment variables defined.
This moves the API object instantiation to checkEnv() so that, e.g.
ips and --help will still work. All other functions already call
checkEnv().
Refs #73

LGTM


example query using this API

Hello again
This API is very useful, but I seem to have difficulties using the queries that infusionSoft provides in their documentation.
If I write something like:
ifs.DataService.query('LeadSource', 1000, 1, "Id => [1,2,3,4]", leadSourceFields).then(leadSources => {
    console.log(leadSources);
    return leadSources;
}).catch(e => { console.log(e) });

Id => [1,2,3,4], one of the example queries copied from IFS's documentation, just seems to cause the program to crash with this: Error: XML-RPC fault: No method matching arguments: java.lang.String
In their documentation they say the query is of type "struct" but how do I declare that type inside javascript?
This really is a low priority thing but I'd appreciate the insight
Thank you

I was able to make an example with some trial and error, basically Javascript Object == Java Struct
Everything in the IFS API is Base 0
and MODULO is the wildcard character for some unknown reason

// Create an ifs object for all XML-RPC transactions.
var ifs = new api.DataContext('{IFSTOKEN}');

// Lead Source potential fields
var leadSourceFields = [
    "Id",
    "Name",
    "Vendor",
    "Status",
    "StartDate",
    "Message",
    "Medium",
    "LeadSourceCategoryId",
    "EndDate",
    "Description",
    "CostPerLead"
];

ifs.DataService.query('LeadSource', 1000, 0, {"Id" : "%"}, leadSourceFields).then(leadSources => {
    console.log(leadSources);
    return leadSources;
}).catch(e => { console.log(e) });```


Aboutsection

Added more details, changed the about section from the README to information about our tool. @YesIfwRONG to make some minor changes before this branch can be merged.

Reminder to not push package lock unless you're updating the packages, it is causing netlify build to fail

A new PR has been made for these changes.


When only one chip target is available for an app, select it automatically

...to save the user the extra click.

@igrr, PR #43 may address this enhancement 😄


Update sys-dm-db-resource-stats-azure-sql-database.md

@fixersatoh : Thanks for your contribution to the SQL documentation! The author, @CarlRabeler, has been notified to review your proposed change.

#sign-off

Only the author of the article can use the sign off comment to add the ready-to-merge label.

@craigg-msft why am I getting this notice that only the author can sign off - as I am the author

Thank you @fixersatoh and @CarlRabeler


Http2 performance issue with firefox

Title: * Http2 performance issue*
Description:
When we upload files with Firefox it took 7 times more than in Chrome browser (7s compared to 1s).
We are using H2 protocol.
When we change the setting network.buffer.cache.size in about:config, our upload time is reduced to 1 second.
IMO the network size is part of flow control implemented in http2 (https://developers.google.com/web/fundamentals/performance/http2#flow_control)
In server side we have set following value:
(https://httpwg.org/specs/rfc7540.html#rfc.section.6.9.2)
Initial Flow-Control Window Size: 104857500
Connection-level flow-control window: 104857500
Actual results:
When we upload files with Firefox it took 7 times more than in Chrome browser (7s compared to 1s).
Expected results:
Same upload time compared to chrome.
[optional Relevant Links:]
Repro steps:
Try to upload a file with firefox with http2
Admin and Stats Output:
/stats: https://gist.github.com/jsenon/8552f40cafa0a25bc9e12b126b27b652
/server_info:
{
 "version": "4cd27af28f54d6da1a487aa756256eb5393fff7d/1.12.0/Clean/RELEASE/BoringSSL",
 "state": "LIVE",
 "hot_restart_version": "11.104",
 "command_line_options": {
  "base_id": "0",
  "concurrency": 4,
  "config_path": "/etc/istio/proxy/envoy-rev0.json",
  "config_yaml": "",
  "allow_unknown_static_fields": false,
  "reject_unknown_dynamic_fields": false,
  "admin_address_path": "",
  "local_address_ip_version": "v4",
  "log_level": "warning",
  "component_log_level": "misc:error",
  "log_format": "[Envoy (Epoch 0)] [%Y-%m-%d %T.%e][%t][%l][%n] %v",
  "log_path": "",
  "service_cluster": "istio-ingressgateway",
  "service_node": "router~<IP_ADDRESS>~istio-ingressgateway-85f6c47d95-gsqrs.istio-system~istio-system.svc.cluster.local",
  "service_zone": "",
  "mode": "Serve",
  "max_stats": "0",
  "max_obj_name_len": "0",
  "disable_hot_restart": false,
  "enable_mutex_tracing": false,
  "restart_epoch": 0,
  "cpuset_threads": false,
  "file_flush_interval": "10s",
  "drain_time": "45s",
  "parent_shutdown_time": "60s"
 },
 "uptime_current_epoch": "411585s",
 "uptime_all_epochs": "411585s"
}

pcap link https://send.firefox.com/download/004e0e9f4ea9ca91/#ad9EdZ0Ijt18Dw5e7-6P3g
Config:
Flow: Client <-> AWS Classical LB <-> Istio/Envoy ingress gateway <-> upstreamsvc uploader
Configured with Istio, and add following envoy filter:
apiVersion: networking.istio.io/v1alpha3
kind: EnvoyFilter
metadata:
  name: h2-control
spec:
  configPatches:
  - applyTo: NETWORK_FILTER
    match:
      listener:
        filterChain:
          filter:
            name: "envoy.http_connection_manager"
    patch:
      operation: MERGE
      value:
        typed_config:
          "@type": "type.googleapis.com/envoy.config.filter.network.http_connection_manager.v2.HttpConnectionManager"
          http2_protocol_options:
            initial_stream_window_size: 524288000
            initial_connection_window_size: 524288000

How big is the upload?

Files are around 2,5MB
FYI I've also open an issue in bugzilla https://bugzilla.mozilla.org/show_bug.cgi?id=1621277


An option for autofixing certain types of suggestions

The suggestions API helps avoid unwanted 'magic' changes, but may become an inconvenience in some circumstances. We recently bumped the dependencies in one large project and noticed that react-hooks/exhaustive-deps is no longer being autofixed.
I understand that this is a feature and not a bug – it originates from https://github.com/facebook/react/issues/16313 and has valid reasons. However, I was wondering if VSCode ESLint extension could provide a solution this new need to manually accept trivial suggestions in some selected cases.
We follow the Rules of Hooks in all components, so after writing a new React hook we end up using this menu with an almost 100% probability:

It’d be great if we could, say, mention react-hooks/exhaustive-deps somewhere in VSCode’s settings.json and save ourselves from a need to do that. VSCode ESLint extension would just pick the first available suggestion from the list as if we used the menu if autofix on save is enabled.
I saw @dbaeumer’s statement saying that suggestions by definition can't be autofixed. This makes me wonder if this is a conceptual or a technical limitation. If it's the former, what what do you think of enhancing the extension and thus helping developers save time in the described scenario?
PS: Congrats on issue #1000 🎉🕺 Awesome extension ❤

@kachkaev I see your point but IMO something like this shouldn't go into the extension. It would IMO be more consistent if the react ESLint plugin would allow you to say to generate an auto fix instead of a suggestions. This would then keep all the ESLint config in one place.


Document bevy_gizmos

Fix #8179
Still needs module-level docs

Once there's module docs this LGTM. Solid work so far, and I like the gratuitous use of doc examples.

Thanks for the review!
There are no breaking changes here since this API was added after 0.10 was released.

There are no breaking changes here since this API was added after 0.10 was released.

Ah yeah, you're right. Thanks for noting that.


Contact Us

Contact Us form. We have email addresses available (hello@, info@).

Link to copy:
https://github.com/citizenlabsgr/homepage-v2/blob/master/draft_copy/contact_us.md

tested and complete.


JSON sent to programs/scripts to be executed via exec property modified slightly

Before we had:
{"id":"some_id","message":"some_message","details":"some_details","time":"2017-10-25T00:00:00Z","duration":0,"level":"INFO","data":{"series":[{"name":"measurement_name","tags":{"some_tag":"some_tag_value"},"columns":["time","count"],"values":[["2017-10-25T00:00:00Z",399]]}],"Messages":null,"Err":null}}

This changed slightly to:
{"id":"some_id","message":"some_message","details":"some_details","time":"2017-10-25T00:00:00Z","duration":0,"level":"INFO","data":{"Series":[{"name":"measurement_name","tags":{"some_tag":"some_tag_value"},"columns":["time","count"],"values":[["2017-10-25T00:00:00Z",399]]}],"Messages":null,"Err":null}}

That is, "series" under "data" field changed to "Series", which made some shell scripts triggered by our ticks to not work properly, due to them extracting tags buried inside those "series".
We fixed that problem, but I've just wanted to know how it came to this change? I've skimmed changelog and noticed nothing related to this change.
Additionally, if there is preferred way to get the same result, please enlighten me :)
Thanks!

What version did you upgrade from/to? We got bit by this same issue around 8 months ago. The name changed from series to Series and then back to series again. Broke our alerting each time :-(
See https://github.com/influxdata/kapacitor/commit/8ed20f124651557db7e099c0f2f8ac30ed372cbb#diff-bd7f9bc9538b2728f328cfbbeaf9b0a0R9

We are facing this issue https://github.com/influxdata/kapacitor/issues/1639

Hey @phemmer , we've went from v1.0 to v1.2 when our ticks got rowdy-ish. I guess transition to v1.3 will revert to old state (thus breaking scripts again)?

@skuxy @phemmer You are right the series key changed. It was always supposed to be series and it was accedentially changed to Series. We reverted the change and added tests around it to ensure that doesn't happen again. Sorry for the trouble of having to deal with this. If you update to >= 1.3, the key will be series.
Relevent note from the CHANGELOG:

#1199: BREAKING: Fix inconsistency with JSON data from alerts. The alert handlers Alerta, Log, OpsGenie, PagerDuty, Post and VictorOps allow extra opaque data to be attached to alert notifications. That opaque data was inconsistent and this change fixes that. Depending on how that data was consumed this could result in a breaking change, since the original behavior was inconsistent we decided it would be best to fix the issue now and make it consistent for all future builds. Specifically in the JSON result data the old key Series is always series, and the old key Err is now always error instead of for only some of the outputs.

@nathanielc thnx for the warning! We'll keep this in mind for the next upgrade.


Window/level presets to choose from

It would be awesome to have different window/level presets based on different percentiles of the data scalar distribution.
A really sweet deal would be if there were thumbnails to go with them just like color function thumbnails.

For CT there are pre-defined window/level values - we should add those.
We should also read and use the DICOM tags for suggested W/L setting.
Extension of #6

Presets should include 0-50th percentile, 30-70th, ...

See also #270


Remove babel-eslint.

What's this PR do?
This fixes a build error that was occurring because the version of babel-eslint that we were using was intended for ESLint 1.x . There was a new version released the other day that supports ESLint 2.x, but it so happens that ESLint actually supports ES2015 natively now!
So it seems like we can potentially remove this dependency and save ourselves some trouble.
How should this be manually tested?
Pull down this branch and run npm install && npm start in your theme directory. Nothing should fail.
Any background context you want to provide?
Here's the failed Jenkins job referenced above. We've had other sporadic errors relating to this plugin in the past, since it works by monkey-patching part of ESLint (rather than using a "standard" API) and so it's fairly brittle.
What are the relevant tickets?
:speak_no_evil:

:+1:


i18n cache + translation missing + rails validations -> Can't dump...

Rails' ActiveModel::Errors#generate_message includes the value of a field in the i18n options. The value of a field can contain things that can't be marshaled, e.g. files (using paperclip) or hashes with procs (custom attr-accessors) or entire sets of objects (validating a relation).
Normally that's not a problem since those options don't get cached. But if the translation is missing then a MissingTranslation Exception is built and the options are included and then passed to the i18n cache. Since most caches use ActiveSupport::Cache::Store they get get marshaled which ultimately leads to an Exception since they can't be marshaled.
MissingTranslation::Base already attempts to catch some of these:
options.each { |k, v| self.options[k] = v.inspect if v.is_a?(Proc) }

But this doesn't cover the case where arbitrary, non-marshalable objects might occur in the options.
One solution would be to .inspect  the whole options hash when building the exceptions. But that might possibly break someone's except-handling logic.

We also stumbled across this problem with I18n::Backend::Cache due to ActiveRecord validations putting the validated object in the options (key ":object"), the I18n backend passing the option into I18n::MissingTranslation's options and the redis cache store finally not being able to marshal it to store it and failing.
TypeError: can't dump hash with default proc

In our case this error was caused by a User object, which we definitely did not want to appear in the translation cache. What we did was to clean all the options that are reserved keys from the MissingTranslation's options hash. To stay compatible, we copied the MissingTranslation object and removed the reserved keys (I18n::RESERVED_KEYS). All these changes were applied to the file
i18n/backend/cache.rb

only.
This is the patch, put this into your config/initializers/i18n.rb (or what suits you best). I hope it may help someone.
module I18n
  module Backend
    module Cache

      protected

      def _fetch(cache_key, &block)
        result = I18n.cache_store.read(cache_key) and return result
        result = catch(:exception, &block)

        # HOTFIX CHANGES START
        # options hash might contain interpolations as well as i18n options
        # (see I18n::RESERVED_KEYS), some of which contain objects that cannot
        # be marshal'ed (e.g. some ActiveRecord-objects). This causes
        # the redis cache store to fail during marshal'ling. To fix it, we
        # remove all the reserved option keys from the MissingTranslation
        # object's options by creating a new object which is then written to
        # the store. To maintain compatibility the original, unmodified
        # MissingTranslation-object is returned.
        cache_result = result
        if result.is_a?(MissingTranslation)
          cache_result = I18n::MissingTranslation.new result.locale, result.key, result.options.except(*I18n::RESERVED_KEYS)
        end
        # HOTFIX CHANGES END

        I18n.cache_store.write(cache_key, cache_result) unless cache_result.is_a?(Proc)
        result
      end

    end
  end
end

I am unable to reproduce this issue on i18n 0.7.0.
If you're still able to reproduce this issue, please provide me with an app which does so.
Thanks!

@radar I can reproduce this with i18n 0.7.0 and 0.8.1
I added a small generated Rails 5.0.2 project with sqlite3 under Ruby 2.3.1
i18n_bug_reproduce.zip
It has a chain with SimpleBackend and ActiveRecord backend.
The tests are configured to use caching. If you start memcached prior to the test run, it will succeed, but you'll see an error in the logs.
The reason is, that I made the Room model un-serializable, using a stored lambda (this example is a bit constructed, but it might happen).
Another way (happened in a real-life project) is the usage of a gem like deferred_associations, which has side effects, too (I debugged into it, but I did not find the root cause, why the associations are not serializable though).
What is the reason behind trying to cache translations exceptions in I18n::Backend::Cache#_fetch? Wouldn't it be sufficient to cache nil instead and handle this?

Running into this issue as well. In my case the result is a MissingTranslation error w/ an active record model in options[:value]

What is the reason behind trying to cache translations exceptions in I18n::Backend::Cache#_fetch? Wouldn't it be sufficient to cache nil instead and handle this?

I would have expected this use case to happen. Or one of:

Invalidate cache entry for this failing key.
Ignore and keep the previous translation around.

We didnt need to store the MissingTranslation error in the cache for our app, worked around the issue at the cache store layer:
class I18nDelegatedCacheStore < DelegateClass(ActiveSupport::Cache::Store)
  def write(name, value, options = nil)
    value = nil if value.is_a? I18n::MissingTranslation
    super(name, value, options)
  end
end

I18n.cache_store = I18nDelegatedCacheStore.new(I18n.cache_store)

@tappleby You solution fits great for our application.

In my case, on v1.8.2, the issue was limited to my test env with:
TypeError: singleton can't be dumped

I'm using rspec. I mock a (unrelated) method on an object, which gets a validation error with a custom message. I18n tries to cache the missing translation with the invalid object attached as an option. However, in rspec, mocking a method adds a singleton method, which fails on Marshal.dump
I can't think of a case where it's necessary, or even desirable, to include the object that triggered the missing translation in the cache. And it could mean that sensitive information is being written to the cache in cleartext. Could this even be a security issue, e.g., if memcached is hacked?
So borrowing from the previous solutions:
module I18n
  class MissingTranslation
    # Note: the object that caused the missing translation might fail marshaling when attempting to write to cache.
    # It seems like a bad idea to include that in the cached value anyway.
    def initialize(*args)
      super
      options.delete :object
    end
  end
end


[stable/external-dns] RFC2136: can not deploy with insecure flag

Hello!
This is a bug report regarding stable/external-dns.
I tried to deploy external-dns using the RFC2136 provider without TSIG (-> without authentication). So I read the documentation of the chart  and disabled the rfc2136.tsigKeyname key as stated in there. After deploying this, I realised, that the application has started with the flag --rfc2136-insecure=false, which is exactly the opposite, of what it says in the documentation.
The problematic piece of code:
          {{- if eq .Values.provider "rfc2136" }}
            - --rfc2136-host={{ required "rfc2136.host must be supplied for provider 'rfc2136'" .Values.rfc2136.host }}
            - --rfc2136-port={{ .Values.rfc2136.port }}
            - --rfc2136-zone={{ required "rfc2136.zone must be supplied for provider 'rfc2136'" .Values.rfc2136.zone }}
            {{- if .Values.rfc2136.tsigKeyname }}
            - --rfc2136-tsig-secret-alg={{ .Values.rfc2136.tsigSecretAlg }}
            - --rfc2136-tsig-keyname={{ .Values.rfc2136.tsigKeyname }}
              {{- if .Values.rfc2136.tsigAxfr }}
            - --rfc2136-tsig-axfr
              {{- end }}
            {{- else }}
            - --rfc2136-insecure=false
            {{- end }}
          {{- end }}

Not sure if it belongs to this ticket: "--rfc2136-insecure=false" fails with "flag parsing error: unexpected false". Should be "--rfc2136-insecure" only without any value?

Right, it's a bug. You can not start external-dns in "insecure" mode with this helm chart.

The fix seems kind of simple: https://github.com/helm/charts/pull/12598/commits/8364ae405c2fe1964bab4f5e9cd3206225fb7a39


Upgrade to React Native 0.64.x

Please verify the following:

[x] yarn ci:test jest tests pass with new tests, if relevant
[x] README.md has been updated with your changes, if relevant

Describe your PR
Upgrades the boilerplate to React native 0.64.0

https://reactnative.dev/blog/2021/03/12/version-0.64
Updated mobx, mobx-react-lite and mobx-state-tree to latest since the Hermes version included in RN064.x should be able to handle proxies.
There where some regression issue(s) introduced with the 0.64.0 release (https://github.com/react-native-community/releases/issues/221), so expect a minor update when the 0.64.1 releases, or I can update this PR with the next 0.64.x release.
Also updated other libraries such as react-navigation and react-native-screens afaik there should be no breaking changes.
Also please be aware of the major dependency changes ⇒ https://reactnative.dev/blog/2021/03/12/version-0.64#major-dependency-version-changes

Hi @jamonholmgren @bryanstearns
Seems that jest-expo depends on fbjs-scripts which is part of the<EMAIL_ADDRESS>which it uses in assetFileTransformer.js (createCacheKeyFunction), as you can see in the build error.
Seems like<EMAIL_ADDRESS>uses another dependency => "@jest/create-cache-key-function" "^26.5.0".
I'm guessing that since expo does not support RN 0.64.x (afaik) this is not an issue for them, yet.
A workaround is to add fbjs-scripts as a temporary dev dependency (it works..) or Ignite needs to wait until expo supports 0.64.x? What do you guys think?
... The app runs though 😅

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add support to Typed headers for HTTP response

Description:
Related issue : https://github.com/ballerina-platform/ballerina-standard-library/issues/2562
public type RateLimitHeaders record {|
    string x\-rate\-limit\-id;
    int x\-rate\-limit\-remaining;
    string[] x\-rate\-limit\-types;
|};

public type OkWithRateLmits record {|
    *Ok;
    RateLimitHeaders headers;
    string body;
|};

service / on new http:Listener(9090) {
    resource function get status() returns OkWithRateLmits {
        OkWithRateLmits okWithRateLmits = {
            headers: {
                x\-rate\-limit\-id: "1xed",
                x\-rate\-limit\-remaining: 3,
                x\-rate\-limit\-types: ["sliver", "gold"]
            },
            body: "full"
        };
        return okWithRateLmits;
    }
}

OAS mapping
paths:
  /ping:
    get:
      summary: Checks if the server is alive.
      responses:
        '200':
          description: OK
          headers:
            x-rate-limit-id:
              schema:
                type: string
            x-rate-limit-remaining:
              schema:
                type: integer
            x-rate-limit-types:
              schema:
                type: array
                items:
                   type: string
       content:
            test/plain:
              schema:
                type: string

Describe your solution(s)
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

Yeah, this mapping is good. Please note that HTTP support boolean as well.


Single quotes in comments should be escaped

Having a comment with a single quote (') should be escaped (\') to prevent a syntax error.
model Foo {
    /// foo's bar
    bar String
}

Will generate broken text.

@iddan thanks for reporting. Please test out the latest dev release with the fix
npm install -D<EMAIL_ADDRESS>

It works!


Add more core imports to extend

Adds many of the types needed when interpreting a jaxpr.

What's the status of this?

Build issues that we need to fix up before merging.


total spin of Heisenberg chain

Hello,
I am trying to set the total spin of the Heisenberg chain model S_tot=contant as I would like to get the spectrum of a particular spin sector. I noticed that there is an option to set the z projection of spin to be constant by setting Nup in the spin_basis_1d, but I am widening if there is a way to set the total spin?
Another question is when I tried to use the API matmat for matrix multiplication, I used "from quspin.operators.quantum_operator_core import matmat", but it does not seem to work, I am wondering if you could let me know how to import it? Thanks very much in advance.

The total spin symmetry is not implemented yet in Quspin.
See this other issue: https://github.com/QuSpin/QuSpin/issues/635
Regarding your other question, I think matmat is a method of quantum operator, so you do not have to import it. You first define a quantum operator Op and then called the method like Op.matmat(X) where X is a dense matrix (numpy array I guess). I have not tried but it should work.

closing due to lack of activity


how does evcache facilitate eventual consistency?

Hi,
I found this post Caching for a Global Netflix on EVCache,  but the "eventual consistency" model hadn't been elaborated in detail.
Is there any posts or sources describing this model now?

Global replication can be configured to perform invalidation or Full replication.

Invalidation : A set in one region for a given key perform a delete on the other regions for the same key. When this key is requested in then other region we read it from the backing store and populate the cache. This ensures cache is coherent.
Full Replication: A set in one region performs an identical operation on the other region. If the same key is written in the other region then this can result in inconsistency. If strong consistency is required then we recommend the approach described in 1.

Thanks! I get it.


spos2xlsx

Would it be possible for you to make something similar to convert a SteamingPileOfSh1t to xlsx ?
(Hmmm... I just opened an xlsx in a text editor and it seems someone has beaten you to it.)

You have to unzip it first. :)

Is that the best you can do !?!?
On 28 February 2018 at 17:03, Chris Rae<EMAIL_ADDRESS>wrote:

You have to unzip it first. :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pugwonk/gif2xlsx/issues/1#issuecomment-369308176, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AUUlP9MdO7IVlp1jwr7m9r-V2f5cIKO1ks5tZYblgaJpZM4SWuy5
.

Nifty bit of scottish driving here...
http://www.bbc.co.uk/news/av/uk-scotland-43239989/near-miss-as-bus-swerves-to-avoid-car-in-edinburgh


Added convertMap

Codecov Report

Merging #280 into master will increase coverage by 0.31%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #280      +/-   ##
==========================================
+ Coverage   83.23%   83.54%   +0.31%
==========================================
  Files           8        8
  Lines        1921     1939      +18
==========================================
+ Hits         1599     1620      +21
+ Misses        242      240       -2
+ Partials       80       79       -1

Impacted Files
Coverage Δ

vm/vmConvertToX.go
87.61% <100%> (+2.56%)
:arrow_up:

vm/vmExprFunction.go
71.65% <0%> (+1.21%)
:arrow_up:

Continue to review full report at Codecov.

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

Thank you


redshift-plasma-applet: update patchPhase to fix manual updates, don't use upstream

Need to patch every redshift to ${redshift }/bin/redshift so
Nix can use the right binary. Current patch misses one.
Upstream applied https://invent.kde.org/plasma/plasma-redshift-control/-/commit/898c3a4cfc6c317915f1e664078d8606497c4049 to add -P to onetime color settings on redshift version >= 1.12
Since nixpkgs uses 1.12, and upstream seems to break manually toggling the applet off, I applied this fix inline in the patches, and took note of it.
I tested this with a local override, and it works on NixOS+KDE

Motivation for this change
Issue https://github.com/NixOS/nixpkgs/issues/83250 has been a large blocker from me using NixOS more. I finally dove into fix it.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Found a better way to do this, closing this.


The number of Nukies should be determined by total players in the lobby

Description
Currently, the number of nukies that get spawned is determined by how many people are readied up at round start. This can lead to a skewed disadvantage for the nukies, since there are always a good handful of people that deliberately choose not to ready up so they can late join as soon as the round starts.
For example, if 26 people ready up there would be 2 nukies. 7 people then late join right after the round starts bringing the total station population up to 31, so in this case there should have been 3 nukies.
If we decided to determine the amount of nukies that spawn based on the number of players in the lobby this could help fix this issue. Of course this might work the other way around if people AFK in the lobby and leave the game, but i believe this will help make the population difference more fair and balanced.
There is also the issue that more people would naturally join the game and become crew on the station as the round progresses. This puts the nukies at a even larger population disadvantage if they drag their feet getting to the station, but this is mostly a skill issue moment. Regardless it still impacts the round and should still be considered.
Additional context
Thoughts on this?

yeah every time its nukies i always see 2-4 operatives which isnt fair

can't there be just additional nukie spawn as people join the station?
it's unlikely to happen but imagine there is 80 person in the lobby, the gamemode start and there is the maximum number of operatives. but only X% of the players join / disconnect

I think this is a good change, having seen two nukies have to go against 40 or so crewmembers

can't there be just additional nukie spawn as people join the station?
it's unlikely to happen but imagine there is 80 persons in the lobby, the gamemode start and there is the maximum number of operatives. but only X% of the players join / disconnect.
Progressive spawn of operatives doesn't sound bad because most of them take a while to prepare

Can't see how this would work. Would it pop up before the late join actually joins after clicking the open role? What if the nukie ship leaves? It would be easier and better to just use the total players in the game. Counting observers shouldn't impact much.

might just make sense to have the ready up button defaulted to true. if a large percentage of people are late-joining, it might just be because of not remembering to hit the button.

might just make sense to have the ready up button defaulted to true. if a large percentage of people are late-joining, it might just be because of not remembering to hit the button.

I'm like 90% sure it's just people wanting to select their role / backfill. Least I'd guess so.

I'm like 90% sure it's just people wanting to select their role / backfill. Least I'd guess so. Having the ready up button default to true would defeat the point. You aren't "readying up" if it's just putting you in. It'd also probably lead to a lot of SSD people being ingame.

if people are latejoining to just get in extra role slots, then we should adjust how those extra slots are added. Maybe have them only be opened if the server pop exceeds the max pop for the map.

if people are latejoining to just get in extra role slots, then we should adjust how those extra slots are added. Maybe have them only be opened if the server pop exceeds the max pop for the map.

I don't mean extra role slots. I didn't even know it opened more slots when you latejoin. I just meant that there have been times where I don't want to play any specific role, so I latejoin and join a department that could use more people. I imagine sometimes people do the same.
It's also possible that the noise on the roundstart lets people who were tabbed out know that a new round started, to which they join. I don't really see people latejoining as an issue, in all honesty, and think basing it on server pop is a fine workaround.

might just make sense to have the ready up button defaulted to true. if a large percentage of people are late-joining, it might just be because of not remembering to hit the button.

This is a massive issue on Citadel main where some of the population is less keen on antags and do a forced late-join to try an attempt to put them at disadvantage or prevent them from spawning.

Here is an example of a round. Game has 61 players but only 3 nukies.
There was a total of 21 late joins within 15 mins of the round starting.
Not sure if this is a problem of people not readying up or if people notice a new round is starting and hop to the server. Perhaps the amount of nukies needs to be skewed in favor of them to help alleviate this issue, if its not a issue of people not readying up.


How to focus on a new DOM element after rendering

Description
I'm submitting a question about how to focus on a DOM element of my custom Component that was just rendered?

An update causes my component to be rendered
The DOM tree for my component is generated
I want to focus on an <input> element of the generated DOM.

Expected Results
Similar to React, I'd like to be able to focus an input element after rendering.
See this StackOverflow issue for reference: https://stackoverflow.com/questions/38071159/reactjs-how-to-set-focus-to-input-element-when-it-enters-the-dom
Context (Environment)

Rust: v1.36.0
yew: v0.8.0
target: wasm32-unknown-unknown
cargo-web: v0.6.26

Accidental duplicate posting of #593


Dashboard bug

This bug is still not fixed in the latest release (1.6.2).
Even after a clean install, the relaunch of the app still causes duplication and unhide sections. 😕
Originally posted by @dmndrz in https://github.com/Dimillian/ACHNBrowserUI/issues/204#issuecomment-638226235

The bug fix was commited 6 hours ago. It will be inside v1.6.3 that has been send to Apple 2 hours ago. Version 1.6.2 is 2 days old :)


The BLEU-4 of IU-Xray is low

Hello, when I run the code with IU-Xray dataset, I can't get the BLEU-4 score as your paper mentioned, can you help me

I run the "4-1.shallow_run.sh" script and set the epoch to 15, and the result is as follows, which is too low。
{'Bleu_1': 0.37467430953611913, 'Bleu_2': 0.2300607949582794, 'Bleu_3': 0.1528020671072428, 'Bleu_4': 0.10738490881409092, 'ROUGE_L': 0.32565372010124155, 'METEOR': 0.21386175881085717, 'CIDEr': 0.11564642715249945}

I run the "4-1.shallow_run.sh" script and set the epoch to 15 on the iu_xray dataset. The result is as follows, which is too low.
{'Bleu_1': 0.37467430953611913, 'Bleu_2': 0.2300607949582794, 'Bleu_3': 0.1528020671072428, 'Bleu_4': 0.10738490881409092, 'ROUGE_L': 0.32565372010124155, 'METEOR': 0.21386175881085717, 'CIDEr': 0.11564642715249945}

Hi, may I ask how you input two images into the LLM? Do you simply concat the two visual embeddings?


Metamask Wallet url fix

Hi! Please be kind, my first pull request on GitHub;) I have fixed the Metamask link and also (rather passive as I'm a Windows user) the asset duplicates have been removed.

well these assets are not really duplicated... could you update your PR to just change the url for Metamask?

well these assets are not really duplicated... could you update your PR to just change the url for Metamask?

@pedrouid  I'll try then with another client then. If these are not duplicated these should be also marked as an issue. As a Windows user I will always have to choose between having one of these files localy.

@pedrouid  I'll try then with another client then. If these are not duplicated these should be also marked as an issue. As a Windows user I will always have to choose between having one of these files localy.

Hopefully now I got it right. Sorry TFS user here, need to get used to Git and the tools:]

Hopefully now I got it right. Sorry TFS user here, need to get used to Git and the tools:]


The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1202      +/-   ##
==========================================
- Coverage   47.10%   47.08%   -0.03%
==========================================
  Files         197      197
  Lines       15103    15103
==========================================
- Hits         7115     7111       -4
- Misses       7057     7059       +2
- Partials      931      933       +2

Impacted Files
Coverage Δ

catalog/mvcc/cataloger_create_entry.go
94.73% <0.00%> (-5.27%)
:arrow_down:

catalog/mvcc/cataloger_create_branch.go
81.53% <0.00%> (-3.08%)
:arrow_down:

Continue to review full report at Codecov.

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

Codecov Report

Merging #1202 (95beb58) into master (a73e4d6) will decrease coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1202      +/-   ##
==========================================
- Coverage   47.10%   47.08%   -0.03%
==========================================
  Files         197      197
  Lines       15103    15103
==========================================
- Hits         7115     7111       -4
- Misses       7057     7059       +2
- Partials      931      933       +2

Impacted Files
Coverage Δ

catalog/mvcc/cataloger_create_entry.go
94.73% <0.00%> (-5.27%)
:arrow_down:

catalog/mvcc/cataloger_create_branch.go
81.53% <0.00%> (-3.08%)
:arrow_down:

Continue to review full report at Codecov.

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

Fixes #1195.

Fixes #1195.

Thanks; pulling!

Thanks; pulling!


Simplify add player extra data

We are getting rid of NetworkMessage,  so the addplayer methods should not pass a NetworkMessage to the user anymore,  but pass the extra data

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Update version to 0.11.0

This change is

Review status: 0 of 2 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Trouble connecting to spot

The spot instance is launching and it appears in my EC2 dashboard, however, I get the following error and the instance is never connected to from the script.
#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#
#~#~#~#~#~#~#~# Launching HAL9000
#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#

Key pair created...
Security Group Created...
Requesting spot instance
Launching...
......Retrieving instance by id
Got instance: i-028ced4f613d4bd90[running]
.
Waiting for instance to boot..............................Online
Profile requesting EFS mount...
Creating EFS file system...
Initializing...
Detected
Waiting for availability........Available
No mount target detected. Creating mount target...
Traceback (most recent call last):
  File "spot_connect.py", line 69, in <module>
    raise e
  File "spot_connect.py", line 67, in <module>
    mount_target, instance_dns, filesystem_dns = spt.retrieve_efs_mount(fs_name, instance, new_mount=args.newmount)
  File "C:\Users\HAL3000.0\Documents\Spot-Instance-AWS-master\Try1\spot_toolbox.py", line 393, in retrieve_efs_mount
    raise(e)
  File "C:\Users\HAL3000.0\Documents\Spot-Instance-AWS-master\Try1\spot_toolbox.py", line 385, in retrieve_efs_mount
    security_group_id,                                             # Apply the security group which must have ingress rules to allow NFS client connections (enable port 2049)
  File "C:\Users\HAL3000.0\Anaconda3\lib\site-packages\botocore\client.py", line 357, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "C:\Users\HAL3000.0\Anaconda3\lib\site-packages\botocore\client.py", line 661, in _make_api_call
    raise error_class(parsed_response, operation_name)
botocore.errorfactory.SubnetNotFound: An error occurred (SubnetNotFound) when calling the CreateMountTarget operation: The subnet ID 'subnet-9db99fe7' does not exist

`#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#
#~#~#~#~#~#~#~# Launching HL9000
#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#

Key pair detected, re-using...
Security group detected, re-using...
Requesting spot instance
Traceback (most recent call last):
  File "spot_connect.py", line 58, in <module>
    raise e
  File "spot_connect.py", line 56, in <module>
    instance, profile = spt.launch_spot_instance(args.name, profile, instance_profile=args.instanceprofile, monitoring=args.monitoring)  # Launch or connect to the spot instance under the given name
  File "C:\Users\HAL3000.0\Documents\Spot-Instance-AWS-master\spot_toolbox.py", line 173, in launch_spot_instance
    InstanceInterruptionBehavior='terminate',                          # Instance terminates if typing `shutdown -h now` in the console
  File "C:\Users\HAL3000.0\Anaconda3\lib\site-packages\botocore\client.py", line 357, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "C:\Users\HAL3000.0\Anaconda3\lib\site-packages\botocore\client.py", line 661, in _make_api_call
    raise error_class(parsed_response, operation_name)
botocore.exceptions.ClientError: An error occurred (MaxSpotInstanceCountExceeded) when calling the RequestSpotInstances operation: Max spot instance count exceeded`

@Frepap3 can you explain what you changed to get to second error?

mount_efs was True in profiles
also on efs_mount.sh there is a specific efs id which might cause a problem?

This has been resolved with the latest release.


Invalid InChI identifiers

Description of the issue:
The InChI identifiers stored in the YAML file do not start with 'InChI=', which is normally the prefix of all InChI identifiers.
I think they were extracted from the MetaNetX chem_prop.tsv, but the prefix is present in that source file when downloaded directly from MetaNetX.
Also, the following InChI is duplicated/associated with 2 metabolites:
"1S/C27H46O2/c1-18(2)7-6-14-27(5,29)24-11-10-22-21-9-8-19-17-20(28)12-15-25(19,3)23(21)13-16-26(22,24)4/h8,18,20-24,28-29H,6-7,9-17H2,1-5H3/t20-,21-,22-,23-,24-,25-,26-,27-/m0/s1"
Associated with m00592m (20-hydroxycholesterol) and m01183c (7alpha-hydroxycholesterol)
In addition, I wonder why the field is named 'inchis' and not just 'inchi' in the files/codes.
Expected feature/value/output:

all InChI identifiers to be prefixed with 'InChI='.
1-to-1 association between metabolite names and InChI identifiers

Current feature/value/output:

missing prefix 'InChI='
InChI "1S/C27H46O2/c1-18(2)7-6-14-27(5,29)24-11-10-22-21-9-8-19-17-20(28)12-15-25(19,3)23(21)13-16-26(22,24)4/h8,18,20-24,28-29H,6-7,9-17H2,1-5H3/t20-,21-,22-,23-,24-,25-,26-,27-/m0/s1" is duplicated

Reproducing these results:

I hereby confirm that I have:

[ ] Tested my code on my own computer for running the model
[ x] Done this analysis in the master branch of the repository
[ x] Checked that a similar issue does not exist already

These existing InChI strings in the model were inherited from HMR2, not from the MetaNetX.

Okay, good to know. When I search in the repo I saw that InChI strings were pulled out from 'chem_prop.xlsx' or chem_prop.tsv', but I was not sure how or if they are used then.
How do you suggested to fix the problem? I thought about modifying the annotations files, but looks like the InChIs are not stored there or maybe I'm missing something.

No, InChI strings are not included in the metabolite annotation file. They probably don't fit there either - their strings are usually extremely long in format.

About the duplicated InChI, it seems straightforward, according to CHEBI, the 7α-hydroxycholesterol should have an other InChI ID.

Yes, the InChI string of 7α-hydroxycholesterol can be assigned through the associated ChEBI id 17500.

The reason that the inchis field was removed before exporting Human-GEM to SBML is because if a metabolite has an InChI entry, it (the RAVEN SBML export function) will not export its formula from the metaboliteFormulas field. In Human-GEM, the metaboliteFormula field has been heavily curated to ensure mass and energy balances, whereas the inchis field has not been curated. Therefore, when possible, the metaboliteFormulas field should always be treated with higher confidence than the inchis field.
As an additional note, many entries in the metaboliteFormulas field differ from those of other databases, such as MetaNetX. So any plans to update or replace metabolite formulas using an automated approach should be done with caution.

@JonathanRob with the high-confident values in the metFormulas field, are you suggesting to remove the inconsistent InChI strings from the model?

@Hao-Chalmers essentially, yes - if the inchi formula disagrees with the metFormulas entry, then the metFormulas entry should be used.

I checked, there are only 2 minor conflicts on inchi formula versus metFormula.  The order is just different in both cases:
C16H13ClN2O != C16ClH13N2O and C15H11ClN2O != C15ClH11N2O. Will fix this using CHEBI, in the same PR.

I checked, there are only 2 minor conflicts on inchi formula versus metFormula.  The order is just different in both cases:
C16H13ClN2O != C16ClH13N2O and C15H11ClN2O != C15ClH11N2O. Will fix this using CHEBI, in the same PR.

According to the Hill system, chemical formulas should begin with carbon atoms, hydrogen atoms next and all others are then listed in alphabetical order. So C16H13ClN2O and C15H11ClN2O are correct.

According to the Hill system, chemical formulas should begin with carbon atoms, hydrogen atoms next and all others are then listed in alphabetical order. So C16H13ClN2O and C15H11ClN2O are correct.


Removed the Preview reference for Azure Container Registry since it …

…was made GA in April.

@jreypo,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/aws-professional/services.md
:white_check_mark:Succeeded
View

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


micro-deposits: record metrics on initiate and confirmation

Codecov Report

Merging #324 into master will decrease coverage by 4.31%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #324      +/-   ##
==========================================
- Coverage   61.17%   56.85%   -4.32%
==========================================
  Files          48       48
  Lines        5239     5241       +2
==========================================
- Hits         3205     2980     -225
- Misses       1431     1692     +261
+ Partials      603      569      -34

Impacted Files
Coverage Δ

internal/microDeposits.go
63.67% <100%> (-1.22%)
:arrow_down:

internal/accounts.go
10.66% <0%> (-66.67%)
:arrow_down:

internal/customers/client.go
18.39% <0%> (-60.92%)
:arrow_down:

internal/database/mysql.go
10.66% <0%> (-50.67%)
:arrow_down:

internal/filetransfer/sftp.go
30.27% <0%> (-42.17%)
:arrow_down:

internal/filetransfer/config.go
70.98% <0%> (-0.42%)
:arrow_down:

Continue to review full report at Codecov.

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


fix(invoice): only notify on settled invoices

Fix a bug where we were incorrectly notifying users that an invoice had been successfully paid when it had actually just been created.
Fix #670

Pull Request Test Coverage Report for Build 3728

0 of 4 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.008%) to 12.311%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

app/reducers/invoice.js
0
4
0.0%

Totals

Change from base Build 3725:
-0.008%

Covered Lines:
466

Relevant Lines:
3334

💛  - Coveralls

utACK b1be3f4


Use double quotes consistently

The codebase is a mess of single and double quotes.
Everything should be changed to double quotes (") for consistency.

Hey @garroadran, new to open source but would like to take this on as my first PR if you're OK with that?

Hi @DnrkasEFF
By all means! I'm always happy to put up issues like these so peeps can get some experience putting in PRs. Have at it!

(and thanks for the help!)


Parallel Coordinate Diagram

I have a use case for Datashader to produce a Parallel Coordinate Diagram (https://en.wikipedia.org/wiki/Parallel_coordinates) for ~100 million independent N - Dimensional vectors.  My current dataset stores each of the N-dimensions as a separate column in a DataFrame.  I was hoping the interface would allow for easy reordering of the columns.
I have attempted to implement a Parallel Coordinate glyph very similar to the line glyph, but my implementation is not running as efficiently as I'd like.
I have a couple of questions:

Am I missing an easy way to generate a Parallel Coordinate Diagram with the existing Datashader interface? (hoping to have efficiency similar to N * line efficiency)
Is there any recommendations to help improve efficiency? See the attached file Line2 glyph for my first attempt.
glyphs.txt

Feel free to follow up with questions.
Thank you for you help,
Justin

I haven't tried it, but I would have thought you could use the existing Line support to do a parallel-coordinates plot, by transposing and padding your data into a tidy format like the one in the timeseries notebook, with each multiline separated by np.NaN.  That should be fast to render, but It's true that such a representation would not facilitate reordering the columns.  So it may be appropriate to write special-purpose code for parallel coordinates organized as you describe, though I would have hoped it would require far less duplication of code than in the attached file.

One of the requirements would definitely be to support column reordering without performing data manipulation.  I agree about the code duplication, I wanted to get something working efficiently before I refactored.

Could you not just reorder the columns (i.e., the x axis) after aggregation?  That should be a quick operation to do, at that point, assuming the data is much larger than the resulting aggregation grid, as it would be in your case.

(Sorry for the noise -- you are presumably aggregating into a 2D image, not a list of columns, so my suggestion would not be appropriate (and is now deleted)!

(...) transposing and padding your data into a tidy format like the one in the timeseries notebook, with each multiline separated by np.NaN. (...)

@jbednar, is there a way to make line splitting (by adding separating np.nan's) that will work also with grouped plots? Like such one:
start = plot_data.time.min()
end = plot_data.time.max()
ds = hv.Dataset(plot_data, ['time', 'variable'], ['value'])
grouped = ds.select(variable=[..., ..., ...], time=(start, end)).to(hv.Curve, 'time', 'value')
datashade(grouped)

When that comment was written in 2017, the only way to have separate lines was to put NaNs between them in one continuous list, but Datashader now supports many different ways to provide multiple lines, and so you can usually choose one that is efficient both for rendering and for whatever else you want to do with the lines, such as having one column per line. See https://datashader.org/user_guide/Timeseries.html#Plotting-large-numbers-of-time-series-together for an example, and look at the docstring for datashader.Canvas.line for the details.
HoloViews will generally choose an appropriate representation already, and if what you are asking here is why you get an error in a specific case, please file that as an issue on HoloViews with the error message or incorrect output so that we can see what needs to be done.
Meanwhile, this issue is about good support for large parallel coordinate plots, which if nothing else needs a good example somewhere, so I'll leave it open for that purpose.