[Idea: JS] Add way to detect react-native (and platform) without require().

Motivation
I have a 3rd-party library that needs to work in react-native (as well as node.js, web, etc.).  I want to detect when it's used in react-native, for analytics purposes.  I can't use require('react-native') or similar because if somebody uses my library with a tool like browserify, it will try to statically satisfy all require() statements and fail on react-native.
Suggestion

Set navigator.product to 'ReactNative' (it is currently 'Gecko')
Set navigator.platform to 'iPhone', 'iPad', or 'Android' as appropriate (it is currently 'MacIntel', at least in the iOS emulator).

Implementing
Code in question is here: https://github.com/facebook/react-native/blob/0fbe0913042e314345f6a033a3681372c741466b/Libraries/JavaScriptAppEngine/Initialization/InitializeJavaScriptAppEngine.js#L114
Related IRC Conversation: https://gist.github.com/mikelehen/822a82a37bf30431a104

I expect that navigator.platform is already something reasonable on device; I don't think we set it. Setting navigator.product sounds somewhat reasonable though…

I'd be fine with dropping the .platform part.  Somebody on IRC had mentioned it.

Proposal to move things forward: navigator.product returns "ReactNative" and navigator.productSub returns the version e.g. "0.5.0". This is a little different than browsers, which return "Gecko" and "20030107" but we'd be returning useful values in this case.
Relevant docs:
https://developer.mozilla.org/en-US/docs/Web/API/NavigatorID/product
https://developer.mozilla.org/en-US/docs/Web/API/Navigator/productSub

FWIW, @ide's proposal would definitely work for our use case.

@spicyj @ide I have doubts that attaching something to the navigator will work in the chrome debugger,  if we go ahead with the decision to run the chrome debugger in a worker (#1632 and #1473).  The code within the worker doesn't have access to window, but just to the worker's own scope, which has I believe a different navigator. See the web worker's context api.

That sounds preferable actually. We don't want any of the browser environment to leak into React Native's environment ideally.

+1 for this idea

It appears that attaching something to navigator is not going to work because navigator is read-only in webworkers. Does anyone have any other ideas on how to determine if code is running under react-native?

@mikelehen It seems that this idea is a nonstarter for the foreseeable future. Have you considered modifying the Firebase API to allow developers to tell you they're running under react-native?
I think an API change will be necessary anyway, because web code that relies on getAuth() being synchronous will probably break. There needs to be a way to pass a callback, either by an optional param to getAuth(), or adding a new call, say getAuthAsync(), to provide the asynchronous return value.
If a developer uses that API point, they're telling you they're using react-native. What do you say?

One thing we agreed on is to add a package.json rule called "react-native" that's going to let you change the root entry point of your module when npm install. The same way browserify, webpack and react-native support the "browser" field.
No one is working on it right now but if someone wants to send a diff i'll happily stamp it.

@vjeux this PR adds the react-native field: https://github.com/facebook/react-native/pull/2208

@chetstone Eh.  I'm not excited about adding an API to indicate you're using React Native.  It really needs to just work.  FWIW, we already have an onAuth() method that's an async notification for auth status, so I'm not too worried about that.  Astute observation about getAuth() though. :-)
The "react-native" package.json rule would actually work for us if that gets in.  It's a pretty heavy-handed solution (we'll essentially just duplicate our "browser" client but add "var REACT_NATIVE = true;"), but whatever.

I'd really need this as well. Is there a workaround-ish way today/now to check for react native? Preferably one which is not expected to break in the future?

@zsszatmari For library developers, probably not. For app developers, what I do is
var { Web } = require('../config/globals')
Then in globals.web.js I export Web = true and in globals.ios.js export Web = false
RN packager will pick up the .ios.js file if you're building for that platform. I use webpack for building the web app, so in my webpack.config I have
  resolve: {
    extensions: ['', '.web.js', '.js', '.jsx']
  },

so webpack will pick up the .web.js file.

Object.defineProperty works for setting navigator.product in Chrome (and should work in pure JSC, but not Safari), and @tadeuzagallo just killed the UIWebViewExecutor, so I think we can make navigator.product work. Would anyone like to send a PR?

I could maybe take a stab at it, but I have a couple of questions. First, what is UIWebViewExecutor and why is it relevant to setting a navigator property? I searched the issues but could not find any reference.
Second, is it OK if it doesn't work in Safari? @mikelehen you say it should just work. It could be confusing to devs if something fails in Safari. Perhaps the package.json fix would be more robust for you.

The web view executor used a UIWebView to run the JS. In Safari, though, you can't use defineProperty to set navigator.product because it is marked as non-configurable. But now the only two executors we have are JSC and Chrome.

So that means it doesn't matter if the navigator.product can't be set in Safari since we can't debug in Safari anyway (Debug in Safari has been removed from the "shake" menu?)

Yeah

BUMP!
@chetstone what happened to your good intention?

Fixed in 3c65e62183ce05893be0822da217cb803b121c61


alignment of paragraphs in a table unchangeable if set earlier in the table style

Setting an alignment property on a ParagraphFormat object of a table style (I tested with WD_ALIGN_PARAGRAPH.LEFT) renders other alignment values unusable on table paragraphs afterwards. If, for instance, you set each paragraph to WD_ALIGN_PARAGRAPH.RIGHT while populating the table with content (say you'd like one column to be aligned differently than the others) it's still aligned to the left in LibreOffice.
That of course forces the user to unset it in the table style and align each paragraph individually, thus voiding the purpose of having the style in the first place.

Hi @ThreefoldBurly, can you provide a snippet of code to reproduce this?
Also, if you could send a document showing this behavior that would be a big help in diagnosis, perhaps the one generated by the code snippet.

It appears LibreOffice (LO) is behaving rather badly in this case, perhaps as a compromise related to preferring ODF format.
It looks like LO takes all the table style value and applies them directly to each element of the table, including paragraphs in this case, where they overwrite whatever was applied directly. This has the additional implication that it effectively interrupts the style inheritance hierarchy for tables.
There's unfortunately nothing to be done on the python-docx side to remedy this. python-docx faithfully writes the <w:jc w:val="right'/> element on the paragraphs in question here, only to have that overwritten by LO Writer when it opens the file.
The only solution I can see is to avoid using a table style or to open the file in LO and let it have its way, and then adjust the file afterward to make the desired settings. I'd be inclined to prefer the former. I'm not sure LO wouldn't just overwrite custom settings again next time the file was opened if you took the latter approach.
You could avoid using a table style in cases where additional customization was required by applying all the formatting directly to the table elements after it was created; basically the same approach LO is taking.

Applying all formatting directly - that's exactly what I did to circumvent it. Thanks a lot for clearing this up. It's not gonna be much of a problem for me, if it's all LO's fault, because actually the files I generate with the python script I'm working on are to be used with MS Word. I just happen to prefer Linux as my development environment.


[Java] mavencentral jars do not ship with libarrow_cdata_jni binding for linux/aarch64

Describe the bug, including details regarding any error messages, version, and platform.
Attempting to use the CData interface from java on linux/aarch64 fails with an exception on recent versions when using the maven central distributions:
java.lang.IllegalStateException: error loading native libraries: java.io.FileNotFoundException: aarch_64/libarrow_cdata_jni.so
Works just fine on mac (m1).
Appears the mavencentral distribution does not include the .so file for aarch64 (it does for x86).

Looks gandiva and dataset jars on mavencentral also do not have distributions with these.
Component(s)
Java

We need to build aarch64 binaries by https://github.com/apache/arrow/blob/947a446c51b685debaf1a19e7c5f91e8e0bd09e4/dev/tasks/java-jars/github.yml#L24-L50
We can use self-hosted aarch64 runner for it: https://github.com/apache/arrow/blob/947a446c51b685debaf1a19e7c5f91e8e0bd09e4/dev/tasks/linux-packages/github.linux.yml#L28

Took a stab at this here: https://github.com/apache/arrow/pull/36487.
My main concern is pushing the Docker image for both aarch64 and x86, but I likely also do not fully understand the implications of everything I'm changing here.


Setup Gatsby boilerplate

Create boilerplate and deploy to test environment with build
https://www.gatsbyjs.org/docs/recipes/

https://hardcore-austin-e75e1d.netlify.com


Rename zenith to neon in python tests

This will break continuity of perf reports since tests are renamed. Better early than later though.
We could mark tests with unique ids which will also allow us to explicitly break continuity without changing names, when the test significantly changes. But this seems too fancy for now.

Thanks for the work 💪 .

Revert envvar changes

I think we only use ZENITH_PAGESERVER_OVERRIDES in tests (specifcally test_remote_storage), so it's safe to rename it to neon.
Regarding ZENITH_BIN, the problem is that we initialize the circle CI files in https://github.com/neondatabase/neon/blob/main/.circleci/config.yml#L160-L167. The failed tests can be fixed by modifying those lines.

This will break continuity of perf reports since tests are renamed. Better early than later though.

One thing I realized recently is that there are many legacy tests, e.g. test_bulk_insert.py::test_bulk_insert, which haven't been updated for a long time. Those tests are deprecated because we add [vanilla] and [zenith] suffixes.


sprite-sheet-packer does not support cocos2d V2

sprite-sheet-packer does not support cocos2d V2 since the tag  sourceColorRect does not appear in the output xml file.
Please help.
Thanks

Sorry, I didn't find the tag sourceColorRect in cocos2d-x source

Try to use cocos2d-old format


Host package on pypi

Hi there, it would be really nice to see and use this lib from pypi.
This PR includes a setup.py script for installation using setuptools.
To install locally:
cd aproximated_ged
pip install -e . # might require sudo

Once on pip
pip install aproximated_ged

release.sh can be used to release this package onto pypi, with your pypi account credentials which the script will prompt.
Involves a directory structure changed to convert it into a python package.
Involves package import path changes, e.g. from VanillaHED import * -> from .VanillaHED import *
Also if you'd prefer travis as well, gimme a mention in the comments.

Thank you @ixaxaar, I was not able to test  until today. I will try to write a proper Readme as soon as possible explaining better the use of the classes. Can you explain me a little bit how pypi works to release the package?

So all you have to do is register on pypi and have a username and password that release.sh will ask during release. Pypi is basically just a repository, so you need an account to upload to that repo, and pip downloads from that repo.
Now, if you'd like to go into exactly how the entire release process goes this is all that I had referred and know. Its not THAT esoteric or difficult, just a lot of config :grimacing:


Update mapcontrol_tryzoominasync_1251712457.md

Reference Min/MaxZoomLevel properties, so it doesn't appear that you're supposed to hard-code the constants into your code.

@jwmsft The PR passed the acceptance checklist. Please evaluate further and approve/complete the PR if appropriate. Thanks!


IF statements not supported

IF/THEN/ELSE was listed as supported, but the "Language elements" section also says control-of-flow statements are not supported. Actually running a query using IF gives an error, e.g.
if @@rowcount = 0
begin
  select top 10 name from account
end

gives:
Msg 40000, Level 16, State 1, Line 15
'IF' statement is not supported. Line:1, Position:1

Waiting for internal feedback.

@MarkMpn
Mark; The documentation is correct. You are combining if and BEGIN which is control of flow.
For example this statement works. Basically user can only use if within the SQL statement context. Not with statement blocks.
IF DATENAME(weekday, GETDATE()) IN (N'Saturday', N'Sunday')
SELECT 'Weekend';
ELSE
SELECT 'Weekday';
Rich

Strangely your example does work, but if I change the SELECT statement to use reference a table I get the original error indicating that IF is not supported:
IF DATENAME(weekday, GETDATE()) IN (N'Saturday', N'Sunday')
  SELECT top 10 name FROM account;
ELSE
  SELECT top 10 fullname FROM contact;

returns:
Msg 40000, Level 16, State 1, Line 1
'IF' statement is not supported. Line:2, Position:1
RequestId: TDS;d983ad5f-723b-43b5-b141-b90120b1eb89;32
Time: 2022-07-01T19:08:51.2056133Z


Add Fuses for SOC Manifest

This request is for adding the following fuses:

SOC Manifest Max SVN (4 Bytes): This indicates what the supported max SVN is.
SOC Manifest SVN (16 Bytes): This is a one-hot encoded fuse indicating the actual SVN.

@mhatrevi Please update the main spec with this info, then we will apply the change to caliptra-rtl.


Support OpenAI compatible API using ChatOpenAI

I want to configure some OpenAI compatible API, but i found most of them are using /v1/chat/completions which is wrapped as ChatOpenAI in langchain.

ollama
lingyiwanwu
kimi (moonshot)

Maybe change to use ChatOpenAI can help this~
  const model = new ChatOpenAI(
    {
      model: modelName,
      apiKey,
      streaming: false,
    },
    {
      basePath,
    }
  );

I forked a demo https://github.com/ahonn/logseq-plugin-ai-assistant/compare/master...Anddd7:logseq-plugin-ai-assistant:master?diff=split&w=

Look great! Could you please raise a PR for this? I would be happy to merge.


Newly added  Events disappears when changing month

When I add new events to the calendar after the calendar already has been loaded, they are being added like they shall. But when I am switching the month forward and afterwards backwards, the event has disappeared. I think the same thing is happening in your demo.
What to do?
Thanks very much in advance.

I have same problem.....

Adding new events issue
When adding new events to the calendar they can disappear when switching months. To solve this add stick: true to the event object being added to the scope.

@jhgil Thanks very much for sharing the solution with me! It Works :-)

