Using server side sorting doesn't seem to fire the modelUpdated event when clicking on the header.

It would be great to be able to detect the sort order being changed so I can tell the server to prepare the data in a new order.

the modelUpdated is from the inMemoryRowModel . . . . . . which is not used when doing Virtual Paging (aka infinate scrolling).
are you using infinite scrolling?
why do you want this event, if you are already in control (via the datasource) of the model updates??

For various reasons I have to store a large dataset in a user's session on the server and the user can request sorted by any of the columns. The act of clicking on the header to sort would then tell the server to perform a sort then reload the grid. At present the only way for me to detect this would be to compare the sortModel in the getRows function with the last sortModel and when this changes, perform the re-sort on the server.
Does that make sense?

yes it does make sense, but i don't think 'on model updated' is what you want. that's intended to be called after rows are loaded, that's the model that's the model that's updated. think you confusing it with the sort model - that doesn't trigger the model updated (but can cause it because it causes a data reload, but that's to late in your case).
sounds to me like a server side problem? you should compare the sort model to the previous sort model.

Thanks for the reply.
Yes, you’re right, and I’ve just implemented that :)
From: Niall Crosby<EMAIL_ADDRESS>Sent: Friday, 19 June 2015 9:22 p.m.
To: ceolter/angular-grid
Cc: craigsh
Subject: Re: [angular-grid] Using server side sorting doesn't seem to fire the modelUpdated event when clicking on the header. (#250)
yes it does make sense, but i don't think 'on model updated' is what you want. that's intended to be called after rows are loaded, that's the model that's the model that's updated. think you confusing it with the sort model - that doesn't trigger the model updated (but can cause it because it causes a data reload, but that's to late in your case).
sounds to me like a server side problem? you should compare the sort model to the previous sort model.
—
Reply to this email directly or view it on GitHub https://github.com/ceolter/angular-grid/issues/250#issuecomment-113444042 .  https://github.com/notifications/beacon/AMFym9xf5AFGpC4wfKQcj1TP2H7Y0L9dks5oU9a6gaJpZM4FGxtF.gif


fix creating this cookie without the "secure" flag and enabling cross-origin resource safe

Proposed changes

creating this cookie without the "secure" flag
enabling CORS is safe：The Access-Control-Allow-Origin header should be set only for a trusted origin and for specific resources. Thus, you can set access_control_allowed_origin_domain="trustedwebsite.com". By default, any domain name is allowed cross-domain access,access_control_allowed_origin_domain = "*"

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Investigate how the local path updates after to wind shifts

Currently, when we have a path with a corner designed for upwind sailing (first picture), and the wind direction shifts to a new direction that allows us to sail straight towards the goal (second picture), the local path doesn't update until a few minutes later when we receive a new Global path. Ideally, the local path should update automatically and more quickly. Keep in mind though, we still don't want the local path to make very small updates too frequently.
Relevant code: https://github.com/UBCSailbot/local-pathfinding/blob/099a29bb4c30e6c3ed6249f9d937d9e70230fac2/python/main_loop.py#L202

Local pathfinding tries to update the local path, but then will come up with an identical path multiple times for at least minutes in a row. I've only seen this happen with paths that have upwind or downwind sailing, but from what I've noticed the reason for trying to recalculate the path is always costTooHigh. Sometimes when I change the wind direction, the path gets updated quickly, and sometimes it takes at least several minutes, but I haven't left any tests running longer than that.
This run was executed at 7:14 on May 30, 2022 on my computer, while I was checked out to the latest commit made to the master branch.
The attached files are a sample of the terminal output demonstrating the potential issue, as well as a screenshot of the visualiser showing the upwind sailing section that should call for a new local path.
Potential Issue.txt

Great observations, I have a couple of questions

Can you detail the commands you ran so that I can reproduce it on my computer?
Why does the path eventually update? Is it because it finally manages to find a path with a lower path cost and that doesn't require a large turn, or is it some other reason?
What do you think the desired behaviour should be? Is a couple minutes to update the path a lot in the grand scheme of things?

I ran roslaunch local_pathfinding all.launch, then in a terminal window I ran rosparam set /global_wind_direction_degrees 50. Use whatever angle you need to create one section of the local path to be sailing straight into the wind, then wait and observe how the local path gets updated in the visualiser.
I think if the path contains upwind or downwind sailing at inappropriate angles, the local path should be updated in under 5-10 seconds or so. I'd be happy to ramble on about my thoughts on this, but the important part is that we are trying to balance "as fast as possible" with just enough patience to know our wind reading is accurate and we are in fact sailing upwind.

As to when it updates, here are some of my findings from testing just now:

when the current leg of the local path directly upwind, it will detect upwind sailing. It seems like it will say it detects more than 2 seconds of upwind sailing which is grounds for an update, but then the next loop, it will only detect 1.5 seconds and not do anything. It takes a while of this before it eventually updates the local path, but when it tries to update, it seems to work correctly.
When a future leg of the local path is upwind sailing, it tries to update because of the pathCost reason, but the path shown in the visualiser doesn't change. This can go on for several minutes, but just now I didn't test exactly how long.
I'm not sure anymore if its just the large turn threshold getting in the way, because if the whole local path is a straight line directly into the wind, the new path should be different by more than 10 degrees. I think I should try printing out if the large turn threshold is getting activated though.

Note that just now I had to try this in my lowWindConditions branch because of some issue I had with the main branch, but previously I observed this same behaviour in the main branch as well. I could see that it wasn't in low wind conditions, so it should be operating like normal.

I ran roslaunch local_pathfinding all.launch, then in a terminal window I ran rosparam set /global_wind_direction_degrees 50. Use whatever angle you need to create one section of the local path to be sailing straight into the wind.
I think if the path contains upwind or downwind sailing at inappropriate angles, the local path should be updated in under 5-10 seconds or so. I'd be happy to ramble on about my thoughts on this, but the important part is that we are trying to balance "as fast as possible" with just enough patience to know our wind reading is accurate and we are in fact sailing upwind.

As to when it updates, here are some of my findings from testing just now:

when the current leg of the local path directly upwind, it will detect upwind sailing, but can't make up its mind about if the amount of upwind sailing is greater than the 2-second threshold or not. It takes a while to update the local path, but when it tries to update, it works correctly.
When a future leg of the local path is upwind sailing, it tries to update because of the pathCost reason, but the path shown in the visualiser doesn't change. This can go on for several minutes, but just now I didn't test exactly how long.

Note that just now I had to try this in my lowWindConditions branch because of some issue I had with the main branch, but previously I observed this same behaviour in the main branch as well. I could see that it wasn't in low wind conditions, so it should be operating like normal.

Future testing/todo:

[ ] Try to get the main branch working again so I can do testing there.
[ ] Investigate whats the worst-case-scenario, ie the longest possible time we can be sailing in irons on the current leg of the local path without updating.
[ ] See if we can make it update the path properly if any leg is in irons, not just the current leg.
[ ] See if the small angle threshold is getting in the way, and modify this if needed. We don't want to be updating the local path with minor changes all the time though.


List desired components in alphabetical order

This PR:

Removes _component-example from preview, dist and demo folders
Ensures that components are always listed in alphabetical order (prevents making changes, when there are none - counteract gulp streams)

Screenshot

This works nicely! 💯


Include checksums in the GitHub releases

It would be very useful if checksums, such as SHA256, was included in the GitHub Releases.
This would enable me to automatically download the latest version of WinGet in SandboxTest script.
It would be also good to follow some kind of pattern, such as the one from goreleaser.
$ curl -L https://github.com/goreleaser/goreleaser/releases/download/v0.143.0/goreleaser_checksums.txt
0920d8b6be4be09744e9263be755965dc8a1df2318d6e8f68805990eb64f404d  goreleaser_armv6.deb
0b713827a2c0e21238a211899e6eb81f23c2dc7c9b39ecb426b06ed6efbce568  goreleaser_Darwin_x86_64.tar.gz

Great idea!

If this feature suggestion gets implemented on the gh , this change would be extremely easy.

I think this should also need to github itself provide checksum on the release file blob as more solutions now using github, Microsoft store as central distribution channels. So each project wouldn't need to reimplement or manually provide it.

I think this should also need to github itself provide checksum on the release file blob as more solutions now using github, Microsoft store as central distribution channels. So each project wouldn't need to reimplement or manually provide it.

Of course. This is a very old feature request that GitHub has, we can assume they won't implement.

We're now including the SHA256 in our releases.


Fix to #1726 - using boolProperty.Equals(true) in filter produces invalid sql

Problem was that we have special treatment for boolean to support queries like Where(c => c.MyBoolProperty). However this breaks for Where(c => c.MyBoolProperty.Equals(true/my_variable/other_bool_property).
Fix is to recognize this pattern in EqualsTranslator and compensate accordingly for boolean arguments.

@anpete


SILGen: Don't crash when compiling if #available with -disable-availability-checking.

This isn't an officially supported configuration, but is useful for testing and runtime development,
and we shouldn't crash.

@swift-ci Please test

Build failed
Swift Test Linux Platform
Git Sha - 18bd2f7526b55de1b1913805ea9335620f525844

@swift-ci Please test Linux


Build date in env-variable?

Target
I want to print App version: [version] | Build date: [buildDate] somewhere in my app built using create-react-app.
Now, where do I get my values from?

version: I read #2466 and found out that I can read the version-property from package.json. This makes sense as it's there anyway, so there's no need to specify another/redundant version number somewhere else.
buildDate: I read how to define custom environment variables and thought I could specify a custom environment variable the has the value of new Date(). But I failed, as I'm no expert in node scripts, etc. But I'm sure it's possible somehow. Maybe using a custom script or an npm package and also using cross-env as I'm developing on Windows and the server is Unix-based.

Idea
But then I thought that it would be nice, if create-react-app would already do that for me. I.e. provide a custom environment variable (e.g. REACT_APP_BUILD_DATE) that I can access in my code. I think it would be nice as from a create-react-app-user perspective

There's no need to add extra packages or add extra scripts
Would work on any OS
Same behavior for all environments (test, prod, etc.)
No extra configuration required on a build server or third party system
I can't imagine I'm the first person wanting to do something like that?

Some additional thoughts
As I said, I'm no expert on node/scripts so there might be a really easy approach to achieve this - basically all I want to do is dynamically set an environment variable to the current date.
If it's an option to include this feature in the product

I can give it a go myself and try to create a PR
There might be need for an extra namespace, e.g. REACT_APP_BUILTIN_ or something?
This functionality could even be extended and made more generic to easily allow devs to specify other properties than just the build date - if this is required

I don't know if this idea matches the philosophy of create-react-app or if it basically none of your business? :smirk:

I faced the same issue today and managed to solve it the following way:
"build": "REACT_APP_BUILD_TIME=$(date +%s) build:js"
Basically, you add the custom env. variable in package.json, under scripts {} collection, and then it can be accessed as process.env.REACT_APP_BUILD_TIME in project code. The date will be given in seconds, as Unix Epoch Time.
However, this will only work in Bash terminals, so in order to avoid cross-platform issues, you'll need to define it in .env.production file. The console command for the date itself may be different in Windows, though.
But for additional convenience, it would be great if such functionality was present in create-react-app out of the box.


ADB should also support a single character flag for the debugger: perhaps -g?

ADB should also support a single character flag for the debugger: perhaps -g?

To clarify, you you mean using both -g and the current --adb, or solely -g. I originally had --adb just so that I could search my command history easier

The accepted idea is that if you introduce double dash switches there there is always a single letter switch that also accomplished the same thing.  So in this case '-g' and '--adb' both do the same thing.

An implementation is now up on the PR. -g and --adb are both supported.

@olwmc Excellent!  One more nitpicky thing.  Could you add descriptions of those switches to the display_help() function?

How's this? It seems to be standard to level them out in this way.
** Asteroid Version 1.1.0 **
(c) University of Rhode Island
usage: asteroid [-<switch>] <input file>

command line flags:
 -s          enable symbol table dump
 -t          AST dump
 -v          version
 -w          disable tree walk
 -z          generate pstats
 -p          disable prologue
 -h          display help
 -r          disable redundant pattern detector
 -e          show Python exceptions
 -F          functional mode
 -g, --adb   run program through debugger

This has also been fixed. Will close when PR is merged

Ahh that makes sense. Alright. I’ll push that when I get home. I have the
changes lined up.
On Tue, Aug 30, 2022 at 12:08 PM Lutz Hamel @.***>
wrote:

The accepted idea is that if you introduce double dash switches there
there is always a single letter switch that also accomplished the same
thing. So in this case '-g' and '--adb' both do the same thing.
—
Reply to this email directly, view it on GitHub
https://github.com/asteroid-lang/asteroid/issues/193#issuecomment-1231874657,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIVRVS7CDNJ7FJW7EOHMZQTV3YWXHANCNFSM6AAAAAAQANLKLY
.
You are receiving this because you were assigned.Message ID:
@.***>


Resolved "No decode delegate for this image format" when converting full PDF (all pages) to png

Resolved "No decode delegate for this image format" when converting full PDF (all pages) to png
Exception encountered when running

Alpine in Docker container.
Node 10
Imagemagick
pdf-image 2.0.0

I'm currently having this issue, any ideas for a solution?

The fix is part of the pull request. But the pull request has yet not been
accepted by the owner/maintainer.
On Wed, Jul 24, 2019, 06:33 Eduards Egle<EMAIL_ADDRESS>wrote:

I'm currently having this issue, any ideas for a solution?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mooz/node-pdf-image/pull/49?email_source=notifications&email_token=AAOFYSANTOIXV3EHLL3BL43QBAVYXA5CNFSM4GOU2QX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2V5LMY#issuecomment-514577843,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOFYSBUE36EGRQCIO4FUX3QBAVYXANCNFSM4GOU2QXQ
.


DateTime is no more localized (in extension)

VSCode Version: 1.16 /1.17 insider
OS Version: Windows 10

In my extension (local-history), I use date.toLocaleString()
Previous return : 17/07/2016 à 10:12:25  (not sure it was in last version, perhaps a previous one...)
Currently return : 2016-7-17 10:12:25
In the console (Help / Toggle Developer Tools), I can still see  "17/07/2016 à 10:12:25"

Hard to say, the value of toLocaleString depends on your timezone and locale: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toLocaleString. I don't think that we have changed that or can event influence that.
@dbaeumer Does your nls-module depends on some process-defaults or on the API?

@jrieken I depend on electron API that I call to find out the locale to use. I somehow remember that I saw that before. Might be an electron problem ?

I try to reinstall the previous version, it worked:
1.15.1:

Now, something changed :
1.16.1:

@zabel-xyz What extension is that?

Like I say, I use date.toLocaleString() in my extension (local-history)
https://github.com/zabel-xyz/local-history/blob/master/src/historyTree.provider.ts#L74
https://github.com/zabel-xyz/local-history/blob/master/src/historyContent.provider.ts#L127

For now, I added a settings in my extension :
"local-history.dateLocale":  locale to use when displaying date


[Feature Suggestion]

Update to goloco v1.8.3?

We have released the new version that updates the project to GoGo Loco v1.8.3 today! Please try it out and have fun!


Error in menu.js

When I use the /template-app/index.html from the Electron's electron-quick-start app, I get this error upon startup:
menu.js:24 Uncaught TypeError: Cannot read property 'addEventListener' of null

The relevant portion in js/menu.js should be modified to this:
// Add the listener
document.addEventListener('DOMContentLoaded', function () {
  document.addEventListener('contextmenu', function (event) {
    menu.popup(remote.getCurrentWindow());
  })
})

Now the context menu opens fine.
Please let me know if you will like me to do a PR. Thanks.

Is there a reason not to use Photon's provided quick start app from app.js? I feel like there will always be some conflicts there.

Hi, not sure about what you mean by "Photon's provided quick start app". I am using the template-app that comes with the Photon distribution. The menu.js file there has this defect.

same here , in menu.js line 24 .
looked for the .js-context-menu manually and couldn't find it

I believe this issue is a duplicate of #49

@connors I'm seeing the same issue. Tried latest electron (pre-built binary).

Same here over a year later, it's referencing .js-context-menu nowhere to be found in quick start app :)

@willkriski I think this project is no longer being maintained. Use at your own risk 😢


no data flows on TCP when Raspberry Pi 4 ethernet offloading is enabled

When using a Raspberry Pi 4 with a recent kernel (e.g. 5.6.18) connecting to a smoltcp server, the TCP connection is established but then no data flows. The same behavior is observed on different devices (ARTIQ, STM32).
Attached is a packet capture (done on the RPI itself, it might be interesting to get another one using port mirroring on a switch); the RPI sends the data but it seems the smoltcp server does not process it.
rpi4smoltcp.zip
This can be worked around by running ethtool -K eth0 rx off tx off on the Raspberry Pi.

I took a look at the capture. It shows the rpi sends 10 bytes to smoltcp, and smoltcp correctly ACKs it. It seems like the TCP part is working correctly. I agree that there must be something fishy if it works without offloading but not without, but from the capture I don't see what it is.
In the capture, the TCP checksums for tx'd packets is incorrect. AFAIU this is normal if you have checksum offload enabled (the CPU sends the packet to the NIC without calculating the checksum, and the NIC calculates it when sending it. Since you're capturing on the CPU you get the packets without calculated checksum).
The checksum for rx'd packets is correct though, so probably smoltcp is filling them correctly, but maybe the NIC is auto-fixing them, and they're wrong on the wire?

what are you passing in ChecksumCapabilities? None means offload, Both means don't offload (calculate in software). If your NIC doesn't support offloading you should use Both.
Just to make sure: the attached capture corresponds to the "not working" case, not the "working" case?
What do you mean by "the smoltcp server does not process it"? It doesn't get returned from recv, recv_slice, peek, etc? Should the server respond with something that's not hitting the wire?
What's the complete setup? The smoltcp device is a Linux machine using tap, or raw socket, or custom hardware?
Attach packet captures for the "working" and "not working" cases, so we can hopefully spot a key difference.
Attach packet captures from the actual wire (port mirroring, or linux machine with 2 ethernet interfaces as bridge). This way we
Attach debug logs from smoltcp (debug and trace levels)

Just to make sure: the attached capture corresponds to the "not working" case, not the "working" case?

That's the not working case of course.

What do you mean by "the smoltcp server does not process it"? It doesn't get returned from recv, recv_slice, peek, etc?

Yes.

What's the complete setup? The smoltcp device is a Linux machine using tap, or raw socket, or custom hardware?

RPI4 connecting to an embedded smoltcp device (seen on STM32 and ARTIQ). Not tried other configurations with RPI4 as client yet.

Can you provide capture from the network, and smoltcp trace logs? it'll be impossible to figure this out otherwise.

Seems to have to do with the Raspberry Pi kernel version as well. 5.6.18 provokes the bug, 5.7.8 does not.

Attached are packet captures on the wire.
wire-capture.zip
Connection: RPI4 client connects to STM32 smoltcp server
Intended behavior: When receive a message, send back the cumulated number of character sent immediately.
Server timeout is set to be 2 seconds
The message duplicates itself in the packet when recv is not working. (e.g. packet no. 4, sent "test\n")
recv works for those that don't have duplicated message. (e.g. packet no. 30, sent "nothing\n")

It seems that there are issues with RPI4 pushing TCP packets onto the wire in 5.6.18.
For me, it only happens when the ethernet frame size is too small and padding is needed (i.e. frame length < 60, not counting frame check sequence). Normally, it is handled by adding paddings with 0-octets to make it at least 60 bytes. For some reason, rpi4 duplicates the data. Below are a few of my observations:

This rpi4 issue seems to be related to the TCP checksum.
The TCP checksum of the sent packets seems to be computed by ignoring the duplicate data. Wireshark thinks otherwise.
So for packet 4 of "wire-capture.zip", Wireshark thinks the checksum should be the 0x2f5d, probably calculated by adding the ASCII value of test\n to the received checksum (i.e. 0x556b+0x0074+0x6573+0x740a = 0x2f5d in 1's complement)
Maybe the problem is the checksum? What if the checksum doesn't change after the duplication? The easiest method I could think of is to send '\0's from RPI4. Here are the captures from the wire.
5-null-byte-test.zip
recv works in this case. Only 5 bytes are returned, which is correct.

This issue pops up with another non-smoltcp server as well.
I tried to set up a very simple Netcat server on another machine and connected RPI4 as a Netcat client.
host: nc -l <port>
client: nc <ip address> <port>

(Left side is the client, the right side is the server, only client sent messages, with hidden '\n' sent at the end of each line)
Sending null characters were also tested and yielded same result.

I am not quite sure whatever happened to me is the same as the OP's issue.

OP sent 10 bytes. No padding will be needed. My findings are strictly related to ethernet paddings.
The PSH got an ACK. As @Dirbaio mentioned, everything seems fine on the TCP part.

TLDR: On my side, there seems to be an issue with RPI4 handling TCP packet when ethernet padding is needed. The issue happens even when smoltcp devices are not involved. It is probably a RPI4 issue.
PS: Everything is fine when using RPI4 with kernel version 5.7.10

2\. This issue pops up with another non-smoltcp server as well.

Okay, I think it seems pretty clear this is a RPI/Linux bug not related to smoltcp.


Harmonise methods for distinguishing different Python source types

Summary
I was looking into #13246 to see if we could land the proposed change as part of Ruff 0.7, and noticed that we're currently pretty inconsistent in how we try to determine whether something is a Python source file or not (and, if so, what kind of source file it is). This PR tries to make it so that we only ever use ruff_python_ast::PySourceType for that purpose. This removes duplicated logic and the number of magic "py" or "pyi" strings across the codebase, and it should make it easier to make changes such as #13246 in the future.
Test Plan
cargo test

Could you create an issue to re-visit the case-insensitive extension matching and assign it to the next milestone. We should re visit this soon.

the codspeed flamegraph for this PR is very noisy so it's hard to tell, but I think that's just a false positive. I don't think I can see anything that would be plausibly related to this PR.

Could you create an issue to re-visit the case-insensitive extension matching and assign it to the next milestone. We should re visit this soon.

I opened https://github.com/astral-sh/ruff/issues/13691


Thunar can't launch vscode in wayland

I try to use thunar custom action to launch vscode, it works in X11, but it doesn't work in wayland (OS is KDE neon)
There is the script of the custom action
code -g %f --no-sandbox --verbose --log debug  > /home/wei-chih/Documents/tmp.txt

tmp.txt reports
[0517/162903.259368:ERROR:directory_reader_posix.cc(42)] opendir /home/wei-chih/.config/Code/Crashpad/attachments/5497eedb-8d17-4175-ba4a-97ed43236eea: No such file or directory (2)

Seems like it's a native crash, could you follow these steps to get a dump? https://github.com/microsoft/vscode/wiki/Native-Crash-Issues

I change the script to
code -g %f --no-sandbox --verbose --log debug --crash-reporter-directory /home/wei-chih/Documents/vscode_dump > /home/wei-chih/Documents/tmp.txt

tmp.txt
Found --crash-reporter-directory argument. Setting crashDumps directory to be '/home/wei-chih/Documents/vscode_dump'

But the dmp file isn't in plain text, is that normal?
vscode_dump.zip

Hey @deepak1556, this issue might need further attention.
@noctildon, you can help us out by closing this issue if the problem no longer exists, or adding more information.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!

@noctildon sorry for the delayed response, missed this issue thread. On wayland, you would need to start vscode with --ozone-platform=wayland to use wayland backend in the runtime. Does the crash happen when you try with this flag ?

Thanks it's fixed by adding the flag


dotenv set up for both services

Documentation here. By convention, .env contains secrets and is .gitignored/strongly discouraged from being uploaded. We could share a copy in drive for development, perhaps.
As an example:
alex@anblox:~/.../data-serving/data-service$ cat .env && echo
PORT=3002
alex@anblox:~/.../data-serving/data-service$ npm run start

><EMAIL_ADDRESS>start [...]/data-serving/data-service
> node dist/server.js

App running at http://localhost:3002.
  Press CTRL-C to stop

nice. should we add some documentation on this so folks know it's a requirement/what fields they need to specify?
(mostly for people outside core dev who, as you said, can share a config privately)

I think there's a larger task here to organize service-/repo-level documentation; there are a handful of pieces that ought to be documented. I'll make that task/assign myself.


[Suggestion] Auto input attacks

Hello,
As a person who doesn't understand Japanese, when adding a Yo-Kai, there is an option to chose the attacks. That is the hard part. When I just put a random attack for all the options in the Yo-Kai and save it, the Yo-Kai would not show up. I think that it is saying that the attacks are not "compatable."
What I am asking is if you could add a button to [Auto Input Attacks]. That would be great.
If you add it, could you let me know what the button is named in Japanese?
Also could you order the Yo-Kai in numbers from 1-??? And add a search function like all the other Yo-Kai Editors? Thanks

What I am asking is if you could add a button to [Auto Input Attacks]. That would be great.

Added. The button label is "デフォルト". It's located below the combo box for 3rd attack.


MQTT : ReceivedMessage : Payload type

Hi, using the docker cloud api image.
I receive some messages from topic: "thing/product/1681F58KDDD5H40B4XZ6/state".
Root object is 'data' but object properties are not the same.
How to deserialize payload to correct object?
Message #1:
Topic: thing/product/1681F58KDDD5H40B4XZ6/state
{"bid":"00000000-0000-0000-0000-000000000000","data":{"firmware_version":"05.01.0000"},"tid":"00000000-0000-0000-0000-000000000000","timestamp":1669801241618,"gateway":"4XLBK4S5526267"}
Message #2:
Topic: thing/product/1681F58KDDD5H40B4XZ6/state
{"bid":"00000000-0000-0000-0000-000000000000","data":{"control_source":"A","home_latitude":26836624.610466,"home_longitude":26836624.610466,"low_battery_warning_threshold":20,"payloads":[{"control_source":"A","payload_index":"53-0-0","sn":"1681F58KDDD5H40B4XZ6-0"}],"serious_low_battery_warning_threshold":10},"tid":"00000000-0000-0000-0000-000000000000","timestamp":1669801241617,"gateway":"4XLBK4S5526267"}
*serials have been changed - not real serial numbers

Also, Which format is used for the coordinates in the 'home_latitude' and 'home_longitude' fields? "home_latitude":26836624.610466,"home_longitude":26836624.610466

The coordinate system is WGS84.
"home_latitude":26836624.610466,"home_longitude":26836624.610466
But this is a bug.

In the demo, the channels are distributed according to the fields of the next level of "data", such as "firmware_version". Please let me know if you have a better way.

Thanks for your reply.
Root object "DATA" should be named according to object type to allow easier deserialization.
Looking at the classes, seems they are deliberatly renamed to data, there is @Data attribute on the root level which i beleieve affects the serialization of the root element to "data";
In example below, root object is "DeviceModelDTO" - i prefer it remain this way and not be renamed to data.
`package com.dji.sample.manage.model.dto;
import lombok.AllArgsConstructor;
import lombok.Builder;
import lombok.Data;
import lombok.NoArgsConstructor;
/**

@author sean

@version 0.2

@date 2021/12/8
*/
@Data
@Builder
@AllArgsConstructor
@NoArgsConstructor
public class DeviceModelDTO {
private String key;
private String domain;
private String type;
private String subType;

}
`


feat: all validators produce blocks

all validators create their own block
disable sync
broadcast to non-validators (clients & provers)

no longer needed.


[for release] Most Recent Backup fixes

Description
This PR addresses two issues:

“Most Recent Backup” values were not appearing in the CSV file downloadable from Linodes Landing.
The “Last Backup” column was not being sorted properly on Linodes Landing.

To fix:

Use nested key for the CSV header (backups.last_successful)
Use nested key for sortable table head label (backups:last_succesful)

I also removed a prop called mostRecentBackup from LinodeCard that was confusing and wasn’t being used anyway.
Note to Reviewers
Please check Linodes Landing. Last backups should appear in the downloadable CSV file and the "Last Backup" column should be sortable. Check group by tag, multiple browsers, etc.

Looks good, only potential issue I see is that if your backup status is 'scheduled' that will still appear blank in the CSV.

Thanks @WilkinsKa1. This was not a regression, so I merged as-is.
Since the column is currently labeled "Most Recent Backup" I'd argue it's appropriate to leave it blank for scheduled backups (the column in the UI is "Last Backup", so not as strict).
It is confusing though... maybe the column in the CSV should also be called "Last Backup" to match the UI.

@WilkinsKa1 just created a ticket to address this: M3-3759.


Parse backend errors that don't throw exceptions.

Description
This PR fixes an issue where errors returned from backend api requests are not converted to camelCase.

Checklist

[x] npm test runs as expected.
[x] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[x] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[x] @clerk/backend
[ ] @clerk/chrome-extension
[ ] @clerk/clerk-js
[ ] @clerk/clerk-expo
[ ] @clerk/fastify
[ ] gatsby-plugin-clerk
[ ] @clerk/localizations
[ ] @clerk/nextjs
[ ] @clerk/clerk-react
[ ] @clerk/remix
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/themes
[ ] @clerk/types
[ ] build/tooling/chore

@Nikpolik could you provide a test for this fix? What is the expected returned error?

@Nikpolik could you provide a test for this fix? What is the expected returned error?

Its exactly the same but camel cased

which matches the ClerkAPIError and the return type
Yes I'll add a test in the factory!


Build Java interface on Travis + Darwin Boost.Build fixes

Builds the Java interface on Travis
Changes some bash script syntax to make behavior on Darwin consistent with Linux (ex - quotes surrounding variable names in case statements)
Further attempts to get Boost to build with the right toolset based on the compiler in use -- seems to work okay now, at least no more undefined symbol errors on OS X
Adds an environment variable that can be set to enable debug info for the dependency installation script

I want to see this build on the mac builds before approving

I would do a merge request


Switch accumulation store to ResetAllLocks, only remove after unbond complete

This also switches to a version of the SDK fork, that fixes CacheKVStore speed under unfortunate access patterns.

Codecov Report

Merging #480 (22d4dc1) into main (a05d119) will increase coverage by 0.09%.
The diff coverage is 88.57%.

@@            Coverage Diff             @@
##             main     #480      +/-   ##
==========================================
+ Coverage   20.06%   20.15%   +0.09%
==========================================
  Files         163      163
  Lines       23326    23349      +23
==========================================
+ Hits         4681     4707      +26
+ Misses      17888    17884       -4
- Partials      757      758       +1

Impacted Files
Coverage Δ

x/lockup/keeper/lock.go
76.73% <87.09%> (+1.27%)
:arrow_up:

app/app.go
86.09% <100.00%> (+1.45%)
:arrow_up:

x/lockup/genesis.go
75.00% <100.00%> (+11.36%)
:arrow_up:

x/lockup/keeper/store.go
94.73% <100.00%> (+0.14%)
:arrow_up:

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 a05d119...22d4dc1. Read the comment docs.


Refactorings related to RunFsPaths (and other paths)

These changes are a preamble for #242. This PR is intended to be read commit by commit

I'm coverting this PR back to a draft because I may have a better solution that I am working on in #242

I like the refactoring with the new Paths module. And good catch on RunFsPaths only working in the HasFS root dir! I just added one remark on the fix. Did this come up through some test and if not, can we add one?

It came up in #242, but it was also something I had spotted a a while ago and planned on changing . I used to have some tests on this branch -- I'll see if I can add them again


Update pricing of models, and include 1106 and 0125 models.

New OpenAI Pricing
OpenAI updated the pricing of gpt-3.5-turbo-0125 on February 9.
Changes
This commit includes the following changes:

Update prices of all models as per OpenAI Pricing page
Include gpt-3.5-turbo-0125
Include gpt-3.5-turbo-instruct
Include gpt-4-0125-preview
Include gpt-4-1106-preview
Include gpt-4-1106-vision-preview

:rocket: This PR description was created by Ellipsis for commit eae0123b97e666c8fa8ed452c692bddae6475c2d.

Summary:
This PR updates the pricing of models and adds new models to the MODEL_COSTS dictionary in instructor/cli/usage.py, and updates the get_model_cost function to handle these new models.
Key points:

Updated pricing of models in MODEL_COSTS dictionary in instructor/cli/usage.py.
Added new models gpt-3.5-turbo-0125, gpt-3.5-turbo-instruct, gpt-4-0125-preview, gpt-4-1106-preview, and gpt-4-1106-vision-preview to MODEL_COSTS.
Updated get_model_cost function to handle new models.

Generated with :heart: by ellipsis.dev

Are you able to add the new embedding models too? His looks great

@jxnl Just added the new embedding models too. Thanks.

@jxnl Done! I put together this simple graph for tracking model alias relationships (and hence pricing), and tracking references, which should facilitate future pricing updates:
Model Literals
{
  "gpt-4-0125-preview": {"points_to": "gpt-4-0125-preview", "price": {"input": "0.01 / 1000", "output": "0.03 / 1000"}, "ref": ["https://platform.openai.com/docs/models/gpt-4-and-gpt-4-turbo"]},
  "gpt-4-turbo-preview": {"points_to": "gpt-4-0125-preview", "price": {"input": "0.01 / 1000", "output": "0.03 / 1000"}, "ref": ["https://platform.openai.com/docs/models/gpt-4-and-gpt-4-turbo"]},
  "gpt-4-1106-preview": {"points_to": "gpt-4-1106-preview", "price": {"input": "0.01 / 1000", "output": "0.03 / 1000"}, "ref": ["https://platform.openai.com/docs/models/gpt-4-and-gpt-4-turbo"]},
  "gpt-4-vision-preview": {"points_to": "gpt-4-vision-preview", "price": {"input": "0.01 / 1000", "output": "0.03 / 1000"}, "ref": ["https://platform.openai.com/docs/models/gpt-4-and-gpt-4-turbo"]},
  "gpt-4": {"points_to": "gpt-4-0613", "price": {"input": "0.03 / 1000", "output": "0.06 / 1000"}, "ref": ["https://platform.openai.com/docs/models/gpt-4-and-gpt-4-turbo"]},
  "gpt-4-0314": {"points_to": "gpt-4-0314", "price": {"input": "0.03 / 1000", "output": "0.06 / 1000"}, "ref": ["https://platform.openai.com/docs/deprecations/2023-06-13-updated-chat-models"], "legacy_model": true},
  "gpt-4-0613": {"points_to": "gpt-4-0613", "price": {"input": "0.03 / 1000", "output": "0.06 / 1000"}, "ref": ["https://platform.openai.com/docs/models/gpt-4-and-gpt-4-turbo"]},
  "gpt-4-32k": {"points_to": "gpt-4-32k-0613", "price": {"input": "0.06 / 1000", "output": "0.12 / 1000"}, "ref": ["https://platform.openai.com/docs/models/gpt-4-and-gpt-4-turbo"]},
  "gpt-4-32k-0314": {"points_to": "gpt-4-32k-0314", "price": {"input": "0.06 / 1000", "output": "0.12 / 1000"}, "ref": ["https://platform.openai.com/docs/deprecations/2023-06-13-updated-chat-models"], "legacy_model": true},
  "gpt-4-32k-0613": {"points_to": "gpt-4-32k-0613", "price": {"input": "0.06 / 1000", "output": "0.12 / 1000"}, "ref": ["https://platform.openai.com/docs/models/gpt-4-and-gpt-4-turbo"]},
  "gpt-3.5-turbo": {"points_to": "gpt-3.5-turbo-0125", "price": {"input": "0.0005 / 1000", "output": "0.0015 / 1000"}, "ref": ["https://platform.openai.com/docs/models/gpt-3-5-turbo"]}, // "The gpt-3.5-turbo model alias will be automatically upgraded from gpt-3.5-turbo-0613 to gpt-3.5-turbo-0125 on February 16th."
  "gpt-3.5-turbo-16k": {"points_to": "gpt-3.5-turbo-16k-0613", "price": {"input": "0.0030 / 1000", "output": "0.0040 / 1000"}, "ref": ["https://platform.openai.com/docs/models/gpt-3-5-turbo"]},
  "gpt-3.5-turbo-0301": {"points_to": "gpt-3.5-turbo-0301", "price": {"input": "0.0015 / 1000", "output": "0.0020 / 1000"}, "ref": ["https://platform.openai.com/docs/deprecations/2023-06-13-updated-chat-models"]},
  "gpt-3.5-turbo-0613": {"points_to": "gpt-3.5-turbo-0613", "price": {"input": "0.0015 / 1000", "output": "0.0020 / 1000"}, "ref": ["https://platform.openai.com/docs/models/gpt-3-5-turbo"], "legacy_model": true}, // "The gpt-3.5-turbo model alias will be automatically upgraded from gpt-3.5-turbo-0613 to gpt-3.5-turbo-0125 on February 16th."
  "gpt-3.5-turbo-1106": {"points_to": "gpt-3.5-turbo-1106", "price": {"input": "0.0010 / 1000", "output": "0.0020 / 1000"}, "ref": ["https://platform.openai.com/docs/models/gpt-3-5-turbo"]},
  "gpt-3.5-turbo-0125": {"points_to": "gpt-3.5-turbo-0125", "price": {"input": "0.0005 / 1000", "output": "0.0015 / 1000"}, "ref": ["https://platform.openai.com/docs/models/gpt-3-5-turbo"]},
  "gpt-3.5-turbo-16k-0613": {"points_to": "gpt-3.5-turbo-16k-0613", "price": {"input": "0.0030 / 1000", "output": "0.0040 / 1000"}, "ref": ["https://platform.openai.com/docs/deprecations/2023-11-06-chat-model-updates"], "legacy_model": true},
  "gpt-3.5-turbo-instruct": {"points_to": "gpt-3.5-turbo-instruct", "price": {"input": "0.0015 / 1000", "output": "0.0020 / 1000"}, "ref": ["https://platform.openai.com/docs/models/gpt-3-5-turbo"]},
  "text-embedding-3-small": {"price": "0.00002 / 1000"},
  "text-embedding-3-large": {"price": "0.00013 / 1000"},
  "text-embedding-ada-002": {"price": "0.00010 / 1000"},
}

@jxnl I've reintroduce the behaviour of using a future model version's prefix to match it to it's model family alias. Good catch, thanks.


The system cannot find the path specified

I'm encountering an issue during arcgic_enterprise_webadpator[Configure Web Adaptor with Portal], I'm getting the error that "The system cannot find the path specified".  It's in reference to the "C;\Program Files (x86)\Common Files\ArcGIS\WebAdaptor\IIS\Tools\ConfigureWebAdaptor.exe". It appears that the server web adpator has placed this file (ConfigureWebAdaptor.exe) in a different location, then stated in this error with portal.

@vmurga So, to be clear, you are trying to configure the Web Adaptor to Portal.  Did you install the Web Adaptor with Chef?
What does your JSON file look like?  Maybe you can set the install dir to the correct location and see if that makes a difference?
{
  "arcgis": {
    "version": "10.5",
    "web_adaptor": {
      "install_dir": "c:\\correctlocation\\IIS\\Tools\\ConfigureWebAdaptor.exe",
    },
    ...

I 'm using Chef and I did try to correct the location.

@vmurga , for that "TCP connection" error, have you tried running chef directly on the node using the chef-client command?

To resolve the issue. I set Portal and Server up on two different machines and configured Tomcat on the Portal machine to 443. Thanks everyone.


README - Add remotes example

Documentation Update
Updated the README to give an example of adding remotes to Heroku. Thought it would be nice to see an example here to prevent someone from having to look it up.

@matthewhatch thanks for the contribution!


As a datastore packager, I want to upload Eia860 source data to Zenodo

Source data can be uploaded to Zenodo via a simple CLI
The Zenodo archive will be given a new version if the uploaded data differs from what exists on the most recent previous version.
The Zenodo archive will be left unchanged if the uploaded data is identical to the most recent previous version.
The archive will contain accurate, well formed frictionless metadata in a datapacakge.json file.

Reminders:

[ ] "resources" field programmatically populated
[ ] "created" , datetime.isoformat() programmatically populated


Ocamlmerlin not running on Windows 10 WSL (Linux Subsystem)

I have an issue getting ocamlmerlin run on windows 10 with WSL (Windows Subsystem for Linux)
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:2255 ocamlmerlin error: /mnt/c/Users/rober/AppData/Roaming/npm/ocamlmerlin: line 1: /node_modules/ocaml-reason-wsl/bin/ocamlmerlin.bat: No such file or directory

now I went on the CLI to that directory
cd C:\Users\rober\AppData\Roaming\npm
.\ocamlmerlin

and tried to start it there but got the same error
/mnt/c/Users/rober/AppData/Roaming/npm/ocamlmerlin: line 1: /node_modules/ocaml-reason-wsl/bin/ocamlmerlin.bat: No such file or directory

the error message is pretty clear as the path does not exist indeed. So I tried to call it directly
.\node_modules\ocaml-reason-wsl\bin\ocamlmerlin.bat
again I get the same error

my fault. sorry


Add support for logging

[x] master
[x] 4-2-stable

seems... premature?

Updated issue title to reflect that fact that the C++ REST API has support for logging even though it doesn't log much information at this time.
Resolved by #52 and #46


Cannot download files when firewall is enabled!

Hello,
When I disable my firewall, I'm able to download files normally over FTP. Port 43257 is my FTP port. However, when I enable it, I'm unable to download over FTP.
FTP config:
Hostname: xxx.xxx.xxx.xxx
Port: 43257
Require explicit FTP over TLS
My firewall config:
22/tcp                     ALLOW IN    Anywhere
80/tcp                     ALLOW IN    Anywhere
443/tcp                    ALLOW IN    Anywhere
43257                      ALLOW IN    Anywhere
20                         ALLOW IN    Anywhere
21                         ALLOW IN    Anywhere
22/tcp (v6)                ALLOW IN    Anywhere (v6)
80/tcp (v6)                ALLOW IN    Anywhere (v6)
443/tcp (v6)               ALLOW IN    Anywhere (v6)
43257 (v6)                 ALLOW IN    Anywhere (v6)
20 (v6)                    ALLOW IN    Anywhere (v6)
21 (v6)                    ALLOW IN    Anywhere (v6)
My firewall logs show entries such as:
[UFW BLOCK] IN=eth0 OUT= MAC=42:01:0a:b4:00:03:42:01:0a:b4:00:01:08:00 SRC=xxx.xxx.xxx.xxx DST=<IP_ADDRESS> LEN=52 TOS=0x00 PREC=0x00 TTL=112 ID=25433 DF PROTO=TCP SPT=53039 DPT=8190 WINDOW=65535 RES=0x00 SYN URGP=0
It should also be noted that rtinst is running on a cloud machine.

It appears that adding the following to the /etc/vsftpd.conf and allowing 10090:10100/tcp through the firewall resolved this issue for me.
pasv_enable=YES pasv_min_port=10090 pasv_max_port=10100
Documentation: https://serverfault.com/questions/897119/ftps-sometimes-timeout-when-ubuntu-firewall-enabled
Should this not be documented somewhere?

This is common knowledge regarding using a firewall... If someone else faces the same issue, they will find this issue when searching in rtinst issues or when using a search motor 👍


review Missing Maps school project materials

https://drive.google.com/drive/u/0/#folders/0B_hW0KstPK1AY0t5M2c0TVhFamc/0B_oUuPnytdlEWUtLOHhjYVR1Umc/0B_oUuPnytdlEaXpZTHRhdDhXZGM
may be some useful pieces to use, people to connect with
status of the program is unknown

@mikel I've reviewed the materials and there are a few gems we can look at, particularly the pieces that consider outreach to schools/educ institutions. Besides Pete, do you know any of the others?

Pete would be the main person to connect with on this ... need his contact?
 On Friday, October 23, 2015 12:12 PM, Steven Johnson<EMAIL_ADDRESS>wrote:

@mikel I've reviewed the materials and there are a few gems we can look at, particularly the pieces that consider outreach to schools/educ institutions. Besides Pete, do you know any of the others?—
Reply to this email directly or view it on GitHub.

OBE


Handled the type element null case

Description
As I used the lint in a production application, I got frequent Null check operator used on a null value errors in the custom.log file. That was due to this code in the TypeChecker class.

/// Returns `true` if representing a super type of [staticType].
///
/// This only takes into account the *extends* hierarchy. If you wish
/// to check mixins and interfaces, use [isAssignableFromType].
bool isSuperTypeOf(DartType staticType) => isSuperOf(staticType.element!);

Sometimes staticType.element is null (Documentation says when the Ast is unresolved but I'm not sure). For now, I have checked the element null case only in the wrap_with_stack assist. But the error is thrown in almost every lint. Need some research on this issue though.
error log:
[WrapWithStack] 2024-01-15T14:15:52.836429 Plugin WrapWithStack threw while analyzing /home/sam/work_projects/flutter/vidaksh_mobile/lib/src/modules/home/presentation/pages/about_us_page.dart:
[WrapWithStack] 2024-01-15T14:15:52.836429 Null check operator used on a null value
[WrapWithStack] 2024-01-15T14:15:52.836429 #0      TypeChecker.isSuperTypeOf (package:custom_lint_core/src/type_checker.dart:224:74)
[WrapWithStack] 2024-01-15T14:15:52.836429 #1      WrapWithStack.run.<anonymous closure> (package:pyramid_lint/src/assists/flutter/wrap_with_stack.dart:29:42)
[WrapWithStack] 2024-01-15T14:15:52.836429 #2      _rootRunUnary (dart:async/zone.dart:1415:13)
[WrapWithStack] 2024-01-15T14:15:52.836429 #3      _CustomZone.runUnary (dart:async/zone.dart:1308:19)
[WrapWithStack] 2024-01-15T14:15:52.836429 #4      LinterVisitor._runSubscriptions (package:custom_lint_core/src/node_lint_visitor.g.dart:29:27)
[WrapWithStack] 2024-01-15T14:15:52.836429 #5      LinterVisitor.visitInstanceCreationExpression (package:custom_lint_core/src/node_lint_visitor.g.dart:609:5)
[WrapWithStack] 2024-01-15T14:15:52.836429 #6      InstanceCreationExpressionImpl.accept (package:analyzer/src/dart/ast/ast.dart:10462:15)
[WrapWithStack] 2024-01-15T14:15:52.836429 #7      NodeListImpl.accept (package:analyzer/src/dart/ast/ast.dart:12998:20)
[WrapWithStack] 2024-01-15T14:15:52.836429 #8      ArgumentListImpl.visitChildren (package:analyzer/src/dart/ast/ast.dart:510:16)

Type of change

[x] Bug fix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Code refactor
[ ] Documentation
[ ] Other

Checklist

[x] I have read the CONTRIBUTING.md document.
[x] I have performed a self-review of my code.
[ ] I have linked the issue ticket in the description.
[ ] I have made the necessary changes to the documentation.
[x] I have checked the formatting with dart format .
[x] I have analyzed my code with dart analyze .
[x] I have run dart run custom_lint example to check for any custom linting issues.

I couldn't reproduce the error.
Are you able to consistently reproduce the error in a fresh project?
Would be great if you could provide me a repo or example code to work with.
Maybe worth reporting the issue to the custom_lint repo.

Hello! I have encountered the same issue and created an issue invertase/dart_custom_lint#229.
The fix has been merged to the latest version custom_lint_builder v0.6.2 and running dart pub upgrade in your project should fix the issue.


Cannot find module 'pages/index.js?v=d187aabeaedb9b4063f6' from '/sandbox'

Version
v2.4.3
Reproduction link
https://codesandbox.io/s/ov642w2v25?module=%2Fnuxt.config.js
Steps to reproduce
Make chunkName as '[name].js?v=[contenthash]' in nuxt.config.js
What is expected ?
There is no error
What is actually happening?
Error page with NuxtServerError
Cannot find module 'pages/index.js?v=d187aabeaedb9b4063f6' from '/sandbox'
Additional comments?
PR https://github.com/nuxt/nuxt.js/pull/4439 make code simplier:
it was before:
bundle.files[asset.name] = compilation.assets[asset.name].source()

and after:
bundle.files[asset.name] = asset.name

I'am not sure is this line works early, but now it don't.
Created .nuxt/dist/server/server.manifest.json contains:
{
  "entry": "server.js",
  "files": {
    "pages/index.js?v=825661537585209d20c2": "pages/index.js?v=825661537585209d20c2",
    "server.js": "server.js"
  },
  "maps": {
    "server.js": "server.js.map"
  }
}

Obviously, there is no that file.

This bug report is available on Nuxt community (#c8640)

This is an issue in the initial scaffolding of create-nuxt-app. Rolling nuxt back to 2.4.2 fixes this for now

@DaleMatthews Could you please provide more details about how to reproduce?

I've just tried generating nuxt apps with various parameters and can't seem to recreate this issue again

Because it's happens randomly. I have this issue in all current Nuxt projects, after I update my package.json. https://cmty.app/nuxt/nuxt.js/issues/c8631#comment-5c66695539ee380014b5037b

@bdrtsky feel free to send in a bug report

@clarkdo Running nuxt-edge solved the issue for me for now, so I'm guessing it's been fixed recently.

@manniL happy to do this, but I am not sure how to reproduce this. It doesn't happens every time, may be once in 10-30 dev server reloading.

@bdrtsky Include as much info as you can. If you can't repro that reliably, state it as is ☺

Having a similar issues as well with just pages/index.js. The only potential issue I see is that I have srcDir set in my nuxt config and maybe sometimes that not read.

This is an issue in the initial scaffolding of create-nuxt-app. Rolling nuxt back to 2.4.2 fixes this for now
@DaleMatthews do you know what is causing the problem in the scaffolding and how to fix it? I have an app generated with 2.4.3, just yarn upgraded to 2.4.5 but still have the issue.

Have the same issue on 2.4.3 and 2.4.5 versions.
2.4.2 is ok.

@arkhamvm the fix has already been rolled out 🤔  via #5007

@manniL actually I'm experimenting the problem without using chunking. I just get
Cannot find module 'pages/index.js' (and for every other route). Then I stop the server, run dev again and if I'm lucky I can start working again. It happens totally random, so I don't really know where to look at

@manniL actually I'm experimenting the problem without using chunking. I just get
Cannot find module 'pages/index.js' (and for every other route). Then I stop the server, run dev again and if I'm lucky I can start working again. It happens totally random, so I don't really know where to look at

Yeah, absolutely similar

@mfrascati @arkhamvm That's a completely different issue. Please create a new bug report.

@manniL @clarkdo I can aprove - bug still present, there is no PR in 2.4.5

It seemed that this pr isn’t included in latest release @manniL @pi0

@clarkdo Whoops.

@mfrascati you just described my problem exactly. Did you managed to create separate issue?

@bdrtsky Opened an issue here: https://github.com/nuxt/nuxt.js/issues/5132

I was just able to delete my node_modules directory and re-run install and it started to work. Im guessing it's because my npm package updated.

It seemed that this pr isn’t included in latest release @manniL @pi0 @clarkdo
Guys, when release is planned?

@karakum This week 😄

I faced the same issue yesterday and today.

Same problem here and yes, it seems random. Not sure how to fix it

@codeofsumit With the ?v=... suffix or more like https://github.com/nuxt/nuxt.js/issues/5132 ?


Is it possible to get full parameterized query back?

For example i run my query like this:
let query = db.run('SELECT * FROM foo WHERE bar = ?', ['xyz'], (err) => {
   ....
});

Is it possible to somehow get back the full query? So i want to get back the full SELECT * FROM foo WHERE bar = 'xyz' query.

Unfortunately I don't think it is, but happy to accept a PR if someone finds out how 🙂


Add travis config to repo

This commit adds a basic travis config to the repo to run unit tests and
pylint. This will mean once we get everything in the repo working this
will enforce we have working tests and style enforcement for all commits
moving forward.

An admin for the Qiskit organization on github will have to enable travis on this repo I think (I tried but it said I didn't have permissions) to verify that this works. We should enable travis first to have this change self testing before merging.


Fix: Only add js hydration client code if needed

Adds the js hydration helper only if the page contains components needed to hydrate.

! Great catch @gregod.

@gregod Looks good. At the laptop I'm realizing that hydrateComponents should never run unless there are components to hydrate. I'm good with this change though as it makes this explicit.


Fix incorrect rstrip configuration #394

Change Summary
Remove - from condition lines since it breaks multiline output for
banner.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes)
[ ] Documentation content changes
[ ] Other (please describe):

Related Issue(s)
Fixes #394
Component(s) name
eos_cli_config_gen
Proposed changes
Use AVD standard condition line without -
How to test
banners:
  login: |-
    My first banner line
    Connected to Device $(hostname) EOF

Result should be:
!
banner login
My first banner line
    Connected to Device $(hostname) EOF
!

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have updated molecule CI testing accordingly
[x] I have read the CONTRIBUTING document.
[x] All new and existing tests passed (pre-commit, make linting and make sanity-lint).

Hi @c-po
Ready for your review

LGTM, Jinja2 is sometimes very picky about its new line stuff.


Change incorrect Projection test

The last commit broke ci because of other changes on main since then.
The test that I changed was incorrect, doing df["x"] will reduce to a Series, selecting x again would reduce to a scalar, so we can't just get rid of the Projection.

Merging to get ci back to green


Dummy Module Database Migration

This PR adds:

Persisting the database version of each module and checking if a db migration needs to occur.
A DB Migration of the Dummy Module integration test.

OK, so things that I realized just recently:

the "outside" (generic code) should persist the current version of db schema for each module instance
user provides map of migrations in ModuleGen and a static current desired db version
"the outside" should be responsible for calling all the migration between the current db schema version and desired db version, probably in the code that does the Module::init of all the modules

Latest version should do most of the above things you mentioned:

the "outside" (generic code) should persist the current version of db schema for each module instance, so the module never even sees it;
See apply_migrations in fedimint_api::db::mod.rs. This is outside modules and handles the DatabaseVersion for each module.

user provides map of migrations in ModuleGen and a static current desired db version
Latest code contains get_migration_map which is part of the ModuleGen trait and allows modules to define which migrations are needed. DATABASE_VERSION constant forces modules to define which version the code is compatible with.

"the outside" should be responsible for calling all the migration between the current db schema version and desired db version, probably in the code that does the Module::init of all the modules
This one is tricky. apply_migrations needs to be called before init, since db is one of the parameters to init and it is unsafe to access the db before the migrations have occurred. However, we can't call one of the trait functions in FedimintConsensus::new until after init since that's what creates the instance of the module in the first place. Perhaps we should statically iterate through all of the "registered modules" (i.e LightningGen, WalletGen, etc) and call apply_migrations on each one? That way we could do the migrations before calling init

However, we can't call one of the trait functions in FedimintConsensus::new until after init since that's what creates the instance of the module in the first place.

Ignore this, I misinterpreted the code. This should be fixed now, apply_migrations is called before init in FedimintConsensus::new

Codecov Report
Base: 65.00% // Head: 65.39% // Increases project coverage by +0.39% :tada:

Coverage data is based on head (56c9050) compared to base (d3f7d45).
Patch coverage: 74.44% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1567      +/-   ##
==========================================
+ Coverage   65.00%   65.39%   +0.39%
==========================================
  Files         129      129
  Lines       23310    23388      +78
==========================================
+ Hits        15153    15295     +142
+ Misses       8157     8093      -64

Impacted Files
Coverage Δ

fedimint-api/src/core.rs
92.00% <ø> (-0.25%)
:arrow_down:

modules/fedimint-ln/src/lib.rs
73.49% <ø> (-0.14%)
:arrow_down:

modules/fedimint-mint/src/lib.rs
77.55% <ø> (ø)

modules/fedimint-wallet/src/lib.rs
77.54% <ø> (+0.23%)
:arrow_up:

fedimint-api/src/db/mod.rs
87.59% <61.53%> (+0.20%)
:arrow_up:

fedimint-server/src/consensus/mod.rs
82.28% <62.50%> (-1.17%)
:arrow_down:

modules/fedimint-dummy/src/db.rs
73.91% <88.23%> (+73.91%)
:arrow_up:

modules/fedimint-dummy/src/lib.rs
35.02% <90.90%> (+34.51%)
:arrow_up:

fedimint-api/src/module/mod.rs
75.25% <100.00%> (+1.17%)
:arrow_up:

gateway/ln-gateway/src/utils.rs
61.53% <0.00%> (-30.77%)
:arrow_down:

... and 11 more

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Since @dpc worked with you on this most I'd like to see his ACK first, then I can do a final review, then maybe squash some of the fixups if applicable and then re-ACK+merge.


<IP_ADDRESS>.0

This PR updates the partner version to <IP_ADDRESS>.0 for release.
DO NOT MERGE

Released: https://github.com/ChartBoost/chartboost-mediation-android-adapter-verve/releases/tag/v<IP_ADDRESS>.0


I don't see the local property of the DbSet

In EF6 I have the property MyDbSet.Local in which I can access to the entities that are in the DbContext, so I can access to the local entities so I don't have to do another queries to the database.
In EF Core I don't see this property, so I would like to know the way that I can access to the entities that are loead in the DbContext.

@ComptonAlvaro DbSet.Local is not yet implemented. You can use  `context.ChangeTracker.Entries' to get access to the entities that are being tracked. For example, to get all tracked entities, you can do:
context.ChangeTracker.Entries().Select(e => e.Entity)

To get all tracked Blog entities, do:
context.ChangeTracker.Entries<Blog>().Select(e => e.Entity)


Update to AndroidX and fix cache copy

I updated to AndroidX to use sdk 29.
Also I fixed on 845c2c0 an error that makes a cache copy either is not a file from google photos. Now it return the remote path from google photos as do it here: https://gist.github.com/chauhan-tarun/15eb908a778ac77835d7433e04f71c16#file-realfilepath-java-L75
Sorry for fix two thing in one PR, I'm little in hurry.
This is related to #12

Closed for improved pull request #15


qa: Fix SourceTest without YAML extension

Previously when the YAML extension was not installed, the test was skipped entirely, as the data provider is invalid:

Error
The data provider specified for CuyZ\Valinor\Tests\Integration\Mapping\Source\SourceTest::test_sources_are_mapped_properly is invalid.
CuyZ\Valinor\Mapper\Source\Exception\YamlExtensionNotEnabled: The PHP YAML extension is not enabled.
/pwd/src/Mapper/Source/YamlSource.php:38
/pwd/src/Mapper/Source/Source.php:55
/pwd/tests/Integration/Mapping/Source/SourceTest.php:74

Now only the YAML test is marked as skipped and the remaining tests are executed.

Hmm. I expected the @throws tag to fix the PHPStan issue based on:
https://phpstan.org/blog/bring-your-exceptions-under-control#inline-%40throws
Will need to look into this later, unless you have a good suggestion.

I think it's ok to not mark the test as skipped when the yaml extension is not loaded (skipped tests don't block the test-suite anyway), so just add a extension_loaded('yaml') condition on the yield and we're good to go.

so just add a extension_loaded('yaml') condition on the yield and we're good to go.

Okay, that works for me. Now done (and also updated the commit message + PR description).

Thanks @TimWolla!


Remove equipment suffixes from aircraft data

Some of them have equipment suffixes on the aircraft model, e.g. the DH8D. These should be removed and added to the common equipment suffixes list.

Turns out there were 9 that had it. Removed.


Data bind on navigation

From @snekbaev on November 27, 2016 22:44
Android, Nexus 5 with Marshmallow, NS 2.4.0. TS + NG. Plugins:
"nativescript-angular": "1.1.3",
"nativescript-direct-sms-send": "file:..\\nativescript_modules\\direct-sms-send",
"nativescript-messenger": "^1.2.0",
"nativescript-permissions": "^1.2.1",
"nativescript-ripple": "^1.0.1",

While continuing my journey with NS and I'm working on my first app. App is very simple and meant for personal use, it is my playground and I'm trying to get as best performance as possible. Current question is related to loading the data on navigation. I have "home" and "history" views. "Home" view has a link that takes user to the "history" view, which lists user smses: small image (set of 2) and the formatted date. Initially I used the ListView and NG's DatePipe and formatted the value in the markup. Tested the transition and noticed a bit of a delay before "history" view pops up, also ListView scrolling wasn't smooth enough. Then I decided to remove the DatePipe from the markup and rather apply it in the component directly to the data before assigning to the items property, so that ListView will render only simple text output, that made the scrolling super smooth. However, navigation lag was still there: a noticeable delay when I tap the "go to history" button. I traced it to the DatePipe's transform function.
Eventually what I wanted is to preprocess the data as much as possible beforehand and not do that on the main thread. So my next solution was to use a worker which does the heavy lifting now (via momentjs). Now navigation is instantaneous* and "history" view immediately loads with a activity indicator and then data comes. This way app feels way more responsive.
Thus, the question: is my understanding correct that when any data preprocessing is needed, even for simple cases like formatting the date basically I have to do that via workers to get the best UX, what eventually means that I probably should start doing nearly all my data binding via workers.
*when app is newly started and first ever navigation is done - there is a small initial delay, usually doesn't happen when doing back-forward after that.
Thank you!
Copied from original issue: NativeScript/NativeScript#3182

@nsndeck please download it from https://github.com/NativeScript/NativeScript/issues/3180#issuecomment-263279171 and use the following ListView:
<ListView [items]="listItems" rowHeight="60">
        <template let-item="item">
                <StackLayout>
                    <Image [src]="item.image"></Image>

                </StackLayout>
        </template>
</ListView>

meanwhile I will try to implement a version that uses date pipe with templates for ListView

Tested with templates:
 <ListView [items]="listItems" rowHeight="60" [itemTemplateSelector]="templateSelector">
         <template nsTemplateKey="odd" let-item="item">
            <StackLayout class="odd">
                <Image [src]="item.image"></Image>

            </StackLayout>
        </template>

        <template nsTemplateKey="even" let-item="item">
            <StackLayout class="even">
                <Image [src]="item.image"></Image>

            </StackLayout>
        </template>
    </ListView>

 public templateSelector = (item: any, index: number, items: any) => {
        return (index % 2) ? "odd" : "even";
    }

fast scrolling is not smooth either.

@nsndeck my initial question wasn't mainly about date pipe per se, but data preprocessing in general because I was getting a noticeable delay when navigating to the "history" view. Of course for some waiting around a second vs several hundreds of milliseconds might not be a big deal, but it just doesn't feel responsive enough to me. Moreover, it might take longer depending on the preprocessing. Refactoring to use worker very nicely improved the navigation UX: now it is reasonably fast, I can see the activity indicator and then the data shows up. However, worker based approach introduced own complexity and scattered the logic, nevertheless, it pays off by making things more responsive. Hopefully JS async/await will address this matter better, just like it is possible in Xamarin now.

@snekbaev Indeed using workers is a great option for improve UX look and feel. I asked for example since there are maybe something else which causes the delay. At the first place I saw a custom pattern for date pipe which is not the perfect case, since there are more native calls compared to a named pipe like fullDate. The funny thing is that we support such pattern, but when it is passed via angular2 there is an issue. I'll investigate and will share what I found here.

@nsndeck
a) I believe the delay is caused by the first/initial time that logic executes, that is whatever NS does there and by the fact that I did data preprocessing on the main thread: I fetched smses and each sms was piped through date pipe or momentjs (not via markup), that was done on UI thread which added up to the delay. Now I still have the initial navigation + firing up the worker extra delay. Yet this approach takes less time to converge.
b) I don't have NS experience without AngularJS, but while I was working on this test app I couldn't stop thinking that AngularJS overhead wasn't justified in my case: app startup time + size. Even if I skip these two I'm left with a bigger one: just because I have the power of NG it doesn't mean I can fully leverage from it, because doing certain things for "developer" convenience will ruin the UX for the end user. I'll try to come up with a more sophisticated test app next year and then try to get it done via pure NS and via NS + NG to validate or disprove my assumptions :)

@snekbaev I've just checked in a small optimization (some caching) for nativescript-intl plugin (which handles date pipe on nativescript side). Could you please try it with nativescript-intl - 0.0.8 and let me know about the result?
You may install it directly in app folder to override its dependency from nativescript-angular.
By the way you can place ListView inside GridLayout instead of StackLayout (this also will improve scrolling and UX experience)

@nsndeck could you please provide more detailed instructions on how to try it out. I'm new to npm and a naive attempt of tns plugin add nativescript-intl doesn't seem to work. My current packages:
{
  "description": "NativeScript Application",
  "license": "SEE LICENSE IN <your-license-filename>",
  "readme": "NativeScript Application",
  "repository": "<fill-your-repository-here>",
  "nativescript": {
    "id": "org.nativescript.ListViewIssue",
    "tns-android": {
      "version": "2.4.1"
    }
  },
  "dependencies": {
    "@angular/common": "2.2.1",
    "@angular/compiler": "2.2.1",
    "@angular/core": "2.2.1",
    "@angular/forms": "2.2.1",
    "@angular/http": "2.2.1",
    "@angular/platform-browser": "2.2.1",
    "@angular/platform-browser-dynamic": "2.2.1",
    "@angular/router": "3.2.1",
    "nativescript-angular": "1.2.0",
    "nativescript-theme-core": "^0.2.1",
    "reflect-metadata": "~0.1.8",
    "rxjs": "5.0.0-beta.12",
    "tns-core-modules": "2.4.0"
  },
  "devDependencies": {
    "babel-traverse": "6.19.0",
    "babel-types": "6.19.0",
    "babylon": "6.14.1",
    "lazy": "1.0.11",
    "nativescript-dev-android-snapshot": "^0.*.*",
    "nativescript-dev-typescript": "^0.3.2",
    "typescript": "^2.0.10",
    "zone.js": "~0.6.21"
  }
}

Sorry for the delay.
Simple npm install --save nativescript-intl inside application root folder should be enough.

Hi,
did that, got "nativescript-intl": "0.0.8" in package.json:
{
  "description": "NativeScript Application",
  "license": "SEE LICENSE IN <your-license-filename>",
  "readme": "NativeScript Application",
  "repository": "<fill-your-repository-here>",
  "nativescript": {
    "id": "org.nativescript.ListViewIssue",
    "tns-android": {
      "version": "2.4.1"
    }
  },
  "dependencies": {
    "@angular/common": "2.2.1",
    "@angular/compiler": "2.2.1",
    "@angular/core": "2.2.1",
    "@angular/forms": "2.2.1",
    "@angular/http": "2.2.1",
    "@angular/platform-browser": "2.2.1",
    "@angular/platform-browser-dynamic": "2.2.1",
    "@angular/router": "3.2.1",
    "nativescript-angular": "1.2.0",
    "nativescript-intl": "0.0.8",
    "nativescript-theme-core": "^0.2.1",
    "reflect-metadata": "~0.1.8",
    "rxjs": "5.0.0-beta.12",
    "tns-core-modules": "2.4.0"
  },
  "devDependencies": {
    "babel-traverse": "6.19.0",
    "babel-types": "6.19.0",
    "babylon": "6.14.1",
    "lazy": "1.0.11",
    "nativescript-dev-android-snapshot": "^0.*.*",
    "nativescript-dev-typescript": "^0.3.2",
    "typescript": "^2.0.10",
    "zone.js": "~0.6.21"
  }
}

On fast scrolling issue remains.

@snekbaev is this issue still reproducible with the latest nativescript-angular and the latest Angular related versions? Both NativeScript and Angular have introduced a lot of performance improvements so please do let me know if you are still experiencing this case.
CLosing this one due to inactivity.

@NickIliev haven't used NS since, feel free to close for now. Thank you!


Date value out of range

I'm using pyodata to get data from an url. Since the url contains a too far date in the past like "<d:StartDate>0001-01-01T00:00:00</d:StartDate>" I'm geting this error :"
value = datetime.datetime(1970, 1, 1, tzinfo=datetime.timezone.utc) + datetime.timedelta(milliseconds=int(value))
OverflowError: date value out of range"
Any help please
Asma

Hi,
Thank you for your reply please find attached json file because I'm not allowed to put the url
EmployeeData.zip

@asmaMdi  I'm sorry but you provided XML. It's not enough to store it in *.json you need to download it as JSON.
The following examples shows the difference:
Example XML:
https://services.odata.org/V2/Northwind/Northwind.svc/Employees
Example JSON:
https://services.odata.org/V2/Northwind/Northwind.svc/Employees?$format=json

I am really wondering what's the content of JSON because I tested pyodata with values for 0001-01-01T00:00:00 and also 9999-12-31T00:00:00 and both worked fine.

Hi,
sorry for my delayed response. Please find attached file.
EmployeeData.zip

@asmaMdi  Thank you very much indeed. The minimal value in your data is represented by the number -62135769600000 which is 172799999miliseconds greater than the current lowest value PyOData can read (-62135596800000).
If you subtract the date 0001-01-01T00:00:00 (your lowest value) from 1970-01-01T00:00:00 (OData base date) you get maximal value which -62135596800000.
import datetime

int((datetime.datetime(year=1, day=1, month=1) - datetime.datetime(year=1970, day=1, month=1)).total_seconds()) * 1000

# result = -62135596800000

If you subtract your lowest value from PyOData lowest value and add the result to the OData zero date, you get 1970-01-02T23:59:999000.
import datetime

datetime.datetime(year=1970, day=1, month=1) + datetime.timedelta(milliseconds=-62135596800001-(-62135769600000))

# result = datetime.datetime(1970, 1, 2, 23, 59, 59, 999000)

Can you, please, report the issue to your OData service provider?
An excerpt of you data:
   {"__metadata":{"uri":"https://{REMOVED_URL}/sap/byd/odata/cust/v1/odata_project/EmployeeEmployeeTypeCollection('0000000000011EE181BFC430CB1AAE84')",
   "type":"cust.EmployeeEmployeeType"},
   "ObjectID":"0000000000011EE181BFC430CB1AAE84",
   "ParentObjectID":"0000000000011EE181BFC41244F70E84",
   "EndDate":"\/Date(253402214400000)\/",
   "StartDate":"\/Date(-62135769600000)\/",
  "InternalEmployeeIndicator":false,

The corresponding XML excerpt:
<link href="EmployeeEmployeeTypeCollection('0000000000011EE181BFC430CB1AAE84')/Employee" rel="http://schemas.microsoft.com/ado/2007/08/dataservices/related/Employee" type="application/atom+xml;type=entry" title="Employee"/>
<content type="application/xml">
<m:properties>
<d:ObjectID>0000000000011EE181BFC430CB1AAE84</d:ObjectID>
<d:ParentObjectID>0000000000011EE181BFC41244F70E84</d:ParentObjectID>
<d:EndDate>9999-12-31T00:00:00</d:EndDate>
<d:StartDate>0001-01-01T00:00:00</d:StartDate>
<d:InternalEmployeeIndicator>false</d:InternalEmployeeIndicator>
</m:properties>
</content>

Thank your for your response. I will see with the OData service provider.

@asmaMdi If they refuse to fix the problem on their side, we will find a way how to work around this issue.

Great! Thank you very much
I reported the problem to the OData service provider.
Thank you

@asmaMdi thank you for the follow up. I am going to close this issue and I would like to ask you to re-open, if the service provider does not fix the issue on their side. I would like to thank you for your cooperation and patience.

@asmaMdi did you hear back from the provider? I also seem to be facing this issue on ByD and am curious what the outcome was.


Apply .text-dark for .badge with some .bg-* classes

In Bootstrap 4, class="badge badge-light" was enough, but in Bootstrap 5, it's class="badge bg-light text-dark". This is less convenient when switching between badge bg-dark and badge bg-light, since text-dark also has to be added or removed.
Bootstrap 5 should apply the styles for text-dark to .badge.bg-light and .badge.bg-warning. The Bootstrap 5 docs also recommend text-dark for bg-info, but I find that one is not necessary.
One workaround is to add this to our SCSS files, which is what Bootswatch does:
@import "~bootstrap/scss/bootstrap";

.badge {
  &.bg-warning,
  &.bg-info, /* optional */
  &.bg-light {
    @extend .text-dark;
  }
}

We removed it on purpose since it's basically duplicated code: it's even more flexible since you can mix background and foreground colours as you need.
I don't think we'll get this back, then.
Also using dark text colour is recommended to ensure sufficient contrats against light background. Using our core colours, other theme colours would fail regarding accessibility. Si Ils recommend to stick with it, obviously.
In my opinion, color and background-color should always be paired to ensure contrats. That's what I did in a branded fork called Boosted.
Keeping this open to discuss!

We don't use yet BS5 in real development projects but I agree with @theonlypwner, having to specify the color makes the use of badges less simple (imho).
We had already planned to add an override on our side to fix this. @ffoodd Thanks for the idea used in your BS fork (nice project btw), I'll use it if BS don't add pairing constraints for color and background-color.
So +1 to not have to add text color css class while using BS badge, background, etc., whatever the solution is.

Also, there is a similar issue with card requiring text-white, introduced in Bootstrap 4.

@theonlypwner This issue concerns v5 and badges, could please open another issue for what you found please?

@ffoodd I opened #34200 for card. Would #34045 already fix it, as some bg-* classes would set color and effectively apply text-white?

Yes it would but I doubt it gets merged.

@ffoodd why don't you apply the same approach with the Buttons?

Because for buttons we need to handle states, so it'd require to add states support top color utilities.

I thought it the other way around - badges could leverage the color-contrast function as well and keep the text-color utility classes for special cases…

With this issue still open, what's the status of the problem on the Bootstrap team side?
For end users, the previous badge color scheme was much simpler. IMHO, for badges we should not have to choose the color of the text.
If there are too many side effects by changing the backgrounds utilities, may be badge-${color} should be reintroduced?

Thinking it might make sense to revisit this for v5.3.0. Going to leave open for now—please feel free to open any PRs you think might be helpful in the mean time :).

Maybe this can be closed with the new text-bg-* classes?

Yes, it definitely can!


ALminer science keyword "low-mass star formation"

Dear Aida,
One particular science keyword "low-mass star formation" query seems to return an issue for pyvo (see below). I encounter no issues if querying for that in the proposal abstract ( alminer.keysearch({'proposal_abstract': ['"low-mass star formation"']}) ).
Any idea of what could be happening here? Thanks.
Cheers,
Carmen
lowmass=alminer.keysearch({'science_keyword': ['"low-mass star formation"']})

================================
alminer.keysearch results
================================
---------------------------------------------------------------------------
DALQueryError                             Traceback (most recent call last)
<ipython-input-8-2d95eb9d1adb> in <module>
----> 1 lowmass=alminer.keysearch({'science_keyword': ['"low-mass star formation"']})

~/opt/anaconda3/lib/python3.7/site-packages/alminer/alminer.py in keysearch(search_dict, tap_service, public, published, print_query, print_targets)
    456     if print_query:
    457         print("Your query is: {}".format(full_query))
--> 458     TAP_df = run_query(full_query, tap_service=tap_service)
    459     # Filter whether the user wants published data, unpublished data, or both (default)
    460     if published:  # case pf published = True

~/opt/anaconda3/lib/python3.7/site-packages/alminer/alminer.py in run_query(query_str, tap_service)
    182     service = _set_service(tap_service)
    183     # Run query
--> 184     pyvo_TAP_results = service.search(query_str)  # for large queries add maxrec=1000000
    185     # Transform output into astropy table first, then to a pandas DataFrame
    186     TAP_df = pyvo_TAP_results.to_table().to_pandas()

~/opt/anaconda3/lib/python3.7/site-packages/pyvo/dal/tap.py in run_sync(self, query, language, maxrec, uploads, **keywords)
    246         return self.create_query(
    247             query, language=language, maxrec=maxrec, uploads=uploads,
--> 248             **keywords).execute()
    249
    250     # alias for service discovery

~/opt/anaconda3/lib/python3.7/site-packages/pyvo/dal/tap.py in execute(self)
    940            for errors parsing the VOTable response
    941         """
--> 942         return TAPResults(self.execute_votable(), url=self.queryurl, session=self._session)
    943
    944     def submit(self, post=False):

~/opt/anaconda3/lib/python3.7/site-packages/pyvo/dal/adhoc.py in __init__(self, votable, url, session)
    109     """
    110     def __init__(self, votable, url=None, session=None):
--> 111         super().__init__(votable, url=url, session=session)
    112
    113         self._adhocservices = list(

~/opt/anaconda3/lib/python3.7/site-packages/pyvo/dal/query.py in __init__(self, votable, url, session)
    318         self._status = self._findstatus(votable)
    319         if self._status[0].lower() not in ("ok", "overflow"):
--> 320             raise DALQueryError(self._status[1], self._status[0], url)
    321
    322         self._resultstable = self._findresultstable(votable)

DALQueryError: ORA-01489: result of string concatenation is too long
 ORA-01489: result of string concatenation is too long

Hey Carmen, sorry for the super late reply. I didn't realize you had opened a second issue with the other one and I totally missed this one. This is an issue upstream at ALMA that we cannot fix unfortunately. It only impacts some projects so I would tackle it by trying to figure out which project is causing it and omit it from the query as a work around until it gets fixed on the server side. It's very difficult with such a generic query, so I would try to narrow down the query if at all possible and go from there. Sorry that this is not so helpful. Let me know if I can help otherwise.

Hi Carmen, this issue has now been solved in the most recent release of the ALMA archive. So I will close this ticket, but please feel free to open a new one if you encounter other issues.


chore!: remove ShareCommitAndSignature

Closes https://github.com/celestiaorg/celestia-app/issues/1269

Codecov Report

Merging #1270 (80d647b) into main (b6e2651) will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1270      +/-   ##
==========================================
+ Coverage   48.84%   48.85%   +0.01%
==========================================
  Files          75       75
  Lines        4369     4368       -1
==========================================
  Hits         2134     2134
+ Misses       2055     2054       -1
  Partials      180      180

Impacted Files
Coverage Δ

x/blob/payforblob.go
0.00% <0.00%> (ø)

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


SQL syntax error when using $table->timestamps() in migrations

Laravel Version: 5.5-dev (ef0e37d44182ac5043b5459bb25b1861e8e036df)
PHP Version: 7.1.7
Database Driver & Version: PDO with MySQL 5.5.55

Description:
I'm trying to execute a migration which contains $table->timestamps() which results in the following error:
 [Illuminate\Database\QueryException]
  SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '() null, `updated_at` timestamp() null) default character set utf8mb4 collate ut' at line 1 (SQL: create table `invoices` (`id` int unsigned not null auto_increment primary key, `created_at` timestamp() null, `updated_at` timestamp() null) default character set utf8mb4 collate utf8mb4_unicode_ci)

  [PDOException]
  SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '() null, `updated_at` timestamp() null) default character set utf8mb4 collate ut' at line 1

When I execute the SQL statement manually and remove the (0) part after the timestamp the migration runs just fine.
This might be related to PR #18847
Steps To Reproduce:
Create a migration with $table->timestamps() and execute it.
<?php

use Illuminate\Database\Migrations\Migration;
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Support\Facades\Schema;

class CreateFooTable extends Migration
{
    /**
     * Run the migrations.
     */
    public function up()
    {
        Schema::create('foo', function (Blueprint $table) {
            $table->increments('id');
            $table->timestamps();
        });
    }

    /**
     * Reverse the migrations.
     */
    public function down()
    {
        Schema::dropIfExists('foo');
    }
}

If I'm reading the docs correctly the TIMESTAMP(N) syntax is possible as of MySQL 5.6: https://dev.mysql.com/doc/refman/5.6/en/fractional-seconds.html

As you see MySQL 5.5 doesn't support it: https://dev.mysql.com/doc/refman/5.5/en/fractional-seconds.html (the same link you shared but for 5.5)

Does this mean we've dropped MySQL 5.5 support in Laravel 5.5?

indeed, column precision was added to timestamp in MysqlGrammar, so it's a breaking change and will need mysql 5.6

There's a difference between an accidental change and an intentional one. Was this an informed decision to drop MySQL 5.5 support, or did it just accidentally happen with the introduction of precisions?

I would believe that its an informed decision to drop MySQL 5.5 support.

Seems accidental. No mention of it on the PR.

Due to the pr #20465 of @themsaid this should be closed.

@dschniepp thanks for the heads up :)

Thanks!

Schema::create('comments', function (Blueprint $table) {
$table->increments('id');
$table->text('body');
$table->string('url',255)->nullable();
$table->integer('user_id')->unsigned();
$table->integer('commentable_id')->unsigned();
$table->string('commentable_type')->unsigned();
$table->foreign('user_id')->references('id')->on('users');
$table->timestamps();
});
this is my code but i m getting following error
i m new in laravel coding
can anyone help me?
SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'unsigned not null, created_at timestamp null, updated_at timestamp null) def' at line 1 (SQL: create table comments (id int unsigned not null auto_increment primary key, body text not null, url varchar(191) null, user_id int unsigned not null, commentable_id int unsigned not null, commentable_type varchar(191) unsigned not null, created_at timestamp null, updated_at timestamp null) default character set utf8mb4 collate 'utf8mb4_unicode_ci')


need some help here: ~/Object_Detection_API/models/research/object_detection/training/labelmap.pbtxt; No such file or directory

I test it on Ubuntu 18.04, tensorlfow 1.10 and it works well on Jupyter tutorial. But when I run this:
python train.py --logtostderr --train_dir=training/ --pipeline_config_path=training/faster_rcnn_inception_v2_pets.config
and I got this error:

WARNING:tensorflow:From /home/bingbing/anaconda3/envs/ob_env/lib/python3.5/site-packages/tensorflow/python/platform/app.py:125: main (from __main__) is deprecated and will be removed in a future version.
Instructions for updating:
Use object_detection/model_main.py.
W1101 12:19:09.538238<PHONE_NUMBER>00864 tf_logging.py:125] From /home/bingbing/anaconda3/envs/ob_env/lib/python3.5/site-packages/tensorflow/python/platform/app.py:125: main (from __main__) is deprecated and will be removed in a future version.
Instructions for updating:
Use object_detection/model_main.py.
WARNING:tensorflow:From /home/bingbing/Object_Detection_API/models/research/object_detection/legacy/trainer.py:265: create_global_step (from tensorflow.contrib.framework.python.ops.variables) is deprecated and will be removed in a future version.
Instructions for updating:
Please switch to tf.train.create_global_step
W1101 12:19:09.587111<PHONE_NUMBER>00864 tf_logging.py:125] From /home/bingbing/Object_Detection_API/models/research/object_detection/legacy/trainer.py:265: create_global_step (from tensorflow.contrib.framework.python.ops.variables) is deprecated and will be removed in a future version.
Instructions for updating:
Please switch to tf.train.create_global_step
Traceback (most recent call last):
  File "train.py", line 184, in <module>
    tf.app.run()
  File "/home/bingbing/anaconda3/envs/ob_env/lib/python3.5/site-packages/tensorflow/python/platform/app.py", line 125, in run
    _sys.exit(main(argv))
  File "/home/bingbing/anaconda3/envs/ob_env/lib/python3.5/site-packages/tensorflow/python/util/deprecation.py", line 272, in new_func
    return func(*args, **kwargs)
  File "train.py", line 180, in main
    graph_hook_fn=graph_rewriter_fn)
  File "/home/bingbing/Object_Detection_API/models/research/object_detection/legacy/trainer.py", line 279, in train
    train_config.prefetch_queue_capacity, data_augmentation_options)
  File "/home/bingbing/Object_Detection_API/models/research/object_detection/legacy/trainer.py", line 59, in create_input_queue
    tensor_dict = create_tensor_dict_fn()
  File "train.py", line 121, in get_next
    dataset_builder.build(config)).get_next()
  File "/home/bingbing/Object_Detection_API/models/research/object_detection/builders/dataset_builder.py", line 123, in build
    num_additional_channels=input_reader_config.num_additional_channels)
  File "/home/bingbing/Object_Detection_API/models/research/object_detection/data_decoders/tf_example_decoder.py", line 297, in __init__
    default_value=''),
  File "/home/bingbing/Object_Detection_API/models/research/object_detection/data_decoders/tf_example_decoder.py", line 59, in __init__
    label_map_proto_file, use_display_name=False)
  File "/home/bingbing/Object_Detection_API/models/research/object_detection/utils/label_map_util.py", line 164, in get_label_map_dict
    label_map = load_labelmap(label_map_path)
  File "/home/bingbing/Object_Detection_API/models/research/object_detection/utils/label_map_util.py", line 133, in load_labelmap
    label_map_string = fid.read()
  File "/home/bingbing/anaconda3/envs/ob_env/lib/python3.5/site-packages/tensorflow/python/lib/io/file_io.py", line 125, in read
    self._preread_check()
  File "/home/bingbing/anaconda3/envs/ob_env/lib/python3.5/site-packages/tensorflow/python/lib/io/file_io.py", line 85, in _preread_check
    compat.as_bytes(self.__name), 1024 * 512, status)
  File "/home/bingbing/anaconda3/envs/ob_env/lib/python3.5/site-packages/tensorflow/python/framework/errors_impl.py", line 519, in __exit__
    c_api.TF_GetCode(self.status.status))
tensorflow.python.framework.errors_impl.NotFoundError: ~/Object_Detection_API/models/research/object_detection/training/labelmap.pbtxt; No such file or directory

In fact that labelmap.pbtxt file do exist in that directory. I dont know how to fix this, thank you for your helping!

Sorry, problem is solved. Here, '~/' can't to be used. Change '~/' to '/home/username/' to fix this problem


lose anything

https://github.com/magicoflolis/Userscript-Plus/releases
v2.4.13

Added ability to customize width
This may resolve issue


Consider using RouteTemplateDefinition for IKameletSpec.template

Please describe the task that needs to be done
Currently it's a custom object with having FromDefinition as a child
https://github.com/KaotoIO/kaoto-next/blob/main/packages/ui/src/models/kamelets-catalog.ts#L36
Kamelet spec.template is actually a RouteTemplateDefinition, so we should be able to use RouteTemplateDefinition from camelYamlDsl.d.ts
We need to investigate if any other adjustment is needed, for example RouteTemplateDefinition accepts route as well, and from is optional. It means Kamelet spec.template also accepts route unless some special restriction is added in Camel K (I guess not).

At least it succeeds to kubectl apply -f kamelet-with-route.kamelet.yaml  with having a route in spec.template.route  instead of in from, and kamel describe kamelet successfully shows the contents


koord-manager: refactor noderesource and add resource calculation extenders

Ⅰ. Describe what this PR does

Add the following extensions for the node-resource controller:

NodeSync: allow the plugin to implement the node update check.
ResourceReset: allow the plugin to reset the corresponding resources for degradation or colocation-disabled.
ResourceCalculate: allow the plugin to implement different resource calculation algorithms other than the batch resource overcommitment.

Ⅱ. Does this pull request fix one issue?

Fixes #1060.
Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews
Just keep the GPU resources reconciliation since it will be refactored in the future.
V. Checklist

[x] I have written necessary docs and comments
[x] I have added necessary unit tests and integration tests
[X] All checks passed in make test

We keep the device resource calculation unchanged, which would be moved into a DP or add a standard implementation.

/hold until local patch merged

/hold cancel
/approve

/lgtm


SW-4308 Add API for replacing monitoring plot

POST /api/v1/tracking/observations/{observationId}/plots/{plotId}/replace will
request that a monitoring plot in an observation be replaced.
Currently this triggers an email notification to be sent to the organization's
Terraware contact (or to the support email if there's no contact) but does not
actually cause the plot to be replaced. However, the API definition can be used
for client-side code generation.

Current dependencies on/for this PR:

main

PR #1396

PR #1397   👈

This comment was auto-generated by Graphite.

Merge activity

Oct 16, 11:40 AM: @sgrimm started a stack merge that includes this pull request via Graphite.


ORCA code of conduct link is broken

Describe the bug
Looks like the destination URL includes the period at the end of the sentence, so it ends up being broken for end users even though the display text of the URL is correct.
To Reproduce
Fill out ORCA form and navigate to the final screen with code of conduct info.
Try to click on the King County code of conduct link in the following block of text:
"City of Seattle ORCA Opportunity Program Rules: Program participants are expected to follow the Metro Code of Conduct, http://kingcounty.gov/depts/transportation/metro/about/safety-security/code-of-conduct.aspx."
Expected behavior
Expect to navigate to http://kingcounty.gov/depts/transportation/metro/about/safety-security/code-of-conduct.aspx
... but it actually navigates to http://kingcounty.gov/depts/transportation/metro/about/safety-security/code-of-conduct.aspx. (notice the period at the end) which ends up hitting a 404 not found page.

For the ORCA program, we could probably work around this by simply deleting the trailing period.

Looks like a problem with com.linkedin.urls.detection.UrlDetector used in the Civiform TextFormatter.

@elisekalstad feel free to unassign yourself once the workaround of removing the trailing period is done. We'll keep the issue open to track the permanent fix.


Drop 32bit arm builds

The sequel to #128

Codecov Report

Merging #129 (3d5b866) into main (db5d5c1) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #129   +/-   ##
=======================================
  Coverage   95.42%   95.42%
=======================================
  Files          15       15
  Lines        1816     1816
=======================================
  Hits         1733     1733
  Misses         62       62
  Partials       21       21

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 db5d5c1...3d5b866. Read the comment docs.