feat(protocol-designer): Disable step creation button when in batch edit

Overview
closes #7294 by disabling the StepCreationButton once a user enters batch edit. It also sneaks in a helpful tooltip when the button is disabled to explain why (copy cleared with Morgan)
Changelog

feat(protocol-designer): Disable step creation button when in batch edit

Review requests
Make/import a protocol and go to design tab

[ ] [Add Step] button is enabled in single select/edit mode
[ ] No tooltip for enabled top level button

Enter batch edit by selecting multiple steps

[ ] [Add Step] button is now disabled
[ ] [Add Step] button has tooltip explaining "New steps cannot be added in Batch Edit mode."

Exit batch edit

[ ] [Add Step] button is now enabled, functioning, and no tooltip for top level (unexpanded) button

Risk assessment
Low, PD only, small refactor

Seems to work fine! Two things:
(1) Can we add tests for this?
(2) I noticed there is a period at the end of the tooltip. We don't normally do that do we?

Sure we can add some tests.
I think we add a period when its a full sentence. The other tooltips on the step creation buttons have a .


Update python version 1.5.0

Docs Build status updates of commit 5b17a8a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

prosepy/docs-ref-conceptual/knownissues.md
:white_check_mark:Succeeded

prosepy/docs-ref-conceptual/relnotes.md
:white_check_mark:Succeeded

xrefmap.yml
:white_check_mark:Succeeded

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


Seems like optimizer.step() has been overridden after learning rate scheduler initialization

Hi,
I'm using your run_lm_finetuning.py script. It works but I would like to know why in the starting of the training, I get:

3 times the following sentence: Gradient overflow.  Skipping step, loss scaler 0 reducing loss scale to ...
and the following warning:

/opt/anaconda3/envs/gpt/lib/python3.7/site-packages/torch/optim/lr_scheduler.py:91:
UserWarning: Seems like `optimizer.step()` has been overridden after learning rate scheduler
initialization. Please, make sure to call `optimizer.step()` before `lr_scheduler.step()`.
See more details at https://pytorch.org/docs/stable/optim.html#how-to-adjust-learning-rate
  "https://pytorch.org/docs/stable/optim.html#how-to-adjust-learning-rate", UserWarning)

It is strange as we can see that optimizer.step() is well called before scheduler.step() from line 359.
Any thought about that?

I also got similar warnings, it's ok.
https://github.com/NVIDIA/apex/issues/318#issuecomment-493797866
https://discuss.pytorch.org/t/cyclic-learning-rate-how-to-use/53796/2

Thanks for the links.
I made the following changes in your run_lm_finetuning.py and the warning is gone now:

I deleted the line 360 (scheduler.step())
I added the following code in the line 297 after the code model, optimizer = amp.initialize(model, optimizer, opt_level=args.fp16_opt_level):

if amp._amp_state.loss_scalers[0]._unskipped != 0: # assuming you are using a single optimizer
     scheduler.step()

You shouldn't delete the line with scheduler.step() inside the learning loop if you use LR scheduling.

Ok but if I remplace only  scheduler.step() by the following code, I'm still getting the WARNING.
if amp._amp_state.loss_scalers[0]._unskipped != 0: # assuming you are using a single optimizer
     scheduler.step()

How to implement the following comment?
To avoid this warning, initialize the scheduler after running amp.initialize(model, optimizer, opt_level).

I'd appreciate to let me know if you find out the proper to get rid of the warning.

I'd appreciate to let me know if you find out the proper to get rid of the warning.

In fact, when I see a warning, I try to find the reason.
Maybe I could forget this warning (ie, your code works well) but I guess you agree with me that there is a reason behind this warning.
Note: I am asking you many questions because I am training GPT-2 in a language other than English and Russian (Portuguese). By the way, I have questions ;-) about the training process.


Fix for Issue #433

Proposed changes
Added NGSI-LD temporal property 'modifiedAt'  and 'observedAt'
Fix for Issue
Types of changes
What types of changes does your code introduce to the project: Put
an x in the boxes that apply

[ x ] Bugfix (non-breaking change which fixes an issue)
[ x ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)

Checklist
Put an x in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to
ask. We're here to help! This is simply a reminder of what we are going
to look for before merging your code.

[ x ] I have read the CONTRIBUTING doc
[ x ] I have signed the CLA
[ ] I have added tests that prove my fix is effective or that my
feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in
downstream modules

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

@daminichopra i am not sure it's the right direction...
I will show you how to proceed over your branch, in the hope this is of help for future PRs:

Let's define the test cases and develop them. In this case @jason-fox was very kind and basically gave us the example to follow: https://github.com/orchestracities/ngsi-timeseries-api/issues/433#issuecomment-830071970. So let's develop the test case that based on the examples by json check that the time_index in the timeseries returned is the correct one.

-> I will make a first pr adding these test cases

let's modify time_index_priority_list in timex.py to set as timeindex the selected attributes.

-> I will make a second pr with the changes required

if all goes well after this PR test cases define in 1 will pass.

@daminichopra i am not sure it's the right direction...
I will show you how to proceed over your branch, in the hope this is of help for future PRs:

Let's define the test cases and develop them. In this case @jason-fox was very kind and basically gave us the example to follow: Include NGSI-LD observed/modified props in time index calcs #433 (comment). So let's develop the test case that based on the examples by json check that the time_index in the timeseries returned is the correct one.

-> I will make a first pr adding these test cases

let's modify time_index_priority_list in timex.py to set as timeindex the selected attributes.

-> I will make a second pr with the changes required

if all goes well after this PR test cases define in 1 will pass.

@daminichopra let me know if you understand what I did and if we can agree to this approach for your future PRs

@daminichopra i am not sure it's the right direction...
I will show you how to proceed over your branch, in the hope this is of help for future PRs:

Let's define the test cases and develop them. In this case @jason-fox was very kind and basically gave us the example to follow: Include NGSI-LD observed/modified props in time index calcs #433 (comment). So let's develop the test case that based on the examples by json check that the time_index in the timeseries returned is the correct one.

-> I will make a first pr adding these test cases

let's modify time_index_priority_list in timex.py to set as timeindex the selected attributes.

-> I will make a second pr with the changes required

if all goes well after this PR test cases define in 1 will pass.

@daminichopra let me know if you understand what I did and if we can agree to this approach for your future PRs

@chicco785 , yes i got it. I will keep this approach in mind. Thanks for this.

@jason-fox i think this is ready for landing, do you mind having a look and check if you requirements have been implemented correctly? (in which case you can approve the pr). if you think some other ngsi-ld experts are better to be involved, let me know!


Fix: allow setting null for one-to-one navigation properties

This PR aims to fix the errors below so one can set null value to one-to-one navigation properies.
TestEntity.builder().toSingleLink(null); //compilation error
TestEntity.builder().fromJson({ toSingleLink: null }); //compilation error
TestEntity.builder().fromJson({ toSingleLink: null } as any); //runtime error

[x] update changelog with compatibility notes

closes: #1102

@marikaner , I updated the complex info in the FromJsonType type and added tests for undefined.


Implement basic StationWare gamemode

Description

The basics:

everyone spawns on the bus
latejoins are disallowed
ware events happen every minute as normal
game continues until one person is left
when one person is left, end the game and report who it was and how long the round lasted.

Closing in favor of challenge-style warioware


Set steps to show integers instead of float

What option can we use to not show 0.0 numbers? I only want whole numbers

Closing - not relevant to wrapper. Please consult the Chart.js documentation for details on how to add custom formatting.


0.9.x backport readme

Backport of #1086 to 0.9.x

I don't think there's any need to backport the README changes since most users are only going to read it when they visit the master branch on GitHub, but since you've already done the work... :)

On second thought, I think this backport is unnecessary. Closing.

It was simple cherry-pick anyway, np. :+1:


[v1.18.0] kubectl's version cannot be retrieved WITHOUT a kube config or additional params

It should be possible to check the kubectl version WITHOUT having a valid or any kubeconfig file.
However, now it just throws an error and does NOT display the version in use (v1.18):
 # kubectl version
W0404 15:19:07.071657   17635 loader.go:223] Config not found: /root/.kube/config
error: Missing or incomplete configuration info.  Please point to an existing, complete config file:

  1. Via the command-line flag --kubeconfig
  2. Via the KUBECONFIG environment variable
  3. In your home directory as ~/.kube/config

To view or setup config directly use the 'config' command.

if you use --client=true it will work:
kubectl version --client=true

Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.0", GitCommit:"9e991415386e4cf155a24b1da15becaa390438d8", GitTreeState:"clean", BuildDate:"2020-03-25T14:58:59Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/amd64"}

I agree that it would be nice to print the client version though even if there is no config file.

when you just use version without any options it should fetch client and server version and fetching server version without kubeconfig file would not be possible, so i think this is expected behaviour
-srini

I think a local tool should be able to print its version without any external dependencies or extra parameters. If it does not have a kubeconfig, it should print the client version and throw the same error after that. If you specify --client=true, it should still print just the client version - the same goes for --server=true.

It actually should not act like this... My PR will fix this:https://github.com/kubernetes/kubernetes/pull/89913

even after https://github.com/kubernetes/kubernetes/pull/89913, this is still not working as it did in 1.17

will be fixed in 1.18 by https://github.com/kubernetes/kubernetes/pull/90244
/assign @soltysh

/kind bug

/sig cli
/area kubectl

Seems to be fixed now.

/close

you can run this command :   export KUBERNETES_MASTER=http://<IP_ADDRESS>:8080    on master role


How to run Asp.net core RTM on mono with Arm based Linux

Now Asp.net core rtm doesn't work on mono.
There's workaround which I tested.

MVC dynamic compilation does not work on mono. Now I used Publish option using right click over project item in solution explorer, Visual Studio.
Copy 1st step's publish files to linux machine.
System.Runtime.InteropServices.RuntimeInformation.dll is only for windows machine, if I compiled it on windows machine. So I have to replace the file to packages\System.Runtime.InteropServices.RuntimeInformation.4.0.0\runtimes\unix\lib\netstandard1.1\System.Runtime.InteropServices.RuntimeInformation.dll.
System.Native is required. Kestrel server only use one function, GetUnixName.
@Tragetaschen made libSystem.Native project. https://github.com/aspnet/Home/issues/1610
Below is compile and installation script.

git clone https://github.com/Tragetaschen/libSystem.Native
cd libSystem.Native/src
cc -c -o libSystem.Native.o GetUnixName.c -fpic
cc -shared libSystem.Native.o -o libSystem.Native.so
/usr/bin/install -c -m 644 libSystem.Native.so /usr/local/lib
echo "/usr/local/lib" | tee /etc/ld.so.conf.d/local.conf
sudo ldconfig -v

Run with mono

mono TestWeb.exe

When will Asp.net core support arm platform or mono?

ASP.NET Core support for Mono isn't planned; we don't do anything to specifically block it, but we also don't test on it. If you have some safe changes that would enable ASP.NET Core / MVC to run on Mono, we can certainly work with you to get those changes made.

After reviewing the source code, I found how to run Asp.net core RTM on linux completely.
Microsoft.Extensions.DependencyModel searches Reference Assemblies inside xbuild-frameworks/.NETFramework/v{.NET Version}.
For working MVC dynamic compilation, use this script.
cd /usr/lib/mono
mkdir xbuild-frameworks
cd xbuild-frameworks
mkdir .NETFramework
cd .NETFramework
ln -s ../../4.5 v4.5.2