https://fullcalendar.io/docs/event_rendering/renderEvent/
var event = new Object();
event.id = 123; // unique event id;
event.title = 'some title';
event.start = new Date(2017,11,4, 00, 00);
event.end = new Date(2017,11,6,00,00);
$('#calendar').fullCalendar( 'renderEvent', event, true ); // 3rd parameter is - `stick: true`

guys, the thing is when my page initially is loaded all my events from the database are shown
after I add an event I'm inserting into the DB removing the events then refetching works like a charm to remove duplicate data but when I press the previous and the next button the only thing that will appear is the last event rendered in the calendar all the rest are gone and I'm using stick true

I am adding stick: true to the event object and it all it does is disables the arrow buttons to go to next and previous months. I still want to be able to look at other months but also keep my events rendered.

Adding new events issue

When adding new events to the calendar they can disappear when switching months. To solve this add

stick: true to the event object being added to the scope.

You're the best

https://fullcalendar.io/docs/event_rendering/renderEvent/
I did this in jQuery and it works. May be, this code can help someone.
var event = new Object();
event.id = 123; // unique event id;
event.title = 'some title';
event.start = new Date(2017,11,4, 00, 00);
event.end = new Date(2017,11,6,00,00);
$('#calendar').fullCalendar( 'renderEvent', event, true );
// 3rd parameter is - `stick: true`

you saved my time, thanks bro.

Confirmed that "true" for the sticky flag works. Thanks.


[QUESTION] cannot export on live server

Prerequisites
Versions

PHP version: 7.2
Laravel version: 5.8
Package version: 3.1

Description
Exporting seems to be working fine on my local machine but doesn't seem to work on my live server (running ubuntu). I have verified that zip, xml, as well as the gd extensions are enabled through the php -m command. The route that acts as a trigger for the download also returns a 200 response so I'm not really sure where to look.
Edit: A friend had helped me out and suggested to look at the response headers which I did and it turns out on my live server the Content-Type response header is set to text/html while on my local machine it is application/vnd.openxmlformats-officedocument.spreadsheetml.sheet. I am currently trying to figure out how I can set the response headers upon download of the file.
Additional Information
I am using XAMPP on my local machine. Nothing is changed. I am using the default settings. While on my live server, I am using nginx as my web server.

Silly me. The problem turned out to be just a simple unpublished file (routes/web.php).


More information on the error "output location does not exist in template.parameters"

We are running:
PS Test-AzTemplate -TemplatePath D:\Documents\ARMTest
the ARMTest file:
ARMTest
{
"$schema": "https://schema.management.azure.com/schemas/0.1.2-preview/CreateUIDefinition.MultiVm.json#",
"handler": "Microsoft.Azure.CreateUIDef",
"version": "0.1.2-preview",
"parameters": {
"outputs": {
"location": {
"type": "string",
"defaultValue": "[resourceGroup().location]"
},
"location": "[location()]"
}
}
}
and receiving this error:
Outputs Must Be Present In Template Parameters
[-] Outputs Must Be Present In Template Parameters (4 ms)
output location does not exist in template.parameters
Can the team provide more information on how to resolve this error ? thank you

I read the doc (https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/createuidefinition-test-cases#include-control-outputs-in-template-parameters)  and found a way to resolve the problem.  Yup, read the doc :)
Hit other issues and used this doc to find errors in the other json files.
https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/template-test-cases
Screenshot mapping my ttk error output to the doc that helped w/ resolution at:

Ok, sounds like you made the connection - I'll close the issue, feel free to reopen if needed.


Provide a way to specify default theme for printing

Duplicates

[X] I have searched the existing issues

Latest version

[x] I have tested the latest version

Summary 💡
In my app, I have support for light and dark themes.
When I initiate printing with window.print() I want the default light theme to be used regardless if the current displed theme is dark or light.
I tried to work around this by using useMediaQuery('print') and setting the theme to light but it does not work with window.print() only on Ctrl+P.
I also tried experimental CssVariables color schemas and if you would add the ability to specify media property for injected global stylesheets that may solve the issue.
Examples 🌈
No response
Motivation 🔦
It does not make sense to print pages on a dark theme because you will use a lot of ink for printing.

I also tried beforeprint, afterprint events with a combination of ReactDOM.flushSync API, but that creates unintentional effects:
Chrome: when the actual page also changes the theme to light after the print preview window appears and until it closes
Safari: theme flickering after print preview window closes
Ideally those @media print { } styles should be already on the page.

Could you share a minimal reproduction with CodeSandbox?


[BUG] NodeUnpublishVolume break for-loop too early to clean all the corrupted mount points

What is your environment(Kubernetes version, Fluid version, etc.)
Fluid 1.0
Describe the bug
When there are multiple corrupted mount points on a fluid volume's targetPath (This should be common when enabling FUSE Recovery feature), it is Fluid CSI Plugin's responsibility to umount all the corrupted mount points in func NodeUnpublishVolume. However, the codebase now returns early without umounting all of them.
A brief go-through of the code:

csi plugin checks if targetPath is likely a mount point. If the targetPath is a corrupted mount point, the func returns true(notMount) and corruptedErr(err). (code)
For corruptedErr, we only log such case and keep going down. (code)
For notMount == true, csi plugin thinks its work is done. But actually there might be multiple corrupted mount points on targetPath (code)
Finally, csi plugin calls func CleanupMountPoint and umount once with other corrupted mount points still left.

Luckily, all the corrupted mount points will eventually umounted because kubelet retries. For example, when tearing down a targetPath with 3 corrupted mount points, kubelet reports like:
Jul 02 17:58:56 iZ2zec8bxibjv02csp8chtZ kubelet[2656]: E0702 17:58:56.346277    2656 nestedpendingoperations.go:348] Operation for "{volumeName:kubernetes.io/csi/fuse.csi.fluid.io^default-demo podName:5309cb53-14cd-420c-bc4a-75d9dc31e759 nodeName:}" failed. No retries permitted until 2024-07-02 17:58:56.846259243 +0800 CST m=+2149126.490387342 (durationBeforeRetry 500ms). Error: UnmountVolume.TearDown failed for volume "data-vol" (UniqueName: "kubernetes.io/csi/fuse.csi.fluid.io^default-demo") pod "5309cb53-14cd-420c-bc4a-75d9dc31e759" (UID: "5309cb53-14cd-420c-bc4a-75d9dc31e759") : kubernetes.io/csi: Unmounter.TearDownAt failed: rpc error: code = Internal desc = NodeUnpublishVolume: failed when cleanupMountPoint on path /var/lib/kubelet/pods/5309cb53-14cd-420c-bc4a-75d9dc31e759/volumes/kubernetes.io~csi/default-demo/mount: stat /var/lib/kubelet/pods/5309cb53-14cd-420c-bc4a-75d9dc31e759/volumes/kubernetes.io~csi/default-demo/mount: transport endpoint is not connected
Jul 02 17:58:56 iZ2zec8bxibjv02csp8chtZ kubelet[2656]: E0702 17:58:56.848552    2656 nestedpendingoperations.go:348] Operation for "{volumeName:kubernetes.io/csi/fuse.csi.fluid.io^default-demo podName:5309cb53-14cd-420c-bc4a-75d9dc31e759 nodeName:}" failed. No retries permitted until 2024-07-02 17:58:57.848525874 +0800 CST m=+2149127.492653986 (durationBeforeRetry 1s). Error: UnmountVolume.TearDown failed for volume "data-vol" (UniqueName: "kubernetes.io/csi/fuse.csi.fluid.io^default-demo") pod "5309cb53-14cd-420c-bc4a-75d9dc31e759" (UID: "5309cb53-14cd-420c-bc4a-75d9dc31e759") : kubernetes.io/csi: Unmounter.TearDownAt failed: rpc error: code = Internal desc = NodeUnpublishVolume: failed when cleanupMountPoint on path /var/lib/kubelet/pods/5309cb53-14cd-420c-bc4a-75d9dc31e759/volumes/kubernetes.io~csi/default-demo/mount: stat /var/lib/kubelet/pods/5309cb53-14cd-420c-bc4a-75d9dc31e759/volumes/kubernetes.io~csi/default-demo/mount: transport endpoint is not connected
Jul 02 17:58:57 iZ2zec8bxibjv02csp8chtZ kubelet[2656]: E0702 17:58:57.855291    2656 nestedpendingoperations.go:348] Operation for "{volumeName:kubernetes.io/csi/fuse.csi.fluid.io^default-demo podName:5309cb53-14cd-420c-bc4a-75d9dc31e759 nodeName:}" failed. No retries permitted until 2024-07-02 17:58:59.855273142 +0800 CST m=+2149129.499401242 (durationBeforeRetry 2s). Error: UnmountVolume.TearDown failed for volume "data-vol" (UniqueName: "kubernetes.io/csi/fuse.csi.fluid.io^default-demo") pod "5309cb53-14cd-420c-bc4a-75d9dc31e759" (UID: "5309cb53-14cd-420c-bc4a-75d9dc31e759") : kubernetes.io/csi: Unmounter.TearDownAt failed: rpc error: code = Internal desc = NodeUnpublishVolume: failed when cleanupMountPoint on path /var/lib/kubelet/pods/5309cb53-14cd-420c-bc4a-75d9dc31e759/volumes/kubernetes.io~csi/default-demo/mount: stat /var/lib/kubelet/pods/5309cb53-14cd-420c-bc4a-75d9dc31e759/volumes/kubernetes.io~csi/default-demo/mount: transport endpoint is not connected
Jul 02 17:58:59 iZ2zec8bxibjv02csp8chtZ kubelet[2656]: I0702 17:58:59.869373    2656 operation_generator.go:888] UnmountVolume.TearDown succeeded for volume "kubernetes.io/csi/fuse.csi.fluid.io^default-demo" (OuterVolumeSpecName: "data-vol") pod "5309cb53-14cd-420c-bc4a-75d9dc31e759" (UID: "5309cb53-14cd-420c-bc4a-75d9dc31e759"). InnerVolumeSpecName "default-demo". PluginName "kubernetes.io/csi", VolumeGidValue ""

