bumping node version to 18.20.4

Bumping node version to 18.20.4 - this is required for Angular 18. No changes required as upon release the latest version of Node 18 will be pulled.

A developer build has not yet been created for this branch. Click here to go ahead and create the build...


Feature request: Add image scaling algorithms

This is a deliberate omission as the image crate already supports scaling: https://docs.rs/image/0.20.1/image/imageops/fn.resize.html
I'm open to suggestions as to how to flag this in the documentation (and not totally opposed to adding methods here that just forward to those in the image crate).

oh hahaha, I looked for it in the image crate too, but I didn't look hard enough apparently, just close this issue then.
Maybe instead of only flagging only that, you should add to the readme that a user should also look in imageops for the image crate before requesting new features and maybe link to it's docs.
Or just take all of the operations in the imageops in the image crate and just put it all in the imageproc now so that all the available image processing functions are contained in one place, even if it means there are some overlap between crates. I feel like it would be easier even if there aren't that many functions avaiable


Latex - Equation environment in markdown does not work

The formula
\begin{equation}
\begin{split}
a = b \\
c = c
\end{split}
\end{equation}
does not compile, but instead shows
ParseError: Katex parse error: Expected & or \ or \cr or \end at end of input: ...= c \end{split}
\end{equation}
In Jupyter Notebook, this works well.
Environment data

VS Code version: 1.63.2
Jupyter Extension version (available under the Extensions sidebar): v2021.11.1001550889
Python Extension version (available under the Extensions sidebar): v2021.12.1559732655
OS (Windows | Mac | Linux distro) and version: XXX
Python and/or Anaconda version: 3.9.7
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
Jupyter server running: Local | Remote | Local

We believe this may be a regression after recent changes to the markdown renderer in core code.

Also if you try the following cell, it will not work in VS Code
& now that we use vscodes renderer text/latext this will no longer work (when it used to)
Hence marking as regression
%%latex
\begin{equation}
\begin{split}
a = b \\
c = c
\end{split}
\end{equation}

@DonJayamanne  Any way we could have detected this earlier?

Reopening to track shipping this in the recovery
Fix should already be in the next insiders build

@mjbvz
Jupyter actually does not count, and does not care whether the environments are nested. It just runs MathJax 2 in the browser, and looks for the nearest matching pair.

You can take this simple notebook with 3 cells as a test case.
{"cells":[{"metadata":{},"cell_type":"markdown","source":"afi\n\\begin{pmatrix}\n\\begin{bmatrix}\n\n\\end{bmatrix}\n\\end{pmatrix}\nafi"},{"metadata":{},"cell_type":"markdown","source":"afi\n\\begin{pmatrix}\\begin{bmatrix}\\end{bmatrix}\\end{pmatrix}\nafi"},{"metadata":{},"cell_type":"markdown","source":"afi\n\\begin{pmatrix}\n\\begin{pmatrix}\n\n\\end{pmatrix}\n\\end{pmatrix}\nafi"}],"metadata":{"kernelspec":{"name":"python3","display_name":"Python 3","language":"python"},"language_info":{"name":"python","version":"3.6.15","mimetype":"text/x-python","codemirror_mode":{"name":"ipython","version":3},"pygments_lexer":"ipython3","nbconvert_exporter":"python","file_extension":".py"}},"nbformat":4,"nbformat_minor":2}

afi
\begin{pmatrix}
\begin{bmatrix}

\end{bmatrix}
\end{pmatrix}
afi

afi
\begin{pmatrix}\begin{bmatrix}\end{bmatrix}\end{pmatrix}
afi

afi
\begin{pmatrix}
\begin{pmatrix}

\end{pmatrix}
\end{pmatrix}
afi

Jupyter indeed has a lot of quirks, perhaps partially caused by Marked.

It does not comply with CM's "block parsing first" strategy:
fi\begin{align}
a
```
\end{align}
```

is an equation.

It does not allow blank line inside an equation:
\begin{align}
a

\end{align}

is not an equation.


BUG: we do not fit an intercept on sparse X

This makes our estimator different from sklearn's Lasso

Yes. It will yield different results from sklearn's.
A possible, ugly and unsafe workaround is to perform X = [add_dummy_feature](http://scikit-learn.org/stable/modules/generated/sklearn.preprocessing.add_dummy_feature.html)(X, 10000.)
and to center y: y -= np.mean(y)
but that may still cause trouble for CV etc so I wouldn't recommend it.
Fitting an intercept on sparse X is not trivial (see how it is done in cd_fast.pyx in sklearn) I should find time to address this next week.

@corradio next week meant next month :) #20 should address this, we'll merge soon

merged


Add a Gitter chat badge to README.md

203sol/newrelic-rabbitmq-plugin now has a Chat Room on Gitter
@brentpabst has just created a chat room. You can visit it here: https://gitter.im/203sol/newrelic-rabbitmq-plugin.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Declining


Add support for imx7d_pico in BoardDefaults.java

Mappings can be found in: https://github.com/androidthings/contrib-drivers/blob/master/rainbowhat/src/main/java/com/google/android/things/contrib/driver/rainbowhat/RainbowHat.java

@JonathanNakhla Johnathan, I am not sure if @proppy and others at Google have already tested this, but I just did a test on one of our i.MX7D Pico-Pi boards and the code works. Using GPIO_34 for button.
Cheers


Guaranteed Big Tanks in Emergency Closets

About the PR

Got rid of the random chance to have small oxygen/nitrogen tanks in emergency closets and guaranteed the big ones.
Why / Balance

It feels like emergency supplies shouldn't really be random, and the fire closets already had guaranteed large tanks with no problems so far.
I view the smaller emergency oxygen tanks that people start with as just a stopgap you can use until you make it to an emergency closet.
It's kind of a disappointment when you only end up finding another small tank when there's a tesloose or a singuloose going on. It doesn't really make sense for the huge emergency locker to have a tiny oxygen tank...
Technical details

yml change to emergency closets
Media

[ X ] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

None
Changelog

:cl:

tweak: Guaranteed larger oxygen and nitrogen tanks in emergency closets.

 Mug someone and replace it in nitro cannister?

 Mug someone and replace it in nitro cannister?

I can add them to the emergency O2 medkits that come with the small oxygen tank.

Yeah, that would be great.

I might support random like 50% small o2, 50% small n2, 10% double small o2, 10% double small n2 independent probability spawns in addition to guaranteed large tanks

I might support random like 50% small o2, 50% small n2, 10% double small o2, 10% double small n2 independent probability spawns in addition to guaranteed large tanks so as not to make the small tanks super rare for the instances you need them (for example you have something on your back you need to carry (a gun / jetpack maybe?) so you use a tank in a pocket slot instead)

I'd be willing to add a random chance for the smaller ones with the guaranteed large tank.

It feels like emergency supplies shouldn't really be random, and the fire closets already had guaranteed large tanks with no problems so far.

If emergency supplies are guaranteed what's the point of having them, the stakes get dropped to the floor when everyone is guaranteed to survive everything.

(discord continuation)
seems like the conclusion is to... get rid of the chance of large tanks altogether from emergency closets (and fire closets?) in favor of using tank dispensers or crafting it at autolathes, so I'll just close the PR. I'm fine if it's intended to go to specific places to get the larger tanks, it was just really annoying knowing when you got screwed by a 20% chance to get a larger tank from a closet


