vba_chroropleth does not allow None

One more from playing with this for a workshop this past week. It seems the function throws an error if alpha_mapclassify and rgb_mapclassify don't have a value (the default None don't seem to work). I picked this up from the example notebook, where everything is passed and it works great, but from the docs, it seems to imply that it'd be just fine by passing the variables. Is that the case? If so, happy to open up a separate issue.
referred to in #45

Can you share here some reproducible example of this bug? I'm not really sure that I follow. I tried to run this function removing both arguments and the results were generated as follows:
import splot
import libpysal as lp
from libpysal import examples
import geopandas as gpd
import pandas as pd
import matplotlib.pyplot as plt
import matplotlib
import numpy as np

% matplotlib inline

link_to_data = examples.get_path('columbus.shp')
gdf = gpd.read_file(link_to_data)

x = gdf['HOVAL'].values
y = gdf['CRIME'].values

from splot.mapping import vba_choropleth

# Create new figure
fig, axs = plt.subplots(1,2, figsize=(20,10))

# use gdf.plot() to create regular choropleth
gdf.plot(column='HOVAL', scheme='quantiles', cmap='RdBu', ax=axs[0])

# use vba_choropleth to create Value-by-Alpha Choropleth
vba_choropleth(x,
               y,
               gdf,
               #rgb_mapclassify = dict(classifier = 'quantiles'),
               #alpha_mapclassify = dict(classifier = 'quantiles'),
               cmap = 'RdBu',
               ax = axs[1])

# set figure style
axs[0].set_title('normal Choropleth')
axs[0].set_axis_off()
axs[1].set_title('Value-by-Alpha Choropleth')

# plot
plt.show()

Even changing to
rgb_mapclassify = None,
alpha_mapclassify = None,

Both arguments of the function the same graphs are generated.

I think @darribas meant if you leave out the y variable or set y=None? So that instead of a vba_choropleth the user sees a normal choropleth?

I'm not sure if I follow still... cause he mentions about being None as the default and currently the alpha_mapclassify and rgb_mapclassify as default.

I think a reproducible example of this bug would be cool to debug it :)

Thanks for this. Yes, it's what @slumnitz suggests. With the following pre:
from libpysal import examples
import geopandas as gpd
import matplotlib.pyplot as plt
import matplotlib
import numpy as np
from splot.mapping import vba_choropleth
link_to_data = examples.get_path('columbus.shp')
gdf = gpd.read_file(link_to_data)

I'm proposing we allow the user to pass:
fig, _ = vba_choropleth('HOVAL', gdf)
plt.show()

And obtain the same we'd get with:
gdf.plot(column='HOVAL')

I think that'd make vba_choropleth a lot more useful and get people to use it in more contexts (for one, geopandas doesn't support all of our classifiers while we could here). My only concern on this, on a second reflection, is whether we should do that in vba_choropleth or have a more general, swiss-army knife, all-encompassing choropleth (or something like that) that allows for all the functionality and essentially just dispatches to other functions (such as vba_choropleth for VBA mapping).
What do you think @slumnitz and others?

Got it, Dani! Thanks for the reproducible example! Well, I think that what would make more sense, in this case, is your "swiss-army knife" suggestion, since that a 'vba' mapping function should expect to receive a value for the alpha itself.
In addition, we were thinking about building some kind of 'general' choropleth explorer interactively with ipywidgets taking into advantages the classification of mapclassify. Something that would look like this:

In this case, I think this issue would be addressed in a certain way if we manage to add some feature like this, what do you think and other?

Sounds great! I'd be game for leaving vba_choropleth as a VBA tool only and then creating something that wraps around all choropleth functionality somewhere else, but preferably in splot? What do others think?
Just out of curiosity, how are you building the explorer in the image? Having the swiss-army knife would come in handy for that too, no?

Yes, I agree with your first point! I think would make more sense to build this under splot! Regarding your question, this is a screenshot that Serge shared with us here in the CGS of a project that we developed some time ago... We didn't find the source code, yet, but wanna to build this (possibly) from scratch. But basically, it is built using ipywidgets, colorbrewer, and mapclassify and definitely the swiss-army knife would be helpful for that! hehe
We're thinking about to make sprints once a while for specific projects. This one is on the list, for sure!

In terms of the explorer graphic renan shared, i think that should stay in mapclassify as the intention originally, was to provide a simple interface to explore the classifiers visually and mimic colorbrewer. We repurposed it when building the old pysal.contrib.viz and I lost the original interface code since then.

Yes, I agree the interactive from the screenshot fits in mapclassify better. What I was suggesting was a method that wraps around all the choropleth functionality we have between splot, geopandas and mapclassify. Basically one function that lets you create choropleths with all the classifiers in mapclassify, with the option for VBA or not, with a unified API. My first thought was that'd fit better in splot but I'm not particularly married to the idea and very happy to discuss further.

I like the idea of also including a choropleth() mapping functionality in splot. I would however leave the via_choropleth as is, I think users would maybe not get to know about the vba option if it is hidden as a parameter int he function call. We could then use splot functionality to call map classify.Quantiles.plot() similarly how we do that in e.g. giddy or esda?


Height error in Sample_TempObstacles？

Sample：Temp Obstacles
Input Mesh：nav_test.obj
i  try and tune the every param in exe. but 'render height' not cover higher ground
when “ Sample = Tile Mesh” ，dont change param , that normal render ，seems fines.
is my params question?
What can I do to normal render？

I'm not sure I quite understand the question, but I assume it is to do with polys not matching up with the terrain when using the temp obstacles sample.
The detailed mesh is what provides height detail and allows the tiled and solo meshes to match polygons snugly to the terrain. However temp obstacles work by rebuilding tiles whenever changes are made, and for that to work efficiently the tiles are small anyway. For small tiles there usually is no need to have height detail, which is why the detailed mesh is not built for the temp obstacles.
Our recommendation in these cases is usually to lower your tile size or switch to a tiled mesh.
Do note that the polygons are there, they are just cutting "below" the terrain because of simplification.

Closing this since there's no more input from @liuyanlin and a good answer was given - if you are still having problems, reply and we'll reopen the issue.


Docker Hub Description

@glimchb the initial commit cfd146d6760bea6d6e8f646296273261ea273093 is missing a signature, it needs to be signed in order to get merged.


Create build_chart.yml

Automate Chart Creation using Github Actions

This looks like a reasonably helpful iteration.
I would particularly like to see workflow CI/CD to semver tag merges to the default branch, and create Releases so that versions of charts can be referenced explicitly in the future.

Automation was added in https://github.com/CloudHealth/helm/pull/92


is it retry_strategy or retryStrategy because i see both in the code

Are the docs correct? Do they both work?

ugh, wrong project, was comparing this to node-redis, sorry.


Faster Protocol Handler

So, we already have a protocol handler for ipfs, ipns and dweb protocols. Although I'd like to suggest something else.

Right now, every time we open a link on those protocols, we call an electron app so it can just tell the OS to open a browser link. Not worth it. Too many resources. Slow.
Faster idea? Create a static binary. In Go perhaps to do this.
Would work on Windows since we can tell directly which binary to handle the protocols.
On macOS? No clue. Perhaps we'd need to create a separate app and install it with Desktop and leave it always running so we wouldn't need to have IPFS Desktop running to handle the links. It would be harder for us than to the end user. But if we got a better UX, I think it'd be worth it.

Somehow related: https://github.com/ipfs-shipyard/ipfs-desktop/issues/1646

Continued in https://github.com/ipfs-shipyard/ipfs-desktop/issues/1646


Update SA1121 and SA1404 to detect global using aliases, using GetImportScopes and compiling expression trees

Another attempt to fix #3594.
SA1404 also suffered from the same problem.