What you expect to happen:
This logic can be optimized by checking corrupted mount points when calling func NodeUnpublishVolume
How to reproduce it

enable FUSE Recovery
delete FUSE Pod some times
delete app pod and check Fluid CSI Plugin's logs.

Additional Information

/assign @TrafalgarZZZ


[1.14.3] Crash when using items

steps to reproduce

install this mod
start the game
use another mod item
crash

crashlog: crashlog

Fixed in f52ce33. Thanks for reporting!


spacy-pkuseg 1.0.0

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

References:

includes #20
(maybe) unblocks https://github.com/conda-forge/spacy-models-feedstock/pull/7

Changes:

conda-forge.yml

add osx-arm64
add bot inspection for future PRs
use azure

.ci_support

add manual numpy2 migration

meta.yaml

remove all jinja vars except version
update pip and pytest invocations
remove cython runtime dep, per https://github.com/conda-forge/spacy-pkuseg-feedstock/pull/11#issuecomment-1120694041

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

Hi! This is the friendly automated conda-forge-webservice.
I tried to rerender for you, but it looks like there was nothing to do.
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12090697238. Examine the logs at this URL for more detail.

@conda-forge-admin please rerender

Hi! This is the friendly automated conda-forge-webservice.
I tried to rerender for you, but it looks like there was nothing to do.
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12090896387. Examine the logs at this URL for more detail.

Thanks @bollwyvl! I'm going to merge this to unblock spacy-models (given how all of that has been blocked for months already), but I'll add @conda-forge/spacy here as a maintainer, and if you'd be willing to join that team, that'd be great!


Update list variable when watching for array changes

In 5c6630b1899af38f1a302454ef87e40b600a0888, watching of arrays was refactored to remove a call to sfSelect, however in the process the list variable stopped getting updated. This led to adverse behaviour when adding new array items in the editor due to list and scope.modelArray being out of sync. This PR ensures the list variable is kept in sync with scope.modelArray when the array changes.

Oh, I didn't realize I broke something! Thank you @lukebennett


Missing Social Icons

Issue Summary
Hello
I found an issue in our website in which social icons are missing for a all  device.
In your Code i see 16 social icon but in display max tot max only 14 on large screen and for small device minimum show only 2 icon .
please you can check it . it want to work on this issue please assign me

Steps to Reproduce
change only css
Ghost Version
5.0
Node.js Version
20v.6.1
How did you install Ghost?
npm install ghost-cli -g
Database type
Other
Browser & OS version
firefox
Relevant log / error output
No response
Code of Conduct

[X] I agree to be friendly and polite to people in this repository

This is not within the Ghost product


Sudden e2e test failures in 2 tests

2 of the e2e tests are consistently failing right now. The cause doesn't seem to be related to a code change, as older versions are also failing now.
E2E TEST:CI-Tests E2E TEST:Validating use of CI tests [It] Should return absence of CI tests in a repo with unsquashed merges

  Captured StdOut/StdErr Output >>
  2023/06/06 09:53:01 CI tests run:   utests.TestReturn{
        ... // 2 identical fields
        NumberOfWarn:  0,
        NumberOfInfo:  0,
  -     NumberOfDebug: 12,
  +     NumberOfDebug: 10,
    }

E2E TEST PAT: scorecard-attestor policy E2E TEST:Validating scorecard attestation policy [It] Should attest to repos based on policy
...
  time="2023-06-06T09:53:54-07:00" level=info msg="Running scorecard on https://github.com/ossf/scorecard"
  time="2023-06-06T09:53:57-07:00" level=info msg="no code reviews linked to unknown(e38c00afd9a6d6cc28510cc571b060812ba1bc68)"
  time="2023-06-06T09:53:57-07:00" level=info msg="not enough approvals for unknown(e38c00afd9a6d6cc28510cc571b060812ba1bc68) (needed:1 found:0)"
  time="2023-06-06T09:53:57-07:00" level=info msg="image failed scorecard attestation policy check"

Using this commit as an example,  the REST (and graphql) API do not (but previously did) return the associated pull request (#2471), causing the two checks to fail. https://api.github.com/repos/ossf/scorecard/commits/e38c00afd9a6d6cc28510cc571b060812ba1bc68/pulls
This isn't happening everywhere though, as running scorecard on ossf/scorecard is showing a 10/10 for code-review.

Seemed to have resolved itself, as the API call is returning associated pull request info again. I'm curious if it was related to this pull request incident:
https://www.githubstatus.com/incidents/1g1gkh0qpyvs


CLOUDSTACK-8485: listAPIs are taking too long to return results

Removed regex. based search/replace of sensitive data on API response introduced as part of commit b0c6d4734724358df97b6fa4d8c5beb0f447745e
Added new response serializer to skip sensitive data from getting logged based on annotation present in resposne object fields
Added annotation (@LogLevel(Log4jLevel.Off)) to sensitive response object fields

Ran the following tests on simulator:
test_vm_life_cycle.py
Test advanced zone virtual router ... === TestName: test_advZoneVirtualRouter | Status : SUCCESS ===
ok
Test Deploy Virtual Machine ... === TestName: test_deploy_vm | Status : SUCCESS ===
ok
Test Multiple Deploy Virtual Machine ... === TestName: test_deploy_vm_multiple | Status : SUCCESS ===
ok
Test Stop Virtual Machine ... === TestName: test_01_stop_vm | Status : SUCCESS ===
ok
Test Start Virtual Machine ... === TestName: test_02_start_vm | Status : SUCCESS ===
ok
Test Reboot Virtual Machine ... === TestName: test_03_reboot_vm | Status : SUCCESS ===
ok
Test destroy Virtual Machine ... === TestName: test_06_destroy_vm | Status : SUCCESS ===
ok
Test recover Virtual Machine ... === TestName: test_07_restore_vm | Status : SUCCESS ===
ok
Test migrate VM ... === TestName: test_08_migrate_vm | Status : SUCCESS ===
ok
Test destroy(expunge) Virtual Machine ... === TestName: test_09_expunge_vm | Status : SUCCESS ===
ok

Ran 10 tests in 306.429s
OK
test_volumes.py
Download a Volume attached to a VM ... === TestName: test_03_download_attached_volume | Status : SUCCESS ===
ok
Delete a Volume attached to a VM ... === TestName: test_04_delete_attached_volume | Status : SUCCESS ===
ok
Detach a Volume attached to a VM ... === TestName: test_05_detach_volume | Status : SUCCESS ===
ok
Delete a Volume unattached to an VM ... === TestName: test_09_delete_detached_volume | Status : SUCCESS ===
ok

Ran 4 tests in 184.132s
OK
test_network.py
Test for delete account ... === TestName: test_delete_account | Status : SUCCESS ===
ok
Test for Associate/Disassociate public IP address for admin account ... === TestName: test_public_ip_admin_account | Status : SUCCESS ===
ok
Test for Associate/Disassociate public IP address for user account ... === TestName: test_public_ip_user_account | Status : SUCCESS ===
ok
Test for release public IP address ... === TestName: test_releaseIP | Status : SUCCESS ===
ok

Ran 4 tests in 783.726s
OK
test_routers.py
Test router internal advanced zone ... SKIP: Marvin configuration has no host credentials                            to check router services
Test restart network ... === TestName: test_03_restart_network_cleanup | Status : SUCCESS ===
ok
Test router basic setup ... === TestName: test_05_router_basic | Status : SUCCESS ===
ok
Test router advanced setup ... === TestName: test_06_router_advanced | Status : SUCCESS ===
ok
Test stop router ... === TestName: test_07_stop_router | Status : SUCCESS ===
ok
Test start router ... === TestName: test_08_start_router | Status : SUCCESS ===
ok
Test reboot router ... === TestName: test_09_reboot_router | Status : SUCCESS ===
ok

Ran 7 tests in 42.958s
OK (SKIP=1)
test_global_settings.py
test update configuration setting at zone level scope ... === TestName: test_UpdateConfigParamWithScope | Status : SUCCESS ===
ok

Ran 1 test in 0.127s
OK
test_resource_detail.py
Test volume detail ... === TestName: test_01_updatevolumedetail | Status : SUCCESS ===
ok

Ran 1 test in 11.492s
OK

I have tried to look for the existing API response objects based on some keyword search for sensitive fields. Please let me know if some response objects are left out.

registerUserKeys log based on this change
2015-11-02 17:15:19,061 INFO  [a.c.c.a.ApiServer]<PHONE_NUMBER>@qtp-678426242-0:ctx-608cad64 ctx-6e00b6fc) (logid:bfb12e9d) (userId=2 accountId=2 sessionId=9g6dq5sjxlk7137t68hfkux8) 0:0:0:0:0:0:0:1 -- GET command=registerUserKeys&response=json&id=e2fdf8e4-73be-11e5-8882-249684d59f9c&_=1446464718702 200 {"registeruserkeysresponse":{"userkeys":{}}}