feat(Add fastexcel-annotation module): [#135]

Extract annotations so that po only needs to depend on fastexcel-annotation

The changes are quite extensive, so we’ll hold off on merging for now. Awaiting further discussion and reviews from others.
变动太大，暂时不合并。等待讨论和其他人的CodeReview。

请问还有什么我能做的吗
我该如何加入你们


Adding new message in Chinese

adding new message in Chinese

https://github.com/spring-projects/spring-petclinic/pull/1263

I will complete subsequent language updates

Closing in favor of #1263


Add "logwright" SDE solver functions

[x] Closes #1856
[x] I am familiar with the contributing guidelines
[ ] Tests added
[ ] Updates entries in docs/sphinx/source/reference for API changes.
[ ] Adds description and name entries in the appropriate "what's new" file in docs/sphinx/source/whatsnew for all changes. Includes link to the GitHub Issue with :issue:`num` or this Pull Request with :pull:`num`. Includes contributor name and/or GitHub username (link with :ghuser:`user`).
[ ] New code is fully documented. Includes numpydoc compliant docstrings, examples, and comments where necessary.
[ ] Pull request is nearly complete and ready for detailed review.
[ ] Maintainer: Appropriate GitHub Labels (including remote-data) and Milestone are assigned to the Pull Request and linked Issue.

This PR implements two new functions in pvlib.singlediode: _logwright_v_from_i and _logwright_i_from_v.  The reference from #1856 (link) provides the v_from_i equation.  I used the same technique to derive the i_from_v equation.  I plan to document the equations in our singlediode.rst page.
The new base functions are then integrated into the rest of the SDE solving machinery.  Here are some runtimes for the pvsystem.i_from_v, v_from_i, and singlediode functions comparing method='lambertw' with method='logwright':

@cwhanse I wonder if you can provide some insight on the calculation result differences I am seeing, relative to the values from method='lambertw'.  In particular the identified vmp and its downstream values are much less accurate than the other values, so I suspected something with the golden section search may be the cause.  However, setting a stricter tolerance in the golden section search doesn't make much difference.  I also looked at the differences from logwright to newton and lambertw to newton, and they're all about the same as this:

@kandersolar you are plotting Vmp (logWright) - Vmp (lambertw)?
What happens if you increase the iterations in tools._logwrightomega?

The curves in the precise_iv_curve*.json files are precise (to 15 significant figures), maybe we can benchmark the three solvers against those (lambertw, log Wright, netwon). Sorry if the format is inconvenient.

@kandersolar you are plotting Vmp (logWright) - Vmp (lambertw)?

Yep.

What happens if you increase the iterations in tools._logwrightomega?

No meaningful change.  I also tried switching to scipy's implementation of the Wright Omega function, and no change there either.

The curves in the precise_iv_curve*.json files are precise (to 15 significant figures), maybe we can benchmark the three solvers against those (lambertw, log Wright, netwon).

Good idea!  I will try that.

Here is a comparison of the various methods, calculating error relative to the "Case 1" known values in https://github.com/cwhanse/ivcurves/tree/main/ivcurves/test_sets:

So newton and brentq do quite well, but the two lambertw-style approaches have some trouble finding the MPP.
Putting aside logwright for the moment, I think I have narrowed the MPP issue down to the golden section search function performing poorly at the peak of the P-V curve, which is relatively flat and broad.  Specifically, P varies by only an ULP or two (~10^-15) over a voltage range of order 10^-7, so unsurprisingly the golden section search has trouble navigating that region.  Here is a plot showing the P-V curve and comparing identified MPPs (horizontal lines show a 1-ULP step, since matplotlib refuses to show tick labels at such a small scale):

Just to see if another search method might work better, I swapped scipy's powell in place of our golden section search and got somewhat better convergence in this single example, but still not as good as the bishop/brentq method.  I am curious how it is that brentq seems to handle this problem so reliably.
Anyway, this is starting to sound like a bug report for _golden_sect_DataFrame.  Perhaps this should be a new issue?

Nicely laid out. Your findings are consistent with my own assessments.
The lambert W methods find the maximum of the (V, P) curve. The bishop88 methods find the zero of the dP/dV curve. I'm not sure the difference is a bug in the usual sense. When that approach was taken, I'm sure we thought 8 digits of accuracy sufficed, and may not have realized the shortcoming in that approach.

I seem to recall another discussion about (vectorized?) root finding recently, but I can't remember where.  Could someone point me to it?

#1661

Or #974.

If the blue line above from the precise IV curve, would it be possible to make it even more precise, or perhaps more ideal, by removing the dithering so it steps up on the left and down on the right of Pmp?

  The blue line in that plot was from lambertw_i_from_v.  The precise curves would presumably not suffer from such numerical artifacts, but they also doesn't have nearly the voltage resolution needed to show them anyway.

Or #974.

That's the one, thanks!

there was a similar issue in pvmismatch which was using argmax to find the max power point (MPP), but in issue 65 there were discontinuities/jumps similar to the issue described for LambertW approach. A simple solution was to calculate the derivative around MPP using central difference and interpolate to find a better zero.

Mmmm, can I be of help with this PR? I see the discussion revolves around the precision of each algorithm, but that doesn't invalidate the fact that logwright is still faster (if I understood correctly).

The convergence error discussed above is large enough to make me uncomfortable, but probably not too large to keep the method from being useful.  The other thing is that only the v_from_i equation has a reference; I derived the i_from_v equation myself.
This PR currently shows that the logwright method has promise, but IMHO a short paper defining the complete method and comparing speed+accuracy with other methods needs to be written before this PR gets picked up again.


Getting the FQDN (or public ip) of a load balancer is not fluent

To get the public facing ip of a load balancer, we can get the IP id in a fluent manner, but then we have to call the base azure object to get the corresponding IP for the IP id provided.
var ipList = azure.VirtualMachineScaleSets.GetByResourceGroup("xxxxx","xxxxx").GetPrimaryInternetFacingLoadBalancer().PublicIPAddressIds
azure.PublicIPAddresses.GetById(ipList.First()).Dump()
This isn't too fluent. It would be ideal if PublicIPAddressIds would return a list of IP objects with .PublicIpAddress property on it.
Thoughts?
I could be fetching the IP address wrong, how should I go about it so it's fluent?
Cheers,
Ofek

@Ofekw can you give us more details, what version of SDK you are referencing to.
Also is this .NET Fluent library?

@Ofekw can you open an issue in the Fluent repo
https://github.com/Azure/azure-libraries-for-net/
Closing...


Concurrent interactive transactions get queued

Bug description
Currently if 2 transactions are sent concurrently that lock the same row,
How to reproduce

https://github.com/matthewmueller/interactive-transactions
Expected behavior
The transactions should be serialized.
Prisma information

Environment & setup

OS:
Database:
Node.js version:

Prisma Version

Duplicate of https://github.com/prisma/prisma/issues/8707


Height auto on element

Hey, I've just update to version 2.3.11 the js code is adding height: auto on html, body and main because of this line. I want a height: 100% and it is pretty hard to override an element css rule. Is there another way to fix #1191 without doing this?

Hello @wen96,
Adding height:auto allows the browser to scroll automatically to the last position upon refresh of the page. However, if you find it necessary to have height 100%, then you could add js line after loading app.js to fix this.
I don't believe that this line is causing issue #1191. There is something else that we are missing.
$(function() {
  $('html, body, .wrapper').css('height', '100%');
})

Thanks!

Hey, thanks for answer. I don't mean that the line is causing the issue #1191, what I mean is that the fix for the issue is causing a new "issue". And what I'm asking for is to solve #1191 on a different way to avoid the new issue. I know, I can fix it overriding the the css class with javascript after AdminLTE is loaded but I don't want to introduce load-order dependencies on my project, it is not good for code maintenance.
TL;DR; The fix for #1191 introduces a new "non-desired" behavior. Could we fix it on a different way?

Same here. This fix is killing a fullscreen cover background on  element on the login page template.

Is this going to be addressed?

Maybe an option could allow to active this behavior. Form what I see app.js must not be incuded in login pages but it must be the case for all other pages:

Page source: https://adminlte.io/themes/AdminLTE/pages/examples/login.html

<!-- jQuery 3.1.1 -->
<script src="../../plugins/jQuery/jquery-3.1.1.min.js"></script>
<!-- Bootstrap 3.3.7 -->
<script src="../../bootstrap/js/bootstrap.min.js"></script>
<!-- iCheck -->
<script src="../../plugins/iCheck/icheck.min.js"></script>

Page source: https://adminlte.io/themes/AdminLTE/pages/forms/general.html

<!-- jQuery 3.1.1 -->
<script src="../../plugins/jQuery/jquery-3.1.1.min.js"></script>
<!-- Bootstrap 3.3.7 -->
<script src="../../bootstrap/js/bootstrap.min.js"></script>
<!-- FastClick -->
<script src="../../plugins/fastclick/fastclick.js"></script>
<!-- AdminLTE App -->
<script src="../../dist/js/adminlte.min.js"></script>
<!-- AdminLTE for demo purposes -->
<script src="../../dist/js/demo.js"></script>

When working with Single pages applications, all main js script must be added to the main page to be loaded. So it would be bad to not import app.js (adminlte.min.js in this example). But when imported, it break the login page because of the $.AdminLTE.layout.activate() call.

I'm also running into this issue.  I'm not sure why this is done in the Js and not in the style of the template.  This seems like it would be better to use the template for this and not to put it in the Javascript.  Then it would make it easier for us to change it.

It appears that the only fix that seems to work is...
	<style>
		html {
			height: 100% !important;
		}
	</style>

Is this issue still open in v2.4.12?


Official launch of documentation site

Explanation
We're in the process of launching an official documentation site that will provide user-friendly information about our library API, and will automatically keep up-to-date with the contents of the JSDoc comments in our codebase.
(Example live site deployed from fork: https://majorlift.github.io/hkt-toolbelt/)
The following are the remaining tasks in that process:
Deployment

[x] https://github.com/poteat/hkt-toolbelt/pull/68

[ ] Configure GitHub Pages to deploy from gh-pages
[ ] Configure official documentation URL:
a) Use poteat.github.io/hkt-toolbelt (conflict with code.lol?)
b) Transfer repo into hkt-toolbelt organization and use hkt-toolbelt.github.io
c) Purchase new domain
[ ] Add documentation link to repo "About" section

[ ] https://github.com/poteat/hkt-toolbelt/pull/66

[ ] Update links in PR to official URL

[ ] Announcements

Contents

[ ] https://github.com/poteat/hkt-toolbelt/issues/69
[ ] https://github.com/poteat/hkt-toolbelt/issues/70

References

Closes https://github.com/poteat/hkt-toolbelt/issues/63
Closes https://github.com/poteat/hkt-toolbelt/issues/18

@poteat Is there anything blocking the documentation site from being launched? We're currently publishing the GitHub Pages to the gh-pages branch with the "Publish docs to GitHub Pages" action, but it seems like the docs aren't being deployed to a public website from there.
These are the steps to deploy:

Navigate to "Settings - Pages - Build and Deployment"
Configure the following:
Source - "Deploy from a branch"
Branch - "gh-pages", "/(root)"

I think even with incomplete coverage, an up-to-date docs website would be less confusing for new users than the outdated API docs we currently have in the readme.

Closed by #66


Pet Task: Add recurring icon and label to tasks

Add the recurring label to Pet Tasks per the design below. Use the Geeks theme icon for 'Social Profiles' here: https://geeksui.codescandy.com/geeks/pages/dashboard-instructor.html

Can I take it?

@wandergithub all yours

this can be closed.


Fixed typo on foundry.md

AssertTest.test_assert_true to AssumeTest.test_assume_true

Why this change? Both tests exist, so they shuold both be fine for the test.

Why this change? Both tests exist, so they shuold both be fine for the test.

Do they? I only see AssumeTest here: https://github.com/runtimeverification/evm-semantics/tree/master/tests/foundry/test

The AssertTest are here: https://github.com/runtimeverification/evm-semantics/blob/master/tests/foundry/test/Simple.t.sol
The selector slug --test ... lets you specify ContractName.test_name, not FileName.test_name.

You're right, my mistake


Add an Official Changelist

So I don't have to look up everything retroactively.

Been handling this pretty good lately so solved as far as I care to declare it.


Integrating In Progress Branches

I have started getting a bit acquainted with the state of the PolicyKit code base and wanted to open an issue to report on my current status and discuss possible ways forward.
There are two main pieces of unmerged work, which I will go into in more detail below. I am working to see what is the most straightforward way to get both into the master branch, but leaving it in a state that is deployable for the metagov instance to use (as well as any other instances, if there are others). After that, it should be easier to continue work on new feature development.
I have been able to get both working locally by merging in https://github.com/policykit/policykit/pull/633 (and consequently, master), to get them up to date and working with Docker for development. So I also have versions of both branches with those merge commits as well as some necessary fixups, but have not attempted any improvements on either yet.
Any corrections to the below are welcome, I am trying to piece this together without having worked on either of these, and I also may have messed things up as I was merging in master.
UI Refactoring Branch
Author: @antiantivirus
Original branch: policykit:new-frontend #632
My version: saulshanabrook:new-frontend
Changes:

rework the main UI
Split large Django templates into smaller modular pieces
Starting use tailwind css
Add a few REST API endpoints to serialize things as JSON

I believe the intent was for this branch to prepare things to start switching the frontend to using React, hence the REST API endpoints, but don't yet see any activity actually using React yet.
Also at least in my version of the branch some of the UI is not finished yet and represents a degradation over the current outdated UI, which seems like it would be the main glaring thing that would have to be fixed before it could be merged. I have not tested it any way exhaustively, just clicked around a bit.

No Code UI Branch
Author: @leijie-wang
Original branch: leijie-wang:new-ux-flows #635
My version: saulshanabrook:new-ux-flows
Changes:

Adds new no-code UI for creating policies at /no-code/main, preserving the existing interface at /main. This is all implemented in jquery, without any build step.
Adds some database migrations as well

It seems to mainly be working. I am unable to add a governing policy, but I am not sure if that's because my instance isn't set up properly. However, since it exists as a separate URL, more work is needed to actually integrate it into the main UI, even though it could be possible to merge it as is and have it be available opt-in for users, as long as the migrations are not destructive (they do delete some fields).

