GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v5.6 to before v5.16.10",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=091876cc355d6739e393efa4b3d07f451a6a035c",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=5b0c9569135a37348c1267c81e8b0274b21a86ed"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "091876cc355d6739e393efa4b3d07f451a6a035c",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "5b0c9569135a37348c1267c81e8b0274b21a86ed",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "phy: ti: Fix missing sentinel for clk_div_table\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.16.10 by commit 5b0c9569135a37348c1267c81e8b0274b21a86ed, it was introduced in version v5.6 by commit 091876cc355d6739e393efa4b3d07f451a6a035c. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2022-1000525


Header lean.h not conforming C++

Description
The public import header lean.h appears to be intended as a C and C++ interop header (as evidenced by #ifdef __cplusplus directives). However, it is does not consist of conforming C++ code, since it uses C language features (namely flexible array members (formerly zero-sized array members)) that do not exist in C++. (Common toolchains support these constructions in both languages as vendor extensions.)
This might just be the result of some shortcuts. The definition of the types in question may well not be necessary for consuming C++ code. All the helper functions that access them are defined inline in the header and only take pointer parameters. This code could conceivably be refactored so that the header merely declares, but does not define the types and functions, and the type and function definitions would be isolated in a single C translation unit. This would make the header contain conforming C++. C code that wishes to take advantage of the definitions for inlining could perhaps include another, intemediate, C-only header.
Impact
This is a mild conformance and portability issue. Code that is strictly standard conforming is possibly easier to maintain, evolve, and port to new platforms than code that relies on vendor extensions.

Thanks for the report!

This is a mild conformance and portability issue. Code that is strictly standard conforming is possibly easier to maintain, evolve, and port to new platforms than code that relies on vendor extensions.

Is there a concrete porting effort, or other project, that is impeded by this? Or is this mostly a cosmetic and hypothetical issue?

I guess it's a matter of pride and standards :-) I.e. is there a goal to write portable code, etc. If you don't care, then no, it doesn't matter, but at the same time, it might be a nice thing to do as a matter of sustainability?
For practical matters, people might enjoy being able to compile their code with stricter conformance flags, as that allows their compilers to give them more information about their bugs. By requiring a looser conformance mode just to process your header, you're basically denying users the use of those tools. I think that's not a terrible argument; compiler warnings are a pretty useful tool.

Not just of pride and standards, but also resources and priorities. Is it worth more or less than, say, a bug fix or a better error message?
No doubt if we had unlimited resources, we'd happily make the code amazingly elegant. Until then I fear we have to focus on what actually improves our users' experience.

Yeah... I don't know how to quantify the trade-offs. E.g. I wouldn't know how to measure how interested users were in having stricter compiler warnings; I expect there's some silent acceptence of the status quo. On the other hand, it's also not a terribly large change, and you could maybe invite a PR from the community?

@tkoeppe Thanks for the detailed report. We are open to considering issues of portability when they impede such efforts but not before that.


Add more tests

I'm not really interested in unit tests, because I am extremely willing and likely to completely change up the implementation details of... everything. But, more integration tests would be good.

Well, all the old integration tests are irrelevant now that I've removed quickstart mode. So, gotta make new tests.


Change Module.cpp to use cast apply macro

Also add license to Expression
Closes #70

Both skip and copy would be useful in payload, but can we save that for a separate task?

Both skip and copy would be useful in payload, but can we save that for a separate task?

definitely


Added collection for lodgement form + fixes

Added a collection to display on the lodgement portal form selector.
SRA need a collection very soon. However, we can add to this collection over the next days.
The objective of this collection is to present industry with an  input control on the lodgement portal form to select when they are submitting reports and data to GSQ.
It needs to be something that meets the needs of both industry and GSQ.
The current ESDC https://vocabs.gsq.digital/vocabulary/earth-science-data-category is very granular.

:lodgement-form a skos:Collection ;
skos:definition "Earth science data categories for selection on lodgement form."@en ;
skos:member
:geochemistry,
:geochronology,
:geology,
:geophysics ;
skos:prefLabel "Lodgement form selection"@en .
Also fixed the skos:inScheme errors

Here is what was in the ModurlTech form:

@LukeHauck and @AdrianStead I'm looping you in here. Essentially the thinking here is that we want to make a collection of concepts for what to display in the lodgement portal so we can choose our level of granularity we want customers to tag their data at. David and I thought that 'get all concepts' made a very long select list and that a broader grouping would be better for the lodgement portal (still can tag

First read i don't think this captures the requirement.  Some reports are based on a dataset, but many (EPM ann) are a report that will have none or many datasets included.  The tying of reports to ESDC is wrong, it should be tying datasets to ESDC, yes?

Reopening this pull request

An alternative raised by Nick was to display concepts from the top two levels, i.e.:
This is a SPARQL query - so the vocabulary can remain as-is. No need for a collection.

I still don't know if i understand the point of this vocab.  Surely we need to tag the data objects as certain data types (seismic survey data, EM survey data, geochem data) at some point in lodgement so it can be picked up and inserted in geoprops.  To do this we need more than a top level geophysics tag.  If the ESDC tag (of lets say geophysics) is added to report, which object is the geophysics object?  And of the geophysics broader ESDC which of the narrower is used to tag the data object?
The only point i see in this at all is that once data objects are tagged correctly (This is EM data, this is soil geochem data as those datasets are lodged) the report displays a tag saying it has broader geochem and geophsy data.  Like the current QDEX keywords functions.  But this is a search function, not a lodgement function in this way.
Where am i missing this?


Fail to load file-based configs

wandb --version && python --version && uname

Weights and Biases version: 0.10.1
Python version: 3.7.7
Operating System: Ubuntu 16.04.5 LTS (Xenial Xerus)

Description
Fail to load file-based configs (either with config-defaults.yaml or using command line argument --configs special-configs.yaml. Configurations within yaml file are not loaded into wandb.config nor logged to run_folder/files/config.yaml.
What I Did
python test_yaml.py

python test_yaml.py --configs config-defaults.yaml

Within test_yaml.py:
import wandb
wandb.init()
wandb.join()

Hi @kaixin96 , can you please update wandb, and see if the issue persists?

Hi @tyomhak , the issue persists under wandb 0.10.2. Though I found explicitly specifying WANDB_CONFIG_PATHS works. But one new issue is that wandb does not support yaml files containing complex python tags.
Initially I thought the user-specified yaml config file would be directly merged into run_folder/files/config.yaml. However, it seems wandb also use json to serialize config object, which precludes using complex python tags. I don't quite get why the config dict need to be json-serialized, given that the final output file is also in yaml.
Can you help look into it ? Thank you.

@raubitsj can you please help here?

Same here. Since version 10, my config-defaults.yaml isn't being read.

Is there any updates on this issue?

Hey @kaixin96 apologies for not updating this ticket.  This was fixed in version 0.10.6 on Oct. 15th: https://github.com/wandb/client/blob/master/CHANGELOG.md#0106-october-15-2020

I'm having similar issues with version 0.10.14. The command:
python test_yaml.py --configs CONFIG_FILE.yaml
results in an empty wandb.config dict.

I'm having similar issues with version 0.10.14. The command:
python test_yaml.py --configs CONFIG_FILE.yaml
results in an empty wandb.config dict.

I haven't tested it again.
But first try putting the contents of that config file into config-defaults.yaml and rerun it without the --configs.
If that doesn't work, try version 0.10.6.

I haven't tested it again.
But first try putting the contents of that config file into config-defaults.yaml and rerun it without the --configs.
If that doesn't work, try version 0.10.6.

The default config file config-defaults.yaml works with version 0.10.15. However, the --configs argument appears to be broken (e.g. I cannot load another config file). I ended up using argparse and yaml myself to read the parameters of another config file.

The default config file config-defaults.yaml works with version 0.10.15. However, the --configs argument appears to be broken (e.g. I cannot load another config file). I ended up using argparse and yaml myself to read the parameters of another config file.


Locomotion issues

Stuck when going up ramp in uro://2036514f-3ecf-44bd-9d12-ff0dcbc98c07

Superseded by https://github.com/V-Sekai/V-Sekai.github.io/issues/216.


docs(prototypes): DLT-1740 left bar prototype

Dialpad's Left bar prototype
Obligatory GIF (super important!)

:hammer_and_wrench: Type Of Change
These types will not increment the version number, but will still deploy to documentation site on release:

[x] Documentation

:book: Jira Ticket
DLT-1740
:book: Description
Added Dialpad's leftbar prototype and layout for the future when we want to start adding the rest of the app prototypes.
:bulb: Context
We need a prototype of how the app should be build with dialtone components, following the correct semantics and fully accessible through screen readers and keyboard navigation.
:pencil: Checklist
For all PRs:

[x] I have ensured no private Dialpad links or info are in the code or pull request description (Dialtone is a public repo!).
[x] I have reviewed my changes.

For all Vue changes:

[ ] I have made my changes in Vue 2 and Vue 3. Note: you may sync your changes from Vue 2 to Vue 3 (or vice versa) using the ./scripts/dialtone-vue-sync.sh script. Read docs here: Dialtone Vue Sync Script
[x] I have validated components with a screen reader.
[x] I have validated components keyboard navigation.

:camera: Screenshots / GIFs

:link: Sources
https://www.figma.com/design/oTY56LgQha8ljb4c8w4GtO/Dialpad-App-Components?node-id=9240-7131&m=dev

Seems like DND or OOO, it is messing a transparency
Current:

Product:

Not sure if it is a behaviour that we should replicate, but maybe it is.
If you have unread msg in some collapsed section, that user conversation/channel or group chat will remain visible.

Maybe there is a slightly improvement for the structure, since it will hold all the Dialpad structure and not just the Leftbar.
Could we create a section folder, move in there Leftbar folder.
There is also a component that will be probably shared trough others sections like options_dropdown.vue, create a components folder at the same level of section
Will be sth like:
prototypes/
├─ dialpad/
│  ├─ sections/
│  │  ├─ leftbar/
│  │  ├─ another_section/
│  ├─ components/
│  │  ├─ options_dropdown.vue/

Not necessary to do it now, we can wait to see how it grows

looks good to me, at least visually! let's wait for Francis to check the semantics

Maybe there is a slightly improvement for the structure, since it will hold all the Dialpad structure and not just the Leftbar. Could we create a section folder, move in there Leftbar folder. There is also a component that will be probably shared trough others sections like options_dropdown.vue, create a components folder at the same level of section
Will be sth like:
prototypes/
├─ dialpad/
│  ├─ sections/
│  │  ├─ leftbar/
│  │  ├─ another_section/
│  ├─ components/
│  │  ├─ options_dropdown.vue/

Sounds like a good improvement, but I'd prefer to keep it as it is right now and mutate when needed in the future, maybe the requirements change, so let's not double the work now and later.

I have some concerns about the static data generated by faked, for now seems to work softly but is there a reason that we want to have some dynamic data in the prototype? I was thinking maybe having a separated folder to hold all this static data.

We want dynamic data on the prototype to check how it behaves on different cases, with long and short texts, we might also want some status with emojis or something like that in the future, all of that can be achieved with faker.
You mean to have a separate folder with some JSON files with this data? I feel like using faker in this way is more natural and automated, which is the advantage of doing the way you're thinking?

You mean to have a separate folder with some JSON files with this data? I feel like using faker in this way is more natural and automated, which is the advantage of doing the way you're thinking?

All static data should be separated from component logic, since it is not required to be there.
Based on that, there should be room for improvement.
For now it can be still working as this way, we just have to pay attention to scalability and to have a readable structure.


Invalid cpu_quota setting

I have noticed on several nodes that the chef_client_systemd_timer resource creates invalid unit files on Ubuntu nodes.  For example, here is the resource definition.

chef_client_systemd_timer 'node' do
accept_chef_license true
cpu_quota '10%'
delay_after_boot '1min'
interval '30min'
run_on_battery true
splay '5min'
end

This create a unit file as follows.

[Unit]
Description=Chef Infra Client periodic execution
After=network.target auditd.service
[Service]
Type=oneshot
ExecStart=/opt/chef/bin/chef-client --chef-license accept -c /etc/chef/client.rb
SuccessExitStatus=3
SuccessExitStatus=213
SuccessExitStatus=35
SuccessExitStatus=37
SuccessExitStatus=41
CPUQuota=10
[Install]
WantedBy=multi-user.target

Systemd does not accept "10" as a cpu_quota value, it must have a % sign appended.

This has been fixed.


Update load flight 2

Docstring from load_flight needed an update to be formatted correctly, so I took the opportunity to add an example and fix a minor secondary time index problem. Here's a screenshot of how the docs page looks after the change:

Codecov Report

Merging #187 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #187      +/-   ##
==========================================
- Coverage   93.23%   93.23%   -0.01%
==========================================
  Files          70       70
  Lines        7712     7711       -1
==========================================
- Hits         7190     7189       -1
  Misses        522      522

Impacted Files
Coverage Δ

featuretools/demo/flight.py
88.37% <ø> (-0.14%)
: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 6e0efa7...f202277. Read the comment docs.

looks good, merging


Failed to invoke procedure apoc.export.cypher.all:

 Issue by ayushKataria
Wednesday Apr 13, 2022 at 09:12 GMT
Originally opened as https://github.com/neo4j-contrib/neo4j-apoc-procedures/issues/2747

Getting below error when trying to run apoc.export.cypher.all:
Caused by: org.neo4j.internal.kernel.api.exceptions.EntityNotFoundException: Unable to load NODE with id 783244.
The node id changes every time we run it. If we restart neo4j and rerun this, it works fine but if after a few days start getting this error again.
Neo4j version: 4.2.8
apoc version: 4.0.1

 Comment by vga91
Wednesday Apr 13, 2022 at 13:24 GMT

@ayushKataria
I've never seen this error, but first of all I would try to change version of apoc.
In fact your version of neo4j and that of apoc are not compatible (although often almost everything works).
You should install a 4.2.x.x apoc (the latest is <IP_ADDRESS>).
See here https://neo4j.com/labs/apoc/4.4/installation/#neo4j-server

 Comment by ayushKataria
Thursday May 05, 2022 at 11:18 GMT

Sorry, a type from me. It is actually <IP_ADDRESS> version of apoc. Will upgrade to the <IP_ADDRESS> anyways and try.
Also, I had seen a community post with the same issue here. We also starting seeing this issue after we upgraded from 3.5 to 4.2 neo4j version.

 Comment by ayushKataria
Friday Jun 03, 2022 at 03:04 GMT

Even after changing to <IP_ADDRESS>, we are still seeing the same issue. Any idea what may have caused it?

 Comment by vga91
Monday Jun 06, 2022 at 13:18 GMT

@ayushKataria
I just tried some migration from 3.5 to 4.x, but everything works. Maybe it could depend on the dataset.
Can you try to execute a consistency check with your database?
Also, when the error Unable to load NODE with id NNNN is thrown,
are you able to execute a match (n) where id(n) = NNNN return n?

 Comment by ayushKataria
Tuesday Jun 07, 2022 at 03:53 GMT

@vga91 match (n) where id(n) = NNNN return n runs fine but obviously doesn't return any node. But any new node I create has a nodeId +1 of the unavailable one, most of the time. Not sure, if that means anything though.
I'll try the consistency check and share.

 Comment by ayushKataria
Wednesday Jun 29, 2022 at 15:46 GMT

@vga91 I ran the consistency check, it didn't produce a inconsistencies file but this was the console output from it.
WARNING: Max 1024 open files allowed, minimum of 40000 recommended. See the Neo4j manual.
neo4j 4.2.8
VM Name: OpenJDK 64-Bit Server VM
VM Vendor: Amazon.com Inc.
VM Version: 11.0.12+7-LTS
JIT compiler: HotSpot 64-Bit Tiered Compilers
VM Arguments: [-XX:+UseParallelGC, -Xmx23800m, -Dfile.encoding=UTF-8]
2022-06-29 15:34:09.807+0000 INFO  [o.n.k.i.s.f.RecordFormatSelector] Selected RecordFormat:PageAlignedV4_1[AF4.1.a] record format from store /mydata_ebs_1/neo4j-4.2-data/data/databases/neo4j
2022-06-29 15:34:09.808+0000 INFO  [o.n.k.i.s.f.RecordFormatSelector] Format not configured for store /mydata_ebs_1/neo4j-4.2-data/data/databases/neo4j. Selected format from the store files: RecordFormat:PageAlignedV4_1[AF4.1.a]
Index structure consistency check
....................  10%
....................  20%
....................  30%
....................  40%
....................  50%
....................  60%
....................  70%
....................  80%
....................  90%
.................... 100%
NodeBasedMemoryLimiter:
  pageCacheMemory:26.89GiB
  jvmMemory:20.66GiB
  machineMemory:62.03GiB
  perNodeMemory:11B
  nodeHighId:21479518
  occupiedMemory:47.56GiB
  ==> numberOfRanges:1
  ==> numberOfNodesPerRange:21479518
STARTED Initialize index sizes
COMPLETED Initialize index sizes, took 24ms
These are considered small node indexes (3):
  org.neo4j.internal.schema.IndexDescriptor@1
  org.neo4j.internal.schema.IndexDescriptor@2
  org.neo4j.internal.schema.IndexDescriptor@3
Consistency check

STARTED IndexChecker[entityType:NODE,indexesToCheck:0]

COMPLETED IndexChecker[entityType:NODE,indexesToCheck:0], took 501ms

STARTED NodeChecker[highId:21479518,indexesToCheck:3]
....................  10%
....................  20%
....................  30%
.
COMPLETED NodeChecker[highId:21479518,indexesToCheck:3], took 22s 219ms

STARTED RelationshipGroupChecker[highId:12736]

COMPLETED RelationshipGroupChecker[highId:12736], took 24ms

STARTED RelationshipChecker[highId:8965861,indexesToCheck:0]
...................  40%
.......
COMPLETED RelationshipChecker[highId:8965861,indexesToCheck:0], took 816ms

STARTED RelationshipChainChecker[highId:8965861]
.............  50%
............
RelationshipChainChecker[highId:8965861] FORWARD took 1s 800ms

RelationshipChainChecker moving over to backwards relationship chain checking
........  60%
..................
RelationshipChainChecker[highId:8965861] BACKWARD took 1s 760ms

COMPLETED RelationshipChainChecker[highId:8965861], took 3s 564ms
..  70%
....................  80%
....................  90%
.................... 100%

 Comment by vga91
Tuesday Jul 12, 2022 at 16:09 GMT

@ayushKataria Yes, everything looks good with the consistency-check.
Just to exclude some causes, does the problem occur with the apoc.export.json.all and the apoc.export.csv.all too?
Anyway, I have found an issue that looks similar. Along the lines of this, by copying the database following this guide, are you able to solve the problem?
If that doesn't work, could you share a dump of the database, or a part of it, with which i could replicate the bug?

 Comment by conker84
Thursday Aug 25, 2022 at 11:27 GMT

@ayushKataria ping

 Comment by ayushKataria
Saturday Aug 27, 2022 at 08:29 GMT

@vga91 It only occurred with apoc.export.cypher.all and not with apoc.export.json.all or apoc.export.csv.all.
Eventually, we ended up replicating the database in a fresh install of neo4j and haven't seen the issue since. We replicated using a successful run of apoc.export.cypher.all and running these cypher queries in the new install.
One more weird thing we saw was, that the database folder size was 151GB in the previous install, while in the new install it was only 2.5GB. Any idea why this might be happening?

@ayushKataria
I really don't know why there is such a big gap between the two databases. a little more space can be expected expected during migrations, but not so much, and personally I've never had this situation.
Anyway, after creation on the new database, did the problem reoccur?

@vga91 No, the issue hasn't reoccurred after the migration.

Ok great, I close the issue for now, as we aren't able to replicate it, and also it regards a version of neo4j out of support.
Feel free to reopen the issue if the problem reoccurs in new versions of neo4j (4.3+)


Minibug: When two definitions are adjacent, one cannot be displayed properly.

Fixed in 0.10.3

Wonderful !


Unable to create child nodes in a mind map if i move the tree

Preflight Checklist

[x] I agree to follow the Code of Conduct that this project adheres to.
[x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Describe the bug
When i use the mindmap container, it allows me to create topics and with the short cut alt + shift (on mac) + arrow lets me create sub topics.  This works fine and is nice.  The problem occurs when I try to move any of the topics or subtopics or parts of the tree.  After i do that, alt + shift (on mac) + arrow no longer creates sub topics but instead creates a leg to a new shape which isn't what i want as i'm trying to continue to build out the mind map.
To Reproduce
Steps to reproduce the behavior:

Go to 'Search Shapes'
Click on 'Mindmap'
Click on the Topic shape
Hold Down Alt + Shift and right to create a sub topic
Hold Down Alt + Shift and up to create another sub topic
Click on the root topic shape again and use the move tree feature to move the tree somewher
Try to create subtopics the way you did with 4 and 5

Expected behavior
Sub topics that you can continue to branch from are created
Screenshots
If applicable, add screenshots to help explain your problem.
https://user-images.githubusercontent.com/60367446/141659139-f4f03670-5beb-44d5-a847-67a93afdc1fb.mov
draw.io version (In the Help->About menu of the draw.io editor):
15.7.3
Desktop (please complete the following information):

OS: MAC
Browser chrome
Version 95.0.4638.69

Smartphone (please complete the following information):

N/A

Additional context

N/A

Reproduced on Win but with "middle" sub topic only.
As a workaround I'd suggest to make space between sub topics wider (as shown in the image) and it should work (at my place it is working this way)
Does it help?


Can you please add icons for Delphi files

Can you please add icons for Delphi files

*.pas
*.dfm
*.dpr

Thank you.

Icon URL?

Found only this reference
http://www.mortenbs.com/?q=delphi-xe2


Add a loadComponents function for easy component loading on NodeJS

This PR adds the loadComponents function mentionned in #972.
Usage:
var Prism = require('./components/prism-core.js');
var loadComponents = require('./components/index.js');
loadComponents(['c', 'javascript']);

@mAAdhaTTah Do you wish to do a quick review on this?

Maybe loadLanguages would be more appropriate as a name, since it can't load other components, like themes or plugins?
Also, we get slightly less code if we just call load within the if block, e.g.:
if (components.languages[language] && components.languages[language].require) {
	loadComponents(components.languages[language].require);
}

Yes ! Both valid points. I updated the PR.


[Redirect] Allow redirect response to have body

Motivation
Currently, we don’t consume the response body of redirect responses. Because of this requests, that receive a redirect response with response body, may hang indefinitely.
Changes

Consume redirect response body if less than 3kb
Cancel redirect response if larger than 3kb

Result
Redirect responses are consumed. Fixes #574

@swift-server-bot test this please!


"Edit Function Signature" does not use calling conventions from the cspec file

Describe the bug
To help the quality of decompilation, I created some function types so they can be used in structures containing function pointers.
My target CPU is MIPS based (R24K series I believe?) and uses a calling convention that is not available in mips*.cspec.
I added a new calling convention called "extended" in .cspec and this convention is working successfully across the entire program I'm analysing.
However, when I create a "function type", the calling convention list only contains some predetermined names that I found at Ghidra/Framework/SoftwareModeling/src/main/java/ghidra/program/model/data/GenericCallingConvention.java.
My expectation is that "Edit Function Signature" would include the calling conventions declared in a .cspec
To Reproduce

Add a new calling convention to a cspec with a different name, e.g. "extended".
Create a function type, for example "int function_t(int)".

You should notice that the "Calling Convention" list box doesn't contain "extended".
Expected behavior
The "Calling Convention" list box should include the additional convention described in .cspec.
Screenshots
Attachments
I attached my mips cspec.
mips32le.zip
Environment (please complete the following information):

OS: Windows 10 with latest feature pack / updates
Java Version: "11.0.2" 2019-01-15 LTS
Ghidra Version: 10.0.4
Ghidra Origin: In this github repository

Many thanks.

So it looks like they use the same/similar calling convention as MIPS 64-bit n32.  Do they ever use they ever use the standard MIPS 32-bit convention?  Any chance that its really 64-32n32?  Do any instructions fail to disassemble?  (I would take a look at the n32 cspec either way to see, there are some differences that look like minor bugs in your spec)

I just double checked and the CPU is a "MIPS32® 34Kf™", which according to the datasheet is a 32-bit core.

Do any instructions fail to disassemble?

Everything disassembles and decompiles fine with "MIPS n32 default".
In any case, the issue I have is not with the convention itself since that I described in my .cspec file works for my case. I don't know if mine differs in anyway with any other similar convention, I only implemented what I see in the binary. The system runs a custom OS (it's a single all-in-one executable) so it is possible that the convention is unusual.
Incomplete or otherwise, I would expect my "extended" convention to show up in the "Edit Function Signature" dialogue box. Am I misunderstanding this?

Currently, Ghidra only uses built-in conventions in these dialogues (annoyingly).  I have converted the enum GenericCallingConvention into a class locally that then adds any protoypes I created to that list.  It is in no way fit to release as I'm sure it doesn't follow the Ghidra ethos!  (But I'm sure you could do something similar.)

@Wall-AF Would you mind sharing your change?
Thanks.

This is my version: GenericCallingConvention.zip
It doesn't help with the issue https://github.com/NationalSecurityAgency/ghidra/issues/3273 though!!!

This is common complaint and recurring discussion.  While we hope to address this limitation in the near future, Function Definition data types are limited to fixed enumeration of Generic Calling Conventions.  On the other hand, Functions are able to refer to calling conventions specified by the associated compiler specification.
The suggested change is not portable and should not be considered a viable approach to solving the issue.
I would prefer to close this issue as a duplicate.

The suggested change is not portable and should not be considered a viable approach to solving the issue.

I agree.  But it works until we've a better solution.
NB: Anyone using it will need to export what they have before upgrading to a more permanent solution.

How can it handle use of data type archives and use of multiple program architectures/compiler-specs?

Its temporary, and just works for someone using a single architecture.

Duplicate of #3267


Error "Unable to set monitor Port field" when using receiver_creator with smartagent/elasticsearch

Hi,
I am trying to use the receiver_creator feature to create a receiver of type smartagent/elasticsearch but the agent is failing with the following error :
otelcol[32207]: 2022-11-14T16:53:43.174+0100        error        receivercreator@v0.63.0/observerhandler.go:154        failed to start receiver        {"kind": "receiver", "name": "receiver_creator/1", "pipeline": "metrics", "receiver": "smartagent/elasticsearch", "error": "failed to load template config: unable to set monitor Port field using Endpoint-derived value of 9200: no field Port of type uint16 detected"}

My configuration below :
    receiver_creator/1:
      watch_observers:
        - host_observer
      receivers:
        smartagent/elasticsearch:
          rule: 'type == "hostport" && port == 9200 && process_name matches "java"'
          config:
            type: elasticsearch
            port: "9200"
            host: <IP_ADDRESS>
            clusterHealthStatsMasterOnly: false
            disableEndpointDimensions: true
            enableEnhancedClusterHealthStats: true
            enableEnhancedNodeIndicesStats:
              - search
              - indexing
              - flush
              - fielddata
              - query_cache
              - request_cache
            extraMetrics:
              - elasticsearch.process.max_file_descriptors
              - elasticsearch.process.cpu.percent
              - elasticsearch.cluster.pending-tasks
              - elasticsearch.cluster.initializing-shards
              - elasticsearch.cluster.status
              - elasticsearch.cluster.task-max-wait-time
              - elasticsearch.jvm.gc.old-time
              - elasticsearch.jvm.gc.count
              - elasticsearch.jvm.mem.heap-used-percent
              - elasticsearch.jvm.mem.pools.old.used_in_bytes
              - elasticsearch.jvm.mem.pools.old.max_in_bytes
              - elasticsearch.jvm.mem.pools.young.used_in_bytes
              - elasticsearch.jvm.mem.pools.young.max_in_bytes
              - elasticsearch.jvm.gc.time
              - elasticsearch.jvm.gc.count
              - elasticsearch.indices.fielddata.evictions
              - elasticsearch.indices.query-cache.evictions
              - elasticsearch.indices.request-cache.evictions
              - elasticsearch.indices.flush.total-time
              - elasticsearch.indices.flush.total
              - elasticsearch.indices.indexing.index-time
              - elasticsearch.indices.indexing.index-total
              - elasticsearch.indices.search.fetch-time
              - elasticsearch.indices.search.fetch-total

If we look at the monitor definition in the smartagent (https://github.com/signalfx/signalfx-agent/blob/main/pkg/monitors/elasticsearch/stats/elasticsearch.go#L26), we can see that the Port is defined as a string as some others are defined as uint16 (like mongodb https://github.com/signalfx/signalfx-agent/blob/main/pkg/monitors/collectd/mongodb/mongodb.go#L35). Also if we look as the receiver code the Port is always converted as a uint16 (https://github.com/signalfx/splunk-otel-collector/blob/2fcbfb1f379d3a35f25cf9210f73e8afd135aac3/pkg/receiver/smartagent/config.go#L182).
I dont know if this is an otel collector bug or if the issue should be adressed on the smart agent side if we consider that every monitor Port value must be a uint16.
Can you have a look into this ?
Thanks.
Charles

I have exactly the same problem. Do you have some news about that ?
Thanks in advance.

Apologies for the delay and thank you for the report. This will be included in the 0.78.0 release.


curve not working

Hi:
I can't get a curved edge with this code, and I don't understand why. I always get a straight line.
If I create the graph with   s.graph.addNode() and s.graph.addEdge(9, the curved edge shows correctly.
Any hint or explanation?

`
`

I have already solved the issue, changing the creation of the graph to
var s = new sigma({graph: g,
renderer: {
container: 'container',
type: 'canvas'
}
});


KAFKA-6813: Remove deprecated APIs in KIP-182, Part III [WIP]

Remove TopologyBuilder, TopologyBuilderException, KStreamBuilder,

Completed the leftover work of https://issues.apache.org/jira/browse/KAFKA-5660, when we remove TopologyBuilderException.

Added MockStoreBuilder to replace MockStateStoreSupplier, remove all XXStoreSupplier except StateStoreSupplier as it is still referenced in the logical streams graph.

Minor: rename KStreamsFineGrainedAutoResetIntegrationTest.java to FineGrainedAutoResetIntegrationTest.java.

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@mjsax this PR is ready for reviews now (although it's large, most of the diffs are due to file deletion).

Please update PR title :)


laravel.EMERGENCY: Unable to create configured logger.

Cashier Version: 10 (latest)
Laravel Version: 6
PHP Version: 7.2.23
Database Driver & Version: MySQL

Description:
I recently installed Cashier 10 and ever since then I've been getting the following errors many many times in my laravel.log. I'm using the default 'stack' logging option. I didn't have this issue at all until I installed Cashier.
Here's my stack trace.
[2020-02-03 23:22:40] laravel.EMERGENCY: Unable to create configured logger. Using emergency logger. {"exception":"[object] (InvalidArgumentException(code: 0): Log [default] is not defined. at /Users/jessehorne/Source/binarycocoa/uppit/vendor/laravel/framework/src/Illuminate/Log/LogManager.php:192)
[stacktrace]
#0 /Users/jessehorne/Source/binarycocoa/uppit/vendor/laravel/framework/src/Illuminate/Log/LogManager.php(118): Illuminate\\Log\\LogManager->resolve('default')
#1 /Users/jessehorne/Source/binarycocoa/uppit/vendor/laravel/framework/src/Illuminate/Log/LogManager.php(98): Illuminate\\Log\\LogManager->get('default')
#2 /Users/jessehorne/Source/binarycocoa/uppit/vendor/laravel/framework/src/Illuminate/Log/LogManager.php(87): Illuminate\\Log\\LogManager->driver('default')
#3 /Users/jessehorne/Source/binarycocoa/uppit/vendor/laravel/cashier/src/CashierServiceProvider.php(64): Illuminate\\Log\\LogManager->channel('default')
#4 /Users/jessehorne/Source/binarycocoa/uppit/vendor/laravel/framework/src/Illuminate/Container/Container.php(799): Laravel\\Cashier\\CashierServiceProvider->Laravel\\Cashier\\{closure}(Object(Illuminate\\Foundation\\Application), Array)
#5 /Users/jessehorne/Source/binarycocoa/uppit/vendor/laravel/framework/src/Illuminate/Container/Container.php(681): Illuminate\\Container\\Container->build(Object(Closure))
#6 /Users/jessehorne/Source/binarycocoa/uppit/vendor/laravel/framework/src/Illuminate/Container/Container.php(629): Illuminate\\Container\\Container->resolve('Stripe\\\\Util\\\\Log...', Array)
#7 /Users/jessehorne/Source/binarycocoa/uppit/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(769): Illuminate\\Container\\Container->make('Stripe\\\\Util\\\\Log...', Array)
#8 /Users/jessehorne/Source/binarycocoa/uppit/vendor/laravel/cashier/src/CashierServiceProvider.php(77): Illuminate\\Foundation\\Application->make('Stripe\\\\Util\\\\Log...')
#9 /Users/jessehorne/Source/binarycocoa/uppit/vendor/laravel/cashier/src/CashierServiceProvider.php(19): Laravel\\Cashier\\CashierServiceProvider->registerLogger()
#10 [internal function]: Laravel\\Cashier\\CashierServiceProvider->boot()
#11 /Users/jessehorne/Source/binarycocoa/uppit/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(32): call_user_func_array(Array, Array)
#12 /Users/jessehorne/Source/binarycocoa/uppit/vendor/laravel/framework/src/Illuminate/Container/Util.php(36): Illuminate\\Container\\BoundMethod::Illuminate\\Container\\{closure}()
#13 /Users/jessehorne/Source/binarycocoa/uppit/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(90): Illuminate\\Container\\Util::unwrapIfClosure(Object(Closure))
#14 /Users/jessehorne/Source/binarycocoa/uppit/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(34): Illuminate\\Container\\BoundMethod::callBoundMethod(Object(Illuminate\\Foundation\\Application), Array, Object(Closure))
#15 /Users/jessehorne/Source/binarycocoa/uppit/vendor/laravel/framework/src/Illuminate/Container/Container.php(590): Illuminate\\Container\\BoundMethod::call(Object(Illuminate\\Foundation\\Application), Array, Array, NULL)
#16 /Users/jessehorne/Source/binarycocoa/uppit/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(829): Illuminate\\Container\\Container->call(Array)
#17 /Users/jessehorne/Source/binarycocoa/uppit/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(812): Illuminate\\Foundation\\Application->bootProvider(Object(Laravel\\Cashier\\CashierServiceProvider))
#18 [internal function]: Illuminate\\Foundation\\Application->Illuminate\\Foundation\\{closure}(Object(Laravel\\Cashier\\CashierServiceProvider), 16)
#19 /Users/jessehorne/Source/binarycocoa/uppit/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(813): array_walk(Array, Object(Closure))
#20 /Users/jessehorne/Source/binarycocoa/uppit/vendor/laravel/framework/src/Illuminate/Foundation/Bootstrap/BootProviders.php(17): Illuminate\\Foundation\\Application->boot()
#21 /Users/jessehorne/Source/binarycocoa/uppit/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(212): Illuminate\\Foundation\\Bootstrap\\BootProviders->bootstrap(Object(Illuminate\\Foundation\\Application))
#22 /Users/jessehorne/Source/binarycocoa/uppit/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(320): Illuminate\\Foundation\\Application->bootstrapWith(Array)
#23 /Users/jessehorne/Source/binarycocoa/uppit/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(129): Illuminate\\Foundation\\Console\\Kernel->bootstrap()
#24 /Users/jessehorne/Source/binarycocoa/uppit/artisan(37): Illuminate\\Foundation\\Console\\Kernel->handle(Object(Symfony\\Component\\Console\\Input\\ArgvInput), Object(Symfony\\Component\\Console\\Output\\ConsoleOutput))
#25 {main}
"}

Hey there,
Since this is the first report we got about this and v10 has been out for quite a while already I suspect something is wrong with your configuration defaults.
Can you first please try one of the support channels below? If you can actually identify this as a bug, feel free to report back and I'll gladly help you out and re-open this issue.

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

Thanks!

CASHIER_LOGGER=default was not added to the .env file.

@gRoberts84 you're correct. No idea why we placed "default" there. I'll update the docs.


add auto instrumentation support for @azure/openai node package

There are two OpenAI node packages:

The OpenAI package maintained by OpenAI: https://www.npmjs.com/package/openai
The Azure OpenAI package maintained by Azure: https://www.npmjs.com/package/@azure/openai

Both packages support calling azure, however our OpenAI auto-instrumentation only patches the openai package.
Add auto instrumentation for Azure OpenAI Package in parity with OpenAI Package

Not planned as Azure openAI client is largely getting deprecated


[Static website] - load SPA via another path (not root) failed (error 403)

Description
Hi all,
I deployed an SPA application (vue JS) via the construct Static Website. It works correctly except one detail.
If i share the url for my SPA to another user, for example : https://app.example.com, it's ok.
But, if i share antoher url, not the root, for example : https://app.example.com/parameters
i have an access denied error :

How to Reproduce
to reproduce, the default construct like this :
constructs:
    app:
        type: static-website
        path: _dist
        domain:
            - app.${self:custom.domain}
            - demo.${self:custom.domain}
        # ARN of an ACM certificate for the domain, registered in us-east-1
        certificate: ${cf(us-east-1):certificate-${opt:stage, 'dev'}.StarCertificate}
        redirectToMainDomain: false

Additional Information
this error could be avoid with 3 adjustments in the construct

update S3 assets bucket to allow host site
update cloudfront origin. Not S3 origin, but CustomOrigin (HttpOrigin) to S3 static's url
manage 403 error like 404 error

With this 3 updates, we could load directly another url (not root url)

I think it's a duplicate of #163
The issue is related to a recent update in the CDK that changed some permissions

Ah, maybe.
I don’t know the CDK background ;)

@piolet it's indeed exactly the same issue.

@moein-tropee same issue 2 options to fix it ;)


RSS not working well

Hello, having issues with RSS :
When fetching from rss client, I am getting almost only « client error 429 », barely can use rss feeds.
I am using my own private Nitter instance (from sekai-soft fork, "I only want a Nitter instance" method w/ brand new burner account).
I only have like 30 accounts followed, not even fetching that much (twice a day), use to work well on first fetch but then stop working as normal. I can wait hours between fetches and still have error, even after 12 hours.
Any idea on how to resolve it ? Thanks ! (Web access seems to be working well, no error)
PS : even with everything configured as expected in doc, it seems that it does not require psw key for RSS to work...
docker logs :
web    | 2024-08-19 13:04:49 - [accounts] Rate limited, retrying userScreenName request...
web    | 2024-08-19 13:04:49 - [accounts] Rate limited, retrying userScreenName request...
web    | error: ProtocolError, msg: Connection was closed before full request has been made, accountId: 182038099XXXXX, url: https://api.twitter.com/graphql/q94uRCEn65LZThakYcPT6g/TweetDetail?variables=%7B%22focalTweetId%22%3A%221497915933364563968%22%2C%22includeHasBirdwatchNotes%22%3Afalse%2C%22includePromotedContent%22%3Afalse%2C%22withBirdwatchNotes%22%3Afalse%2C%22withVoice%22%3Afalse%2C%22withV2Timeline%22%3Atrue%7D&features=%7B%22android_graphql_skip_api_media_color_palette%22%3Afalse%2C%22blue_business_profile_image_shape_enabled%22%3Afalse%2C%22creator_subscriptions_subscription_count_enabled%22%3Afalse%2C%22creator_subscriptions_tweet_preview_api_enabled%22%3Atrue%2C%22freedom_of_speech_not_reach_fetch_enabled%22%3Afalse%2C%22graphql_is_translatable_rweb_tweet_is_translatable_enabled%22%3Afalse%2C%22hidden_profile_likes_enabled%22%3Afalse%2C%22highlights_tweets_tab_ui_enabled%22%3Afalse%2C%22interactive_text_enabled%22%3Afalse%2C%22longform_notetweets_consumption_enabled%22%3Atrue%2C%22longform_notetweets_inline_media_enabled%22%3Afalse%2C%22longform_notetweets_richtext_consumption_enabled%22%3Atrue%2C%22longform_notetweets_rich_text_read_enabled%22%3Afalse%2C%22responsive_web_edit_tweet_api_enabled%22%3Afalse%2C%22responsive_web_enhance_cards_enabled%22%3Afalse%2C%22responsive_web_graphql_exclude_directive_enabled%22%3Atrue%2C%22responsive_web_graphql_skip_user_profile_image_extensions_enabled%22%3Afalse%2C%22responsive_web_graphql_timeline_navigation_enabled%22%3Afalse%2C%22responsive_web_media_download_video_enabled%22%3Afalse%2C%22responsive_web_text_conversations_enabled%22%3Afalse%2C%22responsive_web_twitter_article_tweet_consumption_enabled%22%3Afalse%2C%22responsive_web_twitter_blue_verified_badge_is_enabled%22%3Atrue%2C%22rweb_lists_timeline_redesign_enabled%22%3Atrue%2C%22spaces_2022_h2_clipping%22%3Atrue%2C%22spaces_2022_h2_spaces_communities%22%3Atrue%2C%22standardized_nudges_misinfo%22%3Afalse%2C%22subscriptions_verification_info_enabled%22%3Atrue%2C%22subscriptions_verification_info_reason_enabled%22%3Atrue%2C%22subscriptions_verification_info_verified_since_enabled%22%3Atrue%2C%22super_follow_badge_privacy_enabled%22%3Afalse%2C%22super_follow_exclusive_tweet_notifications_enabled%22%3Afalse%2C%22super_follow_tweet_api_enabled%22%3Afalse%2C%22super_follow_user_api_enabled%22%3Afalse%2C%22tweet_awards_web_tipping_enabled%22%3Afalse%2C%22tweet_with_visibility_results_prefer_gql_limited_actions_policy_enabled%22%3Afalse%2C%22tweetypie_unmention_optimization_enabled%22%3Afalse%2C%22unified_cards_ad_metadata_container_dynamic_card_content_query_enabled%22%3Afalse%2C%22verified_phone_label_enabled%22%3Afalse%2C%22vibe_api_enabled%22%3Afalse%2C%22view_counts_everywhere_api_enabled%22%3Afalse%7D
web    | 2024-08-19 13:18:10 - [accounts] Rate limited, retrying tweetDetail request...

It is odd that web access works well but RSS does not. Can you double check your RSS fetching frequency to make sure it's not fetching too fast?
The rss endpoint would return status code 200 but an empty response if a password is not provided. Can you make sure the INSTANCE_RSS_PASSWORD environment variable is set in the .env file and the value is not empty string?

I did exactly what was in guide but still no need for any psw for web access nor rss feed ! Is my .env file name correct ? I mean, is it only .env or for exemple CONFIG.env ?
RSS config has been tested (rssMinutes) to 100 but still doesn't work.
root@miniDeb:~/guide-nitter-self-hosting# ls -la
total 64
drwxr-xr-x 7 root root 4096 Aug 22 10:05 .
drwx------ 6 root root 4096 Aug  9 21:11 ..
-rw-r--r-- 1 root root  427 Aug  9 21:51 .env
drwxr-xr-x 8 root root 4096 Aug  4 15:58 .git
drwxr-xr-x 3 root root 4096 Aug  4 15:58 .github
-rw-r--r-- 1 root root   81 Aug  4 15:58 .gitignore
-rw-r--r-- 1 root root 1070 Aug  4 15:58 LICENSE
-rw-r--r-- 1 root root 4028 Aug  4 15:58 README.md
-rw-r--r-- 1 root root 2164 Aug  4 15:58 docker-compose.nitter-xposter.yml
-rw-r--r-- 1 root root  954 Aug  4 15:58 docker-compose.nitter.yml
-rw-r--r-- 1 root root 3573 Aug  4 15:58 docker-compose.yml
drwxr-xr-x 2 root root 4096 Aug  4 15:58 docs
drwxr-xr-x 2 root root 4096 Aug  4 15:58 miniflux-chilled-refresher
drwxr-xr-x 2 root root 4096 Aug 18 14:37 nitter-auth
-rw-r--r-- 1 root root 1932 Aug 22 10:01 nitter.conf
-rw-r--r-- 1 root root 1859 Aug  7 01:18 nitter.example.conf.OLD

nitter.conf :
rssMinutes = 10  # how long to cache rss queries
enableRSS = true  # set this to false to disable RSS feeds
tokenCount = 10

.env :
TWITTER_USERNAME=XXXXXXX
TWITTER_PASSWORD= XXXXXXX

INSTANCE_RSS_PASSWORD= XXXXXXX
INSTANCE_WEB_USERNAME=nitter
INSTANCE_WEB_PASSWORD= XXXXXXX

INSTANCE_TITLE=SushiNitter
INSTANCE_THEME=Twitter Dark
INSTANCE_INFINITE_SCROLL=1
INSTANCE_HOSTNAME=192.168.XX.XX:8080

Is there any other config I should do ?
Thanks !

Can you try removing the space in front of the TWITTER_PASSWORD, INSTANCE_RSS_PASSWORD and INSTANCE_WEB_PASSWORD values (unless your passwords do contain spaces, in which case there needs to be a new way to passing those passwords)

Looks like I did make a mistake in the docker-compose.yml file that made passwords not working. Can you pull this repo and try again?

Tried to recreate from zero.
Just modified .env with my data (untouched docker-compose.yml) get me a 502 bad gateway error after asking for my user name and password.

Looks like the credentials are still wrong for some reason.. Can you try using the newly added multiple account approach?

Cool, much better now, it is working. Thanks !
Where can I find nitter.conf that is needed for some custom config ?

If you are following this guide then you have to use environment variables for customization as per this table. The goal was to simplify deployment so if you want a particular config to be customizable, I can make that change. If you are feeling adventurous, you could also just mount your nitter.conf to /src/nitter.conf in the container, but you have to comment out this line and build your own image locally, e.g. point your docker compose stack to use a local nitter repo
This is exposing the 8081 port in your container to <IP_ADDRESS>:8080 to your host, so this is normal. If you want it only exposed on localhost, change <IP_ADDRESS> to <IP_ADDRESS>

Great, we are almost there !
One last question :
If I try to disable NGINX authentification with DISABLE_NGINX=1 then nitter will not launch.
Leaving blank these fields, or #commenting, will also not work. How can I run instance without needing any authentification ?
INSTANCE_RSS_PASSWORD=
INSTANCE_WEB_USERNAME=
INSTANCE_WEB_PASSWORD=

That's an oversight from me lol. You need to change this line to "<IP_ADDRESS>:8080:8080" so that the original nitter port 8080 (instead of nginx port 8081) is mapped to host 8080

Thank you very much ! with you advices I have now a working Nitter instance w/ authentication.
But still have issue fetching RSS feeds.. Can fetch feed one or two times and then get a Request failed: client error (409).
Do you know if there is a setting to enable more fetches or any flood protection on nginx ?

If you've disabled NGINX there shouldn't be any NGINX flood protection, so it's likely a nitter issue. Do you have error logs from nitter container that looks suspicious?

.env file :
DEBUG=1
INSTANCE_ENABLE_DEBUG=1

docker logs --follow XXXXXXX :

web    | 2024-11-03 12:11:39 - [accounts] Rate limited, retrying userScreenName request...
web    | 2024-11-03 12:11:39 - [accounts] Rate limited, retrying userTweets request...
web    | 2024-11-03 12:11:39 - [accounts] Rate limited, retrying userScreenName request...
web    | 2024-11-03 12:11:39 - [accounts] Rate limited, retrying userScreenName request...
web    | 2024-11-03 12:11:39 - [accounts] Rate limited, retrying userScreenName request...
web    | 2024-11-03 12:11:43 - [accounts] Rate limited, retrying userScreenName request...
web    | 2024-11-03 12:11:43 - [accounts] Rate limited, retrying userTweets request...
web    | 2024-11-03 12:11:43 - [accounts] Rate limited, retrying userScreenName request...
web    | 2024-11-03 12:11:43 - [accounts] Rate limited, retrying userScreenName request...
web    | 2024-11-03 12:11:43 - [accounts] Rate limited, retrying userScreenName request...

Is it useful or I need info from another log ?
RSS client gives me 429 client error... It works well when I add a new feed but then if I fetch it more than 2/3 times it will not work anymore.

I was using Miniflux and rss feeds kept failing until recently I figured that you cannot have Miniflux polling the nitter instance using more than one worker. In Miniflux's case, I had to set WORKER_POOL_SIZE=1 to ensure that no more than one request is sent to the nitter instance simultaneously, otherwise Miniflux will hit 429 constantly.

Tried to add WORKER_POOL_SIZE=1 to my .env file but same problem, unable to fetch anything.

Oh I meant if you use Miniflux as your RSS reader, add it to your Miniflux config.

Do you think there is a way to configure NGINX/nitter to accept more than one fetch at time ?
Can't install Miniflux so I think the best solution will come from server side.

No I think the limitation comes from Twitter that you can't perform two fetches at the same time, otherwise it would just rate limit.


Vulnerability issue in shelljs

There seems to be a vulnerability issue in this repo, regarding shelljs. Is it posible to update this?

My bad, didn't saw that it was already updated, will open issue at the place where it suppose to be updated.
https://github.com/kurttheviking/git-rev-sync-js/pull/66


You can see items that you hold in the tank

I'm gonna try to fix this so the tank only moves when you have an empty hand. That way its not OP and people can't use other items while in tank.


Export script order

Hi, just a quick question. When you say:
{
-  "export": "next build && next export",
+  "export": "next build && next export && next-image-export-optimizer"
}

Shouldn't the order actually be
{
-  "export": "next build && next export",
+  "export": "next build && next-image-export-optimizer && next export"
}

So that it first generates the images and then puts them into the appropriate folder? Or am I missing something? Thanks!

Hi @PeterKottas,
The order in the README is correct, as the command "next export" empties the build directory each time it runs. So only after the exported files are put into the build folder can we populate the exported image into this folder.

Gotcha! It was acting out cause it couldn't find the images path and I didn't notice the error. That's what was throwing me off. You're right, all is good, thanks!


Stage history log all output in http stage provider

We even log the http response header.

We need to ignore some internal output and avoid to print them in stage history.
We need to consider the CR size limit. (Seems CR has 1MB size limit). We need to truncate the stage history as needed.

Assign to @lirenjie95


router: 1.52.1 -> 1.54.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/apollographql/router/releases.
meta.description for router is: Configurable, high-performance routing runtime for Apollo Federation
meta.homepage for router is: https://www.apollographql.com/docs/router/
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.53.0 with grep in /nix/store/c7pzzgwyp4wia4g6310xh9idz0xi84lk-router-1.53.0
found 1.53.0 in filename of file in /nix/store/c7pzzgwyp4wia4g6310xh9idz0xi84lk-router-1.53.0

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

router

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/7edc3664d69d38d7436a0346971a6ca8517b869f#router

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

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

1 package built:

router

Maintainer pings
cc @bbigras for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/apollographql/router/releases.
meta.description for router is: Configurable, high-performance routing runtime for Apollo Federation
meta.homepage for router is: https://www.apollographql.com/docs/router/
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.54.0 with grep in /nix/store/5czmls0sfx5hzlq2xxz7zhvxdd29bd6d-router-1.54.0
found 1.54.0 in filename of file in /nix/store/5czmls0sfx5hzlq2xxz7zhvxdd29bd6d-router-1.54.0

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

router

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/ac4a4cb83ca6e63d3d0ea0cda64f8c3aa69b312f#router

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

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

1 package built:

router

Maintainer pings
cc @bbigras for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.


C++ face_mesh Check failed: poller OutputStreamPollerImpl is already destroyed.

i try to write a class based face_mesh project and i got problem in poller , i changed
ASSIGN_OR_RETURN(mediapipe::OutputStream Poller, graph.AddOutputStreamPoller(kOutputStream)); like this
mediapipe::OutputStream poller;
ASSIGN_OR_RETURN(poller, graph.AddOutputStreamPoller(kOutputStream));

and the compilation was successful. but failed in run program.
F20210426 16:27:55.749730  4087 output_stream_poller.h:38] Check failed: poller OutputStreamPollerImpl is already destroyed.
*** Check failure stack trace: ***
    @     0x55890ff22c0c  google::LogMessage::Fail()
    @     0x55890ff22b54  google::LogMessage::SendToLog()
    @     0x55890ff2248a  google::LogMessage::Flush()
    @     0x55890ff25442  google::LogMessageFatal::~LogMessageFatal()
    @     0x55890f51ce3d  mediapipe::OutputStreamPoller::Reset()
    @     0x55890f51a028  FaceMesh::FillGraph()
    @     0x55890f51b307  FaceMesh::InitSolution()
    @     0x55890f51b40b  FaceMesh::test_process()
    @     0x55890f51bbcc  main
    @     0x7f7d2376fbf7  __libc_start_main
    @     0x55890f51994a  _start
    @              (nil)  (unknown)

i try to reset the poller but it's didn't work , Is it necessary to define poller  like ASSIGN_OR_RETURN(mediapipe::OutputStream Poller, graph.AddOutputStreamPoller(kOutputStream));?
Happy for any hints & thanks a lot!

I have already solve the quetion, here is my speculate
Bazel compiles by relocating the program so that the internal file path is the workspace file path.
so you must to run the exe Under the workspace file path.


Is  obsolete?

In https://caniuse.com/#search=hgroup it is said that <hgroup> is an obsolete/deprecated HTML element, but hgroup is not listed in the "Obsolete features" section of the HTML Living Standard (https://html.spec.whatwg.org/multipage/obsolete.html) and it has its own section https://html.spec.whatwg.org/multipage/sections.html#the-hgroup-element.

Yeah, I see it's in the WHATWG spec but not the W3C one, see the note at https://developer.mozilla.org/en-US/docs/Web/HTML/Element/hgroup#Usage_notes
Agree that it should probably be removed from that list.

I do not want to disscuss the MDN note as I do not know the details, but I would say that W3C did not remove hgroup (like frames), rather hgroup was not included in HTML 5 W3C.
Anyway, regarding the discrepancies between the WHATWG living standard and the W3C recommendation, after the [Memorandum of Understanding Between W3C and WHATWG](https://www.w3.org/2019/04/WHATWG-W3C-MOU.html), announced in May, the W3C spec is becoming irrelevant, isn't it?
Of course, everything related with outline is not important nowadays. Keeping information updated is very difficult and I am sure there are a lot of things more important to do. I just wanted to made you aware of this detail.

Available at https://caniuse.com/#feat=mdn-html_elements_hgroup


Create conda package

#67

Requested via https://github.com/conda-forge/staged-recipes/pull/20460 (failing at the moment).

Implemented


404 at /docker-for-windows/wsl/%20for%20details

I found a broken link : https://docs.docker.com/docker-for-windows/wsl/ for details

@Siraphob1995 Thanks for reporting the broken link. Could you let me know how you arrived at this link?

Thanks for reporting; the correct URL is now https://docs.docker.com/desktop/windows/wsl/
I found where the "faulty" URL is coming from; more details in https://github.com/docker/docker.github.io/pull/13382.
I'm closing this ticket, because the broken link is not in the docs itself, but will be fixed in Docker Desktop.


learn from devtron

didn't know this but looks like devtron already has IPC monitoring -- worth seeing how they do it and pulling anything useful out
https://github.com/electron/devtron/blob/master/lib/ipc-helpers.js#L43-L55

released in 3.0.0


[Bug] Unable to limit and order unions

There is no streamlined method to to sort or limit a union query. Eg:
$query1->union($query2)->orderBy('foo');

This sorts $query1, not the union.
From MySQL Docs.
... use of ORDER BY for individual SELECT statements implies nothing about the order in which the rows appear in the final result because UNION by default produces an unordered set of rows.
But I digress, there is no method I can see for applying a limit and order by to the union itself.
Desired SQL:
(query 1 sql) union (query 2 sql) order by foo
Actual SQL:
(query 1 sql order by foo) union (query 2 sql)
Current solution (which is pretty bad):
$result = DB::select(DB::raw($query1->toSql() . ' ORDER BY foo'), $query1->getBindings());

Proposed solution:
$query1->union($query2)->orderUnionBy('foo');
$query1->union($query2)->limitUnion(7);
Better solution
Syntax has not changed, logic has been improved.

If limit() or orderBy() is called after a union(), it will affect the union query, not the calling query. To constrain the query, it must be done before union() is called. Eg:

$query1->orderBy('foo')->union($query2)->orderBy('bar');

Resulting SQL:
(query 1 sql order by foo) union (query 2 sql) order by bar
Let me know if this is acceptable and I will write unit tests and docs for it. No documentation change is required, this is an implied expectation.
Cheers

I'm trying to union two relationships as a related relationship
Im using nova & it applies orderBy to relationships
Table from one of the SELECTs cannot be used in global ORDER clause
public function related()
{
    return $this->parents()->union(
        $this->children()->getQuery()
    );
}

Any idea how keep it a relationship & bypass that error?
One solution is to put the orderBy before the union()
But because it's nova, I don't have control over that


fix incorrect translation key name in consumer incentives screen

I found that I had mistyped the translation key for the customer incentives screen title and summary 🥲

Hey @MuckT, We have verified this issue on Latest Android Internal Build V1.22.3, Test flight Build V1.22.3 & updated our observation in #1544 .
CC: @kathaypacific
Thanks..!!


Update baybe/examples/Basics /campaign.py and baybe/examples/Serialization /basic_serialization.py

In  baybe/examples/Basics /campaign.py, on line 80 recommendation = campaign.recommend(batch_size=2).
The argument to campaign.recommend has been changed to batch_quantity.
Please update the example.
This is also a problem in baybe/examples/Serialization /basic_serialization.py on lines 97, 98.

Hi @mgreiner79
I'm not sure if I can follow, can you be more specific about the versions your looking at? are you on main or 0.7.2 ?
batch_quantity has been renamed to batch_size but that happened after version 0.7.2 and is still unreleased, this means the doc will still show the state of 0.7.2
We are working on having also a versioned documentation so you can always see the doc for latest as well as all published versions
A quick search shows me that the current main does not have unwanted occurrences of batch_quantity

Hi @mgreiner79 and @Scienfitz,
I think there is perhaps some confusion here, probably caused by the fact that we do not yet have a versioned documentation yet as @Scienfitz pointed out (which will hopefully come soon).
To quickly resync everyone:

batch_size is indeed the new keyword. batch_quantity has been deprecated on the current main branch, but the change has not yet been released. Hence, the change is not yet visible on our online documentation.

So I'm now also trying to understand how @mgreiner79 ran into the issue. I suspect he used a version from main (e.g. via git-install) but then executed the code that was shown in the docs? And because the docs still show batch_quantity, he concluded that this is the new keyword? @mgreiner79: could you quickly confirm, or perhaps help us understand how you ran into the error?
FYI: Our examples and code snippets in the documentation are always automatically tested against the respective code version, ensuring that they can be executed without problems. So there is only little chance that something is inconsistent between code and doc. (Note: your issue #120 is in fact an exception since this was a problem related to the environment, not the code). But perhaps you found another edge case, so I'd really appreciate if you could help us find the root cause 🙃

Turned out the problem was due to using code from 0.7.2 but running the examples from the latest main branch, which already included the renaming. Probably, multi-version docs will help to avoid running into these problems in the future.


add (سینا) to  iranianNamesDataset.csv

In fact there are many other missing names in iranianNamesDataset.csv which are all present in iranianNamesDataset.py. Like سینا, سروش, سهراب, سهیل and etc.

hi sina
thanks for your request but I can't merge it because we have  "سینا"  if, in the CSV file, you see the data 8947.
Because the file is large, it is not possible to search the data easily through the browser, but since the data is in the form of alpha letters, it is better to search the data in alphabetical order first, then start adding.
Thank you for your request.

ok bro


[python3] build failure

Operating system
MacOS
Compiler
AppleClang
Steps to reproduce the behavior
`./vcpkg install python3`

Failure logs
Package: python3[core]:x64-osx -> 3.10.7#5
Host Environment

Host: x64-osx
Compiler: AppleClang <IP_ADDRESS>30022
vcpkg-tool version: 2023-04-07-bedcba5172f5e4b91caac660ab7afe92c27a9895
vcpkg-scripts version: 501db0f17 2023-04-15 (6 weeks ago)

To Reproduce
vcpkg install python3
Failure logs
-- Downloading https://github.com/python/cpython/archive/v3.10.7.tar.gz -> python-cpython-v3.10.7.tar.gz...
-- Extracting source /Users/frank.yonamine/Projects/vcpkg/downloads/python-cpython-v3.10.7.tar.gz
-- Applying patch 0001-only-build-required-projects.patch
-- Applying patch 0003-use-vcpkg-zlib.patch
-- Applying patch 0004-devendor-external-dependencies.patch
-- Applying patch 0005-dont-copy-vcruntime.patch
-- Applying patch 0008-python.pc.patch
-- Applying patch 0009-bz2d.patch
-- Applying patch 0010-dont-skip-rpath.patch
-- Applying patch 0012-force-disable-curses.patch
-- Applying patch 0013-configure-no-libcrypt.patch
-- Applying patch 0002-static-library.patch
-- Using source at /Users/frank.yonamine/Projects/vcpkg/buildtrees/python3/src/v3.10.7-a83fe77705.clean
-- Found external ninja('1.11.1').
-- Getting CMake variables for x64-osx-dbg
-- Getting CMake variables for x64-osx-rel
-- Configuring x64-osx-dbg
-- Configuring x64-osx-rel
-- Building x64-osx-dbg
-- Installing x64-osx-dbg
-- Building x64-osx-rel
-- Installing x64-osx-rel
-- Installing: /Users/frank.yonamine/Projects/vcpkg/packages/python3_x64-osx/share/python3/copyright
-- Fixing pkgconfig file: /Users/frank.yonamine/Projects/vcpkg/packages/python3_x64-osx/lib/pkgconfig/python-3.10-embed.pc
-- Fixing pkgconfig file: /Users/frank.yonamine/Projects/vcpkg/packages/python3_x64-osx/lib/pkgconfig/python-3.10.pc
-- Fixing pkgconfig file: /Users/frank.yonamine/Projects/vcpkg/packages/python3_x64-osx/debug/lib/pkgconfig/python-3.10-embed.pc
-- Fixing pkgconfig file: /Users/frank.yonamine/Projects/vcpkg/packages/python3_x64-osx/debug/lib/pkgconfig/python-3.10.pc
CMake Error at ports/python3/portfile.cmake:272 (message):
  There should be no modules with "_failed" suffix:

  /Users/frank.yonamine/Projects/vcpkg/packages/python3_x64-osx/debug/lib/python3.10/lib-dynload/_hashlib.cpython-310d-darwin_failed.so

  /Users/frank.yonamine/Projects/vcpkg/packages/python3_x64-osx/debug/lib/python3.10/lib-dynload/_ssl.cpython-310d-darwin_failed.so

  /Users/frank.yonamine/Projects/vcpkg/packages/python3_x64-osx/debug/lib/python3.10/lib-dynload/_tkinter.cpython-310d-darwin_failed.so

  /Users/frank.yonamine/Projects/vcpkg/packages/python3_x64-osx/lib/python3.10/lib-dynload/_hashlib.cpython-310-darwin_failed.so

  /Users/frank.yonamine/Projects/vcpkg/packages/python3_x64-osx/lib/python3.10/lib-dynload/_ssl.cpython-310-darwin_failed.so

  /Users/frank.yonamine/Projects/vcpkg/packages/python3_x64-osx/lib/python3.10/lib-dynload/_tkinter.cpython-310-darwin_failed.so
Call Stack (most recent call first):
  scripts/ports.cmake:147 (include)

Additional context
Additional context
No response

Original: https://github.com/microsoft/vcpkg/issues/31296

@dg0yt , Here is the logs:
build-x64-osx-dbg-err.log
build-x64-osx-dbg-out.log
build-x64-osx-rel-err.log
build-x64-osx-rel-out.log

I can't reproduce the error.
Comparing the build logs for _ssl.c with my machine, there are only two significant differences in the compiler/linker command lines:
I'm still on MacOSX13.1.sdk (yours: 13.3), and
my log has -mmacos-version-min=12.6 (yours: no such option).

btw hashlib and ssl both depend on openssl.

-mmacos-version-min=12.6 (you

How can I add it?
I don't change any parameter...

12.6 seems to be the version I'm running.
AFAIU you can set environment variable MACOSX_DEPLOYMENT_TARGET.
I don't fully understand the osx particularities and if this is the key to this issue. But things may become interesting when packages choose their own default. OTOH the python3 build is not like anything else, in general and for osx. (Currently looking at osx cross builds...)

12.6 seems to be the version I'm running. AFAIU you can set environment variable MACOSX_DEPLOYMENT_TARGET.
I don't fully understand the osx particularities and if this is the key to this issue. But things may become interesting when packages choose their own default. OTOH the python3 build is not like anything else, in general and for osx. (Currently looking at osx cross builds...)

I have brew installed. I can guess it may be an issue. It works in CI environment because I suppose brew is not installed there.
I want to avoid removing brew because it will mess up my work environment.... but I think I don't have much option...
Come later with your test suggestion and uninstalling brew...

I set the MACOSX_DEPLOYMENT_TARGET to 12.6 and it didn't work.
I removed brew and it didn't work.
I reinstalled brew and it didn't work.
I am not MacOS specialist, so I don't have any idea

I wouldn't call myself a specialist for osx, brew or python3, but...
I just finished adding osx cross build support to the python3 port (#31621). I wouldn't be surprised if some of the changes (search path setup) also improve the situation for native osx builds of that port. Can you test that PR?

I wouldn't call myself a specialist for osx, brew or python3, but... I just finished adding osx cross build support to the python3 port (#31621). I wouldn't be surprised if some of the changes (search path setup) also improve the situation for native osx builds of that port. Can you test that PR?

Ah, your patch worked!

Fixing by #31621.


Extract Graph in TensorFlow 2

I'm wondering how one might extract a graph in Tensorflow2.
Something like this in the pbtxt format:
node {
  name: "a"
  op: "matmul"
}
node {
  name: "b"
  op: "matmul"
  input: "a:0"
}
node {
  name: "c"
  op: "matmul"
  input: "a:0"
  input: "b:0"
}

It was pretty straightforward in TF1.

https://www.tensorflow.org/api_docs/python/tf/io/write_graph

I've seen that. I guess a better way to ask this question is
how to i convert an MNIST model into a graph object for the
argument graph_or_graph_def in
tf.io.write_graph(
    graph_or_graph_def, logdir, name, as_text=True
)

I don't know why you need this but check https://stackoverflow.com/questions/63181951/how-to-get-graph-or-graphdef-from-a-given-model

I designed a custom silicon accelerator.
Now I'm trying to write a TF compiler for it.
Was playing around with MLIR, but MLIR is missing
some basic documentation...

Please use the MLIR channels usually they are very available:
https://groups.google.com/a/tensorflow.org/g/mlir
https://llvm.discourse.group/c/mlir/31
https://discord.com/invite/xS7Z362


chore: update esbuild

Update esbuild to 14.34.
Remove esbuild-wasm from vendored dependencies (see comment from #99)

Seems Deno Deploy could unknowlingly break—esbuild-wasm is not used in testing environments. (I ran tests locally using esbuild-wasm before pushing this PR, btw).
Given that Deno Deploy is the likeliest target environment for fresh users, maybe tests should use esbuild-wasm instead of native esbuild?

esbuild-wasm is not used in testing environments.

It's not used in the CI tests, but each PR is deployed to Deno Deploy and then GitHub Actions will run Lighthouse against the preview URL. So that is sort of a smoke test.
I'd be happy to merge a PR that updates CI to also run the tests with WASM :-)


Publish the Active Development Documentation

New branch accessible via version-picker
New Release Notes topic specific to this version
New installation, quick-start, plug-in procedures
MQ and IMS plug-ins added
TPSRs and BoM

Do not merge until package available on Zowe.org

@jackjia-ibm I think we can just merge this into "Active Development" branch now, since the branch isn't actually visible to users.
Can we ignore the broken links in this particular case?
Meeting with John Mertic this afternoon to get the go ahead on making it live and adding button to Zowe.org.

@BrandonJenkins14 I see all broken links are in the TPSR page.
If we merge to active-development branch, these failures will be carried over and you won't see a successful active-development build. Since the pipeline stops at the broken link check, any new changes to the branches won't be published. So you will not see website updated.
If we decided to merge, we need to apply some tweaks to ignore the error and continue on publishing. @MarkAckert what do you think?

@jackjia-ibm It seems like a few of these websites are indeed live and accessible. Others give me actual 404 errors.

If we could prepend http:// to the links, will solve the issues. The failed links are not recognized as external URLs but as sub folders under our docs domain. The link checker doesn’t really go through third party links except for our own domains.

I can manually add the http for now, then maybe we can adjust automation to add it if it is missing in the future.

@jackjia-ibm Hey, when the time comes to publish this, what will I need to do to merge? I never figured out how to get past the broken links to external websites (see my previous comment), and I'm not familiar with the current build failure. Thanks!


QueueMessageHandlerFactory does not have one single line of JavaDoc

Title says it all.

SQS integration will be heavily revisited in 3.0 and will come with hopefully satisfying amount of documentation.


[HELP] Why my videos looks so awful?

When I create a video, they look like this. I don't think the prompt is wrong. This is the configuration I use (right now it's at 360p but the same thing happens at 720p; it's not a resolution problem, I'm just creating videos in 360p for speed reasons).
I’ve tried more than 100 prompts: longer, shorter, with more details, with fewer details, simpler, more complex, and basically all of them look very similar to this video. Am I doing something wrong?
Any advice you can give me?? Thank you very much.
{'aes': 7.0,  'align': 5,  'aspect_ratio': '16:9',  'batch_size': 1,  'condition_frame_length': 5,  'config': 'configs/opensora-v1-2/inference/sample.py',  'dtype': 'bf16',  'flow': 5.0,  'fps': 24,  'frame_interval': 1,  'model': {'enable_flash_attn': True,            'enable_layernorm_kernel': True,            'force_huggingface': True,            'from_pretrained': 'hpcai-tech/OpenSora-STDiT-v3',            'qk_norm': True,            'type': 'STDiT3-XL/2'},  'multi_resolution': 'STDiT2',  'num_frames': '120',  'prompt': ['A cyclist racing down a forested mountain trail. The cyclist '             'weaves between trees, dodging roots and rocks, with incredible '             'speed and agility. The trail is narrow and treacherous, with '             'dense foliage on either side. The scene is a blur of motion, '             'capturing the adrenaline and challenge of mountain biking.'],  'prompt_as_path': False,  'resolution': '360p',  'save_dir': './samples/samples/',  'save_fps': 24,  'scheduler': {'cfg_scale': 7.0,                'num_sampling_steps': 80,                'type': 'rflow',                'use_timestep_transform': True},  'seed': 44,  'text_encoder': {'from_pretrained': 'DeepFloyd/t5-v1_1-xxl',                   'model_max_length': 300,                   'type': 't5'},  'vae': {'force_huggingface': True,          'from_pretrained': 'hpcai-tech/OpenSora-VAE-v1.2',          'micro_batch_size': 4,          'micro_frame_size': 17,          'type': 'OpenSoraVAE_V1_2'},  'watermark': False}
https://github.com/hpcaitech/Open-Sora/assets/64336798/cc21192b-e65a-470e-a65c-786f79820dd4
EDIT: Others examples
torchrun --standalone --nproc_per_node 1 scripts/inference.py configs/opensora-v1-2/inference/sample.py \   --num-frames 120 --resolution 360p --aspect-ratio 16:9 --watermark False --aes 7 --flow 5 --num-sampling-steps 80 --cfg-scale 7 \   --prompt "A cozy coffe interior on a rainy day. Large windows show the rain falling outside, creating a soothing backdrop. Inside, the café is warm and inviting, with wooden tables, cushioned chairs, and soft lighting. A barista is seen making coffee behind the counter, and patrons are chatting or reading. The atmosphere is relaxed and comforting."
https://github.com/hpcaitech/Open-Sora/assets/64336798/8302946c-2ef9-431b-8622-0fe50396b2d6
torchrun --standalone --nproc_per_node 1 scripts/inference.py configs/opensora-v1-2/inference/sample.py \   --num-frames 120 --resolution 360p --aspect-ratio 16:9 --watermark False --aes 7 --flow 5 --num-sampling-steps 80 --cfg-scale 7 --seed 44 \   --prompt "A peaceful garden with a koi pond. The pond is surrounded by stones and lush greenery, with koi fish swimming gracefully in the clear water. A small wooden bridge arches over the pond, and a stone lantern adds to the tranquil setting. The garden is quiet, with the sound of water gently flowing and birds singing. The atmosphere is serene and meditative."
https://github.com/hpcaitech/Open-Sora/assets/64336798/ee0b2662-87cd-43a1-b3e0-2c999021ff24
torchrun --standalone --nproc_per_node 1 scripts/inference.py configs/opensora-v1-2/inference/sample.py \   --num-frames 120 --resolution 360p --aspect-ratio 16:9 --watermark False --aes 7 --flow 5 --num-sampling-steps 80 --cfg-scale 7 \   --prompt "A tranquil mountain lake surrounded by pine trees. The water is crystal clear, reflecting the surrounding landscape like a mirror. A small wooden pier extends into the lake, with a lone rowboat tied to it. The mountains in the background are majestic, their peaks dusted with snow. The air appears crisp and the scene is calm and serene."
https://github.com/hpcaitech/Open-Sora/assets/64336798/a20bd0a9-a2a0-42ed-89bc-da89b3a97539
=========================================================
TIP: If you first generate an image (text-to-image) and then create a text-to-video using the image as a reference, the quality of the videos improves significantly.
For example:
torchrun --standalone --nproc_per_node 1 scripts/inference.py configs/opensora-v1-2/inference/sample.py \   --num-frames 1 --resolution 1080p --aspect-ratio 16:9 --watermark False --aes 7  --seed 44 --cfg-scale 7 --sample-name image-cond \   --prompt "An underwater city inhabited by bioluminescent sea creatures, glowing in the depths of the ocean."

torchrun --standalone --nproc_per_node 1  scripts/inference.py configs/opensora-v1-2/inference/sample.py \   --num-frames 4s --resolution 360p --aspect-ratio 16:9 --watermark False --aes 7 --flow 5 --num-sampling-steps 90 --seed 44 --cfg-scale 7 \   --prompt 'Create a video capturing the breathtaking beauty of the sunset over the serene lake, with the mountains silhouetted against the colorful sky.{"reference_path": "samples/samples/image-cond_0000.png","mask_strategy": "0"}'
https://github.com/hpcaitech/Open-Sora/assets/64336798/bf278b48-0bb3-4b4c-a2b2-1ebb9537836a

They look fairly reasonable as compared with the demonstrations given by the team. But anyone having suggestions is welcome to share here.


Support for "mutable-content": true

The documentation for UNNotificationServiceExtension indicates

• The remote notification’s aps dictionary includes the mutable-content key with the value set to 1.

The FCM documentation at https://firebase.google.com/docs/cloud-messaging/http-server-ref#send-downstream does not make reference to the mutable-content key or a way to set the mutable-content key.
if I include "mutable-content": true as part of the notification dictionary within the payload submitted to FCM, the value is received (outside of the aps dictionary) on iOS as
    "gcm.notification.mutable-content" = true;

When will FCM support the mutable-content capability? How will I need to specify this within the FCM payload so that it will be received on iOS and allow the use of a UNNotificationServiceExtension to pre-process the received notification?

(bump)
Without this support in the HTTP API we cannot pre-process the received notification either. Setting the message in the notification body is not possible in our case.

Same problem here

Same here

This is a big problem and needs to be fixed ASAP. Without it we can't make any progress on iOS 10 notification service and content extensions.

I can not believe this is not fixed yet, should have been ready while iOS 10 was in beta.

Thanks - we have a FR for it internally, and are looking at the server side changes now. No specific timelines I can share, but should be in a future release.

@ianbarber any update on this?

No update, sorry

we've been waiting for 3 months now, any updates at least ?

@ianbarber any news on this?

@ianbarber is there a timeline for this feature ?

Any Updates please ?

Any updates? Issue is closed now??
Firebase seems a bad choice as a push service provider if you care about ios. We really want to support rich notifications.

Hi all - no update. Issue is closed as the tracker is for bugs on the samples. Support is still being worked on but we don't have a timeline - best place to check is the Firebase Release Notes and the firebase-talk Google group: https://firebase.google.com/support/ - sorry nothing more definitive right now!

This is so bad. We moved everything to FCM and now its lacking the basic features. Why to change the payload to  "gcm.notification.mutable-content" = true; ?

Appreciate your frustration - we should have been ahead of this one, sorry.

@ianbarber but why did you closed this issue .. you need to set bug or enhancement tag on it

Because this issue tracker is for samples, and this is not an issue with
the samples.
On Thu, 10 Nov 2016, 01:29 priyeshmarvi<EMAIL_ADDRESS>wrote:

@ianbarber https://github.com/ianbarber but why did you closed this
issue .. you need to set bug or enhancement tag on it
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/firebase/quickstart-ios/issues/70#issuecomment-259642124,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAM0Vp1f6OczpNHiuxENJibBJ1J7qTbHks5q8uPxgaJpZM4JgsEq
.

Not trying to be disagreeable, but the sample should show how to do this.

Yeah, I get that, but the max the sample should show how to do is things
the product does. If we supported mutable-content, and the sample didn't
show it, that would be a clear sample bug. Its worth noting there is a
specific place for filing product bugs and feature requests too (
https://firebase.google.com/support/contact/bugs-features/) so I'm not
trying to shut down otherwise useful feedback!
On Thu, 10 Nov 2016 at 12:19 Dave Anderson<EMAIL_ADDRESS>wrote:

Not trying to be disagreeable, but the sample should show how to do
this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/firebase/quickstart-ios/issues/70#issuecomment-259790563,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAM0VtLJH4wx_x-sygzENU31XpzNtNxvks5q83afgaJpZM4JgsEq
.

omg, still no fix ?

Just an update for anyone checking the new release for this: its being worked on, but we wont have anything until next year, sorry.

sorry sir,
currently i need to feature send notification with image, but the firebase it not support now, so can you tell me when firebase support this feature?
i need to time clear that have timeline for my project, so please answer ASAP
thank so much!

@ianbarber can you open up the API so we aren't relying on the SDK to whitelist adding these kinds of attributes to payloads? For future-proofing if the SDK isn't going to move as fast as client feature releases.

@ianbarber Thanks for the heads up. Is there any way to escalate this issue? Anything I can do, e.g. file anything similar to Apple's radar?

So basically, If I understood well, we can't use rich notifications on ios 10, because FCM client can't find "mutable-content" in "aps -> notification" node of push message?
NotificationService and NotificationContent extension in that case are not triggered and rich notifications are not created by the iOS 10...
This will be possible next year?

@tomaskraina https://firebase.google.com/support/contact/bugs-features/ is the closest thing to a radar.

I hope this to be fixed ASAP as well. I write a bug report to above link also.
(Everyone who enters this thread should send one bug report for each one. So they can quickly recognize how this is huge bug.)

Is it possible to include the image URL in the data message and create a local notification with image downloaded?

@ianbarber is there any update on rich notification support?

@ianbarber Hi, have you an idea about when this fix will be released ?

Hey guys, just migrated from Parse and found out that 'mutable-content' is not supported. Thought it'd be working out of the box considering iOS10 was released nearly 5 months ago... Anyway, any idea/update about when this will be added? @ianbarber

@aronse I contacted Firebase support team few hours ago and I just received that :

Many developers have already requested this feature for iOS. It is still being discussed by our engineering team and is being prioritized accordingly. I cannot provide any timeline and details regarding this feature, but you can keep track of our release notes.

@N0un Thanks! Well I can't really wait to see this implemented (or not) in the release notes... Also not exactly confident about using something that's 5 months late feature-wise (especially for something as trivial as this) so I guess I'll use something else.

Will we ever have any update on this? Or should I consider using other solutions as soon as possible?

Is there any update on this? We need rich notifications support from firebase.

@debayanb You can have iOS10 rich notification working on Firebase with little bit more work. Hint: Use click_action.
What's missing is being able to mutate the content of the notification, like add an image, for example without implementing Notification Content target.

@tomaskraina that's great, but as far as I know click action was here before iOS 10, what we can't do now is, as you mentioned, mutating the content, like loading and configuring the notification to present in a notification content extension with rich data (which is iOS 10 specific) since our notification service extension never gets called. Please correct me, if I'm wrong.

@Gujci You don't need to mutate the content in order to use the Notification Content Extension and show custom UI. Notification Content extension can be triggered via click-action, which translates into category when sent to APNS. That's what I do in my current app.
Only Notification Service Extension can't be triggered at the moment as you need the mutable-content flag.

@tomaskraina that is cool, but in my case the Notification Content Extension needs more data, basically the Notification Service Extension has to ask the server for more data. But I'll try to skip this step or just use the node apns module on the server. Thanks anyway :)

@Gujci Sure, no prob :) You can request the additional data in the Notification Content Extension.

@tomaskraina thanks man. I'll try it out.

I guess im not the only one waiting on a fix

When are we getting a fix on this ? Please!!!
Lg
Sent from my iPhone 6 Plus

On Feb 4, 2017, at 4:49 PM, Charles E<EMAIL_ADDRESS>wrote:
I guess im not the only one waiting on a fix
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Come on Firebase...
People are waiting for this for a long long time now.
Please deliver on your statements of being truly a cross platform solution for us mobile developers.
This is a very important feature that we REALLY need supported.
so PLEASE!!!

Really, after more than 5 months, nothing???

Hey all,
For anyone missing this feature badly, don't hesitate to file an official feature request with critical urgency at https://firebase.google.com/support/contact/bugs-features/
I recommend using the same title as this github issue and adding a link to the description.
I believe that this could help the engineers and/or managers at Firebase prioritize this issue internally, after seeing how many people need this.

@tomaskraina Did that on Friday and sadly got a sad feedback

Hi Felipe,
Thanks for reaching out. We're definitely aware that many users, such as yourself, would like the support for the "mutable-content" key for iOS available through FCM. We're exploring potential solutions, but I can't share any details or timelines at this time. We'll keep your feedback in consideration moving forward though.
Keep an eye out on our release notes for any further updates.
Cheers,
Firebase Support

Well, if you are counting on it be aware that it looks like it is not even is not even in development yet, let alone scheduled to be released shortly.

[Speculation]
Well, it is kind of understandable as adding this mutable tag to the payload is more than meets the eye. I initially thought it would be just adding a mutable tag to the notification payload until we started doing it on our own push sender mechanism.
When dealing with an app extension while having data on a local database means that you need to use an app group to share data between the app and the extension. Also, you have to migrate the data manually from the app to the app group and, if I had to guess, I would say that they want to make this step as straightforward as possible for developers, which can lead to a lot of complications, resulting in the humungous delay on delivering it.

Hi All,
We added the mutable_content field to FCM API.  Notification messages sent with mutable_content set to true can be intercepted on iOS 10+ clients and be updated before being presented to the user.
The mutable_content field maps to the mutable-content field on APNs.

That's great news! I am not even sad anymore that the support team had no idea of what was going on
@kroikie Do you know if we can expect Firebase SDKs to behave properly even with this app group issue when sharing content data between app and app extensions? If not, do you know who can provide this kind of information?

Hi @felipesabino from an FCM perspective the app group should not have any impact on the receipt of messages. I would assume the same for the other SDKs but I'm less sure about it's impact on them. I will raise it with my team and we will be sure to address any issues that come up, thanks for flagging it.

@kroikie thanks. Did you guys add this to the Notifications UI console? That's where I need it first.

According to the release notes they appear to have added this feature.

Added the mutable_content field to FCM API. When set to true, a notification message can be updated on an iOS 10+ client before it is presented to the user using the Notification Service app extension. The mutable_contentfield in the FCM API corresponds to the mutable-content APNs field.

This is just embarrassing! . Such a quick and easy implementation. And yet we are waiting for 6 months.
Lg
Sent from my iPhone 6 Plus

On Feb 7, 2017, at 8:53 AM, pinireisman<EMAIL_ADDRESS>wrote:
Come on Firebase...
People are waiting for this for a long long time now.
Please deliver on your statements of being truly a cross platform solution for us mobile developers.
This is a very important feature that we REALLY need supported.
so PLEASE!!!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Works perfectly for the rich notifications.

Locking this thread as it is now available in the API. Feel free to raise other feature requests with support - or open issues for other concerns!


Implement sorting

Per the spec, sorting of requests may be implemented via the query string. It appears we could pick either of the two formats, the latter is required for sorting on related objects' properties...which we probably wouldn't support initially anyway, but might be simpler to implement.
This will probably be implemented via an ActionFilter. Probably a separate one, but would there be any benefit to combining it with the one added in #16?

I am leaning towards putting this in a separate action filter too. I can't think of any good reasons why a user wouldn't include both filters, but it's still a cleaner design.

It occurred to me that one might want to omit sorting or querying for performance reasons...lack of indexes etc. could make sorting or filtering perform very poorly.
In fact, it now occurs to me that it might be good to find a way to let the user blacklist or whitelist fields for sorting (or filtering, for that matter). Some of my model objects have computed properties and sorting on one of those (if it even worked) would kill my app.


Guide how to setup and run boost tests

The project contains several boost test classes under https://github.com/spectrecoin/spectre/tree/master/src/test
The included README does not provide information to allow easy setup and run of tests.

Working on that


Please add a searchable field in the linked actors section or any drop down menu.

the issue i have is that i have so many actors to choose from a searchable field would be very time saving.

in the linked actor field and the linked journal field.

Hey!
That is a valid request and I will be adding this in the rework of the module. As it stand, the input is a standard Foundry select element.
The good news however is that by default, you can sort of search in such a select field by typing a letters which should then select an option that matches what you have typed (this however could be browser dependent, I know for a fact that chromium browsers have this functionality).
Thanks for the suggestion and when I have more updates regarding this functionality I will let you know.


virtualbox: 5.0.14 -> 5.0.20

Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

Thank you, but this is now obsolete per 4f5e4ad69c9a4dfb42ebe5ee42d13fa6b5312530