The end of GoodTwitter

https://twitter.com/ZusorOW/status/1258885451055800320

I just saw this too, this sucks real bad.

Gdi

Maybe you can work on a open source front-end for twitter?

This hurts my damn soul. :(

@Gliscor https://github.com/zedeus/nitter exists, they rely on the old UI, but the creator will move it to scrape the new UI soonish

@Gliscor https://github.com/zedeus/nitter exists, they rely on the old UI, but the creator will move it to scrape the new UI soonish

Nitter doesn't allow you to login ad stuff.

@Gliscor http://www.easychirp.com/ Is what you're looking for then.

f


Clean up shape file upload script

The shape upload script presently is spaghetti code. It is unclear how many different things it does and how.
Have to investigate the following to rewrite this:

Is there a wrapper for postgis that allows uploading shape files without manually writing SQL?
Is there perhaps a way to use the geoserver rest API itself in order to take care of everything that needs to be changed at geoserver end after uploading shape file into postgres?

There seems to be a client library at https://github.com/geosolutions-it/geoserver-manager
It doesn't seem to be updated in some years. But the API is cool: https://github.com/geosolutions-it/geoserver-manager/wiki/Various-Examples
Unless there is a better client library, it might very well be worth it to adopt and maintain this project (it is MIT license).


feat(validator): add body length parameter

Adding a body length parameter because some tools (like dependabot) generate very long commit message and we might not need to restrain the length to only 100 characters

Works great in CI :)
Tested here https://github.com/lumapps/rich-text/actions/runs/11066911637/job/30749136883?pr=86


executing the script stops at line 106 from util.py

I have tried to use this script and when it is running it stopped at line 106 from utils.py.

Hi @cybercheat,
What version of Python did you use?

Hi it is python2 the command I'm running is python impot_export_package.py
I'm not sure if the checkpoint appliance has installed pyhton3 .
thanks

Hi,
Since version 5.0 of the tool, the tool supports Python 3.7.
Please use Python 3.7.
Thanks,
Shiran


Add Pokémon identification (only visible to GM)

We can use the Surname field for wild Pokémon and the Box & Position fields for trainer Pokémon.


Unify MessageMetaClass & EventMetaClass.

Add TemplateSendJobFinishEvent.
Close #134 #139

A new inspection was created.

The inspection completed: 4 updated code elements

A new inspection was created.

A new inspection was created.

The inspection completed: 4 updated code elements

The inspection completed: 4 updated code elements


V2 - While sending request to signatory 500 is returned when only spaces is provided for the authority_name

Observed that while sending request to signatory 500 is returned when only spaces is provided for the authority_name
Endpoint https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/request-corporate-signature
HttpMethod POST
Payload
{
"authority_email"<EMAIL_ADDRESS>"authority_name": "              ",
"company_sfid": "0014100000Te0iaAAB",
"project_sfid": "a091700000A5GTvAAN",
"return_url": "https://corporate.dev.lfcla.com/#/company/79b422d0-4261-41d7-a834-ccce7fe07bed",
"send_as_email": true
}
Response

@rinkeshbhutwala can you ensure that we have swagger spec format/pattern to prevent empty or space-only values being passed to our API for this issue?

Verified that 422 with appropriate message is displayed


Graphics::Resize crashes when window minimized

If I minimize the main window by hitting "-" on the title bar, Graphics::Resize() crashes because it tries to resize the SwapChain buffers to 0,0

Thanks for the bug report.  I just pushed a fix to GraphicsCore.cpp.


fix(eslint): consolidated eslint rules and deleted external package from package.json

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] All the files I changed are in the same world language, for example: only English changes, or only Chinese changes, etc.

Closes #40159

Just consolidated the eslint rules and deleted the external package from package.json. I was getting some linting errors after I consolidated so I changed the errors to a warn. I tried to install eslint globally and fix some of the issues but it didn't edit any files. Please feel free to contact me with any questions or concerns. Thanks!

Thanks for the feedback. Will push up changes shortly.

Uh, tried to squash some commits and I think I just made things worse. Sorry! Should be good to go now.


Trying to create new controller in monologue engine

I'm trying to create a description page for blog post authors.  I've created a route:
  mount Monologue::Engine, at: '/blog'

  #create routes for monologue
  Monologue::Engine.routes.draw do
      get 'p/:name', to: 'authors#show', as: :author
  end

And I've created a controller in app/controllers/monologue:
class Monologue::AuthorsController
    def show
	    puts "in show method"
    end
end

I keep getting this error:
undefined method `action' for Monologue::AuthorsController:Class

Long story short: how do I generate a controller within monologue?

It needs to inherit from a bad controller or ApplicationController
Jean-Philippe Boily
Human. Ruby developer.  | http://jipiboily.com/
On Fri, Dec 4, 2015 at 2:56 PM, codeundercoverdev
<EMAIL_ADDRESS>wrote:

I'm trying to create a description page for blog post authors.  I've created a route:
mount Monologue::Engine, at: '/blog'
#create routes for monologue
Monologue::Engine.routes.draw do
get 'p/:name', to: 'authors#show', as: :author
end
And I've created a controller in app/controllers/monologue:
class Monologue::AuthorsController
def show
puts "in show method"
end
end
I keep getting this error:
undefined method `action' for Monologue::AuthorsController:Class
Long story short: how do I generate a controller within monologue?
Reply to this email directly or view it on GitHub:
https://github.com/jipiboily/monologue/issues/274

Probably  mean a " base " controller ☺
On Fri, Dec 4, 2015, 18:03 Jean-Philippe Boily<EMAIL_ADDRESS>wrote:

Closed #274 https://github.com/jipiboily/monologue/issues/274.
—
Reply to this email directly or view it on GitHub
https://github.com/jipiboily/monologue/issues/274#event-483182799.

I was able to fix it by doing this:
module Monologue
	class AuthorsController < Monologue::ApplicationController
    	def show
	    	@rachel = "yes"
    	end
    end
end

I had to nest the class in the Monologue module and had to have it inherit from the Monologue controller because there were conflicts with ApplicationController

@msevestre lol, yes! Autocorrect...I guess? :grimacing:

@codeundercoverdev glad you got it fixed!


[move-package] Support dependency overrides

Motivation
This PR addresses problem with package versioning introducing potential for diamond problems (two sibling dependencies with a shared dependency whose version does not match).
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Respective tests have been added

Overrides are specified explicitly, rather than what the previous solution assumed, that is implicitly. In other words to override some dependency C that A and B depend on (and conflict on), we specify a version of C to be used in the root package's manifest file:
[dependencies]
A = { local = "./deps_only/A" }
B = { local = "./deps_only/B" }
C = { local = "./deps_only/C", version = "1.0.0", override = true }

rather than, what was assumed before, specifying which dependency path is supposed to designate the "winning" version of the package:
[dependencies]
A = { local = "./deps_only/A", override = true }
B = { local = "./deps_only/B" }