Just chatted with @amyxzhang, I am going to open a PR for the no code UI, to see if we can get that deployed first. She was saying getting both the UI refactor and that no code UI integrated are necessary before a more public release.


ICRC-25 reference implementation

This PR adds a reference implementation for the ICRC-25 standard. It includes:

an example relying party
an example signer
a simple target canister implementing the ICRC-21 standard

The implementation in its current state is outdated and is based on the draft version from #32.

Thanks a lot for all the work! It still needs some polishing, but I think it is a good start. 🙂

@frederikrothenberger I updated the PR according to the feedback, I hope I haven't missed anything.


Network boot...

Hi and thank you for a great tool :)
I´m hoping anyone here can help me. I´m using mdt to deploy Windows 10. After mdt deploys bios settings, it reboots and goes straight to network boot. I have no idea why. Any ideas?

Please attach the BIOS-Settings.txt you are using and also the log output of BIOS Sledgehammer so I can get an idea where this problem comes from.

Here is the bios settings file
BiosConfigProdesk600G1.txt
Can you please explain where i can find the log output of sledgehammer?

OK, and the file is called how on your installation in which folder? Because that filename will never be used by BIOS Sledgehammer so the file would be ignored.
How do you boot into MDT - using a USB stick or Network boot? Also, does the machine at least boot once from C: before executing BIOS Sledgehammer or do you try to change the BIOS Settings in the PE (first) phase?
The location of the log file is described in readme.md (directly below the file list when you click on the "Code" tab in this repo).

As there was no response in a long time, I'm closing this issue. Please feel free to reopen it again if you think this incorrect.


Fancy Zones Editor

Description of the new feature / enhancement
Fancy Zones Editor should have the ability to flip layouts horizontally and vertically
Scenario when this would be used?
allows consideration of symmetrical fancy zones being used in multi monitor setups.

^ these layouts are completely symmetrical and the second one could be easily created with the ability to just mirror the first layout vertically. Instead of having to manually make it like I ended up having to do.
Supporting information
No response

Just starting to get into FancyZones - this was an option I was hoping to find buried somewhere. It's not a big deal, can just make "opposite" layouts as you did, but making one layout with a mirror button/hotkey OPTION would be a addition great for a program intended to streamline and declutter how you use your computer.


[Feature Request] app.ini Item for Listen address

Currently it seems as though "<IP_ADDRESS>" is hardcoded without a way to change it.
I would like to request a config item in app.ini to be able to set the listening address to a specific IP.
Use case could be a Server with several network interfaces / ip addresses in different networks and wanting peach to only be served on one of them.
Another use case (my actual use case) would be to use a webserver like apache or nginx with reverse proxy. In this case we need to only listen on localhost.

#46


There is a problem in parsing this file. It is currently pom.xml Is it incomplete?

In addition to the image below, do I need to import other dependencies?

No, it's OK to configure the current remote log address for logback. The remote log can be combined with logback normally. It's included in the documentation. Take a look. So you don't have to deal with it yourself. After adding the adapter of logback, all logs can be customized to remote. The format and log structure are subject to the configuration of logback. (description document is doc.tarsyun.com )

不需要的，logback配置现在的远程日志地址就好了，远程日志可以正常的和Logback结合了，说明文档里面都有。可以看一下。所以不用自己处理了，增加上logback的适配器后，所有的日志都可以自定义到远程，格式和日志的结构以logback的配置为准即可。(说明文档为doc.tarsyun.com)

Which part of the document is the combination of concrete logback.xml and tars?

具体的logback.xml与tars的结合的文档是在哪一部分？


GEOMESA-3042 GeoMesa Accumulo 2 Spark Runtime is missing GeoCQEngine …

…DataStore
Signed-off-by: Jim Hughes<EMAIL_ADDRESS>

lgtm, did you run the cqs script to make sure nothing changed?

lgtm, did you run the cqs script to make sure nothing changed?

I hadn't; good catch, thanks for the reminder.  It did come back clean.
As a note, I only tried this with the HBase 2 Spark runtime with Spark 2.4.7 (and Scala 2.11).  Separately, I tried it with one or two Scala 2.12/Spark 3.1.1 jar.
Hopefully that's a sane enough spot check (or should we test 8-12 combinations?).


Look at Helium

https://github.com/cardinalb/helium-docs/wiki

I don't think we are still looking at Helium, are we?
@StevenCannon-USDA @jd-campbell

I don't think we are still looking at Helium, are we? @StevenCannon-USDA @jd-campbell

