Solve #78 - Add bots to process digital ocean billing checker

Closes #78
Description
On this PR three new bots were added to implement the DigitalOcean billing alerts. This are:

FetchBillingFromDigitalOcean
FormatDoBillAlert
NotifyDoBillAlertEmail

Example:
connection = {
    host: "localhost",
    port: 5432,
    dbname: "bas",
    user: "postgres",
    password: "postgres"
  }

  options = {
    process_options: {
      secret: "digital_ocean_secret_key"
    },
    write_options: {
      connection:,
      db_table: "do_billing",
      tag: "FetchBillingFromDigitalOcean"
    }
  }

  bot = Bot::FetchBillingFromDigitalOcean.new(options)
  bot.execute

  # FORMAT MESSAGE

  options = {
    read_options: {
      connection:,
      db_table: "do_billing",
      tag: "FetchBillingFromDigitalOcean"
    },
    process_options: {
      threshold: 7
    },
    write_options: {
      connection:,
      db_table: "do_billing",
      tag: "FormatDoBillAlert"
    }
  }

  bot = Bot::FormatDoBillAlert.new(options)
  bot.execute

  # SEND EMAIL
  refresh_token = "gmail_account_refresh_token"
  client_id = "gmail_account_client_id"
  client_secret = "gmail_account_secret"

  options = {
    read_options: {
      connection:,
      db_table: "do_billing",
      tag: "FormatDoBillAlert",
      avoid_process: true
    },
    process_options: {
      refresh_token:,
      client_id:,
      client_secret:,
      user_email<EMAIL_ADDRESS>      recipient_email: ["recipient1@mailco", "recipient2@mailco"]
    },
    write_options: {
      connection:,
      db_table: "do_billing",
      tag: "NotifyDoBillAlertEmail"
    }
  }

  bot = Bot::NotifyDoBillAlertEmail.new(options)
  bot.execute

  # SEND DISCORD
  options = {
    read_options: {
      connection:,
      db_table: "do_billing",
      tag: "FormatDoBillAlert"
    },
    process_options: {
      name: "bot_name",
      webhook: "discord webhook"
    },
    write_options: {
      connection:,
      db_table: "do_billing",
      tag: "NotifyDiscord"
    }
  }

  bot = Bot::NotifyDiscord.new(options)
  bot.execute

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

255 of 273 (93.41%)  changed or added relevant lines in 8 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.6%) to 98.974%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/bas/utils/google/send_email.rb
14
32
43.75%

Totals

Change from base Build<PHONE_NUMBER>:
-0.6%

Covered Lines:
2604

Relevant Lines:
2631

💛  - Coveralls


Add shouldCompileJS workaround

Fixes #77
This project uses semver, please check the scope of this pr:

[ ] #none# - documentation fixes and/or test additions
[x] #patch# - backwards-compatible bug fix
[ ] #minor# - adding functionality in a backwards-compatible manner
[ ] #major# - incompatible API change

CHANGELOG

Added _shouldCompileJS() to fix import error on Ember 2.12.

No longer needed as of ember-cli 2.12.1: https://github.com/ember-cli/ember-cli/pull/6884


add onFailure handling to provided listeners

ApplyTransformListener accepts onBatchFailure listeners.  DeleteListener, ExportListener, ExportToWriterListener, and UrisToWriterListener all lack an option to register a failure listener.  This is needed because errors thrown by onUrisReady listeners no longer trigger onQueryFailure listeners for handling.  So, to fit with the usage recommendation:
queryBatcher.onUrisReady(new DeleteListener())

it's a problem that any error in the call to delete the batch would only be logged and could not be handled without something complex like:
DeleteListener deleteListener = new DeleteListener();
queryBatcher.onUrisReady(batch -> {
  try {
    deleteListener.procesBatch(batch);
  } catch (Throwable t) {
    ... code to handle an error ...
  }
);

Instead I'm thinking we'd like (like ApplyTransformListener):
queryBatcher.onUrisReady(new DeleteListener()
  .onBatchFailure((batch, t) ->... code to handle an error ...))

@georgeajit you can look at my checkin for this to see how I caused each listener to fail.  One failure scenario that I didn't know how to simulate is DeleteListener.  Any ideas?  It's a bulk delete call, and that method doesn't throw any error if a uri is missing or invalid.  It would throw an error if the connection info was invalid, but I'm thinking DataMovementManager.readForestConfig() would fail first, not this...

nevermind, I figured out a way to simulate a failure in DeleteListener.  take a look at my last commit.  So now you have my unit tests to refer to in creating functional tests


hang after 1st training battle

Demo https://jslegend.itch.io/p5-pokemon-prototype hangs after  winning the first training battle (against Venusaur) :
score never stops changing at full speed, and keyboard is as dead
no way to go on or restart
on firefox 121.0
lots of warnings but no error message

It's normal that the game just stops after you have either won or lost against the Venusaur. I didn't code the rest haha.
Now what do you mean by the score never stops changing at full speed?

It flickers as if forever changing at lightning speed

Ok this is very strange. Did it only happen once or are you able to reproduce it?

Every time. Same on chrome too.
But maybe it's not the score : it looks dull for a score and it's toggled on/off at each press of SHIFT key

Oh what you referred to as the score is actually the debug mode. What you see is the number of FPS.


Request for supplementary materials

Supplementary materials will be provided in cvf..

Thanks @wangzhuo2019 . Here is the direct link for it: https://openaccess.thecvf.com/content/CVPR2022/supplemental/Wang_Domain_Generalization_via_CVPR_2022_supplemental.pdf

We found some discrepancies in the network architecture i.e. architecture in the paper and the code are different at some places. Which one is the correct one?


GitHub Actions

I created a simple workflow that should greet a person on their first PR/issue, but it isn't working as well as I would have hoped... It would be a fairly simple fix, provided that you're familiar with GitHub Actions
It's my first try at this, I'd really appreciate the help!

This has been resolved, but enhancements are welcome


Optional Auth

Is your feature request related to a problem? Please describe.
Can we have optional JWT?

So we can have single API that returns personalized widgets (with JWT), or default widgets (without JWT).
So we can add in user metadata to response if there's JWT.

Describe the solution you'd like
// .api file
@server(
  jwt: OptionalAuth // I don't know what's the appropriate clause/syntax here
)

rest.WithJwt("secret", rest.WithJwtOptional(true))

Include an optional flag in API file and an additional option rest.WithJwtOptional(true) like above, so it doesn't throw 401 if JWT is not passed.

Describe alternatives you've considered
func (m *OptionalAuthMiddleware) Handle(next http.HandlerFunc) http.HandlerFunc {
	authHandler := handler.Authorize(m.secret)(next)

	return func(w http.ResponseWriter, r *http.Request) {
		if token := r.Header.Get("Authorization"); token == "" {
			next(w, r)
			return
		}
		authHandler.ServeHTTP(w, r)
	}
}

I'm using custom middleware above
Additional context
I'm curious to know what is the correct/idiomatic way to achieve optional auth. If there is none, I believe exposing an optional flag will provide convenience for above use case.
Happy New Year!

Is your feature request related to a problem? Please describe. Can we have optional JWT?

So we can have single API that returns personalized widgets (with JWT), or default widgets (without JWT).
So we can add in user metadata to response if there's JWT.

Describe the solution you'd like
// .api file
@server(
  jwt: OptionalAuth // I don't know what's the appropriate clause/syntax here
)

rest.WithJwt("secret", rest.WithJwtOptional(true))

Include an optional flag in API file and an additional option rest.WithJwtOptional(true) like above, so it doesn't throw 401 if JWT is not passed.

Describe alternatives you've considered
func (m *OptionalAuthMiddleware) Handle(next http.HandlerFunc) http.HandlerFunc {
	authHandler := handler.Authorize(m.secret)(next)

	return func(w http.ResponseWriter, r *http.Request) {
		if token := r.Header.Get("Authorization"); token == "" {
			next(w, r)
			return
		}
		authHandler.ServeHTTP(w, r)
	}
}

I'm using custom middleware above
Additional context I'm curious to know what is the correct/idiomatic way to achieve optional auth. If there is none, I believe exposing an optional flag will provide convenience for above use case.
Happy New Year!

This can be solved by using a middleware that does not pass jwt to pass without validation; pass jwt to validate, and 401 if the validation does not pass, like this: https://github.com/Mikaelemmmm/go-zero-looklook/blob/main/common/middleware /commonJwtAuthMiddleware.go

Thanks for the prompt response!
Was just wondering if there's a built-in way to do it, I will stick with the middleware approach.
Thanks once again!


Disabling auto ripper causes crash

Hi Jlesage,
Thanks you the docker image. So much easier than compiling the source...
I'm still setting it up on my Synology, and got everything running(except eject), so I enabled the auto rip function, which worked as expected. But disabling auto rip, after it was enabled, causes the following crash:
From the log:

stdout	[cont-init.d] 95-check-optical-drive.sh: looking for usable optical drives...
stdout	[cont-init.d] 95-check-optical-drive.sh: found optical drive [-, /dev/sg4], group 0.
stdout	[cont-init.d] 95-check-optical-drive.sh: WARNING: for best performance, the host device - needs to be exposed to the container.
stdout	[cont-init.d] 95-check-optical-drive.sh: exited 0.
stdout	[cont-init.d] 96-install-autodiscripper-srv.sh: executing...
stdout	[cont-init.d] 96-install-autodiscripper-srv.sh: automatic disc ripper disabled.
stdout	[cont-init.d] 96-install-autodiscripper-srv.sh: exited 0.
stdout	[cont-init.d] done.
stdout	[services.d] starting services
stdout	[services.d] starting ERROR: Service 'app' depends on unexisting service 'autodiscripper'.
stdout	...
stderr	s6-svc: fatal: unable to control /var/run/s6/services/ERROR: Service 'app' depends on unexisting service 'autodiscripper'.
stderr	: No such file or directory
stdout	[services.d] done.

After this makemkv is dead. No gui etc...

Are you deleting and re-creating the container when you change the environment variable ?

I was just changing the env parameters and restarting.

So it's working now ?


Upload issues creating new subject set

I seem to be getting an error repeatedly at the same point, when I get to the 671st image uploaded to subject set 2892:
https://www.zooniverse.org/lab/14/subject-set/2892
I have run into this, oddly enough, repeatedly whether I upload 800 images at a time, or 600 in 100 image batches then another 100 etc etc.

Strange, it's not subject limits (checked). I'm pretty sure this is related to local network issues but if it's always the 671st image upload then something funky could be up.
@tedcheese any chance you can send a screenshot of the browser console / network tab when this error is happening?That XMLHttpRequest error isn't very helpful but does indicate an error.

Hmmm well it has allowed me to upload the rest of the set. Sorry, should have grabbed that browser console screenshot; will do so next time. This is the second time this issue has occurred, difference was that this time I had very good local network connectivity.
I've completed the upload and activated these new subject sets. Would you approve the project so that it's publicly visible again?
Happy new year :)

