request-limit-increase action for account resource

Issue #971
Questions:

Should this work for all resources ('EC2', 'ELB', 'VPC', 'AutoScaling', 'RDS', 'EBS', 'SES', 'IAM')?  Only works for EBS right now
Should the severity level be configurable and if so what should the default be?  If not, what should it always be set to?  Choices are urgent, high, normal, and low
Should the code be volume-issue?  (Other choices are other, apis, feature-request, general-guidance)

ideally all resources, although could drop ses and iam i suspect wrt to auto limit increases.
re code, i think general-guidance, but i'll have to double check.
severity, config seems good, default to normal

@kapilt - When I use the service-limit filter I don't see ELB as a service in any of the checks.  I do see CloudFormation.  Are those the same thing?

@kapilt - good to go, pending the three questions I put into the code review

remove emails from test placebo json files

@kapilt - scrubbed.  Awaiting your response to code review.  Thanks

@kapilt - good to go

merge conflict needs resolving before merge.

@kapilt - resolved


feat: support using ARGOCD_AUTH_TOKEN in sync_argocd_apps.sh

Support using ARGOCD_AUTH_TOKEN to authenticate with argocd rather than using username/password
Also moved kubectl requirement closer to the call-site (as it isn't needed if either the password or token are set)

@thesuperzapper we're using this to check for successful deployments from GitHub Actions; do you think the approach seems reasonable?


Fixing linting errors

:tada: This PR is included in version 1.0.1 :tada:
Your semantic-release bot :package::rocket:


Unconfirmed User cannot re-send confirmation instruction

Describe the bug
Unconfirmed Users cannot re-send their confirmation instruction.
System is not recognising the email?
To Reproduce
Steps to reproduce the behavior:
0. Preliminaries: Registered User - not confirmed in the database

Go to https://railsdevs.com/users/confirmation/new
Type in an email from registered user with confirmed_at empty
Click "Resend confirmation instruction"
See error "Invalid E-mail or password."

Additional context
This error message also appears if you try to resend confirmation instructions to an already confirmed user

Thanks for reporting this! I'm not sure why it could be happening as I don't think we have any custom Devise configuration.
Either way, do you have the appetite to try and fix it?

Will check into this later. Documenting my finds here in the meantime:
It seems that something is interfering with the default devise logic, because:

if you put in an already confirmed email the error is still the same. Default devise error would be "email already confirmed"
if you put in a total random email the error is still the same. Default devise would be "email not found"

Somehow it creates a devise failure: not found in database.

See PR: #246

Closed via #246.


fix: remove unnecessary singlequote in tailwind classname

Closes #418
✅ Checklist

[X] I have followed every step in the contributing guide (updated 2022-08-15).
[X] The PR title follows the convention we established conventional-commit
[X] I performed a functional test on my final commit

Changelog
Remove unnecessary singlequote in tailwind classname.

Screenshots

before
after

💯

Can you also generate a changeset please


Doubling input size by two in decoder

Hi @spro,
I still don't get the point why you double the input size by two when initiating attention decoder, RNN layer, and output
self.attn = nn.Linear(self.hidden_size * 2, hidden_size)

self.gru = nn.GRU(hidden_size * 2, hidden_size, n_layers, dropout=dropout_p)

self.out = nn.Linear(hidden_size * 2, output_size)

Can you please elaborate more about this? Thank you!

Each of those layers operate on a concatenation of two hidden_size sized vectors - the attention layer uses hidden state and encoder output (in the concat case); the GRU uses the embedded word and the last attention context; the output layer uses the GRU output and current attention context. These all give the layers some extra information to calculate their outputs with.

Thanks for the clear explanation, now it's totally make sense!


Migration to Turbo Module API

Hi @Mitch528 !
Is there a plan to migrate this package to the new turbo modules API? I tried to migrate this package myself by forking it. But it turned out to rewrite only the Android part.
The IOS source code is written in Swift, but in the new React Native architecture, code generation of interfaces and native bindings is available only in Objective-C, and I have no idea how to link these two implementations.
If you have any ideas or plans about this, please share them with the community)

Hey is this project still active?


Using each in each to access the values of each of the top each

Hello!
I have two codes for each. In the second each, I want to access the values of the first each. But it doesn't. Returns undefined.
Thanks!

Hey !
Please, do a little search before asking a question. 😄

https://github.com/poppinss/edge/issues/32
https://github.com/poppinss/edge/issues/30

So sorry! Thanks for answering!! :)


Continue to make fastlane.ci startup modular

add in more environment vars

FASTLANE_CI_SKIP_RESTARTING_PENDING_WORK
FASTLANE_CI_SKIP_WORKER_LAUNCH
FASTLANE_CI_THREAD_DEBUG_MODE

I added this alias to my .bash_profile: alias cidebug='FASTLANE_CI_SKIP_RESTARTING_PENDING_WORK=1 FASTLANE_CI_SKIP_WORKER_LAUNCH=1 FASTLANE_CI_THREAD_DEBUG_MODE=1 be rackup -p 8080 --env development'


snapshots/devmapper: fix race windown causing IO hangup

The issue beblow happens several times beforing the root
cause found:

A fdisk -l process has being hung up for a long time;
A image layer snapshot device is visiable to dmsetup, which
should not happen because it should be deactivated after
Commit();

The backtrace of fdisk is always the same over time:
[<ffffffff810bbc6a>] io_schedule+0x2a/0x80
[<ffffffff81295a3f>] do_blockdev_direct_IO+0x1e9f/0x2f10
[<ffffffff81296aea>] __blockdev_direct_IO+0x3a/0x40
[<ffffffff81290e43>] blkdev_direct_IO+0x43/0x50
[<ffffffff811b8a14>] generic_file_read_iter+0x374/0x960
[<ffffffff81291ad5>] blkdev_read_iter+0x35/0x40
[<ffffffff8125229b>] new_sync_read+0xfb/0x240
[<ffffffff81252406>] __vfs_read+0x26/0x40
[<ffffffff81252b96>] vfs_read+0x96/0x130
[<ffffffff812540e5>] SyS_read+0x55/0xc0
[<ffffffff81003c04>] do_syscall_64+0x74/0x180

The root cause is, in Commit(), there's a race window between
SuspendDevice() and DeactivateDevice(), which may cause the
IOs of a process or command like fdisk on the "suspended" device
hang up forever. It has twofold:

The IOs suspends on the devices;
The device is in Suspended state, because it's deactivated with
deferred flag and without force flag;

So they cannot make progress.
One reproducer is:

enlarge the race window by putting sleep seconds there;
run while true; do sudo fdisk -l; sleep 0.5; done on one terminal;
and pull image on another terminal;

Fixes it by:

Resume the devices again after flushing IO by suspend;
Remove device without deferred flag;

Fix: #4234
Signed-off-by: Eric Ren<EMAIL_ADDRESS>

@mxpv @fuweid Hi, please take a look at this fix, thanks~

Codecov Report

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

@@           Coverage Diff           @@
##           master    #4235   +/-   ##
=======================================
  Coverage   38.34%   38.34%
=======================================
  Files          90       90
  Lines       12728    12728
=======================================
  Hits         4881     4881
  Misses       7181     7181
  Partials      666      666

Flag
Coverage Δ

#windows
38.34% <ø> (ø)

Continue to review full report at Codecov.

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


scylla_node: start: add replace_node parameter

To be used for replacing a node given its host_id
rather than its ip address.
Makes use of the newly added --replace-node-first-boot scylla option.
Signed-off-by: Benny Halevy<EMAIL_ADDRESS>

Ref https://github.com/scylladb/scylladb/pull/12316
This change does not directly depend on the option being added since no code currently
uses the new replace_node parameter, while the change is backward compatible with replace_address.
but we should wait with merging it until the scylla PR is finalized and merged.

https://github.com/scylladb/scylladb/pull/12316 is merged

scylladb/scylladb#12316 is merged

@bhalevy this have conflict with other change you did with the boot sequence logs

scylladb/scylladb#12316 is merged

@bhalevy this have conflict with other change you did with the boot sequence logs

rebasing...

@fruch branch was rebased


sign in and request bearer token for bespoke api - react

Core Library
@azure/msal-browser
Core Library Version
2.14
Wrapper Library
@azure/msal-react
Wrapper Library Version
1.0.0-beta.1
Description
Hi I am trying to sign in the user and retrieve an access token for my custom API. However, I end up in an endless redirect loop.
MSAL Configuration
import { Configuration, LogLevel } from "@azure/msal-browser";
export const msalConfig: Configuration = {
    auth: {
        clientId: "xxxxxxxxx",
        authority: "https://login.microsoftonline.com/xxxxxxxx"
    },
    cache: {
        cacheLocation: "sessionStorage", // This configures where your cache will be stored
        storeAuthStateInCookie: false, // Set this to "true" if you are having issues on IE11 or Edge
    },
    system: {
        loggerOptions: {
            loggerCallback: (level: LogLevel, message: string, containsPii: boolean) => {
                if (containsPii) {
                    return;
                }
                switch (level) {
                    case LogLevel.Error:
                        console.error(message);
                        return;
                    case LogLevel.Info:
                        console.info(message);
                        return;
                    case LogLevel.Verbose:
                        console.debug(message);
                        return;
                    case LogLevel.Warning:
                        console.warn(message);
                        return;
                }
            }
        }
    }
};
export const loginRequest = {
    scopes: ["api://xyz/acces_as_user"]
};

export const graphConfig = {
    graphMeEndpoint: "https://graph.microsoft.com/v1.0/me"
};

Relevant Code Snippets
`function App() {
  const { instance, inProgress } = useMsal();
  const isAuthneticated = useIsAuthenticated();

  instance.handleRedirectPromise().then(x => {
    if (!isAuthneticated && inProgress === InteractionStatus.None) {
      instance.loginRedirect(loginRequest).then(y => {
        if (!isAuthneticated && inProgress === InteractionStatus.None) {
          instance.acquireTokenRedirect({ scopes: ["api://.../acces_as_user"] }).then(y => {
            AjaxFetchAdapter.register().requestInterceptor = ((req: any) => {
              console.log(req);
              req.config.headers.Authorization = "Bearer " + y;
            }) as any;

            history.push('/home');
          });
        }
      })
    }
  });

  return (...`

Identity Provider
Azure AD / MSA
Source
External (Customer)

@lvasiliou A couple things to point out here:

We don't recommend calling handleRedirectPromise yourself when using msal-react as this is done under the hood by the library.
The loginRedirect and acquireTokenRedirect APIs are not expected to resolve as they will initiate a redirect away from the page. You should not hang a .then off of them.
We generally recommend using acquireTokenSilent instead of acquireTokenRedirect when you need to get a token for an API. acquireTokenRedirect should be used to resolve interaction_required errors if acquireTokenSilent fails.

I would recommend reading through our getting started doc and playing around with one of our react samples as they all demonstrate logging in a user then acquiring a token and calling an API. Let me know if you have additional questions after looking through those.