It's been back-burnered, but I don't think we've abandoned it. We still need a pedigree viewer. Helium is nice. One of the developers (Sebastian Raubach) gave some instructions in May about how to send data via URL into their hosted instance:
Basically, on the Germinate side, we generate a .zip file containing both the pedigree and, optionally, trait data.
The pedigree file *has* to be called “pedigree.helium” and the trait file *has* to be called “pedigree-attributes.helium”.
They both obviously have to follow the supported file formats of Helium.
The generated .zip file has to be accessible publicly on a web server without authentication.
Germinate then generates a link the user can click on, that’s of the form: [https://helium.hutton.ac.uk/#/pedigree?germinateUrl=https%3A%2F%2Fics.hutton.ac.uk%2Fgerminate-demo%2Fapi%2Fdataset%2Fexport%2Fasync%2F04af1e2d-b931-4f60-8571-6b54d216e4e8%2Fdownload](https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelium.hutton.ac.uk%2F%23%2Fpedigree%3FgerminateUrl%3Dhttps%253A%252F%252Fics.hutton.ac.uk%252Fgerminate-demo%252Fapi%252Fdataset%252Fexport%252Fasync%252F04af1e2d-b931-4f60-8571-6b54d216e4e8%252Fdownload&data=05%7C02%7Csteven.cannon%40usda.gov%7Cf0109f232b4d4fec4cf108dc765cc6d7%7Ced5b36e701ee4ebc867ee03cfa0d4697%7C1%7C0%7C638515388077567513%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=lpav9n768H17f3Uaq86by3SzYLw659sv6%2BWRHSwUDwM%3D&reserved=0)
Basically: https://helium.hutton.ac.uk/#/pedigree?germinateUrl={URL TO YOUR ZIP BUT URL-ENCODED}
This will open Helium on the import screen for Germinate data with your URL loaded.
You can then click import to load the data.


Hey

How is it going. Seeing if there are any updates to this project

do you know how to make it work ? is there a copy for computer so i can run easy ? i am not a programmer


Add a ROADMAP

TL;DR add a ROADMAP file
Our first release won't be the fully usable thing we intend to achieve (and need for ourselves). However, we want to release early and not wait until everything is perfectly done.
Users visiting the project after the first release should have a clear understanding where the project is right now and what and in which order they can expect certain things.

We added a ROADMAP section to the README: https://github.com/kubernetes-incubator/external-dns#roadmap


[5.5] Queue ResetPassword notification

I think it's fairly reasonable assumption that all sent emails are queued when app is utilizing job queues.
While even now it's easy to make reset password email queueable, it's a bit tedious in a sense that you need to override sendPasswordResetNotification on a User model and than extend default ResetPassword notification to implement an interface. This isn't something I wish to bother with when scaffolding default authentication.
With sync driver it makes no difference whether the queue and workers are configured or not for this to work so this should be a safe change.

I can't change this on a point release.


[BUG]

Describe what happened:
Upgrading Datadog helm chart from version 3.30.6 to the latest caused the system-probe container to go into CrashLoopBackOff.
The cause of this issue has been identified as an agent issue and not a helm issue due to the fact that if we pin the agent version to 7.44.1 and upgrade the helm chart to the latest, the pods start as expected.
Describe what you expected:
Datadog to be upgraded
Steps to reproduce the issue:
Install Datadog helm chart version datadog-3.31.0 or version 7.45.0 of the agent
Additional environment details (Operating System, Cloud provider, etc):
OS:
Ubuntu 20.04.6 LTS
Agent Version
Agent (v7.45.0)
k8s:
Client Version: v1.25.2
Kustomize Version: v4.5.7
Server Version: v1.24.14+rke2r1
Snippet of the failing POD logs:
2023-07-07 10:20:45 UTC | CORE | ERROR | (pkg/workloadmeta/collectors/internal/kubemetadata/kubemetadata.go:73 in Start) | Could not initialise the communication with the cluster agent: temporary failure in clusterAgentClient, will retry later: "https://<IP>:<PORT>/version" is unavailable: 403 Forbidden

2023-07-07 10:20:48 UTC | CORE | ERROR | (pkg/autodiscovery/config_poller.go:149 in poll) | Cache processing of cluster-checks configuration provider failed: temporary failure in clusterAgentClient, will retry later: try delay not elapsed yet

2023-07-07 10:20:48 UTC | CORE | ERROR | (pkg/autodiscovery/config_poller.go:211 in collect) | Unable to collect configurations from provider endpoints-checks: temporary failure in clusterAgentClient, will retry later: try delay not elapsed yet

2023-07-07 10:21:51 UTC | CORE | ERROR | (pkg/autodiscovery/config_poller.go:211 in collect) | Unable to collect configurations from provider endpoints-checks: failed to unmarshal JSON from URL: api/v1/endpointschecks/configs/<HOSTNAME>, err: unexpected end of JSON input

2023-07-07 10:21:52 UTC | CORE | WARN | (pkg/autodiscovery/providers/clusterchecks.go:197 in heartbeatSender) | Unable to send extra heartbeat to Cluster Agent, err: failed to unmarshal JSON from URL: api/v1/clusterchecks/status/<HOSTNAME>, err: unexpected end of JSON input

system-probe container
system-probe:
    Container ID:  containerd://<ID>
    Image:         gcr.io/datadoghq/agent:7.45.0-jmx
    Image ID:      gcr.io/datadoghq/agent@sha256:c60572ca5a837d3f436b3fb083901882f22e73715aa24a23a63c9a9f99c0096f
    Port:          <none>
    Host Port:     <none>
    Command:
      /opt/datadog-agent/embedded/bin/system-probe
      --config=/etc/datadog-agent/system-probe.yaml
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Error
      Exit Code:    255
      Started:      Fri, 07 Jul 2023 11:23:02 +0100
      Finished:     Fri, 07 Jul 2023 11:23:02 +0100
    Ready:          False
    Restart Count:  5
    Environment:
      GODEBUG:                                          x509ignoreCN=0
      DD_API_KEY:                                       <set to the key 'api-key' in secret 'datadog'>  Optional: false
      DD_AUTH_TOKEN_FILE_PATH:                          /etc/datadog-agent/auth/token
      DD_CLUSTER_NAME:                                  compute-k8s-gb01-emea-sit
      DD_TAGS:                                          <TAGS>
      KUBERNETES:                                       yes
      DD_KUBERNETES_KUBELET_HOST:                        (v1:status.hostIP)
      DD_ENV:                                           sit
      DD_HOSTNAME:                                       (v1:spec.nodeName)
      DD_SECRET_BACKEND_COMMAND:                        /readsecret_multiple_providers.sh
      DD_OTLP_CONFIG_RECEIVER_PROTOCOLS_HTTP_ENDPOINT:  <IP_ADDRESS>:4318
      DD_LOG_LEVEL:                                     INFO

Output from Datadog status
============
System Probe
============
  Status: Not running or unreachable
  Error: temporary failure in system-probe-util, will retry later: Get "http://unix/debug/stats": dial unix /var/run/sysprobe/sysprobe.sock: connect: connection refused

@AMC-7 did you upgrade helm chart version or agent version?

@AMC-7 did you upgrade helm chart version or agent version?

It was the version of the agent causing the issues. We pinned the agent to 7.44.1 and went to the latest helm version.

@AMC-7 did you upgrade helm chart version or agent version?

It was the version of the agent causing the issues. We pinned the agent to 7.44.1 and went to the latest helm version.

Same issue encountered today with the latest build with helm  version 3.36.2 -- stable for me is 3.34.3. will try others later.

I had the same problem with 7.48.1 and downgrading to the mentioned 7.44.1 helped.

We are running into the same issue with agent version 7.48.1. Just wondering why this issue has been marked as fix while it appears to not have been fixed (yet)?


Using hash-bang instead of pushstate with Reach router

I have a scenario where I'd like to enable fragment or hashbang instead of pushstate.
How would I enable that in Reach? Is it possible? What is the fallback mode for Reach if a browser does not support pushstate?

#25


Misror error in window on pip install-e

Hello author ,I have successfully compiled the hit library on the linux system but not the pip install-e. compile in window. Do you know what versions of vs and ninija to compile on the window system?Thanks so much for your reply.

I did not try the program in windows, so I can't answer that. I don't remember needing ninja for linux


Added CocoaError messages

Add missing error messages for known CocoaError codes.
Generated from playground on macOS 10.14.4

CC @millenomi @compnerd

@swift-ci please test

@millenomi Ok, but to be clear, at the moment there is no support for NSLocalizedString() on non-Darwin platforms right?

NSLocalizedString(…) should work, and bundle resources work as well. We just don't have the string files, or a bundle for the Foundation module.


1.0.0

Hey, @danicarrion @javisantana
In my opinion 1.0.0 branch is ready to be merged into master.
What do you think?
BTW, once I have to merge, how should I do it? Seems like both branches won't automatically merge...
EDIT: OK seems like there are only 3 conflicting files... not an issue.

About the docs, are we planning to publish it in our website? (Nice to see
sphinx there 😀)
Do we have CI integration?
On Thu, May 11, 2017, 09:49 Alberto Romeu<EMAIL_ADDRESS>wrote:

Hey, @danicarrion https://github.com/danicarrion @javisantana
https://github.com/javisantana
In my opinion 1.0.0 branch is ready to be merged into master.
What do you think?
BTW, once I have to merge, how should I do it? Seems like both branches
won't automatically merge...
You can view, comment on, or merge this pull request online at:
https://github.com/CartoDB/carto-python/pull/52
Commit Summary

total rewrite with some new features
made some edits and tests for NoAuthClient
removed comments and extra code
Merge pull request #20 from CartoDB/r-edits
finished import tests
fixed python sdk func
minor corrections
Merge pull request #23 from CartoDB/r2
working on carto export
working within sdk
simplifying exportjob, revising tests
have a working and polished export job, going to work on export
manager
checking that everything works
stopped working on exportManager and exportJob works and is cleaned
up
this works on my machiens, will merge with remote
finished export, code polished, git will be up to status, going to
work on named maps
got methods working, need to transform to sdk style and then
implement manager
made the maps_api more like import_api
finsihed named maps, and the format matches import_api, just need to
figure out namedMapManager
got manager to work pretty well
fixed small issues with maps_api file
updated file
fixed small edits in exportJob
Merge pull request #26 from CartoDB/r-export
fixed some pep8 stuff
started work on batch sql api
finishing up batch api functions and dealing with update
finished most of the commands in the batch api, need to talk to dani
fixed namedMapManager and altered namedMaps
finished namedmaps and manager and tests
fixed import_api formatting
fixed formatting
fixed slightly faulty test
trying to get namedmaps mergeable
cleaned up batch api, ready for review
Merge branch '1.0.0' into r-namedmaps
finished last bits of edits
Merge pull request #28 from CartoDB/r-batch
fixed test
pushing namedmaps when merge with everything else
test suuite working
fixed h_method
Merge pull request #27 from CartoDB/r-namedmaps
the python sdk should be fully functional
finished last bit
fixed sqlclient name
Merge pull request #29 from CartoDB/r-docs
made sdk more pythonic
make small edits
no files for testing
Merge pull request #30 from CartoDB/r-docs
massive refactoring, interim commit
user tests pass
comment user tests
dataset tests now pass too (still interim release!!!)
emptied main init.py
rough refactor to use pyrestcli
moving everything to the project root
test folder renamed, tests out of setup.py
everything migrated to pyrestcli except maps, sql and exports
visualizations can be exported
added pyrestcli dependency to requirements.txt
CartoException was accidentally gone
Fixed params in constructor call
fixed visualization export state options
minor changes to work with pyrestcli
removing batch manager
fix on sending requests to bath sql api
Merge pull request #33 from CartoDB/remove-sqlbatchmanager
Merge pull request #34 from CartoDB/jsanz-fix-sendsqlbatch
Auth and SQL clients store base_url and username, base_url doesn't
expect trailing /api anymore
Enforce trailing / from base_url
Merge pull request #46 from dmed256/1.0.0
added ORGANIZATION variable since it is needed for test fixtures
Added tests for auth.py
Updated README.md with instructions to run tests
excludes carto.com/u/ since api endpoints go to .
carto.com
Fixed malformed named map template JSON
Fixed named maps APIs
removes unneeded test
added API method to instantiate anonymous maps
Merge pull request #48 from CartoDB/auth-username-fix
moved tests for the SQL API to pytest
updated to pyrestcli 0.6.2. This change breaks compatibility with
pyrestcli 0.6.1, so you need to upgrade requirements
Use pyrestcli's new session argument
Merge pull request #51 from dmed256/1.0.0
Merged changes in 1.0.0 related to pyrestcli new session parameter
fixed file import API and added tests
fixes #14
Reverting some tests related to file import API since they were
already in the datasets manager tests
ensuring non existing named maps before creation
added myself as a contributor
fixes #32
Added .idea folder to gitignore
Added DS_Store to gitignore
Fixes #38
Added examples from the examples branch
removed old tests
Fixed example description
Change dataset privacy example
Example to export a map as a .carto file
Example for creating a named map
minor fix
Added instantiate map example
removed unused code
Create anonymous map example
Organized examples
Adapted to a change in pyrestcli
Handling exceptions
Added Sphinx API docs
Added API docs in README.md
Updated README.md
Updated requirements and added README.md for the examples folder
Merge branch '1.0.0' into 1.0.0-namedmaps
Update to version 0.6.3 of pyrestcli
Fixed coding style
Added local variables to gitignore
Fixed coding style
Fixed coding style
Fixed coding style
Fixed coding style
Merged changes
Fixed a bug when building maps API urls
Fixed coding style
Added API for downloading map tiles
Merge pull request #49 from CartoDB/1.0.0-namedmaps
Added warnings when using non-public APIs
Updated README.md
Added warnings for non-public APIs in the API docs

File Changes

M .gitignore
https://github.com/CartoDB/carto-python/pull/52/files#diff-0 (4)
M CONTRIBUTORS
https://github.com/CartoDB/carto-python/pull/52/files#diff-1 (2)
M README.md
https://github.com/CartoDB/carto-python/pull/52/files#diff-2 (380)
R carto/init.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-3 (0)
A carto/auth.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-4 (106)
A carto/datasets.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-5 (198)
A carto/exceptions.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-6 (19)
A carto/export.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-7 (74)
A carto/fields.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-8 (49)
A carto/file_import.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-9 (155)
A carto/maps.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-10 (236)
A carto/paginators.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-11 (49)
A carto/permissions.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-12 (44)
A carto/resources.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-13 (106)
A carto/sql.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-14 (224)
A carto/sync_tables.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-15 (152)
A carto/tables.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-16 (65)
A carto/users.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-17 (109)
A carto/visualizations.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-18 (162)
D cartodb/init.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-19 (4)
D cartodb/cartodb.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-20 (278)
D cartodb/imports.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-21 (189)
A doc/Makefile
https://github.com/CartoDB/carto-python/pull/52/files#diff-22 (20)
A doc/build-doc.sh
https://github.com/CartoDB/carto-python/pull/52/files#diff-23 (7)
A doc/source/carto.rst
https://github.com/CartoDB/carto-python/pull/52/files#diff-24 (134)
A doc/source/conf.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-25 (153)
A doc/source/index.rst
https://github.com/CartoDB/carto-python/pull/52/files#diff-26 (20)
A doc/source/modules.rst
https://github.com/CartoDB/carto-python/pull/52/files#diff-27 (7)
A examples/README.md
https://github.com/CartoDB/carto-python/pull/52/files#diff-28 (21)
A examples/change_dataset_privacy.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-29 (59)
A examples/check_query.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-30 (77)
A examples/create_anonymous_map.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-31 (57)
A examples/create_named_map.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-32 (59)
A examples/export_map.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-33 (53)
A examples/files/anonymous_map.json
https://github.com/CartoDB/carto-python/pull/52/files#diff-34 (27)
A examples/files/barris_barcelona_1_part_1.csv
https://github.com/CartoDB/carto-python/pull/52/files#diff-35 (10)
A examples/files/barris_barcelona_1_part_2.csv
https://github.com/CartoDB/carto-python/pull/52/files#diff-36 (11)
A examples/files/barris_barcelona_1_part_3.csv
https://github.com/CartoDB/carto-python/pull/52/files#diff-37 (11)
A examples/files/barris_barcelona_1_part_4.csv
https://github.com/CartoDB/carto-python/pull/52/files#diff-38 (11)
A examples/files/barris_barcelona_1_part_5.csv
https://github.com/CartoDB/carto-python/pull/52/files#diff-39 (11)
A examples/files/barris_barcelona_1_part_6.csv
https://github.com/CartoDB/carto-python/pull/52/files#diff-40 (11)
A examples/files/barris_barcelona_1_part_7.csv
https://github.com/CartoDB/carto-python/pull/52/files#diff-41 (15)
A examples/files/instantiate_map.json
https://github.com/CartoDB/carto-python/pull/52/files#diff-42 (3)
A examples/files/named_map.json
https://github.com/CartoDB/carto-python/pull/52/files#diff-43 (42)
A examples/import_and_merge.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-44 (140)
A examples/import_standard_table.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-45 (64)
A examples/import_sync_table.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-46 (74)
A examples/import_sync_table_as_dataset.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-47 (68)
A examples/instantiate_named_map.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-48 (65)
A examples/kill_query.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-49 (54)
A examples/list_tables.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-50 (224)
A examples/map_info.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-51 (85)
A examples/requirements.txt
https://github.com/CartoDB/carto-python/pull/52/files#diff-52 (4)
A examples/running_queries.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-53 (56)
A examples/sql_batch_api_jobs.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-54 (75)
A examples/table_info.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-55 (175)
A examples/user_info.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-56 (102)
M requirements.txt
https://github.com/CartoDB/carto-python/pull/52/files#diff-57 (6)
D secret.py.example
https://github.com/CartoDB/carto-python/pull/52/files#diff-58 (9)
M setup.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-59 (26)
D test/client.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-60 (63)
A tests/conftest.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-61 (54)
A tests/fake.html
https://github.com/CartoDB/carto-python/pull/52/files#diff-62 (0)
A tests/fake.mp3
https://github.com/CartoDB/carto-python/pull/52/files#diff-63 (0)
A tests/secret.py.example
https://github.com/CartoDB/carto-python/pull/52/files#diff-64 (96)
R tests/test.csv
https://github.com/CartoDB/carto-python/pull/52/files#diff-65 (0)
A tests/test_auth.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-66 (27)
A tests/test_datasets.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-67 (96)
A tests/test_file_imports.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-68 (25)
A tests/test_maps.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-69 (87)
A tests/test_sql.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-70 (98)
A tests/test_sync_tables.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-71 (25)
A tests/test_users.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-72 (81)
A tests/test_visualizations.py
https://github.com/CartoDB/carto-python/pull/52/files#diff-73 (32)

Patch Links:

https://github.com/CartoDB/carto-python/pull/52.patch
https://github.com/CartoDB/carto-python/pull/52.diff

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CartoDB/carto-python/pull/52, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB1wxagSbFwe-dfrjiVQp0kDIqe-6Tjks5r4r2CgaJpZM4NXoYX
.

--
-- CARTO CTO

About the docs, I think @jsanz proposed publish them at readthedocs (at the moment they are just API docs, not developer documentation yet)
There's no CI integration. Should we go with our own CI server or is it OK with something like travis?

To publish at readthedocs we don't need any CI service, just configure the webhook on the repo and that's all. I checked and the only concern is that, as you say, the doc folder compiles the API documentation but not the valuable information on the README file in the root. I'll check if there's a way to include it but I wouldn't wait for it for the release.

we use travis when possible

I think we should leave CI out of the equation for now. We're not going to be releasing that often, IMHO.

I'd not release without CI, that's a min requirement for something
"official" (we are leaving a bunch of things but we can live without them )
and it takes a few hours. It's a little effort and helps a lot when getting
3rd party PR
My 2 cents
On Mon, May 15, 2017, 12:53 Dani Carrión<EMAIL_ADDRESS>wrote:

I think we should leave CI out of the equation for now. We're not going to
be releasing that often, IMHO.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CartoDB/carto-python/pull/52#issuecomment-301442017,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB1w01HEPOFlm6VEQVFIhdtz35Y9zNKks5r6C6QgaJpZM4NXoYX
.

--
-- CARTO CTO

FYI, this is the carto api template doc https://docs.google.com/document/d/14tn8SlFsraodRDcMns5CMYIFsSUs8E3X9OrfrVhCwfY/edit

I guess you mean using CI for running the tests, right? If docs are
automatically set up, I don't see any other place where CI can help on this
one.

Thanks for the doc, I will go through it to see what's pending.
About CI, configuring a job is easy, the issue is that there are some end to end tests, that make actual API requests (with an API key).
Should we use our own CI server instead of Travis?
The other option is to mock all the API requests and use the integration of Github and Travis (not sure if this is easy to do...).
Opinions?

I'd disable those tests on Travis if that's the issue (there is env
variables to check if you are running on Travis)
On Mon, May 15, 2017, 13:50 Alberto Romeu<EMAIL_ADDRESS>wrote:

Thanks for the doc, I will go through it to see what's pending.
About CI, configuring a job is easy, the issue is that there are some end
to end tests, that make actual API requests (with an API key).
Should we use our own CI server instead of Travis?
The other option is to mock all the API requests and use the integration
of Github and Travis (not sure if this is easy to do...).
Opinions?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CartoDB/carto-python/pull/52#issuecomment-301452634,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB1wyes-b7F1ups4lQ2WNBjl6Xnk-J6ks5r6Dv0gaJpZM4NXoYX
.

--
-- CARTO CTO

Hey @txomon thanks for reviewing. I'll take into account your comments.

I've taken some time to move forward this PR:

Added developer docs (see doc folder) and updated README.md
Added a job in Travis for CI
Added a couple more of examples
Some other fixes (thanks @txomon for reviewing)

See here the list of done and pending tasks
Comments? @javisantana @danicarrion

:heart_eyes:

🎉 🎉 🎉


Question about LayoutXLM/LMv2 Image Processing

Hi, First of all, Thank you for sharing nice work.
I am wondered the Layoutlmv2, LayoutXLM visual Encoding process.
In your paper (especially the model architecture figures), it seems that the image is sliced as 4 pieces for model input.
Is this only processed in Pre-trained tasks?
In other words, Is this not slicing the input images when fine-tuning or inference steps such as NER??
I'll waiting the reply.
Thank you.

Got it. Thank you!


notion_out! -> command_out!

Change the output macro to generalize for all channels.
The good news is the macro creates a straight-up String, so mostly this is a rename.

Done in<PHONE_NUMBER>747cd336ddab6e948da92058175a68; leaving open until merged to dev.


unable to link against libopenh264-1.1.0-android19.so

trying to compile & link application leads here:
/usr/bin/ld: warning: libstdc++.so, needed by /usr/lib/arm-linux-gnueabihf/libopenh264.so, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libc.so, needed by /usr/lib/arm-linux-gnueabihf/libopenh264.so, not found (try using -rpath or -rpath-link)
/usr/lib/arm-linux-gnueabihf/libopenh264.so: undefined reference to __errno' /usr/lib/arm-linux-gnueabihf/libopenh264.so: undefined reference to __sF'
/usr/lib/arm-linux-gnueabihf/libopenh264.so: undefined reference to `__assert2'
collect2: error: ld returned 1 exit status
Makefile's LFLAGS += -L/usr/local/lib -lpthread -ludev -lfreetype -lz -lconfig -lm -lopenh264

Hi @mailgate , the problem seems related to environmental problem, and seems that it goes well under some other environment? On which linux and which ndk does the problem occur? Thx.

Hi @sijchen!
I'm trying to utilise the lib in odroid-u3 platform (uname: Linux U3 <IP_ADDRESS> #2 SMP PREEMPT Sun Aug 24 09:15:17 PDT 2014 armv7l armv7l armv7l GNU/Linux) environment. Its not an Android...

@mailgate , in your title you mentioned the android lib. So the problem is on linux and not Android, correct?

both libs present in the system:
root@U3:/usr# ldconfig  -p|grep libc.so
libc.so.6 (libc6,hard-float, OS ABI: Linux 2.6.32) => /lib/arm-linux-gnueabihf/libc.so.6
libc.so.6 (libc6, OS ABI: Linux 2.6.32) => /lib/arm-linux-gnueabi/libc.so.6
root@U3:/usr# ldconfig  -p|grep std
libstdc++.so.6 (libc6,hard-float) => /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
libgstdataprotocol-0.10.so.0 (libc6,hard-float) => /usr/lib/arm-linux-gnueabihf/libgstdataprotocol-0.10.so.0
I have added necessary symlinks of directories to make sure they correspond to packages, mentioned above. - result is the same.
It looks like the binary lib was compiled in corss- environment, while I try to link in native... Although I'm not an expert in such issues...

this is more link some system issue where the standard libs cannot be found and does not look like the codec issue

close this because of no update from asker.


Export HTML Bundle Not Working in Packaged Version

Export to a HTML bundle is not working with release produced by CI/CD
Content of presentation.html is just @@content@@

It seems that the presentation file is not written, just the template files are copied (tested with v0.0.1-alpha.13)

It just turned out the issue occurs when images cannot be resolved. If images can be resolved, it works.

We just need better error handling #47


Version 5.0

In this version, we add support for the Swift Package Manager. To make these changes possible, we decided to make the following breaking changes:

Require iOS 11
Remove the possibility to create items in Objective-C

We are planning to release this version on October 25, 2020. During the next month, please reply to this PR with feedback about any bugs or request.
To use the release candidate version, please use the following tag in your package manager: 5.0.0-rc.1

How come is this even tagged as release candidate?
The Swift Package does not even compile! BTW, my project has target iOS 13.0.

How come is this even tagged as release candidate?
The Swift Package does not even compile! BTW, my project has target iOS 13.0.

Thanks for your constructive feedback! As you can see, @ollitapa already fixed it in develop, I’m just gonna wait a couple more days before tagging a second version, in case more things come up.

Thanks for maintaining this repo!

Hey Alex - Thanks for getting SPM working! I'd love to be able to move this dependency off Carthage and onto SPM. Any chance you could tag RC 2 today?

@aaronbrethorst Done!

Thank you!

Has anyone tested this? It does not seem like it works properly (at least not on Xcode 12.1). Package does not compile.
Tested from main branch and version 5.0.0.
error: Multiple commands produce '/MyCode/MyProject-ezhoowqbocgzhycfoojnfdfrulyf/Build/Intermediates.noindex/BLTNBoard.build/Debug-iphoneos/BLTNBoard.build/Objects-normal/arm64/BLTNBoard.swiftmodule':
1) Target 'BLTNBoard' (project 'BLTNBoard') has compile command for Swift source files
2) Target 'BLTNBoard' (project 'BLTNBoard') has compile command for Swift source files

I've been using the package and it works fine for me. I think the error you are seeing is because you have included the SPM module in two or more Xcode style ".framework" modules. This is a "known" limitation in Xcode and to work around it, you need to make an umbrella ".framework" for your common SPM modules and import that in both of your own modules.

@ollitapa It is in fact a framework but all other SPM packages in the framework just work work perfectly.

Hmm, maybe you have some Carthage/CocoaPods leftovers? Some copy-frameworks step? At least my umbrella framework builds fine.


How to generate with frame shift 12.5ms

Hi, I am runing a exp (cyc-noise-nsf-4) with 12.5ms frame shift, 50ms frame length (to match the config of Tacotron).
I only modify input_reso = [200, 200] in config.py, and corresponding args to extract mel and f0
But, the f0 of the synthesized audio looks dijscontinuous.
Can you help me?

Thanks to trying the code.
First, regarding "audio looks dis-continuous", I am sorry that I cannot tell too much from the spectrogram you showed. Could you please provide more information:

What kind of dis-continuity did you perceive, like the voicing error within a sound (i.e., voiced sound -> unvoiced sound)? Or it occurs during the transition from one sound to another?

How frequently does it happen? Only this one or in every generated utterances?

If it is allowed, please do attach a few audio samples here. Or, you can send the audios to me through emails.

With the audios, I probably can better identify the issue and find a solution.
Thanks in advance.

@Chunhui-Lu

Hi, thanks for your reply.
I found that the pitch sequences I extracted are discontinuous
When I extracted pitch sequences using pyworld again, everything was OK
This is a pitch sequence of a song's segment extracted by amfm_decompy.pYAAPT. You can find that it is discontinuous:
219.178085
219.178085
219.178085
216.216217
213.333328
210.526321
207.792206
207.792206
207.792206
207.792206
207.792206
207.792206
205.128204
205.128204
205.128204
205.128204
205.128204
205.128204
207.792206
207.792206
207.792206
207.792206
207.792206
207.792206
207.792206
207.792206
207.792206
210.526321
210.526321
210.526321
213.333328
213.333328

@Chunhui-Lu Thanks for the reply. It is good to know that.
Yes, no F0 extractor is guaranteed to work at all cases.
I am afraid that I cannot help to solve it : )
I remember that I used to use multiple F0 extractor and do voting ...
I don't have more informative suggestion.

Hi, I am runing a exp (cyc-noise-nsf-4) with 12.5ms frame shift, 50ms frame length (to match the config of Tacotron).
I only modify input_reso = [200, 200] in config.py, and corresponding args to extract mel and f0
But, the f0 of the synthesized audio looks dijscontinuous.
Can you help me?

Hi, did you retrain cyc-noise-nsf-4 using frameshift 12.5ms, if yes, would you mind share the trained model ? I try to test tacotron2 + cyc-noise-nsf-4


Pass changedFiles to onStart

Because estrella watches all JavaScript and TypeScript files on the entry points' directories automatically, it would be useful if there was a way to know which specific files changed. Considering they're already on the log, I thought they could also be available to the consumer.
In the same way that onEnd passes the result of the build, onStart could pass which files triggered that build as the second argument. That would allow us to do things like this:
build({
  entry: "src/estrella.js",
  outfile: "dist/estrella.js",
  onStart(config, changedFiles) {
    if (changedFiles.includes("special.js")) {
      console.log("the special file triggered build!")
    }
  },
})

Didn't bump the version in the PR as I saw you were just playing around with generating builds, let me know what you prefer going forward.

No problem, done!

Thank you!

Included in release 1.0.9 https://github.com/rsms/estrella/releases/tag/v1.0.9 (published to npm)


AddressLowering

Fixes and test cases for interesting scenarios involving tuples and reabstraction.

@swift-ci test and merge.

@swift-ci smoke test and merge.

@swift-ci smoke test and merge.


fix: allow widgets to control value to be validated

Fixes https://github.com/netlify/netlify-cms/issues/3436
When using collection/field level media folders the value that is validated includes the media folder.
Couldn't think of a better way to do it at the moment.
This moves us towards widgets controlling their own validation logic (I think this might be good as well as widgets controlling their defaults).
@erquhart thoughts?

My only thought is that I would eventually like to see us get away from using React class component methods this way, instead relying on functions provided directly through the widget registration object.
For now, though, seems expedient to just go with this.

Thanks! I've tested this change (netlify-cms-app v2.11.32, netlify-cms-core 2.22.2) it appears the issue still persists with both the file and image widget. it is still including the media_folder as part of the validation.

Hi @vai0, the fix was merged into the master branch, but hasn't been released yet

Ah, thanks! Is there a way to check what has been officially released?

You can use<EMAIL_ADDRESS>


Android > stacking notifications

Hello,
i want to stack my notification among each other.
In the documentation stand, i have to provide a  notification ID.
Where and how i define the  notification ID  in the payload.
kevin

@appzer it is defined here: https://github.com/phonegap/phonegap-plugin-push/blob/master/docs/PAYLOAD.md#stacking

notId
if found it. I have to read it two times.
Thanks

it works


Optimize visibility calculation for skinned characters

Visibility calculation for characters has a very high cost. It calls MeshInstance.aabb, which transforms bounding boxes of each bone into world space, ads them up, computes final  bounding sphere and uses this for frustum check.
In my test case with 100 characters of 70 bones each, this takes about 8ms on the MacBook Pro and it is about 10% of the frame.
Would could perhaps at init time evaluate the largest possible bounding box / let user specify it, and use this for early / the only culling.
Alternatively, instead of computing total bounding spheres for each bones, which has no early out, we could cull per bone, which would early out for any visible bone. Or test visibility of root bone of characters at least, before computing total bounding volume for bones.

Calculating largest possible AABB based on animation keyframes, will work, but not for case when bones animated manually and gets complex when need to take morphing and animation groups in account.
First figuring out min/max AABB in local space, based on bones radius max(distanceFromParentBone, initialRadius), and then transforming it to world, probably will be much faster than current generic approach?

@Maksims - in the current implementation, when mesh is loaded, we find bounds in bone space for all vertices a bone affects. (and even morphing is applied to those to enlarge those bounds by it per bone). Then each frame, we transform those per bone bounds by bone matrix into world space, and add them up to final bounds. It sounds like this is what you're suggesting or something else?


Update kubeflow-summit-2023.md

This PR fixes a typo in my name as a speaker for Kubeflow Conference Speaker 2023. It's a tiny error and you can see my correct name here https://www.linkedin.com/in/aioswaldo/

Thank you for the fix @papagala! Please can you rebase your PR ?

I created another tiny Pull Request since after rebasing this one, it got a bit chaotic 😄  https://github.com/kubeflow/website/pull/3595

@Arhell I decided to create another PR https://github.com/kubeflow/website/pull/3595


Merge remote-tracking branch 'CenturyLinkCloud/master' into EB-Cleanup-P5

Closing since there are no files changed in this PR.


after update to 0.87 logbook not work

i am having some problem in my logbook , after the update of home assistant to 0.87 many time i want to see the logbook it takes a lot of time and then says no entried found ,
it was working file before the update ,
https://hastebin.com/budutawuwo.sql
how to resolve this issue ?

i am facing one more problem after these errors , many time my automations also dont work, is it related to something ?
can anybody guide me ?

It takes entirely to long to display the results on the logbook or history pages.  The query run very fast on the database, but it seems the browser is just "processing" the results.  I got multiple warnings from Firefox that this page was causing Firefox to run slow and did I want to wait for terminate the script.

The hastebin link doesn't seem to work anymore.
Have you tried creating a new recorder database? I had a similar problem but haven't noticed any issues since creating a new database.
Your automations may not working because they are disabled. While my recorder was broken the automations would often be disabled after a restart.


Better handling of different Linux distros

I still need to test this by building the various packer images.

Ansible is spiffy.  Nice changes.


Add an initial README.md

This PR adds an initial README.md describing the basic setup process and handling of this repository.
See this for a rendered preview.

feel free to remove the other reviewer as this is the initial version


Update Orleans quickstart with AZD template

Summary
Update the Orleans "Deploy & Scale" quickstart to use an AZD template (orleans-url-shortener)
Key motivations

Reduces the complexity of the quickstart. Now, you simply init the template, deploy the in-memory sample as a container, add packages, change code, and then redeploy the container.
Reduces screenshots. Since AZD deploys the application architecture, there's no need to maintain screenshots that quickly age.
Simplifies changes. The AZD template is already dockerized, so the only changes the user needs to make are to import the package and implement new logic for the silo builder.
Shows best practices. The new template doesn't hard-code strings. It uses RBAC and the system-assigned managed identity of the container app. The deploying user is also given RBAC permissions to make local debugging easier.
Showcasing the quickstart. The AZD template can be added to various platforms like https://github.com/azure/awesome-azd and reference back to the quickstart increasing visibility.

Internal previews

📄 File
🔗 Preview link

docs/orleans/quickstarts/deploy-scale-orleans-on-azure.md
CustomerIntent: As a developer, I want to host my Orleans application in Azure so that I can take advantage of the scaling capabilities for the database and application services.

@IEvangelist, you beat me to the changes 😆


Python2 dppricated and all images that you select to install LinuxDiagnostic extension with fail during deployment.

Currently Python2 is long since dead, and can't be installed using the standard yum command.  Because Python2 does not come on RHEL images (particularly any image 8.x and newer), deployment fails if you have linux diagnostics enabled.  These instructions are no  longer viable, and more importantly, a verion of the LinuxDiagnostics extension should be implemented with Python3 support.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 13249027-1524-dd0c-9d83-15a9733a3d19
Version Independent ID: bf8a2d1a-8d9b-228a-6919-16127f315d40
Content: Azure Compute - Linux diagnostic extension 4.0 - Azure Virtual Machines
Content Source: articles/virtual-machines/extensions/diagnostics-linux.md
Service: virtual-machines
Sub-service: extensions
GitHub Login: @GabstaMSFT
Microsoft Alias: gabsta

@akaWrecks
Thanks for your feedback! We will investigate and update as appropriate.

@akaWrecks
Thank you for bringing this to our attention.
I've delegated this to content author, who will review it and offer their insightful opinions.

Currently reviewing this with the Linux Diagnostic team.

We suggest using Linux AMA which now supports the same scenarios as LAD.
https://learn.microsoft.com/en-us/azure/azure-monitor/agents/azure-monitor-agent-send-data-to-event-hubs-and-storage?tabs=windows%2Cwindows-1

Thanks for your contribution to our documentation
We are moving to a new user feedback system. As part of that effort, we are creating a content request in our backlog to address this gap and are closing this GitHub issue. The updated content will be published shortly.

Please continue to provide feedback about the documentation. We appreciate your contributions to our community.
#please-close


Add GitHub notebook

Adding GitHub notebook that I've shown in conference sessions.

@rapoth Since @ifuseandprint approved this PR, should I go ahead and merge it?


Extend setup timeout for new cluster

Release note:

None

Quick fixes https://github.com/istio/istio/issues/799
https://k8s-gubernator.appspot.com/build/istio-prow/pull/istio_istio/789/new-e2e-rbac_no_auth/244/

/retest

@yutongz: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-suite-rbac-auth.sh
17030f3012c0c16e840adff173110df5a53dd06e
link
/test e2e-suite-rbac-auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


fix(reqif): Fix creation of Relations from a Requirement

This is needed to bring our RequirementsBot into working state again.
While fixing the creation of Relations from the reqif.Requirement side, what about the other side? So creating CapellaOutgoingRelations from any model object to a reqif.Requirement can't be done via capellambse right now, or? I can't find a .relation attribute on GenericElement. Also there are 2 ways of creating Relation. Both lead to different places of where the Relation XML element is written to: Either underneath the model object or underneath the Requirement. The GUI accepts both, so I'd root for capellambse creating Relations just underneath the reqif.Requirement to keep the reqif content compact and bundled inside the RequirementsModule. The latter hasn't been done for now, and is the main factor why this PR is a DRAFT.

While fixing the creation of Relations from the reqif.Requirement side, what about the other side? So creating CapellaOutgoingRelations from any model object to a reqif.Requirement can't be done via capellambse right now, or?

Correct, currently there's no API for this. Do we need it? Then we need to figure out how that API should look.

I can't find a .relation attribute on GenericElement.

relation would be a far too generic name anyways, it would at least have to be requirement_relations or something like that to indicate what to expect on the other side.

Also there are 2 ways of creating Relation. Both lead to different places of where the Relation XML element is written to: Either underneath the model object or underneath the Requirement.

That doesn't sound right. Can you give me some example code?

The GUI accepts both

The GUI can sometimes be very forgiving, but that doesn't mean what we do is correct or even makes sense. A better question would be: Is it possible to do the same with (only) the GUI?

To clarify: The difference between these Relations isn't just their position in the XML. They have different xtypes and their source and target differ. CapellaOutgoingRelations underneath a non-Requirement element have a Requirement referenced in their target attribute. The source attribute does always reference its parent model element. For now the modification of CapellaOutgoingRelations can't be done with py-capellambse, and there is no intention to enable this before we have a legitimite use case.
Therefore I change this into a non-Draft PR.


Does this connector support spark 3?

Hi, I ran the connector successfully on spark 2.4.5, but failed on spark 3.0.0. Is there any support for spark 3? Thanks

I met the same issue, any update on this?

Hi everyone,
I try to create DeltaTable and use Apache Atlas:
I have been able to create from a DeltaTable a table in Hive. CREATE EXTERNAL TABLE delta_tbl(date int, delay int, distance int, origin string, destination string) ROW FORMAT SERDE 'org.apache.hadoop.hive.ql.io.parquet.serde.ParquetHiveSerDe' WITH SERDEPROPERTIES("path" = "/tmp/departureDelays.delta'") STORED BY 'io.delta.hive.DeltaStorageHandler' LOCATION 'file:///tmp/departureDelays.delta';
I can do it but I'm using Delta Lake 0.6.1. I would like to use the last version (0.7) but I need Spark 3.0. I clone this project to work in this but it have a strong dependency with "spark-atlas-connector-main_2.11". I don't find this project to work with this.
Where can I find the code for "spark-atlas-connector-main_2.11"?
Thanks in advance!
Best,

Hi everyone,
I try to create DeltaTable and use Apache Atlas:
I have been able to create from a DeltaTable a table in Hive. CREATE EXTERNAL TABLE delta_tbl(date int, delay int, distance int, origin string, destination string) ROW FORMAT SERDE 'org.apache.hadoop.hive.ql.io.parquet.serde.ParquetHiveSerDe' WITH SERDEPROPERTIES("path" = "/tmp/departureDelays.delta'") STORED BY 'io.delta.hive.DeltaStorageHandler' LOCATION 'file:///tmp/departureDelays.delta';
I can do it but I'm using Delta Lake 0.6.1. I would like to use the last version (0.7) but I need Spark 3.0. I clone this project to work in this but it have a strong dependency with "spark-atlas-connector-main_2.11". I don't find this project to work with this.
Where can I find the code for "spark-atlas-connector-main_2.11"?
Thanks in advance!
Best,

Anyone found solution for this?


Add PCCS Dockerfile and update docker-compose.yml to use it

Closing in favor of https://github.com/taikoxyz/raiko/pull/53


PIP-49 - Docs and Branding

Which of the following two language options are we going to use? (Your choice). I just need to know to make sure there is parity between this copy and other external facing copy.
Option A
Filtering Modes
No Filter - Forwards every statement
Template Filter - Forwards only statements matching specified statement templates in an xAPI Profile
Pattern Filter - Forwards only statements matching specified Patterns in an xAPI Profile
Whole Profile Filter - Forwards statements that match any Pattern in an xAPI Profile
Option B
Filtering
LRSPipe is capable of running in a number of modes with respect to which statements get forwarded. Filtering is generally performed based on the components of provided xAPI Profiles. For more information see the xAPI Profile Specification.
Full Forwarding
In this mode all statements from the source LRS will be replicated into the target LRS.
Statement Template Filtering
In this mode LRSPipe is provided with the location of an xAPI Profile and will only forward statements that match the Statement Templates in the Profile.
This can be made to be even more specific by providing a set of Statement Template Ids, which will cause it to only forward a subset of Statement Templates from a Profile. See usage for details and examples.
Pattern Filtering
In this mode LRSPipe is provided with the location of an xAPI Profile and will attempt to match statements to these Patterns, and will validate and forward matching statements.
Much like Statement Template Filtering, this can also be limited to a set of Pattern Ids if one is provided. See usage for details and examples.


Why Google didn't revoked the device yet?

@S-hdyn https://www.widevine.com/news

Thanks for your reply. Already read that. So the answer is, it can be revoked earlier or maybe until 31st May right?

It will be on the 31st May and some people already have the new cdm (new RSA key) and you can see it here in Github issues (Can't verify license request signature; either the platform is wrong or the key has changed!).
In my opinions the repository should be archived on that day too.

Um, okay. I thought this will taken down ASAP, but not yet since November 2020. Ppl will always have the new CDM and some ppl, group, or team always have the decryptor too. But this is one of the most stunning case in internet history. Hehe...

Ppl will always have the new CDM and some ppl, group, or team always have the decryptor too.

Well, starting May 31, people won't be able to use old CDM versions (<4.10.2209.0) anymore, so they won't be able to decrypt L3 anymore.
Until a new guy (like @tomer8007) leak the new L3 RSA private key 💁♂ But we don't know if (and when) it will happen...

Ppl will always have the new CDM and some ppl, group, or team always have the decryptor too.

Well, starting May 31, people won't be able to use old CDM versions (<4.10.2209.0) anymore, so they won't be able to decrypt L3 anymore.
Until a new guy (like @tomer8007) leak the new L3 RSA private key 💁♂ But we don't know if (and when) it will happen...

I think no. There's enough about L3 concept, and I think nobody doesn't wanna join mouse and cat game with google. Except group who usually work in piracy. Thanks for your replies

what will happen to this repo after may 31? Is it really the end?
And also , is there any workaround to "trick" the widevine that you are using a new version even if it's not?

@09kkthxbb What is going to happen with the repo is up to tomer8007, but what I can tell you is that it's the end for you and most of the people here, because it's not easy, for you, to get the new L3 (and even harder L1, device verified by Google) key, the key Widevine uses for requests. If you can find a way to get the new Windows Chrome L3 key you have to change the key private/public key in the following file: https://github.com/tomer8007/widevine-l3-decryptor/blob/ed8a97745c69b8cc0fc7f59cec9474b216b49e16/content_key_decryption.js
There is no workaround because as I already said you need the new L3 key (there are some other stuff that changes too).


[🐛]: Error compiling hello world

Describe the bug
Attempting to compile a "Hello World" style program to see what the codegen would look like.
To Reproduce
Created a file main.cob with the contents
IDENTIFICATION DIVISION.
PROGRAM-ID. IDSAMPLE.
ENVIRONMENT DIVISION.
PROCEDURE DIVISION.
    DISPLAY 'HELLO WORLD'.
    STOP RUN.

Then ran otterkit build main.cob
Expected behavior
Compile succeeded
Actual behavior
Compiler crashed
> otterkit  build .\main.cob
Otterkit parsing error: C:\Users\jaredpar\temp\cobol\main.cob:1:0
Unexpected token: Missing source unit ID name (PROGRAM-ID, FUNCTION-ID, CLASS-ID...), the identification division header is optional but every source unit must still have an ID.

     |
   1 | PROGRAM-ID. IDSAMPLE.
     |        ~

Attempting recovery: Unexpected tokens will be ignored until a separator period or an anchor point is found
(Anchors: OPTIONS, ENVIRONMENT, DATA, PROCEDURE)

Otterkit parsing recovery: C:\Users\jaredpar\temp\cobol\main.cob:1:3
Parser recovered at the following anchor point: (Anchor: ".")

     |
   1 | PROGRAM-ID. IDSAMPLE.
     |           ~

Unhandled exception. System.InvalidOperationException: Stack empty.
   at System.Collections.Generic.Stack`1.ThrowForEmptyStack()
   at System.Collections.Generic.Stack`1.Peek()
   at Otterkit.Analyzer.<Analyze>g__IDENTIFICATION|7_1() in /Users/ktlsf/Documents/GitHub/otterkit/src/OtterkitAnalyzer.cs:line 198
   at Otterkit.Analyzer.<Analyze>g__Source|7_0() in /Users/ktlsf/Documents/GitHub/otterkit/src/OtterkitAnalyzer.cs:line 116
   at Otterkit.Analyzer.Analyze(List`1 tokenList, String fileName) in /Users/ktlsf/Documents/GitHub/otterkit/src/OtterkitAnalyzer.cs:line 101
   at Otterkit.OtterkitCompiler.CommandLineArguments(String[] args) in /Users/ktlsf/Documents/GitHub/otterkit/src/OtterkitCompiler.cs:line 153
   at Otterkit.OtterkitCompiler.Main(String[] args) in /Users/ktlsf/Documents/GitHub/otterkit/src/OtterkitCompiler.cs:line 39