done re project approval. can you try and get more info the next time this happens?
I'm going to close this for now but feel free to re-open with more info.

yes definitely will find out what I can next time. Thanks


Support rfc2445?

http://www.ietf.org/rfc/rfc2445.txt
http://niemeyer.net/python-dateutil#head-470fa22b2db72000d7abe698a5783a46b0731b57
https://github.com/django-recurrence/django-recurrence

@Koed00 any comments on this?
Seems like a great improvement: allows very advanced schedules and cleans up scheduler code.
Only cons would be the need for a new field widget. There is django-recurrence but that's another dependency I don't know you want.


EC2 Enhanced networking support for official AMIs

I found a disappointing issue with NixOS on AWS EC2 - absence of support for Enhanced Networking (SRI/OV) out of box.
See docs at http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html
Here are separate issues:

ixgbevf is outdated on 16.03 (less then recommended 2.14). Amazon Linux AMI is better then NixOS here
HVM amis are built without --sriov flag. Because of 1) this makes starting spot instances with --sriov trickier

As I'm not an expert in AMI creating, instance management or kernel module packaging, I won't do pull requests on this topic. But I'd like to share some success with others.
Here is the  ixgbevf-3.1.2 kernel module package. Docs say it

supports kernel versions 2.6.18 up through 4.3.3

        ixgbevf = { stdenv, fetchurl, kernel }: stdenv.mkDerivation rec {
          basename = "ixgbevf-${version}";
          name = "${basename}-${kernel.version}";
          version = "3.1.2";

          src = fetchurl {
            url = "mirror://sourceforge/e1000/ixgbevf%20stable/${version}/${basename}.tar.gz";
            sha256 = "1vkrxbp9r3rw1q4ar26gny14swl0wlznvpvbbqdlkk2sdahkfpw4";
          };

          buildInputs = [ pkgs.xz ];

          kernelVersion = kernel.modDirVersion;

          preBuild = ''
            cd src
            substituteInPlace Makefile \
              --replace "\$(shell uname -r)" "$kernelVersion" \
              --replace "/lib/modules" "${kernel.dev}/lib/modules"
          '';
          installPhase = ''
            xz ixgbevf.ko
            install -m444 -Dt $out/lib/modules/$kernelVersion/kernel/drivers/net/ethernet/intel/ixgbevf ixgbevf.ko.xz
          '';
          meta.priority = 1;             # we want this to replace stock ixgbevf.ko.xz
        };

And here is extract from config to enable this module:
          boot.extraModulePackages = [ (ixgbevf { inherit (pkgs) stdenv fetchurl; kernel = pkgs.linuxPackages.kernel; }) ];
          boot.initrd.kernelModules = [ "ixgbevf" ];

My instance started and ssh works. Now I have this:
# ethtool -i eth0
driver: ixgbevf
version: 3.1.2
firmware-version: N/A
expansion-rom-version:
bus-info: 0000:00:03.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: no

Ping @edolstra

Thanks, I wasn't aware of Enhanced Networking. I'll look into it.

Added the driver to the Amazon config: 04eb7492dccb3d314911666fea15a67602c1e422, 3adb769776199ea5e4fe8760fca0e4dca3193fae. Will need to rebuild the AMIs though (and make NixOps enable Enhanced Networking automatically), and add the ena driver for x1 instances.


Add a link to the doc in the basic parser section

Comes handy

Coverage decreased (-0.4%) to 82.277% when pulling 59c77cc921abef6875293c0394082058c64b9b3f on lu-zero:patch-3 into 80a1deab58d1faf41c05a5d741d9e3f51bde3a55 on Geal:master.

Coverage decreased (-0.4%) to 82.277% when pulling 59c77cc921abef6875293c0394082058c64b9b3f on lu-zero:patch-3 into 80a1deab58d1faf41c05a5d741d9e3f51bde3a55 on Geal:master.

thanks!


New Sphinx Immaterial Theme for CVXPY

Description
Please include a short summary of the change.
Issue link (if applicable):
Type of change

[ ] New feature (backwards compatible)
[ ] New feature (breaking API changes)
[ ] Bug fix
[x] Other (Documentation, CI, ...)

Contribution checklist

[x] Add our license to new files.
[x] Check that your code adheres to our coding style.
[x] Write unittests.
[x] Run the unittests and check that they’re passing.
[x] Run the benchmarks to make sure your change doesn’t introduce a regression.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Transurgeon seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

I'm excited about all of this! I think merging should be blocked on removing the readthedocs file that was just for prototyping. Is this correct?

Yes, I was just about to say. Let me remove the readthedocs file now.


FormControlLabel produces error 'Element type is invalid:'

When used as per the website example thusly:
import {
    Checkbox,
    RadioGroup,
    Select,
    TextField,
    Switch,
    FormControlLabel
} from 'redux-form-material-ui'

<FormControlLabel control={<Field name="Solo" component={Checkbox} /> } label="Solo?" />

I get the following error:
Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

FormControlLabel must be imported from Material Ui like so:
import FormControlLabel from '@material-ui/core/FormControlLabel';
Example needs to be updated.


Upgrade to use Node 4 or newer

We currently are pegged at iojs-2.3.1.
This is because newer versions of iojs and Node had some issues with various libraries and also because the build of Electron that this is built against is using iojs-2.3.1 so it creates a consistent environment.
react-native is now marked as only working against Node 4 and newer. We should upgrade and upgrade the Electron build we are using so that it is also on Node 4+.

Done as of Electron 0.34


Stream link template not show full file name so Trakt API and OpenSub not work on external player

Stream link template not show full file name so Trakt API not work on external player
Exp:
https://mediafusion.elfhosted.com/streaming_provider/*Masked*/stream?info_hash=8fbb150d8ba97e2f044117d8046b77d86263cbe5&season=1&episode=6
https://mediafusion.elfhosted.com/streaming_provider/*Masked*/stream?info_hash=937d1159102309d8b0b8b9470599fe5e9ad02e31&season=1&episode=6
Basically now the external player will get the Video file name as stream.
Exp:
Infuse & IINA need file name have template like this
https://hkg1.download.real-debrid.com/d/XXXX/Monsieur.Spade.S01E02.1080p.AMZN.WEB-DL.DDP5.1.H.264-NTb[EZTVx.to].mkv
This is a direct link from real-debrid.
This new template from the Stremio- Jacket which work with Trakt now.
Original he had the similar stream link template like you ( I also the one reported this issue with him)

This one is from torrentio which worked as well ( IMO still the best option- the one I cover is a string which had my API token for Real-Debrib)

By: @olivergiangvu

@olivergiangvu i deleted your original post due to its expose your RD token in MediaFusion Link. so dont post your config link in a public forum. Make sure to reset your RD OAuth code and private key.

I believe this issue is due to this bug https://github.com/Stremio/stremio-web/issues/720 ?

I believe this issue is due to this bug Stremio/stremio-web#720 ?

After read through this bug, I think this not 100% related.
The main thing come from how player use metadata to scrobble Trakt API and search for Subtitle with OpenSub API.
For Infuse/IINA they limited on File Name  and URL only so on the Stream URL need to have these thing in order for them to recognize the metadata - and it should be at the last string of the URL ( based on all my testing so far).
All other addon  that fixed toward that direction wil result a perfect scrobbling when passing URL from Stremio/Kodi/Vidi/ Streamer App to external players.

MediaFusion is not working like this. As you know, the recent debrid changes removed the instant availability endpoint which those addon used to fetch the file data prior to user open a stream. however the MediaFusion took a different approach since it will be downloading once the user start to play that stream.
These url are redirect url. So redirector will resolve the RD link. Why isn't those players are implemented based on the final url?

MediaFusion is not working like this. As you know, the recent debrid changes removed the instant availability endpoint which those addon used to fetch the file data prior to user open a stream. however the MediaFusion took a different approach since it will be downloading once the user start to play that stream.
These url are redirect url. So redirector will resolve the RD link. Why isn't those players are implemented based on the final url?

I don't know technical enough from the player side but seem that the limitation currently for Infuse/IINA.
They can only extract the media/file name from the x-callback URL to match with Trakt and TVDB metadata
https://community.firecore.com/t/pass-metadata-details-via-x-callback-url/51278
https://support.firecore.com/hc/en-us/articles/215090997-API-for-Third-Party-Apps-Services
For IINA - based on an external. scrobbler. for Trakts https://github.com/iamkroot/trakt-scrobbler
And also the similar way like Infuse to get metadata for the Sub searching process.

Added support for showing the video file name in the URL.

Note that the name of the video will only be included if mediafusion already knows about it. Otherwise, it won't be included. Then someone start to play that torrent via file data trusted debrid services like RD then the file name get updated so the next time it will be shown.


The bot keeps telling me I do not have permissions, I'm the guild owner and I added my ID to the controllers section of the json file.

the id needs to be in between 2 "

ah, of course that's the only thing I didn't try (although I did try single quotes)


Update quickstart.md

Felt like the line wasn't finished yet.

Pull Request Test Coverage Report for Build 331281802

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 70.997%

Totals

Change from base Build 256586589:
0.0%

Covered Lines:
1082

Relevant Lines:
1524

💛  - Coveralls

Thanks for the contribution! Awesome. :+1:


Prevent releasing if a job failed.

Hi.
Before this PR, it was possible to do a release if the linter, document checks or the local-gadget unit tests failed.
This PR corrects this bad behavior:

Linter failed and no release is published.
Everything is OK and release is published.

Best regards.

Thank you for the review!


add relatedobjects for immediate creation by CVO

since https://github.com/openshift/cluster-version-operator/pull/318 merged we can have our relatedObjects created immediately so must-gather always works.

/cherrypick release-4.4

/retest

/retest


Tab name

The image should have the file's title at the top, such as index.js. The name should be of the file from which the screenshot is taken.
Also, this tab name should be toggleable from VSCode settings.

Please assign this issue to me @khattakdev


remove wget command

remove wget command from all bootstrap / scripts and replaces it with a standard command such as curl

:tada: This issue has been resolved in version 1.8.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


revert: "chore(deps): update dependency flutter to >=1.22.6"

Reverts zeshuaro/google_api_headers#194

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

v3.0.0
GitHub release

Your semantic-release bot :package::rocket:


Space - Cathy

React Tic Tac Toe
Congratulations!  Please reflect on the assignment with these questions.
Reflection

Prompt
Response

How are events / event handlers and useState connected?
The useState hook allows us to set an initial state of the 9 squares and set new states with a setState function. A callback function that embeds the setState function is passed as props to the Square components so that when an event triggers, it is able to handle the event by calling the callback function and sending back an ID. By calling the callback function, it calls the setState function and sets the new state accordingly.

What are two ways to do "dynamic styling" with React? When should they be used?
External CSS styling sheets or inline CSS styling. External CSS is preferred and can utilize variable classNames or ternary for dynamic styling.

Much like Rails works with the HTTP request->response cycle, React works with the browser's input->output cycle. Describe React's cycle from receiving user input to outputting different page content.
user input -> event triggers -> handle event -> set new state with the setState hook -> find diff in virtual DOM -> re-render -> display new state?