Jenkins build failed with the following error. I saw some other PRs with the same failure. So looks like some random issue.
[ERROR] SLF4J: Class path contains multiple SLF4J bindings.

@koushik-das I've seen it before and the actual error message is
#
# A fatal error has been detected by the Java Runtime Environment:
#
SUREFIRE-859: #  SIGSEGV (0xb) at pc=0xada0752c, pid=22300, tid=4136188736
#
# JRE version: 7.0_25-b15
# Java VM: Java HotSpot(TM) Server VM (23.25-b01 mixed mode linux-x86 )
# Problematic frame:
# C  [libnet.so+0x352c]  _init+0x620
#
SUREFIRE-859: # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/jenkins/jenkins-slave/workspace/cloudstack-pull-analysis/server/hs_err_pid22300.log
#
SUREFIRE-859: # If you would like to submit a bug report, please visit:
#   http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

I think java needs updating on the slave (or we need to reconfigure the job to use a better version)

Usage of @LogLevel(Log4jLevel.Off) seems inappropriate to avoid logging sensitive information, why not still check the sensitive param/annotation to log or not log data?

@bhaisaab What are your reasons for saying that @LogLevel(Log4jLevel.Off) is inappropriate?
By sensitive param/annotation are you referring to the existing @APICommand annotation params requestHasSensitiveInfo/responseHasSensitiveInfo? The problem with this approach is that it doesn't tell about the specific field which is sensitive and so the entire response needs to be searched for sensitive data by means of regex which is very bad in terms of performance.

@bhaisaab @koushik-das Isn't there an annotation on field level for APIs as well? A change was accepted for that. I am looking for it and will update this comment.

@DaanHoogland @bhaisaab I also couldn't find any annotation on API fields for this. So ended up using the LogLevel which is also used in the agent commands.

The field level annotation was discussed as a prefered solution but in the end a regexp on field names was used. I am fine with re-using the LogLevel annotation. It does what is needed and the name suggests this use.

@koushik-das I think it's inappropriate as we're not marking those fields to note that they have hold sensitive information; but anyway that works

Also, it is possible to avoid serializing the objects by hand (like adding/appending {, >, <, } etc by hand?). Probably use any available library, and if that's not possible write unit tests to do some crud like comparisons?

@bhaisaab can you explain ? I like your comment about the annotation not being descriptive on the sensitivity of the field. So for the best solution we would have to write another annotation for that. It would be tchnical similar to the @LogLevel and the paramter of the @APICommand. thoughts?

@DaanHoogland we can simply use @LogLevel I simply shared that there is a slight chance on confusion in future, and do we then remove the requestHasSensitiveInfo/responseHasSensitiveInfo from Param/Apis throughout the codebase?

@bhaisaab no we shouldn't remove those both are used. I didn't understand the {, <, >, }  part.
The @LogLevel is used in the gson serialization and we can abuse it in the API but your comment makes sense. In the meanwhile that doesn't invalidate Koushik's change.
let's make the right decision

@DaanHoogland @bhaisaab requestHasSensitiveInfo/responseHasSensitiveInfo can be removed once this PR is accepted. I don't see any other use of these parameters.

@koushik-das You don't agree that the name LogLevel obfuscates that it is used to hide sensitive data?

@DaanHoogland I think LogLevel is a better/generic name to suppress a field from getting logged. Currently only sensitive field is getting annotated with it. Going forward some non-sensitive field may also be annotated if someone wants to prevent it from getting logged. Also since LogLevel is already used in agent commands, having an uniform approach throughout the code is always better and creates less confusion.

@DaanHoogland if you look at the changes or the code that takes in Object (Response object) and serializes it; we create the json or xml response string by manually adding the delimiters ({, }, <, >, : characters etc). I was wondering if there is a way to avoid that.

@bhaisaab Agree that the existing JSON and XML serialization can be improved but it is better to do it as a separate PR. For JSON, the standard Gson library is used. For XML we may have to check for a ASF compatible library that solves the purpose.

@koushik-das makes sense so we have a policy that for any sensitive field LogLevel(LogLevel.OFF) be used. We should add that as a comment to the enum to document it.

2015-11-04 14:23:51,076 DEBUG [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-34:ctx-0d2ee513 job-104/job-105 ctx-0d5c6252) Done executing VM work job: com.cloud.vm.VmWorkStart{"dcId
":1,"podId":1,"clusterId":1,"hostId":2,"rawParams":{"VmPassword":"<snip/>"},"userId":2,"accountId":2,"vmId":13,"handlerName":"VirtualMachineManagerImpl"}

And some other examples in there. I am looking further. @koushik-das this is going to take a lot of work to get right, right? Like this it is not done I think.

@koushik-das On second thought LogLevel can not be used I think: It is used for json serialization and one might have to serialize a password to be send to an agent while it may not be logged at the same time. We do need a separate annotation. this is not going to fly and hide sensitive data at the same time.

I think we should add isSensitive() to @Parameter and use that.
Also we should base this on gson 2+ and not on the version we are presently using.

@DaanHoogland About the issue you pointed out in com.cloud.vm.VmWorkStart serialization. Nice find but these are already existing issues. They surely needs fixing but I feel a separate effort is better. What do you say?
LogLevel can be safely used. If you look at the code there are 2 different GSON serializers - one for serialising the command that needs to be transmitted over the wire, and another is for logging purposes only. LogLevel is used in the latter one only.

@koushik-das I don't think you are right, command serialisation uses LogLevel as well. Look at com.cloud.agent.transport.RequestTest and tell me if you agree.

@DaanHoogland That's right. I had already mentioned about the agent commands in one of my previous comments

@koushik-das you said 'LogLevel is used in the latter one only.'. That is not true, I think. see com.cloud.agent.transport.RequestTest

@DaanHoogland If you look at ApiResponseGsonHelper.java in this PR there are GSon builders
private static final GsonBuilder s_gBuilder;
private static final GsonBuilder s_gLogBuilder;
Similarly for agent commands, if you look at GsonHelper.java there are 2 of them
protected static final Gson s_gson;
protected static final Gson s_gogger;

I am not fine with this change but must be honest and report regressions tests from the bubble: they all passed.
Test router internal advanced zone ... === TestName: test_02_router_internal_adv | Status : SUCCESS ===
ok
Test restart network ... === TestName: test_03_restart_network_cleanup | Status : SUCCESS ===
ok
Test router basic setup ... === TestName: test_05_router_basic | Status : SUCCESS ===
ok
Test router advanced setup ... === TestName: test_06_router_advanced | Status : SUCCESS ===
ok
Test stop router ... === TestName: test_07_stop_router | Status : SUCCESS ===
ok
Test start router ... === TestName: test_08_start_router | Status : SUCCESS ===
ok
Test reboot router ... === TestName: test_09_reboot_router | Status : SUCCESS ===
ok
test_privategw_acl (integration.smoke.test_privategw_acl.TestPrivateGwACL) ... === TestName: test_privategw_acl | Status : SUCCESS ===
ok
Test reset virtual machine on reboot ... === TestName: test_01_reset_vm_on_reboot | Status : SUCCESS ===
ok
Test advanced zone virtual router ... === TestName: test_advZoneVirtualRouter | Status : SUCCESS ===
ok
Test Deploy Virtual Machine ... === TestName: test_deploy_vm | Status : SUCCESS ===
ok
Test Multiple Deploy Virtual Machine ... === TestName: test_deploy_vm_multiple | Status : SUCCESS ===
ok
Test Stop Virtual Machine ... === TestName: test_01_stop_vm | Status : SUCCESS ===
ok
Test Start Virtual Machine ... === TestName: test_02_start_vm | Status : SUCCESS ===
ok
Test Reboot Virtual Machine ... === TestName: test_03_reboot_vm | Status : SUCCESS ===
ok
Test destroy Virtual Machine ... === TestName: test_06_destroy_vm | Status : SUCCESS ===
ok
Test recover Virtual Machine ... === TestName: test_07_restore_vm | Status : SUCCESS ===
ok
Test migrate VM ... === TestName: test_08_migrate_vm | Status : SUCCESS ===
ok
Test destroy(expunge) Virtual Machine ... === TestName: test_09_expunge_vm | Status : SUCCESS ===
ok
Test to create service offering ... === TestName: test_01_create_service_offering | Status : SUCCESS ===
ok
Test to update existing service offering ... === TestName: test_02_edit_service_offering | Status : SUCCESS ===
ok
Test to delete service offering ... === TestName: test_03_delete_service_offering | Status : SUCCESS ===
ok
Test for delete account ... === TestName: test_delete_account | Status : SUCCESS ===
ok
Test for Associate/Disassociate public IP address for admin account ... === TestName: test_public_ip_admin_account | Status : SUCCESS ===
ok
Test for Associate/Disassociate public IP address for user account ... === TestName: test_public_ip_user_account | Status : SUCCESS ===
ok
Test for release public IP address ... === TestName: test_releaseIP | Status : SUCCESS ===
ok
Test create VPC offering ... === TestName: test_01_create_vpc_offering | Status : SUCCESS ===
ok
Test VPC offering without load balancing service ... === TestName: test_03_vpc_off_without_lb | Status : SUCCESS ===
ok
Test VPC offering without static NAT service ... === TestName: test_04_vpc_off_without_static_nat | Status : SUCCESS ===
ok
Test VPC offering without port forwarding service ... === TestName: test_05_vpc_off_without_pf | Status : SUCCESS ===
ok
Test VPC offering with invalid services ... === TestName: test_06_vpc_off_invalid_services | Status : SUCCESS ===
ok
Test update VPC offering ... === TestName: test_07_update_vpc_off | Status : SUCCESS ===
ok
Test list VPC offering ... === TestName: test_08_list_vpc_off | Status : SUCCESS ===
ok
test_09_create_redundant_vpc_offering (integration.component.test_vpc_offerings.TestVPCOffering) ... === TestName: test_09_create_redundant_vpc_offering | Status : SUCCESS ===
ok
Test start/stop of router after addition of one guest network ... === TestName: test_01_start_stop_router_after_addition_of_one_guest_network | Status : SUCCESS ===
ok
Test reboot of router after addition of one guest network ... === TestName: test_02_reboot_router_after_addition_of_one_guest_network | Status : SUCCESS ===
ok
Test to change service offering of router after addition of one guest network ... === TestName: test_04_chg_srv_off_router_after_addition_of_one_guest_network | Status : SUCCESS ===
ok
Test destroy of router after addition of one guest network ... === TestName: test_05_destroy_router_after_addition_of_one_guest_network | Status : SUCCESS ===
ok
Test to stop and start router after creation of VPC ... === TestName: test_01_stop_start_router_after_creating_vpc | Status : SUCCESS ===
ok
Test to reboot the router after creating a VPC ... === TestName: test_02_reboot_router_after_creating_vpc | Status : SUCCESS ===
ok
Tests to change service offering of the Router after ... === TestName: test_04_change_service_offerring_vpc | Status : SUCCESS ===
ok
Test to destroy the router after creating a VPC ... === TestName: test_05_destroy_router_after_creating_vpc | Status : SUCCESS ===
ok

----------------------------------------------------------------------
Ran 42 tests in 8451.564s

OK

and
Create a redundant VPC with two networks with two VMs in each network ... === TestName: test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | Status : SUCCESS ===
ok
Create a redundant VPC with two networks with two VMs in each network and check default routes ... === TestName: test_02_redundant_VPC_default_routes | Status : SUCCESS ===
ok
Test iptables default INPUT/FORWARD policy on RouterVM ... === TestName: test_02_routervm_iptables_policies | Status : SUCCESS ===
ok
Test iptables default INPUT/FORWARD policies on VPC router ... === TestName: test_01_single_VPC_iptables_policies | Status : SUCCESS ===
ok
Stop existing router, add a PF rule and check we can access the VM ... === TestName: test_isolate_network_FW_PF_default_routes | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName: test_RVR_Network_FW_PF_SSH_default_routes | Status : SUCCESS ===
ok
Create a VPC with two networks with one VM in each network and test nics after destroy ... === TestName: test_01_VPC_nics_after_destroy | Status : SUCCESS ===
ok
Create a VPC with two networks with one VM in each network and test default routes ... === TestName: test_02_VPC_default_routes | Status : SUCCESS ===
ok
Check the password file in the Router VM ... === TestName: test_isolate_network_password_server | Status : SUCCESS ===
ok
Check that the /etc/dhcphosts.txt doesn't contain duplicate IPs ... === TestName: test_router_dhcphosts | Status : SUCCESS ===
ok
Test to create Load balancing rule with source NAT ... === TestName: test_01_create_lb_rule_src_nat | Status : SUCCESS ===
ok
Test to create Load balancing rule with non source NAT ... === TestName: test_02_create_lb_rule_non_nat | Status : SUCCESS ===
ok
Test for assign & removing load balancing rule ... === TestName: test_assign_and_removal_lb | Status : SUCCESS ===
ok
Test to verify access to loadbalancer haproxy admin stats page ... === TestName: test02_internallb_haproxy_stats_on_all_interfaces | Status : SUCCESS ===
ok
Test create, assign, remove of an Internal LB with roundrobin http traffic to 3 vm's ... === TestName: test_01_internallb_roundrobin_1VPC_3VM_HTTP_port80 | Status : SUCCESS ===
ok
Test SSVM Internals ... === TestName: test_03_ssvm_internals | Status : SUCCESS ===
ok
Test CPVM Internals ... === TestName: test_04_cpvm_internals | Status : SUCCESS ===
ok
Test stop SSVM ... === TestName: test_05_stop_ssvm | Status : SUCCESS ===
ok
Test stop CPVM ... === TestName: test_06_stop_cpvm | Status : SUCCESS ===
ok
Test reboot SSVM ... === TestName: test_07_reboot_ssvm | Status : SUCCESS ===
ok
Test reboot CPVM ... === TestName: test_08_reboot_cpvm | Status : SUCCESS ===
ok
Test destroy SSVM ... === TestName: test_09_destroy_ssvm | Status : SUCCESS ===
ok
Test destroy CPVM ... === TestName: test_10_destroy_cpvm | Status : SUCCESS ===
ok
Test for port forwarding on source NAT ... === TestName: test_01_port_fwd_on_src_nat | Status : SUCCESS ===
ok
Test for port forwarding on non source NAT ... === TestName: test_02_port_fwd_on_non_src_nat | Status : SUCCESS ===
ok
Test for reboot router ... === TestName: test_reboot_router | Status : SUCCESS ===
ok
Test for Router rules for network rules on acquired public IP ... === TestName: test_network_rules_acquired_public_ip_1_static_nat_rule | Status : SUCCESS ===
ok
Test for Router rules for network rules on acquired public IP ... === TestName: test_network_rules_acquired_public_ip_2_nat_rule | Status : SUCCESS ===
ok
Test for Router rules for network rules on acquired public IP ... === TestName: test_network_rules_acquired_public_ip_3_Load_Balancer_Rule | Status : SUCCESS ===
ok

----------------------------------------------------------------------
Ran 29 tests in 13087.859s

OK

@DaanHoogland Updated based on our discussion last week

great @koushik-das I'll rerun the tests.

@DaanHoogland did you get a chance to test it?

@koushik-das sorry, no. I have not much test infra and run a lot of tests. Could you force push your changes, please. I'll review your last changes.

@DaanHoogland I have force pushed again. Hopefully a good jenkins slave will pick this up :)