The updated algorithm is as follows (repeated here from the doc-comment for the override_pkg function.
The algorithm relies on the fact that this check is performed when a new  package is added to the graph already containing package with the same name - this allows us to resolve the conflicts pair-wise even if ultimately a package with a given name is a dependency of more than two other packages.
First we check if package already existing in the graph has been inserted there as a result of  an override. If it was, then either:

the new package is dominated by the same override
or
no valid override can be found and error must be reported

Because the overridden dependencies are processed first for each package, it is guaranteed that when searching for overrides for a child (new package), a correct override will be found if it exists because by construction it must be already present in the graph.
If package already existing in the graph has not been inserted as a result of an override then  either:

the new package has been inserted as a result of an override and:

it's dominating override for the existing package then new package is the winner
or
it's not a dominating override for the existing package then an error must be reported
or

the new package has not been inserted as a result of an override and an error must be reported

Correctly finding dominators only works because when trying to add a conflicting package through a new dependency edge, we add this edge early in an non-finalized state (before the package is fully processed), finalizing the edges only after package processing is done.


Heroku deployment button does not deploy working version to Heroku

I clicked on the button and followed the prompts on the Heroku page it redirected me to. No default options were changed.
However, when I try to visit the app running on Heroku, I get the error
An error occurred in the application and your page could not be served. Please try again in a few moments.

When I check the Heroku logs, I see the messages
2016-09-30T07:24:39.282274+00:00 heroku[slug-compiler]: Slug compilation started
2016-09-30T07:24:39.282281+00:00 heroku[slug-compiler]: Slug compilation finished
2016-09-30T07:24:41.789190+00:00 heroku[web.1]: Starting process with command `npm start`
2016-09-30T07:24:45.097942+00:00 heroku[web.1]: Process exited with status 1
2016-09-30T07:24:44.775058+00:00 app[web.1]:
2016-09-30T07:24:44.775072+00:00 app[web.1]: ><EMAIL_ADDRESS>start /app
2016-09-30T07:24:44.775073+00:00 app[web.1]: > node app.js
2016-09-30T07:24:44.775073+00:00 app[web.1]:
2016-09-30T07:24:44.943049+00:00 app[web.1]: /app/app.js:5
2016-09-30T07:24:44.943053+00:00 app[web.1]: itemsapi.get('logger').info('it works!')
2016-09-30T07:24:44.943054+00:00 app[web.1]:                       ^
2016-09-30T07:24:44.943054+00:00 app[web.1]:
2016-09-30T07:24:44.943055+00:00 app[web.1]: TypeError: Cannot read property 'info' of undefined
2016-09-30T07:24:44.943056+00:00 app[web.1]:     at Object.<anonymous> (/app/app.js:5:23)
2016-09-30T07:24:44.943057+00:00 app[web.1]:     at Module._compile (module.js:413:34)
2016-09-30T07:24:44.943057+00:00 app[web.1]:     at Object.Module._extensions..js (module.js:422:10)
2016-09-30T07:24:44.943058+00:00 app[web.1]:     at Module.load (module.js:357:32)
2016-09-30T07:24:44.943059+00:00 app[web.1]:     at Function.Module.runMain (module.js:447:10)
2016-09-30T07:24:44.943058+00:00 app[web.1]:     at Function.Module._load (module.js:314:12)
2016-09-30T07:24:44.943060+00:00 app[web.1]:     at startup (node.js:148:18)
2016-09-30T07:24:44.943065+00:00 app[web.1]:     at node.js:405:3
2016-09-30T07:24:44.952815+00:00 app[web.1]:
2016-09-30T07:24:44.964618+00:00 app[web.1]: npm ERR! Linux 3.13.0-93-generic
2016-09-30T07:24:44.965164+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start"
2016-09-30T07:24:44.965502+00:00 app[web.1]: npm ERR! node v5.11.1
2016-09-30T07:24:44.966199+00:00 app[web.1]: npm ERR! npm  v3.8.6
2016-09-30T07:24:44.966664+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2016-09-30T07:24:44.966848+00:00 app[web.1]: npm ERR<EMAIL_ADDRESS>start: `node app.js`
2016-09-30T07:24:44.967012+00:00 app[web.1]: npm ERR! Exit status 1
2016-09-30T07:24:44.967200+00:00 app[web.1]: npm ERR!
2016-09-30T07:24:44.967412+00:00 app[web.1]: npm ERR! Failed at the<EMAIL_ADDRESS>start script 'node app.js'.
2016-09-30T07:24:44.967659+00:00 app[web.1]: npm ERR! Make sure you have the latest version of node.js and npm installed.
2016-09-30T07:24:44.967894+00:00 app[web.1]: npm ERR! If you do, this is most likely a problem with the itemsapi-starter package,
2016-09-30T07:24:44.968091+00:00 app[web.1]: npm ERR! not with npm itself.
2016-09-30T07:24:44.968376+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system:
2016-09-30T07:24:44.968498+00:00 app[web.1]: npm ERR!     node app.js
2016-09-30T07:24:44.968868+00:00 app[web.1]: npm ERR! You can get information on how to open an issue for this project with:
2016-09-30T07:24:44.968871+00:00 app[web.1]: npm ERR!     npm bugs itemsapi-starter
2016-09-30T07:24:44.969072+00:00 app[web.1]: npm ERR! Or if that isn't available, you can get their info via:
2016-09-30T07:24:44.969577+00:00 app[web.1]: npm ERR!     npm owner ls itemsapi-starter
2016-09-30T07:24:44.969825+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
2016-09-30T07:24:44.976783+00:00 app[web.1]:
2016-09-30T07:24:44.977054+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2016-09-30T07:24:44.977197+00:00 app[web.1]: npm ERR!     /app/npm-debug.log
2016-09-30T07:24:45.121730+00:00 heroku[web.1]: State changed from starting to crashed

Could someone confirm reproducible and suggest steps to troubleshoot this?

Never mind, found that the Heroku button link found on
https://itemsapi.readme.io/docs/getting-started and https://www.itemsapi.com/docs/tutorials/search-backend-for-restaurants-itemsapi-elasticsearch-nodejs are bad, but the one found on the README of this repository is ok.
I think the difference is that the button in this repo tries to deploy the itemsapi/dashboard repo, but the buttons in the other documentation try to deploy the itemsapi/itemsapi-starter repo. Is there a reason why this repository works but the other one does not?

Hello Aaron, thanks for your insight. It is very helpful! Yeah, there was an small issue here itemsapi/itemsapi-starter but it is fixed now (https://github.com/itemsapi/itemsapi-starter/commit/ca117191b13ad889ed182a4816d89a1c953f5f12).
Also small clarification:
https://github.com/itemsapi/dashboard - web dashboard for quick and interactive adding and exploring json data. In the longterm maybe also managing data. Good for testing ItemsAPI and exploring data.
https://github.com/itemsapi/itemsapi-starter - minimalistic search API creator. It was intended to help developers create search API step by step with guides. Still in basic version. Can be also good for creating standalone search oriented Express.js application


.Net: Improve sample 02-Native-Functions

[ ] Alignment to C# coding standards (e.g., file naming conventions).
[ ] Comments for docs snippet references.
[ ] Add developer support for Visual Studio (enable run button)

Closing so we can create new issues for docs later


class .leaflet-tile-loaded is added even in case of a loading error

Class leaflet-tile-loaded is added even in case of a loading error.
(The bug seems to strike on Chrome not Firefox)
Demo:
http://bl.ocks.org/Fil/75b76aec31fa76060a0c872c68ae44da
Fix:
line 4583:
-		L.DomUtil.addClass(tile.el, 'leaflet-tile-loaded');
+		if (!err) L.DomUtil.addClass(tile.el, 'leaflet-tile-loaded');

So that code is around https://github.com/Leaflet/Leaflet/blob/master/src/layer/tile/GridLayer.js#L814

I think this is a regression - in 0.7.7, the leaflet-tile-loaded CSS class in only added on the tileload event, whereas it's not added on tileerror, see https://github.com/Leaflet/Leaflet/blob/v0.7.7/src/layer/tile/TileLayer.js#L566
We should keep in line with the 0.7.7 logic and not fire tileload events when there's a tile loading error, right?
@Fil Can you please try to make a pull request? A simple check wrapping the addClass() and fire('tileload',...) statements should suffice at this point. Anything else and we risk breaking the tile pruning logic.

maybe just a return; here https://github.com/Leaflet/Leaflet/blob/master/src/layer/tile/GridLayer.js#L797

@Fil No, that has the potential of messing up the pruning algorithm if the last tile gives an error.

Sorry I don't know enough Leaflet internals to help with this.
-- Fil
On Thu, Sep 15, 2016 at 9:59 AM, Iván Sánchez Ortega <
<EMAIL_ADDRESS>wrote:

@Fil https://github.com/Fil No, that has the potential of messing up
the pruning algorithm if the last tile gives an error.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Leaflet/Leaflet/issues/4912#issuecomment-247262320,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAbWQUVD1ZiRX1Ntm2rKo0CrUBjSTJEks5qqPrcgaJpZM4J81zR
.

@IvanSanchez By a simple check do you mean if (!err)? Should we add a test?

@thachhoang Yes, just make sure that src/tile/GridLayer, around line 814, does not apply the leaflet-tile-loaded css class if there's been an error, and also it shouldn't fire the tileload event. The _tileReady method should look like:
if (err) {
    fire 'tileerror'
}

request tile fade-in

if (!err) {
   apply leaflet-tile-loaded css class
   fire 'tileload'
}

check if all tiles have been loaded

It seems simple enogh, so I'll let you or @Fil try it, test it, and submit a pull request to fix it.

Fixed via #4980


Travis CI is currently showing build failure for master

Thank you. Somehow I missed Travis' mail. I'll have a look at this.

Thank you for bringing that to my attention. I fixed the configuration. The tests will now succeed as soon as https://github.com/publicsuffix/list/pull/21 is merged.


get actions return null

DAWN-2018-05-22
i want to get actions or transactions with accout, but i have gotten noting
i don't konw why?
i have set  filter_on_accounts = jinmao3 in config.ini
./cleos.sh get currency balance eosio.token jinmao3  EOS
2000.0000 EOS
./cleos.sh get actions jinmao3
seq  when                              contract::action => receiver      trx id...   args

solved #3244

same problem

same issue here, is there a fix to reset default behavior surpassing all actions?


Kubernetes-addon namespaces can be specified and creation optional

What does this PR do?
This change makes it possible to use any of the kubernetes-addon modules with an already extant namespace. In a number of instances, the namespace creation is done via the IRSA module. In those cases, this PR also ensures the namespace is passed from the helm_config.
Motivation
I'm attempting to get my colleagues to adopt this module into our EKS Terraform projects. In our case we deploy operational modules to a single namespace. This is created outside the addon modules. To migrate to these modules, we need to be able to disable namespace creation and allow the namespace to be specified.
More

[x] Yes, I have tested the PR using my local account setup  (Provide any test evidence report under Additional Notes)
[ ] Yes, I have added a new example under examples to support my PR
[ ] Yes, I have updated the docs for this feature
[x] Yes, I ran pre-commit run -a with this PR

Note: Not all the PRs required examples and docs except a new pattern or add-on added.
For Moderators

[ ] E2E Test successfully complete before merge?

Additional Notes

Please add kubernetes-dashboard

Done @Hokwang. I thought the namespace had been removed entirely from the Terraform. Thanks for highlighting this.

@bryantbiggs any chance you could review this again?

Thanks for the changes @bryantbiggs. Was just looking at your comments and then they appeared.

@bobdoah 😅 give me a sec and I should have the rest of the updates - we'll get this across the line today

@askulkarni2 should be ready to re-review if you have time - merge away if things look ok

Thanks for all the changes to sort this @bryantbiggs and merging @askulkarni2


use built in way to call extended widget

So the previous version was:
return $.ui.dialog.prototype._allowInteraction.call(this, event) ? true : !!$( event.target).closest('.ccm-interaction-dialog').length;

It looks like the progression is "Call the parent function, if it returns true just return true. If it returns false, return whether we're underneath .ccm-interaction-dialog or not."
So basically we always call the parent function, if it returns false and we're underneath .ccm-interaction-dialog we return true.
Now this replacement is different !!$( event.target).closest('.ccm-interaction-dialog').length || this._super(event). We're only calling the parent if we're not underneath .ccm-interaction-dialog.
So both versions act the same to a caller, but the new version omits a call to parent where before there was one. So my only question is, does $.ui.dialog.allowInteraction have any side effects?

Aaaaand the answer is no:
        _allowInteraction: function (t) {
            return e(t.target).closest(".ui-dialog").length ? !0 : !!e(t.target).closest(".ui-datepicker").length
        },


Contact info?

Hello, I would love to talk to you about your and my work. I have relatively recently started looking into using ML for trading, as we already do a lot of trading but didn't utilize ML yet but I couldn't find any contact info. Could you please drop me your email or some chat app username?

Sorry I just saw the message, my email is<EMAIL_ADDRESS>


compare bibtext files

Assume I have two bibtex files from different sources. How can I measure similarities between entries? For example, I would like to search for all entries in file 1 which are not in file 2.
git-bob think about this

Let's assume IDs are not identical. I'd prefer to count how many parameters (author, url, title, ...) are identifcal between to bibtex entries. Then, we can assume if > 5 of those parameters are identical, they are the same records.
git-bob think about how to implement this.


Not clear why certain requests with mTLS fail with 503

Probably this is not a bug, but I am not getting why is this happening.
So, according to the documentation, when you enable mTLS, it enables it only for server side, and you need to create a DestinationRule for the client side; otherwise you get 503.
That's exactly what happens until I create this DR, and it returns 200:
apiVersion: "networking.istio.io/v1alpha3"
kind: "DestinationRule"
metadata:
  name: "default"
  namespace: "istio-system"
spec:
  host: "*.local"
  trafficPolicy:
    tls:
      mode: ISTIO_MUTUAL

Now, when I set the destination rule in the namespace foo or bar, this is the result:
~# for from in "foo" "bar"; do for to in "foo" "bar"; do kubectl exec $(kubectl get pod -l app=sleep -n ${from} -o jsonpath={.items..metadata.name}) -c sleep -n ${from} -- curl "http://httpbin.${to}:8000/ip" -s -o /dev/null -w "sleep.${from} to httpbin.${to}: %{http_code}\n"; done; done
sleep.foo to httpbin.foo: 503
sleep.foo to httpbin.bar: 503
sleep.bar to httpbin.foo: 200
sleep.bar to httpbin.bar: 503

So, only 1 of the requests goes through. in this case, the DR was in the namespace: bar.

Starting with Istio 1.1, only destination rules in the client namespace, server namespace and global namespace (default is istio-system) will be considered for a service, in that order.

Question: Shouldn't bar to bar succeed as well? Why is it failing.
If I switch it to foo, the second request (foo to bar) succeeds, and the rest fail with 503. And if I create the DR in both namespaces, all requests fail.
I believe it somehow overwrites the certs? Could you explain this behavior please?

I am a bit confused what ns the destination rule is in. If its in foo, and you go bar -> bar, it should fail, its not in the client (bar), server (bar) or global (istio-system) namespace? Maybe I am misunderstanding though

@nerusnayleinad please note that there could be some delays in the propagation of the configuration to the sidecars. Can you run your test loop a minute after your perform the configuration?

In recent releases propagation time is typically under 200ms
On Thu, Dec 26, 2019, 4:57 AM Vadim Eisenberg<EMAIL_ADDRESS>wrote:

@nerusnayleinad https://github.com/nerusnayleinad please note that
there could be some delays in the propagation of the configuration to the
sidecars. Can you run your test loop a minute after your perform the
configuration?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/19777?email_source=notifications&email_token=AAEYGXOYZ2RO345MTDTT2B3Q2SS5BA5CNFSM4J65MTQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHVRISQ#issuecomment-569054282,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXJJXDCDU4M3QMCMDA3Q2SS5BANCNFSM4J65MTQA
.

@howardjohn When the DR is in the namespace bar, the request from bar to foo works, but fails bar to bar. Is this intended?
In the same way, if I set the DR in foo, foo to bar works, but the rest fails.
And if I create the DR in both namespaces, all requests fail.


Consider racks on NetworkTopologyStrategy

Skips hosts on the same rack until all racks have been included in the DC.
Memoize token building for keyspaces with the same network replication

:+1: LGTM


Wrist

Motor: Brushed DC Car Seat Motor Connected Directly to Robot Rio???????????? Neo
Gear Ratio: ???????????????
Tl;dr: CAD Team said ask Mr. Juan

[x] Physical
[x] Simulated
[ ] Motion Profiling

Not including motion profiling, going under new issue


Check behaviour of "foreground" flag

It is still documented and seems to lead some users the wrong way. Might need cleanup and/or removed.

@maxhq is this used in the testing somewhere? As we have now "no detach" this should be obsolete and can be solved by configuring a non-forking server

It is not used in any active tests anymore and will be removed.


Stop averaging response codes

I'm seeing an "averaged" response code of 213 due to one 404 response (and the rest 200).

Hello @FTCHD
Thank you for the suggestion, will pass down into development. Will update ticket once it's ready


Update dependency from kyazdani42/nvim-web-devicons to nvim-tree/nvim-web-devicons

I get this error (Cybu: nvim-web-devicons enabled, but not installed) on starting Neovim and I assume it's because the repository changed from kyazdani42/nvim-web-devicons to nvim-tree/nvim-web-devicons.

It should not be an issue if you install via the old reference, as it redirects to the new location.
Could you check if nvim-tree/nvim-web-devicons is correctly installed? You can use the following command:
:lua =require'nvim-web-devicons'.has_loaded()

If everything is OK, it should return true. If you receive an error, that means you probably need to install  nvim-tree/nvim-web-devicons first.
Nonetheless, I have updated all references in the README from kyazdani42/nvim-web-devicons to nvim-tree/nvim-web-devicons.

You were right, thank you! Apparently packer.nvim doesn't install dependencies into the same location unless they're explicitly specified as a top-level plugin.


Minor Issue in docs

Very small issue.
Here's the screenshot of the docs

There is no semicolon here. But In the source It is present. I wonder how it's missing here.

It seems the docs are rendered from v1.5.1 tag, while v1.6.0 is the last and includes the fix (https://github.com/sphinx-contrib/redoc/commit/fb4fee642a4336361a8bcac814cb574f7cc48e34).

Just rebuilt the docs. Thank you for noticing that.


Let the user know that "backup" filters have been loaded

Is your feature request related to a problem? Please describe.
The CC Catalog API adds (and sometimes removes) the image providers available. Therefore, the extension loads the latest providers using the /statistics/image endpoint of the API at the start of the popup session (same for the "Filters" tab in the options page).
If there is no internet connection or the API is giving some error, extension loads from a "backup" list of providers. I think that letting the user know that the "backup" filters have been loaded for the current session would be good.
Describe the solution you'd like
We can use snack bar for showing the message but increasing the time duration from ~1sec to something more significant is needed.

Can I pick this up?

Sure, go ahead!


feat: add status prop in checkbox, radio, select, slider and toggle

Checklist

[x] Fix linting errors
[x] Tests have been added / updated (or snapshots)

Change information
To make components more consistents, added the status prop who allows to show the component with different colors based in a status.
components affected: checkbox, radio, select, slider and toggle
Will solve https://github.com/geist-org/react/issues/507

@unix  all Done!


Support for openAPI

do you consider construct agents to consume arbitrary APIs, here APIs conformant to the OpenAPI/Swagger specification.

Yes. That's in the plan.

When is the expected launch time for the feature
I am more focused on importing JSON or YAML format files (Swagger specification) and combining them with LLM to achieve parsing natural language, using formatted prompt words, and calling corresponding APIs through proxies to connect business systems
@li2109

About 2-3 weeks.


Update introduction in README

Suggestion for an updated intro and features in the README.
Rationale: I'm struggling a lot to follow many of the new Yii3 packages due to lacking/unclear docs (also inline). This is a first attempt to make it a bit easier for the newcomers. Feel free to ignore - or change again at a later time.
OT: Also started adding some inline docs mainly for myself - not sure if another PR is welcome. If so I'd definitely need more help/answers as a lot of code is unclear without comments.

@mikehaertl feel free to pull request additional docs. These are welcome. Inline comments may be a signal that the code could be refactored for better clarity or these could be alright (in case thing itself is meant to be complicated).

I've applied changes to diagrams and merged it. Thank you!

@samdark Nice, thanks.
Minor note for the diagram: Without "yes"/"no" labels the diagram can not be read by color blind persons. (According to wikipedia 8% of the male population is affected by red/green blindness).

Adjusted in https://github.com/yiisoft/injector/commit/3a721341add2df148650e18397b1212dd9007156


⚠ Site has degraded performance

In 658fe26, Site (https://fyle.uk) experienced degraded performance:

HTTP code: 200
Response time: 1388 ms

Resolved: Site performance has improved in 9c15f27 after 12 minutes.


Blank screen

I'm getting a blank screen and I can't login. I have restarted my computer but its still persisting.
This is a screenshot

You have internet problem 😜

I had the same issue too. Turned out it was a snort rule in my case (Rule = 1:70969) Thanks to @novdddd

I have the same problem on tusk and Rambox, only works in the browser. I didn't find a solution

Some people reported the same issue in this issue https://github.com/klaussinani/tusk/issues/150
I think we all having issue with Tusk 0.23.0


Scope of embedded-storage

I wanted to start a discussion about the scope of embedded-storage.
It could be one of the following:

Define a common interface between device drivers and generic storage implementations (e.g. filesystems) like embedded-hal.
That way things like LittleFS on any flash chip with an embedded-storage compatible driver would be possible. That's basically what NorFlash currently does.
Define an traits for generic, simple, easy to use, byte addressed storage that could be implemented based on any technology. That is currently the Storage trait.
Provide most commonly used storage implementations based on the traits above.

In my experience with Rust most crates contain either traits to act as a common interface or implementations of other crates' traits. That would mean that the proposed NorFlashStorage of #9 would be better off in a separate crate. I have no strong feelings about this, this is just my observation and I wanted to start a discussion about this so we are all on the same page what the goals of embedded-storage are. It may even be a good idea to start with one crate to easily experiment and separate them later.
At the moment I am not fully convinced of the Storage trait's usefulness. I think traits are only useful if you plan to use it in a library that should be independent of the implementation. I don't really see that for Storage, because it seems to be geared towards the application which can just as easily use the concrete implementation rather than the trait.
Of course it may be that one of you had a specific use case in mind that I am missing and that is why I wanted to have a conversation about it.

I think this is a super valid point.
Personally my aim would be
Aiming for traits for specific flash types with one super-trait that "JustWorks" as non-volatile storage where the performance at best is equal, and at worst is magnitudes worse that using the type specific trait correctly
Personally i don't see why it could be one of the items you listed, rather than all of them?

I think traits are only useful if you plan to use it in a library that should be independent of the implementation.

This part i fully agree on, but i do see lots of usecases for a generic Storage trait? I am not sure i understand why you would think the performance is necessarily as bad as you make it out to be? Pretty much every application with uneven write cycles i can think of would have exactly the same performance as using the NorFlash trait, but with much less hassle on the user?

This was not about the performance, but about the Storage trait. I see the use case for your proposed NorFlashStorage implementation and I think it can be in this crate for the time being.
What I don't see is the use case for the trait. This does not have to mean that there is none, but I just don't see any.

Ahh, okay, that's my bad!
In that case i might be more inclined towards agreeing with you.
I have a few actual libraries where i need the user to provide a storage interface, and i while i guess i could just ask them for an actual NorFlashStorage, but i would much rather ask them for something implementing Storage, making it possible for them to wrap stuff up as they see fit?

I will stop pestering you about the performance issues. :P I am happy as long as it's behavior properly documented.

Hah, it's no problem. Im just trying to figure out if there is something i am missing here? But all my actual runs and implementations end up with exactly the same register reads/writes in both cases.

Actually, looking through my libraries it might be that i can live without it as a trait for most it.

But all my actual runs and implementations end up with exactly the same register reads/writes in both cases.

That's because you are using it correctly.
The way I would use it is to save records that are sent one by one to my device. These would have to be written and acknowledged one by one and this wouldn't go very well with this approach. My other use case would be data logging which would be equally as bad. I think have very different use cases in mind and there lies the confusion.
I looked into #12 and your MultiwriteNorFlash version would make this a lot better for most use cases. Maybe we should look into how to make this possible without specialization. May a NewType wrapper?
As I said I am not against a Storage trait in general, so if you need it that's fine with me.

Maybe we should look into how to make this possible without specialization. Maybe a NewType wrapper?

Sure, we could even make it as simple as MultiwriteNorFlashStorage. Naming might be off :p

Discussing scope, is atomicity and more controlled page erasure something this crate should concern itself with?
Granted, an erase-free interface would (even with conservative assumptions) be much more generic-heavy than the current one, but is this still the right place? (Typical limitations would be that erasing happens for full pages, writes are only possible in particular alignments, and even if overwrites were to have zeroing-only semantics, some implementations would not allow overwrites[1]).
[1]: Particular example I looked at was nrf52, which does allow zeroing overwrites, but only 181 total writes between two erasures of a 512 byte block, which combined with the requirement to write in 32bit words looks like a margin of error in case 0xffffffff are written twice than a realistic method to do zeroing overwrites (which might be used by applications to write bits one-by-one, which a generic API can't allow for these).

Scratch that, sorry for the noise -- the traits are already there and I just didn't find them / only looked at the top-level ones.


Add requireEmailVerification argument to $requireSignIn() firebase auth router helper

Description
This adds an argument (requireEmailVerification) to the $requireSignIn router helper in the angularfire auth service.
When set to true, this will fail if the firebase auth "emailVerified" property is false.
This is useful if you do not want users to access your app until they have verified their email address.
Code sample
_routerMethodOnAuthPromise: function(rejectIfAuthDataIsNull, rejectIfEmailNotVerified) {
      var self = this;

      // wait for the initial auth state to resolve; on page load we have to request auth state
      // asynchronously so we don't want to resolve router methods or flash the wrong state
      return this._initialAuthResolver.then(function() {
        // auth state may change in the future so rather than depend on the initially resolved state
        // we also check the auth data (synchronously) if a new promise is requested, ensuring we resolve
        // to the current auth state and not a stale/initial state
        var authData = self.getAuth(), res = null;
        if (rejectIfAuthDataIsNull && authData === null) {
          res = self._q.reject("AUTH_REQUIRED");
        }
        else if (rejectIfEmailNotVerified && !authData.emailVerified) {
            res = self._q.reject("EMAIL_NOT_VERIFIED");
        }
        else {
          res = self._q.when(authData);
        }
        return res;
      });
    },

I wonder if this would be more appropriate as an argument to $requireSignIn?
Is there a case where you would require email verification but not sign in? I don't think there is.

Good point! You're right it wouldn't make sense to need email verification but not sign in.
I updated it-- what do you think?

Looks good! Could we also get this into the test units?

Sure! :)
Btw, have you seen this error?
I'm getting it when running the tests, but I can look into what's going on as well.
  √ should return true once $loaded() promise is rejected
$ref
  √ should return Firebase instance it was created with

Chrome 56.0.2924 (Windows 8.1 0.0.0) ERROR
Uncaught Possibly unhandled rejection: {}
at .../angularfire/node_modules/angular-mocks/angular-mocks.js:250
Chrome 56.0.2924 (Windows 8.1 0.0.0) ERROR
Uncaught Possibly unhandled rejection: {}
at .../angularfire/node_modules/angular-mocks/angular-mocks.js:250
Chrome 56.0.2924 (Windows 8.1 0.0.0): Executed 50 of 274 ERROR (6.772 secs / 6.475 se
cs)

Thanks for the help!
I added some unit tests and updated the error code as you suggested.
All the Auth tests passed, but I still couldn't get the others working, so I ignored them.
FYI:
I was using node 5.2.0, but updated to 6.9.2, but still got that error.
My Chrome version is 56.0.2924.28 beta (64-bit).
Not very sure how to debug it, but if you have any suggestions, I'll try it out!

Looks great! Thanks for your contribution! I'm going to hold off on merging this in just yet since it updates documentation and I want to time it with the next release. I'll cut a new release before I head off for the holidays at the end of this week.
I'll also look into the testing issues. I was able to reproduce them with Node.js 4.4.5 / Chrome 55.0.2883. Thanks for the added setup info you shared.

FYI I just fixed the unit test issue with https://github.com/firebase/angularfire/pull/890.

Great! Thank you both for all the help and for looking at this so quickly! :)

This has been released as part of AngularFire 2.2.0. Thanks again for your contribution!


Fix typo in WinGet Releaser Example on Docs

[x] The commit message(s) follows the conventional commits guidelines.

This PR fixes a typo on the docs as it is meant to be installers-regex rather than installer-regex, as shown here. Copying over the incorrect example on my project caused it to fail.

@allcontributors please add @russellbanks for doc


[gatsby-theme-minimal-blog]: Failing to install the theme

Description
I'm getting an error when running:
npm install @lekoarts/gatsby-theme-minimal-blog

It seems it could be related to needing to update a few dependencies (react):
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: undefined@undefined
npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!   peer<EMAIL_ADDRESS>|| ^17.0.0" from<EMAIL_ADDRESS>npm ERR!   node_modules/gatsby
npm ERR!     peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@lekoarts/gatsby-theme-minimal-blog
npm ERR!       @lekoarts/gatsby-theme-minimal-blog@"*" from the root project
npm ERR!   1 more (react-dom)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@lekoarts/gatsby-theme-minimal-blog
npm ERR!   @lekoarts/gatsby-theme-minimal-blog@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See ~/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     ~/.npm/_logs/2021-05-31T21_46_46_081Z-debug.log

Steps to reproduce
Start a fresh theme install.
Expected result
NPM should install all the dependencies from the theme.
Actual result
It fails.
Environment
Run gatsby info --clipboard in your project directory and paste the output here:
  System:
    OS: macOS 11.3
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Shell: 3.2.2 - /usr/local/bin/fish
  Binaries:
    Node: 16.2.0 - /usr/local/bin/node
    npm: 7.13.0 - /usr/local/bin/npm
  Languages:
    Python: 2.7.16 - /usr/bin/python
  Browsers:
    Chrome: 90.0.4430.212
    Firefox: 85.0.1
    Safari: 14.1
  npmGlobalPackages:
    gatsby-cli: 3.6.0

I'm having the same issue. Looks like it is dependency related. I'm happy to try things if you have any suggestion. I'll start with checking versions for Babel related stuff.

Solved by running:
npm install<EMAIL_ADDRESS>npm install<EMAIL_ADDRESS>
Also, it's worth mentioning all these deprecated dependencies:
npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated and is no longer supported or maintained
npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated and is no longer supported or maintained
npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated<EMAIL_ADDRESS>This loader has been deprecated. Please use eslint-webpack-plugin
npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated<EMAIL_ADDRESS>Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated<EMAIL_ADDRESS>fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated<EMAIL_ADDRESS>Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated<EMAIL_ADDRESS>babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.
npm WARN deprecated<EMAIL_ADDRESS>Moved to 'npm install @sideway/address'
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated and is no longer supported or maintained
npm WARN deprecated<EMAIL_ADDRESS>Switch to 'npm install joi'
npm WARN deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.

I have a few questions:

Would these warnings go away if we updated this file? (having in consideration there aren't breaking changes).

What's the procedure we should follow to keep our site up to the base theme (@lekoarts/gatsby-theme-minimal-blog)? Should we just run npm update @lekoarts/gatsby-theme-minimal-blog or npm install x@latest would be preferred?

@cesards That unfortunately did not work for me.

I think the theme is broken anyways. It doesn't build the site when running gatsby develop (this issue):
 ~/W/W/cesards (master)> gatsby develop

 ERROR

(node:10101) [DEP_WEBPACK_LIBRARY_TEMPLATE_PLUGIN] DeprecationWarning: webpack.LibraryTemplatePlugin is deprecated and has been replaced by compilation.outputOptions.library or compilation.addEntry + passing a library option
(Use `node --trace-deprecation ...` to show where the warning was created)

 ERROR

(node:10101) [DEP_WEBPACK_AGGRESSIVE_SPLITTING_PLUGIN] DeprecationWarning: AggressiveSplittingPlugin is deprecated in favor of SplitChunksPlugin

success open and validate gatsby-configs - 0.105s
success load plugins - 3.599s
success onPreInit - 0.042s
success initialize cache - 0.010s
success copy gatsby files - 0.084s
success onPreBootstrap - 0.024s
success createSchemaCustomization - 0.023s
success Checking for changed pages - 0.001s
success source and transform nodes - 0.799s

 ERROR

Missing onError handler for invocation 'building-schema', error was 'Error: Cannot create as TypeComposer the following value: ImageFormat.'. Stacktrace was 'Error: Cannot create as TypeComposer the following value: ImageFormat.

Hi!
TL;DR see this SO for a longer explanation: https://stackoverflow.com/a/66620869/10164092
The theme is on the latest Gatsby v2 version (and the v3 release is under its way: https://github.com/LekoArts/gatsby-themes/issues/570) and thus has some older dependencies in them that declared React 16 as a peerDependency. npm 7 by default will try to be "clever" and install those. You'll want to keep the old behavior and use the --legacy-peer-deps flag. Unfortunately we also saw this in the v2 => v3 migration (https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v2-to-v3/#update-gatsby-version) so maybe going forward I'll change up the install instructions and add the flag by default.
The deprecated packages you mentioned are out of my control, those are all Gatsby dependencies. Updating to v3 should help there, too.

Hey @LekoArts, thanks for taking the time to provide more context on the issue. It makes sense.
I tried what you said on the other issue and I couldn't make it work: https://github.com/LekoArts/gatsby-themes/issues/596#issuecomment-852123250
I'll try using gatsby-starter to create a new site from the scratch, moving stuff I previously had. As a non-web developer, this might be a good exercise for me so I figure some stuff out. I'll be paying attention to your updates. Please let me know if there's anything else I could do to help,
Cesar

I had this problem too, the v3 update to gatsby didn't fixed it. Since I wanted to use the starter by using gatsby new then the npm --legacy-peer-deps flag didn't help. For reference to anyone else, what did help was install globally gatsby using yarn, and setting it as its default package manager, see https://www.gatsbyjs.com/docs/glossary/yarn/ .
If you want I can do a commit to the minimal-blog theme @LekoArts , also since I am already here, thanks for the great themes!


Determine means to temporarily bypass the web cache

Problem Description:
During 18 Jun 24's performance test, there were approximately 56K more requests of CloudFront than the middle tier.  A load balancer and web cache instances are between the two and even though it was disabled, not all capabilities appear to be disabled.  The scope of this ticket is to research how we could temporarily completely bypass the web cache during performance tests; i.e., configure CloudFront to the middle tier load balancer.
Expected Behavior/Solution:
Determine how to route requests through the web cache or not through it in a manner that only takes minutes for the switch to occur.
Requirements:
See above
Needed for promotion:
If an item on the list is not needed, it should be crossed off but not removed.
~- [ ] Wireframe/Mockup - Mike~

[ ] Committee discussions - Sarah
[ ] Feasibility/Team discussion - Sarah
[x] Backend requirements - None
[x] Frontend requirements - None
[ ] Are new regression tests required for QA - Amy
[x] Compels performance test?  No.  Just a research ticket.  Once implemented it still would not justify its own performance test.  Not one of its own.  Just check web cache request counts during/after a future performance test.
[ ] Questions
List of questions for discussions. Answers should be documented within the issue.

UAT/LUX Examples:
None.  If this ticket also becomes the implementation, one with AWS Console access could verify by checking request counts at various levels in the stack.  This could and should be done in advance of a performance test.
Dependencies/Blocks:
This issue neither blocks nor is blocked by another.
Related Github Issues:
18 Jun 24's performance test
Related links:
None
Wireframe/Mockup:
N/A

Based on a team conversation today, the decision on whether to implement this ticket is blocked on upcoming discussions on how to perform a performance test.  cc: @jffcamp, @prowns

skipped prioritization review - needs to be reviewed at tomorrows meeting.

I propose we close this ticket.  It falls within the 'false economy' argument and our plans to come up with a performance test that executes while the middle tier cache is enabled.

@brent-hartwig - thanks Brent. Last weeks UAT had a lot of issues. I have added this and other issues, which were not discussed, to next weeks UAT.

During the last performance test discussion, there was consensus that the new (yet-to-be-implemented) approach would leave this cache enabled.  I do not believe this needs to be pursued for the current performance test.  #stillProposeClose

Approved by UAT 9/12 to close


chore: add volunteer Ubaid Russell

Thanks for volunteering @UbaidRussell. Added small comments to the change.

Thanks for making the changes. Welcome!


Rewrite in Go

Pax will be rewritten in Go because of two main reasons:

While Nim is a really good language, its ecosystem of is still relatively small and in-the-works. I've tried three different zip libraries, two of those fail completely, the third doesn't work on Windows. (Or maybe I'm just too dumb?)
Cornstone, written in Go, will eventually be integrated into this project.

Haven't heard a while from the Cornstone guy, and the zip works now because I was previously too dumb.
Continuing in Nim for the time being. It's a fun language.


Which Account and Password Should Be Used to Connect to the ClickHouse Cluster from Outside?

I have installed the Altinity ClickHouse Operator through Helm and deployed a ClickHouse cluster using the following configuration without any additional customization of users or passwords.
apiVersion: clickhouse.altinity.com/v1
kind: ClickHouseInstallation
metadata:
  name: my-clickhouse
spec:
  defaults:
    templates:
      dataVolumeClaimTemplate: default-volume-claim
      logVolumeClaimTemplate: default-volume-claim
  configuration:
    clusters:
      - name: replicas-only
        templates:
          podTemplate: clickhouse-v23.8
          dataVolumeClaimTemplate: default-volume-claim
          logVolumeClaimTemplate: default-volume-claim
        layout:
          # shardsCount not specified, assumed = 1, by default
          replicasCount: 3
    zookeeper:
      nodes:
        - host: clickhouse-keeper.clickhouse.svc.cluster.local
          port: 2181
  templates:
    volumeClaimTemplates:
      - name: default-volume-claim
        provisioner: StatefulSet
        reclaimPolicy: Retain
        spec:
          storageClassName: csi-rbd-sc
          accessModes:
            - ReadWriteOnce
          resources:
            requests:
              storage: 20Gi
    podTemplates:
      - name: clickhouse-v23.8
        spec:
          containers:
            - name: clickhouse
              image: clickhouse/clickhouse-server:23.8
              volumeMounts:
                - name: default-volume-claim
                  mountPath: /var/lib/clickhouse
              resources:
                requests:
                  memory: "256Mi"
                  cpu: "200m"
                limits:
                  memory: "4096Mi"
                  cpu: "2000m"

Now, how can a service outside my Kubernetes cluster access ClickHouse, and which user and password should I use?
I am aware of two accounts:
The 'default' user, with a blank password, but testing has shown that it cannot be used.
The 'clickhouse_operator' user, with a password set during the Helm installation, but testing has also shown that it cannot be used.
I need help determining the correct credentials to access the ClickHouse cluster from an external service.

create a separate user with default profile
look to https://github.com/Altinity/clickhouse-operator/blob/master/docs/custom_resource_explained.md#specconfigurationusers for examples


Sysnonyms are not working in the web

@baimingze for some reason the text in the web is split and the synonyms are not shown. See the example:

Hi Yasset, could you send me the enrichmentinfo for me like this url "http://wwwdev.ebi.ac.uk/Tools/omicsdi/ws/enrichment/getEnrichmentInfo?accession=GPM32320004830&database=gpmdb"?
I don't have an enrichment DB in my local computer, and can't get the info from the url above.

gpmdb.zip

done


Observed Properties and Sensors 404 error with SensorThings API

Steps to Reproduce
Attempt to query a sensor or observed property by ID using the SensorThings API without authentication.
Expected Behavior
Individual observed properties and sensors should be able to be queried by anonymous users.
Actual Behavior
Owned observed properties and sensors return a 404 error if the user isn't signed in.
Any additional comments?
No response

https://github.com/hydroserver2/hydroserver-webapp-back/pull/172


Add a static demo with per-PR review

Problem
There's no place to try out this kernel yet.
Aside from off main, as new features are added, it would be nice to have something that reviewers can try out.
Suggested Improvement

[ ] add a dev-focused binder with jupyter-server-proxy
[ ] get set up for readthedocs (doesn't even require the mamb flag anymore to get a self-consistent environment)

Actually there is one in the https://github.com/jupyterlite/demo repo: https://github.com/jupyterlite/demo/blob/main/content/xeus-sqlite/simple-operations.ipynb
Alongside other xeus-based kernels.

Right, that's a starting point, but stuff has to hit main to show up there,
presumably...

I also note that this repo builds on jupyter-xeus/xeus-sqlite, and that repo has upstream fixes such as https://github.com/jupyter-xeus/xeus-sqlite/pull/119 that will need to be tracked here and in downstream demo environments if folk want to demo latest.

With the ongoing refactoring of the xeus-based lite kernels, it's also possible the lite assets will eventually be developed and shipped from the main jupyter-xeus/xeus-sqlite repo directly.
Making https://github.com/jupyterlite/xeus-sqlite-kernel not strictly necessary.


ModuleNotFoundError: No module named 'gpt_index'

Hi, friends.  I am trying to run the notebook example at examples/vector_indices/PineconeIndexDemo.ipynb , and am getting the following error trying to import StorageContext:
ModuleNotFoundError
Traceback (most recent call last)
[<ipython-input-3-0547849ae4a2>](https://localhost:8080/#) in <cell line: 2>()
      1 # initialize without metadata filter
----> 2 from gpt_index.storage.storage_context import StorageContext
      3
      4
      5 vector_store = PineconeVectorStore(

ModuleNotFoundError: No module named 'gpt_index'

I have received this error both locally now, and in a codespace that I believe is properly configured with the following dependencies:

Python 3.10.4
Flask 2.2.2
llama_index 0.5.27
pinecone-client
wget
langchain
openai

Any ideas? Thanks!

I had the same thought... but, unfortunately:
Exception has occurred: ModuleNotFoundError
No module named 'llama_index.storage'
  File "/workspaces/codespaces-flask/app.py", line 26, in <module>
    from llama_index.storage.storage_context import StorageContext
ModuleNotFoundError: No module named 'llama_index.storage'

an no worries at all!  thanks for your help

@smcady you'll want the newer version of llama index for storage context (currently its in alpha)
pip install llama-index==0.6.0.alpha6

Unfortunately, after upgrade to 0.6.0.alpha,
Exception has occurred: ImportError
cannot import name 'GPTSimpleVectorIndex' from 'llama_index' (/home/codespace/.python/current/lib/python3.10/site-packages/llama_index/__init__.py)
  File "/workspaces/codespaces-flask/app-old2.py", line 18, in <module>
    from llama_index import (GPTListIndex, GPTSimpleVectorIndex, LLMPredictor,
ImportError: cannot import name 'GPTSimpleVectorIndex' from 'llama_index' (/home/codespace/.python/current/lib/python3.10/site-packages/llama_index/__init__.py)

It has been renamed to GPTVectorStoreIndex
I highly recommend checking out the latest docs, a few interfaces changed
https://gpt-index.readthedocs.io/en/stable/guides/primer/usage_pattern.html

Ahh.  Thank you, @logan-markewich

@smcady thanks for your interest and apologies for the doc/lib mismatch.
We were in the process of a pretty big refactor, so didn't synchronize the two super well.  Right now if you pip install, you should get the latest 0.6.0 version, which should match what's on https://gpt-index.readthedocs.io/.
Going to close this issue for now, definitely feel free to open another one if issues pop up!

pip install gpt_index==0.4.15

thanks @Jeewant-Balyan  it worked


feat: assert_never macro

Please verify. this was made with AI. This is a convenience macro.

Hey andrewgazelka, if I understand correctly assert_never!(cond, ...) is exactly equivalent to assert_always(!cond, ...). Right now we are not planning to add such "wrapper macros" to our assertion APIs (except in the case of assert_always_greater_than etc, where the specialized versions can provide more guidance info to our fuzzer). So I'll close this for now.


Toggle takes up too much space on mobile

I don't like this. Some day I will fight with CSS and hopefully win.

The labels are each a span, and both are contained in a single span. The container span doesn't grow enough to contain them both if I have white-space: nowrap. It has plenty of room to grow further, it apparently just can't figure out how wide its content is.

fixed in main


Merge Custom Chart Code

Hi @krmorse  Can we get the Tech Services Version and the Community Version of this app so that we can take advantage of all the changes that are being made to the Community App?

hey @sherimoore the community version is here: https://github.com/RallyCommunity/CustomChart
i'm not sure what the permissions look like for the tech services one, but the code is here: https://github.com/RallyTechServices/CustomChart <-- can you see that?

Hi @krmorse I am able to get to both of these versions of the Custom Chart.  I was hoping that the two versions could be merged in the community so that we don't lose out on any future updates that might happen in the community.  Amy said Tyr was going to merge the code before he left 😞

Unfortunately, I'm not sure what all changes have been made to the tech services version of the app, and most likely the chart wouldn't be backwards compatible.  We wouldn't want to break a ton of existing customers' custom chart community apps.
I'm also not sure what exactly this sort of work might even look like going forward in the new world of HCL.  In general Rally engineering has not done this sort of work...


support aten::type_as in the pytorch frontend

I was trying to convert SSD model in mmdetection to Relay, and find the type_as is not supported. This PR adds support for aten::type_as operator.
@masahi

Thanks @randxie @t-vi

Hey the master CI failure seems relevant to this PR. Could you take a look? Thanks!

Followup https://github.com/apache/incubator-tvm/pull/5799


Create a demo that combines components

I like the components viewed separately on the Components part of the site, but it would be good to see a Demo section which integrates them together as an entire page. So it is more realistic for seeing it presented together (even as a screenshot preview on the LangUI homepage) and also to see how one would combine the elements.
Especially for someone like me who is new who Tailwind and I want to put side, main window and another sidebar together.
I was able to stitch this together for example.

It is unfortunately very limited as the sidebars don't animate though and there's no menu options flying out from the buttons e.g. user -> Settings or Logout.

Even if you put a demo on Codepen and link to it for the code and live preview, that would be useful.

I am adding releasing blocks using LangUI v2 soon, that will help with this. We are already using them here.
One problem with blocks is, they need opininated code, and a selected framework (like React) with state management etc. Our blocks will be React focused. Is that okay for now?

Oh thanks. A folder of runnable React examples there will be useful.
based on the Tailwind website, you could add a button for Explore Templates / Explore Examples next to Browse Components, which could go to a webpage gallery of the examples in the examples folder (even if they are just static screenshots like you have). Then it accomplishes by suggestion which is to see a full page combination of your components as soon as possible when exploring the LangUI homepage.
I still think it can be useful to have a static screenshot on your homepage below the Browse components button. Something like the one I sent of everything together (you can even pull in a favorite image from the examples folder).


[Bug]: Collection id is undefined

What happened?
If I use collection to do similiarity search i get "Required parameter collectionId was null or undefined when calling getNearestNeighbors". Due to issues with import on 1.5.11 I'm running 1.5.3
If i try to retrieve collection via getCollection method id is undefined.
Versions
chromadb node package 1.5.3, node 18.18.0
Relevant log output
Collection {
  name: 'test',
  id: undefined,
  metadata: null,
  api: ApiApi {
    basePath: 'http://localhost:8000',
    fetch: [AsyncFunction: fetch],
    configuration: Configuration {
      apiKey: undefined,
      username: undefined,
      password: undefined,
      authorization: undefined,
      basePath: 'http://localhost:8000'
    },
    options: {}
  },
  embeddingFunction: OpenAIEmbeddings {
    caller: AsyncCaller {
      maxConcurrency: 2,
      maxRetries: 6,
      onFailedAttempt: [Function: defaultFailedAttemptHandler],
      queue: [PQueue]
    },
    modelName: 'text-embedding-ada-002',
    batchSize: 512,
    stripNewLines: true,
    timeout: undefined,
    azureOpenAIApiVersion: undefined,
    azureOpenAIApiKey: undefined,
    azureOpenAIApiInstanceName: undefined,
    azureOpenAIApiDeploymentName: undefined,
    azureOpenAIBasePath: undefined,
    client: undefined,
    clientConfig: {
      apiKey: '{i-will-not-paste-that-here}',
      baseURL: undefined,
      dangerouslyAllowBrowser: true,
      defaultHeaders: undefined,
      defaultQuery: undefined
    }
  }
}

@Kubululo, Can you share a little more about your code:
Are you querying the collection similar to the code (from docs) below:
const result = await collection.query({
    queryEmbeddings: [[11.1, 12.1, 13.1],[1.1, 2.3, 3.2], ...],
    nResults: 10,
    where: {"metadata_field": "is_equal_to_this"},
})

Ref: https://docs.trychroma.com/usage-guide?lang=js#querying-a-collection
Also are you using some other libraries, e.g. langchain or llamaindex?

Hi @Kubululo, did you find a solution? I am facing exactly the same problem


Problem retrieving a data set from wave to a dataframe Spark 2.0

After running Spark 2.0
bin/spark-shell  --packages com.springml:spark-salesforce_2.10:1.0.6
With this code
`
val sqlContext = new SQLContext(sc)
// Reading Dataset
val saql = "q = load "0FbB00000000AN5KAM/0FcB00000000VDsKAM"; q = foreach q generate 'Att' as 'Att', 'Column2' as 'Column2', 'FantPos' as 'FantPos', 'G' as 'G', 'TD1' as 'TD1', 'TD2' as 'TD2', 'Tgt' as 'Tgt', 'Tm' as 'Tm';"
var sfWaveDF3 = sqlContext.
read.
format("com.springml.spark.salesforce").
option("username", "msmiXXXX@rpas.com").
option("password", "coSFSFSFSDFJvqBezm7mCgOQ0m").
option("saql", saql).
option("login","https://login.salesforce.com").
option("inferSchema", "true").
option("resultVariable","q").
load()
`
I get this error
java.lang.NoSuchMethodError: org.apache.http.client.methods.HttpPost.setConfig(Lorg/apache/http/client/config/RequestConfig;)V   at com.springml.salesforce.wave.util.HTTPHelper.post(HTTPHelper.java:50)   at com.springml.salesforce.wave.util.HTTPHelper.post(HTTPHelper.java:28)   at com.springml.salesforce.wave.impl.WaveAPIImpl.query(WaveAPIImpl.java:56)   at com.springml.salesforce.wave.impl.WaveAPIImpl.queryWithPagination(WaveAPIImpl.java:72)   at com.springml.salesforce.wave.impl.WaveAPIImpl.queryWithPagination(WaveAPIImpl.java:29)   at com.springml.spark.salesforce.DatasetRelation.queryWave(DatasetRelation.scala:69)   at com.springml.spark.salesforce.DatasetRelation.read(DatasetRelation.scala:54)   at com.springml.spark.salesforce.DatasetRelation.<init>(DatasetRelation.scala:48)   at com.springml.spark.salesforce.DefaultSource.createRelation(DefaultSource.scala:79)   at com.springml.spark.salesforce.DefaultSource.createRelation(DefaultSource.scala:53)   at com.springml.spark.salesforce.DefaultSource.createRelation(DefaultSource.scala:39)   at org.apache.spark.sql.execution.datasources.DataSource.resolveRelation(DataSource.scala:315)   at org.apache.spark.sql.DataFrameReader.load(DataFrameReader.scala:149)   at org.apache.spark.sql.DataFrameReader.load(DataFrameReader.scala:122)

It seems, Apache HTTP library is changed in Spark 2.0. Will update the library, run against Spark 2.0 and update this ticket.
Thanks for creating the issue

Thanks - I did try downgrading to
docker run --rm -it -p 4040:4040 gettyimages/spark:1.6.2-hadoop-2.6 bin/spark-shell --packages com.springml:spark- salesforce_2.10:1.0.6
Same error so maybe the new library was introduced after Spark 1.4 or 1.5

No. We've been using Spark Salesforce connector with Spark 1.6.2 without any issues. Do you have any additional packages along with Spark Salesforce connector? Or is it a custom build Spark image?

This error also exists on Spark 1.6 with the CDH 5.7.0 distribution. It appears an interval version of this library is included which does not contain the needed function.

@malsmith Sorry for late reply. Could please test this with latest release and let us know for any issues

This still seems not fixed. I am getting the same issue after moving to com.springml:spark-salesforce_2.11:1.1.0 on spark 2.0+ cluster

@leletan - Are you getting this issue in Spark 2.0 from CDH distribution or with vanilla Apache Spark?

I am getting this when deploying the big jar onto a docker-compose local cluster using https://github.com/gettyimages/docker-spark/blob/master/docker-compose.yml

Please provide me the simple steps to start docker-compose with fat jar. Do we need to update the compose files to include spark-salesforce connector?

sure.

docker-compose up of the previous mentioned docker-compose.yml.
sbt assembly the job jar, and copy it into the running docker instances (spark master and spark worker)
docker exec -it spark_master bin/spark-submit
--master spark://master:6066
--deploy-mode cluster
--class
--executor-memory 512M
--driver-memory 512M
--total-executor-cores 2

the build.sbt looks like:
...
libraryDependencies ++= {
val sparkVersion = "2.1.0"
Seq(
// Apache Spark dependencies
"org.apache.spark" %% "spark-sql" % sparkVersion % "provided",
// Salesforce integration
"com.springml" % "spark-salesforce_2.11" % "1.1.0",

...

The job itself is very similar to the demo in readme

@leletan I am able to reproduce this issue. Hadoop 2.7.3 contains very old httpclient jar
hadoop-2.7.3/share/hadoop/common/lib/httpclient-4.2.5.jar
hadoop-2.7.3/share/hadoop/tools/lib/httpclient-4.2.5.jar

But we are shipping he connector with httpclient-4.5.jar.
In the docker container SPARK_DIST_CLASSPATH has the below paths
# echo $SPARK_DIST_CLASSPATH
/usr/hadoop-2.7.3/etc/hadoop/*:/usr/hadoop-2.7.3/share/hadoop/common/lib/*:/usr/hadoop-2.7.3/share/hadoop/common/*:/usr/hadoop-2.7.3/share/hadoop/hdfs/*:/usr/hadoop-2.7.3/share/hadoop/hdfs/lib/*:/usr/hadoop-2.7.3/share/hadoop/hdfs/*:/usr/hadoop-2.7.3/share/hadoop/yarn/lib/*:/usr/hadoop-2.7.3/share/hadoop/yarn/*:/usr/hadoop-2.7.3/share/hadoop/mapreduce/lib/*:/usr/hadoop-2.7.3/share/hadoop/mapreduce/*:/usr/hadoop-2.7.3/share/hadoop/tools/lib/*

This overwrites the httpclient present in spark-salesforce assembly jar.
I don't think reverting the httpclient to old version is right solution for this.
I've verified this vanilla Apache spark and spark comes along with HDP and this connector is working fine.
Could you please try using this in any other spark apart from this docker image?

Sure. Thanks for the advices!

@leletan Please reopen this issue if you face this issue in other spark platforms

I know this is closed, but noticed that this issue still happens in spark 2.4.0. Works fine with 2.4.4, only thing is that I can go as far as 2.4.0 because of CDH. Was wondering if there is a workaround. Thanks


Redis Vectorstore: Redis.from_texts_return_keys() got multiple values for argument 'cls'

System Info
Python 3.10.4
langchain==0.0.171
redis==3.5.3
redisearch==2.1.1

Who can help?
@tylerhutcherson
Information

[ ] The official example notebooks/scripts
[x] My own modified scripts

Related Components

[ ] LLMs/Chat Models
[ ] Embedding Models
[ ] Prompts / Prompt Templates / Prompt Selectors
[ ] Output Parsers
[ ] Document Loaders
[X] Vector Stores / Retrievers
[ ] Memory
[ ] Agents / Agent Executors
[ ] Tools / Toolkits
[ ] Chains
[ ] Callbacks/Tracing
[ ] Async

Reproduction
I was able to override issue #3893 by temporarily disabling the  _check_redis_module_exist, post which I'm getting the below error when calling the from_texts_return_keys within the from_documents method in Redis class. Seems the argument cls is not needed in the from_texts_return_keys method, since it is already defined as a classmethod.
File "/workspaces/chatdataset_backend/adapters.py", line 96, in load
    vectorstore = self.rds.from_documents(documents=documents, embedding=self.embeddings)
  File "/home/codespace/.python/current/lib/python3.10/site-packages/langchain/vectorstores/base.py", line 296, in from_documents
    return cls.from_texts(texts, embedding, metadatas=metadatas, **kwargs)
  File "/home/codespace/.python/current/lib/python3.10/site-packages/langchain/vectorstores/redis.py", line 448, in from_texts
    instance, _ = cls.from_texts_return_keys(
TypeError: Redis.from_texts_return_keys() got multiple values for argument 'cls'

Expected behavior
Getting rid of cls argument from all the Redis class methods wherever required. Was able to solve the issue with this fix.

This is a high priority issue. I ran into this myself yesterday.
Thanks for creating the issue.

Thanks, @tylerhutcherson If you could assign this to me, I can solve it along with #4899 and merge it.

Yes, please do. Tag me in the PR review!

@iamadhee FYI https://github.com/hwchase17/langchain/pull/4

@tylerhutcherson Have added #4932


error creating the lustre FS if cluster still starting (ithink)

Or i think that is. It is at the end when try to save .elasticluster/storage/icel-bcbiolustre.ssh_config, the storage folder/file doesn't exist yet.
Waiting for stack to launch (this will take a few minutes)..........................................................................................
Traceback (most recent call last):
File "/home/lpantano/soft/myconda/bin/bcbio_vm.py", line 4, in
import('pkg_resources').run_script('bcbio-nextgen-vm==0.1.0a0', 'bcbio_vm.py')
File "/home/lpantano/soft/myconda/lib/python2.7/site-packages/setuptools-12.0.5-py2.7.egg/pkg_resources/init.py", line 696, in run_script
File "/home/lpantano/soft/myconda/lib/python2.7/site-packages/setuptools-12.0.5-py2.7.egg/pkg_resources/init.py", line 1621, in run_script
File "/home/lpantano/soft/myconda/lib/python2.7/site-packages/bcbio_nextgen_vm-0.1.0a0-py2.7.egg/EGG-INFO/scripts/bcbio_vm.py", line 290, in
          File "/home/lpantano/soft/myconda/lib/python2.7/site-packages/bcbio_nextgen_vm-0.1.0a0-py2.7.egg/bcbiovm/aws/icel.py", line 164, in create
            File "/home/lpantano/soft/myconda/lib/python2.7/site-packages/bcbio_nextgen_vm-0.1.0a0-py2.7.egg/bcbiovm/aws/icel.py", line 523, in _write_ssh_config
            IOError: [Errno 2] No such file or directory: '/home/lpantano/.elasticluster/storage/icel-bcbiolustre.ssh_config'

Lorena;
Thanks for the heads up on the problem. This was an issue with our new unified storage setup. I fixed so it should hopefully work as expected on future runs. Thanks again.


utc_to_local returning UTC identifier

I'm using utc_to_local to convert a time in UTC to "America/Vancouver"
The time is correct, however it still displays +0 UTC at the end. How do I get this to display the correct UTC offset?
>> start_time
=> Thu, 25 Sep 2014 18:30:00 UTC +00:00
>> tz = TZInfo::Timezone.get("America/Vancouver")
=> #<TZInfo::DataTimezone: America/Vancouver>
>> tz.utc_to_local(start_time)
=> Thu, 25 Sep 2014 11:30:00 UTC +00:00
>>

Running rails 2.3.18 and Ruby 1.8.7

To complete philr answer, without rails:
time = Time.utc(2014,9,25,18,30)
utc_total_offset = timezone.period_for_utc(time).utc_total_offset
time.getlocal(utc_total_offset)


docker hub image needs a rebuild

Issue:
building now fails with
Making site... Build failed: Traceback (most recent call last):
  File "/usr/local/lib/python3.8/dist-packages/foliant/backends/slate.py", line 253, in make
    r = run(
  File "/usr/lib/python3.8/subprocess.py", line 512, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command 'bundle exec middleman build --clean' returned non-zero exit status 1.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.8/dist-packages/foliant/backends/slate.py", line 262, in make
    raise RuntimeError(e.output.decode('utf8', errors='ignore'))
RuntimeError: /var/lib/gems/2.7.0/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86:in `block in materialize': Could not find minitest-5.14.2 in any of the sources (Bundler::GemNotFound)
	from /var/lib/gems/2.7.0/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in `map!'
	from /var/lib/gems/2.7.0/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in `materialize'
	from No result returned by backend

resolution:
The latest slate version (2.8.0) bumped middleman to 4.3.11 which requires a few more gems,
No code changes, but foliant/foliant needs a rebuild to install all the new gems.
temporary fix for projects, change your Dockerfile to this
FROM foliant/foliant:full
RUN mkdir -p /usr/src/app/dependency_files/slate/ \
    && cd /usr/src/app/dependency_files/slate/ \
    && wget -O ./Gemfile https://raw.githubusercontent.com/slatedocs/slate/main/Gemfile \
    && wget -O ./Gemfile.lock https://raw.githubusercontent.com/slatedocs/slate/main/Gemfile.lock \
    && apt install -y zlib1g-dev ruby-full \
    && gem install bundler \
    && bundle install

and run
docker-compose build

or rebuild your own foliant:foliant from scratch

This is also the case with the current foliant/foliant:full image on docker hub:
Parsing config... Done
Applying preprocessor plantuml... Done
Applying preprocessor flatten... Done
Applying preprocessor _unescape... Done
Making site... Build failed: Traceback (most recent call last):
  File "/usr/local/lib/python3.8/dist-packages/foliant/backends/slate.py", line 253, in make
    r = run(
  File "/usr/lib/python3.8/subprocess.py", line 512, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command 'bundle exec middleman build --clean' returned non-zero exit status 1.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.8/dist-packages/foliant/backends/slate.py", line 262, in make
    raise RuntimeError(e.output.decode('utf8', errors='ignore'))
RuntimeError: `/` is not writable.
Bundler will use `/tmp/bundler20210201-20-10q3esc20' as your home directory temporarily.
/var/lib/gems/2.7.0/gems/bundler-2.2.6/lib/bundler/spec_set.rb:87:in `block in materialize': Could not find rouge-3.26.0 in any of the sources (Bundler::GemNotFound)
        from /var/lib/gems/2.7.0/gems/bundler-2.2.6/lib/bundler/spec_set.rb:81:in `map!'
        from /var/lib/gems/2.7.0/gems/bundler-2.2.6/lib/bundler/spec_set.rb:81:in `materialize'
        from /var/lib/gems/2.7.0/gems/bundler-2.2.6/lib/bundler/definition.rb:175:in `specs'
        from /var/lib/gems/2.7.0/gems/bundler-2.2.6/lib/bundler/definition.rb:245:in `specs_for'
        from /var/lib/gems/2.7.0/gems/bundler-2.2.6/lib/bundler/definition.rb:227:in `requested_specs'
        from /var/lib/gems/2.7.0/gems/bundler-2.2.6/lib/bundler/runtime.rb:91:in `block in definition_method'
        from /var/lib/gems/2.7.0/gems/bundler-2.2.6/lib/bundler/runtime.rb:20:in `setup'
        from /var/lib/gems/2.7.0/gems/bundler-2.2.6/lib/bundler.rb:148:in `setup'
        from /var/lib/gems/2.7.0/gems/bundler-2.2.6/lib/bundler/setup.rb:20:in `block in <top (required)>'
        from /var/lib/gems/2.7.0/gems/bundler-2.2.6/lib/bundler/ui/shell.rb:136:in `with_level'
        from /var/lib/gems/2.7.0/gems/bundler-2.2.6/lib/bundler/ui/shell.rb:88:in `silence'
        from /var/lib/gems/2.7.0/gems/bundler-2.2.6/lib/bundler/setup.rb:20:in `<top (required)>'
        from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'
        from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'

No result returned by backend

@anorm sorry for late reply!
We're taking gemfile from slate repo, so all gems should be installed. I just checked, foliant make site -w slate works fine for me. Do you still have this issue?

The issue is the docker container is built with an older Gemfile to build the dependencies and then a newer slate is checked out when making the docs which causes the dependency issue
Steps to reproduce:
git clone https://github.com/foliant-docs/foliant_project_template.git
cd foliant_project_template
docker-compose build
docker-compose run --rm foliant make site -w slate

Even if someone just builds and pushes a new version of foliant/foliant:full without any changes it should start working as it will pull the newer Gemfile.

@BrianMowrey
Yes, that's a limitation, but you can always add steps for updating the dependencies from fresh gemfile to your own Dockerfile, e.g.
FROM foliant/foliant:full

RUN mkdir -p /usr/src/app/dependency_files/slate/ \
    && cd /usr/src/app/dependency_files/slate/ \
    && wget -O ./Gemfile https://raw.githubusercontent.com/slatedocs/slate/main/Gemfile \
    && wget -O ./Gemfile.lock https://raw.githubusercontent.com/slatedocs/slate/main/Gemfile.lock \
    && bundle install

We rebuild the image quite regularly, each time with fresh Gemfile. We also have personal pipelines with Slate projects, so if Slate issues new version and it breaks the image, we should notice, but of course we will be grateful for a friendly nudge if you notice it first :}

yes, that's all this is, a friendly nudge saying the docker hub image isn't working.   Maybe something is broken on your automatic build/push as it has been ~4 months and the docker image is still broken. We've been using the workaround I mentioned since and it's been fine but frustrating for new projects following the documentation to get started.

@BrianMowrey wait, you STILL have this problem? Everything works fine when I try your example:
git clone https://github.com/foliant-docs/foliant_project_template.git
cd foliant_project_template
docker-compose build
docker-compose run --rm foliant make site -w slate
Cloning into 'foliant_project_template'...
remote: Enumerating objects: 11, done.
remote: Counting objects: 100% (11/11), done.
remote: Compressing objects: 100% (7/7), done.
remote: Total 11 (delta 1), reused 11 (delta 1), pack-reused 0
Unpacking objects: 100% (11/11), done.
Building foliant
Step 1/1 : FROM foliant/foliant:full
 ---> f320ab0b4ffe

Successfully built f320ab0b4ffe
Successfully tagged foliant_project_template_foliant:latest
Creating foliant_project_template_foliant_run ... done
Parsing config... Done
Applying preprocessor flatten... Done
Applying preprocessor _unescape... Done
Making site...
Project built successfully.

Done
────────────────────
Result: New_Foliant_Project-2021-03-08.slate/

Have you pulled and built the latest image?

hmm, I am pretty sure I had last time, but I cleaned my docker system and my test case works now.
Thanks!


question model

sry ,you have no discussion button ;)
is it possible to choose a local gguf model ?

hello
yes it is possible, I chose to work with hp loader because it was slightly lighter but you can adapt the code to select a gguf model.


Implement connectFromBits in ChiselEnum

This is necessary to use ChiselEnum in aggregates where things are
casted using .asTypeOf
I also noticed that ReinterpretCast and AsTypeOf testers were the same so I deleted the duplicates.
We should also consider removing the warning when you cast a non-literal UInt to the enum type because this is called every time you cast, this is especially problematic when you put enums in aggregates. Alternatively, it could be turned on for the API MyEnum(someUInt), but off whenever using .asTypeOf...
@hngenc if you could take a look that would be great

Related issue:

Type of change: bug fix

Impact: API addition (no impact on existing code)

Development Phase: implementation
Release Notes
Fix bugs in casting to ChiselEnums

This change looks good to me. I'm also fine with either turning off the warning completely, or turning it off only when writing MyEnum(someUInt). I suppose a great many people will ignore warnings anyway.
In the future, it may also be nice to automatically add asserts to make sure that ChiselEnums aren't invalid.


Not possible to specify endpoint versions

Hello,
I'm trying to call reports.getReportDocument operation's specific version 2021-06-30.
const report = await sellingPartner.callAPI({
            operation: 'reports.getReportDocument',
            path: {
                reportDocumentId: reportDocumentId,
            },
            options:{
                version:'2021-06-30'
            }
        });

But typescript failing because there is no options field on the definition of ReqParams

How can I specify the version on callApi call?

Fixed with PR #81


Error requesting account balance

Description
Request account balance from the accounts screen and errors when there is an account checked.

Steps to reproduce
See above
Additional context
No response
Hedera network
other
Version
0.9.0-alpha.1
Operating system
No response

Please link test case for this issue.

Getting the balance works for the 9401-testnet account


Add the Syscalls trait to libtock_platform.

Syscalls is a trait representing Tock's system call API. It will be implemented by both libtock_runtime (included by TBF binaries) and libtock_fake (included by unit tests). It will allow us to replace the real Tock kernel with a fake Tock kernel for testing purposes.
Syscalls is designed to introduce no overhead over the system call assembly logic. For allow, command, and subscribe, it is based on Tock's Driver trait. A higher-level interface over Tock's system calls, for use by libtock_core and client code, will be introduced in a later PR.

The build issue is #225 and is unrelated to this PR; please review this when you get a chance.

bors r+


Masked content renders visible

Hi!
Part of a text layer that should be hidden renders visible with pdf.js, as you can see here:
https://s3-eu-west-1.amazonaws.com/epaper-dev/pdfjs/dn_dagens-nyheter_page_2015-04-07_b.pdf.
It should look like this:
http://postimg.org/image/5b506gh15.
Tested in browser versions:
Safari: 8.0.4 (106<IP_ADDRESS>)
Firefox: 36.0.4
Chrome: 41.0.2272.118 (64-bit)
Operatingsystem:
OSX Yosemite 10.10.2 (14C109)

Closing as fixed by PR #6723.


React, NextJS, Angular or other JS projects with own server

Is there an existing issue for this?

[X] I have searched the existing issues

Is your feature request related to a problem?
All those frameworks provide their own server with options to build and start or to use dev which includes watch. After that, we go to localhost:3000 and test from there.
What I would like is to issue ddev config which can recognise React/NextJS/Angular/etc type of project, preconfigure containers and router and serve the web site on myreact.ddev.site
Describe your solution
There may be two approaches:

One that excludes the web container and uses some app to serve like npm run dev which is then exposed as the projects entry point for the domain, i.e the npm port 3000 (or any other) is exposed as 80 by the router, removing the need for the port.

The other, where the nginx is used to listen to port 3000 and expose it to the world as the port 80

Describe alternatives
It would be even greater if we could use additional FQDN which could be tied to ports.
I.e. we may have a NextJS web app (tested as build and as dev), backed in PHP (API), some JS service and other stuff like some db, phpMyAdmin, MailHog, etc.
The proposition would be to be able to assign an arbitrary port to FQDN, e.g.
(tech)   container: port FQDN
---------------------------------------
(nextjs)     build: 80   mynext.ddev.site
(nextjs)       dev: 80   dev.mynext.ddev.site
(PHP)          api: 80   api.mynext.ddev.site
(nodejs)   service: 80   service.mynext.ddev.site
(PHP)           db: 3306 mynext.ddev.site
(PHP)          dba: 80   dba.mynext.ddev.site
(MailHog)      hog: 80.  hog.mynext.ddev.site

Additional context
The idea is to mimic the real-world setup as closely as possible.
It also opens the possibility to use/expose more services by domain. Instead of hacking my way through nginx.conf and/or port exposing/assigning, if this is not too complicated it could lower the tech skill needed to have that up and going.
Also, there are many developers now using various JS tech stacks who can benefit from such a local environment and be able to add other services like different db's and to exlopre.

Duplicate of #4854  ?

Haven't found that one, I was looking for 'React'.
This issue extends to the idea that services ports can be mapped to FQDN and also enable exposing the service port (3000) to the custom domain port, 80 or any other.
I'd also like the option to recognise some of the most popular frameworks React/Angular/Vue/NextJS and be open to adding more to remove the traction from easily starting the JS project with ddev.

I'd also like the option to recognise some of the most popular frameworks React/Angular/Vue/NextJS and be open to adding more to remove the traction from easily starting the JS project with ddev.

#4854 is the place to "vote" for you prefered framework and what port it prefers.
There's also the option of creating an addon that might solve your immediate use case. The below addons both expose ports used by javascript.

https://github.com/ddev/ddev-browsersync
https://github.com/torenware/ddev-viteserve

@tyler36 Thanks, these may deserve mentioning in the docs as they are quite valuable. You gave me some ideas about how can I solve it and I agree that the rest should be discussed there.
The part with the FQDN and ports still make sense and is new idea/feature request here?

@macmladen there are so many different ways to use these projects.
I do think that

#4854

is probably the essence of what you're looking for (using nginx as a front-end for a server-side JS platform like node?)
But if you're looking for front-end things there's nothing actually to be done.
As @tyler36 points out, DDEV already has capabilities that are along the line you're looking for, see https://ddev.readthedocs.io/en/latest/users/extend/customization-extendibility/#using-nodejs-with-ddev - the web_extra_daemons and web_extra_exposed_ports do all the things; the only problem is if you don't want the result exposed on a non-standard port.

No response to conversation, and https://github.com/ddev/ddev/issues/4854 may be what's desired here. @macmladen if you want to solve a specific problem we can go ahead and discuss that more. You're invited to Discord as well, https://discord.gg/hCZFfAMc5k


364 nextcloud integration get images

This PR introduces utility functions for fetching and uploading images to Nextcloud as well as a webdav test component for testing this functionality.
webdav-test.tsx serves as an example component to showcase the image upload and fetch functionality with webdav.
When the functionality has been implemented in the layers and the gallery for the website the component can be removed.
It is currently available at /webdav
This PR depends on #320.

[ ] References to issues, e.g. close #X, are in the commit messages.
[ ] The buildserver is happy.
[x] The PR is rebased with current master.

Checklist

[ ] I added unit tests for my code
[x] I fully described what my PR does in the documentation
(not in the PR description)
[x] I fixed all affected documentation
[x] I fixed all affected decisions
[x] I added code comments, logging, and assertions as appropriate
[ ] I translated all strings visible to the user
[x] I mentioned every code or binary not directly written or done by me in reuse syntax

Review

[ ] I've tested the code
[ ] I've read through the whole code
[ ] Documentation is conforming to our Documentation Guidelines
[ ] Examples are well chosen and understandable
[ ] Code is conforming to our Coding Guidelines
[ ] Code is consistent to our Design Decisions

jenkins build please

Thx, great job. Please create an issue to remove the old examples when they are not needed anymore.


Fahrenheit Temp at lowest is 63

When in Midea app it is 62.

The Default unit is Celsius. The AC always expects a celsius temperature.
The Formula from Celsius to Fahrenheit is:
F = C * 1.8 + 32
In your example: 17C = 62.6F
HomeKit can't Show 62.6 so the number is round to the nearest integer 63.
Maybe Midea app round it down.
16C = 60.8F will round to 61
17C = 62.6F will round to 63
18C = 64.4F will round to 64
etc....

The display on the unit rounds down too - might want to align for consistency. I get it, but people would notice :)
[https://i.imgur.com/zf87pbX.jpg]
Benjamin Wesley Thomas
m +1<PHONE_NUMBER> | f +1<PHONE_NUMBER>
e @.***<file:///private/var/mobile/Library/Mobile%20Documents/com~apple~CloudDocs/iOS%20Signatures/EmailSignature1.html#>
w www.benjaminwesleythomas.com<file:///private/var/mobile/Library/Mobile%20Documents/com~apple~CloudDocs/iOS%20Signatures/EmailSignature1.html#>
[https://i.imgur.com/LekBgmL.png]https://twitter.com/benjaminwthomas [https://i.imgur.com/lyRQWJR.png] https://www.linkedin.com/in/benjaminwesleythomas/

From: Yossi Hillali @.>
Sent: Thursday, February 10, 2022 10:22:20 AM
To: hillaliy/homebridge-midea-air @.>
Cc: Benjamin Thomas @.>; Author @.>
Subject: Re: [hillaliy/homebridge-midea-air] Fahrenheit Temp at lowest is 63 (Issue #48)
Closed #48https://github.com/hillaliy/homebridge-midea-air/issues/48.
—
Reply to this email directly, view it on GitHubhttps://github.com/hillaliy/homebridge-midea-air/issues/48#event-6043123532, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALRHQ3PE6ARS7JI7F56S2ITU2PJ2ZANCNFSM5N5RH7WQ.
You are receiving this because you authored the thread.Message ID: @.***>

try beta 1.4.4-beta.1

Fix with version 1.4.4


Validate amount length

Context
ABA files impose a 10-character limit on amounts and credit/debit total amounts.
Change

Apply validations to reflect this limitation.
Sprinkle magic frozen_string_literal comments throughout. 🪄
Tweak Changelog Markdown formatting (to appease Prettier).
Bump version and update changelog.

Thanks @zubin


No module named 'dnnlib'

I kept running into the error below using the basic example script.
Traceback (most recent call last):
  File "d:\Python\LSD\first.py", line 1, in <module>
    from lucidsonicdreams import LucidSonicDream
  File "D:\python\LSD\lsd\lib\site-packages\lucidsonicdreams\__init__.py", line 1, in <module>
    from .main import *
  File "D:\python\LSD\lsd\lib\site-packages\lucidsonicdreams\main.py", line 32, in <module>
    import dnnlib
ModuleNotFoundError: No module named 'dnnlib'

changed the main.py line 32-33 from
import dnnlib
from dnnlib.tflib.tfutil import *

to
from stylegan2 import dnnlib
from stylegan2.dnnlib.tflib.tfutil import *

on my computer and it seems to have fixed that issue

For everybody that didnt get it to work with the above mentioned fix try this(should work on windows and linux):
Use python 3.7, clone the stylegan2 repo and copy dnnlib in the /lib/site-packages/ folder of your env.
Last but not least pip install ffmpeg.
This is not my fix I found it in an comment on reddit form /u/RedditWithBoners

take a look a this , the pip install work for me and the bug was fix
https://github.com/podgorskiy/dnnlib

I worked around this by just putting my script in the stylegan folder

No code editing needed:
just copy the dnnlib folder and drag it outside of stylegan2 folder

ModuleNotFoundError: No module named 'torch_utils.persistence' is the next issue i had. any thoughts?

ModuleNotFoundError: No module named 'torch_utils.persistence'
Hey there! It seems like you're encountering a ModuleNotFoundError related to torch_utils.persistence. This error typically occurs when the required module is missing from your environment.
Resolution Steps:

Check Dependencies: Ensure that you have all the necessary dependencies installed in your environment. In this case, it seems like you might be missing the torch_utils module.

Installation: If torch_utils is a separate package, you might need to install it using a package manager like pip:
pip install torch-utils


Error 400: Bad Request when attempting to query the Azure Resource Graph

@azure/arm-resourcegraph:
^2.0.0:
Windows:
[ ] nodejs

v14.15.0:

Describe the bug
When using @azure/ms-rest-nodeauth and @azure/arm-resourcegraph, it seems that authentication using either interactiveLogin() or loginWithAppServiceMSI() succeeds and a token is returned. However, when attempting to continue and send a simple query to Azure Resource Graph, such as "summarize count() by location", the application fails with an obscure error:
body:{error: {…}}
code:'BadRequest'
message:'Please provide below info when asking for support: timestamp = 2020-12-04T02:30:28.0616308Z, correlationId = 136ab126-266c-481d-832d-ea2ad5dce118.'
request:WebResource {streamResponseBody: false, url: 'https://management.azure.com/providers/Microso…ResourceGraph/resources?api-version=2019-04-01', method: 'POST', headers: HttpHeaders, body: '{"subscriptions":["xxxxxxxx-xxxxxxxx-xxxxxxxx-xxxxxxxx-xxxxxxxx"],"query":"summarize count() by location"}', …}
response:{body: '{"error":{"code":"BadRequest","message":"Pleas… '271f689e-def0-4696-9bf4-026b8f58822e'."}]}}', headers: HttpHeaders, status: 400}
stack:'Error: Please provide below info when asking for support: timestamp = 2020-12-04T02:30:28.0616308Z, correlationId = 136ab126-266c-481d-832d-ea2ad5dce118.\n    at new RestError (C:\source\repos\myrepo\node_modules\@azure\ms-rest-js\dist\msRest.node.js:1403:28)\n    at C:\source\repos\myrepo\node_modules\@azure\ms-rest-js\dist\msRest.node.js:2528:37\n    at processTicksAndRejections (internal/process/task_queues.js:93:5)'
statusCode:400
proto:Error
To Reproduce
Steps to reproduce the behavior:
const msRestNodeAuth = require("@azure/ms-rest-nodeauth");
const { ResourceGraphClient, ResourceGraphModels, ResourceGraphMappers } = require("@azure/arm-resourcegraph");

msRestNodeAuth.interactiveLogin().then((creds) => {
        const client = new ResourceGraphClient(creds);
        res = client.resources(
            {
                subscriptions: ['xxxxxxxx-xxxxxxxx-xxxxxxxx-xxxxxxxx-xxxxxxxx'],
                query: 'summarize count() by location'
            }).then((res) => {
                console.log(res);
            }).catch((err) => {
                console.error(err);
            });
        });
}).catch((err) => {
    console.error(err);
});

Expected behavior
A 200 OK should be returned with relevant data.

I see that @KarishmaGhiya was the last contributor 2 years ago. Any ideas?

We were inputting tenant id instead of subscription ID.

thanks @frangenesys close it.


Check if lexer index is out of bounds before checking for DotDot

When the lexer sees the dot, it increments the index into the bytes
array and then use the incremented index to check for another dot.
However, it did not check if this was out-of-bounds, meaning if a dot
is followed by EOF, the lexer would panic with an array OOB.

Fixed :+1:


allow to pause RTEs

we need a mechanism to pause RTEs from pushing updates. May be anything ranging from pause support on RTEs, stopping RTEs, scaling down/removing the RTE daemonset.
The pause/unpause mechanism should be trivially controllable editing the NUMAResourcesOperator.Spec

/assign @shajmakh

addressed by https://github.com/openshift-kni/numaresources-operator/pull/700