loginRedirect not resolving causes serious race conditions. I am in a situation where my code progresses before I am signed in and before I acquired an API token, resulting in an unauthorised exception. Or maybe I am doing something wrong. So short of re-engineering the entire app to fit in MSAL, I dont see it working otherwise.
`function App() {
const { instance, inProgress } = useMsal();
const isAuthenticated = useIsAuthenticated();
if (!isAuthenticated && inProgress == InteractionStatus.None) {
instance.loginRedirect(loginRequest);
}
if (isAuthenticated === true && inProgress == InteractionStatus.None) {
return (
<AppContext.Provider value={{ EntityManagerProvider: new EntityManagerProvider(instance) }}>`
`export class EntityManagerProvider {
protected masterManager: EntityManager;
constructor(instance: IPublicClientApplication) {
ModelLibraryBackingStoreAdapter.register();
UriBuilderJsonAdapter.register();

let activeAccount = instance.getActiveAccount();
let accounts = instance.getAllAccounts();
if (accounts.length > 0 || activeAccount !== null) {

  instance.acquireTokenSilent({ scopes: loginRequest.scopes, account: activeAccount || accounts[0] }).then(x => {
    AjaxFetchAdapter.register().requestInterceptor = ((req: any) => {
      req.config.headers.Authorization = "Bearer " + x.accessToken;
    }) as any;
  }).catch(e => {
    throw (e);
  });

  DataServiceWebApiAdapter.register();`

loginRedirect not resolving causes serious race conditions.

If you need to block code from running you can await loginRedirect. By its very nature, the page will redirect away from your app before the promise resolves. If you would like a more straightforward API you can use loginPopup instead which will not leave the page.

I am in a situation where my code progresses before I am signed in and before I acquired an API token, resulting in an unauthorised exception

Can you please clarify what code is running before you acquired a token? I would again suggest reading through our docs and looking through our samples as we provide components that will handle login for you and prevent components from being rendered before authentication is complete.

Give us an example of a scalable app in react strict with routing instead of function components. Also, nobody wants to have a screen with a sign in button. And considering how all borwsers block popups, that feels like an outdated scenario.

Give us an example of a scalable app in react strict with routing instead of function components.

All of our samples use React Strict and most demonstrate routing; for example react-router sample.
If you're specifically interested in class components over function components please see:

Documentation about using msal-react with class components
Sample page using class components with raw context
Sample page using class components with HOC

Also, nobody wants to have a screen with a sign in button.

Please see docs and samples about signing a user in on page load without buttons:

Documentation
Documentation specifically for class components
Sample page using function components
Sample page using class components with raw context
Sample page using class components with HOC

Closing, please open a new issue if you have specific questions or actionable feedback after reviewing the docs. Thanks!


TSPS-382 get commands working without having to pass in pipeline name

Description
This PR is related to https://github.com/DataBiosphere/terra-scientific-pipelines-service/pull/170
This PR does three things

update commands to only require pipeline name when necessary
update jobs list command to return the pipeline_name
change the help text for the logout command (we should talk about this!)

Jira Ticket
https://broadworkbench.atlassian.net/browse/TSPS-382

worth noting that both https://github.com/DataBiosphere/terra-scientific-pipelines-service/pull/166 and https://github.com/DataBiosphere/terra-scientific-pipelines-service/pull/170 will need to be merged for all of these changes to be tested/working

awesome. can you also make sure that the CLI documentation is updated?

updated! thanks for the reminder


Add progress bar

Adds progress bar options once https://github.com/patrick-kidger/diffrax/pull/357 is merged

Just thinking: should we check for the diffrax version until the diffrax.progress_meter is actually released?

@abocquet I'm closing this while waiting for the various fixes and integration in Diffrax. 😊 (or we can reopen and make it draft if you prefer)

Reopening as draft to show that this is still WIP. We're mostly waiting for the next release of diffrax to propagate the changes.


Fix es6 build on windows

There were two issues due to directory structure on windows.
Whoever thought that backslash is better than slash when defining a directory should never be consulted.

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/15542/merge
Test environment:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15542/merge/index.html
To test a playground add it to the URL, for example:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15542/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/15542/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/15542/merge
https://gui.babylonjs.com/?snapshot=refs/pull/15542/merge
https://nme.babylonjs.com/?snapshot=refs/pull/15542/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/15542/merge#BCU1XR#0

WebGL2 visualization test reporter:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15542/merge/testResults/webgl2playwright/index.html


Video on /conf needs Flash

@jospoortvliet is it possible to force the embed to use the HTML5 playback?

I don't have the beginnings of a clue. This is most likely a YouTube setting. Best I can do is re-encode the video to a more friendly format and put it as a link somewhere... Is that worth it?

It works fine here on my Chrome. Shows it as HTML5. I think it depends whether HTML5 has been checked at https://www.youtube.com/html5?hl=de and if Flash is available. – Forcing HTML5 seems not to be possible anylonger…

Ok, nevermind then.


Proposal of a new code structure

Continuing discussion from here: https://github.com/luruke/barba.js/issues/41
Here's an example of the code I'd like to be able to write: https://gist.github.com/nicooprat/ea184d51ba3c9ab131bf1d3400ef0ef0
Features

Having different transition for specific routes: ie "/" for the home, or "/posts/*" for all posts, or "/posts/a-specific-post" to overwrite previous one
Different transition between A and B page: going from home to a specific post could have a different transition than if I'm coming from the posts list.
Default transition if no route defined for the new path, or no transition defined for this route
Having a simpler and better control in route transition, according to click event, HTML, and resolving promises

Actually all of this is already kinda doable with getTransition, but that could become very messy with a complex website. I think it should be done by the library by default (and only leave to the developer the possibility to overwrite/hook it maybe). I'd prefer a "config over code" behavior here. I tried to achieve this kind of behavior with v1, but the library is not structured for it, so it's really difficult. Here's what I think would be better:
Structure