code reviewed. LGTM awaiting tests. it is running on one of the INFRA-10703 hosts but I know @abayer did some work on that issue...

also running the regressions suites on it now

1021.network.results.txt
1021.vpc.results.txt
all tests passed

@bhaisaab @jlk want to review give a second lgtm?

LGTM based on these tests (may not have tested the actual change):
nosetests --with-marvin --marvin-config=${marvinCfg} -s -a tags=advanced,required_hardware=true \
component/test_vpc_redundant.py \
component/test_routers_iptables_default_policy.py \
component/test_routers_network_ops.py \
component/test_vpc_router_nics.py \
smoke/test_loadbalance.py \
smoke/test_internal_lb.py \
smoke/test_ssvm.py \
smoke/test_network.py

Result:
Test iptables default INPUT/FORWARD policies on VPC router ... === TestName: test_01_single_VPC_iptables_policies | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName: test_01_isolate_network_FW_PF_default_routes_egress_true | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName: test_02_isolate_network_FW_PF_default_routes_egress_false | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName: test_01_RVR_Network_FW_PF_SSH_default_routes_egress_true | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName: test_02_RVR_Network_FW_PF_SSH_default_routes_egress_false | Status : SUCCESS ===
ok
Create a VPC with two networks with one VM in each network and test nics after destroy ... === TestName: test_01_VPC_nics_after_destroy | Status : SUCCESS ===
ok
Create a VPC with two networks with one VM in each network and test default routes ... === TestName: test_02_VPC_default_routes | Status : SUCCESS ===
ok
Check the password file in the Router VM ... === TestName: test_isolate_network_password_server | Status : SUCCESS ===
ok
Check that the /etc/dhcphosts.txt doesn't contain duplicate IPs ... === TestName: test_router_dhcphosts | Status : SUCCESS ===
ok
Test to create Load balancing rule with source NAT ... === TestName: test_01_create_lb_rule_src_nat | Status : SUCCESS ===
ok
Test to create Load balancing rule with non source NAT ... === TestName: test_02_create_lb_rule_non_nat | Status : SUCCESS ===
ok
Test for assign & removing load balancing rule ... === TestName: test_assign_and_removal_lb | Status : SUCCESS ===
ok
Test to verify access to loadbalancer haproxy admin stats page ... === TestName: test02_internallb_haproxy_stats_on_all_interfaces | Status : SUCCESS ===
ok
Test create, assign, remove of an Internal LB with roundrobin http traffic to 3 vm's ... === TestName: test_01_internallb_roundrobin_1VPC_3VM_HTTP_port80 | Status : SUCCESS ===
ok
Test SSVM Internals ... === TestName: test_03_ssvm_internals | Status : SUCCESS ===
ok
Test CPVM Internals ... === TestName: test_04_cpvm_internals | Status : SUCCESS ===
ok
Test stop SSVM ... === TestName: test_05_stop_ssvm | Status : SUCCESS ===
ok
Test stop CPVM ... === TestName: test_06_stop_cpvm | Status : SUCCESS ===
ok
Test reboot SSVM ... === TestName: test_07_reboot_ssvm | Status : SUCCESS ===
ok
Test reboot CPVM ... === TestName: test_08_reboot_cpvm | Status : SUCCESS ===
ok
Test destroy SSVM ... === TestName: test_09_destroy_ssvm | Status : SUCCESS ===
ok
Test destroy CPVM ... === TestName: test_10_destroy_cpvm | Status : SUCCESS ===
ok
Test Remote Access VPN in VPC ... === TestName: test_vpc_remote_access_vpn | Status : SUCCESS ===
ok
Test VPN in VPC ... === TestName: test_vpc_site2site_vpn | Status : SUCCESS ===
ok
Test for port forwarding on source NAT ... === TestName: test_01_port_fwd_on_src_nat | Status : SUCCESS ===
ok
Test for port forwarding on non source NAT ... === TestName: test_02_port_fwd_on_non_src_nat | Status : SUCCESS ===
ok
Test for reboot router ... === TestName: test_reboot_router | Status : SUCCESS ===
ok
Test for Router rules for network rules on acquired public IP ... === TestName: test_network_rules_acquired_public_ip_1_static_nat_rule | Status : SUCCESS ===
ok
Test for Router rules for network rules on acquired public IP ... === TestName: test_network_rules_acquired_public_ip_2_nat_rule | Status : SUCCESS ===
ok
Test for Router rules for network rules on acquired public IP ... === TestName: test_network_rules_acquired_public_ip_3_Load_Balancer_Rule | Status : SUCCESS ===
ok

----------------------------------------------------------------------
Ran 33 tests in 17014.931s

OK

And:
nosetests --with-marvin --marvin-config=${marvinCfg} -s -a tags=advanced,required_hardware=false \
smoke/test_routers.py \
smoke/test_network_acl.py \
smoke/test_privategw_acl.py \
smoke/test_reset_vm_on_reboot.py \
smoke/test_vm_life_cycle.py \
smoke/test_vpc_vpn.py \
smoke/test_service_offerings.py \
component/test_vpc_offerings.py \
component/test_vpc_routers.py