CS Fundamentals Questions

Question
Answer

What do you think is the BigO complexity of the method you use to compute a winner?
Time-complexity: O(n) where n is the number of squares // Space Complexity: O(1) since I am only using 1 extra variable emptySquares as a counter

Consider what happens when React processes a state change from setState -- it must re-render all of the components that now have different content because of that change.What kind of data structure are the components in, and what sort of algorithms would be appropriate for React's code to "traverse" those components?Speculate wildly about what the Big-O time complexity of that code might be.
When React processes a state change, it is finding differences in the (virtual) DOM, and the DOM is structured as a Tree. I'm guessing the time complexity would be approximately O(n) where n are all the nodes if React is checking node by node. Not sure if a depth-first search on the tree will be more appropriate if React can find the changed parent component first and search down the nested sub-components?

React Tic Tac Toe

Major Learning Goals/Code Review

Criteria
yes/no, and optionally any details/lines of code to reference

Demonstrates proper JavaScript coding style.
✔

Correctly passes props to child components.
✔

Correctly passes callback functions to child components and calls them to respond to user events.)
✔

Maintains the status of the game in state.
✔

Practices git with at least 6 small commits and meaningful commit messages
✔

Uses existing stylesheets to render components
✔

Functional Requirements

Functional Requirement
yes/no

The Square component renders properly and executes the callback on a click event.
✔

The Board component renders a collection of squares
✔

The App component renders a board and uses state to maintain the status of the game.
✔

Utilizes callbacks to UI events to update state
✔

Overall Feedback

Overall Feedback
Criteria
yes/no

Green (Meets/Exceeds Standards)
5+ in Code Review && 3+ in Functional Requirements

Code Style Bonus Awards

Was the code particularly impressive in code style for any of these reasons (or more...?)

Quality
Yes?

Perfect Indentation
✅

Elegant/Clever
✅

Descriptive/Readable
✅

Concise
✅

Logical/Organized
✅

Summary
Great work, you hit all the learning goals here.  Well done.


Abstract setting drivetrain motor powers

Summary
Implements an abstracted function for setting movement powers on drivetrain.
Motivation
Allows for PTO pull request to affect less unrelated code, making it easier to maintain as the rest of LemLib is updated. Also makes future changes like using brake modes cleaner.
Test Plan
Run all movements to ensure results are the same as before.
Additional Notes
If merged, future movement functions should call this function instead of individually setting left and right side motor powers.

Download the template for this pull request:

[!NOTE]
This is auto generated from Add Template to Pull Request

via manual download<EMAIL_ADDRESS>via PROS Integrated Terminal:

curl -o<EMAIL_ADDRESS>https://nightly.link/LemLib/LemLib/actions/artifacts/1426765511.zip;
pros c fetch<EMAIL_ADDRESS>pros c apply<EMAIL_ADDRESS>rm<EMAIL_ADDRESS>

@Miniongolf is this still being worked on?

closing, stale


 Teleport rules are denied by default, but as users create new roles, a baseline deny policy (policy boundaries) will ensure that insecure rules are never authored.
E.g., rules (all deny):

Never allow users to create a role that allows root access to dev cluster (Node.login == root) (Node.labels["env"] == "dev")
Never allow users to create a role that allows user named contractor access any node in prod cluster (User.name == contractor) (Node.labels["env"] == "prod")

Why

It will let us implement policy boundaries as described here.
Highlight violating rules in vscode extension, predicate deploy command etc.

How
This can be done by providing default opinionated recommendation (e.g., flag wildcard assignment) and by letting user's define custom secure baseline.

This can be closed now as first implementation of policy baseline is implemented with https://github.com/gravitational/predicate-lang/pull/61 and more of the policy baselines will be added soon.


cip-mm sort by tag instead of checksum

What would you like to be added:
Currently, if you use cip-mm to promote images, it sorts the generated file by the checksum of the promoted container images. Ideally it would allow sorting the generated file by tag instead or have an option to provide that as a argument.
Why is this needed:
If you promote images for multiple architectures it makes it very difficult to spot if all of them are there when looking at the file.
See for example: https://github.com/kubernetes/k8s.io/pull/2595/files

Hey @mrueg, thanks for filing this (and for using the tools here!)
First up, I want to point out kpromo pr, which includes much of the functionality of cip-mm and should be your go-to tool for creating image promotion PRs. You can read more about it here: https://github.com/kubernetes-sigs/promo-tools/blob/main/docs/promotion-pull-requests.md

it sorts the generated file by the checksum of the promoted container images. Ideally it would allow sorting the generated file by tag instead or have an option to provide that as a argument.

Now, onto this question...
It's actually something I asked when I started using the tool.
The manifest format is a map[string][]string https://github.com/kubernetes-sigs/promo-tools/blob/b245668212a77e73f0f862c9b3f740ea88f1502f/image/image.go#L47-L49
to support mapping a digest to multiple tags, which you can see an example of here: https://github.com/kubernetes/k8s.io/blob/48f96e52a326b0b7ec09ea29de18be9368533950/k8s.gcr.io/images/k8s-staging-artifact-promoter/images.yaml#L27
I agree that this is maybe not intuitive and I'm not saying that we couldn't change it, but it would:

affect the way the promoter reads in images
require us to update all manifests to support this

@kubernetes-sigs/release-engineering @listx -- curious to hear your thoughts here.

Thanks for creating those tools and taking the time to answer this request @justaugustus
I'll update our downstream doc accordingly and will mention kpromo there https://github.com/kubernetes/kube-state-metrics/blob/master/RELEASE.md#prepare-your-release
On the second part, I can see that it is a larger change and agree that it might have only little benefit eventually. For updating all manifests, that could be done in a single batch probably. I haven't thought about the option to have multiple tags on a single digest. I guess for those cases sorting will be difficult.

I agree with this, making sure all intended images in the promo PRs is cumbersome.
I think, however, that it's important to treat separately things intended to be read by machines from those intended to be read by humans.
In this particular case I think I would favor a clear overview of changes in the command line output and having a summary of changes in the PR body for human consumption while leaving the data files as they are for machines to read.

We should move away from expecting humans to examine the YAMLs directly and leave that instead up to a tool. Said tool was proposed a while back here https://github.com/kubernetes-sigs/promo-tools/issues/254, although it didn't gain enough traction.
To make an analogy, it's like how Git saves data under .git/objects/... but gives you the git diff/log/etc tooling to see human-friendly commit information (Git does not expect human users to browse .git/objects/... folder directly). I think the same thing applies here as the YAML manifests become ever larger and becomes difficult to reason about (when put under traditional text-based tooling like diff).
Separately, I'd like to state for the record that I haven't been able to help maintain this project as much as I would have liked due to new work commitments. But in my absence, please defer to @justaugustus.

i did a pr while back https://github.com/kubernetes-sigs/promo-tools/pull/251 and we discussed this.

cc @vincepri @fabriziopandini since we had a similar question when try to use kpromo for Cluster API images

Thanks @CecileRobertMichon for pointing to this thread!
While I understand the reasoning about YAML for machines, I think that changing the ordering to tag, or possibly image/tag, is a small improvement that provides great benefits for the people reviewing the generated PRs.
Rephrasing a little bit, given that the generated PRs requires human intervention and PRs diff shows YAML, IMO a different ordering will be beneficial for all the promo tool users.

I wrote a POC of what this could look like just to show that it's possible. Code is a little spaghetti but it could probably be cleaned up a bit.
result PR: https://github.com/kubernetes/k8s.io/pull/3264
branch: https://github.com/kubernetes-sigs/promo-tools/compare/main...CecileRobertMichon:sort-by-tag

+1, this makes this much easier to read while looking at the code

One question about the statement you made above @justaugustus:

I'm not saying that we couldn't change it, but it would:

affect the way the promoter reads in images
require us to update all manifests to support this

I'm wondering if that's actually required, since some manifests, eg. cluster-api, are not currently sorted by digest since they are manually written by humans and haven't been using the promo-tools so far, and it still works.

opened https://github.com/kubernetes-sigs/promo-tools/pull/493, please review