Tests will fail. That can be fixed and code cleaned up later on. I am more interested in the big picture right now.
Did you have something like this in mind, @sharwell? I haven't wrapped my head around your light-up code completely. I consider my own new code more or less unreadable, but it seems to work :-) I assume that some of it could be generated, but that is beyond me at the moment.
Note that GetImportScopes wasn't available until Roslyn 4.3.0, so with this approach the original issue isn't really resolved perfectly. Are you ok with these rules being broken for Roslyn versions between 4.0.0 (introduction of c# 10) and 4.3.0 (introduction of GetImportScopes)?
Regarding the failing tests: C# 10 tests fail because of the issue with GetImportScopes. What to do?

Upgrade to 4.3.0 in the c# 10 test project. It is still before the 4.4.0 which added c# 11 support, but might not be desirable.
Move the new tests to the c# 11 test project.
...

I moved the tests to the c# 11 test project, because of reasons listed above. Ok?

I moved the tests to the c# 11 test project, because of reasons listed above. Ok?

That seems fine

@sharwell I had a look at this again and I now suspect that I misunderstood the "pattern" of the existing lightup tests. I also realized that I over-complicated the SemanticModelExtensions class a bit. But the main thing was the tests. If you could have look at the comments I added when you have time.

Any more comments on this one, @sharwell? I added comments for some concerns that I have myself.

Rebased and squashed.
Any more comments, @sharwell?

@sharwell?

Sorry for the delays, will try to get to this one soon.
The occasional pings are welcome.


fix : selected item is removed when it 's being filtered from the ava…

…ilable items
Fixes #96
Proposed Changes
-selection should also include items that were selected but not exist on the items (were filtered out)

thx


⚠ Adacta-fintech.com has degraded performance

In bf732b1, Adacta-fintech.com (https://www.adacta-fintech.com) experienced degraded performance:

HTTP code: 200
Response time: 1530 ms

Resolved: Adacta-fintech.com performance has improved in 5c5333a.


Support metric help text in multiprocess mode

Issue #211
Add support for storing the metrics help text in the multiprocess map.
The help will come from the first process read, but it should be the
same for all metrics.
@csmarchbanks not sure if i missed anything but let me know if you need anything changed

Hi @csmarchbanks! Sorry for ping, but can you recheck this PR? It would be cool to get a release with this code 🙏

Thanks for updating this PR, I will take another look soon and give it a bit more thought! It will probably be next week as this week is pretty busy.


Infinite Reload-Loop on application startup

OS?
Windows 10, Chrome (Version 54.0.2840.71 m)
Versions.
λ ng version
angular-cli: 1.0.0-beta.18
node: 5.7.0
os: win32 x64

Repro steps.
When serving my app with beta.18's new --ssl option, I get an endless reload-loop in Chrome. I.e.: I navigate to https://localhost:4200/, the app loads and initializes completely and then reloads (as if I had hit F5).
Angular CLI's output does change (stays at webpack: bundle is now VALID.). The issue might have been caused by files being touched by another process, triggering a rebuild in angular-cli and thus a reload in the browser. This does not happen.
I can reproduce the problem with the "blank" app as created by ng init, but it does not occur everytime like it does with my (more complex) app:

The problem does not occur in Firefox. I tried this Chrome's incognito mode to avoid plugin-problems, but the problem still occurs.
Also, when I switch away to another tab, the cycle stops. The reload itself still works: when I change a file on the filesystem, angular-cli correctly picks that up, rebuilds, triggers a reload and the browser is not sent into the infinite loop.
It feels like this is a timing issue between the reload-script running in the browser and the application's initialization.
As a sidenote: I tried to disable live-reloading (using --live-reload=false) but that does not seem to work.
The log given by the failure.
No error is logged, neither on the command line nor in the browser's console.
Chrome's devtools' network view looks like this:

Heya, I can investigate, but can you give me exact repro steps, i.e. what you used for --ssl, or something I can use myself.

Hi, thanks for taking the time to look into this!
I simply used ng serve --ssl.
You can do this in the default app as generated by angular-cli, but that does not always trigger the problem (chances seem to improve if it is opened in a new browser tab or window). Chances also seem to improve if used on a more complex app.

Closing in favor of https://github.com/angular/angular-cli/issues/5826, it has some extra details about the issue cause.

same here without ssh on local with

Had the same problem here.
I work with atom. It automatically had an extra carriage return at the end of the file which is deleted by webpack at build, but recreate by atom immediatly, forcing rebuild, and so on...
You can monitor this issue by looking at the created webpack hashs which will be the same one after the other : one for extra carriage return, one for no carriage return.
So closing index.html (or configure your ide) will do the trick; well it does for me.
Good luck !

The same problem too. Please help!!!!!
Your global Angular CLI version (1.6.3) is greater than your local
version (1.6.2). The local Angular CLI version is used.
 I'm getting this too.

@silentsnooc : working with atom. Double check auto format options from Prettier / beautifier add on... or native atom settings. Regards.


[Event Request] table 37 "Sales Line" - extend existing event OnCalcVATAmountLinesOnAfterCalcShouldProcessRounding

Hello colleagues,
Could you please extend existing event OnCalcVATAmountLinesOnAfterCalcShouldProcessRounding in table 37 "Sales Line" by adding additional parameters VATAmountLine and TotalVATAmount (by reference).
        OnCalcVATAmountLinesOnAfterCalcShouldProcessRounding(SalesLine, VATAmountLine, TotalVATAmount, Currency, ShouldProcessRounding);

New event signature:
    [IntegrationEvent(false, false)]
    local procedure OnCalcVATAmountLinesOnAfterCalcShouldProcessRounding(var SalesLine: Record "Sales Line"; var VATAmountLine: Record "VAT Amount Line"; var TotalVATAmount: Decimal; Currency: Record Currency; var IsHandled: Boolean)
    begin
    end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 11820.


Publish 0.2 release

We should get 0.2 out before next week. It should include those 0.2 milestone items.

merged to master


[BEAM-11658] Match .snappy files into the given (de)compressor

Snappy is a compression/decompression library. It does not aim for maximum compression or compatibility with any other compression library; instead, it aims for very high speeds and reasonable compression. For instance, compared to the fastest mode of zlib, Snappy is an order of magnitude faster for most inputs, but the resulting compressed files are anywhere from 20% to 100% bigger.
Even if there is support for Snappy in Beam's dependencies, there was no way of matching .snappy files to the given (de)compressor.
This PR provides that.
R: @iemejia
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[x] Update CHANGES.md with noteworthy changes.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

@iemejia I see that the CompressedSourceTest heavily uses the enum CompressionMode, which is deprecated. I could potentially change this test class to use Compression if that's required.

@iemejia I see that the CompressedSourceTest heavily uses the enum CompressionMode, which is deprecated. I could potentially change this test class to use Compression if that's required.

Run Java PreCommit

Run Java PreCommit

@ADBalici if you can additionally improve the tests as you suggested it will be appreciated.

@ADBalici if you can additionally improve the tests as you suggested it will be appreciated.

checkstyle is not happy also for a comment missing a period
[ant:checkstyle] [ERROR] /home/jenkins/jenkins-slave/workspace/beam_PreCommit_Java_Commit/src/sdks/java/core/src/test/java/org/apache/beam/sdk/io/CompressedSourceTest.java:23: Using the '.*' form of import should be avoided - org.hamcrest.Matchers.*. [AvoidStarImport] |
[ant:checkstyle] [ERROR] /home/jenkins/jenkins-slave/workspace/beam_PreCommit_Java_Commit/src/sdks/java/core/src/test/java/org/apache/beam/sdk/io/CompressedSourceTest.java:956: First sentence should end with a period. [JavadocStyle] |

checkstyle is not happy also for a comment missing a period
[ant:checkstyle] [ERROR] /home/jenkins/jenkins-slave/workspace/beam_PreCommit_Java_Commit/src/sdks/java/core/src/test/java/org/apache/beam/sdk/io/CompressedSourceTest.java:23: Using the '.*' form of import should be avoided - org.hamcrest.Matchers.*. [AvoidStarImport] |
[ant:checkstyle] [ERROR] /home/jenkins/jenkins-slave/workspace/beam_PreCommit_Java_Commit/src/sdks/java/core/src/test/java/org/apache/beam/sdk/io/CompressedSourceTest.java:956: First sentence should end with a period. [JavadocStyle] |

@iemejia test class refactored & all checks are passing

@iemejia test class refactored & all checks are passing

Run Java_Examples_Dataflow PreCommit

Run Java_Examples_Dataflow PreCommit

Run Java PreCommit

Run Java PreCommit

@iemejia done :d

@iemejia done :d

Merged now. We just cut the release for 2.28.0 two days ago so this feature will officially be part of 2.29.0 (in around 6-8 weeks). Thanks again!

Merged now. We just cut the release for 2.28.0 two days ago so this feature will officially be part of 2.29.0 (in around 6-8 weeks). Thanks again!


Fix build errors

revert deleted files from api folder (cannot run yarn build without it yet)
revert / downgrade dependencies (the generated site  with yarn build, doesn't render images, breaks fetcher + links after updated dependencies)
modified queries & parts of code that remained from Shopify provider and caused errors,  changed to fit Saleor API like: product sortBy, product filter by collection
fix error after cart item remove
fix other several build errors

https://commerce-2qmuftbb7-cond0r.vercel.app

@cond0r We are still in the process of adapting Saleor for Next.js Commerce. Given our internal roadmap it's more a work-in-progress than a final stage. Thanks for the suggestions. It seems most of them can be integrated as-is. Would you mind rebasing it?

Great PR so far @cond0r, seems very useful 🥇.  Could you have a look at my comments? Let me know if I can help :)

@zaiste it's ok, actually i didn't saw the other pull request, with the changes that covered some things when i made it. Makes more sense now since there are things to do on Saleor too. So the other fixes was about reverting package.json dependencies, revert roles in api folder so it can build. Maybe just consider it.

@cond0r for the revert in package.json, did you also have issues with the build process?

@cond0r Perfect! Could we remove the files framework/saleor/api/. I've added the stubs without directories? Also, it seems that only Next.js itself needs to be downgraded, all other dependencies can be left at the most recent versions. What do you think?

@cond0r would it be possible to squash the last three commits into a single one?


Radius Intelligence Use Case

Adding use case for Radius Intelligence.

LGTM

beat me to cleaning up the commit message..
On Sun, Dec 20, 2015 at 7:48 PM, Xiang Li<EMAIL_ADDRESS>wrote:

Merged #4027 https://github.com/coreos/etcd/pull/4027.
—
Reply to this email directly or view it on GitHub
https://github.com/coreos/etcd/pull/4027#event-496916527.


Remove remnants of libfabric parcelport

Before you do away with the libfabric parcelport, be aware that I have a branch with a lot of improvements, that I had hoped to submit a PR for. We had an intern here last year and he workde on anew allocator, but unfortunately the allocator didn't quite fulfill all of our requirements, so I didn't yet proceed on integrating it with the parcelport.
The parcelport needs to allocate pinned memory and cache it, the allocator provides thiscapability by creating a custom mimalloc arena (ie, requires mimalloc), however the arena cannot be resized after creation, so it isn't ideal (though it would work).  Thus a pre-allocated slabo f memory can be requested on start of the allocator.
Apart from this allocator issue, the parcelport is actually in good shape, though about 1 year out of sync with hpx main and I am aware that a lot of other parcelport related changes have gone in during that time - so breakage is almost inevitable. Perhaps one of the other parcelports has addressed the memory pinning issue and could provide a drop in replacement?
Note that the parcelport also has some quite well optimized polling and dispatching routines, though not as nice as the sender polling for mpi/cuda that is now in pika, which also handles transfer of continuations to the "right place" so that the custom polling pool remains uncluttered with extraneous work.
Given that the mimallloc allocator isn't perfect - would a PR to improve the libfabric in hpx (tested on many machines including amazon AWS etc) be of interest still - or do all the other parcelports now provide good performance and libfabric is no longer needed.

@biddisco I'd be more than happy to accept a PR that makes the current libfabric parcelport usable.

@biddisco I'd be more than happy to accept a PR that makes the current libfabric parcelport usable.

Do any of the other parcelports have code that manages memory pinning etc? Has anyone else worked on this recently?

@biddisco I'd be more than happy to accept a PR that makes the current libfabric parcelport usable.

Do any of the other parcelports have code that manages memory pinning etc? Has anyone else worked on this recently?

IIUC, @JiakunYan pins memory in the LCI parcelport, but that could be part of LCI proper, not the parcelport.

Yes, the memory registration caching code is implemented in LCI. However, it is disabled by default when LCI uses the libfabric backend. I believe libfabric has its own memory registration cache, so I just register and deregister memory buffers plainly. I haven't encountered performance issues related to memory registration by far.


FormField: look at model for minimal validation mode config

It seems as though if you are opting into the "minimal" validation display for one FormField on a form, you very likely would want all the FormFields to be in that mode.
Would it be pragmatic (yet be clean enough) to have FormField consult its bound model to see if it has a minimalValidationMode:true property or something like that?  Not sure about the name... Want to make it clear this is just about the display of validation errors, not reduced or more relaxed validation logic in general.

@lbwexler I would love to look at this quick before finalizing v16, including the prop on FormField itself (currently minimal which I think is too...minimal).
I just added minimal: true to about fifty individual formFields in an app and wish I could have done do in a more centralized manner.

Man, I am sympathetic here.  I guess the problem is that we don't really have a great defaulting story here in the Component hierarchy itself, or a root "Form" class.
Are there other defaults/styling we would like to set on all of the FormFields while we are at it?  Also want to be cognizant of any new properties we'll want w.r.t  to validation behavior.
Perhaps FieldSupport could have the following options bundle.
validationOptions: {
formFieldDefaults: {},
displayOnBlur: true,  // for example
etc.
}

I actually did implement this behavior, i.e. check props.minimal and model.minimal. Following Lee's comment, @TomTirapani and I agreed that the bound model is an awkward place to handle styling.
Tom suggested that you could spread a default minimal prop to avoid repetition in the component. However if minimal mode almost becomes the default case, then I can see how that would also become onerous.
I like the decorator idea, although display options would still be set by the model. Would it be worth creating something like FormLayoutSupport, or just broadening the scope of LayoutSupport?

Is this a good use-case for using React Context? https://reactjs.org/docs/context.html. Seems like this is the kind of problem that Context solves.

Brendan -- didn't fully understand your and Tom's idea regarding the 'default minimal prop'.
Haynes -- Very interesting idea. -- I do think that if  the point of Context is to help do the wiring of the descendant component to its graphical parent.  In this case, the first order of business is defining what that parent is.
Maybe its a Form or a @FormSupport? I almost feel like the whole thing would be easier to grok if we just fully embraced the "form" concept.  @FieldSupport would then become (very naturally) --  @FormModelSupport.
FormSupport could potentially deliver its shared styling and behavior options to its children via a single "FormContext" value.  It could also potentially deliver the model via context as well, which would be one less thing to wire up!

I was imagining something like defining the below function on the component, where defaultProps includes `minimal: true'.
But I agree that's still cumbersome and a decorator + Context solution is cool.
    row = ({field, item}) => {         const {model, defaultProps} = this;         return formField({             item,             field,             model,             ...defaultProps         });     };

ah got it -- thanks -- code samples are always the best....
On Sat, Nov 3, 2018 at 5:01 PM shravnk<EMAIL_ADDRESS>wrote:

I was imagining something like defining the below function on the
component, where defaultProps includes `minimal: true'.
But I agree that's still cumbersome and a decorator + Context solution is
cool.
row = ({field, item}) => { const {model, defaultProps} = this; return
formField({ item, field, model, ...defaultProps }); };
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/exhi/hoist-react/issues/746#issuecomment-435620593,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACM16Umy2zWuhbRWWnwuTos-__PvsSdXks5urgQpgaJpZM4X6rzH
.


Update README.md

fix: spelling mistake

Codecov Report

Merging #12 (e67cf22) into master (39d3552) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #12   +/-   ##
=======================================
  Coverage   83.89%   83.89%
=======================================
  Files           2        2
  Lines         118      118
=======================================
  Hits           99       99
  Misses         14       14
  Partials        5        5

Continue to review full report at Codecov.

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


Update KlipTok.da-DK.json

Minor typo in the Danish translation for "Streamers", changed to "Streamere"

Thank you for fixing the typo!  This will be deployed shortly


fix: allow standard users to get authorization decisions

Lets standard users retrieve authorization decisions. Does not allow these users to retrieve entitlements.
Implements discussion from https://github.com/virtru-corp/data-security-platform/pull/403

Is this a blocker for you @mkleene? There's been recent discussion about adding a Casbin role specific to services that are privileged and distinct from the standard user role to avoid opening up some routes too widely.

Is this a blocker for you @mkleene? There's been recent discussion about adding a Casbin role specific to services that are privileged and distinct from the standard user role to avoid opening up some routes too widely.

Yes, it is. Gateway's decrypt mode needs to be able to determine if a user has access to content.

Is this a blocker for you @mkleene? There's been recent discussion about adding a Casbin role specific to services that are privileged and distinct from the standard user role to avoid opening up some routes too widely.

Although I think that this agrees with @jrschumacher 's thoughts here: https://github.com/virtru-corp/data-security-platform/pull/403, where GetEntitlements is a bit more locked down but these two methods are not.


test: loosen the koala pin to ~> 3.0

The ~> 3.0.0 pin of the koala lib restricted the instrumentation to always be tested against a (7-year old) 3.0.x version. I think it's viable to loosen this restriction and enable testing against 3.x version.
This change also resolves the issue of a failing pipeline, as version 3.0.0 is incompatible with the faraday-multipart 1.1.0 dependency. For reference, here’s an example of the failure: https://github.com/open-telemetry/opentelemetry-ruby-contrib/actions/runs/12399050526/job/34613192801

@michal-kazmierczak I am rescoping this to test since it does not require a release and only impacts the feature matrix


Start REPL with env vars

Hi,
I have a project that have some env dependencies, db, services and stuff like that.. We have been adding that kind of dependencies thru env vars. So on terminal when we start the repl we start with those vars.
question: with proto-repl is it possible to start the repl with some env vars?

Can you show an example of how you start the REPL now at the command line with env vars? I'd imagine you wouldn't type them in every time. I'd imagine you'd put them in a file.
It's possible depending on the way you set them that they're already available. Run this in the REPL to see if they are (keys (System/getenv))
One thing that comes to mind would be to change the leiningen command in the proto repl settings to your own script that would set the environment variables and then call lein repl :headless at the end.

Yes, I have all the vars in a file and I start the repl like this: forego run -e config/production.env lein repl
yeah.. that seems to be a good solution. 👍 but how can I do that?

Yes, I have all the vars in a file and I start the repl like this: forego run -e config/production.env lein repl
yeah.. that seems to be a good solution. 👍 but how can I do that? is it the Lein Args field?
the command that I put there was forego run -e config/production.env lein repl :headless
but I got an error 'forego' is not a task. See 'lein help'. it seems that the whole command is prefixed by lein.. can you help here?

I couldn't figure out a way to do this in Proto REPL without adding it as a special feature. One thing you could do would be to modify the lein script to set the environment variables. Would that work for you?

thanks @jasongilman that would work for me.


Automated cherry pick of #3074: Fix status report of Antrea-native policies

Cherry pick of #3074 on release-1.4.
#3074: Fix status report of Antrea-native policies
For details on the cherry pick process, see the cherry pick requests page.

Codecov Report

Merging #3087 (71b22c6) into release-1.4 (5ad8200) will increase coverage by 3.66%.
The diff coverage is 70.00%.

@@               Coverage Diff               @@
##           release-1.4    #3087      +/-   ##
===============================================
+ Coverage        48.09%   51.76%   +3.66%
===============================================
  Files              283      289       +6
  Lines            23718    24534     +816
===============================================
+ Hits             11408    12699    +1291
+ Misses           10815    10398     -417
+ Partials          1495     1437      -58

Flag
Coverage Δ

kind-e2e-tests
30.28% <10.00%> (-17.82%)
:arrow_down:

unit-tests
40.19% <70.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...ntroller/networkpolicy/networkpolicy_controller.go
63.10% <25.00%> (-4.88%)
:arrow_down:

pkg/agent/controller/networkpolicy/cache.go
80.24% <100.00%> (-1.72%)
:arrow_down:

pkg/controller/types/networkpolicy.go
0.00% <0.00%> (-100.00%)
:arrow_down:

...g/agent/apiserver/handlers/featuregates/handler.go
0.00% <0.00%> (-82.36%)
:arrow_down:

pkg/agent/controller/networkpolicy/reject.go
0.00% <0.00%> (-70.25%)
:arrow_down:

pkg/apis/controlplane/v1beta2/helper.go
33.33% <0.00%> (-66.67%)
:arrow_down:

...formers/externalversions/security/v1alpha1/tier.go
0.00% <0.00%> (-64.29%)
:arrow_down:

...ers/externalversions/core/v1alpha2/clustergroup.go
0.00% <0.00%> (-64.29%)
:arrow_down:

...s/externalversions/core/v1alpha2/externalentity.go
0.00% <0.00%> (-64.29%)
:arrow_down:

...xternalversions/security/v1alpha1/networkpolicy.go
0.00% <0.00%> (-64.29%)
:arrow_down:

... and 163 more

/test-all

/test-all

/test-e2e


fix: error were spies can not accept any missions

Error was coming from the espionage popup file. The show mission briefing function required the target city as an argument also. Simply added the target city plot solved the issue.

Thank you very much for the fix~!!


5e Community Contributed Skills Broken

Commit a1c0b9f by @JasperEX appears to have broken the skills rolls (and potentially other rolls as well).
Relevant forum post

Oh no! I'll fix it tonight.

Looks like the cantrips are also broken. It appends a two to the start of the damage macro. We are working around by adding a -2+[[roll]] for now.
There is also some broken text for spell saves.

I'll do a full check when I get back to my computer.

I've fixed the skills (#10977) Turns out the Cantrip thing was poorly explained feature. The Dmg Scale checkbox adds the appropriate number of damage dice for cantrip damage, if checked. A note has been added to explain the feature.

I pushed a few more commits on the same pull request that address the broken text on spelll saves, as well as a fix for the added weapon slots.


Fix delete review app timeout

Context
Delete review app may fail if concurrent deployment takes more than 2 min
Changes proposed in this pull request
Increase to 30 min and fail the workflow immediately if the timeout is reached
Guidance to review
See same issue in tt api: https://github.com/DFE-Digital/teacher-training-api/runs/2940976784?check_suite_focus=true

 Fix delete review app timeout


fix: esm import error

fix this
import { isEqual, throttle, debounce } from 'lodash';
                            ^^^^^^^^
SyntaxError: Named export 'debounce' not found. The requested module 'lodash' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:

import pkg from 'lodash';
const { isEqual, throttle, debounce } = pkg;

``

This approach will result in the full import of lodash, making it impossible to load on demand.
Perhaps we can consider using lodash-es?

Yes, you're right. I will try this, hope it can work in commonjs too.

It seems link the build assets can both work on commonjs(create-react-app) and esm(nextjs). The only problem is it will broke jest test.

@Daydreamer-riri help rereview it.


modify port setting - allow parallel processing

Great work.
Can you allow modifying the port as an argument so I can run multiple instances to allow parallel processing in OpenRefine?

Hi @yeders
That sounds fine. If you want to do a PR for this, I'll be happy to review and merge.

Do I need to technically know how to do build the variation?


Fix code snippet and typo in tutorial

The action payload first needs to be pushed to the state object before the isNew field is changed, otherwise messages are all always marked as 'read'.
Trivially fixes a couple of references to useEffect where it should be useLayoutEffect in the NotificationsList component.

Yep, looks like I missed a couple of those in the updates. Thanks!


Add event based option to replication policy

This give the possibility to create a event based replication policy and add the mapping for the destination namespace.

@cesarempathy sorry after merging your request I your test failed
=== RUN   TestDestinationNamespace
resource_replication_test.go:109: Step 1/1 error: Error running pre-apply refresh:
Error: Unsupported argument
      on config417152063/terraform_plugin_test.tf line 9, in resource "harbor_retention_policy" "main":
       9: 		  dest_namespace = "gcp-project"

    An argument named "dest_namespace" is not expected here.

@cesarempathy I've revert this pull request please fix your test and submit a new pull request

@wrighbr @cesarempathy can it be merged again?

I think so I fixed the text in this pr
https://github.com/BESTSELLER/terraform-provider-harbor/pull/67

@cesarempathy @wrighbr : in order to be merged again, I created a new branch from master and cherry-picked commits from this PR to it : https://github.com/BESTSELLER/terraform-provider-harbor/pull/76, is it OK for you?


langs issue

having a e.g. abc.lua file, then doing add_comment("something 1")
then having abc2.lua file, then doing add_comment("something 2")
this then makes it so even in abc2.lua, you still see "something 1" even though you should only see "something 2"

https://github.com/face-hh/griddycode/blob/master/Scripts/lua_singleton.gd#L329
The comments are reset when another file extension is opened, so it's weird that this happens

It also occurs with variables and functions.
i was seeing "console" and "process" when in a .java file

Currently unreproducible on v1.0.4

Seeing this issue on v1.1.1

Opened my test.js file and then switched to my test.lua file and opened the comments.
Variables and functions did reset though, so that part has been fixed at v1.1.1

In my last comment I stated the variables and functions did reset when I switched files.
I don't know what changed from then but now they seem to haven't.

(screenshot is in a .py file, those are .lua functions and variables)

We could just re-load everything upon opening a new file regardless of the extension, so if we're working on a lua file and we open a new one everything gets reset and the lua plugin gets reloaded once more, or we could add a different approach, something like vim, where we have buffers and things like highlighting and such are tied to these buffers


chore(ci): rename CI scripts name

What's changed and what's your intention?
Renamed script to match steps in workflows.
Checklist
Refer to a related PR or issue link (optional)

LGTM. By the way, I think I've made a wrong choice to separate the three workflows, as now we need to change all of them if we need to add a new step 🤣 If there any better way to do this?

Choice 1: using conditions. We have only one yaml with all steps, and enable them on (cron|main|pull_request)
Choice 2: introduce a workflow generator, where we have a meta template, and we write yaml for each workflow:

pull_request:
  include_steps: ["build", "test", "..."]
main:
  include_steps: ["build", "test", "..."]
cron:
  include_steps: ["build", "test", "..."]

... or any other way, if you can think of another method.

If they are all placed in a yaml file, the matrix may not be able to be used. I will find a way to optimize it later.


Handle unexpected new line characters when pulling projects

In some cases (only haven been able to reproduce it using the extension) the algorithm files are stored using windows new line separators, but the CLI works with '\n' when the files contents are in memory. This fixes this unexpected file content new line separators for those cases.
Closes #342

Thank you

Potentially this should be handled by the cloud 🤔
On Fri, Jul 14, 2023, 6:10 PM Jared @.***> wrote:

Thank you
—
Reply to this email directly, view it on GitHub
https://github.com/QuantConnect/lean-cli/pull/344#issuecomment-1636500470,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD5F5DF6STT5XNT5UTBBE7TXQG7VZANCNFSM6AAAAAA2K2R7VQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Ingestion stopped running

[09:38:36][giorgio@elife-XPS-13-9370:~/code/sciety]$ kubectl get pods | grep sciety--prod
...
sciety--prod--ingestion-1661059800-8rccv             0/1     Completed   0          4d3h
sciety--prod--ingestion-1661060400-jtntl             0/1     Completed   0          4d2h
sciety--prod--ingestion-1661061000-7525b             0/1     Completed   0          4d2h
sciety--prod--ingestion-1661061600-rzt92             1/1     Running     0          4d2h

$ kubectl logs sciety--prod--ingestion-1661061600-rzt92
{"timestamp":"2022-08-21T06:00:12.164Z","level":"info","message":"Ingestion successful","payload":{"groupName":"ScreenIT","lefts":{},"leftsTotal":0,"rightsTotal":0}}
{"timestamp":"2022-08-21T06:00:12.166Z","level":"info","message":"Ingestion successful","payload":{"groupName":"Arcadia Science","lefts":{},"leftsTotal":0,"rightsTotal":0}}
{"timestamp":"2022-08-21T06:00:12.174Z","level":"info","message":"Ingestion successful","payload":{"groupName":"Biophysics Colab","lefts":{},"leftsTotal":0,"rightsTotal":0}}
{"timestamp":"2022-08-21T06:00:12.674Z","level":"info","message":"Ingestion successful","payload":{"groupName":"ASAPbio crowd review","lefts":{},"leftsTotal":0,"rightsTotal":1}}
{"timestamp":"2022-08-21T06:00:12.893Z","level":"info","message":"Ingestion successful","payload":{"groupName":"Rapid Reviews COVID-19","lefts":{},"leftsTotal":0,"rightsTotal":0}}
{"timestamp":"2022-08-21T06:00:13.410Z","level":"info","message":"Ingestion successful","payload":{"groupName":"PCI Neuroscience","lefts":{},"leftsTotal":0,"rightsTotal":1}}
{"timestamp":"2022-08-21T06:00:13.462Z","level":"info","message":"Ingestion successful","payload":{"groupName":"PCI Paleontology","lefts":{},"leftsTotal":0,"rightsTotal":0}}
{"timestamp":"2022-08-21T06:00:13.840Z","level":"info","message":"Ingestion successful","payload":{"groupName":"PCI Archaeology","lefts":{},"leftsTotal":0,"rightsTotal":0}}
{"timestamp":"2022-08-21T06:00:13.860Z","level":"info","message":"Ingestion successful","payload":{"groupName":"PCI Zoology","lefts":{},"leftsTotal":0,"rightsTotal":1}}
{"timestamp":"2022-08-21T06:00:14.055Z","level":"info","message":"Ingestion successful","payload":{"groupName":"PCI Animal Science","lefts":{},"leftsTotal":0,"rightsTotal":1}}
{"timestamp":"2022-08-21T06:00:16.362Z","level":"info","message":"Ingestion successful","payload":{"groupName":"PeerRef","lefts":{},"leftsTotal":0,"rightsTotal":15}}
{"timestamp":"2022-08-21T06:00:17.961Z","level":"info","message":"Ingestion successful","payload":{"groupName":"PCI Ecology","lefts":{},"leftsTotal":0,"rightsTotal":0}}
{"timestamp":"2022-08-21T06:00:19.127Z","level":"info","message":"Ingestion successful","payload":{"groupName":"PCI Evolutionary Biology","lefts":{},"leftsTotal":0,"rightsTotal":2}}
{"timestamp":"2022-08-21T06:00:19.234Z","level":"info","message":"Ingestion successful","payload":{"groupName":"Review Commons","lefts":{},"leftsTotal":0,"rightsTotal":24}}
{"timestamp":"2022-08-21T06:00:19.398Z","level":"info","message":"Ingestion successful","payload":{"groupName":"PeerJ","lefts":{},"leftsTotal":0,"rightsTotal":17}}
{"timestamp":"2022-08-21T06:00:24.386Z","level":"error","message":"Ingestion failed","payload":{"groupName":"GigaByte","lefts":{"Failed to post evaluation command: Error: Request failed with status code 502. Response data is: \"\r\n<title>502 Bad Gateway</title>\r\n\r\n
502 Bad Gateway
\r\n
nginx\r\n\r\n\r\n\"":1},"leftsTotal":1,"rightsTotal":50}}
{"timestamp":"2022-08-21T06:00:30.908Z","level":"error","message":"Ingestion failed","payload":{"groupName":"PREreview","lefts":{"Failed to post evaluation command: Error: Request failed with status code 502. Response data is: \"\r\n<title>502 Bad Gateway</title>\r\n\r\n
502 Bad Gateway
\r\n
nginx\r\n\r\n\r\n\"":1},"leftsTotal":1,"rightsTotal":89}}
{"timestamp":"2022-08-21T06:00:32.554Z","level":"info","message":"Ingestion successful","payload":{"groupName":"NCRC","lefts":{},"leftsTotal":0,"rightsTotal":106}}
{"timestamp":"2022-08-21T06:00:35.995Z","level":"info","message":"Ingestion successful","payload":{"groupName":"eLife","lefts":{},"leftsTotal":0,"rightsTotal":155}}
{"timestamp":"2022-08-21T06:00:45.019Z","level":"info","message":"Ingestion successful","payload":{"groupName":"GigaScience","lefts":{},"leftsTotal":0,"rightsTotal":308}}

$ kubectl logs sciety--prod--ingestion-1661061600-rzt92 | grep "Ingestion successful" | jq .payload.groupName | sort
"Arcadia Science"
"ASAPbio crowd review"
"Biophysics Colab"
"eLife"
"GigaScience"
"NCRC"
"PCI Animal Science"
"PCI Archaeology"
"PCI Ecology"
"PCI Evolutionary Biology"
"PCI Neuroscience"
"PCI Paleontology"
"PCI Zoology"
"PeerJ"
"PeerRef"
"Rapid Reviews COVID-19"
"Review Commons"
"ScreenIT"

sh -c "npx ts-node src/ingest/update-event-data && wget --quiet https://hc-ping.com/..."


Horizontal scrolling if no data.

I'm submitting a ...  (check one with "x")
[x ] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here

Current behavior
i'm not getting horizontal scrolling if there is no data in the table.
Expected behavior
Reproduction of the problem
What is the motivation / use case for changing the behavior?
To not have columns that are cutoff and not seen.
Please tell us about your environment:
Windows 64 bit 7

Table version: 0.7.x
0.9.3

Angular version: 2.0.x
2.1.2

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
Chrome

Language: [all | TypeScript X.X | ES6/7 | ES5]

+1

In live application, this is really annoying... please give a update on this!

Any update on this issue? Has anyone found the solution to this issue?

Any update on this issue? Has anyone found the solution to this issue?


Test code file reference fixed

The docs written in markdown have been moved to the javadocs and will be maintained there.
Besides thanks for the contribution


Threading issue when using LifestyleScoped

I am getting an internal exception in when resolving using LifestyleScoped in a multi-threaded app.
I'm resolving instances via factories which call a scoped accessor. The exception doesn't occur in the accessor but when attempting to set the Burden. I get the following ArgumentException: "An item with the same key has already been added." with stack trace:
   at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
   at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
   at System.Collections.Generic.Dictionary`2.Add(TKey key, TValue value)
   at Castle.MicroKernel.Lifestyle.Scoped.ScopeCache.set_Item(Object id, Burden value)
   at Castle.MicroKernel.Lifestyle.Scoped.DefaultLifetimeScope.GetCachedInstance(ComponentModel model, ScopedInstanceActivationCallback createInstance)
   at Castle.MicroKernel.Lifestyle.ScopedLifestyleManager.Resolve(CreationContext context, IReleasePolicy releasePolicy)
   at Castle.MicroKernel.Handlers.DefaultHandler.ResolveCore(CreationContext context, Boolean requiresDecommission, Boolean instanceRequired, Burden& burden)
   at Castle.MicroKernel.Handlers.DefaultHandler.Resolve(CreationContext context, Boolean instanceRequired)
   at Castle.MicroKernel.Handlers.AbstractHandler.Resolve(CreationContext context)
   at Castle.MicroKernel.DefaultKernel.ResolveComponent(IHandler handler, Type service, IDictionary additionalArguments, IReleasePolicy policy)
   at Castle.MicroKernel.DefaultKernel.Castle.MicroKernel.IKernelInternal.Resolve(Type service, IDictionary arguments, IReleasePolicy policy)
   at Castle.Facilities.TypedFactory.TypedFactoryComponentResolver.Resolve(IKernelInternal kernel, IReleasePolicy scope)
   at Castle.Facilities.TypedFactory.Internal.TypedFactoryInterceptor.Resolve(IInvocation invocation)
   at Castle.Facilities.TypedFactory.Internal.TypedFactoryInterceptor.Intercept(IInvocation invocation)
   at Castle.DynamicProxy.AbstractInvocation.Proceed()
   at Castle.Proxies.IPSECommonIOFactoryProxy.Create(IFtpObj ftpObj)

My scoped accessor is pretty benign and doesn't throw any exceptions. For reference the code is:
public class ArgScopeAccessor : IScopeAccessor
{
    static readonly ConcurrentDictionary<object, ILifetimeScope> collection = new ConcurrentDictionary<object, ILifetimeScope>();

    public void Dispose()
    {
        foreach (var scope in collection)
            scope.Value.Dispose();
        collection.Clear();
    }

    public ILifetimeScope GetScope(CreationContext context)
    {
        if (context.AdditionalArguments.Count != 1)
            throw new ArgumentException("Expect one and only one argument");
        object arg = null;
        foreach (var a in context.AdditionalArguments.Values)
            arg = a;

        return collection.GetOrAdd(arg, n => new DefaultLifetimeScope());
    }
}

I know this is a really old issue, however it is explicitly called out in the documentation that DefaultLifetimeScope is not thread safe and the docs provide an example of implementing a scope that is. This is a conscience design decision.
DefaultLifetimeScope is used by many lifestyles that don't need multi-threaded scope resolution (and don't want the performance hit of synchronisation) including the PerWebRequest lifestyle where execution happens on a single thread.
#221 includes additional info where this issue has come up again with another custom lifestyle.


feat: add source_branch to control the edit source link default branch

The default branch where I am storing the repository is not "master", and thus when clicking on "Edit this page ->" link, it was working, but only because gitHub is kind enough to redirect to the default branch with that message:

Branch not found, redirected to default branch.

No behavior change expected.

I've updated it to source_version, and made it work with readthedocs.


DSC output is not correct on windows

Th ugly dance does not work on a windows host
==> default: "Running DSC Provisioner with Reboot.ps1..."
PSModulePath Configured: C:\Users\vagrant\Documents\WindowsPowerShell\Modules;C:\Program Files\WindowsPowerShell\Modules
;C:\Windows\system32\WindowsPowerShell\v1.0\Modules
Running Configuration file: C:\tmp\vagrant-dsc-4\manifests\Reboot.ps1
    Directory: C:\tmp\vagrant-dsc-4\staging

Mode                LastWriteTime         Length Name
----                -------------         ------ ----
-a----        9/27/2016  11:54 AM           3420 localhost.mof                                                         V
ERBOSE: Perform operation 'Invoke CimMethod' with following parameters, ''methodName' =
SendConfigurationApply,'className' = MSFT_DSCLocalConfigurationManager,'namespaceName' =
root/Microsoft/Windows/DesiredStateConfiguration'.VERBOSE: An LCM method call arrived from computer WIN-DE48B6UFMAD with
 user sid
S-1-5-21-2858833851-4070451517-2877580039-1000.
VERBOSE: [WIN-DE48B6UFMAD]: LCM:  [ Start  Set      ]VERBOSE: [WIN-DE48B6UFMAD]: LCM:  [ Start  Resource ]  [[Script]Reb
oot]
VERBOSE: [WIN-DE48B6UFMAD]: LCM:  [ Start  Test     ]  [[Script]Reboot]VERBOSE: [WIN-DE48B6UFMAD]: LCM:  [ End    Test
   ]  [[Script]Reboot]  in 0.1070 seconds.
VERBOSE: [WIN-DE48B6UFMAD]: LCM:  [ Start  Set      ]  [[Script]Reboot]VERBOSE: [WIN-DE48B6UFMAD]:
      [[Script]Reboot] Performing the operation "Set-TargetResource"
on target "Executing the SetScript with the user supplied credential".VERBOSE: [WIN-DE48B6UFMAD]: LCM:  [ End    Set
  ]  [[Script]Reboot]  in 0.0360 seconds.
VERBOSE: [WIN-DE48B6UFMAD]: LCM:  [ End    Resource ]  [[Script]Reboot]
VERBOSE: [WIN-DE48B6UFMAD]:                            [] A reboot is scheduled to progress further. Configuration will
 be continued after the reboot.
WARNING: [WIN-DE48B6UFMAD]:                            [] A reboot is scheduled to progress further. Configuration will
 be continued after the reboot.VERBOSE: [WIN-DE48B6UFMAD]: LCM:  [ End    Set      ]
VERBOSE: [WIN-DE48B6UFMAD]: LCM:  [ End    Set      ]    in  0.6650 seconds.
VERBOSE: Operation 'Invoke CimMethod' complete.VERBOSE: Time taken for configuration job to complete is 0.64 seconds

==> default: DSC needs reboot. Wait for the completion of DSC.

Remove the new_line: false, makes the output better:
==> default: "Running DSC Provisioner with Reboot.ps1..."
PSModulePath Configured: C:\Users\vagrant\Documents\WindowsPowerShell\Modules;C:\Program Files\WindowsPowerShell\Modules
;C:\Windows\system32\WindowsPowerShell\v1.0\Modules

Running Configuration file: C:\tmp\vagrant-dsc-4\manifests\Reboot.ps1

    Directory: C:\tmp\vagrant-dsc-4\staging

Mode                LastWriteTime         Length Name
----                -------------         ------ ----
-a----        9/27/2016  12:01 PM           3420 localhost.mof
VERBOSE: Perform operation 'Invoke CimMethod' with following parameters, ''methodName' =
SendConfigurationApply,'className' = MSFT_DSCLocalConfigurationManager,'namespaceName' =
root/Microsoft/Windows/DesiredStateConfiguration'.
VERBOSE: An LCM method call arrived from computer WIN-HDPI7L26RNL with user sid
S-1-5-21-2303000744-480427162-1103718486-1000.
VERBOSE: [WIN-HDPI7L26RNL]: LCM:  [ Start  Set      ]
VERBOSE: [WIN-HDPI7L26RNL]: LCM:  [ Start  Resource ]  [[Script]Reboot]

VERBOSE: [WIN-HDPI7L26RNL]: LCM:  [ Start  Test     ]  [[Script]Reboot]
VERBOSE: [WIN-HDPI7L26RNL]: LCM:  [ End    Test     ]  [[Script]Reboot]  in 0.1260 seconds.

VERBOSE: [WIN-HDPI7L26RNL]: LCM:  [ Start  Set      ]  [[Script]Reboot]
VERBOSE: [WIN-HDPI7L26RNL]:                            [[Script]Reboot] Performing the operation "Set-TargetResource"
on target "Executing the SetScript with the user supplied credential".
VERBOSE: [WIN-HDPI7L26RNL]: LCM:  [ End    Set      ]  [[Script]Reboot]  in 0.0350 seconds.

VERBOSE: [WIN-HDPI7L26RNL]: LCM:  [ End    Resource ]  [[Script]Reboot]
VERBOSE: [WIN-HDPI7L26RNL]:                            [] A reboot is scheduled to progress further. Configuration will
 be continued after the reboot.
WARNING: [WIN-HDPI7L26RNL]:                            [] A reboot is scheduled to progress further. Configuration will
 be continued after the reboot.
VERBOSE: [WIN-HDPI7L26RNL]: LCM:  [ End    Set      ]
VERBOSE: [WIN-HDPI7L26RNL]: LCM:  [ End    Set      ]    in  0.6650 seconds.
VERBOSE: Operation 'Invoke CimMethod' complete.
VERBOSE: Time taken for configuration job to complete is 0.632 seconds

==> default: DSC needs reboot. Wait for the completion of DSC.

Is this on a linux host still required?

Sorry @StefanSchoof, I'm not sure I understand the question.
Are you asking if running vagrant-dsc from a linux host is required? (the answer is a definite yes, as this is pretty much the only way I was/am using this).

In the run_dsc_apply is a part for formatting the output
        # A bit of an ugly dance, but this is how we get neat, colourised output and exit codes from a Powershell run
        last_type = nil
        new_line = ""
        error = false
        machine.communicate.shell.powershell("powershell -ExecutionPolicy Bypass -OutputFormat Text -file #{DSC_GUEST_RUNNER_PATH}") do |type, data|
          if !data.chomp.empty?
            error = true if type == :stderr
            if [:stderr, :stdout].include?(type)
              color = type == :stdout ? :green : :red
              new_line = "\r\n" if last_type != nil and last_type != type
              last_type = type
              @machine.ui.info( new_line + data.chomp, color: color, new_line: false, prefix: false)
            end
          end
        end

        error == false

On a windows host this seems not to work well. So I am asking me, if this has been fixed in vagrant and is no longer required or if this is a host specif problem and has to be done differently on windows and linux.

ha, no worries @StefanSchoof. I talk to myself out loud, you are welcome to write yourself on GitHub issues :)

Gem v1.1.2 released

Thanks for make a Release this fast


1657393: Add missing descriptions

Summary
We are adding descriptions to improve SEO, per 1657393. Suggestions are welcome, but keep in mind our 100-160 char range.
@gewarren - You're listed as author for these topics. Well, one topic. Please review when you get a chance. Our SLA specifies 5 business days for review, but let me know if you need more time. (Also, let me know if you are not the right person to approve. We go by the github author tag.)
Fixes #1657393

@TimShererWithAquent Thank you!


O11y-Op testing

Motivation
In order to raise our confidence in the stability of our observability platform and be sure that our ongoing work and releases won't negatively impact our observability platform operations we need to create extensive tests giving us early feedback loops.
Todo

Investigate some good initial test cases to give us feedback on the stability of a release on mimir on CI. This can be:

Validate Helm chart templating
Deploy chart on Kind (single instance)
Implement those CI test cases

Investigate how we can setup an e2e test case for the o11y-op

We can just check if the configmaps are created and if the content makes sense

Outcome

We have early, automatic feedback about the impact of a release of the o11y-op before releasing.

:heavy_check_mark: Helm chart CI tests done.

@QuantumEnigmaa anything we still have to do here?

Yeah, as discussed during refinement, we'll have to create a "e2e" testing framework on our own :

We will update the PR message to empower the user to perform the required tests before asking reviews for its PR.
A dedicated directory will be created at the repo's root with a file describing the test procedure and possible scripts to run manually after deploying the custom branch version on a MC.
Concerning olly-op specifically, the testing procedure might consist in creating a WC after having deployed olly-op custom branch's version on a testing MC let it run a bit and check on if the remote-write secret for the WC has been created.

Sorry I only updated Loki issue but that will be the same thing for all MC-only app.

No worries :)

Here's the ticket of the new @giantswarm/team-tenet for tests of apps only running on MC: https://github.com/giantswarm/roadmap/issues/2930
have you taken the considerations in there into account?

Yes but as even Marcus isn't sure on how or when this will eventually end, I'd prefer that we craft something on our own for now that will still be usable if tenet's framework become available, even if it's a bit more "manual".

Manual e2e testing procedure and script now available in the app's repo + PR message updated.


Create Weather and Environmental Assistant.md

📝 Description
Add a brief description.
💣 Is this a breaking change (Yes/No):

[ ] Yes
[x] No

🚧 How to migrate?
Don't need.
📝 Additional Information
lol

Dear user,
we appreciate your contribution. But it is difficult for GPT to give the real-time weather. Please try something else.


CDI Lite implementations could/should detect CDI Full feature usages

We could/should require CDI implementations that implement CDI Lite but do not implement CDI Full to detect (as much as they practically can) usages of CDI features they do not implement and treat them as deployment problem. This would let developers know very early on that they're using unsupported APIs.
The features that should be easy to detect and safe to treat as deployment problems:

usage of @SessionScoped and @ConversationScoped
usage of @Interceptors
declaration of @AroundInvoke interceptors on target classes (as in, on classes that are not interceptors)
usage of @Decorator, injection of @Delegate
usage of @Specializes
injection of Conversation
injection of InterceptionFactory
usage of explicit bean archives (bean-discovery-mode="all")
usage of per-bean-archive enablement (and in general any content of beans.xml besides the bean-discovery-mode attribute)

These features require more delicate treatment:

declaration of passivating scope (@NormalScope(passivating=true)): if the context is implemented correctly, it is expected to work, there just won't be any passivation
injection of BeanManager: this is possible in CDI Lite due to compatibility, but only BeanContainer methods must be implemented (the other may throw UnsupportedOperationException)
usage of Portable Extensions: there's a mechanism for Portable Extensions to coexist with Build Compatible Extensions for gradual migration

These features can't be detected [easily], as far as I can tell:

relieance on passivation in general
custom implementations of Bean or Interceptor
obtaining BeanManager in some other way (not through injection)
obtaining InterceptionFactory in some other way (not through injection)

I probably missed something, but this should be a list of the most common things people may stumble upon.
(This is a follow-up on #640.)

This looks good.


Deploy API as Lambda using Terraform

Wrap fast api in a Lambda fubnction and deploy to AWS via terraform need db connection via db proxy
AC:
-can execute all endpoints via http request
--create separate issue for:
API gateway to expose API to internet
E2E testing of API endpoints

potential article to help with this ticket:
https://www.deadbear.io/simple-serverless-fastapi-with-aws-lambda/

The lambda function for the sample API has been deployed to AWS via Terraform, the database connection using AWS secret manager (via Terraform) has been completed as well.


Mod: magit hunk heading face for city-lights

Using city-lights for a while now and there is a face that bothers me which is the magit hunk heading. I've changed the face to use less intrusive colors, and it works better for me.
What are your thoughts about this change? Here is a snapshot from the Magit log for illustration of how it looks, both highlight and normal states:
current:

modified:

I'm ok with this. You should move the section with and add the respective comment down in the major mode's section though

@ema2159 thank you for taking the time to look into this. I've made the proposed changes.


Fix json editor

Closes #

Closes https://github.ibm.com/wiotp/Maximo-Asset-Monitor/issues/2711
Related to https://github.ibm.com/wiotp/Maximo-Asset-Monitor/issues/3653 Section.2

Summary

Fixed Open JSON editor button should always be visible in config pane
Fixed footer of pagination was misaligned

Change List (commits, features, bugs, etc)

fix(cardeditor): fixed Open JSON editor button in config pane
style(simplepaginantion): fixed footer of pagination

Acceptance Test (how to verify the PR)

Open JSON Editor button should be fixed in config pane
Footer content for pagination should not be misaligned

Regression Test (how to make sure this PR doesn't break old functionality)

tests here

Things to look for during review

[ ] Make sure all references to iot or bx class prefix is using the prefix variable
[ ] (React) All major areas have a data-testid attribute. New test ids should have test written to ensure they are not changed or removed.
[ ] UI should be checked in RTL mode to ensure the proper handling of layout and text.
[ ] All strings should be translatable.
[ ] The code should pass a11y scans (The storybook a11y knob should show no violations). New components should have a11y test written.
[ ] Unit test should be written and should have a coverage of 90% or higher in all areas.
[ ] All components should be passing visual regression test. For new styles or components either a visual regression test should be written for all permutations or the base image updated.
[ ] Changes or new components should either write new or update existing documentation.
[ ] PR should link and close out an existing issue

@davidicus some part of code from packages/react/src/components/CardEditor/CardEditForm/CardEditForm.jsx moved to packages/react/src/components/CardEditor/CardEditor.jsx so do the testcases. Functionality wise nothing much changed.
Overall use case: The Open JSON editor button needed to be in the footer.


Error messages not being formatted properly when registry API returns pretty-printed JSON

If a registry or index returns a pretty-printed JSON block, then the result is the following:
docker push localhost/somenamespace/test
The push refers to a repository [localhost/somenamespace/test] (len: 1)
Sending image list
2014/02/05 16:52:13 push: }

Output for non-pretty printed response:
docker push localhost/somenamespace/test
The push refers to a repository [localhost/somenamespace/test] (len: 1)
Sending image list
2014/02/05 16:56:16 push: Error: Status 403 trying to push repository somenamespace/test: {"error": "You do not have permission to create repositories in namespace \"somenamespace\""}

docker version:
Client version: 0.8.0
Go version (client): go1.2
Git commit (client): cc3a8c8
Server version: 0.8.0
Git commit (server): cc3a8c8
Go version (server): go1.2
Last stable version: 0.8.0

@jlhawn @dmcgowan does this still apply?

@jfrazelle this should no longer apply, that error message is now outputted using the logging library.  An example error would now appear like
FATA[0006] Failed to ....

So I can close?
On Wednesday, January 14, 2015, Derek McGowan<EMAIL_ADDRESS>wrote:

@jfrazelle https://github.com/jfrazelle this should no longer apply,
that error message is now outputted using the logging library. An example
error would now appear like
FATA[0006] Failed to ....
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/issues/3951#issuecomment-69979401.


Push to pypi

Hello,
Could we push this package on pip so that it is accessible?
Also, do you plan to add other types of coresets like Bayesian Coresets and so on?
Cheers,
Fred

FYI: I have forked this project and pushed it to pypi. I don't have a lot of context on the project itself, so not planning to add other types of coresets, but open to PRs that do it.


feature support setting skip audit log user

Proposed changes
Sometime we don't want to audit all users operation to audit log.
This PR offer a new FE config skip_audit_users.
Operations of users in this list will not be logged to audit log and audit table.
eg:
skip_audit_users=user1,user2

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

run buildall

run buildall

Need re design


[5.6] Code style fix in Markdown mail layout

Just a small indentation fix.

Thanks for the PR, but I think this is not actually what we want here. Think about what the final output will look like - the first line will have a bunch of spaces before it, then subsequent lines will not.


Update README.md to match current release

And showcase the new kill vs restart feature.

notification screenshot (and gif)
code snippet for the configuration
detail effects of both actions

Do you need some help to update those elements?

@SimonMarquis right, I'd appreciate any contribution to updating the README
Let me know if you want to take any of these points

I already did some screenshots/clip in PR #33.
I did not check out your PR, but I guess the behaviors where similar?

screenshot: https://user-images.githubusercontent.com/1921278/172055445-544a46a0-e59d-4609-8acd-4cd3eca9bd8b.png
clip: would have to be re-done

WDYT? I can start a draft PR

Let's split it into multiple PR, I'd appreciate it if you could create a PR for the screenshot and gif animation

@SimonMarquis thanks for your contribution 👍


[Event Request] - PurchPost.Codeunit.al - OnPostItemChargePerSalesShptOnBeforePostCharge

We like to request the following Event:
Object: PurchPost.Codeunit.al
Where is the event placed:
local procedure PostItemChargePerSalesShpt(PurchHeader: Record "Purchase Header"; var PurchLine: Record "Purchase Line")
var
SalesShptLine: Record "Sales Shipment Line";
TempItemLedgEntry: Record "Item Ledger Entry" temporary;
ItemTrackingMgt: Codeunit "Item Tracking Management";
Sign: Decimal;
DistributeCharge: Boolean;
IsHandled: Boolean;
begin
if not SalesShptLine.Get(
TempItemChargeAssgntPurch."Applies-to Doc. No.", TempItemChargeAssgntPurch."Applies-to Doc. Line No.")
then
Error(RelatedItemLedgEntriesNotFoundErr);
    IsHandled := false;
    OnPostItemChargePerSalesShptOnBeforeTestJobNo(SalesShptLine, IsHandled);
    if not IsHandled then
        SalesShptLine.TestField("Job No.", '');

    Sign := -GetSign(SalesShptLine."Quantity (Base)");

    if SalesShptLine."Item Shpt. Entry No." <> 0 then
        DistributeCharge :=
          CostCalcMgt.SplitItemLedgerEntriesExist(
            TempItemLedgEntry, -SalesShptLine."Quantity (Base)", SalesShptLine."Item Shpt. Entry No.")
    else begin
        DistributeCharge := true;
        ItemTrackingMgt.CollectItemEntryRelation(TempItemLedgEntry,
          DATABASE::"Sales Shipment Line", 0, SalesShptLine."Document No.",
          '', 0, SalesShptLine."Line No.", SalesShptLine."Quantity (Base)");
    end;

    **OnPostItemChargePerSalesShptOnBeforePostCharge**(PurchHeader, PurchLine, SalesShptLine, TempItemLedgEntry, DistributeCharge);

    if DistributeCharge then

Event Code:
[IntegrationEvent(false, false)]
local procedure OnPostItemChargePerSalesShptOnBeforePostCharge(PurchHeader: Record "Purchase Header"; var PurchLine: Record "Purchase Line"; var SalesShptLine: Record "Sales Shipment Line"; var TempItemLedgEntry: Record "Item Ledger Entry" temporary; var DistributeCharge: Boolean);
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


patch: add more paulistes dialects

Pre-Submission Checklist

You have only one commit (if not, squash them into one commit).
All new and existing tests pass the command yarn test and yarn lint.

Description

Thanks, @luizferreira094 for your contribution \0/


Minor optimizations when webp_support is not enabled

This adds 2 checks for cases when webp_support is not enabled:

Omit the type attribute on the <source> element
The primary use case is to work with image services that provide automatic format conversion. If this attribute is not specified, the browser should use the MIME type information from the server. (More on MDN)

Omit the srcWebp and srcSetWebp keys in the media source toArray() output

Thanks @pboivin, looks good to me!


Feature request: allow specifying the size of the chunks provided by File#createReadStream()

Hello,
At the moment, the chunks returned by File#createReadStream() method are 16kb long.
I believe that's Node's default highWaterMark value.
The issue with this is that it consumes too much memory to read a big file.
For a 250mb file, that's 16k chunks, and it consumes 2GB of memory before the process crashes.
If you are okay with it, I'd like to submit a PR to specify the chunks size.
I will look into createReadStream() code tonight and see what I can do.
Meanwhile, any help or guidance is welcome.
Thanks,
Samy

@Dinduks Thank you for reporting this.
Could you please give more details, share your environment details
Environment details

OS:
Node.js version:
npm version:
@google-cloud/storage version:
related modules versions:

Please share a code snippet that causes the issue.
I've tried to reproduce in a couple of ways:

file.download into file/buffer
file.createReadStream into file/buffer
but unsuccessful

@AVaksman Hi Alex.
Indeed, there is no issue with @google-cloud/storage itself.
The memory issues come from the thousands of operations inside my .on('data', () => {}) on the stream created by createReadStream.
I think being able to grab chunks bigger than 16kb would solve this problem by reduce the number of operations inside .on('data', () => {}).
Meanwhile, I'll try to optimize these operations.
I could provide the sample if you think it's relevant.
Also:

OS is Arch Linux kernel 5.2.8
Node version is v11.15.0
npm version is 6.10.3
GS version is 3.3.0 or 3.2.1
Used lib inside .on('data', () => {}) is https://www.npmjs.com/package/stream-buffers.

highWaterMark does not dictate the size of the chunk:
https://github.com/nodejs/node/issues/8855

What's your point @jkwlui?

Would you mind providing us with a simple reproduction code that we can try and replicate? You mentioned using stream-buffers inside the event callback, so if you could provide an example of that it'd be great, thanks!

@Dinduks please feel free to provide more information, but I believe this is an issue to solve at the application level as opposed to our level in the library. You could look into using something like throttle, or otherwise queueing the operations you're running in the .on() handler in steps. You can also use the start and end options when reading a file to only handle chunks of the file at once.
I'm going to close the issue, but I'm happy to re-open if there's more we should do on our side.


Fix infinite loop when parsing incomplete functions

See the unit test for the input that would previously cause an infinite loop. I

Coverage decreased (-0.03%) to 96.54% when pulling 35d26feb5925c1abec7fb4514c05cd898d1e5b82 on grncdr:hotfix-infinite-loop into e47168f5aa9576819830554f1b37dc0d49b76d31 on jshint:master.

Infinite loop?
Using current master branch I haven't any infinite loop.
$ bin/jshint - <<< "function"
stdin: line 1, col 1, Missing name in function declaration.
stdin: line 1, col 1, Expected '(' and instead saw ''.
stdin: line 2, col undefined, Unrecoverable syntax error. (100% scanned).

3 errors

$ bin/jshint - <<< "function what ("
stdin: line 1, col 15, Expected an identifier and instead saw ''.
stdin: line 2, col undefined, Unrecoverable syntax error. (100% scanned).

2 errors

Nevermind, this was already fixed on master.

Cross-posted :smile: The issue is there on 2.7.0, seems like a common enough situation to warrant a point-release to npm in my mind.

It has been a while since the last release, and there have been a number of fixes since then. We should really publish the next one soon

@caitp We're just blocked on gh-2404 . If you could give that a once-over, I'd be happy to release a new version.


x/tools/cmd/godoc: render type aliases in a group

godoc renders each type alias in a dedicated <h2>. Please consider rendering all type aliases in one shared <h2> called Type aliases analogously to how constants and variables are currently rendered. This way, a code refactoring that breaks up a large package by moving a class of type declarations into a dedicated package will reap the benefit of making the table of contents shorter and thus more navigable.

@dmitshur @andybons


Error
Error:
   0: An error occurred during the proxy handshake procedure
   1: invalid SOCKS version 01, expected 04

Metadata

key
value

Version
0.1.3

OS
Windows 11 Education

Command
C:\Users\pznet\Downloads\dispatch-proxy-x86_64-pc-windows-msvc\dispatch-proxy-x86_64-pc-windows-msvc\dispatch.exe -d start <IP_ADDRESS> <IP_ADDRESS> --port 6060

SpanTrace

SpanTrace:
   0: dispatch::socks::handle_request_v4
           with self=SocksHandshake { reader: ReadHalf(PollEvented { io: Some(TcpStream { addr: <IP_ADDRESS>:6060, peer: <IP_ADDRESS>:5845, socket: 924 }) }), writer: WriteHalf(PollEvented { io: Some(TcpStream { addr: <IP_ADDRESS>:6060, peer: <IP_ADDRESS>:5845, socket: 924 }) }), dispatcher: WeightedRoundRobinDispatcher(Mutex { data: WeightedRoundRobinDispatcherInner { ipv4: State { addresses: [WeightedAddress { ip: <IP_ADDRESS>, weight: 1 }, WeightedAddress { ip: <IP_ADDRESS>, weight: 1 }], address_idx: 0, count: 0 }, ipv6: State { addresses: [], address_idx: 0, count: 0 } } }) }
             at src\socks.rs:259
   1: dispatch::socks::handle_handshake_with_version
           with self=SocksHandshake { reader: ReadHalf(PollEvented { io: Some(TcpStream { addr: <IP_ADDRESS>:6060, peer: <IP_ADDRESS>:5845, socket: 924 }) }), writer: WriteHalf(PollEvented { io: Some(TcpStream { addr: <IP_ADDRESS>:6060, peer: <IP_ADDRESS>:5845, socket: 924 }) }), dispatcher: WeightedRoundRobinDispatcher(Mutex { data: WeightedRoundRobinDispatcherInner { ipv4: State { addresses: [WeightedAddress { ip: <IP_ADDRESS>, weight: 1 }, WeightedAddress { ip: <IP_ADDRESS>, weight: 1 }], address_idx: 0, count: 0 }, ipv6: State { addresses: [], address_idx: 0, count: 0 } } }) } version=V4
             at src\socks.rs:121
   2: dispatch::server::handle_socket
           with socket=PollEvented { io: Some(TcpStream { addr: <IP_ADDRESS>:6060, peer: <IP_ADDRESS>:5845, socket: 924 }) } dispatcher=WeightedRoundRobinDispatcher(Mutex { data: WeightedRoundRobinDispatcherInner { ipv4: State { addresses: [WeightedAddress { ip: <IP_ADDRESS>, weight: 1 }, WeightedAddress { ip: <IP_ADDRESS>, weight: 1 }], address_idx: 0, count: 0 }, ipv6: State { addresses: [], address_idx: 0, count: 0 } } })
             at src\server.rs:19

Backtrace

Backtrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: <unknown>
  14: <unknown>
  15: <unknown>
  16: <unknown>
  17: <unknown>
  18: <unknown>
  19: <unknown>
  20: <unknown>
  21: BaseThreadInitThunk
  22: RtlUserThreadStart

Sorry, the plan was to just read the error log from the generated link then read some other issues on here but I guess I misclicked. It works fine in firefox but when I try to do it from windows > internet options > LAN settings > proxy it doesn't. I read some other threads and looks like this isn't a unique problem, sorry again for a duplicate post. Maybe it's just socks5 on windows, I'm no expert so.

Sorry, the plan was to just read the error log from the generated link then read some other issues on here but I guess I misclicked. It works fine in firefox but when I try to do it from windows > internet options > LAN settings > proxy it doesn't. I read some other threads and looks like this isn't a unique problem, sorry again for a duplicate post. Maybe it's just socks5 on windows, I'm no expert so.

I get the smae issue when setting up in Windows 10..did you find any solution

No not really. I tried the Node version and the other go-dispatch version but neither worked. I looked through closed issue threads but couldn't get their solutions working either.


Change to address breaking change to pg 8

node-postgres 8.0 introduced a change:
Change default behavior when not specifying rejectUnauthorized with the SSL connection parameters. Previously we defaulted to rejectUnauthorized: false when it was not specifically included. We now default to rejectUnauthorized: true. Manually specify { ssl: { rejectUnauthorized: false } } for old behavior.
https://node-postgres.com/announcements#2020-02-25
This change is required to allow upgrade of reporting service dependencies https://github.com/lux-group/svc-reporting/pull/1147

Should I make this a new version and tag?

Should I make this a new version and tag?


Support for up-comming --mode library option

Hi,
just started using typedoc and typedocplugin-markdown` today and it is exactly what I was looking for. Thanks for the work on it! 👏
I was looking into auto-generating docs for an npm module. Noticed TypeDoc is developing currently a new mode called --mode module, which is aimed at my use case where you output a single file.
Branch: https://github.com/TypeStrong/typedoc/tree/library-mode
But had an issue using it in combination with typedoc-plugin-markdown:
> typedoc --plugin typedoc-plugin-markdown --theme markdown --mode library --out ./docs/ ./src/index.ts

Loaded plugin typedoc-plugin-markdown

Using TypeScript 3.8.3 from /path/to/project/node_modules/typescript/lib
/path/to/project/node_modules/typedoc-plugin-markdown/dist/theme.js:213
            project.groups.forEach(group => {
                           ^

TypeError: Cannot read property 'forEach' of undefined
    at MarkdownTheme.getNavigation (/path/to/project/node_modules/typedoc-plugin-markdown/dist/theme.js:213:28)
    at NavigationPlugin.onBeginRenderer (/path/to/project/node_modules/typedoc/dist/lib/output/plugins/NavigationPlugin.js:19:44)
    at triggerApi (/path/to/project/node_modules/typedoc/dist/lib/utils/events.js:259:33)
    at triggerApi (/path/to/project/node_modules/typedoc/dist/lib/utils/events.js:110:13)
    at Renderer.trigger (/path/to/project/node_modules/typedoc/dist/lib/utils/events.js:252:13)
    at Renderer.render (/path/to/project/node_modules/typedoc/dist/lib/output/renderer.js:33:14)
    at CliApplication.generateDocs (/path/to/project/node_modules/typedoc/dist/lib/application.js:93:23)
    at CliApplication.bootstrap (/path/to/project/node_modules/typedoc/dist/lib/cli.js:48:26)
    at Object.<anonymous> (/path/to/project/node_modules/typedoc/bin/typedoc:5:5)
    at Module._compile (internal/modules/cjs/loader.js:688:30)

Actually had an issue that ./src/index.ts the file didn't exist. The mode actually works.
Just through the error, I couldn't identify the issue.


BayesianDecisions T2 typo in gaussian formula in slides

Hi,
My students noticed that there is a typo in the W2D1 T2 tutorial video (and slides - slide 34). In the equation for the mixture of Gaussians, the minus sign is missing in the exponent.
Thanks :)

This day has been fully updated for NMA CN 2021.


ERROR 503: Service Temporarily Unavailable.

There is a issue with downloading the archives .
I think the links in the bash script were expired or does not exist.
Please update these. If it is not the problem please look up on this as fast as possible because I was  believing on these projects to make my cad models
This Problem also bugs the Solidworks installer
installer-log.txt

@Lik3Hackdev Thank you very much for this information, but I have looked into your log file and found out that this problem is a temporary issue with no connection to the server for downloading the winetricks packages! ⚠
This issue can sometimes exist when server is down for working or a update and so you must wait for it. ⚙
Please test the installation later. 😊
… and I testing this tomorrow on my Systems. ✅

So, I have checked the connections to servers and it works! :+1:

Yes I think you are right today I reran the script and all worked fine It installed successfully. The servers would have been down when I was running the script.


chore: accept new Cruft update

This pull request includes changes to improve the functionality and usability of the codebase, including adding a wait_for_server_ready function to ensure the server is ready before running tests, modifying the drop_all function to avoid cascade errors, and updating the installation command for Playwright in the README.md file.
Main interface changes:

src/tests/conftest.py: Added wait_for_server_ready function to ensure server is ready before running tests, modified live_server fixture to use this function, and added free_port function to generate a free port on localhost to run the server on.

Bug fixes:

src/fastapi_app/seed_data.py: Modified drop_all function to avoid cascade errors when dropping all tables.

Configuration improvements:

.cruft.json: Updated commit field to d507bca0f2f67be7274add230496456327acef14.

Documentation improvements:

README.md: Updated the installation command for Playwright to use python3 -m playwright instead of playwright.

Minor improvements:

src/fastapi_app/models.py: Modified sql_url variable to include POSTGRES_PORT environment variable in the URL.

ah tests arent working, doesnt like the free port. hm


Add formatting hooks.

Ah, you already added those yourself :) Cool! Merging.

Ah, you already added those yourself :) Cool! Merging.


After installation can't find Marketplace button

🔍 Is there already an issue for your problem?

[X] I have checked older issues, open and closed

ℹ Environment / Computer Info
- Spotify version: I don't know where to find but should be latest according to website
-             Edit: Found to be `<IP_ADDRESS>5.gf2c48e6f`
- Spicetify version: v2.38.4

📝 Description
Downloaded spicetify and spicetify marketplace. Installer asked for Local theme found Do you want to replace it with a placeholder to install themes from the Marketplace? [Y] Yes  [N] No  [?] Help (default is "Y"):, said yes. Screen turned to green mess and either home or marketplace button can't be found
📸 Screenshots

Well, you had Dribblish installed before, so you need to remove it. https://github.com/spicetify/marketplace/wiki/Development#manual-reset

I'm still confused. What exactly do I need to do?

Golly gee I did it


Follow us section added at bottom of page

Follow us section is added at bottom

Summary by CodeRabbit

New Features

Introduced a "Follow Us" section at the bottom of the page for social media engagement.
Enhanced layout with a flexbox design and improved styling for better user experience.

Style

Added new CSS styles for body, links, and emojis to improve visual appeal and interactivity.

hi @KapuluruBhuvaneswariVspdbct
duplicate as #115
also follow this


Some Extra Projects classified into folders

Deals mainly with strings and numbers

Can anybody explain why the checks are  failing?