fail to import LiveImage callback from bluesky.broker_callbacks

xray_vision module missing.
BlueSky [5]: from bluesky.broker_callbacks import LiveImage
---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
<ipython-input-5-3209614a2784> in <module>()
----> 1 from bluesky.broker_callbacks import LiveImage

/home/xf05id1/.conda/envs/collection/lib/python3.4/site-packages/bluesky/broker_callbacks.py in <module>()
      6 from metadatastore.commands import run_start_given_uid, descriptors_by_start
      7 import matplotlib.pyplot as plt
----> 8 from xray_vision.backend.mpl.cross_section_2d import CrossSection
      9 from .callbacks import CallbackBase
     10 import numpy as np

ImportError: No module named 'xray_vision'

what machine are you on (output of "uname -a")?
what environment are you in? (output of "which conda")
what is currently installed? (output of "conda list -e")

(ignore my questions if someone is already helping you :smile: )

(collection)xf05id1@xf05id1-ws2:/nfs/xf05id1/ipython_ophyd$ uname -a
Linux xf05id1-ws2 3.2.0-4-amd64 #1 SMP Debian 3.2.68-1+deb7u5 x86_64 GNU/Linux
(collection)xf05id1@xf05id1-ws2:/nfs/xf05id1/ipython_ophyd$ which conda
/home/xf05id1/.conda/envs/collection/bin/conda
(collection)xf05id1@xf05id1-ws2:/nfs/xf05id1/ipython_ophyd$ conda list -e
This file may be used to create an environment using:
$ conda create --name  --file
platform: linux-64
backports_abc=0.4=py34_0
bluesky=0.4.1=py34_1
boltons=15.0.0=py34_0
channelarchiver=<IP_ADDRESS>.post4=4_gd3e9283_py34
cycler=0.9.0=py34_0
cytoolz=0.7.4=py34_0
databroker=0.3.2.post6=6_g972ef05_py34
decorator=4.0.6=py34_0
doct=1.0.1=py34_0
epics-base=<IP_ADDRESS>=0
filestore=0.2.3=py34_0
fontconfig=2.11.1=5
freetype=2.5.5=0
gnureadline=6.3.3.post16=py34_0
h5py=2.5.0=np110py34_4
hdf5=<IP_ADDRESS>=2
history=0.0.1.post39=py34_0
historydict=1.0.0.post20=py34_0
humanize=0.5.1=py34_0
ipykernel=4.1.1=py34_0
ipython=4.0.1=py34_0
ipython_genutils=0.1.0=py34_0
ipywidgets=4.1.0=py34_0
jbig=2.1=0
jinja2=2.8=py34_0
jpeg=8d=0
jsonschema=2.4.0=py34_0
jupyter_client=4.1.1=py34_0
jupyter_core=4.0.6=py34_0
keyring=5.3=py34_0
libgfortran=1.0=0
libpng=1.6.17=0
libsodium=1.0.3=0
libtiff=4.0.6=1
libxml2=2.9.2=0
lmfit=0.9.2.post15=15_gee41f80_npNonepy34
markupsafe=0.23=py34_0
matplotlib=1.5.1.post61=61_g513da02_py34
metadatastore=0.3.2=py34_0
mistune=0.7.1=py34_0
mongoengine=0.10.5=py34_2
nbconvert=4.1.0=py34_0
nbformat=4.0.1=py34_0
ncurses=5.9=6
notebook=4.0.6=py34_0
numpy=1.10.2=py34_0
openblas=0.2.14=3
openssl=1.0.2d=0
ophyd=0.2.0.post19=19_g4ff4fdc_py34
pandas=0.17.1=np110py34_0
path.py=8.1.2=py34_1
pexpect=3.3=py34_0
pickleshare=0.5=py34_0
pillow=3.0.0=py34_1
pims=0.3.2.post30=30_g717a2de_py34
pip=7.1.2=py34_0
prettytable=0.7.2=py34_0
ptyprocess=0.5=py34_0
pyepics=3.2.5rc3.post24=24_gdeb37ea_py34
pygments=2.0.2=py34_0
pymongo=3.0.3=py34_0
pyolog=4.0.0.post5+g1a24409=py34_0
pyparsing=2.0.3=py34_0
pyqt=4.11.4=py34_1
python=3.4.4=0
python-dateutil=2.4.2=py34_0
pytz=2015.7=py34_0
pyyaml=3.11=py34_1
pyzmq=15.1.0=py34_0
qt=4.8.7=1
readline=6.2.5=1
requests=2.9.0=py34_0
scipy=0.16.1=np110py34_0
setuptools=19.1.1=py34_0
simplegeneric=0.8.1=py34_0
sip=4.16.9=py34_0
six=1.10.0=py34_0
slicerator=0.9.7=py34_0
sqlite=<IP_ADDRESS>=1
super_state_machine=1.0=py34_0
terminado=0.5=py34_1
tifffile=0.7.0=np110py34_1
tk=8.5.18=0
tornado=4.3=py34_0
traitlets=4.0.0=py34_0
tzlocal=1.1.2=py34_0
wheel=0.26.0=py34_1
xz=5.0.5=0
yaml=0.1.6=0
zeromq=4.1.3=0
zlib=1.2.8=0

what does conda install xray-vision -c nsls2-tag --dry-run print to the screen?