(Tracking cip-mm deprecation in https://github.com/kubernetes-sigs/promo-tools/pull/507.)


Introduces templating for custom tree ensemble operators and support float 16

Codecov Report
All modified lines are covered by tests :white_check_mark:

Comparison is base (d6d826c) 78.15% compared to head (90a1139) 78.15%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #94   +/-   ##
=======================================
  Coverage   78.15%   78.15%
=======================================
  Files          34       34
  Lines        3461     3461
=======================================
  Hits         2705     2705
  Misses        756      756

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


"Chase Approvals" action item

Based off of #196 it would be cool if we added some unique behaviours which could increase productivity.
The feature would simple send a new comment on behalf of the user mentioning each of the reviewers (and file owners if they get added to the API) and asking them to take a look.
Would make GitHawk quite fast if you have a lot of PRs and just need to get people looking at them!
Thoughts?
"@rnystrom waiting on your review!"
"Sherlouk chased reviews! ＠rnystrom and ＠BasThomas are remaining!"

Sweet idea. Ya these sort of features would put this app into hyperdrive. Ya could have a "stale" PR/issue section and then ping owners.


QOL-7992 Add CKAN 2.9 compatibility

Split routing into Pylons and Flask versions
Split CLI support into Paster and Click versions
Use 'six' to handle different string types in Python 2 and 3
Skip resource revisions on CKAN 2.9+
Add tests for CKAN 2.7 while we're at it

@ThrawnCA , unsure why master was picked instead of develop, have change it to rebase to develop and there is conflicts.

@ThrawnCA , unsure why master was picked instead of develop, have change it to rebase to develop and there is conflicts.

Oops, that was just the default branch. Resolved conflict now.


Dependency Version Updates

Updates for all dependencies will be notated in this issue. Please subscribe to get notified of the latest updates.

The latest jQuery 2.2.0 version has been added to the global inclusive bundle.
A UMD bundle has been added in ./dist/umd

No version updates, however Electron support has been added to typhonjs-core-gulptasks and there is a new demo that shows how easy it is to create a desktop app from the bundled web app at electron-backbone-es6-localstorage-todos.

backbone-es6 is now at parity with Backbone 1.3.3. New ./dist/ bundles have been generated and jQuery has been updated to v2.2.3 in the global inclusive bundle.


Faster classloader filtering

Use a trie to check for allowed/disallowed package prefixes in FilteringClassLoader.

Started a performance test build against the latest nightly (that the branch is based on) here: https://builds.gradle.org/viewQueued.html?itemId=15929631

Lots of tests failing in workers, is it worth a review yet?

OK, so running the whole branch against the latest nightly shows no proved regression and quite a bit of improvement. I'm saying we should merge this. @melix, wanna take a look now?


Move webhook external dependency to internal

This copies the controller-runtime v0.1's webhook and runtime/inject
packages to an internal package, removing a direct dependency on
controller-runtime v0.1. This is a step towards updating the
controller-runtime dependency to the latest version, keeping the webhook
admission controller support.
The packages are copied into internal/pkg/crv01 dir. All the references
to controller-runtime webhook package now refers to the packages under
internal/pkg/crv01/webhook.

Updated the k8s and operator-sdk dependencies as well in this PR.


Vinodhmohan91 dev 1

Includes all additions and changes to README.md, notebooks and scripts for the repo from branch "Vinodhmohan91-dev-1"

Includes all additions and changes to README.md, notebooks and scripts for the repo from branch "Vinodhmohan91-dev-1"
No Conflicts with base branch

No conflicts - merging the vinodhmohan91-dev-1 branch into master


Default reponse change for /tv

Adds array of objects containing Icelandic TV channel names along with their endpoints. Backwards compatible and non breaking change that helps you build an application without updating the routes for channels

First commit had a syntax error, 2nd commit fixed it (validated the object that time :P), now Travis CI is giving me errors relating to the other endpoints, I think it might have something to do with the tests

Yeah don't worry about the tests, recurring problem..
@kristjanmik shouldn't we push this one through?


running backend and frontend at local ip only

Hi,
Somebody manage to run backend and frontend at the ip local only?
thanks.

Hi,
Somebody manage to run backend and frontend at the ip local only?
thanks.

Yes you can run Whaticket locally (i run both frontend and backend in the same machine), i have mine set as:
backend
NODE_ENV=DEVELOPMENT
BACKEND_URL=http://<IP_ADDRESS>
FRONTEND_URL=http://<IP_ADDRESS>:5555
PROXY_PORT=8085
PORT=8085

frontend
REACT_APP_BACKEND_URL = http://<IP_ADDRESS>:8085/

Hi @esteves67,
thanks for your reply.
I mean, can we bind spesific ip address?
i have local and public ip in the vps, and i just want to bind to ip local.
thanks.


Gui does not open in Fedora 35

[write something useful and descriptive here]
my log id: 6e4e7f0f913ee8c7bb23241c

a solution: https://github.com/keybase/client/issues/24688#issuecomment-974302715


New native-image output causes mandrel-integration-tests to fail on github actions

New native-image output causes mandrel-integration-tests to fail on github actions due to running under constraint memory which results in the following warning being thrown:
GC warning: 15.2s spent in 17 GCs during the last stage, taking up 50.65% of the time.

I see two ways to fixing this:

Pass -H:-BuildOutputGCWarnings to native-image when running in CI. Unfortunately it's not yet possible to dynamically pass additional arguments to native-image.
Add the warning to the whitelist.

Both ways would result in all GC warnings being hidden and rendering us unable to detect changes like going from 50% spent on GC to 70% being spent on GC. Ideally we would like to set a threshold that would allow us to detect such changes. The threshold would need to be set dynamically so that we could set it at a per machine/environment basis.

An automated fail of the build could be implemented by using the JSON output new in 22.3+ and do the calculations in the GHA script. Fail the build as needed.

Out of date


Force SSL missing when using Custom locations

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
YES, pulled today.

Are you sure you're not using someone else's docker image?
Yes, jc21/nginx-proxy-manager:latest

If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network? Not useing Lets Encrypt, but using custom SSL certs.

Describe the bug

A clear and concise description of what the bug is.
After adding a Proxy host using a custom SSL cert (I don't think this matters, but might) with the Force SSL option enabled the site redirects a expected, but when I add a Custom location, with Force SSL still enabled the redirection for HTTP to HTTPS no longer works or these lines are removed.

    # Force SSL
    include conf.d/include/force-ssl.conf;
These line can be be added back using the Advanced tab as a workaround. It seems the Force SSL is skipped when a Custom location is being used.

What version of Nginx Proxy Manager is reported on the login page?
v2.0.14

To Reproduce
Steps to reproduce the behavior:

Add a new Proxy host with Force SSL enabled.
Check the generated config file to confirm it has the force SSL lines. data/nginx/proxy_host/1.conf
Add a Custom location.
Check the generated config file to confirm it has the force SSL lines are now missing.

Expected behavior
To continue to include the force-ssl.conf file when a custom location is added.

i just encountered this issue on v2.3.1, I bypassed it by adding the include conf.d/include/force-ssl.conf; line to the custom configuration of each location, but still kind of annoying...

i have this problem too, and @Kenchava solution not work for me. one year later and we have this problem yet ?

Is there any reason as to why http-> https rewrite for forced SSL should be in the location / block and not part of the global server block? (same for HSTS)
https://github.com/jc21/nginx-proxy-manager/blob/301499dc525d39f226b391fb88f28385ce0cb008/backend/templates/proxy_host.conf#L46
Right now it does not work with custom locations because using another location / block would prioritize it over the first one.

To add to that, there seem to be redundant HSTS entries
https://github.com/jc21/nginx-proxy-manager/blob/301499dc525d39f226b391fb88f28385ce0cb008/backend/templates/proxy_host.conf#L47
https://github.com/jc21/nginx-proxy-manager/blob/301499dc525d39f226b391fb88f28385ce0cb008/backend/templates/proxy_host.conf#L13

I'm still having troubles with this. Statically hosted files served via NPM render continous 301 redirects unless I disable the checkbox for Force SSL. Even adding in the include line and manually adding the if statement into the custom box, I can't get this to work.


Switch to system bus instead of session bus

Jira Issues:

Checklist

[ ] Jira issue has been made public if possible
[ ] [RSPEED-] is part of the PR title
[ ] PR title explains the change from the user's point of view
[ ] Code and tests are documented properly
[ ] The commits are squashed to as few commits as possible (without losing data)

/packit build


Add counts to output?

So one of the ways we're using this is to find added/modified files to pass to our linter. We use           list-files: shell since we pass this list of files to the linter. However, we'd also like to get the count of files so that we can do some different conditionals based on the # of changed files.
Any objections to adding the count to the action outputs?

If there is use-case for it then why not. I will add it later today.
We already have ${FILTER_NAME}_files so this could be ${FILTER_NAME}_count or something like that.

If there is use-case for it then why not. I will add it later today.
We already have ${FILTER_NAME}_files so this could be ${FILTER_NAME}_count or something like that.

Thank you once again!

Thank you once again!


chore: upgrade spark ETL to Java 17 and EMR-6.15.0

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license
Summary
(describe what this merge request does)
Implementation highlights
(describe how the merge request does for feature changes, share the RFC link if it has)
Test checklist

[x] add new test cases
[ ] all code changes are covered by unit tests
[ ] end-to-end tests

[ ] deploy web console with CloudFront + S3 + API gateway
[ ] deploy web console within VPC
[ ] deploy ingestion server

[ ] with MSK sink
[ ] with KDS sink
[ ] with S3 sink

[ ] deploy data processing
[ ] deploy data modeling

[ ] new Redshift Serverless
[ ] provisioned Redshift
[ ] Athena

[ ] deploy with reporting

Is it a breaking change

[ ] add parameters without default value in stack
[ ] introduce new service permission in stack
[ ] introduce new top level stack module

Miscellaneous

[ ] introduce new symbol link source file(s) to be shared among infra code, web console frontend, and web console backend

Does China regions have emr-6.15 runtime?

yes.


Quick question

Wanting to just have fakenet respond like inetsim on a virtual interface...how do I tell fakenet to just listen on that interface?  Thanks.

Inside the config.ini you must enable, in linux version, the MultiHostMode and then set the option "LinuxRedirectNonLocal" with the name of the right interface (as default you find "*").
In any case I think there is some problem because also when fakenet is setted as multihost then it redirects all the traffic as SingleHost.

Thank you!

The LinuxRedirectNonlocal setting strictly concerns redirection of packets destined for foreign hosts. For example, packets destined for hard-coded malware C2 IP addresses or for the foreign IP addresses handed out by DNSListener. The setting does not restrict FakeNet-NG's overall purview to a single interface. For that, I have added issue #62.


Add long arguments support to Uninstaller (-console/-force)

This make uninstaller arguments more consistent with installer ones.

Just updated it, there's also a "-x" but I don't know what to use for a long label on this flag.

Just updated it, there's also a "-x" but I don't know what to use for a long label on this flag.

The -x option is to select the delete all checkbox option in the uninstaller dialog as far as I understand. But I have no long good wording for this either :-)

The -x option is to select the delete all checkbox option in the uninstaller dialog as far as I understand. But I have no long good wording for this either :-)

why not "--force"? 2 dashes seems more like the standard to me. Also why not --delete-all for the -x?

why not "--force"? 2 dashes seems more like the standard to me. Also why not --delete-all for the -x?

the -x option is use to hide the checkbox labeled "Force the deletion of", so it should be  something like -hide-force-option.
I'll add a commit with double dashes and this change.

Well ... Maybe addining 2 dashes support for every options (Uninstaller and Installer) should belong to another pull request.

@akuhtz is there any IZPACK issue for this?

@reinhapa I don't think so. I can create one.


Code lookup feature and Manual Entry Test name change

Created a new feature where you can now click on the valuesets and attritubutes in the record sample form and get a modal pop up with the list of codes associated to that oid. There is a filter functionality for that pop up so you can find the code you need. You can copy and paste any of the codes into the text box. Also changed all of the buttons headers etc. from Manual Entry Test to Record Sample.

still a few places with "Manual".  Change these to "Sample"

Also in the "Download Report"

Closing because the more urgent manual test naming changes were separated out into #781. The review comments here should be addressed in the near future.


MIGRATIONS-867 Added traffic generation container, README

Signed-off-by: Chris Helma<EMAIL_ADDRESS>Description
Added a README and a new Dockerfile that leverages the OpenSearch Benchmarking tool to drive traffic to the Demo Setup.  The README explains how to use the new Dockerfile
Issues Resolved

https://opensearch.atlassian.net/browse/MIGRATIONS-867

Testing
Tested the whole setup manually; you can see the results embedded in the README
Check List

[ ] New functionality includes testing

[ ] All tests pass, including unit test, integration test and doctest