Platform Information (please complete the following information):

OS: Windows
OS Version 11
CPU Architecture x64
Otterkit version: 1.0.15-alpha

Additional context
I have effectively zero experience with COBOL. This could very well a simple PEBKAC problem.
Mostly just curious about what the code gen strategy was and wanted to take a look at it.

Hey @jaredpar, it seems that the codegen is currently broken. I found what the issue is and I'm going to make the commit to fix it and an update to Nuget so that you can check our codegen structure. This should take around 30 minutes.
The last error was the broken codegen, but the first two are actually because the test code is in free format and the compiler defaults to fixed format. To fix the parsing errors you need to specify the --free compiler option.

@jaredpar, The latest commit 830458c should fix this issue for now, but this needs more work later to generate more parts of the language. Right now the codegen is a little limited, but the overall structure will remain the same.
Could you try doing the following steps to check if the codegen is working for you?
Install the project templates and update the compiler:
dotnet new install Otterkit.Templates::1.0.1-alpha

dotnet tool update --global Otterkit --version 1.0.30-alpha

Create a new project and run the build command:
otterkit new app

otterkit build main.cob --free

If it works, this should create a .otterkit folder which contains the built binary inside the "Build" folder and the C# project files inside the "OtterkitExport" folder.

Hey @jaredpar, it seems that the codegen is currently broken. I found what the issue is and I'm going to make the commit to fix it and an update to Nuget so that you can check our codegen structure. This should take around 30 minutes.