collection)xf05id1@xf05id1-ws2:/nfs/xf05id1/ipython_ophyd$ conda install xray-vision -c nsls2-tag --dry-run
Fetching package metadata: /opt/conda/lib/python3.5/site-packages/requests/packages/urllib3/connection.py:266: SubjectAltNameWarning: Certificate for pergamon.cs.nsls2.local has no subjectAltName, falling back to check for a commonName for now. This feature is being removed by major browsers and deprecated by RFC 2818. (See https://github.com/shazow/urllib3/issues/497 for details.)
SubjectAltNameWarning
......
Solving package specifications: ......................
Package plan for installation in environment /home/xf05id1/.conda/envs/collection:
The following packages will be downloaded:
package                    |            build
---------------------------|-----------------
xray-vision-0.0.4.post7    |7_ge6b680f_npNonepy34         136 KB  https://pergamon.cs.nsls2.local:8443/conda/nsls2/linux-64/

The following NEW packages will be INSTALLED:
xray-vision: 0.0.4.post7-7_ge6b680f_npNonepy34 https://pergamon.cs.nsls2.local:8443/conda/nsls2/linux-64/

Dry run: exiting

Ok that is not going to install any weird dependencies. Go ahead and install xray-vision with that command, just remove the --dry-run, so: conda install -c nsls2-tag xray-vision.  After that try to start up ipython and import LiveImage again.

Thanks. this is solved and can be closed.

Great! glad it is importable now


Allow (or just document?) dynamic generation of Netlify _redirects file

I have URLs in my site which look like this:
/episode/15/the-boy-and-the-whale

I would like users who navigate to /episode/15/ to be redirected to the full URL with post slug. While this can be done with alias: in the front matter, it's cleaner to dynamically generate the Netlify _redirects file.
I have done this on another site with the TND Redirects Netlify module. But it looks like Doks may have its own way to do this already:
config.toml:
home = ["HTML", "RSS", "REDIRECTS", "HEADERS"]

# add output format for netlify _redirects
[outputFormats.REDIRECTS]
mediaType = "text/netlify"
baseName = "_redirects"
isPlainText = true
notAlternative = true

I don't see any information in the docs about how to use this output format, though. So I'd like to know if this is already possible, or if I should try to integrate TND Redirects Netlify instead.

Doks can handle this (similar to the TND approach). Not documented that well though — yet 😉
Redirect rules can be appended to /layouts/index.redirects, which is then built to /public/_redirects (as you can see configured in your excerpt of config.toml above).
The default /layouts/index.redirects:
{{- range $p := .Site.Pages -}}
{{- range .Aliases }}
{{ . }} {{ $p.RelPermalink -}}
{{- end }}
{{- end -}}

# /docs/1.0/prologue/   /docs/1.0/prologue/introduction/
# /docs/1.0/help/       /docs/1.0/help/how-to-update/
# /docs/1.0/            /docs/1.0/prologue/introduction/
# /docs/                /docs/1.0/prologue/introduction/
#
# /docs/0.1/*           https://v0-1-0--doks-versioning-poc.netlify.app/docs/0.1/:splat  200
# /docs/0.2/*           https://v0-2-0--doks-versioning-poc.netlify.app/docs/0.2/:splat  200

See also the Netlify docs: Redirects and rewrites.
Hugo Aliases are usually handled by <meta http-equiv="refresh" ...> tags. These have been disabled in ./config/_default/config.toml with disableAliases = true, and instead are handled by Netlify's Redirects and rewrites. This is handled automatically and you should continue to add aliases as described in the Hugo documentation.
To be added to the Doks docs!

Oh, excellent, that's just what I was hoping for. Thank you!


[release/8.1] Backport: Add GetEnvironmentVariableValuesAsync method to  ResourceExtens…

Backporting #4530
Microsoft Reviewers: Open in CodeFlow

IMO it's too late for this so I'd just wait for the next train for this one. @danmoseley thoughts?


Support different gmsh mesh versions

Support different gmsh mesh versions by providing a gmsh_version argument to xyz_mesh, which itselff may be used from Component.to_gmsh
Meshwell version is also bumped to support this API.
Closes #1906

rerunning manually


Ensure osxphotos is responsible process by launching disclaimed

When osxphotos accesses the Photos library the macOS TCC system will check the responsible process for permission to access the library, and if none has been given, the user is asked to give permission via a dialog.
Normally, when an executable is launched from Terminal or iTerm, the responsible app is the terminal app itself, not osxphotos, which means the user needs to give the terminal app the permission to access the Photos library, effectively giving any command executed in the terminal at any point access to the library.
Worse yet, if the user has on some prior occasion denied the terminal app this access, then osxphotos will not get the needed access either, which has been a source for confusion and failures for users.
We now re-launch osxphotos at startup with a special spawn flag that ensures that osxphotos is the responsible process. This will result in TCC dialogs and permissions specific to osxphotos.

Still checking a few things, so please don't merge just yet, thanks 😊

One thing this revealed that osxphotos also requests permission to other apps, as part of resolving the default photo library, and last used photo library:

I think we might be able to check the last-modified-date of the individual photo libraries without reading any files in them to determine the latter, but I've not yet found a way to determine the default library without access to Photo's container.

For reference, this is how the Photos access is presented:

Still checking a few things, so please don't merge just yet, thanks 😊

All good, just wanted to confirm that signing worked.


Added Matchers for chefspec. Issue: #49

Thanks for this!! I added a spec to validate the matchers. This will likely be released after reviewing #59

Awesome thanks.
On Mon, Nov 2, 2015 at 10:37 PM, Matt Wrock<EMAIL_ADDRESS>wrote:

Thanks for this!! I added a spec to validate the matchers. This will
likely be released after reviewing #59
https://github.com/chocolatey/chocolatey-cookbook/pull/59
—
Reply to this email directly or view it on GitHub
https://github.com/chocolatey/chocolatey-cookbook/pull/58#issuecomment-153232012
.

--
David Rodriguez | IT Manager
SpinDance, Inc. | Smart Choice. Smart Products.
main<PHONE_NUMBER> | mobile<PHONE_NUMBER>
SpinDance.com | #SMARTproduct


chore: update README

Current dependencies on/for this PR:

main

PR #2   👈

This comment was auto-generated by Graphite.


Only implicit types at the start of a function are erased

When a function with several implicit arguments is extracted, only implicit types at the start of the arguments are erased.
val fail: #a:Type -> a -> #b:Type -> b -> #c:Type -> (a-> b -> c) -> c
let fail #a x #b y #c f = f x y

Extracts to (in F# and OCaml Respectively)
let fail = (fun ( x  :  'Aa ) ( b  :  Prims.unit ) ( y  :  obj ) ( c  :  Prims.unit ) ( f  :  'Aa  ->  obj  ->  obj ) -> (f x y))

let fail x b y c f = f x y

Changing the function to place the implicit types at the start works :
val pass: #a:Type -> #b:Type -> #c:Type -> a -> b -> (a-> b -> c) -> c
let pass #a #b #c x y f = f x y

Extracts to
let pass = (fun ( x  :  'Aa ) ( y  :  'Ab ) ( f  :  'Aa  ->  'Ab  ->  'Ac ) -> (f x y))

let pass x y f = f x y

This does not work when implicits that are not Type are present; A function with
val fail2 : #a:Type -> #n:nat -> #b:Type -> ....

Will extract to
let fail2 = (fun ( n  :  Prims.nat ) ( b  :  Prims.unit ) ...

let fail2 n b ...

Implicit arguments cannot, in general, be removed.
F* will try to extract some polymorphic functions to ML-polymorphic functions in OCaml/F#. But it cannot extract all F* functions in this way. In particular, your example uses a kind of higher-rank polymophism.
Closing this issue.


Moving test folders

[x] test/* to test/resources
[x] test/testfiles to test/sampleContainer
[x] test only contains the *.js
[x] test/keys contains all the *.pem used

Looks good to me. Merging.


fixed typo on background example

Fixed typo in background example where color prop should be bgColor

thanks @KaiyuanMa !


Update README for prereqs

Part of #353

If you try to use the tool (to convert default net48 console app, for example) without Visual Studio, it will fail with the error "Could not find a Visual Studio installation to use to update." So, the "This may include installing Visual Studio 2019" part is incorrect, currently Visual Studio must be installed.


[Suggestion] Customizable build paths

Feature description
What do you want to see added to the extension?
In the settings i would like to have the ability to change the output directory of a compiled script change so it would reflect the structure of the project directory. By telling the settings what the root is for the source files and root build path it could create a structured compiled script directory.
In the settings i would add two text fields for local paths:
build path: This will determine the root of all the compiled scripts. If left empty it would use the default behavior.
source path: This will determine the root of all script files in a project, when compiling to a custom build path it would exclude this path when constructing the directories for the compiled scripts. If left empty it would assume that the project root is the top level directory for the scripts.
Example:
In the project root directory i have a folder called src, in this folder the source files related to the main plugin would reside, as example i have plugin "Main.sp". Inside this directory is a subdirectory called subplugins in here are plugins that rely and hook into the main plugin but are not essential for the main plugin, as example i have plugin "Modifier.sp".
The full (project local) paths would look as followed:
"src/Main.sp"
"src/subplugins/Modifiers,sp"
In the settings i would've set the following fields:
build path: "compiled"
source path: "src"
When i compile these two scripts it would build the plugins with the following (project local) paths:
"compiled/Main.smx"
"compiled/subplugins/Modifier.smx"
How would it help you?
It would provide me with an opt-in way of managing my plugins. It keeps the organisation i put in to the script files while making a clear distinction between source scripts and compiled plugins. This makes it easier for users that browse my repository to directly grab the latest in dev version of a plugin/.
How often would you use this feature?
This feature would see use in most of my plugins i will write, as i like to have a clear distinction between raw scripts and compiled code.

Hi, thanks for suggesting this.
I suppose that a command to "hot-swap" the build and src path would be useful as well?
A right click to set the current file as the src for example?

I suppose that a command to "hot-swap" the build and src path would be useful as well?
A right click to set the current file as the src for example?

could you provide an example of how that would work?

Yes, in the current version, if you right click inside a file, you have the option to "Set current file as main file", which automatically adds the current file to the MainPath setting.
I was thinking of doing something similar.

sounds like it could definitely be helpful.


DrawNode calls: replacing Color4F with Color4B (without the 'test' folder!)

Describe your changes
Should be a small performance hub
See also axmol-1.0.0 Aug.9 2023:
[REFINE] Change DrawNode api color parameters from Color4F to low Color4B
Issue ticket number and link
Checklist before requesting a review
For each PR

[ ] Add Copyright if it missed:
- "Copyright (c) 2019-present Axmol Engine contributors (see AUTHORS.md)."

[x] I have performed a self-review of my code.
Optional:

[ ] I have checked readme and add important infos to this PR.
[ ] I have added/adapted some tests too.

For core/new feature PR

[ ] I have checked readme and add important infos to this PR.
[ ] I have added thorough tests.

but we may change underlaying color to vec4 in the future release

but we may change underlaying color to vec4 in the future release

The PR is for the current implementation ;)

both Color4F and Color4B is lgtm currently, I will merge it now, let me check


Prevent assignment to "let"-bound values in Swift expressions.

Due to the way that SIL and IR is generated in the Swift compiler
assigning a new value to a let-binding often does not have the desired
effect since there may be many copies of the value in flight and LLDB
only knows about one of them per PC. Worse, sometimes the value known
to LLDB is only a shadow copy that is only used in the debugger.
rdar://problem/16042273

test with https://github.com/apple/swift/pull/27345

test with https://github.com/apple/swift/pull/27345
@swift-ci test

test with https://github.com/apple/swift/pull/27345
@swift-ci test

Most of this is actually reformatting of extant code, which seems all fine.  The part where you are getting the constant value and marking it in the Variable is also pretty clear and seems right.
I didn't understand why you changed the type of the return that we gather from Var to Let (SwiftASTManipulator.cpp:420 or thereabouts).  Was that a drive-by cleanup or was it necessary for this patch?

Was that a drive-by cleanup or was it necessary for this patch?

That's a drive-by cleanup that I now rolled into https://github.com/apple/swift-lldb/pull/2016

Adrian, we can discuss this more in person but you know that we're going to great lengths to make sure generic files in swift-lldb aren't polluted with swift specific support. I don't want to hold this back for too long because it's really good and sorely needed work, but we both agree that this time is probably the right one to design a plugin-style mechanism for DWARF [or, whatever allows us to hide this].

At present, the boundary for the language specific plugin to DWARF parsing is the DWARFASTParser.  We assumed when we split the Swift/Clang DWARF parsing code up that parsing types would be language specific, and should live in separate files, but parsing block and variable information was generic, and didn't need to be split up into separate plugins.
I note there are a couple of places where we do Clang specific stuff in SymbolFileDWARF (look for used of DWARFASTParserClang) so that separation is not as clean as it should be.
If this is something that could fit into the DWARFASTParser interface, that would be a natural home for it.  But it's clear that this separation needs a little more work, since we have to violate it from time to time as well...
Jim

On Sep 26, 2019, at 10:38 AM, Davide Italiano<EMAIL_ADDRESS>wrote:
Adrian, we can discuss this more in person but you know that we're going to great lengths to make sure generic files in swift-lldb aren't polluted with swift specific support. I don't want to hold this back for too long because it's really good and sorely needed work, but we both agree that this time is probably the right one to design a plugin-style mechanism for DWARF [or, whatever allows us to hide this].
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub, or mute the thread.

I do understand there was need to violate this in the past. I'm just nervous that we have a project that's supposed to clean these instances and this patch goes in the other direction.

We discussed this offline and turns out there's no easy way to prevent swift-specific code to leak. We should re-evaluate this in the future, but for now I think this can go in.


i18n.lang is empty when component tested with jest

Hi,
we have a lot of class components that use the withTranslation function component so that we can access the current language and the translation method.
class Test extends React.Component<any,any> {
   render(): JSX.Element {
       const {i18n} = this.props;
       return <>i18n.lang</>
   }
}

export default withTranslation(Test)

The problem is that when we test a component with Jest the lang in the component is empty.
I tried to add the I18nProvider in the test
it('render delivery time productInfoStatus_begin with deliveryId=5', function testDeliveryTime() {
    const wrapper = mount(
        <I18nProvider lang="en">
            <Test />
        </I18nProvider>);

    expect(wrapper..text()).toEqual('en');
});

But then I get this error:
Error: Uncaught [TypeError: router_1.useRouter is not a function]
I also tried to add global.i18nConfig = i18n; to my jest.setup.js
Is there a trick to get the language?
We use the latest next-translate and next.js version
Thanks
Robin

@RobinSCU maybe it helps you to see our tests of the Trans component, we use the I18nProvider. You can pass the config as a prop, apart from the namespace + lang to use.

@RobinSCU can you finally solve it? 😊

how did you fix empty lang key issue?


Bump react-side-effect version floor

People that reinstall react-helmet should receive the latest version of react-side-effect, so you shouldn't need to push out a new version, but bumping the version floor makes it clear that you don't expect someone to have react-side-effect <1.0.2
Closes #42

+1


Don't use native audio

It breaks on our server at > 50 players. Voip starts to stutter making what people say inauditable. Use 3d audio for now I guess

Instead of 'don't use', why not get a repo and then bubble can fix it?

Instead of 'don't use', why not get a repo and then bubble can fix it?

ElPumpo turning off native audio confirmed to fix it for more than 50 players for you?

ElPumpo turning off native audio confirmed to fix it for more than 50 players for you?

yes


Generated .obj not compatible with Godot 3.3.2 or Blender 2.83

Godot 3.3.2 and Blender 2.83 can't import the OBJ files I generated from this tool.  Both see the files as corrupt.

Here are some sample generated .obj files: https://c.mail.com/@976023017429673037/wkf4EbC-Q4SobG1VZlVITw
Thanks.

Found it. This is an embarrassing mistake. I must have broken this in my last minute refactoring. Thanks for letting me know!

Just a final thank you for the fix.  You really saved my bacon.  Here's what happened.  I wanted to generate in Godot every mesh variation of a cube for all permutations of the six sides variously included or omitted, so 64 variations (inc full cube and empty cube, and ignoring duplicates that could be excluded via rotation).  That part was easy.  Next, I needed to get these individual cube instances merged for each visible face.  That too was easy, thanks to "surface tool. append from."  The hard part?  Needing to export these generated meshes out of Godot.  There is literally no way to do it without your script.  It's a frustrating situation that everyone seems to concentrate on getting meshes into Godot (chiefly from Blender) and nobody thinks about getting them out -- as if the idea of anyone doing procgen meshes in Godot is preposterous.  In several hours of Googling I am convinced nobody has solved this except you and the dude who made the CSGObjExport script -- which I had already begun to rewrite for my purposes, but it was going to be a long slog.
Anyway, I slotted in your change just now and voila!  My 63 meshes now freshly minted and ready to import into Blender.  Thank you so much.


Remove IExcludeTypeFilter

Removes IExcludeTypeFilter
Replaced with a property 'ValidateChildren' on ModelMetadata
Teach ValidationVisitor to respect 'ValidateChildren' for enumerable
types.

/cc @dougbu

:shipit: from me.

:watch:

@dougbu updated

:shipit:


[Encoder] add input parameter check as protection for an encoder interface

https://rbcommons.com/s/OpenH264/r/1517/

there is no travis CI check, why is it?


Make paragraph pattern matching transforms extensible

Make paragraph pattern matching transforms extensible, e.g., paragraph to list item, paragraph to image.

We've introduced request/command pairs in a priority list, which provide extensible control over what happens when a given behavior is requested.
We also introduced EditReactions which can alter content after its changed, such as when the user types a character, or pastes content.
We've used these tools internally to accomplish block-level and inline content transformations. These tools should be equally applicable externally, so I'm going to close this issue as complete.


neotest: Add contract signer support

Problem
When using another contract for verification in unit tests, the transaction cost is calculated incorrectly.
...
Solution
To calculate the transaction cost, a test neo-vm is started on which the verification is performed.
...

Just as an idea --- can we reuse a local client internally and provide the regular RPC client API to tests? I think this would solve the problem immediately, calculatenetworkfee handles this and many other cases easily. Other APIs can also be useful.

Just as an idea

I like this idea, but even with RPC-based network fee calculation in neotest I still think that it might be a good point to implement contract signer so that it would be easier to construct contract-based witnesses.


Error: Transform error on using react-navigation/drawer

Description
On installing @react-navigation/drawer and implementing library, I get a Transform error: unexpected token generated from the index.tsx file that comes with the library

React Native version:
System:
OS: Windows 10 10.0.10586
npmPackages:
react: 16.9.0 => 16.9.0
react-native: 0.61.5 => 0.61.5
Contents of sideStack.js
import 'react-native-gesture-handler';
import React from 'react';
import {NavigationContainer} from '@react-navigation/native';
import {createStackNavigator} from '@react-navigation/stack';
import {createDrawerNavigator} from '@react-navigation/drawer';
import About from '../screens/about';
import More from '../screens/more';
import Gallery from '../screens/gallery';
import Excos from '../screens/excos';
import HomeStack from './homeStack';

const Drawer = createDrawerNavigator();

function sideStack() {
  return (
    <NavigationContainer>
      <Drawer.Navigator initialRouteName="Home">
        <Drawer.Screen name="About" component={About} />
        <Drawer.Screen name="Gallery" component={Gallery} />
        <Drawer.Screen name="Excos" component={Excos} />
        <Drawer.Screen name="More" component={More} />
      </Drawer.Navigator>
    </NavigationContainer>
  );
}

export default sideStack;

App.js
import React, {Component} from 'react';
import SplashScreen from 'react-native-splash-screen';
import SideStack from './src/components/routes/sideStack';

class App extends Component {
  componentDidMount() {
    SplashScreen.hide();
  }
  render() {
    return <SideStack />;
  }
}

export default App;

P.S: I am working on a physical device

Hey @juniorbuba,
You should check on react-navigation repository since the error is coming from this package :)

Agreed, you should report this issue on the react-navigation repo.

Will do
Thanks


Skip invalid data instead of exiting completely.

Whether using Unbox or UnboxOrThrow, the current implementation nil's the object or returns an empty collection completely if there is a single property on a single object that is invalid. This is necessary when perfect data is needed.
However, this pull request adds an option to skip invalid data and move on to the next property or object. This way, the consuming developer can prefer to deal with default values instead of an empty collection or nil object.
Use as:
let items: [Post] = UnboxOrSkip(data)

Also part of discussion #39.

Thanks for this PR! :rocket:  I think it's a great addition. :+1:
However, I think it'd be a lot better if you continued the parameter approach (extending Unbox() -> [T] rather than introducing a new UnboxOrSkip() function. Adding a lot of new Unbox... main functions will make the API more complicated and harder to maintain, since every time something is changed all the functions have to be updated. And since it's only relevant for arrays anyway, it makes sense to implement it as a parameter.
Also, skipInvalidData kind of sounds like you will skip on an entire invalid array, rather than elements of the array. The intent here is to surpress errors in case an error was encountered while unboxing a member of the array, so how about naming it allowInvalidElements: Bool = true (this matches the Element naming convenion of Array. What do you think?

Yes I actually toyed with both ways, as an overloaded parameter and using a separate UnboxOrSkip. In retrospect, using an overloaded parameter on Unbox seems like the way to go too because it is indeed a parameter and overkill to create a new function. It doesn't change the overall implementation or return types (returning a nil list is better than empty one, it gives more of an indication of what happened).
I never liked skipInvalidData name. I really really like allowInvalidElements.
Let me make the changes and add some unit tests and I'll update the PR. Thanks a mil for the input!

Awesome! Thank you so much for doing this :+1:

I just updated the PR to include the updates we discussed and it feels better. The only thing I don't like is I was forced to add the allowInvalidElements parameter to UnboxOrThrow as well so it can be reused for Unbox. I think that defeats the purpose of throwing errors since now what possible errors can UnboxOrThrow throw? In other words, does this even make sense?: UnboxOrThrow(data, allowInvalidElements: true)
I've also added a unit test. I couldn't figure how to reuse your mock data so I just generated dummy JSON and unboxed it.
Let me know if you have any thoughts or suggestions from here and I'll be glad to do another iteration on it. Thanks again!

Ok not sure how you're going to feel about this, but I moved the public API logic into private functions of Unboxer. This way, the public API functions are purely wrappers for them and refactoring can happen in the private functions instead of the public UnboxOrThrow functions. This also resolved UnboxOrThrow having the allowInvalidElements parameter.

Sorry for the delayed response :) I really like that you moved the API logic into private functions - it makes a lot of sense :+1: Some minor comments on the formatting, otherwise - great stuff! The only place where I think we need to make some changes is the test - instead of having a JSON string there I think it's a lot better to create the dictionaries in code. Let me know if you want me to help you out on any of these parts :) Thank you a lot for all the work you've done so far :rocket:

Cool, I updated the code based on your comments, except for the testing. Didn't like it either, will take another swing at it..

Awesome stuff! Thanks for making those changes! :+1: Now just the testing left then we can merge this one! :smile:

Having trouble getting the test to work. Here's what I'm trying:
    func testUnboxWithAllowInvalidElements() {
        struct Model: Unboxable {
            let successProperty: String
            let failedProperty: String

            init(unboxer: Unboxer) {
                self.successProperty = unboxer.unbox("success")
                self.failedProperty = unboxer.unbox("notexist")
            }
        }

        let array: [UnboxableDictionary] = [
            [
                "success" : "Hello"
            ],
            [
                "success" : "Unbox"
            ]
        ]

        guard let items: [Model] = Unbox(array, allowInvalidElements: true) else {
            XCTFail("Could not unbox collections from data")
            return
        }

        XCTAssert(items.count == 2, "Unbox did not return correct number of elements with invalid data")
    }

Commenting out the failedProperty makes it work, but otherwise it returns zero items. Not sure if it's the way I'm using UnboxableDictionary or a bug in my code? I committed it in case you want to run it.

..wait think I found something... hang on..

Ok there was actually a bug in my code. There were a few more places I had to add allowInvalidElements parameter on the dictionary side. Also, had to add it to the single-type returns (instead of just collections) so the variable can be carried all the way through. Good thing you told me to update the tests! I added a test for dictionary and another for json. Let me know if you think of anything else and I'll be glad to take another iteration. Much appreciated!

Looks much better now! Although I just thought of something - why add the allowInvalidElements to the Unboxer itself? Isn't it better to keep this flag only in the code that deals with arrays, since it's only relevant for arrays? That is, in performUnboxingWithDictionar(ies)AndContext. That would do the job, and make a lot smaller impact on the rest of the code, right?

You mean as opposed to keeping them in the performUnboxingWithData.. functions? I needed them in the data function to parse JSON from web endpoints.
Or if you mean why keep it in the Unboxer class at all, I originally didn't want to, but I needed to hold that flag in memory so it was always aware of that flag. Otherwise, it exited throwIfFailed. If we can get that flag to be available in throwIfFailed, then we wouldn't need to keep it in the class.

I agree tho, removing that property from Unboxer would bring it closer to being a struct one day and immutable. Hmm..

Yeah, you can put it in performUnboxingWithData as well, and from there call the array based one, given an array from NSData, since the flag only needs to be checked if one dictionary in the array failed to unbox. So the logic would be:
- Unbox from data (allowInvalidElements can be set).
- If the data is an array, call the dictionary API for each element (pass allowInvalidElements).
- If Unboxer did throw for one element, check allowInvalidElements before bubbling the error to the main function.

Makes sense?

Trying to follow but not grasping yet, looking at it more..

@basememara Need to go to bed now (It's 00:40 here), but let's catch up tomorrow. Are you on Twitter? Maybe talking about this through IM is going to be easier, for faster turnaround! But I think we are very close to finishing this :) I'm @johnsundell if you want to catch up on Twitter.

For sure, no rush. Will let it marinate and give it more thought as well. Thanks for the input again.

hey! cool you were right!! I moved allowInvalidElements out of the Unboxer property and scoped it to throwIfFailed as a func parameter. All the tests pass and works with my local app. Can you take a closer look and make sure it jives?

Starts to look really good! Sorry for the slow replies, I'm traveling at the moment so have limited time to review PRs :/ Put some comments inline, let me know what you think.

No worries, take your time. We're making great progress and sleeping on it definitely helps :+1:

And now we have 2 PR with the same stuff... @basememara

@basememara why don't you merge my branch in yours instead of downloading the code and committing it? This way of joining the code destroys commits history right?

Yes I agree. I tried merging, creating pull requests, etc but couldn't get it done. I reverted the change just now. I believe from here you can go ahead and create a pull request against my repo, I'll accept it, then I'll place my changes on top.


[✨] View Transition Hook

Is your feature request related to a problem?
I'm trying a animate a list of item on page navigation. For that I'm animating with Javascript, but there is no way to hook into the transition from the link.
const animate = $(() => {
  const items = document.querySelectorAll('.item');
  for (const item of items) {
    const transitionName = item.style.getProperty('view-transition-name');
    // Animation is not working because I need to be inside the transition
    document.documentElement.animate({
      transform: [....],
    }, {
      pseudoElement: `::view-transition-old(${transitionName})`,
      duration: 200
    })
  }
})
return <Link onClick$={animate} href="...">Link</Link>

Describe the solution you'd like
Ideally the Link element  & useNavigation would expose a callback for that :
const animate = $((transition, element) => {
  ....
})
return <Link onViewTransition$={animate} href="...">Link</Link>

Describe alternatives you've considered
We cannot set the animation inside style because this is a pseudo element of html.
As we cannot update the pseudo element with Javascript and we cannot use css variable like that ::view-transition-old(var(--name)).
We cannot set a <style> on each element because it'll be removed before the view transition is ready.
The only solution is to add <style> inside head with all the  ::view-transition-old() pseudo class and remove them:
const viewTransitionName = "...";
useVisibleTask$(() => {
  const style = document.createElement('stlye');
  style.textContent = `::view-transition-old(${viewTransitionName}) { animation: ....; }`
  const child = document.head.appenChild(style);
  return () => setTimeout(() => document.head.removeChild(child), 1000); // wait for transition to be done
});
return <Link href="">...</Link>

Note: I'm not using ::view-transition-old(*) because I want to target specific elements (not all) and I want to add delay.
Additional context
No response

Related https://github.com/BuilderIO/qwik/issues/3664 and https://github.com/BuilderIO/qwik/issues/2078

I'm going to point the other two issues here since they all want more or less the same thing.
The View Transitions API isn't supported by WebKit yet but according to the tracking issue they are ok with it.
Manu made https://pics-qwik.pages.dev/ last year using the ::view-transition CSS API.
It uses this CSS which assigns the "picture" transition to the images.
So, do we just recommend to use this API or do we implement async callbacks in navigation to allow doing things manually?

I think the discussion should go beyond navigation.
The ViewTransition API can be used for any kind of state changes that involves a mutation of the DOM, not only navigation.
Since rendering is async this is very difficult to run the view transition callback at the correct time, especially when animating with WAPI.
An idea would be to have something like track that would add run view transition when the state changes :
useViewTransition(async ({ track, transition }) => {
  if (!transition) return track(state);
  await transition.ready;
  document.documentElement.animate(...);
})

Since this issue gathers all View Transition problems, let's split it into two part
When does rendering happens
The ViewTransition API expect a callback that would work like that :

startViewTransition
Take a screenshot and create a ::view-transition pseudo element on the documentElement
Run callback that returns a promise
When promise resolve: resolve the transition.ready promise & start transition in the next frame

This is an imperative API, while Qwik is reactive, so we don't know when DOM is updated
Here is a an example that illustrate the problem
const hidden = useSignal(true);
useVisibleTask$(({ track }) => {
  track(() => hidden.value);
  // Case 1: flaky since the DOM might not have been updated at this point
  document.startViewTransition(() => waitForNextFrame());
   // Case 2: slow because it waits for 200ms to start the transition
  document.startViewTransition(() => waitFor200ms());
})

In React they suggest to use flushSync inside the callback to force rerendering. It's a ok-ish workaround since the main thread might be already busy, which might create junky transitions.
Solution 1
One solution Qwik could integrate is a onNextRender function that would resolve when DOM has been rerendered.
const hidden = useSignal(true);
useVisibleTask$(({ track }) => {
  track(() => hidden.value);
  document.startViewTransition(() => onNextRender());
})

Note: Here we might not want to startViewTransition when state initializes.
Solution 2
Create a hook into qwik-city that would do that :
useViewTransition(({ track }) => track(() => hidden.value));

The hook would:

runs once to know on what state changes to run
start view transition when the state changes
wait for next rendering to resolve the startViewTransition callback

Note: This solution might be better designed to allow dev to select in which case run or not the transition.
Hook into the transition flow
The API has two faces: CSS & JS.

CSS is declarative
JS is imperative

CSS :

Advantages: we don't have to know when the view transition happens, since it's already declared.
Problem: Since all elements flagged with view-transition-name will run for all view transition we tends to add/remove them dynamically.

JS:

Advantages: we have more control on the selection
Problem: we need to wait for the ViewTransition object to be ready and we don't know when this happen (as mentioned above)

Example in my initial comment
Solution 1:
Provide a way to hook into a transition :
const location = useLocation();
useViewtransition(({ track, before, ready, finished }) => {
  track(() => location.url);
  before(async () => {
    // Do something before `startViewTransition` is called
  });
  ready(async () => {
    // Hooked into the `transition.ready` promise callback
    // run WAPI animation
  });
  finished(async () => {
    // Hooked into the `transition.finished` promise callback
    // cleanup style or classes needed for the transition
  })
});
useViewTransition(({ track }) => track(() => hidden.value));

The benefit of this API is that we can listen on page transition or local state transition with different behaviors.
The issue is that it's not easy to have different behavior depending on the Link
Solution 2:
Maybe we can plug useViewTransition with <Link/> :
const transition = useViewtransition(({ before, ready, finished }) => {
  before(async () => {
    // Do something before `startViewTransition` is called
  });
  ready(async () => {
    // Hooked into the `transition.ready` promise callback
    // run WAPI animation
  });
  finished(async () => {
    // Hooked into the `transition.finished` promise callback
    // cleanup style or classes needed for the transition
  })
});
return <Link transition={transition} />

This could be used in any UI library which wants to leverage the View Transition API power inside Qwik :
const TabGroup = component$(({ transition }) => {
  const selected = useState(null);
  const select = $((e, el) => {
    console.log(transition.id);
    transition.start(() => selected.value = el.ariaControls)
  });
  return (
    <button role="tab" onClick$={select} aria-controls="tab-panel-1">...</button>
    <div role="tabpanel" id="tab-panel-1">...</div
  )
})

Conclusion
We can have something like that, and use it inside the <Link /> component
const useViewtransition = (params) => {
  const initialized = useSignal(false);
  const id = useId();
  const start = $(async (cb = (() => {})) => {
    await params.before();
    const viewTransition = await new Promise((res, rej) => {
      const transition = document.startViewTransition(async () => {
        await cb();
        await nextRendering();
        res(transition);
      })
    });
    viewTransition.read.then(params.ready);
    viewTransition.finished.then(params.finished)
  });
  // TODO: use something better than useVisibleTask$
  useVisibleTask$(({ track }) => {
    if (!params.track) return;
    track(params.track);
    if (!initialized.value) return initialized.value = true;
    start();
  })
  return { id, start }
}

Note that we could have a QRL prop on DOM nodes that gets awaited before it gets changed by Qwik. Would that be enough?

No I meant like onBeforeDomNodeWillChange

We moved this issue to qwik-evolution repo to create a RFC discussion for this.
Here is our Qwik RFC process thanks.


Example button is not responsive

Clicking the example button should show a dialog box prompting the user to select an example, but this dialog box is not showing up. The Redux action DialogShow is firing but the view is not updated

I noticed this myself on http://scadnano.org/, but couldn't reproduce it in the sense that I went back and the example button worked (and does for me now).
It never happens on https://web.cs.ucdavis.edu/~doty/scadnano/ or on the local dev server. Can you get it to happen in either of those places?

The bug appears in both places, and even in the Github hosted site
scadnano.org
On Mon, Feb 10, 2020 at 7:37 AM David Doty<EMAIL_ADDRESS>wrote:

I noticed this myself on http://scadnano.org/, but couldn't reproduce it
in the sense that I went back and the example button worked (and does for
me now).
It never happens on https://web.cs.ucdavis.edu/~doty/scadnano/ or on the
local dev server. Can you get it to happen in either of those places?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/UC-Davis-molecular-computing/scadnano/issues/186?email_source=notifications&email_token=AHOOY72RVEVHCBQGJPHXGDTRCFYCHA5CNFSM4KSILE2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELI6TUQ#issuecomment-584182226,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHOOY7YNFKLE6ETBD74ZZYLRCFYCHANCNFSM4KSILE2A
.

By "both places", you mean both https://web.cs.ucdavis.edu/~doty/scadnano/ and the local dev server you run?

Yes
On Mon, Feb 10, 2020 at 8:59 AM David Doty<EMAIL_ADDRESS>wrote:

By "both places", you mean both https://web.cs.ucdavis.edu/~doty/scadnano/
and the local dev server you run?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/UC-Davis-molecular-computing/scadnano/issues/186?email_source=notifications&email_token=AHOOY77FVRW7XPAKWYXQALDRCGBXFA5CNFSM4KSILE2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELJIYRY#issuecomment-584223815,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHOOY75WBVO3A4HFIU3JDWTRCGBXFANCNFSM4KSILE2A
.

It seems that this bug only occurs when the application begins to load with no initial dna design. If you clear local storage and refresh the page, the example button will not be responsive. Interestingly, if you load a dna example, the example button is still not responsive (the div containers are missing from the DOM). It's is not until the page is refreshed that these contains are added to the DOM, and the example button and other context menu button work

We've been hit by something like this before.
Can you add some unit/component tests to reproduce this? Specifically unit tests that test the condition that no design is loaded in localStorage already, because such bugs will be likely to go unnoticed by us (since we have designs in localStorage) but will hit every new user.

@dave-doty Any ideas why the Export DNA dialog box still works even if the example and context menus are not responsive?

Nope.

Oh, sorry, yes, I know why that is. It still uses an older package for making the dialog. I didn't replace it with my custom dialog stuff yet (which is what is making the error happen).
BTW I think I fixed the error. I'll commit it now.


importer: refactor and fix GC

Cherry-pick non-docker part from #1602

Use lease API (previoisly, GC was not supported)
Refactored interfaces for ease of future Docker v1 importer support https://github.com/containerd/containerd/pull/1602

For usage, please refer to ctr images import --help.
$ ctr images import --help
NAME:
   ctr images import - import images

USAGE:
   ctr images import [command options] [flags] <in>

DESCRIPTION:
   Import images from a tar stream.
Implemented formats:
- oci.v1     (default)

For oci.v1 format, you need to specify --oci-name because an OCI archive contains image refs (tags)
but does not contain the base image name.

e.g.
  $ ctr images import --format oci.v1 --oci-name foo/bar foobar.tar

If foobar.tar contains an OCI ref named "latest" and anonymous ref "sha256:deadbeef", the command will create
"foo/bar:latest" and "foo/bar@sha256:deadbeef" images in the containerd store.

OPTIONS:
   --format value       image format. See DESCRIPTION. (default: "oci.v1")
   --oci-name value     prefix added to either oci.v1 ref annotation or digest (default: "unknown/unknown")
   --snapshotter value  snapshotter name. Empty value stands for the daemon default value. (default: "overlayfs")

Signed-off-by: Akihiro Suda<EMAIL_ADDRESS>No impact on the server API, but since this contains fix for GC, I suggest setting milestone of this to v1.0.0

LGTM

LGTM


Explained what a deprecation cycle is

Inspired by a question asked in #4696, but does not close that issue

[x] Passes pre-commit run --all-files
[x] User visible changes (including notable bug fixes) are documented in whats-new.rst

Thanks @TomNicholas


Not possible to change or cancel attendance of an event

User story
As an event attendee, I am unable to attend an event I previously got a ticket for. I’d like to cancel and free up spots.
Best solution for this problem
An ability to "Edit RSVP" or "Cancel attendance".
MVP
Just a link in the list of attendees below your own name saying "Cancel attendance" or similar wording.
Metrics
For an event we organize, we got 1 email already of someone who is not able to make it and did not find a way to "unattend". If the functionality is there, it’s less work for everyone writing and answering emails and staying on top of who is coming and who is not.
Documentation
The goal of the documentation should be to make it easier for others to do this
(I don’t fully understand what this is referring to. I assume pointing to a file where the code could be changed?)

@jancborchardt in the case of events with "Non Free" Tickets, what should be the behavior? Should we implement refund? Should we restrict that to Free events first?  cc @piamancini for input

Could be made in incremental steps:

Working only for free events where it’s a "simple" ;) "Cancel attending"
For paid events, people could cancel attending but at this stage would have to leave their ticket price as donation.
As a last step, refunds could be implemented, so that for paid events people can choose between leaving the ticket price as donation, or refunding.

1 & 2 seem doable in the short term.

ref https://github.com/opencollective/opencollective/issues/2533


refactor(bookshop-init): Refactored bookshop init code to save format…

Context
This came about from wanting to use .css files to style bookshop components over .scss. Changing the file extension manually works ok, but having the option when creating a new component would be nice.
That led to adding CSS as an option into bookshop/init - but THAT led to a consideration about whether or not a user would want to specify different formats (yml, toml, etc) per component, or just once across a project... which led to the addition of saving options into the bookshop config file.
THEN... exploring the code, it looked to be 90% set up to prompt the user for all options upon running --new or --component (e.g. project directory, component name, format, style)... so rather than erroring out if the user runs --new or --component without supplied arguments, it prompts them for the required value.
Changes

Altered bookshop-config.ejs.t template to save component_directory, format and style along with engines.
Added a css.ejs.t template for css files
Added an option for CSS to templates.js
In main.js

Check for format in config file before prompting when creating a new component

Check for style in config file before prompting when creating a new component

Save new options into config when creating new project

Added a bit of info text for when bookshop creates the Sample component on --new (it wasn't clear that it was about to do this, and asked the user to specify their component format etc... so just made it more explicit...)

Altered --new and --component functionality to allow user to specify these flags without arguments - bookshop will now prompt for the required info instead of just erroring out

Altered --new workflow to prompt user for their format and style choices up front (once per project) - they can choose "I'll decide later" which will then prompt per component. Note: user can at any time manually alter the bookshop.config file and (providing they specify a valid option) they won't be prompted in the future.

Testing (tester)
The reviewer should check on this branch:

The code
The script locally

Nice!
Re: the failing tests, you'll find these files in /javascript-modules/integration-tests/features/init/, and they should be intuitive enough to edit. To run the tests:

Navigate to /javascript-modules/integration-tests/
Run yarn run itest --name "Creating a new Jekyll Bookshop" (where name is the name of a Scenario from any file)
To run all the tests, run yarn run itest-slow in the same directory (as you might expect, it's slow)

First up — if we're prompting people that .css is a valid option for a component, we need the whole stack to understand CSS files as well as SCSS files. Currently if they pick CSS, their framework Bookshop integration won't pick it up.
Tests:

The test Compiling simple component Sass could do with a Compiling simple component CSS test added below it, using a css file instead.
The Jekyll and Hugo integration test suites don't actually have any SCSS tests — so we should probably add tests for them and then also add CSS tests. I can stub these out for you if you would prefer.

Jekyll does have some tests for SCSS here: output_spec.rb

Packages:

Hugo loads SCSS files via this partial: bookshop_scss.html
Bookshop's style loader is here: bookshopStylePlugin.js
Jekyll loads styles here: style-tag.rb

Totally... agree with all the things...
Re: CSS in Bookshop - I do have a solution that I would love to run by you sometime using postCSS (processes SCSS or CSS or a combination with support for future CSS, etc, etc...) - would be great to get an opinion on it sometime when you have time (which I know is never....)
Re: this PR... would it be worth removing the CSS-specific stuff from the PR for now, but still retaining the 'save options into the config' part? Like the yml format stuff? Because that's useful on its own maybe?


DirtyJTAG 2

Refined XFER commands for faster transfers
New commands for probe-specific needs
More?

I just realized that Bluepill/STM32H103 pinout has changed. Currently working on updating the documentation to match these changes.


HADOOP-18806. Document missing property (ipc.server.read.threadpool.size) in core-default.xml

Description of PR
I think ipc.server.read.threadpool.size is quite important configuration tuning point for scalability. But there is no mention about it in core-default.xml.
There are some articles about hadoop tuning configuration with it. (e.g. https://support.huawei.com/enterprise/en/knowledge/EKB1100015760)
How was this patch tested?
It is just changed documentation.
For code changes:

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m  2s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
50m 30s

trunk passed

+1 :green_heart:
compile
18m 53s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
compile
17m  2s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
mvnsite
1m 42s

trunk passed

+1 :green_heart:
javadoc
1m 14s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
0m 49s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
shadedclient
129m 23s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 56s

the patch passed

+1 :green_heart:
compile
17m 52s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javac
17m 52s

the patch passed

+1 :green_heart:
compile
17m  8s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
javac
17m  8s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
1m 37s

the patch passed

+1 :green_heart:
javadoc
1m  9s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
0m 50s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
shadedclient
44m 24s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
18m 48s

hadoop-common in the patch passed.

+1 :green_heart:
asflicense
0m 59s

The patch does not generate ASF License warnings.

234m 35s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5844/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5844

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell detsecrets xmllint

uname
Linux 1dc32b454f2c 4.15.0-212-generic #223-Ubuntu SMP Tue May 23 13:09:22 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / c6b67a0449b92fa0e8a3b57b416bf076243b4cfe

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5844/1/testReport/

Max. process+thread count
1242 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5844/1/console

versions
git=2.25.1 maven=3.6.3

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

LGTM

how many configs are missing in core-default? I think we should add them all in one go

Hello, @ayushtkn I am willing to follow up on this issue.


Updates small error in documentation

Need to use double quotes in this case for string interpolation.

nothing
sorry


Deleting cluster in GKE does not clean up old "Forwarding Rules"

I ran into a situation where I deleted a Kubernetes cluster off GKE and immediately launched a new one. I re-launched some services that were binding to port 8888. The routing through that port was not working and after a while I checked the Forwarding Rules in Google Cloud. It turned out a rule of the same name for port 7777 was already there, which I believe was from the previous cluster.
I feel 99% sure there was an issue about this already but I couldn't seem to find it. If found just close this as dupe and link to other please... thanks.

#2984?

@zmerlynn Bah, and I even already commented on it... Thanks!


vulkaninfo: Generate vulkaninfo.rc file

Previously whenever a SDK was being built, it would have to manually find and
replace the version data in vulkaninfo.rc file with the appropriate values. This
commit makes it simpler by providing a CMake build argument which allows
setting the version to use from the command line.

CI Vulkan-Tools build queued with queue ID 43269.

CI Vulkan-Tools build # 529 running.

CI Vulkan-Tools build # 529 passed.

CI Vulkan-Tools build queued with queue ID 43320.

CI Vulkan-Tools build # 531 running.

CI Vulkan-Tools build # 531 passed.


The prisma server always creating new mongodb database when I deploy my service

Describe the bug
The prisma server always creating new mongodb database when I deploy my service, It is not using the existing database.
To Reproduce
Connect to existing mongodb database with prisma server. Set up the new service and deploy it on Prisma Server.
Expected behavior
The Prisma server should be use the existing database
IT HAPPENS FOR MONGODB
Whats happen
The prisma server creates a new database based on service name and stage, and don't use the existing database. ALWAYS.

@divyenduz
I can confirm this. To reproduce just try to make project using existing data

Ok, I'm waiting for this fix, thank you

cc @do4gr

same here


cache theme html file

Currently if you generate 5000 emails it will synchronously load the theme file 5000 times: https://github.com/eladnava/mailgen/blob/master/index.js#L51
It would be better to keep the theme html file content into memory so that the generate function won't try to read it each time from disk. That would be a massive improvement.

Hey @alessioalex!
Nice to meet you.
You are absolutely right about this

Hey! No problem. I've opened another 2 issues, let me know if you have time to take a look over them or if you need some help. Cool module btw, thanks!

Excellent, glad you like it :)


Add flag to allow filter options to be passed to varnishstat; Add testcases for varnishstat params

Current Behavior
Exporter performance degrades when a large number of backends are present
Why do we need this change?
We want to be able to filter out backend metrics from varnishstat, providing consistent performance and metric availability regardless of the number of backends present.
Implementation Details

Added -f flag allowing a comma separated list of filters to be passed to the exporter which will in turn be passed to varnishstat on scrape execution.
Added test, testcases for varnishstat params

:house: sc58193

👍  sounds good - I've pushed a build up to S3 - will follow up with a provisioning PR.


Squiggle for TypeScript diagnostic span not updated after Copilot inline suggestion accepted

Does this issue occur when all extensions are disabled?: Yes/No

Version: 1.75.0-insider
Commit: edc432e920c3ec2c2af5e8a99b8e4b782633d298
Date: 2022-12-16T05:22:34.551Z
Electron: 19.1.8
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 22.2.0
Sandboxed: Yes
Steps to reproduce:

Open a TypeScript file and insertexport const fix = {};

if (fix.position) {
  console.log(fix);
}

After position, insert  ! or enough to get a GitHub Copilot inline suggestion of !== undefined, and press tab to accept. (I assume other inline suggestion providers can trigger the same behavior.)
Observe that the rendered error span has moved to the curly brace.
Observe that TS Server logs show the text insertion and subsequent getErr results with proper spans:Info 217  [13:53:13.128] request:
    {
      "seq": 19,
      "type": "request",
      "command": "updateOpen",
      "arguments": {
        "changedFiles": [
          {
            "fileName": "/Users/andrew/Developer/microsoft/eg/ts/src/a.ts",
            "textChanges": [
              {
                "newText": "if (fix.position !== undefined) {",
                "start": {
                  "line": 3,
                  "offset": 1
                },
                "end": {
                  "line": 3,
                  "offset": 22
                }
              }
            ]
          }
        ],
        "closedFiles": [],
        "openFiles": []
      }
    }
Perf 218  [13:53:13.129] 19::updateOpen: elapsed time (in milliseconds) 0.4321
Info 219  [13:53:13.129] response:
    {"seq":0,"type":"response","command":"updateOpen","request_seq":19,"success":true,"body":true}
Info 220  [13:53:13.183] request:
    {
      "seq": 20,
      "type": "request",
      "command": "getApplicableRefactors",
      "arguments": {
        "file": "/Users/andrew/Developer/microsoft/eg/ts/src/a.ts",
        "startLine": 3,
        "startOffset": 34,
        "endLine": 3,
        "endOffset": 34
      }
    }
Info 221  [13:53:13.183] Starting updateGraphWorker: Project: /Users/andrew/Developer/microsoft/eg/ts/tsconfig.json
Info 222  [13:53:13.193] Finishing updateGraphWorker: Project: /Users/andrew/Developer/microsoft/eg/ts/tsconfig.json Version: 4 structureChanged: false structureIsReused:: Completely Elapsed: 9.50390100479126ms
Info 223  [13:53:13.193] Different program with same set of files
Perf 224  [13:53:13.194] 20::getApplicableRefactors: elapsed time (in milliseconds) 10.6177
Info 225  [13:53:13.194] response:
    {"seq":0,"type":"response","command":"getApplicableRefactors","request_seq":20,"success":true,"performanceData":{"updateGraphDurationMs":9.50390100479126},"body":[{"name":"Convert export","description":"Convert default export to named export","actions":[{"name":"Convert default export to named export","description":"Convert default export to named export","kind":"refactor.rewrite.export.named","notApplicableReason":"Could not find export statement"},{"name":"Convert named export to default export","description":"Convert named export to default export","kind":"refactor.rewrite.export.default","notApplicableReason":"Could not find export statement"}]},{"name":"Convert import","description":"Convert namespace import to named imports","actions":[{"name":"Convert namespace import to named imports","description":"Convert namespace import to named imports","kind":"refactor.rewrite.import.named","notApplicableReason":"Selection is not an import declaration."}]},{"name":"Convert import","description":"Convert named imports to default import","actions":[{"name":"Convert named imports to default import","description":"Convert named imports to default import","kind":"refactor.rewrite.import.default","notApplicableReason":"Selection is not an import declaration."}]},{"name":"Convert import","description":"Convert named imports to namespace import","actions":[{"name":"Convert named imports to namespace import","description":"Convert named imports to namespace import","kind":"refactor.rewrite.import.namespace","notApplicableReason":"Selection is not an import declaration."}]},{"name":"Extract type","description":"Extract type","actions":[{"name":"Extract to typedef","description":"Extract to typedef","kind":"refactor.extract.typedef","notApplicableReason":"Selection is not a valid type node"},{"name":"Extract to type alias","description":"Extract to type alias","kind":"refactor.extract.type","notApplicableReason":"Selection is not a valid type node"},{"name":"Extract to interface","description":"Extract to interface","kind":"refactor.extract.interface","notApplicableReason":"Selection is not a valid type node"}]},{"name":"Move to a new file","description":"Move to a new file","actions":[{"name":"Move to a new file","description":"Move to a new file","kind":"refactor.move.newFile","notApplicableReason":"Selection is not a valid statement or statements"}]},{"name":"Add or remove braces in an arrow function","description":"Add or remove braces in an arrow function","actions":[{"name":"Add braces to arrow function","description":"Add braces to arrow function","kind":"refactor.rewrite.arrow.braces.add","notApplicableReason":"Could not find a containing arrow function"},{"name":"Remove braces from arrow function","description":"Remove braces from arrow function","kind":"refactor.rewrite.arrow.braces.remove","notApplicableReason":"Could not find a containing arrow function"}]},{"name":"Convert to template string","description":"Convert to template string","actions":[{"name":"Convert to template string","description":"Convert to template string","kind":"refactor.rewrite.string","notApplicableReason":"Can only convert string concatenation"}]},{"name":"Extract Symbol","description":"Extract function","actions":[{"name":"Extract Function","description":"Extract function","kind":"refactor.extract.function","notApplicableReason":"Cannot extract empty range."}]},{"name":"Extract Symbol","description":"Extract constant","actions":[{"name":"Extract Constant","description":"Extract constant","kind":"refactor.extract.constant","notApplicableReason":"Cannot extract empty range."}]},{"name":"Generate 'get' and 'set' accessors","description":"Generate 'get' and 'set' accessors","actions":[{"name":"Generate 'get' and 'set' accessors","description":"Generate 'get' and 'set' accessors","kind":"refactor.rewrite.property.generateAccessors","notApplicableReason":"Could not find property for which to generate accessor"}]},{"name":"Infer function return type","description":"Infer function return type","actions":[{"name":"Infer function return type","description":"Infer function return type","kind":"refactor.rewrite.function.returnType","notApplicableReason":"Return type must be inferred from a function"}]}]}
Info 226  [13:53:13.228] request:
    {
      "seq": 21,
      "type": "request",
      "command": "geterr",
      "arguments": {
        "delay": 0,
        "files": [
          "/Users/andrew/Developer/microsoft/eg/ts/src/a.ts"
        ]
      }
    }
Perf 227  [13:53:13.228] 21::geterr: async elapsed time (in milliseconds) 0.4260
Info 228  [13:53:13.230] event:
    {"seq":0,"type":"event","event":"syntaxDiag","body":{"file":"/Users/andrew/Developer/microsoft/eg/ts/src/a.ts","diagnostics":[]}}
Info 229  [13:53:13.234] event:
    {"seq":0,"type":"event","event":"semanticDiag","body":{"file":"/Users/andrew/Developer/microsoft/eg/ts/src/a.ts","diagnostics":[{"start":{"line":3,"offset":9},"end":{"line":3,"offset":17},"text":"Property 'position' does not exist on type '{}'.","code":2339,"category":"error"}]}}

https://user-images.githubusercontent.com/3277153/208195703-38dc5929-1079-4b8d-94bc-d9dda63f3249.mp4

Full ts server log: tsserver.log

This bug has been fixed in the latest release of VS Code Insiders!
@andrewbranch, you can help us out by commenting /verified if things are now working as expected.
If things still don't seem right, please ensure you're on version fa13bf16fd237afef07f4df0648da026f43e3963 of Insiders (today's or later - you can use Help: About in the command palette to check), and leave a comment letting us know what isn't working as expected.
Happy Coding!


MSSQL - Unsupported type java.sql.Timestamp for column Datetime

Steps to reproduce
I have the following table in MSSQL db:
CREATE TABLE [atoti].[consumption](
	[Datetime] [datetime] NULL,
	[Consumption] [float] NULL,
	[ZoneCode] [varchar](max) NULL,
	[Hour] [int] NULL,
	[Day] [int] NULL,
	[Month] [int] NULL,
	[Year] [int] NULL,
	[DayOfWeek] [int] NULL,
	[WeekOfYear] [int] NULL,
	[Quarter] [int] NULL
)

I tried to read it with atoti:
consumption = session.read_sql(
    "jdbc:sqlserver://localhost:1433;databaseName=atoti",
    "SELECT * FROM [atoti].[atoti].[consumption];",
    username="atoti",
    password="atoti1",
    store_name="consumption",
    keys=["ZoneCode", "Year", "Month", "Day", "Hour", "WeekOfYear"],
)

consumption.head()

I got the below error message. The same schema on MySQL was fine.
AtotiJavaException: Receiver class io.atoti.loading.sql.SqlDataTable does not define or inherit an implementation of the resolved method 'abstract io.atoti.loading.IDataStoreOperationUnit getOperationUnit()' of interface io.atoti.loading.DataTable.
                    Get the full logs with : session.logs_tail(-1)
                    Get the logs path with : session.logs_path

Environment

atoti: 0.5.2
Python: 3.9.1
Operating System: win32

Logs (if relevant)
2021-03-30 19:03:01.445  INFO 24704 --- [Thread-1] io.atoti.AAtotiSession                   : Server started on port 53285
2021-03-30 19:03:01.844  WARN 24704 --- [Thread-1] io.atoti.loading.sql.JdbcDiscovery       : Unsupported type java.sql.Timestamp for column Datetime: defaulting to Object
2021-03-30 19:03:01.846  INFO 24704 --- [Thread-1] c.q.biz.pivot.impl.ActivePivotManager    : [ActivePivotManager]: Stopped
2021-03-30 19:03:01.847  INFO 24704 --- [qfs-discard-on-gc] com.qfs.multiversion.impl.EpochManager   : Thread com.qfs.multiversion.impl.EpochManager$DiscardOnGcTask@5b622d37 is interrupted!

Thanks to @tibdex,
pip list showed that my atoti-sql library is of a different version:
atoti                     0.5.2                    pypi_0    pypi
atoti-aws                 0.5.2                    pypi_0    pypi
atoti-jupyterlab          <IP_ADDRESS>10304180349         13f74e2    https://activeviam.jfrog.io/artifactory/api/conda/conda-internal
atoti-kafka               0.5.2                    pypi_0    pypi
atoti-sql                 0.5.1                    pypi_0    pypi

Running pip install -U atoti-sql solves the issue.


[FETURE] Include MacOS in CI build matrix

This is to catch and prevent critical bugs like #213 from going unnoticed.
Depends on #220.

Good idea. MacOS builds did not work with MacOS a while ago. But this may have changed.

Closed by #239


Numpy example

This is a really nice example. Thanks!
Quick note: there are a couple of warnings from rasterio about gdal-style transforms being deprecated. Is it easy to fix?


plugins.cordova.io will be deprecated in the near future

according to this
http://phonegap.com/blog/2015/05/26/npm-plugins-available/
http://cordova.apache.org/announcements/2015/04/21/plugins-release-and-move-to-npm.html
so...just want to inform you that your plugin should be move to npm in the future...

I know I know I know

sorry...


Better handling of non-matching submesh indices + materials

Check that materials are not null, change LogError to LogWarning (this is not corrupting data).
Also, better logs for what went wrong

Sure, just rebased on dev

Awesome, thanks!


office-addin-debugging Unsupported engine

office-addin-debugging has a transitive dependency on<EMAIL_ADDRESS>which does not support node v20.

This is being worked on. Are you able to use Node v18 in the meantime?

Any progress on this?

Edit the .npmrc file and remove engines=strict. Node v20 will work fine.

I also just published updates script packages that finally got the version of the dependency that has all the fixes in it.  It should be clean now with the latest office-addin-dev-settings (a dependency of office-adding-debugging).


Added workflow to update current-version-tag in README.md

Will fix #972
As discussed earlier, I have reopened this as a new PR so it can be CLA complaint.

Closing after no activity for over a month. Can re-open.


new Teams meeting expiration settings

where is the info on how to control expired meetings?
Microsoft 365 Roadmap ID: 66921
Timing: these changes are available today
Control: policies in Teams admin center or PowerShell
Action: review and assess impact.
[Enter feedback here]

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

ID: ee6d4c1c-6f16-b1a4-c4a9-be4e6d1f95b7
Version Independent ID: 50ad835d-ed7f-18c6-34ba-322c1574f9c2
Content: Meeting policies and meeting expiration in Microsoft Teams - Microsoft Teams
Content Source: Teams/meeting-expiration.md
Service: msteams
GitHub Login: @cichur
Microsoft Alias: v-cichur

Thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.


Sessions save problem with PHP 7.0.23 with file based sessions

I have been trying to solve the following problem with our current host but without luck.
When I use the file based session paths, I keep getting permission errors with PHP7 which I don't get with PHP 5.6. Our host has been digging the problem also but according to them the PHP7 settings are similar but with some additional security.
When we are using file based sessions I am getting the following error.
is_dir(): open_basedir restriction in effect. File(/var/lib/php) is not within the allowed path(s): (/home/dev/:/tmp/:/var/tmp/:/usr/local/php70/lib/:/usr/local/php54/lib/:/usr/local/php55/lib/:/usr/local/php56/lib/:/usr/local/php70/lib/:/usr/local/php71/lib/:/usr/local/lib/php/:/dev/urandom)

According to our host, concretete5 is the only system affected with this problem.
I have attached PHP information for both 7.0.23 and 5.6.31 as attachment.
Environment information for our sites:
# concrete5 Version
Core Version - 8.3.2
Version Installed - 8.3.2
Database Version -<PHONE_NUMBER>3656

# concrete5 Packages
Afixia: Login Redirect (0.9.2), Login Block (0.9.3)

# concrete5 Overrides
themes/extranet/home.php, themes/extranet/page_forbidden.php, themes/extranet/page_theme.php, themes/extranet/right_sidebar.php, themes/extranet/full.php, themes/extranet/images, themes/extranet/left_sidebar.php, themes/extranet/default.php, themes/extranet/view.php, themes/extranet/page_not_found.php, themes/extranet/elements/header_calendar.php, themes/extranet/elements/header_top_bak.php, themes/extranet/elements/header_top.php, themes/extranet/elements/footer.php, themes/extranet/elements/header.php, themes/extranet/elements/footer_bottom.php, themes/extranet/elements, themes/extranet/description.txt, themes/extranet/css/styles.xml, themes/extranet/css/mixins/mixins.less, themes/extranet/css/mixins, themes/extranet/css/main.less, themes/extranet/css/components/forms.less, themes/extranet/css/components/footer.less, themes/extranet/css/components/header.less, themes/extranet/css/components/navigation.less, themes/extranet/css/components/blocks.less, themes/extranet/css/components, themes/extranet/css/bootstrap-3.2.0/button-groups.less, themes/extranet/css/bootstrap-3.2.0/code.less, themes/extranet/css/bootstrap-3.2.0/variables.less, themes/extranet/css/bootstrap-3.2.0/navs.less, themes/extranet/css/bootstrap-3.2.0/forms.less, themes/extranet/css/bootstrap-3.2.0/breadcrumbs.less, themes/extranet/css/bootstrap-3.2.0/mixins.less, themes/extranet/css/bootstrap-3.2.0/close.less, themes/extranet/css/bootstrap-3.2.0/labels.less, themes/extranet/css/bootstrap-3.2.0/mixins/center-block.less, themes/extranet/css/bootstrap-3.2.0/mixins/grid-framework.less, themes/extranet/css/bootstrap-3.2.0/mixins/image.less, themes/extranet/css/bootstrap-3.2.0/mixins/forms.less, themes/extranet/css/bootstrap-3.2.0/mixins/progress-bar.less, themes/extranet/css/bootstrap-3.2.0/mixins/labels.less, themes/extranet/css/bootstrap-3.2.0/mixins/tab-focus.less, themes/extranet/css/bootstrap-3.2.0/mixins/background-variant.less, themes/extranet/css/bootstrap-3.2.0/mixins/resize.less, themes/extranet/css/bootstrap-3.2.0/mixins/hide-text.less, themes/extranet/css/bootstrap-3.2.0/mixins/gradients.less, themes/extranet/css/bootstrap-3.2.0/mixins/size.less, themes/extranet/css/bootstrap-3.2.0/mixins/pagination.less, themes/extranet/css/bootstrap-3.2.0/mixins/text-emphasis.less, themes/extranet/css/bootstrap-3.2.0/mixins/nav-vertical-align.less, themes/extranet/css/bootstrap-3.2.0/mixins/nav-divider.less, themes/extranet/css/bootstrap-3.2.0/mixins/opacity.less, themes/extranet/css/bootstrap-3.2.0/mixins/table-row.less, themes/extranet/css/bootstrap-3.2.0/mixins/list-group.less, themes/extranet/css/bootstrap-3.2.0/mixins/responsive-visibility.less, themes/extranet/css/bootstrap-3.2.0/mixins/grid.less, themes/extranet/css/bootstrap-3.2.0/mixins/vendor-prefixes.less, themes/extranet/css/bootstrap-3.2.0/mixins/clearfix.less, themes/extranet/css/bootstrap-3.2.0/mixins/border-radius.less, themes/extranet/css/bootstrap-3.2.0/mixins/panels.less, themes/extranet/css/bootstrap-3.2.0/mixins/buttons.less, themes/extranet/css/bootstrap-3.2.0/mixins/text-overflow.less, themes/extranet/css/bootstrap-3.2.0/mixins/alerts.less, themes/extranet/css/bootstrap-3.2.0/mixins/reset-filter.less, themes/extranet/css/bootstrap-3.2.0/mixins, themes/extranet/css/bootstrap-3.2.0/scaffolding.less, themes/extranet/css/bootstrap-3.2.0/utilities.less, themes/extranet/css/bootstrap-3.2.0/tables.less, themes/extranet/css/bootstrap-3.2.0/normalize.less, themes/extranet/css/bootstrap-3.2.0/thumbnails.less, themes/extranet/css/bootstrap-3.2.0/component-animations.less, themes/extranet/css/bootstrap-3.2.0/navbar.less, themes/extranet/css/bootstrap-3.2.0/pagination.less, themes/extranet/css/bootstrap-3.2.0/jumbotron.less, themes/extranet/css/bootstrap-3.2.0/input-groups.less, themes/extranet/css/bootstrap-3.2.0/tooltip.less, themes/extranet/css/bootstrap-3.2.0/glyphicons.less, themes/extranet/css/bootstrap-3.2.0/wells.less, themes/extranet/css/bootstrap-3.2.0/responsive-embed.less, themes/extranet/css/bootstrap-3.2.0/list-group.less, themes/extranet/css/bootstrap-3.2.0/badges.less, themes/extranet/css/bootstrap-3.2.0/grid.less, themes/extranet/css/bootstrap-3.2.0/carousel.less, themes/extranet/css/bootstrap-3.2.0/modals.less, themes/extranet/css/bootstrap-3.2.0/media.less, themes/extranet/css/bootstrap-3.2.0/dropdowns.less, themes/extranet/css/bootstrap-3.2.0/panels.less, themes/extranet/css/bootstrap-3.2.0/buttons.less, themes/extranet/css/bootstrap-3.2.0/progress-bars.less, themes/extranet/css/bootstrap-3.2.0/bootstrap.less, themes/extranet/css/bootstrap-3.2.0/pager.less, themes/extranet/css/bootstrap-3.2.0/print.less, themes/extranet/css/bootstrap-3.2.0/alerts.less, themes/extranet/css/bootstrap-3.2.0/type.less, themes/extranet/css/bootstrap-3.2.0/popovers.less, themes/extranet/css/bootstrap-3.2.0/theme.less, themes/extranet/css/bootstrap-3.2.0/responsive-utilities.less, themes/extranet/css/bootstrap-3.2.0, themes/extranet/css/base/typography.less, themes/extranet/css/base/body.less, themes/extranet/css/base, themes/extranet/css/variables/errors.less, themes/extranet/css/variables/colors.less, themes/extranet/css/variables/typography.less, themes/extranet/css/variables/gutters.less, themes/extranet/css/variables/dimensions.less, themes/extranet/css/variables, themes/extranet/css/bootstrap-modified.css, themes/extranet/css, themes/extranet/js/main.js, themes/extranet/js, themes/extranet

# concrete5 Cache Settings
Block Cache - Off
Overrides Cache - On
Full Page Caching - Off
Full Page Cache Lifetime - Every 6 hours (default setting).

# Server Software
Apache/2

# Server API
fpm-fcgi

# PHP Version
5.6.31

# PHP Extensions
bcmath, calendar, cgi-fcgi, Core, ctype, curl, date, dom, ereg, exif, fileinfo, filter, ftp, gd, gettext, hash, iconv, intl, ionCube Loader, json, libxml, mbstring, mcrypt, mhash, mysql, mysqli, mysqlnd, openssl, pcre, PDO, pdo_mysql, pdo_sqlite, Phar, posix, Reflection, session, SimpleXML, soap, sockets, SPL, sqlite3, standard, tokenizer, wddx, xml, xmlreader, xmlwriter, xsl, Zend Guard Loader, Zend OPcache, zip, zlib

# PHP Settings
max_execution_time - 30
log_errors_max_len - 1024
max_file_uploads - 20
max_input_nesting_level - 64
max_input_time - 60
max_input_vars - 5000
memory_limit - 256M
post_max_size - 64M
sql.safe_mode - Off
upload_max_filesize - 64M
mysql.max_links - Unlimited
mysql.max_persistent - Unlimited
mysqli.max_links - Unlimited
mysqli.max_persistent - Unlimited
pcre.backtrack_limit - 1000000
pcre.recursion_limit - 100000
session.cache_limiter - <i>no value</i>
session.gc_maxlifetime - 7200
soap.wsdl_cache_limit - 5
opcache.max_accelerated_files - 2000
opcache.max_file_size - 0
opcache.max_wasted_percentage - 5

This problem affects all our concrete5 sites when using PHP 7.0.23.
phpinfo5631.pdf
phpinfo7023.pdf

You can try to change where PHP saves the session data with the concrete.session.save_path configuration key

Yes, I have used that.
But if I save sessions in a user defined path, will concrete5 delete old session files? I am wondering if I need to setup some cronjob to clean the sessions folder.

Your host's open_basedir restrictions are not concrete5 bugs.


az aks list command doesn't work from windows terminal azure cloud shell

This is autogenerated. Please review and update as needed.
Describe the bug
az aks list returns error
Command Name
az aks list
Errors:
The command failed with an unexpected error. Here is the traceback:
'ContainerServiceClientConfiguration' object has no attribute 'api_version'
Traceback (most recent call last):
  File "/usr/lib64/az/lib/python3.9/site-packages/knack/cli.py", line 233, in invoke
    cmd_result = self.invocation.execute(args)
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 663, in execute
    raise ex
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 726, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 697, in _run_job
    result = cmd_copy(params)
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 333, in __call__
    return self.handler(*args, **kwargs)
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
    return op(**command_args)
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/command_modules/acs/custom.py", line 724, in aks_list
    return _remove_nulls(list(managed_clusters))
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/core/paging.py", line 129, in __next__
    return next(self._page_iterator)
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/core/paging.py", line 76, in __next__
    self._response = self._get_next(self.continuation_token)
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/mgmt/containerservice/v2022_07_01/operations/_managed_clusters_operations.py", line 977, in get_next
    request = prepare_request(next_link)
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/mgmt/containerservice/v2022_07_01/operations/_managed_clusters_operations.py", line 962, in prepare_request
    _next_request_params["api-version"] = self._config.api_version
AttributeError: 'ContainerServiceClientConfiguration' object has no attribute 'api_version'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
just run az aks list from azcli in windows termnial V 1.15.2875.0

Put any pre-requisite steps here...
az aks list

Expected Behavior
return a list of aks clusters
Environment Summary
Linux-5.4.0-1094-azure-x86_64-with-glibc2.35 (Cloud Shell), CBL-Mariner/Linux
Python 3.9.14
Installer: RPM

azure-cli 2.41.0

Extensions:
aks-preview 0.5.106
log-analytics 0.2.2
automation 0.1.0
spring-cloud 3.1.5
ai-examples 0.2.5
ml 2.10.0
ssh 1.1.2

Dependencies:
msal 1.20.0b1
azure-mgmt-resource 21.1.0b1

Additional Context

route to CXP team

@kennymu This has been resolved as part of this PR - #24270 - and should be available in the next release in a few days. Closing.


Minimal Mongo AST

https://jira.mongodb.org/browse/HIBERNATE-31

I didn't include AstNodeType for it is not used even in POC project. Will add them back if needed

I didn't include AstNodeType for it is not used even in POC project. Will add them back if needed

I included it in POC because it was used in LINQ, though I don't recall off hand what it was used for.

@NathanQingyangXu should we hold off on this and instead add AST nodes as needed to fully implement features?

@NathanQingyangXu should we hold off on this and instead add AST nodes as needed to fully implement features?

Yeah, I think that is more manageable and verifiable. I think we could close this ticket and plan to add AST node rendering incrementally in each of CRUD tickets.


cant bind v-tab disabled

Code like the following won't disable the tab
<v-tab :disabled="state.loading">
Hi
</v-tab>

v0.8.130 solved this


CLI: ansimail

Instead of having multiple files for each action, why not create a full file ansimail, and move each file into a function()? This way you will avoid duplicated code like

need root

Or an other idea, script it in Ruby, publish the gem.
Then you ll just need to do a gem install ansimail to install ansimail CLI.
Let me know your thoughts about that.
Also, i could help you on Ruby or Shell Scripting...

You can publish gem here: RubyGems

That function idea actually sounds really nice, but I feel this is less of a priority as compared to getting things working first. For the moment keeping them separated is going to be easier to debug, which is a higher priority than compactness.
I'll keep this open for now and get back to this after things have settled and we are nearing the first release.

Also I am not going to add ruby as a dependency so lets stick with shell.
I would appreciate the help with shell :)


Dell G5SE - "Supported hardware not detected"

Describe the bug
Seems G5 SE 5505 (4800H / 5600M) is not supported even though it seems like it should be
To Reproduce
Steps to reproduce the behavior:
I used latest version (4.2.2), UAC disabled, ran alienfan-gui / cli as admin, got the "supported hardware not detected" error.
Expected behavior
Able to control fans of my laptop.
Screenshots
N/A
Desktop (please complete the following information):

OS: W10 x64 20H2 (19042.1202)

Additional context
I read about needing test mode but also read that you don't need it anymore due to some kind of driver hack. I didn't get any warning or so so I assume the hack is working - but the control is not.
I can help with providing any dumps that may be needed.

Well... Only Intel-based G-series supported for now, i have this into readme. As well as Radeon not supported.
Now we fight with Ryzen-based G15 here, but still not works well.
If you have "Hardware not supported" - it means my SDK can't find command interface. Driver issues have other message - "Can't install driver".
So... Can you please install RWEverything, save your ACPI dump and share it with me?
I'll check what we can do.

Oh, my bad. I couldn't find the info in readme because I was looking at alienFX readme and not the alienfan one. My bad!
Here's the dump:
AcpiTbls.zip
Thank you very much!

It's my fault - so lazy to organize documentation right way...
So, i check your ACPI dump.
Bad news - Dell never provide 2 notebook lines with the same settings (as well as desktop ones)! You have other device NAME again - Mine and all Alienware has _SB.AMW1, G15 have _SB.AMW3, yours G5 - _SB.AMWW!
Also, they drop the whole control group i use for fan detection, so it will be different for your gear.
As well as make a mess with temperature readings from AWCC interface, i don't sure it will work correctly.
And, of course, you will not have GPU power control - it's for Nvidia only, but you can try to find analog for Radeon yourself.
Good news - The rest looks ok, you have 4 power modes (including manual), and boost read/write.
So let me add your interface version into the code, but better wait, then we are finish with G15 for precise fan control.
I'll drop you beta for compatibility test soon.

So, here is beta - alienfan-tools.zip with you gear support.
I recommend do not use GUI for now, but check CLI instead - start it from admin command prompt and play with switches to be sure all works well.
Also, read my last post into #46 and check your boost type - it should be PWM as well, so let me know which type works for you.

Thank you for the test version!
I tried launching the cli - it starts but hangs right after announcing its version.
C:\Programs\Programs\alienfx-tools>alienfan-cli.exe
AlienFan-cli v<IP_ADDRESS>

In fact I don't use AWCC right now (just nbfc, but the problem is I cannot control the GPU fan based on GPU temperature so I wanted to give your tool a try).
Anything else I can try to provide to help?

Thanks for support, it means i have a bug into new detection system.
Let me fix it and share updated version.
PS: I don't use AWCC as well - it was my target, then i develop alienfx-tools. ThrottleStop works better for under volt, and fx gui better control lights and fans. I even write LightFX emulation for games ^_^.

Try this version - alienfan-cli.exe.zip
Copy it into the same folder, overwrite old one (some files needed).
I add some checks and debug trace for detection process to see why it loops for your gear.

This new version just works, no issue on initialization:
C:\Programs\Programs\alienfx-tools>alienfan-cli.exe getfans
AlienFan-cli v<IP_ADDRESS>
Fan 50 found.
Fan 51 found.
Sensor 257 found.
Sensor 262 found.
Power mode 151 found.
Power mode 152 found.
Supported hardware detected, 2 fans, 2 sensors, 4 power states.
Fan#0 now at 0
Fan#1 now at 0
C:\Programs\Programs\alienfx-tools>alienfan-cli.exe temp
AlienFan-cli v<IP_ADDRESS>
Fan 50 found.
Fan 51 found.
Sensor 257 found.
Sensor 262 found.
Power mode 151 found.
Power mode 152 found.
Supported hardware detected, 2 fans, 2 sensors, 4 power states.
CPU Internal Thermistor: 42
GPU Internal Thermistor: 41
I tried setting the fans, it's a bit wonky with just setfans:
41 - not spinning
42 - 5pct
50 - 22pct
80 - 59pct
100 - 71pct
But with pwm I really don't know how that works at all... I was not able to get it to spin at any other speed than 66.5%
Seems none of the values do anything (even if the fan speed did change).
NBFC is able to control both fans reasonably fine, though it doesn't seem like it can bring them above 80pct. But control up to 80 works flawlessly. I don't know if the below thing tells you anything but that's my NBFC setting for fan control itself:

I tried setting some of the values between the ones you see with pwm but as mentioned, no real change, just 66.5pct on the random values I tried (even if the value of the getfanpwm kept changing).

Aha, so temps looks (can you check then system loaded?) ok... Great.
Most of the fan control tools uses EC access, but i have different approach and control trough ACPI calls - all Alienware and G have interface for AWCC, i'm just RE it and use.
According to EC control, you have PWM-based approach, but seems like AWCC interface re-count values for common boost approach. My current PWM code limited to 91 as a maximum, so that's why you have 70%.
Let me check you ACPI code more close, as well as some other checks.
For now, good news this approach works, bad are we still need to configure out limit values.

Oh, i check. You have 0..100 as a boost.
But real speed depend on power/unlock settings, it's indirect. So you can't fry CPU/GPU stopping fans under heavy load.

alienfan-tools.zip
Here you can try both GUI and CLI (i remove debug print as well).
But to check TOP fan speeds you need boost at 100 and hot system!

Aha, right. It was the same way in AWCC too - no direct speed, just "offsets". It seems to be working in the gui, I tried and GPU is controlled by GPU temp and CPU by CPU temp. Thank you so much!

It was the same way in AWCC too - no direct speed, just "offsets".

Yes. As i said, i use AWCC hardware interface, in fact. But this is a more safe way, and my app more flexible.
BTW, look at your cooling system first - There are no CPU and GPU fans, in common, they are just cool CPU or GPU mostly.
So i recommend always set both fans, but in different proportions.

NB: If you still want to have direct fan control also, try to play with AWCC interface:

Search your AWCC dump for "Method(WMAX" string.
It has 3 parameters, but only 2 of them used.
Read the AML code inside it, found suspicious combinations (most probably in group 0x15).
Try to issue it into hardware using alienfan-cli unlock direct=xx,xx,xx,xx command (f.e. alienfan-cli direct=14,5,32 return your CPU fan RPMs, and alienfan-cli direct=15,2,33,100 set max boost for GPU fan).

If you found command for your gear to set RPM/PWM directly, i'll support it.
You can also check your dump for Radeon power control method (for Nvidia it's \\_SB.PCI0.PEG0.PEGP.GPS, so look into the same zone), and i'll add GPU control as well.

Two things I suppose; the power control here is very complex, primarily because this laptop is one of the very few laptops that have smartshift. I don't think I want to play around with it too much.
Secondly, (and this I kind of noticed in AWCC as well), but the cooling doesn't really work well for the CPU temperature. As mentioned, in AWCC as well, the CPU temp from the EC was always a lot lower than the actual CPU temp reported by CPU, which makes sense if they are measured from some surface rather than internally, and the G5SE AMD version is notoriously known for bad cooling solution.
That said I need to control the CPU fan more proactively based on this so I'm going to play around with combination of nbfc and your tool.
And also yes I know, the fans are not really "separate", so I always set them both to the same thing; but it can be that I have some load that only stresses the GPU (or only the CPU) and in such case I want to spin up the fans more prominently "on that side", so to speak.

I got all power control modes from ACPI. You have 4 of them:

ID 0 (manual)
ID 97
ID 98
ID AB (BTW, it's hidden in modes list, and only available into the function)

I have no idea what PLs they set for CPU/GPU, you can check yourself using HWINFO.
I got it from function 0x15,0x1 of WMAX - you can check yourself.
Yes, fans is a menace. Dell make notebooks for cut the steak, not for work fast and long work load. For Alienware m-series overheat is near permanent issue. Question are - is BIOS fan control + boost squeeze all juice from fans at full load?
I don't get temps from EC, but from ACPI. Maybe it's wrong as well, but for my gear is close to real. Additionaly, at my gear i have 5 more temp sensors, even ambient one, and can tune fans for it.
Yes, different fan settings for different load. And yes, set them to 100% all the time not a good idea (as Performance mode do). But set opposite fan at 40-50 boost at asymmetric loading helps to cool too.
It was one of my target then i design this app. Any sensor now can control any fans at different level (resulted one will be highest). It's what i miss into AWCC, as well as multi-point curve.
BTW, please keep in mind - dynamic fan boost only works then GUI running - it's software, not hardware!

I assume that's all for now.

Yes it is! Thanks, it's working quite well - and you now have one more machine type you support! :D


dimension mismatch of vocabulary

https://github.com/hobincar/RecNet/blob/020b7fc4d71708ea256aa16ba87e153ee45543a5/configs/train_stage2.py#L16
Hi, I think you should add 'unk': 3 in train_stage2.py, or an error will be produced, that is,  size mismatch for out.weight: copying a param with shape torch.Size([9687, 512]) from checkpoint, the shape in current model is torch.Size([9686, 512]).

Thanks! I should have changed like that, but I didn't accidentally. I'll fix it right away.


HDDS-5851. [Ozone-Streaming] Define a PutBlock/maxBuffer fixed boundary for streaming writes.

What changes were proposed in this pull request?
Currently, putBlock call gets executed only during close() when a block is written. The aim here is to have a putBlock boundary similar to async path where the putBlock gets executed which updates the key length and help reduce some memory on client. The  default boundary here is set at 32 MB where a putBlock is executed.  Also a limit is set on the ByteBuffer size the client can send  here (4mb).
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-5851
How was this patch tested?
Unit test

Thanks @sadanand48 for the contribution.


Where can I download ade20k_instance_imgCatIds.json?

As the title says, where can I download ade20k_instance_imgCatIds.json? I can't find it below.
MIT Scene Parsing Benchmark http://sceneparsing.csail.mit.edu/

I solved it with the following issue.
https://github.com/facebookresearch/MaskFormer/issues/7