We are closing this issue because no further action is planned for this issue. If you still have any issues or questions, please log a new issue with any additional details that you have.


Docs: Fix link to snakeviz

Looks like a copy and paste error that got the wrong url in there.
[skip ci]

Thanks for finding and fixing this @hamogu !  Merging.


favicon for rancher

Can we update the favicon to back to rancher? Also, should it be called "Rancher" instead of "Dashboard"?
Dashboard favicon:

Old UI favicon

I'd rather it be called and icon-ed something at least somewhat different to tell tabs apart.
Also all Ranchers have Dashboard but not all Dashboards have Rancher.  After login the window title could potentially change depending on whether Rancher is there or not...

Current dashboard tab.


[BUG] - Blueprint Tweaks and wind towers

When placing a blueprint with wind towers over water, it requires placed foundation, where as without a blueprint, you can just put them on water now and they don't use foundation from inventory

I’m not sure this issue is a bug from Blueprint Tweaks. I would recommend to report the bug to game developers.


Client sending 'stop' message which is causing exceptions in Coniql (Strawberry version)

I've opened this issue to log the problem I have just found but I note that it will solved simply by updating to the new graphql websocket protocol is cs-web-lib.
We recently made a change discussed in issue #11 (PR #12) to stop duplicate subscriptions being sent to Coniql when the client browser reconnects to the server. This occurred in the case where we load our webpage, bring Coniql down and then start again. The change we made means that if we have not received acknowledgment of the connection then we throw an error: https://github.com/dls-controls/cs-web-lib/blob/3453939456917a6e2a1fbafed9042dc9045ebfa6/src/connection/coniql.ts#L310. Underneath the hood, the apollographql client sends a 'stop' message to the server if there is an error (see apollographql issue 9109.
I have been testing the machine status application (which uses cs-web-lib) with the new Coniql version using the Strawberry graphql api. I found that the Strawberry code starts throwing exceptions constantly when running against the latest version of cs-web-lib (with the above fix). Note that this does not happen when running against the original cs-web-proto.
What is happening is that the first thing being received by Coniql when it starts up again is the 'stop' message from the client. When Strawberry receives a 'stop' message it tries to close the subscription, indexing a dictionary with the ID. However, in this case we never started a subscription and so we get a key error. The client is still waiting for the acknowledgment and has not received it as Coniql is throwing errors, hence it keeps throwing errors, which keeps sending 'stop' messages, which continues to cause error in Coniql (and so we go on forever)...
As noted above, this issue does not appear when running against cs-web-proto or the version of cs-web-proto using the new graphql-transport-ws protocol hence I have pinned the issue down to our current subscription method in cs-web-lib.
To fix this in cs-web-lib I would change line 310 to log a warning instead of throwing an error causing the 'stop' message to be sent:
console.warn("Acknowledgment not received from server.");

This needs to be done when we switch to the new version of Coniql, although at this point the strategy may be to move cs-web-lib to the new graphql websocket protocol immediately.

Can you paste an example exception seen in the Coniql logs?

