HTTPS Support

Hello,
I'm not sure if this is an actual issue or if I don't understand how it is supposed to work. But is there a possibility of using this connector with clickhouse cloud, so with a HTTPS connection?
If not, I think this could be really helpful.

This connector underlying uses the official clickhosue java client, so how do u achieve it through the official clickhosue java client?

Well, I can pass a full jdbc url like:  jdbc:clickhouse:http://localhost:8443?ssl=true&sslmode=STRICT
(Source: https://clickhouse.com/docs/en/integrations/java#jdbc-driver)
But I don't see a way to put this in this connector, because host and port are split up
spark-shell \ --conf spark.sql.catalog.clickhouse=xenon.clickhouse.ClickHouseCatalog \ --conf spark.sql.catalog.clickhouse.host="<path-to-host>.clickhouse.cloud" \ --conf spark.sql.catalog.clickhouse.protocol=https \ --conf spark.sql.catalog.clickhouse.http_port=8443 \ --conf spark.sql.catalog.clickhouse.user=<user> \ --conf spark.sql.catalog.clickhouse.password=<pw> \ --conf spark.sql.catalog.clickhouse.database=<db name>\ --repositories https://repo.maven.apache.org/maven2/ \ --packages com.github.housepower:clickhouse-spark-runtime-3.4_2.12:0.7.2,com.clickhouse:clickhouse-jdbc:0.4.6
If it is that obvious, maybe you can point me to my mistake. Thanks

Try appending
--conf spark.sql.catalog.clickhouse.option.ssl=true \
--conf spark.sql.catalog.clickhouse.option.sslmode=STRICT \

This works. Thank you!

thanks for the feedback, actually this question was asked a few times, in different approaches, someone asked how to pass custom options, and another guy asked how to enable SSL, let me update the docs to add it to the demo configurations


Add color scheme cisco_ios

I rebased the branch as requested in https://github.com/folkertvanheusden/multitail/pull/25.
Original Message:
I created a color scheme for Cisco IOS (and IOS-XE) logs.
It looks like this:

Thank you


UI - type explorer doesn't work

The select box 'Metadata server name' is empty

this only occurs if the server name is not picked up from the config. closing as we are reverting the change .


How to increase TOTAL_MEMORY for release_performance?

My game seems to require that. However, I can't figure out how to actually do it. Recompile emscripten somehow? Could you give an example please?

TOTAL_MEMORY is another flag that can be set on the Module object.
See this test for an example of how to set it at runtime and this configuration for the default value of that setting.

Thanks, the runtime example worked for me. I wouldn't know what to do with the config thing.
I added these lines to the html file in the Modules section:
buffer: new ArrayBuffer(3210241024),
TOTAL_MEMORY:<PHONE_NUMBER>,
Except that I had to increase the memory (I simply used times 2).
Whether the ArrayBuffer line was necessary I don't know, but it seemed reasonable to include it.
The performance increase was significant compared to the compatibility. The game is now playable in Firefox as well.


merge package template from arlac77/npm-package-template

package.json

chore(devDependencies): update<EMAIL_ADDRESS>from template

Codecov Report

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

@@          Coverage Diff           @@
##           master    #196   +/-   ##
======================================
  Coverage    92.3%   92.3%
======================================
  Files           2       2
  Lines          13      13
======================================
  Hits           12      12
  Misses          1       1

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 e92e48b...6cc5a42. Read the comment docs.

Coverage remained the same at 92.308% when pulling 6cc5a425fdef8ee11bcd87b7f812b510ad29bbe7 on template-sync-1 into e92e48ba54e2d28cc37b66671c2a9f51df37b0c1 on master.

Coverage remained the same at 92.308% when pulling 6cc5a425fdef8ee11bcd87b7f812b510ad29bbe7 on template-sync-1 into e92e48ba54e2d28cc37b66671c2a9f51df37b0c1 on master.


Fixing logo 404 errors

What is the context of this PR?
Fixes https://github.com/ONSdigital/eq-survey-runner/issues/1054
How to review
See if URLs resolve to images when running the app

Works as expected on branch.


Alias tokens that reference typography tokens are undefined

When using typography alias tokens within component tokens, the output variable is undefined.
Example of our typography token structure:
{
  "font": {
    "heading": {
      "xxl": {
        "value": {
          "fontFamily": "{font-family.cera-pro}",
          "fontWeight": "{font-weight.700}",
          "lineHeight": "{line-height.1}",
          "fontSize": "{font-size.9}",
          "letterSpacing": "{letter-spacing.1}",
          "paragraphSpacing": "{paragraph-spacing.1}",
          "paragraphIndent": "{paragraph-indent.1}",
          "textCase": "{text-case.none}",
          "textDecoration": "{text-decoration.none}"
        },
        "type": "typography"
      },

In the config file, I use the @tokens-studio/sd-transforms package to convert typography tokens into shorthand so that it doesn't just return [object Object]. Example of a variable I get after running style dictionary:
$font-heading-xxl: 700 64px/1 CeraPro;

This all works great, until I have alias tokens/components that reference the typography tokens.
Example of an component-specific token that references the alias typography token:
{
  "balance": {
    "type": {
      "title": {
        "value": "{font.paragraph.sm}",
        "type": "typography",
      },

I've tried dozens of custom transforms to try and see if I can manipulate the output, but no matter what I do I get this:
$balance-type-title: undefined undefined/undefined undefined;

If I dont use the shorthand transform from @tokens-studio/sd-transforms, then I get:
$balance-type-title: [object Object];

If I manually change the component's JSON file to have a type of "font" instead of "typography", it works, but manually changing all of the component JSON files is not a feasible solution and I have not found any other way to get usable output.

Thanks for raising this issue, I've reproduced this and marked it as a bug.


Add files via upload

Official website url: https://www.liceoariosto.edu.it/
URL of a page on the official website where a long-term (>1 year) IT related course is offered: https://www.liceoariosto.edu.it/index.php/orientamento/percorsi-liceali/11-liceo-scientifico-opzione-scienze-applicate
URL of a page or some other proof (.pdf or a screenshot are OK) showing that the university recognizes the domain which you are submitting as an official email domain for the enrolled students: https://i.imgur.com/OdwSoCT.png

@S2024 First stage of verification passed, official domain is liceoariosto.edu.it as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision. Proof of domain ownership: https://www.liceoariosto.edu.it/index.php/la-scuola/orari-e-contatti/email-e-telefoni

@S2024 Thank you for your patience while waiting for a review and processing your request. Pull request merged.

thank you!


default implementation for HBase index qps allocator

Allow config driven QPS allocator implementation for updating HBase Global Index.
Updating hoodie with default implementation that will not change any current behavior of index updates.

@v3nkatesh Left some comments, PTAL

@v3nkatesh Few minor follow up comments and 1 outstanding comment.

@v3nkatesh @n3nash any chance you can resolve this tonight? I'd like to cut a release early tomorrow.

@n3nash, addressed recent comments here -> https://github.com/apache/incubator-hudi/pull/685/commits/d6de18f0cba59ec180ac1535d294c3daee9721d7.
Pls take a look.

@v3nkatesh looks good to me but the build fails, can you take a look ?

@n3nash Just pushed a fix. Will see if the test succeeds.


Windows installer failed to build

The Mac build worked like a charm, but the Windows build failed here:
electron-builder electron/Lunchbox-win32-ia32 --platform=win --config=packager-config.json
I'm on OSX with all the other prerequisites. Here's the npm-debug.log
0 info it worked if it ends with ok
1 verbose cli [ 'node', '/usr/local/bin/npm', 'run-script', 'pack' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose node symlink /usr/local/bin/node
5 verbose run-script [ 'prepack', 'pack', 'postpack' ]
6 info prepack<EMAIL_ADDRESS>7 info pack<EMAIL_ADDRESS>8 verbose unsafe-perm in lifecycle true
9 info<EMAIL_ADDRESS>Failed to exec pack script
10 error<EMAIL_ADDRESS>pack: `npm run build && npm run pack:osx && npm run pack:win`
10 error Exit status 1
11 error Failed at the<EMAIL_ADDRESS>pack script.
11 error This is most likely a problem with the app-template package,
11 error not with npm itself.
11 error Tell the author that this fails on your system:
11 error     npm run build && npm run pack:osx && npm run pack:win
11 error You can get their info via:
11 error     npm owner ls app-template
11 error There is likely additional logging output above.
12 error System Darwin 14.0.0
13 error command "node" "/usr/local/bin/npm" "run-script" "pack"
14 error cwd /Users/mtdukes/Documents/development/lunchbox
15 error node -v v0.10.28
16 error npm -v 1.5.0-alpha-1
17 error code ELIFECYCLE
18 verbose exit [ 1, true ]

Any ideas?

OK, @TylerFisher pointed out my node was out of date and that I didn't run
brew install wine makensis
So did both of those. Now neither installer will build. Seems to fail in several places. Here's the npm-debug.log
0 info it worked if it ends with ok
1 verbose cli [ 'node', '/usr/local/bin/npm', 'run-script', 'pack' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose node symlink /usr/local/bin/node
5 verbose run-script [ 'prepack', 'pack', 'postpack' ]
6 info prepack<EMAIL_ADDRESS>7 info pack<EMAIL_ADDRESS>8 verbose unsafe-perm in lifecycle true
9 info<EMAIL_ADDRESS>Failed to exec pack script
10 verbose stack Error<EMAIL_ADDRESS>pack: `npm run build && npm run pack:osx && npm run pack:win`
10 verbose stack Exit status 1
10 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:214:16)
10 verbose stack     at EventEmitter.emit (events.js:110:17)
10 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:24:14)
10 verbose stack     at ChildProcess.emit (events.js:110:17)
10 verbose stack     at maybeClose (child_process.js:1015:16)
10 verbose stack     at Process.ChildProcess._handle.onexit (child_process.js:1087:5)
11 verbose pkgid<EMAIL_ADDRESS>12 verbose cwd /Users/mtdukes/Documents/development/lunchbox
13 error Darwin 14.0.0
14 error argv "node" "/usr/local/bin/npm" "run-script" "pack"
15 error node v0.12.7
16 error npm  v2.13.2
17 error code ELIFECYCLE
18 error<EMAIL_ADDRESS>pack: `npm run build && npm run pack:osx && npm run pack:win`
18 error Exit status 1
19 error Failed at the<EMAIL_ADDRESS>pack script 'npm run build && npm run pack:osx && npm run pack:win'.
19 error This is most likely a problem with the app-template package,
19 error not with npm itself.
19 error Tell the author that this fails on your system:
19 error     npm run build && npm run pack:osx && npm run pack:win
19 error You can get their info via:
19 error     npm owner ls app-template
19 error There is likely additional logging output above.
20 verbose exit [ 1, true ]

Nevermind! Started over after updating everything and it works great.

Hey, I am trying to build electron apps of lunchbox on Ubuntu; I did install wine and nsis but still get the following output.
Error: Invalid platform.
    at Object.build (/home/kashyap/Documents/lunchbox/node_modules/electron-builder/lib/osx.js:28:24)
    at Object.build (/home/kashyap/Documents/lunchbox/node_modules/electron-builder/index.js:73:42)
    at Object.<anonymous> (/home/kashyap/Documents/lunchbox/node_modules/electron-builder/cli.js:26:9)
    at Module._compile (module.js:652:30)
    at Object.Module._extensions..js (module.js:663:10)
    at Module.load (module.js:565:32)
    at tryModuleLoad (module.js:505:12)
    at Function.Module._load (module.js:497:3)
    at Function.Module.runMain (module.js:693:10)
    at startup (bootstrap_node.js:191:16)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>pack:osx: `electron-builder electron/Lunchbox-darwin-x64/Lunchbox.app --platform=osx --config=packager-config.json`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>pack:osx script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.


Fixed support for php-cs-fixer 2.9.0.

Fixes issue #71
Have tested with versions 2.8.4 and 2.9.0 of php-cs-fixer.
Updated the tests to pass, it seems current code generation libraries use self as a type hint when applicable.

Tests fail for 7.0; could it be that nikic/php-parser acts different depending on the PHP version?
The issue is with using a self typehint vs a class name.
In 7.0 we get the class name and in 7.1 we get self.


⚠ SkipTheCommericals has degraded performance

In 19f43f4, SkipTheCommericals ($STC) experienced degraded performance:

HTTP code: 200
Response time: 1733 ms

Resolved: SkipTheCommericals performance has improved in dfb2543.


How to pass an object to .actor()

Hi there,
I want to create an activity stream object as below:
{   "@context": "https://www.w3.org/ns/activitystreams",   "summary": "Sally accepted an invitation to a party",   "type": "Accept",   "actor": {     "type": "Person",     "name": "Sally"   },   "object": {     "type": "Invite",     "actor": "http://john.example.org",     "object": {       "type": "Event",       "name": "Going-Away Party for Jim"     }   } }
Here, the actor is the type of object but I'm unable to pass the object in .actor(),
Code snippet:
as.accept(). actor({     type: 'Person',     name: 'Sally'   })   .prettyWrite((err, doc) => {     if (err) throw err;     console.log(doc);   });
It gives me below error:
node_modules\activitystrea.ms\src\models\_base.js:415               else base.set(k, v);                         ^ TypeError: base.set is not a function
Please let me know if I'm doing it in a wrong way.
PS: Ignore code formatting.
Thanks.

.actor(
    as.person()
    .set('type', 'Person')
    .set('name', 'Sally')
  )

worked!


Write up documentation on our CLI tools

I suggest we create a markdown file called something like tools.md in https://github.com/scalameta/scalameta/tree/master/semanticdb looks.

It would be good to include --help and example usages for each tool.

Speaking of CLI tools, is using https://github.com/scopt/scopt an option on the table? It would simplify/normalize things like printing the help.

I've found scopt not to be very helpful since

--help causes sys.exit which makes it impossible to use as a library (from sbt-plugin, scalafix,  ...). You can configure scopt to not sys.exit on --help but in those cases you don't have a way to know if --help was called or not (unless you parse Array[String] yourself).
it doesn't save you from writing much boilerplate compared to parsing a List[String] by hand.

I agree we should implement --help however. I personally don't mind writing the --help text by hand.  The interface for metap/metacp is small.

I'll write something down today and submit a pull request.

Implemented in https://github.com/scalameta/scalameta/pull/1567.


Zone mismatches

Dear Brad Chapman,
Great tool you made! I've been playing with it a lot yesterday and today. I launches and relaunches a customized galaxy cloud instance in most cases.
There are however 2 issues:

Sometimes the amazon EC2 instance is launched in a different availability zone us-east1c instead of us-east-1b, therefore the stored snapshots of tools and data cannot be attached to the new instance. Here is the error:

13:16:56 - Retrieved file 'persistent_data.yaml' from bucket 'cm-e90ee86008a58c16f04d9ec29eebdb46' to 'pd.yaml'.
13:16:56 - Master starting
13:16:57 - Completed initial cluster configuration.
13:17:21 - PostgreSQL data directory '/mnt/galaxyData/pgsql/data' does not exist (yet?)
13:17:21 - Prerequisites OK; starting service 'SGE'
13:17:26 - Configuring SGE...
13:17:36 - Successfully setup SGE; configuring SGE
13:18:14 - Attaching volume 'vol-65c8be08' to instance 'i-7ea60e1c' as device '/dev/sdg3' failed. Exception: EC2ResponseError: 400 Bad Request InvalidVolume.ZoneMismatchThe volume 'vol-65c8be08' is not in the same availability zone as instance 'i-7ea60e1c'fd7371c2-acd6-43d1-9a16-8b5bd73f6df2

The size of the data partition is to small, it uses the full 2 GB. I therefore created a snapshot, created a volume of this snapshot of 6GB, created a snapshot of this again and managed to refer to this new snapshot in the yaml file. After this i could resize the new partition using xfs_resize -D 10000000 /dev/xdg2 (or whatever the volume of the galaxy-data partition). It would be usefull to have a bigger partition per default.

Keep up the great work, I hope I can contribute towards this.
Thomas

Thomas;
Thanks very much for the feedback. For problem 1, I pushed an updated version of BioCloudCentral that will consistently launch in us-east-1b to prevent this issue.
For problem 2, Enis (@afgane) is aware of that and was going to push a fix. We need a slightly larger Galaxy volume that has libraries for Python 2.7 and this should run smoothly again without the workaround. This is a fix on the CloudMan side but I'll leave this issue open until we sort that out.
Thanks again; let us know if you run into any other issues,
Brad

Hi Brad,
Thanks so much for the reply (on christmas) and the quick fixes. Everything
is working in zone 1-b now...
This time of the year is the only point at which I can really work on new
stuff. Figuring out how to set up and reorganize galaxy cloud-servers has
been on my to-do list for so long.
You're server goes a long way towards learning how to do this fast and
smart. Here's a couple of thoughts to make the experience even better.

Autobind an amazon elastic IP adress to the server that is instantiated.
By doing so the user can bookmark and link to the server whenever possible.
I for example do this in combination with lastpass to save the login for
the galaxy user etc.

to prevent newbies from incurring a huge bill:

Launching a "limited time" instance, for which the user can set the time
limit at the initiation of the server after which the server will
auto-terminate ~1hr after sending an email to the user that the server will
shutdown.

A link to the S3 bucket in which the relevant data for that server are
stored on the status page, this way the user get's aware of how the
'automagic' reloading of the cluster is done. You do not store any data of
the users yourself right? I can imagine a disclaimer of you not doing so
would convince people more easily to fill in their secret ID etc.

That's all I can think of for now. The service works like a charm. Enjoy
the downtime with christmas, and happy newyear already!
Cheers from the Netherlands,
Thomas
Met vriendelijke Groet,
Thomas van Gurp
On Sun, Dec 25, 2011 at 6:35 PM, Brad Chapman <
<EMAIL_ADDRESS>
wrote:

Thomas;
Thanks very much for the feedback. For problem 1, I pushed an updated
version of BioCloudCentral that will consistently launch in us-east-1b to
prevent this issue.
For problem 2, Enis (@afgane) is aware of that and was going to push a
fix. We need a slightly larger Galaxy volume that has libraries for Python
2.7 and this should run smoothly again without the workaround. This is a
fix on the CloudMan side but I'll leave this issue open until we sort that
out.
Thanks again; let us know if you run into any other issues,
Brad

Reply to this email directly or view it on GitHub:
https://github.com/chapmanb/biocloudcentral/issues/2#issuecomment-3271214

Thomas;
No problem, glad that worked out for you. Thanks for the nice ideas; I'm going to defer to @afgane on these as he is the CloudMan/boto expert but my thoughts are:

Elastic IPs would be awesome, but it doesn't look like the API supports a nice way to do this now since you can't associate metadata with an IP. Ideally you would create an Elastic IP named 'CloudMan your_name' in an account and then be able to pull it up next time. Unfortunately the API only lets you get IPs by number and then associate, so we don't have a good way to know that an existing IP is meant for a CloudBioLinux/CloudMan instance. If you know some workarounds through boto definitely please point us in the right direction.

This would be possible with some modifications to CloudMan, but it's worth thinking through. Learning to shutdown is a critical skill for Cloud work and I wonder if this would ease the learning curve or confuse users when they run a non-shutdown instance. The other worry is a failure to terminate via failed API calls potentially leaving "auto-shutdown" instances running. I'd love to hear Enis' thoughts.

More exposure for the S3 bucket is a great idea and the best place for this info would be in the CloudMan console. Enis, what do you think?

We don't currently store user entered data at all for security reasons. However. there are some cool things we could with accounts and stored data: like elastic IPs and easy push-button relaunch of instances. We could mitigate the security issues a bit by creating IAM instances to use only with CloudMan. So we're leaving open storing as a future option, depending on interest and feedback.

Thanks again,
Brad

Thomas;
Thanks that makes good sense. A lof of these ideas would need to be implemented directly in CloudMan, so Enis will be more knowledgeable about the best way to fit them in when he is back from holiday.
You can prepare your own custom AMIs that work with CloudMan starting from a base CloudBioLinux instance. You do need to clean up the AMI to remove old SGE/RabbitMQ and ssh information. The CloudBioLinux script has a target to do this:
https://github.com/chapmanb/cloudbiolinux
fab -f fabfile.py -H your_instance install_biolinux:cleanup

This wipes ssh keys in preparation for bundling, so would be a last step before building an AMI.
Hope this helps,
Brad

Brad;
thanks for the suggestions. However, I do not really see how I can make my
own custom AMI from an existing one. I created a base CloudBioLinux
instance and executed the cleanup with your fab-file. However, when I want
to create an AMI from this I get this message:
The instance you're using as a template for a new image has the following
volumes:

/dev/sda1, vol-8f6210e2 (), will delete on termination
/dev/sdg1, vol-7f601212 (), will not delete on termination
/dev/sdg2, vol-5b601236 (), will not delete on termination
/dev/sdg3, vol-b10f7ddc (100 GiB), will not delete on termination

Total size of EBS volumes: 100 GiB.
When you create an EBS image an EBS snapshot will also be created for each
of the above volumes.
This means tha /dev/sda1 will always be deleted/reset on termination,
meaning that each time that I modify the 'base' volume I need to recreate
another AMI. This is rather cumbersome but doable. Wouldn't it be easier to
set an option to persist changes in the root partition on instantiation or
am I missing something here?
Kind regards,
THomas
Met vriendelijke Groet,
Thomas van Gurp
On Mon, Dec 26, 2011 at 11:47 AM, Brad Chapman <
<EMAIL_ADDRESS>
wrote:

Thomas;
Thanks that makes good sense. A lof of these ideas would need to be
implemented directly in CloudMan, so Enis will be more knowledgeable about
the best way to fit them in when he is back from holiday.
You can prepare your own custom AMIs that work with CloudMan starting from
a base CloudBioLinux instance. You do need to clean up the AMI to remove
old SGE/RabbitMQ and ssh information. The CloudBioLinux script has a target
to do this:
https://github.com/chapmanb/cloudbiolinux
fab -f fabfile.py -H your_instance install_biolinux:cleanup
This wipes ssh keys in preparation for bundling, so would be a last step
before building an AMI.
Hope this helps,
Brad

Reply to this email directly or view it on GitHub:
https://github.com/chapmanb/biocloudcentral/issues/2#issuecomment-3273891

Thomas;
Apologies for the confusion, I meant that you can create an AMI directly using the Amazon tools:

Boot a CloudBioLinux instance; don't start up any services
Configure the AMI with your custom tools
Run the CloudBioLinux fabfile to clean up
Create an AMI using the AWS EC2 console

Then you can boot your next CloudMan instance from your custom AMI via the console.
CloudMan currently doesn't have any way to do this directly. It is tricky since preparing the AMI requires tearing down all the services and stripping the base instance.
Another option is the post_start_script_url option in the user-data:
http://wiki.g2.bx.psu.edu/Admin/Cloud/UserData
This runs a supplied script after all the services have started, so you can write a script to install your custom libraries on top of what CloudBioLinux provides. This totally removes the need to have a separate AMI so may be much cleaner for your purposes. Here's an example script I use:
https://github.com/chapmanb/cloudbiolinux/blob/master/utils/cbl_exome_setup.py
Hope this helps,
Brad

Hi Thomas,
Sorry for a bit of delay in getting back to this.
As far as your comments:

the elastic IP address is an interesting option. I actually looked into
using it a while ago and decided not to go with it because of the
associated cost. The cost of this service was 10 cents/hour while the
address was not in use and considering these clusters were intended for
periodic use, the cost just did not seem justified. However, I just checked
and the IP address cost seems to have come down to 1 cent/hour so it may be
acceptable now, especially as a user-enabled option. I'll look into it.

The auto-shutdown instances are an interesting idea, but like Brad said,
somewhat controversial. The available auto-scaling option tries to minimize
the cost of running the cluster by reducing the size of it to the absolute
minimum when the cluster is not in use but that obviously does not
terminate it. The email notification part also raises some requirements
because CloudMan does not currently have access to user's email address.
Maybe some form of countdown on the main UI plus a check that there are no
jobs running could be used instead? Still, the biggest issue is a failed
API call that breaks the termination and lack of ability to inform the
user... This should not happen very frequently though so maybe the best
option is to implement the feature and test its acceptance?

A link to cluster's bucket on S3 is a good idea. I'll add that on the
Admin page.

Thanks for the suggestions,
Enis
On Mon, Dec 26, 2011 at 3:05 AM, Brad Chapman <
<EMAIL_ADDRESS>
wrote:

Thomas;
No problem, glad that worked out for you. Thanks for the nice ideas; I'm
going to defer to @afgane on these as he is the CloudMan/boto expert but my
thoughts are:

Elastic IPs would be awesome, but it doesn't look like the API supports
a nice way to do this now since you can't associate metadata with an IP.
Ideally you would create an Elastic IP named 'CloudMan your_name' in an
account and then be able to pull it up next time. Unfortunately the API
only lets you get IPs by number and then associate, so we don't have a good
way to know that an existing IP is meant for a CloudBioLinux/CloudMan
instance. If you know some workarounds through boto definitely please point
us in the right direction.

This would be possible with some modifications to CloudMan, but it's
worth thinking through. Learning to shutdown is a critical skill for Cloud
work and I wonder if this would ease the learning curve or confuse users
when they run a non-shutdown instance. The other worry is a failure to
terminate via failed API calls potentially leaving "auto-shutdown"
instances running. I'd love to hear Enis' thoughts.

More exposure for the S3 bucket is a great idea and the best place for
this info would be in the CloudMan console. Enis, what do you think?

We don't currently store user entered data at all for security reasons.
However. there are some cool things we could with accounts and stored data:
like elastic IPs and easy push-button relaunch of instances. We could
mitigate the security issues a bit by creating IAM instances to use only
with CloudMan. So we're leaving open storing as a future option, depending
on interest and feedback.

Thanks again,
Brad

Reply to this email directly or view it on GitHub:
https://github.com/chapmanb/biocloudcentral/issues/2#issuecomment-3272343


Angular2_CLI_Starter  Table can't responsive

scss core/_layout.scss
.app-body {
display: flex;
flex-grow:1;
flex-direction: row;
overflow-x: hidden;
.main {
flex: 1;
}
.sidebar {
// $sidebar-width is the width of the columns
flex: 0 0 $sidebar-width;
// put the nav on the left
order: -1;
}
.aside-menu {
// $aside-menu-width is the width of the columns
flex: 0 0 $aside-menu-width;
}
}
when delete .app-body{ display:flex;}  table can responsive ,.but layout will be crash.
please how to solve it . thanks all

Do you have any screenshots?

in Angular2_CLI_Starter Project
dashboard.component.html code

    Hello World!

      #
      First Name
      Last Name
      Username
      Username
      Username

      1
      Mark
      Otto
      @mdo
            Otto
      @mdo

      2
      Jacob
      Thornton
      @fat
            Otto
      @mdo

      3
      Larry
      the Bird
      @twitter
            Otto
      @mdo

in mobile picture can't responsive

+1. Responsive tables aren't working on CoreUI @mrholek

facing same issue.


Upgrade OpenSSL from 3.0.0 to 3.0.7

There is a high severity exploit that affects both SSL clients and servers.
https://nvd.nist.gov/vuln/detail/CVE-2022-3602
https://www.malwaretech.com/2022/11/everything-you-need-to-know-about-the-openssl-3-0-7-patch.html
It's been addressed in 3.0.7
The recommendation is to upgrade 3.0.0 to 3.0.7 asap.

I thought I'd document my procedure for addressing this.  First I checked to see what changes we made in our copy of the openssl repo with git log contrib/openssl.  There was only one update, which affected strerror_r.  Here's how I did this, with the results inline:
> cd /home/cribl/appscope/
> git log contrib/openssl
commit 6da7234c41b68bdd6b6a9c24bcc43892c689364a
Author: michalbiesek<EMAIL_ADDRESS>Date:   Sat Apr 23 22:17:42 2022 +0200

    [LOGICAL CHANGE] `strerror_r` change

    - use only XSI-compliant version since musl libc doesn't provide
      the GNU-specific verison
    Ref: https://linux.die.net/man/3/strerror_r

commit<PHONE_NUMBER>7cdb0e89be277054483c35ae6f2d54
Author: john<EMAIL_ADDRESS>Date:   Tue May 11 02:52:04 2021 +0000

    (#164) Control openssl in contrib directory.
    Was cloned from https://github.com/openssl/openssl
    Using refs/tags/openssl-3.0.0-alpha16 of the master branch.

This was how I figured out what files were affected, and how I created a patch file of these changes, so I could make these again after updating to 3.0.7:
> git diff 6da7234c41^ 6da7234c41 | grep "diff --git | grep openssl"
diff --git a/contrib/openssl/crypto/o_str.c b/contrib/openssl/crypto/o_str.c
> git diff 6da7234c41^ 6da7234c41 > ~/openssl.patch

Now I just wiped out all of contrib/openssl in git (the 3.0.0 version), and replaced it with the 3.0.7 version.
> git rm -r contrib/openssl
> ls -al contrib/openssl
total 12
drwxrwxr-x  3 ubuntu ubuntu 4096 Nov 15 17:47 .
drwxrwxr-x 15 ubuntu ubuntu 4096 Nov 15 15:08 ..
drwxrwxr-x  4 ubuntu ubuntu 4096 Nov 15 17:47 doc
> rm -rf contrib/openssl
> mkdir contrib/openssl
> git clone https://github.com/openssl/openssl ~/openssl
> cd ~/openssl
> git checkout openssl-3.0.7
> git archive openssl-3.0.7 | tar -x -C /home/cribl/appscope/contrib/openssl
> cd /home/cribl/appscope/contrib/openssl
> git add --force .
> git commit

Now I needed to reapply the changes we made in 6da7234c41:


Add Contract Tests for LLM Attributes and Models

Description of changes:
Add new contract tests for Gen AI attributes and models.
Test Plan:

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 71.54%. Comparing base (09e6487) to head (f7c0b9f).
Report is 369 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@              Coverage Diff              @@
##               main     #952       +/-   ##
=============================================
- Coverage     85.71%   71.54%   -14.17%
- Complexity       19      305      +286
=============================================
  Files             3       26       +23
  Lines            49     1093     +1044
  Branches          5      145      +140
=============================================
+ Hits             42      782      +740
- Misses            3      265      +262
- Partials          4       46       +42

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


use unified version number

@jdcasey
I try to reacting the pom, use unified version number.
Let release pipeline easy to analysis pom.xml
But , I find one dependency

org.commonjava.indy.docker
indy-docker-gogs-testbase
tar.gz
1.0.1-SNAPSHOT
provided

the version different all indy models, What should I do for the sun model?

Let's wait on this. I have a set of steps I think we need to execute before we can do a good job with the release pipeline. I've been researching this, and I really think we need to have a clearer idea of the design we want first.
I'm not sure what you mean by 'sun model'

sorry  sub model
On Tue, Apr 17, 2018, 6:51 AM John Casey<EMAIL_ADDRESS>wrote:

Let's wait on this. I have a set of steps I think we need to execute
before we can do a good job with the release pipeline. I've been
researching this, and I really think we need to have a clearer idea of the
design we want first.
I'm not sure what you mean by 'sun model'
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Commonjava/indy/pull/929#issuecomment-381774652, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAMzUUzr9mpAKBBQTy-16rO5auswJSfHks5tpSBkgaJpZM4TWHo2
.


d3m exceptions StepFailedError

d3m.exceptions.StepFailedError: Step 7 for pipeline c43355b7-0e87-499f-a9f2-defc56b6713a failed
I have trained this model using fit.py on your given dataset and saved weights in the weights directory than I run produce.py these two files run smoothly.
But when I try to run recognize.py it gives me this exception.

@muneebsaif Could you provide the full traceback. It seems that it runs smoothly in my end.

I'm also having a similar problem trying to do recognition in your demo video, I'm using the fitted_pipeline that I trained using your fit.py example file.
I just installed yesterday autovideo and torch on a fresh python 3.8 conda environment.
I'm using Torch version '1.12.1+cu102'.
autovideo version 1.2.4
Could it be caused by the Torch version? Which one are you using?
Here is the error:
predictions = produce_by_path(fitted_pipeline, video_path)

[INFO:3643289 frame_extraction:110 2022-09-27 13:06:10,985] demo done with 178 out of 179 frames
/usr/local/anaconda3/envs/autovideo1/lib/python3.8/site-packages/torchvision/transforms/transforms.py:332: UserWarning: Argument 'interpolation' of type int is deprecated since 0.13 and will be removed in 0.15. Please use InterpolationMode enum.
warnings.warn(
Traceback (most recent call last):
File "/usr/local/anaconda3/envs/autovideo1/lib/python3.8/site-packages/d3m/runtime.py", line 1114, in _do_run_step
self._run_step(step)
File "/usr/local/anaconda3/envs/autovideo1/lib/python3.8/site-packages/d3m/runtime.py", line 1102, in _run_step
self._run_primitive(step)
File "/usr/local/anaconda3/envs/autovideo1/lib/python3.8/site-packages/d3m/runtime.py", line 988, in _run_primitive
multi_call_result = self._call_primitive_method(primitive.multi_produce, multi_produce_arguments)
File "/usr/local/anaconda3/envs/autovideo1/lib/python3.8/site-packages/d3m/runtime.py", line 1078, in _call_primitive_method
raise error
File "/usr/local/anaconda3/envs/autovideo1/lib/python3.8/site-packages/d3m/runtime.py", line 1074, in _call_primitive_method
result = method(**arguments)
File "/usr/local/anaconda3/envs/autovideo1/lib/python3.8/site-packages/d3m/primitive_interfaces/base.py", line 426, in multi_produce
return self._multi_produce(produce_methods=produce_methods, timeout=timeout, iterations=iterations, inputs=inputs)
File "/usr/local/anaconda3/envs/autovideo1/lib/python3.8/site-packages/d3m/primitive_interfaces/base.py", line 450, in _multi_produce
results.append(getattr(self, method_name)(timeout=timeout, iterations=iterations, **arguments))
File "/usr/local/anaconda3/envs/autovideo1/lib/python3.8/site-packages/autovideo/base/transformation_base.py", line 38, in produce
next_null_idx = inputs[inputs["transformation"].isnull()].index.tolist()[0]
IndexError: list index out of range
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/tmp/ipykernel_3620077/2459137678.py", line 1, in <cell line: 1>
predictions = produce_by_path(fitted_pipeline, video_path)
File "/usr/local/anaconda3/envs/autovideo1/lib/python3.8/site-packages/autovideo/utils/axolotl_utils.py", line 104, in produce_by_path
predictions = produce(test_dataset=dataset,
File "/usr/local/anaconda3/envs/autovideo1/lib/python3.8/site-packages/autovideo/utils/axolotl_utils.py", line 82, in produce
raise pipeline_result.error
File "/usr/local/anaconda3/envs/autovideo1/lib/python3.8/site-packages/d3m/runtime.py", line 1155, in _run
self._do_run()
File "/usr/local/anaconda3/envs/autovideo1/lib/python3.8/site-packages/d3m/runtime.py", line 1131, in _do_run
self._do_run_step(step)
File "/usr/local/anaconda3/envs/autovideo1/lib/python3.8/site-packages/d3m/runtime.py", line 1119, in _do_run_step
raise exceptions.StepFailedError(
StepFailedError: Step 7 for pipeline 4ad30d1d-1f04-47fb-bf9b-efc55bf840f8 failed.

Thanks in advance

Similar issue here : https://github.com/datamllab/autovideo/issues/14 with the hack required to work


Ability to swipe left & right when picking images to send

(accidentally filed originally at https://github.com/vector-im/vector-web/issues/1630)


Update readme to remove old content

Updated Readme per #1258
Critical Changes
Changes
Issues Closed

@mkolodner I think it was because I called the branch feature- rather than feature/ so I recreated it - well, it auto closed the old one when I renamed it. I think this one should pass - fingers crossed.


[BUG] DWD wrongfully scales down resources when api-server takes more than 10s to respond

Describe the bug:
Currently the DWD probe has a timeout of 10s which at times fails when there is request latency of higher than 10s.
In such cases the api-server is reachable and kubelet is also able to update it's heartbeat, however DWD assumes that api-server is not reachable and bring the KCM/MCM/CA down.
Expected behaviour:
DWD should honor the same timeout as set for kubelet.
How To Reproduce (as minimally and precisely as possible):
Create load on the kube-apiserver with high request load resulting latency values beyond 10s to respond.
This should eventually fail the external probe and will eventually bring down the components although the api-server is reachable from the node albeit slow.
Logs:
Screenshots (if applicable):
Anything else we need to know?:

Kubelet configuration:
nodeStatusUpdateFrequency is set to 10s - this is the duration that kubelet will compute node status.
nodeStatusReportFrequency is set to 0s
There is no value set for nodeLeaseDurationSeconds which is defaulted to 40s. This is the duration for which the node lease is valid. The default duration for kubelet to update its lease is 10s.
There is no explicit timeout set on the client that is used by the kubelet to reach KAPI.
On KCM:
node-monitor-grace-period is set to 2m0s (120sec). This means that KCM only moves a node to Unknown state.
On DWD
Current configurations:

Frequency with which probe is called is 10s (sliding - which means computes 10s after the current sync probe function call returns).
Total timeout for probe is 10s

We will change this to:

Total timeout for probe: 30s
In the edge case where the KAPI fails to respond in 30s, then with a failure threshold of 3, total time that the probe will wait will be (30+10)*3 = 120 sec before it breaches the failure threshold and initiates scaling down operation. This is in line with total time KCM allows the kubelet to update its lease as well.

Reference links:

https://kubernetes.io/docs/reference/command-line-tools-reference/kube-controller-manager/
https://kubernetes.io/docs/reference/config-api/kubelet-config.v1beta1/

As part of the fix:

Default timeout for client used to probe the kube API server is now set to 30s (earlier 10s)
A new configuration property (optional) has been introduced probeTimeoutSeconds. The default value of 30s can be overriden by explicitly specifying a new value via this configuration property.


allow to choose a name for files created locally

hello,
it would be great to be able to set the file name, not just the directory for locally created files.
thanks! best,
dan

Closing as captured in #54


PSCIS 197656 not in latest lookup

All the other crossings from funding_project = 'Bulkley River Watershed Fish Passage Restoration Phase 1 - 2020' are present, not sure why this one got missed.

Closed with https://github.com/smnorris/bcfishpass/commit/b67333d88b41696bf707a2bd4d44e4292d523827
@njohanley - not sure what went wrong here, I've applied the spot fix

Closed with https://github.com/smnorris/bcfishpass/commit/b67333d88b41696bf707a2bd4d44e4292d523827
@njohanley - not sure what went wrong here, I've applied the spot fix


Adapt for container-based builds on Linux and builds on OS X

Builds on OS X fail, I guess because of the dynamic libraries naming conventions.

Thanks a lot!


Provide a step that allows to test errors and exceptions

Basically we need a step that will be matching returned error by a pattern, for example:
I should get SOAP Fault error matching "Specified ID \d+ doesn't exist"
The idea is that we can catch the exception in SoapManager::sendRequest and match the exception message in the step, but the tricky part is how do we throw this exception back, or even don't catch it at all when we don't except errors.
I can think of 2 approaches now:
1. Using tags
Tag a scenario with a specific tag that means we're expecting an error, so when SoapManager::sendRequest runs, it will be sure to catch that exception.
Pros:

Clean implementation and usage

Cons:

Requires additional steps from the user, like tagging their scenarios
Once scenarios is tagged once, all SOAP calls in this scenario will not throw exceptions

2. Using afterStep magic
We can catch any exceptions returned in SoapManager::sendRequest but after every step that is not equal to the send request step we check if there is an exception saved and not cleaned out, and throw it. In our new exceptions matching step we can unset the exception from context class before afterStep hook executes so that scenario will not fail.
Pros:

Less work to do in feature files, you just except exception and Behat figures it out, no explicit tagging

Cons:

Not very clear what magic happens
AfterStep will fire only during next step, not during send request steps, so if send request step is the last one, the afterstep will not throw the exception and will pass the test silently, which we probably can check for step not being the last one in the scenario, but Behat provides no clean way to do that.
The message about exception occurred when the exception message doesn't match the provided pattern will appear under the next step, rather then after send request step, this can be a little confusing
If you use no exception checking steps, the exception will appear under a totally different step with the afterStep comment and will confuse users.

Example of confusing step execution output:

This is resolved and merged in #11
@sergiuteaca please give it a try and let us know if you see any bugs or some enhancements are required


Low Fidelity and High Fidelity for Mobile, Tablet and desktop design

High and low fidelity designs for Team Herringpp Landing page (Desktop, Tablet and Mobile) view

@RUKAYAT-CODER please change the name of our web app to chunkit

Name Changed from chunking to Chuk It plus little modification like, logo and colors

Chunking changed to chunk It. plus little  modifications to color and logo


gh/workflows: Disable BPF masq in ci-datapath

It seems to be broken in the direct routing mode. Disable for now in all configurations.
Successful run - https://github.com/cilium/cilium/actions/runs/3952387001/jobs/6767397972.

For the record, this is meant to fix the following fallout in the bpf-next test:

📋 Test Report
❌ 5/31 tests failed (12/237 actions), 0 tests skipped, 0 scenarios skipped:
Test [no-policies]:
connectivity test failed: 5 tests failed
❌ no-policies/pod-to-world/http-to-one.one.one.one-0: cilium-test/client-755fb678bd-r9qf5 (<IP_ADDRESS>) -> one.one.one.one-http (one.one.one.one:80)
❌ no-policies/pod-to-world/https-to-one.one.one.one-0: cilium-test/client-755fb678bd-r9qf5 (<IP_ADDRESS>) -> one.one.one.one-https (one.one.one.one:443)
❌ no-policies/pod-to-world/https-to-one.one.one.one-index-0: cilium-test/client-755fb678bd-r9qf5 (<IP_ADDRESS>) -> one.one.one.one-https-index (one.one.one.one:443)
❌ no-policies/pod-to-world/http-to-one.one.one.one-1: cilium-test/client2-5b97d7bc66-dm6bd (<IP_ADDRESS>) -> one.one.one.one-http (one.one.one.one:80)
❌ no-policies/pod-to-world/https-to-one.one.one.one-1: cilium-test/client2-5b97d7bc66-dm6bd (<IP_ADDRESS>) -> one.one.one.one-https (one.one.one.one:443)
❌ no-policies/pod-to-world/https-to-one.one.one.one-index-1: cilium-test/client2-5b97d7bc66-dm6bd (<IP_ADDRESS>) -> one.one.one.one-https-index (one.one.one.one:443)
Test [to-entities-world]:
❌ to-entities-world/pod-to-world/http-to-one.one.one.one-0: cilium-test/client-755fb678bd-r9qf5 (<IP_ADDRESS>) -> one.one.one.one-http (one.one.one.one:80)
❌ to-entities-world/pod-to-world/http-to-one.one.one.one-1: cilium-test/client2-5b97d7bc66-dm6bd (<IP_ADDRESS>) -> one.one.one.one-http (one.one.one.one:80)
Test [client-egress-l7]:
❌ client-egress-l7/pod-to-world/http-to-one.one.one.one-1: cilium-test/client2-5b97d7bc66-dm6bd (<IP_ADDRESS>) -> one.one.one.one-http (one.one.one.one:80)
Test [client-egress-l7-named-port]:
❌ client-egress-l7-named-port/pod-to-world/http-to-one.one.one.one-1: cilium-test/client2-5b97d7bc66-dm6bd (<IP_ADDRESS>) -> one.one.one.one-http (one.one.one.one:80)
Test [to-fqdns]:
❌ to-fqdns/pod-to-world/http-to-one.one.one.one-0: cilium-test/client-755fb678bd-r9qf5 (<IP_ADDRESS>) -> one.one.one.one-http (one.one.one.one:80)
❌ to-fqdns/pod-to-world/http-to-one.one.one.one-1: cilium-test/client2-5b97d7bc66-dm6bd (<IP_ADDRESS>) -> one.one.one.one-http (one.one.one.one:80)
Error: Process completed with exit code 1.

/test

Is there a release-blocking issue to track re-enabling this test? Why is it broken?

Is there a release-blocking issue to track re-enabling this test? Why is it broken?

@squeed I'm currently investigating this. Could be just matter of the KIND configuration, and I will keep posted.

Do we need an issue to track this and eventually reenable it?

:+1: If I don't fix it by EOD, then I will create an issue.

https://github.com/cilium/cilium/issues/23283 :thinking:


Mlmodel Face recognition

Will you add some Core ML models for Face recognition (age, gender) ? Thanks

There are no plans to add Core ML models for this demo at this time.


RI-376 Make RPCO master point to OSA master

We are moving master from Queens to Rocky.
Issue: RI-376

recheck_all

That error is due to the bug addressed by this patch https://review.openstack.org/#/c/583077/, since it's merged a recheck should clear it up.

recheck_ container_releasenotes_tox-test

recheck_ container_releasenotes_tox_test

recheck_xenial_no_artifacts_swift_deploy


Refactor typecheck.rkt

This refactors class/instance-specific logic out of typecheck.rkt and then hides details about how type contexts are implemented. The purpose of this change is to make it easier to change the representation of type contexts (step towards fixing issue #70 and #62), and to allow me and Alex to hack on the type checker more easily.

This looks good, thanks!


localization for form-contact.html shortcode

I translated the static text in the form-contact.html shortcode to all supported langages.
German is my mother tongue, the rest I translated with DeepL (except for Chinese, there I had to use Google Translate).
This fixes #184

Thanks, @eddex


[networks] Log when DNS inspection is enabled but not supported

What does this PR do?
Log when DNS inspection is enabled but not supported. Also cleanup DNS inspection initialization code a little bit
Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
Describe your test plan
Write there any instructions and details you may have to test your PR.

This could probably use a rebase as well to make CI happy.


IPO - First day (Lifetime first day candle) bullish break

Ive looked under X13 but have not been able to find the required.
Requesting a scanner to list IPO stock whose first day candle is the All time high candle after 2 days of listing. (Attached are 4 examples).
I.e. the IPO stock is bearish immediately after listing.
Looking to avoid listing any IPO stocks where the first day candle high has already been broken by candles in the following days.
.
Based on backtest, a break of first day candle can give about 20% return in 50% cases and 5%Sl in 50%.
Telegram (notnapster)

@notnapster - In the examples above, would your expectation be t have all of the stocks in the samples included or is the expectation to include only Awfis space solutions and Krystal integrated because in these two cases, the first candle was the all time high for the first few days after listing, but other examples you've provided do not fit into that criteria (Stanley and Mukka's high was broken on day 2 candle)
Can you please confirm my understanding?


Empty Element Renders

Following the directions on your README and this blog, I keep getting an empty element that doesn't show the svg. Any ideas?

My svg file is proper.
webpack.config.js (or at least the one that matters, I have configs for each environment but they webpack-merge with this one):
// webpack config
const webpack = require('webpack');
const path = require('path');

module.exports = function() {
  return {
    context: path.join(__dirname, '..', '..'),
    entry: './src/index.jsx',
    output: {
      path: './build/',
      filename: 'bundle.js',
      sourceMapFilename: 'map',
    },
    module: {
      rules: [
        {
          test: /\.(js|jsx)$/,
          exclude: /node_modules/,
          use: 'babel-loader',
        }, {
          test: /\.svg$/,
          include: /assets/,
          use: ['babel-loader', 'svg-react-loader'],
        }
      ]
    },
    resolve: {
      modules: [
        'node_modules',
      ],
    },
  };
};

chatBubble.jsx:
import React from 'react';
import ReactDOM from 'react-dom';
import bubbleIcon from '../assets/bubble.svg'; // TODO: doesn't show properly yet

const buttonStyle = {
  width: 500,
  height: 500,
  position: 'absolute',
  bottom: 3,
  right: 3
};

const bubbleButton = () => (
  <button style={buttonStyle}>
    <bubbleIcon />
    bubble
  </button>
);

export default bubbleButton;

index.jsx (mainly for HMR):
import React from 'react';
import ReactDOM from 'react-dom';
// AppContainer is a necessary wrapper component for HMR
import { AppContainer } from 'react-hot-loader';
import chatBubble from './chatBubble.jsx';

const render = (Component) => {
  ReactDOM.render(
    <AppContainer>
      <Component/>
    </AppContainer>,
    document.getElementById('root')
  );
};

render(chatBubble);

// Hot Module Replacement API
if (module.hot) {
  module.hot.accept('./chatBubble.jsx', () => {
    render(chatBubble)
  });
}

@Mingling94 You're configuration is using react-svg-loader not svg-react-loader
Also, you probably want an include and/or exclude directive on that loader configuration (limit it to a specific folder, or exclude font folders, etc...)

@jhamlet Oh sorry, I did make that error before and fixed it. I just pasted the erroneous code in. Now updated, could I bother you for another glance?
Thanks for the include suggestion :)

@Mingling94 Looking closer I see that your Element's tab is showing the element actually as a <buttonicon> tag. Which I would expect to see <svg...>
What do the contents of your bubble.svg look like?

Same, I thought that odd. I've never gotten it to show as an <svg> element.
bubble.svg:
<?xml version="1.0" encoding="utf-8"?>

<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
<svg version="1.1" id="Layer_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"
	 width="201px" height="96px" viewBox="0 0 201 96" enable-background="new 0 0 201 96" xml:space="preserve">
<path fill-rule="evenodd" clip-rule="evenodd" fill="#FFFFFF" d="M153,96H13C5.847,96,0,90.156,0,83V13C0,5.844,5.844,0,13,0h140
	c26.508,0,48,21.492,48,48S179.507,96,153,96"/>
<path fill-rule="evenodd" clip-rule="evenodd" fill="#6ACFE8" d="M153,93c24.853,0,45-20.147,45-45c0-24.853-20.147-45-45-45H13
	C7.503,3,3,7.503,3,13v70c0,5.496,4.5,10,10,10H153z"/>
<path fill-rule="evenodd" clip-rule="evenodd" fill="#FFFFFF" d="M153,12c-19.883,0-36,16.118-36,36s16.117,36,36,36
	c19.882,0,36-16.118,36-36S172.881,12,153,12"/>
<path fill-rule="evenodd" clip-rule="evenodd" fill="#6ACFE8" d="M153,41.581c3.545,0,6.42,2.874,6.42,6.42
	c0,3.545-2.875,6.42-6.42,6.42c-3.546,0-6.42-2.875-6.42-6.42C146.58,44.455,149.454,41.581,153,41.581 M153,34.119
	c7.666,0,13.881,6.215,13.881,13.882c0,2.202-0.514,4.285-1.427,6.135l0.432-0.269c0,0-0.994,2.771-0.497,4.762
	s0.497,4.478,0.497,4.478s-0.497-0.498-2.279-1.225c-1.249-0.509-5.949-0.305-8.655-0.137c-0.638,0.09-1.289,0.137-1.951,0.137l0,0
	c-7.667,0-13.882-6.215-13.882-13.881C139.118,40.333,145.333,34.119,153,34.119z M153,24.801c12.812,0,23.198,10.387,23.198,23.199
	v18.09c0,2.821-2.287,5.108-5.108,5.108c-2.457,0-4.509-1.734-4.998-4.046c-3.726,2.553-8.234,4.046-13.092,4.046
	C140.187,71.199,129.8,60.812,129.8,48C129.8,35.188,140.187,24.801,153,24.801z"/>
</svg>

@jhamlet Hey, any ideas on what I may be doing wrong? Want to look at my repo for a full view of the project?

@Mingling94 Yeah. That could help.
Also, you arer using the public release of<EMAIL_ADDRESS>correct? I did a re-write that no longer requires babel if you install svg-react-loader@next I wonder if that might solve this?
I haven't released it yet, as I'm still hoping to get more testing done (using Enzyme), but have not had the bandwidth.
;-j

@jhamlet  installed svg-react-loader@next and it installed ^0.4.0-beta.2 which worked for me. Thanks! I'm still not sure why the public release wasn't working for me.

your problem in import bubbleIcon from '../assets/bubble.svg'; component name))) Please read react docs

Caveat:
Always start component names with a capital letter.
For example,  represents a DOM tag, but  represents a component and requires Welcome to be in scope.

Thanks @gibson I had the same issue


Feature Request (minor fix) : hide row filtered out by filter selection

Hi,
Can you change the default behavior or add an optional parameters that allow us to hide the rows or cols where there is no data after applying the filters.
Thanks.

That's already the default behaviour... can you give me an example where this doesn't happen?

Doing an extraction of my data to give you a sample, i found that my data contains nullable value in my measures, that's why i had some blank lines, my mistake.
Thank you for this amazing tool.
Appreciate !


Improvement Make sure instance when change params of StructInfo,Predicates and catch and record exception for every materialization context

Proposed changes

Make sure instance when change params of StructInfo,Predicates.
Catch and record exception for every materialization context, this make sure that if throw exception when one materialization context rewrite, it will not influence others.


Mail::SpamAssassin::PDF::Parser error

How to resolve the error
warn: plugin: eval failed: Can't locate object method "new" via package "Mail::SpamAssassin::PDF::Parser" (perhaps you forgot to load "Mail::SpamAssassin::PDF::Parser"?) at C:\Program Files\JAM Software\SpamAssassin for Windows\runtime\inc\lib/Mail/SpamAssassin/Plugin/PDFInfo2.pm line 326.

Make sure you are using PDFInfo2.pm from the /dist folder and not the one in /lib/Mail/SpamAssassin/Plugin as the former has everything in one file.
Also, I released a new version today that should improve performance.

getting error as below in SA log file, is it related? any assistance to solve it?
Sat Dec  9 00:05:58 2023 [-10692] warn: pdfinfo2: Error parsing pdf: Error getting object 24 0 R: Odd number of elements in hash assignment at C:\\Program Files\\JAM Software\\SpamAssassin for Windows\\runtime\\inc\\lib/Mail/SpamAssassin/Plugin/PDFInfo2.pm line 680.
Sat Dec  9 00:05:58 2023 [-10692] warn: pdfinfo2: Error parsing pdf: Error getting object 24 0 R: Odd number of elements in hash assignment at C:\\Program Files\\JAM Software\\SpamAssassin for Windows\\runtime\\inc\\lib/Mail/SpamAssassin/Plugin/PDFInfo2.pm line 680.

Sat Dec  9 00:06:55 2023 [-8584] warn: pdfinfo2: Error parsing pdf: unknown char ' at C:\\Program Files\\JAM Software\\SpamAssassin for Windows\\runtime\\inc\\lib/Mail/SpamAssassin/Plugin/PDFInfo2.pm line 729.
Sat Dec  9 00:06:55 2023 [-8584] warn: pdfinfo2: Error parsing pdf: unknown char ' at C:\\Program Files\\JAM Software\\SpamAssassin for Windows\\runtime\\inc\\lib/Mail/SpamAssassin/Plugin/PDFInfo2.pm line 729.

Sat Dec  9 00:07:04 2023 [-8584] warn: pdfinfo2: Error parsing pdf: Use of uninitialized value in string eq at C:\\Program Files\\JAM Software\\SpamAssassin for Windows\\runtime\\inc\\lib/Mail/SpamAssassin/Plugin/PDFInfo2.pm line 1964.

Sat Dec  9 04:28:00 2023 [-12668] warn: pdfinfo2: Error parsing pdf: Error getting object 6 0 R: Expected 'obj', got '%%' at offset 567 at C:\\Program Files\\JAM Software\\SpamAssassin for Windows\\runtime\\inc\\lib/Mail/SpamAssassin/Plugin/PDFInfo2.pm line 2132.
Sat Dec  9 04:28:00 2023 [-8060] warn: pdfinfo2: Error parsing pdf: Error getting object 6 0 R: Expected 'obj', got '%%' at offset 567 at C:\\Program Files\\JAM Software\\SpamAssassin for Windows\\runtime\\inc\\lib/Mail/SpamAssassin/Plugin/PDFInfo2.pm line 2132.

Sat Dec  9 04:28:09 2023 [-8060] warn: pdfinfo2: Error parsing pdf: Error getting object 6 0 R: Expected 'obj', got '%%' at offset 567 at C:\\Program Files\\JAM Software\\SpamAssassin for Windows\\runtime\\inc\\lib/Mail/SpamAssassin/Plugin/PDFInfo2.pm line 2132.

This bug and several others have been fixed in the latest release. I am actively working on this project so there might be a few more releases in the coming days/weeks.


Updated use of the word include

"include" is not a noun. Updated to refer to

include file
include files
include as a verb
include extensions

@MikeRayMSFT Mike -- I agree with your edit. We use a lot of shorthand internally that we shouldn't subject users to. Bill reviews PR's in the external guide. Bill, can you take a look? Thanks -- Monica

Thanks. I used extension because it's in the parent heading - https://github.com/MicrosoftDocs/Contribute/blob/6310e304536ba1ebbdf509c87da5324a63943dfe/Contribute/how-to-write-use-markdown.md#ops-custom-markdown-extensions
Having said that, I'm not 100% certain it's right. It actually looks like file could be used throughout.

Thanks for your patience @MikeRayMSFT
I'll :shipit: now.

Thanks @MikeRayMSFT for paying it forward. I expect cookies next time!


fix(bindCallback): add better type overloads

This is currently blocked, as it doesn't seem that TypeScript can really handle inferring types here like I hoped it could

Have you tried re-ordering the signatures so that those with the most parameters precede those with fewer parameters? The most specific signatures should come first.
I saw the issue you created and it looked to me like your approach would be fine.

Blocked by https://github.com/Microsoft/TypeScript/issues/22952

@benlesh I think you can disregard the amendment I made to the comment above. It most likely is only the ordering that's the problem.
I messed up my minimal repro and bound a generic function:
declare function func<T>(callback: (t: T) => void): void;
declare function bindCallback<T>(f: (callback: (t: T) => void) => void): T;
const result = bindCallback(func); // inferred as {}

I'm such a doofus. :grimacing:


FW auto takeoff and landing on runway

This should sum up the last TODO/issues that need to be taken care of before we merge runway takeoff and runway landing with terrain estimator.
There is a new branch with the state we flew today: https://github.com/PX4/Firmware/tree/runway_takeoff_before
All in all it worked really well!
TODOs:

[x] steer on the ground after landing, including using rudder from the flaring point (and use the navigator with a virtual waypoint ahead, like for takeoff and posctl)
[x] parameter for target landing airspeed (factor)
[x] do a proper groundspeed scaling for the wheel controller
[x] add flaps (could also be done later)
[x] rename AERTW mixer and update comments

Optional / second iteration

[ ] 2 step flaps (a: at second last waypoint, b: on slope)

Issues:

[x] after landing it throttles up again for a brief moment
[ ] the switch to mission has to be really fast for the takeoff to work, if assisted is triggered in between it doesn't work
[x] fix issues reported on old runway PR
[ ] in manual, flaps are set 50% when RC switches are not assigned
[x] starting point for navigation on takeoff with WP heading is wrong
[x] navigation with virtual heading results in a heading that points more north or south (same calculation as for posctl, open a separate issue)
[x] integrator for wheel controller is reset as well during takeoff, reset must be separated
[ ] after climbout, TECS pitches down first before it starts tracking altitude again
[x] terrain altitude valid flag was set to true although laser had no values anymore

Issues in existing code

[x] disabling navigation on landing happens too early and is triggered by WP distance instead of height (land_heading_hold_horizontal_distance)
[x] rudder has non-zero output in stabilized, not sure where this comes from yet
[x] some condition makes the plane fly over the landing slope but not descend
(this was caused by the terrain estimate being used although it was wrong. the range finder had a timeout and the valid flag was not set to false.)
[x] during a landing the fixed wing position controller always sticks to using the terrain estimate if enabled even if the estimate is not valid any more. This has to be rethought because if the estimate is just wrong then the landing won't be nice. Either we switch back to using the normal estimate based on gps and baro or we handle this as failure and do e.g a climbout.
See here https://github.com/PX4/Firmware/blob/master/src/modules/fw_pos_control_l1/fw_pos_control_l1_main.cpp#L966
@thomasgubler What do you think?

@tumbili please update if I forgot things

Log of one of the flights from today: http://logs.uaventure.com/view/fWC9YAEzQLX6z5Yqczwjjj

@AndreasAntener @SimonWilks I started fixing some issues, some comments on that:

disabling navigation on landing happens too early and is triggered by WP distance instead of height (land_heading_hold_horizontal_distance):

The plane will now only go into pure heading hold mode after we have started flaring. This will make sure that we are not pushed away from the runway by crosswinds.

during a landing the fixed wing position controller always sticks to using the terrain estimate if enabled even if the estimate is not valid any more

The position controller will now only use the terrain estimate if it's valid. During a landing it can switch between terrain estimation or normal ground estimation, depending on the validity of the terrain estimate. This is the best thing we can do at the moment. Given that the difference between terrain estimate and normal ground estimate based on altitude should be relatively small this shouldn't be a bit issue.

I need a log to find out what is happening with the rudder in stabilized mode, can you send me a link please?

@AndreasAntener @SimonWilks Could you give me some more information on this issue:
the switch to mission has to be really fast for the takeoff to work, if assisted is triggered in between it doesn't work
What exactly happens? If you have a log then that would be even better :-)

You can get the log file here: http://logs.uaventure.com/view/eb266UWc3mWxAaQNbzPchX
Can you send a message back to the ground station if the terrain estimate is no longer valid? It would be good to at least get an audio warning. Alternatively (or additionally) a buzzer error tone could be useful. Basically we want to make the operator aware that something has gone at least partially wrong.

@SimonWilks @AndreasAntener Think I found the bug which lead to rudder output in stabilized.
This one was important! If you guys can manage to do a bench test, that would be great!

@tumbili Cool! I can do a bench test.

Not yet, once sec.

Ok, good to go.

@tumbili here's a log where we have one or two occasions where the main mode switches to ALTCTL before MISSION.
The effect was that it didn't run the takeoff code then, but just started to throttle up.

during a landing the fixed wing position controller always sticks to using the terrain estimate if enabled even if the estimate is not valid any more. This has to be rethought because if the estimate is just wrong then the landing won't be nice. Either we switch back to using the normal estimate based on gps and baro or we handle this as failure and do e.g a climbout. See here https://github.com/PX4/Firmware/blob/master/src/modules/fw_pos_control_l1/fw_pos_control_l1_main.cpp#L966 @thomasgubler What do you think?

I see that https @tumbili addressed this here http://github.com/PX4/Firmware/commit/547ef70efe364c3eed5f39c5167bb910b3b27d26
The reason for the old implementation was that the old landing estimator would sometimes go invalid again for a short time after becoming valid (in the beginning of the landing phase, depending on the terrain). The estimate never became invalid afterwards for the typical use case. (Of course it's possible, but the whole code here is lacking failure handling anyway). We forced it to stick with the estimate to avoid large jumps in the altitude error.
I guess the safest and most natural thing to do would be a go-around if the terrain estimate becomes invalid. This of course leads to further questions such as: what do you do when the landing fails for n times? Should we force/advise the operator to land it manually? Should we fall back to waypoint altitude landing then? Should this code partly be moved to the navigator and commander (sensor failure handling)? etc.
Another idea would be to let the terrain estimate drift smoothly to the landing waypoint altitude if there are no more valid laser ranger finder inputs by e.g. using the landing waypoint altitude as measurement input with a large variance.

@tumbili As long as we don't have the failsafe option I guess switching to the GPOS alt "smoothly" would be a good option? With this I think we can go ahead then and implement failsafe in a next iteration.
On the failsafe: We discussed a few options, one is:

notify user
if alt < climbout height, climb out (keep the heading during climbout)
fly back to previous waypoint

But this would need to be very flexible/configurable. There is no guarantee that a climbout or a turn to go around is even possible.

@tumbili here's a log where we have one or two occasions where the main mode switches to ALTCTL before MISSION. http://logs.uaventure.com/view/jfXbitNoZxe5rCi89Kbyi6
The effect was that it didn't run the takeoff code then, but just started to throttle up.

@tumbili I tried reproducing this in HIL just now, but it doesn't seem to be an issue anymore. Might need to re-check that on the actual setup.

@tumbili Can we merge / close?

Done! Thanks everybody!


(🐞) stream_output: correctly handle virtual terminal ANSI support

Credit to @TBBle for this fix in #104

resolves #104
resolves https://github.com/python-poetry/poetry/issues/1972
resolves https://github.com/python-poetry/poetry/issues/3354

Poetry output before and after this change:

Could a contributing guide be added to this project? I had no idea where to make a news fragment (or how, I just guessed)

Could a contributing guide be added to this project? I had no idea where to make a news fragment (or how, I just guessed)

Sorry, it's still a work in progress, people rarely contribute to this project. I will make the change.
I have dropped the reference to clikit since cleo is no longer entangled with it.
Do you know if we could add any kind of test to check for this (I don't use Windows, so I don't know how Windows coloring works)? I don't feel comfortable with untested code.

I suspect a test for this is going to have to repeat the function's implementation, as the logic for the expected outcome would depend on the same kernel32.GetConsoleMode check for ENABLE_VIRTUAL_TERMINAL_PROCESSING that is used in the code:

ENABLE_VIRTUAL_TERMINAL_PROCESSING set? _has_color_support should return True and ENABLE_VIRTUAL_TERMINAL_PROCESSING remains set.
ENABLE_VIRTUAL_TERMINAL_PROCESSING not set? _has_color_support should either return False and ENABLE_VIRTUAL_TERMINAL_PROCESSING remains not set, or returns True and ENABLE_VIRTUAL_TERMINAL_PROCESSING is now set.

Which is literally what the changed code-block is doing. And depending on how CI is run, _has_color_support may never even reach that code, if one of the early-out checks happens instead; ConEmu has some different behaviour when ENABLE_VIRTUAL_TERMINAL_PROCESSING is set, so you'd probably end up having to carve out the env-check _has_color_support uses for ConEmuANSI to ensure you expect True and don't care about ENABLE_VIRTUAL_TERMINAL_PROCESSING's state.
A manual test could be written to recognise misdetection, but I'm not sure how valuable that is. In the case _has_color_support returns True, then the user can verify colours work and no unhandled escapes (False positive), and if _has_color_support returns False, then the user could verify coloured output shows up as unhandled escapes (False negative). You can do all that with just poetry --version and ANSICON=true poetry --version anyway.
Poking around for other ideas, I found a Go library which also enables ENABLE_VIRTUAL_TERMINAL_PROCESSING, but its test suite mocks-out the code that calls the relevant function.
I also note that that Go library uses the same logic we're changing to here, i.e. if ENABLE_VIRTUAL_TERMINAL_PROCESSING is already set, returns True, not False, and returns False if SetConsoleMode fails.

@KotlinIsland I took the liberty of changing the CHANGELOG.md entry into a news fragment. Please check if it's fine with you, if so, it LGTM and I will merge it.

@Secrus Looks PFGL! merge ASAP


[Java Sample Issue]

Library name and version
azure-storage-file-share 12.8.2
Sample Issue Type

[ ] Sample not working
[X] Sample missing
[ ] Do not understand sample

Issue details
No example code
Expected behavior
No response
Actual behavior
No response
Reproduction Steps
No response
Environment
Java version

@TanTheMan2099
azure-storage-file-share is actually a data-plane SDK. For them, they've got higher quaulity handwritten examples. Please check
https://learn.microsoft.com/en-us/samples/azure/azure-sdk-for-java/storage-file-share-samples/


Fix inconsistent behavior of scalar Jacobi between reference and the others

We have the workaround for zero diagonal value in scalar Jacobi, but reference uses 1 but the others uses zero.
I currently make it be 1.
Note. it is not the proper inverse Jacobi matrix.
first commit adds the test and the second one fixes the issue.

@yhmtsai the second commit seems to be missing

@upsj Yes and sorry. I would like to wait for that some jobs of the first commit fail first


CCUS for waste incineration should be added to the hourly electricity production

CCUS for waste incineration is missing from the hourly electricity production chart. This means that if a waste incinerator is added to the model on beta and CCUS is added to it, the electricity production will show gaps:

The plant should therefore be added to the chart. Additionally, because the plant was already missing from two other charts (#3823 and #3817) it would be good to scan whether the plant still needs to be added to other charts.
@MartLubben or @lottevanvlimmeren do you have time to pick this up?

Solved with: https://github.com/quintel/etmodel/pull/3825#event-5260067060


R3.5

Checklist

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

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

Using toolchain directly in this manner is deprecated.  Consider using the compilers outlined here.


Issue 270 ocn clim

based on top of: https://github.com/PCMDI/pcmdi_metrics/pull/295
@gleckler1 @durack1 all ocean calculations were wrong
please review and merge #295 first

@doutriaux1 I'm reluctant to merge until the travis builds are passing fine.. Do you know what is going on here?

@durack1 you shouldn't merge until #295 has been merged in anyway.

@doutriaux1 no problem - will wait for your update.. @gleckler1 is actively testing stuff now, so it might even be up to him to check your changes and merge..


How to use TimeDistributedMerge using TimeDistributed wrapper ?

I am using TimeDistributedMerge to merge outputs from lstm over time by returning sequences, since TimeDistributedMerge is deprecated, so I changed my implementation to use timedistributed wrapper then it gives error.
File "/Library/Python/2.7/site-packages/keras/engine/topology.py", line 148, in create_node
output_tensors = to_list(outbound_layer.call(input_tensors[0], mask=input_masks[0]))
File "/Library/Python/2.7/site-packages/keras/layers/wrappers.py", line 131, in call
y = self.layer.call(X)  # (nb_samples * timesteps, ...)
File "/Library/Python/2.7/site-packages/keras/engine/topology.py", line 1189, in call
'(at least 2). Got: ' + str(inputs))
Exception: Merge must be called on a list of tensors (at least 2). Got: Reshape{2}.0
My code
model = Sequential()
model.add(Embedding(max_features, 128, input_length=chunk_size, dropout=0.5))
model.add(LSTM(128, dropout_W=0.5, dropout_U=0.1,return_sequences=True))
model.add(TimeDistributed(Merge(layers=None,mode='ave')))
model.add(Dense(num_classes))
model.add(Activation("softmax"))
@fchollet can you help me out with this by giving an example of how to use timedistributed wrapper for lstm return sequences

you can use:

model.add(TimeDistributed(Dense(output_dim= , activation= ))))

to pass your LSTM layer output to time distributed layer

Duplicate. Please search: https://github.com/fchollet/keras/issues/2271

write a lambda layer by yourself
for e.g.
def td_sum(x):
    return K.sum(x,axis=1)


The performance of the retinanet

@yhenon-nextdroid  @yhenon @xu1718191411 @mimoralea @rvandeghen
Thanks to your great works! But i got some training issues in this repo.  The original retinanet using SGD and finetune 12epochs on the ImageNet pretrained Resnet. I change the training settings follow the paper, after solving some small convergence problems, my recurring performance is much lower than the paper (ap30.5% vs 34.3% in 600 px). For this I checked all the relevant details in the code, but did not find any problems, do you know how to solve this problem？Looking forward to your reply.

I don't really have time to work on this project, but I believe the gap in performance is due to the limited data augmentation in this implementation (only flipping). It is currently lacking:

any kind if size/scale augmentation
any kind of color/brightness augmentation
There could also be more advanced augmentation schemes applied. I'd love to see a PR on this, but I can't make time for it right now.


Can you resize and fill the page instead of fitting the image?

Right now when I resize a document that has some full bleed pages, I get white bars on the left and right side. Is there any way to have it fill the page and just cut off the top and bottom of the page when resizing?

Maybe answering my own question here, but it looks like a resize followed by a scale should do it. Just playing with the scale factor now.

Resizing preserves the current positioning and proportional size of the content. So, if you had 10% bleed for example, you would continue to have 10% bleed (which would be bigger in size if you increased the paper size). Resize actually uses fit-to-page with the contents.
Scaling would increase the contents while preserving the paper size.
You can also reposition the contents with other parameters, as described in the help message.
There are many ways to do it. Few possibilities are:
 --hor-align, --horizontal-alignment <left|center|right>
             Where to translate the scaled page
             Default: center
             Options: left, right, center
 --vert-align, --vertical-alignment <top|center|bottom>
             Where to translate the scaled page
             Default: center
             Options: top, bottom, center
 --xoffset, --xtrans-offset <FloatNumber>
             Add/Subtract from the X translation (move left-right)
             Default: 0.0 (zero)
             Options: Positive or negative floating point number
 --yoffset, --ytrans-offset <FloatNumber>
             Add/Subtract from the Y translation (move top-bottom)
             Default: 0.0 (zero)
             Options: Positive or negative floating point number

Not sure how you did it, but you can do everything in a single call (resize + scale).
Cheers!
Gus

I just ended up combining -s 1.01 -r letter and that did exactly what I wanted.

Some PDFs also have a Cropbox that is not the same as the MediaBox, which can cause some problems.
You can tune those with
 -c, --cropbox <paper>
             Resets Cropboxes on all pages to a specific paper size
             Only applies to resize mode
             <paper> can be: full | fullsize - Uses the same size as the main paper/mediabox
                             custom          - Define a custom cropbox size in inches, mm or points
                             std paper name  - Uses a paper size name (eg. a4, letter, etc)


Support hp overrides

It would be cool if hp*-prefixed query params or payload props could be used to override envelope fields.

NOTE: this should be something-something buz instead of hp


fix: request.pipeline edgecases

The optimizated verison of request.pipeline had some hard
to determine edge cases. Reverting back to non-optimized
version until a better solution can be implemented.
Fixes: https://github.com/mcollina/undici/issues/206

Will follow up at some point with a version where the Duplex writes directly to the socket.

Fixed through https://github.com/mcollina/undici/commit/c553ba19c71bb4d00e0699f43c8bdd8c91d96d42 instead.


Footprints error

When a default search is performed (predicate=intersects) with no area specified, main now raises the following server-side error:
AssertionError: Cannot both declare the field  'footprint' and include it in the SpatialEntryFootprintSerializer 'exclude' option.  Remove the field or, if inherited from a parent  serializer, disable with `footprint = None`

This should have been fixed

My mistake, I simply needed to pull the backend! I keep forgetting that the progress on these repos is mutally exclusive


Use dask dataframe shuffle for hash repartition instead of repartition

As noted in https://github.com/rapidsai/cudf/pull/6442, cuDF will eventually remove the ddf.repartition API as it is now supersed by the shuffle API in mainline dask.dataframe. We should proactively update the usage of repartition to shuffle.

[ ] Queries:
[ ] Q02
[ ] Q03
[ ] Q04
[ ] Q08
[ ] Q20
[ ] Q25
[ ] Q29
[ ] Q30
[ ] Hash merge utility


Scale Node Pool Up or Down for RKE2 provisioned clusters is not working for long cluster/node pool names

Setup

Rancher version: v2.6-head
Browser type & version: All

Describe the bug
See the backend issue description for a full breakdown of the problem: https://github.com/rancher/rancher/issues/35452#issue-1050296190
To Reproduce
Create an RKE2/K3S cluster with a very long name (as described above). After the cluster is active, try to scale one of the machine pools.
Result
Nothing happens.
Expected Result
The machine pools should be scaled.
Screenshots

Additional context
Kubernetes has a strict length maximum for names. Therefore, we have to do what we are doing (truncating the name and adding 5 random characters at the end).
Instead of looking at just the name of the MachineDeployment and matching it to the machinePool, the UI will have to do the following:

The MachineDeployment will have an infrastructureRef that points to a MachineTemplate
That MachineTemplate will be cloned from a Config (*)
The Config will be referenced by a machineConfigRef from the cluster object's spec.rkeConfig.machinePools

So the identification of MachineDeployment to machinePool will be more complicated, but I don't really see a way around that at this point.
(*) This is currently in review in the backend.
Backend Issue: https://github.com/rancher/rancher/issues/35452
Backend PR: https://github.com/rancher/rancher/pull/36269

The backend change for this has been merged.

Test Environment:
Rancher version: a64d237
Rancher cluster type: HA
Docker version: 20.10
Downstream cluster type: RKE2 do, aws, linode, azure clusters

Testing:

Create a RKE2 node driver cluster with a long cluster/pool name
Wait for the cluster to provision
Navigate to node pools (Cluster Management > Click on the cluster)
Use "+" to scale up or "-" to scale down a pool

Issue: only AWS cluster's node pools scaling up/down worked as expected
While for other node pools I tried (azure, do, linode) "+" and "-" buttons didn't work with logging a console error
TypeError: Cannot read properties of undefined (reading 'metadata')
    at t.value (cluster.x-k8s.io.machinedeployment.js:84:45)
    at click (provisioning.cattle.io.cluster.vue?161d:5:1419)
    at Qt (vue.runtime.esm.js:1854:26)
    at HTMLButtonElement.n (vue.runtime.esm.js:2179:14)
    at HTMLButtonElement.c._wrapper (vue.runtime.esm.js:6917:25)

Back end does return all annotations as expected for all clusters including rke.cattle.io/cloned-from-name

Weird, this worked for me with DO when the PR was reviewed. It looks like it's an issue with a missing template... which i suggested couldn't ever be the case

2.6-head 8c785a1
I'm not able to scale down/ scale up node pools either on Amazon ec2 node driver rke2 cluster. I see the same console error as Sergei mentioned.
Note scale down/up works if drain on delete option is selected while creating the clusters for the node pools.

Reproduction Setup

Rancher version: 2.6.3
Browser: Chrome Version 99.0.4844.74

Reproduction Steps

Create a RKE2 node driver cluster with a long cluster/pool name
Wait for the cluster to provision
Navigate to node pools (Cluster Management > Click on the cluster)
Use "+" to scale up or "-" to scale down a pool

Result
We see console type errors: t.value cluster.x-k8s.io.machinedeployment
We check the issue within the rancher api resources and find machinepools.machineConfigRef.name doesn't have the appropriately truncated name.
Validation Setup

rancher version: v2.6.4-rc9
Browser:Chrome Version 99.0.4844.74

Validation Steps

Create a RKE2 node driver cluster with a long cluster/pool name
Wait for the cluster to provision
Navigate to node pools (Cluster Management > Click on the cluster)
Use "+" to scale up or "-" to scale down a pool

Result

When we scale down or up the pool we don't see any console errors
When we check the dev tools we can see the appropriately named machineConfigRef (Screenshot for reference)

There are no networks errors within the devtools


[stable/rabbitmq] using load-definition in extraConfiguration

Describe the bug
To configure TTL and Dead Letter Exchange via Helm chart I added the following secret with load-definitions. The way I did that was the result of researching for the usage of a configuration with Helm.
Before I used the load-definition everything worked fine and the container ran successfully. When using load-defintions from a new secret and referencing it in the values-dev.yml the credentials are not accepted anymore.
Version of Helm and Kubernetes:
Helm v2.13.1
Kubernetes: 1.12.9-gke.15
Which chart:
name: company-components-rabbitmq
version: 0.1.0
home: https://bitbucket.org/company/configuration-google/src/master/
description: Basic components
keywords:
  - docker
sources:
  - https://bitbucket.org/company/configuration-google/src/master/
dependencies:
  - name: rabbitmq
    version: 5.5.0
    repository: "@stable"

What happened:
When using helm like this:
helm upgrade --install --namespace=dev company-components-rabbitmq-test -f ./helm-charts/components/rabbitmq/values-dev.yaml ./helm-charts/components/rabbitmq

The StateFul Set of RabbitMQ is being started. The Pod yields the first error that something went wrong. When looking at the Container Logs I read the following:
2019-09-09 12:00:58.546 [warning] <0.573.0> HTTP access denied: user 'test' - invalid credentials

This is the Secret.yml:
apiVersion: v1
kind: Secret
metadata:
    name: load-definition
type: Opaque
stringData:
    load_definition.json: |-
        {
          "vhosts": [
            { "name" : "/" }
          ],
          "policies": [
            {
                "vhost":"/",
                "name":"DLX",
                "pattern":".*",
                "apply-to":"queues",
                "definition":{"dead-letter-exchange":"dead_letter"},
                "priority":0
            }
          ]
        }

And there is the values-dev.yml:
rabbitmq:
  persistence:
    enabled: false
    #existingClaim: rabbitmq-volume-claim #commented because throws errors
  rabbitmq:
    username: test
    password: test123
    loadDefinition:
      enabled: true
      secretName: load-definition
    extraConfiguration:
      management.load_definitions = /app/load_definition.json
  nodeSelector:
    type: backend

The Credentials should be fine.
They are defined in a ConfigMap:
  RABBIT_MQ_USER: test
  RABBIT_MQ_PASSWORD: test123

The ConfigMap and the Secrets seem to be released successfully:
RESOURCES:
==> v1/ConfigMap
NAME                                  DATA  AGE
company-components-rabbitmq-test-config  2     2d22h
==> v1/Secret
NAME                           TYPE    DATA  AGE
load-definition                Opaque  1     2d20h
company-components-rabbitmq-test  Opaque  2     2d22h

Double Checking the ConfigMap shows me that username and password are as expected.
When checking the enviroment variables of the container however I see this:
Liveness probe:
exec
sh -c rabbitmq-api-check "http://test:$RABBITMQ_PASSWORD@<IP_ADDRESS>:23134/api/healthchecks/node" '{"status":"ok"}'

What you expected to happen:
I expect the container to run and have successfull liveness probing as before where I did not defined load-definitions
How to reproduce it (as minimally and precisely as possible):
Try to use my configurations mentioned here.

this worked:
load_definition.json: |-
        {
          "users": [
            {
                "name" : "{{ .Values.rabbitmq.rabbitmq.username }}",
                "password" : "{{ .Values.rabbitmq.rabbitmq.password }}",
                "tags" : "administrator"

            }
          ],
          "vhosts": [
            { "name" : "/" }
          ],
          "policies": [
            {
                "vhost":"/",
                "name":"TTL",
                "pattern":".*",
                "apply-to":"queues",
                "definition":{"message-ttl": 43200000 },
                "priority":0
            },
            {
                "vhost":"/",
                "name":"DLX",
                "pattern":".*",
                "apply-to":"queues",
                "definition":{"dead-letter-exchange":"dead_letter"},
                "priority":0
            }
          ]
        }

I'm glad you were able to solve your issue, @xetra11. Let us know if you find any other issue in the future.
Regards,
Alejandro

@alemorcuq
Yeah to be honest it is hard to find the above configuration described anywhere and there know how the key/value pairs have to be defined. One could try to figure out by looking at the other configuration formats but for me as a beginner that did not worked out.
It has to be more clear that the above configuration can be extracted from the Manager UI. I found that by accident in a blog post.


Allow filters on arbitrary field names

The JSONAPI specification does not define how filters work, so Spine should not force filters to correspond to defined fields.
This PR removes this limitation.

Good thinking. Thanks!


Nonce seed

While using Math.floor( Math.random() * 1000 ) to calculate the seed for the next nonce i recognized a problem:
Math.floor( Math.random() * 1000 )
282
Math.floor( Math.random() * 1000 )
979
Math.floor( Math.random() * 1000 )
396
Math.floor( Math.random() * 1000 )
396
In fact its possible that the seed function returns the same value as before so the nonce calculation would result in the same string as before. The WsseProvider would throw new NonceExpiredException('Previously used nonce detected') and the WsseListener would catch this Exception and return a plain message to the client. This could also result in client JSON errors while it is expecting JSON data.
I would suggest to calculate the nonce string this way:
    tokenHandler.randomString = function(length) {
        var text = "";
        var possible = "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789";
        for(var i = 0; i < length; i++) {
            text += possible.charAt(Math.floor(Math.random() * possible.length));
        }
        return text;
    }

var nonce = tokenHandler.randomString(30);
var created = formatDate(new Date());
var hash = CryptoJS.SHA1(nonce + created + secret);
var digest = hash.toString(CryptoJS.enc.Base64);
var b64nonce = Base64.encode(nonce);
return 'UsernameToken Username="' + username + '", PasswordDigest="' + digest + '", Nonce="' + b64nonce + '", Created="' + created + '"';
Of course there are many ways to calculate, so this is only one suggestion provided by:
https://blog.nraboy.com/2015/03/create-a-random-nonce-string-using-javascript/
Thanks for the great work. Looking forward to see some solution for handling "session timeout" after idling some time to tell the client that the cookie data will be purged and the user has to login again.

This is a better way to generate the nonce, thanks for this function, very usefull :+1:

Hi,
Actually you're totally right, there is a collision risk while generating nonce using random + md5.
Actually to be sure to have a more random nonce generator, it is possible to use random.org API service.
But we have to remember that nonce has a lifetime of 300 seconds so this risk is limited.
Thanks to notice that, I'll correct that nonce generation when I get a moment, you can also make a pull request if you want :)
See you.

Corrected by d26b461


small error in DynamicAttentionWrapper

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):

Not relevant

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):

Not relevant

TensorFlow installed from (source or binary):

Not relevant

TensorFlow version (use command below):

1.1

Bazel version (if compiling from source):

Not relevant

CUDA/cuDNN version:

Not relevant

GPU model and memory:

Not relevant

Exact command to reproduce:

Not relevant
Describe the problem
line 465 in tensorflow/tensorflow/contrib/seq2seq/python/ops/dynamic_attention_wrapper.py says
'''
if not callable(cell_input_fn):.
'''
I think it should say
'''
if not callable(probability_fn):
'''
Source code / logs
None

The attention wrapper has been rewritten in master branch, there is no dynamic_attention_wrapper.py any more.
Anyway, I think this typo was fixed in commit https://github.com/tensorflow/tensorflow/commit/0557e8f90c1a2f027f4561c70558c6c836138058. You can update your TensorFlow and check it.

@vrenkens, thanks for submitting this, but it looks like it is already fixed. Closing for now. Let us know if upgrading doesn't resolve your issues.


Attributes for thermostat write must be implemented for chip tool darwin

chip-tool has some thermostat read attributes which are missing from chip-tool-darwin
Attaching the screen shot;

Fixed in #18276


Bump up Cephadm Ansible collection

I've proposed bumping to 1.18.0 in https://github.com/stackhpc/stackhpc-kayobe-config/pull/1219 (draft), and added a reno.

This is good to close, now https://github.com/stackhpc/stackhpc-kayobe-config/pull/1219 is merged?


Generic DynamicCollection

Hey @cberner 👋 ,
Opening an issue to clarify a TODO regarding generic on DynamicCollection:
https://github.com/cberner/redb/blob/35cbafe6c5051dfbca087291631b1158096f7eb3/src/multimap_table.rs#L248-L249
Is it still relevant? Is the task simply to move V: RedbKey generic from function to struct level?

Ya, the TODO means that V should be removed from iter() and iter_free_on_drop() and moved to the struct

Do you mind if I take it? Wanna start exploring with the codebase

Go for it!
Sent from my phone
On Sat, Jul 1, 2023, 7:23 AM Roman Krasiuk @.***> wrote:

Do you mind if I take it? Wanna start exploring with the codebase
—
Reply to this email directly, view it on GitHub
https://github.com/cberner/redb/issues/632#issuecomment-1615939208, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGNXQD3CCADZBP73TCUBGDXOAXGLANCNFSM6AAAAAAZ2ZQKGY
.
You are receiving this because you were mentioned.Message ID:
@.***>


vue-tsc --noEmit show error when using Svg as component

Vue Language Features (Volar) version v0.27.27
TypeScript Vue Plugin (Volar) version v0.27.27
I am using https://github.com/jpkleemans/vite-svg-loader  to load svg file as component
 import ArrowLeftIcon from '@/assets/arrow-left-icon.svg?component'
usage in template
<div class="app-action-link" @click="goBack()">
      <ArrowLeftIcon class="h-4 w-4 inline-block" /> back
    </div>

vue-tsc show error in <ArrowLeftIcon
JSX element type '__VLS_9' does not have any construct or call signatures.ts(2604)
(property) ArrowLeftIcon: Component<any, any, any, ComputedOptions, MethodOptions>

my tsconfig
{
  "compilerOptions": {
    "target": "esnext",
    "useDefineForClassFields": true,
    "module": "esnext",
    "moduleResolution": "node",
    "strict": true,
    "jsx": "preserve",
    "sourceMap": true,
    "resolveJsonModule": true,
    "esModuleInterop": true,
    "lib": ["esnext", "dom"],
    "strictNullChecks": false,
    "noImplicitAny": false,
    "allowSyntheticDefaultImports": true,
    "skipLibCheck": true,
    "experimentalDecorators": true,
    "importHelpers": true,
    "baseUrl": ".",
    "paths": {
      "@/*": ["./src/*"]
    }
  },
  "include": ["src/**/*.ts", "src/**/*.d.ts", "src/**/*.tsx", "src/**/*.vue"]
}

Create components.d.ts file (https://github.com/johnsoncodehk/volar#using) in src folder.
In my case it is autogenerated by unplugin-vue-components in root folder, including it in tsconfig.json worked for me.
here is my tsconfig
{
  "compilerOptions": {
    "baseUrl": ".",
    "target": "esnext",
    "useDefineForClassFields": true,
    "module": "esnext",
    "moduleResolution": "node",
    "strict": true,
    "jsx": "preserve",
    "sourceMap": true,
    "resolveJsonModule": true,
    "esModuleInterop": true,
    "lib": ["esnext", "dom"],
    "paths": {
      "~/*": ["src/*"]
    }
  },
  "include": ["src/**/*.ts", "src/**/*.d.ts", "src/**/*.tsx", "src/**/*.vue", "components.d.ts"]
}

@GMKR thank you, I follow your suggestion and it works now

I've tried and it is not working for me.
Reference to the other issue in Volar here also with the version 0.27.27
https://github.com/johnsoncodehk/volar/issues/547

Using DefineComponent instead of Component with declare module '*.svg?component' worked for me.

@johnsoncodehk  This is still not working with version 0.27.28
@sapphi-red  can you tell in more detail? in what find you make changes?

Instead of adding /// <reference types="vite-svg-loader" /> to src/vite-env.d.ts, I added
declare module '*.svg?component' {
  import { DefineComponent } from 'vue'
  const src: DefineComponent
  export default src
}

to it.

@sapphi-red thank you, it works like a charm!


[aws/kops-aws-platform] chart-repo.tf does not consider if cluster_name is not default

chart-repo.tf sets cluster_name    = "${var.region}.${var.zone_name}" however when deploying kops module there is the ability to set cluster_name_prefix which overrides the default region name.
Other modules in the root-module set cluster_name the same way.  Does it make sense to move the cluster_name_prefix logic to aws/kops-aws-platform or use some other ENV?

This is now out of date with the new reference architecture #286