For future reference, could you please state what the problem was?

@TriAttack238 The codegen was checking the current scope by searching for the identification, data and procedure keywords, this did work previously but was not ideal.
We later added a scope check to the token classifier but didn't update the codegen to use the new "TokenScope" values from each token. This broke the codegen and would cause it to loop until it hit the end of the token list and throw an exception by trying to access the next token (after the EOF token).
Changing the codegen to use the TokenScope values instead of the keywords fixed the issue.

I have the same problem. Maybe a link with the encoding ?

Here are the error messages. (and I'm on mac ;-)).

@VenierSophie How does the source code look like?

Also, I would recommend to try the Nuget version for the hello world. The newest code in the main branch might not be working completely right now, but I'll work on a fix for it.

@VenierSophie I found the cause of the issue, I'll commit fixes to it soon.

Fixed, the latest code on the main branch should work with the hello world example in this issue.

Great, thank you !

I guess this can be closed now ... and for the following:

[...] the first two are actually because the test code is in free format and the compiler defaults to fixed format. To fix the parsing errors you need to specify the --free compiler option.

You may want to follow GnuCOBOL's latest features here, below others, which are not relevant for  a COBOL2023 only compiler it has three format states: free and fixed (specified on the command line) and auto depending on the first lines (just checking "Is there an expected indicator in col7 - is there "data" before?") - but that likely should be moved out a a separate issue, when closing this one.

Yes this issue can be closed now.

and auto depending on the first lines

Hey @GitMensch thanks for the suggestion, I haven't thought about that before. I'll work on implementing this as a default option when no explicit format is passed on the command line. This should also help improve the developer experience.
Also, since you're here I wanted to ask for your feedback on the new error message format we introduced with this PR: https://github.com/otterkit/otterkit/pull/17. This was inspired by Rust's error messages and related libraries.

Hey @GitMensch, I wanted to let you know that I just implemented the auto source format detection as the default if the user didn't specify one. It seems to be working.


[PE-D][Tester C] Unicode characters are not allowed in email

Input:
edit 1<EMAIL_ADDRESS>Reasoning:
Unicode characters are allowed in the local part of the email. As such<EMAIL_ADDRESS>is a valid email. As mentioned in issue #224, the NGO might have international partners, and as such international email addresses that may contain special characters found in European languages for example should be allowed.

Expected Behaviour:
edit 1<EMAIL_ADDRESS>is a valid command.
Actual Behaviour:

Labels: type.FunctionalityBug severity.Low
original: Siddardar/ped#13

It seems that<EMAIL_ADDRESS>is not a valid english email. Maybe we can add that only english emails are supported?

I do think that this could fall under response.NotInScope so Im not sure if we want to prioritise this change too


Support UNIX domain sockets in dart:io

https://b.corp.google.com/issues/143959178.

Worth linking: https://github.com/dart-lang/sdk/issues/21403
Oddly enough, I just found this issue while googling to see if Dart support Unix domain sockets yet...

Closed as dup of dart-lang/sdk#21403


Unable to configure protocol

Is your feature request related to a problem? Please describe.
All output is forced to be insecure HTTP protocol rather than configurable as HTTP/HTTPS
Describe the solution you'd like
I'm unfamiliar with GO - but it appears that the protocol is partially configurable at design time - but not once compiled.
https://github.com/xteve-project/xTeVe/blob/71dfe912722f3aa7cf10a3764bcd86867ee32fa4/src/config.go#L44
Describe alternatives you've considered
I've looked at the configuration files - but none appear to support the definition of the protocol
Additional context
When serving xTeVe content from a secure proxy, PLEX will not follow HTTP -> HTTPS redirects.

There was once the consideration to implement TLS. Since only a few clients still accept self-signed certificates, one would also have to implement Letsencrypt into xTeVe to enable TSL without pain.
Sorry, too much effort for me.

It's already implemented with Caddy.
I'm using TLS now with no effort - I just need a way to remove the hard coded http.


Minor Readme Update for AWS + Chamber Setup

Description
This PR makes 3 tweaks to the documentation for setting up this repo:
Quick Set Up Section: Added make build_tools to in the list of commands in the Quick Setup Section since it was missing from the list and mentioned along with the other commands in order to get set up.
Direnv Section: Added a link to the Set Up AWS section within the Direnv section since AWS has to be set up in order to use Chamber
Set Up AWS (Optional) Section: Added an updated link for instructions to finish setting up AWS. The previous link went to a 404 page

Warnings

:warning:
Please add the JIRA issue key to the PR title (e.g. MB-123)

  Generated by :no_entry_sign: dangerJS against 98e8666cd7f284becdc0d48719d5b38c2317451d


The component does not react to LOCALE prop & I can't change the GLOBAL LOCALE

Expected behavior
datepicker should act according to:

locale prop
global locale

Actual behavior

datepicker does not consider the locale prop i pass to it.
i can not change the global local in any way i try!

Steps to reprodcue
you can see in the code all the options I've tried.
obviously i tried them separetly and didn't run the component as-is.
import React from 'react';
import moment from 'moment';
import DatePicker from 'react-datepicker';
import 'react-datepicker/dist/react-datepicker.css';

console.log(moment.locale());  // en

import fa from 'moment/locale/fa';
console.log(moment.locale()); // 'en'
moment().locale('fa', fa);
console.log(moment.locale()); // 'en'
moment.updateLocale('fa', fa);
console.log(moment.locale());  // 'en'

//tried this also in a different run:
import 'moment/locale/fa';
console.log(moment.locale());   // 'en
moment().locale('fa');
console.log(moment.locale());   // 'en
moment.updateLocale('fa');
console.log(moment.locale());   // 'en

export default class Calendar extends React.Component {
  constructor(props) {
    super(props);
    this.state = {
      startDate: moment()
    };
    this.handleChange = this.handleChange.bind(this);
  }

  handleChange(date) {
    this.setState({
      startDate: date
    });
  }

  render() {

    return (
      <DatePicker
        dateFormat={'DD/MM/YYYY'}
        selected={this.state.startDate}
        onChange={this.handleChange}
        locale="fa"` // tried also NOT passing this prop in hopping that the locale will be determine from moment.locale()... also didn't work
      />
    );
  }
}

Every option i tried does not change the current locale from 'en'.
what am I missing here?
thank you very much!

Got It!
the mistake was in the way i import the locales from moment.
instead of :
import 'moment/locale/fa';
it should be :
import 'moment/src/locale/fa';


Improved: Converted CustomTimePeriod related services from simple to entity-auto

(OFBIZ-11689)
Thanks Pierre for reporting.

Loaded on trunk thanks


Add interpolateZoom.rho. Fixes #25.

I think we're done. We can remove the getter if you're not happy with it.

This should not be a getter because it’s not mutating the interpolator—it’s returning a new interpolator. The precedent here is other interpolation and easing parameters, such as:
https://github.com/d3/d3-interpolate#interpolate_gamma
https://github.com/d3/d3-ease#back_overshoot
https://github.com/d3/d3-ease#elastic_period
https://github.com/d3/d3-ease#elastic_amplitude

(For context, see also https://github.com/d3/d3-ease/issues/13.)


<IP_ADDRESS> isn't accepted as IP address any more

It results in the following error:
Error 1000 Ray ID: 61686a768d28017a • 2021-01-24 08:34:32 UTC
DNS points to prohibited IP
What happened?

You've requested a page on a website (...) that is on the Cloudflare network. Unfortunately, it is resolving to an IP address that is creating a conflict within Cloudflare's system.
What can I do?

If you are the owner of this website:
you should login to Cloudflare and change the DNS A records for ... to resolve to a different IP address.

Cloudflare Ray ID: 61686a768d28017a • Your IP: <IP_ADDRESS> • Performance & security by Cloudflare

It looks like other addresses work, but not all other addresses. I don't know what would be a good one to recommend as default.

User error: this was caused by an incorrect route.
So the Worker didn't trigger and the browser tried to reach a nonexistent site.

User error: this was caused by an incorrect route.
So the Worker didn't trigger and the browser tried to reach a nonexistent site.


Roll Engine from d5cadd28b0bf to e21cd4f1cbfa (3 revisions)

https://github.com/flutter/engine/compare/d5cadd28b0bf...e21cd4f1cbfa
2021-11-11<EMAIL_ADDRESS>Roll Skia from 6fae0523629f to 9613060bdff0 (1 revision) (flutter/engine#29664)
2021-11-11<EMAIL_ADDRESS>Roll Skia from a583a0fdcc15 to 6fae0523629f (2 revisions) (flutter/engine#29661)
2021-11-11<EMAIL_ADDRESS>Roll Dart SDK from 38e7078fa2b7 to e1a475a40934 (19 revisions) (flutter/engine#29659)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


VRT (Visual Regression Testing)

A test method that saves components as images and compares them with the saved images at test time to verify that the components have not changed in appearance.
It's no different from taking a screenshot and checking it.
Candidates

Storyshots (storybook)
jest-image-snapshot + puppeteer
playwright @playwright/test

Links:
https://kaminashi-developer.hatenablog.jp/entry/expo-storyshots
https://www.wantedly.com/companies/wantedly/post_articles/421107
https://blog.recruit.co.jp/rmp/front-end/visual-regression-testing/
https://zenn.dev/sterashima78/articles/47c9a109988b3c
https://playwright.dev/docs/intro

Solved in #56


IE8 mediaPlayer.play() throws "Object does not support this property or method"

Test case:
http://tipmedia.com/demos/test/media-player/test-case.html
In IE8 the browser will throw a "Object does not support this property or method" error any time you attempt to play the video via javascript (the video's native controls work just fine).  The error is down on like 3134 of mediaelement-and-player.js in the .load() function (which is called from .play()) and on the test page it is called immediately on load to trigger an auto-play-like behavior.
Also, it is impossible to attach an event listener to the media element player right after it is created as well (the addEventListener function is undefined) so I can't even create it and then wait for the "canplay" event!
Attempting to use setTimeout results in strange behavior (wait 5 seconds, call play() video advances 1 frame and remains paused).

@Draco18s Is this still an issue?

Oh jesus christ, this is old. I have no idea. I don't even work for that company any more, much less whatever project it was that we needed it for.
(The example page is still up though)

@Draco18s thanks for your response; I'll test that URL and if I can't find the error using the latest package I'll close this issue

Sure thing! Hope it has been fixed already. :)

@Draco18s I tested http://mediaelementjs.com/ on IE8 and I didn't find that error, so it has been fixed. I'll close this ticket.


fix(versions): update Activiti/activiti-dependencies versions into develop

UpdateBot pushed maven dependency: org.activiti:activiti-core-dependencies to: 7.1.106

UpdateBot commands:
updatebot push-version --kind maven org.activiti:activiti-core-dependencies 7.1.106 --merge false