[X] New functionality has been documented
[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #102 (bd3cc91) into main (7660fe3) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main     #102   +/-   ##
=======================================
  Coverage   91.74%   91.74%
=======================================
  Files          24       24
  Lines        1115     1115
  Branches      110      110
=======================================
  Hits         1023     1023
  Misses         80       80
  Partials       12       12

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Einrichtung fehlgeschlagen, wird erneut überprüft: Überprüfe die Protokolle

The problem already occurred in HA 2024.9.x, disappeared every time after a few restarts of HA. With the transition to HA 2024.10.0, the problem no longer disappears even after several restarts of HA or several “reloads” of Weishaupt WEM Portal. Going back to HA 2024.9.3 has not solved the problem.

Then it would be helpful if you could share the information from the protocol with us. I suspect it is the same error as already reported in #96(?).

It is not a Home Assistant version related issue. The issue is caused by changes Weishaupt made to their portal.

I have the same problem.
Log file:
Traceback (most recent call last):   File "/config/custom_components/wemportal/wemportalapi.py", line 254, in make_api_call     response.raise_for_status()   File "/usr/local/lib/python3.12/site-packages/requests/models.py", line 1024, in raise_for_status     raise HTTPError(http_error_msg, response=self) requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: https://www.wemportal.com/app/device/Read

Same for me

Same for me

The solution: https://github.com/erikkastelec/hass-WEM-Portal/issues/96

Fix has been released in the newest version (1.5.10)


[Request] Linux notifications to ChromeOS

This is the only thing I am seriously missing when using this extension. It'd be awesome if Crouton could see the notifications that pop up in Linux and push them to the notification system of ChromeOS. It might be beyond the scope of this extension, but it would be an incredible feature, which would make this extension perfect in my opinion. Also apologies if this isn't the place to post this, I didn't know where else to ask.

Yes, see #581. But I think what you suggest goes a bit further, so that "standard" X11 notifications are shown (I'm not sure what is actually standard, it looks like libnotify is commonly used).


Refactor jestream to allow different tokenizers

Issue
Currently we assume few things in jetstream which hinders it's generalization:

tokenizer is SentencePiece based.
pad_id is 0
after encode, we pad to nearest power of 2
ResultToken itself is jax specific (the @struct.dataclass annotation requires it's Jax pytreeable).

These assumptions hinders generalization (i.e. support wider varieties of models).
Examples:

llama3 uses tiktoken instead of SentencePiece
llama3 uses pad_id of -1
Pytorch GPU does NOT need to pad to nearst power of 2.
Pytorch GPU version of jetstream would like to use torch.Tensor to hold the data, which is not jax-pytreeable.

Proposal:

EngineAPI.get_tokenizer which returns the tokenizer, should be any object that implements the following interface:

def encode

def decode

@property
def pad_id

@property
def eos_id

Uses of tokenizer should restrict to only this methods.
In particular: encode should do both encoding and padding. So jetstream doesnt do any padding itself; the engine can choose how to pad (or not to pad) by returning a custom tokenizer object whose encode also does the padding.

Allow use different implementation for ResultTokens; same as Prefix and DecodeState. Implementations of the Engine can choose implementation of ResultTokens. jestream should interact with it only through it's 3 public methods (https://github.com/google/JetStream/blob/main/jetstream/engine/engine_api.py#L83)

def get_result_at_slot
def convert_to_numpy
def copy_to_host_async

and are not allowed to access it's fields directly.

#53, #67 adds the interface for tokenizer. Still need to work on ResultTokens.


Pods intermittently start in the non Calico IP range

Expected Behavior
Pods should always get an IP from within CALICO_IPV4POOL_CIDR
Current Behavior
In Calico 3.16.3 running in Amazon EKS pods are sometimes allocated an IP address directly from the VPC range rather than from CALICO_IPV4POOL_CIDR. This seems to happens when a scale event triggers a new node to be added to the cluster and the first pod scheduled on that node will get the incorrect IP.
Steps to Reproduce (for bugs)

Run Calico 3.16.3 in Amazon EKS 1.18 and CALICO_IPV4POOL_CIDR set to <IP_ADDRESS>/16
Scale a deployment to trigger a cluster scale up
Check the IPs assigned to each pod

Further info
Scale up a deployment to trigger a new node
kubectl scale deployment my-app --replicas=10

Look for pods allocated an IP outside of the CALICO_IPV4POOL_CIDR range
kubectl get pods | grep my-app
my-app-864dfdf977-2sqvw                               2/2     Running     0          14m     <IP_ADDRESS>    ip-100-99-37-12.ec2.internal    <none>           <none>
my-app-864dfdf977-54tb6                               2/2     Running     0          33m     <IP_ADDRESS>    ip-100-99-43-127.ec2.internal   <none>           <none>
my-app-864dfdf977-5k98r                               2/2     Running     0          13m     <IP_ADDRESS>   ip-100-99-36-237.ec2.internal   <none>           <none>
my-app-864dfdf977-6hklg                               2/2     Running     0          14m     <IP_ADDRESS>     ip-100-99-36-158.ec2.internal   <none>           <none>
my-app-864dfdf977-8dd98                               2/2     Running     0          13m     <IP_ADDRESS>   ip-100-99-40-163.ec2.internal   <none>           <none>
my-app-864dfdf977-fm7n6                               2/2     Running     0          32m     <IP_ADDRESS>     ip-100-99-40-204.ec2.internal   <none>           <none>
my-app-864dfdf977-pgtvv                               2/2     Running     0          13m     <IP_ADDRESS>     ip-100-99-40-211.ec2.internal   <none>           <none>
my-app-864dfdf977-tp7nd                               2/2     Running     2          14m     <IP_ADDRESS>      ip-100-99-39-160.ec2.internal   <none>           <none>
my-app-864dfdf977-vhxhz                               2/2     Running     0          13m     <IP_ADDRESS>   ip-100-99-42-61.ec2.internal    <none>           <none>
my-app-864dfdf977-z9b6m                               2/2     Running     0          13m     <IP_ADDRESS>      ip-100-99-37-223.ec2.internal   <none>           <none>

Events from the faulty pod
Events:
  Type     Reason                  Age                From                                    Message
  ----     ------                  ----               ----                                    -------
  Warning  FailedScheduling        <unknown>          default-scheduler                       0/131 nodes are available: 100 Insufficient cpu, 13 node(s) had taint {zzzOnly: true}, that the pod didn't tolerate, 18 node(s) had taint {yyyOnly: true}, that the pod didn't tolerate, 4 Insufficient memory.
  Warning  FailedScheduling        <unknown>          default-scheduler                       0/131 nodes are available: 100 Insufficient cpu, 13 node(s) had taint {zzzOnly: true}, that the pod didn't tolerate, 18 node(s) had taint {yyyOnly: true}, that the pod didn't tolerate, 4 Insufficient memory.
  Warning  FailedScheduling        <unknown>          default-scheduler                       0/132 nodes are available: 1 node(s) had taint {node.kubernetes.io/not-ready: }, that the pod didn't tolerate, 100 Insufficient cpu, 13 node(s) had taint {zzzOnly: true}, that the pod didn't tolerate, 18 node(s) had taint {yyyOnly: true}, that the pod didn't tolerate, 4 Insufficient memory.
  Warning  FailedScheduling        <unknown>          default-scheduler                       0/133 nodes are available: 100 Insufficient cpu, 13 node(s) had taint {zzzOnly: true}, that the pod didn't tolerate, 18 node(s) had taint {yyyOnly: true}, that the pod didn't tolerate, 2 node(s) had taint {node.kubernetes.io/not-ready: }, that the pod didn't tolerate, 4 Insufficient memory.
  Warning  FailedScheduling        <unknown>          default-scheduler                       0/134 nodes are available: 100 Insufficient cpu, 13 node(s) had taint {zzzOnly: true}, that the pod didn't tolerate, 18 node(s) had taint {yyyOnly: true}, that the pod didn't tolerate, 3 node(s) had taint {node.kubernetes.io/not-ready: }, that the pod didn't tolerate, 4 Insufficient memory.
  Warning  FailedScheduling        <unknown>          default-scheduler                       0/135 nodes are available: 100 Insufficient cpu, 13 node(s) had taint {zzzOnly: true}, that the pod didn't tolerate, 18 node(s) had taint {yyyOnly: true}, that the pod didn't tolerate, 4 Insufficient memory, 4 node(s) had taint {node.kubernetes.io/not-ready: }, that the pod didn't tolerate.
  Normal   Scheduled               <unknown>          default-scheduler                       Successfully assigned ia-rtl/myapp-864dfdf977-tp7nd to ip-100-99-39-160.ec2.internal
  Normal   TriggeredScaleUp        55m                cluster-autoscaler                      pod triggered scale-up: [{my-asg-az-a-spot2020032809172642090000001e 12->13 (max: 30)}]
  Warning  FailedCreatePodSandBox  52m                kubelet, ip-100-99-39-160.ec2.internal  Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "6ee29b7d58549b3af9686e16caa36a58fe391e0ae8fa3fb85758717f05b072e7" network for pod "myapp-864dfdf977-tp7nd": networkPlugin cni failed to set up pod "myapp-864dfdf977-tp7nd_ia-rtl" network: stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/
  Warning  FailedCreatePodSandBox  52m                kubelet, ip-100-99-39-160.ec2.internal  Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "6b8059960157aafd6d71c36ace32e72e1e4720f81ababf45bb1ed868e31491a6" network for pod "myapp-864dfdf977-tp7nd": networkPlugin cni failed to set up pod "myapp-864dfdf977-tp7nd_ia-rtl" network: stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/
  Normal   SandboxChanged          52m (x2 over 52m)  kubelet, ip-100-99-39-160.ec2.internal  Pod sandbox changed, it will be killed and re-created.

  Normal  NodeHasSufficientMemory  56m (x2 over 56m)  kubelet, ip-100-99-39-160.ec2.internal  Node ip-100-99-39-160.ec2.internal status is now: NodeHasSufficientMemory
  Normal  NodeHasNoDiskPressure    56m (x2 over 56m)  kubelet, ip-100-99-39-160.ec2.internal  Node ip-100-99-39-160.ec2.internal status is now: NodeHasNoDiskPressure
  Normal  NodeHasSufficientPID     56m (x2 over 56m)  kubelet, ip-100-99-39-160.ec2.internal  Node ip-100-99-39-160.ec2.internal status is now: NodeHasSufficientPID
  Normal  NodeAllocatableEnforced  56m                kubelet, ip-100-99-39-160.ec2.internal  Updated Node Allocatable limit across pods
  Normal  NodeReady                55m                kubelet, ip-100-99-39-160.ec2.internal  Node ip-100-99-39-160.ec2.internal status is now: NodeReady

The faulty pod started at 09:15:20:
k describe pod my-app-864dfdf977-tp7nd | grep -i '09:1'
Start Time:   Tue, 19 Jan 2021 09:15:20 +0000
      Started:      Tue, 19 Jan 2021 09:15:42 +0000
      Finished:     Tue, 19 Jan 2021 09:15:43 +0000
      Started:      Tue, 19 Jan 2021 09:18:22 +0000
      Started:      Tue, 19 Jan 2021 09:16:58 +0000
      Finished:     Tue, 19 Jan 2021 09:17:58 +0000
      Started:      Tue, 19 Jan 2021 09:15:58 +0000

I noticed the NetworkUnavailable node status changed 4 seconds later at 09:15:24, I'm not sure if this is relevant
Conditions:
  Type                 Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message
  ----                 ------  -----------------                 ------------------                ------                       -------
  NetworkUnavailable   False   Tue, 19 Jan 2021 09:15:24 +0000   Tue, 19 Jan 2021 09:15:24 +0000   CalicoIsUp                   Calico is running on this node
  MemoryPressure       False   Tue, 19 Jan 2021 10:09:18 +0000   Tue, 19 Jan 2021 09:14:08 +0000   KubeletHasSufficientMemory   kubelet has sufficient memory available
  DiskPressure         False   Tue, 19 Jan 2021 10:09:18 +0000   Tue, 19 Jan 2021 09:14:08 +0000   KubeletHasNoDiskPressure     kubelet has no disk pressure
  PIDPressure          False   Tue, 19 Jan 2021 10:09:18 +0000   Tue, 19 Jan 2021 09:14:08 +0000   KubeletHasSufficientPID      kubelet has sufficient PID available
  Ready                True    Tue, 19 Jan 2021 10:09:18 +0000   Tue, 19 Jan 2021 09:15:18 +0000   KubeletReady                 kubelet is posting ready status

Calico logs from this node are attached below
calico-node-2r5tm.yaml.zip

Hi @2ZZ can you validate what CNI plugin you are using on EKS and maybe provide the logs for the CNI plugin? My first thought is that the CNI plugin is borrowing from a separate range of IPs prior to the node being ready which is why you might see only the first pod being scheduled in a different IP range than the others.

Hi @2ZZ can you validate what CNI plugin you are using on EKS and maybe provide the logs for the CNI plugin? My first thought is that the CNI plugin is borrowing from a separate range of IPs prior to the node being ready which is why you might see only the first pod being scheduled in a different IP range than the others.

Hi @mgleung, it is aws-cni with CNI-Genie also running on there. I asked on Calico Slack and it was suggested CNI-Genie is likely the problem. I can upload logs tomorrow.
I think what is happening is:

node starts
aws-cni starts and sets NetworkReady to true
my app pod is scheduled on the node and gets the wrong IP
calico + cni-genie pods are scheduled and networking gets fully configured
future pods get the correct IPs

Hi @mgleung, it is aws-cni with CNI-Genie also running on there. I asked on Calico Slack and it was suggested CNI-Genie is likely the problem. I can upload logs tomorrow.
I think what is happening is:

node starts
aws-cni starts and sets NetworkReady to true
my app pod is scheduled on the node and gets the wrong IP
calico + cni-genie pods are scheduled and networking gets fully configured
future pods get the correct IPs

Yeah, that's exactly what's going on here, if I had to guess. The cluster will have AWS CNI by default, and Calico won't be available until CNI genie is installed.
This isn't a configuration that we test or support, so I can't provide much more information on it. What is it that you're trying to do?

Thanks @caseydavenport
I worked around it by putting a pre-init script in aws-cni to wait for genie to exist before starting itself.


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add doxygen comments to dust code

Updated existing comments in dust_cuda.cu and added Doxygen comments to dust_cuda.h, dust_cuda.cu, and dust_cuda_tests.cpp. I'm unsure I used \param[in] and \param[out] appropriately in the function doc strings dust_cuda.h. I think that \param[out] should be used for an input parameter that I'm modifying, but not returning in the function, but in the case of dev_conserved I don't know if I should specify the field that I'm modifying or something like that. If anyone has thoughts on this, please let me know!

Here's what the \param in/out stuff means

\param[in] is for variables that are input only and will not be modified in the function. They should also be declared as const or pass by value in the function definition to enforce no unexpected changes
\param[out] is for variables that are output only. Their initial values will not be used and they should be passed in by reference or they should be a pointer type. Generally in this case you should just be returning the value from the function with a return statement; possibly with structured binding if needed.
\param[in, out]' is for variables that are both input and output. Their initial values will be used and the will also contain output; they should be passed in by reference or they should be a pointer type. dev_conservedis almost always either[in]or[in,out]`.

It looks like this failed on one of Bob's new MHD tests - can you try updating the submodule again?

(It's probably my fault for auto-merging in the most recent PR - I guess that doesn't update the submodule.)


Vendor in latest containers/image

Some more features.
docker-archive generates docker legacy compatible images
Do not create $DiffID subdirectories for layers with no configs
Ensure the layer IDs in legacy docker/tarfile metadata are unique
docker-archive: repeated layers are symlinked in the tar file
sysregistries: remove all trailing slashes
Improve docker/* error messages
Fix failure to make auth directory
Create a new slice in Schema1.UpdateLayerInfos
Drop unused storageImageDestination.{image,systemContext}
Load a *storage.Image only once in storageImageSource
Support gzip for docker-archive files
Remove .tar extension from blob and config file names
ostree, src: support copy of compressed layers
ostree: re-pull layer if it misses uncompressed_digest|uncompressed_size
image: fix docker schema v1 -> OCI conversion
Add /etc/containers/certs.d as default certs directory
Signed-off-by: Daniel J Walsh<EMAIL_ADDRESS>

@nalind @TomSweeneyRedHat PTAL

LGTM and happy green test buttons.

@rh-atomic-bot r+


Cooking

@keithyyy There are the cooking.js and storage.js file that you should be able to use in your code.

The code was implemented separately. It was integrated into a semantic js branch.


Both recommended sanitizers don't work on the server side.

Both isomorphic-dompurify and sanitize-html don't work on Cloudflare workers.
In the case of isomorphic-dompurify this is because it tries to access window on the server. This issue is documented here https://github.com/kkomelin/isomorphic-dompurify/issues/228
sanitize-html uses path which is unsupported on cloudflare workers.
isomorphic-dompurify would work perfectly if we could somehow stop it from trying to use window on the server side.
What do you recommend we do in this case?

Hello, I checked out the link you sent and it looks the issue is related to isomorphic-DOMPurify erroneously thinking it is working client-side.
What runtime do Cloudflare workers use? Because, from what you said, it looks like they are neither on a browser-like environment with access to Web API, nor on nodejs(as path is not available).
Anyway, if the problem is just isomorphic-DOMPurify thinking it is running on the client, you could install DOMPurify and jsDOM and create your own isomorphic version, which done by just updating the following:
import { browser } from '$app/environment'; // <== new

function importModule(requiredModule) {
    return requiredModule && requiredModule.default || requiredModule;
}

function initDOMPurifyWithJSDOM() {
  const DOMPurifyInitializer = importModule(require('dompurify'));
  const { JSDOM } = importModule(require('jsdom'));
  const { window } = new JSDOM('<!DOCTYPE html>');
  return DOMPurifyInitializer(window);
}

function resolveDOMPurify() {
  // const isClientSide = typeof window !== 'undefined'; <== remove this
  const isClientSide = browser; // <== use this instead
  return isClientSide ? importModule(require('dompurify')) : initDOMPurifyWithJSDOM();
}

module.exports = global.DOMPurify = global.DOMPurify || resolveDOMPurify();

I'm not 100% this will work, so let me know.
Anyway, for sanitize-html maybe you could manually install path.

https://github.com/jill64/universal-sanitizer
I found this alternative sanitzer and it works perfectly on both SSR and the browser. :fire:


Release 0.9.3

Nanpy 0.9.3 will be released next week, before 18 Feb. 2015.
@ponty have you anything pending that you want to see merged in 0.9.3 release?

Nothing special. I added Landscape.io badge, and fixed some warnings.
But I don't change the code until next release.

@ponty I'd like to freeze 0.9.3 on https://github.com/nanpy/nanpy/commit/5f574cb67a99b5d53d01b69f3d027c69c94eb2c0
Is it ok for you? anything pending?

OK!

Completed! :) :) :+1: :+1:


Add Event Update Route

Right now we have no ability to update an event.

Progress: almost done, needs google sheet range updated to reflect # of rows/cols in event sheet. Then needs tested.
Also, a delete route crossed my mind, so might be useful to make one in the future, but not necessary for MVP.


Another suggestion system

This is my own suggestion system in which I was lightly encouraged to PR here a while ago.
I am confident in saying that it is much cleaner then the one that is currently on here since I use a mention instead of using the footer to get the author of the suggestion
There is also sug list which shows 10 suggestions per page
There is also the auto-deletion (optional) so the suggestion channel doesn't become overbearing with the amount of suggestions in it
It support multiple comments, editing, deleting, and creating them.
I took the bit from my starboard system that scrapes images and such, and added it here, so it has pretty good image and other attachment(s) display, these are also shown in the sug list
I used the PR Piter made for my poll system CC to calculate the percentages of the reaction count.
This uses a similar idea to Devonte's suggestion system, in which suggestions are made by just typing into the suggestion channel, and it'll make an embed anbd such.
There are minimal bugs, although I will be updating this as I improve it and fix it.
Status

[x] Code changes have been tested on an instance of YAGPDB, or there are no code changes
[x] I have read and followed the contribution guide

@Crenshaw1312 is this still being worked on? Or should we close this pull request?

it fits within char requirements if if you remove all of the comments throughout the code, can't speak to the function of this though

@Crenshaw1312 are you still working on this or we should close this PR ?

AHHHHHHH I FORGOT I'LL DO IT

I'll change the comments and spacing so it should fit under 1k characters, I'll leave the top one tho with a note saying to delete it.

you'll have to delete those two files before merging, I have them in the PR no under proper folder names

aight should be good

bump @Crenshaw1312, are you still planning to work on this?

Going to close this for now based on the lack of response. Feel free to re-open if you'd like to continue working on this!


Updating remote access notebook

I'm fixing a few typos in the notebook and adding an explicit way of inspecting the I/O behavior of the different caching strategies implemented in fsspec. I'm also mentioning the impact of chunking in access performance, I think this is now a self contained notebook, I guess we could include the internals of Zarr next.

Hi @scottyhq! do you have suggestions on the failing checks? the link that is apparently broken is not really broken and the other is an example not a real link, on the spellcheck bot the fo is a reference to a file-like object.

Yeah, the link check unfortunately is finicky and I'm not sure how to exclude specific links. For the spellcheck, you can add fo to the ignore list https://github.com/xarray-contrib/xarray-tutorial/blob/08e762ead64fd598799f135068b15e8edfc8c37e/.github/workflows/qaqc.yaml#L39
Thanks for expanding the notebook, happy to do a full review!

Thanks @scottyhq the PR is ready for review.

Thanks for the thorough review @scottyhq! I'll address the suggestions early next week.


React Command Custom Command Bar is updated to RC0

Q
A

Bug fix?
no

New feature?
no

New sample?
no

Related issues?
no

What's in this Pull Request?
React Command Custom Command Bar is updated to RC0

@AJIXuMuK,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

thx Alex, appreciated.


Autogenerated docs contain text suggesting there are links when there are not

For example, https://www.pulumi.com/docs/reference/pkg/vsphere/tagcategory/ has a description "A list object types that this category is valid to be assigned to. For a full list, click here." But "click here" is not a link to anything. We should surface these during build time to ensure that we handle these links properly.

Note that in this case the source documentation is structurally very "unusual", and the offending "click here" is a link to another section within the page itself.  We would need to find a way to pull these subsections of the docs out into the Pulumi docs as well and to re-write cross links to them.
https://github.com/hashicorp/terraform-provider-vsphere/blob/master/website/docs/r/tag_category.html.markdown
The alternative would be to manually re-organize/edit this content in our fork.  It is likely the later is necessary here and elsewhere to address content that is sufficiently structurally "different" like this.


Autodoc doesn't abide by geiser-completion--symbol-begin

This causes the chicken symbol-prefixing to break autodoc.

Near as I can tell this is the biggest irritation with using Geiser and Chicken.

geiser-syntax--scan-sexps

Getting closer to a workable solution; it's changing how completions and autodoc work with chicken, though.


When running yarn run configure below error is shown

Describe the bug
When running yarn run configure
To Reproduce
Git clone and installing all steps from https://github.com/hyperledger/cactus/blob/1413bbe462d29ae2ee98a3f1373fdc818eb55885/BUILD.md
Screenshots
If applicable, add screenshots to help explain your problem.

Cloud provider or hardware configuration:
Are you running the software on a dev machine or somewhere in the cloud?
Operating system name, version, build:
Use this command: printf "$(uname -srm)\n$(cat /etc/os-release)\n"
Linux 5.15.0-27-generic x86_64
PRETTY_NAME="Ubuntu 22.04 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy
Hyperledger Cactus release version or commit (git rev-parse --short HEAD):
1413bbe4

What is your node version?

Should be fixed in https://github.com/hyperledger/cacti/commit/088da9fddef794f2983802e5d4294d0849ec4a69. Closing for now, please re-open if the issue still remains on the main branch.


BUILD Error when using momentjs

Type of Issue
[X] Bug Report
[ ] Feature Request

Description
As a few people before me, I cannot run ng-packagr when using moment. I tried the suggested solutions in other issues but I cannot get it to work.
I added the following:
"lib": {
"externals": {
      "moment": "moment"
    }
}

When using
import * as moment from 'moment';
I get the following
BUILD ERROR
Cannot call a namespace ('moment')
Error: Cannot call a namespace ('moment')

When using
import moment from 'moment'
time-line/node_modules/moment/moment"' has no default export

How To Reproduce
Include moment into something and try to run ng-packagr
I uploaded a small example of my setup to GitHub where the issue is reproducible
https://github.com/Nevergonnachange/moment-ng-packagr/tree/master/src
Expected Behaviour
Build passes
Version Information
ng-packagr: v1.6.0
node: v7.10.1
@angular: v5.0.0
rxjs: 5.5.2
zone.js: 0.8.18
moment: 2.19.2

Thank you very much in advance.

Try using moment-es6 instead of moment like so ...
import moment from 'moment-es6';

Hi @Nevergonnachange,
thanks for putting the repro up!
$ DEBUG=true yarn build
yarn run v1.3.2
$ ng-packagr -p ng-package.json
Building Angular library
[debug] Searching for ng-package config at #/moment-ng-packagr/ng-package.json
[debug] Ng-package config found at #/moment-ng-packagr/ng-package.json
[debug] loading package.json
[debug] Beginning package search from root #/moment-ng-packagr
[debug] Resolved secondary package paths:
[debug] rimraf #/moment-ng-packagr/dist
Generating bundle for moment-ng-packagr
Cleaning bundle build directory
[debug] rimraf #/moment-ng-packagr/.ng_pkg_build/moment-ng-packagr
Processing assets
[debug] processAssets #/moment-ng-packagr to #/moment-ng-packagr/.ng_pkg_build/moment-ng-packagr/ts
[debug] render stylesheet #/moment-ng-packagr/src/time-line.component.css
[debug] postcss with autoprefixer for #/moment-ng-packagr/src/time-line.component.css
Running ngc
[debug] ngc #/moment-ng-packagr/.ng_pkg_build/moment-ng-packagr/ts/tsconfig.lib.json, { basePath: #/moment-ng-packagr/.ng_pkg_build/moment-ng-packagr/ts })
[debug] prepareTsConfig: Resolved tsconfig path to #/moment-ng-packagr/node_modules/ng-packagr/lib/conf/tsconfig.ngc.json
[debug] Reading tsconfig from #/moment-ng-packagr/.ng_pkg_build/moment-ng-packagr/ts/tsconfig.lib.json
[debug] re-mapping sources for #/moment-ng-packagr/.ng_pkg_build/moment-ng-packagr/ts/moment-ng-packagr.js
Compiling to FESM15
[debug] rollup #/moment-ng-packagr/.ng_pkg_build/moment-ng-packagr/ts//moment-ng-packagr.js to #/moment-ng-packagr/.ng_pkg_build/moment-ng-packagr/moment-ng-packagr.js (es)

So this is not a ngc / tsc compile error but rollup goes bust when budling the individual js files to a flat es module file.
Here are some related answers to moment.js and rollup:

https://stackoverflow.com/a/40346098
https://stackoverflow.com/a/43847642
https://github.com/rollup/rollup-plugin-typescript/issues/68

Can you tell if any of these and which one works for you?

FYI: The rollup config ng-packagr generates is the following (bundleOptions):
{
  "context": "this",
  "external": [
    /* angular and rxjs default config here ... */
    "moment"
  ],
  "input": "#/moment-ng-packagr/.ng_pkg_build/moment-ng-packagr/ts//moment-ng-packagr.js",
   "plugins": [
     nodeResolve({ jsnext: true, module: true }),
     commonJs(),
   ]
}