Developer can define routes as object
Each route needs a name (namespace)
Each route can have a path (regex-like) to be able to "guess" the next page namespace before having loaded it (ie /posts/*). Very useful to below out transitions...
Each route can have in and out methods which does a transition (or whatever actually): going "to" this route, or coming "from" it. These methods should receive as parameters:

the original click event
old and new containers html
the previous/next route name in order to create specific transitions according to the current navigation (ie, an "out" transition from Home to Blog, and a different one "out" if going from Home to Contact)
a promise which will be resolved manually in in and out methods, when transition ends (or whatever the developer needs)

Would also be interesting to see if it's possible to better integrate with GSAP (or other), in order to automatically "reverse" in -> out transitions by default (via timeline) for example.
Have a default "route", which has default transition with in and out methods too, same as above
Routes can have methods like before(un)Loaded, after(un)Loaded, and so on, to trigger code (like creating a slider when coming on a page), getting rid of "global" Barba's events listeners

So internally, Barba would do the following when a link is clicked (speaking of transitions, the rest of the library works fine), pretty similar to the fade transition in the docs does:

Fire the current route out transition (with parameters: next route & a promise to be resolved (getting rid of this.done()) and loads the new URL contents
When those 2 promises are resolved, fire the new route in transition (again with route & promise parameters)
Trigger according events in each step

Thank you @nicooprat .
Basically with your proposal, there will be no more separation between a View and a Transition, everything will be incapsulated in this new object Route.
Also you introduce this new concept of in and out, while, currently the transitions are designed as "one way".
I actually like the separations of concern between the Views and the Transition, it makes the Transition:

easily portable in new project
easily reausable for different view

Chaining the out transition and the in transition of two routes can work fine for simple transitions but it may sounds complicate for more advanced ones.
Even if the path it's optional, it assume a certain importance in the new structure, and it's something that can be hardly hardcoded in a CMS driven website.
Also the naming routes it may sounds a bit confusing for some users, since barba doesn't provide any real front-end routing, but keep all the routing duty to the server.

Routes can have methods like before(un)Loaded, after(un)Loaded, and so on, to trigger code (like creating a slider when coming on a page), getting rid of "global" Barba's events listeners

This is already possible with .onEnter, .onEnterCompleted, .onLeave, .onLeaveCompleted on the View, or you are thinking to something different?
In general I need some time to process and think about it, I'd also like some other opinion from someone else.

Basically with your proposal, there will be no more separation between a View and a Transition, everything will be incapsulated in this new object Route.

I agree that, in this case, reusing a transition would be difficult. In your experience, does it really happen often? I was thinking of a default in/out transition for all routes, and the possibility to specify for some.
We could either make routes extendable, or still have views/transitions appart, but it seemed simpler to me to merge these concepts.

Chaining the out transition and the in transition of two routes can work fine for simple transitions but it may sounds complicate for more advanced ones.

Could you elaborate on this? Do you mean that sometimes the two transitions merge, without having a "neutral" moment between them? In my proposal, the developer can resolve the promise whenever he/she needs, so there could be other effects even after the next route begins its own transition (are you following me? :D).

Even if the path it's optional, it assume a certain importance in the new structure, and it's something that can be hardly hardcoded in a CMS driven website.

Not really important, only a bonus I'd say. In my tests, I wanted a special transition when going to a specific page, and there's no "official" way to do that at the moment with Barba. We need to wait the new content to be loaded to get the new namespace from the API. So we've to either check the href from the clicked link (via a global var), or add something clearer like a data-attr to explicitly specify it. That's not really handy. This path property could help Barba guess the next route before having loaded it, at least for simple URLs (that's the case 90% of the time).

Also the naming routes it may sounds a bit confusing for some users, since barba doesn't provide any real front-end routing, but keep all the routing duty to the server.

Naming things are still the hardest :) I agree that the confusion that Barba is a "real" router could be made (well, it's not that far though, it's like a progressive router), but views are often referring to the native world... And one could also suppose you can have multiple views in a page. Speaking of this, that could be another feature request :)

This is already possible with .onEnter, .onEnterCompleted, .onLeave, .onLeaveCompleted on the View, or you are thinking to something different?

That's it, just wanted to note that it would be defined in route-level in my proposal.

In general I need some time to process and think about it, I'd also like some other opinion from someone else.

Wise words! Need more feedbacks :)

not sure if i'm adding much to the discussion... but i've found that i can use essentially a single transition function (a modified version of the fade transition in the docs), and then manage all the different page transitions in the css. this has the additional upside of leveraging css for performant animations, and complexity within animations without any additional js.
let CommonTransition = Barba.BaseTransition.extend({

  start: function() {
    Promise
      .all([this.newContainerLoading, this.pageExit()])
      .then(this.pageEnter.bind(this));
  },

  pageExit: function() {
    return $(this.oldContainer).addClass('is-exiting').delay(300).promise();
  },

  pageEnter: function() {
    this.done();
    $(this.newContainer).addClass('is-entering').delay(300).queue(function(){
      $(this).removeClass('is-entering').dequeue();
    });
  },
});

Barba.Pjax.getTransition = function() {
  return CommonTransition;
};

@nicooprat @luruke
Evening all...
I've managed to knock together some kinda of 'router' type thinger...
The route array:
export default [
	{
		path: '/',
		view: Home
	},
	{
		path: '/case-studies',
		view: CaseStudy,
		children: [
			{
				path: 'ted',
				view: CaseStudyTed
			},
			{
				path: 'helen',
				view: CaseStudyHelen,
				children: {
					path: ':id',
					view: Post
				}
			}
		]
	},
	{
		path: '/blog',
		view: Blog,
		children: {
			path: ':id',
			view: Post
		}
	},
	{
		path: '*',
		view: Fallback
	}
]

Example view/transition thing:
export const Home = {
	onEnter({ from, to, next }) {
		document.body.style.backgroundColor = '#5ea'
		next()
	},

	onLeave({ from, to, next }) {
		next()
	}
}

example here: sponjs.surge.sh
I've not tested the crap out of this yet, but it seems to be working pretty well
https://github.com/magicspon/spon/blob/master/src/js/core/Router.js
Keen to hear your thoughts...
(note, this is very much still in development!)
ta

@magicspon It's basically all I dreamt of! Very nice. Looks like for now it's written directly in your project though, do you plan to make it standalone? I'd like to give it a try :) I'm just about to work on a project to would need it actually!

@nicooprat
Evening...
Here is the router thinger without any of my framework crap in there.
https://github.com/magicspon/barba-router
clone the repo, npm install, npm start
Let me know how you get on?


Cleanup and reorder .gitignore

Group things better in categories, and remove a ton of VS junk.
Some of it might still be needed and could need to be re-added.
Needs testing from users and contributors who use IDEs, and especially people using Visual Studio as it seems to generate a ton of files. I loosely synced with https://github.com/github/gitignore/blob/main/VisualStudio.gitignore but removed some of the too C# and web-centric cruft... but some of it might still be part of the "normal" workflow of contributors using VS (especially when contributing to the Mono module).

Listing some patterns which were removed but still seem needed, I'll make a new PR to add them back once we've got several of them:
# Hint file for IntelliSense
cpp.hint

# Used in subfolders by the Android build output
build/

I pushed the above patterns as b0df742cbe (should be cherry-picked too).

Cherry-picked for 3.5.

Cherry-picked for 3.4.5.


Where are recent files displayed?

I've installed the extension but can't see anything in the UI.

Can't figure it out either!


Custom Ordinal Multi-Logloss

Dear Community, I want to have a custom loss function where the calculated multi_logloss is weighted with np.square(y_pred -  y_test) + 1.0. I checked the advaced example but couldn't succeed doing it. I would very much welcome if someone can help. Thank you in advance for your time and consideration.

Is there any possible way to handle regression of imbalanced data in LightGBM? As my regression labels are discrete, I would like to implement a custom loss function that acts as a weighted mean square error.

I think you are trying to solve the multi-class problem by regression.
If so, you should set the num_class=1.
As for the objective, it is something like:
def object(preds, train_data):
    labels = train_data.get_label()
    weights = np.take(class_weights, labels.astype(int))
    grad = (preds - labels)**2 * weights
    hess = np.ones(grad.shape)
    return grad.flatten('F'), hess.flatten('F')

And you may need to write a customed function to convert the regression prediction to class prediction by yourself.

@guolinke Hello, thank you very much for your response! I have tried this but the regression returns wrong values (too much different from when I use the default loss function). The dataset that I am currently employing is not that unbalanced so I guess there is a mistake at grad or hess calculation. Note: I have also tried to calculate class weights manually and feed them via np.take as you have done.
from sklearn.utils.class_weight import compute_sample_weight

def fobj(preds, train_data):
    labels = train_data.get_label().astype(int)
    weights = compute_sample_weight('balanced', labels.astype(int))
    grad = (preds - labels)**2
    grad = grad * weights
    return grad, weights

@guolinke Ok, I believe that I found out the problem. I have multiplied the "grad" by np.sign(preds-labels) after figuring out that grad also needs the direction (sign). Thank you very much again. Have a nice day.


Feature Gate: Update to burn revoked feature lamports

Problem
As we get ready to migrate built-in (native) programs to BPF, we'll likely start with the Feature Gate program, a program that does not currently exist at Feature111111.... In this repository is the proposed new Feature Gate program with one single instruction: RevokePendingActivation.
This instruction is designed to defund the feature account of its lamports and send them to some designated destination. In order to add additional protection against spam, it may make more sense to instead burn these lamports.
Solution
If so desired, update the program to do so!
cc @joncinque - we should have some discussion on this beforehand, but I wanted to set a reminder here.

Just a side note:
Feature state is size 9.
https://github.com/anza-xyz/agave/blob/6bade6fd88b3d3cd627fb7ad94afda7927e39e4d/sdk/program/src/feature.rs#L26-L29
With default rent, this is 953,520 lamports, or 0.00095352 SOL. It's probably not a huge deal to actually make our initial program burn these lamports, since revoking features should be fairly uncommon. We can always modify to support a destination address in the future.


InputTagHelper use the value from QueryString instead from Model

Describe the bug
When a QueryString use ModelBinding then  the InputTagHelper will not use the value from Model .
The issue caused by the ModelState , ModelBinding add a AttemptedValue to the ModelState
To Reproduce
//// url: GET   /testpage?A=666
//// controller
public IActionResult TestPage(int A)
{
    var m = new MyClass{ A = 11 };
    return View(m);
}

//// view
@model MyClass
<input asp-for="A" />

Expected behavior
input's value is 11  but the actual value is 666
To avoid this
AttemptedValue should only show after there's a Model Bind Error, so before use the AttemptedValue we should check the ModelState.IsValid
https://github.com/aspnet/AspNetCore/blob/799b91a324b531e1a91512ec3f77f783f61c3a82/src/Mvc/Mvc.ViewFeatures/src/DefaultHtmlGenerator.cs#L713-L723

This is expected behavior. The date in the model state wins.


Lecture 6 writeup

Would love a writeup for Lecture 6 on this repo's wiki. Thank you Prof @hwkchia for the excellent articles 🫡

Lecture #6 covers non-examinable material, so I highly encourage students to contribute one chapter...


Improve failure message for all/no rows

At the moment the message is not clear enough. Especially the part about the predicate: we just know that an undefined predicate has been applied. The failure message should contain a clear description of the predicate.
If the predicate is associated to a column or an expression then its name should also be visible

Beta available at https://ci.appveyor.com/project/Seddryck/nbi/build/1.16.0-beta.85.build.86


Adds release date to version list output

Ex.
$ dist/getenvoy_darwin_amd64/getenvoy versions
VERSION	RELEASE_DATE
1.18.3	2021-05-11
1.17.3	2021-05-11
1.16.4	2021-05-11
1.15.5	2021-05-11
1.14.7	2021-04-15

fixes #93

I rolled back the extra code as we don't need tabwriter. In this context, we are fixed width and envoy version width matches "VERSION" width. If we need to later polish, we can, but we can enjoy the higher coverage meanwhile!


Support Volta architecture

Hi, do you have any plan that AutoAWQ will support V100 GPU in the future? I can run Auto-GPTQ on V100, but GPTQ's performance is worse than AWQ.

I am open to PRs that add support. If someone could contribute, it would be awesome

I have a Dell C4140 server with 4x Tesla V100 SXM2 32GB NVLink GPUS and would love to see this setup supported in future!

Hi, this is maked? regards

No, this is not supported yet.

What about this? https://github.com/InternLM/lmdeploy/pull/2090


LoggerAdapter to print the conversation_id in log messages

The goal is to include the conversation_id in log messages.  This lets you search your log for log messages associated with a particular call, which is useful both after-the-fact and during-the-call (if you have 2+ calls happening concurrently).
In practice this seems to work for most messages, but not all.  Here's an example:
INFO:     ('<IP_ADDRESS>', 0) - "WebSocket /connect_call/hj4ZeYJPD9GXEa0tpeoVMg" [accepted]
DEBUG:myapp:Phone WS connection opened for chat hj4ZeYJPD9GXEa0tpeoVMg
DEBUG:myapp:Getting config for hj4ZeYJPD9GXEa0tpeoVMg
DEBUG:myapp:[hj4ZeYJPD9GXEa0tpeoVMg] Trying to attach WS to outbound call
DEBUG:myapp:[hj4ZeYJPD9GXEa0tpeoVMg] Attached WS to outbound call
INFO:     connection open
DEBUG:myapp:[hj4ZeYJPD9GXEa0tpeoVMg] Media WS: Received event 'start': {"event":"start","sequenceNumber":"1","start":{"accountSid":"<snip>","streamSid":"<snip>","callSid":"<snip>","tracks":["inbound"],"mediaFormat":{"encoding":"audio/x-mulaw","sampleRate":8000,"channels":1}},"streamSid":"<snip>"}
DEBUG:myapp:[hj4ZeYJPD9GXEa0tpeoVMg] Filling 2144 bytes of silence
----- PHONE_CALL_CONNECTED
DEBUG:myapp:[hj4ZeYJPD9GXEa0tpeoVMg] Synthesizing speech for message
DEBUG:myapp:[hj4ZeYJPD9GXEa0tpeoVMg] Got transcription:  Well., confidence: 0.6796875
DEBUG:myapp:[hj4ZeYJPD9GXEa0tpeoVMg] Interrupting event
DEBUG:myapp:[hj4ZeYJPD9GXEa0tpeoVMg] sending interrupt
DEBUG:myapp:[hj4ZeYJPD9GXEa0tpeoVMg] Human started speaking
DEBUG:myapp:Responding to transcription
DEBUG:myapp:[hj4ZeYJPD9GXEa0tpeoVMg] Sent chunk 0 with size 8000
DEBUG:myapp:[hj4ZeYJPD9GXEa0tpeoVMg] Interrupted, stopping text to speech after 1 chunks
DEBUG:myapp:[hj4ZeYJPD9GXEa0tpeoVMg] Message sent: -
DEBUG:myapp:[hj4ZeYJPD9GXEa0tpeoVMg] Interrupting event
DEBUG:myapp:[hj4ZeYJPD9GXEa0tpeoVMg] sending interrupt
DEBUG:myapp:[hj4ZeYJPD9GXEa0tpeoVMg] Human started speaking
DEBUG:myapp:[hj4ZeYJPD9GXEa0tpeoVMg] Got transcription:  How can I help you?, confidence: 0.9941406
DEBUG:myapp:Responding to transcription
DEBUG:myapp:[hj4ZeYJPD9GXEa0tpeoVMg] Synthesizing speech for message
DEBUG:myapp:[hj4ZeYJPD9GXEa0tpeoVMg] Synthesizing speech for message
DEBUG:myapp:[hj4ZeYJPD9GXEa0tpeoVMg] Sent chunk 0 with size 8000
DEBUG:myapp:[hj4ZeYJPD9GXEa0tpeoVMg] Sent chunk 1 with size 6420
DEBUG:myapp:[hj4ZeYJPD9GXEa0tpeoVMg] Message sent: Hello, this is Josh.

The ----- PHONE_CALL_CONNECTED message is from my own event handler, so don't worry about that.  Though it is interesting to think about passing the logger through to event handlers?
Aside from that, nearly all other messages now have the conversation_id prepended.  But one message does not:
DEBUG:myapp:Responding to transcription

Why?  Because of this setup in call.py:
        super().__init__(
            TwilioOutputDevice(),
            transcriber_factory.create_transcriber(transcriber_config, logger=logger),
            agent_factory.create_agent(agent_config, logger=logger),

Notice that the logger gets passed through to agent_factory before we get a chance to wrap it inside super().__init__.
I'm not sure what's the best way to handle that.

The one message that doesn't have the conversation id is fine. It also doesn't appear for me when I test this PR.
Looks good! We are looking to revamp logging sometime in the future, but this is great for now! Thanks!


privacy.resistFingerprinting.letterboxing, false | Bug?

Was messing around with the letterboxing pref and test sites (AmIUnique, Panopticlick). I noticed something strange.
With the user.js inserted into a stock firefox and privacy.resistFingerprinting.letterboxing, false (letterboxing disabled), the detected screen/window heights are reduced by 74 pixels.
Example (tested with AmIUnique & Panopticlick, tested 2 different screen resolutions w/ maximized windows):

Stock Firefox
Screen w/h is detected as 1920x1080, available w/h is detected as 1920x1040.
User.js inserted, privacy.resistFingerprinting.letterboxing, false
Screen w/h is detected as 1920x1006, available w/h is detected as 1920x966; both reduced by 74 pixels.

Is this a bug? With letterboxing disabled it should be the same as stock firefox, no? This is surely making people who disable letterboxing more fingerprintable than they need to be?

LB'ing only controls the inner window
to protect outer window, screen and available screen, you need RFP (which then reports those the same as the inner window)

Panopticlick is measuring screen, so LBing is immaterial

LB'ing only controls the inner window

Ok so if I disable letterboxing my inner window measurement should be the same as a stock firefox, right? It's not. The height is 74 pixels less.

to protect outer window, screen and available screen, you need RFP (which then reports those the same as the inner window)

RFP is not reporting these as the same when letterboxing is disabled. It's 74 pixels less than a stock firefox though.
Can you test this or help me understand better?

Oh... the outer window is being protected with RFP, but the inner window is exposed which is why it's giving weird numbers? Honestly I can't quite get my head around it at the moment.

What happens when you start brand new profile + ghacksuser.js? Are the results the same?

my inner window measurement should be the same as a stock firefox, right

WTF is a stock Firefox? There is no such thing. The inner window is always exactly what it is - no-one lies about it, because things need to rely on it to display properly (and there are too many ways to get measure it, and if you play with it you just break things). LBing adjusts the inner window to a different size, but the actual inner window measurements are exactly what they are

Ok so if I disable letterboxing ... The height is 74 pixels less.

 Are you maximized? Are you full-screen? Are you windowed? Is RFP on? The height of what is 74 pixels less .. than  the height of what?
I can't make any sense of what you're asking, because you're not giving precise instructions or enough detail. Just use TZP to see what affects what: it updates in real time


Display of Chinese variants

https://github.com/mikecao/umami/blob/5ecaf5587b6bb5968a4b0c53c110bf807dbe9fed/lib/lang.js#L133-L134
Maybe they should be displayed as zh-CN and zh-TW, or even better, zh-Hans and zh-Hant?

I prefer the short name display. It's uniform across languages.


mgmt: hawkbit: some cleanup

a little cleanup in the hawkBit shell and the hawkBit docs.

Forgot to add HAWKBIT_NOT_INITIALIZED and HAWKBIT_PROBE_IN_PROGRESS to the return values of hawkbit_probe()

Rebase to resolve conflicts


Enable C & C Partner Entries With Project

Create a way for users to enter in new community or campus partners when submitting a project.

Completed tested on #614 and #615


Error: add site dependencies: load resources: loading templates in summary.html:18: unclosed action

Hi, I've been using the theme Blonde for longer than a year now, and recently I started getting the error related to postcss-cli. Thus, I have just updated the theme and follow again all the instructions that you have now in the README.
Now I have a different error:
<EMAIL_ADDRESS>start
> concurrently npm:watch:*

[watch:*tw]
[watch:*tw] ><EMAIL_ADDRESS>watch:tw
[watch:*tw] > tailwindcss -i ./themes/Blonde/assets/css/main.css -o ./themes/Blonde/assets/css/style.css --watch
[watch:*tw]
[watch:*hugo]
[watch:*hugo] ><EMAIL_ADDRESS>watch:hugo
[watch:*hugo] > hugo server
[watch:*hugo]
[watch:*hugo] Error: add site dependencies: load resources: loading templates: "/home/teoten/Code/WebApps/Rwhitedwarf-blog/themes/Blonde/layouts/_default/summary.html:18:1": parse failed: template: _default/summary.html:18: unclosed action
[watch:*hugo] npm run watch:hugo exited with code 255
[watch:*tw]
[watch:*tw] Rebuilding...
[watch:*tw] Done in 3694ms.

Appears when running npm run start locally on hugo v 0.80.0. When run on my server on render.com with Hugo v0.104.1 the error is more complex and longer: if I run npm run start the process would run endlessly with no end and no rendering. If instead I executed hugo --gc --minify" it ends with Build failed` and the last part of the error is
Error: Error building site: failed to render pages: render of "taxonomy" failed: "/opt/render/project/src/themes/Blonde/layouts/_default/baseof.html:7:4": execute of template failed: template: _default/list.html:7:4: executing "_default/list.html" at <partial "head.html" .>: error calling partial: "/opt/render/project/src/layouts/partials/head.html:17:51": execute of template failed: template: partials/head.html:17:51: executing "partials/head.html" at <postCSS (dict "config" "./assets/css/postcss.config.js")>: error calling postCSS: no Resource provided in transformation

Any ideas what can I be doing wrong?

I have updated Hugo locally and now it gives me similar error than render when I run npm run build
one in 3198ms.
Start building sites …
hugo v0.104.2+extended linux/amd64 BuildDate=unknown
ERROR 2022/10/04 22:18:13 render of "page" failed: "/home/teoten/Code/WebApps/Rwhitedwarf-blog/themes/Blonde/layouts/_default/baseof.html:7:4": execute of template failed: template: _default/single.html:7:4: executing "_default/single.html" at <partial "head.html" .>: error calling partial: "/home/teoten/Code/WebApps/Rwhitedwarf-blog/layouts/partials/head.html:17:51": execute of template failed: template: partials/head.html:17:51: executing "partials/head.html" at <postCSS (dict "config" "./assets/css/postcss.config.js")>: error calling postCSS: no Resource provided in transformation
ERROR 2022/10/04 22:18:13 render of "page" failed: "/home/teoten/Code/WebApps/Rwhitedwarf-blog/themes/Blonde/layouts/_default/baseof.html:7:4": execute of template failed: template: _default/single.html:7:4: executing "_default/single.html" at <partial "head.html" .>: error calling partial: "/home/teoten/Code/WebApps/Rwhitedwarf-blog/layouts/partials/head.html:17:51": execute of template failed: template: partials/head.html:17:51: executing "partials/head.html" at <postCSS (dict "config" "./assets/css/postcss.config.js")>: error calling postCSS: no Resource provided in transformation
ERROR 2022/10/04 22:18:13 render of "page" failed: "/home/teoten/Code/WebApps/Rwhitedwarf-blog/themes/Blonde/layouts/_default/baseof.html:7:4": execute of template failed: template: post/single.html:7:4: executing "post/single.html" at <partial "head.html" .>: error calling partial: "/home/teoten/Code/WebApps/Rwhitedwarf-blog/layouts/partials/head.html:17:51": execute of template failed: template: partials/head.html:17:51: executing "partials/head.html" at <postCSS (dict "config" "./assets/css/postcss.config.js")>: error calling postCSS: no Resource provided in transformation
ERROR 2022/10/04 22:18:13 render of "page" failed: "/home/teoten/Code/WebApps/Rwhitedwarf-blog/themes/Blonde/layouts/_default/baseof.html:7:4": execute of template failed: template: post/single.html:7:4: executing "post/single.html" at <partial "head.html" .>: error calling partial: "/home/teoten/Code/WebApps/Rwhitedwarf-blog/layouts/partials/head.html:17:51": execute of template failed: template: partials/head.html:17:51: executing "partials/head.html" at <postCSS (dict "config" "./assets/css/postcss.config.js")>: error calling postCSS: no Resource provided in transformation
Error: Error building site: failed to render pages: render of "page" failed: "/home/teoten/Code/WebApps/Rwhitedwarf-blog/themes/Blonde/layouts/_default/baseof.html:7:4": execute of template failed: template: _default/single.html:7:4: executing "_default/single.html" at <partial "head.html" .>: error calling partial: "/home/teoten/Code/WebApps/Rwhitedwarf-blog/layouts/partials/head.html:17:51": execute of template failed: template: partials/head.html:17:51: executing "partials/head.html" at <postCSS (dict "config" "./assets/css/postcss.config.js")>: error calling postCSS: no Resource provided in transformation
Total in 216 ms

That is with your default config.toml file, my current config file can be found here https://github.com/RWhiteDwarf/blog with all other details of my build

Your layouts/partials/head.html should be this code.
{{ $styles := resources.Get "css/styles.css" | postCSS (dict "config" "./assets/css/postcss.config.js") }}

This code is a bit out of date.
Please replace it with the following code.
{{ $styles := resources.Get "css/style.css" | postCSS }}

I have tested and confirmed that it works.

It did not help. What is weird is that I cloned the latest commit of the overall website that was stable, when I tried to build from there it sent me a different error. I applied there the change you are suggesting here and also could not build.
Anyway thanks a lot for your support. I changed the theme for something more simple and less dependant on npm which is anyway what I need. I'm closing this issue.


How is the "oldest rule" calculated?

Under the tittle "Only one retention label at a time", when it is mentioned that "If there are multiple rules that assign an auto-apply label and content meets the conditions of multiple rules, the retention label for the oldest rule is assigned.", how exactly is the oldest rule calculated? Is it by the creation date? Or is it by the "last modified" date?
The document could be a bit clearer in that regard.
Thanks!

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

ID: 6c49609d-3a62-b9be-24bf-f8fa6948d390
Version Independent ID: df547c86-fbc7-4f87-e893-49d07b045373
Content: Learn about retention policies & labels to automatically retain or delete content - Microsoft 365 Compliance
Content Source: microsoft-365/compliance/retention.md
Service: o365-seccomp
GitHub Login: @cabailey
Microsoft Alias: cabailey

@henascim  "Oldest" is by creation date, not modified date.  I'll clarify this in the docs, thanks for your question!


Important 010_install_plugins.js concurrency problem

It happens more often than not that one or more plugins don't get installed after adding a platform.
010_install_plugins.js does not even show any warnings or errors, which is only part of the problem. As a developer you end up thinking that all is fine until you run the app and get surprised if/when some plugin-dependent feature is broken. This has also been keeping me from updating to the latest Ionic CLI because of unreliability.
Things seems to go haywire for some reasons known to the "cordova plugin add" command internally, but what you try to do in the hook in question is running "cordova plugin add" asynchronously in a forEach.  Such an execution makes the chances for something to go wrong pretty high.
Not sure how this hasn't been noticed yet since you introduced the new hooks.
Now, having spent some time with the issue, the problem goes away when resorting to a sync. execution of "cordova plugin add", for example:
var exec = require('child_process').execSync;
...
sys.puts( exec('cordova plugin add ' + plugin) );

Parallel operations are great/faster but you need to be aware what you may step on.
Environment:
OSX 10.10.2
nvm 0.7.0 / 0.23.3 with node 0.12.0, npm 2.5.1
cordova 4.2.0, ionic cli 1.3.10
I my case I have around 10 plugins specified in package.json.
Command used: ionic platform add ios
cc @jbavari

@zarko-tg I certainly agree.
Part of the problem is, most of our users now are still running on Node 0.10.33-36.
Right now I'm thinking to get the Node 0.12.0 users:
var exec = require('child_process').execSync || require('child_process').exec;
I'd love some help in thinking through how to handle the sync execution for our users of older versions of node.
However, if it's an older version node user, they will still run into the error where plugins step on each other. Any ideas?

I had already written a small piece of code and used it with older (and latest) Node versions. The execution of plugin adding was done via grunt-shell but it shouldn't matter, cause you'll be calling a system command. It'll give you serial execution and stop if any of the chained commands fail. It works across OSes.
Example:
cordova plugin add <path1> && cordova plugin add <path2> && cordova plugin add <path2> ...

Might be sufficient to execute that as a single command using child_process.exec
For reference I'll provide you with my grunt-shell task (Ignore any specifics):
      add_plugins : {
        command : function () {
          var
            plugin_map,
            commands_list = [],
            config        = grunt.config.get( 'plugins_config' );

          // parse plugins.json according to its own format and populate
          // a list of commands
          Object.keys( config.plugins ).forEach( function( plugin ) {
            var disabled_plugin;

            plugin_map = config.plugins[ plugin ];
            disabled_plugin = plugin_map.hasOwnProperty( 'disabled' )
              ? plugin_map.disabled
              : false;

            if ( ! disabled_plugin ) {
              if ( ! plugin_map.versionTag || plugin_map.versionTag.length === 0 ) {
                commands_list.push( node_util.format(
                  'cordova plugin add %s', plugin_map.url
                ));
              }
              else {
                commands_list.push( node_util.format(
                  'cordova plugin add %s#%s', plugin_map.url, plugin_map.versionTag
                ));
              }
            }
          });

          return commands_list.join( ' && ' );
        },
        options : {
          stdout      : true,
          failOnError : true,
          execOptions : { cwd : globalConfig.cordova_dir }
        }
      }

Here's what I came up with

@zarko-tg as an update, I'm thinking of removing these hooks since the cordova-cli will now track these via the config.xml file.
See this announcement.
What do you think? Have you been using the --save command yet?

I have a relatively neutral opinion on the matter. Personally I have my own json file for plugins, Ionic puts them in package.json and Cordova now wants to keep them in config.xml.
So, whatever works.

Now that hooks have been added back to the templates, this bug still occurs and most of build will eventually fail if there are plugins that are missing to the plugins/fooplatform.json files.

Did you try out the ionic hooks remove command?

@jbavari My problem is indeed solved by removing the hooks, but that doesn't mean that the concurrency problem doesn't exist for people wanting to use them.


feat: Use katana instead of the starknet-devnet in the kakarot/devnet image

Feature Request
Describe the Feature Request
Currently, the kakarot devnet image is using the starknet-devnet.
We'd like to use katana instead, and to make it multi-arch
Describe Preferred Solution
In the Dockerfile, install katana instead, and find a way to store state or run deployment script in the command.
Make it multi-arch

Aye, Aye Captian 🫡


State change not being published

Hey,
I've got a door lock that reports it's battery state. I'm finding that while the zwave2mqtt Web interface is showing an updated battery state (93%), the mqtt topic it reports on is still showing the retained message of 100%, so it appears this change isn't being pushed to mqtt.
Any recommendations on what I could try to fix this?
Thanks, love this programme!

Hi @brettyj . That's strange because every value change that goes to the ui is also forwarded to mqtt. Do you see any error on console log? Are you able to do a debug? Are you running the application using docker, pkg or full nodejs app?

Hey,
I've since restarted the pi so the log has been wiped, but I'll keep an eye out for when I notice the battery has changed. When you say do a debug, how do you want me to debug this? I'm happy to help how I can. I'm using this in docker.
Here's a screenshot showing the disparity:

Thanks

Hi brettyj, for the debug you should run the version here in github, than use npm run dev to start the frontend page and node --inpect bin/www to start the debug on the backend, than set some breakpoints for example in value change and in the websocket to check if the messages are forwarded correctly.
The screenshot you have sent here is so strange, what is the correct value? 100 or 92?

I've noticed at some point since my comment it's pushed the new battery level to MQTT. I'll keep an eye on it.
I don't know if it's an issue with the device or this component, but there's a string output by the device called "Log Record" which doesn't seem to update very often - every now and then it will, but I don't know what triggers it.

It is almost impossible that the value changes and the change is not triggered, I think it is mostly a problem with the device or maybe with the device configuration. Try to enable poll of that value and see if the change is triggered correctly.
Daniel

On 26 Jun 2019, at 20:22, Brett Jenkins<EMAIL_ADDRESS>wrote:
I've noticed at some point since my comment it's pushed the new battery level to MQTT. I'll keep an eye on it.
I don't know if it's an issue with the device or this component, but there's a string output by the device called "Log Record" which doesn't seem to update very often - every now and then it will, but I don't know what triggers it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Hey thanks for the reply - how would I go about enabling poll of the value?

You have two options:

Enable pool using Mqtt apis (check docs)
Add a value in gateway settings values table end check the enable poll flag (suggested)

Daniel

On 26 Jun 2019, at 20:43, Brett Jenkins<EMAIL_ADDRESS>wrote:
Hey thanks for the reply - how would I go about enabling poll of the value?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Polling battery devices wouldn’t work as expected.
In OZW 1.6 we do refresh the battery level when a device wakes up tho (via a config variable - see https://github.com/OpenZWave/open-zwave/wiki/CommandClass-Compatibility-Flags (refreshonwakeup)

@Fishwaldo  thanks for the answer. Do you know if openzwave shared is ready for OZW 1.6? I would like to switch to OZW 1.6 in docker container image of zwave2mqtt but I don't want to break everything :(

Sorry. Not sure. I know some work has been done on shared but don’t know how complete it is. Have you tested yet?

Actually I haven’t any device to test so nope :(

On 27 Jun 2019, at 09:06, Justin Hammond<EMAIL_ADDRESS>wrote:
Sorry. Not sure. I know some work has been done on shared but don’t know how complete it is. Have you tested yet?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@Fishwaldo Today I have made some tests (Not with OZW 1.6 but with openzwave shared latest version) and I have found some strange behaviour with valueid type list, seems now something is broken as the value is an integer and not the value string from values array. https://github.com/OpenZWave/node-openzwave-shared/issues/316

You have to take that up with @ekarak. Nothing changed on the OZW side with regards to ValueLists.

Just sent a PR to fix it
Daniel

On 28 Jun 2019, at 16:54, Justin Hammond<EMAIL_ADDRESS>wrote:
You have to take that up with @ekarak. Nothing changed on the OZW side with regards to ValueLists.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Hey,
Sorry to be a pain, but the issue has come back - can I turn on debug logging or something to give you info without debugging it (it wouldn't be easy to debug it as I'm guessing the door lock returns the battery level as and when).
Thanks

I think it is more likely a bug with the xml file configuration

On 8 Jul 2019, at 21:12, Brett Jenkins<EMAIL_ADDRESS>wrote:
Hey,
Sorry to be a pain, but the issue has come back - can I turn on debug logging or something to give you info without debugging it (it wouldn't be easy to debug it as I'm guessing the door lock returns the battery level as and when).
Thanks
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

How do I check that? What do I check for?

You find all config files here https://github.com/OpenZWave/open-zwave/tree/master/config
Daniel

On 8 Jul 2019, at 21:51, Brett Jenkins<EMAIL_ADDRESS>wrote:
How do I check that? What do I check for?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

I'm a bit confused, the battery is showing fine in zwave2mqtt, and people using the hass zwave integration have the battery working fine and it's also using openwave. The issue seems to be that zwave2mqtt isn't broadcasting the change to mqtt

@brettyj I have added the support for the event "value refreshed" that should be triggered for battery updates. Check if it works now (you need t o use the version from master

@robertsLando hey, I've built a new docker container from master, on boot the batteries are synced, I'll keep an eye on it, currently the battery hasn't changed since setting up the new docker container

Ok thanks let me know!
Daniel

On 10 Jul 2019, at 20:46, Brett Jenkins<EMAIL_ADDRESS>wrote:
@robertsLando hey, I've built a new docker container from master, on boot the batteries are synced, I'll keep an eye on it, currently the battery hasn't changed since setting up the new docker container
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I've switched on polling on that value and it seems to be working fine now - all changes are being reflected instantly in HASS - only issue is I can't understand the Polling Intensity - no matter what I set it to, it seems to poll the lock every second or so - how can I make it poll say once an hour or day? (don't want to destroy my battery life)

The poll intensity is bugged right now I don't know if it has been fixed with openzwave 1.6 should ask to @Fishwaldo . It should be 1* 2* 3* poll interval based on the intensity.
Anyway glad it has been fixed so I close this

I've think I've come across a rather urgent bug. I turned off polling, but unknown to me, it was still polling every second and has knocked 10% off my battery life in an hour, so I deleted the entry in the override list, and saved, and it will still polling every second. So I restarted the docker container, and it's STILL polling every second. I've had to stop the docker container because otherwise it will destroy my battery by the end of the day.
How do I solve this? This is pretty urgent as I've had to turn off zwave

Just an update, I deleted the xml files, and reset it up and now it's working, checking once an hour. Phew

Wil reopen this until news

@brettyj Which xml files did you delete? Did you have to re-add any devices to your network afterwards?
I'm having a similar issue where updates aren't being sent to mqtt.

zwcfg_xxx.xml and zwscene.xml - didn't have to re-add anything

@brettyj Can I close this now?


Update tools/generator to allow for multi-swagger packages

After a bunch of chatting with @johanste and @olydis, I've come to the conclusion that I must modify the generator I wrote to allow for multiple-swagger document packages.
Depending on what I find when I go to do this work, I may end up needing to modify the Autorest config files to enumerate which tags are applicable to the Azure-SDK-for-Go. Python handles this in a very similar way, and can be seen here: Azure OpenAPI Specs, compute Python config @8d9497

Finished this with #793


Crashing while interacting on Google Drive

Description
It happens a bit randomly, but mostly when moving around files or navigating too fast.
Steps To Reproduce
No response
Expected behavior
No crash
Files Version
Version: <IP_ADDRESS> OS Version: 10.0.19044.1826
Windows Version
Version	10.0.19044 Build 19044
Relevant Assets/Logs
debug_fulltrust.log
debug.log

Are you using Column view layout mode? Does it happen for other layouts?

I mostly use Column layout. Unsure if it happens in the other layouts. I'll try using another mode to make sure.

@simonMDschu is this still an issue in 2.3.11 (stable release)?

No it seems to be fixed! Amazing work :)


Array ray tracing function

It is highly desirable to have a function for doing bulk ray tracing. PyZDDE doesn't have such a function.

There is a separate repo where we are working on the array ray tracing, independent of PyZDDE at https://github.com/indranilsinharoy/zArrayTrace. We will integrate it with PyZDDE in the near future.

The array tracing functions have been implemented in the branch https://github.com/indranilsinharoy/PyZDDE/tree/arrayTraceUsingZclient. The code is currently undergoing more tests, and will soon be integrated into PyZDDE master.

The functions for array ray tracing has been merged to the master in https://github.com/indranilsinharoy/PyZDDE/pull/47


Redo how sum/avg/min/max in the charts

Lets think of a better way to do these. Especially for averages.

I think we should also add a count feature

I believe the current issue with how aggregation works is that the individual grouped output objects aren't always something that makes sense to aggregate. For example in one internal app, one object is technically a product type at a time at a location in a storage section with a transportation modality. With the additional fact that the base object can change between different statistics it becomes really unclear to both users and API developers what they are summing averaging etc. Even when these functions could be useful, they aren't used due to how unclear this is.
The solution that I'm considering is the ability to specify a grouping level to aggregate over. For example, you could average over weeks, look only at the max lead times per dc, or count the number of products at every store. This would greatly clarify what level we're at, without removing any functionality as users and API designers can just aggregate without specifying a group to get the current behavior

Per our discussion, we'll be moving this to 3.0. as part of a larger overhaul of these structures


Change the name of the generated pdf.sandbox.external for mozilla-central

This patch is blocking https://phabricator.services.mozilla.com/D148600.

@calixteman Given that the Phabricator patch was abandoned and the bug closed as WONTFIX, do we need to back this out to prevent breakage when the next PDF.js update happens?

Yep for now we can revert it.


Stop setting GOPROXY in Dockerfile

What this PR does / why we need it:
We're seeing failures in CI related to goproxy.io. There's no need to set this so simply don't.
Which issue this PR fixes(if applicable):
none.
Special notes for reviewers:
Discussed this on Slack here.
Release note:

NONE

Oh, interesting. I think our job is not testing the code from PRs :see_no_evil: From the last failure:
> [builder 6/6] RUN make build GOOS=linux GOARCH=amd64 GOPROXY=https://goproxy.io,direct/ VERSION=v0.0.99:
52.76 CGO_ENABLED=0 GOOS=linux GOARCH=amd64 GOPROXY=https://goproxy.io,direct/ go build \
52.76 	-trimpath \
52.76 	-ldflags "-w -s -X 'k8s.io/component-base/version.gitVersion=v0.0.99' -X 'k8s.io/cloud-provider-openstack/pkg/version.Version=v0.0.99'" \
52.76 	-o cinder-csi-plugin \
52.76 	cmd/cinder-csi-plugin/main.go
52.77 go: downloading github.com/container-storage-interface/spec v1.9.0
52.78 go: downloading github.com/kubernetes-csi/csi-lib-utils v0.13.0
54.52 pkg/csi/cinder/controllerserver.go:30:2<EMAIL_ADDRESS>reading<EMAIL_ADDRESS>502 Bad Gateway
54.52 	server response: error code: 502
54.52 make: *** [Makefile:75: cinder-csi-plugin] Error 1
------
Dockerfile:60
--------------------
  58 |     COPY cmd/ cmd/
  59 |     COPY pkg/ pkg/
  60 | >>> RUN make build GOOS=${TARGETOS} GOARCH=${TARGETARCH} GOPROXY=${GOPROXY} VERSION=${VERSION}
  61 |
  62 |
--------------------
ERROR: failed to solve: process "/bin/sh -c make build GOOS=${TARGETOS} GOARCH=${TARGETARCH} GOPROXY=${GOPROXY} VERSION=${VERSION}" did not complete successfully: exit code: 2
make: *** [Makefile:173: push-multiarch-image-openstack-cloud-controller-manager] Error 1

/test openstack-cloud-csi-manila-e2e-test

Okay, we're not correctly copying the cloned code into the devstack VM, as expected. With my DNM patch, we see:
 TASK [install-cpo-occm : Ensure CPO source folder] *****************************
fatal: [<IP_ADDRESS>]: FAILED! => {
    "changed": true,
    "cmd": "if [ ! -d $GOPATH/src/k8s.io/cloud-provider-openstack ]; then\n  echo \"$GOPATH/src/k8s.io/cloud-provider-openstack should exist but does not\"\n  env\n  exit 1\nfi\n",
    "delta": "0:00:00.003298",
    "end": "2024-12-05 19:06:51.114875",
    "rc": 1,
    "start": "2024-12-05 19:06:51.111577"
}

Now to figure out why :thinking:

/lgtm
/approve

/cherry-pick release-1.31

/cherry-pick releae-1.30

/cherry-pick release-1.30

/cherry-pick release-1.29


feat: Documenting alias expressions and id input when creating tokens

Description
NEED TO DOCUMENT RESTRICTED CHARACTERS

Documenting id input when creating a token
Adds Aliasing section under Expressions
Documents alias_preserve_format and alias_preserve_length filters

Testing required outside of automated testing?

[ ] Not Applicable

Screenshots (if appropriate):

[ ] Not Applicable

Rollback / Rollforward Procedure

[ ] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

:tada: This PR is included in version 1.55.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


save status dataframe

columns:

success / not success
error message if any
useful for #6 and general understanding of how well it worked

save one parquet file per tar, use that for incremental

done


fixed Api Call Cat 1

Please review this change. It is working for me so far

Raju,
Can you review this?  Thanks.


Invoking better-sqlite3 ES6 "import" causes issues when building the app with webpack

I restricted the issue to a minimum lines of code.
Sources available in github.com/dsportes/bsql3
Regards
My server app runs with node v20 and I try to use only ES6 modules (not CommonJS ones), supposing that becomes the future sandard.
So in my app.js module:
import Database from 'better-sqlite3'
// import { Database } from './loadreq.js'
const db = Database(p)
...

It works. Just run: "npm run start"
Then I tried to build it with webpack. "npn run build"
In webpack.config.mjs I have an "externals" config:
externals: {
  // 'better-sqlite3': 'commonjs better-sqlite3' // Cannot find module 'better-sqlite3'
  // without the line above: TypeError: Cannot read properties of undefined (reading 'indexOf')
}

Without "externals" configuration. When running "npm run test", I get:
Cannot read properties of undefined (reading 'indexOf')
After reading few topics I added the line 'better-sqlite3': 'commonjs better-sqlite3'
"npn run build" and then "npm run test", I get:
Cannot find module 'better-sqlite3'
which is normal, the better-sqlite3 module being excluded.
I have no solution for having an app packed with webpack using better-sqlite3 ES6.
So in my app.js module I change for using CommonJs invocation:
// import Database from 'better-sqlite3'
import { Database } from './loadreq.js'
const db = Database(p)
...
loadreq.js:
import { createRequire } from 'module'
const require = createRequire(import.meta.url)
export const Database = require('better-sqlite3')

Everything is OK.
Why using ES6 style causes troubles to Webpack and not CommonJs style ?
Any idea or workaround ?

now we can use
import { createRequire } from "module"; const nodeRequire = createRequire(import.meta.url); const config = {     client: "better-sqlite3",     connection: {       filename: path.join("./mysqlite.sqlite"),       options: {         nativeBinding: nodeRequire(           "better-sqlite3/build/Release/better_sqlite3.node",         ),       },     },     useNullAsDefault: true,   }; const db = knex(config);

It's old issue but maybe a solution will be useful to someone
const db = new SQLite('db_name.db', {
  nativeBinding: require('better-sqlite3/build/Release/better_sqlite3.node')
})


fix: arrow navigation refactoring

Preflight Checklist

[x] I have read the Contributing Guidelines for this project.
[x] I agree to follow the Code of Conduct that this project adheres to.
[x] I have searched the pull request tracker for a Pull Request (PR) that matches the one I want to submit, without success.

Issue
This PR Closes #
Pull request checklist
Please check if your PR fulfills the following requirements:

[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been reviewed and added / updated if needed (for bug fixes / features)

See Review Guidelines for more information what is checked during review process.
Changes
Changes in this pull request:

sbb-checkbox-group has arrow navigation logic;
so now there are three group components (five with the new sbb-tag-group and sbb-toggle) that share almost the same logic about arrow navigation; it has been extracted and refactored.

Browsers
I tested the build on the following browsers:

[ ] Firefox Desktop
[ ] Chrome Desktop
[ ] Edge Desktop
[ ] Safari Desktop
[ ] Chrome Mobile
[ ] Safari Mobile

Screen readers
I tested the build on the following browsers:

[ ] JAWS Firefox Desktop
[ ] JAWS Chrome Desktop
[ ] NVDA Firefox Desktop
[ ] NVDA Chrome Desktop
[ ] VoiceOver Safari Desktop
[ ] VoiceOver Chrome Desktop
[ ] VoiceOver Safari Mobile
[ ] Android Accessibility Suite Chrome Mobile

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

Does this introduce a breaking change?

[ ] Yes
[x] No

Other information

Codecov Report

Merging #1485 (5608d3b) into master (ab917b0) will decrease coverage by 0.81%.
The diff coverage is 62.56%.

:exclamation: Current head 5608d3b differs from pull request most recent head d719a38. Consider uploading reports for the commit d719a38 to get more accurate results

@@            Coverage Diff             @@
##           master    #1485      +/-   ##
==========================================
- Coverage   54.85%   54.03%   -0.82%
==========================================
  Files          49       71      +22
  Lines        1659     2983    +1324
  Branches      406      810     +404
==========================================
+ Hits          910     1612     +702
- Misses        671     1260     +589
- Partials       78      111      +33

Impacted Files
Coverage Δ

...mponents/sbb-accordion-item/sbb-accordion-item.tsx
0.00% <0.00%> (-37.21%)
:arrow_down:

src/components/sbb-clock/sbb-clock.tsx
0.00% <0.00%> (ø)

src/components/sbb-link/sbb-link.tsx
59.57% <ø> (-31.86%)
:arrow_down:

src/components/sbb-logo/sbb-logo.tsx
0.00% <ø> (ø)

src/components/sbb-menu-action/sbb-menu-action.tsx
65.21% <ø> (ø)

src/components/sbb-menu/sbb-menu.tsx
25.89% <ø> (ø)

...ents/sbb-pearl-chain-time/sbb-pearl-chain-time.tsx
92.30% <ø> (ø)

...in-vertical-item/sbb-pearl-chain-vertical-item.tsx
93.75% <ø> (ø)

...-pearl-chain-vertical/sbb-pearl-chain-vertical.tsx
100.00% <ø> (ø)

...ponents/sbb-pearl-chain/sbb-pearl-chain.helper.tsx
66.66% <ø> (+2.77%)
:arrow_up:

... and 55 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

@dauriamarco I refactored the code a bit, moving to a bit simpler implementation for components.
Would you like to resolve conversations, if it's ok for you?


Move clip to another date (New Years Eve feature)

Soooo I wish you a happy new year. :tada:
I just recorded a clip to after 0:00 with the celebration of the new year.
One Second Diary stored it for the 01.01. but mentally it belongs to the 31.12. for me because I didn't went to bed yet when I took it. :laughing:
So I thought that I could simply rename the file name of the clip. However, when I took the clip of today (01.01.) One Second Diary thought that there's already a video existing. So I guess there's still a reference in a SQLite database or so?
Anyway, I would just love to have a possibility to properly move a clip into another date.
Same things could happen when travelling across time zones or so.
Please ask in case I didn't explain it properly.

Soooo I wish you a happy new year. :tada:
I just recorded a clip to after 0:00 with the celebration of the new year.
One Second Diary stored it for the 01.01. but mentally it belongs to the 31.12. for me because I didn't went to bed yet when I took it. :laughing:
So I thought that I could simply rename the file name of the clip. However, when I took the clip of today (01.01.) One Second Diary thought that there's already a video existing. So I guess there's still a reference in a SQLite database or so?
Anyway, I would just love to have a possibility to properly move a clip into another date.
Same things could happen when travelling across time zones or so.
Please ask in case I didn't explain it properly.

Happy new year!!
The date is rendered on top of the video with ffmpeg, so it's not possible to edit it.
If you also have a video recorded with default camera app, you can wait for the upload feature to land and then add the video from gallery, replacing your current video.
If not, I think the best option is to remove the date with another video editing tool and then do the same process above.
In last case you could leave the date wrong for this one and just change the name of the file like you said 😁

I don't really care about the displayed date in the video but are there any issues since OneSecondDiary wanted to edit the video instead of recording a new one although I renamed the file.
Hence I guess there's something stored somewhere?
Will it interfere somehow?

I don't really care about the displayed date in the video but are there any issues since OneSecondDiary wanted to edit the video instead of recording a new one although I renamed the file.
Hence I guess there's something stored somewhere?
Will it interfere somehow?

No, you can record a new one for today normally, even if it shows edit. If you renamed the file and there's no "2023-01-01.mp4" in the folder, nothing will be deleted.

I'm not sure whether it's related but I can't create a movie any more although the directory is full of clips

I am closing this one since it was resolved, let's move this last issue discussion also to #55 and concentrate efforts there!


[BUG] Noise problems with ADS1115

:bug: Describe the bug
I'm not able to get correct measurings through ADS1115 if i install the pcb in practice conditions. If i power the pcb and the measuring terminals with my laboratory supply i can calibrate and measure correct values. I suppose that i have some problems with the common ground which i can't find.
Fore more info look here: https://forum.arduino.cc/t/ads1115-problems-while-measuring-battery-solar-panel-voltage/1177524
:bangbang: To Reproduce**
:interrobang: Expected behavior
:camera: Screenshots
Additional context
:white_check_mark: Tasks

This issue is obsolete as part of the code transition from Arduino MKR to Arduino Opta


Emdedded object in GROUP BY produces wrong query

Emdedded objects in group by produce wrong queries
Version: (e.g. 2.4.3-SNAPSHOT)
Module: (e.g. quill-sql)
Database: (e.g. postgresql)
  case class Inner(x: Int, y: Int) extends Embedded
  case class Data(inner: Inner)

  def test = {
    val q = quote {
      query[Data].groupBy(_.inner).map { case (key, _) => key }
    }
    dbContext.run(q)
  }

Expected behavior
SELECT x12.x, x12.y FROM Datas x12 GROUP BY x12.x, x12.y

Actual behavior
SELECT x12.x, x12.y FROM Datas x12 GROUP BY x12.inner

https://scastie.scala-lang.org/LXvjNQwOQMSWsRKhqMHrCA


Set shield usage to "held-in-one-hand" when edited from armor sheet

Shields don't function if they can't be held, and the armor UI has no affordances to change the usage.
The armor template defaults to "wornarmor": https://github.com/foundryvtt/pf2e/blob/e3889d815e906e3a840d6740111c9d9725fbb821/static/template.json#L724
An earlier migration fixed this for existing items, but does not address newly created items:
https://github.com/foundryvtt/pf2e/blob/e3889d815e906e3a840d6740111c9d9725fbb821/src/module/migration/migrations/718-carry-type.ts#L26

This should be set on item creation


Adding and deleting static pages

Can we have a GUI to add and delete static pages? The one you've used for slides and steps should be fine

Basic page add,edit and delete added.

Not a priority. But it would be nice if the next page after adding or deleting a static Pages was the Pages tab rather than Steps tab. Same with deleting a Slide


Spurious warnings when run from read-only filesystem due to old ply version

When the code is run from a read only filesystem (e.g. container) then it produces a couple of warnings to the logs, like these:
WARNING: Couldn't open 'parser.out'. [Errno 30] Read-only file system: '<path>/python3.12/site-packages/spdx_tools/spdx/parser/tagvalue/parser.out'
Generating LALR tables
WARNING: Couldn't create 'spdx_tools.spdx.parser.tagvalue.parsetab'. [Errno 30] Read-only file system: '<path>/python3.12/site-packages/spdx_tools/spdx/parser/tagvalue/parsetab.py'

After some investigation if those warnings are important it turns out they come from the ply dependency that is used to parse TAG-VALUE files. Some more digging into that code showed that it tries to create a cache of the parsing tables and has some rather contrived logic on where to store those between calls.
Some solution ideas to avoid the warnings:
The yacc code takes an outdir parameter that will be used instead of the contrived paths, see:
# yacc.py
def yacc(method='LALR', debug=yaccdebug, module=None, tabmodule=tab_module, start=None,
       check_recursion=True, optimize=False, write_tables=True, debugfile=debug_file,
       outputdir=None, debuglog=None, errorlog=None, picklefile=None):

it could be passed some temporary writable dir when instantiating the parser in:
# tagvalue_parser.py
def parse_from_file(file_name: str, encoding: str = "utf-8") -> Document:
    parser = Parser()

However, doing that would require the client calling functions to also pass that parameter along and so on, or use tempfile.mkdtemp() and hope that it uses a writable directory and so on. In any case it complicates things.
After some more digging into the upstream of ply https://github.com/dabeaz/ply it seems that the code is not released anymore on pypi since 2018, https://pypi.org/project/ply/3.11/ but instead it is recommended to copy the github code directly into a project that uses it! (not the best idea but see https://github.com/dabeaz/ply?tab=readme-ov-file#how-to-install-and-use )
It also seems that after the last pypi release the code that causes the above spurious warnings has been removed as the changelog https://github.com/dabeaz/ply/blob/master/CHANGES mentions here:
01/26/20  PLY no longer writes cached table files.  Honestly, the use of
          the cached files made more sense when I was developing PLY on
          my 200Mhz PC in 2001. It's not as much as an issue now. For small
          to medium sized grammars, PLY should be almost instantaneous.
          If you're working with a large grammar, you can arrange
          to pickle the associated grammar instance yourself if need be.
          The removal of table files eliminated a large number of optional
          arguments to yacc() concerning the names and packages of these files.

So in summary it seems best to update ply to its latest upstream version from Github as that has other fixes too and the previous code did quite some contrived logic to cater to very old and very slow machines.
TLDR: the ply code currently used in this library is very old and should be either updated or even replaced with some alternative LALR parser.

Oh and ply code also seems to cause this issue with not being thread-safe https://github.com/spdx/tools-python/issues/801 - I'm not 100% sure if updating the library will fix that but to me it seems it is related to how ply does store the parsing tables and tries to read them on next run again.


feat: update useScript (#203, #197)

This PR improves the useScript hook, inspired by:

Issue #203 suggesting adding shouldLoad and removeOnUnmount options
PR #197 adding in-memory caching

@KATT, @curtvict, I'd be happy to have your review :)
Notes:

It introduces breaking changes and should be added to the v3 branch
Adding unit tests will be very appreciated

Thanks for all @curtvict. This will be in the next release, probably the 2.8.0.


Swaggo ignores package alias

Swaggo ignores package alias, as I can see, it tries to generate from struct that in create package
// @Success     201     object views.JsonApiView[views.JsonApiNode[createView.JsonApiAttributes]]
2022/10/20 07:40:57 Generating $views.JsonApiView-views_JsonApiNode_create_JsonApiAttributes
2022/10/20 07:40:57 Generating $views.JsonApiNode-create_JsonApiAttributes

Try the latest master branch, please.

It looks good, thanks
import (
_ "ordering/internal/gateways/http/views/api/sets/v1/create" // Here is JsonApiAttributesV1
_ "ordering/pkg/views" // Here is generic
)
and in another the same but products instead of sets
import (
_ "ordering/internal/gateways/http/views/api/products/v1/create" // Here is JsonApiAttributesV1
_ "ordering/pkg/views" // Here is still generic
)
The result is
#/definitions/views.JsonApiView-views_JsonApiNode-ordering_internal_gateways_http_views_api_products_v1_create_JsonApiAttributesV1-any
#/definitions/views.JsonApiView-views_JsonApiNode-ordering_internal_gateways_http_views_api_sets_v1_create_JsonApiAttributesV1-any

UPD:
But if i have, smth like this in imports
"ordering/internal/gateways/http/presenters/api/products/v1/create"
_ "ordering/internal/gateways/http/views/api/products/v1/create" // here is JsonApiAttributesV1
It failes with message ParseComment error in file ordering\application\internal\gateways\http\controllers\api\products\v1\create.go :cannot find type definition: create.JsonApiAttributesV1

UPD: resolved by using _.JsonApiAttributesV1 instead of create.JsonApiAttributesV1

UPD: But if i have smth like this in imports
"ordering/internal/gateways/http/presenters/api/products/v1/create" _ "ordering/internal/gateways/http/views/api/products/v1/create" // here is JsonApiAttributesV1
It failes with message ParseComment error in file ordering\application\internal\gateways\http\controllers\api\products\v1\create.go :cannot find type definition: create.JsonApiAttributesV1

swag will search for package with the same name from the imports sequencely, so in this case, first imported package will be selected

i got this, maybe we need to search in every imported package and if in more than one will find the stucture, then throw the error, cause don't know how to resolve whitch one of them needs to choose


The image alternative text is not used when generating PDF with Apache FOP formatter

Actual Behavior
The image alternate text is not processed by the PDF transformation when generate the XSL-FO file. I've used the Apache FOP processor.
Conforming with Apache FOP documentation, images must have an alternate text fox:alt-text
extension attribute (in the fox namespace) on fo:external-graphic and fo:instream-foreign-object to
specify a short text describing the image.
See: https://xmlgraphics.apache.org/fop/2.2/accessibility.html
Possible Solution
Override the next template:
<xsl:template match="*" mode="placeImage">
Location: org.dita.pdf2/xsl/fo/topic.xsl
from org.dita.pdf2.fop plugin:
<!--
	Override the original XSLT template to make images accessible.

	Conforming with Apache FOP documentation, images must have an alternate text fox:alt-text
	extension attribute (in the fox namespace) on fo:external-graphic and fo:instream-foreign-object to
	specify a short text describing the image.

	See: https://xmlgraphics.apache.org/fop/2.2/accessibility.html
-->
<xsl:template match="*" mode="placeImage">
	<xsl:param name="imageAlign"/>
	<xsl:param name="href"/>
	<xsl:param name="height" as="xs:string?"/>
	<xsl:param name="width" as="xs:string?"/>

	<!--
		Call the default processing to get an fo:external-graphic.
	-->
	<xsl:variable name="external-graphic">
		<xsl:next-match>
			<xsl:with-param name="imageAlign" select="$imageAlign"/>
			<xsl:with-param name="href" select="$href"/>
			<xsl:with-param name="height" select="$height"/>
			<xsl:with-param name="width" select="$width"/>
		</xsl:next-match>
	</xsl:variable>

	<!--
		Add fox:alt-text attribute if alt attribute or element is present.
	-->
	<xsl:apply-templates select="$external-graphic" mode="fix-image-alt">
		<xsl:with-param name="ctx" select="." tunnel="yes"/>
	</xsl:apply-templates>
</xsl:template>

<!--
	Add 'fox:alt-text' attribute if image has an alternative text.
-->
<xsl:template match="fo:external-graphic" mode="fix-image-alt">
	<xsl:param name="ctx" tunnel="yes"/>
	<xsl:copy>
		<xsl:choose>
			<xsl:when test="$ctx/@alt">
				<xsl:attribute name="fox:alt-text"
					select="$ctx/@alt"/>
			</xsl:when>

			<xsl:when test="$ctx/alt">
				<xsl:attribute name="fox:alt-text"
					select="$ctx/alt"/>
			</xsl:when>
		</xsl:choose>

		<xsl:apply-templates select="node() | @*" mode="fix-image-alt"/>
	</xsl:copy>
</xsl:template>

<xsl:template match="node() | @*" mode="fix-image-alt">
	<xsl:copy>
		<xsl:apply-templates select="node() | @*" mode="fix-image-alt"/>
	</xsl:copy>
</xsl:template>

Steps to Reproduce
Add an image in a topic:
<image href="../../images/Iris_sanguinea.jpg" scale="50" alt="Alternate text"/>

DITA-OT version: 2.5.2
How did you run DITA-OT?
oXygen
Transformation type:
PDF

@radu-pisoi tested the changes on Windows, using the narrator embedded in Acrobat Reader (main menu "View->Read out loud" after enabling accessibility in the "fop.xconf".

Hi Radu,
When idea when this bug be fixed ?
Thanks.
Regards,
Thiro

Looks like @robander committed a fix for this in: https://github.com/dita-ot/dita-ot/pull/2964 so probably this issue could be closed.
That particular pull request is marked for DITA OT 3.1. @robander do you have a timeline for the release of DITA OT 3.1?
I tried to look in the wiki for meeting minutes from 2018 but they are not present there:
https://github.com/dita-ot/docs/wiki

@raducoravu 3.1 will be out in beginning of June.

👍

Hey, does this work now in DITA-OT 3.x? I tried today with String using DITA-OT 3.3,3 and it doesn't translate into alt text in the PDF output. I examined topic_fop.xsl and the following does show:
<xsl:template match="*|@alt" mode="graphicAlternateText">
<xsl:attribute name="fox:alt-text">
<xsl:apply-templates select="." mode="text-only"/>
</xsl:attribute>
</xsl:template>
I checked and the processor is running through it and the select statement is resolving correctly. But the output doesn't have the alt text. I'd expect alt text to be visible as popup text when I hover the mouse pointer or at least when the Acrobat screen reader reads the content, just as if I had entered the alt text manually in a PDF editor (e.g. MS Word). Neither. Nothing added to the PDF.


Publish on crates.io

It will make easier for others to reuse the library/tool, and will improve project visibility.

https://crates.io/crates/usbrelay-rs

Thank you!


Fix version

Thanks. I’ll release 1.7.1 soon at that moment I’ll fix it. :)

Hmmm it will be better to accept now.


<IP_ADDRESS> For Families is not blocking a porn site

Hi @Ahmad091K, the following docs may be helpful to make sure you've set up <IP_ADDRESS> for Families correctly. It also links out to a form where you can report a miscategorized domain, which may be what is happening here: https://developers.cloudflare.com/<IP_ADDRESS>/setup/#1111-for-families
I am going to close this ticket for the time being. Please feel free to open a new ticket if you have specific updates you'd like to proposed to the developer documentation. Thanks!


[USER ACTION] My First PR to Twindle - Open Source Project

This is my first Pull Request to Twindle - Open Source Project which gives us the developer a platform to learn & build an app together & contribute towards the open source project.

Congrats on first PR to Twindle. 😄

Created a new Resources.md file to get beginners started with the project by learning technologies like node.js, Javascript, git etc.
This file currently contains some Youtube links to get yourself started but you can also add some Blogpost here.

Following Readme and contribution file naming convention use all upper case for file name.
Not sure whether to use this file or wiki. We need to discuss pros and cons.

I think wiki is not a good idea.
Use
https://github.com/twindle-co/twindle/blob/main/docs/RESOURCES.md

I think wiki is not a good idea.
Use
https://github.com/twindle-co/twindle/blob/main/docs/RESOURCES.md

@proful could you elaborate? Is it because everyone can't pitch in?

Yes I don't know how others can push their changes.
Creating files is better imo

Yes @proful we cannot change the wiki page of twindle. We can only create pull request to the main repository.

I have made changes to this PR. Please review it @proful @johnjacobkenny @sarathkumar6

Yes
Update the resources.md under docs


New release

I was wondering when we could expect a new release. It has been a while and I am waiting for some of the fixes that were made since the last release.

v2.0.0-alpha2 is done


[Android] envConfigFiles not picking the right config file updating from 1.4.2 to 1.4.4

While everything was going fine, I updated react-native from 0.64.2 to 0.66.0 and react-native-config from 1.4.2 to 1.4.4. After making a build for production, I saw that react-native-config was actually using my staging config.
During some different builds on different variants and environments react-native-config was mixing them up on Android.
Here is what my envConfigFiles looks like (haven't been changed during the update):
project.ext.envConfigFiles = [
	requesterdebug: ".env.user",
	requesterreleasestaging: ".env.user.staging",
	requesterreleasedemo: ".env.user.staging",
	requesterrelease: ".env.user.production",
	interpreterdebug: ".env.interpreter",
	interpreterreleasestaging: ".env.interpreter.staging",
	interpreterreleasedemo: ".env.interpreter.staging",
	interpreterrelease: ".env.interpreter.production",
]

I highly suspect this commit to create the issue.
In the meantime I used the ENVFILE environment variable to fix the issue.

Solution
The solution for me was to remove everything from line 79.
Explanation
Did some more debugging in dotenv.gradle that might help:
The correct env fill be loaded initially at line 67.
The last part (from line 79) will load the env again which I don't understand why is it necessary?
With task.doFirst that part will run after the configuration phase, but since gradle 4.2.0 its not possible to override final constants.
Without task.doFirst the last part will run directly just like at line 67, so basically the whole section is redundant.
Here are some logs :
With task.doFirst:
> Task :app:generateDigitalhiveDebugBuildConfig
> Configure project :app
Reading env from: ....// <- line 67
...
> Configure project :react-native-firebase_app
> Configure project :react-native-firebase_crashlytics
...

> Task :app:generateDigitalhiveDebugBuildConfig // <- `task.doFirst`
variantConfigString: pierreDebug, need to match env: digitalhivedebug
variantConfigString: pierrestagingDebug, need to match env: digitalhivedebug
variantConfigString: digitalhiveDebug, need to match env: digitalhivedebug
Reading env from: ....
variantConfigString: pierreRelease, need to match env: digitalhivedebug
variantConfigString: pierrestagingRelease, need to match env: digitalhivedebug
variantConfigString: digitalhiveRelease, need to match env: digitalhivedebug

Now without task.doFirst:
> Configure project :app
Reading env from: ... // <- line 67
variantConfigString: pierreDebug, need to match env: pierredebug // <- beginning of the last section
Reading env from: ...
variantConfigString: pierreDebug, need to match env: pierrestagingdebug
variantConfigString: pierreDebug, need to match env: digitalhivedebug
variantConfigString: pierreDebug, need to match env: pierrerelease
variantConfigString: pierreDebug, need to match env: pierrestagingrelease
variantConfigString: pierreDebug, need to match env: digitalhiverelease
variantConfigString: pierrestagingDebug, need to match env: pierredebug
variantConfigString: pierrestagingDebug, need to match env: pierrestagingdebug
Reading env from: ...
variantConfigString: pierrestagingDebug, need to match env: digitalhivedebug
variantConfigString: pierrestagingDebug, need to match env: pierrerelease
variantConfigString: pierrestagingDebug, need to match env: pierrestagingrelease
variantConfigString: pierrestagingDebug, need to match env: digitalhiverelease
variantConfigString: digitalhiveDebug, need to match env: pierredebug
variantConfigString: digitalhiveDebug, need to match env: pierrestagingdebug
variantConfigString: digitalhiveDebug, need to match env: digitalhivedebug
Reading env from: ...
variantConfigString: digitalhiveDebug, need to match env: pierrerelease
variantConfigString: digitalhiveDebug, need to match env: pierrestagingrelease
variantConfigString: digitalhiveDebug, need to match env: digitalhiverelease
variantConfigString: pierreRelease, need to match env: pierredebug
variantConfigString: pierreRelease, need to match env: pierrestagingdebug
variantConfigString: pierreRelease, need to match env: digitalhivedebug
variantConfigString: pierreRelease, need to match env: pierrerelease
Reading env from: ...
variantConfigString: pierreRelease, need to match env: pierrestagingrelease
variantConfigString: pierreRelease, need to match env: digitalhiverelease
variantConfigString: pierrestagingRelease, need to match env: pierredebug
variantConfigString: pierrestagingRelease, need to match env: pierrestagingdebug
variantConfigString: pierrestagingRelease, need to match env: digitalhivedebug
variantConfigString: pierrestagingRelease, need to match env: pierrerelease
variantConfigString: pierrestagingRelease, need to match env: pierrestagingrelease
Reading env from: ...
variantConfigString: pierrestagingRelease, need to match env: digitalhiverelease
variantConfigString: digitalhiveRelease, need to match env: pierredebug
variantConfigString: digitalhiveRelease, need to match env: pierrestagingdebug
variantConfigString: digitalhiveRelease, need to match env: digitalhivedebug
variantConfigString: digitalhiveRelease, need to match env: pierrerelease
variantConfigString: digitalhiveRelease, need to match env: pierrestagingrelease
variantConfigString: digitalhiveRelease, need to match env: digitalhiverelease
Reading env from: ....

As you can see the current version is loading every .env file because its matching every flavor.

I am also encountering this bug.
The issue is that when using React Native < 0.65.0, the new Gradle code doesn't work correctly.
The first you build your appthe env variables are undefined when using the project.ext.envConfigFiles array in your 'android/app/build.gradle'.
In the meantime of fixing this for both React Native releases, I think the requirement of React Native 65 should be added on the release information?

@luancurti Working now, thanks everyone!


[RN Android] Origin field: Origin name is not translated into English

If in the Admin App the 'Origin' field is filled, the name of the source is not translated into English in Mobile App.
Radzima App is opened. Lang of the App is EN.
Steps:

Tap on the search field ->Enter the object (e.g. Pharmacy museum)
Open the object  ->Swipe down -> Check the Origin

Actual result:
Origin name is not translated into English
Expected result:
Origin name is translated into English
https://user-images.githubusercontent.com/94908845/151974611-ee95de16-3504-42a7-a2ce-1a0d4b016c60.mp4
<img src= ""alt=height="300"/>

Admin or backend side translation necessary
There is only 1 language available now