Result:
Test router internal advanced zone ... === TestName: test_02_router_internal_adv | Status : SUCCESS ===
ok
Test restart network ... === TestName: test_03_restart_network_cleanup | Status : SUCCESS ===
ok
Test router basic setup ... === TestName: test_05_router_basic | Status : SUCCESS ===
ok
Test router advanced setup ... === TestName: test_06_router_advanced | Status : SUCCESS ===
ok
Test stop router ... === TestName: test_07_stop_router | Status : SUCCESS ===
ok
Test start router ... === TestName: test_08_start_router | Status : SUCCESS ===
ok
Test reboot router ... === TestName: test_09_reboot_router | Status : SUCCESS ===
ok
test_privategw_acl (integration.smoke.test_privategw_acl.TestPrivateGwACL) ... === TestName: test_privategw_acl | Status : SUCCESS ===
ok
Test reset virtual machine on reboot ... === TestName: test_01_reset_vm_on_reboot | Status : SUCCESS ===
ok
Test advanced zone virtual router ... === TestName: test_advZoneVirtualRouter | Status : SUCCESS ===
ok
Test Deploy Virtual Machine ... === TestName: test_deploy_vm | Status : SUCCESS ===
ok
Test Multiple Deploy Virtual Machine ... === TestName: test_deploy_vm_multiple | Status : SUCCESS ===
ok
Test Stop Virtual Machine ... === TestName: test_01_stop_vm | Status : SUCCESS ===
ok
Test Start Virtual Machine ... === TestName: test_02_start_vm | Status : SUCCESS ===
ok
Test Reboot Virtual Machine ... === TestName: test_03_reboot_vm | Status : SUCCESS ===
ok
Test destroy Virtual Machine ... === TestName: test_06_destroy_vm | Status : SUCCESS ===
ok
Test recover Virtual Machine ... === TestName: test_07_restore_vm | Status : SUCCESS ===
ok
Test migrate VM ... === TestName: test_08_migrate_vm | Status : SUCCESS ===
ok
Test destroy(expunge) Virtual Machine ... === TestName: test_09_expunge_vm | Status : SUCCESS ===
ok
Test to create service offering ... === TestName: test_01_create_service_offering | Status : SUCCESS ===
ok
Test to update existing service offering ... === TestName: test_02_edit_service_offering | Status : SUCCESS ===
ok
Test to delete service offering ... === TestName: test_03_delete_service_offering | Status : SUCCESS ===
ok
Test for delete account ... === TestName: test_delete_account | Status : SUCCESS ===
ok
Test for Associate/Disassociate public IP address for admin account ... === TestName: test_public_ip_admin_account | Status : SUCCESS ===
ok
Test for Associate/Disassociate public IP address for user account ... === TestName: test_public_ip_user_account | Status : SUCCESS ===
ok
Test for release public IP address ... === TestName: test_releaseIP | Status : SUCCESS ===
ok
Test create VPC offering ... === TestName: test_01_create_vpc_offering | Status : SUCCESS ===
ok
Test VPC offering without load balancing service ... === TestName: test_03_vpc_off_without_lb | Status : SUCCESS ===
ok
Test VPC offering without static NAT service ... === TestName: test_04_vpc_off_without_static_nat | Status : SUCCESS ===
ok
Test VPC offering without port forwarding service ... === TestName: test_05_vpc_off_without_pf | Status : SUCCESS ===
ok
Test VPC offering with invalid services ... === TestName: test_06_vpc_off_invalid_services | Status : SUCCESS ===
ok
Test update VPC offering ... === TestName: test_07_update_vpc_off | Status : SUCCESS ===
ok
Test list VPC offering ... === TestName: test_08_list_vpc_off | Status : SUCCESS ===
test_09_create_redundant_vpc_offering (integration.component.test_vpc_offerings.TestVPCOffering) ... === TestName: test_09_create_redundant_vpc_offering | Status : SUCCESS ===
ok
Test start/stop of router after addition of one guest network ... === TestName: test_01_start_stop_router_after_addition_of_one_guest_network | Status : SUCCESS ===
ok
Test reboot of router after addition of one guest network ... === TestName: test_02_reboot_router_after_addition_of_one_guest_network | Status : SUCCESS ===
ok
Test to change service offering of router after addition of one guest network ... === TestName: test_04_chg_srv_off_router_after_addition_of_one_guest_network | Status : SUCCESS ===
ok
Test destroy of router after addition of one guest network ... === TestName: test_05_destroy_router_after_addition_of_one_guest_network | Status : SUCCESS ===
ok
Test to stop and start router after creation of VPC ... === TestName: test_01_stop_start_router_after_creating_vpc | Status : SUCCESS ===
ok
Test to reboot the router after creating a VPC ... === TestName: test_02_reboot_router_after_creating_vpc | Status : SUCCESS ===
ok
Tests to change service offering of the Router after ... === TestName: test_04_change_service_offerring_vpc | Status : SUCCESS ===
ok
Test to destroy the router after creating a VPC ... === TestName: test_05_destroy_router_after_creating_vpc | Status : SUCCESS ===
ok

----------------------------------------------------------------------
Ran 42 tests in 8513.577s

OK

Saw the changes, LGTM


[Doc Update] Install Site Extension REST API requires request body with 'Id' property

The below REST API call requires a request body with an 'Id' property with the value of the site extension ID by passed in its call or it returns a 400 (BadRequest) response:
Web Apps - Install Site Extension - REST API (Azure App Service) | Microsoft Docs
The above documentation does not specify that a request body is required and this call is only successful when a valid request body is passed.
Below is a sample of a request body to send with this API call to install a site extension:
{
"Id":"siteExtensionId"
}
Ask: Update to documentation above confirming that request body is needed to successfully call API and update to Try-It section that provides a sample JSON request body for requests.

Hi
If the problem persists and is related to running it on Azure App Service, please open a support incident in Azure:
https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request
This way we can better track and assist you on this case
Thanks,
Joaquin Vano
Azure App Service


Sub-band selection

Hello.
This is a great example of how to develop a node with LoraWAN technology. Unlike what has been done here, I am using a private server (Chirpstack) whose network is configured in the AU915 region, sub-band 0. How can I choose which sub-band I should use?
From what I understand TTN always works on the same sub-band and maybe this feature is hardcoded, if you can tell me how to change the setting I would appreciate it.
Greetings and congratulations for the great work done here.

Hi, thanks.

How can I choose which sub-band I should use?

What about searching the sourcecode for 'subband'? 😉
Check for LMIC_selectSubBand in LMIC-node.cpp.


Refactor to support "sl-ember-components" class pattern

@notmessenger please assign to me and change title to

Refactor to support "sl-ember-components-[component]" class pattern


help for "--output-format" incorrectly lists "concise" as the default

I've noticed that as of v0.5.0 the default output format has changed from "concise" to "full". However, the help still states that the default is "concise".
Minimal reproduction:
ruff check -h

returns:

Run Ruff on the given files or directories (default)
[yadda yadda]
--output-format <OUTPUT_FORMAT>    Output serialization format for violations. The default serialization format is "concise". In preview mode,
[yadda yadda]

Thank you! PR welcome if anyone is up for it.

Thank you! PR welcome if anyone is up for it.

done


Add a proof of execution to shield funds trusted call.

Send a confirmation extrinsic with the call hash after the shield_funds trusted call has been executed.
Note: The PR is currently big because it depends on #1165. I will rebase on master afterwards.

Closing in favor of #1174


Use stderr, not stdout, for notification

Else it messes with the output of the main command, which in the case of eg. @socketsecurity/cli can be JSON or Markdown.

That would work as well, getting sent all of the variables and one can format it however one likes, that would be nice

An example of why stderr or such would be preferable:
socket info<EMAIL_ADDRESS>--json | jq

Eg. ora uses stderr by default for outputting the spinner in such a CLI command: https://github.com/sindresorhus/ora#stream
update-notifier also uses stderr: https://github.com/yeoman/update-notifier/blob/3046d0f61a57f8270291b6ab271f8a12df8421a6/update-notifier.js#L178-L189

An example of why stderr or such would be preferable:
socket info<EMAIL_ADDRESS>--json | jq

In that CLI command there's an ora spinner to keep track of the API call and it by standard uses stderr for outputting the spinner and thus it won't mess with the JSON output that gets sent into jq: https://github.com/sindresorhus/ora#stream
The larger counterpart to this module, update-notifier, also uses stderr: https://github.com/yeoman/update-notifier/blob/3046d0f61a57f8270291b6ab271f8a12df8421a6/update-notifier.js#L178-L189

Makes sense! I also hadn't realised the original update-notifier used console.error as well so it makes sense to use it here as that is what this one was trying to replicate


intel-media-driver: 21.1.1 -> 21.1.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/intel-media-driver/versions.
meta.description for intel-media-driver is: "Intel Media Driver for VAAPI — Broadwell+ iGPUs"
meta.homepage for intel-media-driver is: "https://github.com/intel/media-driver"
meta.changelog for intel-media-driver is: "https://github.com/intel/media-driver/releases/tag/intel-media-21.1.2"
Updates performed

Version update

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 21.1.2 with grep in /nix/store/218wm4qqh1qgpggr699ivv890fnplvnw-intel-media-driver-21.1.2

directory tree listing: https://gist.github.com/4c202860e46c6d5bf31db81d722c5ef5

du listing: https://gist.github.com/678510da51fe177831fa836109d38087

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
intel-media-driver

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/218wm4qqh1qgpggr699ivv890fnplvnw-intel-media-driver-21.1.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A intel-media-driver https://github.com/r-ryantm/nixpkgs/archive/b6ea166adf7cd90c3a2b8eca800c7f13905e8fc6.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/218wm4qqh1qgpggr699ivv890fnplvnw-intel-media-driver-21.1.2
ls -la /nix/store/218wm4qqh1qgpggr699ivv890fnplvnw-intel-media-driver-21.1.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

intel-media-driver

Maintainer pings
cc @primeos @jfrankenau for testing.

Oh, I was a bit to fast/slow: https://github.com/NixOS/nixpkgs/commit/90e466041a4546bae74b2b27f390f8b4bc854a02


How do we maintain vertical scroll postion of GridViewScroll after postback?

Had the same problem, found the answer here:
http://gridviewscroll.aspcity.idv.tw/Demo/Advanced.aspx#MaintainScrollPosition
Hope this helps!