Thank you very much for your fast response!
import moment from 'moment-es6';

Works fine for me.
The
import moment from 'moment';
+
"allowSyntheticDefaultImports": true

Adding a tsconfig.json with allowSyntheticDefaultImports set in the project root does not change anything. (as far as I understand I cannot change the tsconfig.json file for the ng-packagr).
I will for now use the moment-es6 workaround. It would still be nice to be able to get rid of it.
Thanks very much for you time and this awesome project.

Yeah, I had the same problem with the allowSyntheticDefaultImports solution. Didn't work. But the moment-es6 usage does. Which is fine until the moment project itself adopts it.

Ok, I dedicated moment.js its own section in that not-so-famous #129 :-)

By the way, I just switched to moment-with-locales-es6 because once I hooked up the library that uses moment-es6 to be used in another project I got the following warning ....
WARNING in<EMAIL_ADDRESS>Module not found: Error: Can't resolve './locale' in '/Users/ken/dev/animalus/au-ng/dist/ng-date-utils/@animalus'
resolve './locale' in '/Users/ken/dev/animalus/au-ng/dist/ng-date-utils/@animalus'
  using description file: /Users/ken/dev/animalus/au-ng/package.json (relative path: ./dist/ng-date-utils/@animalus)
    Field 'browser' doesn't contain a valid alias configuration
  after using description file: /Users/ken/dev/animalus/au-ng/package.json (relative path: ./dist/ng-date-utils/@animalus)
    using description file: /Users/ken/dev/animalus/au-ng/package.json (relative path: ./dist/ng-date-utils/@animalus/locale)
      as directory
        /Users/ken/dev/animalus/au-ng/dist/ng-date-utils/@animalus/locale doesn't exist