Example of exception seen:
Error handling request
Traceback (most recent call last):
  File "/home/cnuser/.local/share/virtualenvs/coniql-W5jWBl11/lib/python3.8/site-packages/aiohttp/web_protocol.py", line 433, in _handle_request
    resp = await request_handler(request)
  File "/home/cnuser/.local/share/virtualenvs/coniql-W5jWBl11/lib/python3.8/site-packages/aiohttp/web_app.py", line 504, in _handle
    resp = await handler(request)
  File "/home/cnuser/.local/share/virtualenvs/coniql-W5jWBl11/lib/python3.8/site-packages/strawberry/aiohttp/views.py", line 65, in __call__
    return await self.graphql_ws_handler_class(
  File "/home/cnuser/.local/share/virtualenvs/coniql-W5jWBl11/lib/python3.8/site-packages/strawberry/subscriptions/protocols/graphql_ws/handlers.py", line 70, in handle
    return await self.handle_request()
  File "/home/cnuser/.local/share/virtualenvs/coniql-W5jWBl11/lib/python3.8/site-packages/strawberry/aiohttp/handlers/graphql_ws_handler.py", line 48, in handle_request
    await self.handle_message(message)
  File "/home/cnuser/.local/share/virtualenvs/coniql-W5jWBl11/lib/python3.8/site-packages/strawberry/subscriptions/protocols/graphql_ws/handlers.py", line 85, in handle_message
    await self.handle_stop(message)
  File "/home/cnuser/.local/share/virtualenvs/coniql-W5jWBl11/lib/python3.8/site-packages/strawberry/subscriptions/protocols/graphql_ws/handlers.py", line 150, in handle_stop
    await self.cleanup_operation(operation_id)
  File "/home/cnuser/.local/share/virtualenvs/coniql-W5jWBl11/lib/python3.8/site-packages/strawberry/subscriptions/protocols/graphql_ws/handlers.py", line 192, in cleanup_operation
    await self.subscriptions[operation_id].aclose()
KeyError: '2'

In fact this throw new Error("Acknowledgement not received from server.");  is actually causing lots of errors to be thrown by the client when disconnected which I think is unnecessary. This should be changed to a log.warn to save an influx of errors when refreshing or cycling through pages.
I also see the following error thrown in the client relating to the disconnect/reconnection:
Error: Failed to unsubscribe from pv ...
Error: TypeError: this.subscriptions[pvName] is undefined

We need to fix this.

Fixed in above PR.


How to correlate trace telemetry like parent child relation ship

Hi,
If I use start operation an request.telemetry first, then whenever I log any trace telemetry, it will show up under that request telemetry
Ex:
The trace will have operation Id which is same as request operation id
start request telemetry
log trace telemetry .... etc
stop request telemetry

But if I log trace telemetry in parent then children function
log trace telemetry in parent
log trace telemetry in child1
log trace telemetry in child2

The trace I see in app insight won't have operation Id
My question is that how do I let those trace under same parent have same operation Id, so I can easily correlate/summarize the trace
Ex:
When I see the parent trace telemetry, I want to use operation Id to correlate related child trace telemetry under it.

TraceTelemetry is not an operation (with an start and end); its just a point-in-time log entry. And hence the TraceTelemetry itself cannot have the notion of children.
Only Operations (Request,DependencyTelemetry) can have children.

So the trace telemetry won't have operation id
Only if they are under Operations(request/dependency)
Is it correct understanding?

Yes.
Also check the docs on this : https://learn.microsoft.com/en-us/azure/azure-monitor/app/distributed-tracing-telemetry-correlation


[Refactor] Refactor FragmentNormalizer to support Fragment contains JoinNode

What type of PR is this：

[ ] BugFix
[ ] Feature
[ ] Enhancement
[x] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

FragmentNormalizer.normalize method can normalize a Fragment contains JoinNode at present.
Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto backported to target branch

[ ] 2.5
[ ] 2.4
[ ] 2.3
[ ] 2.2

[FE PR Coverage Check]
:disappointed: fail : 67 / 107 (62.62%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/planner/JoinNode.java
0
2
00.00%
[312, 446]

:large_blue_circle:
com/starrocks/analysis/JoinOperator.java
0
1
00.00%
[133]

:large_blue_circle:
com/starrocks/planner/FragmentNormalizer.java
67
104
64.42%
[234, 490, 494, 496, 498, 500, 502, 506, 511, 512, 515, 516, 518, 519, 522, 523, 524, 525, 526, 528, 545, 554, 563, 564, 566, 567, 570, 571, 578, 594, 595, 596, 597, 598, 599, 600, 601]

run starrocks_admit_test


Bump version to 0.2.46

New release required for https://github.com/rust-lang/rust/pull/57121

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

@bors: r+

:pushpin: Commit 11d1a181d2f0c033bf32c571ee273961daa0d02f has been approved by alexcrichton

:hourglass: Testing commit 11d1a181d2f0c033bf32c571ee273961daa0d02f with merge 39ae9b9e22b61b0ba571f7f464c3f76015fe50fa...

@bors: retry

:hourglass: Testing commit 11d1a181d2f0c033bf32c571ee273961daa0d02f with merge ba17deb87a6aaea59c3ecd0da998d25dbefced65...

:broken_heart: Test failed - status-travis

@bors: retry

:hourglass: Testing commit 11d1a181d2f0c033bf32c571ee273961daa0d02f with merge a9e3cc6c1b529eaffef5b82934d0c47203edebe5...

@alexcrichton Looks like we're still missing a tag. Not sure whether I can add the tag through a PR.

Just a lock file update in the rustc repo and then it should be good to go!


Issue: MinificationMinify files along with versioning

As far as my understanding is concerned, deploy.sh is used to deploy the code to the website. minify.sh is being called in deploy.sh, so why does uglifyjs installation need to be there in the readme? Need user install it?

Few things where I am stuck:

You mentioned mangling somewhere in comments. What exactly am I supposed to do in that?
How to commit package.json :p
I am still unable to figure out changes to be done in profile.js because of which the parse error is coming. I modified the other file though.

ALSO!

If you will check get_static_url , you'll see that I made changes to return minified file if the environment is production. But there are files which are already minified and the uncompressed version DNE. Should I add an exception for them or unminify them and replace them so that the logic remains same throughout?

This (https://www.npmjs.com/package/uglify-js) has a mangle option. What your uglifyjs does right now is just removes extra spaces to compress the files. We also need to change the variable names to shorter versions to reduce the size of the file further.
It's okay if you don't commit package.json for this. package.json is used in npm installations. We will only have one time global installation.
Change

years = Array.from(years).map((el)=> parseInt(el));

to
years = Array.from(years).map(function(el) { return parseInt(el); });

You are right, there would be a few such occurrences. Let's keep it simple - don't call get_static_url on them and remove from the list of files that we use. We don't really need versioning on them as of now.


docs: fix dead link

Signed-off-by: tianqian.zyf<EMAIL_ADDRESS>Description: fix dead link
Risk Level: low
Testing: N/A
Docs Changes: y
Release Notes: N/A

Sorry, can you do a master merge to pick up #4701?


Character limit increase?

Is there any way to increase the character limit? Splitting out a script in multiple cells is a bit clunky and can get pretty slow.
Also, I'm having trouble with variable references in for loops that span multiple cells. For example, in cell A1, I establish a for loop and a dynamic variable under the loop that changes with each iteration. The logic is long, so I exceed the single-cell character limit before finishing. I continue in A2, with proper indentations, and refer to the dynamic variable. I get a syntax error, where references to that same variable in A1 do not have an error.

I have a solution, where the actual Python program is on a worksheet in one of more columns.
The columns are run from left to right.
This requires a small runner program in a Py() cell:
df_runner = xl("B:C")

for column in range(len(df_runner.columns)):
    as_list = df_runner.iloc[0:, column].to_list()
    while as_list and as_list[-1] is None:
        as_list.pop()

    source = "\n".join("" if line is None else str(line) for line in as_list)
    exec(source, globals())

globals().get("output")

Note that in this case, the columns B and C contain the program.
The program may contain print statements and generate a list or dataframe called output, that will be targeted at the Py() cell.
A complete working example can be found here:
Python in Excel - code on sheet mini.xlsx

Right now, we don't have plans to increase the character limit. We still plan to make the init.py (Formulas > Python > Initialization) pane editable which will allow you to edit beyond what you can do in a single cell. Was also cool to see the suggestion above.


Osmcha doesn't work

OSMCha doesnot work for edits after time about day ago. Shows smth like that:

Older changesets are visualised properly

We are having problems processing the changeset data to the map
visualization. Unfortunately, we won't be able to fix it until tomorrow.
Sorry for the inconvenience.
On Wed, 20 Mar 2019, 14:39 literannn<EMAIL_ADDRESS>wrote:

OSMCha doesnot work for edits after time about day ago. Shows smth like
that:
[image: osmcha]
https://user-images.githubusercontent.com/46343992/54706486-1b5c2000-4b50-11e9-806c-f1e435fd59bf.jpg
Older changesets visualise properly
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mapbox/osmcha-frontend/issues/349, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAoqs04zMY_E0YjtbH2UuAr-MPbqDREkks5vYnJDgaJpZM4b_4o4
.

Thanks for working on it.
In the meantime one can open a changeset in Achavi (via "Open with" dropdown). Not as convenient as OsmCha but gets the job done.

Unfortunately, Achavi does not work in Russia, thanks to https://en.wikipedia.org/wiki/Internet_censorship_in_Russia#Increase_in_Internet_censorship :-/

Is there a fix coming soon?

Any news? Seems to be down for a week - Is there anything we can help with?

👋 We're investigating this internally. We'll update this issue once we have more information. Thank you for your patience.

According to the console it give me a "403 Forbidden".
If it helps I have a screenshot:

"403 Forbidden" simply means that the changeset json data hasn't been pushed to AWS S3 yet. It's pretty much meaningless to analyze the issue at hand.

We're still having problems on the OSMCha server infrastructure. There is a delay of 10 to 11 hours between the time a new changeset is created on OpenStreetMap database and the time its visualization is available on OSMCha.
We hope all the issues will be fixed this week.
Thank you for your understanding,

Without this tool I am unable to keep an eye in the BBox of my interest. :-(, because it's makes very easy to understand what and how was changed, for every element of the changeset.
Thanks for your efforts. The delay I am seeing is bigger, Now I cannot analyze anything newer than 2019-03-19.

Hi,
i am still seeing no solution. I worked for some hours a couple days back and we are now back to completely dysfunctional or is that just me?
Flo

Reason seems to be this one: https://github.com/osmlab/changeset-map/pull/179#issuecomment-481691303

Thanks, now Osmcha works good with new edits. Are there any plans to fix visualization for changesets from 19 March to 9, April?

@literannn On the next week we will work to generate the visualization of the changesets that are missing.
Thank you very much @amishas157 @geohacker and @batpad for helping solve those issues. :clap:

@willemarcel : did you read my comment about the outdated changeset-map? That would be the remaining bit to solve this issue, as the old version still causes syntax errors.

@mmd-osm thanks for allerting! Yes, I noticed that the changes didn't get on production, although I have updated the changeset-map version on osmcha-frontend. I think there is some error on the package instalation. Checking it now.

Ok, great!
Byt the way, did you notice that https://s3.amazonaws.com/mapbox/real-changesets/production/69131255.json seems to be the last cs on AWS. The next one https://s3.amazonaws.com/mapbox/real-changesets/production/69131256.json and everything after that one aren't available yet.

it doesn't work again, for about 20 hours :-(

@willemarcel the problem seems to shift somehow. Some changesets work fine. But others are still - half? - broken. Like https://osmcha.mapbox.com/changesets/69204689/ which loads the changeset-comment, but shows an error in console and does not render the map.
(index):1 -1
console.js:35 uncaught at s TypeError: Cannot read property 'indexOf' of null
…
s3.amazonaws.com/mapbox/real-changesets/production/69204689.json:1

Failed to load resource: the server responded with a status of 403 (Forbidden)
overpass.maptime.in/api/interpreter?data=[out:xml][adiff:%222019-04-14T14:49:31Z,%22,%222019-04-14T14:49:32Z%22];(node(bbox)(changed);way(bbox)(changed);relation(bbox)(changed));out%20meta%20geom(bbox);&bbox=13.4426336,52.4664075,13.4426336,52.4664075:1

Failed to load resource: the server responded with a status of 400 (Bad Request)

The SSL certificate on overpass.maptime.in has expired on 04/28/2019.
https://overpass.maptime.in/

Thanks for reporting the issue with the SSL certificate, @mmd-osm ! @amishas157 fixed it on Monday.

Got 403 forbidden from amazonaws just now:
https://s3.amazonaws.com/mapbox/real-changesets/production/70885956.json

I still get random 403.
Do we know when those happen?
Is there a way to re-start the process that prepares the changeset for certain changesets, so they go away?
Example:

https://osmcha.mapbox.com/changesets/70770306/
https://overpass-api.de/achavi/?changeset=70770306

s3.amazonaws.com/mapbox/real-changesets/production/70770306.json:1
Failed to load resource: the server responded with a status of 403 (Forbidden)

overpass.maptime.in/api/interpreter?data=[out:xml][adiff:%222019-05-30T13:20:53Z,%22,%222019-05-30T13:21:00Z%22];(node(bbox)(changed);way(bbox)(changed);relation(bbox)(changed));out%20meta%20geom(bbox);&bbox=13.4245722,52.4771607,13.4364570,52.4850931:1
Failed to load resource: the server responded with a status of 400 (Bad Request)


feat: get the list of storages where an assets can be located

Q
A

Bug fix?
N

New feature?
Y

BC breaks?
N

Deprecations?
N

Fixed tickets
N

Get the list of storage services where an asset can be found

https://github.com/ems-project/EMSCoreBundle/issues/649


option 2: single commit merge (update with latest from watson and bluemix repos)

[Current coverage][cc-pull] is 27.07%

Merging [#45][cc-pull] into [master][cc-base-branch] will decrease coverage by 0.37%

@@             master        #45   diff @@
==========================================
  Files            24         26     +2
  Lines          3500       3586    +86
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            961        971    +10
- Misses         2539       2615    +76
  Partials          0          0

Powered by Codecov. Last updated by [9aa8d6a...3c573a4][cc-compare]
[cc-base-branch]: https://codecov.io/gh/cloudviz/agentless-system-crawler/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/cloudviz/agentless-system-crawler/compare/9aa8d6a6cae9f1e418b981f96072143691e11c6f...3c573a41a3bf18953653a9b01a9ef100a5f67272
[cc-pull]: https://codecov.io/gh/cloudviz/agentless-system-crawler/pull/45?src=pr

given everything passed, it LGTM  but I'll defer to @ricarkol to decide which option to pick  ;-)

I pick this one too.


ARROW-11397: [C++] Support faspfor compress  and decompress for int32 and int64 data type

This PR is to support the fastpfor compress and decompress when the data type is int32 or int64.

Can you explain why this would be useful?
If you want additional compression schemes to be added to the Arrow IPC format you should first discuss it on the dev@ mailing-list.

Can you explain why this would be useful?
If you want additional compression schemes to be added to the Arrow IPC format you should first discuss it on the dev@ mailing-list.

@pitrou Thanks for your review.
In our benchmark environment, we found the fastpfor compress algorithm can achieve better compress ratio than the default LZ4 when the data type is int32 and int64. I will post the detail test result later.

I'm going to close this out for now until we can discuss on the mailing list.


Main UI in home for games

Need multiple pages in home for the differents games with play option and information about the game.

Already in #33


Support for Dynamic Shadows?

Are there any plans for Craft to support dynamic shadows?
That would be a great feature to add to this already great game!

Related to #205


Proposal: create a well defined port for the octant API

Problem:
Octant starts its API on a random port on <IP_ADDRESS>. This avoids potential conflicts. Giving Octant a well defined port number by default means that you could know what the port number is and restarts of the application wouldn't require the browser URL to change. I'm going to suggest two numbers for default ports:

102016 - date Heptio was founded
7777 - Kubernetes people seem to like 7s

+1 for 7777 - easy to remember

I like 8888 or 8088 only because octagon / eight theme

I changed my mind, I actually like 7777 the best.

there should be an option to change this. a --port cli option. I have an issue where an k8 7777 service is forward and now can run octant.


DOA for Oracle

Implement preliminary function to support PL/SQL, which is a format used in Oracle DBMS.

As a first step, DOA structurally parses PL/SQL using our parser and provides assessment results for automatic/manual conversion.
In the next step, DOA performs minimum conversion of source SQLs so that psql accepts converted files without errors.

First step (v2.1.0) completed (#70).

Next we're working on the next step.


Vectorization of the IOU computation between two lists of box2ds

For a function signature
def iou(box1: list[box2d],  box2: list[box2d]) -> np.ndarray:
   ...

For two lists of box2ds, which have the length of N, and M respectively, this function should return a N*M matrix, each element is the iou value (float,[0, 1]).

Code for plan version
    @staticmethod
    def iou_matrix2(box_list1: List[Box2d], box_list2: List[Box2d]) -> np.ndarray:
        def getvalue(boxa: Box2d, boxb: Box2d):
            xmin = max(boxa.xmin, boxb.xmin)
            ymin = max(boxa.ymin, boxb.ymin)
            xmax = min(boxa.xmax, boxb.xmax)
            ymax = min(boxa.ymax, boxb.ymax)
            inter_area = max(0.0, xmax - xmin) * max(0.0, ymax - ymin)
            return inter_area / (boxa.area + boxb.area - inter_area)

        result = list()
        for a in box_list1:
            row = list()
            for b in box_list2:
                row.append(getvalue(a, b))
            result.append(np.asarray(row))
        return np.asarray(result)

I think this issue has been solved now.


NDK versions are being removed without grace period

Description
We build an Android app against the NDK version installed on the GitHub runners. During updates to the runner images, the NDK appears to get bumped and the previous default is no longer available, causing builds to fail.
We cannot control, which image version gets used so our CI is effectively blocked.
Platforms affected

[ ] Azure DevOps
[X] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[X] Ubuntu 22.04
[ ] Ubuntu 24.04
[ ] macOS 12
[ ] macOS 13
[ ] macOS 13 Arm64
[ ] macOS 14
[ ] macOS 14 Arm64
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
https://github.com/firezone/firezone/actions/runs/10804517190/job/29970095787?pr=6564
Is it regression?
Yes, the latest non-prerelease doesn't have the issue.
Expected behavior
The previous default NDK version to not be removed without a grace-period.
Actual behavior
The default NDK version changes and the old one is no longer available.
Repro steps

Create an Android app and build against the current NDK version.
GitHub decides to randomly(?) use "pre-release" images for some CI runs, failing the pipeline.

Hi @thomaseizinger Thank you for bringing this issue to us. We are looking into this issue and will update you on this issue after investigating.

Hi @thomaseizinger ,
We created announcement last month about removal of old NDK versions, please find the announcement. thank you !

That is not the issue. We were already building against NDK 27.0.12077973.
The problem is that we can only ever build against one NDK version and the latest image update removed NDK version 27.0.12077973 and instead installed 27.1.12297006.
This updats appears to have been rolled out incrementally because we saw some CI builds failing and some passing.
This is the fix we had to make: https://github.com/firezone/firezone/pull/6662. But initially, this PR also didn't pass CI reliably because the update was not yet rolled out to all runners.
We don't have any ability to specify, which runner image version we get which essentially leaves us in a broken state: We can only rerun failed CI builds in the hope that we get an old image version with the previous NDK and eventually merge the PR where we use the newer NDK.
Instead of removing the old NDK, can you first add the new NDK to an image release? That would give us time to migrate to the new version. Subsequently, you can then remove the previous version without breaking CI.

HI @thomaseizinger ,

That is not the issue. We were already building against NDK 27.0.12077973.
The problem is that we can only ever build against one NDK version and the latest image update removed NDK version 27.0.12077973 and instead installed 27.1.12297006.

Yes, for every rollout new version will be automatically fetched if it is exist .

Instead of removing the old NDK, can you first add the new NDK to an image release? That would give us time to migrate to the new version. Subsequently, you can then remove the previous version without breaking CI.

yes , before deleting any major versions we will raise an announcement as mentioned above .
When coming to minor and hotfix versions will automatically fetched available versions as per script , if new versions available that will be coming with new rollout .
Thank you ! , hoping you build got succeed with latest release , kindly provide your confirmation on it .

Instead of removing the old NDK, can you first add the new NDK to an image release? That would give us time to migrate to the new version. Subsequently, you can then remove the previous version without breaking CI.

yes , before deleting any major versions we will raise an announcement as mentioned above .

It is nice that you make an announcement that CI will be broken for a couple of days. It would be better if you wouldn't break CI for a couple of days.
The issue is that you can only build an Android App against a single, specific NDK version. Your rollout seems to be incremental, which makes sense. But it means that during the rollout, it is a lottery, whether we are getting a version with the new or the old NDK version, so we are in the following scenario:

main references version 27.0.12077973. Some CI runs will pass because they run on machines that haven't upgraded yet.
As the rollout progressed, more and more CI runs will fail because the NDK version doesn't exist.
At some point in the rollout, we have to force-merge a PR that changes the NDK version 27.1.12297006.
Now, CI runs that are given the new NDK version will pass.
Still, there will be CI runs on runners that are still using the old version and those will fail.

This is a huge service disruption because we cannot merge PRs reliably during this period, see:

When coming to minor and hotfix versions will automatically fetched available versions as per script , if new versions available that will be coming with new rollout .

Instead of replacing the version, can you fetch two versions? The one previously installed and whatever is the latest at the time? That way, the rollout doesn't break CI and we can update to the new NDK version after the rollout is completed.

The issue is that you can only build an Android App against a single, specific NDK version. Your rollout seems to be incremental, which makes sense. But it means that during the rollout, it is a lottery, whether we are getting a version with the new or the old NDK version, so we are in the following scenario:

During the rollout the the existing version will not be changed. the new NDK version available once image rollout completed in to both GitHub Runners and Hosted agents.

Instead of replacing the version, can you fetch two versions? The one previously installed and whatever is the latest at the time? That way, the rollout doesn't break CI and we can update to the new NDK version after the rollout is completed.

Currently, we do not have plans to fetch both the previously installed and the latest NDK versions.  we confirm that ubuntu images have latest NDK version . i hope you're CIs ran successfully .

The issue is that you can only build an Android App against a single, specific NDK version. Your rollout seems to be incremental, which makes sense. But it means that during the rollout, it is a lottery, whether we are getting a version with the new or the old NDK version, so we are in the following scenario:

During the rollout the the existing version will not be changed. the new NDK version available once image rollout completed in to both GitHub Runners and Hosted agents.

That is not true in our experience. We have seen several CI builds that use a "pre-release" image which will have a newer NDK version and thus fail.

Instead of replacing the version, can you fetch two versions? The one previously installed and whatever is the latest at the time? That way, the rollout doesn't break CI and we can update to the new NDK version after the rollout is completed.

Currently, we do not have plans to fetch both the previously installed and the latest NDK versions.

What is your suggestion then to implement reliable CI for Android apps that use the NDK?

Hi @thomaseizinger ,
Pin your NDK version in your CI configuration. This ensures that the build environment remains consistent and reduces the risk of unexpected breaks due to NDK updates.

I can do that yeah. I am not sure what the point of the pre-installed NDK is then if your advice is to install a separate version?

Hi @thomaseizinger ,

We will announce major version removals in advance.
As per image policy , system will automatically fetch the default version i.e. 27.1.12297006( latest NDK) ;
Further pinning of particular  version is not possible.
Thank you!

We will announce major version removals in advance.

Android only allows to build against a specific NDK, thus even a change to a patch version of the NDK is breaking and not just major versions.
I'll spell it out again because my point doesn't seem to be coming across: Removing tools without a grace period for transitioning leads to broken CI even if you announce it ahead of time.
What is the point of pre-installed software if I can't use it because you are swapping it out from underneath me? GitHub actions doesn't expose a way for me to select, which image version of the runner I will get, you need to either expose a mechanism for that or install multiple versions of certain tools side-by-side. Without either of these things, every image update will break CI for many developers.

Yey, it is broken again :tada: :tada: :tada:
https://github.com/firezone/firezone/actions/runs/11450062859/job/31856868142?pr=7103


Sidebar menu on hover

Issue type:
[ ] Feature request
[X ] Bug report
[ ] Documentation

Environment:

AdminLTE Version:  2.4
Operating System:
Browser (Version):  Chrome, FF, IE

Description:
I want to use the sidebar expand on hover function but it doesnt seem to work at all on my end. I have added this right before  :

And adminlte.min.js is added by the footer. My body classes are:

Any ideas?

Found issue: you need to leave the toggle button on page to make it work. I added display: none; in adminLTE.css


Rare SIGSEGV during mainnet benchmark 🥶

Benchmarking Block 15274915(1226 txs, 29928443 gas)/Parallel: Collecting 100 samples in estimated 5.2303 s (1900 iterations)error: bench failed, to rerun pass `--bench mainnet`

Caused by:
  process didn't exit successfully: `.../pevm/target/release/deps/mainnet-2bec42578f0ffffc --noplot --bench` (signal: 11, SIGSEGV: invalid memory reference)

69c90e62b341102223b54169759a8338a6843207 seems to have caused it. This is only reproducible on ARM, not on x86.

This is miraculously fixed by #286. It could have been an unsafe race condition of defer-drop  triggered by referencing data in its mv_memory. We need a better garbage collection mechanism to replace defer-drop (last updated 2 years ago).
https://github.com/risechain/pevm/blob/c41223f553ad4f4c0fd00d706c140b3b7584eaf3/src/pevm.rs#L118-L119

It's very likely to be a rpmalloc issue on Graviton as others don't crash. Current "fix": https://github.com/risechain/pevm/pull/290.


twine let me upload the .whl distribution but not the .tar.gz archive using an API key.

Describe the bug
twine let me upload the .whl distribution but not the .tar.gz archive using an API key on an account with 2FA.
Expected behavior
To upload both files as happened with testpypi and basic authentication:
% python3 -m twine upload --repository-url https://test.pypi.org/legacy/ dist/*
Enter your username: johnsyweb
Enter your password:
Uploading distributions to https://test.pypi.org/legacy/
Uploading sparse_list-0.8-py3-none-any.whl
100%|████████████████████████████████████████████████| 11.8k/11.8k [00:02<00:00, 4.09kB/s]
Uploading sparse_list-0.8.tar.gz
100%|████████████████████████████████████████████████| 10.7k/10.7k [00:01<00:00, 6.12kB/s]

Files for your inspection are here: https://test.pypi.org/project/sparse-list/0.8/#files
To Reproduce
Here's the exact command I ran with the timestamp (Australia / Melbourne) to assist with finding the requests in logs.
[Sun 19/08/04 20:48 AEST][s001][x86_64/darwin18.2.0/18.6.0][5.7.1]
<paj@mrs-cake:~/src/python_sparse_list>
zsh 1759  (git)-[master]-% python3 -m twine upload dist/*

Uploading distributions to https://upload.pypi.org/legacy/
Uploading sparse_list-0.8-py3-none-any.whl
100%|████████████████████████████████████████████████| 11.8k/11.8k [00:03<00:00, 3.33kB/s]
Uploading sparse_list-0.8.tar.gz
100%|████████████████████████████████████████████████| 10.7k/10.7k [00:00<00:00, 27.5kB/s]
NOTE: Try --verbose to see response content.
HTTPError: 403 Client Error: The credential associated with user 'johnsyweb' isn't allowed to upload to project 'sparse-list'. See https://pypi.org/help/#project-name for more information. for url: https://upload.pypi.org/legacy/

Subsequent runs looked like this:
[Sun 19/08/04 21:34 AEST][s001][x86_64/darwin18.2.0/18.6.0][5.7.1]
<paj@mrs-cake:~/src/python_sparse_list>
zsh 1765 [127]  (git)-[master]-% python3 -m twine upload dist/*
Uploading distributions to https://upload.pypi.org/legacy/
Uploading sparse_list-0.8-py3-none-any.whl
100%|████████████████████████████████████████████████| 11.8k/11.8k [00:01<00:00, 6.28kB/s]
NOTE: Try --verbose to see response content.
HTTPError: 403 Client Error: The credential associated with user 'johnsyweb' isn't allowed to upload to project 'sparse-list'. See https://pypi.org/help/#project-name for more information. for url: https://upload.pypi.org/legacy/
[Sun 19/08/04 21:34 AEST][s001][x86_64/darwin18.2.0/18.6.0][5.7.1]
<paj@mrs-cake:~/src/python_sparse_list>
zsh 1766 [1]  (git)-[master]-% python3 -m twine upload dist/* --verbose
Uploading distributions to https://upload.pypi.org/legacy/
Uploading sparse_list-0.8-py3-none-any.whl
100%|████████████████████████████████████████████████| 11.8k/11.8k [00:01<00:00, 6.29kB/s]
Content received from server:

  <title>403 The credential associated with user 'johnsyweb' isn't allowed to upload to project 'sparse-list'. See https://pypi.org/help/#project-name for more information.</title>

403 The credential associated with user 'johnsyweb' isn't allowed to upload to project 'sparse-list'. See https://pypi.org/help/#project-name for more information.

  Access was denied to this resource.

The credential associated with user 'johnsyweb' isn't allowed to upload to project 'sparse-list'. See https://pypi.org/help/#project-name for more information.

HTTPError: 403 Client Error: The credential associated with user 'johnsyweb' isn't allowed to upload to project 'sparse-list'. See https://pypi.org/help/#project-name for more information. for url: https://upload.pypi.org/legacy/

My Platform
% uname -a
Darwin mrs-cake.lan 18.6.0 Darwin Kernel Version 18.6.0: Thu Apr 25 23:16:27 PDT 2019; root:xnu-4903.261.4~2/RELEASE_X86_64 x86_64

% python --version
Python 3.7.3

API Key UID: 54b43a9a-73a4-4c79-a7ac-23dc247eabb1

Cc: @di

Thank you for your report! It uncovered a bug in API Token scoping for projects which didn't take into account normalization per PEP 426. That was resolved in #6363.
The reason of the difference here is that the wheel's metadata had the name correctly normalized (sparse-list), while the sdist did not (sparse_list). So when comparing to the scoped token, one was successful and one was not.
Affected users (including you) will be sent a notification shortly of the issue, notifying them to create new tokens.

Also of note, @johnsyweb if you create a new API token scoped for sparse_list this should be resolved and function as anticipated.

Email received. Thanks for the swift resolution.


Support for Java 9

Java 9 GA has been released so we should plan to properly support it

is there any java 9 feature that jetcd might want?

no it is more about compatibility of jetcd and its dependencies and to trst if we can make jetcd play with JPMS

Tried on Java 11 in an application using JPMS and jetcd does not work. The application can not even start due to the dependecy on gRPC :
Modules grpc.api and grpc.context export package io.grpc to module protobuf.java
https://github.com/grpc/grpc-java/issues/3522


Typescript next projects seem to fail

Followed all the steps in the Documentation, with the exception of passing "--ts" in to the create-next-app command
I've also setup the two flags and NODE_VERSION set to 16
Upon deployment I get a syntax error at the end:
2022-10-26T19:36:53.969765Z	Cloning repository...
2022-10-26T19:36:55.487943Z	Success: Finished cloning repository files
2022-10-26T19:36:56.117328Z	Installing dependencies
2022-10-26T19:36:56.129093Z	Python version set to 2.7
2022-10-26T19:36:59.355548Z	Downloading and installing node v16.18.0...
2022-10-26T19:36:59.7492Z	Downloading https://nodejs.org/dist/v16.18.0/node-v16.18.0-linux-x64.tar.xz...
2022-10-26T19:37:00.267237Z	Computing checksum with sha256sum
2022-10-26T19:37:00.398678Z	Checksums matched!
2022-10-26T19:37:04.815229Z	Now using node v16.18.0 (npm v8.19.2)
2022-10-26T19:37:05.210183Z	Started restoring cached build plugins
2022-10-26T19:37:05.223363Z	Finished restoring cached build plugins
2022-10-26T19:37:05.728749Z	Attempting ruby version 2.7.1, read from environment
2022-10-26T19:37:09.454577Z	Using ruby version 2.7.1
2022-10-26T19:37:09.831197Z	Using PHP version 5.6
2022-10-26T19:37:10.004214Z	5.2 is already installed.
2022-10-26T19:37:10.033486Z	Using Swift version 5.2
2022-10-26T19:37:10.034455Z	Started restoring cached node modules
2022-10-26T19:37:10.053401Z	Finished restoring cached node modules
2022-10-26T19:37:10.576255Z	Installing NPM modules using NPM version 8.19.2
2022-10-26T19:37:10.994932Z	npm WARN config tmp This setting is no longer used.  npm stores temporary files in a special
2022-10-26T19:37:10.99531Z	npm WARN config location in the cache, and they are managed by
2022-10-26T19:37:10.995476Z	npm WARN config     cacache.
2022-10-26T19:37:11.410054Z	npm WARN config tmp This setting is no longer used.  npm stores temporary files in a special
2022-10-26T19:37:11.410518Z	npm WARN config location in the cache, and they are managed by
2022-10-26T19:37:11.410699Z	npm WARN config     cacache.
2022-10-26T19:37:22.210057Z
2022-10-26T19:37:22.210405Z	added 407 packages, and audited 408 packages in 11s
2022-10-26T19:37:22.210883Z
2022-10-26T19:37:22.211107Z	97 packages are looking for funding
2022-10-26T19:37:22.211328Z	  run npm fund for details
2022-10-26T19:37:22.221973Z
2022-10-26T19:37:22.222291Z	6 moderate severity vulnerabilities
2022-10-26T19:37:22.222436Z
2022-10-26T19:37:22.222552Z	Some issues need review, and may require choosing
2022-10-26T19:37:22.222687Z	a different dependency.
2022-10-26T19:37:22.222803Z
2022-10-26T19:37:22.222923Z	Run npm audit for details.
2022-10-26T19:37:22.244996Z	NPM modules installed
2022-10-26T19:37:22.838234Z	npm WARN config tmp This setting is no longer used.  npm stores temporary files in a special
2022-10-26T19:37:22.838642Z	npm WARN config location in the cache, and they are managed by
2022-10-26T19:37:22.838813Z	npm WARN config     cacache.
2022-10-26T19:37:22.857813Z	Installing Hugo 0.54.0
2022-10-26T19:37:23.56131Z	Hugo Static Site Generator v0.54.0-B1A82C61A/extended linux/amd64 BuildDate: 2019-02-01T10:04:38Z
2022-10-26T19:37:23.565706Z	Started restoring cached go cache
2022-10-26T19:37:23.589094Z	Finished restoring cached go cache
2022-10-26T19:37:23.736834Z	go version go1.14.4 linux/amd64
2022-10-26T19:37:23.753772Z	go version go1.14.4 linux/amd64
2022-10-26T19:37:23.757273Z	Installing missing commands
2022-10-26T19:37:23.757612Z	Verify run directory
2022-10-26T19:37:23.757772Z	Executing user command: npx @cloudflare/next-on-pages --experimental-minify
2022-10-26T19:37:24.265282Z	npm WARN config tmp This setting is no longer used.  npm stores temporary files in a special
2022-10-26T19:37:24.265616Z	npm WARN config location in the cache, and they are managed by
2022-10-26T19:37:24.265781Z	npm WARN config     cacache.
2022-10-26T19:37:24.896506Z	⚡ @cloudflare/next-to-pages CLI
2022-10-26T19:37:24.901424Z	⚡
2022-10-26T19:37:24.901752Z	⚡ Installing 'vercel' CLI...
2022-10-26T19:37:24.901928Z	⚡
2022-10-26T19:37:25.414383Z	▲ npm
2022-10-26T19:37:25.415235Z	▲  WARN config tmp This setting is no longer used.  npm stores temporary files in a special
2022-10-26T19:37:25.415487Z	▲ npm WARN config location in the cache, and they are managed by
2022-10-26T19:37:25.415629Z	▲ npm WARN config     cacache.
2022-10-26T19:37:25.41577Z	▲
2022-10-26T19:37:26.40685Z	▲
2022-10-26T19:37:26.407293Z	▲ up to date, audited 408 packages in 1s
2022-10-26T19:37:26.407457Z	▲
2022-10-26T19:37:26.407576Z	▲
2022-10-26T19:37:26.407688Z	▲ 97 packages are looking for funding
2022-10-26T19:37:26.408125Z	▲   run npm fund for details
2022-10-26T19:37:26.408287Z	▲
2022-10-26T19:37:26.416697Z	▲
2022-10-26T19:37:26.41694Z	▲ 6 moderate severity vulnerabilities
2022-10-26T19:37:26.417076Z	▲
2022-10-26T19:37:26.417214Z	▲ Some issues need review, and may require choosing
2022-10-26T19:37:26.417384Z	▲ a different dependency.
2022-10-26T19:37:26.417527Z	▲
2022-10-26T19:37:26.417659Z	▲ Run npm audit for details.
2022-10-26T19:37:26.417773Z	▲
2022-10-26T19:37:26.43072Z	⚡
2022-10-26T19:37:26.431035Z	⚡
2022-10-26T19:37:26.431223Z	⚡ Completed 'npx vercel build'.
2022-10-26T19:37:26.431387Z	⚡
2022-10-26T19:37:26.431532Z	⚡
2022-10-26T19:37:26.431683Z	⚡ Building project with 'npx vercel build'...
2022-10-26T19:37:26.431833Z	⚡
2022-10-26T19:37:26.922421Z	▲ npm
2022-10-26T19:37:26.922816Z	▲  WARN config tmp This setting is no longer used.  npm stores temporary files in a special
2022-10-26T19:37:26.923021Z	▲ npm WARN
2022-10-26T19:37:26.9232Z	▲  config location in the cache, and they are managed by
2022-10-26T19:37:26.923353Z	▲ npm
2022-10-26T19:37:26.923505Z	▲ WARN config
2022-10-26T19:37:26.923652Z	▲      cacache.
2022-10-26T19:37:26.923807Z	▲
2022-10-26T19:37:27.689427Z	▲ Vercel CLI 28.4.12
2022-10-26T19:37:27.68996Z	▲
2022-10-26T19:37:28.083032Z	▲ Installing dependencies...
2022-10-26T19:37:28.083385Z	▲
2022-10-26T19:37:28.501515Z	▲ npm
2022-10-26T19:37:28.501932Z	▲
2022-10-26T19:37:28.502743Z	▲ WARN config tmp This setting is no longer used.  npm stores temporary files in a special
2022-10-26T19:37:28.502946Z	▲ npm
2022-10-26T19:37:28.503116Z	▲  WARN
2022-10-26T19:37:28.50329Z	▲  config
2022-10-26T19:37:28.503437Z	▲  location in the cache, and they are managed by
2022-10-26T19:37:28.50358Z	▲ npm WARN config
2022-10-26T19:37:28.50371Z	▲      cacache.
2022-10-26T19:37:28.50385Z	▲
2022-10-26T19:37:29.22338Z	▲
2022-10-26T19:37:29.223706Z	▲ up to date in 753ms
2022-10-26T19:37:29.223877Z	▲
2022-10-26T19:37:29.224Z	▲
2022-10-26T19:37:29.224123Z	▲ 97 packages are looking for funding
2022-10-26T19:37:29.224255Z	▲   run npm fund for details
2022-10-26T19:37:29.224369Z	▲
2022-10-26T19:37:29.236929Z	▲ Detected Next.js version: 13.0.0
2022-10-26T19:37:29.237337Z	▲
2022-10-26T19:37:29.244903Z	▲ Detected package-lock.json generated by npm 7+...
2022-10-26T19:37:29.245416Z	▲
2022-10-26T19:37:29.245667Z	▲ Running "npm run build"
2022-10-26T19:37:29.246107Z	▲
2022-10-26T19:37:29.747487Z	▲ npm
2022-10-26T19:37:29.747918Z	▲  WARN
2022-10-26T19:37:29.748092Z	▲  config tmp This setting is no longer used.  npm stores temporary files in a special
2022-10-26T19:37:29.748243Z	▲ npm WARN
2022-10-26T19:37:29.748667Z	▲  config location in the cache, and they are managed by
2022-10-26T19:37:29.74887Z	▲ npm WARN config     cacache.
2022-10-26T19:37:29.749071Z	▲
2022-10-26T19:37:29.765875Z	▲
2022-10-26T19:37:29.766156Z	▲ ><EMAIL_ADDRESS>build
2022-10-26T19:37:29.766312Z	▲ > next build
2022-10-26T19:37:29.766429Z	▲
2022-10-26T19:37:29.766538Z	▲
2022-10-26T19:37:30.369708Z	▲ warn  - You have enabled experimental feature (runtime) in next.config.js.
2022-10-26T19:37:30.3701Z	▲
2022-10-26T19:37:30.370384Z	▲ warn  - Experimental features are not covered by semver, and may cause unexpected or broken application behavior. Use at your own risk.
2022-10-26T19:37:30.37056Z	▲
2022-10-26T19:37:30.370715Z	▲
2022-10-26T19:37:30.370852Z	▲
2022-10-26T19:37:30.418714Z	▲ Attention: Next.js now collects completely anonymous telemetry regarding usage.
2022-10-26T19:37:30.419065Z	▲
2022-10-26T19:37:30.419244Z	▲ This information is used to shape Next.js' roadmap and prioritize features.
2022-10-26T19:37:30.419396Z	▲ You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
2022-10-26T19:37:30.41954Z	▲ https://nextjs.org/telemetry
2022-10-26T19:37:30.419677Z	▲
2022-10-26T19:37:30.4198Z	▲
2022-10-26T19:37:30.55511Z	▲ info  - Linting and checking validity of types...
2022-10-26T19:37:30.555564Z	▲
2022-10-26T19:37:32.967327Z	▲
2022-10-26T19:37:32.967631Z	▲ ./pages/api/hello.ts
2022-10-26T19:37:32.967803Z	▲ 3:1  Warning: Unexpected default export of anonymous function  import/no-anonymous-default-export
2022-10-26T19:37:32.967956Z	▲
2022-10-26T19:37:32.968102Z	▲ info  - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/basic-features/eslint#disabling-rules
2022-10-26T19:37:32.968245Z	▲ info  - Creating an optimized production build...
2022-10-26T19:37:32.968379Z	▲
2022-10-26T19:37:33.338757Z	▲ warn  - You are using the experimental Edge Runtime with experimental.runtime.
2022-10-26T19:37:33.339151Z	▲
2022-10-26T19:37:37.880708Z	▲ info  - Compiled successfully
2022-10-26T19:37:37.881022Z	▲
2022-10-26T19:37:37.881196Z	▲ info  - Collecting page data...
2022-10-26T19:37:37.881325Z	▲
2022-10-26T19:37:43.138679Z	▲ info  - Generating static pages (0/2)
2022-10-26T19:37:43.139007Z	▲
2022-10-26T19:37:43.237084Z	▲ info  - Generating static pages (2/2)
2022-10-26T19:37:43.23791Z	▲
2022-10-26T19:37:43.246592Z	▲ info  - Finalizing page optimization...
2022-10-26T19:37:43.246992Z	▲
2022-10-26T19:37:43.251362Z	▲
2022-10-26T19:37:43.251645Z	▲
2022-10-26T19:37:43.273961Z	▲ Route (pages)                              Size     First Load JS
2022-10-26T19:37:43.2744Z	▲ ┌ ℇ /                                      252 B          72.4 kB
2022-10-26T19:37:43.274629Z	▲ ├   /_app                                  0 B            72.1 kB
2022-10-26T19:37:43.274913Z	▲ ├ ○ /404                                   181 B          72.3 kB
2022-10-26T19:37:43.275065Z	▲ └ ℇ /api/hello                              0 B            72.1 kB
2022-10-26T19:37:43.275199Z	▲ + First Load JS shared by all              72.4 kB
2022-10-26T19:37:43.27533Z	▲   ├ chunks/framework-19b86674b25439d7.js   45.4 kB
2022-10-26T19:37:43.275467Z	▲   ├ chunks/main-d2a793b6dc23a82a.js        25.7 kB
2022-10-26T19:37:43.275608Z	▲   ├ chunks/pages/_app-fdaca63b9de4692d.js  295 B
2022-10-26T19:37:43.275739Z	▲   ├ chunks/webpack-8fa1640cc84ba8fe.js     750 B
2022-10-26T19:37:43.275886Z	▲   └ css/ab44ce7add5c3d11.css               247 B
2022-10-26T19:37:43.276009Z	▲
2022-10-26T19:37:43.276131Z	▲
2022-10-26T19:37:43.276264Z	▲ ℇ  (Streaming)  server-side renders with streaming (uses React 18 SSR streaming or Server Components)
2022-10-26T19:37:43.276384Z	▲ ○  (Static)     automatically rendered as static HTML (uses no initial props)
2022-10-26T19:37:43.276506Z	▲
2022-10-26T19:37:43.276614Z	▲
2022-10-26T19:37:44.64983Z	▲ Traced Next.js server files in: 1.208s
2022-10-26T19:37:44.650179Z	▲
2022-10-26T19:37:45.063343Z	▲ Created all serverless functions in: 413.039ms
2022-10-26T19:37:45.063671Z	▲
2022-10-26T19:37:45.174166Z	▲ Collected static files (public/, static/, .next/static): 7.319ms
2022-10-26T19:37:45.174472Z	▲
2022-10-26T19:37:45.20914Z	▲ Build Completed in .vercel/output [17s]
2022-10-26T19:37:45.209458Z	▲
2022-10-26T19:37:45.277658Z	⚡
2022-10-26T19:37:45.278206Z	⚡
2022-10-26T19:37:45.278419Z	⚡ Completed 'npx vercel build'.
2022-10-26T19:37:45.278559Z	⚡
2022-10-26T19:37:45.347169Z	/opt/buildhome/repo/node_modules/@cloudflare/next-on-pages/dist/index.js:3057
2022-10-26T19:37:45.347496Z	  var err = new SyntaxError(message);
2022-10-26T19:37:45.347644Z	            ^
2022-10-26T19:37:45.347784Z
2022-10-26T19:37:45.347928Z	SyntaxError: Unexpected token (200:110)
2022-10-26T19:37:45.348051Z	    at Parser2.pp$4.raise (/opt/buildhome/repo/node_modules/@cloudflare/next-on-pages/dist/index.js:3057:13)
2022-10-26T19:37:45.348168Z	    at Parser2.pp$9.unexpected (/opt/buildhome/repo/node_modules/@cloudflare/next-on-pages/dist/index.js:651:8)
2022-10-26T19:37:45.34831Z	    at Parser2.pp$5.parseExprAtom (/opt/buildhome/repo/node_modules/@cloudflare/next-on-pages/dist/index.js:2440:18)
2022-10-26T19:37:45.348434Z	    at Parser2.pp$5.parseExprSubscripts (/opt/buildhome/repo/node_modules/@cloudflare/next-on-pages/dist/index.js:2304:19)
2022-10-26T19:37:45.348585Z	    at Parser2.pp$5.parseMaybeUnary (/opt/buildhome/repo/node_modules/@cloudflare/next-on-pages/dist/index.js:2275:17)
2022-10-26T19:37:45.3487Z	    at Parser2.pp$5.parseExprOps (/opt/buildhome/repo/node_modules/@cloudflare/next-on-pages/dist/index.js:2206:19)
2022-10-26T19:37:45.348827Z	    at Parser2.pp$5.parseMaybeConditional (/opt/buildhome/repo/node_modules/@cloudflare/next-on-pages/dist/index.js:2190:19)
2022-10-26T19:37:45.348953Z	    at Parser2.pp$5.parseMaybeAssign (/opt/buildhome/repo/node_modules/@cloudflare/next-on-pages/dist/index.js:2147:19)
2022-10-26T19:37:45.349062Z	    at Parser2.pp$5.parseExpression (/opt/buildhome/repo/node_modules/@cloudflare/next-on-pages/dist/index.js:2113:19)
2022-10-26T19:37:45.34917Z	    at Parser2.pp$8.parseStatement (/opt/buildhome/repo/node_modules/@cloudflare/next-on-pages/dist/index.js:839:47) {
2022-10-26T19:37:45.34929Z	  pos: 22596,
2022-10-26T19:37:45.349397Z	  loc: Position2 { line: 200, column: 110 },
2022-10-26T19:37:45.349502Z	  raisedAt: 22597
2022-10-26T19:37:45.349608Z	}
2022-10-26T19:37:45.368882Z	Failed: build command exited with code: 1
2022-10-26T19:37:46.416179Z	Failed: an internal error occurred

I'm getting the same error and I'm not using ts

Please see the issue I raised here, as I had the same error, but managed to get it fixed by patching this @cloudflare/next-on-pages package:
https://github.com/cloudflare/next-on-pages/issues/8#issuecomment-1290518403
Hope to get this fixed soon!

Thanks @kvnang ! Confirmed your patch works. Going to close this issue as a duplicate of yours #8


gram_feat problem u train_tagger.py

Zdravo,
pokušao sam da testiram vaš pos tager ali imam problem jer python script train_tagger.py sadrži nedefinisanu promenljivu  gram_feat.
Kako rešiti ovaj problem?
Pozdrav, Miloš

The variable gram_feat is part of some ghost functions that were used in early experiments on using additional linguistic features during tagging that were proven not to be useful. Running the code should not be an issue, regardless of this uncleaned code.
Could you share more on what you are running and what exceptions or errors you observe? I would also not mind hearing more on what you plan to use the tagger for.


Rename api/proto/common to api/proto/evecommon

Also renamed api/proto/common/common.proto to api/proto/evecommon/evecommon.proto

LGTM. I take it that you did the zedclound build with this as well, correct @kalyan-nidumolu ?

LGTM. I take it that you did the zedclound build with this as well, correct @kalyan-nidumolu ?

Yes.. I sent u the Zedcloud PR as well ( WIP - till eve merges )


Improvement: Friendly Colorname (ColorInfo)

Hi again
Please check my suggestion about having a friendly colorname.
I'm new to c++ and don't follow any convention/protocol so feel 100% free to adapt as you know best if you like this.
This was inspired by C# and MagikCore and overload of Color creation to add just the colorname instead of RGBA.
ColorInfo » Colornames to RGBA  (outside Color to reduce memory footprint)
Color » overload to allow an easy Color("black"), Add a cache if too much called and an Exception if the color doesn't exist.
Thanks
Ricardo
ouzel.graphics.ColorInfo.zip
samples.zip

forget Color.cpp change on the zip
ouzel.graphics.ColorInfo.zip

corrected cache key from char* to string
ouzel.graphics.ColorInfo.zip

Ok, I will add them as constants in Colot.h rather than the string map. String lookup is slow and unneeded and strings take up unnecessary space.
Why do you need the compliance information in a game engine?

Added first color constants (see the commit https://github.com/elnormous/ouzel/commit/743f89c3fbff174dd252fa20440edd355b73b383).

My intention was to give tools and facilitate further integration. This called just on time on object creation - doesn't impact on animation speed.
Please see Xlib on wikipedia


ansible_facts get destroyed under certain conditions

I'm running into a situation in which mitogen destroys/overwrites the ansible_facts hash. The resulting error message is that ansible_facts doesn't contain a key hostname when checking it with something like when: "ansible_facts.hostname != 'whatever'", but only in the second loop iteration.
Confused by the description? Yeah, me too, and I'm sorry about that :) Here's an example playbook that shows the problem:
- hosts: all
  tasks:
    - when: "ansible_facts.hostname != 'doesnotmatter'"
      block:
        - command: "echo {{ item }}"
          with_items: [ 'hello', 'world' ]

Bisecting leads to commit 7d6d76e4449ce69e19a4da3e3eb712059ce96ca1 being the culprit. Running this playbook with any of its parents works fine; running it with any of its children (including today's master at https://gist.github.com/52599f2e96d7d118f43726ce624623a1) fails with the following output:
[0 mosu@sweet-chili (main) ~/ansible/mosu] ansible-playbook -l sweet-chili test.yml

PLAY [all] **********************************************************************************************************************************************************************************************************************************

TASK [Gathering Facts] **********************************************************************************************************************************************************************************************************************
[WARNING]: Platform linux on host sweet-chili is using the discovered Python interpreter at /usr/bin/python, but future installation of another Python interpreter could change this. See
https://docs.ansible.com/ansible/2.9/reference_appendices/interpreter_discovery.html for more information.
ok: [sweet-chili]

TASK [command] ******************************************************************************************************************************************************************************************************************************
changed: [sweet-chili] => (item=hello)
fatal: [sweet-chili]: FAILED! => {"msg": "The conditional check 'ansible_facts.hostname != 'doesnotmatter'' failed. The error was: error while evaluating conditional (ansible_facts.hostname != 'doesnotmatter'): 'dict object' has no attribute 'hostname'\n\nThe error appears to be in '/home/mosu/ansible/mosu/test.yml': line 14, column 11, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n      block:\n        - command: \"echo {{ item }}\"\n          ^ here\nWe could be wrong, but this one looks like it might be an issue with\nmissing quotes. Always quote template expression brackets when they\nstart a value. For instance:\n\n    with_items:\n      - {{ foo }}\n\nShould be written as:\n\n    with_items:\n      - \"{{ foo }}\"\n"}

PLAY RECAP **********************************************************************************************************************************************************************************************************************************
sweet-chili                : ok=1    changed=0    unreachable=0    failed=1    skipped=0    rescued=0    ignored=0

Note that using e.g. debug instead of command does not trigger the issue. Other modules that do trigger the issue include copy.
I've uploaded a run with -vvv with mitogen at a60c6c14a2473c895162a1b58a81bad0e63d1718 here.
I'm running an unmodified Ansible 2.9.11 on Arch Linux. There are no custom modules. Host & target are the same machine running Python 3.8.5.
Note that this only happens when the target is Arch Linux, not when the target is Ubuntu. When the target is Arch Linux, it happens no matter what the host system is (Arch or Ubuntu).
To me it looks like it only happens when the interpreter detection is run & fails somehow.
This is the output of ansible-config dump --only-changed:
ANSIBLE_NOCOWS(/home/mosu/ansible/mosu/ansible.cfg) = True
DEFAULT_HOST_LIST(/home/mosu/ansible/mosu/ansible.cfg) = ['/home/mosu/ansible/mosu/inventory']
DEFAULT_STRATEGY(/home/mosu/ansible/mosu/ansible.cfg) = mitogen_linear
DEFAULT_STRATEGY_PLUGIN_PATH(/home/mosu/ansible/mosu/ansible.cfg) = ['/home/mosu/ansible/mosu/plugins/strategy/mitogen/ansible_mitogen/plugins/strategy']
INTERPRETER_PYTHON(/home/mosu/ansible/mosu/ansible.cfg) = /usr/bin/python3

3 things:

This is a wonderfully detailed ticket :D Thank you for making it so easy to follow.
I'll take a look soon 👍 currently trying to get collections/Ansible 2.10 support finished here since Ansible 2.10 just dropped. Since it's a regression with what's been added since Mitogen 0.2.9 I'll try and get it in before the next Mitogen version is released.
We welcome any PRs; if someone wants to try and tackle this before I get a chance to that'd be cool too! 😄


duplicate error message makes it difficult to determine code location

There are 2 identical error messages in the code making it difficult to work out which code path occurred.
		if firstEndorser == nil || firstResponse == nil {
			return nil, rpcError(codes.Aborted, "failed to endorse transaction, see attached details for more info", errDetails...)
		}

	if endorsements == nil {
		return nil, rpcError(codes.Aborted, "failed to endorse transaction, see attached details for more info", errorDetails...)
	}

in api.go
Would be good to make these distinguishable or have error log messages in the peer so that you have something in the peer logs to indicate the code path

fixed


[Bug] Close Calendar after date selection

Not sure if it's left open by choice, but when selecting the date on the calendar, it stays open until you move onto another part of the screen. Not a major issue, but additional clicking required.

Fixed.

feature delivered and tested.


The line brake element inserting menu option

Excellent work. Man, your code is going viral.
One notice. When editing a template and inserting a menu option, after pressing Enter, the new option is inserted with the line brake  element.

@AntanasPliauskys Thank you for posting this issue, it should be fixed now.


Make data that updates less frequently than every day be displayed as such

Basically we need to format it such that the temporal data only shows data points that are actual updates, while not breaking the model by having it try and use data points that don't exist.

@seamuslo
I made an initial attempt at this. Now the plots handle historical data with missing days fine. On the temporal csv, just leave blank the entries that don't contain data. For modeling and other purposes, calling SD_object.value() will return the last, non empty data point. There are two details to note:

The system will still respond poorly to a history that is completely empty. It needs at least one data point.
When running the simulation, the graph will plot the new simulated data on a daily basis, regardless of the span between data points in the historical data. If we want to set up a mechanism for designating a "plot refresh rate" of something other than daily, we can but it will require more work.


Fix uploadChunk, disable zstd on Windows, and implement generic retry methods

Fixes several reliability issues with the caching action:

Fixes #298, where uploadChunk was not resetting the stream before retrying the upload, causing the second attempt to always fail.

Fixes #301, where bsdtar with zstd was hanging on Windows on large files.  This disables zstd on Windows only.

Adds generic retry methods and uses them for getCacheEntry and uploadChunk.  The new retry methods also treat any Error as retryable, which from testing mostly come from socket-level errors (e.g., connect ETIMEDOUT).

Abandoning, splitting out into separate PRs so we can cherry-pick specific changes easier.


No storage limits documented.

"When database space used reaches the max size limit" - yet there is nowhere where this is actually documented. What is the limit? is it a hard limit or is it based on the storage service, which then relies on their limit.?
The closest doc that talks about the 100TB/8TB limits for Database/Managed Inststance is here, however there is no detailed breakdown on what the limiting factors are.
https://docs.microsoft.com/en-us/azure/sql-database/sql-database-paas-vs-sql-server-iaas

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

ID: 528deb7f-fe1c-f2af-68b3-18d74eb570d4
Version Independent ID: 81880132-cf30-f913-3555-d78897f76611
Content: Azure SQL Database server resource limits
Content Source: articles/sql-database/sql-database-resource-limits-database-server.md
Service: sql-database
Sub-service: single-database
GitHub Login: @stevestein
Microsoft Alias: sstein

@dr-ivan Thank you for the feedback.
As you have rightly pointed, there is an open issue for adding a reference to the storage limits and will be addressed at the earliest.
We will close this issue now.
@stevestein closing this issue as it is a duplicate of #31200


Support for homePageUrl

At the moment eureka-js-client supports healthCheckUrl and statusPageUrl. I miss the support for homePageUrl. Are you interested in a PR that support that?
Eureka REST documentation: https://github.com/Netflix/eureka/wiki/Eureka-REST-operations

Thanks for the heads up! We currently POST the entire config.instance block on the register request. So, technically homePageUrl is already supported if you just add it to your config block. That being said, we do have some code around statusPageUrl and healthCheckUrl in the addInstanceMetadata method here that replaces the host key with the hostname from the AWS metadata, so maybe that's what you're referring to (this would only apply to AWS environments).
Would love a PR that updates that method to support homePageUrl and the README (just the configuration example). Thanks @danielbayerlein!

Thanks @danielbayerlein! Just published v4.1.0.


Distance page

Overview of the Pull Request:
Add the Distance page with updated logic which includes:

Changed content;
Special characters like 'e', 'E', '+', '-' are restricted;
The Save button is disabled unless User inputs a number;
'Google Maps' word - on click is redirecting user to https://www.google.com/maps ;
Once user clicks Next - he/she will be directed to Suggestions page;
Once user clicks Back- he/she will be directed to Confirm page;

link to Trello card or Github issue
Trello card - add 'Distance' page with updated logic and char limit
How Has This Been Tested?

Manual testing;

Pull Request Checklist:
Make sure the following checkboxes[ ] are checked with x before sending your PR -- thank you!

[x] Have you included a link Trello card / Github issue and written sufficient description to help others review your work?
[x] Is your pull request up-to-date with main branch?
[x] Have you checked That code is well formatted? Did npx prettier --check . return no warnings/errors?
[x] Have you written instructions on how to test that your changes work as expected?
[x] Have you tested your work thoroughly on your local machine to ensure you are not breaking anything?

Nice work Olga.

Can we direct the google map link to "https://www.google.com/maps/dir///@" page, where it prompt to user to input the location and destination.

Can we redirect the google map link to "https://www.google.com/maps/dir///@" page, where it prompt to user to input the location and destination. The link url can be hardcoded on the component href.

Good idea @Amutha37 , I didn't know that! 😄👍

Nice work @OlaShabalina !
I wasn't able to test using the preview deployment, that the previously entered (and saved) distance value would appear in the text box when a user revisits form/Distance page (probably because the Next button links to a non-existent page); but when I tested it locally (by updating the Next button link to an existing page), the distance value (previously entered by user) does appear in text box on form/Distance page :+1:


Support new AWS Europe (Zurich) Region eu-central-2

Hello!

Vote on this issue by adding a 👍 reaction
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details
eu-central-2 region was launched in November 2022. At the moment trying to use this region in Typescript results in a type error:

Type '"eu-central-2"' is not assignable to type 'Input | undefined'

Terraform provider has added support for the region: https://github.com/hashicorp/terraform-provider-aws/pull/27814
Workaround in Typescript: add // @ts-ignore

Thanks for the bug report @SijmenHuizenga! This was an oversight and should be fixed in the next release.


Can the MLServer runtime be replaced by Triton?

ModelMesh currently uses the MLServer runtime to serve sklearn, xgboost, and lightgbm models. However, it seems like recent versions of Triton now support all of those model types as well.
Does that mean that ModelMesh could support all types of models using a single runtime? And if so, would it be easy to change the adapter to handle this?

@OvervCW there shouldn't be anything stopping you using these other kinds of models with Triton, would be great if you could try it out!
Hopefully all that should be needed is to:

Update the triton-2.x ServingRuntime spec to include additional supportedModelFormats as needed
Reference the appropriate type in your Predictor and either specify the runtime name explicitly or delete/remove other runtimes like MLServer which also support the same type (or set autoSelect to false in the right places in those other runtimes)
Make sure to include a full Triton model configuration pbtxt file in the storage location that the Predictor's path points to (like this)

@rafvasq -- since you updated the Triton serving runtime last year, it might be worth trying this out and documenting it. WDYT?


Code tidy up

Coverage increased (+0.006%) to 95.385% when pulling 950834981b2ae3dd7ac1a83165b560c14afbd7af on lyncodev:master into 362d613329a45ff26dfc35c440f263638160fcb8 on jtwig:master.


added IDEAS to the list

Insert URLs to the project(s) here:
https://github.com/open-ideas/IDEAS
Explain what this list is about and why it should be included here:
IDEAS is an open source Modelica library that has been maintained and developed at the university of Leuven for over 10 years. It has been used in over 50 research papers. Its goal is to allow detailed and multi-disciplinary simulation and optimisation of building envelope models, including their Heating, Ventilation and air conditioning. Research topics relate to minimising the energy footprint of buildings.
The community behind OpenSustain.tech offers free marketing and consulting for open source projects added to the list. If you are interested just tick here:

[x]  Share the project on all available social media channels. ( Reddit, Twitter, Linkedin, HackerNews ).
[ ]  Collaborative blog post about the project with publication on OpenSustain.tech and OpenSource.com.
[x]  Get feedback on your project.
[ ]  Guidance on further development strategies and funding for the project.

A very interesting project and also highly topical, especially here in Germany. I don't have that much experience with Modelica but I will still give feedback on the project in general. Thanks for your contribution.


State parameter pre-defined options imported incorrectly

If you set some pre-defined options for parameter values (such as in this example state), they are accessed incorrectly in the behavior containing the state.
IE, the state itself would be imported as from flexbe_states_package.state_name import StateName in the behavior_name_sm.py file. But then the state's default parameters are accessed as flexbe_states_package.StateName.DefaultParameterName.
I think the fix is to just access the default parameters as StateName.DefaultParameterName.

It's caused by the value of the default parameter being set in the FlexBE App as package_name.StateName.DefaultParameterName when you click your desired parameter value from the drop-down options. So I guess when you click the drop down the parameter should be set to StateName.DefaultParameterName.

This actually depends on whether the state class name is a duplicate in the workspace or if the respective setting is enabled to consider the state package in addition to the class in general. Still, the completion you pointed out is incorrect in both cases.
The above commit fixes it for both of them.


Change Header Color

Hi Thanks for the wonderful package. I am successfully able to update the header TextStyle using the PlutoGridConfiguration. But I am unable to change the header background color. Is there any way to do so?

@arindammitra06
PlutoGrid version 2.9.3 has been distributed.
A property is added to change the background color of the column.
reference link
https://weblaze.dev/pluto_grid/build/web/#feature/column-group

background color changed but title text color not supported

@huongtran84
Please refer to the link below for column text color.
This can be changed with the titleSpan property.
https://github.com/bosskmk/pluto_grid/blob/master/lib/src/model/pluto_column.dart#L36

How to remove padding as image below?


missing show data on show views

dates of show, gallery address and show blurb (if available) should all be displayed

I assume that the copy and layout should look exactly the same as on martsy?

Yup! Except for the share button (Martsys looks slightly different)
Katarina

On Mar 26, 2015, at 9:04 AM, Eloy Durán<EMAIL_ADDRESS>wrote:
I assume that the copy and layout should look exactly the same as on martsy?
—
Reply to this email directly or view it on GitHub.

Aight 👌

more clarity for what a show in fair versus not in fair should look like


LOADPATH and cluster.pan.includes

When using ant, you have pan.loadpath and cluster.pan.includes. After reading the documentation, it still not very clear to me what these two do and how they can be combined? If I understood it correctly from @stdweird, you can 'prepend' search locations of cluster.pan.includes with pan.loadpath?
It would be nice if somebody could clarify the documentation a bit.

@wpoely86 they are combined in the following code where the filesystem lookup of the pan templates happens:
https://github.com/quattor/pan/blob/master/panc/src/main/java/org/quattor/pan/repository/FileSystemSourceRepositoryImpl.java#L63
(and empty string is always part of loadpath)
includedirs are set outside pan, loadpath inside pan (except for the ant variable, which has no equivalent on panc commandline)
also with loadpath, you cannot break out of the includedirs.
when includedirs are not orthogonal to the loadpaths, you can expect strange issues (but they are not bugs; the behaviour is 100% predictable)
what would you like to see clarified? you want an example how it works (and how it can go wrong? 😉

Some examples/guidelines how to (ab)use it would be nice.
For example, the empty string in loadpath: is it first or last or something else? I assume last?


output ontologies as JSONLD

Use tricks from https://github.com/gs1/EPCIS/tree/master/Ontology#conversion-to-jsonld.
make jsonld

invokes commands like this
ttl2jsonld CGMES-NC/ttl/SteadyStateInstruction-AP-Voc-RDFS2020.ttl | jsonld compact -c file://CIM-ontology-context.jsonld > CGMES-NC/jsonld/SteadyStateInstruction-AP-Voc-RDFS2020.jsonld

I check for JSON-LD irregularities with a command like this;
grep -h '       "@' */*/*.jsonld|perl -pe 's{^ +}{}' |sort|uniq -c

Here are the exceptions, with issue listed:

[ ] https://github.com/Sveino/Inst4CIM-KG/issues/108 IMPORTANT

      1 "@id": "cim:CurrentFlow"
      1 "@id": "cim:Frequency"
      4 "@id": "cim:Money"
      1 "@id": "cim:ReactivePower"
      2 "@id": "cim:RealEnergy"

[ ] https://github.com/Sveino/Inst4CIM-KG/issues/104

   4035 "@id": "uml:attribute"
    886 "@id": "uml:concrete"
    184 "@id": "uml:enumeration"
     53 "@id": "uml:ofAggregate"

[ ] https://github.com/Sveino/Inst4CIM-KG/issues/32: open question about theme: "vocabulary"@en

     43 "@language": "en",
     29 "@value": "vocabulary"

[x] fix09-map-qkUnitsMultipliers-38.ru had cim:UnitMultiplier.none 1.0 (decimal), now fixed to 1E0 (double)

     19 "@type": "xsd:decimal",
     19 "@value": "1.0"

[ ] https://github.com/Sveino/Inst4CIM-KG/issues/109

      1 "@value": "TapChangerControl"
      1 "@value": "TapChangerControlSchedule"
      2 "@value": "consumption"
      2 "@value": "export"
      2 "@value": "holiday"
      2 "@value": "import"
      2 "@value": "production"
      2 "@value": "storage"

This is largely done, see https://github.com/Sveino/Inst4CIM-KG/tree/develop/rdfs-improved/CGMES/jsonld.

Leaving it open and assigning to Svein and Chavdar for the subtasks (checkboxes) above.
Of them, https://github.com/Sveino/Inst4CIM-KG/issues/110 is most important

They are all posted as separate issues, so we may as well close this one.


Fix crash when executing PhysicsServer2D.joint_clear

Fixes #66607
Also changed some existing null checks for clearer error messages.

Thanks!


Bump module-deps to ^3.7.10

# 10.1.1

* Updates module-deps to ^3.7.10, which fixes an issue where under certain conditions the directory for a `package.json` would be attributed to the wrong package. [substack/module-deps#81](https://github.com/substack/module-deps/pull/81) (thanks @pmowrer)

The module-deps dependency is already set to ^3.7.7 so that seems unnecessary?

It's mostly for the changelog entry. What's a good way to let users know that there were relevant upstream fixes?

I think it's best if the relevant package (module-deps) handles that. Otherwise there's so much noise in the main project.

Ok cool. I'll start a changelog there.

Sounds good!


Newman's address stack is broken (handler priority bug)

When adding to NewmanLib.ADR_STACK (which controls, where a change form redirects after save), the from field is sometimes incorrectly set to the new address.
This looks like the handler that sends the page to the new address is called before the address stack is pushed to, so the information about where we come from is already lost.
The code involved is in

ella/newman/static/newman/js/related_lookup.js in function default_adrstack_push_callback
and ella/newman/static/newman/js/kobayashi.js in handlers commented // Set up event handlers

We should discuss personally what's causing this and where to fix it.

I have it fixed already, I'll push it when I push the mass uploader.


Create work experience presenter component

Release Type: Non-Breaking Feature
Fixes https://x-team-internal.atlassian.net/browse/XP-3735
Description
The WorkExperienceEntryPresenter component is fully implemented to render a single work experience entry for consumption on the admin dashboard. The basic framework for using InlineEditor to allow inline editing and creation of work experience entries is also in place, though the editor component is not coming until we finish XP-3736.
Stories are included for all possible prop combinations with the control.
Checklist

[x] set yourself as an assignee
[x] set appropriate labels for a PR (In Review or In Progress depending on its status)
[x] move respective JIRA issue to the PEER REVIEW column
[x] Flow typechecks passed (npm run flow)
[x] Snapshots tests passed (npm run jest) (NOTE: This is temporarily disabled. Skip it.)
[x] if added a new UI component that is meant to be used directly by other apps, remember to export that from the appropriate bundle file: src/index.js and/or src/registration.js
[x] component's documentation (.stories.js file) is changed or added accordingly to reflect any new or updated use cases and/or debug cases
[x] if any snapshots have been changed, verify that component still works and looks as expected and update the changed snapshot (NOTE: This is temporarily disabled. Skip it.)
[x] manually tested the app by running it in several different browsers (Firefox, Chrome, Opera, Safari, MS IE/Edge, etc.) and checked nothing is broken and operates as expected!

Steps to Test or Reproduce
Launch storybook with npm run start in xp-ui, then navigate to UI Controls > Work Experience > Presenter.
The three main scenarios are combinations of props which are required by spec. The various scenarios under "Debug" are there to handle missing props which hypothetically should never happen.
Impacted Areas in Application
XP Admin UI
Screenshots

Updated handling all of the comments.

@jaspax Please rebase to resolve merge conflicts and we should be ready to merge that 🚀 🎉

@nicksp Ready to push now 👍


Text prompt field should support multiline

When a user writes a text prompt, it should expand to multiline when the message exceeds the width of the field.

Closed with d82e58c4fbaec7137876f754b1e924d28c255361


GCS Writing multiple times does not work

Problem description
When I open a GCS bucket object and write multiple times only the data of the first write is stored in the object
The logs must show that it uploaded multiple parts (2+) like this INFO:smart_open.gcs:uploading part #2
Be sure your description clearly answers the following questions:

What are you trying to achieve?

I expect the file to be fully uploaded to the GCS

What are you seeing instead?
Only the first part was uploaded, usually part size is about 200 to 300 KB

Steps/code to reproduce the problem
import os
import io
import logging
from smart_open import open

logging.basicConfig(level=logging.INFO)

url = "gs://smart-open-784235/test-object"
size = 99 * 1024

data = io.BytesIO()
with open(url, "wb") as f:
    for _ in range(10):
        buffer = os.urandom(size)
        data.write(buffer)
        f.write(buffer)

data = bytes(data.getbuffer())
with open(url, "rb") as f:
    remote_data = f.read()

print("Local size:", len(data))
print("Remote size:", len(remote_data))

Output:
INFO:smart_open.gcs:uploading part #1, 304128 bytes (total 0.000GB)
INFO:smart_open.gcs:uploading part #2, 304128 bytes (total 0.001GB)
INFO:smart_open.gcs:uploading part #3, 304128 bytes (total 0.001GB)
INFO:smart_open.gcs:uploading part #4, 101376 bytes (total 0.001GB)
INFO:google.resumable_media.requests.download:No MD5 checksum was returned from the service while downloading https://storage.googleapis.com/download/storage/v1/b/smart-open-784235/o/test-object?generation=1581104519907572&alt=media
(which happens for composite objects), so client-side content integrity
checking is not being performed.
Local size: 1013760
Remote size: 304128

Versions
Linux-5.4.13-201.fc31.x86_64-x86_64-with-fedora-31-Thirty_One
Python 3.7.6 (default, Dec 19 2019, 22:52:49)
[GCC 9.2.1 20190827 (Red Hat 9.2.1-1)]
smart_open 1.9.0
I have downloaded smart-open from github yesterday and used it instead of the repo version as there is not GCS support in the repos
The latest commit at the time of download was https://github.com/RaRe-Technologies/smart_open/commit/72818ca6d3a0a99e1717ab31db72bf109ac5ce65
Checklist
Before you create the issue, please make sure you have:

[x] Described the problem clearly
[x] Provided a minimal reproducible example, including any required data
[x] Provided the version numbers of the relevant software

Thanks for reporting this. It looks like I made some mistakes with the multipart uploading that I'll try to fix this week.

Thank you very much, very much appreciated.


Remove gulp-jsbeautifier from blacklist

gulp-jsbeautifier has been blacklisted as duplicate of gulp-beautify.
Both are wrappers for js-beautify but gulp-jsbeautifier has more features then gulp-beautify.
gulp-beautify works only for javascripts while gulp-jsbeautifier also works for css and html (like js-beautify).

/cc @contra

Closing this because the plugin page has been rewritten and integrated with our main website: https://github.com/gulpjs/gulpjs.github.io
The blacklist isn't currently applied to the new plugin page. It is still used by --verify but that might change soon.


ライセンスの更新

Looks like this was created by accident, closing. If needed, feel free to reopen with more details, thank you!