Thank you, I'll try
Have a nice day (-: Tuien Nguien

From: gymclasshero<EMAIL_ADDRESS>Sent: Wednesday, December 30, 2015 4:49 PM
To: twlikol/GridViewScroll
Cc: tuien
Subject: Re: [GridViewScroll] How do we maintain vertical scroll postion of GridViewScroll after postback? (#29)
Had the same problem, found the answer here:
http://gridviewscroll.aspcity.idv.tw/Demo/Advanced.aspx#MaintainScrollPosition
Demo - Advanced - GridViewScroll with jQueryhttp://gridviewscroll.aspcity.idv.tw/Demo/Advanced.aspx#MaintainScrollPosition
gridviewscroll.aspcity.idv.tw
GridViewScroll with jQuery ... SalesOrderID CustomerID BillToAddressID ShipToAddressID CreditCardID CreditCardApprovalCode
Hope this helps!

Reply to this email directly or view it on GitHubhttps://github.com/twlikol/GridViewScroll/issues/29#issuecomment-168032671.

It worked perfect!
Thank you so much


BV raw not subclass of raw problem when setting reference

Am I doing something wrong here, or is this a bug?
                                            preload=True, verbose=False,
                                            montage=montage_file, reference="M1")```
gives
```TypeError: inst should be Raw, Epochs, or Evoked instead of <class 'mne.io.brainvision.brainvision.RawBrainVision'>.```

It works if no reference is specified, and it worked with reference specified in previous versions. Sorry, I don't understand class stuff enough right now to do it myself.
@teonlamont

good catch. PR is in the works.

closing for pr #1923.


MaterialXEditor: Minor -- scroll wheel zooms and scrolls property editor

A minor nitpick. When the editor has a scroll bar on the right (show all inputs for std surface), if you use the scroll
wheel it will zoom in / out on the preview window but also scroll at the same time so it makes it hard to be able to zoom.
https://user-images.githubusercontent.com/49369885/216150266-3c1f1766-ba0c-4a83-b0fc-03fc580914b8.mp4
Looks like some minor pointer focus / handling issue that the event once handled by the preview window should not be passed onwards back to the scrollbar ?

Thanks for pointing this out @bernardkwok ! The render view zoom only checks right now if the cursor is within the bounds of the render view window which is causing that issue.

There are 3 scroll areas. The entire panel, the renderview, and just the attribute list. Each should trigger different behaviour. Only the panel scroll bar seems to affect the renderview.

Thanks @kwokcb I'll take a look.

Thanks to @kwokcb for reporting this issue, and to @HudsonHN for the fix in #1578!


Add import order linting for JS files

Overview
As per https://github.com/Opentrons/opentrons/pull/4680#discussion_r363102698 we have an unofficial import order we tend to follow in JS files. Let's have this be checked in a linter so we don't have to worry about this on our own/in PR reviews.

The only annoying thing here is that the import/order eslint plugin does not currently support import type ... as it's own import group. See https://github.com/benmosher/eslint-plugin-import/issues/645. That being said, with TypeScript now supporting the import type {...} syntax hopefully there will be some movement soon.
In the mean time, would we want to add this import ordering plugin before the plugin has type import grouping support?

Notes:
Tried out eslint-plugin-simple-import-sort in #6028 and tried out eslint import/order in #6032. Like Mike mentioned above, neither support making type imports their own group and putting them together.
Additional note from slack convo: Mike pointed out

The eslint-plugin-import project does have an open ticket to figure out type imports, and the ticket became newly relevant once TypeScript added import type syntax in their latest (or second latest, not keeping track) release. Not knowing much about how eslint plugins etc. work in detail, maybe it would be an interesting JS guild project to see if we could put a fork+PR together?


Fix TS typings

Fixes error:
node_modules/react-native-linear-gradient/index.d.ts:15:5 - error TS2666: Exports and export assignments are not permitted in module augmentations.

I'm confused, wasn't https://github.com/react-native-community/react-native-linear-gradient/pull/357 supposed to fix this? /cc @henrikra

Yeah. I just updated to 2.4.3 of react-native-linear-gradient and after that you won't get that compilation error. So please @kidcosmic update to 2.4.3 and the error is gone. This PR can be closed when @kidcosmic confirms that 2.4.3 is working for him too

@kidcosmic hey, can you confirm TS errors are gone when you upgrade to 2.4.3?

Good here!


Warn if no lighthouses were configured on a non lighthouse node

Would help in situations like #585

This has also tripped me up by mistake. Maybe also add a check to ignore static_host_map if amLighthouse?

This has also tripped me up by mistake. Maybe also add a check to ignore static_host_map if amLighthouse?

It's ok to have static host entries on a lighthouse node, you can run an entire mesh without a lighthouse if you desire.


how to cancel the debounce?

As you've already figured out that is currently not possible.
May I ask you what is your use case, where you want to cancel debounce? That way we can figure out an API that'll work for most use cases. Or we'll add task parameter like in your suggested pull request.

Hello @Tunous! Sorry I missed your notifications and this slept through the cracks.
The use case is simple:

execute a search API call on every keystroke. However, we debounce this to about 500ms.
if the user hits ENTER it should cancel the debounce Task and immediately make API call
if the user hits ESC it should cancel the debounce Task and never execute it

I'm currently using my own fork, but interested in seeing your solution to a use case like this.

Hey @mesqueeb, thanks for the use case. Here is my proposition.
An optional debouncer parameter on the onChange method. It would provide a function to cancel ongoing debounce at any time. For example:
@State private var debouncer = Debouncer()

var body: some View {
    SomeView()
        .onChange(of: query, debounceTime: .microseconds(500), debouncer: debouncer) {
            callApi()
        }
        .onKeyPress(.return) {
            debouncer.cancel()
            callApi()
            return .handled
        }
        .onKeyPress(.escape) {
            debouncer.cancel()
            return .handled
        }
}

What do you think?

Yes this API makes a lot of sense to me.
My previous PR wasn't even a valid solution I realized btw. 😅 But this should work.

I've submitted #4 with implementation. Try it out by pointing the package to that branch and let me know if this addresses your issue or if some changes are necessary.

Available in 2.0.0


Allow decoding primitive values directly

It's useful to be able to decode some types of responses that are not technically JSON, where the return is a simple raw text string / number / etc.
The easiest way to model this is by allowing JSON fragments, i.e. JSON  where the top level type is not an array or a dictionary. You could then use types like String or Int as valid Returning types in request (right now they will, I believe, compile, but always fail at runtime).
Processing fragments is possible with the old NSJSONSerialization class (https://developer.apple.com/documentation/foundation/nsjsonreadingoptions/nsjsonreadingallowfragments) but not with JSONDecoder / JSONEncoder.
This may eventually be added to JSONEncoder / JSONDecoder (https://forums.swift.org/t/allowing-top-level-fragments-in-jsondecoder/11750/3), at which point it might Just Work, but we should definitely verify it at that point.
it's also possible to fake in various ways (see the last message in the Swift Evolution thread for an example), if we are running into that too often, it may be worth implementing that workaround rather than waiting for official support.

It looks like this has been fixed in JSONEncoder / JSONDecoder now: https://bugs.swift.org/browse/SR-6163. It's a little unclear just from the bug if this is fix is limited to certain iOS versions, but I think if it were it would problaby be iOS 13+ only, which should be fine since we don't have any projects that support iOS 12 any more AFAIK.


Bugfix AnimationPlayer

Unfortunately, the latest changes brought some bugs, here's a fix for the bugs I could find.
bugs:

when pressing pause, and then play, duplicate calls to func with the same idx
if dragging the slider only slightly, duplicate calls to func with the same idx
is already at max_value - 1 and pressing play, duplicate call to func with the same idx
if loop=False, the button would not show as paused when the animation reached the end
example aspring2_player would make a jump at the beginning, because no calls to update_scene happened until pressing play/forward button

additional changes:

now also possible to step backwards from min_value to max_value-1 if loop=True, so looping in both directions is now allowed

note:
I wish it was possible to have self.set_frame(self.min_value) as the last line in the constructor for AnimationPlayer, but with the current layout of the class, that would call _func before all the necessary actors were added.

Great, thanks for providing these fixes!


Directions - Alternate routes

Hey Andy!
I'm wondering that is there any way to display the route alternatives as well?
I'm pretty sure that the directions directive only shows the first alternative.
Thanks,
Peter

Who is Andy?
I am not sure about that we can display route alternatives.
As per here, it just shows the response from Google. I am not sure Google provides us alternative route.
https://github.com/allenhwkim/angularjs-google-maps/blob/8e15800c6be7aa932e9cc3a8820425f529078a0e/directives/directions.js#L67
I am thinking that those advanced features are for Google only. :(

Hey Allen!
Thanks! :)
I found some solutions with the directions API and those can provide alternate routes. I'm pretty sure that not just 'Google' can provide it. I'm going deeper to figure it out.
Thanks,
Peter

I just found:
https://developers.google.com/maps/documentation/javascript/directions#DirectionsRequests
You need to set 'provideRouteAlternatives' true if you want to receive alternative routes.

I just modified
var showDirections = function(request) {
  request.provideRouteAlternatives=true;
  directionsService.route(request, function(response, status) {
    if (status == google.maps.DirectionsStatus.OK) {
      $timeout(function() {
        renderer.setDirections(response);
      });
    }
  });
};

And now it returns alternate routes as well

Hi, @ercseypeter? Have you solved the problem of showing alternative routes on the map? Can you share the HTML file?

Have you solved the problem of showing alternative routes on the map? Can you share the HTML file?


Example code in chap4 breaks with react-router-dom > v5.2

The example code in chap4 breaks with react-router-dom > @v5.2
The Switch component is no longer available and the compilation complains about this

Attempted import error: 'Switch' is not exported from 'react-router' (imported as 'Switch').

Please use the version in the book source code it will work

From: Pavan Shanbhag @.>
Sent: Sunday, March 6, 2022 7:47:34 AM
To: PacktPublishing/Full-Stack-React-TypeScript-and-Node @.>
Cc: Subscribed @.***>
Subject: [PacktPublishing/Full-Stack-React-TypeScript-and-Node] Example code in chap4 breaks with react-router-dom > v5.2 (Issue #21)
The example code in chap4 breaks with react-router-dom > @v5.2
The Switch component is no longer available and the compilation complains about this
Attempted import error: 'Switch' is not exported from 'react-router' (imported as 'Switch').
—
Reply to this email directly, view it on GitHubhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FPacktPublishing%2FFull-Stack-React-TypeScript-and-Node%2Fissues%2F21&data=04|01||0eeaf8b2e62f41d55ff608d9ff6f7cee|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637821676572372161|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=M3RMVmsHJdcrmt0XfJEzGiXMasTlRTgpBVwqwfoMq1U%3D&reserved=0, or unsubscribehttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAALIC5YYMXEA4O7GDXCHEKTU6SSONANCNFSM5QBCSP6A&data=04|01||0eeaf8b2e62f41d55ff608d9ff6f7cee|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637821676572372161|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=sf%2Bbs6Vs1yUu9grTuvLiEOECn0%2FoEcvsaT1hVQcItv8%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01||0eeaf8b2e62f41d55ff608d9ff6f7cee|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637821676572372161|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=E%2FHHdqC%2Bp043NHu6WhWEg4ZrnST7nhLF1qTGkr85Um4%3D&reserved=0 or Androidhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01||0eeaf8b2e62f41d55ff608d9ff6f7cee|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637821676572372161|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=iS5rQ19IoM6VGTsr09IYdSXkuvO4TP8Mx1BtHEK4QzE%3D&reserved=0.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


Use runTests in fuchsia tester.

This allows us to collect code coverage.

@cbracken @tvolkert please take a look.

Re-LGTM. I'll land once the bots go green.


Add M2M100 & NLLB model

The values used in the tests were obtained by running this python script:
from torch import tensor
from transformers import M2M100Model, M2M100ForConditionalGeneration

base = M2M100Model.from_pretrained("hf-internal-testing/tiny-random-M2M100Model")
generation = M2M100ForConditionalGeneration.from_pretrained("hf-internal-testing/tiny-random-M2M100ForConditionalGeneration")

inputs = {
    'input_ids': tensor([[10, 20, 30, 40, 50, 60, 70, 80, 0, 0]]),
    'decoder_input_ids':  tensor([[15, 25, 35, 45, 55, 65, 0, 0]]),
    'attention_mask': tensor([[1, 1, 1, 1, 1, 1, 1, 1, 0, 0]])
}

base(**inputs).last_hidden_state[:,1:4,1:4]
generation(**inputs).logits[:,1:4,1:4]

from transformers import AutoModelForSeq2SeqLM

generation = AutoModelForSeq2SeqLM.from_pretrained("hf-internal-testing/tiny-random-nllb")

inputs = {
    'input_ids': tensor([[10, 20, 30, 40, 50, 60, 70, 80, 0, 0]]),
    'decoder_input_ids':  tensor([[15, 25, 35, 45, 55, 65, 0, 0]]),
    'attention_mask': tensor([[1, 1, 1, 1, 1, 1, 1, 1, 0, 0]])
}

generation(**inputs).logits[:,1:4,1:4]

Here is a notebook demonstrating that it works, but there are issues regarding adding the language codes.

I also saw these warnings that I do not understand:
21:24:16.049 [debug] the following parameters were missing:

  * language_modeling_head.logits_bias.bias

21:24:16.049 [debug] the following PyTorch parameters were unused:

  * lm_head.weight
  * ```

@aymanosman thanks for the PR, looks clean, and great job adding the tests :)