[/Users/ken/dev/animalus/au-ng/dist/ng-date-utils/@animalus/locale]
<EMAIL_ADDRESS>1589:12-46
 @ ./src/app/app.module.ts
 @ ./src/main.ts
 @ multi webpack-dev-server/client?http://<IP_ADDRESS>:0 ./src/main.ts

For a different workaround without the need to use moment-es6 nor allowSyntheticDefaultImports, please see https://github.com/dherges/ng-packagr/issues/163#issuecomment-345448834

@crowmagnumb Did you ever figure out a solution to this? Having the same issue now...

@elliotleelewis Yeah, as I indicated above I imported moment-es6 instead of moment.

@crowmagnumb Apologies, I misread your initial comment. I'm getting that same error when using moment-with-locales-es6 😞

2.18.1. Can you give us code examples and output?


deleted new daosession

Description
Made daoSession a singleton so that database deadlock does not occur.
Related issues and discussion
closes #1068 #1072

@Karljoones can you review this PR

@itchix @Karljoones; Ok with you to merge?

Good with me @policorn!

Merged! Thanks @jaztriumph!


Glyph quality?

fontbm vs notepad vs hiero.
Glyph rendered, not good as Hiero (freetype).
Please take a look,
Chars: Ẳ Ầ Ặ Ẫ Ấ Ắ

fontbm vs bmfont
Baseline still not correct (char: g): https://github.com/vladimirgamalyan/fontbm/issues/8

@0xDC00  can you share the arial.ttf and the command line used for generate the font (can't reproduce on my arial.ttf).

@vladimirgamalyan Hi,
arial.ttf: https://drive.google.com/file/d/17DUIDIneeQRCj_daqJEZjqZGz0Cyg0TI/view?usp=sharing
command: fontbm --font-size 48 --texture-width 512 --texture-height 384 --data-format txt --include-kerning-pairs --chars-file "chars.txt" --font-file arial.ttf --output arial
chars.txt: A Á Â Ấ Ắ Ễ Ỗ
Sorry for the late reply, please check.

I've got it, hiero (and also SFML) uses FT_LOAD_FORCE_AUTOHINT flag to force FreeType hinting module instead font's native hinter (which produces not so good result in our case).
I've added the same flag to last Release, it should fix the issue.

Look better now, thanks.


[Node.js] gRPC Map<string, string> Results in Empty Object

Please answer these questions before submitting your issue.
Should this be an issue in the gRPC issue tracker?
Yes
What version of gRPC and what language are you using?
"grpc": "^1.6.6",
What operating system (Linux, Windows, …) and version?
OSX, Sierra
What runtime / compiler are you using (e.g. python version or version of gcc)
gcc
Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx-include-dir=/usr/include/c++/4.2.1
Apple LLVM version 9.0.0 (clang-900.0.38)
Target: x86_64-apple-darwin16.7.0
What did you do?
Client reads a Msg protobuf type definition from server. No errors but Msg#map produces an empty {}, not an array of key:value pairs.
.proto
message Msg {
  int32 code = 1;
  string text = 2;
  map<string, string> data = 3;
}

Client code:
const map = new Map<string, string>();
if (addr.addr == undefined) return Utils.buildMsg(-1, "Addr.addr", map.set("", "An email address is required."));

Server code:
this._client.add(gRpcAddrMsg, (err: any, result: any) => {
          if (err) {
            console.log(err);
            reject(err);
            return;
          }
          else {
            console.log(result);
            resolve(this.addAddr_gRpc_To_Type(result));
          }
        });

private addAddr_gRpc_To_Type(gRpcMsg: any): AddressEntry|Msg {
    if (gRpcMsg.msg != undefined) {
      const msg: Msg = new Msg();
      msg.code = (gRpcMsg.msg.code != undefined) ? gRpcMsg.msg.code : undefined;
      msg.text = (gRpcMsg.msg.text != undefined) ? gRpcMsg.msg.text : undefined;
      msg.data = (gRpcMsg.msg.data != undefined) ? gRpcMsg.msg.data : undefined;
      return msg;
    }
    ...
}

What did you expect to see?
gRpcMsg.msg.data should be Map containing "", "An email address is required."
What did you see instead?
gRpcMsg.msg.data = {} This happens regardless how many key:value pair populate map.
Here is the JSON returned, reflecting the empty map
{
    "code": -100,
    "text": "Addr.addr",
    "data": {}
}

Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).
None
Anything else we should know about your project / environment?
None

Updated formatting.

This is a cryptic response. What do you mean by updated formatting?
On Fri, Nov 3, 2017 at 5:18 PM Nicolas Noble<EMAIL_ADDRESS>wrote:

Updated formatting.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/grpc/grpc/issues/13248#issuecomment-341829797, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABpcfJcDMZNjw5MZLhlolSaFAaONZV21ks5sy4M7gaJpZM4QQpgZ
.


Plasma server hangs on Get requests containing duplicate object IDs

If a plasma client issues a Get request containing duplicate object IDs, and a timeout of -1, the server will hang.
The logic at the end of PlasmaStore::ProcessGetRequest() only returns a response when the number of satisfied requests match the number of unique objects to wait for.  The former is calculated using the number of requested object IDs, not the number of unique requested object IDs.
To reproduce:

# start the plasma store first

from pyarrow import plasma
client = plasma.connect("/tmp/plasma")
oid = client.put("hello, world")
print(client.get([oid, oid], -1))print("done.")

Environment: tested on Linux/Python 3.8/pyarrow 4.0.1
Reporter: Bruce Martin
Note: This issue was originally created as ARROW-13152. Please see the migration documentation for further details.

Plasma has been deprecated (https://github.com/apache/arrow/issues/33077) in Arrow 10.0 and subsequently removed in Arrow 12.0 (https://github.com/apache/arrow/issues/33243). Given Plasma is no longer an existing component, closing this issue.
For reference, see this mailing list discussion around possible alternatives: https://lists.apache.org/thread/lk277x3b9gjol42sjg27bst2ggm5s0j2


Fails to parse IPv6 addresses in configuration

@dsheets reports that this error appears:
com.docker.slirp: [ERROR] failed to parse com.docker.driver.amd64-linux/slirp/dns: Failed to parse configuration: Ipaddr.Parse_error("invalid character ':' at 4", "2001:8b0:cb40:3495:3291:8fff:fe02:8cde")

We should use Ipaddr.of_string to parse IPv4 and v6 addresses. Probably the only annoying thing is the specification of the port. Perhaps we should use a separate line for that, rather than stick it on the end of the IP address? Some people use [addr]:port also there exist v6 zones like addr%iface. A newline might be the best terminator.
References:

https://tools.ietf.org/html/rfc5952#section-6

Seen in  https://github.com/docker/for-mac/issues/1337


Warnings due to missing keyword in Modelica.Mechanics.MultiBody.Joints.Spherical

Reported by h.m.bakker on 8 Dec 2011 15:41 UTC
OMC gives warnings when using a Spherical joint.
Apparently the 'each' keyword is missing in its definition. I attached the model which raises this warning.
The warnings are:
[C:/OpenModelica1.8.0/lib/omlibrary/Modelica 3.1/Mechanics/MultiBody/Joints.mo:1322:5-1325:115:writable] Warning: Variable spherical1.Q: Non-array modification 'if spherical1.enforceStates and spherical1.useQuaternions then StateSelect.prefer else StateSelect.never' for array component, possibly due to missing 'each'.

[C:/OpenModelica1.8.0/lib/omlibrary/Modelica 3.1/Mechanics/MultiBody/Joints.mo:1333:5-1335:57:writable] Warning: Variable spherical1.phi: Non-array modification 'if spherical1.enforceStates and not spherical1.useQuaternions then StateSelect.always else StateSelect.never' for array component, possibly due to missing 'each'.

[C:/OpenModelica1.8.0/lib/omlibrary/Modelica 3.1/Mechanics/MultiBody/Joints.mo:1336:5-1338:19:writable] Warning: Variable spherical1.phi_d: Non-array modification 'if spherical1.enforceStates and not spherical1.useQuaternions then StateSelect.always else StateSelect.never' for array component, possibly due to missing 'each'.

[C:/OpenModelica1.8.0/lib/omlibrary/Modelica 3.1/Mechanics/MultiBody/Joints.mo:1342:5-1346:99:writable] Warning: Variable spherical1.w_rel: Non-array modification 'if spherical1.enforceStates and spherical1.useQuaternions then StateSelect.always else StateSelect.never' for array component, possibly due to missing 'each'.

[C:/OpenModelica1.8.0/lib/omlibrary/Modelica 3.1/Mechanics/MultiBody/parts.mo:975:5-978:76:writable] Warning: Variable bodyshape1.r_0: Non-array modification 'if bodyshape1.enforceStates then StateSelect.always else StateSelect.avoid' for array component, possibly due to missing 'each'.

[C:/OpenModelica1.8.0/lib/omlibrary/Modelica 3.1/Mechanics/MultiBody/parts.mo:979:5-982:76:writable] Warning: Variable bodyshape1.v_0: Non-array modification 'if bodyshape1.enforceStates then StateSelect.always else StateSelect.avoid' for array component, possibly due to missing 'each'.

[C:/OpenModelica1.8.0/lib/omlibrary/Modelica 3.1/Mechanics/MultiBody/parts.mo:600:5-603:76:writable] Warning: Variable bodyshape1.body.r_0: Non-array modification 'if bodyshape1.body.enforceStates then StateSelect.always else StateSelect.avoid' for array component, possibly due to missing 'each'.

[C:/OpenModelica1.8.0/lib/omlibrary/Modelica 3.1/Mechanics/MultiBody/parts.mo:604:5-607:76:writable] Warning: Variable bodyshape1.body.v_0: Non-array modification 'if bodyshape1.body.enforceStates then StateSelect.always else StateSelect.avoid' for array component, possibly due to missing 'each'.

[C:/OpenModelica1.8.0/lib/omlibrary/Modelica 3.1/Mechanics/MultiBody/parts.mo:682:5-686:65:writable] Warning: Variable bodyshape1.body.w_a: Non-array modification 'if bodyshape1.body.enforceStates then if bodyshape1.body.useQuaternions then StateSelect.always else StateSelect.never else StateSelect.avoid' for array component, possibly due to missing 'each'.

[C:/OpenModelica1.8.0/lib/omlibrary/Modelica 3.1/Mechanics/MultiBody/parts.mo:697:5-700:119:writable] Warning: Variable bodyshape1.body.Q: Non-array modification 'if bodyshape1.body.enforceStates then if bodyshape1.body.useQuaternions then StateSelect.prefer else StateSelect.never else StateSelect.avoid' for array component, possibly due to missing 'each'.

[C:/OpenModelica1.8.0/lib/omlibrary/Modelica 3.1/Mechanics/MultiBody/parts.mo:708:5-711:69:writable] Warning: Variable bodyshape1.body.phi: Non-array modification 'if bodyshape1.body.enforceStates then if bodyshape1.body.useQuaternions then StateSelect.never else StateSelect.always else StateSelect.avoid' for array component, possibly due to missing 'each'.

[C:/OpenModelica1.8.0/lib/omlibrary/Modelica 3.1/Mechanics/MultiBody/parts.mo:712:5-714:42:writable] Warning: Variable bodyshape1.body.phi_d: Non-array modification 'if bodyshape1.body.enforceStates then if bodyshape1.body.useQuaternions then StateSelect.never else StateSelect.always else StateSelect.avoid' for array component, possibly due to missing 'each'.

Migrated-From: https://trac.modelica.org/Modelica/ticket/654

Comment by h.m.bakker on 8 Dec 2011 16:02 UTC
I just found out that other components of the MultiBody library have this error as well. For example, see the errors of the BodyShape part below.
Please change the title of this ticket accordingly (I cannot do it).
[C:/OpenModelica1.8.0/lib/omlibrary/Modelica
3.1/Mechanics/MultiBody/parts.mo:975:5-978:76:writable] Warning:
Variable bodyshape1.r_0: Non-array modification 'if
bodyshape1.enforceStates then StateSelect.always else StateSelect.avoid'
for array component, possibly due to missing 'each'.

[C:/OpenModelica1.8.0/lib/omlibrary/Modelica
3.1/Mechanics/MultiBody/parts.mo:979:5-982:76:writable] Warning:
Variable bodyshape1.v_0: Non-array modification 'if
bodyshape1.enforceStates then StateSelect.always else StateSelect.avoid'
for array component, possibly due to missing 'each'.

[C:/OpenModelica1.8.0/lib/omlibrary/Modelica
3.1/Mechanics/MultiBody/parts.mo:600:5-603:76:writable] Warning:
Variable bodyshape1.body.r_0: Non-array modification 'if
bodyshape1.body.enforceStates then StateSelect.always else
StateSelect.avoid' for array component, possibly due to missing 'each'.

[C:/OpenModelica1.8.0/lib/omlibrary/Modelica
3.1/Mechanics/MultiBody/parts.mo:604:5-607:76:writable] Warning:
Variable bodyshape1.body.v_0: Non-array modification 'if
bodyshape1.body.enforceStates then StateSelect.always else
StateSelect.avoid' for array component, possibly due to missing 'each'.

[C:/OpenModelica1.8.0/lib/omlibrary/Modelica
3.1/Mechanics/MultiBody/parts.mo:682:5-686:65:writable] Warning:
Variable bodyshape1.body.w_a: Non-array modification 'if
bodyshape1.body.enforceStates then if bodyshape1.body.useQuaternions
then StateSelect.always else StateSelect.never else StateSelect.avoid'
for array component, possibly due to missing 'each'.

[C:/OpenModelica1.8.0/lib/omlibrary/Modelica
3.1/Mechanics/MultiBody/parts.mo:697:5-700:119:writable] Warning:
Variable bodyshape1.body.Q: Non-array modification 'if
bodyshape1.body.enforceStates then if bodyshape1.body.useQuaternions
then StateSelect.prefer else StateSelect.never else StateSelect.avoid'
for array component, possibly due to missing 'each'.

[C:/OpenModelica1.8.0/lib/omlibrary/Modelica
3.1/Mechanics/MultiBody/parts.mo:708:5-711:69:writable] Warning:
Variable bodyshape1.body.phi: Non-array modification 'if
bodyshape1.body.enforceStates then if bodyshape1.body.useQuaternions
then StateSelect.never else StateSelect.always else StateSelect.avoid'
for array component, possibly due to missing 'each'.

[C:/OpenModelica1.8.0/lib/omlibrary/Modelica
3.1/Mechanics/MultiBody/parts.mo:712:5-714:42:writable] Warning:
Variable bodyshape1.body.phi_d: Non-array modification 'if
bodyshape1.body.enforceStates then if bodyshape1.body.useQuaternions
then StateSelect.never else StateSelect.always else StateSelect.avoid'
for array component, possibly due to missing 'each'.

Modified by dietmarw on 8 Dec 2011 16:25 UTC

Modified by dietmarw on 8 Dec 2011 16:26 UTC

Comment by dietmarw on 8 Dec 2011 16:30 UTC
This was already reported in #242 and was fixed for MSL3.2. The MSL3.1 which was used in this ticket is no longer maintained hence the fix will not be applied for it.