@aymanosman here's how you can specify the source and target language as expected by the model:
source_lang = "eng_Latn"
target_lang = "pol_Latn"

target_token = Bumblebee.Tokenizer.token_to_id(tokenizer, target_lang)
generation_config = Bumblebee.configure(generation_config, forced_bos_token_id: target_token)

serving = Bumblebee.Text.generation(model_info, tokenizer, generation_config)

text = "The bank of the river is beautiful in spring"
Nx.Serving.run(serving, "#{source_lang} #{text}")

(From brief testing it seems that specifying the source language improves the translation quality)
I am still considering how to best fit this into Bumblebee APIs, but this should unblock your testing :)

@jonatanklosko Thanks. Looking forward to the improved API. I was thinking of modifying the generation serving to take structured input that contained more than just the input text but also the source and target languages.
So something like this would be possible:
Nx.Serving.run(serving, {"eng_Latn", "fra_Latn", "The bank of the river is beautiful in spring"})

But I'll wait for you to come up with a better idea :).

@aymanosman implemented in #395 :)


Fix location of assets

This commit changes the sortable table stylesheet to correctly use the Rails asset pipeline for images.

Smokey in integration is failing because it can't find these assets. Turns out that on AWS for an unknown reason the original assets are not deployed, but only the Rails asset pipeline versioned ones are.


Added Additional Positioning Options

The HUD can now be positioned relative not only to the center of the superview, but also relative to its top/bottom and left/right edges.  xOffset and yOffset apply as expected.  Default behavior is unaffected.
This is useful when you want to position the HUD near an edge of the screen and need to support multiple screen sizes and/or orientations.

Something like this is now possible in the latest version (auto layout) by just setting the x,y center offset to MBProgressMaxOffset. A bit simpler with less layout code.


Rancher apps uncompatible with Helm3 CLI

What kind of request is this (question/bug/enhancement/feature request): If I install a Helm3 chart via the UI it is possible to see the chart in helm using helm ls -A. However, trying to upgrade that same chart using helm fails. If I deploy the exact same helm chart using the Helm3 CLI, then upgrading is also possible but, of course, I no longer see that in Apps in the Rancher UI. Is it possible to somehow get both to work (UI + Helm CLI)?
Steps to reproduce (least amount of steps as possible): In my case I had bitnami/kafka installed via the UI and I tried to upgrade it via Helm CLI and the goal was to upgrade the replicaCount. This failed.
Result: Failed with Helm saying that it is not possible to update StatefulSet properties after deployment and only replicas field can be changed.
Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.4.5
Installation option (single install/HA): single install (Docker)

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): Custom
Machine type (cloud/VM/metal) and specifications (CPU/memory): bare-metal
Kubernetes version (use kubectl version): v1.18.6

Would also like to know if this is possible. Access to the management UI of my cluster keeps failing and being able to update via the CLI would be very useful.


linprog(method='revised simplex') doctest bug

linprog method='revised simplex' (in the 1.3 branch) doesn't solve the example problem in the docstring. The example was supposed to be a doctest, but all the outputs were marked "# may vary", so the problem wasn't caught.
I think a small bug in the phase 1 problem formulation was introduced at some point. Strangely, the issue didn't surface in any of the other tests (or the much more difficult benchmark problems). I can fix it before 1.3 and add the example as a regular test before 1.3 is released. @tylerjereddy Do I submit a PR to the "maintenance/1.3.x" branch?
Reproducing code example:
c = [-1, 4]
A = [[-3, 1], [1, 2]]
b = [6, 4]
x0_bounds = (None, None)
x1_bounds = (-3, None)
from scipy.optimize import linprog
res = linprog(c, A_ub=A, b_ub=b, bounds=(x0_bounds, x1_bounds), method="revised simplex",
              options={"disp": True})
print(res)

The status is 4 (algorithm reported success, but solution was infeasible).

If needed, which seems so, Tyler would backport it

If you open a PR also mark it backport candidate and remove it here maybe?

Will try to do this weekend. Still scheduled to release 5/20?

Hoping we can stick to the schedule yes, but the SkylakeX / AVX OpenBLAS issues have me a little concerned.
The PR should be to master, then we can backport if that seems appropriate--tag the PR to master with backport label so I can see it in the list when I'm doing release duties next time.

Apparently this was fixed on some platforms but not all. There was a mistake in test_bug_10124 such that the remaining issue was not caught:
res = linprog(c, A_ub, b_ub, A_eq, b_eq, bounds, method=self.method, options=self.options)

is supposed to be
res = linprog(c, A_ub, b_ub, A_eq, b_eq, bounds, method=self.method, options=self.o)

@tylerjereddy Didn't realize we were doing a 1.3.1 shortly. Let me get a PR for this out.


New device support -> Blitzwolf BW-FUN3

Device normal info

Brand BlitzWolf
Model BW-FUN3

Device info (please complete the following information, which can be found in log): like this:
{
   "active_time":1617574645,
   "biz_type":18,
   "category":"xxj",
   "create_time":1608581576,
   "icon":"smart/icon/ay1506337792739cXrIR/5d779ee65c541e0a351db6dc01da4720.jpg",
   "id":"734305088caab5f0fee0",
   "ip":"<IP_ADDRESS>",
   "lat":"",
   "local_key":"f4c01d31433175c4",
   "lon":"",
   "name":"BW-FUN3",
   "online":true,
   "owner_id":"11596570",
   "product_id":"6dwaaq5egthwitlb",
   "product_name":"BW-FUN3",
   "status":[
      {
         "code":"switch_spray",
         "value":false
      },
      {
         "code":"mode",
         "value":"small"
      }
   ],
   "sub":false,
   "time_zone":"-03:00",
   "uid":"az1576125271010d3j7N",
   "update_time":1625085721,
   "uuid":"734305088caab5f0fee0"
}

Device specifications (please complete the following information, which can be found in log):
{
   "category":"xxj",
   "functions":[
      {
         "code":"switch_spray",
         "type":"Boolean",
         "values":"{}"
      },
      {
         "code":"mode",
         "type":"Enum",
         "values":"{\"range\":[\"large\",\"small\"]}"
      }
   ],
   "status":[
      {
         "code":"switch_spray",
         "type":"Boolean",
         "values":"{}"
      },
      {
         "code":"mode",
         "type":"Enum",
         "values":"{\"range\":[\"large\",\"small\"]}"
      }
   ]
},
"success":true,
"t":1625437526216
}

I'm trying to add light capacity to the diffuser, but this error ocurrs with this request
Request:
{
"commands":[
{
"code":"switch_led",
"value":true
}
]
}
Response:
{
"code":2008,
"msg":"command or value not support",
"success":false,
"t":1625522202845
}

@Jhonattan-Souza back to Home Assistant Brasil bro kkkkk by L.FREITAS99 <3

@Jhonattan-Souza

@Jhonattan-Souza

@Jhonattan-Souza
This device needs to standardize, so light capacity will be enabled. we will fix it soon.

@tsutsuku Any news on the standardize of this device? Thanks!

@Jhonattan-Souza  It's fixed, try again.

Thanks @tsutsuku !


Add a mode to build with the oldest matching version of a crate instead of the newest one

Sometimes an implicit dependency on a newer stable version of a crate can sneak in without the Cargo.toml file being updated.
e.g. core-foundation 0.4.6 added CFNumber::from and someone could use that function but only be specifying a dependency on 0.4 in the Cargo.toml. This is what happened here: https://github.com/servo/webrender/pull/2190

dup of https://github.com/rust-lang/cargo/issues/4100


[Feature Request] Be able to use parameters for the report title

Hello,
Is your feature request related to a problem? Please describe.
I would like to be able to use a parameter in the report title.
Describe the solution you'd like
Be able to add $my_parameter in the report title.
Describe alternatives you've considered
I couldn't find any solution to dynamically set the report title.
Best regards,
Cobra

Indeed, it works, I should have tried first...
Can you add this feature in the documentation of the parameter select?